‎2006 Apr 24 9:32 AM
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
‎2006 Apr 24 10:47 AM
<b>JOB_OPEN</b>: 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
<b>JOB_CLOSE</b>: 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
‎2006 Apr 24 9:36 AM
‎2006 Apr 24 9:37 AM
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.
‎2006 Apr 24 10:30 AM
Hello,
Use report RSBDCLOG to get the messages from the Session.
Regards,
Naimesh
‎2006 Apr 24 10:36 AM
<b>BATCH INPUT SESSION</b> 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.
<b>Background processing</b>
<b>JOB_OPEN</b> Open Job Scheduling Without Dialog (Including COMMIT WORK)
Open background job and obtain the job Id (JOBCOUNT)
<b>JOB_SUBMIT</b>
Insert Background Task in Background Request with COMMIT WORK
Add step to the opened job
<b>JOB_CLOSE</b> Close Background Request With COMMIT WORK
Release the job
regards
vinod
‎2006 Apr 24 10:47 AM
<b>JOB_OPEN</b>: 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
<b>JOB_CLOSE</b>: 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