topic Re: coding for maintain the multip[le sessions in Application Development and Automation Discussions

coding for maintain the multip[le sessions

Former Member — Wed, 13 Jun 2007 09:53:31 GMT

i have 1,00,000 records in a flat file how to maintain the multiple sessions

each session having 10000 records i want coding for how these multiple sessions

Re: coding for maintain the multip[le sessions

Former Member — Wed, 13 Jun 2007 10:44:56 GMT

Hi,

Read the documenetaion you will able to undresatand clearly.

Batch input sessions enter data non-interactively into an R/3 System. Batch input is typically used to transfer data from non-R/3 Systems to R/3 Systems or to transfer data between R/3 Systems.

This section describes how to manage batch input sessions.

To reach the main menu of the batch input system, select System ® Services ® Batch input. Alternatively, enter transaction SM35.

For information on the Recording function in the batch input manager (transaction SHDB), please see the online guide Basis Programming Interfaces. You can use the recording function to create a batch input session without having to write or run a program to generate a session.

Processing Sessions Automatically

Use

In most cases, batch input sessions can be processed automatically. It is not necessary for a session to wait until a system administrator explicitly starts the processing of the session.

This section explains how to have sessions started automatically soon after the session has been generated in an R/3 System.

Prerequisites

The ABAP program RSBDCSUB must be scheduled as a periodic job in the R/3 background processing system. RSBDCSUB checks for and starts any batch input sessions that have not yet been run. It schedules such sessions for immediate execution in the background processing system.

Procedure

Schedule RSBDCSUB to run periodically in one or more background jobs.

If you have regularly scheduled batch input runs, you can schedule separate jobs for each of the scheduled data transfers. The start time for the RSBDCSUB job can be set according to the batch input schedule. And you can use a variant to restrict RSBDCSUB only to the batch input sessions that you expect.

With RSBDCSUB, you can use all of the selection criteria offered on the batch input main menu to select sessions to run:

session name

date and time of generation

status: ready to run or held in the queue because of errors

Result

Batch input sessions are started automatically rather than by hand. The RSBDCSUB program can be set up to start all sessions that arrive in an R/3 System, or it can be fine-tuned to start only batch input sessions that you expect.

Starting Sessions Explicitly: Run Modes

Use

Running a batch input session executes the transactions in the session and enters data into an R/3 System.

Usually, the system will run batch input sessions automatically. However, you can also start batch input sessions by hand. You may wish to do this for these and other reasons:

To correct transactions that had errors

To check that the transactions in a session have been generated correctly by running the first several transactions

To start a session on special request (the session would not be started automatically or must be started right away).

Prerequisites

Start the batch input management tool: Select System ® Service ® Batch input ® Sessions. Alternate: Enter transaction SM35. Both paths take you to the session overview of the batch input system. transaction SM35.

Procedure

To start a session, mark the session and choose Process from the tool bar. You can then choose how to run a session and with what logging and display options.

You can start any session in new status that is not locked. With Process/foreground or Display errors only mode, you can also re-start transactions that have the status Incorrect. Sessions with the status Processed cannot be run again.

Run Modes

There are three ways to run a session:

Process/foreground: You can interactively correct transactions that contained errors and step through transactions that have not yet been executed.

Display errors only: This mode is like Process/foreground except that transactions that have not yet been run and which do not contain errors are run non-interactively.

If an error occurs, processing stops and the screen upon which the error occurred is displayed.

Background: Use this mode to schedule a session for immediate processing in the background processing facility.

You receive control of your terminal again as soon as the session has been passed to the background processing system.

Note that your session is automatically released for processing in the background processing system. You need not explicitly release the session for processing.

A completed session is handled in one of three ways:

The system deletes a session from the queue when it has been successfully completed. You can check on the outcome of the session by displaying the session log file.

If the KEEP option was set when the session was generated, then the system leaves a session in the queue, even if it was run successfully. The status is changed to Processed.

You cannot run a processed session a second time. You must manually delete it when you no longer need it.

If a transaction in the session contained an error, the incorrect transaction is aborted. All other transactions are completed. The session remains in the queue and is held in the Errors section of the list. You can correct the session in one of the interactive modes and run it to completion.

A transaction contains an error if it issues a message of type E (error) or type A (abnormal termination). Other messages are ignored and do not affect the execution of a session..

A session also is held in the queue in the Errors list if the session was ended with the /bend OK code. Please see Correcting a Session.

Regards

Re: coding for maintain the multip[le sessions

Former Member — Wed, 13 Jun 2007 10:46:41 GMT

see the example program and the selection screen you can maintain how many records per session.

************************************************************************

Report : ZMPPC015
Type : Data upload
Author : Seshu Maramreddy
Date : 05/26/2005
Transport : DV3K920025
Transaction: ??
Description: This ABAP/4 Program to Create Planned Independent
Requirement for SMI plants using MD61 Transaction.
It accepts tab-delimited spreadsheet input and
creates BDC sessions.

************************************************************************

report zmppc015 no standard page heading

line-size 120

line-count 55

message-id zz.

Constants

constants : c_x type c value 'X'," Dynbegin

c_tcode type tstc-tcode value 'MD61'." Transaction Code

Variables

data : v_lines_in_xcel like sy-tabix,

l_tabix like sy-tabix,

v_trans_in_ssn type i,

v_ssnnr(4) type n," Counter

v_ssnname like apqi-groupid,

v_matnr(18) type c. " Material Number

Internal Tables
Internal table for file

data : begin of t_file occurs 0,

matnr(18) type c, " Material Number

berid(10) type c, " MRP Area

PLNMG01(17) type n, " Forecast Month -01

PLNMG02(17) type n, " Forecast Month -02

PLNMG03(17) type n, " Forecast Month -03

PLNMG04(17) type n, " Forecast Month -04

PLNMG05(17) type n, " Forecast Month -05

PLNMG06(17) type n, " Forecast Month -06

PLNMG07(17) type n, " Forecast Month -07

PLNMG08(17) type n, " Forecast Month -08

PLNMG09(17) type n, " Forecast Month -09

PLNMG10(17) type n, " Forecast Month -10

PLNMG11(17) type n, " Forecast Month -11

PLNMG12(17) type n, " Forecast Month -12

WERKS(4) TYPE C, " Plant

end of t_file.

Internal table for BDCDATA Structure

data : begin of itab_bdc_tab occurs 0.

include structure bdcdata.

data : end of itab_bdc_tab.

Selection-screen

selection-screen: skip 3.

selection-screen: begin of block id1 with frame.

parameters: p_name like rlgrap-filename

default 'C:\My Documents\InputFile.txt'

obligatory,

bdc session name prefix

p_bdcpfx(6) default 'ZPIRCT'

obligatory,

number for transction per BDC session

p_trnssn type i

default 2000 obligatory,

retain the BDC session after successfull execution

p_keep like apqi-qerase

default c_x,

user who will be executing BDC session

p_uname like apqi-userid

default sy-uname

obligatory.

selection-screen : skip 1.

Requirement type

parameters : p_bedae like t459u-bedae,

From Date

p_date like sy-datum default sy-datum obligatory.

selection-screen: end of block id1.

at selection-screen on value-request for p_name.

F4 value for Input file

perform filename_get.

main processing

start-of-selection.

To get the data from file to Internal table

perform getdata_fromfile.

loop at t_file.

hang on to xcel line num

l_tabix = sy-tabix.

if num-of-trnas-in-session = 0, create new BDC session

if v_trans_in_ssn is initial.

perform bdc_session_open.

endif.

begin new bdc script for rtg create trans
fill in bdc-data for prod.version maintenance screens

perform bdc_build_script.

insert the bdc script as a BDC transaction

perform bdc_submit_transaction.

keep track of how many BDC transactions were inserted in the BDC
session

add 1 to v_trans_in_ssn.

if the user-specified num of trans in BDC session is reached OR
if end of input file is reached, close the BDC session

if v_trans_in_ssn = p_trnssn or

l_tabix = v_lines_in_xcel.

perform bdc_session_close.

clear v_trans_in_ssn.

endif.

clear t_file.

endloop.

top-of-page.

call function 'Z_HEADER'

EXPORTING
FLEX_TEXT1 =
FLEX_TEXT2 =
FLEX_TEXT3 =

&----

*& Form filename_get

&----

F4 Value for input file

----

FORM filename_get.

CALL FUNCTION 'WS_FILENAME_GET'

EXPORTING

DEF_PATH = 'C:\Temp\ '

MASK = ',.,..'

MODE = 'O'

TITLE = 'Select File '(007)

IMPORTING

FILENAME = p_name

EXCEPTIONS

INV_WINSYS = 1

NO_BATCH = 2

SELECTION_CANCEL = 3

SELECTION_ERROR = 4

OTHERS = 5.

IF sy-subrc <> 0.

MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno

WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

ENDIF.

ENDFORM. " filename_get

&----

*& Form getdata_fromfile

&----

Upload the data from file to Internal table

----

FORM getdata_fromfile.

CALL FUNCTION 'WS_UPLOAD'

EXPORTING

FILENAME = p_name

FILETYPE = 'DAT'

TABLES

DATA_TAB = t_file

EXCEPTIONS

CONVERSION_ERROR = 1

FILE_OPEN_ERROR = 2

FILE_READ_ERROR = 3

INVALID_TYPE = 4

NO_BATCH = 5

UNKNOWN_ERROR = 6

INVALID_TABLE_WIDTH = 7

GUI_REFUSE_FILETRANSFER = 8

CUSTOMER_ERROR = 9

OTHERS = 10.

if sy-subrc eq 0.

sort t_file by matnr .

delete t_file where matnr = ''.

clear v_lines_in_xcel.

describe table t_file lines v_lines_in_xcel.

if v_lines_in_xcel is initial.

write: / 'No data in input file'.

stop.

endif.

else.

write:/ 'Error reading input file'.

stop.

endif.

ENDFORM. " getdata_fromfile

&----

*& Form bdc_session_open

&----

BDC_OPEN_GROUP

----

FORM bdc_session_open.

create bdc session name = prefix-from-selectn-screen + nnnn

add 1 to v_ssnnr.

concatenate p_bdcpfx v_ssnnr into v_ssnname.

CALL FUNCTION 'BDC_OPEN_GROUP'

EXPORTING

CLIENT = SY-MANDT

GROUP = v_ssnname

KEEP = p_keep

USER = p_uname

EXCEPTIONS

CLIENT_INVALID = 1

DESTINATION_INVALID = 2

GROUP_INVALID = 3

GROUP_IS_LOCKED = 4

HOLDDATE_INVALID = 5

INTERNAL_ERROR = 6

QUEUE_ERROR = 7

RUNNING = 8

SYSTEM_LOCK_ERROR = 9

USER_INVALID = 10

OTHERS = 11.

IF SY-SUBRC <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

ENDFORM. " bdc_session_open

&----

*& Form bdc_build_script

&----

BDC Script

----

FORM bdc_build_script.

Local Variables

DATA : l_frdat(8) type c, " From Date

l_todat(8) type c, " To Date

l_frdat1(4) type c, " Year

l_frdat2(2) type c, " Month

l_frdat3(2) type c, " Day

l_tdate like sy-datum, " Subtract date(1)

l_todat1(4) type c, " Year

l_todat2(2) type c, " Month

l_todat3(3) type c. " Day

Get the material number from tables ZMSMI_FERR_RAW,
ZMSMI_SNAP_RAW and ZMSMI_SIMP_RAW

perform get_matnr.

Screen 0100.

perform bdc_screen using 'SAPMM60X' '0100'.

perform bdc_field using 'BDC_OKCODE' '/EBDPT'.

perform bdc_field using 'AM60X-MATAW' 'X'.

perform bdc_field using 'AM60X-MATNR' T_FILE-MATNR.

perform bdc_field using 'AM60X-PRGRP' SPACE.

perform bdc_field using 'AM60X-PBDNR' SPACE.

perform bdc_field using 'RM60X-BERID' T_FILE-BERID.

perform bdc_field using 'AM60X-WERKS' SPACE.

perform bdc_field using 'RM60X-VERSB' '00'.

Converted the date as per MD61 Transaction.
From date

l_frdat1 = p_date+0(4).

l_frdat2 = p_date+4(2).

l_frdat3 = p_date+6(2).

concatenate l_frdat2 l_frdat3 l_frdat1 into l_frdat.

To Date

l_tdate = p_date - 1.

l_todat1 = l_tdate+0(4) + 1.

l_todat2 = l_tdate+4(2).

l_todat3 = l_tdate+6(2).

concatenate l_todat2 l_todat3 l_todat1 into l_todat.

perform bdc_field using 'RM60X-DATVE' l_frdat.

perform bdc_field using 'RM60X-DATBE' l_todat.

perform bdc_field using 'RM60X-ENTLU' 'M'.

Screen 0127

perform bdc_screen using 'SAPMM60X' '0127'.

perform bdc_field using 'BDC_OKCODE' '=WEIT'.

if p_bedae is initial.

perform bdc_field using 'T459U-BEDAE' space.

else.

perform bdc_field using 'T459U-BEDAE' P_BEDAE.

endif.

Screen 0100.

perform bdc_screen using 'SAPMM60X' '0100'.

perform bdc_field using 'BDC_OKCODE' '/00'.

perform bdc_field using 'AM60X-MATAW' 'X'.

perform bdc_field using 'AM60X-MATNR' T_FILE-MATNR.

perform bdc_field using 'AM60X-PRGRP' SPACE.

perform bdc_field using 'AM60X-PBDNR' SPACE.

perform bdc_field using 'RM60X-BERID' T_FILE-BERID.

perform bdc_field using 'AM60X-WERKS' SPACE.

perform bdc_field using 'RM60X-VERSB' '00'.

perform bdc_field using 'RM60X-DATVE' l_frdat.

perform bdc_field using 'RM60X-DATBE' l_todat.

perform bdc_field using 'RM60X-ENTLU' 'M'.

Screen 0200