What is Ale, Edi,IDoc tech for sap

Question

Hi all,
What is Ale, Edi,IDoc tech for sap?
Thanks.

Answer 1

hi deniz,
<b>ALE</b>
ALE
Triggering OB via Change Pointers:
      When an application make a changes in any object an entry is made in CDHDR and CDPOS tables. When any change is made the SMD(Shared Master Data) Tool checks that ALE setting and create a change pointer in the BDCP table that will point to CDHDR table. A standard program RBDMIDOC is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process to distribute to the appropriate destinations. The program will read the table TBDME to determine the IDoc selection program it is MASTERIDOC_CREATE_SMD_MATMAS in the case of MATMAS.
Outbound Process:
When the stand-alone program or the Transaction(BD10) is run, it calls the Idoc
Selection program MASTERIDOC_CREATE_REQ_MATCOR in the case of MATMAS, which is hard coded in the program. The Idoc Selection program reads the master data and create a master Idoc and stores it in the memory. The function module then calls ALE layer by using another function module MASTER_IDOC_DISTRIBUTE which is invoked inside it. Then Idoc filtering, Segment filtering etc.. are done in the ALE layer.
     To dispatch the Idoc to the destination system, the system reads the partner profile to determine the destination system. Then the sending system calls the function module INBOUND_IDOC_PROCESS asynchronously on the remote system and passes the Idoc via memory buffer.
Asynchronous Communication:
The data  that is IDocs and the function module are  stored in ARFCDATA and ARFCSSTATE tables. The function module ARFC_DEST_SHIP will transports data to target System and the program ARFC_EXCUTE will execute the stored function Module. If communication problem occurs RSARFCSE program is automatically scheduled., if successful, entries in the tables ARFCSSTATE and ARFCDATA will be deleted.
Inbound Process:
The INBOUND_IDOC_PROCESS program is triggered as a result of RFC from the Sending System, the Idoc to be sent is passed as parameter for the function module
In the partner profile if Process immediately is selected then RBDAPP01 program is executed. It will read the process code(MATM) from the Partner profile, which in turn invoke the function module IDOC_INPUT_MATMAS for MATMAS
     Function module will call the corresponding SAP transaction using call transaction or uses direct programs to convert the Idoc to Application document .
In the table TBD51 there will be entries to find which option is used.
Transactions:
SALE - IMG ALE Configuration root
•     WE20 - Manually maintain partner profiles
•     BD64 - Maintain customer distribution model
•     BD71 - Distribute customer distribution model
•     SM59 - Create RFC Destinations
•     BDM5 - Consistency check (Transaction scenarios)
•     BD82 – Generate Partner Profiles
•     BD61 – Activate Change Pointers - Globally
•     BD50 – Activate Change Pointer for Msg Type
•     BD52 – Activate change pointer per change.doc object
•     BD59 – Allocation object type -> IDOC type
•     BD56 – Maintain IDOC Segment Filters
•     BD53 – Reduction of Message Types
•     BD21 – Select Change Pointer
•     BD87 – Status Monitor for ALE Messages
•     SALE – Display ALE Customizing     WEDI - ALE IDoc Administration
•     WE60 - IDoc documentation
•     SARA - IDoc archiving (Object type IDOC)
•     WE47 - IDoc status maintenance
•     WE07 - IDoc statistics
BALE - ALE Distribution Administration
•     WE05 - IDoc overview
•     BD87 - Inbound IDoc reprocessing
•     BD88 - Outbound IDoc reprocessing
•     BDM2 - IDoc Trace
•     BDM7 - IDoc Audit Analysis
•     BD21 - Create IDocs from change pointers
•     SM58 - Schedule RFC Failures
<b>EDI</b>
EDI(Electronic Data Interchange )
RFC DESTINATION:
                       A logical name used to identify the remote system on which a function needs to be executed.
Partner Profile:
      It defines the characteristics of data being exchanged with the business partner.
Partner Function:
     Role of the partner Eg:Ship-to-party,bill-to-party,etc in EDI and in ALE legacy system or remote SAP system.
Partner type:
          The type of your business partner .
     EDI        – KU/LI
     ALE     --  LS.
Archiving:
     -Need to archive the important transmitted document
-Created in SARA
     -Assigned in WE20.
PartnerProfile Tips:
•     RSECHK07- Consistency check for Partner Profile.
•     If you want to modify partner profile; copy it and then modify. If you can’t modify it , u have  to delete it.
•     To move partner profile to production system choose Partner ->  Transport
Port defintion:
     It defines the medium through which data is exchanged between systems.
•     tRFC    -   Used by ALE
•     FILe     -   Used by EDI
•     R/2 system system port  – For R/2 system
•     Internet port           - to connect with internet applications
•     It also depends on the  receiving side. If the receiving subsystem accepts tRFC, EDI also can use tRFC.
Remote Function modules required by Subsystem to send status and inbound idoc to SAP:
Startrfc                                         -   Program to execute RFC – enabled Fun.mod. in SAP
EDI_DATA_INCOMING             -   To send data as inbound
EDI_STATUS_INCOMING         -   To send status to SAP
RSPARAM               -   To know the gateway service of the SAP system.
Message Control:
•     Output controller
•     A service program for determining the output type
•     To generate and manage various outputs from an application and control their medium and timing of exchange.
•     To retransmit the document without duplicating it
Procedure:
•     A procedure defines a set of possible outputs for an application
•     There may be more than one procedure but only one can be active
•     Requirement field in procedure specifies the condition which the sales docu. should reach,for sending the sales order response.
Output type:
Defines the characteristics and attributes of the output.
Access Sequence :
Defines  a sequence in which the business rules are checked using condition record of the condition table for proposing output type.
Sapfans Q & A
SREL_GET_NEXT_RELATIONS   -
Function Module that will provide me the number of the document that was created by an IDoc
RLSUB020
Program which uses the above function module.
Upgradation problem
When the old version program is upgraded in to newer version(4.0b &#61664; 4.6c) the SE38 editor won’t allow u get thru’ the programs normally to get rid of this.
Solution:
EDIT > MODIFICATION OPERATIONS > SWITCH OFF ASSISTANT. Hit Enter on the subsequently shown Warnings window. You should now be able to maintain the code as before.
When transporting the dialog program sometimes the links may be missing in the testing and production area. To overcome just check u have properly save your all includes and other stuff in the same request if not, do so. Other options In ver 4.6c -> Within ABAP editor try utilities/Update navigation index
this fixes the links
ALE( Application Link Enabling )
Disk Mirroring:
Changes occurring in the database should reflected to another disk that maintains a mirror image of the main disk’s contents.
Replicas:
Maintaining redundant data across multiple systems.
ALE:
  It provides distributed environment to integrate non-SAP systems
  Provides guaranteed delivery of data regardless of network problem to application.
Logical system :
     The systems involved in distributed environment  are assigned a logical name which uniquely identifies a system in a distributed  environment.
Data Mapping:
     Conversion of a business document in IDoc format to an EDI format (and vice versa) which is performed in the subsystem.
Message Types:
•     Represents a business function
•     Technical structure is the IDoc type
•     Or can say an instance of IDoc.
<b>IDoc  :</b>
     They are containers used to exchange data between any two process.
     It represents an IDoc type and IDoc data
     IDoc type is structure and IDoc data is an instance of it.
<b>Pls reward if helpful.</b>