ale for functioanl

8/6/2019 ALE for Functioanl

1/87

IBM Global Services

Copyright IBM Corporation 2003

Application Link Enabling(ALE)

for Functional Consultants


2/87

IBM Global Services

Copyright IBM Corporation 2003 ABAP | Confidential | ALE For Functional .ppt | 8/2/2011Slide 2

Topics to coverTopics to cover

What is ALE ?

Components of ALE.

Anatomy of an IDoc.

ALE Processing

Transactions For Processing and Monitoring IDocs.

ALE in typical Project Scenario.

Questions


3/87

IBM Global Services


ALE!! What is it ??

It is a set ofIt is a set of

Tools,

programs and

data definitions

that provides the mechanism forthat provides the mechanism for

distributing functionality and data acrossdistributing functionality and data across

multiple system.multiple system.


4/87

IBM Global Services


What Data can be Exchanged ?What Data can be Exchanged ?

Transaction DataSD, MM, FI, CO, etc.

Master Data

Material, Customer, Vendor, etc.

Control DataOrganizational Reference Information

Plants, Sales Orgs, etc.

Data required to enable tightly coupled,distributed applications

Separate HR, Separate Treasury, etc.


5/87

IBM Global Services


What is ALE ?

Components of ALE.

Anatomy of an IDoc.

ALE Processing


Trouble Shooting


Questions



6/87

IBM Global Services


Components of ALEComponents of ALE

Services:Services:

Application ServicesApplication Services

Distribution ServicesDistribution Services

Communication ServicesCommunication Services


7/87

IBM Global Services



Services:Services:




This is where the SAP

applications ( SD, FI,

MM etc. ) generatetheir data and

documents


8/87

IBM Global Services



Services:Services:




Recipients

Formats and

Filters the data

Creates IDocs

( Intermediate

Documents


9/87

IBM Global Services



Services:Services:



Communication ServicesCommunication Services TCP/IP

RFC

tRFC

etc


10/87

IBM Global Services


Application

Data

Master

IDOC DetermineReceipients

Filter/Convert

Data, Create IDOCComm.

IDOC

Application

Functions

Filter/Convert

Data

Comm.

IDOC

Carrier

Application

Layer

Application

LayerDistribution/ ALE

Layer

Distribution/ ALE

LayerCommunication

Layer

Communication

Layer

Application

In a Nut ShellIn a Nut Shell


11/87

IBM Global Services



What is ALE ?

Components of ALE.

Anatomy of an IDoc. ALE Processing

Transactions For Monitoring and Processing IDocs.

Trouble Shooting


Questions


12/87

IBM Global Services

Copyright IBM Corporation 2003|

ALE BUILDING BLOCKS & CONCEPTS

Logical system

Message Type

Idoc Type and Idoc

Customer Distribution Model Filter object type and Filter objects

Change Pointers

Ports

Process Codes

Message Control and Output Type

Partner Profile


13/87

IBM Global Services


LOGICAL SYSTEM

A logical system ( LS ) is the representation of an R/3 or external system in

SAP R/3 for the distribution of data to and from the R/3 system.


14/87

IBM Global Services


MESSAGE TYPE

A message type represents the application message exchanged between

R/3 systems and R/3 and an external system. A message type characterises

the data sent across systems and relates to the structure of the data called

an IDOC type.

Example: MATMAS is message type for Material Master


15/87

IBM Global Services


IDOC TYPE & IDOC

An IDOC type represents the structure of the data associated with a

message type ( DEBMAS02 for message type DEBMAS ) while an IDOC is

an object containing the data of a particular message type.

An IDOC consists of three record types:

- Control Record ( EDIDC ).

- Data Record ( EDIDD )

- Status Record ( EDIDS )


16/87

IBM Global Services


CUSTOMER DISTRIBUTION MODEL

It is a tool that stores information about the flow of messages across various

systems

The model stores data that dictates which messages flow to which logicalsystems

TCODE-----> BD64


17/87

IBM Global Services


CHANGE POINTER

Change Pointers are R/3 objects that mark changes to SAP Master data.

CD objects record the changes in table CDHDR & CDPOS.

Internal mechanisms update table BDCP & BDCPS which host the change pointer.

Activate change pointers for message type or generally.


18/87

IBM Global Services


PORTS

A port is a logical representation of a communication channel in SAP with the data

communicated being IDOCs.

Types of Ports:

- tRFC

- File

- ABAP

- XML

ALE can use all port types to distribute IDOC

EDI typically uses a File-based port

TCODE -------> WE21


19/87

IBM Global Services


PROCESSCODES

Process Codes are used in ALE and EDI to identify the function modules to be invoked

for subsequent processing

Inbound interface uses a process code to determine the application module that will

process the inbound IDOC. Stored in table TEDE1.


20/87

IBM Global Services


Scenario analysisScenario analysis

How does the IDOC look like ?

How is data being sent ?

How is the data being received ?

Who is sending?

To whom is it being sent?

What has been done with the idoc?


21/87

IBM Global Services


Idoc Documentation

WE60WE60


22/87

IBM Global Services


Idoc definition

WE30WE30


23/87

IBM Global Services


1 Idoc contains1 Control record

N Data RecordsN Status Records

IDOC

IntermediateDocument


24/87

IBM Global Services


First record of an IDoc package is always acontrol record. It describes the contents of thedata contained in the idoc.

Control RecordControl Record

Control Recordcontainsinformation about:

IDOC type (whatdata is in the

IDOC)

Message type(how is the IDOCbeing processed)

Senderinformation (whois the sender of

that IDOC)

Receiverinformation (who

is the receiver ofthat IDOC)

Latest status ofEDI processing.

EDI standard andversion.


25/87

IBM Global Services


All records in the IDoc, which come after the

control record, are the IDoc data. They are allstructured alike, with a segment information partand a data part, which is 1000 character inlength, filling the rest of the line.

Data RecordData Record

Hierarchicalstructure (internal

representation as flatstructure)

Contains the actualbusiness data


26/87

IBM Global Services


Status RecordStatus RecordInformation about the IDoc statuslike:IDoc identification number

Status number - table verifiedIDoc typeDirectionData and time stamp

Idoc has been processed

yes/no?Processingsuccessful/erroneous

What type of error?


27/87

IBM Global Services



What is ALE ?

Components of ALE.

Anatomy of an IDoc.

ALE Processing.

i.Outbound Processing

ii.Inbound Processing


Trouble Shooting


Questions


28/87

IBM Global Services


Basic Configuration ElementsBasic Configuration Elements

Create and allocate Logical System BD54

Define Ranges (Idocs, Ports, IDoc types, segment version, change

pointers )

Define RFC Destinations

SM59 Define Ports WE21

Maintain Customer Model BD64

Create Partner Profiles WE20


29/87

IBM Global Services


Partner ProfilesPartner Profiles

TCODE:

WE20


30/87

IBM Global Services


Partner ProfilesPartner Profiles--OutboundOutbound


31/87

IBM Global Services


Distribution ModelDistribution ModelTCODE:

BD64

Required mainly formaster data

Filter values set up for

master data outbound


32/87

IBM Global Services


Outbound program development

Program logic

How is the IDOC being created ?

Triggering

How is the IDOC creation kicked off ?


33/87

IBM Global Services


Sending Master Data IdocsSending Master Data Idocs

Only sendobjects that have

changed ?

Change

Pointer

available?

Master

data ?

Standalone with

custom logic to keep

track of changes

Change Pointer

based Program

y

N

Y

Standalone programwith user-definable

selection criteria

N

Y


34/87

IBM Global Services


Sending Transactional Data IdocsSending Transactional Data Idocs

Ensure trans-

actional

Integrity?

Output

Determinat

ionavailable ?

Transaction

Data ?

hard coded ALE

layerModification

Output determination

based Program

y

N

Y

N

Y

User-Exit

available?

N

Hardcoded ALE layer

no Modification

Y

See Master data


35/87

IBM Global Services


Change PointersChange Pointers

Application Posting

Post Application document

Create Change Document

Are changes ALE relevant ?

Write Change Pointers

Commit Work

ALE configuration

ALE relevant Fields

Batch Program(RBDMIDOC)

IDOCModule(Masteridoc_Create_

SMD_)

Read Change Pointers

Fill IDOC

Call ALE layer

Update Change Pointer

Master data

Change pointers

ALE layer

Master_IDOC_DISTRIBUTE

Determine IDOC module

Call IDOC module


36/87

IBM Global Services


ALE Configuration ForChange PointersALE Configuration ForChange Pointers

Define change pointer creation

Define which change document fields are to be logged

Change pointer activation

Activate generally

Activate per message type

Publish new function module

Link message type to function module


37/87

IBM Global Services


ALE For Transactional dataALE For Transactional data -------- Output DeterminationOutput Determination

NACE


38/87

IBM Global Services


Output TypesOutput Types ---- Partner FunctionsPartner Functions


39/87

IBM Global Services


Output TypesOutput Types ---- Processing RoutinesProcessing Routines


40/87

IBM Global Services


Inbound Processing


41/87

IBM Global Services


Partner ProfilesPartner Profiles--InboundInbound


42/87


43/87

IBM Global Services



What is ALE ?

Components of ALE.

Anatomy of an IDoc.

ALE Processing



Questions


44/87

IBM Global Services


Case 1: Distribution ofMaterial Master Data

- Through Standalone program

Steps Involved:

1. Define Logical Systems [ SALE ].

2. Assign Client to Logical System [ SALE ].

3. Create RFC Destination [ SM59 ].

4. Create Port [ WE21 ].

5. Maintain the Distribution Model [ BD64 ].

6. Create Partner Profiles [ WE20 ] or Generate them from distribution model [ BD82 ].

7. Distribute the Distribution Model [ BD64 ].

8. Ensure that Logical Systems, partner profiles are generated in the receiver too.

(Configured when you distribute a distribution model)

9. In the outbound parameters for sender partner profiles add the message type

SYNCH and IDOC type SYNCHRON along with the material master message type

and IDOC types: MATMAS and MATMAS03 respectively.

10. Execute the process [ BD10 ].


45/87

IBM Global Services


ALE Monitoring Transactions

List Of All IDocs CreatedList Of All IDocs Created - WE02/WE05

Search using idoc data content - WE09

Selection Program For Issuing OutputSelection Program For Issuing Output ---- WE15WE15

Process All Selected IDocsProcess All Selected IDocs -- WE14WE14

Process/monitor idoc

BD87


46/87

IBM Global Services


Select IDocs BD87Select IDocs BD87

Select for

Re-processing error/unprocessed

idocs

Status-wise number if idocs

Display Idocs

Trace Idocs


47/87

IBM Global Services


BD87 contd


48/87

IBM Global Services


BD87 Contd


49/87

IBM Global Services


Some common idoc status

Inbound :

Success 53

Errors 51

Outbound

Successfully created 30

Successfully sent out 03

Errors - 26

G S


50/87

IBM Global Services


Idoc Test Transaction WE19 various options

IBM Gl b l S i


51/87

IBM Global Services


Idoc Processing through test transaction WE19

4 Processing Options

Standard Inbound

Inbound Function Module

Inbound File

Standard Outbound Processing

New idoc gets created at end

IBM Gl b l S i


52/87

IBM Global Services



What is ALE ?

Components of ALE.

Anatomy of an IDoc.

ALE Processing.



Questions

IBM Gl b l S i


53/87

IBM Global Services


Appendix A

Some Useful Transactions

IBM Global Services


54/87

IBM Global Services


Appendix A

To Create Idoc we need to follow these steps:

Create Segment ( WE31)Create Idoc Type ( WE30 )Create Message Type ( WE81 )Assign Idoc Type to Message Type ( WE82 )

Creating a SegmentGo to transaction code WE31

Enter the name for your segment type and click on the Create iconType the short textEnter the variable names and data elementsSave it and go backGo to Edit -> Set ReleaseFollow steps to create more number of segments

Create IDOC TypeGo to transaction code WE30Enter the Object Name, select Basic type and click Create iconSelect the create new option and enter a description for your basic IDOC type and press enter

Select the IDOC Name and click Create iconThe system prompts us to enter a segment type and its attributesChoose the appropriate values and press EnterThe system transfers the name of the segment type to the IDOC editor.Follow these steps to add more number of segments to Parent or as Parent-child relationSave it and go backGo to Edit -> Set release

IBM Global Services


55/87

IBM Global Services


Appendix A

Create Message TypeGo to transaction code WE81

Change the details from Display mode to Change mode

After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter

Click New Entries to create new Message Type

Fill details

Save it and go back

Assign Message Type to IDoc TypeGo to transaction code WE82

Change the details from Display mode to Change mode

After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.

Click New Entries to create new Message Type.

Fill details

Save it and go back

IBM Global Services


56/87

IBM Global Services


Idoc SegmentsIdoc Segments

TCODE:

WE31

IBM Global Services


57/87

IBM Global Services


Idoc TypesIdoc Types

TCODE:

WE30

IBM Global Services


58/87

IBM Global Services


How to Attach SegmentsHow to Attach Segments

IBM Global Services


59/87

IBM Global Services


Message TypesMessage Types

WE81WE82

IBM Global Services


60/87

IBM Global Services


Logical SystemLogical System

TCODE:

BD54

IBM Global Services


61/87

IBM Global Services


Allocate Logical System to the clientAllocate Logical System to the client

SALE > BASIC SETTINGS > SET UP

LOGICALSYSTEM >ASSIGN LOGICAL

SYSTEMTOTHE CLIENT

TCODE:

SCC4

IBM Global Services


62/87

IBM Global Services


Maintaining RFC DestinationsMaintaining RFC Destinations

TCODE:

SM59

IBM Global Services


63/87

IBM Global Services


Displaying and Maintaining PortsDisplaying and Maintaining Ports

AA portport isis aa logicallogical representationrepresentation ofof aa

communicationcommunication channelchannel inin SAPSAP withwith

thethe datadata communicatedcommunicated beingbeing IDocsIDocs.

TCODE:

WE21

IBM Global Services


64/87


Filter ObjectsFilter Objects

BD95BD59

IBM Global Services


65/87


FM Assignment to Message Type and IDoc typeFM Assignment to Message Type and IDoc type

TCODE:

WE57

IBM Global Services


66/87


Process CodesProcess Codes

WE41WE42

IBM Global Services


67/87


Process Codes in Inbound and OutboundProcess Codes in Inbound and Outbound

TCODE:

WE64

IBM Global Services


68/87


Change PointersChange Pointers

BD61BD50

IBM Global Services


69/87


Change Pointers ContinuedChange Pointers Continued

BD52BD60

IBM Global Services


70/87


FM For Inbound EDIFM For Inbound EDI

TCODE:

BD67

IBM Global Services


71/87


Output DeterminationOutput Determination ---- Access SequenceAccess Sequence

IBM Global Services


72/87


Output DeterminationOutput Determination ---- Output TypesOutput Types

IBM Global Services


73/87


Output TypesOutput Types ---- DetailsDetails

IBM Global Services


74/87


Output TypesOutput Types ---- ProceduresProcedures

IBM Global Services


75/87


Output TypesOutput Types ---- Procedures ControlProcedures Control

IBM Global Services


76/87


Output TypesOutput Types ---- Condition recordsCondition records

IBM Global Services


77/87


List Of All IDocs Created. (Default, Additional, EDI)List Of All IDocs Created. (Default, Additional, EDI)---- WE02WE02

IBM Global Services


78/87


Selection Program For Issuing OutputSelection Program For Issuing Output ---- WE15WE15

IBM Global Services


79/87


Process All Selected IDocs. WE14Process All Selected IDocs. WE14

IBM Global Services


80/87


Idoc Search For Business Contents (Database). WE09Idoc Search For Business Contents (Database). WE09


81/87

IBM Global Services


82/87



- Through Standalone program

Steps Involved:




4.C

reate Port [W

E21 ].5. Maintain the Distribution Model [ BD64 ].





9. In the outbound parameters for sender partner profiles add the message typeSYNCH and IDOC type SYNCHRON along with the material master message type

and IDOC types: MATMAS and MATMAS03 respectively.

10. Execute the process [ BD10 ].

IBM Global Services


83/87


Send Material transaction BD10

IBM Global Services


84/87



- Through Change Pointers

Steps Involved:




4.C

reate Port [W

E21 ].5. Create Partner Profiles [ WE20 ].

6. Enable Change Pointers globally [ BD61 ].

7. Enable Change Pointers for a Message Type [ BD50 ].

8. Specify the fields for which Change Pointers are to be written [ BD52 ].

9. Changing the field in Master Data [ MM02 ].

10. Execute the program RBDMIDOC to process the change pointers [ SE38 ].

IBM Global Services


85/87


Case 3: Distribution of Transaction Data

- Purchase Orders

Steps Involved:




4.C

reate Port [W

E21 ].5. Maintain the Distribution Model [ BD64 ].





IBM Global Services


86/87


Distribution of Transaction Data

- Purchase Orders contd.

9. OUTPUT DETERMINATION:

a) Maintain condition table for PO:

SPRO -> Materials Management -> Purchasing -> Message Determination ->

Message Determination -> Condition Table forMessages -> Define condition

table for purchase order -> Messages: Display Condition Table:

b) Define Access sequence:

SPRO ->Materials Management -> Purchasing ->Message Determination ->

Message Determination -> Access Sequences -> Define Access sequence

for purchase order.

c) Configuring the output type:


Message Determination -> Message Types -> Define message types forpurchase order -> Maintain output types: Purchase order

IBM Global Services


87/87

Distribution of Transaction Data

- Purchase Orders contd.

d) Indicate the permitted operations for which the output is activated


Message Determination -> Message Types -> Define message types for

purchase order -> Fine- Tuned Control: Purchase Order

e) link it to an output procedure (message schema):

SPRO -> Materials Management -> Purchasing -> Message Determination ->Message Determination -> Message Schemas -> Define message schemas for

purchase order -> Maintain output determination procedure: Purchase order

f) Create condition records for the tables that are being accessed in certain

sequences that we incorporated in the output type.

Logistics -> Materials Management -> Purchasing -> Master Data -> Messages ->

Purchase Order -> Create

10. Create the PO [ ME21 ]

enter a purchase order document type that was used for creating condition

records during the configuration of output determination.

11. Process the output [ WE15 ]