Choosing Position PVO from BICC - PositionPVO vs PositionPVOViewAll — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

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.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!