Upload
doliem
View
216
Download
2
Embed Size (px)
Citation preview
ORDER MANAGEMENT
201
OSB ERP
September 2016
2
1. Dates & Scheduling
2. Workflow & Statuses
3. Deliveries & Trips
4. Processing Constraints
AGENDA
3
HIGH LEVEL ORDER FLOW
DEPOT DIRECT & HOME DELIVERY
Order String from Customer
• Customer
• PO #
• Ship-to
• RDD
• Qty, Items
• Store #
• Etc.
Isolation Tier Logic
• Home Delivery specific logic
• Generate Tracking #
• Combine PO’s onto one order (OEM Sep)
Isolation Tier SOA Table
SOA Order Staging Table
Order Pre-Processor
• Defaulting rules
• Sales agreement
• Derive Ship Method
Oracle Order Import
• Order Corrections
Oracle EBS
• Order Holds
• Order Booking
DATES & SCHEDULING
5
DATE DESCRIPTION HEADER
OR LINE EDITABLE DEFAULT
IMPACTS
SCHEDULING
CREATION DATE System date when the record
was initially saved BOTH NO SYSDATE NO
UPDATE DATE System date when the record
was last changed BOTH NO SYSDATE NO
ORDER DATE When the order should be
recorded HEADER YES SYSDATE NO
REQUEST DATE When the customer wants the
order to be fulfilled BOTH YES N/A YES
LATEST
ACCEPTABLE DATE LINE NO CALCULATION YES
KEY ORDER DATES
6
HOW DATES AFFECT SCHEDULING (1)
REQ LAD SAD SAD
ATP
EXAMPLE: Request Date Type = Arrival
The scheduling engine (ATP) attempts to schedule so that the Schedule Arrival Date matches the Request
Date (REQ). If the Schedule Arrival Date (SAD) is before the Latest Acceptable Date (LAD) then
scheduling is successful, and Schedule Ship Date (SSD) is calculated.
SSD
SSD = SAD - Transit
7
HOW DATES AFFECT SCHEDULING (2)
REQ LAD SSD
EXAMPLE: Request Date Type = Ship
The scheduling engine (ATP) attempts to schedule so that the Schedule Ship Date matches the Request
Date (REQ). If the Schedule Ship Date (SSD) is before the Latest Acceptable Date (LAD) then scheduling
is successful, and Schedule Arrival Date (SAD) is calculated.
SAD = SSD + Transit
SAD
ATP
SSD
8
• If ATP is Overridden on the order, then the Scheduled Date (Ship or Arrival,
depending on the Request Date Type) can be explicitly set on the order.
• Override ATP authority must be granted to the user responsibility in order for the
user to be able to perform the Override ATP action.
• If ATP has already been overridden on an order, the user needs the Override ATP
authority to make any changes that could impact scheduling.
• All electronic Home Delivery orders will come into Oracle EBS with Override ATP
already selected. This is because we have already communicated and/or agreed to a
delivery date to the consumer upstream, and Oracle EBS must honor this date going
forward.
OVERRIDING ATP
WORKFLOW & STATUSES
10
• The order headers and order lines in Order
Management have distinct workflows to control the
sequence of events that occur during the processing
of orders and returns.
• These workflow events and the related statuses are
visible on the screen, and through a tool called the
workflow monitor.
• Many statuses are moved through very quickly in the
system, so users will see them much less frequently.
The program to progress the workflows runs about
every 2 minutes in Production, and multiple steps can
be executed simultaneously.
WORKFLOWS Header Statuses
Entered
Booked
Closed
Cancelled
Common Line Statuses
Awaiting Fulfillment
Awaiting Invoice Interface
Awaiting Return
Awaiting Shipping
Customer Accepted
Fulfilled
Invoice Interface - Complete
Pending Customer Acceptance
Picked
Picked Partial
Released to Warehouse
Returned
Supply Eligible
Supply Open
Supply Partial
11
WORKFLOW DIAGRAMS
Entered Booked Closed
Cancelled
Entered Booked Awaiting
Shipping
Order Header Example
Order Line Example (common statuses only)
Picked Invoice
Interface Shipped Closed
Cancelled
12
WORKFLOW EXAMPLE
• Most users won’t have access to the system workflow monitor.
• The OM team has developed a report that pulls information from the workflow monitor,
combines it with information from a few other sources, to provide a broader view of the
lifecycle of an order.
THE ORDER TRACK REPORT
DELIVERIES & TRIPS
• The part of Oracle OM that handles execution of the order is called Shipping Execution,
and Shipping Execution acts on Deliveries.
• A Delivery is a group of lines that share common shipping attributes (order number, ship
method, warehouse, ship date, etc.) that will travel together through the logistics planning
and executions processes. Programs run periodically to group the order lines (delivery
details) into Deliveries for processing.
• Deliveries can be sent to OTM for planning shipments… the result of this planning is a
Trip, a Delivery tied to a specific shipment
• Deliveries can be picked and shipped in Shipping Execution
WHAT ARE DELIVERIES?
DELIVERIES, SHIPMENTS, TRIPS
Order
Line
Order
Line
Order
Line
Order
Line
Order
Mgmt
Delivery
Detail
Delivery
Detail
Delivery
Detail
Delivery
Detail
Shipping
Execution
Delivery
Delivery
Order
Release
Order
Release
OTM
Shipment
Shipping
Execution
Trip Stop
Stop Trip
PROCESSING CONSTRAINTS
Or, all the rules
• Processing constraints are rules that control changes to sales documents (e.g. orders)
• Processing constraints can:
• Prevent certain changes, or operations (create, update, delete, cancel, split)
• Require a reason for changes (activates audit trail)
• Require history for changes (activates audit trail)
• Require a reason and history (activates audit trail)
• Raise an integration event
• Processing constraints can use Validation Templates to conditionally apply the constraint
• Processing constraints can use Groups to execute AND/OR groupings of multiple
conditional Validation Templates
PROCESSING CONSTRAINTS OVERVIEW
• 1,238 seeded processing constraints provided out-of-the-box
• Example: cannot delete a booked line
• Example: cannot cancel an order once any order line has been shipped
• Example: cannot update the ship to once any order line has been shipped
• Example: cannot split a line once the line has been fulfilled
• Example: cannot create a line price adjustment once the line has been invoice interfaced
• Workflows control the SEQUENCE of events
• Processing Constraints control the PERMISSION of actions
PROCESSING CONSTRAINTS EXAMPLES
• 181 custom processing constraints added to GEA’s implementation
• Example: cannot delete J.C. Penney orders or lines
• Example: cannot cancel a line once the line has a trip created
• Example: cannot update customer PO once the POD has been printed
• Example: cannot create a new line once the order has been booked (EDI Launch only)
• Example: require reason and history when cancelling a booked line
• Example: require history when updating the schedule ship date once the line has been
PO Approved
• Workflows control the SEQUENCE of events
• Processing Constraints control the PERMISSION of actions
PROCESSING CONSTRAINTS EXAMPLES
• Custom validation templates enable the keying of processing constraints off of criteria
unique to GEA processes
• 20 custom validation templates created (so far) for conditions such as:
• Delivery/trip creation
• Status of the ISO for a given CSO
• Value of the POD print flag UDA
• JCP orders
• Installation items
• These custom templates are considered CEMLI’s and are tracked as such
VALIDATION TEMPLATES
• Cannot disable or edit SEEDED processing constraints
• These constraints may be in place to protect data referential integrity.
• When creating new, custom constraints, have additional options
• Can set second half of the message text that appears on the screen
• Can allow only certain responsibilities (Authorized Responsibilities)
• Can restrict only certain responsibilities (Constrained Responsibilities)
• Can separately choose if applicable to system or user actions
• All Processing Constraints are honored by all order processes
• Forms, Order Import, Process Orders API, Workflow
MORE ABOUT PROCESSING CONSTRAINTS
QUESTIONS!
Questions?