Purchasing

The Purchasing module is the main module for managing requisitions and purchase orders.

General Process

graph TD;
    A[Requisition] --> B[Request for Quotation]
    B --> C
    A -->|direct order| C[Purchase Order]
    C --> D{Awaiting Delivery}
    D -->|not/partially received| C
    D -->|all received/<br>no further items expected| E[Close Purchase Order]

A purchase passes through up to three stages. Not every purchase uses all of them — where the supplier and the price are already settled, a requisition can become a purchase order directly.

Stage What happens Described under
Requisition Someone states what is needed. It is approved, and then either quotations are gathered or an order is placed straight away. RQ - Requisitions
Request for Quotation Suppliers are asked, their quotations are collected and compared, and one or more are chosen. RfQ - Request for Quotation
Purchase Order The order goes to the supplier, the goods are received, and the invoice is recorded. PO - Purchase Orders

Which folder a document sits in follows from its status, and the status changes by itself as the purchase proceeds — see Status changes for what moves where and when.

Two things run alongside all three stages: the Send Queue, which collects documents before they actually go out, and invoicing.

Transaction Numbers (TAN), Transaction Elements and Transaction Stages

Transaction number for each document is built by using a combination of abbreviations, identifiers and running numbers. In most cases the following structure will be used:
[stage]-[vessel]-[costdepartment]-[year]-[runningnumber]
[stage] can have the following values:

Abbr. Description
RQ Requesition
SQ service requisition
RfQ request for quotation
SfQ request for quotation (services)
PO purchase order
SO purchase order for services
   
[vessel] uses the three-letter abbreviation assigned to a vessel
[costdepartment] uses the abbreviation assigned to a cost department
[year] uses the last two digits of the current year
[runningnumber] The running number is automatically created when a new document is created.
Transactions created in office own running numbers with a fixed offset (vessel starts at ‘1’ - office startes at ‘701’).
If a vessel creates more than 700 transactions per year, a higher offset needs to be defined.

If a purchase order needs to be split for sending some order items to one supplier and remaining order items to another, usually the running number of the resulting purchase order TANs will be extended with A, B, C etc.. Examples

TAN Description
RQ-KOR-D-25-108 108th requisition created on ferry Kornatiy for deck department
PO-KRK-E-25-213 213th PO created for ferry KRK for engine department
PO-GAR-25-001-D 1st requisition for vessel Garitan for Department
Abbreviation (last place) Description
D Department Deck on board created
E Department Engine on board created
O Department Office on board created
OD Department Deck in Office created
OE Department Engine in Office created
OO Department Office in Office created