ALE/IDOC FOR SAP Functional Consultants

Overview
ALE and EDI
Components used in ALE/EDI.
Differences between ALE and EDI
Inbound process
Outbound process
Master Data Distribution
Transactions
Periodic Processing
Idoc Archiving

16-May-08

Application Link Enabling (ALE)

SAPs Proprietary Technology

Data Communication between two or more SAP R/3 Systems
Integration, distribution of application and data.
ALE scenarios falls into 3 categories
1.
Master Data - Material Master, Vendor Master
2.
Transactional Data Invoice, Purchase Order
3.
Control Data Business Area, Sales Org, Plant
Message Based Architecture of ALE comprises of 3 layers
1.
Application Layer :Generate or Receive messages.
2.
Distribution Layer :Filtering and converting messages.
3.
Communication Layer : Synchronous and Asynchronous
Synchronous communication of transmission for control data
Asynchronous communication for application data (Transactional +
Master)

16-May-08

Electronic Data Interchange (EDI)

Data communication between SAP and Non SAP systems, vice versa.
EDI is about doing business and carrying out transactions with your trading partners
electronically.
EDI documents such as an invoice, purchase order are industry based.
Most Commonly Used Standards
ANSI X12- American National Standards Institute (North America, Australia)
EDIFACT - Electronic Data Interchange for Administration, Commerce, and
Transport (Europe).

EDI provides connectivity with business partners such as bank, customer and vendors

16-May-08

ANSI Sample
ISA*00*0000000000*00*0000000000*08*6111470100 *01*002521359
*071008*2211*U*00401*000013021*0*P*>~
GS*PO*6111470100*002521359*20071008*2211*4319*X*004010~
ST*850*286614458~
BEG*00*SA*0056-9304975-0551**20071008*D~
REF*IA*3787061*PHILIPS CONSUMER ELECTRON~
REF*DP*056~
FOB*DF*DE*STORE~
CSH*N~
ITD*01*2*****30~
DTM*037*20071014~
DTM*038*20071015~
TD5*B*92*PREPAID AMERICAN FRT~
N1*BY*TARGET DC
0551*92*0551~
N3*7120 HWY 65 N. E.~
N4*FRIDLEY*MN*55432*US~
PO1*1*16*EA*187*WE*CB*056010231*VA*SHS3201/37*UP*609585143449~
CTP*RS*RES*279.99********1~
PID*F*08***10.2"PHILIPS~
PO4*6*************1~
CTT*1*16~
SE*19*286614458~
GE*1*4319~
IEA*1*000013021~

16-May-08

EDIFACT - Sample
UNB+UNOA:2+3012901500000:14+3025610000100:14+070528:0818+308191131633++INVOIC
UNH+1+INVOIC:D:96A:UN:EAN008
BGM+380+6185912994+9
DTM+171:20070529:102
NAD+BY+3025610071001::9++FNAC SA
C/O FNAC LOGISTIQUE+2 A 3 RUE DES CHAMPARTS+MASSY CEDEX++91742+FR
RFF+GN:775661390
NAD+IV+3025610081000::9++FNAC SA
C/O FNAC LOGISTIQUE+2 A 3 RUE DES CHAMPARTS+MASSY CEDEX++91742+FR
RFF+GN:775661390
NAD+DP+3025610011007::9++FNAC SA
C/O FNAC LOGISTIQUE+2 A 3 RUE DES CHAMPARTS+MASSY CEDEX++91742+FR
NAD+SE+3012901500000::9++PHILIPS France:Division P.E.G.P - PCE+64, rue Carnot - BP301+Suresnes Cedex++92156+FR
RFF+GN:402805527
LIN+1++8710895738125:EN
IMD+E+ANM+:::TV DVD36CM 4/3
ALC+C+3001000002138+6+1+TX:::Tape Tax
MOA+23:3
TAX+7+VAT++6.00+:::19.600+S
ALC+C+3001000002336+6+1+TX:::Battery Tax
MOA+23:5
TAX+7+VAT++10.00+:::19.600+S
ALC+C+3001000002459+6+1+TX:::Environmental charge
MOA+23:0.84
TAX+7+VAT++1.68+:::19.600+S
ALC+A++2+1+TD:::remises commerciales
PCD+1:13.04
MOA+204:60.00
MOA+204:90.00
UNS+S

16-May-08

Approach to ALE/EDI Development

Structured approach to develop ALE and EDI Interfaces.

Identification of Interface. Check the ALE/EDI functionality supported for appl. area
5 steps are involved in developing ALE and EDI Interfaces
1.
Prototype the interface to determine the std. functionality delivered
by R/3.
2.
Gap analysis Compare the requirements of the interface with the
result of prototyping
3.
Design and develop Interface to fit the gaps
4.
Data mapping Interface between R/3 and external system.
5.
Testing - Interface tested in all ALE layers

16-May-08

Components Used in ALE/EDI

Logical System
Message Type
Idoc Type
Port
RFC Destination
Partner Profile
Process Code
Customer Distribution Model

16-May-08

Components Used in ALE/EDI

Logical System(LS)
Representation of an R/3 System or External system in SAP R/3
Distribution of data to and from R/3 System.
R/3 Client has to have Base Logical System associated with the client.
Logical system becomes sender for outbound messages.
Logical system becomes receiver for inbound messages.
In addition to the base logical system, an LS should be created within that R/3 system
for each R/3 or external system.
Data for logical system stored in tables TBDLS and TBDLST.
Configured through the transaction SALE

16-May-08

Configuration of Logical system using SALE

Components Used in ALE/EDI

Logical System(LS)

16-May-08

10

Defining Logical System

16-May-08

11

Assign Client to Logical System

16-May-08

12

Configuring Logical System

16-May-08

13

Components Used in ALE/EDI

Message
It represents a specific type of document that is transmitted between two partners.

E.g. Orders, order responses, shipment notices, etc.

Message Type [Transaction Code : WE81 ]
A message type represents application message being exchanged between R/3
systems and R/3 and an external system.
Characterizes the data being sent across the systems and relates to the structure of
data.
Example MATMAS, INVOIC.

16-May-08

14

IDOC (Intermediate Document)

Data container
Inbound and outbound messages
Unique number
Stored in SAP database.
Idocs are based on EDI Standard - EDIFACT
ALE and EDI Integration.
Idocs are independent of sending and receiving system.
Idocs are independent of the direction of data exchange.
Idocs can be viewed as text editor. Data is stored in character format.
An Idoc consists of 3 record types
Structure Table
1. Control record (one per IDOC)
EDI_DC EDIDC
2. Data record (Several)
EDI_DD EDID2
3. Status record (Several)
EDI_DS EDIDS

16-May-08

15

Structure of an Idoc

Control Record

IDoc-ID
Sender-ID
Receiver-ID
IDoc and message type

Data Record

IDoc-ID
Sequence/Hierarchy
Segment
Format definition for
header data
item data

Status Record

IDoc-ID
Status information

16-May-08

16

Idoc Type

Idoc Type [Transaction Code : WE30 ]

An idoc type represents the structure of the data associated with the message type.
An Idoc is an object with the data of a particular message type.
An idoc contains one and only one business object.
Example. An idoc of type SHPMNT01 message type SHPMNT.
An Idoc type has the following characteristics
1. Name
2. List of permitted segments
3. Arrangement (sequence) of segments
4. Mandatory v/s optional
5. Minimum/Maximum range for each segment

16-May-08

17

ZMONREP04

SEGMENTS

IDOC type

Z1EMHDR
Z1WKDET
Z1CLDET

(M,1,1)

(O,1,999
999)
(O,1,1)

LNAME
(10)
WEEKNO
(1)
CLSITE
(20)

FNAME
(10)

SSN
(11)

TOTHOURS
(3)

DOB
(8)
HRLYRATE
(3)

WORKDESC
(40)

M - Mandatory
O - Optional

ZISUMRY

(O,1,1)

TOTHOURS
(3)

TOTAMOUNT
(10)

16-May-08

18

Idoc type structure Transaction WE60

16-May-08

19

IDOC structure - Segments

Segments [Transaction code : WE31]
Defines the format and structure of a data record.
Segments are reusable.
Segment consists of various fields.
Fields can be of 2 types.
1. Positional : Data field occupies fixed position in Idoc
2. Qualifier : Value represented in a field is tied to the qualifier.
Control records (one per IDOC)
Data segments (several)
Status records (several)
IDOC packages (several IDOCs)

16-May-08

20

Idoc Records
Control record
Contains all of the control information about an idoc.
Idoc number
Sender/Receiver
Message type and basic IDOC type
Data records
Idoc contains the application data.
Comprise the basic IDOC type or container
Name and version
Contain data fields
Structured and Nested segments
Qualifiers
A data record has 2 types
(1) An administrative section
(2) A data section

16-May-08

21

Idoc Records
Data Record
Idoc number Segment No Segment Name

Administrative section

1000 bytes of application data

Data Section

Administrative Section : Contains segment name, segment number and Hierarchy level
Data Section is a stream of 1000 bytes where actual data resides

Status Records
- Contain processing information
- Are never transmitted

16-May-08

22

Advantages
Loose coupling processes
Exception handling
Monitoring and test tools
Create and extend Idocs

16-May-08

23

Components Used in ALE/EDI

RFC Destination
It is a logical name.
Used to define the characteristics of a communication link to remote system.
On which function to be executed.
A basic prerequisite for the RFC destination is that the systems should be accessible to
each other via TCP/IP or one of the supported network protocols
Transaction Code : SM59

16-May-08

24

Setting RFC Destination

16-May-08

25

Components Used in ALE/EDI

Port [Transaction Code : WE21]
A logical representation of communication channel in SAP.
There are 4 types ports
1.
tRFC (Transactional RFC)
2.
File
3.
R/2
4.
Internet
ALE uses all tRFC ports to distribute Idoc.
EDI uses File based port
R/2 system ports - communicate with R/2 systems
Internet ports - connect with Internet applications.

16-May-08

26

Setting Transactional RFC Port

16-May-08

27

Components Used in ALE/EDI

Partner Profile [Transaction Code : WE20]
An identifier for a system used for communicating messages.
There are 4 types of partner profile.
1
KU for customer
2
LI for vendor
3
B for Bank
4
LS for Logical System
KU,LI and B are used for EDI partners.
LS is used for ALE communications
Maintain Inbound parameter, Outbound parameter and Message control
Main parameters are message types, idoc types, process codes, partner functions,
application identifiers, message function, output type and port. processing option
(Batch/Immediate)
It routes the specified messages through defined idoc types to a given port.

16-May-08

28

Maintain Partner Profile

16-May-08

29

Setting Partner Profile

16-May-08

30

Outbound Partner Profile - Parameters

Outbound Profiles Parameter Details

16-May-08

31

Outbound Partner Profile - Parameters

Outbound Profiles Message Control Details

16-May-08

32

Inbound Partner Profile - Parameters

Partner Profiles Main Screen WE20

16-May-08

33

Inbound Partner Profile - Parameters

Inbound Profile Parameter Details

16-May-08

34

Inbound Partner Profile - Parameters

16-May-08

35

Components Used in ALE/EDI

Process Code
Used in both ALE and EDI
Identify the function module for subsequent processing
An inbound uses process code to determine the application module.
An outbound uses process code only in case Message control.
Each process code associated with message type.
O/B Process codes are stored in table TEDE1 [ Transaction Code: WE41]
I/B Process codes are stored in table TEDE2 [ Transaction Code: WE42]

16-May-08

36

Setting Partner Profile

16-May-08

37

Components Used in ALE/EDI

Customer Distribution Model [Transaction Code : BD64]
Flow of messages across various system.
Message flowing to Logical Systems.
Many messages to one logical system
One message can flow to several systems.
Filtering of data.
Automatic Generation of PP.

16-May-08

38

Configuring Customer Distribution Model

16-May-08

39

ALE/EDI differences
ALE
Source SAP system
Destination SAP system
Data transfer via memory
EDI
Source SAP system destination external
Source external destination SAP system
Data transfer via file
Similar inbound and outbound process

16-May-08

40

Type of Inbound Process

The inbound process also has two distinct paths for posting the application
documents from the Idocs:
Via Function Module
Via Workflow

16-May-08

41

Inbound ALE/EDI process via Function module

Application
document

Posting program (function module)

IDOC

ALE/EDI interface

IDOC

- process IDOC data

- store application document

- Application Layer

- check IDOC syntax

- IDOC conversion
- read partner profile (use IDOC control record)
- store IDOC in database - Distribution Layer

Communication Layer

Port

16-May-08

42

Inbound ALE/EDI process

Communication Layer
IDOC received and does the basic integrity check
Distribution Layer
Filtering and Conversions (Version)
Add Application IDOC to database
Application Layer
Validate - read partner profile
Partner identified by number/type/function
Message identified by type/code/function
Idoc is marked ready for dispatch (Status : 64 Idoc ready to be passed to appl). If
option is background.
Idoc is passed to the posting program
Application document created (Status = 53) If option is immediate

16-May-08

43

SAP EDI Process-Inbound

EDI Enabled
Application

The EDI transmission is received

From EDI document to IDOC conversion
Transfer of IDOC to SAP Layer
The application document is created

Selection
Program
Inbound
Trigger
Program

EDI Subsystem/
Translator
EDI message
(ANSI X.12,
EDIFACT )

16-May-08

44

Type of Outbound Process

The Outbound Process has two distinct paths for creating IDOC:
With Message Control
Directly-without Message Control

16-May-08

45

Outbound ALE/EDI process

Application Layer
Direct IDOC creation (ALE)

Output type (EDI)

Check message control record partner profile

MASTER_IDOC_DISTRIBUTE
NAST
RSNASTED

Execute FM linked to processing

code and found In partner profile

- filtering and conversions

- store data in IDOC

ALE/EDI interface services

(optional) collect IDOCs
IDOC

RSEOUT00

IDOC

Port
16-May-08

46

Outbound ALE/EDI process Without Message control

Direct (ALE) Without Message Control
Select data from DB
Create IDOC using MASTER_IDOC_CREATE
Master idoc creation
Receiver Determination
Read Partner Profile
Idoc filtering and conversions.
Communication IDocs are generated
Syntax check performed.
1. 26 If errors are found
2. 30 if no errors (Idoc ready for dispatch)
Idocs are dispatched to the communication Layer

16-May-08

47

SAP EDI Process-Outbound

EDI Enabled
Application

Selection
Program
Outbound
Trigger
Program

The Application document is created

The IDOC is generated
IDOC from SAP to operating layer
IDOC to EDI Standards conversion
EDI document transmission
EDI subsystem reports status back to
SAP

EDI Subsystem/
Translator
EDI message
(ANSI X.12,
EDIFACT )

16-May-08

48

Application

Procedure

Output Type - Mail

Access Sequence

Condition Table

Procedure

Active Procedure

Output type - Fax

Output Type - EDI

Access Sequence

Access Sequence

Condition Table

Data Field Data Field Data Field

Data Field

Condition Table

Data Field

Data Field

Condition Table

Data Field

16-May-08

49

Outbound ALE/EDI process With Message control

(Architecture)
SD and MM applications use Message control for output determination.
Message Control can be reached via transaction NACE
Components of Message Control
1. Application ID: Capable of generating outputs are assigned a 2 character.
Example : V1 Sales Order. EF Purchasing Application
2. Communication Structure: It pass application information to MC.
Communication Structure acts as container.
Each application has its own application structure.
Naming Convention : KOMxByy x can be K or P.
yy is two char application id.
KOMKBV1 is the communication structure for Sales order
header information.

16-May-08

50

Outbound ALE/EDI process With Message control

3. Procedure : A Procedure defines set of possible outputs for an application.
An application can have several procedures but only one can be configured
and active.
A procedure has 3 main attributes
1 List of output types 2.Requirement field 3 Manual flag.
List of output types represents a set of outputs possible for an application.
Example : Output types applicable for a sales order.
A> Sales Order response
B> Internal Message
C> Hard copy output
Output types can have some preconditions defined for it.
Example : Sales order response should not be sent unless the sales order
is complete. These preconditions are captured in the requirements.
A requirement is implemented in ABAP/4 program. List of requirements can be viewed
using transaction VOFM.

16-May-08

51

Outbound ALE/EDI process With Message control

4 Output types : An output type defines the characteristics and attributes of the output
itself. Examples of output types available for Sales Order are
1. BA00(Sales order response)
2. ESYM (Internal output)
3. MAIL (Mail)
Attributes defined for an output type
a) A name with 4 characters. Example BA00,ESYM
b) Access sequence, which is basically set of business rules
c) Condition Access Flag. If this flag selected. Values for output medium, timing are
determined from the condition table. If this flag is not selected then values would be
determined from master (Customer. If the application is V1)
c) Default medium for transmission (EDI, print, Mail, ALE)
d) Default timings (Immediate or batch)
An output type can be marked as manual in a procedure.

16-May-08

52

Outbound ALE/EDI process With Message control

e) Whether multiple outputs are permitted
f) Whether multiple outputs can be edited
5. Access Sequence :
It defines a sequence in which the business rules are checked for proposing an output
type.
Business rule checked by Comparing the values ( application data v/s values in the
Condition records of the condition table). If match occurs output values from condition
table.
An access sequence is given a 4 character name, usually a number and has the
following attribute
a>A set of business rules or conditions
b>A sequence in which they are checked
c>A requirement that checks for the business rules using ABAP program.
d>exclusive or inclusive

16-May-08

53

Outbound ALE/EDI process With Message control

6. Condition table:
It specifies the key fields for a business rule.
The key is used to access the condition records for output values like output medium,
partner function, partner number, language and time for the message.
7. Condition Records :
Condition records are inserted in the condition table.
Condition records contain actual data against which the business rules checked to
propose an output

16-May-08

54

Outbound ALE/EDI process With Message control

Processing Programs and Tables
1. Tables
NAST : Stores an entry for each output type along with an application document,
output type, timing and language.
TNAPR : Processing program entry used for an output type
2 Programs
RSNAST00 : Used to process the entries in NAST table
RSNASTED : In case of EDI process the routine EDI_processing.
In case of ALE Process the routine ALE_processing
Read Partner Profile and determine Process code.
FM has input and output parameters. One of the input parameter is NAST entry and
has application data.
The output parameter of FM are Idoc.

16-May-08

55

EDI Scenario

Sales Order (ORDE)

SAP R/3 System

Customer
Invoice SD09

Purchase Order
ME10

Vendor

Invoice
Verification
INVM

Payment

Payment
Advice
REMA

Payment Order

Bank

16-May-08

56

Master data distribution

Direct
Transaction generates Idocs
E.g. KE77 send profit centers
BD10 Send Material
BD11 Send Customer
Shared Master Data Tool
Based on change documents

16-May-08

57

Shared Master Data Tool

16-May-08

58

Change Pointer Configuration

The following Steps to be carried out for Change
Pointer Configuration
Step1 : Enable Change Pointers globally
(Transaction BD61)
Step2 : Enable Change Pointers for a message
Type (Transaction BD50)
Step3 : Specify the fields for which change pointers
are to be written (Transaction BD52)
Step4 : Executing the program RBDMIDOC to
process change pointers

16-May-08

59

ALE/EDI and IDOC Transactions

Main Menu
WEDI Main menu for EDI related activities
BALE Main menu for ALE related activities
SALE Main menu for ALE configuration
NACE Main menu for Message Control configuration
Idoc definition and Monitoring
WE31 Segment editor
WE30 Idoc editor to create and extend idoc type
WE60 IDOC documentation
WE19 Test
WE05 IDOC lists
WE02 IDOC display
Configuration
WE20 Partner Profiles
WE21 Port definition
SM59 RFC Destination

16-May-08

60

ALE/EDI and IDOC Transactions

Reprocessing Idocs
BD87 Process Outbound idocs
BD88 Process Inbound idocs
Configuration of new components
WE81 Create new message type
WE82 Link idoc type and message type
WE41 Create outbound process code
WE42 Create inbound process code
BD64 Maintain customer distribution model.

16-May-08

61

IDOC Status code

Outbound
Status Code
01
03
06
08
10
30
Inbound
50
51
52
53
64

Description
Idoc Created
Data passed to port OK
Translation OK
Syntax check OK
Interchange handling OK
Idoc ready for dispatch
Idoc added
Error Application document not posted
Application document not fully posted
Application document posted
Idoc ready to be passed to application

16-May-08

62

Periodic Processing
SAP Provides several programs to maintain ALE and EDI Interfaces.
These programs can be scheduled as job to run periodically (If required online).
1. Outbound Processing
a> RBDMIDOC : Create Master data Idocs based on change pointers.
Input : Message Type.
Flag would be updated as Processed in BDCPS table
This program can be scheduled periodically to process change
pointers for that message type.
b>RBDSE* : Can be used to create master data IDOCs. [Eg. RBDSEMAT: Creates
material master idocs]
The parameters and selection options vary based on application.
Message type is mandatory.
Eg. RBDSEDEB, RBDSEBOM, RBDSEGLM
This program can be scheduled as batch job in order to refresh or sync
up the data in the other R/3 Systems.

16-May-08

63

Periodic Processing
c> RSNAST00 : Used to create idocs from NAST table.
Used for SD and MM applications.
Supported by message control mechanism
This program is applicable only for timing 4 (Immediate)
Parameters : Application, output type and output medium.
Ensure message control parameters in PP (Output type and Process
code).
This can be scheduled periodically to capture trans data [
created/changed ] to create Idocs.
d>RSEOUT00 : Used to dispatch O/B idoc from 30 status to 03 status (Port).
processing option is collect idocs in PP.
In order to move from status 30 to 03.
Parameters : Message type, receiver info. Idoc number etc
This program can be scheduled periodically to send idocs to out of
the system to another R/3 or external system.

16-May-08

64

Periodic Processing
c> RBDAGAIN : Used for processing idocs with errors.
Valid Statuses : 26 Error during transmitting data to port.
04 Error in EDI subsystem control information
05 Error during translation
25 continue processing despite syntax error
29 Error in ALE service
This program reprocesses these idocs.
Based on processing option status would be moved to 30
or 03.
Parameters: Idoc number, creation date, time, message type etc.
There is checkbox Import in Background
Program attempts to reprocess them in background flagged
Idocs would be processed one after the other not flagged
Generate new idoc with status 30 or 03 based on original idoc.
Original idoc is then placed in status 33 (original of an idoc edited)

16-May-08

65

Periodic Processing
2. Inbound Processing
a>Program RSEINB00
It is used to import files containing idocs into R/3.
This program is used only for inbound idoc.
Parameter : path and file name.
Based on processing option idocs are created in status 64.
b>Program RBDAPP01
It is used to process the idocs that have not been posted to the application.
Valid status : 64
This program posts Idoc data to the application.
Parameter : Idoc number, date, message type, partner details.

16-May-08

66

Periodic Processing
c>Program RBDMANIN
Reprocessing inbound idocs.
Valid status : 51.
This program attempts to post the data to the application.
Parameters: Idoc number, date, time, message type and partner
details.
Import in background Idocs processed in background. If the flag
is checked.
Idocs are displayed and processed individually. If the flag is
unmarked.

16-May-08

67

Periodic Processing
c>Program RBDMANIN
Reprocessing inbound idocs.
Valid status : 51.
This program attempts to post the data to the application.
Parameters: Idoc number, date, time, message type and partner
details.
Import in background Idocs processed in background. If the flag
is checked.
Idocs are displayed and processed individually. If the flag is
unmarked.

16-May-08

68

Periodic Processing
d>Program RBDAGAI2
Reprocessing inbound idocs with errors.
Valid status : 56 Idoc containing errors.
61 Continue processing despite syntax error.
63 Error passing Idoc to the application
65 Error in ALE service
Parameters : Idoc number, date, time, message type and partner
details.
This program has a flag for Importing in background which process
the idocs in background.
If the checkbox is unmarked Idocs are displayed for individual
processing.

16-May-08

69

Idoc Archiving
Overview.

In production, large number of idocs of different messages get created on R/3.

Successfully processed idocs needs to be taken out from R/3
SAP has delivered a mechanism called Archiving
Idoc archiving is similar to the archiving of objects in various applications SD,MM & FI.
In ALE/EDI an idoc object known as IDOC can be archived
Enabled through ADK
SARA central archiving transactions.

16-May-08

70

Idoc Archiving
Preliminary configuration

Enable certain idoc status for archiving [Transaction WE47]

Choose the status through the options possible or exclude.
Maintain & designate physical file path for a logical file name.
Transaction : SF02.
Authorization to perform archiving functions.
For the user id, authorization BATCH_ADMIN_ID = Y
Object S_IDOCCTRL activity 24 in your security profile

16-May-08

71

Idoc Archiving
Archiving Programs
An archiving object (IDOC) comprises of 4 programs
1.
Archiving program
2.
Deletion program
3.
Analysis program
4.
Reload program
1 Archiving Program
-Selection of documents and write those documents into a file
-Documents are present in SAP.
RSEXARCA and RSEXARCB are archiving programs.
RSEXARCB is designed for periodic schedules.

16-May-08

72

Idoc Archiving
2. Deletion Program
Input : archive file
Reads various documents in archive file and documents are then get deleted from
SAP System.
RSEXARCR Reads from archive file
RSEXARCD Deletion program
3. Analysis program
Input : archive file
Analyze the data stored in archive file and generate report.
4. Reload Program
Input : Archive file
Allows you to reload one or more objects from archive back to SAP DB table
RSEXAECL Reload program

16-May-08

73

Thank You

16-May-08

74