ROCANCEL field in R3 extraction program can't catch the LOEKZ (deletion ind

[Former Member]

Why the ROCANCEL field in R3 extraction program can't catch the LOEKZ (deletion indicator) value in EKPO for some item (not all item) deletions in a purchasing doc?

We deleted some purchasing document items on R3, e.g.,

doc 1

item 1 deleted

item 2

item 3

item 4 deleted

item 5

doc 2

item 1 deleted

item 2 deleted

Run RSA3 on the datasource 2LIS_02_ITM, find the extraction program field ROCANCEL(Indicator: Cancel Data Record) for doc1 are all null for each doc1 item that this field ROCANCEL fails to catch EKPO deletion indicator field LOEKZ value for these two deleted item 1 and item 4 showed in table EKPO with value of 'L' for item 1 and item 4.

However this extraction program field ROCANCEL does catches the correct values for doc2 though. Sounds like if all the doc items get deleted then ROCANCEL shows correct value 'R', if only deleting some items of a doc, then ROCANCEL doesn't indicate the deletion!

Any idea? We have searched OSS Notes, but find something which are only for BW other than for R3. The problem starts at R3 extraction program!

Thanks

Message was edited by: Kevin Smith

[edwin_harpino]

hi Kevin,

i almost 'miss' your reply since you did it with 'edit'.

consult with your basis if correction is applicable, you can use SNOTE to apply correction, but i think it should our basis friend's job.

hope this helps.

[Former Member]

hi AHP,

Our BASIS has applied OSS Note 886716, but the field ROCANCEL in extraction program when running RSA3 still fails to catch the Deletion Indicator values!

Seems no help!

[Former Member]

Hello Kevin,

I am facing the same problem Can you Kindly update me on this How you have solved your problem ?

KK

[Former Member]

hi AHP,

There is sth wrong with the website that I can't see the Reply button next to your post.

I check the System Status on our R3, it lists quite a few below:

Software Comp. Release Level

SAP_BASIS 620 0051

SAP_ABA 620 0051

SAP_APPL 470 0024

SAP_HR 470 0046

EA-IPPE 110 0019

PI 2003_1_470 0009

PI_BASIS 2003_1_620 0007

EA-APPL 110 0020

BTW, I checked the OSS Note 886716, find the 4th tab called "Correction Instructions" contains the following lines below. Which line should we use in our system?

Correction Instruction Valid from Valid to Installation Soft. Component ID

Ref. Correction Modification Status Last Changed on

0000419802 600 600 0120031469 SAP_APPL 1

P7DK006929 Released 07.10.2005 07:43:39

0000420067 500 500 0120031469 SAP_APPL 1

P6DK060509 Released 09.10.2005 22:50:11

0000420068 470 470 0120031469 SAP_APPL 1

P6BK206659 Released 09.10.2005 23:02:38

0000420253 46C 46C 0120031469 SAP_APPL 1

P9CK458509 Released 10.10.2005 00:33:01

Download

Thanks

Message was edited by: Kevin Smith

hi AHP,

I run se38 to check the form XMCEKPO_ERGAENZEN_LIS_NEW, but find it doesn't exist at all in our R3 system!

Thanks

[edwin_harpino]

hi Kevin,

...

<b>SAP_APPL 470 0024</b>

<b>SAP_HR 470 0046</b>

EA-IPPE 110 0019

<b>PI 2003_1_470 0009</b>

...

so you r/3 should be 4.7 one,

try to check the correction mentioned

4.7

https://websmp202.sap-ag.de/~form/handler?_APP=00200682500000000733&_EVENT=CORR_OBLI&_CINSTA=0120031...

compare the code with existing in your system.

hope this helps.

[edwin_harpino]

hi Kevin,

should oss note there, we had the same problem.

check 886716 ?

correction is done in r/3

what's your r/3 version ?

4.6c

https://websmp202.sap-ag.de/~form/handler?_APP=00200682500000000733&_EVENT=CORR_OBLI&_CINSTA=0120031...

4.7

https://websmp202.sap-ag.de/~form/handler?_APP=00200682500000000733&_EVENT=CORR_OBLI&_CINSTA=0120031...

5.0

https://websmp202.sap-ag.de/~form/handler?_APP=00200682500000000733&_EVENT=CORR_OBLI&_CINSTA=0120031...

6.0

https://websmp202.sap-ag.de/~form/handler?_APP=00200682500000000733&_EVENT=CORR_OBLI&_CINSTA=0120031...