Workday provides tenant-wide configuration options that control how documents and their related attachments are displayed to users across the system, and these settings are centralized in a single configuration task to ensure consistent behavior across all companies in the tenant. The Official Workday Pro Procure-to-Pay Guide identifies Edit Tenant Setup - Financials as the task containing the option to display supplier invoice and invoice adjustment attachments side by side when applicable, improving usability for accounts payable staff reviewing supporting documentation. Option B is incorrect because Edit Company Accounting Details configures company-specific accounting settings such as ledger assignment and fiscal calendars, not document display preferences. Option C is incorrect because Edit Company Procurement Options governs procurement-specific behaviors like sourcing and requisition defaults, and does not control invoice attachment display. Option D is incorrect because Edit Supplier Account Options is not the task that manages tenant-level display configuration for supplier invoice attachments; this setting is a financial display preference configured at the tenant level.

Worktags are the dimensions, such as cost center, fund, project, and custom worktags, used throughout Workday for accounting, reporting, and security. Because some worktag values should only be usable in combination with certain other worktags or organizations, Workday provides a configuration layer to control these allowed combinations. The Official Workday Pro Procure-to-Pay Guide identifies Maintain Related Worktag Usage as the task used to view and modify which worktag values are allowed together on a transaction, effectively defining the permitted, or allowed, worktag relationships across the tenant. Option A, Maintain Worktag Usage, is incorrect because that task controls whether a worktag type is Required, Optional, Primary, or Not Used on a given business object, rather than which specific values are allowed in combination. Option B is incorrect because Maintain Custom Validations creates conditional messages for transactions, not allow-lists of worktag values. Option C is incorrect because Maintain Spend Categories manages the spend category hierarchy and its attributes, and has no role in defining allowed combinations of worktags across the tenant.

When a purchase item on a requisition line is already covered by an active, on-contract supplier agreement, Workday has sufficient information, including the supplier and negotiated pricing, to bypass the manual sourcing step that would otherwise be required for the buyer to assign a supplier. The Official Workday Pro Procure-to-Pay Guide explains that once the requisition business process completes approval for an on-contract item, the requisition line automatically becomes a purchase order line, since the contract has already established the supplier and pricing terms needed to generate the PO. Option A is incorrect because requisition lines are not sent to suppliers for review; supplier-facing communication occurs through purchase orders. Option B is incorrect because the defining characteristic of an on-contract item is that it does not require buyer sourcing, since the supplier is already determined by the contract. Option C is incorrect because the requisition line becomes a transactional purchase order line, not a catalog item, which is a setup record rather than an output of the requisition process.