R/3 configurations (Idoc to File)

Hi,
while we create RFC Destination (SM59) in R/3 System, in logon security tab do we need to provide R/3 credentials or XI credentials??!!
Note: Scenario-- Idoc to file
Thanks.,
abhi

For idoc - file scenario - The purpose of RFC destination is to connect with any external system, XI in this case.
So to connect with XI, credentials of XI should be given
Regards,
Prateek

Similar Messages

Configuring IDOC to file Scenario in PI 7

Hello All,
I am doing an IDOC to file scenario, all the configuration is done. When i trigger the outbound IDOC, I can see in SXMB_MONI the sender component, sender Namespace, sender interface and reciever component are coming up correctly as configured.
1. But the reciever namespace and Reciever Interface are having the same values as the sender namespace and sender interface interface respectively. I am sure they have to be as per the config in ID.
2. Also on further going into the error message
SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_ERROR</SAP:Code
SAP:AdditionalText>No standard agreement found for , DEV400, ANZ, BC_RECV_PAYM_ORD, urn:sap-com:document:sap:idoc:messages, PAYEXT.PEXR2002</SAP:AdditionalText>
Can anyone please suggest , what is it that I am doing wrong.
---Prashanth

Hi,
Please delete the Receiver determination and try creating again. refresh cache.
Can you please have a look at the sap notes if of any use .. i think its a different case altogether , but pls have a look.
SAP Notes 1278244- https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1278244
SAP Note 1284103 -https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1284103
Regards,
Srinivas

IDOC to FILE Scenario-Error in defining Adapter specific Identfier

Hi All,
I am configuring IDOC to FILE scenario where IDOC will be send from ECC to PI System.I did following configuration
I created RFC,PORT,LS and Partner Profile on R/3 System. I had maintained SLD and IR. In ID I created Configuration scenario and business system.When I click on menu->Adapter specific Identfier where I want to specify IDOC Adapter and RFC Adapter. But it is not allowing to edit it is not editable. As we provide LOGICAL SYSTEM,sender system ID and client number of the sender system.

Hi Kavi,
I assume you correctly filled the Logical System of your Business System in the SLD...
Then in Integration Direction, use menu "SLD clear cache".
Always in Integration Direction, open your Business System, go to menu "adapter specific identifier", and... close to button "close", you should have another button like something ''check'' or "compare to SLD' or ''retreive SDL data'' (I have not an openned PI to check the right term). Use this button to get value stored in SLD to this local definition.
Mickael

Idoc to File scenario using Party

Hi All,
I have to configure Idoc to File scenario .This file needs to be posted in EDI Subsystem .My receiver partner type is LI.That means i need to use Party here.So please let me know the step by step solution to do this.Specially i want to know the configuration in Party Identifier and Receiver Communication channel Identifiers.
How the control record values from idoc are transferred to EDI File structure and how will XI identify one of the many customers to post the file.
All valuable suggestions will be rewarded the points.
Please send me the documents for such scenario with screen shots.

Hi,
Let me see if I had you requirement correct.
When the Idoc is sent from R3, sender partner type is LS and Receiver Partner Type is LI.
If yes,
1. Create a Party in ID.
2. The Agency , Scheme and Identifier will have values,
Agency --> Receiver Business System name or Business Service Name to be used for File.
Scheme --> ALE#LI
Identiier --> Value of the RCVPRN field in the idoc control Record. Basically the Receiver Partner Name.
All the Configuration In ID will use this Party as the Receiver Party and the corresponding Service asthe Receiver service.
No need for a sender party as sender partner is LS.
Regards
Bhavesh

IDOC to File Scenario - Configuration steps need to be done in R3 and XI

Hi Experts,
I am working with IDoc to File scenario. Can someone please explain, what are the steps or configuration things need to be done in R3 and as well as in XI too.
Thanks in advance.
Regards,
Sree

Hi Sree,
I thought i will just share a few basic thoughts that you need to take care while doing an IDOC to File Scenario. Just see if it helps you in anyways.
While doing an IDOC -> XI -> File scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
IDOC -> File scenario ref:
<a href="/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters scenario</a>
File -> IDOC ref:
<a href="/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping to IDOC</a>
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
Also have a look at these forum threads...
IDOC TO FILE SCENARIO
idoc to file scenario
I hope this answers your query.
Regards,
Abhy Thomas

Integration Directory configurations for IDOC - XI - File

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

> 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

How To Test Idoc To File Scenario in ID From Tools- Test Configuration

Hi All,
Can any body help me in step by step process including screenshots for testing Idoc to file scenario in integration directory from tools->test configuration.
My scenario is passing the PO Idoc data from R/3 into a file using XI.
i have processed the idoc from R/3 and now i went to sxmb_moni in XI system and took the payload xml data.
In ID I have navigated to test configuration from tools then i have provided the following information.
Sender Service : Business system of R/3 b'coz here R/3 is the sender.
Sender Interface : ORDERS.ORDERS6
Receiver Service : Business system of XI b'coz here XI receives the data and places it into a file
In payload text box i have copied the xml code which i have taken from sxmb_moni and clicked the run button. then i got the following error:
Sender Agreement
Internal Error
 HTTP connection to ABAP Runtime failed.
 Error: 403 Forbidden
 URL: http://bxdci.boewe.custservice.de:8093/sap/xi/simulation?sap-client=100
 User: PIDIRUSER
Kindly look into it and correct me if iam wrong or is there any other way to test this scenario in ID please suggest.
Thanks & Regards,
Venkat

Hi Venkat,
Specify the test confisuration as follows.
Sender
Service : Business System of SAP R/3 System
Interface : The outbound message interface name of type the IDOC.
Namespace : will automatically loaded when u select the Interface. Check if it the correct namespace.
Receiver:
Service : Business System name for the Fle system.
Paste the payload that u copied from the sxmb_moni.
Now click on Run and test ur Scenario.
Was the scenario sucessfull in the Message Monitor.
Regards
Santhosh

Step-by-step configuration from XI to R/3 for Idoc to File Scenarious

Hi Gurus,
Am the Beginner in Xi, I tried to connect the Xi to R/3 for Idoc to File Scenario but the connection fails, (error in Rfc showing ), could any one send me the step-by-step sm59 configuration. R/3 version 4.6c and Xi version 3.0
rewards sure
advance thanks
with regards
Thambee

hi,
I connected my 800 r/3 client to 100(xi) client, R/3 client is version 4.6d in it rfc test connection is sucessful but remote logon is not responding in my R/3 model view distributed and it's reflected in xi client, when I push the Idoc from R/3(bd10), Idoc created sucessfuly but not despatched
Idoc message type is 10 and 30.
Second thing am confused with Ip address bcoz 2 ip address in both system one is loopback and anoter one is tcpip adapter which one i have to give is sm59, help me plz
with regards,
Thambe

IDoc to File configuration

Hi,
Can anybody help me on the configuration part of IDoc to File scenario.

Hi,
I think you will find following links helpful:
IDOC-XI-File Scenario:
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Idoc-XI-POS (Triversity) scenario - new in XI
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
Collection of IDoc to Single File
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
Collection of Multiple type IDOCs in BPM:
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
Collecting IDocs without using BPM:
/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
XI:Idoc Message Packages
/people/sravya.talanki2/blog/2005/12/09/xiidoc-message-packages
Collecting from Multiple Interface and sending it to R3:
/people/prasadbabu.nemalikanti3/blog/2006/02/27/collecting-and-bundling-vendor-records-from-different-multiple-interfaces-file-systempeoplesoft-and-sending-to-sap-r3-system-part-2
IDOC PROCESSING:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
SAP R/3 IDoc Cookbook for EDI and Interfaces
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
/people/sravya.talanki2/blog/2005/08/17/outbound-idocs--work-around-using-party - Handling
different partners for IDoc
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133 - Idocs not
reaching XI. Not posted in the receiver SAP
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change - IDOC
bundling
idoc creation : http://www.supinfo-projects.com/cn/2005/idocs_en/2/

Which all configurations you need to do in R/3 for an Idoc to file scenario

which all configurations you need to do in R/3 for an Idoc to file scenario?
Rgds
Ruchitha

Hi ruchitha thakur ,
A Summary of the Steps to be carried out to enable a SAP R/3 System send Idocs to SAP Exchange Infrastructure.
First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
To Enable Acknowledgement:
SXMB_ADM ->Integration Engine Configuration ->Specific Configuration ->Add New entry -> Select parameters as:
Category: RUNTIME
Parameters: ACK_SYSTEM_FAILURE
Current Value: 1
GO TO SLD:
Create Technical System: Choose WEB AS ABAP if the system is R/3 -> Define SAP SID, Installation Number and Database Host Name a Maintain message Server Details according to Sender System -> Maintain Client Details of Sender System ->Select a Installed Product for Sender System
Create Business System: Choose WEB AS ABAP if the system is R/3 -> Choose the Technical System and the client Created Before -> Choose the Installed Product -> Set:
Business System Role: Application System
Related Integration Server: Integration Server
Integration Builder
Integration Directory:
Add Business System: Adapter Specific Identifiers -> 'Logical System' identical to the 'Logical System Name' in the SLD Business System
IDoc Receiver Communication Channel: port the same as XI System IDX1
The following web-sites give u step-by-step solution to configure R/3 :
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
How to convert an IDoc-XML structure to a flat file and vice-versa in XI 3.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
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
IDOCs (Multiple Types) Collection in BPM
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
Step by Step Procedure of IDOC to File Scenario using BPM
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/main&
cheers!
gyanaraj
****Pls reward points if u find this useful

Error/Doubts in Idoc-XI-File scenario

Dear All,
I am doing one scenario in which DELIVERY idoc is posted from R/3 to XI and then from XI that idoc is to be sent as flat file to one local folder.
For this scenario, I have done all ALE settings and I am able to see the idoc in XI in cXML format.Now I want to sent it as flat file.
Now, for doing this I created 2 BS & 2 TS. 1 BS & TS of type Third Party for receiver & 1 BS & TS are of type Web as ABAP for sender. Then I have created one namespace in IR. I have not created any DT, MT, MI, MM becoz the structure of source and target file are same. Now, I created one IM in which I specified specified Type as "ABAP Class" & Mapping program name as one of the Z function module as specified in one of the SAP Guides.
Then in ID, I created 2 Parties ie. one for Sender & one for receiver. Sender is having a communication channel of type Idoc & receiver is having communication channel of type File. And thn further Receiver Agreement, Inetrface Determination, Sender Agreement & Receiver Agreement are configured.
In my system there is one scenario already configured which is using Delivery idoc so I have used party in my scenario for both sender & receiver.
Now, when I am sending the idoc from R/3, I am able to see cXML in SXMB_MONI but it is taking receiver as the one which is defined for the already existing scenario but not the receiver defined by me.
Can anybody guide if I have followed the correct steps & where I am doing the error.
Warm Regards,
N.Jain

Hi ,
Plese refer the following blogs ,
IDoc to File
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
You have to do all this settings mentioned in the docuemnt:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
Also can you check this weblogs on the same:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Thanks ,
Suvarna
Award pts if it helps .

Integration server as logical system in IDoc to file scenario

Hi,
Will we configure integration server as logical system in IDoc to file scenario or the RFC destination related to the port will be suffice?
For which logical system will the outbound partner profile configured?
Regards,
Gajendra.

Hello,
I feel that the RFC destination linked to the port is the key here.
Because the scenario (IDoc to File) works in both the cases:
Case 1: Used the logical system as Integration server
Case 2: Used the logical system related to the file (third party) in the SLD.
In both the above cases the RFC destination points to the integration server.
Is this the case that in the XI scenarios (where IDoc are sent) the logical system name in the partner profile is just dummy and has not much significance??
It is the port that matters and once the Idoc reaches XI the routing takes place based on the configuration in ID.
Thanks.
Regards,
Gajendra.

R/3 to XI (Idoc to File): Do we need to maintain distribution model in R/3?

Hi All,
I have a very basic question regarding Distribution model.
My scenario is IDOC-->File ( SAP R/3 --> XI). So all I am trying to do is send the IDOC frrom R/3 to XI. ( Within XI I am going to do an FTP to the 3rd party file server)
I have created a distribution model, but was wondering if I really need to create one as message is going from R/3 to XI and not from R/3 to another R/3.
Please help let me know If I need to distribute this model to XI or to SAP production sytem or I do not need to duistribute at all for this scenario.
Thanks
Shirin

Hi,
if you create partner profiles and port via t.code.
i hope, it's not required to maintain Distribution model.
please check the below points.
Configuration Steps for Idoc to File Scenario.
This is complete step by step document for configuring the idoc to file scenario along with ALE Settings
To Configure the IDOC TO FILE SCENARIO, SETTINGS IN SAP-XI
STEP 1:ALE SETTINGS IN SAP-XI
We need to do the following settings in XI
1) Create an RFC Destination to the Sending System in transaction code (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.Both should be succesful
2) Create Port Using Transaction Code 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 Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) ALE SETTINGS TO POST IDOC OUT OF SAP-R/3 ***********************************************************************
a) Create RFC Destination using T.code in SM59.
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.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(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)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Outbound Parameters (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
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
5) Create Customer Distribution model in the transaction code BD64
1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3) Save the Distribution model
Generate Partner Profiles
Click on Menu Item u2018Generate Partner Profilesu2019
It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
Then, you will be intimated about the partners, port creation, and outbound parameters creation
4) Distribute Customer Distribution Model
In the menu item GO to Edit->Modal View-> u2018Distributeu2019 to the destination client
Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
warm regards
mahesh.

IDoc to File, SM58 shows error, ST22 short dump - Runtime error

Hi friends,
I am doing a simple IDoc to file scenario using the EVMSTA01 IDoc. My XI is running on client 100 and I am trying to send the IDoc from the client 200 on the same machine. I have completed the design and configuration steps required and also performed the required steps in Sender client (Sm59, we21 and BD54) and receiver client (Sm59, IDX1 and IDX2).
When I tried sending the IDoc from WE19, status meesage says that, the IDoc has been successfully sent to the receiver but SM58 shows error "IDOC_ERROR_WORKFLOW_START_R". When I looked in to ST22, there was a short dump with the below message -
Runtime Errors         MESSAGE_TYPE_X
Date and Time          18.10.2008 23:24:29
ShrtText
     The current application triggered a termination with a short dump.
What happened?
     The current application program detected a situation which really
     should not occur. Therefore, a termination with a short dump was
     triggered on purpose by the key word MESSAGE (type X).
Error analysis
     Short text of error message:
     Unable to read RFC destination WORKFLOW_LOCAL_200
     Technical information about the message:
     Message classe...... "SWF_RUN"
     Number.............. 617
     Variable 1.......... "WORKFLOW_LOCAL_200"
     Variable 2.......... "RFC_READ_DESTINATION_TYPE"
     Variable 3.......... "DESTINATION_NOT_EXIST"
     Variable 4.......... " "
     Variable 3.......... "DESTINATION_NOT_EXIST"
     Variable 4.......... " "
Trigger Location of Runtime Error
     Program                                 CL_SWF_RUN_WIM_LOCAL==========CP
     Include                                 CL_SWF_RUN_WIM_LOCAL==========CM07Z
     Row                                     10
Module type                             (METHOD)
Module Name                             IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
rce Code Extract
e SourceCde
1 METHOD if_swf_run_wim_utl_internal~get_system_user .
2   DATA: l_excp TYPE REF TO cx_swf_run_wim.
3
4   TRY.
5       IF me->m_int_state-system_user IS INITIAL.
6         me->m_int_state-system_user = cl_swf_run_workflow_properties=>get_rfc_destination_us
7       ENDIF.
8       re_user = me->m_int_state-system_user.
9     CATCH cx_swf_run_wim INTO l_excp.
>>       MESSAGE ID     l_excp->t100_msg-msgid
11               TYPE   'X'
12               NUMBER l_excp->t100_msg-msgno
13               WITH   l_excp->t100_msg-msgv1 l_excp->t100_msg-msgv2
14                      l_excp->t100_msg-msgv3 l_excp->t100_msg-msgv4.
15   ENDTRY.
16
17 ENDMETHOD.                    "
Any help would be appreciated..!!
PS: Points would be assigned to all the helpful replys without fail

Hi,
See check for RFC destination and it is working as per your configuration or not , i mean , it is trying to locate remote server.. , so try to check in sm59, remote login and the respective result is going to your required client or not ??
Also see the further errors while doing Idoc related scenarios..
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133 - Idocs not reaching XI. Not posted in the receiver SAP
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
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
Regards
Chilla

IDOC to file scenario

Hi Experts,
In IDOC to file scenario i did in this way.
1)created logical system.
2)Using SALE tcode I assign logical system to client ,created RFC destination,Port and Partner's profile.
It is showing all the thing correct.
3) In XI system , I configured using IDX1 and IDX2.
Then I created the material and checked the status which is green in we05.
But in tcode IDX5, the material is not coming.
Here I am confused that why data is not coming to XI system.
can anyone help me?
Thanks
Rabi

Hi,
The Following are the Possible checks
1) Check in R/3 side SMQ1 & SMQ2
2) Check in R/3 side SM58
   In R/3 system, Goto SM58 tcode and see if the IDOC have stuck up in Queue.
   If the entry is available then select it and press F6, to push it manually.
    This happens normally if IDOC stuck up in queues.
3) Check in PI SMQ2 and IDX5
regards,
ganesh.

R/3 configurations (Idoc to File)

Similar Messages

Maybe you are looking for