sanv20z2 19:10 IDoe Basics For Functional Consultants | SAP Blogs Community © SAP Community - Planned Downtime x There will be a 2-hour planned downtime on Sunday, November 20 from 10 am CET (4 am ET) to 12 pm CET (6am ET). Some services may not be available during this time, Please save your work, Aska Question Write a Blog Post Niranjan Nagle December 31,2012 | 12 minute read IDoc Basics For Functional Consultants Flsi5 hes © 845,886 Like ABSTRACT Today IDocs are used in most SAP applications for transfer of message(information) from SAP system to other systems and vice versa. Though lot of documentation is available on IDocs it is difficult for a functional consultant to understand such documents due to their technical nature. While a functional consultant is not expected to know the IDoc concepts in its entirety, an effort has been made to capture the minimum necessary information that one needs to be aware of in order to handle project/support issues on IDocs. BV RSS Feed hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 1189sanv20z2 19:10 'Doe Basics For Functional Consultants | SAP Blogs OVERVIEW IDoc is an SAP object that carries data of a business transaction from one system to another in the form of electronic message. IDoc is an acronym for Intermediate Document. The purpose of an IDoc is to transfer data or information from SAP to other systems and vice versa. The transfer from SAP to non-SAP system is done via EDI (Electronic Data Interchange) subsystems whereas for transfer between two SAP systems, ALE is used. IDoc can be triggered in SAP system or in EDI subsystem. This depends on the direction in which |Doc is sent and is called as Inbound IDoc and Outbound |Doc accordingly. In case of outbound flow, IDoc is triggered in SAP through document message control which is then sent to EDI subsystem. EDI converts the data from IDoc into XML or equivalent format and then sends the data to partner system through Internet. For inbound flow, EDI converts partner data and IDoc is created in SAP, After successful processing of this IDoc, Application Document is posted in SAP. < INFORMATION FLOW INBOUND INFORMATION FLOW OUTBOUND > EDI STANDARDS AND IDOC “EDI is electronic exchange of business document between the computer systems of business partners, using a standard hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 2139sanv20z2 19:10 1boe Basics ForFurconal Cnsutanis| SAP Blogs format over a communication network’. EDI stands for Electronic Data Interchange. For transmission of information electronically, two widely used standards are ANSI ASC X12 and EDIFACT. ANSI ASC X12 is a committee formed by representatives of major organizations, government bodies and EDI software companies which defines standards and guidelines for information interchange over EDI. UN/EDIFACT stands for United Nations EDI for Administration, commerce and Transport and was formed in 1985 using ANSI X12 and UNTDI (United Nations Trade Data interchange) as base standards. ANSI X12 describes business document as transactions and each transaction is represented by three digit number e.g. 850 — Purchase Order, 855 — Purchase Order Acknowledgement. EDIFACT describes business document as messages, represented by standard names e.g. ORDERS for purchase order. IDOC TERMINOLOGIES IDOC (BASIC) TYPE IDoc Types are based on the EDI standards and mostly on EDIFACT standards. Basic Types (or IDoc Type) defines the structure of an IDoc. Each basic type describes standard IDoc segments, format of data fields and their size. Basic Type also defines number of segments and fields in an |Doc. All the fields that are necessary for transmission of message for a particular business transaction are mapped in different segments. It also defines the structure and relationship of IDoc segments along with mandatory and optional segments. hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 3139)sanv20z2 19:10 'Doe Basies For Functional Cons Basic Type: ORDERSOS: SAP Blogs: ORDERSOS Purchasing/Sales E1EDKO1 \Doc : Document Header General Data E1EDK14 {ce : Document Header Organizational Data E1EDKO3, 1Ooe : Document Header Date Segment —— E1EDKO4 'Doe : Document Header Taxes E1EDKOS, {Ove : Document Header Conaitons (© |ENEDKA1 {00e : Document Header Partner information E1EDK18, 100: Document Header Terns of Payment (©) (EAEDPOt. "Doc: Document tem General Data E1EDPO2 \Oce : Document item General Data E1CUREF (CU. Reference order tery instance mn contiguration ~~ E1ADDIt (0: Adcbonals E1EDPO3 'Do« : Document fem Date Segment E1EDPOS \Ooe : Document item Taxes, E1EDPO5, 'Ooe : Document item Conations ——— E1EDP20 \Ooe Schecie Lines IDOC EXTENSION Basic type contains all the standard fields that are necessary for carrying out a business transaction. However, if any additional values are to be sent to the partner then we can make use of the IDoc Extension feature. IDoc extension is extension of basic type and contains additional custom IDoc segments and fields that are not available in standard basic type. IDOC SEGMENTS IDoc segments contain the actual data that is sent to or received from a partner. These segments contain the actual values that are sent as part of IDoc transmission. E1EDPO2 <= IDOC Segment Field Name | Field Value WwENG [1 AMENG [0 EDATU 20120909 hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 439,sanv20z2 19:10 IDoe Basics For Functional Consultants | SAP Blogs PARENT AND CHILD SEGMENTS IDoc segment is termed as Parent segment if it contains its own segments. The dependent segments are called as child segments. -}— E1EDP01 (=== Parent Segment ~~ E1EDP02 E1CUREF , Child Segments ~~ E1ADDI1 E1EDP03 INBOUND/OUTBOUND IDOCS IDocs sent outside the system are termed as Outbound IDocs and the ones that are received into the system, are called as Inbound IDocs. (eeveins-reaeoae-an > SAP RIS. OO -hta rr Anweene SSSA IDOC DIRECTION This signifies the direction is which information is sent and is similar to terminology used in mails. If information is sent outside the system then the direction is outbox when it is received into the system then direction is inbox. In SAP Outbox direction is represent by “1” i.e. outbox and Inbox direction is represented by “2”. SAP R/3. ‘ PARTNER PARTNER hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 539)sanv20z2 19:10 Doc Basics For Functional Consultants | SAP Blogs Partner is the Business Partner with which the exchange of information is to take place using |Doc. It can be a vendor or customer or any other system. Depending on the direction of information in which the information is sent it plays a role of either a “sending partner” or a “receiving partner’. p PARTNER TYPE Partner type/role is used to identify partners within the sap systems. Partner type is KU for customer, LI for vendor and LS for Logical System. MESSAGE TYPE Doc processing involves transmission or receipt of document in the form of a message, each of which represents a document in SAP. These documents can be Order, Shipment Confirmation, Advance Shipping Notification, Goods Receipt, or Invoice. Message type is associated with Basic IDoc Type (Basic Type) and defines the kind of data or document that is exchanged with the partner. hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 339sanv20z2 19:10 IDoe Basics For Functional Consultants | SAP Blogs PROCESS CODE The process code contains the details of the Function Module that are used for [Doc processing. Message Type can be linked to the Process code PORT IDoc Port contains the information about the way data is sent between the source or target system. The type of port defines the information contained within the port. For port type “Internet” Port will contain IP address of the target system. For port type “file”, directory or file name information is maintained. “tRFC” port contains information about the RFC destination of the target system. For IDoc transmission using ALE “tRFC” ports are used. PARTNER PROFILE MAINTENANCE PARTNER PROFILE (WE20) Partner profile must be maintained for all the business partners to whom we want to send or receive the IDocs. The TCODE for maintaining the partner profile is WE20. Partner profiles 24) ty | EI) Partner Description 2 Partner Profiles D CyPartnerTypeB Bank CaPartner Type BP Benefits provider CaPariner Type GP Business Partner > GyPartner Type KU Customer b GyPartner Type LI Vendor GyPartner Type LS Logical system GaPariner Type US User (first 10 characters, no Double clicking on the Partner will show the following screen: hitps:ologs.sap.com/2012/12/81idoc-basics-fr-unctional-consutants! 7139)sor12022 19:10 Doe Basics For Functional Consults | SAP Blogs JOXXXXXKC | XYZ uo Post processing: permitted agent Ty. & Position Agent SOOXXXXX/ EDI Technical Errors Lang. EN English |ORDCHG. CIC 4) Partner profile contains parameters for Inbound and Outbound processing of IDocs. For each message type we can maintain, inbound/outbound options, message control, post processing options and contact information within Inbound and outbound parameters. OUTBOUND OPTIONS (OUTBOUND PARAMETERS) This involves sender/receiver port, Output mode and relation to |Doc type i.e. Basic Type and extension. hitpsologs.sap.com/2012/12/81fdoc-asics-frfunctional-consutans)sanv20z2 19:10 Doe Basics For Functional Consultants | SAP Blogs Partner profiles: Outbound parameters AQOODOXX Transactional REC Pack. Size 250 Dhoueve Processing Ouiput Mode ‘© Tranafer Doc trimod, © Collect IDocs ‘Tee Type Basic type ‘RDERSO eoneeeen ZXXXXX View iGencel Processing After Syntax Error ‘S09. reiaasein Dee type ‘Segment Apol. Rel. MESSAGE CONTROL (OUTBOUND PARAMETERS) This contains application for which |Doc will be created e.g. EF for Purchase order, the message type of the application that will trigger the IDoc and Process Code that will convert SAP document to an IDoc. For example, if PO is to be sent to the Vendor AXXXXZ, then in the outbound option of the partner AXXXXZ we need to maintain the message type ZXX1 and link it to the Process Code ME10. So when message type ZXX1 is triggered in the PO then an IDoc will be created for the partner vendor AXXXXZ. Process Code is linked to the Function Module in SAP that converts application data into an IDoc. Standard function modules are provided by SAP for this conversion however these can also be customized as per business needs. hitpsologs.sap.com!2012/12/31fdoc-asics-forfunctional-consutants) 9139)IDoe Basics For Functional Consultants | SAP Blogs sanv20z2 19:10 ® Application: EF Purchase Order © Message Type: ZXK1: PO for Vendor 'H Process Code: E10: ORDERS: Purchase order ‘Change message ‘Application |_ Message type _]. Process code ZXX1. hero = LS [<)>] Change Message Indicator indicates whether the [Doc is sentas a notification of change. For example, Purchase Order change messages are sent to vendor using EDI standard message type 860. & Application EF : Purchase Ordor © Message Type: --ZXX1: PO for Vendor F Process Coe: = ME1O. Separate message type should be triggered in the purchase order for PO change. Additional line with change message type must be added in the Message control tab with change message indicator on. hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 10139sanv20z2 19:10 IDoe Basics For Functional Consultants | SAP Blogs Display View "Process Codes, Outbound": Details 4 | > |B) B Ver. List| (@ Processing with ALE service rocessing wo ALE service © Processing w. trigger (inbound) INBOUND OPTIONS (INBOUND PARAMETERS) For inbound options process code is maintained in the Inbound screen only. IDoc processing can be triggered by background program and triggered immediately. Process cade ESA Detvey ave DESADV Wn D 1ZicanelProcesting Aer Sys Eno Tigger by background program Tigger immeckatey POST PROCESSING (INBOUND/OUTBOUND PARAMETERS) In the post processing option we can maintain the workflow details of the users or positions to which an error notification will be sent if an IDoc processing fails. hitpsologs.sap.com!2012/12/81idoc-asics-frfunctional-consutants/ 11189sanv20z2 19:10 IDoe Basios For Functional Con _ Outboune Options | Message Control | CLI) Ty. s & Postion Agent SHORE Test User Lang EN English TELEPHONY (INBOUND/OUTBOUND PARAMETERS) We can also maintain the contact details in the telephony option. _// Post Processing: Permitted Agent | ‘Telephony | EDI Standard “Telephone No. Country Key Name Company EDI STANDARD (OUTBOUND PARAMETERS) EDI standard screen contains the details of the Standard EDI terminology used for the IDoc transmission. _7/, Post Processing: Permitted Agent | Telephony | ED/ Standard | EDI Standard x Message type 850 Version 08010 For example, Message Type 850 is an EDI standard for Purchase Order IDoc and is linked to IDoc Message Type Orders. IDOC STRUCTURE AND RECORDS STRUCTURE |Doc structure is divided into Control Record, Data Records and Status records. hitps:fologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 1289sanv20z2 19:10 IDoe Basios For Functional Con SAP Blogs: IDoc display ‘SF E{VIDoe o00000xxxxxxxx1 B contro! Rec. D @)Data records Total number: 000051 b> (Status records These records are stored in the transparent tables in SAP. These are EDIDC, EDID4 and EDIDS. CONTROL RECORD (EDIDC) It contains information such as IDoc number, direction, IDoc Status, Basic Type, Message Type, Partner (Sender/Receiver), date and time of creation/update, Interchange File or ISA number,etc. hitps:fologs.sap.com/2012/12/81idoc-basics-fr unctional-consutan's! 13399112022 19:0 Doc Basics For Functional Consultants | SAP Blogs Display Control Record Doe Display TEST Test Inbound Port Partner Number = RECEIVER hitpsologs.sap.com!2012/12/81fdoc-asics-frfunctional-consutans/ 14139sanv2022 19:10 Serialization UXXXXXXXXL Time of creation Date 19.08.2012 Time 00:22:31 Last database update Date 19.08.2012 Time 04:44:40 Interchange File ABCDEFGH Message Group ABCDEFGH Reference 0001 Identification EDI Options 7 Standard uy Version 00401 Message Type DATA RECORD (EDID4) It contains the details of the [Doc segments. hitps:fologs.sap.com/2012/12/81doc-basics-fr unctional-consutants! 1539sanv20z2 19:10 Doe Basics For Functional Consultants | SAP Blogs © Control Rec. &Data records Total number: 000009 Segment 000001 ‘Segment 000002 ‘Segment 000003 ‘Segment 000004 ‘Segment 000005 Segment 000006 Segment 000007 Segment 000008 ‘Segment 000009 Db G)Status records IDoc segment has fields that contain the data necessary for posting the documents. ‘Total number: 600000 ‘Segment 000001 ‘Segment 000002 ‘Segment 000003, ‘Segment 000004 ‘Segment 000005, ‘Segment 000006 ‘Segment 000007 ‘Segment 000008, Segment 000008 hitps:fologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 16389sanv20z2 19:10 IDoe Basis For Functional Consultants | SAP Blogs Doe dspiay > Doe 000000xXXKKAXT ‘Towa number: 090008 ‘Segment 000001 ‘Segment 000002 ‘Segment 000003 ‘Segment 900006 ‘Segment 900005 ‘Segment 000006 ‘Segment 000007 ‘Segment 000008 ‘Segment 000009 STATUS RECORDS (EDIDS) IDoc Status defines the processing status of the IDoc. IDoc statuses are used to track the IDoc and its various processing states. Status Numbers represents IDoc status. Current status of the IDoc is present in Control record. Dicontoirer, > Capa recores “ote runtber 000000, 1S Gsuusrecows ros ‘Aopsication document posi B Purchasing ounent OX030041 suecessuly processed ons {0s passed to appicaton D Drecteat surwa 2 oe {Doe recy tbe tarstere tb eppicaton B fio hers No convenien No version change. Qs loo asa Initial Status numbers are 64 for inbound and 03 for outbound. Successful status is 53 for inbound and 16 for outbound |Docs. hitpsologs.sap.com!2012/12/81fdoc-asics-frfunctional-consutans/ 17139sanv20z2 19:10 IDoe Basics For Functional Consultants | SAP Blogs SENDING AND RECEIVING IDOCS TRIGGERING AN OUTBOUND IDOC Outbound |Docs can be triggered from the output message types of Purchase Orders, deliveries, Material Documents, invoices, etc. The following figure shows that once the output ZXX1_ of PO XXXXXXX1_ is processed an Doc “O00000XXXXXXXXX1" is added/created. The relationship between the IDoc and the application document can be found in two ways: 1. Relationship tab of IDoc Attachment list Private note ” tal number: 000088 Help for object services *C+F hitpsologs.sap.com!2012/12/81fdoc-asics-frfunctional-consutans/ 1839sanv20z2 19:10 IDoe Basies For Functional Consultants | SAP Blogs pplication Object or OulboundID9e Purchasing Doc | xxXXXKNXA | 01.01.2013 01.0929 2. Relationship tab of Application Document, e.g. PO, SO, Material Document, etc, {@2] NB - Standard PO "Document Overview On || DY a9 | & ‘ye NBNB Standard PO, The initial status of this IDoc will be 30, which after successful processing will convert into status 16. 2 GiDoc O0COOOXXXXXXXXL b (Data records Total number: 000029 Status records Bie Functional Acknowledgement positive @12 Dispatch OK Bios Translation OK Bis Triggering EDI subsystem OK b Bos Data passed to port OK b B30 IDoc ready for dispatch (ALE service) Boa IDoc generated A successful outbound |Doc will pass through all the above statuses in reverse order (01-03-18-06-12-16). Each status represents an IDoc validation step. If an IDoc passes all the validations it would reach status 16. These different validation steps for outbound IDocs are explained below: 01: IDoc generation successful 30: IDoc is ready to be processed by IDoc Processing job hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 19139sanv20z2 19:10 'Doe Basics For Functional Consultants | SAP Blogs 03: IDoc data is passed to the Port 18: IDoc successfully triggered EDI subsystem 06: IDoc data translated to EDI format 12: IDoc is dispatched successfully to the partner 16: Partner has received the IDoc successfully IDoc can possibly fail at any of the above steps during validation. RECEIVING AN INBOUND IDOC The initial status of an inbound IDoc is 64 and successful status is 53. Different validation steps for inbound IDocs are explained below: 50: IDoc received successfully in the system 64: IDoc is ready to be processed by IDoc processing job 53: Application document created and saved successfully. The document number can be found by expanding the status node 53, !Doc display SEY WDoe O0G0G 0K KKK “Gy Conitroi Rec: D Data records Total number: 000009 & Status records > B53 Application document posted b Bez 'Doc passed to application 2 Bas 'Doc ready to be transferred to application B50 IDoc added GStatus records 2 Bs3 B 0001 inbound detiveryideliveries created (nos, 01»xXxXxx: to OLxXXXIXX? hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 20139)tortie 19:10 1boe Basics ForFurconal Cnsutanis| SAP Blogs An inbound IDoc goes through all the above statuses in reverse order (50-64-53). IDOC PROCESSING AUTOMATIC/IMMEDIATE PROCESSING In this case, IDoc are processed immediately as they generated or added in the system. The check “Transfer IDoc immediately” is selected in Outbound Options and “Trigger Immediately” is selected in Inbound Option. These checks are generally used when the real time information exchange is necessary between two systems. Recever pot ArocECOKL Transactional RE Pack. Size 1 [Queue Processing Output Mode @ Transfer IDoc immed. ‘Output Mode 2 © Collect Ieee Process code ‘ORDR SUS. ‘oRDRSP [ZCancel Processing After Syntax Error Processing by Function Module” ‘© Trigger by background program @ Trigger immediately MANUAL PROCESSING IDocs can also be manually processed using the TCODE BD87 in SAP. PROCESSING VIA BACKGROUND JOB IDoc processing by background is the most preferred way of processing the IDocs. Following Programs are used from processing the IDocs using background job: hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 21139)sanv20z2 19:10 'Doe Basics For Functional Consultants | SAP Blogs RBDAPP01 — Inbound |Docs RSEOQUTOO — Outbound IDocs REPROCESSING IDOCS On the basis of IDoc statuses different programs can be used for reprocessing of failed IDocs. These are given below: INBOUND/OUTBOUND | STATUS PROGRAM FOR REPROCESSING 51,63, RBDMANIZ INBOUND 60 RBDSYNER Cy RBDAGAIE 02, 04, 05, 25, and29 | RBDAGAIN ‘OUTBOUND 6 RBDSYNER 32 RBDAGAIE SEARCHING IDOCS IN SAP TCODE WE02/WE05: GENERAL SEARCH IDocs can be displayed in system via TCODE WE02 and WEOS. If IDoc number is not known then search can be made on the basis of IDoc Date, Direction, BASIC TYPE, MESSAGE TYPE, and PARTNER NUMBER. Partner number can be found in the Output Messages of the documents. hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 22139sanv20z2 19:10 23:59:59 25.08.2012 23:59:59 Basic Type ORDERSOS i i sess |Doc search can also be made on the basis of ISA or Transfer file Reference. WDoc List ‘Transl Fe Roorence » Reference Message Group » Message Reference » Epiarctive Key » Distant Diversion EDI Message Type » Clee} Bletele) TCODE WE09: SEARCHING DATA IN IDOC SEGMENTS If we are looking for specific information within the IDocs Segments then this can be found using TCODE WEO9. This is useful if you are searching for a particular information in similar kind of IDoc within IDoc segments. For example, if you want to hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 23139sanv2022 19:10 Doc Basics For Functional Consultants | SAP Blogs search a particular Purchase Order number e.g. 100000001 in multiple IDocs which lies in Segment E1EDKO1 of an IDoc under field BELNR. Then the search can be executed in the following manner. Fast Search Mode (w]Max. One Segment per IDoc Griteria for Search in Data Records ” Search in Segment... E1EDKOL Search in Field ... BELNR for Value... 100000001 and Search in Field ... for Value ... IDOC VALIDATIONS, COMMON IDOC ERRORS AND SOLUTION Document Locking | TN Cheek Fade SMT er ecks ane te ercess he Dee ence [Bor canal somsme benure of cra ‘pelba oe ones PO can be opened in change. mace whch 1D Procesing fo ty © ute Eosmaten Tre PO. Paral procesing out oma tat ee cessing te Does che {mune rogram are tig process one toc then th IOee tom one of he rogrems. Ensure Bal fos IDs the pees pom eat fa he ck Duptete Woes VOUT Check water cla Doe mg pst aeacy posted (Dar canaa ft epee oe ‘Communal he sane cnr ater aan Sega mitng ayn MOU Qh wth En he rm tn ar etn Sars ‘a me mancan oy enon 9s wan ac For nt Characters VOUT Try remow he special characters ak he prer eband ‘Spectinvna choc inthe IOs wil not ahow be 1 ne met Soe (Bor ot ose evel msn forte tare ach case ry ovotcte to inv test system nd ty 4 tn Tot coe By Ceozpn he ete tet na Though, the IDoc failure may not be related to any of the above mentioned reasons, the best way to find the IDoc error is to compare the existing IDoc with the good example. Good example IDoc can be easily searched with any of the IDoc search methods as described above. hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 24139)sanv20z2 19:10 IDoe Basics For Functional Consultants | SAP Blogs DOCUMENTATION FOR IDOC TYPES IDoc documentation can be found using TCODE WE60 and can be helpful to obtain information of the IDoc Type or its particular segment. It also provides information such as mandatory and optional segments, minimum and maximum number of segments, etc. Documentation for Basic type WMMEIDO2 a Basic type Structure of basic type WMMBID02 WMMBID02 Seen ™""=" Stock movements from ext. systems Release 40A EIMBXYH : Goods movements for mobile data entry (header data) 7 Status: Required , min. mame = 1, max. number 1 + EIMBXYI : Add goods movement from external system: Item Status: Required, min, number: 1, max, number: 9999 Sirneture sEIMBXY4J : Create Goods Movement from Non SAP. ‘System: Heme ‘Status: Ontinal min. number 1 max. number: 1 i GENERAL INFORMATION FOR COMMON IDOC MESSAGE TYPES The following list gives the Basic Type and Message Type combination for common idocs hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 25139sanv20z2 19:10 IDoe Basies For Functional Con SAP Blogs: BUSINESS DOCUMENT BASIC TYPE MESSAGE TYPE ORDERSO1 SALES ORDER ORDERSO2 ORDERS ORDERSOS ‘ORDERSO4 PURCHASE ORDER ORDERS ORDERSOS DELVRYO1 DELIVERY SHIPPING NOTIFICATION | DELVRYO2 DESADV DELVRYO3 INVOICE INVOICOt INVOIC ARCHIVING/DELETION OF IDpocs FROM DATABASE As |Docs grow older they are archived and deleted from the database. Archived IDocs can be viewed using TCODE SARI in Achieve Explorer using archiving object as IDoc. Following are the few programs that are used for archiving and deletion of |Docs from database. hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 26139sanv2022 19:10 Doe Basics For Functional Consultants | SAP Blogs PROGRAM PURPOSE RSEXARCA | Archive Idocs RSEXARCD | Delete archived IDocs from the database RSEXARCR | Read the IDocs from archive file RSEXARCL Retrieve IDocs from the archive into the database RSETESTD Delete IDocs from Database Assigned Tags MM (Materials Management) SAP ERP edi enterprise resource planning idoc sap sap erp logistics materials management hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 27139sanv20z2 19:10 IDoe Basics For Functional Consultants | SAP Blogs Similar Blog Posts SAP Enhancement & Modification Basics - Must read for Functional Consultant By chandan bhatnagar Nov 13, 2022 Inbound Delivery : Automatic Creation from Outbound Delivery By Former Member Oct 06, 2014 Functional Consultant roles and understanding on SAP Interfaces By Abdul Saleem Mar 21, 2022 Related Questions IDOC's Process in MM ina easy way By Former Member May 02. 2008 RELATION_NOT_FOUND error Rollout By Ramon Pajes. Jun O1, 2021 Idoc message type and basic type By sowrya masarapu Oct 30, 2019 315 Comments You must be Logged on to comment or reply to a post. BS Hada December 1, 2016 at 7:30 am Very Informative, thanks vike3 | Share hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 28139sanv20z2 19:10 IDoe Basics For Functional Consultants | SAP Blogs 8 SantheshVeotedeho.16 am Many Thanks for this information Like] | Share Former Member December 4, 2016 at 2:11 pm It's really very helpful... Like1 | Share Former Member December 20, 2016 at 4:25 pm Hi Niranjan Nagle, thank you so much for this helphul information, I've read your explanation about IDOC and I'm thinking to use it to post a Sales Order on SAP. My client is asking me to post SO based on the existing data in the Purchase order. Based on your explanation in the "Overview" paragraph, you said" for transfer between two SAP systems, ALE is Used do you think if used ALE it will be feasible for such requirement. Please let me know your opinion and if you have any explanation regarding my client requirement, Thank you so much, Moha Like O | Share Former Member January 16, 2017 at 8:47 pm Hi Mohamad, Yes, itis true that ALE can be used in this scenario. | am assuming you are trying to post SO in one system that triggers PO in another system. You still have to generate outbound IDoc (for SO) in sending system and Inbound IDec (for PO) in receiving system. Please check with your basis consultant on the usage of ALE in this scenario. hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 29139sanv20z2 19:10 IDoe Basics For Functional Consultants | SAP Blogs Regards, Niranjan -ike 0 | Share CMA Ramesh Kolluru February 23, 2017 at 10:11 am Excellent Article ...aptly tailored for functional consultants like me. Thanks a lot for your efforts and time. Like O | Share DAMODAR SAI MALLIKA May 20, 2017 at 3:20 am Very Helpful.. Good Work Like O | Share Former Member June 3, 2017 at 8:48 am very useful. Thanks Like O | Share Former Member September 16, 2017 at 6:19 am This is Very useful document. Thank you Very Very much Respect your hard work and knowledge sharing spirit, Like O | Share hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 30139sanv20z2 19:10 IDoe Basics For Functional Consultants | SAP Blogs Former Member November 3, 2017 at 2:54 pm Very much informative, Thank you: Like 0 | Share Former Member January 8, 2018 at 11:15 pm found this information really useful. Well explained. Appreciate the work you have put into this. Like 0 | Share Former Member February 8, 2018 at 6:30 am Great work Niranjan. Regards, GM.Shivakkumar Like O | Share ‘Adarsha Ak March 13, 2018 at 6:08 am ‘Thanks for making us to understand in simple way. Thanks, AK Like O | Share hitps:ologs.sap.com/2012/12/81idoc-basics-fr-unctional-consutants! 31139)sanv20z2 19:10 IDoe Basics For Functional Consultants | SAP Blogs Angelo Flores ) March 21, 2018 at 6:39 am Great, Thanks. Like O | Share Marky ACS, Hi Niranjan Nagle Good day Do you have also an article that explain how does SAP populate IDOCS? Regards, Mark. Like O | Share Raghava S April, 2018 at 6:06 pm Hi Niranjan, Well documented...! You simply rocked it BR Raghava Like O | Share Forme Merb hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 32139sanv20z2 19:10 IDoe Basics For Functional Consultants | SAP Blogs Very helpful documentation. Thank you for sharing this with us. Best Regards, Carsten Like O | Share Nripacharya Chowdhury August 28, 2018 at 7:25am Very helpful document. .ikeO | Share Samy G October 26, 2018 at 6:42 am Hi Niranjan...very informative docs..keep rocking Like 0 | Share Felipe Ricardo Guerra Soto December 3, 2018 at 8:21 pm Hi Niranjan Nagle, thank you so much for this great document with very useful information Like O | Share Jeff Sirkis January 16, 2019 at 7:47 pm | have been reading everything | can find regarding IDoc and EDI and this is the best post | have found, Thank you for sharing! Like 0 | Share hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 33139)sanv20z2 19:10 IDoe Basics For Functional Consultants | SAP Blogs Santosh Mathew July 25, 2019 at 3:29 pm ‘Awesome Blog, Had | read this blog before | could have got through my interview @) :). Great work and very useful for functional guys like me. This is more than basic information and everything at one place. Great!! Like1 | Share Rahul Ramesh September 5, 2019 at 4:23 am Extremely helpful read! Thanks for sharing, Like O | Share Vijay Sonavane October 31, 2019 at 6:16 am Thanks for sharing, Very much informative doc. Like O | Share Deepesh Kumar November 3, 2019 at 4:45 pm Very Helpful Like O | Share hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 34139)sanv2022 19:10 IDoe Basics For Functional Consultants | SAP Blogs 8 MinvaHisystiro at 6:23 am ‘Thanks so much for your post. It is very useful information for me. Like O | Share Sijin Chandran April 3, 2020 at 8:25 am This document is GOLD especially for IDOC beginners like me. It really helped me in getting a clear picture of IDOCs. This should be a one stop document which everyone should refer before getting into IDOCs. ‘And not only for Functional even for Technical(am a Technical resource) as well this document is very helpful Thanks, Sijin Like O | Share Roddi Gee May 7, 2020 at 7:35 pm ‘Thanks for your post, Well written and extremely useful and helpfull Like O | Share Sreemohan Sivadasan J May7,2020 at 10:15 pm Excellent document and contains very useful information. Like O | Share hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 35139sanv20z2 19:10 IDoe Basics For Functional Consultants | SAP Blogs NARAYANAPPA KURABA May 11, 2020 at 11:08 am Thank you for in detailed explanation on IDOCs. Very informative, vike O | Share Nitish Chawla May 26, 2020 at 5:33 am Even after 8 years of publishing... document is still relevant and informative @ a big thanks !!! Like O | Share Jorge Velasquez June 24, 2020 at 2:13 pm Hi How do you send Product Category to CPI--> C4C Regards. vike 0 | Share Naga Koteswara Rao Panchumarthi August 13, 2020 at 4:52 am Good one. vike 0 | Share hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 3639sanv20z2 19:10 IDoe Basics For Functional Consultants | SAP Blogs ‘Sai Kumar Mada ‘August 16, 2020 at 5:59 am Hats up and big thank you. vike O | Share JAGANNATHAN SRINIVASAN Thanks a lot for @ wonderful effort, Even though as a Functional Consultant | can wash off my hand to the technical consultant stating failure of idoc, after going through | can provide more inputs to the technical guy based on your document for quickly resolving the issue of why idocs failed. Great effort Like O | Share Rajya Lakshmi Chithaluri November 12, 2020 at 12:51 pm Nice document (Y) vike O | Share Navya Sree November 16, 2020 at 7:07 am Very Informative and Thanks for the explanation, Like O | Share Babu Abraham Gidla February 20, 2021 at 4:47 pm Thanks a ton. Really very helpful and you did a real help here, Like O | Share hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 37139sanv20z2 19:10 IDoe Basics For Functional Consultants | SAP Blogs Bob marray March 27, 2021 at 4:23 pm Very helpful documentation, Thank you for sharing this with us. vike O | Share Halil Erdur July 13, 2021 at 12:20 pm very informative article, thank you very much, we look forward to the next :) Like O | Share Tiarnan Mc Gabhann January 5, 2022 at 5:46 pm Really really useful post. Thank you very much. vike 0 | Share Yuxi Liang January 16,2022 at 10:02 am useful Like O | Share Veena Valsan February 4, 2022 at 3:24 am Excellent writing . Found it very useful..! Thank you! Like O | Share hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! 38139sanv2022 19:10 IDoe Basics For Functional Consultants | SAP Blogs bolin zhang February 23, 2022 at 4:01am Very Helpful! Thank you! Like O | Share Manoranjan Tamilarasan ‘August 12, 2022 at 6:23 pm Its Excellent Like O | Share Previous | 60f6 Find us on Privacy Legal Disclosure Trademark Newsletter hitps:ologs.sap.com/2012/12/81idoc-basics-fr unctional-consutants! Terms of Use Copyright Preferéncias de Cookies Support 39139