IDoc settings

Hello Guru's
Can any one send methe link where i can find the Idoc settings related material or screenshots.
regards
aryan

Hi,
check the following links:-
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
http://help.sap.com/saphelp_nw2004s/helpdata/en/ab/bdb13b00ae793be10000000a11402f/content.htm
/people/sriram.vasudevan3/blog/2005/09/01/mdm-55-data-distribution-using-sap-xi
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/0b/2a65ec507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/02/265c3cf311070ae10000000a114084/content.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
Regards,
Archit

Similar Messages

IDOC to JDBC scenario-IDOC settings

Hi all i m doing an idoc to JDBC scerio and i have configured the settings and trying to trigger an ido and see whether i am able to post the data into the Db or not but i cant see idocs in XI:these are the steps i follwed posted in earlier forums:
Create an RFC destination to XI in the sender SAP system using SM59
Create a transactional port to XI using the RFC destination created in the above step
Create a Partner agreement using transaction we20 in the sender SAP system
Create a logical system using transaction bd54 for the partner agreement created in the above step
Select an IDOC using transaction we19 and change the EDIDC header recipient port & LS name
Create an RFC destination to the Sender SAP system using SM59
Create port to sender system using idx1 in the XI system for the RFC destination created in the above step
Create Metadata in idx2 transaction..
I have done the above and trying to trigger an idoc in we19 by changing the control records...but my idoc is not getting triggered.
Did i miss any other configuration?Please guide me.
also my guess is that i might have missed something in my partner profile config,
i specified ordrsp msg type in o/b parameters,specfied the port,selected trasfer idoc immediatley option,specified process code..i guess thats about it
Am i rite?Am I missing something.
Thanks

HI Aarthi,
In WE19 while triggering Idoc, what are you getting ? ANy error..Is it created any Idoc number . If so go to WE02 and check the status ...
If Idoc is triggered and it is not reached into XI, then you can check in SM58 for the status.
TO cross check the configuration-
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
Also check how to guide for Idoc scenario.
https://websmp106.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&
Regards,
Moorthy

Idoc settings for Backend Contract creation in SRM 5.0

Hello,
Im working on SRM 5.0 (HP 11) and want to create a Backend contract in R/3 (46C) directly.
I do not need Local Contracts or GOAs en SRM!
As I interprete the config guide for Sourcing (page 59 and 70-75, the scenario I need uses the BADIs:
BBP_DETERMINE_LOGSYS (determining Back End System)
BBP_CTR_BE_CREATE (for Mapping SRM settings with R/3)
I also understand that the Idoc configuration only needs to be done in the backend!!? (page 73 / 74)
Trx: WE42 and WE20.
Is this correct? Or do I have to maintain also the the IDOCs config in the SRM system?
Thanks for any clue.
Aart

Hi,
Pls refer the foll thread for all settings:
Follow-on contract from Bid Invitation
BR,
Disha.
Do reward points for useful answers.

FILE to IDOC settings

Hi all,
I am doing the scenario of file to idoc in which is it necessary to create RFC destination on both XI side and R/3 side. Clarify the settings required from XI to R/3 ..
regards,
kumar

This is expalined both the scenarios:
Please follow the below process for configuration:
Pre-requisites for Inbound IDoc to R/3 from PI:
Configuration required at Xi side:
Go to IDX1: configure the port.
Go to IDX2: load the DOC metadata.
Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
Configiration required at R3 side:
Maintain Logical System for PI (SALE transaction):
Maintain Partner Profile for XI system(WE20):
Pre-requisites for Outbound IDoc from R/3 to PI:
Configurations required in R/3:
Maintain Logical System (SALE)
Define RFC Destination (SM59) which points to PI system
Maintain Port (WE21)
Maintain partner profile. (WE20):
Maintain Distribution Model (BD64):
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
Thnx
Chirag

Single Host for netweaver/xi & Idoc settings in ale

HI,
In the case of a single system which is the R/3 system as well as the xi system...what settings are to be done from ALE to enable idoc processing...is this the same as a dual system configuration..or ?
I am pasting some of the steps suggested for the ale configuration.
Can anyone re-organize this or format this so that it applies for a single system that is the db host, Xi Host, and r/3 host.
There are several ways of doing it, all eventually leading to the same conclusion..but in the case of a non-distrubuted system, there are some differences..Can someone put some clarity here...as i have tried the steps and not all of them clearly apply in the case of a single host.
link1) https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
Link 2) /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
3) ALE settings.==> Author( Raghavesh Reddy )
SAP XI1) 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 XI 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.

If you want to configure your R/3 system to send IDocs to XI the first thing you have to do is configure the basic ALE:
Logical System
-Representation of a system R/3 will communicate with
-Every R/3 client used in ALE must have a logical system associated
-BD54 change logical systems (add), SCC4 change clients (attach logical system)
-Stored in tables TBDLS and TBDLST
Ports
-Logical representation of a communication channel
-How you refer tie together RFC destinations with partner system
-WE21 or WEDI
Partner Profile
-Ties together many pieces of the ALE puzzle
-Message types, IDoc types, process codes, partner functions, application identifiers, message function, output type, and port
-Maintain inbound and outbound parameters (partner type, port, transfer immediately or collect IDocs)
-WE20, WEDI, or SALE
-Viewed as a gateway, routes a particular message of a specific IDoc type to the given port and invoking the appropriate function modules
The next thing you have to do is configure the IDoc adapter in XI to prepare the system to accept IDoc's into the integration builder from other SAP systems.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098

LSMW - BAPi(Idoc settings)

Hi ,
i want to call BAPi in LSMW so in the intial screen iam goin go to settings - idoc inbound processing.
there it is asking for fileport nad partner number: what details should i give.
step by step pls
Thanks,
Donald

Hi Donald,
Go through the following Steps
check this link for step by step procedure on how to do LSMW using Idocs with screen shots
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
http://sapabap.iespana.es/sapabap/manuales/pdf/lsmw.pdf
Inbound Processing of LSMW Via IDOC's
Step1) Create the Partner Profiles & Port for Inbound Process and Ctivate the Inbound Process for LSMW.
     a) Goto Tcode SALE
                1) Create Logical System for Receiver Save & Come Back
                2) assign Logical to Client for LSMW inbound Process
     b) Goto Tcode SM59
                1) Create RFC Destinations for ALE
     c) Goto Tcode WE21
                1) Create a file port which can read the data from the specified path.
                Here select "FILE" Node --> Click on Create Button(F5)
                Give the following Information
                Port : FILE
                Desc : File Port for Inbound Processing of LSMW Via IDOC's
          Goto Outbound File Tab.
          Select Logical Directory Radio Button.
          Give LOCAL_TEMPORARY_FILES as Logical Path.
          If it is Physical Pthat : C:\TEMP\Filename.
Goto Tcode LSMW
===============
Give      Project          : ZPROJECT
     SubProject        : ZPROJECT
     Object            : ZPROJECT
Click on Create Button
then goto Settings Mwnu
          Click on IDoc Inbound Process.
Here you need to Pass File Port : File
                   Partner Type : LS
                   Partner No. : Port Name (Just Created from WE21 Tcode)
Save And Click on ACTIVATE IDOC INBOUND PROCESS
Save and Come Back.
1) Click on Execute(F8)    1 Maintain Object Attributes
Select IDoc(Intermediate Document)
Message Type : MATMAS
Basic Type   : MATMAS05
Save & Come Back
Then Your Getting the following Steps need to Do
2 Maintain Source Structures
3 Maintain Source Fields
4 Maintain Structure Relations
5 Maintain Field Mapping and Conversion Rules
6 Maintain Fixed Values, Translations, User-Defi
7 Specify Files
8 Assign Files
9 Read Data
10 Display Read Data
11 Convert Data
12 Display Converted Data
13 Start IDoc Generation
14 Start IDoc Processing
15 Create IDoc Overview
16 Start IDoc Follow-Up
2) Select the 2nd Radio Button & Execute.
Click on Create Button.
     Source Structure : ZE1MARAM
        Description      : XXXXXXXXXX
Click on Continu Button
Select Just Created "Source Structure : ZE1MARAM"
Again Click on Create Button this is your Second Source Structure.
     Source Structure : ZE1MAKTM
        Description      : XXXXXXXXXX
It Asks the Same Level or Lowerlavel of Source Structure : ZE1MARAM
select Lower Level Radio Button.
Click on Continue Button
Save & Come Back.
3) Select the 3rd Radio Button and click on Execute Button
Select the first Source Structure
   Click on Copy Button
Select the Third Radio Button
   Click on Copy Button
     Give the Tab Name is E1MARAM
Click on Continue Button.
Save this
Go bottom
Select the 2nd Source Structure " ZE1MAKTM"
   Click on Copy Button
Select the Third Radio Button
   Click on Copy Button
     Give the Tab Name is E1MAKTM
Click on Continue Button.
Save & Come Back.
4) Select the 4TH Radio Button and click on Execute Button
Select E1MARAM -->Click on Relationship Button
     Here A Small window comes then Select ZE1MARAM
     Click on Continue Button.
Select E1MAKTM -->Click on Relationship Button
     Here A Small window comes then Select ZE1MAKTM
     Click on Continue Button.
The Above two Structure are appears in Blue Color
Save & Come Back.
5) Select the 5TH Radio Button and click on Execute Button
First Structure : EDI_DC40 this is Control Record of your IDoc.
after this you will find a Structure "E1MARAM" this is in Orange Color Remember
Select MSGFN Field and Click on Source Field
         a New window will comes here select the ZE1MARAM-->MSGFN field and double Click on it.
Select MATNR Field and Click on Source Field
         a New window will comes here select the ZE1MARAM-->MATNR field and double Click on it.
Select MTART Field and Click on Source Field
         a New window will comes here select the ZE1MARAM-->MTART field and double Click on it.
Select MBRSH Field and Click on Source Field
         a New window will comes here select the ZE1MARAM-->MBRSH field and double Click on it.
Select MATKL Field and Click on Source Field
         a New window will comes here select the ZE1MARAM-->MATKL field and double Click on it.
Select MEINS Field and Click on Source Field
         a New window will comes here select the ZE1MARAM-->MEINS field and double Click on it.
Select GEWEI Field and Click on Source Field
         a New window will comes here select the ZE1MARAM-->GEWEI field and double Click on it.
Save This.
Go Bottom.
you will find a Structure "E1MAKTM" this is in Orange Color Remember
Select MSGFN Field and Click on Source Field
         a New window will comes here select the ZE1MAKTM-->MSGFN field and double Click on it.
Select SPRAS Field and Click on Source Field
         a New window will comes here select the ZE1MAKTM-->SPARS field and double Click on it.
Select MAKTX Field and Click on Source Field
         a New window will comes here select the ZE1MAKTM-->MAKTX field and double Click on it.
Save and Comeback.
Create Your Flat Files Like he following Format. and save it in C:\TEMP folder Only
1st File : MARA.TXT
001     MAT001                                   COUP     C     15          KG                                                                                          01
2nd File : MAKT.TXT
001     EN     New Material For Inbound Processing of LSMW Via IDOC's
6) Select the 6TH Radio Button and click on Execute Button
     We don't do any process here Just Come Back.
7) Select the 7TH Radio Button and click on Execute Button
     Click on Legacy data : Click on F5 Button.
              Add Two Files 1) C:\TEMP\MARA.TXT
                   2) C:\TEMP\MAKT.TXT
     Select Tablator Radio Button as Delimiter
     Save & Come Back.
8) Select the 8TH Radio Button and click on Execute Button
     Select ZE1MARAM Structure and Click on Assignment Button
     Save this
     Select ZE1maktm Structure and Click on Assignment Button
     Save and Come Back.
9) Select the 9TH Radio Button and click on Execute Button
     Click F8 Button.
     Check the Read Dada
10) Select the 10TH Radio Button and click on Execute Button
     Click F8 Button.
     Check the Display Read Data.
11) Select the 11TH Radio Button and click on Execute Button
     Click F8 Button.
     Check the Convert Data.
12) Select the 12TH Radio Button and click on Execute Button
     Click F8 Button.
     Check the Display Convert Data.
13) Select the 13TH Radio Button and click on Execute Button
     Click F8 Button.
14) Select the 14TH Radio Button and click on Execute Button
     This is WE05 Tcode Screen Start IDoc Process.
15) Select the 15TH Radio Button and click on Execute Button
     This is WE05 Tcode Screen Creating IDoc Here
16) Select the 16TH Radio Button and click on Execute Button
     Select Posting Radio Button(that is 5th Button)
     then Click on F8 or Execute Button.
After this your will check your Material exist in receving Side or Not.
Regards
Sreeni

IDOC settings from sap r/3 to sap pi7.3

Hi Guru,
actual problem when i am triggering the idoc from ERP,it is trigeering to the abap stack in sap pi.but i am using idoc_aae adapter at sender side,the message is flowing from sap ERP to file but the message is seen in sxmb_moni,but actually it is not seen in moni .
Please if any one have the idoc setting from sap erp to sap pi7.3. and iam using ICO configuration.
Please help me
Regards
Reddy

Hi,
Please go through the below link :
http://wiki.sdn.sap.com/wiki/display/XI/ALE-Idocconfiguration-+%28R3XIFile%29
Also in your software component version please check whether import of IDocs and RFCs are allowed
from your respective ECC system, and check the ECC system parameters are correctlt maintained or not.
Try out once.

IDoc to IDOC, settings

Hi!
I would like to implement IDoc to IDoc scenario.
I have one ECC 6.0 system with 2 clients and SAP XI system.
The problem is that the the message type MATMAS does not exist in XI system.
Furthermore I give the following error when I try to load metadata in tcode IDX2:
Basic type 'MATMAS02' is unknown
Message no. EA224
I already created Ports in tcode IDX1, defined the RFC connections
Can some one give me exactly the steps for business systems and XI to execute?
What I already have done:
1) Sender SAP ECC 6.0 (SID:ERB, client 100))
WE21: Creation of port SAPERP with RFC destination XI_SYSTEM
WE20: Creation of Partner LS according to logical names:
EC6CLNT100 (Outbound parameters: MATMAS and SYNCH)
EC6CLNT200
PIBCLNT100
2) XI System (SID:PIB, client 100)
WE21: Which Ports should I create here?
WE20 : Which partner LS should I create here and with which outbound/inbound parameters?
3) Receiver system SAP ECC 6.0 (SID:ERB, client 200))
WE21 Which Ports should I create here? ()
WE20 Which partner LS should I create here and with which outbound/inbound parameters?
It will be great to get some information.
Thank you very much!
regards
Holger

Hi,
Are some name conventions for the ports?
it should be SAP<System id>_<clent_no> in XI system. Transaction : IDX1
Other questions
What is the succesful condition/steps to see the meta data in IDX2 of SAP XI system?
If you have maintaned ports and RFC destiantion in XI for R3, metadat willl be loaded automatically in first run of your interface.
Do I need to create logical systems of both business systems in SAP XI?
Yes you need to create two business systems for each client.
Regards,
sreenivas.

IDOC settings and monitoring transactions-

Hi gurus,
What are the settings in customizing and in easy access to send a PO via EDI to a vendor?
Regards,
Deepak.

1. You must maintain an e-mail address in the address in the vendor master.
2. The same applies to your own user master. You also have to specify an e-mail address there in order to identify the sender.
Note that it is not possible to change the e-mail address of the vendor via the SAP purchase order transaction (ME21N, ME22N, and so on). The system only uses the e-mail address of the vendor that is maintained in the vendor master!
3. For the output type for default values, a communication strategy needs to be maintained in the Customizing that supports the e-mail. You can find the definition of the communication strategy in the Customizing via the following path: (SPRO -> IMG -> SAP Web Application Server -> Basic Services -> Message Control -> Define Communication Strategy). As a default, communication strategy CS01 is delivered. This already contains the necessary entry for the external communication. Bear in mind that without a suitable communication strategy it is not possible to communicate with a partner via Medium 5 (external sending).
4. Use the standard SAP environment (program 'SAPFM06P', FORM routine 'ENTRY_NEU' and form 'MEDRUCK') as the processing routines.
5. In the condition records for the output type (for example, Transaction MN04), use medium '5' (External send).
6. You can use Transaction SCOT to trigger the output manually. The prerequisite for a correct sending is that the node is set correctly. This is not described here, but it must have already been carried out.
7. To be able to display, for example, the e-mail in Outlook, enter PDF as the format in the node.

IDOC-XI scenario problem

I have a IDOC - XI scenario,
where IDOC is generating from a R/3,
the problem is, an IDOC was sent from R/3, but has not reached XI,
in R/3, i have seen in WE05, there i see this IDOC having status '03',
and, also in SM58, there i no error corresponding to this IDOC,
but in XI, in IDX5, i cant see that IDOC,
where the problem lies?

Make sure that the sender partner and receiver partner values corrrespond to the logical system names you have used in your partner profile in we20. Sender Partner Name should be your R3's logical system name, and Receiver Partnr Name should be the Logical System name for which you have created an Outybound Entry in We20.The Sender port and receiver port also should be be the ones created in We21 for XI, and SAP+"SYSID" for R3
) Check your PARTENER PROFILE settings ; is IDOC in outbound messages.
2) You may need to check Bussiness System given for Technical System for r3 and in ID check Adapter Specific Identifiers in OBJECTS ->Bussiness System->Service
Go to bd87 and trigger them. You can only trigger the idocs if they are in yellow color. If it is in red it is having an error.
So try to send the one which are in yellow error so that we can see whether it is reaching XI or not. If everything is OK then you should see the idoc in sxmb_moni.
Please see the below links ,
/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
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
idocs - /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
note:reward points if solution found helpfull.....
regards
chandrakanth.k

Idocs from XI to a flat file

Dear All,
I having a scenario in which whenever a Delivery is created in R/3 an idoc is posted into XI. I am able to see the idocs in transaction IDX5. Now I want to download this Idoc into a flat file thru XI.
Kindly guide me how this can be done oe tell me the suitable links to do the same.
Warm Regards,
N.Jain

HI Jain
It is IDOC to File Scenario.
Follow the steps in the wiki ...
https://wiki.sdn.sap.com/wiki/display/XI/StepbyStepProcedureofIDOCtoFileScenariousingBPM
see the below links
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
Also
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
Cheers..
Vasu
** REward Points if found useful **

JDBC to IDOC Scenario

Hi Experts,
I have tried JDBC to IDOC Scenario but it is giving No Segments Found Exception. I don't know where I am doing the mistake.
can any body please send me a pdf document for JDBC TO IDOC Scenario with step by step procedure from scratch (including creation of LS,LI etc)
Thanks in Advance,
Murthy

Hi Murthy
The steps are pretty much the same as any other scenario with some exceptions
1: You import the IDOC structure from the R/3 System. This acts as the DT, MT and MI.
You also need to do some configurations on the ABAP Stacks of sender and XI system.
Sender:
WE20 Partner Profiles
SM59 RFC Destination
XI:
SM59 RFC Destination
IDX1 Ports
IDX2 This is the metadata repository so you wont necessarily need this.
Also because you IDOCs can be sent directly to the ABAP stack/Integration Server you do not need a sender comm channel or sender agreement.
The rest is pretty much as any other scenario.
Please see the below links
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
Cheers..
Vasu
** Reward Points if found useful **

What all configurations to do in SAP R/3 to send an iDOC to XI system

I want to send an idoc from an SAP R/3 ECC5.0 to an XI system Netweaver 04's.
Pls let me know the STEPS I HAVE TO DO IN MY r/3 SYSTEM .
I have created the RFC destination in R/3 and XI system but still the idoc is not going into XI system.
It would be a great help if i can get step bu step guide for the configurations i have to do in R/3 .

Hi,
First check the status , with we02
Also see the below links
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
/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 erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
Regards
Chilla

Reg : Idoc Transfer From SAP R/3 to Gentran

Hi Floks /
Any body can transfer SAP R/3 idoc to external Sterling Gentran intgration suite . what are process steps required to sending and what are the transaction codes are available in Gentran and Sap .
can u please help me out.
thanks
suresh

HI,
See the below links
In Gentran
XI with Gentran
XI vs Gentran for EDI
SAP ECC 5.0 Upgrade questions with Gentran, BDC, screens
Gentran EDI ?
Interuppting/debugging response from Gentran
Gentran and XI 3.0 question
Interuppting/debugging response from Gentran
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d53af8ca-0801-0010-08b0-dce9e02130a8
In R3 IDocs
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping - Any flat file to any Idoc
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm - Collection of IDoc to Single File
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
File-XI-IDoc Scenario - File to Idoc
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
idocs - /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
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
/people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii
see the below links to get more details about IDocs
ALE/ IDOC/ XML
Troubleshooting of ALE Process - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
Please check this online document for ALE and IDoc.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
serialization /people/alessandro.guarneri/blog/2006/11/26/content-based-serialization-dynamic-queue-name-in-xi
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.henrikfrank.dk/abapexamples/IDOC/gl_postings2.htm
http://searchsap.techtarget.com/ sDefinition/0,,sid21_gci852485,00.html - 45k - Cached - Similar pages
Process codes in IDOC
http://help.sap.com/saphelp_erp2005/helpdata/en/dc/6b806743d711d1893e0000e8323c4f/frameset.htm
http://edi.stylusstudio.com/msg04418.htm
Check this link to find out the difference b/w ALE,IDOC and BAPI
http://www.sap-img.com/abap/ale-bapi.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
---Split messages :
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
/people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure
Regards
Chilla

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 settings

Similar Messages

Maybe you are looking for