Multiple Delivery sites

IBE: Use Line Level Shipping: Yes
Specifies whether customers can enter line level shipping information in shipping information page. Possible values - Yes/No. Default = Yes. If set to Yes, set IBE: Merge Shopping Cart Lines to No, as you cannot enable shopping cart line merging
and line splitting simultaneously.
IBE: Merge Shopping Cart Lines : No
Specifies whether to merge item lines in the shopping cart if the same item is added to the cart more than once. Yes = Lines are merged if duplicate; No = No line merging. Default = No. If set to Yes, set IBE: Use Line Level Shipping to No.
After adding products to the shopping cart and clicking the Check Out button

We can see an option to specify different shipping details for items. Once we select yes and continue checkout, we arrive at the page shown below

The user can select the item and update shipping details on an item level basis.

for further details please visit the knowledge section in www.ibizsoftinc.com

Release 12 - Customer Acceptance

Customers in some industries and geographies often need to be able to defer invoicing and/or revenue recognition for shipped goods until the customer receives the shipment and formally accepts the material. Customer acceptance can be captured from customers, customer service representatives, or from an external system. Customers can log into the self-service Order Information portal, customer service representatives can call the Order Information portal from their sales order workbenches, or Order Import/Process Order API can import customer acceptance captured from an external system. Oracle Order Management supports only full acceptance or total rejection for each outbound order line. One can set the number of days for Implicit acceptance, after the product has been shipped.

The OM System Parameter to enable Customer Acceptance has been introduced to take care of this new feature. This is for performance reasons, as calling the AR API to invoke their rules engine on every order line is expected to be expensive. It is called Enable Fulfillment Acceptance and the values are Yes/No. The default is No. This new parameter is seeded in the Generic
Category of System Parameters. Once this parameter is enabled, the Accounts Receivables API is called to invoke the rules engine to validate customer acceptance on every order line.

The basic business need is to defer invoicing and/or revenue recognition for the shipped goods till the customer
receives the shipment and accepts the material. Consequently, COGS accounting is deferred till customer communicates acceptance. In pre-billing acceptance, the customer accepts the goods first and then invoicing takes place. For pre-billing and
post-billing acceptance, you can accept the goods explicitly or implicitly.

Customer Acceptance is set up in AR’s Revenue Management module. At order entry, Order Management defaults the customer acceptance deferral reason and its attributes from Receivables onto the sales order line.

Customer acceptance can be enabled at Operating Unit level through OM system parameter: Enable Fulfilment Acceptance – Y/N.

We need to enable function security for the given responsibility for the following two functions:

1. Sales Orders: Fulfillment Acceptance – This ensures that the action attribute Fulfilment Acceptance is available in the Actions LOV.
2. Sales Orders: Update Acceptance Attributes – This allows for updating the acceptance attributes of Acceptance Name and Acceptance Expire days. These are attached to the sales order menu – ONT_ Sales_Order.

We will also need to define a deferral Reason, as follows

• Navigation: Revenue Management Super User -> Contingency Search / Definition -> this launches an HTML page.
• Define assignment rules to assign the deferral reason to customer, site, item, etc.
• For defining a Pre-billing Acceptance, use the deferral reason removal event as Invoicing.
• For defining a Post-billing Acceptance, use the deferral reason removal event as Customer Acceptance.

The Invoice Interface Workflow subprocesses handles sending interface data to Oracle Receivables for invoice and credit memo creation. It is used to handle pre-billing customer acceptance. If an order line requires pre-billing Customer Acceptance, this sub-process will prevent the order line from being interfaced to Receivables.

The Invoice Interface module does the following:
• Checks if pre-billing Customer Acceptance is required on the order line.
• If required, it waits until customer acceptance is recorded.
• When customer acceptance has been recorded, it continues the invoice interface process.
• If pre-billing acceptance is not required, it continues the invoice interface process without waiting for customer acceptance.
• Interface acceptance information and the deferral reasons information to Receivables.
• OM will change Invoice Interface to not interface an RMA line to AR if it references pre-billing rejected quantity.

Release 12 - Credit Card Security Code

This requirement was a much required functionality for any transaction involving Credit Cards in earlier releases, such as 11i. Typically the fraud rates are higher in case of Web-Orders, Mail orders and telephone orders than face-to-face transactions. Credit card companies are now directing merchants to ask cardholders for the Credit Card Verification Value of their credit card when cardholders place orders.

The Credit Card Verification Value is a three or four digit security code that is most often printed on the back of credit cards. By asking the cardholder to provide the Credit Card Verification Value the merchant can validate that a genuine card is being used during the transaction. Merchants using Credit Card Verification Value can expect to reduce their chargebacks by as much as 26 percent. Visa calls the credit card verification value for CVV2, MasterCard/Eurocard calls it CVC2, Discover Card and American Express calls it CID.

Credit Card Security Code is supported through Order Import in addition to Order Management user interfaces and process order public API.The security code is however, not stored anywhere in the database, although the Credit Card numbers are stored in encrypted form.

Some points to be noted :

Copying of payment attributes from a source order to a destination order would be supported only when the security code is not
set as mandatory. If the security code was set as mandatory in Oracle Payments, when trying to copy an order to a new order, you would have to uncheck the Payments box in the header or line before copying. If you go ahead with the copy, an appropriate error message would be displayed, asking the user to use copy appropriately. The reason why this is happening is because the security code value is available only temporarily, that too only till the time authorization is done. Once authorization is done, the security code value gets nulled out and is not stored anywhere. Hence, when an order is copied, it will the Security Code is null and the copy is not successful.

Release 12 - Price Book

With R12, Oracle Advanced Pricing provides a robust self-service capability for users to generate and publish lists of products they sell with their related prices. The user has the ability to generate a Price Book showing list and net prices for a specific customer.

The Price Book can cross multiple price lists to derive the net price for a customer. Multi-currency price lists as well as formula pricing are included. Current, past or future effective pricing dates are supported. Input criteria can optionally include specific items, item category, pricing attributes, qualifiers and price lists.

The final price will be the list price with the adjustments and Freight and special Charges (This is different from the Sales Orders window where you can see the list price and adjustments). You can add textual information, images, and other data to
use as a catalog with specified effective dates.

The Price Book uses the customer item cross reference number (when available) rather than the internal item number, making it easy for the customer to identify their items. A Price Book can be generated for a customer or a Delta Price Book showing only items with changed prices can be created.

The publication options for the Price Book include printed report, online views, XML messages and email. Additionally, a Price Book API is provided for other applications to generate a price book and then use the information as required.

The feature is available in Basic and Advanced Pricing. Basic Pricing users have a subset of the full price book functionality.

Using the Pricing User responsibility, navigate to the Reports tab in the Advanced Pricing HTML Page. You can create a new Price Book or search for an existing one.

Click the Price Book Name in the search results table to view the Price Book details. You can print the Price Book from the window shown below:

The Price Book lines are categorized according to categories.

Release 12 - Inventory Convergence

With this release, customers of Oracle’s Process Manufacturing applications can now use Oracle Inventory and Oracle Warehouse Management. The use of a single inventory application provides the Oracle Process Manufacturing user seamless integration with the rest of the e-Business Suite. This feature opens up additional functionality that was previously only available to Discrete Oracle Inventory users, such as vendor-managed and consigned inventory, reservations, move order requisitions, kanban, min-max replenishment and robust physical inventory and cycle counting functionality. The ability to implement Oracle Warehouse Management allows users to leverage sophisticated picking rules, license plates (LPN’S), putaway rules and task management.

Oracle Inventory, is the one source of all material management information. Key areas that have been enhanced for Oracle Order Management include improved allocation (picking) rules and added features to Move Orders. Additionally, the ability to price by a secondary quantity is available to all users who track their inventory in two quantities. Process users can leverage all of the functionality in Oracle Order Management, such as enhanced scheduling and reservations, and international drop shipments, as well as Oracle Warehouse Management functionality.

Oracle Inventory’s Dual Unit of Measure Control enables users to transact inventory in two unrelated units of measure where the conversion between the measures vary from lot to lot or from one transaction to the next. If an item is dual unit of measure control enabled, during transactions, users are prompted to enter the transaction quantity in both units and are able to query on hand balances, availability and reservations in both units for full supply chain visibility to all required handling units of measure.

This particular feature has an impact on the following functionalities

Product Development Workbench
Formula Management
Routings
Operations
Recipe Management
Simulator
Formula Analysis, Formula Inquiry,Indented BOM
Mass Search and Replace
Product Development Workflow and ERES

Release 12 - Web Analytics Support

Web Analytics is a new product that provides a complete web tracking solution – reporting on the entire online customer flow from clicks to lead generation to orders.

It is a tracking tool and reporting solution for Oracle iStore sites, providing seamless integration with the Oracle iStore site management infrastructure. It also tracks Oracle Partner Management and Oracle iSupport set up using the Oracle iStore site infrastructure. All of the reports provided by Oracle Web Analytics work out-of-the-box with these Oracle E-Business Suite sites. Oracle Web Analytics tracks Customer Application pages with no customization required, and then reports on these interactions.

Oracle iStore logs contexts to help Web Analytics track the user browsing pattern in Oracle iStore sites. Some of these contexts and events include:

• Product and Section ID contexts
• Login and logout events
• Cart creation events
• Order placement events

In Release 12 iStore provides the necessary framework support to Web Analytics product for the following features:

• Tracking visits
• Tracking registrations
• Tracking products and sections in the iStore catalog
• Tracking iStore shopping carts
• Tracking iStore order, payment and invoice inquiries
• Instrumentation and categorization of seeded iStore templates to allow the tracking
• Online privacy management for registered and anonymous visitors

Oracle Web Analytics, in combination with Oracle iStore, answers such questions as:

• Which sources bring the most customers, orders and revenue?
• Who are my most profitable online campaign partners?
• What is my conversion funnel?
• Which navigational paths lead to the most conversions?
• Is my online channel profitable?
• Does my online channel have usability issues slowing down the adoption?
• How are my summary traffic statistics (visitors, pages, visits, etc.) changing over time?
• How can I leverage my customer analytics from the web in my multi channel process?

Release 12 - Order Management System Parameters Setup

Parameters set up is one of the significant steps in Order Management Set up. These Parameters define basic steps or action to be taken as required. For example, when to start an audit trail or what to do when there is no response from the approver etc. The Parameters can be grouped into specific categories when creating them.


The values of these parameters can be set-up using tables or constant values. To navigation to the parameter definitions and values set up is as follows,

Order Management -> Setup-> System Parameters

The ‘define’ form gives a provision to create a new parameter. The interface is very straight forward. It asks to define the parameter code, name, description, category, value set, and open orders check. Value set allows us to select the type of value the parameter can take. It can take values from a table or the values can be entered as characters or numbers depending on the selection that is made. The category is taken from the lookup type ‘OM_PARAMETER_CATEGORY’.

Once the parameters are defined it has to be given a value when it is used in the order management set up for an organization. The ‘Values’ form can be selected by navigating as described above. The form has a field that displays the selected organization. The category can be selected to display the parameters only for the required category. The ‘Show all’ option will display all parameters from all categories. If ‘Show all’ option is selected the category field will be disabled. The required changes can be made to the parameter values and then it can be saved.