Reference: Financial Management Tenant Configuration Guidelines

Administrator Guide

Download PDF

This table includes tenant configuration guidelines that Workday recommends for:

Allocations

Account Certifications

Average Daily Balances

Budgets

Consolidation Data Capture

Intercompany Supplier Invoices

Intercompany Transactions

Journal Sources and Mapping

Project Management & Core Setup

Project Resource Management

Requisitions

Retained Earnings

Settlement Runs

Supplier Accounts

Supplier Integration

Supplier Invoices

Component	Issues and Causes	Configuration Guidelines
Allocations	Issue : Slow performance or failure when processing allocations. Cause : You’ve assigned a large number of worktags to the target and offset of allocations.	Removing unnecessary worktags from the process, especially if you’re mapping worktags from source, will help speed up allocation calculations and can significantly reduce journal line output. Security: Set Up: Allocations domain in the Financial Accounting functional area. Access the Create Allocation Definition task. In the Target and Offset sections, remove unnecessary worktags from the Worktag Mapping grid. See also, Improving Expense Allocation Processing Time.
Allocations	Issue : Unable to select any ledger period for a new fiscal year on the Allocation Work Area report. Cause : You haven't opened the new fiscal year and the ledger periods in the new fiscal year. The new fiscal year has a Created status and not an Open status.	Open the fiscal year and the ledger periods. Security: Process: Period End in the Common Financial Management functional area. Access the Mass Update Ledger Period Status task. Select the new fiscal year you want to open. Select All Periods to open all ledger periods for the fiscal year. Click OK .
Account Certifications	Issue : Account certification business process is auto approving journals with activity and where the account balance in not zero. Cause : You may have configured the Account Certification with an incorrect worktag hierarchy. When you configure Worktag values, which may include hierarchies, on the Account Certification, all Worktag values on the journal lines and the account certification must match, otherwise the business process will not submit the certification for approval.	Ensure you have configured the Account Certification with the correct Worktag values, which may include hierarchies.
Account Certifications	Issue : Service Representative who is assigned as an Account Certifications Reviewer and Account Certifications Preparer is unable to view an Account Certification Workbook. Cause : The service representative may not have a company role assigned.	Assign a company role to the service representative. Access the company to which you want to assign the service representative a role. From the related actions of the company, select Role Assign Roles . Select an effective date and click OK . Perform 1 of these actions: Assign any role to the service representative. Create a new company role and assign the new role to the service representative. This assigns a company role to the service representative.
Average Daily Balances	Issue : Average Daily Balance processing is slow to complete. Cause : You're using average daily balance (ADB) 2.0.	Adopt Average Daily Balance (ADB) version 3.0. For detailed information on how to opt-in to ADB 3.0, see the What’s New Post on Community: Performance Enhancements for Average Daily Balance.
Budgets	Issue : Unable to submit a plan for a period using the Submit Plan task. Cause : You may have a critical validation that is preventing you from submitting the plan. Deleting the critical validation is not enough. You need to also update the Budget Entry Line to submit the plan.	Remove the critical validation on the Budget Entry Line. Create a new custom validation of Warning to replace the critical validation. Access the Maintain Custom Validations report. Security: Set Up: Custom Validations in the Common Financial Management System functional area. For Budget Line , add a validation of Warning that will ignore the critical error you had. The Warning validation will display a warning but will not prevent you from submitting your plan. Access the period for which you were unable to submit the plan. From the related actions of the Plan Period , select Plan Period Maintain Budget . Enter the necessary Ledger Account/Summary and Worktags and click OK . Confirm the Plan Line values and click OK . Workday validates the Budget Line with the new Warning validation that you previously created. Once the validation is complete, you can submit the plan. After the plan is successfully submitted, remove the Warning validation you created.
Consolidation Data Capture	Issue : User is unable to view a diagnostic audit file generated from a Consolidated Data Capture run. Cause : User may not have access to the audit file.	Assign user access to the audit file. Access the View Domain report. Depending on your configuration needs, select 1 or both of these domains: Integration Process Integration Event From the related actions of the domain, select Domain Edit Security Policy Permissions . Ensure the user is a member of the security group configured/defined within the security policy. If the user is not a member of the security group, add the user to the security group. Access the Activate Pending Security Policy Changes task. Enter a comment and click OK . Select Confirm and click OK .
Intercompany Supplier Invoices	Issue : A number of Direct Intercompany supplier invoices are not showing as available for selection in Settlement Run. Cause : You’ve removed the supplier from the Operates as Supplier field on the Maintain Companies as Customers or Suppliers task after you created an intercompany invoice and before running the settlement.	Access the Maintain Companies as Customers or Suppliers task and confirm the supplier company is setup as a supplier. Direct intercompany invoices that you create while the Direct Intercompany configuration is in place won't be available for settlement if you change the intercompany configuration before settlement.
Intercompany Transactions	Issue : Intercompany transactions are not balancing. Cause : You have incorrectly created an operational direct intercompany transaction between 2 companies, where the intercompany affiliate from the billing company is being displayed on the supplier invoice. This has resulted in the same company being entered on the journal Header and Lines. This may occur when you didn’t enable the Default Affiliate option, for the 2 companies on the Maintain Companies as Customers or Suppliers task.	Ensure that you have the Default Affiliate option enabled for the billing and supplier companies. Access the Maintain Companies as Cuomsters or Suppliers task. Security: Set Up: Company Accounting domain in the Common Financial Management Ensure the Default Affilate option is enabled for both the companies with the intercompany operational transaction.
Journal Sources and Mapping	Issue : Missing journal sources on operational journals can cause potential reporting or downstream transaction impacts. Cause : There is a blank field in the Maintain Journal Source Mapping to Operational Transactions task.	Ensure you have all fields filled out in the Maintain Journal Source Mapping to Operational Transactions task.
Project Management & Core Setup	Issue : There are two projects with the same project ID. This project ID is also listed in the sequence generator for projects. Cause : There may be a number of causes that create this issue. Each cause has a different configuration guideline. #1 : Your configured sequence generator for projects has ran out of sequence numbers. #2 : Your time-based reset settings are causing duplicate sequence numbers upon reset. #3 : Your users are manually entering a project ID for a sequence number that has already been used. #4 : Your users are manually entered project IDs for a future number that the sequence generator is likely to create. Eventually the sequence number generator will create a duplicate with this project ID.	Follow each guideline sequentially to diagnose and solve the issue. If your issue isn’t solved, continue to the next cause and configuration guideline. #1 : Configure the Sequence ID Overflow Behavior field. See Step 6 in Create ID Definitions and Sequence Generators . #2 : Access 1 of these sequence generator tasks that you use: Create ID Definition / Sequence Generator Create ID Definition / Gapless Sequence Generator In the Sequence ID Format field, if you’ve set the restart frequency interval, ensure that the generated sequence number is unique by including the specific time period in the format. Example: If the Restart Frequency time period is Month , include [month] and [year] in the format. Make sure that the padding value is large enough that the sequence generator doesn't encounter an overflow condition during the time period. Note: The Restart Frequency field isn't available for gapless sequence generators. #3 : Ensure the user is not entering a duplicate project ID that already exists, as the sequence generator will propose a project ID based on the sequence. #4 : Run the View Reference ID report and sort the Reference ID values to find the last used Reference ID for the sequence pattern. Access 1 of these sequence generator tasks that you use: Create ID Definition / Sequence Generator Create ID Definition / Gapless Sequence Generator Under Last Sequence ID, enter the Last Sequence Used .
Project Resource Management	Issue : Time Entry submitted doesn't contain the Required Project Role. Cause : You performed 1 of these actions: Didn't select the Require _{Project Role} for Time Entry check box on Time Entry Template. Removed the worker from the project talent pool before Time Entry was approved.	Ensure: To select the Require _{Project Role} for Time Entry check box. The worker is in the project talent pool. See: Steps: Set Up Project Time Entry.
Requisitions	Issue : Delay in processing requisitions. Cause : You’ve assigned a security group with a large number of users to a print-related business process step.	You can experience slow performance when you assign a security group with multiple users to a report step on these print-related business processes: Goods Delivery Run Inventory Count Event Inventory Pick List Event Inventory Shipment Event Inventory Par Count Event The business processes generate separate print jobs for each user instead of a single job. Workday therefore recommends you assign a security group with smaller number of users. Example: Integration User group. See: Concept: Security Groups. Create User-Based Security Groups.
Retained Earnings	Issue : Worktags types that you removed from the Retained Earnings field continue to display on journals when you roll forward retained earnings. Cause : The tenant-level worktag configuration only impacts activity balances and doesn't affect balances that you roll forward from prior years.	Identify the beginning balance journal lines from prior years from which to remove worktag types during roll forward. Create a summarized reversal manual journal that includes all of worktag types for the journal. Create a second summarized reversal manual journal and exclude the worktag types you don't want to roll forward. Roll forward the second new journal. See Roll Year-End Balances Forward.
Retained Earnings	Issue : The Adaptive Journal integration fails after moving to the new Retained Earnings Framework. Cause : You performed a Retained Earnings Uptake and didn't update your adaptive integrations.	To update your Adaptive Integrations, reach out to Expert Assist.
Settlement Runs	Issue : Scheduled settlement runs are not running. Cause : Worker who created the scheduled run does not have the security domain required to view the bank accounts in that run.	Ensure that the worker has access to the security domain required to view the bank account. Re-add the worker to the correct security domain. See Edit Domain Security Policies.
Supplier Accounts	Issue : You’re noticing that the Spend Obligation Journals generated by a Purchase Order are not being posted to the respective ledger accounts. Cause : While editing an invoice, you may have deleted the original splits on the invoice line and created new splits. When you delete the original splits which are associated to the Purchase Order line splits, the link between the invoice line splits and the related Purchase Order line splits are broken. Since the new splits are no longer linked to the original Purchase Order line splits, the Obligation journals can’t locate the ledger accounts to post to.	When you edit supplier invoice, ensure you do not delete the splits on the invoice line as they are linked to the Purchase Order line splits. To accurately link invoice line splits to the Purchase Order lines and splits, you can cancel the invoice, and recreate the invoice correctly against the purchase order.
Supplier Integration	Issue : New suppliers are not being assigned on the Supplier Event Business Process. Cause : You may have configured the Supplier Event Business Process incorrectly.	Add additional security group as user-based or unconstrained role-based to the Supplier Event Business Process. See: Create User-Based Security Groups Create Role-Based Security Groups
Supplier Invoices	Issue : Missing sequence numbers for supplier invoices when you close your ledger year period. Cause : You ran 2 concurrent jobs to open the same period for 2 different company hierarchies that have a common company included in both hierarchies.	When you open a ledger period for company hierarchies, we recommend that you include a company in just 1 hierarchy or schedule jobs to run at a different day or time. See Change the Status of Ledger Periods.
Supplier Invoices	Issue : Unable to specify the Tax Point Date Type on the Submit Supplier Invoice Adjustment web service when creating an adjustment against existing invoices. Cause : You have not enabled the Enable Tax Point Date Configuration for Transaction Taxes option on the Edit Tenant Setup-Financials task.	Security: Set Up: Tenant Setup – Financials in the System domain. Access the Edit Tenant Setup – Financials task and under the Tax Options section, select Enable Tax Point Date Configuration for Transaction Taxes. Run the Submit Invoice Adjustment web service and enter Tax_Point_Date_Type _ID under both these nodes: Tax_Data Tax_Rate_Data