High- Level Specification

Functional Overview

The functional design of the Integration Process defines both inbound and outbound interfaces. An integration defines a specific physical interaction that will need to occur between the system and an external application in response to some business event. 

Syensqo uses Descartes (3rd party system) which is the market-leading global trade content for GTS that provides the most current regulatory data for Customs Classification Codes. HTS (Harmonized Tariff Schedule) codes are used to classify imported and exported goods. The first six digits are the international Harmonized System (HS) code, and the last four are specific to the U.S. and its import duties and statistical categories. 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 HTS (commodity & tariff codes) customs 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 daily basis, hence the set up of the program will be marked as daily 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 (the upload program to the GTS system is covered within FS: https://wiki.syensqo.com/x/ZWfJO).

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. 

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 HTS 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 HTS 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 (run on a daily basis).

• 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 → Parent directory: Take all the .zip available/found under all subfolders inside E4H, exception makes folder Dual Use and LDR (do not mark this one).

Note1: any future country that might show up on E4H directory which is not listed below should be picked up too; if the case, and same applies for the .zip files inside the subfolders).

• 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.

Note2: always upload the latest version of the zip file. If at the time of the extraction the version number is same as per the last run program should end - no action.

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 daily basis the FTP XML EARUS content from Descartes (Source).

The time of the daily setup to be confirmed on a later stage.

Processing within Middleware

Processing within Target

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

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 day (TBD the time of the daily run).

Delta or Full Load Requirements

First upload will be considered the initial upload for HTS 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, 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 Launchpad to the GTS IT users
3. No file available at the time when the custom program is scheduled to run →  End program.
4. Always upload the latest version of the zip file. If at the time of the extraction the version number is same as per the last run  → End program.

Testing

How to Test

Test Conditions and Expected Results

Test Considerations/Dependencies

Other Information

Development Details

Package

Other Development Objects

Appendix

See also

Change log