APSD - PAPS

APSD is a time tracking and expenses tracking system that connects to CRSM (Oracle Financing) in order to generate invoices. The project is currently at iteration 1 - replacing SCRAM with APSD.

System Profile

Environment Access Information

NAPA-SNAPA API

Azure Resources

System Overview

The Aeronautical Products Service Delivery Database is used by identified Transport Canada Civil Aviation staff to enter their daily hours against various tasks. These tasks includes hourly certification projects where the data in SCRAM is then used to invoice clients for time spent on individual aircraft certification projects. Data in SCRAM is then submitted to the Activity Reporting and Standards System (ARASS) but its also used for NOP and IPR planning and reporting processes.

Roles

Engineers are the lowest permission level - they can only see Timesheets and Service Requests. They can submit their own timesheets and create service requests that are based on NAPA projects.

Managers can do what engineers can, plus they can approve timesheets for those under them. They can also view invoices and do the first-level approval of them.

Cost Recovery Officers can view all 4 sections (Timesheets, Service Requests, Expenses, Invoices). They can only create timesheets, not approve them for others. They can also create service requests for projects that are not linked to a NAPA project. They can create expenses and invoices.

Invoice Manager has the most access to the app. They are able to do everything a cost recovery officer can, except for submitting an expense. They can also act as a manager and approve timesheets. They can also approve expenses and do both first and second-level approvals for invoices.

Admin App (Model-Driven App)

The APSD-PAPS Admin app can be used to view all the data in the system. There is also an extra module that give super-users extra functionalities. Access to these modules is granted by the developers (by sharing the “APSD-PAPS User Management“ canvas app) and requires the approval of the Product Owner.

Note: Only users with the Cost Recovery Officer or Invoice Manager role are able to access the admin app. All others will get the following error:

Open

Extra Module (Manage Users)

Manage Users

Allows a user to add or remove APSD access for a user. To add a user, the user’s email and role must be provided (manager’s email is optional).

Open

Note: A user’s manager can be edited through the normal Users view in the Admin section by clicking on the user profile and searching for the manager in the manager field.

Edit Approved Time Entries [REMOVED]

Allows a user to edit already approved time entries by searching for the user and the timesheet. The number of hours, billable, overtime, and comments for a specific time entry can be modified.

Old Wiki: https://tcmarin.atlassian.net/wiki/spaces/APCR

Invoices

In order to submit an invoice in APSD to Oracle (2nd level approval), the user must also be granted permissions in Oracle Finance. Requests for access can be sent to Leigh Ashe.

Invoices are submitted using SPAPI.invoicecontrollervSubmitToOracle endpoint. APSD currently does not pass any value over in the optional EmailAddresses parameter. Once Oracle receives the invoice information from APSD, an email is sent to the person who originally created the invoice in APSD (RequestorNetworkId in SPAPI) with a copy of the official Oracle Finance invoice to confirm that the invoice has been created (example below).

eBilling emails (for external customers) are only generated if the customer is registered for eBilling. If they are registered, the Oracle invoice is sent to the registered customer’s (person) and customer contact’s (organization) email addresses. The submitter will also receive an email with a subject line like ‘eBilling customer/ Invoice intentionally blank/ SR# 208016 (ref:4042) - Invoice# 4952221000500 - Cli', indicating that the client is setup for eBilling and will receive the invoice via the eBilling process. The PDF invoice attachment is blank in these cases to avoid sending out duplicate invoices. On the other hand, if the client is not registered for eBilling, then it is the billing clerk’s responsibility to send out the invoice to the client.

Open

Iteration 1 Diagram

The following iterations were planned out at the beginning of the project: RDIMS #17272924

Data Model Diagram

Please note that ap_TimeEntry_ap_ServiceRequest entity has a note that reads:

This table is an N:N relationship table generated automatically, It is not visible to us. We CAN NOT add any columns to that table.

Open

Process Diagrams

SA&A Documents

CRSM API Security Documents