PERSON_BASIC_SYNC IB messages via the PSFT_XOUTBND Node Are Active in CS Bundle #44
(Doc ID 2240922.1)
Last updated on FEBRUARY 03, 2019
Applies to:PeopleSoft Enterprise CS Campus Community - Version 9 and later
Information in this document applies to any platform.
Why is the node PSFT_XOUTBND within CS Bundle #44 active?
It is trying to send PERSON_BASIC_SYNC IB messages via the PSFT_XOUTBND node back to Oracle's development servers (sdc60004sems.us.oracle.com/sdc60010sems.us.oracle.com).
Research shows the following:
- The basic IB configuration is identical in all the environments.
- The active routing PERSON_BASIC_SYNC_TO_AIA is indeed pointing to the oracle website. (sdc60004sems.us.oracle.com/sdc60010sems.us.oracle.com).
- The only differences I can see from within the configuration of the PERSON_BASIC_SYNC Service Operation are:
In patch environment – there are two ACTIVE – PERSON_BASIC_SYNC_TO_AIA and SCC_PERSON.
In production, only the PERSON_BASIC_SYNC_TO_AIA is active.
In patch environment – there are three ACTIVE handlers – HRS_JPM_SYNC,SCC_PERSON, and SCC_SERVICE
In production, only the HRS_JPM_SYNC handler is active
- No reason PERSON_BASIC_SYNC messages being generated in PRD.
What is the purpose of these new messages?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document