Ansicht
Dokumentation

SDXPRA01 - Xpra for enhancing customer purchase order number

BAL_S_LOG - Application Log: Log header data   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Description

Up until Release 4.0 the purchase order number field used to be saved in the sales document header with a length of 20. Now it should be saved in the business data for the sales document in a length of 35 (because of EDI). This means that as of Release 4.0, it can also be entered at item level.

The report reads through the whole of table VBAK and transports the following fields into the new fields in table VBKD:

. vbak-bstnk --> vbkd-bstkd + vbkd-bstkd_m

. vbak-bsark --> vbkd-bsark

. vbak-bstdk --> vbkd-bstdk

. vbak-ihrez --> vbkd-ihrez

Processing takes place step by step:

100 VBAK records are read, then the corresponding VBKD records are
processed and updated. A DB Commit takes place after 200 packets.

Requirements

XPRA doesn't run if the number of VBAK data records is greater than 600,000 lines and an upgrade is active. XPRA has to run after the upgrade.

If a purchase order is read from CO, then XPRA has to run during the upgrade.

The query for this is:

T880-INDPO <> initial and (T000k-GSBK <> initial or
T000K-PCK <> intial ).

rdisp/max_wprun_time - Maximum work process run time   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 1417 Date: 20240601 Time: 080113     sap01-206 ( 23 ms )