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.
Usability:
Procure to Pay - Invoice Processing:
- When an intercompany batch is created with the invoice flag enabled, the Transfer to Receivables process successfully generates an AR transaction. However, interface errors can occur during the Transfer to Payables process. These errors cause the related global intercompany invoices to be rejected in the AP interface. Currently, the Correct Import Spreadsheet allows users to delete these rejected intercompany invoices. If a global intercompany invoice is deleted from the AP interface after the corresponding AR transaction has been created (and possibly accounted), this may result in reconciliation discrepancies between AR and AP. To mitigate this risk, users are now prohibited from deleting intercompany invoices (source = GLOBAL_INTERCOMPANY) from the AP interface using the Correct Import Error spreadsheet.
The feature is controlled via Dev Opt-In.
Customers who wish to use this feature must enable the corresponding Dev Opt-In and download a new Correct Import Errors spreadsheet. Previously downloaded or older spreadsheets will not support this functionality. Customers who do not enable the Dev Opt-In will not be affected and may continue using their existing spreadsheets.
Steps to Configure:
- Navigate to Setup and Maintenance.
- Search and navigate to Task: Manage Standard Lookups.
- Search for Lookup Type: ORA_ERP_CONTROLLED_CONFIG.
- Define a lookup code under the ORA_ERP_CONTROLLED_CONFIG lookup type with the following details:
- Lookup Code: AP_37826370
- Enabled: Selected
- Meaning/Description: Restrict Delete of GLOBAL_INTERCOMPANY Invoices from Correct Import Errors sheet.
- Select Save and Close.
Note: To leverage this functionality, users must download the latest Correct Import Errors Worksheet after enabling the Dev Opt-In.
Credit to Cash - Bill Management:
- The Bill Management Transaction History page now displays standard and on-account credit memos, whether partially or fully applied.
Performance:
Credit to Cash - Receivables:
- The Create Balance Forward Billing (BFB) ESS process has been enhanced to support parallel execution, improving the processing speed for high-volume transactions. This enhancement is managed by a Dev Opt-In feature. Customers who wish to utilize this improvement must explicitly enable the Dev Opt-In. Those who do not enable the option will not be affected and can continue using the current Create Balance Forward ESS job without any changes.
Steps to Configure:
- Navigate to Setup and Maintenance.
- Search and navigate to Task: Manage Standard Lookups.
- Search for Lookup Type: ORA_ERP_CONTROLLED_CONFIG.
- Define a lookup code under the ORA_ERP_CONTROLLED_CONFIG lookup type with the following details:
- Lookup Code: AR_37329108
- Enabled: Selected
- Meaning / Description: Opt-in for Create BFB parallelization enablement
- Select Save and Close.
Resiliency:
Record to Report - Accounting Processing:
- To prevent situations that can lead to financial data corruption, the standard precision setting of a currency can no longer be increased or decreased. You can continue to make changes to its extended precision setting. This applies to any currency that had already been used to record transactions in the system, specifically for entered and accounted amounts in General Ledger journals.
Increasing or decreasing the precision for currencies can cause problems.
- Issues with audit and compliance: Financial data must remain consistent across reporting periods to meet regulatory and audit requirements. Adjusting currency precision can alter historical records.
- Calculation errors in accounting processes: Many accounting processes, such as foreign currency conversion, asset depreciation, revaluation, translation and allocation depend on consistency with the currency precision. A change can cause unexpected variations and impact the accuracy of these computations.
- Disruptions with system integrations: External systems that interact with accounting data (for example, tax engines, financial consolidation systems, reporting tools) expect a consistent currency precision. A change can cause failures with such integrations.
By preventing an actively used currency precision from getting updated, this will help prevent the occurrence of such problems that can result in corrupted financial data.
Improvement:
Credit to Cash - Collections and Delinquency Management:
- The Strategy Tasks infotile in the Advanced Collection work area has been enhanced to include the collections score and aging bucket balances as optional columns. By default, these columns are hidden but can be added from the Columns list. This enhancement provides collectors with greater insight into customer payment risk and delinquency directly from the task overview, enabling better prioritization of strategy tasks, faster identification of high-risk and past-due customers, and more informed, timely collections actions. Additionally, the collections score is now displayed in the Details and Strategies tabs of the Customer Profile page, ensuring consistent access to this information across collections work areas.
Steps to enable and configure
You don't need to do anything to enable this feature.