Ale & Idoc Training

Embed Size (px)

Citation preview

  • SAP ALE-IDOCDeepak Rampur, [email protected]

  • Agenda Introduction to ALEOver view of ALEIntroduction to IDOCProcess flow for outbound processProcess flow for inbound processConfiguring the ALE InfrastructureCreating the new IDOC typeConfiguring the system for new IDOCCase studyQuestions

  • Agenda Introduction to ALEOver view of ALEIntroduction to IDOCProcess flow for outbound processProcess flow for inbound processConfiguring the ALE InfrastructureCreating the new IDOC typeConfiguring the system for new IDOCCase study

  • Introduction to ALE

    Application linking and enabling (ALE) is SAPs technology to support distributed process across several SAP systems.

    A distributed process is one in which part of a business is carried out in one system and part on another.

    A distributed process may contain SAP and non SAP Systems. It is not necessarily between only SAP systems.

    ALE can be used to exchange the data between, SAP to SAP system SAP to Non-SAP system Non SAP to SAP System

  • Agenda Introduction to ALEOver view of ALEIntroduction to IDOCProcess flow for outbound processProcess flow for inbound processConfiguring the ALE InfrastructureCreating the new IDOC typeConfiguring the system for new IDOCCase study

  • Over view of ALE

    R/3 System

    R/3 System

    Non-SAP System Translator ALE Interface ALE Interface

  • Agenda Introduction to ALEOver view of ALEIntroduction to IDOCProcess flow for outbound processProcess flow for inbound processConfiguring the ALE InfrastructureCreating the new IDOC typeConfiguring the system for new IDOCCase study

  • Introduction to IDOCThe term IDOC stands for Intermediate document. It is simply a data container used to exchange information between any two process. That can understand the syntax and semantics of the data.IDOCs are made using the segmentsIDOCs are stored in the data baseEvery IDOC has unique numberAn IDOC is attached to a message type and identified by its message typeIDOC consists of three types of records One control record One or many data records One or many status records.

  • Introduction to IDOCControl Record: A control record contains all of the control information about an IDOC, IDOC number Sender and receiver information Message type it represents Its direction

  • Introduction to IDOCControl Record

  • Introduction to IDOCControl Record

  • Introduction to IDOCData Record In an IDOC the data record contains the application data.

  • Introduction to IDOCStatus Record Status records are attached to an IDOC throughout the process as the IDOC achieves different milestones or encounter an error. At every milestone a status code, date and time are assigned. The system defines numerous status code, 0 49 are reserved for outbound process 50 and above are reserved for inbound process

  • Introduction to IDOCStatus record

  • Introduction to IDOCIDOC as seen in transaction WE02

  • Agenda Introduction to ALEOver view of ALEIntroduction to IDOCProcess flow for outbound processProcess flow for inbound processConfiguring the ALE InfrastructureCreating the new IDOC typeConfiguring the system for new IDOCCase study

  • Process flow for outbound processSelection screenSelection Program/Build IDOC dataMaster IDOCApplication RepositoryConversionFilteringVersion ChangeCommunication IDOCRESOUT00ARFCDATARSARFCEXApplication LayerALE Service layerCommunication LayerDestination systemFunction module MASTER_IDOC_ DISTRIBUTE

  • Agenda Introduction to ALEOver view of ALEIntroduction to IDOCProcess flow for outbound processProcess flow for inbound processConfiguring the ALE InfrastructureCreating the new IDOC typeConfiguring the system for new IDOCCase study

  • Process flow for inbound processApplication RepositoryDirect input function module or CALL transactionPosting programRBDAPP01Application IDOCsConversionFilteringVersion ChangeID0C_INBOUND_ASYNCHRONOUSCommunication IDOC from remote systemApplication LayerALE Service layerCommunication Layer

  • Agenda Introduction to ALEOver view of ALEIntroduction to IDOCProcess flow for outbound processProcess flow for inbound processConfiguring the ALE InfrastructureCreating the new IDOC typeConfiguring the system for new IDOCCase study

  • Configuring the ALE InfrastructureThe basic settings for the IDOC interface must be maintained once on each system involved in distributed process

    Basic settings for IDOCs

    Maintaining logical systemAllocating logical system to the clientSetting up an RFC destinationThe port definitionMaintain the distribution modelCreate a partner profile

  • Configuring the ALE Infrastructure1. Maintaining logical system Transaction SALE

  • Configuring the ALE Infrastructure1. Maintaining logical system

  • Configuring the ALE Infrastructure2. Allocating logical system to the client Transaction SALE

  • Configuring the ALE Infrastructure2. Allocating logical system to the client Transaction SALE

  • Configuring the ALE Infrastructure3. Setting up an RFC destination Transaction SM59Transaction SM51 to Identify the Target Host of remote system

  • Configuring the ALE Infrastructure4. The Port definition Transaction WE21

  • Configuring the ALE Infrastructure 5. Maintaining the distribution model Transaction BD64

  • Configuring the ALE Infrastructure6. Create the partner profile Transaction WE20

  • Configuring the ALE InfrastructurePartner profile : outbound parameters

  • Configuring the ALE InfrastructurePartner profile : Inbound parameters

  • Agenda Introduction to ALEOver view of ALEIntroduction to IDOCProcess flow for outbound processProcess flow for inbound processConfiguring the ALE InfrastructureCreating the new IDOC typeConfiguring the system for new IDOCCase study

  • Creating the new IDOC typeIDOC is created using one or more segments. Each segment will have one or more fields. Group functionally related fields into segments. Then use segments to create the IDOC.

    2. Release segment type and basic IDOC type

    3. Allowed data type for the segments. CHARCharacter strings CLNTClient CUKYCurrency key, referenced by CURR fields DATSDate field (YYYYMMDD) stored as char(8) LANGLanguage key NUMCCharacter fields with only digits TIMSTime field (HHMMSS) stored as char(6)

  • Creating the new IDOC typeCreate the segments Transaction WE31

  • Creating the new IDOC type2. Create the basic IDOC type Transaction WE30 step 1

  • Creating the new IDOC type2. Create the basic IDOC type Transaction WE30 step 2

  • Creating the new IDOC type2. Create the basic IDOC type Transaction WE30 step 3

  • Creating the new IDOC type2. Create the basic IDOC type Transaction WE30 step 4

  • Creating the new IDOC type2. Create the basic IDOC type Transaction WE30 step 5

  • Agenda Introduction to ALEOver view of ALEIntroduction to IDOCProcess flow for outbound processProcess flow for inbound processConfiguring the ALE InfrastructureCreating the new IDOC typeConfiguring the system for new IDOCCase study

  • Configuring the system for new IDOCConfiguring the outbound process Create the new message type (WE81)Link the IDOC type to the message type (WE82)Add the message to the ALE distribution model (BD64)Create the partner profile (WE20)

  • Configuring the system for new IDOCConfiguring the inbound processCreate the new message type (WE81)Link the IDOC type to the message type (WE82)Allocate the function module to the logical message (WE57)Define the attributes for the inbound function module (BD51)Create new process code (WE42)Assign the process code to the function module (WE42)Create the partner profile (WE20)

  • Agenda Introduction to ALEOver view of ALEIntroduction to IDOCProcess flow for outbound processProcess flow for inbound processConfiguring the ALE InfrastructureCreating the new IDOC typeConfiguring the system for new IDOCCase study

  • Agenda Introduction to ALEOver view of ALEIntroduction to IDOCProcess flow for outbound processProcess flow for inbound processConfiguring the ALE InfrastructureCreating the new IDOC typeConfiguring the system for new IDOCCase studyQuestions

  • Questions?

  • Thank You