PO release strategy at item level

[toniolie]

Hello Guys!

We are facing a situation here, which is quite demanding.

We were asked to develop a release strategy for a purchase order, at item level.

We know that there is no standard way for this, but it is the requirement we are having.

Once this request won't be backed down, we must develop something to attend this matter.

The aim of this questions is to verify other understandings and point of views, and possible ways to attend this demand.

NOTE: It is mandatory to develop something, somehow, to have a release strategy at PO item level.

Release strategy inputs:

- Whenever the field on PO "Requested by" is filled with some specific users, this item must have release strategy.

- PO must not be sent while the status of these release strategy is "pending approval".

- If the approval is denied and no other item has a "pending approval", PO can be sent omitting the items which didn't get an approval.

We had a couple ideas, all of which are very demanding and would require a kinda big development.

For example, one of them would be:

1. Create a field on ME21N, with 3 (or more) possible values.

- Blank = approved

- PD = pending approval

- RJ = approval rejected

2. When saving the purchase order, on ME21N:

2.1. System should somehow verify if there is any value on this new field, for each PO item.

2.2 If no match is found, system can proceed with the standard procedure for PO print out.

3. If at least one match is found, system should NOT send the PO.

3.1. If the value on "requested by" return no matches in comparison to a list of requestor (inputted in some table, sm30), value on the new field must be BLANK.

3.2. If the value on "requested by" matches a list of requestors, value on this new field must be PD.

3.2.1. In this case, the ITEM would have to be approved in some Z tcode.

4. If the item was approved, value on the new field must be set to BLANK.

4.1 System should verify if there are other items with approval pending (value PD on new field), for this PO.

4.1.1. If there are not, system should proceed to print out the PO.

4.1.2. If there are, system should NOT print out the PO.

5. If the item was rejected, value on the new field must be set to RJ.

Very summarized, this would be a way we thought to solve this situation.

If anyone else have other ideas to implement it, we'd be glad to hear.

Thank you.

Best regards,

Estevão Tonioli.

[former_member186746]

Hi,

It is a daunting task, one which you can only conceive by developing a custom workflow where you use something other than classification to control when to approve the entire PO with which release code.

Kind regards, Rob Dielemans

[ankurch]

Yes, it is not possible in the standard, but you can cover your requirement by maintaining release procedure with out classification for the purchase requisition.