Specific system configurations are often needed to upload control class codes or classify products. The system configuration in SAP GTS revolves around establishing numbering schemes.
Numbering schemes define the behavior of classification numbers. Numbering schemes are used for all classification-related master data: control class codes, commodity codes, tariff code numbers, PGA/OGA codes, and excise duty codes.
The configuration for these numbering schemes can be found in the SAP Global Trade Services, edition for SAP HANA node under the Implementation Guide (IMG). The essential transactions for this setup are located under General Settings > Numbering Schemes.
The setup process involves two main steps: setting up a numbering scheme and assigning numbering scheme content. Afterward, the numbering scheme needs to be assigned to the related legal regulations. This last assignment is merged into a single step for all numbering schemes, simplifying the configuration.
Considering that most numbering schemes, aside from a few subsettings, follow a similar definition pattern, examples will be provided using tariff code numbers and PGA codes, which typically present the most complexity during setup. Let’s dive into the configuration activities:
In this customization task, measure systems are defined, and units of measure (UoMs) are assigned to them. The system validates UoMs entered in the application and during tariff number uploads by using the units from the designated UoM system. Note that a UoM system can be used across multiple numbering scheme contents.
In this customization task, a numbering scheme for tariff numbers is established through defined steps. The process commences by providing a name and description for the numbering scheme, followed by specifying the required length of the classification numbers within the scheme (the length of a classification code can vary based on country-specific regulations). Additional settings are available to determine if the numbering scheme supports end use. Furthermore, there is an option to select a reference scheme if the need arises to cascade the classified number between different numbering schemes.
In this customization task, the primary objective is to define the structure of the tariff numbers for customs processing. The following settings need to be made:
In this customization task, the objective is to enable and activate the designated numbering scheme content. The process involves selecting the relevant numbering scheme and entering the applicable validity period and associated numbering scheme content.
In this customization process, the objective is to link numbering schemes to their corresponding legal regulations within specific application domains, such as legal control, import and export processing, excise duty monitoring, and so on.
The next figure shows that the standard settings in the Customizing already encompass predefined numbering schemes and their respective assignments to legal regulations across different application areas.
In this customization task, the objective is to define a number set within the IMG. Number sets play a role in simplifying the product classification process across both country and application levels. This feature allows for the use of a predefined number set in Customizing, which can be further refined during master data maintenance. Consequently, it enables the classification of a product across multiple countries and functionalities simultaneously, such as Compliance Management and Customs Management.
To initiate this task, ensure the numbering schemes for customs code numbers (e.g., Harmonized Tariff Schedule [HTS] numbers, commodity codes) have been previously maintained. These customs code numbers should already be present either through manual input or upload. Define the number set by providing a distinct name and a detailed description. Then, associate all the relevant numbering schemes that should be part of this number set.
Select a reference scheme, which serves as the definitive numbering scheme used to determine the number set during classification. A number set can only have one reference scheme.
The PGA functionality needs to be activated per numbering scheme. The agency and program-specific format definition of records and fields isn’t available out of the box but must be maintained by PGA experts.
A PGA is a governmental entity collaborating with CBP to regulate commodities being imported or exported into the US. SAP GTS offers a tailored solution to meet the specific requirements set forth by PGAs. To configure the system, the PGA functionality must be activated for the required numbering scheme.
The precise format definition for records and fields specific to agencies and programs isn’t readily available as a standard configuration. This level of customization requires expertise from PGA specialists, who are responsible for maintaining and defining these essential formats. These necessary customizations can be accessed via the IMG path SAP Global Trade Services, edition for SAP HANA > General Settings > Partner Government Agencies (PGA). The configuration activities are as follows:
The initial step involves defining the agencies and their respective programs. An illustrative example of such an agency is the FDA, accompanied by programs like Biologics (BIO), Cosmetics (COS), and others.
The next step entails defining and assigning relevance codes to the relevant programs. This allows the system to associate the PGA relevance codes, which are assigned once a product is classified, to the correct program codes.
The third step involves defining the structures, that is, PGA records, for the respective agency programs. This process involves specifying which records are necessary for each program. Numerous PGA records exist, and every agency defines which records are required, or optional, to satisfy the requirements when filing PGA information.
After assigning the structures to the relevant programs, the fields per structure are assigned, as shown in the final figure. All fields are provided by SAP; however, it’s up to the PGA expert to identify per agency and its respective program which fields are mandatory, conditional, or optional.
To conclude the setup, the permissible values for each field corresponding to the PGA must be defined. The agencies set out strict rules in how the data should be maintained in the records. For some data fields, only predefined values are allowed. As an example, the FDA only allows codes “A” and “F” to be filed as disclaim codes—any other code would be inadmissible while maintaining the field in the product master data.
Editor’s note: This post has been adapted from a section of the book Implementing SAP Global Trade Services by Nick Moris, Pablo LeCour, and Li Yu.