Integration Directory configurations for IDOC -> X...

Hi all,

I have a scenario as above: IDOC-XI-FILE

The IDOCs come from an R/3 system - NHGDDBS01.

I've configured 2 BS:

1) BS_NHGDDBS01

-> TS: NHGDDBS01, type: WebAS ABAP

-> SWCV: BASIS 6.20

2) BS_DEV1_NAUTICUS_OOTS

-> TS: TS_DEV1_NAUTICUS_OOTS, type:Third Party.

-> SWCV: SWCV_DEV1_NAUTICUS_OOTS, type: Third Party

-> PDT: PDT_NAUTICUS_OOTS

With this setup, can someone help me by showing me how to configure the Integration Directory in order to receive IDoc from R/3 (nhgddbs01)?

Please help.

Thanks.

Ron

SAP Managed Tags:
SAP Process Integration

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (5)

Dear All,

For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.

For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.

I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.

Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Check this out

<a href="https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&">SAPR/3 to IdocsToXI</a>

Message was edited by:

Himadri Chakraborty

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi chong i wil give all the scenario's basic steps Doc.Please go through this. u wil feel easy to understand.Give me ur mail id so that i can send i t to u.

regards

babu

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

> Hi chong i wil give all the scenario's basic steps

> Doc.Please go through this. u wil feel easy to

> understand.Give me ur mail id so that i can send i t

> to u.

> regards

> babu

Babu, please send the documents to laiwc@sg.fujitsu.com

Thanks.

Ron

HI,

See the below links to get IDoc to File.

/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File

IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario

idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping

IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process

/people/sravya.talanki2/blog/2006/12/25/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-i

Idoc Adapter - https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6f...

Regards

Chilla

> HI,

> See the below links to get IDoc to File.

> https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/

> 1819 - IDoc to File

> IDOc testing -

> https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/

> 2923

> idoc mapping -

> https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/

> 3199

> IDoc erros troubleshooting -

> https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/

> 5212

> /people/sravya.talanki2/blog/2006/12/25/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-i

> Idoc Adapter -

> https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot

> /docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e09

> 8

> Regards

> Chilla

I did a quick check on SM58 on the R/3.

The error shown is: Transaction IDX1: Port SAPDV11, client 108, RFC destination contains error.

What does this error mean?

Please hep.

Thanks.

Ron

This is known issue.....Check the below steps.............

Go to XI system ->and IDX1 transaction.. And check the port number + RFC destination is given correctly. this should point to SAP system ..

Check thsi RFC destination is having all the entires and test connection success

And the port should have the naming convention SAP<System Id>.

........................Check this SAP Note -940313

> This is known issue.....Check the below

> steps.............

> Go to XI system ->and IDX1 transaction.. And check

> the port number + RFC destination is given correctly.

> this should point to SAP system ..

> Check thsi RFC destination is having all the entires

> and test connection success

> And the port should have the naming convention

> SAP<System Id>.

> ........................Check this SAP Note -940313

Hi,

I followed the SAP Note.

The SAP System ID is DV1.

I've configured IDX1 with the following port:

Port: SAPDV1

Client:108

Description: <blank>

RFC_Destination: PI_001 (This RFC destination points to DV1, despite the naming. Connection test is successful)

I recreated metadata on IDX2:

IDoc Types: ZPATINFO

Source Port: SAPDV1

IDoc Types: ZADMINFO

Source Port: SAPDV1

However, when I test the message from R/3 using WE17, SM58 on R/3 it's still showing the error:

Transaction IDX1: Port SAPDV1_108, client 108, RFC Destination error.

May I know where did this error occur and how to rectify this?

Please advise.

Thanks.

Ron

Hi,

Check this blog and make sure that you follow steps as mentioned in below blog:

<a href="/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters:///people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters

Regards,

Subhasha ranjan

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Create reciever and interface determination and also reciever agreement.....No need to create the sender agreement.

After activating the objects,test Your scenario with the help of IDOC test tool (WE19).

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

> Create reciever and interface determination and also

> reciever agreement.....No need to create the sender

> agreement.

> After activating the objects,test Your scenario with

> the help of IDOC test tool (WE19).

When defining the Receivier Determination, I need to specify the Service.

For my above-mentioned scenario, which service should I choose?

Please help.

Thanks.

Ron

When defining the Receivier Determination, I need to specify the Service.

For my above-mentioned scenario, which service should I choose?

Sender service ie the one which created for IDOC(BS_NHGDDBS01)

> When defining the Receivier Determination, I need

> to specify the Service.

> For my above-mentioned scenario, which service should

> I choose?

> Sender service ie the one which created for

> IDOC(BS_NHGDDBS01)

Thanks.

One more question - I defined my message mappings under SWVC_DEV1_NAUTICUS_OOTS.

How can I make this work?

Please help.

Thanks.

Ron

Give your Interface mapping name and Inbound Interface name(Message Inteface for File) in Interface determination step of ID.

> When defining the Receivier Determination, I need

> to specify the Service.

> For my above-mentioned scenario, which service should

> I choose?

> Sender service ie the one which created for

> IDOC(BS_NHGDDBS01)

Thanks.

One more question - I defined my message mappings under SWVC_DEV1_NAUTICUS_OOTS.

How can I make this work?

Please help.

Thanks.

Ron

One more question - I defined my message mappings under SWVC_DEV1_NAUTICUS_OOTS.

How can I make this work?

Give your Interface mapping name and Inbound Interface name(Message Inteface for File) in Interface determination step of ID.

> Give your Interface mapping name and Inbound

> Interface name(Message Inteface for File) in

> Interface determination step of ID.

Thanks for your help so far.

My current setup for Receiver Determination is:

Service: BS_NHGDDBS01

Interface: ZPATINFO_IDTY.ZPATINFO

Namespace: urn:sap-com:document:sap:idoc:messages

Configured Receivers:

Service: BS_DEV1_NAUTICUS_OOTS

Inbound Interface:

Name: MI_PatientDemographics_Inbound_Async_UpdatePatientDemographics

Namespace: urn:dev1:fapl:oots:PatientDemographics

Interface Mapping:

Name: IM_PatientDemographics_Async_UpdatePatientDemographics

Namespace: urn:dev1:fapl:oots:PatientDemographics

SoftwareComponent Version: SWCV_DEV1_NAUTICUS_OOTS , 1.0 of fapl

May I know if this configuration is correct?

Please help me understand because I'm new to IDocs scenario.

Thanks.

Ron

May I know if this configuration is correct?

Yes....create reciever agrement also...

> May I know if this configuration is correct?

> Yes....create reciever agrement also...

Yes I've created that.

Thanks.

I'll test it out and let you know the results.

Thanks.

Ron

> > May I know if this configuration is

> correct?

> > Yes....create reciever agrement also...

> Yes I've created that.

> Thanks.

> I'll test it out and let you know the results.

> Thanks.

> Ron

Hi all,

I'm Ron, Wee Chong Lai

I'm using another account because my account has been locked for some reason.

Anyway, I've tried the above configurations, however, when R/3 sends an IDOC, it shows successful status on R/3, but I do not see any messages in SXMB_MONI.

Why is that so?

Can I understand how does R/3 know which message interface in XI to send the IDoc to?

Please help.

Thanks.

Ron

Ask a Question

Top Q&A Solution Author

User

Count