08-01-2006 9:27 PM
Hello all,
Can somebody send me documentation over Idoc interfaces? I need for Inbound now...but Outbound will be helpful though for future use )
And I have a question related to middleware too. A flat file will be the input to middleware (XI or webmethods). What is the output? Is it an IDOC format file or IDOCS with status 64 in SAP?
Thanks,
Message was edited by: Somen
08-01-2006 9:41 PM
Hi,
For inbound idoc in partner profiles if you set trigger immediately for a message type , whenever idoc comes from middleware , it will be processed automatically . for process success idoc status will become 53, if it is failed idoc status becomes 51.
at partner profiles if idoc process selected as process through background program , whenever idoc comes from middleware it goes to 64 status. for these idoc's we need to schedule RBDAPP01 program to process 64 status idoc's or we can process these idoc's from BD87 transaction
Check these links:
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/72/c18eff546a11d182cc0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/9c/2744f5fa7464429a13345be4050fb6/frameset.htm
http://www.sappoint.com/ppt/ale.ppt
below details might help you.
WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
WE05 View IDocs
WE19 EDI test tool. Use to test inbound Function module changes.
WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing
WE30 Create IDoc extension type
WE31 Segment create
WE57 Assign function module to logical message and IDoc type
WE60 IDoc type documentation tool
WE82 Link Release detail to Extension IDoc Type
BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations
BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
BALA ALE Application Distribution
BALM ALE Master Data Distribution
WEDI - main transaction for all ALE settings
Regards
Appana
*Award Points for helpful answers
08-01-2006 9:32 PM
Hi,
Please refer to this link :
<b>http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7e6c43d711d1893e0000e8323c4f/content.htm</b>
Regards,
Varun .
08-01-2006 9:39 PM
Hi Somen,
Please check this links for online documents.
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/printdocu/core/Print46c/en/data/pdf/SDEDI/SDEDI.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESIDOCXML/BCFESIDOCXMLSTR.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDED/BCFESDED.pdf
And I have a question related to middleware too. A flat file will be the input to middleware (XI or webmethods). What is the output? Is it an IDOC format file or IDOCS with status 64 in SAP?
Generally the output will be in IDoc format but you can also create an IDoc file as well. If you setup the partner profile to trigger by background job then the IDoc will be in status 64 and you need to run program RBDAPP01 to post the IDoc to application. Otherwise, the IDoc will be posted automatically to application when XI sends to R/3.
For an IDoc file, you need to run program RSEINB00 in order to process the file and generate IDocs.
Hope this will help.
Regards,
Ferry Lianto
08-01-2006 9:41 PM
Hi,
For inbound idoc in partner profiles if you set trigger immediately for a message type , whenever idoc comes from middleware , it will be processed automatically . for process success idoc status will become 53, if it is failed idoc status becomes 51.
at partner profiles if idoc process selected as process through background program , whenever idoc comes from middleware it goes to 64 status. for these idoc's we need to schedule RBDAPP01 program to process 64 status idoc's or we can process these idoc's from BD87 transaction
Check these links:
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/72/c18eff546a11d182cc0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/9c/2744f5fa7464429a13345be4050fb6/frameset.htm
http://www.sappoint.com/ppt/ale.ppt
below details might help you.
WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
WE05 View IDocs
WE19 EDI test tool. Use to test inbound Function module changes.
WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing
WE30 Create IDoc extension type
WE31 Segment create
WE57 Assign function module to logical message and IDoc type
WE60 IDoc type documentation tool
WE82 Link Release detail to Extension IDoc Type
BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations
BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
BALA ALE Application Distribution
BALM ALE Master Data Distribution
WEDI - main transaction for all ALE settings
Regards
Appana
*Award Points for helpful answers
08-01-2006 10:09 PM
hi
give me ur email id.i will send you a good document..
Cheers,
Abdul Hakim
08-01-2006 10:17 PM
08-01-2006 10:23 PM
08-01-2006 11:19 PM