SAP ABAP IMG Activity PP_OM_HEADER_MAT (BAdI: Determine Header Material of Purchase Requisition)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ PP (Application Component) Production Planning and Control
     ⤷ PP_OM_SFWS_SC (Package) PP Core Enhancements for Outsourced Manufacturing
IMG Activity
ID PP_OM_HEADER_MAT BAdI: Determine Header Material of Purchase Requisition  
Transaction Code S_E4A_94000253   (empty) 
Created on 20080626    
Customizing Attributes PP_OM_HEADER_MAT   Define Purchase Requisition Header Material 
Customizing Activity PP_OM_HEADER_MAT   Define Purchase Requisition Header Material 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name PP_OM_BD_BANF_HEADER_MATERIAL    

Use

You can use this Business Add-In (BAdI) to populate the Material field in the purchase requisition item if a purchase requisition is created through an externally processed operation. This enables you to also transfer the configuration data.

This material then appears in the external processing data of the routing or recipe.

If a purchasing info record is used, it must have been created for this material. You cannot specify a purchasing info record for a material group because the purchase requisition now relates to a material and no longer to a text item.

The short text of the purchase requisition item is not changed.

Requirements

Standard settings

  • In the standard system, the BAdI is not active.
  • The BAdI can be used multiple times.
  • The BAdI is filter-independent.

Activities

After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.

If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:

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

    The screen for creating BAdI implementations is now displayed.

  2. Enter a short text for the implementation in the Short text for implementation field.
  3. From the tab index, choose Interface.

    The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.

  4. Save your entries, and assign the implementation to a development class.
  5. Place the cursor on the method, and double-click to enter method processing.
  6. Enter the code for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
  7. Save and implement your code. Return to the Edit Implementation screen.
  8. Save the entries on the Edit Implementation screen.

    Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.

  9. Choose Activate

    The code you stored in the method will be run when the application program is executed.

Example

The example implementation PP_OM_BI_BANF_HEADER_MAT_DEMO has been developed for the following scenario:

Within a production order, a semifinished product is to be sent to an external processor (subcontractor) for further work to be carried out on it. Purchase requisitions and purchase orders are used to handle the commercial side of the processing. If a reference material for original batches has been maintained for the header material of the production or process order and #WIP batches required# has been specified in the control key of the externally processed operation, the reference material is adopted in the purchase requisition. Otherwise, the header material of the production or process order is adopted in the requisition. The configuration of the production or process order is also adopted in the latter document.
After this, the external processor returns the processed material to the ordering party. The latter takes over the new material that has been created and may carry out further work on it. At the end of the production process, the finished product is booked into the warehouse as a goods receipt against the production order.

In the standard SAP system, semifinished products can only be mapped through the use of work-in-process (WIP) batches. That is, you must activate the business function LOG_PP_WIP_BATCH to be able to use the example implementation for this scenario.

The example implementation has been developed specifically for the above-mentioned scenario. Other scenarios/requirements may not be completely covered by it.

Restrictions on the implementation of this BADI known to date:

  • If you work with info records, it is mandatory to enter a purchasing info record for the material in the routing or recipe and the production or process order. You cannot use a purchasing info record for a material group.
    You cannot maintain a purchasing info record for a material in a reference operation set.
  • In the goods receipt for a subcontract order, the inspection type is taken not from the operation as hitherto, but from the master record of the header material. If you want to use a special inspection type for externally processed operations, you must use the user exit QAAT0001.
  • The implementation does not work with materials that are subject to a serial number requirement.
  • At the time of the goods receipt for the account-assigned subcontract order, the consumption data is updated for the ordered material. If you actively use the consumption data, you must define a reference material. In this way, you prevent consumption data from incorrectly being updated for the header material.
  • If the production order contains several external processing operations that are to be carried out at different prices, you cannot assign any info records to the operations. In this case, you must maintain the purchasing data manually on the #External Processing# tab page.
  • The unit of measure of the externally processed operation must be the same as the base unit of measure of the material that is transferred to the purchase requisition.

General:

  • If a routing references a reference operation set, a material can only be adopted for these referenced operations in the resulting production order if no purchasing info record has been maintained in the reference operation set.
  • Not listed or excluded here are any consulting or modification notes that may exist which enable the realization of further functionalities.

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 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20080813 
SAP Release Created in 604