Edit Manual Revenue Recognition Data for Sales Document Item

[ashuklacplus]

Hello,

We are looking for BO information around the Edit Manual Revenue Recognition Data --> Edit Percentage of Completion available under Cost and Revenue work center in Sales Document Items view.

Today, there is no function to extract the data on this screen and/or to do mass upload of multiple Sales Document Items:

1. Plan Revenue
2. Plan Revenue for Project
3. Estimated Project Costs
4. Estimated Costs
5. Manual PoC
6. Calculated PoC
7. Last PoC Used
8. Last PoC reference date used manual-poc-data.png

We as a partner are looking to build a custom solution which can publish the existing data for Sales Document Items with 108 - Cost to Cost Project PoC accrual method assigned and also upload the following data set to ByDesign for selected Sales Document Items

1. Plan Revenue
2. Estimated Costs
3. Manual PoC with Valid From, Valid To and Percentage

Could someone from SAP Product Team tell us which BO contains this information and whether partner can read and write the data set of not?

Thanks, Ankur SHUKLA

[caroline_lost · Accepted solution]

Hi Ankur,

the BO for the manual Revenue Recognition data is FIA_FAV_SLS_SRV_DOC.

Business Object Details (taken from Cloud Application Studio Repository Explorer):

Name: FinancialAccountingViewOfSalesAndServiceDocument

Namespace: http://sap.com/xi/AP/FinancialAccounting/Global

Deployment Unit: Financials

Process Component: FinancialAccountingMasterDataManagement

Object Category: Business Transaction Document

Technical Category: Standard Business Object

Object Type Code: 531

UI Text: Copy of Sales and Service Document for Accounting.

This BO is released for Partner Solutions.

I know that it is possible to edit the manual data for sales document items with accrual method 'Recognize based on manual amounts'. I am unsure if it can be achieved to edit the POC.

I hope this helps.

Kind regards,

Caroline

[ashuklacplus · Accepted solution]

Hello Caroline,

Thanks a lot for sharing the details; we found the BO node and it's Item node where the information related to manual POC is maintained but in the OData editor the create and update function is not allowed, but create and update at header level is allowed.

Do you know, if the Items level nodes could be allowed for create and update function?

Thanks,

Ankur

[caroline_lost · Accepted solution]

Hi Ankur,

I'll check this for you and get back soon.

Thanks,

Caroline

[ashuklacplus · Accepted solution]

odata-access-issue.pngThanks for your support on this topic Caroline!

If it helps, I'm attaching the screenshot comparing what has been mentioned in the BO Documentation vs what we get in the OData Editor when we add the same BO and it's Node Item.

And we are also following up this issue on the Incident with External Reference ID 740354/2020.

Thanks and regards,

Ankur

[ashuklacplus · Accepted solution]

Hi caroline.lost, I hope you are well!

Have you had a chance to check and confirm about the discrepancy reported on the OData access elements?

Thanks,

Ankur

[caroline_lost]

Hi Ankur,

the problem in terms of the data manipulation via the ODATA editor, for Sales Order items using the accrual method 108-Recognize using cost-to-cost project POC, is that all costs and revenues are bundled in one Leading Sales Order item. But, to store the pricing total amount or the manual values that you can maintain in the Edit Manual POC screen, an internal, only project-based item is used. The Edit manual POC screen is based only on this internal item - An indicator for this is that the Sales Oder item specification is initial here.

It might be possible to release further attributes of this BO, even on item level. However, any such change will never result in a change on the actual Sales Order Item level..

We have therefore created a BADI, BADI_FIA_SLSL_ACCR_POC_PLAN ( Get Plan Value for Sales Accruals POC Calculation ) which, we think, can help you best to achieve what you are looking for.

Please check this option with your development team.

Thanks so much and kind regards,

Caroline