High- Level Specification

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 created manually in SAP GTS. Due to the huge volume of these organizational elements in Syensqo, creation of FTO and LU 

business partner data is to be automated. Mapping of company code is 1: 1 and mapping of plants is also 1: 1. For every company code in feeder, only one FTO will be created in GTS. Similarly for every plant in feeder, only one legal unit will be created.

Insert the flowchart and fill in the steps

Assumptions

1. Company code must be available in S/4 HANA Feeder system.
2. Plants must be available in S/4 HANA system.
3. SAP GTS system should be available during transfer. 
4. 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 and storage locations. 

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.

To detail the security requirements for processing this enhancement, any data integrity issues associated with the object and the teams that will be responsible for processing the object, i.e. authorization/roles required to who can execute the enhancements, etc.

- Custom Tables, enhancement, transaction codes, programs, Web Dynpro Application, Code Data Services (CDS), Open Data Protocol (OData), BI reports, and Functional Modules need to have at least one authority check either standard or custom. (custom should be an exception)

- All custom tables will be maintained in a certain Authorization Group (example: ZFIN, etc.)

- In the case of transaction codes an additional check other than the object S_TCODE is required. You can use SU24 to find the related authorization objects to check.

All other WRICEFs

- If the authorization check is already performed in the calling Programs, this section can be filled as “Follow calling programs authorization check” (example : BADI to redirect DMS to OpenText, in which the calling Manage Purchase requisition Fiori App already performed authorization check)

- If the authorization check is not checked in any of the development, this section should be filled with the proposed authorization check. You can refer to SU24 to see the standard authorization objects. (example: full custom Fiori App to enable user to download/upload the project plan)

Configuration Requirements

RFC connection should be established between the S/4 HANA and GTS E4H system. 

Language Requirements

Specify the language requirements for this object. Specify the required language and type of translation, like labels, data.

Special Requirements

Specify any special requirements or considerations that may impact the enhancement based on specific locations, regulatory compliance or system limitations. Clearly outline requirements e.g. localization rules for countries like China

If the enhancement interacts with third-party systems such as Icertis, describe any additional integration, security or authentication considerations that must be taken into account.

Design Rationale

Functional Requirements

Existing process of creating the organizational elements FTO and LU is manual. In BP transaction , FTO and LU will be created one by one by referring to the data from the S/4 feeder. 

Going forward, as part of this enhancement execution, company codes and plants will be replicated as business partners in GTS. For FTOs, the naming convention will be FTO_XXXX where XXXX will be the company code from S/4 feeder. For LUs, the naming convention will be LU_XXXX where XXXX is the plant from S/4 feeder. 

For FTO, it should be created in 3 different BP roles -000000 Business Partner (General), SLLFTO(Foreign Trade Org) and FS0000(Financial Services BP).

For LU, it should be created in 3 different BP roles- 000000 Business Partner (General), SLLSIT(Legal Unit) and FS0000(Financial Services BP).

The BP fields which are usually populated for FTO and LU are : Name, Street/House number, Postal Code/City, Country, Region, Timezone. Communication details if available in feeder can also be copied including email, telephone etc.

Proposed Technology to Use

Typically, an enhancement will be based on an existing SAP BADI / user exit. If this is the case, please provide the proposed details of the BADI / user exit.

Data Source Considerations

Include an overview of the source

Data Validation Considerations

Only one to one mapping should exist between company code from feeder and FTO in GTS.

Similary one to one mapping for plants and legal units from feeder to GTS.

Include an overview of the data validation requirement

Custom Tables

If any custom configuration tables are required, which will be read by the enhancement logic, then specify them here.

Master Data

<Title Custom Table 1>

<Include an overview of the table and what it’s used for>

Configuration Table

Title Configuration Table 1

Include an overview of the table and what it’s used for

Selection Screen Enhancement

This section will give the details on the selection screen parameters, parameter type and whether it’s obligatory or not. This section can be used to define the Import Export parameters for Function Module or User Exit or Screens.

Processing Logic

This section defines the detailed step-by-step logic implemented within the BAdI/User Exit to process the data received from the standard SAP program and database retrieval. It explains the operations performed on the data, the expected outcomes in different scenarios and how the system should behave in response to specific conditions.

Volumetrics

Provide volumetrics details: Initial load volumes, Number of Records, Expected Frequency, Expected Long term Growth)

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.

Error Handling

Any failures in the job 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

Test Considerations/Dependencies

List any considerations essential for application test planning (e.g., test this before ABC along with DEF separate from GHI). If the development encompasses a user interface, explain how to test it. List any insights as to how this component could be tested the most efficiently.

Other Information

Development Details

Package

Enhancement Implementation

Other Development Objects

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.

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.

Change log