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.

Similar Messages

  • 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

  • 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!

  • 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

  • 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

  • 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

  • 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

  • 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

  • Internal Sales order not using Price List, Price Showing '0'

    Dear All,
    In the Internal Sales Order, why the list price is not used from the price list, why do we need to set the cost to get the price?
    Plz Clarify
    Thanks
    RSM

    Hi,
    Internal Sales order is nothing but selling the goods between 2 inventory organizations under same operating unit.
    This inventory Org is always within the operating Unit/Business group.
    Hence Item Cost defaults in the Item Cost and not the item Price.
    If Items are sold to external Customers then Item Prcie will be seen in the sales orders.
    iBut yes,upon customization we can still see Item Price in Sales Orders.
    Thanks
    -Arif.

  • Sales Order with zero price.

    Hi,
                                   I am creating sales order using the bapi  'BAPI_SALESORDER_CREATEFROMDAT2'  .For some materials we have condition type 'ZR00' and amount 0.00 per 1 unit. The problem is when i  create sales order, in item conditions it shows zero amount. How can I pass ZR00 price value through BAPI.?i.e i mean to oerwrite the value in Vk13.
    Regards,
    Vinsa.R

    HI Vinsar
    Make use of tables: ORDER_CONDITIONS_IN and ORDER_CONDITIONS_INX of the BAPI.
    Required paramters to be passed for the structures:
    <b>ORDER_CONDITIONS_IN</b>
    --ITM_NUMBER --> Item Number Eg: 000010
      COND_TYPE -> Condition Type(ZR00)
      COND_VALUE -> Amount
    <b>ORDER_CONDITIONS_INX</b>
    -- ITM_NUMBER -> Item Number(000010)
       COND_TYPE -> Cond Type(ZR00)
       UPDATEFLAG -> 'I'
       COND_VALUE -> 'X'
    Hope the info helps you.
    Kind Regards
    Eswar

  • Unable to update Sales order item level prices after invoice is created

    Dear All ,
    I have the following issue .
    When the sales order was created Z001 price was populated based on the condition record and  the order was in complete status  Then we created delivery and  invoice , the invoice had the same price as that of sales orders.
    Due to some code change related to pricing condition type - Z001 the prices in the sales order is changed to "ZERO" , when the sales order is opened in VA02 .
    We now corrected the code related to condition type - Z001  and now need to get back the on the line items . I wanted to Update prices by clicking on icon " Update" in the line item condition tab . I am not able to do it as the update icon is grayed out.
    Can any one help me with ideas for  fixing this issue  or any SAP utility  program .
    Looking forward to your help .
    Thanks and regards
    Veera

    Hi
    Without reversing invoice we can't update price and this is standard bevaior which is logical too. For your scenario I am wondering why would you want to change price for a line item or order which is alrady invoiced and posted to FI. What difference would it make to change price in sale order when this has already been posted in FI?
    Thank$

  • TEXT material in Sales Order - Unit of Measurement is blank

    We need to trigger a PR from a text item in sales order.
    Only problem we are facing is an error message saying "Enter Order Unit". But there is no value in F4 help for order unit. There is no permissible value for unit of measure in F4 help, as it is derived from material master.

    here is the exact requirement. We want to trigger a PR for procurement of services from a sales order. To trigger a PR for services and use service entry sheet for service confirmation we need to use item category D-Services in the PR and PO. Item category D does not allow a material to be entered as there will be no invetory tracking for this services. This is standard SAP property for item category D in the PR.
    So to trigger a PR only with a text line from a sales order you need to have a sales order line item only with the text and trigger a schedule line category with the order type NB, Item category as D and account assignment category as R.

  • Conversion factor error in sales order - Unit of measure

    Hi All,
    I have uploaded a sales item in to sales order with alternate UoM. The base unit of measure for that material is TO but i have uploaded with a alternate UoM KG. After that i have created project deliveries, invoices and accounted those invoices in last financial year and now i found that the conversion factor which is taken by the system was wrong.
    Instead of taking 1000 KG = 1 TO, system has taken 1KG = 1000 TO
    I have checked the material master there there is no alternate UoM has maintained.
    So now my concern is that
    1. how i can correct this conversion factor with out disturbing my old transactions.
    2. From where system is considered this conversion factor.
    Thanks & Regards,
    Bhadrarao.

    Check your conversion factors in your Unit of Measure configuration.  Transaction CUNI. Look at the unit of measures for Mass.
    Best Regards,
    Brian

  • 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

  • Sales order items without prices

    Dear experts,
    In default SAP, it is allowing to enter the items in sales orders which has not defined the price.
    We want to restrict this.
    What is the procedure for this?
    Thanks & Regards,
    Buddhika

    Hi,
    There are two ways of doing this.
    1.Maintain the condition type as "Required" in the pricing procedure.
    2.Maintain "Net value" as one of teh field in the incompletion log.Goto the T.Code "VOV8".Select your Order type.Details.
    Maintain the tick mark for the field "Incomplet. messages".
    Save.
    You can go for any one of these two options.
    Regards,
    Krishna.

Maybe you are looking for

  • Help me update playlist

    hey everyone! yeh everytime i hook up my usb cord it says " songs on the ipod cannot be updated because all the playlists selected for updating no longer exist." Yeah, i think i deleted it by accident. Can anyone tell me how to make another one? I st

  • How do i edit a name in message AIM buddy list

    my daughter shows one way to me in the AIM buddy list and another way to another one of my daughter's.  this leads me to believe that i can change the representation on my machine, but i cannot figure out how to do it.  how do i do it?

  • Issue in Date Format in Production

    Hi , I have written for Invoice Prining SAP SCript for F.62. In developemt and Quality system Date format is coming" MM/DD/YYYY" But in Production system it is showing "YYYY/DD/MM'. I have checked the Program aslo, which is also same in every server

  • Provider hosted app installed on SharePoint 2013 on premises is returning internal 500 error !

    Hello, I have deployed the basic provider hosted app on sharepoint 2013 on premises. However when I try to run the app, its throwing an error on following as mentioned in screen: It seems an authentication issue, would you please tell me how can I re

  • Inserting embeded PDF to database

    Hi, I have created a pdf file(a Form) that I would like to put on my website where I could enter the data inside the form's fields, and then save the pdf file to a database(mysql). If it can be done, how would I go about doing it? What I have tried s