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 SFTP location in a zip format. The files are supposed to the stored after successful upload to GTS system - for audit purposes (the upload program to the GTS system is covered within FS ERP-717.

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) using secure protocols.

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 XML upload of ECCN codes for the Legal Reg. EARUS 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).
• Connection details:
  • SFTP Server: sftp://download.custominfo.com
  • Directory Path: /E4H/Dual Use and LDR
  • Filename : E4H_ECCN_US_EN_vXXXXXX.zip (do not select the other .zip like *LDR or *DULUS)

• The program should download the .zip folder, unzip it and upload the XML in GTS.
• If error appears during integration process, a notification should be send to the GTS IT users (see Interface Alert & Monitoring chapter).

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

For this integration there will be no processing within the Source. 

Processing within Middleware

CPI will pass the file without modification or transformation.

Processing within Target

The files will not be modified in the target but placed directly in the file server without any transformation. Once this interface notifies the GTS system via the System Interface developed in ERP-717, the data will be loaded to relevant tables.

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

Interface Dependency

N/A

Interface Constraints

Upon polling, if CPI finds an updated file in Data Provider (Descartes) SFTP, it will be processed.

Descartes does not provide a Test or Dev tenant, so all CPI and GTS tenants will connect and access the Production Descartes SFTP.

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 as 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

Technical alerts are sent to the GTS IT super user team listed under sco-digops-gts@syensqo.com in case the interface face any issues. 

CALM interface alerts are send out if the interface has an issue allowing users to monitor and manage system.

Interface Reporting

N/A

Language Requirements

English

User Interface Requirements

N/A

Volumetrics

File sizes: 
ZIP file, less than 1MB

Extracted XML file, around 5MB

Performance Consideration

File sizes: 
ZIP file, less than 1MB

Extracted XML file, around 5MB

Error Handling

Log requirements:

1. Extract - Not able to access file server→ technical alert to the GTS IT users.
2. Authorization issue to access the FTP site → technical alert to the GTS IT users.
3. File matching the naming convention is not found in the FTP site →  technical alert to the GTS IT users.
4. Interface face issue to trigger the wrapper program →  technical alert to the GTS IT users.

Testing

How to Test

Open the FTP site and login with the credentials given. 

Download the file with naming convention E4H_EECN_US_EN_vXXXXX.zip from the week before of the run date.

Run the file interface and the file should be successfully placed in the defined file server for this requirement.

Test Conditions and Expected Results

Test Considerations/Dependencies

Test the file interface program and then test the standard transaction to upload the file to GTS system.

Other Information

Development Details

Package

Other Development Objects

Appendix

See also

Change log