Oracle E-Business Suite R12 Supply Chain Management

Guys,
I got a request to review book “Oracle E-Business Suite R12 Supply Chain Management” written on Oracle Supply Chain by Muneeb A. Siddiqui and published by Packt Publishing.

Apparently it seems to me good book for beginners with Case study etc. I will review this and will keep everyone posted. Meanwhile you guys can have a look at Sample Chapter on following link

Advertisements

Price List Bulk Loader Example Scripts

Please apply Patch#4900462 and find the following example scripts under QP_TOP/patch/11.5/sql directory.

QPBLKEX1.sql – Script populates interface tables to insert price list header and price list line.

QPBLKEX2.sql – Script populates interface tables to insert price list header and price list line and pricing attributes.

QPBLKEX3.sql – Script populates interface tables to insert price list header and price break line.

QPBLKEX4.sql – Script populates interface tables to update price list header with qualifiers.

QPBLKEX5.sql – Script populates interface tables to attach secondary price lists to the primary price list.

Calculate Price Flag in Oracle Order Management

Price Flag indicates the control for which the price is frozen

Calculate Price Flag in Oracle Order Management

How to list down Attribute Mapping Rules in Oracle Advanced Pricing

SELECT QPSEG.SEGMENT_MAPPING_COLUMN, QPSOUR.USER_SOURCING_TYPE,

QPSOUR.USER_VALUE_STRING, QPCON.PRC_CONTEXT_CODE,

QPSOUR.ATTRIBUTE_SOURCING_LEVEL, QPSOUR.REQUEST_TYPE_CODE,

QPREQ.PTE_CODE, QPCON.PRC_CONTEXT_TYPE, QPSEG.SEGMENT_CODE,

QPCON.SEEDED_FLAG CONTEXT_SEEDED_FLAG,

QPSEG.SEEDED_FLAG ATTRIBUTE_SEEDED_FLAG

FROM QP_SEGMENTS_B QPSEG,

QP_ATTRIBUTE_SOURCING QPSOUR,

QP_PRC_CONTEXTS_B QPCON,

QP_PTE_REQUEST_TYPES_B QPREQ,

QP_PTE_SEGMENTS QPPSEG

WHERE QPSOUR.SEGMENT_ID = QPSEG.SEGMENT_ID

AND QPPSEG.USER_SOURCING_METHOD = ‘ATTRIBUTE MAPPING’

AND QPSOUR.REQUEST_TYPE_CODE = ‘ONT’

AND QPSEG.PRC_CONTEXT_ID = QPCON.PRC_CONTEXT_ID

AND QPREQ.REQUEST_TYPE_CODE = QPSOUR.REQUEST_TYPE_CODE

AND QPPSEG.PTE_CODE = QPREQ.PTE_CODE

AND QPPSEG.SEGMENT_ID = QPSOUR.SEGMENT_ID

AND QPPSEG.SOURCING_ENABLED = ‘Y’

AND QPCON.PRC_CONTEXT_TYPE IN

(‘PRICING_ATTRIBUTE’, ‘PRODUCT’, ‘QUALIFIER’)

Examples to use in setting up modifiers in Oracle Advance Pricing

Example 1: Line level discount of 8% discount on all products

File Path: $QP_TOP/patch/115/sql/QPXEXDS1.sql

Example 2: Buy more than 5 quantities of item 62081 , Get 8% discount

File Path: $QP_TOP/patch/115/sql/QPXEXDS2.sql

Example 3: For customer 1000, Buy more than 2 Units of item 62081, Get 10% discount

File Path: $QP_TOP/patch/115/sql/QPXEXDS2.sql

Example 4: Charge 2% surcharge on all products

File Path: $QP_TOP/patch/patch/115/sql/QPXEXSUR.sql

Example 5: For customer 1000, Buy more than 2 units of item 62081, Get a Payment Term 2/10 NET 30

File Path: $QP_TOP/patch/115/sql/QPXEXTSN.sql

How to Define Event Phases in Oracle Advanced Pricing

Events are points in pricing process flow when the calling application sends a pricing request to the pricing engine (similar to a workflow event). The information that the pricing engine returns, for example, base prices, price adjustments, promotions, or freight charges, depends on the pricing phases of the event.

 

A pricing phase controls what modifiers are considered by the pricing search engine and in what sequence they should be applied to the request. The attributes of a pricing phase allow us to control which modifiers can be placed in a phase. (Metalink)

Example

We need to Apply Surcharge at two events when order booked and when order line entered so we need to define event phase as shown in following picture.

To Define Event Phase

Navigate to

Setup –> Event Phases

By using Oracle Pricing manager Responsibility

11.JPG

 

When we assign a modifier to a pricing phase the Modifier Setup form matches the attributes of the modifier to the attributes of the available pricing phases to validate which pricing phase or phases a modifier can be placed in. A Modifier can only be assigned to one Phase

Now Map This Event Phase in Modifier interface as shown below

21.JPG

How to enable Pricing Engine Request Viewer

The Pricing Engine Request Viewer window captures the pricing call from any calling application such as Order Management, and displays the inputs and outputs of the pricing call.

The information displayed by the Pricing Engine Request Viewer helps us to diagnose which lines were selected or rejected by the pricing engine to determine why certain prices and adjustments were or were not applied. The Pricing Engine Request Viewer displays the most recent pricing request each time the pricing engine captures a new transaction.

The Pricing Engine Request Viewer window is available in Oracle Order Management using the following navigation path

Sales Orders à Tools à Pricing Engine Request Viewer.

Features available in the Pricing Engine Request Viewer window

Using the Pricing Engine Request Viewer window, we can do the following:

1. View Pricing Engine Requests

2. View Pricing Engine Request Lines

2.1. List Price

2.2. Selling Price

2.3. Service and Serviceable Items

3. View Pricing Engine Request Line Details

3.1. Price List lines and Modifier lines evaluated and deleted by the pricing engine

Process for the Pricing Engine Request Viewer

The following process outlines the series of activities when a pricing call is made:

  1. The calling application makes a call to build qualifiers and builds the contexts through sourcing.
  1. The calling application then calls the pricing engine with the attributes generated by attribute mapping.
  1. The pricing engine processes the request then searches for and evaluates eligible price list and modifier lines.
  1. If the profile option QP Debug is set to Request Viewer On, then the pricing engine inserts records into the permanent pricing debug tables and generates a unique request ID, storing the information from the calling application.
  1. The pricing request information can then be viewed by querying the request in the Pricing Engine Request Viewer from the OM Sales Order Pad or through the Pricing Manager responsibility menu.

Setting up the user profile options

QP: Debug:

Set the value of this profile option to Request Viewer to capture pricing request details into the pricing debug tables, and debug log information into the debug log table. The debug log text file is also created. The default value is Request Viewer Off. Must set this value to “Request Viewer On” at user

Check The Screen below after setting up above profile