You are on page 1of 81

2/10/2023

Purchasing (MM-PUR)
Generated on: 2023-02-10 12:39:49 GMT+0000

SAP ERP | 6.0 EHP8 Latest

PUBLIC

Original content: https://help.sap.com/docs/SAP_ERP/967e1c2a6a8c4183b7e07d28e7574445?locale=en-


US&state=PRODUCTION&version=6.18.latest

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit the SAP Help Portal 1
2/10/2023

Version Management

Use
In the case of procurement transactions extending over a longer period of time (for example, in the procurement of capital
goods), you may need to differentiate between various versions of the purchasing document. You may also need to refer to one
particular version when corresponding with the vendor.

Version Management enables you to generate and manage versions of purchase requisitions and external purchasing
documents, such as purchase orders. A version groups together the change documents generated in the course of subsequent
processing of the relevant document. A version thus indicates the revision level of a document (version 0 = original document,
versions 1 + = revisions) and provides the user with an overview of the various changes that may have been made in the course
of time.

Version management thus represents an extension to the hitherto existing change documentation functionality for internal and
external purchasing documents.

Integration
Version management can be used in connection with purchase requisitions (ME51N, ME52N and ME53N only), RFQs, purchase
orders, contracts, and scheduling agreements.

 Note
It is not possible to create different versions of quotations or scheduling agreement delivery schedules.

The system can also generate versions of externally generated purchase requisitions (from PS Project System or PM Plant
Maintenance and Service Management , for example).

 Note
The system does not generate versions for requisitions created by MRP Material Requirements Planning .

Only if such a requisition is changed via Change Purchase Requisition (ME52N) does the system generate a version and x
( rm) this requisition. It cannot then be changed again through requirements planning.

Prerequisites
To be able to use version management, you must activate it in Customizing for Purchasing as follows:

For purchase requisitions under Version Management Set Up Version Management for Purchase Requisitions (for
the relevant combination of document category and document type)

For external purchasing documents under Version Management Set Up Version Management for External
Purchasing Documents (for the relevant combination of document category, document type, and purchasing
organization)

 Note
If you deactivate version management in Customizing after purchasing documents with versions have been created, versions
will continue to be generated for these documents.

This is custom documentation. For more information, please visit the SAP Help Portal 2
2/10/2023

Features
When you create a requisition or an external purchasing document (such as a PO), the system automatically creates an initial
version (version 0). From this time on, changes and newly entered data are documented in the current version that is valid in
each case.

 Note
In the case of requisitions, one version is generated per requisition item (at item level). In the case of external purchasing
documents, one version is generated per document (at header level).

Once all necessary data has been entered for the purchase requisition, the version must be completed. Only then can:

The purchase requisition be released or converted into a follow-on document

 Note
If a requisition is subject to an overall release procedure, the versions of all requisition items must be completed in
order for the requisition to be released and converted.

The external purchasing document be released or output (printed out or transmitted, for example, as a fax or EDI
message)

You complete a version by setting the Completed indicator in the version data. The processor of a purchase requisition or
external purchasing document thereby explicitly indicates that he or she has now made all changes desired at the time.

 Note
You can specify that version 0 is to be completed automatically in Customizing for Purchasing . To do so, set the Version 0 OK
indicator under Version Management Set Up Version Management .

New Versions

New change documents are always assigned to the current version, even if the Completed indicator has been set. This is done
until such time as a new version is created.

New Versions of Purchase Requisitions

The system always creates a new version when the requisition has reached a nal state. This means one of the following
processing states:

Active

If you do not use the document release functionality

Release completed

If you use the document release functionality

Not every change to a requisition results in a new version. The following changes lead to a new version:

All version-relevant changes

You de ne which changes are version-relevant in Customizing for Purchasing under Version Management Version-
Relevant Fields of Purchase Requisitions .

Changes in document assignment

This is custom documentation. For more information, please visit the SAP Help Portal 3
2/10/2023
Changes in address

Changes in service items

New Versions of External Purchasing Documents

The system always creates a new version when the purchasing document has reached a nal state. This means one of the
following processing states:

Active

If you do not use the document release functionality

Release completed

If you use the document release functionality

 Note
For a new version of a purchasing document to be created, all messages must have also been transmitted.

No new versions are generated for purchase orders that are on hold.

Not every change to an external purchasing document results in a new version. Only the following changes lead to a new
version:

All print-relevant changes

You de ne which changes are print relevant in Customizing for Purchasing under Messages Fields Relevant to
Printouts of Changes .

Changes in document assignment

Changes in address

 Note
Address changes result in a new version only if the eld ADRC-NAME1 has been de ned as a eld that is relevant to
printouts of changes.

Changes to master conditions

 Note
Changes in master conditions result in a new version only if the eld EKPO-NETPR has been de ned as a eld that is
relevant to printouts of changes.

Version Data

You will nd the version data:

In the item details on the Versions tab page in the single-screen transactions for purchase requisitions (ME51N, ME52N,
and ME53N)

In the header data on the Versions tab page of the single-screen transactions for purchase orders (ME21N, ME22N, and
ME23N)

Under Header Versions in RFQs, conventional purchase orders (ME21, ME22, and ME23), contracts, and scheduling
agreements.

This is custom documentation. For more information, please visit the SAP Help Portal 4
2/10/2023
There you can maintain version data (for example, reason for change) and complete the version. In addition, the Value change
eld shows you whether and to what extent the value of a requisition or external purchasing document item has changed in
comparison with the previous version.

You can display the change documents for one or more versions by selecting the relevant versions and choosing Display
changes .

See also:

Texts for Versions in Requisitions and External Purchasing Documents

Purchase Requisitions from the SAP Advanced Planner and Optimizer

The Version Management facility can also be active for purchase requisitions transferred from the SAP Advanced Planner and
Optimizer (SAP APO) . This depends on the document type de ned in Customizing for Purchasing under De ne Default Values
for Document Type (ME51N).

In the SAP APO system, you have the option of automatically converting requisitions that have already been transferred to the
ERP system into external purchasing documents. If version management is active for the document type of the purchase
requisition, however, this is only possible if the version of the requisition was completed manually. Otherwise, you must manually
convert the requisition into an external purchasing document in the ERP system.

 Note
You can deactivate version management for purchase requisitions from SAP APO in Customizing for Purchasing under
Version Management Set Up Version Management for Purchase Requisitions .

User exit EXIT_SAPLMEPI_003 of enhancement CIFPUR02 enables you to in uence the document type for purchase
requisitions transferred from SAP APO and use a document type for which version management is not active.

Cancelling Versions of Purchase Requisition Items

Use
You may want to cancel versions of a requisition item because the changes made in a certain version are not to be applied after
all, for example.

Integration
Versions of a purchase requisition item can be cancelled in Change Purchase Requisition (ME52N).

Features
You can cancel a version by clicking Cancel version on the Versions tab page. As far as possible, the system then
automatically cancels the changes made in this version. If the system was unable to cancel certain changes, you are made
aware of this through error messages. You must then cancel them manually.

 Note

If it was possible to cancel all changes automatically, the version is automatically completed.

If some changes have to be cancelled manually, you must complete the version manually as well.

This is custom documentation. For more information, please visit the SAP Help Portal 5
2/10/2023

The version remains in existence, but is assigned the status C (cancelled). Such versions cannot be re-opened. In the event of
new changes, a new version is opened.

Deleting Versions of External Purchasing Documents

Use
You may want to delete versions of an external purchasing document (because the changes made in a certain version are not to
be applied after all, for example).

Integration
Versions of a purchasing document can be deleted in the relevant change transaction for the purchasing document (e.g. in
Change Purchase Order (ME22N)).

Prerequisites
The following prerequisites must be satis ed before a version of a purchasing document can be deleted:

The changes made in the version must have been reversed (cancelled, revoked)

All open messages must have been deleted

Activities
To delete a version of an external purchasing document, proceed as follows:

1. Manually reverse all changes made to the purchasing document in this version.

If you do not reverse the changes of the current version, the changes will be assigned to the previous version.

1. Manually delete all open messages for the purchasing document.

1. Delete the version by choosing Delete version on the Version tab page.

When you delete a version, it is completely deleted from the database.

Texts for Versions in Requisitions and External Purchasing


Documents

Use
If you are using version management, the system also manages the texts (for example, delivery texts or the material master
PO text) that are included in the versions. As a result, in addition to the current text , you also have older text editions at your
disposal and communication with your vendor over a period is fully documented.

A text edition is a copy of a text that has been made obsolete through subsequent changes and which is assigned to a version.

This is custom documentation. For more information, please visit the SAP Help Portal 6
2/10/2023

Integration
Text editions are generated for the following documents: purchase orders (single-screen transaction), RFQs, purchase orders,
contracts, and scheduling agreements.

Prerequisites
For the system to be able to generate text editions for versions, Version Management must be activated in Customizing for
Purchasing under Version Management Set Up Version Management for Purchase Requisitions or Set Up Version
Management for External Purchasing Documents .

Features
When changes are made to item or header texts, the system automatically generates a text edition for the previous text status
and assigns it to the previous version. You can either display these text editions individually or compare them with each other or
with the current text in order to identify changes.

When is a text edition generated?

When you change a text in the current version, a text edition is generated for this text (which was already stored in the
database) and assigned to the previous version if no text edition has yet been assigned to that version.

If the text in the current version is changed again, this change has no effect on the text edition in the previous version. The
interim text is overwritten by the current changes.

 Note
Only one (the nal) text edition can exist per version.

Only changes to print-relevant texts automatically generate a new version.

 Example
This is custom documentation. For more information, please visit the SAP Help Portal 7
2/10/2023
A delivery text is entered when purchase order item 10 covering 100 pc pressure sensors is created.

After the PO has been released, the PO quantity is increased to 140 pc. Due to this change, the system automatically
generates version 1. Version 1 is completed and the PO re-released.

Since the pressure sensors are sensitive instruments, requiring careful handling, it is decided to add special packing
instructions to the delivery text. Due to this change, the system generates version 2.

The system automatically generates a text edition for the previous text and assigns it to version 1. The new text is held in the
current version. If this text is changed in a future version, the system generates a text edition.

If the delivery text in version 2 is changed again, no new text edition is generated. Instead the current text is simply updated.
The text edition of version 1 remains unaffected by the new changes.

Displaying a Text Edition

To display a text edition for a version, proceed as follows:

1. Choose Display Texts for Versions on the Versions tab page.

2. Select a text and choose Display Text .

Comparing Text Editions

To compare two texts, proceed as follows:

1. Choose Display Texts for Versions on the Versions tab page.

2. Select two texts and choose List or Text .

 Note
Note that texts of various types and from different document items may be available for selection.

Further Functions
Here you will nd further Purchasing functions, such as working with manufacturer part numbers or the Document
Management System.

Manufacturer Part Number (MPN)

Use
If you wish to in uence the precise source or quality of materials, you can tell the vendor from whom you want to procure a
material which manufacturer the material is to be supplied by and the part number used by that manufacturer.

You can also tell your vendor exactly which of a manufacturer’s plants is to supply the material you wish to procure.

The manufacturer’s part number (MPN) and description, as well as the speci c manufacturing plant (if applicable), are included
in the data sent to the vendor with the purchase order.

This is custom documentation. For more information, please visit the SAP Help Portal 8
2/10/2023
Your vendor gets the steel bolts he supplies to you from the manufacturers Zenith Co. and Miller Corp.

However, you are not satis ed with the quality of the Zenith product. You wish to have the steel bolts that are manufactured by
Miller Corp. You advise your vendor of this in the purchase order by specifying the manufacturer and the MPN.

For procurement purposes, you can use the material or part number used by the manufacturer (MPN) alongside your rm’s own
material number.

If you wish to check whether a certain Manufacturer Partmay be ordered and used within your enterprise, you should make use
of the approved manufacturer parts list (AMPL). The latter indicates exactly which of a manufacturer’s plants the materials
included on the list are to be procured from.

For more information, refer to the section Approved Manufacturer Parts List .

Prerequisites
If you wish to work with manufacturer part numbers, you must satisfy the following prerequisites:

Make the necessary Customizing settings

Create material master records

De ne manufacturer part pro le

Create master records for manufacturers and manufacturer plants

Make the necessary Customizing settings

If you wish to work with MPNs, you must set the Manufacturer part number indicator in Customizing for Logistics (General), (
Material Master Basic Settings Make Global Settings)

Create material master records

If you work with MPNs, the number of manufacturers of a manufactured part corresponding to one of your rm’s own materials
determines the number of material master records you have to create:

If there is just one MPN corresponding to one of your rm’s own materials, you can enter it and the manufacturer directly
in the master record for your own material. In this case, you need not create an MPN Material.

If there are several MPN materials corresponding to one of your rm’s own materials, you must create MPN material
master records with the material type HERS. In the Purchasing view, enter the manufacturer part number, the

This is custom documentation. For more information, please visit the SAP Help Portal 9
2/10/2023
manufacturer (this can be either a vendor master record or a manufacturer master record), and your rm’s own,
inventory-managed material.

The MPN material master records are assigned to your rm’s own material. Stocks are managed with respect to the
rm’s own material.

 Example
0.8 cm steel bolts with a diameter of 0.5 cm are identi ed and stocked in your enterprise as the rm’s own, inventory-
managed material RAW_S_08.

The manufacturer Meyer & Co. sells these bolts under the number 8001 (the manufacturer part number). This
information is stored in the MPN material master record S_MEYER.

The manufacturer Smith Corp. supplies similar bolts under the number 4711. This information is stored in the MPN
material master record S_SMITH.

The MPN material master records S_MEYER and S_ SMITH are assigned to the material master record RAW_S_08.

De ne manufacturer part pro le

Manufacturer part pro les (MPN pro les) allow you to specify for each of your rm’s own materials the conditions under which
the MPN material may be used in the procurement process.

Using the MPN pro le, you can determine the following, for example:

Whether the MPN material has to be entered in the purchase order.

Whether purchasing info records are created for the rm’s own material or for the MPN materials.

Whether the PO text for the rm’s own material or the one for the MPN material is used.

Whether the MPN material may be changed during the procurement process.

Whether the system is to check the approved manufacturer parts list when an MPN material is entered.

You de ne the MPN pro les in Customizing for Purchasing under Material Master.

You enter the MPN pro le in the master record for your rm’s own material (Purchasing view).

Create master records for manufacturers and manufacturer plants

If, during the process of procuring materials, you wish to have the option of choosing between several manufacturers of a
material, or between several of a certain manufacturer’s plants, you must create separate master records for such
manufacturers and for the relevant plants belonging to the latter.

The number of master records you will need to create for manufacturers, manufacturer plants, and vendors, depends on

Whether the vendor is also the manufacturer

Which of the plants belonging to a certain manufacturer you wish to procure materials from

Vendor is not the manufacturer

If the manufacturer is not a vendor (end supplier), you can store the manufacturer data in a manufacturer master record
with a minimum of data entry effort. You then assign the account group MNFR to this manufacturer master record. If you
wish to store an external ID for the manufacturer, enter it in the control data ( External manufacturer eld). This
identi cation will appear in the purchase order.

Vendor is also the manufacturer

This is custom documentation. For more information, please visit the SAP Help Portal 10
2/10/2023
If the vendor is simultaneously the manufacturer, you can work with vendor master records. You must then ensure that a
partner schema that takes the partner role HS into consideration is assigned to the account group of the vendor master
record. (In Customizing for Purchasing under Partner Determination Partner Settings in Vendor Master Record
Assign Partner Schemas to Account Groups ).The manufacturer plants must then have the partner role HS in the
vendor master record.

You wish to procure materials from certain speci c manufacturer plants

If the manufacturer has several Manufacturer Plants, you can create a separate manufacturer master record with the
account group MNFR for each of them. The manufacturer plants must have the partner role HS (manufacturer plant) in
the manufacturer (vendor) master record.

The following graphic shows which partner roles you have to maintain in the master records for the vendor, manufacturer, and
manufacturer plant:

Features
See Searching for MPN Materials

See Manufacturer Part Number: Features

For further information on the use of manufacturer part numbers, refer to the documentation Quality Management in
Procurement under Manufacturer Part Number Management in QM .

Approved Manufacturer Parts List (AMPL)


Use

This is custom documentation. For more information, please visit the SAP Help Portal 11
2/10/2023
If you wish to check and control which MPN materials may be procured, you should make use of the approved manufacturer
parts list (AMPL).

In this list, you can specify for each MPN material

Whether it can be procured for a certain plant only or for all the plants of your enterprise

The period during which the MPN material may be procured

Whether it must belong to a certain revision level

Whether it may only be procured from a certain manufacturer plant

Whether it is blocked and, if so, why

 Note

You can de ne reasons for blocking MPN materials in Customizing for Purchasing under Material master.

Prerequisites

You should de ne a Manufacturer part pro le under Material master in Customizing for Purchasing . Set the indicator
for AMPL management so that the system checks the approved manufacturer parts list when the MPN material is
entered.

Enter the manufacturer part pro le in the master record of the inventory-managed material (Purchasing view).

In order that the system checks whether the manufacturer plant entered is allowed, you must

Create master records with the account group MNFR for the manufacturer plants;

Enter the manufacturer plants with the partner role HS in the manufacturer or vendor master record;

Specify a checking rule in the manufacturer part pro le.

Activities

You maintain the approved manufacturer parts list via the Purchasing menu under Master data Appr. manuf. parts
Maintain .

At this point, SAP provides the enhancement AMPL0001, enabling you to de ne your own criteria for the admissibility of
manufacturer parts.

Searching for MPN Materials

Use
You can search for MPN materials using the input help.

Prerequisites
In order that this function does not impair system performance, the indexes BMA and MPN must exist in the table MARA
(material master). Once you have generated the indexes, they are updated by the system.

Activities
This is custom documentation. For more information, please visit the SAP Help Portal 12
2/10/2023
You generate an index as follows:

1. From the system menu, choose Tools ABAP Workbench.

2. Choose Development Dictionary.

3. Change the database table MARA.

4. Choose Goto Indexes...

5. Choose the index BMA (number of the internal material master).

6. Set the indicators Non-unique index and Index to all database systems .

7. Activate your changes.

Also perform steps 5 to 7 for the index MPN (manufacturer part number/number of a manufacturer).

Manufacturer Part Number: Functions

Searching for MPN Materials


You can search for MPN materials by calling up the value help and then choosing the search help for the manufacturer part
number.

Entering MPN Materials


If the material master record for your company’s own material contains a manufacturer part pro le providing for checking
against the approved manufacturer parts list, the system will check each MPN material that is entered to verify that it is an
approved one.

In the course of the procurement process (e.g. when a purchase order is created with reference to a requisition), it may be
necessary to change the manufacturer part number if parts that are comparable in form and function are involved. You can
specify in the MPN pro le whether it is generally permissible to switch the MPN material in this way.

Purchasing Info Record

If you wish to store different prices for different MPN materials corresponding to one of your company’s own materials, you
should create purchasing info records not for your company’s own materials but for the MPN materials. To be able to do so, you
must specify in the MPN pro le that purchasing info records can only be created for MPN materials. In this case, you will not be
able to create an info record for your company’s own material.

 Caution

If you are working with consignment info records, you must create the info records for your rm’s own material. Reason: in
the case of goods issues involving consignment materials, the system searches for the info records for the rm’s own,
inventory-managed materials and does not take MPN materials into account.

Source List and Quota Arrangement

For source determination purposes, you can use either MPN materials or the company’s own material. If you wish to use the
MPN material, you must rst enter the company’s own material on the initial screen. You can enter the MPN material on the
overview screen.

This is custom documentation. For more information, please visit the SAP Help Portal 13
2/10/2023
Purchase Requisition

You can enter your rm’s own material or the MPN material in the item overview. If you specify the MPN material, the system
converts your entry into your rm’s own material (that is to say, on the item overview screen you always see your rm’s own
number and the MPN).

The MPN material is shown again on the item detail screen, where it can be changed.

Source Determination

If you are working with an MPN material, both the MPN material and your rm’s own material are used in the source
determination process.

All sources of the MPN materials are also taken into account during the process of source determination with respect to
your rm’s own, inventory-managed material, since sources such as source lists, contracts, quota arrangements etc. can
be created for both MPN materials and for the inventory-managed material.

All sources of the rm’s own material are also taken into account during the source determination process with respect
to the MPN material.

 Example

There are two MPN materials supplied by vendor Smith Corp. corresponding to the inventory-managed material Steel_02.
There is an info record for each of the two MPN materials Steel_MPN_01 and Steel_MPN_02, because the manufacturer
part pro le stipulates that purchasing info records must be created for MPN materials. There are no other sources such as a
quota arrangement, a source list entry or a contract.

If you have entered the inventory-managed material Steel_02 in the purchase requisition, the source determination process
will yield the two info records for the MPN materials. The system will not assign a source to the requisition because it is
unable to identify a unique one.

RFQ and Quotation

If you create an RFQ without reference to a purchase requisition, you can enter the MPN material or the rm’s own material.

If you create an RFQ with reference to a purchase requisition that already contains an MPN material, you can change the latter.
A precondition for this is that the MPN pro le allows you to change the MPN material.

The system inserts the MPN material from the RFQ into the quotation. You cannot then change the number in the quotation.

Contract

You can enter your rm’s own material or the MPN material in the item overview. If you enter the MPN material, the system
converts it into the rm’s own material. In the item overview, you always see the rm’s own material number and the
manufacturer part number. The MPN material is shown again on the item detail screen.

If you do not specify the MPN material in the contract, you can enter it in a subsequent release order. Once you have saved the
contract release order, you cannot then change the MPN material. However, you do have the option of deleting the item and
creating a new one.

Purchase Order and Scheduling Agreement

If procurement of the MPN material is mandatory, you must specify the MPN material in the purchase order and in the
scheduling agreement. If you nevertheless enter the inventory-managed material, the system will ask you to enter the MPN
material.

This is custom documentation. For more information, please visit the SAP Help Portal 14
2/10/2023
If no MPN requirement has been de ned for the material to be procured, you can enter either the MPN material or the rm’s
own material.

If you create a purchase order referencing an existing document that already contains an MPN material, the latter is adopted in
the new PO.

Con rmation

Acknowledgment

Your vendor’s acknowledgment can relate to an MPN material that differs from the PO item. If the order acknowledgment is the
only category of con rmation, it must be marked as "subject to GR assignment requirement" in Customizing for Purchasing. If,
in addition, a shipping noti cation is expected, the MPN material quoted in the acknowledgment has provisional character only.

Inbound delivery

It is possible to give noti cation of shipment of a different MPN material. The con rmation category "inbound delivery" must be
marked as "subject to GR assignment requirement" in Customizing for Purchasing. The noti ed MPN material is GR-relevant.

If the MPN material and the price in the inbound delivery differ from the corresponding data in the PO, the system does not
carry out a new price determination process because the vendor’s price is assumed to be correct.

Special Forms of Procurement with MPN Materials

You can only create a consignment order if info records exist for your rm’s own material (because the system can only
uniquely nd the relevant info record at the time of goods issue if this is the case).

You can create stock transport orders (for inter-plant stock transfers). The goods issue is effected using your rm’s own
material number because the Sales and Distribution component can only work with the rm’s own, inventory-managed
material.

You can create subcontract and third-party orders with MPN materials.

Goods Receipt

You can change the MPN material at the time of goods receipt. The stock of the rm’s own materials is updated.

 Note

The system does not carry out the price determination process for the MPN material because inventory management is
always based on the rm’s own material.

Invoice Veri cation

No special aspects.

Message Output (Printing/Transmission of Documents in Message Format)

RFQs, POs, contracts, or scheduling agreements in message format for communication to vendors (e.g. for transmission as
hardcopies or via EDI) contain the following data that is not displayed in the system document:

All manufacturer plants included on the approved manufacturer parts list (AMPL) and the revision level of the MPN
material.

The manufacturer part numbers and the external ID of the manufacturer stored in the manufacturer master record.

This is custom documentation. For more information, please visit the SAP Help Portal 15
2/10/2023
Archiving MPN Materials

If you wish to archive MPN materials that you have entered on the approved manufacturer parts list, you must rst set a
deletion indicator in the list.

For more information on archiving, refer to the Cross-Application Components documentation, under CA Archiving Application
Data (section on MM Materials Management ).

Addresses in Purchasing

Use
The addresses used in purchasing documents (i.e. vendor address for normal and one-time vendors, delivery address, and
storage location address) are administered using the Business Address Services (BAS) facility of the SAP System.

 Note

Up to and including the Basis Release 4.6D, the Business Address Services facility was called Central Address Management .

For further information, refer to the Basis documentation under Business Address Services (BC-SRV-ADR) .

You can store data such as the following:

Several telephone and fax numbers

E-mail addresses

Address details such as the district of a city or relevant building or part of a building complex

Activities
You can choose addresses from Business Address Services (with the option of changing them in the purchasing document) via
the menu Master data Delivery addresses .

Document Management System

Use
You can link documents stored in the Document Management System (DMS) with an item of a purchasing document. You can
then display these documents. If you print out the purchasing document and send it to the vendor, or fax the purchasing
document to the latter, the vendor will receive a list of all DMS documents linked to the item.

Activities
You will nd the function in purchasing document display or processing modes under Item More functions .

Requirement Prioritization

This is custom documentation. For more information, please visit the SAP Help Portal 16
2/10/2023

Purpose
This function enables you to prioritize requirements according to their urgency, in order that key requirements can be covered
even in bottleneck situations. With the aid of requirement prioritization, you control the sequence in which material requisitions
are serviced right through the entire supply chain. The goal is to shorten lead times from the creation of the material requisition
through to the availability of the goods supplied.

Prerequisites
You have activated requirement prioritization in Customizing for Materials Management under General Settings for Materials
Management Requirement Prioritization and de ned the corresponding priorities and their dependencies.

For more information, refer to the Implementation Guide (IMG) for Requirement Prioritization, especially under De ne
Prioritizations.

Scope of Functions
You can use requirement prioritization in the purchasing and reservation processes. You assign a requirement urgencyat item
level in purchasing and reservation documents. You have consolidated different requirement urgencies to form requirement
urgency groupsand have de ned organizational priorities In Customizing. The system determines the requirement priority as
the overall priority of a material requisition from the combination of requirement urgency group and organizational priority, This
is displayed at item level in purchase requisitions, purchase orders, and reservations.

 Note
The de nition of organizational priorities in Customizing is optional and allows you to specify further factors on which
requirement priority is to depend. Such factors can include plants and storage locations (standard SAP setting) or selected
elds at header and item levels of your purchasing and reservation documents (Business Add-In). You can also specify in
Customizing that requirement priority is to be determined exclusively in dependence on the requirement urgency group.For
more information, refer to the IMG for Materials Management under General Settings for Materials Management
Requirement Prioritization De ne Organizational Priorities .

In the case of purchase orders, the requirement priority is converted into a delivery priority taking the requirement urgency into
account and thus taken into account in deliveries. The delivery priority determined is displayed at item detail level ( Shipping tab
page) in purchase orders.

In orders, you can assign an order priority at document header level. You assign the order priority to the individual requirement
urgencies in Customizing depending on the order type. The system determines the corresponding requirement urgency and
priority for each reservation item that is created when an order is saved on the basis of this assignment.

Activities
You can use requirement prioritization in the purchasing and reservation processes.

Purchase requisitions

When creating and changing purchase requisitions, you can assign the requirement urgency at item detail level and have the
system display the requirement priority it has determined ( Source of Supply tab page).

Purchase order

You can select requisitions according to their requirement priority when creating POs via the assignment list and during
automatic PO creation. In the process, the requirement urgency and priority are adopted in the purchase order.

This is custom documentation. For more information, please visit the SAP Help Portal 17
2/10/2023
Conversion only takes place if sufficient stock is determined at the issuing storage location in the course of the
availability check.

When you create a purchase order without reference to a requisition or change a purchase order, you can assign the
requirement urgency at item level and have the system display the requirement priority it has determined.

Provided that you have made the relevant assignments in Customizing, the requirement urgency and priority are
converted into the delivery priority in purchase orders. If you have not de ned an assignment in Customizing, the system
determines the value for the delivery priority from the customer-material info record or the creditor master record as
standard. You can view the delivery priority determined on the Shipping tab page.

The requirement urgency and priority are displayed in individual overview lists of purchase orders.

Reservation

When creating and changing reservations, you can assign the requirement urgency at item level and have the system
display the requirement priority it has determined.

If an associated reservation is automatically generated when an order is created, the system assigns a requirement
urgency and a requirement priority to each reservation item. The system determines the prioritization on the basis of
the Customizing settings for Requirement Prioritization ( Assign Order Priorities ).

Requirement urgency and requirement priority are taken into account in the reservation list as selection and output
elds. This also applies to the requirement priority in the picking list.

Material requirements planning

Requirement prioritization impacts the external procurement process via requirement urgencies and priorities in
purchase requisitions and reservations. On the requirements side there is no prioritization. The requirement
prioritization is not taken into account in the MRP run.

A subsequent change in priorities does not lead to renewed MRP for the affected requirements.

The requirement priority determined for purchasing and reservation documents is displayed in the stock/requirements
list, in the planning result, and in the MRP list. However, the requirement priority is not displayed in the order report or
the pegged requirements display.

Integration of Web-Based Catalogs in Purchasing

Use
Upload and Download Catalogs

In Purchasing, you can also make use of Web-based catalogs via an OCI interface. You can not only upload purchasing data from
the system into a catalog but also download catalog data into material items of purchasing documents (requisitions with
ME51N and purchase orders with ME21N).

Send Purchasing Data to a Catalog

Using the transaction Send Purchasing Data to Catalog (transaction code MECCM), you can transfer data from the items of
purchase contracts and purchasing info records to a linked SAP Catalog Content Management System (SAP CCM) via SAP
NetWeaver XI . You can select the data to be transferred by material, vendor, purchasing organization, and receiving plant.

In addition to the selection criteria, you must enter a technical and language-independent name plus up to three language-
dependent names for the catalog that is to be generated.

This is custom documentation. For more information, please visit the SAP Help Portal 18
2/10/2023
To generate multi-lingual catalogs, you can also enter several language keys. The system attempts to read the corresponding
language-dependent long texts for the selected materials from the material master record.

A further input eld is the price determination date. This eld is prepopulated with the current date at the start of the
transaction. By entering a different, future date, you cause the system to carry out a price determination process for the
selected objects as at that date and then send the price thus calculated to the catalog system. In the event that conditions with
scales exist, note that for contracts the standard release order quantity and for purchasing info records the standard purchase
order quantity is used for price calculation purposes.

By setting the Test Run indicator, you can start the selection including price determination and check the result in a log without
a transfer taking place.

The system transfers the following data:

Material number

Material group

Price

Order unit

Planned delivery time

Vendor number

Contract number and contract item number

Number of purchasing info record

Purchasing organization

MDM Catalog Connection

If you use an SAP NetWeaver MDM catalog, you can copy not only materials, but also service structures with hierarchies from
the MDM catalog to purchase orders, purchase requisitions, and maintenance orders. This means that the MDM catalog for
services with hierarchical structures is available as a central source of purchasing information in the service procurement
process between SAP ERP and SAP SRM.

You can use service structures from an MDM catalog, which can consist of up to ve item levels. If you select more than ve
levels, the system issues an error message. You can copy individual service items or whole service structures from the MDM
catalog to purchasing documents. In addition, you can transfer purchasing data from SAP ERP to SAP SRM for the MDM
catalog.

Prerequisites
Upload and Download Catalogs

You make the technical settings for uploading and downloading catalog data in Customizing for Purchasing in the IMG activity
Web Services: ID and Description. Here you can specify several catalogs. The catalog for which you set the default indicator is
used in the transactions for purchase orders and requisitions.

Send Purchasing Data to a Catalog

To ensure correct processing of the data for Number of Purchasing Info Record and Purchasing Organization , it is necessary to
add the following entries in SAP CCM:

OCI: NEW_ITEM-PURCHINFREC

This is custom documentation. For more information, please visit the SAP Help Portal 19
2/10/2023
OCI: NEW_ITEM-PURCHORG

Also ensure that the vendor from the ERP system has been de ned as a business partner in SAP CCM.

Furthermore, you must make certain that the two new characteristics are present in the schemas of the main catalog and the
purchasing catalog:

Characteristic ID: PURCHORG INFREC

Description Purchasing organization Number of purchasing info record

OCI Field NEW_ITEM-PURCHORG NEW_ITEM-PURCHINFREC

Single or Multiple Value Characteristic? Single Single

Data Type ID PURCHORG_TYPE PURCHINF_TYPE

Data Type STRING STRING

To enable the transfer of the data, the link to the ECC system must be entered in the connected XI system. The message
interface used is CatalogueUpdateNoti cation_Out .

Subsequent Settlement
Vendors may agree to immediate or retrospective reductions in the purchase price on condition that a certain quantity or value
of goods is bought, that payment is effected promptly, or that promotional activities are carried out, for example. Conditions of
purchase involving retrospective vendor payments may also be designed to cater for situations in which the vendor bears all or
part of certain costs initially incurred by you (e.g. costs of disposal of used packaging).

Conditions can be divided into two groups: those having immediate effect based on individual invoice dates, and those requiring
"subsequent" settlement (retrospective settlement at the end of a certain period).

Conditions that have immediate effect at time of invoice

These are taken into account immediately in or at the time of processing individual vendor invoices.

Conditions that require subsequent settlement

Settlement accounting for these conditions is effected at the end of an agreed period.

For further information on how the system supports the updating of cumulative business volume, and settlement accounting,
please see ISR – SAP Retail: Subsequent (End-of-Period Rebate) Settlement . Please note that the documentation for
SAP Retail is geared towards retailing terminology (see Retail Terminology ).

Periodic Declarations (SD-FT-GOV)

This is custom documentation. For more information, please visit the SAP Help Portal 20
2/10/2023

Purpose
SAP's Foreign Trade/Customs (FT) Periodic Declarations component simpli es the creation of declarations required by customs
offices and other government authorities. Such declarations are used to maintain statistics on goods that are exported or
imported into economic zones and trade areas.

You can transfer the data required in declarations using printed documents, diskettes, EDI procedures and/or by email.

With this component, you can create customs declarations required by the European Union (EU), the European Free Trade
Agreement (EFTA), the North American Free Trade Agreement (NAFTA) and Japan.

Integration
To create customs declarations, this component copies data from SAP's Materials Management (MM) and Sales and
Distribution (SD) documents. When you create import declarations, this component copies data from MM's purchase orders,
goods receipts, and invoice receipts. When you create export declarations, it copies data from SD's billing documents.

Features
Creation of customs declarations (illustrated in above graphic)

Creation of declarations in the foreground or as a batch process in the background

Transmission of declarations on paper, diskette, magnetic tape, EDI format, or by email depending on government
requirements

This is custom documentation. For more information, please visit the SAP Help Portal 21
2/10/2023
Test runs before creating customs declarations

Comprehensive log of incomplete items to support the creation of accurate and complete customs declarations

Creation, display and printing of goods catalogs required by the authorities

See also:

Cockpit - Periodic Declarations

Communication/Printing

Return to Foreign Trade / Customs main topic.

Cockpit - Periodic Declarations

Use
Foreign Trade's Cockpit for Periodic Declarations is designed to provide you with a quick, easy-to-use overview of the most
important functions in the area of declarations to the customs authorities.

To go to the Cockpit for Periodic Declarations from the SAP main menu, choose Logistics Sales and Distribution (or
Materials Management) Foreign Trade/Customs Periodic Declarations Cockpit – Periodic Declarations .

Prerequisites
Before using the function for Special Regulations (see below), you need to set up the corresponding tables in Customizing as
follows:

Choose Sales and Distribution (or Materials Management Purchasing) Foreign Trade/Customs Periodic
Declarations

Features
There are ve sections in the Cockpit for Periodic Declarations:

Screen Section Function

Operations Create periodic customs declarations

Maintain declaration data

Perform archiving tasks

Monitoring Display and update foreign trade data in material master records

Goods catalog Create and display goods catalogs

Settings Make relevant settings in the Implementation Guide (IMG)

Additional Declaration Germany Create declaration for foreign trade in Germany involving mineral oil
products

These sections are described in more detail below:

This is custom documentation. For more information, please visit the SAP Help Portal 22
2/10/2023
Additionally, there is a text area or picture container on the initial screen for Periodic Declarations . In this area, you can display
either a picture or a text. You can include the standard picture or text in this screen from Customizing or by choosing
Environment Maintain user data from the initial screen. The standard picture is SD_FT_GOV_START. You can create a
standard text for display in this area by choosing Tools Form print SAPscript Standard text from the SAP standard
menu.

Operations

Create Periodic Declarations

For creating periodic declarations, the user interface presents several processes associated with customs declarations on a
single screen. For example, if you select INTRASTAT declaration for France, the following easy-to-use options are available for
inbound and dispatched goods:

Select data

Create a data le

Print a form

Create a diskette

You can select each of these options with a con gurable variant or execute all steps with a variant. Options that are not
available for selected countries (such as creating a diskette) are suppressed when you select the respective country.

 Note

Once you execute a step, choose Help Application help from the menu bar to display detailed information about each of
the reports.

From the display lists, you can view and modify incomplete document items in SD billing documents (see Data Selection for
Declarations ) or MM purchase orders without leaving the transaction screen.

Individual maintenance

The individual maintenance tasks enable you to display and maintain data relevant to INTRASTAT and EXTRASTAT declarations.
For example, you can retrieve declarations and modify the data before sending it to the customs authorities. (See Add and
Change Entries .)

Archiving INTRASTAT/EXTRASTAT

Archiving functions enable you to archive INTRASTAT and EXTRASTAT records, delete them, and if required, reload them back
into the worklists.

Monitoring

In this section, you can display and update foreign trade data in material master records.

Goods Catalog

In this section you can create and display goods catalogs on paper or on disk for submission to the authorities. See Goods
Catalog .

Settings

This is custom documentation. For more information, please visit the SAP Help Portal 23
2/10/2023
This section contains two customizing wizards that allow you to follow step-by-step procedures that ensure that your settings in
Customizing are correctly maintained. You use these wizards to con gure customizing tables for

Dispatch / Export

Receipt / Import

Additional Declaration Germany

Foreign trade activity involving mineral oil products in Germany requires an additional declaration. Here you can create the form
for the mineral oil declaration.

Additional Information

For reporting purposes, you can use the ABAP List Viewer for several standard functions, such as sorting or ltering items
displayed on your screen.

Activities
To ensure efficient processing of foreign trade data for functions that are repetitive in nature, you can create variants and save
them in the system. See Using Variants .

Creation of Periodic Declarations

Purpose
This topic describes the general process for creating a customs declaration. The process involves selecting relevant data from
purchasing or billing documents and then creating the declaration based on that data.

This is custom documentation. For more information, please visit the SAP Help Portal 24
2/10/2023

Prerequisites
If required, create a goods catalog and submit it to the customs authorities if they do not have one already on le for your
company. For more information, see Goods Catalog .

Process Flow
You enter the parameters the system uses to select data for the declaration.

For example, you can have the system select relevant data from purchasing documents or billing documents for the past month.

Based on these parameters, the system selects the data and writes the selected data to an intermediate database. The
intermediate database is also called a sequential le.

You can use the data in the intermediate database as many times as needed. However, if you run another data selection, the
system overwrites data currently in the intermediate database.

The system can require a lot of processing time to select billing documents and incoming invoices for a declaration. It is
recommended that you carry out the data selection in background processing.

The table below lists the intermediate databases the system creates.

Economic zone Declaration Intermediate database

This is custom documentation. For more information, please visit the SAP Help Portal 25
2/10/2023

Economic zone Declaration Intermediate database

EU INTRASTAT VEIAV

EXTRASTAT VEXAV

KOBRA VEKAA, VEKAB, VEKAC

EFTA VAR VEXAV

NAFTA AERP VESED

SED VESED

HMF VESED

Since the Japanese declarations supported by the SAP System are paper-based, the system does not create intermediate
databases for them.

You create the declaration on paper, magnetic tape, or diskette depending on the requirements of the customs officials.

The system generates the country-speci c layouts for declarations on paper and the country-speci c data record structures for
declarations on magnetic tape or diskette.

If you want to create a declaration on magnetic tape or diskette, rst create a le from the selected billing documents or goods
receipts. Then transfer the le to tape or diskette. You can transfer the le to diskette from within the SAP System, but to
transfer the le to magnetic tape, you must do so outside of the SAP System.

The graphic below summarizes the declaration process.

This is custom documentation. For more information, please visit the SAP Help Portal 26
2/10/2023

See also

Data Selection for Declarations

Creating Declarations on Diskette or Magnetic Tape

Data Selection for Declarations

This is custom documentation. For more information, please visit the SAP Help Portal 27
2/10/2023

Use
This function selects Materials Management (MM) and Sales and Distribution (SD) documents relevant for declarations to
authorities. To limit the documents the system selects, enter criteria like the company code and reporting month and year. For
export/dispatch declarations, you can also specify the billing document types the system searches.

Features
Test Runs and Live Data Selection

The system can select the data in a test or a live (productive) run. In a test run, the selected data appears on the screen and
you can print it, but the system does not store the data in an intermediate database. In productive runs, the system overwrites
the data that currently exists in the intermediate database.

The SAP System supports data selection for the following declarations:

For the US , the AERP

For the EU, KOBRA, INTRASTAT (dispatches only), and EXTRASTAT (exports only)

For EFTA, the VAR

During data selection, the system selects only documents that have already been posted to FI accounting. In a live run, the
selected data appears on the screen and is saved in an intermediate database. You can call the data from the database at any
time.

Incompletion Logs

For both test and productive runs, the system can generate incompletion logs. The incompletion log lists data that is required
for the declaration but is missing from the selected documents. You can change existing data or enter missing data in the
corresponding documents directly from the log of incomplete items.

Log of Open Business Transactions

When you select customs declaration data for dispatch/export, in addition to the selection log and log of incomplete items, the
system also issues a log that displays documents that have not been posted to FI (Financial Accounting). This log of blocked
"open business events" appears in the navigation tree when you display either the selection log or the incompletion log. The
reason for the entry in this log appears in parentheses next to the document number. If you change a document in this list to
correct the reason for its entry in this log, the system will move it either to the log of incomplete items (if data is missing) or to
the selection log when you post it to FI.

Afterwards, you need to select Refresh log to update the data listed .

Activities
You can execute this function from the Cockpit for Periodic Declarations . To access this function from the cockpit's initial screen,
choose Create Periodic Declarations. Data selection is the rst step for the corresponding country. The Log type eld
determines whether the selection of data is simulated or a live run that will update data in the intermediate database.

When you execute this function, the system displays a list with the selected documents. If the selection was a productive run,
the system overwrites the data in the intermediate database with the list.

From this list, you can

View the incompletion log (if you selected B, E, or F in the Log type eld).

This is custom documentation. For more information, please visit the SAP Help Portal 28
2/10/2023
Print the list of selected documents

Save the list of selected documents in a le

Display a document listed in the incompletion log (for export and dispatch declarations)

Add data to a document listed in the incompletion log (for import and receipt declarations)

Create a declaration based on the list

 Note
If you access a document from the incompletion log and change its data, you need to run data selection again to
include the revised data in the intermediate database.

You can also update the data by selecting Update log of incomplete items.

See also:

Add and Change Entries

Incompletion Log for Declarations

De nition
A list of billing or purchasing documents that are missing data required in declarations to authorities.

Use
From logs of incomplete items created during data selection, you can access the listed documents and enter the missing data.
From incompletion logs created during live data selection of billing documents, you can only display the listed documents
because these documents have already been posted to the Financial Accounting (FI) application component. From
incompletion logs created during live selection of purchasing documents, you can still change documents that are missing data.

The elds the system checks come from the declaration’s intermediate database. You can change the scope of the incompletion
log in Customizing for Foreign Trade/Customs . Choose Sales and Distribution Foreign Trade/Customs Periodic
Declarations Control Data Log of Incomplete Items - Aggregation Criteria - Individual Maintenance . On that screen,
you can specify for countries and declarations which elds in each document must be complete. For example, you can require
that purchasing documents for INTRASTAT declarations in Germany must contain import code numbers.

Creating Declarations on Paper, Diskette or Tape

Use
In this task, the system formats preselected data based on the requirements of the reporting country and transfers it to paper
or to a diskette.

The SAP System supports transferring a declaration’s le to diskette and the procedure for transfer appears below. The SAP
System does not support transferring a le to magnetic tape. If you want to submit the declaration on magnetic tape, you must
This is custom documentation. For more information, please visit the SAP Help Portal 29
2/10/2023
transfer the le outside of the SAP System.

Prerequisites
Before you create a declaration on paper or diskette, you must rst create a le based on the selected billing documents or
purchasing documents. The data selected is written to an intermediate database (sequential le) (see Creation of Periodic
Declarations ).

Select documents for the declaration. See Data Selection for Declarations .

If you are working on a PC, make sure that it is possible to transfer data from the UNIX le of your PC.

Creating a File Based on the Selected Documents


You can execute this function from the Cockpit for Periodic Declarations .

To access this function from the cockpit's initial screen, choose Create Periodic Declarations.

Based on the economic zone and the type of declaration, choose the corresponding declaration type and country from the menu
displayed on the left.

Data selection is the rst step for the corresponding country. Choose Step 1 to select the data.

Creating a le or form is the second step. Choose Step 2 to create the le.

Maintain the parameters for creating the le.

Be sure to enter a full name in the File name for output eld.

Choose Program → Execute .

If you selected the Issue log eld, the data appears on the screen and can be printed as required. If you selected the Create le
eld, the system creates the le with the name you assigned.

Transferring a File to a Diskette or Hard Disk


You can execute this function from the Cockpit for Period Declarations .

To transfer a le to a diskette or hard drive, rst perform the rst two steps above. File transfer to a diskette is the third step.

This step is not available for all countries. If it is not available, the Step 3 button will be repressed and you cannot select it.

Choose Step 3 and enter the criteria for the data transfer.

Choose Program → Execute .

If you selected the Issue log eld, the le’s contents appear on the screen. You can print this data as necessary.

If you selected the Copy le eld, the system transfers the le to the designated diskette or hard disk. Before transferring the
le, the system displays a dialog box prompting you to con rm or change the path or lename.

This is custom documentation. For more information, please visit the SAP Help Portal 30
2/10/2023
Choose Transfer in the dialog box.

Choose Continue .

Printing Diskette Labels


To support the exchange of data carriers, you can print labels for 3.5-inch diskettes.

Choose Create Periodic Declarations from the Cockpit for Periodic Declarations .

Start the le creation (or, if applicable, CUSDEC/INSTAT) program application (Step 2).

The system displays a navigation tree on the left side of the screen and a document selection screen on the right.

Start the printing function by choosing Diskette label from the navigation tree.

Label printing is only possible if you rst create a le.

Creating and Printing Cover Sheets


In addition to the disk label, you can print a cover sheet with the most important information about the customs declaration.
The system creates the cover sheet in DIN A4 format (or letter format for AERP/SED declarations). Like the diskette label, you
can create the cover sheet from the navigation tree. The print information is not restricted to any output medium (such as
form, le/diskette).

Aggregation of Data in Declarations

Use
This function reduces data volume by aggregating declaration data based on criteria you de ne. This function is especially
useful when you create declarations on paper because it can considerably reduce the number of lines to be declared. For
example, the function can combine all items that have the same commodity code to a single line while aggregating quantities
and values such as statistical values and net tare masses for these items.

 Example

As an example, consider the following four data items:

Commodity Code Value

12340815 US$ 10,000

12340817 US$ 20,000

12340815 US$ 5,000

12340817 US$ 2,000

This is custom documentation. For more information, please visit the SAP Help Portal 31
2/10/2023
The system would aggregate these four items as follows:

Commodity Code Value

12340815 US$ 15,000

12340817 US$ 22,000

This function is available for the Swiss VAR declaration and the EU declarations INTRASTAT, EXTRASTAT, KOBRA and NAFTA.

Prerequisites
According to your national declaration regulations, de ne aggregation criteria in Customizing for Foreign Trade/Customs .
Choose Periodic Declarations Control Data Log of Incomplete Items - Aggregation Criteria - Individual Maintenance .
To use a characteristic as an aggregation criterion for a country and declaration, select the Aggreg. crit. column.

If you do not de ne aggregation criteria, the system uses its defaults that correspond to official requirements.

Add and Change Entries

Use
This function adds or changes records in a declaration’s intermediate database. This function, available only for INTRASTAT,
EXTRASTAT and VAR declarations, edits the respective intermediate databases, VEIAV and VEXAV, directly.

Use this function if you need to do any of the following to data selected for declarations:

Complete or correct data in billing document already posted to the Financial Accounting (FI) application component

Make any other changes to declaration data

Prerequisites
To control which elds in the database this function treats as display-only, changeable, and required, choose the following in
Customizing for Foreign Trade: Periodic Declarations Control Data Log of Incomplete Items - Aggregation Criteria -
Individual Maintenance . Then select the line corresponding to the country and eld you want to maintain and choose Goto
Details . Enter the settings for the eld under Field selection for maintenance transaction (this section only appears for
INTRASTAT and EXTRASTAT declarations).

Activities
You can perform this function from the Cockpit for Periodic Declarations .

1. To execute this function from the Operations section of the cockpit, choose Individual maintenance for INTRASTAT or
EXTRASTAT declarations .

2. Based on the criteria you enter on the selection screen, the system displays a list of records.

3. From the display screen, you can change existing records or add new records.

The system saves the revised data in the intermediate database.

This is custom documentation. For more information, please visit the SAP Help Portal 32
2/10/2023

Checklist for Creating Declarations

Purpose
Problems creating declarations to authorities are often caused by incomplete data. This process lists the data you need to fully
maintain to create declarations. It covers data in Customizing , master records, and documents.

 Note

Implementation "Wizards" are provided for both dispatch/dxport and receipt/import on the initial screen of the Cockpit for
Periodic Declarations .

Process Flow
Data in Customizing

To go to Customizing for Foreign Trade, choose Sales and Distribution Foreign Trade/Customs in the Implementation
Guide (IMG).

1. Maintain your company’s ID number.

2. You can maintain this number in Customizing for Foreign Trade/Customs . Choose Sales and Distribution Foreign
Trade Periodic Declarations Maintain Official Numbers for Declarations to Authorities . Select your company code
and choose Goto Detail . Select Additional details . Then enter your company’s number in the appropriate eld(s).

3. Maintain the appropriate region code.

4. In Customizing for Foreign Trade/Customs , choose Periodic Declarations Maintain Region. Then in the State of
manufac. eld, enter the region or state of manufacture.

5. Maintain the commodity code and special unit of measure.

6. In Customizing for Foreign Trade/Customs , choose Basic Data for Foreign Trade De ne Commodity Codes/Import
Code Numbers by Country . Select a line and choose Goto Details . In the Spec. unit of measure eld, enter the
unit.

7. Maintain the default business transaction type table.

8. In Customizing for Foreign Trade/Customs , choose Basic Data for Foreign Trade De ne Business Transaction Types
and Default Value De ne Default Business Transaction Type .

9. Maintain the import/export procedure.

10. In Customizing for Foreign Trade/Customs , choose Basic Data for Foreign Trade De ne Procedures and Default
Value De ne procedure default .

11. Maintain the completeness check.

12. In Customizing for Foreign Trade/Customs , choose Periodic Declarations Log of Incomplete Items - Aggregation
Criteria - Individual Maintenance. Make sure only the relevant declarations are selected for each eld name and
country.

13. Maintain the currency conversion.

14. If the document currency differs from the local currency, the system converts the value into the local currency if the
relevant tables contain the correct settings. In Customizing , choose General Settings Currencies Enter
exchange rates . Be sure to maintain the currencies for conversion in both directions (for example, USD to DEM and
DEM to USD). You can also check the entries under Set decimal places for currencies and Check exchange rate types .
This is custom documentation. For more information, please visit the SAP Help Portal 33
2/10/2023

Some countries’ customs authorities use their own exchange rate for official declarations. You can take this rate into
account by using the parameter "exchange rate type I" when selecting data for INTRASTAT declarations. You must also
maintain the exchange rate tables accordingly.

15. Maintain the route de nition (relevant only for dispatches).

16. You can maintain the mode of transport in the route’s Details screen. The system automatically copies this mode of
transport into the foreign trade header data if a route is assigned to the delivery or billing document.

To display the detail screen for route de nition, choose the following in Customizing for Sales and Distribution :
Basic Functions Routes De ne Routes De ne Routes and Stages . Select the route and choose Goto
Details .

17. Maintain the transportation connection point de nition (relevant only for dispatches).

You can select a transportation connection point as the border crossing point as part of the leg, which, in turn, is part of the
route. The system automatically transfers the office of exit entered for the transportation point to the foreign trade header
data only if the point is marked as the border crossing point and the address for the point is maintained (especially the Country
eld).

In Customizing for Sales and Distribution , choose Basic Functions Routes De ne Routes De ne Transportation
Connection Points .

Data in Master Records

1. In the material master record, maintain all data relevant for export and dispatch.

2. On the General Data screen of the customer master record, maintain the customer’s EC VAT registration number.

3. On the Control screen of the vendor master record, maintain the vendor’s EC VAT registration number, the mode of
transport and the customs office of entry.

Data in Documents

Foreign trade data must be maintained for all documents relevant for declarations. If, for example, you want to select credit
memos for a declaration, you must also maintain foreign trade data in the credit memos. The system selects only those
documents containing foreign trade header or item data.

1. Maintain pricing data.

Make sure that the invoice value or purchase value and statistical value are maintained. So that the system can calculate the
statistical value, do the following:

Maintain condition type GRWR in the pricing procedure

Create the corresponding condition records for condition type GRWR

1. Maintain delivery and billing (Sales and Distribution) data.

2. Maintain the dispatch data (under Foreign Trade data ) in the header and in the items.

3. Maintain purchase order (Materials Management) data.

Maintain the goods receipt data in the header (choose Header Import ) and in the items (choose Item More
functions Import ).

This is custom documentation. For more information, please visit the SAP Help Portal 34
2/10/2023

Special Business Cases in Declarations

Use
This function includes special purchasing transactions like third-party and consignment orders in the selection report. It also
supports enhancements to purchasing documents.

Features
Special Purchasing Transactions Included in the Selection Report

Third-party Orders

Purchase orders having the item category S and for which no goods receipt but only an invoice receipt has been recorded are
also taken into consideration.

 Note

If a dealer in country A procures material for a customer in country A from a vendor in country B, and the material is
delivered directly to the customer by the vendor, the PO is selected in the dealer’s system for the INTRASTAT declaration of
arrivals.

If the dealer, customer, and vendor are each located in different countries, the purchase order must be excluded from the
INTRASTAT declaration unless the countries of the dealer and customer constitute a single declaration entity (that is, they have
the same INTRASTAT reference number).

Consignment Orders

The goods receipt is valuated with the consignment price from the consignment info record.

Subcontract Orders

You can send the material components to the subcontracting vendor through an SD delivery and a pro forma billing document.
The system calculates the value of the PO item using the material valuation price.

Upon receipt of the processed material from the subcontractor, the system checks during the selection run how much material
has been delivered. By applying the new condition type GWLB, the system determines the proportionate value at the time the
materials crossed the border (statistical value). This gure is added to the previous statistical value (GRWR).

Return Deliveries and Credit Memos

With regard to material that you regard as unacceptable due to quality de ciencies, you can either return the material to the
vendor or elect to receive a credit memo for it.

The return delivery is initiated with the aid of report RMEXST00. This report converts the import data from the purchase order
into export data.

In the case of a credit memo, report RMIMST00 reduces the invoice value accordingly.

Enhancements to Purchasing Documents and User Exits

Purchasing Documents

This is custom documentation. For more information, please visit the SAP Help Portal 35
2/10/2023
In the purchasing documents, the exclusion indicator can be set at header and item levels. If you set the indicator at header
level, it applies to the entire document regardless of the indicator in the individual items.

The screen control and default values for the import data screens depend on the goods supplier (supplying vendor) – if one has
been maintained – not on the vendor in the purchase order.

If the goods supplier in the PO header is changed, the system then updates the default values of all already existing PO items.

User Exits

The following user exits are available for the default values of the import data screens:

EXIT_SAPLV50E_002 for the import data in the PO header

EXIT_SAPLV50E_004 for the import data in the PO item

The system determines the default values from the master data of the material and vendor master records and the info record.
If required, you can set customer-speci c default values using the exits.

Customer Exits for Periodic Declarations

Use
Customer exits in Foreign Trade/Customs (FT) allow you to de ne your own logic based on your own requirements. The following
customer exits are available for use in the FT Periodic Declarations component:

Customer Exits for Periodic Declarations

SAP Enhancement Project User Exit Title

FTGOVSEL EXIT_SAPLV50G_001 Data Selection

FTGOVSEL EXIT_SAPLV50G_002 Database update

You can modify and use these customer exits to

In uence the task of selecting declaration data

Change declaration data

Determine how data will be saved to the database.

Prerequisites
De ne exclusion indicators and assign them to item categories using the following steps in Foreign Trade/Customs Customizing
under Periodic Declarations :

De ne Exclusion/Inclusion Indicators:

Assign to Item Categories for SD Sales Orders

Assign to Item Categories for SD Deliveries

Activities
This is custom documentation. For more information, please visit the SAP Help Portal 36
2/10/2023
The following customer exits were available prior to Release 4.6c. In these customer exits, you could not select certain item
categories for customs declarations.

Cust. Exit Program Trans. Declaration type

RVEXKUEI RVEXST00 VE01 INTRASTAT

RVEXKUE2 RVEXEX00 VE04 EXTRATSTAT

RVEXKUE3 RVEXKO00 VE13 KOBRA

RVEXKUEA RVEXCH00 VE21 VAR

RVEXKUEI RVEXSE00 VE18 AERP/SED

RVEXKUEI RVEXSE01 VE25 AERP/SED

RVEXKUEI RVIVST00 VI98 INTRASTAT: Spec. bus. cases

The customer exits in this table have been deactivated and you can no longer use them. Instead, you should con gure your
system to use or exclude speci c item categories. You can de ne exclusion indicators in Customizing using the Table
Declarations to Authorities: Exclusion/Inclusion Indicators . You can then assign the exclusion indicators to item categories
(see Prerequisites above). When you select these documents for the relevant customs declarations, the system then checks
whether a certain item category should be excluded from the relevant declaration type.

Additionally, you need to transfer any of your own coding (that exists in the customer exits listed in the table above) into the
two available customer exits (EXIT_SAPLV50G_001 and EXIT_SAPLV50G_002 ).

See also:

Detailed information is available in SAP Note 146279.

Goods Catalog

De nition
A document kept on le with the authorities that lists the materials your company imports or exports.

Goods catalogs contain materials’ commodity codes and import code numbers for keeping foreign trade statistics.

Use
In cases like INTRASTAT and EXTRASTAT declarations in Germany, the authorities will only accept a declaration made on diskette
or magnetic tape (according to the simpli ed procedure) if they have a goods catalog for your company on le. In addition, your
company must rst have approval from the authorities to use the simpli ed procedure.

You must give the authorities an updated catalog yearly. After you submit your company’s rst goods catalog, the authorities
assign the catalog a number. Use this number when you submit updates to your company’s goods catalog.

You can create a goods catalog on paper or on disk. When you create a goods catalog, the system searches the database for
material numbers in your system and creates the goods catalog for your company.

Creating Goods Catalogs

You can create goods catalogs from the Cockpit for Periodic Declarations .

This is custom documentation. For more information, please visit the SAP Help Portal 37
2/10/2023

 Note

When you create a goods catalog for the rst time, select all of the materials relevant for your country and company code.
For future goods catalogs, enter a date in the New materials from eld to mark all materials in the catalog that are new
compared to the previous version.

To save the le version to disk from the display screen, choose List Save File and save the output in rich text
format.

EU Declarations
Use

This function creates the following declarations for EU member-state authorities.

Declaration Supported for paper or diskette? Comments

Intra European Trade Statistics One or both depending on the country Supported for all EU-member states
(INTRASTAT)

Extra European Trade Statistics Disk only Supported only for Germany and the
(EXTRASTAT) Netherlands

Kontrolle bei der Ausfuhr (KOBRA Disk only Applies only to Germany
declaration)

INTRASTAT Declarations

De nition
Monthly declaration that provides EU authorities with statistics on foreign trade within the European Union (EU) (for example,
trade between France and Germany).

There is one intra-European Union trade statistics ( INTRASTAT ) declaration for receipts (arrivals) and one for dispatches.

Use
Since the establishment of the single European market on January 1, 1993, the economies of the member states of the
European Union have become increasingly interdependent. To assess their international competitiveness and dependency of
individual products and sectors on import and export, as well as monitor price developments in foreign trade, it is still necessary
for EU member states to keep statistical records of trade within EU borders, even after the removal of internal tariffs.

The new system developed to keep these records within the EU is the INTRASTAT system.

 Note

This note is valid for Germany only.

As of January 1, 1993, companies with a turnover of more than 200,000 German Marks in the current year or in the previous
year are required to make regular Intra-EU trade statistics declarations (INTRASTAT declarations). All deliveries made and
received within the EU during the reporting period must be reported in the INTRASTAT declarations.

This is custom documentation. For more information, please visit the SAP Help Portal 38
2/10/2023

Data Required for INTRASTAT Declarations


The following reports from the European Commission provides you with information (from the Official Journal of the European
Communities 96/C 378/02) on the data required by member states from traders (according to articles 21 and 23 of Regulation
(EEC) No. 3330/91 of the European Parliament).

These reports use the ISO Alpha 2 country codes listed in the table shown below.

This is custom documentation. For more information, please visit the SAP Help Portal 39
2/10/2023
Information Required for Dispatches

Transmission Deadline for Dispatch

This is custom documentation. For more information, please visit the SAP Help Portal 40
2/10/2023

Information Required for Receipts

This is custom documentation. For more information, please visit the SAP Help Portal 41
2/10/2023

Transmission Deadlines for Receipts

This is custom documentation. For more information, please visit the SAP Help Portal 42
2/10/2023

Constraints to INTRASTAT Declarations


The following constraints apply to INTRASTAT declarations:

Invoiced value of goods reported

Goods movements not relevant for declaration

Customer-speci c settings

Integration

Return deliveries

Invoiced Value of Goods Reported


The following invoiced values of goods must be reported in the INTRASTAT declaration:

Invoice value

The amount stated in the invoice in the relevant currency

Statistical value

Value of goods before tax, including transportation and insurance costs, which arise in the exporting member state when the
export is made

Goods Movements not Relevant for Declaration


The following goods movements are not relevant for the INTRASTAT declaration:

Tax free goods movement between bonded warehouses

Goods movement between free trade areas

Free shipments to non-EU states of non-resaleable samples

Customer-Speci c Settings
See Customer Exits for Periodic Declarations .

Integration
This is custom documentation. For more information, please visit the SAP Help Portal 43
2/10/2023
To create an INTRASTAT declaration for receipts, the system uses values from either invoices for goods receipts or purchase
orders as in the following example.

 Example

In Germany, the INTRASTAT declaration must be sent to the relevant authorities ten working days after the end of the
reporting month at the latest. If no invoice exists for a goods receipt following the reporting month, the declaration of goods
is postponed until the following month. If no invoice has been received a month later, the system uses the purchase order to
determine the value of the goods and the goods movement is reported.

Return Deliveries
Inbound deliveries, such as customer returns, are processed organizationally in Sales and Distribution. Records of transactions
involving foreign trade are kept, for example, by intra-European Union trade statistics (INTRASTAT), and there is a requirement
to submit customs declarations for such receipts and imports to the responsible government authorities.

Process in the System

For customer returns as well as credit memos, debit memos, or other documents that are referenced to an inbound delivery,
entries are created for the purpose of maintaining trade statistics for the receipt and import of commodities.

Example for an SD Return Process

For example, your business delivers goods to a customer in another EU member state. When the goods are received and
inspected, your customer discovers that part of the delivery is damaged. For the subsequent damaged goods regulations or
warranty process, the following possibilities exist:

1. The damaged goods are returned to you for a credit memo.

2. The damaged goods remain with the customer and a credit memo is issued.

3. The damaged goods are returned and you deliver a cost-free replacement.

4. The damaged goods remain with the customer and you deliver a cost-free replacement.

The ensuing process is as follows:

1. For the returned goods, you need to submit an INTRASTAT declaration for receipts. The values in the credit memo must
be paid.

2. You need to create a declaration for the dispatch. The amount of the credit memo for the damaged goods must be
included.

3. If the INTRASTAT declaration for the dispatch has not yet been submitted, the credit memo can be excluded immediately.

If the INTRASTAT declaration has already been submitted, the original declaration for the dispatch must be corrected.

4. You need to submit an INTRASTAT declaration for receipts for the returned damaged goods. For the replacement
delivery, you need to submit an INTRASTAT declaration for dispatches.

5. For the delivered replacement goods, you need to submit an INTRASTAT declaration for dispatches (again).

Media Supported for INTRASTAT Declarations


The table below lists the media the SAP System supports for INTRASTAT declarations.

This is custom documentation. For more information, please visit the SAP Help Portal 44
2/10/2023

Transmission of Declarations by Email


This is custom documentation. For more information, please visit the SAP Help Portal 45
2/10/2023
The SAP Foreign Trade / Customs application component supports the transmission of INTRASTAT customs declarations in
EDIFACT format CUSDEC/INSTAT for Great Britain, Portugal and Sweden. You can send the data les created by the system to
the authorities either by diskette or via Internet as an attachment to an email message.

Internet Transmissions
You can transmit INTRASTAT declarations as an attachment to an email message via the Internet to the customs authorities in
EDIFACT format CUSDEC/INSTAT to three EU member states: the United Kingdom, Portugal and Sweden.

If your system can access the Internet, you can create the email in the SAP System and send it. To transmit the declarations via
email, choose Create Periodic Declarations from the Cockpit for Periodic Declarations . Start the CUSDEC/INSTAT program
application (Step 2) for the United Kingdom, Portugal or Sweden. In the navigation tree on the left side of the screen, choose
Send le via Internet .

As an alternative, you can save the declaration on your hard drive as a le. From there, you can manually attach the le to an
email message. It is important to ensure that the name of the attached le is uniquely identi ed (for example with the year,
month, and a sequential number).

The following email addresses are valid as of December 1999 and may be used for sending declarations to the customs
authorities:

Sweden: idep@scb.se

Portugal Lisbon: aixa@ine.pt

Porto, Portugal: neci.drn@ine.pt

United Kingdom: edcs@edcsdata.hmce.gov.uk

 Note

You can save email addresses for the customs authorities in Foreign Trade/Customs Customizing for Periodic
Declarations under Data Selection Control .

Before you send a declaration to one of these offices, please contact them rst.

Who to Contact for INTRASTAT Information


The following addresses and telephone numbers are provided as a service by SAP. Please contact the appropriate office in each
respective country for questions you may have regarding INTRASTAT declarations to the authorities in those countries.

Offices Responsible for INTRASTAT in EU Member States

Austria Österreichisches Statistisches Zentralamt (Östat)

Abteilung 4: Außenwirtschaft und Verkehr

Hintere Zollamtsstraße 2b

Postfach 40 00

A - 1033 Wien

Tel.: (0043) 1 / 7 11 28 76 54

Fax: (0043) 1 / 7 15 07 48

Belgium Banque Nationale de Belgique (BNB)

This is custom documentation. For more information, please visit the SAP Help Portal 46
2/10/2023
Statistique du Commerce Extérieur

boulevard de Berlaimont 14

B - 1000 Bruxelles

Tel.: (0032) 2 / 221 3728

Fax: (0032) 2 / 221 31 46

Denmark Danmarks Statistik

Sejrøgade 11

DK - 2100 København Ø

Tel.: (0045) 39 17 39 17

Fax: (0045) 31 18 48 01

Finland National Board of Customs

Statistical Unit

Box 512

FI - 00101 Helsinki

Tel.: (003 58) 96 14-1

Fax: (003 58) 96 14 28 13

France Ministère de l'Economie, des Finances et du Budget

Direction Général des Douanes et Droits Indirects

8. rue de la Tour des Dames

F - 75436 Paris Cédex 09

Tel.: (0033) 1 / 55 07 49 19

Fax: (0033) 1 / 55 07 49 41

Germany Statistisches Bundesamt

Gruppe VB Außenhandel

D - 65180 Wiesbaden

Tel.: (0049) 611 / 75 34 22

Fax: (0049) 611 / 75 39 65

Greece National Statistical Service of Greece (NSSG)

Industrial and External Trade Statistics

Unit: INTRASTAT

14-16 Rue lycourgou

GR - 10166 Athenes

Tel. / Fax: (0030) 1 / 3 24 93 72

Ireland Customs and Excise - Statistics Division

The Revenue Commissioners VIMA Office

Newry Road co. Louth

IRL - Dundalk

This is custom documentation. For more information, please visit the SAP Help Portal 47
2/10/2023
Tel.: (00353) 42 / 2 62 62

Fax: (00353) 42 / 3 61 84

Italy Instituto Nazionale di Statistica (ISTAT)

Servizio Commercio Estero

Via Cesare Balbo. 16

I - 00184 Roma

Tel.: (0039) 6 / 46 73 + ext

Fax: (0039) 6 / 46 73 25 60

Luxembourg STATEC

Service central de las statistique et des etudes economiques

B.P. 304

L - 2013 Luxembourg

Tel.: (00352) 478 - 1

Fax: (00352) 46 42 89

Netherlands Centraal Bureau voor de Statistiek (CBS)

International Trade

Kloosterweg 1

P.O. Box 4481

NL - 6401 CZ Heerlen

Tel.: (0031) 45 / 5 70 60 00

Fax: (0031) 45 / 5 72 74 40

Portugal Instituto Nacional des Estatistica (INE)

Dep. Estatisticas dos Services - INTRA

Av. de Antonio de José Almeida

P - 1078 Lisboa

Tel.: (00351) 1 / 8 47 00 50

Fax: (00351) 1 / 8 47 39 66 or 8 48 94 80

Spain Agencia Tributaria

Subdirección General de Plani cación y Estatistica

en el Departemento de Aduanas e II. EE.

Guzmán el Bueno. 137

E - 28071 Madrid

Tel.: (0034) 1 / 5 54 32 00

Fax: (0034) 1 / 5 54 78 96

Sweden Statistics Sweden

Foreign Trade ES/IN

Box 24300

This is custom documentation. For more information, please visit the SAP Help Portal 48
2/10/2023
S - 10451 Stockholm

Tel.: (0046) 8 / 7 83 40 00

Fax: (0046) 1 / 7 83 45 71

United Kingdom Tariff and Statistical Office

HM Customs and Excise

Portcullis House

27 Victoria Avenue

Southend-on-Sea

GB - Essex SS2 6AL

Tel.: (0044) 17 02 / 36 + ext.

Fax: (0044) 17 02 / 36 65 96

Issuing INTRASTAT/EXTRASTAT Declarations

Prerequisites
Before issuing an INTRASTAT or EXTRASTAT declaration:

If you plan to submit the declaration on diskette, create a goods catalog if required by your country’s authorities

Select data for the declaration

For more information, see Goods Catalog and Data Selection for Declarations .

Procedure
You can create INTRASTAT declarations from the Cockpit for Periodic Declarations .

1. From the Cockpit for Periodic Declarations , choose Create Periodic Declarations.

2. Select the appropriate country under the corresponding declaration type.

3. Choose File or Form as necessary and execute Step 2 .

4. Enter the parameters for the declaration and choose Program Execute.

See also:

For information on transferring the declaration to diskette, see Creating Declarations on Paper, Diskette or Tape .

Declaration of Foreign Trade Involving Mineral Oil Products

Use
The clearance form for the declaration of foreign trade involving mineral oil products in Germany is available in the SAP Foreign
Trade/Customs application component.

This is custom documentation. For more information, please visit the SAP Help Portal 49
2/10/2023
All goods movements involving mineral oil products must be declared by the 20th day of the following month to the Bundesamt
für Wirtschaft (Federal Office of Economics in Germany). For the declaration of these products, the SAP System identi es the
relevant items in the INTRASTAT declaration(recorded in the table for INTRASTAT data VEIAV) based on the mineral oil indicator
in the corresponding commodity codes.

Prerequisites
As a rst step, you must perform the data selection for the corresponding INTRASTAT declaration for the desired time period
(see Data Selection for Declarations ).

Procedure
You can create and print the declaration both from the initial screen of the Cockpit for Periodic Declarations and from the SAP
standard menu.

To create the declaration from the SAP standard menu, choose Logistics Materials Management (or Sales and
Distribution) Foreign Trade/Customs PeriodicDeclarations PeriodicDeclarations Operational Create
periodicdeclarations EuropeanUnion INTRASTAT Additionaldeclarations Mineral oil declaration Germany .

From the initial screen of the Cockpit for Periodic Declarations ,

Choose Mineral oil declaration Germany .

Enter the selection criteria and execute the task.

The system displays a list of mineral oil products for the declaration.

In addition to performing sorting and other mathematical functions, you can print the declaration from the data display screen.

EXTRASTAT Declarations

De nition
Monthly declaration that provides EU authorities with statistics on trade between EU member states and non-EU countries (for
example, trade between Germany and the US).

There is an EXTRASTAT declaration for exports and one for imports. The system selects data from billing documents and
purchasing documents and writes the data to the declaration’s intermediate database, VEXAV (system table).

Use
R/3 supports EXTRASTAT declarations on diskette and magnetic tape only.

Issuing INTRASTAT/EXTRASTAT Declarations

Prerequisites
Before issuing an INTRASTAT or EXTRASTAT declaration:

If you plan to submit the declaration on diskette, create a goods catalog if required by your country’s authorities

This is custom documentation. For more information, please visit the SAP Help Portal 50
2/10/2023
Select data for the declaration

For more information, see Goods Catalog and Data Selection for Declarations .

Procedure
You can create INTRASTAT declarations from the Cockpit for Periodic Declarations .

1. From the Cockpit for Periodic Declarations , choose Create Periodic Declarations.

2. Select the appropriate country under the corresponding declaration type.

3. Choose File or Form as necessary and execute Step 2 .

4. Enter the parameters for the declaration and choose Program Execute.

See also:

For information on transferring the declaration to diskette, see Creating Declarations on Paper, Diskette or Tape .

KOBRA Declaration
De nition

A monthly declaration to the German authorities that records the export of sensitive goods (for example, weapons and goods
that can be used to manufacture weapons).

The system selects data from the relevant billing documents and writes it to the declaration’s intermediate databases, VEKAA,
VEKAB, and VEKAC.

The SAP System supports KOBRA declarations on diskette and magnetic tape only.

Issuing KOBRA Declarations


The procedure for issuing KOBRA declarations is the same as for issuing INTRASTAT and EXTRASTAT declarations . For this
procedure, you do not need to create a goods catalog.

See also:

Data Selection for Declarations

Creating Declarations on Paper, Diskette or Tape

EFTA Declarations
Use

European Free Trade Association (EFTA) declarations involve declarations to Swiss authorities.

The SAP System supports the simpli ed export regulation [Vereinfachte Ausfuhrregelung (VAR)] for Switzerland. You can
create the VAR on paper, as a le on your hard disk or on a diskette.

This is custom documentation. For more information, please visit the SAP Help Portal 51
2/10/2023

VAR Declaration
De nition

A monthly declaration to the Swiss authorities that provides statistics on exports from Switzerland.

The system selects data from billing documents relevant to the simpli ed export regulation [Vereinfachte Ausfuhrregelung
(VAR)] and creates the intermediate database VEXAV for the declaration.

Issuing VAR Declarations

Prerequisites
Select data from billing documents for the reporting period. See Data Selection for Declarations .

If you want to issue the declaration on diskette, create a le from the selected billing documents. See Creating
Declarations on Paper, Diskette or Tape .

Procedure
You can create VAR declarations from the Cockpit for Periodic Declarations .

1. From the Cockpit for Periodic Declarations , choose Create Periodic Declarations.

2. Select Switzerland from the menu on the left.

3. Depending on whether you want to issue the declaration on paper or as a le, execute Step 2 for Form or File .

4. Enter the parameters for the declaration.

5. Choose Program Execute .

NAFTA Declarations

Use
This function creates the following export/dispatch declarations to NAFTA member-state authorities.

Declaration Supported for paper or diskette? Comments

Shipper’s Export Declaration (SED) Paper only Applies only to the US

Automated Export Report Procedure (AERP) Disk only Applies only to the US

Harbor Maintenance Fee (HMF) Paper only Applies only to the US

Prerequisites
Before issuing a NAFTA declaration, select the relevant billing documents for the declaration. The system selects data from the
billing documents and writes the data to the intermediate database VESED. This database forms the basis for the NAFTA
declarations.

This is custom documentation. For more information, please visit the SAP Help Portal 52
2/10/2023
The system includes separate data selection procedures for exporters and forwarding agents. The separate procedures
continue to be the case even though a standard data layout record (AERP) was set up on by the US Bureau of the Census on
January 1, 1995.

Features
When creating a declaration, you can specify the following criteria for selecting billing documents:

Relevance of exports for declaration

Processing criteria

Technical speci cations

Relevance of Exports for Declaration

You can indicate whether the system selects exports that you must declare or exports that you do not have to declare.

If the export meets any of the following criteria, it requires declaration:

The value of the export item is greater than USD 2500

An export license that requires declaration is assigned to the license

In this case, the system does not consider the ship-to country or the export’s value.

The export is an in-transit export leaving the US by ship

If the export meets any of the following criteria, it does not require declaration:

The value of the export item is less than USD 2500

The export’s ship-to country is Canada

The item is being dispatched by post and has a value less than USD 500

The export is an in-transit export leaving the US by a mode other than ship

Processing Criteria

You can choose to have items with the same commodity code summarized (compressed) within a billing document.
Summarizing items helps reduce the volume of data in the declaration. The system summarizes data for NAFTA declarations
using xed rules in the coding.

When summarizing items for a declaration, the system aggregates the items’ data. This data includes:

Statistical value

Net mass

Special mass unit

Gross weight

Technical Speci cations

You can specify whether the system issues the output in list or le form.

This is custom documentation. For more information, please visit the SAP Help Portal 53
2/10/2023

Activities
You can create NAFTA's SED and AERP declarations from the Cockpit for Periodic Declarations . The procedure is basically the
same as for creating EU declarations (see Issuing INTRASTAT/EXTRASTAT Declarations ).

SED Declaration
De nition

A monthly declaration that reports all exports from the US to Mexico or to countries that are not members of NAFTA. File
Shipper’s Export Declarations (SEDs) with the United States Department of Commerce on the tenth day of the following
month.

The system selects data from the intermediate database VESED to create the SED. US authorities accept the SED on paper
only but no special form is required.

For an alternative export reporting system, see US Customs: Automated Export System (EDI) and AERP Declaration .

Issuing SED Declarations


1. From the SAP main menu screen, choose Logistics Sales and Distribution Foreign -Trade/Customs Periodic
declarations Periodic declarations Operational Create periodic declarations NAFTA AERP Create
document USA – Shippers Declaration in list form .

2. Enter the parameters for the declaration including the reporting month and year.

3. Choose Program Execute .

4. The SED appears.

5. Print the declaration by choosing List Print .

AERP Declaration

De nition
A monthly declaration reporting exports from the US to the Bureau of the Census.

Use
The Bureau of the Census, responsible for collecting US export statistics, introduced the Automated Export Reporting Program
(AERP) to the US in 1970. This program permitted exporters and forwarding agents to declare their export transactions each
month directly to the Bureau of the Census by using electronic media. Consequently, creating a paper Shipper’s Export
Declaration (SED) was no longer necessary. The Bureau of the Census combines data received electronically and on paper to
produce official US foreign trade statistics.

The advantages of issuing the AERP declaration instead of the paper SED included reduced costs, reduced administration, and
faster generation of trade statistics. Until December 31, 1999, you could transfer the AERP declaration to the Bureau of the
Census in three ways:

Direct computer transmission

This is custom documentation. For more information, please visit the SAP Help Portal 54
2/10/2023
Magnetic tape

Diskette

The system selects data from the intermediate database VESED, creates the information relevant to the declaration, and
writes the information in a special le. This le forms the basis for creating a magnetic tape or diskette for the AERP.

 Note

AERP has been replaced by the Automated Export System (AES). At midnight on December 31, 1999, the Automated Export
Reporting Program was turned off. AERP lers who did not migrate to AES by January 1, 2000, had to revert to ling paper
Shipper's Export Declarations (SEDs) on that date.

See also

US Customs: Automated Export System (AES) .

HMF Declaration

De nition
A quarterly declaration to the US authorities that reports the value of goods loaded and unloaded in US harbors.

Use
Maintaining and extending ports and harbors in the US was originally nanced by taxes. To ease the burden on US taxpayers,
the federal government issued the Water Resources Development Act in 1986 to levy the greater part of the necessary funds
directly from those who use the port to import and export goods.

Created by the Water Resources Development Act, the Harbor Maintenance Trust Fund raises 40% of the nances necessary to
maintaining US harbors. Most contributions to the fund come from the Harbor Maintenance Fee (HMF), levied each time a ship
is loaded or unloaded in a US harbor. This fee also applies to the transport of passengers. Importers and exporters pay the
Department of Treasury a fee of 0.125% of the value of the transported goods.

The basis of the HMF declaration is the data the system collects when creating a regular SED (Shipper’s Export Declaration).
The system evaluates all dispatches leaving the US from a US port by ship and then totals the value of the goods. The fee is a
percentage of this sum.

Issuing HMF Declarations


1. From the main SAP menu, choose Logistics Sales and Distribution Foreign Trade/Customs Periodic d
eclarations Periodic declarations Operational Create periodic declarations NAFTA HMF USA .

2. Enter the parameters for the declaration including the reporting quarter and year.

3. Choose Program Execute .

The system calculates the harbor maintenance fee for the selected transactions.

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 55
2/10/2023
Currently, the system calculates the harbor maintenance fee for exports only.

Japanese Declarations

Use
This function creates the following declarations for the Japanese authorities.

Declaration Supported for paper or diskette?

MITI Export Report Paper only

Customs Declaration for Import Paper only

Features
As the graphic below shows, you can print MITI Export Reports in either of the following ways:

Using output control for billing documents to print the report with reference to a single billing document

Printing multiple export reports for billing documents meeting the selection criteria

This is custom documentation. For more information, please visit the SAP Help Portal 56
2/10/2023

MITI Export Report

De nition
A declaration for reporting exports with a value greater than 5 million yen to the Japanese Ministry of Trade and Industry (MITI).

Use
The Japanese government uses this declaration for currency control and statistical purposes.

You must print the each MITI Export Report on a special form ( Yushutsu Houkokusho ) provided by the authorities. Print three
copies and give them to the Japanese customs authorities after the customs inspection is completed. The customs authorities
keep the original and one of the duplicates. They check and stamp the second duplicate and return it to the exporter. They
forward the original to MITI and the duplicate to the Ministry of Finance.

Structure
The MITI Export Report contains the following data:

Name and address of the shipper

Ship-to party

Commodity code

Freight category number

Official bank con rmation on foreign currency

Items and quantity

FOB value and total invoice amount

Currency

Means of payment

Date of payment

Number of the valid export license issued by MITI (if applicable)

Issuing Multiple MITI Reports


1. From the SAP main menu, choose Logistics Sales and Distribution Foreign Trade/Customs Periodic
declarations Periodic declarations Operational Create periodic declarations Asia Japan MITI – Export .

2. Enter the parameters for the declaration.

3. Choose Program Execute .

4. A list of billing documents meeting the selection criteria appears.

5. In the list, select the billing documents for which you want to create MITI Export Reports.

6. Choose Execute .

This is custom documentation. For more information, please visit the SAP Help Portal 57
2/10/2023

Customs Declaration for Import (Japan)

De nition
A declaration to the Japanese customs authorities that provides information on goods imported into Japan. This declaration
must be created for each vendor import invoice.

Use
You must print the declaration on the customs declaration form ( Yunyukamotsu no shiharai ni kansuru hokokusho , form
number T2010) provided by the authorities.

Structure
The Customs Declaration for Import contains

The date and address of the importer

Data on the quantity and value of the imported goods

The customs tariff number for the goods

Type of payment

Payment deadline

Issuing Customs Declarations for Import (Japan)


1. From the SAP standard menu, choose Logistics Sales and Distribution Foreign Trade/Customs Periodic
declarations Periodic declarations Operational Create periodic declarations Asia Japan Customs decl.-
Import .

2. Enter the parameters for the declaration.

3. Choose Program Execute .

4. The system creates a list of purchase orders and invoice receipts. From this list you can print customs declarations.

5. To print a customs declaration, select the document in the list and choose Create customs declaration .

Progress Tracking (PS-PRG-TRC)

Purpose
Progress Tracking enables you to closely monitor the progress of WBS elements, network activities and network components in
the Project System and purchase orders in Materials Management, by tracking events that you have de ned in Customizing for
Progress Tracking or in the Progress Tracking function itself.

Integration
Progress Tracking is a new function that contains all the features of the Monitoring Dates function related to Materials
Management in the Project System. Progress Tracking, however, is enhanced by a more exible Customizing for creating default

This is custom documentation. For more information, please visit the SAP Help Portal 58
2/10/2023
settings, as well as additional functions, such as status information, mass change, copying, ltering, and printing features, and
overall analysis. The use of new technology enables you to create user and application-speci c layouts and provides a more
user-friendly interface.

Features
Progress Tracking Objects

You can use Progress Tracking for the following objects:

Network components

Purchase orders

Work breakdown structure elements

Network activities

The object that you monitor in Progress Tracking is referred to as the Progress Tracking object.

Selection Screens and Main Screen

Before you reach the main Progress Tracking screen, there is a two-stage selection process, which enables you to select those
Progress Tracking object whose progress you wish to monitor. On the initial selection screen, you have the option of using
customer-speci c data elds to limit your selection.

The main Progress Tracking screen has a clearly arranged and intuitive interface, which is independent of the current object
that you are tracking. As it is made up of two SAP List Viewer (ALV) overviews, you can de ne and maintain user or application-
speci c layouts.

For more information, see Selection of Progress Tracking Objects .

Events

To monitor the progress of a Progress Tracking object, you de ne Progress Tracking events in Customizing for Progress Tracking
or in the Progress Tracking function itself. You can de ne whichever events you require, for example, milestones in the
production or purchasing process, such as a goods receipt, or an internal event such as the creation of a purchase order.

For the events, you can:

Enter up to four date types

Stipulate dates for events using enhancements for either system dates or external data

Schedule dates for events, and analyze variances

Evaluation

The main Progress Tracking screen allows you to look at the events of one Progress Tracking object at a time. The evaluation
function provides you with an overview of all data for the Progress Tracking objects that you have selected. For more
information, see Evaluation of Progress Tracking Data .

Business Add-Ins (BADIs)

Progress Tracking provides numerous enhancements (Business Add-Ins) that you can con gure individually for the functions
offered.

For more information, see Business Add-Ins (BAdIs) for Progress Tracking .

This is custom documentation. For more information, please visit the SAP Help Portal 59
2/10/2023

Selection of Progress Tracking Objects

Use
Before you can use Progress Tracking, you need to select those WBS elements, network activities, network components or
purchase orders whose progress you wish to track.

Prerequisites
To use Progress Tracking you must create at least one Progress Tracking pro le in Customizing. Customizing for the Project
System:

Progress Progress Tracking:

⇒ De ne Progress Tracking Pro le (for network components)

Settings for Work Breakdown Structures De ne Progress Tracking Pro le for Work Breakdown Structures (for Work
Breakdown Structures)

Settings for Networks De ne Progress Tracking Pro le for Networks (for Networks)

Customizing forMaterials Management, by choosingPurchasing Purchase Order Progress Tracking De ne Progress


Tracking Pro le . (for purchase orders)

Features
There are two steps to selecting the objects whose progress you wish to track.

Selection Screen

The initial selection screen is divided into four sections:

First you must enter a pro le. You must de ne at least one pro le in Customizing for Progress Tracking , which you can
then select from the drop-down menu in the Pro le eld.

Then you can enter application-speci c selection criteria in the Project Selection and Further Selection Parameters
sections. For example, if you are selecting network components, you can enter the network to which the component
belongs or the requirements date for the material. If you are selecting purchase orders, you can enter the purchasing
group or the manufacturer, for example.

You can also limit the selection according to Progress Tracking data itself, for example, scenario or event, under Progress
Tracking Parameters .

Finally, you have the option of using customer-speci c data elds to limit your selection, by choosing Customer Fields
.

 Note
The customer-speci c elds are usually set up by the system administrator. For more information about customer
includes, see Business Add-Ins (BAdIs) for Progress Tracking .

Progress Tracking Object Selection

In this second stage of the selection process you see an overview of all the objects that ful ll the selection criteria you entered
in the rst stage described above.

This is custom documentation. For more information, please visit the SAP Help Portal 60
2/10/2023
The selection screen is in the form of a SAP List Viewer (ALV) overview containing the objects and related information. In this
overview you can:

Sort and lter the information in any way you like

De ne and maintain user or application-speci c layouts

Select as many entries as you like, which you can process together in Progress Tracking

 Note
When you return to this overview from the main Progress Tracking screen, the objects that you originally selected are
still highlighted. This means that you can clearly see what you have already processed, which allows you to select the
next block of unprocessed entries, if required.

Activities
Selection Screen

To access the initial selection screen for Progress Tracking, choose:

LogisticsorAccounting Project System Progress Progress Tracking Progress Tracking (for network component)

LogisticsorAccounting Project System Progress Progress Tracking Progress Tracking for Work Breakdown
Structures (for work breakdown structures)

LogisticsorAccounting Project System Progress Progress Tracking Progress Tracking for Networks (for networks)

Materials Management Purchasing Purchase Orders Follow-On Functions Progress Tracking. ( for purchase orders)

Enter your selection criteria on this screen and choose Execute .

Layout Variant

You can adapt this screen to your own requirements by creating a layout variant. Choose Goto Variants Save as Variant
to branch to the Save as Variant screen.For more information about creating and saving variants, choose Information About
Variant Attributes on the Save as Variant screen.

Progress Tracking Object Selection

To start Progress Tracking, select the object(s) you wish to process in Progress Tracking and choose Change , or if you want
to display them only, choose Display .

Hotspots

If the data in a eld in the overview is underlined, this means that it has a “hotspot”. You can branch to the transaction for
displaying the relevant object by clicking the underlined data once.

Layout Variant

To nd out how to create a layout variant for the ALV overview, choose to branch to the SAP List Viewer (ALV) Grid Control
documentation in the SAP Library. Choose SAP List Viewer (ALV) Grid Control Layouts.

The Main Progress Tracking Screen


This is custom documentation. For more information, please visit the SAP Help Portal 61
2/10/2023

Use
After you have selected the objects that you wish to process in Progress Tracking, you reach the main Progress Tracking screen.
This is the central tool for Progress Tracking where you execute various functions or branch to other transactions.

Prerequisites
You have selected the objects whose progress you wish to track and chosen Change or Display , as described in Selection
of Progress Tracking Objects .

Features
The main Progress Tracking screen is divided into two sections:

Progress Tracking Object Overview : This is located in the top half of the screen and contains the Progress Tracking
objects that you selected, with an overview of relevant information for each object. When Progress Tracking is rst
started, the rst entry in this section is selected as the current entry and is highlighted accordingly.

Events Overview : This is located in the bottom half of the screen and displays the events for the Progress Tracking object
that is the current entry in theProgress Tracking Object Overview .

Data describing the current entry is displayed between the two overviews. You can use the scroll keys to the left of this data to
go to the next or previous entry in the Progress Tracking Object Overview . When you scroll through, the corresponding entry is
then automatically highlighted in the Progress Tracking Object Overview and its events can be seen in the Events Overview .

For both of these sections you can create a user or application-speci c design. To nd out how to do this, choose End User
Docu to branch to the documentation for the SAP List Viewer in the SAP Library. Choose SAP List Viewer (ALV) Grid Control
Layouts .

Progress Tracking Object Overview

Use
The Progress Tracking Object Overview mainly contains data that describes the components, network activities, work
breakdown structure elements or schedule lines (the Progress Tracking objects). The only eld in which you can enter data is for
the event scenario.

Features
Information Icons

Particular information about the Progress Tracking object is also displayed within the overview in the form of the following icons,
for example, in the event eld, depending on the processing status of the relevant object:

Icon Description Other info

Initial Event Overview Events have been assigned during the


process of the current transaction but have
not yet been scheduled or manually
processed.

This icon is displayed in the event column (


Evnt ).

This is custom documentation. For more information, please visit the SAP Help Portal 62
2/10/2023

Icon Description Other info

Event Overview Displayed as the alternative to the Initial Also displayed in the toolbar, for navigating
Event Overview icon above. to the displayed assignment.

Events are assigned to the Progress


Tracking object and have already been
saved once, or at least scheduled or
manually processed.

This icon is displayed in the event column (


Evnt ).

Subitems Subitems exist for the Progress Tracking Also displayed in the toolbar, for navigating
object. to the displayed assignment.

This icon is displayed in the subitem See Maintaining Subitems


column ( SItm ).

Status Note Status information exists for the Progress


Tracking object

Documents Document assignments exist for the Also displayed in the toolbar, for navigating
Progress Tracking object from the to the displayed assignment.
corresponding standard transactions.

Function Icons

The following icons are also displayed in the toolbar:

Icon Description Other info

Object Filter Filter the overview according to Progress


Tracking attributes

Reset Reset the Object Filter

Date Mass Change Mass change of dates of individual events


for the selected Progress Tracking objects

Scenario Mass Change Mass change of the event scenario


assignment

Complete View Call up the Evaluation function for the See Evaluation of Progress Tracking Data
selected Progress Tracking objects

Send Message to Requester Inform someone via mail with an executable


work item for displaying the Progress
Tracking for the selected Progress Tracking
object

E-Mail Send an e-mail

Activities
Assigning an Event Scenario

The event scenario eld is the only eld in the Progress Tracking Object Overview into which you can enter data. There are
three different ways of assigning a scenario:

Manual assignment

This is custom documentation. For more information, please visit the SAP Help Portal 63
2/10/2023
Assignment by a material group

Assignment by a customer enhancement

For more information, see Assigning an Event Scenario .

Filtering According to Progress Tracking Data

Using the Object Filter , you can lter the overview of Progress Tracking objects according to the Progress Tracking data. You
can:

Limit the lter criteria to exactly one event or include all events

Filter according to all variances or select a particular variance

Filter by event priorities

Filter by particular dates or intervals of one or more event scheduling types

Mass Change to Dates of an Event

When you choose Date Mass Change you can change one or more dates of an event for the selected Progress Tracking
object. You can also carry out mass initialization, which means that the dates in question are set to zero and thereby deleted.

 Note
Fixed dates are excluded from the mass change function.

Mass Change Scenario

The mass change scenario function enables you to set new event scenario assignments and overwrite existing assignments for
one or more Progress Tracking objects. You select the Progress Tracking objects, choose Scenario Mass Change and select
the scenario you require. This scenario is then assigned to all the selected Progress Tracking objects. If you overwrite an existing
scenario those events that are not assigned to the new scenario are automatically deleted. Manually assigned events are also
deleted.

Hotspots

If an individual data eld is underlined, this means that a hotspot has been de ned for this eld. To branch to the display of the
master data for the relevant eld, click the underlined data once.

Assigning an Event Scenario

Use
You create event scenarios and the standard events that they contain in Customizing for Project System , by choosing:

Progress Progress Tracking:

⇒ De ne Standard Events / De ne Event Scenario (for network components )

Settings for Work Breakdown Structures De ne Standard Events for Work Breakdown Structures / De ne Event
Scenario for Work Breakdown Structures (for work breakdown structures)

Settings for Networks De ne Standard Events for Networks / De ne Event Scenario for Networks (for networks)

This is custom documentation. For more information, please visit the SAP Help Portal 64
2/10/2023
Customizing for Materials Management, by choosing

Purchasing Purchase Order Progress Tracking De ne Standard Events / De ne Event Scenario .(for purchase
orders)

The event scenario allows you to collect together those events that you use over and over again, and assign them to your
Progress Tracking objects all at once, rather than having to create each event individually.

Among other things, you can:

Designate an event in a scenario as the start event for automatic scheduling

Enter a time interval in days for each pair of events, which is taken into account during the scheduling of event scenarios.
You can also set a reference indicator for the time interval, which prevents it from being changed in Progress Tracking.

De ne whether the event relationship is taken into account during forwards and/or backwards scheduling

You assign the event scenario to your Progress Tracking objects manually in the Progress Tracking Object Overview , or you can
create a default assignment in Customizing via the material group or using a customer enhancement.

When you assign a scenario, the standard events de ned for the scenario in Customizing for Progress Tracking are
automatically assigned to the Progress Tracking object. If you overwrite an existing scenario manually or by using mass change,
then those events that were already assigned to the Progress Tracking object and are not part of the new scenario are
automatically deleted. This applies both to standard events and manually assigned events.

Procedure
Manual Assignment

To assign an event scenario manually:

1. Select the Scenario eld of the Progress Tracking object in question

2. Choose one of the scenarios from the list of scenarios that you have created in Customizing for Progress Tracking

The events for the Progress Tracking object can now be seen in the Events Overview in the bottom half of the screen.

Assignment by a Material Group

You can create a default scenario for a material group in Customizing for Progress Tracking under Assign Default Scenario to
Material Group . This scenario is automatically used for the material group but can be overwritten manually, as described above,
or by a customer enhancement.

Assignment by a Customer Enhancement

You can also de ne which pro le and events are assigned to a Progress Tracking object by way of a customer enhancement. For
more information, refer to Business Add-Ins (BAdIs) for Progress Tracking .

Result
When you rst assign a scenario to a Progress Tracking object, the corresponding entry in the upper list is agged with Initial
Event Overview . This shows clearly that events have been assigned to an entry during the process of the current transaction
run, and that these events have neither been scheduled nor manually processed. By ltering the list of Progress Tracking
objects by this icon, you can easily select all entries whose newly assigned events have not yet been processed.

This is custom documentation. For more information, please visit the SAP Help Portal 65
2/10/2023
As soon as you have scheduled or manually processed the events for a Progress Tracking object and updated the screen by
choosing Refresh or carrying out another transaction, the icon changes to Event Overview .

You can call up and maintain the offsets in the event scenario from the Events Overview by choosing Event Scenario . For
more information, see Events Overview .

Maintaining Subitems

Use
You can create subitems for each Progress Tracking object and de ne and monitor as many events as you like for each subitem.

Procedure
Branching to the Subitem Overview

To branch to the overview of subitems select the Progress Tracking object in the Progress Tracking Object Overview and choose
Subitems .

If a Progress Tracking object already has subitems, the above icon is entered in the SItm column and you can also choose the
icon in the column to branch to the overview of subitems.

Creating a Subitem

The subitems screen looks similar to the main Progress Tracking screen. The top half contains the subitems and the bottom
half, the events for the current subitem.

1. To create a subitem choose Append Row.

2. Enter an ID for the subitem in the subitem eld. The other eld ( Event Maintained ) is lled by the system automatically
as soon as you assign events to the subitem.

Creating Events for Subitems

You can de ne and track as many events as you like for each subitem.

To transfer the events of the superior Progress Tracking object to the subitem, choose Transfer Event

To create an event manually, choose Append Row

To assign a standard event to a subitem, select the subitem in the subitem overview and then choose Standard Event

When you rst create an event or transfer events from the superior Progress Tracking object, Ini al Event Overview appears
in the Event Maintained eld in the upper half of the screen. As soon as you manually edit or schedule these events, Event
Overview appears in the Event Maintained eld.

Returning to the Main Screen

Choose Main Items in the subitems overview toolbar to return to the main screen, or Back .

Customer-Speci c Subitem Data

Customer-speci c subitem data can be de ned individually by customers by using the customer includes CI_SUBOBJ_CP from
table TCP_SUBOBJ for network components, or CI_SUBOBJ_PO from table TPO_SUBOBJ for schedule lines.

This is custom documentation. For more information, please visit the SAP Help Portal 66
2/10/2023
Using a further Progress Tracking BAdI, the individual elds in the ALV Grid eld catalog can be in uenced and controlled.
Another BAdI is available that allows you to create and update subitems when Progress Tracking is called up for the rst time.

For more information about BAdIs, see Business Add-Ins (BAdIs) for Progress Tracking .

Events Overview

Use
In the Events Overview section of the main Progress Tracking screen, you can see the events that have been entered for the
Progress Tracking object currently highlighted in the Progress Tracking Object Overview .

Features
In addition to the standard icons, the Events Overview toolbar contains the following icons:

Icon Description

Standard Event Assign standard events. See Assigning Events in the Events
Overview

Event Scenario Call and maintain the event scenario

Schedule Call up scheduling

Copy Dates Copy the dates of events assigned to one Progress Tracking object
to the events of other Progress Tracking objects. See Copying
Event Dates

Refresh Update the overview

Full Scr./Half Scr. Switch the full screen on or off

Activities
Sorting the Events

If you have not set up your own sorting criteria, the events are arranged according to their sorting rank. You de ne the sorting
rank for a standard event when you create it in Customizing for Progress Tracking . However, you can overwrite this individually
on the events overview, both for standard events and events you have entered manually.

Calling Up and Maintaining the Event Scenario

Choose Event Scenario to display the scenario, including the corresponding event relationships, that is assigned to the
Progress Object in question, if one has been assigned. The time intervals can be changed here individually for the current
transaction run, as long as the reference indicator has not been set for the time interval in Customizing for Progress Tracking
under De ne Event Scenario / De ne Event Scenario for Work Breakdown Structures / De ne Event Scenario for Networks .

Calling Up Scheduling

To call up scheduling you must select one event only, which is used as the start event for scheduling and then choose
Schedule . Only the standard events of an assigned event scenario can be scheduled. The settings in the Progress Tracking
pro le de ned in Customizing for Progress Tracking determine the way in which scheduling is carried out and also the
scheduling types that are to be scheduled. A Progress Tracking BAdI can be used to de ne customer-speci c time intervals for

This is custom documentation. For more information, please visit the SAP Help Portal 67
2/10/2023
the event relationships per scheduled entry. For more information about BAdIs, see Business Add-Ins (BAdIs) for Progress
Tracking .

Automatic Scheduling

When you call up Progress Tracking, the system checks for each scenario whether an event has been set as the start event for
automatic scheduling in Customizing for Progress Tracking under Maintain Relationships Between Events in a Scenario . If this
is the case, the events are always scheduled according to the settings in the pro le, so that the dates of the corresponding
events are always current in terms of scheduling.

Date Types

The date types for standard events that are referenced only, as de ned in Customizing for Progress Tracking under De ne
Event Scenario / De ne Event Scenario for Work Breakdown Structures / De ne Event Scenario for Networks , cannot be
maintained on the events overview.

The individual date types are underlined in red or yellow, according to the Progress Tracking pro le settings for variances. The
maximum variance of the date types for an event is displayed as a traffic light for each event.

Updating the Event Overview

In the SAP List Viewer grid, entries can be checked together using a function or individually and are then transferred to the
corresponding work areas. So that more than one eld in the Events Overview can be maintained quickly using tabulator
navigation, the entries in the events overview are not transferred to the relevant work areas immediately. Not until a function is
called up or you navigate somewhere else, does the system transfer the data and update any dependent data. If you want to
update the data manually at any particular time, you can choose Refresh .

Assigning Events in the Events Overview

Use
A standard event is an event that you create in Customizing for Progress Tracking . There are two ways of assigning a standard
event to a Progress Tracking object:

Manually in the Events Overview .

By assigning an events scenario to the Progress Tracking object in the Progress Tracking Object Overview . For more
information, see Assigning an Event Scenario .

In addition to the standard events that have been created in Customizing , you can also create events directly in the Events
Overview . These events however, cannot be part of the assigned event scenario.

Procedure
Assigning Events

Assigning Standard Events Manually

1. To assign a standard event, select the Progress Tracking object in the Progress Tracking Object Overview.

2. Choose Standard Event in the Events Overview toolbar.

3. Choose one of the standard events from the list.

This is custom documentation. For more information, please visit the SAP Help Portal 68
2/10/2023
Assigning Non-Standard Events

1. To enter a non-standard event manually, choose Append Row.

2. Enter the required data (description, dates and so on).

Result
The events you create are displayed in the Events Overview .

Copying Event Dates

Use
You can copy dates from events assigned to a particular Progress Tracking object and transfer these dates to the events of
different Progress Tracking objects.

Procedure
Copying All the Dates of All Events

1. Select the Progress Tracking object in the Progress Tracking Object Overview whose dates you want to copy (the source
object).

2. Select all the events in the Events Overview by choosing Select All .

3. In the Progress Tracking Object Overview , select the Progress Tracking objects whose event dates you wish to change
(the target object).

4. Choose Copy Dates .

5. Con rm by choosing Yes in the dialog box that appears.

Copying the Dates of Individual Events

If you do not wish to copy all the dates of all events but want to copy the dates of, for example, two or three events, or just one
event, then you must use the following method, whereby you locate the exact date by selecting the column and row, like
coordinates.

1. Select the Progress Tracking object in the Progress Tracking Object Overview whose dates you want to copy (the source
object)

2. Select the event whose date you wish to copy in the Events Overview , for example, speci cation.

3. Press the control key (CTRL) and select the column or columns of the date(s) you wish to copy, for example, the forecast
date alone, or the forecast, baseline and plan dates.

4. In the Progress Tracking Object Overview , select the Progress Tracking object whose event date(s) you wish to change
(the target object).

5. Choose Copy Dates .

6. Con rm by choosing Yes in the dialog box that appears.

This is custom documentation. For more information, please visit the SAP Help Portal 69
2/10/2023

Evaluation of Progress Tracking Data

Use
The main Progress Tracking screen allows you to look at the Progress Tracking objects and their events one at a time. For a
broader overview that shows you all the data for each Progress Tracking object in one screen, you use the complete view for
Progress Tracking, or the Evaluation screen. This provides you with an overview of your Progress Tracking data and enables you
to compare and analyze it in more depth.

Features
Evaluation Screen

The evaluation screen is split into two parts. The selected Progress Tracking objects and their substructures are displayed in the
left tree structure. The components/schedule lines with their events and their subitems, plus the events of the subitems, are
displayed in the right tree structure.

In the right tree structure:

For each event, the dates are underlined in red or yellow in the case of variances, according to the settings in the Progress
Tracking pro le

Each event is assigned an icon whose color represents the worst variance (green circle, yellow triangle, red square).

The events are agged in the right tree structure with:

Each subitem or component/schedule line is assigned an icon whose color represents the current worst variance of the
assigned events (green circle, yellow triangle, red square). The subitems are agged with: .

Rule for Displaying Aggregated Variance

To provide the most informative representation possible, the following rule is used for displaying the aggregated variance per
component/schedule line and subitem:

The variance of an event is only taken into account, if there is no logical event following it, in terms of rank in the sorting of the
events, for which an actual date is maintained and whose variance is evaluated as being weaker than the variance of the current
event.

By using this rule, the degree of variance for an event can be made relative or be completely resolved by the completion of a
succeeding event or adjustment to its execution time.

In the left tree structure, the aggregated variances of the component/schedule line are identi ed per subordinate object as a
colored icon (green circle, yellow triangle, red square).

Activities
You can call up the Evaluation function:

By selecting one or more Progress Tracking objects in the Progress Tracking Object Overview on the main Progress Tracking
screen and then choosing Complete View .

This is custom documentation. For more information, please visit the SAP Help Portal 70
2/10/2023

This menu path is only available for network components and schedule lines.

By choosing Logistics → Project System → Information System → Progress → Progress Tracking Evaluations (transaction
ACOMPXPD) or Logistics → Materials Management → Purchasing → Purchase Order → Reporting → Progress Tracking
Evaluations (transaction AXPD)

When you call up the Evaluation function as a separate transaction, the Progress Tracking initial selection screen appears,
where you can select those network components or purchase orders that you are interested in.

From this screen, you can also choose User-De ned Evaluation to call up your own report. You can enter your own
evaluation report in Customizing for Progress Tracking under Customer-Speci c Evaluation This feature gives you the option
of integrating a report that re ects your own particular requirements, for example, you may want to include particular data or
have a different layout.

Navigation

By double-clicking a node in the left tree structure, the related subtree is expanded and brought into focus. All other
substructures in the right tree structure are collapsed accordingly.

You can switch the complete screen on or off by choosing Full Screen On/Off , above the left tree structure.

Filtering

Using the toolbar in the right tree structure, you can lter according to objects with a particular color of variance by choosing:

Display (Show Red Events)

Display (Show Yellow Events )

Close All (Display Objects Only)

You can also create a more detailed lter for the evaluation screen, in which you lter according to events, variances, priorities
and intervals, by choosing Filter View .

Statistics

By choosing Statistics , located above the left tree structure, you can call up statistics for objects in the evaluation. In
addition to the total number of objects, the quantities and percentage of open or overdue objects are also displayed:

Open means that there are still events without actual dates

Overdue means that there are still events without actual dates whose planned and baseline date have already been exceeded
by today’s date

Printing

Unlike the main Progress Tracking screen, where you can only print the individual ALV overviews, here you can print out the
complete view by choosing Print view .

You have the choice of printing out the current view or the entire hierarchy, with a print preview option for both of these.
This is custom documentation. For more information, please visit the SAP Help Portal 71
2/10/2023

Business Add-Ins (BAdIs) for Progress Tracking


For the customer enhancements for Progress Tracking the following methods are de ned for the BADI de nition EXPD_UPDATE:

Method Description Parameter for the Method Description

SET_OBJ_TYPE Set an individual Progress I_OBJ_TYPE Object type of a Progress


Tracking object when calling up Tracking object
Progress Tracking

GET_DEFAULT_SCENARIO Assign a default scenario when I_OBJECT_DATA Data of a Progress Tracking


you call up Progress Tracking object
I_OBJ
for objects to which neither a
Object type of a Progress
scenario nor an event is E_SCHDSC
Tracking object
assigned
Default scenario

GET_NEWS_EVENTS Generate own events for I_OBJECT_DATA Data of a Progress Tracking


Progress Tracking when you call object
I_OBJ
up Progress Tracking
Object type of a Progress
T_EVENTS
Tracking object

Table of customer-speci c
events

UPDATE_SUB_ITEMS Generate, delete and update I_OBJECT_DATA Data of a Progress Tracking


subitems when calling up object
I_OBJ
Progress Tracking
Object type of a Progress
T_SUB_ITEM
Tracking object

Table of subitems

This is custom documentation. For more information, please visit the SAP Help Portal 72
2/10/2023

Method Description Parameter for the Method Description

GET_REFERENCE_DATE Determine reference dates for I_OBJECT_DATA Data of a Progress Tracking


events when calling up Progress object
I_NMRID
Tracking
Subitem key
I_EVENT
Event
I_BASELINE
Indicator of the reference of the
I_CURRENT baseline date

I_FORECAST
Indicator of the reference of the
I_ACTUAL plan date

I_XBASELINE Indicator of the reference of the


forecast date
I_XCURRENT
Indicator of the reference of the
I_XFORECAST actual date

I_XACTUAL Baseline date

I_EXP_PRIO Plan date

E_XBASELINE Forecast date

E_XCURRENT Actual date

E_XFORECAST Priority

E_XACTUAL Baseline date

E_EXP_PRIO Plan date

E_PRIO_SET Forecast date

Actual date

Priority

Indicator priority is set

UPDATE_FIELDCAT_MAINITEM In uence the ALV grid eld I_OBJECT_DATA Data of a Progress Tracking
catalog for events of Progress object
T_FIELDCATALOG
Tracking objects
Field catalog

UPDATE_FIELDCAT_SUBITEM In uence the ALV grid eld I_OBJECT_DATA Data of a Progress Tracking
catalog for subitems object
T_FIELDCATALOG
Field catalog

UPDATE_OFFSET Update the time intervals for I_BACKWARD Indicator for backwards
event relationships when calling scheduling
I_OBJECT_DATA
up scheduling of events of a
Data of a Progress Tracking
Progress Tracking object T_SCENARIO
object
T_OFFSET
Table of event relationships for
the event scenario

Table of relevant time intervals

This is custom documentation. For more information, please visit the SAP Help Portal 73
2/10/2023

Method Description Parameter for the Method Description

PRINT_STATUS_NOTE Control the printing of status I_TSTNT Administration data of the


information status information
I_OBJECT_DATA
Data of a Progress Tracking
T_LINES
object

Table status information lines

SAVE_EVENTS Update the events for Progress T_EVENTS Table of events


Tracking when saving

To display the methods of the BAdIs and thereby the interfaces, use transaction SE18.

To implement the methods, use transaction SE19.

Displaying Progress Tracking Data in the Purchase Order

Use
If you use the single screen transaction to create, change, or display purchase orders (ME21N, ME22N, ME23N) or release them
(ME29N), the item details provide status information and progress tracking data for monitoring the progress of purchase
orders.

Prerequisites
The display of progress tracking data in the purchase order item details is not determined by your own, customer-speci c
Customizing settings. To create and change progress tracking data in transaction EXPD, however, you must have made the
required settings in Customizing for Project System under Progress Progress Tracking .

Features
You can display all progress tracking data that can also be called in the overview screen of the Progress Tracking: Purchase
Order Selection transaction (EXPD) for individual purchase order items. The system archives purchase order-related progress
tracking data together with the purchase order.

Displaying Progress Tracking Data

You can use list elds to choose the purchase order item and order schedule line for which you want the system to display an
overview of all relevant progress tracking data. From the event overview, you can access the progress tracking subitems and
query status information.

 Note
In the purchase order, you can only display progress tracking data. To select order schedule lines as progress tracking objects
and enter or change progress tracking data , you must use the Progress Tracking: Purchase Order Selection transaction
(EXPD).

You can use the Business Add-In (BAdI) BADI_EXPD_MM to specify which progress tracking pro le the system should use to
display the progress tracking data in the purchase order. If you do not implement the BAdI, the system determines the progress
tracking pro le from the personal settings in the user master.

Archiving Progress Tracking Data

This is custom documentation. For more information, please visit the SAP Help Portal 74
2/10/2023
The system archives all purchase order-related progress tracking data that is displayed on the Progress Tracking tab page
together with the purchase order. Data on the event assignment and the change time stamp is deleted. When you display
archived purchase orders (ME23N), the system also displays the archived progress tracking data.

Sustainability

Material Sustainability Record

De nition
A data record used to record all sustainability data relating to a particular material.

Use
You use this business object to record information about a material. You can enter information such as environmental
certi cates awarded to the material and their ratings, and the emission and waste associated with it. You use this information
when evaluating materials.

Integration
You access this object through the material record.

Vendor Sustainability Record

De nition
A data record used to record the sustainability information relating to a particular vendor.

Use
You use this business object to record a vendor's level of environmental, social, and economic compliance. For example, you can
enter information relating to a vendor's compliance with environmental initiatives, their adherence to labor policies such as
child labor, and the level of supply risk they pose. You can assign the vendor a score for each of these attributes, as well as an
overall score. You use this information to evaluate vendors and their products.

Integration
You access this object through the vendor record.

Uploading Data for Sustainability Info. Records

Use
You use this task to upload sustainability data for sustainability info. records from Microsoft Excel using the Data Transfer
Workbench. This enables you to do a mass upload of data, rather than entering data one record at a time.

This is custom documentation. For more information, please visit the SAP Help Portal 75
2/10/2023

Prerequisites
You have created the data in Microsoft Excel in the correct format. For more information on the speci cations of the le, see
Excel Format for Sustainability Info Records.

Procedure
Creating the Task

1. Open the SAP Easy Access Screen.

2. To open the Data Transfer Workbench, choose Tools Data Transfer Workbench , or enter the transaction SXDA.

3. Choose the Create Project button.

4. In the Project and Descriptions elds, enter the relevant details.

5. Choose the Sub-Project Wizard button and choose Continue.

The wizard for sub-projects opens.

6. In the Project step, if the details you already entered are correct, choose Continue.

7. In the Subproject step, make the relevant selection under the Object Description and choose Continue.

8. To upload material data, choose Standard Material under the Object Description (Obj. Type BUS1001001).

9. In the Tasks step, in the Subproject and Description elds, enter the relevant details.

10. Under Tasks, select the Load Data checkbox.

11. Choose the Attributes button and under Task Type, select the LOA REPO radio button and choose Continue.

12. Choose the Complete button.

The task to upload data has been created.

The project has been created and you have the option to run the task now, or schedule it to run later.

Running the Task

1. To upload the data now, under the Data Transfer Projects tree structure, navigate to your project.

2. Choose your project and choose the Start Run button.

3. Navigate to the location your Microsoft Excel le is stored and select the correct le.

4. Choose the Execute button.

The data starts uploading to system.

More Information
For more information on the Data Transfer Workbench, see Data Transfer Workbench.

For more information on how to upload sustainability data for vendors, see Uploading Sustainability Data for Vendors.

Excel Format for Sustainability Info. Records


This is custom documentation. For more information, please visit the SAP Help Portal 76
2/10/2023

Use
The Microsoft Excel le for uploading the master data for sustainability info. records needs to be in format below. You cannot
use any special characters in this le.

The data in the elds must correspond to the following data:

Features

Column Heading Format Example

A MATNR Alphanumeric 612

B LIFNR Alphanumeric 2000000153

C WERKS Numeric 00001

D EKORG Numeric 00001

E VALIDITY_START Date DD.MM.YYYY 01.01.2010

F VAILIDITY_END Date DD.MM.YYYY 01.01.2011

G WERKS_NAME Alphanumeric Plant

H DEL_FLAG Can be empty or 'X' X

I OVERALL_RAITING Numeric ≤100 78

J RECYCLED_CONTENT Numeric 23

K GHG_SCOPE1 Numeric 21

L GHG_SCOPE1_UN Text, de ned unit KT

M GHG_SCOPE2 Numeric 35

N GHG_SCOPE2_UN Text, de ned unit KT

O GHG_SCOPE3 Numeric 867

P GHG_SCOPE3_UN Text, de ned unit KT

Q DIRECT_ENERGY Numeric 36

R DIRECT_ENG_UNIT Text, de ned unit KJ

S DIRECT_WATER Numeric 86

T DIRECT_WATER_UN Text, de ned unit CCM

U DIRECT_WASTE Numeric 77

V DIRECT_WASTE_UN Text, de ned unit KT

More Information
For information on how to upload material sustainability data, see Uploading Data for Sustainability Info. Records.

For information on how to upload vendor sustainability data, see Uploading Sustainability Data for Vendors.

This is custom documentation. For more information, please visit the SAP Help Portal 77
2/10/2023

Excel Format for Vendor Sustainability Data

Use
The Microsoft Excel le for uploading vendor master data needs to be in format below. You cannot use any special characters in
this le.

The data in the elds must correspond to the following data:

Features

Column Heading Format Example

A LIFNR Alphanumeric 237682

B VALIDITY_START Date DD.MM.YYYY Date DD.MM.YYYY

C VALIDITY_END Date DD.MM.YYYY 01.01.2011

D AUDIT_AGENCY Text Price Agency

E AUDIT_CONDUCT_ON Date DD.MM.YYYY 01.01.2011

F SUPP_COC Can be empty or ʻX’ X

G SUPP_COC_DAT Date DD.MM.YYYY 01.01.2011

I SUST_RPT_RATING Numeric ≤100 40

J SUST_REPORT_DATE Date DD.MM.YYYY 01.01.2011

K DEL_FLAG Can be empty or ʻX’ X

L OVERALL_SCORE Numeric ≤100 78

M TOT_RESP_SCORE Numeric ≤100 45

N TOT_ENV_SCORE Numeric ≤100 16

O TOT_ECO_SCORE Numeric ≤100 61

P SOC_COMMENTS Text Freetext

Q SOC_PROC_SYS ʻ0’ or ʻ1’ or ʻ2’ or ʻ3’ 2

R HUMAN_RIGHTS ʻ0’ or ʻ1’ or ʻ2’ or ʻ3’ 1

S HEALTH_SAFETY ʻ0’ or ʻ1’ or ʻ2’ or ʻ3’ 3

T SOC_FINES Numeric 455

U SOC_FINES_CURR Text, de ned currency USD

V DISCRIMINATION ʻ0’ or ʻ1’ or ʻ2’ or ʻ3’ 0

W CHILD_LABOUR ʻ0’ or ʻ1’ or ʻ2’ or ʻ3’ 3

X FORCED_LABOUR ʻ0’ or ʻ1’ or ʻ2’ or ʻ3’ 2

Y COL_BARGAINING ʻ0’ or ʻ1’ or ʻ2’ or ʻ3’ 1

Z ANTI_CORRUPTION ʻ0’ or ʻ1’ or ʻ2’ or ʻ3’ 2

AA WOMEN_OWNED ʻ0’ or ʻ1’ or ʻ2’ 0

This is custom documentation. For more information, please visit the SAP Help Portal 78
2/10/2023
AB WOM_OWNED_EXP Date DD.MM.YYYY 01.01.2011

AC MINORITY_OWNED ʻ0’ or ʻ1’ or ʻ2’ 1

AD MIN_OWNED_EXP Date DD.MM.YYYY 01.01.2011

AE ENV_COMMENTS Text Freetext

AF ENV_PROTECTION ʻ0’ or ʻ1’ or ʻ2’ or ʻ3’ 3

AG ENV_INITIATIVES ʻ0’ or ʻ1’ or ʻ2’ or ʻ3’ 2

AH ENV_TECHNOLOGY ʻ0’ or ʻ1’ or ʻ2’ or ʻ3’ 1

AI ENV_PROC_SYS ʻ0’ or ʻ1’ or ʻ2’ or ʻ3’ 0

AJ ENV_FINES Numeric 355

AK ENV_FINES_CURR Text, de ned currency USD

AL TTL_ENR_CONS Numeric 21

AM TTL_ENR_CONS_UN Text, de ned unit KJ

AN RENEWABLE_ENERGY Numeric 34

AO RENEW_ENERGY_UN Text, de ned unit KJ

AP TTL_WATER_CONS Numeric 45

AQ TTL_WATER_CON_UN Text, de ned unit CCM

AR RECYCLED_WATER Numeric 56

AS RECYCL_WATER_UN Text, de ned unit CCM

AT GHG_SCOPE1 Numeric 21

AU GHG_SCOPE1_UN Text, de ned unit KT

AV GHG_SCOPE2 Numeric 22

AW GHG_SCOPE2_UN Text, de ned unit KT

AX GHG_SCOPE3 Numeric 34

AY GHG_SCOPE3_UN Text, de ned unit KT

AZ WASTE_NON_HZD Numeric 23

BA WASTE_NON_HZD_UN Text, de ned unit KT

BB WASTE_HZD Numeric 13

BC WASTE_HZD_UNIT Text, de ned unit KT

BD WASTE_RECYCLED Numeric 13

BE WASTE_RECYCLD_UN Text, de ned unit KT

BF TOTAL_SPEND Numeric 1000

BG TOTAL_SPEND_CURR Text, de ned currency USD

BH TOTAL_REVENUE Numeric 3000

BI TOT_REVENUE_CURR Text, de ned currency USD

BJ EMPLOYEE_COUNT Numeric 899

This is custom documentation. For more information, please visit the SAP Help Portal 79
2/10/2023

BK TOTAL_RISK ʻ0’ or ʻ1’ or ʻ2’ or ʻ3’ 0

BL FINANCIAL_RISK ʻ0’ or ʻ1’ or ʻ2’ or ʻ3’ 1

BM LOGISTICAL_RISK ʻ0’ or ʻ1’ or ʻ2’ or ʻ3’ 2

BN QUALITY_RISK ʻ0’ or ʻ1’ or ʻ2’ or ʻ3’ 3

BO POLITICAL_RISK ʻ0’ or ʻ1’ or ʻ2’ or ʻ3’ 0

BP DUMMY_EW_SSTN Single character X

More Information
For information on how to upload vendor sustainability data, see Uploading Sustainability Data for Vendors.

For information on how to upload material sustainability data, see Uploading Data for Sustainability Info. Records.

Uploading Sustainability Data for Vendors

Use
You use this procedure to upload sustainability data for vendors from Microsoft Excel using the Data Transfer Workbench. This
enables you to do a mass upload of data, rather than entering data one record at a time.

Prerequisites
You have created the data in Microsoft Excel in the correct format. For more information about the speci cations of the le, see
Excel Format for Vendor Sustainability Data.

Procedure
Creating the Task

1. Open the SAP Easy Access screen. To open the Data Transfer Workbench, choose Tools Data Transfer Workbench
or enter the transaction SXDA.

2. Choose Create Project.

3. In the Project and Descriptions elds, enter the relevant details.

4. Choose Sub-Project Wizard and choose Continue.

5. In the Project step, if the details you already entered are correct, choose Continue.

6. In the Subproject step, make the relevant selection under the Object Description and choose Continue.

7. To upload vendor data, choose Vendor under the Object Description (Obj. Type LFA1).

8. In the Tasks step, in the Subproject and Description elds, enter the relevant details.

9. Under Tasks, select the Load Data checkbox.

10. Choose Attributes and under Task Type, select the LOA REPO radio button and choose Continue.

11. Choose Complete.

This is custom documentation. For more information, please visit the SAP Help Portal 80
2/10/2023
The system creates a project and you can run the task now or schedule it to run later.

Running the Task

1. Navigate to your project in the Data Transfer Projects tree structure.

2. Choose your project and choose the Start Run button.

3. Navigate to the location your Microsoft Excel le is stored and select the correct le.

4. Choose the Execute button.

The system starts uploading the data.

More Information
For more information about the Data Transfer Workbench, see Data Transfer Workbench.

For more information about how to upload data for material info records, see Uploading Data for Sustainability Info. Records.

Vendor Sustainability Records

Use
You use this report to display sustainability information for a vendor, such as a vendor’s level of environmental, social, and
economic compliance, and their overall rating. You use this information when evaluating vendors.

Prerequisites
Before you run the report, you must select a unit for mass, volume, and energy as these are mandatory elds.

Activities
To access this report, on the SAP Easy Access screen, choose Logistics Materials Management Purchasing Master Data
Vendor List Displays Vendor Sustainability Records

Enter the relevant selection criteria and choose Execute.

This is custom documentation. For more information, please visit the SAP Help Portal 81

You might also like