on 07-14-2008 11:10 AM
Hi All,
I am new to XI. I need to know what is an IDoc? How it works? and what are all the configuration to work with IDoc?
Thanks & Regards
Nithya
Hi,
for IDoc please have a look here:
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm
this is helpful for configuration:
Regards
Patrick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I got the below error in receiver RFC channel....can any one pls suggest me what to do to resolve this...
Error in processing caused by: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling ZXI_BAPICHECKWRAPPER_RFC in remote system (RfcClient[ECC_RFC_Out]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: HDR ID C400641D0870E548 PCK 0000 already registered (duplicate)
Thanks,
Madhu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI
IDOCS:
Idoc is a data container itu2019s not a process, these are stored in database tables and each idoc has a unique number. Idocs are independent of direction of adapt exchange. Idocs are based on EDI Standards and close to EDIFACT. Idocs can be viewed in text editor and do not contain any binary data.
Workflow is used to control and co-ordinate the sequence of steps in a business process
Idocs are of 2 types.
1. Master IDOC.
2. Communication IDOC.
Master Idoc is a temporary idoc and it is not stored in database table.
First of all master idoc is created and if it succeeds in validations, it is converted to communication idoc.
Idoc Structure is of 2 types.
1. Basic
2. Extension
A basic idoc type will have the following characteristics:
Name: Can be up to 30 characters
List of permitted segments
Hierarchy of segments
Mandatory vs. Optional segments
Maximum/Minimum Range for segments.
Information hold by IDOCS is of 3 types. They are:
Control Record: Specifies Sender & receiver information.
Data Record: Contains data to be transferred.
Status Record: Contains status of IDOC.
Format of IDOC in Control Record: EDIDC
Message Type
Idoc Structure
Direction -1 or 2 1 is for outbound & 2 is for Inbound
Port [Receiver]
Partner Number [Logical System Name]
Partner Type
Format of IDOC in Data Record: EDIDD
Segment Name - SDATA (1000)
Format of IDOC in Status Record is EDIDS.
Segments: Segments will define format and structure of data record. Segments are reusable components. Segments contains field that represent data in data record.
Segments can hold only 1000 characters of data, if it exceeds new segment will be created.
The following are segment components:
Segment Type: It is the name of segment. Starts with u2018E1u2019 for sap defined and Starts with u2018Z1u2019 for user defined.
Segment Definition: It canu2019t be >1000 bytes and starts with E2 for sap defined and starts with Z2 for user defined
Segment Documentation: Represents data dictionary documentation for each field. Starts with E3 for sap defines and u2018Z3u2019 for user defined.
Segments get created as structure in dictionary and every segment must be released. Generally Release no for outbound is 620 and 640 for inbound.
Set release means, changes are made permanent. To make any changes to released segment, first cancel the release, then make necessary changes, save then release again.
Transaction Ports: These are used to transfer idoc between r/3 systems.
File ports: These are used to transfer idocs to sub systems in form of files.
Outbound programs referred as u2018IDOC Generatorsu2019
Inbound programs called as u2018POSTING Programsu2019.
Posting programs are implemented as function modules and are generally named as u2018IDOC_INPUT_<MSG TYPE>.
Status of IDOC:
01 - Initial status.
30 - Ready for dispatch
03 - Waiting at port.
12 - Reached Destination.
Modes of Transport: Outbound & Inbound
Outbound and Inbound numbers of idoc will not be same but data is same.
Reduced Message Type: To suppress some segments of standard structure.
Extended Idocs: Adding some new segments to existing idocs.
SOLD-TO-PARTY: Customer who placed order.
SHIP-TO-PARTY: To whom goods are sent
BILL-TO-PARTY: To whom bill is sent.
Filters are applied on mandatory segments. If filters are applied on optional segment, still idoc is sent to target system, but without optional data.
Transaction codes for ALE:
BD54 - To create Logical system
SCC4 - To assign client to logical system
WE81 - Message Type
WE31 - For Creation of Segment
WE30 - To create IDOC Structure
WE82 - To link between message type & IDOC Structure
WEDI - List all transaction codes for IDOC & EDI
SALE - List BD54 & SCC4.
WE21 - To create port of receiver
WE20 - Partner profiles
BD64 - For Distribution Model
cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nithya ,
IDoc u2013 Intermediate Document
IDoc is an Intermediate document that holds application data.
A container used to exchange data
It is independent of the complex SAP structure to store data.
It serves as the vehicle for data transfer.
IDoc Type defines the structure and format in which the data is exchanged.
It is similar to a structure in SAP
IDoc data is an instance of IDoc Type
IDoc acts as a standard SAP interface to exchange business data through ALE.
From an SAP system, an IDoc can be sent to and received from
An SAP R/3 system
An SAP R/2 system
An EDI subsystem
Any third-party application software
Segments . Idoc data is arranged in Rows, The rows make up segments of an idoc. Each segment consists of fields/segments. Fields can contain data.
These r the available T/Codes which we come across in IDocs:
TCODE TTEXT
BD10 Send Material
BD100 IDoc display object channel view
BD101 Consistency check
BD102 Outbound registry
BD103 Inbound registry
BD104 maintain tbd53
BD105 Maintain Supported Business Objects
BD11 Get Material
BD12 Send customer
BD13 Get customer
BD14 Send vendor
BD15 Open vendor
BD16 Send Cost Center
BD17 Get Cost Center
BD18 Send General Ledger Account
BD19 Get General Ledger Account
BD20 IDoc passed to application
BD21 Select change pointer
BD22 Delete change pointers
BD23 Delete serialization data
BD24 Send Cost Elements
BD25 Send Activity Type
BD26 Get Activity Type
BD27 Send cost center activity prices
BD28 Send obj/cost element control data
BD30 Distribute material object list
BD31 Distribute document object list
BD32 Distribute plant allocations(matBOM)
BD33 Distribute material variants (ALE)
BD34 Distribute order BOM
BD35 Send Business Process Groups
BD36 Send Business Processes
BD37 Send Business Process Price
BD40 Read change pointer for group
BD41 Dispatch IDocs for group
BD42 Check IDocs for group
BD43 Post IDocs for group
BD44 Assign Message Types to Serlz. Group
BD47 Dependencies between methods
BD48 Dependency method - message
BD50 Activate Change Ptrs for Mess. Type
BD51 Maintain function modules (inbound)
BD52 Activ.change pointer per chng.doc.it
BD53 Reduction of Message Types
BD54 Maintaining Logical Systems
BD55 Maintain IDoc Conversion
BD55OLD Maintain IDoc Conversion
BD56 Maintain IDoc Segment Filters
BD57 Maintain link and serialization ty.
BD58 Convert organizational units
BD59 Allocation object type -> IDoc type
BD60 Additional data for message type
BD61 Activate Change Pointers - Generally
BD62 Define Segment Conversion Rule
BD62OLD Define Segment Conversion Rule
BD63 Transport ALE Tables of Message Type
BD64 Maintenance of Distribution Model
BD65 Maintain IDoc type required fields
BD66 IDoc type field -> change doc.field
BD67 Maintain methods (inbound)
BD68 Maintain Lists
BD68OLD Maintain Lists
BD69 Assignment of Message Type to IDoc
BD70 Synchronize Number Ranges
BD71 Define FM for dependent bus. object
BD72 Activate Events
BD73 Reposting of IDocs (ALE)
BD75 Convert IDoc Status
BD77 Distribution of control data
BD78 Monitoring control data distribution
BD79 Maintain IDoc Conversion Rules
BD79OLD Maintain IDoc Conversion Rules
BD81 Filter objects parameter filtering
BD82 Generate Partner Profiles
BD83 Send IDocs after an ALE error
BD84 Post IDocs after ALE error
BD85 Consistency check for transfer
BD86 Consistency check for sales
BD87 Status Monitor for ALE Messages
BD89 Control data model. - initial screen
BD91 Send Characteristic
BD92 Send Class
BD93 Send Classification
BD95 Specify ALE object types
BD96 filter objects of receiver determin.
BD97 Assign RFC dest. to Logical Systems
BD98 Consistency Check Workflow Connectn.
BD99 Message type dependencies
WE02 Display IDoc
WE05 IDoc Lists
WE06 Active IDoc monitoring
WE07 IDoc statistics
WE08 Status File Interface
WE09 Search for IDocs by Content
WE10 Search for IDoc in Archive
WE11 Delete IDocs
WE12 Test Modified Inbound File
WE14 Test Outbound Processing
WE15 Test Outbound Processing from MC
WE16 Test Inbound File
WE17 Test Status File
WE18 Generate Status File
WE19 Test tool
WE20 Partner Profiles
WE21 Port definition
WE23 Verification of IDoc processing
WE24 DefaultValuesForOutboundParameters
WE27 DefaultValues for Inbound Parameters
WE30 IDoc Type Development
WE31 Development IDoc Segment
WE32 Development IDoc View
WE34 Object for Display of XML IDocs
WE40 IDoc Administration
WE41 Process codes, outbound
WE42 Process codes, inbound
WE43 Funct.module: Status record display
WE44 Partner Types and Checks
WE45 Forward (inbound) (V3, EDILOGADR)
WE46 Error and Status Processing
WE47 Status Maintenance
WE50 System process codes: Texts
WE51 System process codes: Change texts
WE54 FMs for changing file names
WE55 Function Module for Path Names
WE56 IDoc Administration
WE57 Assignment Messages for Appl. Objs
WE58 Status process codes: Texts
WE59 Change status process codes
WE60 Documentation for IDoc types
WE61 Documentation for IDoc record types
WE62 Documentation for segments
WE63 Documentation
WE64 Documentation message types
WE70 Conversion: Basic types
WE71 Conversion: Extensions
WE72 Conversion: IDoc types
WE73 Conversion: Logical messages
WE81 Logical message types
WE82 Assign Messages for IDoc Type
WE84 Assignment of IDoc and appl. fields
WE85 Create Rule Names
WEBU Printing Labels via Assortment List
WEDI EDI Basis
WEINBQUEUE IDoc Inbound Queue
WEKF Purchase order SAP Retail
WEL0 Forward (inbound) (EDILOGADR)
WEL1 EDI: Interface Invoice for EDILOGADR
WELI Maintain Status Groups
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Using WE30 we create Basic Idocs and IDOC extensions also.
IDOC basic Types are stored in EDBAS table
see the steps for Idoc creation:
Creation of Custom IDOc type and message Type
First Create Partner Profile(WE20 Tcode) and Port Definition in WE19 Tcodes.
take the Basis help to create them.
1.First create segments in WE31 Tcode with the required dataelements
2.Create the Basic Idoc Type in WE30
release the Segments and IDOC type.
3.Create Message type in We81
4.Assign the message type to IDOC type in WE82 T code
5.Create the process code in We41 (for Outbound) WE42 (for Inbound)
6.Create A fun module in SE37 starting with ZIDOC_OUTPUT_.. by copying some Inbound (for Inbound) Outbound Fun module
7.Create Workflow setting if needed ..
8. Assign the fun module to Idoc Type, Message Type and WF object (if it is there0
9.Define setting for fun module in BD51
10.In BD51 Define the settings for Fun module..
10.Assign the Processs Code to Fun mod`ule
Thanks,
Madhu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
>>I need to know what is an IDoc?
It is a SAP standard form used for interchanging the information between the SAP systems.
>>How it works?
A function module/BAPI/report can either update the IDoc data to the SAP tables are query the data from the SAP table and create an IDoc.
>>what are all the configuration to work with IDoc?
ALE configuration needs to be done to trigger or transfer a IDoc from one system to other.
Thanks
SaNv...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
An IDoc Type is SAP's format for data being moved between applications. Essentially, SAP has defined what a sales order, financial statement, invoice, etc will look like electronically. This includes how fields are grouped together (segments), the order and hierarchy of these groupings, and the format of each individual field.
If you're familiar with EDI at all, then an IDoc will look very familiar to you. Nearly everything you're used to is there: from segment name to allowable codes to min/max occurs.
It is important to note that an IDoc Type is really just a structure defined on the system and given a name (i.e., ORDERS04). An actual IDoc, however, consists of data, which fits within the defined structure of the IDoc Type. This IDoc is identified by a number rather than by a type.
For example : A delivery note trigger in the SAP should be udpated in the wearhouse system (Remote place). Which may be a non-sap system.
When an idoc is triggered from SAP. The data of the delivery note will be carried in the Data Record
(Structure/Segments),From and to address will be there in the control record.
Status record holds the status (Once the remote system receives the IDOC) the status is updated in this area.
Idoc creation
IDOC Programming
There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS( IDOC is send to other system . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
The basic structure of all outbound programs is same. The CONTROL
record which is of TYPE EDIDC has to be filled. It contains important fields like
IDOCTP IDOC type
MESTYP Message Type
RCVPRN Recieving Partner (Destination)
RCVPRT Partner Type (it is LS i.e Logical System)
The DATA RECORD internal table which is of TYPE EDIDD has to be filled
in the same order as there are segments in the IDOC definition.
It has 2 important fields which are to be filled ,these are
SEGNAM Name of the segment
SEGDATA Data in the segment and can be upto 1000 bytes.This field
is corresponds to each data segment in the IDOC.
e.g.
DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA W_SEGDATA LIKE zsegment "custom segment zsegment
INT_EDIDD-SEGNAM = 'ZSEGMENT'
W_SEGDATA-field1 = value "taken from some table
W_SEGDATA-field2 = value "taken from some table
INT_EDIDD-SEGDATA = W_SEGDATA
APPEND INT_EDIDD
This will fill the data record corresponding to the segment ZSEGMENT . For all
segments the sam steps will be repeated until all the data corresponding to all the
segments in the idoc is filled in the internal table of type EDIDD.
There is only one control record and can be multile data records in the idoc
structure.
Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.
Check out these links for more details.
IDOC Convertion
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
Regards
Aashish Sinha
PS : reward points if helpful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Creation of Custom IDOc type and message Type
First Create Partner Profile(WE20 Tcode) and Port Definition in WE19 Tcodes.
take the Basis help to create them.
1.First create segments in WE31 Tcode with the required dataelements
2.Create the Basic Idoc Type in WE30
release the Segments and IDOC type.
3.Create Message type in We81
4.Assign the message type to IDOC type in WE82 T code
5.Create the process code in We41 (for Outbound) WE42 (for Inbound)
6.Create A fun module in SE37 starting with ZIDOC_OUTPUT_.. by copying some Inbound (for Inbound) Outbound Fun module
7.Create Workflow setting if needed ..
8. Assign the fun module to Idoc Type, Message Type and WF object (if it is there0
9.Define setting for fun module in BD51
10.In BD51 Define the settings for Fun module..
10.Assign the Processs Code to Fun mod`ule
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
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
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
ALE/ IDOC/ XML
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
Thanks,
Madhu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.