User-Defined Fields
Oracle provides 22 user-defined fields on the PS_PENDING_ITEM table in the delivered system that are exclusively for your use. These fields are known as user fields. The following table lists the fields:
| Amount Fields | Date Fields | Character Fields |
|---|---|---|
|
USER_AMT1 |
USER_DT1 |
USER1 |
|
USER_AMT2 |
USER_DT2 |
USER2 |
|
USER_AMT3 |
USER_DT3 |
USER3 |
|
USER_AMT4 |
USER_DT4 |
USER4 |
|
USER_AMT5 |
|
USER5 |
|
USER_AMT6 |
|
USER6 |
|
USER_AMT7 |
|
USER7 |
|
USER_AMT8 |
|
USER8 |
|
|
|
USER9 |
|
|
|
USER10 |
You may want to make two types of modifications to user fields:
-
Changing the manner in which the fields are updated.
-
Adding more fields.
Changing User Fields
Currently, the system processes all character user fields the same way. Note that the system takes the RP_I_USER values from PS_ITEM USER1 if PS_ITEM is updated. The following statement rolls forward an existing value if none is present on the PENDING_ITEM record:
UPDATE %Table(RP_USER_TAO)
SET USER1 = RP_I_USER1
WHERE PROCESS_INSTANCE = %Bind(PROCESS_INSTANCE)
AND USER1 = ' '
You can change the way that you handle these fields on a case-by-case basis. You may want to specify that certain user fields not be overwritten if they have a value, regardless of the value on subsequent transactions. The following statement rolls forward an existing value even if a new value is present on the PENDING_ITEM that is to be processed:
UPDATE %Table(RP_USER_TAO)
SET USER1 = RP_I_USER1
WHERE PROCESS_INSTANCE = %Bind(PROCESS_INSTANCE)
AND RP_I_USER1 <> ' '
You can change the way that the system processes numerics and dates in a similar fashion. To make modifications, open the AR_POSTING Application Engine program in PeopleSoft Application Designer.
The following list shows the names of the sections that you need to modify based on the type of user field. You can modify the existing code or add a new effective-dated section with the changes.
-
Section USER_ALP (for alpha fields)
-
Section USER_NUM (for numeric fields)
-
Section USER_DAT (for date fields)
For more information, see the product documentation for PeopleTools: Application Designer Developer's Guide.