3.

1 Automatic Updates to General Ledger (GL) Date

Description Requesters can specify the GL date (encumbrance date) for each distribution against a line at the time of
creating purchase orders. If the value of the GL Date is invalid, for example, the date is in a closed GL period,
or in a period that is not yet open, then the application automatically defaults the GL date to the system date if
the current period is open. The GL date is also validated during the time the purchase order is submitted for
approval. To use this feature, the value of the PO: Validate GL Date Period profile option must be set to the
newly introduced Redefault value.
New, Changed, This section lists the components that were added, changed, or made obsolete for this feature in Oracle
Obsolete iProcurement in Release Procurement Family R12.1.3 September Update 2012. These components may include
Components the following: forms, windows, reports, C programs, SQL*Loader programs, workflows, alerts, tables, or APIs.

For additional information, refer to the Oracle Electronic Technical Reference Manuals (eTRM) located on My
Oracle Support.

Changed Windows or Pages

This table lists the changed windows and pages.

Changed Window or Page Technical Name Description

Name
Checkout Requisition CheckoutSummaryPG Setting of the PO: Validate GL Period profile
Information option impacts the GL Date field. Purchasing
administrators can set the PO: Validate GL Period
profile option value to Redefault, so that the GL
date is automatically corrected to the system date,
if found invalid.
Requisition Information: Edit CheckoutLinesPG Setting of the PO: Validate GL Period profile
Lines option impacts the GL Date field. Purchasing
administrators can set the PO: Validate GL Period
 profile option value to Redefault, so that the GL
date is automatically corrected to the system date,
if found invalid.
Changed Profile Options

This table lists the changed profile options.

Changed Profile Option Feature Area Description

PO: Validate GL Period GL Date in This existing profile option controls the validation of
purchase order the GL Date in purchase order distributions and
distributions requisition distributions.
and requisition
distributions Currently, two values are available for this profile
option:

 Yes: The application verifies the GL date and

displays an error message if the date is
invalid, for example, the date is in a closed
GL period or in a period that is not yet open.
Buyers must modify the date to reflect a valid
date. Yes is the default value.
 No: The application does not validate the GL
date.

With this release, a new Redefault value is available.

Purchasing administrators can select this value, so
that if the date is found invalid, for example, the date
is in a closed GL period, or in a period that is not yet
open, the application automatically corrects the GL
date to reflect the current system date. A message
informs the buyer that the GL date is updated
 automatically.
Changed Public APIs

This table lists the changed APIs.

Changed API Name Description

POXCOPES.pls Includes a new procedure
PO_PERIODS_SV.build_GL_Encumbered_Date to build the
GL Date and Period Name when the PO:Validate GL Period
profile option is set to Redefault.
New Custom Hook

This table lists the new custom hooks.

Changed API Name Description

PO_CUSTOM_FUNDS_PKG.plb A new procedure gl_date
(PO_CUSTOM_FUNDS_PKG.gl_date) is available to write
custom code to default the GL Date.

Implementation New and Changed Setup Steps

Considerations
This section lists the setup steps that were added or changed for Oracle iProcurement in Release Procurement
Family R12.1.3 September Update 2012.

To automatically correct the invalid GL date to system date, complete the following steps:

1. Log in to the System Administrator responsibility.

2. Navigate to the System Profiles window.

 3. Search for the PO:Validate GL Period profile option.

4. Select the Redefault value at the appropriate level.

Upgrade Considerations

There are no upgrade considerations for this feature.

Sizing

Tablespace Considerations

There are no tablespace considerations for this feature.

Performance Considerations

XMLDB Usage

There are no XMLDB usages for this feature.

Load Balancing

There is no load balancing information for this feature.

New Bulk Interfaces

There are no new bulk interfaces for this feature.