2LIS_03_BX setup table run taking too long

[Former Member]

Hi Gurus,

I am filling the setup table for the 2LIS_03_BX using the tcode MCNB. I am running the jobs in parallel by giving the selection plant wise.

I have divided them into 6, 7 parallel jobs. But it still it takes few hours to complete! It takes 4, 5 hours to complete.

So how can i speed up the setup table fill?

BR,

Shreesh.

[Former Member]

Hello Shreesh,

The setup table activity does takes time/. Probably you are running 7-8 jibs in parallel that's why there is effect on the performance.

Try going with 3 jos in parallel with smaller selection to check if the reason for this time is hige volume of data. Downtime is required for setup table activity.

Regards,
Amit

[Former Member]

Hi Amit/Sander, Taking downtime in such cases is impossible. That too when the setup job for BX runs for 3, 4 hours and then for BR it will run min 2, 3 hours. In such a scenario, in no industry, they will agree to lock the users for such a long time. Its simply impossible.

I verymuch understand the imp of taking the downtime and have discussed with our IT management, but simply they wont agree to keep system down for even a small time.

I dont know how others work with this inventory cube 0IC_C03. 

BR,

Shreesh.

[former_member185132]

Hi Shreesh,

Taking downtime for 2LIS_03_BX is absolutely essential. If you do not take downtime and if users are carrying out goods movements while BX is being setup, the data that reaches BW will certainly be inaccurate and cannot be corrected. Considering this, if business wants accurate data then they have to accept a downtime for BX. There isn't any alternative.

We did minimize the downtime though by the below process:

1. Carry out BF setup for previous years and periods (no downtime needed as long as you take closed periods). The majority of BF will be covered by this. Also load the setup data into the PSA layer
2. Begin downtime
3. Setup of BX - will take 3-4 hrs
4. Simultaneously setup BF for current period. - will take less time as the data is small
5. End downtime
6. Load BX and BF to PSA
7. Rest of the process is as normal

With this you can manage it in 3-4 hours.

Regards,

Suhas

[sander_vanwilligen]

Hi Shreesh,

Unfortunately, you will need some downtime if you follow the classic approach (i.e. 2LIS_03_BX for stock initialization, 2LIS_03_BF for goods movements and 2LIS_03_UM for revaluations). Otherwise you cannot guarantee the data integrity.

There are however certainly ways to minimize it. Please see SAP Note 753654 - How can downtime be reduced for setup table update. You can dramatically reduce the downtime to distinguish between closed and open periods. The closed periods can be updated retrospectively.

If the company can accept small differences during one day, then you might consider to skip the downtime. You should then choose a time-window in which the postings are as minimal as possible. Some corrections of double records might be necessary. You can find some tips in the document , e.g. how to determine a window with minimal or no updates.

However, for stock initialization using 2LIS_03_BX downtime is crucial for reliable figures. You cannot work here with open and closed periods. You can only reduce the data selection (e.g. skip irrelevant plants, do not transfer zero stocks).

As mentioned in the above document it should not be very time-consuming since no document items from the MSEG table are read. Instead it reads from smaller tables like MARC and MARD. I really wonder why it takes so long in your case (maybe too many parallel processes? - see my comment of Dec. 28). I advice to investigate further on this issue.

Last but not least, you might want to have a look at the following SAP Notes:

• SAP Note 436393 - Performance improvement for filling the setup tables;
• SAP Note 602260 - Procedure for reconstructing data for BW.

Best regards,

Sander

[Former Member]

Hello Shreesh,

As already mentioned by others, downtime is essential for setup table activity. Only then you can have correct data in BW, because setup tables filling is done in ECC box which is the OLTP system recording the transactions/postings, so a downtime is required so that no postings are happening in the system while you prepare to load data 1st time in BW

But once the setup tables are filled for BX and you have done INIT without data transfer, you can unlock the users and perform FULL LOAD

You can also decrease the downtime by clearing the delta queues prior to downtime, so that during downtime less no of records are in delta queue.

Also run the whole activity in Quality system to now and understand what all challenges you may come across in Production.

Regards,

Amit

[sander_vanwilligen]

Hi Shreesh,

As a general advice be careful with activating the option "Zero stock to be transferred". This option will increase the runtime considerably.

Please also review the following SAP Notes:

• SAP Note 655798 - No values with stock key figures (0IC_C03, for example);
• SAP Note 728360 - PLUG: Performance of stock initialization;
• SAP Note 823951 - Consistency check of non-cumulative InfoCubes.

Best regards,

Sander

[Former Member]

Hi Sanders, I have surely not selected Zero stk to be transferred, Also I have only 32 materials to be transfered. Also I have split the job into 8, 9 parallel jobs, by gining selection over materials.

Still few jobs are running since more than 3 hrs.

Also I have followed those notes. any other way out?

BR,

Shreesh.

[sander_vanwilligen]

Hi Shreesh,

I have only three suggestions left:

• Try out different selections as suggested in SAP Note 728360 (solution 1);
• Monitor the system (e.g. using t/code ST05 - SQL trace) to detect possible bottlenecks;
• Let the basis administrators check the technical infrastructure and give an advice on the maximum no. of parallel processes.

The first and second action you can already execute in another system (e.g. Quality) to prepare for the real production initialization.

Best regards,

Sander

[KodandaPani_KV]

Hi,

All jobs run in the background process i think it will take for the filling of set up tables because of the huge data.

for us also it take 2 or 3 hours.

Thanks,

Phani.

[Former Member]

Hi phani, then did you take a downtime of 3 hours? or lock users for such along time?

BR,

Shreesh.

[Former Member]

I have selected only valuated stocks option. & num of data recs per LUW as 5000.