Important! The outputs of the COA Mapping Tool should not be used as the source of truth to transact in Oracle. This tool should only be used to visualize a potential translation from 10 digit FAS account to a multi-segment COA and POETAF string. Review the individual segments within Oracle to ensure your COA segments are accurate.

Upon entering a COA or POETAF string into Oracle for the first time, the combination may not be "found" in Oracle, even if it is correct. Leverage Oracle Guided Learning (OGL) in the system to guide you through the process.

The COA Hierarchies Orbit Report provides a comprehensive view of each segment's hierarchy.

Additional Chart of Accounts Resources

Choose the Procurement Categories - Non-Catalog and Payment Request that most closely matches your purchase.

Payment Requests in Oracle should be used in select cases only. For example, invoices with contractors and recurring payments should not use payment requests. These should have an associated purchase order.

For goods and services not found in a punchout or local catalog, a Non-Catalog Requisition should be created.

Oracle Transition Status

• This document provides guidance on what various status updates mean in Oracle, including approvals, payment and workflow status, and more.

Buying Troubleshooting Guide

BuySite Purchase Order Conversion (requires UChicago Intranet log in)