- Revision History
- Overview
- Optional Uptake of New Features (Opt In)
- Feature Summary
- Collaboration Messaging Framework
- Financials Common
- Accounting and Control
-
- Budgetary Control
- General Ledger
- Joint Venture Management
-
- Data Security for Joint Venture Management
- Descriptive Flexfields for Joint Venture Operational Measures
- Fixed Amount Overhead Method Type
- Joint Venture Partner Contribution Transfer
- Obsolete Profile Option for Descriptive Flexfields Enablement in Joint Venture Management
- Period Processing for Identify Joint Venture Transactions Process
- Joint Venture Overhead
-
- Subledger Accounting
- Payables and Expenses
- Receivables and Cash
- Asset and Lease Management
- Region and Country-Specific Features
- U.S. Federal Financials
Update 24A
Revision History
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
Date | Module | Feature | Notes |
---|---|---|---|
28 JUN 2024 | Expenses | Audit Evaluation of Resubmitted Expense Reports for Potential Duplicates | Updated document. Added link to Key Resources. |
31 MAY 2024 | India | India Document Numbering for Multiple Legal Reporting Units with the Same Tax Registration Number | Updated document. Added link to Key Resources. |
31 MAY 2024 | Financials for EMEA | Support for Additional Supply Chain Transactions in Portugal SAF-T | Updated document. Revised Key Resources. |
31 MAY 2024 | Assets | Total Cost Display for Parent Asset Addition Lines in Assets | Updated document. Added link to Key Resources. |
31 MAY 2024 | Revenue Management | Prospective Accounting Treatment for Immaterial Price Changes of Subscription Products | Updated document. Added link to Key Resources. |
31 MAY 2024 | Receivables | Third-Party Tax Registration Number Defaulting for Receivables Transactions | Updated document. Added link to Key Resources. |
31 MAY 2024 | Payables | Performance Improvements to the Payables Holds Infotile | Updated document. Added link to Key Resources. |
31 MAY 2024 | Payables | IDR Supplier Derivation in Email Subject | Updated document. Added link to Key Resources. |
31 MAY 2024 | Payables | Campaign Enhancements for Dynamic Discounting | Updated document. Added link to Key Resources. |
31 MAY 2024 | Payables | Assignment of Exception Categories to Payables Exceptions | Updated document. Added link to Key Resources. |
31 MAY 2024 | Subledger Accounting | Improvements to Transfer of Subledger Accounting Entries to General Ledger | Updated document. Added Tips & Considerations. |
31 MAY 2024 | General Ledger | Journal Attachments Audit to Monitor and Adhere to Compliance Policies | Updated document. Added link to Key Resources. |
29 MAR 2024 | U.S. Federal Financials | Federal DATA Act Reporting Configurations | Updated document. Revised feature information. |
29 MAR 2024 | General Ledger | Legal Entity-Specific Secondary Ledgers with Controlled Replication from Primary Ledgers | Updated document. Revised feature information. |
09 FEB 2024 | Common Financials | Approvals Work Area with Enhanced User Interface and Adaptive Search | Updated document. Added new feature in update 24A. |
02 FEB 2024 | Joint Venture Management | Data Security for Joint Venture Management | Updated document. Revised Opt In information |
02 FEB 2024 | Joint Venture Management | Joint Venture Overhead | Updated document. Revised Opt In information |
14 DEC 2023 | Assets | Segregation of Asset Transaction Entry and Transaction Posting Duties Using Spreadsheets | Updated document. Revised feature information. |
01 DEC 2023 | Created initial document. |
Overview
HAVE AN IDEA?
We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.
DISCLAIMER
The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.
This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.
Optional Uptake of New Features (Opt In)
Oracle Cloud Applications delivers new updates every quarter. This means every three months you'll receive new functionality to help you efficiently and effectively manage your business. Some features are delivered Enabled meaning they are immediately available to end users. Other features are delivered Disabled meaning you have to take action to make available. Features delivered Disabled can be activated for end users by stepping through the following instructions using the following privileges:
- Review Applications Offering (ASM_REVIEW_APPLICATIONS_OFFERINGS_PRIV)
- Configure Oracle Fusion Applications Offering (ASM_CONFIGURE_OFFERING_PRIV)
Here’s how you opt in to new features:
- Click Navigator > My Enterprise > New Features.
- On the Features Overview page, select your offering to review new features specific to it. Or, you can leave the default selection All Enabled Offerings to review new features for all offerings.
- On the New Features tab, review the new features and check the opt-in status of the feature in the Enabled column. If a feature has already been enabled, you will see a check mark. Otherwise, you will see an icon to enable the feature.
- Click the icon in the Enabled column and complete the steps to enable the feature.
In some cases, you might want to opt in to a feature that's not listed in the New Features work area. Here's how to opt in:
- Click Navigator > My Enterprise > Offerings.
- On the Offerings page, select your offering, and then click Opt In Features.
- On the Opt In page, click the Edit Features (pencil) icon for the offering, or for the functional area that includes your feature.
- On the Edit Features page, complete the steps to enable the feature.
For more information and detailed instructions on opting in to new features for your offering, see Configure Offerings.
Opt In Expiration
Occasionally, features delivered Disabled via Opt In may be enabled automatically in a future update. This is known as an Opt In Expiration. If your cloud service has any Opt In Expirations you will see a related tab in this document. Click on that tab to see when the feature was originally delivered Disabled, and when the Opt In will expire, potentially automatically enabling the feature. You can also click here to see features with Opt In Expirations across all Oracle Cloud Applications.
Feature Summary
Column Definitions:
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
Collaboration Messaging Framework
Exchange B2B Messages with Your Trading Partners Using GHX Marketplace
A new predefined service provider, GHX, is available for your electronic healthcare B2B messaging needs. If you subscribe to GHX’s services, you can connect to the GHX supply chain network and exchange B2B messages with your trading partners.
GHX's messages and endpoints are predefined, and a new simplified process is provided to streamline the B2B setup in the Collaboration Messaging work area.
Steps to Enable
At a high level, to set up the predefined GHX service provider:
- Configure GHX to exchange messages with your trading partners.
- Create trading partners.
- Associate the trading partners with your suppliers and select the documents you want to exchange.
These steps are detailed in the Configuring and Managing B2B Messaging for Oracle Fusion Cloud SCM guide.
Configure GHX to Exchange Messages with Your Trading Partners
- Select Manage Collaboration Messaging Service Providers from the Tasks panel tab, search for the GHX service provider, and select Actions > Edit.
The overview tab displays the following GHX details:
- Connection type that's configured.
- Check box to indicate whether credentials are configured.
- Number of trading partners configured for GHX.
- Number of trading partners with override message definitions.
- Number of suppliers set up with GHX as the service provider.
Service Provider Overview
- Select Actions > Manage Delivery Settings to configure the settings for outbound message delivery.
-
-
Select Test or Production from the Outbound Delivery Connection Type drop-down list to reflect the environment you're setting up.
-
Enter the username and password provided by GHX for sending messages to their network in the Service Provider User Name and Password fields.
-
You can modify the outbound purchase order message to email POs to suppliers conditionally, for example, bill-only orders. The email address for these POs is provided in the payload. You can enter an email address in the Recipient Email ID field to use if an email address isn't found in the payload.
-
If some POs are being emailed to a supplier who doesn’t accept specific file extensions as attachments, you can specify a File Extension. After the supplier receives the file, they can rename the extension.
-
By default, the file is zipped when a PO is being sent to a supplier by email. Select the Transmit the PO PDF as an unzipped file when it’s the only attachment check box if you want to send the PO as a PDF file when it's the only attachment.
-
Manage Delivery Settings
- Select the Outbound Message Setup tab to activate the outbound purchase order message, GHX-OAGIS-10.1-Purchase-Order-Collaboration-Message-Out.
The PO message will be sent as an XML message using the web service delivery method by default. Alternatively, you can conditionally send the PO as a PDF file via email to some suppliers by modifying the XSL associated with this message definition. For example, this can be done when sending bill-only orders.
Outbound Message Setup
- Select the Inbound Message Setup tab to activate the messages you plan to use. There are three messages available:
- GHX-OracleB2B-1.0-Purchase-Order-Acknowledgment-In-V2
- GHX-OAGIS-10.1-Invoice-Collaboration-Message-In
- GHX-OAGIS-10.1-Shipment-Collaboration-Message-In-V2
Inbound Message Setup
Create Trading Partners
After completing the service provider setup, create your trading partners.
- Select Manage B2B Trading Partners on the Tasks panel tab.
- On the Manage B2B Trading Partners page, select Actions > Create, and add your trading partners.
- Select GHX as the service provider.
Create a Trading Partner
Associate Trading Partners with Your Suppliers
Next, associate the trading partners with your suppliers and select the documents you plan to exchange.
- Select Manage Supplier B2B Configuration on the Tasks panel tab and search for your suppliers.
- Select a supplier and then select Edit Supplier B2B Configuration.
- On the Edit Supplier B2B Configuration page, select the Trading Partner Assignment tab and click Actions > Add Row to add a trading partner and the GHX service provider.
Supplier Trading Partner Assignment
- On the Edit Supplier B2B Configuration page, select the Document Setup tab and add the documents you want to exchange with the selected supplier.
Supplier Document Setup
Tips And Considerations
- If you want to conditionally send POs to suppliers, i.e., for bill-only orders, refer to the Configuring and Managing B2B Messaging for Oracle Fusion Cloud SCM guide for details about modifying the XSL.
- Make sure you provide the email address in the PO payload for sending orders by email. The Recipient Email ID XPath associated with the message definition for GHX-OAGIS-10.1-Purchase-Order-Collaboration-Message-Out determines its location within the payload.
Key Resources
- Refer to the Configuring and Managing B2B Messaging for Oracle Fusion Cloud SCM guide on the Oracle Help Center.
Access Requirements
Users who are assigned a configured job role that contains these privileges can access this feature:
- Manage B2B Supplier Trading Partners (CMK_B2B_SUPPLIER_TRADING_PARTNERS_PRIV)
- Manage B2B Trading Partners (CMK_B2B_TRADING_PARTNERS_PRIV)
- Manage Service Provider (CMK_MANAGE_SERVICE_PROVIDER_PRIV)
These privileges were available prior to this update.
Connect with Your Trading Partners using SPS Commerce Fulfillment for Oracle Cloud
A new predefined service provider, SPS Commerce, is available for your order-to-cash electronic messaging needs. If you subscribe to SPS Commerce services, you can connect with your trading partners and exchange messages using SPS Commerce fulfillment for Oracle Fusion Cloud.
SPS Commerce messages and endpoints are predefined, and a new simplified process is provided to streamline the B2B setup in the Collaboration Messaging work area.
Steps to Enable
At a high level, to set up the predefined SPS Commerce service provider:
- Configure SPS Commerce to exchange messages with your trading partners.
- Create trading partners.
- Associate the trading partners with your customers and select the documents you want to exchange.
These steps are detailed in the Configuring and Managing B2B Messaging for Oracle Fusion Cloud SCM guide.
Configure SPS Commerce to Exchange Messages with Your Trading Partners
- Select Manage Collaboration Messaging Service Providers from the Tasks panel tab, search for the SPS Commerce service provider, and select Actions > Edit.
The overview tab displays the following SPS Commerce details:
- Connection type that is configured, Test or Production.
- Check box to indicate whether credentials are configured.
- Number of trading partners configured for SPS Commerce.
- Number of trading partners with override message definitions.
- Number of customers set up with SPS Commerce as the service provider.
Service Provider Overview
- Select Actions > Manage Delivery Settings to configure the settings for outbound message delivery.
-
- Select Test or Production in the Outbound Delivery Connection Type drop-down list to reflect the environment you're setting up.
-
- Enter the username and password provided by SPS Commerce for sending messages to their network in the Service Provider User Name and Password fields.
Manage Delivery Settings
- Select the Outbound Message Setup tab to activate these outbound messages:
- Purchase Order Acknowledgment
- Advance Shipment Notice
- Invoice
Outbound Message Setup
- Select the Inbound Message Setup tab to activate the inbound PO.
Inbound Message Setup
Create Trading Partners
After completing the service provider setup, create your trading partners.
- Select Manage B2B Trading Partners on the Tasks panel tab.
- On the Manage B2B Trading Partners page, select Actions > Create, and add your trading partners.
- Select SPS Commerce as the service provider.
Create a Trading Partner
Associate Trading Partners with Your Customers
Next, associate the trading partners with your customers and select the documents you plan to exchange.
- Select Manage Customer B2B Configuration on the Tasks panel tab, and search for your customers.
- Select a customer and then select Edit Collaboration Configuration.
- On the Edit Customer B2B Configuration page in the Associated Service Providers section, select Actions > Add Row to add a trading partner and the SPS Commerce service provider.
- On the Collaboration Documents for Service Provider section, select Actions > Add Row. Add the following three inbound documents, and set their Association Status to Enabled.
- Purchase Order - Inbound
- Purchase Order Acknowledgment - Outbound
- Advance Ship Notice - Inbound
Customer B2B Collaboration
- To set up the outbound invoice for your customers, select Manage Customer Account B2B Configuration on the Tasks panel tab, then select Order to Cash from the Collaboration Business Process drop-down list and search for your customers.
- Select a customer and then select Edit Collaboration Configuration.
- On the Edit Customer Account B2B Configuration page in the Associated Service Providers section, select Actions > Add Row to add a trading partner and the SPS Commerce service provider.
- On the Collaboration Documents for Service Provider section, select Actions > Add Row. Add the outbound invoice document and set the Association Status to Enabled.
Customer Account B2B Collaboration
Key Resources
- Refer to the Configuring and Managing B2B Messaging for Oracle Fusion Cloud SCM guide on the Oracle Help Center.
Access Requirements
Users who are assigned a configured job role that contains these privileges can access this feature:
- Manage B2B Customer Trading Partners (CMK_B2B_CUSTOMER_TRADING_PARTNERS_PRIV)
- Manage Customer Account Collaboration Configuration (CMK_B2B_CUSTOMER_ACCOUNT_TRADING_PARTNERS_PRIV)
- Manage B2B Trading Partners (CMK_B2B_TRADING_PARTNERS_PRIV)
- Manage Service Provider (CMK_MANAGE_SERVICE_PROVIDER_PRIV)
These privileges were available prior to this update.
Support Additional Electronic Invoicing Requirements in the New UBL PEPPOL Invoice Message
A new version of the outbound invoice message definition for UBL-2.1-PEPPOL-Invoice-Out-V2 is available.
This message definition supports additional invoicing data items required for electronic invoicing in France. It includes payer details such as their address and contact information. It also includes order rounding amounts and ship-to addresses.
The details of the updated data mapping for this message are described in the Configuring and Managing B2B Messaging for Oracle Fusion Cloud SCM guide.
Steps to Enable
At a high level, to use this new message definition to send outbound invoices:
- Add the message definition as an outbound message to your trading partners.
- Associate your trading partners to your customer accounts and select the outbound invoice document.
Add the Message Definition as an Outbound Message to Your Trading Partners
- Select Manage B2B Trading Partners on the Tasks panel tab.
- On the Manage B2B Trading Partners page, search for and select your trading partner.
- Select Actions > Edit.
- On the Edit Trading Partners page, select the Outbound Collaboration Messages tab. Select Actions > Add Row.
- Select the UBL-2.1-PEPPOL-Invoice-Out-V2 message definition and set the Status to Active.
Add Outbound Message to Trading Partner
Associate Trading Partners to Customer Accounts
- To set up the outbound invoice for your customers, select Manage Customer Account B2B Configuration on the Tasks panel tab.
- Select Order to Cash from the Collaboration Business Process drop-down list and search for your customers.
- Select a customer and then select Edit Collaboration Configuration.
- On the Edit Customer Account B2B Configuration page in the Associated Service Providers section, select Actions > Add Row to add a trading partner.
- In the Collaboration Documents for Service Provider section, select Actions > Add Row.
- Add the outbound invoice document and set the Association Status to Enabled.
Customer Account Collaboration
Key Resources
- Refer to the Configuring and Managing B2B Messaging for Oracle Fusion Cloud SCM guide on the Oracle Help Center.
Access Requirements
Users who are assigned a configured job role that contains these privileges can access this feature:
- Manage Customer Account Collaboration Configuration (CMK_B2B_CUSTOMER_ACCOUNT_TRADING_PARTNERS_PRIV)
- Manage B2B Trading Partners (CMK_B2B_TRADING_PARTNERS_PRIV)
- Manage Service Provider (CMK_MANAGE_SERVICE_PROVIDER_PRIV)
These privileges were available prior to this update.
Financials Common
Common Financials
Service Excellence Continuing Investments
Our ongoing investment in service excellence has a focus on overall usability, resiliency, performance, and security. This work is based on monitoring performance trends, reviewing common use patterns, analyzing service requests, and participating in many discussions with customers.
In this update, our ongoing investment in service excellence includes improvements in the following areas.
Usability:
- Enhanced the AutoPost Journals process to post journal entries for all ledgers across all data access sets assigned to the user at the time of submission. This helps reduce the manual effort that was required to post all assigned journal entries. Previously the AutoPost Journals process only posted journal entries for ledgers in the assigned data access set belonging to the user's active session.
Steps to Enable
You don't need to do anything to enable this feature.
Approvals Work Area with Enhanced User Interface and Adaptive Search
Use the Approvals work area to review and take action on your approval tasks. The Approvals work area provides an enhanced user interface and adaptive search functionality where tasks can be filtered by approval type, task type, or sender, or be searched by keyword.
When enabled, the Approvals work area replaces the Worklist: Approvals and Notifications work area.
If the application is set up, you can click Navigator > Tools > Approvals to open it, instead of Navigator > Tools > Worklist to open the Worklist: Approvals and Notifications work area.
The Approvals work area has three views.
Approvals Tasks
The Approvals Tasks page shows a list of the tasks assigned to the current user, including business attributes related to the approval type. You can organize your work using supplied filters, search on keywords, and approve or reject approvals.
Supplied filters include:
- Task type, for example Approval, FYI, or Request
- Approval type, for example, expense reports
- From, or the person who sent the approval
You can also search by keywords on other attributes of the tasks. Any combination of search and filters can be bookmarked and shared.
You can quickly address your tasks without waiting for each to complete before moving to the next approval. Supported actions include:
- Approve
- Reject
- Dismiss (FYIs)
You can also comment on approval or rejection actions in a drawer if comments are set up as 'Required' in the task configuration in Business Process Management.
Quick View
Click a task in the list to open the Quick View, which displays additional information about the task and allows you to approve or reject it. You can click the arrow to navigate to the next task in the list.
To get more information or take an action that isn’t yet available in the Quick View, click View More Details to open the Analytics Publisher or Application Development Framework (ADF) notification.
Click the Approvals Tasks link to navigate back to the list.
Approvals Status and History
Click Approvals Status and History to view the current status and assignee for approvals that you’ve either submitted or been assigned as an approver.
Use the supplied filters and search by keyword to find historic approval information.
The Approvals work area is limited in functionality and isn’t a complete replacement for the Business Process Management (BPM) Worklist. For this reason, it’s available to set up at a site or user level.
The Approvals work area is designed and built with performance as a priority. The user experience is improved for both desktop and tablet or mobile users, making it easy to act quickly on approval tasks and notifications.
Steps to Enable
- Check that your environment is enabled for hybrid search. Refer to the 'Set Up the Approvals Work Area' topic in the Implementing Applications guide in Oracle Help Center for details.
- In the Scheduled Processes work area, run the Create Search Index for Worklist scheduled process once and ensure it has completed.
- In the Setup and Maintenance work area, go to the Manage Applications Core Administrator Profile Values task in the Application Extensions functional area. Set the Approval Requests UI Enabled (ORA_FND_APPROVALS) profile value depending on whether you want the Approvals work area to be available to all users or only some users.
Tips And Considerations
- The Approvals work area doesn’t replace the BPM worklist or change the behavior of the Notifications icon. You still click Show All from the notifications list in the global header, then click Worklist to open the BPM Worklist and use these tools with the application. Setting up the application doesn’t impact the BPM Worklist or Notifications icon and data remains consistent.
- The Tasks List view isn't currently configurable. It includes two attributes for each approval type, and additional attributes are shown in the Quick View.
- Users can only approve, reject or respond to request for information for the supported workflows in the Approvals work area. For all other actions, use the actions in the in-app notifications.
- As a new application, not all BPM Worklist use cases are yet supported. You can choose to set up the application at the site or user level. If you have some users who would benefit from this application, but want to keep others using the existing Worklist for all tasks, you can enable this feature for specific users by setting the profile option at the user level.
- Notifications for the following Financial workflows are available in the Approvals work area.
Product | Workflow |
---|---|
Payables | Invoice Approval |
Payables | Payment Approval |
Expenses | Expense Report Approval |
Expenses | Cash Advance Approval |
Expenses | Spend Authorization Approval |
General Ledger | Journal Approval |
Intercompany | Intercompany Transaction Approval |
- In addition to these, notifications for the following Financials workflows are also available in the Approvals work area. However, the requisite primary actions for such workflows are not yet supported in the Approval work area and thus, users should take action on such tasks using the in-app notifications. Click on View More Details in the Quick View page to open the in-app notification.
Product | Workflow |
---|---|
Payables | Invoice Account Coding Workflow |
Payables | Holds Resolution Workflow |
Intercompany | Intercompany Enter Receiver Distribution Workflow |
Key Resources
- Set Up the Approvals Work Area
- Use the Approvals Work Area to Manage Approvals
- Update Existing Setup Data
- Set Profile Option Values
Taxes
Embedded Tax Compliance Service for Avalara
Implement Avalara for tax partner processing in Oracle Tax with automated tax partner enablement.
Use the Manage Indirect Tax Automation with Avalara page to initiate Avalara enablement and track the status of each individual task.
The page displays three required tasks.
- Geography Content Import - Loads the geography data which is used for addresses and transaction tax calculations.
- Tax Content Import - Loads the regime-to-rate flow setup, configuration owner tax options and business unit subscriptions.
- Partner Tax Activation - Loads the application credentials and activates partner tax calculation for subledger transactions.
Oracle customers need real-time access to tax compliance solutions as part of their ERP. Oracle and Avalara have pre-wired and pre-configured the two systems to streamline and automate the integration between them and reduce ERP implementation efforts.
Steps to Enable
You don't need to do anything to enable this feature. However, you must complete some pre-requisite setups before you can initiate the enablement from the Manage Indirect Tax Automation with Avalara page.
- Complete the registration process with Avalara and get the login details.
- Create a new Oracle user and assign the Tax Administrator role to the user.
- Create a new custom role with Role Category of BI - Abstract Roles. Add the Manage Reports and Analytics privilege to the role and add the user created in the previous step to this role.
- Role Name – user defined value
- Role Code – user defined value
- Role Category – BI – Abstract Roles
- Description - user defined value
The user should now have both the roles assigned.
- Run the Retrieve Latest LDAP Changes process followed by Send Personal Data for Multiple Users to LDAP process.
You can use this user to initiate the enablement and provide the same user to Avalara on the Oracle Readiness for Avalara Enablement page. It is displayed once you initiate the enablement and login using your Avalara credentials.
Tips And Considerations
- The Oracle Fusion Cloud ERP customers who are also Avalara customers can take advantage of this automated enablement process.
- This automated enablement process is only available for pods without geography setup or Avalara tax content setup configured. You can't use this process if you already use Avalara for tax partner calculations.
- This automated enablement process is currently limited to business units and legal entities based in the United States and subject to United States taxes.
- The automated enablement process is only for initial configuration. For incremental updates, you should use your existing processes.
Access Requirements
You need to have a job role assigned that has the privilege Manage Tax Partner Configuration (ZX_MANAGE_PARTNER_CONFIGURATIONS_PRIV) to access the Manage Indirect Tax Automation with Avalara page. The Tax Administrator role has this privilege so you can access the page if you have this role assigned.
Accounting and Control
Budgetary Control
Budgetary Control for Project-Specific Procurement to an Inventory or Work Order Destination
Check for funds availability, reserve funds against control budgets, and account for encumbrances, if applicable, when procuring material to an inventory destination for sponsored or non-sponsored projects. This capability is also available when procuring material directly to a work order destination from a project-specific manufacturing or maintenance work order.
Project-specific requisitions created with an inventory or work order destination, as well as back-to-back requisitions, can have funds reserved as a commitment against the project or chart of account-based control budgets or both, when budgetary control is enabled for these transaction types. Funds reserved will include both the raw (requisition cost) and related burden costs.
Requisition for Inventory Destination with Project Details
When budgetary controlled validation is performed on purchase orders created independently or from such requisitions, funds are reserved as an obligation. Also, commitments for requisitions, if applicable, are liquidated. The funds status on the purchase order is updated throughout the procurement lifecycle, until the costs have been imported into Project Costing.
Purchase Order with Funds Status showing Partially Liquidated for a Partial PO Receipt imported into Project Costing
The inventory receipt and costing of items for such purchase orders are not budgetary controlled in Receipt Accounting or Cost Management. It is at the time of importing the purchase order related inventory costs from Supply Chain Cost Management into Project Costing that the purchase order obligation is liquidated, and the inventory costs reserved as project expenditures. This includes raw (inventory) costs and related burden costs. If the burden schedule associated with the project has been updated with new rates between purchase order creation and the import of inventory costs into Projects, then the revised burden rates will be used to reserve the funds. Project Costing will also liquidate the raw and burden costs originally reserved against the purchase order.
Use the Budgetary Control Analysis Report to view control budget balances for non-sponsored projects, and the Manage Awards page to view control budget balances for sponsored projects.
Budgetary Control Analysis Report Showing the Funds Reservation and Liquidation Happening at Requisition, Purchase Order and Project Costing
Payables invoices associated to project-specific purchase orders with inventory and work order destinations are not applicable for budgetary control validation. Invoice variances, if any, will be budgetary controlled by the Import Costs process in Project Costing when the acquisition adjustment costs are imported from Supply Chain Cost Management. Payables Invoices now display project attributes at the invoice line and distribution levels for invoices matched to project-specific purchase orders.
If encumbrance accounting is enabled for the relevant business function and transaction subtypes, then accounting and liquidation of the encumbered raw and burden costs is done when creating accounting for the requisition, purchase order, receipt accounting, and project costs.
Returns, cancellations, and other adjustments on project-specific purchase orders to an inventory or work order destination and back-to-back orders are budgetary controlled. Applicable encumbrances are also accounted.
Funds that the Project Costing subledger reserved at the time of importing purchase order costs from the Supply Chain Cost Management application might differ from the accounted encumbrances on the same transaction. This is because the Supply Chain Cost Management application could have imposed item cost overheads, resulting in additional costs to the originally encumbered purchase order costs. Funds reservation in Project Costing will be based on these actual costs received from the Supply Chain Cost Management application.
These are the business benefits of this feature:
- Efficient fund management and monitoring of budgetary controlled projects for project-specific procurement to an inventory or work order destination.
- Control your project budgets effectively for project-specific procurement to an inventory or work order destination.
- Improved review of payables invoices matched to project-specific purchase orders.
Steps to Enable
- Navigate to the Manage Budgetary Control task in the Functional Setup Manager. For your concerned ledger and business unit, edit the Budgetary Control and Encumbrance Accounting options. In the Edit Budgetary Control and Encumbrance Accounting page:
- Enable budgetary control for the ledger, business units assigned to the ledger, and the project accounting business function.
- Enable budgetary control and encumbrance accounting for these Requisitioning business function transaction subtypes:
- Project purchase requisition to inventory for project-referenced requisition with an inventory destination.
- Requisition back to back for back-to-back orders
- Project direct purchase work order for direct procurements made to a work order destination from a project-referenced manufacturing or maintenance work order.
Budgetary Control and Encumbrance Accounting Enablement for Business Function Requisitioning
- Enable budgetary control and encumbrance accounting for these Procurement business function transaction subtypes:
- Project purchase order to inventory for project-referenced purchase orders with an inventory destination.
- Project order back to back for back-to-back orders
- Project work order purchase order for direct procurements made to a work order destination from a project-referenced manufacturing or maintenance work order.
Budgetary Control and Encumbrance Accounting Enablement for Business Function Procurement
- This feature also makes available two new journal line rules for encumbrance accounting in Project Costing. 'Same Line Project Encumbered Burden Cost Liquidation for PO' for same line burdening enabled projects, and 'Separate Line Project Encumbered Burden Cost Liquidation for PO' for separate line burdening enabled projects. They are already available in the ‘Inventory Cost’ and ‘Burden Cost’ seeded journal entry rule sets.
New Project Costing Journal Entry Rules for Liquidation of Encumbered Burden Cost for Same Line Project
New Project Costing Journal Entry Rules for Liquidation of Encumbered Burden Cost for Separate Line Project
- If your ledger is assigned with a user-defined subledger accounting method, then add these new journal line rules to your rule sets and recompile your subledger accounting method for encumbrances to be accounted successfully for project-specific procurements to an inventory or work order destination.
Tips And Considerations
Budgetary Control:
- The new transaction subtypes that are introduced to support budgetary control and account encumbrances for a project-specific procurement to an inventory or a work order destination and back-to-back orders will be enabled by default for newly created business units and ledgers that are enabled for budgetary control. New business units and ledgers refers to those created on or after release 24A. The new transaction subtypes will remain disabled for existing business units and ledgers that are enabled for budgetary control. They will have to be manually enabled if you would like to have budgetary control and account encumbrances for project-specific procurement to an inventory or work order destination and back-to-back orders.
- To successfully budgetary control and account encumbrances for a project-specific procurement that involves use of both requisitions and purchase orders to an inventory or a work order destination and back-to-back orders, you must enable the new transaction subtypes for BOTH the Requisitioning and Procurement business functions. Failure to enable the new subtypes for both the business functions will result in funds being reserved or liquidated incorrectly.
Requisitions:
- Project-specific requisitions for inventory or work order destination as well as back-to-back requisitions created before enabling budgetary control or encumbrance accounting for requisition transaction subtypes, will remain as not applicable for budgetary control and encumbrance accounting. Once you enable the new transaction subtypes for the requisitioning business function, only new requisitions will be subject to budgetary control and encumbrance accounting.
Purchase Orders:
- Project-specific purchase orders for inventory or work order destination, as well as back-to-back purchase orders created before budgetary control is enabled for these transaction subtypes, will continue being excluded from budgetary control and encumbrance accounting throughout their fulfillment cycle. Once budgetary control for these transaction types is enabled for existing inventory or work order destination purchase orders, the changes listed below will trigger budgetary control and encumbrance accounting.
- Changes to account, project, or budget date
- Addition of new back-to-back or project-specific lines, schedules, or distributions
Receipt Accounting and Cost Management:
- Verify that the journal sources for cost accounting and receipt accounting are displayed in the Budgetary Control Journal Exceptions section, under the Ledger Options region in the Edit Budgetary Control and Encumbrance Accounting page. Add these sources if they have not been previously included.
Journal Source and Category Exceptions for Cost Accounting and Receipt Accounting
- The encumbrance liquidation of raw (purchase order) costs will be done by the Receipt Accounting subledger using the following transaction types:
Transaction Flow |
Transaction Type |
---|---|
Delivery of Receipt into Inventory |
Delivery to Inventory Destination |
Delivery of Receipt into Work Order |
Delivery to Work Order Destination |
Correction to Delivery Event |
Correction to Deliver for Inventory |
Correction to Deliver for Work Order |
|
Return to Receiving |
Return to Receiving for Inventory |
Return to Receiving for Work Order |
|
Price update on Inventory Purchase Order |
Cost Adjustment - PO Price Update for Inventory Destination |
Price update on Work Order Purchase Order |
Cost Adjustment - PO Price Update for Work Order Destination |
- Encumbrance liquidation of raw costs due to price update to a purchase order is done only for the un-invoiced receipt quantities in Receipt Accounting using the transaction types ‘Cost Adjustment - PO Price Update for Inventory Destination’ and ‘Cost Adjustment - PO Price Update for Work Order Destination.’
- To successfully reserve funds for invoice variance costs in projects for project-specific purchase orders to an inventory and work order destination, disable the profile option to Exclude Invoice Variances from Cost Management if enabled.
- For description-based purchase orders without item reference and to a work order destination, the encumbrance liquidation and budgetary check will be done directly in receipt accounting using the transaction type ‘Delivery to Expense’.
Projects:
- Project-specific purchase orders to an inventory or work order destination and back-to-back orders that were created prior to enabling the new transaction subtypes may exist. This can also include inventory receipts and returns. If these project costs are imported into the Project Costing subledger after enabling the new transaction subtypes, they will be subject to budgetary control in Project Costing. Funds reservation will happen in Project Costing for such scenarios irrespective of whether funds were originally reserved at the time of creating the purchase order or not. It is recommended you review and adjust your control budgets to allow for these reservations.
- Budgetary control, when enabled for this feature, is successful only for projects with project types that have not been enabled for exclusion from cost collection in the Manage Project Type Cost Exclusions task.
- The encumbrance liquidation of the purchase order raw costs will be done by Receipt Accounting and that of burden costs associated to the purchase order by Project Costing. It is recommended you run the relevant create distributions and accounting processes for each application without delay to ensure the encumbrances are accounted promptly.
Payables:
- Before this feature, for budgetary control enabled ledgers, Payables reserved funds for invoice price variances in the applicable control budgets when the invoice was matched to project-specific purchase orders to an inventory destination. With this feature, Payables will stop reserving funds for invoice price variances and the reservation will instead be done by Project Costing. It is recommended to review your existing user-defined business flows that could be impacted by this change.
- When invoice price variances exist for project-specific purchase orders to an Inventory and Work Order destination, the funds status for such distributions will show as not applicable. These distribution lines are also not subject to further funds reservation at General Ledger.
Budgetary Control Status of Invoice Price Variance in Payables
- Before this feature, for capital projects or construction-in-process (CIP) projects, there was a possibility of capitalization or asset lines being created twice, once in Payables and again in Projects, if the accrual account is also an asset clearing account. With the project details being captured at Payables, this will no longer occur. It is recommended to review your existing user-defined business flows, if any, that could be impacted due to this change.
- View and report project details on payables invoice lines and distributions, available in the OTBI Subject Area: “Payables Invoices — Transactions Real Time”.
Other:
- Budgetary control for purchase orders related to outside processing services or contract manufacturing is not supported at this time.
- Budgetary control and encumbrance accounting is not supported for project-specific internal material transfer requisitions to an inventory destination.
Key Resources
For more information on budgetary control and encumbrance accounting, refer to the following topics:
- Overview of Budgetary Control and Encumbrance Accounting in the Using Financials for the Public Sector manual in the Financials Cloud Applications documentation.
- Overview of Project-Driven Supply Chain topic in the Using Project Costing manual.
- Budgetary Control topic in the Defining and Managing Financial Projects manual.
- Direct Procurement of Materials for Work Orders topic under Manage Production in the Using Manufacturing manual.
Access Requirements
No new access requirements.
Maintenance of Public Budget Account Groups 
Provide budget managers update access in the Budget Monitor to all public budget account groups that belong to their control budgets. This allows both budget managers and budget account group owners to manage monitored budget accounts.
In the Budget Monitor region of the Budgetary Control Dashboard, open the Manage Budget Account Group page. Use this page to update, delete, or change the owner of public budget account groups of the control budgets that you manage.
Budget Account Group with Public Access
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- To edit, delete, or change the owner, you must be the budget manager of the control budget.
- To set the budget account group to private, assign yourself as the owner to enable the Access field.
Budget Account Group with Private Access
Key Resources
- Budget Monitor in Using Financials for the Public Sector
-
This feature originated from the Idea Labs on Oracle Customer Connect: Add Back the Edit/Delete Options for Budget Account Groups
Access Requirements
No new access requirements.
General Ledger
Journal Attachments Audit to Monitor and Adhere to Compliance Policies
Enable the audit of insert/check in, delete, update and download activities by users on journal attachment files. This provides accounting managers with ability to track and assess attachment activity for both subledger and general ledger journals.
Business benefits include:
- Increased level of governance and security when carrying out audit processes.
- Improved visibility and insight into General Ledger and Subledger Accounting journals.
Steps to Enable
To enable this feature:
- Navigate to the Manage Audit Policies page, select Configure Business Object Attributes and choose the General Ledger or Subledger Accounting product.
- For the General Ledger product, click the Journals drop down and select the Journal Header Attachments or Journal Batch Attachments check box.
- For the Subledger Accounting product, click the Subledger Journals drop down and select the Subledger Journal Attachments check box.
Tips And Considerations
- Attachments audit is only available for General Ledger and Subledger Accounting journal attachments added from the UI.
- View audit history of attachments on the Audit Reports ---> View Audit History page.
Key Resources
Access Requirements
To use this feature, you need these privileges:
- Privilege Name and Code:
- Manage Audit Policies (FND_MANAGE_AUDIT_POLICIES_PRIV)
- Privilege Name and Code:
- View Audit History (FND_VIEW_AUDIT_HISTORY_PRIV)
Legal Entity-Specific Secondary Ledgers with Controlled Replication from Primary Ledgers
Assign a secondary ledger only a subset of the primary balancing segment values that are assigned to the primary ledger and its legal entities. This effectively enables organizations to populate secondary ledgers for specific legal entities when the primary ledger represents multiple legal entities or countries.
Organizations use secondary ledgers when they require an alternative accounting representation for the legal entities represented in the primary ledger. All accounting entries in the primary ledger are typically propagated to a secondary ledger, except for adjustment-only secondary ledgers. This feature allows a journal-level or subledger-level secondary ledger to now include only a partial accounting representation of the primary ledger. Administrators can choose to assign only a subset of the primary balancing segment values that are assigned to the primary ledger and its legal entities, to a journal-level or subledger-level secondary ledger.
Journal-Level Secondary Ledgers
When journal entries are entered in the primary ledger, the accounting processes propagate to each journal-level secondary ledger only those journal lines with the primary balancing segment values assigned to the secondary ledger.
Subledger-Level Secondary Ledgers
- When journal entries are created manually or through a spreadsheet or through file-based data import in the primary ledger, the accounting processes propagate to each subledger-level secondary ledger only those journal lines with the primary balancing segment values assigned to the secondary ledger.
- When the journals are created in the primary ledger from subledger sources, the accounting processes propagate to each subledger-level secondary ledger the journal lines based on the subledger accounting rules, but not according to the primary balancing segment conversion rules. Therefore, administrators must configure mapping sets and/or additional journal rules conditions in the Subledger Accounting application to replicate, partially based on specific primary balancing segment values.
This implementation is useful for companies in Financial Services or other service industries that have (1) operations in multiple countries that share a single ledger currency and can be included in the same primary ledger, and (2) have light regulatory requirements that can be met through General Ledger reporting in the journal-level secondary ledger. Legal entity-specific secondary ledgers may not support full compliance with local regulations in highly regulated countries. Carefully review your reporting obligations and review the Cloud ERP Enterprise Structures White Paper (Doc ID 2415848.1) for a complete list of considerations before adopting this implementation.
You can navigate to the Map Primary to Secondary Ledger page to define the mapping and the conversion rules between primary and secondary ledgers. For the Journal and Subledger-level data conversion level mapping, you can now define primary balancing segment value conversion rules.
Here are the steps to define primary balancing segment value conversion rules.
- Navigate to the Map Primary to Secondary Ledger page and enable the checkbox Replicate journals by primary balancing segment values in the Primary Balancing Segment Value Conversion Rules section.
- You can enter the child and parent primary balancing segment values by selecting the value type as Single Value and Parent Value. The Primary Balancing Segment Value field will show all the child values or parent values applicable to the value type. If you would like to define the primary balancing segment values based on parent values, then you must select a tree code and version.
Primary Balancing Segment Value Conversion Rules
- You can search the primary balancing segment values based on the value, description or legal entity.
The replication of journals by primary balancing segment values can be enabled for new or existing secondary ledgers.
- The primary ledger posting process will stop the replication of all journals into the associated journal-level secondary ledgers that are enabled for replication by primary balancing segment values. The journals created in the primary ledgers are replicated to these secondary ledgers by running a new process, Replicate Journals by Primary Balancing Segment Values.
- For subledger-level secondary ledgers, the primary ledger posting process will stop the replication of journals created manually, through a spreadsheet, or through file-based data import, into the associated subledger-level secondary ledgers that are enabled for replication by primary balancing segment values. These journals are replicated into the subledger-level secondary ledgers by running a new process, Replicate Journals by Primary Balancing Segment Values.
- For subledger-level secondary ledgers, when journals are created in the primary ledger from subledger sources, the Create Accounting process will replicate partial accounting from the primary ledger to the subledger-level secondary if mapping sets and/or additional journal rules conditions are configured in the Subledger Accounting application to replicate partially based on the primary balancing segment values.
Business benefits include:
- Simplifies inquiry and reporting in a secondary ledger when it only contains data for the relevant legal entity.
- Improves operational efficiency of the Create Accounting and Post Journals processes when fewer journals are propagated to each secondary ledger.
Steps to Enable
- To enable the feature, you must enable the lookup code GL_35799450.
- Navigate to the Manage Standard Lookups task and search for the ORA_ERP_CONTROLLED_CONFIG lookup type. In the Lookup Codes section, add the lookup code GL_35799450 and select the Enabled check box. Enter the applicable start date and save.
Tips And Considerations
- This feature allows you to set up the controlled replication for secondary ledgers associated with primary ledgers for Journal and Subledger data conversion levels. For subledger-level secondary ledgers, administrators must configure mapping sets in the Subledger Accounting application to replicate partial accounting from the primary ledger to the secondary ledger for journals created from subledger sources.
- If you change a tree code or version after defining the primary balancing segment value conversion rules, a warning message will indicate that invalid values will be deleted for the new tree code and version. Though the application allows you to change the tree code and version at any time, it is recommended that you use a specific tree code for the replication by primary balancing segment values to address the reporting requirements.
Key Resources
- Refer to the following topics in the Implementing Enterprise Structures and General Ledger guide on the Oracle Help Center:
- For further details about common Oracle Fusion Cloud ERP enterprise structures, how they relate to each other, and best practice recommendations, review the Cloud ERP Enterprise Structures White Paper (Doc ID 2415848.1).
- For further details on how to configure mapping sets and/or additional journal rules conditions, review the Mapping Sets topic in the Implementing Subledger Accounting guide on the Oracle Help Center.
Access Requirements
No new privileges are required to access the Primary Balancing Segment Value Conversion Rules section on the Map Primary to Secondary Ledger page. Users with the Post Journal (GL_POST_JOURNAL_PRIV) privilege can run the Replicate Journals by Primary Balancing Segment Values process.
Opening Balance Initialization for New Reporting Currencies and Secondary Ledgers 
Generate journals to initialize the opening balances for a new reporting currency or secondary ledger created for a primary ledger or secondary ledger already in operation. For example, an organization may need to add a new reporting currency or secondary ledger to an existing primary ledger when it merges or acquires a new business, undergoes a change in its fiscal year, expands to new countries of operation, or when a country where it operates introduces a new currency. This feature automatically generates journals based on the primary ledger’s account balances to record the opening balances for actual, average and encumbrance balances for the first accounting period of the new reporting currency or secondary ledger. The reporting currency or secondary ledger can be journal-level or subledger-level. This feature also applies to journal-level reporting currency ledgers associated with secondary ledgers.
Steps for balance initialization:
- Enable balance initialization for the target ledger (secondary ledger or reporting currency) by selecting the pre-populated balance initialization period during the setup of the new secondary ledger or reporting currency.
Select the pre-populated Balance Initialization Period along with the Conversion Date and Conversion Rate Type for determining the rates to initialize the balances from the source ledger to the target ledger.
- Ensure that the user has write access to the target ledger (secondary ledger or reporting currency). Also, ensure that the accounting period prior to the initialization period is in an open status in the target ledger.
- Initialize balances by running the Create Opening Balance Journals in Reporting Currency or Secondary Ledger process.
- Specify the source and target ledger.
- Optionally enable the Create Journal Batches by Primary Balancing Segment Values check box.
- Also, optionally specify the account filter to restrict the range of accounts for balance initialization.
- Once the process is successfully complete, you can review the generated journals from the Manage Journals page and post them to initialize the balances in the target ledger.
Business benefit:
- Reduces the need to manually create journals to record the initial balances for a new reporting currency or secondary ledger.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Special considerations may apply if you have Lease Accounting, Fixed Assets, or Cost Accounting subledgers, or if Budgetary Control is enabled. Refer to the Implementing Enterprise Structures for General Ledger guide for details.
Key Resources
- Refer to the Ledgers chapter in the Implementing Enterprise Structures and General Ledger guide on the Oracle Help Center.
Access Requirements
To submit the Create Opening Balance Journals in Reporting Currency or Secondary Ledger process, you need the existing privilege Run Create Opening Balance Journals in Reporting Currency Program (GL_RUN_CREATE_OPENING_BALANCE_JOURNALS_IN_REPORTING_CURRENCY_PROGRAM_PRIV).
Joint Venture Management
Data Security for Joint Venture Management
Release 24A is the final release in which data security setup is optional for Joint Venture Management.
Business Impact:
Starting with release 24B data security for joint venture management is no longer optional for Joint Venture Management and will be auto enabled.
You must set up your users with data security if you haven’t already done so. After this release, if you haven’t set up Joint Venture Management users with data security, they won't be able to access, set up, and process Joint Venture Management objects and data.
Steps to Enable
Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.
Offering: Financials No Longer Optional From: Update 24B
- Associate business units to users using the security console.
- Associate a business unit to joint venture definitions when setting up the joint ventures.
Key Resources
- For more information, refer to
- Implementing Joint Venture Management guide and
- Using Joint Venture Management guide.
Access Requirements
- Joint Venture Application Administrator
- Joint Venture Accountant
- Joint Venture Accounting Manager
Descriptive Flexfields for Joint Venture Operational Measures
Manage descriptive flexfields for Joint Venture Operational Measures within the provided application.
Business Benefit:
Easily capture and manage additional attributes as descriptive flexfields for operational measures, eliminating the need to create custom processes to manage them.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- For more information, refer to
- Implementing Joint Venture Management guide and
- Using Joint Venture Management guide.
Access Requirements
- Joint Venture Application Administrator
- Joint Venture Accountant
- Joint Venture Accounting Manager
Fixed Amount Overhead Method Type
Use the Fixed Amount Overhead Method to enable managing partners to charge the joint venture partners a fixed amount for overhead.
Business Benefit:
This provides an additional method for the managing partner to recover costs associated with managing the joint venture and to help ensure compliance with the joint operating agreement.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Release 24A is the final release in which Joint Venture Overhead setup and processing is made available to users through an opt-in. After this release, Joint Venture Management users will automatically have access to these capabilities and can choose to use them according to your business practices.
Key Resources
-
Watch Joint Venture Overhead Readiness training.
- For more information, refer to
- Implementing Joint Venture Management guide and
- Using Joint Venture Management guide.
Access Requirements
- Joint Venture Application Administrator
- Joint Venture Accountant
- Joint Venture Accounting Manager
Joint Venture Partner Contribution Transfer
Transfer the remaining balance of a joint venture partner contribution to another partner contribution or use the remaining balance to create a new partner contribution.
Business Benefit:
Managing partner contribution transfers through the Joint Venture Management processes eliminate errors associated with manual processing, increasing joint venture accountant productivity.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
-
Watch Joint Venture Partner Contribution Transfer demo.
- For more information, refer to
- Implementing Joint Venture Management guide and
- Using Joint Venture Management guide.
Access Requirements
- Joint Venture Application Administrator
- Joint Venture Accountant
- Joint Venture Accounting Manager
Obsolete Profile Option for Descriptive Flexfields Enablement in Joint Venture Management
From 24A, you don't need to set up the ORA_JV_ENABLE_DFF_DISPLAY profile option to enable the use of descriptive flexfields in Joint Venture Management.
Business benefit:
Reduced steps to configure descriptive flexfields for Joint Venture Management.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- For more information, refer to
- Implementing Joint Venture Management guide and
- Using Joint Venture Management guide.
Access Requirements
- Joint Venture Application Administrator
- Joint Venture Accountant
- Joint Venture Accounting Manager
Period Processing for Identify Joint Venture Transactions Process
The Identify Joint Venture Transactions process now selects transactions from General Ledger and Subledger Accounting by default for the earliest open accounting period.
Business Benefit:
This lets managing partners generate joint venture billings for the accounting period that is being closed.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Prior to this change, the Identify Joint Venture Transactions process selected transactions from General Ledger and Subledger Accounting by default for the latest open accounting period.
Key Resources
- For more information, refer to
- Implementing Joint Venture Management guide and
- Using Joint Venture Management guide.
Access Requirements
- Joint Venture Application Administrator
- Joint Venture Accountant
- Joint Venture Accounting Manager
Joint Venture Overhead
Joint venture overhead provides the ability to:
- Create user-defined rules to calculate overhead charges or management fees for managing partners of a joint venture to recover costs associated with managing the joint venture.
- Process the calculated overhead as cost recovery or as revenue to the managing partner.
- Define periodic adjustment factors to adjust overhead method percentages and rates on a periodic basis.
Enables the managing partner to:
- Conform to the joint operating agreement by ensuring accurate calculation and distribution of overhead and management fees to be billed to the joint venture partners.
- Minimize month-end processing and reduce potential errors caused by manual entry through the use of automated processes.
Steps to Enable
Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.
Offering: Financials No Longer Optional From: Update 24B
Tips And Considerations
Starting with release 24B joint venture overhead is no longer optional for Joint Venture Management and will be auto enabled.
Key Resources
- For more information, refer to
- Implementing Joint Venture Management guide and
- Using Joint Venture Management guide.
-
Watch Joint Venture Overhead Readiness Training.
Access Requirements
- Joint Venture Application Administrator
- Joint Venture Accountant
- Joint Venture Accounting Manager
Subledger Accounting
Improvements to Transfer of Subledger Accounting Entries to General Ledger
Transfer subledger accounting entries directly to General Ledger without running the Post Subledger Journal Entries and Journal Import processes.
After the Create Accounting sub-process generates the subledger accounting entries, these entries are summarized and transferred to general ledger through the “Post Subledger Journal Entries” parent process and its child “Journal Import” process.
When you submit the Create Accounting process with the Transfer to General Ledger parameter set to Yes, the Create Accounting sub-process summarizes and transfers the subledger accounting entries to General Ledger without launching the Post Subledger Journal Entries and Journal Import processes. If you submit the standalone Post Subledger Journal Entries process, the subledger accounting entries are transferred to General Ledger without launching the Journal Import process.
Other changes included in this feature:
- If the subledger accounting entry references an invalid account that has an alternate account defined, the alternate account is automatically used while creating the General Ledger journals.
- If there are validation errors during General Ledger journal batch creation from subledger accounting entries, the valid accounting entries are transferred to General Ledger and the invalid accounting entries are not transferred.
- You can review validation errors generated during the transfer of subledger accounting entries to General Ledger in the Manage Accounting Errors page.
Business benefits include faster overall processing during accounting and posting of journals with efficient use of system resources.
Steps to Enable
Use the following steps to enable the Improvements to Transfer of Subledger Accounting Entries to General Ledger feature for all Subledger and Accounting Hub applications -
- Navigate to Setup and Maintenance.
- Select the Setup Offering: Fusion Accounting Hub.
- Click on the Functional Area: Accounting Transformation.
- Click on the Setup Task: Manage Subledger Accounting Lookups.
- Search the Lookup Type: ORA_XLA_PROMOTIONAL_OPTIONS.
- Define the following Lookup Code under above Lookup Type -
- Lookup Code: XLA_PROMO_31776850_ON
- Reference Data Set: Common Set
- Enabled: <Checked>
- Meaning: Skip Post Subledger Journal Entries and Journal Import
- Save the changes.
Tips And Considerations
- This feature does not apply under any of the following conditions:
- Online Accounting is submitted from the Transaction pages.
- The Multiperiod Accounting process is submitted does not skip the Post Subledger Journal Entries process but does skip the Journal Import process.
- Subledger accounting transfers outside of Fusion General Ledger, such as EBS General Ledger and PeopleSoft General Ledger.
-
If the "Improvements to Transfer of Subledger Accounting Entries to General Ledger" feature is enabled and Transfer to General Ledger is set to "Yes" during submission of the Create Accounting process, the Processing Unit Size specified in the "Create Accounting Processing Options" section of the Subledger Accounting System Options page is used to transfer journals to General Ledger.
NOTE: This may affect the number of journal batches that are generated when the feature is enabled. For example: if the Create Accounting Processing Unit Size is set to 1000 and the General Ledger Transfer Processing Unit Size is set to 2000, when the feature is enabled it may result in 2X number of journal batches when there are more than 2000 events in a batch.
-
If the "Improvements to Transfer of Subledger Accounting Entries to General Ledger" feature is enabled and the Post Subledger Journal Entries process is used to transfer journals to General Ledger, the Processing Unit Size specified in the "Transfer to General Ledger Processing Options" section of the Subledger Accounting System Options page is used.
Payables and Expenses
Expenses
Audit Evaluation of Resubmitted Expense Reports for Potential Duplicates 
Evaluate resubmitted expense reports using audit rules to identify potential duplicates. This helps auditors identify potential duplicate expenses added to the resubmitted expense report.
When an employee submits an expense report, Expenses identifies duplicate expenses both in the existing report and in expense reports previously submitted by the employee. The Expense Item Audit Reason Details page displays for auditors any duplicate expenses during the expense report audit.
If the employee withdraws and resubmits the expense report, new potential duplicate expenses may emerge in the report due to the addition of new expense items in the current report or new expense items to other reports. This feature now evaluates all resubmitted expense reports for duplicate expenses.
The Business benefits of this feature includes:
- Provides auditors with the most current list of potential duplicate expenses.
- Streamlines the overall audit process.
- Reduces the risk of non-compliance.
- Reduces potential overpayments.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- Detailed View of Audit Results in Expense Audit
- This feature originated from the Idea Labs on Oracle Customer Connect: Idea 658823
Payables
Assignment of Exception Categories to Payables Exceptions
Generate the Payables Exception Report to view the invoice exceptions grouped by the exception categories. You can use the report to delegate specific exceptions to resources for reviewing and resolving them.
The report lists all exceptions of type Holds, Import Rejections, and Approval Rejections. They are assigned exception categories based on the action required to resolve them. So, you can use the categorization to quickly determine the type of action for resolving the exception.
Exception Categories
The following categories are supported.
- Business Rule: Exceptions that are placed due to organization policies. For example, matching holds like billed quantity exceeding ordered quantity over the defined tolerance.
- Configuration: Exceptions that are placed due to inactive or missing setups.
- Tax Calculation: Exceptions encountered during the tax calculation process.
- Transaction: Exceptions that are placed due to incorrect, incomplete or missing data on the transaction. For example, line variance hold placed on invoice when header amount doesn't match the total of invoice line amount, invalid supplier site used during importing an invoice, and so on.
Generate the report by running the task Run Payables Exception Listing from the Tasks pane on the Invoices landing page. You will receive the report through in-app notification. While submitting the request to generate the report, you can opt to be notified by an email. The exception listing request supports following parameters.
- Exception Type: Type of exception like Holds, Approval Rejections, Import Rejections
- Ledger
- Business Unit
- Source
- Supplier
- Exception Category
- Notify: User who should be notified with the report output.
Sample Report Output
The business benefits include
- Increases efficiency by streamlining exception assignment for user action.
- Improves decision-making for Payables Managers in resource allocation.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Access Requirements
Users who are assigned these Payables privileges can access this feature.
- Validate Payables Invoice
- Import Payables Invoice
Campaign Enhancements for Dynamic Discounting
Select suppliers for a dynamic discounting campaign based on payment terms, payment method, and payment currency. In order to maximize the effectiveness of the campaign, enable the campaign manager to select suppliers according to these criteria: suppliers with longer payment terms; suppliers who receive payments electronically; and currencies where the buyer has surplus cash.
Buying organizations can earn additional return on surplus funds by applying a discount dynamically over the length of the payment terms. The earlier the invoice is paid, the larger the discount received. The campaign manager can select suppliers for a dynamic discounting campaign based on the payment terms, payment method, and payment currency. This helps the campaign manager to tailor the dynamic discounting campaign to their target suppliers.
For example, the campaign manager can select suppliers with longer payment terms as they are more likely to accept dynamic discounting offers. They can also create multiple campaigns with different APR according to the range of payment terms. If the buyer has surplus cash in a specific currency, such as US Dollars, they can select only the suppliers who receive payments in US Dollars.
Business benefits include:
- Improved effectiveness of dynamic discounting campaign by targeting suppliers who are more likely to accept offer.
- Improved usability in building campaigns.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
IDR Language Support for Danish, Turkish, and French 
Enable invoice document recognition for all invoice header and invoice line attributes in Danish and Turkish, and improve the quality of invoice document recognition in French. IDR now supports 14 languages.
Business benefit includes:
- Improves user satisfaction for customers who primarily use Danish, Turkish or French as their business language.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- For more details, refer to:
- Recognized Attributes and Languages in Help Center
- Idea Lab 587002: IDR Languages Required for Business
IDR Supplier Derivation in Email Subject
Derive the supplier on incoming invoices from the supplier number prefix in the email subject line using IDR. Suppliers derived in this way take precedence over the standard IDR supplier detection.
You can now easily improve the supplier recognition accuracy on non-PO invoices by instructing your suppliers to insert a valid Supplier Number within parentheses as a prefix in the email subject line.
Business benefit:
Increase efficiency by improving the supplier recognition accuracy.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Identifying Valid Supplier Numbers
- Navigate to Procurement > Suppliers.
- In the Tasks panel tab, click Manage Suppliers.
- Search for the supplier by name in the Keywords field.
You can locate the supplier number in the search results.
Manage Suppliers screen
Format for Adding a Supplier Number in the Email Subject Line
- You must enclose the supplier number in parentheses.
- Enter the supplier number as a prefix of the email subject. It must come before the subject line.
NOTE: IDR automatically ignores standard Forward and Reply prefixes like "Fw:" and "Re:"
For more information, refer to the Scan Invoices Using IDR section in Using Payables Invoice to Pay on Oracle Help Center.
Order of Precedence for Supplier Detection in IDR
- PO Number: IDR derives the supplier from the PO number detected on the invoice.
- Supplier Number in Email Subject: IDR detects a valid supplier number in the email subject.
- Supplier Detection: IDR matches supplier name, address, and other identifying information to detect the supplier.
Key Resources
Performance Improvements to the Payables Holds Infotile
Receive invoice hold information more quickly with performance improvements to the Holds infotile in the Invoice landing page.
You can configure the Holds infotile to show the count of invoices on hold for over 7 days (default view), 15 days, 30 days, or all days.
Business benefits include:
- Reduces the time to identify and resolve holds on your supplier invoices, which ultimately allows timely payment and reduces the risk of unnecessary disputes.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Payments
Employee Bank Account Creation Using a Unique Bank Identifier
Search for a bank using a unique bank branch identifier to create employee bank accounts. This lets your employees and external parties create bank accounts without knowing the bank and branch details.
Business benefits include:
- Increase productivity by saving time spent on finding out bank and branch details.
- Improved employee satisfaction by eliminating the need for remembering the bank and branch details during account creation.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- A new checkbox is included to search the bank and bank branch using the branch identifier. The branch identifier label is displayed as per the value available in CE_CTRY_SPECIFIC_UI_RULES.
- This check box is displayed only when the profile option 'CE_USE_EXISTING_BANK_BRANCH' is set to 'Yes'.
- In the countries where the bank branch number is displayed and mandatory, this check box is checked and the default search will be based on the bank branch identifier.
- For other countries, this checkbox is unchecked and the default search will be based on bank and branch.
- The same behavior applies to both self-service and admin UIs.
Receivables and Cash
Receivables
Bulk Upload of Alternate Name Mapping Rules for Japan Bank Accounts
Use the Zengin Format for Japan REST API to upload alternate payer name mapping rules for Japanese customer bank accounts in bulk. The alternate payer name mapping rules identify Japanese customers during Zengin lockbox processing. The upload process verifies and updates existing rules, creates new rules, and deletes obsolete.
Japan Bank Association provides the mapping of customer account to the alternate name that needs to be synced up in Manage Alternate Name Mapping Rules Setup in Receivables.
Business benefits:
- Reduces the need for manual review, update and delete of alternate payer name mapping rules.
- Helps create a regular schedule for maintaining alternate payer name mapping rules for Japanese customer bank accounts.
Steps to Enable
Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > APIs & Schema). If you are new to Oracle's REST services you may want to begin with the Quick Start section.
Access Requirements
No additional access requirements are needed to use this feature.
Electronic Invoicing Enrichment for Legislative Updates
Enhance the Receivables XML invoice extract to include additional data elements as required by the mandates in several countries. This reduces the need for implementation specific changes.
Electronic invoicing streamlines financial transactions and provides more accurate and transparent data to businesses and tax authorities, contributing to better government compliance. Many countries are mandating electronic invoices in the next couple of years. The electronic invoicing extract needs enriching to support these additional country requirements.
The Receivables XML invoice extract and the UBL 2.1 message contain additional data elements. The Receivables XML invoice transformed message includes additional data and all can be used for the mapping to UBL 2.1 e-invoicing messages.
Available data elements in the Receivables XML Original Message include:
1.Header
- Transaction Source - Transaction / General Information / Transaction Source
- Accounting Date – Transaction / General Information / Accounting Date
- Notes - Transaction / General Information / Notes (see setup and max 4000 bytes). The private Notes are not extracted.
- FOB - Transaction / General Information / Edit Freight / FOB
- Exempt from late charges - Transaction / General Information / Payment Check box / Exempt from late charges
- Default Tax Exemption Handling - Transaction / General Information / Miscellaneous - Default Tax Exemption Handling code and Description
- Print Date - Transaction / General Information / Miscellaneous / Print Date. Note: The date when the XML was generated.
- Attachment Title and Description - Transaction / Attachments / Title and Description
- Payment Status – Not Paid, Paid, Partially paid
- Product Type – Concatenated Product Type values from transaction lines
- Internal Notes from Projects
2. Line details
- Channel - Transaction / Line / Sales Order / Channel
- Exemption Handling - Transaction / Line / Tax Exemption / Exemption Handling - Exemption Handling Code and Description
- Certificate Number - Transaction / Line / Tax Exemption / Certificate Number
- Sales Order - Transaction / Line / Number, Line, Channel, Date
- Ship-to - Transaction / Line / Ship-to Customer – Name, Address Line 1-4, City, County, State, Province, Postal Code, Country
3. Tax lines details
- Tax Status Code - Transaction / Line / Detail Tax Line / Tax Status - Tax Status Name and Tax Status Code
- Legal justification message when the setup is on tax rule level.
4. Memo lines details
- Memo lines Global Descriptive Flexfields
5. Bill To Customer details
- Translated Customer Name for Bill to Customer - Customer / Site Details / Account Address Details / Translated Customer Name
- SIRET Number - Customer / Site / Profile History / Site Profile / Additional Information / Regional Information – Customer Profiles for France / SIRET Number
- Routing Code - Customer / Site / Profile History / Site Profile / Additional Information / Regional Information – Customer Profiles for France / Routing Code
- Tax Registration Status for TRN defined on Transaction Header - Customer / Site /Tax Profile / Tax Registration / Create Tax Registration / Tax Registration Status
6. Ship To Customer details
- Party Site Descriptive Flexfields
- Concatenate Party Site Purpose
7. Paying Customer details
- Paying Customer Name – Transaction / Customer / Paying Customer / Name
- Descriptive Flexfields - Customer / Site / Profile History / Site Profile / Additional Information / Context Value / Descriptive Flexfields
- Global Descriptive Flexfields - Customer / Site / Profile History / Site Profile / Additional Information / Regional Information – Customer Profiles for France / SIREN Number and Routing Code
- Customer Account Site Information Descriptive Flexfields - Customer / Site / Site Details / Enter Customer Account Site information / Descriptive Flexfields
- Address details - Address Line 1-4, City, County, State, Province, Postal Code, Country
- Tax Registration Number - Customer / Site / Tax Profile / Tax Registration / Edit Tax Registration / Registration Number and Tax Regime Name. The Tax Registration Number is extracted based on following rules:
- One Tax Registration Number for a Customer Site is defined, exposed is this Tax Registration Number.
- Multiple Tax Registration Numbers for a Customer Site are defined, and default Tax Registration Numbers is defined, exposed is default Tax Registration Numbers.
- Multiple Tax Registration Numbers for a Customer Site are defined, and default Tax Registration Numbers is not defined, no value is exposed.
- Account and Site Primary Contacts – Land Phone, Email and Contact Name
8. Legal Entity details
- Place of Registration – Manage Legal Entity Registration / Place of Registration
9. Legal Reporting Unit Registration details
- Registered Name – Manage Legal Reporting Unit Registration / Registered Name
- Alternate Name – Manage Legal Reporting Unit Registration / Alternate Name
- Registration Number – Manage Legal Reporting Unit Registration / Registration Number
10. Bank Account details
- Description - Manage Bank Accounts / Description
- Account Type, Deposit Type - Manage Bank Accounts / Account Type or Deposit Type
11. Bank Account assigned Legal Entity details
- Legal Entity Name - Manage Bank Accounts / Legal Entity Name
- Legal Entity address details - Address Line 1-4, City, County, State, Province, Postal Code, Country
- Legal Entity primary Contact Name, Land Phone, Email
- Legal Entity Registration Number and Code
- Legal Reporting Unit Registration Number and Code
12. Payment Card details
- Credit Card – Transaction / Payment / Payment Details / Credit Card. Masked Credit Card number.
- Name on Card - Transaction / Payment / Payment Details / Name on Card
13. Reference to a previous invoice details
- Previous Invoice Type
- ID of previous invoice
- Number of previous invoice line
- Date of previous invoice
New elements in the UBL2.1 Transformed Message for Legal Entities with Country Code France:
Attribute Name |
UBL Element Path |
XML Path |
|
---|---|---|---|
1 | Business process type |
/cbc:ProfileID |
PaymentStatus and ProductTypeValues - B-Goods, S-Service, 1 -Not paid, 2 - Fully or Partially paid |
2 | Buyer’s identifier (SIRET) |
/cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID |
TransferDocBillToTradeParty/SprfGlobalAttribute1 |
3 | Scheme identifier (SIRET) |
/cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID/@schemeID |
Value = 0009 |
4 | Payer’s company name |
/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PartyLegalEntity/cbc:RegistrationName |
TransferDocPayerTradeParty/PartyName |
5 | SIREN number |
/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PartyLegalEntity/cbc:CompanyID |
First 9 characters from the SIRET Number. |
6 | Scheme identifier |
/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PartyLegalEntity/cbc:CompanyID/@schemeID |
Value = 0002 |
7 | Payer’s VAT identifier |
/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PartyTaxScheme/cbc:CompanyID |
TransferDocPayerTradeParty/CustomerTaxRegNumber |
8 | Payer’s tax identification scheme |
/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PartyTaxScheme/cac:TaxScheme/cbc:ID |
Value = VAT |
9 | Payer’s electronic address |
/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cbc:EndpointID |
TransferDocPayerTradeParty/EmailAddress |
10 | Payer’s electronic address scheme identifier |
/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cbc:EndpointID/@schemeID |
Value = EM |
11 | Payer’s address - line 1 |
/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PostalAddress/cbc:StreetName |
TransferDocPayerTradeParty/ AddressLineOne |
12 | Payer’s address - line 2 |
/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PostalAddress/cbc:AdditionalStreetName |
TransferDocPayerTradeParty/ AddressLineTwo |
13 | Payer’s address - line 3 |
/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PostalAddress/cac:AddressLine/cbc:Line |
TransferDocPayerTradeParty/ AddressLineThree |
14 | Payer’s location |
/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PostalAddress/cbc:CityName |
TransferDocPayerTradeParty/ City |
15 | Payer’s postal code |
/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PostalAddress/cbc:PostalZone |
TransferDocPayerTradeParty/ PostalCode |
16 | Payer’s country subdivision |
/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PostalAddress/cbc:CountrySubentity |
TransferDocPayerTradeParty/ County |
17 | Payer’s country code |
/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PostalAddress/cac:Country/cbc:IdentificationCode |
TransferDocPayerTradeParty/ CountryCode |
18 | Payer contact point |
/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:Contact/cbc:Name |
TransferDocPayerTradeParty/ SiteCpName |
19 | Payer contact phone number |
/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:Contact/cbc:Telephone |
TransferDocPayerTradeParty/ SiteCpPhoneCountryCode TransferDocPayerTradeParty/ SiteCpPhoneAreaCode TransferDocPayerTradeParty/ SiteCpPhoneNumber TransferDocPayerTradeParty/ SiteCpPhoneExtension |
20 | Payer contacts electronic address |
/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:Contact/cbc:ElectronicMail |
TransferDocPayerTradeParty/ SiteCpEmailAddress |
21 | Payment account identifier |
/cac:PaymentMeans/cac:CardAccount/cbc:PrimaryAccountNumberID |
MaskedCcNumber |
22 | Payment account name |
/cac:PaymentMeans/cac:CardAccount/cbc:HolderName |
CcHolderName |
23 | Amount paid |
/cac:LegalMonetaryTotal/cbc:PrepaidAmount |
PrepaymentAmount |
24 | Rounded amount |
/cac:LegalMonetaryTotal/cbc:PayableRoundingAmount |
OrderRoundingAmount |
25 | ID of previous invoice |
/cac:BillingReference/cac:InvoiceDocumentReference/cbc:ID |
TransferDocLine/ OriginalTrxNumber |
26 | Previous invoice type |
/cac:BillingReference/cac:InvoiceDocumentReference/cbc:DocumentTypeCode |
TransferDocLine/ OriginalTrxType TransferDocLine/ OriginalTrxClass |
27 | Date of previous invoice |
/cac:BillingReference/cac:InvoiceDocumentReference/cbc:IssueDate |
TransferDocLine/ OriginalTrxDate |
28 | Number of previous invoice line |
/cac:BillingReference/cac:BillingReferenceLine/cbc:ID |
TransferDocLine/ OriginalLineNumber |
29 | Identifier of sales order by line |
/cac:OrderLineReference/cac:OrderReference/cbc:SalesOrderID |
TransferDocLine/ TransferDocSalesOrder/ SalesOrder |
30 | Invoice sales order line |
/cac:OrderLineReference/cbc:SalesOrderLineID |
TransferDocLine/ TransferDocSalesOrder/ SalesOrderLine |
31 | Address line 1 |
/cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:StreetName |
TransferDocLine/ ShipToLocAddress1 |
32 | Address line 2 |
/cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:AdditionalStreetName |
TransferDocLine/ ShipToLocAddress2 |
33 | Address line 3 |
/cac:Delivery/cac:DeliveryLocation/cac:Address/cac:AddressLine/cbc:Line |
TransferDocLine/ ShipToLocAddress3 |
34 | City of delivery |
/cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:CityName |
TransferDocLine/ ShipToLocCity |
35 | Delivery postal code |
/cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:PostalZone |
TransferDocLine/ ShipToLocPostalCode |
36 | Country subdivision |
/cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:CountrySubentity |
TransferDocLine/ ShipToLocCounty |
37 | Country code |
/cac:Delivery/cac:DeliveryLocation/cac:Address/cac:Country/cbc:IdentificationCode |
TransferDocLine/ ShipToLocCountry |
38 | Payment account identifier |
/cac:PaymentMeans/cac:CardAccount/cbc:PrimaryAccountNumberID |
MaskedCcNumber |
Process flow to generate UBL 2.1 e-invoicing messages:
- Create Receivables transactions with tax lines and all required details.
- Run Generate and Transfer XML Transactions process.
- Go to Manage Collaboration Messaging History page and open original extract message and the Transformed UBL 2.1. message.
Business benefits include:
- Additional data elements in the extract help reduce time to implement specific changes to the UBL 2.1 messages.
- Use the additional data elements in the UBL 2.1. mapping to create custom output files with required data.
Steps to Enable
Setup Notes for Electronic Invoicing for France:
- Navigate to the Setup and Maintenance > Manage Receivables Note Type.
- Search for Lookup ZMM_NOTE_TYPE with following details:
- Meaning = Note Type
- Description = Product specific classification of the note
- Module = Notes
- Lookup Configuration Level = Extension
- Define new Lookup Code. Note: For France the Lookup Code must be from UNTDID 4451 list. See following example setup:
- Lookup Code: AAI
- Enabled: Checked
- Start Date: 01/01/2024
- Meaning: General information
- Description: FR BT-21
- Save.
- Navigate to the Setup and Maintenance > Manage Receivables Note Type Mapping.
- Select Receivables Transactions as Business Object.
- Add row and define the Lookup Codes for Notes with following details:
- In the Mapped Lookup Value define the Lookup Code from previous step.
- Define Default as Yes or No.
- Save.
Tips And Considerations
- Complete the required prerequisite steps in Collaboration Messaging Framework to set up the message exchange between Oracle Cloud Applications and trading partners.
- A run of the Generate and Transfer XML Transactions process generates and displays the Original Message extract file and the UBL2.1 Transformed Message in the Manage Collaboration Messaging History page.
- The output file contains the XML File Header, Invoice Header, Invoice Lines, Invoice Tax details and additional invoice information specific to the transaction.
Access Requirements
No additional setup is required.
Third-Party Tax Registration Number Defaulting for Receivables Transactions 
Automatically assign the third-party tax registration number to Receivables transactions during transaction creation. This improves the accuracy of the tax information presented on Receivables transactions.
The third-party tax registration number belongs to the customer legal entity. You manually assign the third-party tax registration number to the bill-to customer in the Create or Edit Transaction page.
You can optionally enable automatic assignment of the legal entity third-party tax registration number to the bill-to customer during Receivables transaction creation. Transaction creation includes AutoInvoice import, manual creation using the Create Transaction page, and REST API and PL/SQL API web services.
Automatic assignment of the third-party tax registration number is helpful for companies in jurisdictions that require the tax registration number on transactions, and companies that use XML standards for invoicing, where the third-party tax registration number is a required field.
If automatic assignment of the third-party tax registration number is enabled, and no value is provided during transaction creation, the legal entity third-party tax registration number is assigned to the transaction according to the logic in this table.
# | Check | Match found | Match not found |
---|---|---|---|
1 | Does the Bill-to Site have a default tax registration number? |
If yes, assign the default tax registration number of the Bill-to Site to the transaction. |
If No, go to the next step #2 |
2 | Does the Bill-to Party have a default tax registration number? |
If yes, assign the default tax registration number of the Bill-to Party to the transaction. |
If No, go to the next step #3 |
3 | Does the Bill-to Party Site have a tax registration number in any of the following countries?
|
Check for a tax registration number for the Bill-to Party Site in the order:
If found, use the tax registration number of that registration. |
If not found, go to the next step #4 |
4 | Does the Bill-to Party have a have a tax registration number in any of the following countries?
|
Check for a tax registration number for the Bill-to Party in the order:
If found, use the tax registration number of that registration. |
If not found, then the third-party tax registration cannot be derived. |
If there are multiple taxes defined for a country, and therefore multiple matches are found, the tax registration number that corresponds to the tax regime and/or tax defined in the Oracle Tax Manage Country Default Controls page for that country is assigned to the transaction.
At the same level, a jurisdiction-specific tax registration is assigned over a tax-specific jurisdiction, and a tax-specific jurisdiction is assigned over a tax-regime-specific jurisdiction.
Business benefits include:
- Support automatic transaction creation processes that require the tax registration number.
- Support invoicing-related XML standards.
Steps to Enable
Enable the automatic assignment of the tax registration number to transactions for each applicable legal entity.
In Oracle Tax, in the Controls and Defaults section of the Edit Legal Entity Tax Profile page, enable the “Assign third-party tax registration number during Receivables transaction creation” option.
Tips And Considerations
Automatic assignment of the tax registration number occurs at transaction creation time only, and not during any transaction edits.
- If you manually enter the third-party tax registration number during transaction creation, then this value is used and the legal entity tax registration number is not assigned.
- Automatic assignment of the tax registration number to credit memos applies to on-account credit memos only created using the Create Transaction: Credit Memo page. It does not apply to credit memos created using the Credit Transaction page.
Key Resources
Revenue Management
Prospective Accounting Treatment for Immaterial Price Changes of Subscription Products
Use a prospective accounting treatment to reflect minor unit selling price changes for subscription products imported from Oracle Subscription Management.
While performing price adjustments for a particular period of a subscription's recurring charge in Oracle Subscription Management, you can choose the prospective accounting option. When this option is selected, Subscription Management:
- Sends a revision line with the revised plan end date (the date until which the initial selling price is applicable).
- Sends a new line with the new unit selling price and the start and end dates that the new price is in effect.
- Sends a second new line with the initial selling price for the remainder of the subscription.
For example, you have customer contract with one subscription from 01-Jan-2023 to 31-Dec-2023 at a selling price of 100 USD per month which is 1200 USD for the entire year. For an immaterial price decrease of 5 USD performed for March 2023, Subscription Management will:
- Revise the initial revenue line with line amount of 200 USD and end date as 28-Feb-2023.
- Send a new revenue line for March 2023 for the same item with unit selling price of 95 USD, line amount of 95 USD, start date as 01-Mar-2023 and end date as 31-Mar-2023.
- Send another new revenue line for the rest of the subscription period with unit selling price of 100 USD, line amount of 900 USD, start date as 01-Apr-2023 and end date as 31-Dec-2023.
Because the price change is set to initiate prospective accounting, after processing these lines, Revenue Management performs prospective accounting on the customer contract where the transaction price is reallocated only from the contract revision date. Revenue recognized before the contract revision date remains intact.
You can also choose the prospective accounting option in Subscription Management while performing the following actions:
- Close
- Close action terminates a subscription.
- Subscription Management sends a revision line revising the plan end date. Revenue recognized until the termination date remains intact and the remaining transaction price on the customer contract in Revenue Management is reallocated among the open performance obligations.
- Amend
- Amend implies closing a subscription and creating a new subscription.
- Based on your setup, Subscription Management either sends the new subscription as a new revenue line, which is created as a new customer contract in Revenue Management; or sends the new subscription to be added to the existing customer contract. Revenue Management performs prospective accounting by reallocating the new transaction price from the contract revision date among the new and open performance obligations.
- Suspend
- Subscription Management sends a revision line revising the plan end date. Revenue recognized until the suspension date remains intact and the remaining transaction price on the customer contract in Revenue Management is reallocated among the open performance obligations.
- Renewal
- Upon renewal, Subscription Management creates new subscription upon renewal. Based on your setup, Subscription Management either sends the new subscription as a new revenue line, which is created as a new customer contract in Revenue Management; or sends the new subscription to be added to the existing customer contract. Revenue Management performs prospective accounting by reallocating the new transaction price from the contract revision date among the new and open performance obligations.
- Rate adjustment of Pricing Term
- Whenever there is a change in the rate adjustment, Subscription Management sends a revision line for that pricing term with the new unit selling price. Revenue Management performs prospective accounting by reallocating the new transaction price among the open performance obligations from the contract revision date. Revenue recognized until a day before the contract revision date remains intact.
When processing immaterial price changes that do not significantly alter the initial terms and the net consideration of the contract such as price changes due to indexation, you can choose the prospective accounting treatment. The impact on the price change impacts only current and future periods. This allows you to record the price changes without having to restate any previously recognized revenue.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- Subscription Management lets you choose the prospective accounting option only for recurring charges. Price revisions of one-time and usage charges are always sent using the retrospective accounting option.
- Prospective accounting is supported only when the satisfaction plan is Daily rates partial periods. Because the satisfaction plan is defaulted from the Manage Source Document Types page, you must set the default value of the satisfaction plan to Daily rates partial periods for the source document type Subscription Management.
- Any revisions performed on a one-time charge trigger retrospective accounting on the customer contract.
- A new one-time charge added to an existing contract triggers retrospective accounting on the customer contract.
- If any of the revenue lines with a satisfaction measurement model of Quantity or Percent are not fully satisfied in the contract, it always triggers retrospective accounting on the customer contract.
- If you perform a backdated price adjustment on a customer contract on which prospective accounting was previously performed, the backdated price adjustment triggers retrospective accounting on the customer contract.
Key Resources
- Prospective Accounting for Immaterial Price Changes in Subscription Products
- Guidelines for Using Prospective Accounting with Subscription Products
Access Requirements
No new role access is needed to use this feature.
Asset and Lease Management
Assets
Segregation of Asset Transaction Entry and Transaction Posting Duties Using Spreadsheets
Segregate the duties for users who enter and prepare asset transactions and users who review and post the transactions using spreadsheets. This helps enforce the internal control requirement that users who review and post asset transactions are different from those who create the transactions.
When you segregate duties, two unique users with a custom job role assigned to each user are required for each transaction.
- Transaction Preparer User can:
- Create all asset transactions, including Addition, Adjustment, Transfer and Retirement transactions in draft and set the status to Review, but can't post transactions using an ADFdi spreadsheet.
- Create Impairment and Revaluation transactions and set the posting status to Review after the transactions have been previewed.
- Transaction Reviewer User can:
- Review transactions in Edit mode and post all the asset transactions, including Addition, Adjustment, Transfer and Retirement, Impairment and Revaluation transactions, but cannot Create or Edit the transactions.
- Send a transaction back to the preparer if it requires corrections by changing the queue status to New.
Business benefits include:.
- Enforces the internal control requiring one user to create a transaction and a different user to review and post the transaction.
- Eliminates errors when recording transactions because they're prepared and reviewed by two different users.
- Ensures transactions are verified and reviewed before they're posted.
- Ensures efficiency in recording transactions because the segregation of duties is at the user level and not at the asset book level.
- Allows easy preparation and review of transactions in volume using an ADFdi spreadsheet.
Steps to Enable
- Use the Opt in to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.
- Offering: Financials
- Use the opt-in for Segregation of Asset Transaction Entry and Transaction Posting Duties in Fixed Assets to enable this feature.
- Setup and Maintenance -> Financials -> Change Feature Opt in -> Financials -> Edit Feature -> Segregation of Asset Transaction Entry and Transaction Posting Duties.
- Roles for the Transaction Preparer
- Create a custom job role by copying the predefined 'Asset Accounting Manager' Job role. (ORA_FA_ASSET_ACCOUNTING_MANAGER_JOB)
- Delete the predefined duty role 'Fixed Asset Transaction Management' from the copied custom job role.
- Create the 'Custom Asset Transaction Entry Duty' custom duty role by copying the predefined Fixed Asset Transaction Management (ORA_FA_FIXED_ASSET_TRANSACTION_MANAGEMENT_DUTY duty role)
- Add the custom duty role ‘Custom Asset Transaction Entry Duty’ to the custom job role.
- Remove the following functional privileges for the Transaction Preparer user to disable to post privileges:
- Post Fixed Asset Online Transactions (FA_POST_FIXED_ASSET_ONLINE_TRANSACTIONS)
- Post Mass Fixed Asset Financial Transactions (FA_POST_MASS_FIXED_ASSET_FINANCIAL_TRANSACTIONS)
- Post Mass Fixed Asset Retirement (FA_POST_MASS_FIXED_ASSET_RETIREMENT)
- Post Mass Additions (FA_POST_MASS_ADDITIONS)
- Post Mass Fixed Asset Assignment (FA_POST_MASS_FIXED_ASSET_ASSIGNMENT)
- Roles for the Transaction Reviewer
- Create a custom job role by copying the predefined 'Asset Accounting Manager' job role. (ORA_FA_ASSET_ACCOUNTING_MANAGER_JOB)
- Create a custom duty role called 'Custom Asset Transaction Review Duty'
- Add the custom duty role 'Custom Asset Transaction Review Duty' to the custom job role.
- Add the following functional privileges for the Transaction Reviewer.
- View Fixed Asset Addition (FA_VIEW_FIXED_ASSET_ADDITION_PRIV)
- View Fixed Asset Adjustment (FA_VIEW_FIXED_ASSET_ADJUSTMENT_PRIV)
- View Fixed Asset Transfer (FA_VIEW_FIXED_ASSET_TRANSFER_PRIV)
- View Fixed Asset Retirement (FA_VIEW_FIXED_ASSET_RETIREMENT_PRIV)
- To enable the profile option for performing impairment transactions, complete these steps.
- In the Setup and Maintenance work area, go to the Manage Profile Options page.
- Search for the profile code FA_IMPAIRMENT_PREPARER.
- Enable the: Enabled and Updatable check boxes for the User.
- In the Setup and Maintenance work area, go to the Manage Fixed Assets Profile Options task
- Search for the Profile Option Code: FA_IMPAIRMENT_PREPARER
- Add the transaction preparer user and set the Profile Value to 'Y'.
- Click Save and Close
Tips And Considerations
For cost adjustments, the transaction reviewer can review and post these transactions only after the preparer changes the posting status to Review. The transaction preparer does this after adding an asset to the existing asset by clicking the Add to Asset button in the Assets landing page or the Prepare Source Lines page.
Segregation of Duties with transaction preparer and reviewer doesn't apply to the following transactions.
- Transfer Reserve for Group Assets
- Capitalize CIP Asset
- Change Descriptive Details
- Delete Asset
Key Resources
- Refer to Segregation of Transaction Entry and Posting Duties in the Implementing Assets guide on Oracle Help Center.
- How to create custom role and privileges
Total Cost Display for Parent Asset Addition Lines in Assets
View the total cost of the parent and its merged child addition lines in the Assets Landing page, Lines Selected for Merge dialog box, and Prepare Source Lines page.
View of Merged Cost Column in Assets Landing Page
Lines Selected for Merge Dialog Box
View of Merged Cost Column in Prepare Source Lines Page
Business Benefit:
The display of the merged cost of the parent and child source lines in the Prepare Source Lines page, Assets landing page, and Lines Selected for Merge dialog box helps you view at a glance the cost at which the asset will be capitalized when it's added.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Lease Accounting
End of Lease Processing for Revenue Leases
Perform the end of lease processing activities: exercise or cancel a lease option or terminate a lease. Exercise a lease option to automatically put into effect the right conferred by the option; either to shorten or extend the lease. Cancel a lease option if the option wouldn't be exercised in the future. Terminate a lease, fully or partially, if the lessor or the lessee needs to break the lease early. In all cases, the contract is automatically amended to adjust billing, revenue recognition, and accounting balances; and maintain an audit of the changes.
The following screenshots describe the process of terminating a revenue lease.
Terminate Leases available from Actions
Create Lease Termination Page
Business benefits include:
- Improve operational efficiency with streamlined lease termination and option management processes.
- Reduce time and effort through the automated expiration of leases.
- Gain insights into upcoming options through the Lease Accounting dashboard.
Steps to Enable
Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.
Offering: Financials No Longer Optional From: Update 24D
Access Requirements
You do not need any new role or privilege access to set up and use this feature.
Lease Term Reduction with Liability Remeasurement
Modify leases to shorten the lease term in accordance with ASC 842 lease accounting standards. Account the lease modification under ASC 842 by remeasuring the lease liability. The carrying amount of the right-of-use asset is adjusted by the amount of the remeasurement of the lease liability.
The following screenshots describe the process of amending a lease to account for term reduction with liability remeasurement.
Create Amendment Page
Update Lease Details Page
Business benefits include:
- Enable compliance with ASC 842 lease accounting for lease term reduction.
- Increase operational efficiency with streamlined lease amendments.
Steps to Enable
Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.
Offering: Financials
Access Requirements
You do not need any new role or privilege access to set up and use this feature.
Miscellaneous Lease Charges for Revenue Leases
Capture miscellaneous items associated with a lease, and transfer them to Receivables for billing and collection. Miscellaneous lease-related items include cleaning fees or fees to decorate the lobby for the holidays and other such items.
The following screenshots describe the process of creating miscellaneous payments.
Manage Revenue Payments Page
Create Miscellaneous Payment Page
Business benefits include:
- Better tracking of one-time and ad hoc payments by lease.
- Accurate and timely billing to lessees.
- Simplified data entry.
Steps to Enable
Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.
Offering: Financials No Longer Optional From: Update 24D
Access Requirements
You do not need any new role or privilege access to set up and use this feature.
Revenue Lease Contract Import and Conversion
Use the Lease Import process to simplify both lease conversions and new lease creation. The Lease Import process removes or reduces the need for manual intervention during the lease creation process. Import a batch of leases directly into the desired status: Draft, Validated, Complete, or Booked.
The following screenshot describes the process of importing revenue lease contracts.
Revenue Lease Contract Import
Use the Lease Amendment Import process to simplify contract changes. The Lease Amendment Import process removes or reduces the need for manual intervention during the lease amendment process. Amendments include scope increases, scope decreases, and nonfinancial changes. Import a batch of lease amendments directly into the desired status: Draft, Validated, Complete, or Booked.
The following screenshot describes the process of importing revenue lease amendments.
Revenue Lease Amendment Import
Business benefits include:
- Reduce data entry effort with revenue lease contract and amendment import.
- Streamline business processes by importing revenue lease contracts and amendments from origination systems.
- Reduce implementation time and increase ROI with functionality to migrate existing portfolios.
Steps to Enable
Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.
Offering: Financials No Longer Optional From: Update 24D
Access Requirements
You do not need any new role or privilege access to set up and use this feature.
Region and Country-Specific Features
Financials for EMEA
Support for Additional Supply Chain Transactions in Portugal SAF-T
Include additional supply chain transactions, such as transfer orders, in the SAF-T report for Portugal.
The report now includes the required information for customers with multiple customer accounts, ship-to sites, and bill-to sites.
Under the new logic introduced, each CustomerID created for billing transactions in Receivables, will be recorded with the bill-to address in detail and the ship-to address set as Desconhecido, meaning Unknown in Portuguese. This establishes data integrity when the same customer and bill-to site is used to create multiple transactions with different ship-to sites. Similarly, each CustomerID created for shipping transactions in Order Management and Shipping, will be recorded with the ship-to address in detail and the bill-to address set as Desconhecido.
In Order Management, if the same customer and ship-to site is assigned to transactions with different customer accounts, the customer account selected for the CustomerID definition for both the transactions and the master-file sections of the SAF-T report is the one associated with the ship-to site.
The length of the customer account number used in the creation of the CustomerID, for both Financials and Order Management transactions, has been increased from 11 to 14 characters. Any customer account number that exceeds 14 characters is truncated in reverse order.
This release includes these features:
- The predefined receipt method ORA_AP/AR Netting is assigned to receipts created by the Netting application. You cannot update this receipt method with a country-specific descriptive flexfield. For SAF-T requirements, the receipt method for these receipts is hard-coded as CS, the corresponding method for Netting.
- The Unit of Measure values in all sections of the SAF-T report use the UOM_Name values in the Shipping documents.
- The Suppliers block is included with the Customers block in the master-file sections of all reporting level parameter values of SAF-T.
- In accordance with recent tax legislation, you can optionally exclude the Payments block along with all receipts entered for the given period. The update includes the exclusion of the CustomerIDs from the master-files section, for customers used only for receipts in the given period.
Business benefits include:
- Expands the usability of the SAF-T report for Portugal with a more comprehensive view of current business practices and requirements.
- Ensures the validity of the SAF-T XML extract for each additional business case considered.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- The inclusion in the customer master-file records of all ship-to sites under Financials transactions and all bill-to sites under Shipping transactions is optional. These values can be replaced with the value Unknown in the SAF-T. A validation error occurs if the number of ship-to sites exceeds 300 locations. And the inclusion of all bill-to sites under Shipping generates multiple copies of the same CustomerID in the master-file section.
- Certain shipping transaction types require clarification of the customer account number to use for the CustomerID. Otherwise, if the default account values are updated, this can create customer account and ship-to site combinations that don’t exist in third-party records.
- The length of the customer account number increase from 11 to 14 characters accommodates new user requirements. The maximum length of the CustomerID is 30 characters, and 16 of these characters are assigned to the site or location ID with hyphen. Truncation of a customer account number works backward from the final character, since the numbers tend to differ in the final digits.
- The Payments block is not required if the receipts are not signed and printed by the system.
- The resolution of the additional issues reported removes the related validation errors and ensures complete delivery of the SAF-T extract to the tax authorities.
The default functionality of the application is to report all sections, including the receipts. The users that want to restrict the receipts block to be reported need to create and enable the lookup code value JE_35952576 under the ORA_ERP_CONTROLLED_CONFIG lookup_type.
Key Resources
- All the updates will be included in the next update of the Oracle ERP Cloud Certification for Portugal document.
India
India Document Numbering for Multiple Legal Reporting Units with the Same Tax Registration Number
Allow document numbering for multiple legal reporting units that share the same tax registration number in India for Global Intercompany transactions.
Under the India GST tax regime, a taxpayer may have one tax registration number for a particular state, but may be required to report multiple gapless document sequences for the same tax registration. For example, a customer with a single GST Tax Registration Number (GSTIN) in a particular state may want to supply goods and services from 2 different locations registered as SEZs in this state. In this case, even though both locations/units are under the same GST Registration Number, the tax invoice numbers must be generated in separate gapless document sequences, if the goods and services are from these units.
The Document Fiscal Classification (DFC) tax attribute can manage this scenario for customer transactions. But for Global Intercompany invoices imported through the AGIS (FUN) module, the DFC cannot be derived. To support this requirement, customers have been creating multiple additional setups or adopting multiple manual steps that deviate from the automated processing of Intercompany invoices.
ERP Cloud now enables customers to define Document Numbering for India, based on Legal Reporting Units with the same GST Registration number for Global Intercompany transactions. The system automatically derives the underlying Legal Reporting Unit mapped to the Intercompany Organization in the Intercompany setups and derives the correct Document Sequence to generate the Tax Invoice Number from the India Document Numbering setup.
Business benefits include:
- Maintain fewer tax registration setups and reduce the workload on the Tax engine.
- Streamline resource bandwidth with fewer steps and automated Intercompany flows without manual intervention.
Steps to Enable
- Introduced a new column "Legal Reporting Unit" in the India Document Numbering Setup ADFDI sheet.
- Against the "Receivables" application, a new document class value ('Global Intercompany Invoice') in the LOV is added.
Navigation: FSM Task --> Search --> Search for “Manage Localization Document Numbering” --> Search for “India”
- Perform the setup for Application=Receivable, Document class= 'Global Intercompany Invoice' and choose the relevant Legal Reporting Unit which is mapped to the Intercompany Organization setup against the Provider Org.
Tips And Considerations
- Legal Reporting Unit is associated with a list of values containing valid LRUs against the First Party Tax Registration Number selected at the header level of the setup.
- Valid values appear in the LOV when Application = Receivable and Document Class = Global Intercompany Invoice. Other combinations in the Legal Reporting Unit field will not retrieve any LOV values. This is to ensure that this feature applies only to transactions created from the Global Intercompany System.
- If there are no entries available for Application = Receivable and Document Class = Global Intercompany Invoice in the India Document Numbering setup, then the system derives the document sequence using existing rules.
Key Resources
- Review the following What's New content to understand how you can associate the first-party tax registration number with the intercompany organization and pass the number as an attribute to the subledger for intercompany transaction tax calculations.
- 23B What's New content, Intercompany > Tax Calculation for Intercompany Invoices Based on First-Party Tax Registration Number
U.S. Federal Financials
U.S. Federal Financials
Federal DATA Act Reporting Configurations
Configure the attributes related to the US Federal DATA Act process and report in accordance with Treasury’s reporting requirements. Configure each attribute for the DATA Act balances, including the DATA Act balance name, file type, and related balance criteria.
The DATA Act requires agencies to report data monthly to the US Department of the Treasury. There are three types of DATA Act files that are used to report financial data based on Treasury’s specifications for the DATA Act process. The DATA Act files include:
General Ledger data:
- File A–Appropriations Account Data–13 balance columns
- File B–Object Class and Program Activity–32 balance columns
Purchasing, Accounts Payable, and General Ledger data:
- File C–Award Financial (Procurement and Grants) –32 balance columns and detailed transactions
The Manage Federal DATA Act Balances page is used to create and update Treasury-defined DATA Act field names and navigate to the DATA Act Balance Sequence page to create sequences for each of the file types. You can enter the USSGL accounts that need to be summed for the field. Existing DATA Act fields can be summed to create the balance for a new DATA Act field using the Total type. You can use sequencing to update the list of reported DATA Act balance fields and the order in which they will be reported.
Manage Federal DATA Act Balances
The Manage Federal DATA Act Balances page displays all existing DATA Act Balance fields by Type and File.
The Manage Federal DATA Act Balances page for the Balances type allows a user to add USSGL accounts to calculate the balance.
The Manage Federal DATA Act Balances page for the Total type allows a user to create the balance for a new DATA Act field by summing existing DATA Act fields.
DATA Act Balance Sequence
The DATA Act Balance Sequence page lists all DATA Act Balance fields by File Type (A, B, or C) and allows the user to add or remove fields from the report as necessary. The DATA Act Balance Sequence page is accessed by clicking File A Sequence, File B Sequence, or File C Sequence from the More Actions menu of the Manage Federal DATA Act Balances page.
DATA Act Balance Sequence: Criteria Tab
Use the Criteria tab to add one or more criteria that you can use for filtering selected accounting records.
Business Benefit:
The configurations will provide the infrastructure needed to perform the DATA Act process and report generation for Treasury reporting requirements.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- For more information on Federal DATA Act Reporting Configurations, refer to the implementing U.S. Federal Financials and Using U.S. Federal Financials guides.
Access Requirements
- Financial Application Administrator
Federal GTAS Reporting Configurations
Configure the attributes related to the U.S. Federal GTAS process and report in accordance with Treasury’s reporting requirements. Configure account attributes, attribute supplemental rules, and attribute assignment, including Treasury-defined attribute names, their sources, and their association with different USSGL accounts.
GTAS serves as the single USSGL trial balance for each TAS including budgetary and proprietary USSGL beginning and ending balances. Use the following GTAS configuration interfaces to report financial data based on Treasury’s specifications for the GTAS process:
- Manage Federal Attributes
- Manage Federal Account Attributes
- Manage Federal Attribute Supplemental Rules
Use the Manage Federal Attributes page to map the category, source, and source lookup type for each of the federal attributes.
Use the Federal Account Attributes page to enter attributes for USSGL accounts or natural accounts.
Use the Manage Federal Attribute Supplemental Rules page to map account combinations to federal attributes as well as to override attribute assignments for the federal attributes.
Business Benefit:
The configurations will provide the infrastructure needed to perform tasks required for GTAS reporting.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- For more information on federal GTAS reporting configurations, refer to the Implementing U.S. Federal Financials and Using U.S. Federal Financials guides.
Access Requirements
- Financial Application Administrator