FILE to IDOC

[Former Member]

I am having somany doubts in FILE to IDOC scanario.

The following steps we have to configure on XI server.

<b>• SM59 : RFC Destination</b>

in this step we have to give RFC destination suppose it is “R3DEST”

1. what it(R3DEST) is actually represent ? (is it logical system name ?) in ALE it is logical system nameand it is assigned to some cloent.

2. This R3DEST can we configured before?

<b>• IDX1 : Create the IDOC port.</b>

Port, suppose it is “SXICLNT100”

3. can we configure this name in TCODE: SALE or some where else? From where we got this port name ?

<b>• IDX2 : Maintain the Idoc Metadata</b>

Thank NAG

[Former Member]

Hi....

In file to idoc scanario i am getting error no: <b>56, i.e. IDoc with errors added</b>

and message: <b>EDI: Partner profile inbound not available</b>.

how to solve this error ...ple provide solusion

Thanks NAG

[Former Member]

Hi Muthavarapu,

this means that the partner profile is wrong.

Please check in the IDoc header which is the sender partner number (SNDPRN) and the idoc message type, then define the partner profile in WE20 accordingly.

If you have to use an already existing partner profile then fill this info in the header of the idoc inside the mapping in XI and in the idoc adapter flag "apply control record values form payload".

Regards,

Sergio

[Former Member]

Hi Sergio

Thanks for reply...but i culd't understand hoe to go...

ple provide some navigation steps....

Thanks NAG

[Former Member]

Hi

please have a look at this threads, they clearly describe all the steps to solve your problem:

Kind Regards,

Sergio

[Former Member]

Hi ....

i have confsion among Logical system, partner number and port.

can anybody clarify ...

Thanks NAG

[Former Member]

let me add to the above points....

<b>

ALE SETTINGS</b>

Once the mapping is done then re-check the ALE settings.

<b>

SAP XI

1) RFC Destination (SM59)</b>

a) Choose create.

b) Specify the name of the RFC destination

c) Select connection type as 3 and save

d) In the technical settings tab enter the details SAP SID/URL and system number#.

e) Enter the Gateway host as same details above SID/URL.

f) Gateway service is 3300+system number#.

g) In the Logon /Security tab, enter the client user & Password details of Destination system.

<b>h) Test the connection and remote logon.

2) Create Port (IDX1)</b>

a) Select create new button

b) Enter the port name as SAP+SID (The starting char should be SAP)

c) Enter the destination client.

d) Enter the RFC Destination created in SAP R/3 towards other system.

e) Save

<b>3) Load Meta Data for IDOC (IDX2)</b>

a) Create new

b) IDOC Message Type

c) Enter port created in IDX1.

<b>

<b>SAP R/3</b>

1) RFC Destination (SM59)</b>

a) Choose create.

b) Specify the name of the RFC destination

c) Select connection type as 3 and save

d) In the technical settings tab enter the details SAP SID/URL and system number#.

e) Enter the Gateway host as same details above SID/URL.

f) Gateway service is 3300+system number#.

g) In the Logon /Security tab, enter the client user & Password details of Destination system.

h) Test the connection and remote logon.

<b>2) Create Port (We21)</b>

a) First Select Transactional RFC and then click create button

b) Enter the destination port name as SAP+SID (The starting char should be SAP)

c) Enter the destination client.

d) Enter the RFC Destination created in SAP R/3 towards other system.

e) Save

<b>3) Create Partner Profile (WE20)</b>

a) Create New

b) Create the Partner no. name as same the logical system name of the destination system.

c) Select Partner type LS

d) Enter details for Type: US/USER, Agent, and Lang.

e) Click on the + button to select the message type.

f) Select Partner no. and LS which ever create above.

g) Select Message type

h) Select Process code related to the Message type.

I) save.

<b>In SLD – System Landscape Directory</b>

TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.

Ts for Third Party (Logical system):-

BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.

BS for Third Party (Logical system):-Enter the XI logical system name.

<b>

In Transaction SALE</b>

Define and Assign the logical system name.

[Former Member]

Hi...

now i am configuring in TCode: WE20 of R3 server...but it is giving error.

i am Creating the Partner no.

i have given

1. Partner no is LS100CL (This logical system of XI server of client 100)

2. Partner type LS

3. Type: US/USER,

4. Agent sapuser

5. Lang EN.

Plus button is grade out (inactive) this is for message type.

it is giving message <b>"enter a permissible partner number"</b> now what i can do...ple provide solution

Thanks NAG

[Former Member]

Create the classification for the profile.

[Former Member]

Hi Nageswara Rao ,

<i>1. Partner no is LS100CL (This logical system of XI server of client 100)</i>

Go to Transaction SCC4 or SALE.

CHECK Logical system name of your R3 system and give that name in WE20,not destination system's. First Save it then "+"/ " ADD" Button will be activated.

and maintain ( means JUST ADD NEW ENTRY) Destination system's Logical system name with proper client in SCC4 .

Reagards,

Ramesh.

[Former Member]

Hi Sreeramoju Ramesh,

i am configuring in TCode: WE20 from R3 server...but it is giving error.

you are right...but my point is that the partner no LS100CL is the logical system of client 100 of XI server. that means R3 server does't have LS100CL. look at below 1st 3 steps i have configured on XI server. next 3 steps (4,5,6) are configuring from R3 server. in this case how TCODE SALE of R3 server contain LS100CL ? here i really struck.

<b>SAP XI</b>

1) RFC Destination (SM59)

2) Create Port (IDX1)

3) Load Meta Data for IDOC (IDX2)

<b>SAP R/3</b>

4) RFC Destination (SM59)

5) Create Port (We21)

6) Create Partner Profile (WE20)

Thanks NAG

[Former Member]

Hi ,

As i said earlier you can add the logical system of XI in R3's SCC4 with NEW ENTRIES option.

->>>In R3

->Just Open SCC4,

->Check logical systems of both R3 and XI are existed or not.

-> If not there you can add.

-> check the clients.

try this and let me know what is happening.

Regards,

Ramesh

[udo_martens]

Hi NAG,

>>>>what it(R3DEST) is actually represent ?

Destination (connection) to R/3

>>>>(is it logical system name ?)

No

>>>>it is assigned to some cloent.

yes, look to the log on data

>>>This R3DEST can we configured before?

Hmmm, your english...

Dont change it, it might be important for somebody else. If it is connection type 3 (ABAP), you can use it.

>>>>Port, suppose it is “SXICLNT100”

3. can we configure this name in TCODE: SALE or some where else?

No. Only in IDX1

>>>>From where we got this port name ?

100 is from R/3 client, SXICLNT is a free name give in IDX1

>>>>IDX2 : Maintain the Idoc Metadata

Do nothing there

Regards,

Udo

[Former Member]

Udo ...

can u give me ur contact number (CELL number) sothat i can call you

otherwise u can mail me: mnrao_89@yahoo.com

Thanks NAG

[udo_martens]

Hi NAG,

if you have some questions regarding XI dont hesitate to post them here. Answering time is low and quality of most postings is very good. And it is for free..

Regards,

Udo

[Former Member]

Hi,

For File to IDOC you need to do following steps and bolg .

SLD-

1) Create a Product/Software Component

2) Technical System pointing to R/3 system

3) Business System for the above technical system

In the Repository

1) Import the Software component created in the sld

2) Create a namespace,

3) import the idoc and then create sender data type/message type etc and mapping

4) Mapping Rules is depends on the requirement

In the Directory

1) Create a Scenario /import the business system

2) Create Receiver/Interface determination

3) Create communication channels for sender and receiver

4) Sender Agreeement and Receiver Agreement.

Then the file adapter configuration is depend on the input file format.

Also you need to have Logical destionation created in the XI , and the IDX1 entry

In R/3

Port, Partner profile should be created with inbound idoc details.

Have a look into this document~

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38...

Regards,

Ramesh.

[Former Member]

Hi Muthavarapu,

1) if the RFC destination to your target system is already defined you can just use it, you do not need to create a new one.

2) the name of the idoc port is normally SAP<System ID>, you do not specify the client also in the name because in transaction IDX2 you will see more clients (if available) associated to the same name.

3) In IDX2 you have to import the idoc metadata, that means you have to import the structure of the idoc, so that when it will come into XI, XI will be able to recognize and handle its content.

Kind Regards,

Sergio

[Former Member]

Hi Sergio...i need some more clarification for 1st one:

i want to create new one, in this case give me navigation steps..

Thanks

[Former Member]

Hi Muthavarapu,

from Transaction SM59:

click on create

enter a name in the RFC destination, if it is a SAP system the standar is <System ID>CLNT<Client>.

Set connection type 3 (that means R3 system)

Insert a description

Insert the host name and system number of your target system (R3)

In the logon/security tab insert the logon data for the target system.

Kind Regards,

Sergio

[Former Member]

Hi Muthavarapu,

Hey check the following link

<a href="/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi:///people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi

Regards,

Akshay

[Former Member]

Hi,

Just check this link where you can find all your requirements:

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&

--Satish