0PM_ORDER loading time too long

[Former Member]

Hi All. We have about 600 000 PM orders in the system. Loading the master data attributes for this into BW/BI takes almost an hour. There seems to be no delta load available. Most of this running time is on ECC6. I cannot restrict the orders in the info package because there are orders created a long time ago which are still active.

Any suggestions?

Thanks,

Johan Loock

[Former Member · Accepted solution]

We have just under 600,000. After perfroming a full load of all Orders, what we did to deal with 0PM_ORDER load times was to use the ABAP Conversion exit on the Infopackage's Data Selection tab. The datasource contains Created On(ERDAT) and Change(AEDAT) dates and we rely on those dates to filter the Orders we extract.

We load two Infopackages (full loads) each day, one that loads any Orders created in the last 7 days and another that loads any Orders changed in the last 7 days.

ABAP conversion exit code for created in last 7 days -

data: l_low_date like sy-datum,

l_idx like sy-tabix.

read table l_t_range with key

fieldname = 'ERDAT'.

l_idx = sy-tabix.

l_low_date = sy-datum - 6.

l_t_range-option = 'BT'.

l_t_range-low = l_low_date.

l_t_range-high = sy-datum.

modify l_t_range index l_idx.

p_subrc = 0.

The Changed code is the same, but it references AEDAT.

The load times for the Created and Changed Infopackages are about 1 - 2 minutes each.

[Former Member]

Thanks Pizzaman , that solved the problem.

It would be nice though if SAP can provide us with a Delta load.

Anybody at SAP listening?

Regards,

Johan Loock

[Former Member]

Hi,

are there any user exits to be processed while extraction? May you have some inperformant coding in there. Additionally you might need to check the source table. As it is the same table as for pp, cs.. orders you might face an issue with a index or with database statistics for the table.

regards

Siggi