SAP GTS

SAP BusinessObjects Global Trade Services 8.0

Preferred Practice

US – Automated Export Systems (AES)

SAP BusinessObjects September 2010

2

©SAP Labs LLC. 2010

SAP BUSINESSOBJECTS GLOBAL TRADE SERVICES 8.0

PREFERRED PRACTICE US - AES

SANCTIONED PARTY LIST OFFLINE SCREENING UPLOAD

Introduction

SAP BusinessObjects Global Trade Services release 8.0 provides automatic communications with the US

Customs and Border Patrol (CBP) system – Automated Export System (AES).

As of June 2, 2008 the CBP released this notice.

Mandatory Automated Export System (AES) Filing for all Shipments Requiring Shipper’s Export Declaration (SED) information The U.S. Census Bureau has issued the final rule implementing provisions in the Foreign Relations Authorization Act, Public Law 107-228. This rule was published in the Federal Register on June 2, 2008, amending Title 15, Code of Federal Regulations, Part 30, Foreign Trade Regulations (FTR) in its entirety. Effective July 2, 2008, the Census Bureau is requiring mandatory filing of export information through the Automated Export System (AES) or through the AESDirect for all shipments where a Shipper’s Export Declaration (SED) is required. We are also providing the trade an additional 90 days to implement these new requirements. After the 90-day implementation period, which ends September 30, 2008, you must file your export information electronically through the AES or AESDirect. Additionally, these new regulations have tougher penalty provisions that affect everyone in the export process. Penalties may be imposed per violation of the FTR from $1,100 to $10,000 both civil and criminal, for the delayed filing, failure to file, false filing of export information, and/or using the AES to further any illegal activity. Also, all AES filers are faced with new filing deadlines by mode of transportation for reporting export information. It is important that you understand these new requirements so that you avoid the increased penalties and seizure of your commodities. The Census Bureau has instructed filers of export information to make every effort to submit these data via the AES or AESDirect to eliminate the use of paper SEDs immediately. During the 120-day implementation phase, the Census Bureau will use “informed compliance” to outreach to filers identified in violation of the FTR. Anyone submitting paper after September 30, 2008 will be in violation of the FTR and subject to penalties.

The following is a guide for the implementation of the functionality of US AES with SAP BusinessObjects

Global Trade Services 8.0 and SAP ERP 6.0 as a preferred practice. With this document and SAP standard

GTS configuration guides, the implementer should be able to set up the communication between the SAP

BusinessObjects Global Trade Services 8.0 system and the customs office system successfully.

3





Prerequisites

PREREQUISITE DETAILS

SAP BusinessObjects Global

Trade Services

SAP BusinessObjects Global Trade Services Release 8.0 Required

Required components and Support Packages for SLL-LEG 800

SAP_BASIS 700 SAPKB70017

SAP_ABA 700 SAPKA70017

PI_BASIS 2005_1_700 SAPKIPYJ7H

SAP_BW 700 SAPKW70019

SAP_AP 700 SAPKNA7009

Support Packages for SLL-LEG 8.00

Notes: 1308225, 1323790, 1336999, 1358751, 1374015, 1381113, 1407571, 1433953 1432686, 1453424

SAP ERP feeder system for

logistics processing

SAP ERP 6.0 – Configuration and enhancements will need to be done to determine

the billing documents and information that come over to SAP BusinessObjects

Global Trade Services Customs Processing. (Not included in this documentation.)

ERP plug-in for SAP BusinessObjects Global Trade Services

Note 858706

SEEBURGER Converter One of the converters that can be used for the EDI communication. Plan and budget for approximately one week of time and cost for SEEBURGER Consulting. The converter (client software, interface maps) is included in the GTS license, but the installation and configuration activities performed by SEEBURGER are not. Here is the contact information of SEEBURGER: Phone: +1 (770) 604-3888 Website: http://www.seeburger.com/. Please refer to SAP OSS notes 1307709 and 1453578 for detailed mapping information.

Customs Communication

Authorization

Request and receive authorization for electronic communication with a Customs

Office, this would include ID and password.

Letter of Intent Complete and submit a letter of intent to US Customs as soon as possible. It can take a long time (months) to have a Customs Case Officer assigned and engaged. i. You can find the LOI form here: http://www.cbp.gov/xp/cgov/trade/automated/aes/letter_intent/form_commodity_data.xml ii. And instructions/overview here: http://www.cbp.gov/xp/cgov/trade/automated/aes/letter_intent/register.xml

IDoc Customizing IDocs are used for communication with customs offices. IDocs capture the

necessary data used by the SEEBURGER converter to send information to customs

offices in the correct format.

https://service.sap.com/sap/support/notes/858706

http://www.seeburger.com/

http://www.cbp.gov/xp/cgov/trade/automated/aes/letter_intent/form_commodity_data.xml

http://www.cbp.gov/xp/cgov/trade/automated/aes/letter_intent/form_commodity_data.xml

http://www.cbp.gov/xp/cgov/trade/automated/aes/letter_intent/register.xml

4





Scenario Description

This process describes the export of product from IDES US, USA to IDES AG, Germany. The product is

subject to authorization. The foreign trade relevant activities are fully integrated in the logistic process. The

relevant export documents for AES are available and can be printed at the end of the process.

Process Diagram

Note:

The Commercial Invoice is not shipped “out-of-box” with the standard process.

SAP recommends SEEBURGER converter as the EDI converter, which is covered in this document. But,

you have choice to use other ones.

5





Step-By-Step Procedure

Part I: Steps need to perform or verify after upgraded from previous releases to SAP BusinessObjects Global

Trade Services 8.0

1. Verifying the Message Scheme

2. Adding New Partner Functions

3. EAR License Types – Compliance Management Integrated Scenario

4. Changes in the Inbond Code and Filing Option Indicator

5. EDI Converter Mapping Upgrade

Part II: Steps to Customize US AES in a newly installed SAP BusinessObjects Global Trade Services 8.0

system

1. Foreign Trade Organization and Legal Unit

2. Configure the Legal Regulation

3. Define and Assign the Determination Procedure

4. Activate Legal Regulation

5. Configure Messages for PPF Actions

6. Check Electronic Messages

7. Customs Management Service Control

8. Setup Process Flow For Customs Processing With AES

9. Define Rules for Message Output

10. Customs Code Lists

11. Partner Group

12. EAR License Types – Compliance Management Integrated Scenario

13. Document Type

14. Customizing Communication Process

15. Print Control for Documents

16. Printer Determination

17. Defaulting Data

18. Sample Messages

6





Part I: Steps After Upgraded to SAP BusinessObjects

Global Trade Services 8.0

In this section, the steps required for AES after upgraded from previous release to SAP BusinessObjects

Global Trade Services 8.0 is described.

1. Verifying the Message Scheme

Verify the Message Scheme and Electronic Message IDs

In the SAP BusinessObjects Global Trade Services 8.0 system, the new message scheme for US export is

“CUS_US_2”.

In transaction SM31, call the view “/SAPSLL/V_TLEEME” in maintenance view for the message scheme

“CUS_US_2”:

To display the details of electronic message ID, select the message ID and click “Details”.

To change the customizing of electronic message ID, highlight the Message ID and click “Display →

Change” to edit.

7





Double-check the highlighted three electronic message IDs.

Make sure the electronic message ID to the authorities (AES2), and the responses (CSFR, CSWR) are set up

as shown in the screenshots below:

8





Check the Message Definitions

Enter transaction code SPRO and choose SAP Global Trade Services → SAP Customs Management →

General Settings → Communication Processes → Define Messages for Communication Processes

Search for the message M0410 – Export Declaration Option 2 (US) and double-click on it:

9





The upgrade to this release changes the message definition of M0410 with “out-of-box” default values. You

need to make sure the “Action Definition” is the same as it was before the upgrade in your system. You need

to change the value back to the value before the upgrade. The “out-of-box” default value for the field is

“US_CU_EX_CUSEX_M_UAES2”. Notice that the default value for the field “Incompleteness Schema” is

“US_EX_AES2”.

The function module for Incompleteness Schema “US_EX_AES2” is updated with a new one. Please see the

next section for details.

Then, verify the messages I1560 - Commodity Shipment Filing Response (US) and I1570 - Commodity

Shipment Warning Response (US).

Double-click on each message and make sure they are maintained according to the screenshots below

respectively. Pay attention to the values of Message Scheme, Message ID and the checkbox “Document

Update”.

10





I1560:

I1570:

New Function Module for Incompleteness Checks

The incompletion procedure should use the new function module /SAPSLL/CHECK_US_CUS_AES2_RE1.

This can be verified with the following menu path:

11






General Settings → Document Structure → Control Incompleteness Checks in Customs Shipments and

Customs Declarations

2. Adding New Partner Functions

Partner functions are combined in a group for US exports. The partner function group controls which types of

functions are displayed in the customs declaration. When upgraded from previous releases to this release,

four new partner functions need to be included in the partner function group PGCEUS.

Forwarding Agent

One of the new partner functions is CUSSTP (Forwarding Agent). It has the partner function type CUSSTP

assigned. This partner function is required when filing export declaration with an employed forwarding

agent. When this partner function is used, a contact person is required as well (more details about contact

persons in the next section).

The partner function SP (Freight Forwarder) in previous releases is renamed to “Carrier/Fr. Fwd” (Carrier or

Freight Forwarder) in this release. It has the partner function type CUSFRW assigned. The partner function of

“Carrier/Fr. Fwd” is always required, as the value of SCAC/IATA in the message sent to the AES system is

taken from the business partner master data of “Carrier/Fr. Fwd”.

As a summary, this new release supports the following AES filing scenarios:

1) AES self-filer without forwarding agent

2) AES self-filer with employed forwarding agent (new in this release)

However, this new release does not support the following AES filing scenario:

3) Forwarding Agent filing on behalf of USPPI (U.S. Principle Party in Interest)

Contact Persons

The other three new partner functions are:

1) CTPSTP - Contact person for Forwarding Agent*

2) CTPEMP - Contact person for Intermediate Consignee

3) CTPEND - Contact person for Ultimate Consignee

12





* This partner function is required if the partner function CUSSTP is used in the customs declaration.

Partner Function Group

Verify that the new partner functions are in the partner function group PGCEUS with the following menu

path:

Enter transaction code SPRO and choose SAP Global Trade Services → General Settings → Partner

Structure → Define Groups of Partner Functions

Select the partner group PGCEUS - Partner Group for Export "Customs Processing" - U.S. and double-click

on the folder “Assign Partner Function”. Check if all the partners are included as shown in the screenshot

below, specifically those highlighted new partner functions.

13





3. EAR License Types – Compliance Management

Integrated Scenario

With correct customizing of license types in compliance management, all required EAR license information

will be automatically copied to the “Documents/Evidence” tab at item level in customs declaration.

Note: this works only if you use the compliance management for license control, meaning previous customs

documents created in compliance management are based on sales orders and/or deliveries from feeder

system.

Assign Customs Code Lists Procedure to Legal Regulations

First, maintain the relationship between the legal regulation, the customs code list and the customs procedure.


General Settings → Customs Code Lists → Assign Customs Code Lists Procedure to Legal Regulations

14





Enter the legal regulation, and select the value “Type of Previous Document/Document/Certificate” from the

dropdown of the “Code List Object”. Finally, select the value “CUSUS” from the dropdown of “Procedure”

to assign it to the legal regulation.

Maintain Customs Code Lists for Legal Regulation

Maintain the previous documents for CUII types with compliance License and License Exemption Type

Codes (AES Appendix F - License and License Exemption Type Codes). It helps ensure the official code is

used in the communication with customs authorities.


General Settings → Customs Code Lists → Maintain Customs Code Lists for Legal Regulation

http://www.cbp.gov/linkhandler/cgov/trade/automated/aes/tech_docs/aestir/june04_intro/appendices/apndx_f.ctt/apndx_f.doc

15





Enter the legal regulation and click the “Execute” button. Then, select the “Type of Previous

Document/Document/Certificate” from the Custom Code Lists dropdown.

Click the “Maintain” button to enter all the License and License Exemption Type Codes (AES Appendix F -

License and License Exemption Type Codes) for the CUII category as shown below.

There should be a license type in compliance management for each of the CUII categories maintained in the

above screenshot. For example, there are two NLR CUII entries in the table above (C32 and C33), there

should be two different NLR license types defined in compliance management.

License Type Customizing

The default data of license information for customs declaration can be customized in the definition of the

corresponding license type in compliance management:

Enter transaction code SPRO and choose SAP Global Trade Services → SAP Compliance Management →

Legal Control Service → Define License Types



16





Select the license type EXCPT of legal regulation EAR, for example. Scroll down to the section “Default

Data for SAP Customs Management” and maintain the “Type of Doc: Customs Declar” as per the screenshot

below. The field “Doc. Type: Customs Declaration” should have the specific license type as per AES

Appendix F - License and License Exemption Type Codes:

Once a license is assigned to a previous customs document in compliance management, the same license

information will be copied to the customs declaration in the “Documents/Evidence” tab at item level. The

advantage of this feature over the previous releases is that you can see and verify the assigned license in the

customs declaration now. In case you do not use the GTS system for compliance management, you can

manually enter the license information here.

In addition, you have the option to add or modify the license data for customs declaration in the method

“MODIFY_IDOC_VIEW” of the BAdI “BAdI for EDI Outbound Processing and Incompleteness Checks”.

You can find the BAdI with the following path:


Business Add-Ins for SAP Customs Management → BAdI for EDI Outbound Processing and Incompleteness

Checks

The table below shows the EAR data required for the fields of the method “MODIFY_IDOC_VIEW”. They

are stored in the internal table “CS_ECC_CUHD-HD-HD_IT-IT_DOC”. Please note that this internal table

should be filled for each line item. This means that for each record of the table “CS_ECC_CUHD-HD-

HD_IT”, the first record of the embedded table “IT_DOC” has to be populated with the values as following:

Field in internal table

X.12 Segment and Name

Example

CS_ECC_CUHD-HD-

HD_IT-IT_DOC

QALDOC N/A. Internal GTS technical requirement and must be 'CUII' CUII

PAPTY X.107 - LICENSE CODE/LICENSE EXEMPTION CODE C32

PAPNO X.102 - EXPORT LICENSE NUMBER NLR

KSAEX X.103 - Export License Status Code 1

ECCN X.116 - EXPORT CONTROL CLASSIFICATION NUMBER

(ECCN)

EAR99

ORI X.109 - FOREIGN/DOMESTIC ORIGIN INDICATOR D



17





4. Changes in the Inbond Code and Filing Option Indicator

Inbond Code

In previous releases, US AES required field “Inbond Code” (segment M12 in X.12 format) was being

mapped from the line item level, in the tab “Placement”, field “Custs Status Plct” in the customs declaration.

Here is a screenshot from the previous release:

Since the “Inbond Code” is required to report at header level by US AES, starting from this release, this field

is mapped from the header level, in the tab “Transportation”, field “Customs Status”.

Here is a screenshot from this new release:

Please refer to the following table for the field changes of “Inbond Code” in customs declaration:

Object In previous releases of GTS system In new release of GTS system

18





Inbond Code

Item level, Placement tab, field

Custs Status Plct

Header level, Transportation tab, field

Customs Status

Accordingly, the proposed values for this field are now maintained in the Customs Code List “Customs

Status” with the following menu path.


Customs Code List → Maintain Customs Code Lists for Legal Regulation

Fill in the legal regulation and select the “Customs Status” from the Customs Code List dropdown. Make sure

the highlighted customs statuses are defined. They are new in this release.

As the values of import and export are mixed together in this Customs Code List, the values of export must

be assigned to the export process CUSEX with the following menu path.


Customs Code List → Assign Customs Status to a Process and Legal Regulation

19





20





Filling Option Indicator

The “Filing Option Indicator” (record YNQ01 in X.12 Format) in previous releases used the field “Customs

Status” in “Transportation” tab, at the header level.

Here is a screenshot from the previous release

Starting from this new release, the “Filing Option Indicator” is now mapped to the field “Declar. Type” in

“Transportation” tab, at the header level.

Here is a screenshot from this release:

Please refer to the following table for the field changes of “Filling Option Indicator” in customs declaration:

Object In previous releases of the GTS

system

In new release of GTS system

Filling Option Indicator Header level, Transportation tab, field

Customs status

Header, Transportation tab, field

Declar Type field

21





Accordingly, the proposed values for this field are now maintained in the Customs Code List “Declaration

Type” with the following menu path.



Fill in the legal regulation and select the “Declaration Type” from the Customs Code List dropdown. Make

sure the highlighted entry types are defined. They are new in this release.

Since the values of import and export are mixed together in this Customs Code List, the values of export

must be assigned to the export process CUSEX with the following menu path.


Customs Code List → Assign Declaration Type to a Process and Legal Regulation:

22





5. EDI Converter Mapping Upgrade

In this new release, a new IDoc type is used for the outbound customs declaration message.

In transaction WE20, you can verify that the new IDoc type “/SAPSLL/CCECUS02” is assigned to the logical

message type “/SAPSLL/CUS_EXP”.

Accordingly, an EDI mapping update with this new IDoc type is needed in the EDI converter when

upgrading from previous releases to this new release. Make sure to discuss with your EDI converter provider

(such as SEEBURGER) to update the mapping with this new IDoc type.

23





Part II: Steps to Customize US AES in a newly

Installed SAP BusinessObjects Global Trade Services

8.0 system

In this section, the steps required to customize US AES scenario in a new installation of SAP

BusinessObjects Global Trade Services 8.0 system is described.

1. Foreign Trade Organization and Legal Unit

The GTS system uses the SAP business partner concept. You create a business partner for each party (person,

organization) involved in foreign trade business. Within the individual business transactions, such as an

import transaction, a business partner can take on various partner functions, providing the business partner

meets the relevant requirements.

When creating both foreign trade organization and legal unit, you have to at least enter the address and assign

the relevant role for each business partner.

Foreign Trade Organization

Enter transaction code SPRO and choose SAP Global Trade Services → General Settings → Organizational

Structure → Define Foreign Trade Organizations

24





Maintain the business partner role “SLLFTO” for Foreign Trade Organization:

Legal Unit


Structure → Define Legal Units

25





Maintain the business partner role “SLLSIT” for Legal Unit:

Assign Company Code to Foreign Trade Organization


Structure → Assignment of Organizational Units from Feeder System to Foreign Trade Org:

26





The Foreign Trade Organization (FTO) can be assigned at Feeder System Level or Feeder System Group

Level. It depends on if you have set up a Feeder System Group or not.

You can manually assign or automatically transfer company codes from feeder system to FTO.

If you choose to do it automatically, double-click on “Automatically Transfer Company Code”. You will

have to enter the Logical System (Feeder System) from where data is to be transferred, and enter the FTO to

assign the company code.

If you choose to do it manually, double-click on “Manually Assign Company Code”, and then select the

button “New Entries”. Enter the company code information and match it to your desired FTO.

Assign Legal Unit to Foreign Trade Organization


Structure → Assign Legal Unit to the Foreign Trade Organization:

27





Assign Plant from Feeder System to Legal Unit


Structure → Assignment of Organizational Units from Feeder System to Legal Unit

You can assign the plant from feeder system to the legal unit either at Feeder System or Feeder System

Group level. You have the options to do it manually or automatically. If you select to do it automatically, you

need to enter the feeder system. If you select to do it manually, click the button “New entries”, then chose the

Legal Units to assign the plant from the feeder system.

28





2. Configure the Legal Regulation

Legal regulations are the central control elements for services performed in the GTS system. Here you define

which laws are checked for export and import processes. In addition, you assign different deadline types to

each legal regulation and the country groups a legal regulation is valid for. If country groups are used during

the license determination, you need to define the country groups first.

Enter transaction code SPRO and choose SAP Global Trade Services → General Settings → Legal

Regulations → Define Legal Regulation

29





Note:

1) This legal regulation represents the procedure of AES

2) The Type of Legal Code is: Customs Processing

3) The country from which the legal regulation was issued is: US

3. Define and Assign the Determination Procedure

You have to enter a determination procedure to enable the system to determine the legal regulations for a

service. To do so, you assign the determination table to the determination procedure. The system can then

uses the departure country (export) and the destination country (import) to determine the legal regulations.

You can also define for each determination procedure whether the system stops determination as soon as it

finds the first active legal regulation or whether it goes through all the available active legal regulations for

the service. If your logistics processes involve several countries and legal regulations in a service, this lets

you perform the checks and determination for several legal regulations.

30





Define Determination Procedure


Regulations → Define Determination Procedure for Active Legal Regulations

Assign Determination Procedure to Service


“Customs Processing” Service → Assign Determination Procedure for Active Legal Regulations

31





4. Activate the Legal Regulation

Here you activate the legal regulations for each departure country or country group (export) and destination

country or country group (import). This enables you to specifically define the validity area of a legal

regulation.

Activate the Legal Regulation for a Country


Regulations → Activate Legal Regulations at Country/Country Group Level

In this case, the departure country for export is US.

Activate the Legal Regulation for Export

Here you activate the legal regulations for each departure country or country group (export) and destination

country or country group (import) for each service that will be active in the GTS system.

Enter transaction code SPRO and choose SAP Global Trade Services → Customs Management → “Customs

Processing” Service → Activate Legal Regulations

32





5. Configure Messages for Post Processing Framework

Actions for Customs Shipments/Declarations

The configuration of the Post Processing Framework (PPF) defines the technical medium that the GTS

system uses to communicate with the US Customs offices.


General Settings → Communication Processes → Define Techn. Medium for Msgs (PPF Actions) from

Cust.Shipm. and Cust.Decl.

Action Definition

33





Process Type


General Settings → Communication Processes → Define Conditions and output Parameters for Comm. of

Cust. Ship. & Cust. Dcl

34





6. Check Electronic Messages

Double-check Electronic Message ID

These are electronic messages that the GTS system uses to communicate with the US customs authorities as

the customs declaration.

In transaction SM31, call the view “/SAPSLL/V_TLEEME” in maintenance view for the message scheme

“CUS_US_2”:

To display the details of electronic message ID, select the message ID and click “Details”. To change the

customizing of electronic message ID, highlight the message ID and click “Display → Change” to edit.

35





Double-check the highlighted three electronic message IDs. Make sure the electronic message ID (AES2) to

the US customs authorities and responses (CSFR, CSWR) are set up as shown in the screenshots below:

36





Check Message Definitions


General Settings → Communication Processes → Define Messages for Communication Processes

Search for the message M0410 – Export Declaration Option 2 (US).

37





Make sure it is maintained with the values as shown below:

Then, verify the messages I1560 - Commodity Shipment Filing Response (US) and I1570 - Commodity

Shipment Warning Response (US).

Double click on each message and make sure they are maintained according to the screenshots below

respectively. Pay attention to the values of Message Scheme, Message ID and the checkbox “Document

Update”.

38





I1560:

I1570:

39





If you need to print the Shipper’s Export Declaration (SED), check out the message P0360 and verify its

settings. Perform the same action to other printing documents.

40





Verify the Function Module for Incompletion Checks

The incompletion schema should be configured to use the function module

“/SAPSLL/CHECK_US_CUS_AES2”. This can be checked with the menu path:

Enter transaction code SPRO and choose SAP Global Trade Services →SAP Customs Management →

General Settings → Document Structure → Control Incompleteness Checks in Customs Shipments and

Customs Declarations

7. Customs Processing Service Control

You specify the possible status, status sequence and time zone for the authorizations. You also assign process

template to a legal regulation.


“Customs Processing” Service → Control Settings for “Customs Processing” Service

41





8. Set up Process Flow for Customs Processing with AES

In order to declare export goods with the US government electronic customs system, AES, you must define a

process flow that allows you to electronically communicate with the US customs authorities. The process

template is where electronic messages are attached for entering and sending a Customs Export Declarations.

If your export declaration is accepted, the customs authorities send you a confirmation with a registration

number (confirmation number).

Define Process Template

You assign the schema “CUS_US_2” for electronic messages to this process template.


General Settings → Communication Processes → Define Control Settings for Communication Processes

42





Define Processes

Define communication process with customs authorities, for example “CUSEX” for US export.

Define Activities

You can logically group messages into activities for the chosen process. In the example below, one activity

(CUSEX) is set up for electronic messages and another one (CUSE2) for printed messages.

Assign Messages to Activities

You assign messages to activities. The screenshot below shows that messages for electronic communication

with US AES are assigned to the activity “CUSEX”.

If you chose to have a single activity for the US export process, add the printed messages into this activity as

well. If you prefer having another activity for all the printed messages, assign those printed messages to that

separate activity.

43





Define Activity Sequences

You define the activity execution order in the Subsequent Activities level. The example below shows that the

process of electronic messages (CUSEX) is followed by the printed messages (CUSE2). In another words, the

printed messages will not be executed until the process of electronic messages is completed.

The delivered customizing only allows you to process the printed messages until the first activity is finished.

If you would like to print regardless of the electronic communication, you can configure a single activity with

both electronic and printed messages.

44





Define Fall-back Activities Sequence

Here, you define the default activity sequence in case the AES system is down, or the communication

between the GTS system and the AES system is broken. The example shown here indicates that printed

messages are the fallback procedure.

9. Define Rules for Message Outputs

Once the Post Processing Framework (PPF) is properly configured, it is necessary to tell the GTS system

which messages are expected to appear under the “Communication” tab of the export declaration. This is

specified in default rules of output determination:

Open the area menu in the GTS system with transaction code /SAPSLL/MENU_LEGAL and choose SAP

Customs Management → Master Data → Default Data → Define Rules for Output Determination

Select the procedure “COEUS” Messages – Export – U.S. and your legal regulation for US customs exports.

At a very minimum level, you should select the outbound AES message (M0410); plus all the printed

messages you expect to be processed:

45





10. Customs Code Lists

Define Customs Code List Procedure

The customs code lists are issued by customs offices. You need the customs codes for communications with

customs authorities, and in particular for the exchange of electronic messages. The customs codes are

officially valid values which enable customs authorities to precisely identify goods, means of transport and

other general attributes for import and export processes.

As a first step, a customs code list procedure is created so that custom codes can be assigned to it.

Enter transaction code SPRO and choose SAP Global Trade Services → Customs Management → General

Settings → Customs Code Lists → Define Procedures for Customs Code List

46





Assign Customs Code List

In this step, you select which customs code lists are valid for your legal regulation.


Customs Code List → Assign Customs Code Lists Procedure to Legal Regulations

Maintain Customs Code Lists

Maintain values of customs code lists for legal regulations with the following menu path:



Below are the values of the customs code lists “Range of Goods” and “Customs Status”:

47





Since the values of import and export are mixed together in the customs code list “Customs Status” above,

the values of export must be assigned to the export process CUSEX with the following menu path:


Customs Code List → Assign Customs Status to a Process and Legal Regulation

48





Below are the values of the customs code list “Declaration Type”.

Since the values of import and export are mixed together in the customs code list “Declaration Type” above,

the values of export must be assigned to the export process CUSEX with the following menu path:


Customs Code List → Assign Declaration Type to a Process and Legal Regulation:

49





11. Partner Group

Partner functions are combined in a group for US Exports. The partner function group controls which types

of functions are displayed in the customs declaration. When upgraded from previous releases to this new

release, four new partner functions need to be included in the partner function group “PGCEUS”.

Enter transaction code SPRO and choose SAP Global Trade Services → General Settings → Partner

Structure → Define Groups of Partner Functions

Forwarding Agent

One of the new partner functions is CUSSTP (Forwarding Agent). This partner function is required when

filing an export with an employed forwarding agent (new functionality for this new release). When this

partner function is used, a contact person is required as well (more details about contact persons in the next

section).

The partner function SP (Freight Forwarder) in previous releases is renamed to “Carrier/Fr. Fwd” (Carrier or

Freight Forwarder) in this new release. The “Carrier/Fr. Fwd” is always required, as the value of

SCAC/IATA in the message sent to the AES system is taken from the business partner master data of

“Carrier/Fr. Fwd”.

As a summary, this release supports the following AES filing scenarios:

1) AES self-filer without forwarding agent

2) AES self-filer with employed forwarding agent (new in this release)

However, this release does not support the following AES filing scenario:

3) Forwarding Agent filing on behalf of USPPI (U.S. Principle Party in Interest)

Contact Persons

The other three new partner functions are:

1) CTPSTP - Contact person for Forwarding Agent*

2) CTPEMP - Contact person for Intermediate Consignee

3) CTPEND - Contact person for Ultimate Consignee

* This partner function is required if the partner function CUSSTP is used in the customs declaration.

Partner Function Group

Verify that the new partner functions are in the partner function group PGCEUS with the following menu

path:

Enter transaction code SPRO and choose SAP GTS → General Settings → Partner Structure → Define

Groups of Partner Functions

50





Select the partner group PGCEUS - Partner Group for Export "Customs Processing" - U.S. and double-click

on the folder “Assign Partner Function”. Check if all the partner functions are included as shown in the

screenshot below, specifically those highlighted new partner functions.

51





12. EAR License Type – Compliance Management

Integrated Scenario

With correct customizing of license types in compliance management, all required EAR license information

will be automatically copied to the “Documents/Evidence” tab at item level in customs declaration.

Note: this works only if you use the compliance management for license control, meaning previous customs

documents created in compliance management are based on sales orders and/or deliveries from feeder

system.

Assign Customs Code Lists Procedure to Legal Regulations

First, maintain the relationship between the legal regulation, the customs code list and the customs procedure.


General Settings → Customs Code Lists → Assign Customs Code Lists Procedure to Legal Regulations

52





Enter the legal regulation, and select the value “Type of Previous Document/Document/Certificate” from the

dropdown of the “Code List Object”. Finally, select the value “CUSUS” from the dropdown of “Procedure”

to assign it to the legal regulation.

Maintain Customs Code Lists for Legal Regulation

Maintain the previous documents for CUII types with compliance License and License Exemption Type

Codes (AES Appendix F - License and License Exemption Type Codes). It helps ensure the official code is

used in the communication with customs authorities.


General Settings → Customs Code Lists → Maintain Customs Code Lists for Legal Regulation


53





Enter the legal regulation and click the “Execute” button. Then, select the “Type of Previous

Document/Document/Certificate” from the Custom Code Lists dropdown.

Click the “Maintain” button to enter all the License and License Exemption Type Codes (AES Appendix F -

License and License Exemption Type Codes) for the CUII category as shown below.

There should be a license type in compliance management for each of the CUII categories maintained in the

above screenshot. For example, there are two NLR CUII entries in the table above (C32 and C33), there

should be two different NLR license types defined in compliance management.

License Type Customizing

The default data of license information for customs declaration can be customized in the definition of the

corresponding license type in compliance management:

Enter transaction code SPRO and choose SAP Global Trade Services → SAP Compliance Management →

Legal Control Service → Define License Types



54





Select the license type EXCPT of legal regulation EAR, for example. Scroll down to the section “Default

Data for SAP Customs Management” and maintain the “Type of Doc: Customs Declar” as per the screenshot

below. The field “Doc. Type: Customs Declaration” should have the specific license type as per AES

Appendix F - License and License Exemption Type Codes:

Once a license is assigned to a previous customs document in compliance management, the same license

information will be copied to the customs declaration in the “Documents/Evidence” tab at item level. The

advantage of this feature over the previous releases is that you can see and verify the assigned license in the

customs declaration now. In case you do not use the GTS system for compliance management, you can

manually enter the license information here.

In addition, you have the option to add or modify the license data for customs declaration in the method

“MODIFY_IDOC_VIEW” of the BAdI “BAdI for EDI Outbound Processing and Incompleteness Checks”.

You can find the BAdI with the following path:


Business Add-Ins for SAP Customs Management → BAdI for EDI Outbound Processing and Incompleteness

Checks

The table below shows the EAR data required for the fields of the method “MODIFY_IDOC_VIEW”. They

are stored in the internal table “CS_ECC_CUHD-HD-HD_IT-IT_DOC”. Please note that this internal table

should be filled for each line item. This means that for each record of the table “CS_ECC_CUHD-HD-

HD_IT”, the first record of the embedded table “IT_DOC” has to be populated with the values as following:

Field in internal table

X.12 Segment and Name

Example

CS_ECC_CUHD-HD-

HD_IT-IT_DOC

QALDOC N/A. Internal GTS technical requirement and must be 'CUII' CUII

PAPTY X.107 - LICENSE CODE/LICENSE EXEMPTION CODE C32

PAPNO X.102 - EXPORT LICENSE NUMBER NLR

KSAEX X.103 - Export License Status Code 1

ECCN X.116 - EXPORT CONTROL CLASSIFICATION NUMBER

(ECCN)

EAR99

ORI X.109 - FOREIGN/DOMESTIC ORIGIN INDICATOR D



55





13. Document Type

Define Document Type

Define the document type for Export Customs Processing services in Customs Management.


General setting → Document Structure → Define Document Types

Activate the Document Type

Activate the document type for Export Customs Processing services in Customs Management.


General setting → Document Structure → Activate Document Types

Assign the Document Type from Feeder Systems

Assign the document type for Export Customs Processing services in Customs Management to document

types from feeder system at Feeder System or Feeder System Group Level.


General setting → Document Structure → Assignment of Document Types from Feeder Systems

56





In the pop-up, select application level SD0C and enter the document type from the Feeder System or Feeder

System Group that triggers the creation of the export customs declaration in GTS:

Define Item Category

Define the item category for Export Customs Processing services in Customs Management.


General setting → Document Structure → Define Item Categories

Assign Item Category

Assign the item category for Export Customs Processing services in Customs Management to an item

category from a Feeder System or Feeder System Group.


General setting → Document Structure → Assignment of Item Categories from Feeder Systems

57





14. Customizing Communication Process

The following steps are used to customize how the outbound IDocs are sent out of the GTS system to the EDI

converter and from there to the customs authorities, and vice versa for the inbound IDocs.

RFC Destination

First, create a RFC destination of Connection Type “TCP/IP” with the transaction SM59.

Port

In transaction WE21, create a port in the folder “Transactional RFC” with reference to the RFC destination

defined above:

58





Partner Profile

In transaction WE20, create a partner profile under the “Partner Type GP” for each customs office you plan

to communicate with. The port for each customs office should have the outbound message type

“/SAPSLL/CUS_EXP” assigned:

59





Verify that the new IDoc type “/SAPSLL/CCECUS02” is assigned to the logical message type

“/SAPSLL/CUS_EXP”.

60





Also in transaction WE20, create a partner profile under the “Partner Type GP” for the EDI converter (for

example, SEEBURGER converter). Only one partner profile is needed for the EDI converter. The port for the

converter must have the inbound message type “/SAPSLL/CUS_INBOUND” assigned:

61





15. Print Control for Documents

The following steps are used to customize the print control that enables you to create and print the Shippers

Export Document. Other customs-relevant foreign trade documents can be customized in the same manner.


General Settings → Communication Processes → Print Control for Foreign Trade Documents

62





16. Printer Determination

The GTS system uses the legal unit and user ID to determine which output device to use for printed

messages. If you have specified this information, the printer name displays next to the printed message in the

customs declaration under the “Communication” tab.


Customs Management → Master Data → Print Processing → Configure Printer Determination

17. Defaulting Data

Based on the business rules, the GTS system allows you to default data when generating customs declarations

in customs management. Defaulting data significantly speeds up the process of creating customs declaration

documents.


General Settings → Procedures for Defaulting Data → Define Default Data for Document Fields, Messages,

and Documents

63





Default Rules

Once the rules are defined in the customizing, business user can set the declaration default values from the

GTS Area Menu based on the procedure and legal regulation.

Below is an example of how to default the office of departure based on the Foreign Trade Organization and

the Legal Unit


Customs Management → Master Data → Default Data → Define Rules for Default Document Data

64





18. Sample Messages

Messages generated with a customs declaration:

Notice that the electronic message M0410 is sent out of the GTS system to the AES system. The response

from the AES system is I1560.

65





Here is a sample outbound EDI message (X12 601) to the AES system:

Note:

The transmitter ID (EIN) and password have been blacked out in the sample files for security reason.

66





Here is a sample inbound EDI (X12 824) message with acceptance status from the AES system.

Here is a sample inbound EDI (X12 824) message with rejection status from the AES system.

67





Comments and Feedbacks

Your feedback is very valuable and will enable us to improve our documents. Please take a few moments to

complete our feedback form. Any information you submit will be kept confidential.

You can access the feedback form at: http://www.surveymonkey.com/s.aspx?sm=stdoYUlaABrbKUBpE95Y9g_3d_3d

http://www.surveymonkey.com/s.aspx?sm=stdoYUlaABrbKUBpE95Y9g_3d_3d

68





Copyright SAP Labs, LLC. 2010 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.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge 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 and associated logos

displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only.

National product specifications may vary.

The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license

agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of

the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or

development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or

completeness of the information, text, graphics, links, or other items contained within this material. This document is provided

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 have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages

that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. 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