Ansicht
Dokumentation

/CWM/PO_HIST_VALUE - BAdI: Determining Values for Purchase Order History

BAL_S_LOG - Application Log: Log header data   General Material Data  
This documentation is copyright by SAP AG.

Business Add-In (BAdI) /CWM/PO_HIST_VALUE is used in the Catch Weight Management (IS-CWM) component.

You can use this BAdI to update values in the purchase order history (database tables EKBE and EKBZ) when posting goods movements to purchase orders.

Behavior in the standard system

Goods movements are valuated in Logistics. This means that when they are posted to purchase orders, quantities and valuation data are available and are updated to the purchase order history.

Behavior in Catch Weight Management

In SAP Catch Weight Management, goods movements are not valuated in Logistics, but rather in Inventory Accounting. In Logistics, valuation information is no longer available when posting takes place. Therefore, when goods movements are posted to purchase orders, only the quantities are posted to the purchase order history. The values are not updated.

BAdI /CWM/PO_HIST_VALUE

You can use BAdI /CWM/PO_HIST_VALUE to create your own procedures for determining values for the purchase order history update.

To this end, the BAdI contains the methods CALCULATE_VALUE_EKBE (update of database table EKBE) and CALCULATE_VALUE_EKBZ (update of database table EKBZ for delivery costs/conditions).

When the BAdI is called, the same data is provided as is used by the database tables EKBE and EKBZ when data records are created for the purchase order history update. As a result, the BAdI returns the contents of the following fields:

• DMBTR (Amount in Local Currency)

• HSWAE (Local Currency)

• WRBTR (Amount in Document Currency)

• WAERS (Currency Key)

The values determined by the BAdI are transferred to the aforementioned database tables for the purchase order history when goods movements are posted to purchase orders.

In SAP Catch Weight Management, there are no functions that depend on these values, for example, posting logic or determination of default values in logistics invoice verification. The values determined in this way are of a purely static nature.

• Im Standard ist das Business Add-In nicht aktiv.

• Das Business Add-In ist nicht mehrfach nutzbar.

• Das Business Add-In ist nicht filterabhängig.

After you have called the IMG activity, proceed as follows:

1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.

If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.

1. In the corresponding field, enter a short text for implementation .
2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
3. Choose the tab Interface.

The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.

If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.

1. Save your entries and assign a package.
2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
4. Save and activate your coding, and navigate back to the screen Change Implementation.
5. Save on the screen Change Implementation.

Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.

1. Choose Activate.

When the application program is executed, the coding you have created will be run.

Methoden

Ermittlung von Werten für Tabelle EKBE

Ermittlung von Werten für Tabelle EKBZ

General Material Data   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 5155 Date: 20240419 Time: 151114     sap01-206 ( 70 ms )