SAP SOLUTIONS FOR GOVERNANCE,

RISK, AND COMPLIANCE

How-To Guide

How To Upload the XML File of

Customs Offices in GTS
SAP GRC Regional Implementation Group

Applicable Releases:
GTS 7.2

Version 1
December 2008

 Copyright 2008 SAP AG. 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 AG. The information contained
herein may be changed without prior notice.
Some software products marketed by SAP AG and its
distributors contain proprietary software components of
other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are
registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel
Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,
OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,
Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,
i5/OS, POWER, POWER5, OpenPower and PowerPC are
trademarks or registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader
are either trademarks or registered trademarks of Adobe
Systems Incorporated in the United States and/or other
countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered
trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame,
WinFrame, VideoFrame, and MultiWin are trademarks or
registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or
registered trademarks of W3C, World Wide Web
Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems,
Inc., used under license for technology invented and
implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP
NetWeaver, and other SAP products and services
mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in
Germany and in several other countries all over the world.
All other product and service names mentioned are the
trademarks of their respective companies. Data contained
in this document serves informational purposes only.
National product specifications may vary.

These materials are subject to change without notice.

These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only,
without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with
respect to the materials. The only warranties for SAP
Group 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.
These materials are provided as is without a warranty of
any kind, either express or implied, including but not
limited to, the implied warranties of merchantability,
fitness for a particular purpose, or non-infringement.
SAP shall not be liable for damages of any kind including
without limitation direct, special, indirect, or consequential
damages that may result from the use of these materials.
SAP does not warrant the accuracy or completeness of the
information, text, graphics, links or other items contained
within these materials. SAP has no control over the
information that you may access through the use of hot
links contained in these materials and does not endorse
your use of third party web pages nor provide any warranty
whatsoever relating to third party web pages.
SAP NetWeaver How-to Guides are intended to simplify
the product implementation. While specific product
features and procedures typically are explained in a
practical business context, it is not implied that those
features and procedures are the only approach in solving a
specific business problem using SAP NetWeaver. Should
you wish to receive additional information, clarification or
support, please refer to SAP Consulting.
Any software coding and/or code lines / strings (Code)
included in this documentation are only examples and are
not intended to be used in a productive system
environment. The Code is only intended better explain and
visualize the syntax and phrasing rules of certain coding.
SAP does not warrant the correctness and completeness of
the Code given herein, and SAP shall not be liable for
errors or damages caused by the usage of the Code, except
if such damages were caused by SAP intentionally or
grossly negligent.
Disclaimer
Some components of this product are based on Java. Any
code change in these components may cause unpredictable
and severe malfunctions and is therefore expressively
prohibited, as is any decompilation of these components.
Any Java Source Code delivered with this product is only
to be used by SAPs Support Services and may not be
modified or altered in any way.

Typographic Conventions

Icons

Type Style

Description

Icon

Example Text

Words or characters quoted

from the screen. These
include field names, screen
titles, pushbuttons labels,
menu names, menu paths,
and menu options.
Cross-references to other
documentation

Example text

Emphasized words or
phrases in body text, graphic
titles, and table titles

Example text

File and directory names and

their paths, messages,
names of variables and
parameters, source text, and
names of installation,
upgrade and database tools.

Example text

User entry texts. These are

words or characters that you
enter in the system exactly as
they appear in the
documentation.

<Example
text>

Variable user entry. Angle

brackets indicate that you
replace these words and
characters with appropriate
entries to make entries in the
system.

EXAMPLE TEXT

Keys on the keyboard, for

example, F2 or ENTER.

Description
Caution
Note or Important
Example
Recommendation or Tip

Table of Contents
1.

Business Scenario ..........................................................................................................1

2.

Background Information .................................................................................................1

3.

Prerequisites....................................................................................................................2

4.

Step-by-Step Procedure..................................................................................................3

5.

4.1

Prepare the XML file of the US customs office...........................................................3

4.2

Upload the XML file into SAP GTS system ................................................................4

4.3

Run the modification program to update the customs office identification number in
GTS..........................................................................................................................8

Appendix..........................................................................................................................9

1.

Business Scenario

The list of US Port Codes is a required master data in SAP Global Trade Services (GTS) Customs
Management and can be uploaded from an XML file. During upload, SAP GTS creates these port
codes as customs office business partners in the system. In the current release of GTS 7.2, the port
code (ex. 2809) in the XML file is used as both the external business partner number (if this option is
selected) and the office number of the customs office in GTS.
In some cases, existing business partners (ex. 2809 Vendor John Doe) in GTS may overlap with these
customs office numbers (ex. 2809 Port of San Francisco). Therefore, the upload of the XML file may
generate conflicts during the business partner creation for the customs offices.
This How-To guide provides a workaround to solve the issue while uploading the XML file of customs
offices. The goal is to create unique business partners for US customs offices (ex. US2809) and then
assign the appropriate port code (2809).

2.

Background Information

The list of US customs offices is published in the Schedule D from US Customs and Border
Protection (CBP). Each US customs office is identified with a unique 4-digit identification number in
Schedule D. In this guide, the XML file of US customs office is used to illustrate the procedure of the
workaround.
Here are the major steps of the workaround provided in this guide:
...

1. Modify the US customs office XML file

2. Upload the customs office XML file
3. Use the ABAP program found in the Appendix of this guide as a reference to correct customs
office identification number for each customs office in GTS
4. Verify the result in GTS cockpit

This guide is based on the SAP GTS 7.2 release. However, this approach can also be applied to other
SAP GTS releases.
The ABAP program in Appendix A is only a sample code for reference. Please modify it accordingly to
fit your system environment.

CAUTION
In GTS, if you have business partner external numbers in the format USxxxx where xxxx
is the 4-digit official US customs office identification number; you will run into the conflicts
that this workaround tries to solve. In this case, you need to modify the step 1 and step 3
accordingly. However, the approach remains the same.

3.

Prerequisites
Software
SAP GTS 7.2
The Compliance and Customs Management are working in your SAP GTS system.
Hardware
SAP GTS server
Required/recommended expertise or prior knowledge
Basic knowledge of SAP GTS
Basic knowledge of ABAP programming
Basic knowledge of XML.

4.

Step-by-Step Procedure

First of all, you need to get the XML file of US customs office from your data provider. The file from
CBP website is not in the XML format at the time this guide is written.

4.1

Prepare the XML file of the US customs office

...

1. Open the XML file of the US customs offices with an editor, such as notepad.
2. Add two characters US in front of the 4-digit identification number for each customs office, as
shown in following.

Note
If you already have business partners with external numbers in the format USxxxx where
xxxx is the 4-digit official US customs office identification number; you can add other
characters instead, such as ABC. However, you will need to modify the ABAP program
in the Appendix of this guide accordingly.
3. Save and close the XML file.

4.2

Upload the XML file into SAP GTS system

...

1. From the GTS cockpit, follow the navigation path:

SAP GTS Area Menu -> SAP Customs Management -> Master Data -> Customs Offices

2. Before the upload, check the existing information in GTS system for legal regulation ACE by
clicking on Maintain Customs Office Numbers.
3. Load the XML file by clicking on the Load Customs Offices from XML File in the Customs
Offices section.
4. Provide the information of Data Provider, Legal Regulation, and the full path of the XML file.
Tip
You might want to try the Simulation Mode first to make sure everything is correct
before the actual upload.

5. Click on Execution button and wait to see the message Tasks performed successfully in the
display log.
6. Click on the Save button to save the data in database.
7. Display the result of the upload by clicking on Maintain Customs Office Numbers in the
Customs Offices section (or transaction /SAPSLL/BP_MAIN_DNR).
8. Enter the legal regulation, and US* in the Business Partners selection field.

Notice the customs office identification number in the column OFN has the values in the format
USxxxx, where the xxxx is the customs office identification number. We need to remove the prefix
US created during the XML file upload to make it a 4-digit number as published by the CBP.
9. Check the business partner creation of the customs offices after the upload with transaction BP.

4.3

Run the modification program to update the

customs office identification number in GTS

...

1. Create the modification program with the sample code in Appendix A as reference, by SE38.
Modify it accordingly to fit your system environment.
2. Activate and execute the program.
3. Verify the result by clicking on Maintain Customs Office Numbers in the Customs Offices
section (or transaction /SAPSLL/BP_MAIN_DNR). The column OFN should be only assigned
with the 4-digit official US customs office number.

5.

Appendix

This is only a sample code for reference. Please modify it according to your system environment.

Appendix A - ABAP program to remove the prefix for the customs office
numbers in GTS
*&---------------------------------------------------------------------*
*& Report Z_MODIFY_OFN
*&
*&---------------------------------------------------------------------*
*& The report removes the prefix for the customs office numbers,
*& for example from 'US5582' to '5582'.
*&
*&---------------------------------------------------------------------*
REPORT Z_MODIFY_OFN.
DATA: update_needed TYPE syst-input value ' '.
DATA: l_pinid
TYPE /SAPSLL/ADRLRID-pinid.
DATA: lt_adrlrid TYPE TABLE OF /SAPSLL/ADRLRID.
FIELD-SYMBOLS <ls_adrlrid> TYPE /sapsll/adrlrid.
SELECT *
FROM /sapsll/adrlrid
INTO TABLE lt_adrlrid
WHERE pinid like 'US%'.
IF sy-subrc = 0.
LOOP AT lt_adrlrid ASSIGNING <ls_adrlrid>.
l_pinid = <ls_adrlrid>-pinid.
SEARCH l_pinid for 'US*'.
IF SY-SUBRC = 0 and ( strlen( l_pinid ) = 6 ).
<ls_adrlrid>-pinid = l_pinid+2(4).
update_needed = 'X'.
ENDIF.
ENDLOOP.
IF update_needed = 'X'.
update /SAPSLL/ADRLRID from TABLE lt_adrlrid.
IF sy-subrc = 0.
WRITE: 'The table of customs offices is updated successfully.'."#EC NOTEXT
ELSE.
WRITE: 'Table update failed.'.
"#EC NOTEXT
ENDIF.
ENDIF.
ELSE.
WRITE: 'There is no record to be updated. Everything is OK.'."#EC NOTEXT
ENDIF.