Ansicht
Dokumentation

CRM_FS_CP_CUST_I - BAdI: Change Proc. at Item - Changing of Customer-Specific Data Segement

CRM_FS_CP_CUST_I - BAdI: Change Proc. at Item - Changing of Customer-Specific Data Segement

BAL_S_LOG - Application Log: Log header data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the Quotation and Contract component (CRM-LAM-BTX-CTR).

You can use this BAdI to change the data segment for customer-specific fields at item level in the follow-up document. You use the following methods to do this:

  • BUILD_CUSTOMER_I: This method is mandatory. You use it to configure the customer-specific data segment for the follow-up document. To do this, you have to fill the change parameters CT_CUSTOMER_I_COM and CT_INPUT_FIELDS.
  • CHECK: This method is optional. You can use it to execute checks on the customer-specific fields. If errors occur, you must enter X for the export parameter EV_CHECK_NEGATIVE and display a message in the error log.

The BAdI is called from change process processing. The responsible developer must possess the following knowledge:

  • ABAP development
  • In-depth knowledge of the CRM business transaction data model
  • Experience in programming with the function module CRM_ORDER_MAINTAIN
  • Experience with the programming model for change processes
  • Experience with the relevant data model for the application (leasing, UBB, and so on)

No default or example implementation is provided for the BAdI.

The BAdI is not designed for multiple use.

The BAdI is dependent on filter values.

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.

The BAdI uses the interface IF_EX_CRM_FS_CP_CUST_I. For more information about the methods, display this interface in the Class Builder.






RFUMSV00 - Advance Return for Tax on Sales/Purchases   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 3972 Date: 20240523 Time: 174142     sap01-206 ( 58 ms )