UJHANA_SYNC

[Former Member]

Hi experts.

We are migrating a BPC MS to BPC 10 on BWoH and we are facing a few problems.

We have activated the enable_ native_ hana_model parameter to use the runallocation but this writes the data in a different HANA table than saving data through the EPM Add-In for excel. This lead to inconsistencies in reports.

As an example we have,

Account	time	sdata
A	2014.MAY	1
B	2014.MAY	2

If we execute runallocation to 2014.JUN, we get

Account	Time	sdata
A	2014.JUN	1
B	2014.JUN	2

Let’s say that we save now a 5 on account A for June, What we have?

Account	Time	sdata
A	2014.JUN	6
B	2014.JUN	2

Why? Because of those 2 tables in HANA, the one for writing (used by runallocation) and the one for reading (used in last saving). We have found out that we need to run UJHANA_SYNC to synchronize both tables but we would like to use it as a process in the chain after the execution of the logic to do the synchronization just after the write in the tables and only for the correspondent model to avoid the inconsistencies.

Is it possible? Or it can only be scheduled as batch job? We have try but we didn´t get it, the process seem to get in some kind of endless loop trying to execute the report.

Thanks in advance.

[Former Member · Accepted solution]

A note resolving this issue has been developed and has been included in hanabpc 80106 and cpmbpc 80108. 2049426 - Posting data has problem after enabled native hana model