/
Requisition triggered wrong REQ Workflow Business Rule
Requisition triggered wrong REQ Workflow Business Rule
- Knowledge Assistant
Owned by Knowledge Assistant
Mar 31, 2023
1 min read
Analytics
Loading data...
Description of Issue
Requisition triggered REQ business rule with Type: SOA (GL Segment and Amount) for the wrong Department
Context
Munis
Requisitions
Workflow
Cause
New to functionality
Resolution
The GL Segments listed on the business rule were Department. GL Segment Department is unrelated to Purchasing Department that is specified on the REQ header. So the REQ did trigger the proper rule since it had a GL account on it that contained a Department segment which was included in the rule.
Additional Information
, multiple selections available,
Related content
REQ Workflow Being Sent to User with no Group By Option Set
REQ Workflow Being Sent to User with no Group By Option Set
More like this
Workflow rule with User Defined Fields not triggering as expected
Workflow rule with User Defined Fields not triggering as expected
More like this
Requisitions program not consistent with Requisition Entry in regards to default account logic
Requisitions program not consistent with Requisition Entry in regards to default account logic
More like this
Requisition Approvals are routing incorrectly for one fund code
Requisition Approvals are routing incorrectly for one fund code
More like this
Requisitions not pulling GL accounts only associated with segments set on Amounts by Segments contracts
Requisitions not pulling GL accounts only associated with segments set on Amounts by Segments contracts
More like this
What workflow process codes should a Requisition flagged as a pick ticket be expected to hit
What workflow process codes should a Requisition flagged as a pick ticket be expected to hit
More like this