Sage ERP X3 Workflow.

Similar presentations

2 What do we mean by “X3 Workflow”An X3 workflow is a message.The message may suggest an action by the recipientA customer is placed on holdForward to crediting, cancel an order, …The message may require an action by the recipient(s)Purchase request requires signatures to be released to the suppliersApprove or reject the purchase requestThe message may be purely informationalA user logged on at this time and logged off at that timeIn the end, these are messages meant to support business processes in an expedited fashionLet’s look at these in detailBusiness workflows have a broader definition than the X3 workflow. The business workflows can cover multiple workflow components such asShipping from X3 through to UPS or FEDEX followed by customer deliver and customer payment involves several different workflow systems

3 1 An X3 Object Changes StateExample: A high value customer has their sales order go on holdState change on order to ‘Hold’It could be processed with the next days business but it is a significant customer and a larger order –Expedite the resolution via a workflowMost objects in X3 have the signaling required to support X3 workflows based on object state changes.New customer addedChange of an itemCreation of an invoiceReceiving a purchase orderAnd so onThis is a little technical but stay with me and I will give examples.

4 2 Recipients-change an X3 object state thru workflowExample: Purchase requests of a certain dollar value require specific approvals to be released to an orderCreate a purchase requestRequest the signature – approve/reject – track responsesThe signature message is inbound to X3While the signature functionality is dependent on the function, the workflow process is generally independent of the function –For example, the functionality related to signatures on sales quotes is different than the functionality related to purchase requestsBut the messaging aspect is the same – approve/rejectSignature workflowsA common problem when signatures do not work as expected.Sage ERP X3 6DescriptionPurchase order signature is not updated after Workflow reply.After a user has signed or rejected a PO using the link from the POHSIG Workflow , the signature flag status remains as "To be signed".CauseThe X3 Web Server generates a file corresponding to the user's answer in directory WRKRMTDIR.Then the AWRKSIG needs to be run to update the Quote, Order or Request.ResolutionCreate a recurring task for AWRKSIG under Usage, Batch server, Recurring task management.Once the response file is generated, the recurring task AWRKSIG will update the signature accordingly.

5 3 Report based on the current object stateExample: Alert customer and A/R when invoice of certain value goes past due by X daysIn this case, the state change is caused by ‘time’The way to signal these types of state changes is byRunning a workflow through all the concerned objects – in this case unpaid invoices.Send an to the customer with a copy of the invoice and notify accounts receivableExpediting paymentsThis type of workflow is relatively new to X3And had an unusual name attached to it -- ‘batch workflow’Meaning –these types of workflows could be setup to run in batchTime-based object state change events

6 Workflows From these 3 types of workflow messaging –Create several variants to specialize the entry of the workflow rulesThe workflow monitorThis is a way to view the workflow messaging and signatures that have occurred.The monitor could be under utilized. It is possible to track messages only through the monitor if that is appropriate.