Copy sequence not workinq from AO only RSPLAN trace mode, BPC 11.1 Embedded Model BW4/HANA

[cristina_ungureanu]

Hello,

I have created a planning function and a sequence, when I run the sequence from RSPLAN in trace mode, the copy is done and I can save the data. But from AO, I receive a successful message but the query is not refreshed with the copied values.

I am on BPC 11.1, BW/4HANA.

I will appreciate your help.

Best Regards,

Cristina Ungureanu

[mayiya]

Hi Cristina.

I´m facing the same issue, how could you resolve it ?

[scalou1977]

Hello,

Did you saved the data in AFO once the planning sequence finished ?

Pascal.

[cristina_ungureanu]

Hello Maria,

In my case the fiscal period was incomplete, so I have generated the fiscal period using: RSRHIERARCHYVIRT.

Best regards,

Cristina Ungureanu

[former_member283567]

Hello,

We faced the same issue several times.
We are very grateful for all the information we could get to solve our issues.
On our turn we would like to share our solutions with you as it took us a lot of time to figure out these solutions.
We are using PAK (Planning Application Kit) for Integrated Planning on HANA.
We use virtual cubes in our planning model based on HANA calculation views.
Based on the technical concept of SAP delivered virtual cube /ERP/SFIN_V20 (S/4HANA Financials: Plan Data from ACDOCP)

Issue 1
RSPLAN error for planning sequence in test trace mode without clear explanation of the error.
We found out that running in the 'normal' step mode gave us clear information of the error.
E.g. we hade a NVARCHAR3 calculation view field linked to a NUMC4 infoobject (Purchase Order Item).
The PAK did not allow this and in the normal test run there was a clear message explaining this.
We solved this by creating a calculated column in the calculation view with type NVARCHAR with length 4 and linking this calculated column to the NUMC4 infoobject in the virtual cube.

Issue 2
One of the errors was related to NULL values for date fields.
Date fields can be initial (00000000) but must not be empty (NULL).
We fixed this in the calculation view by using calculated columns and linking the calculated columns to the virtual cube date infoobjects.
Calculated column formula example: if( isnull("NETDT"), date(00000000), date("NETDT"))
Especially when you do a join lookup in the calculation view the (date) fields are NULL when the lookup does not find anything.
Transaction SM21 also gives clear information on this type of error.

Issue 3
We had date values outside (before) the permitted date interval according to transaction RSRHIERARCHYVIRT.

Issue 4
Planning sequence runs ok in RSPLAN trace mode, but in 'normal' mode it gives error: Invalid characteristic combinations exist (RSPLS_CR-070).
Indeed, according to OSS note 1911914 (BW In-memory Planning will not be Executed in Trace Mode) the Hana engine (PAK) is not triggered in trace mode. PAK seems to be more strict.
The error's long text gave the details of the characteristic combination, but we had no clue which infoobject had a wrong value.
After 1,5 day (!) search, trial & error and process of elimination we found out that the empty value (#, unassigned) was not allowed for an infoobject (Data Origin) that we had created with reference to technical infoobject 0INFOPROV.
However, we could select the unassigned value in the planning filter for this infoobject, PAK gave an error on this, trace mode did not.
Maybe this is not completely illogical, as BW does not allow you to use infoobjects with reference to technical infoobjects. We once tried to use an infoobject with reference to audit infoobject 0AUSER. In that case we received an error message during cube definition, telling us not to use technical fields.
In our humble opinion it is a small bug or that PAK does not allow the empty value for an infoobject with reference to 0INFOPROV, or it is a bug that BW does not give an error message when including an infoobject with reference to 0INFOPROV in the planning model.

We hope by sharing this we save you valuable time.

[former_member283567]

Sorry for the late reply. Maybe useful for others.
We once had the same error.
In our case, the real problem was not in the Characteristic Combination, but in the Data Slice, that blocked the Characteristic Combination.
So the error message was a bit misleading.
When testing the planning sequence in RSPLAN, we received a clear error message explaining that it was the Data Slice that blocked the data.

[cristina_ungureanu]

Hello experts,

I have again a similar problem, but only on 0RSPL_COPY functions, in RSPLAN is working properly but when loading it from AFO I receive the following errors(An important mention I have this issue only in Production.):

xxx function ended with errors (RSPLF-114, BHP): Diagnosis Errors have occurred while executing planning function xxx.

PE error 2.048: column store error: alterPlanningSession error: [38001] Session '20210618134145_9252800' not valid. Last error: Condition (RSR_PE-005, BHP): Diagnosis Internal Planning Engine error on HANA System Response &1: &2 &3 &4 Procedure Please contact your system administrator. Procedure for System Administration Check the SAP HANA system information to analyze the system's health and check for any general problems or unexpected state. Use the system time provided for the problem to locate any unusual or exceptional entries in the SAP HANA index server diagnosis files (trace or alert files). Check the diagnosis files for error entries containing the prefix 'ple_' in any words or fragments. If this analysis does not yield a known and solved issue, open a SAP support ticket. If possible, attach a detailed description of how to reproduce the problem, along with the identified diagnosis file passages for initial analysis.

Errors occurred while executing xxxx (RSPLS-411, BHP): Diagnosis Errors messages occurred when you executed the sequence &V1& (&V2 & ). Procedure Analyze the log.

I will highly appreciate your help.

Best regards,

Cristina