Unblocking of Scheduling Agreements

[thomas_lu]

Dear Experts,

in context of a scheduling agreement, a customer has the requirement to edit Purchase Orders although the scheduling agreement is already blocked. Currently the scheduling agreement has to be manually unblocked to be able to edit the purchase orders. To avoid this I am looking for a simpler way e.g. only blocking the scheduling agreements "partially" so that the purchase orders can still be edited. Could you suggest a functioning work around or suggest a solutions?

Thanks in advance!

Best regards

Thomas

[Dennis_Suck85]

Hello Thomas, 

Basically, if you block a delivery schedule:
The entire scheduling agreement is blocked.
Call-offs (forecast delivery schedules, JIT delivery schedules) are prevented.
Subsequent processes (e.g. goods issue, delivery, billing) may also be blocked.
Order processing in the sense of Alteration of items or creation of call-offs is not permitted.

Unfortunately, it is also not possible to "partially" block the scheduling agreements in the public cloud.

Possible solutions:
Instead of blocking the scheduling agreement completely, you could:
- Use a separate status field (e.g. user status or release status.
- This is only used for information purposes, without activating the system lock.
- This would allow employees to recognize: "This plan is critical or under revision", but order call-offs are still possible.

Configurable logic: Business Rules (Custom Fields & Logic / BAdI)
If you have access to SAP BAdIs (Business Add-Ins) or Custom Logic, you can:
- Write an authorization or check rule (e.g. via "Custom Logic App")
- This checks: Is a certain release status set? → Only then allow retrieval.
Example: MM_PUR_SCHDL_AGRMNT_MODIFY BAdI - if available in your environment - allows control over scheduling agreement processing.

Documentation instead of blocking + process rule
 A purely organizational solution: Instead of setting a block, an internal process is used:
- E.g.E.g. a custom field "Editing restricted = YES"
- In combination with user training not to edit in critical phases.

Best regards 

Dennis