Ansicht
Dokumentation

BADI_050 - Business Add-In for Warranty Search and Warranty Check

General Data in Customer Master   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

This Business Add-In enables customer-specific enhancements for warranty determination and the warranty check. Two methods are available:

• Method CRM_WTY_SEARCH_OBJECTS

This method is called in the CRM_WTY_MGNT_SEARCH function module to read the warranties for the refererence object. The Business Add-In returns information about the links between warranties and installed base components.

As input for the warranty determination, the method receives all of the function module import parameters and the warranties already determined for the reference object in the CRM standard system. In the function module, you can restrict or extend the number of warranties determined in the CRM standard system.

• Method CRM_WTY_CHECK

This method is called in the CRM_WTY_MGNT_CHECK function module to check the warranties. The Business Add-In returns information about links between warranties and installed base components.

The method receives all of the function module import parameters as input for the warranty check. In the function module, you can code the entire warranty determination and warranty check to meet your requirements.

The warranty check in the CRM standard system can be deactivated if you activate the EV_NO_STANDARD_CHECK parameter in the method.

You have activated the warranty check in the CRM standard system. This means you have assigned a profile for the warranty check to the service-specific business transaction type (service order, service confirmation, complaint). For more information, see Define Profile for Warranty Check.

The warranty check is started when you make changes to the item data or in the header data for the reference object. Firstly the CRM_WTY_MGNT_CHECK function module is called. If a reference object exists, the CRM_WTY_MGNT_SEARCH function module is then called.

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.

Fill RESBD Structure from EBP Component Structure   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 4221 Date: 20240524 Time: 011658     sap01-206 ( 80 ms )