| Status | Approved |
|---|---|
| Owner | TATARU-ext, Eugenia |
| Stakeholders | CASTELEIRA, Patricia @Massimo Lietaert |
| Jira Request ID | ERP-496 |
| Jira Development ID | ERP-716 |
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
Syensqo uses Descartes which is the market-leading global trade content for GTS to provide the most current regulatory data for Compliance Classification Codes Export Control on EARUS. This data provider is a 3rd party system for SAP GTS. 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 EARUS compliance classification codes published by the Government into SAP GTS. The update should occur when a file is provided by Data provider Descartes. Updates can be received on a weekly basis, hence the set up of the program will be marked as weekly.
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 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 |
Assumptions
- SAP GTS E4H system will be available at the time of execution.
- SPL legal regulation will be configured in GTS system.
- Upload logs will be generated.
- Notification functionality will be handled by standard GTS Fiori Launchpad.
Dependencies
Descartes must published the XML for EARUS.
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 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
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
Processing within Middleware
Processing within Target
Interface Dependency
Interface Constraints
Delivery Requirements
Delta or Full Load Requirements
Interface Alert & Monitoring
Interface Reporting
Language Requirements
User Interface Requirements
Volumetrics
Performance Consideration
Error Handling
Testing
How to Test
Test Conditions and Expected Results
| ID | Condition | Expected Results |
|---|---|---|
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 |
|---|---|---|---|