Unit selling price is not updating

Hi
I am updating unit selling price of an item using API.
code:
v_line_tbl (1).request_date := SYSDATE;
v_line_tbl (1).unit_selling_price := 299;
in the above code request_date is updating to sysdate but selling price is not updating.
how to do this?
Thanks

The CALCULATE_PRICE_FLAG is in the OE_ORDER_LINES_ALL table. This setting could override determines pricing engine calls which could be overriding your update.
Values -
Calculate Price (Y)
Partial Price (P)
Freeze Price (N)
Thank you,
Debbie

Similar Messages

Need Sample API code to update Quote Line level Unit Selling Price alone.

Hi,
i want to update Unit Selling Price alone using API, can any one have sample code to do that.
ASO_QUOTE_PUB.Update_Quote_Line
Thanks!
Kishore

Hi,
please find the code below for ASO Quote Line Update. Here this sample only shows an DFF Attribute update. You can try the same for the Unit Selling price Update.
DECLARE
l_Api_Version_Number NUMBER;
l_Init_Msg_List VARCHAR2(1000);
l_Commit VARCHAR2(1000);
l_Validation_Level      NUMBER;
l_Qte_Header_Rec ASO_QUOTE_PUB.Qte_Header_Rec_Type;
l_Qte_Line_Rec ASO_QUOTE_PUB.Qte_Line_Rec_Type;
l_Control_Rec ASO_QUOTE_PUB.Control_rec_Type;
l_Qte_Line_Dtl_TBL ASO_QUOTE_PUB.Qte_Line_Dtl_tbl_Type;
l_Line_Attribs_Ext_Tbl ASO_QUOTE_PUB.Line_Attribs_Ext_Tbl_type;
l_Payment_Tbl ASO_QUOTE_PUB.Payment_Tbl_Type;
l_Price_Adj_Tbl ASO_QUOTE_PUB.Price_Adj_Tbl_Type;
l_Price_Attributes_Tbl ASO_QUOTE_PUB.Price_Attributes_Tbl_Type;
l_Price_Adj_Attr_Tbl ASO_QUOTE_PUB.Price_Adj_Attr_Tbl_Type;
l_Shipment_Tbl ASO_QUOTE_PUB.Shipment_Tbl_Type;
l_Tax_Detail_Tbl ASO_QUOTE_PUB.Tax_Detail_Tbl_Type;
l_Freight_Charge_Tbl ASO_QUOTE_PUB.Freight_Charge_Tbl_Type;
l_Sales_Credit_Tbl ASO_QUOTE_PUB.Sales_Credit_Tbl_Type;
l_Quote_Party_Tbl ASO_QUOTE_PUB.Quote_Party_Tbl_Type;
l_Update_Header_Flag VARCHAR2(100);
X_Qte_Line_Rec ASO_QUOTE_PUB.Qte_Line_Rec_Type;
X_Qte_Line_Dtl_TBL ASO_QUOTE_PUB.Qte_Line_Dtl_TBL_Type;
X_Line_Attribs_Ext_Tbl ASO_QUOTE_PUB.Line_Attribs_Ext_Tbl_type;
X_Payment_Tbl ASO_QUOTE_PUB.Payment_Tbl_Type;
X_Price_Adj_Tbl ASO_QUOTE_PUB.Price_Adj_Tbl_Type;
X_Price_Attributes_Tbl ASO_QUOTE_PUB.Price_Attributes_Tbl_Type;
X_Price_Adj_Attr_Tbl ASO_QUOTE_PUB.Price_Adj_Attr_Tbl_Type;
X_Shipment_Tbl ASO_QUOTE_PUB.Shipment_Tbl_Type;
X_Tax_Detail_Tbl ASO_QUOTE_PUB.Tax_Detail_Tbl_Type;
X_Freight_Charge_Tbl ASO_QUOTE_PUB.Freight_Charge_Tbl_Type;
X_Sales_Credit_Tbl ASO_QUOTE_PUB.Sales_Credit_Tbl_Type;
X_Quote_Party_Tbl ASO_QUOTE_PUB.Quote_Party_Tbl_Type;
lX_Return_Status VARCHAR2(1000);
lX_Msg_Count NUMBER;
lX_Msg_Data VARCHAR2(1000);
     lc_last_update_date date;
     l_file varchar2(2000);
     CURSOR c_quote(c_qte_header_id NUMBER) IS
     SELECT last_update_date
     FROM ASO_QUOTE_HEADERS_ALL
     WHERE quote_header_id = c_qte_header_id;
BEGIN
     BEGIN
     MO_GLOBAL.init('SQLAP');
     MO_GLOBAL.set_policy_context('S',83);
     fnd_global.apps_initialize(1175,50689,280);
     END;
     OPEN c_quote(l_qte_header_rec.quote_header_id);
     FETCH c_quote INTO lc_last_update_date;
     CLOSE c_quote;
     aso_debug_pub.SetDebugLevel(10);
aso_debug_pub.Initialize;
l_file:= ASO_DEBUG_PUB.Set_Debug_Mode('FILE');
aso_debug_pub.debug_on;
aso_debug_pub.add('Update Quote',1, 'Y');
dbms_output.put_line('File :'||l_file);
dbms_output.put_line( to_char(sysdate, 'mm/dd/yyyy:hh24:SS') );
     l_qte_header_rec.quote_header_id := 24649;
     l_qte_header_rec.last_update_date := lc_last_update_date;
     l_control_rec.last_update_date := lc_last_update_date;
     l_qte_line_rec.quote_header_id := 24649;
     l_qte_line_rec.quote_line_id := 27712;
     l_qte_line_rec.attribute12 := 1000;
     ASO_QUOTE_PUB.Update_Quote_Line(
P_Api_Version_Number => '1.0',
P_Init_Msg_List =>     l_Init_Msg_List,
P_Commit =>     l_Commit,
P_Qte_Line_Rec =>     l_Qte_Line_Rec,
P_Control_Rec =>     l_Control_Rec,
P_Qte_Line_Dtl_Tbl =>     l_Qte_Line_Dtl_Tbl,
P_Line_Attribs_Ext_Tbl =>     l_Line_Attribs_Ext_Tbl,
P_Payment_Tbl =>     l_Payment_Tbl,
P_Price_Adj_Tbl =>     l_Price_Adj_Tbl,
P_Price_Attributes_Tbl =>     l_Price_Attributes_Tbl,
P_Price_Adj_Attr_Tbl =>     l_Price_Adj_Attr_Tbl,
P_Shipment_Tbl =>     l_Shipment_Tbl,
P_Tax_Detail_Tbl =>     l_Tax_Detail_Tbl,
P_Freight_Charge_Tbl =>     l_Freight_Charge_Tbl,
P_Update_Header_Flag =>     l_Update_Header_Flag,
X_Qte_Line_Rec =>     X_Qte_Line_Rec,
X_Qte_Line_Dtl_Tbl =>     X_Qte_Line_Dtl_Tbl,
X_Line_Attribs_Ext_Tbl =>     X_Line_Attribs_Ext_Tbl,
X_Payment_Tbl =>     X_Payment_Tbl,
X_Price_Adj_Tbl =>     X_Price_Adj_Tbl,
X_Price_Attributes_Tbl =>     X_Price_Attributes_Tbl,
X_Price_Adj_Attr_Tbl =>     X_Price_Adj_Attr_Tbl,
X_Shipment_Tbl =>     X_Shipment_Tbl,
X_Tax_Detail_Tbl =>     X_Tax_Detail_Tbl,
X_Freight_Charge_Tbl =>     X_Freight_Charge_Tbl,
X_Return_Status =>     lX_Return_Status,
X_Msg_Count =>     lX_Msg_Count,
X_Msg_Data =>     lX_Msg_Data
fnd_msg_pub.count_and_get( p_encoded => 'F'
, p_count => lx_msg_count
, p_data => lx_msg_data);
dbms_output.put_line('no. of FND messages :'||lx_msg_count);
for k in 1 .. lx_msg_count loop
lx_msg_data := fnd_msg_pub.get(
p_msg_index => k,
p_encoded => 'F');
dbms_output.put_line('Error msg: '||substr(lx_msg_data,1,240));
end loop;
dbms_output.put_line(lx_return_status);
dbms_output.put_line(to_char(lx_msg_count));
dbms_output.put_line(lx_msg_data);
dbms_output.put_line('end');
END;
COMMIT;
Thanks
Sunil Devulapally
Edited by: user13150483 on 05-Jan-2012 10:59

Manual override option for Unit selling price in Order line level.

In OM R-12
Our client wants manual override option for Unit selling price in Order line level.
But there is no solution available to fulfill this requirment. To be able to manually override the price on a Sales Order line you
must have defined a manual modifier that qualifies for the Sales Order line in question. Without a suitable manual modifier the price cannot be changed.
This is current standard functionality.
Anybody can give some suggestion/workaround to override selling price in Order header level without using the modifiers.
regards,

Hi Kashif,
I'm finding it little difficult to buy Oracle Support's feedback with regards to R12 functionality for direct List Price update without using any modifier (manual or whatever). After all it is Oracle's product and they should know better. But test results in Solution Beacon's Vision 12.0.6 instance (http://www.solutionbeacon.com/tools_r12vision.htm) and documentation updates in R12 (R12.0.4) OM user guide & implementation manuals potray a different picture.
After your last post, I did a test in Solution Beacon's Vision 12.0.6 instance with following details:
OM: List Price Override Privilege = "Unlimited Access" at user level
OM: Discounting Privileges = "None" at user level
No manual modifiers defined and Order status = "Entered"
I could display the "List Price" field from folder under Line Items >> Main tab, override the list price to a new value and save. The unit selling price showed the new value based on updated List Price as soon as I tabbed out of the list price field after overriding. After saving it showed the new selling price. _Please note that under Line Items >> Pricing tab there is another "List Price" field and that is not editable_. For such overrides "View Adjustments" (from Line >> Actions) will not show any adjustment details as it is a direct update of list price.
Also please note that, if "Enforce List Price" checkbox is selected for the order type, the list price cannot be overridden even if the profile option is set to "Unlimited Access".
Document References:
Oracle® Order Management User's Guide
Release 12, Part No. B28099-03, September 2007 >> R12.0.4
Page No. 10-74
+Note: Note: If any order line for an order has the Calculate Price Flag value equal to Partial Price or Freeze Price new order level adjustments will not be applied or allowed to be overridden. _The profile option OM: List Price Override Privilege controls your ability to override the unit list price. If you have this profile set to Unlimited, you may modify the unit list price by editing the current value displayed_. The original list price is saved in a hidden folder field, so you can display it if necessary+.
Page No. 10-94
User Procedures
_A new profile option, OM: List Price Override Privilege controls whether or not you can update the List Price_. It is enabled and updated at the application, responsibility and user level. It is not user visible and updatable. The values include+:
- View Only: This is the default value. If set to this value, the current behavior is retained, which means unit list price field is protected.
- Unlimited Privilege: If set to this value, you can override the unit list price field from the main tab and immediately see selling price adjusted accordingly.
To use Override List Price:
+1. Navigate to the Sales Orders/Quick Sales Orders window.+
+2. Enter the header and line information, including the ordered item and quantity, then tab to the next field. The Selling Price and List Price display+.
+3. If the profile is set to Unlimited Privilege, you can enter a new list price in the List Price field. You can either proceed to the next line or save your work+.
+4. You can see the new, entered list price, and if there are automatic discounts applied, they will be based on the new list price+.
+5. If the folder has been modified to show the Original List Price, the original list price displays+.
+6. To change the List Price again, go to the list price field and enter a new value, replacing a previously entered value. If Audit Trail is enabled for List Price and a reason is required, a window appears to enter a reason and optional comments+.
Note: Subsequent overrides of the List Price, after the order line is saved, can be captured by Audit Trail, depending on the setup of Audit Trail (entered or booked state) and any processing constraints that have been set up.
In the OM Implementation Manual also there are notes related to this.
OM Implementation Manual
Release 12, Part No. B25975-03, September 2007 >> R12.0.4
You can refer to page no. 2-59, C-4 etc.
Thanks
Supro

Unit Selling Price Override through PROCESS_ORDER API

Hi All,
I have this below requirement to be achieved through process_order API.
1. In the Order Oganizer UI, I open the Order Entry form.
2. Open the Lines tab
3. For the Unit Selling Price, I change the price manually and tab out.
4. Its gives me a LOV to select a Surcharge modifier.
5. I select one of the surcharge and click save.
6. The price is overridden and a manual price adjustment is created for the above selected surcharge.
This functionality I want to acieve through the PROCESS_ORDER API. Basically, I want to override the unit selling price and apply a surchage modifier. This should change the selling price and create a adjustement record for the above line.
Please let me know if anyone knows about this. That would help me.
Thanks,
Anand

Anand
I tested this in 12.0.4 vision and works. Also if you need to use update option if you are applying the same modifier more than once(not create), just like the way screen changes behave.
DECLARE
l_return_status VARCHAR2 (30);
x_msg_data VARCHAR2 (2000);
x_msg_count NUMBER;
l_adj_rec oe_order_pub.line_adj_rec_type;
l_adj_tbl oe_order_pub.line_adj_tbl_type;
l_x_header_rec oe_order_pub.header_rec_type;
l_x_header_adj_tbl oe_order_pub.header_adj_tbl_type;
l_x_header_scredit_tbl oe_order_pub.header_scredit_tbl_type;
l_x_line_tbl oe_order_pub.line_tbl_type;
l_x_line_adj_tbl oe_order_pub.line_adj_tbl_type;
l_x_line_scredit_tbl oe_order_pub.line_scredit_tbl_type;
l_x_lot_serial_tbl oe_order_pub.lot_serial_tbl_type;
l_x_action_request_tbl oe_order_pub.request_tbl_type;
l_x_header_price_att_tbl oe_order_pub.header_price_att_tbl_type;
l_x_header_adj_att_tbl oe_order_pub.header_adj_att_tbl_type;
l_x_header_adj_assoc_tbl oe_order_pub.header_adj_assoc_tbl_type;
l_x_line_price_att_tbl oe_order_pub.line_price_att_tbl_type;
l_x_line_adj_att_tbl oe_order_pub.line_adj_att_tbl_type;
l_x_line_adj_assoc_tbl oe_order_pub.line_adj_assoc_tbl_type;
l_list_line_type_code VARCHAR2 (30) := NULL;
l_list_line_id NUMBER;
l_x_header_payment_tbl oe_order_pub.header_payment_tbl_type;
l_x_line_payment_tbl oe_order_pub.line_payment_tbl_type;
l_prc_adj_request oe_order_pub.request_tbl_type;
l_prc_adj_index NUMBER := 1;
l_price_adj_id NUMBER;
v_msg_index_out NUMBER;
x_header_rec_type oe_order_pub.header_rec_type;
x_header_val_rec_type oe_order_pub.header_val_rec_type;
x_header_adj_tbl_type oe_order_pub.header_adj_tbl_type;
x_header_adj_val_tbl_type oe_order_pub.header_adj_val_tbl_type;
x_header_price_att_tbl_type oe_order_pub.header_price_att_tbl_type;
x_header_adj_att_tbl_type oe_order_pub.header_adj_att_tbl_type;
x_header_adj_assoc_tbl_type oe_order_pub.header_adj_assoc_tbl_type;
x_header_scredit_tbl_type oe_order_pub.header_scredit_tbl_type;
x_header_scredit_val_tbl_type oe_order_pub.header_scredit_val_tbl_type;
x_line_tbl_type oe_order_pub.line_tbl_type;
x_line_val_tbl_type oe_order_pub.line_val_tbl_type;
x_line_adj_tbl_type oe_order_pub.line_adj_tbl_type;
x_line_adj_val_tbl_type oe_order_pub.line_adj_val_tbl_type;
x_line_price_att_tbl_type oe_order_pub.line_price_att_tbl_type;
x_line_adj_att_tbl_type oe_order_pub.line_adj_att_tbl_type;
x_line_adj_assoc_tbl_type oe_order_pub.line_adj_assoc_tbl_type;
x_line_scredit_tbl_type oe_order_pub.line_scredit_tbl_type;
x_line_scredit_val_tbl_type oe_order_pub.line_scredit_val_tbl_type;
x_lot_serial_tbl_type oe_order_pub.lot_serial_tbl_type;
x_lot_serial_val_tbl_type oe_order_pub.lot_serial_val_tbl_type;
x_request_tbl_type oe_order_pub.request_tbl_type;
x_header_payment_tbl_type oe_order_pub.header_payment_tbl_type;
x_header_payment_val_tbl_type oe_order_pub.header_payment_val_tbl_type;
x_line_payment_tbl_type oe_order_pub.line_payment_tbl_type;
x_line_payment_val_tbl_type oe_order_pub.line_payment_val_tbl_type;
l_control_rec oe_globals.control_rec_type;
BEGIN
fnd_global.apps_initialize (1005902, 21623, 660);
mo_global.set_policy_context ('S', 204);
l_x_line_tbl (1).line_id := 319799;
l_x_line_tbl (1).header_id := 155008;
l_adj_rec := oe_order_pub.g_miss_line_adj_rec;
l_adj_rec.price_adjustment_id := fnd_api.g_miss_num;
l_adj_rec.list_header_id := 8988; --Modifier id
l_adj_rec.list_line_id := 16596; --Modifier line id
l_adj_rec.automatic_flag := 'N';
l_adj_rec.list_line_type_code := 'DIS'; --Change this is it is surcharge
l_adj_rec.arithmetic_operator := 'AMT'; --Percentage or amount
l_adj_rec.operand := 10; --How much?
l_adj_rec.operation := oe_globals.g_opr_create;
l_adj_rec.line_index := 1;
l_adj_rec.update_allowed := 'Y';
l_adj_rec.applied_flag := 'Y'; --this is required to change the price of the line
l_adj_rec.change_reason_code := 'MANUAL';
l_adj_rec.change_reason_text := 'Manually applied adjustments';
l_adj_tbl (1) := l_adj_rec;
l_control_rec.process_entity := oe_globals.g_entity_line_adj;
l_control_rec.process := TRUE;
oe_order_pub.process_order (p_api_version_number => 1.0
, x_return_status => l_return_status
, x_msg_count => x_msg_count
, x_msg_data => x_msg_data
, p_header_rec => l_x_header_rec
, p_header_adj_tbl => l_x_header_adj_tbl
, p_header_scredit_tbl => l_x_header_scredit_tbl
, p_header_payment_tbl => l_x_header_payment_tbl
, p_line_tbl => l_x_line_tbl
, p_line_adj_tbl => l_adj_tbl
, p_line_scredit_tbl => l_x_line_scredit_tbl
, p_line_payment_tbl => l_x_line_payment_tbl
, p_lot_serial_tbl => l_x_lot_serial_tbl
, p_action_request_tbl => l_prc_adj_request
, p_header_price_att_tbl => l_x_header_price_att_tbl
, p_header_adj_att_tbl => l_x_header_adj_att_tbl
, p_header_adj_assoc_tbl => l_x_header_adj_assoc_tbl
, p_line_price_att_tbl => l_x_line_price_att_tbl
, p_line_adj_att_tbl => l_x_line_adj_att_tbl
, p_line_adj_assoc_tbl => l_x_line_adj_assoc_tbl
, x_header_rec => x_header_rec_type
, x_header_val_rec => x_header_val_rec_type
, x_header_adj_tbl => x_header_adj_tbl_type
, x_header_adj_val_tbl => x_header_adj_val_tbl_type
, x_header_price_att_tbl => x_header_price_att_tbl_type
, x_header_adj_att_tbl => x_header_adj_att_tbl_type
, x_header_adj_assoc_tbl => x_header_adj_assoc_tbl_type
, x_header_scredit_tbl => x_header_scredit_tbl_type
, x_header_scredit_val_tbl => x_header_scredit_val_tbl_type
, x_header_payment_tbl => x_header_payment_tbl_type
, x_header_payment_val_tbl => x_header_payment_val_tbl_type
, x_line_tbl => x_line_tbl_type
, x_line_val_tbl => x_line_val_tbl_type
, x_line_adj_tbl => x_line_adj_tbl_type
, x_line_adj_val_tbl => x_line_adj_val_tbl_type
, x_line_price_att_tbl => x_line_price_att_tbl_type
, x_line_adj_att_tbl => x_line_adj_att_tbl_type
, x_line_adj_assoc_tbl => x_line_adj_assoc_tbl_type
, x_line_scredit_tbl => x_line_scredit_tbl_type
, x_line_scredit_val_tbl => x_line_scredit_val_tbl_type
, x_line_payment_tbl => x_line_payment_tbl_type
, x_line_payment_val_tbl => x_line_payment_val_tbl_type
, x_lot_serial_tbl => x_lot_serial_tbl_type
, x_lot_serial_val_tbl => x_lot_serial_val_tbl_type
, x_action_request_tbl => x_request_tbl_type
DBMS_OUTPUT.put_line (l_return_status);
IF x_msg_count > 0
THEN
FOR v_index IN 1 .. x_msg_count
LOOP
oe_msg_pub.get (p_msg_index => v_index, p_encoded => 'F', p_data => x_msg_data, p_msg_index_out => v_msg_index_out);
x_msg_data := SUBSTR (x_msg_data, 1, 200);
DBMS_OUTPUT.put_line (x_msg_data);
DBMS_OUTPUT.put_line ('============================================================');
END LOOP;
END IF;
END;
Thanks
Nagamohan

Cannot manual adjustment unit selling price for Retrobill order

Dears,
I try formpersonalzation to set to update allowed and alterable,but still cannot update unit selling price?
there is a message:
Get_manual_adjustment#2 ORA-01403:no data found in Package oe_order_adj_pvt Procedure oe_line_adj.calulate_adjustments
Edited by: user6911393 on 2011/5/18 下午 9:00
Is there method can find the way to adjustment unit selling price manually fro Retrobill order?
Thank you very much!

Dears,
I try formpersonalzation to set to update allowed and alterable,but still cannot update unit selling price?
there is a message:
Get_manual_adjustment#2 ORA-01403:no data found in Package oe_order_adj_pvt Procedure oe_line_adj.calulate_adjustments
Edited by: user6911393 on 2011/5/18 下午 9:00
Is there method can find the way to adjustment unit selling price manually fro Retrobill order?
Thank you very much!

Sales Order - Unit Selling Price - Format Mask

Hi,
I want to change Format Mask of Unit Selling Price column on Sales Order Form. By using Forms Personalization it is not being done.
Please guide me how could I change its format mask from 5 decimal places to 2 decimal places.
Regards
Waqas Hassan

Hi Waqas,
In the define Currency form in GL setup, change the existing currency code precision to 2.
this should resolve your issue.
Make sure you logout and login back to recheck the issue.
General Ledger Super User-->Setup-->Currency-->Define.
Thanks
-Arif.

Inforecord Efective price is not Updating

Dear All
I have seen that the Effective price is not updating in Inforecord.
Kindly can I know why it is not updating?
I am Maintaining gross price condition
eg:ZM00 8:00/-
Result: Condition
Net Price: 8.00/-
Effective Price: 0.00/-
Regards
Chaitanya

System can only update Net or Effective price in the info record based on the customizing setting made.
sproMMPIR---Define price history.
Reg,
Deepak.
Edited by: deepak k b on Oct 30, 2008 7:22 AM

In material master standerd price field not updating in group currency

In material master accounting 1 tab, under price and values table. standerd price is not updating in group currency.
Can you sugest me how to resolve this issue

Hi,
As per My Knowledge,Wht ever currency is assigned as company code currency , tht will only be updated in Material Master as Per standard.
Thanks
Goutam

Last Purchase price is not updated

Hi
The last purchase price is not updated when posting a GRPO.
Any Ideas?
Its 2005 A SP01 PL48
Thanks
Franz

Check this WIKI
[Does a Goods Receipt PO update the Last Purchase Price List?|https://www.sdn.sap.com/irj/scn/wiki?path=/pages/viewpage.action&pageid=36438427]

Unit Selling Price in OM

Hi All,
I am new in OM. i just want to know when my user enter and modified unit selling price the message shows no list of values contain no entries, please advice how can i add its list or how can i use range of list against list.
Thanks

Dear All,
Please advice above issue
thanks

KEPM: Error msg if plan selling price is not maintained in VK11

Hi
I am using KEPM (COPA Planning tool)... I am entering my sales qty plan in KEPM and then valuating my plan sales qty to get Sales Revenue and Std cost for the Qty entered
If the std cost is not released, system gives an error based on my settings in the costing key.. Similarly, i want an error, if the selling price is not maintained for the material in VK11
In the IMG step "Define Valuation Strategy", I have assigned a SD Pricing Procedure for Valuation Strategy 002, Application Type "V" and Qty Field as ABSMG.... This Pricing procedure has a condition type named ZPLN
I entered sales plan for 10 materials but Plan Price is maintained in VK11 for ZPLN only for 9 materials... But system did not give any error and posted the sales revenue as zero for one material
I believe, currently I have not done any setting to issue any such error msg.. Can this be done??
Rgd, Ajay

Hi Kamala,
I would kindly ask you to check transaction OKEQN with your relevant planning version you are using in KEPM and where the above error occurs.
The system checks within derivation (where the error comes from) if the characteristic value is valid for a specific date set within the version (thus trans. OKEQN). If you have PRCTR '1000 102C511' not valid for the date set in the version within OKEQN, then this error message is justified, as the system realises that the PRCTR was not valid by that time.
Could you please check this? If the profit center is not valid for this date please adjust the date to a more recent one.
Best Regards,
Abhisek Patnaik

Unit Selling Price - Round Off

Hi All,
My requirement is to round off the unit selling price in Sales Order screen,
for example
Item AS16101 unit selling price is 12.99, while entering this item it should be 13, and saved to database as 13
Item AS16103 unit selling price is 12.40, while entering this item it should be 12
In WHEN VALIDATE RECORD, i used round function in form personlization, but in data base its saving the original value.
Any help on this.
Regards,
Max

In Personalization i have shown the value in messages, its showing correctly but when i enabled the custom events, after my message with value it showing PRE_QUERY trigger and saving the actual value.
Regards,
Max

Po prices is not updateing from inforecord

Guru
In Po when enter the Material & QTy & Price for that material is appering from info earlear now the problem is that Price is not picking from the last Po or Inforecord what must be problem. can u help me
Thanks
Sudhir

Hi
Price from inforecord has following steps
1) System will search for inforecord with valid price if it finds then the price will be pulled to PO
2) If there is inforecord and no valid price then system will look for last PO to pull the price.
3) If there is no info record then we have to enter the price manually.
In your case check the above prerequisites additon to that
1) If it is refering the last PO no then check whether the item is deleted or not.
2) If it is refereing the valid price in info record then check the validity period of the PIR.
Hope it helps.
Thanks/Karthik

Condition Record Price is not updated in Inforecord

Dear Experts
For a material , the price in the condituion record is maintained as below.But in the info record the value is showing as 14 , instead of 10 at present.
Validity from      Validity to      amount
3/2/2008     3/30/2011     14
3/31/2011     3/31/2011     10
4/1/2011     4/30/2011     14
5/1/2011     12/31/9999     10
please help how to get the condition record amount in Inforecord.
Thanks
chandra

Hi Chandra,
You should run the program "RM06INP0" with SE38 to update the latest prices in PIR.

Moving Avg Price is not updating in material master even after PO GR

Dear Gurus,
All of the materials in our company won't update the MAP even after the goods movement, and the Price control is set as 'V'.
Can anybody give me the idea how to track the IMG setting?
Jamie

Check the Mat type
Check Qty , value update is active .
Please give the above details
MAP works as below- Is your understanding correct ?. From then current stock position and Inv value , When you do GR for 30 qty at $300 / EA. MAP is moved from 300 to 301
Item
Qty
MAP
Stock Value
Current
       1,000
          300
       300,000
GR done for 30 Qty with price 330/Ea
       1,030
          301
       309,900

Unit selling price is not updating

Similar Messages

Maybe you are looking for