on 02-13-2013 9:56 PM
Hi Guru's,
We have established the connection between SAP R/3 and SAP PI (7.11) (first time established the connection) using all the steps (like creating RFC connections,ports,partner profile setup in R/3 in PI creating RFC connection, maintaining IDX1,imported meata data in IDX2,). all looks good.
But I am failing at the first step.
I have created the IDOC and triggered in to port through we19 and the status is showing as 03.
But I am unable to see the messae anywhere. I have tried to check that in SXMB_MONI, SM58 Etc.. I am not able to findout what is the exact issue.
Can you pls direct me how to analyse or where is the starting point to check.
Appreciate your quick help.
Thanks
Arun
Hi Arun,
You can compare your configuration details with Article.
Sreeni.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Did you created the Business system for the ECC in SLD of PI ?
if no create technical system, logical system and business system in SLD for ECC..
Search SDN or help if you require more info..
HTH
Rajesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
If you cannot see anything at all on PI-side, I would definitely verify with TA SM58 on the R/3-side. Please make sure to leave the field with the "username" blank when you go to SM58 to see all IDocs that have been created.
Kind Regards
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
idoc should be there in SM58(ECC) or IDX5(PI) or check SM21(in PI for any kind of error), if it is showing WE05(green).
But still it is not showing there, just check rfc pointing to correct PI system, may be idoc going some where else instead of PI box you are checking. check RWB messages also if something in error there.
ROhan,
Just a quick question. We have 2 R/3 systems which are connceting with same PI system. the RFC connection names which are created in both R/3 systems are same. Is that a problem.
Also I have checked in SM21 on PI system, it is showing some error related to communication used which is created in R/3. See the log below.
Transaction Canceled IDOC_ADAPTER 601 ( SAPWSD 400 )
Documentation for system log message D0 1 :
The transaction has been terminated. This may be caused by a
termination message from the application (MESSAGE Axxx) or by an
error detected by the SAP System due to which it makes no sense to
proceed with the transaction. The actual reason for the termination
is indicated by the T100 message and the parameters.
Additional documentation for message IDOC_ADAPTER 601
No service for system &1, client &2 in Integration Directory
&CAUSE&
Unable to determine the service for system &1, client &2.
&SYSTEM_RESPONSE&
You tried to determine a service for system &1, client &2.
The system ID is taken from the sender port of the IDoc control record,
which must have the form 'SAP' + system ID. In the case of external
systems, in the sender port field you must enter the logical system
that is assigned to the service in the Integration Directory.
&WHAT_TO_DO&
Maintain a service in the Integration Directory for system &1,
client &2.
&SYS_ADMIN&
Contact your system administrator.
Can you pls suggest some by seeing this?
Thanks
Arun
Just go to you ECC business system/business component you have created in ID.
go to menu, then go to communication component, then go to Adapter specific identifiers, then enter or correct Logical System Name, R/3 System ID, Client in popup box.
Above will fix your issue, then re-try sending Idoc from We19 from ECC to PI.
Hi ,
Please go through the below link for steps to create SLD part (for your ref).
http://sapxitutorials.blogspot.in/2008/12/sap-xi-tutorials-sap-xi-resources-and_1631.html
Regards
Venkat
User | Count |
---|---|
92 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.