Purchase orders

When the AP Workflow is enabled for an organization, you can configure how the Line Pairing Correction, Line Pairing Exception, and Exception activities are routed during production.

These activities can be routed to the requisitioner or creator of the PO in the ERP system. Tungsten AP Agility supports importing PO creators and requisitioners as part of the PO header data.

Selecting the PO Requisitioner or the PO Creator routes the activity to a corresponding user in the AP PO Processors resource group. That user must then match with a user from the ERP that is included in the PO header data.

To avoid routing activities to Tungsten TotalAgility users that have no access to AP Agility, it is necessary to add all users that are allowed to process PO-related activities to the AP PO Processors group created in the AP Agility category. The search for matches must be for members of that group only.

AP Agility supports matching by full name, user name, and by email address. A match by full name may not produce unique results if a company has multiple employees with the same name. A match is only accepted if the result is unique. If a name cannot be found or it exists twice, the match is rejected and the default resource for the activity is used.

If no unique match or no match at all is found, the default resource for the activity is used.

These settings are overridden if any of the following business rules are configured.

IP Custom Assign LPR Correction Resource
AP Custom Assign Line Pairing Exception Resource
AP Custom Assign Exception Resource