3 Message Formats

Data exchanged between Oracle Banking Treasury Management and the external systems will be in the form of XML messages. These XML messages are defined in OBTR in the form of XML Schema Documents (XSD) and are referred to as ‘OBTR formats’. An XML Schema is uniquely identified by its Namespace and its Root Element (root node).

The root node for XSDs of gateway messages are generated as per the following pattern:

• <OPERATION>_<MESSAGE EXCHANGE PATTERN>_REQ
• <OPERATION>_<MESSAGE EXCHANGE PATTERN>_RES

where,

• <OPERATION> refers to an Oracle Banking Treasury Management operation like CREATECUSTACC
• <MESSAGE_EXCHANGE_PATTERN> refers to the request & response message patterns exchanged.

The Message Pattern is of the following types

• FS (Full Screen) -This indicates that the payload will contain all the elements on the corresponding Oracle Banking Treasury Management screen.
• IO (Input Only) - This indicates that the payload will contain the only input elements on the corresponding Oracle Banking Treasury Management screen.
• IO (Input Only) - This indicates that the payload will contain the only input elements on the corresponding Oracle Banking Treasury Management screen.
• PK (Primary Key): This indicates that the payload will contain only the Primary Key elements of the corresponding Oracle Banking Treasury Management screen

. <MESSAGE_EXCHNAGE_PATTERN> is a combination of message patterns. The <MESSAGE_EXCHNAGE_PATTERN> available in OBTR is shown below:

• FSFS - Full Screen Request and Full Screen Response
• IOPK - Input Only Request and Primary Key Response
• IOFS - Input Only Request and Full Screen Response

This topic has the following sub-topics:

• Non-query Formats
  This topic describes the non-query and query formats.
• Oracle Banking Treasury Management Envelope
  The OBTR Envelope topic explains the OBTR header and body components.
• Oracle Banking Treasury Management Notification
  This topic describes the generated notification messages.