Workday Workday-Procure-to-Pay - Workday Pro Procure-to-Pay Certification Exam

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.

Purchase order lines represent the agreed scope of goods or services to be delivered and billed, and closing a line signals that no further receiving or invoicing activity is expected, which can also affect budget checks and encumbrance balances. The Official Workday Pro Procure-to-Pay Guide indicates that the appropriate time to close a PO line is once all goods or services on that line have been fully received and fully invoiced, confirming that the line's lifecycle is complete and no remaining activity is anticipated. Option A is incorrect because focusing on whether the supplier invoice has been paid ties the closure decision to the payment process rather than to the completeness of receiving and invoicing, which are the relevant triggers. Option C is incorrect because closing a line immediately after approval would prevent any receiving or invoicing from ever occurring against that line, which contradicts its purpose. Option D is incorrect because tying line closure strictly to fiscal year-end is arbitrary and could result in closing incomplete lines prematurely or leaving completed lines open unnecessarily.

In this scenario, every procurement item being loaded must be identified as Office Supplies, which represents the single, required classification that every purchase item in Workday must carry through its spend category assignment. The Official Workday Pro Procure-to-Pay Guide explains that fulfilling this required association means creating a spend category named Office Supplies and assigning it to these items, since spend category is the mandatory, primary classification field on every purchase item. Option B is incorrect because purchase groups provide additional, optional grouping for reporting but are not the required, primary classification mechanism that spend category represents. Option C is incorrect because item tags, or related worktags, are used for additional, non-required classifications, such as the General Use or Promotional categorizations described in the related scenario, not for the mandatory primary classification. Option D is incorrect because alternate item identifiers store supplementary reference codes, such as part numbers, and have no role in fulfilling a categorical classification requirement like Office Supplies.

Workday categorizes procurement at a high level into Goods and Services to support different transactional behaviors, particularly around receiving, since physical items typically require quantity-based confirmation of delivery while services do not. The Official Workday Pro Procure-to-Pay Guide identifies Goods as the procurement type used to track spend for physical, tangible items, enabling the standard requisition, purchase order, and receiving workflow appropriate for inventory-type purchases. Option A is incorrect because Project-based Services is used for tracking billable, project-related service work rather than physical items, and follows a different tracking model tied to project worktags. Option C is incorrect because Matching is not a procurement type at all; it refers to the three-way matching process used to reconcile supplier invoices against purchase orders and receipts. Option D is incorrect because the general Service procurement type covers intangible deliverables such as labor or consulting, which typically do not involve the physical receipt of goods in the same manner as items procured under the Goods type.

Purchase items can carry additional reference codes beyond their standard Workday item identifier, which is useful when organizations need to track external identifiers, such as manufacturer part numbers, and associate suppliers with specific identifier values to support sourcing decisions and supplier prioritization. The Official Workday Pro Procure-to-Pay Guide identifies Alternate Item Identifiers configured on the purchase item as the correct setup for tracking manufacturer part numbers and linking suppliers to those identifiers, since this is where item-specific identifier and supplier association data is maintained directly on the item record. Option A is incorrect because spend categories classify broad groups of items for reporting and accounting purposes and do not hold item-specific identifiers like manufacturer part numbers. Option B is incorrect because configuring identifiers on suppliers would not tie a specific manufacturer part number to a specific purchase item in a structured, reusable way. Option C is incorrect because supplier contracts govern pricing and contractual terms and are not the storage location for alternate item identifier data on procurement items.

Supplier contracts in Workday are formal, approved agreements that govern terms such as pricing, dates, and total contract amount with a supplier. Once a contract reaches Approved status, its terms are locked and cannot simply be overwritten through direct editing. Per the Official Workday Pro Procure-to-Pay Guide, the correct mechanism for changing approved contract data, such as the contract amount, is to initiate a Create Contract Amendment business process. The amendment creates a new version of the contract with the corrected amount while preserving the original document and a full audit trail of the change, including any required re-approval. Option A is incorrect because catalogs hold pricing for items, not the overall contract amount, and changing a catalog does not alter the contract record itself. Option B is incorrect because an attachment is purely supplementary documentation; it does not update the actual data field driving contract value or downstream processing. Option C is incorrect because invoices are transactional documents created against POs or contracts during the procure-to-pay cycle and cannot be used to replace or modify a contract record.