cancel
Showing results for 
Search instead for 
Did you mean: 

How to distinguish PO item deleted manually to PO item archived ?

former_member644785
Participant
0 Kudos

Hello MM experts,

We're testing the archiving on PO and we are very surprise to see that PO items archived are identified by a trush icon.

So it's not easy to distinguish  PO item deleted manually to PO item archived.

Is there a way to  change the icon for the archiving ? 

Thank you very much for your suggestion.

Regards,

Nicolas

Accepted Solutions (0)

Answers (2)

Answers (2)

BijayKumarBarik
Active Contributor
0 Kudos

Hi,

This difference you can find with table CDHDR with PO number where manual deletion with business user ID only and archiving deletion with a separate user with a specific user type.

Regards,

Biju K

JL23
Active Contributor
0 Kudos

Technically the icon just depends on the indicator at the field EKPO-LOEKZ, and this indicator is equal for a manual deletion and a deletion from the archiving run.

The only difference is that manual deletions have change history while there is no change history in the PO when the deletion indicator was set from the archiving jobs.

If you really want show a different icon then it requires a modification based on the result from reading the change history which may even influence the performance.

former_member644785
Participant
0 Kudos

OK thank very much for your answer

We've found also that if some PO items can't  be archived, the PO is not archived but the deletion icon is displayed for the items that could be archived.

Is this a normal way?

Thank you for your help.

Regards,

Nicolas

JL23
Active Contributor
0 Kudos

Setting the deletion indicator is a prerequisite for archiving, and this is done with the pre-run of purchase order archiving.

All items which can be archived get a deletion indicator, if one item cannot get this deletion indicator then the spool file will have the reason.

If all items have got a deletion indicator but the PO did not get archived, then this is because the time between residence time 1 and residence time 2 was not over when you started the write job. And this is normal.