Post-activation validation checklist
After Multicurrency is activated and workflow patching is complete, validate that currency-related behavior works as expected.
You do not need to review every workflow from scratch. Start by validating standard user-facing behavior. Review custom workflows only if your environment uses them.
Validate standard behavior
-
Confirm that Currency Code appears on the expected full forms for Purchase Orders, Assets, Vendors, Consumables, Contracts, and Service Catalog Items.
-
Confirm that create actions for those objects include Currency Code and that it is prefilled with the default currency.
-
Confirm that step actions containing monetary fields also include Currency Code before the monetary field.
-
Confirm that Purchase Order's Vendor selection is filtered by the current Currency Code.
-
Confirm that PO Items, Invoices, Invoice Items, and Vendor Products inherit currency from their parent object.
-
Confirm that monetary values are displayed with the expected symbol or ISO currency code in full forms, action forms, read-only forms, and grids.
Review customizations (only if used)
-
If your environment uses customized worklfows or virtual monetary fields, verify that currency context is handled as expected.
-
If your environment uses custom UDFs or modified financial workflows, verify whether Currency Code needs to be added or referenced in those customizations.
For example, if your environment has a Purchase Order workflow that creates line items from a vendor catalog, validate that a PO in JPY only exposes vendors that use JPY and catalog items priced in JPY.
This checklist is focused on currency-related behavior introduced by activation and patching.