Reporting on-premise

Reporting v. 87

Released  20 August  2025 - 87.0 / 12 September 2025 - 87.1

Requirements:

*or a separate script (see upgrade guide for details).

Payment card type name limit in Reporting (RTC-52823)

Reporting accepts payment card types with names up to 20 characters. If the name is longer, it is automatically shortened to fit the limit. This prevents reporting from rejecting valid transactions.

Export codes in RIGAL F-file (RTC-51526)

The RIGAL F-file includes new export codes that give more detailed insights into transactions.

Available codes:

• IRN – OK status

• ISO – Total value of paid customer orders

• IXP – Number of items excluding open PLU

• IQP – Requested price

• IEP – Changed price

• IBS – Deleted items in parked receipts

Some codes require extra setup in the POS Services configuration file:

• IBL – Tracks transactions that change drawer amounts (requires StoreSettlementCashDrawerTenderControlTypes)

• R01–R99 – Shows turnover by coupon type (requires StoreSettlementCouponTypes)

• Q01–Q99 – Shows amount or quantity by webshop card type (requires StoreSettlementPaymentCardTypes)

This makes it possible to monitor transactions in more detail and to report based on specific payment, coupon, or cash drawer changes.

Wet Stock – tank structure and reporting (RTC-48077)

The system imports and processes tank structures, wet stock transactions, and sales when tank–tank group relationships change. It creates a new tank structure and closes the previous one with an end date to keep historical data.

Reports 0750_WetStock and 0751_DailyWetStock require manual updates during Reporting upgrades. Updated report files are available at:
\\Sp-egdev0319.egdev.lan\Distribution\Lindbak POS Reporting\Reports\St1\RTC-48077

Search for members from cash register (RTC-50164)

To prevent timeouts during member searches at the cash register, the query in the procedure GetMemberBonusPoints uses (nolock). This allows the system to read data without waiting for other operations to finish, which improves performance during peak usage.

Manual fix for unknown article sales (RTC-48335)

A package is available to manually fix unknown article sales. It finds sales lines with unknown articles and retrieves the corresponding POSLog data from the Journal database for further lookup.
This process must be handled manually for now. Import functionality will be added later.

Member campaign data handling in sales updates (RTC-51273)

Sales linked to member campaigns use campaign details directly from the POSLog. This improves accuracy by ensuring each sale connects only to its actual campaign, avoiding links to unrelated campaigns.

Balance registration – avoiding duplicate transactions (RTC-51959)

Balance transactions use only the transaction date from POSLogs, not the full timestamp. This avoids registering the same transaction more than once when timestamps differ but the date is identical.

Improved query performance in RealTime partition job (RTC-11588)

The partition job in RealTime uses the same optimized query as the N-job. This improves performance for customers using SQL Enterprise, especially when handling large data volumes.

Improved data availability in reports (RTC-45386)

The field for line notes is available in the view pub.vSales, and the receipt reference is available in the view pub.vReceipts. This makes it easier to include these details in custom reports and data exports.

Track time spent per receipt (RTC-51008)

A new field called duration is added to retail transaction data. It shows how long a transaction takes from start to finish. This makes it possible to report on time spent per receipt and helps understand customer behavior and checkout efficiency.

Procurement orders update without order lines (RTC-51206)

Procurement orders with status 2 update even when they have no order lines. This prevents merge errors and supports smoother order processing.

Reporting v. 86

Released 21 May 2025 - 86.0 / 12 September 2025 - 86.1

Requirements:

*or a separate script (see upgrade guide for details).

Payment card type name limit in Reporting (RTC-52823)

Reporting accepts payment card types with names up to 20 characters. If the name is longer, it is automatically shortened to fit the limit. This prevents reporting from rejecting valid transactions.

Extended Promotion details in DimPromotion (RT-48667)

DimPromotion includes the actual names of both Promotion and Offer. This makes it easier to understand and identify promotions when reviewing data or reports.

Merging items (RTC-48751)

The StagingMerger job in LIP has been updated to provide more accurate error descriptions.

Reporting v. 85

Released 15th of May 2025

Requirements:

*or a separate script (see upgrade guide for details).

Return reason codes report

(RTC-45714)

Shows reason codes used for returns on sale transactions. Helps identify why items are returned, making it easier to follow up on common issues or trends.

The report is available in the report list under EG Retail Chain.

Full description of report: List of reports - EG Retail Chain - Confluence EG A/S

Sales revenue report

(RTC-46685)

Shows sales revenue across all cash registers in stores where sales take place. Helps track store performance and compare sales between locations.

Details about how the report works are available in the report list on Confluence:

List of reports - EG Retail Chain - Confluence EG A/S

Articles sold with open price

(RTC-47002)

The data cube includes a new measure that shows how many articles are sold using open price. This helps track and analyze manually priced sales more accurately.

Cashier safety report

(RTC-47002)

A new report shows statistics per cashier, such as transaction counts and exceptions. This supports internal control and improves visibility on individual cashier activity. Requires Reporting version 84.

For a full description, see: List of reports - EG Retail Chain - Confluence EG A/S

Compare sales between two stores

(RTC-47005)

Use a new report to compare sales between two stores. The report shows differences in revenue, number of transactions, and other key sales figures side by side. This helps identify trends, performance gaps, or similarities between store locations.

Detailed explanation is available in Confluence.: List of reports - EG Retail Chain - Confluence EG A/S

Cashier report

(RTC-47013)

Shows total revenue and a breakdown of payment methods used by each cashier during their shift. This helps store managers track sales performance and understand how customers pay:.List of reports - EG Retail Chain - Confluence EG A/S

Workstation report

(RTC-47014)

Shows sales and payment methods per workstation. Use this report to see how much each workstation sells and which payment methods are used. This makes it easier to track performance and understand how customers pay at different locations or registers: List of reports - EG Retail Chain - Confluence EG A/S

Order line changes added to history table in POSLog extractor

(RTC-47395)

The POSLog extractor adds order line changes to the history table. This makes it possible to report on changes made to individual order lines, such as quantity or product updates, using the on-premise reporting solution.

Order line history tracking

(RTC-47396)

Order lines import into the FactOrderLinesHistory table. This makes it possible to report on changes to individual order lines over time.

Cleanup of FactOrderLinesHistory

(RTC-47397)

A new package has been implemented to clean up old records in the FactOrderLinesHistory table. The retention period is configurable via the parameter varDaysToKeepOrderHistoryLines in the LindbakPOSReportingConfig.dtsConfig file.

The package runs as part of the N-job and is enabled by default.

Audit of shopping control

(RTC-47779)

To enhance reporting on shopping cart controls, a new control transaction has been added to the Reporting database and cube. Additionally, a new Audit dimension has been introduced to enable reporting on the results of these controls.

Age control enhancement

(RTC-47792)

The existing solution has been extended to include social/age control by adding the corresponding dimension name and integrating the related data into the OLAP cube.

Payment card types

(RTC-47794)

To enhance reporting on card types, the database and OLAP cube have been extended to include PaymentCardTypes.

Improvements

Bonus calculation for returns with zero quantity items (RTC-47629)

Bonus points are no longer calculated for returned items if the quantity is zero. This avoids incorrect bonus adjustments when returns include items with no remaining quantity.

Supplier information (RTC-48639)

To support reporting on suppliers, the article information in the OLAP cube has been extended to include SupplierItemNO.

Reporting v. 84

Released 7th of February 2025

Requirements:

*or a separate script (see upgrade guide for details).

New control transactions

(RTC-43210, RTC-43209)

Reporting supports new control transactions: Float and Spot check.

New report: Cash drawer control transactions (0161)

(RTC-46639)

New report showing control transactions which affects the cash drawer. For complete documentation see confluence: List of reports.

Reporting view pub.vSales extended with LineNote

(RTC-44249)

Line notes from article lines has been included in the view: pub.vSales.

Cash settlement: F-file supports new currencies

(RTC-41883)

F-file was extended with new settlement codes to support new currencies: CAD, CHF and JPY.

Improvement

Avoid duplicate balance transactions

(RTC-44695)

Balance transaction updates have been improved to avoid duplicates.

Reporting v. 83

Released 24.06.2024

Requirements:

*or a separate script (see upgrade guide for details).

End of day consolidation

(RTC-41365)

Solution to export end of day data to a new blob type: Reporting.Export.EndOfBusinessDayStatistics.

Solution consists of two parts:

• when EOBD receipts are updated from cash register, total number of EOBD candidates is saved in a new column WorkstationsCount in table dbo.FactEndOfBusinessday.

• new on-prem LIP-job EndOfBusinessDayStatisticsExport in ReportingDataIntegration package will check new entries in FactEndOfBusinessDay table and see if the number of EOBD receipts for given store and date matches the number in WorkstationsCount (the job runs on schedule, default: every minute). If it does, the job will export EOBD data and publish it to the configured blob storage.

For further technical information about the job, see ReportingDataIntegration LIP package documentation.

Further information about the content in EndOfBusinessDayStatisticsExport can be found swagger (ReportingService): https://docs.egretail.cloud/.