3543349 - Revenue Recognition Error: Deep merging is not supported

The revenue recognition run finishes with the error message "Doc. item XYZ/XX: Deep merging is not supported." m(XYZ/XX refers to a sales order item ID XYZ-XX)

SAP Business ByDesign

1. In the Cost and Revenue work center go to the Revenue Recognition run.
2. Execute a revenue recognition run for sales order XYZ (XYZ refers a sales order ID). 
3. It finishes with the error "Doc. item XYZ/XX: Deep merging is not supported."

Sales order item XYZ-XX uses accrual method 108 - Recognize using cost-to-cost project POC. 

When using accrual method 108, all fix-price sales order items are bundled into one, the leading, sales order item, here XYZ-XX. 
To bundle and merge all project values, an internal, only project-based item is generated as well. 
So, for each project and all the connected fix-price sales order items there is always only one leading sales order item and only one internal item. 
Sometimes, usually because of accrual method changes and when sales order items are created at different times, not one internal item but two internal items are generated, connected to different sales order items, causing the Deep-Merging-not-supported-error. 

The internal item can be found in the backend.

But you can also find it in the Manual Revenue Recognition data of any of the fix-price sales order items connected to the associated customer project: 

1. In the Sales Document Items view find, for example, item XYZ-XX.
2. Press Edit Manual Revenue Recognition Data and choose Percentage of Completion.
3. In the new screen you should see only one line per set of books, for which accrual method 108 is used, showing now sales order item assignment. SO if there are two set of books assigned to your company, there should be only two empty sales order item lines. 
4. If there are more than one empty line per set of books, the data is inconsistent. 

Send a case to Technical Support with the permission to correct the inconsistency from the backend: 

To correct the inconsistency we
1. change the accrual method of all fix price items in the user interface (UI), connected to the affected project. 
2. In the backend we then remove all internal items. 
3. After,  we reassign accrual method 108 back to all fix-price items. 
4. Finally, we verify, in the UI as well as from the backend that only one internal item is generated for the project. 

Once corrected, the deep merging error will no longer appear. 

2860171 - Revenue Recognition Run Errors for fix-price Sales Order Items: Use one merge item with code 'replace basic data' only

2845657 - Revenue Recognition Run Error for Fix-Price Sales Order Items Without Accrual Method 108 - Recognize using cost-to-cost project POC

2479036 - Revenue Recognition Run Error - Doc. item: Only Doc. Items of the Same Profit Center can be Merged

Deep Merging, 108 - Recognize using cost-to-cost project POC, revenue recognition error , KBA , SRD-FIN-COR , Cost & Revenue , Problem