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

Similar Messages

Value Mapping replication from SAP

Hi
I have gone thru the Blogs and threads related to value mapping replication from SAP.
Inmy observervation http://sap.com/xi/XI/System of SAP BASIS 7.00
still I have some doubts...
1)what is the differnce between ValueMappingReplication(Asynchronous) and ValueMappingReplicationSynchronous .
when we will use them.
2) Message type ValueMappingReplication contains Operation ,GroupId,Context,scheme,agency.
what is the meaning of Operation??
what is the use of group ID??
is this necessary to maintain all these values in Ztable and also source and target values ?? and use them in Abap aproxy logic??
3) is there any Message Mapping Needed.?? and Interface Mapping Needed to implement value Mapping replication??
but in this blog
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1301i [original link is broken] [original link is broken] [original link is broken] didnt find any interface mapping .
4)what is the Sender Adapter type ??
5) if I did replication from SAP..can I see the details in ID
please guide me
regards
munna

hi
1)what is the differnce between ValueMappingReplication(Asynchronous) and ValueMappingReplicationSynchronous .
In sync you will get the value mapping replication status back and in async you won't. In sync based on the response u can update again in case of any failure. If data size is large use async.
2) Message type ValueMappingReplication contains Operation ,GroupId,Context,scheme,agency.
what is the meaning of Operation??
The operation that you are going to perform. Below is the operations list and the contents to be set in the message for the same
Insert = all fields must be set;
Delete =all fields must be set;
DeleteGroup = fields GroupID and context must be set;
DeleteContext = field Context must be set;
DeleteContextGeneric = Context contains the starting part for the context to be deleted
what is the use of group ID??
Displays the different representations of an object.
A value mapping group is identified uniquely by a GUID.
You can also assign a name to a value mapping group.
is this necessary to maintain all these values in Ztable and also source and target values ?? and use them in Abap aproxy logic??
no. system creates the value mapping table. you can take it frm there. no need of any ztables.
3) is there any Message Mapping Needed.?? and Interface Mapping Needed to implement value Mapping replication??
You will be sending the value mapping data from a sender system. If it can sent in the same format not required, otherwise you will have to.
4)what is the Sender Adapter type ??
Any adapter...depends on the sender system.
5) if I did replication from SAP..can I see the details in ID
You can see it in Cache monitoring in RWB.
for more details refer
http://help.sap.com/saphelp_nw70/helpdata/EN/13/ba20dd7beb14438bc7b04b5b6ca300/content.htm
rgds
Arun

What triggers idoc posting in outbound message from sap ?

Do change or create events can be used to trigger Posting to IDOC? Have any body used idoc for outbound message sending from SAP?

Hi Reddy,
Posting IDoc Packets
Two groups of function modules are used to post IDocs:
· Function modules which process IDocs in mass. These transfer packets of IDocs for which individual IDocs are updated in the same Logical Unit of Work (LUW).
· Function modules which process one IDoc per call.
· INPUTTYP contains the code for posting function modules.
To display the function module's INPUTTYP on the ALE Development screen, choose IDoc ® Inbound Processing ® Function Module® Maintain Attributes (BD51).
INPUTTYP can contain the following values:
· "0", for function modules which process IDocs in packets.
"1" and "2" for function modules which process one IDoc per call:
If you post the IDocs immediately, the SAP sending system determines the packet size. ALE inbound processing can recognize if the posting function module allows packet processing and if so, passes the IDoc packet to it. If not, the IDoc packet is split into individual IDocs.
If IDocs are posted in the background, you can specify the size of the IDocs to be generated in the program RBDAPP01.
If you use function modules that can process IDocs in mass, the database load is reduced.
If you group IDocs into packets, this may also be practical for function modules that post inbound IDocs one at a time, because the ALE layer calls the function module several times in the same dialog process, thereby reducing the administrative load on the SAP system.
If program RBDAPP01 carries out the background processing, as a guide, you should use a packet size of between 20 and 100 IDocs.
Packet processing and parallelism complement one another. Packet processing and parallelism complement each other, although in some situations they may compete with each other. If the size of the packet is too big, this may mean that not all the available dialog processes are being used.
Scheduling IDoc Posting
There are two ways of posting IDocs in ALE inbound processing:
·        Immediate processing:
Upon receipt inbound IDocs are immediately released for posting. ALE inbound processing splits the IDoc packets into individual IDocs.
·        Background processing
Inbound IDocs and IDoc packets are first saved in the database. IDoc packets are split into single IDocs beforehand.
The program RBDAPP01 later releases the saved IDocs for processing. Single IDocs can be put into packets and then processed.
Perform the following steps:
1.       Set-up background processing (IDoc/ALE area menu):
IDoc Interface/ALE ® Administration ® Runtime Settings ® Partner Profiles (WE20)
Then the required setting is: In the detail screen Inbound Parameters select the option Trigger by background program.
2.       Schedule posting (ALE customizing):
Transaction SALE ® Set-Up System Monitoring ®
         Posting IDocs in Recipient System ®Schedule
You can also process the IDocs manually by passing them to the posting function module. In ALE Administration choose Monitoring ®Status Monitor (BD87), select the IDocs and then select Process.
Regards,
Kumar.

Inserting a conversion routine in SLT replication from SAP EWM system to HANA

We are a new SAP HANA customer trying to get the 1st report out… having few issues with data replications from SAP EWM system. EWM material conversion use a Kernel level FM to convert material GUID code to human readable material code, HANA does not use this routine so we are exploring whether we can insert ABAP routine to update the SLT replication or conversion logic, for example we can call EWM: CONVERSION_EXIT_MDLPD_OUTPUT routine and update human readable material code into correct data field in HANA. With this HANA can see the reportable material code directly. We came across few SLT specific FM’s in EWM, but need to find an enhancement spot to insert a code. I really appreciate If any of you SLT experts can let us know what would be the best way to do this.

Hi,
well, some correction notes for SP08 were missing. Mea culpa :-) Unfortunately implementation of the notes did not solve all Problems. Now the field length is correct but the field order and "not null"-Status of the fields is still wrong.
Best regards
Harry

Downloading Employees photos from SAP: ECC6

Hi Experts,
There are lot of photos for employees in system. Now client is asking to download the photos.
How to download those photos.
OAAD is uploading the photograph similarly is there any Tcode or table where we can download the photos directly
Thanks in advance. . .
rgds

Hai,
Try the below link, might help.....
http://sap.ittoolbox.com/groups/technical-functional/sap-hr/download-the-employee-photo-from-sap-46c-version-1551699?cv=expanded
Regards,
Yoganand.V

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

EDI IDOC OUTBOUND send Purchase Orders from sap to vendors

Hi Experts,
I am new to EDI IDOCS, but i got object on this. So my requirement is purchase orders are send to vendors from sap (OUTBOUND) through EDI-850 format. and also i have to add some more fields to standard idoc type ORDERS05, one more condition is if vendor type is not EDI, then the POs should send through fax, email, how can we solve this condition.
So plaese send some sample code on this object.
Thanks in advance,
S Reddy

Hi ,
You can send the purchase order to the vendors using different outytpes configurations in NACE transaction .
If you define a particular output type where you need to give medium 6 and define partner functions within this you can also set condition which partner needs to recieve EDI output and which one FAX or email all this will be done by Functional expert.
For adding extra segments to your basic type ORDERS05 you need to extend the idoc you can do it via WE30 and WE31 .Link you message type to basic type and extension . Please follow below tcodes for further help . Create all the requested steps in the tcodes mentioned below.
we20:patner profile
we21:port
we30:idoc creation
we30:segment creation
we81:message type
we82:link message with idoc type.
we02:to status of idocs.
Now you need to write code for filling those extra segments you have added to you extension type. For that you need to check where your new segment is placed in Idoc structure . There will be a exit avaliable to attach your code to fill those segments .
Please go through previous SDN links to see more info.
One the settings are done in the NACE , issue output from PO transction and once your output is processed check your Idoc in WE02 to see if the segments are coming with the desired data.
Regards
Vikas

Vendor replication from SAP 4.6C to SRM 4.0

Hello all,
I hope you can help me with the following issue.
I'm having an issue with replicating vendors with Russian cyrillic characters from SAP R/3 4.6C into SRM 4.0
The vendor cyrillic characters are scrumbled when I view the vendor in SRM via transaction BUP3
I have done some analyses and I have found the following.
When I login with language RU (Russian) in SAP R/3 and create the vendor in cyrillic then the cyrillic characters are correctly replicated to SRM 4.0 when I run transaction BBPGETVD
The issue is that when the vendor is set up in cyrillic in R/3 using logon language EN (English) then the cyrillic characters don't get correctly replicated into SRM.
I have tried to login in R/3 with language RU and then to reenter the vendor name in cyrillic and then to replicate the vendor via BBPUPDVD. This did not work as the characters still show scrumbled in SRM.
I think the issue is that even the vendors were initially created in cyrillic in R/3 but because the logon language was EN the English code page got updated. I have tried to update the vendor in cyrillic by login with language RU in SAP but I still get the vendors not correctly in SRM. I think this is because the characters are stuck in english code page.
Has anyone experienced this before and how was this resolved?
Kind regards

Anyway I think you have to create your transport request in 4.6.
Go through AL11 and you can see directories of SAP SYSTEM
ABAP transport files are in trans/cofiles and trans/data. Cofiles and data file must be copied in the same directories on ECC 6.
Go in the stms on ECC 6. In the stms, Throughout the list, you should find your request. You must go into Requests->Import and it's finished.
Pay attention that what are you transporting is free of incompatibility with ecc 6 (call standard function non present in ecc 6, standard tables, or something like that,etc..)
Hope to help

Idoc status 51 while loading from R/3 to PSA

hi experts,
I am loading from R/3 to BW (fiar data), the request is in yellow status and running for long time and showing zero(0) records.
i have checked that some of the idocs are not posted.
when i try to push through BD87 still the status is showing 51 only.
can you plz giv solution for this.
regards
venuscm

Hi,
Maybe this is due to bugs in the TRFC programs that are solved with the
attached notes:
1280898,,IDoc hangs when it is to be sent immediately with
1338739 RFC calls in the wrong system
1377863 max no of gateways exceeded
Also please refer to the following note for additional info:
1250813 SAPLARFC uses all dialog work processes
1403974 Determining the maximum connections in transactione error
I hope it helps you.
Regards,
Fran.

Tracking Idoc status in target system from XI

Hi
We have done File to IDOC Scenario succesfully i.e HR
data from file has been mapped to HR Idoc(HRMD_A06) .
Now when Idoc is posted to R/3 , SXMB_MONI shows
successful status(Idoc posted successfully) .
But when we check in R/3 in WE05 transaction ,though
the idoc is present but it shows status 51/52
with message "Idoc could not be posted" /"IDOC not
fully posted" .
In this case how can we track in XI whether the Idoc
is properly posted in the target system(i.e R/3) .
Since XI only shows that Idoc was successfully sent
irrespective of the status in R/3 .
Please suggest as we are new to XI .
Regards,
Shikha

Hi
Thanks for the guide.
we are not sure of the steps to configure it in R/3
system so that it sends the acknowledgement back to XI
system.
When we tried to configure it as per the guide , for
test purposes we executed the program RBDSTATE but it
gave message "No parties are interested in the selected
data" .
Please guide us on this .
Thanks
Shikha
Message was edited by: Shikha Jain

Material Master Replication From SAP R/3 to SRM

Hi Gurus
For the testing, I maintain a Job for the program SMOF_DOWNLOAD on daily basis in SRM system and I created the 5 material Masters in R/3. I am facing two issues.
1. The Material Master are replicated immediately, its not working as per the job Scheduled ( I Scheduled the job on every day night at 24:00:00).
2. I am able to see the R/3 Material Masters in SRM system in tcode COMMPR01, but I am unable to use the Product IDs in SC creation, I am receiving the error message as "Product 1000056822 does not exist in plant 1560 or it has been flagged for deletion (Item Test SAP R/3 to EBOP )".
My material master is relevant to plant 1500, I change the plant 1500 in SC basic data, but the error is not disappearing.
Please suggest me.
Thanks in advance
Thanks & Regards
Sada

HI,
Check if the plant is defined in the PPOMA_BBP org structure.
If you have not defined the org elements in the extended attributes tab then the system will not know in which plant the material is been created.
Thanks & Regards,
Kiran

Employee replication from HR

Hi
When i am trying replicate the HR Employees to CRM, i am getting an error stating that
"Grouping 20 has external number assignment, enter a number"
If i am maintaining the internal number range, employees are getting created.
But i want to keep the same number range between HR and CRM for employees.
I have done all the settings required for replicating the HR Organization and Employees to CRM
Can someone please help me in this regard.
Thanks and regards,
Karunakar.

Issue got resolved. We maintained the number range as external for that we need to maintain value 3 in HRALX PNUMB.
regards,
KK

IDOC Status, Tracking in SAP PI/PO Single Stack

Hi All,
My PO version: 7.4, SP4. I am not sure my questions below are still a limitation in current PI/PO single stack systems, and hence requesting your help for the same.
1) Is there a way we can track outbound idocs in SAP PI/PO single stack similar to PI abap stack IDX5? ( Note:- I couldn't find any option in IDOC monitoring in single stack SAP PO 7.4, SP4)
2) IDOC status is always 0 in SAP PO 7.4 single stack IDOC monitoring. I am not sure if this status is just specific to my PO system. Any setting needs to be applied?
ps: Please post only relevant answers/solutions
Thanks,
Praveen Gujjeti
Message was edited by: Praveen Gujjeti

Hi All,
As per SAP help: Comparison of IDoc Adapter (IE) and IDoc Adapter (AAE) - SAP NetWeaver PI Reference Documentation - SAP Library idoc status and tracking not supported in current PO versions. May be SAP will add this feature in upcoming PO versions
Auditing, Monitoring ,and Tracing Functions
Attribute/Feature
IDoc Adapter (IE)
IDoc Adapter (AAE)
ALE Audit
Supported
Supported
IDoc tracing
Supported (transaction IDX5)
Not supported
IDoc monitoring
Transaction IDX5
Integration with channel monitor and message monitor (as part of Advanced Adapter Engine monitor)
Status tracking -SYSTAT
(analysis and further processing of messages that have not been processed)
Not supported
Not supported
RFC monitoring
Supported
Not supported
Message persistence in the IDoc adapter
Supported
Message correlation information can be stored in IDoc adapter.
Not supported.
Message is persisted in messaging system with correlation data persisted in adapter.
Regards,
Praveen Gujjeti

Sales Order iDoc from SAP SCM 7.0

Hi Experts
I have two question fro you guys.
1. Can we generate VMI sales order idoc from SAP SCM 7.0? I know is can generate xml message. If we can generate idoc for VMI sales order from SAP SCM , please give me some direction or path to explore.
2. Can I use idoc to to create to VMI sales order in ECC skiping CIF. But the changes in ECC to these order should use the CIF to update the VMI orders in SAP SCM.
Please share your experience on this.

Hi,
Did you set up this scenario? I want something similar, but I want an ERP order to be created. Do you know if that is possible? Do you have som tips?
regards Camilla

Warnings while receiving IDOC from SAP

Hi All,
I am running BTS 2010. I configured recieve location to recieve ORDERS05 Idocs. But I am receiving below mentioned warning.
1) In SAP the Idoc shows as successfully sent
2) On the BizTalk side we cannot find the Idoc anywhere
3) In the EventLog of our BTS we get the following errors (the errors are raised exactly at the same time when the Idoc which “disappears” is sent from SAP to BizTalk )
Error 1:
Event Type: Warning
Event Source: BizTalk Server 2010
Event Category: (1)
Event ID: 5740
Date: 1/10/2014
Time: 12:38:59
User: N/A
The adapter "WCF-Custom" raised an error message. Details "Microsoft.ServiceModel.Channels.Common.XmlReaderGenerationException: The segment or group definition E1234 was not found in the IDoc metadata. The UniqueId
of the IDoc type is: IDOCTYP/3/ORDERS05//700. For Receive operations, the SAP adapter does not support unreleased segments.
   at Microsoft.Adapters.SAP.TypedIdocBodyWriter.OnWriteBodyContents(XmlDictionaryWriter writer)
   at System.ServiceModel.Channels.BodyWriter.WriteBodyContents(XmlDictionaryWriter writer)
   at System.ServiceModel.Channels.BodyWriterMessage.OnWriteBodyContents(XmlDictionaryWriter writer)
   at System.ServiceModel.Channels.Message.WriteBodyContents(XmlDictionaryWriter writer)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfMarshaller.CreateBizTalkMessageStream(Message wcfMessage, IAdapterConfigInboundMessageMarshalling config)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfMarshaller.CreateBizTalkMessage(IBaseMessageFactory messageFactory, IAdapterConfigInboundMessageMarshalling marshallingConfig, Message wcfMessage)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfMarshaller.CreateBizTalkSubmitMessage(IBaseMessageFactory factory, String inboundTransportLocation, String inboundTransportType, RLConfig config, Message wcfMessage,
String ssoToken)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkSubmitBase..ctor(Message message, BizTalkEndpointContext endpointContext, ControlledTermination control, AsyncCallback realCallback, String ssoToken)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkSubmit..ctor(Message message, AsyncCallback callback, Object state, BizTalkEndpointContext endpointContext, String ssoToken, ControlledTermination control)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkOperation.Create(Message message, AsyncCallback callback, Object state, String ssoToken, Boolean bizTalkOneWay, BizTalkEndpointContext endpointContext, ControlledTermination
control)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkServiceInstance.BeginOperation(Message message, AsyncCallback callback, Object state, Boolean bizTalkOneWay)".
Error 2:
Event Type: Warning
Event Source: BizTalk Server 2010
Event Category: (1)
Event ID: 5740
Date: 1/10/2014
Time: 12:38:59
User: N/A
The adapter "WCF-Custom" raised an error message. Details "Microsoft.Adapters.SAP.RFCException: Details: ErrorCode=RFC_INVALID_HANDLE. AdapterErrorMessage=An exception has occurred on the listener while executing
RfcWaitForRequest..
   at Microsoft.ServiceModel.Channels.Common.Design.AdapterAsyncResult.End()
   at Microsoft.ServiceModel.Channels.Common.Channels.AdapterReplyChannel.EndTryReceiveRequest(IAsyncResult result, RequestContext& requestContext)
   at Microsoft.Adapters.Internal.LayeredChannelBindingElement.LayeredInboundChannel`1.System.ServiceModel.Channels.IReplyChannel.EndTryReceiveRequest(IAsyncResult result, RequestContext& context)
   at System.ServiceModel.Dispatcher.ReplyChannelBinder.EndTryReceive(IAsyncResult result, RequestContext& requestContext)
   at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.EndTryReceive(IAsyncResult result, RequestContext& requestContext)".
Error 3:
Event Type: Warning
Event Source: BizTalk Server 2010
Event Category: (1)
Event ID: 5740
Date: 1/10/2014
Time: 12:38:59
User: N/A
The adapter "WCF-Custom" raised an error message. Details "The WCF service host at address sap://CLIENT=100;LANG=;@a/SAPD.corp.int/10?ListenerDest=BIZTALKD&ListenerGwServ=sapgw10&ListenerGwHost=SAPD.corp.int&ListenerProgramId=BIZTALKD&RfcSdkTrace=False&AbapDebug=False
has faulted and as a result no more messages can be received on the corresponding receive location. To fix the issue, BizTalk Server will automatically attempt to restart the service host.".
Error 4:
Event Type: Warning
Event Source: BizTalk Server 2010
Event Category: (1)
Event ID: 5740
Date: 1/10/2014
Time: 12:38:59
User: N/A
The adapter "WCF-Custom" raised an error message. Details "System.ServiceModel.CommunicationObjectFaultedException: The communication object, Microsoft.Adapters.Internal.LayeredChannelBindingElement.LayeredInboundChannel`1[System.ServiceModel.Channels.IReplyChannel],
cannot be used for communication because it is in the Faulted state.
   at System.ServiceModel.Channels.CommunicationObject.Close(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Close()
at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.Close()".
http://social.msdn.microsoft.com/Forums/en-US/57a18e78-d902-4a39-a99f-95ef732792f7/adapter-pack-20-sap-adapter-problem
As per the replies in the above link i made the changes but still warning continues.
Please suggest
Thanks,

The IDOC has not arrived in BizTalk, that's why you do not see it. The problem is that the IDOC fails at adapter level, when the SAP RFC Library is called.
The actual problem is that the IDOC you are receiving is containing unreleased segments and that's not supported, you should contact your SAP administrator to get this problem resolved.
If I'm not mistaken it's transaction WE30 in SAP, there you have to select the IDOC type (ORDERS05 in your case) and then you can set the release. But your SAP administrator will probably know better how to do this
Glenn Colpaert - MCTS BizTalk Server - Blog : http://blog.codit.eu

IDoc status 53 in employee replication from SAP HR

Similar Messages

Maybe you are looking for