Ansicht
Dokumentation

CRMS4_SOLO_SUBSC_MOD - BAdI: Modify Subscription Billing Data During Solution Order Orchestration

General Material Data   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

The Business Add-In (BAdI) CRMS4_SOLO_ORC_SB_SUBSC_MODIFY is used in the Solution Order(CRM-S4-SOL-SLO) component.

You can use this BAdI to copy custom fields from solution orders to the custom references field in follow-up subscriptions. The system calls the BAdI during orchestration or simulation of subscription billing items in solution orders. You can use this BAdI to modify the subscription data based on your requirements. You can change the custom reference and the bill split element fields at the subscription header and item level. You can also change the technical resources field at the subscription item level.

Solution order is integrated with SAP Subscription Billing.

• You can use the Custom Fieldsapp to create custom fields in solution orders. The app allows you to create custom fields for specific business contexts. The business contexts Service Headerand Service Itemare used to create custom fields for solution order.

• You can use the Adapt UI capability in solution orders to enable these custom fields in the solution order user interface. If required, you can map these custom fields in the solution order header or item to the subscription billing custom reference, bill split element, and technical resources fields.

To create a BAdI implementation, you can use the Custom Logicapp. When you use the Custom Logicapp, the following applies:

• The app provides a special ABAP language version ABAP for Key Users. This makes the implementation of the BAdIs for business experts and implementation consultants easier.

• The app ensures that you can use only released interfaces.

The following parameters are provided:

• BUSINESSSOLUTIONORDER: Contains the solution order ID that is being processed. Using the solution order ID, you can read other information (for example, partner information, appointments, and so on) about the solution order by querying the exposed CDS views. For example, you can query the CDS view I_ServiceDocumentEnhcd.

Note: The BAdI is called during orchestration or when a subscription simulation is triggered. When a business user creates a solution order and triggers the subscription item simulation, the solution order ID doesn’t exist until the solution order is saved. As the solution order ID is not generated yet, you cannot use this field to read from the database.

• BUSINESSSOLUTIONORDERITEM: Contains the solution order item ID that is currently being processed.

• SERVICEHEADER_EXTENSION: Contains information about the custom fields that are available for the Service Headerbusiness context.

• SERVICEITEM_EXTENSION: Contains information about the custom fields that are available for the Service Item business context.

• SUBSCRPNBILLGSUBSCRIPTION_IN: Contains information about the subscription used as a reference when modifying the subscription data in the BAdI.

• SUBSCRPNBILLGSUBSCRIPTION_OUT: Contains the fields that you can modify before creating a follow-up subscription or during simulation of a subscription billing item (for example, bill split element and customer reference).

Note: The data passed in this parameter (SUBSCRPNBILLGSUBSCRIPTION_OUT) should be correct as there is no additional validation. Subscriptions created in SAP Subscription Billing are based on the data retrieved from the parameter.

If you want to copy the custom field values from solution orders to the custom reference field in SAP Subscription Billing, you can follow the steps below:

• Create a custom reference field for the subscription document in SAP Subscription Billing.

• Create custom fields in SAP S4/HANA Cloud using the Custom Fieldsapp.

• Adapt the solution order user interface to enable these new custom fields in the solution order header or item (based on the requirement).

• Implement this BAdI.

CL_GUI_FRONTEND_SERVICES - Frontend Services   General Material Data  
This documentation is copyright by SAP AG.

Length: 4850 Date: 20240523 Time: 161429     sap01-206 ( 88 ms )