regarding Idoc scenario....

[Former Member]

Hi Gurus,

Could any one explain what are the configurations required for idoc to file scenario ?

i have configured every thing, with defining a logical system, assigning a logical system, creating port and partner profile and i am getting confusing about how to trigger an idoc from r/3 system and how the data flow through these settings?

could any one of u please explain me about how the message will be flown in the settings that done in between R/3 to XI..

regards.,

sai kumar

[prateek · Accepted solution]

The Idoc can be triggered for test purpose using we19. When triggered, based on the port, a particular message type is transferred to the XI system using the RFC destination for XI system created at the R3 system

Regards,

Prateek

[Former Member · Accepted solution]

Hi Raj,

Once if i posted the idoc using WE19 i am unable to trace whether it is delivered to XI server or not, i am unable to see the sucess of failure in the moni.. how to trigger the idoc if i use matmas.. is the only wat to trigger by using we19 or any other type to trigger..

regards,

sai

[Former Member · Accepted solution]

Hi,

Check with this

/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi

Regards

Seshagiri

[former_member556603 · Accepted solution]

Hi Sai,

As u have told there is no access to we19 transaction, the other way to test ur scenario is by using component monitoring of Runtime Work Bench.

Just log into component monitoring of runtime workbench,then click on display,then select adapter engine and finally go to test tab of adapter engine and give ur sending system and the payload.

This method is similar to triggering an IDoc.

Finally click on send message.

Reward Points if it is Useful..

Thanks,

satya

Edited by: SATYA KUMAR AKKARABOYANA on Apr 3, 2008 1:33 PM

[Former Member · Accepted solution]

Hi,

Did u refer my links which is provided to you. Once u psot the IDOC through WE19 then u can check the status of IDOC from WE02 tcode and check what is the stauts of IDOC(whether it is in error stage or not) if its showing green flag then u go to SXMB_MONI and check the status there.

I hope u have dloaded the metadata in IDX2 tcode in XI.

chirag

[Former Member · Accepted solution]

HI Chiraj,

thanks for ur reply..

Its showing green , the status was 03.. and unable to see in moni..

regards,

sai

[former_member556603 · Accepted solution]

Other Type of Trigerring Idoc..

For example You Dont have access to we19 transaction, the other way to test ur scenario is by using component monitoring of Runtime Work Bench.

Just log into component monitoring of runtime workbench,then click on display,then select adapter engine and finally go to test tab of adapter engine and give ur sending system and the payload.

This method is similar to triggering an IDoc.

Finally click on send message.

Reward Points if it is Useful..

Thanks,

satya

[Former Member · Accepted solution]

HI satya,

we dont use any IDOC adapter in sender side .. how is it possible?

regards,

sai

[Former Member · Accepted solution]

Hi,

Check the RFC destination which is created in R3 and check whether it is pointing to Xi system or not. check the test connection tab and check the result.

Check the partner profile.

have u uploaded the metadata in IDX2 tcode of XI.

refer the configuration link which was given to u by me.

Now coming to

we dont use any IDOC adapter in sender side .. how is it possible?

IDOC adapter resides on ABAP stack hence we do not require any sender agreement and Sender communication channel.

chirag

[former_member238007]

Hi

See this

Steps

SAP XI

1) RFC Destination (SM59)

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.

2) Create Port (IDX1)

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

3) Load Meta Data for IDOC (IDX2)

a) Create new

b) IDOC Message Type

c) Enter port created in IDX1.

SAP R/3

1) RFC Destination (SM59)

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.

2) Create Port (We21)

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

3) Create Partner Profile (WE20)

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.

In SLD – System Landscape Directory

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.

In Transaction SALE

Define and Assign the logical system name.

IDOC Posting

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

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

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

StepsSummarized&

*Processing IDOC Errors *

http://help.sap.com/saphelp_sm32/helpdata/en/52/16adef543311d1891c0000e8322f96/content.htm

IDOC to file Scenario

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

regards,

Kishore

[former_member556603]

Hi Sai,

Hi

These are the steps which u have to do

STEPS IN DESIGN

1. Import idoc from the SAP System (SAP02) through imported objects.

2. Create Data Type, Message Type, Message Interface for the Outbound File.

3. Create Message Mapping with file Message and idoc (Matmas04)

5.Create Interface mapping between File Interface and the idoc.

Steps to be followed in Creation of Technical and Business System

Technical System

In SLD, click on technical landscape->New Technical System->WebAS ABAP.

Business System.

1.Goto Business Landscape->New Business System->Name the business system.

2. Choose the technical system that needs to be attached->WebAS ABAP->Technical System Name.

Preconfiguration steps for transfer of data to IDOCS

1.Create a RFC Destination in SM59 of XI Server of type.

2.In transaction IDX1 ,create a port for the client of XI server.

3. The port has to be displayed in the idx2 transaction and we should be able to view the idoc’s which we imported through integration repository.

Steps in Configuration

1. Goto service without party, right click->Assign a business system.

2. Choose the business system to be added.

3. Create a File Sender Service with communication channel for the same.

4. Create an idoc receiver channel under the business system.

7. The Idoc type( which data is to be written) is mentioned as inbound parameter.

8. Mention the logical Name in the Service->Adapter Specific Parameters of both the File Sender Service as well as the business system.

9. Make the Sender Agreement for theFile Sender with communication channel.

10.Create the Receiver Determination and Interface Determination for the business system.

11.Create the Receiver Agreement for the Business system.

Step for Configuration fo IDOC in R/3

SM59-rfc destination

IDX1-port

IDX2-load metadata

we05-IDoc status records

BD54-Create Partner Number

We20-Create Partner Profile

WE19-Testing IDoc Processing

Do these configurations in R/3 and in XI...

SAP XI

1) RFC Destination (SM59)

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.

2) Create Port (IDX1)

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

3) Load Meta Data for IDOC (IDX2)

a) Create new

b) IDOC Message Type

c) Enter port created in IDX1.

SAP R/3

1) RFC Destination (SM59)

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.

2) Create Port (We21)

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

3) Create Partner Profile (WE20)

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.

Idoc Testing...

Testing:

1. Log in to Adaptor Monitor and check for the file adaptor. The status of the adaptor should be green and working.

2. Check the ftp connection, it should connect to destination folder without any error.

3. Log in to sender system, go to transaction WE19 (test tool to generate IDoc), generate Idoc of the required message type.

4. Log in to Xi system and execute transaction SXMB_MONI and check for the XML messages. Use your source and destination system to filter messages, it should have chequered flag.

5. Check the destination directory, it should have file with the name specified along with the time stamp. Check the file, it should have data for all segments.

Hope this information is useful to you..

Reward points if it is useful to you..

Thanks,

Satya..

[Former Member]

Hi,

Data will be passed to Partner sys based on the Port and the RFC Destination created in R/3 towards XI.

It will identify the Partner and deliver it to that based on the Control record Info

Regards

Seshagiri

[Former Member]

Hi,

here is the link refer both of them.

ALE configuration for pushing idocs from SAP to XI

/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

IDOC testing using WE19

/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi

chirag