Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
MM-PUR (Application Component) Purchasing⤷
MECR (Package) Plug-In Enhancements in Purchasing for CRM
IMG Activity
| ID | CRM_SRV_LOG_BADI_GR | Business Add-In: Item Grouping |
| Transaction Code | S_XBE_58000009 | (empty) |
| Created on | 20030711 | |
| Customizing Attributes | CRM_SRV_LOG_BADI_GR | BAdI: Grouping of Items for Purchase Orders |
| Customizing Activity | CRM_SRV_LOG_BADI_GR | BAdI: Item Grouping |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMGCRM_SRV_BADI_GR |
Use
This Business Add-In (BAdI) is used in the context of logistics integration between SAP CRM and SAP R/3.
It controls whether all purchase order items of a service order or in-house repair in a document (reservation, purchase requisition, or purchase order) are collected or are distributed to several documents.
Note
This BAdI is available to you as of SAP CRM 4.0 Add-On for Service Industries.
Requirements
This function is only available to you if you have selected Group Type: Ind. Grouping (BADI) in the IMG activity Grouping of Items for the corresponding business object type.
Standard settings
This Business Add-In is not active in the standard system. Default coding is executed automatically.
The Business Add-In is not designed for multiple use.
The Business Add-In is not dependent on a filter. The filter is the business object type of the document.
The active implementations CRM_SRV_GROUP_PO_STD, CRM_SRV_GROUP_PR_STD, and CRM_SRV_GROUP_RS_STD are delivered externally.
The logic for the procurement logistic scenarios is as follows:
- Reservation
If the logistics scenario is a reservation, Customizing of the IMG activity: Establish Controlling Type, Controlling Level, and Controlling Scenarios is read.
- If the Controlling level is set to transaction in Customizing for the corresponding CRM transaction type, a collective document is created.
- If the Controlling level is set to item in Customizing for the corresponding CRM transaction type, a single document is created.
- Purchase Requisition
If the logistics scenario is a purchase requisition, a collective document is created.
- Purchase Order
If the logistics scenario is a purchase order, the items are grouped depending on the source of supply.
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:
- 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. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- 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.
- Save your entries and assign the Add-In to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the
method <Interface Name>~<Name of Method>.andendmethod.statements. - 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: - Choose Activate.
When the application program is executed, the code you created is run through.
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 |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20030814 |
| SAP Release Created in | 2003_1_470 |
