Generating LCM Charges Using Custom Pricing Attributes

8/9/2019 Generating LCM Charges Using Custom Pricing Attributes

1/9

Generating LCM Charges using Custom Pricing Attributes Page 1

Generating LCM Charges using

Custom Pricing Attributes

An Oracle White Paper

May 2014


2/9


Generating LCM Charges using Custom

Pricing Attributes

EXECUTIVE SUMMARY

The new application, Landed Cost Management (LCM), enables exact

shipment charges to be applied to incoming receipts. These charges are

calculated using the Freight and Special Charges functionality from Advanced

Pricing within the Pricing Transaction Entity of “Purchasing”.

Advanced Pricing is very flexible in that custom attributes can be defined to

derive specific charges. The way that Landed Cost Management builds these

attributes is different from the processing for Advanced Pricing withPurchasing.

Introduction

Using the standard Pricing Attributes for Item Number and ‘Purchasing’ Item

Category, as well as the other seeded Qualifiers will generate the charges in

LCM. When trying to define custom attributes to derive charges, it appeared

that the system was not calculating the correct values.

There are several notes that exist within My Oracle Support regarding thesetup of Advanced Pricing to function with LCM. This document is designed

to supplement those documents.

Related Notes

EBS LCM How to setup Landed Cost Management with Advanced

Pricing(QP) Formula (Doc ID 966357.1)

How to Customize Charges Generation in LCM (Doc ID 1218614.1)


3/9


CALLING THE PRICING PACKAGE

Overview

When prices in Purchasing are affected by modifiers using the integration to

Advanced Pricing, either Discounts or Surcharges, the package

‘PO_ADVANCED_PRICE_PVT’ is used to link the purchasing document to

the pricing objects. However, for Landed Cost Management (LCM), the

values created for the charges against the receipt shipments are derived by

Modifiers created as Freight and Special Charges in Advanced Pricing and

they must be defined against the “Purchasing” Pricing Transaction

Entity(PTE) and “PO” System Source Code.

Using this PTE, the package “PO_ADVANCED_PRICE_PVT” is used again,

however, LCM uses different values in the package, and the correct

calculation of charges will be dependent on calling the correct variables when

the receipt shipments are processed.

The package contains set of variables split between Header values

(‘header_rec_type’) and Line values (‘line_rec_type’). The list below

indicates which values are populated when a shipment is processed in LCM,

i.e. ‘Generate Charges’.

header_rec_type line_rec_type

org_id supplier_id

p_order_header_id supplier_site_id

supplier_id ship_to_location_id

supplier_site_id ship_to_org_id

creation_date item_id

ship_to_location_id category_id

ship_to_org_id currency_code

shipment_header_id need_by_date

shipment_num shipment_line_id

currency_code primary_unit_of_measure

source_org_id to_organization_id

unit_of_measure

source_document_code

quantity


4/9


Therefore, in the procedure of creating custom packages and functions

defined to generate non-standard attributes for pricing and qualifiers, the

variables to be used need to be defined per the list above.

For pricing calls in Purchasing the general approach is to use the‘order_line_id’, i.e. PO_ADVANCED_PRICE_PVT.G_LINE.order_line_id and in the

query for the custom function reference this value against the po_line_id in

PO_LINES_ALL.

However, for calls from Landed Cost Management when the shipments have

the charges generated, there is a different call to be made. The ‘order_line_id’

is a NULL value, and therefore not in the list. Thus as charges are created for

shipments, the best value to use is ‘shipment_line_id’. This value does not

exist in PO_LINES_ALL, but instead in INL_SHIP_LINES_ALL.

The table INL_SHIP_LINES_ALL has references to the

INVENTORY_ITEM_ID and SHIP_TO_ORGANIZATION_ID . This table also

has the SHIP_LINE_SOURCE_ID which links to the LINE_LOCATION_ID in

PO_LINE_LOCATIONS_ALL . So it is very easy to link back to the original

Purchase Order from the LCM shipment.


5/9


EXAMPLE PACKAGE

The below package and function is designed to retrieve a specific Category

value from an item. This is not the Purchasing Category Set, this is a different

Category Set, in this example, ‘Customs Class’.

Note: One could use a custom profile option then hard-code the Category Set

in the query.

Specification

Body

Advanced Pricing Set Up

To accompany the custom package and function, the following Advanced Pricing


6/9


SETUP REQUIRED

Responsibility: Oracle Pricing Manager

Navigate to: Setup > Attribute Management > Context and Attributes

Context and Attributes


7/9


Responsibility: Oracle Pricing Manager

Navigate to: Setup > Attribute Management > Attribute Linking and Mapping

Attribute Mapping (PTE)

Attribute Mapping

Choose the Attribute Mapping button.


8/9


This set up will link the custom package and function to the custom attribute,

in this case a qualifier. The normal pricing Modifier set up can be defined and

after Build Attribute Mapping is completed, the correct charges applied in

LCM.


9/9

Generating LCM Charges using Custom Pricing Attributes

May 2014

Author: Marcus Lawrence

Contribution Acknowledgements: Samir Othman and Kelli Stone

Oracle Corporation

World Headquarters

500Oracle Parkway

Redwood Shores,CA94065

U.S.A.

WorldwideInquiries:

Phone: +1.650.506.7000

Fax: +1.650.506.7200

www.oracle.com

Oracle Corporation provides the software That powers the Internet.

Oracle is a registered trademark of Oracle Corporation.Various

Product and service names referenced here in maybe trademarks

Of Oracle Corporation.All other product and service names mentioned maybe trademarks of the irrespective owners.

Copyright©2002 Oracle Corporation

All rights reserved.

Documents

Generating LCM Charges Using Custom Pricing Attributes