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.
Choosing Position PVO from BICC - PositionPVO vs PositionPVOViewAll
Summary:
We are implementing a data warehouse and establishing BICC data extraction pipelines. In reviewing the available PVOs for HCM Position data, there are two relevant PVOs:
• HcmTopModelAnalyticsGlobalAM.PositionAM.PositionPVO
• HcmTopModelAnalyticsGlobalAM.PositionAM.PositionPVOViewAll
We are trying to discover which is the most performant option for BICC pipeline to our warehouse.
Content:
There are two relevant PVOs in BICC for Positions. In each View Object (VO), there exists the same number and identify of view object attributes, and the primary key table for both is HR_ALL_POSITIONS_F. The total number and identities of view object attributes are the same in both VOs.
Tagged:
1