cancel
Showing results for 
Search instead for 
Did you mean: 

BPC Incorrect Scoping?

jbell
Explorer
0 Kudos
181

Hi

BPC Standard 10.1 NW

I have a customer facing an issue with the scoping for default and journal logics, in instances where data is keyed via EPM addin and Journal by two different users at almost exactly the same time, details of the issue as follows (taken from the System Reports -> Data Changes in web admin):

1. Data entered by two different users within 1 second of eachother, one via journal and one via EPM addin (column B). Note that EPM Add-in is against INPUT & E_C60 entity, whilst Journal is against ADJ_LC_EAGLEELM and various entities (including E_C61, rows 6 and 7 of the journal input, but excluding E_C60).

2. User WARDR triggers journal logic at 16:06:40 and a further two sets of time entries; 16:06:41 and 16:06:44. For ADJ_LC_EAGLEELM, the journal logic does not include entity E_C61.

There are other records for the journal logic that contain both E_C60 and E_C61 entities, but these are all nominal amounts, fractions of pennies.

3. User HAMERK triggers default logic at 16:06:41, but this is for the values and members as input by WARDR in the journal, ie ADJ_CL_EAGLEELM and E_C61.

The upshot of all of this is that the default logic is not triggered for the inputs keyed in via EPM and therefore expected calculations are not carried out and results are ultimately incorrect. It almost seems like there is a crossover and confusion in the back-end in such a scenario.

Default script as follows:

Journal script as follows:

I was potentially going to log with SAP, but thought I would reach out first to see if anyone had came across such a scenario and could provide any advice? Note that this appears to be inconsistent and customer is not able to reliably replicate in their QA system.

If any further info is required, please get in touch and I will be happy to provide.

Cheers

JB

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member186338
Active Contributor
0 Kudos

First of all, you have to look on default/journal logic logs!

jbell
Explorer
0 Kudos

Hi Vadim

Thanks for your response.

I have reviewed the logs via UJFS, details below:

For WARDR journal script logs - no apparent issues

For HAMERK default script logs, errors around being unable to access entity members, however these are entity members from user WARDR's journal inputs. The 3 successes will be relating to the screenshot from point 3 in my original post for E_C61. There is no mention of E_C60 which was posted to via EPM.

Thanks

JB