E-AD: Fields Copied To Target Database Even If Field Definition Is Not In Project
Last updated on JANUARY 04, 2017
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.4 and later
Information in this document applies to any platform.
If a record contains a new field that is not in the target database, and the project containing that record is copied, the field is automatically created in the target database.
For example, the Field exists in one of the Records in the project, but the actual Field Definition itself is not in the project. In such a scenario, when the project copy was done, the field was created in the database automatically.
The field should not be created automatically. Since the Field Definition itself is not in the project, you cannot select an Action for it, or check/uncheck the "Upgrade" flag manually.
The issue exists even in PeopleTools 8.50, 8.51 and 8.52.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms