Confirm sales order with idoc ORDERS05

Hi everybody.
I´d like to know if it´s possible to confirm a sales orders with idoc ORDERS05 and message type ORDCHG and posting FM IDOC_INPUT_ORDCHG_VMI.
How would I have to fill the idoc data??
Thanks a lot

Hi,
For inbound idoc you can use the message Orders , process code ORDE and the function mdoule IDOC_INPUT_ORDERS to create a sales order.
Regards,
Nagaraj

Similar Messages

Creation of sales order via IDoc ORDERS05 - specify a reason of rejectio

Hi,
I want to create a sales order via IDoc (type:ORDERS05), i specify for an E1EDP01 segment a reason of rejection (ABGRU),
The sales order is created succefully by calling the FM IDOC_INPUT_ORDERS but the order quantity of the item where i have specified a reason of rejection is equals to 0.
Is this normal? i want that this will take 3 value either 0?
Could anyone help me?
Thx

Hi,
Thank you for ur answer.
I've followed the procedure that you have explained and the Quantity 3 have been succefully passed to VA01 but is set to zero when i execute the next OK-CODE (=UER2, i think it is llike Enter button ). I simulate the same procedure by creating a sales order on VA01 and i've finally found the problem : at item level, if i enter the Material (MATNR), the order Quantity (KWMENG) and the Reason of rejection (ABGRU), the quantity is set to zero after clicking the enter button ; but if i enter only The material and The quantity followed by enter button, and enter after the Reason of rejection, it works fine, the Quantity doesn't change.
What is the solution that you propose to me?
I've try this one on debugger mode:
The FM which interpret the Idoc create the sales order by CALLING TRANSACTION 'VA01' USING bdcdata....
I've modified the bdcdata to implement the sequence of the steps before (MATNR + QTY <ENTER> ABGRU <ENTER>).
1. Is it possible to code this modification?
2. Is there a way to structure the Idoc for having this sequence in bdcdata?
Thanks in advance!
Narivelo

Problem creating sales order using IDoc ORDERS05 (Inbound)

Hello Experts,
We are trying to create a sales order using the IDoc ORDERS05 with process code ORDE for creating sales order. I am getting the following error "VKORG, VTWEG, SPART cannot be determined for customer 0000006000 , vendor
Diagnosis
No sales organization, distribution channel or division were sent to the IDOC. This data is necessary if a sales order is to be added automatically. If this data is unavailable, you cannot create a sales order document.
I was not able to find the fields to fill the distribution channel and divison in the Idoc structure. I have filled in Sales organization in E1EDK14 segment as 3000.
I am not able to figure out the cause for the error.
Same data works fine from BAPI_SALESORDER_CREATEFROMDAT2.
Please help.
Thanks,
Suma
Edited by: Suma B on Jun 17, 2008 11:12 AM

Hello Suma
In this case I would recommend to debug the IDoc processing.
Call transaction WE19 and start the inbound processing of your IDoc in debugging mode. The error message will most likely occur in function module IDOC_INPUT_ORDERS.
LOOP AT idoc_contrl.
* SET/GET Parameter und interne Tabellen neu initialisieren
* initialize SET/GET Parameter and internal tables
    PERFORM initialize_organizational_data.
* IDOC-Segmente in die entsprechenden Anwendungsdaten übernehmen
* Move IDOC to internal tables
    PERFORM interpret_idoc_orders.                    "<= check here
* Prüfen ob gewisse Segmente gefüllt sind
* check IDOC-Segments
    PERFORM check_idoc_segments.                 "<= check here
* Prüfen und Ermitteln von Organisationsdaten
* check internal tables and determine organization data
Regards
Uwe

Configuration data on sales order not update with idoc ORDERS05

Hi All,
I'm trying to post Inbound ORDERS05 to create a sales order with configuration data. In particular i'm using the messsage type ORDERS, process code J3AA (identification J_4A_IDOC_INPUT_ORDERS).
On the IDOC tree, segments E1CUREF,E1CUCFG,E1CUINS,E1CUVAL are correctly valorized.
It is creating the order but not updating the configuration data, can someone please let me know if there are other fields/Segments that need to be populated in order to get the config updated in the sales order ?
Thanks
Piergiorgio

Hi ,
I am facing similar issue ( Configuring data in orders idoc )
Please give your inputs if your successfully
Thanks,
Raghu..

Create a Sales Order with Reference to Contract using IDoc / LSMW ( AFS )

Hi Gurus,
I need to crate a Sales Order with reference to a Contract. I need to upload Sales Orders with reference to contract via LSMW.
So far, I've been able to create the Sales Order with ref to contract. But, the Sales Order Quantity is not getting deducted from the Original Qty in Referred Contract ( When try to create another Sales Order referring to the same Contract.) When a Sales Order is created manually, this is working fine.
Please tell me if I've missed some parameter which stopping it create the link to exact schedule line ( Sizes level )
The Details of the IDoc which is been created via LSMW are as follows;
Message Type: ORDERS
Basic Type     : /AFS/ORDERS05
Process Code : ORDE / DELO
( Tried with both process codes. But the Identification is the same for both: IDOC_INPUT_ORDERS )
*_In Header;_
Segment : E1EDK02 - IDoc: Document header reference data *
Qualifier : '043' - Vendor Contract Number ( Tried with ' 005' - Customer Contract, but it's not working )
Contract Order is mapped for field BELNR
*_In Item;_
Segment : E1EDP02 - IDoc: Document Item Reference Data *
Qualifier : '043' - Vendor Contract Number ( Tried with ' 005' - Customer Contract, but it's not working )
Contract Order is mapped to field BELNR
Line Item of the Contract is mapped to field ZEILE
I also tried passing the Schedule line of Contract in Segment : E1J3P01 AFS IDoc: Doc.item general data
to following fields;
J_3AETENV
J_3AVGETE
/AFS/UETENR
Still its not getting updated in the VBEP also..
Please help me with regard to this. Points will be awarded for your valuable contribution.
Thanks.

Hi,
This issue is been resolved.
One of my friend helped me with resolving this issue..
Once the below mentioned configurations were done on SPRO, the Sales Order was created with reference to Contract and the Qty was reflected when tried to create a new Order referring the same contract.;
u2022     SPRO --> SD -->Sales --> Sales Documents --> Sales Document Header --> Define Sales Document Types --> Field : Outline agreement message; from blank to u201CBu201D.
u2022     SPRO -->SD -->Sales --> Sales Documents --> Sales Document Header --> Maintain Sales Document Types for AFS --> Field : Outline agreement message; from blank to u201CAu201D

Reference contract within Sales order supplied by ORDERS05 IDOC

I am creating Distributed sales orders using IDOC of type ORDERS05. The orders are being raised okay upto now, but now I want to perform various checks against a reference contract should one be added to the IDOC. The IDOC segment E1EDK02 with a qualifier of '005' (Customer contract) can be used to supply the reference contract. I'm using one of the supplied BADI's to process segments that are not catered for in the SAP standard code, however, I don't know where to populate the supplied reference contract number within the deep structure CRMXIF_BUSTRANS that is available for this purpose.
Has anyone ever processed a reference contract in this manner ?.
Blue

I have found a table within the deep structure CRMXIF_BUSTRANS called DOC_FLOW which seems to have all the necessary fields, I think. However, it's going to be a lot of trial and error to determine what needs to be populated in this table to successfully create a Preceding doc in the doc flow of the Sales order raised. The preceding document being of type CONSIP/reference contract.
If anyone has ever populated this data I would be most keen to identify the exact fields entered.
Blue

ERROR IN CREATING SALES ORDER,USING IDOC TYPE ORDERS05

I am using exit to write my code for creating sales order of IDOC Type ORDERS05 and order type ZDRX.
IF I proceess the Idoc in background each time error message comes
FIELD kuwev-kunnr(ship to party)is not an input field.
but if i run in foreground in debugging mode,sales order is getting created..
please suggest something.

If thats not working..
try BAPI_SALESORDER_CREATEFROMDAT2
If BAPI is not working. try creating a bdc for the same if there's not error on trying from VA01

How create sales order with respect to an idoc?

hi ,
does any one know how to create a sales order using an idoc number ?
thanks
mmn

Hi refer below Reward if helps
XI IDOC ORDERS04 create sales order update VBKD_BSARK
For creating sales documents (sales order) through IDOCS you will have to use the T code WE19. In that click basic type and enter order05(IDOC type) and select via message type then enter ORDERS(message type), click execute.
You will get to see many fields.here you have to enter the datas that you enter in the VA01 screen in order to create sales order. The datas such as material name, date, qty, P.O no etc. After entering all the datas, you click standard inbound the IDOC would be created by the system.You can see the created order by going in to VA03 screen.
Next time when you create the IDOC, in same tcode WE19 screen, click existing IDOC and enter the IDOC which you created in the above step and just change the P.O no.Sytem will create new sales order through new IDOC
Before doing all you need to maintain the partner profile in T code WE20. For this Discuss with EDI consultant.

Sales Order Outbound IDOC - Restricting Items being created with a Segment

Hi,
I have a requirement to restrict segments being created for Items (Child) in Sales Order Outbound IDOC based on conditions in the Items (Parent & Child). Can you please suggest me a suitable solution?
Basic Type: ORDERS05, Message Type: ORDRSP. What is the IDOC Function Module to be used to create Outbound IDOC for Sales Order?
Appreciate Your Help.
Thanks,
Kannan
Edited by: Kannan SA on Jan 3, 2008 3:03 PM

Hi,
if the segments are mandatory then you can't trigger the idoc without those segments.
Otherwise, you can read the segment and clear all the data in it, the segment will not be attached to the outbound idoc.
Where to do it? Search the CALL CUSTOMER-FUNCTION '002' for the outbound idoc for example IDOC_OUTPUT_INVOICE for Invocing.
Regards,
Baburaj

Sales orders with credit issues taking availability stock

Hi,
I am doing confirmation using Global ATP in APO. The confirmation is well done, but the confirmed quantity for sales orders with clients that have credit issues is taken the available sotck for other sales orders with ok clients that I want to confirm the quantity they ordered.
For example:
Stock: 10 PC
Client A order 15 PC and 10 are confirmed, but the ordered is retained becuse of credit issues with client A.
Then client B order 3 PC, but nothing is confirmed because the ordered for client A is reserving the stock (note: this would be ok if client A had not credit issues).
So, I want that the 3 PC for client B are confirmed and the 10 PC not reserved for the cient A while client A has credit issues.
How could I configured, so that the orders with credit issues do not reserve stock for the incoming orders?
Thanks a lot.

Hi DB49,
thanks for the quick answer.
I checked the configuration in the R3 and seems to be fine. To prove it, I disconnect APO and did the availability check in the R3 system and it is working fine; the orders quantities that are blocked because of credit issues, do not reserve stock for incoming orders.........son new incoming orders are well confirmed.
But after connecting APO the problem continues. I checked the next points.
In R3 transaction CO09: takes to the APO screen and you see the ATP available quantity OK (do not consider the quantities of the credit issues orders). But at the moment that you make the order (VA01) it does not confirm any stock and if you select the line and go to the ATP screen (the same you get from the CO09) the quantities of credit issues orders are taken into account..the ATP availability quantity changes from the first going directly from the CO09.
What could it be?
Note: it was working fine with APO, I started to have the issue after implementing note 1262475 in APO. This note was becuase the BAPI_APOATP_CHECK was not brigning any value for the ATPQTY_***.
Thanks a lot!!!

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.

VL10E report should show only sales order with complete stock

Hello Friends,
I have to make-to-order scenario. While creating a sales order the system proposes a delivery date based on the inhouse production day maintained in the material master.
In VL10E the system gives list of Sales Order for which delivery is due on that particular date. It does not check whether actually the material is really available on that date for the concerned sales order.
Is there any scope ( any config change or user_exit) which will show only the sales order with complete stock confirmed through production order in the VL10E report.
Regards
Debesh

Hi,
Check userexit LV50R_VIEWG02. If CF_SUBRC = 1 you will not see it in the list. For this purpose in the interfase you have the information in IS_VBEP. Set a break-point and check the conditions.
For more info check the Note 198137 - VL10: Customer-specific enhancements / user exits
I hope this helps you
Regards
Eduardo

EDI: creating a sales order with reference to contract

Dear gurus,
we would like to create a sales order with reference to a SD contract from an ORDERS IDoc.
OSS say we have to populate the E1EDx02 segments with the contract number to do this.
We tested this in our system by manually editing the incoming IDoc and this is what we found:
- qualifier u201C005 : Customer Contract Numberu201D set and BELNR = u201Cthe customeru2019s outline agreement number in his MMu201D (= normal MM behaviour) -> reference is not processed at all, sales order is created without reference
- qualifier u201C043: Vendor Contract Numberu201D set and BELNR = our contract number in SD -> Sales order successfully created. BUT where can I store an external outline agreement number in MM so that the BELNR in the IDoc is populated with it?
- qualifier u201C058: Customer Contract Numberu201D set and BELNR = the customeru2019s outline agreement number in his MM -> Error:
The system could not determine a contract number
Message no. VG226
Diagnosis
The system could not determine a contract number for the selection criteria: external contract number 5100000020 and customer number 0044000004.
This error appears although we maintained the external number 5100000020 in the PO number field (VBKD-BSTKD) in our SD contract.
Could anyone please explain what we do wrong?
Cheers
Alicia

Hi again,
@Lakshmipathi: Thank you, but it is VG226, like I wrote. But still, the OSS note is interesting: "You create a sales order with reference to an MM contract using EDI." Where's the sense in that? Why would I ever want to create a sales order with reference to an outline agreement in MM???
@Rags: Sure we could do that, but I find it hard to believe that there is no standard way to do this. Especially given there are plenty of OSS notes stating that this is possible, e.g. note 562710.
Any other ideas?
Cheers
Alicia

Credit sales order with credit check without top up limit

Hi Experts,
I have a silly question, just wanted to confirm is this possible in SAP system?
I have check thru seem no such function.
My user requested a requirement is credit sales order with credit limit check however without top up credit limit to specific customer. eventually allow this specific customer sales order, delivery order without blocking and created succesfully?
Thanks & Regards,
Yong Kok Wah

Hi,
Use a seprate risk category for such customer. In OVA8 Setting for the given risk category set the Credit Limit Seasonal factor.
By means of above setting system will support the concept of TOP Up credit limit (for a given time period) for given customer against said credit limit.
Regards
Digambar Pandey

Creation of sales order from idoc; items referencing to different contracts

Hi All,
My requirement is to create sales order from an idoc.
IF a sale order contains multiple items , then the order should be created with contract referenced
-at the So item level, the valid contract found for each material is different
hence am not able to use the following bapis
BAPI_SALESORDER_CREATEFROMDAT2 is not triggering the copy controls.
BAPI_SALESDOCUMENT_COPY i can give only one reference document
Please help
Thanks
Deepa

Hi Deepa,
Following link can help you for creating sales order with reference
http://msdn.microsoft.com/en-us/library/cc185190.aspx
http://www.sap-img.com/fu036.htm
Award points if useful
Thanks,
Ravee..

Confirm sales order with idoc ORDERS05

Similar Messages

Maybe you are looking for