Ansicht
Dokumentation

BBP_LIMIT_XPRA400 - XPRA for Conversion Limit to Item

Vendor Master (General Section)   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Purpose

Conversion of limit purchase orders with limit set at header level to limit purchase orders with limit set at item level:

For all limit purchase orders for which the limit is assigned to the document header, a new item with item category 'LIMI' (limit item) is generated. Purchasing information is stored for this new limit item. This information is determined from the document header and the limit set.

In addition, a new limit item in the link handler is assigned to the relevant limit set. The link between the document header and the limit set in the link handler is deleted. Also, an account assignment set in the limit purchase order is also assigned to the new limit item in the link handler and the previous link to the document header in the link handler is deleted.

An object linkage between the new limit item and the relevant shopping cart item is created.

Integration

The conversion and updating occur in one client. If a client has been successfully updated, then an entry is made in table T77ZZ. This ensures consistency. For example,, if the XPRA crashes during an execution, the new XPRA run starts again with the last client processed.

Conversion within a client works as follows:

First, all limit purchase orders are identified using the database table CRMD_LINK. For these purchase orders, all the information required to create the new limit items is determined via the database tables CRMD_ORDERADMIN_H, BBP_PDHGP, BBP_PDLIM and CRMD_LINK.

Then, an entry is made in the internal table GT_CRMD_ORDER_LINK for each limit item to be generated; the entry includes all the information that has been determined for this limit purchase order. An entryis only made if all the required information from the limit purchase order is available. If, for example, the limit set specified in the link handler (Table CRMD_LINK) does not exist in table BBP_PDLIM, then the system outputs a warning message specifying the GUID, and the relevant limit purchase order is not converted. If, however, an account assignment set is not assigned to a limit purchase order, a conversion does occur because a limit purchase order is consistent even without an account assignment.

The new limit items are finally generated from the internal table GT_CRMD_ORDER_LINK. Only the relevant information is transferred to tables CRMD_ADMIN_I and BBP_PDIGP for the new limit items. As before, the update of the changed links between limit purchase order and limit set and between limit purchase order and account assignment set is prepared in the link handler CRMD_LINK. An object linkage is created.

If at least one new limit item has been generated, then the database is updated. Otherwise, the relevant client receives a warning message. If the database update could not be completed successfully, an error message is output and the entire client is not converted.

Once the update of the new limit items has been completed, all messages are written to a log and this is output when the report has finished.

Prerequisites

The XPRA is only carried out in EBP Releases EBP 1.0, EBP 2.0, EBP 3.0 and EBP 3.5. As of Release EBP 4.0, the limit purchase orders are already based on the structures with limit set at item level.

Features

Selection

Standard Variants

Output

Activities

Example

BAL_S_LOG - Application Log: Log header data   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 3681 Date: 20240520 Time: 074008     sap01-206 ( 86 ms )