Skip to main content

YCLASSICAL_JOINING

*&---------------------------------------------------------------------* *& Report  YCLASSICAL_JOINING *& *&---------------------------------------------------------------------* *& *& *&---------------------------------------------------------------------* REPORT   yclassical_joining  NO   STANDARD   PAGE  HEADING                               LINE - SIZE   110                               LINE - COUNT   255                               MESSAGE - ID  z...

Difference Between ALE and EDI in SAP ABAP

Difference Between ALE and EDI in SAP ABAP

The main difference between ALE and EDI is ALE used for internal communications within the SAP Environment and EDI is meant for external communications that is communicating with Non-systems.
ALE(Application Link Enabling):
ALE is technology for SAP ,is used to transfer data between SAP systems.
ALE is used to support integrated processes across several SAP systems.
ALE includes controlled exchange of data messages guarantying data consistency across loosely coupled applications. ALE consists three layers which are Application Services , Distribution Services and Communication Services.
ALE provides a distributed and fully integrated R/3 system. Each application is self-capable. The use of self-capable system implies a certain measure of data redundancy.Hence data has to be both distributed and synchronized.
ALE uses an IDOC format to exchange data between systems, both participating systems should understand the IDOC format.
ALE transfers the data using memory buffers whereas EDI uses file port to transfer the data.
Distribution of applications between specific releases of R/3 Systems
Continued records alternate after a release upgrade without requiring special protection
Customer-specific extensions.
Communication interfaces that allow connections to non-SAP structures.
Coupling of R/three and R/2 Systems.
EDI( Electronic Data Interchange )
EDI means Electronic Data Interchange, is the electronic exchange of structured business data between different applications. Such as purchase orders, invoices, inquiries, planning, acknowledgements, pricing, order status, scheduling, test results, shipping and receiving, payments, and financial reporting.
When you are using EDI technology you always need a translator to convert the IDOC to X12 (Outbound), X12 to IDOC (Inbound).But in the case of ALE you don’t reuire a translator.
EDI Architecture contains EDI-enabled applications which support the automatic processing of business transactions.
The IDoc interface which consists of IDoc types and function modules that form the interface to the application.
The EDI subsystem which converts the IDoc types into EDI message types and vice versa. This component of the EDI architecture is not provided by SAP.
EDI is the independent technology use to transfer data between two systems, they can be SAP systems or non SAP systems.
Below following tasks related to EDI processing:
Conversion of data·
Message and Interchange Handling.
Communication·
Administration of partner profiles·
Monitoring of processing
All data is transferred in files between the R/3 System and the EDI subsystem. Synchronous RFC (Remote Function Call) is implemented to define the time of transfer for a file between the two systems.
Improves data accuracy
With EDI business can eliminate the need to re-enter data from paper documents and thus prevent potential data entry errors.
Lowers personnel costs
EDI can help companies reduce the need for personnel involved in orders and accounting processing. Speeds up information exchange- EDI systems can shorten the lead time between receipt and fulfillment of orders.
Reduces technical complexity related to data interchange
With EDI companies use standardized data formats to exchange documents. EDI allows companies using different business applications and systems to achieve computer-to-computer electronic exchange of business documents.
End

Comments

Popular posts from this blog

How to Create SAP ABAP Query Using SQ01 Step by Step Guide

How to Create SAP ABAP Query Using SQ01 Step by Step. You can create ABAP query objects ,if they are not exist in the SAP system. You can create SAP query without  ABAP programming knowledge. ABAP Query provides users with a variety of ways to define and create different types of  reports , such as  Basic Lists ,  Stats , and  Sorted Lists . ABAP query consists of four elements: Queries InfoSets Groups Translation query Queries The query component is used by end users for Queries. You can create queries, change and queries executed. Transaction  SQ01. Trnslation component / QUERY Many texts to define queries, InfoSets and user groups are generated. These texts are displayed in the language we choose to access the SAP system. We can compare the text or languages ​​that use this component. InfoSets InfoSets are the views of the Special Data Sources. An InfoSet Describes the fields of a data source that can be reported in the q...

ALV Field Catalog in SAP ABAP

ALV Field Catalog in SAP ABAP Field Catalog Field catalog is an internal table which is used to pass a list of fields to display in ALV report, we can set different properties to fields that will be display in ALV output. Type Group It is a data dictionary object which contains all the reusable user-defined types. Example for a type group is SLIS, which contains all the user-defined types for developing ALV reports. TYPE-POOLS is a keyword which is used to assign the type-group to a ALV report . Syntax : TYPE-POOLS SLIS . DATA : <IT_FCAT> TYPE SLIS_T_FIELDCAT_ALV . "INTERNAL TABLE FOR FIELD CATALOG DATA : <WA_FCAT> TYPE SLIS_FIELDCAT_ALV . " WORK AREA FOR FIELD CATLOG Field catalog types Field catalog: Field catalog is a format description of the display area. There are three procedures to build a FIELD CATALOG. 1. Automatic field catalog. 2. Semi-automatic field catalog. 3. Manual field catalog. Automatic field catalog. If the list structure has ...

SAP Table Structure T-codes

SAP table structure tcodes E11 - ABAP Dictionary Maintenance Basis - Dictionary Maintenance SE14 - Utilities for Dictionary tables Basis - Activation Program, Conversion Program, DB Utility, MC,  SPDDCU61 - Create table structure Cross Application - Object Dependencies CU63 - Display table structure Cross Application - Object Dependencies CU62 - Change table structure Cross Application - Object Dependencie CU64 - table structure List Cross Application - Object Dependencies LBWE - LO Data Ext.: Customizing Cockpit Logistics - Logistics Information System (LIS)RSA6 - Maintain DataSources Basis - BW Service APIRSO2 - Oltp Metadata Repository Basis - BW Service  APISE84 - Repository Information System Basis - Workbench Tools: Editors, Painters, Modelers SE38 - ABAP Editor Basis - ABAP Editor SE16 - Data Browser Basis - Workbench Utilities SM30 - Call View Maintenance Basis - Table Maintenance Tool SE37 - ABAP Function Modules Basis - Function Builder SE80 - Object N...