Beruflich Dokumente
Kultur Dokumente
ORDER MANAGEMENT
Agenda
Introduction
Questions
Query transactions across multiple Operating Units by leaving the field blank
MOAC - Benefits
Users can access data from multiple operating units from a single responsibility. Also access reports, concurrent programs, setups from one place without having to switch responsibilities. Data security is still maintained using security profiles that are defined for a list of operating units and determine the data access privileges for a user. Operating Unit field is added to setup forms for payment terms, system parameters, shipping tolerances, transaction types and approval. It is also added to all the forms that allows you to view and manage sales agreement, quotes, orders and returns across multiple operating units. Case Example: If MOAC is implemented for Oracle Order Management Operating Unit is a mandatory field to create an order. All the operating unit specific/relevant fields like Ship-to, Bill-to, Order type will appear. Whenever the user changes the OU, the OU sensitive fields will disappear
Benefits
Faster data entry and modification Avoid duplication of effort Controlled modification of line attributes
CHA In 11i
CHA - Modify SO
Modify field Customer PO of existing order Profile Cascade Header Changes to Line is set to Askme
CHA - Modify SO
13
14
Also can copy fulfillment sets from one sales order/line to another sales order/line
Copyright 2010 Hitachi Consulting
15
Mass Scheduling
The Schedule Orders concurrent program now has enhanced functionality, not only to schedule lines that have failed workflow scheduling, but also the following: Lines that have failed manual scheduling Lines that are manually entered and in Entered status Lines that are imported into Order Management in Entered status Ability to sort scheduled orders Additional query parameters
Scheduling Organizer
Transaction windows (SO, SA, etc.) provide direct navigation to Open errors and retry workflow activity that failed
New workflow error handling process generates an OM - specific notification that uses standard workflow functionality to enable the recipient to retry an activity in error. The workflow also generates diagnostic information for the problematic order or line automatically Also includes a record of errors and corresponding diagnostic information for Oracle Support to aid in fixing the problem
22
Item Orderability
Businesses need the ability to control which customers are allowed to order which products. For example, Customer A may purchase all items except for repair parts and promotional items. Alternately, Customer B buys only repair parts from you. This new Order Management feature provides you with an easy way to define orderable products You define orderability rules in a new form, called Orderability Rules. It would be possible to apply Orderable Products business rules to items or Item Categories defined for an organization. Based on the rules defined in the Orderability UI, you will be able to restrict the Items that can be ordered from the Sales Order and Quick Sales Order form.
23
Item Orderability
Lets you easily control who can order what goods and services.
Allows you to ensure and enforce that you only sell goods and services whose fulfillment conditions you can meet Allows you to gradually introduce new goods and services to select customers, regions and locations Allows you to restrict goods and services to select customers Allows control by 11 attributes customer, customer class, customer category, end customer, order type, sales channel, sales person, ship to location, bill to location, deliver to location and regions Allows you to define inclusive or exclusive rules
24
Generally Available Checkbox: Check this if you want the item to be available for all orders except the ones mentioned in the rules.
25
Generally Available Checkbox: Keep this unchecked if you want the item to be only available for below mentioned rules.
27
Customer Acceptance
A way for customer to let you know theyve accepted the goods and services you have sold them. A way to defer invoicing and/or revenue recognition until the customer accepts Customer Acceptance of Goods and Services Pre-Billing or Post-Billing Acceptance Explicit or Implicit Acceptance Full Acceptance or Full Rejection of a given item Support for multiple item types Standard, Service, ATO / PTO Model, Kit For Service, ATO / PTO Model, Kit Acceptance contingency is defined at the parent level, child lines inherit acceptance information from the parent Does not apply to returns, internal orders or retro bill orders
Customer Acceptance
Pre-Billing Acceptance
Sales Order Line in Pending Pre-billing Acceptance Record Acceptance explicit or implicit Line status moves to closed and line gets interfaced to AR Invoice generation and Revenue Recognition happen subsequently Sales Order Line in Pending Post-billing Acceptance Invoice generation Record Acceptance explicit or implicit Line status moves to closed Revenue Recognition happens once acceptance is completed
Post-Billing Acceptance
Explicit Acceptance
Customer or CSR logs into the Order Information Portal or uses order import to record acceptance explicitly
Implicit Acceptance
Deferral reason has to be defined in AR with event attribute as Ship Confirm date and expiration days Request Set has two concurrent requests
Generate Pre-billing Acceptance Program for Pre-billing, Implicit Acceptance Revenue Contingency Analyzer for Post-billing, Implicit Acceptance
This has values as: Accept / Reject. The user selects a line or multiple lines and submits for acceptance or rejection.
Post Acceptance Order Line status changes to Closed Invoice cannot be raised until line status is closed in Pre-billing acceptance. Revenue Recognition happens subsequently
At Shipping, Deferred COGS is debited As Revenue is recognized, corresponding % of Deferred COGS moves to real COGS
Process:
No change to the OM user experience COGS recognized as Revenue recognized done by Costing and AR Support for multiple item types Standard, Service, ATO / PTO Models, Kits Solves ATO/PTO matching problems
If a sales order line has a contingency attached, revenue recognition happens only after contingency is removed For non-invoicable line, COGS is recognized 100% at close of line
Other Enhancements
Post Booking Item Substitution:
Item Substitution functionality support has been extended to post-Booking in
Sales Order, Quick Sales Order, and Scheduling Order Organizer forms.
operating Units. When Receivables places a customer on credit hold a hold source will be created in all operating units .
40
41
42
43
44
Execution Mode:
View Purge Selection - A report prints indicating all records meeting purge criteria. But, Records are not purged. Purge - All selected records are purged A report prints indicating all records that have been purged
Benefits: Reduce Pick Release processing time by evenly distributing load between multiple processes Improve throughput by spawning multiple child process to do the work Enhanced flexibility with the profile to optimize hardware capabilities
Ability to enter the Actual Departure Date on Release Sales Order Form.
Ability to enter the Actual Departure Date on the Auto Ship Confirm SRS
parameters form
Benefits:
Reduce ambiguity of actual ship date compared to system transaction
date
Increase revenue recognition accuracy by realizing revenue based on the
Routings.
Can be controlled from Shipping and Global Parameters. History of key activities performed. View workflows via Shipping Transactions form.
200
54
List Price, Net Price, Discounts, Surcharges, Price Breaks, and Freight & Special Charges Price Break and Pricing Attribute Details Customer Item(s)
Pricing Effective Date: past, current or future date Pricing Attributes and Qualifier Attributes
Supports Full or Delta Price Book Multiple publishing options UIs Based on Internal or External User Available for Basic and Advanced Pricing Users
Delta Price Book and XML Messaging supported with Advanced Pricing license
Provides a snapshot of list and net prices for product(s) for a given customer Validate prices for a customer
Track price changes for a customer at different points in time Reduce maintenance costs
unique Prices are based on the pricing perspective (request type) Specific to a currency Generate prices for a single item, item category, all items, or items within a specified price list. Pricing Effective Date: past, current, or future date Inputs for Price Calculation Criteria
Quantity, qualifiers, pricing attributes Based on Price List, Agreement, or Sales Agreement as a starting point
3 seeded RTF templates which allows output formats of PDF, RTF, and Excel
Price Book Details Price Book Errors Price Book Summary
date
Input criteria
Breaks are evaluated as greater than the Value From and up to and equal to the Value To
Support for all newly created Price Break Lines Improved usability through defaulting
1-10
11-20 21-999999
$100 0-10
$90 10-20 $80 20-
$100
$90 $80
Pricing Transactions
Blanket Agreement
Line Price
Pricing Engine Requisitions Price Break Custom API Price List
Lists
Accurate Pricing of Transactions without the need for Manual
Overrides
Decrease supplier over billing
Orders
Documents
Decrease Supplier Over Billing
Utilize available discounts and/or promotions for your existing open
orders
Questions
72
Thank You!!