| Status | Approved |
|---|---|
| Owner | TATARU-ext, Eugenia |
| Stakeholders | |
| Jira Request ID | ERP-496 - Getting issue details... STATUS |
| Jira Development ID | ERP-717 - 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 system interface defines the API to be provided or consumed.
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 system interface is to automatize the process by, 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 Descartes. Updates can be received on a weekly basis, hence the set up of the program will be marked as weekly.
In terms of errors that can occur via the automatic upload, IT GTS users will get a notification within Fiori Launchpad in order to troubleshoot the problem (manual intervention).
The file movement (CPI-S/4) is covered via FS: https://wiki.syensqo.com/x/elvJO.
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
Step | Description | Comment |
|---|---|---|
1 | EARUS XML codes published by Descartes | |
2 | File interface program to fetch the EARUS XML file and place it in the application server | |
3 | Upload to GTS system using the standard transaction /n/SAPSLL/LLNS_UPL002 | |
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 | |
6 | After a successful upload , the program will then archive the file from the directory. |
Assumptions
- SAP GTS E4H system will be available at the time of upload.
- 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 EARUS codes.
Security, Integrity and Controls
- 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 XML upload of ECCN codes for the Legal Reg. EARUS on a regularly basis and it needs to be replaced by this automated solution.
Variant for the file weekly upload program of /SAPSLL/LLNS_UPL002 (/SAPSLL/NSC_NUM_UPLOAD_002).
→ Number specific-parameters:
- Data Provider: Descartes
- Numbering schemes content: ECCN**
→ 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.
Additional explanation on some of the mentioned fields:
- Path of Number files → This is the path taken from the APP server.
- Package Check Active→ If this indicator is active a new version can only be loaded if all packages or files were loaded successfully for the previous version. If is deactivated you can upload a new version, although the previous version was not loaded completely (not recommended).
- Update Schema Definition → Displays whether scheme definitions are to be transferred from the upload file.
- Simulation Mode → If this indicator is selected, processing is only performed in the simulation mode and results cannot be updated to the database.
API Use
API usage is provided.
Data Structure
N/A
The following fields will be used to provide the required data structure of the interface:
| Parent | Field | Description | Mandatory (Y/N) | Data Type |
|---|---|---|---|---|
Calculation and Validation
N/A
| Parent | Field | Rule Type | Rule Instruction |
|---|---|---|---|
Processing Logic
Once the XML files are fetched from the Data Provider, these will be uploaded to GTS system using standard transaction /n/SAPSLL/LLNS_UPL002. This program will be scheduled to run once a week (date & time TBD).
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):
| Key fields | Data Element | Data Type | Length |
|---|---|---|---|
| Client | MANDT | CLNT | 3 |
| User ID | SYUNAME | CHAR | 12 |
Language Requirements
English
User Interface Requirements
Volumetrics
Performance Consideration
For the XML size during upload, 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 | Upload a file with error | File follows error procedure and sends notification to GTS IT user |
| 2 | 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 |
|---|---|---|---|