Once attribute price selected, updating the price on the large product layout?

For my e-commerce site I need to setup, when a customer picks an attribute (such as 'Custom Artwork +£5.00') The price on the large product layout updates automatically before proceeding to the Shopping Cart for the price to update.
Is this achievable?

Hi Paul,
In case you still in need, (assuming you are using the attribute to pass the information to the cart) you can adjust the displayed price to reflect the selected option.
--not sure if this is the right way.. however it works.
---html--
<div id="catProdAttributes2_8090953" class="productAttributes">
     <div class="catProductAttributeGroup" data-productattributegroup="1851262">
          <div class="catProdAttributeTitle">Warehouse</div>
          <div class="catProdAttributeItem">    
          <input type="radio" id="13466918" name="1851262" mandatory="1" />    
          <span>US Warehouse $0</span>
          <img src="/images/attributeimageUS.png" alt="US Warehouse" border="0" /></div>
          <div class="catProdAttributeItem">
          <input type="radio" id="13466919" name="1851262" mandatory="1" />
          <span>AUS Warehouse $2.26</span>
          <img src="/images/attributeimageAUS.png" alt="AUS Warehouse" border="0" />
          </div>
     </div>
</div>
                <span class="updated_price">{tag_totalprice}</span>
                <span style="display:none;" class="original_price">{tag_totalprice}</span>
--Script---
<script type="text/javascript">
$('.catProdAttributeItem img').on("click",function(){
$(this) .siblings ('input[type=radio]') .attr('checked', true);
var original_price = $('.original_price').text() .replace(/[^0-9\.]/g, '');
parseFloat(this.original_price);
var warehouse_price = $(this).siblings('.catProdAttributeItem span') .text() .replace(/[^0-9\.]/g, '');
     warehouse_price=parseFloat(warehouse_price);
var total_price = parseFloat(original_price) + parseFloat(warehouse_price);
$('.updated_price').html('$' + total_price.toFixed(2));
</script>

Similar Messages

  • Adding a free sample button to the large product layout?

    hello guys
    im trying to figure out how to add a free sample button to the large product layout
    the site is a tiles shop http://ceramic-planet2.businesscatalyst.com/
    and we want to give the customer the option of ordering a sample from the large layout of the product they are viewing.
    A sample button underneath the add to cart button that is free but still charges a few $ for p&p.
    so I figure the sample button would be a add to cart tag of a seperate product added to the layout of the main product it is based on.
    any ideas how I can link a new different product to a product layout.
    plus not every product will need this button so is there a way of adding it to certain products? im thinking maybe using the custom tag? can I link products to a custom tag?
    if im not being clear I apologise but hopefully its simples
    Dave

    thanks for the help so far Mihai_Tica
    almost there Ive played with the cutom template like you said
    I made a template called samplebutton which has a tag_name_nolink and a add to cart button. Thats it nothing fancy.
    every product is going to have its very own sample button so I couldn't just add this custom template to the large template as it would only work for that one item I linked it to.
    so I added the module code with added custom template to the custom tag field for the large product and added it to the page {tag_custom3)  thus able to add different sample products to different large products.
    and it looks like its going to work.......until I add to cart and the product reverts back to small product template take a look http://ceramic-planet2.businesscatalyst.com/bathroom-tiles/cardiff-marron
    any ideas why when I add to cart the product reverts to small product template and how I can stop this from happening?

  • When Changing the quantity on a product the price displayed is not updating

    Hi all,
    When playing around with products on the front of the site we have noticed that the {totalprice} tag does not update if the quantity is changed, does anyone know why this may be happening or a fix for this issue?
    Thanks,
    Tom

    Hi Tom, On the large or small product layouts this price does not update. It is the total of 1 item. If you view the cart you will see the updated value based on multiple items.
    This is always been part of BC and not something that is broken.
    If you want the price to dynamcially change when you select 2,3,4 items on say the large product layout you will need to create some javascript.
    If you are refering to the cart - make a backup of the changes you have done and restore the cart to default. You will see the correct tags and working functionality. if that works compared to what you have carefull review your changes to find what you change to break the functionality.

  • RM06INP0 not update conditions price

    Dear.
    I run report RM06INP0.
    I have verified that this program update the net price of the info-record from the last purchase order.
    But the conditions prices (PB00 and RA00) of the info-record arenu2019t updated.
    Do you help me in order to solve this problem ?
    Thanks in advance.

    RM06INP0 will only take the last PO price if there are no conditions in the info record.
    It will never update conditions.
    It will only update the price field that you see in purchasing data view before you go into the conditions.
    Example:
    if you maintain today (may) a price for May and another one for June  in conditions, then the may price is updated as well in the EINE table (the net price field in info record purchasing data view)
    This EINE table price is not automatically updated with the june price if the date turns into June. You have to run RM06INP0 on June 1st to make this happen.
    This is the prupose of this report.

  • Error in Updating the Prices through DTW

    Hello Expert,
                         I am getting an error while updating the item prices through DTW.
    I upload all the items in SAP and prices in Price List 01
    Now I create One more Price List with Other name and want to update the Price in this Pricelist for all items through DTW
    but system giving an error "this entry is already present in Table(ODBC-2035) Application Defined or Object Defined ErrorItems"
    SAP 8.8
    PL 5
    Regards
    Atif

    What Neetu suggests is great.  However, you will run into problems if your users have deleted a price list.  Perform the following query as suggested:
    SELECT T0.[ListNum], T0.[ListName] FROM OPLN T0
    Copy this to excel and create a further column called 'RealNumber' or something
    Start numbering cells in this new column from 0 to whatever you need to cover all the lists from the database.
    The number in the 'Real Number' column is the one you should insert into the LineNum field in the prices spreadsheet.
    Hope this helps.  Reply if you need more guidance.
    Regards
    Bob

  • Recalculate the Price in SRM once the item is transfer to SRM from SRM MDM

    Hi Experts,
    I am technical person and am facing one issue,we are using MDM catalog for selecting the product and after selection the product is getting transfer to the SRM.
    In SRM we have Quantity field available which is editable(we don't want to make it read only field),everything works fine if no one is changing the Quantity field which is coming from SRM MDM.
    But when a requester is changing the quantity field of the product in SRM then the total price is not getting change accordingly in SRM.is there any way to fetch the price field again from SRM MDM once it is transferred to the SRM.
    I know that before transferring the field to SRM if we change the quantity field there there is "RECALCULATE" button availabe to change the total price but after transferring the item whats is the procedure to change the Price if quantity is changed in SRM.
    Note that Price field depends on the Quantity field in SRM MDM and it is maintained in MDM but not in SRM.
    Please Help me friends.

    Hi ,
    I just want to clarify that after the product  toSRM it will check data from their price data maintained in SRM.
    For yr problem just try these things and get back with yr results
    1. whatever quantity you are putting in SRM ,try with same quantity in mdm catalog and check what price is coming
         If that is same then not a prob because may bbe  for that product multiple price maintained for different quantity
        otherwise for sure SRM are fetching the price from their  storage.
    2. Instead of add an item from catalog  add same item from srm using the  product id ,supplier part number and other information
         may be  at srm level they maintain different condition on item level.
    Please try at yr end and get back with yr result.
    (for validation of price from mdm there is a setting spro that when checked do validate the price from mdm catalog when ypu copy yr product in srm)
    Thanks,
    Sudhanshu

  • HT4059 i have an american iPad2 (set to the UK), iOS version 6.1.2,  & iBooks version1.3.2 & can't get the price box to be selectable to purchase the book I want to buy from the iBookstore. What am I missing?????

    i have an american iPad2 (set to the UK), iOS version 6.1.2,  & iBooks version1.3.2 & can't get the price box to be selectable to purchase the book I want to buy from the iBookstore. What am I missing?????

    Backup with iTunes. If iTunes is asking you if you want to backup, say yes to that and it will backup your iPad. Have you ever synced with this computer before?
    My boilerplate response for anyone that wants to update the iOS.
    What you should do anytime that you update the device is to transfer purchases from the iPad into iTunes - File>Transfer Purchases - and you should backup the iPad as well. When you update the update the device, if something goes wrong, you can restore from the backup.
    However, iTunes should ask if you want to backup before you update, but just in case create the backup yourself before you update. The backup contains your app data and settings - along with other items - so make sure you backup first.
    If you have any other important files, you may want to transfer them to your computer as well, prior to the update.
    How to transfer purchases into your iTunes library
    http://support.apple.com/kb/HT1848
    How to backup and restore from a backup
    http://support.apple.com/kb/HT1766

  • Updating the Price for a PO Line ... What's Wrong?

    Both MsgBoxes return the correct values.  So, the B1 Purchase Order object appears to be functioning correctly.  However, the POR1 table is not updated in the database.  What am I doing wrong?
    Dim oPO As SAPbobsCOM.Documents
    Dim oPO_Lines As SAPbobsCOM.Document_Lines
    oPO = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oPurchaseOrders)
    oPO.GetByKey(lBaseRef)
    oPO_Lines = oPO.Lines
    oPO_Lines.SetCurrentLine(lBaseLine)
    MsgBox("Before Update: Price = " & oPO_Lines.Price)
    oPO_Lines.Price = dPrice
    MsgBox("After Update: Price = " & oPO_Lines.Price)
    oPO.Update()
    oPO.Close()
    lBaseRef and lBaseLine were assigned from a Purchase Invoice before this code was executed.

    Ah!  I figured this out.  The Purchase Order is Closed (and unedittable at the database level) once the Purchase Invoice is created for these items.  Therefore, the assignement of dPrice to the Price column is "NOT" updated in the POR1 table.
    Too bad that exceptions are not raised for such errors.  Also, it is confusing that the 2nd MsgBox() shows a misleading "updated" value.  Apparently, data validation is being handled at two layers in the application.  Why?  I would assume SAP would implement the validation at the business logic layer, especially given the recommendations to develop all customizations through the SDK.
    I can perform the update using a recordset query; but, this direct editting of the table would require modifying several lines in both the POR1 and OPOR tables.  Thus, this solution (my only solution for this project) would be extraordinarily difficult to maintain.  Therefore, I am going to recommend dropping this implementation requirement.

  • Valuation Type Price not updating in the PR

    We are using two valuation types for a material.
    Valuation type(New)in Material master has some price value in it Ex: 50 dollars per unit and Valuation type (Expense) is with Zero value.
    While creating a Purchase Requisition,default valuation type(New) gets updated and if we change the valuation type to (Expense) in the PR,there is no change in the Price.Actually the price should be Zero as defined in Material Master.
    Why the price is not updating ????
    Apperciating ur immediate response.

    Hi,
    During PR creation, Valuation Price is to be maintained derogatorily and generally it gets defaulted from Material Master.
    Once the Valuation Type "NEW" is getting defaulted in PR then it is copying the price from this and after changing the valuation type it doesn't change the Price since the valuation price obligation has already been fulfilled.
    So if you will stop defaulting the Valuation Type "NEW" for the material then it will ask Valuation type in PR and then it will pick up the price for that Valuation type.
    Default Valuation Type is maintained in OMWC
    Go to OMWC, there click on "Global Categories", here position cursor on the Valuation category (Maintained for Material Master) and click on "Change" button, here check have you entered any Valuation type "NEW" in field "Default: val.type ext.procure."

  • How to update the condition price in sales order while creating the invoice

    Hi,
    How to update the condition price in the sales order to carry out the new price while creating the invoice?
    While creating the invoice it should update the condition price in sales order.
    Thanks,
    Balaram

    No, pricing is not there in delivery.
    I found an exit for VF01transaction where we can update the price in order.
    Can you please tell me how to update the price if I have the order, material numbers and conditions number?
    Thanks,
    Balaram

  • If I increase an iBook price from $20 to $25 do to a major edition revision, is there a way for those who already purchased it to update and only pay the $5 difference?

    I've recently updated an iBook in iBooks Author and added 30% more content in the second edition. I'd like to raise the price but wanted to know if the people that already purchased the iBook could just pay the additional fee for the new edition, and not have to buy the whole iBook again. I have changed the cover art, but the title of the book is the same, just a second edition. Any help would be much appreciated.
    Patrick

    Once purchased, any updates you make to the book will appear to the purchasers as a free update.
    Lifting or lowering a  price affects  only new buyers
    Like wise I paid for apps which Google  later took over and made them free... I never got my money back!

  • ProcessOrder API not populating the Price from the pricing attribute setup.

    Hi,
    I am having a problem while adding a line on the existing order through the Oe_Order_pub.Process_order API. A line is added but the pricing is not fetched using the pricing attribute.
    I have passed calculate_Price_flag=’Y’ but in vain. I am not passing price list id but instead want to use a pricing attribute that will fetch the price on the item automatically.
    But, it is working when I am calling this procedure from TOAD but when it is called through the Workflow, a line is added but no price is fetched.
    Could anyone help me out on this? Here’s the code:
    p_api_version_number NUMBER := 1.0;
    p_init_msg_list VARCHAR2 (1) := FND_API.G_TRUE;
    p_return_values VARCHAR2 (1) := FND_API.G_TRUE;
    p_action_commit VARCHAR2 (1) := FND_API.G_FALSE;
    x_return_status VARCHAR2 (1);
    x_msg_count NUMBER := 0;
    x_msg_data VARCHAR2 (2000);
    p_header_rec oe_order_pub.header_rec_type:= oe_order_pub.g_miss_header_rec;
    p_old_header_rec oe_order_pub.header_rec_type:= oe_order_pub.g_miss_header_rec;
    p_header_val_rec oe_order_pub.header_val_rec_type:= oe_order_pub.g_miss_header_val_rec;
    p_old_header_val_rec oe_order_pub.header_val_rec_type:= oe_order_pub.g_miss_header_val_rec;
    p_header_adj_tbl oe_order_pub.header_adj_tbl_type:= oe_order_pub.g_miss_header_adj_tbl;
    p_old_header_adj_tbl oe_order_pub.header_adj_tbl_type:= oe_order_pub.g_miss_header_adj_tbl;
    p_header_adj_val_tbl oe_order_pub.header_adj_val_tbl_type:= oe_order_pub.g_miss_header_adj_val_tbl;
    p_old_header_adj_val_tbl oe_order_pub.header_adj_val_tbl_type:= oe_order_pub.g_miss_header_adj_val_tbl;
    p_header_price_att_tbl oe_order_pub.header_price_att_tbl_type:= oe_order_pub.g_miss_header_price_att_tbl;
    p_old_header_price_att_tbl oe_order_pub.header_price_att_tbl_type:= oe_order_pub.g_miss_header_price_att_tbl;
    p_header_adj_att_tbl oe_order_pub.header_adj_att_tbl_type:= oe_order_pub.g_miss_header_adj_att_tbl;
    p_old_header_adj_att_tbl oe_order_pub.header_adj_att_tbl_type:= oe_order_pub.g_miss_header_adj_att_tbl;
    p_header_adj_assoc_tbl oe_order_pub.header_adj_assoc_tbl_type:= oe_order_pub.g_miss_header_adj_assoc_tbl;
    p_old_header_adj_assoc_tbl oe_order_pub.header_adj_assoc_tbl_type:= oe_order_pub.g_miss_header_adj_assoc_tbl;
    p_header_scredit_tbl oe_order_pub.header_scredit_tbl_type:= oe_order_pub.g_miss_header_scredit_tbl;
    p_old_header_scredit_tbl oe_order_pub.header_scredit_tbl_type:= oe_order_pub.g_miss_header_scredit_tbl;
    p_header_scredit_val_tbl oe_order_pub.header_scredit_val_tbl_type:= oe_order_pub.g_miss_header_scredit_val_tbl;
    p_old_header_scredit_val_tbl oe_order_pub.header_scredit_val_tbl_type:= oe_order_pub.g_miss_header_scredit_val_tbl;
    p_line_tbl oe_order_pub.line_tbl_type:= oe_order_pub.g_miss_line_tbl;
    p_old_line_tbl oe_order_pub.line_tbl_type:= oe_order_pub.g_miss_line_tbl;
    p_line_val_tbl oe_order_pub.line_val_tbl_type:= oe_order_pub.g_miss_line_val_tbl;
    p_old_line_val_tbl oe_order_pub.line_val_tbl_type:= oe_order_pub.g_miss_line_val_tbl;
    p_line_adj_tbl oe_order_pub.line_adj_tbl_type:= oe_order_pub.g_miss_line_adj_tbl;
    p_old_line_adj_tbl oe_order_pub.line_adj_tbl_type:= oe_order_pub.g_miss_line_adj_tbl;
    p_line_adj_val_tbl oe_order_pub.line_adj_val_tbl_type:= oe_order_pub.g_miss_line_adj_val_tbl;
    p_old_line_adj_val_tbl oe_order_pub.line_adj_val_tbl_type:= oe_order_pub.g_miss_line_adj_val_tbl;
    p_line_price_att_tbl oe_order_pub.line_price_att_tbl_type:= oe_order_pub.g_miss_line_price_att_tbl;
    p_old_line_price_att_tbl oe_order_pub.line_price_att_tbl_type:= oe_order_pub.g_miss_line_price_att_tbl;
    p_line_adj_att_tbl oe_order_pub.line_adj_att_tbl_type:= oe_order_pub.g_miss_line_adj_att_tbl;
    p_old_line_adj_att_tbl oe_order_pub.line_adj_att_tbl_type:= oe_order_pub.g_miss_line_adj_att_tbl;
    p_line_adj_assoc_tbl oe_order_pub.line_adj_assoc_tbl_type:= oe_order_pub.g_miss_line_adj_assoc_tbl;
    p_old_line_adj_assoc_tbl oe_order_pub.line_adj_assoc_tbl_type:= oe_order_pub.g_miss_line_adj_assoc_tbl;
    p_line_scredit_tbl oe_order_pub.line_scredit_tbl_type:= oe_order_pub.g_miss_line_scredit_tbl;
    p_old_line_scredit_tbl oe_order_pub.line_scredit_tbl_type:= oe_order_pub.g_miss_line_scredit_tbl;
    p_line_scredit_val_tbl oe_order_pub.line_scredit_val_tbl_type:= oe_order_pub.g_miss_line_scredit_val_tbl;
    p_old_line_scredit_val_tbl oe_order_pub.line_scredit_val_tbl_type:= oe_order_pub.g_miss_line_scredit_val_tbl;
    p_lot_serial_tbl oe_order_pub.lot_serial_tbl_type:= oe_order_pub.g_miss_lot_serial_tbl;
    p_old_lot_serial_tbl oe_order_pub.lot_serial_tbl_type:= oe_order_pub.g_miss_lot_serial_tbl;
    p_lot_serial_val_tbl oe_order_pub.lot_serial_val_tbl_type:= oe_order_pub.g_miss_lot_serial_val_tbl;
    p_old_lot_serial_val_tbl oe_order_pub.lot_serial_val_tbl_type:= oe_order_pub.g_miss_lot_serial_val_tbl;
    p_action_request_tbl oe_order_pub.request_tbl_type := oe_order_pub.g_miss_request_tbl;
    x_header_rec oe_order_pub.header_rec_type;
    x_header_val_rec oe_order_pub.header_val_rec_type;
    x_header_adj_tbl oe_order_pub.header_adj_tbl_type;
    x_header_adj_val_tbl oe_order_pub.header_adj_val_tbl_type;
    x_header_price_att_tbl oe_order_pub.header_price_att_tbl_type;
    x_header_adj_att_tbl oe_order_pub.header_adj_att_tbl_type;
    x_header_adj_assoc_tbl oe_order_pub.header_adj_assoc_tbl_type;
    x_header_scredit_tbl oe_order_pub.header_scredit_tbl_type;
    x_header_scredit_val_tbl oe_order_pub.header_scredit_val_tbl_type;
    x_line_tbl oe_order_pub.line_tbl_type;
    x_line_val_tbl oe_order_pub.line_val_tbl_type;
    x_line_adj_tbl oe_order_pub.line_adj_tbl_type;
    x_line_adj_val_tbl oe_order_pub.line_adj_val_tbl_type;
    x_line_price_att_tbl oe_order_pub.line_price_att_tbl_type;
    x_line_adj_att_tbl oe_order_pub.line_adj_att_tbl_type;
    x_line_adj_assoc_tbl oe_order_pub.line_adj_assoc_tbl_type;
    x_line_scredit_tbl oe_order_pub.line_scredit_tbl_type;
    x_line_scredit_val_tbl oe_order_pub.line_scredit_val_tbl_type;
    x_lot_serial_tbl oe_order_pub.lot_serial_tbl_type;
    x_lot_serial_val_tbl oe_order_pub.lot_serial_val_tbl_type;
    x_action_request_tbl oe_order_pub.request_tbl_type;
    i NUMBER := 1;
    x_data VARCHAR2(2000);
    x_index NUMBER;
    x_err_msg VARCHAR2(4000);
    x_user_id NUMBER;
    x_appl_id NUMBER;
    x_resp_id NUMBER;
    X_DEBUG_FILE Varchar2(400);
    BEGIN
    oe_msg_pub.initialize();
    oe_debug_pub.initialize;
    X_DEBUG_FILE := OE_DEBUG_PUB.Set_Debug_Mode('FILE');
    oe_debug_pub.SetDebugLevel(3);
    -- INITIALIZATION REQUIRED FOR R12
    MO_GLOBAL.INIT('ONT');
    MO_GLOBAL.SET_ORG_CONTEXT(p_org_id,'','ONT');
    p_header_rec := OE_ORDER_PUB.G_MISS_HEADER_REC;
    p_action_request_tbl(i) := OE_ORDER_PUB.G_MISS_REQUEST_REC;
    p_line_tbl.delete;
    p_action_request_tbl.delete;
    p_line_tbl (i) := OE_ORDER_PUB.G_MISS_LINE_REC;
    p_line_tbl (i).operation := OE_GLOBALS.G_OPR_CREATE;
    p_line_tbl (i).header_id := p_header_id;
    p_line_tbl (i).ordered_quantity := p_qty;
    p_line_tbl (i).line_number := p_line_number;
    p_line_tbl (i).shipment_number := 1;
    p_line_tbl (i).calculate_price_flag := 'Y';--p_calc_price_flag;
    p_line_tbl (i).created_by := p_user_id ;
    p_line_tbl (i).creation_date := SYSDATE ;
    p_line_tbl (i).inventory_item_id := p_item_id;
    p_line_tbl (i).last_update_date := SYSDATE;
    --p_line_tbl (i).last_update_login        := -1;
    p_line_tbl (i).last_updated_by := p_user_id ;
    p_line_tbl (i).line_type_id := p_line_type_id;
    p_line_tbl (i).order_quantity_uom := p_qty_uom;
    p_line_tbl (i).org_id := p_org_id;
    --p_line_tbl (i).price_list_id            := p_price_list_id;
    p_line_tbl (i).ship_from_org_id := p_ship_from_org_id ;
    p_line_tbl (i).ship_to_contact_id := p_ship_to_contact_id;
    p_line_tbl (i).ship_to_org_id := p_ship_to_org_id;
    p_line_tbl (i).sold_from_org_id := p_sold_from_org_id ;
    p_line_tbl (i).sold_to_org_id := p_sold_to_org_id;
    p_line_tbl (i).subinventory := p_subinventory ;
    --p_line_tbl (i).unit_list_price          := p_price;
    --p_line_tbl (i).unit_selling_price       := p_price;
    p_line_tbl (i).booked_flag := 'Y';
    p_line_tbl(i).flow_status_code := 'CLOSED';
    --SAVEPOINT BEFORE_PROC_API;
    OE_ORDER_PUB.PROCESS_ORDER (
    p_api_version_number => p_api_version_number
    ,p_init_msg_list => p_init_msg_list
    ,p_return_values => p_return_values
    ,p_action_commit => p_action_commit
    ,p_header_rec => p_header_rec
    ,p_old_header_rec => p_old_header_rec
    ,p_header_val_rec => p_header_val_rec
    ,p_old_header_val_rec => p_old_header_val_rec
    ,p_header_adj_tbl => p_header_adj_tbl
    ,p_old_header_adj_tbl => p_old_header_adj_tbl
    ,p_header_adj_val_tbl => p_header_adj_val_tbl
    ,p_old_header_adj_val_tbl => p_old_header_adj_val_tbl
    ,p_header_price_att_tbl => p_header_price_att_tbl
    ,p_old_header_price_att_tbl => p_old_header_price_att_tbl
    ,p_header_adj_att_tbl => p_header_adj_att_tbl
    ,p_old_header_adj_att_tbl => p_old_header_adj_att_tbl
    ,p_header_adj_assoc_tbl => p_header_adj_assoc_tbl
    ,p_old_header_adj_assoc_tbl => p_old_header_adj_assoc_tbl
    ,p_header_scredit_tbl => p_header_scredit_tbl
    ,p_old_header_scredit_tbl => p_old_header_scredit_tbl
    ,p_header_scredit_val_tbl => p_header_scredit_val_tbl
    ,p_old_header_scredit_val_tbl => p_old_header_scredit_val_tbl
    ,p_line_tbl => p_line_tbl
    ,p_old_line_tbl => p_old_line_tbl
    ,p_line_val_tbl => p_line_val_tbl
    ,p_old_line_val_tbl => p_old_line_val_tbl
    ,p_line_adj_tbl => p_line_adj_tbl
    ,p_old_line_adj_tbl => p_old_line_adj_tbl
    ,p_line_adj_val_tbl => p_line_adj_val_tbl
    ,p_old_line_adj_val_tbl => p_old_line_adj_val_tbl
    ,p_line_price_att_tbl => p_line_price_att_tbl
    ,p_old_line_price_att_tbl => p_old_line_price_att_tbl
    ,p_line_adj_att_tbl => p_line_adj_att_tbl
    ,p_old_line_adj_att_tbl => p_old_line_adj_att_tbl
    ,p_line_adj_assoc_tbl => p_line_adj_assoc_tbl
    ,p_old_line_adj_assoc_tbl => p_old_line_adj_assoc_tbl
    ,p_line_scredit_tbl => p_line_scredit_tbl
    ,p_old_line_scredit_tbl => p_old_line_scredit_tbl
    ,p_line_scredit_val_tbl => p_line_scredit_val_tbl
    ,p_old_line_scredit_val_tbl => p_old_line_scredit_val_tbl
    ,p_lot_serial_tbl => p_lot_serial_tbl
    ,p_old_lot_serial_tbl => p_old_lot_serial_tbl
    ,p_lot_serial_val_tbl => p_lot_serial_val_tbl
    ,p_old_lot_serial_val_tbl => p_old_lot_serial_val_tbl
    ,p_action_request_tbl => p_action_request_tbl
    ,x_header_rec => x_header_rec
    ,x_header_val_rec => x_header_val_rec
    ,x_header_adj_tbl => x_header_adj_tbl
    ,x_header_adj_val_tbl => x_header_adj_val_tbl
    ,x_header_price_att_tbl => x_header_price_att_tbl
    ,x_header_adj_att_tbl => x_header_adj_att_tbl
    ,x_header_adj_assoc_tbl => x_header_adj_assoc_tbl
    ,x_header_scredit_tbl => x_header_scredit_tbl
    ,x_header_scredit_val_tbl => x_header_scredit_val_tbl
    ,x_line_tbl => x_line_tbl
    ,x_line_val_tbl => x_line_val_tbl
    ,x_line_adj_tbl => x_line_adj_tbl
    ,x_line_adj_val_tbl => x_line_adj_val_tbl
    ,x_line_price_att_tbl => x_line_price_att_tbl
    ,x_line_adj_att_tbl => x_line_adj_att_tbl
    ,x_line_adj_assoc_tbl => x_line_adj_assoc_tbl
    ,x_line_scredit_tbl => x_line_scredit_tbl
    ,x_line_scredit_val_tbl => x_line_scredit_val_tbl
    ,x_lot_serial_tbl => x_lot_serial_tbl
    ,x_lot_serial_val_tbl => x_lot_serial_val_tbl
    ,x_action_request_tbl => x_action_request_tbl
    ,x_return_status => x_return_status
    ,x_msg_count => x_msg_count
    ,x_msg_data => x_msg_data
    p_status := x_return_status;
    IF x_return_status != apps.fnd_api.g_ret_sts_success THEN
    x_err_msg:= 'API Error Occured while creating Recycle Fees line ' ;
    FOR i in 1..x_msg_count
    LOOP
    OE_MSG_PUB.GET(i,'F',x_data,x_index);
    x_err_msg := x_err_msg || x_data ;
    END LOOP;
    p_error := x_err_msg;
    insert into xx_test values('API ERR: '||SYSDATE|| p_error);
    -- ROLLBACK TO SAVEPOINT BEFORE_PROC_API;
    END IF;
    EXCEPTION
    WHEN OTHERS THEN
    -- ROLLBACK TO SAVEPOINT BEFORE_PROC_API;
    p_error := 'Error Occured in Order Line API: '||SYSDATE||substr(SQLERRM,1,250) ;
    p_status := 'E';
    END call_order_api;
    Thanks,
    Rahul

    Another striking feature here is, the API works absolutely well for the Internal Orders (Book--> Release-->Ship) but price is not pulled for the External Drop Ship Orders.

  • Update the price related to condtions in Sales Order

    Hi all,
    I want to update the price related to condtions in Sales Order from input file. I am using bapi 'BAPI_SALESORDER_CHANGE' to for this.
    the code for this
        wa_conditions-itm_number = wa_itab-itm_number.
        wa_conditions-cond_value = wa_itab-kbetr.
        wa_conditions-cond_type  = 'ZPSV'.
        wa_conditions-cond_count = wa_itab-kwmeng.
        APPEND wa_conditions TO it_conditions.
        wa_conditionsx-itm_number =  wa_itab-itm_number.
        wa_conditionsx-cond_count = wa_itab-kwmeng.
        wa_conditionsx-cond_value = 'X'.
        wa_conditionsx-cond_type  = 'ZPSV'.
        wa_conditionsx-updateflag = 'U'.
        APPEND wa_conditionsx TO it_conditionsx.
    But this is creating a new line in conditions instead of updating the existing line, I want to update the exsting line with new condition rate instead of creating a new line.
    i have tried by   lv_logic-pricing = 'B'.
    But it works when values are maintained in vk11.
    Please help me if you have any soultion for this.

    hi siya,
    plz refer to the following threads
    Re: problem using Bapi_Salesorder_Change
    http://www.sapfans.com/forums/viewtopic.php?p=160339&sid=bf9e3219db318d89596f7e911462416f
    i hope it helps.
    arjun

  • Updating the Price Determination Field in the Material Master (MBEW-MLAST)

    I'm doing a material conversion into an existing SAP system and the program to load the materials didn't load a value in the price determination field (MBEW-MLAST).  Normally this field is required but because the conversion BAPI doesn't do as much validation as MM01 it was possible to create the record without a value.  The field is not open to input when I use MM02, and even though it appears to work, when I do MM17 mass change the field is also not updated.  Finally I tried transaction CKMM - Change Material Price Determination for Material Ledger but it required an entry in the Old Price Determination field and it won't let me enter blank. 
    We've since corrected the program but my problem is that I've converted about 5000 materials without a value in the field meaning the FI guys can't release cost estimates which is causing a bunch of problems for the testing that we want to do in this system.   We've taken about 3 weeks to do this conversion so going back and doing it again is a terrible option.  Does anybody know a way to get a value into this field other than what I've mentioned above (MM02, MM17, CKMM)?
    Suggestions please.

    have a look into OSS Note 1491364 - BAdI CKML_SET_VPRSV: Price determination cannot be changed

  • BAPI_PO_CHANGE to update the Price for the line item not updating the Price

    Hi,
    I am using BAPI_PO_CHANGE to update the Price for the line item. This BAPI is not updating the Price. I am using external cummit also, but the BAPI is not updating price.
    I am passing following data to the BAPI.
    Plant: CQ11
    PO                   Material                Price
    4500002142     TEST_BATCH     12
    Please provide suggestion.
    Regards,
    Jubin.

    Hi,
    check this link...this has sample code
    [http://www.sap-img.com/abap/sample-abap-code-on-bapi-po-change.htm]
    Regards,
    Surinder

Maybe you are looking for