| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Designing: MFVR Errors |
|
| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Designing: MFVR Errors |
|
Creating a Runtime Environment
Designing Business Processes in the Sun Business Process Manager
Working with TCP/IP HL7 Collaborations
Developing Sun Master Indexes (Repository)
Developing Sun Master Patient Indexes
Developing OTDs for Application Adapters
Developing OTDs for Communication Adapters
Developing OTDs for Database Adapters
Developing OTDs for Web Server Adapters
Designing with Application Adapters
Designing with Communication Adapters
Designing with Web Server Adapters
Overview of SWIFT Message Libraries
What's New in Java CAPS 6 Update 1
Installing the SWIFT Message Library
SWIFT OTD Library System Requirements
Installing the SWIFT OTD Libraries
Installing the eWay on a Java CAPS Supported System
Increasing the heap size from the Enterprise Designer
OTD and Collaboration Locations in Enterprise Designer
SWIFT Message Library JAR Files
Using Message Validation Features
Message Format Validation Rules (MFVR)
In Collaboration Validation Methods
SWIFT Projects and the Enterprise Designer
SWIFT Sample prjSwift_JCD_MFVROnly Project
SWIFT Sample prjSwift_JCD_MFVRAndBICPlusIBAN Project
SWIFT Sample prjSwift_JCD_BICPlusIBANOnly Project
SWIFT Correlation Repository Sample
SWIFT Sample eInsight™ Project
Configuring the Modeling Elements
Configuring the Integration Server
Creating the Deployment Profile
Creating and Starting the Domain
Building and Deploying the Project
BICDirService Method Operation
BICPlusIBAN Validation Method Definitions
Using SWIFT FIN-Based Funds OTDs
SWIFT OTD Library Funds Features
Using SWIFT OTD Library Java Classes
Designing with Sun JCA Adapters
These errors result from the application of the Semantic Validation Rules. Multiple errors are possible, and they are given in the order in which they occurred and with the sequences, fields, or subfields used to determine them.
For example, an MFVR failure on a 535 Collaboration OTD appears as follows:
MFVR MT535 Error
SVR Rule 103 - Error code: D031001 = Since field :94a:: is present
in Sequence B, then fields :93B::AGGR and :94a::SAFE are not
allowed in any occurrence of Subsequence B1a.mt_535.Mt_535.Data[1].
SubSafekeepingAccount mt_535.Mt_535.Data[1].SubSafekeepingAccount[0].
SubSeqB1[0].SubSeqB1a.Balance
SVR Rule 104 - Error code: D04-1001 = Since field :93B::
AGGR is present in Subsequence B1a,then
:field 94a::SAFE must be present in the same Subsequence B1a.
mt_535.Mt_535.Data[1].SubSafekeepingAccount[0].SubSeqB1[0].
SubSeqB1a.Balance
For more information on error messages, see Error Message Information.
|