Skip to content

DESCRIPTION.md

Latest commit

 

History

History
37 lines (29 loc) · 2.38 KB

DESCRIPTION.md

File metadata and controls

37 lines (29 loc) · 2.38 KB

MSC Plan Order Upload - Case Study & Technical Analysis

Executive Summary

The MSC Plan Order Upload is a powerful tool that allows planners to "action" the recommendations from the ASCP plan in bulk. Instead of manually clicking "Release" on hundreds of planned orders in the Planner's Workbench, users can download the recommendations to Excel, review/modify them, and upload the release actions back to Oracle.

Business Challenge

The "Planner's Workbench" UI can be slow and cumbersome for mass updates.

  • Mass Release: "I have 500 planned orders for next week. I want to release them all to Purchasing at once."
  • Modifications: "I need to change the dates on 50 orders before releasing them. Doing this one by one takes hours."
  • Review Process: "I want to review the plan in Excel, filter for my suppliers, and then mark the ones I approve for release."

Solution

The MSC Plan Order Upload bridges the gap between analysis (Excel) and execution (Oracle).

Key Features:

  • Action Support: Supports "Release", "Reschedule In", and "Reschedule Out" actions.
  • Modification: Allows users to change the Implement Date and Implement Quantity before releasing.
  • Auto-Release: Can be configured to automatically set the release status for all downloaded rows.

Technical Architecture

The tool uses a WebADI-style upload mechanism to update the plan tables.

Key Tables and Views

  • MSC_SUPPLIES: The table storing the planned orders.
  • MSC_SYSTEM_ITEMS: Item validation.
  • MSC_PLAN_ORGANIZATIONS: Plan context.

Core Logic

  1. Download: Retrieves Planned Orders based on criteria (Plan, Org, Planner).
  2. User Action: The user updates the "Update Release Status" column (e.g., to 'Release') and optionally modifies dates/quantities.
  3. Upload: The tool updates the corresponding records in MSC_SUPPLIES with the new status and values.
  4. Execution: A subsequent concurrent request (in Oracle) processes these marked records and generates the actual WIP Jobs or Purchase Requisitions.

Business Impact

  • Productivity: Reduces the time spent on administrative tasks (releasing orders) by 90%.
  • Accuracy: Reduces manual data entry errors during the release process.
  • Control: Gives planners a familiar environment (Excel) to review and approve the plan before execution.