BPC Controls Error:COLLECT is not permitted for non-numeric fields.

[Former Member]

Hi Experts,

I am trying to a run a Control to Validate Data for Balance Carry Forward Scenario where Carry Forwarded Balance = Prior Year Closing Balances.

I am implementing Real Time Consolidation on S4 HANA on premise 1610 Release stack 02(05/2017) FP.

Lets say I have carry forwarded the Balances from 2017 Dec to 2018 Jan, then I am running the Control in 2018 Jan.

Below is the Control Snapshot:

When I am running Control in 2018 Jan, I am getting the following error:

A Snapshot from the Composite Provider showing 2018 Jan and Dec 2017 Balances:

What are we missing here?

Any Suggestions..

Regards,
SHUBHAM

[lucas_costa3]

Look at recent notes around controls in the launchpad. Had some issues in controls fixed a couple of months ago.

Filter the component BW-PLA-BPC-CTR (Controls) and sort by Released On

[damovand]

Hello,

Please provide a larger screen print of the control configuration and your BW version and SP#

Are you using any compounding objects?

Do you have any dimension members with leading zeroes and if so do you have alpha conversion enabled?

Do you have any errors on the server side, SLG1, SM21 or ST22?

Best Regards,

Leila Lappin

[Former Member]

Hi,

I am attaching the Controls rule.control-rule.png

Yes I have entity info object /ERP/ECOMP and /ERP/ICOMP which has leading zeroes and alpha conversion is enabled.

The error from ST22 says below:

Error in the ABAP application program. | | | | The current ABAP program "CL_UJCTRL_READ_DATA_PF_RT=====CP" had to be | | terminated because it found a | | statement that could not be executed.

In statement "COLLECT [wa INTO] itab", all fields that do not belong to | | the table must have a numeric type (types I, F and P). | | In the present case, this condition is not met for table | | "<LT_TRANS_DATA_COLLECTED>".

If the error occurs in a non-modfied SAP program, you might be able to | | find a solution in the SAP Notes system. If you have access to the SAP | | Notes system, check there first using the following keywords: | | | | "TABLE_COLLECT_CHAR_IN_FUNCTION" | | "CL_UJCTRL_READ_DATA_PF_RT=====CP" bzw. CL_UJCTRL_READ_DATA_PF_RT=====CM005 | | "IF_UJCTRL_READ_DATA_PF_RT~READ_TRANS_DATA"

I am trying to get any SAP note but haven't come across any till now.

Regards,
SHUBHAM

[damovand]

Hello,

I have found only one report of this issue for BPC and it is currently being investigated. However, I found fourteen notes for this error for components FIN-SEM-BCS-INT-BI or FIN-FB. Depending on your version of FI, these may be helpful. I have attached the list of notes. If these notes are not helpful then I recommend reporting this to BPC support.

If you end up reporting this issue, please be sure to include the following details as well as your S4HANA, BW, and if you are on BW 7.4 your BPC versions.

• Is this the first time configuring control for BPC environment?
• Is this error specific to this control or general across all controls?
• Have you confirmed if the data region the control is referring has transaction values?
• Your BPC and BW versions, including SP#

Best Regards,

Leila Lappin

cusersi815070documentsnotes-for-table-collect-char.txt

[Former Member]

Hi Leila,

I have raised an incident for this.

Strange thing is, that the Control runs in DEV and the same has been imported to Quality using the SAP program RSBPCA_CONS_RULE_TRANS.

There in Quality, it throws the error on same data set.

Regards,
SHUBHAM

[damovand]

Hi Shubham,

Based on what I found while researching this error, this could be something in your finance data. We will know.

Best Regards,

Leila Lappin

[Former Member]

Hi Leila,

We did some debugging and came to a conclusion to not leave /erp/compcode dimension blank in Controls.

We have kept Audit and Compcode as breakdown dimension. Now after assigning the TOTAL_COMPCODE to model, we assigned it in Controls and now it is working.

Thanks for your support!!

SHUBHAM

[damovand]

Hello Shubham,

That is great that you have it working. Just to be clear, we are also working on the root cause of this issue. Thank you for the update.

Best Regards,

Leila Lappin