Drag and Drop Question A company uses Dynamics 365 Business Central. The accounting manager wants partially shipped and invoiced sales orders that will not be fulfilled to not be displayed on the…

Question

Exhibit

Answer Area

Explanation

Explanation: Closing Partially Fulfilled Sales Orders in Business Central

The Goal

Remove partially shipped/invoiced sales orders from the active Open Sales Orders list, while preserving a historical record for reporting ordered vs. delivered quantities.

Why This Order? - Step-by-Step Breakdown

Step 1: Archive Invoiced Sales Orders in Sales & Receivables Setup

This is a system-level prerequisite and must come first. The Delete Invoiced Sales Orders job will archive orders before deleting them - but only if archiving is already enabled. If you run the delete job first and enable archiving afterward, those deleted orders are gone permanently. No archive = no reporting. This setting unlocks all the reporting capability the scenario requires.

Common mistake: Enabling this after deletion and wondering why no archive records exist.

Step 2: Change the sales order status to Released

The orders are likely in Open status after partial shipment. Releasing the order confirms it to the warehouse/inventory subsystem. In BC, reducing unshipped quantities on a Released order properly clears outstanding warehouse entries and reservations tied to the unfulfilled lines. Doing the quantity reduction while Open may leave dangling warehouse commitments.

Common mistake: Assuming you should skip this because you think you need Open status to edit - but BC allows quantity reduction on Released orders specifically for unshipped lines.

Step 3: Reduce the sales order quantity to match the shipped quantity

This is the core action. The Delete Invoiced Sales Orders job only deletes orders where:

Qty Ordered = Qty Shipped = Qty Invoiced

A partially shipped order has remaining unshipped quantity, so the job skips it. Reducing the ordered quantity to match what was already shipped and invoiced makes the order appear fully fulfilled to the system, making it eligible for deletion.

Common mistake: Running the delete job without this step and wondering why orders still appear on the list.

Step 4: Set the status of sales orders to Open

The Delete Invoiced Sales Orders batch job only processes orders with status = Open. Released orders are invisible to it. After reducing the quantity, you must reopen the order so the delete job can find and process it.

Common mistake: Leaving orders in Released status and running the delete job - nothing gets deleted.

Step 5: Run the Delete Invoiced Sales Orders job

Now all conditions are satisfied:

• Archiving is ON (Step 1)
• Qty Ordered = Qty Invoiced (Step 3)
• Status = Open (Step 4)

The job archives the order first (creating the record available for reporting), then deletes the live order (removing it from the Open Sales Orders list). Both requirements of the scenario are fulfilled.

Common mistake: Thinking "delete" means the data is lost - when archiving is enabled, the delete job creates the archive as part of the deletion process.

Summary of the Logic Chain

The sequence is a strict dependency chain - each step enables the next. Archiving must be configured before deletion; quantity must be reduced before deletion; Open status must be set before deletion; and deletion is the final act.

No community discussion yet for this question.