Order Confirmed - No Order Found

I am still waiting on an outcome to this, I have not received an email response. I do have a case number for this but I am unable to call during business hours today to follow up. I have a copy of my order confirmation from the website but the order number still shows invalid. I would like to know how to proceed so that I can receive the product I attempted to purchase at the sale price you advertised. Thank you.
Email below (code numbers and account numbers removed)
I placed an order tonight and did not get an email confirmation. I checked my rewards coupon and Student Discount and they have been redeemed but there does not seem to be an order. I did get a confirmation and an order number at time of order but no emails and it does not show up in my order history.
I wanted to make sure this goes through since the sale price was a great deal. I used my rewards certificate and my student promo code but I was unable to re-do the order because it said codes have been used already.

Hello ehz1,
Placing an order online should be a quick and easy process, so it's surprising to read that you never received an order confirmation page. I'd be confused too if I found myself in a similar situation, especially if an immediate resolution didn't appear to be available.
I've had the chance to review your account and was able to confirm that our post-purchase support team was not able to locate records of your initial order. It's also my understanding they've offered to assist you in placing another order at the same pricing, so I'd encourage you follow up with the sales reps at 1-888-BEST-BUY (1-888-237-8289) if you haven't already done so. As you may have been informed yesterday, the My Best Buy reward certificates you initially attempted to use should also post back to your account in the next 2-3 business days.
Thank you for your patience and understanding!
Aaron|Social Media Specialist | Best Buy® Corporate
Private Message

Similar Messages

Order confirmation and Order changes

Hello Guru's,
I am having following issue, please let me know ur inputs on the same how to handle below situation.
There is Customer Vendor relationship under one system and under one company code.
Customer orders goods from Vendor and this Vendor supplies goods against this PO. These are nothing but plants in reality.
1) There is no issue when creating SO against the PO raised..
2) Once the SO is created how to send sales order confirmation and how to add the confirmation line in PO?
3) When the sales is changed and changes made at the time of sales order creation wrt to PO from customer: how to send these changes to customer and update his PO also.
Please let me know if anyone has gone thr' such situation. This should happen via ALE IDOC only.
Best regards,
Prasad

Hi Kris,
It's ok.. as I knew the process.
The problem I had, when I change sales order and trigger ORDERS05 and ORDRSP idoc then it shows changes but also it shows all the sales order data.
The requirement which I have is as below:
1) If the sales order is changed then send only changed data and update the PO at customer side which is in same system.
i.e. let us say sales order is created and confirmation also send via ORDERS05 and ORDRSP. Now when SO is changed for quantity and price, then I want to send only these quantity and price changes via idoc and update PO accordingly.
This also applies for back order processing or supersession, where date or item itself can be changed or added.
Please come back if knows further.. Awaiting for ur reply.
I am interested to know what steps I have to follow and even if any routine I need to write to capture these changes.
Best regards,
Guru

Printing sales order confirmation if order changes

Hi all,
I have to implement some changes in output control to achieve a particular requirement.
Business wants sales order confirmations to get re-printed if and only if some changes in the sales order were cought.
For example if the quanity of a position changes then, the sales order confirmation must be re-printed.
I was thinking to use requirement routine for sales order confirmation but in the structure komkbv1 and kompbv1 there are not all the fields i need to understands if in the sales order, any changes have been performed.
Another way would be the user exit save_document_prepare in which i can use xvbak and yvbak in order to gather info about the changes in the sales order, but i am not sure this is the right way to achieve what business has asked to me.
Do you have any ideas? Please, any suggestion is welcome!
Regards,
Fabrizio

Hi gurus,
My idea is:
-user exit save_document_prepare: check chenges in SO using xvbak, yvbak etc.. If a change occurs i will set a particular parameter using "SET PARAMETER".
-user exit USEREXIT_KOMKBV1_FILL: i will fill the communication structure with respect of the instruction of "GET PARAMETER"
- requirement routine for sales order (vofm): checking of the communication structure to understand if sales order confirmation has to be re-processed or not.
What do you think about this solution?
Thanks,
Fabrizio

O2 order confirmation with Order no & collection reference but no record of mobile on my o2

Please can someone help?I set up a pay monthly phone online 2 days ago and recieved an o2 order confirmation along with Order No and collection reference in the store I chose to pick up in but I've heard no more. I spoke to the online team and they told me that my order is still with the credit check team. So why have I got an order confirmation? Also I cannot see this order in my O2. So confuse

If it's with the credit check team still it means you have not yet been accepted so the order won't show and no confirmation until they do approve.

No order confirmation or order history

I placed an order this morning on the website for store pickup under my account and have not gotten the order confirmation or an entry for the order in order history. My Paypal accoutn was charged for the order so this is a little disconcerting. Hope someone can help me with this as I will need the order number etc... to pick up at the store.

Good afternoon sqadan, and welcome to the Best Buy forum,
I am glad to hear that you have finally received your confirmation email. Due to maintenance we performed on BestBuy.com last night, the delivery of some confirmation emails have been delayed. I pulled up the order that you placed and confirmed that it is currently ready to be picked up. Please let us know if you have any other questions, as we are always happy to help.
Thank you for reaching out to us!

Re: No order confirmation or order history

I made an online order this morning as well, but mine is to ship out rather than pick up. I never got a confirmation email from BBY, nor is my order showing up on the order history page. I did get a confirmation of the order from PayPal, however. Unlike you though, my order is still MIA. Is there some kind of glitch happening today with ordering? I've never had this problem before.

Good evening brent_ohara-
I apologize for an inconvenience that you might have been under by not receiving your confirmation email after you placed your recent order with Best Buy. It has come to my attention that there was a maintained preformed on BestBuy.com that delayed some confirmation emails.
I took the opportunity to review your order using the email address that you used to register on the forum, and confirmed that it’s processing accordingly. You should now be able to view the order history on your BestBuy.com account. If you continue to have trouble locating the information, feel free to reach out to me.
Regards,

MM-SUS Scenario: Order confirmed but No Order Ack triggered to XI

Hi,
We have configued ECC(MM)-XI-SRM(SUS) for Classic scenario.
When new PO is being created in ECC, the same is getting posted in SRM and we could see in the SUS portal. Upon Order Confirmation, the Order is moved from <b>"New/In Process"to "Confirmed" orders</b>. But no message(PurchaseOrderConfirmation_out) is being sent out of SRM system.
How will this message get triggered?
Regards,
Siva

HI,
in one my earlier implementation, we have done similar scenario. In that case , we will send the PO information to SUS. But we did not have confirmation scenario. I think, it is better to check out in the SUS side i.e go to transaction SXMB_MONI in SUS to check any messages. Provided , I think, SUS is sending this ack thru porxy.
anyway TO know more -
https://websmp201.sap-ag.de/ibc -->go to mySAP SRM and find the required scenario.
Hope this helps,
Regards,
moorthy

Order confirmation Print Program and Smartform

Hi,
I found a smartform for the order confirmation.'/SMB40/SDORC_A'.I have searched the forums and found the print program to be the same.But we don't have it.We're on ECC 6.0Where can we download the program from?
Thanks..
Edited by: John G on Feb 4, 2008 5:19 PM

Hi John,
He has given some FM that is generated by that form. But that FM will vary from system to system . So thats very very wrong.
Some times smartforms will not be there in our system . You have to request your superiors to place the forms in place.
Reward points if useful
Regards,
Nageswar.

Partial Pick Confirming Sales Order

Hi Folks,
I have a requirement where I have to Pick Confirm and Ship confirm Sales Order through API.
1. When the quantites to be picked are same as quantity ordered the code seems to work just fine.
But suppose in my example my quantity in SO line is 50 and I want to partially Ship confirm the lines lets say 20 quantites.
then which API i need to use?
The approach I am following is while pick confirming I am passing 20 quantites only and the ship confirming it.
I researched and found that we can use the following API to update shipping attributes 'WSH_DELIVERY_DETAILS_PUB.Update_Shipping_Attributes' but when I run it (I tried before and after Pick confirm) the API runs fine but no changes are getting affected and the code Pick confirms all the quantity.
Could some please help me with this.
Please find the codes for pick confirm and updating shipping attributes
Pick confirm code
DECLARE
lv_order_num        number := 700145812;
vMoveOrderLineId    NUMBER;
p_pick_conf_qty     NUMBER;
pStatus             VARCHAR2(100);
pMsgData            VARCHAR2(4000);
v_movehdr_rec       INV_MOVE_ORDER_PUB.TROHDR_REC_TYPE;
v_movehdr_val_rec   INV_MOVE_ORDER_PUB.TROHDR_VAL_REC_TYPE;
v_moveln_tbl        INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_tbl_p      INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_zero_tbl   INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_zero_tbl_p INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_tbl_d      INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_tbl_o      INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_val_tbl    INV_MOVE_ORDER_PUB.TROLIN_VAL_TBL_TYPE;
v_mold_tbl          INV_MO_LINE_DETAIL_UTIL.G_MMTT_TBL_TYPE;
v_mold_tbl_p        INV_MO_LINE_DETAIL_UTIL.G_MMTT_TBL_TYPE;
l_mold_tbl          INV_MO_LINE_DETAIL_UTIL.G_MMTT_TBL_TYPE;
l_moveln_tbl        INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
l_trolin_rec        INV_MOVE_ORDER_PUB.TROLIN_REC_TYPE;
l_trolin_tbl        INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
l_return_status     VARCHAR2(240);
l_msg_count         NUMBER;
l_msg_data          VARCHAR2(2000);
l_move_hdr_id       NUMBER;
l_move_order_no     NUMBER := 0;
v_return_values     VARCHAR2(2000) := FND_API.G_TRUE;
v_move_hdr_rec      INV_MOVE_ORDER_PUB.TROHDR_REC_TYPE;
v_move_hdr_val_rec INV_MOVE_ORDER_PUB.TROHDR_VAL_REC_TYPE;
v_api_pick_confirm NUMBER;
cv_fail             VARCHAR2(100) := 'Fail';
cv_success          VARCHAR2(100) := 'Success';
g_user_id      number;
g_resp_id      number;
g_resp_appl_id number;
p_user_name    varchar2(100) := 'SYSADMIN';
p_resp_name    varchar2(100) := 'Order Management Super User';
p_mo_apps      varchar2(100) := 'ONT';
CURSOR c_mmtt_recs(vMoveOrderLineId NUMBER) IS
    SELECT transaction_header_id,
           transaction_temp_id,
           source_code,
           source_line_id,
           transaction_mode,
           lock_flag,
           last_update_date,
           last_updated_by,
           creation_date,
           created_by,
           last_update_login,
           request_id,
           program_application_id,
           program_id,
           program_update_date,
           inventory_item_id,
           revision,
           organization_id,
           subinventory_code,
           locator_id,
           transaction_quantity,
           primary_quantity,
           transaction_uom,
           transaction_cost,
           transaction_type_id,
           transaction_action_id,
           transaction_source_type_id,
           transaction_source_id,
           transaction_source_name,
           transaction_date,
           acct_period_id,
           distribution_account_id,
           transaction_reference,
           requisition_line_id,
           requisition_distribution_id,
           reason_id,
           lot_number,
           lot_expiration_date,
           serial_number,
           receiving_document,
           demand_id,
           rcv_transaction_id,
           move_transaction_id,
           completion_transaction_id,
           wip_entity_type,
           schedule_id,
           repetitive_line_id,
           employee_code,
           primary_switch,
           schedule_update_code,
           setup_teardown_code,
           item_ordering,
           negative_req_flag,
           operation_seq_num,
           picking_line_id,
           trx_source_line_id,
           trx_source_delivery_id,
           physical_adjustment_id,
           cycle_count_id,
           rma_line_id,
           customer_ship_id,
           currency_code,
           currency_conversion_rate,
           currency_conversion_type,
           currency_conversion_date,
           ussgl_transaction_code,
           vendor_lot_number,
           encumbrance_account,
           encumbrance_amount,
           ship_to_location,
           shipment_number,
           transfer_cost,
           transportation_cost,
           transportation_account,
           freight_code,
           containers,
           waybill_airbill,
           expected_arrival_date,
           transfer_subinventory,
           transfer_organization,
           transfer_to_location,
           new_average_cost,
           value_change,
           percentage_change,
           material_allocation_temp_id,
           demand_source_header_id,
           demand_source_line,
           demand_source_delivery,
           item_segments,
           item_description,
           item_trx_enabled_flag,
           item_location_control_code,
           item_restrict_subinv_code,
           item_restrict_locators_code,
           item_revision_qty_control_code,
           item_primary_uom_code,
           item_uom_class,
           item_shelf_life_code,
           item_shelf_life_days,
           item_lot_control_code,
           item_serial_control_code,
           item_inventory_asset_flag,
           allowed_units_lookup_code,
           department_id,
           department_code,
           wip_supply_type,
           supply_subinventory,
           supply_locator_id,
           valid_subinventory_flag,
           valid_locator_flag,
           locator_segments,
           current_locator_control_code,
           number_of_lots_entered,
           wip_commit_flag,
           next_lot_number,
           lot_alpha_prefix,
           next_serial_number,
           serial_alpha_prefix,
           shippable_flag,
           posting_flag,
           required_flag,
           process_flag,
           error_code,
           error_explanation,
           attribute_category,
           attribute1,
           attribute2,
           attribute3,
           attribute4,
           attribute5,
           attribute6,
           attribute7,
           attribute8,
           attribute9,
           attribute10,
           attribute11,
           attribute12,
           attribute13,
           attribute14,
           attribute15,
           movement_id,
           reservation_quantity,
           shipped_quantity,
           transaction_line_number,
           task_id,
           to_task_id,
           source_task_id,
           project_id,
           source_project_id,
           pa_expenditure_org_id,
           to_project_id,
           expenditure_type,
           final_completion_flag,
           transfer_percentage,
           transaction_sequence_id,
           material_account,
           material_overhead_account,
           resource_account,
           outside_processing_account,
           overhead_account,
           flow_schedule,
           cost_group_id,
           demand_class,
           qa_collection_id,
           kanban_card_id,
           overcompletion_transaction_id,
           overcompletion_primary_qty,
           overcompletion_transaction_qty,
           end_item_unit_number,
           scheduled_payback_date,
           line_type_code,
           parent_transaction_temp_id,
           put_away_strategy_id,
           put_away_rule_id,
           pick_strategy_id,
           pick_rule_id,
           common_bom_seq_id,
           common_routing_seq_id,
           cost_type_id,
           org_cost_group_id,
           move_order_line_id,
           task_group_id,
           pick_slip_number,
           reservation_id,
           transaction_status,
           transfer_cost_group_id,
           lpn_id,
           transfer_lpn_id,
           pick_slip_date,
           content_lpn_id
      FROM MTL_MATERIAL_TRANSACTIONS_TEMP
     WHERE move_order_line_id = vMoveOrderLineId;
l_moveln_fidx     NUMBER;
l_moveln_lidx     NUMBER;
n_mvln_cntr       NUMBER;
l_Index           NUMBER := 1;
v_records_in_mmtt NUMBER := 0;
REC C_MMTT_RECS%ROWTYPE;
BEGIN
select user_id
    into g_user_id
    from fnd_user
   where user_name = p_user_name;
select responsibility_id, application_id
    into g_resp_id, g_resp_appl_id
    from apps.fnd_responsibility_vl
   where responsibility_name = p_resp_name;
Apps.FND_Global.Apps_Initialize(g_user_id, g_resp_id, g_resp_appl_id);
MO_GLOBAL.INIT(p_mo_apps);
for mol in (select wda.delivery_id,
                     wda.delivery_detail_id,
                     wda.parent_delivery_detail_id,
                     wdd.source_code,
                     wdd.inventory_item_id,
                     wdd.organization_id,
                     wdd.ship_from_location_id,
                     wdd.ship_to_location_id,
                     wdd.requested_quantity,
                     wdd.requested_quantity_uom,
                     wdd.move_order_line_id,
                     wdd.org_id,
                     mtrl.quantity,
                     mtrl.quantity_delivered
                from wsh_delivery_details     wdd,
                     wsh_delivery_assignments wda,
                     oe_order_lines_all       ol,
                     oe_order_headers_all     oh,
                     mtl_txn_request_lines    mtrl,
                     mtl_txn_request_headers mtrh
               where wdd.source_line_id = ol.line_id
                 and wdd.delivery_detail_id = wda.delivery_detail_id
                 and ol.header_id = oh.header_id
                 and wdd.move_order_line_id = mtrl.line_id(+)
                 and mtrl.header_id = mtrh.header_id(+)
                 and oh.order_number = lv_order_num) loop
    vMoveOrderLineId := mol.move_order_line_id;
    p_pick_conf_qty := mol.quantity - nvl(mol.quantity_delivered,0);
    SELECT COUNT(move_order_line_id)
      INTO v_records_in_mmtt
      FROM MTL_MATERIAL_TRANSACTIONS_TEMP
     WHERE move_order_line_id = vMoveOrderLineId;
    IF v_records_in_mmtt > 1 THEN
      pStatus := cv_fail;
      pMsgData := 'Wrong number of records in MMTT for the MOVE_ORDER_LINE_ID : ' ||
                  vMoveOrderLineId;
      DBMS_OUTPUT.PUT_LINE('Multiple records in MMTT for move_order_line_id = ' ||
                           vMoveOrderLineId);
      v_api_pick_confirm := 0;
      GOTO end_of_pkcnf;
    ELSIF v_records_in_mmtt = 0 THEN
      --means that the delivery is already pick confirmed
      pStatus := cv_success;
      DBMS_OUTPUT.PUT_LINE('No records in MMTT for move_order_line_id = ' ||
                           vMoveOrderLineId ||
                           ' hence it is already pick confirmed');
      v_api_pick_confirm := 0;
      GOTO end_of_pkcnf;
    END IF;
    SELECT mtrh.header_id, mtrh.request_number
      INTO l_move_hdr_id, l_move_order_no
      FROM mtl_txn_request_headers mtrh, mtl_txn_request_lines mtrl
     WHERE mtrh.header_id = mtrl.header_id
       AND mtrl.line_id = vMoveOrderLineId;
    DBMS_OUTPUT.PUT_LINE('Obtained MTRH.HEADER_ID = ' || l_move_hdr_id ||
                         ' MTRH.REQUEST_NUMBER = ' || l_move_order_no ||
                         ' for move_order_line_id = ' || vMoveOrderLineId);
    INV_MOVE_ORDER_PUB.GET_MOVE_ORDER(p_api_version_number => 1.0,
                                      p_init_msg_list      => FND_API.G_FALSE,
                                      p_return_values      => v_return_values,
                                      x_return_status      => l_return_status,
                                      x_msg_count          => l_msg_count,
                                      x_msg_data           => l_msg_data,
                                      p_header_id          => l_move_hdr_id,
                                      p_header             => l_move_order_no,
                                      x_trohdr_rec         => v_move_hdr_rec,
                                      x_trohdr_val_rec     => v_move_hdr_val_rec,
                                      x_trolin_tbl         => v_moveln_tbl,
                                      x_trolin_val_tbl     => v_moveln_val_tbl);
     COMMIT;
    DBMS_OUTPUT.PUT_LINE('Return status of INV_MOVE_ORDER_PUB.GET_MOVE_ORDER = ' ||
                         l_return_status);
    IF l_return_status != FND_API.G_RET_STS_SUCCESS THEN
      pStatus := cv_fail;
      pMsgData := 'Failed to get move order inv_move_order_pub.get_move_order for MOVE_ORDER_LINE_ID : ' ||
                  vMoveOrderLineId;
      GOTO end_of_pkcnf;
    END IF;
    OPEN c_mmtt_recs(vMoveOrderLineId);
    FETCH c_mmtt_recs
      INTO rec;
    CLOSE c_mmtt_recs;
    v_mold_tbl(1).transaction_header_id := rec.transaction_header_id;
    v_mold_tbl(1).transaction_temp_id := rec.transaction_temp_id;
    v_mold_tbl(1).source_code := rec.source_code;
    v_mold_tbl(1).source_line_id := rec.source_line_id;
    v_mold_tbl(1).transaction_mode := rec.transaction_mode;
    v_mold_tbl(1).lock_flag := rec.lock_flag;
    v_mold_tbl(1).last_update_date := rec.last_update_date;
    v_mold_tbl(1).last_updated_by := rec.last_updated_by;
    v_mold_tbl(1).creation_date := rec.creation_date;
    v_mold_tbl(1).created_by := rec.created_by;
    v_mold_tbl(1).last_update_login := rec.last_update_login;
    v_mold_tbl(1).request_id := rec.request_id;
    v_mold_tbl(1).program_application_id := rec.program_application_id;
    v_mold_tbl(1).program_id := rec.program_id;
    v_mold_tbl(1).program_update_date := rec.program_update_date;
    v_mold_tbl(1).inventory_item_id := rec.inventory_item_id;
    v_mold_tbl(1).revision := rec.revision;
    v_mold_tbl(1).organization_id := rec.organization_id;
    v_mold_tbl(1).subinventory_code := rec.subinventory_code;
    v_mold_tbl(1).locator_id := rec.locator_id;
    v_mold_tbl(1).transaction_quantity := rec.transaction_quantity;
    v_mold_tbl(1).primary_quantity := rec.primary_quantity;
    v_mold_tbl(1).transaction_uom := rec.transaction_uom;
    v_mold_tbl(1).transaction_cost := rec.transaction_cost;
    v_mold_tbl(1).transaction_type_id := rec.transaction_type_id;
    v_mold_tbl(1).transaction_action_id := rec.transaction_action_id;
    v_mold_tbl(1).transaction_source_type_id := rec.transaction_source_type_id;
    v_mold_tbl(1).transaction_source_id := rec.transaction_source_id;
    v_mold_tbl(1).transaction_source_name := rec.transaction_source_name;
    v_mold_tbl(1).transaction_date := rec.transaction_date;
    v_mold_tbl(1).acct_period_id := rec.acct_period_id;
    v_mold_tbl(1).distribution_account_id := rec.distribution_account_id;
    v_mold_tbl(1).transaction_reference := rec.transaction_reference;
    v_mold_tbl(1).requisition_line_id := rec.requisition_line_id;
    v_mold_tbl(1).requisition_distribution_id := rec.requisition_distribution_id;
    v_mold_tbl(1).reason_id := rec.reason_id;
    v_mold_tbl(1).lot_number := rec.lot_number;
    v_mold_tbl(1).lot_expiration_date := rec.lot_expiration_date;
    v_mold_tbl(1).serial_number := rec.serial_number;
    v_mold_tbl(1).receiving_document := rec.receiving_document;
    v_mold_tbl(1).demand_id := rec.demand_id;
    v_mold_tbl(1).rcv_transaction_id := rec.rcv_transaction_id;
    v_mold_tbl(1).move_transaction_id := rec.move_transaction_id;
    v_mold_tbl(1).completion_transaction_id := rec.completion_transaction_id;
    v_mold_tbl(1).wip_entity_type := rec.wip_entity_type;
    v_mold_tbl(1).schedule_id := rec.schedule_id;
    v_mold_tbl(1).repetitive_line_id := rec.repetitive_line_id;
    v_mold_tbl(1).employee_code := rec.employee_code;
    v_mold_tbl(1).primary_switch := rec.primary_switch;
    v_mold_tbl(1).schedule_update_code := rec.schedule_update_code;
    v_mold_tbl(1).setup_teardown_code := rec.setup_teardown_code;
    v_mold_tbl(1).item_ordering := rec.item_ordering;
    v_mold_tbl(1).negative_req_flag := rec.negative_req_flag;
    v_mold_tbl(1).operation_seq_num := rec.operation_seq_num;
    v_mold_tbl(1).picking_line_id := rec.picking_line_id;
    v_mold_tbl(1).trx_source_line_id := rec.trx_source_line_id;
    v_mold_tbl(1).trx_source_delivery_id := rec.trx_source_delivery_id;
    v_mold_tbl(1).physical_adjustment_id := rec.physical_adjustment_id;
    v_mold_tbl(1).cycle_count_id := rec.cycle_count_id;
    v_mold_tbl(1).rma_line_id := rec.rma_line_id;
    v_mold_tbl(1).customer_ship_id := rec.customer_ship_id;
    v_mold_tbl(1).currency_code := rec.currency_code;
    v_mold_tbl(1).currency_conversion_rate := rec.currency_conversion_rate;
    v_mold_tbl(1).currency_conversion_type := rec.currency_conversion_type;
    v_mold_tbl(1).currency_conversion_date := rec.currency_conversion_date;
    v_mold_tbl(1).ussgl_transaction_code := rec.ussgl_transaction_code;
    v_mold_tbl(1).vendor_lot_number := rec.vendor_lot_number;
    v_mold_tbl(1).encumbrance_account := rec.encumbrance_account;
    v_mold_tbl(1).encumbrance_amount := rec.encumbrance_amount;
    v_mold_tbl(1).ship_to_location := rec.ship_to_location;
    v_mold_tbl(1).shipment_number := rec.shipment_number;
    v_mold_tbl(1).transfer_cost := rec.transfer_cost;
    v_mold_tbl(1).transportation_cost := rec.transportation_cost;
    v_mold_tbl(1).transportation_account := rec.transportation_account;
    v_mold_tbl(1).freight_code := rec.freight_code;
    v_mold_tbl(1).containers := rec.containers;
    v_mold_tbl(1).waybill_airbill := rec.waybill_airbill;
    v_mold_tbl(1).expected_arrival_date := rec.expected_arrival_date;
    v_mold_tbl(1).transfer_subinventory := rec.transfer_subinventory;
    v_mold_tbl(1).transfer_organization := rec.transfer_organization;
    v_mold_tbl(1).transfer_to_location := rec.transfer_to_location;
    v_mold_tbl(1).new_average_cost := rec.new_average_cost;
    v_mold_tbl(1).value_change := rec.value_change;
    v_mold_tbl(1).percentage_change := rec.percentage_change;
    v_mold_tbl(1).material_allocation_temp_id := rec.material_allocation_temp_id;
    v_mold_tbl(1).demand_source_header_id := rec.demand_source_header_id;
    v_mold_tbl(1).demand_source_line := rec.demand_source_line;
    v_mold_tbl(1).demand_source_delivery := rec.demand_source_delivery;
    v_mold_tbl(1).item_segments := rec.item_segments;
    v_mold_tbl(1).item_description := rec.item_description;
    v_mold_tbl(1).item_trx_enabled_flag := rec.item_trx_enabled_flag;
    v_mold_tbl(1).item_location_control_code := rec.item_location_control_code;
    v_mold_tbl(1).item_restrict_subinv_code := rec.item_restrict_subinv_code;
    v_mold_tbl(1).item_restrict_locators_code := rec.item_restrict_locators_code;
    v_mold_tbl(1).item_revision_qty_control_code := rec.item_revision_qty_control_code;
    v_mold_tbl(1).item_primary_uom_code := rec.item_primary_uom_code;
    v_mold_tbl(1).item_uom_class := rec.item_uom_class;
    v_mold_tbl(1).item_shelf_life_code := rec.item_shelf_life_code;
    v_mold_tbl(1).item_shelf_life_days := rec.item_shelf_life_days;
    v_mold_tbl(1).item_lot_control_code := rec.item_lot_control_code;
    v_mold_tbl(1).item_serial_control_code := rec.item_serial_control_code;
    v_mold_tbl(1).item_inventory_asset_flag := rec.item_inventory_asset_flag;
    v_mold_tbl(1).allowed_units_lookup_code := rec.allowed_units_lookup_code;
    v_mold_tbl(1).department_id := rec.department_id;
    v_mold_tbl(1).department_code := rec.department_code;
    v_mold_tbl(1).wip_supply_type := rec.wip_supply_type;
    v_mold_tbl(1).supply_subinventory := rec.supply_subinventory;
    v_mold_tbl(1).supply_locator_id := rec.supply_locator_id;
    v_mold_tbl(1).valid_subinventory_flag := rec.valid_subinventory_flag;
    v_mold_tbl(1).valid_locator_flag := rec.valid_locator_flag;
    v_mold_tbl(1).locator_segments := rec.locator_segments;
    v_mold_tbl(1).current_locator_control_code := rec.current_locator_control_code;
    v_mold_tbl(1).number_of_lots_entered := rec.number_of_lots_entered;
    v_mold_tbl(1).wip_commit_flag := rec.wip_commit_flag;
    v_mold_tbl(1).next_lot_number := rec.next_lot_number;
    v_mold_tbl(1).lot_alpha_prefix := rec.lot_alpha_prefix;
    v_mold_tbl(1).next_serial_number := rec.next_serial_number;
    v_mold_tbl(1).serial_alpha_prefix := rec.serial_alpha_prefix;
    v_mold_tbl(1).shippable_flag := rec.shippable_flag;
    v_mold_tbl(1).posting_flag := rec.posting_flag;
    v_mold_tbl(1).required_flag := rec.required_flag;
    v_mold_tbl(1).process_flag := rec.process_flag;
    v_mold_tbl(1).error_code := rec.error_code;
    v_mold_tbl(1).error_explanation := rec.error_explanation;
    v_mold_tbl(1).attribute_category := rec.attribute_category;
    v_mold_tbl(1).attribute1 := rec.attribute1;
    v_mold_tbl(1).attribute2 := rec.attribute2;
    v_mold_tbl(1).attribute3 := rec.attribute3;
    v_mold_tbl(1).attribute4 := rec.attribute4;
    v_mold_tbl(1).attribute5 := rec.attribute5;
    v_mold_tbl(1).attribute6 := rec.attribute6;
    v_mold_tbl(1).attribute7 := rec.attribute7;
    v_mold_tbl(1).attribute8 := rec.attribute8;
    v_mold_tbl(1).attribute9 := rec.attribute9;
    v_mold_tbl(1).attribute10 := rec.attribute10;
    v_mold_tbl(1).attribute11 := rec.attribute11;
    v_mold_tbl(1).attribute12 := rec.attribute12;
    v_mold_tbl(1).attribute13 := rec.attribute13;
    v_mold_tbl(1).attribute14 := rec.attribute14;
    v_mold_tbl(1).attribute15 := rec.attribute15;
    v_mold_tbl(1).movement_id := rec.movement_id;
    v_mold_tbl(1).reservation_quantity := rec.reservation_quantity;
    v_mold_tbl(1).shipped_quantity := rec.shipped_quantity;
    v_mold_tbl(1).transaction_line_number := rec.transaction_line_number;
    v_mold_tbl(1).task_id := rec.task_id;
    v_mold_tbl(1).to_task_id := rec.to_task_id;
    v_mold_tbl(1).source_task_id := rec.source_task_id;
    v_mold_tbl(1).project_id := rec.project_id;
    v_mold_tbl(1).source_project_id := rec.source_project_id;
    v_mold_tbl(1).pa_expenditure_org_id := rec.pa_expenditure_org_id;
    v_mold_tbl(1).to_project_id := rec.to_project_id;
    v_mold_tbl(1).expenditure_type := rec.expenditure_type;
    v_mold_tbl(1).final_completion_flag := rec.final_completion_flag;
    v_mold_tbl(1).transfer_percentage := rec.transfer_percentage;
    v_mold_tbl(1).transaction_sequence_id := rec.transaction_sequence_id;
    v_mold_tbl(1).material_account := rec.material_account;
    v_mold_tbl(1).material_overhead_account := rec.material_overhead_account;
    v_mold_tbl(1).resource_account := rec.resource_account;
    v_mold_tbl(1).outside_processing_account := rec.outside_processing_account;
    v_mold_tbl(1).overhead_account := rec.overhead_account;
    v_mold_tbl(1).flow_schedule := rec.flow_schedule;
    v_mold_tbl(1).cost_group_id := rec.cost_group_id;
    v_mold_tbl(1).demand_class := rec.demand_class;
    v_mold_tbl(1).qa_collection_id := rec.qa_collection_id;
    v_mold_tbl(1).kanban_card_id := rec.kanban_card_id;
    v_mold_tbl(1).overcompletion_transaction_id := rec.overcompletion_transaction_id;
    v_mold_tbl(1).overcompletion_primary_qty := rec.overcompletion_primary_qty;
    v_mold_tbl(1).overcompletion_transaction_qty := rec.overcompletion_transaction_qty;
    v_mold_tbl(1).end_item_unit_number := rec.end_item_unit_number;
    v_mold_tbl(1).scheduled_payback_date := rec.scheduled_payback_date;
    v_mold_tbl(1).line_type_code := rec.line_type_code;
    v_mold_tbl(1).parent_transaction_temp_id := rec.parent_transaction_temp_id;
    v_mold_tbl(1).put_away_strategy_id := rec.put_away_strategy_id;
    v_mold_tbl(1).put_away_rule_id := rec.put_away_rule_id;
    v_mold_tbl(1).pick_strategy_id := rec.pick_strategy_id;
    v_mold_tbl(1).pick_rule_id := rec.pick_rule_id;
    v_mold_tbl(1).common_bom_seq_id := rec.common_bom_seq_id;
    v_mold_tbl(1).common_routing_seq_id := rec.common_routing_seq_id;
    v_mold_tbl(1).cost_type_id := rec.cost_type_id;
    v_mold_tbl(1).org_cost_group_id := rec.org_cost_group_id;
    v_mold_tbl(1).move_order_line_id := rec.move_order_line_id;
    v_mold_tbl(1).task_group_id := rec.task_group_id;
    v_mold_tbl(1).pick_slip_number := rec.pick_slip_number;
    v_mold_tbl(1).reservation_id := rec.reservation_id;
    v_mold_tbl(1).transaction_status := rec.transaction_status;
    v_mold_tbl(1).transfer_cost_group_id := rec.transfer_cost_group_id;
    v_mold_tbl(1).lpn_id := rec.lpn_id;
    v_mold_tbl(1).transfer_lpn_id := rec.transfer_lpn_id;
    v_mold_tbl(1).pick_slip_date := rec.pick_slip_date;
    v_mold_tbl(1).content_lpn_id := rec.content_lpn_id;
    v_mold_tbl(1).transaction_quantity := p_pick_conf_qty;
    v_mold_tbl(1).primary_quantity := p_pick_conf_qty;
    v_mold_tbl(1).shipped_quantity := p_pick_conf_qty;
    INV_PICK_WAVE_PICK_CONFIRM_PUB.PICK_CONFIRM(p_api_version_number => 1.0,
                                                p_init_msg_list      => FND_API.G_FALSE,
                                                p_commit             => FND_API.G_FALSE,
                                                x_return_status      => l_return_status,
                                                x_msg_count          => l_msg_count,
                                                x_msg_data           => l_msg_data,
                                                p_move_order_type    => 3 -- PickWave - Order
                                                p_transaction_mode   => 1 -- 1:On-Line, 2:Concurrent, 3:Background
                                                p_trolin_tbl         => v_moveln_tbl_d,
                                                p_mold_tbl           => v_mold_tbl,
                                                x_mmtt_tbl           => v_mold_tbl,
                                                x_trolin_tbl         => v_moveln_tbl_o,
                                                p_transaction_date   => SYSDATE);
    COMMIT;
    DBMS_OUTPUT.PUT_LINE('Return status of INV_PICK_WAVE_PICK_CONFIRM_PUB.PICK_CONFIRM = ' ||
                         l_return_status);
    IF l_return_status != FND_API.G_RET_STS_SUCCESS THEN
      pStatus := cv_fail;
      pMsgData := 'Failed to pick confirm move order inv_pick_wave_pick_confirm_pub.pick_confirm for MOVE_ORDER_LINE_ID : ' ||
                  vMoveOrderLineId;
      GOTO end_of_pkcnf;
    END IF;
    v_api_pick_confirm := 1;
    dbms_output.put_line('Status of the Pick Confirm is : ' ||
                         l_return_status);
    <<end_of_pkcnf>>
    NULL;
end loop;
END;
Updating Shipping attributes
DECLARE
--Standard Parameters.
p_api_version NUMBER;
init_msg_list VARCHAR2(30);
p_commit      VARCHAR2(30);
--Parameters for WSH_DELIVERY_DETAILS_PUB.update_shipping_attributes.
source_code        VARCHAR2(15);
changed_attributes WSH_DELIVERY_DETAILS_PUB.ChangedAttributeTabType;
--out parameters
x_return_status VARCHAR2(10);
x_msg_count     NUMBER;
x_msg_data      VARCHAR2(2000);
x_msg_details   VARCHAR2(3000);
x_msg_summary   VARCHAR2(3000);
-- Handle exceptions
vApiErrorException EXCEPTION;
BEGIN
-- Initialize return status
x_return_status := WSH_UTIL_CORE.G_RET_STS_SUCCESS;
-- Call this procedure to initialize applications parameters
FND_GLOBAL.APPS_INITIALIZE(user_id      => 0,
                             resp_id      => 21623,
                             resp_appl_id => 660);
source_code := 'OE';
changed_attributes(1).delivery_detail_id := 9317811; -- delivery_detail_id
changed_attributes(1).shipped_quantity := 0; -- quantity to update
changed_attributes(1).cycle_count_quantity := 30;
--Call to WSH_DELIVERY_DETAILS_PUB.Update_Shipping_Attributes.
WSH_DELIVERY_DETAILS_PUB.Update_Shipping_Attributes(p_api_version_number => 1.0,
                                                      p_init_msg_list      => init_msg_list,
                                                      p_commit             => p_commit,
                                                      x_return_status      => x_return_status,
                                                      x_msg_count          => x_msg_count,
                                                      x_msg_data           => x_msg_data,
                                                      p_changed_attributes => changed_attributes,
                                                      p_source_code        => source_code);
                                                      commit;
IF (x_return_status <> WSH_UTIL_CORE.G_RET_STS_SUCCESS) THEN
    RAISE vApiErrorException;
ELSE
    dbms_output.put_line('The shipped quantity is updated with ' ||
                         changed_attributes(1)
                         .shipped_quantity || ' for the delivery detail ' ||
                         changed_attributes(1).delivery_detail_id);
END IF;
EXCEPTION
WHEN vApiErrorException THEN
    WSH_UTIL_CORE.get_messages('Y',
                               x_msg_summary,
                               x_msg_details,
                               x_msg_count);
    IF x_msg_count > 1 THEN
      x_msg_data := x_msg_summary || x_msg_details;
      DBMS_OUTPUT.PUT_LINE('Message Data : ' || x_msg_data);
    ELSE
      x_msg_data := x_msg_summary;
      DBMS_OUTPUT.PUT_LINE('Message Data : ' || x_msg_data);
    END IF;
WHEN OTHERS THEN
    DBMS_OUTPUT.PUT_LINE('Unexpected Error: ' || SQLERRM);
END;
Thanks

Hi,
Goto VTFL.Select you valid combination.
Click on item.Select yout item category there.Goto details.
Select the Pos/neg quantity field as "+".
Maintain the billing quantity as "A".
Maintain VBRK/VBRP as "001".
Save.
Goto VOV7 and select your item category.Details.
Select completion rule as "B" and billing relevance as "F".
Save.
Pls go through the follwing threads that are posted by me earlier.
[Invoice split|Re: Invoice split]
[Splitiing of invoice|Re: Invoice split]
Regards,
Krishna.

COGI error generated while collective order confirmation

hi ALL, this is the real task for all PP GURUS.
the issue is related with collective order confirmation.
client is using customised program ZPP_CONF to confirm the collective order which is based on the sap spro program CORUPROC.this include automatic goods receipt,backflush & actual cost update .as user use zpp_conf for confirmation all this actions happened in backgruond.
now after using ZPP_CONF . the confirmation is not happening .instead of that it is going in COGI where they are getting a error massage which is as follows
"You have no authorization for this transaction with movement type 101u201D
this error continues for 10-15 minutes after doing refresh it goes. & confirmation happens.
this is not happening for all orders but for 8 out of 10.
users have proper authorisations.
they have enough stocks in st. locn.
they are loosing lot of time becuse of this.
HOW CAN I RECTIFY THIS ERROR GURUS?
when i search i found this is written in the CORUPROC documentation
Incl. incorrect goods movement: Not only preselected but also incorrect goods movements that are usually processed with transaction COGI are selected and processed.
VENKADESH

Hi,
The Program CORUPROC only can adjust the Errors in Goods movements. It can not handle the Table Locks..
The Program CORUAFWP, can taek care of table locks also, apart from the Errors in Goods Movements.
Refer below thread for similar type of problem..
COGI errors
Hope this helps..
Regards,
Siva

Link between Service Order / Confirmation in CRM and Purchase Order in ECC

Hi all,
Does anyone knows what the possible link is between a Service Order / Service Order Confirmation in CRM and a Purchase Order in ECC ? I heard that this could be found somewhere in the document flow of a Service Order ....
How do we get the Purchase Order number from ECC in the Document flow section of an Service Order in CRM ?
We need the PO number somehow to be able to create a Goods Received document in ECC from CRM.
BR,
Abjuh

Hello Abjuh,
As of CRM 4.0 (with Service Industry extensions), you can automatically create ECC Purchase Orders from a CRM service order.
It is possible to track the status of the individual service order items with the document flow.
Please refer to the SAP Help for more information.
http://help.sap.com/saphelp_crm70/helpdata/EN/46/8bae7e9e886160e10000000a1553f7/frameset.htm
Kind regards,
Kristoff.

Document number-PM order confirmation by IW41

Hi,
For PM work order confirmations, I want to fetch the document number. In which table can I find the document number stored? I found it in AFRU-CATSBELNR, but only for CATS confirmation. For confirmation of work order through IW41 transaction, is there any table where I get the document number?
Thanks and Regards,
Jegashree

Hi Jane,
I am getting the confirmation number.but not able to fetch the document number (I need this document number to fetch the cost per line item/confirmation from COEP table) Does the PM order confirmation through IW41 transaction have any document number?
Thanks

Production Order confirmed finish date

Good morning,
I have a question concerning the confirmed finish date (GLTRI) on the general tab of the production order header. We have an order that a partial confirmation was done on the last operation with no yield. This was the first confirmation of the order. The general tab shows a confirmed start date and a confirmed finish date. First question is why the confirmed finish date if nothing was completed. The confirmation was then canceled and the start confirmed date was removed but the confirmed finish date remained. More testing revealed if a final confirmation was performed on the last operation where it is set to do an automatic goods movement the start and finish confirm date was filled in. When the confirmation was canceled the start and finish confirmed dates were removed. Has anyone come across this before?

dear John,
I played in our TST system and found the same behaviour (which I consider is a standard).
I can't see this "confirmed dates" settings in config.
It seems like as soon the first entry comes in AFRU system sets the 'Start Confirmed' date even if LMNGA is zero
After cancellation system cleans this field date because the order status comes back to REL (the was only the one zero partial confirmation which was cancelled later). but keeps 'Finished Confirmd' field populated. Of course, the second record in AFRU (the cancellation) is created.
To avoid a misunderstanding I suggest advise your users to run CO14 (display prod.order confirmation) or just use COOIS.
good luck!

Production order confirm thru IDOC

Hello Guru,
we are having problem to our confirm Production order it has COGI error BA deficit on a same material with same batch.
our production order A, B, C, and D are process thru transaction code LM00. afterw that we check the process order thru WE02 and it already has status 64 thats why we do BD20 to Order A,B,C and D (all process in same time) to make it status 53. the problem seems occur after doing BD20 all of this order pick one batch 11111 for component material 123. this cause us 4 COGI error after BA deficit since batch 11111 had no enough stocks to make the requirement of material 123 for the order A, B, C and D.
How was this happen? and how could we fixed this?
Please provide helps
Thanks
Ryan

Hi Rosalinda, i have the same problem. You found some solution ?
Thanks a lot !!!.
Federico Cicerchia

Order confirmation through BAPI

Dear Gurus,
I am having a scenarion for heat treatment proces. In a single HT cycle there is a possibility of clubbing the multiple orders. For example I am having 2 orders... one for material A and another for material B. In these two orders operation 30 (in order A) and operation 40 (in order B) are HT operations. I am creating a group order. In this group order I will select the original order number and operation number (i.e. A-30 and B-40). And in this Z transaction I will mention the total activity consumption... this activity consumption will be segregated based on the weight of each order.
After segregation of activities... I want to trigger the individual operation confirmation. This I am planning with the help of BAPI. I found BAP "". But during the testing (by giving order number, operation number and activity values)... I am receiving message saying that confirmation of order XXXXX saved. But I didn't find this confirmation data in Table. Please let me know ... what could be the reason.
If you need any further clarification, please let me know.
Regards,
Surya.

Hi Surya,
Try the BAPI not from Se37, but from a test program. Also call the BAPI_TRANSACTION_COMMIT so that changes are saved permamnatly.

Order Confirmed - No Order Found

Similar Messages

Maybe you are looking for