High- Level Specification

Functional Overview

Syensqo uses Descartes which is the market-leading global trade content for GTS to provide the most current regulatory data for Compliance Classification Codes Export Control on EARUS. This data provider is a 3rd party system for SAP GTS. New classification codes are provided by Descartes regularly within XML files.

The purpose of this interface is to automatize the process, by pulling & uploading the list of EARUS compliance classification codes published by the Government into SAP GTS. The update should occur when a file is provided by Data provider Descartes. Updates can be received on a weekly basis, hence the set up of the program will be marked as weekly.

Whenever an error occurs via the automatic interface, IT GTS users will get a notification within Fiori Launchpad in order to troubleshoot the problem (manual intervention).

Scope and Objectives

While GTS is the leading system for classification codes and product assignment, this step is the prerequisite before classifying any product and before any export can happen in the system. 

The emails that Descartes is sending to GTS IT team with the new classification codes will be replaced by this new automatization which follows one straight objective: to reduce the workload of man/hour which involves emails, dependency on an user action/availability or knowledge transfer within the team.

With the 3 different instances of GTS system for US, China and Rest of World, the EARUS file must be available in all systems for the product-classification codes to happen.

Process Flow Diagram

Assumptions

1. SAP GTS E4H system will be available at the time of execution.
2. SPL legal regulation will be configured in GTS system.
3. Upload logs will be generated.
4. Notification functionality will be handled by standard GTS Fiori Launchpad.
5. Users listed under DL sco-digops-gts@syensqo.com will be used as basis to send notification via Fiori whenever custom program runs successfully or fails.

Dependencies

Descartes must published first the XML content for EARUS.

Security, Integrity and Controls

Security Considerations for the Integration are:

• Connection to Descartes to retrieve files will use SAP Integration Suite Middleware (zip, unzip, download).
• Uploading the file to an accessible file server (to be accessed by the Standard Program) is to be done securely through Cloud Connector.

Configuration Requirements

You have made the following settings in Customizing for the GTS system:

• You have defined numbering schemes in Customizing for the general settings. The numbering scheme contains the underlying structure for the numbers. 

• You have defined and configured the necessary legal regulations in Customizing and activated them for the application areas.

• You have set up system communication.

• You transferred products from your feeder system to the GTS system.

Special Requirements

Overwriting should be possible. Whenever there is an emergency and cannot wait for the interface program to run, the GTS IT user can login to the FTP server, download the XML file and then upload the file to GTS manually.. However, at the next run of the program this should overwrite the entries stated by the GTS IT user.

Design Rationale

Data Structure

Source Structure

The following fields will be used to provide the required information for this interface:

Target Structure

The following fields will be used to provide the required information for this interface:

Mapping and Calculation

Processing Logic

Processing within Source

Develop a custom interface which will retrieve on a weekly basis the FTP XML EARUS content from Descartes (Source).

Processing within Middleware

N/A

Processing within Target

The files fetched from the data provider will be uploaded to GTS system with standard transaction /n/SAPSLL/LLNS_UPL002.

Interface Dependency

N/A

Interface Constraints

N/A

Delivery Requirements

This interface should work like a batch program which runs on the same time every week (TBD the day and time).

Delta or Full Load Requirements

First upload will be considered the initial upload for EARUS XML classification codes → full upload.

After that, the rest are considered delta, whenever new codes shows up or changes.

Interface Alert & Monitoring

A notification via Fiori Launchpad (standard) is send to the GTS IT user if any error occurs during file upload in GTS, but also if upload was successfully executed.

Interface Reporting

NN/A

Language Requirements

English

User Interface Requirements

N/A

Volumetrics

Performance Consideration

For the XML size, reach out to the owner of the FS to provide details to login to Descartes website and do the check.

Error Handling

When a file has errors during upload the file is not archived from the directory. A notification is sent to the GTS IT user to check the error. Worst case, the user must upload manually the XML and do correction manually in GTS.

If no file found the customs program will stop with an error ending the program.

Log requirements (Is there a log that shows the job was run?):

1. Extract - Not able to access folder → notification via Fiori Launchapd to the GTS IT users
2. Upload- File error when moving file from FTP site to Application server →  notification via Fiori Launchapd to the GTS IT users
3. No file available at the time when the custom program is scheduled to run →  End program.

Testing

How to Test

Test Conditions and Expected Results

Test Considerations/Dependencies

N/A

Other Information

Development Details

Package

Other Development Objects

Appendix

See also

Change log