OutcomeService Messages Resulting in an 'Incomplete Data' Error.

(Doc ID 2420833.1)

Last updated on JULY 09, 2018

Applies to:

PeopleSoft Enterprise CS SA Integration Pack - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

On : 9.2 version, SA Integration Pack Set Up

OutcomeService failing to parse sendingAgentIdentifier

The SAIP OutcomeService is getting an "incompletedata" error. There appears to be a problem with the XML parsing, where it's not locating the sendingAgentIdentifier field in the request XML, so can't match up with the correct Target ID.

ERROR
-----------------------
Returning HttpStatusCode : 200
<imsx_syncResponseHeaderInfo xmlns="http://www.imsglobal.org/services/lis/oms1p0/wsdl11/sync/imsoms_v1p0"><imsx_version>V1.0<imsx_messageIdentifier/><imsx_statusInfo><imsx_codeMajor>failure<imsx_severity>error<imsx_messageRefIdentifier/><imsx_operationRefIdentifier/><imsx_description/><imsx_codeMinor><imsx_codeMinorField><imsx_codeMinorFieldName>TargetEndSystem<imsx_codeMinorFieldValue>incompletedata




STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Process outcomeservice using SAIP.


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms