Ship to(partner fun - WE) address detail during user exit.

Hi All,
I am doing changes in user exit - MV45AFZZ
Now I can get address no. for ship to in XVBPA table and get the address detail. But if some one changed the value manualy how could I find the new value.
Mean is there any internal table which I could read to get the address detail for ship to partner function in user exit.
Please update me. Thanks a lot.

Hi even if someone changed the value manually in the correspondingaddr table,then  table would again be updated in the address table from where you are picking the details using the address number.
Regards,
SuryaD.
Edited by: SuryaD on Dec 21, 2009 9:58 PM

Similar Messages

  • User exit/BADI for Return PO item delivery Address

    Hi Guyz,
    We have a requirement where in when a PO item is marked as return PO item(In ME21n/ME22n/ME23n We have check box at item level) and click on enter/Check/Save, In delivery address of item details we have to populate Vendor address. By default SAP populates Plant address. If we manually give Vendor number in item details=>Delivery address tab then it populates vendor address. We want to automate this functionality.
    Is there any Exit/BADI which serve this purpose.
    Note: We need this functionality for few doc types(i.e PO doc type should also be available in the exit).
    Any ideas could be really helpfull.
    Thanks,
    Vinod.

    Hi,
    there are some user-exit & enhancements....
    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
    MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
    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
    MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
    MEETA001                                Define schedule line type (backlog, immed. req., preview)
    ME590001                                Grouping of requsitions for PO split in ME59
    M06E0005                                Role determination for release of purchasing documents
    M06E0004                                Changes to communication structure for release purch. doc.
    M06B0005                                Changes to comm. structure for overall release of requisn.
    M06B0004                                Number range and document number
    M06B0003                                Number range and document number
    Some BADI s:
    ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Customer
    ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
    ME_PO_PRICING                           Enhancements to Price Determination: Internal
    ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
    ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
    ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
    ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
    SMOD_MRFLB001                           Control Items for Contract Release Order
    MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
    ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
    ME_REQ_POSTED                           Purchase Requisition Posted
    ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_PURCHDOC_POSTED                      Purchasing Document Posted
    ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
    ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
    ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
    ME_BSART_DET                            Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
    EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
    ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN                    Commitment for return item
    ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
    ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
    ME_CHECK_OA                             Check BAdI for Contracts
    ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
    ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
    No.of Exits:         35
    No.of BADis:         55
    Arunima

  • What user exit to use for Address Delivery in ME53N?

    Hi all,
    I make a mistake on my last week question. However, it has also added some extra knowledge to me and marks has been given out to respected consultants providing solution to me.
    Ok, my correct question should be:
    What is the user exit to maintain Delivery Address (CMMDA-ADRN2) in ME53N?
    Hope to get some reply from you all as soon as possible.
    Thanks,
    William Wilstroth
    Message was edited by: william wilstroth

    User Exit for ME53N,The Bold One below would solve the purpose...and other user exist related to ME53...
    <b>Kindly rewards points.</b>
    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
    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.
    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
    <u><b>MM06E010  </b></u>          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
    <i><b>MMDA0001 </b></i>           Default delivery addresses
    MMFAB001            User exit for generation of release order

  • User exit is used to get incoterms from ship-to-party.

    Hi Gurus,
    my client needs to catch incoterms from ship-to-party,
    please let me know which user exit is used to get incoterms from ship-to-party.
    regards,
    Naren

    In our system we get the inco terms from the ship to party. We use user exit move_fields_to_vbkd in program mv45afzz. The code looks like this:
    Inco terms
    Added to get the values of Inco Terms from
    Ship-To-Party instead of Sold-To-Party.
    data: oldship like kuwev-kunnr value space.
    if sy-ucomm   <> 'UEBR' and  "Ordre er ikke oprettet med reference
       t180-trtyp <> 'A'.        "Der er ikke Vis mode
      import oldship from memory id 'ZSS'.
      if *vbkd-inco1 is initial. "Første gang vi er i User-Exitet
        if kuwev-kunnr <> kuagv-kunnr. "Varemodtager forskellig fra ordregiver
          select single inco1
                        inco2
         into (vbkd-inco1,
               vbkd-inco2)
         from knvv
        where kunnr = kuwev-kunnr
          and vkorg = vbak-vkorg
          and spart = vbak-spart
          and vtweg = vbak-vtweg.
        endif.
      elseif oldship <> kuwev-kunnr and
       ( *vbkd-inco1 <> vbkd-inco1 or
         *vbkd-inco2 <> vbkd-inco2 ).
        select single inco1
                      inco2
          into (vbkd-inco1,
                vbkd-inco2)
          from knvv
         where kunnr = kuwev-kunnr
           and vkorg = vbak-vkorg
           and spart = vbak-spart
           and vtweg = vbak-vtweg.
      endif.
    endif.
    Det skal ligge udenfor if-sætningen for at undgå at det overskrives
    ved oprettelse med reference
    move kuwev-kunnr to oldship.
    export oldship to memory id 'ZSS'.
    /Torben

  • User exit for incoterms from ship-to-party

    Hi Gurus,
    my client needs to catch incoterms from ship-to-party,
    please let me know which user exit is used to get incoterms from ship-to-party.
    regards,
    Naren

    In our system we get the inco terms from the ship to party. We use user exit move_fields_to_vbkd in program mv45afzz. The code looks like this:
    Inco terms
    Added to get the values of Inco Terms from
    Ship-To-Party instead of Sold-To-Party.
    data: oldship like kuwev-kunnr value space.
    if sy-ucomm   <> 'UEBR' and  "Ordre er ikke oprettet med reference
       t180-trtyp <> 'A'.        "Der er ikke Vis mode
      import oldship from memory id 'ZSS'.
      if *vbkd-inco1 is initial. "Første gang vi er i User-Exitet
        if kuwev-kunnr <> kuagv-kunnr. "Varemodtager forskellig fra ordregiver
          select single inco1
                        inco2
         into (vbkd-inco1,
               vbkd-inco2)
         from knvv
        where kunnr = kuwev-kunnr
          and vkorg = vbak-vkorg
          and spart = vbak-spart
          and vtweg = vbak-vtweg.
        endif.
      elseif oldship <> kuwev-kunnr and
       ( *vbkd-inco1 <> vbkd-inco1 or
         *vbkd-inco2 <> vbkd-inco2 ).
        select single inco1
                      inco2
          into (vbkd-inco1,
                vbkd-inco2)
          from knvv
         where kunnr = kuwev-kunnr
           and vkorg = vbak-vkorg
           and spart = vbak-spart
           and vtweg = vbak-vtweg.
      endif.
    endif.
    Det skal ligge udenfor if-sætningen for at undgå at det overskrives
    ved oprettelse med reference
    move kuwev-kunnr to oldship.
    export oldship to memory id 'ZSS'.
    /Torben

  • Want to know about User exit in detail

    Hi ALL,
    I M NEW TO sap ABAP. I WANT TO KNOW ABOUT USER EXIT IN DETAIL. PLS DO THE NEEDFUL . If there are eny document regarding this pls mail to this id [email protected]
    thanks and regards
    Nandha

    Hi Nanda,
    Welcome to SDN,
    Userxits allow us to add our own functionality to SAP standard program
    without modifying it . These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.
    User exits are used when the flow for a particular transaction has to take some other route other then the normal flow. this can be the case when you have to attach some additional functionality lik u need a customised screen, or new functionality (using a functional module). based on these things user exits can be classified as screen exits, function module exits, field exits( not used anymore). hope this gives some help on userexits.
    The naming standard of function modules for functionmodule exits is:
    EXIT_<program name><3 digit suffix>
    The call to a functionmodule exit is implemented as:
    CALL CUSTOMER.-FUNCTION <3 digit suffix>
    To find a Exit.
    Goto Transaction -- Find The Package
    SMOD >f4>Use the Package here to Find the Exits In the Package.
    Else if you Want to search by Application Area wise ,
    There is one more tab to find the Exits in the Respective Application Area.
    Implementing the Exit-- CMOD Create ProjectsAssgn your Component .
    Now Run ur Transaction to Check if it Triggers.
    Thats it..
    For More information on Exits, check these links
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sap-img.com/ab038.htm
    http://www.planetsap.com/userexit_main_page.htm
    http://www.sap-basis-abap.com/sapab013.htm
    http://sap.ittoolbox.com/documents/popular-q-and-a/user-exits-for-the-transaction-code-migo-3283
    These links will help you to learn more on user exits.
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
    http://www.planetsap.com/userexit_main_page.htm
    http://www.allsaplinks.com/user_exit.html
    www.sap-img.com/abap/what-is-user-exits.htm
    Also please check these threads for more details about user exits.
    Re: Screen exit
    user exit and customer exit
    user exit
    1. Document on UserExits in FI/CO
    http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
    2. Finding User Exits...
    http://sap.ionelburlacu.ro/abap/sap2/Other_Useful_Tips.html#Finding_User_Exits
    3. List of all User Exits...
    http://www.planetsap.com/userexit_main_page.htm

  • "Ship To Address" details missing in the SC and subsequent documents

    Hi All,
    We have a strange situation.
    There is no "Ship To Address" details in the shopping Cart and its subsequent documents.
    This happens only for some shopping carts.
    As per my understanding "Ship To Address" is a mandatory partner information without which the Shopping cart should not be created at all.
    Can anyone please let me know the possible reasons for "Ship to Address" not being present?
    Thanks & Regards,
    Mayank

    Hi Mayank,
    Have a look at the following OSS Note:
    Note 738534 - Ship to address disappears when product category is changed
    Note 953657 - BBP_POC: Ship to address cleared during change of PO item
    Note 1022048 - BBPSC03: Ship-to address gets cleared off
    Hope it helps.
    Thanks,
    Pradeep

  • Changing the Ship-to partner details in Sales order header through exit

    Hi all,
      I have a requirement where in during the process of the sales order creation, based on certain
      criteria, the details in the ship-to partner would have to be modified.
      These details like the Name, Street, etc would be maintained in a local table and based on the criteria,
      the appropriate record from this table would be fetched and updated to the ship-to partner.
      I was trying to implement this in the MV45AFZZ user exit. However, I was not able to update this through the exit.
      Would I have to somehow update the ADRC table directly through this exit or is there any better method.
      Please suggest.
    Regards,
    Sudeep

    Hi,
    If you could not find Street in this Routine call the BAPI BAPI_BUPA_ADDRESS_CHANGE to update Street and required details ..
    Thanks and regards,
    Sree.

  • Address details while saving the order

    hello experts
    i am having the requirement where i wanted to fetch the Ship-to Address details that is changed by the user while saving the order.
    I tried using different FMs like BAPI_BUPA_ADDRESS_GETDETAIL but these fetch the address from master data. What i want is the new address entered by the user.
    In CRM_ORDER_READ i am getting a new ADRNR for the newly entered address (itab_partner-addr_nr)but not able to find any FM to get the details out of it.
    did anyone know how to get the same?
    Thanks in advance.
    regards
    rajeev

    Hi,
    I tried FM BUA_BUPA_ADRC_GET. This one returns address details from memory but doesn't have partner relation in it.
    basically it populates partner's name into NAME1 field of ADRC.
    regards
    rajeev

  • Manual Updation of Ship to Partner (Customer) in Purchase order Item

    Hello Sap Gurus,
    While creating Purchase order (ME21n) of Type RTN or STO, the client wishes to Select the Ship to partner manually if more than 1 Ship to Partner is assigned to the Customer Master Data / Sales Organisation. Currently this is auto picked by SAP and the field is uneditable.
    I Have added the Functionality to PO Header to show the additional ship to partners in a drop down through use of enhancements. On selection of one of the ship to partners in PO header the Customer in Shipping Tab in all the PO items and Corresponding Delivery Addresses needs to be updated based on the selection.
    SAP Note 303453 shows how to change selected shipping data fields but not the customer or shipping address. My requirement is somewhat described by Note 652763 but that cannot be used in ME21n.
    Kindly help in this regard on how to achieve the functionality.

    Hello Helena,
    Unfortunately there is not possible to get the partner determination on the item level in the standard. The Partner determination in the standard system will be done on the header level only.
    The another thing is that if you change the partner (exept the  sold-to partner) in the sales order no new partner determination runs. It is the standard. Please also review the note 380507 (points 1 and 2).
    Best regards,
    Lela

  • Update ship-to partner in sales order using BAPI_SALESORDER_CHANGE

    Dear all,
    We are trying to update the ship-to partner in a sales order using BAPI_SALESORDER_CHANGE. This is working correctly for most of our orders, so we do fill the BAPI correctly. However for some of our orders on item level a different payer is specified than on header level. However in that case the BAPI will not update the ship-to partner, but given an error message VPD 034 u2018The document must contain the same credit control areas for all payersu2019. Debugging already learned that actually the message is given not because of different credit control areas, but due to the fact that the payers and therefore the credit customers are different (although in the same credit control areas). For this reason we can not update the ship-to party of a large number of our sales orders with this BAPI. Actually we have 2 questions:
    ·         Has somebody experienced the same issue and did you manage to solve it somehow, so the BAPI could be used for this purpose of updating partner data?
    ·         Do you know other ways of updating the partners or partner address of an existing sales order in the background?
    Thanks in advance for your assistance.
    Regards,
    Satish.

    It was caused by standard SAP.

  • Copy down Ship-to Partner from main item to sub-items on Sales Order

    This is my first post on the forums here.  I'd appreciate any help you can give on my issue below.
    I have a requirement to copy down the ship-to partner from the main item to sub-items during sales order create or change.  Currently I have code in include MV45AFZB within user exit USEREXIT_FILL_VBAP_FROM_HVBAP as follows:
    <i>* Need to be able to copy the ship-to of a BoM parent down to the
    respective BoM children if the parent has a different ship-to
    from the header.
    data:  wa_xvbpa like vbpa.
    Clear: wa_xvbpa.
    read table xvbpa into wa_xvbpa with key posnr = hvbap-posnr
                                            parvw = 'WE'.
    A BoM parent line has a different ship-to from the header.
        if sy-subrc = 0.
          read table xvbap with key uepos = hvbap-posnr.
    See if current line is the child of that BoM parent
            If xvbap-uepos = hvbap-posnr.
              move wa_xvbpa-kunnr to xvbpa-kunnr.
              move xvbap-vbeln to wa_xvbpa-vbeln.
              move xvbap-posnr to wa_xvbpa-posnr.
              move 'WE' to wa_xvbpa-parvw.
              modify vbpa from wa_xvbpa.
            endif.
          Endif.</i>
    This isn't working for me.  At one point, I was able to copy the ship-to down to the first sub-item but not any subsequent ones.  I'm sure I need to add some code to another sales order user exit to get this to work, but I'm at a loss at this point.   Has anyone had to do this or something similar before? 
    Thanks very much in advance for your help.
    Angela

    Hi,
    Can you check few more things and tell me?
    - In this exit, does XVBPA and XVBAP contains all the line items. ( main and sub items ).
    - In Sales order creation time, do these table have VBELN populated when this exit triggers.
    - If you modify XVBPA or XVBAP in this exit, do they get overwritten after that.
    Try this code. See if it works.  Let me know if you still have a problem.
    DATA: wa_hvbpa LIKE vbpa,
          wa_xvbpa like vbpa.
    CLEAR: wa_hvbpa, wa_xvbpa.
    * check if HVBAP and VBAP line items are not same
    IF vbap-posnr <> hvbap-posnr.
    * read the ****-to partner from main-item
      READ TABLE xvbpa INTO wa_hvbpa WITH KEY posnr = hvbap-posnr
                                              parvw = 'WE'.
      IF sy-subrc = 0.
    *   read the line item data for sub-item based on main item
        READ TABLE xvbap WITH KEY posnr = vbap-posnr
                                  uepos = hvbap-posnr.
    * See if current line is the child of that BoM parent
        IF sy-subrc = 0.
          MOVE wa_xvbpa-kunnr TO xvbpa-kunnr.
          MOVE xvbap-vbeln TO wa_xvbpa-vbeln.
          MOVE xvbap-posnr TO wa_xvbpa-posnr.
          MOVE 'WE' TO wa_xvbpa-parvw.
          MODIFY vbpa FROM wa_xvbpa.
        ENDIF.
      ENDIF.
    ENDIF.
    Regards,
    RS

  • Address details of a BP

    Hi All,
            I want to get detailed address of a buisness partner like street,city country which are in the structure ADDR2_DATA.
    How can I fetch the data in CRM?

    Hi
    Use FM BUPA_ADDRESS_GET_DETAIL. Just pass Partner no to exporting parameter IV_PARTNER and u will get the address details in importing table ES_ADDRESS, tel no in ET_ADTEL, fax no in ET_ADFAX and email address in ET_ADSMTP.
    This works
    Thanks
    RR

  • Is there a Ship To Partner for Subcontract POs?

    I have a vendor with multiple "repair centers" around the world.  I send repairs to the various vendor locations depending on the type of repair.
    I want to use the same VN (vendor) partner for all of the repair locations.  However, the problem is that the delivery document that is created for the warehouse seems to only use the "customer address" associated to VN partner.  This does not work since there are actually multiple addresses that the repair could be sent to.
    Here are the options so far:
    1. Create different vendor codes for each "repair center".  This does not allow me to use one VN partner thus multiplying my master data.
    2. Overwrite the delivery address on the delivery document itself.  This could be an issue with timing due to the fact that we use the SAP warehouse module and they will instantly see the delivery as created.
    3. Create a custom user exit to overwrite the delivery address on the delivery document for specific repair centers (perhaps based on a custom partner that the user applies to the PO header).
    Does anybody have any other suggestions such as using other partners on the PO header?

    Hi,
    I've had a similar requirement. The ship-to is determined by the corresponding customer master. If you have multiple ship-to's for a customer and you create an order in SD, a popup comes up and asks you to choose a ship-to. In ME2o this does not happen. If you mark a specific ship-to as default, it will always pick up this one up but you're not going to change the default each time.
    I would go for a BADI or exit, which allows you to choose between the different ship-to's (just as in SD).
    MZ
    Edited by: MZ on Apr 16, 2009 9:33 AM

  • Sales Employee without HR - Maintaining Address Details

    Hi All,
    We are using Sales Employee without HR.
    When the Sales Employee is linked as a partner on a Sales Document, the address details are filled with "XXXX".
    Example:
    Name: Graham Shanks
    Street: XXXXXX
    Post Code: XXXX
    City: XXXXXX
    I want to be able to maintain the address, specifically the email address of the Sales Employee to setup an email output condition for the order confirmation.
    Please assist.
    Regards,
    Tim Reid

    Hi,
    Once you create sales employee without HR,then go to t-code,
    PAL3  or  PA30
    Select infotype text ADDRESS & click on create icon at TOP of leaft hand side
    Maintain the address detail and save it.
    My suggestion is take help of HR consultant, he will configure infotype for address.
    Kapil
    Edited by: Kapildev Farakte on Jan 6, 2010 5:17 AM
    Edited by: Kapildev Farakte on Jan 6, 2010 5:17 AM

Maybe you are looking for