LE - Logistics Execution

Release 4.6C

HELP.CAARCLE

LE - Logistics Execution

SAP AG

Copyright
Copyright 2001 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft , WINDOWS , NT , EXCEL , Word , PowerPoint and SQL Server are registered trademarks of Microsoft Corporation. IBM , DB2 , OS/2 , DB2/6000 , Parallel Sysplex , MVS/ESA , RS/6000 , AIX , S/390 , AS/400 , OS/390 , and OS/400 are registered trademarks of IBM Corporation. ORACLE is a registered trademark of ORACLE Corporation. INFORMIX -OnLine for SAP and Informix Dynamic Server Informix Software Incorporated.
TM

are registered trademarks of

UNIX , X/Open , OSF/1 , and Motif are registered trademarks of the Open Group. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C , World Wide Web Consortium, Massachusetts Institute of Technology. JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.

April 2001

SAP AG

LE - Logistics Execution

Icons
Icon Meaning Caution Example Note Recommendation Syntax

April 2001

LE - Logistics Execution

SAP AG

Inhalt
LE - Logistics Execution ....................................................................................5
Archiving Warehouse Management Records (LE-WM) ............................................................. 6 Object Definition (LE-WM) ............................................................................................................ 7 Program Technical Data (MM-WM) .............................................................................................. 8 Set up the System to Run Archiving Programs (LE-WM) ......................................................... 9 Archive Warehouse Management Records (MM-WM) ............................................................. 10 Make a Test Run (MM-WM) ......................................................................................................... 11 Read Archived Data (MM-WM) ................................................................................................... 12 Archiving of Deliveries (LE-SHP)............................................................................................... 13 Special Features in Archiving (LE-SHP) ................................................................................... 16 Checks (LE-SHP) ......................................................................................................................... 17 Variant Settings for Archiving (LE-SHP)................................................................................... 19 Variant Settings for the Check (LE-SHP) .................................................................................. 21 Variant Settings for Reloading (LE-SHP) .................................................................................. 22 Application Customizing (LE-SHP)............................................................................................ 23 Analyzing an Existing Archive (LE-SHP) .................................................................................. 25 Single Document Display using SAP AS (LE-SHP) ................................................................. 26 Authorizations (LE-SHP) .......................................................................................................... 28 Archiving of Shipments (LE-TRA) ............................................................................................. 29 Archiving Shipment Documents (LE-TRA) ............................................................................... 31 Reloading Shipments (LE-TRA) ................................................................................................. 32 Archiving Shipment Cost Documents (LE-TRA) ...................................................................... 33 Archiving Shipment Cost Documents (LE-TRA) ...................................................................... 35 Reloading Shipment Cost Documents (LE-TRA) ..................................................................... 36

April 2001

SAP AG

LE - Logistics Execution LE - Logistics Execution

LE - Logistics Execution
The following table shows the available archiving objects: Objects in LE Archiving Objects RL_* [Seite 7] RV_LIKP [Seite 13] SD_VTTK [Seite 29] SD_VFKK [Seite 33]

Warehouse Management Records Deliveries Shipment Documents Shipment Cost Documents

April 2001

LE - Logistics Execution Archiving Warehouse Management Records (LE-WM)

SAP AG

Archiving Warehouse Management Records (LE-WM)

Batch programs have been provided to archive records in the Warehouse Management (WM) system and delete old data that is no longer needed in the system. These programs can be used to free space in the database and to provide accessible records for future reference. Object Definition (LE-WM) [Seite 7] Program Technical Data (LE-WM) [Seite 8]

How to...
Set up the System to Run Archiving Programs (LE-WM) [Seite 9] Archive Warehouse Management Records (LE-WM) [Seite 10] Make a Test Run (LE-WM) [Seite 11] Read Archived Data (LE-WM) [Seite 12]

April 2001

SAP AG

LE - Logistics Execution Object Definition (LE-WM)

Object Definition (LE-WM)

For the Warehouse Management (WM) system, you can archive WM records using the objects and reports listed in the following table: Objects/Reports used for Archiving Warehouse Management Records Object RL_TA RL_TB RL_LUBU RL_LINKP RL_LINV RL_LSEG Tables to be archived LTAK, LTAP LTBK, LTBP LUBU LINK, LINP LINV LSEG Report RLREOT00 RLREOB00 RLREOU00 RLREOI00 RLREOH00 RLREOL00 Records Transfer orders Transfer requirements Posting change notices System inventory records Inventory histories Warehouse material movements

These reports archive processed records that have been in the WM system for a specified number of days. Using these programs, it is possible to archive records for several warehouse numbers simultaneously.

When you archive transfer orders that are earmarked for the entry of worker performance data, the system checks to see whether the performance data was completely processed. This is checked in the logical RTL database. For test purposes, you can display a list of the number of records that will be archived and deleted from the system before actually archiving them. Additionally, you can read data that has been archived.

April 2001

LE - Logistics Execution Program Technical Data (MM-WM)

SAP AG

Program Technical Data (MM-WM)

Memory Requirement
The amount of memory needed to archive records varies with the size and number of objects archived. For example, the memory requirement for archiving transfer orders (TOs) is based on the following formula: (TO header length + avg. no. of items) x no. of TOs

Run Time
The time needed to run the archiving program depends on the number of records that are archived and the system load and performance.

April 2001

SAP AG

LE - Logistics Execution Set up the System to Run Archiving Programs (LE-WM)

Set up the System to Run Archiving Programs (LE-WM)

1. Check the path and archive names that are in the platform-independent table of archive names. The system then references a physical data path that you can maintain as a system parameter. You can find information about how to do this step in the Basis Implementation Guide. 2. Create variants for the reports: Use Customizing for Archiving [Extern] for the deletion report. Use the archiving management transaction SARA for the archiving report. 3. In Customizing for Archiving [Extern], you determine the size of the archive file in MB and define the maximum number of documents for each archive file. 4. If you want to save the archive optically, you also have to maintain the data for optical archiving in Customizing for Archiving [Extern]. For information about optical archiving, see the documentation on this topic. In any case, you have to maintain the spool data and can decide whether you want the summary of the archived and deleted documents to be printed or stored in a spool file. You can find archiving management data using the transaction SARA. The PATH and FILE names under which the data is archived are of particular significance.

April 2001

LE - Logistics Execution Archive Warehouse Management Records (MM-WM)

SAP AG

Archive Warehouse Management Records (MM-WM)

To archive documents, we recommend that you do not start the archiving reports directly, but rather in the background using the archiving management transaction SARA. Archiving and the deletion of records from the data base are separated into two reports. The archiving programs create the archives and then start the deletion programs as a separate job for each archive. The deletion reports can only delete data that they read from the archives (see also The Archiving Procedure [Extern]). The size of the archive files can be set in advance. Since archiving and deletion programs are processed simultaneously, system performance is improved significantly when processing large quantities of data.

10

April 2001

SAP AG

LE - Logistics Execution Make a Test Run (MM-WM)

Make a Test Run (MM-WM)

To determine how many documents will be archived, you can start these reports directly for a test run. You can also print the displayed list. 1. Select System Services Reporting from any SAP menu. The system displays the initial screen for starting reports. 2. Enter the report name (see table under Object Definition (MM-WM) [Seite 7]) in the Program field and select Execute. The system displays the initial screen. 3. Select only the check box for the Test run (do not delete) field on the initial screen of each report and enter the number of days beyond which the records are to be archived. Do not select the checkbox for the Create archive field. You can also place a time limit on the archiving programs. For example, you can limit the batch program to archive all transfer orders that have been confirmed prior to 90 days ago. The system default is 200 days. 4. To display the log, select Execute.

When you start the report to archive and delete documents using the archiving management transaction SARA, the system does not display a log online because these programs are started as a batch process.

April 2001

11

LE - Logistics Execution Read Archived Data (MM-WM)

SAP AG

Read Archived Data (MM-WM)

To read data that has been archived, select System Services Reporting from any menu and enter one of the following in the Program field. RLRB0001 RLRT0001 RLRU0001 RLRI0001 RLRH0001 Transfer requirements Transfer orders Posting change notices Inventory documents Inventory histories

The WM archive files have the general logical file name "ARCHIVE_DATA_FILE". You can start the reports used for reading the archived files from archive management.

12

April 2001

SAP AG

LE - Logistics Execution Archiving of Deliveries (LE-SHP)

Archiving of Deliveries (LE-SHP)

Definition
Archiving object RV_LIKP for archiving deliveries (inbound and outbound deliveries). See also: The Archiving Object [Extern]

Use
Before using the archiving object, you should first check the application Customizing. See also: Application Customizing (LE-SHP) [Seite 23]

Structure
Tables
When you use the archiving object RV_LIKP, the system archives data from the following tables: Table reference Table EIKP EIPO LIKP LIPS LIPSDG NAST SADR VBFCL VBPA VBUK VBUP VBUV LIPSDG DLFLD LIPSPO LIPSRF Table Name Foreign trade: Export/Import item data Foreign trade: Export/Import header data Sales and distribution document: Delivery: Header data Sales and distribution document: Delivery: Item data Appendix table for dangerous goods data Output status Address management: Company data Sales document flow cluster Sales document: Partner Sales document: Header status and administrative data Sales document: Item status Sales document: Incompletion log Appendix table for dangerous goods data Delivery fields that cannot be changed (Decentralized WM) LIPS reference data for purchase order (Decentralized WM) LIPS reference data for purchase order (Decentralized WM)

April 2001

13

LE - Logistics Execution Archiving of Deliveries (LE-SHP)

SAP AG

You can carry out archiving for handling units using the archiving object LE_HU (see also Archiving Handling Units (LO-HU) [Extern] The following archiving classes are also archived: Tables for Archiving Class TEXT [Extern] Tables for Archiving Class CHANGEDOCU [Extern]

Function
The following functions are available for RV_LIKP: Function/report assignment Function Report Archive Delete Analyze Restore See also: Variant Settings for Archiving (LE-SHP) [Seite 19] Variant Settings for Reloading (LE-SHP) [Seite 22] Analyzing an Existing Archive (LE-SHP) [Seite 25] Variant Settings for Checking (LE-SHP) [Seite 21] S3LIKPWR S3LIKPDL S3LIKPAU S3LIKPRL

Checking S3LIKPPT

Calling Up Archiving
To archive sales activities, choose Environment Archive documents Deliveries on the Shipping Screen [Extern]. To archive inbound deliveries, choose Environment Archive documents Inbound deliveries on the Shipping Screen [Extern]. Alternatively, you can also call up archive administration via Tools Administration and then Administration Archiving. Enter the object name RV_LIKP.

Integration
Inbound deliveries should be archived before sales documents and billing documents. This sequence is a result of the way the documents are linked via document flow. Inbound deliveries that are not relevant for goods movements can only be archived after the underlying purchase order has been archived. Inbound deliveries that are relevant for goods movements are complete after the goods receipt posting, and they can be archived directly after the other conditions have been checked successfully. If corresponding shipments exist (LE-TRA), deliveries can only be archived after these shipments have been archived successfully.

14

April 2001

SAP AG

LE - Logistics Execution Archiving of Deliveries (LE-SHP)

April 2001

15

LE - Logistics Execution Special Features in Archiving (LE-SHP)

SAP AG

Special Features in Archiving (LE-SHP)

Check Suitability for Archiving
When using deliveries, a report (S3LIKPPT) is provided for carrying out a check on suitability for archiving. See also: Variant Settings for Checking (LE-SHP) [Seite 21]

16

April 2001

SAP AG

LE - Logistics Execution Checks (LE-SHP)

Checks (LE-SHP)
The following checks are carried out on a delivery before it can be archived. Residence time Flow (mandatory) Status of the shipment document Status of billing document FI (optional) Check residence of flow documents (optional) Alternative database access (optional)

Residence time
A delivery can only be archived if a period defined in Customizing (residence time) has elapsed since the completion date (see also: Application Customizing (LE-SHP) [Seite 23]). For this purpose, the system checks the following entries for the outbound delivery: If a residence time is maintained for delivery type and sales organization, then this value is checked in the document. If no entry exists, then the search is carried out using only the sales organization. If no entry exists for this either, then the standard value of 30 days is used. The residence time is checked only on the basis of the delivery type since inbound deliveries are not assigned to any sales organization. In Customizing, maintain the entry Sales organization, as described under Application Customizing (LE-SHP) [Seite 23].

For this purpose, the system checks the following entries for the inbound delivery.

The selection screen for the variants contains the checkbox Check doc. flow residence, with which you can set the basis for calculation of the residence time. If the checkbox is not set, then the residence time is calculated on the basis of the creation date of the document. If the checkbox is set, then the residence time is calculated on the basis of the last flow document

Status of the shipment document

In the next stage, the transportation planning status is checked. If the shipment containing the delivery has a status of A or B (not processed or partially processed), then the delivery cannot be archived. If the shipment has status C (completed), then the system also checks whether it has already been archived. If this is not the case, then the delivery cannot be archived.

Status of billing document

In the final stage, the status of the billing document is checked for the outbound deliveries, that is, the system checks whether the billing document has been forwarded to Financial Accounting. The checking sequence for sales organization and delivery type is the same as for the residence time. If no entry exists, then the status is set to X (= to check).

April 2001

17

LE - Logistics Execution Checks (LE-SHP)

SAP AG

Accounting documents
If the checkbox Check FI document is set, the system checks whether the billing document is settled in Financial Accounting (e.g. via payment).

Alternative Database Access

If you select the Alternative DB access checkbox, you allow the database to use an alternative method for carrying out data procurement This can, for example, be used to improve performance of the archiving program.

18

April 2001

SAP AG

LE - Logistics Execution Variant Settings for Archiving (LE-SHP)

Variant Settings for Archiving (LE-SHP)

Use
You can set the archiving criteria in variant settings for archiving.

Range of Functions
The following options are available:

Entry Fields
Document selection Select the documents to be archived. Delivery type Choose the delivery type of the deliveries to be archived. In one archiving run, you can process either outbound deliveries only or inbound deliveries only.

Checkboxes
Create archive Select this option if you want to create archive files. Deletion program in test mode If you do not want the archived data to be deleted automatically after the archive files have been created, select this option. This option is ignored if Create archive has been deactivated. Check FI document (optional) If the checkbox Check FI document is set, the system checks whether the billing document is settled in Financial Accounting (e.g. via payment). Check residence of flow documents If the checkbox is not set, then the residence time is calculated on the basis of the creation date of the document. If the checkbox is set, then the residence time is calculated on the basis of the last flow document Alternative Database Access If you select the Alternative DB access checkbox, you allow the database to use an alternative method for carrying out data procurement This can, for example, be used to improve performance of the archiving program.

Activities
The following table provides an overview of some typical settings: Task Settings

April 2001

19

LE - Logistics Execution Variant Settings for Archiving (LE-SHP) Test run Productive run See also: Creating Archive Files [Extern] Select the documents 1. Select the documents. 2. Choose Create archive.

SAP AG

20

April 2001

SAP AG

LE - Logistics Execution Variant Settings for the Check (LE-SHP)

Variant Settings for the Check (LE-SHP)

Use
You can set the checking criteria in variant settings for the check.

Remember that checking delivery documents is carried out via the preliminary run function. The preliminary run can also be started directly in the ABAP Editor via Report S3LIKPPT.

Features
The following options are available:

Entry Fields
Document selection Select the documents to be checked.

Checkboxes
Detail display Select this option if you want to see the checking log for each document that could not be archived. Check residence of flow documents If the checkbox is not set, then the residence time is calculated on the basis of the creation date of the document. If the checkbox is set, then the residence time is calculated on the basis of the last flow document

Check FI document Select this option if you want to check whether all existing accounting documents for a delivery have been cleared.

Alternative Database Access If you select the Alternative DB access checkbox, you allow the database to use an alternative method for carrying out data procurement This can, for example, be used to improve performance of the archiving program.

Activities
The checking log is split into two sections - the header and the detail display. The header contains the statistical data for the check; the detail display shows the checking status for each delivery. You reach the order display transaction by clicking on the line containing the delivery number. The detail display is activated via the Detail display checkbox.

April 2001

21

LE - Logistics Execution Variant Settings for Reloading (LE-SHP)

SAP AG

Variant Settings for Reloading (LE-SHP)

Use
You can set reloading criteria in variant settings for reloading.

When reloading deliveries, the corresponding CO data is not simultaneously reloaded into the system. Therefore you should reload deliveries only in case of emergency, for example, if documents were wrongly selected. For this reason you cannot call this function up with the menu. Please contact your system administrator.

Features
The following options are available:

Entry Fields
Document selection Select the documents to be reloaded.

Checkboxes
Test run Select this option if you only want to simulate reloading, for example, to check possible errors. See also: Reloading Archived Data [Extern]

22

April 2001

SAP AG

LE - Logistics Execution Application Customizing (LE-SHP)

Application Customizing (LE-SHP)

Use
In application Customizing, you can set delivery-specific requirements for archiving.

Range of Functions
The following input fields are at your disposal: Sales organization Delivery type Residence time of a delivery in days You use these parameters to set the residence time for every combination of sales organization and delivery type. Since inbound deliveries are not assigned to any sales organization, maintain a generic entry (X) for the sales organization for this delivery type. Check billing documents for completion You use this parameter to check whether a billing document has been forwarded to Financial Accounting.

Entry Options in Application Customizing (V_TVARL)

The following table displays possible value combinations that you can use when maintaining views V_TVARL: Sales organization 1. 2. 3. 4. 5. * 0001 * 00* 0001 Delivery type * * LF L* LF Document date 40 20 100 1

The examples can be understood as follows: 1. The standard residence time (30 days) is used for all delivery types for all sales organizations. 2. A residence time of 40 days is used for all delivery types for sales organization 0001. 3. A residence time of 20 days is used for delivery type TA for all sales organizations. 4. A residence time of 100 days is used for all delivery types starting with L for all sales organizations starting with 00. 5. A residence time of 1 day is used for delivery type LF for sales organization 0001.

If you do not maintain the views, the system cannot archive the documents. So that archiving for inbound deliveries functions correctly, you must make sure that you maintain a residence time other than zero for this delivery type and that you set

April 2001

23

LE - Logistics Execution Application Customizing (LE-SHP)

SAP AG

a generic entry for the sales organization. You should set your entries as follows if EL is the delivery type of the inbound delivery: Sales organization * See also: Customizing [Extern] Delivery type EL Document date >1

24

April 2001

SAP AG

LE - Logistics Execution Analyzing an Existing Archive (LE-SHP)

Analyzing an Existing Archive (LE-SHP)

Use
The Analyze function allows you to view a list of the most important header and item data for archived deliveries from a number of archiving runs specified by you.

Entry Fields
Document selection Select the documents that you want to display.

April 2001

25

LE - Logistics Execution Single Document Display using SAP AS (LE-SHP)

SAP AG

Single Document Display using SAP AS (LE-SHP)

Use
You can use the business view in the standard system for the object RV_LIKP to display individual documents for archived deliveries via the archiving information system (SAP AS). These are presented in list form.

Prerequisites
There is at least one information structure for the archiving object RV_LIKP, created on the basis of the standard SAP field catalogues SAP_ RV_LIKP_001 or SAP_ RV_LIKP_002. The information structure has been activated and set up. The information structure contains the field VBELN as a key field.

In order to be able to use the process-oriented views (see below) in the archiving information system, there must be information structures available for the archiving objects SD_VBAK and SD_VBRK. The authorizations [Seite 28] for displaying archived deliveries have been maintained.

Features
Single document display
Within the single document display for deliveries, you can display the header and item data. The directly preceding document as well as all subsequent documents to the selected single document can be displayed. By clicking with the mouse you can display the corresponding preceding or subsequent document. It is irrelevant here whether the selected document is still in the database or has already been archived.

If a business view of the archiving information system is available, this is used to access the archived data. If there is no business view available and the document is no longer in the database, it is not possible to display the document. In this case, you only see the document number, further details are not possible. Specific documents such as WM transport orders or shipping elements have no display functions and can not be displayed if they are in the database. You can use the function Display originals to show the original document for an archived delivery via ArchiveLink. If they are available this also applies to related Workitems and IDOCs.

Displaying via ArchiveLink is only possible when there is a correct link to the Archive Link. The ArchiveLink Viewer must also be set correctly and enable access to the

26

April 2001

SAP AG

LE - Logistics Execution Single Document Display using SAP AS (LE-SHP)

corresponding optical archive. The link entries in the relevant tables for ArchiveLink, Workitem and IDOCs must also be available.

Process Orientated Retrieval

From the entry document you have the option of navigating along the whole process chain. It does not matter whether the preceding or subsequent document is still in the database or has already been archived. The following prerequisites must be fulfilled: The document to be displayed must have an online display function; this feature is identified by the magnifying glass symbol. The document must if it has been archived be part of an active SAP AS information structure. To be able to display the corresponding archived preceding or subsequent document, a business view must be available for the archiving object being used.

You can use this function to navigate in the business process as you want to. The individual navigation steps are called up and are specified with a screen number behind the document type.

Displaying the Original Documents via ArchiveLink

After leaving the business view, there is the option of going directly from the SAP AS list into the ArchiveLink originals. This also applies to linked Workitems and IDOCs, if these are available.

The same prerequisites apply for displaying original documents as for the individual document displays (see above). You can find further information on the Archiving Information System (SAP AS) under Archiving information system (SAP AS) [Extern].

April 2001

27

LE - Logistics Execution Authorizations (LE-SHP)

SAP AG

Authorizations (LE-SHP)
To display individual documents from archived deliveries via the archiving information system, you must have at least the following authorizations: 1. Reading archives: Object S_ARCHIVE APPLIC ARCH_OBJ ACTVT Value SD RV_LIKP 03 Description Application Archiving object Displaying archives

2. Displaying archived deliveries Object V_LIKP_VST VSTEL ACTVT Value * 03 Description Shipping point; can be specified Displaying the sales documents

3. Displaying documents set up via ArchiveLink: Object S_WFAR_OBJ OAARCHIV OAOBJEKTE OADOKUMENT ACTVT Value * * * 03 Description Access to a physical archive: can be specified Object category access; can be specified Document type access; can be specified Displaying archived originals

28

April 2001

SAP AG

LE - Logistics Execution Archiving of Shipments (LE-TRA)

Archiving of Shipments (LE-TRA)

The following points will be followed in this section Object Definition Check criteria for the archiving/deletion of data

Archiving Object Definition

You archive shipments in SD using the SD_VTTK archiving object. The following table lists the data archived by SD_VTTK. (You can also display this information by using Transaction SAR1). Parent Segment Segment Description VTTK VTTK VTTK VTTK VTTK VTTK VTTK VTTK VTTK VTTK VTTP VTTS VTSP VTPA VTFA VEKP VEPO NAST SADR Shipment document: Header data Shipment document: Item data Shipment document: Stages Shipment document: Assigning stages and items Partner for shipment Shipment document flow Sales document: Shipping element header Sales document: Shipping element item (contents) Output status Address management: Company data

You can carry out archiving for handling units using the archiving object LE_HU (see also Archiving Handling Units (LO-HU) [Extern]

Criteria for Archiving and Deleting

You can: Specify a number of days after the shipment document creation date as the retention period Specify a number of days after the shipment document change date as the retention period Check the minimum overall status of the shipment Check the transportation planned status of all the deliveries in the shipment This must be planned. Check the goods movement status of the shipment This must have either a Not relevant or a Fully processed status. Check the suitability for archiving of all other shipments in the transportation chain. This means that these shipments must meet all of the criteria described above and that they must fall within the range of shipment numbers specified when you started archiving.

April 2001

29

LE - Logistics Execution Archiving of Shipments (LE-TRA)

SAP AG

While the system always checks the last three criteria, you can set the first three in Customizing for Sales and Distribution under Data Transfer and Archiving Archiving Control.

30

April 2001

SAP AG

LE - Logistics Execution Archiving Shipment Documents (LE-TRA)

Archiving Shipment Documents (LE-TRA)

To archive shipment documents: 1. Choose Logistics Sales/distribution Shipping. 2. Choose Environment Archive documents. 3. If there is no variant, you must create a new one: Enter a description for the variant and choose Maintain. 4. Define the following for the variant: The range of shipment documents to be archived Whether the system should create archive files without deleting data from the database during a test run. Whether the system issues a normal or a detail log. If you specify a detailed log, the system reads all data within the shipment number range you specify from the database. The system checks data to determine if it can be archived, and it logs the result. ALL checks are carried out for every shipment. The archiving program runs faster if you do not mark the Issue log texts checkbox.

5. Choose Edit Continue. You reach the data screen in which you can define further attributes for the variant. 6. Save your variant. 7. Define a start time for the archiving run. 8. Enter a spool parameter, if you want a printout.

April 2001

31

LE - Logistics Execution Reloading Shipments (LE-TRA)

SAP AG

Reloading Shipments (LE-TRA)

To reload archived shipment documents: 1. Choose Logistics Sales/distribution Shipping. 2. Choose Environment Reload documents. 3. If there is no variant, you must create a new one: Enter a description for the variant and choose Maintain. 4. Define the following for the variant: The range of billing documents to be reloaded Whether reloading should run in test mode Whether to issue a standard or detailed log. You reach the data screen in which you can define further attributes for the variant. 6. Save your variant. 7. Select the archive file that contains the shipment documents. 8. Define a start time for the reload run. 9. Enter a spool parameter, if you want a printout.

5. Choose Edit Continue.

32

April 2001

SAP AG

LE - Logistics Execution Archiving Shipment Cost Documents (LE-TRA)

Archiving Shipment Cost Documents (LE-TRA)

The following points will be followed in this section Object Definition Check criteria for the integration of archiving/deletion of data

Archiving Object Definition

You archive shipping cost documents using the SD_VFKK archiving object The table lists the data archived by SD_VFKK. (You can also display this information by using Transaction SAR1). Parent Segment Segment Description VFKK VFKK VFKK VFKK VFKP VFKP VFKP VFKP VFKN VFPA VFSI VFZP KONV Shipment cost document: Header data Shipment cost document: Item data Shipment cost document: Accounting assignment Shipment cost document: Partners Shipment cost document: Subitem data Shipment cost document: Condition assignment Shipment cost document: Conditions

Criteria for Archiving and Deleting

The archiving program checks several criteria for every shipment cost document. A shipment cost document can be archived when the following requirements are met: The creation date of the shipment cost document must be at least N days in the past. I.e., the residence time of the shipment cost document must be N days. The last change date of the shipment cost document must be at least N days in the past. I.e., the residence time of the shipment cost document since the last change must be M days. If the shipment cost document has not yet been changed, then the creation date is used as the last change date. The purchase order for the shipment cost document should be completed and archived. The system determines this by checking whether the subsequent document(s) for the shipment cost document (i.e. service entry sheets) has already been archived. This check can be activated in Archiving control for shipment costs. The status of calculation must be set to C (fully calculated). The status of account assignment must be set to _ (blank = not relevant for account assignment) or C (fully account assigned). The status for forwarding must be set to _ (blank = not relevant for forwarding) or C (fully forwarded). The shipment, to which the shipment cost document refers, must be fully calculated.

April 2001

33

LE - Logistics Execution Archiving Shipment Cost Documents (LE-TRA)

SAP AG

The first four criteria are always checked by the program and cannot be altered, the last three, however, can be configured in Customizing.

34

April 2001

SAP AG

LE - Logistics Execution Archiving Shipment Cost Documents (LE-TRA)

Archiving Shipment Cost Documents (LE-TRA)

To archive shipment cost documents: 1. Select Logistics Logistics Execution Transportation Shipment Shipment costs Environment Archive documents 2. If there is no variant, you must create a new one: Enter a description for the variant and choose Maintain. 3. Define the following for the variant: The range of shipping cost documents to be archived Whether the system should create archive files without deleting data from the database during a test run. Whether the system issues a normal or a detail log. If you specify a detailed log, the system reads all data within the shipment cost document number range you specify from the database. The system checks data to determine if it can be archived, and it logs the result. ALL checks are carried out for every shipment cost document. The archiving program runs faster if you do not mark the Issue log texts checkbox.

4. Choose Edit Continue. You reach the data screen in which you can define further attributes for the variant. 5. Save your variant. 6. Define a start time for the archiving run. 7. Enter a spool parameter, if you want a printout.

April 2001

35

LE - Logistics Execution Reloading Shipment Cost Documents (LE-TRA)

SAP AG

Reloading Shipment Cost Documents (LE-TRA)

To reload shipment cost documents: 1. Select Logistics Logistics Execution Transportation .Shipment Shipment costs Environment Reload documents 2. If there is no variant, you must create a new one: Enter a description for the variant and choose Maintain. 3. Define the following for the variant: The range of shipment cost documents to be reloaded Whether reloading should run in test mode Whether the system issues log texts

4. Choose Edit Continue. You reach the data screen in which you can define further attributes for the variant. 5. Save your variant. 6. Choose the archive files from which you want to reload the shipment cost documents. 7. Define a start time for the reload run. 8. Enter a spool parameter, if you want a printout.

Result
The shipment cost documents you specified are reloaded. If a shipment cost document cannot be reloaded from the archive file (maybe because it is not within the correct number range or because an error occurred during reloading), then it is placed in a new archive file.

It generally only makes sense to reload documents soon after they have been archived. If important data, such as master data or Customizing settings, have been altered between the archiving and the reloading of the documents, this can lead to extreme discrepancies in the documents, since the entire environment has changed.

36

April 2001