Enhancement for picking confirmation inbound idoc

Hi Friends,
I'm using Message type SHPCON , Basic Type Delvry03 and process code DELV for picking confirmation. where as i have to extend the basic type for a field LIPS-UECHA ( Batch split Indicator) which is not avilable in basic type. which userexit or badi i have to use to plopoualte this filed data in to SAP? Can any one help.
Thanks&Regards,
Naren.

Hi,
You exttend the basic IDOC type DELVRY03. To which Segment you want to add this under E1EDL24 or E1EDL37. Change the process code inorder to fetch the data from the application.
WE31 to add the field to the segments and create a new segment
WE30 extend the basic type and add the newly created segment
WE82 to add the extended basic type to Message type.
change the process code.
Regards
Kannaiah

Similar Messages

User-exit / BAdi for Pick Confirmation

Does anyone know any user-exit/BAdi that can be used on 'Pick confirm all entries' option in Delivery change (VL02N) in ECC6.0 environment.
Thanks

Hi,
Try out from the following user exits-----
Transaction Code - VL02N                    Change Outbound Delivery
Exit Name           Description
V02V0001            Sales area determination for stock transport order
V02V0002            User exit for storage location determination
V02V0003            User exit for gate + matl staging area determination (headr)
V02V0004            User Exit for Staging Area Determination (Item)
V50PSTAT            Delivery: Item Status Calculation
V50Q0001            Delivery Monitor: User Exits for Filling Display Fields
V50R0001            Collective processing for delivery creation
V50R0002            Collective processing for delivery creation
V50R0004            Calculation of Stock for POs for Shipping Due Date List
V50S0001            User Exits for Delivery Processing
V53C0001            Rough workload calculation in time per item
V53C0002            W&S: RWE enhancement - shipping material type/time slot
V53W0001            User exits for creating picking waves
VMDE0001            Shipping Interface: Error Handling - Inbound IDoc
VMDE0002            Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003            Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004            Shipping Interface: Message SDPACK (Packing, Inbound)
No of Exits:         17
Regards,
Prashant.

Vendor Acknowledgment for PO using Inbound Idoc.

HI,
I have a scenario, where we send the PO to the supplier through Idoc, which is sucessfully recieved, when the supplier tries to send the acknowledgment for the PO through Idoc the Idoc fails with an error message "Confirmed price cannot be set in document conditions" - A condition type with condition category 'd' is not included among the document conditions. I am using message type as ORDRSP. Can any one please tell me where i would have gone wrong in the settings.
Regards
JJJ

Hi,
As per my assumption If the IDOC is recieved with the Error status.There shouldn't be any problem with settings.Please put the break point in the Inbound function module and test the IDOC in Tcode WE19 and try to find out from where the error is.
Please let me know if you require anything else.
Regards,
Sharath
Edited by: sharath Girmaji on Aug 29, 2008 7:58 PM

Picking confirmation using IDOC

Hi,
I have to create pick confirmation from WMS to SAP. I'm uing SHPCON message type and DELVRY03 basic type and idoc_input_delvry FM from my development. very this is fine i have got all fields reqired in basic type the problem is
1. IF WMS don;t send any pick quantity for line item or if it sends '0' quantity the line item has to be deleted from the Delivery.
2. If in case pick qty is more than the delivery qty it should generate an error.
3.Thre is a concept called Batch split in Outbound delivery. What it the functionality of the batch split.
Can any one come accross these kind of scenario plz help me.
Thanks & Regards,
Naren.

i think u r going to generate the 51 status for the conditions in ur idoc
for 1 and 2 .
Pick quantity is not maintained for the table . The reference for this is the Delivered Quantity.
Goto delivery (vl02n) and enter a delivery now see the delivery qty for a particular item .
say 16 for Del qty now keep pick qty as 0.
and save .
now see the over all pick status . this will be 'A'.
repeat the same process and now keep pick qty as 4 .
and save .
now see the over all pick status . this will be 'B'.
this becomes 'C' means completely picked if the pick qty is eq 16 in this scenario.
i cannot pick 17 as this is out of scope error will be triggered.
<b>Pickup the segment which is populating the pick qty and keep the options above u
and compare it with delivered qty.</b>
for 3 ..
refer this..
Let me put it this way.
The process is suppose a sales order is there
and that is scheduled
16 on dec 29
24 on dec 30
if i create a delivery as of today ie dec 29
then the pick qty is 16
and i create a delivery on dec 30 ie tommow
then the pick qty is 24.
total quantity for that item is 40 (break
16+24).
For this break up u need to look into Vbep
Entries .
This is the process of scheduling where in two
deliveries are created for one sales order .(as
example).
regards,
vijay.

URGENT- Update for picking confirmation & PGI

Hi Experts,
Is there any FM/BAPI to update delivery for both the picking confirmation & PGI.
I am trying to use WS_UPDATE_DELIVERY_2 but it is triggerring me an error at delivery positions.
If it is the correct FM used then plz forward me the parameters for the req.
Thank you,
Sangeetha

Check with below logic :
if flag = 'X'. Assume that flag = X means - PGI else delivery update.
Use FM - WS_DELIVERY_UPDATE
else.
Use FM : SD_DELIVERY_UPDATE_PICKING
endif.
Check the below code for ref PGI ..
REPORT ZWM_OVERWEIGHT_FIX no standard page heading
                           message-id zwm.
======================================================================
Program Name : ZWM_OVERWEIGHT_FIX                                    *
Description : Tool to fix Overweight in delivery line item,         *
               Used All Function module to cancel invoice ,          *
               Reverse the goods issue ,Update Delivery qty,Create *
               invoice                                               *
Author       : Seshu                                                 *
Date         : 05/08/2007                                            *
MODIFICATION HISTORY                                                 *
DATE    | AUTHOR   | CHANGE #   | DESCRIPTION OF MODIFICATION        *
--|||--
05/08/07| Seshu    | DEVK921979 | Initial                            *
D A T A - D E C L A R A T I O N     *******************
Tables
Tables : vbak,
         vbap,
         vbfa,
         likp,
         lips,
         vbrk,
         vbrp.
Internal Tables
data : i_lips like lips occurs 0 with header line,
       i_vbap like vbap occurs 0 with header line.
Variables
data : v_deliv like vbfa-vbelv,
       v_invoic like vbfa-vbelv.
Data Declaration Part for Post Goods Issue
DATA: l_vbeln LIKE likp-vbeln,
      l_vbkok LIKE vbkok,
      i_prot LIKE prott OCCURS 0 WITH HEADER LINE,
      ef_error_any_0 TYPE c,
      ef_error_in_item_deletion_0 TYPE c,
      ef_error_in_pod_update_0 TYPE c,
      ef_error_in_interface_0 TYPE c,
      ef_error_in_goods_issue_0 TYPE c,
      ef_error_in_final_check_0 TYPE c,
      d_return   LIKE bapireturn1.
Internal tables for BAPI Function Module
data : i_cret like BAPIRETURN1 occurs 0 with header line,
       i_csucess like BAPIVBRKSUCcESS occurs 0 with header line,
       i_ret2 like bapiret2 ,
       flag type c,
       i_mesg like mesg occurs 0 with header line.
Data Declaration for Invoice Creation
DATA: VBSK_I     LIKE VBSK.
data: d_success type c.
DATA: XKOMFK LIKE      KOMFK   OCCURS 0 WITH HEADER LINE,
      XKOMV LIKE      KOMV    OCCURS 0 WITH HEADER LINE,
      XTHEAD LIKE      THEADVB OCCURS 0 WITH HEADER LINE,
      XVBFS LIKE      VBFS    OCCURS 0 WITH HEADER LINE,
      XVBPA LIKE      VBPAVB OCCURS 0 WITH HEADER LINE,
      XVBRK LIKE      VBRKVB OCCURS 0 WITH HEADER LINE,
      XVBRP LIKE      VBRPVB OCCURS 0 WITH HEADER LINE,
      XVBSS LIKE      VBSS    OCCURS 0 WITH HEADER LINE,
      XKOMFKGN LIKE    KOMFKGN OCCURS 0 WITH HEADER LINE.
S E L E C T I O N - S C R E E N   ******************
Selection-screen
Selection-screen : begin of block blk with frame title text-001.
parameters : p_vbeln like vbak-vbeln obligatory.
selection-screen : end of block blk.
A T - S E L E C T I O N - S C R E E N ***************
Validation on Sales order
at selection-screen on p_vbeln.
Check the data on VBAK Table
select single vbeln from vbak into vbak-vbeln
                            where vbeln = p_vbeln.
if sy-subrc ne 0.
    message e006 with p_vbeln.
endif.
S T A R T - O F - S E L E C T I O N *******************
Start-of-selection.
break sreddy.
Get the Invoice Number corresponding Sales Order Number
perform get_invoice.
Step 1.
Cancel the Invoice - Transaction VF11
perform cancel_invoice.
Reverse the goods issue
perform reverse_goodsissue.
Get the Order and Delivery Items
perform get_sales_deliv.
Delivery Change
perform Delivery_change.
Create Invoice document
perform invoice_create.
E N D - O F - S E L E C T I O N *******************
end-of-selection.
if flag = 'X'.
message i012 with p_vbeln.
endif.
*&      Form get_invoice
      Get Invoice Number
FORM get_invoice.
Clear Variables
clear : v_deliv,
          v_invoic,
          flag.
Get the Delivery Number First
select single vbeln from vbfa into v_deliv
                           where vbelv = p_vbeln
                           and   vbtyp_n = 'J'.
if sy-subrc ne 0.
    message i004 with p_vbeln.
    stop.
endif.
Get the Invoice Number
select single vbeln from vbfa into v_invoic
                           where vbelv = p_vbeln
                           and   vbtyp_n = 'M'.
if sy-subrc ne 0.
    message i003 with p_vbeln.
    stop.
endif.
ENDFORM.                    " get_invoice
*&      Form cancel_invoice
      Cancel the Invoice
FORM cancel_invoice.
clear : i_ret2,
          i_cret,
          i_csucess.
refresh : i_cret,
            i_csucess.
CALL FUNCTION 'BAPI_BILLINGDOC_CANCEL1'
    EXPORTING
      BILLINGDOCUMENT       = v_invoic
TESTRUN               =
NO_COMMIT             =
BILLINGDATE           =
    TABLES
      RETURN                = i_cret
      SUCCESS               = i_csucess
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
       EXPORTING
            WAIT   = space
       IMPORTING
            RETURN = i_ret2.
read table i_cret with key type = 'E'.
if sy-subrc ne 0.
    message i005 with v_invoic.
    stop.
endif.
ENDFORM.                    " cancel_invoice
*&      Form reverse_goodsissue
      Reverse the goods Issue
FORM reverse_goodsissue.
Local Variable
data : lv_vbtyp like likp-vbtyp.
clear : i_mesg,
          lv_vbtyp.
refresh : i_mesg.
select single vbtyp from likp into lv_vbtyp
                           where vbeln = v_deliv.
CALL FUNCTION 'WS_REVERSE_GOODS_ISSUE'
    EXPORTING
      I_VBELN                         = v_deliv
      I_BUDAT                         = sy-datum
    I_COUNT                         =
    I_MBLNR                         =
    I_TCODE                         =
      I_VBTYP                         = lv_vbtyp
    TABLES
      T_MESG                          = i_mesg
   EXCEPTIONS
     ERROR_REVERSE_GOODS_ISSUE       = 1
     OTHERS                          = 2
if sy-subrc ne 0.
    message i007 with v_deliv.
endif.
ENDFORM.                    " reverse_goodsissue
*&      Form get_sales_deliv
      Get the Sales order and Deliv Items
FORM get_sales_deliv.
Local Variables
data : lv_kwmeng like vbap-kwmeng.
clear : i_lips,
          i_vbap.
refresh : i_lips,
            i_vbap.
Select the data from LIPS
select * from lips into table i_lips
                     where vbeln = v_deliv.
if sy-subrc ne 0.
    message i008 with v_deliv.
    stop.
endif.
sort i_lips by vbeln posnr.
Get the Sales order Item Data.
select * from vbap into table i_vbap
                          where vbeln = p_vbeln.
if sy-subrc ne 0.
    message i006 with p_vbeln.
    stop.
endif.
sort i_vbap by vbeln posnr.
Compare delivery Item and Order Items
loop at i_lips.
    clear lv_kwmeng.
    read table i_vbap with key posnr = i_lips-posnr.
    if sy-subrc eq 0.
      lv_kwmeng = i_vbap-kwmeng * 2.
      if lv_kwmeng >= i_lips-lfimg.
        i_lips-lfimg = i_vbap-kwmeng.
        modify i_lips.
      endif.
    endif.
endloop.
ENDFORM.                    " get_sales_deliv
*&      Form Delivery_change
      Delivery Update
FORM Delivery_change.
Clear : i_prot.
refresh : i_prot.
Delivery Update
CALL FUNCTION 'LE_MOB_DELIVERY_UPDATE'
       EXPORTING
            do_commit                = 'X'
       TABLES
            t_delivery_items         = i_lips
            prot                     = i_prot
       EXCEPTIONS
            conversion_overflow      = 1
            essential_data_missing   = 2
            error                    = 3
            nothing_to_update        = 4
            lock_after_update_failed = 5
            error_in_delivery_update = 6
            OTHERS                   = 7.
COMMIT WORK.
IF sy-subrc <> 0.
    MESSAGE i009 with v_deliv.
endif.
Post Goods Issue
CLEAR:    d_return,
            i_prot,
            l_vbeln,
            l_vbkok.
REFRESH i_prot.
CLEAR: ef_error_in_item_deletion_0    ,
          ef_error_in_pod_update_0       ,
          ef_error_in_interface_0        ,
          ef_error_in_goods_issue_0      ,
          ef_error_in_final_check_0      .
carry out goods issue
l_vbeln          = v_deliv.
l_vbkok-vbeln_vl = l_vbeln.
l_vbkok-wabuc    = 'X'.
carry out goods issue
l_vbeln          = v_deliv.
l_vbkok-vbeln_vl = l_vbeln.
l_vbkok-wabuc    = 'X'.
SET UPDATE TASK LOCAL.
CALL FUNCTION 'WS_DELIVERY_UPDATE'
       EXPORTING
            vbkok_wa                    = l_vbkok
            synchron                    = 'X'
            no_messages_update          = ' '
            update_picking              = 'X'
            commit                      = 'X'
            delivery                    = l_vbeln
            nicht_sperren               = 'X'
            if_error_messages_send_0    = space
       IMPORTING
            ef_error_any_0              = ef_error_any_0
            ef_error_in_item_deletion_0 = ef_error_in_item_deletion_0
            ef_error_in_pod_update_0    = ef_error_in_pod_update_0
            ef_error_in_interface_0     = ef_error_in_interface_0
            ef_error_in_goods_issue_0   = ef_error_in_goods_issue_0
            ef_error_in_final_check_0   = ef_error_in_final_check_0
       TABLES
            prot                        = i_prot
       EXCEPTIONS
            error_message               = 1
            OTHERS                      = 2.
if sy-subrc ne 0.
    message i010 with v_deliv.
else.
    COMMIT WORK .
endif.
ENDFORM.                    " Delivery_change
*&      Form invoice_create
      Invoice Creation
FORM invoice_create.
refresh: XKOMFK, XKOMV,
           XTHEAD, XVBFS,
           XVBPA, XVBRK,
           XVBRP, XVBSS.
clear : XKOMFK, XKOMV,
           XTHEAD, XVBFS,
           XVBPA, XVBRK,
           XVBRP, XVBSS,
           VBSK_I.
VBSK_I-SMART = 'F'.
XKOMFK-VBELN = v_deliv.
XKOMFK-VBTYP = 'J'.
APPEND XKOMFK.
CALL FUNCTION 'RV_INVOICE_CREATE'
       EXPORTING
            VBSK_I       = VBSK_I
            WITH_POSTING = 'C'
       TABLES
            XKOMFK       = XKOMFK
            XKOMV        = XKOMV
            XTHEAD       = XTHEAD
            XVBFS        = XVBFS
            XVBPA        = XVBPA
            XVBRK        = XVBRK
            XVBRP        = XVBRP
            XVBSS        = XVBSS.
if sy-subrc eq 0.
    COMMIT WORK.
   flag = 'X'.
else.
message i011 with p_vbeln.
endif.
ENDFORM.                    " invoice_create
Thanks
Seshu

Confirm Inbound IDOC FM

Hi,
Please confirm whether this FM can be used to post the inbound cycle count.
L_IDOC_INPUT_WMINVE
Let me know whether it relates to li11n transaction.
Regards,
B.Anandh

Yes to both.

How to create the INBOUND Function Module for INBOUND IDOCs

Hi Friends,
Can any Suggest me How to proceed to Create an INBOUND Function Module for Processing the INBOUND IDOCS
which are recieved from XI Server ?
I am working in SAP-ISU
Here i will recieve the INBOUND IDOCs for the Meter Reading Orders.
We have a Standard INBOUND FUNCTION MODULE
IDOC_INPUT_ISU_MR_UPLOAD
which Uploads the Meter Reading Results.
I copied the Same function Module into ZIDOC_INPUT_
and working on it.
Can any one suggest me, whether i am going in correct way or not.
In IDOC_INPUT_ISU_MR_UPLOAD Inbound fun module,
BAPI_MTRREADDOC_UPLOAD is used to Update or Insert the Meter Reading Results,
My requirment is to Insert and Update the Meter Reading Orders which are Inbounded from XI.
Can I Use the Same BAPI
BAPI_MTRREADDOC_UPLOAD
to Update the below fields,
EABL-SERNR
EABL-ZWNUMMER
EABLG-ABLESGR
EABL-V_ZWSTAND
EABL-N_ZWSTAND
EABL-ABLHINW
EABL-ZSKIPC
EABL-ADAT
EABL-ATIMTATS
EABL-ADATTATS
EABL-ATIM
EABL-ZMESSAGE
EABL-ABLESER(Meter reader number)
Kindly Suggest me,
Thanks in Advance,
Ganesh

Hello Ganesh
I think you are going completely astray with you z-function module for IDoc processing.
If you look at TABLES parameter METERREADINGRESULTS (type BAPIEABLU ) of BAPI_MTRREADDOC_UPLOAD you will find many of the requested fields already:
EABL-SERNR => BAPIEABLU-SERIALNO
EABL-ZWNUMMER =>REGISTER
EABLG-ABLESGR
EABL-V_ZWSTAND
EABL-N_ZWSTAND
EABL-ABLHINW
EABL-ZSKIPC
EABL-ADAT
EABL-ATIMTATS => ACTUALMRTIME
EABL-ADATTATS => ACTUALMRDATE
EABL-ATIM
EABL-ZMESSAGE
EABL-ABLESER(Meter reader number)
Field EABL-ZMESSAGE appears to be custom field (at least I cannot find it on ECC 6.0). If this field was added using include CI_EABL then you probably can get these values into the BAPI using the EXTENSIONIN parameter.
Check routine CHECK_UPLOADRECORDS in the BAPI which allows two extension structures:
- BAPI_TE_EABL
- BAPI_TE_EOSB
Not surprisingly BAPI_TE_EABL contains the include CI_EABL.
Regards
Uwe

Creation of Service Contract from Inbound IDOC

Hi Experts,
I am using Inbound IDOC type ORDERS02 with message type ORDERS for creation of Sales Order. Now my requirement is like to create a Service Contract from that Inbound IDOC. The IDOC type contains all the data require to create a Service Contract. The scenario is like, after creation of Sales Order it will check for the corresponding Service Contract exits or not by querying on a Z table which contains all those entries.
So my idea is to create a Z Program, in which it will check for the Service Contract and will create the same by reprocessing the same IDOC or by calling some Function Module. Please suggest how shall i proceed to create a Service Contract.
Is there any way to reprocess the IDOC or to collect the Data from the IDOC segments pass them to a FM which is responsible for creation of Inbound IDOC. Please suggest if this is feasible.
Thanks in Advance.
Regards,
Priyabrata.

Actually there is problem with BDCDATA. Inside the FM it's calling transaction with help of BDCDATA. If i am creating a Sales order or contract alone its creating successfully. But when i am trying to create both, it's retuning sy-subrc '1001' after calling the transaction on the second attempt. Is there any problem with BDCDATA like we can't handle with less time gap? Please help and give your inputs.
Regards,
Priyabrata

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.

Inbound IDOC & Comminication in Nomination

We have a scenario on the Mining industry where we created nomination (T Cd : O4NSN ) for transport of coal by railways . The outbound communication IDOC was successfully sent to a Transport Agency and is reflected in the u201C Communication Tabu201D of the Nomination.
I am getting following issues :
1. Subsequently , the Transporter/railways has send a back a communication via incoming Idoc which fails with following Eror Message : EDI: Partner profile not available
We have tried to create the partner function for processing of Inbound Idoc with following data .
Message type     : OIJ_NOM_COMM
Basic Type     : OIJ_NOM_DETAIL01
Partner Type     : KU
Can you please inform me the approriate Process Code for the inbound IDOC ?
2. Also I have noticed that that During Outbound Communication to the transporter the u201CActionu201D (Communication Tab of Nomination) field idicates as u201C Current Itemu201D. But my understanding is that it should show status : u201C New entry sentu201D .
Can you please guide on how I can define the partner function and resolve these issues .

An inbound IDOC in error will have the status 51, & it is marked for deletion it has a status of 68.
http://www.dataxstream.com/2009/10/mass-status-change-sap-idoc/
http://wiki.sdn.sap.com/wiki/display/ABAP/IDoc+Statuses
Edited by: Krupaji on May 6, 2011 2:38 PM

Inbound idoc failing to reach SAP system.

Hi All,
We are upgrading our SAP system from release 700 to 730. Post upgrade we have identified that idocs which are supposed to reach SAP as inbound are failing in Biz Talk with below message.
Error details: Microsoft.ServiceModel.Channels.Common.XmlReaderParsingException: The segment name is not valid for the IDOCTYP, Release, or CIMTYP. Segment name: E2EDT37003GRP IDOCTYP: SHPMNT03 Release: 700 CIMTYP: . Ensure that your message xml validates against the operation schema.
This happening for only one inbound idoc which is using SHPMNT03 idoc.Whereas other inbound idoc which is using /AFS/ORDERS05 idoc is reaching SAP without any issues. I am bit confused why this is happening for idoc SHPMNT03.
Please let me know your thoughts.
Thanks,
Gowrinath.

Hi Ramya,
Thanks for your response.
In Biz Talk schema is designed for 700 release idoc.Whereas our system is upgraded to 731 release.
Hotfix is for Biz Talk. Can't we implement any solution in SAP side.
Thanks,
Gowrinath.

Enhancement for inbound idoc posting(idoc_input_ordrsp)

hi,
please find solution for the below.
business senario: when the vendor send purchase order confirmation through idoc a automated acknowledgement has to be send.
technical: when vendor send idoc (orders05) it updates with FM (idoc_input_ordrsp) our system.
but in the idoc a segment E1EDP19 will have the field IDNLF which has to be filled to send a acknowledgement .
in my case:
the user some times will fill the segment so to get automated acknowledgement we have to write an enhacement to populate the segment in inbound FM.
i have written code in EXIT_SAPLEINM_007. and populated the data in internal table. but the changed data in internal table is not reflecting in processed idoc(in we02 direction 2).

idoc_data is the intenal table which hold all the segment data in run time.
now i fetched matnr from ekpo table populated E1EDP19
and modified the internal table by adding idoc_data-sdata when idoc_data-segnam is E1EDP19 .
ultimately the sdata is reflecting in the idoc_data-sdata for the segment.
but when we check in we02 for the processed idoc the changes are reflecting.
give me a solution for the data to reflect in processed idoc.

Enhancement for inbound idoc

Hi gurus
one help....
i need to read the of purchase requsition from inbound idoc , basic type purqchg02
iam unable to find its exit, plz help me asap....

idoc_data is the intenal table which hold all the segment data in run time.
now i fetched matnr from ekpo table populated E1EDP19
and modified the internal table by adding idoc_data-sdata when idoc_data-segnam is E1EDP19 .
ultimately the sdata is reflecting in the idoc_data-sdata for the segment.
but when we check in we02 for the processed idoc the changes are reflecting.
give me a solution for the data to reflect in processed idoc.

User exits for delivery picking confirmation and transfer order creation

Hi
We have a scenario for which we need help.
This is to do with replenishment from plant to plant.
We have sales sets.
The sales sets needs to be replenished from one plant to another. We want the componenets of the sales sets to picked from the issuing plant. For this we need a transfer order. this needs tobe confirmed and then the goods issue should take place from the issuing plant. Its a two step process.
we are doing Sales sets in STO. The explosion takes place in STO. However when we create deliveries for this. Only the sales set header item without its components are flowing into the delivery.
The Tranfer order does not contain the components either.
However post the goods issue we can create a TO with reference to the TR. This is is not acceptable because we want the picking and confirmation to occur before PGI from the issuing plant.
Could anybody help: We want the TO to be created with the components even though in the delivery only the Sales set header appears. Can u suggest a user exit in which when we create the TR from the delivery the components of the set.
After confirmation of the TO then we want the picking status to be put as C.
Supreeth

Hi,
Check the following users exits.
MWMRFSSG            user exit for sorting TOs in RF system-guided transaction
MWMRFUP             Customer defined general purpose pushbutton called from scr.
MWMRP001            Cust. Exit for Fixed Bin Replenish.: Delivery Item Selection
MWMRP002            Cust. Exit for Fixed Bin Replenishment: TR Quantity Distr.
MWMRP003            Customer Exit for Replenishment using RLLNACH1
MWMRP004            User Exit for Replenishment using RLLNACH4
MWMTO001            Enhancements for end of transfer order generation
MWMTO010            Exit: Calculation of Total Planned TO Processing Time
MWMTO011            Correction of Planned Processing Time for TO Item
MWMTO012            Correction of Sorting and Split Transfer Order
MWMTO013            Stock Removal for Sev. Storage Types as in Stringent FIFO
MWMTOAU3            Separate selection of posting changes for autom.TO creation
MWMTR001            Exits at the end of transfer rqmnt creation (IM,PP interf.)
MWMD0001            Transfer order print via RLVSDR40
MWMD0002            Transfer order print as multiple process with RLKOMM40
MWMIDI07            Enhancement for Output WMPIHU (Create Pick-HU) Inbound
MWMIDO11            Enhancement for message WMTORD: TO with several items
MWMIDO12            Enhancement for Output WMPIHU (Pick-HUs) Outbound
MWMIDO13            Extension for WMMBXY (subsequent tasks after goods movement)
MWMPP001            Enhancement WM/PP Interface (automatic TR generation)
Regards,
Murali

Inbound idoc for updating delivery date of purchase order

Hi All,
Our vendor sends a delivery file consisting of delivery date and quantity(could be partial) for line items of a purchase order.
I need to update the Purchase order line item with the delivery date and quantity sent from the Vendor. It should add a new confirmation line with custom confirmation category in the confirmation tab of the line item in the Purchase order.
Each time we get a delivery file we need to add a new confirmation line in the confirmation tab of the purchase order line item.
How can I get this working using inbound idoc processing? Which Idoc type should I use to solve my issue. Will ORDERSP work for my scenario?
Thank you,
Sonali.

>
sonali ashi wrote:
> We have all EDI set up done for ORDERSP idoc in our system. Problem when I use this idoc type by default system is always adding confirmation catgeory 'AB' but we want our custom category to be added instead of 'AB'.
> Edited by: sonali ashi on Dec 23, 2010 9:47 PM
Confirmation category used for order acknowledgement is define in configuation. You can change that from AB to your custom condition and EDI should pickup that.
SPRO->Material Management->Purchasing->Confirmation->Define Internal Confirmation Category
>
sonali ashi wrote:
> I have also noticed that 'AB' confirmation accepts only full quantity order acknowledgement through Idoc processing.
> Manually I can add a "AB" confirmation for partial quantity but in the idoc processing it fails.
> Edited by: sonali ashi on Dec 23, 2010 9:47 PM
Check tolerance limit defined for confirmation category in 'Conformation Control' Node in SPRO at same level as above.
Regards,
Pawan.

Enhancement for picking confirmation inbound idoc

Similar Messages

Maybe you are looking for