--- title: "Customer management" type: OpenSpec status: Draft --- # Customer management ## Customer profile ### Requirement Definition 1. OLS administration screens include a “Customer Profile” function to view Customer details. 2. Customer records are view-only, and can only be updated from source systems by batch ==TBD=== ### Process Flow [Image Removed] ### Trigger * + - 1. User want to verify/ get customer’s information. ### Pre-Conditions 1. User have to have the access right on both “Customer Profile module under “Customer Mangement” Group. ### Wireframe * + - * 1. Summary listing page [Image Removed] * + - * 1. Filter [Image Removed] * + - * 1. Create/Edit mode 1. [Image Removed] * + - 1. Detail view [Image Removed] ### Business Rules 1. Click on Customer Profile icon in Main Menu to list customer records, as illustrated in the [wrireframe](#_Wireframe_13). 2. Use the filter to locate particular customer, which will be listed in the display. 3. Click on a row to view details of the customer record, as illustrated in the [wireframe](#_Wireframe_13). 4. Filter description: | | | | | | --- | --- | --- | --- | | **Index** | **Field** | **Description** | **Data type** | | **Filter** | | | | | | Quick search | As common function, OLS allows find customer record by quick search function. Put and press enter any key related to these field to find data. | | | | Gender / Giới tính | If Gender are provide then just get customer who have selected gender If gender are not provided then get all customer | Drop -down Allow multiple select | | | Country Origin /Quốc gia | If Country are provide then just get customer who have selected Country Issused If Country are not provided then get all customer | Drop -down Allow multiple select | | | Date of Birth/Ngày sinh | Find customer who have day of birth matched with selected date | Date Time picker | | | Card number/ Số thẻ | Find customer who have the account of inputed Card number | Text box | | | Account number/Số tài khoản | Find customer who have the inputed Account | Text box | 1. **Screen description** Screen description at create/edit mode | | | | | | --- | --- | --- | --- | | **Index** | **Field (EN/VN)** | **Description** | **Data type** | | **Step 1: Customer Profile / Hồ sơ khách hàng** | | | | | | CIF number \* / Số CIF | Unique CIF Number assingn to each customer. | X(30) | | | Frist Name \*/ Tên | Customer First Name | X(50) | | | Last Name \* / Họ | Customer last name Frist Name + Last Name will be customer Name which will be stored in database for refering | X(50) | | | Date of Birth\*/ Ngày sinh | Customer birth date | Date | | | Registration Date/ Ngày đăng kí | The date customer open an account | Date | | | Gender / Giới tính | Customer Gender | Drop-down Select one Lookup value from Code\_Management table where code type is “gender”. Refer to “get-type-by-code”API under Master data | | | Customer Status \*/Trạng thái khách hàng | Customer status | Drop-down Select one Lookup value from Code\_Management table where code type is “customer-status”. Refer to “get-type-by-code”API under Master data | | | Customer Block Code | Customer block code | X(10) | | | Marital Status/ Tình trạng hôn nhân | Customer marital ima status | Drop-down Select one Lookup value from Code\_Management table where code type is “marital-status”. Refer to “get-type-by-code”API under Master data | | | ID Type/ Loại ID | ID Type of cardholder ID | Drop-down Select one Lookup value from Code\_Management table where code type is “cardholder-idtype”. Refer to “get-type-by-code”API under Master data | | | Cardholder ID/ Số ID | Cardholder ID Condition field. This field is required when Cardholder type is selected otherwise this will be optional field. | X(30) | | | Country Origin/ Quốc gia | Customer country orgin | Drop-down Select one Lookup value from “Country” table. Refer “Country Code” API under Code Maintenance | | | Customer Income/Thu nhập | Customer income | 9(14,2) Should be greater than or equal to 0 if provided | | | Datetime of maitenance date/ Ngày cập nhật thông tin | The sysdate to create/update record via OA screen. The maintenance date from request if input via batch job | Datetime The date format must adhere to the configured format Display for view mode only | | | Profile Picture /Ảnh hồ sơ | Drag or drop photo Or Browse file to upload image file | | | **Step 2: Contact Detail/ Thông tin liên hệ** At least one contact detail record should be provided Each customer can have more than one contact detail information such as customer contact and guardian contact…. | | | | | | Addess Type\*/ Loại địa chỉ | Adress type A drop-down list to select one of following address: Home Address Business Address Shipping Address Billing Address | Drop-down Select one Address type should be unique on each customer | | | Phone number\*/ Số điện thoại | Phone number | X(30) | | | Email Address\*/ Địa chỉ Email | Email Adress This field must be under email format | X(50) | | | Address 1/ Địa chỉ 1 | The main address | X(100) | | | Address 2/ Địa chỉ 2 | Other address | X(100) | | | State/Tỉnh-Khu vực | State | Drop-down Select one Lookup value from “State\_Code” table Refer to “State code” API under Code maintenance | | | City/ Thành phố | City | Drop-down Select one Lookup value from “City\_Code” table Refer to “City code” API under Code maintenance | | | Zip Code/ Mã bưu điện | Zip code/postal code | Drop-down Select one Lookup value from “ZIP\_CODE” table Refer to “Zip Code” API under Code Maintenance | * 1. **Processing** + If a request is adding a record which whose CIF # locates an existing Client record in OLS with record Status = “A”, the incoming record will be rejected. + If a request is updating or deleting a CIF # that does not locate an existing Client record with record Status = “A” in OLS, the request will be rejected. + If a request is deleting a CIF# that locates a Client record that is linked to one or more Account that is still active in OLS, the request will be rejected. + When new customer is added in OLS then: + Customer record is added in both Client and Client\_corr table. + The corresponding LOYALTY\_ACCOUNT is created. * + - When customer is deleted then: + Logically delete the record by moving it to History table. + Locate record in LOYALTY\_ACCOUNT and move that to History table. * + - Records added thru this screen cannot be updated by records from the OLS batch. Record created/updated by OLSCUST batch cannot be CHANGED from the admin screen. This implicit check can be disabled through a parameter in App Param. 1. **View mode of active record is display as customer 360 which is described** **in section 5.2.** ### Post-Conditions * + - * 1. Able to access submodule in customer management module which will be described more detail as following section. ### Exception Flow N/A ## Customer 360 ### Requirement Definition 1. OLS administration screens include a “Customer 360” function to view Customer details. 2. Customer 360 contains key information about customer. User can use it as a strategy guide to creating personalized experiences. ### Process Flow N/A ### Trigger N/A ### Pre-Conditions 1. User need to have the access right in Customer Profile module in order to able to view this dashboard. 2. User must select a customer in customer profile listing page to bring up the customer dasboard. ### Wireframe [Image Removed] [Image Removed] ### Business Rules 1. Clicking on the chart icon at the top of the main Customer list page will toggle between the Customer list view and the Customer dashboard view. 2. Customer dashboard update constantly, giving user a real-time view of customer behavior and information. 3. Click any customer record in listing page to see the customer profile of each customer. 4. **OLS support following information:** #### Customer information [Image Removed] * + 1. Click “See profile details” to see customer profile detail. The system bring up the screen as pop-up screen for customer profile as illustrated as following: [Image Removed] 1. User can edit/delete customer from this screen. #### Customer’s rewards statistic [Image Removed] * + 1. This part displays statistical indicators related to the customer's rewards. OLS introduces 2 indicators: + Points: The customer’s total available points. Use sysdate to determine the balance bucket periods. + Cash back: The customer’s total available cash back. Use sysdate to determine the balance bucket periods. #### Account / Card information * + 1. The Customer’s account holdings and all of the customer’s card are displayed, regardless of whether account or card number is used. 2. **The Account/ Card information listing give user have a general overview of customer’s cards:** **+ A = Set of card list of all account in the selected customer** **+ B= Set of card lists for the specifically selected customer.** **Therefore C= Card in listing page = Distinct cards from the union of A and B** * + 1. **In case account there is no card is added then just show the account list of selected customer.** 2. Quick shortcut to support adding new Card or new Account from this screen. 3. Detail listing description: | | | | | | --- | --- | --- | --- | | **Seq** | **Filed** | **Description** | **Data type** | | **Layout** [Image Removed] | | | | | | Account type\*/Loại tài khoản | The combination of Product Account Level and Prodcut Account Type of customer. All Customer’s account holding are displayed here. | Display | | | Account Number\* /Số tài khoản | Product Account No. | Link Click on each Account number to bring up the Account Detail screen to see more about this account. See more on [Account](#_Account) section | | | Card Number/Số thẻ | Card number | Link Click on each Card number to bring up the Card Detail screen to see more about this card. See more on [Card](#_Card) section. | | | CIF Number\*/Số CIF | CIF number of card will be the same as selected CIF number for Principal card For supplement card then this is CIF number of Card instead CIF Number of Account. | Display | | | Card Status/Trạng thái thẻ | Card status | Display Lookup value from Card table | | | Card indicator/Chỉ thị thẻ | Card indicator | Display Lookup value from Card table | | | Card block code/Mã chặn tài khoản | Card block code | Display Lookup value from Card table | | | Card expiry date/Ngày hết hạn thẻ | Card expiry date | Display Lookup value from Card table | | | Account block code/Mã chặn tài khoản | Account block code | Display Lookup value from Product\_Account table | | | Account status\*/Trạng thái tài khoản | Account status | Display Lookup value from Product\_Account table | | | Account Open Date\*/Ngày mở tài khoản | Account Open Date | Display Lookup value from Product\_Account table | #### Transaciton statistic A combination of two charts is used to describe the transaction statistic for selected period of a customer. The line chart describes the fluctuations in a customer's balance for the selected pool over a specified period. The combo chart illustrates the relationship between the total number of transactions and the total number of transacted merchants for the selected pool over a specified period. Screen description | | | | | | --- | --- | --- | --- | | **Index** | **Field** | **Description** | | | **Filter** [Image Removed] | | | | | | Period | This is drop-down filter key Madatory and select one only OLS support following periods: * + 1. This month 2. Last month 3. Last 3 months 4. Last 6 months Default as “This month” This filter is apply for both graph | | | | Pool | Mandatory field Allow multiple select Lookup value from Pool Defintion Display Pool ID and Pool Name per each pool. This filter is applied for left graph only | | | | Account type | Drop-down list to select combination of PAT and PAL. Allow multiple select. This filter is applied for right graph only | | | | MCC | Drop-down list to select MCC of the transaction. Allow multiple select Display code and description per each MCC This filter is applied for right graph only | | | **Line chart** **Layout** [Image Removed] [Image Removed] | | | | | | Vertical axis | Total point each selected period/ selected pool Each line is assinged for one transaction type. | | | | Horizontal axis | Condition data. If Period “This month” or “Last Month” is selected then horizontal axis is including all day of the month. Total point will be daily total point. If Period “Last 3 months” is selected then horizontal axis is including last 3 month from currenlty month. Total points will be monthly total points. If Period “Last 6 months” is selected then horizontal axis is including last 6 months from currenlty month. Total points will be monthly total points. Hover over the line graph to view a count of redemmed points/earned points/ adjusted points for the date range/time frame defined. | | | **Data source** | | | | | Get data from the TRANSACTION table with transaction type = “Award” for earned points/Transaction type = “Redeem” for redeemed points / Transaction type =’ Adjust” for Adjusted points during each selected month on the selected pool. The transaction should not be a cancellation transaction. Use the transaction date to determine the period. | | | | | **Combo chart** Layout [Image Removed] [Image Removed] | | | | | | Left vertical axis | | Total number of transacted merchants during selected period of selected pool Use Bar chart to describe total number per each period | | | Right vertical axis | | Total number of transaction during selected period of selected pool Use line chart to describe total number per each period | | | Horizontal axis | | Condition data. If Period “This month” or “Last Month” is selected then horizontal axis is including all day of the month. If Period “Last 3 months” is selected then horizontal axis is including last 3 month from currenlty month. Total points will be monthly total points. Hover over the line graph to view a count of transaction for the each day/month Hover over the bar graph to view a count of transacted merchant for the each day/month | | **Data source** | | | | | | Lookup value from TRANSACTIONS table Use transaction date to determine period Use Store data as merchant to determine transacted merchant Each OLS Reference No should be one and only transaction. | | | #### Customer Activities * + - * 1. The all customer activites will be triggerd and displayed here. 2. Some types of customer activities as following: 1. Loyalty program All OLS transaction of customer such as: * + - Enrolling in and participating in OLS loyalty programs. - Redeeming points - Transfer points - Earn points 1. Feedback and Review + Leaving customer’s feedback on the portal app. 2. Email engagement + Receive email from OMR 3. Account management Refering to all bellow action in portal app such as: * + - Updating customer information, such as contact details, payment methods, and preferences. - Password resets and login activity. 1. Allow user filter data by time frame (Start date and End date). 2. Layout [Image Removed] #### Customer Segmentation * + - 1. Deviding the customer base into segmentation groups based on specific characteristics, behaviors and demographics. 2. Introduce the criteritions on each segmentation group and the conditons to meet each criterion. Based on this, OLS introduce a program to collect data and devide customers into each segment. 3. Demographic segmentation includes following segment: 1. Gender: Famale or Male 2. Age: Teenager / Adult/ Middle- Aged person/ Senior Citizens: Based on criteria (Age’s range) to devide customer’s age. 3. Matirial Status: Single or Married 4. Income: Low / Medium / High: Based on criteria (customer’s income range) to devide icom segment. 5. Layout [Image Removed] 1. Behaviors segmentation includes following segment: 1. Frequency of purchase: Daily / Weekly/Montly..: Based on the frequency of the transaction to devide this segment. 2. Membership class: Depending on the organization, business. Some common types of membership class: * Basic membership * Premium membership * Platium membership * Gold membership * Daimon membership * VIP membership 3. Purchase channel: Categorizing customers based on customer’s preferred purchase channels, such as in-store, online, mobile app, or phone (Call to call center)… 4. Hobby: Based on customer’s hobby to create siutable loyatly program. 6. Layout [Image Removed] #### Most Redemmed Items The top 10 (this value should be configurable value) redeemed items of the customer are displayed here. Just show top 5 item on each page. Each row contains a summary for an item, including the item code, the total redeemed quantity, and the redeemed points/cash amount to use for the specificed period. Shortcut to support quick add new item redemption transaction from this screen. Listing page description: | | | | | | --- | --- | --- | --- | | **Seq** | **Field** | **Descriptions** | **Data type** | | **Layout** [Image Removed] | | | | | F**ilter** | | | | | | Period | Period used to filter data. | This is drop-down filter key Mandatory and select one only OLS support following periods: * + 1. Today 2. This month 3. Last month 4. Last 3 motnhs Default as “To day” | | | Item type | Optional field The drop-down to select item type to get top N item. If item type is not provided then top N of all item type will be displayed. | Drop down Multiple select Default Evoucher type | | **Listing page** | | | | | | Item code/Mã vật phẩm | Item code | Display Lookup value from CAT\_CATALOGUE\_TRANS\_DETAIL table | | | Item Name/Tên vật phẩm | Item Name | Display Lookup value from ITEM table | | | Category/ | The categories are assigned to item | Display Lookup value from Item table Each item can be assinged more than one category | | | Quantiy/Số lượng | Total redemmed quantity of selected customer for top item on selected period | Display as number format Lookup value from CAT\_CATALOGUE\_TRANS\_DETAIL table | | | Redemmed points/ Điểm đã sử dụng | Total redemmed point of selected customer for top item on selected period | Display as number format Lookup value from CAT\_CATALOGUE\_TRANS\_DETAIL table | | | Cash Amount used/Tiền đã sử dụng | Cash used to redeem | Display as number format Lookup value from CAT\_CATALOGUE\_TRANS\_DETAIL table | | **Data source** | | | | | | Lookup value from CAT\_CATALOGUE\_TRANS\_DETAIL table Use Post\_Date to determine period Order by quantity descending order. | | | #### Balance information 1. The all customer’s pool balances are displayed here. 2. Each row contains the summary for a Pool: the total balance (sum of all buckets in a Pool), redeemable balance and the expiry date of the earliest expiring bucket. 3. Listing page descriptions | | | | | | --- | --- | --- | --- | | **Seq** | **Field (EN/VN)** | **Descriptions** | **Data type** | | Layout [Image Removed] | | | | | **Fitler** | | | | | | Pool | Optional field A drop-down to select the reward pools, which quickly retrieves the customer's balance. If Pool is provided then the system display all balance of the selected pool of the customer. If pool is not provided then all pool balance of the customer are displayed. | Drop –down Default as empty Multiple select Lookup from pool definition screen Display only the pools with a non-zero balance. | | **Listing page** | | | | | | Pool ID/Mã pool | Pool ID | Link Click on the pool id to bring up the “[Pool Balance Enquiry](#_Balance_Detail_Enquiry) ” detail view of this pool. | | | Pool Name/Tên pool | Pool Name | Display Lookup value from Pool Definition | | | Balance/Số dư | Sum all balance buckets of a pool of customer. | Display as number format Lookup value from LAB table | | | Redeemable Balance/ Số dư khả dụng | The sum all non-balance buckets of a pool of customer. The bucket should have: Start date <= Processing date <= Expiry date | Display as number format Lookup value from LAB table | | | Earliest Exp Bal and Date/ Số dư gần nhất | The earliest expiring bucket date for a pool, for non-0 balance buckets. And Balance that is expiring on The earliest expiring bucket date. The balanace should not be zero balance. | Display as number format Lookup value from LAB table | ### Post – condition * + 1. User can use it as a strategy guide to creating personalized experiences.. ### Exception Flow N/A ## Account ### Requirement Definition Account tab show all customer’s holding account. Account information means anything relating to customer’s holding acccount which sent from external system to OLS or Added by user via OLS system. ### Process Flow [Image Removed] ### Trigger N/A ### Pre-Conditions 1. Users have to have access rights in both “Customer Profile” and “Account” modules under “Customer Mangement” Group in order to able to view this screen. 2. User must select a customer in customer profile listing page to access the “Account” tab. 3. An account type must be available in the OLS system before adding any account of that type. ### Wireframe Summary listing page [Image Removed] Figure 1: Listing page [Image Removed] Figure 2: Filter Add/Edit mode [Image Removed] [Image Removed] Detail view * 1. Record detail [Image Removed] * 1. Record status and history [Image Removed] ### Business Rules Account records are updated in the external system and then loaded into OLS. Account records can be added by adding functions in administration screens. Click on the Account tab in the Customer profile screen to bring up the Account listing as illustrated in the [wireframe](#_Wireframe_4). Use the filter to locate a particular Account, which will be listed in the display. Click on a row to view details of the Account record, as illustrated in the [wareframe](#_Wireframe_4). Screen description | | | | | | | | --- | --- | --- | --- | --- | --- | | **Seq** | **Field (EN/VN)** | **Description** | | | **Data type** | | | CIF numnber\* / Số CIF) | CIF number of selected customer | | | Display | | | Product Account Level (PAL) \* /Hạng tài khoản | Product Account Level of Account | | | Drop-down Lookup value from PRODUCT\_ACCOUNT\_LEVEL table Refer to “ Product Account Level” API under “Code Maintenance” | | 2. | Product Account Type (PAT)\* /Loại tài khoản | Product account type which belongs to selected PAL that assigned to Account Combination PAL and PAT as Account Type of Account | | | Drop-down Lookup value from PRODUCT\_ACCOUNT\_TYPE table where PAL as selected PAL Refer “ Product Account Type” API under “Code Maintenance” | | 3 | Account Number\*/ Số tài khoản | Product Account Number | | | X(20) Combination Account Type + Account Number should be unique. An Combination Account No + Account Type is assigned to an ASN. ASN is unique in the OLS system | | | Account Open Date \*/Ngày mở tài khoản | Product Account Open Date | | | Date The date format must adhere to the configured format | | | Account Indicator\*/ Chỉ thị tài khoản | P- Personal account C- Corporate Account | | | Drop-down Select one Lookup value from “Code Management” table where type code is “Acct-indicator”. Refer “List-by-code-type” API under Master Data. | | | Account block code/ Mã chặn tài khoản | The account block code is used to check block transaction via TP or on some MQ validation | | | X(10) | | | Block code reason / Mã lí do chặn tài khoản | Reason to block account | | | X(100) | | | Block code last update date/ Ngày chặn cuối cùng | The day to block account | | | Date The date format must adhere to the configured format | | | Cycle / Ngày sao kê | Statement cycle date | | | 9(02) Should be greater than 0 if provided | | | Account status\*/ Trạng thái tài khoản | Product account status The Account status is used to check block transaction via TP or on some MQ validation | | | Drop-down Select one Lookup value from “Account Status” screen (Account\_status table). Refer “Account status” API under Code Maintenance | | **Card information/Thông tin thẻ** When click to view any active account then this pannel is display to show the card of cards belong to selected account. The pannel includes following information: | | | | | | | | Card number / Số Thẻ | | Card Number | Display Lookup value from Card\_Product\_Account\_Rel table where account is selected account. Refer “Card” API under Customer Management | | | | Card status/ Trạng thái thẻ | | Card Status Display both code and description of status | Lookup value from Card table by Card Number Lookup description from Code\_Management table by code type is “card-status”. Refer “Card” API and “get-by-code-type” API | | | | Card Indicator/Chỉ thị thẻ | | Card indicator Display both Code and description of indicator | Display Lookup value from Card table by Card Number Lookup description from Code\_Management table by code type is “card-indicator”. Refer “Card” API and “get-by-code-type” API | | | | Card Creation Date/ Ngày tạo thẻ | | Creation Date of Card | Display date format The date format must adhere to the configured format. Lookup value from Card table by Card Number Refer “Card” API under Customer Management | | | | Card Expiry Date /Ngày hết hạn | | Expiring date of Card | Display date format The date format must adhere to the configured format. Lookup value from Card table by Card Number Refer “Card” API under Customer Management | | | | CIF number/ Số CIF | | CIF number of Card | Display Lookup value from Card table by Card Number Refer “Card” API under Customer Management | | | | Card block code/Mã chặn thẻ | | Card block code | Display Lookup value from Card table by Card Number Refer “Card” API under Customer Management | | Each account is belong to only one Customer. OLS don’t support to change CIF number of account in this screen. If have to change CIF number of the account then it should be processed via CIF Merge batch if needed. Records added thru this screen cannot be updated by records from the OLSACCT batch. Record created/updated by OLSACCT batch cannot be CHANGED from the admin screen. This implicit check can be disabled through a parameter in App Param. When an account is added then: * If locate any exiting record with the same combination Account No+ Account Type in OLS (record status is “A”) then the record is rejected. * If not then: + - Account record is added in PRODUCT\_ACCOUNT table. - The corresponding LOYALTY\_ACCOUNT\_PRODUCT is created When an account is modified then : * If there is no combination Account No+ Account Type is found in OLS then the record is rejected. * If found the same combination Account No+ Account Type existing record in OLS then update Product Account fields with the incoming field values accordingly. The original record is moved to his table after record is approved. * Upgrade Account case :==tbd=== When account is deleted then: * If there is no combination Account No+ Account Type is found in OLS then the record is rejected * If locates a Product Account record that has a Card record with record Status “A” linked to it, the incoming delete action is rejected. * If found the same combination Account No+ Account Type existing record in OLS then move record into history table. The corresponding LOYALTY\_ACCOUNT\_PRODUCT is moved to his table as well. ### Post – Codition * 1. Allow to add Card. 2. Allow to post transaction with new account. ### Exception Flow * + 1. Input data are not passed all validations and then user choose cancel the action then use case ends in failure. ## Card ### Requirement Definition Card tab show all customer’s card. Card information means anything relating to customer’s card which sent from external system to OLS or added by users on the OLS system. ### Process Flow [Image Removed] ### Trigger N/A ### Pre-Conditions 1. User have to have access rights in both “Customer Profile” and “Card” modules under “Customer Mangement” Group to able to view this screen. 2. User must select a customer in customer profile listing page to access the “Card” tab. 3. An account must be available in the OLS system before adding any card of that account. ### Wireframe Summary listing page [Image Removed] Figure 1: Listing page [Image Removed] Create/Edit view [Image Removed] [Image Removed] Detail record view * 1. Record detail [Image Removed] * 1. Record status and history [Image Removed] ### Business Rules Card records are updated in external system and then loaded into OLS, so OLS only provides view functions in administration screens for Card records. There is no further actions. Click on Card tab in Customer profile screen to brings up the Card listing as illustrated in the [wareframe](#_Wireframe_5). Use the filter to locate particular Card, which will be listed in the display. Click on a row to view details of the Card record, as illustrated in the [wareframe](#_Wireframe_5). Create/Edit screen description | | | | | | --- | --- | --- | --- | | **Seq** | **Field (EN/VN)** | **Description** | **Data type** | | | CIF number \*/Số CIF | CIF Number of Card | Drop-down Get data from Client table Default as CIF Number of selected customer but user can modify if Supplement Card is added. Support quick search CIF number by enterd al least 4 digits of CIF number. | | | Account Type\*/ Loại tài khoản | Combination of Product Account Level and product account type PAT : Visa [001] PAL: Debit [830] Account type : 830-001 | Drop-down Lookup value from PRODUCT\_ACCOUNT table where Account Type is Account type of select customer (Use CIF number which is selected from listing page). Refer to “Product account” API under “Customer Management”. | | | Account number \*/ Số tài khoản | Product Account number | Drop-down All account of selected account type of selected customer. Refer to “Product account” API under “Customer Management” | | 3 | Card number\* /Số thẻ | Card number | X(20) Must be unique value in whole system. | | | Masked Card Number/ ==tbd== | Masked Card Number | X(20) | | | Cardholder Name\*/ Tên chủ thẻ | Cardholder Name | X(50) | | | Card Indicator\*/ Chỉ thị thẻ | Card indicator: S- Supplement Card P – Principal Card K – Corporate Card …. For principal card then CIF of card must be the same as CIF of Account. | Drop-down Select one Lookup value from “Code management” table where type code is “card-indicator”. Refer “list-by-code-type” API under “Master Data”. | | | Card status \*/Trạng thái thẻ | Card status The Card status is used to check block transaction via TP or on some MQ validation | Drop-down Lookup value from “Card Status” screen (Card\_status table). Refer “Card status” API under Code Maintenance | | | Card block code/Mã chặn thẻ | Card block code The Card block code is used to check block transaction via TP or on some MQ validation | X(10) | | | Card activation date /Ngày kích hoạt thẻ | Card activation date | Date | | | Card creation date\*/ Ngày mở thẻ | Card creation date | Date | | | Card expiry date \*/ Ngày thẻ hết hạn | Card expiry date | Date | | | Old Card Number/ Số thẻ cũ. | Old Card Number | Drop-down list Card belong to selected account. In BAU processing, this is the existing card number to be replaced by new Card Number in this record. This field should have a value only if this record is ADDING a NEW CARD NUMBER which is to replace the OLD CARD NUMBER. Both new card and old card should under the same account. | | | ==tbd== | | | 1. Records added thru this screen cannot be updated by records from the OLSCARD batch. Record created/updated by OLSCARD batch cannot be CHANGED from the admin screen. This implicit check can be disabled through a parameter in App Param. 2. When a record is adding with whose Card Number already exists in OLS, the record will be rejected. 3. When a record is adding/updating with whose Account does not exists in OLS, the record will be rejected. 4. When a record is adding/updating with whose CIF Number does not exists in OLS, the record will be rejected. 5. **Processing** * Each Card is belong to only one Account and only one customer. OLS don’t support to change CIF number Or Account of Card in this screen. If have to change CIF Numnber of card or account of card then it should be processed via CIF Merge batch if needed. * When a record is adding with inputed data passed the card record validation then: + - The card record is added in CARD table. - The linked record to the Account through CARD\_PRODUCT\_ACCOUNT\_REL table is added as well. * When a record is updated whose Card Number passes the validations then the Card record and the Card–Account relationship record are updated. Original record is moved to his table. * When a Card is deleted then the Card record is moved to history table to indicate a logical delete. The corresponding CARD\_PRODUCT\_ACCOUNT\_REL record for this card is also moved to history table. * For principal card CIF number of account should be the same CIF number of card. * For replacement case: A new Card issued to the Cardmember in case of loss, theft, mutilation or non-receipt of a Card. Therefore new card is coming to replace old card. When replace card then: + - Add the incoming record as a new Card record with the same PSN as old card number. - The linked record to the Account through CARD\_PRODUCT\_ACCOUNT\_REL table is added as well. - Old Card Number will continue to be processed until the Card Status and/or Block Code is/are updated to make the card ineligible. - All Attributes, Counters and Pool Buckets which were linked to the old Card number will be automatically linked to the new Card record. 1. Card listing will be the list card of all account of selected customer. ### Post – Codition N/A ### Exception Flow * + 1. Input data are not passed all validations and then user choose cancel the action then use case ends in failure. ## Pool Balance Detail ### Requirement Definition OLS will support Pool balance enquiry as a tab on Customer Profile Screen. Pool Balance tab to list a summary of all Pools of the customer. ### Process Flow [Image Removed] ### Trigger User would like to check balance detail of customer. ### Pre-Conditions 1. User have to have access rights in both “Customer Profile” and “Balance Enquiry” modules under “Customer Mangement” Group to able to view this screen. 2. User must select a customer in customer profile listing page to access the “Pool Balance Detail” feature. ### Wireframe Summary listing page * + 1. Listing page [Image Removed] * + 1. Filter [Image Removed] 1. Detail view * 1. Detail view per each pool [Image Removed] * + 1. Click on each row in Pool Balance View to brings up the pop-op detail view [Image Removed] ### Business Rules * 1. Click on Pool Balance tab to list a summary of all Pools of the customer. 2. All summary of pool balance display in listing page. 3. This screen just display only. There is no Add/Mofify action on this screen. 4. Each row contains the summary for a Pool: the total non-balance (sum of all buckets in a Pool), and redeemable balance and the expiry date of the earliest expiring bucket. 5. Use the filter to locate particular pool balance detail record, which will be listed in the display. 6. Click on any record to bring up the breakdown of the Pool in that row on the “Pool Balance Detail” Screen as illustrated in the [Wireframe](#_Wireframe_2). 7. User stories and acceptance criteria [Image Removed] * 1. Pool Balance Detail screen descriptions | | | | | | --- | --- | --- | --- | | **Seq** | **Field (EN/VN)** | **Descriptions** | **Data type** | | **Pool Balance /Số dư pool** | | | | | | Pool ID / Mã pool | Pool ID | Display | | | Pool Name/ Tên pool | Pool Name | Display Lookup value from Pool Definition | | | Pool type/ Loại pool | Pool Type | Display Lookup value from Pool Definition | | | Pool Entity level / Cấp thực thể pool | Pool Entity level | Display Lookup value from Pool Definition and master data table | | | Balance / Số dư | Sum all balance buckets of selected pool | Display as number format Lookup value from LAB table | | | Redeemable Balance/ Số dư khả dụng | The sum all non-balance buckets of selected pool The balance bucket must be non-expired and available to use. | Display as number format Lookup value from LAB table | | | Next Expiring Balance/ Số dư hết hạn gần nhất | The earliest non-expiring balance bucket of the selected pool. | Display as number format Lookup value from LAB table | | **Pool Balance View/ Chi tiết số dư pool** The breakdown of the Pool in that row following: [Image Removed] 1. Each row is a bucket containing the remaining points earned by the Account/Card shown, and expiring on the date shown. Expired buckets but haven’t yet forfeited will be shown as well. 2. If Customer pool level then all Pools buckets of the customer are shown under each speparaty account even it is customer entity-level. 3. If Account pool level then all only the Pool buckets earned by the presented Account will be shown. 4. If Card pool level then only the Pool buckets earned by the presented card will be shown. | | | | | | Account type/ Loại tài khoản | Combination of Product Account Type and Product Account level of Account | Display Lookup from Product\_Account table Lookup from Product\_Account number by ASN from LAB table. | | | Account No/ Số tài khoản | Product Account Number | Display Lookup from Product\_Account number by ASN from LAB table. | | | Card Number/ Số thẻ | Card number | Present for Card pool entity level only | | | Pool ID/ Mã pool | Pool ID | Selected pool | | | Balance / Số dư | Non zero balance | Display Loopkup value from LAB table. Group by Expiry date / LA/ASN/CSN/Pool ID | | | Expiry Date/ Ngày hết hạn | Expring date | Display Loopkup value from LAB table | ### Post – Codition N/A ### Exception Flow N/A ## Transaction History ### Requirement Definition * + - 1. Transaction History is a tab under Customer profile. 2. A transaction history is a running record of all of the transactions logged in OLS including cancellation transactions. 3. Noted that: Transaciton hisstory listing depened on housekeep parameter. Nomarly It will show all transaction on the last 12 months. ### Process Flow [Image Removed] ### Trigger User would like to check transaction history of customer. ### Pre-Conditions 1. User have to have access rights in both “Customer Profile” and “Transaction History” modules under “Customer Mangement” Group in order to view this screen. 2. User must select a customer in customer profile listing page to access the “Transaction History” tab. ### Wireframe * + - * 1. Summary listing page [Image Removed] * + 1. Detail record 1. Transaction Detail [Image Removed] * 1. Record status [Image Removed] 1. Right panels * + Quick view desribes expand information for this transaction. + Click on each item to bring up the according tab + Support scrollbar for pop-up detail view. 1. Reward details [Image Removed] * 1. Item Redemption Transaction Details [Image Removed] * 1. Counter Transaction Details [Image Removed] ### Business Rules * 1. Click on Transaciton History tab to list all transaction of the customer as illustrated in the [wireframe](#_Wireframe_3). 2. One transaction detail record is combination of all input field (assinged to an OLS Reference No). 3. Transaction history listing all transaction in OLS of customer include cancellation transactions. 4. This screen just view only. There is no futher action. 5. Use the filter to locate particular transactions, which will be listed in the display. 6. Click a listed record to display the details of the transaction as illustrated in the following: | | | | | | --- | --- | --- | --- | | **Index** | **Field (EN/VN)** | **Description** | **Data type** | | **Account Detail/Chi tiết tài khoản** | | | | | | Account Number/ Số tài khoản | Transacting Product Account Number | Display Lookup value from TRANSACTIONS table | | | Product Account Type/ Loại tài khoản | Transacting Product Account Type | Display Lookup value from TRANSACTIONS table | | | Product Account Level/Hạng tài khoản | Transacting Product Account Level | Display Lookup value from TRANSACTIONS table | | | Card Number/ Số thẻ | Transacting Card Number | Display Lookup value from TRANSACTIONS table | | **Transaction Detail/ Chi tiết giao dịch** | | | | | | Invoice No/ Số hóa đơn | Internal invoice No generated by OLS system. | Unique for each transaction Display only Lookup value from TRANSACTIONS table | | | Reference No/Số tham chiếu giao dịch | OLS Transaction Reference Number | Unique for each transaction Display only Lookup value from TRANSACTIONS table | | | Source Reference Number | Reference number from source system For refrence only | Display | | | OLS Transaction Code | OLS Transaction Code | Display Lookup value from TRANSACTIONS table | | | Gross Amount/ Giá trị giao dịch gộp | Gross transaction amount | | | | Nett Amount/Giá trị giao dịch ròng | Nett transaction Amount | | | | Redeem points/Điểm đổi thưởng | Redeem points Total redeem points of the choosen transaction. The total point shoule equal to total redeem points on each campaign rule which will be display on quick view. | Display Lookup value from TRANSACTIONS table | | | Points Redeemed Amount/ Giá trị điểm đổi thưởng | Redemmed point Amount Total redeem point amount of the choosen transaction. The total point shoule equal to total redeem point amount on each campaign rule which will be display on quick view. | | | | Adjust Points/ Điểm điều chỉnh | Adjustment point Total adjustment points of the choosen transaction. The total point shoule equal to total adjust points on each campaign rule which will be display on quick view. | Display Lookup value from TRANSACTIONS table | | | Points Adjustment Amount/ Giá trị điểm điều chỉnh | Adjustment points amount Total adjust point amount of the choosen transaction. The total point shoule equal to total adjust point amount on each campaign rule which will be display on quick view. | | | | Award Points/ Điểm thưởng | Earned points Total award points of the choosen transaction. The total point shoule equal to total award points on each campaign rule which will be display on quick view | Display Lookup value from TRANSACTION table | | | Points Awarded Amount/Giá trị điểm thưởng | Earned points amount Total award point amount of the choosen transaction. The total point shoule equal to total award point amount on each campaign rule which will be display on quick view. | | | Transaction Date/Ngày giao dịch | Transaction Date Time | | | Post Date/ Ngày đăng | Post Date | | | Settlement Date/ Ngày ghi sổ | Settlement Date | | | Cancellation Indicator/Chỉ thị hủy | Cancellation Indicator | | | MCC | Transaction MCC Code | | | Store/ Cửa hàng-đơn vị | Transaction Store ID | | | Terminal / Cấp thiết bị đầu cuối | Transaction Terminal ID | | | Transaction Description/Mô tả giao dịch | Transaction Description in OLS or Shop Name from external source system. | | | Currency Code/ Mã tiền tệ | Currency code of the original transaction amount | | | Country Code /Mã quốc gia | Country code of the original transaction. | | | Transaction Mode/ Phương thức giao dịch | Mode of transaction at point of payment | | | Transaction Channel /Kênh giao dịch | Transaction channel | | | Salary Credit/ Chỉ báo tiền lương | Indicates bundled deposit account is receiving regular salary credits | | | POS Entry Mode/ =tbd= | POS Entry Mode | | | Reason Code/ Mã lí do | Adjustment reason code | For Adjustment transaction | 1. Quick view in right panel displays the award, redeem, adjust and counter update details of the transaction including the campaign rules applied to the transaction and the Pool Units earned and redeemed. Click on each item to bring up the according tab. 1. Award/Redeem/Adjust detail: Total balance in right panel should be equal to blanace which is displayed in transaction detail. This quick view displays the reward details of the transaction. | | | | | --- | --- | --- | | **Seq** | **Field (EN/VN)** | **Descriptions** | | | Campaign Rule / Quy tắc chiến dịch | Campaign rule that transaction has been triggered This value may be empty if transaction does not trigger campaign rule | | | Transaction Type/ Loại giao dịch | Transaction Type | | | OLS Transaction Code/Mã giao dịch OLS | OLS Transaction Code | | | Pool/ Pool | Reward Pool | | | Pool Unit/ Đơn vị Pool | Award/Redeem/Adjust points Depended on transaction type | | | Pool Unit Amount / Giá trị đơn vị Pool | Award/Redeem/Adjust points amount Depended on transaction type | * 1. Counter Transaction Detail: + This part displays the counter value, which is updated by the transaction on each campaign rule. | | | | | --- | --- | --- | | **Seq** | **Field (EN/VN)** | **Descriptions** | | | Campaign Rule / Mã quy tắc | Campaign rule that transaction has been triggered | | | Counter / Bộ đếm | The counter for that transaction has been updated | | | Entity / Cấp thực thể | Entity level of counter | | | Counter Value/Giá trị bộ đếm | Counter Value | | | Bucket Number/ Bộ đếm số | Counter bucket number which one is updated by this transaction. | | | Bucket Start Date/ Ngày bộ đếm bắt đầu | The start date of the counter bucket for the updated counter has been changed | | | Bucket End Date /Ngày bộ đếm kết thúc | The end date of the counter bucket for the updated counter has been changed | * 1. Item Redemption Transaction Detail + This quick view displays the item redemption details of the transaction. | | | | | --- | --- | --- | | **Seq** | **Field (EN/VN)** | **Descriptions** | | | Item / Mã vật phẩm | Item | | | Descriptions/ Mô tả | Remark of the redemption transaction | | | Redemmed quantity / Số lượng đổi thưởng | Redemmed quantity | | | Redeemed points/ Điểm đổi thưởng | Redeemed points | | | Cash Amount used/Số tiền đã dùng | Cash amount is used to redeem item. | ### Post – Codition N/A ### Exception Flow N/A ## No Hit CP – Transaction –IF “RULE EVALUATION” IMPLEMENTED THEN THIS SCREEN IS REDUNDANT ### Requirement Definition * + - 1. In the nearest version, there is no screen to be tracking the transaction which did not trigger campaign rule by some reasons. 2. In this version, we introduce a new screen under the 'Customer Management' module to track all non-eligible transactions (those that did not meet the rule criteria) or transactions with no linked rules 3. A 'No-Hit Transaction' is a running record of all transactions sent to OLS to trigger a CP rule but not eligible for a campaign rule or incoming transactions with no linked campaign rule. If an incoming transaction hits Rule A but does not hit Rule B, this transaction will still appear on this screen for Rule B 4. Noted that: Listing is depending on housekeep parameter. Nomarly It will show all transaction on the last 12 months. ### Process Flow [Image Removed] ### Trigger * + - * 1. User would like to verfiy why transaction did not hit campaign rules. ### Pre-Conditions Incoming transactions trigger campaign but do not hit CP. User have to have access rights in both “Customer Profile” and “No hit CP- Transaction” modules under “Customer Mangement” Group in order to view this screen. User must select a customer in customer profile listing page to access the “No hit CP- Transaction” tab. ### Wireframe Summary listing page [Image Removed] Detail view * 1. Record detail [Image Removed] * 1. Record status [Image Removed] ### Business Rules * 1. Click on No Hit CP- Transaction tab to list all No-Hit CP transaction of the customer as illustrated in the [wireframe](#_Wireframe_15). 2. One transaction detail record is one incoming transaction ( assinged to one Invoice No). 3. Detail view screen will display all campaign rule which transaction trigger but does not hit. 4. This screen just view only. There is no further actions. 5. Use the filter to locate particular transactions, which will be listed in the display. 6. Lookup no – hit transactions from OLS\_ORPHAN\_TXN\_NO\_HIT table for transaction which trigger campaign rule but not meet rule criteria OR transaction no linked any campaign rule. 7. This screen should desribe detail why transactions do not hit CP rule such as if critertia do not meet then which criteria failed. TP should response detail the error description to can show in this screen. 8. Screen description | | | | | | --- | --- | --- | --- | | **Index** | **Field** | **Description** | **Data type** | | **Account Information** | | | | | | CIF Number | Transacted CIF Number If incoming transaction are not provided then lookup by Account/ Card which are provided. | Display | | | Product Account No | Transacted Product Account Number and combination of Product Account Level and Product Account Type. If Incoming transaction are not provided then lookup by Card Number which is provided | Display | | | Account Type | | | Card number | Transacted Card Number | From incoming transaction | | **Transaction Detail** | | | | | | Invoice No | Unique Invocie No which generate by OLS system to determine unique incoming transaction. | Display | | | Transaction Type | Transaction Type of CP rule AWD- Award RED- Redeem ADJ- Adjust | Display | | | OLS Transaction Code | Transaction code which used to locate CP rule. | | | | Transaction Date Time | Transaction Date and Time | Display as date time format. The date format must adhere to the configured format From incoming transaciton | | | Transaction Amount | Transaction Gross Amount from incoming transaction for Award/Redeem transaction Adjust point for Adjustment transction | Display as number format 999,999,999.99 From incoming transaciton | | | Corporate | Transaction corporate ID Lookup value from transaction store | Display | | | Chain | Transaction chain ID Lookup value from transaction store | Display | | | Store | Transaciton Store ID | Display From incoming transaciton | | | Terminal | Transaction Terminal ID | Display From incoming transaciton | | | Transaction MCC | Transaction MCC Id | Display From incoming transaciton | | | Transaction Description | Transaction description | Display From incoming transaciton | | | Currency Code | Currency code of the original transaction amount | Display From incoming transaciton | | | Transaction Mode | Mode of transaction at point of payment | Display From incoming transaciton | | | DCC indicator | DCC indicator From incoming transaciton If empty then mean for non -DCC transaction | Display | | | Tap2Pay Indicator | Tap2Pay Indicator If empty then mean for transaction is not a Tap2Pay(token) transaction | Display | | | Token Requestor ID | Token Requestor ID (mobile pay) 3rd party wallet providers (Apple Pay, Samsung Pay, Android Pay etc | From incoming transaciton | | | Salary Credit | Salary Credit | From incoming transaction Indicates bundled deposit account is receiving regular salary credits | | | POS Entry Mode | POS entry Mode | From incoming transaction | | **CP Rule Listing** **Detail error description for each campaign Rule which incoming transaction trigger but do not hit this campaign Rule** | | | | | | Campaign ID | Campain ID | Lookup value by Campaign Rule ID | | | Campain Rule | Campaign Rule ID | Display | | | Pool ID | The reward pool of campaign rule | Display Lookup value by Campaign Rule ID | | | Error Code | Error response code from OLS | Display | | | Error Descriptions | Error response description | Display | Post-condition * + - 1. User can adjust incoming transaciton to meet Campain Rule or explain to customer why they do not get reward. ### Exception Flow N/A ## Statement ### Requirement Definition * + 1. Statement Enquiry is a list of all transactions for a customer/ account over a set period, usually monthly. The statement includes earned, redeemed and adjusted, as well as the beginning and ending balance for the period, along with any interest earned. ### Process Flow [Image Removed] ### Trigger User would like to review/verify statement detail of customer. ### Pre-Conditions 1. User have to have access rights in both “Customer Profile” and “Statement Enquiry” modules under “Customer Mangement” Group in order to this screen. 2. User must select a customer in customer profile listing page to view customer profile and access the “Statement Enquiry” tab. ### Wireframe * + - 1. Summary listing page [Image Removed] * + - 1. Detail view 1. Record detail [Image Removed] * 1. Record status [Image Removed] ### Business Rules * + 1. OLS statement output support Customer level and Account level, however statement records will be stored under Account level therefore Statement Enquiry show under Account level for both Statement Pool Entity level. 2. Statement Enquiry includes all active statement records of statement pool. 3. Statement records are updated by OLS batch jobs, so in administration functions (OA) only provides view in screens. There is no further actions. 4. Click on Statement Enquiry tab to list all statement records of the customer as illustrated in the [wireframe](#_Wireframe_6). 5. Click a listed record to display the details of the transaction as illustrated in the [wireframe](#_Wireframe_6). 6. Screen description | | | | | | --- | --- | --- | --- | | **Index** | **Field** | **Description** | **Data type** | | **Statement detail** | | | | | | Loyalty Account Number | Loyalty Account Number | Display Lookup value from STATEMENT table | | | Product Account Number | Product Account Number | Display Lookup value from PRODUCT\_ACCOUNT table by ASN in Statement table. | | | Account Type | Combination of Product Account Level and Product Account Type | | | Pool ID | Statement Pool | Display Lookup value from STATEMENT table | | | Cycle start date | Cycle start date time Provious statement cycle | | | Statement Opening balance | Previous Statement Points Balance | | | Total Award | Total earned points in this cycle | | | Total Redeem | Total redemmed points in this cycle | | | Total Adjust | Total Adjusted points in this cycle | | | Statement Closing Blance | Accumualted points | | | Expired points | Balance in expired buckets which have not yet been forfeited | | | Last transaction Date | Last transaction post date on this cycle | | | Cycle statement date | Cycle statement date time | | **Transaction Detail** This part display all transaction of account/customer on each cycle. [Image Removed] Get data from TRANSACTION table where: * + 1. LA is LA of customer statement records. 2. Pool ID is statement pool 3. ASN is ASN of Account statement records. 4. Post date from Cycle Start Date upto Last Transaction Date 5. Without cancellation transaction 6. Points are not equal to 0 | | | | | | Reference Number | OLS Reference Number | Display | | | Transaction Type | Transaction Type of this transaction | Display Lookup value from Transaction table | | | Unit | Earned/ Redeemed/Adjusted point Depended on transaction type Group by Reference No,Post Date,Transaction date and Txn type | | | Post Date | Post Date time | | | Transaction Date | Transaction Date Time | ### Post – Condition N/A ### Exception Flow N/A ## Attribute ### Requirement Definition * + - * 1. In nearest version of OLS, on each sub tab: Customer profile, Account and Card will display according attribute: 1. Customer profile screen dislays customer information and Customer attribute lisitng. 2. Account Detail screen dislays Account information and Account attribute of customer. 3. Card detail screen displays Card information and Card attribute of customer. 1. In new OLS version Attribute will be displayed on separately tab under Customer profile module. ### Process Flow [Image Removed] ### Trigger * + 1. User would like to review/ verify attribute detail of customer. ### Pre-Conditions 1. User have to have access rights in both “Customer Profile” and “Attribute” modules under “Customer Mangement” Group to able to view this screen. 2. Users must select a customer on the customer profile listing page to access the "Attribute Enquiry" tab. ### Wireframe * + - 1. Summary listing page [Image Removed] Figure 1: Listing page [Image Removed] Figure 2: Filter * + - 1. Detail view 1. Record detail [Image Removed] * 1. Record status and history [Image Removed] ### Business Rules * + - * 1. Get data from ATTRIBUTE\_VALUE table. The attribute values inserted/update form OLS batch process (Attribute maintenance batchs or OMR batch job) OR can be updated by the Attribute maintenance batch as well as by Campaign Rules. 2. This screen just display atribute value only. There is no further action. 3. The Attributes listing screen is accessed from the Attribute Tab in the Customer profile module. Clicking on the Attributes Tab will bring up a listing of Attributes, as illustrated in the [wireframe](#_Wireframe_7). 4. In this screen will display all attribute of customer including Customer attribute/Account attribute/ Card attribute. 5. Clicking on the Attribute value row in listing page will bring up the attribute value detail of customer, as illustrated in the [wireframe](#_Wireframe_7). 6. Description of Attribute value detail field | | | | | | --- | --- | --- | --- | | **Seq** | **Field (EN/Vn)** | **Description** | **Data type** | | **Filter** Apply quick search functions as common function on OLS administrator screen without Entity ID and Effect date. | | | | | | Entity /Thực thể | Optional field Including: Client/Product\_Account/ Card If Client entity is selected then listing all customer attribute of customer. If Product\_Account entity is selected then listing all account attribute of customer. If Card entity is selected then listing all card attribute of customer. If Entity is not provided then get all attribute of customer which under Customer/ Account/Card entity level | Drop-down Allow multiple select. Default as empty | | 2. | Effective Date From /Ngày bắt đầu có hiệu lực | Mandatory Listing attribute value during selected date frame. | Date time | | 3. | Effective Date To/Ngày kết thúc hiệu lực | | | Only effective records listed/Chỉ hiển thị các giá trị thực thể có hiệu lực | Use processing date to compare with attribute value effective date. If selected then only effective records listed If non-select then all attribute record including expired attribute value records listed | Check box Default as selected | | **Attribute value detail field / Thông tin chi tiết thuộc tính** | | | | | | Attribute Group/Nhóm thuộc tính | Attribute group of attribute | Display Lookup value from ATTRIBUTE\_MAINTENANCE table by Attribute ID | | | Attribute ID/ID thuộc tính | Attribute ID | Display Lookup value from ATTRIBUTE\_VALUE table | | | Attribute Name / Tên thuộc tíng | Attribute Name | Display Lookup value from ATTRIBUTE\_MAINTENANCE table by Attribute ID | | | Entity / Thực thể | Entity level of attribute Indicates the Entity to which this Attribute belongs Client: Customer Product\_Account : Account Card: Card | Display Lookup value from ATTRIBUTE\_MAINTENANCE table by Attribute ID | | | Entity ID/ ID thực thể | The identifier for the Entity to which the Attribute value in this record belongs. If Entity is : • “Product\_Account”, this field contains the PA Number • “Card”, this field contains the Card Number • “Client”, this field contains the CIF Number * “Store”, this field contains the Store ID * ……etc…. | Entity value will be : * + 1. CSN for customer attribute. 2. ASN for account attribute 3. PSN for Card attribute. Use Entity and Entity\_ID of attribute for lookup according value: | | | Account Type/ Loại tài khoản | Combinaiton of Product Account Level and Product Account Type of Account attribute. Present for Account attribute only | Display Lookup value from PRODUCT\_ACCOUNT table | | | Attribute value /Giá trị thuộc tính | Attribute value | Display Lookup value from ATTRIBUTE\_VALUE table | | | Effective Date From/ Ngày bắt đầu có hiệu lực | Start date of the effective period for the Attribute value | | | Effective Date To/Ngày kết thúc hiệu lực | End date of the effective period for the Attribute value | | **List of Campaign/Danh sách chiến dịch** **This appear when user click to view detail of any record** [Image Removed] | | | | | | Campaign ID/ID chiến dịch | Campaign ID which reference to Campaign Rule | Display Lookup value from “Campaign Rule screen” | | | Campaign Name | Name of Campaign | Display Refer to “Campaign “ API under Campaign Management Lookup value from “Campaign” table. | | | Campaign Rule | Campaign Rules which reference to this attribute | Display Lookup value from “Campaign Rule” screen to list all campaign rules which includes this attribute on at least following items: * + 1. Attribute Criteria 2. Formula 8 3. Formula 7 4. Award limit | | | Campaign Rule Name | Name of Campaign rule | Display Lookup value from “Campaign\_Rule” tablle Refer “Campaign Rule” API under Campaign Management | | | Effect date | The Effect date of Campaign Rule Dislay both Effective from date and effective to dat e | Display The date format must adhere to the configured format | ### Post-Conditions N/A ### Exception Flow N/A ## Counter ### Requirement Definition * + - * 1. In nearest version of OLS, on each sub tab: Customer profile, Account and Card will display according Counter: - Customer profile screen dislays customer information and customer -level counter listing - Account Detail screen dislays Account information and account -level counter of customer. - Card detail screen displays Card information and card -level counter of customer. 1. In new OLS version Counter will be displayed on separately tab under Customer profile module. ### Process Flow ### Trigger * + 1. Users would like to review and verify the counter detail of the customer. ### Pre-Conditions 1. User have to have access rights in both “Customer Profile” and “Counter” modules under “Customer Mangement” Group in order to view this screen. 2. Users must select a customer on the customer profile listing page to access the "Counter " tab. ### Wireframe * + - 1. Summary listing page [Image Removed] Figure 1: Listing page [Image Removed] Figure 2: Filter * + - 1. Record detail 1. Record detail view [Image Removed] * 1. Record status [Image Removed] ### Business Rules * + - * 1. Get data from the table that updates the counter value (Campaign\_Counter table). The counter values are inserted/updated from the OLS batch process that triggers the Campaign Rules as well as the OA screen. 2. This screen just displays counnter value only. There is no further action. 3. The Counter Detail listing screen is accessed from the Counter Tab in the Customer profile module. Clicking on the Counter Tab will bring up a listing of the counter, as illustrated in the [wireframe](#_Wireframe_8). 4. In this screen will display all counter bucket for the chosen customer, including Customer-level counter/Account -level counter/ Card- level counter. 5. Clicking on the Counter value row in listing page will bring up the counter value detail of customer, as illustrated in the [wireframe](#_Wireframe_7). 6. Description of Counter value detail field: | | | | | | --- | --- | --- | --- | | **Seq** | **Field (EN/VN)** | **Description** | **Data type** | | **Filter** Apply quick search functions as common function on OLS administrator screen without Entity level and Counter bucket period | | | | | | Entity /Thực thể | Optional field Including: **Customer [CU]/ Account [PA] /Card [CA].** If “Customer[CU]“ is selected then listing all customer -level counter of customer. If “Account [PA]” is selected then listing all account- level counter of customer. If “Card [CA]”is selected then listing all card -level counter of customer. If Entity level is not provided then get all counter level of customer which under Customer/ Account/Card entity level. | Drop-down Allow multiple select. Default as empty | | 2. | Bucket Start Date / Ngày bắt đầu | Mandatory Listing counter value during selected date frame. | Date | | 3. | Bucket End Date/ | | | Only effective records listed/Chỉ hiện thị counter hiện tại | Use processing date to compare with counter bucket period. If selected then only effective records listed. Use processing date to determine the effective of the counter bucket. If non-select then all counter value record including expired counter records listed | Check box Default as selected | | **Counter value detail field** | | | | | | Counter/Bộ đếm | Counter | Display | | | Entity /Cấp bộ đếm | Entity counter level Cust- CU Account – PA Card – CA | Display | | | Entity ID/ID thực thể | The identifier for the Entity to which the counter value in this record belongs. If Entity is : • “Account”, this field contains the Account Number • “Card”, this field contains the Card Number • “Customer”, this field contains the CIF Number | Display | | | What to count/ Tiêu chí đếm | The data entity that is to be counted or tracked | Display | | | Counter Value/Giá trị bộ đếm | Counter value | Display as number format | | | Bucket start date | Start date of the bucket period for the Counter value | Display as date format | | | Bucket end date | End date of the bucket period for the Counter value | Display as date format | | | Counter state/Tình trạng bộ đếm | Counter state A: Awared C: New | Display Show state code only | | **Counter Statistic / Tổng hợp bộ đếm** [Image Removed] **This part will list the details of the counter history statistics for the chosen counter bucket in the listing page** | | | | | | Reference No/ Số tham chiếu giao dịch | OLS Transaction Reference Number | Display | | | Post Date /Ngày đăng | The post date of the transaction | Dipslay as date time format The date format must adhere to the configured format | | | Counter Value/Giá trị bộ đếm | Counter value which is updated on this transaction | Display as number format | | | Bucket Number/Số bộ đếm | The bucket number of selected counter | Display as interger number format | | | Update Date | The system date when counter value is updated | Dipslay as date time format The date format must adhere to the configured format | | | Updated by | The batch/User who post the transaction that make counter value is changed. | Display | ### Post-Conditions N/A ### Exception Flow N/A ## Adjustment ### Requirement Definition 1. Adjustment transactions can be manually posted through the Customer Management module in the administration screen function under. 2. This screen display all manually adjustment transaction of customer. ### Process Flow [Image Removed] ### Trigger * + 1. User would like to review/ verify manually adjustment transaction of customer. 2. There is some wrong in balance of customer then user have to manually adjust via OA screen. ### Pre-Conditions 1. User have to have access rights in both “Customer Profile” and “Adjustment Entry” modules under “Customer Mangement” Group in order to view this screen. 2. Users must select a customer on the customer profile listing page to access the "Adjusment Entry" tab 3. Depending on the user’s access rights, they can view/edit/add or approve manually Adjustment transaction records. ### Wireframe * + - 1. Summary listing page [Image Removed] * + - 1. Active record Record detail [Image Removed] [Image Removed] 1. Create/Edit form Create /Edit mode [Image Removed] [Image Removed] * + - After selected/inputted card/Account/CIF click to quick view icon to see right panel information [Image Removed] ### Business Rules 1. While under “Transaction Management” module in the administration screen function, manually adjustment transaction can be posted for any customer then in “Customer management”module manually adjustment transaction can be posted for selected customer only. 2. Click on the Adjustment Entry tab in the “Customer Profile “sreen to bring up the screen for accessing the Adjustment Entry listing page. The detail as illustrated in the [wireframe](#_Wireframe_9). 3. Click on Add button ([Image Removed]) in the screen to bring up the edit form; clicking on the MoreOutLined icon (⋮) then click on Edit icon (!) also brings up the same edit form. The edit form for Adjustment Entry screen is illustrated in the [wireframe](#_Wireframe_9). 4. Noted that Edit icon (!) and Delete icon just display for pending and rejected record only. 5. User stories and acceptance criteria [Image Removed] 1. Screen desscriptions | | | | | | | --- | --- | --- | --- | --- | | **Index** | **Field** | **Desscription** | **Data type** | | | **Adjustment detail** | | | | | | | Posted transaction by\*/ Tạo giao dịch bởi | Transacting Account/Customer identifier. Only one of the followings: CIF number/ Account / Card must be provided | Radio button Default posted by Card Look up value from master data | | | | | | Under Customer management module | Under Transaction Management module | | | Card Number/Số thẻ | Any of the customer's card numbers. Condition filed This field is only active and required if txn is posted by Card. | Drop -down Select one List all card of selected customer | Drop-down Select one Put any Card number in OLS system. Default emptu to avoid performance issue then user must enter at least 4 digits of Card number to find card. Refer “Customer” API under Customer Management | | | Product Account Level/Loại tài khoản | Product Account Level Condition Filed This field is only active and required if txn is posted by Account. | Drop-down Select one List distinct account level for all accounts of selected customer. Refer “==tbd== “ API | Drop-down Select one List all account level in the OLS system. Refer “Product Account Level” API under Code Maintenance service | | | Product Account Type/Hạng tài khoản | Product Account Type Condition Filed This field is only active and required if txn is posted by Account. | Drop-down Select one List distinct account types for the selected account level of the selected customer. Refer “==tbd== “ API | Drop-down Select one List all account type in the OLS system by selected Account level. Refer “Product Account Type” API under Code Maintenance service | | | Account Number /Số tài khoản | Product Account Number Condition filed This field is only active and required if txn is posted by Account. | Drop-down Select one List all account number for selected account type of selected customer Refer “Account “ API under Customer Management service | Drop-down Select one List all account number for selected account type in the OLS system. Default empty to avoid performance issue then user must enter at least 4 digits of Card number to find card. Refer “Product Account” API under Customer Management. | | | CIF number /Số CIF | CIF number Condition filed This field is only active and required if txn is posted by Customer. | Read only This is selected CIF Number | Drop-down Select one List all CIF number in the OLS system. Default empty to avoid performance issue then user must enter at least 4 digits of CIF number to find CIF. Refer “Customer Profile” API under Customer Management. | | | Quick view/Xem nhanh | Click on each quick view icon (balance or Buket Balance Detail View) to retrieve the available balances of the customer after entering the card/account/CIF number. The details will be displayed in the right panel. See more in Quick view part Show error message if Requesting Card/Account/CIF is invalid.t With Edit/Create mode the system will expand / collapse on the same screen to user can see and continue input needed information as illustrated following: [Image Removed] With View/Approve/Reject mode the system will show detail as pop-up when click on each quick view icon as illustrated following: [Image Removed] | Hyperlink/Icon | | | | Adjustment Quantity is +ve/-ve \*/ Điều chỉnh âm/dương | Indicates whether the adjustment is a positive adjustment or a negative adjustment | Drop-down Select one Lookup value from “Code\_Management” table Refer “list-by-code-type” API with code type is “adj-type” | | | | Store \*/Đơn vị/Cửa hàng | The store of transaciton | Drop-down Select one Lookup active Store record from “Store” screen Refer “Store” API under Merchant Managemant. | | | | Pool Id \*/Mã pool | The pool to be adjusted Should respect pool entity level For example: Cant posted txn by Account if pool to be adjusted is card- entity level pool. | Drop-down Select one | | | | Transaction Date\*/Ngày giao dịch | Transaction date | Time picker within time also DD-MM-YYYYY HH:MM:SSS Allow user input from keybroad | | | | Expiry Date \*/Ngày hết hạn | This is the expiry date of the new bucket after the expired points have been adjusted. Present for postive adjustment only Show the balance bucket based on transaciton Date and expire policy of adjusted pool. When update transaction date / Card number (Account /CIF) OR Pool then this value should be automation updated. Allow user modify this value | Time picker without time DD-MM-YYYY Allow user input from keybroad | | | | Bucket Expiry Date/ … | This is the expiry date of the bucket will be deduct poitn. Present for negative adjustment only If not selected then follow by TP processing for Redemption/Negative adjustment approach. If selected then just adjust on the selected bucket. | Drop-down Select one Loopkup value from customer balance based on adjusted pool/selected card. | | | | Adjustment Quantiy \* /Số lượng điều chỉnh | The pool units by which to adjust the pool balance. | 9(12,2) Should be greater than 0 if provided | | | | Reason Code \*/Mã lí do điều chỉnh | The Reason Code is a drop-down providing a set of pre-defined reason codes to explain the reason for the adjustment. | Drop-down Lookup value from Reason Code screen | | | | Transaction Code \*/Mã giao dịch | OLS transaciton code of transaction | Drop- down Lookup value from OLS Transaction Code screen | | | | Remarks/Ghi chú | A description of the adjustment. | X(100) | | | **Quick view** **Balance Detail View** [Image Removed] Show pool bucket balances take into account the entity level in the display. If posted txn by Card then : Show pool bucket balances take into Card considering entity level in the display: * + 1. Get all balance bucket of customer regardless selected card for customer entity- level pool. 2. Get all balance buckert of Account of the selected card for account entity-level pool 3. Get the balance bucket of the selected card only for the card entity-level pool. If posted txn by Account then : Show pool bucket balances take into Account considering entity level in the display: * + 1. Get all balance bucket of customer regardless selected Account for customer entity -level pool. 2. Get all balance of Account of selected card for account entity- level pool 3. Card pool –entity level should not be present. If posted txn by CIF number then: Get all customer – entity level pool balance bucket of chosen customer. Card and account pool entity-level should not be present. **Noted that: Each row represent each pool which take into account the entity level in the display** **Use processing date to determine available balance which ready to be redeemed.** | | | | | | | Pool ID | Pool ID | Lookup value from LAB table | | | | Balance | Total balance buckets of a reward pool of customer. Show up to the pool entity level | Display as number format Lookup value from LAB table | | | | Redeemable Balance | The sum all non-balance buckets of a pool of customer. Show up to the pool entity level | Display as number format Lookup value from LAB table | | | | Earliest Exp Bal and Date | The earliest expiring bucket date for a pool, for non-0 balance buckets. Show up to the pool entity level And Balance that is expiring on The earliest expiring bucket date. The balanace should not be zero balance. | Display as number format Lookup value from LAB table | | | **Bucket Balance Detail View** [Image Removed] The same as [Balance enquiry](#_Balance_Detail_Enquiry) Display all buckets of the Pool of the customer, regardless of Entity Level | | | | | | | Account number | Product Account No | Display Present for all pool entity-level | | | | Product Account Type | Combination of Product Account Type and Product Account level of Account | | | Product Account level | | | Card Number | Card number | Display Present for Card pool entity level only If there are more than Card under the same Plastic Serial Number then the newest cards is present. | | | | Pool ID | Pool ID | Display Loopkup value from LAB table. | | | | Balance | Non zero balance | Display Loopkup value from LAB table. | | | | Expiry Date | Expring date | Display Loopkup value from LAB table | | * + - 1. Edit Action just be applied for Pending/Rejected record. 2. For Active Record just view only. 3. After the transaction has been saved, it is put in the pending tab. 4. An authorised user has to retrieve the transaction and approve it before it is processed and pool is updated: **Based on entity level/account selection alog** * 1. For postive adjustment transaction then: + If have negative balance bucket then adjusted point used to offset negative balance bucket to 0 first. + The remaining points will be added for selected bucket. 2. For negative adjustment transaction then: [Image Removed] * + - 1. Approved transaction is putted in the active tab. ### Post-Conditions * + - Pool balance buckets are updated. - Transaciton is posted and viewable on the transaction history screen. ### Exception Flow * + 1. Input data are not passed all validations and then user choose cancel the action then use case ends in failure. 2. Transaciton is rejected by TP validation such as block code validation, ATG validation … ## Transfer balance ### Requirement Definition 1. Transfer balance transactions can be manually posted through the Customer Management module in the administration screen function under. 2. Change in UI/UX and change to support both user can transfer balance from their account to other customer or transfer between its own self. ### Process Flow [Image Removed] ### Trigger * + 1. The user would like to review/verify the manually transferred points from a customer to another customer or between the customer's own accounts/cards. ### Pre-Conditions 1. User have to have the access rights in both “Customer Profile” and “Transfer Balance” modules under “Customer Mangement” Group in order to view this screen. 2. Users must select a customer on the customer profile listing page to access the "Transfer Balance" tab. 3. Depending on the user’s access rights, they can view/add/Edit or Approve manually transfer points transaction records. ### Wireframe * + - 1. Summary listing page [Image Removed] * + - 1. View detail form [Image Removed] * + - 1. Create/Edit form [Image Removed] ### Business Rules 1. Click on the “Transfer Balances” tab in the “Customer Profile “screen to bring up the screen for accessing the Transfer Points listing page. The detail is illustrated in the [wireframe](#_Wireframe_10). 2. Click on the Add button ([Image Removed]) in the screen to bring up the edit form; clicking on the MoreOutLined icon (⋮) and then clicking on the Edit icon (!) also brings up the same edit form. The edit form for the Transfer Balance screen is illustrated in the [wireframe](#_Wireframe_10). 3. Noted that the Edit icon (!) and Delete icon just display for pending and rejected records only. 4. The point transfer function will transfer all pools linked directly from the “From” to the “To”. 5. Expiry Dates will be preserved unless a specific date is provided. 6. User stories and acceptance criteria [Image Removed] 1. F**orm descriptions:** | | | | | | --- | --- | --- | --- | | **Seq** | **Field** | **Descriptions** | **Data type** | | | Transfer mode \*/ Phương thức điều chuyển | Use transfer mode to determine the relationship between from transfer source and the transfer destination. Check on the “Internal” mode to transfer balances itself. Check on the “External” mode to transfer the balance from a customer to another customer in the OLS system. Use Application Parameter to allow/disallow transfer mode: Apply both or only Internal or only external | Radio button Default “Internal” transfer Lookup value from “Code\_Management” table where code type is ‘transfer-mode’. Refer “list-by-code-type” API under Master Data. | | | Transfer Type\*/Loại điều chuyển | Condition field Depend on Transfer Mode to disable/enable as follows: Note: “X” stands for enable | | | | | | --- | --- | --- | --- | | **Transfer mode** | **Transfer Type disable/enable** | | | | **Card** | **Account** | **Client** | | Internal | X | X | | | External | X | X | x | | Radio button Default “Card”. Lookup value from “Code\_Management” table where code type is ‘entity-lvl’. Refer “list-by-code-type” API under Master Data. | | | From \*/Từ | A card/Account/CIF number must be present which depends on the transfer mode. | Drop-down Select one | | | Product Account Type /Hạng tài khoản | Condition filed This field is only active and required if transferred by Account. This is the product account type of the selected source account | Drop-down Select one | | | Product Account level /Cấp tài khoản | Condition filed This field is only active and required if transferred by Account. This is the product account level of the selected source account | Drop-down Select one | | | Quick view/Xem nhanh | Click on each quick view icon to retrieve the available balances of the customer after entering/selecting the card number. The details will be displayed in the right panel. See more in the Quick view part Show an error message if the Requesting Card is invalid. With Edit/Create mode the system will expand/collapse on the same screen to user can see and continue input needed information but with View/Approve/Reject mode the system will show detail as pop-up when click on each quick view icon See more in Quick view part | Hyperlink | | | To \*/Đến | Card /Account/CIF number must be present which depened on transfer mode. If Transfer Type is “Account” then Account type is present. | Drop-down Select one | | | Product Account Type /Hạng tài khoản | Condition filed This fild is only active and required if transfer by Account. This is product accout type of selected destination Account | Drop-down Select one | | | Product Account level /Cấp tài khoản | Condition filed This fild is only active and required if transfer by Account. This is product accout level of selected destination Account | Drop-down Select one | | | Pool ID\*/Mã pool | The pool from which to transfer Just show the pool of “From” balance buckets as following: X: Display | | | | | | --- | --- | --- | --- | | **Transfer Type** | **Pool balance bucket of “From” Customer.** | | | | **Pool Level Card** | **Pool level Account** | **Pool Level cust** | | Card | X Display distinct Card- entity Pool of balance bucket of Inputed card only | X Display distinct account -entity Pool of balance bucket of Account of Inputed card | X Display distinct customer -entity pool of balance bucket of customer of inputed card | | Account | | X Display distinct account- entity Pool of balance bucket of inputed account only | X Display distinct customer- eintiy pool of balance bucket of customer of inputed account | | Client | | | X Display distinct customer-entity pool of balance bucket of inputed CIF Number | | Drop- down Based on Transfer Type and “From” to lookup pool from LAB and Pool Definition table. | | | Store\*/Cửa hàng-Đơn vị | The store which transaciton is logged | Drop -down Lookup value from Store screen- Store table. Refer “Store” API under Merchant Management | | | Amount to Transfer \*/Mức điều chuyển | The amount to transfer. Defaults to the whole pool balance. | 9(14,2) Should be greater than 0 if provided | | | Expiry Date (after transfer)/Ngày hết hạn | The expiry date of the points after the transfer. By default the expiry date will be the source expiry date. | Date time | | | Transaction Code\*/Mã giao dịch | OLS transaction code which transaction is logged | Drop -down Lookup value from OLS TC screen. Refer “OLS Transaction Code” API under Campaign Management | | | Reason Code \*/Mã lí do điều chuyển | Select from a list of pre-defined codes to identify the reason for the transfer | Drop-down Lookup value from Reason Code screen (Reason\_Code table). Refer “Reason Code” API under Code Maintenance | | | Remarks/Ghi chú | Remarks to be appended to the transaction, for reference | Text box X(100) | | **Bucket Balance Detail view of Source** The same as [Balance enquiry](#_Balance_Detail_Enquiry) Display all buckets of the Pool, regardless of Entity Level | | | | | | Account number/Số tài khoản | Product Account No | Display Present for all pool entity level | | | Product Account Type/Hạng tài khoản | Combination of Product Account Type and Product Account level of Account. | Display Present for all pool entity level | | | Product Account level/Cấp tài khoản | | | Card Number/Số thẻ | Card number | Display Present for Card pool entity level only If found more than one Card under the same Plastic Serial Number then the newest card is present. | | | Pool ID/Mã pool | Pool ID | Display Loopkup value from LAB table. | | | Balance /Số dư | Non zero balance | Display Loopkup value from LAB table. | | | Expiry Date/Ngày hết hạn | Expring date | Display Loopkup value from LAB table | | **Bucket Balance Detail view of Destination** The same as [Balance enquiry](#_Balance_Detail_Enquiry) Display all buckets of the Pool, regardless of Entity Level | | | | | | Account number/Số tài khoản | Product Account No | Display Present for all pool entity level | | | Product Account Type/Hạng tài khoản | Combination of Product Account Type and Product Account level of Account. | Display Present for all pool entity level | | | Product Account level/Cấp tài khoản | | | Card Number/Số thẻ | Card number | Display Present for Card pool entity level only If found more than one Card under the same Plastic Serial Number then the newest card is present. | | | Pool ID/Mã pool | Pool ID | Display Loopkup value from LAB table. | | | Balance /Số dư | Non zero balance | Display Loopkup value from LAB table. | | | Expiry Date/Ngày hết hạn | Expring date | Display Loopkup value from LAB table | 1. After the transaction has been saved, it is put in the pending list. 2. An authorised user has to retrieve the transaction and approve it before it becomes effective. 3. OLS will validate the status permission and block code permission for both “From” and “To”, the transfer transaction will be rejected if any permission disallowed to perform adjustment. 4. Transfer transaction will be rejected if Pool balance of “From” is insufficient. 5. The Approved transfer transaction is logged as Adjustment transactions and following by TP processing: 1. Each bucket in the “From” is transferred as a negative adjustment to the “From” and logged as a positive Adjustment to the “To”. 2. The Reason Code will be selected from a list of Adjustment Reason codes. 3. The Adjustment Reason Code is important for determining the GL posting accounts. ### Post-Conditions * + 1. Pool balance buckets are updated. ### Exception Flow * + 1. Pool balance of “From” is insufficent. 2. Transaciton is rejected by TP validation such as block code validation, ATG validation … 3. Input data are not passed all validations and then user choose cancel the action then use case ends in failure. ## Re-instatement ### Requirement Definition 1. This screen is used to re-instatement for expired balance bucket which have not been forfeited. 2. If balance have been forfeited, then “re-instatement” does not apply and an adjustment transaction should be used to return points to the customer. ### Process Flow [Image Removed] ### Trigger * + - 1. User want to review/verify Re-Instatement transaction 2. User want to re-instate expired bucket. ### Pre-Conditions 1. User have to have access righsts in s both “Customer Profile” and “Re-Instatement” modules under “Customer Mangement” Group in order to view this screen. 2. Users must select a customer on the customer profile listing page to access the "Re-Instatement" tab. 3. Customers have pool expired bucket which have not been forfeited. 4. Depending on the user's access rights, they can view, add, edit, or approve manually Re-Instatement Transaction records. ### Wireframe * 1. Summary listing page [Image Removed] * 1. Record detail view [Image Removed] * 1. Create/Edit form [Image Removed] ### Business Rules 1. Click on the “Re-Instatement” tab in the “Customer Profile “sreen to bring up the screen for accessing the Re-Instatement listing page. The detail as illustrated in the [wireframe](#_Wireframe_11). 2. Click on Add button ([Image Removed]) in the screen to bring up the edit form; clicking on the MoreOutLined icon (⋮) then click on Edit icon (!) also brings up the same edit form. The edit form for Re-Instatement screen is illustrated in the [wireframe](#_Wireframe_11). 3. User stories and acceptance criteria [Image Removed] 1. Noted that Edit icon (!) and Delete icon just display for pending and rejected record only. 2. Form description: | **Seq** | **Field** | **Description** | **Data type** | | | --- | --- | --- | --- | --- | | | Posted transaction by\*/ Tạo giao dịch bởi | Transacting Account/Customer identifier. Only one of the following 3 (CIF Number, Account , Card Number) must be provided | Radio button Default posted by Card Lookup value from “Posted txn by” type code in master data | | | | | | **Under customer management** | **Under Transaction Management** | | Card Number/Số thẻ | Any of the customer's card numbers. Condition filed This field is only active and required if txn is posted by Card. | Drop -down Select one List all card of selected customer | Drop-down Select one Put any Card number in OLS system. Default emptu to avoid performance issue then user must enter at least 4 digits of Card number to find card. | | Product Account Level/Loại tài khoản | Product Account Level Condition Filed This field is only active and required if txn is posted by Account. | Drop-down Select one List distinct account level for all accounts of selected customer. | Drop-down Select one List all account level in the OLS system. | | Product Account Type/Hạng tài khoản | Product Account Type Condition Filed This field is only active and required if txn is posted by Account. | Drop-down Select one List distinct account types for the selected account level of the selected customer. | Drop-down Select one List all account type in the OLS system by selected Account level. | | Account Number /Số tài khoản | Product Account Number Condition filed This field is only active and required if txn is posted by Account. | Drop-down Select one List all account number for selected account type of selected customer | Drop-down Select one List all account number for selected account type in the OLS system. Default empty to avoid performance issue then user must enter at least 4 digits of Card number to find card. | | CIF number /Số CIF | CIF number Condition filed This field is only active and required if txn is posted by Customer. | Read only This is selected CIF Number | Drop-down Select one List all CIF number in the OLS system. Default empty to avoid performance issue then user must enter at least 4 digits of CIF number to find CIF. | | | Quick view /Xem nhanh | Click on each quick view icon (balance or Buket Balance Detail View) to retrieve the available/expired balances of the customer after entering the customer information. The details will be displayed in the right panel. See more in Quick view part Show error message if Requesting Card/Account/CIF are invalid. With Edit/Create mode the system will expand / collapse on the same screen to user can see and continue input needed information as illustrated following: [Image Removed] With View/Approve/Reject mode the system will show detail as pop-up when click on each quick view icon as illustrated following: [Image Removed] | Hyperlink | | | | Store \*/Cửa hàng\_Đơn vị | Store | Drop -down Select one | | | | Pool Id \*/Mã pool | The pool to be adjusted. The pool of the bucket to Re-instate. Just list the pool have balance which has already expired, but are still within the grace period (haven’t forfeited), while respecting the pool entity-level based on transfer mode. E.g Use account to re-instate then cant select card pool entity-level | Drop-down Select one | | | | Bucket to Re-instate \*/Số lô cần gia hạn | The drop-down displays the expired buckets of the selected pool which have not been forfeited The bucket to be re-instated must be selected individually and the new expiry date must be provided in the “Expiry Date” field. | Drop-down Select one Lookup value based on LAB table. | | | | Expiry Date \*/Ngày hết hạn | This is the expiry date of the new bucket after the expired points have been re-instated. | Date The date format must adhere to the configured format | | | | Reason Code \*/Mã lí do | The Reason Code is a drop-down providing a set of pre-defined reason codes to explain the reason for the re-instatement. | Drop-down Select one Lookup value from Reason Code screen with Reason type is Re-instatement Refer “Reason Code” API under Code Maintenance | | | | Remarks/Ghi chú | Additional remarks on the re-instatement. | X(100) | | | Quick View Expired Balance Detail This part display Expired bucket which haven’t been forfeited of selected/inputted acccout/Card/CIF. The expired pool bucket balances should take into account the entity level in the display. **If use Card to post re-instatement txn then:** * + 1. Get all expired balance buckets of customer regardless selected/inputed card for Customer entity level pool 2. Get all balance expired buckets of Account of selected/inputed card for Account entity level pool 3. Get all blance expired buckets of selected/inputed card only for Card entity level pool If **use Account to post re-instatemeen txn then:** * + 1. Get all balance expired buckets of customer regardless selected/inputed account for Customer entity- level pool 2. Get all balance expired buckets of selected/inputed account for Account entity -level pool. 3. Card pool entity-level should not be present. If **use CIF numebr to post re-instatemeen txn then** get all customer – entity level pool expired balance bucket of chosen customer. Card and account pool entity-level should not be present. Take note that: Use Processing Date to compare with expiry date to located eligible pool balance bucket. **Each row represent each pool which take into account the entity level in the display** | | | | | | | Pool ID/Mã pool | Pool ID | Display Lookup value from LAB table via selected Card. | | | | Balance /số dư | Total Expired balance | | | Expiry Date/Ngày hết hạn | Expiry date | | **Bucket Balance Detail view** The same as [Balance enquiry](#_Balance_Detail_Enquiry) Display all buckets of the Pool, regardless of Entity Level | | | | | | | Account number/Số tài khoản | Product Account No | Display Present for all pool entity level | | | | Product Account Type/Hạng tài khoản | Combination of Product Account Type and Product Account level of Account. | Display Present for all pool entity level | | | | Product Account level/Cấp tài khoản | | | Card Number/Số thẻ | Card number | Display Present for Card pool entity level only If found more than one Card under the same Plastic Serial Number then the newest card is present. | | | | Pool ID/Mã pool | Pool ID | Display Loopkup value from LAB table. | | | | Balance /Số dư | Non zero balance | Display Loopkup value from LAB table. | | | | Expiry Date/Ngày hết hạn | Expring date | Display Loopkup value from LAB table | | 1. After the transaction has been saved, it is put in the pending list. 2. An authorised user has to retrieve the transaction and approve it before it becomes effective. 3. The re-instatement will be posted as an Adjustment, with the Reason Code set to the selection. 4. The balance in the expired buckets will be set to 0. 5. If the bucket with the required expiry date exists, the adjustment amount will be added to the bucket. 6. Otherwise, a new bucket with the new expiry date as entered in the Re-instatement edit form is created with the balance from the expired bucket. ### Post-Conditions ### Exception Flow * + 1. Transaciton is rejected by TP validation such as block code validation, ATG validation … 2. Input data are not passed all validations and then user choose cancel the action then use case ends in failure. ## Item Redemption ### Requirement Definition 1. Customers call the customer service (call center) and requests to redeem an item, giving identification and item code. 2. Item redemption requests are processed against the catalogue item set-up parameters. The details are described against the relevant parameter in the catalogue item set-up description in section 7. 3. All redemptions are in real-time. 4. Redemption through administration screens that requires approval is real-time only at time of approval. ### Process Flow [Image Removed] ### Trigger * + - 1. Users use this screen to assist customers in exchanging points for items. 2. Users want to review and verify the redemption item transaction details of customers, which includes all online transactions via the OA screen or M as well. ### Pre-Conditions 1. Users have to have access rights in both “Customer Profile” and “Item Redemption Entry” modules under “Customer Mangement” Group in order to view this screen. 2. Users must select a customer to access the “Item Redemption Entry” tab. 3. Depending on the user's access rights, they can view, add, edit, or approve manually Item Redemption Transaction records. ### Wireframe * 1. Summary listing page [Image Removed] * 1. Record detail view [Image Removed] Click on each item to bring up item detail view [Image Removed] * 1. **Create** **Step 1: Add General information** [Image Removed] [Image Removed] **Step 2: Add Physical /Evoucher item** [Image Removed] [Image Removed] **Step 2: Add Miles item** [Image Removed] [Image Removed] **Step 2: Add cash rebate item** [Image Removed] [Image Removed] **Step 2: Add other items** [Image Removed] [Image Removed] ### Business Rules 1. Click on the “Item Redemption Entry” tab in the “Customer Profile “screen to bring up the screen for accessing the Item Redemption Entry listing page. The detail as illustrated in the [wireframe](#_Wireframe_12). 2. Click on Add button ([Image Removed]) in the screen to bring up the edit form; clicking on the MoreOutLined icon (⋮) then click on Edit icon (!) also brings up the same edit form. The edit form for Re-Instatement screen is illustrated in the [wireframe](#_Wireframe_12). 3. User can’t modify transaction after transaction is posted. 4. User stories and acceptance criteria [Image Removed] 1. Screen descriptions: | | | | | | | --- | --- | --- | --- | --- | | **Seq** | **Field** | **Description** | **Data type** | | | **General information** | | | | | | | Posted transaction by\*/ Tạo giao dịch bởi | Transacting Account/Customer identifier. Only one of the followings: (CIF Number, Account , Card Number) must be provided | Radio button Default posted by Card Lookup value from master data | | | | Condition fileds as following descriptions | | **Under customer management** | **Under Transaction Management** | | Card Number/Số thẻ | Any card belonging to the customer can be used for making a redemption Condition filed This field is only active and required if txn is posted by Card. | Drop -down Select one List all card of selected customer | Drop-down Select one Put any Card number in OLS system. Default emptu to avoid performance issue then user must enter at least 4 digits of Card number to find card. | | Product Account Level/Loại tài khoản | Product Account Level Condition Filed This field is only active and required if txn is posted by Account. | Drop-down Select one List distinct account level for all accounts of the choosen customer. | Drop-down Select one List all account level in the OLS system. | | Product Account Type/Hạng tài khoản | Product Account Type Condition Filed This field is only active and required if txn is posted by Account. | Drop-down Select one List distinct account types for the selected account level of the choosen customer. | Drop-down Select one List all account type in the OLS system by selected Account level. | | Account Number /Số tài khoản | Product Account Number Condition filed This field is only active and required if txn is posted by Account. | Drop-down Select one List all account number for selected account type of selected customer | Drop-down Select one List all account number for selected account type in the OLS system. Default empty to avoid performance issue then user must enter at least 4 digits of Card number to find card. | | CIF number /Số CIF | CIF number Condition filed This field is only active and required if txn is posted by Customer. | Read only This is selected CIF Number | Drop-down Select one List all CIF number in the OLS system. Default empty to avoid performance issue then user must enter at least 4 digits of CIF number to find CIF. | | | Quick view /Xem nhanh | Click on each quick view icon (Balance Detail or Buket Balance Detail View Or Expired Balance View) to retrieve the available balances of the customer after entering the card number. The details will be displayed in the right panel. See more in Quick view part Show error message if Requesting Card invalid. | Hyper link | | | | Redemption Channel \*/Kênh đổi thưởng | Redemption Channel | Drop-down Select one Lookup value from master data | | | | Redemption Date \*/Ngày đổi thưởng | The redemption transaction date | Date time Date time format must respect the date configuration format | | | | Store\*/Đơn vị | The drop-down list to select any acitive Store in the OLS. Redemption Transaciton will be logged under this store. | Drop -down Select one | | | | Appliable Fee/ Áp dụng phí | The fee will be applicable for this transaction if item has a fee See more about fee on Item price section. | Switch button Default OFF | | | **Item details** | | | | | | | Catalogue Code\*/Nhóm vật phẩm | The drop-down to select the effected catalog | Drop – down Select one Use Redemption Date to determine effected catalogue. | | | | Item\*/Vật phẩm | The drop-down to select the item code to be redeemed. The item must belong to the selected catalogue. Display an error message if item has no matched price. | Drop-down Select one Use Redemption Date and selected catalogue to determine effected item. From selected item and inputed data to determine price of the item. Please refer Item price to get more detail | | | | Redemption Mode\*/Loại đổi thưởng | A drop-down list with the following choices: * Fixed Partial (Cash + Points) * Fixed Points If Price configuration did not allow Partial Redeem then just Fixed Partial is disable. If Price configuration allow “Partial Redemption” mode then both mode are enable. | Radio button Defaut fixed points Look up value from master data | | | | Unit Price \*/Giá mỗi đơn vị | Point required **For Fixed points Mode then this is Price in point in item price configuration and user can’t change.** **For Fixed Partial Mode, the sytem must automation populate than “Minimum Partial Redeem Points” in item price configuration and user can modify this value but Unit Price must be equal to or greater than “Minimum Partial Redeem Points”.** | 9(12,2) | | | | Unit Cash Amount required./Tiền phải trả mỗi đơn vị | Condition field This field is only active and required Fixed Partial mode only. The system must automation populate as: ( **Full Price in Point – Unit Price** ) \* **Price in Cash (per point) ( from item Price Configuration)** | Display | | | | Unit Face value/Giá trị mỗi đơn vị | Condition field Active only when this item required face value on the configruration **Get face value from Item price cofiguration with higher priority. Otherwise this is base face value from item master.** | Display as 9(14,2) format | | | | Quantity on hand/Số lượng còn lại | Available item can be redeemed. Just display if the item is tracked by quantity. | Display as 9(9) format | | | | Redemption Quantity\*/Số lượng đổi thưởng | Redemption quantity If the item is tracked by quantity, then the redemption quantity must not be greater than the quantity on hand. Don’t allow to redeem if redemption quantity is greater than quantity on hand | 9(5) Should be greater than 0 if provided | | | | Total price\*/Tổng cộng | **The system must automation populate as Unit Price \* redemption quantity** | Display | | | | Total Cash amount required/Tổng tiền phải trả | Condition field This field is only active and required Fixed Partial mode only. **The system must automation populate as** **Unit Cash Amount required\* Quantity.** | Display | | | | Total face value/ Tổng giá trị | Condition field. Active only when this item required face value on the configruration **The system must automation populate as** **Unit Face value \* redemption quantity** | Display as 9(14,2) format | | | | FFP Ship number/ Mã số thẻ | FFP ship number | X(50) Condition fields Display and required for Miles items and should be configurable. Automation populate value from Attribute value based on configuration attribute ID and allow user modify this one. These fields to be used to send to partner. | | | | FFP First Name/Tên | FFP First Name | | | FFP last name /Họ | FFP last name | | | Delivery Address/Địa chỉ | Delivery Address 1 Condition field Only active for Evoucher item and Physical item Auto populate from customer’s address 1 and allow user modify. | X(100) | | | | Zip code/Mã bưu điện | Zip code Condition field Only active for Evoucher item and Physical item. Auto populate from customer’s Zip code and allow user modify. | Drop-down Select one | | | | Recipient Name/Người nhận | Recipient Name Condition field Only active and required for Evoucher item and Physical item. Auto populate from customer’s Full Name and allow user modify. | X(50) | | | | Email adress /Địa chỉ email | Email address Auto populate from customer’s email and allow user modify. | X(50) | | | | Mobile Phone/Số điện thoại | Mobile Auto populate from customer’s email and allow user modify. | X(50) | | | | Remark/ Ghi chú | Additional remarks on the item redemption transaction | X(100) | | | **Quick view** **Balance Detail View** [Image Removed] Show pool bucket balances take into account the entity level in the display. If posted txn by Card then : Show pool bucket balances take into Card considering entity level in the display: * + 1. Get all balance bucket of customer regardless selected card for customer entity- level pool. 2. Get all balance buckert of Account of the selected card for account entity-level pool 3. Get the balance bucket of the selected card only for the card entity-level pool. If posted txn by Account then : Show pool bucket balances take into Account considering entity level in the display: * + 1. Get all balance bucket of customer regardless selected Account for customer entity -level pool. 2. Get all balance of Account of selected card for account entity- level pool If posted txn by CIF number then: Get all customer – entity level pool balance bucket of chosen customer. **Noted that: Each row represent each pool which take into account the entity level in the display** **Use processing date to determine available balance which ready to be redeemed.** | | | | | | | Pool ID | Pool ID | Lookup value from LAB table | | | | Balance | Total balance buckets of a reward pool of customer. Show up to the pool entity level | Display as number format Lookup value from LAB table | | | | Redeemable Balance | The sum all non-balance buckets of a pool of customer. Show up to the pool entity level The balance bucket must be non-expired and available to use. | Display as number format Lookup value from LAB table | | | | Earliest Exp Bal and Date | The earliest expiring bucket date for a pool, for non-0 balance buckets. Show up to the pool entity level And Balance that is expiring on The earliest expiring bucket date. The balanace should not be zero balance. | Display as number format Lookup value from LAB table | | | **Bucket Balance Detail View** The same as [Balance enquiry](#_Balance_Detail_Enquiry) Display all buckets of the Pool of the customer, regardless of Entity Level | | | | | | | Account number | Product Account No | Display Present for all pool entity-level | | | | Product Account Type | Combination of Product Account Type and Product Account level of Account | | | Product Account level | | | Card Number | Card number | Display Present for Card pool entity level only If there are more than Card under the same Plastic Serial Number then the newest cards is present. | | | | Pool ID | Pool ID | Display Loopkup value from LAB table. | | | | Balance | Non zero balance | Display Loopkup value from LAB table. | | | | Expiry Date | Expring date | Display Loopkup value from LAB table | | | Expired Balance Detail This part display Expired bucket which haven’t been forfeited of selected/inputted acccout/Card/CIF. The expired pool bucket balances should take into account the entity level in the display. **If use Card to post re-instatement txn then:** * + 1. Get all expired balance buckets of customer regardless selected/inputed card for Customer entity level pool 2. Get all balance expired buckets of Account of selected/inputed card for Account entity level pool 3. Get all blance expired buckets of selected/inputed card only for Card entity level pool If **use Account to post re-instatemeen txn then:** * + 1. Get all balance expired buckets of customer regardless selected/inputed account for Customer entity- level pool 2. Get all balance expired buckets of selected/inputed account for Account entity -level pool. 3. Card pool entity-level should not be present. If **use CIF numebr to post re-instatemeen txn then** get all customer – entity level pool expired balance bucket of chosen customer. Card and account pool entity-level should not be present. Take note that: Use Processing Date to compare with expiry date to located eligible pool balance bucket. **Each row represent each pool which take into account the entity level in the display** | | | | | | | Pool ID/Mã pool | Pool ID | Display Lookup value from LAB table via selected Card/Account/Customer | | | | Balance /số dư | Total Expired balance | | | Expiry Date/Ngày hết hạn | Expiry date | | **Bucket Balance Detail view** The same as [Balance enquiry](#_Balance_Detail_Enquiry) Display all buckets of the Pool, regardless of Entity Level | | | | | | | Account number/Số tài khoản | Product Account No | Display Present for all pool entity level | | | | Product Account Type/Hạng tài khoản | Combination of Product Account Type and Product Account level of Account. | Display Present for all pool entity level | | | | Product Account level/Cấp tài khoản | | | Card Number/Số thẻ | Card number | Display Present for Card pool entity level only If found more than one Card under the same Plastic Serial Number then the newest card os present. | | | | Pool ID/Mã pool | Pool ID | Display Loopkup value from LAB table. | | | | Balance /Số dư | Non zero balance | Display Loopkup value from LAB table. | | | | Expiry Date/Ngày hết hạn | Expring date | Display Loopkup value from LAB table | | ### Post-Conditions * + 1. Transactions are logged into the related table in the database. The transaction listing includes not only transaction which to be posted under the OA but also transaction to be posted from the member site. 2. Balance are updated. Quantity on hand are updated if transaction is posted successfully in the system. 3. The net transaction of the redemption transaction is the sum of the tax amount, total fee, and total cash required. 4. At the end of day (EOD), all approved items include are output in a OLS output file to be sent to parnter to be tracking or created back to the account/customer used in the item redemption, etc. 5. TP process to approve Transaction [Image Removed] ### Exception Flow * + 1. Transaciton is rejected by TP validation such as block code validation, ATG validation… 2. Input data are not passed all validations and then user choose cancel the action then use case ends in failure. ## Award Transaction ### Requirement Definition ### Process Flow Process follow for award transaction (Award service on TP side: ) [Image Removed] ### Trigger ### Pre-Conditions ### Wireframe * + - 1. Create /Edit [Image Removed] ### Business Rules 1. Click on the “Award Transaction” tab in the “Customer Profile” screen to bring up the screen for accessing the Award Transaction Entry listing page. The detail as illustrated in the [wireframe](#_Wireframe_10). 2. Click on Add button ([Image Removed]) in the screen to bring up the edit form; clicking on the MoreOutLined icon (⋮) then click on Edit icon (!) also brings up the same edit form. The edit form for Re-Instatement screen is illustrated in the [wireframe](#_Wireframe_10). 3. Noted that Edit icon (!) and Delete icon just display for pending and rejected record only. 4. User stories and acceptance criteria [Image Removed] 1. Screen descriptions: | | | | | | --- | --- | --- | --- | | **Index** | **Field (EN/VN)** | **Descriptions** | **Data type and data source** | | | Posted transaction by\*/ Tạo giao dịch bởi | Transacting Account/Customer identifier. Only one of the following 3 (CIF Number, Account , Card Number) must be provided | Radio button Default posted by Card Lookup value from “Posted txn by” type code in master data | | | | | Condition fileds as following descriptions | | Under Customer profile | | Under Transaction Management | | Card Number/Số thẻ | Any of the customer's card numbers. Condition filed This field is only active and required if txn is posted by Card. | Drop -down Select one List all card of selected customer | Drop-down Select one Put any Card number in OLS system. Default emptu to avoid performance issue then user must enter at least 4 digits of Card number to find card. | | | Product Account Level/Loại tài khoản | Product Account Level Condition Filed This field is only active and required if txn is posted by Account. | Drop-down Select one List distinct account level for all accounts of selected customer. | Drop-down Select one List all account level in the OLS system. | | | | Product Account Type/Hạng tài khoản | Product Account Type Condition Filed This field is only active and required if txn is posted by Account. | Drop-down Select one List distinct account types for the selected account level of the selected customer. | Drop-down Select one List all account type in the OLS system by selected Account level. | | | Account Number /Số tài khoản | Product Account Number Condition filed This field is only active and required if txn is posted by Account. | Drop-down Select one List all account number for selected account type of selected customer | Drop-down Select one List all account number for selected account type in the OLS system. Default empty to avoid performance issue then user must enter at least 4 digits of Account number to find card. | | | CIF number /Số CIF | CIF number Condition filed This field is only active and required if txn is posted by Customer. | Read only This is selected CIF Number | Drop-down Select one List all CIF number in the OLS system. Default empty to avoid performance issue then user must enter at least 4 digits of CIF number to find CIF. | | | | Quick view | Click on each quick view icon “Balance” to retrieve the available balances of the customer after entering the card/account/CIF number. The details will be displayed in the right panel. See more in Quick view part With Edit/Create mode the system will expand / collapse on the same screen to user can see and continue input needed information as illustrated following: [Image Removed] With View/Approve/Reject mode the system will show detail as pop-up when click on each quick view icon as illustrated following: [Image Removed] | Hyperlink | | | | | Transaction Code\* /Mã giao dịch | OLS Transaction Code This TC is used to locate the Campaign Rule to use for processing. | Drop-down Select one Lookup value from “Transaction\_Code” table. Refer “OLS Transaction Code” API under Campagin Management | | | | | Transaction Date \*/Ngày giao dịch | Must be valid date. Transaction rejected if not valid. Transaction rejected if this date is older than sysdatetime by N days, where N is a system setting. | Date time | | | | | Source Reference Number/Số giao dịch gốc | Source Transaction Reference Number Unique transaction identifier from source system | X(20) | | | | | Store\*/Đơn vị/Cửa hàng | Transaction Store Id | Drop-down Select one Lookup value from “Store” table Refer “Store” API under merchant management | | | | | Terminal /Thiết bị đầu cuối | Transaction Terminal Id | Drop-down Select one Lookup value from “Terminal” table Refer “Terminal” API under merchant management | | | | | Transaction Amount\*/ Giá trị giao dịch | Transaction Gross amount Note: It is dependent on each project, Lets it be gross transaction amount first. | 9(14,2) Should be greater than 0 if provided | | | | | Transaction Description/ Mô tả giao dịch | Shopname from Source system or OLS transaction description | X(100) | | | | | Transaction Currency Code/ Mã tiền tệ giao dịch | It can be anpha code or number code. Let’s it be anpha code first | Drop-down Select one Lookup data from “Currency\_code” table Refer “Currency Code” API under Code Maintenance | | | | | Transaction Mode/Phương thức giao dịch | Mode of transaction at point of payment | Radio button Lookup value from “Code\_Management” table where code type is “txn-mode’. Refer “get-by-code-type” API under master data | | | | | POS Entry Mode/Phương thức thiết bị bán hàng | POS Entry Mode | X(04) This field is subdivided as follows: 0 – Unknow , 1- Manual (key entered) 3- Bar code ---Etc | | | | | MCC code/Mã MCC | Merchant category code | Drop-down Select one Lookup value from “MCC” table Refer “MCC” API under merchant management | | | | | Country Code/Mã quốc gia | Country code | Drop-down Select one Lookup value from “Country\_Code” table Refer “country code”API under Code Maintenance | | | | | Salary Crediting Indicator/ Tài khoản nhận lương | Indicates bundled deposit account is receiving regular salary credits | Switch button Default OFF | | | | | Transaction Channel/Kênh giao dịch | Transaction channel | Drop-down Select one Lookup value “Code\_Management” table where type code is “txn-channel” Refer “get-by-code-type” API under master data | | | | **Quick view** **Balance Detail View** [Image Removed] Show pool bucket balances take into account the entity level in the display. If posted txn by Card then : Show pool bucket balances take into Card considering entity level in the display: * + 1. Get all balance bucket of customer regardless selected card for customer entity- level pool. 2. Get all balance buckert of Account of the selected card for account entity-level pool 3. Get the balance bucket of the selected card only for the card entity-level pool. If posted txn by Account then : Show pool bucket balances take into Account considering entity level in the display: * + 1. Get all balance bucket of customer regardless selected Account for customer entity -level pool. 2. Get all balance of Account of selected card for account entity- level pool 3. Card pool –entity level should not be present. If posted txn by CIF number then: Get all customer – entity level pool balance bucket of chosen customer. Card and account pool entity-level should not be present. **Noted that: Each row represent each pool which take into account the entity level in the display** **Use processing date to determine available balance which ready to be redeemed.** | | | | | | | | Pool ID | Pool ID | Lookup value from LAB table | | | | | Balance | Total balance buckets of a reward pool of customer. Show up to the pool entity level | Display as number format Lookup value from LAB table | | | | | Redeemable Balance | The sum all non-balance buckets of a pool of customer. Show up to the pool entity level The balance bucket must be non-expired and available to use. | Display as number format Lookup value from LAB table | | | | | Earliest Exp Bal and Date | The earliest expiring bucket date for a pool, for non-0 balance buck Show up to the pool entity level And Balance that is expiring on The earliest expiring bucket date. The balanace should not be zero balance. | Display as number format Lookup value from LAB table | | | ### Post-Codition Refer Process flow to get more detail for post-conditon when transaction is approved. ### Exception -flow * + 1. Transaciton is rejected by TP validation such as block code validation, ATG validation. 2. Input data are not passed all validations and then user choose cancel the action then use case ends in failure.