Attribute ADDR_SHIPT Ship to address

Hi,
I have a problem I cannot resolve that for some of my users the Ship to address number has been maintained in the attributes in PPOMA_BBP so that the user has a default delivery address. However, no matter what we do the ship to address is not defaulting into the cart even though the address can be found via the F4 search help from the cart itself. Does anyone know why this would happen as it only happens for a few users?
Thanks
Andrew

Hi Andrew
Are they inherited the ship to adress attribute? which version of SRM 550 or 700?
interesting..
however display
what is the entry for your address number.
check boxes?
Use Address as: 
  Standard Address 
  Ship-To Address     Copy as Default 
  Invoice Recipient Address     Copy as Default 
Does addresses have BP number .check in adrc table too
br
Muhtu

Similar Messages

  • Delivery address _ Attribute ADDR_SHIPT

    Hi experts
    We have maintain plant wise addresses in the tab "Edit Internal addresses"  and asssigned the delivery address numbers to the attribute ADDR_SHIPT in PPOMA_BBP.
    However when we are creating the shopping cart it pick up the default address maintained in the Edit Internal Address where there is radio button for default address.
    can we deactivate that radio button and direct that the address should be picked up from the attribute ADDR_SHIPT.
    This is required so that when user creates a SC the address is defaulted  from the ADDR_SHIPT.
    We have tick on as default in PPOMA_BBP - ADDR_SHIPT attribute.
    Can some throw light on this,
    regards,
    Nimish Sheth

    Nimish,
    In SRM, you can create addresses in the system (stored in table ADRC) and asssign them to a business partner.
    This business partner should be your company code org ID defined in PPOMA_BBP.
    The format of your flat file should contain the fields needed by the function I gave in this thread. It should at least contain the mandatory fields (ex: description, name, street, post code, city, country).
    One issue: the addresses might be created with the BUPA/company name instead of the entered name/description (this can be overrided by a BUPA BADI).
    Those addresses will get a new address number in SRM (ADRC & BUT020).
    When transfering data to backend documents, delivery addresses can be passed to R/3, where a new address will be created (a new ADRC entry).
    Look at a recent thread on transfer of delivery address to R/3 and related OSS notes.
    Rgds
    Christophe

  • Ship to address Attribute Table

    Hi SRM Experts
    We are looking for the table where in we can find the ship to address number for all SRM users.
    thanks

    Hi
    use this FM BBp_read_attributes and give input user,orgstr no and  attr as addr_shipt and in the output you may get the address number by using of this address number pass this value into ADRC table you will get all details address.
    regards
    Muthu

  • SHIP-TO address from HR?

    Hello all,
    we would like that HR is maintaing Ship-To address for all users in EBP.
    Which infotype is that?
    Is that address transferred as user address (business partner address) or as another company ship-to address (like creating through "Edit internal adresses"?
    TIA
    Gordan

    Hi Mike,
    In our scenario the default settings are catched by the user's attributes in the org structure. For example ship to address is brought by the attribute ADDR_SHIPT. I thought this was the standard functionning.
    Best regards,
    Laurent.

  • Ship to address doesn't display in PO

    Hello all.
    When one of our purchasers made a PO, this PO doesnu2019t display the ship-to address, the field is empty. The user was customized in PPOMA_BBP with several internal addresses and we check one of them like default address, however the field still empty.
    This case only appear whit one user, in others users, include user of the same unit org. the addresses are ok.
    Please, any suggestion?

    Hi Rahul
    can you see his shopiing cart. since ship to address must copy into PO from sc.
    however check his attribute inheritance
    bbp_read_attributes
    The ship to addresses are maintained manually in SRM system .
    do you maintain ADDR_SHIPT maintained in PPOMA_BBP
    The ship to addresses are maintained using web transaction 'Edit Internal Addresses'.
    br
    muthu

  • To delete the default flag set in ship to address screen in shopping car.

    Hi All,
            I have a requirement to delete the default flag that will be set in ship to address screen in shopping cart in SRM system.
    I am able to view the list of ship to address throuh Edit internal address ( transaction BBPADDRINTC) and I am able to change the default. The requirement is, the requester should not set default at all so it should be cleared even if he sets.
    I tried with Badi - BUPA_ADDR_UPDATE. But couldn't find it useful.
    Please guide me on this.
    Thanks,
    Ramya

    Hi
    You must have maintained address number of ship to attribute in the organisation structure .
    so there you take up action.
    ADDR_SHIPT = 1233
    so CHECK THIS ADDRESS NUMBER 1234
    br
    muthu

  • Not defaulting through the Ship to Address from a previously created Cart?

    Hi Folks,
    Does anyone know of a way that prevents a new Shopping Cart defaulting through an performance locations and ship to address from a previously created Cart?
    The issue we have is that the system is holding the previously used one on all new Carts. Our preferance would be for the system to clear these fields out. I would be interested to hear how other sites have dealt with such an issue.
    Thanks, Mikey,

    Hi Mike,
    In our scenario the default settings are catched by the user's attributes in the org structure. For example ship to address is brought by the attribute ADDR_SHIPT. I thought this was the standard functionning.
    Best regards,
    Laurent.

  • SRM 7.0 Ship-To Address

    All,
    I am trying to determine how I can build and maintain a list of delivery addresses in SRM 7.0. I realize tht all company codes have an address which can be used as a deliver to address, but in 5.0, you could use the transaction "Maintain Address for Own Company" where you could add as many addresses for a company code you wanted. You could then set this address as a "Ship-to" address or something else if desired. The user could have this maintained in PPOMA_BBP in the GUI, OR they could perform a search when creating a shopping cart.
    I can find delivery addresses I create (or have been created based on th ecompany creation) in the table ADRC in the SRM 7.0 GUI, however, I can not select any of these addresses when in the shopping cart as ship-to/delivery addresses.
    Does anyone have any input on this? I don't know how a shopping cart can be created without having to free-text a manual delivery address for every line item of every shopping cart.
    Thanks in Advance -Eric

    Purchasers can set the following addresses and defaults for suppliers or for themselves:
    Ordering address
    Ship-from address
    Invoicing party address
    System administrators can set the following addresses and defaults for their own company (purchasing side):
    Ship-to address
    Invoice recipient address
    ==
    Define the attributes Ship-to address (ADDR_SHIPT) and Company (COMPANY) at least once at a high level in the organizational plan. The number of the organizational unit is then copied to the COMPANY attribute. The Ship-to address and Company attributes are then inherited by organizational units at a lower level in the organizational plan. If you define other organizational units as subsidiaries, you can identify these as separate legal entities with different addresses using these attributes.
    Hi Eric
    if you maintain a address number in the ADDR_SHIPT . you must get a address.
    br
    Muthu

  • Endereço Ship to Address em itens vindos de requisições de compras

    Olá amigos.
    Estamos usando o SRM 5 no cenário clássico extendido e estamos enfrentando um problema durante a migração de requisições de compras proveniente de um backend para o SRM:
    O procedimento é referente ao endereço Ship to Address e acontece no seguinte caso:
    (01) Criamos uma requisição de compra (PR) no R/3 e enviamos para o SRM;
    (02) O endereço de entrega dos itens (Ship to Address) é sempre preenchido com o endereço da Organização de Compras definido na aba de endereço da Organização de Compras no PPOMA_BBP (este endereço também pode ser visto como o endereço principal da Organização na BP);
    (05) Quando nós criamos um pedido (PO) para a PR através do Portal e tentamos mudar o endereço de entrega (Ship to Address) para algum já existente (usando o search help disponível  na tela), as únicas opções de endereço são aqueles que estão listadas como endereço de entrega (Ship to Address) para a Organização de Compras na transação BP. O problema é que mesmo depois de escolher o novo endereço, quando voltamos para a tela de parceiros, o nome do endereço ainda aponta para o endereço antigo.
    Levando em consideração que:
    (01) Nós não estamos usando ADDR_SHIPT atributo de PPOMA_BBP;
    (02) Utilizamos a transação BP para manter quatro endereços de entrega (Ship to Address) para a Organização de Compras.
    temos dois problemas:
    (01) Como devemos proceder para preencher o endereço de entrega (Ship to Address) do item no SRM com o mesmo endereço preenchido para o item na PR? É possível por configuração ou só por customização?
    (02) É possível corrigir o erro relatado no item 5 acima realizando alguma configuração ou somente através de customização?
    Por favor nos ajudem com essas questões que nos são críticas.
    Obrigado,
    Evandro Miasato

  • Error while updating Ship to Address on Sales Order form

    hi ,
    A user is trying to update the ship to address on a standard sales orders screen, this is pretty common and never caused any issues. However with one particular order the user gets the following error :
    "You cannot update Ship To Location; the standard value rule set prevents override. "
    This is an Oracle shipped message and not custom code. The message name is OE_SEC_UPDATE_VIOLATION whose text is : You cannot update &ATTRIBUTE; &REASON
    Seems like REASON is the message : OE_SEC_SV_VIOLATION, whose text is
    " the standard value rule set prevents override. "
    This is a message shipped by Oracle Order entry. I am not able to locate this message since the oracle shipped files are not available to us and this is not in any database code(i searched the code)
    Does anyone know when this message is thrown. It seems like some value set error but am not able to figure out where it is being set.
    Any help in this will be appreciated.
    Thanks

    Did you check if any Processing rule is defined for Ship to location update :
    Setup> Rules > Security > Processing constraint ?
    Maybe this order matches condition that prevents this field from being updated.

  • Ship-To Address/Performance Location

    Hi experts,
    i'd like to know the origin of the default values into the tab "Ship-To Address/Performance Location".
    Are these valuesthe same values which are in the "Plant" into Organizative Structure (ppoma_bbp)?
    Are they replicated on the back-end? (ecc 6.0)
    Regards
    andrea

    Hi,
    The ship to addresses are maintained manually in SRM system and do not come from backend. However plant addresses are replicated but they are attached to Location address and not assigned as Ship to address.  The ship to addresses are maintained using web transaction 'Edit Internal Addresses'. Here you can create ship to address as well as Invoicing addresses. All addresses are attached to the company code Business partner. After creating these addresses you can maintain one of the addresses as default using 'Ship to' attribute in ppoma_bbp.
    Regards,
    Sanjeev

  • Ship to addresses output list in F4 help in PO

    Hi all,
    SRM 5.0 SP12 ECS.
    In std,in process PO transaction,when I click on f4 helpfor ship to address ,the list show only the address for company code which is mainateind  in  the org structure.
    My reqt is to display all the ship to addresses for the company/porg for the buyer who is creating the PO so that he can change the ship to address to any other address than the defayult address which gets selected from his attributes mainatine din the org structure.How do I achieve this??Is this possible?
    Thanks.

    Hi Experts,
    Any update?

  • Populating Ship-to-address

    Hi all,
    I have to populate the default address into ship-to-address/performance location when the user attributes have incorrect address. If the user attributes are correct it is getting defaulted correctly. If it is incorrect i want to populate that adress, so i have implemented the BBP_DOC_CHANGE_BADI (BBP_SC_CHANGE). Here i have internal table it_partner where i can get the address details. And in chaging et_partner table i want to insert a row for partner function '23'. But it is not updating that row.
    Can any one help me how to proceed or any other BADI to update the address. thanks in advance.
    vinoth

    Hi,
       If you are using the table it_partner,you can check for the record where partner no is 27(For Ship to address).But when you are using the CHANGE badi,you need to move the data frm all the importing tables to the changing tables.
    i.e.  move it_item[] to et_item[].
        move it_account[] to et_account[].
        move it_partner[] to et_partner[].
        move it_orgdata[] to et_orgdata[].
        move it_hcf[] to et_hcf[].
        move it_icf[] to et_icf[].
    HTH.
    BR,
    Disha.
    Pls reward points for helpful answers.

  • How to create hundreds of  SHIP TO ADDRESS in SRM 7.0

    Hi Experts,
    We are configuring SRM7.0 with ECC6 ( Ehp4) having Classic Scenario .
    In ECC we are maintaing the Delivery Address  at Storage Location level  and we have such approx 4000 storage Location Address and so in SRM the Delivery Address in Shopping Cart should be address of the Stoarge Location.
    But in SRM 7.0, the attribute ADDR_SHIPT is maintained for the "Internal Buiness Partner : Purchasing Companies".
    1. Can anyone suggest, how these large no. of addresses ( i.e. approx 4000) can be created for One Purchasing Company ?
    2. By using some BADi, while creating the S/C,  is it possible to pull the address of the Storage Location & fill the address in S/C , when this Sto.Loc will be entered ?
    3. Is it possible to keep the Delivery address BLANK in the S/C, by NOT maintaing the ADDR_SHIPT at all, so that while creating the Classic PO, system will pick up the delivery address of Sto .Loc in ECC and it will appear in tyhe PO Form ?
    Waiting for reply.
    Thanks
    NAP

    Hi,
        Sorry for the delay we wrote the program in SRM and when running it will call R/3.
    report  zebp_address_synch    no standard page heading
                                  message-id com_product
                                  line-count 65
                                  line-size 100.
    *Include for Data
    include zebp_address_synch_top.
    *Include for Subroutines
    include zebp_address_synch_sub.
                    At Selection-screen on value request
    *at selection-screen on value-request for p_org.
    **search help for p_org
    perform f_search_help.
    *Initialization.
    initialization.
    *initialize the parameter with default RFC dest
      perform f_get_rfc_dest.
    *get the titles in the EBP system from table TSAD3
      perform f_get_titles.
    *get the all organizational units flagged as companies
      perform f_get_is_company.
                    At Selection-screen validation
    at selection-screen.
    *Check either the storage location range or the plant range is entered
    *on the screen
      perform f_validate_input.
                          START OF SELECTION                         *
    start-of-selection.
    *Check data and get the corresponding company code
    perform f_check_data.
    *check the selection screen values
      if p_org is initial.
    *check the selection screen values and the get the plant-org relation
        perform f_filter_data.
      endif.
    *If No Error then Proceed
      if g_error ne 'X'.
    *select data from R/3
        perform f_select_data.
      endif.
    *If No Error then Proceed
      if g_error ne 'X'.
    *clear workarea
        clear: i_plant_wa.
    *process one record at a time from i_plant table
        loop at i_plant into i_plant_wa.
    *Process the data from the internal table
          perform f_process_data.
    *refresh all internal tables and global vaiables used to store data
         perform f_refresh_local.
    *clear workarea
          clear: i_plant_wa.
        endloop.
      endif.
                          END OF SELECTION                           *
    end-of-selection.
    *summary of run
      perform f_write_summary.
    *Transfer Messages to Application Log
      perform f_transfer_message.
    *Refresh all The Internal tables Used
      perform f_refresh_tables.
    *&  Include           ZEBP_ADDRESS_SYNCH_TOP
    tables: hrt5502,hrp1001,bbp_pdorg,bbp_pdbei.
                          Types                                          *
    types:begin of t_part_addr,
    *Fields for Partner and Address Number     
      partner     type bu_partner, "Business Partner Number
      addrnumber  type ad_addrnum, "Address number
       end of t_part_addr.
    types:begin of t_st_addr,
    *Fields for Partner and Address Number     
      mandt      type sy-mandt,        "Client
      werks      type werks_d,         "Plant/Valuation area
      lgort      type lgort_d,         "Storage Location
      lfdnr(3)   type c,               "Sequential address number
      addrnumber type ad_addrnum,      "Address number
       end of t_st_addr.
    types:begin of t_addr,
    *Fields for Partner and Address Number     
      partner    type bu_partner,      "Partner Number
      addrnumber type ad_addrnum,      "Address number
      adext      type bu_adext,         "Storage Location
       end of t_addr.
    types:begin of t_org,
    *Fields for org unit     
      object_id    type pd_objid_r,    "Object ID
      short_text   type short_d,       "Object Abbreviation
      long_text    type stext,         "Object Name
      comp_code    type bukrs,         "Company Code
      comp_name    type butxt,         "Name of the company code or company
       end of t_org.
    types:begin of t_org_1,
    *Fields for org unit     
      object_id    type pd_objid_r,    "Object ID
      werks        type werks_d,       "Plant/Valuation area
       end of t_org_1.
                          Types                                          *
    types:begin of t_plant,
    *Structure for storing plant/valuation area
      werks  type werks_d, "Plant/Valuation area
      bukrs  type bukrs,   "Company Code
       end of t_plant.
                          Internal Tables                                *
    data:
    i_part_addr type standard table of t_part_addr initial size 0,
    i_st_addr type standard table of t_st_addr initial size 0,
    i_addr_ext type standard table of t_addr initial size 0,
    i_addr_key type standard table of addr_key initial size 0,
    i_adrc type standard table of adrc initial size 0,
    i_adr2 type standard table of adr2 initial size 0,
    i_adr3 type standard table of adr3 initial size 0,
    i_adr6 type standard table of adr6 initial size 0,
    i_adrc_1 type standard table of adrc initial size 0,
    i_adr2_1 type standard table of adr2 initial size 0,
    i_adr3_1 type standard table of adr3 initial size 0,
    i_adr6_1 type standard table of adr6 initial size 0,
    i_org_unit type standard table of t_org initial size 0,
    i_org_stru type standard table of t_org_1 initial size 0,
    i_objects type standard table of bapi_objec initial size 0,
    i_plant type standard table of t_plant initial size 0,
    i_messages type standard table of bapiret2 initial size 0,
    i_message_tab type standard table of balmi initial size 0,
    i_title type standard table of tsad3 initial size 0.
                        Work Areas                                       *
    data:
      i_part_addr_wa       type t_part_addr,
      i_st_addr_wa         type t_st_addr,
      i_addr_ext_wa        type t_addr,
      i_addr_key_wa        type addr_key,
      i_adrc_wa            type adrc,
      i_adr2_wa            type adr2,
      i_adr3_wa            type adr3,
      i_adr6_wa            type adr6,
      i_org_unit_wa        type t_org,
      i_org_stru_wa        type t_org_1,
      i_plant_wa           type t_plant,
      i_messages_wa        type bapiret2,
      i_message_tab_wa     type balmi.
                        Global Variables                                 *
    data: g_error(1)  type c,
          g_failed    type sy-tabix,
          g_exists    type sy-tabix,
          g_modified  type sy-tabix,
          g_inserted  type sy-tabix,
          g_deleted   type sy-tabix,
          g_comp_code type bukrs,
          g_partner   type bu_partner.
                        Constants                                        *
    constants:
         c_object        type balhdr-object             value 'SRM',
         c_subobject     type balhdr-subobject          value 'ZST_SYNC',
         c_msgid         type sy-msgid                  value 'COM_PRODUCT',
         c_i             type sy-msgty                  value 'I',
         c_e             type sy-msgty                  value 'E',
         c_w             type sy-msgty                  value 'W',
         c_num           type sy-msgno                  value '898',
         c_otype         type swhactor-otype            value 'O',
         c_cocode        type om_attrib                 value 'COCODE',
         c_207           type hrp1001-relat             value '207'.
        c_as            type bbp_det_account-acc_cat   value 'AS',
        c_v             type bbp_det_account-acc_cat   value 'V',
        c_j             type bbp_det_account-acc_cat   value 'J'.
    Selection Screen
    selection-screen begin of block b5 with frame title text-001.
    selection-screen begin of block b1 with frame title text-0s1.
    *Plant
    select-options: s_plant for bbp_pdbei-be_plant no-extension obligatory.
    *Storage Location
    select-options: s_sloc for hrt5502-storage_loc no-extension obligatory.
    selection-screen end of block b1.
    selection-screen begin of block b3 with frame title text-0s3.
    selection-screen begin of block b3b with frame title text-0s4.
    *Organization Unit
    *select-options: s_org for hrp1001-objid no intervals no-extension.
    *Organization Unit
    parameters: p_org type hrp1001-objid no-display.
    selection-screen end of block b3b.
    selection-screen end of block b3.
    selection-screen end of block b5.
    selection-screen begin of block b4 with frame title text-002.
    *RFC Destination
    parameters: p_rfc type bbp_backend_dest-dest obligatory.
    selection-screen end of block b4.

  • Address number , person number and address type in Ship to address

    HI All,
    We  are working on SRM 6.0.
    In our system we have ship to address as partner function 27 in  shopping cart line item  .
    If all the line items in the same shopping cart have same address  then also we are getting different  address number , person number and address type in the partner functions of SC line items.
    In ship to partner function,  how the address number , person number and address type is decided?
    Your inputs will be valuable for us.
    Thanks
    Snehal

    Hi
    Ship to address no is set up at company level - you can also create a ship to address and you can main in the attribute ship to address.
    if you enter the ship to address manually then new address number might be created.
    What is the setting in your existing system.
    for eg. create a sc with 2 line item  let one from inherited ship to address and anothe ritem you undo them and enter new address.
    and click partner function 27 for line item 1 and 2 in the bbp_pd and it takes you to crmd_partner table and show you different address no.
    br
    muthu

Maybe you are looking for