User Guide | PUBLIC

2024-03-28

Conversion Guide for SAP Global Trade Services,

edition for SAP HANA
© 2024 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 Purpose Of This Conversion Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Useful Links and SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Useful Links for the Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Getting Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 SAP Global Trade Services, edition for SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.1 Changes Between SAP Global Trade Services and SAP GTS, edition for SAP HANA. . . . . . . . . . . . . . 10
XPRAs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
BAdIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Business Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Main Function Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Main Data Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Change Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
2.2 Overview of the Conversion Process of SAP GTS, edition for SAP HANA. . . . . . . . . . . . . . . . . . . . . . 59
Preparing the Conversion of a Test or Production System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Executing the Conversion of a Development System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Executing the Conversion of a Test or Productive System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Conversion of a Simple System Landscape of SAP Global Trade Services. . . . . . . . . . . . . . . . . . 63
2.3 Preparing the Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Planning & System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Maintenance Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Cross-Application Preparation Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
Application-Specific Preparation Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
2.4 Executing the Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Software Update Manager (SUM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
System Downtime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
XPRAs Executed During Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Optimizing the Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Follow-On-Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

3 Server Release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
3.1 SAP S/4HANA Foundation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Documentation, Tools, and SAP Notes for the Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Overview of the Conversion Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
2 PUBLIC Content
3.2 SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
Content PUBLIC 3
1 Purpose Of This Conversion Guide

This guide is the central starting point for the conversion from SAP Global Trade Services 10.0, 10.1 und
11.0 (SAP GTS) to SAP Global Trade Services, edition for SAP HANA (SAP GTS, edition for SAP HANA). This
Conversion Guide explains the conversion process.

This Conversion Guide addresses the following target audience:

• System administrators
• Technical consultants
• Key users

SAP Global Trade Services, edition for SAP HANA

SAP Global Trade Services, edition for SAP HANA is not the successor of SAP Global Trade Services. SAP
Global Trade Services, edition for SAP HANA is a new product, built entirely on one of the most advanced
in-memory platforms today – SAP HANA® – and incorporates modern design principles through the SAP Fiori
user experience (UX). For the new 2023 product version, the software component name has changed from
SLL-LEG to GTSCORE.

This Guide describes the conversion of SAP Global Trade Services 11.0 to SAP
Global Trade Services, edition for SAP HANA 2023:

Conversion to SAP S/4HANA FOUNDATION 2022 from the following starting status:
• SAP Global Trade Services 11.0 on SAP NetWeaver
• SAP Global Trade Services, edition for SAP HANA 2020 on SAP S/4HANA FOUNDATION 2020/2021

Conversion to SAP S/4HANA 2022 from the following starting status:

• SAP Global Trade Services 11.0 on SAP ERP 6.0

SAP S/4HANA FOUNDATION

SAP S/4HANA FOUNDATION is the next-generation business suite foundation platform. It is fully built on the
most advanced in-memory platform existing today: SAP HANA.

The product uses modern design principles with the SAP Fiori user experience (UX) as well as a new role-based
user experience concept. With the move to SAP S/4HANA FOUNDATION, you are benefitting from continuous
application innovations such as the following:

• Application optimizations specific for SAP HANA in-memory platform

With SAP S/4HANA FOUNDATION, SAP optimizes the application to make best use of the capabilities of
the SAP HANA database. For example, we removed aggregates, and reduced the data footprint.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
4 PUBLIC Purpose Of This Conversion Guide
 • Responsive user experience design
With SAP S/4HANA FOUNDATION, SAP designs the application with the latest role-based user experience
(UX).
• Unifying functionality in the core
With SAP S/4HANA FOUNDATION, SAP removes redundancy by providing one functionality for one
objective.
With SAP S/4HANA FOUNDATION, SAP helps businesses to run simple in the digital economy, including
such topics and principles as the Internet of Things, Big Data, business networks, and mobile-first.

SAP S/4HANA

SAP S/4HANA is the next-generation business suite. It is fully built on the most advanced in-memory platform
existing today: SAP HANA. The product uses modern design principles with the SAP Fiori user experience (UX)
as well as a new role-based user experience concept. With the move to SAP S/4HANA, you are benefitting from
continuous application innovations such as:

• Application optimizations specific for SAP HANA in-memory platform With SAP S/4HANA, SAP optimizes
the application to make best use of the capabilities of the SAP HANA database. For example, we removed
aggregates, and reduced the data footprint.
• Responsive user experience design With SAP S/4HANA, SAP designs the application with the latest
role-based user experience (UX).
• Unifying functionality in the core With SAP S/4HANA, SAP removes redundancy by providing one
functionality for one objective.

With SAP S/4HANA, SAP helps businesses to run simple in the digital economy, including such topics and
principles as the Internet of Things, Big Data, business networks, and mobile-first.

Getting Started [page 5]

1.1 Getting Started

Document History [page 5]

Useful Links and SAP Notes [page 6]

Useful Links for the Conversion [page 8]

Getting Support [page 9]

1.1.1 Document History

This document is release-dependent. For future versions, this document will be updated. Make sure you have
the latest version of this document.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
Purpose Of This Conversion Guide PUBLIC 5
  Note

The latest version of this document is available on SAP Help Portal at https://help.sap.com/gtse4h

1.1.2 Useful Links and SAP Notes

The following resources provide access to more information about general topics.

Resource Where to Find It

SAP Notes Search https://support.sap.com/notes

SAP Software Download Center https://support.sap.com/swdc

Product Availability Matrix https://support.sap.com/pam

Get Involved Early https://support.sap.com/en/offerings-programs/get-in-

volved-early.html

Sizing https://www.sap.com/about/benchmark/sizing.html

Performance https://www.sap.com/about/benchmark/sizing/perform-
ance.html

Informs about support package stacks, latest software ver- https://support.sap.com/sp-stacks

sions, and patch level requirements

Informs about how to install and implement this product and Administration Guide for SAP Global Trade Services, edition
also provides security, integration operation, and UI technol- for SAP HANA
ogy information

Useful Links for the Conversion

SAP Notes for Installation

SAP Note Title

3271443 Release strategy and maintenance information for the ABAP

add-on GTSCORE 200

3271369 Release strategy and maintenance information for the ABAP

add-on UIGRCGTS 200

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
6 PUBLIC Purpose Of This Conversion Guide
 SAP Note Title

2356692 Enhancement of uninstallation class as part of conversion to

SAP GTS, edition for SAP HANA 2023

2964245 SAP GTS, edition for SAP HANA: Conversion readiness

check - installation

3237135 General Information: Installation details of SAP Fiori front-

end server 2022 for SAP S/4HANA

3191581 SAP Fiori front-end server 2022 for SAP S/4HANA

3143630 S/4HANA FOUNDATION 2022: Release Information Note

070228 Add-ons: Conditions and upgrade planning

83458 @19@OCS Info: Patch download from SAP Service Market-

place

337623 Customizing after installation or upgrade

Information and instruction how to take over sample config-

uration of the SAP standard (client 000).

More Information

Link Document

PAM FND2022 (select the SAP S/4HANA FOUNDATION Product Availability Matrix of SAP S/4HANA FOUNDATION
2022 version) 2022

PAM S/4HANA 2022 Product Availability Matrix of SAP S/4HANA 2022

Maintenance Planner Maintenance Planner

Software Provisioning Manager Software Provisioning Manager

Choose System Provisioning System Provisioning

Scenarios Installation Option of Software Provisioning
Manager 2.0 SP 00 (or higher) Installation Guides -
Application Server Systems.

These installation guides are sorted by database, technical

stack (ABAP), and operating system platform. For the in-
stallation of SAP S/4HANA FOUNDATION, choose the SAP
HANA Database guide for your operating system (UNIX,
IBM, or Windows), the ABAP Stack, and the SAP HANA Da-
tabase.

SUM Software Update Manager (SUM)

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
Purpose Of This Conversion Guide PUBLIC 7
Link Document

SAINT SAP Add-On Installation Tool (SAINT)

SAP Fiori Implementation SAP Fiori Implementation Information

See here SAP HANA Server Installation and Update Guide

1.1.3 Useful Links for the Conversion

SAP Notes for the Installation

SAP Note Title

3271443 Release strategy and maintenance information for the ABAP

add-on GTSCORE 200

3271369 Release strategy and maintenance information for the ABAP

add-on UIGRCGTS 200

2356692 Enhancement of uninstallation class as part of conversion to

SAP GTS, edition for SAP HANA 2023

2964245 SAP GTS, edition for SAP HANA: Conversion readiness

check - installation

3237135 General Information: Installation details of SAP Fiori front-

end server 2022 for SAP S/4HANA

3191581 SAP Fiori front-end server 2022 for SAP S/4HANA

3143630 S/4HANA FOUNDATION 2022: Release Information Note

070228 Add-ons: Conditions and upgrade planning

83458 @19@OCS Info: Patch download from SAP Service Market-

place

337623 Customizing after installation or upgrade

Information and instruction how to take over sample config-

uration of the SAP standard (client 000).

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
8 PUBLIC Purpose Of This Conversion Guide
More Information

Link Document

PAM FND2022 (select the SAP S/4HANA FOUNDATION Product Availability Matrix of SAP S/4HANA FOUNDATION
2022 version) 2022

PAM S/4HANA 2022 Product Availability Matrix of SAP S/4HANA 2022

Maintenance Planner Maintenance Planner

Software Provisioning Manager Software Provisioning Manager

Choose System Provisioning System Provisioning

Scenarios Installation Option of Software Provisioning
Manager 2.0 SP 00 (or higher) Installation Guides -
Application Server Systems.

These installation guides are sorted by database, technical

stack (ABAP), and operating system platform. For the in-
stallation of SAP S/4HANA FOUNDATION, choose the SAP
HANA Database guide for your operating system (UNIX,
IBM, or Windows), the ABAP Stack and the SAP HANA Data-
base.

SUM Software Update Manager (SUM)

SAINT SAP Add-On Installation Tool (SAINT)

SAP Fiori Implementation SAP Fiori Implementation Information

See here SAP HANA Server Installation and Update Guide

1.1.4 Getting Support

If you encounter any problems with SAP Global Trade Services, edition for SAP HANA, report an incident on
SAP Support Portal. To report an incident, go to SAP Support Portal at http://support.sap.com/incident .

All application components for SAP Global Trade Services, edition for SAP HANA begin with FT-LEG*. The
application component must be specified to at least the third level, for example, FT-LEG-ISR for Intrastat.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
Purpose Of This Conversion Guide PUBLIC 9
2 SAP Global Trade Services, edition for
SAP HANA

This chapter provides you with technical information regarding the conversion from a previous release of SAP
Global Trade Services to SAP Global Trade Services, edition for SAP HANA.

Changes Between SAP Global Trade Services and SAP GTS, edition for SAP HANA [page 10]

Overview of the Conversion Process of SAP GTS, edition for SAP HANA [page 59]

Preparing the Conversion [page 67]

Executing the Conversion [page 77]

2.1 Changes Between SAP Global Trade Services and SAP

GTS, edition for SAP HANA

XPRAs [page 10]

BAdIs [page 46]

Authorizations [page 56]

Business Roles [page 56]

Main Function Modules [page 57]

Main Data Tables [page 57]

Change Documents [page 58]

2.1.1 XPRAs
The XPRAs (Execution of programs after inputs) /SAPSLL/XPRA_V8000, /SAPSLL/XPRA_GTSC200 (XPRA
Report for Upgrade to SAP GTS, edition for SAP HANA), and /IBPP/XPRA_IBPP200_VD_ITEM (Move 'Source'
Information from IBVD Header to IBVD Item) are started during the conversion to SAP Global Trade Services,
edition for SAP HANA. Each XPRA executes the relevant conversion tasks in parallel. The XPRA report /
SAPSLL/XPRA_V8000 generates a processing log and lists the tasks individually. This enables you to check if
all tasks were executed successfully, or if there were tasks executed with errors. This lets you recognize if the
data conversion ran successfully, or if postprocessing is required.

There may be additional XPRAs delivered with the underlying release of SAP S/4HANA FOUNDATION 2022
that are not listed here.

Each XPRA contains checks to determine whether it really needs to convert any data based on the current data
in the system.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
10 PUBLIC SAP Global Trade Services, edition for SAP HANA
The following contains listed details of the individual XPRA Conversion Task IDs for each application area:

Conversion Tasks for General Application Area [page 11]

Conversion Tasks for Compliance Management [page 11]

Conversion Tasks for Customs Management [page 23]

Conversion Tasks for Preference Management [page 39]

Conversion Tasks for Intrastat [page 42]

Conversion of Customizing [page 45]

2.1.1.1 Conversion Tasks for General Application Area

UPD_TCOGVS_2_TCOGVS and UPD_TCOGVST_2_TCOGVST

Client Independency Removed

To enable current settings in View /SAPSLL/V_TCOGVS, the client independency was removed, and the Client
field was added to the following tables:

• /SAPSLL/TCOGVS (Group of Logical Systems)

• /SAPSLL/TCOGVST (Description of Group of Logical Systems)

UPD_TCOGVA_2_TCOGVA

Client Independency Removed

To enable current settings in View /SAPSLL/V_TCOGVA, the client independency was removed and the Client
field was added to the following tables:

• /SAPSLL/TCOGVA (Assignment of Logical Systems to Groups of Logical Systems)

2.1.1.2 Conversion Tasks for Compliance Management

UPD_2_CUHD

Data Migration to table /SAPSLL/CUHD

Data transfer from the following tables:

• /SAPSLL/CUHDSTA Customs Document Header: Status

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 11
• /SAPSLL/CUHDDAT Customs Document Header: Date Specification

What's New

The following fields were added:

• /SAPSLL/CUHD~FTORG Business Partner Number of the Foreign Trade Organization

• /SAPSLL/CUHD~FTVBS Business Partner Number of the Legal Unit; is filled exclusively for customs
documents that were created or will be created as part of SAP GTS Customs Management
• SPL screening via TREX is no longer supported; for this reason, value [1E] = “Not Screened / Blocked:
TREX Not Available” of field /SAPSLL/CUHD~STSPL_AGG was replaced by [1A] = „Not Screened /
Blocked“
• Fields from table /CUHDDAT
• Fields from table /CUHDSTA
• Processing status and processing progress of a customs declaration are depicted in the following fields
and replace /CUHDSTA~PROST:
• /SAPSLL/CUHD~CDSTS Processing Status
• /SAPSLL/CUHD~CDPRG Processing Progress
• /SAPSLL/CUHD~WRESP Waiting for Response from Authority
• /SAPSLL/CUHD~ARCHI Archiving Flag
• The field /SAPSLL/CHDSTA~PROVO Previous Document Processing Status has been retired and is not part
of the data migration

Retirement of the following tables:

• /SAPSLL/CUHDSTA Customs Document Header: Status

• /SAPSLL/CUHDDAT Customs Document Header: Date Specification

UPD_2_CUIT

Data Migration to table /SAPSLL/CUIT

Data migration from the following tables:

• /SAPSLL/CUITSTA Customs Document Item: Status

• /SAPSLL/CUITDAT Customs Document Item: Date Specification

What's New

The following fields were added:

• /SAPSLL/CUIT~CDTYP Document Type

• /SAPSLL/CUIT~FTORG Business Partner Number of the Foreign Trade Organization
• /SAPSLL/CUIT~FTVBS Business Partner Number of the Legal Unit
• /SAPSLL/CUIT~RPTDA Check Date for Prohibitions and Restrictions
• SPL screening via TREX is no longer supported; for this reason, value [1E] = “Not Screened / Blocked:
TREX Not Available” of field /SAPSLL/CUIT~STSPL was generally replaced by [1A] = “Not Screened /
Blocked”
• Field RPTDA was added and replaces field /SAPSLL/CUIT~RPTDT (Definitive Date as Time Stamp).

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
12 PUBLIC SAP Global Trade Services, edition for SAP HANA
Retirement of the following tables:

• /SAPSLL/CUITSTA Customs Document Item: Status

• /SAPSLL/CUITDAT Customs Document Item: Date Specification

UPD_2_CORCTS

Changes in table /SAPSLL/CORCTS

What's New

• The actual classification code replaces the classification UUID.

• Field /SAPSLL/CORCTS~GUID_CTSNUM was retired and replaced by /SAPSLL/CORCTS~CCNGN.
• In the future, field /SAPSLL/CORCTS~CLSTY describes the classification type, for example, [A] = tariff
number, [B] = commodity code, [C] = export control classification number, and so on.

INS_CORCTSC_2_CORCTS

Data Migration to table /SAPSLL/CORCTS

What's New

• The classification UUID was replaced by the actual classification code /SAPSLL/CORCTS~CCNGN

Retirement of table: /SAPSLL/CORCTSC Customs Document Item: Country-Dependent Classification

UPD_2_LEGCON

Changes in table /SAPSLL/LEGCON

What's New

• The classification UUIDs of fields GUID_CTS_VDP and GUID_CTS_QDP were retired and were
replaced by the actual classification codes in table fields /SAPSLL/LEGCON~CCNGN_VDP and /SAPSLL/
LEGCON~CCNGN_QDP.

UPD_2_LICHD

Changes in table /SAPSLL/LICHD

What's New

• Fields from table /SAPSLL/LCLIC were migrated to /SAPSLL/LICHD

• The Valid From and Valid To time stamps (/SAPSLL/LICHD~DATAB and /SAPSLL/LICHD~DATBI) were
transferred to data fields (/SAPSLL/LICHD~VALFR and /SAPSLL/LICHD~VALTO).

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 13
INS_LCLICC_2_LICHDCL

Data Migration to table /SAPSLL/LICHDCL

What's New

• Fields from table /SAPSLL/LCLICC were migrated to /SAPSLL/LICHDCL

• The UUID reference to the control class was dropped (/SAPSLL/LCLICC~GUID_CTS) and was replaced
by the actual classification code of the control class (/SAPSLL/LICHDCL~CONCL) in the context of the
corresponding numbering scheme (/SAPSLL/LICHDCL~STCTS).

Retirement of table: /SAPSLL/LCLICC License: Control Classes

INS_LCLICAV_2_LICHDRV

Data Migration to table /SAPSLL/LICHDRV

What's New

• The UUID reference to the classification code was dropped (/SAPSLL/LCLICAV~GUID_CTS) and was
replaced by the classification code (/SAPSLL/LICHDRV~CCNGN).

Retirement of table: /SAPSLL/LCLICAV License: Write-Off / Available Value

INS_LCLICAVL_2_LICHDRVL

Data Migration to table /SAPSLL/LICHDRVL

• No structural changes between target table and source table. Simply adjustment of the names of the
referenced table /SAPSLL/LICHDRVL, for example, field /SAPSLL/LCLICRVL~GUID_LCLICRV.

Retirement of table: /SAPSLL/LCLICAVL License: Write-Off Logging / Available Value

INS_LCLICAQ_2_LICHDRQ

Data Migration to table /SAPSLL/LICHDRQ

• The UUID reference to the classification code was dropped (/SAPSLL/LCLICAQ~GUID_CTS) and was
replaced by the classification code (/SAPSLL/LICHDRQ~CCNGN).

Retirement of table: /SAPSLL/LCLICAQ License: Write-Off / Available Quantity

INS_LCLICAQL_2_LICHDRQL

Data Migration to table /SAPSLL/LICHDRQL

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
14 PUBLIC SAP Global Trade Services, edition for SAP HANA
 • No structural changes between target table and source table. Simply adjustment of the names of the
referenced table /SAPSLL/LCLICRQ, for example, field /SAPSLL/LICHDRQL~GUID_LCLICRQ.

Retirement of table: /SAPSLL/LCLICAQL License: Write-Off Logging / Available Quantity

UPD_2_TCOCMP

Changes in table /SAPSLL/TCOCMP

• SPL screening via SAP TREX was retired (/SAPSLL/TCOCMP~CMPTR = [ ] )

INS_CD01_2_CD01N

Data Migration to table /SAPSLL/CD01N

• The Valid From and Valid To time stamps (/SAPSLL/CD01~DATAB and /SAPSLL/CD01~DATBI) were
transferred to data fields (/SAPSLL/CD01N~DATAB and /SAPSLL/CD01N~DATBI).
• The UUID reference to the classification condition (/SAPSLL/CD01~GUID_CTSCD) is obsolete and was
dropped without replacement.

Retirement of table: /SAPSLL/CD01 Determination Strategy (License Type): Country / Control Grouping

INS_CD02_2_CD02N

Data Migration to table /SAPSLL/CD02N

• The Valid From and Valid To time stamps (/SAPSLL/CD02~DATAB and /SAPSLL/CD02~DATBI) were
transferred to data fields (/SAPSLL/CD02N~DATAB and /SAPSLL/CD02N~DATBI).
• The UUID reference to the control class was dropped (/SAPSLL/CD02~GUID_CTS) and was replaced
by the actual classification code of the control class (/SAPSLL/CD02N~CONCL) in the context of the
corresponding numbering scheme (/SAPSLL/CD02N~STCTS).
• The UUID reference to the classification condition (/SAPSLL/CD02~GUID_CTSCD) was dropped and was
replaced by the classification code of the classification condition (/SAPSLL/CD02N~CTSCD) in the context
of the corresponding numbering scheme (/SAPSLL/CD02N~STCTS_CTSCD).

Retirement of table: /SAPSLL/CD02 Determination Strategy (License Type): Country / Control Class

INS_CD03_2_CD03N

Data Migration to table /SAPSLL/CD03N

• The Valid From and Valid To time stamps (/SAPSLL/CD03~DATAB und /SAPSLL/CD03~DATBI) were
transferred to data fields (/SAPSLL/CD03N~DATAB and /SAPSLL/CD03N~DATBI).

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 15
• The UUID reference to the classification condition (/SAPSLL/CD03~GUID_CTSCD) is obsolete and was
dropped without replacement.

Retirement of table: /SAPSLL/CD03 Determination Strategy (License Type): Country Group / Control Group.

INS_CD04_2_CD04N

Data Migration to table /SAPSLL/CD04N

• The Valid From and Valid To time stamps (/SAPSLL/CD04~DATAB und /SAPSLL/CD04~DATBI) were
transferred to data fields (/SAPSLL/CD04N~DATAB and /SAPSLL/CD04N~DATBI).
• The UUID reference to the control class was dropped (/SAPSLL/CD04~GUID_CTS) and was replaced by
the reference number of the control class (/SAPSLL/CD04N~CONCL) in the context of the corresponding
numbering scheme (/SAPSLL/CD04N~STCTS).
• The UUID reference to the classification condition (/SAPSLL/CD04~GUID_CTSCD) was dropped and was
replaced by the reference number of the classification condition (/SAPSLL/CD04N~CTSCD) in the context
of the corresponding numbering scheme (/SAPSLL/CD04N~STCTS_CTSCD).

Retirement of table: /SAPSLL/CD04 Determination Strategy (License Type): Country Group / Control Class

INS_CD05_2_CD05N

Data Migration to table /SAPSLL/CD05N

• The Valid From and Valid To time stamps (/SAPSLL/CD05~DATAB and /SAPSLL/CD05~DATBI) were
transferred to data fields (/SAPSLL/CD05N~DATAB and /SAPSLL/CD05N~DATBI).
• The UUID reference to the classification condition (/SAPSLL/CD05~GUID_CTSCD) is obsolete and was
dropped without replacement.

Retirement of table: /SAPSLL/CD05 Determination Strategy (License Type): Country

INS_CD06_2_CD06N

Data Migration to table /SAPSLL/CD06N

• The Valid From and Valid To time stamps (/SAPSLL/CD06~DATAB und /SAPSLL/CD06~DATBI) were
transferred to data fields (/SAPSLL/CD06N~DATABund /SAPSLL/CD06N~DATBI).
• The UUID reference to the classification condition (/SAPSLL/CD06~GUID_CTSCD) is obsolete and was
dropped without replacement.

Retirement of table: /SAPSLL/CD06 Determination Strategy (License Type): Country Group

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
16 PUBLIC SAP Global Trade Services, edition for SAP HANA
INS_CD07_2_CD07N

Data Migration to table /SAPSLL/CD07N

• The Valid From and Valid To time stamps (/SAPSLL/CD07~DATAB and /SAPSLL/CD07~DATBI) were
transferred to data fields (/SAPSLL/CD07N~DATAB and /SAPSLL/CD07N~DATBI).
• The UUID reference to the classification condition (/SAPSLL/CD07~GUID_CTSCD) is obsolete and was
dropped without replacement.

Retirement of table: /SAPSLL/CD07 Determination Strategy (License Type): Control Grouping

INS_CD08_2_CD08N

Data Migration to table /SAPSLL/CD08N

• The Valid From and Valid To time stamps (/SAPSLL/CD08~DATAB and /SAPSLL/CD08~DATBI) were
transferred to data fields (/SAPSLL/CD08N~DATAB and /SAPSLL/CD08N~DATBI).
• The UUID reference to the control class (/SAPSLL/SAPSLL/CD08~GUID_CTS) was dropped and was
replaced by the reference number of the control class (/SAPSLL/CD08N~CONCL) in the context of the
corresponding numbering scheme (/SAPSLL/CD08N~STCTS).
• The UUID reference to the classification condition (/SAPSLL/CD08~GUID_CTSCD) was dropped and was
replaced by the reference number of the classification condition (/SAPSLL/CD08N~CTSCD) in the context
of the corresponding numbering scheme (/SAPSLL/CD08N~STCTS_CTSCD).

Retirement of table: /SAPSLL/CD08 Determination Strategy (License Type): Control Class

INS_CD09_2_CD09N

Data Migration to table /SAPSLL/CD09N

• The Valid From and Valid To time stamps (/SAPSLL/CD09~DATAB and /SAPSLL/CD09~DATBI) were
transferred to data fields (/SAPSLL/CD09N~DATAB and /SAPSLL/CD09N~DATBI).
• The UUID reference to the classification condition (/SAPSLL/CD09~GUID_CTSCD) is obsolete and was
dropped without replacement.

Retirement of table: /SAPSLL/CD09 Determination Strategy (License Type): Legal Regulation

INS_CD10_2_CD10N

Data Migration to table /SAPSLL/CD10N

• The Valid From and Valid To time stamps (/SAPSLL/CD10~DATAB and /SAPSLL/CD10~DATBI) were
transferred to data fields (/SAPSLL/CD10N~DATAB and /SAPSLL/CD10N~DATBI).
• The UUID reference to the classification condition (/SAPSLL/CD10~GUID_CTSCD is obsolete and was
dropped without replacement.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 17
Retirement of table: /SAPSLL/CD10 Determination Strategy (License Type): Country / LoC Partner Group

INS_CD11_2_CD11N

Data Migration to table /SAPSLL/CD11N

• The Valid From and Valid To time stamps (/SAPSLL/CD11~DATAB and /SAPSLL/CD11~DATBI) were
transferred to data fields (/SAPSLL/CD11N~DATAB and /SAPSLL/CD11N~DATBI).
• The UUID reference to the classification condition (/SAPSLL/CD11~GUID_CTSCD is obsolete and was
dropped without replacement.

Retirement of table: /SAPSLL/CD11 Determination Strategy (License Type): Country Group / LoC- Partner
Group

INS_CD12_2_CD12N

Data Migration to table /SAPSLL/CD12N

• The Valid From and Valid To time stamps (/SAPSLL/CD12~DATAB and /SAPSLL/CD12~DATBI) were
transferred to data fields (/SAPSLL/CD12N~DATAB and /SAPSLL/CD12N~DATBI).
• The UUID reference to the classification condition (/SAPSLL/CD12~GUID_CTSCD is obsolete and was
dropped without replacement.

Retirement of table: /SAPSLL/CD12 Determination Strategy (License Type): LoC Partner Group

INS_CD13_2_CD13N

Data Migration to table /SAPSLL/CD13N

• The Valid From and Valid To time stamps (/SAPSLL/CD13~DATAB and /SAPSLL/CD13~DATBI) were
transferred to data fields (/SAPSLL/CD13N~DATABand /SAPSLL/CD13N~DATBI).
• The UUID reference to the control class (/SAPSLL/CD13~GUID_CTS) was dropped and was replaced by
the reference number of the control class (/SAPSLL/CD13N~CONCL) in the context of the corresponding
numbering scheme (/SAPSLL/CD13N~STCTS).
• The UUID reference to the classification condition (/SAPSLL/CD13~GUID_CTSCD) was dropped and was
replaced by the reference number of the classification condition (/SAPSLL/CD13N~CTSCD) in the context
of the corresponding numbering scheme (/SAPSLL/CD13N~STCTS_CTSCD).

Retirement of table: /SAPSLL/CD13 Determination Strategy (License Type): Country / Control Class /
Grouping

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
18 PUBLIC SAP Global Trade Services, edition for SAP HANA
INS_CD14_2_CD14N

Data Migration to table /SAPSLL/CD14N

• The Valid From and Valid To time stamps (/SAPSLL/CD14~DATAB and /SAPSLL/CD14~DATBI) were
transferred to data fields (/SAPSLL/CD14N~DATAB and /SAPSLL/CD14N~DATBI).
• The UUID reference to the control class (/SAPSLL/CD14~GUID_CTS) was dropped and was replaced by
the reference number of the control class (/SAPSLL/CD14N~CONCL) in the context of the corresponding
numbering scheme (/SAPSLL/CD14N~STCTS).
• The UUID reference to the classification condition (/SAPSLL/CD14~GUID_CTSCD) was dropped and was
replaced by the reference number of the classification condition (/SAPSLL/CD14N~CTSCD) in the context
of the corresponding numbering scheme (/SAPSLL/CD14N~STCTS_CTSCD).

Retirement of table: /SAPSLL/CD15 Determination Strategy (License Type): Country / Control Class /
Grouping

INS_CD15_2_CD15N

Data Migration to table /SAPSLL/CD15N

• The Valid From and Valid To time stamps (/SAPSLL/CD15~DATAB and /SAPSLL/CD15~DATBI) were
transferred to data fields (/SAPSLL/CD15N~DATAB and /SAPSLL/CD15N~DATBI).
• The UUID reference to the control class (/SAPSLL/CD15~GUID_CTS) was dropped and was replaced by
the reference number of the control class (/SAPSLL/CD15N~CONCL in the context of the corresponding
numbering scheme (/SAPSLL/CD15N~STCTS).
• The UUID reference to the classification condition (/SAPSLL/CD15~GUID_CTSCD) was dropped and was
replaced by the reference number of the classification condition (/SAPSLL/CD15N~CTSCD in the context of
the corresponding numbering scheme (/SAPSLL/CD15N~STCTS_CTSCD).

Retirement of table: /SAPSLL/CD15 Determination Strategy (License Type): Control Class / Grouping

INS_CD18_2_CD18N

Data Migration to table /SAPSLL/CD18N

• The Valid From and Valid To time stamps (/SAPSLL/CD18~DATAB and /SAPSLL/CD18~DATBI) were
transferred to data fields (/SAPSLL/CD18N~DATAB and /SAPSLL/CD18N~DATBI).
• The UUID reference to the control class (/SAPSLL/CD18~GUID_CTS) was dropped and was replaced by
the reference number of the control class (/SAPSLL/CD18N~CONCL) in the context of the corresponding
numbering scheme (/SAPSLL/CD18N~STCTS).
• The UUID reference to the classification condition (/SAPSLL/CD18~GUID_CTSCD) was dropped and was
replaced by the reference number of the classification condition (/SAPSLL/CD18N~CTSCD) in the context
of the corresponding numbering scheme (/SAPSLL/CD18N~STCTS_CTSCD).

Retirement of table: /SAPSLL/CD18 Determination Strategy (License Type): Country Group / Country Group /
Control Class

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 19
INS_CD19_2_CD19N

Data Migration to table /SAPSLL/CD19N

• The Valid From and Valid To time stamps (/SAPSLL/CD19~DATAB and /SAPSLL/CD19~DATBI) were
transferred to data fields (/SAPSLL/CD19N~DATAB and /SAPSLL/CD19N~DATBI).
• The UUID reference to the control class (/SAPSLL/CD19~GUID_CTS) was dropped and was replaced by
the reference number of the control class (/SAPSLL/CD19N~CONCL) in the context of the corresponding
numbering scheme (/SAPSLL/CD19N~STCTS).
• The UUID reference to the classification condition (/SAPSLL/CD19~GUID_CTSCD) was dropped and was
replaced by the reference number of the classification condition (/SAPSLL/CD19N~CTSCD) in the context
of the corresponding numbering scheme (/SAPSLL/CD19N~STCTS_CTSCD).

Retirement of table: /SAPSLL/CD19 Determination Strategy (License Type): Country Group / Country Group /
Control Class / Control Group

INS_CD20_2_CD20N

Data Migration to table /SAPSLL/CD20N

• The Valid From and Valid To time stamps (/SAPSLL/CD20~DATAB and /SAPSLL/CD20~DATBI) were
transferred to data fields (/SAPSLL/CD20N~DATAB and /SAPSLL/CD20N~DATBI).
• The UUID reference to the control class (/SAPSLL/CD20~GUID_CTS) was dropped and was replaced by
the reference number of the control class (/SAPSLL/CD20N~CONCL) in the context of the corresponding
numbering scheme (/SAPSLL/C20N~STCTS).
• The UUID reference to the classification condition (/SAPSLL/CD20~GUID_CTSCD) was dropped and was
replaced by the reference number of the classification condition (/SAPSLL/CD20N~CTSCD) in the context
of the corresponding numbering scheme (/SAPSLL/CD20N~STCTS_CTSCD).

Retirement of table: /SAPSLL/CD20 Determination Strategy (License Type): Region / Region / Control Class

INS_CD21_2_CD21N

Data Migration to table /SAPSLL/CD21N

• The Valid From and Valid To time stamps (/SAPSLL/CD21~DATAB and /SAPSLL/CD21~DATBI) were
transferred to data fields (/SAPSLL/CD21N~DATAB and /SAPSLL/CD21N~DATBI).
• The UUID reference to the classification condition (/SAPSLL/CD21~GUID_CTSCD) is obsolete and was
dropped without replacement.

Retirement of table: /SAPSLL/CD21 Determination Strategy (License Type): Region / Region / Control
Grouping

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
20 PUBLIC SAP Global Trade Services, edition for SAP HANA
INS_CNTRY_2_EMBCTY

Data Migration to table /SAPSLL/EMBCTY

• The Valid From and Valid To time stamps (/SAPSLL/CNTRY~DATAB and /SAPSLL/CNTRY~DATBI) were
transferred to data fields (/SAPSLL/EMBCTY~DATAB and /SAPSLL/EMBCTY~DATBI).

Retirement of table: /SAPSLL/CNTRY Embargo Situation for Each Country

INS_CCCTRY_2_EMBCLR

Data Migration to table /SAPSLL/EMBCLR

• The Valid From and Valid To time stamps (/SAPSLL/CCCTRY~DATAB and /SAPSLL/CCCTRY~DATBI) were
transferred to data fields (/SAPSLL/EMBCLR~DATAB and /SAPSLL/EMBCLR~DATBI).

Retirement of table: /SAPSLL/CCCTRY Embargo Situation for Each Country and Legal Control

INS_CEEMB_2_EMBCCR

Data Migration to table /SAPSLL/EMBCCR

• The Valid From and Valid To time stamps (/SAPSLL/CEEMB~DATAB und /SAPSLL/CEEMB~DATBI) were
transferred to data fields (/SAPSLL/EMBCCR~DATAB und /SAPSLL/EMBCCR~DATBI).

Retirement of table: /SAPSLL/CEEMB Embargo Situation for Each Legal Control and Country of Departure/
Destination

INS_PRCON_2_PRLRG

Data Migration to table /SAPSLL/PRLRG

• The Valid From and Valid To time stamps (/SAPSLL/PRCON~DATAB and /SAPSLL/PRCON~DATBI) were
transferred to data fields (/SAPSLL/ PRLRG~DATAB and /SAPSLL/PRLRG~DATBI).

Retirement of table: /SAPSLL/PRCON Control Data for Legal Control for Product

INS_CORCTZ_2_PRATC

Data Migration to table /SAPSLL/PRATC

What's New

• Fields from table /SAPSLL/CORCTZ were migrated to /SAPSLL/PRATC

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 21
• The classification UUID in /SAPSLL/CORCTZ was replaced by its reference number /SAPSLL/
PRATC~CCNGN
• The UUID reference to the tariff measure according to field /SAPSLL/SAPSLL/CORCTZ~GUID_CTSMAE is
dropped.
• The reference to the product is given by field /SAPSLL/PRATC~GUID_PR. Fields GUID_MOBJ and MOBJT
are not in place.

Retirement of the following tables:

• /SAPSLL/CORCTZ Customs Document Item: Status

• INS_PRCTS_2_PRCLS

Data Migration to table /SAPSLL/PRCLS

What's New

• Fields from table /SAPSLL/PRCTS were migrated to /SAPSLL/PRCLS

• The Valid From and Valid To time stamps (/SAPSLLPRCTS~DATAB and /SAPSLL/PRCTS~DATBI) were
transferred to data fields (SAPSLL/PRCLS~DATAB and /SAPSLL/PRCLS~DATBI).
• The UUID reference to commodity code according to field /SAPSLL/PRCTS~GUID_CTS is dropped and
replaced by the direct reference to the commodity code (/SAPSLL/PRCLS-CCNGN).
Retirement of the following tables:
• /SAPSLL/PRCTS Product Master - Global Customs Tariff Numbers

INS_CTSNZR_2_CTSACN

Data Migration to table /SAPSLL/CTSACN

What's New

• Fields from table /SAPSLL/CTSNZR were migrated to /SAPSLL/CTSACN

Retirement of the following tables:

• /SAPSLL/CTSNZR Customs Tariff Numbers: Number-Custom Code Relation

INS_CTSNUM_2_CTSNR

Data Migration to table /SAPSLL/CTSNR

What's New

• Fields from table /CTSNUM were migrated to /SAPSLL/CTSNR

Retirement of the following tables:

• /SAPSLL/CTSNUM Customs Tariff Number

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
22 PUBLIC SAP Global Trade Services, edition for SAP HANA
INS_CTSNUMT_2_CTSNRT

Data Migration to table /SAPSLL/CTSNRT

What's New

• Fields from table /SAPSLL/CTSNUMT were migrated to /SAPSLL/CTSNRT

Retirement of the following tables:

• /SAPSLL/CTSNUMT Text for Customs Tariff No.

INS_CTSGEN_2_CTSHR

Data Migration to table /SAPSLL/CTSHR

What's New

• Fields from table /CTSGEN were migrated to /SAPSLL/CTSHR

Retirement of the following tables:

• /SAPSLL/CTSGEN Generic Part of Customs Tariff No.

INS_CTSGENT_2_CTSHRT

Data Migration into table /SAPSLL/CTSHRT

What's New

• Fields from table /SAPSLL/CTSGENT were migrated to /SAPSLL/CTSHRT

Retirement of the following tables:

• /SAPSLL/CTSGENT Text for Generic Customs Tariff No.

2.1.1.3 Conversion Tasks for Customs Management

UPD_2_CUHD

Data Migration to table /SAPSLL/CUHD

Data transfer from the following tables:

• /SAPSLL/LEGCOM Customs Document: Communication Numbers

• /SAPSLL/LEGTPR Customs Document Header: Specific Customs Declaration Data
• /SAPSLL/CUHDSTA Customs Document Header: Status

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 23
• /SAPSLL/CUHDDAT Customs Document Header: Date Specification

What's New

The following fields were added:

• /SAPSLL/CUHD~FTORG Business Partner Number of the Foreign Trade Organization

• /SAPSLL/CUHD~FTVBS Business Partner Number of the Legal Unit; is filled exclusively for customs
documents that were created or will be created as part of SAP GTS Customs Management. This field
also replaces entries in table /SAPSLL/CORPAR with PATYP = CUSVBS which will no longer be created.
• SPL screening via TREX is no longer supported; for this reason, value [1E] = “Not Screened / Blocked:
TREX Not Available” of field /SAPSLL/CUHD~STSPL_AGG was replaced by [1A] = „Not Screened /
Blocked“
• Fields from table /SAPSLL/LEGTPR
• Fields from table /SAPSLL/CUHDDAT
• Fields from table /SAPSLL/CUHDSTA
• Processing status and processing progress of a customs declaration are depicted in the following fields
and replace /SAPSLL/CUHDSTA~PROST:
• /SAPSLL/CUHD~CDSTS Processing Status
• /SAPSLL/CUHD~CDPRG Processing Progress
• /SAPSLL/CUHD~WRESP Waiting for Response from Authority
• /SAPSLL/CUHD~ARCHI Archiving Flag
• The field /SAPSLL/CHDSTA~PROVO Previous Document Processing Status has been retired and is
not part of the data migration
• /SAPSLL/CUHD~ZREGNR Registration Number
• Numbers with the following qualifier (field QALCOM) in table /SAPSLL/LEGCOM are migrated to this
field:
• ZREGNR
• SREGNR
• ARCNR
• MRN
• /SAPSLL/CUHD~AREGNR Additional Registration Number
• Numbers with the following qualifier (field QALCOM) in table /SAPSLL/LEGCOM are migrated to this
field:
• AREGNR
• TREGNR
• /SAPSLL/CUHD~SCRNR Scrapping Number
• Numbers with the following qualifier (field QALCOM) in table /SAPSLL/LEGCOM are migrated to this
field:
• SCRNR
• /SAPSLL/CUHD~LRNNO Company-Internal Reference Number
• Numbers with the following qualifier (field QALCOM) in table /SAPSLL/LEGCOM are migrated to this
field:
• LRNNR
• /SAPSLL/CUHD~LCBRF Customs Broker Transaction Number

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
24 PUBLIC SAP Global Trade Services, edition for SAP HANA
 • Numbers with the following qualifier (field QALCOM) in table /SAPSLL/LEGCOM are migrated to this
field:
• SLLCB
• Communication numbers in fields ZRGENR and AREGNR of table /SAPSLL/CUHD are stored with no more
leading zeros. The conversion exit which has been in place for these ones in table /SAPSLL/LEGCOM is
dropped.
• Entries in table /SAPSLL/LEGCOM with qualifier DOCNR are stored in table /SAPSLL/LEGMES with reference
to their messages

Retirement of the following tables:

• /SAPSLL/LEGCOM Customs Document: Communication Numbers

• /SAPSLL/LEGTPR Customs Document Header: Specific Customs Declaration Data
• /SAPSLL/CUHDSTA Customs Document Header: Status
• /SAPSLL/CUHDDAT Customs Document Header: Date Specification

UPD_2_CUIT

Data Migration to table /SAPSLL/CUIT

Data transfer from the following tables:

• /SAPSLL/LEGCOM Customs Document: Communication Numbers

• /SAPSLL/LEGCUS Customs Document: Customs Processing
• /SAPSLL/CUITSTA Customs Document Item: Status
• /SAPSLL/CUITDAT Customs Document Item: Date Specification

What's New

The following fields were added:

• /SAPSLL/CUIT~CDTYP Document Type

• /SAPSLL/CUIT~FTORG Business Partner Number of the Foreign Trade Organization.
• /SAPSLL/CUIT~FTVBS Business Partner Number of the Legal Unit.
• /SAPSLL/CUIT~RPTDA Check Date for Prohibitions and Restrictions.
• SPL screening via TREX is no longer supported; for this reason, value [1E] = “Not Screened / Blocked:
TREX Not Available” of field /SAPSLL/CUHD~STSPL_AGG was replaced by [1A] = „Not Screened /
Blocked“
• Field RPTDA was added and replaces field /SAPSLL/CUIT~RPTDT (Definitive Date as Time Stamp).
• /SAPSLL/CUIT~MREGNR Registration Number from Migration for Special Procedures
• Numbers with the following qualifier (field QALCOM) in table /SAPSLL/LEGCOM are migrated to this
field:
• ZREGNR
• /SAPSLL/CUIT~FDACN FDA Registration Number
• Numbers with the following qualifier (field QALCOM) in table /SAPSLL/LEGCOM are migrated to this
field:
• FDACN

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 25
• Communication numbers in fields MREGNR and FDACN of table /SAPSLL/CUIT are stored with no more
leading zeros. The conversion exit which has been in place for these ones in table /SAPSLL/LEGCOM is
dropped.
• Fields from table /SAPSLL/LEGCUS except the following fields which are not migrated:
• CUBVAL_FLT Customs Assement Base
• CUAVAL_FLT Customs Duty
• EUBVAL_FLT Assessment Base for EU Tax
• EUAVAL_FLT Duty - EU Tax
• STAVAL_FLT Statistical Value
• CUCUR Currency
• EUCUR Currency
• STCUR Currency
• Fields from table /SAPSLL/CUITSTA
• Fields from table /SAPSLL/CUITDAT

Retirement of the following tables:

• /SAPSLL/CUITSTA Customs Document Item: Status

• /SAPSLL/CUITDAT Customs Document Item: Date Specification
• /SAPSLL/LEGCUS Customs Document: Customs Processing

UPD_2_CORCTS

Changes in table /SAPSLL/CORCTS

What's New

• The classification UUID was replaced by the reference number of the classification.
• Field /SAPSLL/CORCTS~GUID_CTSNUM was retired and was replaced by /SAPSLL/CORCTS~CCNGN.
• In the future, field /SAPSLL/CORCTS~CLSTY describes the classification type, for example, [A] = tariff
number, [B] = commodity code, [C] = export control classification number, and so on.

INS_CORCTSC_2_CORCTS

Data Migration to table /SAPSLL/CORCTS

What's New

• The classification UUID was replaced by its reference number /SAPSLL/CORCTS~CCNGN

Retirement of table:

• /SAPSLL/CORCTSC Customs Document Item: Country-Dependent Classification

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
26 PUBLIC SAP Global Trade Services, edition for SAP HANA
INS_CORCTZ_2_LEGATC

Data Migration to table /SAPSLL/LEGATC

What's New

• Fields from table /SAPSLL/CORCTZ were migrated to /SAPSLL/LEGATC

• The classification UUID in /SAPSLL/CORCTZ was replaced by its reference number /SAPSLL/
LEGATC~CCNGN
• The UUID reference to the tariff measure according to field /SAPSLL/CORCTZ~GUID_CTSMAE is dropped.
• The following reference type codes (REFTY) are obsolete:
• 1 Code Number
• 2 General Measure
• 3 Measure Customs Duty Rate
• The following reference type codes (REFTY) are new:
• 5 NCLO-/PGA Code
• 6 Additional Tariff Number

Retirement of table:

• /SAPSLL/CORCTZ Customs Document Item: Status

INS_CORCTZ_2_PRATC

Data Migration to table /SAPSLL/PRATC

What's New

• Fields from table /SAPSLL/CORCTZ were migrated to /SAPSLL/PRATC

• The classification UUID in /SAPSLL/CORCTZ was replaced by its reference number /SAPSLL/
PRATC~CCNGN
• The UUID reference to the tariff measure according to field /SAPSLL/CORCTZ~GUID_CTSMAE is dropped.
• The reference to the product is given by field /SAPSLL/PRATC~GUID_PR. Fields GUID_MOBJ and MOBJT
are not in place.

Retirement of the following tables:

• /SAPSLL/CORCTZ Customs Document Item: Status

INS_LC_CUSB1_2_DTRCUS

Data Migration to table /SAPSLL/DTRCUS

What's New

• Fields from table /SAPSLL/LC_CUSB1 were migrated to /SAPSLL/DTRCUS

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 27
• The legal regulation was dropped
• The reference to the numbering scheme (/SAPSLL/LC_CUSB1~STCTS) was replaced with a reference to
the numbering scheme content (/SAPSLL/DTRCUS~STCCS)
• The classification UUID was kept and additionally the reference number of the classification was added.

Retirement of the following tables:

• /SAPSLL/LC_CUSB1 Customs Processing: Duties for Third Country / Pharmaceuticals

INS_LC_CUSB2_2_DTRPRE

Data Migration to table /SAPSLL/DTRPRE

What's New

• Fields from table /SAPSLL/LC_CUSB2 were migrated to /SAPSLL/DTRPRE

• The legal regulation was dropped
• The reference to the numbering scheme (/SAPSLL/LC_CUSB2~STCTS) was replaced with a reference to
the numbering scheme content (/SAPSLL/DTRPRE~STCCS)
• The classification UUID was kept and additionally the reference number of the classification was added.

Retirement of the following tables:

• /SAPSLL/LC_CUSB2 Customs Processing: Duties for Preference

UPD_2_DPDATA

Changes in table /SAPSLL/TDPCMB and /SAPSLL/DPDATA

What's New

• The data proposal fields G_STAWN (UUID of the commodity code) and G_IMPCN_UUID (UUID of the tariff
number) are obsolete and are replaced by the field combinations I_STAWN and I_IMPCN, which represent
the classification numbers directly.
• These changes are reflected in the data proposal schemes where the fields named above where replaced
by the new ones.

UPD_2_CUPED

Changes in table /SAPSLL/CUPED

What's New

• The conversion exit on field /SAPSLL/CUPED~REGNR is not in place any more which added/removed
leading zeros. As a consequence, leading zeros will get significant for the registration number.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
28 PUBLIC SAP Global Trade Services, edition for SAP HANA
UPD_2_TSHD

Changes in table /SAPSLL/TSHD

What's New

• The conversion exit on field /SAPSLL/TSHD~REGNR is not in place any more which added/removed leading
zeros. As a consequence, leading zeros will get significant for the registration number.

UPD_2_TSCHD

Changes in table /SAPSLL/TSCHD

What's New

• The conversion exit on field /SAPSLL/TSCHD~REGNR is not in place any more which added/removed
leading zeros. As a consequence, leading zeros will get significant for the registration number.

UPD_2_TSPED

Changes in table /SAPSLL/TSPED

What's New

• The conversion exit on field /SAPSLL/TSPED~REGNR is not in place any more which added/removed
leading zeros. As a consequence, leading zeros will get significant for the registration number.

UPD_2_LICHD

Changes in table /SAPSLL/LICHD

What's New

• The Valid From and Valid To time stamps (/SAPSLL/LICHD~DATAB and /SAPSLL/LICHD~DATBI) were
transferred to data fields (SAPSLL/LICHD~VALFR and /SAPSLL/LICHD~VALTO).

INS_LCLICW_2_LICHDSC

Data Migration to table /SAPSLL/LICHDSC

What's New

• Fields from table /SAPSLL/LCLICW were migrated to /SAPSLL/LICHDSC

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 29
• The UUID reference to commodity code according to field /SAPSLL/LCLICW~GUID_CTS is dropped and
replaced by the direct reference to the commodity code (/SAPSLL/LICHDSC-CCNGN).

Retirement of the following tables:

• /SAPSLL/LCLICW Licences – Commodity Codes

INS_LCLICI_2_LICHDTN

Data Migration to table /SAPSLL/LICHDTN

What's New

• Fields from table /SAPSLL/LCLICI were migrated to /SAPSLL/LICHDTN

• The UUID reference to commodity code according to field /SAPSLL/LCLICWN~GUID_CTS is dropped and
replaced by the direct reference to the commodity code (/SAPSLL/LICHDTN-CCNGN).

Retirement of the following tables:

• /SAPSLL/LCLICI Licences – Import Code Numbers

INS_LCLICN_2_LICHDCP

Data Migration to table /SAPSLL/LICHDCP

What's New

• Fields from table /SAPSLL/LCLICN were migrated to /SAPSLL/LICHDCP

• The UUID reference to commodity code according to field /SAPSLL/LCLICN~GUID_CTS is dropped and
replaced by the direct reference to the commodity code (/SAPSLL/LICHDCP-CCNGN).

Retirement of the following tables:

• /SAPSLL/LCLICN Licences – CAP Numbers

INS_LCLICWF_2_LICHDSCF

Data Migration to table /SAPSLL/LICHDSCF

What's New

• Fields from table /SAPSLL/LCLICWF were migrated to /SAPSLL/LICHDSCF

• The UUID reference to commodity code according to field /SAPSLL/LCLICNWF~GUID_CTS is dropped and
replaced by the direct reference to the commodity code (/SAPSLL/LICHDSCF-CCNGN).

Retirement of the following tables:

• /SAPSLL/LCLICN Licences – Finished Products

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
30 PUBLIC SAP Global Trade Services, edition for SAP HANA
UPD_2_LCLICPT

Changes in table /SAPSLL/LICHDPT

What's New

• The UUID reference to commodity code according to field /SAPSLL/LCLICPT~GUID_CTSNUM is dropped

and replaced by the direct reference to the commodity code (/SAPSLL/LICHDPT-CCNGN).

UPD_2_LICHDPTM

Changes in table /SAPSLL/LICHDPTM

What's New

• The UUID reference to commodity code according to field /SAPSLL/LCLICPTM~GUID_CTSNUM is dropped

and replaced by the direct reference to the commodity code (/SAPSLL/LICHDPTM-CCNGN).

INS_PRCTS_2_PRCLS

Data Migration to table /SAPSLL/PRCLS

What's New

• Fields from table /SAPSLL/PRCTS were migrated to /SAPSLL/PRCLS

• The Valid From and Valid To time stamps (/SAPSLLPRCTS~DATAB and /SAPSLL/PRCTS~DATBI) were
transferred to data fields (SAPSLL/PRCLS~DATAB and /SAPSLL/PRCLS~DATBI).
• The UUID reference to commodity code according to field /SAPSLL/PRCTS~GUID_CTS is dropped and
replaced by the direct reference to the commodity code (/SAPSLL/PRCLS-CCNGN).

Retirement of the following tables:

• /SAPSLL/PRCTS Product Master - Global Customs Tariff Numbers

INS_PRCTSC_2_PRCLS

Data Migration to table /SAPSLL/PRCLS

What's New

• The country dependency of a classification in a numbering scheme is obsolete.

• Fields from table /SAPSLL/PRCTSC were migrated to /SAPSLL/PRCLS
• The Valid From and Valid To time stamps (/SAPSLLPRCTS~DATAB and /SAPSLL/PRCTS~DATBI) were
transferred to data fields (SAPSLL/PRCLS~DATAB and /SAPSLL/PRCLS~DATBI).
• The UUID reference to commodity code according to field /SAPSLL/PRCTS~GUID_CTS is dropped and
replaced by the direct reference to the commodity code (/SAPSLL/PRCLS-CCNGN).

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 31
Retirement of the following tables:

• /SAPSLL/PRCTSC Product Master - Country-Dependent Customs Tariff Numbers

INS_PRACM_2_PRACA

Data Migration to table /SAPSLL/PRACA

What's New

• Fields from table /SAPSLL/PRACM were migrated to /SAPSLL/PRACA

Retirement of the following tables:

• /SAPSLL/PRACM Product Master - Global Customs Tariff Numbers

INS_CTSNZR_2_CTSACN

Data Migration to table /SAPSLL/CTSACN

What's New

• Fields from table /SAPSLL/CTSNZR were migrated to /SAPSLL/CTSACN

Retirement of the following tables:

• /SAPSLL/CTSNZR Customs Tariff Numbers: Number-Custom Code Relation

INS_CTSNTR_2_CTSRNT

Data Migration to table /SAPSLL/CTSRNT

What's New

• Fields from table /SAPSLL/CTSNTR were migrated to /SAPSLL/CTSRNT

Retirement of the following tables:

• /SAPSLL/CTSNZR Customs Tariff Nos.: Number-Text Relation

INS_CTSDMA_2_CTSDCN

Data Migration to table /SAPSLL/CTSDCN

What's New

• Fields from table /SAPSLL/CTSDMA were migrated to /SAPSLL/CTSDCN

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
32 PUBLIC SAP Global Trade Services, edition for SAP HANA
Retirement of the following tables:

• /SAPSLL/CTSDMA Assignment of Customs Duty Rate Condition to Tariff Number

INS_CTSMAE_2_CTSACT

Data Migration to table /SAPSLL/CTSACT

What's New

• Fields from table /SAPSLL/CTSMAE were migrated to /SAPSLL/CTSACT

Retirement of the following tables:

• /SAPSLL/CTSMAE Mapping of Agency Code (e.g. Authority) to Numbers

INS_CTSNUM_2_CTSNR

Data Migration to table /SAPSLL/CTSNR

What's New

• Fields from table /SAPSLL/CTSNUM were migrated to /SAPSLL/CTSNR

Retirement of the following tables:

• /SAPSLL/CTSNUM Customs Tariff Number

INS_CTSNUMT_2_CTSNRT

Data Migration to table /SAPSLL/CTSNRT

What's New

• Fields from table /SAPSLL/CTSNUMT were migrated to /SAPSLL/CTSNRT

Retirement of the following tables:

• /SAPSLL/CTSNUMT Text for Customs Tariff No.

INS_CTSNUMC_2_CTSNR

Data Migration to table /SAPSLL/CTSNR

What's New

• Fields from table /SAPSLL/CTSNUMC were migrated to /SAPSLL/CTSNR

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 33
Retirement of the following tables:

• /SAPSLL/CTSNUMC Country-Specific Customs Tariff No.

INS_CTSNUMCT_2_CTSNRT

Data Migration to table /SAPSLL/CTSNRT

What's New

• Fields from table /SAPSLL/CTSNUMCT were migrated to /SAPSLL/CTSNRT

Retirement of the following tables:

• /SAPSLL/CTSNUMCT Text for Country-Specific Customs Tariff No.

INS_CTSGEN_2_CTSHR

Data Migration to table /SAPSLL/CTSHR

What's New

• Fields from table /SAPSLL/CTSGEN were migrated to /SAPSLL/CTSHR

Retirement of the following tables:

• /SAPSLL/CTSGEN Generic Part of Customs Tariff No.

INS_CTSGENT_2_CTSHRT

Data Migration to table /SAPSLL/CTSHRT

What's New

• Fields from table /SAPSLL/CTSGENT were migrated to /SAPSLL/CTSHRT

Retirement of the following tables:

• /SAPSLL/CTSGENT Text for Generic Customs Tariff No.

INS_CTSATR_2_CTSRTT

Data Migration to table /SAPSLL/CTSRTT

What's New

• Fields from table /SAPSLL/CTSATR were migrated to /SAPSLL/CTSRTT

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
34 PUBLIC SAP Global Trade Services, edition for SAP HANA
Retirement of the following tables:

• /SAPSLL/CTSATR Customs Tariff Numbers: Additional Text References

INS_CTSTXT_2_CTSTXH

Data Migration to table /SAPSLL/CTSTXH

What's New

• Fields from table /SAPSLL/CTSTXT were migrated to /SAPSLL/CTSTXH

Retirement of the following tables:

• /SAPSLL/CTSTXT Texts for Customs Tariff Numbering System (Rule Set)- Header

INS_CTSTXTT_2_CTSTXL

Data Migration to table /SAPSLL/CTSTXL

What's New

• Fields from table /SAPSLL/CTSTXTT were migrated to /SAPSLL/CTSTXL

Retirement of the following tables:

• /SAPSLL/CTSTXTT Texts for Customs Tariff Numbering System (Rule Set)

INS_CTSFND_2_CTSDFN

Data Migration to table /SAPSLL/CTSDFN

What's New

• Fields from table /SAPSLL/CTSFND were migrated to /SAPSLL/CTSDFN

Retirement of the following tables:

• /SAPSLL/CTSFND Footnote Definition

INS_CTSFNA_2_CTSAFN

Data Migration to table /SAPSLL/CTSAFN

What's New

• Fields from table /SAPSLL/CTSFNA were migrated to /SAPSLL/CTSAFN

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 35
Retirement of the following tables:

• /SAPSLL/CTSFNA Footnote Assignment

INS_CTSDMD_2_CTSDCD

Data Migration to table /SAPSLL/CTSDCD

What's New

• Fields from table /SAPSLL/CTSDMD were migrated to /SAPSLL/CTSDCD

Retirement of the following tables:

• /SAPSLL/CTSDMD Customs Duty Rate Conditions Definition

INS_CTSMND_2_CTSTMD

Data Migration to table /SAPSLL/CTSTMD

What's New

• Fields from table /SAPSLL/CTSMND were migrated to /SAPSLL/CTSTMD

Retirement of the following tables:

• /SAPSLL/CTSMND Measure Determination

INS_CTSMNDC_2_CTSTMDC

Data Migration to table /SAPSLL/CTSTMDC

What's New

• Fields from table /SAPSLL/CTSMNDC were migrated to /SAPSLL/CTSTMDC

Retirement of the following tables:

• /SAPSLL/CTSMNDC Measure Determination: Excluded Countries

INS_CTSMNDP_2_CTSTMDP

Data Migration to table /SAPSLL/CTSTMDP

What's New

• Fields from table /SAPSLL/CTSMNDP were migrated to /SAPSLL/CTSTMDP

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
36 PUBLIC SAP Global Trade Services, edition for SAP HANA
Retirement of the following tables:

• /SAPSLL/CTSMNDP Measure Determination: Excluded Period

INS_CTSTNA_2_CTSTNAR

Data Migration to table /SAPSLL/CTSTNAR

What's New

• Fields from table /SAPSLL/CTSTNA were migrated to /SAPSLL/CTSTNAR

Retirement of the following tables:

• /SAPSLL/CTSTNA Attribute for Customs Tariff Number

INS_CTSMAC_2_CTSTMC

Data Migration to table /SAPSLL/CTSTMC

What's New

• Fields from table /SAPSLL/CTSMAC were migrated to /SAPSLL/CTSTMC

Retirement of the following tables:

• /SAPSLL/CTSMAC Measure Condition

INS_CTSMAI_2_CTSTMI

Data Migration to table /SAPSLL/CTSTMI

What's New

• Fields from table /SAPSLL/CTSMAI were migrated to /SAPSLL/CTSTMI

Retirement of the following tables:

• /SAPSLL/CTSMAI Measure Type ID

INS_CTSADD_2_CTSADC

Data Migration to table /SAPSLL/CTSADC

What's New

• Fields from table /SAPSLL/CTSADD were migrated to /SAPSLL/CTSADC

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 37
Retirement of the following tables:

• /SAPSLL/CTADD Additional Code

INS_LC_CUSXC_2_DTREXC

Data Migration to table /SAPSLL/DTREXC

What's New

• Fields from table /SAPSLL/LC_CUSXC were migrated to /SAPSLL/DTREXC

Retirement of the following tables:

• /SAPSLL/LC_CUSXC GTS: Customs Management: Toll Cat: Customs Tolls: Exclusion

INS_CDWLM_2_CDWLMEA

Data Migration to table /SAPSLL/CDWLMEA

What's New

• Fields from table /SAPSLL/CDWLM were migrated to /SAPSLL/CDWLMEA

Retirement of the following tables:

• /SAPSLL/CDWLM Worklist for Determination Rules

INS_CTSACD_2_CTSACC

Data Migration to table /SAPSLL/CTSACC

What's New

• Fields from table /SAPSLL/CTSACD were migrated to /SAPSLL/CTSACC

Retirement of the following tables:

• /SAPSLL/CTSACD Action Code Definition

INS_CTSTRR_2_CTSTAXR

Data Migration to table /SAPSLL/CTSTAXR

What's New

• Fields from table /SAPSLL/CTSTRR were migrated to /SAPSLL/CTSTAXR

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
38 PUBLIC SAP Global Trade Services, edition for SAP HANA
Retirement of the following tables:

• /SAPSLL/CTSTRR Tax Refund Rates for Tariff Number

INS_WLTRRT_2_WLTAXR

Data Migration to table /SAPSLL/WLTAXR

What's New

• Fields from table /SAPSLL/WLTRRT were migrated to /SAPSLL/WLTAXR

Retirement of the following tables:

• /SAPSLL/WLTRRT Worklist of Tax Refund Rates

2.1.1.4 Conversion Tasks for Preference Management

UPD_2_PRFPMRC

Changes in Table /SAPSLL/PRFPMRC

What's New

• The classification UUID was replaced by the reference number of the classification.
• Field /SAPSLL/PRFPMRC~GUID_HTSNUM was retired and was replaced by /SAPSLL/PRFPMRC~CCNGN.

INS_PRPRFS_2_PRPRES

Data Migration to table /SAPSLL/PRPRES

• The UUID reference to the classification code was dropped (/SAPSLL/PRPRFS~GUID_HTSNUM) without
any replacement. Also, the validity period defined in fields /SAPSLL/PRPRFS~DATAB and SAPSLL/
PRPRFS~DATBI was dropped without replacement. The special requirements are now time-independent.

Retirement of table:

• /SAPSLL/PRPRFS SLL: Product Master: Preference Data: Special Requirements

INS_PRPRFC_2_PRPREC

Data Migration to table /SAPSLL/PRPREC

• The UUID reference to the classification code is no longer stored in field /SAPSLL/PRPRFC~GUID_HTSNUM,
but in /SAPSLL/PRPREC~GUID_PRCLS. Also, the timestamps for the validity period (/SAPSLL/

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 39
 PRPRFC~DATAB and /SAPSLL/PRPRFC~DATBI) have been converted to date fields (/SAPSLL/
PRPREC~DATAB and /SAPSLL/PRPREC~DATBI).

Retirement of table:

• /SAPSLL/PRPRFC SLL: Product Master: Preference Data: Confirm. Pref. Reqmts

UPD_2_PRFPM

Changes in Table /SAPSLL/PRFPM

What's New

• The classification UUID was replaced by the reference number of the classification.
• Field /SAPSLL/PRFPM~GUID_HTSNUM was retired and was replaced by /SAPSLL/PRFPM~CCNGN.

UPD_2_PRFPMRA

Changes in Table /SAPSLL/PRFPMRA

What's New

• The classification UUID was replaced by the reference number of the classification.
• Field /SAPSLL/PRFPMRA~GUID_HTSNUM was retired and was replaced by /SAPSLL/PRFPMRA~CCNGN.

UPD_2_PRVDREL

Changes in Table /SAPSLL/PRVDREL

What's New

• The field /SAPSLL/PRVDREL~REQUEST_RELEVANCE has been added. Data from field /SAPSLL/
PRVDREL~PRREL was moved to /SAPSLL/PRVDREL~REQUEST_RELEVANCE with the following logic:
If PRREL is set to "X" then the request relevance is set to "-". Otherwise the value 'D' is set.
• The field /SAPSLL/PRVDREL~GOODS_RETENTION_PERIOD was added. No data migration necessary as
this is used in the new LTSD management process.

UPD_2_PREBDOC

Changes in Table /SAPSLL/PREBDOC

What's New

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
40 PUBLIC SAP Global Trade Services, edition for SAP HANA
 • The field /SAPSLL/PREBDOC~PARTNER_ADRNR_REFTYPE has been added. The field is set with the
following logic:
If the Address Number (/SAPSLL/PREBDOC~PARTNER_ADRNR) exists in table ADRV with
ADRV~ADDR_GROUP = “SL03”, ADRV~APPL_TABLE = “SLL_PREBDO”, ADRV~APPL_FIELD = “ADRNR”
and ADRV~OWNER = “X”, then PARTNER_ADRNR_REFTYPE is set to "3" (Document Address). Otherwise,
the value "1" (Partner Default Address) is set.

UPD_2_DOOHD

Changes in Table /SAPSLL/DOOHD

What's New

• The field /SAPSLL/DOOHD~PARTNER_ADRNR_REFTYPE has been added. The field is set with the following
logic:
If the Address Number (/SAPSLL/DOOHD~PARTNER_ADRNR) exists in table ADRV with
ADRV~ADDR_GROUP = “SL03”, ADRV~APPL_TABLE = “SLL_PREBDO”, ADRV~APPL_FIELD = “ADRNR”
and ADRV~OWNER = “X”, then PARTNER_ADRNR_REFTYPE is set to "3" (Document Address). Otherwise,
the value "1" (Partner Default Address) is set.

UPD_2_RIRHD

Changes in Table /SAPSLL/RIRHD

What's New

• The field /SAPSLL/RIRHD~LTSD_RECEIVER_ADRNR_REFTYPE has been added. The field is set with the
following logic:
If the Address Number (/SAPSLL/RIRHD~LTSD_RECEIVER_ADRNR) exists in table ADRV with
ADRV~ADDR_GROUP = “SL03”, ADRV~APPL_TABLE = “SLL_PREBDO”, ADRV~APPL_FIELD = “ADRNR”
and ADRV~OWNER = “X”, then LTSD_RECEIVER_ADRNR_REFTYPE is set to "3" (Document Address).
Otherwise the value "1" (Partner Default Address) is set.

UPD_2_LLS_CUSTLTSD_D

Changes in Table /SAPSLL/LLS_CUSTLTSD_D

What's New

• The field LLS_CUSTLTSD_D~LTSDRECEIVERADDRREFERENCETYPE has been added. The field is set with
the following logic:
If the Address Number (LLS_CUSTLTSD_D~ LTSDRECEIVERADDRESSID) exists in table ADRV with
ADRV~ADDR_GROUP = “SL03”, ADRV~APPL_TABLE = “SLL_PREBDO”, ADRV~APPL_FIELD = “ADRNR”
and ADRV~OWNER = “X”, then LTSDRECEIVERADDRREFERENCETYPE is set to "3" (Document Address).
Otherwise the value "1" (Partner Default Address) is set.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 41
UPD_2_LLS_REISRSN_D

Changes in Table /SAPSLL/LLS_REISRSN_D

What's New

• The field LLS_REISRSN_D~LTSDRECEIVERADDRREFERENCETYPE has been added. The field is set with
the following logic:
If the Address Number (LLS_REISRSN_D~LTSDRECEIVERADDRESSID) exists in table ADRV with
ADRV~ADDR_GROUP = “SL03”, ADRV~APPL_TABLE = “SLL_PREBDO”, ADRV~APPL_FIELD = “ADRNR”
and ADRV~OWNER = “X”, then LTSDRECEIVERADDRREFERENCETYPE is set to "3" (Document Address).
Otherwise, the value "1" (Partner Default Address) is set.

2.1.1.5 Conversion Tasks for Intrastat

UPD_2_ALRG01

Reduction of Activation Options

The activation options of the legal regulations for Intrastat are reduced to the following options:

• [ ] = Not Active
• [1] = Active

This applies to the following table fields:

• /SAPSLL/ALRG01~ERAC1: Activation of Legal Regulation for Receipts

• /SAPSLL/ALRG01~ERAC2: Activation of Legal Regulation for Dispatches

UPD_2_ALRG02

Reduction of Activation Options

The activation options of the legal regulations for Intrastat are reduced to the following options:

• [ ] = Not Active
• [1] = Active

This applies to the following table fields:

• /SAPSLL/ALRG02~ERAC1: Activation of Legal Regulation for Receipts

• /SAPSLL/ALRG02~ERAC2: Activation of Legal Regulation for Dispatches

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
42 PUBLIC SAP Global Trade Services, edition for SAP HANA
UPD_2_ALRG03

Reduction of Activation Options

The activation options of the legal regulations for Intrastat are reduced to the following options:

• [ ] = Not Active
• [1] = Active

This applies to the following table fields:

• /SAPSLL/ALRG03~ERAC1: Activation of Legal Regulation for Receipts

• /SAPSLL/ALRG03~ERAC2: Activation of Legal Regulation for Dispatches

UPD_2_ALRG11

Reduction of Activation Options

The activation options of the legal regulations for Intrastat are reduced to the following options:

• [ ] = Not Active
• [1] = Active

This applies to the following table fields:

• /SAPSLL/ALRG11~ERAC1: Activation of Legal Regulation for Receipts

• /SAPSLL/ALRG11~ERAC2: Activation of Legal Regulation for Dispatches

UPD_2_ALRG12

Reduction of Activation Options

The activation options of the legal regulations for Intrastat are reduced to the following options:

• [ ] = Not Active
• [1] = Active

This applies to the following table fields:

• /SAPSLL/ALRG12~ERAC1: Activation of Legal Regulation for Receipts

• /SAPSLL/ALRG12~ERAC2: Activation of Legal Regulation for Dispatches

UPD_2_ALRG13

Reduction of Activation Options

The activation options of the legal regulations for Intrastat are reduced to the following options:

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 43
• [ ] = Not Active
• [1] = Active

This applies to the following table fields:

• /SAPSLL/ALRG13~ERAC1: Activation of Legal Regulation for Receipts

• /SAPSLL/ALRG13~ERAC2: Activation of Legal Regulation for Dispatches

Caution

 Note

The namespace of the tables was changed from /ECRS/ to /ECRG/ and the data in the tables in the /
ECRS/ namespace was copied to /ECRG/.

UPD_2_RPIT

Data Migration to table /ECRG/RPIT

Data is transferred from the following table:/ECRG/RPLI: Log Item Import from Worklist

The following fields were added:

• /ECRG/RPIT~ICRTY: Creation Type

• /ECRG/RPIT~DOTYP: Document Type
• /ECRG/RPIT~DONUM: Document Number
• /ECRG/RPIT~DOITM: Document Item Number
• /ECRG/RPIT~RDTYP: Reference Document Type
• /ECRG/RPIT~RDNUM: Reference Document Number
• /ECRG/RPIT~RDITM: Reference Document Item Number
• /ECRG/RPIT~LOGSY: Logical System

The following field is initialized: /ECRG/RPIT~ITNUM: Item Number

The following table is no longer used: /ECRG/RPLI: Log Item Import from Worklist

UPD_2_RPIC

Data Migration to table /ECRG/RPIC

Data is transferred from the following table: /ECRG/RPLI: Log Item Import from Worklist

The following fields were added:

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
44 PUBLIC SAP Global Trade Services, edition for SAP HANA
 • /ECRG/RPIC~ICRTY: Creation Type
• /ECRG/RPIC~DOTYP: Document Type
• /ECRG/RPIC~DONUM: Document Number
• /ECRG/RPIC~DOITM: Document Item Number
• /ECRG/RPIC~RDTYP: Reference Document Type
• /ECRG/RPIC~RDNUM: Reference Document Number
• /ECRG/RPIC~RDITM: Reference Document Item Number
• /ECRG/RPIC~LOGSY: Logical System

The following field is initialized: /ECRG/RPIT~ITNUM: Item Number

The following table is no longer used: /ECRG/RPLI: Log Item Import from Worklist

2.1.1.6 Conversion of Customizing

Due to the Introduction of the Numbering Scheme Content, the following Customizing Tables have been
replaced:

Conversion of Customizing
Deprecated Replacement Description of Replacement

/SAPSLL/TCOTS /SAPSLL/TCOCT Numbering Scheme Content

/SAPSLL/TCOTST /SAPSLL/TCOCTT Description of Numbering Scheme

Content

/SAPSLL/TCOTS /SAPSLL/TCOCA Activation of Numbering Scheme

Content

/SAPSLL/TCOTS /SAPSLL/TCONS Definition of Numbering Scheme

/SAPSLL/TCOTST /SAPSLL/TCONST Description of Numbering Scheme

/SAPSLL/TCOTS /SAPSLL/TNSETD Number Set Definition

/SAPSLL/TCOTST /SAPSLL/TNSETDT Description Number Set

/SAPSLL/TCOTSA /SAPSLL/TCOCTA Structure of Numbering Scheme

Content

/SAPSLL/TCOTSAT /SAPSLL/TCOCTAT Structure of Numbering Scheme

Content - Description

/SAPSLL/TCOTSB /SAPSLL/TCOCTB Definition Alternative No. Scheme

Content for Data Upload

/SAPSLL/TCOTSK /SAPSLL/TCOCTK Definition of Government Agency Code

/SAPSLL/TCOTSKT /SAPSLL/TCOCTKT Government Agency Code - Description

/SAPSLL/TCOTSZ /SAPSLL/TCOCTZ Assignment of Additional Schemes to

Numbering Scheme Content

/SAPSLL/TCOPGC /SAPSLL/TCTPGC PGA Program Codes

/SAPSLL/TCOPGCT /SAPSLL/TCTPGCT PGA Program Codes - Name

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 45
Deprecated Replacement Description of Replacement

/SAPSLL/TCOPCG /SAPSLL/TCTPCG Grouping of PGA Program Codes

/SAPSLL/TCOPCGT /SAPSLL/TCTPCGT Grouping of PGA Program Codes -

Name

/SAPSLL/TCOPCGA /SAPSLL/TCTPCGA Assignment of Program Code to

Grouping

/SAPSLL/TCOPRC /SAPSLL/TCTPRC PGA Process Codes

/SAPSLL/TCOPRCT /SAPSLL/TCTPRCT PGA Process Codes - Description

/SAPSLL/TCODCD /SAPSLL/TCTDCD PGA Disclaimer Code

/SAPSLL/TCODCDT /SAPSLL/TCTDCDT PGA Disclaimer Codes - Description

/SAPSLL/TCTSMS /SAPSLL/TCTSMC Measure Content

/SAPSLL/TCTSMST /SAPSLL/TCTSMCT Measure Content - Name

/SAPSLL/TCTSMS /SAPSLL/TCTSMCA Activation Measure Content

/SAPSLL/TCOTINC /SAPSLL/TCTIN Chapter Restriction During Number

Upload

/SAPSLL/TCOTNA /SAPSLL/TCTNA Tariff Number Attributes Definition

/SAPSLL/TCOTNAT /SAPSLL/TCTNAT Tariff Number Attributes Definition-

Name

/SAPSLL/LC_CUSM /SAPSLL/TEDTM Mapping External Duty Types to Internal

Duty Types

/SAPSLL/TLC_CRUL /SAPSLL/TDTRCAC Define External Calculation Codes for

No. Scheme Content

/SAPSLL/TLC_CRUT /SAPSLL/TDTRCACT Description for External Calculation

Code

/SAPSLL/TCOTNV /SAPSLL/TCTNAV Values of Tariff Number Attributes

/SAPSLL/TCOTNVT /SAPSLL/TCTNAVT Values for Tariff Number Attributes -

Description

/SAPSLL/CTYGPA /SAPSLL/CTYGRA Assign Country to Country Group

2.1.2 BAdIs

Changes to the data model for SAP GTS, edition for SAP HANA have effects on existing Business Add-Ins
(BAdIs). The BAdI compatibility mode ensures that BAdI implementations can be consumed with minimal
changes after completing the technical upgrade. Parameters of BAdI methods or parts of them are filled even
when the underlying DDIC tables or table fields are invalid. This affects BAdI methods that reference the
following DDIC structures:

• /SAPSLL/CUHD_OBJ_S
• /SAPSLL/LCLIC_OBJ_S
• /SAPSLL/PR_OBJ_S.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
46 PUBLIC SAP Global Trade Services, edition for SAP HANA
For an overview of changes to the data model, see Main Data Tables [page 57].

Note the following restrictions:

• The primary key (for example, a Globally Unique Identifier GUID) of a DDIC table that has become invalid
owing to the revised data model cannot be reconstructed. You must change your BAdI implementation as
far as you have implemented corresponding access.
• The GUID reference to a classification has been replaced by its reference number. Updating the numbering
schema content, for example, by using the upload function or exchanging numbering schema content
could lead to access using the GUID reference resulting in no result or an incorrect one. Adjust the program
logic of your BAdI implementation by exclusively using the classification reference number for access.

The BAdI definitions in compatibility mode are deactivated for a follow-on release and are no longer called. We
therefore recommend a timely migration of the BAdI implementations to corresponding new BAdI definitions.
These successor BAdIs replace the previous BAdIs; they exclusively provide the currently valid view of the data
model.

Create an implementation for the corresponding successor BAdI and copy the logic of your previous BAdI
implementations. The names of the BAdI methods and the method parameters are kept the same. Also
implement empty methods.

For classic BAdIs, kernel-based successor BAdIs are available. The kernel-based BAdIs do not result from the
BAdI migration, so the implementation must also be copied.

Note that as soon as a successor BAdI is implemented and activated, only this one can be called at runtime.

You can manage the BAdIs with compatibility mode or their implementations by using transactions SE18 and
SE19. You can also access successor BAdIs through the IMG Implementation Guide.

The following contains listed details of the individual BAdIs for each application area:

BAdI for General Settings [page 47]

BAdIs for Compliance Management [page 48]

BAdIs for Customs Management [page 50]

BAdIs for Preference Management [page 55]

BAdIs for Intrastat [page 55]

2.1.2.1 BAdI for General Settings

Old BAdI New BAdI

/SAPSLL/BADI_EXT_PRD /SAPSLL/BADI_EXT_PRD_N

[Obsolete] Data Backup from External Applications in Cus- Data Backup from External Tables in Customer-Defined Ta-
tomer-Defined Tables bles

Enhancement Spot: /SAPSLL/ES_BADI_EXT_PRD

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 47
2.1.2.2 BAdIs for Compliance Management

Old BAdI New BAdI

/SAPSLL/BADI_CDOC_EX_UI_CON /SAPSLL/BADI_CDOC_EX_UI_CON_N

[Obsolete] Interface Control when Linking External Applica- Interface Control when Linking External Application to Cus-
tion to Customs Document toms Document

Enhancement Spot: /SAPSLL/ES_BADI_CDOC_EXT

Old BAdI New BAdI

/SAPSLL/BADI_CUHD_BOM /SAPSLL/BADI_CDOC_BOM_N

[Obsolete] Explosion of Document-Based BOMs Explosion of Document-Based BOMs

Enhancement Spot: /SAPSLL/ES_CDOC_REL

Old BAdI New BAdI

/SAPSLL/CUHD_RELEASE /SAPSLL/BADI_CDOC_REL_N

[Obsolete] Release Blocked Documents Release of Blocked Documents

Enhancement Spot: /SAPSLL/ES_CDOC_REL

New BAdI New BAdI

/SAPSLL/BADI_ECMC_ELANK2 /SAPSLL/BADI_ECMC_ELANK2_N

[Obsolete] Mapping for Calling Webservice ELANK2 Mapping to Call Web Service ELANK2

Enhancement Spot: /SAPSLL/ECMC_OUT

New BAdI New BAdI

/SAPSLL/LCLIC_PROP /SAPSLL/BADI_LCLIC_PROP_N

[Obsolete] Default when Entering Licenses Default Data when Entering and Processing Licenses

Enhancement Spot: /SAPSLL/ES_LCLIC_PROP

 Note

SAP GTS, edition for SAP HANA 2023 is the first product version that allows a co-deployment.

For this reason, the activities you must perform to enable a co-deployment are listed below.

Changes to the data model for SAP GTS, edition for SAP HANA have effects on existing Business Add-Ins
(BAdIs). Parameters of BAdI methods or parts of them are exchanged. This affects BAdI methods that
reference the following DDIC structures:

• /SAPSLL/LCLIC_OBJ_S
• /SAPSLL/CLIC_OBJ_S

For an overview of changes to the data model, see the chapter Main Data Tables.

The implementations of the following BAdIs need to be adopted.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
48 PUBLIC SAP Global Trade Services, edition for SAP HANA
 BAdI

/SAPSLL/LCC_DOCUMENT

Legal Control: Synchronous Check

Change

Method LICENSES_GET: Change of reference type for parameter IT_LCLIC to /SAPSLL/LICHD_T

BAdI

/SAPSLL/CUHD_RELEASE

[Obsolete] Release Blocked Documents

Change

Method RELEVANT_LICENSES_GET: Change of reference type for parameter IT_LCLIC to /SAPSLL/LICHD_T

BAdI

/SAPSLL/CUHD_RELEASE_N

Release Blocked Documents

Change

Method RELEVANT_LICENSES_GET: Change of reference type for parameter IT_LCLIC to /SAPSLL/LICHD_T

BAdI

/SAPSLL/ITAR_TRACK_ES

[Obsolete] ITAR Tracking: Value Calculation

Enhancement Spot

/SAPSLL/ITAR_TRACK_ES

Change

Method SET_PR_VALUE: Change of reference type for parameter:

• IS_LCLIC to /SAPSLL/LICHD
• IS_LCLICA to /SAPSLL/LICHDA
• IS_LCLICRQL to /SAPSLL/LICHDRQL
• CS_LCLICRVL to /SAPSLL/LICHDRQL

BAdI

/SAPSLL/ITAR_TRACK_ES_N

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 49
BAdI

Determination of Authorizations

Enhancement Spot

/SAPSLL/ITAR_TRACK_ES

Change

Method SET_PR_VALUE: Change of reference type for parameter:

• IS_LCLIC to /SAPSLL/LICHD
• IS_LCLICA to /SAPSLL/LICHDA
• IS_LCLICRQL to /SAPSLL/LICHDRQL
• CS_LCLICRVL to /SAPSLL/LICHDRQL

BAdI

/SAPSLL/BADI_LCLIC_PROP_N

Default Data when Entering and Processing Licenses

Enhancement Spot

/SAPSLL/ES_LCLIC_PROP

Change

Method LICENSE_DATA_PROPOSE: Change of reference type for parameter CS_OBJ to /SAPSLL/LICHD_OBJ_S

BAdI

/SAPSLL/LCLIC_PROP

[Obsolete] Default when Entering Licenses

Change

Method LICENSE_DATA_PROPOSE: Change of reference type for parameter CS_OBJ to /SAPSLL/LICHD_OBJ_S

2.1.2.3 BAdIs for Customs Management

Old BAdI New BAdI

/SAPSLL/BADI_BRKR_MNTRG_EXPRT /SAPSLL/BADI_BRKR_MNTRG_EXP_N

[Obsolete] Monitor Communication with a Customs Broker Monitor Communication with a Customs Broker During Ex-
During Export port

Enhancement Spot: /SAPSLL/ES_BADI_BRKR_COMM

Old BAdI New BAdI

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
50 PUBLIC SAP Global Trade Services, edition for SAP HANA
 Old BAdI New BAdI

/SAPSLL/BADI_BRKR_MNTRG_IMPRT /SAPSLL/BADI_BRKR_MNTRG_IMP_N

[Obsolete] Monitor Communication with a Customs Broker Monitor Communication with a Customs Broker During Im-
During Export port

Enhancement Spot: /SAPSLL/ES_BADI_BRKR_COMM

Old BAdI New BAdI

/SAPSLL/BADI_CDOC_COPY /SAPSLL/BADI_CDOC_COPY_N

Copy Data Between Documents in Manual Procedure Transi-

[Obsolete] Copy External Data Between Customs Declara-
tion
tion and Customs Shipment

Enhancement Spot: /SAPSLL/ES_BADI_CDOC_COPY

Old BAdI New BAdI

/SAPSLL/BADI_CDOC_EXT /SAPSLL/BADI_CDOC_EXT_N

Data Backup from External Tables in Customer-Defined Ta-

[Obsolete] Data Backup from External Applications in Cus-
bles
tomer-Defined Tables

Enhancement Spot: /SAPSLL/ES_BADI_CDOC_EXT

Old BAdI New BAdI

/SAPSLL/BADI_CDOC_EXT_UI /SAPSLL/BADI_CDOC_EXT_UI_N

Interface Control when Linking External Applications to

[Obsolete] Interface Control when Linking External Applica-
Documents
tions to Documents

Enhancement Spot: /SAPSLL/ES_BADI_CDOC_EXT

Old BAdI New BAdI

/SAPSLL/BADI_CDOC_SCP_OP /SAPSLL/BADI_CDOC_SCP_OP_N

Transfer of BOM Information from External System for Out-

[Obsolete] Transfer of BOM Information from External Sys-
ward Processing
tem for Outward Processing

Enhancement Spot: /SAPSLL/ES_BADI_CDOC_SCP

Old BAdI New BAdI

/SAPSLL/BADI_CUHD_BOM /SAPSLL/BADI_CDOC_BOM_N

Explosion of Document-Based BOMs

[Obsolete] Explosion of Document-Based BOMs

Enhancement Spot: /SAPSLL/ES_BADI_CUHD_BOM

Old BAdI New BAdI

/SAPSLL/BADI_IFMAP_CUS_CEVE /SAPSLL/BADI_IFMAP_CEVE_N

Determine Additional Data for Customs Event for External

[Obsolete] Determine Additional Data for Customs Event for
System
External System

Enhancement Spot: /SAPSLL/ES_BADI_EXTIF_CUS_CDOC

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 51
Old BAdI New BAdI

Old BAdI New BAdI

/SAPSLL/BADI_TSHD_ECC /SAPSLL/BADI_TSHD_ECC_N

BAdI for Tax Statement Area Electronic Messages

[Obsolete] BAdI for Tax Statement Area Electronic Messages

Enhancement Spot: /SAPSLL/ES_BADI_TSHD

Old BAdI New BAdI

/SAPSLL/CUS_EXPORT_WITH_TIB /SAPSLL/BADI_EXP_WITH_TRS_N

Opening of Transit Procedure in Export Processing

[Obsolete] Opening of Transit Procedure in Export Process-
ing

Enhancement Spot: /SAPSLL/CUS_EXPORT_WITH_TIB

Old BAdI New BAdI

/SAPSLL/EXPRT_DECL_REQ_CHK /SAPSLL/BADI_EXPDECL_REQ_CHK_N

Integration with Customs Brokers: Check Incompleteness

[Obsolete] Integration with Customs Brokers: Check Incom-
for Requesting Customs Export Declarations
pleteness for Requesting Customs Export Declarations

Enhancement Spot: /SAPSLL/CU_SPOT_ES_CHK

Old BAdI New BAdI

/SAPSLL/CUHD_PROP /SAPSLL/BADI_CDOC_PROP_N

Default Data in Customs Management Documents

[Obsolete] Default Data in Customs Management Docu-
ments

Enhancement Spot: /SAPSLL/ES_CDOC_PROP

Old BAdI New BAdI

/SAPSLL/CUS_ECC /SAPSLL/BADI_CUS_ECC_N

EDI Outbound Processing and Incompleteness Checks

[Obsolete] EDI Outbound Processing and Incompleteness
Checks

Enhancement Spot: /SAPSLL/ES_CUS_ECC

Old BAdI New BAdI

/SAPSLL/DUTY_CALC /SAPSLL/BADI_DUTY_CALC_N

Customs Duty Calculation: Completeness and Exclusion

[Obsolete] Cust. Duty Calc.: Completeness and Exclusion
Condition
Cond

Enhancement Spot: /SAPSLL/ES_DUTY_CALC

Old BAdI New BAdI

/SAPSLL/DUTY_CALC_EV /SAPSLL/BADI_DUTY_CALC_EV_N

Customs Duty Calculation: Evaluation of Duties

[Obsolete] Cust. Duty Calculation: Evaluation of Duties

Enhancement Spot: /SAPSLL/ES_DUTY_CALC

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
52 PUBLIC SAP Global Trade Services, edition for SAP HANA
 Old BAdI New BAdI

Old BAdI New BAdI

/SAPSLL/ECC_INBOUND /SAPSLL/BADI_ECC_INBOUND_N

EDI Inbound Processing

[Obsolete] EDI Inbound Processing

Enhancement Spot: /SAPSLL/ECC_INBOUND

Old BAdI New BAdI

/SAPSLL/PRN_DET /SAPSLL/BADI_PRN_DET_N

Message Determination in Communication Process

[Obsolete] Message Determination in Communication Proc-
ess

Enhancement Spot: /SAPSLL/ES_PRN_DET

Old BAdI New BAdI

/SAPSLL/PRN_MSG /SAPSLL/BADI_PRN_MSG_N

Print Form
[Obsolete] Print Form

Enhancement Spot: /SAPSLL/ES_PRN_MSG

Old BAdI New BAdI

/SAPSLL/SAFETY_DET /SAPSLL/BADI_SAFETY_DET_N

Determination of Comprehensive Guarantee

[Obsolete] Determination of Comprehensive Guarantee

Enhancement Spot: /SAPSLL/ES_SAFETY_DET

Old BAdI New BAdI

/SAPSLL/GRANT_DETERMINE /SAPSLL/BADI_GRANT_DETERMINE_N

Determination of Authorizations
[Obsolete] Determination of Authorizations

Enhancement Spot: /SAPSLL/GRANT_DETERMINE

Old BAdI New BAdI

/SAPSLL/IMPRT_DECL_REQ_CHK /SAPSLL/BADI_IMPDECL_REQ_CHK_N

Integration with Customs Brokers: Check Incompleteness

[Obsolete] Integration with Customs Brokers: Check Incom-
for Requesting Customs Import Declarations
pleteness for Requesting Customs Import Declarations

Enhancement Spot: /SAPSLL/CU_SPOT_ES_CHK

Old BAdI New BAdI

/SAPSLL/CU_SE_EXPRTDECL_REQ /SAPSLL/CU_SE_EXPDECL_REQ_N

Outbound Interface ExportDeclarationRequest_Out

[Obsolete] Outbound Interface ExportDeclarationRe-
quest_Out

Enhancement Spot: /SAPSLL/CU_SPOT_SE_EXPRTDECL

Old BAdI New BAdI

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 53
Old BAdI New BAdI

/SAPSLL/CU_SE_IMPRTDECL_REQ /SAPSLL/CU_SE_IMPDECL_REQ_N

Inbound Interface ImportDeclarationRequest_Out

[Obsolete] Outbound Interface ImportDeclarationRe-
quest_Out

Enhancement Spot: /SAPSLL/CU_SPOT_SE_IMPRTDECL

Old BAdI New BAdI

/SAPSLL/CU_SE_EXPRTDECL_NOTIF /SAPSLL/CU_SE_EXPDECL_NOTIF_N

Inbound Interface ExportDeclarationNotification_In

[Obsolete] Inbound Interface ExportDeclarationNotifica-
tion_In

Enhancement Spot: /SAPSLL/CU_SPOT_SE_EXPRTDECL

Old BAdI New BAdI

/SAPSLL/CU_SE_IMPRTDECL_NOTIF /SAPSLL/CU_SE_IMPDECL_NOTIF_N

Inbound Interface ImportDeclarationNotification_In

[Obsolete] Inbound Interface ImportDeclarationNotifica-
tion_In

Enhancement Spot: /SAPSLL/CU_SPOT_SE_IMPRTDECL

Old BAdI New BAdI

/SAPSLL/BADI_EXT_PRD /SAPSLL/BADI_EXT_PRD_N

Data Backup from External Tables in Customer-Defined Ta-

[Obsolete] Data Backup from External Applications in Cus-
bles
tomer-Defined Tables

Enhancement Spot: /SAPSLL/ES_BADI_EXT_PRD

Old BAdI New BAdI

/SAPSLL/BADI_EXT_UI_PRD /SAPSLL/BADI_EXT_UI_PRD_N

Interface Control when Connecting External Applications

[Obsolete] Interface Control when Connecting External Ap-
with Product
plications with Product

Enhancement Spot: /SAPSLL/ES_BADI_EXT_PRD

Old BAdI New BAdI

/SAPSLL/GRANT_DETERMINE /SAPSLL/BADI_GRANT_DETERMINE_N

Determination of Authorizations
[Obsolete] Determination of Authorizations
Enhancement Spot: /SAPSLL/GRANT_DETERMINE
Enhancement Spot: /SAPSLL/GRANT_DETERMINE

Method: GRANT_DETERMINE: change of reference type for parameter IT_LCLIC to /SAPSLL/LICHD_T

Old BAdI New BAdI

/SAPSLL/BADI_CME_NCTS_INB_XD /SAPSLL/BADI_CME_NCTS_INB_XD_N

Synchronize External Application on Receipt of NCTS Mes-

[Obsolete] Synchronize External Application on Receipt of
sage
NCTS Message

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
54 PUBLIC SAP Global Trade Services, edition for SAP HANA
 Old BAdI New BAdI

Enhancement Spot: /SAPSLL/ES_CME

2.1.2.4 BAdIs for Preference Management

Due to the new data model for long-term supplier's declarations, the following BAdIs were deleted or replaced
by new BAdIs.

Old BAdI New BAdI

/SAPSLL/BADI_VD_EXTIF_MAP Not available yet

BAdI: Mapping of External Data to Structure of Worklist

Enhancement Spot: /SAPSLL/ES_BADI_VD_EXT

Old BAdI New BAdI

/SAPSLL/BADI_VD_EXT_CREATE Not available yet

BAdI: Integration of External Data with Structure of Supplier

Declaration

Enhancement Spot: /SAPSLL/ES_BADI_VD_EXT

Old BAdI New BAdI

/SAPSLL/PRE_PRINT Not available yet

GTS: BAdI: Print

Classic BAdI

2.1.2.5 BAdIs for Intrastat

The following BAdIs for Intrastat declarations were replaced by new BAdIs in SAP GTS, edition for SAP HANA:

Old BAdI New BAdI

/ECRS/RP_CHECK_ITEM /ECRG/RP_CHECK_ITEM

Additional Item Checks in Intrastat Declarations Additional Item Checks in Intrastat Declarations

Enhancement Spot of the old BAdI: Enhancement Spot of the new BAdI:

/ECRS/RP /ECRG/RP

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 55
Old BAdI New BAdI

/ECRS/RP_FILE_TRANSFER /ECRG/RP_FILE_TRANSFER

Transfer of Intrastat Declaration Files to Authorities Transfer of Intrastat Declaration Files to Authorities

Enhancement Spot of the old BAdI: Enhancement Spot of the new BAdI:

/ECRS/RP /ECRG/RP

Due to the new interfaces for Intrastat declarations in SAP GTS, edition for SAP HANA, the following BAdI in the
feeder systems SAP ERP and SAP S/4HANA was replaced by a new BAdI.

Old BAdI New BAdI

/SAPSLL/ECR_EXTRACT /SAPSLL/INTRASTAT_SELECTION

Intrastat Extractor for SAP Electronic Compliance Reporting Intrastat Data Selection for SAP GTS, edition for SAP HANA

Classic BAdI Enhancement Spot of the new BAdI: /SAPSLL/

INTRASTAT_SELECTION

2.1.3 Authorizations

For relevant information, see Administration Guide for SAP GTS, edition for SAP HANA under Authorization
Objects.

2.1.4 Business Roles

The roles for the User Menu/SAP Easy Access Menu have been replaced by the listed business roles. The
following business roles for the Launchpad are available:

• Trade Classification Specialist

• Trade Compliance Manager
• Trade Compliance Specialist
• Trade Compliance Specialist - Screening
• Preference Specialist
• Customs Export Specialist
• Customs Import Specialist
• Customs Special Procedure Specialist
• EMCS Specialist
• Intrastat Specialist

The following User Menu Role in the back end is available:

• Administrator

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
56 PUBLIC SAP Global Trade Services, edition for SAP HANA
  Note

For more information, see User Management in the Administration Guide for SAP Global Trade Services,
edition for SAP HANA.

2.1.5 Main Function Modules

Simplification of the data model in SAP GTS, edition for SAP HANA affects the signature of central SAP GTS
function modules. If you use function modules in your implementation, you must adjust the call to the changed
signature.

Examples

Function Modules for Reading and Processing Customs Documents

Reference type /SAPSLL/CDOC_OBJ_S replaces /SAPSLL/CUHD_OBJ_S in the interface parameters of the

signature of the following function modules:

• /SAPSLL/CUHD_GET_OBJECT
• /SAPSLL/CUHD_GET_OBJECT_PK
• /SAPSLL/CUHD_MAINTAIN_OBJECT

Function Modules for Reading and Processing Products

Reference type /SAPSLL/CPRD_OBJ_S replaces /SAPSLL/PR_OBJ_S in the interface parameters of the

signature of the following function modules:

• /SAPSLL/PRODUCT_GET_OBJECT
• /SAPSLL/PRODUCT_GET_OBJECT_SK
• /SAPSLL/PRODUCT_MNTN_OBJECT

Function Modules for Reading and Processing Licenses, Authorizations and Securities

Reference type /SAPSLL/LICHD_OBJ_S replaces /SAPSLL/LCLIC_OBJ_S in the interface parameters of the

signature of the following function modules:

• /SAPSLL/LCLIC_GET_OBJECT
• /SAPSLL/LCLIC_GET_OBJECT_PK
• /SAPSLL/LCLIC_MAINTAIN_OBJECT

2.1.6 Main Data Tables

Simplification of the data model in SAP GTS, edition for SAP HANA has the consequence that particular tables
can no longer be used.

The data content is migrated to other tables. A complete overview of all DDIC table changes is documented in
key words in the XPRAs [page 10] chapters.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 57
The following table changes are substantial ones. They concern customs documents used as part of Customs
Management and Compliance Management.

DDIC table changes

Disused Tables Data Migration Target Tables

/SAPSLL/CUHDSTA /SAPSLL/CUHD

/SAPSLL/CUHDDAT /SAPSLL/CUHD

/SAPSLL/LEGTPR /SAPSLL/CUHD

/SAPSLL/LEGCOM /SAPSLL/CUHD

/SAPSLL/LEGCUS /SAPSLL/CUIT

/SAPSLL/CUITSTA /SAPSLL/CUIT

/SAPSLL/CUITDAT /SAPSLL/CUIT

/SAPSLL/CORCTSC /SAPSLL/CORCTS

/SAPSLL/PRCTS /SAPSLL/PRCLS

/SAPSLL/PRCTSC /SAPSLL/PRCLS

/SAPSLL/CTSNUM /SAPSLL/CTSNR

/SAPSLL/CTSNUMC /SAPSLL/CTSNR

/SAPSLL/LCLIC /SAPSLL/LICHD

/SAPSLL/LCLICC /SAPSLL/LICHDCL

/SAPSLL/LCLICM /SAPSLL/LICHDM

/SAPSLL/LCLICS /SAPSLL/LICHDS

/SAPSLL/LCLICW /SAPSLL/LICHDSC

 Note

Obsolete DDIC objects are assigned to development package /SAPSLL/DEPRECATED in SAP GTS, edition
for SAP HANA.

2.1.7 Change Documents

With SAP GTS, edition for SAP HANA, the change document settings for object /SAPSLL/CUHD have been
updated. Table /SAPSLL/CUIT, which is included in this object, is now set not to log any fields with

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
58 PUBLIC SAP Global Trade Services, edition for SAP HANA
initial values when being deleted. This can reduce the data footprint for change documents of this objects
significantly.

If you have registered any Business Workflow Events via linkage of change documents for the deletion of a field,
this event may no longer be triggered. You will have to verify that the field you have registered will not have an
initial value when you expect the event to be triggered for a deletion.

2.2 Overview of the Conversion Process of SAP GTS,

edition for SAP HANA

SAP provides a process for the conversion to SAP S/4HANA. The following figure gives an overview of the
tools, the phases, and activities involved in the process.

 Recommendation

We recommend that you carry out the activities in the sequence shown and explained in the figure and
sections below.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 59
Overview of the Conversion Process

A conversion of one single system is always divided into a preparation phase and a realization phase. The
preparation and the execution phase in the yellow part (top) refer to the conversion of a development system;
the preparation and the execution phase in the green part (bottom) refer to the conversion of a test or a
productive system.

The whole conversion process is arranged in a sequence along the time (black arrow). On a large scale, you
see that conversion of a development system should be executed before the conversion of a test or productive
system. On a lower scale, you see several subphases and execution points within the main phases for one
system, as this is the sequence in which the conversion process is expected to be executed for each individual
system.

The preparation phase has the same sequence of subphases and execution points for development-, test-,
or production systems. However, the execution phase differs between the development system and the other
types of systems because it is expected that you recorded the work you have done based on the new product

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
60 PUBLIC SAP Global Trade Services, edition for SAP HANA
in a development system (for example, code adaptation) in transport requests and then integrate this work in a
customer transport during conversion.

 Recommendation

If you decide on a system conversion of the respective system type in your system landscape, we
recommend that you perform the activities in the sequence shown in the figure and explained in the
sections below.

 Recommendation

We recommend that you perform a test conversion with a copy of your production system in a dedicated
system of your system landscape before you convert the real productive system.

Handling of Application Data

Besides the adaptation of customer code and configuration, which are tasks for you to be performed during
or after technical conversion, another important aspect during the conversion of an individual system is to
prepare and handle the application data in the system. The vast majority of application data stays unchanged
during the conversion to SAP GTS, edition for SAP HANA 2023. However, there are also cases where application
data is affected, and your involvement is needed.

Some application data should be reduced or removed before conversion because, after conversion, such data
cannot be handled by standard functionality owing to the functionality having been deleted in the new product.

Preparing the Conversion of a Test or Production System [page 61]

Executing the Conversion of a Development System [page 62]

Executing the Conversion of a Test or Productive System [page 63]

Conversion of a Simple System Landscape of SAP Global Trade Services [page 63]

2.2.1 Preparing the Conversion of a Test or Production

System

Before starting the execution phase for the conversion of an individual system, preparatory activities are
required. The preparation phase can be split into several subphases and is similar for development-, test-, or
productive systems.

For a detailed description of the individual conversion phases and execution points in the preparation phase of
the conversion, see Preparing the Conversion [page 67].

Planning & System Requirements

It all starts with a planning phase. A system conversion of an SAP Global Trade Services-System is a complex
project. There are technical requirements for the system conversion due to the change in base product version
and the required database version SAP HANA DATABASE 2.0. Application-specific prerequisites in SAP Global
Trade Services must be fulfilled.

For more detailed information, see Planning & System Requirements [page 67].

Maintenance Planner

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 61
You need to run the maintenance planner tool as a mandatory step in the conversion process. It checks your
installed components including add-ons and provides the possible conversion paths to SAP GTS, edition for
SAP HANA 2023. It also creates the stack file used for the actual conversion process (done by the Software
Update Manager tool).

For more detailed information, see Maintenance Planner [page 70].

 Note

This step is mandatory because the Software Update Manager requires the stack file for the conversion
process.

Cross-application preparation activities

In addition to the preparation steps described above, you also need to make some general cross-application
preparations. For more detailed information, see Cross-Application Preparation Activities [page 74].

2.2.2 Executing the Conversion of a Development System

After you have made the steps of the prepare phase, you continue with the activities of the realize phase.
For a detailed description of the individual conversion phases and execution points in the realize phase of the
conversion, see Executing the Conversion of a Test or Productive System [page 63].

Software Update Manager

When you have completed the steps of the prepare phase to ensure your system and your custom code is
suited for a conversion to SAP GTS, edition for SAP HANA, you then run the Software Update Manager (SUM).
The SUM does the database migration (if required), the actual software update, and the data conversion. For
more detailed information, see Software Update Manager (SUM) [page 77].

Application-specific adaptation activities

Adaptation of custom code is carried out in your development systems, where you record all your necessary
changes in custom code (customer business processes, BAdI implementations, etc.) in transport requests. In
addition, most of the custom client configuration is also created in development systems and is eventually
transported into your production system. Owing to the changes between SAP GTS 11.0 and SAP GTS, edition
for SAP HANA, you likely have to adapt some custom code and/or custom configuration so that your business
processes can again run as you require in the new product. You should also include deletion of custom code or
configuration where the functionality of the SAP standard is deleted in the new product or where the custom
code/configuration is no longer needed. All these software changes to the custom code and custom client
configuration should be recorded in transport requests so that you can later be incorporated as customer
transports in the SUM process of conversions of other systems based on the same new product.

Cross-application follow-on activities

Other general cross-application activities may also be required. For more detailed information, see Cross
application follow-on activities.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
62 PUBLIC SAP Global Trade Services, edition for SAP HANA
2.2.3 Executing the Conversion of a Test or Productive
System

The execution phase of a test or production system differs from the execution phase of a development system.
In the following, only these differences are described. For a detailed description of the individual conversion
phases, milestones, and points of execution in the realization phase of the conversion, see Executing the
Conversion of a Development System [page 62].

Software Update Manager

The Software Update Manager runs through the same SUM phases as in the development system. However,
your technical setup and application data in your system might be different. In addition, you should also apply
all necessary software changes recorded in your development system by incorporating a customer transport
into the SUM process to reduce the overall conversion time.

2.2.4 Conversion of a Simple System Landscape of SAP

Global Trade Services

When planning your conversion project, you should be aware that you need new systems in addition to your
existing system landscape. The figures below are an example of a simple version of a starting system landscape
for SAP Global Trade Services from SAP comprising only one development and productive system to illustrate
the principle.

Starting System Landscape

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 63
The figure “Starting system landscape” shows that there is a development system (DEV) used to apply updates
and patches to the productive system (PROD), which, at the beginning of the conversion project both are
systems running SAP Global Trade Services

––––––––––––––––––––––––––––––––––––––––––––

Establish New Development System

Then you set up a second development system (DEV_NEW) with the goal to eventually have a system
running SAP Global Trade Services, edition for SAP S/4HANA. You adapt the custom code and custom client
configuration in this system so that your business processes can run in the new product.

 Note

The development system DEV usually continues to exist as you must still be able to apply changes and fixes
to your productive system, which is still running on SAP Global Trade Services.

As you record your changes in transport requests, the new development system DEV_NEW can serve as the
source to supply the necessary software changes to your custom code and configuration to another system,
which should be converted at a later point in time.

• One option for the setup of DEV_NEW is a system copy of the original DEV system (shown in the figure
above). You use the second development system to perform and test all phases of the conversion. After
conversion, the existing custom code and configuration must be adapted in the event of changes between
the old and new product. You can collect all the necessary software changes (including the necessary
deletions of custom code or custom client configuration) during the test conversion in transport requests,
including those that can only be done after a conversion. Note that DEV_NEW at t1 and DEV_NEW at t2 in the
figure above represent the same system before (t1) and after (t2) conversion.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
64 PUBLIC SAP Global Trade Services, edition for SAP HANA
  Note

In this option, the application data created in DEV in development tests, which is copied to DEV_NEW via the
system copy, still resides in DEV_NEW after conversion. As some of the functions and features of SAP Global
Trade Services no longer exist in SAP Global Trade Services, edition for SAP HANA, the application data in
these cases may continue to exist and can no longer be processed after conversion if you do not clean up
this data prior to or during conversion.

• You can create DEV_NEW as a new installation of SAP Global Trade Services, edition for SAP HANA.
You then collect all your relevant custom code and custom client configuration in the system landscape
running SAP Global Trade Services and apply them as merge transports to the new development system
DEV_NEW. You can then work on adapting your code and configuration in the new product as needed
and record all the software changes (including the necessary deletions of custom code or custom client
configuration). This option allows for a clean start with respect to the application data in the development
system DEV_NEW.

––––––––––––––––––––––––––––––––––––––––––––

Test Conversion for Copy of Productive System

• The collected transports with the required software changes in the development system DEV_NEW can be
handed over to the Software Update Manager (SUM) tool and applied as customer transport during the
conversion of another system. It is recommended to also test the conversion of the productive system in
advance to the real final conversion with a system copy of the productive system PROD to test how the
conversion can handle your code and data in the productive environment. In the figure above the system
TEST_NEW is this system copy of the production system still running on SAP Global Trade Services. This
could be a new test system or an existing test system in your system landscape, it just needs to fulfill
the requirements to act technically as target for the system copy of your productive system. Note that
TEST_NEW at t3 and TEST_NEW at t4 as shown in the figure also describe the same system before (t3)

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 65
 and after (t4) the conversion. You could carry out this test conversion multiple times to practice the whole
conversion process.

 Note

Usually you have additional test and/or quality systems in your existing system landscape for SAP Global
Trade Services and you could also want a conversion of such systems. However, as you still need to be
able to apply changes and fixes to your productive system, you should keep the systems needed for quality
assurance of your production system available in your existing landscape as long as the productive system
is still running on SAP Global Trade Services! Therefore, as long as the productive system is not converted,
you should use the same algorithm as for the test conversion of the productive system, using an additional
system and a system copy of the source system for a conversion of such a system. In contrast, you can
also always establish new test or quality systems in your system landscape for SAP Global Trade Services,
edition for SAP HANA via a new installation.

––––––––––––––––––––––––––––––––––––––––––––

Conversion of Real Productive System

The real conversion of the productive system PROD is eventually carried out, where PROD at t5 and at t6
represent the same productive system before (t5) and after (t6) conversion.

The use of additional new systems in your system landscape for your conversion allows you to take as long as
needed to identify and process the software changes required by the conversion and then apply these changes
efficiently during the conversion of your productive system to minimize downtime.

 Note

If you also established a test or quality system running on SAP Global Trade Services, edition for SAP HANA
in your system landscape and use it as a source for the configuration of the productive system running on

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
66 PUBLIC SAP Global Trade Services, edition for SAP HANA
 SAP Global Trade Services, edition for SAP HANA, you should also record the necessary configuration in
transport requests and apply these transports after the conversion.

 Note

The development system DEV is no longer needed once the productive system has been converted
successfully and you could either dismantle or convert it. The same is true for any remaining test or quality
systems still running on SAP Global Trade Services.

2.3 Preparing the Conversion

Before conversion to SAP Global Trade Services, edition for SAP HANA 2023, you have to prepare an overall
project plan and schedule the tasks. The preparation activities described in this section give you an idea of
what is involved. For a brief overview of the process and tools, see Overview of the Conversion Process of SAP
GTS, edition for SAP HANA [page 59].

 Note

Please also read the planning section of the Software Update Manager guide. For more information, see
Useful Links and SAP Notes [page 6].

Planning & System Requirements [page 67]

Maintenance Planner [page 70]

Cross-Application Preparation Activities [page 74]

Application-Specific Preparation Activities [page 75]

2.3.1 Planning & System Requirements

Please also check the system requirements for SAP S/4HANA Foundation 2022 or SAP S/4HANA 2022:

• System Requirements [page 90]

• SAP S/4 HANA 2022

Unicode

As a prerequisite for the conversion, your system needs to be a Unicode system. If your system is still
non-Unicode, you can follow a two-step conversion approach. First, perform a combined upgrade and Unicode
conversion with one of the supported start releases as the target. Then perform the conversion to SAP GTS,
edition for SAP HANA.

What’s the Impact on Your System Landscape? [page 68]

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 67
 Supported Start Releases [page 69]

Application-Specific Prerequisites [page 69]

Conversion Readiness Check [page 69]

Application-Specific Restrictions [page 70]

2.3.1.1 What’s the Impact on Your System Landscape?

When you convert your system to SAP Global Trade Services, edition for SAP HANA, you may have to adapt
further systems or components in your system landscape.

SAP Fiori

The SAP Fiori application is contained within the product SAP FIORI FOR SAP GTS E4H 2023, product instance
UI for SAP GTS Ed4H.

There are two possible deployment options for the product SAP FIORI FOR SAP GTS E4H 2023:

• Embedded Deployment
If the system being converted did not have any SAP Fiori apps installed before conversion, then you
can simply install the required ABAP add-ons during conversion. For more information, see Maintenance
Planner [page 70].
• Hub Deployment
Hub deployment is possible for SAP Fiori for SAP GTS, edition for SAP HANA 2023. However, this can be
achieved via a system upgrade of an existing front-end server or this can be achieved via a new installation
of the product instance for UI for SAP GTS Ed4H of SAP FIORI FOR SAP GTS E4H 2023 based
on SAP Fiori front-end server 2022 for SAP S/4HANA, product instance SAP Frontend Server 7.52
(Hub deployment). Please note that certain restrictions apply to hub deployment and that upgrade
dependencies exist between the front-end and back-end product versions of the SAP Fiori apps. For more
information, see 2590653 and 3237135 .

 Note

SAP recommends the embedded deployment option for SAP Fiori for SAP GTS, edition for SAP HANA 2023.

 Note

For more information about SAP Fiori front-end server 2022 for SAP S/4HANA, please check 3237135 .

 Note

For more information about technical overview of the deployment options, please check Product
Availability Matrix .

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
68 PUBLIC SAP Global Trade Services, edition for SAP HANA
If the system being converted did not have any SAP Fiori apps installed before conversion, then you can simply
install the required ABAP add-ons during conversion. For more information, see Maintenance Planner [page
70].

2.3.1.2 Supported Start Releases

For a one-step conversion, your system needs to have a minimum release level. The following start releases are
supported:

• SAP Global Trade Services 10.0

• SAP Global Trade Services 10.1
• SAP Global Trade Services 11.0

The conversion to SAP Global Trade Services, edition for SAP HANA is based on the de-installation of the ABAP
artifacts and table entries of SAP Global Trade Services and subsequent installation of the new product. The
collection of the ABAP artifacts for SAP Global Trade Services is based on the piece lists of its initial shipment
stack and support packages. However, table entries that only come into the system via SAP Notes cannot be
seen by this algorithm, which may lead to a low number of table entries that are not handled correctly in the
conversion. Starting from a high support package level minimizes this effect.

2.3.1.3 Application-Specific Prerequisites

Before you start the realize phase and the technical conversion process of a system using the Software Update
Manager (SUM) 2.0, the following prerequisites must be fulfilled:

• You must use SUM 2.0 SP017 Patch Level 9 or a later version.
• You must use SPAM 85 or a later version.
• In addition, as a preparation for the conversion process after system downtime, you should choose either a
support package level of SP20 or greater for software component version ST-PI 740in the target stack.

 Note

Take care you have the latest version of uninstallation class. See 3291054 .

2.3.1.4 Conversion Readiness Check

Report /SAPSLL/READINESS_CHK_V8000 performs an Readiness Check that checks whether the system
prerequisites for the upgrade have been fulfilled and lists the measures you have yet to take to be able to
upgrade to SAP GTS, edition for SAP HANA.

Ensure that you execute report /SAPSLL/READINESS_CHK_V8000 in sufficient time before the planned
upgrade. Execute report /SAPSLL/READINESS_CHK_V8000 in your current productive system.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 69
  Note

The steps required for installing report /SAPSLL/READINESS_CHK_V8000 are described in SAP Note
2964245 .

 Note

For a more detailed description of the measures to be taken, see SAP Note 2973223 .

2.3.1.5 Application-Specific Restrictions

Zero Downtime Option is not supported during a system conversion

The conversion definitely requires a system downtime.

For this reason, the Zero Downtime Option (ZDO) is not supported for a system conversion to SAP Global Trade
Services, edition for SAP HANA.

2.3.2 Maintenance Planner

This chapter deals with the specialties regarding the use of the Maintenance Planner in the context of SAP
Global Trade Services, edition for SAP HANA. You have to plan the conversion with the Maintenance Planner.

You can use the Maintenance Planner to choose the latest support package stack and so also receive the latest
support package from GTSCORE. You also have the option of choosing only the Initial Shipment Stack = SP00
(ISS) instead of any Support Package Stack (SP xx).

 Recommendation

When upgrading, we recommend that you always select the latest Support Package Stack using the
Maintenance Planner.

For a conversion to SAP GTS, edition for SAP HANA 2023 you must use the
Maintenance Planner.

SAP GTS, ED. FOR SAP HANA 2023 uses the special feature for conversion with combined uninstallation/
installation, as the main software component will change from SLL-LEG to GTSCORE and SAP_AP will be
uninstalled during conversion in the context of conversion to SAP S/4HANA FOUNDATION.

In the context of SAP GTS on ERP, the software component SLL-LEG will change to GTSCORE, too. SAP_AP will
do a retrofit into S4CORE.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
70 PUBLIC SAP Global Trade Services, edition for SAP HANA
  Note

All the steps in Maintenance Planner (Deinstallation, Update NW, Convert to SAP S/4HANA, or install new
product version SAP GTS, edition for SAP HANA) have to be performed within the same maintenance
planner transaction.

The planning of your changes has to follow a specific sequence:

1. You must first plan the deinstallation of the existing product instances for SAP Global Trade Services.
2. Then you need to plan the update of the base server release to SAP S/4HANA FOUNDATION 2022. In case
of SAP NetWeaver deployment or SAP S/4HANA 2022 in case of SAP ERP deployment.
3. Finally, you have to plan the installation of the new desired product instances of SAP GTS, edition for SAP
HANA 2023 that you want.

 Note

A system conversion is only supported for systems that have SAP Global Trade Services 10.0, 10.1 or 11.0
installed.

For such systems, the conversion process is only supported to a system that has SAP GTS, ED. FOR
SAP HANA 2023 (technical name) with technical release 1.0 installed on SAP S/4HANA FOUNDATION
2022 as the base product version. These are known as standalone systems.

It is not possible to convert a system that has SAP GTS 10.0, 10.1 or 11.0 installed on SAP NetWeaver to a
system that is based on SAP S/4HANA 2022 as the base product version.

A system conversion to SAP S/4HANA 2022 is only possible if the supported SAP GTS releases are
installed on EHP<x> FOR SAP ERP 6.0.

In the following, you find detailed steps how to plan a conversion of a system that has only one instance of SAP
Global Trade Services installed as the source product version and that should be converted to SAP GTS, edition
for SAP HANA 2023 depending on the deployment scenario in the to be converted system.

Maintenance Planning SAP GTS on SAP Netweaver to SAP GTS, ED. 2023 on SAP S/4 FOUNDATION 2022
[page 71]

Maintenance Planning SAP GTS on EHP<x> FOR SAP ERP6.0 to SAP GTS, ED. 2023 on SAP S/4 2022
[page 73]

2.3.2.1 Maintenance Planning SAP GTS on SAP Netweaver

to SAP GTS, ED. 2023 on SAP S/4 FOUNDATION
2022

Uninstall of SAP GTS

In your planning sequence, you first need to select Uninstall Add-Ons.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 71
Select the existing installed product version SAP Global Trade Services 10.0, SAP GTS 10.1, or SAP GTS 11.0,
then the Maintenance Planner automatically selects all installed product instances contained in the product
version of SAP Global Trade Services (for example, SLL-LEG or SLL-LEG on NW 7.50+).

 Note

If the Add-On Product Version GTS IDENT PREF PROCESS 2.0 is installed, Maintenance Planner will
mark this automatically for to be uninstalled, too.

Important:

Please do not unmark GTS IDENT PREF PROCESS 2.0 for Deinstallation in Maintenance Planner in step
“Uninstall Add-Ons”. In this special scenario, it must be uninstalled.

A pop-up occurs in Maintenance Planner with the information that GTS IDENT PREF PROCESS 2.0 has
to be uninstalled if the Add-On Product Version GTS IDENT PREF PROCESS 2.0 is installed with one of
the following Instances:

• Id Proc Serv GTS 10.1 NW 7.31

• Id Proc Serv GTS 10.1 NW 7.4
• Id Proc Serv GTS 11.0 NW 7.4

This pop-up can be ignored.

Reason:

GTS IDENT PREF PROCESS 2.0 (Software Component Version IBPP 200) does a retrofit into SLL-LEG
V8000 200 (SAP GTS ED FOR SAP HANA 2020) and this software is now also part of GTSCORE 200 (SAP
GTS ED FOR SAP HANA 2023).

Update of base server release

In your planning sequence, you next need to select Update SAP NetWeaver. Then select the product version
SAP S/4HANA FOUNDATION 2022. SAP recommends you select the highest available Support Package Stack
for this product version.

 Note

The Support Package Stack must be at least SPS02, as this is a prerequisite for later installation of SAP
GTS, edition for SAP HANA 2023.

Installation of SAP Global Trade Services, edition for SAP HANA

In your planning sequence, you next need to select Install or Maintain an Add-On.

Select the product version SAP GTS, edition for SAP HANA 2023. Then you need to select at least product
instance GTSCORE. Continue with the following standard Maintenance Planner steps.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
72 PUBLIC SAP Global Trade Services, edition for SAP HANA
You can use the Maintenance Planner to choose the latest support package stack and so also receive the latest
support package from GTSCORE. You also have the option of choosing only the Initial Shipment Stack = SP00
(ISS) instead of any Support Package Stack.

 Recommendation

When upgrading, we recommend that you always select the latest Support Package Stack using the
Maintenance Planner.

For detailed information about the product instances and software components contained of SAP GTS, ED.
FOR SAP HANA 2023, see also Administration Guide for SAP GTS, ED. FOR SAP HANA 2023 or the Product
Availability Matrix (PAM) for SAP GTS, ED. FOR SAP HANA 2023

For more information, see the Maintenance Planner User Guide.

For preparatory steps specific to the conversion, also see Cross-Application Preparation Activities [page 74].

2.3.2.2 Maintenance Planning SAP GTS on EHP<x> FOR

SAP ERP6.0 to SAP GTS, ED. 2023 on SAP S/4
2022

Uninstall of SAP GTS

In your planning sequence, you first need to select Uninstall Add-Ons.

Select the existing installed product version SAP Global Trade Services 10.0, SAP GTS 10.1, or SAP GTS 11.0,
then the Maintenance Planner automatically selects all installed product instances contained in the product
version of SAP Global Trade Services (for example, SLL-LEG or SLL-LEG on NW 7.50+).

 Note

If the Add-On Product Version GTS IDENT PREF PROCESS 2.0 is installed, Maintenance Planner will
mark this automatically for to be uninstalled, too.

Important:

Please do not unmark GTS IDENT PREF PROCESS 2.0 for Deinstallation in Maintenance Planner in Step
“Uninstall Add-ons”. In this scenario it should be uninstalled.

A pop-up occurs in Maintenance Planner with the information that GTS IDENT PREF PROCESS 2.0
must be uninstalled if the Add-On Product Version GTS IDENT PREF PROCESS 2.0 is installed with one
of the following Instances:

• Id Proc Serv GTS 10.1 NW 7.31

• Id Proc Serv GTS 10.1 NW 7.4
• Id Proc Serv GTS 11.0 NW 7.4

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 73
 Reason:

GTS IDENT PREF PROCESS 2.0 (Software Component Version IBPP 200) did a retrofit into SLL-LEG
V8000 (SAP GTS ED FOR SAP HANA 2020).

Update of base server release

In your planning sequence, you next need to select Plan a Conversion to SAP S/4HANA. Then select the
product version SAP S/4HANA 2022, at least SPS02. SAP recommends you select the highest available
Support Package Stack for this product version.

 Note

The Support Package Stack must be at least SPS02, as this is a prerequisite for later installation of SAP
GTS, edition for SAP HANA 2023.

Installation of SAP Global Trade Services, edition for SAP HANA

In your planning sequence, you next need to select Install or Maintain an Add-On.

Select the product version SAP GTS, edition for SAP HANA 2023. Then you need to select at least product
instance GTSCORE. Continue with the following standard Maintenance Planner steps.

You can use the Maintenance Planner to choose the latest support package stack and so also receive the latest
support package from GTSCORE. You also have the option of choosing only the Initial Shipment Stack = SP00
(ISS) instead of any Support Package Stack.

 Recommendation

When upgrading, we recommend that you always select the latest Support Package Stack using the
Maintenance Planner.

For detailed information about the product instances and software components contained of SAP GTS, ED.
FOR SAP HANA 2023, see also Administration Guide for SAP GTS, ED. FOR SAP HANA 2023 or the Product
Availability Matrix (PAM) for SAP GTS, ED. FOR SAP HANA 2023

For more information, see the Maintenance Planner User Guide.

For preparatory steps specific to the conversion, also see Cross-Application Preparation Activities [page 74].

2.3.3 Cross-Application Preparation Activities

Before starting conversion activities, you need to do the general preparatory activities necessary for conversion
to a system based on SAP S/4HANA Foundation described in subchapter Cross-Application Preparations
[page 92] of main chapter SAP S/4HANA Foundation [page 87].

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
74 PUBLIC SAP Global Trade Services, edition for SAP HANA
2.3.4 Application-Specific Preparation Activities

Preparation Activities for Intrastat [page 75]

2.3.4.1 Preparation Activities for Intrastat

Completing Intrastat Declarations [page 75]

Backup for Worklist for Intrastat Declaration [page 75]

Backup for Provider of Information Data [page 76]

Exclusion of Regions from Intrastat [page 76]

Default Values for Import Worklist [page 76]

Deletion of Background Jobs for Importing Worklist [page 76]

Deletion of Background Jobs for Deletion of Worklist [page 77]

2.3.4.1.1 Completing Intrastat Declarations

During conversion, all worklist entries are deleted and cannot be imported into Intrastat declarations after
conversion.

Ensure that all available Intrastat declarations contain all required data from the feeder systems before
conversion.

If data is required from the feeder systems after conversion for Intrastat declarations created before
conversion, you have to delete these Intrastat declarations and transfer all required data from the feeder
systems again.

2.3.4.1.2 Backup for Worklist for Intrastat Declaration

The data of the table /ECRS/WLEN (Worklist for Intrastat Declaration) is deleted during conversion.

Therefore, all data from this table is lost after conversion.

If you need data from this table after the conversion, you have to create a backup before the conversion.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 75
2.3.4.1.3 Backup for Provider of Information Data

The following provider of information data is deleted during conversion:

• Address Data of Provider of Information

• VAT Registration Number of Provider of Information
• Indicator Generate Header in Declaration File (only relevant for Italy)

You need to back up this data before the conversion, because this data is required for the Business Partners for
Providers of Information [page 84] and Switch to New File Format for Intrastat Declarations in Italy [page 84]
follow-on activities.

2.3.4.1.4 Exclusion of Regions from Intrastat

The table /ECRS/TERE (Exclusion of Regions from Intrastat) is deleted during conversion and the
corresponding functionality for excluding regions from Intrastat is not available after conversion.

Therefore, the exclusion of regions from Intrastat must be done in the feeder systems.

Implement the exclusion of regions from Intrastat in the feeder systems before conversion.

2.3.4.1.5 Default Values for Import Worklist

The table /ECRS/DVIA (Default Values for Import Worklist) is deleted during conversion and the corresponding
functionality for default values for import worklist is not available after conversion.

Therefore, this functionality must be implemented in the feeder systems.

Implement the corresponding functionality in the feeder systems before conversion.

Related Information

SAP Note 3421450

2.3.4.1.6 Deletion of Background Jobs for Importing

Worklist

The worklist for Intrastat declarations is not available after conversion.

Report /ECRS/WL_IMPORT for importing worklist is deleted during conversion.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
76 PUBLIC SAP Global Trade Services, edition for SAP HANA
Delete all background jobs using this report before conversion.

2.3.4.1.7 Deletion of Background Jobs for Deletion of

Worklist

The worklist for Intrastat declarations is not available after conversion.

The report /ECRS/WL_DELETE for deletion of worklist is deleted during conversion.

Delete all background jobs using this report before conversion.

2.4 Executing the Conversion

After the prepare phase, you start with the realization of the conversion to SAP S/4HANA using the Software
Update Manager (SUM) tool. For an overview of the entire process, see Overview of the Conversion Process of
SAP GTS, edition for SAP HANA [page 59].

Software Update Manager (SUM) [page 77]

System Downtime [page 78]

XPRAs Executed During Conversion [page 78]

Optimizing the Performance [page 79]

Follow-On-Activities [page 80]

2.4.1 Software Update Manager (SUM)

The Software Update Manager (SUM) is the technical tool used for the system conversion to SAP GTS, edition
for SAP HANA.

 Note

You must use at least SUM 2.0 SP017 Patch Level 9 and always use the latest available patch version.

The following steps are carried out within the SUM process in a one-step procedure (for dedicated start
releases):

1. Database migration (optional).

If your source system is not yet running on the SAP HANA database, use the database migration option
(DMO) of the Software Update Manager to migrate your database to SAP HANA during the conversion
2. Installation of the software stack of SAP GTS, edition for SAP HANA
3. Conversion of your data into the new data structures used by SAP GTS, edition for SAP HANA (this is the
automated part)

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 77
For more information about using the SUM, see the available guides for Software Update Manager 2.0. You can
find these guides under the link provided in chapter Useful Links and SAP Notes [page 6].

2.4.2 System Downtime

At some point, the SUM process shuts down the system to apply the new software stack and subsequently
apply all necessary technical follow-up processes. No business runs during system downtime.

2.4.3 XPRAs Executed During Conversion

The following table contains all the application-specific XPRAs that are started during conversion to SAP GTS,
edition for SAP HANA 2023.

• Each XPRA contains checks to determine whether it really needs to convert or migrate any data based on
the current data in the system.
• Each XPRA can be restarted.

 Note

If the XPRA issues an error message indicating problems, you can continue the conversion. However, you
have to ensure that the problems are removed and the XPRA is restarted after the end of the conversion,
but before beginning productive use of the system. Otherwise, problems may arise in the production
system.

 Note

For a detailed description of the purpose and the prerequisites of the XPRA, see the documentation
provided for the XPRA. The documentation can be accessed with the XPRA name in transaction SE38
(choose Goto Documentation Display .

• The table also specifies the release with which the XPRA was first delivered.

• If you upgrade from a start release greater or equal to the release in which the XPRA was delivered, you can
expect the XPRA to be executed faster and without any data transfer because the data in your system is
already in the desired final state.

Additional XPRAs that are not listed here may be delivered with the underlying release of SAP NetWeaver.

XPRA Released Short Description

/SAPSLL/XPRA_GTSC200 SAP GTS, edition for SAP HANA 2023 Data conversion for upgrade to SAP
GTS, edition for SAP HANA 2023

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
78 PUBLIC SAP Global Trade Services, edition for SAP HANA
2.4.4 Optimizing the Performance

It is highly recommended to perform the system conversion on a sandbox system before upgrading the
production system. The sandbox environment is ideally a 1:1 copy of your production system on equivalent
hardware. This will allow you to figure out the optimal settings for the production system conversion.

The XPRA /SAPSLL/XPRA_GTSC200 uses a common parallelization framework. Therefore, the configuration
has also been harmonized for all data conversion methods using parallel tasks. The configuration is stored in
table SHDB_PFW_CONF and can be preset / adjusted via transaction SE16 or an SQL command line.

A suitable point in time to perform this configuration is just before entering the technical downtime, e.g.
when SUM reaches phase CHECK4NOTES_TOOL_SHD2 (see SAP Note 2207944 on how to activate this
break-point).

Typical candidates for fine-tuning are:

• COMPONENT="RESOURCE PROVIDER", PARAM="ABAP_MAX_WP": Maximum amount of parallel ABAP

processes used to perform the data migration (assuming adequate number of configured dialog processes
for scheduling aRFC tasks). Default is 20 for XPRA /SAPSLL/XPRA_GTSC200. May be increased up
to 64 assuming sufficient resources on both AS ABAP and HANA. The parallelization framework will
automatically decrease the actual parallel degree if it recognizes a resource shortage on AS ABAP or
HANA.
• COMPONENT="RESOURCE PROVIDER", PARAM="HARD_DELTA_LIMIT_FOR_MERGE": Threshold to suspend
scheduling of new tasks until delta store in cleaned up by delta merge. Default is 200mio. May be increased
up to 1000mio if available HANA memory is no concern, and if you experience large gaps between tasks
completing, and new tasks being scheduled.
• COMPONENT="DISPATCHER", PARAM="WAKEUP_INTERVAL": Interval in seconds used to process completed
tasks and scheduling new ones. Default is 5 seconds. May be decreased to 1 second in case parallel tasks
do finish within a few seconds and there are hundreds of packages to process.
• COMPONENT="DISPATCHER", PARAM="MAX_WAIT_FOR_COLLECTOR": Timeout in seconds for gathering
HANA resource utilization metrics from HANA monitoring tables. If you experience "collector timeouts",
increase the value.

 Example

Following example will increase the maximal number of parallel tasks for procedure /SAPSLL/
XPRA_GTSC200 to 32 and reduce the wakeup interval for scheduling new packages to 1sec.

INSERT INTO SHDB_PFW_CONF

(APPL_NAME,COMPONENT,PARAM,TYPE,LENGTH,DECIMALS,VALUE,CHANGEABLE) VALUES ('/

SAPSLL/XPRA_GTSC200','RESOURCE PROVIDER','ABAP_MAX_WP','I',4,0,'32','N');

 Note

The prerequisite for being able to make use of the default of 20 dialog processes for XPRA/
SAPSLL/XPRA_GTSC200 is that you specify a minimum of 20 dialog processes in SUM dialog
PREP_CONFIGURATION/INITSUBST, parameter ABAP PROCESSES (DOWNTIME). If hardware resources
allow a higher number, you can further increase the number of processes.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 79
Measures specific to HANA

 Note

The following HANA parameter changes will help data conversion performance, but may impact productive
performance. Therefore, if you apply these changes before entering technical downtime, don’t forget to
revert the same before the system Go-Live on SAP GTS, edition for SAP HANA.

• Increase the CPU capacity used for delta merges by changing the indexserver.ini parameter
[mergedog] -> load_balancing_func value to “LCC / 2”. Remember the original value to restore it later.
• Increase the number of merge tokens and merge threads by setting indexserver.ini parameters
[mergedog] -> token_per_table and [indexing] -> parallel_merge_threads to a value of available
physical CPU cores divided by 2 (but no more than 256).
• • Increase the parallelism for partitioned tables by setting indexserver.ini parameter [indexing] ->
parallel_merge_part_threads to a value of available physical CPU cores divided by 2 (but no more than
256). If the parameter is not yet existing in section [indexing], add it as a new parameter.

 Note

For detailed information about HANA workload and resource management, see SAP Note 2222250 -
FAQ: SAP HANA Workload Management .

For detailed information about HANA delta merge parameters and cost functions see the SAP HANA
Administration Guide for HANA Platform.

Observe and manage available system resources

Most of the measures described above are around configuring an appropriate number of parallel tasks. If doing
so, you should monitor both your SAP (on OS level) and HANA database (on OS level or SAP HANA Cockpit)
systems for CPU, disk I/O activity and memory consumption.

In case of underutilization (overall CPU and disk activity in average below 60% for more than a minute), you
can increase the number of parallel tasks by changing parameters as described above.

In case of very high CPU usage and/or disk activity (in average over 85% for more than a minute), and/or high
wait CPU cycles (in average over 10% for more than a minute) you should decrease the number of parallel
tasks. Also decrease the number of parallel tasks when you detect high memory consumption on your HANA
database server.

If increasing the number of parallel tasks to a large extend, you should monitor the memory usage of the HANA
database server. Use the visual load history of the HANA cockpit, or the relevant monitoring views such as
M_SERVICE_MEMORY or M_HEAP_MEMORY.

2.4.5 Follow-On-Activities

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
80 PUBLIC SAP Global Trade Services, edition for SAP HANA
 Cross Application follow-on Activities [page 81]

Application-Specific Follow-On Activities [page 81]

2.4.5.1 Cross Application follow-on Activities

Adapt Authorizations

You need to review your existing PFCG role menus for obsolete transactions as well as for transaction code
replacements. One option to do this is to use the postprocessing capabilities in transaction SU25.

Fiori Apps

To use the new Fiori apps of SAP GTS, edition for SAP HANA 2023, you need to check and follow the
corresponding setup procedures in the Administration Guide for SAP GTS, edition for SAP HANA under UI
Technology Information.

Follow-On Activities for Archiving [page 81]

2.4.5.1.1 Follow-On Activities for Archiving

This chapter is only mandatory to follow if you have already archived customs documents.

Due to the database redesign for the customs document, archive infostructure /SAPSLL/CUHD had to be
changed. It was necessary to add field ZRGENR, which previously resided in table /SAPSLL/LEGCOM. As a
consequence, the archive infostructure has to be rebuild after the upgrade.

For more information, see SAP Knowledge Base Article 1954602 SAP Archiving: Inconsistency in Archive Info
Structure /SAPSLL/CUHD.

In case of a huge data volume, you can use report AS_BUILD_SCHEDULER to parallelize several jobs building
the infostructure.

2.4.5.2 Application-Specific Follow-On Activities

Follow-On Activities for Preference Management [page 82]

Follow-On Activities for Intrastat [page 83]

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 81
 Follow-On Activities for Compliance Management [page 85]

2.4.5.2.1 Follow-On Activities for Preference Management

Migration of Long-Term Supplier´s Declaration Management [page 82]

Migration of Identity-Based Supplier‘s Declarations [page 82]

Check Definition of Bill of Material Evaluation [page 83]

2.4.5.2.1.1 Migration of Long-Term Supplier´s Declaration

Management

If you have converted from SAP Global Trade Services 11.0 to SAP Global Trade Services, edition for SAP HANA,
you have the option to migrate your data from the legacy system to the new database tables.

To assist you in doing so, the following migration reports are available (SAP Note 3138866 - LTSD Management
– Migration):

• /SAPSLL/PRE_MIG_LTSD_REQUESTS (Migration of LTSD requests)

• /SAPSLL/PRE_MIG_LTSD_INBOUND (Migration of supplier-based long-term supplier’s declarations)
• /SAPSLL/PRE_MIG_LTSD_OUTBOUND (Migration of customer-based long-term supplier’s declarations)
• /SAPSLL/PRE_MIG_PARTNER_PROP (Migration of preference properties for business partners)

You can execute the reports after a successful upgrade to SAP GTS, edition for SAP HANA.

For details and advice about how to migrate your data from the older system, see SAP Note 3140386 – Guide
for migration of LTSDs from SAP GTS 11.0 to LTSDs in SAP GTS, edition for SAP HANA.

Related Information

SAP Note 3138866

SAP Note 3140386

2.4.5.2.1.2 Migration of Identity-Based Supplier‘s

Declarations

If you have converted from SAP Global Trade Services 11.0 to SAP Global Trade Services, edition for SAP HANA,
you have the option to migrate your data from the legacy system to the new database tables.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
82 PUBLIC SAP Global Trade Services, edition for SAP HANA
To assist you in doing so, the following migration report is available: /SAPSLL/PRE_MIG_IBVD (Migration of
IBSDs to product identifiers)

You can execute the migration report after a successful upgrade to SAP GTS, edition for SAP HANA. For details
and advice how to migrate legacy data, see SAP Note 3348804 – Guide for migration of IBSDs from SAP GTS,
identity-based preference processing to the data model of SAP GTS, edition for SAP HANA.

Related Information

SAP Note 3348804

2.4.5.2.1.3 Check Definition of Bill of Material Evaluation

If you have converted from SAP Global Trade Services 11.0 to SAP Global Trade Services, edition for SAP HANA,
we recommend that you check the definition of the Bill of Material Evaluation again. If you are using a 3-system
landscape, we recommend that you make settings in Customizing so that the same plant is assigned only with
one logical system.

 Example

Plant 1000 was only assigned for logical system GTPCLNT100 in the production system. The logical
systems GTDCLT100 and GTQCLNT100 are only assigned in the corresponding development or test
system.

If you do not follow the recommendation, please note that the same plant may be displayed more than once in
certain applications. This can occur on the Classification tab in the "Manage Products" app, for example, if you
want to edit preference conditions at plant level.

 Note

Please check the recommendation in the Configuration Guide for SAP Global Trade Services, edition for SAP
HANA and refer to the description for a corresponding adjustment:

• Defining the Plant-Specific Bill of Material Evaluation

• Defining the Cross-Plant BOM Evaluation

2.4.5.2.2 Follow-On Activities for Intrastat

Authorization Objects for Intrastat [page 84]

Business Partners for Providers of Information [page 84]

Switch to New File Format for Intrastat Declarations in Italy [page 84]

Switch to New File Formats for Intrastat Declarations in BE, CZ, DK, IE, PL, and PT [page 84]

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 83
2.4.5.2.2.1 Authorization Objects for Intrastat

The following two authorization objects in SAP GTS, edition for SAP HANA were replaced.

Old Authorization Object New Authorization Object

/ECRS/RP: Edit Intrastat Declarations /ECRG/RPHB: Intrastat Declaration for

Business Partner

/ECRS/POI: Maintain Providers of Information /ECRG/POIB: Provider of Information for

Business Partner

Assign authorizations for Intrastat users based on new authorization objects. For more information, see
Administration Guide for SAP Global Trade Services, edition for SAP HANA, under Authorization Objects for
Intrastat.

2.4.5.2.2.2 Business Partners for Providers of Information

Providers of information in SAP GTS, edition for SAP HANA require business partners assigned to them.

For each provider of information, create a business partner with the business partner role SLLPOI (Provider
of Information) and enter address data and the VAT registration number in the country of declaration for this
business partner.

Assign this business partner to the corresponding provider of information in the Manage Providers of
Information app.

2.4.5.2.2.3 Switch to New File Format for Intrastat

Declarations in Italy

If you use the Intrastat declaration file format with an additional header line for a provider of information in
Italy (which means that the indicator Generate Header in Declaration File in provider of information is set before
conversion), you have to assign the new file format 2 (ASCII File with Additional Header Line) to this provider of
information in the Manage Providers of Information app.

2.4.5.2.2.4 Switch to New File Formats for Intrastat

Declarations in BE, CZ, DK, IE, PL, and PT

Some Intrastat declaration file formats are deleted during conversion in the following countries:

• BE (Belgium)

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
84 PUBLIC SAP Global Trade Services, edition for SAP HANA
 • CZ (Czech Republic)
• DK (Denmark)
• IE (Ireland)
• PL (Poland)
• PT (Portugal)

Check whether the Intrastat declaration file formats you use are still available after conversion.

If they are not available after conversion, you have to assign new file formats in the Manage Providers of
Information app.

2.4.5.2.3 Follow-On Activities for Compliance Management

Execute Report /SAPSLL/SPL_HANA_SPLMD_CONVERT to prepare concatenated names and streets of

SPL entities [page 85]

Optimized Audit Trail [page 85]

Define New Release Reasons [page 86]

2.4.5.2.3.1 Execute Report /SAPSLL/

SPL_HANA_SPLMD_CONVERT to prepare
concatenated names and streets of SPL entities

Execute report /SAPSLL/SPL_HANA_SPLMD_CONVERT once, either before or after the system conversion.
This prepares the concatenated names and streets for SPL entities. So that the SPL hits are displayed
correctly in name Matches and Address Matches column in the Manage Blocked Partners and Manage Blocked
Documents apps. This also prepares the data for SPL HANA Search.

 Note

This report /SAPSLL/SPL_HANA_SPLMD_CONVERT is not mandatory if you have already executed the
report in system of SAP GTS 11.0. So it is not required to execute the report again in SAP Global Trade
Services, edition for SAP HANA.

In the Manage Blocked Partners and Manage Blocked Documents apps, to ensure that the Name Matches
and Addresses Matches columns are filled correctly in the table, you must execute report /SAPSLL/
SPL_HANA_SPLMD_CONVERT once, either before or after the system conversion. This guarantees that the
SPL hits are displayed correctly.

2.4.5.2.3.2 Optimized Audit Trail

You should configure the settings of audit trail if optimized audit trail is not activated in SAP Global Trade
Service 11.0, since the settings for old audit trail are removed from customizing and they cannot be converted

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
SAP Global Trade Services, edition for SAP HANA PUBLIC 85
to the settings of optimized audit trail. In the Implementation Guide, choose SAP Global Trade Services
Compliance Management Sanctioned Party List Screening Control Settings for Sanctioned Party List
Screening to set the usage of optimized audit trail for customs document, business partner, offline and
simulation screenings in each SPL legal regulations.

If optimized audit trail is not activated in SAP Global Trade Service 11.0, you should schedule background job to
do periodic screening for blocked partners and documents. Display Blocked Documents and Display Blocked
Partners apps need optimized audit trail data to display the screening result.

2.4.5.2.3.3 Define New Release Reasons

If you want to convert or upgrade from SAP Global Trade Services 11.0 to SAP Global Trade Services, edition for
SAP HANA, you must define new release reasons because Sanctioned Party List Screening only uses a standard
determination procedure SPLRELBLK for the release reason and another standard determination procedure
EMBRELBLK is used for the embargo check.

You define new release reasons in SAP Global Trade Services, edition for SAP HANA in Customizing, under:
SAP Global Trade Services, edition for SAP HANA Compliance Management Define Reasons for
Releasing Blocked Documents and Business Partners

Save Control Settings for Embargo Check

You must make any changes in each legal regulation in Control Settings for Embargo Check and save them.
It could save the standard determination procedure for release reasons in the control settings for legal
regulations. To do this, select Control Settings for Embargo Check in Customizing under SAP Global Trade
Services, edition for SAP HANA Compliance Management Embargo Check .

Save Control Settings for Sanctioned Party List Screening

You must make any changes in each legal regulation in Control Settings for Sanctioned Party List Screening
and save them. It could save the standard determination procedure for release reasons in the control settings
for legal regulations. To do this, select Control Settings for Sanctioned Party List Screening in Customizing
under SAP Global Trade Services, edition for SAP HANA Compliance Management Sanctioned Party
List Screening .

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
86 PUBLIC SAP Global Trade Services, edition for SAP HANA
3 Server Release

If you run SAP GTS on SAP Netweaver standalone, you have to follow Chapter SAP S/4HANA Foundation.

If you run SAP GTS on SAP ERP, you have to follow Chapter SAP S/4HANA [page 93].

SAP S/4HANA Foundation [page 87]

SAP S/4HANA [page 93]

3.1 SAP S/4HANA Foundation

SAP S/4HANA foundation is the next-generation Business Suite foundation platform and is fully built on the
most advanced in-memory platform existing today: SAP HANA. SAP S/4HANA foundation comprises the
ABAP platform plus a re-use layer built out of the components S4FND and MDG_FND. With SAP S/4HANA
foundation, SAP helps businesses to run simple in the digital economy, including such topics and principles as
the Internet of things, Big Data, business networks, and mobile-first. The software component uses modern
design principles with the SAP Fiori user experience (UX) as well as a new role-based user experience concept.

 Note

SAP S/4HANA foundation is not allowed to be used standalone but only as a foundation in combination
with an ABAP add-on as depicted on the corresponding allow list.

Documentation, Tools, and SAP Notes for the Conversion [page 87]

Overview of the Conversion Process [page 88]

3.1.1 Documentation, Tools, and SAP Notes for the

Conversion

Required Documents, Tools, and SAP Notes

You require the following conversion assets to prepare and run a conversion project.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
Server Release PUBLIC 87
Document Available at Comment

System Conversion to SAP S/4HANA Software Logistics Toolset Describes how to prepare the system
using SUM 2.0 SP <latest version> for running the Software Update Man-
(SL Toolset System Maintenance
(incl. DMO) ager, how to use it, and what general
System Conversion to SAp S/4HANA follow-up steps are required.
using SUM 2.0 <latest SP>

Maintenance Planner User Guide http://help.sap.com/maintenanceplan- Describes how to use the Maintenance
ner Planner for calculating and download-
ing the required stack.xml file and soft-
ware packages.

SAP S/4HANA foundation: Release In- https://support.sap.com The Release Information Note for a spe-
formation Note cific product version of SAP S/4HANA
To find the release information note for foundation provides valuable informa-
your target product version, search for tion, e.g. about supported ABAP Add-
SAP S/4HANA FOUNDATION Release Ons and about supported start releases
Information Note.

Additional Information and SAP Notes

The following table lists important additional documents and SAP Notes.

Document Available at Comment

SAP S/4HANA foundation: Always-Off SAP Note 2240359 -

Business Functions

SAP S/4HANA foundation: Always-On SAP Note 2240360 -

Business Functions

Uninstalling ABAP Add-Ons SAP Note 2011192 -

3.1.2 Overview of the Conversion Process

Preparation Phase

SAP provides a process for the conversion to SAP S/4HANA foundation. Before starting the realization phase
of the conversion process, you have to do the following preparatory activities:

1. Planning
You need to gain an idea of the project steps and necessary preparations. Use the Roadmap Viewer to
familiarize yourself with the project steps required for the transition to SAP S/4HANA foundation. For more
information, see https://roadmapviewer-supportportal.dispatcher.hana.ondemand.com/.
2. System requirements

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
88 PUBLIC Server Release
 You need to be aware of system requirements, start releases, conversion paths, and data volume. See the
following sections for more information:
• System Requirements [page 90]
• Supported Start Releases [page 90]
3. Maintenance Planner
You need to run the Maintenance Planner tool as a first step in the conversion process. It checks your
components, add-ons, and business functions to ensure compatibility with SAP S/4HANA foundation and
also creates the stack file used for the actual conversion process (done by the Software Update Manager
tool). For more information, see Maintenance Planner [page 91].

 Note

This step is mandatory, because the Software Update Manager requires the stack file for the
conversion process.

The Maintenance Planner has replaced the Maintenance Optimizer, which is not supported by SAP
S/4HANA foundation.

4. Cross-application preparation activities

In addition to the general preparation steps described above, you also need to do some cross-application
preparations. For more information, see Cross-Application Preparations [page 92].

Realize Phase

After you have executed the steps in the preparation phase, you can continue with the activities of the realize
phase using the Software Update Manager (SUM). The Software Update Manager does the database migration
(if required), the actual software update, and the data conversion. For more information, see Realizing the
Conversion [page 93].

Preparing the Conversion [page 89]

Realizing the Conversion [page 93]

3.1.2.1 Preparing the Conversion

For the conversion to SAP S/4HANA foundation you have to prepare an overall project plan and schedule the
tasks. The preparation activities described in this section give you an idea of what is involved.

 Note

In addition, review the planning section of the Software Update Manager guide System Conversion to SAP
S/4HANA using SUM 2.0 <latest version> at https://support.sap.com/sltoolset Software Logistics
Toolset (SL Toolset) System Maintenance .

System Requirements [page 90]

Supported Start Releases [page 90]

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
Server Release PUBLIC 89
 Maintenance Planner [page 91]

Cross-Application Preparations [page 92]

3.1.2.1.1 System Requirements

Unicode

As a prerequisite for the conversion, your system needs to be a Unicode system. If your system is still
non-Unicode, you can follow a two-step conversion approach: First, perform a combined upgrade and Unicode
conversion with one of the supported start releases as target, then perform the conversion to SAP S/4HANA
foundation.

For additional information, see Unicode Conversion Overview (on SAP SCN).

Application Server ABAP Only

Your system has to be an AS ABAP only system. Dual stack systems (AS ABAP and AS Java combined in one
system) are not supported for the conversion. If your system is a dual-stack system, you have to split it before
doing the conversion.

For additional information on how to perform a dual-stack split, see:

• SAP Note 1655335

• Guide at https://support.sap.com/sltoolset System Provisioning System Provisioning Scenarios
Split a System using Software Provisioning Manager 1.0 Dual Stack Split Guides .
• Dual Stack Split

3.1.2.1.2 Supported Start Releases

A one-step conversion from a minimum released level is supported in SAP S/4HANA foundation.

SAP S/4HANA foundation is not allowed to be used standalone but only as a foundation in combination with an
ABAP add-on.

Therefore, the supported start releases for a conversion of SAP S/4HANA foundation also depend on the
source and target stack of the installed add-on. For more information , see the add-on specific conversion
information in which the SAP S/4HANA Foundation chapter is included.

Check the release information note for the target product version of SAP S/4HANA foundation for the
supported start releases with regard to the foundation and the required feature package stack equivalencies.
For more information, see Documentation, Tools, and SAP Notes for the Conversion [page 87].

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
90 PUBLIC Server Release
3.1.2.1.3 Maintenance Planner

Overview

The Maintenance Planner generates the download files (add-ons, packages, DBDs, and the stack configuration
file) that the Software Update Manager (SUM) uses to do a conversion or an upgrade. In particular, the
Maintenance Planner checks if the following items are supported:

• Add-ons to your system

• Active business functions in your system

The Maintenance Planner checks whether there is a valid path for any of the items listed above (for example,
an add-on is not released for the conversion or the upgrade yet). After the check, the Maintenance Planner
creates the stack configuration file (stack.xml).

 Note

In order to generate the stack.xml, you need to have valid licenses of the target SAP products. You can
do the above checks without a license, but you cannot create a stack.xml with the Maintenance Planner
without a license.

For more information, see the Maintenance Planner User Guide at http://help.sap.com/maintenanceplanner.
For specific preparatory steps, see also Cross-Application Preparations [page 92].

Business Functions

Business functions can have the following status: always on, customer switchable, and always off.
This results in the following behavior during the process:

• If a business function was switched on in the start release system but defined as always off in the
target release, then a system conversion or upgrade is not possible with this release.
• If a business function was switched off in the start release system but defined as always on in the target
release, then the business function will be activated during the process.
• If a business function is defined as customer switchable in the target release, it will keep the state defined
in the source release during the upgrade.

For more information about always off and always on business functions in SAP S/4HANA foundation, see SAP
Notes 2240359 and 2240360 .

Add-Ons

Add-ons are either merged into SAP S/4HANA foundation or deleted during the process if no successor is
available. Some add-ons may be included without being fully functional.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
Server Release PUBLIC 91
For a list of supported add-ons in the target stack, see the respective Release Information Note for the product
version of SAP S/4HANA foundation in the target stack.

For information about uninstalling add-ons, see SAP Note 2011192 .

3.1.2.1.4 Cross-Application Preparations

Before starting the process, you need to do the preparatory activities described in the next sections.

Prepare the Use of the Maintenance Planner

Context
Besides the general preparation described in the Maintenance Planner User Guide, you have to make the
following specific preparatory steps:

Procedure
1. Setup the Maintenance Planner as described in the Maintenance Planner User Guide available at http://
help.sap.com/maintenanceplanner.
2. Check the SPAM/SAINT version in your source release system.

 Note

SPAM/SAINT patch 66 (or higher) is required.

3. Apply SAP Note 2186164 to your SAP Solution Manager system.

4. Create an RFC connection between your source release system and SAP Solution Manager:
1. In SAP Solution Manager, choose SOLMAN_WORKCENTER Solution Manager Administration
Landscape (Technical Systems) .
2. Click RFC connections Start New Window .
3. Select client 000 and choose Advanced Mode.
4. Under Export Options, fill in the field Create SM_<SID>CLNT<CLNT>_READ.
5. Under Communication RFCs, select Create SM_<SID>CLNT<CLNT>_READ.
6. Select Create New User.
7. Enter a password.
8. Enter a user and password under Managed System Setup Administrator, and choose Test Login in the
group Administration Users to check that it works.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
92 PUBLIC Server Release
Remove Client 066

Context
Client 066 is the Early Watch client which was set up during the installation of your system. This client is not
used in SAP S/4HANA foundation. To prevent issues, for example, with job scheduling, you have to remove it
before starting the process.

Procedure
To remove client 066, proceed as described in SAP Note 1749142 .

3.1.2.2 Realizing the Conversion

After the preparation phase, you start with the realization of the conversion to SAP S/4HANA foundation using
the Software Update Manager (SUM) tool.

Software Update Manager (SUM) is the technical tool used for the system conversion to SAP S/4HANA
foundation.

 Note

You have to run the Maintenance Planner before the SUM, because the SUM requires the stack.xml
generated by the Maintenance Planner as an input. For more information, see Maintenance Planner [page
91].

Within the SUM process the following steps are done in a one-step procedure (for dedicated start releases):

1. Database migration (optional)

If your source system is not yet running on the SAP HANA database, use the database migration option
(DMO) of the Software Update Manager to migrate your database to SAP HANA during the conversion.
2. Installation of the SAP S/4HANA foundation software
3. Conversion of your data into the new data structure used by SAP S/4HANA foundation (this is the
automated part of the data migration).

For all information about using the SUM, see the System Conversion Guide available at http://help.sap.com/
sltoolset Software Logistics Toolset System Maintenance System Maintenance Scenarios System
Conversion to SAP S/4HANA using SUM 2.0 <latest SP> .

3.2 SAP S/4HANA

You can find overview information about how to move from SAP ERP to S/4HANA 2022 on the SAP Help Portal:
S/4HANA

As a first step, please see the Getting Started Guide.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
Server Release PUBLIC 93
For detailed information about how to plan and realize your conversion, please see the Guides below the
Implement tab. Here, you can find all relevant Information. Please see the Conversion Guide, which supports
the conversion from SAP ERP to SAP S/4HANA.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
94 PUBLIC Server Release
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:

• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using
such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.

Conversion Guide for SAP Global Trade Services, edition for SAP HANA
Important Disclaimers and Legal Information PUBLIC 95
www.sap.com/contactsap

© 2024 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN