Professional Documents
Culture Documents
Order Management Fundamentals PDF
Order Management Fundamentals PDF
Order Management Fundamentals PDF
Fundamentals
Volume 2 - Student Guide
n l y
e O
U s
A I
O
l &
D16814GC20
n a
Edition 2.0
te r
January, 2005
D40233 I n
c l e
r a
O
Copyright © 2005, Oracle. All rights reserved.
This documentation contains proprietary information of Oracle Corporation. It is provided under a license agreement containing
restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. If this
documentation is delivered to a U.S. Government Agency of the Department of Defense, then it is delivered with Restricted Rights
and the following legend is applicable:
Use, duplication or disclosure by the Government is subject to restrictions for commercial computer software and shall be deemed
to be Restricted Rights software under Federal law, as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, Rights in
Technical Data and Computer Software (October 1988).
This material or any portion of it may not be copied in any form or by any means without the express prior written permission of the
Education Products group of Oracle Corporation. Any other copying is a violation of copyright law and may result in civil and/or
criminal penalties.
If this documentation is delivered to a U.S. Government Agency not within the Department of Defense, then it is delivered with
“Restricted Rights,” as defined in FAR 52.227-14, Rights in Data-General, including Alternate III (June 1987).
The information in this document is subject to change without notice. If you find any problems in the documentation, please report
them in writing to Worldwide Education Services, Oracle Corporation, 500 Oracle Parkway, Box SB-6, Redwood Shores, CA 94065.
Oracle Corporation does not warrant that this document is error-free.
Oracle and all references to Oracle Products are trademarks or registered trademarks of Oracle Corporation.
All other products or company names are used for identification purposes only, and may be trademarks of their respective owners.
Author
Vanessa Graziano, Rebecca Zarchikoff, David Reitan, Susan Flierl, Natalia Rachelson, Stacey n l y
Gomes, David Barnacle, Steve Best, Amit Batra, Nami Hosomatsu, Bernadette Kennedy,
Chayne Kosloske, David Chin, Eric O'Brien, Friederun Baudach-Jaeger, Kathy Wohnoutka,
e O
Lynn Warneka, John Brazier, David Millin.
U s
This book was published using: oracletutor
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © 2005, Oracle. All rights reserved.
e O
Overview of Order Management Integration.................................................................................................2-14
s
Overview of the Order Management Process ...............................................................................................2-15
Overview of Customer Relationships ............................................................................................................2-16
U
Overview of Inventory Organizations ...........................................................................................................2-17
A I
Overview of Inventory Items.........................................................................................................................2-18
Overview of Simple Negotiation within Order Management ........................................................................2-19
O
Overview of Order Entry...............................................................................................................................2-20
Overview of Blanket Sales Agreements ........................................................................................................2-21
l &
Overview of Querying on Prices and Availability.........................................................................................2-22
Overview of Managing Orders ......................................................................................................................2-23
a
Summary........................................................................................................................................................2-24
n
te r
Items .................................................................................................................................................................3-1
Items ..............................................................................................................................................................3-2
Objectives ......................................................................................................................................................3-3
I n
Agenda...........................................................................................................................................................3-4
What is Enterprise Structure? ........................................................................................................................3-5
c e
Enterprise Structure Example 1 .....................................................................................................................3-7
l
Enterprise Structure Example 2 .....................................................................................................................3-8
Inventory Structure Considerations ...............................................................................................................3-10
r a
Enterprise Structure in Vision .......................................................................................................................3-12
Guided Demonstration – Enterprise Structure in Vision Operations.........................................................3-13
O
Agenda...........................................................................................................................................................3-15
Define Units of Measure................................................................................................................................3-16
Unit of Measure Example..............................................................................................................................3-18
y
Objectives ......................................................................................................................................................4-3
l
Agenda...........................................................................................................................................................4-4
n
Customer Overview.......................................................................................................................................4-5
O
Party Model Overview...................................................................................................................................4-6
Party Model ...................................................................................................................................................4-8
e
Party Model and Relationships......................................................................................................................4-9
U s
Party Model Components ..............................................................................................................................4-11
Managing Parties ...........................................................................................................................................4-12
A I
Party Sites......................................................................................................................................................4-13
Customer Accounts........................................................................................................................................4-14
Integrating Party Information ........................................................................................................................4-15
O
Data Quality Management Overview ............................................................................................................4-16
Agenda...........................................................................................................................................................4-17
l &
Profile Classes ...............................................................................................................................................4-18
Profile Class Characteristics ..........................................................................................................................4-20
a
Practice - Create a Customer Profile Class ................................................................................................4-21
n
te r
Solution - Create a Customer Profile Class ...............................................................................................4-22
Managing Customer Account Profiles...........................................................................................................4-23
Updating Profile Classes ...............................................................................................................................4-24
I n
Reviewing Profile Class Changes..................................................................................................................4-25
Agenda...........................................................................................................................................................4-26
l e
Data Quality Management Overview ............................................................................................................4-27
c
Data Quality Management (DQM) ................................................................................................................4-28
a
How Does DQM Work? ................................................................................................................................4-29
r
Fuzzy Search .................................................................................................................................................4-30
Query Word Replacement .............................................................................................................................4-31
O
Entry Methods ...............................................................................................................................................4-32
Business Issues ..............................................................................................................................................4-33
Business Purposes..........................................................................................................................................4-34
n l y
Agenda...........................................................................................................................................................4-70
Merge Parties or Customer Accounts ............................................................................................................4-71
e O
Party Merge ...................................................................................................................................................4-73
Agenda...........................................................................................................................................................4-74
s
Reviewing Information..................................................................................................................................4-75
Common Search Scenarios ............................................................................................................................4-76
U
Reports...........................................................................................................................................................4-77
A I
Agenda...........................................................................................................................................................4-78
Required Customer Profile Setup Steps.........................................................................................................4-79
O
Collectors.......................................................................................................................................................4-80
Payment Terms ..............................................................................................................................................4-81
l &
Optional Customer Profile Setup Steps .........................................................................................................4-82
Required Setup Steps for Customers .............................................................................................................4-84
n a
Profile Options...............................................................................................................................................4-85
Optional Setup Steps for Customers..............................................................................................................4-87
te r
Flexible Address Formatting .........................................................................................................................4-89
Summary........................................................................................................................................................4-91
I n
Enter Orders ....................................................................................................................................................5-1
Enter Orders...................................................................................................................................................5-2
l e
Objectives ......................................................................................................................................................5-3
c
Agenda...........................................................................................................................................................5-4
a
Order Creation Methods ................................................................................................................................5-5
r
Simple Negotiation in Oracle Order Management ........................................................................................5-6
Sales Order ....................................................................................................................................................5-7
O
Blanket Sales Agreements .............................................................................................................................5-9
Order Against Blanket Sales Agreements......................................................................................................5-10
Authoring and Negotiating Contract Terms ..................................................................................................5-11
n l y
Entering Line Information .............................................................................................................................5-52
Related Items .................................................................................................................................................5-54
Entering Line Pricing Information.................................................................................................................5-55
e O
Line Pricing Fields.........................................................................................................................................5-57
Line Date Fields ............................................................................................................................................5-58
s
Entering Line Shipping Information..............................................................................................................5-59
Guided Demonstration - Entering Line Information..................................................................................5-60
U
Practice - Create a Sales Order Line ..........................................................................................................5-61
A I
Solution - Create a Sales Order Line .........................................................................................................5-62
Available to Promise (ATP) ..........................................................................................................................5-63
O
Entering Sets..................................................................................................................................................5-64
Guided Demonstration - Entering Line Sets..............................................................................................5-65
l &
Automatic Fulfillment Set and Line Set Assignment ...................................................................................5-66
Ship Set For Each Line..................................................................................................................................5-67
n a
Entering Line Addresses................................................................................................................................5-68
Entering Return Information..........................................................................................................................5-69
te r
Entering Return Information (continued) ......................................................................................................5-70
Ordering Service Programs............................................................................................................................5-71
n
Guided Demonstration - Ordering Service Programs ................................................................................5-72
I
Applying Attachments ...................................................................................................................................5-73
Guided Demonstration - Applying Attachments .......................................................................................5-74
e
c l
Multiple and Partial Payments.......................................................................................................................5-75
How Multiple and Partial Payments differ from Single Payment..................................................................5-76
r a
Agenda...........................................................................................................................................................5-77
Blanket Sales Agreements (BSA)..................................................................................................................5-78
O
Negotiation Agreement..................................................................................................................................5-79
Approve BSA ................................................................................................................................................5-80
Customer Signs BSA .....................................................................................................................................5-81
Order Against BSA (Blanket Release) ..........................................................................................................5-82
e O
Guided Demonstration - Reserving an Order Line ....................................................................................5-137
Practice - Schedule Order ..........................................................................................................................5-138
s
Solution - Schedule Order .........................................................................................................................5-140
Modes of Reserving.......................................................................................................................................5-142
U
Scheduling Across Orders .............................................................................................................................5-144
A I
Scheduling Organizer Window......................................................................................................................5-145
Enhanced Reservations..................................................................................................................................5-146
O
Agenda...........................................................................................................................................................5-148
Booking Orders .............................................................................................................................................5-149
l &
Guided Demonstration - Booking Orders ..................................................................................................5-150
Practice - Book Order ................................................................................................................................5-151
n a
Solution – Creating and Booking the Order ..............................................................................................5-152
Agenda...........................................................................................................................................................5-153
te r
Copying Orders .............................................................................................................................................5-154
Guided Demonstration - Copying Orders ..................................................................................................5-155
n
Practice - Copying Orders With the Quotes Function ...............................................................................5-156
I
Solution – Copying Orders with the Quotes Function...............................................................................5-157
Copy Function to support Quotes and BSA...................................................................................................5-159
e
c l
Agenda...........................................................................................................................................................5-160
Import Orders Processing ..............................................................................................................................5-161
r a
High Volume Order Processing (HVOP) ......................................................................................................5-162
Agenda...........................................................................................................................................................5-164
O
Required Setup Steps for Entering Orders.....................................................................................................5-165
Additional Required Setup Steps...................................................................................................................5-166
Profile Options...............................................................................................................................................5-167
Parameters .....................................................................................................................................................5-169
y
Manual Versioning ........................................................................................................................................6-23
l
Tracking Versions..........................................................................................................................................6-24
n
Audit Trail .....................................................................................................................................................6-25
O
Processing Constraints for Audit Trail ..........................................................................................................6-26
Splitting Order Lines .....................................................................................................................................6-27
e
Guided Demonstration - Splitting Order Lines..........................................................................................6-29
U s
Practice - Split Line and Create Ship Set...................................................................................................6-30
Solution - Split Line and Create Ship Set ..................................................................................................6-31
A I
Agenda...........................................................................................................................................................6-34
Approval Enhancements................................................................................................................................6-35
Approval Workflow.......................................................................................................................................6-36
O
Agenda...........................................................................................................................................................6-37
Hold Types ....................................................................................................................................................6-38
l &
Hold Names ...................................................................................................................................................6-39
Guided Demonstration – Create Hold Name .............................................................................................6-40
a
Practice - Create Hold Name .....................................................................................................................6-41
n
te r
Solution - Create Hold Name.....................................................................................................................6-42
Apply Holds...................................................................................................................................................6-44
Guided Demonstration – Apply Holds ......................................................................................................6-46
I n
Practice - Apply Holds...............................................................................................................................6-48
Solution - Apply Holds..............................................................................................................................6-50
l e
International Trade Management (ITM) Partner Integration .........................................................................6-56
c
Release Holds ................................................................................................................................................6-57
a
Guided Demonstration – Release Holds ....................................................................................................6-58
r
Practice - Release Holds ............................................................................................................................6-60
Solution - Release Holds ...........................................................................................................................6-61
O
Agenda...........................................................................................................................................................6-66
Manage Credit Checking ...............................................................................................................................6-67
Credit Check Hold .........................................................................................................................................6-68
n
Navigator Tree Functionality.........................................................................................................................7-17
y
Summary Form ..............................................................................................................................................7-14
l
O
Guided Demonstration – Navigator Tree...................................................................................................7-18
Folder Files....................................................................................................................................................7-19
e
Guided Demonstration - Folder File ..........................................................................................................7-20
U s
Practice - Order Organizer.........................................................................................................................7-21
Solution - Order Organizer ........................................................................................................................7-23
A I
Agenda...........................................................................................................................................................7-28
Order Information Portal ...............................................................................................................................7-29
Order Status Information ...............................................................................................................................7-30
O
Delivery Information .....................................................................................................................................7-31
Summary........................................................................................................................................................7-32
l &
Credit Management.........................................................................................................................................8-1
n a
Credit Management .......................................................................................................................................8-2
Objectives ......................................................................................................................................................8-3
te r
Agenda...........................................................................................................................................................8-4
Set Up Oracle Credit Management................................................................................................................8-5
I n
Define Credit Analysts ..................................................................................................................................8-6
Assign Credit Analyst to Accounts................................................................................................................8-7
e
Define Lookups .............................................................................................................................................8-8
c l
Define System Options..................................................................................................................................8-9
Define Scoring Models..................................................................................................................................8-10
r a
Assign Automation Rules ..............................................................................................................................8-11
Credit Checklist .............................................................................................................................................8-12
O
Credit Usage Rule Sets ..................................................................................................................................8-13
Define Credit Hierarchies ..............................................................................................................................8-14
Define Customer Profile Classes ...................................................................................................................8-15
Customer Profile Classes: Credit Profile Tab...............................................................................................8-16
n
Overview of Formulas ...................................................................................................................................9-16
y
Overview of Price Lists .................................................................................................................................9-13
l
O
Overview of Qualifiers ..................................................................................................................................9-17
Overview of Modifiers ..................................................................................................................................9-18
e
Overview of Contexts and Attributes ............................................................................................................9-20
U s
Overview of Freight and Special Charges Modifiers.....................................................................................9-21
Overview of Basic vs. Advanced Pricing ......................................................................................................9-22
A I
Summary........................................................................................................................................................9-24
Basic Pricing.....................................................................................................................................................10-1
O
Basic Pricing..................................................................................................................................................10-2
Objectives ......................................................................................................................................................10-3
l &
Agenda...........................................................................................................................................................10-4
Pricing Security Overview.............................................................................................................................10-5
n a
Security Implementation Steps ......................................................................................................................10-6
Security Implementation Steps – Mapping Security Requirements ..............................................................10-7
te r
Security Implementation Steps – Assigning Pricing Entities to an Operating Unit.....................................10-8
Security Implementation Steps – Creating Privileges....................................................................................10-9
I n
Security Implementation Steps – Setting up Default Security Profile Options .............................................10-10
Security Implementation Steps – Turning Security On .................................................................................10-11
e
Security Features and impact on Forms/Windows ........................................................................................10-12
c l
Agenda...........................................................................................................................................................10-13
Price List Creation .........................................................................................................................................10-14
r a
Price List Header ...........................................................................................................................................10-15
Price List Line ...............................................................................................................................................10-17
O
Price List Line (contd.)..................................................................................................................................10-19
Copy Price List ..............................................................................................................................................10-21
Guided Demonstration – Copy a Price List ...............................................................................................10-22
Practice - Copy Price List ..........................................................................................................................10-23
n l y
Agenda...........................................................................................................................................................10-63
Qualifier Overview ........................................................................................................................................10-64
Seeded Qualifier Contexts .............................................................................................................................10-65
e O
Agenda...........................................................................................................................................................10-67
Modifier Overview ........................................................................................................................................10-68
s
Modifier List..................................................................................................................................................10-69
Modifiers Lines .............................................................................................................................................10-70
U
Modifier Line Examples ................................................................................................................................10-72
A I
Modifier Types ..............................................................................................................................................10-73
Agenda...........................................................................................................................................................10-74
O
Overview of Freight and Special Charges Modifiers.....................................................................................10-75
Seeded Freight Charges .................................................................................................................................10-76
l &
Setting up Freight and Special Charges Modifiers ........................................................................................10-77
Guided Demonstration – Freight and Special Charges Modifiers .............................................................10-78
n a
Practice - Freight and Special Charges Modifiers .....................................................................................10-79
Solution – Freight and Special Charges Modifiers ....................................................................................10-80
te r
Agenda...........................................................................................................................................................10-83
Overview of Attribute Management ..............................................................................................................10-84
n
Setup Steps – Creating Contexts and Attributes ............................................................................................10-87
I
Setup Steps – Linking Attributes to a Pricing Transaction Entity (PTE).......................................................10-89
Agenda...........................................................................................................................................................10-91
e
c l
Profile Options in Basic Pricing ....................................................................................................................10-92
Summary........................................................................................................................................................10-94
r a
Oracle Shipping Execution Overview ............................................................................................................11-1
Oracle Shipping Execution Overview ...........................................................................................................11-2
O
Objectives ......................................................................................................................................................11-3
Order to Cash Life Cycle...............................................................................................................................11-4
Overview of Shipping in the Order to Cash Process .....................................................................................11-5
n l y
Shipping Exceptions ......................................................................................................................................12-29
O
Guided Demonstration – Define Shipping Exceptions ..............................................................................12-31
Agenda...........................................................................................................................................................12-32
e
Release Sales Orders .....................................................................................................................................12-33
U s
Guided Demonstration – Release Sales Orders .........................................................................................12-35
Practice - Release Sales Orders .................................................................................................................12-37
A I
Solution - Release Sales Orders.................................................................................................................12-38
Methods to Pick Release................................................................................................................................12-44
Pick Release Parameters ................................................................................................................................12-45
O
Configuring Pick Release Process .................................................................................................................12-47
Auto Create Delivery.....................................................................................................................................12-49
l &
Agenda...........................................................................................................................................................12-51
Ship Confirm .................................................................................................................................................12-52
a
Guided Demonstration – Ship Confirm Delivery ......................................................................................12-54
n
te r
Practice - Ship Confirm Delivery ..............................................................................................................12-56
Solution – Ship Confirm Delivery .............................................................................................................12-57
Shipping Transaction Parameters ..................................................................................................................12-62
I n
Shipping Documents......................................................................................................................................12-64
Guided Demonstration – Define Document Sets.......................................................................................12-65
l e
Ship Confirm Rules .......................................................................................................................................12-66
c
Ship Confirm Deliveries SRS........................................................................................................................12-69
a
Agenda...........................................................................................................................................................12-71
r
Working with Deliveries and Delivery Lines ................................................................................................12-72
Delivery Parameters ......................................................................................................................................12-75
O
Delivery Line Processing Statuses.................................................................................................................12-77
Packing into LPNs/Containers.......................................................................................................................12-79
Container Load Details ..................................................................................................................................12-81
n l
Shipping Roles and User Security .................................................................................................................12-126
Guided Demonstration – Define Roles ......................................................................................................12-128
y
Choose Printers..............................................................................................................................................12-125
e O
Guided Demonstration – Grant Access to Roles .......................................................................................12-129
Practice - Define Roles ..............................................................................................................................12-130
s
Solution - Define Roles .............................................................................................................................12-131
Practice - Grant Access to Roles................................................................................................................12-136
U
Solution -Grant Access to Roles................................................................................................................12-137
A I
Regions and Zones.........................................................................................................................................12-138
Calendars .......................................................................................................................................................12-140
O
Profile Options...............................................................................................................................................12-141
Lookups .........................................................................................................................................................12-144
l &
Shipping Execution Reports ..........................................................................................................................12-146
Departure Ship Notice Outbound (DSNO) ....................................................................................................12-151
n a
Oracle Transportation Execution...................................................................................................................12-152
Summary........................................................................................................................................................12-153
te r
Appendix A: Tax Accounting Process ...........................................................................................................13-1
Appendix A Tax Accounting Process............................................................................................................13-2
I n
Objectives ......................................................................................................................................................13-3
Agenda...........................................................................................................................................................13-4
l e
Order Management Global Taxes Overview .................................................................................................13-5
c
Receivables Global Tax Overview ................................................................................................................13-6
a
Other Products ...............................................................................................................................................13-7
r
Global Tax Overview ....................................................................................................................................13-8
Tax Overview ................................................................................................................................................13-10
O
Value Added Tax Overview ..........................................................................................................................13-11
US Sales Tax Overview.................................................................................................................................13-12
US Sales Tax Example ..................................................................................................................................13-13
n
Practice - Deferred Tax Codes...................................................................................................................13-49
Solution - Deferred Tax Codes ..................................................................................................................13-50
l y
e O
Defining Receivables Activities ....................................................................................................................13-52
Changing Tax Transactions ...........................................................................................................................13-53
s
Adjusting Tax on Invoices.............................................................................................................................13-54
Tax Credit Memo...........................................................................................................................................13-56
U
Agenda...........................................................................................................................................................13-57
A I
Tax Reporting Ledger Overview ...................................................................................................................13-58
Tax Extract Overview....................................................................................................................................13-59
O
Sources of Data..............................................................................................................................................13-61
Tax Ledger Reporting Options ......................................................................................................................13-62
l &
Matrix Reporting ...........................................................................................................................................13-63
RXi Report Steps ...........................................................................................................................................13-64
n a
Modifying Attribute Sets ...............................................................................................................................13-65
Defining Summary Details ............................................................................................................................13-67
te r
Publish RXi Reports ......................................................................................................................................13-68
Managing Access to RXi Reports and Attribute Sets ....................................................................................13-69
n
Summary........................................................................................................................................................13-70
e I
c l
r a
O
Copyright © 2005, Oracle. All rights reserved.
Before you begin this course, you should have the following qualifications:
Prerequisites
11i Oracle Order Management Fundamentals is an instructor-led course featuring lecture and
hands-on exercises. Online demonstrations and written practice sessions reinforce the concepts
and skills introduced.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © 2005, Oracle. All rights reserved.
Additional Publications
• Read-me files
• Oracle Magazine
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © 2005, Oracle. All rights reserved.
l
For further information, see Oracle7 Server SQL Language
Reference Manual.
n y
courses,
variables
Enter user_id@us.oracle.com, where user_id is the
name of the user.
e O
Quotation
marks
Interface elements
with long names
that have only
U s
Select “Include a reusable module component” and click Finish.
Arrow
table names
Menu paths
te r Select File > Save.
Brackets
Commas
I n
Key names
Key sequences
Press [Enter].
Press and release keys one at a time:
Plus signs
c l e
Key combinations
[Alternate], [F], [D]
Press and hold these keys simultaneously: [Ctrl]+[Alt]+[Del]
r a
O
Copyright © 2005, Oracle. All rights reserved.
(N) Invoice > Entry > Invoice Batches Summary (M) Query > Find (B) Approve
n a
(M) = Menu
te r
(T) = Tab
I n
l
(B) = Button
c e
a
(I) = Icon
r
O
(H) = Hyperlink
1. In the navigation frame of the help system window, expand the General Ledger entry.
4. Review the Enter Journals topic that appears in the document frame of the help system
window.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © 2005, Oracle. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 1
Order Inquiry
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 2
Objectives
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 3
Agenda
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 4
Pricing and Availability
n l y
e O
Pricing and Availability
U s
A I
When you enter an item in the Pricing and Availability window, the related pricing and
availability information of that item is displayed for you. This window enables you to query for
O
the price and availability of an item without creating a sales order, reservation, etc. The Pricing
and Availability window enables you to:
l &
• Perform price and availability checking without creating an order
n a
• Perform price and availability checking without placing demand or reservations
r
• Easily create an order or quote if the query results in a customers decision to buy the item
te
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 5
Inquire on Price without creating Sales Order
n l y
e O
Inquire on Price without creating Sales Order
U s
A I
Usually the pricing engine displays the price of an item on the order line. Now, without creating
a sales order, you can view the list price and selling price of an item using the Pricing and
Availability window.
O
l &
The Pricing and Availability window merely displays the price and stock status of an item. It
does not confirm that the displayed price or quantity will be the same on the actual order line.
a
Keeping the above in mind, the Pricing and Availability window gives you the entire pricing
n
te r
picture of a given item. Price Breaks, Price Lists, Modifiers, Adjustments are all displayed in the
Pricing and Availability window so that you can see all the price information at a glance.
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 6
Inquire on Availability
n l y
e O
Inquire on Availability
U s
A I
Now, without creating a sales order, you can view the availability of an item using the Pricing
and Availability window. The item number needs to be entered in the query block and all the
O
information related to the item is displayed in the results block.
l &
The Pricing and Availability window merely displays the stock status of an item. It does not
confirm that the displayed price or quantity will be the same on the actual order line. Keeping the
a
above in mind, the Pricing and Availability window gives you the entire availability picture of a
n
te r
given item. You can view the warehouse, available quantity, reservable quantity and earliest
available date for an item’s availability. Item information like UOM, lead time and other
seen.
I n
attributes are also displayed. Related items with their selling price and availability can also be
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 7
Automatically create quote or sales order from Price and
Availability inquiry
n l y
e O
U s
A I
Automatically create quote or sales order from Price and Availability inquiry
O
When you query an item and the result set displays its pricing and availability data, you can then
save the item details to the Current Selections region. This region acts as a placeholder to contain
l &
multiple items, that can be used to create quotes or sales orders. Click Save as Quote or Create
Order to specify an order type and then create a quote/sales order. You can also open the newly
n a
created quote/sales order in its appropriate form, this is launched from the Pricing and
Availability window.
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 8
Agenda
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 9
Order Organizer Overview
n l y
e O
Order Organizer Overview
U s
Order Management Super User, Vision Operations (USA)
(N) > Orders, Returns > Order Organizer A I
O
The Order Organizer is a series of folder files that can acts as an Orders Workbench.
l &
Use the Order Organizer to Find existing orders, Add new orders, or perform mass updates
across many orders or order lines.
n a
te r
The Order Organizer matches the criteria entered on the Find Orders form against Orders and
Order Lines. The selection criteria can be stored as a saved query then reused when needed
from the Navigator Tree.
I n
The Summary Form is used to display the retrieved Orders and Lines. This makes it possible to
c l e
manage several orders at the same time, i.e. perform mass updates.
The Order Organizer is Right Mouse enabled making many of the Folder features easy to
r a
implement and manage.
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 10
Find Orders
n l y
e O
Find Orders
U s
Order Management Super User, Vision Operations (USA)
(N) > Orders, Returns > Order Organizer > (B) Find A I
O
The Find Orders form uses AND logic to build the selection criteria. This enables you to create
&
complex queries that meet your business needs by combining fields from any of the Find Order
l
tabs.
n a
Further enhance your search by using date ranges. Date Ranges included: Order Date, Request
I n
• Use the Order Category and Order Type to find groups of orders.
l e
• Many times you need to find an order by a specific pieces of information such as a
c
Customer’s PO, Invoice Number, or Purchase Requisition Number.
r a
• Order Clerks can quickly find all their orders by searching by the Created By field.
O
• Use the Order Source to find orders generated from another source such as Quotes,
iStore, Service, or EDI transactions.
Order Line tab
Order Inquiry
Chapter 7 - Page 11
• Find Orders by the Item/Warehouse combination to retrieve all the order lines that may
be affected by a shortage or a quality hold.
• Find orders by Freight Carrier to prepare for a possible carrier strike.
• Use the Waybill number to find the sales order numbers that shipped together.
Hold Information tab
• Enables you to specify holds related criteria and find orders that are on hold.
• Find Hold Sources you may wish to release.
Advanced tab
• Enables you to specify whether the query should include Closed or Cancelled Orders and
Order Lines.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 12
Guided Demonstration - Find Orders and Order Lines
Responsibility: Order Management Super User, Vision Operations
(USA)
(N) > Orders, Returns > Order Organizer > (B) Find
1. Select Customer.
Note: If using the Vision demo database you can use Business World.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 13
Summary Form
n l y
e O
Summary Form
U s
Order Management Super User, Vision Operations (USA)
(N) > Orders, Returns > Order Organizer > (B) Find > (T) Summary A I
O
Orders and Order Lines that meet your Find criteria are returned to the Summary Form.
l &
From the Summary form you can perform many of the same actions that are allowed in the
n
actions on groups of orders and lines. a
Enter Orders window. But since you are on a summary form you have the ability to do Mass
You can:
te r
I n
• Apply and Release Holds
• Cancel Orders and Lines
l e
• Copy orders and Lines.
c
Notification Action - you can send workflow notifications to your customer, support analyst,
r a
or engineers to keep them informed about special order needs. The Action notification does not
O
put a hold on the order or order line and does not require a response. If you are the User
responsible for responding to a Workflow Notification you can use the Action - Progress Order
to allow the Sales Order to proceed to it’s next work flow activity.
Order Inquiry
Chapter 7 - Page 14
Additional information action - gives you extensive information about your Orders and
Order Lines. This allowing you to respond to Customer or Internal inquiries, or track down
possible problems that might be affecting your order.
Holds tab - provides you the visibility to the Hold Name, the criteria which put the entity on
hold and when the hold was applied. Once the hold has been released the Holds tab displays
when the hold was released and who released it.
Return Activity tab - is populated if you use the Reference option when creating a Return
Order. Return Activity displays the Return order number, quantity returned, credited price,
and the Invoice Number which was credited.
Deliveries tab - is populated by the Pick Release and Ship Confirm processes. This tab allows
you to find vital shipping information for tracking down lost shipments.
Internal Requisition tab - gives you visibility to the Purchase Requisition which initiated the
Internal Sales Order.
Drop Ship tab – used to track your supplier shipments. Initially it will display the purchase
requisition number and status. Once the purchase order has been created the drop ship tab’s
requisition number is replaced with the purchase order number and status. The supplier and
buyer are also displayed.
Quantity History tab- used to track quantity decreases. Only booked orders are tracked.
Available information is quantity prior to decrease, date of quantity change and the reason for
the quantity change.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 15
Guided Demonstration – Summary Form
Responsibility: Order Management Super User, Vision Operations
(USA)
(N) > Orders, Returns > Order Organizer > (B) Find > (T) Summary
1. Select Customer.
Note: If using the Vision demo database you can use Business World.
Note: If using the Vision demo database you can use AS18947.
n l y
7.
8.
Click on each tab to view the additional information.
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 16
Navigator Tree Functionality
n l y
e O
Navigator Tree Functionality
U s
Order Management Super User, Vision Operations (USA)
(N) > Orders, Returns > Order Organizer (T) Orders A I
O
To access the Navigator Tree click on the Orders tab from the Find Orders form.
l &
Today's Orders is a seeded folder that displays all orders entered today by the current user.
a
Search Results is a seeded folder that displays all orders or lines matching your query criteria.
n
te r
The orders and order lines that are displayed in the Summary form are retrieved based on the
search criteria entered on the Find orders form. This criteria can be saved as a User-Defined
Query.
I n
To create a User-Defined Query Right Mouse Click in the Navigator Tree region after records
l e
are displayed in the Summary form. The Save Query form will pop, choose Save Query. The
c
other choices are Delete and Rename.
r a
User-Defined Queries saved as Public can be used by many users and are stored in seeded
Public Folders files. User-Defined Queries that are not saved as public are stored in seeded
O
Personal Folder files.
Order Inquiry
Chapter 7 - Page 17
Guided Demonstration – Navigator Tree
Responsibility: Order Management Super User, Vision Operations
(USA)
(N) > Orders, Returns > Order Organizer > (B) Find > (T) Summary
Note: First you will perform a Find in order to create a query statement.
1. Select Customer.
Note: If using the Vision demo database you can use Business World.
Note: If using the Vision demo database you can use AS18947.
5. Right Mouse Click in the Navigator Tree region (Left hand side of window).
n l y
7.
•
Enter a unique Query name.
te
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 18
Folder Files
n l y
e O
Folders Files
U s
Order Management Super User, Vision Operations (USA)
(N) > Orders, Returns > (T) Order Organizer > (I) Folder Tools A I
O
All the windows that are part of the Order Organizer are Folder Files. Use the Profile Option:
&
Folders: Allow Customization to control who can manage folders.
l
a
Click the Folder menu or the Folder Tools icon to save your folder.
n
When creating folders:
te r
• Folder files are associated with the user name that created it and only made public if
saved as Public.
I n
• Folders saved as a Default Folder will only default for the user who created them.
l e
• Use the Folder Tools icon, Folder Menu or Right Mouse click to Customize Folders by
c
rearranging, expanding/contracting, hiding/displaying and renaming fields.
r a
• To Open Existing Folders click the Folder icon.
O
• To Delete a folder file click the Folder icon and select the folder you want to delete then
use the Folder Menu or the Folder Tools to delete it.
Order Inquiry
Chapter 7 - Page 19
Guided Demonstration - Folder File
Responsibility: Order Management Super User, Vision Operations
(USA)
(N) > Orders, Returns > Order Organizer (T) Summary
2. Using the Folder Menu Create a new folder file for the Summary form.
5. Save as Default.
6.
7.
Using your mouse “drag” fields into different positions.
te r
(for example: by customer, or order date range)
I n
12. Retrieved records are displayed in your new summary folder
c l e
Note: It is VERY important to understand that folder files are associated with a User Name.
r a
Since many users are logged in as Operations/Welcome the last user to exit the Order
Organizer Summary tab will set the default value.
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 20
Practice - Order Organizer
Overview
In this practice you will learn how to customize and use the Order Organizer.
• Save a Query
Assumptions
• “XX” is your initials.
• iSupport has been installed along with other dependencies and patches.
• The URL s for accessing the HTML login page and apps login page.
•
Seeded Vision Data.
n
You must have access to an Oracle Application Vision database or comparable training l y
or test instance at your site on which to complete this practice.
e O
Tasks
U s
1.
2.
Login to the database.
A I
Choose the responsibility Order Management Super User, Vision Operations (USA).
O
3. Create a Default Summary form.
l &
•
a
N > Orders, Returns > Quick Order Organizer
n
4. Shrink the status field.
te r
5.
I n
Change the Customer PO prompt.
6.
l e
Move the Customer PO Field to the left of the Status field.
c
7.
r a
Save your modified folder.
8.
O
Use the Quick Order Organizer to Find all the Orders for Business World entered last week
and this week.
Order Inquiry
Chapter 7 - Page 21
• N > Orders, Returns > Quick Order Organizer
10. Look at Todays Orders. (Note: You only see the current user’s orders).
11. Look at the Orders that were retrieved from the last execution of the Find form.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 22
Solution - Order Organizer
Login
• Password: welcome
Choose Responsibility
3. Close the Find window to view the main Quick Order Organizer window.
Order Inquiry
Chapter 7 - Page 23
Shrink the Status Field
10. Place your cursor on each icon so that the tooltip appears and select the Shrink icon.
c
Save Folder
r a
O
18. Click (M) Folder > Save and close windows.
Order Inquiry
Chapter 7 - Page 24
Find all the Orders for Business World
n l y
e O
Save the Query
U s
I
23. Put your cursor in the white, left side of the Order Organizer (T) Summary form.
A
O
24. Right Mouse click. When the menu displays, select the Save Query option.
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 25
25. Name: XX-Bus.World Current Orders. Select the Public box and click (B) OK.
n l y
e O
U s
A I
O
l &
n a
te r
I n
26. Click on the Public folder icon to see your new saved query.
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 26
Look at Todays Orders
n l y
e O
U s
Look in the Personal Folder
A I
29. Double click on Personal Folders O
l &
n a
te r
I n
c l e
r a
O
30. Close the Quick Order Organizer window.
Order Inquiry
Chapter 7 - Page 27
Agenda
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 28
Order Information Portal
n l y
e O
Order Information Portal
U s
The Order Information Portal consists of four tabs:
A I
• Home: This is the default page that Order Information opens to. It displays recent orders,
O
recent deliveries and a What’s New section. The Home page can be customized.
&
• Order Status: This tab displays details about sales orders. Additionally, information about
l
n a
quality, pricing, shipping and invoicing is also available.
• Delivery: This tab displays delivery details.
te r
• Customer Service: This tab contains a Contact Us section where you can add contact
information about your company.
I n
The Order Information Portal allows both internal and external user access. View for the external
c l e
user is secured by Customer, which you can assign. Users can be assigned in the Define users
window in System Administration responsibility in Oracle Applications. A user without an
r a
assigned customer is treated as an internal customer.
Throughout the Order Information Portal, you can use either a simple search or an advanced
O
search to look for information. The Advanced Search button is available on all the pages and
when you click it, the Advanced Search page opens, enabling you to enter more criteria.
Order Inquiry
Chapter 7 - Page 29
Order Status Information
n l y
e O
Order Status Information
U s
A I
The Order Status tab is central to the Order Information Portal. It not only enables you to view
sales order information, but additional information like pricing, invoicing, quality etc. The
O
Order Status tab consists of a simple search region and an advanced search button to help you
search for sales order and related information.
l &
The simple search criteria are: Customer Name, Customer Purchase Order, or Sales Order
a
Number. The advanced search criteria are: Sales Order, Delivery Number, Customer PO,
n
te r
Customer Name and Ship To. Additional advanced search criteria are: Order Date Between,
Order Date To, Requested Ship Date Between, Requested Ship Date To. The Search Results
I n
window populates with the rows matching the criteria. Some of the headers of the search
results window are links – if you click on them, they will sort the rows in ascending or
l
descending order.
c e
The search results output is called the Sales Order Summary and displays the basic order
r a
information. The additional information is classified into four broad sections: General,
Shipping, Billing and Item Information. Under the General section, two links are provided to
O
view Quality Plan and Invoice Information. Under the Shipping section, the View Delivery
Summary and View Line Details links are used to display further delivery and line information.
Under the Billing section, the Pricing link displays more pricing information.
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 30
Delivery Information
n l y
e O
Delivery Information
U s
A I
Like the Order Status tab, the Delivery tab also enables you to perform a simple or an advanced
search to view delivery-related information and when items ship. The simple search criteria are:
O
Delivery Number, Customer Purchase Order Number, or Sales Order Number. The advanced
l &
search criteria include: Planned Ship Date (From and To), Actual Ship Date (From and To),
Planned Arrival Date (From and To) and Actual Arrival Date (From and To). The search results
a
window displays the following information about deliveries: Delivery Number, Planned Ship
n
te r
Date, Actual Ship Date, Freight Carrier, Waybill etc. When you click a Delivery Number, you
can drill down to the detailed delivery information. The Delivery Details page consists of the
Shipping Information and Delivery Lines sections that contain more information about the
delivery.
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 31
Summary
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Order Inquiry
Chapter 7 - Page 32
Credit Management
Chapter 8
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 1
Credit Management
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 2
Objectives
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 3
Agenda
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 4
Set Up Oracle Credit Management
n l y
e O
Set Up Oracle Credit Management
U s
A I
Credit policies are uniquely identified by the type of credit reviews that you perform at your
enterprise, as well as by the credit relationships that you have with your customers and
O
prospects. These two dimensions, known as the credit review type and credit classification,
I n
• Define Credit Management system options
l e
• Define scoring models
c
• Assign automation rules (optional)
r a
• Define checklists
O
• Verify usage rules
• Define the credit hierarchy for your customers and prospects
Credit Management
Chapter 8 - Page 5
Define Credit Analysts
n l y
e O
Define Credit Analysts
U s
A I
Before you can define credit analysts in Resource Manager, you must first define them as
employees in Oracle Human Resources Management System (HRMS). Later, when you are
O
ready to define your credit analysts, you import employees from HRMS into Resource
Manager and assign roles.
l &
After you define a credit analyst, you can modify any of the analyst’s information, except the
employee and user names.
n a
to setup functionality.
te r
Note: You can assign the credit manager role to a credit analyst. A credit manager has access
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 6
Assign Credit Analyst to Accounts
n l y
e O
Assign Credit Analyst to Accounts
U s
A I
To assign a credit analyst to a customer or account, you update the assigned profile class. If the
applicant does not have an assigned credit analyst, or is a prospect, then any credit review for
O
that applicant is routed to the Credit Scheduler for analyst assignment
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 7
Define Lookups
n l y
e O
Define Lookups
U s
A I
For example, to identify an applicant’s potential credit risk, you must select a credit
classification, if not previously assigned, when entering a credit application. The credit
O
classification describes the type of credit relationship that you have with the applicant.
l &
Credit Management provides you with High Risk, Low Risk, and Moderate Risk, but you can
optionally define new credit classifications to fit your business needs.
n a
You use the Oracle Receivables Lookups window to define any additional lookups that you
require.
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 8
Define System Options
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 9
Define Scoring Models
n l y
e O
Define Scoring Models
U s
A I
A scoring model consists of a group of data points, with scored ranges and a relative weighting
factor for each data point. During a credit analysis, Credit Management calculates a score from
O
0 to 100, with 0 representing the most risk and 100 representing the least risk.
l &
The View Scoring Models page displays a table of all existing scoring models. You can view
and update the scoring models by clicking the respective inline icons, or you can define a new
scoring model.
n a
te r
You can assign a default scoring model to a credit checklist. Alternatively, you can generate
various “what–if” scenarios during a credit review by selecting different scoring models from
the case folder.
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 10
Assign Automation Rules
n l y
e O
Assign Automation Rules
U s
A I
Automation rules base credit decisions upon the credit score that the assigned scoring model
calculates. For each automation rule, you define recommendations for a related credit score
O
range. For example, if the credit score is below 50, you might want to automatically reject a
credit request.
l &
The Automation Rules page provides you with an overview of all scoring models for which a
a
set of automation rules is defined. You can view and update existing sets of automation rules
n
Note: This step is optional.
te r
by clicking the respective inline icons, or you can create a new set.
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 11
Credit Checklist
n l y
e O
Credit Checklist
U s
A I
For example, when a high risk customer seeks to increase its credit limit with your enterprise,
your credit policies might dictate a conservative approach until this customer relationship is
O
more established. In this scenario, you would use a conservative checklist to determine whether
l &
to grant additional credit and what the credit limit should be.
The flexible setup procedures that follow reflect Oracle Credit Management’s ability to meet
a
the demands of your enterprise’s particular credit policies.
n
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 12
Credit Usage Rule Sets
n l y
e O
Verify Credit Usage Rule Sets
U s
A I
For example, if a customer is assigned the Default profile class with a credit usage rule set that
includes USD, EUR, and CAD, then any transactions of those currencies are included in that
O
customer’s case folder for data points such as Count of Open Invoices or Amount of Open
Invoices.
l &
In Oracle Order Management, credit usage rule sets define the set of currencies that will share
a
a predefined credit limit during the credit checking process, and enable the grouping currencies
n
for global credit checking.
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 13
Define Credit Hierarchies
n l y
e O
Define Credit Hierarchies
U s
A I
To provide global credit limits that are shared by some or all entities within a complex,
multinational organization, you can define credit relationships between parties using Oracle
Trading Community Architecture Relationship Manager.
O
l &
You can define a credit hierarchy of parties, party relationships, hierarchy levels, accounts, and
account sites. Typically, the party object and party subject in a credit relationship represent a
a
parent and child, or HQ and division hierarchy. For each entity in the hierarchy, you can view
n
te r
credit information, such as credit hold status, credit limits by currency, and credit review cycle.
Using Relationship Manager, you assign to your entities an existing relationship type, such as
I n
Global Ultimate, or your own user–defined Credit Management relationship type. You then
link the relationships to Credit Management by assigning the relationship type to the AR:
l e
Credit Hierarchy Type profile option. When you conduct a credit review for an entity that has
c
hierarchical relationships, Credit Management consolidates and displays all data for the entire
r
hierarchy.
a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 14
Define Customer Profile Classes
n l y
e O
Define Customer Profile Classes
U s
A I
You can also define amount limits for your finance charges, dunning, and statements for each
currency in which you do business. Define your standard customer profiles in the Customer
O
Profile Classes window. These profiles contain generic options you can use to group your
customers into broad categories.
l &
For example, you might define three categories: one for prompt paying customers; one for late
a
paying customers with high finance charge rates; and a third for customers who mostly pay on
n
te r
time, with discount incentives for early payment.
You can also use the profile class “DEFAULT,” which Oracle Receivables provides.
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 15
Customer Profile Classes: Credit Profile Tab
n l y
e O
Credit Profile Tab in Customer Profile Classes form
U s
Periodic Review Cycle
• Defines the frequency of automatic reviews for a customer. A I
O
Note: Eligible reviews are processed via the Periodic Review Cycle concurrent program.
Credit Analysis
l &
a
• The credit analysis automatically is assigned to all parties, accounts, and sites which have
n
this profile class.
Credit Tolerance
te r
I n
• The percentage upon which credit exposure is exceeded before an order will be placed on
credit holds. Credit holds automatically submit a credit request.
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 16
Use Customers-Standard
n l y
e O
Customers-Standard Window
U s
address level take precedence over those set at the customer level. A I
If a profile is assigned to a customer and an address of the same customer, the options set at the
O
For statement site and dunning site profile amounts, however, Receivables uses the options at
option to Yes.
l &
the address level only if you set the AR: Use Statement Site & Dunning Site Profiles profile
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 17
Agenda
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 18
Process Credit Reviews
n l y
e O
Credit Review Process
U s
A I
During the credit review, the Credit Management Application workflow manages the process
flow of credit data collection and analysis, as well as the implementation of credit decisions. In
O
addition, Credit Management provides various tools that you can use to determine if your
credit policies are effective.
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 19
Initiate a Credit Review
n l y
e O
Initiate a Credit Review
U s
A I
For example, if a sales order is put on credit hold, then the credit hold process in Oracle Order
Management passes this information to the Credit Review Request API, which automatically
O
initiates a credit review. Other events, such as a quarterly review, can also trigger a credit
review.
l &
Note: You can also use the Credit Review Request API to initiate a credit review from a non–
Oracle system.
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 20
Collecting Credit Data
n l y
e O
Collecting Credit Data
U s
A I
The credit checklist indicates which data points are required for different types of credit
analyses and decisions, and can optionally indicate which scoring model will be used for the
O
review. In this way, the checklist enforces your enterprise’s credit policies.
l &
If the checklist identifies required data points that already exist within Oracle Applications or
are calculable, such as available credit, aging, and so on, then Credit Management
a
automatically inserts that information directly into the credit application and case folder. If the
n
te r
checklist requires data points that must be manually supplied, such as bank and trade
references, then a credit analyst must enter the required data into the credit application or case
folder.
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 21
Analyzing Credit Data
n l y
e O
Analyzing Credit Data
U s
A I
The Credit Analysis data pages comprise the universe of data points for the applicant. The
Credit Analysis data pages that are available off of the Analysis tab include:
• Credit Analysis: Case Folder O
• Credit Analysis: Credit Summary
l &
a
• Credit Analysis: Billing and Payment Details
n
r
• Credit Analysis: Aging Details
te
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 22
Making a Recommendation
n l y
e O
Making a Recommendation
U s
A I
Generally, a recommendation is specific to the type of review that was just concluded. For
example, a credit review that an order hold originally initiated would most likely result in a
recommendation to:
O
from hold.
l &
• Increase the credit limit to accommodate the amount of the order and remove the order
n a
• Deny the request for an increase in the credit limit and leave the order on hold.
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 23
Implementing the Recommendation
n l y
e O
Implementing the Recommendation
U s
approved it. A I
Receivables automatically implements the recommendation after all required parties have
O
For example, if the recommendation indicates that the order should be removed from credit
l &
hold, then the workflow will call the Remove Credit Hold API and pass the necessary
information, such as order ID, account ID, and so on, to initiate the process.
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 24
Agenda
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 25
Credit Management Application Workflow
n l y
e O
Credit Management Application Workflow
U s
A I
For each credit review, the workflow checks the automation rules that you previously defined:
• If the credit review is automated, then the workflow attempts to automatically make and
implement credit decisions without user intervention. O
&
• If the workflow stops due to conditions such as missing data, then the workflow routes
l
n a
notifications to the appropriate credit analyst for resolution.
• If a credit analyst was never assigned because the credit review was automated, then the
te r
workflow notifies the user with the Credit Scheduler responsibility that a credit analyst
must be assigned. The Credit Scheduler can select the credit analyst to be assigned from
I n
the List of Values. The assigned credit analyst then receives a notification that they have
a credit request in their queue.
l e
• If the credit review is not automated, then the workflow assigns the credit review to the
c
r a
appropriate credit analyst and notifies the analyst about the assignment.
• With unautomated credit reviews, credit analysts make recommendations, such as
O increasing or decreasing the credit limit, after performing the credit analysis.
Credit Management
Chapter 8 - Page 26
Oracle Approvals Management (AME)
n l y
e O
Oracle Approvals Management (AME)
U s
manages the approvals for that application’s transactions. A I
Once you define the rules for a given application, the Oracle Approvals Management Engine
O
If approval is required, then the workflow routes notifications according to the approval
hierarchy:
l &
n a
• If the recommendation is approved by the appropriate personnel, then the workflow
automatically implements the decision.
te r
• If the recommendation is rejected as it is routed through the approval hierarchy, then the
workflow sends notifications to the appropriate personnel and updates the case folder.
I n
If a credit analyst cannot be identified, then the workflow notifies the person assigned to the
l e
Credit Scheduler role that a credit analyst assignment is required. The Credit Scheduler is a
role used in Credit Management to assign credit tasks to credit analysts.
c
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 27
Agenda
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 28
Review Credit Management Performance
n l y
e O
Review Credit Management Performance
U s
A I
On the Performance tab, you can access simple views into the workload and effectiveness of
the checklists and scoring models that you have set up and used in credit reviews, including:
• Credit Workload Quick Check O
• Top 10 Customer Credit Exposure
l &
• Customer Trends (Pay Trend)
n a
• Checklist Usage by Month
te r
• Scoring Model Usage by Month
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 29
Agenda
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 30
Define Credit Hierarchies
n l y
e O
Use Relationship Manager
U s
Relationship Manager, you can: A I
Relationship Manager lets you easily build, view, and edit relationships between entities. Using
n
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 31
Identify a Credit Hierarchy
n l y
e O
Use Relationship Manager
U s
A I
Using Relationship Manager, you assign to your entities an existing relationship type, such as
Global Ultimate, or your own user–defined Credit Management relationship type. You then
O
link the relationships to Credit Management by assigning the relationship type to the AR:
Credit Hierarchy Type profile option.
l &
When you conduct a credit review for an entity that has hierarchical relationships, Credit
a
Management consolidates and displays all data for the entire hierarchy.
n
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 32
Summary
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 33
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Credit Management
Chapter 8 - Page 34
Overview of Pricing
Chapter 9
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 1
Overview of Pricing
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 2
Objectives
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 3
Agenda
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 4
Order to Cash Lifecycle
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 5
Overview of Pricing in the Order to Cash Process
n l y
e O
Overview of Pricing in the Order to Cash Process
U s
The ordering process leads to:
• Shipping of goods A I
• Invoicing of customer O
l &
• Receipt of cash and reconciling of the bank statement
a
In Order Management the pricing engine prices the items after the order is entered or booked
n
te r
(depending on the pricing setup). Once the order is booked, it proceeds through the workflow
process. If it is a shipping item and the quantities are available, the order is processed by
Shipping Execution. During shipping, the freight and special charges can be calculated and the
I n
price of the item is adjusted accordingly.
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 6
Overview of Pricing Integration
n l y
e O
Overview of Pricing Integration
U s
The following products use Oracle Pricing setup and engine processing:
• Complex MRO A I
• Core Contracts O
• Demand Planning
l &
• Financial Services
n a
• Inter-company transactions
• Logistics
te r
• Marketing
I
• Order Capture/Quoting n
c l
• Order Management e
r a
• Procurement
• Sales for Communications
O
• Service Contracts
• Service Core (Via Order Management)
Overview of Pricing
Chapter 9 - Page 7
• Service for Communications
• Trade Management
The following products use Oracle Pricing engine processing only:
• iStore
• TeleSales
• Sales Online
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 8
Overview of Pricing Concepts
n l y
e O
Overview of Pricing Concepts
U s
A I
The pricing engine determines the selling price for products and services. It provides the final
selling price after retrieving the initial price from the price list or customer agreement. If this
O
order qualifies for any increases or decreases from the initial price, adjustments called
modifiers are applied to the price.
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 9
Overview of Pricing Concepts
n l y
e O
Overview of Pricing Concepts
U s
A I
When the sales order is entered, the pricing engine is called and reads the relevant price list or
pricing agreement. The appropriate modifiers are then applied to the base price and the final
O
selling price is sent to the sales order line or the calling application. The Adjustments window
&
displays the original price, applied modifiers, and the final price.
l
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 10
Overview of the Pricing Engine
n l y
e O
Overview of the Pricing Engine
U s
A I
The pricing engine works through open APIs to provide the pricing results to the calling
application. It consists of a search engine and a calculation engine. From the pricing request,
O
the pricing engine evaluates the appropriate modifiers and price lists, resolves incompatibility
l &
issues, retrieves the list price, and calculates the unit selling price and adjustments. The search
engine receives pricing information from entities like price lists, modifiers, qualifiers,
formulas, products and pricing attributes.
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 11
Overview of Pricing Security
n l y
e O
Overview of Pricing Security
U s
A I
In Oracle Applications, the basic level of security called functional security is implemented to
control users’ access to different windows, controls, and reports in the application.
O
Additionally, Oracle Pricing has its own security setup called pricing security that works along
l &
with functional security to provide a secure environment where the user can view, update, or
add pricing entities within a framework of authorizations and permissions. Pricing entities are
a
price lists, modifiers, and agreements. You can set up pricing security if you have the Oracle
n
te r
Pricing Administrator responsibility.
Using pricing security, you can assign pricing entities to operating units, assign privileges, and
n
set security rules for pricing entities.
I
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 12
Overview of Price Lists
n l y
e O
Overview of Price Lists
U s
A I
A price list is useful for maintaining the prices and other pricing details of products and
services. It serves as a repository of items with their related pricing details. You can call up a
O
price list and add/edit/delete related items and item categories. You can also use the price list to
l &
define attributes for the products, which will then determine the pricing action.
An item should have a price when it is entered on a sales order line. Once the pricing engine
a
populates the Unit Price field by deriving the price from the appropriate price list, the order can
n
be booked.
te r
The header region of the price list consists of fields to store the price list name, the effective
I n
dates of the price list, currency, multi-currency conversion, pricing controls, rounding factor
and shipping defaults like freight terms and freight carriers.
l e
You can enter one or more pricing lines to the price list. However you may add only one
c
secondary price list. Pricing attributes can also be used to determine the price in the price list.
r a
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 13
Overview of Price Lists
n l y
e O
Overview of Price Lists
U s
A I
You can create as many price lists as needed by entering the information or copying existing
price lists. The price lists can be modified to include new items or groups of items. The list
O
price of the price list lines can be increased or decreased by either an amount or a percentage.
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 14
Overview of Pricing Agreements
n l y
e O
Overview of Pricing Agreements
U s
A I
Oracle Pricing enables you to establish agreements with your customers, where you can define
prices, payment terms, and freight terms for items. Two types of agreements can be created:
Standard Agreements or Pricing Agreements.
O
l &
• Standard Agreements use standard price lists. Standard Agreements can be generic or
specific to a customer or customer family.
n a
• Pricing Agreements use Agreement Price Lists. These price lists are set up and
te r
maintained through the Agreements window. Special terms and conditions can also be
specified in the Pricing Agreement which can then be defaulted in the sales order.
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 15
Overview of Formulas
n l y
e O
Overview of Formulas
U s
A I
You can define prices as constant values or create formulas to provide pricing flexibility and
the ability to carry out complex computations. Some of the formulas that are created are based
on the following formula component types:
O
&
• Factor List – You can apply different factor values for varying item attributes
l
• Numeric Constant – Numeric value
n a
• Pricing Context – Grouping of pricing attributes, of which a maximum of 100 can be
te r
incorporated in the formula
• Product Context – which contains only one attribute, item
I n
You can create formulas in the Pricing Formulas window.
l e
Oracle Pricing provides seeded formulas, such as the Freight and Special Charges Formulas
c
which includes the Cost to Charge Conversion formula and Cost to Charge Markup formula.
r a
These formulas carry out the process of converting freight costs to freight charges.
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 16
Overview of Qualifiers
n l y
e O
Overview of Qualifiers
U s
A qualifier defines eligibility rules for modifiers and price lists.
A I
A qualifier can be a customer name, a customer class, an order type, or an order amount that
can span orders. O
&
Though a qualifier may be set up independently, it comes into effect only when linked to a
l
n a
modifier or a price list. Thus, the modifier that is set up and linked to a qualifier determines
who the price adjustment will affect as well as the amount that will change.
te r
You can create qualifier groups to apply individual qualifiers as a set. When you group
qualifiers, they become a set, which allows for faster searching and setup.
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 17
Overview of Modifiers
n l y
e O
Overview of Modifiers
U s
A I
Modifiers determine the adjustments made to the list price. These are dependant on various
business factors such as the type of adjustments to make, the level at which the adjustments are
O
made, how the modifiers are qualified, how they are applied, etc. You can create three modifier
list types in Oracle Pricing:
• Discount List
l &
• Surcharge List
n a
te r
• Freight and Special Charges List
There are four modifier line types available in Oracle Pricing:
• Discount
I n
• Surcharge
c l e
• Freight and Special Charges: Amount applied to the customer invoice for movement of a
r a
shipment to a destination
O
• Price Break: Only point price breaks are allowed in Basic Pricing modifiers. For
example, the following pricing decisions are:
If Item Quantity = 1-50, then discount = 5%
Overview of Pricing
Chapter 9 - Page 18
If Item Quantity = 51-100, then discount = 7%
If Item Quantity is between 101 and 99999999999, then discount = 10%.
So if the ordered item quantity is 110, then the discount applicable is 10%.
Modifier controls are of the following types:
Pricing Event is a time in the process flow of the calling application at which it makes a call to
the pricing engine (analogous to an Oracle Workflow event); for example, Book Order in
Order Management.
Pricing Phase is a user-defined group of modifiers that the search engine considers together
when applying them to pricing requests, for example, Phase 1: Line Adjustments.
Incompatibility: In any given level within the same phase, the system only allows one modifier
to be selected. The pricing engine may retrieve more than one modifier that meets the calling
request and can be applied. There are three methods to resolve incompatibilities within the
modifiers that the pricing engine retrieves:
• Precedence
• Best price
• Exclusivity
Incompatibility Level: Each modifier has an incompatibility level. If there is more than one
modifier line with the same incompatibility level, the pricing engine selects the one with the
highest precedence. If there is more than one modifier with the highest precedence in an
incompatibility level, the pricing engine selects the modifier that provides the best benefit to
the customer.
l y
In Basic Pricing, users cannot add additional phases or events, and incompatibility level and
buckets are defaulted.
n
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 19
Overview of Contexts and Attributes
n l y
e O
Overview of Contexts and Attributes
U s
There are three types of Pricing Contexts or groups in Basic Pricing:
• Product A I
• Pricing O
• Qualifier
l &
a
Attributes are fields in the Standard or Quick Sales Orders window that can be used to
n
te r
determine the price of an item. A context is comprised of a grouping of attributes. However,
the product context type has only one context – item.
I n
Through Attribute Management, the Pricing Engine evaluates all the values defined in the
qualifier and pricing attributes.
l e
Basic Pricing allows the creation and linking of only Pricing contexts with a maximum of 100
c
attributes or less.
r a
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 20
Overview of Freight and Special Charges Modifiers
n l y
e O
Overview of Freight and Special Charges
U s
A I
Freight and Special Charges are applied to the customer’s invoice, charging for the movement
of goods from the supplier to the destination. Freight and Special Charges can be applied to the
O
order as a whole or to individual order lines. Costs that are associated with the shipment of
l &
goods can be entered in the Sales Orders window or the Shipping Transaction window. Freight
charges can be automatically derived from the freight cost. The freight charge represents the
a
amount charged to the customer receiving the shipment. The freight charge can be equivalent
n
r
to the freight cost or to a greater amount, for example, freight cost plus a markup.
te
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 21
Overview of Basic vs. Advanced Pricing
n l y
e O
Overview of Basic vs. Advanced Pricing
U s
A I
Oracle offers two levels of pricing functionality: Basic and the separate enhanced product,
Advanced Pricing. While both levels of functionality share some similarities, the licensed
O
Advanced Pricing application extends the ability to adjust pricing.
Price Lists
l &
n a
The creation of price lists within both levels carries many of the same elements. Both are able
to add items to, and copy price lists. However, as you implement Advanced Pricing, the ability
te r
to use Qualifiers, Pricing Attributes, and Secondary Price Lists becomes extended from only
allowing the default or one context element in Basic, to an unlimited number of values being
available.
Agreements I n
l e
The use of Agreements is the same for both Basic and Advanced Pricing. They are both able
c
r
Formulas a
to identify customer items, create price lists, use versioning, and define price breaks.
O
Both Basic and Advanced Pricing allow Static Formulas, while only Advanced Pricing allows
the use of Dynamic Formulas.
Overview of Pricing
Chapter 9 - Page 22
Modifiers
While both basic and Advanced Pricing have the ability to execute Discounts, Surcharges,
Freight Charges, and point-based price breaks, Advanced Pricing extends this functionality
greatly. Advanced Pricing also allows price modifications via Coupons, Terms Substitution,
Promotions, Item Upgrades, and Other Items discounts. Additionally, Advanced Pricing
allows you to implement adjustment functionality that will change the list price used for the
adjustment; affect the timing of when the adjusting activity will occur; and enable you to
define rules affecting which adjustments may be used at the same time. In Advanced Pricing,
you can also flag discounts as exclusive, which implies that only that discount will be eligible
and no others.
Note: Additionally, Advanced Pricing enables you to derive prices from external sources. For
further information on the Advanced Pricing functionality, please refer to the Advanced
Pricing User and Implementation Manuals.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 23
Summary
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Overview of Pricing
Chapter 9 - Page 24
Basic Pricing
Chapter 10
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 1
Basic Pricing
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 2
Objectives
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 3
Agenda
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 4
Pricing Security Overview
n l y
e O
Pricing Security Overview
U s
The following terms are used in pricing security:
• Pricing entity: can be a price list, modifier, or agreement. A I
O
• Entity type: a type of pricing entity like a Pricing Agreement, Standard Price List etc.
l &
• Entity usage: grants the entity’s usage to one or all operating units so it can be
used during pricing engine calls.
n a
te r
• Global Usage: when this is enabled for a pricing entity, the entity can be used across all
operating units. When this is set to No, then the usage of the pricing entity is restricted to
I n
the operating unit that created it. However if the global usage as well as the operating unit
are specified, then global usage takes precedence.
le
• Grantee: the user who is granted permission to view or maintain a pricing entity
c
• Grantee Type: the level at which privileges are granted:
r - Globala
O - Operating Unit
• Access Level: is of two kinds – View-Only and Maintain access given to a grantee for a
pricing entity.
Basic Pricing
Chapter 10 - Page 5
Security Implementation Steps
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 6
Security Implementation Steps – Mapping Security Requirements
n l y
e O
Security Implementation Steps – Mapping Security Requirements
U s
A I
All pricing entities are first identified and then mapped to different grantee types according to
the requirements. For example, a pricing agreement can be mapped to an operating unit so that
O
all users of that operating unit only can view and maintain the pricing agreement.
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 7
Security Implementation Steps – Assigning Pricing Entities to an
Operating Unit
n l y
e O
U s
A I
Security Implementation Steps – Assigning Pricing Entities to Operating Units
O
There are two scenarios where you can assign pricing entities to operating units: before
implementing Pricing Security and after implementing Pricing Security.
l &
Pricing entities that have been created before implementing Pricing Security normally would
n a
not have operating units assigned to them. In such a situation, the Pricing Administrator can
assign ownership of pricing entities to the appropriate operating unit. Also the Global Usage
te r
option can be used to enable or disable the use of the pricing entity across operating units.
After Pricing Security is implemented, a Global box is added to the header of the price list or
I n
modifier entity. Though the Global check box is selected by default, the user can clear this to
e
restrict the entity to the user’s operating unit. Also all pricing entities that have been created
l
after implementing Pricing Security have a unique system-generated Operating Unit identifier
c
assigned to them. When querying newly-created pricing entities in the Pricing Security pages,
r a
the operating unit ownership is displayed in the Owned By Operating Unit field.
O
Assign Global Usage or owned by Operating Units to multiple pricing entities collectively
using the Bulk Update Entity Usage button on the Entity Usage page.
Basic Pricing
Chapter 10 - Page 8
Security Implementation Steps – Creating Privileges
n l y
e O
Security Implementation Steps – Creating Privileges
U s
Responsibility, and User. A I
You can grant privileges to different grantee types such as Global, Operating Unit,
O
After the mapping of security requirements, it is necessary to give the privileges to the pricing
l &
entities. This implies that you can define rules for a pricing entity that will restrict a specific
user or group of users to accessing entities for a specific customer, group of customers or a
specified customer hierarchy level.
n a
te r
You can assign privileges using the following privileges pages:
• Privileges page – the default page to assign privileges
I n
• Express Create Privileges page – to assign privileges to a specific pricing entity
c le
• Bulk Create Privileges page – to assign privileges to multiple entities collectively
In case a user has multiple privileges, it is always the Maintain privilege that will take
r a
precedence. For example, if a user has Maintain access at his operating unit level, but has a
view-only access at his user level, the Maintain access privilege will have precedence.
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 9
Security Implementation Steps – Setting up Default Security
Profile Options
n l y
e O
U s
A
Security Implementation Steps – Setting up Default Security Profile Options I
O
• QP: Security Default ViewOnly Privilege: This is applicable for newly created pricing
entities. This profile option enables you to set the view-only privileges at one of the
l &
following grantee levels: Global (Default), Operating Unit, Responsibility, User, or
None. This controls which users can view newly-created price lists and modifiers.
n a
• QP: Security Default Maintain Privilege: This is applicable for newly created pricing
te r
entities. For example, if the profile option is set to Operating Unit, then the maintain
privileges for that price list or modifier are restricted to the pricing users of the operating
I n
unit where the price list or modifier was created. This profile option enables you to set
maintain privileges at one of the following levels: Global (Default), Operating Unit,
le
Responsibility, User, or None.
c
• For already existing pricing entities, the Privileges window should be used to change the
r a
access privileges.
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 10
Security Implementation Steps – Turning Security On
n l y
e O
Security Implementation Steps – Turning Security On
U s
steps have been completed: A I
Before turning the profile option QP: Security Control on, you must ensure that the following
n a
te r
If these steps are not completed, then users will not be able to use any pricing entities. Once
Pricing Security is activated, it should not be turned off.
I n
When the profile option QP: Security Control is set to ON, the Global box is dynamically
added to the headers of all price lists and modifiers. Though this box is visible to all, it can be
c le
cleared or selected only by users with Maintain privileges.
Before the profile option is turned on, it is essential that the pricing entities are assigned to an
r a
operating unit. After the profile is turned on, a newly created pricing entity gets assigned the
creating operating unit automatically.
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 11
Security Features and impact on Forms/Windows
n l y
e O
Security Features and impact on Forms/Windows
U s
A I
• Changes made to existing Pricing windows: When pricing security is turned on, a Global
box appears on the pricing windows, enabling you to decide if the pricing entity is to be
available across all operating units.
O
l &
• Changes to price lists: A price list that has Global box checked is accessible to all
operating units, even though it may be assigned to a specific operating unit. If a price list
a
is copied, it is assigned the default privileges from the pricing security options.
n
te r
• Changes to Modifier windows: A modifier with Global Usage assigned to it is accessible
to all operating units, even though it may be assigned to a specific operating unit. After
I n
pricing security is turned on, the default view and maintain properties for modifiers are
determined by the pricing security profile options.
le
• Changes to Order Management: All list of values (LOV) for price lists in Oracle Order
c
Management will call the Pricing API, Get_Pricelists(), to return a list of valid price lists.
r a
The API returns the price lists owned by the same operating unit as the operating unit of
O the current user and those price lists where the Global box is selected.
Basic Pricing
Chapter 10 - Page 12
Agenda
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 13
Price List Creation
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 14
Price List Header
n l y
e O
Price List Header
U s
responsibility. A I
Order Management Super User, Vision Operations (USA) or Oracle Pricing Manager
te r
consider price lists that share the same currency as the Pricing Request. Therefore a sales order
placed in Yen will have to utilize a Yen based price list.
I n
There is a Round to field in Price List window. This field controls the rounding factor.
le
Entering a positive number affects positions to the left of the decimal. Entering a negative
number affects positions to the right of the decimal. Example –2 would round to the second
c
r a
decimal point. The type of currency – standard or extended – which has to be defaulted on the
price list is determined by the Profile Option: QP: UNIT_PRICE_PRECISION_TYPE.
O
Secondary Price Lists
As with other areas of pricing, the Basic Pricing license controls available functionality to the
user. Basic Pricing allows one Secondary price list. A secondary price list allows the pricing
Basic Pricing
Chapter 10 - Page 15
engine to look at more that one price list to determine the value of the sales order line. The
Pricing engine will look to the Secondary Price list if the requesting item and unit of measure is
not on the Primary Price list. A secondary price list is a price list you have defined previously.
Any price list has the ability to be used as a secondary price list.
Price Lists and Sales Order Defaults
Fields such as Payment Terms, Freight Terms, and Freight Carrier are available on the Price
List form. By defining the Order Management defaulting rules to use these fields from the
Price List window, you are able to default values directly into the sales order based upon which
price list has been selected for the order. For more information on Defaulting Rules, see the
Order Management User’s Guide.
Note: Price Lists cannot be deleted, however a price list is made valid or invalid with the use of
its effective dates. Alternatively, selecting or deselecting the Active box also temporarily or
permanently makes the price list available or unavailable for use.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 16
Price List Line
n l y
e O
Price List Line
U s
Order Management Super User, Vision Operations (USA)
(N) Pricing > Price Lists > Price List Setup (T) List Line A I
O
The Product Attribute enables you to enter one price per Item number, one price per Item
&
Category, or one price for All Items. If you have entered all three prices on a Price List, the
l
Item Category’s over All Items.
n a
Pricing Engine will always select the Item Number’s price over the Item Category’s and the
te r
The List line UOM is a required element of the validation process. The Pricing request is for an
Item/UOM and only price lists that have the same item and unit of measure will be considered.
I n
If you have the Primary UOM checked and you enter an item/unit of measure combination on
le
a sales order that is not on a Price list, the Pricing engine converts the unit of measure on the
order to the item’s primary UOM and then uses the UOM conversions to calculate the unit
c
price.
r a
Example: Price List setup: BB-2200, $6.00 each, Primary UOM is selected. Sales Order
O
request: BB-2200 1 dozen. Result: 12*6.00 = $72.00 unit price.
You can use the Precedence column to specify a number. This number is taken into
consideration when comparing lines that are similar (i.e. the same price for the same item). A
Basic Pricing
Chapter 10 - Page 17
price list line with a lower value in the Precedence column will have a higher precedence – the
price from the line will be used by the pricing engine first to price the line.
You can select product, pricing and qualifier contexts in the price list and choose the
corresponding attributes that you want to determine the pricing action. The product context
contains only one context type – Item. The pricing context contains all the pricing attributes
that have been created and linked through the Attribute Management windows. The qualifier
context allows you to link your customer hierarchy to the pricing action and ensure that the
customer attributes also play a part in determining pricing of the item.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 18
Price List Line (contd.)
n l y
e O
Price List Line (contd.)
U s
A I
You can enter an absolute value that represents the unit price of your List line item. For service
program items you have a choice of pricing methods. You can enter an absolute value that
O
represents the unit price of your service program or you can enter a percentage value that
l &
represents the percentage of another item’s price. When you are selling a service program on a
sales order you are prompted for the item that the service program will cover. The Pricing
a
Engine finds the price of the covered item and calculates the price of the service program by
n
te r
multiplying the percent times the item’s unit price. It then takes that amount times the duration
of the coverage. Example of percent of other price:
Price List setup:
I n
• Service Program’s item number is set up at 10% per year.
le
• Sales Order request: Customer purchases 1 year’s worth of coverage for an Item which
c
sells for 1200.00.
r a
• The Pricing Engine calculates .10 * 1200 * 1 (year) = 120.00.
O
Formulas can be used to if you need an algebraic expression to calculate the selling price.
Basic pricing supports entering a formula name in the Static Formula field. Static Formulas
Basic Pricing
Chapter 10 - Page 19
require that a concurrent program, Update Formula package, be run to populate the List Price
value prior to being used by the Pricing Engine.
The Price list supports both positive and negative values. This enables you to create an item
which represent a re-stocking fee. Enter this item on your price list with a negative value, then
enter this item on your Return order. When the Pricing Engine calculates the total value of the
return it will subtract the re-stocking fee thus lowering the value of the credit memo.
Start and End dates are respected by the Pricing Engine.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 20
Copy Price List
n l y
e O
Copy Price List
U s
Order Management Super User, Vision Operations (USA)
(N) > Pricing > Price Lists > Copy Price List A I
O
Copying a Price List enables you to create a new price list without adding lines manually to the
&
price list. You are able to utilize controls within the Copy Price List window to determine
l
n a
which line items will be copied during the process.
One option is to include the copying of discounts (modifiers) when copying an existing price
te r
list. This option will create new modifiers for each existing modifier that has the original price
list as either a Modifier List Qualifier or a Modifier Line Qualifier. The new modifier’s name
I n
will be a concatenation of the original modifier plus a sequence number and the new price list
will have a Modifier List Qualifier.
le
When creating the new price list you can specify any applicable effective dates. As the Pricing
c
r a
Engine will not use the new price list until its Effective Date, this will allow you to create price
lists before they are required and used in the application.
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 21
Guided Demonstration – Copy a Price List
Responsibility: Order Management Super User, Vision Operations
(USA)
(N) > Pricing > Price Lists > Copy Price List
1. In the Copy From region, enter Corporate in the Price List field.
3. Select the check box Retain Effective Dates to copy the effective dates of price list lines. If
selected, Price List Lines that no longer have a current effective date will not be copied to
the new price list.
4. In the Copy to region, enter XX-New Corporate in the Price List field.
8. Verify that the request completed normally by using (M) View > Requests. Enter your
request ID and then click (B) Find.
n l y
9. O
Verify that the new price list was created by using (N) Pricing > Price Lists > Price List
e
Setup
Basic Pricing
Chapter 10 - Page 22
Practice - Copy Price List
Overview
In this practice you will learn how to create a new Price List by copying an existing price list.
Assumptions
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
• Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
Tasks
1. Navigate to the Copy Price List window. Create a copy of the Corporate price list retaining
the effective dates and using the item category set to copy only items belonging to a
particular item category. Name the new price list XX-New Corporate.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 23
Solution - Copy Price List
Login to the database
Select Responsibility
3. (N) > Pricing > Price Lists > Copy Price List
− Copy From - Price List: Corporate
5. Item Category: Choose a category for which you know items exist
Basic Pricing
Chapter 10 - Page 24
8. Click (B) Submit.
9. Click (M) View > Requests > (B) Find (using your request ID).
10. Verify that the concurrent request has completed normally. Then verify that a new price list
was created.
11. (N) > Pricing > Price Lists > Price List Setup
12. Click the flashlight icon to find XX-New Corporate price list.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 25
Agenda
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 26
Price List Maintenance - Overview
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 27
Manual Price List Updates
n l y
e O
Manual Price List Updates
U s
responsibility. A I
Order Management Super User, Vision Operations (USA) or Oracle Pricing Manager
(N) Pricing > Price Lists > Price List Setup (T) List Line O
&
To change existing Price Lists manually, navigate to the Price List Setup window and find the
l
price list to maintain.
n
You can add or update the following: a
te r
• Add or update Secondary Price List.
I n
• Add new list lines to existing Price Lists.
• Change list line values. Note: If you overwrite the existing value with a new one, the
le
previous data is not retained anywhere.
c
• Maintain Pricing History by manually entering an end date on the list line value that is
r a
being discontinued, then add a new line with the same item number and unit of measure
but with the new value. The new list line’s start date must be greater than the end date of
O the original line.
• The Pricing Engine always validates the Price List and List Line’s Effective Dates.
Basic Pricing
Chapter 10 - Page 28
Guided Demonstration – Manual Price List Update
Responsibility: Order Management Super User, Vision Operations
(USA)
(N) > Pricing > Price Lists > Price List Setup
3. Use F11 to enter query mode and put your cursor in the Product Value field. Enter
AS18947 and use Ctrl + F11 to execute your query.
4. Scroll to the right and put an End Date of the last day of this month for this price list line.
6. Insert a new List line with the same item and UOM. Use a value of 1820 for the unit price
and give it a starting date of the first day of the next month.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 29
Practice - Manual Price List Update
Overview
In this practice you will learn how to manually update a Price List.
Assumptions
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
• Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
n l y
Tasks
e O
1.
U s
Navigate to the Price List Setup window. Find your XX-Base Prices price list. Put an end
A I
date on the list line for item AS18947. Add a new line for the same item/uom with a future
start date and Unit Price of 1820. This preserves the pricing history of an item.
2. O
Change the selling price for item AS54888 to 1550 without maintaining the pricing history.
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 30
Solution - Manual Price List Update
Login to the database
• Password: welcome
Select Responsibility
3. (N) > Pricing > Price Lists > Price List Setup
n l y
6.
7.
Save.
(I) Save.
te r
I n
Change Selling Price
c le
10. Query all rows: Ctrl + F11.
r a
O
11. Change the Value for AS54888 to 1550.
Basic Pricing
Chapter 10 - Page 31
Adjust Price List
n l y
e O
Adjust Price List
U s
Order Management Super User, Vision Operations (USA)
(N) Pricing > Price Lists > Adjust Price List A I
O
Use the Adjust Price List program to mass update your price list values. Note that using the
&
Adjust Price List program to change values does not create a history record. You will not be
l
n a
able to recapture the old price. If you need to retrieve expired prices, do not use Adjust Price
List option. This option enables you to increase or decrease the current price by a percent or an
amount.
Elements you can update:
te r
I n
• Optionally adjust only a Range of Items.
c le
• Optionally adjust only an Item Category. Many companies adjust their Items’ selling
prices annually or when the product cost has drastically changed. This is often done by
r a
Product Family. If you set up an Item Category to represent the Product Family you can
quickly markup the subset of Price List Lines.
O
• Optionally adjust only Items with a specific Item Status.
Basic Pricing
Chapter 10 - Page 32
• Any time a new line is added to a price (manually, copy, or Add Items) the system
populates the Creation Date with the system date.
• Use the Creation Date to select only items that were added on a given date. This is very
helpful when you have used the Add Items to Price List program to add new items At
Cost. This enables you to markup the new items while leaving the older lines untouched.
• Use the Copy program to create as many price list as your business procedures support
and then Adjust the Price List Value by a Percent or an Amount.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 33
Guided Demonstration – Adjust Price List
Responsibility: Order Management Super User, Vision Operations
(USA)
(N) > Pricing > Price Lists > Adjust Price List
7. (N) > Pricing > Price Lists > Price List Setup
8. Use the Flashlight to find XX-New Corporate. Check the line items to view the adjusted
price.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 34
Practice - Adjust Price List
Overview
In this practice you will learn how to perform a mass adjustment of a price list.
Assumptions
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
• Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
Tasks
1. Navigate to the Adjust Price List window. Adjust the XX-New Corporate price list by 5%
for all items.
2. Review the price list to verify that the adjustment completed correctly.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 35
Solution - Adjust Price List
Login
• Password: welcome
Choose Responsibility
2. (N) > Pricing > Price Lists > Adjust Price List
− Price List: XX-New Corporate.
− Adjust by: Percent.
− Value: 5.
Note: If the price list XX-New Corporate does not exist, you can create it by using the
option Pricing > Price List Setup.
Basic Pricing
Chapter 10 - Page 36
− Write your Request ID: ____________________________________.
4. Click (M) View > Requests > (B) Find (all requests).
n l y
Validate that your concurrent request completed normally.
e O
5. (N) > Pricing > Price Lists > Price List Setup.
U s
6. Use the flashlight to find XX-New Corporate.
A I
7. Click (T) List Lines.
O
&
Notice that the prices have been adjusted by an increase in 5%.
l
8. Close windows.
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 37
Add Items to Price List
n l y
e O
Add Items to Price List
U s
Order Management Super User, Vision Operations (USA)
(N) Pricing > Price Lists > Add Items to Price List A I
O
The Add Items to Price List window enables you to quickly add items to an existing price list.
&
When using the Add Items to Price list functionality you can use a number of control attributes
l
n a
within the window to identify which items should be added to the list. These options include
addition by the range of item numbers, item category, and item status. Note that you can only
te r
add items from this window to one list at a time. To add all of the items that have a category of
Shippable to five different price lists, use the Add Items to Price List window five times, to
I n
add the Shippable category to each price list individually.
Using the Set Price Equal to Cost option, you can retrieve the current cost of the item by
le
selecting an inventory organization that stores item costs; the current cost retrieved is stored in
c
the same price list as the item.
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 38
Guided Demonstration - Add Items to New Price List
Responsibility: Order Management Super User, Vision Operations
(USA)
(N) > Pricing > Price Lists > Add Items to Price List
4. Select the checkbox for adding items equal to cost using Seattle Manufacturing as the
Inventory Organization.
6. When the concurrent request has completed find your price list to see the results.
(N) > Pricing > Price Lists > Price List Setup
7. Use the Flashlight to find the Price list that was updated.
8.
n l y
If the item has a zero unit price, it is because the item had no costs associated with it in
Inventory.
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 39
Add Items to Price List
n l y
e O
Add Items to Price List for Maintenance
U s
Order Management Super User, Vision Operations (USA)
(N) Pricing > Price Lists > Add Items to Price List A I
O
You can use the Add Items to Price List program to add Product Lines to existing price lists.
&
When new product lines are added to your inventory, assign unique Categories to them, so that
l
n a
you can add them to your existing Price Lists using the Add Items feature by Item Category.
If you are in an industry where your selling prices are set at a given Percent over cost, add your
I n
Note that the Add Items to Price List program does not overwrite any List Lines that have the
le
same Item Number and Unit of Measure as the Inventory Item Number and its Primary unit of
measure. This means that you cannot accidentally overwrite current valid values.
c
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 40
Practice - Add Items to a Price List
Overview
In this practice you will learn how to add items from inventory to an existing price list. Then
using Adjust List price you will adjust your price list prices.
Assumptions
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
• Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
n l y
Tasks
e O
1. Navigate to the Add Items to Price List window. Add Active Items from the Inv.Items
U s
Category Set to your XX-Base Prices price list. Set the list price equal to the Cost of the
items from the Seattle Manufacturing inventory organization.
A I
2.
O
Navigate to the Adjust Price List window. Mass adjust all items on your price list by 10
currency units.
Basic Pricing
Chapter 10 - Page 41
Solution - Add Items to a Price List
Login to the database
• Password: welcome
Select Responsibility
3. (N) > Pricing > Price Lists > Add Items to Price List
− XX-Base Prices.
− Item Status: Active.
Note: If the price list XX-Base Prices does not exist, create it without including any items
using the Pricing > Price List Setup option.
n l y
5.
6.
Inventory Organization: Seattle Manufacturing.
Click (M) View > Requests > Specific Requests > Request ID > (B) Find.
Basic Pricing
Chapter 10 - Page 42
8. Confirm that your request completed normally.
Mass Adjust
9. (N) > Pricing > Price Lists > Adjust Price List
− Price List: XX-Base Prices.
− Adjust by: Amount
− Value: 10
n l y
e O
• U s
Write the Request ID: _____________________________________.
l &
12. Use the flashlight to find XX-Base Prices.
n a
13. Click (T) List Lines.
te r
I n
14. Scroll to right to see the new prices.
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 43
Agenda
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 44
Agreement Overview
n l y
e O
Agreements Overview
U s
You can set up two kinds of Agreements, Standard or Pricing:
A I
• A Standard Agreement could have special Freight or Payment terms. You can associate
O
an existing Price List to a Standard Agreement. Optionally, you can create Discounts that
&
are qualified by the Agreement Name or Agreement Type.
l
n a
• A Pricing Agreement allows you to create a Price List as part of the Agreement setup.
The Agreement Price List has fields that are not on a regular Price List. These fields
te r
allow you to optionally enter Customer Item Numbers that have been created in
Inventory and cross referenced to an Internal Item Number.
I n
Agreements can be Generic or Customer Specific. If it is Generic then all customers are
eligible to use it. If it is Customer Specific then only the Customer Name entered on the
le
Agreement will be eligible.
c
r a
The Agreement Type has many functions. It can be used as a Qualifier for a Discount
(Modifier). It can be used by the Order Transaction Type to restrict a group of orders to only
O
allow Agreements of a specified Type. It can be used to group similar agreements for reporting
purposes.
Basic Pricing
Chapter 10 - Page 45
Besides restricting which Agreements a sales order can use, the Order Transaction Type can
also specify whether an Agreement is required to book a Sales Order.
Many of the fields entered on your Agreements can be used to default the appropriate data on
to a new sales order/line. Your agreement can default Customer PO, Freight Terms, Freight
carrier, payment terms, Salesperson, Invoicing Rules, and Accounting Rules.
By using the Revision number, Revision Date, and Revision Reason you can maintain a history
of all the changes to your Agreements.
Note: You can enter an agreement number of your choice, which you can then use to reference
a legal document given to your customer.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 46
Agreement
n l y
e O
Agreement
U s
Order Management Super User, Vision Operations (USA)
(N) Pricing > Pricing Agreement A I
O
If you do not enter a Customer you are creating a Generic Agreement.
l &
Effective Dates are used by the Pricing Engine to ensure that only currently valid Agreements
n a
are used. The Effective dates are also used by the Revision Control logic.You cannot create a
new revision unless the current revision has an Effective end date.
te r
If you set the Price List Type to Agreement Price List you can create a price list as part of the
Agreement setup.
I n
If you set the Price List Type to Standard Price List you will be prompted to enter the name of
c le
an existing Price List.
Note: You cannot add items to a Standard Agreement as an existing price list is attached to it.
r a
In fact the items block will appear as read-only.
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 47
Guided Demonstration – Agreement Price List
Responsibility: Order Management Super User, Vision Operations
(USA)
(N) > Pricing > Pricing Agreements
Note: You can create two kinds of agreements, Pricing and Standard. Pricing agreements
allow you to add agreement lines to define the agreement prices. A Standard agreement uses
a standard price list and will not allow addition or updation of agreement lines.
1. In the Agreement tabbed region, enter an agreement name in the Agreement Name field.
3. Enter Business World in the Customer field. The customer number (1608) displays in the
Cust Number field. If you leave these fields blank, you are creating a generic agreement that
can be used by all customers.
4. Select an agreement type of Standard Terms and Conditions in the Agreement Type field.
e O
8.
9.
Click on the Pricing tab.
Select the Agreement Price List type in the Price List Type field:
U s
existing list of values of Pricing Agreement Price List.
A I
− For Pricing Agreements: You can create a new price list name or choose from an
n a
te r
10. Enter a default freight carrier in the Freight carrier field.
r a
14. In the Rules region, enter IMMEDIATE in the Accounting Rule field.
O
15. Enter ARREARS INVOICE in the Invoicing field.
Basic Pricing
Chapter 10 - Page 48
16. To set the accounting rule override flag select the Accounting Rule check box.
17. To set the invoicing rule override flag select the Invoicing Rule check box.
18. At the bottom of the form, enter AS54888 in the Product Value field.
23. Enter a new line for item AS54999 with the same UOM, Application Method and Line Type
and a price of 1500.
24. Enter the effectivity dates in Start Date and End Date. They should be within the effectivity
dates of the agreement.
n
r
Note: Notice the Agreement number is displayed under the total field.
te
n
32. Select your agreement name from the LOV.
I
le
33. Click (T) Line Items.
c
a
34. Enter item AS54888 from your Agreement price list.
r
ONote that the price is retrieved from the Agreement price list.
Basic Pricing
Chapter 10 - Page 49
Practice - Agreement Price List
Overview
In this practice you will learn how to create an Agreement Price List
Assumptions
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
• Use Order Management Super User, Vision Operations (USA) or comparable Super
Tasks
User Order Management responsibility.
n l y
1.
e O
Create a new customer agreement with Standard Terms and Conditions for Business World
of 1450 and AS54999 with a unit price of 1500. You may select any Payment Term,
U s
(Customer #1608) that has its own price list with pricing lines for AS54888 with a unit price
A I
2.
O
Enter a new Sales Order using your Agreement. You may need to use folder tools to show
the Agreement field on the Main tab of the Sales Order.
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 50
Solution - Agreement Price List
Login to the database
• Password: welcome
Basic Pricing
Chapter 10 - Page 51
4. Click (T) Pricing.
n l y
5. Agreement Price List.
− XX-AGREEMENT PL.
e O
6. Enter a Description.
U s
7. Accept defaults.
A I
O
l &
n a
te r
I n
c le
r a
8. O
Click (T) Payment.
Basic Pricing
Chapter 10 - Page 52
10. Select Accounting Rule from the LOV.
n l y
e O
U s
16. Save.
A I
Enter a new Sales Order using Agreement
O
(N) > Orders, Returns > Quick Sales Orders
l &
n a
IMPORTANT: If you don’t see the Agreement field on the order header use the folder
te r
functionality to display the field.
I n
17. Customer: Business World (1608).
le
18. Customer PO: XX-012.
c
a
19. Agreement: XX Pricing Agreement.
r
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 53
Notice that the Price List was updated from the agreement.
Note: The pricing engine uses the price from the Agreement price list.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 54
Agenda
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 55
Formula Overview
n l y
e O
Formula Overview
U s
from the static formula. A I
Enter the formula name on the list line of the Price List for those items deriving their price
O
You must run the Update Formula Prices concurrent program after entering your Formula
l &
name in the Static Formula field of the price list. The concurrent request updates the formula,
making it usable in the price list. Additionally, a formula can be linked to a Freight and Special
a
Charges modifier when the modifier is created for the order header.
n
te r
With Basic Pricing you are restricted to three formula component types: Numeric Constant,
Pricing Attribute, and Factor List.
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 56
Basic Pricing Formula
n l y
e O
Basic Pricing Formula
U s
Order Management Super User, Vision Operations (USA)
(N) Pricing > Pricing Formulas > Formulas Setup A I
When using the basic pricing formula: O
l &
• The formula is an arithmetic expression made up of step numbers. Each step number is
n a
entered in the Formula Lines region. You can repeat step numbers in the formula.
Example: 1 * 2 + 3 – 1. Thus step 1 (or line 1) contains a numeric constant and step 2
te r
contains a pricing attribute. The numeric constant will be multiplied by the pricing
attribute as the formula step numbers indicate that 1*2.
I n
• The Name is a unique identifier.
c le
• The Pricing Engine uses the Effective dates.
• Use the Formula field to enter your formula expression. Each numeric value entered must
r a
be defined using a Formula Type on the Formula Line tab. You can use mathematical
operators, numeric operands, and built-in functions to create your formula.
O
• The formula type Numeric Constant can be any numeric value. It can be a whole number
or a decimal number (1 or .1).
Basic Pricing
Chapter 10 - Page 57
Pricing Attributes
n l y
e O
Pricing Attributes
U s
A I
Pricing attributes are characteristics of products and services that you can specify when the
characteristics help to determine the price of a product or service. Distance, age or usage,
O
number of users, and level of service are examples of pricing attributes.
l &
You can specify one or a combination of pricing attributes and assign them to a product or
service. The absolute value of a pricing attribute (such as thickness or height) of an item can be
used as a Step in the formula.
n a
Example:
te r
This formula uses a Constant Value and a Pricing attribute to calculate an item’s unit price.
I n
You sell glass plates that can vary in thickness. You want the price to vary depending on the
c le
thickness. Create a formula 1* 2 to calculate the price of a glass item.
• Step 1 is a pricing attribute for thickness.
r a
• Step 2 is a numeric constant that represents the base value for the item.
Calculation: If 100 is the base price of the glass item and 0.3 is the value of the thickness
O
attribute of the glass then the pricing engine evaluates the formula as 0.3*100 which is 30.
Basic Pricing
Chapter 10 - Page 58
Factor List
n l y
e O
Factor List Formula Type
U s
A I
Use Factor Lists to associate values and factors with a Pricing Attribute. The Pricing engine
compares the values entered on a sales order to the values in the Factor List to select the
correct factor to use.
O
sales order price.
l &
For example you may need to factor in the Skill level of your Consultants when calculating the
Staff
te r
Apprentice .85
1.0
Markdown $ 85
Regular Price 100
I n
Principal 1.5 Markup 150
le
The Formula’s Pricing Context must match the Pricing Context on the Price List Line that the
c
formula is being attached to.
r a
You can utilize the OR logic in the conditions that you define your factor list. Each value that a
Pricing Attribute can have is entered as a Base Price Attribute line. Example of OR logic:
O
• Base Price Attribute Thickness = Value: 0.1 mm Factor: 1
• Base Price Attribute Thickness = Value: 0.2 mm Factor: 2
Basic Pricing
Chapter 10 - Page 59
• The pricing engine will retrieve a Factor if the customer orders a thickness of 0.1 mm
OR .2 mm.
You can utilize the AND logic if you link an Associated Pricing Attribute line to the Base Price
Attribute line. Example of AND logic:
• Base Price Attribute Thickness = Value: 0.1 mm Factor: 7
• Associate Pricing Attribute Length = Value: 0.5 mm.
The pricing engine will use the Factor 7 if the customer orders a thickness of 0.1 mm AND a
length of 0.5 mm.
You can assign a single value to the Pricing Attribute or a range of values by using the
Operator field. The Operator = (equal) is a single value. The Operator BETWEEN allows you a
range of values.
You can also use multiple values within factor lists. Example of multiple values:
• Base Price Attribute Thickness BETWEEN Value: 0.1 and .3 mm Factor: 3
• Base Price Attribute Thickness BETWEEN Value: 0.4 and .6 mm Factor: 6
• The Pricing Engine will use the Factor 6 if the customer orders a thickness of 0.5mm.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 60
Guided Demonstration – Pricing Formula
Responsibility: Order Management Super User, Vision Operations
(USA)
(N) > Pricing > Pricing Formulas > Formula Setup
4. Select Modifier Value as the Formula Type for line 1 with a value of 1 in the Step field.
5. Select Numeric Constant as the Formula Type for line 2 with a value of 1.5 in the
Component field and a value of 2 in the Step field.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 61
Static Formula Update Program
n l y
e O
Static Formula Update Program
U s
Order Management Super User, Vision Operations (USA)
(N) Pricing > Pricing Formulas > Update Formula Prices A I
O
After a formula has been entered or updated, the updated formulas are not automatically
&
incorporated in the price list or modifiers. To ensure that the updates are reflected in the pricing
l
n a
entities, run the Update Formula Prices concurrent program. This concurrent program loads the
updated formulas to a price list or modifier and calculates the list price, displaying it in the
te r
price list or modifier. Using the Update Formula Prices window, you can choose to update
either a specific formula or all formulas.
I n
After the concurrent program completes successfully, you can enter orders in the Sales Orders
window and the updated prices will be in effect during the pricing of an order line.
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 62
Agenda
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 63
Qualifier Overview
n l y
e O
Qualifier Overview
U s
A I
Qualifiers are an intrinsic part of pricing logic. Qualifiers create rules that protect your Price
Lists and Modifiers from being misused. To create your qualifier rules, group any of the seeded
qualifiers using AND and OR condition.
O
&
• If the Grouping Numbers are the same, AND logic is applied.
l
n a
• If the Grouping Numbers are different, OR condition is applied.
• If the Grouping Number is –1, then that qualifier is always used with an AND condition
te r
with the other qualifiers. The qualifier with a grouping number of –1 is mandatory and
must be satisfied, irrespective of other qualifiers.
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 64
Seeded Qualifier Contexts
n l y
e O
Seeded Qualifier Context
U s
A I
The Qualifier Attributes represent values that can be compared to values on your sales order.
Using these qualifier attributes the Pricing engine can determine which modifier list and
modifier lines should be applied to the order.
O
Line.
l &
Basic Pricing limits the seeded qualifier contexts for both the Modifier List and the Modifier
c
• Customer Class le
r
Modifier List: a
O
• Price List
Qualifiers for Modifier Lines:
Customer:
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 65
• Agreement Name
• Agreement Type
Order:
• Customer PO
• Order Type
Note: When a qualifier has a grouping number –1, it implies that the qualifier will be taken as
mandatory in comparison to other qualifiers.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 66
Agenda
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 67
Modifier Overview
n l y
e O
Modifier Overview
U s
A I
Using Modifiers is the only way you are allowed to adjust the Price List price.
Discounts, Surcharge, and Freight and Special Charges are all valid Modifier types in Basic
Pricing. O
&
• Create Order Level Modifiers to apply modifier to all order lines.
l
a
• Create Line Level Modifiers to apply modifier to only the current line.
n
te r
Qualify your Modifier List to improve the performance. If the Pricing Engine can disqualify
Lists that are not applicable to the current pricing request it will improving processing time.
I n
By putting qualifiers on your modifier List and Lines, you can create rules that will be
automatically applied by the Pricing Engine.
le
From the order or order line you can use the Action – View Adjustments to see the details of
c
Modifiers that were applied automatically by the Pricing Engine or to apply Manual discounts.
r a
Also, if the modifier is overridable you can use this window to enter new values or override the
pre-defined values.
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 68
Modifier List
n l y
e O
Modifier List
U s
Order Management Super User, Vision Operations (USA)
(N ) Pricing > Modifiers > Modifier Setup A I
O
The Modifier Type restricts the kinds of lines that can be attached. Basic Pricing supports three
types of Modifier Lists:
l &
a
• Discounts create a negative price adjustment.
n
te r
• Surcharges create a positive price adjustment.
• Freight and Special Charges (including Handling charges) create a charge amount.
I n
Elements within the Modifier List window:
• The Active check box allows the modifier list to be used by the Pricing Engine.
le
• The Start Dates indicate when the Modifier List is effective.
c
r a
• The currency on the Modifier list must match the currency on the Pricing Request.
• Use a combination of qualifiers to establish pricing rules that will be respected by the
O Pricing Engine.
• Modifiers can remain Price List independent or you can use your Price Lists as qualifiers.
Basic Pricing
Chapter 10 - Page 69
Modifiers Lines
n l y
e O
Modifier Lines
U s
Order Management Super User, Vision Operations (USA)
(N) Pricing > Modifiers > Modifier Setup (T) Modifier Summary A I
O
The Modifier number is a unique identifier within a List. It can be alphanumeric.
Levels within modifier lines:
l &
a
• If you create an Order Level modifier the adjustment will be applicable to all lines on the
n
te r
order. If it is a Freight Charge it would only be applied once to the Order Header.
• Line Level modifiers only adjust the pricing request’s line.
Types of modifier lines:
I n
• Define Discounts to markdown the Price List Price.
le
• Define Surcharges to markup the order price.
c
r a
• Create Freight and Special Handling charges to meet your business requirements.
• Price Breaks can either be Discounts or Surcharges.You can break on order quantity or
O amount.
Elements when defining modifier line:
Basic Pricing
Chapter 10 - Page 70
• The Pricing Engine uses the Start and End Dates to establish effectivity .
• The Print on Invoice functionality is controlled by a profile option: OM: Show Discount
Details on Invoice. If it is selected the discounts will print on your invoices. Otherwise,
the net amount is passed to Receivables.
• The Automatic check box is selected if you want the Pricing Engine to apply the modifier
to all qualified orders and order lines.
• To create Manual discounts leave Automatic unchecked.You can use the Action – View
Adjustments in the Sales Orders window to apply manual modifiers.
• To avoid changing the Selling Price calculated by the Pricing engine, leave the Override
check box unchecked.
• Some businesses have such a flexible selling price that they need the ability to overwrite
the calculated price with a new price. To do this, create a modifier line which has
Automatic unchecked and Override checked.
• Optionally, restrict the modifier to a specific Item number or item category by using the
Product Attribute.
If the Pricing Engine finds multiple discounts that are qualified to be applied, it always applies
the modifier which will give the lowest price to the customer based on best price or
precedence.
View your Discounts and Surcharges from the Sales Order’s Action – View Adjustments
menu. View your Freight and Special Handling charges from the Action – Charges menu.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 71
Modifier Line Examples
n l y
e O
Pricing Adjustment Examples
U s
The major pricing modifiers found in Basic Pricing are:
A I
• Discount – when the seller offers a discount on the list price of the item. The discount can
be a percent, lump sum, amount or new price. O
&
• Surcharge – the price of the item attracts an additional charge. As with discounts, the
l
n a
surcharge can be a percent, lump sum, amount or new price.
• Freight and Special Charges – These are charges applicable during the shipping of items.
te r
• Price Breaks – Price Break modifiers are applied only at the line level. In this type of
modifier, the quantity or amount is clubbed into various ranges and when the user selects
I n
a quantity or amount that falls within a particular range of values, the corresponding price
is applied.
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 72
Modifier Types
n l y
e O
Modifier Types
U s
A I
The table depicts modifier list types and the line types that can be associated to each list type:
discounts, surcharges, and freight and special charges. The check mark (3) indicates that the
O
line modifier is available for the list modifier. The cross mark (2) indicates that the line
modifier is not available for the list modifier.
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 73
Agenda
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 74
Overview of Freight and Special Charges Modifiers
n l y
e O
Overview of Freight and Special Charges Modifiers
U s
A I
Freight and Special Charges are costs associated with the shipment of goods. Using Freight and
Special Charges modifiers, you can apply different freight charges to an order or line and thus
O
increase the selling price. Additionally you can enter the Freight and Shipping costs in
l &
Shipping Execution and have the Freight and Special Charges modifiers convert them into
charges in Order Management. The freight charge may be equal to the freight cost, or it could
be the freight cost with a markup.
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 75
Seeded Freight Charges
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 76
Setting up Freight and Special Charges Modifiers
n l y
e O
Setting up Freight and Special Charges Modifiers
U s
A I
Freight and Special Charges Modifiers enable you to define how to apply charges to orders.
You can apply the modifiers automatically or manually. An example of how to set up
O
automatic order level charges using qualifiers along with the modifiers: First select the Freight
l &
and Special Charges List as the type of modifier. Then at the Modifier Summary tab, enter the
modifier lines, specifying that the modifier is to be applied at the order level. Then set up
a
header level qualifiers that will be applicable at the list level. You can define the qualifier to
n
te r
accept only orders with Freight Terms of Prepay and Add. Now when you enter an order with
Freight Terms of Prepay and Add, the charges are applied to the order automatically and you
can view them in the order window.
I n
Please note that this is only one example of a type of setup, various other ways of setting up
le
Freight and Special Charges Modifiers are possible.
c
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 77
Guided Demonstration – Freight and Special Charges Modifiers
Responsibility: Order Management Super User, Vision Operations
(USA)
(N) > Pricing > Modifiers > Modifier Setup
6. Enter the Level as Order and select the Automatic and Override boxes. Enter the Pricing
Phase as Header Level Adjustment.
7. Click (T) Discounts/Charges. Enter the Charge Name as Freight Costs with an Application
Method of Percent and a Value of 5.
n l y
8.
9.
Enter the Customer Number as 1608 in the Order Header window.
Click (T) Line Items and enter the item AS54999 with a quantity of 1.
e O
U
10. Click (T) Order Information > Main and view the Freight cost in the Charges field.s
A I
11. Click (B) Actions > Charges to verify that the modifier has been applied.
12. Save your work and close the sales orders window. O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 78
Practice - Freight and Special Charges Modifiers
Overview
In this practice you will learn how to create a Freight and Special Charges modifier and apply it
to a sales order:
Assumptions
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
• Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
n l y
Tasks
e O
1. Create a new Freight and Special Charges modifier and add qualifiers to it.
U s
2.
I
Enter a new sales order and see the modifier being applied in the Charges field.
A
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 79
Solution – Freight and Special Charges Modifiers
Login to the database
• Password: welcome
n
6.
r
Create a second line with the Charge Name = Handling Costs, Application Method =
Lumpsum and Value = 10.
te
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 80
7. Click (B) List Qualifiers in the header region on the Main tab. In the Header Level
Qualifiers window that displays, enter the following:
n l y
− Grouping Number: 1
− Qualifier Context: Customer
e O
− Qualifier Attribute: Customer Name
− Precedence: Accept Default
U s
− Operator: =
− Value From: AT&T Universal Card (1005)
A I
O
l &
n a
te r
8. Click (B) OK. I n
c le
Create a sales order and have the Freight and Special Charges Modifier applied
r a
(N) > Orders, Returns > Sales Orders
9. O
Customer Number: 1005. The related customer data defaults in the order header window.
Basic Pricing
Chapter 10 - Page 81
10. Click (T) Line Items and enter the item AS518947 with a quantity of 1.
12. The Freight and Special Charges modifier has been applied and is displayed in the Charges
field.
13. You may verify that the modifier has been applied by clicking (B) Actions > Charges and
viewing the charges in the window.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 82
Agenda
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 83
Overview of Attribute Management
n l y
e O
Overview of Attribute Management
U s
A I
An attribute is a characteristic of an item which governs its price. The attributes of an item and
its values need to be passed to the Pricing Engine so that the Pricing Engine can evaluate the
O
attribute and then based on the value of the attribute, choose the appropriate price list and
l &
modifier(s) for pricing the item. Attribute Management enables you to organize the attributes,
group them in contexts, define calling applications and source applications for the attributes.
a
An attribute gets its value from a function, a constant value, a multi-record API, system
n
te r
variable or profile. This value comes from a source application or source system and is read by
the pricing engine, which determines if this is the attribute/value that the requesting application
I n
has called for. If it is the correct attribute/value, then the pricing engine looks up the price list
and modifiers to apply and calculates the unit selling price.
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 84
Overview of Attribute Management
n l y
e O
Overview of Attribute Management
U s
Some common Attribute Management terms include:
A I
• Contexts - Contexts are groupings of attributes that are related. There are three contexts
O
available in Basic Pricing – Pricing Context, Product Context, and Qualifier Context.
&
• Attributes – The specific values or characteristics that you use to define pricing rules. For
l
n a
example, height and weight are attributes that will determine the price of the item.
Attribute values can be defined at the order level, line level, or both.
te r
• Mapping data for an attribute – There are different ways the data can be mapped:
- User Entered: The attribute value is entered by the user; this is the only sourcing
I n
feature that is supported in Basic Pricing.
Pricing:
c le
• Other mapping methods for sourcing attribute data are available only in Advanced
r a
- Custom Sourced: The user must provide code to source the attribute.
- Attribute Mapping: An attribute mapping rule must be defined in the Attribute
O Mapping window either for the order, line, or both.
Basic Pricing
Chapter 10 - Page 85
- Runtime Sourced: Sourced in the pricing engine by a custom API. This is used to
source an accumulation attribute at runtime.
• Pricing Transaction Entity (PTEs) – An entity that supports a many to many relationship
between source systems and request types. The seeded PTEs are Order Fulfillment,
Demand Planning, Intercompany Transaction, Logistics, Complex MRO, and
Procurement.
• Source System – The application that has the pricing data like price lists, modifiers, as
well as setup information. Examples of source systems are Oracle Marketing, Oracle
Order Capture, Oracle Purchasing, etc.
• Request Type – The request made by an application for pricing data. Some applications
may even share request types, for example, iStore and Order Capture.
Note: In Basic Pricing, the Pricing Transaction Entity – Source System and Request Types
window is view-only: you can view the request types and source system for a given Pricing
Transaction Entity but not make any updates.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 86
Setup Steps – Creating Contexts and Attributes
n l y
e O
Setup Steps – Creating Contexts and Attributes
U s
The following seeded context types are available in Basic Pricing:
A I
Product contexts and attributes define the product hierarchy and are related to product
O
information. For example, the product context "Item" may consist of attributes such as Item
Number, Item Category, and All Items.
l &
n a
Pricing contexts and attributes define eligibility for a price list line or modifier. Pricing
contexts and attributes can be used for a price list line, as a formula component, or in
modifiers.
te r
Qualifier contexts and attributes define what can be used to create qualifiers that determine
I n
eligibility for a modifier (who is eligible to receive the modifier).
c le
Contexts cannot be deleted if they have more than one attribute attached.
To create a new context, use the Oracle Pricing Manager responsibility:
r a
(N) Setup > Attribute Management > Context and Attributes
The Context Setup window enables you to choose the context type – Pricing, Product, or
O
Qualifier. Enter a code for the context and enable it. In the same window, you may enter the
appropriate attributes for the context in the Attributes region. Enter a code for the attribute; you
Basic Pricing
Chapter 10 - Page 87
may enter a precedence number (the lower the value, the higher the precedence over other
attributes) and map the attribute to any one of the hundred customizable attribute fields to store
the value of the derived attribute. If no application name is selected, Oracle Pricing displays.
After saving your work, you can now link the attributes to a Pricing Transaction Entity.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 88
Setup Steps – Linking Attributes to a Pricing Transaction Entity
(PTE)
n l y
e O
U s
Setup Steps – Linking Attributes to a Pricing Transaction Entity (PTE)
A I
O
A Pricing Transaction Entity is used to maintain the relationship between source systems and
request types. It ensures that those source systems linked to the Pricing Transaction Entity are
n a
Using the Oracle Pricing Manager responsibility:
te r
(N) Setup > Attribute Management > Attribute Linking and Mapping
Select the PTE and the context, and the Contexts region populates with all the attributes that
I n
are created for that PTE/Context. To link an attribute to a PTE, select the context name and
information:
c le
then click (B) Link Attributes. The Link Attributes window enables you to enter the following
r a
• Code (usually populated by default with the attribute code that you specified in the
Context and Attributes window)
O
• Level – Line, Order, or Both
• Attribute Mapping Method – only User Entered is available in Basic Pricing
Basic Pricing
Chapter 10 - Page 89
Save your work and exit the window. You can view the newly linked context in the Pricing
Transaction Entity-Attribute Linking window. The Assigned to PTE box indicates that the
context and its attributes have been assigned to this PTE.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 90
Agenda
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 91
Profile Options in Basic Pricing
n l y
e O
Profile Options in Basic Pricing
U s
A I
The system administrator sets up the pricing profile options so that the access and control of
data can be determined by Basic Pricing. The level at which the profile options can be set are
O
user, responsibility, application and site. The permissions for setting the profile options are
l &
View, View and Update, No Access. The Required column determines if the profile option
requires a value or not. If it is Required, then you must provide a value. If it is Optional, you
a
may leave it blank. The Default Value column allows you to provide a default value for the
n
Profile Option r
profile. Following are some common profile options used in Basic Pricing:
c le
QP: Blind Discount Option Required Yes
QP: Debug
r a
QP: Inventory Decimal Precision
Optional
Required
Request Viewer Off
10
O
QP: Item Validation Organization
QP: Negative Pricing
Required
Required
No Default
No Default
Basic Pricing
Chapter 10 - Page 92
QP: Price Rounding Required Blank
QP: Qualify Secondary Price Lists Optional No
QP: Return Manual Discounts Optional Yes
QP: Satisfied Qualifiers Option Optional Yes
QP: Security Control Optional Off
QP: Security Default Maintain Privilege Required Blank
QP: Security Default ViewOnly Privilege Required Blank
QP: Selling Price Rounding Options Optional Individual : =
round(list price) + round(adj)
QP: Set Request Name Required Blank
QP: Unit Price Precision Type Required Standard
QP: Valueset Lookup Filter Optional Yes
QP: Verify GSA Violations Required No
Please refer to the Oracle Order Management Implementation Manual for further details.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 93
Summary
n l y
e O
U s
A I
O
l &
n a
te r
I n
c le
r a
O
Copyright © Oracle, 2005. All rights reserved.
Basic Pricing
Chapter 10 - Page 94
Oracle Shipping Execution
Overview
Chapter 11
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Overview of Shipping in the Order to Cash Process
U s
A I
You run Pick Release for orders booked from Oracle Order Management. After the Pick
Release process is executed, the orders are moved from inventory and dropped in the staging
O
area before being shipped. When the orders are shipped, Oracle Shipping Execution
l &
decrements Oracle Inventory and updates the sales order line. After the sales order line is
updated, the lines proceed through Auto Invoice to Oracle Accounts Receivable.
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Overview of Shipping Execution Integration
U s
A I
Pick Release is executed on booked sales order lines from Oracle Order Management. After
processing Ship Confirm, Oracle Shipping Execution decrements Oracle Inventory and updates
O
the sales order line. In addition, Oracle Inventory triggers the creation of the Cost of Goods
l &
Sold account (COGS). The order line is processed through AutoInvoice to Oracle Accounts
Receivables. The general ledger is updated from Oracle Inventory and Oracle Accounts
Receivables.
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Overview of Shipping Concepts
U s
A I
• A trip is carrier specific and includes at least two stops – a pick-up and a drop-off.
• A stop is a point along the route of the trip and can consist of a pick-up, drop-off, or both.
O
• A delivery is a consolidation of sales order lines based on at least the customer, ship from
location, and ultimate ship to location.
l &
or trip.
n a
• A delivery leg is represented by a bill of lading and consists of at least two stops and one leg
Example:
te r
Stop1: San Francisco
Stop2: Chicago
I n
Stop3: New York
c l e
Trip 1: San Francisco to Chicago, Chicago to New York.
r a
Delivery 1: San Francisco to Chicago
O
Delivery Leg 1
• Stop 1: San Francisco (pick-up)
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Overview of Pick Release
U s
specifying three important rules A I
The Pick Release process can be customized based on your business requirements by
O
Release Rules: Defining Release Rules enables you to specify the criteria by which the Sales
Orders are selected for Pick Release.
l &
n a
Release Sequence Rules: Defining the Release Sequence Rules enables you to specify the
order in which the available inventory will be allocated to the Sales Order line that has been
pick released.
te r
Pick Slip Grouping Rules : Defining Pick Slip Grouping Rules enables you to specify the
I n
criteria by which the Pick Slip will be grouped. For example, by ship to address, delivery date,
or purchase order number.
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Overview of Pick Confirm and Staging Subinventory
U s
A I
A staging subinventory is a logical or physical location where orders are placed before loading.
Pick Confirm is a process that is run to systematically transfer material from a source inventory
O
location to a shipping staging subinventory. Pick Confirm automatically transfers the high-
staging location.
l &
level reservation to an allocated reservation (including lots, subinventory, and locators) in the
a
Note: Pick confirm can be completed manually or automatically.
n
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Overview of Ship Confirmation
U s
A I
You run the Ship Confirm process to indicate that the items are loaded onto the carrier from the
staging location. When you run the Ship Confirm process, the system decrements Oracle
O
inventory and updates the sales order line status. This information can then be transferred
l &
through AutoInvoice to Oracle Accounts Receivables for invoicing. Finally, accounting
information can be sent to the general ledger from Oracle Inventory and Oracle Accounts
Receivables.
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Overview of Deliveries and Delivery Lines
U s
Delivery Lines
A I
Sales order lines that have been released for shipping are called delivery lines and can be
used to create a delivery. O
Deliveries
l &
n a
A delivery consists of set delivery lines that are scheduled to be shipped to a customer’s ship-
to location on a specific date and time. In a delivery, you can include items from different
te r
sales orders as well as back orders. You can either manually or automatically group delivery
lines to create a delivery. If a delivery is autocreated, the delivery lines are grouped together
I n
by the mandatory default criteria, ship-from location and ship-to Location. However,
additional grouping criteria can be included.
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Overview of Packing LPNs/Containers
U s
A I
Containers, also called as License Plate Numbers(LPNs), are packed with delivery lines that
are delivered to the customer. You can create and manage LPNs at any point in the shipping
process.
O
Auto-Pack
l &
n a
Auto-packing provides a convenient and quick way of automatically packing delivery lines
into Containers(LPNs). The delivery lines are packed into LPNs based on the container-item
Packing Workbench
te r
relationship set up in Oracle Shipping Execution or in Oracle Inventory.
I n
You can use Packing Workbench to assign and pack delivery lines into one or more LPNs.
Manually Packing
c l e
You can manually pack delivery lines into an LPN or multiple LPNs.
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Overview of Trips
U s
A I
A trip is an instance of a specific shipment originating from and moving to a particular
location. A trip is carrier specific and must contain at least two stops – a pick-up and a drop-
O
off. A trip can also have intermediate stops, which can be either a pick-up stop or a drop-off
stop.
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Overview of Query Manager
U s
A I
The Query Manager window is used to define and save queries to search for and manage the
shipping entities such as trips, stops, deliveries, delivery lines, containers/ License Plate
O
Numbers (LPNs). You can create customized queries by entering your search criteria and save
l &
them. You can save them as Personal Query, Public Query.
Personal Query: Queries you save for your personal use. This query is not available to other
users.
n a
centrally manage the queries.
te r
Public Query: Queries you save and share with other users. This very useful if you want to
I n
Temporary Query: Queries which are not used frequently such as those that you use only
once`
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Overview of Shipping Transactions Form
U s
A I
The Shipping Transaction form enables you to consolidate planning, executing and viewing all
aspects of the Shipping Process. The user interface consists of the Query Manager and Data
Manager.
O
&
Query Manager: Performs search on trips, stops, deliveries, delivery lines, containers/LPNs
l
Data Manager:
n a
• Enables updating of, and creation of trips, stops, deliveries, delivery lines,
containers/LPNS
te r
• Performs Shipping Functions such as planning, pick releasing, and ship confirming
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Overview of Quick Ship
U s
Quick Ship enables you to enter minimum requirements and process a shipment.
The Quick Ship window provides the following features: A I
O
• Visibility to trips, deliveries, and delivery lines in the same window
l &
• Ship confirm multiple deliveries at the same time
a
• Change ship quantities and also specify the inventory controls for each delivery
n
te r
• View and resolve the shipping exceptions for the delivery, trip and delivery lines
• Customization of the display of fields, initial view (delivery or trip), and folder options
n
for each entity based on your business needs
I
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Overview of Shipping Exceptions
U s
A I
A shipping exception is raised to indicate that the shipping entity is not taking the normal
course of action. In this situation, Oracle Shipping Execution may proceed further without
O
handling the exception. The shipping entities that raise a shipping exception are deliveries,
trips, and containers/LPNs.
l &
Shipping exceptions enable you to identify and handle nonconforming operations that violate
a
the requirements of your business or that of your carriers and customers. Also, you can create
n
te r
your own shipping exceptions to meet your specific business requirements.
Seeded Exceptions: Seeded exceptions are the default exceptions that ship with Oracle
Shipping Execution.
I n
Manual Exceptions: You can create manual exceptions to meet your business requirements.
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Shipping Execution Flow
U s
A I
After a sales order has been booked, the sales order lines must complete all workflow activities
leading up to the shipping activity. Two typical preceding workflow activities are Schedule –
Line and Create Supply.
O
Schedule – Line:
l &
n
also sets the Shipment Schedule Date. a
Scheduling the line makes the order line’s demand visible to Oracle Inventory for planning. It
Create Supply:
te r
Variety of subflow paths can be taken within Create Supply Line based on the type of item
I n
shipped. They are as follows:
c l e
• Configurable Items: Configurable items must complete the Create Supply activity
which takes an order line through a build cycle. The final assemblies that are completed
r a
out of Oracle Work in Process are received into Oracle Inventory as Reserved for a
specific customer’s order.
O
• Drop ship: Drop ship order lines must complete the Create Supply activity too. After a
Purchase Requisition has been passed to Oracle Purchasing the order line advances to the
Shipping Activity.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Shipping Concepts
U s
Trip
A I
• A trip is carrier specific and represent a unique instance of that carrier leaving your
warehouse with deliveries. O
&
• The carrier could be a public carrier such as DHL or could be a company’s own fleet of
l
trucks.
n a
• A trip could represent a truck, air cargo, ship cargo, or railcar. These entities would be set
te r
up as items in Oracle Inventory with an item type of Vehicle.
• Each trip has a minimum of two stops, pick-up and drop-off.
I n
• A trip can be created automatically or manually from the Shipping Transactions form or
c l e
can be automatically created from the Ship Confirm window. You can also create a trip
as a part of a concurrent process.
r a
• Companies that use public carriers can enable the system to automatically create Trips as
part of of the Ship Confirm process. This eliminates unnecessary transactions.
O
Stops
• A stop is a point along the route of a trip that is due for pick-up or drop-off.
A I
• Delivery lines are visible from the Shipping Transactions form. They are also visible
O
from the sales order line’s Additional Information – Deliveries tab.
LPNs
n a
te r
• LPN, (License Plate Number) are also known as Containers. An LPN can be loaded
inside of another container, for example, pack an item into a box and then pack that box
onto a pallet.
I n
• Optionally LPNs can be setup as inventory items if the shipper is interested in using
l e
weight and Volume and packing functionality.
c
r
Ship From a
• LPNs can be made mandatory using your Shipping Parameters.
O
• The ship-from location represents the warehouse that is performing the shipping
transaction. A warehouse is an Inventory organization.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Pick Release Concepts
U s
Release Rules
A I
• Release rules define the criteria to be used during Pick Release. Only orders that meet the
O
criteria and are eligible will be released. An order line is eligible if it has completed the
&
prerequisite workflow activities, such as Schedule - Line or Create Supply.
l
Release Sequence Rules
n a
• Release Sequence rules determines the order in which inventory is allocated to sales
te r
orders. You choose to allocate by order, outstanding Invoice value, Scheduled Date,
Departure Date and Shipment Priority.
I n
• The order in which sales orders are filled could be very important. If a company has a
l e
problem of running out of material before all of their orders have been filled it is very
important that they have filled their most important orders first.
c
r a
Picking Rules
• Picking rules, which are created and maintained in Oracle Inventory, suggest which
O material to use, based on inventory controls such as revision control, lot control, FIFO
(first in first out) or subinventory/locator picking numbers.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Pick Release Process
U s
What Happens during Pick Release:
A I
• A pre-approved move order is automatically created in Oracle Inventory.
O
• A move order is a request for a subinventory transfer from the source (stocking)
&
subinventory to the destination (staging) subinventory.
l
n a
• A move order is created for every sales order line that has the status of Awaiting
Shipping and passes the picking criteria (Use your Release Rules to guide this process).
te r
• The destination subinventory is the staging subinventory entered on the Release Sales
Orders form or defaulted from the Shipping Parameters. Only one staging subinventory is
I n
allowed per picking batch.
c l e
• Note: A picking batch is the total number of order lines that were released at one time.
• Oracle Inventory uses the move order to manage material requisitions within an
r a
organization.
Allocate Inventory to the move order
O
Copyright © Oracle, 2005. All rights reserved.
number.
l &
Detail reservations puts a reservation on specific subinventory, locator, revision, and lot
n a
• If you transact less than the requested quantity, the move order will stay open until the
te r
total quantity is transacted, or the order is closed or cancelled.
• The status of the sales order line, which is linked to the move order, is changed to Picked
I n
making it eligible for ship confirm.
l e
• If not all of the move order quantity was transacted the status of the sales order line, is
changed to Picked Partial. During Ship Confirm the order line will split into 2 shipment
c
r a
schedules (e.g. 1.1 and 1.2). The status of the unfilled line will be changed to Awaiting
Shipping.
O
• If there is a shortage of material a shortage messages alerts the appropriate individual.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Ship Confirm Process Flow
U s
What happens during Ship Confirm:
The results of the picking process are recorded against a delivery. A I
O
• Ship Confirm can only be performed on deliveries or trips with delivery lines that have
been Pick Confirmed.
l &
n a
• Ship Confirming a delivery or a trip records the results of the shipping process. These
results could be shipped, backordered, staged or cycle count or a combination of all 4.
te r
• The workflow activity will be completed when the quantity picked is recorded as
Shipped.
I n
• If the ordered item is set up with the item attribute Shippable checked then Ship
c l e
Confirming is a prerequisite for invoicing.
• The sales order Action, Additional Line Information provides a complete history of the
r a
line’s shipping process from Ready to Release through Interfaced.
Over/Under Tolerances
O
Copyright © Oracle, 2005. All rights reserved.
U s
• The cost of goods sold account number that is passed to Oracle Inventory is workflow
generated. In Oracle Inventory it creates a Material Distribution record that is ultimately
passed to the general ledger.
A I
• If Ship Confirm is partial the remaining quantity can be either staged or backordered.
Backordered Quantities
O
returned to their source location.
l &
• Backordered quantities are left in the staging subinventory. They are not automatically
a
• A new Pick Release will be required before they can be Ship Confirmed.
n
te r
• The backordered quantity is removed from the delivery being Ship Confirmed.and the
reservation is removed making the quantity available to ATP.
I n
• The sales order line splits into shipment schedules. One schedule will have the quantity
that was shipped and a status of Shipped. The other schedule will have the quantity that
l e
was backordered and a status of Awaiting Shipment. Example of resulting split.
c
Line Item a
Original Sales Order line:
O
1.1 BB-2002
1.1 BB-2202
10
8
Picked After Ship Confirm (8 shipped 2 backordered)
8 Shipped
n y
inventory to be reserved by another delivery line. By using the cycle count functionality
l
you have the option to transfer the reservation on a Pick Released item to cycle count and
simultaneously backorder the delivery line quantities which helps keep available
inventory accurate.
e O
• This would be used if unexpected situations occur while staging orders such as, an item is
damaged or physical inventory is out of balance with the system inventory. By
U s
transferring the reservation to cycle count, future reservations cannot be placed against
that quantity.
A I
• If you select Cycle Count all the entire reserved quantity for a delivery is transferred to
O
Cycle Count and the delivery line status is changed to backordered.
l &
• If only specific quantities should be transferred to cycle count you must first enter a
shipped quantity on the delivery line’s detail form. Then from the Ship Confirm form
a
select Ship Entered Quantities and in the Unspecified Quantities LOV select Cycle
n
te r
Count. The result is that only the shipped quantities are confirmed and the balance of the
delivery lines will be backordered and the reservations for that quantity will transfer to
I n
Cycle Count. Example of resulting split.
• Original Sales Order line:
Line Item
c l e Ordered Shipped Status
r a
1.1 BB-2002 10 Picked
After Ship Confirm (8 shipped 2 backordered)
O 1.1 BB-2202
1.2 BB-2202
8
2
8 Shipped
Awaiting Shipment
n l y
e O
Automated Ship Confirm
U s
A I
You can automatically Ship Confirm all deliveries that have all lines at status of staged.
Automated Ship Confirm can be executed as a concurrent program (set to run at specific
intervals) or it can be launched manually.
O
l &
You can enable the Automated Ship Confirm for any delivery by utilizing the Enable Ship
Confirm flag at the Delivery tab. If the check box is selected, the delivery will be considered
for Automated Ship Confirm.
n a
Running Automated Ship Confirm:
te r
• Define a Ship Confirm Rule: You must define a ship confirm rule in the Ship Confirm
Rule window.
I n
l e
• Auto Ship Confirm from the Shipping Transaction form: From within the Shipping
Transaction form, you can select deliveries or delivery lines that you want Auto Ship
c
r a
Confirm to run against.
• Auto Ship Confirm from the Quick Ship window: From within the Quick Ship
O window, you can select deliveries that you want to Ship Confirm.
• Auto Ship Confirm using Ship Confirm Deliveries SRS: You can use the Ship
Confirm Deliveries SRS window to systematically ship confirm your deliveries.
n l y
e O
One Step Shipping
U s
A I
One step shipping is the process of picking, optionally packing, and ship confirming delivery
lines in one step. Utilizing the Actions named Pick and Ship, and Pick, Pack, and Ship, within
O
the Shipping Transaction form, Deliveries tab, and Delivery Lines tab enables this
l &
functionality. The two actions can be utilized depending on your business needs.
• Pick and Ship: This action can be used for one or more deliveries or delivery lines. Pick
and Ship will perform the following:
n a
te r
- Autocreate deliveries if deliveries are not associated with all or some of the lines.
- Launch Pick Release and Pick Confirm all lines assigned to the deliveries
I n
(autocreated as well as manually created.)
l e
- Ship Confirm all deliveries if all assigned lines have a line status of Staged/Pick
Confirmed and do not require any additional actions such as serial numbers or other
c
r ainventory controls.
- Autocreate trips if manually created trips/stops are not associated with any or all of
O the deliveries
- Close auto created or manually created trips
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Shipping Transactions Form
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Transactions A I
O
The Shipping Transactions form is a workbench that consolidates planning, executing and
&
viewing all aspects of the shipping process. The user interface is composed of two elements;
l
n a
the Query Manager and the Data Manager. It allows for extensive use of Oracle Folders and
tree capabilities. You can change prompts, move fields, hide/retrieve fields based on your
needs.
Query Manager
te r
I n
• You can finds trips, stops, deliveries, delivery lines and containers.
Data Manager
c l e
• You define and Save queries using the Query Manager for fast retrieval of data.
r a
• Create or change data using the Data Manager.
O
• Plan trips, stops, deliveries, delivery lines, and containers.
• Perform Pick Release and Ship Confirm from the same form.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
3. (T) Lines
− Line Status: Not Shipped
5. (B) Find. All lines which are not shipped are displayed in the Shipping Transaction Form
n l y
e O
Quick Ship User Interface
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Quick Ship A I
O
You use the Quick Ship window to process shipments quickly, using the minimum shipping
&
requirements with the benefit of configurability. You can access deliveries, trips, and delivery
l
shipment data.
n a
lines/LPNs within the Quick Ship window. Quick Ship offers the benefit of quickly entering
te r
The Quick Ship window is configurable. Using the Folders feature, you can hide fields, show
fields, and show an Additional tab on the window. You can set the default view of the Quick
I n
Ship window by defining the WSH: Quick Ship Default View profile option.
c l e
You can perform the following tasks using the Quick Ship window:
• Ship Confirm deliveries
r a
• Adjust shipment quantities
• Print Shipping documents
O
• Enter delivery freight costs
• View and resolve shipping exceptions
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
2. (M) Tools > Change View to toggle between the two Quick Ship views. The two Quick Ship
views are as follows:
− Delivery Confirm View
− Trip Confirm View
Finding Deliveries
3. Ensure that you are in the Delivery Confirm View.
4. You can find the deliveries in the Quick Ship window using any one the following methods:
− Enter the delivery in the Name field and click Tab
− Click on Name LOV to find for a delivery.
n
− Click on the Find icon to find the delivery using Find Deliveries window. In the l y
enter.
e O
Find Deliveries window, you can find the delivery based on the search criteria you
l
6.
a
To show a field, you can use anyone of the following methods:
n
− (M) Folder > Show Field. Select a field, which you want to display from the LOV.
te r
− Right click on any field, select Folders option on the popmenu and click Show field.
n
Select a field, which you want to display from the LOV.
I
c l
following methods. e
7. To change the position of a field in the Quick Ship window, you can use anyone of the
•
r a
Click on the field to be moved. Click (M) Folder and click on Move Right, Move Left,
10. Select the Show Additional Delivery to display the Additional tab.
11. Select the Show Trip Information to display the Trip tab
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Shipping Roles and User Security
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Grants and Roles Definitions A I
O
Oracle Shipping Execution provides data access controls called roles that control users’ access
&
to the Actions list and Tools menu in the Shipping Transactions form and the Quick Ship
l
shipping data or actions.
n a
window. Roles are assigned to users using grants that control access to view or edit specific
te r
This is useful, for example, if you want to assign a grant to inexperienced users that provides
view-only access or assign grants that prevent unwanted actions such as unintentional pick
I n
releases across multiple organizations.
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Shipping Exceptions
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Define Exceptions A I
You can use Oracle Shipping Execution to do the following: O
l
• View and update logged shipping exceptions
&
• Log a new shipping exception manually
n a
te r
• Purge logged shipping exception
View and update logged shipping exception
I n
• You can use the Find Exception window to find selected exceptions or all exceptions.
The search displays the results in a series of tabs in the View Exceptions window.
l e
• In the View Exceptions window, you can track, review, and update current and past
c
exceptions that have been logged either manually or automatically. The following tabs
r a
are available in this window
O
• Exception tab: Displays general information about the exception such as the exception
name and exception ID.
- Trip tab: Displays all trip information specific to the exception.
l
• Select an existing exception name as a template to which you can add specific shipping
entity details.
n y
e O
• Log a new exception without selecting an exception name. This is useful if you want to
create a new exception not based on the default values of an existing exception name.
Purging Logged Shipped Exceptions
U s
To help maintain your shipping exception records and conserve computer storage space, you
A I
may want to purge (delete) logged shipping exception records that are no longer required. For
example, you may want to purge shipping exception records that are five months and older.
O
You also may want to mass change the status of (resolve) shipping exceptions. You must use
l &
the Resolve/Purge Exceptions Parameters window to resolve and purge shipping exceptions.
You cannot select, resolve, and purge shipping exception records from the View Exceptions
window.
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Release Sales Orders
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Release Sales Order > Release Sales Order A I
O
Releasing Sales Orders for picking is the first step in the shipping process.
l &
• The shipping activity must be in the line’s workflow. The sales order line status must be
a
Awaiting Shipment and the item’s attribute Shippable must be selected.
n
te r
• Some companies have a problem with material shortages or incorrect balances. To
combat these issues it may be necessary for a scheduler to manually reserve inventory for
specific sales order lines, before to picking. In order to assure that the picking process
I n
selects only the orders planned by your schedulers, select Prior Reservations Only from
c l e
the Release Sales Order form.
• The document set defines what reports will be printed from your picking process. For
r a
example you may request that pick slips and an Exception Report be printed.
• Move orders are created for every sales order line that is released.
O
Holds
• All user defined holds must be removed from the order or order line before picking.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Book Order
1. (N) Order, Returns > Sales Orders
6. (B) Book Order, and note your sales order number. _______________
U s
9. (T) Inventory.
− Warehouse: M1
A I
O
Note: The Pick Slip Grouping rule gets defaulted based on the value set to Pick Slip
Grouping Rule field in the Shipping Parameters window for M1 organization.
− Auto Allocate: Yes
l &
10. (T) Shipping.
n a
− Autocreate Delivery: Yes
− Auto Pick Confirm:
te r
Yes
n
− Release Sequence Rule: Defaulted
I
l e
11. (B) Concurrent. To submit your picking criteria.
c
r a
12. Note your Batch number, which you can use to identify your concurrent requests.
O
View Concurrent Request
13. (M) View > Request
15. Your Batch number will be displayed in the concurrent request parameters field.
19. (T) Lines. Scroll right to check the Status field of the line and confirm the status is “Picked”.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Assumptions
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
• Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
n l y
Tasks
e O
1.
U s
Create and Book a Sales Order with 3 order lines that will be used in the Picking and
A I
Shipping practices. Use Business World (1608) as the customer. Use Items AS54888,
AS72111 and AS18947. Select a quantity of 10 for the first two items. For item AS18947
O
split the line so that a quantity of 2 has today’s date shipping to New York and that a
quantity of 2 has a date two weeks from today shipping to San Jose. Then Book your sales
order and note the Sales Order number.
l &
2.
n a
Pick Release your Sales Order by using the Sales Order number. Select M1 as the
3.
I n
View your concurrent request to validate that the Pick Release was successful.
4.
c l e
Query your Sales Order number and view the line and delivery information.
r a
O
Copyright © Oracle, 2005. All rights reserved.
• Password: welcome
Choose Responsibility
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
8. (B) Split.
n l y
e O
U s
14. (T) Inventory A I
O
15. Enter the following information:
− Warehouse: M1
l &
− Auto Allocate: Yes
n a
•
te r
Note: The Shipping parameters for Seattle will default values on to the Release Criteria
form.
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
20. (M) View > Requests > (B) Find (all requests).
21. Look for your Batch # in the Parameters for the two concurrent requests, Pick Selection List
Generation and Pick Slip Report.
n l y
e O
U s
23. (M) File > Close Form .
A I
Find Sales Order
O
l &
24. (N) Orders, Returns > Order Organizer > (B) Find
n a
25. Find your Sales Order-by-Order Number or Customer PO XX-020.
30. If you do not see the above delivery information (“Staged/Pick Confirmed”) let your
n l y
If it is not booked “Book” your order then release it).
e O
instructor know. (Check to make sure your Order is booked before alerting your instructor.
O
33. (M) File > Close Form .
n l y
e O
Methods to Pick Release
U s
Online
A I
• When the Release Sales Orders is submitted from the user interface, as Online, it releases
O
one order immediately, eliminating waiting for the order to process through the
concurrent manager queue.
l &
n a
• Only one sales order at a time is allowed.
• A Release Rule and document set is required.
Concurrent
te r
I n
• When the process is submitted through the user interface, as Concurrent, it runs Pick
Release in the background, allowing you to run other processes simultaneously.
l e
Standard Report Submission (SRS)
c
• When a Standard Report Submission (SRS) runs Release Sales Orders it runs in the
r a
background on an automatic, scheduled basis. Using SRS and your Release Rules, you
can run a specific release at the same time every day, or several times every day.
O
Note: The Shipping Transaction’s Tools menu provides a link to the Release Sales Order form
to allow picking either Online or Concurrent.
n l y
e O
Pick Release Parameters
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Shipping Parameters (T) Pick Release A I
O
The Pick Release tab on the Shipping Parameters form sets most of the parameters that relate
to the picking process.
l &
have their own values defined.
n a
Since shipping parameters are organization specific, each of your shipping organizations can
te r
Release Sequence Rule: Select a value from the LOV to default in the Release Sales Orders
form. This value can be over written before submitting the release, if applicable.
I n
Pick Slip Grouping Rule: Select a value from the LOV to default in the Release Sales Order
c l e
form. It can be over written if necessary.
Print Pick Slip: The LOV has two values, At the End or Immediate.
r a
• If At the End is selected, the system will wait until the Pick Release job is finished before
sending them to a printer.
O
• If Immediate is selected, the system will send a pick slip immediately to the printer after
it finds the specified number of pick slip lines.
or across orders.
U s
• Whether grouping delivery lines into deliveries will be restricted to within a sales order
A I
• Whether to automatically create deliveries as part of the picking process.
O
• Whether to automatically allocate inventory as soon as the move order is created.
• Whether the Picking process should respect Ship sets and Ship Model complete sets.
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Configuring Pick Release Process
U s
One-Step Process
Auto Allocate is set to Yes and Auto Pick Confirm is set to Yes. A I
O
• When the request is submitted the system automatically creates a move order for all
&
eligible order lines that meet the picking criteria.
l
a
• The Release Sequence Rule can be used to sequence the orders for inventory allocation.
n
material.
te r
• Oracle Inventory’s Picking Rule can be used to detail the move order with suggested
I n
• Pick Slips are printed and can be reprinted if needed later.
• The subinventory transfer is executing moving the material from it’s source location to
l e
the destination staging subinventory.
c
• The delivery line status is changed to Staged/Pick Confirmed, making it eligible to be
r a
Ship Confirmed.
O
One Step Shipping Scenario:
The one step process would be for an organization who's shipment profile is one where the
order lines do not require a lot of change. Typically the majority of what is picked is shipped in
l &
Note: You can autocreate deliveries during Pick Release by setting the Autocreate Delivery
a
option to Yes within the Shipping tab of the Release Sales Orders for Picking window or by
n
r
specifying a Release Rule that has the Autocreate Delivery option set to Yes.
te
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Auto Create Delivery
U s
Deliveries are required to perform Ship Confirm.
A I
Deliveries can be automatically created from the Release Sales Order form during Pick Release
O
or from the Shipping Transaction’s Action menu any time before Ship Confirm.
&
If Autocreate is not executed, deliveries can be manually created from the Shipping
l
Transactions form.
Deliveries Lines
n a
te r
Delivery Lines are sales order lines which have completed all workflow activities that are
prerequisites to shipping such as Schedule – Line or Create Supply.
Delivery Tab
I n
l e
Lines are grouped based on the grouping attributes specified on the your organization’s
c
Shipping Parameters – Delivery Tab. There are two mandatory attributes, Ship From Location
r a
and Ship To Location. Optionally, group by Customer, Freight Terms, FOB code, Intermediate
Ship To Location, and Ship Method.
O
Process Deliveries SRS
Order Management Super User, Vision Operations (USA)
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Ship Confirm
U s
A I
Ship Confirm is the last step in the shipping process. Order lines that have been Ship
Confirmed and have a status of Shipped will be allowed to continue through the workflow to
O
the Invoicing activity. Ship Confirm can be done through the following:
l &
• Auto Ship Confirm: Auto Ship Confirm enables you to automatically Ship Confirm all
deliveries that have all delivery lines at status of staged. Auto Ship Confirm can be
a
executed as a concurrent program (set to run at specific intervals) or it can be launched
n
te r
manually. Each method of executing Auto Ship Confirm has its advantages. You can
utilize either or both processes depending on your business needs. This is the least
I n
common way to Ship Confirm.
- Concurrent Submission: If Auto Ship Confirm is executed as a concurrent job,
l e
you will not have to manually Ship Confirm each delivery. If configured to do so,
c
this method can also create a trip if one isn’t already associated with the delivery. It
r ais designed to support delivery selection based on range of parameters. Because the
concurrent request is typically run at frequent intervals, there is little opportunity for
O backordering lines prior to Ship Confirm.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
2. (I) Find.
4. (B) Find.
e O
8. (B) Done.
U s
9. Enter the following in the Delivery Lines/LPNs region.
− Shipped Qty: 5
A I
10. (B) Ship Confirm. O
11. Validate
l &
a
− “Ship Entered Quantities” is the Ship Option.
n
te r
− “Create Delivery for Staged Quantities” is checked.
− “Set Delivery In-Transit” is checked.
I n
− “Close Trip” is checked.
− “Defer Interface” is unchecked.
15. Validate
− “Ship Entered Quantities” is the Ship Option.
− “Create Delivery for Staged Quantities” is checked.
− “Set Delivery In-Transit” is checked.
− “Close Trip” is checked.
− “Defer Interface” is unchecked.
18. (M) View > Requests > (B) Find (all requests)
21. (N) Orders, Returns > Order Organizer > (T) Order Information
− Enter your Sales Order number
n l y
22. (B) Find.
O
entered only 5 quantities to be shipped, the remaining 5 items are backordered.
Assumptions
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
• Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
Tasks
1. Ship Confirm Deliveries created in the Release Sales Order practice. Ship confirm 5 units and
backorder 5 units of the item AS54888, AS72111. Ship confirm 2 units of AS18947. Apply
serial numbers when required. Use the Freight Costs button to assign freight costs. Use the
Ship Confirm button to ship confirm.
n l y
2. Go to your Sales Order window and query your sales order to review the Delivery
information and Line status to see the results of your shipping process.
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
• Password: welcome
Choose Responsibility
4. (I) Find
n l y
5. Enter the following information:
− Source System: Order Management
e O
− Order Number:
s
The Sales Order # noted in the Release Sales Order Practice
U
6. (B) Find
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
13. (B) Done
I n
14. (M) File > Save
c l e
a
15. (B) Ship Confirm
r
O
16. Validate
− “Ship Entered Quantities” is the Ship Option.
− “Create Delivery for Staged Quantities” is checked.
n l y
e O
U s
17. (B) OK
A I
• O
Write your Interface Trip Stop Request ______________________.
l &
18. (B) OK
n a
r
19. (M) View > Requests > (B) Find (all requests)
te
n
20. Validate that your concurrent request completed normally.
I
l
21. (M) File > Save
c e
a
Look at Sales Order Delivery Information
r
O
22. (N) Orders, Returns > Order Organizer > (T) Order Information
− Enter your Sales Order number
− And/or Customer PO XX-020
25. (B) Actions > Additional Order Information > (T) Deliveries
n l y
e O
U s
I
28. Notice that a new Delivery is automatically created for the Shipped quantity.
A
29. (M) File > Close Form
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Shipping Transaction Parameters
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Shipping Parameters (T) Shipping Transaction A I
O
Shipping parameters are organization specific. During the Ship Confirm process the shipping
&
parameters are used to control the confirmation process.
l
Confirm process.
n a
Default Ship Confirm document set: These documents are printed as part of the Ship
te r
Default Ship Confirm rule: The default ship confirm rule that will be applied when you ship
confirm. The rule you select here will be defaulted when you auto ship confirm.
I n
Auto-pack option: You can set the Auto-pack option to No, Yes, or Autopack Master
l e
• No: Autopack will not be enabled
c
• Yes: Auto-pack will be enabled and delivery line items will be systematically packed into
r a
LPNs based on container item relationships
O
• Autopack Master: Auto-pack will be enabled and delivery line items will be
systematically packed into LPNs based on container-item relationships and the container
will then be packed into another container, such as a freight container for transport
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Shipping Documents
U s
Select the Document Set you want to attach with the reports. A I
Specify if the document set you are creating is for the Pick Release or Ship Confirm process.
O
Use the sequence field to define the printing order for the reports attached to the document set.
l &
There are three seeded document sets that you can use immediately.
• Pick Release Documents
n a
• All Shipping Documents
• Pack Slip Only
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
e
5. (M) File > Save.
U s
To Edit Document Sets
6. (I) Find. A I
O
7.
&
Select a document set from the Find Document Set window.
l
8.
a
Edit Effective Dates, Printing Method, add new documents, or delete existing ones.
n
9. (M) File > Save.
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Ship Confirm Rules
U s
business needs. A I
You use the Ship Confirm Rules window to define the Ship Confirm Rules based on your
You can specify the following for the Ship Confirm Rule: O
&
• The effective period with in which the rule is applicable
l
a
• Within the Ship Options region, you select one of the following:
n
- Ship All
te r
- Ship Entered Quantities
- Backorder All
I
- Cycle Count Alln
l e
• The Ship Options region also enables you to determine the action to perform with
c
Unspecified Quantities. Select one of the following options:
r a
- Ship
O - Backorder
- Stage
program.
A I
• Release Sales Orders SRS: You can use the Release Sales Orders SRS concurrent to
pick release the delivery at specific time.
O
l &
• Shipping Transactions Form: You can select a Ship Confirm Rule in the Confirm
Delivery window. The Ship Confirm Rule can also be defaulted here based on the
Shipping Parameter by the same name.
n a
te r
• Auto Ship Confirm Report: The Auto Ship Confirm Report is designed to provide
visibility to batches that have been successfully Ship Confirmed by Auto Ship Confirm
Note: I n
concurrent program.
l e
1. If your application is setup to allow Auto Ship Confirming of staged delivery lines, you can
c
optionally prevent deliveries (and their assigned lines) from being ship confirmed when this
r a
process is kicked off. You do this by finding the delivery that you want to prevent from being
O
considered for ship confirm and deselect (uncheck) the check box named Enable Auto Ship
Confirm.
2. The Ship Confirm Rule can be set in the Release windows only if the following is set
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Ship Confirm Deliveries SRS
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Auto Ship confirm Deliveries SRS A I
O
You use the Ship Confirm Deliveries SRS window to run Ship Confirm concurrently. For
&
example, you can run Ship Confirm on a set of deliveries at the same time every day based on
l
n a
the options you set in the Ship Confirm Deliveries SRS window.
You select a Ship Confirm Rule in the Ship Confirm Deliveries SRS window based on how the
your SRS
te r
Ship Confirm is to be run concurrently. You also define the batch prefix to uniquely identify
I n
You specify the following details in the Ship Confirm Deliveries SRS window for auto
packing:
c l e
• Organization from which the shipment is originating
r a
• Pick Release Batch name that contains the deliveries to be Ship Confirmed
• Auto Pack Batch name that contains the deliveries to be Ship Confirmed
O
• Range of delivery name to be Ship Confirmed
• Range of bill of lading to be Ship Confirmed
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Working with Deliveries and Delivery Lines
U s
You can perform the following actions with Delivery and Delivery Lines:
Splitting Delivery Lines A I
O
You can use the Split Delivery Line window to split shipments for certain customer
&
requirements. For example, an original shipment may need to be split if your customer wants a
l
n a
part of the ordered quantity delivered on a different date or to a different location. In another
example, if a stock picker finds only a partial quantity when picking inventory to fill a given
te r
order line, the delivery lines could be split so that the partially processed quantity can progress
further through the Order process.
I n
Transferring Delivery Lines to Cycle Counting
l e
You can use the Transfer to Cycle Count window to transfer delivery lines to cycle counting to
manage inventory discrepancies. For example, the inventory discrepancies can be caused by
c
r a
miscounting or defect in the item.
For example, you are processing a staged delivery line with quantity 10. If you use the transfer
O
cycle count functionality with this delivery line and specify two, the transfer cycle count
functionality:
U s
Confirmation. However, costs assigned after Ship Confirmation are not passed as freight costs
to Oracle Order Management; instead, they are stored in the shipping system for future
reference.
A I
Although freight costs can be defined in any currency, only the currency that is defined is
O
displayed. When costs are passed to Oracle Order Management, the currency is converted to
the order header currency.
l &
If you want to pass freight costs entered in the Shipping Transactions window to Oracle Order
a
Management for invoicing, then you have to set up a pricing modifier. Refer to the latest
n
Freight and Special Charges.
te r
version of Oracle Order Management Suite Implementation Guide for more information about
I n
Calculating Weight and Volume for Delivery Lines
You can calculate the weight and volume for selected delivery lines. When a new delivery
l e
detail (line) is created because of change in order line quantity, the system will retrieve the unit
c
weight and volume from the existing delivery details (belonging to same order line) so that all
r a
delivery details belonging to same order line have the same unit weight and volume. When a
O
delivery detail is created for a new order line, the system will retrieve the latest unit weight and
volume from Oracle Inventory Master Item window.
Pick Release Delivery Lines
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Delivery Parameters
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Shipping Parameters (T) Delivery A I
O
You use the Delivery tab to define the delivery grouping attribute, criteria for autocreate
delivery, and setting the appending limit.
l &
n a
Delivery Grouping Attributes: The shipping organization’s grouping rules that will be used
for grouping delivery lines into a Deliveries. Whenever a Delivery is created either
te
mandatory grouping attributes:
r
automatically or manually the Delivery Grouping rules must be adhered to. There are two
I n
• Ship From Location (Shipping Inventory Organization) and
c l
Optionally select e
• Ship To Location (Customer’s Ship-to site).
r a
• Customer
O
• Freight Terms
• FOB Code
• Intermediate Ship To Location
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Delivery Line Processing Statuses
U s
Not Applicable A I
Delivery Line statuses reflect the current Delivery Line placement within the shipping process.
O
The delivery line is invoicable but non-shippable, for example, a service line or a warranty
line.
l &
Not Ready to Release
n a
te r
The delivery line is not eligible for Pick Release
Occurs when the order line is manually imported into Oracle Shipping Execution using the
activity.
I n
Import Delivery Line concurrent process. It has not reached the Awaiting Shipping workflow
l
Ready to Release
c e
The sales order line that has been booked and passed to Oracle Shipping Execution. It is now a
r a
delivery line that is eligible for Pick Release.
O
Released to Warehouse
Pick Release has been started on the delivery line but not completed. Either no allocations were
created or the allocations have not been Pick Confirmed.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Packing into LPNs/Containers
U s
A I
You can pack multiple containers with multiple lines using one of following methods:
Auto-packing: Auto-packing provides a convenient and quick way of automatically packing
O
delivery lines into LPNs. The delivery lines are packed into LPNs based on the container-item
l &
relationship set up in Oracle Shipping Execution or in Oracle Inventory (defined as a customer
item). The container-item relationship defines the container that is used for packing the
a
delivery lines. The weight and volume allowances of the selected container are used to
n
te r
determine the number of required LPNs.
Auto-packing can be done in by selecting either of the following option:
I n
• Auto-pack: Only the detail LPNs are created and packed
l e
• Auto-pack Master: The delivery lines are packed into the detail container, and the detail
containers are packed into the parent/master container in one action
c
r a
Packing Workbench: You can use the Packing Workbench to split the delivery lines between
containers or to pack sequentially one container at a time to its full capacity.
O
Manually Packing Delivery Lines into Containers: You can manually pack containers if you
have delivery lines you want to pack without using the auto-pack method: for example, to
quickly pack delivery lines into a box.
U s
Prerequisite: Auto-Pack Deliveries SRS will only autopack items that have a pre-defined
container-item relationship. If Auto-Pack Master option is selected, then you must also have a
pre-defined container-container relationship.
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Container Load Details
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Container Load Details A I
O
When setting up container-item relationships, you define the maximum quantity of load items
&
(delivery lines) that can be packed into a container. These relationships are used to:
l
n a
• Calculate/estimate the number of containers required for delivery lines in a delivery or
trip. This enables you to use the auto-pack function to auto-pack delivery line items into
te r
new containers. The number of containers required to pack the delivery lines is
automatically calculated based on the container-item relationships.
I n
• Calculate the fill percentage for containers when the Fill Percentage Shipping parameter
c l e
is set to Quantity.
In addition to packing delivery lines in containers, Oracle Shipping Execution features an
r a
Auto-pack Master function that enables you to auto-pack delivery line items into containers,
and then auto-pack these containers into master containers such as pallets or railway boxcars.
O
The innermost container is considered the detail container item, and the pallet or boxcar is the
master (outermost) container. If you want to use the auto-pack master feature, you must set up
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
3. Continue defining all your Container-Item relationships in the next lines until completed.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Working with Trips
U s
A I
A Trip is carrier specific and contains at least two stops such as a stop to pick up goods and
another stop to drop off goods, and may include intermediate stops. Trips can be created
manually or automatically.
O
Creating Automatic Trip
l &
create trips:
n a
If your shipping process does not require advanced planning, you may prefer to automatically
te r
• Auto-creating a trip for a delivery: You can find the delivery you want to ship, and
auto-create a trip and related trip stops.
I n
• Auto-creating a trip for containers and lines: You can find the lines and containers
stops.
c l e
you want to ship and auto-create a trip which creates a trip, related deliveries, and trip
r a
Creating Manual Trip
• During transportation planning, you can manually create a trip and later assign delivery
O lines or find the delivery lines and create a trip. For example, for a regular trip scheduled
to depart every Friday, you can manually set up a trip ahead of time and then assign
delivery lines.
e O
• Calculates the weight, volume, and fill percentage of each open delivery and adds the
values to the trip’s current weight, volume, and fill percentage.
• Validates that the maximum load weight, the maximum internal volume, and the
U s
maximum fill percentage are not exceeded.
• Validates that minimum fill percentage requirements are attained.
A I
O
• Calculates (estimates) the number of containers for each delivery line based on
n a
You can execute Ship Confirm at the trip level. Within Shipping Transactions window, after
process.
te r
you have queried your trip, you can utilize Ship Confirm from the Action menu to run the
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Shipping Parameters
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Shipping Parameters A I
O
You define the default values for basic shipping information such as units of measure, Pick
&
Release rules, and delivery grouping rules. Shipping Parameters are organization specific. The
l
n a
parameters are arranged into the following tabbed regions in the Shipping Parameters window:
General: You define shipping units of measure such as weight, volume, and unit of measure
screening is required.
te r
used for percent fill basis calculations. You also determine whether or not export compliance
I n
Pick Release: You select pick slip grouping rules, release sequence rules, and printing
l e
parameters. You can select the Autocreate Deliveries to use the Delivery Grouping Rules you
define to group delivery line into deliveries. The Delivery Grouping Rules can be defined in
c
r a
the Delivery tab.
Shipping Transaction: You define the default document set to be printed at ship confirm,
O
default ship confirm rule, auto-pack options, goods dispatched (COGS) account, and enforce
packing in containers in this tab.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
General Parameters
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Shipping Parameters > (T) General Parameters A I
O
You use the General tab to define the weight and volume unit of measure (UOM) class
&
parameters, determine whether Export Compliance Screening is required, and select the
l
n a
percent fill basis calculations. The units of measure you select as the default are used when you
calculate the weight and volume of deliveries and the fill percentage of containers.
te r
Weight UOM Class: Select the weight class that contains the UOM used to set up your items,
containers and vehicles physical attributes. The values in the LOV are set up in Oracle
Inventory.
I n
l e
Volume UOM Class: Select the volume class that contains the UOM used to set up items,
containers and vehicles physical attributes. The values in the LOV are set up in Oracle
c
Inventory.
r a
Percent fill basis:There are three choices in the LOV, weight, volume, quantity.
O
• If weight or volume is chosen, the calculation will be made from the item’s and
container’s physical attributes defined in Oracle Inventory.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Transportation
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Shipping Parameters (T) Transportation A I
O
You use the transportation tab on the Shipping Parameters form to define Oracle
&
Transportation Execution specific parameters that meet your business needs.
l
In this tab you can set the following:
n a
Auto Apply Routing Rules:
te r
• Do not Apply: Routing guide rules are not applied
I n
• Delivery Creation: Routing guide rules will be applied for a delivery when it created
• End of Append Delivery: Routing guide rules will applied for a delivery when its
l e
appending limit has reached
c
Freight Payment and Audit:
r a
• Positive Tolerance Amount: You can define the positive tolerance for discrepancies in the
O freight bills. The value you specify is taken in terms of the currency value. For example,
you can set value of 10, which means that the discrepancy between the freight bill and the
bill of lading cannot be more 10.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Global Shipping Parameters
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Global Parameters (T) General (T) TransportationA I
O
You use the Global Shipping Parameters window to define parameters that impact the Oracle
&
Shipping Execution and Oracle Transportation Execution across all organizations of a
l
particular instance.
General Tab
n a
te r
You use the General tab on the Global Shipping Parameters form to define miscellaneous
parameters such as whether or not to enforce ship methods, defer interface, consolidate
I n
backorders, allow future ship dates. You also define the unit of measure(UOM) defaults for all
c l e
of your organizations.
• Enforce Ship Method: You select this check box to enforce that a ship method (carrier)
r a
is entered and recorded for each shipment. This is recommended if your business
practices require a record of the ship method/carrier for each shipment.
O
• Allow Future Ship Date: If you select this check box, you can enter a future date as the
Actual Departure Date while Ship Confirming the delivery. If you do not select this
O
- Firm Routing: The system will automatically change Firm status of Oracle
l &
Transportation Planning trips when it is tendered to Routing.
- Firm Content & Routing: The system will automatically change Firm status of
n a
Oracle Transportation Planning trips when it is tendered to Routing & Contents.
te r
• Calculation of Distance and Time:
- Highway Distance Empirical Constant: This is a numeric constant used to adjust
I n
the Euclidean distance to obtain the approximate highway distance between two
c l e
locations. It does not have a UOM.
- Average Highway Speed: This is the user specified average highway speed.
r a
• Number of Units UOM: The value you set here is used by Oracle Transportation Truck
Load (TL) loader to store rates based on the number of pieces or number of pallets.
O
• Pallet Item Type: This value is used by Oracle Transportation Execution to identify
pallets and to rate palletized Truck Load (TL) shipments.
- Supplier
e O
- Organization
- Customer
U s
•
- Carrier
A I
Delivery Date Calculation Method: You can select to determine the calculation of
O
initial pick-up date and ultimate drop-off date of a delivery.
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Shipping Exceptions
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Define Exceptions A I
O
The Shipping exceptions feature enables you to identify and correct shipping exceptions that
&
violate the requirements of your operation or that of your carriers and customers. The shipping
l
n a
exceptions feature gives you the ability to define exceptions and processes for handling them.
You can record exceptions automatically from within Oracle Shipping Execution, or you can
te r
log exceptions manually through the user interface input forms. You can initiate exception
handling, and view and track the exceptions as you manage them to resolution.
I n
Any automation requires user defined workflow activities.
l e
Application Program Interfaces (APIs) are provided to enable you, with some custom
programming, to use third party applications to log exceptions.
c
r a
See the Oracle Order Management Implementation Manual for further information about the
seeded exceptions.
O
Copyright © Oracle, 2005. All rights reserved.
Find Exception
1. (N) Shipping > Exceptions
2. (I) Find.
3. To view all exceptions, leave the search fields blank and choose the Find button.
− Exception Name: The particular name of the exception: for example, Picking Hold
exception.
− Logging Entity: The log-on entity of the exception: shipper, receiver, or
transportation carrier.
− Logged At Location: The location where the exception report was run (logged
location may be different from where the shipping exception occurred).
− Exception Location: The location where the shipping exception occurred.
− Inventory Organization: Exceptions according to a particular inventory
organization.
− Exception Type: Type of exception: delivery, picking, and trip.
− Exception Behavior: The behavior of the exception:
− Error: The exception must be handled before the task can be completed.
n l y
− Information Only: The exception must be handled before the task can be
e O
completed. However, you can override it so that the task can be completed.
− Warning: A warning is given but the task can be completed.
− Delivery Name: Exceptions for a particular delivery name.
U s
− Status: Describes the current status of the exception:
A I
− Open: Initial status--not yet associated with an exception name.
O
− Manual: This exception needs to be processed manually.
− No Action Required: No handling required for this exception.
l &
− Not Handled: This exception could not be handled.
a
− Departure Date: Exceptions according to the departure date.
n
te r
− Arrival Date: Exceptions according to the arrival date.
− Creation Date: Exceptions according to the date of creation.
4.
I n
Once you have completed your entries, click (B) Find.
c
View Exceptions l e
5.
r a
Click the tab that corresponds to the information you want to view or update. For example,
O
to update trip information for an exception, choose the Trip tab. Choose from the following
tabs:
7. (B) Open to display the selected exception in the Log Exception window.
8. Select the tab to display the details that you want to view or update: Exception tab,
Trip/Delivery/Container tab, or Inventory tab.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Pick Slip Grouping Rules
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Picking > Define Pick Slip Grouping Rules Form A I
O
Pick Slip Grouping Rules determine how released order lines will be grouped on Pick Slips.
l &
You have multiple Grouping Rules to meet a variety shipping needs. By associating Grouping
slips.
n a
Rules with Release Rules, you control what will be picked and how they will appear on pick
te r
You can select the following as the grouping criteria:
I n
• Subinventory: You group orders by subinventory so that all orders filled from one
subinventory would be filled before going to the next subinventory.
l e
• Order Number: You group picking lines that has the same order number.
c
• Delivery: All picking lines for the same delivery are grouped together on a pick slip. If
r a
there are multiple deliveries, multiple pick slips are created.
O
• Customer: All picking lines for the same customer are grouped together on a pick slip.
• Ship To: All picking lines for the same Ship To location are grouped together on a pick
slip.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
• User Defined: You can modify the Group By clause with this value. Grouping is done
according to the parameters set by the user. A unique pick slip number is generated
for each group. All tasks corresponding to a pick slip number is dispatched to a single
user.
• Wave Picking: Grouping by zone and the items are later sorted and consolidated into
individual orders. Wave picking is the quickest method for picking multi-item orders.
•
l y
Order Picking: Grouping is done by order and a unique pick slip number is generated
n
for each order. The entire order will subsequently be dispatched to a single user.
• O
Cluster: No grouping of pick tasks is done. The tasks are ordered by locator and
e
•
dispatched to the appropriate users.
U s
grouping and dispatched to the appropriate users.
A I
Bulk: Grouping by item and locator is done. Tasks are consolidated based on this
Assumptions
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
• Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
Tasks
1. Define a new pick slip grouping rule with a User Defined Pick Methodology, the name XX-
Subinventory and select source subinv to group By.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
• Password: welcome
Choose Responsibility
3. (N) Shipping > Setup > Picking > Define Pick Slip Grouping Rules
− Pick Methodology: User Defined.
− Rule Name: XX-Subinventory.
− Description: Group picking lines by source subinventory.
− Group by: Source Subinv.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Release Sequence Rules
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Picking > Define Release Sequence Rules Form A I
O
Release Sequence Rules are used during the Pick Release process to determine in what order to
&
allocate material to the released sales order lines. This can be very important if inventory
l
first.
n a
balances are less than 100% accurate. If material runs out, the most important orders are filled
Release Rule.
te r
Default the appropriate Release Sequence Rule on to the Release Sales Order form by using a
I n
Assign a numeric value to Order Number, Outstanding Invoice Value, Shipment Priority,
l e
Schedule Date and Departure Date to prioritize the importance of each attribute within the rule.
The lower the value the higher the priority.
c
r
Example: a
Specify whether the attribute should be evaluated in an ascending or descending order
O Priority
Shipping Priority: 1
Order
Descending
Meaning
(Highest to Lowest Value)
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Note 1: The lower the numeric value the higher the priority.
• Order: When you assign a number, you prioritize based on the order number.
• Outstanding Invoice Value: When you assign a number, you prioritize based
largest invoice value.
• Schedule Date: When you assign a number, you prioritize based on schedule
ship date.
n l y
•
O
Departure Date: When you assign a number, you prioritize based on planned to
ship date.
e
•
U s
Shipment Priority: When you assign a number, you prioritize based on planned
to ship date.
A I
O
Note 3: The “Outstanding Invoice Value” attribute is mutually exclusive with
“Order” attribute.
l &
3.
a
Select Ascending or Descending to prioritize entities in the ascending order or descending
order.
n
4. (M) File > Save.
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
In this practice you will learn how to create a Release Sequence rule.
Assumptions
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
• Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
Tasks
1. Create a release sequence rule with a name of XX-Oldest First that will allocate inventory to
the orders with the earliest ship date. If multiple orders have the same ship date, you want
the oldest orders to be filled first. Use an ascending priority scheme.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
• Password: welcome
Choose Responsibility
3. (N) Shipping > Setup > Picking > Define Release Sequence Rules
n l y
e O
Release Rules
U s
Order Management Super User, Vision Operations (USA)
A I
(N) Order Management > Shipping > Setup > Picking > Define Release Rules Form
O
Release Rules are used during the Pick Release process to define the criteria used to determine
&
which order lines will be released for picking. You can define Release Rules using the
l
following criteria:
n a
• Based on Rule: On the Release Sales Orders form as the Based on Rule. If used in this
I n
• Release Rule Name: On the Release Sales Orders SRS form as the Release Rule Name
l e
to dictate the release criteria which will execute in the background from a concurrent
request. A Release Rule is required to use SRS, standard report submission.
c
r a
Release Rules can be created based on criteria represented in three different tabs. This will
enable you to create rules that can respond to all of your picking needs.
O
Order tab - criteria = order type, order number, customer, item, category, delivery line status,
ship set #, #, scheduled ship dates start within and end within, or from and to, request dates
start within and end within, or from and to.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
3. (T) Inventory
5. (T) Shipping
Assumptions
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
• Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
Tasks
1. Create a Release Rule with a name of XX-Seattle’s Rule that will select eligible order lines
that are shipping from Seattle’s M1- location. Your rule will pick unreleased orders as well
2.
as backorders.
n
Select your XX-Oldest First Release Sequence Rule and choose to Autocreate Deliveries.
l y
3. Use M1 as the Warehouse, select your XX-Subinventory Pick Slip Grouping Rule and
e O
choose to Auto Allocate and Auto Pick Confirm.
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
• Password: welcome
Choose Responsibility
3. (N) Shipping > Setup > Picking > Define Release Rules form > (T) Order
− XX-Seattle’s Rule
− All
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
4.
r a
(T) Inventory
− M1
O − XX-Subinventory
− Yes
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Freight Carriers
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Freight Carriers, Cost Types > Freight CarriersA I
O
A freight carrier is a commercial company that transports shipments to and from customers,
&
suppliers, and internal organizations. You must set up each carrier’s information in Oracle
l
n a
Shipping Execution before shipping goods; You also must associate a general ledger account
with each carrier to collect associated costs.
te r
Enter the name and description of the carrier along with an account number. This account can
be used when you perform inter-organization transfers and specify freight costs. The account
I n
number is also available to the Account Generator workflow to build the account numbers that
will be used to capture shipping charges that will be passed to AR.
l e
Three setup steps are required. The are as follows:
c
r a
• Create Freight Carriers
• Create or select Service Level
O
• Create or select Mode of transportation
1. (N) Shipping > Setup > Freight Carriers, Cost Types > Freight Carriers
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Freight Cost Types
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Freight Carriers, Cost Types > Freight Cost TypesA I
O
Freight Costs are the actual costs incurred for the movement of goods by a carrier.
l &
Freight Costs include, but are not limited to: transportation costs, handling charges, insurance,
n a
import/export license fees, and miscellaneous charges, for example restocking fees, return fees,
and late payment charges. These miscellaneous charges are seeded Freight Cost type lookup
te r
codes that can be linked to a Freight Cost Type record.
You can assign a currency and an estimated amount to each Freight Cost record. The amount is
I n
defaulted on to the Freight Cost window within the Shipping Transactions form when a freight
c l e
cost name is entered, but can be over written when appropriate.
r a
O
Copyright © Oracle, 2005. All rights reserved.
1. (N) Shipping > Setup > Freight Carriers, Cost Types > Freight Cost Types
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Freight Costs – Freight Charges
U s
Charges
A I
Freight and Special Charges are defined as the dollar amount applied to the customer invoice
for movement of a shipment to a destination. O
&
Freight and Special Charges may be for the or the entire order or for a specific order line.
l
n
automatically based on the modifier setup. a
You can apply the changes to the order manually, through order import, through an API, or
Costs
te r
I n
Freight Costs are the actual costs incurred for the movement of goods that the carrier.
Within Shipping Execution, you can enter the freight costs and pass them to Oracle Order
l e
Management; Oracle Order Management then uses the cost as a basis for applying freight
c
charges to the customer invoice. To accomplish this process the user defines a pricing modifier
r a
to apply the charges to the order.
A cut-off point exists for processing charges to a customer invoice. The shipper has the ability
O
to enter freight and special charges at any time. However, only those costs entered prior to Ship
Confirm will qualify for processing with the customer invoice.
n l y
e O
Transit Times
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Regions and Zones > Transit Times A I
O
You use the Transit Times window to define the transit time for shipping items from origin
&
location to destination location. The origin and destination can be an internal location, external
l
n a
location, region, or zone. In this window, you define the different ship methods that can be
used to ship the items. For each ship method you define the following:
• Instransit Time
te r
• Maximum allowable daily load weight capacity that may be transported through ship
method
I n
c l e
• Cost per unit of goods transported with the ship method
Note: Defining the transit time enables Oracle Advance Planning application and Oracle
r a
Global Order Promising to calculate the ship or arrival date of the shipment.
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Shipping Documents Sets
U s
Define Shipping Document Sets
Order Management Super User, Vision Operations (USA) A I
(N) Shipping > Setup > Documents > Document Sets O
l &
You can group related shipping documents and other reports in a set that can be printed at Pick
n a
Release or Ship Confirm. You can include a variety of shipping documents in a set such as a
Bill of Lading and Packing Slip Report and determine the print sequence.
te r
Shipping Execution provides three pre-defined (seeded) document sets:
I n
• All Pick Release documents: You can set the default Pick Release Document Set in the
Pick Release tab of the Shipping Parameters window
l e
• Ship Confirm documents: You can set the default in the Document Set field of the Ship
c
Confirm window
r a
• Pack Slip only (at ship confirm): You can set the default in the Document Set field of
the Ship Confirm window
O
Choosing Printers for Shipping Documents and Labels
Order Management Super User, Vision Operations (USA)
number invoices generated by Oracle Oracle Accounts Recievables and bills of lading and
packing slips in Oracle Shipping Execution. n l
in an Oracle Applications product. For example, document sequencing can be used to uniquely
y
Using the Sequence Assignments window, you assign your sequence to number only those
e O
users create can be accounted for.
U s
documents that satisfy rules you define. Document sequences ensure that every document your
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Choose Printers
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Documents > Choose Printers A I
Assign your shipping documents and reports to specific printers.O
l &
Printers can be assigned on multiple levels; User, Responsibility, Applications and Site. If set
n a
at the User level each user could print to a different printer. If set at the Site level anyone
generating the report would be directed to the same printer.
te r
Choose the Document tab to display all documents assigned to a printer, and the printers tab to
display all printers assigned to a document.
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Roles and User Security
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Grants and Roles Definitions > Define Roles A I
Define Roles O
l &
Oracle Shipping Execution provides data access controls called roles that control users’ access
n a
to the Actions list and Tools menu in the Shipping Transactions form and the Quick Ship
window. Roles are assigned to users using grants that control access to view or edit specific
shipping data or actions.
te r
For each role, you can select the following data access controls that control edit and view
I n
access to shipping entities such as trips, stops, deliveries, lines/LPNs.
c l e
• Data Access Edit enables you to edit and view the data
• Data Access View enables you to browse the data
r a
• Data Access None prevents you from editing and browsing data and performing actions
O
A role can provide either view-only, edit-only, or a combination of view and edit access
depending on the set up of the role. You can create customized roles by defining the access
n l y
effective, or future), the default is view-only access to all organizations. If the user has
O
grants, the user's access is controlled by the effective grants. If there are overlapping
grants in the same organization or an intersection of grant date ranges, the union of grant
e
privileges controls the user's access.
• A grant cannot be designated as the default grant.
U s
A I
A role can be assigned to a user that spans all organizations instead of granting a unique grant
per organization. If an organization is not specified, the grant is applicable to all organizations.
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
1. (N) Shipping > Setups > Grants and Role Definitions > Define Roles
3. (T) Trips.
5. (B) Disable Actions to block all trip activities for this role.
6. (T) Stops.
e O
9. (T) Deliveries. Review the list of actions.
U s
10. (T) Lines/LPNs. Review the list of actions.
1. (N) Shipping > Setups > Grants and Role Definitions > Grants
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Assumptions
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
• Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
Tasks
1. Define a new role for your shipping clerks named XX-Shipping Clerk. Disable access to all
functions under Trips and Stops.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
• Password: welcome
Choose Responsibility
Define a Role
(N) > Shipping > Setup > Grants and Role Definitions > Define Roles
3. Name: XX-Clerk.
5. (T) Trips.
U s
10. Validate that Data Access is Edit.
A I
11. Accept all defaults.
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
A I
14. Accept all defaults.
O
15. Save.
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Assumptions
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
• Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
Tasks
1. Grant the shipping clerk role to the OMSUPER user for all Organizations.
• Password: welcome
Choose Responsibility
Grant Role
3. (N) > Shipping > Setup > Grants and Role Definitions > Grants
− User OMUSER
− Role: XX-Clerk.
− Leave Org. blank.
− Accept Start and End Dates.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Regions and Zones
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Regions and Zones > Regions and Zones A I
O
You use the Regions and Zones window to group locations by geographical areas and save the
&
effort of setting up point-to-point transit times. Transit Time refers to the time in business days
l
that it takes to ship between two sites.
You can perform the following:
n a
te r
• Group geographical areas into regions and set transit times for your warehouses to the
regions. For example: Create a region for San Francisco Bay U.S.A and specify that it
I n
consists of the cities San Francisco, Oakland, and Berkeley. Set up transit time of two
c l e
days from your New York U.S.A. warehouse to the San Francisco Bay U.S.A. region.
• Group regions into zones and set transit times from your warehouses to the zones to
r a
encompass a larger geographic area.
The advantage of planning shipments in terms of regions and zones are as follows:
O
• You enter and maintain in-transit and sourcing rules information between zones rather
than between every ship-from/ship-to address information
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Calendars
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Calendars > Assign A I
O
You use the Assign Calendars window to define valid shipping days and hours for a shipper,
&
receiver, and carrier. The shipping and receiving calendars are used to designate when your
l
n a
customers, customer sites, suppliers, supplier sites, and internal organizations can ship and
receive. For example, if you are shipping a delivery on Tuesday to arrive at your customer’s
te r
site on Wednesday, Ship Confirm checks the calendars to confirm the following:
• Your warehouse can ship on Tuesday
I n
• Your customer can receive goods on Wednesday
c l e
• Your carrier is able to pick up and drop off the deliveries on those days
Note: A Calendar must be created and defined in the Oracle Bill of Material (BOM)
r a
application as a Workday Calendar before it is assigned to a shipper, receiver, or carrier.
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Profile Options
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Profiles A I
O
During implementation, you set a value for each user profile option to specify how Oracle
&
Shipping Execution controls access to and processes data. The following are the profiles
l
n a
options available for Oracle Shipping Execution:
• WSH: Debug Enabled: When this option is set to Yes, the debug feature is activated.
te r
• WSH: Debug File Prefix: Naming convention for the Debug file is <Debug File Prefix
Profile>sessionid.dbg if the value of profile is null, naming convention is wsh
I n
<username>_<sessionid>.dbg established, it will be defaulted to dbuser:<dbusername>.
c l e
<sessionid> is database session id.
• WSH: Debug Log Directory: The value entered for this profile option must be specified
r a
as a UTL_FILE parameter value.
• WSH: Debug Module: The Module describes where to find the log message within the
O code. This profile indicates that debug messages from only those modules with names
beginning with the profile value will be logged. The naming convention for Module is:
n l y
access UPS servers for United Parcel Service integration. If no firewall is installed at
•
s
WSH: Overpicking Enabled: When you enable this option, overpicking is allowed.
U
Overpicking is using the Pick Confirm transaction to pick more than the requested
•
quantity of a delivery, up to the overshipment tolerance.
A I
WSH: Pick Release Batch Size: When you enable this option, you change the batch
O
size from 3 to 1000. Any value less than 3 is interpreted as 3 and any value greater than
1000 is interpreted as 1000
•
l &
WSH: Quick Ship Default View: When you enable this option, you are able to
a
determine the default view of the Quick Ship window. The default is the Delivery
n
•
Confirm view.
te r
WSH: Retain ATO Reservations: When you enable this option, you are allowed to
I n
avoid the redundancy of re-reserving an item. The inventory system retains the
reservation and the reservation status changes from Staged to Unstage, while the delivery
•
c e
line status changes to Backordered.
l
WSH: Run PL/SQL Profiler: When you enable this option, you determine whether or
• r a
not run the PL/SQL profiler.
WSH: Bulk Batch Size: When you enable this profile option, you to specify how many
O lines are to be interfaced to Oracle Order Management per call. This profile also enables
you to specify the batch size that is inserted in the Oracle Inventory tables.
Note: Usually the system administrator sets and updates the profile values. See: Setting User
Profile Options, Oracle Applications System Administrator’s Guide.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Lookups
U s
Order Management Super User, Vision Operations (USA)
(N) Shipping > Setup > Lookups A I
O
You use the Oracle Shipping Lookups window to define custom values for any list of values
&
(LOVs) throughout Oracle Shipping Execution. This enables you to customize the LOVs to
l
n a
meet your business requirements. This involves two steps:
1. Creating the values for the LOV in the Oracle Shipping Lookups window
te r
2. Creating a LOV and assigning the values from the Lookup window
I n
For example, when you create freight carrier in Oracle Shipping Execution, you can define the
various ship methods in the Oracle Shipping Lookups window and assign the same to a Freight
Carrier.
c l e
The values defined in the Oracle Shipping Lookups window depends on your accessibility
r a
level. They are explained as follows:
• User: You can add or update the lookup values as needed.
O
• Extensible: You can add new lookup values, but seeded values can only be modified or
disabled if your responsibility matches with the LOV.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Shipping Execution Reports
U s
A I
Oracle Shipping Execution provides you with a variety of flexible and easy-to-use reports to
help you improve productivity and increase control. Text attachments can be used with reports
O
and documents to print shipping application data: for example, unpacking instructions entered
l &
on a delivery line can be printed on the Packing Slip.
You can use the Shipping Reports and Documents window to select the report you want to
a
generate. The Shipping Execution Reports are displayed based on the report parameters you
n
te r
enter. The following are the Shipping Execution Reports:
Backorder Detail Report: Use the Backorder Detail Report to print details about backordered
I n
items for your organization.
Backorder Summary Report: Use the Backorder Summary Report to prints list of all
l e
unshipped orders. The report includes only open orders in an order cycle that includes Pick
c
Release. Multiple items and their backordered summary lines are displayed on the same page.
r a
This report displays order information such as the order type, order numbers, warehouse, last
O
shipped date, monetary amounts ordered, and the number of items outstanding and shipped.
These amounts involve totals for shippable items only because the Backorder Summary Report
does not account for non-shippable items.
U s
number, delivery name, shipper, ship-to address, carrier name, waybill number, quantity and
description of unpacked items, quantity and total of items packed in containers, total quantity
O
Master Bill of Lading Report: The master bill of lading is a record of the physical bills of
l &
lading and prints, on preprinted forms, the Ship Confirmed deliveries for a trip. It includes
origin, final destination, stop off points, container description, and trailer weight.
a
The Master Bill of Lading report shows information when a trip has multiple deliveries from
n
are deliveries in the trip.
te r
the origin to a common drop off point. It can be printed for a single delivery as long as there
I n
Commercial Invoice Report: The Commercial Invoice Report lists all confirmed shipped
items in a delivery. If you specify only a delivery name when defining the parameters of this
l e
report, Shipping Execution prints one commercial invoice per delivery within the trip.
c
This report lists ship date, commercial invoice ID (same as the delivery name),
r a
shipper/exporter, ship-to address, exporter identification number, freight carrier, all confirmed
items within each delivery (including purchase order number, order number, quantity, unit of
O
measure, unit value, and extended value for the items), total packages, total weight, and total
value. Country of origin is for future use.
l y
error information for each unprocessed request (partner, error type, error code, and interpreted
value).
n
The adapter statuses are:
• Start: Start up signal received
e O
• Active: Adapter is running
• Stop: Shut down signal received
U s
• ShutDown: Shut down in progress
A I
• Inactive: Adapter is inactive
O
Mailing Label Report: The Mailing Label Report consists of labels that print at document
l &
generation for identifying the ship-to address of the shipment. You will be able to print mailing
n a
labels before Ship Confirm since containers can be created without having to be associated to a
Delivery. If delivery and trip information is available, it also appears on the mailing label, for
te r
example, customer name, ship to address, carrier name, waybill number, number of packages
in the shipment, delivery number, container number, order number, and tracking number.
I n
Pick Slip Report: The Pick Slip Report prints all picking line details in a picking batch. This
c l e
report is used by the picker in the warehouse to collect all items included in shipments.
The pick slip displays the following sections:
r a
• Pick slip header: Lists report date, warehouse, pick slip number, and pick batch number.
• Release criteria: Lists pick slip grouping rule name and criteria used in grouping the pick
O slip such as customer, ship-to address, delivery name, trip stop address, order number,
shipment priority, carrier, subinventory, and requisition number.
U
Vehicle Load Sheet Detail Report: The Vehicle Load Details report prints the loadings
• organization from which the report is running
A I
sequence of items within a delivery. This report prints the following header information:
• customer name
I n
l
• delivery name
c e
• loading sequence number for the delivery
r a
• gross weight
O
geographical information each time. The filters are country, country code, province/state, city,
city code, and postal code.
&
Ship Confirm Deliveries SRS: Ship Confirm Deliveries SRS enables you to utilize the Auto
l
n a
Ship Confirm functionality within Oracle Shipping Execution.
Interface Trip Stop SRS: The Interface Trip Stop-SRS process runs the interface to update
te r
Oracle Order Management sales order lines, Departure Ship Notice Outbound (DSNO)
generation, and inventory.
I n
Process Deliveries SRS: Use this process to append deliveries and autocreate deliveries with
c l e
unassigned delivery lines and to auto create trips with delivery groups according to the
grouping parameters and compatibility constraints. This process can be limited in the execution
r a
of the request to particular delivery lines status, delivery status, date ranges, ship method or
customer. This program is applicable only to outbound delivery lines and deliveries. This
O
process will not consolidate deliveries into trips when Oracle Transportation Planning is
installed.
n l y
e O
Departure Ship Notice Outbound (DSNO)
U s
A I
The Departure Ship Notice Outbound (DSNO) is a notice used by the supplier to provide
advance notification of a shipment to the buyer or trading partner that the material has been
O
shipped. To perform the DSNO transaction the following steps have to followed:
l &
• Enable the Trading Partner for DSNO: This is one-time setup step for each Trading
Partner/Site/Transaction. The details of the trading partner is defined in the Define
a
Trading Partner window in the Oracle EDI Gateway. In this window you specify the
n
te r
transactions that are eligible for DSNO.
• Close Trip Stop: The Close Trip Stop procedure should be initiated in the Oracle
I n
Shipping Execution. This will initiate the EDI Gateway export process for each eligible
delivery associated with that Trip Stop. The DSNO is also generated when the Interface
l e
Trip Stop process is run.
c
• Invoke the EDI Translation Software: The Oracle EDI Gateway export process is
r a
complete when the output flat file has been generated. To complete the EDI process, a
O third party EDI translation software package is invoked to process the Gateway flat file
and transmit the result.
n l y
e O
Oracle Transportation Execution
U s
A I
Oracle Transportation Execution enables you to communicate, collaborate, and manage your
transportation processes with complete visibility to carrier rates, schedules, intransit events, and
O
delivery information. Deliveries can be managed with both carriers and customers. You can
l &
process and rate deliveries according to carrier requirements, and you can automatically assign
carriers to deliveries based on customer requirements, commodity requirements, or warehouse
a
location. For a complete integrated logistics solution, you can use Oracle Transportation
n
te r
Execution with Oracle Order Management, Oracle Warehouse Management, and Oracle
Shipping Execution to streamline your entire logistics execution process, from picking and
packing to shipping and final delivery. From the customer order to the final delivery, Oracle
I n
Transportation Execution provides you an automated process ensuring that your customer orders
c l e
are efficiently processed.
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Order Management Global Taxes Overview
U s
A I
This diagram is an overview of the tax process in Oracle Order Management. Tax Codes and
Tax Groups are assigned to items, customers, and sites, then use defaults and other setup
options to enter a tax estimate on the sales order..
O
• Implement global taxes for each operating unit.
l &
• Assign tax codes to customers.
n a
• Use the same setup steps in both Order Management and Receivables.
te r
• Estimate tax for orders at the time of order entry.
I n
• Define US Sales tax calculation based on customer ship-to address.
• For Order Management and Receivables, you can enter either a Tax Code or a Tax Group
l e
in the Tax Code field (for example, in the Customers - Standard window).
c
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Receivables Global Tax Overview
U s
A I
This diagram is an overview of the tax process in Oracle Receivables. Tax Codes and Tax
Groups are assigned to items, customers, and sites, or revenue account, then use defaults and
O
other setup options to default to the transaction to enable tax calculation. The main differences
Oracle Receivables.
l &
is tax estimations are created in Order Management versus the tax calculations created in
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Other Products
U s
A I
Tax calculation can involve other products, such as Oracle Projects and Oracle Order Capture.
Certain Customer Relationship Management (CRM) products use Order Capture to call the
Tax Engine and interface into Oracle Order Management. O
&
AutoInvoice involves calling the Tax Engine and then AutoAccounting to create the General
l
create invoices.
n a
Ledger account numbers when importing information from Order Management or Projects to
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Global Tax Overview
U s
Receivables to control all the tax calculations, accounting, and reporting.A I
With country specific setups, the Order to Cash process can be automated and enable
O
• Value Added Tax (VAT) - Imposed on the value added to goods or services at each stage
of their supply.
l &
professional services.
n a
• Goods and Services Tax (GST) - Sales tax levied on many consumer products and
te r
• Latin America - The Latin Tax Engine is an Oracle Global Financials feature used to
meet special tax needs in Latin American countries.
I n
• Canada - Goods and Services Tax (GST), Harmonized Sales Tax (HST), and Provincial
c l e
Sales Tax (PST) are sales taxes at the federal or provincial level.
• Japan - Consumption tax is VAT paid on an expense (input tax) that is recoverable
r a
against the VAT charged on revenue (output tax).
• Norway - Investment tax applies to certain items that are purchased for use or
O consumption by a VAT-registered entity.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Tax Overview
U s
A I
Oracle Order Management and Oracle Receivables process Output Tax, which is charged on
the supply of taxable goods and services, for example, on customer invoices or revenue items.
O
You should report Output Tax whenever you account for sales. Oracle Payables and Oracle
l &
Purchasing process Input Tax, which is paid on supplier invoices.
• Input tax: What you pay your tax authority via supplier invoices.
n a
• Output tax: What you receive from customers and then pay to your tax authority.
te r
• Amount Due to the Tax Authority consists of Output Tax on customers invoices minus
any Recoverable Input Tax on supplier invoices.
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Value Added Tax Overview
U s
A I
Value Added Tax (VAT) is imposed on the supply of goods and services paid for by the
consumer, but collected at each stage of the production and distribution chain. The VAT
O
charged on a customer invoice is called Output Tax. Any VAT paid on a vender invoice is
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
US Sales Tax Overview
U s
In general, the following are the series of steps in the US Sales tax cycle.
A I
• The amount that the customer pays a supplier includes US Sales tax, if applicable.
O
• The supplier is responsible for remitting the sales tax to the state tax authority.
l &
• Sales tax may not be applicable if the product is not taxable in the relevant tax
jurisdiction.
n a
r
• The state and local tax jurisdictions collect sales tax from suppliers.
te
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
US Sales Tax Example
U s
A I
Receivables determines sales tax based on a customer’s ship to address by using the Sales Tax
Location Flexfield structure. Every segment in the Sales Tax Location Flexfield is mandatory
O
during entry of you customer address for this process to function properly.
l &
The tax calculation process can be integrated with a tax partner. A tax partner is a third party
product that Oracle Applications integrates with to calculate and report state and local United
a
States (US) Sales tax. Tax partners include Taxware and Vertex.
n
te r
Note: If you are implementing a VAT system and do not wish to calculate tax nor validate
addresses, you can select the “No Validation – Country” Sales Tax Location Flexfield structure
I n
which requires that only the country is entered. In this case, Receivables derives the default
country from the “Default Country” system option. You may also implement Flexible Address
l e
Formats for country specific validation of customer address information.
c
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Tax Partner Process Overview
U s
A I
The United States (US) Tax Partner Solutions let you provide for complex tax calculation
needs while retaining the full power of Receivables to create and store all other tax data.
O
Receivables will use this information to create the appropriate tax line(s) and related
accounting information.
l &
n a
• Tax information stored in Receivables tax tables passes to the tax partner.
• The Tax Partner Solution is called whenever a tax rate is calculated by the Receivables
Tax Engine.
te r
• The Tax Partner returns a tax rate and tax amount for every invoice line.
I n
• AutoAccounting then generates account distribution tax lines based on the tax
c l e
information that the Tax Partner returned.
Oracle integrates with these partner products:
r a
Taxware Sales Use Tax System (PLSQL)
O
Vertex Quantum for US Sales & Use Tax (PLSQL)
Note: The integration supports US Sales tax only. Beginning with Oracle Release 11.5.7,
Taxware and Vertex software is bundled with Oracle Applications.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Oracle Applications supports other types of tax:
U s
Guides. A I
Recoverable and Non-Recoverable Input Taxes: See Oracle Purchasing or Payables User
n a
Withholding Taxes: Used in Oracle Payables to withholding taxes from suppliers in
te r
compliance with IRS or local authorities’ orders.
Goods and Service Tax: Sales tax levied on many consumer products and professional
services.
I n
c l e
Canadian Government, Provincial, and Harmonized Sales Tax
Sales Equalization Taxes
r a
Investment Taxes
O
Excise Duties
Latin and South American Tax regimes: Brazilian ICMS, IPI, Tributary Substitutions;
Argentine VAT Perception, Turnover Perception; Colombian VAT.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Tax Setup Steps
U s
A I
1. Select a Tax Method: Use Tax Method, along with the value you entered for the Calculate
Tax field assigned to your transaction type, to determine whether to calculate tax on your
transactions.
O
rates.
l &
2. Define Tax Codes and Rates: Enter and maintain your tax codes and their associated tax
n a
3. Setup Inclusive and Exclusive Taxes: Determine whether a line includes tax or the tax is
listed as a separate line.
te r
4. Setup Tax Groups (Optional): Group multiple conditional taxes under one name.
I n
5. Setup Item or Account Method (Optional): Define rules associated with line item and
l
revenue account.
c e
destination (point of supply) or assign a tax code to the natural account segment of your
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Tax Setup Steps (continued)
U s
A I
6. Define Tax Preferences, Defaults, and Results: Define Tax Code Defaults and hierarchy to
determine the order in which Receivables derives a default tax rate for manually entered or
imported transactions using AutoInvoice.
O
l &
7. Define Tax Exemptions and Exceptions: Exempt customers and items from a specific tax
or assign special rates to products you ship to specific locations.
n a
8. Define Transaction Types: Calculate tax for transactions with a specific transaction type.
te r
9. Define AutoAccounting For Tax: Assign account numbers to tax transactions.
10. Enable Calculation of Tax on Freight: Allow tax on freight transactions.
I n
11. Define Tax Profile Options: Set profile options to calculate tax in different ways based on
business needs.
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Defining Tax Codes and Rates
U s
Receivables, Vision Operations (USA)
(N) > Setup > Tax > Codes A I
O
Use the Tax Codes and Rates window to define the tax codes that you will use to record tax
&
information in Order Management and Receivables documents.
l
n a
Individual taxes can be either inclusive or exclusive on the price list. These taxes can both raise
and lower the price list amount and be calculated using a different Taxable Basis.
te
For each tax code, you can enter: r
I n
• Tax type: Select a Tax Method in the Tax Type field as VAT or Sales.
• Tax rate: Percentage used to calculate tax.
l e
• Taxable basis: Value of item or services used to calculate tax. Use After Discount, Before
c
Discount, Quantity, PL/SQL Formula, or Prior Tax as the basis.
r a
• Effective dates: Dates the Tax Code is available.
O
• Tax controls: Permits selection of Output or Input Tax class, Inclusive Tax, or Allow
Exempt check box of tax exemptions.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Setting Up Inclusive and Exclusive Tax
U s
Receivables, Vision Operations (USA)
(N) > Setup > Tax > Codes > (T) Control A I
O
AutoAccounting separates inclusive taxes from extended line amounts before creating revenue
&
and tax accounting entries. Tax inclusive calculations at the transaction line level may be
l
required in Canada, Japan, and Latin America.
n a
• Inclusive Tax: Line amount for an item includes the tax for the item.
te r
• Exclusive Tax: Tax not included in the line amount for the item.
I n
• Check Inclusive Tax check box in Tax Codes and Rates window for inclusive tax codes.
• Check Allow Inclusive Override check box if you want to allow changing tax code from
l e
inclusive to exclusive (or vice versa) when entering invoices.
c
r a
O
Copyright © Oracle, 2005. All rights reserved.
Assumptions
• If you are not attending training at an Oracle University or Authorized Partner
Education Center, you must have access to an Oracle Application Vision database or
comparable training test instance on which to complete this Practice.
• Replace XX in the Practice with a unique identifier such as your initials or a number.
(For Instructor Led Training classes, this number will be assigned to you). This is
necessary in order to create unique records within the database when performing the
Practice.
Tasks
Define a Tax Code
e O
2. Enter a tax code using the following information:
− Tax Code: XXTAX
U s
− Tax Type: Sales Tax
− Taxable Basis: After Discount
A I
− Tax Rate %: 10
− Sign: Credit O
− Tax Class: Output
l &
− Tax Account: 01-000-2520-0000-000
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
2. (T) Control
− Tax Class: Output
3. (T) More
− Tax Account: 01-000-2520-0000-000
4. (I) Save
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Tax Groups Overview
U s
A I
Multiple tax codes can be grouped together within the Order to Cash business cycle to build a
schedule or group of taxes.You can use tax groups to centralize the complex rules for finding a
O
tax code for a given place of supply and item. Tax groups can automate the selection of a
l &
single tax code based on condition sets. For example, in condition sets for a tax group, you can
specify which tax code to use for which destination country. In particular, tax groups support:
• Tax on cross-border transactions.
n a
• iStore and CRM applications.
te r
Tax groups can be used to calculate:
I n
• Multiple taxes for a transaction or transaction line.
c l e
• Compound taxes for a transaction.
- Assign a precedence number to each tax code in the Compounding Precedence
r afield. The highest precedence number calculates tax on all tax lines with a lower
precedence number, except when the taxable basis is prior tax.
O - Tax groups can also contain multiple independent branches of compounded tax.
n l y
e O
Setting Up Tax Groups (Optional)
U s
Groups window. A I
The Inclusive Tax setting from the tax code defaults to the Inclusive Tax check box in the Tax
O
You can assign tax groups to inventory items, customers, or customer sites.
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Compound Tax Example
U s
A I
Receivables permits the creation of compound tax charges during invoice entry and import if
the Compound taxes system option is set to Yes. Precedence numbers are assign to indicate
O
which tax line you want Receivables to compound. In the example of above, the tax is
l &
calculated on Line 1 and then the total amount of 107, which consists of 100 for the line
amount plus 7 for the Tax on Line 1 are used to calculate the tax on Line 2. The two taxes are
a
then added together to give a total tax due of 17.70. When setting up compound tax the
n
following is applicable:
te r
• Define tax precedence rules for compounding tax.
I n
• Prior to Release 11i, only one compounding branch was allowed.
• Compounding rules support multiple groups of “tax on tax” in a single invoice.
l e
• Use compounding precedence field to group tax lines together.
c
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Inclusive Tax with Compounding Example
U s
A I
The example illustrates multiple compounding with an Inclusive branch. Only one
compounding branch may be inclusive. If a compounding branch is inclusive, all Tax Codes in
the branch must be inclusive.
O
l &
In the example, Code A and B are one branch, both are Inclusive, and B uses the total of 100
plus A’s tax of 20 to calculated the 12 tax thus compounding Code A’s tax. Both Code A and
a
B taxes are added to the line because they are inclusive bring the line total to 132.
n
te r
Code C and D are a second branch with Code D compounding Code C tax. Code C and D are
not Inclusive so a separate line will be added to the invoice for the tax of 43 from Code C and
n
D’s calculation. The total invoice will be 132 plus 43 equals 175.
I
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Defining Condition Sets
U s
Receivables, Vision Operations (USA)
(N) > Setup > Tax > Groups > (B) Conditions > (T) Lines > (T) Actions A I
O
(N) > Setup > Tax > Groups > (B) Group Constraints > (T) Lines > (T) Actions
l &
Use group constraints to ensure that specific conditions are met before using a particular tax
a
group. Example: If ship-to province is not found, display system error message
n
te r
• Condition Sets indicate that each tax code is dependent on one or more conditions that
you specify such as: If ship-to country is Argentina, use this (Argentina) tax code.
I n
• Exception Sets can be assigned to the tax code to specify exceptions, including changing
the rate for a tax code automatically.
l e
• Constraints can be assigned to a tax group to ensure that specific conditions are met
c
before using this tax group. Example: If ship-to province is not found, display system
r a
error message.
O
Copyright © Oracle, 2005. All rights reserved.
Assumptions
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
n l y
1. Create a tax group named <XX> GSTPST with the following information:
e O
Tax Code Tax Compounding Condition
U s
Ship-to Location
GST 7
Rate
1
Precedence
Country
A I
Canada
NBPST 11 2 Province O New
l & Brunswick
QCTVQ 6.5 2
n aProvince Québec
Precedence
cl e
in Quebec province, Canada. Calculate the tax amount manually and complete this table:
Tax Code Tax Rate Taxable Calculation Tax Amount
r a Amount
O Total
3. Select the following tax codes, enter compounding precedence, and Conditions:
te r
− True, Use this tax code, False, Do not use this tax code.
I n
− Tax Code: QCTVQ
− Tax Rate: 6.5%
l e
− Compounding Precedence: 2
c
− (B) Conditions
r a
− Condition Name: <XX>Quebec
O − Clause: If
− Entity: Ship-To
− Field: Province
4. (I) Save.
Determine Tax
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Select a Tax Control Method
U s
transactions. A I
Receivables provides two methods for deriving the appropriate VAT tax code and rate for your
• Item Method O
• Account Method
l &
n a
Note: Before implementing Receivables, you need to decide whether you want to derive a
transaction line's tax code and rate from the line's item or the line's natural revenue account.
te r
Normally, the tax code for a transaction (line) is derived using rules associated with the line
item and destination (Point of Supply).
I n
The Item Method defaults tax codes based on a search hierarchy that you define in the System
l e
Options window. Typically within the Item Method, the system searches for a tax code at the
item, customer site, customer, and system option levels (in that order) and ignores any tax
c
r a
codes associated with the Revenue Account of the line item. The Item Method:
• Derives tax code from combination of inventory item and ship-to country.
O
• Can be used for multiple, conditional, compounded taxes.
• Supports integration between Oracle Receivables and:
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Setting Up Account Method (Optional)
U s
General Ledger, Vision Operations (USA)
(N) > Setup > Tax > Tax Options > (T) Account Level A I
Receivables, Vision Operations (USA) O
l &
(N) > Setup > System > System Options > (T) Tax Defaults and Rules
To set up the Account Method:
n a
te r
In General Ledger Tax Options window, assign a tax code to the natural account segment of
your revenue account. Set up validation by deriving tax code from revenue account).
I n
In System Options window, check Enforce Tax from Revenue Account and Revenue Accounts
check boxes and set Revenue Accounts tax code defaulting hierarchy to 1. Make sure Allow
l e
Tax Code Override check box is not checked for accounts that you want to validate.
c
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Setting Up Item Method
U s
Receivables, Vision Operations (USA)
(N) > Setup > Transactions > Items > Define Items > (T) Invoicing A I
O
Use tax groups to control tax calculation based on item destination. For example, use
&
conditions such as “If ship-to warehouse = Korea, use this tax code.”
l
n
using the default from the Master Item. a
Note: A different tax code or group can be assigned to each Inventory Organization rather than
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Defining Tax Preferences, Defaults, and Rules
U s
Receivables, Vision Operations (USA)
A
(N) > Setup > System > System Options > (T) Tax or (T) Tax Defaults and Rules
I
Tax Tab O
l &
Use the Tax tabbed region to define how Receivables calculates taxes.
a
Specify your tax method, the Location Flexfield Structure to use to determine your taxes for
n
te r
different customer locations, and whether to compound taxes for your customers.
Select to recognize tax exception rates for customers, customer sites, specific locations, and
take precedence.
I n
products, and whether exemptions that you define for specific products or customers should
l e
Tax Defaults an Rules Tab
c
Use the Tax Defaults and Rules tabbed region to Enforce Tax from your Revenue Account.
r a
Optionally set up your system to ensure that the tax code for your invoice lines is the same as
O
the tax code assigned to the “Account” segment of your Revenue account.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Defining Tax Exemptions
U s
Receivables, Vision Operations (USA)
(N) > Setup > Tax > Codes A I
For Customers: (N) > Customers > Standard > (T) Classification O
l &
For Customer Sites: (N) > Customers > Standard > (T) Addresses > (B) Open > (T) Business
Purposes >
(B) Open
n a
te r
For Items: (N) > Setup > Transactions > Items > Define Items > (T) Invoicing
I n
Exemptions: Define tax exemptions to fully or partially exempt a customer, item, or range of
items from specific tax codes.
l e
Exception: Define tax exceptions to assign special tax rates to products that you ship to specific
locations.
c
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Defining Transaction Types
U s
Receivables, Vision Operations (USA)
(N) > Setup > Transactions > Transaction Types A I
Order Management Super User, Vision Operations (USA) O
(N) > Setup > Transaction Types > Define
l &
a
Check the Tax Calculation check box in the Transaction Types window for each transaction
n
te r
type to ensure calculation of tax for all invoices.
Customers and customer sites not subject to tax should be assigned an exempt tax code.
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Defining AutoAccounting for Tax
U s
Receivables, Vision Operations (USA)
(N) > Setup > Transactions > AutoAccounting A I
O
Use the AutoAccounting window to specify how Oracle Receivables determines the General
&
Ledger account for tax. Enter Tax in the Type field.
l
n
you want to use to derive the account. a
Query all the segments of your Tax Account Flexfield. For each segment, assign the value that
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Defining Tax Profile Options
U s
System Administrator
(N) > Profile > System A I
O
• Tax: Allow Manual Tax Lines: Determines whether users can enter manual tax lines in
the Transactions windows in Receivables.
l &
n a
• Tax: Allow Ad Hoc Tax Changes: Provides selections for updating rates and amounts
assigned to tax codes in the transactions window in Receivables, if you defined tax codes
te r
in the Tax Codes and Rates window and set Ad Hoc to Yes.
• Tax: Allow Override of Customer Exemptions: Prevent users from entering unapproved
I n
exemptions in Receivables.
c l e
• Tax: Allow Override of Tax Code: Provides choices to override a system-derived tax
code during order or invoice entry.
r a
Note: The Tax: Calculate Tax on Credit Memos profile option has moved to the System
Options window.
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Defining Profile Options
U s
System Administrator
(N) > Profile > System A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Tax Accounting Overview
U s
A I
In Oracle Receivables, flexible setup options provide choices on how the tax is calculated and
which tax accounts to use for each activity. This can reduce tax liability in countries where
O
adjusting entries for tax are allowed. To set up for tax accounting, define:
• Tax accounting information for tax codes:
l &
- Deferred tax
n a
• Accounting rules for Receivables Activities:
te r
- Miscellaneous transactions
- Discounts
- Adjustments
I n
l e
- Finance charges
c
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Setting Up Tax Accounting for Deferred Tax
U s
Receivables, Vision Operations (USA)
(N) > Setup > Tax > Codes > (B) Tax Accounting A I
O
Deferred tax is an accounting method that defers the liability of tax to the time that the cash is
collected, rather than when the invoice is created.
l &
a
• Define deferred tax codes in the Tax Codes and Rates window.
n
te r
• Check the Deferred check box in the Tax Accounting window.
• Enter accounts in the Tax Account and Interim Tax Account fields of the Tax Accounting
window.
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
Assumptions
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
1. Define a deferred tax code with a 20% rate.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
3.
I n
Select Output in the Tax Class field in the Control tab.
4.
−
c l e
Enter the GL Accounts in the More tab.
Tax Account: 01.000.2520.0000.000
5. r a
Select the Tax Accounting button to open the Tax Accounting window.
6. O
Select the Deferred Tax check box.
General Ledger (GL) accounts for Receivables Activities that have Tax Code as the
source may be entered in this window.
8. (I) Save.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Defining Receivables Activities
U s
Receivables, Vision Operations (USA)
(N) > Setup > Receipts > Receivable Activities A I
Define the GL Account and Tax Code Sources. O
• GL Activity Source Options:
l &
- Activity GL Account
n a
- Revenue on Invoice
- Tax Code on Invoice
te r
I n
- Distribution Set
Tax Code Source Options:
• None
c l e
r
• Invoicea
• Activity
O
Check the Recoverable or Non-Recoverable check box if the Tax Code Source is Invoice.
Enter a Tax Code if the tax code source is Activity.
n l y
e O
Changing Tax Transactions
U s
Receivables, Vision Operations (USA)
(N) > Transactions > Transactions Summary > (B) Open A I
O
In Receivables, Tax Adjustments can be made in the Transactions or Transactions Summary
window.
l &
n a
The profile option, Tax: Allow Override of Tax Code, permits changing an automatically
generated tax code. Oracle Receivables displays the new tax rate and amount.
te r
If you use AutoAccounting, rerun the Review Accounting after changing the tax code to update
your tax account for this invoice line.
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Adjusting Tax on Invoices
U s
Receivables, Vision Operations (USA)
(N) > Transactions > Transactions Summary > (B) Adjust A I
Receivables activities for tax adjustments must be set up first. O
l &
• When you create a tax adjustment Oracle Receivables automatically verifies that it is
within your adjustment approval limits.
n a
te r
- If within your assigned approval limit for the currency of that item, Oracle
Receivables updates your customer’s balance to reflect the adjustment.
I n
- If outside your approval limits, Oracle Receivables creates a pending adjustment
with a status of Pending Approval which will need to be approved by a higher level
c l e
employee with the proper approval limit.
• Any adjustments that have been applied to the tax lines of an invoice and cannot be
r a
claimed from the state, should use a receivables activity where tax is not posted to a sales
tax liability account (for example, bad debt write-offs of sales tax amounts).
O
• If using a tax partner and the option for posting adjustments to the tax partner is selected
in the Receivables Activities window:
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Tax Credit Memo
U s
A I
Tax Credit Memos can be entered from the Credit Transactions or Transactions Summary
window, or by selecting the Credit Lines and entering individual credit lines.
• The credit can be either an amount or tax percentage. O
&
• When crediting lines individually, the tax for the item line will automatically calculate,
l
a
just as it would if you entered transaction lines.
n
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Tax Reporting Ledger Overview
U s
Reporting Ledger. A I
Oracle Applications simplifies global tax management by providing a single cross-product Tax
O
• Tax Reporting Ledger produces a single report of all your taxable sales and purchase
&
documents across Oracle Receivables, Oracle Payables, and Oracle General Ledger.
l
n a
• The Tax Reporting Ledger can be used in conjunction with any reporting tool, including
RXi and Application Desktop Integrator for Variable Format Reports.
te r
• The following tax registers are supported:
- Single Cross-Product Tax Register.
I n
- Standard Input and Output Tax Registers.
l e
- Deferred Output Tax Register.
c
- Recoverable and Non-Recoverable Tax Registers.
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Tax Extract Overview
U s
A I
The Tax Extract finds all taxed transaction details from any of the sources, summarizes this
information, and records a copy in the interface table for reporting. Information from
O
designated global descriptive flexfields is also copied into the interface table.
l &
The interface table is a standard RXi extract format that allows RXi, Oracle Reports, or any
client program to access the data using a simple query.
n a
The Tax Extract can be called from several sources, including Oracle Reports and RX and
RXi-enabled concurrent programs:
te r
• Financial Tax Register: The Financial Tax Register uses the RXi reporting tool to
I n
generate tax register reports with the Tax Extract data. This version runs both the extract
and the publishing steps together. Available attribute sets:
l e
- DEFAULT (Tax Register) - Reporting on Receivables and General Ledger
c
r atransactions
- ATTRSET2 (Tax Register with Tax Recovery) - Reporting on Payables
O transactions
- User-defined
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Sources of Data
U s
A I
Global descriptive flexfields store country or region-specific information that is extracted into
the Tax Reporting Ledger through the Tax Extract, letting you include country/region-specific
information in country/region-specific formats.
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Tax Ledger Reporting Options
U s
A I
The MO: Top Reporting Level profile option and the Reporting Context (Parameters) on the
Reports are used to meet both Multiple Organization and Cross Product reporting
requirements.
O
l &
The MO: Top Reporting Level profile option determines which reporting levels are available
for a particular responsibility when reporting across multiple organizations. Available values
a
include: Set of Books, Legal Entity, and Operating Unit.
n
te r
• To create reports across multiple organizations, use the Reporting Level and Reporting
Context parameters to determine the report content.
I n
- For Oracle Applications Multiple Organization Support feature, the Reporting
Level parameter defaults to Operating Unit.
l e
- For others, it defaults to Set of Books.
c
r a
• To create cross-product reports with information from Oracle Payables, Oracle
Receivables, and Oracle General Ledger, enter ALL in the Product parameter.
O
• To create report across operating units and products, use the Product parameter along
with the Reporting Context parameters and the MO: Top Reporting Level profile option
to control content.
n l y
e O
Matrix Reporting
U s
amounts. A I
Use Matrix Reporting to show a single line in the Tax Reporting Ledger for two or more tax
te r
To enable Matrix Reporting, use the Matrix Report Flag parameter on the Tax Reporting
Ledger.
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
RXi Report Steps
U s
A I
The RXi Report Administration Tool is used to design content layout of reports and then
publish the report with the designed layout to meet reporting requirements. Steps are:
O
• Design content and layout of reports by selecting the RX-only report and then, copying
&
and modifying the existing attribute set using the columns available.
l
n
(publish) the data that was extracted. a
• Extract the data into the interface table which results in an RX-only file, and then print
r
• Publish reports in different formats using different attribute sets.
te
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Modifying Attribute Sets
U s
modify an existing attribute set that you previously defined. A I
Use the Attribute Set window to change a new attribute set that you have just copied or to
Displayed Columns O
&
In the Displayed Columns tab, the Available list box displays all columns that are available for
l
n a
this report but not currently included in the report output. The Displayed list box displays the
report columns that are included in the report output. There are more than 600 available
te r
columns for the Tax Reporting Ledger. Use the Default Format tab to define how date and time
values should be displayed in the report.
Available Column Groups
I n
Extract
Legal Entity
c l e Reporting Entity
Transaction Header Level
Reporting Context
Billing
r
Shipping
a
Taxable Amounts
Banking
Taxable Line fields
Receivables Transactions
Tax Amounts
O
Tax Line fields, including Tax Code and Tax Rate Total Amounts
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Defining Summary Details
U s
A I
A summary column is a column whose values are either summed or counted. You can
designate the summed and counted levels printed, and you can rename the default summary
prompts.
O
l &
The Summary Details window displays the report summary levels and the column grouping
levels for the column that you select in the Column Details window.
The report summary levels are:
n a
the page
te r
• Page Total Sum: The sum or count of records on the current page printed at the bottom of
I n
• Running Page Total: The sum or count of records up to and including the current page
c l e
printed at the bottom of the page
• Previous Page Total Sum: The sum or count of records up to but not including the current
r a
page printed at the top of the page
• Report Total Sum: The sum or count of records in the entire report. The grouping levels
O displayed in the Summary Details window are all grouping levels up to, but not
including, the grouping level for the selected column.
n l y
e O
Publish RXi Reports
U s
A I
Use the Publish RX Reports concurrent program to print RXi report output. You can generate
an RXi report with its default attribute set, or with an attribute set that you defined in the
O
Attribute Set window. The report is created according to the layout definition of the attribute
n a
Use the the Submit Request window or the ReQuest Center in Application Desktop Integrator
te r
(ADI) to submit the RXi report and the Publish RX.
• If you run the RXi report and the Publish RX Reports concurrent program together in one
I n
step, the Attribute Set and Output Format parameters are included in the list of RXi report
parameters.
l e
• If you need to submit the Publish RX Reports concurrent program separately after you
c
r a
run the RXi report, use the Requests window to obtain the RXi report request ID.
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
Managing Access to RXi Reports and Attribute Sets
U s
interface table by RXi reports. A I
User access to RXi reports means that a user also has access to any data retrieved into the
O
Because an attribute set controls the content of the report output, you must assign attribute sets
&
to a responsibility if you want to restrict data access.
l
n a
• Use the Define Security window in the Report eXchange Designer responsibility to
assign RXi report attribute sets to a request security group.
te r
• The request security group can then be assigned to one or more responsibilities.
• If you define a new attribute set, by default this attribute set is available to all users who
I n
have access to the associated report.
c l e
• However, if you link this attribute set to a particular responsibility, then only that
responsibility can access the attribute set and use it when publishing reports.
r a
• By default, the Attribute Set window and the Purge RX Interface Data concurrent
program available only from the Report eXchange Designer responsibility.
O
Copyright © Oracle, 2005. All rights reserved.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
Copyright © Oracle, 2005. All rights reserved.