Show TOC

 Storage Optimization of Transaction Logs

 

With SAP Customer Activity Repository 2.0 FP1, new mechanisms have been added to help manage the growing size of your POS transaction database and its impact on the performance of analytical scenarios.

Additional Information

This release of SAP Customer Activity Repository provides you with two new ways to manage the size of the transaction log (TLOG) tables to lower your total cost of ownership and reduce SAP HANA-related hardware costs:

  • Archiving and Deleting

    You can use new reports to archive and delete major portions of transactions from the TLOG, keeping only those transaction record qualifiers required by analytical scenarios.

  • Optimizing Customer Extensions

    You can now segregate TLOG customer extensions into one of two database tables, depending on whether the extensions are required by analytical scenarios:

    • /POSDW/TLOGF, for extensions required by analytical scenarios

    • /POSDW/TLOGF_X, for extensions not required by analytical scenarios

Technical Details

Product feature is

New

Country Dependency

Valid for all countries

Software Component Version

RTLPOSDM 300

Application Component

CA-RT-CAR-PIP

Availability

SAP Customer Activity Repository 2.0 FP1

Effects on Customizing

TLOG Extension Optimization

The following BAdIs have been added:

BAdI

Path

BAdI: POS Transaction Log Extension Write Enhancements (/POSDW/TLOGF_X_WRITE_ENH)

Start of the navigation path SAP Customer Activity Repository Next navigation step POS Data Management Next navigation step POS Inbound Processing Next navigation step Customer-Specific Enhancements and BAdI Implementations Next navigation step Enhancements for In-Memory Analytics Next navigation step BAdI Implementations End of the navigation path

BAdI: POS Transaction Log Extension Read Enhancements (/POSDW/TLOGF_X_READ_ENH)

Start of the navigation path SAP Customer Activity Repository Next navigation step POS Data Management Next navigation step POS Inbound Processing Next navigation step Customer-Specific Enhancements and BAdI Implementations Next navigation step Enhancements for In-Memory Analytics Next navigation step BAdI Implementations End of the navigation path

Effects on Existing Data

TLOG Size Optimization

  • The Archiving POS Transactions: Reload Program report (/POSDW/ARCHIVE_RELOAD_HDB_F) was enhanced to allow deleting all the entries that were kept and marked as archived by the archive delete report in order to avoid any data duplication and inconsistencies.

  • The Archiving POS Transactions: Deletion Program report (/POSDW/ARCHIVE_DELETE_HDB_F) was enhanced to allow keeping entries that correspond to a provided record qualifiers list (exclusion list). These entries will then be marked as archived using tables fields.

  • The Restore TLOG Entries From Archiving report (/POSDW/ARCHIVE_RESTORE_TLOG_F) was created to restore archived transaction log (TLOG) entries that correspond to selected record qualifiers and flag those entries as archived.

TLOG Extension Optimization

  • The Classify TLOG Tables report (/POSDW/CLASSIFY_TLOG_TABLES) was created to classify the /POSDW/TLOGF, /POSDW/TLOGF_EXT, and /POSDW/TLOGF_Xtables and control the distribution of the tables (or table partitions) across the different nodes of a distributed SAP HANA database.

See also

Optimization of POS Transaction Tables