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?
<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.
<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.