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

 In SAP GTS, an Intrastat Inbound flow involves capturing data from an IBD or GR in an ERP system and transferring it to GTS for Intrastat Declaration processing.

There are cases when for indirect materials coming from Ariba Guided Buying, goods without material master data such as: laptop, supplies or even services to be having missing classification and free text mentioned on the PO. At the time of the PO creation in S/4 and send it to GTS, the information received will be incomplete; the Intrastat Specialist User will require additional data on the declaration in GTS in order to make a better idea of the item used; for this the Intrastat Inbound Declaration will have to be enhanced with other data coming from S/4 like: Vendor and Material Group description (PO source).

Detail the functional scope and objectives of the Enhancements. Please also describe the gap that will be addressed by this enhancement (Compared to SAP Standard)

Insert the flowchart and fill in the steps

Assumptions

1. SAP GTS & S/4HANA interface connection available.
2. SAP GTS configuration settings performed.

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

N/A

Indicate any dependencies or constraints that may impact this development, in terms of requirements from internal or external applications, other work streams, time constraints, data or system access restrictions. Also, please specify scheduling or process dependencies, e.g. interface/batch job that must run beforehand or process steps that need to be completed prior to executing this development.

Security, Integrity and Controls

N/A

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

In GTS:

1. Create Business Partner with BP Role as: SLLFTO, SLLPOI, General and Financial Services.
2. Create Provider of Information for the respective BP.
3. Define the necessary Business Transaction types.
4. Activate Legal Regulation
5. Define Partner Countries
6. Assign Partner Countries to Countries of Declaration
7. Define Country of Origin
8. Assign Country of Origin to Countries of Declaration
9. Define Movement Codes
10. Define Modes of Transport at the Border
11. Define Incoterms

In S/4: ensure Intrastat-relevant data is maintained such as: commodity codes, country of origin and vendor/material master data.

Specify the configuration requirements for this object. Like in case of substitution/ routine specify the configuration needed

Language Requirements

EN only.

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

Special Requirements

N/A

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

For Intrastat Inbound flows, the POs from S/4HANA will trigger the creation of the declaration in GTS. For cases when POs are missing its master data (free text only), or when classification missing, it required to enhance the declaration in GTS with other data in order to provide a better clarity on the item used.

Therefore, following data must be added to the standard Fiori App “Manage Intrastat Declarations” ,under Additional data Tab for those whose length is 20 and 40.

• Material group description → assign it to CHAR 40

• Supplier name → assign it to CHAR 40

• Supplier number → assign it to CHAR 20

Detail the functional requirements that are desired to be achieved by the Enhancement compared to current functionality

Proposed Technology to Use

BADI /SAPSLL/INTRASTAT_SELECTION in SAP S/4HANA.

The fields on a PO transactional level can be found as:

EKPO-MATKL for material group (description)

EKPO-LIFNR for Supplier (number and description)

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

N/A

Include an overview of the source

Data Validation Considerations

N/A

Include an overview of the data validation requirement

Custom Tables

N/A

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

Master Data

N/A

<Title Custom Table 1>

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

Configuration Table

N/A

Title Configuration Table 1

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

Selection Screen Enhancement

N/A

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

BADI /SAPSLL/INTRASTAT_SELECTION

Method CHANGE_DATA use parameter CT_DECL_ITEMS_FS

Within component types: /SAPSLL/ADDF1, /SAPSLL/ADDF2/, /SAPSLL/ADDF3 link it to the below EKPO technical fields and send it to GTS within ADDA1, ADDA2, ADDA3 fields. Ensure the length is matching between S/4 - GTS additional data fields (20, 40 CHAR).

• EKPO-MATKL for material group (description)
• EKPO-LIFNR for Supplier (number and description)

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

N/A

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

Performance Considerations

N/A

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

N/A

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

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