LO cockpit - SD Billing setup-initialization performance

[vikram_kate]

Hi,

We are planning for initialization of SD - billing data (2LIS_13_VDHDR & 2LIS_13_VDITM). We have almost 30 millions of records in VBRP table. Client requires data for last 3 years which is still more than 15 million records.

For performing SD Billing setup in ECC (OLI9BW) we have 3 fields for selection - Company Code, Sales Org & Billing Document. (No idea why Billing date is not provided along with it?? )

As about 95% data comes from 1 Company Code+ Sales Org, we are not able to use these fields for parallel setup jobs. And for billing documents, customer is using customized document number range depending on the Location/Year/doc type logic, which is also impossible to use for doing setup.

Without any selections, it takes around 3 days to complete the setup, and it is impossible to take downtime on ECC for 3 days for this activity.

Is there any other way by which we can reduce the total setup time & ultimately downtime required for setup/initialization?

Or is there any possibility to use Billing date in the the selections for setup?

Request you guys to help if anyone has performed setup in such scenario,

Thanks,

Vikram.

[Former Member · Accepted solution]

check which program is used to fill the setup table (let's call it "setup table filler")

then write an ABAP that makes your selection the way you want (e.g. billing date), convert to billing documents (ideally in range format) and call the "setup table filler" with these billing documents

should work

[former_member188011]

Hi Vikram:

Take a look at the alternatives below.

Note 753654 - "How can downtime be reduced for setup table update"

"How to... Minimize Downtime For Delta Initialization"

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/5d51aa90-0201-0010-749e-d6b993c7a...

"SAP NetWeaver 7.0 BI: How Tou2026 Minimize the Reporting Downtime during the initial data load", blog by Michael Hoerisch.

/people/community.user/blog/2007/09/23/sap-netweaver-70-bi-how-to133-minimize-the-reporting-downtime-during-the-initial-data-load

Regards,

Francisco Milán.

[vikram_kate]

Issue resolved,

I will be performing following steps -

First change the existing data flow to have an DSO in between.

(Datasource VDITM/VDHDR --> DSO --> Infocube)

1. Delete setup table and delta/extraction queue.

2. Execute Init without Delta infopackge from BI for VDHDR/VDITM -> This will mark delta pointer in ECC for the datasource.

3. Run the setup jobs (divide entire document range in about 5 sets and schedule parallely)

4. After completion of setup, execute Full repair infopackage with last 3 years selection.

5. Update data from PSA

5. Then Schedule jobs to send data from LBWQ to Delta Queue in LBWE.

6. Schedule Delta infopackage

7. Schedule DTPs in BI accordingly

• While setup job is running there may be some documents which will be in Setup table and LBWQ as well, but as I have introduced DSO in between it will take care of these duplicate data.

Thanks,

Vikram.