Creating Local Reference Fields in T24
Uploaded by
MrCHANTHA- Introduction to Local Reference Fields
- Learning Objectives
- Understanding Local Reference Fields
- Creating Local Reference Fields
- Configuring the LOCAL.TABLE Application
- Using the LOCAL.REF.TABLE
- Standard Selection and Field Permissions
- Testing the Local Field
- Complex Conditions in LOCAL.TABLE
- Workshop
- Quiz
- Summary
- Review
- Conclusion
Common questions
Powered by AIThe LOCAL.TABLE application is used for creating the Local Reference Field and setting its properties, such as the field description, name, character limits, and data type. Once the field is defined, the LOCAL.REF.TABLE application links the created field to a specific T24 application. This involves specifying the application name and indicating if the field is part of a multi-value set, ensuring the field integrates seamlessly without altering the core application structure .
When creating a multi-value Local Reference Field in T24, one must define the field as part of an associated multi-value set using SUB.ASSOC.CODE, denoting beginning, part, or end of the set. Consideration must also be given to character restrictions and whether the field is mandatory. The maximum number of characters is set using MAXIMUM.CHAR, and if MINIMUM.CHAR is defined, the field becomes mandatory. Care is needed to ensure proper linkage and formatting without disrupting existing fields, as changes to their order can invalidate the configuration .
The OVERRIDE.POSSIBLE field allows input that does not meet set decision criteria to be accepted, but with a warning. If set to 'Y', the system prefixes non-compliant input with 'OV!' and prompts for an override. This function is crucial for flexibility in data entry, where strict adherence to rules may not accommodate every real-world scenario, thus balancing system integrity with user adaptability .
The VETTING.TABLE allows for predefined value constraints, providing a list of acceptable input options for a Local Reference Field. This feature helps enforce consistent data entry, reduces input errors, and supports controlled data environments by limiting user input to known and authorized values. While not mandatory, its use is vital in situations demanding high data accuracy and consistency, especially in regulated domains .
The main constraint when adding new Local Reference Fields in existing T24 applications is the inability to insert new fields between existing ones due to fixed order requirements. Additionally, once created, Local Reference Fields cannot be deleted, so careful planning is essential to avoid future data structure issues. These constraints necessitate thorough upfront design and validation to ensure the fields meet all current and foreseeable needs .
The USR.TYPE field in the STANDARD.SELECTION application, set to 'I', identifies the Local Reference Field as an I-descriptor field. This designation indicates that the field is not physically stored under the same name in the database and affects how the field data is processed and displayed. It helps manage user-defined fields without altering the database structure, thus maintaining consistency and system integrity .
Decision criteria in Local Reference Fields are defined using several fields from the LOCAL.TABLE application. The DECIS.FIELD specifies which application field's value should be checked, while REPLACE.FILE and REPLACE.FIELD enable conditional logic by referencing related application fields. The DECISION field determines the operation against the related field, and DECISION.FR and DECISION.TO specify valid value ranges. These criteria control whether a user must input values that meet predefined conditions, or if an override is permitted, enabling complex validation logic .
Improper configuration of Local Reference Fields in a banking application can lead to data integrity issues such as incorrect data capture, loss of critical information, or validation failures, impacting both operational efficiency and regulatory compliance. Misconfigurations may also disrupt existing workflows, hinder data analysis, and lead to increased maintenance overhead. Thorough testing and validation are vital to mitigate these risks and ensure seamless operation .
Local Reference Fields in T24 are primarily used to allow banks to record extra information specific to their needs without altering the standard application code, catering to individual client environments while ensuring the application remains consistent for all users. This customization is essential as it lets banks add fields that are not universally required, thereby providing flexibility and local adaptation .
Setting a Local Reference Field as mandatory in T24 means that users must input a value for this field during the data entry process. This is controlled by defining a minimum character count in the MINIMUM.CHAR field. The implications include ensuring data completeness and consistency for records containing this field. However, this also increases the burden on users to provide necessary input, which may require changes in business processes to accommodate data capture .
