DSO Activation Issue

[Former Member]

Hi Community,

We have a issue where the DSO activation, there is a huge time gap of 2 hrs between Start of activation and the actual execution of the data packets. Below is the screen shot of the time.....

We have huge volume of data to load and activate... this delay of 2 hrs will impact the delivery.

Can anyone tell me what is causing this delay in this processing.....?

Thanks,

Ashok.

[Former Member]

Hello Ashok,

From your log, it is quite clear that longer time is taken not for DSO Activation but while checking the over-lapping area for archiving in the GWFDARDT table.

I suppose this archiving has been carried out recently and there is a lot of data archived.

So what might be happening is that all the new records are being checked against the old time range for which data has been archived. While comparing the data is too huge to load and compare which is accounting for long time.

If this archiving is carried with business permission, inform them that delay will happen

What I would suggest here is to reduce the archiving time period to reduce the overlapping checking time taken by system.A compromise has to be found for archived data duration to provide delivery in time.

Br,

Arpit

[Former Member]

Hi,

If the flow is in 7x then you can check the packet size of the DTP. Check what is the maximum limit that can be given in a DTP to load the huge amount of Data.

Also check the ABAP code either in the start routine or end routine, check with an ABAPer for code optimisation so that the loading is improved .

Regards

Vilas Kamath

[former_member182343]

HI,

It depends various reasons:

- Resource availability.

- Check the previous activation job time of same DSO. If it taking same time as previous, it good.

If it have difference with previous activation the you need to analyse.

- If you are testing in Dev system. Then try with write optimized DSO and make sure you want deltas or not.

- rvc

[Former Member]

Hi,

check resource availability , may be the reason for delay,

You can ask BASIS team to check table space also.

Regards,

Anand Mehrotra.

[Former Member]

Hi Ashok,

The time difference in the job log (nearly 2hrs in your case) doesn't always mean a delay. If you check the job status at application server level(http://scn.sap.com/docs/DOC-25323), you will find the updates done. So you can wait for the job to complete if its progressing at the server level.

Hope this helps

Regards

Sai