cancel
Showing results for 
Search instead for 
Did you mean: 

Solution Manager BI Process Chain Monitoring.

Former Member
0 Kudos

Hi,

We configured BI Process Chain monitoring on Solman 7.1 SP13. We are pulling through status and duration on the Process Chains with there sub chaine or child chains, the problem we are is that the Log ID is the same for all the process chains that we add to be monitored. As far as I know this Log id is supposed to be unique for every run of a process chain. Because of this we are getting the in correct run time pulling through on the duration status.

When i search for the log id that you see in the screenshots i get to one Process Chain.

I have taken screenshots of 3 process chains which you can see that the log id is the same for all the chains.

Please let me know how i can resolve this problem.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

We resolved the above issue by applying the fix in SAP Note 2344438.

There is a error in the data collector that needs to be fixed using this note.

Shaffey

Answers (1)

Answers (1)

benu_mariantony2
Participant
0 Kudos

Hello Shaffey,

Have you tried with Job Monitoring? Job Monitoring was unveiled to the customers from SP10.
Job Monitoring has a provision to monitor the following,

1. ABAP Jobs
2. Process Chains / elements
3. Business Objects Jobs
4. Data Services Jobs
5. SMSE Jobs (from SP14)

There are a lot of advantages of using Job Monitoring

> Stateful data collection - The results are very much accurate
> Unified Data Collection
> Performance of the collector was much optimized

Now coming to the roadmap...
Starting Solution Manager 7.2 SP03, the following Monitoring Use cases are unified with Job Monitoring's unified architecture.

> Job Scheduling Management (Job Documentation)
> BP Operations
> Technical Monitoring (BI & Job Monitoring)


Please let me know for more information.

Ciao
Benu

Former Member
0 Kudos

Hi Benu,

Thank you for the feedback and information.

We cannot change the Solution now we have already agreed with the customer that this is the way we going to go.

The funny thing about this problem is that it works on a different BW system.

Shaffey

benu_mariantony2
Participant
0 Kudos

Hello Shaffey,

Could you create an incident to SV-SMG-MON-JBI-JOB?

Regards,
Benu

Former Member
0 Kudos

Hi,

Do you mean create incident to SAP?

Shaffey

benu_mariantony2
Participant
0 Kudos

Yes

benu_mariantony2
Participant
0 Kudos

Hello,

The LOG ID of Process Chain and Element looks to be IDENTICAL. Please refer the below screenshot.

Also make sure you had implemented the note 1558756 in the Managed BW System

Ciao
Benu

Former Member
0 Kudos

Hi Benu,

You are seeing the Log ID as being identical because that is for a parent the same parent chain. On our system the Log ID is identical for different Chains which is not correct.

I have checked SAP Note 1558756 as all prereqs are met.

I found this note which we are planning to implement and resolve the issue.

2240308 - Variables of Process Chain are stored for wrong LOG ID.

Shaffey

benu_mariantony2
Participant
0 Kudos

Hello Shaffey,

So in BW system we get the identical LOG IDs for different Process Chains.

Is this correct? I assume implementing a note 2240308 would solve the problem

Regards,
Benu

Former Member
0 Kudos

Hi Benu,

i dont think you having the same probem, you are seeing the same Log Id because you are seeing a main chain with its child chains. These could have the same Log Id.

Please read the note carefully before implementing.

Shaffey.