Updating QVD files

[#1]

Hi,

I am working on developing a QlikView application for invoicing. I have information in a database (that updates each night) and store my tables as QVD files. However, I am worried that the files will remain static. What is the most common method of updating QVD files before/while publishing the application? Do you use SQL to fill the QVD files with new info from the database or some other common method? A piece of my script is below - how does/can the Header.qvd file get updated with new info?

Load
    BELNR & BUKRS & GJAHR as %DocKey,
    BELNR,
    BLART,
    BUKRS,
    GJAHR,

    POSID,

    Left(POSID,6) as project_code,
    HWAER,
    MONAT,
    UKURS
FROM (qvd)
WHERE GJAHR > 2010 AND BLART <> 'KZ' AND MANDT = 101 AND BLART <> 'ZP';

[MK_QSL]

Search for Incremental Load !

[datanibbler]

Hi Espen,

the usual method for updating qvd is in three steps:

- Load the existing qvd

- Load from the database all data that does not yet exist in that table

- Store the new table again, overwriting the old qvd.

Is that what you want to do? Otherwise I'm afraid I have not yet understood what you are trying to do.

Best regards,

DataNibbler

[qlikmsg4u]

Please go through these

Incremental Load

www.analyticsvidhya.com/blog/2014/09/qlikview-incremental-load/

[Peter_Cammaert]

To read data from SAP, you'll need a connector as the SAP database may be an RDBMS but internally it's still organized as an ancient network DB with loads of metadata.

The connector will take the task of interpreting the complex internal structures off your shoulders. There are two suppliers for SAP connectors. The connectors connect straight to SAP and use a SQL dialect called OpenSQL (defined by SAP).

Then you need to define a staging architecture. How is your data going to be transferred from the source (every night, incrementally, a straight copy of the original tables) and how is it going to be converted into a QlikView datamart (as a separate step? What about renames, data cleansing, aggregations etc.)

Then you will implement these layers as headless QlikView documents whose reloads are triggered before you reload your end-user document. The QlikView server is an ideal environment to set-up that chain.

Best,

Peter