Wiki source code of 18.1 Plan Types
Last modified by Admin User on 2023/06/30 10:26
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | There are 5 types of plan. Each one will route specific documents. | ||
2 | |||
3 | **~1. Requisition Approval Plans**: these plans __**route the whole Requisition**__ through a chain of approval steps when it is submitted. At the end of the approval steps the requisition is split into individual purchase orders – one for each supplier. The individual purchase orders are then available for processing (optionally) through a Purchase Order Approval Plan. PECOS P2P therefore processes Requisitions through a Requisition Plan **before** it routes orders through an Order Plan. Requisition Plans allow the Approvers to do four things during the approval process: approve, edit and approve, reject or edit and reject. | ||
4 | |||
5 | //One// Requisition Plan may be assigned to each user through an Approval Rule Group. | ||
6 | |||
7 | **2. Purchase Order Approval Plans**: these plans __**route individual Purchase Orders**__ through a chain of approval steps. A Purchase Order Plan will be followed **after** a Requisition Plan. If a Requisition Plan is not assigned to a user, after submitting the Requisition PECOS P2P will immediately create the individual Purchase Orders and route them through the Purchase Order Plan. At the end of the approval steps the Purchase Orders are transmitted electronically to suppliers. | ||
8 | |||
9 | //One// Purchase Order Plan may be assigned to each user through an Approval Rule Group. | ||
10 | |||
11 | **Examples:** | ||
12 | |||
13 | **If both a requisition type plan and a purchase order type plan is assigned**. PECOS P2P will firstly route the whole requisition through the requisition plan and upon completion, create purchase orders. The purchase orders will then be routed through the purchase order plan and upon completion be transmitted to the suppliers. | ||
14 | |||
15 | **If only a requisition plan is assigned.** PECOS P2P will route the whole requisition through the requisition plan and upon completion, create purchase orders and transmit them to suppliers. | ||
16 | |||
17 | **If only a purchase order plan is assigned.** When submitted, the requisition will be split into purchase orders and the individual orders routed through the purchase order plan. When complete the orders will be transmitted to suppliers. | ||
18 | |||
19 | **3. Change Order Approval Plans:** these plans are used to __**route changed purchase orders**__ for approval. The change order may or may not be re-transmitted to the supplier. These plans are not used to route original documents and are not mandatory. | ||
20 | |||
21 | //One //Change Order Plan may be assigned to each user through an Approval Rule Group. | ||
22 | |||
23 | **4.** **Receipt Approval Plans:** these plans are used to __**route the receipt object**__ for multi-stage receipting and quantitative or qualitative review. Receipt workflow improves the receipting process by providing a means to resolve delivery discrepancies (prior to the invoice and matching process) and better manage simple two stage receipting. | ||
24 | |||
25 | //One// Receipt Plan may be assigned to each user through an Approval Rule Group. | ||
26 | |||
27 | **5.** **Invoice Settlement Approval Plans:** these plans are used to __**route all system processed invoices**__ whether processed against a PECOS P2P purchase order or entered as a Manual Invoice. Invoices will follow settlement approval only after financial matching has been run. Rules can be written to route only those invoices that require approval – for example based on certain matching statuses. | ||
28 | |||
29 | //One //Invoice Settlement Plan may be assigned to each user through an Approval Rule Group. Assignment is NOT mandatory and if no plan is assigned, invoice approval will not be performed. |