New to idocs

hi,
can u pls tell me
1.wht is idocs?
2. wht is the use of idocs?
3.how xi will use idocs?
4.who will create idocs?
5.why xi will use idoc ?
6.wht is the functionality of idocs?
7.how sap r/3 uses idocs(my mean is in which scenario ?)
can u explain me in ur won words
regards
Guru

Hi Guru
1.wht is idocs? -
> IDOC Intermediate document(Which can hold the data ...)
2. wht is the use of idocs? --> To transfer the Data using IDOC
3.how xi will use idocs? ---> XI is using the to integrate based on the Scenario
                                          Idoc to file or File 2 Idoc etc....
4.who will create idocs? ---> We can create the new Idocs or Existing idocs can
                                          be used based on the client requirement and scenario
5.why xi will use idoc ? ---> Sap can send data either in the form of IDOC or RFC
                                        (BAPI) ...so integrate the SAP systems Idocs or Rfc's
                                        will be used
6.wht is the functionality of idocs? ---> just holding the data
                                                        every IDOC contains many segments
                                                         control,Status,data records
7.how sap r/3 uses idocs(my mean is in which scenario ?)
                                                   SAP ---XI -
FTP/RDBMS/SAP ...any
                                                 any system to SAP
Note : Idoc can be in general Asyn...scenario's
         This is the basic information but In SDN APAP CA you can find lot information on this
I hope tihs will help you
Regards
Prasad

Similar Messages

New to idocs and ale

dear friends ,
i am new to ale and idocs . i was practicing creating idocs . For eg say i wanted to send an SD invoice to a third party system . How would i go about starting the process . What are the things i need to take care of to start with like configuring and creating idocs . I would appreciate ur assistance in me learning the subject well.
Thank you ,
Message was edited by: Hari Krishna

HI Hari,
let me give u one example...
FUNCTION·MASTER_IDOC_CREATE_XAMPLE.
*"Local·interface:
*"·······IMPORTING
*"·············VALUE(APPL_HEADER)·LIKE·XHEAD·STRUCTURE··XHEAD
*"·······TABLES
*"··············APPL_ITEM·STRUCTURE··XITEM
*·variables·of·general·interest
··DATA:
*·······control·record·for·the·IDoc
········IDOC_CONTROL·LIKE·EDIDC,
*·······data·records·for·the·IDoc
········T_IDOC_DATA·LIKE·EDIDD·OCCURS·0·WITH·HEADER·LINE,
*·······table·for·the·IDocs·created·by·MASTER_IDOC_CONTROL
········T_COMM_CONTROL·LIKE·EDIDC·OCCURS·0·WITH·HEADER·LINE,
*·······partner·type·for·logical·system
········C_PARTNER_TYPE_LOGICAL_SYSTEM·LIKE·EDIDC-RCVPRT,
*·······help·variable·for·the·check·if·an·IDoc·has·to·be·created
········H_CREATE_IDOC.
*·variables·specific·for·this·example
··DATA:
*·······field·strings·with·IDoc·segment·structure
········E1XHEAD·LIKE·E1XHEAD,
········E1XITEM·LIKE·E1XITEM,
*·······data·to·be·put·to·the·control·record
········C_MESSAGE_TYPE·LIKE·EDIDC-MESTYP·VALUE·'XAMPLE',
········C_BASE_IDOC_TYPE·LIKE·EDIDC-IDOCTP·VALUE·'XAMPLE01',
*·······segment·types·to·be·put·to·the·data·record·table
········C_HEADER_SEGTYP·LIKE·EDIDD-SEGNAM·VALUE·'E1XHEAD',
········C_ITEM_SEGTYP·LIKE·EDIDD-SEGNAM·VALUE·'E1XITEM'.
*·check·if·an·IDoc·has·to·be·created,·read·the·distribution·model
··CALL·FUNCTION·'ALE_MODEL_DETERMINE_IF_TO_SEND'
·······EXPORTING
············MESSAGE_TYPE···········=·C_MESSAGE_TYPE
*·········SENDING_SYSTEM·········=·'·'
*·········RECEIVING_SYSTEM·······=·'·'
*·········VALIDDATE··············=·SY-DATUM
·······IMPORTING
············IDOC_MUST_BE_SENT······=·H_CREATE_IDOC.
*····exceptions
*·········own_system_not_defined·=·1
*·········others·················=·2.
··IF·H_CREATE_IDOC·IS·INITIAL.
*···no·message·flow·maintained·in·the·model,·nothing·to·do
····EXIT.
··ENDIF.
*·put·the·application·header·record·to·the·IDoc
··MOVE-CORRESPONDING·APPL_HEADER·TO·E1XHEAD.
*·convert·SAP·codes·to·ISO·codes
··PERFORM·E1XHEAD_CODES_SAP_TO_ISO
····USING
······APPL_HEADER
····CHANGING
······E1XHEAD.
*·append·record·to·IDoc·data·table
··T_IDOC_DATA-SEGNAM·=·C_HEADER_SEGTYP.
··T_IDOC_DATA-SDATA·=·E1XHEAD.
··APPEND·T_IDOC_DATA.
··LOOP·AT·APPL_ITEM.
*···put·the·application·item·record·to·the·IDoc·segment
····MOVE-CORRESPONDING·APPL_ITEM·TO·E1XITEM.
*···convert·currency·amounts·from·SAP·internal·to·neutral·format
····PERFORM·E1XITEM_CURRENCY_SAP_TO_IDOC
······USING
········APPL_HEADER-CURRENCY
······CHANGING
········E1XITEM.
*···convert·SAP·codes·to·ISO·codes
····PERFORM·E1XITEM_CODES_SAP_TO_ISO
······USING
········APPL_ITEM
······CHANGING
········E1XITEM.
*···left·justify·all·non·character·fields
····PERFORM·E1XITEM_CONDENSE
······CHANGING
········E1XITEM.
*···append·record·to·IDoc·data·table
····T_IDOC_DATA-SEGNAM·=·C_ITEM_SEGTYP.
····T_IDOC_DATA-SDATA·=·E1XITEM.
····APPEND·T_IDOC_DATA.
··ENDLOOP.
··CALL·FUNCTION·'MASTER_IDOC_DISTRIBUTE'
*·in·update·task···"if·application·document·is·posted·in·update·task
·······EXPORTING
············MASTER_IDOC_CONTROL············=·IDOC_CONTROL
·······TABLES
············COMMUNICATION_IDOC_CONTROL·····=·T_COMM_CONTROL
············MASTER_IDOC_DATA···············=·T_IDOC_DATA.
*······exceptions
*···········error_in_idoc_control··········=·1
*···········error_writing_idoc_status······=·2
*···········error_in_idoc_data·············=·3
*···········sending_logical_system_unknown·=·4
*···········others·························=·5.
*·A·commit·work·has·to·be·done.·It·could·also·be·done·in·the·calling
*·application.
··COMMIT·WORK.
··READ·TABLE·T_COMM_CONTROL·INDEX·1.
··IF·SY-SUBRC·<>·0.
*·no·IDoc·was·created,·you·can·react·here,·if·neccessary
··ENDIF.
ENDFUNCTION.
*&······Form··E1XITEM_CONDENSE
·······text···························································
*··-->··p1········text
*··<--··p2········text
FORM·E1XITEM_CONDENSE
··CHANGING
····IDOC_SEGMENT·LIKE·E1XITEM.
*·left·justify·all·non·character·fields
··CONDENSE:·IDOC_SEGMENT-QUANTITY,
············IDOC_SEGMENT-VALUE.
ENDFORM.·······························"·E1XITEM_CONDENSE
*&······Form··E1XITEM_CURRENCY_SAP_TO_IDOC
·······text···························································
*··-->··p1········text
*··<--··p2········text
FORM·E1XITEM_CURRENCY_SAP_TO_IDOC
··USING
····CURRENCY_CODE·LIKE·TCURC-WAERS
··CHANGING
····IDOC_SEGMENT·LIKE·E1XITEM.
··CALL·FUNCTION·'CURRENCY_AMOUNT_SAP_TO_IDOC'
·······EXPORTING
············CURRENCY····=·CURRENCY_CODE
············SAP_AMOUNT··=·IDOC_SEGMENT-VALUE
·······IMPORTING
············IDOC_AMOUNT·=·IDOC_SEGMENT-VALUE.
*······exceptions
*···········others······=·1.
ENDFORM.·······························"·E1XITEM_CURRENCY_SAP_TO_IDOC
*&······Form··E1XHEAD_CODES_SAP_TO_ISO
·······text···························································
*··-->··p1········text
*··<--··p2········text
FORM·E1XHEAD_CODES_SAP_TO_ISO
··USING
····APPL_DATA·LIKE·XHEAD
··CHANGING
····IDOC_SEGMENT·LIKE·E1XHEAD.
*·convert·a·currency·code·from·SAP·code·to·ISO·code
··IF·NOT·APPL_DATA-CURRENCY·IS·INITIAL.
····CALL·FUNCTION·'CURRENCY_CODE_SAP_TO_ISO'
·········EXPORTING
··············SAP_CODE·=·APPL_DATA-CURRENCY
·········IMPORTING
··············ISO_CODE·=·IDOC_SEGMENT-CURRENCY.
*······exceptions
*···········not_found·=·1
*···········others····=·2.
··ELSE.
····IDOC_SEGMENT-CURRENCY·=·APPL_DATA-CURRENCY.
··ENDIF.
*·convert·a·country·from·SAP·code·to·ISO·code
··IF·NOT·APPL_DATA-COUNTRY·IS·INITIAL.
····CALL·FUNCTION·'COUNTRY_CODE_SAP_TO_ISO'
·········EXPORTING
··············SAP_CODE·=·APPL_DATA-COUNTRY
·········IMPORTING
··············ISO_CODE·=·IDOC_SEGMENT-COUNTRY.
*······exceptions
*···········not_found·=·1
*···········others····=·2.
··ELSE.
····IDOC_SEGMENT-COUNTRY·=·APPL_DATA-COUNTRY.
··ENDIF.
ENDFORM.·······························"·E1XHEAD_CODES_SAP_TO_ISO
*&······Form··E1XITEM_CODES_SAP_TO_ISO
·······text···························································
*··-->··p1········text
*··<--··p2········text
FORM·E1XITEM_CODES_SAP_TO_ISO
··USING
····APPL_DATA·LIKE·XITEM
··CHANGING
····IDOC_SEGMENT·LIKE·E1XITEM.
*·convert·a·unit·of·measure·from·SAP·code·to·ISO·code
··IF·NOT·APPL_DATA-UNIT·IS·INITIAL.
····CALL·FUNCTION·'UNIT_OF_MEASURE_SAP_TO_ISO'
·········EXPORTING
··············SAP_CODE·=·APPL_DATA-UNIT
·········IMPORTING
··············ISO_CODE·=·IDOC_SEGMENT-UNIT.
*······exceptions
*···········not_found···=·1
*···········no_iso_code·=·2
*···········others······=·3.
··ELSE.
····IDOC_SEGMENT-UNIT·=·APPL_DATA-UNIT.
··ENDIF.
*·convert·a·package·type·from·SAP·code·to·ISO·code
··IF·NOT·APPL_DATA-SHIP_INST·IS·INITIAL.
····CALL·FUNCTION·'SAP_TO_ISO_PACKAGE_TYPE_CODE'
·········EXPORTING
··············SAP_CODE·=·APPL_DATA-SHIP_INST
·········IMPORTING
··············ISO_CODE·=·IDOC_SEGMENT-SHIP_INST.
*······exceptions
*···········not_found·=·1
*···········others····=·2.
··ELSE.
····IDOC_SEGMENT-SHIP_INST·=·APPL_DATA-SHIP_INST.
··ENDIF.
ENDFORM.·······························"·E1XITEM_CODES_SAP_TO_ISO
U can search this link..it ll help u well
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b826f43d711d1893e0000e8323c4f/frameset.htm
for ALE programing guide...
u can check this link..
http://help.sap.com/saphelp_nw04/helpdata/en/78/21785851ce11d189570000e829fbbd/frameset.htm
Reward points..if it helps..:-)
regards
manikandan R
Message was edited by: manikandan rajendran

How to copy the new application IDOC

I want have a Z Idoc with all features of Orders05.
(in fact i need to reduce some segments)
I also want to have the message type of ZOrders.
In this case do i need also to copy the interface program.
If this is at sender system. how can i operate the same idoc at receiver system..
please explain me breifly, if some one has some info.
Regards

Hi,
You need to perform following things for new IDOC type.
1. Creating new IDOC Basic type ( in ur case copy ORDERS05, let's say ZORDERS05).
2. Assigning Message type to IDOC type: WE82 ( in your case assign ORDRSP to ur new IDOC ZORDERS05).
3. Before you can use your new basic type in workflow (optional in inbound processing but required in error handling), you should create a corresponding object type in the Business Object Repository (BOR).
4. Creating a New Function Module (Outbound Processing under MC): SE37
Assigning a New Process Code to a New Function Module and Message (Outbound Processing): WE41
Go thru following documentation for detail answer. It contains information for both OUTBOUND and INBOUND.
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b828943d711d1893e0000e8323c4f/frameset.htm
It is not an easy process and requires many things to do, but of course not impossible.
All the best...
Pratik

Triggering new outbound IDOC via message control.

HI All,
I have a new outbound function module which is a copy of ALE_GOODSMVT_CREATE (ZALE_GOODSMVT_CREATE) for goods movements. I have created a new process code and linked the message type to the code. This function was created by copying the standard bsuiness object for goods movement BUS2017 and registering as a new interface in BDBG.
I have created a new output type in nace for ME, but was unsure how to correctly setup the processing routine. What medium (A, 6 or 8), program and routine do I use, or do I need to create a new program to call my function module? If I use RSNASTED and ALE_PROCESSING (medium A), I get a short dump as the parameters of the function do not match the parameters of my new function ZALE_GOODSMVT_CREATE.
Has anyone ran into a similar problem or can help with this?
Bets regards,
James.

Hi Sanjay,
I have created a distribution model, and added the new function to the ditribution module via the createformdata method which the function is linked to. I have also created the partner profile for message type using an LS partner. I have added my new process code to this message in the partner profile.
Now when I process my goods movement I get the error message "No recipient found for message type ZSUBCON in the ALE model". The distribution model and the partner profile appears to be setup correctly. Any ideas?
Rgds,
James.

How to post an Inbound IDOC .... I am new to IDOCs

I am working on an inbound idoc for creating a goods receipt based on PO.
I dont know how to post the idoc.... Some body pls help me..
Thanks in advance

Hi Raja,
Check this out.
Inbound IDocs are triggered by either external systems (edi, wms etc) or can be triggered by inhouse applications in SAP to post a application document.
1. EDI_DATA_INCOMING can create a IDoc from a file on the OS layer. It just needs a IDoc flat file containing control and data records, it will create an Idoc from it if the control record successfully matches a inbound partner profile parameters.
2. IDOC_INBOUND_ASYNCHRONOUS can be triggered by external/internal programs to creae IDoc withing SAP, whereas IDOC_INBOUND_SYNCHRONOUS can be used by inhouse SAP programs to create inbound Idoc.
3. WE19 can create and post an existing inbound Idoc to application
Hope this resolves your query.
Reward all the helpful answers.
Regards

CCMS - issue configuring new IDoc monitor template

Hi,
we wan´t to create a new CCMS IDoc monitortemplate in our central ALE configuration system and define all relevant remote SAP System and transport the complete template to the Solution Manager System.
We wan´t to customize the template in the ALE configuration System, "not" in SolMan.
These are the steps i´ve already done.
1. create new MTE´s by transaction BDMONIC2
2. customize the new MTE´s by tr. BDMONIC
3. create a new Template in RZ20
4. create a new Monitor for the new TEMPLATE in RZ20
5. after some minutes (the new created MTE´s are available for configuration)
First question. Why i have to wait some minutes to see the new MTE´s in the new monitor ?
anyway,
the monitortemplate for my own system(template creation system) is working fine.
6. Now i´ve created new entries to monitor remote SAP Systems in RZ21
7. I can see the new SAP Systems in my new TEMPLATE in RZ20
8. I would like to use my created MTE´s for every SAP System. Transport all MTE´s and configuration to the relevant SAP Systems.
9. I can see all entries in BDMONIC2 and BDMONIC in the remote System ...
... but I can´t see the new MTE´s in RZ20 in the remote System and
I can´t see the the new MTE´s (for the remote system) in my new TEMPLATE in the ALE configuration System (where the remote system is assigned).
note: I saw that a new MTE creates a new alert class in RZ21.
This class is filled in the template creation system(ALE configuration) but not in the remote system.
Any ideas what is going wrong here ?
thx,
Gordon
Edited by: Gordon Breuer on Jul 30, 2009 2:28 PM

Hi,
check this links:
http://help.sap.com/saphelp_nw04s/helpdata/en/9d/df1241c738f423e10000000a155106/frameset.htm
https://www.sdn.sap.com/irj/sdn/forums
Regards,
Spandan

How to read file from prsntn server in Inbound idoc FM.

Hi Experts,
I am new to idoc.
I have requirment that i need to read a file from presentation and application server and put in inbound idoc FM.Idoc will be processed in batch.
How can i put selection screen in FM and read the file?or how can i proceed with the solution?
Please help..
Umesh

Hi Umesh,
My understanding on your requirement is to read a file from pres. server and pass the data to an IDoc function module. Am I correct?
If this is the case then you can create a report which picks up the file from pres. server and then read data from the file and pass it to the parameters of the required function module.
Hope this helps.
Regards,
-Sandeep

How to send vendor IDOC data from SAP R/3 to XI.

Hi experts,
I have developed the IDOC to FILE scenario for Vendor Master Upload. I want to place flat file in local folder with in XI or Outside of XI. (Using NFS or FTP protocol in FILE adapter). My First quesstion is How to setup Folder with in XI ro Out side XI?
And also I want to push the IDOC from SAP r/3 to test the scenario. Both XI and R/3 systems are configured to exchange data.
How to Push Vendor IDOC from SAP R/3 to XI? (we can send XML directly to XI; but the R/3 kernal should be moe than 6.20).
Thanks in Advance.....

Hi,
>>My First quesstion is How to setup Folder with in XI ro Out side XI?
Its a normal way to creation of folders in Os level . u can create the folder in XI Server or on the FTP Server.
ALE Settings
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-XI-File scenario
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Posting the IDOC from R/3 to XI
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
REgards
Seshagiri

How to get IDocs list or BAPIs in IR

Hi Every one / XI Gurus,
I am learning XI.
I am an ABAPer for past 4 years.
I have learnt XI to some extent by using SDN (some docs, links and some weblogs).
Thank you all.
I have done File to File and XML to XML (both are almost same) scenario using a weblog mentioned in SDN.
It was very good and easy for beginners.
When i am trying to do the scenario IDocs to File or File to IDoc or
BAPI/RFC to File or File to BAPI/RFC using the Weblogs available in SDN
I am facing certain problems.
I am not sure if i am correctly giving the parameters in SLD.
But when i import the SLD to IR, i am not able to view IDocs or BAPIs in the IR.
Can you please help me in setting the SLD and getting the list of IDocs and BAPIs
in the IR.
Please do not suggest me any existing weblogs because i have gone through all of them available in SDN.
Thanks,
Priyanka.

Hi,
In IR you can import the RFC from R/3 system.
Right Click on the Imported Objects and click the RFC and choose import the RFC.
Select the Radio Button Import of RFC/iDoc allowed. After U Create a Namespace
Save it And Activate
The Follow the Following Steps To Do
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.
Regards
Khanna

IDOC: Error in ALE Service

Hi All,
I have created a new outbound idoc type ZSLSRPT and assigned it to a partner profile with type LI in we20. I tried running my customized program for idoc outbound and the status shows Error in ALE Service, Entry in outbound table not found.
Am I missing something with the partner definition? Do I need to configure the vendor output type in NACE? Please help.
Thanks,
Kenny

Hi Kenny,
Have you setup the distribution model (BD64) for the corresponding message type?
Also check this link for your reference.
http://help.sap.com/saphelp_nw04/helpdata/en/52/16adef543311d1891c0000e8322f96/content.htm
Regards,
Ferry Lianto

Development of custom IDOC's

Hi All,
Can we go for approach of developing custom IDOC's? where in our scenarios are getting files from thrid party and updating data in file into ECC.
Approach towards Custom IDOC's is for error monitoring and recprocessing.
Would request your inputs and suggesions in this regard.
Is that good approach for going to custom idocs? if not why?
Thanks,
chandra.

Hi,
SAP R/3 systems send out data through IDoc (Intermediate Document), which in internally has segments and fields containing the data. But sometimes, these fields are not sufficient for a specific end-to-end business scenario as far as data transfer is concerned. So in such scenario, either few fields are to be added or subtracted, or completely new structure- IDoc needs to be created.
At times because of the business scenario we do have to create Custom idocs .
Regards,
Bhanu

Idoc exchange between SAP R/3 4.6C and AS/400

Hi
We need to develop an interface between SAP 4.6C and AS/400 Warehouse System. The users are totally new to idoc concept. I need some information where I can get information on how idoc can be created from by AS/400 warehouse persons ? What kind of middleware is needed, etc. ?
Hopefully in simple terms since the users are in South Korea.
Thanks!

Hi Dhanesh,
You can use SAP XI (Exchange Infrastructure) as a middleware to establish
the interface between SAP R/3 & AS/400.
The output of an AS/400 can be of any format, but that will be converted by
SAP XI into IDoc & will post the same in SAP R/3.
For information on XI, check the following PDF:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1ebea490-0201-0010-faad-a32dd753d009
http://help.sap.com/saphelp_nw2004s/helpdata/en/0f/80243b4a66ae0ce10000000a11402f/frameset.htm
best regards,
Thangesh

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.

File to IDOC - issue with partner profile

I have done File to IDOC scenario and tested it end to end successfully. For same have done all require configuration setting in R/3 like defining logical System and partner profile. And it sends new IDOC successfully in R/3 with status code 50 (IDoc added).
But when I create new logical system and partner profile in R/3 and when I use same logical system in my above mention scenario then my new generate IDOC in R/3 return status code 56 (EDI: Partner profile inbound not available). But same scenario work fine with my earlier partner profile. Here I have done all require changes at adapter level like adapter specific identification and same new logical system I have update in SLD with my business system Logical System Name.

Hi Bhavesh,
Thanks for your reply.
In control record, I checked with sender and receiver partner. In this sender partner is new partner profile which I have created with port details. Receiver partner has logical system name which I have mentioned in my SLD for my receiver business system. But in receiver partner dont have any port details.
But still it has same problem.
-Sunil

ALE Configurations in File to IDOC Scenario

Hi All,
We are doing File to IDOC Scenario.
ALE Configurations done:
R/3 Side:
1. Created RFC dest, pointing to XI and tested the connection for remote login to XI.
2. Created port in R/3(using automatically generated port name) and assigned the RFC dest created above.
3. Created partner profile and assigned the ports to the message types.
4. Created Logical system
XI side:
1. Created RFC dest, pointing to XI and tested the connection for remote login to r/3.
2. Created port using IDX1 transaction with port name starting with SAP<SID> and assigned the RFC dest created above. (SID of XI)
3. Unable to load metadata in XI.
Now we are unable to test the scenario as it provides an error message in MONI as "Error: Transaction IDX1: Port SAP<SID>, client , RFC destination contain errors".
Also Let me know whether the steps mentioned above are correct for the scenario.
Regards,
Nithiyanandam

Hello,
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 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 #####+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.
With Regards,
Vidya.
*******Reward with Points if found useful

New to idocs

Similar Messages

Maybe you are looking for