cancel
Showing results for 
Search instead for 
Did you mean: 

Delta failure of Inventory (Urgent Production Issue)

Former Member
0 Kudos
141

Hello Every one,

we have a delta load for Inventory 2lis_03_bf,

Where due to Inventory Auditing in R/3 they stopped Inventory related transaction with out any notice, Where due to background scheduling the delta with zero records was loaded with red light(load failed).

Where I'm trying to do Repeat delta but it is taking to Initialization ....

how can i continue the delta

Please through light on this production issue(urgent)

Regards

Sandy

View Entire Topic
Former Member
0 Kudos

Hi Sandy,

please describe with more detail....

As far as I understand.

- all inventory postings transactions (Material movements) have been stopped in source system.

- your delta loads being scheduled periodically, you ended with a delta of 0 records because no posting were done anymore.

What do you mean by "it is taking to initialization"??

- Check in R3/RSA7 that your 03_BF (and eventually 03_UM) are initialized. You can also check this from BW/InfoPackage menu scheduler/ init options.

- What is the EXACT error message of your 0 record delta load?

- in R/3 check in SMQ1 if you have any LUW for MCEX03 application as well as for your delta queues BW<CLNT>2LIS_03_BF resp UM).

let us know,

Olivier.

Former Member
0 Kudos

Dear Mr Olivier Cora,

As far as your understanding it is rite,

<i>What do you mean by "it is taking to initialization"??</i>

when i am opening the Infopackage of BF to schedule repeat again, the Update type is set to initialization.

In R/3/RSA7 the BF and UM are generating the delta with XXX records

In BW/InfoPackage menu scheduler/ init options...their is nothing to select....

The exact error of 0record delta

error massage : Start Infopackage ZPAK_******(same)

In R/3 SMQ1 --->

LUW for MCEX03 application have 321

2LIS_03_BF have 532

UM have442

Regards

Sandy

Former Member
0 Kudos

Hi,

but why are you reqesting an update of initialization again?

Is your red request posted into datatargets or only sitting in the PSA?

- if yes then delete this request from all datatargets where it is posted.

and then

execute an InfoPackage with update = delta. The system should prompt asking if you want to repeat the detal. Acknowledge by click on repeat.

let us know

Olivier.

Message was edited by:

Olivier Cora

Former Member
0 Kudos

Dear Mr Olivier Cora,

U r correct , i had deleted the red request from the data targets...where my issue was, the Infopackage which is Delta load pervious was changed to Initialization...

when we double click the Infopackage to schedule it is giving a message as below

<b>There is no active delta initialization for this

IS/QS/DATA source</b>

and if we enter to the Infopackage the Update is converting to Init

How to load delta ?

Regards

Sandy

Former Member
0 Kudos

Hi Sandy,

in your previous post you are telling that 2LIS_03_BF has 532 LUWs so this means that the delta is initialized; check again in RSA7 if you see one entrey for 2LIS_03_BF for your BW client.

let us know,

Olivier.

Former Member
0 Kudos

Dear Olivier cora,

<b>In R/3/RSA7 the 2LIS_03_BF has total 538 now,</b>

<i>But in BW if i am going to Same InfoPackage it is showing the massage before getting in InfoPackage where Update was changed to Init</i>

this is what i was confused

Please conform me wheather in source system delta is generating are init is generating?

where this load is carrying from 3years...

Please through some light

Regards

Sandy

Former Member
0 Kudos

Hi,

you first need to initialize to delta prior to be able to load deltas. Once you have your Datasource delta initilaized, the system will record any changes relevant for your datasource (these changes you are seing in SMQ1 MC03... and delta Q in RSA7).

Now, your delta is already initialized since you have pending LUWs in R/3.

The issue is that your last delta request has records and is in error status.

Therefore I repeat again:

1. delete this request from all datatargets where it is posted.

2. leave its QM status to RED: this is very important because if you change the QM status to GREEN, the next time you'll fire a delta load, R/3 will send you the next delta and you will perhaps miss data. Leaving it RED and requesting the next delta load will end with a repeat of the delta;

3. open your IPack, change the update to delta and execute it; you should get a prompt to confirm the request of the repeat; acknowledge. With this repeat you are sure to not miss any data.

As you are saying, the delta is running since 3 years; if for whatever reason you miss records in a delta; you'll have to reinit this datasource via the filling of the SETUP tables (LO extractors work like this)... This procedure is very expensive...

hope this helps...

Olivier.