1 Spend Transaction Configuration

This topic provides information on Spend Transaction Configuration.

Spend Module Transaction Flow:

Overview:

The system fetches spend transactions from the core system and saves them locally in the digx_sp_categorized_txns table. To activate the Spend module features, you need to set up the necessary OBRH entries. Please note that the Spend module is supported exclusively when using the OBRH adapter.

Data Capture Timing:

The Spend module collects and stores transaction data until the day before the current calendar day, which OBDX bases on the current date (i.e., one day prior to the OBDX system date). As a result, the Spend module will make transactions completed on the OBDX current date accessible the next day.

Fetch Criteria on User Login:

Every/Each time a retail user signs in, the system makes an asynchronous request to get spending data for the appropriate time frame.
  1. From Date: The user’s last login date.
  2. To Date: The OBDX current date minus one day.

This method guarantees that the system captures every transaction made from the user's last login until the day before the current OBDX date in the Spend module. As a result, users can see their latest spending activities up to the most recently processed day.

For a seamless Spend flow experience, ensure that:

  1. The correct OBRH entries for the Spend module are configured as per requirements.
  2. All entity-specific values (such as %ENTITY_ID%) are accurately updated before deployment.
  3. The OBRH adapter is tested and verified for integration with the Spend module in your environment.
    Insert into DIGX_FW_CONFIG_ALL_O (PROP_ID,PREFERENCE_NAME,PROP_VALUE,DETERMINANT_VALUE,CREATED_BY,CREATION_DATE,LAST_UPDATED_BY,LAST_UPDATED_DATE) values ('%ENTITY_ID%.com.ofss.digx.extxface.spendanalysis.adapter.transaction.ISpendUnCategorizedTransactionAdapter.getUncategorizedTransactions','ExtxfaceAdapterPreference','com.ofss.digx.extxface.spendanalysis.impl.SpendDDATransactionAdapter','01','ofssuser',sysdate,'ofssuser',sysdate);

Note:

Replace %ENTITY_ID% with the actual entity ID for your deployment.