AFS - SCHDULE LINE WISE PRICE

Hi gurus,
              We are created a sale order for some qty.Here Size wise rates are different.
I go to AFS DATA-> AFS CONDITIONS -> Here i want to give the gridvalue wise pricing but system not taken the price.Where we check?
(.ie) S RED - 2 USD
      M RED - 3 USD
      L RED - 4 USD
Regards,
T.Murugu

Dear Venkatesh,
Already i given the Pricing indicator - 01(Different price by size).But When i go to sale order creation in AFS data->AFS conditions ->Amount column is not taken the price.Can i check anyconfiguration in pricing procedure?
Pls help me.
Regards,
T.Murugu
Edited by: MURUGA ANANTHAM on Mar 5, 2009 10:15 AM

Similar Messages

SHIPPING POINT WISE PRICE ??

HI
Requirement is Shipping point wise price will be vary for a material, So i created a table like " Shipping Point & Material" ( shipping pt is not avilable in standard feild catalogue so i added the feild in catelogue)
then i created a Condition Record.
but while creating Sales order system is saying "Condition record missing" ( valid Condition record is there in vk12)
shipping point is in KOMK structure, is it bcoz of that not picking?
If we add new feilds in to catelogue what r the steps we need to take care?
Thanks in Advance
Rajen

Hi Rajendra Prasad,
As per my knowledge we need to add Shipping point field in KOMG Stracture. And aloso u need to check the Step number filed for this table in the accessequence is change mode or disply mode if it is in change mode please select that line and open the fields and save the accessequence then it will come in to disply mode then system will pick the condition record..
I hope this will help you..
rewards, if it is useful...
Regards
Durga Prasad

Price from Order Line and Price from QP_PREQ_PUB.PRICE_REQUEST is different

Hi,
I have trouble in using QP_PREQ_PUB.PRICE_REQUEST to derive the price of an item.
RDBMS : 11.1.0.7.0
Oracle Applications : 12.1.3
From the Pricing Request Viewer or from Order Entry Line, The price lis coming as expected, but not from QP_PREQ_PUB.PRICE_REQUEST API.
Here are the details -
Primary Price List - 'Primary'
Secondary Price List - 'Secondary1' - Item Price 40 (Precedence 150)
Secondary Price List - 'Secondary2' - Item Price 25 (Precedence 130) , Custom Qualifier Qualifier_Attribute31 = > Attribute1('Yes/No') from Item Master.
From the application, it is giving 25. Where as using the below code it is giving 40, Can you please advise what could be the issue/fix for it?
DECLARE
p_line_tbl QP_PREQ_GRP.LINE_TBL_TYPE;
p_qual_tbl QP_PREQ_GRP.QUAL_TBL_TYPE;
p_line_attr_tbl QP_PREQ_GRP.LINE_ATTR_TBL_TYPE;
p_LINE_DETAIL_tbl QP_PREQ_GRP.LINE_DETAIL_TBL_TYPE;
p_LINE_DETAIL_qual_tbl QP_PREQ_GRP.LINE_DETAIL_QUAL_TBL_TYPE;
p_LINE_DETAIL_attr_tbl QP_PREQ_GRP.LINE_DETAIL_ATTR_TBL_TYPE;
p_related_lines_tbl QP_PREQ_GRP.RELATED_LINES_TBL_TYPE;
p_control_rec QP_PREQ_GRP.CONTROL_RECORD_TYPE;
x_line_tbl QP_PREQ_GRP.LINE_TBL_TYPE;
x_line_qual QP_PREQ_GRP.QUAL_TBL_TYPE;
x_line_attr_tbl QP_PREQ_GRP.LINE_ATTR_TBL_TYPE;
x_line_detail_tbl QP_PREQ_GRP.LINE_DETAIL_TBL_TYPE;
x_line_detail_qual_tbl QP_PREQ_GRP.LINE_DETAIL_QUAL_TBL_TYPE;
x_line_detail_attr_tbl QP_PREQ_GRP.LINE_DETAIL_ATTR_TBL_TYPE;
x_related_lines_tbl QP_PREQ_GRP.RELATED_LINES_TBL_TYPE;
x_return_status VARCHAR2(240);
x_return_status_text VARCHAR2(240);
qual_rec QP_PREQ_GRP.QUAL_REC_TYPE;
line_attr_rec QP_PREQ_GRP.LINE_ATTR_REC_TYPE;
line_rec QP_PREQ_GRP.LINE_REC_TYPE;
detail_rec QP_PREQ_GRP.LINE_DETAIL_REC_TYPE;
ldet_rec QP_PREQ_GRP.LINE_DETAIL_REC_TYPE;
rltd_rec QP_PREQ_GRP.RELATED_LINES_REC_TYPE;
x_price_contexts_result_tbl QP_Attr_Mapping_PUB.Contexts_Result_Tbl_Type;
x_qual_contexts_result_tbl QP_Attr_Mapping_PUB.Contexts_Result_Tbl_Type;
v_line_tbl_cnt integer;
I BINARY_INTEGER;
l_version VARCHAR2(240);
l_file_val VARCHAR2(60);
L_MODIFIER VARCHAR2(4000);
L_ADJUSTMENT_AMOUNT VARCHAR2(300);
L_MOD_NAME VARCHAR2(240);
l_unit_price number;
l_selling_price number;
BEGIN
MO_GLOBAL.INIT('ONT');
MO_GLOBAL.SET_POLICY_CONTEXT('S',89);
--FND_GLOBAL.APPS_INITIALIZE(1130,21623,660);
DBMS_OUTPUT.PUT_LINE('1');
v_line_tbl_cnt := 1;
---- Control Record
p_control_rec.pricing_event := 'BATCH';
p_control_rec.calculate_flag := QP_PREQ_GRP.G_SEARCH_N_CALCULATE;
p_control_rec.simulation_flag := 'Y';
p_control_rec.source_order_amount_flag := 'Y';
p_control_rec.PUBLIC_API_CALL_FLAG := 'N';
p_control_rec.rounding_flag := 'Q';
p_control_Rec.manual_discount_flag := 'N';
--p_control_rec.MANUAL_ADJUSTMENTS_CALL_FLAG := 'Y';
p_control_rec.request_type_code := 'ONT';
p_control_rec.TEMP_TABLE_INSERT_FLAG := 'Y';
DBMS_OUTPUT.PUT_LINE('2');
line_rec.request_type_code :='ONT';
--line_rec.PRICE_LIST_HEADER_ID := 8007;
line_rec.line_id :=2125125; -- Order Line Id. This can be any thing for this script
line_rec.line_Index :=1; -- Request Line Index
line_rec.line_type_code := 'LINE'; -- LINE or ORDER(Summary Line)
line_rec.pricing_effective_date := TRUNC(sysdate); -- Pricing as of what date ?
line_rec.active_date_first := TRUNC(sysdate); -- Can be Ordered Date or Ship Date
line_rec.active_date_second := TRUNC(sysdate); -- Can be Ordered Date or Ship Date
line_rec.active_date_first_type := 'ORD'; -- ORD/SHIP
line_rec.active_date_second_type :='SHIP'; -- ORD/SHIP
line_rec.line_quantity := 1; -- Ordered Quantity
line_rec.line_uom_code := 'EA'; -- Ordered UOM Code
line_rec.currency_code := 'USD'; -- Currency Code
line_rec.price_flag := 'Y'; -- Price Flag can have 'Y' , 'N'(No pricing) , 'P'(Phase)
p_line_tbl(1) := line_rec;
DBMS_OUTPUT.PUT_LINE('3');
---- Line Attribute Record
line_attr_rec.LINE_INDEX := 1;
line_attr_rec.PRICING_CONTEXT :='ITEM'; --
line_attr_rec.PRICING_ATTRIBUTE :='PRICING_ATTRIBUTE3';
line_attr_rec.PRICING_ATTR_VALUE_FROM :='ALL';
line_attr_rec.VALIDATED_FLAG :='Y';
p_line_attr_tbl(1) := line_attr_rec;
line_attr_rec.LINE_INDEX := 1;
line_attr_rec.PRICING_CONTEXT :='ITEM'; --
line_attr_rec.PRICING_ATTRIBUTE :='PRICING_ATTRIBUTE1';
--line_attr_rec.COMPARISON_OPERATOR_CODE         := 'BETWEEN';
line_attr_rec.PRICING_ATTR_VALUE_FROM := '4466'; -- INVENTORY ITEM ID
line_attr_rec.VALIDATED_FLAG :='Y';
p_line_attr_tbl(2) := line_attr_rec;
line_attr_rec.LINE_INDEX := 1;
line_attr_rec.PRICING_CONTEXT :='ITEM'; --
line_attr_rec.PRICING_ATTRIBUTE :='PRICING_ATTRIBUTE1';
--line_attr_rec.COMPARISON_OPERATOR_CODE         := 'BETWEEN';
line_attr_rec.PRICING_ATTR_VALUE_FROM := '2395'; -- INVENTORY ITEM ID
line_attr_rec.VALIDATED_FLAG :='Y';
p_line_attr_tbl(3) := line_attr_rec;
line_attr_rec.LINE_INDEX := 1;
line_attr_rec.PRICING_CONTEXT :='ITEM'; --
line_attr_rec.PRICING_ATTRIBUTE :='PRICING_ATTRIBUTE30';
--line_attr_rec.COMPARISON_OPERATOR_CODE         := 'BETWEEN';
line_attr_rec.PRICING_ATTR_VALUE_FROM := 'Yes'; -- INVENTORY ITEM ID
line_attr_rec.VALIDATED_FLAG :='Y';
p_line_attr_tbl(3) := line_attr_rec;
DBMS_OUTPUT.PUT_LINE('4');
---- Qualifier Attribute Record
qual_rec.LINE_INDEX := 1; -- Attributes for the above line. Attributes are attached with the line index
qual_rec.QUALIFIER_CONTEXT :='MODLIST';
qual_rec.QUALIFIER_ATTRIBUTE :='QUALIFIER_ATTRIBUTE4';
qual_rec.QUALIFIER_ATTR_VALUE_FROM :='8007'; -- PRICE LIST ID
qual_rec.COMPARISON_OPERATOR_CODE := '=';
qual_rec.VALIDATED_FLAG :='Y';
p_qual_tbl(1) := qual_rec;
DBMS_OUTPUT.PUT_LINE('5');
qual_rec.line_index := 1;
qual_rec.qualifier_context := 'ITEM';
qual_rec.qualifier_attribute := 'QUALIFIER_ATTRIBUTE31';
qual_rec.qualifier_attr_value_from := 'Yes';
qual_rec.comparison_operator_code := '=';
qual_rec.validated_flag := 'Y';
p_qual_tbl (2) := qual_rec;
DBMS_OUTPUT.PUT_LINE('6');
OE_ORDER_PUB.G_LINE.inventory_item_id := 4466;
DBMS_OUTPUT.PUT_LINE(Fnd_Profile.VALUE('QP_CUSTOM_SOURCED') );
--QP_Attr_Mapping_PUB.Build_Contexts
--( p_request_type_code => 'ONT',
-- p_line_index => 1,
-- p_pricing_type_code => 'L'
QP_Attr_Mapping_PUB.Build_Contexts(
p_request_type_code => 'ONT',
p_pricing_type => 'L',
--p_org_id => 89,
x_price_contexts_result_tbl => x_price_contexts_result_tbl,
x_qual_contexts_result_tbl => x_qual_contexts_result_tbl );
I := x_qual_contexts_result_tbl.FIRST;
IF I IS NOT NULL THEN
LOOP
DBMS_OUTPUT.PUT_LINE('Context: '||x_qual_contexts_result_tbl(I).context_name);
DBMS_OUTPUT.PUT_LINE('attribute_name: '||x_qual_contexts_result_tbl(I).attribute_name);
DBMS_OUTPUT.PUT_LINE('attribute_value: '||x_qual_contexts_result_tbl(I).attribute_value);
EXIT WHEN I = x_qual_contexts_result_tbl.LAST;
I := x_qual_contexts_result_tbl.NEXT(I);
END LOOP;
END IF;
I := x_price_contexts_result_tbl.FIRST;
IF I IS NOT NULL THEN
LOOP
DBMS_OUTPUT.PUT_LINE('Context: '||x_price_contexts_result_tbl(I).context_name);
DBMS_OUTPUT.PUT_LINE('attribute_name: '||x_price_contexts_result_tbl(I).attribute_name);
DBMS_OUTPUT.PUT_LINE('attribute_value: '||x_price_contexts_result_tbl(I).attribute_value);
EXIT WHEN I = x_price_contexts_result_tbl.LAST;
I := x_price_contexts_result_tbl.NEXT(I);
END LOOP;
END IF;
DBMS_OUTPUT.PUT_LINE(Fnd_Profile.VALUE('QP_CUSTOM_SOURCED') );
DBMS_OUTPUT.PUT_LINE('7');
l_version := QP_PREQ_GRP.GET_VERSION;
dbms_output.put_line(OE_ORDER_PUB.G_LINE.price_list_id);
dbms_output.put_line(OE_ORDER_PUB.G_LINE.inventory_item_id);
QP_PREQ_PUB.PRICE_REQUEST
(p_line_tbl,
p_qual_tbl,
p_line_attr_tbl,
p_line_detail_tbl,
p_line_detail_qual_tbl,
p_line_detail_attr_tbl,
p_related_lines_tbl,
p_control_rec,
x_line_tbl,
x_line_qual,
x_line_attr_tbl,
x_line_detail_tbl,
x_line_detail_qual_tbl,
x_line_detail_attr_tbl,
x_related_lines_tbl,
x_return_status,
x_return_status_text);
-- Return Status Information ..
DBMS_OUTPUT.PUT_LINE('8');
DBMS_OUTPUT.PUT_LINE('Return Status text '|| x_return_status_text);
DBMS_OUTPUT.PUT_LINE('Return Status '|| x_return_status);
DBMS_OUTPUT.PUT_LINE('+---------Information Returned to Caller---------------------+ ');
DBMS_OUTPUT.PUT_LINE('-------------Request Line Information-------------------');
I := x_line_tbl.FIRST;
IF I IS NOT NULL THEN
LOOP
DBMS_OUTPUT.PUT_LINE('Line Index: '||x_line_tbl(I).line_index);
DBMS_OUTPUT.PUT_LINE('Unit_price: '||x_line_tbl(I).unit_price);
DBMS_OUTPUT.PUT_LINE('Percent price: '||x_line_tbl(I).percent_price);
DBMS_OUTPUT.PUT_LINE('Adjusted Unit Price: '||x_line_tbl(I).adjusted_unit_price);
DBMS_OUTPUT.PUT_LINE('Pricing status code: '||x_line_tbl(I).status_code);
DBMS_OUTPUT.PUT_LINE('Pricing status text: '||x_line_tbl(I).status_text);
EXIT WHEN I = x_line_tbl.LAST;
I := x_line_tbl.NEXT(I);
END LOOP;
END IF;
DBMS_OUTPUT.PUT_LINE('-----------Pricing Attributes Information-------------');
I := x_line_detail_attr_tbl.FIRST;
IF I IS NOT NULL THEN
LOOP
DBMS_OUTPUT.PUT_LINE('Line detail Index '||x_line_detail_attr_tbl(I).line_detail_index);
DBMS_OUTPUT.PUT_LINE('Context '||x_line_detail_attr_tbl(I).pricing_context);
DBMS_OUTPUT.PUT_LINE('Attribute '||x_line_detail_attr_tbl(I).pricing_attribute);
DBMS_OUTPUT.PUT_LINE('Value '||x_line_detail_attr_tbl(I).pricing_attr_value_from);
DBMS_OUTPUT.PUT_LINE('Status Code '||x_line_detail_attr_tbl(I).status_code);
DBMS_OUTPUT.PUT_LINE('---------------------------------------------------');
EXIT WHEN I = x_line_detail_attr_tbl.last;
I:=x_line_detail_attr_tbl.NEXT(I);
END LOOP;
END IF;
DBMS_OUTPUT.PUT_LINE('-----------Qualifier Attributes Information-------------');
I := x_line_detail_qual_tbl.FIRST;
IF I IS NOT NULL THEN
LOOP
DBMS_OUTPUT.PUT_LINE('Line Detail Index '||x_line_detail_qual_tbl(I).line_detail_index);
DBMS_OUTPUT.PUT_LINE('Context '||x_line_detail_qual_tbl(I).qualifier_context);
DBMS_OUTPUT.PUT_LINE('Attribute '||x_line_detail_qual_tbl(I).qualifier_attribute);
DBMS_OUTPUT.PUT_LINE('Value '||x_line_detail_qual_tbl(I).qualifier_attr_value_from);
DBMS_OUTPUT.PUT_LINE('Status Code '||x_line_detail_qual_tbl(I).status_code);
DBMS_OUTPUT.PUT_LINE('---------------------------------------------------');
EXIT WHEN I = x_line_detail_qual_tbl.last;
I:=x_line_detail_qual_tbl.NEXT(I);
END LOOP;
END IF;
I := x_line_detail_tbl.FIRST;
DBMS_OUTPUT.PUT_LINE('------------Price List/Discount Information------------');
IF I IS NOT NULL THEN
LOOP
L_MOD_NAME := '';
DBMS_OUTPUT.PUT_LINE('Line Index: '||x_line_detail_tbl(I).line_index);
DBMS_OUTPUT.PUT_LINE('Line Detail Index: '||x_line_detail_tbl(I).line_detail_index);
DBMS_OUTPUT.PUT_LINE('Line Detail Type:'||x_line_detail_tbl(I).line_detail_type_code);
DBMS_OUTPUT.PUT_LINE('List Header Id: '||x_line_detail_tbl(I).list_header_id);
DBMS_OUTPUT.PUT_LINE('List Line Id: '||x_line_detail_tbl(I).list_line_id);
DBMS_OUTPUT.PUT_LINE('List Line Type Code: '||x_line_detail_tbl(I).list_line_type_code);
DBMS_OUTPUT.PUT_LINE('Adjustment Amount : '||x_line_detail_tbl(I).adjustment_amount);
DBMS_OUTPUT.PUT_LINE('Line Quantity : '||x_line_detail_tbl(I).line_quantity);
DBMS_OUTPUT.PUT_LINE('Operand Calculation Code: '||x_line_detail_tbl(I).Operand_calculation_code);
DBMS_OUTPUT.PUT_LINE('Operand value: '||x_line_detail_tbl(I).operand_value);
DBMS_OUTPUT.PUT_LINE('Automatic Flag: '||x_line_detail_tbl(I).automatic_flag);
DBMS_OUTPUT.PUT_LINE('Override Flag: '||x_line_detail_tbl(I).override_flag);
DBMS_OUTPUT.PUT_LINE('status_code: '||x_line_detail_tbl(I).status_code);
DBMS_OUTPUT.PUT_LINE('status text: '||x_line_detail_tbl(I).status_text);
DBMS_OUTPUT.PUT_LINE('-------------------------------------------');
EXIT WHEN I = x_line_detail_tbl.LAST;
BEGIN
SELECT NAME INTO L_MOD_NAME
FROM QP_LIST_HEADERS_ALL
WHERE LIST_HEADER_ID=x_line_detail_tbl(I).list_header_id
AND x_line_detail_tbl(I).list_line_type_code <>'PLL'
AND x_line_detail_tbl(I).adjustment_amount IS NOT NULL;
L_MODIFIER := L_MODIFIER||'~'||L_MOD_NAME;
EXCEPTION
WHEN OTHERS THEN
NULL;
END;
IF x_line_detail_tbl(I).list_line_type_code <>'PLL' AND x_line_detail_tbl(I).adjustment_amount IS NOT NULL THEN
L_ADJUSTMENT_AMOUNT := L_ADJUSTMENT_AMOUNT||'~'||x_line_detail_tbl(I).adjustment_amount;
END IF;
I := x_line_detail_tbl.NEXT(I);
END LOOP;
END IF;
SELECT line_unit_price , order_uom_selling_price
INTO l_unit_price , l_selling_price
FROM qp_preq_lines_tmp
WHERE pricing_status_code = Qp_Preq_Pub.g_status_updated
ORDER BY line_id;
DBMS_OUTPUT.PUT_LINE('Unit Price := '||l_unit_price);--x_line_tbl(1).UNIT_PRICE );
DBMS_OUTPUT.PUT_LINE('Selling Price := '||l_selling_price);---x_line_tbl(1).LINE_UNIT_PRICE );
DBMS_OUTPUT.PUT_LINE('L_MODIFIER: '||L_MODIFIER);
DBMS_OUTPUT.PUT_LINE('L_ADJUSTMENT_AMOUNT: '||L_ADJUSTMENT_AMOUNT);
DBMS_OUTPUT.PUT_LINE('--------------Related Lines Information for Price Breaks/Service Items---------------');
I := x_related_lines_tbl.FIRST;
IF I IS NOT NULL THEN
LOOP
DBMS_OUTPUT.PUT_LINE('Line Index :'||x_related_lines_tbl(I).line_index);
DBMS_OUTPUT.PUT_LINE('Line Detail Index: '||x_related_lines_tbl(I).LINE_DETAIL_INDEX);
DBMS_OUTPUT.PUT_LINE('Relationship Type Code: '||x_related_lines_tbl(I).relationship_type_code);
DBMS_OUTPUT.PUT_LINE('Related Line Index: '||x_related_lines_tbl(I).RELATED_LINE_INDEX);
DBMS_OUTPUT.PUT_LINE('Related Line Detail Index: '||x_related_lines_tbl(I).related_line_detail_index);
DBMS_OUTPUT.PUT_LINE('Status Code: '|| x_related_lines_tbl(I).STATUS_CODE);
EXIT WHEN I = x_related_lines_tbl.LAST;
I := x_related_lines_tbl.NEXT(I);
END LOOP;
END IF;
END; -- procedure --;
Edited by: user7751421 on Apr 20, 2013 8:54 AM

I tried with bellow code but it shows both Unit Price (price after apply all adjustment) and List price same_
What I need is get unit selling price before order book, when customer called for inquiry only._
DECLARE
p_line_tbl QP_PREQ_GRP.LINE_TBL_TYPE;
p_qual_tbl QP_PREQ_GRP.QUAL_TBL_TYPE;
p_line_attr_tbl QP_PREQ_GRP.LINE_ATTR_TBL_TYPE;
p_LINE_DETAIL_tbl QP_PREQ_GRP.LINE_DETAIL_TBL_TYPE;
p_LINE_DETAIL_qual_tbl QP_PREQ_GRP.LINE_DETAIL_QUAL_TBL_TYPE;
p_LINE_DETAIL_attr_tbl QP_PREQ_GRP.LINE_DETAIL_ATTR_TBL_TYPE;
p_related_lines_tbl QP_PREQ_GRP.RELATED_LINES_TBL_TYPE;
p_control_rec QP_PREQ_GRP.CONTROL_RECORD_TYPE;
x_line_tbl QP_PREQ_GRP.LINE_TBL_TYPE;
x_line_qual QP_PREQ_GRP.QUAL_TBL_TYPE;
x_line_attr_tbl QP_PREQ_GRP.LINE_ATTR_TBL_TYPE;
x_line_detail_tbl QP_PREQ_GRP.LINE_DETAIL_TBL_TYPE;
x_line_detail_qual_tbl QP_PREQ_GRP.LINE_DETAIL_QUAL_TBL_TYPE;
x_line_detail_attr_tbl QP_PREQ_GRP.LINE_DETAIL_ATTR_TBL_TYPE;
x_related_lines_tbl QP_PREQ_GRP.RELATED_LINES_TBL_TYPE;
x_return_status VARCHAR2 (240);
x_return_status_text VARCHAR2 (240);
qual_rec QP_PREQ_GRP.QUAL_REC_TYPE;
line_attr_rec QP_PREQ_GRP.LINE_ATTR_REC_TYPE;
line_rec QP_PREQ_GRP.LINE_REC_TYPE;
detail_rec QP_PREQ_GRP.LINE_DETAIL_REC_TYPE;
ldet_rec QP_PREQ_GRP.LINE_DETAIL_REC_TYPE;
rltd_rec QP_PREQ_GRP.RELATED_LINES_REC_TYPE;
x_price_contexts_result_tbl QP_Attr_Mapping_PUB.Contexts_Result_Tbl_Type;
x_qual_contexts_result_tbl QP_Attr_Mapping_PUB.Contexts_Result_Tbl_Type;
v_line_tbl_cnt INTEGER;
I BINARY_INTEGER;
l_version VARCHAR2 (240);
l_file_val VARCHAR2 (60);
L_MODIFIER VARCHAR2 (4000);
L_ADJUSTMENT_AMOUNT VARCHAR2 (300);
L_MOD_NAME VARCHAR2 (240);
l_unit_price NUMBER;
l_selling_price NUMBER;
l_item_id number:=17155;
BEGIN
MO_GLOBAL.INIT ('ONT');
MO_GLOBAL.SET_POLICY_CONTEXT ('S', 91);
--FND_GLOBAL.APPS_INITIALIZE(1130,21623,660);
DBMS_OUTPUT.PUT_LINE ('1');
v_line_tbl_cnt := 1;
---- Control Record
p_control_rec.pricing_event := 'LINE';
p_control_rec.calculate_flag := 'Y';
p_control_rec.simulation_flag := 'Y';
p_control_rec.source_order_amount_flag := 'Y';
p_control_rec.PUBLIC_API_CALL_FLAG := 'N';
p_control_rec.rounding_flag := 'Q';
p_control_Rec.manual_discount_flag := 'N';
--p_control_rec.MANUAL_ADJUSTMENTS_CALL_FLAG := 'Y';
p_control_rec.request_type_code := 'ONT';
p_control_rec.TEMP_TABLE_INSERT_FLAG := 'Y';
DBMS_OUTPUT.PUT_LINE ('2');
line_rec.request_type_code := 'ONT';
-- line_rec.PRICE_LIST_HEADER_ID := 386481;
line_rec.line_id := 72202; -- Order Line Id. This can be any thing for this script
line_rec.line_Index := 1; -- Request Line Index
line_rec.line_type_code := 'LINE'; -- LINE or ORDER(Summary Line)
line_rec.pricing_effective_date := TRUNC (SYSDATE); -- Pricing as of what date ?
line_rec.active_date_first := TRUNC (SYSDATE); -- Can be Ordered Date or Ship Date
line_rec.active_date_second := TRUNC (SYSDATE); -- Can be Ordered Date or Ship Date
line_rec.active_date_first_type := 'ORD'; -- ORD/SHIP
line_rec.active_date_second_type := 'SHIP'; -- ORD/SHIP
line_rec.line_quantity := 10; -- Ordered Quantity
line_rec.line_uom_code := 'Ea'; -- Ordered UOM Code
line_rec.currency_code := 'USD'; -- Currency Code
line_rec.price_flag := 'Y'; -- Price Flag can have 'Y' , 'N'(No pricing) , 'P'(Phase)
p_line_tbl (1) := line_rec;
DBMS_OUTPUT.PUT_LINE ('3');
---- Line Attribute Record
line_attr_rec.LINE_INDEX := 1;
line_attr_rec.PRICING_CONTEXT := 'ITEM'; --
line_attr_rec.PRICING_ATTRIBUTE := 'PRICING_ATTRIBUTE3';
line_attr_rec.PRICING_ATTR_VALUE_FROM := 'ALL';
line_attr_rec.VALIDATED_FLAG := 'N';
p_line_attr_tbl (1) := line_attr_rec;
line_attr_rec.LINE_INDEX := 1;
line_attr_rec.PRICING_CONTEXT := 'ITEM'; --
line_attr_rec.PRICING_ATTRIBUTE := 'PRICING_ATTRIBUTE1';
--line_attr_rec.COMPARISON_OPERATOR_CODE := 'BETWEEN';
line_attr_rec.PRICING_ATTR_VALUE_FROM := '17155'; -- INVENTORY ITEM ID
line_attr_rec.VALIDATED_FLAG := 'Y';
p_line_attr_tbl (2) := line_attr_rec;
-- line_attr_rec.LINE_INDEX := 1;
-- line_attr_rec.PRICING_CONTEXT := 'ITEM'; --
-- line_attr_rec.PRICING_ATTRIBUTE := 'PRICING_ATTRIBUTE1';
-- --line_attr_rec.COMPARISON_OPERATOR_CODE := 'BETWEEN';
-- line_attr_rec.PRICING_ATTR_VALUE_FROM := '72201'; -- INVENTORY ITEM ID
-- line_attr_rec.VALIDATED_FLAG := 'Y';
-- p_line_attr_tbl (3) := line_attr_rec;
-- line_attr_rec.LINE_INDEX := 1;
-- line_attr_rec.PRICING_CONTEXT := 'ITEM'; --
-- line_attr_rec.PRICING_ATTRIBUTE := 'PRICING_ATTRIBUTE30';
-- --line_attr_rec.COMPARISON_OPERATOR_CODE := 'BETWEEN';
-- line_attr_rec.PRICING_ATTR_VALUE_FROM := 'Yes'; -- INVENTORY ITEM ID
-- line_attr_rec.VALIDATED_FLAG := 'Y';
-- p_line_attr_tbl (3) := line_attr_rec;
DBMS_OUTPUT.PUT_LINE ('4');
---- Qualifier Attribute Record
qual_rec.LINE_INDEX := 1; -- Attributes for the above line. Attributes are attached with the line index
qual_rec.QUALIFIER_CONTEXT := 'MODLIST';
qual_rec.QUALIFIER_ATTRIBUTE := 'QUALIFIER_ATTRIBUTE4';
qual_rec.QUALIFIER_ATTR_VALUE_FROM := '386481'; -- PRICE LIST ID
qual_rec.COMPARISON_OPERATOR_CODE := '=';
qual_rec.VALIDATED_FLAG := 'Y';
p_qual_tbl (1) := qual_rec;
DBMS_OUTPUT.PUT_LINE ('5');
-- qual_rec.line_index := 1;
-- qual_rec.qualifier_context := 'ITEM';
-- qual_rec.qualifier_attribute := 'QUALIFIER_ATTRIBUTE31';
-- qual_rec.qualifier_attr_value_from := 'Yes';
-- qual_rec.comparison_operator_code := '=';
-- qual_rec.validated_flag := 'Y';
-- p_qual_tbl (2) := qual_rec;
qual_rec.LINE_INDEX := 1; -- Attributes for the above line. Attributes are attached with the line index
qual_rec.QUALIFIER_CONTEXT := 'CUSTOMER';
qual_rec.QUALIFIER_ATTRIBUTE := 'QUALIFIER_ATTRIBUTE5';
qual_rec.QUALIFIER_ATTR_VALUE_FROM := 5728; -- Customer Account ID
qual_rec.COMPARISON_OPERATOR_CODE := '=';
qual_rec.VALIDATED_FLAG := 'Y';
p_qual_tbl (3) := qual_rec;
qual_rec.LINE_INDEX := 1;
qual_rec.QUALIFIER_CONTEXT := 'ITEM_CATEGORY';
qual_rec.QUALIFIER_ATTRIBUTE := 'QUALIFIER_ATTRIBUTE35';
qual_rec.QUALIFIER_ATTR_VALUE_FROM := 'TOOLS.HARDWARE TOOLS (DISCOUNTABLE).'; -- item category
qual_rec.COMPARISON_OPERATOR_CODE := '=';
qual_rec.VALIDATED_FLAG := 'N';
p_qual_tbl (4) := qual_rec;
DBMS_OUTPUT.PUT_LINE ('6');
OE_ORDER_PUB.G_LINE.inventory_item_id := l_item_id;
DBMS_OUTPUT.PUT_LINE (Fnd_Profile.VALUE ('QP_CUSTOM_SOURCED'));
--QP_Attr_Mapping_PUB.Build_Contexts
--( p_request_type_code => 'ONT',
-- p_line_index => 1,
-- p_pricing_type_code => 'L'
QP_Attr_Mapping_PUB.
Build_Contexts (
p_request_type_code => 'ONT',
p_pricing_type => 'L',
--p_org_id => 89,
x_price_contexts_result_tbl => x_price_contexts_result_tbl,
x_qual_contexts_result_tbl => x_qual_contexts_result_tbl);
I := x_qual_contexts_result_tbl.FIRST;
IF I IS NOT NULL
THEN
LOOP
DBMS_OUTPUT.
PUT_LINE (
'Context: ' || x_qual_contexts_result_tbl (I).context_name);
DBMS_OUTPUT.
PUT_LINE (
'attribute_name: '
|| x_qual_contexts_result_tbl (I).attribute_name);
DBMS_OUTPUT.
PUT_LINE (
'attribute_value: '
|| x_qual_contexts_result_tbl (I).attribute_value);
EXIT WHEN I = x_qual_contexts_result_tbl.LAST;
I := x_qual_contexts_result_tbl.NEXT (I);
END LOOP;
END IF;
I := x_price_contexts_result_tbl.FIRST;
IF I IS NOT NULL
THEN
LOOP
DBMS_OUTPUT.
PUT_LINE (
'Context: ' || x_price_contexts_result_tbl (I).context_name);
DBMS_OUTPUT.
PUT_LINE (
'attribute_name: '
|| x_price_contexts_result_tbl (I).attribute_name);
DBMS_OUTPUT.
PUT_LINE (
'attribute_value: '
|| x_price_contexts_result_tbl (I).attribute_value);
EXIT WHEN I = x_price_contexts_result_tbl.LAST;
I := x_price_contexts_result_tbl.NEXT (I);
END LOOP;
END IF;
DBMS_OUTPUT.PUT_LINE (' Fnd_Profile.VALUE (QP_CUSTOM_SOURCED): ' || Fnd_Profile.VALUE ('QP_CUSTOM_SOURCED'));
DBMS_OUTPUT.PUT_LINE ('7');
l_version := QP_PREQ_GRP.GET_VERSION;
DBMS_OUTPUT.put_line (OE_ORDER_PUB.G_LINE.price_list_id);
DBMS_OUTPUT.put_line (OE_ORDER_PUB.G_LINE.inventory_item_id);
QP_PREQ_PUB.PRICE_REQUEST (p_line_tbl,
p_qual_tbl,
p_line_attr_tbl,
p_line_detail_tbl,
p_line_detail_qual_tbl,
p_line_detail_attr_tbl,
p_related_lines_tbl,
p_control_rec,
x_line_tbl,
x_line_qual,
x_line_attr_tbl,
x_line_detail_tbl,
x_line_detail_qual_tbl,
x_line_detail_attr_tbl,
x_related_lines_tbl,
x_return_status,
x_return_status_text);
-- Return Status Information ..
DBMS_OUTPUT.PUT_LINE ('8');
DBMS_OUTPUT.PUT_LINE ('Return Status text ' || x_return_status_text);
DBMS_OUTPUT.PUT_LINE ('Return Status ' || x_return_status);
DBMS_OUTPUT.
PUT_LINE (
'+---------Information Returned to Caller---------------------+ ');
DBMS_OUTPUT.
PUT_LINE ('-------------Request Line Information-------------------');
I := x_line_tbl.FIRST;
IF I IS NOT NULL
THEN
LOOP
DBMS_OUTPUT.PUT_LINE ('Line Index: ' || x_line_tbl (I).line_index);
DBMS_OUTPUT.PUT_LINE ('Unit_price: ' || x_line_tbl (I).unit_price);
DBMS_OUTPUT.
PUT_LINE ('Percent price: ' || x_line_tbl (I).percent_price);
DBMS_OUTPUT.
PUT_LINE (
'Adjusted Unit Price: ' || x_line_tbl (I).adjusted_unit_price);
DBMS_OUTPUT.
PUT_LINE ('Pricing status code: ' || x_line_tbl (I).status_code);
DBMS_OUTPUT.
PUT_LINE ('Pricing status text: ' || x_line_tbl (I).status_text);
EXIT WHEN I = x_line_tbl.LAST;
I := x_line_tbl.NEXT (I);
END LOOP;
END IF;
DBMS_OUTPUT.
PUT_LINE ('-----------Pricing Attributes Information-------------');
I := x_line_detail_attr_tbl.FIRST;
IF I IS NOT NULL
THEN
LOOP
DBMS_OUTPUT.
PUT_LINE (
'Line detail Index '
|| x_line_detail_attr_tbl (I).line_detail_index);
DBMS_OUTPUT.
PUT_LINE ('Context ' || x_line_detail_attr_tbl (I).pricing_context);
DBMS_OUTPUT.
PUT_LINE (
'Attribute ' || x_line_detail_attr_tbl (I).pricing_attribute);
DBMS_OUTPUT.
PUT_LINE (
'Value ' || x_line_detail_attr_tbl (I).pricing_attr_value_from);
DBMS_OUTPUT.
PUT_LINE ('Status Code ' || x_line_detail_attr_tbl (I).status_code);
DBMS_OUTPUT.
PUT_LINE ('---------------------------------------------------');
EXIT WHEN I = x_line_detail_attr_tbl.LAST;
I := x_line_detail_attr_tbl.NEXT (I);
END LOOP;
END IF;
DBMS_OUTPUT.
PUT_LINE ('-----------Qualifier Attributes Information-------------');
I := x_line_detail_qual_tbl.FIRST;
IF I IS NOT NULL
THEN
LOOP
DBMS_OUTPUT.
PUT_LINE (
'Line Detail Index '
|| x_line_detail_qual_tbl (I).line_detail_index);
DBMS_OUTPUT.
PUT_LINE (
'Context ' || x_line_detail_qual_tbl (I).qualifier_context);
DBMS_OUTPUT.
PUT_LINE (
'Attribute ' || x_line_detail_qual_tbl (I).qualifier_attribute);
DBMS_OUTPUT.
PUT_LINE (
'Value ' || x_line_detail_qual_tbl (I).qualifier_attr_value_from);
DBMS_OUTPUT.
PUT_LINE ('Status Code ' || x_line_detail_qual_tbl (I).status_code);
DBMS_OUTPUT.
PUT_LINE ('---------------------------------------------------');
EXIT WHEN I = x_line_detail_qual_tbl.LAST;
I := x_line_detail_qual_tbl.NEXT (I);
END LOOP;
END IF;
I := x_line_detail_tbl.FIRST;
DBMS_OUTPUT.
PUT_LINE ('------------Price List/Discount Information------------');
IF I IS NOT NULL
THEN
LOOP
L_MOD_NAME := '';
DBMS_OUTPUT.
PUT_LINE ('Line Index: ' || x_line_detail_tbl (I).line_index);
DBMS_OUTPUT.
PUT_LINE (
'Line Detail Index: ' || x_line_detail_tbl (I).line_detail_index);
DBMS_OUTPUT.
PUT_LINE (
'Line Detail Type:'
|| x_line_detail_tbl (I).line_detail_type_code);
DBMS_OUTPUT.
PUT_LINE (
'List Header Id: ' || x_line_detail_tbl (I).list_header_id);
DBMS_OUTPUT.
PUT_LINE ('List Line Id: ' || x_line_detail_tbl (I).list_line_id);
DBMS_OUTPUT.
PUT_LINE (
'List Line Type Code: '
|| x_line_detail_tbl (I).list_line_type_code);
DBMS_OUTPUT.
PUT_LINE (
'Adjustment Amount : ' || x_line_detail_tbl (I).adjustment_amount);
DBMS_OUTPUT.
PUT_LINE ('Line Quantity : ' || x_line_detail_tbl (I).line_quantity);
DBMS_OUTPUT.
PUT_LINE (
'Operand Calculation Code: '
|| x_line_detail_tbl (I).Operand_calculation_code);
DBMS_OUTPUT.
PUT_LINE ('Operand value: ' || x_line_detail_tbl (I).operand_value);
DBMS_OUTPUT.
PUT_LINE (
'Automatic Flag: ' || x_line_detail_tbl (I).automatic_flag);
DBMS_OUTPUT.
PUT_LINE ('Override Flag: ' || x_line_detail_tbl (I).override_flag);
DBMS_OUTPUT.
PUT_LINE ('status_code: ' || x_line_detail_tbl (I).status_code);
DBMS_OUTPUT.
PUT_LINE ('status text: ' || x_line_detail_tbl (I).status_text);
DBMS_OUTPUT.PUT_LINE ('-------------------------------------------');
EXIT WHEN I = x_line_detail_tbl.LAST;
BEGIN
SELECT NAME
INTO L_MOD_NAME
FROM QP_LIST_HEADERS_ALL
WHERE LIST_HEADER_ID = x_line_detail_tbl (I).list_header_id
AND x_line_detail_tbl (I).list_line_type_code = 'PLL'
AND x_line_detail_tbl (I).adjustment_amount IS NOT NULL;
L_MODIFIER := L_MODIFIER || '~' || L_MOD_NAME;
EXCEPTION
WHEN OTHERS
THEN
NULL;
END;
IF x_line_detail_tbl (I).list_line_type_code = 'PLL'
AND x_line_detail_tbl (I).adjustment_amount IS NOT NULL
THEN
L_ADJUSTMENT_AMOUNT :=
L_ADJUSTMENT_AMOUNT
|| '~'
|| x_line_detail_tbl (I).adjustment_amount;
END IF;
I := x_line_detail_tbl.NEXT (I);
END LOOP;
END IF;
SELECT line_unit_price, order_uom_selling_price
INTO l_unit_price, l_selling_price
FROM qp_preq_lines_tmp
WHERE pricing_status_code = Qp_Preq_Pub.g_status_updated
ORDER BY line_id;
DBMS_OUTPUT.PUT_LINE ('Unit Price := ' || l_unit_price); --x_line_tbl(1).UNIT_PRICE );
DBMS_OUTPUT.PUT_LINE ('Selling Price := ' || l_selling_price); ---x_line_tbl(1).LINE_UNIT_PRICE );
DBMS_OUTPUT.PUT_LINE ('L_MODIFIER: ' || L_MODIFIER);
DBMS_OUTPUT.PUT_LINE ('L_ADJUSTMENT_AMOUNT: ' || L_ADJUSTMENT_AMOUNT);
DBMS_OUTPUT.
PUT_LINE (
'--------------Related Lines Information for Price Breaks/Service Items---------------');
I := x_related_lines_tbl.FIRST;
IF I IS NOT NULL
THEN
LOOP
DBMS_OUTPUT.
PUT_LINE ('Line Index :' || x_related_lines_tbl (I).line_index);
DBMS_OUTPUT.
PUT_LINE (
'Line Detail Index: '
|| x_related_lines_tbl (I).LINE_DETAIL_INDEX);
DBMS_OUTPUT.
PUT_LINE (
'Relationship Type Code: '
|| x_related_lines_tbl (I).relationship_type_code);
DBMS_OUTPUT.
PUT_LINE (
'Related Line Index: '
|| x_related_lines_tbl (I).RELATED_LINE_INDEX);
DBMS_OUTPUT.
PUT_LINE (
'Related Line Detail Index: '
|| x_related_lines_tbl (I).related_line_detail_index);
DBMS_OUTPUT.
PUT_LINE ('Status Code: ' || x_related_lines_tbl (I).STATUS_CODE);
EXIT WHEN I = x_related_lines_tbl.LAST;
I := x_related_lines_tbl.NEXT (I);
END LOOP;
END IF;
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.
PUT_LINE ('SQLERRM' || SQLERRM);
END;
Kindly provide sugession if I miss any thing.
Regards,
Akil
Edited by: 1004537 on May 9, 2013 7:20 AM
Edited by: 1004537 on May 9, 2013 7:20 AM

How to check itab1 with copy of itab by line wise?

Hi Friends,
I have two internal tables itab and jtab.
jtab is a copy of itab with rows 10 and column wise 12.
Both have same records since jtab is a copy of itab.
My requirement is (at the end of the program if i update new reocrd to itab) I want to chek the itab line wise with jtab.
I know we can do it with loop one by one with field. Is there any other way I can check the whole line of 12 fields with itab record.
Ex:If lineitem = 2 of jtab with lineitem = 2 of itab.
itab have 12 fields in that 2nd line item of vendor name(ex) is XYZ and 2nd line item of jtab is ABC.I have to check the whole line item.
Please advise.
thanks & regards
Sankar.

if wa = wa1.
endif.

Item does not match schdule line ( program error ) message no . V1427

*Item does not match schdule line ( program error ) message no . V1427 .* This is the message I am getting when I am trying to display a quotation through VA23 . From here system exits the transaction .
As per my observation , when I compared VBAP and VBEP tables, there are 2 items in VBEP table with schedule lines but the same items are not present in VBAP table. User says he tried to delete these items because there is no quanity , Inspite of that these items appear in VBEP table .
The document is a reservation document where in schedule line category does TOR and availability check.
I checked various related notes - 442831 , 401463 , 389687 etc . These are quite old notes and I am in release ECC 5.0 .
What is the best way as this doc has nearly 30 items and nearly all of them have quanity confirmed .
Please provide your valuble inputs ...
Regards
Raghav..

Nitin,
Below are the steps to check
Transaction SE18
Definition name: BADI_SD_SALES
Menu: Implementation -> Overview
double-click on implementation: IM_CORE_CHECK
Now you will get an overview on the methods.
check whether implementation IM_CORE_CHECK is active or not.
If not Press the change button and activate
looking at the your system pack level this should be active. If it is active then the inconsistency must be modified directly at database level through Z report.
Ramesh

Cash Discount at header is not reducing line item price

Hi Experts,
While putting cash discount at header, it is not reducing price of the my total line item. I am having total line item price = 100 USD (10 USD * 10 Qty). I am entering 10 USD as cash discount at header. It is not reducing total line item price to 90. Also in my accounting document 10 USD (cash discount) is going to my tax account.
Please advise.
Regards,
Kamal

Hi,
The cash discount case will only be applicable in connection with terms of payment. You will have to define your customized discount condition type in M/06 and assign it to your PO pricing schema via M/08 transaction. Make sure it shall not be set as 'Statistics' condition type.
Cheers,
HT

Customer wise Item Wise Price List History Report

Hello Experts,
My Customer Wants the Customer wise Item Wise Price List History Report
Dixit Patel

Dear Dixit,
SELECT CardCode,ItemCode,T0.DocDate,DocNum,Price FROM RDR1 T1
INNER JOIN ORDR T0 ON T1.DocEntry=T0.DocEntry
ORDER BY CardCode,ItemCode,T0.DocDate DESC
Is this will be enough?
Best Regards,
Hendry Wijaya

Schdule line data source

hi all,
what is purpose of schedule line data source.
pls explain to me.

Hi,
Hi schdule line data source extracts the data at the schedule line level.
basically the data in the orders deliveries or purchase are didvide in the following flow.
order->item->schedule line.
So a particular order can contain several item and in turn an item can contain different schedule lines.
A material is checked for the abailabilty when requested through a purchase order or delivered through a delievry order.
So if for example 100 qty is order and only 10 is available then 10 is delivered with that delievry date and 90 is left and then in the next turm 90 is delievred if 90 is available next time.
So now your item will have these two entries as schedule line.
This two entries cannot be brought at the item extractors as it is more granular then item
therefore it is brough thorugh another extarctor which gives in how many parts a particlaur item has been delievered.
Hope it clears
Thanks

Sales Order line item Price after Discount

Hi all
How to get the line item price after discount in Sales Order Query?
Kedalene

Hi Kedalene,
Please check below Query.
SELECT T0.[DocNum], T0.[DocDate], T0.[CardName], T1.[Dscription], T1.[Quantity], T1.[Price] as Price_After_Discount, T1.[PriceBefDi] As Price_Before_Discount,T1.[DiscPrcnt], T1.[LineTotal] FROM ORDR T0 INNER JOIN RDR1 T1 ON T0.[DocEntry] = T1.[DocEntry]
Hope this help
Regards:::::
Atul Chakraborty

Approval template for line item price variation

Any recommendation on how to managed price variations at a line item level with using approval templates? The approval templates currently only allow for TOTAL document differences.
A senario as follows
1. Purchase order with line item price created
2. GRNI created (and unit price changed)
3. AP invoice created - AP approval template kicks in advising that there is a price discrepancy at a line item level between the Base and target documents.

Hi!
You can achive this via Stored Procedure.
Approval Procedure will not work for Row Level.

WIP configuration - GL for WIP - Product Line wise

Dear All
Is there a way to maintain Fl accounts product line wise to configure WIP. i.e.: we have 4 different production line for different products. Currently we assigned common GL account against cost elements.
Thanks
MKJ

Hi
If you are asking for Separate GL Accounts for Posting in FI - Its not possible
In CO, you can manage separate secondary cost elements (Catg 31) by creating Separate Line ID and RA Key as per your Product Line
In BADI Workorder_update, you can write a logic to default an RA Key in the Prod order depending on prod line
br, Ajay M

Error in adding List Line in Price Lists setup form

Hi Gurus,
users are facing below error message while they try to add new items in the list lines on the "Price List Setup" Screen.
Navigation - Order Management Super User --> Pricing --> Price Lists --> Price List Setup. Query the required price list. go to the list lines and add new line. While saving the new line below error message encountered.
Error ORA-00001: unique constraint (QP.QP_LIST_LINES_U1) violated in Package QP_Price_List_Line_Util Procedure Insert_Row
QP_LIST_LINES_U1 is a unique index with below script -
CREATE UNIQUE INDEX QP.QP_LIST_LINES_U1 ON QP.QP_LIST_LINES
(LIST_HEADER_ID, LIST_LINE_NO)
LOGGING
TABLESPACE APPS_TS_TX_IDX
PCTFREE 10
INITRANS 11
MAXTRANS 255
STORAGE (
INITIAL 128K
NEXT 128K
MINEXTENTS 1
MAXEXTENTS UNLIMITED
PCTINCREASE 0
BUFFER_POOL DEFAULT
NOPARALLEL;
N:B:- when we try to do the same thing in our test instance which is last refreshed from production 2 weeks ago, we are able to add new line and save without the error message. seems like some data corruption has occured in production recently. please help on how to diagnostic the corruption. its quite critical issue now from bussiness point of view.
Regards,
Samir Kumar Das

Hi Samir,
Please follow the below metalink notes...
Cannot Add Item To Price List as it Errors With ORA-00001: unique constraint (QP.QP_LIST_LINES_U1) violated in Package QP_Price_List_line_Util Procedures Insert_Row [ID 466320.1]
Thanks
-Arif.

Modifying line item price in Purchase Order

Hi guys,
Need your help regarding pricing modification in purchase order. I know the below explanation is quite long enough, but still if you can look into it and put some thoughts:
The price picked for a line item from PIR, needs to be modified depending on total price.
Say for example, in a PO there are two line items
Mat1     10PC 10 usd/1pc
Mat2     10PC 20 usd/1pc
so total price for PO goes as 300 usd.
Now, if PO price exceeds 250 usd a different price needs to be picked from a custom table for line items. Say it should now become 8 usd/1PC and 18 usd/1PC for Mat1 and Mat2 respectively.
So, after entering PO items if the user presses the 'check' button, new price should be picked, as per the above example the new lines should be shown as
Mat1     10PC 8 USD/1PC
Mat2     10PC 18 USD/1PC
so total price for PO goes as 260 USD.
Hope I've made you clear about the requirement.
Now, what we are able to do so far is:
We have used the 'check' method BADI 'me_process_po_cust'. And we are calculating the total price and changing the item conditions.
But it's not reflecting on the me21n screen even after execution of the 'check' method successfully.
It still shows the line items as
Mat1     10PC 10 USD/1PC
Mat2     10PC 20 USD/1PC
But, now if we make any changes in the line items (say we add the requisitioner name) and hit ENTER the changed prices are reflected. And the items become
Mat1     10PC 8 USD/1PC
Mat2     10PC 18U SD/1PC
This is a thing we are stuck into.
Please express if you have any idea how to come out of this issue.
Thanks in advance.
Anupam

Hi Anupam,
Flow Logic of the screen.
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
LOOP AT ITAB WITH CONTROL TABC.
ENDLOOP.
PROCESS AFTER INPUT.
LOOP AT ITAB.
    MODULE READ_TABLE_CONTROL.
ENDLOOP.
Write the read_table_control module like below
MODULE read_table_control INPUT.
   MODIFY itab INDEX tabc-current_line.
   "The above will update the entered data on table control
ENDMODULE.
Kindly check if this table control gets updated in PAI or not.... if not... try to find an exit where this can be done on PAI.....
Regards,
Deeba

Document line with price zero in SBO 2007 A

Hi All
We have a DI API AddOn that occationally has to create a document line with the total price of zero.
In SBO 2005 A we just set SBODocument.Lines.Price = 0, but that doesn't work in SBO 2007 A.
In 2007A when we set SBODocument.Lines.Price = 0 it takes the price from the pricelist as though we had not entered a price at all. If we set SBODocument.Lines.Price to something else that zero it does correctly take the price we entered.
We have tried to set SBODocument.Lines.UnitPrice or SBODocument.Lines.LineTotal to zero in stead but it gives the same result.
Any help appriciated.
Rgds
Jesper Carstensen

Sorry, my mistake.
The solution WAS indeed to set SBODocument.Lines.UnitPrice = 0
Rgds
Jesper Carstensen

Each PO Line Item price should be as per the scale in contract?

Hi
I have a PO with 2 line items, both line items are for the same material.As I order 2 different quantities, I get 2 different prices, i.e. per line item. (As per the Scales Maintained in the contract)
However once I save the PO, and then display the PO, the price is taken for the total quantity. Is there any way that I can have 2 different prices for both materials in the same PO?
This behaviour has changed in the last 1 month only.
Earlier in our SAP system each line item had different price as the scale for the ordered quantity in that line item.
We though it could be due to Group Condition checked in the Condition Type, but that check has been in our system since long time, hence it cannot be the reason.
Thanks in Advance!

Yes... this is a standard behavior..
You can do one option...
When PO fetch the price from contract, then copy the price and enter it manually again, then PO can remember the price after save..
Check the similar discussion PO Price update issue

AFS - SCHDULE LINE WISE PRICE

Similar Messages

Maybe you are looking for