High- Level Specification

Functional Overview

The functional design of the enhancements describes the scenario(s) where enhancements to existing SAP programs are required.

Scope and Objectives

1. Organizational Context: GBUs and Legal Entities

Syensqo operates through several Global Business Units (GBUs). Each GBU has its own sales processes and revenue recognition procedure and serves as a commercial representation of the Syensqo organization.

These GBUs are active across multiple countries, which requires the use of legal entities (Company Codes) to manage local operations and ensure regulatory compliance - this represents the operational view of Syensco. 

• In some cases, a legal entity is dedicated to a single GBU.
• In other cases, one legal entity may serve multiple GBUs, resulting in a shared use of financial systems and transactional data across different units.

2. Current Situation in GTS 

In the current Global Trade Services (GTS) system, product- level segregation by GBU is missing, with the exception of Composite Materials (CM). This lack of segmentation makes it difficult to: 

• Identify the responsible business contact for classification questions
• Process license requests accurately
• Link the right Customer Service Representative (CSR) to specific products in compliance scenarios

3. Objective

The goal is to extend GBU identification to all product types in the new GTS e4H system, not just Composite Materials

To support this, the system must be enhanced to assign a GBU tag to each product during material replication from S/4HANA to GTS. 

4. Proposed Solution and Logic

A new logic will be introduced to ensure proper GBU tagging: 

• When a product is extended to a plant in S/4HANA, it will be replicated to GTS.
• At the time of replication, the product will be tagged with its corresponding GBU.
• This tag will be stored as an Additional Characteristic in the GTS Product Master to allow for GBU-level filtering and reporting.
• The GBU value will be derived from the Profit Center assigned in the Material Master in S/4HANA.

5. Business Benefits of GBU Segregation

Introducing the GBU field in GTS will: 

• Help Customer Service and Compliance teams find the correct point of contact for product classification or supplier-related questions. 
• Support license management, where identifying the GBU responsible is often required.

Process Flow Diagram

Assumptions

Describe any assumptions that have been made in the process of completing this design. What functionality is expected of configuration or other developments that pass information to this development and/ or retrieve the information processed by it (performance, triggers, exceptions, etc.)

Dependencies

None.

Security, Integrity and Controls

Change access is granted to GTS users to create, maintain and display entries in the GBU custom table. All other users are restricted to display-only access for monitoring and validation purposes. 

Configuration Requirements

Based on this enhancement, the following configuration path must be completed in GTS.

Global Trade Services IMG →  General Settings → Customs Products:

1) Define Product Characteristics from the feeder system →  define the attribute technical name.

2) Assign Field attributes to the product characteristics from the feeder system → assign field length to the attributes defined at step 1.

3) Define Attributes of Product Characteristics with Length 01 → define possible values for the attribute.

Below is the list of relevant tables for this functionality:

• /SAPSLL/PRGEN - Product attributes in GTS
• /SAPSLL/TCOATR - Definition of characteristics from feeder system
• /SAPSLL/TCOATC - Generic settings for general attributes maintenance
• /SAPSLL/TCOATA - Control of general attribute maintenance - assignment of attributes

Language Requirements

N/A

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

Current functionality: The Composites Business has export controlled products under EAR and ITAR Regulations, and Composition data is considered export controlled technology. The Composition data of ITAR and Certain EAR items must be secured and limited to only US citizens. For that reason, the SBS-CCT-CTC organization in the US will manage the HTS classification for Composites in all countries. At the moment, the SBS-CCT-CTC Team is located in Lisbon supporting all other GBU’s by managing the HTS Classification in GTS for all countries. The Composites structure creates the requirement to segregate the products to be classified by Lisbon from the products to be classified by the US Team. 

To-be functionality: Sends GBU(Profit Center) for all material types across all S/4HANA systems available based on logical system and plants maintained. Use table material/plant combination on S/4HANA side and send the profit center/GBU via standard user exit of the GTS S/4HANA plugin. Simple data mapping needed to update master data in GTS client.

Proposed Technology to Use

S4 user exit: EXIT_SAPLSLL_LEG_PRR3_004

Data Source Considerations

N/A

Data Validation Considerations

Custom Tables

Master Data

Configuration Table

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.

1 GBU =1 Profit Center. 

Reference table = MARC -PRCTR

Following is the logic to Derive GBU from Profit center

• Get the First letter of the profit center
• Based on the first letter, assign the below - Note that this will have to be a config table so that the description can be changed
  • S=SPEC. POLYMERS 
  • C=COMPOSITE MATERIALS 
  • N=NOVECARE 
  • T=TECHNOLOGY SOLUTIONS 
  • B=CBS

Scenarios:

1. If 1:1 material/plant → sends '1' GBU available to GTS by fetching it from MARC-PRCTR and coding it under User Exit: EXIT_SAPLSLL_LEG_PRR3_004
2. If 1:n material/plant → sends 'n' GBU available to GTS by fetching it from MARC-PRCTR and coding it under User Exit: EXIT_SAPLSLL_LEG_PRR3_004. Note: For this scenario, when multiple plants are assigned to same material and if several GBUs are maintained for the different plants, then Business Global Unit should be separated by a “,” when shown in GTS under Additional Characteristics, for e.g: ABC, CDE, EFG.

Prerequisites: configuration steps in GTS are to be done as per described on Configuration Requirements chapter.

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

Detail how errors will be handled: Notification, Restart/ Recovery and Re-Processing Procedures

Testing

How to Test

Please provide some guidance and/or test data to help the developer unit test the enhancement. Please include both positive and negative testing (to validate error situations handling). The developer will need to test repeatedly, so where appropriate provide instructions to reverse the actions performed so the test may be run again or explain how to create new input data to the test. The developer will need logons for test users representing the various roles within the approval process.

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

In case of a change in the GBU/Profit Center value of the Product inside master data, this change will reflect to GTS, only if a dedicated user will collect all impact products and send them via GTS area menu in an S/4HANA system, as /SAPSLL/MENU_LEGALR3.

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