Ansicht
Dokumentation

CRMV_UBB_CHNG1 - Assign Change Process IDs to Transaction Category

CRMV_UBB_CHNG1 - Assign Change Process IDs to Transaction Category

BAL Application Log Documentation   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

In this Dialog Structure, you define a key for each contract change process and then assign one of the following transaction categories to that key as the leading transaction category:

  • BUS2000112 for change processes for Service Contracts at header level
  • BUS2000137 for change processes for Service ContractItems
  • BUS2000252 for change processes for Usage-Based Service Contract Items
  • BUS2000250 for change processes for Usage-Based Single Pool Contracts and Usage-Based Aggregate Contracts at header level
  • BUS2000251 for change processes for Usage-Based Single Pool Contract Items and Usage-Based Aggregate Contract Items

If entry fields are necessary for the change process, set the Input Req. indicator. If you create your own change process for which the Input Req. indicator is set, you must create your own configuration for component CRM_UBB_CHANGE for view CRM_UBB_CHANGE/Input.

If you want to define a change process as a mass change process, set the Mass Change indicator. Mass changes are only possible for BUS2000112.

Note for custom-defined change processes:

  • You must assign the change process key that you defined there to the key you created in this activity, using the field Change Process.

In the BAdI Implementation, in the field Implementing Class, enter CL_IM_CRM_UBB_CP_H for change processes at header level and CL_IM_CRM_UBB_CP_I for change processes at item level.
  • If you want to define your own change process, create it in this Customizing activity, but leave the Change Process field blank. Then, you must create your own implementation with your own Implementing Class in BAdI: Change Process, and then enter the filter you defined there in field Contract Change Process.

If change processes should be executable for contracts at header level or item level, you must assign all the desired change processes to the corresponding transaction types in this Dialog Structure.






ROGBILLS - Synchronize billing plans   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 3536 Date: 20240523 Time: 175110     sap01-206 ( 52 ms )