Release strategy: User should release only with his highest release code

[Former Member]

Hello,

Because of personel absences we want to configure the release strategy so that:

User A or user B releases in the normal case the first level of a PO (with release code 01).

User C (Manager) releases after release code 01 with release code 02.

User A is deputy of user C. In this case user B will release with code 01 and user A will release with code 02.

Because user A can use depending of the case release code 01 or 02 (C deputy) it must be avoided that user B sets release code 01 and 02 for the same purchase order.

Do you know about a solution for this issue

Br

Manuel

[Former Member]

Dear Manuel,

From your scenario, it seems that A can replace C and A have authorization of release code 01 and 02, from your scenario i think if you give B authoriazation for release code 01 only, that he''ll never can release with release code 02 for any PO document

So you can achive this scenario with user Authorization, the authorization object M_EINK_FRG.

Regards,

w1n

[Former Member]

Thank you for your response.

For B i think it is all OK.

What is not clear for me is the constellation for A:

A can release only for relese code 01, when A, B and C are present.

A can release only for relese code 02, when A and B are present and C abscent. In the last case A cannot release for 01 and 02 (e.g. to accelerate the process because B is present but not reachable). ALWAYS 2 different persons MUST be involved in the release strategy.

Do you have some idea how to ensure this?

Br

Manuel

[Former Member]

Dear Manuel,

But the system dont know which person is present or not.

I think you can create another release code to act as their present , and then assign it to related person that need to approve during the unpresent of the other person.

regards,

w1n

[Former Member]

Dear W1N,

But the systems knows that A released with code 01 and when A tries to release with code 02 the system knows that the same person of release code 01 is trying with release code 02.

<b>The aim is to avoid the second release from the same person and not to automate the release strategy.</b>

In such a case A has to cancel the release for code 01 (ME28) and wait until B is reachable to do the release of code 01.

When C is absent A knows that his task is to release code 02.

Is this check really not possible?

Best regards

Manuel

[Former Member]

Dear Manuel,

I think ,The release procedure is not design to track the same person that release the document with same release code, it can be limit by release code, but in your case the release code is the same for more than 1 person.

yes there's history change, but there's no standard check in release procedure for this function to check until user id.

You need to customize it.

Or you can add a new release code just to define it as a substitute release and then if something goes wrong(one person release a document that he not supposed to ), then you can track it by the substitute release code.