Specify Time Zone for Validating Effective Status of Purchase Agreements
Set a time zone for validating the effective status of purchase agreements. Before this release, if you were operating in regions with large UTC offsets, your agreement would become effective or expire much earlier or later than intended. Now, you can set a UTC offset using a profile option value that the application will use to determine if the agreement is currently active.
With this feature, application converts the agreement sourcing date to the time zone specified by the profile option. The converted date is used to determine the effective status of an agreement and agreement line.
Here are some examples:
This table provides an example of a blanket purchase agreement configured with the start date and end date.
| BPA | Start Date | End Date | BPA Line | Item | Price | Line Expiration Date |
|---|---|---|---|---|---|---|
| 1003801 | July 1, 2025 | July 11, 2025 | 1 | Liquid Soap | 11 | July 11, 2025 |
| 1003802 | July 12, 2025 | July 31, 2025 | 1 | Liquid Soap | 12 | July 31, 2025 |
A purchase order created on 19:00:00 hours on July 11, 2025 UTC.
This table depicts the source agreement and source agreement line you can select on the purchase order based on the value of the profile option.
| Profile Option Value | Current Date | Current Date Converted to Specified Time Zone | Source Agreement LOV | Source Agreement Line LOV | Price |
|---|---|---|---|---|---|
| UTC+9 | July 11, 2025 19:00 PM UTC | July 12, 2025 04:00 AM | 1003802 | 1 | 12 |
| Not Set | July 11, 2025 19:00 PM UTC | July 11, 2025 19:00 PM UTC | 1003801 | 1 | 11 |
Converted application date is used to validate purchase agreements for catalog search results.
Shopping Catalog Search Results
| Profile Option Value | Search Term | Current Date | Current Date Converted to Specified Time Zone | Search Results | ||
|---|---|---|---|---|---|---|
| Agreement | Line | Price | ||||
| UTC+9 | Liquid Soap | July 11, 2025 19:00 PM UTC | July 12, 2025 04:00 AM |
1003802 | 1 | 12 |
| Not Set | Liquid Soap | July 11, 2025 19:00 PM UTC | July 11, 2025 19:00 PM UTC |
1003801 | 1 | 11 |
Converted requested delivery date is used to validate purchase agreements when processing a punchout payload.
Punchout Cart
| Profile Option Value | Item Description | Requested Delivery Date | Requested Delivery Date Converted to Specified Time Zone | Agreement Data | Is Agreement Valid? | |
|---|---|---|---|---|---|---|
| Agreement | Line | |||||
| UTC+9 | Liquid Soap | July 11, 2025 11:59 PM UTC | July 12, 2025 08:59 AM | 1003801 | 1 | No |
| Not Set | Liquid Soap | July 11, 2025 11:59 PM UTC | July 11, 2025 11:59 PM UTC | 1003801 | 1 | Yes |
This screen capture illustrates the feature.
Set Time Zone Using Profile Option
Steps to Enable
You must enable the Time Zone Reference for Procurement (ORA_PO_PROCUREMENT_TZ) profile option to access the feature and convert UTC time zone to local time zone.
To enable the profile option, follow these steps:
- In the Setup and Maintenance work area, search and select the Manage Purchasing Profile Options task.
- On the Manage Purchasing Profile Options page, search for and select the profile option name or code.
- Set the Profile Value at required local time zone.
- Click Save and Close. Changes in the profile value will affect users the next time they sign in.
Tips And Considerations
- For purchasing flows, the feature is supported in both classic UI and Redwood environments.
- The current date is used for agreement line sourcing and validation if both these features are enabled. The application converts the current date from UTC to the time zone specified by the profile option.
- Specify a Start Date for Blanket Purchase Agreement Lines
- Use Order Date to Determine the Price on Purchase Orders
- When requested date is used for agreement and agreement line sourcing and validation, the application assumes the requested date to be in the time zone of the purchase order's ship-to organization if the Use the Deliver-to Inventory Organization Time Zone When Fulfilling Supply Chain Demand feature is enabled. If the feature isn't enabled, the requested date is assumed to be in the time zone of purchase order legal entity. If a time zone isn't set for the purchase order legal entity, the requested date is converted from UTC to the time zone specified by the profile option.
- The converted date is used to validate purchase agreements in these purchase requisition flows:
- Enter Requisition Line
- Noncatalog Request
- Smart Form
- The converted date is used to validate purchase agreements in these purchasing flows:
- Process requisitions
- Approved supplier list
- Edit Purchase Order
- Automatic document sourcing
- Retroactive pricing
- Generate Orders
- Touchless PO creation
- Draft Purchase Order REST API
- File-Based Data Import (FBDI)
- When this feature is used:
- The converted current date is used to populate the end date search parameter for expiring and expired purchase agreement infolets.
- The include closed and expired documents search parameter on the Manage Agreements search page in the classic UI displays purchase agreements that has expired as per the converted current date.
Access Requirements
No specific privileges are needed to specify time zone for validating effective status of purchase agreements.