Error in target system : iDOC -XI-iDOC

We are getting this error in smq2 when we are processing bulk idocs thru XI "Error in target system " . The setting on receiving system is trigger by background program .
Manish

Hi Manish,
If so, can you control the number of idocs sending to XI box. This is workaround
Is this may be because of number of work process . I am not sure here. So you can increase the work process.
But you can seek help from SAP to audit on this provided if you are able to reproduce the error..
This is just my views~
Regards,
moorthy

Similar Messages

Error in target system !!!

Hello,
I have the same error in Dev, Quality and production (wich are in different machines) with XI 2.0 To R/3 4.7, we send tRFC to IDOC and all messages are " error in target system" in sm58
in sxmb_moni, for a message, the first flag is OK, the second flag (A. Status) is red.
When we check the RFC Connection in sm59, it's sometimes good, sometimes not, we think it's a network problem (maybe with firewall...)
have someone any idea please ?
Cedric Rousseau

Hi Manish,
If so, can you control the number of idocs sending to XI box. This is workaround
Is this may be because of number of work process . I am not sure here. So you can increase the work process.
But you can seek help from SAP to audit on this provided if you are able to reproduce the error..
This is just my views~
Regards,
moorthy

CHARM error - No Target system for Normal transport generated from another client

Hi Gurus,
This is regarding normal change. We have two clients in development. (Workbench and Customizing)
We were trying to do Automatic import from development client to Quality. When importing the job, I’m getting an error related to Project Status switch. "you cannot import any request for the project at the moment" It works fine for another development client and we can see the target system in Project status switch.
But, checking the Project Status switch, looks like there’s no Target System defined for Normal transport generated from another client of development.
I attached some screenshots related to this.
Can you please help how to add a target system for another client of development ?
Regards,
Salman

yes, client 110 is present in the task list of the project. yes route is defined because it is working for urgent change

Inbound Proxy Error in Target System

Hi
My scenario ís MQ>XI>SAp R/3. I am successfully able to pick file from MQ and I see the success flag in SXMB_MONI(XI) and XI sends to SAP R/3 via Inbound proxy.
But on recieving system (R/3) via proxy the data is not recieved correctly.
I see Failure message with error in R/3 SXMB_MONI and the error is as follows.
I guess my Mapping is correct as it passes trhough XI successfully. Is something wrong with the Inbound proxy?
Kindly let me know your views on the same going through the error message I am unable to interpret anything. As the date format which I am recieving is correct.
++
Best Regards
Swetank

Hi,
When u define ur Data type (Messageinterface) dataelement as xsd:Date it is of the format CCYY-MM-DD. (ex 2003-12-31). So yyyyMMdd is not compatable with the ABAP data type that has been generated at the proxy end.
Make sure dats-8 and xsd:Date use the same Date format.This might be the error that i can see.
xsd:date format
http://help.sap.com/saphelp_nw04/helpdata/en/fe/26da4105aa3f5de10000000a1550b0/content.htm
Hope this helps
Cheers,
Siva Maranani.

Workflow Event Trace:RFC Status : Error in target syst

Hi Gurus,
I am working on a custom workflow which is called in a loop from a transaction. There is a transaction which creates multiple documents. We need to start the workflow for each of them. This works fine for around 80-85 documents. For the remaining documents workflow does not start. I am trying with 200 documents.For the remaining documents event is triggered and in event trace, i see the information that receiver started correctly.But in RFC Status it displays as 'Error in Target System'. This is definitely due to system overload. Is there something that can be done for the same. Is this number configured somewhere like how many workflows can work in parallel.

Hello,
How do you know it's due to system overload?
200 workflows should be okay, but how quickly are they created? If it's all done within one second then yes, there could be a problem. You could stretch it out programmatically or you could use the queue, as Sue suggests.
regards
Rick Bakker
hanabi technology

** File to IDoc scenario - IDoc not created in target system

Hi friends,
We are doing File to IDoc scenario. We made required setting in both application as well as XI system. While test the scenario, the file is picked up and successfully processed in SXMB_MONI, but the inbound IDoc is not created in target system. What could be the problem?
We are using DEBMAS message type DEBMAS06 IDoc type. We checked the following.
1) SM59 - Connections are OK both application and XI system
2) IDX1 - In XI System, we have assigned SAP<R/3> port.
3) IDX2 - IDoc is imported.
4) In ID - Sender File - Business Service - Adapter-Specific Identifier - Logical System name is given.
5) In application system. - Partner Profile maintained correctly.
6) SM58 - There is no error.
So, what could be the reason ?
Kindly reply, friends,
Thanking you.
Kind Regards,
Jeg P.

Hi,
Check all the steps ..
File to IDOC
Do these configurations in R/3 and in XI...
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
Thanks,
Satya

Error in Message Mapping "Target message IDOC: ORDRSP.ORDERS02 does not exi

Hi,
I have joined newly to the team.
When I tried to open one message mapping it throwinf follwing error...
"Target message IDOC: ORDRSP.ORDERS02 does not exist in software component version ID: 44423362454456485465..
Check whether the software component version ID: 44423362454456485465 is in Enterprise Service Repository. Import this version if necessary"
Is there any impact because of which in the message flow?
In my case some of the messages are failing with mapping error "runtime exception occured during application mapping com/sap/xi/tf/_SUS2MMOrderResponse_; java.lang.NullPointerException: while trying to invoke the method java.util.Map.get(java.lang.Object) of an object loaded from field com.sap.aii.map`"
And some of the messages are processed sucessfully and they also using the same mapping program 'SUS2MMOrderResponse'.
Could someone tell me is there any relation for the above error in XML messages and to the message mapping?
Regards
Baskaran K

Could someone tell me is there any relation for the above error in XML messages and to the message mapping?
The error mentions that you have used an IDOC in your mapping program which is not found in the ESR....you need to check if the IDOC is present in the ESR and is present under the correct SWCV.
Once you have done the check do some dummy change to the mapping and activate it (if in DEV) and then check the CACHE.

SAP Idocs -How to handle response from target system

Hi,
I am working on a scenario in which I will send Idocs asynchronously from SAP thro a SOAP adapter to a webservice deployed on the target system.
After the Idoc data is posted in the target system,the target system will send the acknowledgement for the receipt(basically response message).How to handle this scenario?
SAP Idoc( outbound asynchronous)---> SAP XI3.0(soap adapter) ---> Target system(inbound synchronous)
Do I need to go for BPM to handle this situation?
Is there any alterantive to BPM.
If any of the forum members who have worked on the similar scenario could help me in finding a better solution,I will be thankful to them.
Thanks,
Leo

Hi Udo,
Thanks for the info.My scenario is like this.
SAP R/3 Idoc -> SAP XI 3.0 <-> Webservice in the target system.
The webservice in the target system will receive the Idoc as a request messsage and send a response message synchronously.
Since Idoc is sent asynchronously( I believe Idocs sent from SAP are always asynchronous),there is no Proxy waiting in SAP R/3 to receive the response message from the target system.
If I go for BPM for the above scenario,will the BPM steps look like the following.
1)Receive Idoc from SAP.
2)Send Idoc sysnchronously to webservice
3)Receive the response from the webservice synchronously.
4.Post the response message to a proxy which can handle it further in SAP R/3.
Please note that my knowledge in BPM is limited and correct me if I am wrong.
Thanks in advance
S.Banukumar

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

How to know whether all Idocs sent perfectly or not to target System

Hi All,
We are sending the Material Master Idocs via XI and to WMS File system ( Idoc-XIFile)
How can a business user confirm that all the sent Idocs are reached to WMS by End of the day.
Is there any way to match or any report kind of thing for this please
Regards
Vamsi

HI vamsi,
Following is the solution that we are using >
1. There is a separate interface ( file to idoc )that runs at the end of the business day..
This interface will pick up a file ( from say ur WMS system) and post an idoc STATUS.SYSTAT01
the file in this case will have the idoc number of the material idoc and the status( say 11 for OK ) and the same will be mapped to idoc.
This idoc in turn will change the status of the material idoc from 03 to 11 . Then a filter can be made on this to find out which idocs did not reach status 11..
however here there are chances that this ack interface can go in error as well
2. Or u can have a separate interface ( file to Proxy ) ..here the difference would be that single file will have all the idoc numbers that were received during that day and then in the proxy u can write abap code to change the status of those idocs to say status OK
Edited by: Tarang Shah on Feb 6, 2010 8:05 PM
Edited by: Tarang Shah on Feb 6, 2010 8:06 PM
Edited by: Tarang Shah on Feb 6, 2010 8:14 PM

SAP system IDOC - XI - SAP system IDOC

Hi,
I have created several scenarios for sending IDOCs between different SAP systems, but I have a problem with just one SAP system that is a copy of our production system when is acting as a source.
When sending the IDOC from source system, I can see the IDOC in SM58, with the following error message;
"client xxx is not available in this system" where the client is actually the client of the receiving system.
I have successfully sent IDOCs from other SAP systems to the same target SAP system so there is nothing wrong with the target system.
Anyone experienced the same? Any ideas?
best regards
Torstein

Hi,
I am facing the same issue too. My target system is also release 700 and I have done all my SALE config, we21 settings. But still the error repeats as " Client XXX is not available in the system". How did you fix this issue?
-Teresa

You are not authorized to logon to the target system error code1(in SM58)

Hi Basis Gurus,
In my test system Idocs are in error status.
When I check tRFC monitering in SM58, there are several Idocs are strucked.
Status Text: You are not authorized to logon to the target system (error code 1).
Recently we have refreshed our test system with production data.
Before system refresh it was normal.
The RFC connection is also working fine.
Please suggest the solution as I'm struck in this issue.
I'm a Basis Guy.
Thanks & Regards,
Ravi.

Hi,
Change the RFC user password in target system however there are 2 tests to analyse from SM59 :
1) RFC Connection test
2) Authorization Test
And i guess you have only tested the 1st one from the RFC(SM59) check whether you can succeed with option 2 if not then you may need to change the password.
Thanks,
Salim

Error while testing Inbound Idoc

The error message "Interface for function Z***** is incorrect*." is shown while trying to test an incoming IDOC in we19.
PL HELP!!!!!!!
The procedure followed by me was,
WE31 created custom segments,
WE30 Created custom basic type,
we81 Custom message type,
se37 function module,
we82,
we57,
bd51,
we42,
bd67,
we20,
Am not able to figure out why exactly is the error message being shown.
please tell me if a step was missed or what the possible error is, I think the parameters of function module are correct....

Hi friend,
if it is help full please give max reward point.
Standard program, RBDMOIND is scheduled or executed online to determine whether the communication was successful. If IDoc is Dispatched to destination system, RBDMOIND updates the status of the IDoc to 12 (Dispatched OK), Otherwise remains in status 03.
Two programs enable cross-system reporting:
     RBDSTATE: It reports the status of the incoming IDocs to sending system, using ALEAUD message and ALEAUD01 IDoc
     RBDAUD01: It executed on sending system to analysis the audit log and display the output as a report
IDoc Status in Receiving System          IDoc status in Sending System via ALEAUD
53 Application docu posted     =>     41 Application docu created in receiving sys
51 Error: Application docu      =>     39 IDoc in receiving sys. Status repeated
     not posted                         each time RBDSTATE runs.
68 Error: No further processing     =>     40 Application docu not created
ALE Auditing
BDM7          =>     ALE Audit: Statistical Analysis
BDM8          =>     ALE Audit: Sending the Confirmations
RBDSTATE     =>     Run on Receiving System to return Audit Message

Idocs are unable to transfer from R3 to PI system, IDOC status is 03

Hello Gurus,
Idocs are unable to transfer from R3 to PI system, IDOC status is 03
in sm58 getting below error
RFC are working fine
"EDISDEF: Port SAPCEP segment defn Z2SH_DESCR000 in IDoc type MATMAS03 CIM"
Regrds
vamsi

Hi,
I am also facing same problem, Can any one suggest me what is the issue..

BI Idoc Type IS NOT THE SAME AS SOURCE SYSTEM IDOC TYPE

Hi all,
how can we solve the IDoc miss match in source system (ECC6).
Error :
BI Idoc Type ZSTC029 IS NOT THE SAME AS SOURCE SYSTEM IDOC TYPE ZSTC031
please provide me solutions..
Thanks in advance,
Venkatesh

Hi Venkatesh,
Check here.........
BW idoc type not same as source system idoc type
Thanks,
Vijay.

Error in target system : iDOC -XI-iDOC

Similar Messages

Maybe you are looking for