SAP ABAP IMG Activity BADI_MM_PRIO_ORG (BAdI: Determination of the Org. Priority During Requirement Prioritization)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ MM (Application Component) Materials Management
     ⤷ MM_PRIO (Package) DFPS: Retrofit Requirement Prioritization
IMG Activity
ID BADI_MM_PRIO_ORG BAdI: Determination of the Org. Priority During Requirement Prioritization  
Transaction Code S_PCO_36000460   (empty) 
Created on 20050618    
Customizing Attributes BADI_MM_PRIO_ORG   Determination of the Organizational Priority During Reqmt Prioritization 
Customizing Activity BADI_MM_PRIO_ORG   BAdI: Determination of the Org. Priority During Requirement Prioritization 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BADI_MM_PRIO_ORG    

Use

This Business Add-In (BAdI) is used in the Materials Management (MM) component.

During requirement prioritization, this BAdI enables you to determine the organizational priority in accordance with your own criteria.

The default implementation determines the organizational priority on the basis of the plant/storage location combination of the relevant document item. You can use this BAdI to define the organizational priority on the basis of other document data (fields at header and item level). These methods enable you to define the organizational priority in the purchasing and reservation process as well as during material requirements planning.

In your BAdI implementation, you can, for example, evaluate a separate Customizing table in which you assign specific document types or item categories to the organizational priorities. Create the class for your BAdI method implementation as a subclass of class CL_DEFIMP_BADI_MM_PRIO_ORG (default implementation), that is, so that the class you created inherits from CL_DEFIMP_BADI_MM_PRIO_ORG.

The BAdI is called when the organizational priority is determined.

Requirements

Standard settings

In the standard system, the BAdI is active. A default code exists. The BAdI is not filter dependent or intended for multiple use.

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.

Example

See also

Methods

Interface
Determination of the Organizational Priority

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   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 BADI_MM_PRIO_ORG 0 HLA0009510 Materials Management 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20050619 
SAP Release Created in 600