Table EKKO-LOEKZ Delete Indicator can't be changed once set

[Former Member]

Hi Gurus:

We ran Archive Object MM_EKKO Preprocessing Program RM06EV70. This set the deletion indicator EKKO-LOEKZ to an 'L' on 2008 Purchase Orders. It was discovered that around 100 really can't be archived. On this Forum we were told that SAP Tcode MEMASSPO can change LOEKZ back to blank. Our SCM Team tried that but we get error messages that the PO can't be changed and that Purchasing document 6200000617 already archived.

Does anyone know what we are doing wrong or another way to set LOEKZ back to blank?

Thank you

Dennis

[JL23 · Accepted solution]

Please tell the full story.

if the Preprocessing Program RM06EV70 sets the L in EKKO-LOEKZ, then this document CAN be archived. so why should 100 not be able to be archived while they have the L ?

[Former Member]

Hi Jurgen:

I use Tcode MEMASSPO.

I select fields on Purchase Order Header. I select the deletion indicator MASSEKKO-LOEKZ on the list.

I enter a PO Number with an 'L' in the LOEKZ field from the preprocessor.

I change the new value field to blank on the PO Header. I hit the mass change button. The 'L' is changed to a blank.

I hit the save icon. I get all of the following errors.

6200000617 : Instance 6200000617 of object type PurchaseOrder could not be changed

6200000617 : Instance 6200000617 of object type PurchaseOrder could not be changed

6200000617 : Purchasing document 6200000617 already archived.

If we do this for a PO that was not set to a 'L' by the preproessor program. We can change it to using MEMASSPO to 'L' (SAP Changes it to 'C' and we can blank it out again.

I don't think there is anyway to get MEMASSPO to change the PO. Any ideas?

[JL23]

SAP is comparing the field BEDAT from EKKO and EIPA table.

and if EKKO-BEDAT is higher than EIPA-BEDAT, then this archiving message ME615 is issued as well.

can you check how the values for this BEDAT field are in EKKO and EIPA table in your system?

[Former Member]

Jurgen:

I looked at the BEDAT field from EKKO and EIPA. There is no PO in the EIPA Table for the PO I was testing. In addition. the MEMASSPO never hits a BEDAT message ME615. It looks like MEMASSPO will not be able to change preprocessor loekz set flag of 'L'.

[JL23]

had you read the OSS Note 688856 - BAPI_PO_CHANGE: EKKO-LOEKZ not changeable

SAP is explaining there that this field is unchangable in certain releases because of a program error.

this not does not just have the Z-report that was mentioned by Ariane, it has as well the program fixes. After you applied this note, you should be able to do it with MEMASSPO as desired.

[Former Member]

Jurgen:

We had looked at that OSS Note mention 688856. We are at currently at SAP_APPL of 60407. Note 688856 is for SAP_APPL of 470 or 500. We didn't think it would apply anymore to ECC 6.

Dennis

[JL23]

maybe the error is back and SAP does not know yet.

log an incident yourself at SAP.

[Former Member]

Jurgen:

Thank you for your help. We will ask SAP about it.

Dennis

[Former Member]

Hello Dennis,

You should do it with BAPI_PO_CHANGE. In the standard system there is no way to mass change the LOEKZ. A report should be written to cover this functionality.

Please review the information provide in the following Link:/people/arminda.jack/blog/2010/03/03/why-can-certain-fields-not-be-changed-using-memasspo-or-which-fields-can-be-changed

There you can see that the LOEKZ can not be changed with the MEMASSPO.You can also see this in note 417067.

Report Z_RESET_EKKO_LOEKZ (note 688856) should only be used for POs that have been incorrectly set for deletion. This report is not intended to be used for all POs.

Regards,

[JL23]

Hello Ariane,

MEMASSPO was (maybe still is in many machines) a batch input program, but there is an OSS note that describes how to change it from batch input to BAPI .

And the BAPI has an own exclusion list in function module ME_LIMIT_FIELDS_PO_BAPI where this EKKO-LOEKZ is not excluded.

Hence so many people here already use this BAPI to delete POs at header level. SEarch the forum with key word EKKO-LOEKZ or "deletion at header level" .

I really wonder about the reason behind this "feature" that only creates inconsistencies.

The exclusion list in the fuction module will already prevent the field from appearing in MEMASSPO, so if DennisDK1 can enter values into this field, then this means for me that he has already the BAPI version of MEMASSPO and it should update as expected.

[JL23]

this was OSS note: 545754 to change MEMASSPO from batch input to BAPI method

[Former Member]

Hi:

Yes around 100 of our PO's that the pre-processing program set for archiving, were later discovered to need to be updated in order to give the customer the money we owed them. With the LOEKZ deletion indicator set, these PO's can't be updated. We are looking for an SAP way to clear our the deletion indicator (LOEKZ) back to a blank. After that, we can update the PO's with the correct information. Does anyone know how to blank out LOEKZ? We tried using MEMASSPO but it wouldn't change it because of the LOEKZ field being an 'L'. MEMASSPO says the POs are already archived and can't be changed.

Dennis

[JL23]

I know that it could be removed using MEMASSPO, as I tried it myself before I advised this solution and I got the feedback that it worked for the person who had asked as well.

Can you describe in a bit detail what you do in MEMASSPO, so that I can imagine what you do as I do not see your screen