Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.8K Databases
- 221.5K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 477 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.8K SQL & PL/SQL
- 21.3K SQL Developer
- 295.4K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.1K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 27 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 392 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 230 Portuguese
PeopleSoft: Fluid Position Data is not saving in classic position record

The development team is encountering an issue in our development environment when we are trying to transact in Fluid Position Data.
The issue is when we save a new row in position through the fluid position data, the row is saved in the fluid record PS_POSITION_DATA_E but not in the classic record PS_POSITION_DATA. We already validated that this is working as expected in the demo (delivered) environment, but when we made some changes in according to the requirement, we are experiencing this issue.
We can see some logged CI exception messages through the peoplecode trace, but we cannot see where we can find the consolidated messages or even if the classic CI (CI_POSITION_DATA) was actually called by the fluid CI (CI_POSITION_DATA_FL).
Does anyone experienced this when implementing the Fluid Position Data in their end?
Answers
-
Make sue that your Position is approved after you have saved. Field for workflow status WF_STATUS from PS_POSITION_DATA_E. on approval of the Fluid position the data from PS_POSITION_DATA_E will get copied to PS_POSITION_DATA Record.
-
This happened to us due to the user being an approver but the row security of the user is not sufficient (has no access to the Department or dept tree). The CI fails since it cannot call the Job Data.