Billing Split issue solution order management

[alexbeer]

Hi folks, 

we are exploring the scope item #4GT Solution order management and are facing a billing split of the

• service item and
• sales item

The situation is displayed within the attached screenshots. 

• the customer reference of the solution order has not been copied to sales order
• trying to bill service item and delivery item results in a billing split -  split analysis please find attached. 
  
  

What is the designated way to bill the solution order items together within one billing document?
Do we have to implement Cloud BAdI SD_BIL_DATA_TRANSFER to align the header fields between billing request and delivery document?

Best regards

Alex

[RACHID_AITBOUALE]

This is a common challenge with the #4GT scope item, @alexbeer! The split occurs because the "integration seams" between the Service BDR and the Sales Delivery don't share identical header fields like Customer Reference or Assignment by default.

To resolve this without breaking your Clean Core, you should indeed use the Cloud BAdI SD_BIL_DATA_TRANSFER. This allows you to programmatically align the header fields (like VBRK-BSTNK) so the system perceives them as a single logical transaction.

For long-term governance, I recommend using SAP Cloud ALM to document this custom logic and validating it with Tricentis Tosca to ensure that future S/4HANA upgrades don't revert your header alignment and re-introduce the splits.

[alexbeer]

Dear @RACHID_AITBOUALE,
I appreciate your comment and the confirmation of our solution idea regarding the Cloud BAdI.
To the readers: Please keep in mind, that the table VBRK is NOT accesible within this BAdI.
We have to handle structures like BIL_DOC_RES and BIL_DOC_CLEAR_FLDS_F_SPLIT. In addition the split analysis overview in app "Create Billing" does not display the technical names of the fields raising the split. The Solution Order is a great improvement - but splitting items within the billing document which have been held together within the order is a pity.
Keep you posted as soon as we have implemented a suitable solution.

Kind regards Alex