Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remote Table Replication - Design Time Object for Calculation View & Fulltext Index Replicas #20751

Closed
ezennerGRE opened this issue Nov 23, 2022 · 3 comments
Assignees

Comments

@ezennerGRE
Copy link

ezennerGRE commented Nov 23, 2022

Tutorials: https://developers.sap.com/tutorials/hana-cloud-mission-extend-09.html

This tutorial has been hugely helpful for simple table replication from an S/4HANA instance. We are running into two issues with the remote table replication. Could you please provide guidance on these common scenarios?

  1. When attempting to deploy a calculation view with a replication table that is created using the demo, we receive the error "The file requires "db://S4HANA_BSEG_LCL" which is not provided by any file". I believe this is because following the tutorial creates the replication table via SQL without a design time object. From our experience a design time object is required for calculation view references in BAS. For example, we've created .hdbvirtualtable files with text definitions of "VIRTUAL TABLE "S4HANA_AUSP" AT "S4HANA"."".SAPABAP1.AUSP". What would the corresponding file type and text definition be of the table replica created in step 3? Alternative, is there a way to reference the replica in a calculation view without a design time definition?

  2. Replication of certain virtual tables (e.g. PRPS, LFM1) fail with "Fail: Cross-DB ATR doesn't support table with ASYNC fulltext index". We are not looking to replicate the full text index as it exists in our S/4HANA DB. Is there a way to replicate the raw data of these source tables? We're open to any workaround here.

Thanks in advance!
-Eric

@ezennerGRE ezennerGRE changed the title Remote Table Replication - Design Time Object for Calculation View Remote Table Replication - Design Time Object for Calculation View & Fulltext Index Replicas Nov 23, 2022
@jmmargo
Copy link
Contributor

jmmargo commented Aug 12, 2024

@thomashammerSAP I am reassigning this issue to you. Please provide a response to the feedback.

@whome000
Copy link

Tutorials: https://developers.sap.com/tutorials/hana-cloud-mission-extend-09.html

This tutorial has been hugely helpful for simple table replication from an S/4HANA instance. We are running into two issues with the remote table replication. Could you please provide guidance on these common scenarios?

  1. When attempting to deploy a calculation view with a replication table that is created using the demo, we receive the error "The file requires "db://S4HANA_BSEG_LCL" which is not provided by any file". I believe this is because following the tutorial creates the replication table via SQL without a design time object. From our experience a design time object is required for calculation view references in BAS. For example, we've created .hdbvirtualtable files with text definitions of "VIRTUAL TABLE "S4HANA_AUSP" AT "S4HANA"."".SAPABAP1.AUSP". What would the corresponding file type and text definition be of the table replica created in step 3? Alternative, is there a way to reference the replica in a calculation view without a design time definition?
  2. Replication of certain virtual tables (e.g. PRPS, LFM1) fail with "Fail: Cross-DB ATR doesn't support table with ASYNC fulltext index". We are not looking to replicate the full text index as it exists in our S/4HANA DB. Is there a way to replicate the raw data of these source tables? We're open to any workaround here.

Thanks in advance! -Eric

Sorry for the belated reply.

#1. We only support replicating physical objects and do not support virtual tables from the source system. To overcome this, you can try to create one manually in the target schema with the same name. Hopefully this can resolve the issue.

#2. The fulltext index error was due to the difference of how they are implemented between the 2 systems. This needed a migration logic built into the replication. The issue is resolved now and requires an upgrade to the following versions HANA 2.0 Rev72+, Rev67.03+, Rev59.10+ (+ means 'or higher' for the mentioned SPS)

Best regards,
Tae-Suk Son
SAP HANA Product Management

@jmmargo
Copy link
Contributor

jmmargo commented Aug 14, 2024

Thank you @whome00 As a solution was provided, I am closing this issue. Please reopen it if needed.

@jmmargo jmmargo closed this as completed Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants