Scribd
Upload
126 views2 pages

Pricing API

The document discusses how ATTRIBUTE_GROUPING_NO and PRICE_LIST_LINE_INDEX are used in the Oracle Advanced Pricing API QP_PRICE_LIST_PUB.Process_Price_List. ATTRIBUTE_GROUPING_NO can be set to 1 and is not required. PRICE_LIST_LINE_INDEX identifies the price list line that a pricing attribute is attached to.

Uploaded by

Sandy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
126 views2 pages

Pricing API

The document discusses how ATTRIBUTE_GROUPING_NO and PRICE_LIST_LINE_INDEX are used in the Oracle Advanced Pricing API QP_PRICE_LIST_PUB.Process_Price_List. ATTRIBUTE_GROUPING_NO can be set to 1 and is not required. PRICE_LIST_LINE_INDEX identifies the price list line that a pricing attribute is attached to.

Uploaded by

Sandy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Document 1620289.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

Copyright (c) 2018, Oracle. All rights reserved.

How Are ATTRIBUTE_GROUPING_NO and PRICE_LIST_LINE_INDEX Used in API


QP_PRICE_LIST_PUB.Process_Price_List? (Doc ID 1620289.1)

In this Document

Goal
Solution

APPLIES TO:

Oracle Advanced Pricing - Version 12.1.3 and later


Information in this document applies to any platform.

GOAL

The goal of this document is to address the question "How Are ATTRIBUTE_GROUPING_NO and PRICE_LIST_LINE_INDEX Used in API
QP_PRICE_LIST_PUB.Process_Price_List?".

For example, reference this oracle standard QPPLXMP2.sql to write a script to upload mass price lists using
QP_PRICE_LIST_PUB.Process_Price_List

gpr_pricing_attr_tbl(J).ATTRIBUTE_GROUPING_NO := 1;
gpr_pricing_attr_tbl(J).PRICE_LIST_LINE_INDEX := 1;

Why are these 2 fields set to 1? Will they always be 1?


Are we supposed to use seq number for Attribute_grouping_no?

(it appears that on the price list form this uses sequence..when I enter one manually and
click Pricing Attributes, attribute_grouping_No is assigned a seq number not 1; however, if
one copies a price list line using the attribute_grouping_no is the same for the next price list line).

SOLUTION

We are not using attribute grouping number in pricing attributes this is not a required value, you can ignore this and/or set it to 1.

gpr_pricing_attr_tbl(J).ATTRIBUTE_GROUPING_NO := 1;

Price_list_line_index is to identify the price list line to which the pricing attribute is attaching.

gpr_pricing_attr_tbl(J).PRICE_LIST_LINE_INDEX := 1;

Suppose you are inserting three lines to price list like

Line A - 1
Line B - 2
Line C - 3

If you want to attach two pricing attributes to each line then

for Line A -1

1 of 2 6/20/2018, 10:35 AM
Document 1620289.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

pricing attribute table will be

gpr_pricing_attr_tbl(1).PRICE_LIST_LINE_INDEX := 1;
gpr_pricing_attr_tbl(2).PRICE_LIST_LINE_INDEX := 1;

for Line B -2

pricing attribute table will be

gpr_pricing_attr_tbl(1).PRICE_LIST_LINE_INDEX := 2;
gpr_pricing_attr_tbl(2).PRICE_LIST_LINE_INDEX := 2;

for Line C -3

pricing attribute table will be

gpr_pricing_attr_tbl(1).PRICE_LIST_LINE_INDEX := 3;
gpr_pricing_attr_tbl(2).PRICE_LIST_LINE_INDEX := 3;

Didn't find what you are looking for?

2 of 2 6/20/2018, 10:35 AM

You might also like