ReSA accepts POS/OMS data as an RTLOG file. It then performs an initial validation on the data. This data is then loaded into the ReSA database tables. A batch process then audits the uploaded data. The store day records in ReSA are locked during validation to prevent any manual updates of the data. All errors are written to error tables.
The data import is considered complete once the batch process has updated the store data and audit status for each store day record.
This chapter contains the following topics to help you understand the import process:
The following is the process followed while importing data into ReSA.
Create a Store Day.
ReSA requires a store day to process data from POS/OMS. The creation of store day for the current day automatically happens at the end of processing for the previous day.
Receive RTLOG from POS and OMS.
Filter the duplicate transactions received from POS and OMS.
Import RTLOG into ReSA.
Run batch files to import the RTLOG files into ReSA.
Validate RTLOG with the reference data and configuration options during import.
Run audit rules and totals on the uploaded data.
Flag auditing failures as well as mismatched with reference data for manual audit.
Close store day once all RTLOGs for the business day are processed.
It is necessary to close the Store Day in the POS system, to enable the HQ auditors to perform audit of the sales data after it is imported in the ReSA system.
The following is a list of valid ReSA transaction types.
Transaction Code | Transaction Description |
---|---|
OPEN | Open |
CLOSE | Close |
COND | Daily Store Conditions |
DCLOSE | Day close indicator |
LOAN | Loan |
METER | Meter Reading for Fuel |
NOSALE | No Sale |
PAIDIN | Paid In |
PAIDOU | Paid Out |
PULL | Pull |
PUMPT | Pump Test for Fuel |
PVOID | Post Void |
REFUND | Return of customer's original check |
RETURN | Return |
SALE | Sale |
TANKDP | Tank Dip |
TOTAL | POS generated totals |
EEXCH | Even exchange |
VOID | Void (aborted transaction) |