| Status | Approved |
|---|---|
| Owner | TATARU-ext, Eugenia |
| Stakeholders | CASTELEIRA, Patricia @Lietaert Massimo |
| Jira Request ID | ERP-497 - Getting issue details... STATUS |
| Jira Development ID | ERP-718 - Getting issue details... STATUS |
High- Level Specification
| Parameter | Value |
|---|---|
| Application System (Source) | Descartes FTP Website |
| Application System ( Target) | SAP GTS E4H |
| Business Process Reference | 12.02.01.01. Manage Classification Codes |
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 to provide the most current regulatory data for Customs Classification on commodity codes (known as HTS codes). 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 HTS Customs classification codes published by the Government into SAP GTS. The update should occur when a file is provided by Descartes. Updates can be received on a regularly basis, hence the set up of the program will be marked as daily.
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 HTS file must be available in all systems for the product-classification codes to happen.
Process Flow Diagram
Step | Description | Comment |
|---|---|---|
1 | HTS XML codes published by Descartes | Commodity codes |
2 | File interface program to fetch the HTS XML file and place it in the application server | |
3 | Upload to GTS system using the standard transaction /n/SAPSLL/LLNS_UPL102 | |
4 | Notification is send to the GTS IT users if successful/failed | |
5 | If upload fails, log the details of the upload and GTS IT users to troubleshoot the error |
Assumptions
- SAP GTS E4H system will be available at the time of execution.
- Numbering schemes content & Legal Regulations will be configured in GTS system.
- Upload logs will be generated.
- Notification functionality will be handled by standard GTS Fiori Launchpad.
- Users listed under DL sco-digops-gts@syensqo.com will be used as basis to receive notification via Fiori whenever custom program runs successfully or fails.
Dependencies
Descartes must published first the XML content for HTS codes.
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 content 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
Existing process is manual upload of HTS XML file on a regularly basis and it needs to be replaced by this automated solution.
Variant for the file weekly upload program of /n/SAPSLL/LLNS_UPL102 (/SAPSLL/NSC_NUM_UPLOAD_102).
→ Number specific-parameters:
- Data Provider: Descartes
- Numbering schemes content: **HTS
→ Application Servers:
- Path of number file: application server.
→ General Control Parameters:
- Package check active: ticked
- Update Schema definition: ticked
- Simulation Mode: only when is controlled manually or testing purposes.
Data Structure
Source Structure
The following fields will be used to provide the required information for this interface:
| Field | Description |
|---|---|
Target Structure
The following fields will be used to provide the required information for this interface:
| Field | Description |
|---|---|
Mapping and Calculation
| Source Table | API or Portlet Name | Source Field | Required (Y/N) | Description | Target Field | API or Portlet Name | Target Field | Required (Y/N) | Description | Rule Type | Rule Instruction |
|---|---|---|---|---|---|---|---|---|---|---|---|
Processing Logic
Processing within Source
Develop a custom interface which will retrieve on a daily basis the FTP XML HTS content from Descartes (Source).
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 week (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.
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?):
- Extract - Not able to access folder → notification via Fiori Launchapd to the GTS IT users
- Upload- File error when moving file from FTP site to Application server → notification via Fiori Launchapd to the GTS IT users
- 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
| ID | Condition | Expected Results |
|---|---|---|
| 1 | Sample file from Descartes test folder to be uploaded | File should be fetched and uploaded to GTS system |
| 2 | Upload a file with error | File follows error procedure and sends notification to GTS IT user |
| 3 | Upload a file successfully | Sends notification to GTS IT user |
Test Considerations/Dependencies
Other Information
Development Details
Package
| Package Name | Parent Package |
|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|
