foregin trade (第4页)

第 110 页 / 共 272 页

Inbound Processing - Foreground

SAP System

Customs office

DDaattaa pprroovviiddeerrss

IDoc 02451

Import code

AAuutthhoorriittiieess IDoc 02452 Post

number

IDoc 02453

......

Business

transaction type

SAP

ª SAP AG 1999

(cid:132)(cid:3)A data provider or authority normally makes customs data available to you at regular intervals.

This data must be in syntactically correct IDoc format (FTDABA01, FTDACU01, COND_A).

(cid:132)(cid:3)If the customs data is to be processed in the foreground, a dialog-oriented processing function

appears once the IDoc has been processed initially. If the foreground processing option was

chosen, the system automatically creates a worklist from the IDoc that was received.

(cid:132)(cid:3)For foreground processing in dialog mode, the person responsible receives an e-mail message

(optional) informing him or her that this IDoc has arrived.

(cid:132)(cid:3)Now, this person can use the Import customs objects function in the Data Service Cockpit to select

the corresponding IDocs.

(cid:132)(cid:3)He or she can use drag-and-drop to select the relevant foreign-trade data from the worklist. This

data can also be checked for consistency before being transferred to the corresponding Customizing

tables or master data tables.

(cid:132)(cid:3)If the system discovers data inconsistencies, it creates an error log.

Note:

The system prevents you from entering information that does not belong in your system (information

that refers to a country that is not included in the country table, for example).

© SAP AG LO640 5-10

ID
ID oc 02451
ID IDoc

第 111 页 / 共 272 页

Inbound Processing - Background

SAP System

DDaattaa pprroovviiddeerrss

IDoc 02451

AAuutthhoorriittiieess IDoc 02452 Direct posting

IDoc 02453

...... SAP

ª SAP AG 1999

(cid:132)(cid:3)A data provider or authority normally makes customs data available to you at regular intervals.

This data must be in syntactically correct IDoc format (FTDABA01, FTDACU01, COND_A).

(cid:132)(cid:3)After initial inbound processing, the data is transferred directly into the corresponding Customizing

tables or master data tables.

(cid:132)(cid:3)If the system discovers data inconsistencies, the IDoc is rejected and given an "error" status.

(cid:132)(cid:3)Once corrections are made, the IDoc can be returned to the initial inbound processing stage, if

necessary.

© SAP AG LO640 5-11

ID
ID oc 02451
ID IDoc ID oc 02452
02453
AP

第 112 页 / 共 272 页

Distribute Customs Data

SAP - Operative system_03

SAP - Operative system_02

SAP Central customs server ALE

SAP - Operative system_01

Customs office

IDoc 01451

Import code

IDoc 01452

number IDoc 01453

Business Direct posting

transaction type

ª SAP AG 1999

Distribute customs data

(cid:132)(cid:3)In a distributed system infrastructure that separates operative systems from the central system, it is

necessary to use the ALE distribution model to distribute the customs data.

(cid:132)(cid:3)The Distribute cust. objects function is available for this purpose in the Data Service Cockpit. This

function allows you to select specific basic data and customs data for a particular country and

several languages.

(cid:132)(cid:3)Finally, 1 – n IDocs are created that provide the operative systems with information based on the

ALE distribution model. Inbound processing can then be carried out in the operative systems either

in the foreground or in the background, as described above.

Note:

A distributed scenario has the advantage that the data only needs to be maintained centrally and the

operative systems always contain data that is up-to-date.

© SAP AG LO640 5-12

SAP - Operative system_03 AP - Operative system_02 Operative system_01
S AP - Operative system_02 Operative system_01
SA P - Operative system_01
Direct posting
IDoc 01451
I ID Doc 0145 oc 01453

第 113 页 / 共 272 页

Data Service in Foreign Trade: Summary

z Wizards help you set up data services and

distribution scenarios.

z You can upload basic foreign-trade data, customs

data and customs duty rates into the corresponding

system tables.

z The system allows you to transfer specific basic

foreign-trade data and customs data.

z All customs data can also be uploaded into

Customizing tables and master data tables using

background processing.

z The ALE distribution model is used for distributing

customs data.

ª SAP AG 1999

© SAP AG LO640 5-13

第 114 页 / 共 272 页

Communication / Printing

z

Communication

(cid:132) IDoc import - purchase order

(cid:132) IDoc export - billing document

(cid:132) Automated Export System (AES) - USA

(cid:132) Application scenario

z

Printing

(cid:132) Export documents

(cid:132) Output control

(cid:132) Printing transactions

ª SAP AG 1999

© SAP AG LO640 6-1

第 115 页 / 共 272 页

Communication / Printing: Unit Objectives

At the conclusion of this unit, you should be

able to:

z

Determine which settings should be made in

the system

z

Describe how to create IDocs

z

Name the application scenarios in which you

could use these IDocs

z

Describe how to print export documents

z

Use the user enhancement V55ECTRL

ª SAP AG 1999

© SAP AG LO640 6-2

第 116 页 / 共 272 页

Communication / Printing: Overview Diagram

Introduction Communication / Printing

Basic Data Legal Control

Documents in Foreign Trade Documentary Payments

Import Basis Module Periodic Declarations

Data Service Preference Determination

ª SAP AG 1999

© SAP AG LO640 6-3

第 117 页 / 共 272 页

Communication - Future Procedure

Import data becomes export data

SAP System Customs Customs SAP System

Import Export

MM SD

USA USA

Purchase ACE AES Order

order

Broker

Inbound Europe Europe Outbound

delivery In-house delivery

DE-ATLAS development DE-ATLAS

Goods

Software Goods issue

receipt

Japan Japan

Invoice TEDI TEDI Billing

document

Export data becomes import data

ª SAP AG 1999

(cid:132)(cid:3)The aim is to achieve uninterrupted communication, so that your export data immediately

becomes import data for your subsidiary, for example. The different types of documents and the

maintenance effort associated with these are not necessary.

(cid:132)(cid:3)In addition to internal company communication, you can also communicate with other business-

sector partners involved in customs, such as customs authorities, customs brokers, vendors,

customers or other authorities.

(cid:132)(cid:3)The authorities of different countries and economic zones are currently attempting to develop

standardized systems for sending foreign trade data from one business-sector partner to another

electronically. Examples of these standardized systems include ACE and AES in the USA, ATLAS

in the European Union and TEDI in Japan.

(cid:132)(cid:3)The basic principles for conversion of foreign trade data in the SAP System are outlined in the

corresponding conversion tables and in Customizing.

(cid:132)(cid:3)IDocs (Intermediate Documents) are the basis for data exchange.

© SAP AG LO640 6-4

SAP System
USA ACE Broker In-house development Software
Europe DE-ATLAS
Japan TEDI
Invoice
SAP System
USA AES
Europe DE-ATLAS
Japan TEDI

第 118 页 / 共 272 页

Basic Data

z

Basis: UN/EDIFACT - Message types

ª SAP AG 1999

© SAP AG LO640 6-5

(cid:0)

CUSDEC Customs Declaration Message

(cid:0)

CUSRES Customs Response Message

z

Using ISO (International Standards Organization) codes

z

SAP EDI Basis: Component WF-IDOC-EDI menu (below)

(cid:0)

Determine IDocs EXPINV02 and IMPINV01

(cid:0)

Define partners

(cid:0)

Define ports

z

Output control

(cid:132)(cid:3)We have chosen the internationally recognized UN/EDIFACT standard as the basis for Printing /

Communication. The most important message types in foreign trade are CUSDEC (Customs

Declaration Message) and CUSRES (Customs Response Message).

(cid:132)(cid:3)All future electronic foreign trade/customs systems or those currently being developed use these

standard messages. These include:

y(cid:3)

USA ACE - Automated Commercial Environment

y(cid:3)

Germany ATLAS - Automated tariff and local customs processing system

y(cid:3)

Austria EDV/ZOLL (Data processing/customs)

y(cid:3)

Holland SAGITTA2000

y(cid:3)

France DOUANE2000

y(cid:3)

Japan TEDI

第 119 页 / 共 272 页

Output Control / EDI

11 22 33

SAPScript Sub-system EDI

Medium Medium

1/2 8 6

Print/fax Special function EDI

EDI

SAP Sub-system

ª SAP AG 1999

(cid:132)(cid:3)Using output control, you can decide on the type of output and also on what type of communication

should be used:

y(cid:3)

Printing export documents within the SAP System

y(cid:3)

Printing export documents externally from the SAP System in another system

y(cid:3)

Sending an EDI message within the company or to the authorities

(cid:132)(cid:3)In all three cases, you must activate output control.

(cid:132)(cid:3)EDI tools are used for the last two communication types. You can make the final settings for these

two communication types in the EDI section.

© SAP AG LO640 6-6

EDI Sub-system

第 120 页 / 共 272 页

Import IDoc

Customizing

Output control

IImmppoorrtt ddaattaa Purchase

EDI/ALE

order

HHeeaaddeerr

Vendor 1080 Inbound

delivery

Import IDoc

IItteemm

IMPINV01

• 010 DPC1000 Goods ...

IItteemm Partner data E1EDKA1

receipt

...

• 020 P-402

FT data (header) E1EDK29

Item data E1EDP01

Invoice

...

FT data E1EDP28

(item) ...

...

11 22 33

SAPScript Subsystem EDI

ª SAP AG 1999

(cid:132)(cid:3)The IMPINV01 import IDoc for import data can be set up using output control in the purchase

order. The corresponding settings must also be made in the EDI area.

(cid:132)(cid:3)Particular attention should be paid to the partner- and port definitions.

(cid:132)(cid:3)The system includes example message type ACE1.

(cid:132)(cid:3)The import IDoc IMPINV01 contains order data and the corresponding foreign trade data at header

and item level.

(cid:132)(cid:3)The import IDoc serves as a basis for EDIFACT-supported paperless customs processing.

© SAP AG LO640 6-7

第 121 页 / 共 272 页

Export IDoc

Customizing

Output control

Order

EExxppoorrtt ddaattaa

EDI/ALE

HHeeaaddeerr Outbound

Customer 1450 delivery Export IDoc

EXPINV04

IItteemm

...

• 010 DPC1000 Goods issue Partner data E1EDKA1

IItteemm ...

FT data (hdr) E1EDK29

• 020 P-402 Billing

Item data E1EDP01

document

...

FT data E1EDP28

(item) ...

...

11 22 33

SAPScript Subsystem EDI

ª SAP AG 1999

(cid:132)(cid:3)Export IDoc EXPINV02/-03/-04 is set up using output determination in the customer billing

document.

(cid:132)(cid:3)Pay attention here to the settings to be used in the EDI area.

(cid:132)(cid:3)The export IDoc can be used for three methods:

y(cid:3)

Printing export documents internally with the SAP System using SAPScript

y(cid:3)

Connecting to a sub-system to print the export documents

y(cid:3)

Connecting and sending data by EDI

y(cid:3)

A combination of several methods, such as printing and EDI, is also possible.

(cid:132)(cid:3)Export IDoc EXPINV02/-03/-04 contains the billing document data as a primary document and the

delivery data as a secondary document. In this IDoc, foreign trade data is set at header and item

level.

(cid:132)(cid:3)The system also creates data regarding assigned financial documents or export licenses.

© SAP AG LO640 6-8

第 122 页 / 共 272 页

AES: Automated Export System - USA

Sales and Distribution

Order US Customs

EEDDIIFFAACCTT ccoonnvveerrtteerr

Census Bureau

Outbound

delivery Export Administration

Defense Trade Controls

Goods issue

Other Federal Agencies

VVaalluuee AAddddeedd NNeettwwoorrkk

NNeettwwoorrkk -- PPrroovviiddeerr

Billing

document

ª SAP AG 1999

(cid:132)(cid:3)The AES (Automated Export System) transfers any existing or planned foreign trade data in

electronic form to business-sector partners (such as customers, forwarding agents or brokers) and to

the customs authorities.

(cid:132)(cid:3)The official UN/EDIFACT-messages CUSDEC (Customs Declaration) and CUSRES (Customs

Response) are used for successful certification by the US customs authorities.

(cid:132)(cid:3)The AES was developed by US Customs and other American authorities and should improve the

export operations and increase the quality of the data that is reported.

© SAP AG LO640 6-9

US Customs Census Bureau Export Administration Defense Trade Controls Other Federal Agencies
Order
O d utboun elivery
Go ods iss
B d illing ocume

第 123 页 / 共 272 页

A.E.S.: Options - USA

Option 1 Option2 Option 3 Option 4

Message type: Message type: Message type: Message type:

FUSD AES2 AES3 AES4

Medium: Medium: EDI Medium: EDI Medium: EDI

Printing

Dispatch time: Dispatch time: Dispatch time:

Dispatch time: Before the Part of the data maximum 10

Before/at the goods before the goods; days after the

same time as the complete goods

goods declaration max. 5

Shipper’s days after the

Export goods

Declaration

EDI EDI EDI EDI

1 1 2 1 2 3 1 2

ª SAP AG 1999

AES (Automated Export System) offers four methods for declaring export processes from the USA.

(cid:132)(cid:3)Option 1: You can file a copy of the Shipper‘s Export Declaration (message type FUSD) at the same

time or before the export.

(cid:132)(cid:3)Option 2: This message is sent via EDI (message type AES2) before the goods are physically

exported.

(cid:132)(cid:3)Option 3: A message with a reduced amount of data is send via EDI before the goods are physically

exported. At the very latest, the complete message is sent five days after the goods are exported.

Once again, the message is sent via EDI. Both messages use message type AES3.

(cid:132)(cid:3)Option 4: This message is sent via EDI a maximum of 10 days after the goods are physically

exported. (message type AES4)

Note: You must apply for a special official license in order to use options 3 or 4.

© SAP AG LO640 6-10

第 124 页 / 共 272 页

Application Scenario - Outbound

SAP System document flow

Order Pro forma

OR invoice F5

Outbound Pro forma IDoc EDI Business

delivery LF invoice F8 EXPINV02* converter sector

Invoice

F2

• You can send at three different points in the document chain

• An external converter transfers the data

*) Release 46C: EXPINV04

Scenario recommended for AES

ª SAP AG 1999

Within the SD process chain there are three different scenarios:

(cid:132)(cid:3)Scenario 1: The F5 pro forma invoice is based on the SD order. This scenario is only recommended

if there is reliable order data and the settings for foreign trade have been correctly determined.

(cid:132)(cid:3)Scenario 2: The F8 pro forma invoice is based on the SD delivery document and can be created once

all the shipping steps have been completed. The advantage of this scenario is that correct and

complete export data is available at the time of processing.

(cid:132)(cid:3)Scenario 3: You can also use export billing documents (F2) that have already been forwarded to

financial accounting as the basis for setting up IDocs. However, there are limitations on which data

you can change in billing documents.

© SAP AG LO640 6-11

第 125 页 / 共 272 页

Application Scenario - Inbound

Person responsible is

Scenario 1 advised of the process

via e-mail

US EDI IDoc

Customs converter TXTRAW01

Triggers a workflow

Scenario 2

in the SAP System

ª SAP AG 1999

(cid:132)(cid:3)The receipt of information from the customs authorities has been implemented in AES in such a way

that the standard IDoc TXTRAW01 is also included. This enables you to display the OK (or error)

messages from the customs authorities.

(cid:132)(cid:3)Using standard functions in the EDI area, you can either start a workflow or send information to the

person or group of people responsible by e-mail.

© SAP AG LO640 6-12

第 126 页 / 共 272 页

Printing Options

Printing Create billing

transaction document

.............................. ..............................

.............................. Telex ..............................

....... ..................................................... ..............................

..............................

....... .....................................................

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . . .. . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . Printer . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . .

. . . . . . . .

Immediately

(dispatch time 4)

Explicit request

(dispatch time 3)

Scheduling

..............................

....... . . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . . . . . . . . . . . . . . . . With selection run,

..............................

. . . . . . . . . . . . . . . . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . ........ either next (dispatch time 1)

.............. ... ... ... ... . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . or at time specified (dispatch time 2)

. . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . .

. . . . . . . .

ª SAP AG 1999

You can define the dispatch time when output is to be issued.

The following times are available:

(cid:132)(cid:3)The output to be sent is selected by a standard program (RSNAST00) at regular intervals. You can

decide whether the output is selected during the next program run (dispatch time 1) or at a time

selected by the user (dispatch time 2).

(cid:132)(cid:3)There is also a special selection program available for the different applications with which output

can be explicitly processed in dialogue or in the background (dispatch time 3). Background

processing enables you to process output regularly (see dispatch time 1).

(cid:132)(cid:3)The output is sent automatically as soon as a document has been posted (dispatch time 4).

© SAP AG LO640 6-13

elex
T elex
.............................. .............................. .. ..................................................... ......................... ........................................... .................. .. ... ... ... ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
........................ .. ............................................... ......................... ........................................... .................. .. ... ... ... ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
....... .................................. ........................ ....... ............................................... .............................. .............. ... ... ... ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....... .................................. ........................ .. ............................................... ......................... ......... ... ... ... ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .................................. ................... ..................................... .................. .. ... ... ... ... . . . . . . . . . . . . . . . . . . . .
. . .
.............................. .............................. .. ..................................................... ......................... ........................................... .................. .. ... ... ... ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
..... ........................ .. ............................................... ......................... ........................................... .................. .. ... ... ... ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
................. ........................ ....... ............................................... .............................. .............. ... ... ... ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ................. ........................ .. ............................................... ......................... ......... ... ... ... ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ................. ................... ..................................... .................. .. ... ... ... ... . . . . . . . . . . . . . . . . . . . .
. . .

第 127 页 / 共 272 页

Printing Process

Output

determination

Printing

Billing

document

PPrriinnttiinngg

ttrraannssaaccttiioonn

ª SAP AG 1999

(cid:132)(cid:3)Foreign trade has its own print transaction for printing foreign trade documents.

(cid:132)(cid:3)This transaction lists all the documents due to be printed.

(cid:132)(cid:3)There are several different types of printing:

y(cid:3)

Initial processing

y(cid:3)

Repeated processing

y(cid:3)

Error processing

y(cid:3)

Special case processing

(cid:132)(cid:3)You can use Foreign Trade: Message Control in Customizing to make settings for the following

functions:

y(cid:3)

Select packing data

y(cid:3)

Print commodity code

y(cid:3)

Link the printout of the document to a number range

y(cid:3)

Make the official document number a required entry

y(cid:3)

Update the official document number for monitoring purposes

y(cid:3)

Receive a confirmation prompt before printing

(cid:132)(cid:3)As of Release 4.6A, it is possible to change data for printing.

© SAP AG LO640 6-14

第 128 页 / 共 272 页

Changes Before Printing

Printing

Billing document

Billing

document

Printing transaction

Change form fields

Change

manually before

history Update

printing

ª SAP AG 1999

(cid:132)(cid:3)As of Release 4.6A, an independent print transaction allows you to change data for printing. Your

changes only affect the printout, not the data in the billing document.

(cid:132)(cid:3)You can use Customizing (Form Data Control / table T609PP) to define for each output type which

form fields can be changed in the print transaction.

(cid:132)(cid:3)In the Foreign Trade: Output Control Customizing activity (table T609P), you can activate the

Create audit entry for man. changed form data function. The changes made in the print transaction

will then be updated in the change history.

© SAP AG LO640 6-15

第 129 页 / 共 272 页

List of Message Types Delivered for Various

Releases

Rel 4.0 Rel 4.5 Rel 4.6B Rel 4.6C

Message Types (Generic Templates)

AUS1 Template - EDI AUS1 Template - EDI AUS1 Template - EDI AUS1 Template - EDI

AUS2 Template - Export decl. AUS2 Template - Export decl. AUS2 Template - Export decl. AUS2 Template - Export decl.

AUS3 Template - Movem. certif. AUS3 Template - Movem. certif. AUS3 Template - Movem. certif. AUS3 Template - Movem. certif.

AUSJ Template - Export rep. JP AUSJ Template - Export rep. JP AUSJ Template - Export rep. JP AUSJ Template - Export rep. JP

Message Types for EU Countries

FECO EU certificate of origin FECO EU certificate of origin FECO EU certificate of origin FECO EU certificate of origin

FEEA EU Export refund FEEA EU Export refund FEEA EU Export refund

FEEU EUR1 document FEEU EUR1 document FEEU EUR1 document FEEU EUR1 document EUR1

FEEV Simp. export decl. SAD FEEV Simp. export decl. SAD FEEV Simp. export decl. SAD FEEV Simp. export decl. SAD

FEEX Export declaration SAD FEEX Export declaration SAD FEEX Export declaration SAD FEEX Export declaration SAD

FET1 Shipping declaration T1 FET1 Shipping declaration T1 FET1 Shipping declaration T1 FET1 Shipping declaration T1

FET2 Shipping declaration T2 FET2 Shipping declaration T2 FET2 Shipping declaration T2 FET2 Shipping declaration T2

FET5 T5 document FET5 T5 document FET5 T5 document FET5 T5 document

FETR ATR document FETR ATR document FETR ATR document FETR ATR document

FEAG Applic. export license

FEAN Export license

Message Types for Japan

FJCI Export invoice - JP FJCI Export invoice - JP FJCI Export invoice - JP FJCI Export invoice - JP

FJCO Cert. of origin Osaka FJCO Cert. of origin Osaka FJCO Cert. of origin Osaka FJCO Cert. of origin Osaka

FJCT Cert. of origin Tokyo FJCT Cert. of origin Tokyo FJCT Cert. of origin Tokyo FJCT Cert. of origin Tokyo

FJEP Export packing list - JP FJEP Export packing list- JP FJEP Export packing list- JP FJEP Export packing list- JP

FJER Export report - Japan FJER Export report - Japan FJER Export report - Japan FJER Export report - Japan

Message types for the USA

AES1 Autom. Export System AES1 Autom. Export System AES1 Autom. Export System AES1 Autom. Export System

FUCI Commercial inv. USA FUCI Commercial inv. USA FUCI Commercial inv. USA

FUCO U.S. Cert. of origin FUCO U.S. Cert. of origin FUCO U.S. Cert. of origin

FUEP Export packing list FUEP Export packing list FUEP Export packing list

FUPI Pro forma inv. USA FUPI Pro forma inv. USA FUPI Pro forma inv. USA

FUSD Shipper’s exp. decl. FUSD Shipper’s exp. decl. FUSD Shipper’s exp. decl.

FUSI Ship. letters instr. FUSI Ship. letters instr. FUSI Ship. letters instr.

ª SAP AG 1999

© SAP AG LO640 6-16

Message Types (Generic Templates) AUS1 Template - EDI AUS1 Template - EDI AUS1 Template - EDI AUS2 Template - Export decl. AUS2 Template - Export decl. AUS2 Template - Export decl. AUS3 Template - Movem. certif. AUS3 Template - Movem. certif. AUS3 Template - Movem. certif. AUSJ Template - Export rep. JP AUSJ Template - Export rep. JP AUSJ Template - Export rep. JP AUS1 Template - EDI AUS2 Template - Export decl. AUS3 Template - Movem. certif. AUSJ Template - Export rep. JP
Message Types for EU Countries FECO EU certificate of origin FECO EU certificate of origin FEEA EU Export refund FEEU EUR1 document FEEU EUR1 document FEEV Simp. export decl. SAD FEEV Simp. export decl. SAD FEEX Export declaration SAD FEEX Export declaration SAD FET1 Shipping declaration T1 FET1 Shipping declaration T1 FET2 Shipping declaration T2 FET2 Shipping declaration T2 FET5 T5 document FET5 T5 document FETR ATR document FETR ATR document FECO EU certificate of origin FEEA EU Export refund FEEU EUR1 document FEEV Simp. export decl. SAD FEEX Export declaration SAD FET1 Shipping declaration T1 FET2 Shipping declaration T2 FET5 T5 document FETR ATR document FECO EU certificate of origin FEEA EU Export refund FEEU EUR1 document EUR1 FEEV Simp. export decl. SAD FEEX Export declaration SAD FET1 Shipping declaration T1 FET2 Shipping declaration T2 FET5 T5 document FETR ATR document FEAG Applic. export license FEAN Export license
Message Types for Japan FJCI Export invoice - JP FJCI Export invoice - JP FJCO Cert. of origin Osaka FJCO Cert. of origin Osaka FJCT Cert. of origin Tokyo FJCT Cert. of origin Tokyo FJEP Export packing list - JP FJEP Export packing list- JP FJER Export report - Japan FJER Export report - Japan FJCI Export invoice - JP FJCO Cert. of origin Osaka FJCT Cert. of origin Tokyo FJEP Export packing list- JP FJER Export report - Japan FJCI Export invoice - JP FJCO Cert. of origin Osaka FJCT Cert. of origin Tokyo FJEP Export packing list- JP FJER Export report - Japan
Message types for the USA AES1 Autom. Export System AES1 Autom. Export System AES1 Autom. Export System AES1 Autom. Export System FUCI Commercial inv. USA FUCI Commercial inv. USA FUCI Commercial inv. USA FUCO U.S. Cert. of origin FUCO U.S. Cert. of origin FUCO U.S. Cert. of origin FUEP Export packing list FUEP Export packing list FUEP Export packing list FUPI Pro forma inv. USA FUPI Pro forma inv. USA FUPI Pro forma inv. USA FUSD Shipper’s exp. decl. FUSD Shipper’s exp. decl. FUSD Shipper’s exp. decl. FUSI Ship. letters instr. FUSI Ship. letters instr. FUSI Ship. letters instr.

第 130 页 / 共 272 页

Creating New Documents in the SAP System:

Activities

z

Copy a sample message type

z

Copy a print program

z

Modify the new print program

z

Copy a SAPScript form

z

Modify the new form

ª SAP AG 1999

(cid:132)(cid:3)All of the export data contained in the system is available in the RVADAUS1 program in the

standard system. If other data is required, you can enhance the EXPINV02 IDoc by adding the

necessary fields.

(cid:132)(cid:3)You can tailor the IDOC_OUTPUT_INVOIC function module to match your needs with a user

enhancement. This function module populates the EXPINV02 IDoc with document data.

© SAP AG LO640 6-17

第 131 页 / 共 272 页

User Enhancement V55ECTRL

z

Field control according to user specifications

z

Redetermination of all data for:

ª SAP AG 1999

© SAP AG LO640 6-18

(cid:1) Single Administrative Documents

(cid:1) Movement certificate EUR1

(cid:1) ATR

(cid:1) EC certificate of origin

(cid:1) NAFTA documents

z

Incompleteness check (DOCUMENT_INCOMPLETE

parameter)

z

Modification of packing information related to the given

document

(cid:132)(cid:3)You can tailor the IDOC_OUTPUT_INVOIC function module to meet your needs with a user

enhancement. This function module populates the EXPINV02 IDoc with document data.

(cid:132)(cid:3)In this function module, you can control whether certain additional information from the delivery

such as packing data needs to be read.

(cid:132)(cid:3)As of Release 4.5A, you can use the T609P control table to set up printing of packing data from the

foreign trade documents in the standard system.

(cid:132)(cid:3)There are more user enhancements for SAP extension V55ECTRL in the printing programs. These

make it possible for you to change the data right in the foreign trade documents.

第 132 页 / 共 272 页

Communication / Printing: Summary

z

Output control is used to determine the

communication type.

z

The IDoc for the import purchase order is the

first module in the electronic customs process.

z

The export billing document IDoc can be used

to print documents relevant for export, to send

via EDI, and as a data basis for supporting

partner systems.

ª SAP AG 1999

© SAP AG LO640 6-19

第 133 页 / 共 272 页

Exercises

Communication / Printing

• Export and Import IDocs

• Printing export documents and using output control:

You are responsible for foreign trade in your company and must ensure

that the relevant export documents for billing are correctly printed or

created for EDI messages.

Exercises - Communication / Printing

CCuussttoommeerr Customs

11 Export declaration

PPllaanntt

Customs

ª SAP AG 1999

© SAP AG LO640 6-20

第 134 页 / 共 272 页

1 EDI Partner settings

Display the partner profile for vendor 1080 with partner type LI.

You can find the Partner Profile section under Foreign Trade/Customs in the menu

(Tools fi Business Communication fi IDoc Basis fi IDoc).

Outbound parameters:

Message type _____________________

Receiver port _____________________

IDoc basic type _____________________

Message control:

Application _____________________

Message type _____________________

Partner function _____________________

2 Communication EDI: Display IDoc

You want to see the structure of the Import Basis IDoc. What are the first three

fields for the General foreign trade data at item level (segment E1EDP28)?

For this exercise, go to the IDoc documentation section of the Communication /

Printing cockpit (which you can reach via the Initial Screen Foreign

Trade/Customs).

Field name: _____________________

Field name: _____________________

Field name: _____________________

© SAP AG LO640 6-21

第 135 页 / 共 272 页

3 Creating an IDoc on the basis of a purchase order

Order 10 pieces of material MHA_## from vendor 1080.

You want to send an EDI message to this vendor.

Describe how you performed this step.

______________________________________

______________________________________

______________________________________

______________________________________

Note:

When you create the purchase order, the system notifies you that the import item

data is incomplete. Why? Maintain the missing data.

Check the contents of the following fields in the IDoc you just created.

For this exercise, go to the Communication/EDI section (IDoc subsection) of the

Communication / Printing cockpit (which you can reach via the Initial Screen

Foreign Trade/Customs).

Customs office ________________________

Currency of statistical value ________________________

Description of trading country ________________________

You can create an EDI message for exports in the same way as you would for

imports.

This EDI message is created to support the new EDI processes, such as the

American AES - Automated Export System.

© SAP AG LO640 6-22

第 136 页 / 共 272 页

4 Creating an IDoc on the basis of an SD billing document

Display your billing document from exercise 8 in the Documents in Foreign Trade

unit.

What messages are proposed automatically?

Message type ________________________

Standard message type ________________________

Medium for transmission ________________________

You want to view all IDocs of type EXPINV that were created last month. Describe

how you performed this step.

______________________________________

______________________________________

5 Printing an export declaration FEEX

Create an export declaration on the basis of the billing document from exercise 8 in

the Documents in Foreign Trade unit.

1. Add message type (output type) FEEX to the billing document.

2. Choose P633 as the logical destination.

3. Save the billing document.

Display the export declaration on the screen.

For this exercise, select First processing in the Printout section of the

Communication / Printing cockpit (which you can reach via the Initial Screen

Foreign Trade/Customs).

© SAP AG LO640 6-23

第 137 页 / 共 272 页

6 Changing the data that is to be printed in an export declaration (FEEX)

Before you created the export declaration in exercise 5, the system informed you

that the transportation data had changed.

Your goods are now scheduled for transport on a ship with ## as its ID number.

Check to make sure that this change on the export declaration is also reflected in the

invoice. Then, print the document.

After you have printed the document successfully, you want to display the changes

that you have made.

Describe how you performed this step.

________________________________________________

7 Message control (optional)

What is the name of the print program for output type FET1 T1 shipping

document?

________________________________________________

What is the name of the SAPScript form for output type FET1 T1 shipping

document?

________________________________________________

8 Print control (optional)

Your customs office gives you the authorization to assign your own document

numbers on your export declarations.

You also want to make sure that the system always offers a safety query before it

prints export declarations.

Describe how you performed this step.

________________________________________________

________________________________________________

________________________________________________

________________________________________________

© SAP AG LO640 6-24

第 138 页 / 共 272 页

9 Changing the modifiable fields in the export declaration (optional)

In the future, you also want to be able to use the print transaction for foreign trade

documents to change field 20 - Delivery conditions in an export declaration before

it is printed.

Describe how you performed this step.

________________________________________________

________________________________________________

________________________________________________

© SAP AG LO640 6-25

第 139 页 / 共 272 页

Solutions

Communication / Printing

1 EDI Partner settings

o o

Logistics Sales and Distribution Foreign Trade/Customs

o o

Communication / Printing Environment IDOC / EDI basis

o

IDoc Partner Profile

o

Partner type LI 1080

Outbound parameters:

Message type IMPINV Import declaration

Receiver port SAPID3 Port for ID3 system

IDoc basic type IMPINV01 Import Basis IDoc (I.B.I.)

Message control:

Application EF Purchase Order

Message type ACE1 New PO printout

Partner function VD Vendor

© SAP AG LO640 6-26

第 140 页 / 共 272 页

2 Communication EDI: Display IDoc

o o

Logistics Sales and Distribution Foreign Trade/Customs

o

Cockpit - Communication / Printing IDoc documentation section

Select Import IDoc and then choose IDoc documentation.

Object name: IMPINV01

IMPINV01 fi E1EDP01 fi E1EDP28 fi Segment fields

Field name: EXNUM

Field name: EXPOS

Field name: STAWN

3 Creating an IDoc on the basis of a purchase order

Once you have created the purchase order with the data given, you must use the

o

Goto Messages to add the message type ACE1.

Check the Further data for the message to make sure that the message will be

processed as soon as the purchase order is posted: Dispatch time 4 – send

immediately (when application is saved) must be selected.

After you have posted the purchase order, you can use the following path to display

the IDoc of type IMPINV01 type that was created:

o o

Logistics Sales and Distribution Foreign Trade/Customs

o

Cockpit – Communication / Printing Communication/EDI section

o

IDoc section List

Selection parameters: Logical message type IMPINV

© SAP AG LO640 6-27

第 141 页 / 共 272 页

You can determine the values in the following segments by double-clicking on your

IDoc and then placing the cursor on the following segments in the data records

folder:

- E1EDK29 - IDOC: Document Header - General Foreign Trade Data

- E1EDP28 - IDOC: Document Item - General Foreign Trade Data

From segment E1EDK29:

– Customs office CUSTOMSA 3816 - Weil am Rhein

– Currency of the statistical value GRWC UNI

From segment E1EDP28:

- Name of the country involved in trade HANLD_TX France

4 Creating an IDoc on the basis of a Sales and Distribution (SD) billing

document

o o

Logistics Sales and Distribution Billing

o o

Information system Billing documents List Billing Documents (Search

term: Payer DEU_XX)

Select billing document

o o

Goto Header Output

The system suggests output RD00 – Invoice automatically by default.

In order to display all IDocs with the type EXPINV, proceed as follows:

o o

Logistics Sales and Distribution Foreign Trade/Customs

o

Cockpit – Communication / Printing Communication/EDI section

o

IDoc section List

Selection parameters: Logical message type EXPINV

© SAP AG LO640 6-28

第 142 页 / 共 272 页

5 Printing an export declaration (FEEX)

o o

Logistics Sales and Distribution Billing

o o

Information system Billing Documents List Billing Documents (Search

term: Payer DEU_XX)

Select billing document

o o

Goto Header Output

- Add output FEEX

- Save the billing document

o o

Logistics Sales and Distribution Foreign Trade/Customs

Cockpit Communication / Printing

o

Printout section

Select First processing and then choose Print.

A selection screen appears. Select output type FEEX and then choose Print

preview.

6 Changing the data that is to be printed in an export declaration (FEEX)

o o

Logistics Sales and Distribution Foreign Trade/Customs

o

Cockpit – Communication / Printing Printout section

Select First processing and then choose Print.

A selection screen appears. Select output type FEEX and then choose Form data.

Select field 18 – Indicator for the means of transport at departure in the hierarchy

on the left side of the screen. Then, enter the new data in the dialog box that

appears.

Then, select Back and choose Print. Finally, confirm that the system should print

the data that you have changed in the following dialog box.

Displaying print changes

o o

Logistics Sales and Distribution Foreign Trade/Customs

Cockpit Communications / Printing

o

Printout section

Monitoring subsection

o

Print changes

© SAP AG LO640 6-29

第 143 页 / 共 272 页

7 Output control

o o o

IMG Sales and Distribution Foreign Trade/Customs

o

Printing/Communication Assign Forms/Programs for Export Billing

Documents

The print program for output type FET1 is

RVADAUS1 ENTRY_FET1

The SAPScript form for output type FET1 is

SD_EXPORT_EUDC

8 Print control

o o

Logistics Sales and Distribution Foreign Trade/Customs

o

Cockpit Communication/Printing Environment section

You can use the Print control function to control the printing transaction. Select

the output type FEEX and then choose Details.

Assign your own document numbers

Select the Internal using number range entry in the Document number section

and then assign the FT_DRU_AM object in the Number range object field and

enter 01 in the Number range number field.

Safety query

Select the Safety query before starting printing field in the Print transaction –

General section.

9 Changing the modifiable fields in the export declaration

o o o

IMG Sales and Distribution Foreign Trade/Customs Printing /

o o

Communication Control Foreign Trade Documents Form Data Control

Select the Changeable indicator for element F020 – 20 Delivery condition for output

type FEEX.

© SAP AG LO640 6-30

第 144 页 / 共 272 页

Legal Control

Contents:

z

Licenses

z

UNO embargo

z

Sanctioned Party Lists

z

Scope and course of checks

z

System settings

z

Further uses

ª SAP AG 1999

© SAP AG LO640 7-1

返回TECH参考资料列表