PIEE Administration - Web Based Training
 

Each Application that comes on board in the PIEE Environment will have Application Level Administrators. They will administer things within each specific application.

They will NOT administer the PIEE Users, Roles, or Groups.

Exception to the Rule: If an application requires special approval of a role during activation which may not be performed by any PIEE Level Admins, a PMO must be established to handle that special case unless a currently established PMO can be designated for that task.


Administration Console Demos

Document Demo Doc Last Updated Notes
WAWF PMO - Enhanced WAWF Routing This is an overview of the Demo video. This is an overview of Enhanced WAWF Routing Demo document. May 2019

This demonstration will review the Accountable Property System of Record (APSR) extract sign-up process created to allow the PMO to designate which APSR should receive a copy of the APSR extracts (856_PSN and 861) by evaluating the following data elements:

  • Issuing Office
  • Admin Office
  • Pay Office
  • Ship To
  • Accept By
  • Inspect By
  • Mark For
  • MILSTRIP (prefix)
  • AAI
WAWF PMO - PCM XML Extract Overview This is an overview of the WAWF PMO - PCM XML Extract Overview changes Demo video. This is an overview of the WAWF PMO - PCM XML Extract Overview changes Demo document. August 2019 This is an overview of the PCM XML Extract Overview, which will be maintained by the WAWF PMO via the Admin Console.
WAWF PMO - PMO GPC Bank Information n/a This is an overview of WAWF PMO GPC Bank setup (PDF). n/a This is an overview of the steps required for the WAWF PMO to setup the GPC Bank and the GPC Banks Extract Sign up Process.
myInvoice Data Sharing myInvoice Data Sharing myInvoice Data Sharing July 2021

This overview describes the myInvoice Data Sharing feature. This functionality is to create a myInvoice file out of a secured server so customers are able to pull files whenever needed.

Data extracts will run at pre-determined intervals each morning and vendors will be able to upload the data into their system without accessing WAWF or myInvoice.

The directory path where the myInvoice file will be placed will be specified by the Level 2 Government Administrators. When a directory is set for a Group, a myInvoice file will be generated daily containing the Status and Date report for all CAGEs within that group, and within any groups below it.

Archiving Deactivated DODAACs n/a Archiving Deactivated DODAACs January 2020

This guide gives instructions for users to archive deactivated DoDAAC's.

The purpose of this was to provide the option to archive deactivated DoDAACs. This is applicable to Pay Office DoDAACs within the application.

Level 2 GAMs and PMO can deactivate a pay location code and have the option to automatically move the pay location code to the Archived DoDAACs group upon deactivation.

NOTE: Pay location codes will not be removed from the pay location codes tables because doing so would prevent users from registering as Pay Official View Only.

PMO can set a pay location code back to Active in case the pay location code was deactivated in error.

Only allows the Pay Official View Only role to be assigned/activated/maintained for deactivated Pay DODAACs.

Provides a mechanism whereby, when a Pay DoDAAC is deactivated, all non-View Only roles associated with that Pay DoDAAC are also archived.

Automate Contract Distribution/EDI 850 860 Routing Directory Update Process This presentation is an overview the Automate Contract Distribution / EDI 850 860 Routing Directory Update Process for Contractor Administrators (CAM). This presentation is an overview the Automate Contract Distribution / EDI 850 860 Routing Directory Update Process for Contractor Administrators (CAM). August 2021

This presentation is an overview the Automate Contract Distribution / EDI 850 860 Routing Directory Update Process for Contractor Administrators (CAM).


There are three major use cases the hierarchy needs to solve:

  1. Push a complete version of the hierarchy to an external system
  2. Push changes/ additions/ deletions made to the hierarchy to an external system
  3. Provide the Procurement/ Grant specific parts of the hierarchy as of a specific date

Due to size of the PIEE hierarchy, the best way to provide this as a service should be researched. The hierarchy should be made exportable as a csv with the 5.11.1 release. If this is truly the best way to provide the whole hierarchy, then no changes should be needed.

Changes are going to be made to the hierarchy (currently spanning 35K groups and 55K DoDAACs) nearly every day. PIEE shall determine the best way to provide these updates to external systems so they can stay in sync with changes made in PIEE.

Provide an API to distribute changes to the procurement and grants DoDAACs in the hierarchy.

  • The scope of this service is limited to the procurement DoDAAC changes.
  • Other DoDAACs, Pay, Acceptance, Ship To, etc. are NOT in scope for this change.

When a change does occur to a procurement DoDAAC in the PIEE hierarchy, make that change available to consumers of the service.

  • Changes include:
    • New Procurement/ Grant DoDAAC Added to Hierarchy
    • Procurement/ Grant DoDAAC is moved from one group to another

Provide the ability to export the Procurement hierarchy (Groups and DoDAACs that manage Procurement DoDAACs) as of a specific date. For Example:

  • System “X” requests a copy of the procurement hierarchy on Friday with an as of date of Monday
  • A new DoDAAC was added on Wednesday
  • The output should NOT include the DoDAAC that was added (or any other changes after 23:59 Monday)
Document Demo Doc Last Updated Notes
Procurement Hierarchy API Overview This is an overview of the Procurement Hierarchy API changes Demo video. This is an overview of the Procurement Hierarchy API changes Demo document. August 2018 This is an overview of the Procurement Hierarchy API changes.

The purpose of this ECP was for the new implementation of DAAS web-services that populate the DoDAAC and MAPAC data by utilizing the DoDAAF_Broadcast_ByDateRange and MAPAAC_Broadcast_ByDateRange web-services.

The implementation is implemented with separate web-service names: DODAACs_byDateTime, MAPAACs_byDateTime.