cancel
Showing results for 
Search instead for 
Did you mean: 

Consolidation package doesnt work, monitor works perfectly fine.

Former Member
0 Kudos

Hello All,

I am facing a very weird problem. I have setup the consolidation and ownership models with all the structure configured and all the equity/intercompany elims configured. When I trigger the consolidations from Consolidation monitor, it works perfectly fine but when I trigger it from the data manager package, it doesnt do anything. I have not changed the script logic for consolidations. (FX works fine).

I staged some data for intercompany elims and tried to run the package but it didnt eliminate the balances. Then I ran the consolidation monitor, the monitor eliminates the balances and we see the expected results. From BW, we see that the package is triggering the LEGAL_CONSOLIDATION process chain but it doesnt process any records.

(Version is the category dimension)

*RUN_PROGRAM CONSOLIDATION

VERSION = %VERSION_SET%

GROUP = %SCOPE_SET%

TID_RA = %TIME_SET%

*ENDRUN_PROGRAM

Any suggestions on what could be wrong, how can I debug it? Thanks a lot in advance.

Mandar.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Do you run Group Currency conversion before the Consolidation program in your logic?

Try also adding INCREMENTAL_MODE = N

Former Member
0 Kudos

Yes, before I trigger the consolidation, I first translate the local currency.

I tried adding INCREMENTAL_MODE = N but it didnt work. Any other settings that we can check?

Also, I tried to create a new test environment from the scratch and the package seems to be working there fine. It still calls the same process chain. We already have done a lot of work in the existing environment so moving to a new environment is not an option for us right now.

Thanks Jef. Appreciate it.

Mandar.

Former Member
0 Kudos

Hi Mandar, you've understood me wrong there.

There are 2 types of currency conversions in BPC. You have to make sure you are running GROUP currency conversion.

It's best you add this part in your logic file as well. It should look like this:

*RUN_PROGRAM CURR_CONVERSION
  CATEGORY = %CATEGORY_SET%
  GROUP = %SCOPE_SET%
  TID_RA = %TIME_SET%
  RATEENTITY = GLOBAL
  INCREMENTAL_MODE = N
*ENDRUN_PROGRAM

*RUN_PROGRAM CONSOLIDATION
  CATEGORY = %CATEGORY_SET%
  GROUP = %SCOPE_SET%
  TID_RA = %TIME_SET%

  INCREMENTAL_MODE = N
*ENDRUN_PROGRAM

*COMMIT

Former Member
0 Kudos

Hi Jef, sorry for that . Yes, we have the FX piece in there and it is converting the data group currency. I was referring to the same piece of the code.

We confirmed all the settings in the environment for dimension properties/business rules. Since the consolidation monitor works fine, it tells me that the configuration is done correctly. I am at a loss here, not sure what else to validate.

Mandar

Former Member
0 Kudos

Ok, here are a few ideas:

- Replace VERSION = %VERSION_SET% with CATEGORY = %VERSION_SET%

As the left side is a program variable, the right side is linked to your dimension name and "_SET" suffix.

- in your DM package script, try to add "DEBUG(ON)" on the first row. I think this should have given you the error on the above point.

Former Member
0 Kudos

You are the man!!!

That did the trick. The package is working fine now. Thanks a lot Jef. Full points.

Mandar.

Answers (0)