cancel
Showing results for 
Search instead for 
Did you mean: 

Avoid reversal for previous value - ACDOCP

balosoy
Explorer
0 Kudos

Dear ACDOCP Experts,

We understand that when uploading to ACDOCP, data with the same characteristics within a scope will be deleted before new plan data is posted.

We would like to load planning data from a feeder system via oData API into ACDOCP. This feeder system delivers the data in several deliveries and these would have to be cumulated in the ACDOCP in each case. With the current settings, the existing data is deleted and replaced by new data.

To avoid this problem, we think that a field should be included in the scope that makes each delivery unique (e.g. something like timestamp).

Is there a standard SAP field that we can use for this? This field would then have to be linked to a field from the feeder system so that each booking is unique and is no longer overwritten.

Many thanks for your help!

OwenLiu
Product and Topic Expert
Product and Topic Expert
0 Kudos

We helped you to accept the answer, since there were no updates after 7 days.

You can unaccept it anytime if you have further questions.

Accepted Solutions (1)

Accepted Solutions (1)

Susanne_Helbig
Product and Topic Expert
Product and Topic Expert
0 Kudos

Dear balosoy,

if you need to load the data in several steps then the data must be logically disjoint.

Depending on your data this can be, for example, Fiscal Year or Company Code, or a combination this.

Can you please explain why the data is loaded in several steps into ACDOCP?

Thanks and best regards
Susanne

balosoy
Explorer
0 Kudos

Dear susannehelbig

Thank you for your answer

The feeder systems receive their input data from different sources at different times. Consequently, the feeder system sends the data with the same characteristics (same scope) to the ACOCOP at different times but always with the same characteristics (company code, year, plan category, etc.) This feeder system also delivers the ACTUAL data to the ACDOCA and is configured for continuous delivery. Thus, the expectation is that the delivered data is accumulated and not overwritten.

Is there a way to adapt the interface (oData API) so that the data deliveries are posted supplementary?

Best regards,

Mehmet

Susanne_Helbig
Product and Topic Expert
Product and Topic Expert
0 Kudos

Dear balosoy,

What I understood so far is the following:

Plan data is entered in different systems, at different times for the same scope, e.g.
Today:
CCtr01 - Acct01 - Period01 - Year2024 - $100
Tomorrow:
CCtr01 - Acct01 - Period01 - Year2024 - $50
Next week:
CCtr01 - Acct01 - Period01 - Year2024 - $75

and in the end you want to see the following data in ACDOCP:
CCtr01 - Acct01 - Period01 - Year2024 - $225

Is my understanding correct?

I'm still not clear about your business case, can you please give some more details about your process?

Best regards
Susanne

balosoy
Explorer
0 Kudos

Dear susannehelbig

Exactly, your understandig is correct.

Best regards

Mehmet

Susanne_Helbig
Product and Topic Expert
Product and Topic Expert
0 Kudos

Thanks for your confirmation.

But I'm still not clear about your business case, can you please give some more details about your process?

Best regards
Susanne

Susanne_Helbig
Product and Topic Expert
Product and Topic Expert
0 Kudos

Dear balosoy,

I would need some more details regarding your planning process to answer your question properly.

For details regarding adding custom fields to your planning content, please follow the instructions in the SAP Help portal:

Best regards
Susanne

Answers (0)