Skip to main content
Skip table of contents

POPO (Print Purchase Order) | Services

POPO | Services

This is a process automation model for running and handling the "POPO" (likely "Print Purchase Order" for "Purchase Request"). It operates on scheduled intervals (daily, weekly, monthly), and the business scenario is to manage, run, and monitor the completion of PO printing jobs for PRs (Purchase Requests) in an approval process.


Workflow Steps

Key steps and logic:

  1. Starting Point

  • The workflow starts (activity "Start") when a Purchase Request has been approved (Status = "PR" and Approval Code = "APRV").

  1. Set System Variables ("System Variables")

  • The model gathers environment information such as:

    • The system URL

    • Connection name

    • Sets up initial dates for printing

  1. Run POPO Job

  • The workflow identifies the final approver for the PR. If the final approver is not available, a default value "BSI" is used.

  • A request is sent to the backend system to run the POPO job (print the purchase order).

  • The process constructs a special XML message with all necessary information and parameters (e.g., Purchase Order Date, Purchase Request Number, etc.).

  • The system waits for a response.

  1. Check Job Status

  • The workflow checks the backend system/database to determine if the POPO job is completed.

  • If not finished, it will wait and recheck periodically.

  • If completed, it checks the result to see if it succeeded or failed.

  1. Notifications

  • On Success: Sends a success notification email to a specified address (marouso.haniotis@sungardps.com) detailing that the POPO job was completed successfully, including the Job Number.

  • On Failure: Sends a failure notification email to the same address indicating the failure, including error details and the Job Number.

  1. End of Workflow

  • The process ends normally after notifications are sent.

  • There are additional "end" handlers for exceptional or error scenarios (e.g., when the workflow is rejected or cannot transition).

  1. Error Handling

  • When an error occurs, a notification is sent to TS_SUPPORT@oakland.k12.mi.us with a message including details of the error and the associated purchase request.


Key Variables Used

  • sysURL: System URL for use in requests.

  • sysConnName: System/database connection name.

  • POSeed: Sequence or identifier for POs, defaulted to "SEED".

  • PrintDate: Derived date for printing purposes (if before July uses July 1st of the current year, otherwise today's date).

  • JobStatus/JobCompletion: Track POPO job status for conditional handling and messaging.

  • IFASJobNumber: Stores the job number retrieved from the backend after the job is submitted.

  • JobLimit: Placeholder for limits.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.