![]() ![]() An IDoc for Every Interface. A common request often voiced on list groups and other professional forums is for a standard cross- reference between SAP IDocs and EDI transaction sets and messages. Over the years I've seen some spreadsheets that link IDocs to X1. I've built my share of IDoc to EDI cross- reference spreadsheets that meet the needs of a particular project. But here's the rub. There's no official standard cross- reference out there. You can literally map anything to anything. IDocs and EDI transactions are only data structures, after all. The key is what do you do with their data in the backend SAP system at your site. SAP provides archiving programs and deletion programs for several. Miscellanous Tips part 1. Usefull standard programs. Use program RSNAST00 to process the IDOCs. Sap r/3 /sap crm/sap edi/ale/idocs/abap/4/fi/sd/mm/pp user exits/badi. You can use the below Programs for IDocs. Writes IDocs to the archive. SAP Community Network. This is what the business process is all about. SAP sends and receives IDocs. But SAP is generally introduced into an environment where EDI is already being used. So the EDI transactions have been already agreed to with the trading partners and are already being used in legacy. ![]() The key is ensuring that you select IDocs that meet the data requirements of the business process designed in your SAP system and then figuring out how to map them to your existing, and any new, EDI transactions or messages. In other words, like everything else you do in SAP, you need to understand the underlying business process before you can select the appropriate IDoc to map to EDI. The business process drives everything. Urgent Assistance Requested SAP/IDOCS Schema Generation. IDOC XML schema generated by the adapter is not an SAP standard. Sticking to a phantom “SAP standard” for IDocs, which does not actually exist in R/3. Step-by-step guide to ALE and IDOCs. 3.Idoc is transferred from SAP to. TO Process IDOCS the following. SAP Standard for E2E Solution Operations. IDocs, qRFC, or XI/PI. On the inbound, that means understanding what document the IDoc creates when it hits SAP and what data that document needs. On a deeper technical level, that means knowing the code, the processing function and the create transaction that the IDoc calls to create the business document. The EDI team may not need to know this, but somebody on the SAP team does. This knowledge drives the mapping requirements. On the outbound, it's all about the business document that generates the IDoc and the configuration and/or code needed to collect the application data and output the IDoc. In general, but not always, virtuall all the data in a business document is sent in an outbound IDoc. This data must then be matched up to the EDI data that is being sent to the trading partner by the legacy system. A Team Effort. The key take- away in all this is that it's not just about about mapping messages and transactions. It's about how the data being exchanged is processed and consumed in SAP and by the trading partner. Selecting the correct IDoc to map is a team effort that requires both EDI and SAP skills and input. If you understand these pieces, and if you know what EDI transactions or messages you need to exchange with your trading partner, you can make an intelligent decision about what IDocs to use, assuming you got out of the right side of your bed that morning or that you don't have a hang- over or some other self- inflicted malady. Having said all that, there are some commonly accepted pairings between IDocs and EDI transaction sets and messages. So I consulted a few sources and came up with a starting point cross- reference for inbound and outbound interfaces. I began with two OSS Notes from the SAP Support Portal: 1. IDocs to X1. 2 transaction sets and 1. IDocs that are commonly used in EDI. I also consulted ERP Genie which has a very useful SAP EDI portal with a number of spreadsheets that map IDocs to different EDI standards. Then I dug through some IDoc tables and code in SAP, ransacked my own experience and knowledge, such as it is, tweaked a little here, a little there, and came up with a mapping that I hope you find useful. I used the most recent IDoc versions wherever appropriate, confirmed by consulting SAP. I'm a firm believer in using the latest IDoc versions. Some of these choices are arbitrary and some you may not agree with. Some pose design issues that some may not want to pursue. Message type TXTRAW, for example, can be mapped to any EDI text report. But would you want to do it? TXTRAW formats a text message that is distributed through SAPOffice email. I normally handle these kinds of interfaces in the EDI subsystem, by designing a report with a map and attaching it to an email sent through the regular email system. But you never know what opportunities circumstance will throw your way. If you have any additions to this mapping, or if you object strenuously to some of these choices, I'm all ears. Feel free to comment or to send me an email. One last point: this mapping is IDoc centric because SAP is the business system of record. We begin with the IDoc and map its associated EDIFACT messages and X1. It could just as easily be displayed from the EDI perspective. So without further ado, Odysseus is pleased to present this preliminary SAP IDoc to EDI mapping. Enjoy. Inbound Interfaces. Msg. Type. Basic. Type. Description. EDIFACTX1. 2ACLPAYACLPAY0. Freight invoice. INVOIC2. CREADVPEXR2. 00. 2Credit advice. CREADV8. 12. CREADVPEXR2. Extended credit advice. CREEXT8. 12. CREADVPEXR2. Multiple credit advice. CREMUL8. 12. CREMASCREMAS0. Vendor/Org info. PARTIN8. DEBADVPEXR2. 00. 2Debit advice. DEBADV8. 12. DEBADVPEXR2. Multiple debit advice. DEBMUL8. 12. DEBMASDEBMAS0. Customer/Org info. PARTIN8. 16. DELFORDELFOR0. Delivery schedule. DELFOR8. 30. DELINSDELFOR0. Delivery schedule. DELFOR8. 30, 8. 62. DELJITDELFOR0. 1Just in time delivery. DELJIT8. 30, 8. 62. DELORDORDERS0. 5Delivery request. ORDERS8. 30, 8. 50. DESADVDELVRY0. 3Delivery (Despatch Advice)DESADV8. DIRDEBPEXR2. 00. 2Direct debit. DIRDEB8. 28. DIRDEBPEXFI0. Direct debit. DIRDEB8. FINSTAFINSTA0. 1Financial statement. FINSTA8. 21, 8. 22. GSVERFGSVERF0. 3Credit memo procedure. ORDERS8. 61. IFTMINSHPMNT0. Forwarding order. IFTMIN2. 04, 3. 04. INVOICINVOIC0. 2Vendor Invoice. INVOIC8. 10, 8. 80. LOCKBXFINSTA0. 1Lockbox. PAYORD8. 23. MBGMCRMBGMCR0. Post Goods Mvmt & PGI Del. RECADV8. 56, 8. 67, 9. MBGMCRMBGMCR0. 3Goods Mvmt & Goods Receipt PORECADV8. ORDCHGORDERS0. 5PO Change Request. ORDCHG8. 60, 8. 76. ORDERSORDERS0. 5Customer POORDERS8. ORDRSPORDERS0. 5PO confirm. ORDRSP8. 55, 8. 65. PAYEXTPEXR2. 00. 2Extended payment order. PAYEXT8. 20. PAYEXTPEXR2. Multiple payment order. PAYMUL8. 20. PAYEXTPEXR2. Payment order. PAYORD8. PROACTPROACT0. 1Inventory Report. INVRPT8. 46, 8. 52. PROACTPROACT0. 1Sales forecast. SLSFCT8. 52. PROACTPROACT0. Sales report. SLSRPT8. REMADVPEXR2. 00. 2Credit advice. CREADV8. 20. REMADVPEXR2. Payment advice. REMADV8. REQOTEORDERS0. 5Response to request for quotation. REQOTE8. 40. SDPICKSDPIID0. Pick/Ship confirm & PGIRECADV8. SHPADVSHPMNT0. 5Advanced Ship Notification. SHPMNT8. 56. SHPCONDELVRY0. Ship confirm/PGIRECADV8. SHPMNTSHPMNT0. 5Advanced ship noticifaction. SHPMNT8. 56. SHPORDDELVRY0. Delivery despatch order. DESADV8. 30, 8. 50, 8. STATUSSYSTAT0. 1Acknowledgement. CONTRL9. 97. STATUSSYSTAT0. Functional acknowledgement. FUNACK9. 97. TXTRAWTXTRAW0. Error report (text msg)APERAK8. TXTRAWTXTRAW0. 2Error report (text msg)GENRAL8. WHSCONDELVRY0. 3Stock confirmation & PGIRECADV8. WHSORDDELVRY0. 3Delivery stock order. DESADV9. 40. WMTORDWMTOID0. Transport request (goods movement)RECADV8. WMMBXYWMMBID0. 2Post goods receipt (goods movement)RECADV8. Outbound Interfaces. Msg. Type. Basic. Type. Description. EDIFACTX1. 2 Txn. BENREPBENEFIT3. Benefit enrollment. N/A8. 34. CREMASCREMAS0. Vendor/Org info. PARTIN8. DEBMASDEBMAS0. 6Customer/Org info. PARTIN8. 16. DELFORDELFOR0. Delivery schedule. DELFOR8. 30. DELINSDELFOR0. Delivery schedule. DELFOR8. 30, 8. 62. DELJITDELFOR0. 1Just in time delivery. DELJIT8. 30, 8. 62. DESADVDELVRY0. 3Delivery (Despatch Advice)DESADV8. DESADVDELVRY0. 3Delivery (Despatch Advice)IFTMIN8. EXPINVEXPINV0. 4Export invoice. INVOIC8. 10, 8. 80. IFTMINSHPMNT0. 4Forwarding order. IFTMIN2. 04, 3. 04. IMPINVIMPINV0. 1Import declaration. CUSDECN/AINVOICINVOIC0. Customer Invoice. INVOIC8. 10, 8. 80. MATMASMATMAS0. 5Material master/product data. PRODAT8. 32. ORDCHGORDERS0. PO Change Request. ORDCHG8. 60, 8. 76. ORDERSORDERS0. 5Vendor POORDERS8. ORDRSPORDERS0. 5PO Response. ORDRSP8. 55, 8. 65. PAYEXTPEXR2. 00. 2Extended payment order. PAYEXT8. 20. PAYEXTPEXR2. Multiple payment order. PAYMUL8. 20. PAYEXTPEXR2. Payment order. PAYORD8. PRICATPRICAT0. 2Price/Sales Catalog. PRICAT8. 32, 8. 79, 8. PRICATPRICAT0. 2Product data. PRODAT8. 32, 8. 79, 8. PROACTPROACT0. 1Inventory Report. INVRPT8. 46, 8. 52. PROACTPROACT0. 1Sales forecast. SLSFCT8. 52. PROACTPROACT0. Sales report. SLSRPT8. QUOTESORDERS0. 5Quotation. QUOTES8. 43. REMADVPEXR2. Credit advice. CREADV8. REMADVPEXR2. 00. 2Debit advice. DEBADV8. 20. REMADVPEXR2. Payment advice. REMADV8. REQOTEORDERS0. 5Request for quotation. REQOTE8. 40. SHPADVSHPMNT0. Advanced Ship Notification. SHPMNT8. 56. SHPCONDELVRY0. Ship confirmation. RECADV8. 56, 8. 67, 9. SHPMNTSHPMNT0. 5Advanced ship noticifaction. SHPMNT8. 56. SHPORDDELVRY0. Delivery despatch order. SHPORD8. 30, 8. 50, 8. SHPORDDELVRY0. 3Delivery despatch order. DESADV9. 40. SYIDOCSYIDOC0. EDI/IDoc Guidelines Defintion. IMPDEFN/ASYRECDSYRECD0. EDI/IDoc Guidelines Defintion. IMPDEFN/AWHSCONDELVRY0. Stock confirmation. RECADV8. 56, 8. 67, 9. WHSORDDELVRY0. 3Delivery stock order.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
October 2017
Categories |