Introducing International Trade Management With SAP S4HANA
Introducing International Trade Management With SAP S4HANA
Introducing International Trade Management With SAP S4HANA
Introducing International
Trade Management with
SAP S/4HANA®
Arup Chakraborty
Arup Chakraborty
Introducing International
Trade Management with
SAP S/4HANA ®
Marie-Luise Wagener
Introducing Governance, Risk, and Compliance (GRC) in SAP S/4HANA
www.sap-press.com/4682 | $29.99 | 132 pages
Ashish Mohapatra
Introducing Credit Management with SAP S/4HANA
www.sap-press.com/4990 | $24.99 | 88 pages
by force. During the early 20th century, world leaders and economists real-
ized that the progress of society and humankind at large can be better
achieved via free trade between nations. This realization led to the need of a
new set of rules and an international organization to monitor and ensure
implementation of such rules and laws by participating nations. The World
Trade Organization (WTO) located in Geneva, Switzerland, was established
on January 1, 1995, based on multiple rounds of negotiations between partic-
ipating countries.
Regulatory Changes
The laws and regulations governing international trade can be categorized
in three groups:
쐍 Supranational groups
Supranational groups are international bodies comprising many mem-
ber nations that create and prescribe standards by taking into consider-
ation all the concerns and interests of the member nations. The WTO and
the International Monetary Fund (IMF) are a couple of examples of supra-
national organizations.
쐍 Free trade agreements
A free trade area is created based on free trade agreements mostly on a
regional basis or between a few participating countries as a group. The
purpose of such a free trade area is to facilitate trading between the par-
ticipating nations. The North American Free Trade Agreement (NAFTA),
which includes Canada, Mexico, and the United States, and the Associa-
tion of Southeast Asian Nations (ASEAN)—which consists of Brunei
Other examples include the U.S. exiting from the Iran deal and imposing
stringent sanctions against Iran and very recently the Indian government’s
withdrawing of its unilateral most favored nation (MFN) status given to
Pakistan. The ongoing process of Britain exiting from the European Union
(EU), also known as Brexit, will have a big impact on the trade regulations
between EU countries and Britain.
electronic invoice for all parties involved in international trade across the
EU, including Iceland, Liechtenstein, and Norway.
Figure 1.1 shows the screen for the General Foreign Trade Processing cockpit
(Transaction VX99) in the SAP ERP system. There are similar cockpits for
periodic declaration, legal control, document payments, communication and
print, preference service, and data service.
Figure 1.2 shows the SAP GTS area menu (Transaction /SAPSLL/MENU_
LEGAL).
쐍 Compliance Management
The Compliance Management service module provides all the necessary
functionality related to product classification based on export or import
control classification numbers. It maintains data related to a denied party
list, which is used for scanning business transactions such as sales orders,
deliveries, purchase orders, and financial documents for business part-
ners to ensure that the transaction is valid and does not involve any
blacklisted partners. The system enables automating the solution based
on interfacing with data service providers to import the denied party list
and update the SAP GTS master data with the latest information. The
sanctioned party list screening, audit trail, and embargo checks in SAP
GTS are much better solutions compared with the SD-FT component’s
functionality available in SAP ERP. This module covers checks for licens-
ing requirements for both export and import transactions. In addition,
this module of SAP GTS also supports country- or country group-specific
embargo checks.
쐍 Customs Management
The Customs Management service module enables handling master data
relevant for customs management. It provides solutions for maintaining
tariff codes, product classification, and reclassification based on valid tar-
iff codes. It allows you to execute and carry out customs declarations
(both export and import) electronically. SAP GTS can be connected to cus-
toms systems via certified middleware. It also provides standard PDF
templates for various customs-related documents (for example, export
accompanying document, shipper’s letter of instructions, and so on). The
customs bonded warehouse solution covers the monitoring of inventory
in the warehouse via integration with SAP ERP or a warehouse system.
This module also enables you to do special customs transit processes and
handle products subjected to excise duties. These are some of the
advanced features that are not covered by the SD-FT component’s func-
tionality in core SAP ERP.
쐍 Risk Management
The Risk Management module covers the preferential processing, restitu-
tion management, and letter-of-credit processing. You can maintain and
execute in SAP GTS all relevant master data and calculation methods for
determining preferential status of the product. Restitution management
supports the EU’s policy to support the farming and agriculture industry
in Europe, which is known as the Common Agricultural Policy (CAP).
Under this policy, the farmers exporting surplus agricultural goods to
countries outside the EU receive tax refunds. This module also provides
complete support for financial payment documents and functionality for
monitoring and handling of letter of credit.
쐍 Electronic Compliance Reporting
The Electronic Compliance Reporting module mainly supports the intra-
stat reporting requirement. This is relevant for all countries in the EU.
쐍 System Administration
The System Administration module covers the technical setup of system
interfaces (communications) and monitoring. In addition, this module
covers the data archiving solution related to various objects used in SAP
GTS.
Figure 1.3 shows a typical user home page based on the SAP Fiori user expe-
rience. You can see some of the common apps related to SAP S/4HANA for
international trade.
The new features related to SAP S/4HANA for international trade are part of
SAP’s governance, risk, and compliance solutions. Under the old SAP GUI
user interface, the user menu contained only four transactions related to
intrastat reporting. The idea is to use the new SAP Fiori-based user interface,
and hence, instead of transaction codes, different SAP Fiori apps support
the required functionality for international trade.
SAP S/4HANA for international trade supports managing the customs tariff
codes and control classification numbers. It allows product classification
and reclassification functionality.
For organizations based in the EU, the system supports creating and send-
ing intrastat reports.
2 Product Classification
In general terms, product classification means grouping and organizing
products and services based on their specific features and attributes. The
product classification we discuss here is not related to classification of prod-
ucts and services from a marketing perspective; rather, it is related to trad-
ing of such products and services internationally.
Today, about 183 member countries follow this coding system. The first six-
digit HS codes have been adopted globally and a further two- or four-digit
numerical code is added based on the national classification that local
authorities prescribed.
The heading 8483 provides further details about the product, and the sub-
heading 8483.30 shows specific information about the product. An addi-
tional subheading (the last four digits) 8483.30.5020 is as per U.S. Schedule
B, which provides the detailed product description.
8483.30.5020
84 Chapter:
Nuclear reactors, boilers, machinery and mechanical appliances; parts thereof
8483 Heading:
Transmission shafts (including camshafts and crankshafts) and cranks;
bearing housings, housed bearings and plain shaft bearings; gears
International and gearing; ball or roller screws; gear boxes and other speed
(6 digits as per HS) changers, including torque converters; flywheels and pulleys,
including pulleyblocks; clutches and shaft couplings
(including universal joints); parts thereof
8483.30 Subheading:
Bearing housings; plain shaft bearings
The heading 8501 further describes the product, and the subheading 850110
provides specific information about the product. Another subheading (the
last two digits) 85011091 is as per CN8, which provides the detailed product
description of the product.
85011091
85 Chapter:
Electrical machinery and equipment and parts thereof; sound recorders and
reproducers; television image and sound recorders and reproducers; and
International parts and accessories of such articles
(6 digits as per HS) 8501 Heading:
Electric motors and generators (excl. generating sets)
850110 Subheading:
Motors of an output <= 37,5 W …
European Union 85011091 Subheading:
(2 digits as per CN8) Universal AC-DC motors of an output <= 37,5 W …
Because only the first six digits of the codes are based on the globally
accepted HS code system and then there are an additional two or four digits
that are based on a national (country-specific) classification system, the
classification codes need to be managed on the country level.
Now, let’s see how the commodity code (or tariff codes) are managed in an
SAP S/4HANA system.
There are two SAP Fiori apps for managing commodity codes and tariff
codes:
Figure 2.3 shows the Manage Customs Tariff Numbers screen. The code
8483305020 with a description and a validity period exists in the system.
You can select the row and edit (click the pencil icon) or delete (click the
delete icon) the record. You can carry out a mass update based on this app.
To add a new code, click the Add (+) icon, enter the required code, and save
the record.
Based on the system configuration, the length of the code can be fixed. For
example, say a tariff code length is defined as 10 digits. As a result, the sys-
tem will display an error message, as shown in Figure 2.4, if a code with
incorrect length (more than or less than 10 digits) is entered. After you
enter the code with the correct length, the system allows you to save the
record.
The Manage Commodity Codes app is similar to the Manage Customs Tariff
Numbers app. However, for commodity codes (CN8), the length is set as eight
digits. Figure 2.5 shows the overview screen of Manage Commodity Codes.
You can select all commodity codes and click the change icon (the pencil) to
carry out changes/updates for multiple codes from the list.
As shown in Figure 2.6, in the Edit Commodity Codes screen, the Valid To date
is changed for the selected list of CN8 codes.
Besides managing the commodity codes via the Manage Commodity Codes
or Manage Customs Tariff Numbers apps, you can also define and maintain
number schemes in the SAP S/4HANA system based on an external data pro-
vider or to get codes transferred from a connected SAP GTS system. This is
based on the definition of the number scheme customization in the system.
nine categories of products and technologies that are put under control,
and furthermore, there are two separate lists for sensitive and very sensi-
tive products and technologies.
6A005
6 Category
Sensors and lasers
A Group
Systems, equipment, and components
6A005
“Lasers,” “components,” and optical
equipment, excluding items that are
subject to the export licensing
authority of the Nuclear
Regulatory Commission
The WA and U.S. CCL provide guidelines on the restrictions and controls for
products based on the classification. For example, the U.S. CCL provides
detailed information per control classification on the restrictions based on
parameters such as partner(s), partner countries, quantity, and/or value of
such control goods.
Note that codes can contain more detail than shown in this example.
Now, let’s see how to manage the control classes in SAP S/4HANA. There are
two SAP Fiori apps that can be used for managing control class data:
Figure 2.8 shows the overview screen of the Manage Control Classes app. The
system allows you to edit multiple control classes by selecting relevant
rows. To create a new control class number, click the + icon. In the example,
you can see that the control class is as per the U.S. Export Control Class
(USECC) number scheme defined in the system. This number is based on
the U.S. Control Classification List.
Figure 2.9 shows the overview screen of the Manage Control Groupings app.
This app allows the possibility of creating new control groups and editing
multiple control groups by selecting relevant rows. To create a new control
group, click the + icon.
Next, we’ll explain how the commodity code and control class numbers are
used to classify products in the system.
There are six main SAP Fiori apps for product classification and reclassifica-
tion:
Figure 2.10 shows the overview screen of the Classify Products – Commodity
Codes app. With this app, you can select multiple products and carry out
mass classification. In the example, number scheme CN8 representing EU
combined nomenclature is used for classification of the products 25 Win-
dow frame and 34 Door frame. After you click the Classify button, the system
will take you to the screen wherein the relevant CN8 code can be assigned to
the products. You can search for products based on description. In this
example, based on searching for “frame,” the system has identified the
products 25 and 34.
Figure 2.11 shows the mass classification screen wherein the two products
are classified with the CN8 code 44011100 and saved.
Now, let’s move on to product reclassification. Figure 2.12 shows the over-
view screen of the Reclassify Products – Commodity Codes app. Just as you
did for classification, you can carry out mass reclassification of products
here.
Figure 2.12 The Reclassify Products – Commodity Codes SAP Fiori App
Similarly, you can carry out product classification and reclassification for
tariff codes using the relevant apps for tariff codes. For legal control, you can
flag the products as relevant for legal control or not using the Classify Prod-
ucts – Legal Control or Reclassify Products – Legal Control apps. The actual
assignment of the control classification numbers to the products are main-
tained via Business Rule Framework plus (Transaction BRF+). The Business
Rule Framework plus provides business users with more flexibility in man-
aging business rules and decision tables without depending on technical
developers to build custom code in the system. This provides an application
programming interface (API) and user interface for defining and processing
business rules.
3 Trade Compliance
An important aspect of international trade is to ensure required legal regu-
lations are adhered to while exporting or importing goods across interna-
tional borders.
In the following sections, we explain how various trade licenses can be man-
aged based on SAP S/4HANA for international trade. We also explain briefly
how cross border transactions are monitored for licensing requirements
and how automated checks are carried out to ensure the transactions meet
legal requirements.
쐍 The purpose and end use of the product or technology by the consignee
or purchaser.
The Manage Licenses SAP Fiori app (F2545) is used for managing licenses for
trade compliance.
Figure 3.1 shows the Manage Licenses app overview screen. It provides vari-
ous selection fields to search for specific licenses. The Legal Regulation field
is mandatory, and in this example, the list of licenses displayed is based on
the EAR. The system allows you to create, change, and delete various
licenses. You can also set the status of a license as active or expired. The sys-
tem will block a transaction if the valid license is not in active status.
Now, we’ll show you how to create a new license for license type Shipments
to Country Group B Countries (GBS). Click the Create button to open the Cre-
ate License pop-up box, as shown in Figure 3.2.
The License Owner field is for the legal entity (the company code in the SAP
system), and the Legal Regulation field is for information about the organi-
zation under which the license is issued—in this case it is EAR, and for this
example, the License Type field is GBS. Click the OK button to add further
details.
Now we’ll explain how different attributes relevant for a license can be
maintained in the system via the following sections:
쐍 General Information
In Figure 3.3, relevant Legal Regulation EAR, License Type GBS, and the cur-
rent Status A (License Created) are shown. This information indicates that
the legal entity (organization) has submitted a request to relevant author-
ities for a GBS license. The General Information section shows the Official
License No. field, which is filled once a valid license is received from the
authorities. In addition, the validity date of the license and the legal
owner (for example, company USA; company code 1100) are specified at
this level in the Valid To: and License Owner fields, respectively.
쐍 Control Classes
Figure 3.4 shows the Control Classes section. In this section, you can main-
tain relevant control classes by clicking the + icon. From the options in
the dropdown list, you can select and maintain relevant and multiple
control classes per license.
쐍 Partner Countries
Figure 3.5 shows the section for Partner Countries. In this section, you can
maintain a relevant destination country by clicking the + icon. From the
options in the dropdown list, you can select and maintain relevant and
multiple countries (ISO country codes) per license.
쐍 Attachments
In Figure 3.6, the Attachments section is shown. You can attach additional
documents or links to the specific licenses. You can scan and attach the
official approved license (hard copy) as a PDF to this license. Finally, you
can save this document as a draft or save and submit it.
Using the Manage Licenses app, you can monitor the list of existing licenses.
Figure 3.8 shows the list of licenses and their relevant statuses.
You can set the status of a license to active once approval (or a license) is
received from the relevant authorities. You can also set a license as expired
(if not extended) once it has passed its validity date (Valid-To date).
Note
The examples shown in this section are dummy data taken from a sandbox. We
recommend consulting the latest recommendations under relevant legal regu-
lations.
Figure 3.9 shows the Manage Documents – Trade Compliance app displaying
a list of international trade-related business transactions. The app lists both
released and blocked documents.
You can go in to the specific blocked transactions and either confirm the
block and close the transaction or assign a relevant and valid license and
release the transaction by carrying out a recheck.
Let’s look at one of the blocked documents in detail. Figure 3.10 shows that
the sales order item is blocked as per legal regulation EAR and that a deci-
sion is pending. On the right side, you can see that the reason for the block
is because the product is not classified (i.e., the control class is missing). You
can click the Edit Classification button, maintain the required value, and
save the document. Alternatively, you can confirm the block and stop the
transaction from further processing.
Now, let’s look at the Resolve Blocked Documents app. This app is similar
to Manage Documents – Trade Compliance, but it lists only international
business transactions that are blocked due to missing data or an invalid
license.
Figure 3.11 shows the Resolve Blocked Documents – Trade Compliance over-
view screen with a list of blocked documents. It shows that two orders—
1549 and 1548—are blocked and it has flagged that for the next action, there
are two days left. In this case, the next action due is related to delivery cre-
ation (earliest delivery date).
Figure 3.11 Resolve Blocked Documents – Trade Compliance SAP Fiori App
Before recheck, let’s look at the details of the blocked document. As shown
in Figure 3.12, the item is missing classification (i.e., the product is not clas-
sified with a relevant ECCN); therefore, the system has blocked the transac-
tion.
Now, we’ll explain how to maintain the relevant ECCN for the product and
save instead of confirming the block. From the dropdown list, ECCN EAR99
is selected and maintained for this product and relevant for this transac-
tion, as shown in Figure 3.13.
Go back to the initial screen that shows the list of blocked documents. As
shown in Figure 3.14, the sales order 1548 appears blocked. Because the
required product classification is maintained for this transaction, you can
carry out a recheck by clicking the Recheck button.
In Figure 3.15, you can see that the order 1548 item is still blocked and now it
is because the system has not been able to find a relevant export license for
the product with ECCN EAR99 and destination country PK (Pakistan). From
the dropdown list, you can select and attach a license (for example, EU-
Statement [end-user statement] license is assigned to the transaction), and
save. After you save the transaction document, the system will carry out a
recheck of the transaction and release the document as it is assigned to
valid license now. The transaction will no longer appear in the Resolved
Blocked Documents – Trade Compliance app.
Now you verify that order 1548 in the Manage Document app is released.
Figure 3.16 indicates that the sales order status is released by user, and the
right side of the screen shows the ECCN assigned to the product and the
export license number EU-STATEMENT-9999-001 (the external license num-
ber) of license type CIV assigned to the transaction.
If the products are correctly classified and relevant licenses are maintained,
the system will then carry out a trade compliance check and automatically
assign the relevant license.
4 Embargo Checks
In general, embargo means an official ban imposed by a country or group
of countries or an international organization on trade with a specific coun-
try. The purpose of such bans is to ensure nations abide by the interna-
tional obligation in the areas of counterterrorism, prevention of prolifera-
tion of weapons of mass destruction, and protection of children in arm
conflicts.
The EU has a framework called Common Foreign and Security Policy (CFSP)
based on which EU country imposes trade bans on countries (for example,
on Iran and Syria).
Note
The aforementioned regulatory bodies and countries under embargo do not
make up an exhaustive list. It is recommended to refer the latest international
and national regulations related to such a list and the scope of the restrictions.
In Figure 4.1, you can see the various selection parameters, such as Legal
Regulation, Country, Valid From, Valid To, and so on. The Legal Regulation
field is mandatory; in our example, you enter EMBUN, short for embargo
country list based on the United Nations. Similarly, there could be other
legal regulations specifying a different set of embargo country lists. Once
you select the relevant legal regulation and click the Go button, the sys-
tem will display the list of countries with embargo blocks, as shown in
Figure 4.2.
Click the + icon to enter new entries in the list of embargo countries. After
you click the + icon, you can enter the country key that you want to main-
tain as the embargo country and click the Go button. Based on this entry,
you get the relevant country key listed under the Items table. Then, double-
click the country key listed under Items to add a new country to the em-
bargo list. Finally, click the Save button to save the entry in the list. Selecting
the checkbox on the left side against a specific country (row) enables the
options to edit and/or delete the entry from the list.
Figure 4.3 shows an example of creating embargo countries for the legal reg-
ulation EMBUN. There is a search option example based on ISO country key
or long name with which you can search and add the valid country code to
the list. In our example, North Korea is added to the list.
In Figure 4.4, you can see that Syria has been added to the list of embargo
countries under the EMBUN legal regulation.
Figure 4.4 Syria and North Korea Added to the Embargo Country List
Based on this list of embargo countries, the system will carry out automatic
embargo checks of sales and procurement transactions.
Sweden
Iran
India
The Manage Documents Trade Compliance (F2826) SAP Fiori app is used for
managing all such transactions that are blocked due to legal compliance
checks (including embargo checks).
Figure 4.6 shows the overview screen of the Manage Documents – Trade
Compliance app.
The top part of the screen has selection criteria (for example, Legal Regula-
tion, Company Code, Plant, and so on). In this example, two sales orders are
listed that have the status Blocked and need to be reviewed before they can
be further processed.
1 This section shows the overview of the total item, product, net value and
the status.
2 This section provides more information, including the legal regulation
based on which the item is blocked and the status Decision Pending.
3 This section shows which partner has an embargo situation—in this
case, it is the ship-to partner (the destination country), which is in Iran.
Figure 4.8 shows the pop-up box that appears after you click the Confirm
Block button. In this case, the reviewer has decided to not allow further pro-
cessing on the order. You can enter relevant comments and click the OK
button to save the decision. Similarly, a pop-up box appears to register com-
ments in case the reviewer would have decided to release the block.
Figure 4.9 shows the final decision Confirmed Block for the sales order item
based on the reviewer’s decision and comment.
In Figure 4.10, the detail screen of the app Resolved Blocked Documents –
Trade Compliance (F2792) is shown for a blocked sales order item due to the
embargo situation in Syria. You can also use this app (which we introduced
in Section 3.2) to manage and review blocked business transactions due to
compliance issues.
The examples discussed are based on sales orders; however, the functional-
ity is the same for customer delivery and purchase orders.
5 Intrastat Reporting
Intrastat stands for the intra-community statistics on trade of goods be-
tween countries belonging to the EU. As per the single market concept, the
internal border restriction between member countries was opened for free –
movement of goods, people, and services. Currently, 28 countries are part of
the EU and have this requirement of intrastat reporting.
The collection of the data takes place in different steps. First, the relevant
statistical data is collected on a national level by each EU member country,
and then the consolidated information is passed on to Eurostat, the statisti-
cal office of the EU. Eurostat then compiles and publishes the final report.
Today, the authorities also use the figures from the intrastat report with
value-added tax (VAT) reporting and EC Sales List (ESL) figures for any dis-
crepancy. Thus, it is important that the figures reported in intrastat match
the figures reported in an ESL report.
Note
The ESL is a financial report that economic operators (individuals/organiza-
tions) need to report the VAT on sales of goods and services to the EC. Tax
offices in the EU use the report to monitor and ensure that correct tax amounts
are paid by all relevant parties.
Although these laws are common across all of the EU member countries,
there are allowed provisions for some minor deviations based on local
country-specific requirements. In this section, we’ll cover the following
high-level requirements that are common across all the member countries:
Now, let’s look at the content or data elements to be included in the report.
Note
There are subtle differences between the mandatory contents of the report and
the format depending on the specific EU member country. We are not going to
cover all the individual country-specific versions, but touch upon the main con-
tent common across all the EU member countries.
쐍 Identification number
This number is the VAT registration number of the responsible person/
partner submitting the report. Such a person/partner is also known as a
provider of statistical information (PSI).
쐍 Period for which the report is submitted
All cross border transactions (goods movement) during a calendar month
is included in the report, and the relevant month number is also specified
in the report. The period is given in numeric number (for example, 01 for
January, 02 for February, and so on until 12 for December).
쐍 Direction of goods flow
Inbound or arrivals when goods arrive at an EU member country and out-
bound or dispatch when the goods leave the EU member country.
쐍 Commodity code identifying the product
This is based on product classification as per CN8 prescribed under Coun-
cil Regulation (EEC) no. 2658/87 on the tariff and statistical nomenclature
and on the Common Customs Tariff.
쐍 Country of dispatch/destination
The country of dispatch is determined based on the country of the con-
signor, and the country of destination represents the EU member coun-
try in which the goods arrive and change of goods ownership takes place.
쐍 Country of origin of the product
This information depends on the CN8 classification and based on the
general guidelines that state that the country of origin of a product is
the country where the product undergoes substantial and economically
쐍 Statistical procedures
This information is used to categorize transactions into a group with sim-
ilar characteristics. For example, categorization of a final dispatch of
goods versus a temporary dispatch of goods for processing under con-
tract (subcontract goods).
쐍 Quantity of the goods
This information needs to be declared based on net mass (excluding
packaging weight) or based on the supplementary unit of measure
depending on the product classification based on CN8 nomenclature.
Master Data
The first prerequisite, naturally, is to set up system configuration related to
the intrastat functionality, which is not in the scope of this E-Bite. Then, you
can proceed with setting up some key master data elements.
Provider of Information
One of the mandatory master data to set up is the provider of information.
This represents the organization (company) in the system. To maintain the
data, you can use the Manage Providers of Information SAP Fiori app, or
alternatively, you can use the SAP GUI Transaction /n/ECRS/POI_EDIT.
After you click the Manage Providers tile (app), the system opens a new page,
as shown in Figure 5.1, wherein a list of providers of information is dis-
played.
In Figure 5.2, you can see a typical example of Provider of Information master
data.
The Manage Intrastat Service Codes SAP Fiori app (F2517) is used to maintain
the valid service codes to be used for service product classification.
As shown in Figure 5.3, using the Manage Intrastat Service Codes app, you
can change, update, and display these service codes. You also can specify a
certain validity period for each of these service codes.
You can then use the service codes maintained for classifying service prod-
ucts using SAP Fiori apps.
There are also two SAP Fiori apps related to the classification of service
products based on intrastat service codes:
Figure 5.4 shows the screen for classification of a service product (CONSULT-
ING) based on a numbering scheme (ZINTRASTAT) via the Classify Products
Intrastat Service Codes app. After you click the Classify button, the system
takes you to the next screen wherein you can select the relevant intrastat
service code in the Intrastat Srvc. Code field and save the data.
Figure 5.4 Classify Products – Intrastat Service Codes SAP Fiori App
In Figure 5.5, you can see the service product CONSULTING is classified with
service code 620111, which is valid for a specified period. Similarly, you can
reclassify and update the intrastat service code of a product.
In Figure 5.6, the Reclassify Products – Intrastat Service Codes app is shown.
As you can see, the service product CONSULTING is assigned intrastat ser-
vice code 620111. After you click the Reclassify button, the system takes you
to the next screen wherein you can select relevant intrastat service codes.
You can also reclassify the product and save the data.
Figure 5.6 Reclassify Products – Intrastat Service Codes SAP Fiori App
Creating a Report
The creation of an intrastat report is carried out in two steps, which we’ll
discuss in this section. The first step is to select relevant business transac-
tions for dispatch and arrivals, and in the second step, the relevant data is
reviewed and released. After the data is released, you can generate the
required intrastat report file.
The following two SAP Fiori apps are meant to schedule background jobs for
relevant business transaction selections:
Those who have worked with the SD-FT component in SAP ERP systems are
aware of various transaction codes that are based on a country-specific intra-
stat reporting requirement. However, in SAP S/4HANA for international
trade, there are only four SAP GUI transaction codes, and the rest are based
on SAP Fiori apps. The few old transaction codes for selection of relevant
business transactions for intrastat reporting are still valid in SAP S/4HANA
(Transaction MEIS for arrivals and Transaction VE01 for dispatches).
Figure 5.8 shows the selection screen for another SAP GUI transaction,
Transaction VE01.
for which report is to be created. Again, the relevant plant for which the
report is to be generated is taken from the provider of information master
data. In addition, from this transaction in SAP S/4HANA you no longer can
select or exclude any specific billing document (sales-related billing docu-
ment) or select business transactions based on any specific foreign trade-
related data. It is worth mentioning here that the foreign trade data tab on
the header and item levels on delivery, billing, or purchasing documents is
also not available in SAP S/4HANA.
For both these transactions, after you execute them, the system displays a
pop-up message box that states how many relevant transactions the sys-
tem selected for the specified provider of information and the period for
which the transaction is executed.
Intrastat Declaration
The final step is to create the required intrastat report. To create the intrastat
report, you can use either the SAP GUI transaction (Transaction /n/ECRS/
RP_EDIT) or the Manage Intrastat Declaration SAP Fiori app.
Figure 5.9 shows the list of declarations that the system created based on
the business transactions selected in the previous step.
쐍 Provider of Info.
The list of declarations from different periods is displayed for the pro-
vider of information 9999.
쐍 Direction
Data under this column indicates if the declaration is for Receipt (arrivals)
or Dispatch.
쐍 Status
Data under this column shows if the report was released or is still in pro-
cess.
쐍 Correct
The checkboxes under this column show if the data selected is complete
and verified. If a checkbox is not selected, there are records in this list that
might have missing data (information). To resolve this issue, select the
row or double-click it to go to the item details and correct (maintain) rel-
evant data and save.
쐍 File Created
A selected checkbox indicates that an intrastat file was created for a spe-
cific record.
쐍 Number of Items
Data under this column indicates the number of transactions selected.
For example, for the Year 2019 and period (Month) 8, two dispatch trans-
actions were selected for reporting.
쐍 Inv. Value
Data under this column shows the aggregated statistical value in com-
pany code (local) currency of all the items selected as part of the list.
쐍 Net Weight
Data under this column shows the aggregated weight of all the items
selected as part of the list.
In addition to the SAP GUI transaction, there is also an SAP Fiori app named
Manage Intrastat Declarations based on SAP Screen Personas.
Figure 5.10 shows the screen when the Manage Intrastat Declarations app is
used. It has the same functionality and features as those used for the SAP
GUI Transaction /ECRS/RP_EDIT.
Now let’s explain how to verify that the data selected has all the required
information and how to take necessary action if any data is missing before
you release the declaration for generating the intrastat file.
After selecting a file from the list, go to the Header level and verify that the
data is correct.
In Figure 5.11, you can see the Header level of the list. When you click the
Check Header button, the system verifies the record and issues a message
relaying whether the record is correct or not. In this case, the system has
found the record to have the correct header data.
Similarly, from the main screen, you can select the list and go to item level
details. Figure 5.12 shows the option of selecting and verifying item level
data from the Change Intrastat Declaration: Item Overview screen. You can
either place the cursor on an item row and click the details icon (the magni-
fying glass) or double-click an item row. The system then will take you to the
item detail screen.
Figure 5.13 shows the item detail screen that displays a list of missing data
under Check Result. In our example, business transaction type and com-
modity code (the tariff code of the product) are missing. Maintain the rele-
vant data and save the record.
As shown in Figure 5.14, after you maintain relevant data and click the Check
Item button to carry out a recheck, the system first verifies all mandatory
data for declaration and accordingly issues a message. This time the system
confirms that all information is correctly maintained.
As shown in Figure 5.15, the dispatch record for Year 2019 and period (Month)
8 is in Released status. This information means that the system is ready to cre-
ate a declaration file. To do so, click the Create Declaration button on the appli-
cation bar. This action displays a pop-up message with a default file name.
Select the relevant folder, and if desired, rename the file before saving.
Finally, as shown in Figure 5.16, after you save the file, the File Created check-
box appears ticked and a relevant message is also displayed at the bottom of
the screen.
6 Implementation at a Glance
The move to the SAP S/4HANA system is a complex process. The implemen-
tation approach depends on the current application and level of customer-
specific customization that has been carried out in the existing application.
The two common implementation approaches are as follows:
쐍 Greenfield
This approach is based on the “start-from-scratch” strategy. This strategy
provides an opportunity to review the existing processes and business
models that have been built over the years based on previous technology
and software capabilities. Now, based on the new possibilities with the
enhanced SAP S/4HANA digital core and various cloud applications per
line of business, it might be good to consider a complete business trans-
formation. This approach can be followed for an on-premise, cloud, or
hybrid solution.
쐍 Brownfield
This approach is for an existing SAP ERP installed base. The idea is to carry
out conversion and migration of existing applications and data from SAP
ERP to an SAP S/4HANA system. SAP provides various migration paths
and tools based on the existing system version to latest SAP S/4HANA
version. This approach promises to enable you to move to SAP S/4HANA
in a shorter time. However, it all depends on the current business process
and level of client-specific customization existing in the system. This
approach is recommended for on-premise systems only.
The system readiness check consists of the following analyses that can be
carried out in an existing SAP ERP system:
쐍 Add-on compatibility
This provides an analysis of any add-on components that have been used
with the existing system and determines if they are compatible with the
target SAP S/4HANA system version. In some cases, an add-on version
might need an upgrade. If the add-on component is not supported, then
the report provides other possible options.
쐍 Business functions
Business functions that are active in the systems are verified, and the
report provides a list of business functions that might need to be
switched on after system conversion.
쐍 Simplification lists
Based on the existing database tables and used transaction codes, the
analysis report prescribes a simplification list that provides details of
what action or workaround should be considered while moving to an SAP
S/4HANA system. Based on the analysis the list of simplification items is
classified in three different categories. The first category is of simplifica-
tion items that are relevant and need immediate action based on the de-
tails that SAP recommended. The second category is of simplification lists
that are relevant, but need to be verified to determine if immediate adjust-
ment is needed. The final category of simplification items includes those
that are found relevant, but are not of high importance from a strategic
System Migration
SAP S/4HANA for international trade has replaced the SD-FT component’s
functionality existing in SAP ERP. This means there is no easy option for sys-
tem conversion and data migration related to the SD-FT component. You
need to consider this migration based on specific functionality that has been
used in your current SAP ERP application. SAP S/4HANA for international
trade supports product classification for both commodity codes and export
control classification. It also enables trade compliance and license manage-
ment, embargo checks, and intrastat reporting. The option is to carry out
data migration (including foreign trade-related data) after the system is con-
verted to SAP S/4HANA. This part of the data migration needs to be treated
as a greenfield project.
Note
There is a detailed step-by-step description provided in SAP Note 2520879 –
Migration of Financial Documents from SD-FT to Trade Finance in Treasury and
Risk Management.
If you have been using the SAP ERP SD-FT component’s functionality along
with a third-party customs application, then before migrating, you need to
check the integration with such third-party systems because the data struc-
ture is completely changed in the SAP S/4HANA system.
7 What’s Next?
You’ve explored the ins and outs of SAP S/4HANA for international trade.
Now, expand your logistics horizons even further! Walk through foreign
trade with SAP Global Trade Services, discover more logistics processes in
your SAP S/4HANA system, map out your company’s compliance with key
data regulations, and more. Your SAP PRESS journey is only just beginning!
In addition to this book, our editors picked a few other SAP PRESS publica-
tions that you might also be interested in. Check out the next page to learn
more!
Notes on Usage
This E-Bite is protected by copyright. By purchasing this E-Bite, you have
agreed to accept and adhere to the copyrights. You are entitled to use this
E-Bite for personal purposes. You may print and copy it, too, but also only
for personal use. Sharing an electronic or printed copy with others, how-
ever, is not permitted, neither as a whole nor in parts. Of course, making
them available on the Internet or in a company network is illegal.
For detailed and legally binding usage conditions, please refer to the section
Legal Notes.
Service Pages
The following sections contain notes on how you can contact us.
Legal Notes
This section contains the detailed and legally binding usage conditions for
this E-Bite.
Copyright Note
This publication is protected by copyright in its entirety. All usage and
exploitation rights are reserved by the author and Rheinwerk Publishing; in
particular the right of reproduction and the right of distribution, be it in
printed or electronic form.
Digital Watermark
This E-Bite copy contains a digital watermark, a signature that indicates
which person may use this copy. If you, dear reader, are not this person,
you are violating the copyright. So please refrain from using this E-Bite
and inform us about this violation. A brief email to info@rheinwerk-
publishing.com is sufficient. Thank you!
Limitation of Liability
Regardless of the care that has been taken in creating texts, figures, and pro-
grams, neither the publisher nor the author, editor, or translator assume
any legal responsibility or any liability for possible errors and their conse-
quences.
1
ISBN 978-1-4932-1933-9
© 2020 by Rheinwerk Publishing, Inc., Boston (MA)
1st edition 2020
All rights reserved. Neither this publication nor any part of it may SAP, the SAP logo, ABAP, Ariba, ASAP, Concur, Concur ExpenseIt,
be copied or reproduced in any form or by any means or translated Concur TripIt, Duet, SAP Adaptive Server Enterprise, SAP Advan-
into another language, without the prior consent of Rheinwerk tage Database Server, SAP Afaria, SAP ArchiveLink, SAP Ariba, SAP
Publishing, 2 Heritage Drive, Suite 305, Quincy, MA 02171. Business ByDesign, SAP Business Explorer, SAP BusinessObjects,
SAP BusinessObjects Explorer, SAP BusinessObjects Lumira, SAP
Rheinwerk Publishing makes no warranties or representations BusinessObjects Roambi, SAP BusinessObjects Web Intelligence,
with respect to the content hereof and specifically disclaims any SAP Business One, SAP Business Workflow, SAP Crystal Reports,
implied warranties of merchantability or fitness for any particular SAP EarlyWatch, SAP Exchange Media (SAP XM), SAP Fieldglass,
purpose. Rheinwerk Publishing assumes no responsibility for any SAP Fiori, SAP Global Trade Services (SAP GTS), SAP GoingLive, SAP
errors that may appear in this publication. HANA, SAP HANA Vora, SAP Hybris, SAP Jam, SAP MaxAttention,
SAP MaxDB, SAP NetWeaver, SAP PartnerEdge, SAPPHIRE NOW,
“Rheinwerk Publishing” and the Rheinwerk Publishing logo are
SAP PowerBuilder, SAP PowerDesigner, SAP R/2, SAP R/3, SAP
registered trademarks of Rheinwerk Verlag GmbH, Bonn, Ger-
Replication Server, SAP S/4HANA, SAP SQL Anywhere, SAP Strate-
many. SAP PRESS is an imprint of Rheinwerk Verlag GmbH and
gic Enterprise Management (SAP SEM), SAP SuccessFactors, The
Rheinwerk Publishing, Inc.
Best-Run Businesses Run SAP, TwoGo are registered or unregistered
trademarks of SAP SE, Walldorf, Germany.
All of the screenshots and graphics reproduced in this book are
subject to copyright © SAP SE, Dietmar-Hopp-Allee 16, 69190 Wall- All other products mentioned in this book are registered or unreg-
dorf, Germany. istered trademarks of their respective companies.