No suitable purchasing documents found?

I came across an issue where a scheduling agreement approver, trying to use ME35L, wasn’t able to find the document he had to approve. The standard message ME 260 ‘No suitable purchasing documents found’ greeted him.

I realized that it must have been a case where the purchasing document got skipped because of missing authorization. One way of checking this is to run SU53 after the message.

To get more clarity on the way it works, I went into the source code of ME35L and found that there are three authorization objects that get checked.

For scheduling agreements (document category L)
M_LPET_EKG
M_LPET_LPA
M_LPET_EKO

For purchase orders (document category F)
M_BEST_EKG
M_BEST_LPA
M_LPET_EKO

For RFQs (document category A)
M_ANFR_EKG
M_ANFR_LPA
M_ANFR_EKO

For contracts (document category K)
M_RAHM_EKG
M_RAHM_LPA
M_RAHM_EKO

ID ‘ACTVT’ FIELD ’02’ – activity for change
ID ‘EKGRP’ FIELD xekko-ekgrp (means purchasing group)

As it turned out, someone had changed the roles and things went haywire from there 🙂

Also, I learnt that in order to know the authorization objects to be checked in an application, just search for the keyword AUTHORITY-CHECK OBJECT

Leave a comment