2.12.2 Description

This topic provides a description of the number generation – statement, customer, business, vendor and producer.

  • Added a new set of lookups to Existing Number Generation Entities as Statement, Customer Number, Vendor, and Producer:
    • Deprecated the following system parameters:
      • UPR_PRO_NBR_SYS_GENERATED PRODUCER NUMBER IS SYSTEM GENERATED
      • UVN_VEN_NBR_SYS_GENERATED VENDOR NUMBER IS SYSTEM GENERATED
      • SYP_AUTO_GEN_BUS_NBR AUTO GENERATE BUSINESS NUMBER FOR CONVERSION PROCESS
      • SYP_AUTO_GEN_CUS_NBR – This parameter still exists, considering the dependency on the Account Onboarding service.
  • By default, the system refers to the configuration, and if it finds a match, it will follow the Number Gen Configuration; otherwise, it will follow the default logic.

Table 2-28 Entity

Entity Impact handled
Customer / Business

User Interface:

  • Funding
  • Transaction posting (add new customer)

Web Service:

  • Account On-boarding.
  • Asynchronous Account On-boarding
  • Conversion (old and new)
  • Application status change
Vendor User Interface and Web Service
Producer User Interface and Web Service
Statement Batch and Backdated Funding/Account Onboarding
  1. Number Generation Setup Changes (common):
    • Provided a new User Defined record as Producer Number, Vendor Number, Statement ID, Business Number and Customer Number.
    • For all these except Statement, Channel becomes read only with the default value 'ALL'.
    • On click of Validate sequence, system validates, Account Number, Application Number and External Application Number not applicable for "Producer, and Vendor Number" entities.
    • On click of Validate sequence, system validates, Cross-Reference Number, Account Number, Application Number and External Application Number not applicable for "Business", and "Customer Number" entities.
    • Existing = Note: System sequence is mandatory if 'Cross-Reference Number' is not enabled. If Cross-Reference Number' is enabled, then System sequence is not mandatory.
  2. Producer and Vendor number Generation process:
    • Currently, if a user try to Add a new record in User Interface, the system will make Producer and Vendor editable when the parameter = 'Y'. After this change, the system always keeps the filed as editable with a default value as ' UNDEFINED' as existing.
    • While saving the record, system checks if the value is "UNDEFINED", then looks for the setup. If it found, then generate with setup logic, else go ahead with default i.e., <state code>-00001.
    • If the value is not "UNDEFINED", then validate the uniqueness and create it - this is existing.
  3. Statement Number Generation Process (Similar to account number):
    • Setup:
      • System does not allow to enable the record with 'External Application Number' unit, if user enables it shows an error, 'External Application Number unit is not applicable for Statement Entity'.
      • Provided a new Unit 'Account Number'. This unit is only applicable for 'Statement' alone. While enabling the definition, validates and shows, 'Account Number unit is applicable only for Statement Entity':
        • Here, system considers the Sample Number of Account Number = 'ACCNUM1001' i.e., Length should be 10. Validates the total length of characters by considering 10 for the account number.
      • User allows to create record with a different company, branch, and channel combination:
        • Here, the company, branch, and channel is considered for the corresponding Account's details for the statement number.
    • While the statement gets generated, system looks into the setup and if system finds a matching definition in the combination of company, branch, and channel, then the Statement Id gets generated else, the system will go with default logic i.e., NULL.
  4. Customer Number and Business Number Generation Process:
    • Setup:
      • Company and Branch are allowed only as 'ALL' for Customer and Business Numbers.

        Note:

        Below is the summary of how User Interface behaves while adding the record:

        While editing, "Entity"should always be read-only for all entities.

        While editing, "Entity"is always read-only for all entities.

        Table 2-29 Entity

        Entity Company Branch Channel
        Producer Editable Editable Read Only
        Vendor Editable Editable Read Only
        Customer Read Only Read Only Read Only
        Business Read Only Read Only Read Only
        Statement Editable Editable Editable
        Account Editable Editable Editable
        Application Editable Editable Editable
  5. Web service Impact:
    • Account GET service have new tags → Statement Block→ Statement, Coverage Start & End Date.