Change Inbound Delivery(VL32N) using BAPI.

Hi Experts,
                  Which BAPI can I use to change the Shiping & Administration data of Inbound Delivery (VL32N).
                  I would be passing the Inbound delivery No. as the input to BAPI.
                  Please suggest me the BAPI thru which I can change the above Inbound delivery data.
                  Thanks in advance for your answer & support.
Regards
Jitendra Gujarathi.

Hi,
   Please try the BAPI BAPI_SHIPMENT_CHANGE.
Regards
Raj.

Similar Messages

  • Change Inbound Delivery(BAPI_INB_DELIVERY_CHANGE )

    Hi All,
    I want to change Inbound delivery Header and Item Data By useing BAPI- BAPI_INB_DELIVERY_CHANGE. But its not able to change.
    Plz help me for changeing  Inbound delivery by useing BAPI in my program.
    Reagards,
    Sunil Sahoo

    Hi Sunil,
    Have you used BAPI_TRANSACTION_COMMIT after your BAPI ?
    Regards,
    Nitin.

  • How to Change a Sales Order using BAPI

    Hi All
    How can we change the sales document using BAPI as the requirement is
    --> First we create a Sales order using a BAPI.
    --> If the sales order is changed then we get the changed order information alonge with the old order data in a CSV file.
    here i have the problem that we are uncertain which fields will be changed some times we may get the item changes or some times we may get the quantity changed information and some times the condition type may be changed . So how to handle this ?
    Thanks,
    Chindam

    Hi,
    try this
    DATA: IT_MESSAGE TYPE STANDARD TABLE OF BAPIRET2,
          WA_VBELN TYPE BAPIVBELN-VBELN.
    DATA: WA_BAPIHEAD TYPE BAPISDH1,
          WA_BAPIHEADX TYPE BAPISDH1X,
          WA_HEADDATA TYPE BAPISDH1.
    DATA: I_BAPIITEM TYPE STANDARD TABLE OF BAPISDITM,
          WA_BAPIITEM TYPE BAPISDITM,
            WA_DATA TYPE BAPISDITM,
          I_BAPIITEMX TYPE STANDARD TABLE OF BAPISDITMX,
          WA_BAPIITEMX TYPE BAPISDITMX.
    CHANGE ITEM DATA
    WA_BAPIITEM-ITM_NUMBER =WA_DATA-ITM_NUMBER.
    WA_BAPIITEM-REASON_REJ = WA_DATA-REASON_REJ. "(REASON FOR REJECTION)
    WA_BAPIITEMX-ITM_NUMBER = WA_DATA-ITM_NUMBER. "(ITEM NUMBER)
    WA_BAPIITEMX-UPDATEFLAG = 'X'.
    WA_BAPIITEMX-REASON_REJ = 'X'.
    APPEND WA_BAPIITEM TO I_BAPIITEM.
    APPEND WA_BAPIITEMX TO I_BAPIITEMX.
    TO CHANGE HEADER DATA
    WA_BAPIHEADX-UPDATEFLAG = 'U'.
    WA_BAPIHEADX-DLV_BLOCK = 'X'.
    WA_BAPIHEAD-SALES_ORG = WA_HEADDATA-SALES_ORG. "(COMPANY CODE)
    WA_BAPIHEAD-DLV_BLOCK = WA_HEADDATA-DLV_BLOCK. "(DELIVERY BLOCK)
    WA_VBELN = '0000000168'.
    CALL BAPI AND PASS THE VALUE
    CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
       EXPORTING
         SALESDOCUMENT               = WA_VBELN " (SALES AND DOCUMENT NO)
        ORDER_HEADER_IN             = WA_BAPIHEAD
         ORDER_HEADER_INX           = WA_BAPIHEADX
       TABLES
         RETURN                     = IT_MESSAGE
        ORDER_ITEM_IN               = I_BAPIITEM
        ORDER_ITEM_INX              = I_BAPIITEMX
    CLEAR IT_MESSAGE.

  • Attaching Handling Unit ID to Inbound delivery (Vl32N)

    Hello All ,
    I am trying to attach External handling unit ID to the Inbound delivery (Vl32N) .Iam using WS_DELIVERY_UPDATE ,but somehow its not working .can u help whether there are any other functions that will do this ??
    Thanks .

    Hi,
    Try with PROCESS_HU_INBOUND_DLVRY, WS_DELIVERY_UPDATE, SD_DELIVERY_UPDATE_PACKING
    Thanks,
    Abhijit

  • BAPI to change Inbound delivery - Delivery Date.

    Hi Expert,
    I wanna change the  Inbound delivery - Delivery Date .
    i have check the BAPI_INB_DELIVERY_CHANGE and WS_DELIVERY_UPDATE but both seems to be not useful for me or i have mis sumthing.
    so kindly suggest BAPI or any other solution.
    thx in advance.

    Hi guys,
    plz get following code,
    REPORT  ztest_inboun_deli.
    TYPES : lty_dead TYPE STANDARD TABLE OF bapidlvdeadln.
    DATA :lt_header_deadlines TYPE lty_dead,
          wa_header_deadlines TYPE bapidlvdeadln,
          wa_header_control TYPE bapiibdlvhdrctrlchg,
          it_return TYPE STANDARD TABLE OF bapiret2,
          wa_delivery TYPE bapiibdlvhdrchg-deliv_numb,
          wa_header_data TYPE bapiibdlvhdrchg.
    write : sy-datum.
    wa_header_deadlines-deliv_numb = '0080000069'.
    wa_header_deadlines-timetype    = 'WSHDRLFDAT'. "Delivery date
    wa_header_deadlines-timestamp_utc = 20120909000000. "YYYYMMDDHHMMSS
    wa_header_deadlines-timezone    = 'ALA'. "Western Europe
    APPEND wa_header_deadlines TO lt_header_deadlines.
    wa_header_data-deliv_numb = '0080000069'.
    wa_header_control-deliv_numb     = '0080000069'.
    wa_header_control-deliv_date_flg = 'X'.
    CALL FUNCTION 'BAPI_INB_DELIVERY_CHANGE'
      EXPORTING
        header_data                = wa_header_data
        header_control             = wa_header_control
        delivery                   = wa_delivery
      TABLES
       header_deadlines           = lt_header_deadlines
        return                     = it_return.
    IF sy-subrc EQ 0.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    ENDIF.

  • VL32N Change inbound delivery quantity after a partial goods receipt

    Dear.
    I have created an inbound delivery using VL31N from a purchase scheduling agreement.
    I have executed a partial goods receipts using MIGO for the inbound delivery.
    I need to reduce the delivery quantity for the inbound delivery using VL32N but the system donu2019t allow to change the delivery after a goods receipt.
    How can I proceed ?
    Thanks for your help.

    Hi,
    When a (partial) goods receipt has been posted to an inbound delivery item, the possibilities to change this item are restricted.
    If the delivery quantity is the same as the goods receipt quantity, then the item is fully posted goods receipt. No change of quantity is possible.
    If the delivery quantity is still higher than the goods receipt quantity, you can create one or several new TO's for the rest and
    confirm, if needed, with differences.
    You have also the chance to adjust the delivery quantity to the picked (and already posted) quantity with VL32N and menu:
    Edit => Copy Putaway Quantities as Delivery Quantities
    Please also have a look at note 796053.
    Hope this can help
    Regards
    Mauro

  • Post goods receipt against a Inbound Delivery(VL32N) FM or BAPI Method

    Hi Expert,
       I am looking for a Function Module or BAPI Method to Confirm the Inbound Delivery i.e. that can post Goods Movement Against a Delivery Document.
    My scenario is Create PO-> create Inbound delivery-> post Goods Receipt.
    Regards,
    Kapil.
    Edited by: Kapil Kumar Gupta on May 5, 2011 2:46 PM

    In OSS note 520813 it is said:
    16. Question:
    Which goods movements should I not post using the BAPI_GOODSMVT_CREATE BAPI?
    Answer:
    You should not post the goods receipt for the inbound delivery using BAPI_GOODSMVT_CREATE BAPI because the document base and the status of the inbound delivery are not updated. See Note 199703.
    If you check OSS note 199703 you can see that it is valid from release 45 to release 500.
    Assigned to this note you can find another: 1050944 (it's worth of reading!!!).
    I feel there are contradictions here - it might possible that the first note (520813) is not updated properly. (As far as I remember in my case this BAPI was working properly too).
    In my opinion you should send a message to OSS and ask them whether the statement in note 520813 is still valid or not - you should also tell them that the referred note (199703) is not applicable to ECC6.0.
    (there's a setting in ECC6.0 which enables that document flow is updated if GR is posted via MIGO with reference to IBD - V_TVSHP-SPE_INB_VL_MM)
    I would like to ask you if you have a reply from them, please update this thread - it may be helpful for us.
    Edited by: Csaba Szommer on May 9, 2011 2:34 PM
    One more remark: (based on OSS note 1050944) it seems that you cannot use it only in case of packing (IBD with HU).
    Edited by: Csaba Szommer on May 9, 2011 3:05 PM

  • Change inbound delivery using /SPE/IDOC_INPUT_DESADV1

    Hello -
    We are creating an inbound delivery using the idoc function module /SPE/IDOC_INPUT_DESADV1.  I have need to be able to change an existing delivery via idoc processing, so we are populating and mapping an E1EDL18 segment with the qualifier 'CHG'.  However, in /SPE/IDOC_INPUT_DESADV1, it does not appear to handle CHG.  I have debugged down into the code and in method PARSE_AND_HANDLE_IDOC_DELVRY03, when the segment is E1EDL18, there is a case statement that looks at the qualifier, and CHG is not dealt with. 
    Any ideas how to handle this?  Or is this a legitimate bug I should report to SAP?
    Thanks for any help!
    Sharon McClure

    Sharon McClure wrote:
    Or is this a legitimate bug I should report to SAP?
    Hard to say. Why not just report it? The worst they can do is say it's a consulting issue.
    Rob

  • Workflow for vl32n - Change inbound delivery

    Hi All,
       I need to create a workflow after saving the putawayqty field in vl32n.
    I will enter the inbound delivery number and i will change the qty field . then i will click on save button.
    Then after saving, workflow should be trigerred.
    But there is no event getting trigerred for this transaction.
    How to trigger  a event? so that i can activate my workflow according to that event.
    Is event should be trigerred via userexit or Badi's.
    if userexit or Badi's, which user exit i should write a code to trigger the event.
    Its urgent.
    Points will be awarded.
    Regards,
    Sandhya.

    Hi,
    The requirement is to trigger a workflow, when an inbound delivery is changed. However, the solution suggested by you, is a workflow, which is triggred when inbound delivery is created. Is there any workflow which is triggred when inbound delivery is changed? Or do any of you know the user exit or badi where a new task can be implemented, when a inbound delivery is changed?
    Regards,
    Sandhya

  • Deletion of Scheduling Agreement and Delivery Schedule using BAPI

    Hi SAP MM Gurus,
    Please assist in inquiry below:
    My scenario is that I am trying to delete delivery schedules and scheduling lines using BAPIs. I have no issues when there is no GR made yet for the delivery schedules. The error arises when there are already existing Goods Receipts and Invoices for the schedule line that I wish to delete
    When using the BAPIs (either BAPI_SAG_CHANGE or BAPI_SCHEDULE_MAINTAIN), I set the deletion indicator to "L" and set to X all change relevant fields (i.e. DELETION_INDX). However, whenever I execute it, I get the error message 06088. The funny thing is both the Quantities and the delivered quantities that are normally populated are left blank.
    For example:
    Normal error for 06088:
    Quantity 100.0 smaller than quantity delivered 179.0
    Error using BAPI with deletion indicator:
    Quantity  smaller than quantity delivered
    Is this a bug of the BAPI? or am I just missing some settings?
    Your immediate response is appreciated
    Regards,
    DeLo

    Hi,
    Please find the below link check the setting are correct or not
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a02cb00a-bfb4-2c10-98aa-e33e7f64ba28?quicklink=index&overridelayout=true
    Reagrds,
    Pramod

  • Inbound delivery creation using shipment Idoc details

    Hi,
       My requirement is that I need to create inbound delivery using SHPMNT05 idoc sending from a different plant.
    Below are the fields I am getting from the SHPMNT05 Idoc. So I need to create  Inbound delivery in Receiving plant.
    SAP - Field     IDoc Segment- Position - Field Name
    LIKP-LFART     E1EDL21 – 001 – LFART
    LIKP-LIFEX     E1EDT01 – 001 – VBELN
    LIKP-LIFNR     E1EDT44 – 009 – LIFNR
    LIKP-MBDAT     E1EDL24 – 039 = ABRDT
    LIPS-LFIMG     E1EDL24 – 013 – LFIMG
    LIPS-MATNR     E1EDL24 – 002 – MATNR
    LIPS-VGPOS     E1EDL41 – 006 – POSEX
    LIPS-PSTYV     E1EDL26 – 001 – PSTYV
    LIPS-VGBEL     E1EDL41 – 002 – BSTNR
    LIPS-VRKME     E1EDL24 – 014 – VRKME
    VEKP-EXIDV     E1EDL37 – 001 – EXIDV
    VEKP-VHILM     E1EDL37 – 017 – VHILM
    VEPO-MATNR     E1EDL44 – 007 – MATNR
    VEPO-POSNR     E1EDL44 – 003 - POSNR
    VEPO-VBELN     E1EDL44 – 002 - VBELN
    VEPO-VELIN     E1EDL44 – 001 – VELIN
    VEPO-VEMEH     E1EDL44 – 006 – VEMEH
    VEPO-VEMNG     E1EDL44 – 005 – VEMNG
    Could you please help me to find some workaround to solve this ?
    Thanks in advance.
    Regards.
    Ranjith

    Hi Ranjith,
    I guess there is a BAPI " /SPE/INB_DELIVERY_REPLACE " which can be used to create an inbound delivery.
    Documentation-
    FU /SPE/INB_DELIVERY_REPLACE
    Short Text
    Create inbound delivery
    Functionality
    You can use this method to distribute inbound deliveries from an ERP system to a WM system.
    The following parameters are required:
    HEADER_DATA Inbound delivery header data
    SENDER_SYSTEM System of the sender
    HEADER_PARTNER Header data of the partners
    HEADER_DEADLINES Header data of the dates
    ITEM_DATA Item data of the inbound delivery
    ITEM_ORG Organisation data of the inbound delivery
    Notes
    The required parameters have the following required fields:
    Import parameter HEADER_DATA
    INB_DELVRY_NO
    DLV_TYPE
    Import parameter SENDER_SYSTEM
    SENDERSYSTEM
    Table parameter HEADER_PARTNER
    PARTN_ROLE = 'LF'   Vendor is required partner
    PARTNER_NO
    Table parameter HEADER_DEADLINES
    TIMETYPE = 'WSHDRLFDAT' Delivery date
    Table parameter ITEM_DATA
    INB_DELVRY_NO
    ITM_NUMBER
    MATERIAL
    DLV_QTY
    SALES_UNIT_ISO oder SALES_UNIT
    Table parameter ITEM_DATA_ORG
    PLANT
    Further information
    HEADER_PARTNER
    Since the partners in the delivery are not managed on an item basis, the ITM_NUMBER field in the BAPIDLVPARTNER segment is left blank and not analyzed.
    HANDLING_UNIT_ITEM
    If the BAPI is used as an external interface for an external system, the packing hierarchy should be described as usual by using external identification numbers for shipping materials (HDL_UNIT_EXID_INTO/HDL_UNIT_EXID).
    Parameters
    HEADER_DATA
    SENDER_SYSTEM
    TECHN_CONTROL
    HEADER_DATA_SPL
    HEADER_CONTROL_SPL
    HEADER_PARTNER
    HEADER_PARTNER_ADDR
    HEADER_DEADLINES
    ITEM_DATA
    ITEM_ORG
    ITEM_STOCK_TRANS
    ITEM_CODING_BLOCK
    ITEM_REF_PURCHASE_ORDER
    ITEM_SERIAL_NO
    ITEM_DATA_SPL
    TEXT_HEADER
    TEXT_LINES
    HANDLING_UNIT_HEADER
    HANDLING_UNIT_ITEM
    HANDLING_UNIT_SERNO
    HANDLING_UNIT_ITEM_SPL
    HANDLING_UNIT_HEADER_CROSS
    HANDLING_UNIT_IDENTIFIERS
    EXTENSION1
    EXTENSION2
    RETURN
    TOKENREFERENCE
    Exceptions
    Function Group
    /SPE/INB_DELIVERY
    Check if this helps.
    Reward helpful answers.
    Regards
    Parag

  • Changing the delivered quantity using  BAPI

    As  per the reqt,  for Internal customers  I m changing the delivered qty (LIPS-LFIMG) to a rounded quantity based on the KNMT-RDPRF(full box qty) value.
    I m passing the rounded quantity  to an BAPI_OUTB_DELIVERY_CHANGE , expecting it to change the delivery quantity value from the all the related delivery tables like the LIPS and others.
    But this BAPI is not functioning as desired, what might be the error and is there any other option by which which I can change  the deliverey quantity to an rounded qty in the field LIPS-LFIMG.
    Please help to resolve this.

    Hi Vishnu,
    At first I was surprised to see this question. We cannot change material number. Hence there are 2 options available:
    1) Create a copy of the material and change the material number to what you want at the time of creation of the new material by inserting code in the fm that generates a material number.
    2) use the field material_external to store the material number required. This field is available in the import parameter 'HEADDATA' of BAPI_MATERIAL_SAVEDATA.
    The second option should be better.
    Regards,
    Nimish

  • Pricing issue - When posting with inbound delivery VL32N

    Hi Experts,
    Here is the present situation. We have no info records maintained for the precious metals . Base price comes from contract and market price comes from the condition record maintained in MEK1. There is a link between PO and condition record created.
    We are doing inbound delivery for the items where our present design was to have the same date populated in delivery date field and actual GR date field. This way the price of the item is determined on the day  when the item was actually delivered from the condition table maintained and posted on that day that might be only past last month assuming periods well be open.When PGR was done the actual GRdate picks up the right price from the condition record.
    Issue is that insted of actual GR date the inbound delivery VL31N / VL32N progam should look at delivery date and get the right price from the condition record insted of actual GR DATE when PGR is done. Since the actual GR date is the posting date Finace has decided to closethe previous months periods and so it is a problem. We have to keep the Actual GR date as present date and delivery date should get the price for that day when item was physically delivered in past.
    I have tried looking at pricing procedure  and condition types but was not able to get any success. Please advise how to resolve this issue.
    Thanks in advance.
    Edited by: Born-Legacy on Jan 15, 2012 7:54 PM

    Hi,
    Just a couple of ideas - not sure if they can achieve what you need.
    There's a field in the contract, called "Pr. date category", EKPO-MEPRF. It controls which date shall be used for pricing. This field is copied over to the PO together with the pricing conditions. The value 2 to the best of my understanding means the "delivery date in the PO". Can you make the delivery date in the PO to be the same as the delivery date in the inb. delivery?
    If not, you might be able to use an own developed formula in the pricing procedure, column "CalcType" (V_T683S-KOFRM).
    BR
    Raf

  • Inbound delivery creation using VL31N

    Hi All,
    I could find that the message type DESADV, IDoc type DELVRY01 and process code DELS is used for creation of this.
    Let me know if this is correct. When i checked in my system I could not find process code DELS. Do i need to do some additional settings to get this.
    What is difference between IDOC type DELVRY01 and DELVRY03. Which one should be used.
    Here the ASN received is triggering inbound delivery creation.
    Please let me know on this.
    Regards,
    Shahu

    Hi,
    Where did you check that process code in WE64?
    Check in the correct set(Inbound messages).
    DELVRY03 is the latest one. You should use it only.
    Regards,
    Ravi

  • Need to change CONTRACT End date using Bapi BAPI_CUSTOMERCONTRACT_CHANGE

    Hi,
    I need to change date of a contract and for the same I am using Bapi "BAPI_CUSTOMERCONTRACT_CHANGE".
    I am passing the following Parameters to the BAPI.
    SALESDOCUMENT  -- Have passed the Contract Number in this.
    CONTRACT_HEADER_IN -- Have passed the values of the following fields ::
    COLLECT_NO -- Sales Document number
    Sales_Org  -- Sales Organization
    Distribution Channes -- Dist. Channel
    Division -- Division
    CT_VALID_T -- New date which I want as the contract end date.
    CONTRACT_HEADER_INX -- Following values have been paased in this Structure.
    UPDATEFLAG -- 'U'.
    CT_VALID_T -- 'X'.
    Now when I run the BAPI with these inputs I get the output as ' Field 'GUEEN' cannot be copied, because it is not ready for input'.This is a information message. But the changes are not reflected in the contract. I have done the commit work after BAPI.
    When I changes the value for CT_VALID_T flag from 'X' to 'U' the message mentioned above does not come but the end result is same and changes are not reflected in the contract.
    I would be really helpful to you if get any kind of helf to know ehy the output is not coming.
    Thanks a Lot for your kind help!!!!
    Regards,
    Lalit Kabra

    Hi Lalit,
    The value for CT_VALID_T flag has to be 'X' in the CONTRACT_HEADER_INX structure.
    In this case, you receive an informative message "Field 'GUEEN' cannot be copied, because it is not ready for input'"
    That is the problem. You cannot change this field because your functional team has this field as "not ready for input" in change mode.
    Can you change this field in transaction VA42? If you can't modify it in dialog, you can't modify it with BAPI.
    Regards,

Maybe you are looking for