100%(1)100% fanden dieses Dokument nützlich (1 Abstimmung)
249 Ansichten25 Seiten
This document provides an overview of intermediate documents (IDocs) in SAP systems. It defines an IDoc as a structured ASCII data file used to exchange information between independent systems. IDocs are stored in SAP database tables and are independent of the sending and receiving systems. They contain control, data, and status records with information like sender, receiver, and current status. IDocs can be transmitted between systems using Application Link Enabling (ALE) or Electronic Data Interchange (EDI) technologies. The document also discusses IDoc processes, partner profiles, transaction codes, status values, and general settings.
This document provides an overview of intermediate documents (IDocs) in SAP systems. It defines an IDoc as a structured ASCII data file used to exchange information between independent systems. IDocs are stored in SAP database tables and are independent of the sending and receiving systems. They contain control, data, and status records with information like sender, receiver, and current status. IDocs can be transmitted between systems using Application Link Enabling (ALE) or Electronic Data Interchange (EDI) technologies. The document also discusses IDoc processes, partner profiles, transaction codes, status values, and general settings.
Copyright:
Attribution Non-Commercial (BY-NC)
Verfügbare Formate
Als PPT, PDF, TXT herunterladen oder online auf Scribd lesen
This document provides an overview of intermediate documents (IDocs) in SAP systems. It defines an IDoc as a structured ASCII data file used to exchange information between independent systems. IDocs are stored in SAP database tables and are independent of the sending and receiving systems. They contain control, data, and status records with information like sender, receiver, and current status. IDocs can be transmitted between systems using Application Link Enabling (ALE) or Electronic Data Interchange (EDI) technologies. The document also discusses IDoc processes, partner profiles, transaction codes, status values, and general settings.
Copyright:
Attribution Non-Commercial (BY-NC)
Verfügbare Formate
Als PPT, PDF, TXT herunterladen oder online auf Scribd lesen
ON ON IDOCs IDOCs 14 December 2011 14 December 2011 2 2 Intermediate Documents Intermediate Documents (IDOCs) (IDOCs) An IDoc is structured ASCII data fiIe that is used to An IDoc is structured ASCII data fiIe that is used to exchange information between systems and partners exchange information between systems and partners that can understand the syntax and semantics of the that can understand the syntax and semantics of the data data 14 December 2011 14 December 2011 3 3 Intermediate Documents Intermediate Documents (IDOCs) (IDOCs) Interchange Document Interchange Document Exchanged between compIeteIy independent systems and partners Exchanged between compIeteIy independent systems and partners Data is transmitted in ASCII format i.e., in human readabIe format Data is transmitted in ASCII format i.e., in human readabIe format 14 December 2011 14 December 2011 4 4 Intermediate Documents Intermediate Documents (IDOCs) (IDOCs) In SAP system, IDOCs are stored in database tabIes. In SAP system, IDOCs are stored in database tabIes. IDOCs are independent of the sending and receiving systems. IDOCs are independent of the sending and receiving systems. IDOCs are independent of the direction of data exchange. IDOCs are independent of the direction of data exchange. 14 December 2011 14 December 2011 5 5 Contents of IDocs Contents of IDocs ControI Record ControI Record - - Contains information about Sender and Contains information about Sender and Receiver Receiver Data Record Data Record - - Contains the message to be exchanged Contains the message to be exchanged between Sender and Receiver between Sender and Receiver Status Record Status Record - - Contains Status of IDoc at various stages Contains Status of IDoc at various stages during the transmission of IDoc between during the transmission of IDoc between Sender and Receiver. Sender and Receiver. 14 December 2011 14 December 2011 6 6 Contents of IDocs Contents of IDocs Control Record Sender ID Receiver ID Idoc Type Sender Port Receiver Port Message Type Data Record Data Record Containing the message to be exchanged in multiple records Status Record Containing the status oI IDoc exchanged at various stages. Each record corresponds to one stage - 49 14r Outb4und Pr4cess - 7 14r nb4und Pr4cess 14 December 2011 14 December 2011 7 7 Contents of IDocs Contents of IDocs 14 December 2011 14 December 2011 8 8 Direction Direction EXAMPLES EXAMPLES Outbound Outbound 2 2 Inbound Inbound 14 December 2011 14 December 2011 9 9 PARTNER TYPES PARTNER TYPES EXAMPLES EXAMPLES KU KU Customer Customer LI LI Vendor Vendor 14 December 2011 14 December 2011 10 10 PARTNER STATUS PARTNER STATUS EXAMPLES EXAMPLES A A Active Active II Inactive Inactive 14 December 2011 14 December 2011 11 11 Message Type Message Type Message type identifies the message being exchanged Message type identifies the message being exchanged Every IDoc type is assigned to a Message type Every IDoc type is assigned to a Message type AII IDoc carrying simiIar message ( simiIar IDoc type ) AII IDoc carrying simiIar message ( simiIar IDoc type ) can be recognized by message type can be recognized by message type Message Types Message Types - - ExampIes ExampIes DESADV DESADV DeIivery: Shipping Notification DeIivery: Shipping Notification EXPINV EXPINV Export Invoice Export Invoice INVOICE INVOICE Invoice / BiIIing Document Invoice / BiIIing Document ORDRSP ORDRSP Purchase Order / Order Confirmation Purchase Order / Order Confirmation 14 December 2011 14 December 2011 12 12 Transmission of IDoc Transmission of IDoc Transmission of IDoc can be defined as technoIogy using Transmission of IDoc can be defined as technoIogy using which an IDoc from SAP port is transmitted to the receiver or which an IDoc from SAP port is transmitted to the receiver or an IDoc is received at the SAP port from the sender. an IDoc is received at the SAP port from the sender. ALE, EDI are among these technoIogies. ALE, EDI are among these technoIogies. 14 December 2011 14 December 2011 13 13 Applicati4n Link Enabling Applicati4n Link Enabling ALE Objectives ALE Objectives ALE incorporates controIIed exchange of ALE incorporates controIIed exchange of data messages ensuring data consistency across IooseIy data messages ensuring data consistency across IooseIy coupIed appIications. coupIed appIications. ALE comprises of three Iayers. ALE comprises of three Iayers. AppIication Services AppIication Services Distribution Services Distribution Services Communication Services Communication Services Transmission mode can be RFC or TRFC Transmission mode can be RFC or TRFC In TRFC the IDoc is returned to sender in case cannot be In TRFC the IDoc is returned to sender in case cannot be deIivered to receiver successfuIIy by the middIe ware unIike deIivered to receiver successfuIIy by the middIe ware unIike RFC. RFC. 14 December 2011 14 December 2011 14 14 Applicati4n Link Enabling Applicati4n Link Enabling SENDER Application Sender Port RECEIVER Application Receiver Port Middle ware IDoc 14 December 2011 14 December 2011 15 15 Electr4nic Data nterchange Electr4nic Data nterchange The IDoc is transmitted to the receiver Via EDI subsystem The IDoc is transmitted to the receiver Via EDI subsystem The EDI subsystem is connected to the SAP system. The EDI subsystem is connected to the SAP system. EDI subsystem is aIso connected to the reciver system EDI subsystem is aIso connected to the reciver system 14 December 2011 14 December 2011 16 16 Electr4nic Data nterchange Electr4nic Data nterchange SENDER Application Sender Port RECEIVER Application Receiver Port Middle ware IDoc EDI Sub System EDI Sub System IDoc IDoc 14 December 2011 14 December 2011 17 17 IDoc Process IDoc Process OUTBOUND PROCESS OUTBOUND PROCESS - - The process of creating and sending The process of creating and sending the IDoc is termed as outbound the IDoc is termed as outbound process process INBOUND PROCESS INBOUND PROCESS - - The process of receiving and The process of receiving and processing the IDoc is termed as processing the IDoc is termed as inbound process inbound process 14 December 2011 14 December 2011 18 18 Maintaining Partner ProfiIes Maintaining Partner ProfiIes Types of Partners Types of Partners LS LS- - LogicaI system LogicaI system B B - - Bank Bank LI LI - - Vendor Vendor KU KU - - Customer Customer BP BP - - Benefits provider Benefits provider GP GP - - Business partner Business partner LS is the partner type used in ALE where as aII others wiII be used LS is the partner type used in ALE where as aII others wiII be used in EDI and other technoIogies. in EDI and other technoIogies. Creating new partner profiIe requires partner name, type and Creating new partner profiIe requires partner name, type and processing agent detaiIs. processing agent detaiIs. 14 December 2011 14 December 2011 19 19 Registering ProfiIe of a Registering ProfiIe of a Partner Partner 14 December 2011 14 December 2011 20 20 IMPORTANT TRANSACTION IMPORTANT TRANSACTION CODES CODES WE2 WE2 DispIay of Idoc DispIay of Idoc WE Idoc List WE Idoc List WE7 Idoc Statistics WE7 Idoc Statistics WE9 Test TooI WE9 Test TooI - - No authorization No authorization WE2 Partner ProfiIes WE2 Partner ProfiIes BD87 Status Monitor for ALE Messages BD87 Status Monitor for ALE Messages 14 December 2011 14 December 2011 21 21 STATUS VALUES STATUS VALUES Status by the SAP system (IDoc Basis): Status by the SAP system (IDoc Basis): IDoc added IDoc added IDoc with errors added IDoc with errors added Error during syntax check of IDoc (inbound) Error during syntax check of IDoc (inbound) Processing despite syntax error (inbound) Processing despite syntax error (inbound) 2 2 IDoc passed to appIication IDoc passed to appIication Error passing IDoc to appIication Error passing IDoc to appIication 4 4 IDoc ready to be passed to appIication IDoc ready to be passed to appIication Error in ALE service Error in ALE service IDoc waits for predecessor (SeriaIization) IDoc waits for predecessor (SeriaIization) 8 8 Error Error - - no further processing no further processing 74 74 IDoc added by test transaction IDoc added by test transaction 14 December 2011 14 December 2011 22 22 STATUS VALUES STATUS VALUES Status by the SAP system (AppIications) Status by the SAP system (AppIications) Error Error - - AppIication document not posted AppIication document not posted 2 2 AppIication document incompIete posted AppIication document incompIete posted AppIication document posted AppIication document posted 14 December 2011 14 December 2011 23 23 GeneraI Settings GeneraI Settings LogicaI name to system LogicaI name to system - - LogicaI system name shouId LogicaI system name shouId be defined and then it can be assigned to any cIient of be defined and then it can be assigned to any cIient of SAP. GeneraIIy this settings are done for ALE, as ALE SAP. GeneraIIy this settings are done for ALE, as ALE considers every partner as a system. considers every partner as a system. Transaction Code SALE which can be used for aII ALE Transaction Code SALE which can be used for aII ALE settings contains options for defining LogicaI systems settings contains options for defining LogicaI systems and assigning LogicaI systems to CIient. and assigning LogicaI systems to CIient. 14 December 2011 14 December 2011 24 24 GeneraI Settings GeneraI Settings 14 December 2011 14 December 2011 25 25 DATABASE TABLES DATABASE TABLES IDocs are stored in database tabIes EDI* IDocs are stored in database tabIes EDI* for the data, controI data and the Iog fiIes for the data, controI data and the Iog fiIes EDID4 EDID4IDoc Data IDoc Data EDIDC EDIDC IDoc ControI Data IDoc ControI Data EDIDS EDIDS IDoc Status Data IDoc Status Data