topic Re: batch input in Application Development and Automation Discussions

batch input

Former Member — Mon, 24 Apr 2006 08:32:19 GMT

hi!

what is the diffrence between using BI in call transaction to OPEN_JOB and CLOSE_JOB.

and how in the latter can i get messages from BI?

regards

yifat

Re: batch input

Former Member — Mon, 24 Apr 2006 08:36:26 GMT

go through this link ...

Re: batch input

Former Member — Mon, 24 Apr 2006 08:37:04 GMT

Hi yifat,

1. In call transaction, data is updated

when u run the program itself.

2. in the other method,

the whole bdc data is

INTERMEDIATELY STORED IN ONE SESSION.

(We have to afterwards run that session,

so that data is updated)

regards,

amit m.

Re: batch input

naimesh_patel — Mon, 24 Apr 2006 09:30:29 GMT

Hello,

Use report RSBDCLOG to get the messages from the Session.

Regards,

Naimesh

Re: batch input

vinod_gunaware2 — Mon, 24 Apr 2006 09:36:39 GMT

BATCH INPUT SESSION is an intermediate step between internal table and

Database table. Data along with the action is stored in session i.e. data for screen fields, to which screen it is passed, program name behind it, and how next screen is processed.

Go to SM36 and create background job by giving job name, job class and job steps (JOB SCHEDULING).

After that u can get log of that particular job.

Background processing

JOB_OPEN Open Job Scheduling Without Dialog (Including COMMIT WORK)

Open background job and obtain the job Id (JOBCOUNT)

JOB_SUBMIT

Insert Background Task in Background Request with COMMIT WORK

Add step to the opened job

JOB_CLOSE Close Background Request With COMMIT WORK

Release the job

regards

vinod

Re: batch input

Former Member — Mon, 24 Apr 2006 09:47:19 GMT

JOB_OPEN: Create a Background Processing Job

Use JOB_OPEN to create a background job. The function module returns the unique ID number which, together with the job name, is required for identifying the job.

Once you have "opened" a job, you can add job steps to it with JOB_SUBMIT and submit the job for processing with JOB_CLOSE.

For more information, please see the online documentation in the function module facility (transaction SE37) or Sample Program: Creating a Job with JOB_OPEN.

http://help.sap.com/saphelp_40b/helpdata/ru/fa/096ee5543b11d1898e0000e8322d00/content.htm

JOB_CLOSE: Pass a Job to the Background Processing System

Use JOB_CLOSE to pass a background job to the background processing system to be run. Once you have "closed" a job, you can no longer add job steps to it or change job/job step specifications.

The function module returns an indicator as to whether the job was automatically released or not. A job is automatically released to run only if the user who scheduled the job has RELE release authorization for the authorization object Operations on background jobs.

A job step is an independent unit of work in a job, the execution of an ABAP or external program. Each job step can have its own authorizations user and printer/optical archiving specifications.

Related function modules include:

JOB_OPEN: Create a background job.

JOB_SUBMIT: Add job steps to a job.

For more information, please see the online documentation in the function module facility (transaction SE37) or Scheduling a Job: Full-Control Method.

http://help.sap.com/saphelp_40b/helpdata/ru/fa/096eff543b11d1898e0000e8322d00/content.htm