Ext. System communicating IDoc's with XI
Hello,
we are trying to connect an EDI-system to XI via the IDoc adapter. We have set up in IDX1 a port (EXTEDI, client 999). We have mapped the client 999 to field MANDT in EDIDC. And set up a Business system that mapps the logical name of the SNDPRN (sender partner) and the Business system. The repository is set-up and the directory. But we get technical problems when connecting the EDI-system wiht XI 3.0. The following error message occurs.
I have also created a TCP/IP RFC connection with program id amtrix_gothmog.
LogId <40088> MsgType <QUEUED>
Source: <aleCSE>, <NONE>
Destination: <log>, <TRFCONTROL>
Data (Inline)
ERROR :041028:14.04.44:r4edi(ale):Error sending IDoc to SAP
ERROR :041028:14.04.44:r4edi(ale):Key: RFC_ERROR_SYSTEM_FAILURE
ERROR :041028:14.04.44:r4edi(ale):Message: No service for system EXTEDI, client 999 in Integration Directory
INFO :041028:14.04.44:edirouter:Routing to 'aleCSE' pid=2095. RinfoId=741
LogId <40088> MsgType <FAILED>
Source: <aleCSEout>, <NONE>
Destination: <aleCSE>, <TRFCONTROL>
Data (Inline)
INFO :041028:14.04.44:edirouter:Routing to 'supervisor' pid=2080. RinfoId=30
LogId <40088> MsgType <FAILED>
Source: <aleCSE>, <NONE>
Destination: <log>, <TRFCONTROL>
Data (Inline)
WARNING:041028:14.04.44:r4edi(supervisor):Transfer failed for entry with LogId 40088
ERROR :041028:14.04.44:r4edi(supervisor):Entry with logId 40088 is EXHAUSTED.
Does anyone have any proposal for solution?
Brgds
Kalle
Hi Karl,
I don't think it is possible to set up the IDOC connection as you intended.
As to your first question:
I found that the XI IDOC adapter tightly integrated to SAP systems using TRFC. Since you are not using a SAP system this might cause problems.
As to your second question:
Note if the IDOC is not imported into the IDOC adapter XI will connect to the R/3 system to retrieve it. Again this will cause a problem since you don't use an R/3 system.
As to your third question:
You don't need to format the IDOC fields HLEVEL etc. When processing the IDOC the segements are matched using the IDOC definition (basic type) imported in the IDOC adapter.
I recommend to find an other form for communication. Does the tool vendor provide an adaptor?
Best Regards, Harald
Message was edited by: Harald Kastelijn
Message was edited by: Harald Kastelijn
Similar Messages
-
Please help with Sun Java System Communications Sync crashe with IEx 7.x
Dear All!
Recently i've upgrade my IExplorer to 7.x version. After that i began to have problems with Communications Sync (latest version). When i try to sync Outlook 2003 with the server (SSL connection/ self signed certificate) the Comm Sync asks if i want to allow to open connection with wrong certificate (happed only after installing IEx 7.x) and then when i press YES it crashes.
Any help on how to fix this problem is appriciated.
Konstantin
P.S.: Adding a self signed certificate to IEx DB and adding the website to the trusted websites list did not help.Hi,
Not sure how much we can help with this issue - especially if you are already running the latest version of the sync tool. About all I can offer is to uninstall your current sync software and reinstall the latest public version:
http://sunsolve.sun.com/private-cgi/getpatch.pl (search for patch #124734).
If that doesn't help I suggest you log a sun support case for this (assuming you have a sun support contract that is).
Regards,
Shane. -
Communication between SAP and 3rd Party Systems using IDOC HTTP XML Interfa
Hi
i am try do
Communication between SAP and 3rd Party Systems using IDOC HTTP XML Interface
With The help of SDN Contribution
link----
( have look on it)
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4943f2b7-0a01-0010-37af-faff35b2f08c
I am getting error in
Partner system as HTTPLOG and "Execute" to check the results
Error is -- Port could not be created
RFC destination HTTPLOG Not specified for system HTTPLOG
any 1 have any idea if plzzzzzzzz...........
Thank u
RamHello .
we are also in process of implementing the same
could you share the knowledge pl?
1)is it a separate add on with ALE to saphr
or using ECC ??
2)can u share the configuration part ??
we are trying it on webas as addon 3.0 . -
Business system for idoc reciver communication channel.
hi gurus,
iam doing one file to idoc scenerio.
for defining reciver idoc adapter ,which type of businees system i required that is configured in SLD.
pls guide me .
warm regards.Hi
You can use th Buiness system as a receiver for IDOC.
Making sure
1. the LS of the system(R/3) is same in the SLD and it is also reflecting in the adapter specific attributes in the ID.
2. Use the same LS name for the BS pointng to FIle in the SLD.
Complete the IDOC configuration from XI
1. Create the RFC dest from XI to ECC
2. Create the Trfc port and call this RFC dest created..
3. Use this Trfc port in the IDOC receiver
On ECC:
Make sure the Partner Profiles is created properly.
it is suggested to use always the business systems when you deal with IDOC and Proxies.
Edited by: Nisar Khan on Feb 27, 2008 1:31 PM -
File to multiple IDOCs scenario with the same receiver system
Hi guys,
I have to design and implement the following scenario:
I will receive one file with many lines (Records) with data for materials, quantities, operations etc..
Based on the values of some fields of each line, I will have to create an IDOC for each material.
For example:
if operation type = "INSERT", and Labor = 001 then create 3 Idocs of type MBGMCR with movement types=101, 261,311 that have to be posted one after the other to the same receiver system.
else if operation type = "INSERT", and Labor <> 001 then create an Idoc MBGMCR with movement type=311 and plant = 1001.
else if operation type = "Delete", and Labor = 001 the created 3 Idocs MBGMCR with movement type=312, 262 1002 and post them serially to the same receiver system.
else if operation type = "Delete", and Labor <> 001 the created 1 Idoc MBGMCR with movement type=312.
All IDOCS are posted to the same SAP R/3 system. We do not care about the sequence, except for the cases where 3 IDOCS are created.
I am trying to think of a good design in performance terms.
It is obvious that I will need BPM for sure.
I am thinking of creating a mapping program that will produce 4 message types for the different cases from the initial file and then create a different message mapping for each case from the message type to the IDOC.
I am asking you if I have to include everything (mappings) in BPM with a "fork" step?
Or shall I produce only the 4 message types and then post them to R/3 and execute the mappings in R/3?
Best Regards
Evaggeloshi,
>>I am thinking of creating a mapping program that will produce 4 message types for the different cases from the initial file and then create a different message mapping for each case from the message type to the IDOC.
To me this seems to be the right solution.
here u will create different message mappings and write them sequentially in interface determination. the multi mapping will then be utilised in transformation step in BPM.
thus if this is the only requirement there is no need of using a fork step.
[reward if helpful]
regards,
latika. -
Info IDoc received with status 8 in BI but Data available in source system
Hello Experts,
I am loading Budget Period (attributes) into PSA in BI.
Budget Period data Loading Issue : No data available while loading. But source system ie ECC has data in that data source
Data source: 0PU_BDGTID_ATTR
This is full load.
I checked that whether I am making any mistake during data selection. I could not find any issue. Message while loading data into PSA (Yellow Traffic light)
No data available
Diagnosis
The data request was a full update.
In this case, the corresponding table in the source system does not
contain any data.
System Response
Info IDoc received with status 8.
Procedure
Check the data basis in the source system.
Already looked this thread and googled also.
Re: IDoc received with status 8.
Check points:
sm58 - NO issue
BD87 in ECC (RSINFO Idoc status: 03) -sucessful
BD87 in BI (RSINFO Idoc status : 53)
ST22 - NO issue
sm37 - Job is successful (I could see Idoc no in ECC source system in Job log)
I am not sure if I am missing any thing.
Thanks
RanaHi all,
I've got exactly the same issue with several extractors. I'm inialising the Master Data in a all new system, in the Quality the loads succeeded but in Prod it failed.
For instance with the basic DataSource "0FUNCT_LOC_TEXT", I've made the following test:
RS3 (R/3) - > 0 data
ST22 -> no short dump
WE05 (Idoc) - > everything is ok
I reactivated the Datasource in R/3 (RSA5) and then deleted it and replicated it in BW but the same issue occured.
Any ideas?
Thanks
jak -
IDOC Tables with Errors Post System Refresh
Hi Everyone,
Is there any Report or other way through which one can get List of IDOC Tables with Errors Post System Refresh.
Thanks,
Regards,
- IshanHi,
While selecting the Infopackage to run the INIT load, it is taking me to the ECC login screen. Once i enter my credentials, its showing a dump with the message:
Short text of error message:
No RFC authorization for user XXXXX ( RSA8 ).
Long text of error message:
Technical information about the message:
Message class....... "RSAR"
Number.............. 051
Variable 1.......... "No RFC authorization for user XXXXX ( RSA8 )."
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Please advice.
Regards
sneha -
No Communication Idocs are creating with the tcode BD21 for ARTMAS
Hi,
I am executing BD21 for the message type ARTMAS to trigger the Article master change pointer idocs. Before executing it I have changed the Article message using the t.code MM42. After executing the BD21 it is only creating Master Idoc but not Communication Idocs. If any one have idea on this please help me.
Regards,
Vasu.Hi Jack,
change pointer configuration is ok for the message type ARTMAS. Also the MAKT-MAKTX is also there in the tcode BD52 for the message type ARTMAS. Once I change the material through MM42, I am able to see the entry in table BDCP2 but not in table BDCPS. I am able to trigger the idocs through BD10 successfully.
Regards,
Vasu. -
When I activate source system in BW, problem with IDoc (ZSBB027) occurs.
Hi,
I made some enhancing data source in R3 and when I would replicate and activate source system in BW, some error message occurs:
"Type IDoc ZSBB027 BW is not like IDoc in source system,
Incorrect IDoc ZSBA0003 in definition source system."
Can I find which data source is bad?
Thank You very much.Hi,
there is no need to activate ur Source system unless if there is any problem in ur Source system.
When ever u do some changes in ur data source then replicate that into ur BW by going into RSA1-> Source system-> right click , Replicate data source. later u can assign that to ur info source..
Once if u do the replication then u have to activate ur Transfer rules by executing RS_TRANSTRUE_ACTIVATE_ALL.
Hope it helps-
Regards-
MM -
Communication IDoc is not generating after master IDoc for "DEBMAS"
Hi gurus,
i have done all steps from the beginning to the end for an Idoc transfer of type "DEBMAS".I have created the settings in BD61,BD50 and BD52.And also i can work with other master message types like ARTMAS.I didn't give any filter groups in BD64 for the message type "DEBMAS".When ever i execute BD21(RBDMIDOC) only master idoc is generating,there is no communication idocs for the message type "DEBMAS".Please help someone in this issue.
My special question / doubt is, when ever a master idoc creating ,is it must to create a communication idoc ,if there is no filter in "DEBMAS"?
Please clear someone and explain my doubt.
your help will be highly appreciative...
rgds
tom
Moderator message: Please don't use all upper case in subject line
Edited by: Thomas Zloch on Feb 28, 2010 5:25 PMhi,
communication IDoc is missing when ...
- Distribution Modell is missing
- Filter in Distribution Model is existing an no IDoc is generated (Filter at KNA1M segment only)
try the following.
Goto BD12. Choose your partner and the receiving System and send an IDoc.
Is the Comm. IDoc generated ?
if yes ... there is something with your ChangePointer Logik (BD52, .... look at Table BDCP/V)
if no ... you should take a deeper look at BD64 distribution model.
Maybe the receiver partner or filter is not correct.
good luck,
Gordon
Edited by: Gordon Breuer on Feb 25, 2010 1:12 PM -
Difference b/w Master & Communication IDocs
Hi All,
What is the difference b/w Master & Communication IDocs.
Akshitha.The master Idoc is the Temporary Idoc & kept in memory buffers until communication IDocs are generated. These recipient-specific IDocs are called Communication IDocs and are Stored in the Database.
But the master Idoc is not.
The Communication IDocs are transferable IDocs not the Master Idoc. For every Receiver, each separate communication Idocs will be created from master Idoc.
more info on idocs....
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
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.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
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://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Check these links.
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.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
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
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
Regards
vasu -
What is memory idoc , communication idoc
plz tell me about
memory idoc , communication idoc.hi kalyan,
Master IDOC : This idoc collects all the required data into
single IDOC and this is temporarily stored in memory.
Communication IDOC: there can be n number of communication
IDOCs generated. This comes into picture after the Master
IDOC is validated from the distribution model . And this
IDOC is stored in database table . you can see this IDOC
from we02 tcode..comm idoc is the physical idoc which is reciever specific
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.
NEED FOR ABAP PROGRAMMING arises if
1)New IDOC was created
Depending upon the triggering mechanism i.e change pointer,message control
etc the programming technique changes and the type of process.
2)Existing IDOC was extended
User Exits are used to populate data in new segments added and to read them
back.
3)To enhance an exsiting process.
User Exits are used .
Basic structure of an OUTBOUND PROGRAM
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.
OUTBOUND PROCESS AND OUTBOUND PROGRAM
Outbound programs are used in outbound process to genearte IDOCs . There
purpose is to extract the data from the tables and to fill the IDOC data records
and the control record in the IDOC and pass ito the ALE layer for distribution to the recieving system .
Depending upon the triggering mechanism (how and when the outbound program will be started different techniques and interface is used for outbound program.
1)Message control
Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.
In outbound programs(function module) that use message control the key of the
application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the
message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.
The parameteers passed to the function module are
IMPORTING PARAMETERS
OBJECT LIKE NAST
It contains documents key.
CONTROL_RECORD_IN LIKE EDIDC
It contains the partailly filled control record
EXPORETING PARAMETER
OBJECT_TYPE
CONTROL_RECORD_OUT LIKE EDIDC
TABLES
INT_EDID LIKE EDIDD
The internal table used to fill the data records in the same order as they exists in
the IDOC.
The important parameters that should be filled in the custom function module are
CONTROL_RECORD_OUT and INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.
2)Stand alone programs
Generally used for Master Data transfer and as such depending upon the requirement can have different interfaces.The programs have a selection screen which has select options to select the objects, and parameters for specifying the recipient Logical System and the Message Type.
Data is selected based on the specified objects from the tables . and control record of type EDIDC is created and filled with important values like DIRECTION ,IDOCTP,RCVPRT,RCVPRN and MESTYP .
Data is filled in an internal table of TYPE EDIDD according to segment definitions
and in same order and the function module MASTER_IDOC_DISTRIBUTE is called passing the control record and the internal table containg IDOC data and importing an internal table consisting of control records for each communication IDOCS created.
3)Change pointer
Change Pointer table is read and checked if changes were made to important fields , if so the outbound program will be triggered automatically , these have predefined interfaces
thanks
abdul
reward me if usefull -
ALE distribution error - 0 communication IDOC
Hello,
We are getting 0 communication IDOC generated for message type DOCMAS error for ALE document distribution error. Please advice where to look for the error.
Anirudhhi,
ani,
u check this,
If you want work items to be created when errors occur for the purpose of error handling, you need to assign the standard task TS40007915 PCROLL to a position or a workflow organizational unit.
Or
You can also distribute dependent objects manually for classes. You can use report program RCCLDIHI to distribute a complete class hierarchy including all classes characteristics, and characteristic values.
Only the message code (004 - change) is allowed for sending a document (message type DOCMAS). This function also creates the document in the target system.
You can control the sending of documents with the indicator Distribution lock. An object with this indicator in its status will not be distributed into other ALE systems.
You can set the indicator in Customizing Document Management System Define document type Define status. The distribution lock is read when a distribution automatically starts after a change pointer is set or for an Integrated Distributed PDM Solution (ID PDM).
You can ignore this setting by starting the distribution manually. When you set the indicator Ignore distribution lock in the initial screen, then all documents will be distributed overriding the previously set status.
You control the distribution of object links with the indicator You cannot maintain the object links via ALE and Object link unchanged in target system.
Information about object links are distributed through IDoc type DOLMAS01.
The data is transferred to the workstation application and to storage data in IDoc type DOCMAS04 if an original file exists to a document. The Remote Function Call interface protocol transfers the contents of the original file, for example text or design drawing.
You can determine whether you want originals of a certain document type to be distributed by ALE into another system under the setting Document Management System Define document type Define transport of originals for ALE. You can control distribution with various criteria.
You want to distribute all original files of the application WRD (Microsoft Word) for the document type R-1 (report) that are stored in vault VAULT1 (Vault for Office Applications). You do not want to distribute documents of the same document type for the application WWI (Winword 6.0).
You can process the status for the desired objects.
1. Select in Customizing Cross Applications Components Distribution (ALE) Standard ALE Business Processes Logistics Master Data Distribution Integrated Distributed PDM Solution (ID PDM) Object status (for example, Define BOM status).
2. Process the indicator Distribution lock
ben -
Steps for connecting ext. system (nonSAP) via tRFC
Hi i need detailed description on how to connect ext. system (nonSAP) or program to XI.
I need a RFC-Destination - what type?! TCP/IP?!
Scenario will be that we send a receive IDoc from this nonSAP-System.
Can someone provide me with detailed informations?! Which user-type etc., do i need a user....?
brHi,
Assuming target system is your R3.
You need to follow the below 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 XI (transaction SALE)
Maintain Port (WE21)
Maintain partner profile for XI. (WE20):
This is just example you can see the configuration part:
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 -
Difference between Master Idoc and Communication Idoc.
Can anyone list out the difference between Master Idoc and Communication Idoc?
IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
Form and content: IDoc terminology
As is often the case with proprietary technologies, SAP assigns specific, object-oriented meanings to familiar terms. When referring to IDocs, the term document refers to a set of data comprising a functional group of records with a business identity. (For example, all the data in a purchase order, or all the profile information of a supplier in a supplier master record.)
A message refers to the contents of a specific implementation of an IDoc; its a logical reference. This differs from a reference to the IDoc itself, which specifies the messages physical representation. Think of it this way: If youre watching a parade pass by, the mayor waving to the crowd from his limousine is the message, and the mayors limousine (which is specific to the mayor) is the IDoc. Youre building a logical object, and the IDoc is both its container and the vehicle that moves it.
The IDoc control record
Each IDoc has a single control record, always the first record in the set. The structure of this record describes the content of the data records that will follow and provides administrative information, such as the IDocs functional category (Message Type/IDoc Type), as well as its origin (Sender) and destination (Receiver) as in conventional EDI
Layout of an IDoc control record
This cover slip format informs the receiving system of the IDocs purpose, and the receiving system uses it to determine the correct processing algorithm for handling the arriving IDoc.
Data records
The data records following the control record are structured alike, including two sections: a segment information section and a data section.
In the first part of a data record, the segment information section describes the structure of the data that follows, for the benefit of the IDoc processor. There is a segment name (like an EDI segment identifier) that corresponds to a data dictionary structure to which the IDoc processor has access. The remaining information is useful for foreign systems, such as a partner companys Oracle system, which has no such data dictionary.
The second part of the record is the data itself, a storage area of 1,000 characters.
Status records
If youve ever ordered a package from a faraway location and tracked its progress using the Internet-based tracking utilities now provided by most major parcel carriers, youre familiar with the list of stops and transfer points through which a package passes on its way to you.
This collection of records is exactly what youll see in an IDoc that has begun its work. Following the data records in an IDoc, status records accumulate as an IDoc makes its way from one point in a process to another.
Typically, an IDoc will acquire several of these records as its does its job. They are simple records, consisting of a status code (there are more than 70 codes, covering a broad range of conditions and errors), a date/time stamp, and some additional status information fields for system audit purposes. In addition, as errors occur in the processing of an IDoc, status records are used to record these errors and the date/time of their occurrence.
IDoc Base
IDocs, as data formatting tools, enable the easy sharing of data between databases and applications within a company as well as being an efficient data courier between companies. Typically in SAP, a database of IDoc definitions exists, to which any application may have access.
This IDoc Base gives all the applications and processes in your company domain the capacity to send, receive, and process a document in a contextually appropriate way, without doing anything to the data. For example, a purchase order IDoc can filter through every process it touches, passing from system to system, accumulating status records to track its progress.
Every department using the data can use it appropriately without any cumbersome intermediate processes, because each department draws its key to interpreting the IDoc from the same source.
Multiple messages
One cumbersome feature of conventional EDI is the embedding of more than one functional record type in a document. The unwieldy X-12 888 Item Maintenance transaction set is an example: It purports to handle so many different configurations of product master data that it is horrifically difficult to integrate into an existing system.
IDocs, on the other hand, handle multiple messages with ease. Given the centralized IDoc interpretation that SAP provides to all its parts, its no problem to define an IDoc that will contain more than one message, that is, more than one data record type.
A customer master IDoc, for example, may contain customer profile information records for a customer with many locations. But it may also contain location-specific pricing information records for that customer in the same document. This is an incredibly efficient way of bundling related records, particularly when passing large amounts of complex information from system to system Records in a multiple-message IDoc
Maybe you are looking for
-
MSS Approval Report Links to Busines Workflow Task in UWL
Hello All, I have a scenario below that I'm hoping you can help. I copied the standard business workflow task "TS31000007: CATS Approval by Supervisor" to create our own task (general task) and link the 'CatManagerApprove' application and 'sap.com/ms
-
I've been reading a previous post (which is now locked) regarding the 100GB useage limit. In this the moderators have mentioned some form of online useage monitor - which I have to search for myself. In my household we have 4 computers (occasionally
-
Faulting module quicktimestreaming.qtx
I have a workstation where I work getting an eventlog error and is causing Internet Explorer version 7.0.6000.16735 to crash. It says "Faulting application iexplore.exe, version 7.0.60000.16735, faulting module quicktimestreaming.qtx, version 7.55.90
-
does anyone know how you can preset the width of your page when you open a document? it's a bit irritating to fix it every time you open a document.
-
PCA substituion for Sales Order
Hi, Our requirement is to create the sales order substition for the followins For each region different PCA values, we have 20 regions. Can you please tell us how to achieve this through substituion. Thanks,