PK LnÉHoaŤ, mimetypeapplication/epub+zipPK LnÉH OEBPS/ofbsb_chap15.htm ˙
Oracle purchasing is the formal process of buying goods and services. The process usually starts with a demand or requirement - this could be for a physical part (inventory) or a service. A requisition is generated, which details the requirements, and which actions the procurement department to raise the purchase order.
Purchase orders can be of various types, including:
Standard purchase order - a one-time buy.
Blanket purchase agreement - an agreement on specific terms and conditions: date and quantity and amount are not specified.
Purchase orders are normally accompanied by terms and conditions which form the contractual agreement of the transaction. The supplier delivers the products or service and the customer records the delivery. An invoice is sent by the supplier which is checked against the purchase order and documents specifying the goods received. The payment is then made and transferred to the supplier.
This chapter describes the following test flows in Oracle Purchasing:
Online Standard Purchase Order Creation
Online Blanket Purchase Agreement and Release Creation
Standard Purchase Order Creation using Autocreate
Release Creation using Autocreate
Release Creation using Autocreate with Approved Supplier List and Sourcing Rules
Standard Purchase Order Creation using Autocreate with Contract Purchase Agreement Reference
Online Standard Purchase Order Creation in Buyer Work Center
Standard Purchase Order Creation using Autocreate in Buyer Work Center
Standard Purchase Order Creation with Global Blanket Purchase Agreement Reference using Autocreate in Buyer Work Center
Standard Purchase Order Creation with Global Blanket Purchase Agreement Reference using Autocreate with Approved Supplier List and Sourcing Rules in Buyer Work Center
Standard Purchase Order Creation using Autocreate with Contract Purchase Agreement Reference in Buyer Work Center
Requisition Change Order
Online Standard Purchase Order Creation for Services Item using Forms
Online Standard Purchase Order Creation for Services Item using Buyer Work Center
Modification of Standard Purchase Order in Forms
Modification of Standard Purchase Order in Buyer Work Center
Cancellation of Standard Purchase Order in Forms and Backing Requisition Cancellation
Cancellation of Standard Purchase Order in Buyer Work Center and Backing Requisition Cancellation
Copy of Standard Purchase Order in Forms
Copy of Standard Purchase Order in Buyer Work Center
eBtax for Purchasing
None.
Table 15-1 Profile Options for Oracle Purchasing
Profile Name | Profile Value | Profile Level |
---|---|---|
MO: Operating Unit |
Vision Operations |
Site |
MO: Default Operating Unit |
Vision Operations |
Site : Vision Operations Level : Responsibility Value : iProcurement |
MO: Security Profile |
Global Vision |
Site |
HR: Security Profile |
Vision Corporation |
Site |
HR: Business Group |
Vision Corporation |
Site |
GL: Data Access Set |
Vision Operations (USA) |
Site |
POR: Amount Based Services Line Type |
Fixed Price Services |
Site |
Not applicable.
Operating Unit : Vision Operations (Used for Creating Requisition, POs, Invoices and Payments)
Inventory Org : V1 (Used for Receiving Goods)
Table 15-2 User Setup Data for Oracle Purchasing
User | Employee | Role | Position | Job | Hierarchy |
---|---|---|---|---|---|
Tgreen |
Green, Mr. Terry |
Requestor |
ACC430.Senior Accountant |
ACC400.Accountant |
Materials |
Operations |
Stock, Ms. Pat |
Buyer or Approver |
MM400.Materials Manager |
MGR500.Manager |
Materials |
Cbaker |
Baker, Catherine |
Buyer or Approver |
BUY501.Buyer 1 |
BUY500.Buyer |
Materials |
Mfg |
Smith, Mr. Jonathan |
Receiver |
VPM200.VP Materials |
VPM200.Vice President Of Materials |
Materials |
Cbrown |
Brown, Ms. Casey |
Account Payable or Buyer |
EX140.Chief Financial Officer |
EX100.Executive |
Materials |
Table 15-3 Approval Setup Data for Oracle Purchasing
Employee | Position | Approval Assignments | Approval Group | Comments |
---|---|---|---|---|
Green, Mr. Terry |
ACC430.Senior Accountant |
Requisition, Standard Purchase Order, Blanket Purchase Agreement, Contract Purchase Agreement , Release |
Manager |
Can approve doc total Up to $25,000 |
Stock, Ms. Pat |
MM400.Materials Manager |
Requisition, Standard Purchase Order, Blanket Purchase Agreement, Contract Purchase Agreement, Release |
Manager |
Can approve doc total Up to $25,000 |
Baker, Catherine |
BUY501.Buyer 1 |
Requisition, Standard Purchase Order, Blanket Purchase Agreement, Contract Purchase Agreement, Release |
Buyer Materials |
Can approve doc total Up to $50,000 |
Brown, Ms. Casey |
EX140.Chief Financial Officer |
Requisition, Standard Purchase Order, Blanket Purchase Agreement, Contract Purchase Agreement, Release |
Executive |
Can approve any doc total |
If the document total is more than $25,000, the document moves to the next approver in the hierarchy, which in this case is cbaker.
If the document total is more than $50,000, the document moves to the next approver in the hierarchy, which in this case is cbrown.
Table 15-4 Responsibility Setup Data for Oracle Purchasing
Window Name | Field Name | Field Value |
---|---|---|
Responsibility |
Responsibility |
Purchasing, Vision Operations(USA) iProcurement Inventory, Vision Operations(USA) Payables, Vision Operations(USA) Human Resource, Vision Enterprises Tax Managers |
Table 15-5 Item Setup Data for Oracle Purchasing
Window Name | Field Name | Field Value |
---|---|---|
Item Master |
Item |
CM00042 (with all orgs assigned and with the properties: Inventory, Stackable, Transactable, Reservable, Purchased, Purchasable, Invoiceable, Costing Enabled and Inventory Asset Value) |
Table 15-6 Purchasing Related Page Setup Data for Oracle Purchasing
Page Name | Field Name | Field Value |
---|---|---|
Purchasing Options |
Line Type |
Goods |
Accrue Expense Items |
Period end | |
Accrue Inventory Items |
At Receipt | |
Expense Ap Accrual Account |
01-000-2220-0000-000 | |
PO Number |
Automatic | |
Requisition Number |
Automatic | |
Receiving Options |
Receiving Inventory Account |
01-000-1410-0000-000 |
Clearing Account |
01-000-1410-0000-000 | |
Next Receipt Number |
Any value |
Table 15-7 Purchasing Related Window Setup Data for Oracle Purchasing
Window Name | Field Name | Field Value |
---|---|---|
Financial Options |
Use Approval Hierarchies |
Yes |
Table 15-8 Document Styles for Oracle Purchasing
Page Name | Field Name | Field Value |
---|---|---|
Document Styles |
Standard Purchase Order |
Goods, Services, Temp Labor |
Blanket Purchase Agreement |
Price Breaks, Price Differentials |
Table 15-9 Document Types for Oracle Purchasing
Page Name | Field Name | Field Value |
---|---|---|
Standard Purchase Order |
Default Hierarchy |
Materials |
Owner can Approve |
Check | |
Forward Method |
Hierarchy | |
Security Level |
Public | |
Archive On |
Approve | |
Blanket Purchase Agreement |
Default Hierarchy |
Materials |
Owner can Approve |
Check | |
Forward Method |
Hierarchy | |
Security Level |
Public | |
Archive On |
Approve | |
Contract Purchase Agreement |
Default Hierarchy |
Materials |
Owner can Approve |
Check | |
Forward Method |
Hierarchy | |
Security Level |
Public | |
Archive On |
Approve | |
Purchase Requisition |
Default Hierarchy |
Materials |
Owner can Approve |
Check | |
Forward Method |
Hierarchy | |
Security Level |
Public |
Buyer logs in with Purchasing responsibility and creates a standard purchase order with Goods 6oÉline type for an inventory item. Receiver logs in with Inventory responsibility and receives the full quantity of the goods against standard purchase order and a receipt is created in the inventory organization. The Accounts Officer logs in with Payables responsibility and creates a standard invoice, matches the invoice to the standard purchase order and validates the invoice. Once the invoice is validated, a quick payment is done and payment document is created.
None.
Not applicable.
Not applicable.
Not applicable.
Buyer logs in with Purchasing responsibility and creates a blanket purchase agreement with goods line type for an inventory item. Buyer creates a blanket release against the agreement. Receiver logs in with Inventory responsibility and receives the full quantity of the goods against blanket release and a receipt is created in the Inventory organization. The Accounts Officer logs in with Payables responsibility and creates a standard invoice, matches the invoice to the standard purchase order and validates the invoice. Once the invoice is validated, a quick payment is done and payment document is created.
None.
Not applicable.
Not applicable.
Not applicable.
This flow covers approval functionality. Once the buyer approves the standard purchase order which has a document total more than $25000, the document goes for approval for the next approver. The approver approves the standard purchase order from the notification received.
Requester logs in with Purchasing responsibility and creates a purchase requisition with Goods line type for an inventory item. Buyer creates standard purchase orders from requisition using Auto Create process. After submitting for approval, standard purchase order goes to the next approver in the hierarchy as the document total is more than $25000. Receiver logs in with Inventory responsibility and receives the full quantity of the goods against standard purchase order and a receipt is created in the inventory organization. Accounts Officer logs in with Payables responsibility and creates a standard invoice, matches the invoice to the standard purchase order and validates the invoice. Once the invoice is validated, a quick payment is done and payment document is created.
None.
Not applicable.
Not applicable.
Not applicable.
Requester logs in with Purchasing responsibility and creates a purchase requisition with Goods line type for an inventory item. Buyer creates blanket purchase agreement and creates a release from requisition using auto create process. Receiver logs in with Inventory responsibility and receives the full quantity of the goods against blanket release and a receipt is created in the inventory organization. Accounts Officer logs in with Payables responsibility and creates a standard invoice, matches the invoice to the standard purchase order and validates the invoice. Once the invoice is validated, a quick payment is done and payment document is created.
None.
Not applicable.
Not applicable.
Not applicable.
Requester logs in with Purchasing responsibility and creates a purchase requisition with Goods line type for an inventory item. Buyer creates blanket purchase agreement .Buyer then creates approved supplier lists, sourcing rules for the item and sources the blanket agreement. Now Buyer creates a release from requisition using auto create process. Receiver logs in with Inventory responsibility and receives the full quantity of the goods against blanket release and a receipt is created in the Inventory organization. Accounts Officer logs in with Payables responsibility and creates a standard invoice, matches the invoice to the standard purchase order and validates the invoice. Once the invoice is validated, a quick payment is done and payment document is created.
None.
Not applicable.
Not applicable.
Not applicable.
Requester logs in with purchasing responsibility and creates a purchase requisition with Goods line type for an inventory item. Buyer creates contract purchase agreement and then a standard purchase order is created from requisition using auto create process referring the contract purchase agreement. Receiver logs in with inventory responsibility and receives the full quantity of the goods against standard purchase order and a receipt is created in the inventory organization. Accounts Officer logs in with payables responsibility and creates a standard invoice, matches the invoice to the standard purchase order and validates the invoice. Once the invoice is validated, a quick payment is done and payment document is created.
None.
Not applicable.
Not applicable.
Not applicable.
Buyer logs in with purchasing responsibility and creates a standard purchase order with Goods line type for an inventory item in Buyer Work Center. Receiver logs in with inventory responsibility and receives the full quantity of the goods against standard purchase order and a receipt is created in the inventory organization. Accounts Officer logs in with payables responsibility and creates a standard invoice, matches the invoice to the standard purchase order and validates the invoice. Once the invoice is validated, a quick payment is done and payment document is created.
None.
Not applicable.
Not applicable.
Not applicable.
Requester logs in with iProcurement responsibility and creates a purchase requisition with goods line type for an inventory item. Buyer creates standard purchase orders from requisition using Auto Create process in Buyer Work Center. After submitting for approval, standard purchase order goes to the next approver in the hierarchy as the document total is more than $25000. Receiver logs in with Inventory responsibility and receives the full quantity of the goods against standard purchase order and a receipt is created in the Inventory organization. Accounts Officer logs in with Payables responsibility and creates a standard invoice, matches the invoice to the standard purchase order and validates the invoice. Once the invoice is validated, a quick payment is done and payment document is created.
None.
Not applicable.
Not applicable.
Not applicable.
Requester logs in with iProcurement responsibility and creates a purchase requisition with Goods line type for an inventory item. Buyer creates a global blanket purchase agreement and then a standard purchase order is created from requisition using auto create process referring the global blanket purchase agreement in buyer work center. Receiver logs in with inventory responsibility and receives the full quantity of the goods against standard purchase order and a receipt is created in the inventory organization. Accounts Officer logs in with payables responsibility and creates a standard invoice, matches the invoice to the standard purchase order and validates the invoice. Once the invoice is validated, a quick payment is done and payment document is created.
None.
Not applicable.
Not applicable.
Not applicable.
Requester logs in with iProcurement responsibility and creates a purchase requisition with Goods line type for an inventory item. Buyer creates approved supplier list, sourcing rules for the item. Creates a global blanket purchase agreement and then a standard purchase order is created from requisition using auto create process referring the global blanket purchase agreement in buyer work center. Receiver logs in with inventory responsibility and receives the full quantity of the goods against standard purchase order and a receipt is created in the inventory organization. Accounts Officer logs in with payables responsibility and creates a standard invoice, matches the invoice to the standard purchase order and validates the invoice. Once the invoice is validated, a quick payment is done and payment document is created.
None.
Not applicable.
Not applicable.
Not applicable.
Requester logs in with iprocurement responsibility and creates a purchase requisition with Goods line type for an inventory item. Buyer creates contract purchase agreement and then a standard purchase order is created from requisition using auto create process referring the contract purchase agreement in Buyer Work Center. Receiver logs in with inventory responsibility and receives the full quantity of the goods against standard purchase order and a receipt is created in the inventory organization. Accounts Officer logs in with payables responsibility and creates a standard invoice, matches the invoice to the standard purchase order and validates the invoice. Once the invoice is validated, a quick payment is done and payment document is created.
None.
Not applicable.
Not applicable.
Not applicable.
Requester logs in with iProcurement responsibility and creates a purchase requisition with Goods line type for an inventory item. Buyer creates standard purchase order from requisition using auto create process in Buyer Work Center. Requester creates a change order by changing the quantity and need by date and submits for buyer's approval. Buyer receives the notification for change request and all the changes will be reflected to the standard purchase order automatically once the buyer approves the notification.
None.
Not applicable.
Not applicable.
Not applicable.
Buyer logs in with purchasing responsibility and creates a standard purchase order with Fixed Price Services line type in forms. Receiver logs in with iProcurement responsibility and receives the services against the standard purchase order and a receipt is created. Accounts Officer logs in with payables responsibility and creates a standard Invoice, matches the invoice to the standard purchase order and validates the invoice. Once the invoice is validated, a quick payment is done and payment document is created.
None.
Not applicable.
Not applicable.
Not applicable.
Buyer logs in with purchasing responsibility and creates a standard purchase order with Fixed Price Services line type in Buyer Work Center. Receiver logs in with iProcurement responsibility and receives the services against the standard purchase order and a receipt is created. Accounts Officer logs in with payables responsibility and creates a standard Invoice, matches the invoice to the standard purchase order and validates the invoice. Once the invoice is validated, a quick payment is done and payment document is created.
Receipt Routing "Direct Delivery" set at Supplier level.
Not applicable.
Not applicable.
Not applicable.
Buyer logs in with purchasing responsibility and creates a standard purchase order with Goods line type for an inventory item in forms. Once the document is approved, buyer updates the quantity and approves the document
None.
Not applicable.
Not applicable.
Not applicable.
Buyer logs in with purchasing responsibility and creates a standard purchase order with Goods line type for an inventory item in Buyer Work Center. Once the document is approved, buyer updates the quantity and approves the document
None.
Not applicable.
Not applicable.
Not applicable.
Requester logs in with purchasing responsibility and creates a purchase requisition with Goods line type for an inventory item in forms. Buyer creates standard purchase order from requisition using auto create process. Buyer cancels the standard purchase order along with backing requisition.
None.
Not applicable.
Not applicable.
Not applicable.
Requester logs in with purchasing responsibility and creates a purchase requisition with Goods line type for an inventory item. Buyer creates standard purchase order from requisition using auto create process in buyer work center. Buyer cancels the standard purchase order along with backing requisition.
None.
Not applicable.
Not applicable.
Not applicable.
Buyer logs in with purchasing responsibility and creates a standard purchase order with Goods line type for an inventory item in forms. Once the document is approved, buyer copies the same document to create another standard purchase order.
None.
Not applicable.
Not applicable.
Not applicable.
Buyer logs in with purchasing responsibility and creates a standard purchase order with Goods line type for an inventory item in Buyer Work Center. Once the document is approved, buyer duplicates to create another standard purchase order in Buyer Work Center.
None.
Not applicable.
Not applicable.
Not applicable.
Requester logs in with purchasing responsibility and creates a purchase requisition with Goods line type for an inventory item in forms and specify the ship to location (Costa Mesa, CA) for which the tax is enabled and verifies that the tax is applied to the requisition. Buyer creates standard purchase order from requisition using auto create process in forms and verifies that the tax is applied to the standard purchase order.
None.
Not applicable.
Not applicable.
Oracle Receivables allows you to streamline invoicing, receipt, and customer deduction processing while improving cash flow, optimizing customer relationships, and providing strategic information. As a sub ledger, Oracle Receivables provides the flexibility to meet the demands of a global market with strong financial controls to assist in instilling corporate and fiscal discipline.
This chapter describes the following test flows in Oracle Receivables:
Create Receipt and Take Earned Discount
Create Receipt and Clear using Cash Management
Create Standard Receipt Reversal
Create Invoice with 'In Advance' Accounting Rule
Create Debit Memo Receipt Reversal
Create Invoice with Split Payment Term and Apply Credit Memo
Create Adjustment - within Approval Limits
Create Invoice with Document Number when Saved
Create Deposit and Attach to Invoice
None.
Table 12-1 Profile Options for Oracle Receivables
Profile Name | Profile Value |
---|---|
POS: SM: Enable Supplier Profile Management Extension |
No |
POS: SM: Supplier Data Hub Configuration |
None |
Not applicable.
Table 12-2 Setup Data for Oracle Receivables
Window Name | Field Name | Field Value |
---|---|---|
AutoAccounting |
Type: Factored Bills Receivable |
01 000 1245 0000 000 |
Type: Bills Receivable |
01 000 1220 0000 000 | |
Type: Remitted Bills Receivable |
01 000 1245 0000 000 | |
Type: Unpaid Bills Receivable |
01 000 1220 0000 000 | |
Type: Freight |
01 430 7220 0000 000 | |
Type: Receivable |
01 000 1210 0000 000 | |
Type: Revenue |
01 000 1150 0000 000 | |
Type: AutoInvoice Clearing |
01 000 1222 0000 000 | |
Type: Tax |
01 000 5110 0000 000 | |
Type: Unbilled Receivable |
01 000 1232 0000 000 | |
Type: Unearned Revenue |
01 000 2550 0000 000 |
Creates payment term without discount, creates invoice and receipt, and takes earned discount. Verifies invoice balance and receipt accounting.
None.
Not applicable.
Not applicable.
Not applicable.
Creates a receipt class method by matching, creates invoices, creates receipts, verifies receipt accounting, clears receipt through cash management, and verifies receipt accounting.
None.
Not applicable.
Not applicable.
Not applicable.
Creates receipt, reverses receipt, and verifies invoice balance and receipt accounting.
None.
Not applicable.
Not applicable.
Not applicable.
Creates accounting rule, raises an invoice on the customer with in-advance invoicing rule. Runs Revenue Recognition program and verifies accounting.
None.
Not applicable.
Not applicable.
Not applicable.
Creates transaction type, creates invoice, creates receipt and reverse receipt, and verifies receipt accounting, invoice balance and debit memo balance.
None.
Not applicable.
Not applicable.
Not applicable.
Creates invoice with split payment term, verifies invoice balance, and applies credit memo to invoice.
None.
Not applicable.
Not applicable.
Not applicable.
Creates receivable activity for adjustment, creates invoice and adjusts it, and verifies the invoice and adjustment accounting.
None.
Not applicable.
Not applicable.
Not applicable.
Creates transaction type, sets document sequence, defines category, creates invoice, and verifies the generated document.
None.
Not applicable.
Not applicable.
Not applicable.
Creates transaction type for deposit, creates deposit, raises an invoice on the customer, and applies the deposit. Verifies deposit balance, creates accounting, creates receipt and applies to deposit. Verifies deposit balance and receipt accounting.
None.
Not applicable.
Not applicable.
Not applicable.
Oracle Flow Manufacturing is a comprehensive manufacturing software solution that supports demand driven flow and lean manufacturing techniques designed to reduce product cycle times, minimize inventories, simplify production, and improve product quality. These techniques provide manufacturing operations with the ability to quickly respond to changing customer needs in an E-Business environment. Oracle Flow Manufacturing is part of the Oracle E-Business Suite, an integrated set of applications that are engineered to work together.
This chapter describes the following test flows in Oracle Flow Manufacturing:
Define Setup for Flow Routing
Flow Schedule Completion in Workstation
None.
Not applicable.
Table 29-1 Predefined Data for Oracle Flow Manufacturing
OA Page Name | Field Name | Field Value |
---|---|---|
User |
User name /password |
MFG/welcome |
Responsibility |
Responsibility Name |
Manufacturing and Distribution Manager |
Table 29-2 Setup Data for Oracle Flow Manufacturing
OA Page Name | Field Name | Field Value | Comments |
---|---|---|---|
Organization |
Organization Name |
V1 |
V1 master organization |
Organization Name |
S1 |
S1 child organization |
Defines new flow line, standard line operations, standard processes and flow events. Creates new flow assembly and defines the flow routing.
None.
Not applicable.
Not applicable.
Creates flow schedule for lot and serial controlled assembly in line schedule workbench, opens and updates workstation parameters Schedule Selection Mode in HTML flow workstation. Performs flow schedule and completes with back flush items.
Finished assembly is lot and serial controlled.
BOM, flow routing.
All dependent components have on-hand inventory.
Flow routing for the assembly with three standard operations or events and processes.
Network routing for the assembly and line is defined in graphical line work designer.
Flow schedule defined for the line and assembly combination on the given date.
Not applicable.
Table 29-4 Predefined Data for Flow Schedule Completion in Workstation Flow
Window Name | Field Name | Field Value |
---|---|---|
Line Scheduling Work bench |
Scheduling Rule |
NEW RULE |
WIP Parameters |
Class |
Flow |
Define Schedule Rules |
Leveling |
Mixed Model |
Table 29-5 Setup Data for Flow Schedule Completion in Workstation Flow
Window Name | Field Name | Field Value | Comments |
---|---|---|---|
Line Scheduling Work bench |
Assembly |
CHA_FLM_LSR_ASSY | |
Bill of Material |
Components |
CHA_LOT_SR_CMP1 |
Lot and serial controlled component with supply type Operation Pull |
Components |
CHA_SR1 |
Serial controlled component with supply type Operation Pull | |
Components |
CHA_CMP1 |
Plain component with supply type Assembly Pull | |
Flow Routing |
Standard Operation |
op10 |
Attach standard operations to the event |
Standard Operation |
Op20 |
Attach standard operations to the event | |
Standard Operation |
Op30 |
Attach standard operations to the event | |
Standard Events |
e1 |
Attach standard events to the resource | |
Standard Events |
e2 |
Attach standard events to the resource | |
Standard Events |
e3 |
Attach standard events to the resource | |
Standard Processes |
pr10 |
Attach standard processes to the events | |
Standard Processes |
Pr20 |
Attach standard processes to the events | |
Standard Processes |
Pr30 |
Attach standard processes to the events |
Oracle Engineering enables you to control new item revisions and bill of material changes. Its prototype also enables you to move toward concurrent engineering by integrating engineering prototype data with manufacturing data.
This chapter describes the following test flows in Oracle Engineering:
Create, Copy ENG to MFG, Propagate and Implement Engineering Change Order.
Create Engineering Change Order (ECO) and Implement.
None.
Not applicable.
Table 27-1 Predefined Data for Oracle Engineering
Window Name | Field Name | Field Value |
---|---|---|
Responsibility |
Responsibility Name |
Manufacturing and Distribution Manager |
Organization |
Organization |
V1, M1 |
Engineering Bills Of Material |
Display |
Future and Current |
Action |
Add | |
Action |
Disable | |
Component Changes |
Action |
Add |
Engineering Bills Of Material |
Supply Type |
Push |
Table 27-2 Setup Data for Oracle Engineering
Window Name | Field Name | Field Value |
---|---|---|
User |
User Name / Password |
Plmmgr / welcome |
Item Template |
Template |
Finished Goods |
Creates an engineering BOM; transfers item bill from engineering to manufacturing, propagates engineering change order to child organization and implements engineering change order in child organization.
None.
Table 27-3 Profile Options for Create, Copy ENG to MFG, Propagate and Implement Engineering Change Order Flow
Profile Name | Profile Value | Level |
---|---|---|
Enable Security Group |
No |
Site |
Defines engineering change order approval list, creates engineering change order, transfers and copies engineering items and bills to manufacturing, implements engineering change order and generates engineering change order detail report.
None.
Not applicable.
Table 27-6 Predefined Data for Create Engineering Change Order and Implement Flow
Window Name | Field Name | Field Value |
---|---|---|
Responsibility |
Responsibility Name |
Manufacturing and Distribution Manager |
Table 27-7 Setup Data for Create Engineering Change Order and Implement Flow
Window Name | Field Name | Field Value |
---|---|---|
User |
User Name / Password |
plmmgr / welcome |
Item Template |
Template |
Purchased Item |
Approval Lists |
Lists |
JEAL |
Employee |
Name |
Williams, Steve, Smith, Mr. Jonathan |
Master Item |
Item |
EBS_COMP_10 |
Item |
EBS_COMP_11 | |
Item |
EBS_COMP_12 | |
Item |
EBS_COMP_11 |
This Part of the Oracle Flow Builder Starter Pack for E-Business Suite Release 12.2 provides information about the flows used with Procurement applications.
This Part contains the following chapter:
Oracle Project Resource Management helps to manage the capacity and deployment of people and assets for project work by finding and deploying the most qualified resources to the projects. Oracle Project Resource Management centralizes information to empower project, resource, and staffing managers to better utilize their single most critical resource: people.
This chapter describes the following test flows in Oracle Project Resource Management:
Project Requirement Creation to Approval
None.
Not applicable.
Not applicable.
Not applicable.
Project requirement creation to approval covers the creation of a project from a project template. It creates a requirement for the project, assigns a person to the requirement to convert into an assignment and approves the assignment of the project.
Users with responsibilities as:
Table 20-1 Users Prerequisites for Project Requirement Creation to Approval Flow
User | Responsibility |
---|---|
00amason |
Project Super User |
00bclark |
Staffing Manager |
00Dgeorge |
Resource Manger |
Job CON600.Consultant in the job group Vision Corporation.
Employees with roles as:
Table 20-2 Employees Prerequisites for Project Requirement Creation to Approval Flow
Employee name | Role |
---|---|
00Langer, Daniel |
Employee for assigning to a requirement |
Clark, Ms.Boris |
Staffing owner |
George, Mr.David |
Approver for requirement |
00Mason, Abraham |
Project manager |
PRC: Maintain Project Resources run to access the employees in Projects.
Open Accounting and GL periods for the current year.
Table 20-3 Profile Options for Project Requirement Creation to Approval Flow
Profile Name | Profile Value | Level |
---|---|---|
PA: Licensed to use Project Resource Management |
Yes |
Site |
PA: Availability Duration |
0 |
Site |
PA: Availability or Over commitment Calculation Period |
Daily |
Site |
MO: Operating Unit |
Vision Services |
Site |
MO: Security Profile |
Vision Corporation |
Site |
HR: Business Group |
Vision Corporation |
Site |
Not applicable.
Table 20-4 Setup Data for Project Requirement Creation to Approval Flow
Page Name | Field Name | Field Value | Comments |
---|---|---|---|
Project |
Project Template |
Cost Plus |
Project type Contract is used in the template |
Organization |
PJR Organization1 |
Organization Type- Division Classification-HR Organization, Project Expenditure or Event Organization and Project Task Owning Organization | |
Project or Customer and contacts |
Customer Name |
Hilman and Associates |
Customer must be created in Accounts Receivables |
Role |
Name |
DBA |
Job CON600.Consultant should be attached to the role |
Calendar |
Name |
PJR Calendar 1 |
Calendar exceptions [Holidays] defined and Shifts assigned to it [ Shift: 8x5 ] the calendar periods should fall in the project start and end dates |
Oracle Inventory Management is part of the supply chain management solution and integrates seamlessly with other supply chain management applications, including Oracle Warehouse Management, Oracle Mobile Supply Chain Applications, Oracle Order Management, Oracle Purchasing, Oracle Discrete Manufacturing, Oracle Process Manufacturing, and Oracle Cost Management.
Oracle Inventory Management allows organizations to consolidate their disparate inventory tracking and control systems into a single, global inventory management solution for material in every stage of the product or production lifecycle as well as for different business types.
This chapter describes the following test flows in Oracle Inventory Management:
Inventory Miscellaneous Receipt
Inventory Miscellaneous Issue
Move Order Requisition of Type Move Order Issue with Automatic Allocation
Direct Transfer between Two Inventory Organizations
Inventory Intransit Shipment with Direct Receipt between Two Inventory Organizations
Inventory Sub-inventory Transfer
Perform Cycle Counting
Perform Physical Inventory
Kanban Replenishment
Min- Max Planning
Replenishment Count
Standard PO Partial Receipt with Immediate Mode
Positive Correction Transactions
Return to Vendor from Inventory Transactions
Material Issue through Sales Order
RMA Direct Receipt
Organization (M1) with Non WMS and Non Process Manufacturing options enabled.
Open cost periods for corresponding transaction dates.
Table 31-1 Profile Options for Oracle Inventory Management
Profile Name | Profile Value | Level |
---|---|---|
TP:INV Transaction processing mode |
On-line processing |
Site |
RCV: Processing Mode |
Immediate |
Site |
Table 31-2 Predefined Data for Oracle Inventory Management
Window Name | Field Name | Field Value |
---|---|---|
Organization Parameters |
Organization Code |
M1 |
Templates |
Template |
Purchased Item template |
Table 31-3 Setup Data for Oracle Inventory Management
Window Name | Field Name | Field Value |
---|---|---|
Inventory Accounting Periods |
Period or Status |
'Open' (Current month period should be opened) |
Miscellaneous receipts are used to receive material from general accounts ledger into the current organization. This feature can be used to perform receipts of items that were acquired by means other than a purchase order.
Transactable inventory item.
If the item is locator enabled, sub inventory used is also locator enabled.
Not applicable.
Not applicable.
Not applicable.
Miscellaneous Issue is used to issue material from general accounts ledger in the current organization. This feature can be used to issue items to individuals, departments, projects or to issue damaged goods to expense accounts such as scrap.
Transactable inventory item.
Not applicable.
Not applicable.
Not applicable.
Move order issue is used to issue material from a stock location in the organization. This transaction will check for sufficient material at the stock location, and on approval, will deliver the material to the destination location specified by the user. The material is automatically allocated for transfer from the source location.
Reservable stock for the material.
Not applicable.
Not applicable.
Not applicable.
Direct transfer is used to transfer material from one inventory organization to another. In this type of transfer the receiving organization is not required to perform any operation to receive the material. The material is transferred from the source to the destination organization as soon as the transaction is saved.
Material is available at the source organization.
Not applicable.
Not applicable.
Not applicable.
Inventory intransit shipment is used to transfer material from one inventory organization to another. For this type of transfer, the user creates a shipment from the source organization and saves it. The receiving organization is expected to create a receipt to receive the material. The creation of the receipt concludes the transfer.
Material is available at the source organization.
Not applicable.
Not applicable.
Not applicable.
Sub-inventory transfer is used to transfer material within the current organization between sub-inventories or between two locators within a sub-inventory. This transfer can be performed from an asset to expense sub-inventory and from a tracked to a non tracked sub-inventory.
Material is available at the source sub-inventory.
Not applicable.
Not applicable.
Not applicable.
Cycle counting is used to check the inventory in a specific location that can be restricted to a particular sub-inventory. Cycle counting is performed in a specific location that can be restricted to a particular sub inventory.
None.
Not applicable.
Not applicable.
Not applicable.
Physical inventory is used to check and update the system with the actual on hand inventory. Snapshots are taken of the system inventory values and cross checked with the actual on hand quantity. Reconciliation is performed based on the difference.
During this activity the system will not prevent the user from performing inventory transactions.
None.
Not applicable.
Not applicable.
Not applicable.
Kanban replenishment is a pull based replenishment to be used on items with a fairly constant demand and high production volume. A Kanban item is defined along with the pull sequence to indicate from where the replenishment will take place. A color card can be used to serve as a trigger to start the replenishment. It is a means of supporting pull-based replenishment in manufacturing systems, which can be replenished from an external supplier or an internal organization.
None.
Not applicable.
Not applicable.
Not applicable.
Min-max planning maintains inventory levels, or sub-inventory level, for all of the items or selected items. With min-max planning, minimum and maximum inventory levels can be specified for the items. When the inventory level, or sub-inventory level, for an item (on-hand quantities plus quantities on order) drops below the minimum, Oracle Inventory suggests a new purchase requisition, internal requisition, move order, or job to bring the balance back up to the maximum.
None.
Not applicable.
Not applicable.
Not applicable.
Replenishment count is used to plan and create requisition orders for items that need to be replenished. Verify the replenishment count when the order quantity and the maximum ordered quantity are defined for the item.
Replenishment count can only be used at the sub-inventory level.
Item-sub-inventory relationship.
Not applicable.
Not applicable.
Not applicable.
A standard purchase order is used to receive material from a supplier to the inventory organization. The user creates a purchase order and sends it for approval. After approval the material is shipped to the organization. The receiving organization creates a receipt for the material. During receipt the receiver can choose to receive a partial quantity.
Receiving sub-inventory for receipt of material.
Not applicable.
Not applicable.
Not applicable.
Positive correction transactions are used for purchase orders. This feature permits the user to increase the quantity on a receipt for a previously received order.
Purchase order receipt.
Not applicable.
Not applicable.
Not applicable.
Return to vendor feature is used when the receiver wants to return the goods previously received through a purchase order. After receipt of a purchase order, if any goods are to be returned, a return to vendor transaction is created and the goods are sent back to the supplier of the purchase order.
Purchase order receipt.
Not applicable.
Not applicable.
Not applicable.
Sales order is used to ship goods to the customer. During the outbound flow, the user creates a sales order. Based on the availability of the goods, the sales order is booked and released. Material is allocated against this sales order and then shipped out to the customer.
Reservable and transactable quantity in the inventory location.
Not applicable.
Not applicable.
Not applicable.
Return material authorization (RMA) is used when the customer, to whom goods have been previously sold, wants to return the goods. These are the goods for which a sales order was previously created. When the goods are returned at the receiving dock, an RMA is created. A receipt is made against this RMA to acknowledge the returned goods.
Sales Order that was previously shipped.
Not applicable.
Not applicable.
Not applicable.
Flow Builder Starter Pack Reference Guide for E-Business Suite Release 12.2
Release 12.4.0.1
E50740-01
March 2014
Oracle Functional Testing Flow Builder Starter Pack Reference Guide for E-Business Suite Release 12.2 Release 12.4.0.1
E50740-01
Copyright Š 2014,  Oracle and/or its affiliates. All rights reserved.
Primary Author: Â Prasanti Madireddi
Contributing Author: Â Rick Santos
Contributor:
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
Oracle Order Management is an order-to-cash solution that provides the capabilities for customers, partners and employees to select the right products and services, negotiate the best prices and ensure timely order fulfillment. Oracle Order Management drives the order fulfillment process of any business. The open, workflow based architecture supports non-customized, tailored and automated fulfillment processes. It captures multi-channel demand from sources including EDI, XML, Telesales and web storefronts. As part of a complete order to cash solution, it enables global order promising and is integrated with Transportation Management.
This chapter describes the following test flows in Oracle Order Management:
Create Order from Quote for a Standard Line
Generate Invoice for PTO Model, ATO Model and Standard Line
Verify Scheduling Dates for Sales Order by Assigning to Ship Sets
Verify Split Configuration Concurrent Program for PTO Model Line, ATO Model Line and Kit
Verify Authorization of a Sales Order with Credit Card and Cash
Create and Verify Tax on Sales Order
Verify Intercompany Invoicing for Sales Order
Fulfillment of a Bill Only Line With Standard Item
Multiple Processing Constraints Validations for a Sales Order Header and Line
Verify Audit History for a Sales Order Header and Line
Create Processing Constraints for Customer PO
User is logged in with Order Management Super User responsibility.
Oracle Quoting offers limited capability to create quotes and progress it through the negotiation phase and finally creates sales order, thus acting as a single point of entry into Oracle Order Management.
The Create Order from Quote for a Standard Item flow creates an order from quote for a standard line, with approvals and converts the same to a sales order.
Transaction type Mixed of workflow type Negotiation Flow-Generic.
Transaction type Mixed of workflow type Negotiation Flow-Generic, with Use Approvals Management Engine check box deselected.
A customer or party, with address and account number.
Not applicable.
Not applicable.
Table 36-1 Setup Data for Create Order from Quote for a Standard Item Flow
Window Name | Field Name | Field Value |
---|---|---|
Quote |
Customer Number |
1005 (Pick a Party of type Organization) |
Ordered Item |
AS54888 (Pick a standard item of finished goods template) | |
Order Type |
Mixed (Pick an Order Type) | |
Price List |
Corporate (Pick a Price List) |
Invoice processing in Oracle Order Management is the process by which data from orders and returns is interfaced to Oracle Receivables for the creation of invoices and credit memos, to recognize revenue and manage sales credits. This flow verifies the generation of invoice for the PTO Model, ATO Model and Standard Line.
A standard item of type 'Finished Good' template.
An item of PTO model type with optional classes and optional items.
An item of ATO model type with optional classes and optional items.
A customer or party, with address and account number.
A non-WMS warehouse.
Not applicable.
Not applicable.
Table 36-2 Setup Data for Generate Invoice for PTO Model, ATO Model and Standard Line Flow
Window Name | Field Name | Field Value |
---|---|---|
Sales Order |
Customer Number |
1005 (Pick a customer number) |
Order Type |
Mixed (Pick an order type) | |
Warehouse |
M1(Pick a non-WMS organization) | |
Ordered Item |
Vision-SMC-PTO-Model -Vision-PTO-Non-ATP-Op-Item -Vision-PTO-ATP-Op-Item (Pick a PTO model with optional classes and items) | |
Ordered Item |
Vision-ATO-Model -Vision-ATO-Op-Item (Pick an ATO model with optional classes and items) | |
Ordered Item |
AS54888(Pick a finished good) |
Creates a sales order and verifies the scheduling dates. This flow assigns the new ship set, adds to the existing hip set and verifies whether lines are getting scheduled or not.
A customer or party, with address and account number.
A non-WMS warehouse.
Two standard items with finished good template.
A Hold Source for an item.
PTO Model with PTO-Model template.
ATO Model with ATO-Model template.
Kit Model with Kit-Model template.
Not applicable.
Not applicable.
Table 36-3 Setup Data for Verify Scheduling Dates for Sales Order by Assigning to Ship Sets Flow
Window Name | Field Name | Field Value |
---|---|---|
System Parameters |
Schedule Lines on Hold |
Yes or No |
OM: Auto Schedule Sets |
Yes or No | |
OM: Auto Schedule |
Yes or No | |
Schedule Lines on Hold |
Yes or No | |
Sales Order |
Customer Number |
1005 (Pick A customer Number) |
Warehouse |
V1 (Select a non WMS warehouse ) | |
Ordered Item |
AS54888 (Select a product) | |
Ordered Item |
AS54999 (Select a product) | |
Ordered Item |
(Select a PTO Model product) | |
Ordered Item |
(Select an ATO Model product) | |
Ordered Item |
(Select a KIT Model product) | |
Ship Set |
Ship Set |
Any value for a ship set |
Users can split lines in the background using the concurrent request Split Configuration in the Sales Orders window. This applies to ATO Models, PTO configurations and Kits. The Defer Split check box in the Split Line window enables splitting configuration lines in the background and continuing with other actions on the sales order. When a user selects the Defer Split box and clicks Split, the Split Configuration concurrent program splits the lines as a background process.
This test flow verifies the split line functionality using the Split Configuration concurrent program for PTO Model line, ATO Model Line and Kit.
An item of PTO model type with optional classes and optional items.
An item of ATO model type with optional classes and optional items.
An item of type Kit.
A customer or party, with address and account number.
A non WMS warehouse.
Not applicable.
Not applicable.
Table 36-4 Setup Data for Verify Split Configuration Concurrent Program for PTO Model Line, ATO Model Line and Kit Flow
Window Name | Field Name | Field Value |
---|---|---|
Sales Order |
Customer Number |
1006 (Pick A customer number) |
Order Type |
Mixed (Pick an Order Type) | |
Warehouse |
M1(Pick a non-WMS organization) | |
Ordered Item |
Vision-PTO-Model (Pick a valid PTO model with optional classes) | |
Ordered Item |
Vision-ATO-Model (Pick a valid ATO model with optional classes) | |
Ordered Item |
Vision-SMC-Kit (Pick an item of type Kit template) |
This flow tests the authorization of a sales order with credit card and cash. It also verifies multiple payments for a standard item.
Credit check rule.
Credit option for the payment terms in the sales order is selected.
A customer or party, with address and account number.
A transaction type with the Credit Check rule set at ordering level.
A non WMS warehouse.
Not applicable.
Not applicable.
Table 36-5 Setup Data for Verify Authorization of a Sales Order With Credit Card and Cash Flow
Window Name | Field Name | Field Value |
---|---|---|
Sales Order |
Transaction Type |
Mixed (Pick a Transaction Type) |
Rule |
CC-Rule1 | |
Customer Number |
1005(Pick a Party of type Organization) | |
Warehouse |
V1 (Select a valid non WMS warehouse ) | |
Ordered Item |
AS54888 (Select a product) | |
Ordered Item |
AS54999 (Select a product ) | |
Name |
N30 (Pick a Payment Term) |
This test flow verifies the tax applicability for a customer who comes under the United States jurisdiction. A tax rate is set up using Tax Manager responsibility with tax rate as 10% with United Status jurisdiction, and tax calculation is verified when a sales order is created for the customer falling under that tax jurisdiction.
A new tax rate for a transaction:
New tax.
New tax status.
New tax rate with 10%.
New tax jurisdiction with geography as NY, United States.
A customer or party, with address and account number, with bill to site under New York location.
A tax code.
Not applicable.
Table 36-6 Predefined Data for Create and Verify Tax on Sales Order Flow
Window Name | Field Name | Field Value |
---|---|---|
Sales Order |
Payment Type |
Cash |
Table 36-7 Setup Data for Create and Verify Tax on Sales Order Flow
Window Name | Field Name | Field Value |
---|---|---|
Sales Order |
Customer Number |
1001 (Pick a Party of Type Organization) |
Warehouse |
M1 (Pick a non-WMS organization) | |
Order Type |
Mixed (Pick an Order Type) | |
Price List |
Corporate (Pick a Price List) | |
Ordered Item |
AS54888 (Pick a finished good) | |
Tax Code |
VISIONUSSALESTAX (Select a Tax Code) |
When a customer processes and invoices an order, the selling organization records entries to Accounts Receivable for revenue, tax and freight. The shipping warehouse records entries to the inventory asset account and cost of goods sold (COGS) account. When the above scenario involves a selling organization in one operating unit and a shipping organization in another operating unit, additional accounting takes place.
The shipping organization must bill the selling organization at the transfer price and the selling organization must make the corresponding payment. The intercompany accounts receivable invoice is the transaction the system uses, to record the intercompany receivable accounting for the shipping organization. It debits the intercompany accounts receivable at transfer price, charges tax and freight cost, and credits the intercompany revenue.
The intercompany Accounts Payable invoice is the transaction the system uses to record the payable accounting for the selling organization. The system debits the intercompany COGS and freight, and credits the intercompany payable account.
This flow verifies the inter-company invoicing as follows:
Places an order with the selling operating unit.
The system ships the order to the customer from a shipping warehouse associated with an operating unit that differs from the selling operating unit.
The shipping operating unit issues an intercompany receivable invoice to the selling operating unitdZĽ at the transfer price.
The selling operating unit issues an intercompany invoice payable to the shipping operating unit.
If the customer is external, then the selling operating unit sends a separate invoice to the customer.
Shipping networks between the selling and shipping organizations.
Intercompany transaction flows between the selling and shipping operating units.
An internal location for the selling organization.
An internal customer with an internal location to the customer's ship-to site attached.
Price lists for selling and shipping OU, and the internally used price lists attached to the internal customer's bill-to site.
Tax structures in Oracle Payables and Oracle Receivables.
Oracle Receivables system options are defined.
Account Generator for the COGS accounts is set up.
Table 36-8 Profile Options for Verify Intercompany Invoicing for Sales Order Flow
Profile Name | Profile Value |
---|---|
AR: Use Parallel Hints |
No |
Not applicable.
Table 36-9 Setup Data for Verify Intercompany Invoicing for Sales Order Flow
Window Name | Field Name | Field Value |
---|---|---|
Requisitions |
Item |
AS54888 (Pick a finished good) |
Organization |
M1 Seattle Manufacturing (Pick a non-WMS organization) | |
Organization (Source) |
D1 Singapore Distribution Center (Pick a non-WMS organization) |
This process refers to the fulfillment of a line, the line type being Bill Only, with standard item and Generic - Bill only with Inventory Interface workflow.
A standard item with finished good template.
A transaction type with line type as Bill Only and process name as Line Flow - Generic, Bill only with Inventory Interface.
A customer or party.
Not applicable.
Not applicable.
Table 36-10 Setup Data for Fulfillment of a Bill Only Line with Standard Item Flow
Window Name | Field Name | Field Value |
---|---|---|
Sales Order |
Order Type |
Mixed (Pick an Order Type) |
Customer Number |
1006 (Pick a Party of Type Organization) | |
Warehouse |
V1 (A non WMS Warehouse can be selected) | |
Ordered Item |
AS54888 (A product can be selected) | |
Payment Terms |
N30 (A Payment Term value can be selected) |
This test flow verifies multiple processing constraints validations for a sales order header and line for change in payment terms, customer purchase order and warehouse.
Processing constraints for the warehouse, customer PO and payment terms attributes are created for both header and line.
A non WMS warehouse.
A valid customer or party, with address and account number.
Not applicable.
Not applicable.
Table 36-11 Setup Data for Multiple Processing Constraints Validations for a Sales Order Header and Line Flow
Window Name | Field Name | Field Value |
---|---|---|
System Parameters |
Audit Trail |
Enable when Order is Entered |
Sales Order |
Order Type |
Mixed (Pick an Order Type) |
Payment Terms |
N30 (Pick a Payment Term) | |
Customer Number |
1006 (Pick a Party of type Organization) | |
Warehouse |
M1 (Pick a Non-WMS Warehouse) | |
Ordered Item |
AS54888 (Pick a product) | |
Processing Constraints (Application :Order Management) (Entity: Order Header and Order Line) |
Operation Group Scope Validation Entity Record Set Validation Template User Message |
Update 101 Any Order Header Order Booked Booked |
User Action |
Require Reason and Require History Generate Version and Require Reason Not Allowed | |
Attribute |
Payment Term Warehouse Customer PO |
This flow verifies the audit history recorded for a sales order header and line, for change in payment terms.
Processing constraints for the attribute payment terms for both header and line.
A non WMS warehouse.
A customer or party, with address and account number.
Not applicable.
Not applicable.
Table 36-12 Setup Data for Verify Audit History for a Sales Order Header and Line Flow
Window Name | Field Name | Field Value |
---|---|---|
System Parameters |
Audit Trail |
Enable when order is entered |
Sales Order |
Customer Number |
1006 (Pick a party of type Organization) |
Warehouse |
V1 (Pick a non WMS warehouse ) | |
Ordered Item |
AS54888 (Pick a product) | |
Payment Terms |
N 30 (Pick a payment term) | |
Processing Constraints (Application :Order Management) (Entity: Order Header) |
Operation Attribute User Action Group Scope Validation Entity Record Set Validation Template User Message |
Update Payment Term Require Reason and Require History 101 Any Order Header Order Booked Booked |
Processing Constraints (Application :Order Management) (Entity: Order Line) |
Operation Attribute User Action Group Scope Validation Entity Record Set Validation Template User Message |
Update Payment Term Require Reason and Require History 101 Any Order Line Line Booked Booked |
The processing constraints for a customer PO attribute are checked for the processing constraints with user action as Versioning and Not Allowed. User can create the processing constraints for Not Allowed user action for customer PO and verify the same in the sales order. Also, the versions of a sales order are generated whenever the customer PO is updated.
A customer or party.
A non WMS warehouse.
Not applicable.
Oracle Quality is a flexible enterprise-wide quality management system that lets you collect, distribute and analyze critical quality data throughout your supply chain. Oracle Quality is part of the Oracle E-Business Suite, and is tightly integrated with Oracle Work In Process, Oracle Flow Manufacturing, Oracle Shop Floor Management, Oracle MES for Discrete Manufacturing, Oracle Purchasing, Oracle Internet Supplier Portal, Oracle Mobile Supply Chain, Oracle Warehouse Management System, Oracle Enterprise Asset Management, Oracle Depot Repair, and Oracle Service, enabling you to collect quality data at source.
This chapter describes the following test flows in Oracle Quality:
Create Quality Setups and Capture Quality Results
Purchase Order Inspection with Quality
None.
Not applicable.
Not applicable.
Not applicable.
Creates collection element and collection plan. Enters, updates, and views quality results and generates reports.
None.
Not applicable.
Not applicable.
Table 38-1 Setup Data for Create Quality Setups and Capture Quality Results Flow
Window Name | Field Name | Field Value | Comments |
---|---|---|---|
User |
User name /password |
MFG/welcome | |
Master Item |
Item |
G1000 |
Plain item |
Collection Element |
Element Name |
Item |
Mandatory, Enabled, Displayed |
Element Name |
RP_NUM3 |
Enabled, Displayed | |
Element Name |
RP_NUM4 |
Enabled, Displayed | |
Element Name |
Comments |
Mandatory, Enabled, Displayed | |
Element Name |
Result |
Enabled, Displayed | |
Collection plan template |
Template Name |
RP_CP_SPEC |
Contains following element: Item, RP_NUM3, RP_NUM4 |
Creates, receives, and inspects purchase order and moves it to sub-inventory.
None.
Table 38-2 Profile Options for Purchase Order Inspection with Quality Flow
Profile Name | Default Value or User value | Profile Value |
---|---|---|
QA:PO inspection |
Default Value |
Oracle Quality |
ICX: Date format mask |
31-DEC-1999 |
Not applicable.
Table 38-3 Window Setup Data for Purchase Order Inspection with Quality Flow
Window Name | Field Name | Field Value | Comments |
---|---|---|---|
Organization |
Organization Name |
V1 - Master Organization | |
Organization Name |
M1 - Child Organization | ||
Master Item |
Item Name |
MS-PUR2 |
Inventory item, Stackable, Transact able, Reserve able Purchased, Purchasable, List price:10 |
Location |
Location |
123 | |
Collection plan |
Collection plan |
PO INSPECTION PLAN |
Mandatory for receiving transaction. Trigger: Item is MS-PUR2 Mandatory for inspection transaction. Trigger: Item is MS-PUR2 Create collection plan with the following collection elements. Item, Inspection Result (prompt: Inspect Result and it is mandatory), Quantity (mandatory) UOM Name (Prompt: UOM), PO Quality Code (Prompt: Quality Code), Inspection Reason Code (Prompt: Inspect Reason), Inspection Supplier Lot Number (Prompt: Sup Lot Number), Transaction Date (Prompt: Transact Date and mandatory), Comments. |
Sub inventory |
Sub inventories |
FGI |
Qty Tracked, Asset, Locator Control: Item level control |