Idoc to file scenario

[Former Member]

Dear All

Please guide in idoc to file scenario.

how to create a partner profile

i am getting an error while creating partner profile "enter permissible parner no"

kindly help

Regards

Blue

[Former Member]

thank you all

[former_member556603]

Dear Hiddu,

IDoc to file scenario in which an IDoc from an SAP system is converted into a Flat File and routed to the FTP Server via Exchange Infrastructure.

1.2 Prerequisites:

One Business System representing the sending R/3 is required to be configured of type 3rd party in SLD (System Landscape Directory).

FTP configuration should be in place to transfer the output file to desired location.

2 Configurations at the Sender System (SAP R/3)

This section describes all the configurations needed in the Sender SAP System (R3X) for sending an IDoc to XIR.

2.1 Create RFC Destination

Use TCode SM59 to create RFC Destination in R3X to connect to XI (XIR) system.

RFC Destination in R3X: R3X_TO_XIR

2.2 Maintain Ports

Use TCode WE21 to create a tRFC Port. The RFC Destination created in the previous step should be assigned to this port.

Port in R3X: SAPXIR

2.3 Maintain Partner Profile

Create a Partner Profile for the Receiver System (XIRCLNT100) using the T-Code WE20, with the following outbound parameters.

Message type: MATMAS

IDoc Type: MATMAS05

Receiver port: SAPXIR

2.4 Create Distribution Model (BD64)

Create model view and add Message type with following

Sender System u2013 R3XCLNT100

Receiver System u2013 XIRCLNT100

Message type - MATMAS

Distribute the Model view.

3 Configurations in the Integration Server

This section gives an overview of all the configurations required in the Integration server. These settings are required for the XI system to receive the IDoc sent by the Sender SAP system.

3.1 Create RFC Destination

Use TCode SM59 to create an RFC Destination of Type 3 in order to establish communication with the Sender SAP system.

Sender RFC Destination in XIR: R3XCLNT100

3.2 Create Port

On the Integration Server, create a port for IDoc communication using transaction IDX1.

Ideally, the port name should be of the format SAPxxx, where xxx is the system id of the SAP system. The created port has to be bind with the RFC Destination of the Sender SAP system configured in the Step 3.1 above.

Sender Port in XIR: SAPR3X

3.3 Transaction IDX2

This configuration step is used to import the metadata of the IDoc using the corresponding Business systemu2019s port as below.

Thanks,

satya Kumar

[Former Member]

Hi,

i am getting an error while creating partner profile "enter permissible parner no

Partner number which you are trying to enter should be existing in ECC. Are you sure that the Partner profile from ECC is created already to send the Outbound IDOC.If not then ask your ECC guys to make one assign the message type to it and release.

Then from PI side we need create RFC destination (SM59)and Port (IDX1). While creating the port you will be asked to enter the partner Number which was created in ECC for the PI system.

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

to understand what needs to be done from ECC side to send an outbound IDOC.

Regards,

Srinivas

[Former Member]

Hi,

As its a IDOC to File scenario lets say your File system is 3rd party so its a R3 to 3rd party scenario.

you need to maintain the 3rd party logical system in BD54 first in R3 side and the create the partner in WE20 for that logical system(LS)

Once the partner(3rd party LS) is created,maintain the IDOC message type in the Outbound parameter of it.

Along with you need to maintain the port also WE21 and RFC destination SM59 alongwith.

cheers,

Abhishek.

[Former Member]

Hi

use the Tcode - WE20 to create partner profiles

IDX1 to create the Port

/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi

Regards

Ramg

[former_member181962]

Check this link:

http://help.sap.com/saphelp_NW04/helpdata/en/dc/6b809b43d711d1893e0000e8323c4f/content.htm

Regards,

Ravi