Do we need have Distribution model in ECC for PI(JAVA Only Stack)

[former_member257758]

Hi Friends,

My scenarios is IDOC to File. We are using SAP PI 7.3 (Java Only Stack). I have gone through below forums to understand the connectivity setup for IDOC_AAE adpater.

http://scn.sap.com/people/william.li/blog/2011/05/04/configuring-pi-730-java-idoc-adapter

http://scn.sap.com/docs/DOC-31398

http://scn.sap.com/docs/DOC-34155

But I have question regarding the distribution model (BD64) in ECC side. Do we need maintain distribution model (for IDOC) in ECC when we are using IDOC_AAE adapter?

I know that we need to create the distribution model (for the corresponding logical system,IDOC type,Message Type) when we were using PI dual Stack.

But in single stack  we will to create RFC destination with connection type TCP/IP with program ID (which was created in PI already) in ECC. I think ECC and PI will communicate through this Program ID If I am correct.

Can anyone let me know whether we need to have distribution model created in ECC for PI Java only stack?or No?. IDOC to file scenario will work without distribution model in ECC?

Appreciate your help.

Thanks

Ar

[smavachee]

Basic difference in configuring the RFC destination in ECC for IDOC_AAE is to create TCP/IP connection. Traditionally we are not used to create TCP/IP for similar scnario.

For more details, refer links provided in earliesr replies.

Hope it helps.!

Regards,

Sunil

[former_member207622]

For IDoc communication , you will surely need a partner profile . IF you create partner profile and  run the scenario you will surely be able to to get successful posting

Now the question is you want to create partner profile via we20   or generate partner profile via BD 64

The best practice is to have distribution model in place in case of Idoc scenarios

distribution model is required when you communicate between SAP and Non SAP systems via ALE .

http://www.riyaz.net/sap/beginners-guide-to-ale-and-idocs-part-ii/19/

Have a look at the blog which has steps to be performed in ECC

[Former Member]

Hi Arun,

Distribution Model is not mandatory for IDOC_AAE to file using java stack.

Please refer the below link

https://scn.sap.com/thread/1979607

http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a610f507d11d18ee90000e8366fc2/frameset.htm

[MichalKrawczyk]

Hi,

>>>>Distribution Model is not mandatory for IDOC_AAE to file using java stack.

distribution model has nothing to do with IDOC adapter - if it's there for old idoc is has to stay with the new IDOC adapter,

Regards,

Michal Krawczyk

[former_member257758]

Hi Swathi,

Thanks for the response. But I am confused after reading both the forums. Can you pls clarify below.

1. Do we need to use BD64 settings for standard IDOCS( MATMAS,ORDERS Etc) when communicating with PI Java only Stack?

2. What about custom IDOC, In our case we have copied the MATMAS to ZMATMAS and trying to communicate (to create a file) with PI Java only Stack.

3. Is there any use case when we do we go for BD64 setup when we are communicating between SAP ECC and PI Java only stack.

But one thing I am sure is I have created all the setup including BD64 when we were doing IDOC to file between SAP ECC and PI dual stack for standard IDOC type (MATMAS).

Appreciate your response.

Thanks

Ar

[former_member257758]

Hi Michal,

Thanks for the response. we are not migrating any thing between any PI versions. We started the development directly in PI 7.3 Java only stack. Can you pls clarify the below questions.

1. Do we need to use BD64 settings for standard IDOCS( MATMAS,ORDERS Etc) when communicating with PI Java only Stack?

2. What about custom IDOC, In our case we have copied the MATMAS to ZMATMAS and trying to communicate (to create a file) with PI Java only Stack.

3. Is there any use case when we do we go for BD64 setup when we are communicating between SAP ECC and PI Java only stack.

But one thing I am sure is I have created all the setup including BD64 when we were doing IDOC to file between SAP ECC and PI dual stack for standard IDOC type (MATMAS).

Thanks

Ar

[MichalKrawczyk]

Hi,

>>>1. Do we need to use BD64 settings for standard IDOCS( MATMAS,ORDERS Etc) when communicating with PI Java only Stack?

yes - exactly in the same was as with double stack PI

>>>>2. What about custom IDOC, In our case we have copied the MATMAS to ZMATMAS and trying to communicate (to create a file) with PI Java only Stack.

same thing - if you change the logical system to a new one - just copy the model

>>>>3. Is there any use case when we do we go for BD64 setup when we are communicating between SAP ECC and PI Java only stack.

does not matter if PI is double or single - for most of the master data you need a distribution model

Regards,

Michal Krawczyk

[former_member257758]

Hi Michal,

Thanks a lot. One last questions. What about if I have custom IDOC (no copy from standard IDOC) for transactional data.

Do I still need to maintain Distribution model?

Thanks

Ar

[baskar_gopalakrishnan2]

Do I still need to maintain Distribution model?

yes you need to maintain for the custom idoc too.

[former_member207622]

IDoc configuration in ECC is same  for single stack as well as dual stack of PI . Only differnce is RFC conection used is TCP -IP

create logical system for ECC as well as PI

Maintain logical system name in business system representing ECC in SLD

Follow the same procedure as you would do to connect to r/3 to PI dual stack

Distribution model is mandatory and I would recommend it .check these threads

http://scn.sap.com/thread/3207569

http://scn.sap.com/thread/3199913

Hope this helps

Thanks

Ninad Sane

[former_member257758]

Hi Ninad,

I have referred both the links, but I did not see any explanation regarding the BD64 setup in ECC for PI Java only stack.

Can you pls let me know the sequence of steps to do in ECC side when we are using PI Java only stack.

Thanks

Ar

[MichalKrawczyk]

Hi,

>>>Can you pls let me know the sequence of steps to do in ECC side when we are using PI Java only stack.

there's not difference for distribution model at all for new and old IDOC adapter,

only port and the RFC inside it gets changed,

Regards,

Michal Krawczyk