Replication of IDOC in R/3

Hi,
I had a query that in an inbound scenario of Idoc..after XI processed from source to target Idoc..How it is going to replicate in SAP R/3..as vendor master or customer master..
Thanks & Regards
Guna

hi,
>>>going to replicate in SAP R/3..as vendor master or customer master..
if you need specific details on those two IDOC then
for CREMAS (vendor) use process code CRE1
for debmas (customer) use process code DEBM
for general details about IDOCs and XI I'd propose my book:
www.sap-press.com/product.cfm?account=&product=H1935
Regards,
Michal Krawczyk

Similar Messages

Failure in the SOAP Runtime: Employee Master Data Replication Using IDoc OTM_EMPL

During employee master data replication from ECC to CfTE, we encountered the following error:
Unexpected element -el=OTM_EMPL ns=urn:sap-com:document:sap:idoc:soap:messages
We are using the 1402 WSDL for Replication of Employee Master Data with Employment Details (humancapitalmanagementmasterd2). The payload was not received in CfTE.
Can anybody please advise how to resolve this issue?
Thank you.

Dear Joselito,
This issue need deeper investigation in customer system.
Kindly report an incident for SAP Support for further help.
Regards,
Rahul Mishra

HR Replication - poSition replication with IDOC status 52

Hi,
When I replicate the poSition, I got the following waring messages (IDOC status 52). Please help
Relationship 008 (from 01S 5xxxxxxx to employee 0000xxxx ) will be ignored
Message no. HRALX00_ORG532
Employee 0000xxxx does not have a central person
Message no. HRALX00_ORG535
Thanks
Pranav
Edited by: Pranav on Feb 18, 2008 3:14 PM

Hi, Pranav.
Have you solved this proplem? I have the same issue.

MDG Replication model required for MDGF with Co-Deployment?

Hi MDGF experts,
We are implementing MDGF 6.1 and I am not sure if I have to set up a replication model if MDG should send to the same client(Co-Deploy) and if we need to perform Key mapping if we use the standard OG data model.
In another document I read that you still have to setup Replication model for MDGF if you post to the same client. http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/6043b83f-1a37-3110-cd8e-f2dabb672019?QuickLink=index&… but this document is for MDG 7.
If, I do indeed have to setup Replication model do I use Replication via Idoc, services, RFC?
Your help will be highly appreciated
Thanks and best regards
Riaan

Hi Abdullah,
Thanks for the document. In the document it describes settings for HUB and ECC client. To me it looks like you have to create 2 profiles for end to end communication for HUB and target. Thus if in my instance I want to replicate in the same client do I still have to setup 1 profile as hub and a second profile for ECC on the same client or do I use the same profile and add all the target and hub services definitions in the same profile or only the target system settings.
Also what do I do about integration scenario configuration in the MDG hub system and integration scenario configuration in the MDG target system or do I only have to do it for target system seeing in my instance it is the same system.
Thanks and best regards
Riaan

MDG-F Data Replicate within same client

Hi
Let me explain my understanding about data replication.
Data replication with SOA method is used only for replication of data into non sap system.
Data replication with ALE/IDOC method is used only for replication of data into sap system.
Please confirm above basic understanding.
My scenario is as per below
In SALE we defined LEOCLNT300 : Logical Systm for MDG HUB/LEO_300 : Logical System for MDG Target Client)
In SM59 define RFC Destinations for both logical systems
IN WE21 define ALE tRFC port with RFC Destination for LEOCLNT300
In BD64 define distribution Model with all meaasge types (GLAMAST,COSMAS,PRAMAS,COELEM,COGRP1,COGRP2 and COGRP6)
In WE20 define partner profiles for partner Type LS
Thus we complete our ALE distrbution setting
Now for DRF configuration
We assign BO types with business System LEO_300 and assign each BO Type to communication channel Replication via Idoc
We definde Data Replication Model ZF with outbound parameter 1012 (General Ledger Account Master Idoc)
Then we activated data replication model.
But when we execute DRFOUT it only shows Green signal but no data replicated from MDG tables in to ECC ( We have two active records for GL accounts in MDG database like /1MD/MD______01into ECC Data base like SKA1

Hi Kiran
Group COA is not used in our case
And below if screen shot for GL count from FS00
Is there any releationship of GL account group with GL account replication? In MDG-F also I selected GL account group field as it is reqiured field

HR Replication - only part of org structure needed in SRM - excess IDOC's

Dear peers,
we are running HR-ALE to replicate HR master data from a separate HR system (ECC 6) into the ERP system (ECC 6, with SRM as add-on).
Only a part of the organizational structure is needed in SRM, this O-unit is specified in PFAL for initial replication. Delta replication is setup through change pointers - as recommended by SAP.
Unfortunately change pointers are generated for the complete org structure, not just for the org part we are replicating into SRM. This results in a lot of IDOC's that go into error because of missing and irrelevant data.
What can we do to avoid generating IDOC's that are not needed?
> continue with the change pointers, and filter out non-relevant data via user exit on outbound side
> switch off change pointers, and schedule PFAL in update mode instead
> perhaps the root org structure can be specified in the ALE distribution model filter as well so IDOC's generated from change pointers take this into account
Thanks for your point of view on this topic
Cheers, Linda

Hi Linda,
In our project SAP is the single point of truth. So we are not stopping any replication pertaining to postion and organization unit in SRM as well as CRM from SAP.
Having said that user is assgined to postion and user has role. As a results if any user doesn't have any role related to SRM and CRM , user will not be replicated. In that case those user deosn't have any authorization to access the SRM systems though their postion and organization unit may be avaialble in SRM.
otherwise : switch off change pointers, and schedule PFAL in update mode instead
This will be simplest methods
Regards
Dayal

Whats the best method to stop IDOC generation and ECC replication?

Hi Gurus,
I would like to do mass data conversion in CRM (adding data origin field for bp's) , during this process i dont want IDOC to be generated and any replication to ECC , how to achive this in tweaking middleware ?
Vinay

Hi
Try tcode SMW3_00 and make an enty into the table with the following:
BDOC_TYPE = BUPA_MAIN
DONOTSEND = 'X'
Paparao Undavali

MDG-F Data replication for CCH using IDOC

Hi
Can anyone explains differance between Cost Center Hierarchy and Cost Center Group in MDG? As per my KX CCH in MDG is Alternative CCH in ECC not Standard CCH in ECC as it is created in Customization for Controlling Are.We can able to create alternative CCH in MDG with single processing also but when trying to replicate in ECC
SLG1 logs says as per below
Here it says CCH uses SOA but we maintained IDOC,Is CCH replication is not possible through IDOC with message type COGRP1.
Secondally we maintained ZG replication model but it says DIRECTLY replication Model . Any Clue?
Also how to assign MDG alternative hierarchy to ECC Standard Hierarchy node in MDG or we have to do it in KSH2 only from ECC side?

Hello Sanjay,
you've already create a similar thread http://scn.sap.com/thread/3585348 with the same screenshot and similar questions. Please do not open multiple threads for the same questions.
Thank you for your understanding
Michael

IDoc status 53 in employee replication from SAP HR

Hi experts,
We are having some problems in CRM BP creation with role employee.
We are using CRM 5.0 and SAP ECC 6.0 and we are trying to replicate employees information to CRM from HR.
After read the notes 934372, 615896, 550055, 363187, 312090 we made the next configuration steps in our systems:
R/3:
- Creation of connection port (trans. WE21)
- Creation of logical system (trans. WE20) and assignment of outbound message HRMD_ABA
- Creation of distribution model (trans. BD64) with all filters indicated in note 312090
CRM
- Creation of logical system (trans. WE20) and assignment of inbound message HRMD_ABA
- Creation of conversion between basic types HRMD_A05 and HRMD_ABA01 (trans. WE70) as described in note 312090
- Creation of conversion between message types HRMD_A and HRMD_ABA (trans. WE73) as described in note 312090
- Creation of external number range ZE from HR01200001 to HR01299999 (using PA04 in R3 we found the number range between 01200001 and 01299999)
- Creation of BP Grouping with the same name of number range (ZE) checked to be external too
- Update of table T77S0 (using SM30):
HRALX HRAC X
HRALX PBPON OFF
HRALX PBPHR ON
HRALX PBPON ON
HRALX PNUMB 3
HRALX PPROL BUP003
HRALX PSUBG ZE
PLOGI PLOGI MV
We know we should have the same value in R3 and CRM for PLOGI/PLOGI, so we created in CRM MV because that is the plan version used in R3. To create it, we just manually add a new row in table T778P and then selected it in table T77S0. Is this the correct way to create a plan version?
After these steps, in R3 we execute program RHALEINI with parameters:
- Plan version = MV
- Object type = P
- Object ID = an active employee
- Reporting period = all
- Transfer mode = Insert
- Receiving system:
Receiving partner No = DCRCLNT300 (logical system created in WE20)
Message type = HRMD_ABA
And everything looks fine in R3.
In CRM, using trans. WE05, we can see that the iDoc is created, apparently without problems with status 53 - "Applicaton document posted" but the business partner is never created.
Did we miss some configuration steps?
Should we do something more after see the iDoc in CRM to create BP?
Thanks in advance.
Alda

hi pratk bhai,
ya i have done the same setting what Ada has mentioned eariler,
and as of your suggestion to maintatin the mandatory infotype, i have even done tht,
after running RHALEINI in R3, the status is all green here.
when i run the tcode BD87 to check the Idoc status its showing fine (Error free).
now, through tcode se38 the report CRMHRALE_CENTRAL_PERSON shows all the employees as status green,,
but the partner number is not getting generated. ( i have used HRALX-PNUMB= 3 (Prefeexing the number range coming from R3)).
kindly advice me what should be done in order to generate a BP number for the replicated HR Employee.
best regards,
Madhup

Issues in employee replication from ECC to CRM through ALE/IDOC

Hi,
We are replicating the employees from ECC to CRM through ALE/IDOC.
Some times for some employees, the Idoc status in CRM is 52(Application document not fully posted) in CRM (WE02 tcode)
If I see the details its showing as " Identification Category BPCCOD is Not Assigned to Any Identification Type"
What I need to do now to avoid this.
Pl suggest
Regards
BABU.

Hi Babu, I'm having the same error when I replicate my employes. I have define BPCCOD in spro - Cross-Application Components - SAP Business Partner - Business Partner - Basic Settings - Identification Numbers, but this configuration does not resolve my problem.
Could you resolve this problem?.
Pls. let me know...
Regards,
George

Data replication problem in SRM using inbound idoc FM IDOC_INPUT_HRMD

Hello Experts,
We are using FM IDOC_INPUT_HRMD for replicating HR data in SRM 5.0.
Now the data which was passed to port is in insert mode i.e in transaction PFAL we are passing Idoc in Insert mode.
So this means whatever data exist in target system that should be overwritten by this new Idoc data.
The Idoc which is created in target system (in SRM) is in status 52 & message is 'Business Partner already exist',
So data is not posted in system due to this error.
Idoc details as below:
Process code:HRMD
FM: 'IDOC_INPUT_HRMD'.
Could you please help in this?
regards,
Amol'

Hi
Authorizations might be one of the reason.
So IDOC transfered but no records to be writeen to DB.
regards
vijay

User Master Replication thru ALE IDoc

Hi,
I have a scenario where i have to replicate the user master data from one server to another using ALE IDoc.
Can anybody explain the procedure to do so emphasising on
- Which message type to use?
- Is there a need to create port?
- Extending any Basic type?
etc.
Thanx in advance...

Hi Aarti,
First you do the ale configuration. After creation of logical system go for following steps.
1. Rfc destination(sm59).
2. Port creation(WE21).
3.Partner profile creation(WE20).
4.Distribution Model(BD64)- After creation disribute it.
5.Check the availability of intended user in SU01D.
6. From CUA in se38 execute RSCCUSND, make entry of Receiving system and User again execute, you will get Userclone idocs in 03 status then in 12 status, then monitor these idocs at receiving systems.
Thanks,
Asit Purbey

What is the diffrence btween IDOC and BDOC?

what is the diffrence btween IDOC and BDOC?

Hi,
In short Idoc is an Intermediate Document and Bdoc is an Business Document.
Data can Be Transferd from Sap to Non Sap using Idoc where as we can transfer
data between sap to sap in Bdoc.
IDoc
IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions
BDOC
BDoc is a business document which is technically similar to an IDoc. BDocs are used to communicate data between two systems.
BDocs come in two types. One is the message BDoc (MBDoc) and the second is the Synchronizing BDoc (SBDoc).
MBDoc is used for replicating the data between SAP CRM and SAP R/3
SBDoc is used for replication and realignment between SAP CRM and mobile clients
som times SAP will be integrated with som other third party systems
ex SAP with BAAN here we should comunicate one to other systems
here we can integrate using EDI technology in this the formate of data will be in I DOCS EX :EDI is a bridge between 2 systems .I doc is a container to transfer data from one sys to other
this Idocs we can use in ALE technology also
BDoc is called Business Document,
BDoc represents data in a structural format. This sturctural architecture is use to either input data to system or send data to other system.
BDocs are data carrier that can either collected in system(Inbound) or can be send out of system(Outbound)
Please refer following link:
http://help.sap.com/saphelp_crm40sr1/helpdata/en/ec/8d7e3a7e760b55e10000000a114084/content.htm
Thanks,
Medha.

Vendor Master Replication Error from ECC to SUS : Error in ALE Service

Dear Experts,
We are implementing MM SUS (SRM 5.0). As a part of this we need to replicate vendors from ECC to SUS system via XI. We have created a Reduced Message Type Z_CREMAS_SUSMM and had set up the partner profile in WE20 with SUS logical system as destination and specifing the Message Type, and port of the XI system
We executed the transaction BD14 for replication, it is resulting in error 29 : Error in ALE Service : Entry in Outbound table not found.
Please provide inputs to overcome this problem
Thank you,
Regards,
Ravi

Hi,
Check
Re: Idoc Error Status "Entry in outbound table not found "
Looks like some issue with the partner profile set up for the sender or receiver of the EDI message in WE20.
Set up them again and When these have been set up try reprocessing your IDocs from BD87

Replication of Business Partner Data from ECC to legacy

Hi,
My requirement is to replicate any changes made to Business Partner,should immediately get reflected in the legacy.
Which is the best method to follow.I am planning to use ABAP proxies instead of IDOCS.
As the replication needs to be immediate,Can I use ABAP Proxy.?
And for tigerring this proxy I need to enhance the code for Business Partner(BP) to call the proxy.
Is my approach correct or do I need to follow any other approach.
Regards,
Vinod Kumar.

Hi,
The approach should be based on the kind of data you want to upload in SAP. if you want to upload some standard process documents like Sales order/ purchase order then it will be good to use IDOC. As we have Standard IDOCs available in SAP to upload such document in ECC. In case you want to track the change in data from BP which is not part of any standard process then in that case you can go for ABAP proxy.
If you are using ABAP proxy you dont need to call it from BP. From BP the changes will be sent to PI (in the form of File/database Query/JMS Queues ..etc ). Then PI will call inbound proxy from ECC and post the data.
Please let me know if you have any other Qs.
Shweta.

Replication of IDOC in R/3

Similar Messages

Maybe you are looking for