Problem in replicating plant

Hai Gurus
i have problem in replicating plant.First created organisation structure in R/3.created material.and replicated material.while creating shopping cart error is popping(Plant for the follow-on -document doesnt exist).
so i replicated plant  in sa38 and checked in SLG1.here i got error"No internal standard grouping doesnt exist for plant"
Thanks
chandrasekahr

Hai muthu
thanks for replying.thing is i checked business partner ID numbers in BP transaction.so what i found is 1000001064 is the last business partner no.when i create PERSON in BP transaction it is popping the same error"no internal standard grouping exist"
Regarding  No:range for Business Partner ID (not the Business partner NO:range) from where did it pick that no:range.As ther is no matching no:range  Business Partner ID
Thanks
chandrasekhar

Similar Messages

  • Problems in replicating plants from ERP

    Hello Experts,
    In the process of setting up SRM 7.0 system,  We are running into some problems while replicating plants from ERP.
    1. BBP_LOCATIONS_GET_FROM_SYSTEM takes a very long time to execute.
    2. I can see few plants replicated in BBP_LOCMAP table, but when I search for locations in the org structure, it says no values found.
    3. I used the BP number in the BBP_LOCMAP table and  searched for business partner details in BP trxn, even there it shows BP number does not exist.
    If anyone has encountered similar problems please throw some light in resolving these issues.
    Thanks, AV

    Hi Muthu,
    The program is going in endless loop because there was some memory dump in ERP. We have resolved the issue and have successful in running the program, but In SLG1 there are errors -
    1. Business Partner "0000000x" does not exist
    2. Error Changing Location.
    Somehow the plant entries are shown in BBPLOCMAP tables with the BP numbers even though system is not generating the business partner numbers.
    I am guessing problem might be with the business partner number ranges, but I have checked everything and couldn't find any issue there either.
    Did I miss anything else?
    Thanks, AV

  • Problems replicating plants from R3

    Hi,
    I have been struggling with syncronising plants from ECC to SRM.
    In ECC i have 3 plants, (0001, 1000, 2000). I have run BBP_LOCATIONS_GET in SE38. 0001 and 1000 transfer fine when viewing the SLG1 report.
    Plant 2000 errors with "Location already exists, partner 0000000102 Plant 1000 System: ERQCLNT300 The plant is a duplicate in the same system plant:2.
    It seems to be trying to recreate plant 2000 as the same partner as plant 1000.
    is my setup wrong in ecc somewhere?!
    To create plant 2000 in ecc, I copied plant 1000 and changed the address and company details.
    Any help that can be offered wil lbe greatly appreciated.
    Iain
    Edited by: bruceiow on Feb 8, 2011 11:38 AM

    its ok.
    0001, 1000, 2000 - these three plants are available in bbp_locmap TABLE right. no issues
    now you have to map them in the organisation structure - Extended attribute --> LOCATIONS

  • Problem with replicated partitioning between two BSO db's. version 9.3.0.1

    Hi there,
    I have a problem with partitioning between two BSO db’s.
    I created the partition, it validates and I made an export for the partion definiton(xml file).
    Everything is fine if I set this partition up as transparent partition.
    This means I can see the data from the src in the trg db as ecpected.
    But when I change over to replicated (what in fact I want to do) nothing happens for the trg site - there are still no data. (Yes I have choosen Update all cells.)
    I got no error in any way neither AAS nor in the app logs of src and trg.
    (Mayby this it important: one src-dimension is mapped to void for the trg.)
    Can anyone give me a hint or even confirm this behaviour ?
    Thank you in advance
    Andre
    Below the log infos:
    log of src db:
    [Fri Dec 04 15:29:03 2009]Local/AAA///Info(1013210)
    User [hyperion] set active on database [db]
    [Fri Dec 04 15:29:03 2009]Local/AAA/db/hyperion/Info(1013091)
    Received Command [PutReplicatedCells] from user [hyperion]
    [Fri Dec 04 15:29:03 2009]Local/AAA///Info(1013210)
    User [hyperion] set active on database [db]
    [Fri Dec 04 15:29:03 2009]Local/AAA/db/hyperion/Info(1013091)
    Received Command [XferReplicatedCells] from user [hyperion]
    [Fri Dec 04 15:29:03 2009]Local/AAA///Info(1013214)
    Clear Active on User [hyperion] Instance [1]
    [Fri Dec 04 15:29:03 2009]Local/AAA/db/hyperion/Info(1023005)
    Update of replicated partition elapsed time : [0] seconds
    [Fri Dec 04 15:29:03 2009]Local/AAA/db/hyperion/Info(1243010)
    Partition refreshed
    log of trg db:
    [Fri Dec 04 15:29:03 2009]Local/AAA1///Info(1013210)
    User [hyperion] set active on database [db]
    [Fri Dec 04 15:29:03 2009]Local/AAA1/db/hyperion/Info(1013091)
    Received Command [ReqXferReplicatedCells] from user [hyperion]
    [Fri Dec 04 15:29:03 2009]Local/AAA1///Info(1013210)
    User [hyperion] set active on database [db]
    [Fri Dec 04 15:29:03 2009]Local/AAA1/db/hyperion/Info(1013091)
    Received Command [ProtocolXchg] from user [hyperion]
    [Fri Dec 04 15:29:03 2009]Local/AAA1/db/hyperion/Info(1023044)
    Processing distributed request from [P4B5A856A, AAA, db]
    [Fri Dec 04 15:29:03 2009]Local/AAA1/db/hyperion/Info(1013091)
    Received Command [PutLastUpdatedTime] from user [hyperion]
    [Fri Dec 04 15:29:03 2009]Local/AAA1///Info(1013214)
    Clear Active on User [hyperion] Instance [1]
    [Fri Dec 04 15:29:03 2009]Local/AAA1///Info(1013214)
    Clear Active on User [hyperion] Instance [1]

    It sounds like you are doing it all correctly. One thing you might try just to be sure you are not getting any data in the target database is the following:
    1) clear the target database
    2) Run the replication for all cells
    3) Run an export of all data on the target database
    See if you get anything in the export file, maybe you are getting some of the data or possibly it is a rollup issue. Just a thought.
    Jeff

  • Problem in replicating the purchase order items

    Hi,
    The Requirement  is to replicate the line items of Purchase Order in ME23N which is extracted from BAPI_PO_GETDETAIL1 and copy it  in BAPI_PO_CHANGE .
    The problem is when i am passing ACCTASSCAT(Account assignment category) it is not replicating else it is replicating.
    while debugging the program the i am getting the data into internal table but it is not getting updated in database (ME23N).
    I am getting messages in RETURN table as follows:
    Instance 4200000020 of object type PurchaseOrder could not be changed
    Purchase order item 00170 still contains faulty account assignments
    Please also populate interface parameter POITEMX
    Account 402201 requires an assignment to a CO object
    Please find the code below.

    move 'X' to LT_ITEMX-HL_ITEM.
        move 'X' to LT_ITEMX-GR_TO_DATE.
        move 'X' to LT_ITEMX-SUPP_VENDOR.
        move 'X' to LT_ITEMX-SC_VENDOR.
        move 'X' to LT_ITEMX-KANBAN_IND.
        move 'X' to LT_ITEMX-ERS.
        move 'X' to LT_ITEMX-R_PROMO.
        move 'X' to LT_ITEMX-POINTS.
        move 'X' to LT_ITEMX-POINT_UNIT.
        move 'X' to LT_ITEMX-POINT_UNIT_ISO.
        move 'X' to LT_ITEMX-SEASON.
        move 'X' to LT_ITEMX-SEASON_YR.
        move 'X' to LT_ITEMX-BON_GRP2.
        move 'X' to LT_ITEMX-BON_GRP3.
        move 'X' to LT_ITEMX-SETT_ITEM.
        move 'X' to LT_ITEMX-MINREMLIFE.
        move 'X' to LT_ITEMX-RFQ_NO.
        move 'X' to LT_ITEMX-RFQ_ITEM.
        move 'X' to LT_ITEMX-PREQ_NO.
        move 'X' to LT_ITEMX-PREQ_ITEM.
        move 'X' to LT_ITEMX-REF_DOC.
        move 'X' to LT_ITEMX-REF_ITEM.
        move 'X' to LT_ITEMX-SI_CAT.
        move 'X' to LT_ITEMX-RET_ITEM.
        move 'X' to LT_ITEMX-AT_RELEV.
        move 'X' to LT_ITEMX-ORDER_REASON.
        move 'X' to LT_ITEMX-BRAS_NBM.
        move 'X' to LT_ITEMX-MATL_USAGE.
        move 'X' to LT_ITEMX-MAT_ORIGIN.
        move 'X' to LT_ITEMX-IN_HOUSE.
        move 'X' to LT_ITEMX-INDUS3.
        move 'X' to LT_ITEMX-INF_INDEX.
        move 'X' to LT_ITEMX-UNTIL_DATE.
        move 'X' to LT_ITEMX-DELIV_COMPL.
        move 'X' to LT_ITEMX-PART_DELIV.
        move 'X' to LT_ITEMX-SHIP_BLOCKED.
        move 'X' to LT_ITEMX-PREQ_NAME.
        move 'X' to LT_ITEMX-PERIOD_IND_EXPIRATION_DATE.
        move 'X' to LT_ITEMX-INT_OBJ_NO.
        move 'X' to LT_ITEMX-PCKG_NO.
        move 'X' to LT_ITEMX-BATCH.
        move 'X' to LT_ITEMX-VENDRBATCH.
        move 'X' to LT_ITEMX-CALCTYPE.
        move 'X' to LT_ITEMX-NO_ROUNDING.
        move 'X' to LT_ITEMX-PO_PRICE.
        move 'X' to LT_ITEMX-SUPPL_STLOC.
        move 'X' to LT_ITEMX-SRV_BASED_IV.
        move 'X' to LT_ITEMX-FUNDS_RES.
        move 'X' to LT_ITEMX-RES_ITEM.
        move 'X' to LT_ITEMX-GRANT_NBR.
        move 'X' to LT_ITEMX-FUNC_AREA_LONG.
        move 'X' to LT_ITEMX-ORIG_ACCEPT.
        move 'X' to LT_ITEMX-ALLOC_TBL.
        move 'X' to LT_ITEMX-ALLOC_TBL_ITEM.
        move 'X' to LT_ITEMX-SRC_STOCK_TYPE.
        move 'X' to LT_ITEMX-REASON_REJ.
        move 'X' to LT_ITEMX-CRM_SALES_ORDER_NO.
        move 'X' to LT_ITEMX-CRM_SALES_ORDER_ITEM_NO.
        move 'X' to LT_ITEMX-CRM_REF_SALES_ORDER_NO.
        move 'X' to LT_ITEMX-CRM_REF_SO_ITEM_NO.
        move 'X' to LT_ITEMX-PRIO_URGENCY.
        move 'X' to LT_ITEMX-PRIO_REQUIREMENT.
        move 'X' to LT_ITEMX-REASON_CODE.
        move 'X' to LT_ITEMX-LONG_ITEM_NUMBER.
        move 'X' to LT_ITEMX-EXTERNAL_SORT_NUMBER.
        move 'X' to LT_ITEMX-EXTERNAL_HIERARCHY_TYPE.
        move 'X' to LT_ITEMX-RETENTION_PERCENTAGE.
        move 'X' to LT_ITEMX-DOWNPAY_TYPE.
        move 'X' to LT_ITEMX-DOWNPAY_AMOUNT.
        move 'X' to LT_ITEMX-DOWNPAY_PERCENT.
        move 'X' to LT_ITEMX-DOWNPAY_DUEDATE.
        move 'X' to LT_ITEMX-EXT_RFX_NUMBER.
        move 'X' to LT_ITEMX-EXT_RFX_ITEM.
        move 'X' to LT_ITEMX-EXT_RFX_SYSTEM.
        move 'X' to LT_ITEMX-SRM_CONTRACT_ID.
        move 'X' to LT_ITEMX-SRM_CONTRACT_ITM.
        move 'X' to LT_ITEMX-BUDGET_PERIOD.
        append LT_ITEMX.
        clear LT_ITEMX.
      endloop.
      describe table LT_ITEM1 lines LV_NO.
      sort LT_ITEM1[] by PO_ITEM.
      read table LT_ITEM1 index LV_NO.
      append lines of LT_ITEM1 to LT_ITEM.
      clear LT_ITEM.
      LV_NUM = LV_NO * 10.
      condense LV_NUM.
      concatenate '000' LV_NUM into LV_NUM.
      loop at LT_ITEM where PO_ITEM is not initial.
        LV_INDEX = SY-TABIX.
        read table LT_ITEM1 with key PO_ITEM = LT_ITEM-PO_ITEM.
        if SY-SUBRC eq 0.
          if LV_INDEX gt LV_NO.
            LT_ITEM-PO_ITEM = LT_ITEM-PO_ITEM + LV_NUM.
            modify LT_ITEM transporting PO_ITEM.
          endif.
        endif.
      endloop.
    *LOOP at i_item.
      call function 'BAPI_PO_CHANGE'
        exporting
          PURCHASEORDER = LS_TAB-V_EBELN
        tables
          RETURN        = LT_RETURN
          POITEM        = LT_ITEM
          POITEMX       = LT_ITEMX.
    *ENDLOOP.
      if not lt_iTEM[] is initial..
        call function 'BAPI_TRANSACTION_COMMIT'
          exporting
            WAIT   = 'X'.
         importing
           RETURN = LT_RETURN.
       WRITE: I_RETURN-MESSAGE.
      endif.
    endform.

  • Update Plant details from MM to SRM for an already replicated plant

    Hi All,
    In order to replicate all plants from MM to SRM, we use program - BBP_GET_LOCATIONS_ALL
    In order to replicate selected plants from MM to SRM, we use program - BBP_GET_LOCATIONS_SELECTED
    In case a plant has already been replicated from MM to SRM, and subsequently the plant address details are changed in MM,
    what is the process to reflect the changed plant details in SRM side? Is there a separate program for this?
    Please advise.
    Thanks in advance,
    Ruchika

    Hi
    LOCATIONS reports helpful to bring plant data into SRM as a business partner.
    even you do run a report again you maigh get a report that plant BP updated successfully in SLG1 log.
    you can test them in develoment box.
    but we dont deal with any processing in EBP other than plant number.
    Plant address is not a ship to address as in EBP . Ship to address attributes helps for f\delivery address.
    i believe no harm in plant ADDRESS data in srm.
    BR
    Muthu

  • Problem in replicating 3.x Datasource

    Hi Gurus,
    When i tried to replicate datasource  0BBP_TD_SC_1 , 0BBP_TD_SC_APPR_1 it is not prompting in 3.x  by default it is replicating in 7. I need it in 3.x Please share your suggestion
    Thanks!

    The datasource you are replicating, does they already exists in your system?
    You can try "Restore 3.X datsource" option in tcode RSDS..

  • Journal Problem with Replicating another dimension on User Defined

    Hi experts,
    A curious thing is happing on development, I follow the HTG "SAP Business Planning and Consolidation for NetWeaver - Journals.pdf"; and this generate fine the journal, but when I was testing, doing a simple journal entry, a trouble occurred, the template has the structure below:
    Header:
    Category
    Time
    Group
    Row:
    DataSrc
    Entity
    Account
    Intco
    Flow - SubTable
    CLucro - User Defined
    CCusto - User Defined
    So when I fill all the information to every dimension and put the amount, I save, and don't get any error message, but on CLucro and CCusto appears the value of flow, and if I consult the Infocube on listcube I get this dimensions in blank.
    Fonte Empresa Conta        TipMov CLucro CCusto IntCo Remark Debit     Credit
    AJUSTE 1161 PC011101010001 BLK BLK BLK C1161                      100
    AJUSTE 1161 PC013604030001 BLK BLK BLK C1161       100
    Does anybody know what could be ? Journal can't has user defined dimension ?
    Best Regards
    Alexandre Mendoza Collepicolo

    Hi Ethan,
    I'm on BPC version NW 7.5 SP04. The HTG is on this link:
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/00497d6a-0f38-2d10-bfb5-d50b91c9c0e5
    I'm with the same problem related by M. Weisheit on this thread
    Re: Journal entry disappear
    Someone knows what could be ?
    Best regards

  • Facing problem in replicating data containing LOB column

    Hi All,
    did everyone implemented stream replication successfully using LOB data. MY replication is up and runningas all other tables (w/o LOB columns) are replicated fine but table with LOB column giveing Insert error. Is any thing special to be done for LOB column?
    thanks in advance

    hi,
    i have these field:
    *select VBAK~KUNNR VBAK~ERNAM VBAK~AUDAT VBAK~AUFNR VBAP~KWMENG VBAP~MATNR VBAP~MATKL
      up to 10 rows
        from VBAK inner join VBAP on VBAK~VBELN = VBAP~VBELN
        into table IT_VBAKUK.
    endform.*
    I want to add these field in my parameter by using WHERE clause but don't know how to restrict these field using where clause.
    Kindly give me some example related to this.
    Regards

  • A problem about replica

    When I created LDAP master, I just create 4 LDAP replica as well.
    When I look into the service from Server Admin > Open Directory, the replica Status are OK initally.
    But now, there are 2 servers having status - ERROR PasswordService -NotFound
    I had tried to remove replica, but it seems never been removed.
    I had restarted the 2 replica server as well, no help for the situation.
    May someone help me? Thanks in advance.

    This is the MacBook Pro forum. You have a Mac Pro.
    https://discussions.apple.com/community/desktop_computers

  • Problem in replicating the material from SRM to CCM

    Hi SRM gurus
    We have material created in ECC6 and replicated to SRM, but the same material is not being replicated to CCM. Back ground job for program BBP_CCM_TRANSFER_CATALOG is running.
    we are on SRM 5.0, Extended calssic scenario.

    Hi
    Which CCM version are you using ? What steps are you doing ?
    CatalogUpdateNotification_Out is configuration on XI for the location of the XI server.
    When you run report BBP_CCM_TRANSFER_CATALOG this sends the materials to the XI server, when then sends that back to the CCM instalation (on our system this is the same client/box as the SRM application). Once there the catalog can be published through the authoring tool to the respective catalog, or a report could run to send this out.
    <u>I would suggest looking at the <b>config guide for CCM2</b> - it goes through what you need step by step.</u> Incase you don't have the same, i can email at your mail id, if any.
    <b>Please go through the SAP OSS Notes and links below, which will definitely help -></b>
    Note 979079 Increases waiting time during SRM catalog transfer
    Note 904757 Further performance improvement of BBP_CCM_TRANSFER_CATALOG
    Note 874874 To improve performance of "BBP_CCM_TRANSFER_CATALOG"
    Helpful links ->
    Re: Material/service master catalog upload (ECC-CCM)
    CCM SRM product catalog
    Re: How to load materials, contract lines & info recs directly from R/3 to CCM
    BBP_CCM_TRANSFER_CATALOG  (product catalog)
    Re: Product ID format settiings in R/3, EBP and CCM?
    Re: Uploading Product Data from SRM to CCM?
    Do let me know.
    Regards
    - Atul

  • Addindex problem on replicas

    Hi,
    My application uses two nodes, one is bdb master and the other is slave. My dbxml version is linux/2.4.14. The flag is DB_THREAD | DB_INIT_LOCK| DB_INIT_LOG | DB_INIT_MPOOL | DB_INIT_TXN | DB_RECOVER|DB_CREATE|DB_PRIVATE.
    I stop the application at the first node, then the second application become master. This is expected.
    Then I add an index (use dbxml without transcation) to the container at the first node. Some new documents are inserted into the container at the second node. Then I try to restart the application at the first node, but it fails. I got some error: BDB: PANIC: fatal region error detected; run recovery. The error can easily be reproduced. Even if I run db_recover -c -h ./, it still fails.
    How to add an index to the containers in a master/replica(slave) environment?
    Thank you very much.
    -hua
    Edited by: user10929419 on Mar 23, 2009 9:26 PM

    Hi Hua,
    >
    My bdb version is db4.7.25 with all patches. My application is using DB_PRIVATE.
    Are you using dbxml shell to add the index? In my case, dbxml shell still doen't work. Yes. I think dbxml shell doesn't support replica environment in this version. You can dig into src/utils/shell/dbxmlsh.cpp, modify the code for your special usage, re-compile the dbxml shell and try it again.
    >
    Then I wrote a program with c++ API addindex, also use DB_INIT_REP flag. It works. But I have to stop both master and replica first before I can add index to them using the program.I've try to add index into master and it works. Please make sure that:
    1. ALL PART of your operations are protected by EXPLICIT transaction.
    2. Protect your ALL operations by try&catch blocks and re-try logic. Output the caught exception may help you to see what error occur.
    If I stop only one of them(Let's say, stop master and keep slave running), index can be added successfully to master, but will then be removed from maser automatically after master is restarted. Is this reasonable?In fact you CANNOT add index on slave. And what happen is reasonable: the master re-joined the network, failed at the election and have to sync with the new master(the previous slave). So the index you've inserted is removed.
    Thanks,
    Rucong

  • Problem when replicating employees using ALE

    Hi All
    We are using the CRM 7.0. we are integrating the CRM with the ERP HCM (HR) i have assigned an internal number range for the organizational units creation and and external number range for the employees creations as I want to have the same employee number in both systems CRM and ERP . When I am trying to send employee data I got error that the number range grouping has external number assignment, and I should enter the number
    Note the employee number range in the ERP is also external as the business requirements
    When I changed the number range grouping in table  T77S0 to an internal number range the employees are replicated
    But I need to have the same number for the employees on both systems
    Thanks in advance
    Jacopo
    Edited by: CRM on Nov 11, 2009 3:44 PM

    i used this lnk
    Re: External Number Ranges in HR - CRM Integration

  • Weird Problem? Replicating Triggers

    Hello
    We are having a strange issue with DDL replication.
    Version 11.1.1.1.2_03 13555424 OGGCORE_11.1.1.1.3_PLATFORMS_120104.0600
    Release 11.2.0.3.0 ProductionThe problem is when we create triggers on source schema, it will replicate them sometimes and we are unable to find the cause for this.
    On source we have the option DDL INCLUDE ALLand on our replicat the configuration is as below:
    DDL INCLUDE MAPPED
    DDLERROR DEFAULT IGNORE RETRYOP
    MAP SOURCE.*, TARGET.*;We do have DBOPTIONS SUPPRESSTRIGGERS but I would not expect this to be a problem at all.
    Tables work fine, views, sequences and other kind of objects work properly aswell.
    Any ideas?
    Thanks in advance,
    N K

    question was not very clear as what you want as end result (replicat trigger or Not to replicate)
    "The problem is when we create triggers on source schema, it will replicate them sometimes and we are unable to find the cause for this."
    So, now I know that you really want to replicate the trigger, let me know which user you were connected as when running create trigger from sqlplus and TOAD. Also please paste your complete extract param file

  • Problem with replicating syncbo

    I am testing MDK example,
    At the stage of replication of the newly created syncbo, I get the following in Merep_ex_replic. 
    SyncBO MIAUTH does not exist
    I have tried multiple custom syncbos including MIAUTH, they all give me this error, but they do exist.
    Any idea?
    Thanks

    Hi Ezatullah Yaqub,
    After the fresh installation of MI Server component in your WAS, you will have to
    import one default request from the migration table, which contains the MIAUTH SyncBO itself.Make it sure that u have already done it or not.
    After the fresh installation of MI Server component in your WAS,
    there is one table merep_810 (Common Table for Migration), which contains one default transport request .(SyncBo MIAUTH is made available with a transaport request in the table merep_810).
    The steps for importing the default transport request are,
    1)  run the transaction merep_mig
    2)  go to table merep_810 using transaction se11.
    3)  from there you will get one default transport request number  - S6DK003813
    4)  In the Migration Tool(merep_mig), select transport action as 'Import'.Here you   have to enter the default request number and execute.
    After these steps, just go to SyncBo Builder(merep_sbuilder) and check, the MIAUTH SyncBO is there or not. If its there , regenerate it and make it enable through merep_pd(Profile Dialog).
    just refer these forums also..
    Re: How to Configure MIAUTH?
    Re: How to R3 can manage MIAUTH SyncBo
    Re: creating MIAUTH sync bo problem
       Regards,
       Kishor Gopinathan

Maybe you are looking for