My Oracle Support Banner

E-AD: PS Build Script does not Respect Field Definition in Application Designer for Certain Types of Numbers (Doc ID 2664387.1)

Last updated on APRIL 28, 2020

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.57 and later
Information in this document applies to any platform.

Symptoms

When building records on Oracle through Application Designer, the build script is NOT taking into account what is defined in Field Definition for certain types of numbers. The build script that is generated converts certain numbers through aliases. For example:

CREATE TABLE PSOPRDEFN (
...
PTALLOWSWITCHUSER SMALLINT NOT NULL) ...

Note: Field definition PTALLOWSWITCHUSER is defined in Application Designer as Numer, with Integer Positions: 1, Decimal Positions: 0


Aliases that are used:

ALIAS             FIELD WILL BE CREATED IN ORACLE AS:
--------------------------------------------------------------

INT                 NUMBER(38)
SMALLINT        NUMBER(38)
NUMBER(p,s)   NUMBER(p,s)
DECIMAL(p,s)  NUMBER(p,s)

In the example above, SMALLINT will translate to NUMBER(38) on Oracle.

 

 
 
The issue can be reproduced at will with the following steps:
1. Create a Record in Application Designer, containing a field that is defined as Number(1), e.g.: PTALLOWSWITCHUSER
2. Create the build SQL script
3. Check the build SQL script. The field is created throuh an alias, in this case: PTALLOWSWITCHUSER SMALLINT NOT NULL
4. Run the build sql script on the database.
5. Check the description of the table. For the field in the example above, it will be created as:
    PTALLOWSWITCHUSER NOT NULL NUMBER(38)



Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.