C
Error Codes

This appendix lists error messages and causes that are specific to operation of Oracle Application Server ProcessConnect.

This appendix contains these topics:

AIP-10000 to AIP-10438 Runtime Error Codes

AIP-10000 thread execution error in thread "{0}": Cause: An internal error occurred. Contact Oracle Support Services.
AIP-10001 No role processor was found to process the given event instance.: Cause: The associations for the given event instance are not correct. So we cannot assign a role processor to process this event.
AIP-10002 event instance of invalid event type: Cause: The event instance has either invalid or no event type associated.
AIP-10003 event instance in wrong state for role processor: Cause: The event instance is not in RAISED or WAIT state, so it cannot be processed by some role processor.
AIP-10004 invalid bootstrap context: Cause: The context is of wrong type for this bootstrap.
AIP-10005 no bootstrap context: Cause: Attempt to start a runtime component without a context.
AIP-10006 operation not supported: Cause: The runtime factory tried to create a not yet supported object.
AIP-10010 failed to get JDBC connection from repository service: Cause: The JDBC connection could not be retrieved from the repository service.
AIP-10011 A SQL error occurred while accessing the databus.: Cause: The databus cannot be accessed because of a SQL error.
AIP-10012 A JMS error occurred while accessing the databus.: Cause: The databus cannot be accessed because of a JMS error.
AIP-10013 A SQL error occurred while pushing a token to the databus.: Cause: Failed to push an event token to the databus because of a SQL error.
AIP-10014 A JMS error occurred while pushing a token to the databus.: Cause: Failed to push an event token to the databus because of a JMS error.
AIP-10015 A SQL error occurred while retrieving a token from the databus.: Cause: Failed to retrieve an event token from the databus because of a SQL error.
AIP-10016 A JMS error occurred while retrieving a token from the databus.: Cause: Failed to retrieve an event token from the databus because of a JMS error.
AIP-10017 No event instance was found for the given token.: Cause: An internal error occurred in event manager. Contact Oracle Support Services.
AIP-10018 cannot retrieve an event instance for the given token: Cause: An internal error occurred in event manager. Contact Oracle Support Services.
AIP-10050 invalid sensor type: Cause: An internal error occurred. Contact Oracle Support Services.
AIP-10051 invalid state sensor type: Cause: An internal error occurred. Contact Oracle Support Services.
AIP-10052 No DMS process name was specified.: Cause: The DMS spy requires a process name to be specified.
AIP-10053 spy configuration error: Cause: A configuration error occurred while initializing the DMS spy.
AIP-10054 spy publisher error: Cause: A publisher error occurred while initializing the DMS spy.
AIP-10055 system monitor manager not initialized: Cause: The system monitor manager must be initialized before creating a system monitor.
AIP-10070 system log manager not initialized: Cause: The system log manager must be initialized before creating individual system loggers.
AIP-10071 error deleting from the system log: Cause: An internal error occurred in system log manager. Contact Oracle Support Services.
AIP-10072 error updating the system log: Cause: An internal error occurred in system log manager. Contact Oracle Support Services.
AIP-10073 error selecting from the system log: Cause: An internal error occurred in system log manager. Contact Oracle Support Services.
AIP-10074 error truncating the system log: Cause: An internal error occurred in system log manager. Contact Oracle Support Services.
AIP-10100 The event manager failed to update an event instance.: Cause: Failed to update an event instance because of a business logic layer error.
AIP-10101 The event manager failed to update an event instance.: Cause: Failed to update an event instance because of a data validation error.
AIP-10102 The event manager failed to update an event instance.: Cause: Failed to update an event instance because of an optimistic lock error.
AIP-10103 The event manager failed to update an event instance.: Cause: Failed to update an event instance because of an object not found error.
AIP-10104 The event manager failed to update an event instance.: Cause: Failed to update an event instance because of a uniqueness violation error.
AIP-10105 adapter framework instance not set: Cause: The event manager has no adapter framework instance; use the activate method to do this.
AIP-10106 The event manager is already activated.: Cause: The event manager is already activated. Passivate it before you activate it again.
AIP-10107 The event manager is not active.: Cause: The event manager is not active. Activate it first before passivating it.
AIP-10108 The event manager failed to create an event instance.: Cause: Failed to create an event instance because of a business logic layer error.
AIP-10109 The event manager failed to complete the creation of an event instance.: Cause: Failed to complete the creation of an event instance because of missing data.
AIP-10110 The event manager failed to copy an event instance.: Cause: Failed to copy an event instance.
AIP-10111 The event manager failed to raise an event instance.: Cause: Failed to raise an event instance. It is likely that there is an error putting an event token on the databus.
AIP-10112 The event manager failed to get a JDBC connection from the repository service.: Cause: Failed to get a JDBC connection from the repository.
AIP-10113 The event manager failed to create subscriber "{0}" because of a SQL error.: Cause: Failed to create subscriber "{0}" because of a SQL error.
AIP-10114 The event manager failed to create subscriber "{0}" because of a JMS error.: Cause: Failed to create subscriber "{0}" because of a JMS error.
AIP-10115 The event manager failed to create subscriber "{0}".: Cause: Failed to create subscriber "{0}" because no parties were found for the given adapter framework instance.
AIP-10116 The event manager failed to create subscriber "{0}".: Cause: Failed to create subscriber "{0}" because query for parties failed.
AIP-10117 The event manager failed to get the adapter framework instance for ID "{0}".: Cause: Failed to get the adapter framework instance with ID "{0}".
AIP-10118 The event manager failed to get an adapter framework instance for ID "{0}".: Cause: Failed to get the adapter framework instance with ID "{0}".
AIP-10119 The event manager cannot raise an event of state "{1}".: Cause: An internal error occurred in event manager. Contact Oracle Support Services.
AIP-10120 The event manager cannot raise an event with a from role set.: Cause: An internal error occurred in event manager. Contact Oracle Support Services.
AIP-10121 The event manager cannot raise an event with no current role.: Cause: An internal error occurred in event manager. Contact Oracle Support Services.
AIP-10122 The event manager cannot raise an event on a role other than the native role.: Cause: An internal error occurred in event manager. Contact Oracle Support Services.
AIP-10123 The event manager cannot raise an event that is outbound.: Cause: An internal error occurred in event manager. Contact Oracle Support Services.
AIP-10124 The event manager cannot raise an event with a type other than the native event type.: Cause: An internal error occurred in event manager. Contact Oracle Support Services.
AIP-10125 The event manager cannot raise an event with no current port.: Cause: An internal error occurred in event manager. Contact Oracle Support Services.
AIP-10126 The event manager cannot raise an event with no coordination.: Cause: An internal error occurred in event manager. Contact Oracle Support Services.
AIP-10200 failed to boot integration manager: Cause: Failed to start integration manager.
AIP-10201 Integration manager initialization failed.: Cause: Failed to create subscribers.
AIP-10202 Integration manager initialization failed.: Cause: Cannot find a class to load into integration manager.
AIP-10203 Integration manager initialization failed.: Cause: Cannot find a method from a class to load into integration manager.
AIP-10204 Integration manager initialization failed.: Cause: Cannot instantiate a class to load into integration manager.
AIP-10205 Integration manager initialization failed.: Cause: Invalid access for class to load into integration manager.
AIP-10206 Integration manager initialization failed.: Cause: Invocation target error.
AIP-10207 Integration manager startup failed.: Cause: Cannot start invocation engine.
AIP-10208 Integration manager startup failed.: Cause: Cannot start the integration manager.
AIP-10209 Integration manager restart failed.: Cause: Cannot instantiate a class to load into integration manager.
AIP-10210 Integration manager restart failed.: Cause: Invalid access for class to load into integration manager.
AIP-10211 Integration manager restart failed.: Cause: Invocation target error.
AIP-10212 The integration manager failed to get a JDBC connection.: Cause: Cannot get a JDBC connection from the repository service.
AIP-10213 The integration manager failed to create subscribers.: Cause: A SQL error occurred while trying to create subscribers for the integration manager.
AIP-10214 The integration manager failed to create subscribers.: Cause: A JMS error occurred while trying to create subscribers for the integration manager.
AIP-10215 Telnet daemon I/O error: Cause: An I/O error occurred while initializing the Telnet daemon.
AIP-10216 Telnet error: Cause: An internal error occurred. Contact Oracle Support Services.
AIP-10217 failed to create the system monitor for integration manager: Cause: The integration manager system monitor cannot be created.
AIP-10250 integration manager fatal error: Cause: An internal error occurred in integration manager. Contact Oracle Support Services.
AIP-10251 cannot retrieve event token attributes: Cause: An internal error occurred in integration manager. Contact Oracle Support Services.
AIP-10252 role processor "{0}" transaction error: Cause: An internal error occurred in integration manager. Contact Oracle Support Services.
AIP-10253 error processing an event: Cause: An internal error occurred in integration manager. Contact Oracle Support Services.
AIP-10269 runtime error in processor "{0}": Cause: An internal error occurred in integration manager. Contact Oracle Support Services.
AIP-10270 A SQL error occurred while applying an algorithm.: Cause: SQL error occurred while applying an algorithm.
AIP-10271 repository error: Cause: A repository error occurred while applying an algorithm.
AIP-10272 business logic error: Cause: A business logic error occurred while applying an algorithm.
AIP-10273 general error: Cause: An error occurred while applying an algorithm.
AIP-10274 unknown error: Cause: An unknown error occurred while applying an algorithm.
AIP-10275 The algorithm failed to update an event instance.: Cause: Failed to update an event instance because of a business logic layer error.
AIP-10276 The algorithm failed to update an event instance.: Cause: Failed to update an event instance because of a data validation error.
AIP-10277 The algorithm failed to update an event instance.: Cause: Failed to update an event instance because of an optimistic lock error.
AIP-10278 The algorithm failed to update an event instance.: Cause: Failed to update an event instance because of an object not found error.
AIP-10279 The algorithm failed to update an event instance.: Cause: Failed to update an event instance because of a uniqueness violation error.
AIP-10280 runtime error: Cause: A runtime error occurred while applying an algorithm.
AIP-10300 error creating data flow instance: Cause: Role manager cannot create data flow instance. More than one data flow group instance found between the from and current roles of the event.
AIP-10301 error creating data flow group instance: Cause: Design error. There should be exactly one data flow group between the from and current ports of the event.
AIP-10302 error creating data flow instance: Cause: Design error. There should be exactly one data flow group between the from and current ports of the event.
AIP-10303 error getting target role: Cause: Design error. More than one target role for an inbound event.
AIP-10400 The invocation engine failed to create a transition instance.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10401 The invocation engine failed to create a step instance.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10402 The invocation engine failed after creating the step instance but before joining a transition created as part of an earlier invocation.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10403 The invocation engine failed when raising a business event after executing the step.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10404 The invocation engine failed when trying to query for a step instance given its type.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10405 The invocation engine failed when creating data flow instances (isInbound "{0}").: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10406 The invocation engine failed when querying for a source port instance given the transition type and role instance to look in.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10407 The invocation engine failed when querying for a target role port instance given the transition type and role instance to look in.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10408 The invocation engine failed when querying for transition instances to join.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10409 The invocation engine failed when finding the source step instance for the specified transition type.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10410 The invocation engine encountered a step that cannot be executed.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10411 The invocation engine failed when putting data (the output of the executed step) on the step output ports.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10412 The translation step failed during execution.: Cause: An error occurred during translation of event. Check if content of Oracle record being raised is valid; if valid, contact Oracle Support Services; if not valid, correct and re-raise a new Oracle record with valid content.
AIP-10413 The condition step callout failed during execution.: Cause: An error occurred while executing the condition step. Check if content of Oracle record being raised is valid; if valid, contact Oracle Support Services; if not valid, correct and re-raise a new Oracle record with valid content.
AIP-10414 The condition step failed during execution.: Cause: An error occurred while executing the condition step. Check if content of Oracle record being raised is valid; if valid, contact Oracle Support Services; if not valid, correct and re-raise a new Oracle record with valid content.
AIP-10415 The consume step callout failed during execution.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10416 The split step callout failed during execution.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10417 The pass-through step callout failed during execution.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10418 The set adapter exchange protocol step callout failed during execution.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10419 The set adapter type step callout failed during execution.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10420 The set party step callout failed during execution.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10421 The end step failed during execution.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10422 The transformation step callout failed during execution.: Cause: An error occurred during transformation. Check if content of Oracle record being raised is valid; if valid, contact Oracle Support Services; if not valid, correct and re-raise a new Oracle record with valid content.
AIP-10423 The transformation step failed during execution.: Cause: An error occurred during transformation. Check if content of Oracle record being raised is valid; if valid, contact Oracle Support Services; if not valid, correct and re-raise a new Oracle record with valid content.
AIP-10424 The invocation engine failed to create the invocation object from the dequeued token.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10425 The translation step failed when creating the target event.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10426 The invocation engine failed to fetch the repository connection.: Cause: The invocation engine encountered a DC exception when fetching repository connection through persistency service.
AIP-10427 The invocation engine failed to create a subscriber.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10428 The invocation engine failed while initializing the invocation selector object.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10429 The invocation engine failed while shutting down the invocation selector object.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10430 The invocation engine failed while fetching the next invocation.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10431 The invocation engine failed before step execution.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10432 The invocation engine failed after step execution.: Cause: An internal error occurred in invocation engine. Contact Oracle Support Services.
AIP-10433 An error occurred while initializing the invocation processor object.: Cause: An error occurred during the initialization of invocation processor object.
AIP-10434 An error occurred in the invocation processor object while committing the transaction.: Cause: An error occurred during transaction commit in invocation processor object.
AIP-10435 An exception occurred while populating the return code port with a domain error.: Cause: An exception occurred while populating the return code port with a domain error.
AIP-10436 An error occurred while executing a step.: Cause: An error occurred during the execution of a step.
AIP-10437 An error occurred while refreshing a repository object.: Cause: An error occurred while refreshing a repository object.
AIP-10438 An error occurred while creating a system monitor object.: Cause: An error occurred during creation of system monitor object.

AIP-11000 to AIP-11999 Repository Error Codes

AIP-11000 transaction already open: Cause: Transaction already open.
AIP-11001 transaction closed: Cause: Transaction closed.
AIP-11002 connection already established: Cause: Connection already established.
AIP-11003 failed to create connection: Cause: Failed to create connection.
AIP-11004 unimplemented feature used: Cause: Unimplemented feature used.
AIP-11005 invalid association "{0}": Cause: Invalid association "{0}".
AIP-11006 object not found in association: Cause: Object not found in association.
AIP-11007 object deleted: Cause: Object is deleted.
AIP-11008 modification not allowed: Cause: Modification not allowed.
AIP-11009 connection not opened: Cause: Connection not opened.
AIP-11010 infinite loop detected: Cause: Infinite loop detected.
AIP-11011 Writing objects to database failed.: Cause: Writing objects to database failed.
AIP-11012 Commit failed.: Cause: Commit failed.
AIP-11013 Invalid object added to cache.: Cause: Attempt to add invalid object to cache.
AIP-11014 Object already exists in cache.: Cause: Object already exists in cache.
AIP-11015 Object does not exist "{0}".: Cause: Object does not exist "{0}".
AIP-11016 SQL error: Cause: SQL error.
AIP-11017 class "{0}" not found: Cause: Class "{0}" not found.
AIP-11018 invalid OID "{0}": Cause: Invalid Oracle Internet Directory "{0}".
AIP-11019 driver not loaded: Cause: Driver not loaded.
AIP-11020 metadata manager not loaded: Cause: Metadata manager not loaded.
AIP-11021 unknown type of bind variable: Cause: Unknown type of bind variable.
AIP-11022 unable to create GUID: Cause: Unable to create GUID.
AIP-11023 invalid domain value "{0}" for attribute "{1}": Cause: Invalid domain value "{0}" for attribute "{1}".
AIP-11024 writing to CLOB failed: Cause: Writing to CLOB failed.
AIP-11025 unsupported operation in predicate: Cause: Unsupported operation in predicate.
AIP-11026 Only a query statement is allowed.: Cause: Only query statement is allowed.
AIP-11027 unable to construct base object: Cause: Unable to construct base object.
AIP-11028 invalid cache parameter: Cause: Invalid cache parameter.
AIP-11029 creating rollback or savepoint failed: Cause: Create rollback or savepoint failed.
AIP-11030 transaction rollback failed: Cause: Transaction rollback failed.
AIP-11031 rollback to last savepoint failed: Cause: Rollback to last savepoint failed.
AIP-11032 cache rollback failed: Cause: Cache rollback failed.
AIP-11033 unable to create savepoint: Cause: Unable to create savepoint.
AIP-11034 unable to sort the base object for batch update: Cause: Unable to sort the base object for batch update.
AIP-11035 reading from CLOB failed: Cause: Reading from CLOB failed.
AIP-11036 rollback beyond savepoint: Cause: Rollback beyond savepoint.
AIP-11037 object is updated in database: Cause: Object is updated in database.
AIP-11038 inconsistent metadata: Cause: Inconsistent metadata.
AIP-11039 The object type is different than the required object type.: Cause: Object type is different than required object type.
AIP-11040 The attribute type "{0}" is not supported.: Cause: Attribute type "{0}" is not supported.
AIP-11041 error in querying strong aggregation: Cause: Error in querying strong aggregation.
AIP-11042 A many-to-many association is not supported.: Cause: Many-to-many association is not supported.
AIP-11043 The object is not a first class object.: Cause: Object is not a first class object.
AIP-11044 error while adding object with unsupported state in persistency service: Cause: Error while adding object with unsupported state in persistency service.
AIP-11045 error while locking objects before commit: Cause: Error while locking objects before commit.
AIP-11046 unsupported list: Cause: Unsupported list.
AIP-11047 invalid OID string used to create OID: Cause: Invalid Oracle Internet Directory string used to create Oracle Internet Directory.
AIP-11048 SQL tracing not supported for thin JDBC driver: Cause: SQL tracing not supported for thin JDBC driver.
AIP-11049 "{0}" is not a persisted column. It cannot be used as part of the ordering clause.: Cause: "{0}" is not a persisted column. Cannot be used as part of ordering clause.
AIP-11050 cannot specify null column as part of ordering clause: Cause: Cannot specify null column as part of ordering clause.
AIP-11051 Not all rows are updated.: Cause: Not all rows are updated.
AIP-11052 Writing object "{0}" failed due to constraint violation "{1}".: Cause: Writing objects "{0}" failed due to constraint violation "{1}".
AIP-11053 The CLOB column cannot be used as part of the ordering clause.: Cause: Clob column cannot be used as part of ordering clause.
AIP-11054 The XMLType column cannot be used as part of the ordering clause.: Cause: XMLType column cannot be used as part of ordering clause.
AIP-11055 Persistency service for this object is no longer valid.: Cause: Persistency service for this object is no longer valid.
AIP-11056 Persistency service for this object is no longer valid.: Cause: Persistency service for this object is no longer valid.
AIP-11057 reading/commit LargeString/XMLString before closing writer: Cause: Reading/commit LargeString/XMLString before closing writer.
AIP-11058 cannot call setAttribute() method for LargeString and XMLString: Cause: Cannot call setAttribute() method for the LargeString and XMLString.
AIP-11059 invalid object "{0}" state "{1}" to persist: Cause: Invalid object "{0}" state "{1}" to persist.
AIP-11060 The row has changed in the database.: Cause: Row has changed in database.
AIP-11061 error in audit query: Cause: Error in audit query.
AIP-11062 error in audit delete: Cause: Error in audit delete.
AIP-11063 error enabling audit trigger: Cause: Error enabling audit trigger.
AIP-11064 OID or a class type is required for an audit query.: Cause: Oracle Internet Directory and class type cannot both be null.
AIP-11065 The MetaClass already has an AssociationEnd called "{0}".: Cause: The MetaClass already has an AssociationEnd called "{0}".
AIP-11200 The export service is open.: Cause: Export service is open.
AIP-11201 The export service is closed.: Cause: Export service is closed.
AIP-11202 File name "{0}" does not exist or cannot be created.: Cause: File name "{0}" does not exist or cannot be created.
AIP-11203 error while closing export output file: Cause: Error while closing export output file.
AIP-11204 error while ordering the objects for exporting: Cause: Error while ordering the objects for exporting.
AIP-11205 error while adding object in transaction: Cause: Error while adding object in transaction.
AIP-11206 mandatory attribute "{0}" missing in import: Cause: Mandatory attribute "{0}" missing in import.
AIP-11207 error deleting duplicate rows during import: Cause: Error deleting duplicate rows during import.
AIP-11208 invalid import mode: Cause: Invalid import mode.
AIP-11209 invalid file during import: Cause: Invalid file during import.
AIP-11210 error in import: Cause: Error in import.
AIP-11211 import service open: Cause: Import service open.
AIP-11212 error parsing XML file: Cause: Error in parsing XML file.
AIP-11213 Configuration table rows cannot be exported.: Cause: Configuration table rows cannot be exported.
AIP-11300 The given MetaClass does not exist.: Cause: Given MetaClass does not exist.
AIP-11301 The MetaClass "{0}" does not have the role "{1}".: Cause: The MetaClass "{0}" does not have the role "{1}".
AIP-11302 The MetaClass "{0}" does not have the attribute "{1}".: Cause: The MetaClass "{0}" does not have the attribute "{1}".
AIP-11303 Either role or type must be specified.: Cause: Either role or type must be specified.
AIP-11304 The MetaClass "{0}" is not a dependent type of the DepObject "{1}".: Cause: The MetaClass "{0}" is not a dependent type of the DepObject "{1}".
AIP-11400 "{0}" object is not versionable: Cause: "{0}" object is not versionable.
AIP-11401 error initializing the version service: Cause: Error in initializing the version service.
AIP-11402 Only one version is supported per transaction.: Cause: Only one version is supported for each transaction.
AIP-11403 The "{0}" object cannot be in a created state.: Cause: The "{0}" object cannot be in created state here.
AIP-11404 Versioning is not enabled.: Cause: Versioning is not enabled.
AIP-11405 The import failed while mapping the OID.: Cause: Import failed while mapping the Oracle Internet Directory before importing into database.
AIP-11407 wrong command line arguments: usage "{0}": Cause: Wrong command line arguments: usage "{0}".
AIP-11408 export not supported for multiple "{0}": Cause: Export not supported for multiple "{0}" configuration/Deployable BusinessProcess.
AIP-11409 The deployable flag "{0}" is not supported in file "{1}".: Cause: Deployable flag "{0}" is not supported in file "{1}". It should be true/false.
AIP-11410 The attribute or association for "{0}" does not exist in MetaClass "{1}".: Cause: Attribute or association for "{0}" does not exist in MetaClass "{1}".
AIP-11411 The predicate is null for the export business process.: Cause: Predicate is null for the export business process. Unique values are not defined in input file.
AIP-11412 Business process "{0}" is not deployed.: Cause: Exporting business process "{0}" which is not deployed with deployable flag in input file is not supported.
AIP-11413 Model "{0}" does not exist.: Cause: Model "{0}" does not exist in repository.
AIP-11414 Model version "{0}" in the importing repository is higher than export file version "{1}".: Cause: Higher model version "{0}" exists in importing repository than export file version "{1}".
AIP-11415 unable to convert value "{0}" to datatype "{1}": Cause: Unable to convert value "{0}" to datatype "{1}".
AIP-11416 SAX parser exception while parsing file "{0}"; invalid XML format: Cause: SAX Parser exception while parsing file "{0}". It means invalid XML format.
AIP-11418 Object "{0}" is mandatory or part of a unique key for role "{1}" of object "{2}".: Cause: Object "{0}" is mandatory or part of unique key for role "{1}" of object "{2}".
AIP-11419 Class "{0}" is not instantiable from class "{1}".: Cause: Class "{0}" is not instantiable from class "{1}".
AIP-11420 Class "{0}" is not a first class object. Export is supported for the first class object only.: Cause: Class "{0}" is not first class object. Export only supported for the first class object.
AIP-11421 error converting the XML reserved characters while exporting: Cause: Error while converting the XML reserved characters while exporting.
AIP-11422 Configuration "{0}" is a design type. Exporting a design type configuration is not supported.: Cause: Configuration "{0}" is design type. Exporting design type configuration is not supported.
AIP-11423 File entry "{0}" in the imported compressed file is invalid or contains more than one entry.: Cause: File entry "{0}" in imported compressed file is invalid or more than one entry.
AIP-11424 Object ID "{0}" is referred to before creating the object: error ordering objects during export.: Cause: Object ID "{0}" is referred to before creating the object. Error ordering object during export.

AIP-12000 to AIP 12600 Adapter Error Codes

AIP-12000 cannot find agreement in event "{0}": Cause: Event has no agreement.
AIP-12001 A local transaction in the resource adapter failed to begin.: Cause: Failure to begin a local transaction in the resource adapter.
AIP-12002 The interaction failed to execute and update.: Cause: Interaction failed to execute and update successfully.
AIP-12003 The interaction failed at execution.: Cause: Interaction failed at execution.
AIP-12004 The connection failed to close.: Cause: Closing connection after processing outbound event.
AIP-12005 The resource adapter failed to commit a local transaction.: Cause: Resource adapter failed to commit local transaction.
AIP-12006 The outbound processor failed to activate the event manager.: Cause: Failure to activate event manager for this adapter framework instance.
AIP-12007 The outbound processor failed to passivate the event manager.: Cause: Failure to passivate event manager for this adapter framework instance.
AIP-12008 The outbound processor failed to create a JCA interaction.: Cause: Failure to create a connection or JCA interaction for the identified event.
AIP-12009 The output record did not convert to an event instance.: Cause: Failure to convert output record from an outbound interaction execution to an event instance.
AIP-12010 An error occurred while activating the outbound event manager.: Cause: An error occurred while activating the outbound event manager.
AIP-12011 An error occurred while fetching the system monitor object.: Cause: An error occurred while fetching the system monitor object.
AIP-12012 An error occurred while ending the native role.: Cause: An error occurred while ending the native role.
AIP-12013 An error occurred during the begin, commit, or rollback of the outbound transaction.: Cause: An error occurred during begin, commit, or rollback of the outbound transaction.
AIP-12014 An error occurred during the persistency service operation.: Cause: An error occurred during persistency service operation.
AIP-12100 The event manager failed to activate in inbound.: Cause: Failed to activate event manager in inbound.
AIP-12101 The Oracle record failed to convert to the event instance.: Cause: Failed to convert Oracle record to event instance.
AIP-12102 failed to get an active configuration status: Cause: Failed to get an active configuration status.
AIP-12103 error in finding correlated events for the inbound event "{0}": Cause: Error in finding correlated events for the inbound event "{0}".
AIP-12104 Correlated events for the inbound event do not have process role instances.: Cause: Correlated events for the inbound event do not have process role instances.
AIP-12105 Correlated events for the inbound event do not have coordinations.: Cause: Correlated events for the inbound event do not have coordinations.
AIP-12106 No unique native role was found for the inbound event "{0}".: Cause: No unique native role found for the inbound event "{0}".
AIP-12107 The inbound event "{0}" is not native, inbound, or before native role.: Cause: Inbound event "{0}" is not native, inbound or before native role.
AIP-12108 no effective agreement between process role "{0}" and party "{1}": Cause: No effective agreement between process role "{0}" and party "{1}".
AIP-12109 No initiating or noninitiating process role was found for the inbound event "{0}".: Cause: The adapter framework did not find a native role that could accept the event. This is most likely due to not having a valid agreement for that native role. Ensure that the agreement is approved and that the effective dates are either blank or set to an interval. Another possibility is that a native event was created for the record for which there is not an inbound native role port. If you have multiple native events for the file adapter record, check the event map conditions. It may be that the wrong event map is evaluating to true and there is no inbound role port for this type.
AIP-12110 error creating a new coordination: Cause: Error creating a new coordination.
AIP-12111 error creating a new process role instance: Cause: Error creating a new process role instance.
AIP-12112 no effective agreement between the correlated event process role "{0}" and party "{1}": Cause: No effective agreement between correlated event's process role "{0}" and party "{1}".
AIP-12113 The configuration is retired. No inbound events can be accepted.: Cause: Configuration is retired. No inbound events can be accepted.
AIP-12114 The configuration is quiescing. No new uncorrelated inbound events can be accepted.: Cause: Configuration is quiescing. No new uncorrelated inbound events can be accepted.
AIP-12115 The configuration is not active and no new coordinations can be created for inbound events.: Cause: Configuration is not active. No new coordinations can be created for inbound events.
AIP-12116 An exception occurred while querying for adapter types.: Cause: Exception occurred while querying for adapter types.
AIP-12117 An exception occurred while querying for parties.: Cause: Exception occurred while querying for parties.
AIP-12118 An exception occurred while querying for the connection parameter value.: Cause: Exception occurred while querying for connection parameter value.
AIP-12119 An exception occurred while querying for the outport instance, given the inport instance.: Cause: Exception occurred while querying for outport instance, given inport instance.
AIP-12120 An exception occurred while querying for the process role list.: Cause: Exception occurred while querying for process role list.
AIP-12121 An exception occurred while querying for the effective agreement.: Cause: An exception occurred while querying for the effective agreement.
AIP-12122 An exception occurred while querying for the adapter type.: Cause: Exception occurred while querying for adapter type.
AIP-12123 An exception occurred while querying for inbound interactions.: Cause: Exception occurred while querying for inbound interactions.
AIP-12124 An exception occurred while querying for the B2B adapter type.: Cause: Exception occurred while querying for B2B adapter type.
AIP-12125 An exception occurred while querying for the interaction group.: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12126 An exception occurred while querying for the value of the parameter.: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12127 An exception occurred while querying for the adapter provider.: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12128 An exception occurred while querying for the adapter exchange protocol.: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12129 cannot find class: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12130 cannot instantiate class: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12131 cannot access class: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12132 cannot create connection factory: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12133 cannot find method: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12134 cannot access method: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12135 cannot invoke method: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12136 An error occurred while setting the correlated events association.: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12137 An error occurred while updating the event.: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12138 An exception occurred while querying for the record type.: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12139 The specified adapter framework instance is invalid.: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12140 The specified record type is invalid.: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12141 An exception occurred while creating a native event instance from an Oracle record.: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12142 An error occurred while raising the inbound event.: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12143 error starting a transaction when raising a native event: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12144 error committing a transaction when raising a native event: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12145 An exception occurred when querying for ports that are ready to receive the specified event type from the specified roles.: Cause: Exception occurred when querying for ports that are ready to receive specified event type from specified roles.
AIP-12146 An exception occurred when querying for ports that can receive the specified event type from the specified roles.: Cause: Exception occurred when querying for ports that can ever receive specified event type from specified roles.
AIP-12147 An exception occurred when querying for ports that are ready to receive the specified event type from the specified coordination.: Cause: Exception occurred when querying for ports that are ready to receive specified event type from specified coordination.
AIP-12148 An exception occurred when querying for ports that can receive the specified event type from the specified coordination.: Cause: Exception occurred when querying for ports that can ever receive specified event type from specified coordination.
AIP-12149 An exception occurred when querying for role types that can receive the specified event type.: Cause: Exception occurred when querying for role types that can receive specified event type.
AIP-12150 An exception occurred when querying for the application.: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12151 An exception occurred when querying for the trading partner.: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12152 An out-of-order event cannot be raised to runtime.: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12200 The adapter cannot get metadata.: Cause: Adapter getMetadata failed.
AIP-12201 cannot get the next event for the outbound processor: Cause: Failed to get the next event for outbound processor.
AIP-12202 cannot consume event "{0}": Cause: Failed to consume event "{0}".
AIP-12203 cannot set state to "{0}" for event "{1}": Cause: Failed to set state to "{0}" for event "{1}".
AIP-12204 cannot set to error state for event "{0}": Cause: Failed to set state to error for event "{0}".
AIP-12205 The adapter type already exists.: Cause: The adapter type already exists.
AIP-12206 cannot create interaction group: Cause: Failed while creating interaction group.
AIP-12207 An error occurred while creating the interaction.: Cause: Failed while creating interaction.
AIP-12208 An error occurred while creating the body and record elements.: Cause: Failed while creating record element and corresponding native and application event body elements.
AIP-12209 An error occurred while getting the parameter values.: Cause: Failed while getting connection parameter used for connection factory or connection specification.
AIP-12210 resource exception from adapter: Cause: Resource exception from adapter while creating interaction.
AIP-12211 cannot initialize the adapter framework: Cause: Failed to initialize the adapter framework.
AIP-12212 cannot create a system monitor: Cause: Failed to create a system monitor in the adapter framework.
AIP-12213 cannot initialize the adapter manager: Cause: Failed to initialize the adapter manager in the adapter framework.
AIP-12214 cannot create a record instance: Cause: An internal error occurred within the adapter framework. Contact Oracle Support Services.
AIP-12500 No adapter framework instance was found for "{0}".: Cause: No adapter framework instance found for "{0}".
AIP-12501 cannot connect to B2B adapter "{0}": Cause: Cannot connect to B2B adapter "{0}".
AIP-12502 cannot initialize resource adapter "{0}": Cause: Failed to initialize resource adapter "{0}".
AIP-12503 cannot find the class for resource adapter "{0}": Cause: Cannot find the class resource adapter "{0}".
AIP-12504 Resource adapter "{0}" caused an invalid access error.: Cause: Resource adapter "{0}" caused an invalid access error.
AIP-12505 cannot start resource adapter "{0}": Cause: Failed to start resource adapter "{0}".
AIP-12506 cannot stop resource adapter "{0}": Cause: Failed to stop resource adapter "{0}".
AIP-12507 cannot start B2B adapter "{0}": Cause: Failed to start B2B adapter "{0}".
AIP-12508 cannot stop B2B adapter "{0}": Cause: Failed to stop B2B adapter "{0}".
AIP-12509 cannot deactivate resource adapter "{0}": Cause: Failed to deactivate resource adapter "{0}".
AIP-12600 generic adapter error: Cause: Message logged by adapter.

AIP-13000 to AIP-16014 Business Logic Layer Error Codes

AIP-13000 class not found: Cause: The specified class was not found.
AIP-13001 error getting an instance of the persistency service: Cause: There was an error obtaining an instance of the persistency service.
AIP-13002 SQL error getting the data source: Cause: There was a SQL error while trying to create the data source.
AIP-13003 The object is not a base object.: Cause: The object to be added to the cache is not a base object. Make sure it is a model object.
AIP-13004 A context has already been started.: Cause: The current context must be exited before starting a new one.
AIP-13005 error disconnecting from the persistency service: Cause: An error occurred disconnecting from the persistency service.
AIP-13006 The execution context must be initialized.: Cause: The execution context must be started for each request.
AIP-13007 error reading properties file "{0}": Cause: There was an error reading the properties file "{0}".
AIP-13100 The parameter "{0}" is null for object "{1}".: Cause: A null parameter is not allowed as a valid value.
AIP-13101 The mandatory attribute "{0}" must be defined.: Cause: The mandatory attribute must be set.
AIP-13102 The attribute "{0}" was not found in object "{1}".: Cause: Attribute with given name does not exist in the object.
AIP-13103 The string length of the attribute "{0}" is more than the maximum allowed length.: Cause: String length cannot be longer than maximum allowed length.
AIP-13104 The string length of the attribute "{0}" is less than the minimum allowed length.: Cause: String length shorter than minimum allowed length.
AIP-13105 Syntax validation failed.: Cause: One of the attributes does not satisfy syntax validation.
AIP-13106 The object "{0}" was previously updated.: Cause: Optimistic lock check determined that the object "{0}" has been updated by someone else in the system.
AIP-13107 The class "{0}" was not found.: Cause: The specified class "{0}" was not found.
AIP-13108 The constructor for class "{0}" was not found.: Cause: The specified constructor for the given class was not found.
AIP-13109 unable to instantiate an instance of class "{0}": Cause: Unable to instantiate an instance of the specified class.
AIP-13110 no access to the constructor of class "{0}": Cause: Access to the constructor of the specified class is restricted.
AIP-13111 error invoking the constructor of class "{0}": Cause: There was an error invoking the constructor of the specified class.
AIP-13112 invalid date range specification: Cause: The start date must occur strictly before the end date.
AIP-13113 Two or more objects do not share the same parent object.: Cause: The objects must share a common parent object to be associated.
AIP-13114 error parsing the connection information: Cause: An error occurred parsing the connection information.
AIP-13115 not in an active transaction: Cause: A transactional operation was attempted while not inside an active transaction.
AIP-13116 The object "{0}" was not found.: Cause: Object "{0}" was not found in the system.
AIP-13117 The seed data was not loaded.: Cause: The seed data must be loaded into the system for the system to be functional.
AIP-13118 internal error in business logic: Cause: An internal error occurred. Contact Oracle Support Services.
AIP-13119 An operation was performed on one or more business objects while not in seed data mode.: Cause: Operation performed on one or more business objects while not in seed data mode.
AIP-13120 unable to set 'IsSeeded' flag in new instance of class "{0}": Cause: Unable to set 'IsSeeded' flag in new instance of the specified class.
AIP-13200 error adding hosted trading partner: Cause: System does not allow adding more than one hosted trading partner.
AIP-13201 The party already exists.: Cause: Party object name is not unique in the system.
AIP-13202 The party was not found.: Cause: Party was not found in the system.
AIP-13203 Deleting the hosted trading partner is not allowed.: Cause: One hosted trading partner must always exist in the system.
AIP-13204 The party identification already exists.: Cause: A party identification object with the given name already exists within the party.
AIP-13205 The party identification was not found.: Cause: The party identification was not found in the system.
AIP-13206 The contact information was not found.: Cause: The contact information was not found in the system.
AIP-13207 The document exchange was not found.: Cause: The document exchange was not found in the system.
AIP-13208 The delivery channel was not found.: Cause: The delivery channel was not found in the system.
AIP-13209 The transport was not found.: Cause: The transport was not found in the system.
AIP-13210 The contact information already exists.: Cause: The contact information exists in the system.
AIP-13211 The object is not contact information.: Cause: The ID did not map to a contact information object, so there was a ClassCastException.
AIP-13212 The document exchange already exists.: Cause: The document exchange exists in the system.
AIP-13213 The delivery channel already exists.: Cause: The delivery channel exists in the system.
AIP-13214 The transport already exists.: Cause: The transport exists in the system.
AIP-13215 The certificate and document exchange are not from the same trading partner.: Cause: The certificate and document exchange must be part of the same trading partner to be associated.
AIP-13216 The certificate and transport are not from the same trading partner.: Cause: The certificate and transport must be part of the same trading partner to be associated.
AIP-13217 The object is not a trading partner.: Cause: The ID did not map to a trading partner object, so there was a ClassCastException.
AIP-13218 The object is not a party identification.: Cause: The ID did not map to a party identification object, so there was a ClassCastException.
AIP-13219 The object is not a document exchange.: Cause: The ID did not map to a document exchange object, so there was a ClassCastException.
AIP-13220 The object is not a delivery channel.: Cause: The ID did not map to a delivery channel object, so there was a ClassCastException.
AIP-13221 The object is not a transport.: Cause: The ID did not map to a transport object, so there was a ClassCastException.
AIP-13222 The person already exists.: Cause: The person object already exists in the system.
AIP-13223 The person was not found.: Cause: The person was not found in the system.
AIP-13224 The object is not a person.: Cause: The ID did not map to a person object, so there was a ClassCastException.
AIP-13225 The certificate already exists.: Cause: The certificate object already exists in the system.
AIP-13226 The certificate was not found.: Cause: The certificate was not found in the system.
AIP-13227 The object is not a certificate.: Cause: The ID did not map to a certificate object, so there was a ClassCastException.
AIP-13128 The party identification type already exists.: Cause: Party identification type object name is not unique in the system.
AIP-13129 The party identification type must be removed from all party identifications.: Cause: The party identification type cannot be removed if it is currently being used to identify a party identification in the system.
AIP-13130 The party identification type was not found.: Cause: Party identification type was not found in the system.
AIP-13131 The contact type was not found.: Cause: Contact type was not found in the system.
AIP-13132 The contact type already exists.: Cause: Contact type already exists in the system.
AIP-13233 The object is not a party identification type.: Cause: The ID did not map to a party identification type object so there was a ClassCastException.
AIP-13234 The object is not a contact type.: Cause: The ID did not map to a contact type object, so there was a ClassCastException.
AIP-13235 The business protocol cannot be disassociated until related associations are broken.: Cause: The exchange protocol must be disassociated from document exchange of the corresponding party before the business protocol of the same party can be disassociated.
AIP-13236 The protocol element was not associated with the document exchange.: Cause: The given protocol element was not previously associated with the document exchange. The value cannot be retrieved because it does not exist.
AIP-13237 The business protocol was not associated with the party.: Cause: The given business protocol was not previously associated with the party. The objects do not need to be disassociated.
AIP-13238 The exchange protocol was not associated with the party.: Cause: The given exchange protocol was not previously associated with the party through the business protocol. The business protocol of this exchange protocol needs to be associated with the party before the exchange protocol can be associated with the document exchange.
AIP-13239 The document exchange and delivery channel must belong to the same party.: Cause: The document exchange and delivery channel must belong to the same party in order to be associated.
AIP-13240 The transport and delivery channel must belong to the same party.: Cause: The transport and delivery channel must belong to the same party in order to be associated.
AIP-13241 The document exchange associations still exist.: Cause: Document exchange must be disassociated from delivery channel before it can be removed, either by removing the delivery channels or associating new document exchanges with them.
AIP-13242 The certificate associations still exist.: Cause: Certificate must be disassociated from document exchange and transport before it can be removed.
AIP-13243 The transport associations still exist.: Cause: Transport must be disassociated from delivery channel before it can be removed, either by deleting the delivery channel or by associating a new transport with the delivery channel.
AIP-13244 The contact type associations still exist.: Cause: Contact information objects using contact type must be removed before the contact type can be removed.
AIP-13250 The protocol endpoint was not found.: Cause: The protocol endpoint was not found in the system.
AIP-13251 The object is not a protocol endpoint.: Cause: The ID did not map to a protocol endpoint object, so there was a ClassCastException.
AIP-13252 The endpoint was not found.: Cause: The endpoint was not found in the system.
AIP-13253 The object is not an endpoint.: Cause: The ID did not map to a endpoint object, so there was a ClassCastException.
AIP-13254 The protocol endpoint already exists.: Cause: The protocol endpoint exists in the system.
AIP-13255 The endpoint already exists.: Cause: The endpoint exists in the system.
AIP-13256 The protocol endpoint that precedes the new protocol endpoint was not found.: Cause: The protocol endpoint, which is supposed to be used as the position to place the new protocol endpoint before, does not exist in the system.
AIP-13300 The agreement already exists.: Cause: Agreement object name is not unique in the system.
AIP-13301 The agreement was not found.: Cause: Agreement was not found in the system.
AIP-13302 The collaboration was already implemented.: Cause: Collaboration is already implemented by the agreement.
AIP-13303 The collaboration was not implemented.: Cause: Collaboration is not implemented by the agreement.
AIP-13304 collaboration dependency error: Cause: Unable to remove collaboration due to object interdependencies.
AIP-13305 The party is not an agreement participant.: Cause: Party is not a participant in the agreement.
AIP-13307 The party is already an agreement participant.: Cause: Party is already an active participant in the agreement.
AIP-13308 The object is not an agreement.: Cause: The ID did not map to an agreement object, so there was a ClassCastException.
AIP-13309 An association dependency error occurred.: Cause: An association dependency error occurred.
AIP-13400 The collaboration was not found.: Cause: Collaboration was not found in the system.
AIP-13401 The object is not a collaboration.: Cause: The ID did not map to a collaboration object, so there was a ClassCastException.
AIP-13402 The collaboration already exists.: Cause: Collaboration object name is not unique in the system.
AIP-13500 The process diagram already exists.: Cause: Process diagram exists in the system.
AIP-13501 The process diagram was not found.: Cause: Process diagram was not found in the system.
AIP-13502 The object is not an actor.: Cause: The ID did not map to an actor object, so there was a ClassCastException.
AIP-13503 The actor already exists.: Cause: Actor exists in the system.
AIP-13504 The actor was not found.: Cause: Actor was not found in the system.
AIP-13505 The object is not an actor.: Cause: The ID did not map to an actor object, so there was a ClassCastException.
AIP-13506 The composite step already exists.: Cause: Composite step exists in the system.
AIP-13507 The composite step was not found.: Cause: Composite step was not found in the system.
AIP-13508 The state vertex already exists.: Cause: State vertex exists in the system.
AIP-13509 The state vertex was not found.: Cause: State vertex was not found in the system.
AIP-13510 The object is not a state vertex.: Cause: The ID did not map to an state vertex object, so there was a ClassCastException.
AIP-13600 The business protocol was not found.: Cause: Business protocol not found.
AIP-13601 The exchange protocol was not found.: Cause: Exchange protocol not found.
AIP-13602 The transport protocol was not found.: Cause: Transport protocol was not found in the system.
AIP-13603 The transport protocol already exists.: Cause: Transport protocol already exists in the system.
AIP-13604 The object is not a transport protocol.: Cause: The ID did not map to a transport protocol object, so there was a ClassCastException.
AIP-13605 The business protocol already exists.: Cause: Business protocol already exists in the system.
AIP-13606 The object is not a business protocol.: Cause: The ID did not map to a business protocol object, so there was a ClassCastException.
AIP-13607 The exchange protocol already exists.: Cause: Exchange protocol already exists in the system.
AIP-13608 The object is not an exchange protocol.: Cause: The ID did not map to a exchange protocol object, so there was a ClassCastException.
AIP-13609 The protocol element was not found.: Cause: Protocol element object not found.
AIP-13610 The protocol element already exists.: Cause: Protocol element already exists in the system.
AIP-13611 The document protocol was not found.: Cause: Document protocol object not found.
AIP-13612 The document protocol already exists.: Cause: Document protocol already exists in the system.
AIP-13613 The object is not a document protocol.: Cause: The ID did not map to a document protocol object, so there was a ClassCastException.
AIP-13614 The process protocol was not found.: Cause: Process protocol object not found.
AIP-13615 The process protocol already exists.: Cause: Process protocol already exists in the system.
AIP-13616 The object is not a process protocol.: Cause: The ID did not map to a process protocol object, so there was a ClassCastException.
AIP-13617 The packaging protocol was not found.: Cause: Packaging protocol object not found.
AIP-13618 The packaging protocol already exists.: Cause: Packaging protocol already exists in the system.
AIP-13619 The object is not a packaging protocol.: Cause: The ID did not map to a packaging protocol object, so there was a ClassCastException.
AIP-13620 The packaging ID was not found.: Cause: Packaging ID object not found.
AIP-13621 The object is not a packaging ID.: Cause: The ID did not map to a packaging ID object, so there was a ClassCastException.
AIP-13622 The process protocol and business protocol are not associated.: Cause: There is no association between process protocol and business protocol.
AIP-13623 The secure exchange protocol was not found.: Cause: Secure exchange protocol object not found.
AIP-13624 The secure exchange protocol already exists.: Cause: Secure exchange protocol already exists in the system.
AIP-13625 The object is not a secure exchange protocol.: Cause: The ID did not map to a secure exchange protocol object, so there was a ClassCastException.
AIP-13626 The digital signature already exists.: Cause: Digital signature already exists in the system.
AIP-13627 The digital envelope already exists.: Cause: Digital envelope already exists in the system.
AIP-13628 The algorithm already exists.: Cause: Algorithm already exists in the system.
AIP-13629 The algorithm was not found.: Cause: Algorithm not found.
AIP-13630 The object ID is not an algorithm.: Cause: The ID did not map to a algorithm object, so there was a ClassCastException.
AIP-13631 The digital signature was not found.: Cause: Digital signature not found.
AIP-13632 The object ID is not a digital signature.: Cause: The ID did not map to a digital signature object, so there was a ClassCastException.
AIP-13633 The digital envelope was not found.: Cause: Digital envelope not found.
AIP-13634 The object ID is not digital envelope.: Cause: The ID did not map to a digital envelope object, so there was a ClassCastException.
AIP-13650 The datatype was not found.: Cause: Datatype was not found in the system.
AIP-13651 The datatype already exists.: Cause: Datatype already exists in the system.
AIP-13652 The object is not a datatype.: Cause: The ID did not map to a datatype object, so there was a ClassCastException.
AIP-13653 The datatype member was not found.: Cause: Datatype member was not found in the system.
AIP-13654 The datatype member already exists.: Cause: Datatype member already exists in the system.
AIP-13655 The object is not a datatype member.: Cause: The ID did not map to a datatype member object, so there was a ClassCastException.
AIP-13656 The scalar member is associated with the wrong datatype.: Cause: Scalar member can refer to scalar datatype only.
AIP-13657 A valid value was not found.: Cause: Valid value was not found in the system.
AIP-13658 A valid value already exists.: Cause: Valid value already exists in the system.
AIP-13659 The object is not a valid value.: Cause: The ID did not map to a valid value object, so there was a ClassCastException.
AIP-13660 The event type was not found.: Cause: Event type was not found in the system.
AIP-13661 The event type already exists.: Cause: Event type already exists in the system.
AIP-13662 The object is not an event type.: Cause: The ID did not map to a event type object, so there was a ClassCastException.
AIP-13663 The event body was not found.: Cause: Event body was not found in the system.
AIP-13664 The event body already exists.: Cause: Event body already exists in the system.
AIP-13665 The object is not an event body.: Cause: The ID did not map to a event body object, so there was a ClassCastException.
AIP-13666 The event type class was not found.: Cause: Event type class was not found in the system.
AIP-13667 The event type class already exists.: Cause: Event type class already exists in the system.
AIP-13668 The object is not an event type class.: Cause: The ID did not map to a event type class object, so there was a ClassCastException.
AIP-13669 The protocol object is not an instance of either the business protocol, document protocol, or exchange protocol.: Cause: Datatype object could be associated either with business protocol, document protocol or exchange protocol.
AIP-13670 The instance of the datatype does not match the instance of the scalar member.: Cause: Scalar member could be associated only with scalar datatype.
AIP-13700 The process role was not found.: Cause: Process role was not found in the system.
AIP-13701 The process role already exists.: Cause: Process role already exists in the system.
AIP-13702 The object is not a process role.: Cause: The ID did not map to a process role object, so there was a ClassCastException.
AIP-13703 The data flow group was not found.: Cause: Data flow group was not found in the system.
AIP-13704 The data flow group already exists.: Cause: Data flow group already exists in the system.
AIP-13705 The object is not a data flow group.: Cause: The ID did not map to a data flow group object, so there was a ClassCastException.
AIP-13900 user authentication unsuccessful: Cause: User cannot be authenticated due to invalid user name or password.
AIP-13901 access denied to use case "{0}": Cause: User does not have privilege to access the use case. Grant appropriate user roles to the user.
AIP-13902 invalid authentication token "{0}": Cause: The supplied authentication token is invalid.
AIP-13903 The use case group "{0}" already exists.: Cause: Use case group name is not unique in the system.
AIP-13904 The use case "{0}" already exists.: Cause: Use case name is not unique in the system.
AIP-13905 The use case was not found.: Cause: Use case was not found in the system.
AIP-13906 The user role "{0}" already exists.: Cause: User role name is not unique in the system.
AIP-13907 The user role was not found.: Cause: User role was not found in the system.
AIP-13908 The object is not a user role.: Cause: The ID did not map to a user role object.
AIP-13909 The use case "{0}" is not granted to user role "{1}".: Cause: The specified use case has not been granted to the user role.
AIP-13910 The user role "{0}" is not granted to person "{1}".: Cause: The specified user role has not been granted to the person.
AIP-13911 The configuration type was not found.: Cause: Configuration type begin set is not seeded.
AIP-13912 The execution context was not found for the ID.: Cause: Execution context not found.
AIP-13913 The object "{0}" is invalid.: Cause: Object is invalid.
AIP-13950 The XML schema cannot be parsed due to error "{0}".: Cause: The XML schema could not be parsed due to error(s) "{0}".
AIP-13951 exclusive import mode violated: Object "{0}" in "{1}" is defined in the XSD but already exists in the database.: Cause: Exclusive import mode violated: Object "{0}" in "{1}" is defined in the XSD but already exists in the database.
AIP-13952 The attribute "{0}" cannot have the value "{1}".: Cause: Attribute "{0}" cannot have value "{1}".
AIP-13953 failed to get a valid URL from XSD filename "{0}": Cause: Failed to get a valid URL from XSD filename "{0}".
AIP-13954 error storing the imported document as a string: Cause: Error storing the imported document as a string.
AIP-13955 An XSD cannot import its own target namespace.: Cause: The XML schema imports another XML schema whose namespace is identical. This is not supported by XML schema.
AIP-13956 There must be an XMLNS attribute for each namespace referenced in an import tag.: Cause: The XML schema imports another XML schema; however there is no XMLNS attribute in reference to the imported schema.
AIP-13957 Every input tag in a schema must have a schema location attribute.: Cause: The XML schema includes another schema; however a value is not supplied for the mandatory attribute 'schemaLocation'.
AIP-13958 An XSD that is imported using importString or importStream may not contain an import or include tag.: Cause: The XSD input contains an import or include tag.
AIP-13959 There cannot be a "{0}" in "{2}" and a "{3}" in "{4}" that are both named "{1}".: Cause: The definition of a "{0}" named "{1}" in "{2}" conflicts with the definition of a "{3}" in the same namespace also named "{1}" in "{4}".
AIP-13960 "{0}" is not a valid event type classification for an XSD import.: Cause: "{0}" is not a valid event type classification for an XSD import.
AIP-13961 cannot find the seeded datatype "{1}" in namespace "{2}" with event type class "{3}" to which the XSD type "{0}" maps: Cause: Could not find the seeded datatype "{1}" in namespace "{2}" with event type class "{3}" that the XSD type "{0}" maps to.
AIP-13962 The XSD type "{0}" has no mapping to a datatype for event type class "{1}".: Cause: XSD type "{0}" has no mapping to a datatype for event type class "{1}".
AIP-13963 cannot resolve the canonical path of "{0}": Cause: Could not resolve the canonical path of "{0}".
AIP-13964 The XSD file "{0}" does not exist.: Cause: XSD file "{0}" does not exist.
AIP-13965 An error occurred while saving XSD "{0}" as a string.: Cause: Error saving XSD "{0}" as a string.
AIP-13966 "{0}" "{1}" in namespace "{2}" is referred to in "{3}" but is not defined.: Cause: "{0}" "{1}" in namespace "{2}" is referred to in "{3}" but never defined.
AIP-13967 The root element "{0}" was not found in the XSD.: Cause: The XML schema does not contain a root element which is required by the XSD converter.
AIP-13968 unsupported XSD tag "{0}" "{1}" encountered: Cause: The XSD importer does not support "{0}" "{1}". Remove this tag or decrease the schema validation level.
AIP-16000 A null parameter cannot be passed into the model validation engine.: Cause: A null parameter cannot be passed into the model validation engine.
AIP-16001 Model validation cannot be processed because of a system error.: Cause: An internal error occurred, so model validation could not be processed.
AIP-16002 no seed data: Cause: Seed data is not loaded.
AIP-16003 The model validation engine cannot resolve the validation context.: Cause: An internal error occurred so engine could not resolve validation context.
AIP-16004 Rule "{0}" in class "{1}" fails while processing.: Cause: An internal error occurred during rule execution.
AIP-16005 The class "{0}" was not found.: Cause: An internal error occurred during execution. The class "{0}" cannot be located.
AIP-16006 The method "{1}" was not found in class "{0}".: Cause: An internal error occurred during execution. The method "{0}" cannot be located in the class "{1}".
AIP-16007 The attributes are not correct in rule "{0}" class "{1}".: Cause: An internal error occurred during rule invocation.
AIP-16008 no access to rule class "{1}": Cause: An internal error occurred during rule execution. No access to rule class "{1}".
AIP-16009 The "{1}" subject type "{0}" was not found.: Cause: An internal error occurred during execution. The "{1}" subject type "{0}" cannot be located.
AIP-16010 The object "{0}" already exists.: Cause: Object "{0}" already exists in the system.
AIP-16011 The object "{0}" cannot be deleted because object "{1}" refers to it.: Cause: Object "{0}" cannot be deleted because child object "{1}" exists.
AIP-16012 The parameter "{0}" is unique for object "{1}".: Cause: Parameter "{0}" is unique for object "{1}".
AIP-16013 The object "{0}" cannot be updated or created because the parent object "{1}" does not exist.: Cause: Object "{0}" cannot be updated or created because parent object "{1}" does not exist.
AIP-16014 The object "{0}" is a database view. Update/delete/create is not allowed for database views.: Cause: Object "{0}" is database view. Update/delete/create is not allowed for database views.

AIP-14000 to AIP-14018 Transformation Error Codes

AIP-14001 The operand "{0}" does not evaluate to a value.: Cause: Operand "{0}" does not evaluate to a value.
AIP-14002 An instance of the event body element "{0}" was not found in the event instance of type "{1}".: Cause: Instance of event body element "{0}" not found in event instance of type "{1}".
AIP-14003 error in invoking header function "{0}": Cause: Error in invoking header function "{0}".
AIP-14004 error in invoking domain value function "{0}": Cause: Error in invoking domain value function "{0}".
AIP-14005 error in invoking a callout datatype transformation map implemented by class "{0}": Cause: Error in invoking a callout datatype transformation map implemented by class "{0}".
AIP-14006 Data value "{0}" is in an invalid format.: Cause: Data value "{0}" is in an invalid format.
AIP-14007 The XML element "{0}" is expected to contain a text node.: Cause: XML element "{0}" is expected to contain a text node.
AIP-14008 The invalid condition expression "{0}" cannot be evaluated.: Cause: Invalid condition expression "{0}" cannot be evaluated.
AIP-14009 The operand "{0}" results in the selection of multiple items where a single item is expected.: Cause: Operand "{0}" results in selection of multiple items where single item is expected.
AIP-14010 internal error in transformation engine: Cause: Internal Error in Transformation Engine.
AIP-14011 Event Body Element Instance Values of type {0} corresponding to Event Body Element {1} of Event Type {2} not supported.: Cause: Event Body Element Instance Values of type {0} corresponding to Event Body Element {1} of Event Type {2} not supported.
AIP-14012 The transformation map parameter "{0}" instance is not specified while invoking the map.: Cause: Transformation map parameter "{0}" instance not specified while invoking map.
AIP-14013 error evaluating path for the operand "{1}": Cause: Error in evaluating path for the operand "{1}".
AIP-14014 error in populating return code for transformation: Cause: Error in populating return code for transformation.
AIP-14015 error in accessing XML content of datatype or event instance: Cause: Error in accessing XML content of datatype or event instance.
AIP-14016 error in creating XML content of datatype or event instance: Cause: Error in creating XML content of datatype or event instance.
AIP-14017 error in saving the event or datatype instance corresponding to map parameter: Cause: Error in saving the event or datatype instance corresponding to map parameter.
AIP-14019 Invalid party {0} in SetToParty: Cause: Invalid party in SetToParty.
AIP-14020 Invalid party {0} in SetFromParty: Cause: Invalid party in SetFromParty.

AIP-14100 to AIP-14114 Translation Error Codes

AIP-14100 The converter class "{0}" in translator "{1}" is invalid.: Cause: The converter class "{0}" in translator "{1}" is invalid.
AIP-14101 error getting interaction specification type or interaction specification parameters from converter "{0}": Cause: Error getting interaction specification type or interaction specification parameters from converter "{0}".
AIP-14102 a system error occurred during translation: Cause: System error occurred during translation.
AIP-14103 invalid event body element "{0}": Cause: Invalid event body element "{0}".
AIP-14104 invalid application datatype set in OutConverterRecord: Cause: Invalid application datatype set in OutConverterRecord.
AIP-14105 invalid interaction specification "{0}" set in OutConverterRecord: Cause: Invalid interaction specification "{0}" set in OutConverterRecord.
AIP-14106 error getting value from interaction specification for parameter "{0}": Cause: Error getting value from interaction specification for parameter "{0}".
AIP-14107 invalid event type "{0}": Cause: Invalid event type "{0}".
AIP-14108 invalid source event body element instance "{0}": Cause: Invalid source event body element instance "{0}".
AIP-14109 invalid translation direction specified: Cause: Invalid translation direction specified.
AIP-14110 invalid target event body element instance "{0}": Cause: Invalid target event body element instance "{0}".
AIP-14111 The translator class "{0}" in translator "{1}" is invalid.: Cause: The translator class "{0}" in translator "{1}" is invalid.
AIP-14112 error creating interaction specification using reflection: Cause: Error creating interaction specification using reflection.
AIP-14113 error populating interaction specification with parameter values: Cause: Error populating interaction specification with parameter values.
AIP-14114 A translation error occurred in translator "{0}".: Cause: Translation error occurred in translator "{0}".

AIP-14115 to AIP-14119 XSD Translation Error Codes

AIP-14115 The inbound XML's base datatype is null: Cause: The root element's datatype of the inbound XML is null.
AIP-14116 The base datatype {0} is a scalar datatype, but the inbound XML root type is complex: Cause: The root element's datatype {0} is a scalar datatype, but the inbound XML root element is a complex datatype.
AIP-14117 The inbound XML is invalid, as the current element {0} of namespace {1} cannot appear in the XML instance after {2} from namespace {3} according to the datatype model: Cause: The inbound XML is invalid, as element {0} of namespace {1} cannot appear in the XML instance after {2} from namespace {3} according to the datatype model.
AIP-14118 Element {0}'s datatype member ID is invalid: Cause: Element {0}'s datatype member ID is invalid.
AIP-14119 There is an unsupported XML instance construct {0} within {1} in the native XML: Cause: There is an unsupported XML instance construct {0} within {1} in the native XML.

AIP-14321 to AIP-14325 Event Validation Error Codes

AIP-14321 Native event validation for the native event body element "{0}" failed in validation class "{1}".: Cause: Native event validation for native event instance element "{0}" failed in validation class "{1}".
AIP-14322 Native event validation for the native event body element "{0}" failed because validation class "{1}" cannot be found.: Cause: Native event validation for native event body element "{0}" failed because validation class "{1}" cannot be found.
AIP-14323 Native event validation for the native event body element "{0}" failed because "{1}" cannot be instantiated.: Cause: Native event validation for native event body element "{0}" failed because "{1}" cannot be instantiated.
AIP-14324 Native event validation for the native event body element "{0}" failed because "{1}" is not accessible.: Cause: Native event validation for native event body element "{0}" failed because "{1}" is not accessible.
AIP-14325 Native event validation for native event body element "{0}" to call out class "{1}" failed due to resource exception.: Cause: Native event validation for native event body element "{0}" to call out class "{1}" failed due to resource exception.

AIP-14401 to AIP-14406 Correlation Error Codes

AIP-14401 The number of operands exceeds the maximum for the correlation manager.: Cause: The number of operands exceeds correlation manager maximum specification.
AIP-14402 cannot find body element instance in the event instance: Cause: Could not find body element instance in the event instance.
AIP-14403 SQL exception thrown: Cause: Unexpected error: SQL exception thrown.
AIP-14404 DC exception thrown: Cause: Unexpected error: DC exception thrown.
AIP-14405 cannot find correlated events: Cause: Cannot find correlated events.
AIP-14406 cannot find corresponding native event instance: Cause: Cannot find correlated native event instance.

AIP-14451 to AIP-14455 Domain Value Map Error Codes

AIP-14451 cannot find the target column: Cause: Cannot find the target column.
AIP-14452 cannot find the row in domain value map: Cause: Cannot find the row in the domain value map.
AIP-14453 cannot find the column in domain value map: Cause: Could not find the column in the domain value map.
AIP-14454 No such party exists.: Cause: No such party exists.
AIP-14455 No domain for the party exists.: Cause: No domain for the party exists.

AIP-16020 to AIP-17997 Metadata Validation Rules Error Codes

AIP-16020 The business process {0} must have at least one approved agreement.: Cause: Associate at least one approved agreement with the business process.
AIP-16060 All collaborations within the agreement {0} must have a trading partner participant corresponding to each of its actors.: Cause: For all collaborations used within an agreement, associate both actors of that collaboration to an individual trading partner participant within that agreement.For example, if collaboration A and B are used, and collaboration A has actor 1 and 2, and collaboration B has actors 3 and 4, then there should be 4 trading partner participants, one for 1, one for 2, one for 3, and one for 4.
AIP-16061 The agreement {0} must have at least one native role.: Cause: Associate at least one native role with the agreement.
AIP-16062 The application agreement {0} must have exactly one application participant.: Cause: Provide only one application participant in the application agreement. For example, if the participant is an application participant there should only be one.
AIP-16063 The B2B agreement {0} must have exactly two trading partners.: Cause: In a B2B agreement, please have exactly two trading partners for all the trading partner participants owned by this agreement. For example, SUN and ORACLE can play several roles, but CISCO can not be part of this agreement because only two trading partners are allowed.
AIP-16064 In the B2B agreement {0} only one of the trading partners can be a local trading partner.: Cause: In the B2B agreement, specify only one local trading partner.
AIP-16065 The actor {0} of the hosted trading partner participant {1} must be an actor of a collaboration supported by the agreement {2} through one of its native roles.: Cause: The actor of a hosted trading partner participant must be an actor of a collaboration supported by the agreement through one of its native roles. For example, if Oracle is the hosted trading partner, and there is PIP3A4 buyer and PIPxxy seller associated with the agreement, then there must be two trading partner participants with Oracle as the trading partner, one whose supported actor is buyer, the other whose supported actor is seller.
AIP-16066 The complement of the hosted trading partner's supported actor {0} must be the actor used by the other trading partner for a given native role.: Cause: The complement of the hosted trading partner's supported actor should be the actor used by the other trading partner for a given native role. For example, if Oracle is the hosted trading partner who is playing buyer, then Sun, the remote trading partner, must be playing seller.
AIP-16067 Each application participant in the agreement {0} must have at least one party adapter type that matches the adapter type used by the native role.: Cause: For each application participant in an agreement, specify at least one party adapter type that matches the adapter type used by the native role.
AIP-16068 For the application participant there must be no more than one application delivery channel for every adapter type that matches the adapter type used by the native role.: Cause: For the application participant, specify no more than one application delivery channel for every adapter type that matches the adapter type used by the native role.
AIP-16069 The agreement {0} is only allowed to interact in one business process.: Cause: Allow the agreement to interact in only one business process.
AIP-16070 Both trading partner participants and application participants cannot coexist in the same agreement {0}.: Cause: Either remove the trading partner participants or the application participants from the same agreement.
AIP-16071 Agreement {0} must have one local trading partner.: Cause: Permit only one local trading partner for the B2B agreement.
AIP-16072 Each application participant in the agreement {0} should have at least one application delivery channel for every adapter type that is used.: Cause: For each application participant in an agreement, specify at least one application delivery channel for every adapter type that is used.
AIP-16073 Non-repudiation of origin/non-repudiation of receipt is enabled for trading partner delivery channel {0} but is not enabled for {1}.: Cause: If non-repudiation of origin or non-repudiation of receipt is enabled for one trading partner delivery channel, then the other trading partner delivery channel must also be enabled.
AIP-16074 Hosted trading partner has client authentication enabled, but the remote trading partner transport {1} does not have a security certificate.: Cause: If client authentication is enabled for the hosted trading partner, then there must be a security certificate for the remote trading partner.
AIP-16075 The agreement {0} must have at least one participant.: Cause: Provide at least one participant to the agreement.
AIP-16080 The delivery channel {0} of the trading partner participant must be a trading partner delivery channel.: Cause: If the participant is a trading partner participant the delivery channel must be a trading partner delivery channel.
AIP-16081 The trading partner identification, supported actor and trading partner delivery channel associated with the trading partner participant must be owned by the same trading partner.: Cause: The trading partner identification, supported actor and trading partner delivery channel directly associated with this trading partner participant must be owned by the same trading partner.
AIP-16082 The trading partner participant must have exactly one trading partner identification associated with it.: Cause: Associate a trading partner identification with the trading partner participant.
AIP-16084 There must be an adapter framework instance with trading partner override set to true.: Cause: Create an adapter framework instance whose trading partner override attribute value is true.
AIP-16085 The trading partner {0} participating as {1} in revision {2} of collaboration {3} must have at least one trading partner delivery channel.: Cause: Specify a trading partner delivery channel for the trading partner participant.
AIP-16086 The trading partner {0} participating as {1} in revision {2} of collaboration {3} must have no more than one trading partner delivery channel.: Cause: The trading partner participant must have no more than one trading partner delivery channel.
AIP-16100 The delivery channel {0} of the application participant must be an application delivery channel.: Cause: If the participant is an application participant, then the delivery channel must be an application delivery channel.
AIP-16101 The application delivery channel {0} must be owned by the application specified in the same participant.: Cause: The application delivery channel must be owned by the application specified in the same participant.
AIP-16102 There must be at least one adapter framework instance whose application override is set to true or the application associated with this participant must be associated with at least one adapter framework instance.: Cause: Either have at least one adapter framework instance whose application override is set to true or associate the application associated with this participant with at least one adapter framework instance.
AIP-16140 The trading partner {0} must have at least one trading partner identification.: Cause: Specify a trading partner identification for the trading partner.
AIP-16141 The document protocol parameter value {0} must be associated with the document protocol parameter of the same document protocol that the parent document protocol usage is associated with.: Cause: The document protocol parameter values must be associated with the document protocol parameters of the same document protocol that the parent document protocol usage is associated with.
AIP-16142 The document parameter value {0} must be associated with a document parameter of the same document type {1} that the parent document type usage is associated with.: Cause: A document parameter value must be associated with a document parameter of the same document type that the parent document type usage is associated with.
AIP-16143 The trading partner {0} can have only one association with the domain column for a specific domain value map.: Cause: A party can have only one association with the domain column for a specific domain value map.
AIP-16160 If the trading partner identification type is DUNS, then its value must be a 9 digit string.: Cause: Specify a 9 digit string for the DUNS trading partner identification type.
AIP-16161 If the trading partner identification type is DUNS+4, then its value must be a 13 digit string.: Cause: Specify a 13 digit string for the DUNS+4 trading partner identification type.
AIP-16162 The trading partner identification value {0} is not a unique DUNS number.: Cause: If a trading partner identification is a DUNS number then its value must be unique.
AIP-16180 The trading partner delivery channel {0} must have exactly one transport parameter.: Cause: Specify a transport parameter for the trading partner delivery channel.
AIP-16181 The trading partner delivery channel {0}, document exchange {1} and transport parameter {2} must all belong to the same trading partner.: Cause: The trading partner delivery channel, document exchange and transport parameter must all belong to the same trading partner.
AIP-16182 The transport protocol of the protocol endpoint associated with the trading partner delivery channel {0} via the transport parameter {1} must be one of the transport protocols supported by the exchange protocol of the document exchange of the same trading partner delivery channel.: Cause: The transport protocol of the protocol endpoint associated with the trading partner delivery channel through the transport parameter must be one of the transport protocols supported by the exchange protocol of the document exchange of the same trading partner delivery channel.
AIP-16183 If either non-repudiation of origin or non-repudiation of receipt are true then the document exchange {0} associated with the trading partner delivery channel {1} must have a digital signature.: Cause: If either non-repudiation of origin or non-repudiation of receipt are true then the document exchange associated with the trading partner delivery channel must have a digital signature.
AIP-16184 If encryption is true then the document exchange {0} associated with trading partner delivery channel {1} must have a digital envelope.: Cause: If encryption is true then the document exchange associated with the trading partner delivery channel must have a digital envelope.
AIP-16185 The trading partner delivery channel {0} must have exactly one document exchange.: Cause: A trading partner delivery channel must have exactly one document exchange.
AIP-16186 For trading partner delivery channel {0} header encryption override specified via the document exchange {1} should only be applied to protocol headers with a name of ServiceHeader only if encryption is enabled and the exchange protocol is RosettaNet version 02.00.: Cause: If encryption is true and if the exchange protocol of the document exchange has a name of RosettaNet and a version of 02.00, then a user can enable header encryption override on the protocol header with a name of ServiceHeader only. Note that even if header encryption override is specified for any other protocol header, it will not be encrypted.
AIP-16200 The document exchange {0} must have exactly one ExchangeProtocol.: Cause: Provide an exchange protocol for the document exchange.
AIP-16201 The exchange protocol {0} must be associated with the same trading partner {1} as the document exchange {2} via the business protocol.: Cause: The exchange protocol must be associated with the same trading partner as the document exchange through the business protocol.
AIP-16202 The protocol encryption override elements should map to the protocol elements of the exchange protocol {0} that is associated with the document exchange {1}.: Cause: The protocol encryption override elements should map to the protocol elements of the exchange protocol that is associated with the document exchange.
AIP-16203 The digital signature used within the document exchange {0} must be one of the supported security specifications of that document exchange.: Cause: The digital signature used within a document exchange must be one of the security specifications supported by that document exchange.
AIP-16204 The digital envelope used within the document exchange {0} must be one of the supported security specifications of that document exchange.: Cause: The digital envelope used within a document exchange must be one of the security specifications supported by that document exchange.
AIP-16205 The signing certificate in the document exchange {0} must be present when the digital signature is present.: Cause: If the digital signature is present then the signing certificate must also be present.
AIP-16206 The encryption certificate in the document exchange {0} must be present when the digital envelope is present.: Cause: If the digital envelope is present then the encryption certificate must also be present.
AIP-16207 The exchange protocol parameter value {0} of the document exchange {1} must be associated with an exchange protocol parameter of the same exchange protocol {2} that is associated with that document exchange.: Cause: The exchange protocol parameter values of the document exchange must be associated with exchange protocol parameters of the same exchange protocol that is associated with the document exchange.
AIP-16208 The certificate {0} associated with the document exchange {1} must belong to the same trading partner {2} as that document exchange.: Cause: A certificate associated with a document exchange must belong to the same trading partner as that document exchange.
AIP-16220 The transport parameter {0} must have at least one protocol endpoint.: Cause: Provide a protocol endpoint to the transport parameter.
AIP-16221 The trading partner of the transport parameter {0} must be the same trading partner as that of a certificate associated with an endpoint that is associated with that transport parameter if a certificate exists on that transport protocol.: Cause: The trading partner of the transport parameter must be the same trading partner as that of a certificate associated with an endpoint that is associated with that transport parameter if a certificate exists on that transport protocol.
AIP-16222 The transport parameter {0} must have no more one protocol endpoint.: Cause: Provide exactly one protocol endpoint to the transport parameter.
AIP-16223 The protocol endpoint associated with transport parameter {0} must belong to the same trading partner {1} as that of the transport parameter.: Cause: The protocol endpoint associated with this transport parameter must belong to the same trading partner as that of the transport parameter.
AIP-16240 A protocol endpoint must have an endpoint.: Cause: Provide an endpoint to the protocol endpoint.
AIP-16241 A protocol endpoint must have a certificate associated with it if and only if it has a transport protocol security associated with it.: Cause: If the protocol endpoint has a transport protocol security associated to it, then it must also have a certificate associated to it. Otherwise, it must not have a certificate associated with it.
AIP-16242 A protocol endpoint must have a transport protocol.: Cause: Provide a transport protocol to the protocol endpoint.
AIP-16261 Parameter values specified in the application delivery channel {0} must exist for all connection parameter objects of the adapter type that that application delivery channel is connected to.: Cause: Specify parameter values in the application delivery channel that exist for all connection parameter objects of the adapter type that application delivery channel is connected to.
AIP-16264 The connection parameter value {0} should match its datatype {1}.: Cause: Provide a connection parameter value that matches its datatype. For example, if a connection parameter, port, is of type integer, then the value must be a valid integer.
AIP-16265 The connection parameter value {0} must be one of the domain values of that connection parameter.: Cause: Provide a connection parameter value that is one of the domain values of that connection parameter.
AIP-16280 The connection factory associated with the adapter type {0} must belong to the same adapter provider {1} that the adapter type belongs to.: Cause: Associate a connection factory with the adapter type that belongs to the same adapter provider that the adapter type belongs to.
AIP-16281 The connection spec associated with the adapter type {0} must belong to the same adapter provider.: Cause: Associate a connection spec with the adapter type that belongs to the same adapter provider that the adapter type belongs to.
AIP-16282 The adapter type {0} must have exactly one connection factory associated with it.: Cause: Associate exactly one connection factory with the adapter type.
AIP-16300 If, in the adapter framework instance {0} the application override is set to true, then it must have no party adapter framework instances for applications.: Cause: Either remove all party adapter framework instances for that adapter framework instance's applications or set the application override to false.
AIP-16301 If, in the adapter framework instance {0} the trading partner override is set to true, then it must have no party adapter framework instances for trading partners.: Cause: Either remove all party adapter framework instances for that adapter framework instance's trading partners or set the trading partner override to false.
AIP-16320 For business process {0}, there must be a tree structure to all other nodes.: Cause: From a business process role there must be a tree structure to all other roles. It cannot be a network.
AIP-16321 The native role {0} can only be used with one business process.: Cause: Native roles can only be used with one business process.
AIP-16322 The business process: {0} contains steps (spanning one or more roles) illegally connected in a loop. Step: {1} was detected as being part of the following loop: {2}: Cause: A given business process cannot contain steps connected, using control flows, dataflows within roles and dataflows across roles, such that there is a loop or cycle.
AIP-16323 The business process: {0} contains an invalid OR step: {1}. None of the paths coming into [{1}] from [{2}, {3}] are mutually exclusive and hence will result in runtime race conditions.: Cause: A given business process cannot contain an OR step such that control flows into it are not mutually exclusive. This is to prevent resulting runtime race conditions.
AIP-16324 The business process: {0} contains an invalid step: {1}. The paths shown below coming into [{1}] from [{2}, {3}] are mutually exclusive and hence will result in indefinite wait during runtime. (1) Path: {4}, (2) Path: {5}.: Cause: A given business process cannot contain a step such that control flows into it are mutually exclusive. This is to prevent resulting infinite wait at runtime.
AIP-16325 The business process: {0} contains an invalid port: {1}. None of the paths coming into [{1}] from [{2}, {3}] are mutually exclusive and hence will result in runtime race conditions.: Cause: A given business process cannot contain a port such that dataflows into it are not mutually exclusive. This is to prevent resulting runtime race conditions.
AIP-16340 The process role {0} must have exactly one enclosing composite step that is not a step.: Cause: Every process role must have exactly one enclosing composite step that is not a step.
AIP-16341 The port {0} of business process {1} can accept or send only event types and not datatypes.: Cause: The ports of a business process can accept or send only event types (and not datatypes).
AIP-16342 The event type {0} used in the port of the business process {1} must be of type business event type.: Cause: All of the event types used in the ports of a business process must be business event types.
AIP-16344 The business process {0} must not have any inbound data flow groups associated with it.: Cause: There must be no inbound data flow groups associated with a business process.
AIP-16345 The business process {0} must have at least one outbound data flow group associated with it.: Cause: There must be one or more outbound data flow groups associated with a business process.
AIP-16380 The business role {0} must have exactly one enclosing composite step that is not a step.: Cause: A business role must have exactly one enclosing composite step that is not a step.
AIP-16381 The port {0} of business role {1} can accept or send only event types and not datatypes.: Cause: The ports of a business role can accept or send only event types (and not datatypes).
AIP-16382 The event type {0} used in the port of the business role {1} must be of type business event type.: Cause: All of the event types used in ports of a business role must be business event types.
AIP-16384 The business role {0} must have at least one inbound data flow group associated with it.: Cause: There must be at least one inbound data flow group associated with a business role.
AIP-16386 The business role {0} must have at least one outbound data flow group associated with it.: Cause: There must be at least one outbound data flow group associated with a business role.
AIP-16387 The business role {0} must have no more than one inbound data flow group associated with it.: Cause: There must be no more than one inbound data flow group associated with a business role.
AIP-16388 Business role ports can be data flow bound to multiple binding role ports only if the data flows belong to different data flow groups.: Cause: If there is a port on a business role that has more than one data flow to a port owned by another role, then each such data flow must be owned by a different data flow group and the other roles must be binding roles.
AIP-16389 Data flow criteria is required on the data flow groups to distinguish between multiple binding roles that a business role is associated with.: Cause: If a business role has more than one data flow group that associates it with different binding roles, then each data flow group must have a data flow criteria.
AIP-16390 A data flow criteria with a unique priority among all data flow groups is required on the data flow groups to distinguish between multiple binding roles that a business role is associated with.: Cause: If a business role has more than one data flow group that associates it with different binding roles, then each data flow group must have a data flow criteria with a unique priority among all of the data flow groups.
AIP-16393 The same business role ports must be used in all data flow groups between a business role and different binding roles.: Cause: If a business role has more than one data flow group that associates it with different binding roles, then each data flow group must contain data flows to and from the same business role ports.
AIP-16420 The binding role {0} must have exactly one enclosing composite step that is not a step.: Cause: Every binding role must have exactly one enclosing composite step that is not a step.
AIP-16421 The port {0} of binding role {1} can accept or send only event types and not datatypes.: Cause: The ports of a binding role can accept or send only event types (and not datatypes).
AIP-16422 The event type {0} used in the port of this binding role {1} must be either of type application event type and native event type or of application event type and business event type.: Cause: All of the event types used in the ports of a binding role must be of type application event type and native event type or of type application event type and business event type.
AIP-16424 The binding role {0} must have exactly one inbound data flow group associated with it.: Cause: There can be at most one inbound data flow group associated with a binding role.
AIP-16426 The binding role {0} must have at least one outbound data flow group associated with it.: Cause: A binding role must have at least one outbound data flow group associated with it.
AIP-16428 The binding role {0} must have no more than one inbound data flow group associated with it.: Cause: A binding role can have no more than one inbound data flow group associated with it.
AIP-16460 The application role {0} must have exactly one enclosing composite step that is not a step.: Cause: Every application role must have exactly one enclosing composite step that is not a step.
AIP-16461 The port {0} of application role {1} can accept or send only event types and not datatypes.: Cause: The ports of an application role can accept or send only event types (and not datatypes).
AIP-16462 The event type {0} used in the port of the application role {1} must be of type application event type.: Cause: All of the event types used in the ports of an application role must be of type application event type.
AIP-16464 The application role {0} must have at least one inbound data flow group associated with it.: Cause: There must be at least one inbound data flow group associated with an application role.
AIP-16466 The application role {0} must have at least one outbound data flow group associated with it.: Cause: There must be at least one outbound data flow group associated with an application role.
AIP-16467 The application role {0} must have no more than one inbound data flow group associated with it.: Cause: An application role must not have more than one inbound data flow group associated with it.
AIP-16520 The native role {0} must have exactly one enclosing composite step that is not a step.: Cause: Every native role must have exactly one enclosing composite step that is not a step.
AIP-16521 The port {0} of native role {1} can accept or send only event types and not datatypes.: Cause: The ports of a native role can accept or send only event types (and not datatypes).
AIP-16522 The event type {0} used in the port of the native role {1} must be of type native event type.: Cause: All of the event types used in the ports of a native role must be of type native event type.
AIP-16523 In native role {0}, if there are multiple out facing receiving ports (ports not bound to other ports but to interaction usages) and the non-initiating ports are receiving, then a correlation must be defined between the native event {1} of the non-initiating port {2} and the native event of an initiating port (a port connected to an initiating step).: Cause: Define a correlation expression for the native event of the non-initiating port and the native event of the initiating port.
AIP-16524 The native role {0} must have at least one inbound data flow group associated with it.: Cause: A native role must have at least one inbound data flow group associated with it.
AIP-16525 The port {0} of native role {1} must have a data flow to a binding role port or it must be associated with an interaction.: Cause: Either provide a data flow to a binding role port or associate the port with an interaction.
AIP-16526 The native role {0} must not have any outbound data flow groups associated with it.: Cause: There must not be any outbound data flow groups associated with a native role.
AIP-16527 Port {0} owned by native role {1} must be associated with either two data flows or one data flow and one interaction.: Cause: Ports owned by a native role are associated with either two data flows (to a step port and a port on a binding role) or one data flow (to a step port) and one interaction.
AIP-16529 The interaction usage tied to port {0} must also be tied to another port owned by the same composite step.: Cause: An interaction usage tied to a port must also be tied to another port owned by the same composite step.
AIP-16530 The record type of the native event type of the input port {0} must match the in record type of the inbound interaction it is tied to via the interaction usage.: Cause: A record type of a native event type of an input port must match the in record type of the inbound interaction it is tied to through the interaction usage.
AIP-16531 The record type of the native event type of input port {0} must match the out record type of the outbound interaction it is tied to via the interaction usage.: Cause: A record type of a native event type of an input port must match the out record type of the outbound interaction it is tied to through the interaction usage.
AIP-16532 The record type of the native event type of output port {0} must match the in record type of the outbound interaction that it is tied to via the interaction usage.: Cause: A record type of a native event type of an output port must match the in record type of the interaction that it is tied to through the interaction usage.
AIP-16533 If a port is tied to an interaction usage that is tied to another port, then one port must be out (receiving = false) and the other must be in (receiving = true).: Cause: If a port is tied to an interaction usage that is tied to another port, then one port must be out and the other must be in.
AIP-16534 If a port is tied to an interaction usage that has only an in record type, then the port must be an input port if the interaction is inbound or an output port if the interaction is outbound.: Cause: If a port is tied to an interaction usage that has only an in record type, then the port must be an input port if the interaction is inbound or an output port if the interaction is outbound.
AIP-16535 The native format {0} associated with the event body element {1} of the native event type {2} must be a supported native format through the native role {3}.: Cause: The native format associated with each event body element of a native event type must be a supported native format through the native role.
AIP-16540 The enclosing step {0} associated with role {1} must not be owned by any other step.: Cause: An enclosing step of a role must not be owned by any other step.
AIP-16542 Only one start step is allowed in role {0}.: Cause: Only one start step is allowed in a given role.
AIP-16545 The role {0} must have at least one input port and one output port.: Cause: Provide at least one input port and one output port to the specified role.
AIP-16546 The role {0} must have at least two data flows binding its role ports.: Cause: Provide at least two data flows that bind the ports of the role.
AIP-16548 The port {0} of step {1} owned by role {2} must be associated with that owning composite step as an available port.: Cause: All ports of steps owned by a given role must be associated with that role as available ports.
AIP-16549 The steps within role {0} must not form a loop.: Cause: The steps within a given role must not form a loop.
AIP-16550 The step {0} cannot own another step.: Cause: No step can own another step.
AIP-16560 The passthrough step {0} must have at least one outbound control flow or data flow to another step.: Cause: Provide either an outbound control flow or a data flow for the step to another step.
AIP-16561 The passthrough step {0} can only own a port.: Cause: A passthrough step can only own a port.
AIP-16562 The passthrough step {0} must have at least two ports.: Cause: Provide at least two ports to the passthrough step.
AIP-16563 The passthrough step {0} must have no more than two ports.: Cause: Provide at most two ports to the passthrough step.
AIP-16580 The transformation step {0} must have at least one outbound control flow or data flow to another step.: Cause: Provide either an outbound control flow or a data flow for the step to another step.
AIP-16581 The map parameter {0} associated with the output Port {1} and the transformation map associated with the transformation step {2} must be a target parameter.: Cause: Each output port associated with a transformation step must be associated with an output map parameter that is associated with the transformation map that is associated with the same transformation step.
AIP-16583 The map parameter {0} associated with the input port {1} and the transformation map associated with the transformation step {2} must be a source parameter.: Cause: Each input port associated with a transformation step must be associated with an input map parameter that is associated with the transformation map that is associated with the same transformation step.
AIP-16584 The transformation step {0} can only own ports.
AIP-16585 The transformation step {0} must be associated with exactly one transformation map.: Cause: A transformation step must be associated with exactly one transformation map.
AIP-16586 The map parameter {0} of the transformation map {1} associated with the transformation step {2} must have a port associated with it that is owned by that transformation step.: Cause: A transformation step must own at least one port for each event map parameter and each datatype map parameter.
AIP-16587 The map parameter {0} of the transformation map associated with the transformation step {1} must not have more than one port associated with it that is owned by that transformation step.: Cause: There must be no more than one port for each event map parameter and each datatype map parameter.
AIP-16588 The datatype of datatype map parameter {0} must match the datatype of the port.: Cause: The datatype of a datatype map parameter must match the datatype of the port.
AIP-16589 The datatype or event type of event map parameter {0} must be the same as the datatype or event type of the port.: Cause: The datatype or event type of an event map parameter must be the same as the datatype or event type of the port.
AIP-16590 For an event map parameter associated with a datatype, there must be a datatype associated with a port of the transformation step. Similarly, for an event map parameter associated with an event type, there must be an event type associated with the Port.: Cause: For an event map parameter associated to a datatype, there must be a datatype associated to a port of the transformation step. Similarly, for an event map parameter associated to an event type, there must be an event type associated to the port.
AIP-16591 The transformation step {0} must have one output port marked as a return code port.: Cause: A transformation step must have one return code port.
AIP-16600 The translation step {0} must have at least one outbound control flow or data flow to another step.: Cause: Provide either an outbound control flow or a data flow for the step to another step.
AIP-16604 The translation step {0} can only own ports.: Cause: A translation step can only own ports.
AIP-16606 The translation step {0} must have at least two ports that are not return code ports.: Cause: Provide at least two ports that are not return code ports to the translation step.
AIP-16607 The translation step {0} must have no more than two ports that are not return code ports.: Cause: Provide no more than two ports that are not return code ports to the translation step.
AIP-16608 The translation step {0} must have one output port marked as a return code port.: Cause: A translation step must have one return code port.
AIP-16609 The translation step {0} must own at least one input port and at least one output port that is not a return code port.: Cause: Provide at least one input port and at least one output port that is not a return code port to the translation step.
AIP-16610 The translation step {0} can own at most one input port and at most one output port that is not a return code port.: Cause: A translation step can own at most one input port and at most one output port that is not a return code port.
AIP-16611 If application event {0} is on the outgoing Port {1} of translation step {2} then the native event must be on the incoming port {3}.: Cause: If an application event is on the outgoing port of a translation step, then the native event must be on the incoming port.
AIP-16612 If application event {0} is on the incoming port {1} of translation step {2} then the native event must be on the outgoing port {3}.: Cause: If an application event is on the incoming port of a translation step, then the native event must be on the outgoing port.
AIP-16620 The condition step {0} must have at least one outbound control flow or data flow to another step.: Cause: Provide either an outbound control flow or a data flow for the step to another step.
AIP-16621 The output port {0} of condition step {1} must correspond with an output parameter of the condition it is associated with.: Cause: The output ports of a condition step must correspond with the output parameters of the condition it is associated with.
AIP-16623 The input port {0} of condition step {1} must correspond with the input parameters of the condition it is associated with.: Cause: The input ports of a condition step must correspond with the input parameters of the condition it is associated with.
AIP-16624 The condition step {0} can only own ports.: Cause: A condition step can only own ports.
AIP-16625 The condition step {0} must be associated with exactly one condition expression.: Cause: Association a condition expression with the condition step.
AIP-16626 The condition step {0} must have at least one input port.: Cause: A condition step must have at least one input port.
AIP-16627 The condition step {0} can have at most one input port.: Cause: A condition step can have at most one input port.
AIP-16628 The condition step {0} must have at least two outbound control flows.: Cause: A condition step must have at least two outbound control flows.
AIP-16629 The condition step {0} can have at most two outbound control flows.: Cause: A condition step can have at most two outbound control flows.
AIP-16630 The condition step {0} must have one outbound control flow with guard value set to true or success and one outbound control flow with guard value set to false or failure.: Cause: A condition step must have one outbound control flow with guard value set to true or success and one outbound control flow with guard value set to false or failure.
AIP-16631 The condition step {0} must have one output port marked as a return code port.: Cause: A condition step must have one return code port.
AIP-16640 The validate step {0} must have at least one outbound control flow or data flow to another step.: Cause: Provide either an outbound control flow or a data flow for the step to another step.
AIP-16644 The validate step {0} can only own ports.: Cause: A validate step can only own ports.
AIP-16645 The validate step {0} must be associated with exactly one validation.: Cause: A validate step must be associated with exactly one validation.
AIP-16660 The receiving port {0} of the initiating step {1} is connected to a non-receiving port {2} of the step {3} instead of a receiving port of a role.: Cause: The receiving port of an initiating step must be connected to a receiving role port and not to a non-receiving step port.
AIP-16661 The port {0} of role {1} must be owned by a data flow group that contains another port connected to a different role.: Cause: A role port must be owned by a data flow group that contains another role port that is connected to a neighboring role.
AIP-16662 The port {0} must be associated with either one event type or one datatype, but not both.: Cause: The port is associated to both an event type and a datatype. It should be associated either to the event type or the datatype.
AIP-16663 The composite step associated with port {0} must be the owner of the step that owns the port.: Cause: Every port is associated with the owning composite step of its owning step. This association is set incorrectly. Contact Oracle Support Services.
AIP-16664 The initiating flag of port {0} can only be set to true if that port belongs to the start step or if that port is connected to another port that belongs to the start step.: Cause: The initiating flag is set to true only on a port that belongs to start step or on a port that is connected to a port that belongs to start step.
AIP-16665 The port {0} can only be associated with an interaction if it belongs to a native role.: Cause: A port that is not a native role port cannot be associated with an interaction. Associate this port with the port of another role, and not with an interaction.
AIP-16666 The record type of the native event associated with the receiving port {0} must match the out record type of the inbound interaction with which it is associated.: Cause: The record type of the native event type associated with the port does not match the out record type of the inbound interaction with which it is associated. Make sure the record types are the same.
AIP-16667 The port {0} can only be associated with a datatype if it is not a role port.: Cause: The port is associated with a datatype even though it is associated with a role and not a step. A role port must only be associated with an event type.
AIP-16668 The port {0} must have one source and one target transition. Only outgoing (associated with an interaction) native role ports and outgoing (attached to a binding role port) business role ports involved in branching may not have exactly one source and one target transition.: Cause: This port does not have a source and target transition. Associate this port with two ports, one of which is the source and the other of which is the target.
AIP-16669 The record type of the native event of the output port {0} must match the in record type of the outbound interaction with which it is associated.: Cause: The record type of the native event type associated with the output port does not match the in record type of the outbound interaction with which it is associated. Make sure the record types are the same.
AIP-16670 The port {0} of role {1} must have an event type.: Cause: Associate an event type with the role port.
AIP-16671 The port {0} of step {1} must have either an event type or a datatype.: Cause: Associate either an event type or a datatype with the step port.
AIP-16681 The native event {0} must be associated with a record type.: Cause: A native event must be associated with a record type.
AIP-16682 The native event {0} must be associated with exactly one adapter exchange protocol.: Cause: A native event must be associated with exactly one adapter exchange protocol.
AIP-16683 The event body elements of native event type {0} must be associated one to one with the record type elements of the record type that is associated with that native event type.: Cause: The event body elements of a native event type must be associated one to one with the record type elements of the record type that is associated with that native event type.
AIP-16684 The native event type {0} must point to an application event type.: Cause: A native event type must point to an application event type, and the application event type must point to the same native event type.
AIP-16685 The adapter exchange protocol for native event type {0} must match the adapter exchange protocol for the record type.: Cause: The native event type and the record type must have the same adapter exchange protocol.
AIP-16686 The native event body element {0} of native event type {1} must point to a native datatype.: Cause: Associate a native datatype with the record type element.
AIP-16687 The native event type {0} must point to another event type.: Cause: Associate the native event type with another event type.
AIP-16689 The event body element {0} of native event type {1} is not associated with a translator.: Cause: Associate the event body element of the native event type with a translator.
AIP-16700 Each event body element of the application event type {0} must map to a datatype.: Cause: Map each event body element of the application event type to a datatype.
AIP-16701 The event type classification of datatype {0} associated with event body element {1} must be application event.: Cause: A datatype can only be associated with an event body element whose associated event type is the same as the event type class of the datatype. For example, application datatypes can only be associated with application event body elements.
AIP-16703 Application event type {0} does not have a native event type.: Cause: Associate a native event type with the application event type.
AIP-16704 Application event type {0} does not point to an event type.: Cause: Associate the application event type with an event type.
AIP-16705 The application event type {0} must be associated with an adapter exchange protocol.: Cause: Associate an adapter exchange protocol with the application event type.
AIP-16720 Each event body element of business event type {0} must map to a datatype.: Cause: Map each event body element of the business event type to a datatype.
AIP-16721 The event type classification for datatype {0} associated with the event body element {1} must be the same as the business event type associated with the event body element.: Cause: A datatype can only be associated with an event body element whose associated event type is the same as the event type class of the datatype. For example, business datatypes can only be associated with business event body elements.
AIP-16723 The business event type {0} must not have the application event to native event aassociation.: Cause: The application event to native event association is not permitted on business event types.
AIP-16724 The business event type {0} must not be associated with an adapter exchange protocol.: Cause: Remove the association between the business event type and the adapter exchange protocol.
AIP-16740 Multiple union member datatype intersection objects (associated with one union member) must each in turn be associated with different datatype objects.: Cause: Multiple union member datatype intersection objects (associated with one union member) each in turn should be associated with different datatype objects. For example, the intersections of a union member must each point to different datatypes.
AIP-16741 The complex datatype with name {0}, datatype namespace {1}, event type class {2} and ref type only {3} already exists.: Cause: Each named datatype must have a unique combination of name, datatype namespace, event type class and ref type only.
API-16742 The name of compound member {0} in datatype {1} does not match the name {2} of the ref type only datatype it refers to.: Cause: If the member of a datatype is a ref type only, then the member must have the same name as its type.
AIP-16743 The complex datatype {0} must be a subset of the complex datatype that it is restricted by.: Cause: If complex datatype is derived by restriction from another datatype, then it must be a subset of what the other datatype is. For example, if there is a datatype, SHIRT, that has a complex datatype member, size, that is a choice of int{8, 10} or char{S, M}, and there is also a datatype MY_SHIRT that is derived from SHIRT, then MY_SHIRT can also have a size choice int{8,10}, but it cannot have a size choice int{8,10,12}.
AIP-16744 Complex datatype {0} cannot be handled by translation because an instance cannot be exactly matched to it.: Cause: The complex datatype cannot be handled by translation because an instance cannot be exactly matched to it.
AIP-16745 There can be at most one member with member group head set to true within complex datatype {0}.: Cause: Ensure that there is only one member with member group head set to true in the complex datatype.
AIP-16746 Within complex datatype {0} whose member group type is set to true, there must be at least two members.: Cause: Provide at least two members to the complex datatype.
AIP-16747 Within complex datatype {0} whose member group type is set to true, there must not be any anonymous members.: Cause: Provide names for all members of the complex datatype.
AIP-16748 Complex datatype member {0} in complex datatype {1} must be derived from member group head complex datatype member {2}.: Cause: All complex datatype members within a complex datatype must be derived from the complex datatype member whose isMemberGroupHead value is true.
AIP-16749 Element wildcard member {0} in complex datatype {1} must be the last element member of that datatype.: Cause: If a complex datatype has an element wildcard member, then that member must be the last element member of the complex datatype.
AIP-16760 The default value {0} of scalar member {1} referring to scalar datatype {2} is not a valid value of the enumeration facet associated with that datatype.: Cause: If the default value of a scalar member is set, and its scalar datatype is associated with an enumeration facet, then that facet must have a valid value that equals the default value of the scalar member.
AIP-16761 The scalar member {0} in datatype {1} must be associated with either a scalar datatype or a facet.: Cause: Associate the scalar member with either a scalar datatype or a facet.
AIP-16762 The fixed value {0} of scalar member {1} referring to scalar datatype {2} is not a valid value of the enumeration facet associated with that datatype.: Cause: If the fixed value of a scalar member is set and its scalar datatype is associated with an enumeration facet then that facet must have a valid value that equals the fixed value of that scalar member.
AIP-16763 The scalar datatype {0} must be a subset of the base scalar datatype {1} by which it is restricted.: Cause: A scalar datatype that is derived by restriction from another scalar datatype must be a subset of the scalar datatype by which it is restricted.
AIP-16764 Scalar datatype {0} can have only one facet of type enumeration.: Cause: A scalar datatype can have only one enumeration facet, but this facet can have multiple valid values.
AIP-16767 The scalar datatype {0} cannot own mutually exclusive facets minInclusive and minExclusive.: Cause: A scalar datatype cannot own both a facet with a facet type of minInclusive and a facet with a facet type of minExclusive.
AIP-16768 The scalar datatype {0} cannot own mutually exclusive facets maxInclusive and maxExclusive.: Cause: A scalar datatype cannot own both a facet with a facet type of maxInclusive and a facet with a facet type of maxExclusive.
AIP-16769 The scalar datatype {0} can own at most one facet of each facet type.: Cause: A scalar datatype cannot own more than one facet of a particular facet type.
AIP-16770 For the scalar datatype {0}, the value of its minLength facet must be less than or equal to the value of its maxLength facet.: Cause: If a scalar datatype owns both a minLength facet and a maxLength facet, the minLength facet value must be less than or equal to the maxLength facet value.
AIP-16771 The value of the minInclusive facet of scalar datatype {0} must be less than or equal to the value of its maxExclusive or maxInclusive facet.: Cause: For a scalar datatype that owns a facet with a facet type of minInclusive and one with a facet type of either maxInclusive or maxExclusive, the facet value of the minInclusive facet must be less than or equal to the facet value of the maxInclusive or maxExclusive facet.
AIP-16772 The value of the minExclusive facet of scalar datatype {0} must be less than or equal to the value of its maxExclusive or maxInclusive facet.: Cause: For a scalar datatype that owns a facet with a facet type of minExclusive and one with a facet Type of either maxInclusive or maxExclusive, the facet value of the minInclusive facet must be less than or equal to the facet value of the maxInclusive or maxExclusive facet.
AIP-16773 The scalar datatype with name {0}, datatype namespace {1}, event type class {2} and ref type only {3} already exists.: Cause: Each named datatype must have a unique combination of name, datatype namespace, event type class and ref type only.
AIP-16774 The name of compound member {0} in datatype {1} does not match the name {2} of the ref type only datatype it refers to.: Cause: If the member of a datatype is a ref type only, then the member must have the same name as its type.
AIP-16775 Scalar member {0} in datatype {1} does not match the name of its ref type only scalar type {2}.: Cause: A scalar member must have the same name as its scalar type if its scalar type is ref type only.
AIP-16776 Scalar datatype {0} in namespace {1} must have a base scalar type.: Cause: Every scalar datatype must be derived from one of the core types.
AIP-16780 The array datatype {0} must not refer to itself in any form of a loop.: Cause: An array datatype cannot refer to itself in any form of a loop.
AIP-16781 The array datatype {0} does not refer to a datatype.: Cause: Associate the array datatype with either a complex datatype, scalar datatype or an array datatype.
AIP-16782 The array datatype with name {0}, datatype namespace {1}, event type class {2} and ref type only {3} already exists.: Cause: Each named datatype must have a unique combination of name, datatype namespace, event type class and ref type only.
API-16783 The name of compound member {0} in datatype {1} does not match the name {2} of the ref type only datatype it refers to.: Cause: If the member of a datatype is a ref type only, then the member must have the same name as its type.
AIP-16820 Only one data flow group can exist between two process roles.: Cause: Only one data flow group can exist between two process roles. For example, if there is a process role, R1 and a process role R2, R1 and R2 cannot own two data flow groups that go between R1 and R2. If there is another process role, R3, then R1 is allowed to own a data flow group that goes between R1 and R2, and a data flow group that goes between R1 and R3.
AIP-16821 The data flow group {0} can exist only between the following: (1) A native role as the out role and a binding role as the in role, (2) A binding role as the out role and an application role as the in role, (3) A binding role as the out role and a business role as the in role, (4) A business role as the out role and a business process as the in role, (5) An application role as the out role and a binding role as the in role.: Cause: Connect the data flow group between one of these valid combinations.
AIP-16824 The data flow group {0} must own at least one transition.: Cause: Every data flow group must own at least one transition.
AIP-16825 Every transition owned by the data flow group {0} must be between ports owned by different composite steps.: Cause: Every transition owned by a data flow group must be between ports owned by different composite steps.
AIP-16826 The data flow group {0} can only own a data flow criteria if it associates a business role and a binding role.: Cause: Only a data flow group that associates a business role and a binding role can own a data flow criteria.
AIP-16840 The adapter exchange protocol {0} associated with the data flow criteria must belong to the adapter type also associated with the data flow criteria if it exists.: Cause: The adapter exchange protocol associated with a data flow criteria must belong to the adapter type also associated with the data flow criteria if it exists.
AIP-16841 If an adapter type is associated with the data flow criteria then an adapter exchange protocol must also be associated with the data flow criteria.: Cause: If an adapter type is associated with the data flow criteria then an adapter exchange protocol must also be associated with the data flow criteria.
AIP-16860 A control flow must be between steps, and not ports.: Cause: Connect the control flow between steps. Otherwise, change the control flow to a data flow.
AIP-16861 A control flow must have different steps as its source and target.: Cause: The same step cannot be the source and target of a control flow. Connect the control flow between different steps.
AIP-17862 A control flow cannot be connected to port {0}.: Cause: A control flow cannot be connected to a port. Only data flows can be connected to ports. Connect the control flow between steps.
AIP-16880 A data flow between ports {0} and {1} must be between ports associated with the same datatype or event type.: Cause: Associate the data flow only between ports that are associated with the same datatype or event type.
AIP-16881 The source port {0} and target port {1} of a data flow must be different.: Cause: The same port cannot be the source and the target for a data flow. Connect the data flow between different ports.
AIP-16882 A data flow between ports {0} and {1} must be used in one of the following situations: (1) From a role receiving port to a step receiving port, (2) From an output port of a step to an output port of a role, (3) From an output port of a step to a receiving port of a step and (4) From an output port of a role to a receiving port of a role.: Cause: Make sure that the data flow is used in one of the above situations.
AIP-16883 The ports {0} and {1} of a data flow owned by data flow group {2} must be ports of different roles.: Cause: The data flow owned by a data flow group must be between role ports of different roles.
AIP-16884 A data flow between port {0} of step {1} and port {2} of step {3} within a role must be between ports within the same role. For example, either between steps within the role or between a step port and the role port.: Cause: The source and targets of the data flow within a role must be between ports of steps within the role or between a step port and a role port.
AIP-16900 Person {0} belongs to a remote trading partner and therefore must not have any associations to user enrollment or access control entry.: Cause: Persons belonging to remote trading partners must not be allowed privileged access.
AIP-16920 The application {0} must be associated with an application type.: Cause: Associate the application with an application type.
AIP-16921 The application {0} can have only one association with the domain column for a specific domain value map.: Cause: Provide only one association from the application to the domain column for a specific domain value map.
AIP-16940 The and step {0} must have at least one in control flow and at least one out control flow.: Cause: The and step must have at least one control flow where it is the target and at least one control flow where it is the source.
AIP-16941 The and step {0} must have at least one outbound control flow or data flow to another step.: Cause: Provide either an outbound control flow or a data flow for the step to another step.
AIP-16960 The or step {0} must have at least one in control flow and at least one out control flow.: Cause: The or step must have at least one control flow where it is the target and at least one control flow where it is the source.
AIP-16961 The or step {0} must have at least one outbound control flow or dataflow to another step.: Cause: Provide either an outbound control flow or a data flow for the step to another step.
AIP-16980 The split step {0} must have at least one outbound control flow or dataflow to another step.: Cause: Provide either an outbound control flow or a data flow for the step to another step.
AIP-16982 The split step {0} can only own ports.: Cause: A split step can only own ports.
AIP-16983 The split step {0} must own at least one input port and at least one output port.: Cause: Provide at least one input port and at least one output port to the split step.
AIP-16984 The split step {0} can own at most one input port.: Cause: Provide a single input port to the split step.
AIP-17000 The set adapter type step {0} must have at least one outbound control flow or dataflow to another step.: Cause: Provide either an outbound control flow or a data flow for the step to another step.
AIP-17002 The set adapter type step {0} can only own ports.: Cause: A set adapter type step can only own ports.
AIP-17003 The set adapter type step {0} must be associated with exactly one adapter type.: Cause: Associate an adapter type with the set adapter type step.
AIP-17004 The set adapter type step {0} can own at most one input port and at most one output port.: Cause: Provide at most one input port and at most one output port to the set adapter type step.
AIP-17005 The set adapter type step {0} must own at least one input port and at least one output port.: Cause: Provide at least one input port and at least one output port to the set adapter type step.
AIP-17020 The set party step {0} must have at least one outbound control flow or data flow to another step.: Cause: Provide either an outbound control flow or a data flow for the step to another step.
AIP-17022 The set party step {0} can only own ports.: Cause: A set party step can only own ports.
AIP-17023 The set party step {0} must be associated with exactly one application or trading partner.: Cause: Associate either an application or a trading partner with the set party step.
AIP-17024 The set party step {0} can own at most one input port and at most one output port.: Cause: Provide at most one input port and at most one output port to the set party step.
AIP-17025 The set party step {0} must own at least one input port and at least one output port.: Cause: Provide at least one input port and at least one output port to the set party step.
AIP-17040 The set adapter exchange protocol step {0} must have at least one outbound control flow or data flow to another step.: Cause: Provide either an outbound control flow or a data flow for the step to another step.
AIP-17042 The set adapter exchange protocol step {0} can only own ports.: Cause: A set adapter exchange protocol step can only own ports.
AIP-17043 The set adapter exchange protocol step {0} must be associated with exactly one adapter exchange protocol.: Cause: Associate an adapter exchange protocol with the set adapter exchange protocol step.
AIP-17044 The set adapter exchange protocol step {0} can own at most one input port and at most one output port.: Cause: Provide at most one input port and at most one output port to the set adapter exchange protocol step.
AIP-17045 The set adapter exchange protocol step {0} must own at least one input port and at least one output port.: Cause: Provide at least one input port and at least one output port to the set adapter exchange protocol step.
AIP-17050 The event transformation map {0} must contain at least one map parameter referring to an event type.: Cause: An event transformation map must contain at least one map parameter referring to an event type.
AIP-17060 The datatype transformation map {0} must contain at least one parameter referring to a datatype.: Cause: A datatype transformation map must contain at least one parameter referring to a datatype.
AIP-17061 The datatype transformation map {0} must contain at least one transformation block.: Cause: The datatype transformation map which has been declaratively defined must contain at least one transformation block.
AIP-17080 The transformation statement {0} which is not invoking a map or function within transformation map {1} must contain at least one transformation statement.: Cause: A transformation statement which is not invoking a map or function must own at least one other transformation statement.
AIP-17081 The datatype transformation map {0} has been implemented as a java callout, hence it can not have any transformation statements within it.: Cause: If the datatype transformation map has been implemented as a java callout it can not have any transformation statements within it.
AIP-17082 The transformation statement {0} within transformation map {1} can only be contained within a condition because it is marked to be executed on the false evaluation of a condition.: Cause: A transformation statement marked to be executed on the false evaluation of a condition can only be contained within a condition.
AIP-17090 The transformation rule within transformation map {0} must provide a binding for parameter {1} of the invoked datatype transformation map {2}.: Cause: A transformation rule invoking a datatype transformation map needs to provide bindings for all parameters of the invoked map.
AIP-17100 The condition {0} within transformation map {1} must contain at least one transformation statement.: Cause: A condition must own at least one transformation statement.
AIP-17110 Within transformation statement {0} of transformation map {1}, binding is provided for parameter which does not belong to the invoked datatype transformation map {2}.: Cause: A transformation statement can provide bindings only for parameters of invoked map or function.
AIP-17111 Within transformation statement {0} of transformation map {1} the binding for parameter {2} can be specified in the context of parameter {3} of the owning event Transformation map only if the parameter is associated with a datatype.: Cause: The transformation statement can define the binding in the context of a map parameter of a event transformation map only if the parameter is associated with a datatype.
AIP-17112 The transformation statement {0} within transformation map {1} is referring to a transformation iterator {2} which is not accessible - a transformation statement can refer to a transformation iterator only it is defined within the transformation iterator.: Cause: A transformation statement can refer to a transformation iterator only if the statement has been defined within the transformation iterator.
AIP-17113 Within transformation statement {0} of transformation map {1} the parameter {2} of type {3} is bound to an invoked parameter of incompatible type {4}.: Cause: A parameter of a datatype map can be bound to an item with the same or compatible datatypes.
AIP-17114 Invalid path specified in the binding for parameter {0} within transformation statement{1} of the transformation map {2}.: Cause: The components of the path must logically fit together.
AIP-17115 Incompatible binding from parameter {0} of map {1} within transformation statement {2} to invoked parameter {3} - they must both be either source or target.: Cause: The parameter of the invoked map and the map parameter from which its value is bound must both be either source or target.
AIP-17117 Within transformation statement {0} of transformation map {1}, binding is provided for parameter which does not belong to the invoked event header function.: Cause: A transformation statement invoking a event header function can define bindings only for parameters of invoked function.
AIP-17118 Within transformation statement {0} of transformation map {1} binding is provided for parameter which does not belong to the invoked domain value map function.: Cause: A transformation statement invoking a domain value map function can define bindings only for parameters of invoked function.
AIP-17119 Within transformation iterator or condition expression statement {0} of transformation map {1}, a binding may not be defined for parameters of invoked datatype transformation map, event header function or domain value map function.: Cause: Binding within transformation iterator or condition expression of transformation map may not be for parameters of invoked datatype transformation map, event header function or domain value map function.
AIP-17120 Invalid condition expression {0} within transformation map {1} as condition evaluation supports only scalar values for operator {2}.: Cause: Condition evaluation is supported only for scalar values.
AIP-17121 The transformation statement {0} within transformation map {1} needs to provide a binding for an invoked parameter(s) {2}.: Cause: Bindings need to be provided for all parameters of invoked map or function.
AIP-17125 Within transformation statement {0} of transformation map {1} binding for parameter {2} is invalid as the parameter does not belong to the invoked datatype transformation map {3}.: Cause: A transformation statement can provide bindings only for parameters of invoked map or function.
AIP-17126 Within transformation statement {0} of transformation map {1}, the binding for invoked parameter {2} can be specified in the context of parameter {3} of event transformation map only if the parameter is associated with an event type.: Cause: The transformation statement can define the binding in the context of a map parameter of a Event Transformation Map only if the parameter is associated with a Event type.
AIP-17127 Binding for parameter {0} defined within transformation statement {1} of transformation map {2} refers to an event body element {3} which is not part of the event type {4} associated to the transformation map parameter {5} in whose context the binding is defined.: Cause: Binding defined within transformation statement can only refer to an event body element of the event type of the transformation map parameter.
AIP-17128 Within transformation statement {0} of transformation map {1} the parameter {2} of type {3} is bound to an invoked parameter of incompatible type {4}.: Cause: A parameter of a datatype map can be bound to an item with the same or compatible datatypes.
AIP-17129 Incompatible binding from parameter {0} of map {1} within transformation statement {2} to the invoked parameter {3} - They must both be either source or target.: Cause: The parameter of the invoked map and the map parameter from which its value is bound must both be either source or target.
AIP-17130 Invalid path specified in the binding for parameter {0} within the transformation statement {1} of the transformation map {2}.: Cause: The components of the path must logically fit together.
AIP-17131 Within transformation statement {0} of transformation map {1}, the binding for parameter {2} is invalid as the parameter does not belong to the invoked event header function {3}.: Cause: A transformation statement invoking a event header function can define bindings only for parameters of invoked function.
AIP-17132 Within transformation statement {0} of transformation map {1} binding for parameter {2} is invalid as the parameter does not belong to the invoked domain value map function {3}.: Cause: A transformation statement invoking a domain value map function can define bindings only for parameters of invoked function.
AIP-17133 Within transformation iterator or condition expression statement {0} within transformation map {1},a binding may not be defined for parameters of invoked datatype transformation map, event header function or domain value map function.: Cause: Binding within transformation iterator or condition expression of transformation map may not be for parameters of invoked datatype transformation map, event header function or domain value map function.
AIP-17134 The transformation statement {0} within transformation map {1} needs to provide a binding for an invoked parameter(s) {2}.: Cause: Bindings need to be provided for all parameters of invoked map or function.
AIP-17135 Only condition expressions which are owned by a transformation rule can be associated with a datatype map parameter.: Cause: Only condition expressions which are owned by a transformation rule can be associated with a datatype map parameter.
AIP-17136 An event header rule associated with a condition expression in transformation map {0} can define bindings only for parameters of event header function.: Cause: An event header rule associated with condition expression in a transformation map can define bindings only for parameters of event header function.
AIP-17137 A domain value map rule {0} associated with a condition expression {1} in transformation map {2} can define bindings only for parameters of domain value map function.: Cause: A domain value map rule associated with a condition expression in a transformation map can define bindings only for parameters of domain value map function.
AIP-17138 A condition expression {0} bound within transformation iterator or condition expression {1} of transformation map {2} may not be for parameters of invoked datatype transformation map, event header function or domain value map function.: Cause: Binding within transformation iterator or condition expression of transformation map may not be for parameters of invoked datatype transformation map, event header function or domain value map function.
AIP-17139 The condition expression {0} can only be owned by another condition expression, transformation condition or correlation.: Cause: A condition expression can only be owned by another condition expression, transformation condition or correlation.
AIP-17140 The condition expression {0} must be binary when it uses a binary operator and unary when it uses a unary operator.: Cause: Provide two operands for a binary condition expression and only one for a unary condition expression.
AIP-17141 Binding within condition expression {0} used by correlation and event map for event type {1} must be a scalar member datatype if the operator is a binary operator.: Cause: Provide a condition expression whose event body items are scalar member datatypes as the operator is a binary operator.
AIP-17142 Only equal-to and not-equal-to operators are supported for boolean datatypes in condition expression {0}.: Cause: Use either an equal-to or not-equal-to operator in the specified condition expression.
AIP-17145 A correlation must be between two native event types.: Cause: Specify two native event types for the correlation.
AIP-17146 The leaf condition expression must be defined as an expression where the left hand side is an event body item from the left event type (e.g. the incoming correlating event type) and the right hand side is an event body item from the right event type (e.g. the correlated event type). For example, POA.id = PO.id and POA.orgunit = PO.orgunit.: Cause: Provide a condition expression where the left hand side is an event body item from the left event type and the right hand side is an event body item from the right event type.
AIP-17147 Condition expression {0} used by correlation between native event {1} and native event {2} cannot have datatype member {3} under datatype {4} in its path specification because more than one more datatype member can appear in instance in same place.: Cause: A condition expression used by a correlation between two native events cannot have a duplicate datatype member.
AIP-17161 Within transformation statement {0} of the transformation map {1} the constant value {2} cannot be bound to invoked parameter {3} of a complex type.: Cause: A constant value may be bound only to a map parameter with a scalar type.
AIP-17162 The format of the constant value {0} within transformation statement {1} of transformation map {2} is not compatible with datatype {3} of invoked parameter {4}.: Cause: The constant value must be in a format corresponding to the datatype of the map parameter to which it is bound.
AIP-17163 Constant value {0} within transformation statement {1} of transformation map {2} cannot be bound to a invoked target parameter {3}.: Cause: Constant values can be used only for binding to source parameters.
AIP-17164 Invalid binding within the transformation statement {0} of transformation map {1} to parameter {2} of datatype transformation map.: Cause: Only operands which are owned by a transformation rule can be associated with a datatype map parameter. For example, the association mapParameter from operand to datatype map parameter can be set only if the operand is owned by a transformation rule.
AIP-17165 An event header rule {0} associated with a constant operand {1} in transformation map {2} can define bindings only for parameters of event header function.: Cause: An event header rule associated with a constant operand in a transformation map can define bindings only for parameters of event header function.
AIP-17166 A domain value map rule {0} associated with a constant operand {1} in transformation map {2} can define bindings only for parameters of domain value map functions.: Cause: A domain value map rule associated with a constant operand in a transformation map can define bindings only for parameters of domain value map function.
AIP-17167 A constant operand {0} bound within transformation iterator or condition expression {1} of transformation map {2} may not be for parameters of invoked datatype transformation map, event header function or domain value map function.: Cause: Binding within transformation iterator or condition expression of transformation map may not be for parameters of invoked datatype transformation map, event header function or domain value map function.
AIP-17200 The consume step {0} can only own ports.: Cause: A consume step can only own ports.
AIP-17201 The consume step {0} must own at least one input port.: Cause: Provide at least one input port to the consume step.
AIP-17202 The consume step {0} can own at most one input port.: Cause: Provide a single input port to the consume step.
AIP-17203 The consume step {0} must not have an output port {1}.: Cause: Remove any output ports from the consume step.
AIP-17204 The consume step {0} must have at least one outbound control flow or dataflow to another step.: Cause: Provide either an outbound control flow or a data flow for the step to another step.
AIP-17250 The domain value map {0} must have exactly one domain column whose business view domain value is true.: Cause: Provide only one domain column with business view domain set to true.
AIP-17251 The domain value map {0} must have at least one domain column whose business view domain value is false.: Cause: Provide at least one domain column with business view domain set to false.
AIP-17252 The domain column name {0} is not unique within the domain value map {1}.: Cause: The names of domain columns within a domain value map must be unique.
AIP-17253 For each domain value map row there must be a domain value map row value for each domain column for map in the domain value map {0}.: Cause: The number of domain value map values for each domain value map row must be equal to the number of domain column for maps.
AIP-17300 The translator {0} must be associated with at least one native format.: Cause: Associate the translator with at least one native format.
AIP-17301 The inbound interaction spec type associated with translator {0} must have a parameter value that is associated with an event body element of a native event type.: Cause: Associate with the translator an inbound interaction spec type that has a parameter value that is associated with an event body element of a native event type.
AIP-17321 The interaction spec type {0} must be either associated with an adapter provider or a translator.: Cause: Associate the interaction spec type with either an adapter provider or a translator.
AIP-17322 The interaction spec type {0} associated with adapter provider {1} has a mandatory parameter {2} that must have a parameter value that is associated with an interaction.: Cause: Provide a parameter value to the interaction spec type and associate it with an interaction.
AIP-17336 The record type {0} must have at least one event map.: Cause: Provide an event map for the record type.
AIP-17337 If the record type {0} has more than one event map then each event map must have a condition expression.: Cause: Provide a condition expression to each event map of the record type.
AIP-17350 The domain value map function associated with the domain value map rule of transformation map {0} of transformation step {1} can only be used in a transformation binding role.: Cause: Domain value map functions must only be used in a transformation binding role.
AIP-17351 The datatype {0} of domain value map function parameter {1} and the datatype {2} of the item associated with the domain value map rule whose transformation map is {3} must be of type string or scalar datatypes implicitly convertible to string.: Cause: The operands of a domain value map rule must be of type string or scalar datatypes implicitly convertible to string.
AIP-17365 Condition expression {0} used by event map between record {1} and native event {2} cannot have datatype member {3} under datatype {4} in its path specification because more than one more datatype member can appear in instance in same place.: Cause: A condition expression used by an event map between a record and a native event cannot have a duplicate datatype member.
AIP-17800 The adapter type {0} resource adapter class name {1} must be in the CLASSPATH.: Cause: Include the resource adapter class name class of the adapter type in the CLASSPATH.
AIP-17801 The resource adapter class name value of adapter type {0} is mandatory at runtime.: Cause: Provide a value for the resource adapter class name attribute of the adapter type.
AIP-17802 The adapter type {0} connectionless metadata {1} must be in the CLASSPATH.: Cause: Include the connectionless metadata of the adapter type in the CLASSPATH.
AIP-17803 The java class name {0} of the connection factory must be in the CLASSPATH.: Cause: Include the java class name of the connection factory in the CLASSPATH.
AIP-17804 The java class name {0} of the connection spec must be in the CLASSPATH.: Cause: Include the java class name of the connection spec in the CLASSPATH.
AIP-17805 The parameter type value of parameter {0} is mandatory at runtime.: Cause: Provide a value for parameter type attribute of the parameter.
AIP-17806 The mandatory value of parameter {0} is mandatory at runtime.: Cause: Provide a value for the mandatory attribute of the parameter.
AIP-17807 The hidden value of parameter {0} is mandatory at runtime.: Cause: Provide a value for the hidden attribute of the parameter.
AIP-17808 The java class name {0} of the interaction spec type must be in the CLASSPATH.: Cause: Include the java class name of the interaction spec type in the CLASSPATH.
AIP-17809 The protocol name value of security specification {0} is mandatory at runtime.: Cause: Provide a value for the protocol name of the security specification.
AIP-17815 The max occurence value of port {0} must be greater than or equal to zero.: Cause: Provide a value greater than or equal to zero for the max occurrence attribute of the port.
AIP-17816 The receiving value of port {0} is mandatory at runtime.: Cause: Provide a value for the receiving attribute of the port.
AIP-17817 The mandatory value of port {0} is mandatory at runtime.: Cause: Provide a value for the mandatory attribute of the port.
AIP-17818 The recurring value of port {0} is mandatory at runtime.: Cause: Provide a value for the recurring attribute of the port.
AIP-17819 The concurrent conversations value in the agreement {0} must be greater than zero.: Cause: Provide a value for concurrent conversations that is greater than zero.
AIP-17820 The invocation limit value of agreement {0} must be greater than zero.: Cause: Provide a value for invocation limit that is greater than zero.
AIP-17823 The agreement id value of agreement {0} is mandatory at runtime.: Cause: Provide a value for the agreement id attribute of the agreement.
AIP-17825 The agreement id of agreement {0} must be unique.: Cause: Provide a unique value for the agreement id attribute of the agreement.
AIP-17827 The time to acknowledge value of trading partner delivery channel {0} must be greater than or equal to zero.: Cause: Provide a value greater than or equal to zero for the time to acknowledge attribute of the trading partner delivery channel.
AIP-17828 The retry count value of trading partner delivery channel {0} must be greater than or equal to zero.: Cause: Provide a value greater than or equal to zero for the retry count attribute of the trading partner delivery channel.
AIP-17829 The non-repudiation of origin value of trading partner delivery channel {0} is mandatory at runtime.: Cause: Provide a value for the non-repudiation of origin attribute of the trading partner delivery channel.
AIP-17830 The non-repudiation of receipt value of trading partner delivery channel {0} is mandatory at runtime.: Cause: Provide a value for the non-repudiation of receipt attribute of the trading partner delivery channel.
AIP-17832 The acknowledgement mode value of trading partner delivery channel {0} is mandatory at runtime.: Cause: Provide a value for the acknowledgment mode attribute of the trading partner delivery channel.
AIP-17833 The envelope enabled value of trading partner delivery channel {0} is mandatory at runtime.: Cause: Provide a value for the envelope enabled attribute of the trading partner delivery channel.
AIP-17834 The transport security enabled value of trading partner delivery channel {0} is mandatory at runtime.: Cause: Provide a value for the transport security enabled attribute of the trading partner delivery channel.
AIP-17835 The global usage code value of trading partner delivery channel {0} is mandatory at runtime.: Cause: Provide a value for the global usage code attribute of the trading partner delivery channel.
AIP-17836 The time to perform value of the supported actor must be greater than or equal to zero.: Cause: Provide a value greater than or equal to zero for the time to perform attribute of the supported actor.
AIP-17838 The transport mode value of transport parameter {0} is mandatory at runtime.: Cause: Provide a value for the transport mode attribute of the transport parameter.
AIP-17839 The client authentication enabled value of the transport endpoint associated with transport parameter {0} is mandatory at runtime.: Cause: Provide a value for the client authentication enabled attribute of the transport endpoint.
AIP-17840 The system identifier value of trading partner identification type {0} is mandatory at runtime.: Cause: Provide a value for the system identifier attribute of the trading partner identification type.
AIP-17842 The event type class value of datatype {0} in namespace {1} is mandatory at runtime.: Cause: Provide a value for the event type class attribute of the datatype.
AIP-17843 The anonymous value of datatype {0} is mandatory at runtime.: Cause: Provide a value for the anonymous attribute of the datatype.
AIP-17844 The model group value of complex datatype {0} is mandatory at runtime.: Cause: Provide a value for the model group attribute of the complex datatype.
AIP-17845 The minimum cardinality value of compound member {0} in complex datatype {1} is mandatory at runtime.: Cause: Provide a value for the minimum cardinality attribute of the compound member.
AIP-17847 The source or target value of event map parameter {0} belonging to event transformation map {1} is mandatory at runtime.: Cause: Provide a value for the source or target attribute of the event map parameter.
AIP-17848 The source or target value of datatype map parameter {0} belonging to datatype transformation map {1} is mandatory at runtime.: Cause: Provide a value for the source or target attribute of the datatype map parameter.
AIP-17849 The else block value of the transformation statement {0} of transformation map {1} is mandatory at runtime.: Cause: Provide a value for the else block attribute of the transformation.
AIP-17850 The logical operator value of the condition expression {0} is mandatory at runtime.: Cause: Provide a value for the logical operator attribute of the condition expression.
AIP-17851 The directional value of the correlation is mandatory at runtime.: Cause: Provide a value for the directional attribute of the correlation.
AIP-17852 The hosted value of organization {0} is mandatory at runtime.: Cause: Provide a value for the hosted attribute of the organization.
AIP-17853 The priority value of the data flow criteria is mandatory at runtime.: Cause: Provide a value for the priority attribute of the data flow criteria.
AIP-17854 The mandatory value of complex datatype member {0} in complex datatype {1} is mandatory at runtime.: Cause: Provide a value for the mandatory attribute of the complex datatype member.
AIP-17855 The qualified value of complex datatype member {0} in complex datatype {1} is mandatory at runtime.: Cause: Provide a value for the qualified attribute of the complex datatype member.
AIP-17857 The process contents value of wildcard member {0} in complex datatype {1} is mandatory at runtime.: Cause: Provide a value for the process contents attribute of the wildcard member.
AIP-17858 The certificate location value of certificate {0} is mandatory at runtime.: Cause: Provide a value for the certificate location attribute of the certificate.
AIP-17859 The value value of the contact info for party {0} is mandatory at runtime.: Cause: Provide a value for the value attribute of the contact info.
AIP-17860 The converter class name value of translator {0} is mandatory at runtime.: Cause: Provide a value for the converter class name attribute of the translator.
AIP-17901 A control flow cannot be owned by data flow group {0}. Only data flows can be owned by data flow groups.: Cause: Control flows cannot be owned by a data flow group.
AIP-17902 The start step {0} must not have any incoming control flows.: Cause: A start step must not be the target of any control flow. Remove the incoming control flow to the start step.
AIP-17903 The end step {0} must not have any outgoing control flows.: Cause: An end step must not be the target of any control flow. Remove the outgoing control flow from the end step.
AIP-17904 Cannot assign any privileges to person {0} without a password.: Cause: Provide a password to the user with whom privileges are being granted.
AIP-17911 The event type {0} must not be associated with an adapter exchange protocol.: Cause: Business event types must not be associated with an adapter exchange protocol. Remove the association between the event type and the adapter exchange protocol.
AIP-17920 No transition owned by the data flow group {0} can have a guard value.: Cause: Guard values can only be for transitions (control and data flows) within a role. Data flows between roles cannot have guard values. Remove the guard value on the data flows of the given data flow group.
AIP-17922 A transition whose source is {0} must have exactly one target.: Cause: A transition must have exactly one target.
AIP-17923 A transition whose target is {0} must have exactly one source.: Cause: A transition must have exactly one source.
AIP-17931 At least one of either the name of the datatype namespace or the association between that namespace and a datatype must be defined.: Cause: A datatype namespace must have either a name or an association with a datatype.
AIP-17934 A transformation statement cannot be owned by a transformation rule, an event header rule, or a domain value map rule {0} of transformation map {1}.: Cause: A transformation statement cannot be owned by a transformation rule, an event header rule, or a domain value map rule.
AIP-17935 The datatype transformation map {0} has been implemented as a java callout, hence it can not have any transformation statements within it.: Cause: Because the datatype transformation map has been implemented as a java callout, it can not have any transformation statements within it.
AIP-17936 A transformation iterator {0} within transformation map {1} cannot be owned by a transformation statement invoking a rule, an event header functionor a domain value map function or a transformation condition.: Cause: A transformation iterator cannot be owned by transformation statement invoking a rule, an event header function or a domain value map function or a transformation condition.
AIP-17938 Neither a condition expression nor a constant operand can be owned by a transformation iterator {0} within transformation map {1}.: Cause: Neither a condition expression nor a constant operand can be owned by a transformation iterator.
AIP-17940 The valid value {0} must be owned by a facet whose facet type is either enumeration or pattern.: Cause: A valid value can only be owned by a facet whose facet type is either enumeration or pattern.
AIP-17942 Only a data flow group between a business role and a binding role can own a data flow criteria.: Cause: Data flow criteria can only be owned by a data flow group that is between a business role and a binding role. Remove the data flow criteria of the given group.
AIP-17946 The step {0} cannot own other steps or ports.: Cause: And state, or state, start and end steps cannot own ports or other steps.
AIP-17947 The record type element {0} of record type {1} must be associated with a native format.: Cause: Associate a native format with the record type element.
AIP-17948 The datatype associated with the domain column {0} must be the core string datatype.: Cause: The datatype associated with domain columns must be the core string datatype.
AIP-17949 The event header function {0} must have exactly one header function parameter.: Cause: Provide exactly one header function parameter to the event header function.
AIP-17950 A transformation statement invoking a event header function {0} within transformation map {1} must have exactly onebinding for the invoked parameters.: Cause: A transformation statement invoking a event header function must have exactly one binding for the invoked parameters
AIP-17951 The member group head value in complex datatype member {0} can only be set to true if the owning complex datatype {0} has member group type also set to true.: Cause: If member group head is set to true in a complex datatype member, set the member group type value to true in the owning complex datatype.
AIP-17975 If adapter type {0} needs connection for metadata is false, then connectionless metadata should be set, otherwise it should be set to null.: Cause: If needs connection for metadata is false, then set the connectionless metadata, otherwise set it to null.
AIP-17976 The minimum cardinality of compound member {0} in complex datatype {1} must be less than or equal to its maximum cardinality.: Cause: Specify a value for minimum cardinality that is less than or equal to the value of maximum cardinality.
AIP-17977 The minimum cardinality of array datatype {0} must be less than or equal to its maximum cardinality.: Cause: Specify a value for minimum cardinality that is less than or equal to its maximum cardinality.
AIP-17978 The business action {0} has non-repudiation of receipt enabled but non-repudiation of origin is not enabled.: Cause: Enable non-repudiation of origin for the business action.
AIP-17979 The effective from date of agreement {0} must be less than or equal to its effective to date.: Cause: Specify a from date that is less than or equal to the to date.
AIP-17980 The exchange protocol {0} has non-repudiation of receipt enabled but non-repudiation of origin is not enabled.: Cause: Enable non-repudiation of origin for the exchange protocol.
AIP-17981 If anonymous is true for datatype {0} then the datatype cannot have a name, otherwise it must have one.: Cause: Specify the datatype as either anonymous with no name, or specify a name with the datatype.
AIP-17982 The datatype is anonymous and therefore must have no datatypes derived either by restriction or extension from that datatype.: Cause: Do not derive datatypes from an anonymous datatype.
AIP-17983 A ref type only datatype cannot be anonymous.: Cause: Provide a name to the ref type only datatype.
AIP-17984 Ref type only datatype {0} in namespace {1} cannot have any datatypes derived from it.: Cause: Do not derive datatypes from the ref type only datatype.
AIP-17985 The trading partner delivery channel {0} has non-repudiation of receipt enabled but non-repudiation of origin is not enabled.: Cause: Enable non-repudiation of origin for the trading partner delivery channel.
AIP-17986 The name of the the anonymous complex datatype member {1} in complex datatype {0} must not be set.: Cause: The names of anonymous complex datatype members belonging to complex datatypes must not be set.
AIP-17987 The qualified attribute value {0} in complex datatype member {1} is incompatible with its associated translation metadata {2}.: Cause: A complex datatype member is associated to a translation metadata if and only if the member is qualified.
AIP-17988 The minimum cardinality of wildcard member {0} belonging to the complex datatype {1} must be less than or equal to its maximum cardinality.: Cause: Provide a value for minimum cardinality of the wildcard member that is less than or equal to its maximum cardinality.
AIP-17989 Wildcard member {0} of complex datatype {1} does not have the correct number of datatype namespaces based on the replacement namespace value {2}.: Cause: A wildcard member must have the correct number of datatype namespaces depending on the value of the replacement namespace attribute.
AIP-17990 At least one of either the in translator class name or the out translator class name values of translator {0} are mandatory at runtime.: Cause: Provide a value for at least one of either the in translator class name or out translator class name attributes.
AIP-17991 The remote trading partner {0} must not have a wallet password.: Cause: Only a hosted trading partner can have wallet password. Remove the wallet password from the remote trading partner.
AIP-17992 A wallet password is required for the hosted trading partner {0}.: Cause: For hosted trading partners, wallet passwords are mandatory at runtime. Provide a wallet password to the hosted trading partner.
AIP-17993 The facet of type {0} cannot have a facet value.: Cause: Enumeration and pattern facets cannot have a facet value.
AIP-17994 The facet value {0} is not valid for a facet whose type is {1}.: Cause: The value of a facet must be valid for its particular facet type.
AIP-17995 If member group type is true in complex datatype {0} then ref type only must be true and model group must be CHOICE.: Cause: Change the ref type only value to true and set the model group value to CHOICE in the complex datatype.
AIP-17996 The approval date of an agreement must be on or after the send for approval date.: Cause: Ensure that the approved date for the agreement is on or after the send for approval date.
AIP-17997 Trading partner {0} cannot be a hosted trading partner because there can be only one defined in the system.: Cause: Verify that only one hosted trading partner is defined in the system.

AIP-18000 to AIP-18999 Deployment Error Codes

AIP-18010 Calculation of deployment unit failed.: Cause: Calculation of deployment unit failed.
AIP-18020 error during validation: Cause: An error occurred during validation.
AIP-18030 Deployment unit "{0}" is invalid.: Cause: The deployment unit is invalid.
AIP-18040 execution context not started: Cause: The execution context was not started.
AIP-18050 SQL error during deployment: Cause: SQL error during deployment.
AIP-18060 error writing to buffered stream: Cause: An error occurred while writing to the buffered stream.
AIP-18070 more than one start state: Cause: You can have only one start state.
AIP-18070 no end state for workflow: Cause: At least one end state in the workflow is needed.
AIP-18071 The guard value is not defined for the transition.: Cause: The guard value for the target transition of the conditional step is not defined.
AIP-18080 deploy property "{0}" not found: Cause: Deploy property "{0}" not found.
AIP-18090 The transition object is not an instance of data flow.: Cause: The transition object is not an instance of data flow.
AIP-18100 error uploading workflow file.: Cause: An error occurred while uploading the workflow file.
AIP-18110 The state vertex is not a step or a pseudostate.: Cause: State vertex is not step or pseudostate.
AIP-18120 The state is not a supported state (workflow generation).: Cause: State not supported state (workflow generation).
AIP-18130 error generating workflow: Cause: An error occurred while generating the workflow.
AIP-18140 fatal error during deployment: Cause: Fatal error during deployment.

AIP-19000 to AIP-19999 UI Modeling Error Codes

AIP-19000 The same native role was chosen for both the initiating and invoked spokes. You must choose two different spokes by selecting different native roles.: Cause: The same native role was chosen for both the initiating and invoked spokes. Two different spokes must be chosen by selecting different native roles.
AIP-19001 The interactions for the initiating spoke and the invoked spoke are both inbound. You must select an interaction that is inbound and another that is outbound.: Cause: The interactions for the initiating spoke and the invoked spoke are both inbound. One interaction must be inbound and the other must be outbound.
AIP-19002 The interactions for the initiating spoke and the invoked spoke are both outbound. You must select an interaction that is inbound and another that is outbound.: Cause: The interactions for the initiating spoke and the invoked spoke are both outbound. One interaction must be inbound and the other must be outbound.
AIP-19003 The outbound interaction for the response was not specified. You must select the outbound interaction for the response or check Ignore response.: Cause: The outbound interaction for the response was not specified. You must select the outbound interaction for the response or check Ignore response.
AIP-19004 invalid response interaction. The outbound interaction for the response cannot have an outbound record also.: Cause: Invalid response interaction. The outbound interaction for the response cannot have an outbound record also.
AIP-19005 The business event name was not specified. You must enter a name for the new business event.: Cause: The business event name was not specified. You must enter a name for the new business event.
AIP-19006 The business event was not specified. You must chose an existing business event.: Cause: The business event was not specified. You must chose an existing business event.
AIP-19007 The business event name was not specified for the inbound event flow. You must enter a name for the new business event for the inbound event flow.: Cause: The business event name was not specified for the inbound event flow. You must enter a name for the new business event.
AIP-19008 The business event was not specified for the inbound event flow. You must chose an existing business event for the inbound event flow.: Cause: The business event was not specified for the inbound event flow. You must chose an existing business event for the inbound event flow.
AIP-19009 The transformation map name was not specified. You must enter a name for the new transformation map.: Cause: The transformation map name was not specified. You must enter a name for the new transformation map.
AIP-19010 The transformation map was not specified. You must chose an existing transformation map.: Cause: The transformation map was not specified. You must chose an existing transformation map.
AIP-19011 The transformation map name was not specified for the inbound transformation. You must enter a name for the new transformation map for the inbound transformation.: Cause: The transformation map name was not specified for the inbound transformation. You must enter a name for the new transformation map for the inbound transformation.
AIP-19012 The transformation map was not specified for the inbound transformation. You must chose an existing transformation map for the inbound transformation.: Cause: The transformation map was not specified for the inbound transformation. You must chose an existing transformation map for the inbound transformation.
AIP-19013 The same role naming convention was specified for both spokes. Specify unique role naming conventions for each spoke.: Cause: The same role naming convention was specified for both spokes. Specify unique role naming conventions for each spoke.
AIP-19014 The business process name was not specified. You must enter a name for the new business process.: Cause: The business process name was not specified. You must enter a name for the new business process.
AIP-19015 The business event was not specified. You must chose an existing business process.: Cause: The business event was not specified. You must chose an existing business process.
AIP-19016 attempting to create an event flow for an incomplete spoke. Complete the spoke first or chose a spoke that is already complete.: Cause: Attempting to create an event flow for an incomplete spoke. To be a complete spoke, the spoke must have all roles bound from the native role to the business process. Complete the spoke first or chose a spoke that is already complete.
AIP-19017 The selected interaction is not valid for the port direction (input/output). An inbound interaction must be associated with an input port.: Cause: The selected interaction is not valid for the port direction (input/output). An inbound interaction must be associated with an input port.
AIP-19018 Click the flashlight and select a datatype for this port. Do not type a name.: Cause: Click the flashlight and select a datatype for this port. Do not type a name.
AIP-19019 Click the flashlight and select an event for this port. Do not type a name.: Cause: Click the flashlight and select an event for this port. Do not type a name.
AIP-19020 An event type was not selected. If you chose the pass-through option, an event type must be selected.: Cause: An event type was not selected. If you chose the pass-through option, an event type must be selected.
AIP-19021 The updated port direction is not compatible with the existing data flow from port "{0}" in "{1}". You must either delete the data flow first or chose the opposite direction for the port.: Cause: The updated port direction is not compatible with the existing data flow from port "{0}" in "{1}". You must either delete the data flow first or chose the opposite direction for the port.
AIP-19022 The updated port event type is not compatible with the existing data flow from port "{0}" in "{1}" of event type "{2}". You must either delete the data flow first or chose the same event type for this port.: Cause: The updated port event type is not compatible with the existing data flow from port "{0}" in "{1}" of event type "{2}". You must either delete the data flow first or chose the same event type for this port.
AIP-19023 The updated port datatype is not compatible with the existing data flow from port "{0}" in "{1}" of datatype "{2}". You must either delete the data flow first or chose the same datatype for this port.: Cause: The updated port datatype is not compatible with the existing data flow from port "{0}" in "{1}" of datatype "{2}". You must either delete the data flow first or chose the same datatype for this port.
AIP-19024 Start and end steps cannot be deleted.: Cause: Start and end steps cannot be deleted.
AIP-19025 The direction of the data flow group from the binding role to the application role cannot be determined. Bind the binding role to a native role or a business role first.: Cause: The direction of the data flow group from the binding role to the application role cannot be determined. There is a binding role on both the inbound and outbound side of the application role. Bind the binding role to a native role or a business role first.
AIP-19026 Port "{0}" on role "{1}" is already bound to "{2}" on role "{3}". You must first delete the data flow to this port or select another port.: Cause: Port on role is already bound. Ports on this role can only be data flow bound to one other port. You must first delete the data flow to this port or select another port.

AIP-50000 to AIP-51999 Transport Error Codes

AIP-50000 successful: Cause: Successful.
AIP-50002 successfully received business document from XML gateway: Cause: Successfully received business document from XML gateway (delivery confirmation).
AIP-50003 collaboration initiation error: Cause: Collaboration initiation error.
AIP-50004 collaboration message sequencing error: Cause: Collaboration message sequencing error.
AIP-50005 collaboration abort error: Cause: Collaboration stop error.
AIP-50006 exception received: Cause: Exception received.
AIP-50007 notification of failure received: Cause: Notification of failure received.
AIP-50008 time to perform exceeded: Cause: Time to perform exceeded.
AIP-50009 unable to send: Cause: Unable to send.
AIP-50010 trading partner agreement identification error: Cause: Trading partner agreement identification error.
AIP-50011 message correlation error: Cause: Message correlation error.
AIP-50012 pack/unpack error: Cause: Pack/unpack error.
AIP-50013 security error: Cause: Security error.
AIP-50014 general error: Cause: General error.
AIP-50025 repository error: Cause: Repository error.
AIP-50026 A null parameter cannot be passed as a valid input parameter.: Cause: A null parameter cannot be passed as a valid input parameter.
AIP-50027 unable to write data into output stream: Cause: Unable to write data into output stream.
AIP-50028 unable to read data from input stream: Cause: Unable to read data from input stream.
AIP-50029 runtime error: Cause: Runtime error.
AIP-50030 invalid input parameter: Cause: The parameter which is passed cannot be understood.
AIP-50050 B2B initialization successful: Cause: B2B initialization successful.
AIP-50051 The B2B engine initialization failed.: Cause: The B2B engine initialization failed.
AIP-50052 The B2B engine was already initialized.: Cause: The B2B engine was already initialized.
AIP-50053 The B2B engine was not initialized.: Cause: The B2B engine was not initialized.
AIP-50054 cannot access configuration file: Cause: Cannot access configuration file.
AIP-50055 error in configuration file: Cause: Error in configuration file.
AIP-50056 unknown error: Cause: Unknown error. Contact Oracle Support Services.
AIP-50057 An invalid wallet location was specified for the SSL.: Cause: SSL requires the wallet to be specified in .txt format. The Oracle Wallet needs to be exported to a file and the WRL should have the exported file name.
AIP-50075 cannot find Document Exchange Plugin "{0}": Cause: Cannot find Document Exchange Plugin "{0}".
AIP-50076 cannot find Packaging Plugin "{0}": Cause: Cannot find Packaging Plugin "{0}".
AIP-50077 cannot initialize transport: Cause: Cannot initialize transport.
AIP-50078 cannot shut down transport: Cause: Cannot shut down transport.
AIP-50079 transport error: Cause: Transport error.
AIP-50080 protocol identification error: Cause: The B2B adapter is unable to identify the B2B message with its supported protocols.
AIP-50125 error from workflow "{0}": Cause: Error from workflow "{0}".
AIP-50126 Oracle error while determining workflow agent: Cause: Oracle error while determining workflow agent.
AIP-50127 Oracle error when initializing workflow event subscriptions: Cause: Oracle error when initializing workflow event subscriptions.
AIP-50128 Oracle error when shutting down AQ session pertaining to workflow: Cause: Oracle error when shutting down AQ session pertaining to workflow.
AIP-50129 error when publishing event "{0}" to workflow: Cause: Error when publishing event "{0}" to workflow.
AIP-50130 error when subscribing for workflow events: Cause: Error when subscribing for workflow events.
AIP-50131 error while instantiating the event manager for subscribing to workflow events: Cause: Error while instantiating event manager for subscribing to workflow events.
AIP-50132 exception when collaboration manager received event raised from workflow: Cause: Exception when collaboration manager received event raised from workflow.
AIP-50133 Oracle error when initializing context for publishing events to workflow: Cause: Oracle error when initializing context for publishing events to workflow.
AIP-50134 SQL error accessing collaboration-related tables: Cause: SQL error accessing collaboration-related tables.
AIP-50135 invalid business activity type: Cause: Invalid business activity type.
AIP-50136 Responding activity cannot belong to a new collaboration.: Cause: Responding activity cannot belong to a new collaboration.
AIP-50137 Signal message cannot belong to a new collaboration.: Cause: Signal message cannot belong to a new collaboration.
AIP-50138 Error message cannot belong to a new collaboration.: Cause: Error message cannot belong to a new collaboration.
AIP-50139 invalid direction for signal and error messages: Cause: Invalid direction for signal and error messages.
AIP-50140 SQL exception: Cause: SQL Exception when retrieving workflow event parameters.
AIP-50141 business transaction usage not found for name "{0}": Cause: Business transaction usage not found for name "{0}".
AIP-50142 collaboration instance not found for Collaboration ID "{0}": Cause: Collaboration instance not found for Collaboration ID.
AIP-50143 transaction instance not found for Transaction ID "{0}": Cause: Transaction instance not found for Transaction ID "{0}".
AIP-50144 agreement not found for trading partner agreement ID "{0}": Cause: Agreement not found for trading partner agreement ID "{0}".
AIP-50145 collaboration "{0}" not found for version "{1}": Cause: Collaboration "{0}" not found for version "{1}".
AIP-50146 exception thrown by repository: Cause: Exception thrown by repository.
AIP-50147 cannot start collaboration; concurrently executing "{0}" collaborations: Cause: Concurrent collaborations exceeded. Unable to start collaboration.
AIP-50148 cannot start collaboration; maximum collaboration limit of "{0}": Cause: Maximum collaborations exceeded. Unable to start collaboration.
AIP-50149 cannot map value "{0}" to a valid business transaction state: Cause: Invalid business transaction state.
AIP-50500 trading partner agreement not found for the given input values: from party [ID-ROLE] "{0}", to party [ID-ROLE] "{1}", collaboration name "{2}": Cause: Unable to identify the trading partner agreement from the given input values.
AIP-50501 trading partner agreement not found for the given input values: from party [NAME-ROLE] "{0}", to party [NAME-ROLE] "{1}", collaboration name "{2}": Cause: Unable to identify the trading partner agreement from the given input values.
AIP-50502 trading partner agreement details not found for the trading partner agreement ID "{0}": Cause: Unable to get the trading partner agreement details from the given trading partner agreement ID.
AIP-50503 delivery channel not found for the Trading Partner ID "{0}": Cause: Unable to get delivery channel details.
AIP-50504 transport endpoint not found for the Trading Partner ID "{0}": Cause: Unable to get the transport endpoint details.
AIP-50506 cannot find collaboration details for the action name "{0}": Cause: Unable to find collaboration details for the given action name.
AIP-50507 From role "{0}" in the message is different from role "{1}" in the agreement.: Cause: The from role in message is different from agreement.
AIP-50508 To role "{0}" in the message is different from role "{1}" in the agreement.: Cause: The to role in message is different from agreement.
AIP-50509 From service "{0}" in the message is different from service "{1}" in the agreement.: Cause: The from service in message is different from agreement.
AIP-50510 To service "{0}" in the message is different from service "{1}" in the agreement: Cause: The to service in message is different from agreement.
AIP-50511 Business transaction name "{0}" in the message is different from business transaction name "{1}" in the agreement.: Cause: Business transaction name "{0}" in the message is different from business transaction name "{1}" in the agreement.
AIP-50512 Business transaction revision "{0}" in the message is different from business transaction revision "{1}" in the agreement.: Cause: Business transaction revision "{0}" in the message is different from business transaction revision "{1}" in the agreement.
AIP-50513 Business transaction time to perform "{0}" in the message is different from business transaction time to perform "{1}" in the agreement.: Cause: Business transaction time to perform "{0}" in the message is different from business transaction time to perform "{1}" in the agreement.
AIP-50514 Collaboration name "{0}" in the message is different from collaboration name "{1}" in the agreement.: Cause: Collaboration name "{0}" in the message is different from collaboration name "{1}" in the agreement.
AIP-50515 Collaboration revision "{0}" in the message is different from collaboration revision "{1}" in the agreement.: Cause: Collaboration revision "{0}" in the message is different from collaboration revision "{1}" in the agreement.
AIP-50516 Collaboration code "{0}" in the message is different from collaboration code "{1}" in the agreement.: Cause: Collaboration code "{0}" in the message is different from collaboration code "{1}" in the agreement.
AIP-50517 Collaboration time to perform "{0}" in the message is different from collaboration time to perform "{1}" in the agreement.: Cause: Collaboration time to perform "{0}" in the message is different from collaboration time to perform "{1}" in the agreement.
AIP-50518 The transport protocol "{0}" for the message is different from the transport protocol "{1}" in the agreement.: Cause: The transport protocol "{0}" for the message is different from the transport protocol "{1}" in the agreement.
AIP-50519 The transport protocol version "{0}" for the message is different from the transport protocol version "{1}" in the agreement.: Cause: The transport protocol version "{0}" for the message is different from the transport protocol version "{1}" in the agreement.
AIP-50520 The transport protocol endpoint "{0}" for the message is different from the transport protocol endpoint "{1}" in the agreement.: Cause: The transport protocol endpoint "{0}" for the message is different from the transport protocol endpoint "{1}" in the agreement.
AIP-50521 Acknowledgment mode "{0}" in the message is different from acknowledgment mode "{1}" in the agreement.: Cause: Acknowledgment mode "{0}" in the message is different from acknowledgment mode "{1}" in the agreement.
AIP-50522 Response mode "{0}" in the message is different from response mode "{1}" in the agreement.: Cause: Response mode "{0}" in the message is different from response mode "{1}" in the agreement.
AIP-50523 Document exchange protocol name "{0}" in the message is different from document exchange protocol name "{1}" in the agreement.: Cause: Document exchange protocol name "{0}" in the message is different from document exchange protocol name "{1}" in the agreement.
AIP-50524 Document exchange protocol version "{0}" in message is different from document exchange protocol version "{1}" in the agreement.: Cause: Document exchange protocol version "{0}" in message is different from document exchange protocol version "{1}" in the agreement
AIP-50525 The agreement signature information is null.: Cause: Message non-repudiation is enabled but no signature information is specified.
AIP-50526 The message has been signed using "{0}", which is different from signing protocol "{1}" in the agreement.: Cause: The message has been signed using "{0}", which is different from signing protocol "{1}" in the agreement.
AIP-50527 The signing protocol version "{0}" in the message is different from the signing protocol version "{1}" in the agreement.: Cause: The signing protocol version "{0}" in the message is different from the signing protocol version "{1}" in the agreement.
AIP-50528 The signing algorithm "{0}" in the message is different from the signing algorithm "{1}" in the agreement.: Cause: The signing algorithm "{0}" in the message is different from the signing algorithm "{1}" in the agreement.
AIP-50529 The digest algorithm "{0}" in the message is different from the digest algorithm "{1}" in the agreement.: Cause: The digest algorithm "{0}" in the message is different from the digest algorithm "{1}" in the agreement.
AIP-50530 The signer certificate in the message is different from the certificate in the agreement.: Cause: The signer certificate in the message is different from the certificate in the agreement.
AIP-50531 The agreement envelope information is null.: Cause: Message confidentiality is enabled but no envelope information is specified.
AIP-50532 The message has been enveloped using "{0}", which is different from envelope protocol "{1}" in the agreement.: Cause: The message has been enveloped using "{0}", which is different from envelope protocol "{1}" in the agreement.
AIP-50533 The envelope protocol version "{0}" in the message is different from the envelope protocol version "{1}" in the agreement.: Cause: The envelope protocol version "{0}" in the message is different from the envelope protocol version "{1}" in the agreement.
AIP-50534 The encryption algorithm "{0}" in the message is different from the encryption algorithm "{1}" in the agreement.: Cause: The encryption algorithm "{0}" in the message is different from the encryption algorithm "{1}" in the agreement.
AIP-50535 unable to get the certificate from the given location "{0}": Cause: Unable to get the certificate from the given location "{0}".
AIP-50536 exchange protocol not found for the given input values: Name "{0}", Revision "{1}": Cause: Exchange protocol not found for the given input values: Name "{0}", Revision "{1}".
AIP-50537 more than one exchange protocol found for the given input values: Name "{0}", Revision "{1}": Cause: More than one exchange protocol found for the given input values: Name "{0}", Revision "{1}".
AIP-50538 business signal not found for the given input values: Name "{0}", Revision "{1}": Cause: Business signal not found for the given input values: Name "{0}", Revision "{1}".
AIP-50539 more than one business signal found for the given input values: Name "{0}", Revision "{1}": Cause: More than one business signal found for the given input values: Name "{0}", Revision "{1}".
AIP-50540 The exchange protocol parameter "{0}" value "{1}" in the message is different from the value "{2}" in the agreement.: Cause: The exchange protocol parameter "{0}" value "{1}" in the message is different from the value "{2}" in the agreement.
AIP-50801 failed to construct B2B event with "{0}" : "{1}": Cause: Failed to construct B2B event with "{0}" : "{1}".
AIP-50802 failed to set B2B event "{0}" : "{1}": Cause: Failed to set B2B event "{0}" : "{1}".
AIP-50803 failed to get B2B event "{0}": Cause: Failed to get B2B event "{0}".
AIP-50804 failed to get JMS Topic "{0}"."{1}" with option "{2}" or create subscriber "{3}": Cause: Failed to get JMS Topic "{0}"."{1}" with option "{2}" or create subscriber "{3}".
AIP-50805 failed to close JMS Topic "{0}"."{1}" or close subscriber "{2}": Cause: Failed to close JMS Topic "{0}"."{1}" or close subscriber "{2}".
AIP-50806 failed to publish JMS message to Topic "{0}"."{1}": Cause: Failed to publish JMS message to Topic "{0}"."{1}".
AIP-50807 JMS Topic "{0}"."{1}" has not been initialized.: Cause: JMS Topic "{0}"."{1}" has not been initialized.
AIP-50808 failed to publish JMS message to Topic "{0}"."{1}": Cause: Failed to publish JMS message to Topic "{0}"."{1}".
AIP-50809 failed to receive JMS message from Topic "{0}"."{1}": Cause: Failed to receive JMS message from Topic "{0}"."{1}".
AIP-50810 failed to initialize database context: Cause: Failed to initialize database context - failed to get transaction from persistency service.
AIP-50811 failed to shut down database context: Cause: Failed to shutdown database context - failed to close persistency service.
AIP-50812 failed to shut down database context: Cause: Failed to shutdown database context - failed to close JDBC connection.
AIP-50814 failed to begin transaction: Cause: Failed to begin transaction.
AIP-50815 failed to commit transaction: Cause: Failed to commit transaction.
AIP-50816 failed to roll back transaction: Cause: Failed to roll back transaction.
AIP-50817 failed to add repository object into transaction: Cause: Failed to add repository object into transaction.
AIP-50818 failed to retrieve system date and time from repository: Cause: Failed to retrieve system date and time from repository.
AIP-50819 failed to insert data into database table "{0}": Cause: Failed to insert data into database table "{0}".
AIP-50820 failed to close SQL statement or result set after insert data into database table "{0}": Cause: Failed to close SQL statement or result set after insert data into database table "{0}".
AIP-50821 failed to select rows from database table "{0}": Cause: Failed to select rows from database table "{0}".
AIP-50822 failed to select rows from database table "{0}" by order: Cause: Failed to select rows from database table "{0}" by order.
AIP-50823 failed to select all rows from database table "{0}": Cause: Failed to select all rows from database table "{0}".
AIP-50824 failed to delete rows from database table "{0}": Cause: Failed to delete rows from database table "{0}".
AIP-50825 failed to delete all rows from database table "{0}": Cause: Failed to delete all rows from database table "{0}".
AIP-50826 failed to update rows to database table "{0}": Cause: Failed to update rows to database table "{0}".
AIP-50827 failed to initialize catalog in data context: Cause: Failed to initialize catalog in data context.
AIP-50828 failed to initialize JDBC connection pool in data context: Cause: Failed to initialize JDBC connection pool in data context.
AIP-50829 failed to close catalog in data context: Cause: Failed to close catalog in data context.
AIP-50830 failed to close JDBC connection pool in data context: Cause: Failed to close JDBC connection pool in data context.
AIP-50831 failed to retrieve new database context: Cause: Failed to retrieve new database context.
AIP-50832 failed to retrieve new connection from JDBC connection pool: Cause: Failed to retrieve new connection from JDBC connection pool.
AIP-50833 failed to initialize JMS connection or session in data runtime context: Cause: Failed to initialize JMS connection or session in data runtime context.
AIP-50834 failed to close JMS connection or session in data runtime context: Cause: Failed to close JMS connection or session in data runtime context.
AIP-50835 failed to enqueue ADT message into event topic: Cause: Failed to enqueue ADT message into event topic.
AIP-50836 failed to dequeue ADT message from event topic: Cause: Failed to dequeue ADT message from event topic.
AIP-50837 failed to initialize JMS message listener for event topic: Cause: Failed to initialize JMS message listener for event topic.
AIP-50838 failed to shut down JMS message listener for event topic: Cause: Failed to shutdown JMS message listener for event topic.
AIP-50901 failed to find a business message with B2B message ID "{0}": Cause: Failed to find a business message with B2B message ID "{0}".
AIP-50902 failed to find a wire message with B2B message ID "{0}": Cause: Failed to find a wire message with B2B message ID "{0}".
AIP-50903 Message "{0}" retry count is zero.: Cause: Message "{0}" retry count is zero.
AIP-50904 Refer to message not found: Cause: Refer to B2B message ID not found.
AIP-50905 collaboration not found: Cause: B2B Collaboration ID not found.
AIP-50906 failed to retrieve XPATH: Cause: Error in extracting XPATH Value.
AIP-50925 unable to raise inbound interaction for Record "{0}": Cause: Unable to raise inbound interaction.
AIP-51000 general packaging error: Cause: General packaging error.
AIP-51001 packing failed: Cause: Packing failed.
AIP-51002 unpacking failed: Cause: Unpacking failed.
AIP-51003 encoding failed: Cause: Encoding failed.
AIP-51004 decoding failed: Cause: Decoding failed.
AIP-51005 validating packaging metadata information failed: Cause: Validating packaging metadata information failed.
AIP-51006 invalid input parameter: Cause: Invalid input parameter.
AIP-51007 missing packaging metadata information: Cause: Missing packaging metadata information.
AIP-51008 circular dependency in packaging metadata information: Cause: Circular dependency in packaging metadata information.
AIP-51009 missing one or more packaging elements in packaging metadata information: Cause: Missing one or more packaging elements in packaging metadata information.
AIP-51010 missing composite packaging element in packaging metadata information: Cause: Missing composite packaging element in packaging metadata information.
AIP-51011 bad or corrupt packaging metadata information: Cause: Bad or corrupt packaging metadata information.
AIP-51012 missing list of message components: Cause: Missing list of message components.
AIP-51013 missing one or more message components in the list of message components: Cause: Missing one or more message component(s) in the list of message components.
AIP-51014 missing data for message component: Cause: Missing data for message component.
AIP-51015 missing security information: Cause: Missing security information.
AIP-51016 missing signature information: Cause: Missing signature information.
AIP-51017 missing envelope/encryption information: Cause: Missing envelope/encryption information.
AIP-51018 The message is not digitally signed.: Cause: The message is not digitally signed.
AIP-51019 The message is not encrypted.: Cause: The message is not encrypted.
AIP-51020 The signature protocol is not supported.: Cause: The signature protocol is not supported.
AIP-51021 The encryption protocol is not supported.: Cause: The encryption protocol is not supported.
AIP-51022 The digest algorithms do not match.: Cause: The digest algorithms do not match.
AIP-51023 signature information already set for message: Cause: Signature information already set for message.
AIP-51024 envelope information already set for message: Cause: Envelope information already set for message.
AIP-51025 Wallet resource location strings do not match.: Cause: Wallet resource location strings do not match.
AIP-51026 encoding type not supported: Cause: Encoding type not supported.
AIP-51050 Mime content-types do not match.: Cause: Mime content-types do not match.
AIP-51051 Mime content-type parameter lists do not match.: Cause: Mime content-type parameter lists do not match.
AIP-51052 bad or corrupt mime content-type header or information: Cause: Bad or corrupt mime content-type header or information.
AIP-51053 bad or corrupt mime content disposition header or information: Cause: Bad or corrupt mime content disposition header or information.
AIP-51054 missing content-type information: Cause: Missing content-type information.
AIP-51055 missing information for message component: Cause: Missing information for message component.
AIP-51056 missing or unable to read data from message: Cause: Missing or unable to read data from message.
AIP-51057 bad or corrupt message: Cause: Bad or corrupt message.
AIP-51075 missing signer certificate: Cause: Missing signer certificate.
AIP-51076 missing encryption certificate: Cause: Missing encryption certificate.
AIP-51077 missing certificate chain: Cause: Missing certificate chain.
AIP-51078 missing or corrupt digest of the message: Cause: Missing or corrupt digest of the message.
AIP-51079 The S/MIME version is not supported "{0}".: Cause: The S/MIME version is not supported "{0}".
AIP-51080 The signature algorithm is not supported "{0}".: Cause: The signature algorithm is not supported "{0}".
AIP-51081 The digest algorithm is not supported "{0}".: Cause: The digest algorithm is not supported "{0}".
AIP-51082 The encryption algorithm is not supported "{0}".: Cause: The encryption algorithm is not supported "{0}".
AIP-51083 general failure creating S/MIME digital signature: Cause: General failure creating S/MIME digital signature.
AIP-51084 general failure verifying S/MIME digital signature: Cause: General failure verifying S/MIME digital signature.
AIP-51085 general failure encrypting S/MIME message: Cause: General failure encrypting S/MIME message.
AIP-51086 general failure decrypting S/MIME message: Cause: General failure decrypting S/MIME message.
AIP-51087 Creating digest data for S/MIME digital signature failed; "{0}".: Cause: Creating digest data for S/MIME digital signature failed; "{0}".
AIP-51088 Creating S/MIME digital signature failed; "{0}".: Cause: Creating S/MIME digital signature failed; "{0}".
AIP-51089 Verifying S/MIME digital signature failed; "{0}".: Cause: Verifying S/MIME digital signature failed; "{0}".
AIP-51090 Creating S/MIME message recipient list failed; "{0}".: Cause: Creating S/MIME message recipient list failed; "{0}".
AIP-51091 Adding recipient to S/MIME message recipient list failed; "{0}".: Cause: Adding recipient to S/MIME message recipient list failed; "{0}".
AIP-51092 Encrypting S/MIME message failed; "{0}".: Cause: Encrypting S/MIME message failed; "{0}".
AIP-51093 Decrypting S/MIME message failed; "{0}".: Cause: Decrypting S/MIME message failed; "{0}".
AIP-51094 Processing signature information for S/MIME message failed.: Cause: Processing signature information for S/MIME message failed.
AIP-51095 Processing envelope information for S/MIME message failed.: Cause: Processing envelope information for S/MIME message failed.
AIP-51096 More than one signer in the S/MIME digital signature is not supported.: Cause: More than one signer in the S/MIME digital signature is not supported.
AIP-51097 An empty packaging IDs list was passed for the packaging plugin initialization.: Cause: An empty packaging IDs list was passed for the packaging plugin initialization.
AIP-51098 The packaging metadata contains invalid content-type "{0}".: Cause: The packaging metadata contains invalid content-type "{0}".
AIP-51099 not a RosettaNet 1.1 message: Cause: Not a RosettaNet 1.1 message.
AIP-51500 document exchange successful: Cause: Successful operation of the document exchange layer.
AIP-51501 document exchange general initialization failure: Cause: The document exchange protocol adapter failed to initialize.
AIP-51502 document exchange generic shutdown failure: Cause: The document exchange protocol adapter failed to shut down.
AIP-51503 general create message error: Cause: The CreateMessage() method fails to create the protocol specific B2B message.
AIP-51504 general decode incoming message() error: Cause: The DecodeIncomingMessage() method fails to decode the B2B message.
AIP-51505 general validation error: Cause: An unexpected error occurred during validation.
AIP-51550 invalid usage code: Cause: The usage code must be either Production or Test.
AIP-51551 invalid timestamp: Cause: The timestamp used is not in the following format: CCYYMMDDThhmmss.sssZ.
AIP-51552 mismatched PIP binding ID: Cause: The PIP binding ID in the initiating message does not match the PIP binding ID in the response message.
AIP-51553 mismatched PIP code: Cause: The PIP code in the initiating message does not match the PIP code in the response message.
AIP-51554 mismatched PIP instance ID: Cause: The PIP instance ID in the initiating message does not match the PIP Instance ID in the response message.
AIP-51555 mismatched PIP version: Cause: The PIP version in the initiating message does not match the PIP version in the response message.
AIP-51556 The message ID in the initiating message does not match the message ID in the RefTo field of the response message.: Cause: The message ID in the initiating message does not match the message ID in the RefTo field of the response message.
AIP-51557 The PIP binding ID exceeds 255 characters.: Cause: The PIP binding ID exceeds 255 characters. The maximum allowed is 255 characters.
AIP-51558 invalid IsSecureTransportRequired field: Cause: IsSecureTransportRequired can only be 'Yes' or 'No'.
AIP-51559 content-type mismatch: Cause: The content-type in the manifest does not match the content-type associated with the attachment.
AIP-51560 content ID mismatch: Cause: The content ID in the manifest does not match the content ID associated with the attachment.
AIP-51561 mismatched FromService/ToService: Cause: The FromService field in the initiating message does not match the ToService field in the response message.
AIP-51562 mismatched ToService/FromService: Cause: The ToService field in the initiating message does not match the FromService field in the response message.
AIP-51563 mismatched FromRole/ToRole: Cause: The FromRole field in the initiating message does not match the ToRole field in the response message.
AIP-51564 mismatched ToRole/FromRole: Cause: The ToRole field in the initiating message does not match the FromRole field in the response message.
AIP-51565 error initializing XML parser: Cause: An unexpected error occurred while initializing the XML parser.
AIP-51566 parse stream error: Cause: An unexpected error occurred while parsing the input stream.
AIP-51567 invalid content-type: Cause: The subtype of the content-type in the HTTP header has to be either multipart/related or multipart/signed.
AIP-51568 encode error: Cause: An unexpected error occurred while encoding data.
AIP-51569 decode error: Cause: An unexpected error occurred while decoding data.
AIP-51570 form attachment error: Cause: An unexpected error occurred while forming attachment as component data.
AIP-51571 form attachment error: Cause: An unexpected error occurred while forming attachment as XML data.
AIP-51572 error reading input stream: Cause: An unexpected error occurred while reading input stream.
AIP-51700 error during packaging--general error: Cause: An unexpected error occurred during packaging.
AIP-51701 error during action performance--general error: Cause: An unexpected error occurred while servicing the RosettaNet Business Message.
AIP-51702 error during action performance--validating the service content against a PIP-specified dictionary: Cause: An error occurred while servicing the RosettaNet Business Message. The service content fails validation against the PIP-specific dictionary.
AIP-51703 error during unpackaging--general error: Cause: An unexpected error occurred during unpackaging the RosettaNet Business Message.
AIP-51704 error during unpackaging--verifying the signature of the RosettaNet business message: Cause: An error occurred while verifying the signature of the RosettaNet Business Message.
AIP-51705 error during unpackaging--reading the preamble: Cause: An error occurred during unpackaging the RosettaNet Business Message. The preamble cannot be read correctly.
AIP-51706 error during unpackaging--validating the preamble: Cause: An error occurred during unpackaging the RosettaNet Business Message. The preamble is invalid.
AIP-51707 error during unpackaging--reading the delivery header: Cause: An error occurred during unpackaging the RosettaNet Business Message. The delivery header cannot be read correctly.
AIP-51708 error during unpackaging--validating the delivery header: Cause: An error occurred during unpackaging the RosettaNet Business Message. The delivery header is invalid.
AIP-51709 error during unpackaging--reading the service header: Cause: An error occurred during unpackaging the RosettaNet Business Message. The service header cannot be read correctly.
AIP-51710 error during unpackaging--validating the service header: Cause: An error occurred during unpackaging the RosettaNet Business Message. The service header is invalid.
AIP-51711 error during unpackaging--verifying manifest against the attachment body parts: Cause: An error occurred during unpackaging the RosettaNet Business Message. The verification of the manifest in the service header against the actual attachment body parts failed.
AIP-51712 error during unpackaging--validating the message sequence: Cause: An error occurred during unpackaging the RosettaNet Business Message. Validation of the message sequence failed.
AIP-51713 unexpected response type in the HTTP header: Cause: An unexpected error occurred during unpackaging the RosettaNet Business Message. The response type in the HTTP header is not understood.
AIP-51714 error decrypting the message: Cause: An error occurred during unpackaging the RosettaNet Business Message. Decryption of the message failed.
AIP-51715 error during unpackaging--reading the service content: Cause: An error occurred during unpackaging the RosettaNet Business Message. The service content cannot be read correctly.
AIP-51716 error during unpackaging--validating the service content: Cause: An error occurred during unpackaging the RosettaNet Business Message. The service content is invalid.

AIP-51801 to AIP-51928 RosettaNet Validation Error Codes

AIP-51801 The XML document to be validated is empty.: Cause: The XML document to be validated is empty.
AIP-51802 Validation rule ID = "{0}" failed. Node "{1}" is required.: Cause: Validation rule ID = "{0}" failed. Node "{1}" is required.
AIP-51803 Validation rule ID = "{0}" failed. If "{1}", then "{2}" is required.: Cause: Validation rule ID = "{0}" failed. If "{1}", then "{2}" is required.
AIP-51804 Validation rule ID = "{0}" failed. "{1}" must be one of the allowed instance values in message guidelines.: Cause: Validation rule ID = "{0}" failed. "{1}" must be one of the allowed instance values in message guidelines.
AIP-51805 Validation rule ID = "{0}" failed. "{1}" must be in "{2}" format.: Cause: Validation rule ID = "{0}" failed. "{1}" must be in "{2}" format.
AIP-51806 Validation rule ID = "{0}" failed. If "{1}" exists, then sub-node "{2}" is required.: Cause: Validation rule ID = "{0}" failed. If "{1}" exists, then sub-node "{2}" is required.
AIP-51807 Validation rule ID = "{0}" failed. "{1}" must be "{2}".: Cause: Validation rule ID = "{0}" failed. "{1}" must be "{2}".
AIP-51808 The XML parser generated an error while parsing the document. The parser error is "{0}".: Cause: The XML parser generated an error while parsing the document. The parser error is "{0}".
AIP-51809 The XML parser encountered an I/O error while parsing the document. The error is "{0}".: Cause: The XML parser encountered an I/O error while parsing the document. The error is "{0}".
AIP-51810 Validation rules "{0}" failed.: Cause: Validation rules "{0}" failed.
AIP-51811 The document to be validated has no DTD specified.: Cause: The document to be validated has no DTD specified.
AIP-51851 unknown validation constraint: Cause: Unknown validation constraint validated.
AIP-51861 An internal error occurred while validating the document. The internal error code is "{0}".: Cause: An internal error occurred while validating the document. The internal error code is "{0}".
AIP-51901 RN_Tag-"{1}": The element "{2}" must have a value "{3}".: Cause: RN_Tag-"{1}": The element "{2}" must have a value "{3}".
AIP-51902 RN_Tag-"{1}": The element "{2}" must have one of these values: ("{3}").: Cause: RN_Tag-"{1}": The element "{2}" must have one of these values: ("{3}").
AIP-51903 RN_Tag-"{1}": The element "{2}" is required.: Cause: RN_Tag-"{1}": The element "{2}" is required.
AIP-51904 RN_Tag-"{1}": The element "{2}" must be a number with up to 3 digits before and after an optional decimal point.: Cause: RN_Tag-"{1}": The element "{2}" must be a number with up to 3 digits before and after an optional decimal point.
AIP-51905 RN_Tag-"{1}": The value of element "{2}" must be a string with minimum length "{3}".: Cause: RN_Tag-"{1}": The value of element "{2}" must be a string with minimum length "{3}".
AIP-51906 RN_Tag-"{1}": The value of element "{2}" must be a string with length between "{3}" and "{4}".: Cause: RN_Tag-"{1}": The value of element "{2}" must be a string with length between "{3}" and "{4}".
AIP-51907 RN_Tag-"{1}": The element "{2}" must be an integer up to 15 digits.: Cause: RN_Tag-"{1}": The element "{2}" must be an integer up to 15 digits.
AIP-51908 RN_Tag-"{1}": The element "{2}" must be in correct date format (YYYYMMDDZ: where YYYY is the year, MM is the month, DD is the day. Optional character 'Z' indicates that the date is in UTC.: Cause: RN_Tag-"{1}": The element "{2}" must be in correct date format (YYYYMMDDZ: where YYYY is the year, MM is the month, DD is the day. Optional character 'Z' indicates that the date is in UTC.
AIP-51909 RN_Tag-"{1}": The element "{2}" must be in correct date-time format (YYYYMMDDThhmmss.sssZ: where YYYY is year, MM is month, DD is day. Character 'T' separates date and time. hh is hour, mm is minutes, ss.sss is seconds. Optional character 'Z' indicates that the date is in UTC.: Cause: RN_Tag-"{1}": The element "{2}" must be in correct date-time format (YYYYMMDDThhmmss.sssZ: where YYYY is year, MM is month, DD is day. Character 'T' separates date and time. hh is hour, mm is minutes, ss.sss is seconds. Optional character 'Z' indicates that the date is in UTC.
AIP-51910 RN_Tag-"{1}": The value of element "{2}" must be a valid day of the month (an integer between 1 and 31).: Cause: RN_Tag-"{1}": The value of element "{2}" must be a valid day of the month (an integer between 1 and 31).
AIP-51911 RN_Tag-"{1}": The value of element "{2}" must be one of the instance values listed for that element in RosettaNet message guidelines.: Cause: RN_Tag-"{1}": The value of element "{2}" must be one of the instance values listed for that element in RosettaNet message guidelines.
AIP-51912 RN_Tag-"{1}": The value of element "{2}" must be a valid DUNS number (9 digit integer).: Cause: RN_Tag-"{1}": The value of element "{2}" must be a valid DUNS number (9 digit integer).
AIP-51913 The element "{2}" is not allowed.: Cause: The element "{2}" is not allowed.
AIP-51914 RN_Tag-"{1}": The value of element "{2}" must be alphanumeric with minimum string length "{3}".: Cause: RN_Tag-"{1}": The value of element "{2}" must be alphanumeric with minimum string length "{3}".
AIP-51915 RN_Tag-"{1}": The value of element "{2}" must be one of the instance values specified in message guidelines. Also, if the GlobalPurchaseOrderTypeCode is 'Quote to order', then the only allowed value is 'Quote'.: Cause: RN_Tag-"{1}": The value of element "{2}" must be one of the instance values specified in message guidelines. Also, if the GlobalPurchaseOrderTypeCode is 'Quote to order', then the only allowed value is 'Quote'.
AIP-51916 RN_Tag-"{1}": If GlobalPurchaseOrderType is 'Government', then "{2}" is required. Also the value of "{2}" must be from one of the instance values given in message guidelines.: Cause: RN_Tag-"{1}": If GlobalPurchaseOrderType is 'Government', then "{2}" is required. Also the value of "{2}" must be from one of the instance values given in message guidelines.
AIP-51917 RN_Tag-"{1}": The value of element "{2}" must be a 9-digit integer followed by a 4-letter string (DUNS 9+4 location format).: Cause: RN_Tag-"{1}": The value of element "{2}" must be a 9-digit integer followed by a 4-letter string (DUNS 9+4 location format).
AIP-51918 RN_Tag-"{1}": The value of element "{2}" must be a string between 3 and 15 digits (GlobalNationalPostalCode).: Cause: RN_Tag-"{1}": The value of element "{2}" must be a string between 3 and 15 digits (GlobalNationalPostalCode).
AIP-51919 RN_Tag-"{1}": If "{3}", then "{2}" is required.: Cause: RN_Tag-"{1}": If "{3}", then "{2}" is required.
AIP-51920 RN_Tag-"{1}": If "{3}", then "{2}" is required. The value of "{2}" must be one of the instance values listed in RosettaNet message guidelines.: Cause: RN_Tag-"{1}": If "{3}", then "{2}" is required. The value of "{2}" must be one of the instance values listed in RosettaNet message guidelines.
AIP-51921 RN_Tag-"{1}": If "{2}" is specified, then either netTermsDay.DayOfMonth or netTermsDays.CountableAmount is required.: Cause: RN_Tag-"{1}": If "{2}" is specified, then either netTermsDay.DayOfMonth or netTermsDays.CountableAmount is required.
AIP-51922 RN_Tag-"{1}": Either "{2}" or "{3}" is required.: Cause: RN_Tag-"{1}": Either "{2}" or "{3}" is required.
AIP-51923 RN_Tag-"{1}": The value of element "{2}" must be a real number.: Cause: RN_Tag-"{1}": The value of element "{2}" must be a real number.
AIP-51924 RN_Tag-"{1}": The value of element "{2}" must be a string with length between 2-4 (GlobalCarrierCode).: Cause: RN_Tag-"{1}": The value of element "{2}" must be a string with length between 2-4 (GlobalCarrierCode).
AIP-51925 RN_Tag-"{1}": The value of element "{2}" must be a 14-digit integer (GlobalProductIdentifier).: Cause: RN_Tag-"{1}": The value of element "{2}" must be a 14-digit integer (GlobalProductIdentifier).
AIP-51926 RN_Tag-"{1}": The value of element "{2}" must be a real number with up to 13 digits before the decimal point and up to 5 digits after the decimal point (9(13)V9(5)).: Cause: RN_Tag-"{1}": The value of element "{2}" must be a real number with up to 13 digits before the decimal point and up to 5 digits after the decimal point (9(13)V9(5)).
AIP-51927 RN_Tag-"{1}": Element "{2}" is required if the corresponding GlobalBusinessIdentifier is not specified. The value must be a string with nonzero length.: Cause: RN_Tag-"{1}": Element "{2}" is required if the corresponding GlobalBusinessIdentifier is not specified. The value must be a string with nonzero length.
AIP-51928 RN_Tag-"{1}": The value of element "{2}" must be alphanumeric with string length between "{3}" and "{4}".: Cause: RN_Tag-"{1}": The value of element "{2}" must be alphanumeric with string length between "{3}" and "{4}".

C Error Codes

AIP-10000 to AIP-10438 Runtime Error Codes

AIP-11000 to AIP-11999 Repository Error Codes

AIP-12000 to AIP 12600 Adapter Error Codes

AIP-13000 to AIP-16014 Business Logic Layer Error Codes

AIP-14000 to AIP-14018 Transformation Error Codes

AIP-14100 to AIP-14114 Translation Error Codes

AIP-14115 to AIP-14119 XSD Translation Error Codes

AIP-14321 to AIP-14325 Event Validation Error Codes

AIP-14401 to AIP-14406 Correlation Error Codes

AIP-14451 to AIP-14455 Domain Value Map Error Codes

AIP-16020 to AIP-17997 Metadata Validation Rules Error Codes

AIP-18000 to AIP-18999 Deployment Error Codes

AIP-19000 to AIP-19999 UI Modeling Error Codes

AIP-50000 to AIP-51999 Transport Error Codes

AIP-51801 to AIP-51928 RosettaNet Validation Error Codes

C
Error Codes