The adapter exposes the FINDKEYS functionality of PeopleSoft Component Interface technology as a feature which can be used with the adapter's Request-Response Service. If the
FINDKEYS values are specified in the incoming request, they take precedence over any
GETKEYS or
CREATEKEYS values specified. The adapter's Request-Response Service uses the same to query PeopleSoft and return a sequence of
FINDKEY keys with values, which satisfy the query criterion, as a reply. Please note that any other part of the incoming request (
GETKEYS,
CREATEKEYS or
PROPERTIES) is ignored.
Fields in FINDKEYS should be a superset of fields in
GETKEYS() as the fields under these will decide the query criterion.
The adapter primarily uses GETKEYS to update a particular record in PeopleSoft. For Request-Response Service, if the
FINDKEYS values are not specified in the incoming request, the adapter looks for
GETKEYS values. For a Subscription service, the adapter by default looks for
GETKEYS and ignores the
FINDKEYS completely.
If the GETKEYS values are specified (if not specified, see
CREATEKEYS), the adapter queries PeopleSoft to check if the record exists. If the record exists, the adapter updates that record in PeopleSoft fields with values specified under the
PROPERTIES keys.
The GETKEYS keys should be a subset of the
FINDKEYS keys. This is to avoid an error scenario wherein the adapter is trying to search a record with a key which is not a part of
FINDKEYS in the CI definition.
The adapter primarily uses CREATEKEYS to create a record in PeopleSoft. If neither
GETKEYS nor
FINDKEYS are specified in the incoming requests (or due to the conditions arising out of the two scenarios described in
GETKEYS), the adapter looks for
CREATEKEYS in the incoming request.
If specified, the adapter queries PeopleSoft to check if the record already exists. If the record is not found, the adapter creates a new record with the CREATEKEYS fields as primary fields and
PROPERTIES keys as values for the non-primary fields. If the record already exists, an error is thrown by the adapter saying
CREATEKEYS failed.
The CREATEKEYS should be a subset of the
FINDKEYS keys. This is to avoid an error scenario wherein the adapter is trying to search a record with a key which is not a part of
FINDKEYS in the CI definition.
In case of the Publication Service (CI based as well as Application Messaging based), the adapter populates the PROPERTIES with the values extracted from the parsed XML (obtained from the
TIB_CI_MQUEUE table). The
GETKEYS,
CREATEKEYS or
FINDKEYS hold no significance whatsoever.
PeopleSoft Component Interface can have multiple levels up to Level 3. The adapter can INSERT,
UPDATE or
DELETE the records at all these levels. In these case, the key fields should be present at all levels and the user needs to provide the operation code at all levels.
For all CREATEKEYS scenarios, specify
I as the value for
OPRN_CODE for all the records in the request.