AB1005 - Data upload - BDC, Call Transaction v1.

India SAP CoE, Slide 1

Data upload - BDC, Call Transaction

1 2

Introduction Syntax Description

3

Demonstration
Exercises Help Me

5
India SAP CoE, Slide 2

Data upload - BDC, Call Transaction

1 2

Introduction Syntax Description

3

Demonstration
Exercises Help Me

5
India SAP CoE, Slide 3

Introduction
Purpose Use

India SAP CoE, Slide 4

Purpose
BDC stand for BATCH DATA COMMUNICATION Through this concept we transfer the data into SAP R/3 System Legacy System R/3 System

Data

BATCH INPUT

India SAP CoE, Slide 5

Purpose

cont.

Batch input is used to transfer large amounts of data into the SAP system. In this topic, we will learn the basics of batch input. There are 2 types of transfers Conversions and interfaces. Conversions: This type of transfer refers to a one-time transfer from a legacy system to the SAP system. In this case, the legacy system is the old system that is being replaced by the SAP system. Interfaces: This type of transfer refers to an ongoing transfer from a complementary system to the SAP system. In this case, the complementary system is a system that will run along side the SAP system.

India SAP CoE, Slide 6

Use
This is used for uploading the master data and different type of application data from legacy system to SAP R/3 system like as: Create Vendor using transaction (FK01), Change Vendor using transaction (FK02)

India SAP CoE, Slide 7

Data upload - BDC, Call Transaction

1 2

Introduction Syntax description

3

Demonstration
Exercises Help Me

5
India SAP CoE, Slide 8

Reading data from application server or presentation server

Presentation server

WS_UPLOAD

ABAP/4 PROGRAM

Application server

Internal table

Read Dataset

India SAP CoE, Slide 9

Dialog Program
A dialog program conducts a dialog with the user. As a result of user input the program executes which in turn displays an output or changes the database in a consistent way. A transaction code can be connected to dialog program which calls the corresponding program

India SAP CoE, Slide 10

Structure of a dialog program

India SAP CoE, Slide 11

Procedural steps in data migration

Data Transfer Program

BDC Program.

India SAP CoE, Slide 12

Concept Of Customer Transfer Program

Sequential file 1

India SAP CoE, Slide 13

Concept Of Customer Transfer Program cont.

USING ABAP/4 PROGRAMS

USING EXTERNAL PROGRAMS

India SAP CoE, Slide 14

Concept Of Customer Transfer Program

India SAP CoE, Slide 15

BDCDATA Structure

To simulate user dialogue, you must know the following information: 1. Online program name, 2. Screen numbers, 3. Field names 4. Field values

ABAP Dictionary BDCDATA

The BDCDATA ABAP Dictionary structure is used in a batch input program to collect this information for an entire transaction.
India SAP CoE, Slide 16

PROGRAM DYNPRO DYNBEGIN FNAM FVAL

Example - Change Vendor

Vendor

TEST1

For our example, we will use the Change Vendor transaction (FK02) to add a street address to an already existing vendor.

Company code

Address

Name Street City

Computers, Inc 123 Main St. Philadelphia

India SAP CoE, Slide 17

Researching Transaction 2nd Screen

Step #1 Use SystemStatus menu path to determine online program name (SAPMF02K), screen number (0110) Step #2 Use F1 key and Technical Info pushbutton in each screen field to be filled to determine the field name.

Name

Computers, Inc

Street
City

123 Main St.

Philadelphia

Step #3 Determine how to proceed in the transaction (save the record by clicking on the Save pushbutton or pressing the F11 key).

India SAP CoE, Slide 18

BDC Table Contents

After researching the transaction we can determine the contents of the BDC table.

PROGRAM SAMPF02K

DYNPRO DYNBEGIN 0106 X

FNAM

FVAL

RF02K-LIFNR RF02K-D0110 SAMPF02K 0110 X LFA1-STRAS BDC_OKCODE

India SAP CoE, Slide 19

TEST1 X 123 Main St. /11

Batch Input Methods

METHOD #1 CALL TRANSACTION USING STATEMENT

METHOD #2 METHOD #3

BATCH INPUT SESSION

DIRECT INPUT

India SAP CoE, Slide 20

Call transaction - for data transfer

Processing batch input data with CALL TRANSACTION USING is the faster of the two recommended data transfer methods. In this method, legacy data is processed inline in your data transfer program. Syntax: CALL TRANSACTION <tcode> USING <bdc_tab> MODE <mode> UPDATE <update>

A Display all E Display errors only N No display

S Synchronous A Asynchronous L Local update

India SAP CoE, Slide 21

The process flow of CALL TRANSACTION

A program that uses CALL TRANSACTION USING to process legacy data should execute thefollowing steps:

Prepare a BDCDATA structure for the transaction that you wish to run.
Prepare a internal table to store error messages Tab_Mess like structure of BDCMSGCOLL. With a CALL TRANSACTION USING statement, call the transaction and prepare the BDCDATA structure. For example: CALL TRANSACTION MM01' USING BDCDATA MODE 'A' UPDATE 'S'. MESSAGES INTO TAB_MESS.
Value 0 <=1000 Explanation Successful Error in dialog program Batch input error

IF SY-SUBRC <> 0.
<Error_handling>. ENDIF.

> 1000

India SAP CoE, Slide 22

Overview of Batch Input Session

BDC PROGRAM External Data The first batch input method is to create a batch input session. It is the processing of this batch input session that updates the database, not the execution of the batch input program.

BATCH INPUT SESSION

SAP DATABASE TABLE

India SAP CoE, Slide 23

Process flow of Batch Input Session

Opens the Session

Process BDC table for each record

Close the Session

India SAP CoE, Slide 24

Function Modules

BDC_OPEN_GROUP
CALL FUNCTION BDC_OPEN_GROUP EXPORTING CLIENT GROUP HOLDDATE KEEP USER EXCEPTIONS CLIENT_INVALID .. OTHERS = 11. =1

= = = = =

<client> <session name> <lock session until date> <keep or delete session> <user name>

India SAP CoE, Slide 25

BDC_INSERT
CALL FUNCTION BDC_INSERT EXPORTING TCODE TABLES DYNPROTAB EXCEPTIONS INTERNAL_ERROR .. OTHERS = 5. =1 = <bdc internal table> = <transaction code>

India SAP CoE, Slide 26

BDC_CLOSE_GROUP
CALL FUNCTION BDC_CLOSE_GROUP EXCEPTIONS NOT_OPEN QUEUE_ERROR OTHERS =1 =2 =3

India SAP CoE, Slide 27

Batch Input Session Structure

Header Section Creator Client Session Name Authorization User Hold Date Keep or Delete

Batch Input Session

Data Section Transaction Data

India SAP CoE, Slide 28

Processing Batch Input sessions

When you create a batch input session, it remains in the batch input queue until it is explicitly started. Session processing can be started in two ways:

An on-line user can start the session using the batch input menu options. (To access the batch input options, choose System

Services Batch Input.)

SM35

You can submit the background job RSBDCSUB to start a session in background processing. If several sessions have the same name, RSBDCSUB starts them all.

India SAP CoE, Slide 29

Direct Input
To enhance the batch input procedure, the system offers the direct input technique, especially for transferring large amounts of data. In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not process screens. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. To maintain and start these programs, use program RBMVSHOW or Transaction BMV0. It is better to use BDC method unless data volume is very high, as validations are very critical to data upload in SAP. Examples for direct input programs are:

India SAP CoE, Slide 30

Data upload - BDC, Call Transaction

1 2

PrepareMe Syntax Description

3

Demonstration
Exercises Help Me

5
India SAP CoE, Slide 31

Demonstration
Transaction Recorder (SHDB) How to Upload Presentation Server Flat file to SAP R/3 system??? How to upload application server file to R/3 system? Definition Example - Call Transaction Method Error Handling Example- Batch Input Method Summary
India SAP CoE, Slide 32

Transaction Recorder (SHDB)

Before you work with the Batch Input methods, you should know the purpose of the tool Transaction Recorder. Use: You can use the transaction recorder to record a series of transactions and their screens. Features: You can use the recording to create Data transfer programs that use batch input or CALL TRANSACTION Batch input sessions Test data Function modules. Note: It doesnt record F1, F4 and Scrollbar movements
India SAP CoE, Slide 33

Transaction Recorder Overview

India SAP CoE, Slide 34

Transaction Recorder Overview

India SAP CoE, Slide 35

Transaction Recorder Overview

India SAP CoE, Slide 36

Upload Flat file from Presentation Server to SAP R/3

CALL FUNCTION GUI_UPLOAD' EXPORTING

CODEPAGE
FILENAME FILETYPE TABLES DATA_TAB EXCEPTIONS

= IBM'
= P_UFILE = 'DAT'

= INT_TAB

CONVERSION_ERROR FILE_OPEN_ERROR FILE_READ_ERROR INVALID_TYPE NO_BATCH UNKNOWN_ERROR INVALID_TABLE_WIDTH =4 =5

=1 =2 =3

=6 =7

GUI_REFUSE_FILETRANSFER = 8
CUSTOMER_ERROR OTHERS = 10 . =9

IF SY-SUBRC NE 0. MESSAGE E999(FR) WITH 'ERROR IN FILE UPLOAD'. ENDIF.

India SAP CoE, Slide 37

Upload file from application server to SAP R/3

Open the the application server file
OPEN DATASET <dsn> FOR INPUT <mode>

Read the data from application server file

READ DATASET <dsn> INTO <wa>

And then close the application server file CLOSE DATASET <dsn>
India SAP CoE, Slide 38

Definition- Declaring BDC Table

DATA: BDC_TAB LIKE STANDARD TABLE OF BDCDATA INITIAL SIZE 6 WITH HEADER LINE .

The internal table used to collect the transactions information must be declared LIKE BDCDATA.

India SAP CoE, Slide 39

Filling BDC Table Method #1

FORM FILL_BDC_TAB. REFRESH BDC_TAB. CLEAR BDC_TAB. BDC_TAB-PROGRAM = SAPMF02K. BDC_TAB-DYNPRO = 01016. BDC_TAB-DYNBEGIN = X. APPEND BDC_TAB. CLEAR BDC_TAB. BDC_TAB-FNAM = RF02K-LIFNR. BDC_TAB-FVAL = TEST1. APPEND BDC_TAB. CLEAR BDC_TAB. BDC_TAB-FNAM = RF02K-D0010. BDC_TAB-FVAL = X. APPEND BDC_TAB. CLEAR BDC_TAB. BDC_TAB-PROGRAM = SAPMF02K. BDC_TAB-DYNPRO = 0110. BDC_TAB-DYNBEGIN = X. APPEND BDC_TAB. CLEAR BDC_TAB. BDC_TAB-FNAM = LFA1-STRAS. BDC_TAB-FVAL = 123 Main St.. APPEND BDC_TAB. CLEAR BDC_TAB. BDC_TAB-FNAM = BDC_OKCODE. BDC_TAB-FVAL = /11. APPEND BDC_TAB. ENDFORM.

India SAP CoE, Slide 40

Filling BDC Table Method #2

FORM FILL_BDC_TAB. REFRESH BDC_TAB. PERFORM POPULATE_BDC_TAB USING: 1 SAPMF02K 0106, RF02K-LIFNR TEST1, RF02K-D0010 X, 1 SAPMF02K 0110, LFA1-STRAS, 123 Main St., BDC_OKCODE, /11. CLEAR BDC_TAB. IF FLAG = 1. BDC_TAB-PROGRAM = VAR1. BDC_TAB-DYNPRO = VAR2.. BDC_TAB-DYNBEGIN = X. ELSE. BDC_TAB-FNAM = VAR1. BDC_TAB-FVAL = VAR2. ENDIF. APPEND BDC_TAB. FORM POPULATE_BDC_TAB USING FLAG VAR1 VAR2.

ENDFORM.
ENDFORM. This two subroutine method to fill the BDC table is preferable because the POPULATE_BDC_TABLE subroutine is reusable throughout all batch input programs.

India SAP CoE, Slide 41

Example #1 - Change Vendor (Call Transaction Method)

To illustrate the CALL TRANSACTION methods, we will use the example to change vendors coming from a sequential file

.
Vendor Company code

Vendor Company code

TEST1

TEST2

Address

Address

Name Computers, Inc Street 123 Main St. City

Name Street City

Computer Land
10 Walnut St. Boston

Philadelphia

India SAP CoE, Slide 42

Example #1- Declaration Section

REPORT Y180DM10.
Step #1 Step #2 DATA: BDC_TAB LIKE STANDARD TABLE OF BDCDATA INITIAL SIZE 6 WITH HEADER LINE. INFILE(20) VALUE /tmp/bc180_file4. DATA: BEGIN OF INREC. VENDNUM LIKE LFA1-LIFNR. STREET LIKE LFA1-STRAS. END OF INREC. PARAMETERS: DISPMODE DEFAULT A, UPDAMODE DEFAULT S.

***** This program is continued on the next slide*****

India SAP CoE, Slide 43

Example #1 Main Program

Step #3 START-OF-SELECTION. OPEN DATASET INFILE FOR INPUT IN TEXT MODE. DO. READ DATASET INFILE INTO INREC. IF SY-SUBRC < > 0. EXIT. ENDIF. PERFORM FILL_BDC_TAB. CALL TRANSACTION FK02 USING BDC_TAB MODE DISPMODE UPDATE UPDAMODE. IF SY-SUBRC < > 0. WRITE: /ERROR. ENDIF. ENDDO. CLOSE DATASET INFILE.

Step #4 Step #5 Step #6 Step #7

Step #8

Step #9

*** This program is continued on the next slide ***

India SAP CoE, Slide 44

Example #1 - Subroutines
FORM FILL_BDC_TAB. REFRESH BDC_TAB. CLEAR BDC_TAB. PERFORM POPULATE_BDC_TAB USING: 1 SAPMF02K 0106, RF02K-LIFNR INREC-VENDNUM, RF02K-D0010 X, 1 SAPMF02K 0110, LFA1-STRAS, INREC-STREET, BDC_OKCODE, /11. ENDFORM. IF FLAG = 1. BDC_TAB-PROGRAM = VAR1. BDC_TAB-DYNPRO = VAR2.. BDC_TAB-DYNBEGIN = X. ELSE. BDC_TAB-FNAM = VAR1. BDC_TAB-FVAL = VAR2. ENDIF. APPEND BDC_TAB. ENDFORM. FORM POPULATE_BDC_TAB USING FLAG VAR1 VAR2.

India SAP CoE, Slide 45

Synchronous versus Asynchronous

DO. PERFORM FILL_BDC_TAB. CALL TRANSACTION FK02 USING BDC_TAB MODE N UPDATE S. IF SY-SUBRC < > 0. WRITE: /ERROR. ENDIF. ENDDO. DO. PERFORM FILL_BDC_TAB. CALL TRANSACTION FK02 USING BDC_TAB MODE N UPDATE A. IF SY-SUBRC < > 0. WRITE: /ERROR. ENDIF. ENDDO.

With synchronous updating, we can check SY-SUBRC to determine the success of the transaction and the actual update to the database.

With asynchronous updating, we can check SY-SUBRC to determine the success of the transaction only, not the actual update to the database.

India SAP CoE, Slide 46

Error Handling

Write an error report.

ERROR

Send the record(s) in error to an error file. Create a batch input session with the record(s) in error.

India SAP CoE, Slide 47

Error Handling
To store error messages ( CALL TRANSACTION ) data: begin of Tab_Mess occurs 0. include structure bdcmsgcoll. data : end of Tab_Mess,

cont.

CALL TRANSACTION FK02 USING BDC_TAB MODE N UPDATE S MESSAGES INTO TAB_MESS. IF SY-SUBRC NE 0. WRITE: / Tab_MESS-TCODE, Tab_MESS-DYNUMB, Tab_MESSMSGTYP , Tab_MESS-MSGID. ENDIF.

India SAP CoE, Slide 48

Example #1- Change Vendor (Batch Input Session)

Vendor

TEST1

In this example, we will create a batch input session to add a street address to an already existing vendor (TEST1)

Company code

Address

Name

The Change Vendor transaction is FK02.

Computers, Inc 123 Main St. Philadelphia

Street City

India SAP CoE, Slide 49

Example #1 Declaration Section

REPORT Y180DM08. DATA: BDC_TAB LIKE STANDARD TABLE OF BDCDATA INITIAL SIZE 6 WITH HEADER LINE, SESSION LIKE APQ1-GROUPID VALUE DEMO #8.

Step #1

India SAP CoE, Slide 50

Example #1 Main Program

Step #2

Step #3

START-OF-SELECTION. CALL FUNCTION BDC_OPEN_GROUP EXPORTING CLIENT = SY-MANDT GROUP = SESSION USER = SY-USERNAME EXCEPTIONS. PERFORM FILL_BDC_TAB. CALL FUNCTION BDC_INSERT EXPORTING TCODE = FK02 TABLES DYNPROTAB = BDC_TAB EXCEPTIONS. CALL FUNCTION BDC_CLOSE_GROUP EXCEPTIONS.

Step #4

Step #5

***** This program is continue on the next slide *****

India SAP CoE, Slide 51

Example #1 - Subroutines
FORM FILL_BDC_TAB. REFRESH BDC_TAB. CLEAR BDC_TAB. PERFORM POPULATE_BDC_TAB USING: 1 SAPMF02K 0106, RF02K-LIFNR TEST1, RF02K-D0010 X, 1 SAPMF02K 0110, LFA1-STRAS, 123 Main St., BDC_OKCODE, /11. IF FLAG = 1. BDC_TAB-PROGRAM = VAR1. BDC_TAB-DYNPRO = VAR2.. BDC_TAB-DYNBEGIN = X. ELSE. BDC_TAB-FNAM = VAR1. BDC_TAB-FVAL = VAR2. ENDIF. APPEND BDC_TAB. ENDFORM. FORM POPULATE_BDC_TAB USING FLAG VAR1 VAR2.

ENDFORM.

India SAP CoE, Slide 52

Summary
Research Transaction

Code BDC Program

Execute BDC Program Batch Input Session Control Process Batch Input Session SAP Database Updated
India SAP CoE, Slide 53

Data upload - BDC, Call Transaction

1 2

Introduction Syntax Description

3

Demonstration
Exercises Help Me

5
India SAP CoE, Slide 54

Exercises
Exercise-01 Using call transaction method Mode N

Upload the attached file. Create the vendor using transaction XK01 Display the output report.

India SAP CoE, Slide 55

Exercises
Exercise -02 Using Batch Input Session Method Run Mode Background

Upload the attached file. Create the material master using transaction MM01 Create the session and run.

India SAP CoE, Slide 56

DATA UploadBDC /Call Transaction

1 2

Introduction Syntax Description

3

Demonstration
Exercises Help Me

5
India SAP CoE, Slide 57

Help Me

Additional Info Job Schedule Overview

India SAP CoE, Slide 58

Scheduling a Background Job

Transaction SM36 Job Scheduling

Start date
General data Job name Job class

Steps

<job name> A Scheduled <target system for processing>

Status
Target host

India SAP CoE, Slide 59

Creating Step for Background Job

Steps
Job Scheduling

ABAP/4

External program

ABAP/4 program
Name Variant Language <name of report program> <name of variant> E

India SAP CoE, Slide 60

Start Criteria for Background Job

Start date
Job Scheduling

Immediate

Date/Time

After Job

After Event
Jobs can be scheduled to run after an event has been triggered/raised.

Jobs can be scheduled to run immediately or at a particular date/time.

Jobs can be scheduled to run after another job has been completed.

If you start a job based on a date/time or an event, you can schedule the job to run at regular intervals, not just at a particular time.

India SAP CoE, Slide 61

Scheduling a Periodic Job

Start date
Period values
Job Scheduling

Periodic job

Hourly Daily

By checking the Periodic Job option, you can specify that the job run at regular intervals.

Weekly Monthly Other period

With the Period Values pushbutton, you can schedule the job to run hourly, daily, weekly, monthly, etc.

India SAP CoE, Slide 62

Scheduling Job after Another Job

Start date
After Job
Job Scheduling

Name <job name>

X Start status-depend.

After clicking on the After Job pushbutton, you must specify the name of the job that must be completed before this job will run.

If you check the Start status-depend. option, this job will run only if the specified job ends successfully.

India SAP CoE, Slide 63

Scheduling Job After an Event

Start date
After Event
Job Scheduling

Event Parameter

<event name>
<parameter>

After clicking on the After Event pushbutton, you must specify the name of the event that must be raised before this job will run. You can distinguish between different occurrences of a particular event by specifying a parameter.

X Periodic job

If you check the Periodic Job option, the system starts a new job each time the specified event is raised.

India SAP CoE, Slide 64

Triggering/Raising Events
To trigger/raise an event from within an ABAP/4 program, you must call the BP_EVENT_RAISE function module.

CALL FUNCTION BP_EVENT_RAISE EXPORTING EVENTID = <event name> EVENTPARM = TARGET_INSTANCE = EXCEPTIONS BAD_EVENTID =1 The only required EVENTID_DOES_NOT_EXIST = 2 exporting parameter is the EVENTID_MISSING =3 name of the event to raise. RAISE_FAILED =4 OTHERS = 5.

India SAP CoE, Slide 65

Phases of Background Processing

Job Scheduling

Job Processing

Job Overview

India SAP CoE, Slide 66

Processing a Background Job

Scheduler

Job

Dispatcher

Background Job Processing

Job

India SAP CoE, Slide 67

Processing a Background Job

Application Server Work Processes
8 Online
1 Spool 3 Background

Job Processing

Transaction SM50

India SAP CoE, Slide 68

Processing a Background Job

Job Log
Scheduler
Entries from start and end modules. All messages issued by job steps and system.

Start Module
Job Step #1 Job Step #2 Job Step #3 End Module

PRINT SPOOL
Job Processing

List
All WRITE statement output from job step.

India SAP CoE, Slide 69

Job Overview
Transaction SM37

Job Status

Job Overview

India SAP CoE, Slide 70

Other Background Processing Topics

Passing Data to Subsequent Job Steps

Scheduling Job within ABAP/4 Program

India SAP CoE, Slide 71

Passing Data to Subsequent Job Steps

Global ABAP/4 Memory
Background Job Step #1 ... EXPORT <data> TO MEMORY. ... Step #2 ... IMPORT <data> FROM MEMORY. ...

<data>

India SAP CoE, Slide 72

Passing Data to Subsequent Job Steps

Global ABAP/4 Memory Background Job Step #1 ... EXPORT <data2> TO MEMORY ID <id2>. ...

<id1> <data>

<id2> <data2>

Step #2 ... IMPORT <data2> FROM MEMORY ID <id2>. ...

India SAP CoE, Slide 73

Scheduling Job within ABAP/4 Program

Open Background Job JOB_OPEN
JOB_SUBMIT is called for each step that is to be added to the job.

Insert Job Step JOB_SUBMIT

Close Background Job JOB_CLOSE

India SAP CoE, Slide 74

JOB_SUBMIT
JOB_SUBMIT Exporting: authcknam = <user> jobcount = <job #> jobname = <job name> report = <report> variant = <variant> Background Job <job name> <job #> Step #1

Step #2

India SAP CoE, Slide 75

JOB_CLOSE
JOB_CLOSE Exporting: jobcount = <job #> jobname = <job name> sdlstrtdt = <start date> sdlstrttm = <start time> strtimmed = <flag1> Importing: job_was_released = <flag2> Background Job <job name> <job #> Step #1

Step #2

India SAP CoE, Slide 76

Session Overview
Process Batch Input Session

Transaction Code SM35

SystemServicesBatch InputEdit menu path

Session SESSION5 SESSION1

Date 01/04/97 01/04/97

Time [Link] [Link]

Locked 01/31/97

Created by DANTHON DANTHON

Tran 5 5

Screen 10 10

Authroisation DANTHON DANTHON

Session SESSION3

Date 01/04/97

Time [Link]

Locked

Created by DANTHON

Tran 1

Screen 2

Authorization DANTHON

India SAP CoE, Slide 77

Session Log
Log Created 01/08/1997 [Link]
Time [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] [Link] Tran FK02 FK02 FK02 Screen

Session name SESSION3

User DANTHON

Message S00300 Session SESSION3 is being SAPMF02K 0110 SF2056 Changes have been made SAPMF02K 0110 SF2056 Changes have been made SAPMF02K 0106 EF2163 Vendor TESTX has not been created S00370 S00363 S00364 S00365 S00366 S00382 Processing Statistics 3 transactions read 2 transactions processed 1 transactions with errors 0 transactions deleted Batch input processing ended

India SAP CoE, Slide 78

Processing Modes

Process Batch Input Session in the FOREGROUND DISPLAY ERRORS ONLY when processing batch input session.

Process Batch Input Session in the BACKGROUND

India SAP CoE, Slide 79

Processing Options
/bdel /n /bda /bde /bend Delete Transaction Next Transaction Process/Foreground Display errors only Cancel

India SAP CoE, Slide 80

Program RSBDCSUB

Execute Program RSBDCSUB

Specify batch input session to process

Batch input session scheduled to be processed in the background.

India SAP CoE, Slide 81

Important Tips
Function Modules:
GUI_UPLOAD -------Upload flat file from presentation server to application server FORMAT_MESSAGE---------Formats message WS_FILENAME_GET-------Call file selector BDC_OPEN_GROUP, BDC_INSERT, BDC_CLOSE_GROPUP----Create&Maintain Sessions

Transaction codes:
SM35-----Process session,

SHDB----Transaction Recorder tool,

BMV0----Maintain and start Direct input programs

DIRECT INPUT PROGRAM

Tables:
T100-------Table for Messages

Includes:
BDCRECXX, BDCRECXY, BDCRECX1.

Structures:
BDCDATA, BDCMSGCOLL
India SAP CoE, Slide 82

END of Session

India SAP CoE, Slide 83