ECC Via XI to Third Party system through Idocs

[Former Member]

Hello,

I have done all the setting required to IDOC communication,

RFC's are created,

Distribution Model

Imported the Meta data

Partner Profile

ESR Objects Made (IDoc as my Source and WSDL as External Definition for Target)

ID Configuration made, sender channel is SOAP.

SLD Configuration (Business and technical system as third party systems and ECC as ABAP system)

Sender is ECC, no sender channel will be required (correct me if i am wrong), where as

now when i test my scenario with WE19, i do not see my XML while using tcode sxi_monitor.

have i missed any step.

Any help will be appreciated,

Regards,

Abhishek

[former_member184681 · Accepted solution]

Hi Abhishek,

First of all, just to make sure: you are checking sxi_monitor in PI, not in ECC, aren't you? If yes, then perform following steps to diagnose the source of your problem:

1. Check your IDoc in ECC in we02 or similar - are there no errors in processing (like: partner profile found correctly, passed to port and so on)?

2. Check sm58 for tRFC connection errors. Only after checking this can you be sure that the IDoc with green traffic light in we02 has really been delivered to PI correctly. You can also schedule an ABAP report to change IDoc status correspondingly.

3. If no errors found in sm58, your IDoc should actually be received by PI, but still there are some possibilities when it is not visible in sxi_monitor: in case of a synchronous scenario or when using AAE (in PI 7.3 for IDocs).

And yes you are right, sender agreement is not mandatory for sender IDoc scenarios.

Hope this helps,

Greg

[Former Member · Accepted solution]

Hello,

Thank you all for your replies,

my idoc's are

in IDX5 i get an error in the status, "* System is not a Central Integration System: unable to start program*"

In SM58

I get an error,"* Name or password is incorrect (Repeat Logon)*"

How do i resolve both my errors.

Regards,

Abhishek

[Former Member · Accepted solution]

System is not a central XI;cannot start program" Err

.........................................................................................................................

In SM58

I get an error," Name or password is incorrect (Repeat Logon)"

Check the transaction: SM59. For the given RFC Destination (it will be one under ABAP Connections or R/3 Connections - with Connection Type 3) under the "Logon & Security" tab page we need to maintain the user name and pass word. Check if they are correct.

Click on the button "Remote Logon" in the Application tool bar, you should be able to get into your target system. If not we have to correct this.

This is the problem with transaction SM59 - Maintaining RFC Connection.

[Former Member · Accepted solution]

Hello,

I am able to logon using remote logon, in sm59 and my test is throws no error.

Regards,

Abhishek

[Former Member · Accepted solution]

check Question 11 in below thread:

http://wiki.sdn.sap.com/wiki/display/NWTech/QAforPI-Onestopforall(Part-1)

[former_member184681]

Hi Abhishek,

Are you sure that there are no errors in sm58 for your messages? In the thread history I can see that you've done some investigation there, but the verification method suggested by bhavanisankar.solasu does not really seem adequate. It is not the "Remote Logon" option to be chosen in sm59, as it allows you to provide logon credentials during the test. Instead, use the "Connection Test" button, as it uses the logon credentials from the "Logon & Security" tab page. Moreover, perform the Unicode Test and make sure settings in "MDMP & Unicode" tab page are correct.

Hope this helps,

Greg

[former_member184681]

Hi,

Please see this thread for a solution for this problem:

Setting the role of your business system as Integration Server should fix the whole thing.

Hope this helps,

Greg

[Former Member]

Hello,

Steps I followed:

Created RFC destination for PI in ECC (Connection test successful) ABCLNT001

Similarly created RFC destination in PI for ECC (Connection test successful) XYZCLNT200

Created Ports in the both the systems (WE21). generated the system ports

Imported Metadata using IDX1 and IDX2 (MATMAS05)

Maintained The distribution Model (BD64)

Maintained Partner Profile (We20) I guess this incorrect. kindly shed some light on this

Using the RFC Destination made earlier, what should be my Logical System in ECC for PI.

SO when i test my IDoc FM, the status is 03,

But in SXI_MONITOR not able to view my XML (No message found)

Check sm58 no error's

Regards,

Abhishek

[Former Member]

Using the RFC Destination made earlier, what should be my Logical System in ECC for PI.

please refer below thraed and check r u created all required steps / not?

[idoc|http://www.saptechnical.com/Tutorials/XI/IDocToFile/IDocToFile1.htm]

[Former Member]

Hello,

I have all the followed all the steps mentioned on the document.

My Idoc in WE02 status 03

No Error in SM58

IDX2 Metadata imported

All the configuration objects designed on ESR and ID and channel is activate

Scenario IDOC to PI to SOAP Message.(URL maintained)

Not able to see in any message in SXI_MONITOR, nor in the communication channel.

any help will be appreciated hugely

Regards,

Abhishek

[Former Member]

Hope you are checking sxi_monitor in XI?

[Former Member]

Hello,

Yes, i am checking SXI_MONITOR is SAP PI .

Regards,

Abhishek

[Former Member]

hi Abishek,

Not able to see in any message in SXI_MONITOR, nor in the communication channel.

you have to check Stauts in SXMB_MONI on pi stack,

if there is no message , once you have to check INBOUND Queue on pi stack by using t.c SMQ2.

[Former Member]

Hello,

Check the status in sxmb_moni, please explain in detail.

also the inbound queue show nothing empty

How do i configure IDX5 tcode

Regards,

Abhishek

[Former Member]

Check the status in sxmb_moni, please explain in detail.

also the inbound queue show nothing empty

How do i configure IDX5 tcode

first you check status in SXMB_MONI :

SXMB_MONI ->double click on "Monitor for Processed XML Messages " and

enter ur inbound and outbound service interface names in related fields and check the status.

How do i configure IDX5 tcode

just execute t.c idx5

[Former Member]

Hello,

Whether i execute sxmb_moni and specify the interface name or sxi_monitor, it guess its the same.

I get an error when i execute idx5

Regards,

Abhishek

[Former Member]

hi ,

Whether i execute sxmb_moni and specify the interface name or sxi_monitor, it guess its the same.

ya same and can u Elaborate what is the issue whenever u execute the t.c IDX5 ( i get an error when i execute idx5

and can i know that what kind of idoc are you used like standard/custom?

[Former Member]

Hello,

My scenario,

IDOC to SOAP (SAP to Non-SAP system)

Using custom Idoc to sent PR and Line Item Details.

Imported Metadata in IDX2 also imported IDoc in the ESR

Using the WSDL, have done the Message Mapping in ESB.

Using Configuration wizard, generated the Configuration Objects, Communication channel and other objects.

Distribution Model created,

IDoc in status 03 ECC

sxi_monitor no message visible.

in IDX5 System is not a Central Integration System: unable to start program is the error, if i fix this error what will be impacts on the system

Regards,

Abhishek

Edited by: Abhishek Biwal on Jan 23, 2012 5:24 PM

[Former Member]

in IDX5 System is not a Central Integration System: unable to start program is the error, if i fix this error what will be impacts on the system

please follw bwlow step:

Check SXMB_ADM --> Check the Integration Engine Configuration

In the Global Configuration Data :

Role of Business System should be Integration server

Corresponding IS should point to Pipeline URL.

please check below link

and

Transaction SAP Adapter u2013 Monitoring (IDX5) : provides you with an overview of all messages sent to or from the Integration Server as IDocs. Double-clicking a message provides you with detailed information on this message in the Integration Server.

You can monitor the status of all XML messages by using transaction Integration Engine u2013 Monitoring (SXMB_MONI).

You can use transaction SM58 to monitor native RFC communication on the Integration Server. This type of communication protocol is used in two places here:

To send an IDoc from an SAP system to the Integration Server

To send an IDoc from the Integration Server to an SAP system

and one more thing are you tested Rfc destination ? is it working ?

[Former Member]

Hello,

Yes, i have tested my RFC connections and they are successful.

What i'll do is try to make all the ESR and ID objects again.

Regarding, making the configurations for IDX5, this is an existing live system, what will the impact on the system, will any services get affected or not.

Regards,

Abhishek

[Former Member]

What i'll do is try to make all the ESR and ID objects again.

that is not a problem with ESR and ID objects .if you want to make again , delete all objects and activated then start again , imported objects also (IDOC)

Regarding, making the configurations for IDX5, this is an existing live system, what will the impact on the system, will any services get affected or not.

u ll make the configuration of IDX5, not affected to any systeem any how u ll make the changes with basis people

[Former Member]

Hello,

I have made the objects again, but to no avail, still not able to view the message in SXI_MONITOR or SXMB_MONI

Regarding IDX5, i'll be doing the configuration settings, we do not have a basis guy, no a bit skeptical to carry out the same.

Regards,

Abhishek

[Former Member]

i'll be doing the configuration settings, we do not have a basis guy, no a bit skeptical to carry out the same.

u ll configure the same whatever I posted earlier.

[Former Member]

Please refer bellow steps:

First you need to check status of idoc by using t.c we05/we02 on R3 Sys

If status is Success(03) , you need to check RFC Monitoring by using t.c SM58 on R3 Sys

If there is no issue in Sm58,you need to check Inbound QUEUE by using t.c SMQ2 ON PI Sys.

please refer below blog and it's very helpful for ur issue:

[blog|]

[Former Member]

Hi,

Please check in ECC about the Idoc status in we02, if it is green, go to sm58 in ECC, if it is there(stuck in t-rfc(SM58)), reprocess it. if it is not stuck in t-rfc(SM58) then go to PI system and check it into IDX5, u will get it there.

Regards,

Chandra