Base Message Format in PeopleSoft Integration Broker

Before you create a transformation schema, it helps to understand the base XML document format used by PeopleSoft Integration Broker to package application data:

<?xml version="1.0"?>
<PeopleSoftMessageName>
	<FieldTypes>
		<RecordName1 class="R">
			<fieldname1 type="CHAR"/>
			<fieldname2 type="NUMBER"/>
			...
		</RecordName1>
		<RecordName2 class="R">
			<fieldname1 type="CHAR"/>
			<fieldname2 type="NUMBER"/>
			...
		</RecordName2>
		...
	</FieldTypes>
	<MsgData>
		<Transaction>
			<RecordName1 class="R">
				<fieldname1>Fieldvalue</<fieldname1>
				<fieldname2>Fieldvalue</<fieldname2>
				 ...
			<RecordName1>
			<RecordName2 class="R">
				<fieldname1 type="CHAR"/>
				<fieldname2 type="NUMBER"/>
				 ...
			</RecordName2>
		<PSCAMA class="R">
			<AUDIT_ACTN>ActionCode</AUDIT_ACTN>
         	</PSCAMA>	
					...
		</Transaction>
		...
	</MsgData>
</PeopleSoftMessageName>

This format is then packaged into an XML document for transmission to the target application. If you have attached one of the supported framework transformation programs to the message, the transformation program identifies the appropriate transformation map and applies the transformation schema to the message, modifying its structure. The message is then repackaged into an XML document in its altered form and delivered.

Note:

The transformation message must be supported by the transformation framework. Only supported programs can work with the transformation maps. You can also add configured Application Engine or XSLT transformation programs as part of the relationship definition independent of the transformation framework.

The transformation program can modify the following elements of the standard message structure:

Term	Definition
PeopleSoftMessageName	The name of the message as it is defined in PeopleSoft using Application Designer. The transformation program can change the message name.
FieldTypes	The metadata for the records and their fields. The transformation program can select the fields required by the target applications and can change their names.
Transaction	Contains the data for the records and their fields and organizes them into a hierarchy. The record tags at each level contain the fields for that record. The transformation program can select one or more record subsets and their fields or just a subset of fields required by the target service operation and can change their names.
PSCAM (PeopleSoft Common Application Message Attributes)	The last record within a transaction that provides information about the entire transaction. The PSCAMA record contains fields that are common to all messages. The <PSCAMA> tag repeats for each row in each level of the transaction section of the message. The sender can set PSCAMA fields to provide basic information about the message, for example, to indicate the message language or the type of transaction a row represents. The transformation program copies this structure to the target message structure.