Explore topic-wise InterviewSolutions in .

Saimptlogfin.pc CREATES a balance group entry (SA_BALANCE_GROUP table) for the store/day, cancels post voided transactions, updates the DATA Status to ‘Fully Loaded’ if the ‘DCLOSE’ transaction is received (sets Store Status to ‘Closed’ if single level AUDIT). It also REMOVES missing transaction records that are now present due to loading data out of sequence.

Saimptlogfin.pc creates a balance group entry (SA_BALANCE_GROUP table) for the store/day, cancels post voided transactions, updates the Data Status to ‘Fully Loaded’ if the ‘DCLOSE’ transaction is received (sets Store Status to ‘Closed’ if single level audit). It also removes missing transaction records that are now present due to loading data out of sequence.

ReSA does not have its own SKU/UPC tables. Sagetref.pc creates a NUMBER of output files from different RMS tables such as ITEM_MASTER, VAR_UPC_EAN etc and the saimptlog.pc batch program READS the files to perform field level VALIDATION. Some EXAMPLES of these output files are a list of all valid SKUs, UPCS, promotions, codes, tenders, etc…

ReSA does not have its own SKU/UPC tables. Sagetref.pc creates a number of output files from different RMS tables such as ITEM_MASTER, VAR_UPC_EAN etc and the saimptlog.pc batch program reads the files to perform field level validation. Some examples of these output files are a list of all valid SKUs, UPCs, promotions, codes, tenders, etc…

Sagetref.pc read the sa_cc_val and WRITES to the credit card MAPPINGS file. This table is used to maintain information for credit card validation. This table holds the prefix range, credit card number length, and type of validation (modulus 10 or none) for a specific credit card.

This table is maintained by the DBA or IT Group. There are no front-end screens.

Sagetref.pc read the sa_cc_val and writes to the credit card mappings file. This table is used to maintain information for credit card validation. This table holds the prefix range, credit card number length, and type of validation (modulus 10 or none) for a specific credit card.

This table is maintained by the DBA or IT Group. There are no front-end screens.

There is no setting in ReSA to DEFINE if a store will be trickle polled. The only requirement is to send a ‘DCLOSE’ transaction to ReSA at the end of the day. If a Retail Transaction Log (RTLOG) is LOADED but does not CONTAIN the ‘DCLOSE’ transaction, the Data STATUS is UPDATED to ‘Partially Loaded’. If the ‘DCLOSE’ transaction is received the Data Status is updated to ‘Fully Loaded’.

There is no setting in ReSA to define if a store will be trickle polled. The only requirement is to send a ‘DCLOSE’ transaction to ReSA at the end of the day. If a Retail Transaction Log (RTLOG) is loaded but does not contain the ‘DCLOSE’ transaction, the Data Status is updated to ‘Partially Loaded’. If the ‘DCLOSE’ transaction is received the Data Status is updated to ‘Fully Loaded’.

When the ‘D CLOSE’ record is received from the Point of SALE (POS) in a multi-LEVEL audit scenario, RESA updates the Data Status to ‘Fully Loaded’. If errors are found, ReSA sets the Audit Status to ‘Store Errors Pending’. If no errors are found, ReSA sets the Audit Status to ‘Audited’ and Store Status will be Worksheet.

 When the ‘D CLOSE’ record is received from the POS in single level audit scenario, ReSA updates the Data Status to ‘Fully Loaded’ and the Store Status to ‘Closed’. If errors are found, ReSA sets the Audit Status to ‘HQ Errors Pending’. If no errors are found, ReSA sets the Audit Status to ‘Audited’.

When the ‘D CLOSE’ record is received from the Point of Sale (POS) in a multi-level audit scenario, ReSA updates the Data Status to ‘Fully Loaded’. If errors are found, ReSA sets the Audit Status to ‘Store Errors Pending’. If no errors are found, ReSA sets the Audit Status to ‘Audited’ and Store Status will be Worksheet.

 When the ‘D CLOSE’ record is received from the POS in single level audit scenario, ReSA updates the Data Status to ‘Fully Loaded’ and the Store Status to ‘Closed’. If errors are found, ReSA sets the Audit Status to ‘HQ Errors Pending’. If no errors are found, ReSA sets the Audit Status to ‘Audited’.

RESA requires the ‘DCLOSE’ transaction in both multi-LEVEL and single level audit scenarios. This transaction indicates to ReSA that all Point of SALES (POS) TRANSACTIONS have been RECEIVED. Once the ‘DCLOSE’ transaction is received, ReSA will not accept any more RTLOGs for the given store/day.

ReSA requires the ‘DCLOSE’ transaction in both multi-level and single level audit scenarios. This transaction indicates to ReSA that all Point of Sales (POS) transactions have been received. Once the ‘DCLOSE’ transaction is received, ReSA will not accept any more RTLOGs for the given store/day.

Stock Counts, RECEIPTS, Transfers and Inventory Adjustments are not sent through ReSA. These types of transactions can either be supported by Retail Store Systems (RSS) or loaded directly into the Retail Merchandise System (RMS) from the POS. Transfer Ins, Transfer OUTS, Receipts, and Return to Vendor (RTVs) can be loaded directly into RMS using upload files. 

Main transactions processed by ReSA are the following:

• Sales
• Returns
• Exchanges
• Voids
• POST Voids
• Paid In / Paid Out
• No Sales
• Pull
• Loan
• Open
• Close
• FUEL Transactions (e.g. Tank Dips, Meter Readings, etc…) 

NOTE: Not all POS systems support all of these transactions.

Stock Counts, Receipts, Transfers and Inventory Adjustments are not sent through ReSA. These types of transactions can either be supported by Retail Store Systems (RSS) or loaded directly into the Retail Merchandise System (RMS) from the POS. Transfer Ins, Transfer Outs, Receipts, and Return to Vendor (RTVs) can be loaded directly into RMS using upload files. 

Main transactions processed by ReSA are the following:

NOTE: Not all POS systems support all of these transactions.

These are USED for the Flash Sales reports – ENABLING the business to determine when a store has sufficient trading history. The date to determine comp. STATUS can be based on three FACTORS: store OPEN date, remodel date, or acquire date. These dates are held on the store table in the Retail Merchandising System (RMS).

These are used for the Flash Sales reports – enabling the business to determine when a store has sufficient trading history. The date to determine comp. Status can be based on three factors: store open date, remodel date, or acquire date. These dates are held on the store table in the Retail Merchandising System (RMS).

To verify whether a user was granted a privilege, or a role was granted a privilege, you can use the following (for this example, RMSDEV101A is USED): 

Check to see if the user was granted the SYSTEM privilege directly: 

SQL> desc dba_sys_privs 

SQL> select * from dba_sys_privs where grantee = 'RMSDEV101A';

If the result for the above QUERY does not show the system PRIVILEGES granted for the user, check to see what roles the user was granted, and then check to see what privs has been granted to that role:

SQL> desc dba_role_privs 

SQL> select * from dba_sys_privs where grantee = 'DEVELOPER'; 

Whenever you want to see what roles and system privileges a user has and what system privileges are assigned to specific roles, you should look at the dba_role_privs and dba_sys_privs views. 

From a ReSA perspective a user should have the following privileges to create totals and views: 

• Create any view 
• Create any procedure 
• Alter any procedure 
• Drop any view 
• Drop any procedure

To verify whether a user was granted a privilege, or a role was granted a privilege, you can use the following (for this example, RMSDEV101A is used): 

Check to see if the user was granted the system privilege directly: 

SQL> desc dba_sys_privs 

SQL> select * from dba_sys_privs where grantee = 'RMSDEV101A';

If the result for the above query does not show the system privileges granted for the user, check to see what roles the user was granted, and then check to see what privs has been granted to that role:

SQL> desc dba_role_privs 

SQL> select * from dba_sys_privs where grantee = 'DEVELOPER'; 

Whenever you want to see what roles and system privileges a user has and what system privileges are assigned to specific roles, you should look at the dba_role_privs and dba_sys_privs views. 

From a ReSA perspective a user should have the following privileges to create totals and views: 

SAEXPGL exports totals to ORACLE FINANCIAL Application general ledger for: 

• Sales transactions 
• Tenders 
• Paid-ins 
• Paid-outs 
• Taxes 

This export batch module works by first GETTING the store day. Then it finds the totals to export and verifies that individual totals CONTAIN no errors for either the store/day (if store/day is the unit-of-work defined by the user) or store/day/total (if store/day/total is the unit-of-work defined by the user). Next the module looks at the SA_FIF_ORA_CROSS_REF table to determine which Oracle account ID (Cost Center ID) it needs to export to. Determine if the selected store/day/total has been previously exported; if so, reverse the previous posting, and post the latest adjustments to the General Ledger (GL) staging table. Finally it moves the data to the Oracle staging GL_INTERFACE. (No RMS staging table is involved.)

SAEXPGL exports totals to Oracle Financial Application general ledger for: 

This export batch module works by first getting the store day. Then it finds the totals to export and verifies that individual totals contain no errors for either the store/day (if store/day is the unit-of-work defined by the user) or store/day/total (if store/day/total is the unit-of-work defined by the user). Next the module looks at the SA_FIF_ORA_CROSS_REF table to determine which Oracle account ID (Cost Center ID) it needs to export to. Determine if the selected store/day/total has been previously exported; if so, reverse the previous posting, and post the latest adjustments to the General Ledger (GL) staging table. Finally it moves the data to the Oracle staging GL_INTERFACE. (No RMS staging table is involved.)

This information is maintained on the Store Data window of the Store Maintenance form in the Retail Merchandising System (RMS). The multi-LEVEL audit settings for INDIVIDUAL stores are stored on the ds_store_data table. Stores are defined as multi-level audit stores when the system_code field is ‘MLA’and the imp_exp field is ‘I’ for a specific store. If these settings are not defined for a store, then RESA defines the store as a single level audit store. Single level audit would be defined if the user chooses ‘Point Of SALE (POS)’ as an import for a given store. 

This information is maintained on the Store Data window of the Store Maintenance form in the Retail Merchandising System (RMS). The multi-level audit settings for individual stores are stored on the ds_store_data table. Stores are defined as multi-level audit stores when the system_code field is ‘MLA’and the imp_exp field is ‘I’ for a specific store. If these settings are not defined for a store, then ReSA defines the store as a single level audit store. Single level audit would be defined if the user chooses ‘Point Of Sale (POS)’ as an import for a given store. 

sa_system_options is not UPDATED from RESA UI but is POPULATED at time of INSTALLATION by running the SCRIPT sa_system_required.sql 

sa_system_options is not updated from RESA UI but is populated at time of installation by running the script sa_system_required.sql 

If a store employee is ASSIGNED a home store in the Employee Maintenance form, the Store Day Find form will display only records for that given store when Edit/View is selected from the action BOX. To view all the stores assigned to the user in RESA (the Employee Maintenance form), CLICK the REFRESH button and select the Assigned Stores radio button. 

If a store employee is assigned a home store in the Employee Maintenance form, the Store Day Find form will display only records for that given store when Edit/View is selected from the action box. To view all the stores assigned to the user in ReSA (the Employee Maintenance form), click the refresh button and select the Assigned Stores radio button.