BPC 10.0 SP20 : IC data and Flow dimension

[Former Member]

Hi BPC experts,

When I run an IC Data package, the original flow data are all converted into an opening flow (called F_OB in my case).

Here is my logic script, where the FLOW F_TOT is the parent of F_OB and other flow (such as F_DEP - depreciation, etc.):

Now the issue :

I would like to keep the flows as they are in the original data. IC Data converts every flow into F_OB, which is not what I want. Is it possible to keep the flows as they are in the beginning ?

Thank you in advance,

Dat

[Former Member]

Hi Dat,

Why you are mentioning Flow Dimension in your logic ..?

Kindly remove Flow from your code as shown below..!

I Hope this will help you to resolve your issue......

Aravind

[Former Member]

Hi Aravind,

The flow is specified because if we use IC data when there is an opening flow and a copy of these data in a closing flow, the IC data will take these two flows into account. This leads to a wrong IC booking afterwards.

Dat

[Former Member]

Hi Dat ,

I know the process you explained .........

But khokan also mentioned and explained in detail why there is no need of Flow Dimension in ICDATA....... And you also Marked that as a Helpful Answer ..... Remove Flow Dimension...

Me too tried to tell you the same in Short...... As per standard procedure no need of Flow in ICDATA.....

Aravind

[Former Member]

Hi Aravind,

Although the answer from Khokan has relevant contents, it does not solve my issue unfortunately.

Anyway, I found an alternative since the client needs very fast results...

Thank you for your reply.

Dat

[Former Member]

That's great to hear Dat....

But appreciated if you can share your alternate solution with us which will help consultants with similar issue....

Aravind

[Former Member]

Well, this post was just for making a report with intercompanies.

I wanted the following format :

                                                 AUDITTRAIL (ICDATA1 and ICDATA2) DIFFERENCE             

INTERCO ACCOUNT FLOW

but it was not possible with the flows. The flow were supposed to define the origin of data (such as input/local adjustments even if audittrail should have done that). The advantage of using IC DATA was that I don't need to make many reports to consider all intercompanies. One workbook with a page by entity is enough.

Instead I did the following report format :

                                                                 ENTITY 1   ENTITY 2 DIFFERENCE

INTERCO ACCOUNT AUDITTRAIL

In this case, the audittrail is used for what it is supposed to be. the data shown are relevant but I need to make more reports. One workbook by entity and each page is an intercompany.

I don't think this is the best solution but it answers the requirements.

Dat

[Former Member]

Hi Dat,

The BPC script logic not execute in parent label.Your flow member F_TOT is a parent member of F_OB. Try to use some other flow member and see what result come, are flow member shifted or not?

Khokan

[Former Member]

Hi and thank you for your reply Khokan.

I changed the logic script with only base members for the flow but it is still not working : every flow is still converted into F_OB.

I do not understand your question : what do you mean by flow member shifted ?

Dat

[Former Member]

Hi Dat,

Generally we are not using flow member in ICDATA.The flow member is use in IC matching process,this for define business rule for book  eliminated value. ICDATA  is just copy the data to the unique data source for facilitate the reconciliation process and generate different data source record .ICMatching use for generate data as per data source structure.Flow dimension you use in model it's for ICMatching not for ICData it's a standard scenario. So my advice you to you remove the flow member from script logic ICData and use the closing flow in IC matching business rule.

Khokan