Delta extraction of modified data in already closed periods

[Former Member]

Hi everyone,

we're currently facing a scenario where data in BI does not seem to match R/3. We're using the business content extractors 0ec_pca_3 & 0ec_pca_4 to get data for a balance sheet report, but some of the figures don't match. The client currently uses periods 001 - 013, in other words they have one special period. After much investigation and discussions with the users, we found out that the client sometimes goes back and makes changes to periods that have already been closed. For instance, period 013.2007 is closed in R/3 (and loaded to BI), at some point in 2008 the client "reopens" the period and modifies the data. This data does not seem to be picked up by the BI delta extractor. So our theory is that the two systems don't balance because of this late period modification. My questions are:

Is it part of standard SAP FI process to re-open an already closed period and add/change/delete data?

If so, would this changes be picked up by the standard delta extraction? If not why and is there anything we can do to achieve this?

If not part of standard process, what would the solution be? We've suggested to potentially create a separate period, say period 014, for these changes? Would this be a recommended way forward?

Thanks for your time.

Cheers,

Dion

[Former Member · Accepted solution]

0EC_PCA_4 does not support delta right?

Have you already checked contraints mentioned in these links?

http://help.sap.com/saphelp_nw70/helpdata/EN/5d/ac7d8082a27b438b026495593821b1/frameset.htm

Can a full load for the missing records be tried?

Also look at Note 577644

[Former Member · Accepted solution]

Hi,

we did a full load over the weekend and managed to get all the records. But we're still unsure if lets say for instance the customer now goes in and changes something in an already closed period. Will these changes be added to the delta queue for the next load or will the extractor ignore them as the period is closed?

I've looked through the documentation, the constraints themselves are not the problem. We've also looked at the sap notes.

Cheers,

Dion