E-AD: Which Setting Controls Whether the DDL Script, Generated by Application Designer, Will Take Into Account the Field Defaults Defined in the Record Definition ?
(Doc ID 2676813.1)
Last updated on JUNE 03, 2020
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.57 and later
Information in this document applies to any platform.
Which setting controls whether the DDL script, generated by Application Designer, will take into account the field defaults defined in the Record Definition?
The PORTAL_CSS_RUN table, for example, has defaults on Fields PORTAL_FLDRP_FLAG, PORTAL_CREFP_FLAG and PT_PRTL_SYNC_ALL, as observed in Application Designer.
The DDL script that is generated by Application Designer, when building that Record, will take into account those defaults.
Taking the VOUCHER table as another example, that table does have lots of fields with default values as well. Yet, the DDL script for that table does NOT take any of those defaults into account.
The question is: Why? What's different in the PORTAL_CSS_RUN table that makes the DDL script to be generated with defaults? What's different in the VOUCHER table that makes the DDL script to be generated with NO defaults?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document