bcquality/microsoft/knowledge/scm/carry-out-requisition-actions-through-the-standard-workflow.md

bc-version	domain	keywords	technologies	countries	application-area
all	scm	requisition-line action-message accept-action-message req-wksh-make-order carryoutbatchaction demand-order-no planning-flexibility	al	w1	all

Carry out requisition actions through the standard workflow

Description

A requisition/planning line is a pending change to a supply/demand network, not just a template for a purchase line. Carry-out interprets New, change-quantity, reschedule, and cancel actions, preserves referenced supply and planning flexibility, and moves reservation/tracking ownership before finalizing the proposal. Creating a plausible purchase order and deleting the requisition line can leave new supply unrelated to the demand that caused it.

Best Practice

For requisition batch carry-out, initialize "Req. Wksh.-Make Order" with Set and invoke CarryOutBatchAction on the intended accepted lines. Supply the order/posting/receipt defaults separately from the ending-order-date cutoff, and preserve the selected worksheet/batch/line filters. A plain Run or a single order-line insertion helper is not a replacement for this batch initialization and finalization.

Use the standard "Carry Out Action" dispatch for broader planning output and its configured purchase, transfer, assembly, or manufacturing choices. Do not turn every action into a new purchase order, bypass source-specific reservation transfer, or delete proposals before the owning workflow has completed their supply change.

Ordinary manual purchase creation that does not consume planning output is outside this rule. Users may reject or delete unwanted proposals without creating supply; temporary planning simulations, pre-carry-out enrichment, and engine-owned cleanup are also legitimate. Delete(true) on a requisition line is not intrinsically a defect.

The samples select an existing accepted New/Purchase item proposal with sales-demand context. Dates are explicit, the source selection remains bounded, and the clean sample leaves order creation and reservation handoff to the standard workflow; it is not a complete planning-run generator.

Anti Pattern

Report code that consumes accepted persistent "Requisition Line" action messages, manually creates or changes supply from a subset of fields, and then deletes or marks the proposal handled without the standard carry-out/source-reservation handoff. Running purchase-field validation and the requisition delete trigger does not first move the proposal's demand links to the new purchase line.

Require both proposal-consumption intent and a visible supply conversion. Do not flag an isolated deletion of an unwanted suggestion, an ordinary purchase-order API, or the standard carry-out engine's own insert/delete sequence.

Samples

• carry-out-requisition-actions-through-the-standard-workflow.bad.al
• carry-out-requisition-actions-through-the-standard-workflow.good.al

References

• Perform planning action messages
• Planning functionality
• Reservation, order tracking, and action messaging
• BaseApp carry-out caller and date defaults
• Batch initialization and selection
• Reservation handoff before supply finalization