Inbound Response Format

TIBCO BusinessConnect RosettaNet Protocol uses the following message class to forward inbound response messages to the initiator private process.

Class BCResponseToPP

Installation prefix.installation.INITIATOR.RESPONSE (JMS queue)

Message Fields

BCResponseToPP Fields
Message Field Type Required Description
transaction ID String No The tracking identifier specified by the initiator private process when it initiates the PIP request.

See the description of transactionID in Table 19, BCRequestFromPP Message Fields, on page 65 for more information on how to specify a tracking identifier for a PIP transaction. This field is empty if no transactionID is defined by initiator private process in the corresponding BCRequestFromPP message.

standardID String Yes The string "RosettaNet".
operationID String Yes

A three-part PIP ID of the following format:

PIP/version/activity.

For eample: 3A4/1.4/Create Purchase Order.

closure String No Reserved
sender RosettaNet/ Info/TPInfo Yes The initiating trading partner. See See TPInfo Fields for formatting information.
Note: You must copy the value of this field fromthe original BCRequestToPP message
receiver RosettaNet/Info/TPInfo Yes The responding trading partner. See TPInfo Fields for formatting information.
extraInfo RosettaNet/ Response/ RNResponse FromPP Yes RosettaNet protocol specific data.

See RNResponseFromPP Object, on for formatting information.

attachment List Sequence of RosettaNet/Info/ AttachmentInfo No A sequence of attachments. See AttachmentInfo Object on for formatting information.
response String No The content of the entire RosettaNet PIP response. See Request and Response Fields for formatting information. Do not use this field to send an exception response, but use the status field instead
file Reference String No

The absolute path of the file containing the PIP request document.

RNResponseToPP Object

Included in the extraInfo field is the RNResponseToPP object, RosettaNet/Response/RNResponseToPP. This object contains useful information extracted from the MIME-formatted message. See the following table for a description of each field:
RNResponseToPP Object
Message Field Type Description
globalUsage Code String The PIP mode extracted from the <GlobalUsageCode> element in the inbound response document’s preamble header.
messageSent String The time stamp of the received PIP response.

This field is formatted as follows:

YYYY/MM/DD HH:MM:SS.SSS.

For example:

2007/08/30 14:41:35.500

rnifVersion String The RNIF version extracted from the <VersionIdentifier> element in the inbound response document’s preamble header.
pipCode String The PIP code extracted from the <GlobalProcessIndicatorCode> element of the inbound response document’s service header.
pipVersion String The PIP version extracted from the <VersionIdentifier> element of the inbound response document’s service header.
pip Transaction String The name of the PIP transaction extracted from the <GlobalTransactionCode> (RNIF 1.1) or <BusinessActivityIdentifier> (RNIF 2.0) element of the inbound response document’s service header.
pipAction String The name of the PIP transaction extracted from theActionControl/ActionIdentity/GlobalBusinessActionCode element of the inbound responsedocument’s service header.
process Instance Identifier String The instance identifier extracted from theProcessIdentity/InstanceIdentifier (RNIF 1.1) orpipInstanceId/InstanceIdentifier (RNIF 2.0) element of the inbound response document’s service header
transaction Identifier String (RNIF 1.1 only) The transaction’s instance identifier extracted from the TransactionIdentity/InstanceIdentifier element of the inbound response document’s service header. RNIF 1.1 only.
transaction AttemptCount Integer (RNIF 1.1 only) Number for the current attempt (first one is 1) extracted from the <AttemptCount> element of the inbound response document’s service header.
proprietary Document Identifier String The value of the<proprietaryDocumentIdentifier> element in the inbound response document.