What does preprocessing job in archiving objects MM_EKKO & MM_EKPO does ?

[former_member674485]

Hi,

Hope you are doing well. Could you please let me know what exactly preprocessing jobs for archiving objects MM_EKKO and MM_EKPO does ? will it sets deletion flags ? And if yes, will that updates in log tables ?

Regards,

Anil.

[DominikTylczyn]

Hello aya743

Indeed it's archiving not authorization object - my bad, sorry, have already corrected.

You can branch to the MM_EKKO documentation by clicking on the button:

This will launch your web browser and display the following page of SAP Help: Archiving Purchasing Documents (MM-PUR)

Check out the section Variant Settings for Preprocessing MM_EKKO (MM-PUR). It provides a list of conditions that prevents deletion flag setting:

• The document could not be blocked.
• No additional check is active for the affected document category or document type
• An item is blocked.
• The delivery costs have not been cleared for an item.
• The blocked stock for an item is not 0.
• Down payments exist for an item.
• Parked invoices exist for an item.
• The GR quantity is not equal to the GI quantity.
• The GR quantity is not equal to the delivered quantity for an item.
• The GR quantity is less than the ordered quantity minus the underdelivery tolerance for an item.
• The “delivery completed” indicator has not been set for an item.
• The invoiced quantity is not equal to the GR quantity for an item.
• The invoiced quantity is less than the ordered quantity for an item.
• An item does not satisfy the criteria of the additional checks.
• Open rebate arrangements exist.
• The last PO history transaction/event for an item lies outside the tolerance.
• The date of the last release (call-off) for an item lies outside the tolerance.
• No quotation has been entered, or a quotation has not been rejected, or the deadline for submission of quotations has not expired for an item.

Best regards

Dominik Tylczynski

[DominikTylczyn]

Hello aya743

First, MM_EKPO is not an archiving object. MM_EKKO is one.

Preprocessing step of MM_EKKO runs RM06EV47 report. Although the report is not documented, the first lines of code gives an answer to your question:

*&---------------------------------------------------------------------
*& Report  RM06EV47                                                    *
*&                                                                     *
*&---------------------------------------------------------------------*
*& report sets LOEKZ for EKPO which is a prerequisite for archiving    *
*& for ekko-bstyp = 'A' a
*& for ekko-bstyp 'L' and 'K' customizing settings from T161Z is needed*
*&---------------------------------------------------------------------*

The report simply sets deletion flag EKPO-LOEKZ.

Refer to note 948493 - Residence time in new reports RM06EV47, RM06BV47 for details on how residence time is calculated.

Best regards

Dominik Tylczynski

[former_member674485]

Hi sir,

Firstly, thanks for your reply. I have mentioned it’s an archiving object, not authorisation object. Correct me if that can’t be called as archiving object.

I want to know whether deletion flag sets for line items of a incomplete PO ? Because we have an issue where deletion flag was set for few line items of in-completed PO’s. If we want to restrict that to only completed PO’s, Do you know any solution or fix for that ? Or any configurations ?

Awaiting for your reply.

Thanks,

Anil kumar.