Get Started with Redwood for Oracle Cloud HCM Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Job Code Configuration Advice-New to TBE
Summary
Looking for Advice-Job Requisition Job CodeContent
Hi, We use Peoplesoft Position Management and are using the Position data fields to drive many of the Job Requisition content in TBE (location, salary etc using an API). Position number is a one to one relationship to Job Code. Job Code is a one to many to Positions. I feel that I should use the Position Number as the TBE Job Code but not sure what the system wide implications are to TBE. May I obtain advice on the decision points that should be considered in making this decision?
One of the benefits I have seen with Position Data is that we will be able to search on Position which we would do more often than on job code. Short notice I know but we are anxious to hear any of your advice.
Tagged:
0