HANA ChangeList - Issue Transporting Calculation View

[celo_berger]

Hello,

We've just setup the HALM in our HANA Sidecar, to allow us to move changes from Dev to QA. We've setup the delivery unit, and created a few calculation views. They were captured in changelists, which we then released, and used the transport mechanism to move from dev to QA. However, we're facing an error:

[usw-system][HQ1@HQ1][7/19/2018 10:20:35 AM][Activation][8] Object: EA_KFI.REV_REC.REV_REC_ADJ.calculationview ==> Error Code: 40117

[usw-system][HQ1@HQ1][7/19/2018 10:20:35 AM][Activation][8] Repository: Encountered an error in repository runtime extension;Model inconsistency. Create Scenario failed: The following errors occurred: Index does not exist;Failed to get CalcIndex

We have:

- Replicated all the same tables that exist in dev into QA;

- Done schema mapping from dev into QA;

All the views are working perfectly in fine in dev, so wondering what we could be missing.

Appreciate your support.

Marcelo

[SergioG_TX]

the schema names are the same on both environments right?

are you able to select? do you have any (SAP) client mapping?

what is your SAP HANA SP version and patch ?

are you able to query these tables in the sql console?

is the issue in all the calc views or just a few?

[celo_berger]

We are using SLT to replicate from ECC.

1. The schemas in dev and Q are different, but we have maintained the schema mappings.

DEV= SAPECCD / QA = SAPECCT

2. Yes, I'm able to do a data preview on the replicated tables in QA

3. No SAP client mappings have been maintained

4. SP Version/Patch 2.00.030.00.1522209842

5. Yes, I can query the tables using SQL console

6. We originally were able to move a single calculation view and that has activated successfully. We originally started developing our views in a temporary package (DEV) in the development environment. When we were done, we copied all the views to the "official" package in dev (OFF) which has the delivery unit assigned to it. We then reactivated all of them in the OFF package to capture them in a change list, and that's when we started facing issues.

Thanks for your help!

[SergioG_TX]

did the references from the original package updated to the new package?

[celo_berger]

What I can tell from the schema mapping, yes it did

[celo_berger]

Ok, so I've actually narrowed the issue down.

We have a calculation view that uses data from a flat file that we imported into schema FLAT_FILE in dev. In QA, we've created the exact same schema and we've uploaded the file there too. Both tables have identical names and structures between both systems. I've also provided SELECT access to user _SYS_REPO in both systems.

However, we're getting the error below:

Repository: Encountered an error in repository runtime extension;Model inconsistency. Create Scenario failed: Mapped source attribute FIELD_NAME is missing in node TABLE_NAME(calculationNode (P_INFOR) -> inputs -> input (TABLE_NAME) -> mappings -> mapping (FIELD_NAME))The following errors occurred: Inconsistent calculation model (34011)

Where FIELD_NAME is the field from the table, and TABLE_NAME is the table to which we've imported the flat file.

Again, this is working in DEV. I tried the schema mapping option, but since both schema names are identical, it didn't allow me to do it.

[SergioG_TX]

make sure FIELD_NAME is spelled correctly.. .if you are not using all capital letters... then use "FIELD_NAME" (double quotes) for case sensitive names

[celo_berger]

Hey Sergio, my issue has now morphed into something else. Do you know if there's a way to reset or delete released changelists so we can have a fresh start when trying to move the views? Because changelists try to import the predecessor changelists not yet imported, it is causing some issues due to packages that are no longer used.

Thanks again!

[SergioG_TX]

no there is no way to undo a changelist that has been release... you will need to revert your view change... and re-deploy...

as you mentioned .. the history of the changelists is kept until they are moved out of the next env, (dev-qa... then to prod) for example

[ssurampally]

if you do n't want to import the current change list and it's predecessor change list. you may try this option,

Refactor your views to a different package -- > Capture in a new change list(TR), if you can, then you should be able to ignore the current problem change lists in this case.