This chapter covers the following topics:
Processing an Order requires integration with many other business areas. Most integration points with other Oracle products are implemented via PL/SQL-based APIs. The following summarizes the integration points between OM and other products, organized by Product Family:
AK serves as a common runtime dictionary for both the Defaulting and Processing Constraints Frameworks. These modules use AK for object and attribute information. AK replaces the functionality provided by SO_OBJECTS and SO_ ATTRIBUTES in R11 Order Entry.
Additionally Order Management uses the following tables to extend the AK data model to support Usage functionality:
OE_AK_OBJECT_EXT
OE_AK_OBJ_ATTR_EXT
Order Management uses the following AOL features:
Document Sequences
AOL Document Sequences feature meets Order Numbering requirements. This lets you number Order and Returns using Manual, Automatic or Gapless sequences.
You can define Document Sequences using the AOL Define Document Sequences form. When you define an Order Transaction Type, the application automatically creates a Document Sequence Category of the same name. You can assign a pre-defined sequence to one or more Document Sequence Categories, using the AOL Sequence Assignments form. When an Order is created, Order Management calls AOL Document Sequence APIs to number the Order.
Attachments
Order Management drives off the AOL Attachment functionality enabling you to attach images and web pages as well as short or long text. It also offers multi-lingual document capability. Attachment definition and usage data is stored only in AOL.
Automatic Addition rule definitions are stored in Order Management (OE_ ATTACHMENT_RULES, OE_ATTACHMENT_RULE_ELEMENTS). In addition to the attributes (Customer, Ship-to, Invoice-to, Order Type, Item, PO #) that were previously available, you can now define rules based on the Order Category, Line Category and Line Type.
The Profile Option OM: Apply Automatic Attachments determines whether rule based attachments are automatically applied (without User intervention).
The eCommerce Gateway has the ability to load orders and order changes into Order Management via Order Import. Order Management pushes Order Acknowledgment and Change Order Acknowledgment data back to the eCommerce Gateway.
iSetup pushes setup information into the Order Management schema after an implementer has answered questions regarding their business setup.
Order Management uses Oracle Workflow to manage Order and Line processing. PL/SQL based Workflow is a natural replacement for Order Cycles functionality. It provides a Graphical User Interfaces for defining activities, notifications, flows and viewing flow status. There are no limits on the number of custom functions or notifications you can define.
Additionally, it provides the following features:
In-built flexibility: You can easily extend functions or flows using the Workflow Builder.
Support for notifications: Approval functionality is supported via Notification activities. You can easily define notifications via the Workflow builder and use them in flows. Notifications can be accessed via any electronic mail application or the Notifications web page.
Coordination between parent-child flows: This aids in synchronizing Header and Line flows. Thus you can have lines wait for the Order header to complete a certain header activity or have the Header wait for all lines to complete a certain line activity.
A built-in on-line/background mode with a user-definable threshold: This enables you to run certain activities such as Credit Checking off-line.
Every Order Header and Line entered into the system starts a workflow. Order Headers follow Header flows and Order Lines follow Line flows. The product comes seeded with several Order and Line flows. Every business function is workflow enabled and the product comes seeded with functional workflow sub-processes.
Order Headers are mapped to the OM Order Header workflow item type (OEOH). Order Lines are mapped to the OM Order Line workflow item type (OEOL). The Workflow Engine APIs are used to create, start and manage flows. The Order Type tied to an Order determines the Header flow it starts. The Order Type, Line Type, and Item type determines the Line flow a Line starts.
The FLOW_STATUS column on Order headers and Lines provides summary information about the flow. Its value changes as the Order or Line progresses in its respective flow. You can also use the Public query APIs (OE_HEADER_STATUS_ PUB, OE_LINE_STATUS_PUB) to get information regarding various functional statuses and when an Order or Line activity was completed.
The Workflow builder is available on the Windows (NT, 98 and 2000) platform. You can use this graphical tool to define flows. The Workflow monitor is a Java based tool that can be launched from the Sales Orders form. It lets you graphically monitor a workflow's progress as well and view its transaction history.
The XML Gateway has the ability to load orders and order changes into Order Management via Order Import. Order Management pushes Order Acknowledgment and Change Order Acknowledgment data back to the XML Gateway.
Order Management leverages many business objects belonging to Advance Pricing, including price lists, modifiers, and agreements. Order Management, through its Sales Agreement functionality, creates price lists and pushes them into the Advanced Pricing tables. Order Management calls the Pricing Engine to make pricing requests during the processing of orders, and receives pricing information back from Advanced Pricing.
Order Management integrates with Oracle Configurator to support ordering and validation of configurations. The Configurator window is a Java Applet that can be launched from the Sales Order form. Order Management communicates with Oracle Configurator through XML messaging. See: Oracle Configurator Developer User's Guide
iStore generates quote header and lines which are then sent to Order Management using the Order Capture API. RMAs are generated using Order Management's Process Orders API.
Oracle Release Management pushes orders, lines and Sales Agreement releases into Order Management via the Process Order API. Order changes arising from changes to schedules in Release Management are also communicated to Order Management via Process Order. Order Management sends order status information back to Release Management, so that its schedules can be kept in sync with the orders.
Order Management provides APIs to Shipping to view lines that are eligible for delivery planning, picking and shipping. The view OE_DELIVERY_LINES_V returns all open, booked, shippable lines that are not interfaced to Shipping. When an Order Line reaches the Ship Line workflow activity, Order Management calls Shipping APIs to indicate that a line is pick eligible and communicate changes to the line once it is interfaced to Shipping. When a delivery is ship-confirmed, Shipping calls OM APIs to communicate the event, triggering the line flow to move forward. If Freight Costs were input during ship confirmation, that information is communicated back to Order Management when the delivery line is interfaced back from Shipping.
Oracle Order Management/Shipping Execution, provides an XML-based adapter to integrate to International Trade Management (ITM) Applications. The Oracle International Trade Management Adapter serves as the interface point to third party international trade management partners. With this adapter, Oracle E-Business Suite applications can embed global trade functionality into core business transactions.Oracle Order Management has expanded the ITM features that are available when using Oracle Order Management and the Oracle ITM Adapter in conjunction with a third party ITM partner. Features include:
Export Compliance Workbench: Process screening failures without having to navigate to multiple forms
Export Compliance Screening Concurrent Program: Progress multiple lines that have failed earlier due to data errors
Export Compliance Screening Failure Report: Manage screening failures
Export Compliance Report to Government: Provide the US Government with a list of exported lines
Booked and fulfilled order lines from Order Management are pulled into the Applications Data Warehouse, where they become input to the various sales Business Intelligence reports.
Order lines from Order Management are pulled into the Daily Business Intelligence product to produce up-to-date performance metrics.
Order Management accepts Credit Card information when entered on orders. It integrates with Oracle Payment to validate this information and get Credit Card authorizations. This information is then interfaced to Receivables.
Order Management integrates with iReceivables through the Order Information Portal. This integration allows users of the Order Information Portal to view invoices and credits related to the order they are viewing.
Order Management accesses the AP Bank Accounts table to populate the Credit Card LOV when an order is being entered with a payment type of Credit Card. Additionally, if a new credit card number is entered and the authorization of that card through iPayment is successful, Order Management calls an AR API to create a new bank account record for the customer in the Bank Accounts table.
Order Management integrates with Oracle Receivables in the following function areas:
Invoice Interface: Order Management sends invoices and credit memos to Receivables via the Invoice Interface workflow activity. The seeded Invoice Interface - Line workflow sub-process populates the Receivables interface table. You run AutoInvoice to create invoices.
Order Management also supports Header level invoicing via the seeded Invoice Interface - Order.
Receipts: Order Management calls Receivables' Receipt API to create receipts for prepaid credit card orders. Order Management receives a payment-set id from AR when the receipt is created, and then passes that id back to AR in the autoinvoice tables at invoicing time so that the invoice can be matched to the receipt.
Tax: Order Management calls the Global Tax Engine APIs to default the Tax Code (ARP_
TAX.GET_DEFAULT_TAX_CODE) and to calculate estimated tax (ARP_PROCESS_TAX.SUMMARY) for the order Line. The estimated tax value is now stored on the line and re-calculated only when any of the attributes affecting tax change. Information about the tax value is also stored as Line Price Adjustments.
The Tax Engine looks at the view OE_TAX_LINES_SUMMARY_V to calculate the estimated tax value for an Order Line.
Credit Management: If the Credit Management product is installed, notifications are sent to it by Order Management when an order or line goes on credit hold, to initiate a credit review. If the credit review results in a decision to approve the order, a business event is posted which OM subscribes to and then releases the credit hold.
Order Management integrates with Oracle Trading Community Architecture to access customer setup information, including party data, account information, account sites, relationships and contacts. Many attributes of importance to Order Management, such as preferred warehouse, preferred order type, set preferences, price list and many others, are stored in the TCA data model at the account and account site level and are used by Order Management as defaulting sources.
In addition, Order Management, through the 'Add Customer' functionality, allows users to input new customer accounts, addresses and contacts. This data is pushed to the TCA schema, using TCA APIs. 'Add Customer' functions can also be performed through Order Management's Order Import program.
Order Management integrates with Oracle Training Administration to link classes and enrollments with orders for the purpose of billing. When classes or enrollments are marked as having been attended, the associated order lines are updated as fulfilled, and their line flows advance to the invoicing step.
Order Management integrates with Oracle Inventory Management through Managing Reservations. Order Management calls Inventory's reservation APIs to manage reservations. You can create reservations to on-hand quantities from the Sales Orders form. You can also go to Inventory's reservation form from the Sales Orders form and create a reservation to any level of inventory such as sub-inventory, locator, or lot if supply is available.
When supply is created for a ATO configuration (for a configuration item), it is reserved to a Work Order. This reservation gets transferred to on-hand when the work order is completed, thus reserving the Order line to on-hand. For every Order created, Order Management creates a record in MTL_SALES_ORDERS, an entity that Inventory uses to manage demand from various sources.
Reservation information is stored in MTL_RESERVATIONS. Reservation records for order Lines point to both MTL_SALES_ORDERS and OE_ORDER_LINES_ALL.
Order Management integrates with Oracle Bill of Material when models and kits are entered on sales orders. Order Management uses the Bill of Material defined for the model or kit or explode the model into its components, for the purpose of the user selecting options and for shipping purposes.
Order Management integrates with Oracle Product Lifecycle Management in the following areas:
Items: Order Management integrates with Oracle Product Lifecycle Management to access item setup information, including items, cross references and item relationships. Many attributes of importance to Order Management, such as preferred warehouse, processing flags, item type, price list, catchweight-enabled and many others, are stored in the item database and are used by Order Management as defaulting sources.
Customer-Item Cross reference: You can use Oracle PLM to set-up Customer Items and Customer Item Cross reference information. You can then place orders using those pre-defined customer item identifiers. Order Management calls the Inventory API INV_CUSTOMER_ITEM_GRP to derive the internal item based on the specified customer item, ship-to site and the warehouse on the Order Line. The Item Identifier Type on the Order Line indicates the Cross-reference Type that was used for placing the order. The Ordered Item tracks identifier that was used to place the order.
Related Items: Item Relationships set up in PLM are used in Order Management to display the 'Related Items' window on the Sales Order form, to give users visibility to, for example, upsell and cross-sell items, substitute items, item supercessions, and so on.
Advanced Item Search: Order Management integrates with PLM's advanced item catalog to enable parametric searches of the item catalog.
Order Management integrates with Oracle Purchasing in the following functional areas:
Return Receipts: Order Management uses the Oracle Purchasing Receipt functionality to handle Return receipts. When an item is received, Purchasing calls Order Management to indicate delivery and to get COGS information. When an item is accepted and delivered to Inventory, Purchasing calls Order Management (OE_RMA_RECEIVING) to indicate acceptance. Fulfillment of the Return line is driven off the acceptance event.
Purchasing looks at the view OE_PO_ENTER_RECEIPTS_VIEW to determine the Order Lines to expect Return receipts against. This view returns lines that are booked, receivable and are waiting at the Wait for Receiving block activity.
Internal Orders: Oracle Purchasing uses Order Import to create internal orders. Purchasing calls the Process Order API to communicate changes in the requisition to Order Management. Order Management calls a Purchasing API (PO_SUPPLY) to communicate changes in the internal order to Purchasing.
Drop-Ship Orders: Order Management integrates with Purchasing to fulfill drop-ship orders. It populates the PO requisitions interface table with information for order lines that need to be fulfilled via an external source. Purchasing calls Order Management APIs (OE_DROP_SHIP_GRP) to communicate information about the requisition, purchase order and receipts. Order Management provides a link to the Drop Ship information from the Additional Line and Additional Order Information windows of the Sales Order form.
Order Management uses Advanced Supply Chain Planning's Global Order Promising functionality to check the availability of ordered items and to schedule order lines. Scheduled Order Lines are viewed as demand by the Advanced Planning System.
To check availability or schedule an order line (scheduling checks availability and consumes supply if there is any available), Order Management calls an MRP API (MRP_ATP_PUB.CALL_ATP). MRP checks for item availability (or group availability if a group of lines is passed) and returns back the results. The API also sources the line (find a ship from location) when a ship from location is not specified. A source will only be returned if there are sourcing rules set up in MRP. To ascertain open demand Planning looks at the view MTL_DEMAND_OM_VIEW, based off OE_ORDER_LINES. This returns open (un-shipped) lines whose visible to MRP flag is set to Y. The visible to MRP flag is set to Y, when a line is scheduled.
Before booking, Advanced Supply Chain Planning also performs item substitution during scheduling for order lines, when the ordered item is not available at the sourcing location and a substitute is available for the total line amount.
Sourcing rules can be used in scheduling for ATO models to select a warehouse for an ATO model. You do not need to specify a warehouse for the ATO model. To supply the warehouse for an ATO model, there is interaction with GOP and ASCP. Licensing these applications for autosourcing of the warehouse is not necessary, but you cannot use the Match feature without licensing both GOP and ASCP, and using PDS.
Order Management calls the Cost Management CST_COST_API to obtain cost from cst_item_costs or cst_quantity_layers when the Gross Margin feature of OM is enabled. Item cost is stored on the order line, for ease of calculating the margin.
Order Management integrates with Configure-to-Order processes to fulfill orders for Replenish to Order models and items. These business functions are Workflow enabled. If the item is a 'buy' item, the process routes the items to Purchasing by creating a requisition. This process is called back-to-back orders. If the item is a 'make' item, the process flow creates the Configuration Item, BOM, Routings, Work Orders, and Flow Schedules. When the item is replenished (either by making it or buying it), the item is received into inventory and the reservation is transferred to the OM order line, so it can be shipped.
Order Management's Sales Order UI provides a link to the Supply to Order Workbench where the user can see the supply details and status for documents (purchase order or work order) that are reserved or referenced to the ATO sales order line. This enables customer service representatives to give customers an order status without having to navigate to the PO, WIP or flow forms.
Order Management is able to process orders for items whose inventory is tracked in the Oracle Inventory application.
When processing orders for items in inventory organizations, Order Management enables additional attributes at the order line level to allow dual unit-of-measure (catchweight) and grade support. The secondary unit-of-measure and pricing unit-of-measure are interfaced to Advanced Pricing for catchweight items to enable accurate pricing at time of shipment.
If a line is sold for a project tracked in PJM, you can record in Order Management the project and task number. Order lines that are identified as belonging to a project and task are pulled into PJM after fulfillment to update status in PJM.
Oracle Order Management provides visibility to Quality Plans for items displayed via the Order Information Portal through integration with Quality.
Order Management integrates with Oracle Work in Process to fulfill orders for Assemble to Order models and items. These business functions are Workflow enabled. The ATO process flow creates the Configuration Item, BOM, Routings, Work Orders, and Flow Schedules as required. The Work Order carries a link back to the OM order line, and the OM user can see the WIP job number and status by viewing the Inventory Reservation associated with the order line. Once the WIP job is complete or partially complete, the reservation is transferred to the OM line, and the line continues on its process flow.
Oracle Order Management together with Oracle Sales Contracts can create long term agreements or a one-time sale, including terms and conditions for use by Sales Managers, Sales Representatives, Contract Negotiators, Contract Administrators as well as Legal Representatives. This functionality enables Oracle Sales Contracts and includes formal negotiation complete with internal approval and customer acceptance. Fundamental capabilities required for sales negotiation are supported, as well as additional contractual capabilities such as terms and conditions, price holds and the capability to enforce the agreed upon terms for future customer purchases. All Oracle Order Management transactions support the formal sales contract flows.
Incentive Compensation (previously called Sales Compensation) pulls order lines from Order Management using a transaction collection API to calculate commissions and effectively align compensation with business objectives.
Order Management integrates with a few CRM products such as iStore, Quoting, and Depot Repair through Order Capture. The external teams can use the Order Management Process Order Group APIs to convert a quote to an order. Any changes to the Order Management Objects are communicated on-line to Order Capture via the Order Capture feedback queue. CRM products which are interested in the Order related information need to subscribe to the Order Capture queue to poll the messages.
Partners Online sends orders and lines entered through its user interface to Order Management by way of the Process Order API.
Telesales' eBusiness Center has several integrations with Order Management. There is an Order tab to view order history and create new orders. The New button on the Order tab launches the Sales Order window. The Party, Account, Address and Contact information entered in the eBusiness Center are carried over and populated in the Sales Orders window. Order Management automatically creates an account, if an Account does not yet exist for the Party provided in TeleSales. The user can then enter the other details and process the Order.
Order Management can receive RMA orders and lines from Oracle Trade Management as part of its dispute handling functionality. In addition, Order Management leverages the Promotion Limits feature of Trade Management through Advanced Pricing calls.
Order Management is the ERP module used by Depot Repair to create RMA and Sales Orders, validate customer accounts, and invoice customers for repairs.
See: Order Capture
Field Service Report requires specifically that you setup Price Lists, Units of Measure (UOM), and two Inventory Item Attributes in Order Management. Price Lists contain the list price for an item. Items could be material, but also labor and expenses like units of driving distance. Once material, expense and labor transactions for a task have been taken down on the Field Service Debrief, this information is updated to Charges. In Charges the list price for the item is received from Order Management and is used to generate an invoice for a customer.
Information about Install Base trackable items is interfaced to Install Base in the following ways:
Shippable Items: For both orders and returns, information is interfaced to Install Base via Inventory Interface.
Non-Shippable Items: For both order and returns, information is interfaced to Install Base via the Order Management Fulfillment workflow activity
Install Base also supports Internal Sales Order transactions by appropriately creating / updating item instances as a result of transactions between internal organizations such as pick transactions, shipments, and receipts.
Service Contracts has an API which pulls information from the Install Base newly created customer records and creates an ownership record.
Warranty: A Warranty contract is created when a Serviceable product is shipped. A Warranty contract is created when serviceable product with bill of material contains a warranty. Whenever possible, where multiple products are sold on one order, one warranty is created for all the products. Each different warranty item creates a separate warranty line on the contract.
Extended Warranty: An Extended Warranty contract is created when an Extended Warranty is sold on a sales order. Extended Warranty contracts can also be consolidated. Order Management interfaces to Service Contracts via the Fulfillment workflow activity (Fulfill Line). This activity populates the Service Contracts interface table. You need to run the Service Contracts Order Processing concurrent program to process the interface records.
When a serviceable item is returned for credit, whether the customer is credited for the extended warranty depends on the setting for the profile OKS: Raise Credit Memo for IB Instance Termination. Additionally the amount of credit issued is determined by the Global Contracts default setting. This can be overridden at the serviceable item return line level via the workflow activity Set Order Line- Service Credit. You can use this activity to set the service_credit_eligible_code to a value of Full, Pro-rated or None.
Subscription: Fulfillment starts after the contract approval process. Driven by each subscription line's instantiated fulfillment template, a concurrent program creates a sales order in Oracle Order Management for each delivery. The order details are populated with information from the subscription agreement. Once the order is created in Order Management, you can release and ship them. The integration to Oracle Service Contracts is bidirectional. Service Contracts sends Item and fulfillment details to create a sales order. Delivery and status details are sent to Service Contracts, when the order is ship confirmed, to be stored in the Subscription contract.
RMA: Service Contracts sends Order Management RMA information via the Process Order API.
In previous releases, Service Contracts used Order Capture as an integration point to create service contracts initiated by Order Management. In release 12, direct API calls from Order Management to Service Contracts replace Order Capture.
The Service Contracts (OKS) API processes one order line at a time, however it is also used for High Volume Order Processing for multiple lines.
This OKS API processes extended warranty/service (immediate or delayed) order lines.
The OKS Service Contracts Order Processing Concurrent program takes the data from the interface tables that have been populated by the API call and creates service contracts. You can run this concurrent program in multiple instances to create service contracts.
The Service Contracts Order Processing Concurrent program verifies that the instances are interfaced to Install Base before processing the interfaced service order lines.
Order Management integrates with SFM via workflow activities that can be inserted into the Order Management header and line flows. Order lines holding items that are marked as provisionable will be sent to SFM instead of through the Shipping Execution process for fulfillment.
As part of the Oracle Service suite of products, Spares Management is classified as an installable module provided with the Field Service solution. Oracle Inventory and Oracle Order Management are the only prerequisite products specifically required for a Spares Management implementation.
Integration with Oracle Order Management provides the ability to move parts among multiple inventory organizations and includes several sophisticated warehouse management features.
Oracle Spares Management supports the business processes involved in the management of spares parts in a field service organization. It is integrated with a number of Oracle's ERP and CRM applications. This integration provides extensive functionality to manage the business activities involved in the spares management process.
Oracle Order Management provides the functionality for the processing of an internal order to deliver parts to a field engineer for a specific task. An internal order is initiated in Spares Management in the Parts Requirement window. Within Order Management, the internal order is processed almost exactly like an order that is to be shipped to an external customer. This processing includes the picking, packing, shipping and receiving of the order.
Key integration features with Oracle Order Management include:
Ability to create Internal Orders to transfer parts across inventory organizations
Ability to use mobile applications in the warehouse
Ability to use barcode and scanning functionality
Ability to use pick, pack and ship functionality
Oracle Order Management users can create long-term agreements or contracts for a one-time sale, including contract terms and conditions based on a library of pre-approved clauses and contract templates, using Oracle Sales Contracts functionality. This functionality includes formal contract terms negotiation complete with internal approval and customer acceptance. All Oracle Order Management documents provide access to the contract terms library, and to the contract terms negotiation features provided by Sales Contracts:
Quotes: Sales Orders beginning with a Negotiation workflow
Sales Orders: Sales Orders beginning with a Fulfillment workflow
Release Orders: Sales Orders with a Sales Agreement reference governing items, price, and terms
Sales Agreements: Long-term agreements which can be referenced on a single transaction to leverage volume pricing, terms and conditions
This profile determines if an installation is authorized to use the contractual option provided in Order Management, and is set at the site level to enable terms and conditions integration in Order Management. If the profile option is set to Yes, you can author, negotiate and manage sales contracts including Agreements and Sales Orders and leverage Sales Contracts functionality such as Microsoft Word Integration and Collaboration, and Contract Expert to assemble your contract rapidly and efficiently.
To set up Oracle Sales Contracts for Authoring and Negotiating Contract Terms
Set up the Contract Terms Library. Create any necessary:
Clauses
Contract Templates
Contract Expert Rules
See Oracle Sales Contracts Implementation and Administration Guide
You may create a Contract Template or you could add terms using the MS Word Integration functionality. Terms in the form of an MS Word document, pdf, or any format can be attached as well. If it is an Oracle generated document, terms are merged during preview of Sales Agreements / Sales Orders. Also terms are attached to notification for approval. Contract Templates can be enabled for different document types. You can have one or more Contract Templates per Document Type, such as for Sales Orders or Sales Agreements. It is not mandatory to define a default Contract Template on the Transaction Type. See Oracle Sales Contracts Implementation and Administration Guide.
Create at least one Layout Template. The Layout Template is part of Oracle Applications Technology Group (ATG) functionality. If you are using Preview and Print, a template must be available. The layout template is not mandatory to define on the transaction type. A layout template can also be chosen from Oracle Sales Contracts or defined as a default. The transaction type default will override Oracle Sales Contract default.
NOTE: During Layout Template setup, it is recommended to leave the end date blank. Without an end date, Layout Templates will not become inactive thus preventing use of an inactive Layout Template with an open sales document.
Set the profile option OKC: Enable Sales Contracts to Yes. See Setup Profile Options for more information.
Oracle Sales Contracts Implementation and Administration Guide
To set up Authoring and Negotiating Contract Terms
Set up workflow extensions. Add the Sales Agreement/Sales Order Generation activity to the Negotiation with Approval workflow between Submit Draft and Internal Approval. This enables automatic attachment on the workflow notification to allow approvers to easily view the document and on the transaction itself as a reference in Contract Documents.
If your business process includes an additional approval layer for non-standard clauses, extend workflow to check the sales document for the existence of non-standard clauses, and if they exist, route the sales document to additional approvers. As an example, the workflow activity, "Non Standard Clause Exists?" can be inserted between "Get Next Approver" and "Approved" to route to additional legal approvers while the Quote or Sales Agreement is in the "Pending Internal Approval" status.
If needed, set the profile option OM: Printed Document Extension Class Name. Use this profile with a custom java code class path to enable printing from customized tables. See Preview and Print.
Set up the transaction type. This can include:
Contract Templates
Layout Templates
A setup list of approvers
Assigning default templates for Contract and Layout are not mandatory. If your workflow supports Approvals, set up an Approval list for each transaction type. See Approvals.
Note: Contract Templates and Layout Templates can be attached to any OM transaction type.
Related Topics
See:Oracle Sales Contracts Implementation and Administration Guide for more details on authoring and negotiating Contract terms.
There are two ways to use the Sales Contracts Workbench: Sales Contracts Workbench Administrator and Sales Contracts Workbench User. Sales Contracts Workbench Administrator has additional ability to update Contracts Admin via Assign Contract Administrator functionality. Contract Administrators now can use the Contracts Workbench to carry out tasks like viewing and accessing contracts, and notifications. The Contracts Workbench is an HTML page that can be personalized by administrators. Bins or personalizable views are used in the Workbench page to enable administrators to displaying contract information, and additional seeded bins will display a user’s notifications, and commonly used shortcuts to additional contract functions. Administrators can take actions on the contracts directly from the bins, depending on their access rights and the contract status. They can also bookmark contracts for frequent use.
The available functionalities for Workbench are listed below:
Search Capabilities – you can perform simple and/or advanced searching in the Workbench. You can open and update documents from the search results.
Contract bins - defines the contract bins shown on the Workbench, and how users can personalize each bin to determine bin content (results) based on different bin views.
Notifications bins.
Shortcuts – links to frequently used actions and reports like Creating Sales Agreements and Sales Orders, Clause Analysis and Assign Contract Administrator.
Please see the Oracle Sales Contracts Implementation and Administration Guidefor more details.
The integration between Siebel Order Capture and Oracle eBusiness Suite (EBS) Order Management modules enables two way movement of data at user defined business events between these products. This feature supports inbound integration for create, update, and cancel of sales order or line using web service and outbound integration to notify selective sales order changes (like hold application, release, close) by raising work flow business events.
Using this integration, you can:
Import an order created using Siebel Order Capture into Oracle EBS Order Management for the first time.
Communicate the changes back to EBS Order Management whenever the specific order is updated in Siebel Order Capture.
Communicate process flow changes from Oracle EBS Order Management to Siebel Order Capture functionality.
To integrate Siebel Order Capture and Oracle EBS Order Management, you must set up the following:
Implement the Order to Cash: Siebel CRM - EBS Process Integration Pack. See: Siebel CRM Integration Pack for Oracle Order Management: Order to Cash 2.5 - Implementation Guide
Set up the following profiles to address the way Order Management returns freight charges and tax amounts to the Seibel Order Capture application:
OM: Roll Up Charges on Line Level for AIA Synch
OM: Roll Up Charges on Header Level for AIA Synch
OM: Roll Up Tax on Header Level for AIA Synch
If required, then administrators can extend the flow status synchronization capability.
You must set the following profiles at Site level, to a value of Yes or No. If you do not set any value, then the application considers the default value of No, and implements appropriate behavior. The application treats an SQL NULL value for these profile option values as a No, for the purpose of computation of the freight charges and tax amounts.
OM: Roll Up Charges on Line Level for AIA Synch
If the profile value is Yes, then Oracle EBS Order Management includes the freight charges total (rolled up to the order line level) in its response messages to Siebel. If the profile value is No, then the response messages will not contain the freight charges rolled up to the order line level. Seeking a line-level roll up for charges can prove to be performance critical at times (specially in case of orders with many order lines). To this extent, you must take additional care in setting this profile option to a value of Yes.
OM: Roll Up Charges on Header Level for AIA Synch
If the profile value is Yes, then Oracle EBS Order Management includes the freight charges total (rolled up to the order header) in its response messages to Siebel. If the profile value is No, then the response messages will not contain the freight charges rolled up to the header level.
OM: Roll Up Tax on Header Level for AIA Synch
If the profile value is Yes, then Oracle EBS Order Management includes the tax amount total in its response messages to Siebel. If the profile value is No, then the response messages will not contain the tax amount total rolled up to the header level.
Note: Regardless of this profile option, the response messages will always include line-level tax amounts.
The integration between Siebel Order Capture and Oracle eBusiness Suite (EBS) Order Management modules use the predefined flow status codes where the Oracle EBS Order Management application raises an event on a change in the flow status code. As an Order Management administrator, you can enable or disable specific flow status code change to raise an outbound communication event using the AIA – Sales Order Status Synchronization window. Using this window, you can update the data defined in the OE_FLOW_STATUS_AIA_SYNC table. This table stores the information about the order/line flow status codes, and whether a specific change to a given flow status code needs to initiate a communication to AIA layer (by raising business event). Based on the configurations, EBS Order Management sends applicable information to Siebel Order Capture.
You can configure the following flow status codes to raise a business event to communicate status change with Siebel Order Capture application:
Awaiting Fulfillment
Awaiting Receipt
Cancelled
Inventory Interfaced
Interfaced to Receivables
Partially interfaced to Receivables
Awaiting Invoice Interface – Pending Complete Delivery
Awaiting Invoice Interface – On Hold
Awaiting Invoice Interface – Incomplete Data
In Receiving
In Receiving Partial
Returned
External Req Open
External Req Partial
External Req Requested
Internal Req Open
Internal Req Partial
Internal Req Requested
BOM and Routing Created
Config Item Created
Supply Eligible
Booked
Awaiting Shipping
Shipped
Fulfilled
Closed
Awaiting Invoice Interface - RFR Item
Invoice Interface – Not Applicable
Pending pre-billing acceptance
Awaiting Return
Awaiting Return Disposition
Of these, statuses 3, 23, 24, 25, 26 are enabled by default for synchronization while the others are disabled by default for synchronization. You can edit the synchronization preferences for all these status using the AIA – Sales Order Status Synchronization window.
To extend the flow status synchronization capability:
Navigate to the AIA – Sales Order Status Synchronization window.
Indicate synchronization for the applicable flow statuses to raise a business event to communicate status change with Siebel Order Capture application.
Save and close the window.