Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
MM-PUR (Application Component) Purchasing⤷
MMPUR_UI_MODEL (Package) Model Components for Web Dynpro Applications, Purchasing
IMG Activity
| ID | BADI_FEEDER_MATERIAL | BAdI for POWL Feeder Material |
| Transaction Code | S_AC0_52000851 | (empty) |
| Created on | 20050405 | |
| Customizing Attributes | BADI_FEEDER_MATERIAL | BAdI for POWL Feeder Material |
| Customizing Activity | BADI_FEEDER_MATERIAL | BAdI for POWL Feeder Material |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | BADI_FEEDER_MATERIAL |
Use
This Business Add-In (BAdI) is used in the component MM-PUR.
Enhancement spot: ES_BADI_MMPUR_UI_MODEL_FEEDER
The BAdI BADI_FEEDER_MATERIAL implements the interface IF_BADI_FEEDER_POWL and enables you to change the selection criteria, the detailed information, and the actions to be performed in the "personal object worklist" (POWL) for purchase orders.
The following methods are made available via the interface:
- GET_ACTIONS
Here you can define pushbuttons for your own additional actions. - GET_ACTION_CONF
If necessary, you can define confirmation messages for actions here. The action is then only performed if you have acknowledged the message with "YES". - GET_DETAIL_COMP
Here you can specify a Web DynPro detail component that is to be branched to when a POWL line is selected. - GET_FIELD_CATALOG
This method enables you to change the attributes of the fields of the standard field catalog. - GET_MAX_RESULTS
This method enables you to define the number of hits after which the search ends. This prevents the system from, for example, selecting all existing data records for an object and displaying them in the POWL. - GET_OBJECTS
This method makes available the objects that have already been selected as standard. If you have defined additional selection criteria, you can reselect the purchase orders here on the basis of these criteria. - GET_SELECTION_CRITERIA
Here you can define additional selection criteria or default values for the standard selection criteria. - HANDLE_ACTION
In this method, you define the portal follow-on operations for your additionally defined actions.
Requirements
If you define an action of your own, you must set up the business object that is to be navigated to and the operation that is to be performed on it in the portal.
If you specify a detail component, it must implement the interface POWL_DETAIL_COMP_IF.
Standard settings
The Business Add-In cannot be used multiple times.
The Business Add-In is not filter-dependent.
There is no default implementation and no example implementation. You can use the example CL_EXM_IM_BADI_FEEDER_VENDOR of the BAdI BADI_FEEDER_VENDOR, which realizes the vendor selection via CL_MMPUR_UI_FEEDER_VENDOR, as an example implementation.
Activities
To activate the Business Add-In, you must create an active implementation. To do this, choose the following path in the SAP Menu: Tools -> ABAP Workbench -> Utilities -> Business Add-Ins -> Implementation
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
Example
Business Attributes
| ASAP Roadmap ID | 153 | Design enhancements |
| Mandatory / Optional | 3 | Nonrequired 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_FEEDER_MATERIAL | 0 | HLA0006038 | Vendor-Material Relationships and Conditions |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20050405 |
| SAP Release Created in | 600 |
