topic Re: Technical settings in SAP for /QTQVC/ tables in QlikView

Technical settings in SAP for /QTQVC/ tables

sschiller — Mon, 26 Jan 2026 18:19:17 GMT

Hi,

in SAP, I see table /QTQVC/STATUS defined with active flag "log data changes" in technical settings. By this, a log entry is written in table DBTABLOG. How can those entries in DBTABLOG be deleted and is it really necessary to log data changes on this table? Or how to get rid of this table as we do not have change permission for /QTQVC/ namespace.

Regards,

Sebastian Schiller

Re: Technical settings in SAP for /QTQVC/ tables

sschiller — Mon, 23 May 2022 13:17:59 GMT

No one with experiences on this? How do I get support?

Re: Technical settings in SAP for /QTQVC/ tables

marcus_sommer — Mon, 23 May 2022 13:53:18 GMT

I'm far away from having knowledge of SAP but I think it's the default behaviour from SAP that if any data are changing that this will be logged. Further AFAIK nothing should be deleted within SAP else it's important to track each new record and/or the change of an existing one. If anything is wrong an appropriate change on the values and/or a revers record needs to created - and will be logged. This depends purely on SAP respectively your company permissions how they would like/must handle the processing.

But this doesn't mean that you need to keep all data within Qlik else you could delete unwanted data there or maybe better just to flag them with 'old', 'invalid', 'data-quality score of X' whatever ...

- Marcus

Re: Technical settings in SAP for /QTQVC/ tables

sschiller — Mon, 23 May 2022 14:07:06 GMT

Markus,

thanks for the reply. As I see it, the question has to be answered by someone who knows about the provision of data in SAP. The mentioned data base tables within the QLIK namespace and their setting are in responsibility of QLIK and I hope that someone can answer this as the settings mentioned can be a DB and storage killer - especially in a memory data base environment as HDB.

Looking forward a hint from technical support or where to reach out for this.

Regards,

Sebastian

Re: Technical settings in SAP for /QTQVC/ tables

marcus_sommer — Mon, 23 May 2022 15:03:07 GMT

I'm not sure if I understand you right but I assume that you have a SAP connector and pulling with it data to Qlik. There may a more or less advanced wizard included to test the connection, search for tables, choosing fields and maybe even do some simple transformation - but in the end it's just a SQL statement which is executed from SAP.

Like with all other data-sources you will need an incremental logic to handle bigger data-sets. Implementing one may not be trivial but within the community and also outside are various examples how it might be done:

How To Master QlikView Incremental Load (quickintelligence.co.uk)

- Marcus

Re: Technical settings in SAP for /QTQVC/ tables

sschiller — Tue, 24 May 2022 08:57:35 GMT

Hi,

no, this is not my question.

We have received SAP coding in namespace of QLIK, were we find the mentioned table /QTQVC/STATUS defined in SAP DDIC with technical settings of active table change logging. And this table is obviously for movement data type where many entries are written. This causes a high load of change entries that are obviously unnecessary. A support request of our customer to me is now hoe to reduce the load of change logs!?

But this can only be changed by the owner of the table which is QLIK obviously. Do you have a support for the SAP side implementations?

Regards,

Sebastian

Re: Technical settings in SAP for /QTQVC/ tables

marcus_sommer — Tue, 24 May 2022 09:08:47 GMT

@Sonja_Bauernfeind could you help on the matter respectively forwarding it to the right guys?

- Marcus

Re: Technical settings in SAP for /QTQVC/ tables

Doner — Tue, 30 Apr 2024 12:20:43 GMT

Hi,
Has the matter been resolved?
Does the "log data changes" flag have to be active?

Re: Technical settings in SAP for /QTQVC/ tables

FloHero — Tue, 30 Apr 2024 12:48:53 GMT

Hello Sebastian,

maybe this link will help you

https://help.qlik.com/en-US/connectors/Subsystems/SAP_Connectors_Help/Content/Connectors_SAP/Important-general-information.htm

Florian

Re: Technical settings in SAP for /QTQVC/ tables

sschiller — Tue, 30 Apr 2024 13:07:30 GMT

Hi,

partially resolved... as we do not have received any technical feedback, the root cause is still present (active flag in technical settings, cannot be changed in the installed environment as the namespace is protected). This is something that must be done in source development system and potentially updated. For me this is a bug in deployment.

We added some of the /QTQVC/-tables to archiving object BC_DBLOGS to reduce the load in SAP's change log table DBTABLOG. Now we have at least a constant instead of an increasing load coming from these tables.

Regards,

Sebastian

Re: Technical settings in SAP for /QTQVC/ tables

sschiller — Tue, 30 Apr 2024 13:09:52 GMT

Hi Florian,

no, it doesn't help. The information is about the content of the tables but the reported issue and question is about the technical setup of at least the status table. As mentioned, the jobs are performing entries into /QTQVC/STATUS which results in a change log entry in DBTABLOG. This shouldn't be the case for tables containing movement data.

Sebastian

Re: Technical settings in SAP for /QTQVC/ tables

FloHero — Tue, 30 Apr 2024 13:15:39 GMT

Which version of SAP Connector are you using?

Re: Technical settings in SAP for /QTQVC/ tables

sschiller — Tue, 30 Apr 2024 13:19:11 GMT

How to identify this from SAP side?

Re: Technical settings in SAP for /QTQVC/ tables

FloHero — Thu, 02 May 2024 07:53:43 GMT

The release be found in the connector logs, for example here:

C:\ProgramData\QlikTech\Custom Data\QvBexConnector\Log

C:\ProgramData\QlikTech\Custom Data\QvSAPSqlConnector\Log

Re: Technical settings in SAP for /QTQVC/ tables

sschiller — Thu, 02 May 2024 11:51:13 GMT

As this is on client side, I unfortunatelly cannot answer this. In addition, I do not see a relation as the technical setting I'm refering to is a setting for the defined table on SAP side, which cannot be overruled from any client.