High- Level Specification

Functional Overview

Syensqo uses Descartes (3rd party system) which is the market-leading global trade content for GTS that provides the most current regulatory data for Compliance Classification Codes (Export Control on EARUS). New classification codes are always provided by Descartes on a regular basis via XML files.

The purpose of this integration specification is to automatize the process by, extracting the list of EARUS compliance classification codes published by the Government from Descartes's website and upload it to GTS. The update should occur when a file is provided by Descartes. Updates can be received on a weekly basis, hence the set up of the program will be marked as weekly to do the file movement. The files will be taken from the directory path within Descartes website in a zip format. The files are supposed to the stored after successful upload to GTS system - audit purposes.

In terms of errors that can occur 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. 

This new automatization 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 Cloud Platform Integration connectivity is available.
2. SAP GTS E4H system is available at the time of extraction.

Dependencies

Descartes must published first the XML content for Export Control Classification Numbers- EARUS codes.

Security, Integrity and Controls

• Connection to Descartes to retrieve files will use SAP Integration Suite Middleware CPI (download zip, unzip, upload).

Configuration Requirements

N/A

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

Existing process is a manual upload of ECCN EARUS XML files on a regularly basis into GTS and it needs to be replaced by this automated solution:

• The CPI middleware will handle the file from FTP and push it to GTS (S/4 instance).
• Path to the XML files within Descartes website: [DIR] Files (your files available for download) → [DIR] E4H → Open Parent directory: Dual Use and LDR/ → Take the .zip under E4H_EECN_US_EN_vXXXXX (do not mark the other .zip under *LDR or *DULUS- TBC with the Business)
• The parent directory contains all XMLs stored in format .zip. 
• The program should download the .zip folders, unzip it and upload the XML one by one or multiple files at once in GTS.
• If error appears during integration process, a notification should be send to the GTS IT users stored under the custom table (see Interface Alert & Monitoring chapter) via Fiori Launchpad standard process.
• Once files are successfully uploaded, these should be archived inside GTS system.

Data Structure

N/A

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

N/A

Processing Logic

Processing within Source

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

The day and time of the weekly setup to be confirmed later.

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.

Users listed under DL sco-digops-gts@syensqo.com will be added to a custom maintenance table (SM30):

Interface Reporting

N/A

Language Requirements

English

User Interface Requirements

N/A

Volumetrics

Performance Consideration

For the XML size during extraction, reach out to the owner of the FS to get the details to login to Descartes website and to do the technical 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 has 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