User exit to change partner for inbound delivery creation

Hello,
I have a requirement to change the partner number for
the inbound delivery creation.
I only see the USEREXIT_MOVE_FIELD_TO_LIKP but I am not sure if this is
the right user exit for this requirement.
Is there the user exit for modifying partner in the inbound delivery?
Thanks in advance,

HI
There is a program with which you can find the available exits as per your requirement. You have to execute the same and give your transaction code. Hope this helps...
*& Report  ZFINDUSEREXIT
report  zfinduserexit.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.
select single * from tstc where tcode eq p_tcode.
if sy-subrc eq 0.
select single * from tadir where pgmid = 'R3TR'
and object = 'PROG'
and obj_name = tstc-pgmna.
move : tadir-devclass to v_devclass.
if sy-subrc ne 0.
select single * from trdir where name = tstc-pgmna.
if trdir-subc eq 'F'.
select single * from tfdir where pname = tstc-pgmna.
select single * from enlfdir where funcname =
tfdir-funcname.
select single * from tadir where pgmid = 'R3TR'
and object = 'FUGR'
and obj_name eq enlfdir-area.
move : tadir-devclass to v_devclass.
endif.
endif.
select * from tadir into table jtab
where pgmid = 'R3TR'
and object = 'SMOD'
and devclass = v_devclass.
select single * from tstct where sprsl eq sy-langu and
tcode eq p_tcode.
format color col_positive intensified off.
write:/(19) 'Transaction Code - ',
20(20) p_tcode,
45(50) tstct-ttext.
skip.
if not jtab[] is initial.
write:/(95) sy-uline.
format color col_heading intensified on.
write:/1 sy-vline,
2 'Exit Name',
21 sy-vline ,
22 'Description',
95 sy-vline.
write:/(95) sy-uline.
loop at jtab.
select single * from modsapt
where sprsl = sy-langu and
name = jtab-obj_name.
format color col_normal intensified off.
write:/1 sy-vline,
2 jtab-obj_name hotspot on,
21 sy-vline ,
22 modsapt-modtext,
95 sy-vline.
endloop.
write:/(95) sy-uline.
describe table jtab.
skip.
format color col_total intensified on.
write:/ 'No of Exits:' , sy-tfill.
else.
format color col_negative intensified on.
write:/(95) 'No User Exit exists'.
endif.
else.
format color col_negative intensified on.
write:/(95) 'Transaction Code Does Not Exist'.
endif.
at line-selection.
get cursor field field1.
check field1(4) eq 'JTAB'.
set parameter id 'MON' field sy-lisel+1(10).
<b>Do reward if useful...</b>
Regards
Dinesh

Similar Messages

  • User exit to change data in inbound orders idoc

    Hi everybody.
    Id like to know what user exit I have to use to change an inbound idoc orders in inbound process???
    Thanks a lot

    Hi,
    Please search on SCN.
    However you can look for an exit that matches your requirement :-
    [http://wiki.sdn.sap.com/wiki/display/ERPLO/UserExitfor+Deliveries]
    Regards
    Abhii

  • Confirmation control key check for inbound delivery creation

    Hi,
    Currently, in the Client's company, the process of receiving goods from purchase orders looks like that (SAP-wise):
    - create a purchase order,
    - receive goods using MIGO and automatically create an inbound delivery,
    - pack the delivery and post goods receipt.
    Recently, some patches have been installed, including one described by note 1602047 (which basically enforces checking confirmation control keys if goods receipt assignment and goods receipt relevance are activated for inbound deliveries). Note says that it only affects two-step stock transfer and creation of automatic inbound deliveries using SPED output but it seems it also affects other basic processes like PO receipt in MIGO.
    Now, when using the old control key (that had MRP-Relevant and GR-Relevant fields checked), the system is unable to automatically create an inbound delivery after the goods receipt is posted with MIGO (with message VL148 - Not possible to create an inbound delivery). I learned that this is because the "GR Assignment" field must be checked in the confirmation control key so it's possible to automatically create aninbound delivery after receiving a purchase order in MIGO.
    After changing the confirmation control key to have the missing field checked it's not possible anymore to receive goods from PO in MIGO as the PO requires shipping notification in order to be processed in MIGO thus requiring of manual creation of an inbound delivery.
    Is there any way to skip this check so the process would remain the same (this model has been working fine for few years in the Client's system) and the inbound delievery would be created automatically after posting the receipt in MIGO?
    Thanks in advance,
    Piotr

    Hi,
    don't know if you found a solution, but we received the following message from SAP:
    The advent of the new version requires some attention to the users. It
    was necessary to avoid inconsistencies which in the past version the
    system was susceptible.
    Main Program SAPMM07M
    Source code of MM07MLVS
    sy-msgid VL sy-msgty E sy-msgno 148
    I have checked the process and through debugged I could confirm the
    following information SAP is providing to all similar incidents reportedfor us:
    Error message VL 148 is issued if in the confirmation control key used
    in the purchase order, the fields for MRP-relevance (T163G-KZDIS),
    GR relevance (T163G-WEREL) and GR assignment indicator (T163G-WEZUO)
    are not set.
    The correction of note 1602047 was necessary to avoid inconsistencies
    (table EKES) in the purchase order. Without having the GR assignment
    (T163G-WEZUO) set, there is no unique reference created between the
    purchase order history (table EKBE) and the inbound delivery
    confirmation (table EKES) at goods receipt which leads to a problem if
    several inbound deliveries exist for the same purchase order.
    If you set T163G-WEZUO to 'X', this assures that, for an inbound
    delivery, the confirmation record (EKES) belonging to this inbound
    delivery (EKES-VBELN) is also accurately updated at goods receipt.
    How to solve the issue?
    Use a confirmation control key with the GR assignment indicator set
    and then create the inbound delivery with VL31N. If you want to be able
    to create the inbound delivery with reference to a certain line item in
    the PO, use transaction VL34.
    If you still want to use transaction MIGO, there is the following
    workaround:
    - Create a purchase order without any confirmation control key
    - Create a goods receipt (GR) in transaction MIGO with reference to this PO and post the GR to a non-HU-managed storage location
    - Create a transfer posting with MIGO using movement type 311 to
    transfer the goods from the non-HU-managed storage location to the
    HU-managed storage location.
    As the transfer posting is an additional step for the user, the whole
    process could be automated using a partner storage location
    (T001l-PARLG) for the GR which then triggers (through a modification)
    the BAPI 'BAPI_GOODSMVT_CREATE' to create the transfer posting without
    user interaction.
    I hope to have satisfied you on the reason why it is now happening and
    also I believe you can explain to business that it is a new behavior
    necessary done from SAP side to avoid worse situations, we are aware of
    potential dissatisfaction it might cause. SAP Support is always
    available to clarify any issue.
    Sorry for not having a more positive answer.
    I hope it helps!
    Leentje

  • BAPI for inbound delivery creation

    Hi,
    I have to create and modify inbound deliveries from a code, so I'm wondering if exists any BAPI (or function module) to create or modify inbound delivery.
    Thanks in advance

    This is an example of BAPI_INB_DELIVERY_CHANGE. It is in the documentation of the function
    I hope it helps you...
    Example
    If you want to change the quantity for a distributed quantity, then following entries are required for the transfer to the connected system:
    In the header data of inbound delivery parameter (HEADER_DATA)
    The delivery number (DELIV_NUMB)
    In parameter item data of inbound delivery (ITEM_DATA)
    The delivery number (DELIV_NUMB)
    The delivery item (DELIV_ITEM)
    The delivery quantity in sales unit (DLV_QTY)
    The actual delivery quantity in base UoM (DLV_QTY_IMUNIT)
    The sales unit (SALES_UNIT)
    The ISO code for the sales unit (SALES_UNIT_ISO)
    The base unit of measure (BASE_UOM)
    The ISO code for the base unit of measure (BASE_UOM_ISO)
    In the control of the inbound delivery at item level parameter (ITEM_CONTROL)
    The delivery number (DELIV_NUMB)
    The delivery item (DELIV_ITEM)
    The Change Delivery Quantity indicator(CHG_DELQTY)

  • IDoc or BAPI for inbound delivery creation with reference to PO.

    Hi
    I have requirement to create a inbound delivery, I  will get a ASN from external system with PO, Vendor Material number & batch. I want to know is there any BAPI or IDoc that can be used to create inbound delivery in R/3. I used BBP_INB_DELIVERY_CREATE to create inbound delivery and I was successful but problem is that inbound delivery was not updated with Vendor Material number & Batch.  Can some one suggest me any other BAPI or IDoc ?
    Thanks in advance
    Nagendra P Boggarapu
    Edited by: Nagendra P Boggarapu on May 6, 2010 4:06 PM

    Use Delvry0* IDOC.
    Reddy

  • BAPI For Inbound Delivery using Purchase Order Number

    Hi All,
    Is there any BAPI for posting Inbound Delivery (VL31N) using Purchase Order as reference.
    thanks
    bobby

    Not sure what it has to do with enhancements and modifications, but there is no such BAPI:
    http://tech.groups.yahoo.com/group/ABAP/message/38307
    http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/bapi-for-inbound-delivery-creation-and-update-vl31n-1201265
    FYI all BAPIs may be viewed in BAPI transaction.

  • ASN from vendor and inbound delivery creation

    hi
    I have a scenario where vendor sends ASN via EDI to R/3.
    This inbound ASN should create an inbound delivery. 
    Can you please help me knowing the idoc type, message type etc which will serve my purpose.
    Also the FM / Badi for inbound delivery creation.
    thanks in advance,
    Jo

    Hi,
    Use DESADV Message type and basic type DESADV01
    Use function module IDOC_INPUT_DESADV
    Edited by: Chandra Shekhar Singh on Jul 5, 2011 12:39 PM

  • Need to know the user exit to change unlimited check box in delivery tag

    Need to know the user exit,
    To change the <b>unlimited check box(</b>EKPO-UEBTK) in <b>delivery tag</b> of <b>item details</b> for tcode <b>ME21N/ME22N</b> on <b>SAVE</b>. 
    Thanks in Advance.
    Baburaj

    HI Baburaj,
    Use the BADI ME_PROCESS_PO_CUST to change the unlimited check box(EKPO-UEBTK)
    Implement the BADI and insert the code in the method PROCESS_ITEM
    Example code :
    *Data Declarations
    DATA: ls_mepoitem TYPE mepoitem,
          ls_mepoitemx type mepoitemx,
            ls_customer TYPE mepo_badi_exampl,
            ls_tbsg     TYPE tbsg.
      INCLUDE mm_messages_mac. "useful macros for message handling
    *here we  get item data
      ls_mepoitem = im_item->get_data( ).
    *work area for price value
    data : begin of it_eban,
      banfn type  mepoitem-banfn,
      bnfpo type  mepoitem-BNFPO,
      pries type mepoitem-NETPR,
    end of it_eban.
    *Get the Purchase requisition price from EBAN table
    select single banfn bnfpo preis from eban into it_eban
                                            where
                                              banfn = ls_mepoitem-banfn
                                          and bnfpo = ls_mepoitem-bnfpo.
    *if entry is available.
    if sy-subrc eq 0.
    *check if price is zero
        if it_eban-pries EQ 0.
    *if zero, set FREE field of PO to 'X'.
          ls_mepoitem-uebtk = 'X'.
        endif.
        endif.
    *Set updated fields
    CALL METHOD im_item->set_data
    EXPORTING
    im_data = ls_mepoitem
    Reward if Helpful*****

  • Finding BAPI for  inbound Delivery change(VL32N)

    HI,
    Plz help me For finding BAPI for  inbound Delivery change(VL32N).
    I have to pass delivery no as input parameter and should able to change shipment heder information
    like Special processing indicator.
    REGARDS,
    Sunil Sahoo.

    hi ,
    there are three  BAPI  your requirment
    1) BAPI_INB_DELIVERY_CONFIRM_DEC
    2) BAPI_INB_DELIVERY_SAVEREPLICA
    3) BAPI_INB_DELIVERY_CHANGE
    but for requirment
    The third BAPI
    BAPI_INB_DELIVERY_CHANGE
    will Sound promising. try this out
    regards
    Prashant

  • User exit to change Delivery type

    Is there a user exit to change the delivery type when creating delivery wrt a sales order.
    Thanks.

    Use BADI   LE_SHP_DELIVERY_PROC
    Edited by: abhishek shukla on Sep 24, 2008 12:00 AM

  • User exits while changing the PO Output Medium

    Hello Champions,
    Will anyone share me, is there any user exit which triggers while changing Purchase Order Output Medium in ME22N transaction.  How to know list of user exits which are applicable for ME22N transaction?.  will anyone guide me.
    Reward with Full point

    Hi PV,
    These are the list f User exits for ME22N:
    Exit Name           Description
    AMPL0001            User subscreen for additional data on AMPL
    LMEDR001            Enhancements to print program
    LMELA002            Adopt batch no. from shipping notification when posting a GR
    LMELA010            Inbound shipping notification: Transfer item data from IDOC
    LMEQR001            User exit for source determination
    LMEXF001            Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001            Customer-Specific Source Determination in Retail
    M06B0001            Role determination for purchase requisition release
    M06B0002            Changes to comm. structure for purchase requisition release
    M06B0003            Number range and document number
    M06B0004            Number range and document number
    M06B0005            Changes to comm. structure for overall release of requisn.
    M06E0004            Changes to communication structure for release purch. doc.
    M06E0005            Role determination for release of purchasing documents
    ME590001            Grouping of requsitions for PO split in ME59
    MEETA001            Define schedule line type (backlog, immed. req., preview)
    MEFLD004            Determine earliest delivery date f. check w. GR (only PO)
    MELAB001            Gen. forecast delivery schedules: Transfer schedule implem.
    MEQUERY1            Enhancement to Document Overview ME21N/ME51N
    MEVME001            WE default quantity calc. and over/ underdelivery tolerance
    MM06E001            User exits for EDI inbound and outbound purchasing documents
    MM06E003            Number range and document number
    MM06E004            Control import data screens in purchase order
    MM06E005            Customer fields in purchasing document
    MM06E007            Change document for requisitions upon conversion into PO
    MM06E008            Monitoring of contr. target value in case of release orders
    MM06E009            Relevant texts for "Texts exist" indicator
    MM06E010            Field selection for vendor address
    MMAL0001            ALE source list distribution: Outbound processing
    MMAL0002            ALE source list distribution: Inbound processing
    MMAL0003            ALE purcasing info record distribution: Outbound processing
    MMAL0004            ALE purchasing info record distribution: Inbound processing
    MMDA0001            Default delivery addresses
    MMFAB001            User exit for generation of release order
    MRFLB001            Control Items for Contract Release Order
    Regards,
    Maia

  • SAP System inconsistency for Inbound delivery / MIGO and a "sap note"

    Hello Friends ,
    After following SAP instruction on how to remove the inconsistency between posting GR through MIGO (Inv. mang.) and the reflection of the goods movement status in the inbound delivery document - done that using sap note 570991
    the problem is that the system start behaving in a weird way throwing unjustified Error messages for any suggested goods receipt using MIGO with reference to inbound
    for example after creating an inbound delivery document and trying to post it via migo , an error will pop up
    - Inbound delivery storage location cannot be changed to here Message no. VLA316
    the thing is i didn't even maintain any storage location entry up to that point and yet i cannot post any stock !!
    also another error  like
    - Inbound delivery batch cannot be changed to *** here
    which doesn't make any sense because there is not batches in the inbound document !!
    i think this behavior is coming from the "Document Flow Update for Stock Postings" inbound  indicator  at the shipping parameter at client level customization
    i need help on  how to overcome this annoying SAP Bug/Problem specially i am in a post go live critical situation

    Hi,
       The messages you mentioned were introduced to avoid inconsistency between inbound delivery and IM, through the note:  1050944 - GR for inbound delivery using inventory mgmt as of ECC 6.00
       If the messages are issued incorrectly, then you may check for SAP notes (I couldnt find anything relevant) or raise an OSS ticket to SAP.
    Regards,
    AKPT

  • Function Module to Fetch data of Vendor for Inbound Delivery at runtime

    Hi All,
    I am new to EWM. I am using BADI /SCWM/EX_DLV_DET_PROCTYPE method CHANGE_PROCTYPE to change process type of the inbound delivery as per some logic from a custom table. However the parameter Vendor is not available in IS_ITEM during inbound delivery creation. Vendor is one of the key fields in my table.
    Does anyone know any solution/function modules to fetch vendor data for the inbound delivery at runtime. I know the database tables to fetch vendor but this works only once the inbound delivery is saved.
    Thanks and Regards,
      Vanessa Noronha

    Hi All,
    I am new to EWM. I am using BADI /SCWM/EX_DLV_DET_PROCTYPE method CHANGE_PROCTYPE to change process type of the inbound delivery as per some logic from a custom table. However the parameter Vendor is not available in IS_ITEM during inbound delivery creation. Vendor is one of the key fields in my table.
    Does anyone know any solution/function modules to fetch vendor data for the inbound delivery at runtime. I know the database tables to fetch vendor but this works only once the inbound delivery is saved.
    Thanks and Regards,
      Vanessa Noronha

  • Function Module / BAPI for Inbound Delivery from Purchase Order

    Hi,
    I need to create an inbound delivery from Purchase Order items and am looking out for some Function Module or BAPI for the same.
    The requirement is that i should be able to specify selected line items from PO for delivery.
    I tried the BDC method for VL31N , but the particular item selection is problem, since by default it shows all the items of PO and i want only selected items.
    Do reply.
    Thanks in advance.

    check these and their documentations.
    BAPI_INB_DELIVERY_CHANGE       Change inbound delivery
    BAPI_INB_DELIVERY_CONFIRM_DEC  BAPI for inbound delivery verification from a decentralized system
    BAPI_INB_DELIVERY_SAVEREPLICA  BAPI Function Module for Replication of Inbound Deliveries
    Regards
    Prabhu

  • VL09 Authorization issue for Inbound Delivery

    Dear Experts,,
    When we reverse the goods movement in VL09, authorization check is made for Goods receiving/Shipping Point.
    This is fine for outbound delivery because we always have a shipping point defined.
    However, most of the Inbound Deliveries have no Goods Receiving/Shipping Point. 
    So, if we give the authorization for u201CBlanku201D receiving point = "  ", the user can reverse goods movement for any inbound delivery.
    How can we restrict this? 
    Please suggest your valuable inputs
    Regards,
    Shahsidhar

    Hi,
    most of the Inbound Deliveries have no Goods Receiving/Shipping Point.
    If you doing inbound delivery by VL10B, then you should specify shipping point.
    Define shipping point for inbound delivery and maintain authorization
    kapil

Maybe you are looking for