Previous
3.5.2 Result Messages
Inside the element <resultMessages> (described above) there may be zero, one or more result messages. The purpose of these messages is to clarify why a request message was not processed successfully. The message text contains the message text in which the substitution parameters have been set.
For example, the Claims In Integration Point's response message to a request message which failed to process successfully could contain :
<resultMessages result='F'>
<resultMessage code='CLA-IP-CLAI-010'>
CLA-IP-CLAI-010: The specified product code ABC is unknown
</resultMessage>
</resultMessages>
Result messages are common or specific:
- Integration Point Specific messages can only occur in the response of a specific Integration Point. Such messages are described in the description of the concerned Integration Point. The example above shows a result message specific to the Claims In Integration Point.
- Messages common across Integration Points can occur in the responses of many Integration Points. These messages relate to common functionality, like the use of dynamic fields. These message are described below.
Messages common across Integration Points:
|
Code |
Severity |
Message |
|---|---|---|
|
GEN-ACRE-001 |
Fatal |
Access restriction code {code} is unknown. Request cannot be processed |
|
GEN-TRAS-001 |
Fatal |
A reference may only be provided in combination with a transaction source |
|
GEN-TRAS-002 |
Fatal |
Transaction source code {code} is unknown |
|
GEN-CURR-001 |
Fatal |
Currency code {code} is unknown |
|
GEN-DYNA-001 |
Fatal |
The dynamic field: {dynamicFieldUsageName} should have unique values. There is already a record with value: {value} |
|
GEN-DYNA-002 |
Fatal |
{dynamicFieldUsageName}: There is already a value present in this period of time ({startDate} - {endDate}) |
|
GEN-DYNA-003 |
Fatal |
Cannot insert same value for the flex code in case the dynamic field is multivalue |
|
GEN-DYNA-004 |
Fatal |
Dynamic field {dynamicFieldUsageName} is not time valid. Request cannot be processed |
|
GEN-DYNA-005 |
Fatal |
Dynamic field {dynamicFieldUsageName} may have only one single value. Request cannot be processed |
|
GEN-DYNA-006 |
Fatal |
Dynamic field flex code definition code {code} is unknown. Request cannot be processed |
|
GEN-DYNA-007 |
Fatal |
The flex code {code} is unknown to dynamic field {dynamicFieldUsageName}. Request cannot be processed |
|
GEN-DYNA-008 |
Fatal |
Dynamic field name {dynamic field usage name} is unknown. Request cannot be processed |
|
GEN-DYNA-010 |
Fatal |
{dynamicFieldUsageName} should have a value and a {startDate} |
|
GEN-DYNA-011 |
Fatal |
{dynamicFieldUsageName} value {value} does not belong to flex code definition {code} |
|
GEN-DYNA-012 |
Fatal |
{dynamicFieldUsageName}: the same value {value} is present in another period ({startDate} - {endDate}) |
|
GEN-DYNA-013 |
Fatal |
Only one value allowed for {dynamicFieldUsageName} |
|
GEN-DYNA-015 |
Fatal |
The field {dynamicFieldUsageName} is not allowed to be empty |
|
GEN-DYNA-016 |
Fatal |
Dynamic Record Definition with type {dynamicFieldUsageName} could not be found |
|
GEN-DYNA-017 |
Fatal |
Dynamic record definition {dynamicFieldUsageName} does not define field {flexCodeFieldUsageCode} |
|
GEN-DYNA-018 |
Fatal |
Usage {dynamicFieldUsageName} can only have a record when the condition defined evaluates to true |
|
GEN-DYNA-019 |
Fatal |
Usage {dynamicFieldUsageName} should have at least one record |
|
GEN-DYNA-020 |
Fatal |
Key field {flexCodeFieldUsageCode} should have unique value for Dynamic record {dynamicFieldUsageName} |
|
GEN-DYNA-021 |
Fatal |
Dynamic Records should specify the value for key field. Dynamic Record {dynamicFieldUsageName} does not specify value for key {flexCodeFieldUsageCode} |
|
GEN-DYNA-022 |
Fatal |
Dynamic record {dynamicFieldUsageName} is not time valid. Request cannot be processed |
|
GEN-PROC-001 |
Fatal |
Value provided is not of type Date |
|
GEN-PROC-002 |
Fatal |
Value provided is not of type Number |
Besides these messages, business rule messages may also occur in the responses of Integration Points. Business rule messages are raised in the validation layer of OHI Components applications and are common to both the User Interface Pages and the Integration Points. For example, business rule GEN-TMVL-001: "The start date should lie before the end date for {dynamicFieldUsageName}".
Lastly, technical error messages may be returned through the responses of Integration Points. For example, database message GEN-ORA-01400: "DESCR" column is mandatory for table "PRI_FEE_SCHEDULES".