SAP ABAP IMG Activity /CWM/PO_HIST_VALUE (BAdI: Determining Values for Purchase Order History)
Hierarchy
☛ IS-CWM (Software Component) Industry Solution Catch Weight Management
   ⤷ IS-CWM (Application Component) Industry Solution Catch Weight Management
     ⤷ /CWM/APPL_MM (Package) Inventory Management
IMG Activity
ID /CWM/PO_HIST_VALUE BAdI: Determining Values for Purchase Order History  
Transaction Code /CWM/15000037   (empty) 
Created on 20050303    
Customizing Attributes /CWM/PO_HIST_VALUE   BAdI: Determining Values for Purchase Order History 
Customizing Activity /CWM/PO_HIST_VALUE   BAdI: Determining Values for Purchase Order History 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name /CWM/PO_HIST_VALUE    

Use

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.

Requirements

Standard settings

  • 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.

Activities

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

  1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.
    The system displays the initial screen for creating Business Add-In implementations.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. Save and activate your code. Navigate back to the Change Implementation screen.
    Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

Siehe auch:

Methoden

Ermittlung von Werten für Tabelle EKBE

Ermittlung von Werten für Tabelle EKBZ

Example

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG /CWM/PO_HIST_VALUE 0 /CWM/SO70000001 Industry Solution Catch Weight Management 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20050303 
SAP Release Created in 200