2006 Nov 02 11:27 AM
Hi,
I want to know hat does t-code SM64 do?
It triggers an event. I want to know what sort of event does it trigger, I am making a BDC for that but am not sure for all of its functionality.I also want to know when exactly does it create an event manually...
Also in the program if the bdc executes then under which circumstances does an entry be present in SM35 and not present in Sm35 if SY-SUBRC =0, i.e no error.
Regards
Arnab.
Hi,
I want to know hat does t-code SM64 do?
It triggers an event. I want to know what sort of event does it trigger, I am making a BDC for that but am not sure for all of its functionality.I also want to know when exactly does it create an event manually...
Also in the program if the bdc executes then under which circumstances does an entry be present in SM35 and not present in Sm35 if SY-SUBRC =0, i.e no error.
Regards
Arnab.
2006 Nov 02 11:29 AM
hi,
use FM BP_EVENT_RAISE.
BAPI_XBP_EVENT_RAISE. This is rfc enabled.
to raise event.
rgds
anver
2006 Nov 02 11:31 AM
I will have to use this only...so i need to know things on this code... I know that that fm can be used but I need to do it with this. Is there any problem at runtime that arises for this .
2006 Nov 02 11:53 AM
I need more details about the t-code SM64 or some links where I can find some details.
2006 Nov 02 11:55 AM
hi,
Hope this will help.
Events let you start background jobs when particular changes in the SAP system take place. When an event occurs, the background processing system starts all jobs that were scheduled to wait for that event.
http://help.sap.com/saphelp_nw04s/helpdata/en/fa/096e2a543b11d1898e0000e8322d00/frameset.htm
Events have meaning only in the background processing system. You can use events only to start background jobs.
Triggering an event notifies the background processing system that a named condition has been reached. The background processing system reacts by starting any jobs that were waiting for the event.
http://help.sap.com/saphelp_nw04s/helpdata/en/fa/096e37543b11d1898e0000e8322d00/frameset.htm
Use function module BP_EVENT_RAISE to trigger an event from an ABAP program.
Example
Report processing before triggering event...
Trigger event to start background jobs waiting for the event.
DATA: EVENTID LIKE TBTCJOB-EVENTID.
DATA: EVENTPARM LIKE TBTCJOB-EVENTPARM.
EVENTID = 'SP_TEST_EVENT'. " Event name must be defined
" with transaction SM62.
EVENTPARM = 'EVENT1'. " Optional: a job can be
" scheduled to wait for an
" EVENTID or combination of
" EVENTID and EVENTPARM.
CALL FUNCTION 'BP_EVENT_RAISE' " Event is triggered. Jobs
EXPORTING " waiting for event will be
EVENTID = EVENTID " started.
EVENTPARM = EVENTPARM
TARGET_INSTANCE = " Instance at which an event
" should be processed. Can
" generally be omitted.
EXCEPTIONS OTHERS = 1. " Exceptions include event not
" defined, no EVENTID
" exported, etc.
Regards,
anver
2006 Nov 02 12:15 PM
HI Anversha,
Thanx for your reply,
Link is helpful, will get back to you for more queries...
Regards,
Arnab
2006 Nov 02 12:28 PM
hi
good
It contains two things one is Event name and Parameter Id->
Background event ID->
Name of the event to which a job is linked.
An event is a signal stating that a predefined status in the system has been reached. The background processing system receives events and then starts the background job/jobs that is/are linked to an event.
Procedure
In the job overview: Enter the event name to list the jobs that are linked to the event.
When scheduling a job: Enter the event name on which the start of this job should depend.
You can specify predefined events of the SAP applications or SAP System kernel or events you defined yourself. Which SAP events you can use is explained in the documentation of the SAP applications.
Scheduling Jobs Periodically
In order to schedule a job each time an event occurs, select Execute job periodically when scheduling.
-
Background Event Parameters (Such as, Jobname/Jobcount)
Procedure
If an event requires a parameter, enter the required parameter in this field. A parameter qualifies an event. For example, job name and job number are also output as a parameter for the event SAP_END_OF_JOB.
In order to find out whether an event outputs a parameter, refer to the documentation of the respective SAP application.
Examples
System-internally, job concatenations are represented with the event SAP_END_OF_JOB.
If you schedule a job which is linked to a previous job, your job has to wait for the event SAP_END_OF_JOB. By means of the identification of the previous job, the system recognizes that the correct job was finished. The identification is stored as a parameter of SAP_END_OF_JOB.
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |