| Status | |
|---|---|
| Owner | |
| Stakeholders | |
| Jira Request ID | https://syensqo.atlassian.net/browse/ERP-102 |
| Jira Development ID |
High- Level Specification
| Parameter | Value |
|---|---|
| Application System | S/4HANA |
| Business Process Reference | 12.01.01.01. Set-up GTS Organizational Structure |
Functional Overview
Foreign Trade Organization(FTO) and Legal Units(LU) are the organizational elements in GTS. These organizational elements are required to comply with the legal and customs requirements to allow execution of the respective country's import and export processes.
Foreign Trade Organization (FTO) is the top level organizational unit in SAP GTS and it corresponds to the company code in the feeder system.
Legal unit(LU) corresponds to the plant in the feeder system. FTO and LU are created as business partner in SAP GTS system with different roles.
The objective of this application job is to automate the creation of the FTO and LU business partner in GTS by executing the report in the feeder S/4 HANA system.
Scope and Objectives
Foreign Trade Organization and Legal unit business partners are currently created manually in SAP GTS. This is error prone and labour intensive. In Sy-Way the creation of these elements will be automated.
This document provides the rules and mappings required for these automations. Per one company code in S/4 there will be one FTO created in GTS.
Per one plant in S/4 there will be one Legal Unit created in GTS.
Process Flow Diagram
Step | Description | Comment |
|---|---|---|
| 1. | Company codes are created in S/4 system. | |
| 2 | Plants are created in S/4 systems. | |
| 3 | Company codes to be replicated in GTS system as a business partner | Each GTS instance will get the data from the corresponding S/4 Instance |
| 4 | Plants to be replicated in GTS system as a business partner | Each GTS instance will get the data from the corresponding S/4 Instance |
Assumptions
- Company code must be available in S/4 HANA system.
- Plants must be available in S/4 HANA system.
- SAP GTS system should be available during transfer.
- Address elements like name, street, city , country etc are available in the feeder business partner.
Dependencies
Finance team will be responsible for the creation of company codes.
Supply Chain team will be responsible for the creation of plants.
These are mandatory for the bp creation in GTS.
Security, Integrity and Controls
Master Data Specialist - Business Partner Data is the role for the BP transaction and it should be available for the application job to create bp.
Configuration Requirements
RFC connection should be established between the S/4 HANA and GTS E4H system.
Language Requirements
The data should be replicated in the same language that is maintained in S/4 HANA
Special Requirements
N/A
Design Rationale
Functional Requirements
The program shall create FTO and LU as Business Partners in GTS by referring to the data from the S/4 HANA.
The program shall use the below naming conventions
- For FTOs, the naming convention will be FTO_XXXX where XXXX will be the company code from S/4 HANA
- For LUs, the naming convention will be LU_XXXX where XXXX is the plant from S/4 HANA.
The program shall create FTO in 3 different BP roles -000000 Business Partner (General), SLLFTO(Foreign Trade Org) and FS0000(Financial Services BP).
The program shall create LU in 3 different BP roles- 000000 Business Partner (General), SLLSIT(Legal Unit) and FS0000(Financial Services BP).
The program shall copy the below BP fields for FTO and LU
- BP number from T001-BUKRS/T001W-WERKS field and add the corresponding prefix of FTO_for company codes and LU_ for plants.
- All other address details to be copied from the ADRC table.
The program shall mark company codes / plants marked for deletion in S/4 HANA as expired in GTS
The company codes and plants which are marked for deletion in S/4 shall start with naming convention D*.
Since its a soft deletion, the corresponding company codes and plants shall be expired in GTS.
The program shall be available to run as a background/ batch job
The program shall be available to run in simulation mode, and it should output the list of Business Partners that will be created in GTS based on the selection criteria
The program shall invalidate the Business Partner based on the status of the plant and company code
Proposed Technology to Use
Application job in GTS that reads the change object class for plant - BETRIEB and it creates the BP or updates the BP in GTS for legal units (table T001).
Data Source Considerations
Following are the data source for company code - FTO
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
| T001 | BUKRS | This would be created as the BP name in GTS with a prefix FTO_( to be confirmed by Dean on the naming convention) E.g. If company code is XXXX in T001-BUKRS, in GTS it will be created as FTO_XXXX. |
| ADRC | All fields | Structure is same in S/4 and GTS. So whichever value is populated , it can be moved to GTS. |
Following are the data source for Plant - LU
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
| T001W | WERKS | This would be created as the BP name in GTS with a prefix LU_(to be confirmed by Dean on the naming convention) E.g. If plant is YYYY in T001W-WERKS, in GTS it will be created as LU_YYYY. |
| ADRC | All fields | Structure is same in S/4 and GTS. So whichever value is populated , it can be moved to GTS. |
Data Validation Considerations
Only one to one mapping should exist between company code from feeder and FTO in GTS.
Custom Tables
N/A
Master Data
No Master data required
Configuration Table
N/A
Selection Screen Enhancement
Following are the selection screen elements for the program:
| Field Name | Description | Select: Option or Parameter Check box or Radio button Import or Export | Data Type/Length | Default Value/ Validation rule/ Value Help | Selection Logic |
|---|---|---|---|---|---|
| BUKRS | Company Code | Option | CHAR 4 | This can be blank. When it is blank all the company codes will be selected | |
| WERKS | Plant | Option | CHAR 4 | This can be blank. When it is blank all the plants will be selected | |
| Simulation | Checkbox | To run the program in simulation mode |
Processing Logic
On scheduling the application job for company code transfer , the program should validate the entries are company codes. Error should be shown if the details entered in selection screen are not valid company codes.
And then fetch the relevant company code details from feeder. All the address details including Name , Street/House number, Postal Code/City, Country, Time zone etc.
And in GTS system , corresponding to this company code, BP master data should be created and available in transaction BP with all the fields populated.
Three roles are to be created for the FTO(Foreign Trade Organization ) in GTS - 000000 Business Partner (General), SLLFTO(Foreign Trade Org) and FS0000(Financial Services BP).
Similarly on scheduling the application job for transfer of plants, program should validate the entries are plants. Error should be shown if the details entered in selection screen are not valid plants.
And then fetch the relevant plant details from feeder including Name , Street/House number, Postal Code/City, Country, Time zone etc.
And in GTS system , corresponding to this plant, BP master data should be created and available in transaction BP with all the fields populated.
Three roles are to be created for the Legal Unit(LU) in GTS -000000 Business Partner (General), SLLSIT(Legal Unit) and FS0000(Financial Services BP).
For company codes and plants marked for deletion in S/4 HANA , that will be expired in GTS system. Every company code and plant will have an entry in table /SAPSLL/PNTBP. Valid- to date of this table should be updated with the date when the deletion flag is set up in S/4 HANA.
There should be option to run this program in simulation mode and check the details.
A log should be generated with the details of transfer and also record any errors during transfer.
Volumetrics
Provide volumetrics details: Initial load volumes, Number of Records, Expected Frequency, Expected Long term Growth)
This program should be run as part of cutover task to have all the company code and plants to be created in GTS same as the feeder system S/4. Also after go-live , if any new company codes/plants are created/changed, it should be possible to transfer them as well.
Performance Considerations
Specify if there are any specific performance factors that need to be taken into consideration during development i.e. enhancement must be able to be executed by 10 users at the same time, etc.
As part of Syensqo, we have a list of company codes and plants. So the program should be able to handle this transfer.
Error Handling
Any failures in the report must be logged for further review.
Testing
How to Test
Run the application job and validate in GTS system , the corresponding org units are created.
Test Conditions and Expected Results
| ID | Condition | Expected Result |
|---|---|---|
| 1 | Replicate a company code XXXX transfer via the application job | FTO_XXXX created in GTS with 3 different roles - BP General(0000000), SLLFTO, FS00000 |
| 2 | Replicate a plant YYYY transfer via the application job | LU_YYYY created in GTS with 3 different roles-BP General(0000000), SLLSIT, FS00000 |
| 3 | Negative case- Invalid company code entered in selection and try to schedule the application job | Error showing incorrect company code entered |
| 4 | Negative case- Invalid plant entered in selection and try to schedule the application job | Error showing incorrect plants. |
Test Considerations/Dependencies
For this report to work, company codes and plants are to be available in S/4 HANA.
Other Information
Development Details
Package
| Package Name | Parent Package |
|---|---|
Enhancement Implementation
| Enhancement Type | Standard Definition Name | Custom Implementation Name | Design Rationale Reference |
|---|---|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|
Appendix
Custom Authorization Group Naming Convention
This table is based on the Syensqo development standards document. It provides the naming conventions for authorization groups to associated with custom reports and tables to comply with security requirements.
ABAP | ZFI | ZMM | ZPS | ZCO | ZSD | ZBC | ZFI | ZCA |
|---|---|---|---|---|---|---|---|---|
| TABLES | ZFIT | ZMMT | ZPST | ZCOT | ZSDT | ZBCT | ZFIT | ZCAT |
See also
Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.
