Setup tables doubt

[guillermo_m]

Hello gurus!

I have the 2LIS_12_VCITM datasource activated and working fine since 1 year ago. That time I filled the setup tables for the company 0001. Now I need to fill the setup table for the company 0002. Do I need to fill the setup tables again for the to companies or I can fill the setup tables for the company 0002? If I could do this, the first initialization (company 0001) will continue working well?

Thanks in advance.

Regards.

[Former Member · Accepted solution]

Hi,

You can fill the setup tables based on company codes with transaction OLI8BW for deliveries (better with sales document) before delete the setup table data.

Thanks

Edited by: satya prasad on Apr 23, 2010 9:08 AM

[guillermo_m · Accepted solution]

I don't get clear if I should delete the setup tables. Or if I can fill the company 0002 without deleting the setup tables (previously filled with data of company 0001).

Thanks again.

[former_member186445 · Accepted solution]

assuming you keep your current delta for 0001 running, you'll do a new init only for 0002. this means that you can leave the data in the setup tables if you are sure that you have never loaded 0002 data in the setup table. however from a performance point of view, you're better of deleting first the content of the setup table as having less records in the table will improve the extraction time.

anyway data that is currently in the setup table is useless...

M.

[Former Member · Accepted solution]

Hi,

For an application if volume of records are more we use to create variants and fill set-up table parallely for different selection. In your case 0001 is already filled.You can fill the set-up table for 0002 without deleting set-up table. (since only 0001 data is there already)

Before that check the delta queue in RSA7 and LBWQ. In RSA7, if there are delta records for any of the 2LIS_12* data sources clear the queue (till LUW ='0').

Then fill it.

[guillermo_m · Accepted solution]

Thanks a lot for all your help!

I'm assuming that if I fill the setup table for company 0002 then I need to create a new Infopackage in BW for the new init. delta for 0002 because I have one with the initialization done for company 0001. So I will use to delta infopackage (one for company 0001 and another for company 0002), is it right?

If finally I choose to delete all the setup table and make a new fill for both companies... Could I run two paralelly jobs (one for company 0001 and another for company 0002) to improve the time of the fills? If I do this, could I use one infopackage only for initialization of both companies?

Thanks again!

[former_member186445 · Accepted solution]

you need to created a second init infopackage for your 0002 init, but the delta package will automatically pick up the new init, so you don't have to create a second delta infopackage (which is not permitted by the system anyway). so once the second delta init is succesfull, check your delta package and you'll see that a sel criteria on 0002 will have automatically been added.

if you want to fill setup tables for both comp codes (after deleting the contents ofcourse) you can indeed run the two jobs in parallel. however if you put the "block documents" flag (for production) you can do this only in one of the two jobs else you'll have a dump; you need to put the flag on the job that is foreseen to run the longest

M.

[Former Member · Accepted solution]

Hi,

1. If you are going to fill the set-up table without deletion, no need to initialize., trigger a repair full load it will bring all records in set-up table (both 0001 and 0002). Make sure no company selection in infopackage.

No need to create infopackage for delta also., You can continue with existing delta infopackage.

2. If you decide to delete set-up table. Fill the set-up tables using variants (var1 for 0001 and var2 for 0002) parallely.

No need to do anything with initialization,let the delta pointer not disturbed. You can schedule repair full load. and then continue with delta.

[desgallagher]

Hello Pepe,

It is a better option to delete the data from the setup table first before filling it with the new selections so you don't get duplicate data, please read the SAP note 602260 where the filling of the setup tables is discussed in detail and also the common problems that can occur in this area.

Best Regards,

Des

[Former Member]

Filling setup tables for Delivery data source is not based on company. You may fill the setup tables based on the delivery doc nos.

In you scenario,if company 002 is newly created, data for the corresponding will be capture automatically in the delta extraction.

If i'm not right, pl eloborate the issue or doubt.

Guru

[Pravender]

You can fill setup table for any condition but first delete the exisitng data from the setup table using LBWG --> Application code 12. If you will not delete it then there may be a chance of duplicate records if the data already exists in setup table.

There is no relation of this with the delta initialization.