To transform the sample tables into the format required by the content validation node in Business Rules, a set of database views is required. The binary tables used by Business Rules
cannot be edited directly. The database views provide a way to combine the database tables that the user
edited with the Business Rules user interface and the binary tables used by Business Rules at run time.
X9_VAL_CONTENT_GLOBAL_V database view
For the X9 set of edits, the X9_VAL_CONTENT_GLOBAL_V database view (
Table 1) joins the X9_VAL_CONTENT_GLOBAL, X9_VAL_FIELDS,
and ERROR_CODES tables to provide the data for the content validation required fields. See
Content
validation table record layout for more information about the required fields.
Table 1. X9_VAL_CONTENT_GLOBAL_V view definition
| Field name |
Source table |
Source column |
| ibmFileFormat |
X9_VAL_CONTENT_GLOBAL |
DATA_TYPE |
| ibmNprRecordType |
X9_VAL_CONTENT_GLOBAL |
RECORD_TYPE |
| ibmValRecordRuleNum |
Automatically generated by the view as a sequential
counter |
| ibmValFieldNum |
X9_VAL_CONTENT_GLOBAL |
FIELD_NUMBER |
| ibmValFieldReq |
X9_VAL_CONTENT_GLOBAL |
EDIT_REQUIRED |
| ibmValFixedPos |
X9_VAL_FIELDS |
FIXED_FIELD_POS |
| ibmValFixedLen |
X9_VAL_FIELDS |
FIXED_FIELD_LEN |
| ibmValVarPos |
X9_VAL_FIELDS |
FIXED_FIELD_POS |
| ibmValVarLen |
X9_VAL_FIELDS |
FIXED_FIELD_LEN |
| ibmValMandatory |
X9_VAL_CONTENT_GLOBAL |
MANDATORY |
| ibmValMandErrorCode |
X9_VAL_FIELDS |
MANDATORY_ERR_CODE |
| ibmValMandReject |
ERROR_CODES |
REJECT |
| ibmValMandOverride |
ERROR_CODES |
OVERRIDE |
| ibmValType |
X9_VAL_FIELDS |
TYPE |
| ibmValTypeErrorCode |
X9_VAL_FIELDS |
TYPE_ERR_CODE |
| ibmValTypeReject |
ERROR_CODES |
REJECT |
| ibmValTypeOverride |
ERROR_CODES |
OVERRIDE |
| ibmValFormat |
X9_VAL_FIELDS |
FORMAT |
| ibmValFormatErrorcode |
X9_VAL_FIELDS |
FORMAT_ERR_CODE |
| ibmValFormatReject |
ERROR_CODES |
REJECT |
| ibmValFormatOverride |
ERROR_CODES |
OVERRIDE |
| ibmValValues1 |
X9_VAL_CONTENT_GLOBAL |
VALUES1 |
| ibmValValues2 |
X9_VAL_CONTENT_GLOBAL |
VALUES2 |
| ibmValValues3 |
X9_VAL_CONTENT_GLOBAL |
VALUES3 |
| ibmValValues4 |
X9_VAL_CONTENT_GLOBAL |
VALUES4 |
| ibmValValues5 |
X9_VAL_CONTENT_GLOBAL |
VALUES5 |
| ibmValValueErrorCode |
X9_VAL_FIELDS |
VALUE_ERR_CODE |
| ibmValValueReject |
ERROR_CODES |
REJECT |
| ibmValValueOverride |
ERROR_CODES |
OVERRIDE |
| ibmValJJustification |
X9_VAL_CONTENT_GLOBAL |
JUSTIFICATION |
| ibmValJustification2 |
X9_VAL_CONTENT_GLOBAL |
JUSTIFICATION2 |
| ibmValJustificationErrorCode |
X9_VAL_FIELDS |
JUSTIFICATION_ERR_CODE |
| ibmValJustificationReject |
ERROR_CODES |
REJECT |
| ibmValJustificationOverride |
ERROR_CODES |
OVERRIDE |
| ibmValJustification2ErrorCode |
X9_VAL_FIELDS |
JUSTIFICATION2_ERR_CODE |
| ibmValJustification2Reject |
ERROR_CODES |
REJECT |
| ibmValJustification2Override |
ERROR_CODES |
OVERRIDE |
| ibmValValue1ErrorCode |
X9_VAL_FIELDS |
VALUE1_ERR_CODE |
| ibmValValue1Reject |
ERROR_CODES |
REJECT |
| ibmValValue1Override |
ERROR_CODES |
OVERRIDE |
| ibmValValue2ErrorCode |
X9_VAL_FIELDS |
VALUE2_ERR_CODE |
| ibmValValue2Reject |
ERROR_CODES |
REJECT |
| ibmValValue2Override |
ERROR_CODES |
OVERRIDE |
| ibmValValue3ErrorCode |
X9_VAL_FIELDS |
VALUE3_ERR_CODE |
| ibmValValue3Reject |
ERROR_CODES |
REJECT |
| ibmValValue3Override |
ERROR_CODES |
OVERRIDE |
| ibmValValue4ErrorCode |
X9_VAL_FIELDS |
VALUE4_ERR_CODE |
| ibmValValue4Reject |
ERROR_CODES |
REJECT |
| ibmValValue4Override |
ERROR_CODES |
OVERRIDE |
| ibmValValue5ErrorCode |
X9_VAL_FIELDS |
VALUE5_ERR_CODE |
| ibmValValue5Reject |
ERROR_CODES |
REJECT |
| ibmValValue5Override |
ERROR_CODES |
OVERRIDE |
Notes:
- The reject and override values for each error code are obtained by joining the error code column of the
error codes table with the appropriate error code column from X9 fields. The various reject and override
columns may contain different values.
- The X9 fields table is joined to itself using the variable length field number column. The ibmValFixedPos
and ibmValFixedLen fields are the result.
|
X9_VAL_CONTENT_FORWARD_V database view
The X9_VAL_CONTENT_FORWARD_V database view (
Table 2) joins the X9_VAL_FORWARD_RULES_MAP,
X9_VAL_CONTENT_FORWARD, X9_VAL_FIELDS, and ERROR_CODES tables to provide the data for the content validation
required fields, context validation required fields, and the view in
Table 1. See
Content validation table record
layout and
Context validation table record layout for more information about the content
and context validation required fields.
Table 2. X9_VAL_CONTENT_FORWARD_V view definition
| Field name |
Source table |
Source column |
| ibmValCollectType |
X9_VAL_FORWARD_RULES_MAP |
COLLECTION_TYPE |
Note: The remaining fields for this view are the same as the fields in the X9_VAL_CONTENT_GLOBAL view ( Table 1). However, the fields that have
X9_VAL_CONTENT_GLOBAL as the source table in the X9_VAL_CONTENT_GLOBAL_V view have a source table of
X9_VAL_CONTENT_FORWARD in this view.
|
X9_VAL_CONTENT_RETURN_V database view
The X9_VAL_CONTENT_RETURN_V database view (
Table 3) joins the X9_VAL_RETURN_RULES_MAP,
X9_VAL_CONTENT_ RETURN, X9_VAL_FIELDS, and ERROR_CODES tables to provide the data for the content validation
required fields and the view in
Table 1. See
Content validation table record layout for more information about the required fields.
Table 3. X9_VAL_CONTENT_RETURN_V view definition
| Field name |
Source table |
Source column |
| ibmValCollectType |
X9_VAL_RETURN_RULES_MAP |
COLLECTION_TYPE |
Note: The remaining fields for this view are the same as the fields in the X9_VAL_CONTENT_GLOBAL view ( Table 1). However, the fields that have
X9_VAL_CONTENT_GLOBAL as the source table in the X9_VAL_CONTENT_GLOBAL_V view have a source table of
X9_VAL_CONTENT_RETURN in this view.
|
X9_CONTENT_PRODUCT_V database view
The X9_CONTENT_PRODUCT_V database view (
Table 4) joins the X9 product content rules, X9
fields, and error code tables to provide the data for the content validation required fields and
Table 1. See
Content validation table record
layout for more information about the required fields.
Table 4. X9_CONTENT_PRODUCT_V view definition
| Field name |
Source table |
Source column |
| ibmValProductId |
X9_VAL_CONTENT_PRODUCT |
PRODUCT_CODE |
Note: The remaining fields for this view are the same as the fields in the X9_VAL_CONTENT_GLOBAL view ( Table 1). However, the fields that have
X9_VAL_CONTENT_GLOBAL as the source table in the X9_VAL_CONTENT_GLOBAL view have a source table of
X9_VAL_CONTENT_PRODUCT in this view.
|
X9_DEPOSITOR_CONTENT_V database view
The X9_DEPOSITOR_CONTENT_V database view (
Table 5) joins the X9 depositor content rules, X9
fields, and error code tables to provide the data for the content validation required fields and
Table 1. See
Content validation table record
layout for more information about the required fields.
Table 5. X9_DEPOSITOR_CONTENT_V view definition
| Field name |
Source table |
Source column |
| ibmValDepositorId |
X9_VAL_CONTENT_DEPOSITOR |
DEPOSITOR |
Note: The remaining fields for this view are the same as the fields in the X9_VAL_CONTENT_GLOBAL view ( Table 1). However, the fields that have
X9_VAL_CONTENT_GLOBAL as the source table in the X9_VAL_CONTENT_GLOBAL view have a source table of
X9_VAL_CONTENT_DEPOSITOR in this view.
|
X9_ORIGINATOR_CONTENT_V database view
The X9_ORIGINATOR_CONTENT_V database view (
Table 6) joins the X9 originator content rules, X9
fields, and error code tables to provide the data for the content validation required fields and
Table 1. See
Content validation table record
layout for more information about the required fields.
Table 6. X9_ORIGINATOR_CONTENT_V view definition
| Field name |
Source table |
Source column |
| ibmValProcessor |
X9_VAL_CONTENT_ORIGINATOR |
ORIGINATOR |
Note: The remaining fields for this view are the same as the fields in the X9_VAL_CONTENT_GLOBAL view ( Table 1). However, the fields that have
X9_VAL_CONTENT_GLOBAL as the source table in the X9_VAL_CONTENT_GLOBAL view have a source table of
X9_VAL_CONTENT_ORIGINATOR in this view.
|
NACHA_VAL_CONTENT_SPEC_V database view
The NACHA content spec database view (
Table 7) is based on the X9 content rules view (
Table 1). It has the following additional keys:
- Standard Entry Class Code
- Addenda Type Code
It also has the following additional payload:
Table 7. NACHA_VAL_CONTENT_SPEC_V view definition
| Field name |
Source table |
Source column |
| ibmAchSecCode |
NACHA_VAL_CONTENT_SPEC |
SEC_TYPE |
| ibmAchAddendaType |
NACHA_VAL_CONTENT_SPEC |
ADDENDA_TYPE |
| ibmValFwdRtnIndicator |
NACHA_VAL_CONTENT_SPEC |
FWD_RTN_INDICATOR |
Note: The remaining fields for this view are the same as the fields in the X9_VAL_CONTENT_GLOBAL view ( Table 1). However, the fields that have
X9_VAL_CONTENT_GLOBAL as the source table in the X9_VAL_CONTENT_GLOBAL view have a source table of
NACHA_VAL_CONTENT_SPEC in this view.
|
NACHA_VAL_CONTENT_PRODUCT_V database view
The NACHA product content database view has the same layout as the NACHA content spec view (
Table 7) as a base, and then adds the fields shown
in
Table 8.
Table 8. NACHA_VAL_CONTENT_PRODUCT_V view definition
| Field name |
Source table |
Source column |
| ibmValProductId |
NACHA_VAL_CONTENT_PRODUCT |
PRODUCT_CODE |
NACHA_VAL_CONTENT_DEPOSITOR_V database table
The NACHA depositor content database view has the same layout as the NACHA content spec view (
Table 7) as a base, and then adds the fields shown
in
Table 9.
Table 9. NACHA_VAL_CONTENT_DEPOSITOR_V view definition
| Field name |
Source table |
Source column |
| ibmValDepositorId |
NACHA_VAL_CONTENT_DEPOSITOR |
DEPOSITOR |
NACHA_VAL_CONTENT_ORIGINATOR_V database view