Filling the Inventory Setup Tables

[Former Member]

We are carrying out a dry run to fill up the inventory setup tables.

Filling MC03BF0SETUP takes more than 3 days. When we move to production and carry out the actual fill we will not have this amount of time to have the R3 production system offline. What is the best approach to handle such a scenario. For example can we break the fill over two weekends and if not why not and if so what are the potential areas of concern if any? Thanks

[Former Member · Accepted solution]

This is an idea. You can divide initialization in several pieces, first you can initialize last periods with productive off-line (less time to initialize a couple of periods) after that initialize closed past periods in which no posting can be done with system online.

[Former Member · Accepted solution]

That is a great idea. So just to clarify

I fill my 2LIS_03_BF setup table as follows:

1) When R3 system is down load the data for say Posting Date 01.01.2006 - 31.12.2006

2) If the Posting date is before that period the fill can be carried out whilst the system is online if necessary

Does it not make a difference if I load the most recent records prior to records which were posted earlier?

Eric,

Running parallel processes to the same setup table did not encounter any locks?

Message was edited by: Niten Shah

[Former Member · Accepted solution]

Yes, first initialize offline from 01.01.2006 to 31.12.9999. After that initialize online the previous periods, because they are closed and no posting can be done in them.

If you initialitaons are not underlied there is no problem with loads.

[Former Member · Accepted solution]

Never had a lock issue.

You are running with non-overlapping selections remember.

Regards,

Eric

[Former Member]

Niten,

You can run parallel setup jobs to break it down into smaller chunks. But talk to your functional and make sure that there can be no retro-active postings to earlier periods either online or thru batch utilities. Otherwise, you will miss some data. Also, run the setup in the batch mode for better utilization of the resources.

Abdul

[Former Member]

Try running several setup jobs in parallel for non-overlapping selections. It should reduce your setup window significantly.

I recently completed a setup using 5 parallel jobs for 5 consecutive years. Running one job for the 5 years takes quite a while longer.

Regards,

Eric

[Former Member]

Hi,

You can absolutely break up the initializations over a period of time using selective initializations. Also, if possible, you don't need to wait for the weekends, if you can break them up into even smaller chunks, you can also do that during off hours, or during windows when there is no to minimal user activity.

Cheers,

Kedar