Plant replication issue in SRM

Hi Experts,
We replicated around 70 plants from ECC to SRM.Each plant coressponds to unique company code only.
The only similarity in all the plants is the adress details.
After replication,faced the red error for about 5 plants out of the 70 stating "Location Already Exists, Partner: 00100025XX Plant: 1090 System: DE1XXXXXXX The Plant is a Duplicate in the same System Plant: 36XX".
I maintained the Search term field in the adress details of those 5 plants and then replicated them from ECC to SRM.Those 5 plants got replicated succesfully.This was in Development environment.
In quality system when i try to replicate the plants,am facing the same red error for 50 out of the 70 plants.
I have checked in table BBP_LOCMAP and i find no entries related to plants which are said to be duplicate.
Please advise.
Thanks in advance
Supriya

Hello,
Please find all of the information on plant replication and maintenance
below.
Firstly, see the note:
563180 Locations - Replication of R/3 plants
1. BBP_LOCATIONS_GET_ALL should be run once in your system.
This cannot be scheduled as a report.
2. For further replication of plants, please use
BBP_LOCATIONS_GET_SELECTED.
3. The reason for the error BBP_LOCATION004 is due to duplicate
address data for plants. The system will check all address fields and
look for duplicates, if any are found the system will issue this
message and the plant will not be replicated.
4. Once replicated plant address data etc should be maintained using
the browser transaction 'Manage Business Partners' BBPMAININT.
Please set this transaction up as a browser transaction
for the SRM admin user.
5. Plants can also be created in SRM using this transaction BBPMAININT.
The can be assigned to R/3 plants.
See note 563108:
"You can also create individual locations via the Web transaction
'Managing Business Partners' and assign them to an R/3 plant."
Hope this information clarifies your issue.
Kind Regards,
Edel.

Similar Messages

Plant Replication Classic Scenario SRM 3.0

Hi,
would anyone remember the report to replicate plants from R/3 into SRM in SRM 3.0
In 4.0 / 5.0 it is
BBP_LOCATIONS_GET_ALL OR
BBP_LOCATIONS_GET_FROM_SYSTEM
But these so not exists in SRM 3.0
This is urgent.
Regards,
Rahul

Other things I have checked are
1) RFc / ALE settings - they are fine as I could replicate the Prodcut Cat from backend
2)Checked the Backend Systems
3)Checked the Product Cat - Backend System.. Here I have selected each Product Category, assigned R/3 as source system and SRM as Target System (IS THIS OKAY)
4) Checked the Pur Grp - Product Cat Assignment. Pur Grp is the Org Str Id of the Pur Grp in SRM. When I select the Prod Cat, it selects the backend system automatically.
Only thing I have not done so far is that I have not replicated the Vendors. When I try to do it, it does not brings any vendors forward either. I thought I will look into this error later. I hope nothing inter-connected

An Issue in SRM

Hi,
I got an issue in SRM. How to do this?
Spend and savings reports are two of the most common reporting areas within the sourcing organization. In addition to common report characteristics like vendor name, material number, calendar year, etc., a key characteristic for sorting spend and savings data is SCO (supplier subcommodity owner). By including the SCO characteristic within the Spend/Savings cube, end users will be able to rollup spend/savings based on the vendor classification. The SCO code is assigned to a vendor in One-Source. To make this meaningful to users, the description needs to be stored in R/3 and then extracted to BW.
Kindly reply,
Thankyou,
ABC

Hi
First, let me one thing like "ET_MESSAGES" is not a database table it is an EXPORTING parameter of BADI (BBP_DOC_CHANGE_BADI).
This exporting parameter is referred to one TABLE TYPE (BBP_TMESSAGES_BADI) and internally it refers to the structure (BBP_SMESSAGES_BADI).
So, what you need to do is just capture all the error messages in to some internal table and loop the internal table and populate "ET_MESSAGES" internal table which is a exporting parameter.
Hope it helps you.
Thanks
Siva

JPY Currency issue in SRM 5 Limit Items

Hi
We are having an issue JPY Currency issue in SRM Limit Items (550 SP 13).
Basically the currencies like JPY, KWR where there are no decimals causes value to be multiplied by 100.
There are lot of notes and threads on JPY currency issues.
But I have not found one that helps fix SRM Limit Items.
Let me know if there is a note or thread that talks about it.
We are on SRM 550 SP 13.
Thank You
Nikhil

see MDM forum

Issue connecting SRM 7.01 to a R/3 4.5B back-end

Guys,
I need your help with the following. We are currently trying to connect a SRM 7.01 system to a R/3 4.5B back-end. We almost got everything working except for a small problem, maybe you can help. We are using the classic scenario and are creating purchase orders in the back-end based on a SRM SC.
First question did anyone successfully connected a SRM 7.01 system to a R/3 4.5B back-end?
The problem we are encountering is as follows. In customizing in SRM I have selected system type R/3_4.5B as the back-end system type in u2018define system landscapeu2019.This causes for the determination of driver FM B45A_PO_CREATE when SRM wants to create the PO in the back-end (BBP_PD_SC_TRANSFER ).This action succeeds because the PO is created in the back-end.
However, the next action of BBP_PD_SC_TRANSFER is to read the data again from the back-end via FM B45A_PO_GETDETAIL. This synchronous call is done in order to update the SC status in SRM and create the linkages in BUS2121. This last action fails, because at the time the get detail Bapi is executed by SRM, the EKKO table in the back-end is not yet up to date and error u2018W5 107 purchase order does not existsu2019 is issued by the BAPI_PO_GETDETAIL in te back-end. This causes the SC in SRM to get status I1112 (error in process). Even though this status is issued in SRM, the PO is available in the back-end without any errors if I check this via ME23.
What I see is if I debug the SC transfer process and wait 1 or 2 seconds between the B45A_PO_CREATE and B45A_PO_GETDETAIL. The issue is not there. In this case it appears that the EKKO table is updated on time in the back-end and the B45A_PO_GETDETAIL can be processed in SRM without problems in order to update the SC status. I get status I1113 follow-on document created in this case.
Thus my conclusion is there is a timing issue when connecting to a R/3 4.5B system. Does anyone know a solution. Our thought goes to a small enhancement in the B45A_PO_GETDETAIL FM creating a timer to wait a second before the execution and fetching of the data. I tried it and it worked. But of course I prefer a standard SAP solution. Did anyone experienced similar behavior? Or knows a standard SAP solution to this problem?
Appreciate your help.
Best regards,
Skander

Hi Surender,
The code changes in this note only apply if the system type is u201CERP_Xu2019u201D. This is not the case over here, we are trying to connect to a R/3 4.5B system.
Some additional info, we have multiple back-ends connected. All ECC back-end function correctly and for these we do not have the problem. Only for the very very old R/3 4.5B system.
Any way I tried the note but no luck. This because of the above.
Thx.

10.9: Server Replication Issue

Hi ther guys,
I have seen several posts about this replication issue since 2012, i have 2 fresh install systems 10.9 Server app 3.0.2 on both boxes DNS shows correctly setup but im totaly lost on where to continue.
Is there anyone out there that already resolved this?
domaintest2:~ admin$ sudo slapconfig -createreplica 192.168.2.17 diradmin
Password:
2014-01-08 01:05:11 +0000 slapconfig -createreplica
diradmin's Password:
2014-01-08 01:05:22 +0000 1 Creating computer record for replica
2014-01-08 01:05:26 +0000 command: /usr/sbin/slapconfig -delkeychain /LDAPv3/127.0.0.1 domaintest2.int$
2014-01-08 01:05:26 +0000 Added computer password to keychain
2014-01-08 01:05:26 +0000 Adding ldap and host service principals
Unable to obtain kerberos princ, using CRAM-MD5: -2
Unable to obtain kerberos princ, using CRAM-MD5: -2
2014-01-08 01:05:26 +0000 2 Creating ldap replicator user
2014-01-08 01:05:26 +0000 _ldap_replicator exists from previous replica - migrating
2014-01-08 01:05:26 +0000 NSString *_getReplicatorPasswordWithNode(ODNode *): no syncrepl attribute found in results
2014-01-08 01:05:26 +0000 Unable to get replicator password, recreating replicator
2014-01-08 01:05:27 +0000 GetLastServerID: Error creating DSLDAPContainer: 77014 Can't contact LDAP server (-1)
2014-01-08 01:05:27 +0000 ServerID for this replica 1
2014-01-08 01:05:27 +0000 SetLastServerID: Unable to create DSLDAPContainer: 77014 Can't contact LDAP server (-1)
2014-01-08 01:05:27 +0000 Error setting last server id
2014-01-08 01:05:28 +0000 command: /usr/bin/sntp -s time.apple.com.
2014-01-08 01:05:29 +0000 3 Updating local replica configuration
2014-01-08 01:05:29 +0000 4 Gathering replication data from the master
2014-01-08 01:05:29 +0000 5 Copying master database to new replica
2014-01-08 01:05:29 +0000 Removed directory at path /var/db/openldap/openldap-data.
2014-01-08 01:05:29 +0000 Starting LDAP server (slapd)
2014-01-08 01:05:30 +0000 slapd started
2014-01-08 01:05:30 +0000 Stopping LDAP server (slapd)
2014-01-08 01:05:31 +0000 command: /usr/sbin/slaptest -f /etc/openldap/slapd.conf -F /etc/openldap/slapd.d
2014-01-08 01:05:31 +0000 command: /usr/sbin/slapadd -c -w -l /var/db/openldap/openldap-data/backup.ldif
2014-01-08 01:05:31 +0000 command: /usr/sbin/slapadd -c -w -b cn=authdata -l /var/db/openldap/authdata/authdata.ldif
2014-01-08 01:05:31 +0000
2014-01-08 01:05:31 +0000 52cca45b slapd is running in import mode - only use if importing large data
52cca45b bdb_monitor_db_open: monitoring disabled; configure monitor database to enable
2014-01-08 01:05:31 +0000 6 Starting new replica
2014-01-08 01:05:31 +0000 Starting LDAP server (slapd)
2014-01-08 01:05:31 +0000 slapd started
2014-01-08 01:05:31 +0000 command: /usr/bin/ldapmodify -c -x -H ldapi://%2Fvar%2Frun%2Fldapi
2014-01-08 01:05:31 +0000 command: /usr/bin/ldapsearch -x -LLL -H ldapi://%2Fvar%2Frun%2Fldapi -b cn=config -s base olcServerID
2014-01-08 01:05:31 +0000 command: /usr/bin/ldapmodify -c -x -H ldapi://%2Fvar%2Frun%2Fldapi
2014-01-08 01:05:31 +0000 Starting password server
2014-01-08 01:05:37 +0000 CFStringRef CopyHostGUID(DSLDAPContainerRef, CFStringRef): Could not get query results
2014-01-08 01:05:37 +0000 FATAL : Could not retrieve HOST GUID for parent
2014-01-08 01:05:37 +0000 FATAL : Could not retrieve HOST GUID for parent (error = 78)
2014-01-08 01:05:37 +0000 Deleting Cert Authority related data
2014-01-08 01:05:37 +0000 No intCAIdentity, not removing int CA from keychain
2014-01-08 01:05:37 +0000 command: /bin/launchctl unload -w /System/Library/LaunchDaemons/com.apple.xscertd.plist
2014-01-08 01:05:37 +0000 command: /bin/launchctl unload -w /System/Library/LaunchDaemons/com.apple.xscertd-helper.plist
2014-01-08 01:05:37 +0000 command: /bin/launchctl unload -w /System/Library/LaunchDaemons/com.apple.xscertadmin.plist
2014-01-08 01:05:37 +0000 Updating ldapreplicas on primary master
2014-01-08 01:05:37 +0000 Unable to create ODNode for domaintest1.int: 2100 Connection failed to the directory server.
2014-01-08 01:05:37 +0000 Primary master node is nil!
2014-01-08 01:05:37 +0000 Unable to locate ldapreplicas record: 0 (null)
2014-01-08 01:05:37 +0000 Error setting read ldap replicas array: 0 (null)
2014-01-08 01:05:37 +0000 Error setting write ldap replicas array: 0 (null)
2014-01-08 01:05:37 +0000 ODRecord *_getODRecord(ODNode *, NSString *, NSString *, NSArray *): ODNodeRef parameter error
2014-01-08 01:05:37 +0000 int _removeReplicaFromConfigRecord(ODNode *, NSString *): ODRecord not found
2014-01-08 01:05:37 +0000 Error synchronizing ldapreplicas: 0 (null)
2014-01-08 01:05:37 +0000 Removing self from the database
2014-01-08 01:05:37 +0000 Warning: An error occurred while re-enabling GSSAPI.
2014-01-08 01:05:38 +0000 Stopping LDAP server (slapd)
2014-01-08 01:05:39 +0000 Stopping password server
2014-01-08 01:05:39 +0000 Removed all service principals from keytab for realm DOMAINTEST1.INT
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/__db.001.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/__db.002.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/__db.003.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/__db.004.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/__db.005.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/__db.006.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/altSecurityIdentities.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/apple-config-realname.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/apple-generateduid.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/apple-group-memberguid.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/apple-group-nestedgroup.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/apple-group-realname.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/cn.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/DB_CONFIG.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/dn2id.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/entryCSN.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/entryUUID.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/gidNumber.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/givenName.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/id2entry.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/ipHostNumber.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/log.0000000001.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/macAddress.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/memberUid.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/objectClass.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/ou.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/sn.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/uid.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/openldap-data/uidNumber.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/authdata/__db.001.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/authdata/__db.002.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/authdata/__db.003.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/authdata/__db.004.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/authdata/__db.005.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/authdata/__db.006.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/authdata/alock.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/authdata/authdata.ldif.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/authdata/authGUID.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/authdata/DB_CONFIG.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/authdata/dn2id.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/authdata/draft-krbPrincipalAliases.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/authdata/draft-krbPrincipalName.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/authdata/entryCSN.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/authdata/entryUUID.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/authdata/id2entry.bdb.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/authdata/log.0000000001.
2014-01-08 01:05:39 +0000 Removed file at path /var/db/openldap/authdata/objectClass.bdb.
2014-01-08 01:05:39 +0000 Removed directory at path /var/db/openldap/authdata.
2014-01-08 01:05:39 +0000 Removed file at path /etc/openldap/slapd_macosxserver.conf.
2014-01-08 01:05:39 +0000 Removed file at path /etc/openldap/slapd.conf.
2014-01-08 01:05:39 +0000 Removed directory at path /etc/openldap/slapd.d/cn=config.
2014-01-08 01:05:39 +0000 Removed file at path /etc/openldap/slapd.d/cn=config.ldif.
2014-01-08 01:05:39 +0000 Removed directory at path /etc/openldap/slapd.d.
2014-01-08 01:05:39 +0000 Removed directory at path /etc/openldap/slapd.d.backup/cn=config.
2014-01-08 01:05:39 +0000 Removed file at path /etc/openldap/slapd.d.backup/cn=config.ldif.
2014-01-08 01:05:39 +0000 Removed directory at path /etc/openldap/slapd.d.backup.
2014-01-08 01:05:39 +0000 Stopping password server
2014-01-08 01:05:39 +0000 Removed file at path /etc/ntp_opendirectory.conf.
2014-01-08 01:05:39 +0000 Removed file at path /Library/Preferences/com.apple.openldap.plist.

We're having the exact same issue, also between two 10.9 servers - any luck finding a resolution?

Active directory SYSVOL replication issues

Hello.
I have 2 domain controllers, both of them on the same site DC1 & DC2. I have added a new site with a DC3. When I have added DC3 to the domain, I have realized, SYSVOL was not initialized correctly. I went back to DC1 and found out, there's following
error in the event viewer:
Error: 4012 on DC1
The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 99 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter
(60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected.
Error: 2213 on DC2
The DFS Replication service stopped replication on volume C:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication
WMI method to resume replication.
This indicates a DFS replication issue between DC1 & DC2 and probably this would be the reason, why the SYSVOL was not properly initialized on DC3.
How can I restore correct DFS replication between DC1 & DC2? I've read
this article, but it's not clear to me, which of the 2 domain controllers has a good version of SYSVOL + I can not find a decent step-by-step article for reconnecting Windows 2012 domain controller.
Any idea, how I can proceed further here?

Here's a complete documentation with resolution of my issue. I have created this documentation for my own purposes in our WIKI, so I will paste it here (I hope, it will help somebody else in the future):
The Problem
We have bought a new server for our domain. This server (NEWDC01) was promoted to be a domain
controller in the DOMAIN. After the promotion, I have added a single computer to the domain. When I have logged on the client to the domain, I realized, this computer is not using the new domain controller (NEWDC01)
for authentication, but DC02 domain controller instead. This is not intended. Local clients should use local domain controllers for authentication (assuming, the Active directory sites & services are configured properly). Further investigation revealed,
there are some replication errors on OLDDC01 & OLDDC02 servers. First I need to solve these replication errors. Then I can
add the NEWDC01 server to domain properly.
Analysis
There are several errors related to DFSR replication on both domain controllers:
Error: 4012 on OLDDC01
The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain.
This server has been disconnected from other partners for 99 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder
until this error is corrected.
Error: 2213 on OLDDC02
The DFS Replication service stopped replication on volume C:. This occurs when a DFSR JET database
is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.
In order to have active directory in a healthy condition, one must ensure, there’s a successful
replication between existing domain controllers up and running. If the replication does not work correctly, you can expect bunch of issues.
group policies and logon scripts are not applied correctly, or as intended
when you want to add a new domain controller to the domain, it will not work as expected (although, you will not see any specific errors after the
server is promoted to be a domain controller)
Active directory backup
I have scheduled an AD backup on OLDDC01 server using the ‘Windows Backup’ solution to make sure,
I can restore the AD / SYSVOL, in case something goes wrong. The backup is scheduled to be executed every day.
Active directory restore
In this particular case, I will talk only about SYSVOL restore. As indicated above, we must get
rid of the DFSR event viewer errors which you can find in event viewer. One of them is indicating, that the JET database was not shut down cleanly and autorecovery was disabled. The other error indicates, the SYSVOL volume is no longer replicated. I am not
sure, what is the reason, why the AD’s in the domain stopped to replicate. Probably it was an unclean server shutdown. The DFSR service stopped to replicate the SYSVOL share and I was not aware about that. When the replication did not run for more than ~99
days, the SYSVOL share was excluded from the DFSR replications.
Find out the most accurate SYSVOL share in the domain
I have compared the content of the SYSVOL directories on both OLDDC01 and OLDDC02 servers: C:\Windows\SYSVOL\domain\Policies.
Both directories have 37 subdirectories. Each subdirectory corresponds to one group policy. This means, that the content is approximately the same, thus I can’t tell, which version is most recent. I do most of the GPO changes on OLDDC01, so I made a conclusion,
that this server contains the most recent version of the SYSVOL share.
There are 2 types of SYSVOL restores, you can do:
Authoritative restore
Non-authoritative restore
Non-authoritative restore
This is a more simple kind of a restore. You can perform this kind of restore, when you are sure,
that one of the domain controllers is authoritative (e.g. you presume, the SYSVOL share is intact and working properly). If you can identify such a working server, you can perform non-authoritative restore of the active directory on a broken domain controller.
Authoritative restore
In this case, you can designate a specific domain controller to be authoritative. You set a special
flag on this server, which will prohibit to overwrite it’s state from another domain controllers, when the replication is enabled on the server again. After you designate one server to be authoritative, you need to update all the another domain controllers
using the non-authoritative procedure.
In this article, you can find, how to perform authoritative vs. non authoritative AD resotre:
http://support.microsoft.com/kb/2218556.
In my case, I was not sure, which of the domain controllers had a more recent copy of AD, so I
have decided to make OLDDC01 authoritative (check the link above). Once this has been done, I have made a non-authoritative update on OLDDC02 server.
Everything was almost ready. The last step, I needed to execute was, I needed to fix the ‘JET’
event viewer error on SRVBK1. In the event log entry on the bottom, you can find following:
Recovery Steps
1. Back up the files in all replicated folders on the volume. Failure to do
so may result in data loss due to unexpected conflict resolution during the recovery of the replicated folders.
2. To resume the replication for this volume, use the WMI method ResumeReplication
of the DfsrVolumeConfig class. For example, from an elevated command prompt, type the following command:
wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig
where volumeGuid="D37A9FC3-8B1D-11E2-93E8-806E6F6E6963" call ResumeReplication
For more information, see http://support.microsoft.com/kb/2663685.
Final words
After I have executed this command, the replication was again started between OLDDC01 and OLDDC02
servers. After I have started up the NEWDC01 server, I have realized, it has automatically replicated the contents of the SYSVOL share - almost immediately after the server was started up. I have again tried to login with the local client into DOMAIN domain
and now I see, that local client is using local Domain controller for authentication.
Everything seems to be OK now.

AD replication issue. had 1722 error after running repadmin

Hi,
I got 1722 error ( The RPC server is unavailable) when I run repadmin /replsummary. The result points that one source DSA is having 1722 error and the problem DC is the DC I run repadmin command from.
Do it make sense. Why DC itself cannot rpc to itself?
Thanks
Qing

I would start with what is mentioned in this Wiki article: http://social.technet.microsoft.com/wiki/contents/articles/18513.active-directory-replication-issues-basic-troubleshooting-steps-single-ad-domain-in-a-single-ad-forest.aspx
That should be a good start for troubleshooting.
This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Get Active Directory User Last Logon
Create an Active Directory test domain similar to the production one
Management of test accounts in an Active Directory production domain - Part I
Management of test accounts in an Active Directory production domain - Part II
Management of test accounts in an Active Directory production domain - Part III
Reset Active Directory user password

Replication issue between lync 2010 FE and lync 2013 FE

Hello
I face any issue in my lync server's .
I was in the last steps in the migration process from lync 2010 to 2013 enterprise edition .
where CMS was moved already to 2013 , and later on many time I checked the replication and it was fine , then I deleted the CMS DB FROM 2010 FE and I checked the replication and it was fine .
later on I proceed to delete the archiving server and monitoring server and it was fine .
later on I proceed to
Reset call admission control
Prevent sessions for services
Stop Lync Server 2010 services
Remove a Front End Server from a pool
I just I face this replication issue after I start the process to delete the lync 2010 pool which im stuck on it now .
one more thing while I was trying to delete the 2010 front end pool , I got the error .
Error: An error occurred: "System.InvalidOperationException" "Cannot publish topology changes. Conference directories still exist on a pool that would be deleted. Remove the conference directories before continuing."
so I moved the conference directories from 2010 pool to the 2013 pool successfully.
but later on when I check the replication I notice the replication issue ?
Get-CsManagementStoreReplicationStatus
UpToDate           : False         """""""""""""""""""it is already shutdown
ReplicaFqdn        : HQ-EDGE01.mydom
LastStatusReport   :
LastUpdateCreation : 3/23/2015 11:22:17 AM
ProductVersion     :
UpToDate           : True
ReplicaFqdn        : HQ-LYNC2013-FE.mydom
LastStatusReport   : 3/19/2015 5:21:27 PM
LastUpdateCreation : 3/19/2015 5:21:25 PM
ProductVersion     : 5.0.8308.556
UpToDate           : False
ReplicaFqdn        : HQ-LYNC-FE-01.mydom
LastStatusReport   : 3/19/2015 11:38:25 AM
LastUpdateCreation : 3/23/2015 11:52:17 AM
ProductVersion     : 4.0.7577.0
then I run the
I run Invoke-CsManagementStoreReplication
Get-CsManagementStoreReplicationStatus
UpToDate           : False     """""""""""""""""""it is already shutdown """"""""""""""""""
ReplicaFqdn        : HQ-EDGE01.mydomain
LastStatusReport   :
LastUpdateCreation : 3/23/2015 10:18:22 PM
ProductVersion     :
UpToDate           : True
ReplicaFqdn        : HQ-LYNC2013-FE.mydomain
LastStatusReport   : 3/23/2015 10:18:26 PM
LastUpdateCreation : 3/23/2015 10:18:22 PM
ProductVersion     : 5.0.8308.556
UpToDate           : False
ReplicaFqdn        : HQ-LYNC-FE-01.mydomain
LastStatusReport   : 3/19/2015 11:38:25 AM
LastUpdateCreation : 3/23/2015 10:18:22 PM
ProductVersion     : 4.0.7577.0
====================
Get-CsManagementStoreReplicationStatus
UpToDate           : False """"""""""""""" it is already down """""""""""""""""""""
ReplicaFqdn        : HQ-EDGE01.mydomain
LastStatusReport   :
LastUpdateCreation : 3/23/2015 10:53:23 PM
ProductVersion     :
UpToDate           : True
ReplicaFqdn        : HQ-LYNC2013-FE.mydomain
LastStatusReport   : 3/23/2015 10:18:26 PM
LastUpdateCreation : 3/23/2015 10:18:22 PM
ProductVersion     : 5.0.8308.556
UpToDate           : False
ReplicaFqdn        : HQ-LYNC-FE-01.mydomain
LastStatusReport   : 3/19/2015 11:38:25 AM
LastUpdateCreation : 3/23/2015 10:53:23 PM
ProductVersion     : 4.0.7577.0
why LastUpdateCreation : 3/23/2015 10:53:23 PM from the lync 2010 pool ????
I'm not doing any change on 2010 pool now (I just try to delete it ) , all the change it is on 2013 pool .
for edge server 2013 I shut down the server since there is another configuration issue there (so replication to edge server not the issue now since it is down).
my question is this will affect my lync 2013 since it is the production now ? is this un completed steps for removing the 2010 pool affect my production.
is the replication issue affects my 2013 pool ?
Kind Regards
MK

Hi,
From your description above, did you mean before deleting the Lync Server 2010 Pool from topology, you found the replication of Lync 2010 FE Server not update to date?
If it is the case, based on my knowledge, there is no affect for Lync Server 2013 Pool. Please double check if Lync Server 2013 Pool work normally, and Lync users in Lync 2013 Pool can use all Lync function without issues. Then you can delete Lync 2010 Pool
from Topology and publish it. After finish it, please re-run step 2 on Lync Server 2013 FE Servers.
Best Regards,
Eason Huang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Eason Huang
TechNet Community Support

DC Replication issue

Hello Team,
We have built a new Domain Controller in our environment with OS 2003 Server.
While checking for replication from an existing server (using the command repadmin /replsummary) I get and an as below:
1753 - NLHAAAHDC002
(NLHAAAHDC002 is the DC name that is built new)
Also if I run the same command on the new server (NLHAAAHDC002) I get the error that as below:
"'repadmin' is not recognized as an internal or external command,
operable program or batch file".
An urgent response is appreciated.
Regards,
Suman Rout

Hi Suman,
Please refer the below link on Microsoft KB article for Troubleshooting steps - DC Replication issue,
http://support.microsoft.com/kb/2089874/en-us
Regards,
Gopi
JiJi
Technologies

Plant/Location Address issue in SRM

Hi All,
We are on SRM 5.O R/3 4.6C , Extended Classic scenario
We are dealing with a weird issue at this time. The issue is, in the Plant address country is being changed by an unknown program.
I looked at the plants address in R/3 , it is not changed there. And we dont run any batch job for updating plant details between SRM and R/3. All we have are standard SRM jobs set up as the background jobs (Clean req, getstatus 2 vendor update).
Has anyone ran in to weird issue like this? Can someone please give me pointers? let me know what should I be doing in fixing this weird issue.
Thanks in advance.

Hello Krishnav,
If i understand correctly, you think location address was changed in SRM and not in R/3 ?
Check CHUSR, CHDAT and CHTIM fields in BUT000 table: they will give you user ID who made last modifications and when.
Those address modifications should have been done directly is SRM (using Web GUI) or running BBP_GET_LOCATION_XX reports.
Regards.
Laurent.

SRM product category replication issue

Hi,
I am trying to replicate the product category from ECC to SRM
I have run the R3AS, but no success,
In SRM SMQ2 no entry created
In ECC SMQ1 no entry created
In R3AM1 "DNL_CUST_PROD1" is running status, not changing to green
I also found that
In R3AM1 DNL_CUST_BASIS3 also running and both the status is block
Please help to resolve status.
Thx
Jai

Hello Roy,
Kindly follow the below steps to resolve the issue here.
1) Maintain the table TBLSYSDEST in both SRM and ERP system with regards to the logical system and Technical and Dialog rfc's.
Also assign the MW_admin in the rfc user.Register the queues with * smqr.
2) Follow the sap note 720819 and maintain all the 5 tables correctly.
3) Before you start the download, you must use transaction SE38 to execute the report BBP_PRODUCT_SETTINGS_MW in the EBP system. In the 'User' field, enter the consumer name that you selected (for example, "SRM").
Select the radio button depending on whether service products should be active or not. The report starts with the default settings in test mode.
4) Ensure that the table CRMATAB in ERP system holds the entries after the step 1. IF it is blank then follow the sap note 1498111 and run the report SMOF_FILL_CRMATAB in SRM.
5) Also check for the R3-Guid in the tables CRMMLSGUID (SRM system) and CRMPRLS (ERP system ). Both should be identical with the logical system.
Kindly abort and load the object again, it should work fine.
Also to replicate the new material groups, you need to trigger the delta load.
Best Regards,
rahul

HR - SRM Replication: Issue with company code and cost center

Hello Experts,
We have a scenario where we are trying to replicate the HR Org Structure into the SRM system.
All the standard settings have been made using relevant SAP Notes and other help available on SRM.
However, the company code and cost center for a particular position are not getting updated into SRM.
These details are present in the Inbound Idoc from the ECC system.
Is there any setting we may have missed out on?
Please help.

Hi
Kindly check your ALE Filter in BD64 in the sending system. You need to maintain the objects C K O S and infotype 1001 and related subtypes in the filter model.
Also check the Evaluation path that you are using to send data.
Regards
Vijay V

Vendor Replication Issue

Hello Experts,
We are in SRM 7.0 classic scenario.We are facing an issue in Vendor replication as described below:-
We have connected a new backend R/3 system to the SRM system i.e now the SRM system is connected to 2 backend R/3 system.
We replicated the vendor from the new backend R/3 system as shown below
1.Transaction BBPGETVD to bring the vendors from the new backend R/3 system into SRM system
2.Transaction BBPUPDVD to update the vendor from the new backend R/3 system.
There were around 25000 vendors linked to the Required Purchasing org in the the new backend R/3 system, but out of these only 2 could be replicated.
We verified the Vendor Replication as described below
1) SE16-Table VENMAP(logsys-new backend R/3 system)
2) SE16-BBPM_BUT_FRG0061(To confirm the Org ID of the Porg for which these vendors are extended)
We can see that the vendor are from the New backend R/3 system and extended for the required Porg.
However, when we try to search for these vendors in the SRM portal, we are unable to find it.
Can you all experts, plz let us know
1. Why only 2 vendors were successfully replicated from the new backend R/3 system?We checked the vendors status using LFM1 & LFB1 and could see many more vendor could had been replicated.
2.Why we were unable to search for the vendors in portal inspite of the fact the we can see the vendor in VENMAP and also in the BBPM_BUT_FRG0061(we have ensured that we are putting the correct Porg ID in the search for eg. 0 5*******) and also we can search the vendor from the old R/3 system?
We would like to also mention that we have same vendors with different vendor numbers in different backend R/3 system.
Any pointers to resolve this issue will be highly appreciated.
Regards,
RKS

Hello Experts ,
I forgot to mention that ,i'm getting following warning message:-
Warning:
If you use external number assignment,you will lose data records
Number of supplier lost                                   23.333
The following allocation results from the transfer.
Total number of suppliers:                              23.335
Adoption of R/3 description                            23.333
Can you all experts plz explain what is "external number assignment" and also we are using option transfer only R/3 number
but still why 23.333 verdors are lost
Thank you in advance for suggestions,
Thaks & Regards,
RKS

Replication issue in MDG-S

Hello Experts,
We are trying to do an MDG implementation for Vendor master data. We are using the Data Model BP for this. Initially we have done all the configurations for master data BP. Later since we wanted the Master Data to be Vendor, we changed the configurations to Vendor instead of BP. Now we are facing issues in replication of Vendor master into the ECC system. MDG and ECC reside in the same system. We see the Access Class 'CL_MDG_BS_SUPPL_TYP2CHK_ACCESS' assigned in the Reuse area. We are a lot confused between the BP settings and Vendor master data settings. We have got the following queries, request your reply
          1. Whatever configuration that are given in the config guide for Vendor we have done that. Is there anything else needed to be done for the config?
          2. Do we require to do UIBB setting changes for Vendor and BP separately?
          3. Is replication required for Vendor Master Data?
          4. Does the reuse area Access class required to be changed for Vendor Master?
Kind Regards,
Thamizharasi N

          1. Whatever configuration that are given in the config guide for Vendor we have done that. Is there anything else needed to be done for the config?
you got the check the following
General BP setting.
Supplier settings
CVI integration setting under each node of MDGIMG
          2. Do we require to do UIBB setting changes for Vendor and BP separately?
Check out the changes mention in Config.doc if change needs to done do it.
          3. Is replication required for Vendor Master Data?
Replication of data depends on your business requirement whether you need to create them in SRM or visa-versa.
          4. Does the reuse area Access class required to be changed for Vendor Master?
          currently we are using the access class with no issue ,hence continue using it if no issue
regards
shankar

Plant replication issue in SRM

Similar Messages

Maybe you are looking for