Delta Report (/sapapo/ccr) in the background

[Former Member]

Hi Gurus,

Is it possible to execute /sapapo/ccr in the background which also includes automatically executing iteration in the background?

I tried scheduling a job with /sapapo/cif_deltareport3 in the background, but it seems what it does is to only compare the data between the two systems. Is there a way that the iteration of the inconsistencies also be done in the background?

Thanks in advance!

[Former Member · Accepted solution]

Sabado,

Unfortunately, iteration is only done during display.

You can set the iteration indicator for a batch run, but that only means that the re-compare will be done when you call up the results for review.

It sounds like you are asking if the program can be made to re-compare the results an additional time, before saving. The standard program will not do this.

You can set the iteration flag in batch and save the results. When you then call up the results later, for review and action, this will have the effect that the iteration will be performed immediately prior to displaying the results. Typically, then, less errors will be displayed for your users to resolve. Time lag is typically insignificant.

The volume of temporary inconsistancies can be reduced by executing the reconciliation report during the periods of least data transfers between APO and its connected systems. Under these conditions, the requirement for iteration is reduced or eliminated.

http://help.sap.com/saphelp_scm2007/helpdata/en/8e/1ed0c5e6dc724ba0731545fc48e7be/frameset.htm

Regards,

DB49

[Former Member]

Hi Napoleon,

As you required, the delta report iteration cannot be done in background.

But what you can do is you can schedule that delta report in background, identify the errors and comeback from the initial screen and again run delta report only with error items and do the iteration.

For example, if you have 1000 items in your supply chain, if you run delta report in foreground, it consumes all resources and lot of time to give the output. Also you have to spend lot of time in monitoring to get the results followed by iteration. Instead, if you could schedule the job in background, later on you could see the results and put another delta job only with error items which will take very few minutes to display the results and subsequent iteration. This is the best practice which I have identified.

Hope this helps. Please confirm.

Thanks & Regards

R. Senthil Mareeswaran.