How and where to manage job BPM_DATA_COLLECTION_X?

[Former Member]

Dear All,

Do you guys have any idea where to trigger this job : BPM_DATA_COLLECTION_X ?

Is this job : BPM_DATA_COLLECTION_X being triggered automatically whenever you save the "Business Process Monitoring" configuration (configured with proper setting on Monitor Schedule.) ?

Besides, realized the run time of this job : BPM_DATA_COLLECTION_X in my R/3 system is varies time to time..From the job log, it reading different Monitoring Object for different jobs..... may I know how to control the job to read specific Monitoring Object , for example :IMIDOC01? Is this controlled by the business processes that I defined (to be monitored) in the SOLMAN ?

Best Regards,

Ken

[Former Member]

Dear VivekHegde and Keiji,

Is that possible for us to configure the "job class" of BPM_DATA_COLLECTION_X ?

Best Regards,

Ken

[keiji_mishima]

Hi Ken

The program is automatically scheduled from BPMon. So I do not recommend to change it manually.

In the BPMon the job is scheduled using background programming interface.

Like using CALL FUNCTION 'JOB_OPEN', CALL FUNCTION 'JOB_SUBMIT', and CALL FUNCTION 'JOB_CLOSE'.

So as you can see in the following help, it is scheduled class C.

http://help.sap.com/saphelp_nw70/helpdata/en/fa/096cff543b11d1898e0000e8322d00/content.htm

>Always set by default to class C. No other priority can be set with the background programming interface.

>You can set other priorities only by hand, in the job-scheduling transaction (SM36, also SM37).

Best Regards

Keiji

[Former Member]

Dear Keiji,

Thanks a lot for the finding ,

Besides,there is another question related to this BPM job actually ....

As far as I knew, when we have activate the "data collection in

background" in "Business Process Monitoring Setup",a job :

BPM_DATA_COLLECTION_<number> will be triggered in the satellite system.

For example, in the Solution A, the BPM I setup will send an email-

alert to the users whenever threshold limist is hit.

However, I realized that as long as the job :

BPM_DATA_COLLECTION_<number> is still in active mode, the users will

not receive an email and in SOLMAN_WORKCENTER ( Alert Inbox ) will not

see the particular alert.

As you know, the BPM_DATA_COLLECTION_<number> was shared by multiple

solutions perhaps, for example, the BPM in Solution A, B, C have run

the "data collection in background" at the same time and the same

system, thus, I can see multiple monitoring object running the

BPM_DATA_COLLECTION_<number> Job in the satellite system.

However, as mentioned, the email-alert will not send out as long as

the BPM_DATA_COLLECTION_<number> job is still active. All the alerts,

get delayed when it reached to the user side if at the point of time,

there is multiple of monitoring objects running at the same jobs.

So my question is, is that possible to restrict / configure, one

Solution tied with one BPM_DATA_COLLECTION job ? OR One Monitoring

Object tied with one BPM_DATA_COLLECTION job within the same Solution?

Best Regards,

Ken

[keiji_mishima]

Hi Ken

In my understanding, BPM_DATA_COLLECTION* job is shared with multiple solution +

multiple objects. If multiple collection is allowed, there is possibility to use up all resource,

so I guess it is not designed in that way.

Normally BPM_DATA_COLLECTION_1 run every 5 min, and in case of

BPM_DATA_COLLECTION_1 takes long (for example active), BPM_DATA_COLLECTION_2 is triggered.

In your case, you mentioned due to long run of the job, you cannot get alert timely.

In this case, I would rather focus on the setting of your data collector

(which monitoring objects is configured) and performance of your data collector.

Do you know have any idea which data collector is configured and takes long ?

Normally people want to receive quick alert from interface fail or job fail (some job issue).

So for these monitoring objects, you may schedule monitor like every 15 min etc.

(But normally it may not take long. <Off course your DB size is so huge or having

lots of interface data in process, it may be different>.

Regarding on the document monitoring (through put / backlog monitoring), there is

possibility to take time (also depending on the size and also parameter you specify).

For these collector, it should not be scheduled like every 10 min.

If you have performance issue coming from document monitoring, I would recommend

you to review your scheduling settting

- Avoid schedule of these monitor on same time

PP document 3AM

SD document 2AM

MM document 4AM

- Schedule with less workload

- Schedule with lwo frequency (like once a day)

Also there are several SAP Notes improve performance of data collector. So

Example)

1447051 ST-A/PI 01L: Performance improvements for MM TBIs

1423722 ST-A/PI 01L: Performance improvements for LE TBIs etc.

1423721 ST-A/PI 01L: Performance improvements for SD TBIs

1321015 ST-A/PI 01L: IDoc Monitoring Corrections <=IDoc

if you uses ST-A/PI version L, please also check above notes.

if above information does not help you, also consider to request help to SAP support via customer message

under the component "SV-SMG-MON-BPM".

Best Regards

Keiji Mishima

[Former Member]

Dear Keiji,

I saw the longest running job always running with this SQL statement :

    SELECT                                                                                
T_00 . "LGNUM" , T_01 . "NLTYP"                                                                          
FROM                                                                                
"LTAK" T_00 , "LTAP" T_01                                                                                
WHERE                                                                                
( T_01 . "MANDT" = :A0 AND T_00 . "LGNUM" = T_01 . "LGNUM" AND T_00 . "TANUM" = T_01 . "TANUM" ) AND     
  T_00 . "MANDT" = :A1 AND T_00 . "LGNUM" BETWEEN :A2 AND :A3 AND T_00 . "TRART" = :A4 AND T_01 . "PQUIT"  
  = :A5 AND T_01 . "NLTYP" IN ( :A6 , :A7 ) AND T_01 . "QDATU" = :A8 

So I think this should be Monitoring Object : KPWM0002 iwhich taking so long f not mistaken but I am not sure why is that taking so long. And the current ST-A/PI in our R/3 and SOLMAN is 01M_R3_470. Perhaps I will raise an OSS to SAP for this.

Besides, actually we have two BPM* jobs now...

BPM_DATA_COLLECTION_1 and BPM_DATA_COLLECTION_2

BPM_DATA_COLLECTION_1 was failed due to the Job's Onwer was deleted and I don't know what is the proper procedure to handle this, thus the job : BPM_DATA_COLLECTION_1 was changed to scheduled.

BPM_DATA_COLLECTION_2 (different job owner) will still being triggered by the SOLMAN from time to time being.

Not sure will this be an issue or not.

Best Regards,

Ken

[keiji_mishima]

Hi Ken

Thank you for the information about ST-A/PI.

I guess it might be something from WM key figure like "Number of confirmed outbound Transfer Order Items".

I cannot guarantee whether it is possible to optimize performance. So there is a possibility for you to schedule

the monitor with less frequently and during the time with less workload.

But to judge this, it is better to check your system how is the data volume <Table size LTAK,LTAP> and configuration<Whether KPWM0002 is used in multiple and its frequency> looks like). So please request help to OSS.

Best Regards

Keiji Mishima

[former_member184806]

Hi Keiji,

Are you aware of the case in Background job monitor?

There is no option for us  to select the "Data Collection in BC" and like IDoc monitoring there is no by default selection of "Data Collection in BC".

So for Background Job Monitoring is the data collection done in Dialog work processes or Background work processes.

Regards,

Vishal

[keiji_mishima]

Hi Vishal

What I described just apply the monitor run on application monitor framework.

So back ground job monitor is not relevant. BPMon background job monitor run different framework. So it just run via online mode. And you only gave to option (critical/non critical) for data check interval.

IDoc monitoring run on application monitor framework. In old setup session 15 min background data collection was default setting. But in new web based setup screen, default setting just gone.

Best Regards

Keiji

[keiji_mishima]

Hi Ken

Regarding on the job, BPMon trigger the job automatically if you use monitoring object with background data collection.

The job is scheduled when BPMon is activated (every 5 min).

In your monitoring object (let's say, document monitoring "purchase order"), you can specify when the data collection should be run and how (online/background).

If you use background and specify the data collection on 2AM, the BPMon data collector job trigger data collection within the job

in satellite system after 2 AM.

(every 5 min, job is running, but since there is no necessity to do specific data collection, it finish quickly. But when it reach 2 AM, then the job needs to trigger data collection for purchase order, thus runtime of the job bit longer than other case).

That is why, the runtime of this job become different. (Basically this comes from the setting of your monitoring objects).

In your description, you mentioned "IMIDOC01". This object comes from IDoc monitoring. (IDoc monitoring is bit special). When you setup IDoc monitoring, it is scheduled to use background job and minimum frequency is every 15min. So if you use IDoc monitoring, it is designed to use background data collection framework by default.

So when you activate BPMon in solman, the job is automatically scheduled in satellite system. (If you do not change the frequency, then I guess every 15 min, IDoc data collection is conducted.).

You can also find out this kind of information in following document.

www.service.sap.com/bpm =>media library =>technical document =>

Trouble shooting guide BPMon. I recommend you to check page 15&16.

(Page 16 decries exact behavior on the job).

Hope this information help your understanding.

Best Regards

Keiji

[former_member1109645]

Hi Keiji,

I have jsut started BPMON , what do you mean by job run and data collection, every time when job runs it fetches data in bacground right? Kindly explain ?

Thanks ,

Kannan

[former_member184806]

Hi Kannan,

If you select the data collection in background then every 5 mins the BPM_DATA_COLLECTION_X runs in the managed system. But it is not necessary that it will collect data every time it runs.

For example if you have set the data collection of incomplete orders at 10:30 in background then the job will run at 10:15, 10:20, 10:25, but will not collect data as it will not find any monitoring object for which the data needs to be collected. When it runs at  10:30 it will find that the data has to be collected for incomplete sales order and so it will collect data only in that run.

You can check the log of this job run when you have scheduled the data collection of any particular monitor. You will find in the log that "found monitoring ID xxxxx" showing the data collection for particular monitor.

Regards,

Vishal

[keiji_mishima]

Hi Kannan

BPM_DATA_COLLECTION_X run every 5 minutes regardless whether there is required data collection or not. If you only define some monitor to do data collection at 1 AM in background mode,

BPM_DATA_COLLECTION_X really start data collection at 1 AM (between 1:00-1:05).

In other time slot, althrough BPM_DATA_COLLECTION_X run in background, it finish immediately because there is no need to do real data collection activities within the job. (no real impact of system resoruce).

For the BPM_DATA_COLLECTION_X that start after 1 AM (1st time), it start real data collection within the job.

BPM_DATA_COLLECTION_X  00:45 ->start & finish immediately

BPM_DATA_COLLECTION_X  00:50 ->start & finish immediately

BPM_DATA_COLLECTION_X  00:55 ->start & finish immediately

BPM_DATA_COLLECTION_X  01:00 -> real data collection occur (access application tables)

BPM_DATA_COLLECTION_X  01:05 ->start & finish immediately

BPM_DATA_COLLECTION_X  01:10 ->start & finish immediately

Best Regards

Keiji Mishima

[former_member1109645]

Hi Keiji,

Thanks for the explanation.

Kindly check my below thread,

http://scn.sap.com/thread/3386251

Thanks,

Kannan N

[Former Member]

HI Keji,

I am facing issue in BPMON, I have set up Analytic monitoring object for sales document, Job is running fine, But job log is showing this error:

Job started

Step 001 started (program /SSA/EXS, variant , user ID SMTMZP7)

No Job RUNNING. Processing started...

I: Equeue OK APPMONZ

I: Dequeue OK APPMONZ

Starting DC with Monid: 000001606840000 monitoring object: KPSD00

Solution ID: ZP70020247162

SID: SP7

CLIENT: 100

APPMONA: KPSD0003 000001606840000

No Alert found

End DC 000001606840000 monitoring object: KPSD0003

I: Equeue OK APPMONI

PTAB read failed. APPMONI

I: Dequeue OK APPMONI

I: Dequeue OK APPMONI

I: Equeue OK APPMONZ

I: Dequeue OK APPMONZ

I: Equeue OK DA_IDOC

I: Dequeue OK DA_IDOC

I: Equeue OK APPMONZ

I: Dequeue OK APPMONZ

An we are not able see any data in the Dashboards of Solman.

We are Solman 7.1 SP13.

ST-PI

2008_1_700

0013

ST-A/PI

01S_700

0000

In Managed system we have:

ST-PI

2008_1_700

0011

ST-A/PI

01R_700

0002

Thanks,

Ashwani.

[Vivek_Hegde]

Hello Ken,

The Job BPM_DATA_COLLECTION_X should be triggered at managed systems.

Please refer SAP Note No. 1300420 for more details and troubleshooting.

Regards

Vivek