Kontakt

Ansicht
Dokumentation

CRM_SRV_LOG_BADI_GR - Business Add-In: Item Grouping

CRM_SRV_LOG_BADI_GR - Business Add-In: Item Grouping

CL_GUI_FRONTEND_SERVICES - Frontend Services   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the context of logistics integration between SAP CRM and SAP S/4HANA.

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.

This BAdI is available to you as of SAP CRM 4.0 Add-On for Service Industries.

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.

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.

After you have called the IMG activity, proceed as follows:

  1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.
If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.
  1. In the corresponding field, enter a short text for implementation .
  2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
  3. Choose the tab Interface.
The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.
If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.
  1. Save your entries and assign a package.
  2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
  3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
  4. Save and activate your coding, and navigate back to the screen Change Implementation.
  5. Save on the screen Change Implementation.
Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.
  1. Choose Activate.
When the application program is executed, the coding you have created will be run.






CPI1466 during Backup   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 4410 Date: 20240523 Time: 180947     sap01-206 ( 56 ms )