SkySuite Wiki - User contributions [en-gb]

Station Index

2026-03-27T11:09:32Z

Betsy:

<roles>SLXGLOBALADMIN,SLXLOCALADMIN,SLXOPERATIONAL,AIRLINEADMIN,AIRLINEOPS</roles>

{{Tips and tricks}}

__TOC__

=Summary=
A station is an Organization that provides flight or passenger services to an airline at an airport. This includes caterers, cabin cleaners, and other ground handling service providers as well as passenger lounges and ticketing agencies. In order for a Station record to exist, there must first be an Organization and OrganizationSite to which that Station can be linked.

=Create organization=
Organization refers to the company as a whole e.g. Lufthansa, Gate Group, or Coca-Cola, underneath the Organization there can be multiple OrganizationSites (see below). In order to be linked to a Station, the Organization type must be "Caterer/Service Provider".
First, please check if the Organization already exists in SkyLog. Here you can find the list of all Organizations [[https://rsprod.skylogportal.com/Organization'''link''']]. If the Organization already exists please move to the next step. Organizations are centrally controlled and maintained to avoid duplicate organizations being created across multiple operations, therefore if the Organization does not exist contact a Global Administrator or raise a support request. [[http://wiki.skylogportal.com/index.php?title=Organization_Index '''For more details about Organizations click here''']]

=Organization Sites=
An Organization site represents a physical location from which the Organization operates, the site record contains the physical address of the location as well as the main site contact details and the timezone of that site. The site record must exist before you can create a Station record or for that matter any other supply chain participant type such as AirlineSupplier, Warehouse, etc. Firstly Please check if a site is already created in SkyLog with the same address and linked to the same Organization, it is important not to duplicate organization sites. [[http://wiki.skylogportal.com/index.php?title=OrganizationSite_Index '''For more details about Organization Sites click here''']]

=Stations=
The station setup contains specifications of that station's operations such as the frequency it should report inventory of airline-owned items and a list (StationItems) of the airline-owned items it needs to provide the services to the airline. Against each item, we record the par levels e.g. how many days of inventory to hold, the frequency of replenishment, the replenishment source and lead time, etc. SkyLog allows you to define at the station level many parameters to customize stations processes. For example, automatic stock count approvals, different ways of RMA management, and the level of automation within process flows.

==Stations creation==
To create a station record a few things are required to be confirmed: station setup, Supply sources,
You can start creating a new station by going to Reference Data/Airline Participants/Stations

[[File:CreateStationRef.png]]

SkyLog allows advanced customization of the station processes. To deliver the most productive setup please consult the guide below which explains each customization option on the page


<table width="0">
<tr>
<td width="170">
<p><strong>Field</strong></p>
</td>
<td width="444">
<p><strong>Description</strong></p>
</td>
</tr>
<tr>
<td width="170">
<p>Station Site</p>
</td>
<td width="444">
<p>Link to Organization site. It is the source of the Station address that is printed on invoices, transport bills and communicated to 3rd parties</p>
</td>
</tr>
<tr>
<td width="170">
<p>Airport</p>
</td>
<td width="444">
<p>Every station must have link to the airport it services. If a single OrganizationSite serves two or more airports then you should create a station record for each airport served.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Service Type</p>
</td>
<td width="444">
<p>Assign relevant station type, e.g. "Caterer", "Airport Lounge",</p>
</td>
</tr>
<tr>
<td width="170">
<p>Active</p>
</td>
<td width="444">
<p>It is a yes /no field that can only be active once all the requirements have been sent up.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Valid From</p>
</td>
<td width="444">
<p>Date of start of operations.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Valid To</p>
</td>
<td width="444">
<p>Date of station closure. If not known or open ended leave blank.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Station Provisioning Manager</p>
</td>
<td width="444">
<p>The person who will be responsible for the provisioning/replenishment of goods for the station (i.e. who will approve requisition requests, inventory reports, etc.). This will be a person within the Airline or the Airline's 3rd party Control Tower</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="444">
<p>The person to be assigned (from users registered in SkyLog) who will be responsible for stock counts, this will be someone within the organization of the Station. The selected person will be the recipient of related notifications such as reminders to count, shipment notifications and various escalations/alerts regarding Station Provisioning and Inventory Management</p>
</td>
</tr>
<tr>
<td width="170">
<p>Is Station Independent from Skylog?</p>
</td>
<td width="444">
<p>Station exists within Skylog but is not expected to have any interactions via the UI (Portal)with Skylog – if the station will raise requisitions in SkyLog and/or be expected to submit inventory reports then this setting should always be set as 'No'. Typically this will only be set to 'Yes' if the Station uses their own systems to submit inventory counts and place requisitions and there is an interface between that system and SkyLog</p>
</td>
</tr>
<tr>
<td width="170">
<p>Automatically Generate Requisitions?</p>
</td>
<td width="444">
<p>Yes/No field will either allow (if yes) to generate automatic requisitions after a stock count, via schedule or even manually. If no, only manual orders are allowed to be placed by station. Setting to No is more common for lounges.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Non Orderable Items in Requisitions</p>
</td>
<td width="444">
<p>Typically, Skylog only permits 'current' materials to be requisitioned. However, some users prefer to see all materials on the requisition so that they can make informed judgements, including temporary materials which may have been supplied in the past in place of a regular material (e.g. substitute materials where the station par level status = "Temp/Sub"). If the station wishes to see such temporary/substitute items on requisitions then this configuration flag should be set as 'Yes', otherwise, set as 'No'. This setting is often enabled for stations for SAP-Centric clients.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Generate Automatic Requisitions Upon Count Approval</p>
</td>
<td width="444">
<p>This can only be set to "Yes" if "Will Requisitions Be Automatically Generated for This Station?" is also set to "Yes". If set as "Yes" then Skylog will create a new automatic-requisition when an inventory count is approved - this relies upon station par levels being configured for event-driven requisitioning though. If you would prefer that automatic-requisitions are triggered for this station based upon an automatic schedule cycle* then this setting should be configured as "No". * - If you do wish to trigger automatic requisitions based upon an automatic schedule then "Will Requisitions Be Automatically Generated For This Station?" should be set as "Yes" and each material to be included (for automatic requisitioning) should be set as Schedule-driven requisitioning - if set as such, you will be prompted to provide a next requisition trigger date; such configuration is achieved via the station par levels for this station.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Keep Back Orders?</p>
</td>
<td width="444">
<p>When a new requisition is processed should Skylog retain existing back-orders? If Skylog should discard open back-orders upon processing a new requisition, set this configuration flag to 'No'. Otherwise, if Skylog should leave the decision as to whether a back-order is cancelled or processed to a member of the operational team then set this configuration flag to 'Yes'.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Confirm RMA Shipments?</p>
</td>
<td width="444">
<p>If the configuration flag is set as 'No' it is not necessary for the station to confirm the despatch for a RMA. If the configuration flag is set as 'Yes' then the station returning the goods must confirm the despatch.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Automatic Requisition Negative Numbers Default to Zero</p>
</td>
<td width="444">
<p>If SkySuite believes that the station has too much stock, it will suggest a negative order quantity in the requisition. If the station does not wish to return such goods, then the requested quantity should be set as zero – meaning that the line/position will be ignored by SkySuite. With this configuration flag set as 'Yes', Skylog will automatically set the requested number from a negative value to zero. If this configuration is set as 'No' then the requested quantity will always default to suggested order quantity (even if the suggested order quantity is less than zero). For stations where the autorequisitions are generated based on days of the week, is recommended to set this flag to 'Yes', otherwise SkySuite will include the quantity to return in the calculation of the suggested quantities, leading to additional stock being suggested to be sent to the station.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Enforce RMA Qty</p>
</td>
<td width="444">
<p>If Station is allowed to issue a RMA for parts they haven't ordered from inbound flights etc. then set to 'No'. If 'Yes', the Station will be allowed to return only that stock qty that they counted in the last stock count.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Receipt Configuration</p>
</td>
<td width="444">
<p>The default expectation is that stations will always receipt-confirm all inbound transactions (station orders, direct purchase orders, station-to-station transfers etc.). If however it is permitted for some transactions to be 'automatically' received (i.e. without user interaction), then this can be configured via this setting.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Default Requisition Confirmed Qty to Zero</p>
</td>
<td width="444">
<p>If the flag is set to 'No', SkySuite will pre-populate requested quantity to match the suggested quantity. If the flag is set to "Yes", SkySuite will pre-populate the requested quantity with zero, and the station provisioner will need to either enter manually the quantity to approve, or select the option to populate that for all lines. For stations where the autorequisitions are generated based on days of the week, is recommended to set this flag to 'No', otherwise SkySuite will not include the quantity on automated requisitions awaiting review or approval, leading to additional stock being suggested to be sent to the station.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Should Skylog Consider External Target Quantity Data in Core Functions?</p>
</td>
<td width="444">
<p>Specifies whether or not external target quantities, commonly known as FOS + BUS values (supplied to Skylog via uploaded SCA files), will be used by Skylog to affect various Skylog functions. Such functions would include the calculation of the suggested order quantity figure for automatically generated requisitions. The target values will also be used to determine if a material on a submitted inventory count would be flagged as a query or not. If this setting is set as 'No' then Skylog will use the traditional formulas (which won't use target quantity values). If this setting is set as 'Yes', Skylog will consider the target quantities in its calculations.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Station Depot</p>
</td>
<td width="444">
<p>A unique code that identifies the specific station (unique across all airlines).</p>
</td>
</tr>
<tr>
<td width="170">
<p>Station Loading Code</p>
</td>
<td width="444">
<p>An alternate station identifying code which is used by third-party systems to identify a specific station. This code would be used in data files originating from those partner-systems, such as the Service Rules interface EDI. If this interface is used by the operation associated with the station then the uploading and offloading stations identified within the service rules data must correspond to the Station Loading Codes held by Skylog.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Customer Code</p>
</td>
<td width="444">
<p>This is an optional property and should be left blank/empty, it serves a special purpose for a handful of specific catering facilities but has no relevance for the majority of stations and thus can be ignored.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Default Loading</p>
</td>
<td width="444">
<p>This is a mandatory field that may be used when SkyLog generates a forecast for the airline; it can be set to Yes or No (true or false) and it will be used if there is insufficient pre-set data or rules to determine the loading or unloading station. The SSIM (Flight Schedule) file that we receive and process for the airline only tells us the departure and arrival ports for each flight in the schedule. Some ports will be setup with multiple catering stations at a given port and we will determine which station loads and unloads the content of any provisioning code based on pre-set data in the provisioning rule and/or exchange rules. However if there is insufficient pre-set data/exchange rules to tell us which station will perform the loading/unloading then the forecast will use the default station which is determined by this field. Importantly, there can only be a SINGLE default catering station per combination of Port & Airline (additionally, in case it’s not obvious, the station must be active for the default loading to be set to Yes).</p>
</td>
</tr>
<tr>
<td width="170">
<p>GL Cost Centre Code</p>
</td>
<td width="444">
<p>An alternate station identifying code which is used by third-party systems to identify a specific station. This code would be used in data files originating from those partner-systems, such as the Service Rules. GL Cost Centre field links financial data with customer financial systems. In case a new GL Cost Centre is required to be set up please follow the link for guidance how to [[http://wiki.skylogportal.com/?title=Station_CostCentreCategoryIndex'''link''']].</p>
</td>
</tr>
</table>

=Supply Source=
Supply sources define which warehouses will be supplying stations with goods and which modes of transport are used. It is possible for stations to be supplied by multiple warehouses and this could be defined at the item level in Station Item / Par Level tables. Multiple modes of transport could be assigned for each supplying warehouse with different transportation and handling lead times and a priority ranking to determine the preferred mode of transport.

The Supply Sources button is found in the '''Reference Data/Supply Chain Participants/Stations'''. Select desired station by clicking on [[File:Edit.png]]. At the bottom of the new page will be [[File:SupplySourceButton]].

==Add Warehouse==
To add a warehouse that will be supplying station:
<ol>
<li>Select [[File:PlusPlus.png]]</li>

<li>Select Warehouse</li>

[[File:SelectWarehouse.png]]

<li>Set as active </li>

[[File:SetActiveWarehouse.png]]
</ol>

==Add Transport Methods==
<ol>
<li>Under the Warehouse-Station Link, next to set up warehouse select [[File:Expand.png]] to expand the field as per below and select [[File:PlusPlus.png]] to add mode of transport from selected warehouse.</li>

[[File:AddModeOfTransport.png |1200px|]]

<li>Select accordingly
<ol style="list-style-type: lower-alpha;">
<li>Method of transport from drop down list. Note that there are more options then seen on the screen, use scrolling down option to see all modes of transport available.</li>

<li>Preparation time – days it takes the warehouse to pick and pack.</li>

<li>Transport duration – days it takes from dispatch until station receipt.</li>

<li>Rank – priority / default option.</li>
</ol>
</ol>

[[File:AddModeOfTransportSpec.png]]

Complete table should look like this.

[[File:CompleteTransprotSetup.png |1200px|]]

=Station Count Category=
Station count categories define which items are counted by the Station and how often they are counted. It also allows you to set the tolerances between expected and actual count quantities (count variances) at which a count line is set to "Query". The level of automation in the count and approval process and also be set – some counts can be set up as auto accepted after they are submitted, a useful feature for stations like lounges with little turnover. Station Count Category can be found under '''Daily Activities/Inventory Counts/Station Count Categories'''.

<ol>
<li>Select [[File:PlusPlus.png]] in the Station Count Categories page </li>

<li>Select station requiring new station count category</li>

[[File:SelectStationRequiringNewStationCountCategory.png]]

{| class="wikitable" style="width:80%"
|-
! Field
! Sample
! Description
|-
!Count Category Description
|Full
|Description of the count category. The station could have multiple counts with different parts under each, so naming of the count category is useful to avoid confusions. A typical example might be to set up a count category called "Major Equipment" for all technical equipment such as Trolleys/carts or to have a category "Disposables" for all disposable items.
|-
!Count Schedule Option
|Automatic Schedule
|There are 3 options "Automatic Schedule" (repeats based on provided frequencies), "Manual Schedule" (follows manual dates listed in manual schedule table on the bottom of the page) and "None" (stock counts generated only manually)
|-
!Automatic Schedule Options
|Specific Day/s of the Week
|You can pick between days of the week or days of the month, days of the week or days of the month [that new inventory counts will be due]
|-
!Specific Day/s of the Week or Month
| --
|tick/specify days when stock count should be triggered; if specifying days of the month, each must be comma-separated. Note: you can not specify consecutive days; there has to be at least one day's gap between inventory counts [it's not allowed to instruct a station to perform a new count each and every day
|-
!Weeks Between Counts
|1
|Number of weeks between counts (if 'Automatic Schedule Options' = "Specific Days of the week", rather than Specific Days of the Month)
|-
!Notify Days
|3
|Number of days the stock count will be generated before the expected count date, the station will get an email notification at when the count is generated and then has the notify days to prepare for the count.
|-
!Next Count Generation Date
|September 28, 2023
|Select next/first stock date for a count to be scheduled. This date is automatically updated each time a count is generated but a user can re-sync the schedule by editing the date
|-
!Value Tolerance for Count Variances
|100
|Not mandatory, select variances in value per line to tolerate as ok. Meaning if, for example, there is a 100 GBP tolerance and the discrepancy from the expected stock count is 99 GBP, the count will appear as ok. Different tolerance levels can also be set at the item level and the count category tolerance will only apply if there is no item-level tolerance defined.
|-
!% Quantity Tolerance for Count Variances
|10
|Not mandatory, select variance in quantity % per line to be tolerated from the expected count. Meaning if, for example, there is a 10% tolerance and the discrepancy from the expected stock count is 5%, it will not appear as a query. Different tolerance levels can also be set at the item level and the count category tolerance will only apply if there is no item-level tolerance defined.
|-
!Person Responsible for Counts
| --
|Select the person (out of those assigned to this station/organization site), that will be responsible for counts and will be receiving notifications related to it. Leave this field blank if you would prefer alerts to be sent to ALL points of contact associated with the station. If no point of contact can be found, alerts will be sent to the station provisioning manager (in lieu of being sent to caterer / groundhandlers with links to the station).
|-
!Include Floating Qty
|Yes
|Float stock represents the stock that is in the inbound, outbound, and production areas of the station often known as "WIP" (Work in Progress), it does not include stock that is in a storeroom/warehouse area of the Station. If selected "Yes", columns will appear on the stock count page to count both Backup stock and Float stock and report both quantities separately. Backup stock is the stock in a storeroom/warehouse area). If selected "No" then only the Backup stock is expected to be counted and reported.
|-
!Include Breakages
|No
|If yes, will add a column for breakages to be filled by the Station during the stock count. This reflects any losses at the station since the previous count as a result of breaking/damaging products (to an extent they can no longer be used) - e.g. cracked glass, chipped chinaware, etc.
|-
!Attach Count Sheet File When Notifying Station
|Yes
|Advise selecting Yes, which will attach an excel file to the notification email, that when filled could be uploaded to SkyLog for submission. It is a good tool to avoid manual entries in the portal. Note, for new airlines, additional setup is required to enable this - please raise a support ticket and ask for this option to be enabled though.
|-
!Consumption Trend Span (Days)
|180
|Default value is 180, and if left blank it will generate a value of 180 days. This value is used in the calculation of the "smooth" average past daily consumption, if set to 180 it will look at the last 180 days when calculating the daily average but it can be set longer or shorter.
|-
!Generate Automatic Requisitions Upon Count Approval
|Yes
|If Yes, the system will generate an automatic requisition after the stock count is approved (although this is dependent upon the station itself being configured to support automatic requisitioning too).
|-
!Include All Items in Automatic Requisitions
|Yes
|Yes, will include all active items in any auto requisition (even if the suggested order is 0)
|-
!Delay (Hours) For Automatic Requisition Generation
|0
|This is the number of hours after count approval before which any automatically triggered requisition should be triggered
|-
!Include All Station Par Levels In Counts
|No
|Only select YES for "special" counts which are additional to the regular counting cycle, such as a coordinated global stocktake. Thus for regular counts, this setting should be set as NO. Only count categories where this configuration setting is set as NO will appear as a valid option when defining a default count category (See 'Station Defaults' section below).
|-
!Update Station Par Levels
|Yes
|Only select NO for "special" counts which are additional to the regular counting cycle, such as a coordinated global stocktake. So for regular counts, this should be set as YES. Only count categories where this configuration setting is set as YES will appear as a valid option when defining a default count category (See 'Station Defaults' section below). When set as YES, assuming that the count is approved, the approved inventory figures will be copied across to the station par levels and will be used as the starting inventory figures for the next iteration of the count. Additionally, with this configuration flag set as YES, it will also mean that average consumption figures are calculated and may have a bearing on RMA functionality too (depending on station-level configuration tho).
|-
!Count Auto Approval Option
|Review Required
|
* Review Required - will request that the Station Manager does a full review of every stock count submitted by the Station for this count category, even if there are no lines on the count that are flagged as outside of tolerance

* Auto-Approve When No Queries - stock count will be automatically approved by the system if all count lines are within the defined tolerances (i.e. no queries were generated by the system.

* Auto-Approve Regardless - this will mean that even if there are lines on the count that are flagged as being outside of tolerance, the count will automatically approve - the station provisioning manager will not be alerted and will not need to review the count, thus there can be no re-count process.

* Approval NOT Required - only select this option for "special" counts which are additional to the regular counting cycle, such as a co-ordinated global stocktake

<b>NOTE:</b> You can only select the 'Approval NOT Required' option when the 'Update Station Par Levels' flag is set to 'No'.

<b>IMPORTANT:</b> Be warned, this is the final configuration flag when you add or edit a station count category record, if you select this option, you will find that it will toggle (update) the settings for "Include ALL Station Par Levels" and "Update Station Par Levels" - so you may find that your resultant count category is not as you had originally specified it because of this final setting.

If you want regular (standard) counts to always sail through, skipping the approval step then choose the "Auto-Approve Regardless" option instead; thus, the station provisioning manager won't be notified to review the count when the caterer has submitted their inventory figures.
|-
|}
</ol>

==Sample of complete Station Count Category setup==
[[File:SampleCategoryCount.png]]

=Station Defaults=
Station defaults are used whenever doing a mass creation of Station Item records, for example - when copying the items from one station to another, or when the forecasting system, as a result of loading or flight schedule changes, creates new items for that station. The criteria in station defaults will be applied to all items copied or created from forecasting but can be edited item by item as required.
<ol>
<li>In the Stations page (Reference data/Supply Chain Participants/Stations) select a station in edit mode. </li>

<li>Fill Station Default table accordingly. Table with descriptions is presented below</li>


<table width="0">
<tr>
<td width="217">
<p><strong>Field</strong></p>
</td>
<td width="81">
<p><strong>Sample</strong></p>
</td>
<td width="267">
<p><strong>Description</strong></p>
</td>
</tr>
<tr>
<td width="217">
<p>Transport Method/Duration (Days)</p>
</td>
<td width="81">
<p> </p>
</td>
<td width="267">
<p>Select default method of transport</p>
</td>
</tr>
<tr>
<td width="217">
<p> </p>
</td>
<td width="81">
<p> </p>
</td>
<td width="267">
<p> </p>
</td>
</tr>
<tr>
<td width="217">
<p>Security Stock (Days)</p>
</td>
<td width="81">
<p>14</p>
</td>
<td width="267">
<p>Security / safety stock of the item to be held at the station in days</p>
</td>
</tr>
<tr>
<td width="217">
<p>Days Needed for Preparation</p>
</td>
<td width="81">
<p>1</p>
</td>
<td width="267">
<p>This is the number of days needed to get stock prepared for for a flight.</p>
</td>
</tr>
<tr>
<td width="217">
<p>Days Needed to Recycle</p>
</td>
<td width="81">
<p>1</p>
</td>
<td width="267">
<p>This is the number of days needed to recycle stock from inbound flights to be ready for re-use e.g. the separation & and washing time</p>
</td>
</tr>
<tr>
<td width="217">
<p>Specify Order Frequency Type</p>
</td>
<td width="81">
<p> </p>
</td>
<td width="267">
<p>Days between delivery/orders or days of the week.</p>
</td>
</tr>
<tr>
<td width="217">
<p>Days Between Delivery/Orders</p>
</td>
<td width="81">
<p>7</p>
</td>
<td width="267">
<p>This field will only appear if the Order Frequency type is "Days between delivery Orders" and it represents the number of days between regular replenishment orders.</p>
</td>
</tr>
<tr>
<td width="217">
</td>
</tr>
<tr>
<td width="217">
<p>Ordering days of week</p>
</td>
<td width="81">
<p> </p>
</td>
<td width="267">
<p>This field will only appear if the Order Frequency type is "Days of week" and it represents the days when the automatic requisitions need to be generated taking into account the planned delivery date and the lead time in the system. For example, if the order needs to be delivered on Tuesdays and Fridays and the total lead time to the station (including preparation time and transit days) is three days, then you should select Sunday (Tuesday's delivery) and Wednesday (Friday's delivery). If the working days for the station are Monday to Friday, then Skylog will generate the requisition on the previous working day. [[File:20200520 Ordering days.png|400px]]</p>
</td>
</tr>
<tr>
<td width="217">
<p>% Loss at the Station</p>
</td>
<td width="81">
<p>10</p>
</td>
<td width="81">
<p>This is used by the forecasting system. Any percentage here will be applied and deducted from the calculated recovery of the item at the Station. So if the forecasting system has calculated that a quantity of 200 should be recovered from inbound flights but this field is set to 10% then only 180 will be considered usable to meet future demand.</p>
</td>
<td width="267">
<p> </p>
</td>
</tr>
<tr>
<td width="217">
<p>Count Category</p>
</td>
<td width="81">
<p>Full</p>
</td>
<td width="267">
<p>Selects a stock count category (set up in previous chapter) to which the item will be added. <b>PLEASE NOTE</b> that only counts where "Update Par Levels" is set to YES and "Include All Par Levels" is set as NO will appear as a choice on the drop down list.</p>
</td>
</tr>
<tr>
<td width="217">
<p>Round Requisition Quantities?</p>
</td>
<td width="81">
<p>Yes</p>
</td>
<td width="81">
<p>Yes, means and suggested requisition quantities will be rounded up to multiples of the default unit of issue</p>
</td>
<td width="267">
<p> </p>
</td>
</tr>
<tr>
<td width="217">
<p>Include Target Floating Stock For Automatic Requisitions</p>
</td>
<td width="81">
<p>No</p>
</td>
<td width="267">
<p> </p>
</td>
</tr>
<tr>
<td width="217">
<p>How Is Item To Be Requisitioned?</p>
</td>
<td width="81">
<p>Events</p>
</td>
<td width="267">
<p>Event refers to auto requisitions, Manual to manually raised requisitions</p>
</td>
</tr>
<tr>
<td width="217">
<p>Default Requisition Confirmed Qty to Zero</p>
</td>
<td width="81">
<p>No</p>
</td>
<td width="267">
<p> </p>
</td>
</tr>
</table>
<p> </p>

</ol>

=Stock Items / Par Levels=
Station Par levels refers to items a Station would be allowed to place orders for and receive into stock. These can be created in a few ways: copy Par Levels from identical/similar station or do it one item at a time

==Copy Par Level from existing station==
<ol>
<li>in Station Par Levels select a stations you want to copy whole par level from</li>
<li>At the bottom of the screen press the button "Copy"</li>
[[File:LocationOfCopyParLevelsButton.png |1200px|]]

<li>In field “Use Destination Station Defaults?” mark to “Yes”. </li>
<li>Select station you want to copy par levels to. </li>
[[File:CopyParLevelToStationPage.png |1200px|]]

<li>Confirmation screen will appear. </li>
[[File:CopyParLevelsConfirmPage.png]]

</ol>

==Adding Items to Par Levels==
Station Par levels are available for review and edit under <b>Daily Activities</b> in <b>Provision section</b>. Please select the Station with [[File:Edit.png]]. To add a new item press [[File:PlusPlus.png]] and complete filling in the table to finalize the setting up, make sure that the item status is marked "Active" on the bottom of the page.

=Closing Station=
In order to close an active station, prior to marking the Station as not active, few very important steps need to be taken to make sure the MRP forecast is reflected correctly for material planners, and that all the assets are accounted for, the below steps need to be taken;

==Stock In transit is accounted for==
Any stock that is in transit to the Station needs to be receipted and moved via RMA to another location (another Station or Warehouse), used up at the station, or scrapped with a scrap order. There should be no stock left at the station before the station can be closed

==Station Stock Counts are closed==
All station stock counts need to be closed, and most importantly, the last stock count needs to have all items showing zero - the last stock count qty of each item needs to be 0. This is important to reflect correct consumption and asset valuations.

==End of the forecast ==
Any manual forecast uploaded in SkyLog related to the Station you want to close needs to be removed from SkyLog.

Station Index

2026-03-27T11:08:12Z

Betsy:

{{Tips and tricks}}

__TOC__

=Summary=
A station is an Organization that provides flight or passenger services to an airline at an airport. This includes caterers, cabin cleaners, and other ground handling service providers as well as passenger lounges and ticketing agencies. In order for a Station record to exist, there must first be an Organization and OrganizationSite to which that Station can be linked.

=Create organization=
Organization refers to the company as a whole e.g. Lufthansa, Gate Group, or Coca-Cola, underneath the Organization there can be multiple OrganizationSites (see below). In order to be linked to a Station, the Organization type must be "Caterer/Service Provider".
First, please check if the Organization already exists in SkyLog. Here you can find the list of all Organizations [[https://rsprod.skylogportal.com/Organization'''link''']]. If the Organization already exists please move to the next step. Organizations are centrally controlled and maintained to avoid duplicate organizations being created across multiple operations, therefore if the Organization does not exist contact a Global Administrator or raise a support request. [[http://wiki.skylogportal.com/index.php?title=Organization_Index '''For more details about Organizations click here''']]

=Organization Sites=
An Organization site represents a physical location from which the Organization operates, the site record contains the physical address of the location as well as the main site contact details and the timezone of that site. The site record must exist before you can create a Station record or for that matter any other supply chain participant type such as AirlineSupplier, Warehouse, etc. Firstly Please check if a site is already created in SkyLog with the same address and linked to the same Organization, it is important not to duplicate organization sites. [[http://wiki.skylogportal.com/index.php?title=OrganizationSite_Index '''For more details about Organization Sites click here''']]

=Stations=
The station setup contains specifications of that station's operations such as the frequency it should report inventory of airline-owned items and a list (StationItems) of the airline-owned items it needs to provide the services to the airline. Against each item, we record the par levels e.g. how many days of inventory to hold, the frequency of replenishment, the replenishment source and lead time, etc. SkyLog allows you to define at the station level many parameters to customize stations processes. For example, automatic stock count approvals, different ways of RMA management, and the level of automation within process flows.

==Stations creation==
To create a station record a few things are required to be confirmed: station setup, Supply sources,
You can start creating a new station by going to Reference Data/Airline Participants/Stations

[[File:CreateStationRef.png]]

SkyLog allows advanced customization of the station processes. To deliver the most productive setup please consult the guide below which explains each customization option on the page


<table width="0">
<tr>
<td width="170">
<p><strong>Field</strong></p>
</td>
<td width="444">
<p><strong>Description</strong></p>
</td>
</tr>
<tr>
<td width="170">
<p>Station Site</p>
</td>
<td width="444">
<p>Link to Organization site. It is the source of the Station address that is printed on invoices, transport bills and communicated to 3rd parties</p>
</td>
</tr>
<tr>
<td width="170">
<p>Airport</p>
</td>
<td width="444">
<p>Every station must have link to the airport it services. If a single OrganizationSite serves two or more airports then you should create a station record for each airport served.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Service Type</p>
</td>
<td width="444">
<p>Assign relevant station type, e.g. "Caterer", "Airport Lounge",</p>
</td>
</tr>
<tr>
<td width="170">
<p>Active</p>
</td>
<td width="444">
<p>It is a yes /no field that can only be active once all the requirements have been sent up.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Valid From</p>
</td>
<td width="444">
<p>Date of start of operations.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Valid To</p>
</td>
<td width="444">
<p>Date of station closure. If not known or open ended leave blank.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Station Provisioning Manager</p>
</td>
<td width="444">
<p>The person who will be responsible for the provisioning/replenishment of goods for the station (i.e. who will approve requisition requests, inventory reports, etc.). This will be a person within the Airline or the Airline's 3rd party Control Tower</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="444">
<p>The person to be assigned (from users registered in SkyLog) who will be responsible for stock counts, this will be someone within the organization of the Station. The selected person will be the recipient of related notifications such as reminders to count, shipment notifications and various escalations/alerts regarding Station Provisioning and Inventory Management</p>
</td>
</tr>
<tr>
<td width="170">
<p>Is Station Independent from Skylog?</p>
</td>
<td width="444">
<p>Station exists within Skylog but is not expected to have any interactions via the UI (Portal)with Skylog – if the station will raise requisitions in SkyLog and/or be expected to submit inventory reports then this setting should always be set as 'No'. Typically this will only be set to 'Yes' if the Station uses their own systems to submit inventory counts and place requisitions and there is an interface between that system and SkyLog</p>
</td>
</tr>
<tr>
<td width="170">
<p>Automatically Generate Requisitions?</p>
</td>
<td width="444">
<p>Yes/No field will either allow (if yes) to generate automatic requisitions after a stock count, via schedule or even manually. If no, only manual orders are allowed to be placed by station. Setting to No is more common for lounges.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Non Orderable Items in Requisitions</p>
</td>
<td width="444">
<p>Typically, Skylog only permits 'current' materials to be requisitioned. However, some users prefer to see all materials on the requisition so that they can make informed judgements, including temporary materials which may have been supplied in the past in place of a regular material (e.g. substitute materials where the station par level status = "Temp/Sub"). If the station wishes to see such temporary/substitute items on requisitions then this configuration flag should be set as 'Yes', otherwise, set as 'No'. This setting is often enabled for stations for SAP-Centric clients.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Generate Automatic Requisitions Upon Count Approval</p>
</td>
<td width="444">
<p>This can only be set to "Yes" if "Will Requisitions Be Automatically Generated for This Station?" is also set to "Yes". If set as "Yes" then Skylog will create a new automatic-requisition when an inventory count is approved - this relies upon station par levels being configured for event-driven requisitioning though. If you would prefer that automatic-requisitions are triggered for this station based upon an automatic schedule cycle* then this setting should be configured as "No". * - If you do wish to trigger automatic requisitions based upon an automatic schedule then "Will Requisitions Be Automatically Generated For This Station?" should be set as "Yes" and each material to be included (for automatic requisitioning) should be set as Schedule-driven requisitioning - if set as such, you will be prompted to provide a next requisition trigger date; such configuration is achieved via the station par levels for this station.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Keep Back Orders?</p>
</td>
<td width="444">
<p>When a new requisition is processed should Skylog retain existing back-orders? If Skylog should discard open back-orders upon processing a new requisition, set this configuration flag to 'No'. Otherwise, if Skylog should leave the decision as to whether a back-order is cancelled or processed to a member of the operational team then set this configuration flag to 'Yes'.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Confirm RMA Shipments?</p>
</td>
<td width="444">
<p>If the configuration flag is set as 'No' it is not necessary for the station to confirm the despatch for a RMA. If the configuration flag is set as 'Yes' then the station returning the goods must confirm the despatch.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Automatic Requisition Negative Numbers Default to Zero</p>
</td>
<td width="444">
<p>If SkySuite believes that the station has too much stock, it will suggest a negative order quantity in the requisition. If the station does not wish to return such goods, then the requested quantity should be set as zero – meaning that the line/position will be ignored by SkySuite. With this configuration flag set as 'Yes', Skylog will automatically set the requested number from a negative value to zero. If this configuration is set as 'No' then the requested quantity will always default to suggested order quantity (even if the suggested order quantity is less than zero). For stations where the autorequisitions are generated based on days of the week, is recommended to set this flag to 'Yes', otherwise SkySuite will include the quantity to return in the calculation of the suggested quantities, leading to additional stock being suggested to be sent to the station.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Enforce RMA Qty</p>
</td>
<td width="444">
<p>If Station is allowed to issue a RMA for parts they haven't ordered from inbound flights etc. then set to 'No'. If 'Yes', the Station will be allowed to return only that stock qty that they counted in the last stock count.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Receipt Configuration</p>
</td>
<td width="444">
<p>The default expectation is that stations will always receipt-confirm all inbound transactions (station orders, direct purchase orders, station-to-station transfers etc.). If however it is permitted for some transactions to be 'automatically' received (i.e. without user interaction), then this can be configured via this setting.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Default Requisition Confirmed Qty to Zero</p>
</td>
<td width="444">
<p>If the flag is set to 'No', SkySuite will pre-populate requested quantity to match the suggested quantity. If the flag is set to "Yes", SkySuite will pre-populate the requested quantity with zero, and the station provisioner will need to either enter manually the quantity to approve, or select the option to populate that for all lines. For stations where the autorequisitions are generated based on days of the week, is recommended to set this flag to 'No', otherwise SkySuite will not include the quantity on automated requisitions awaiting review or approval, leading to additional stock being suggested to be sent to the station.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Should Skylog Consider External Target Quantity Data in Core Functions?</p>
</td>
<td width="444">
<p>Specifies whether or not external target quantities, commonly known as FOS + BUS values (supplied to Skylog via uploaded SCA files), will be used by Skylog to affect various Skylog functions. Such functions would include the calculation of the suggested order quantity figure for automatically generated requisitions. The target values will also be used to determine if a material on a submitted inventory count would be flagged as a query or not. If this setting is set as 'No' then Skylog will use the traditional formulas (which won't use target quantity values). If this setting is set as 'Yes', Skylog will consider the target quantities in its calculations.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Station Depot</p>
</td>
<td width="444">
<p>A unique code that identifies the specific station (unique across all airlines).</p>
</td>
</tr>
<tr>
<td width="170">
<p>Station Loading Code</p>
</td>
<td width="444">
<p>An alternate station identifying code which is used by third-party systems to identify a specific station. This code would be used in data files originating from those partner-systems, such as the Service Rules interface EDI. If this interface is used by the operation associated with the station then the uploading and offloading stations identified within the service rules data must correspond to the Station Loading Codes held by Skylog.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Customer Code</p>
</td>
<td width="444">
<p>This is an optional property and should be left blank/empty, it serves a special purpose for a handful of specific catering facilities but has no relevance for the majority of stations and thus can be ignored.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Default Loading</p>
</td>
<td width="444">
<p>This is a mandatory field that may be used when SkyLog generates a forecast for the airline; it can be set to Yes or No (true or false) and it will be used if there is insufficient pre-set data or rules to determine the loading or unloading station. The SSIM (Flight Schedule) file that we receive and process for the airline only tells us the departure and arrival ports for each flight in the schedule. Some ports will be setup with multiple catering stations at a given port and we will determine which station loads and unloads the content of any provisioning code based on pre-set data in the provisioning rule and/or exchange rules. However if there is insufficient pre-set data/exchange rules to tell us which station will perform the loading/unloading then the forecast will use the default station which is determined by this field. Importantly, there can only be a SINGLE default catering station per combination of Port & Airline (additionally, in case it’s not obvious, the station must be active for the default loading to be set to Yes).</p>
</td>
</tr>
<tr>
<td width="170">
<p>GL Cost Centre Code</p>
</td>
<td width="444">
<p>An alternate station identifying code which is used by third-party systems to identify a specific station. This code would be used in data files originating from those partner-systems, such as the Service Rules. GL Cost Centre field links financial data with customer financial systems. In case a new GL Cost Centre is required to be set up please follow the link for guidance how to [[http://wiki.skylogportal.com/?title=Station_CostCentreCategoryIndex'''link''']].</p>
</td>
</tr>
</table>

=Supply Source=
Supply sources define which warehouses will be supplying stations with goods and which modes of transport are used. It is possible for stations to be supplied by multiple warehouses and this could be defined at the item level in Station Item / Par Level tables. Multiple modes of transport could be assigned for each supplying warehouse with different transportation and handling lead times and a priority ranking to determine the preferred mode of transport.

The Supply Sources button is found in the '''Reference Data/Supply Chain Participants/Stations'''. Select desired station by clicking on [[File:Edit.png]]. At the bottom of the new page will be [[File:SupplySourceButton]].

==Add Warehouse==
To add a warehouse that will be supplying station:
<ol>
<li>Select [[File:PlusPlus.png]]</li>

<li>Select Warehouse</li>

[[File:SelectWarehouse.png]]

<li>Set as active </li>

[[File:SetActiveWarehouse.png]]
</ol>

==Add Transport Methods==
<ol>
<li>Under the Warehouse-Station Link, next to set up warehouse select [[File:Expand.png]] to expand the field as per below and select [[File:PlusPlus.png]] to add mode of transport from selected warehouse.</li>

[[File:AddModeOfTransport.png |1200px|]]

<li>Select accordingly
<ol style="list-style-type: lower-alpha;">
<li>Method of transport from drop down list. Note that there are more options then seen on the screen, use scrolling down option to see all modes of transport available.</li>

<li>Preparation time – days it takes the warehouse to pick and pack.</li>

<li>Transport duration – days it takes from dispatch until station receipt.</li>

<li>Rank – priority / default option.</li>
</ol>
</ol>

[[File:AddModeOfTransportSpec.png]]

Complete table should look like this.

[[File:CompleteTransprotSetup.png |1200px|]]

=Station Count Category=
Station count categories define which items are counted by the Station and how often they are counted. It also allows you to set the tolerances between expected and actual count quantities (count variances) at which a count line is set to "Query". The level of automation in the count and approval process and also be set – some counts can be set up as auto accepted after they are submitted, a useful feature for stations like lounges with little turnover. Station Count Category can be found under '''Daily Activities/Inventory Counts/Station Count Categories'''.

<ol>
<li>Select [[File:PlusPlus.png]] in the Station Count Categories page </li>

<li>Select station requiring new station count category</li>

[[File:SelectStationRequiringNewStationCountCategory.png]]

{| class="wikitable" style="width:80%"
|-
! Field
! Sample
! Description
|-
!Count Category Description
|Full
|Description of the count category. The station could have multiple counts with different parts under each, so naming of the count category is useful to avoid confusions. A typical example might be to set up a count category called "Major Equipment" for all technical equipment such as Trolleys/carts or to have a category "Disposables" for all disposable items.
|-
!Count Schedule Option
|Automatic Schedule
|There are 3 options "Automatic Schedule" (repeats based on provided frequencies), "Manual Schedule" (follows manual dates listed in manual schedule table on the bottom of the page) and "None" (stock counts generated only manually)
|-
!Automatic Schedule Options
|Specific Day/s of the Week
|You can pick between days of the week or days of the month, days of the week or days of the month [that new inventory counts will be due]
|-
!Specific Day/s of the Week or Month
| --
|tick/specify days when stock count should be triggered; if specifying days of the month, each must be comma-separated. Note: you can not specify consecutive days; there has to be at least one day's gap between inventory counts [it's not allowed to instruct a station to perform a new count each and every day
|-
!Weeks Between Counts
|1
|Number of weeks between counts (if 'Automatic Schedule Options' = "Specific Days of the week", rather than Specific Days of the Month)
|-
!Notify Days
|3
|Number of days the stock count will be generated before the expected count date, the station will get an email notification at when the count is generated and then has the notify days to prepare for the count.
|-
!Next Count Generation Date
|September 28, 2023
|Select next/first stock date for a count to be scheduled. This date is automatically updated each time a count is generated but a user can re-sync the schedule by editing the date
|-
!Value Tolerance for Count Variances
|100
|Not mandatory, select variances in value per line to tolerate as ok. Meaning if, for example, there is a 100 GBP tolerance and the discrepancy from the expected stock count is 99 GBP, the count will appear as ok. Different tolerance levels can also be set at the item level and the count category tolerance will only apply if there is no item-level tolerance defined.
|-
!% Quantity Tolerance for Count Variances
|10
|Not mandatory, select variance in quantity % per line to be tolerated from the expected count. Meaning if, for example, there is a 10% tolerance and the discrepancy from the expected stock count is 5%, it will not appear as a query. Different tolerance levels can also be set at the item level and the count category tolerance will only apply if there is no item-level tolerance defined.
|-
!Person Responsible for Counts
| --
|Select the person (out of those assigned to this station/organization site), that will be responsible for counts and will be receiving notifications related to it. Leave this field blank if you would prefer alerts to be sent to ALL points of contact associated with the station. If no point of contact can be found, alerts will be sent to the station provisioning manager (in lieu of being sent to caterer / groundhandlers with links to the station).
|-
!Include Floating Qty
|Yes
|Float stock represents the stock that is in the inbound, outbound, and production areas of the station often known as "WIP" (Work in Progress), it does not include stock that is in a storeroom/warehouse area of the Station. If selected "Yes", columns will appear on the stock count page to count both Backup stock and Float stock and report both quantities separately. Backup stock is the stock in a storeroom/warehouse area). If selected "No" then only the Backup stock is expected to be counted and reported.
|-
!Include Breakages
|No
|If yes, will add a column for breakages to be filled by the Station during the stock count. This reflects any losses at the station since the previous count as a result of breaking/damaging products (to an extent they can no longer be used) - e.g. cracked glass, chipped chinaware, etc.
|-
!Attach Count Sheet File When Notifying Station
|Yes
|Advise selecting Yes, which will attach an excel file to the notification email, that when filled could be uploaded to SkyLog for submission. It is a good tool to avoid manual entries in the portal. Note, for new airlines, additional setup is required to enable this - please raise a support ticket and ask for this option to be enabled though.
|-
!Consumption Trend Span (Days)
|180
|Default value is 180, and if left blank it will generate a value of 180 days. This value is used in the calculation of the "smooth" average past daily consumption, if set to 180 it will look at the last 180 days when calculating the daily average but it can be set longer or shorter.
|-
!Generate Automatic Requisitions Upon Count Approval
|Yes
|If Yes, the system will generate an automatic requisition after the stock count is approved (although this is dependent upon the station itself being configured to support automatic requisitioning too).
|-
!Include All Items in Automatic Requisitions
|Yes
|Yes, will include all active items in any auto requisition (even if the suggested order is 0)
|-
!Delay (Hours) For Automatic Requisition Generation
|0
|This is the number of hours after count approval before which any automatically triggered requisition should be triggered
|-
!Include All Station Par Levels In Counts
|No
|Only select YES for "special" counts which are additional to the regular counting cycle, such as a coordinated global stocktake. Thus for regular counts, this setting should be set as NO. Only count categories where this configuration setting is set as NO will appear as a valid option when defining a default count category (See 'Station Defaults' section below).
|-
!Update Station Par Levels
|Yes
|Only select NO for "special" counts which are additional to the regular counting cycle, such as a coordinated global stocktake. So for regular counts, this should be set as YES. Only count categories where this configuration setting is set as YES will appear as a valid option when defining a default count category (See 'Station Defaults' section below). When set as YES, assuming that the count is approved, the approved inventory figures will be copied across to the station par levels and will be used as the starting inventory figures for the next iteration of the count. Additionally, with this configuration flag set as YES, it will also mean that average consumption figures are calculated and may have a bearing on RMA functionality too (depending on station-level configuration tho).
|-
!Count Auto Approval Option
|Review Required
|
* Review Required - will request that the Station Manager does a full review of every stock count submitted by the Station for this count category, even if there are no lines on the count that are flagged as outside of tolerance

* Auto-Approve When No Queries - stock count will be automatically approved by the system if all count lines are within the defined tolerances (i.e. no queries were generated by the system.

* Auto-Approve Regardless - this will mean that even if there are lines on the count that are flagged as being outside of tolerance, the count will automatically approve - the station provisioning manager will not be alerted and will not need to review the count, thus there can be no re-count process.

* Approval NOT Required - only select this option for "special" counts which are additional to the regular counting cycle, such as a co-ordinated global stocktake

<b>NOTE:</b> You can only select the 'Approval NOT Required' option when the 'Update Station Par Levels' flag is set to 'No'.

<b>IMPORTANT:</b> Be warned, this is the final configuration flag when you add or edit a station count category record, if you select this option, you will find that it will toggle (update) the settings for "Include ALL Station Par Levels" and "Update Station Par Levels" - so you may find that your resultant count category is not as you had originally specified it because of this final setting.

If you want regular (standard) counts to always sail through, skipping the approval step then choose the "Auto-Approve Regardless" option instead; thus, the station provisioning manager won't be notified to review the count when the caterer has submitted their inventory figures.
|-
|}
</ol>

==Sample of complete Station Count Category setup==
[[File:SampleCategoryCount.png]]

=Station Defaults=
Station defaults are used whenever doing a mass creation of Station Item records, for example - when copying the items from one station to another, or when the forecasting system, as a result of loading or flight schedule changes, creates new items for that station. The criteria in station defaults will be applied to all items copied or created from forecasting but can be edited item by item as required.
<ol>
<li>In the Stations page (Reference data/Supply Chain Participants/Stations) select a station in edit mode. </li>

<li>Fill Station Default table accordingly. Table with descriptions is presented below</li>


<table width="0">
<tr>
<td width="217">
<p><strong>Field</strong></p>
</td>
<td width="81">
<p><strong>Sample</strong></p>
</td>
<td width="267">
<p><strong>Description</strong></p>
</td>
</tr>
<tr>
<td width="217">
<p>Transport Method/Duration (Days)</p>
</td>
<td width="81">
<p> </p>
</td>
<td width="267">
<p>Select default method of transport</p>
</td>
</tr>
<tr>
<td width="217">
<p> </p>
</td>
<td width="81">
<p> </p>
</td>
<td width="267">
<p> </p>
</td>
</tr>
<tr>
<td width="217">
<p>Security Stock (Days)</p>
</td>
<td width="81">
<p>14</p>
</td>
<td width="267">
<p>Security / safety stock of the item to be held at the station in days</p>
</td>
</tr>
<tr>
<td width="217">
<p>Days Needed for Preparation</p>
</td>
<td width="81">
<p>1</p>
</td>
<td width="267">
<p>This is the number of days needed to get stock prepared for for a flight.</p>
</td>
</tr>
<tr>
<td width="217">
<p>Days Needed to Recycle</p>
</td>
<td width="81">
<p>1</p>
</td>
<td width="267">
<p>This is the number of days needed to recycle stock from inbound flights to be ready for re-use e.g. the separation & and washing time</p>
</td>
</tr>
<tr>
<td width="217">
<p>Specify Order Frequency Type</p>
</td>
<td width="81">
<p> </p>
</td>
<td width="267">
<p>Days between delivery/orders or days of the week.</p>
</td>
</tr>
<tr>
<td width="217">
<p>Days Between Delivery/Orders</p>
</td>
<td width="81">
<p>7</p>
</td>
<td width="267">
<p>This field will only appear if the Order Frequency type is "Days between delivery Orders" and it represents the number of days between regular replenishment orders.</p>
</td>
</tr>
<tr>
<td width="217">
</td>
</tr>
<tr>
<td width="217">
<p>Ordering days of week</p>
</td>
<td width="81">
<p> </p>
</td>
<td width="267">
<p>This field will only appear if the Order Frequency type is "Days of week" and it represents the days when the automatic requisitions need to be generated taking into account the planned delivery date and the lead time in the system. For example, if the order needs to be delivered on Tuesdays and Fridays and the total lead time to the station (including preparation time and transit days) is three days, then you should select Sunday (Tuesday's delivery) and Wednesday (Friday's delivery). If the working days for the station are Monday to Friday, then Skylog will generate the requisition on the previous working day. [[File:20200520 Ordering days.png|400px]]</p>
</td>
</tr>
<tr>
<td width="217">
<p>% Loss at the Station</p>
</td>
<td width="81">
<p>10</p>
</td>
<td width="81">
<p>This is used by the forecasting system. Any percentage here will be applied and deducted from the calculated recovery of the item at the Station. So if the forecasting system has calculated that a quantity of 200 should be recovered from inbound flights but this field is set to 10% then only 180 will be considered usable to meet future demand.</p>
</td>
<td width="267">
<p> </p>
</td>
</tr>
<tr>
<td width="217">
<p>Count Category</p>
</td>
<td width="81">
<p>Full</p>
</td>
<td width="267">
<p>Selects a stock count category (set up in previous chapter) to which the item will be added. <b>PLEASE NOTE</b> that only counts where "Update Par Levels" is set to YES and "Include All Par Levels" is set as NO will appear as a choice on the drop down list.</p>
</td>
</tr>
<tr>
<td width="217">
<p>Round Requisition Quantities?</p>
</td>
<td width="81">
<p>Yes</p>
</td>
<td width="81">
<p>Yes, means and suggested requisition quantities will be rounded up to multiples of the default unit of issue</p>
</td>
<td width="267">
<p> </p>
</td>
</tr>
<tr>
<td width="217">
<p>Include Target Floating Stock For Automatic Requisitions</p>
</td>
<td width="81">
<p>No</p>
</td>
<td width="267">
<p> </p>
</td>
</tr>
<tr>
<td width="217">
<p>How Is Item To Be Requisitioned?</p>
</td>
<td width="81">
<p>Events</p>
</td>
<td width="267">
<p>Event refers to auto requisitions, Manual to manually raised requisitions</p>
</td>
</tr>
<tr>
<td width="217">
<p>Default Requisition Confirmed Qty to Zero</p>
</td>
<td width="81">
<p>No</p>
</td>
<td width="267">
<p> </p>
</td>
</tr>
</table>
<p> </p>

</ol>

=Stock Items / Par Levels=
Station Par levels refers to items a Station would be allowed to place orders for and receive into stock. These can be created in a few ways: copy Par Levels from identical/similar station or do it one item at a time

==Copy Par Level from existing station==
<ol>
<li>in Station Par Levels select a stations you want to copy whole par level from</li>
<li>At the bottom of the screen press the button "Copy"</li>
[[File:LocationOfCopyParLevelsButton.png |1200px|]]

<li>In field “Use Destination Station Defaults?” mark to “Yes”. </li>
<li>Select station you want to copy par levels to. </li>
[[File:CopyParLevelToStationPage.png |1200px|]]

<li>Confirmation screen will appear. </li>
[[File:CopyParLevelsConfirmPage.png]]

</ol>

==Adding Items to Par Levels==
Station Par levels are available for review and edit under <b>Daily Activities</b> in <b>Provision section</b>. Please select the Station with [[File:Edit.png]]. To add a new item press [[File:PlusPlus.png]] and complete filling in the table to finalize the setting up, make sure that the item status is marked "Active" on the bottom of the page.

=Closing Station=
In order to close an active station, prior to marking the Station as not active, few very important steps need to be taken to make sure the MRP forecast is reflected correctly for material planners, and that all the assets are accounted for, the below steps need to be taken;

==Stock In transit is accounted for==
Any stock that is in transit to the Station needs to be receipted and moved via RMA to another location (another Station or Warehouse), used up at the station, or scrapped with a scrap order. There should be no stock left at the station before the station can be closed

==Station Stock Counts are closed==
All station stock counts need to be closed, and most importantly, the last stock count needs to have all items showing zero - the last stock count qty of each item needs to be 0. This is important to reflect correct consumption and asset valuations.

==End of the forecast ==
Any manual forecast uploaded in SkyLog related to the Station you want to close needs to be removed from SkyLog.

WarehouseTransfer Index

2025-06-25T11:16:47Z

Betsy:

{{Tips and tricks}}

=Generating proforma invoice=
The proforma invoice contains details required for the export and import clearance of the consignment. To generate the document, the shipment should be on status Despatched or partially received. Click on view option on the shipment you want to generate the proforma invoice for, and the option Generate Pro Forma Document will be displayed at the bottom of the page.

[[File:20210118_RMA_generate_proforma.png|250px]]

After you click, a message will be displayed, click close and refresh the page.

[[File:20210118_RMA_PDF_request.png|450px]]

A new icon will appear next to Generate Pro Forma document, click on it to download the document.

[[File:20210118_Download_proforma.png|280px]]

Substitution UnplannedIndex

2025-06-25T10:58:55Z

Betsy:

<roles>SLXGLOBALADMIN,SLXLOCALADMIN,SLXOPERATIONAL,AIRLINEADMIN,AIRLINEOPS</roles>
{{Tips and tricks}}

__TOC__

=Unplanned Substitutions=
==Summary==
Unplanned substitutions allows for the short to mid-term substitution of a stock item for a single alternative with respect to station replenishment in situations where a particular item is no longer available for order due to any number of possible reasons such as deemed unfit for purpose, have supply problems, or even that demand has exceeded expected demand and an insufficient quantity was ordered. There are a lot of situations in which an unplanned substitution would need to be actioned, but it is not ideal for your airline as it may affect the passengers experience if the replacement item varies significantly from the original item that had been planned.

Unplanned substitutions principally affect DRP but may also affect MRP too (if client is using that module). For DRP, unplanned substitutions have relevance for both automatically generated requisitions and also manually created requisitions although note, unplanned substitutions have no relevance for SAP-Centric clients as material substitutions are managed entirely in SAP.

Setting up an unplanned substitute request is, as the name implies, a reactive response to a problem rather than one that is pre-planned months in advance. A substitute request is raised within the SkyLog Portal, after which it is subject to a simple approval sign off by an authorised user before waiting for activation by the system. Activation could be immediate, or could occur in the near future. The activation period of the substitution has both a start and end date, after which the substitution will be de-activated and orders comprising the original item will be allowed to continue unchanged.

==Setting up a Unplanned Substitution==
===1. Initial Setup===
To set up an unplanned substitution navigate to the 'unplanned substitutions' page within SkyLog and click the add new record button.

[[file:Unplanned_Subs_1.PNG]]

You are then able to setup a new substitute request from the next screen as shown below.

[[file:UnplannedSubstitution3.PNG]]

An explanation of the options is as follows (* = Non-Mandatory);
* '''Reason''' - A list of different reasons are pickable, these identify why the substitution is being set up such as 'defective goods' for example.
* '''Stock Item''' - This is the stock item that is required to be substituted.
* '''Substitute Stock Item''' - The replacement stock item.
* '''Should a Conversion Factor Be Applied?''' (See ER #30049 for further details)- For example, consider purchasing 300 bottles of water. The original item is 500ml/bottle, and the substituting item is 600ml/bottle. Ordering 300x 600ml water bottles would result in 30,000ml of excess water, hence a Conversion Factor must be applied. It also can be applied when the stocking unit is cases and the case size of the subsitute item is different to the original item. To determine the conversion factor, you must divide the total volume of the original item by the substituting item.
Conversion Factor = (Total Volume of Original Item) / (Total Volume of Substituting Item) .
* '''Urgent''' - Selecting 'Urgent' will set the 'Date From' automatically to today, but is also used for identifying and reporting urgent substitutions.
* '''Date From''' - The date you want the substitution to start.
* '''Date To''' - The date you want the substitution to end.
* '''Substitute Complete Network''' - If the substitution is for all stations across your network then select 'Yes', if it is station specific select 'No'.
* '''Send Email Alerts''' - This will send emails to all relevant users to inform them of the substitution.
* '''Summary''' - A quick text summary of the substitution plus.
* '''Comment*''' - Any additional comments can be added.

Once all the mandatory fields are entered you can either 'Save and Continue' or 'Save and Exit', selecting 'Save and Continue' will enable you to then select stations affected (if 'Substitute Complete Network' was set to 'No').

===2. Additional Information===
As per above if you selected 'Save and Continue' you can now add notes and attachments relating to the substitution and/or affected stations, if you saved and exited you can navigate back to your new record from the main unplanned substitutions screen. For either section, simply click the add new record button to upload documents or select relevant stations.

[[file:Unplanned_Subs_3.PNG|750px]]

Note: Section 'Affected Stations' will only be displayed if 'Substitute Complete Network' = 'No'

===3. Submission===
Once all of the information you want to add to the substitution is complete, you will need to submit it for review by your airlines 'User Responsible for Approval of Substitutes'. Simply click 'Submit' at the bottom of the page to do so.

[[file:Unplanned_Subs_4.PNG]]

===4. Additional Changes===
You are able to edit all information on your substitution prior to submission, but once submitted and prior to approval you cannot edit and are required to wait until it is 'Approved' or 'Active'. But when in these statuses though you can only alter the date or cancel.

[[file:Unplanned_Subs_5.PNG|750px]]

==Process/ Statuses for Unplanned Substitutions==
===Approved/ Rejected===
Once your new substitution has been submitted it will now have to be approved by your airlines 'User Responsible for Approval of Substitutes', they will receive an email alert that a new substitution has been logged and requires their approval. They have the option to approve or reject, if they do reject your substitution then its status will be set to 'Rejected' and its workflow terminated meaning that you will need to log a new substitution as the previous one will no longer be editable. If the substitution is approved its status will become 'Active' as soon as the 'Date From' is elapsed, until that time though it will stay at 'Approved'.

===Active===
As per the above section, once the substitution has been approved the status becomes 'Active' as long as the 'Date From' is elapsed, but if todays date is prior to the 'Date From' then the status will stay as 'Approved'. But as soon as it is 'Active' all station orders (requisitions), for stations affected by the substitution, will use the replacement item until the status of the substitution is no longer 'Active'.

===Complete===
Completed substitutions are ones that have elapsed their 'Date To' which was initially set when the substitution was set up, or if the already active substitution has its 'Date To' manually set to a date in the past as detailed above in section "4. Additional setup".

===Cancelled===
If for some reason that prior to the substitution becoming active, such as the stock out issue is resolved, you can cancel it by simply by editing the 'Provisional', 'Approved' or 'Active' status substitution and selecting 'Cancel' (or, for some statuses, 'Close').

[[file:Unplanned_Subs_C.PNG]]

==Impact of Substitutions in SkyLog==
Substitutions are vital for your airline, as soon as they become active various modules of SkyLog are affected, such as station orders (Requisitions), station par levels and forecasts.

===Requisitions===
Once an unplanned substitution is active any requisitions created for a station, affected by the substitution, will reflect the item nominated to temporarily replace the original stock item. Each substitute line will be highlighted so that all parties are aware, clicking the substitute wheel icon will also show you the original item;

[[file:Unplanned_Subs_6.PNG|850px]]

When creating a requisition manually, users can do so via a template or manually line by line, but when selecting the original item a substitute wheel icon will be displayed and the substitute item will instead be added.

[[file:Unplanned_Subs_7.PNG|850px]]

Similarly, when creating a manual requisition, if the user selects an item for the requisition that has an active substitution then the portal will display a popup informing them that the item will be substituted and they should adjust quantities of the substitute appropriately;

[[file:Unplanned_Subs_8.PNG]]

===Par Levels===
You will find that items being used as a substitutes at (all or specific) stations may be of a different status before and after the substitution has been activated and deactivated. Below is a breakdown of each scenario;

{| class="wikitable" style="text-align: center;"
|-
! style="color:black" | Situation before Substitution (SPLs only)
! style="color:black" | Action on activation of substitute request on SPL records
! style="color:black" | Action on completion of Substitution
|-
|The substitute item already exists as 'Active'
|No update
|No update
|-
|The substitute item already exists as 'Phase Out'
|Item updated to 'Active'
|Item moved back to 'Phased Out'
|-
|The substitute item already exists as 'Provisional'
|Item advanced to 'Active'
|No update
|-
|The substitute item does not exist
|Item created as 'Active'
|Item updated to 'Phased Out'
|}

Station Index

2024-06-07T12:17:53Z

Betsy:

Station ParLevelIndex

2022-05-19T16:04:31Z

Betsy: Redirected page to Station Index#Stock Items .2F Par Levels

#REDIRECT [[Station_Index#Stock_Items_.2F_Par_Levels]]

SkyShare PublicationIndex

2021-10-28T14:59:46Z

Betsy:

{{Tips and tricks}}

__TOC__

<h1>Search Publication to Review</h1>

Whenever a publication is approved, you’ll receive an email notification. To review a publication, go to SkySuite Portal Home page. If you have publications pending to acknowledge, the following notification message button will be shown:

[[File:Unread Publications.png|700px]]

The total number of publications that haven’t been acknowledged will be highlighted in yellow. And the number of the unacknowledged publications for where the deadline date (“Review-by-Date”) is overdue, will be highlighted in red.

Click on the notification message button to view the publications not yet acknowledged. Alternatively, you can select the “Create/Review Publications” option from the Publications menu:

[[File:Create-Review Publications.png|700px]]

Then, filter in the “Reviewed?” column by the following criteria: “Please Review” and/or “Review Required”.

<h1>Review Publication Content</h1>

Click on the ''View'' icon [[File:View Icon.png]] to see the publication content:

[[File:Publication Details.png|700px]]

Note that if the publication replaces another publication, there will be a link for its review on the top right corner on the publication details banner:

[[File:View Previous Publication.png|700px]]

The publication details contains three sections: Publication header, relevant dates, optional fields and publication details.

<h2>Publication Header</h2>

“Publication Header” provides guidance on the type of publication:

• ''Publication Group'': category for the publication content (Security, Health & Safety, Loading Specification, Station Provisioning, Purchase Order, Inventory Management, Warehouse, Menu/Meal Planning, Transport Management, Miscellaneous)

• ''Publication Type'': subcategory within the publication group.

• ''Publication Title'': brief description of the publication content.

• ''Publication Details'': detailed description of the publication.

<h2>Relevant Dates</h2>

“Relevant Dates” indicates the publication validity dates and the latest day to acknowledge:

• ''Valid From'': initial date the publication is effective.

• ''Valid To'': last date the publication is effective.

• ''Review-by-Date'': latest date by which the publication should be acknowledged.

<h2>Optional Fields</h2>

“Optional Fields” details additional information relating where the publication applies:

• ''Aircraft'': shown if the publication applies to a specific aircraft type.

• ''Market'': shown if the publication applies to a specific market.

• ''City Pair'': shown if the publication applies to a specific route.

• ''Flight'': shown if the publication applies to a specific flight.

<h2>Publication Detail</h2>

“Publication Detail” contains attachments and related publications:

• ''Attachments'': Images and PDF file types can be viewed without downloading. All file types can be downloaded when selecting the “Download” button.

• ''Linked Publications'': Related Publications.

• ''Audit History'': records of any attachment title update, attachment addition/deletion.

<h1>Acknowledge a Publication without Attachments</h1>

Click on the ''View'' icon [[File:View Icon.png]] or the ''Arrow'' icon [[File:Arrow Icon.png]] at the publication line level. And select the “I Acknowledge This Publication” button -located on the left bottom-, to confirm that you have read and understood the publication:

[[File:Acknowledge without Attachments.png|700px]]

It’s '''important''' to make sure you have fully reviewed the publication before acknowledging its receipt.

A review email notification will be sent if a publication without attachments has already been reviewed, and attachments have been added since then.

<h1>Acknowledge a Publication with Attachments</h1>

Click on the ''View'' icon [[File:View Icon.png]] or the ''Arrow'' icon [[File:Arrow Icon.png]] at the publication line level. Then click on the ''Arrow'' icon at the attachment line level. The “Acknowledge” button will be available after viewing an image or a PDF file attached; other file types attached have to be previously downloaded.

For every attachment you must click the “Acknowledge” button to confirm that you have read and understood it:

[[File:Acknowledge with Attachments.png|700px]]

It is '''important''' to make sure you have fully reviewed the attachment before acknowledging it. All the attachments must be acknowledged.

A review email notification will be sent if a publication with attachments has already been reviewed, and new attachments have been added since then.

SkyShare PublicationIndex

2021-10-28T14:57:26Z

Betsy:

{{Tips and tricks}}

__TOC__

<h1>Search Publication to Review</h1>

Whenever a publication is approved, you’ll receive an email notification. To review a publication, go to SkySuite Portal Home page. If you have publications pending to acknowledge, the following notification message button will be shown:

[[File:Unread Publications.png|700px]]

The total number of publications that haven’t been acknowledged will be highlighted in yellow. And the number of the unacknowledged publications for where the deadline date (“Review-by-Date”) is overdue, will be highlighted in red.

Click on the notification message button to view the publications not yet acknowledged. Alternatively, you can select the “Create/Review Publications” option from the Publications menu:

[[File:Create-Review Publications.png|700px]]

Then, filter in the “Reviewed?” column by the following criteria: “Please Review” and/or “Review Required”.

<h1>Review Publication Content</h1>

Click on the ''View'' icon [[File:View Icon.png]] to see the publication content:

[[File:Publication Details.png|700px]]

Note that if the publication replaces another publication, there will be a link for its review on the top right corner on the publication details banner:

[[File:View Previous Publication.png|700px]]

The publication details contains three sections: Publication header, relevant dates, optional fields and publication details.

<h2>Publication Header</h2>

“Publication Header” provides guidance on the type of publication:

• ''Publication Group'': category for the publication content (Security, Health & Safety, Loading Specification, Station Provisioning, Purchase Order, Inventory Management, Warehouse, Menu/Meal Planning, Transport Management, Miscellaneous)

• ''Publication Type'': subcategory within the publication group.

• ''Publication Title'': brief description of the publication content.

• ''Publication Details'': detailed description of the publication.

<h2>Relevant Dates</h2>

“Relevant Dates” indicates the publication validity dates and the latest day to acknowledge:

• ''Valid From'': initial date the publication is effective.

• ''Valid To'': last date the publication is effective.

• ''Review-by-Date'': latest date by which the publication should be acknowledged.

<h2>Optional Fields</h2>

“Optional Fields” details additional information relating where the publication applies:

• ''Aircraft'': shown if the publication applies to a specific aircraft type.

• ''Market'': shown if the publication applies to a specific market.

• ''City Pair'': shown if the publication applies to a specific route.

• ''Flight'': shown if the publication applies to a specific flight.

<h2>Publication Detail</h2>

“Publication Detail” contains attachments and related publications:

• ''Attachments'': Images and PDF file types can be viewed without downloading. All file types can be downloaded when selecting the “Download” button.

• ''Linked Publications'': Related Publications.

• ''Audit History'': records of any attachment title update, attachment addition/deletion.

<h1>Acknowledge a Publication without Attachments</h1>

Click on the ''View'' icon [[File:View Icon.png]] or the ''Arrow'' icon [[File:Arrow Icon.png]] at the publication line level. And select the “I Acknowledge This Publication” button -located on the left bottom-, to confirm that you have read and understood the publication:

[[File:Acknowledge without Attachments.png|700px]]

It’s '''important''' to make sure you have fully reviewed the publication before acknowledging its receipt.

A review email notification will be sent if a publication without attachments has already been reviewed, and attachments have been added since then.

<h1>Acknowledge a Publication with Attachments</h1>

Click on the ''View'' icon [[File:View Icon.png]] or the ''Arrow'' icon [[File:Arrow Icon.png]] at the publication line level. Then click on the ''Arrow'' icon at the attachment line level. The “Acknowledge” button will be available after viewing an image or a PDF file attached; other file types attached have to be previously downloaded.

For every attachment you must click the “Acknowledge” button to confirm that you have read and understood it:

[[File:Acknowledge with Attachments.png|700px]]

It’s '''important''' to make sure you have fully reviewed the attachment before acknowledging its receipt. Also, it’s important to acknowledge all of the attachments.

A review email notification will be sent if a publication with attachments has already been reviewed, and new attachments have been added since then.

Requisition Index

2021-07-30T14:39:12Z

Betsy:

Please use our '''[[Tips and Tricks]]''' page for understanding how the SkySuite portal works and how to navigate faster and easier.

__TOC__

<h1>Creating Manual Requisitions</h1>

Typically, you will create a Requisition from scratch if you want to order 1 or a small number of items outside your regular ordering sequence due to some unforeseen circumstance. If you need to order a lot of items, you will find it quicker to create the Requisition from a pre-stored template but see the below [[#Creating a New Requisition from a Template|''''Creating a New Requisition from a Template'''']] for more details on this, and also this [[http://wiki.skylogportal.com/?title=Requisition_ManageStationTemplates '''link''']] for maintaining the template.

To create a Requisition from scratch you should take the add icon from the Create/ Review Requisitions page.

[[File:Req_pic_1.PNG]]

The following page will be displayed;

[[File:Req_pic_2.png]]

In the header section you enter the date you require the goods by and any comment you may like to record.

In the detail section you add the items you want by pressing the add icon.

[[File:Req_pic_3.png]]

This will then display a screen allowing you to select the item (You simply select an item by pressing the “Select” Button, if you don’t see the item you want you can page though until you find it our use the filters by clicking the three dots on each column) and then add the required quantity.

[[File:Req_pic_4.png]]

If you enter a quantity that is not a multiple of the default pack size, you will get the following pop up in which you will need to detail whether to round up or down accordingly.

[[File:Req_pic_5.png]]

After entering the header section and when you press the add button to select detail or you press the “Save” button the system performs a check to see if the date you requested is possible if it is not you will see a message similar to the one below;

[[File:Req_pic_6.png]]

Once you have added a line you will be returned to the page where you see the lines added so far and you can add another line by pressing Add Icon again.

[[File:Req_pic_7.png]]

==Submitting your Requisitions==

You can continue to add lines until you have entered all the items you need. When you are ready to submit your Requisition to SkylogistiX press the “Submit” button, after this you will no longer be able to add to this Requisition so only press Submit when you have entered everything. If you wish to save and come back to the Requisition later use “Save and Exit” to save your work in this case the status of the Requisition will stay “Pre-Manual Submit” and you can come back to it later. Once you press Submit the status will change to “Awaiting Approval” which means SkylogistiX will review it. You will receive an email advising you that the Requisition has been successfully submitted for review.

On the main Create/Review Requisitions screen you will see that it is now at “Awaiting Approval” status – see below example.

[[File:Req_pic_8.png]]

<h1>Creating a New Requisition from a Template</h1>

You can create new Templates or maintain your existing Templates by pressing 'Lightening bolt ' icon from the main “Create/ Review Requisitions” page;

[[File:Req_pic_9.png]]

Once you press “Manage Templates” you will see a list of any existing templates for your station;

[[File:Req_pic_10.png]]

In the example above there is a template stored call “LAX Template”, to see the items in the template click the drop down arrow;

[[File:Req_pic_11.png]]

If you wanted to create a Requisition from this Template press the “Create” button. This will automatically create a new Requisition with all the items that are defined on the Template. In the example below you can see the Requisition with 6 items has been created.

[[File:Req_pic_12.png]]

From here you can edit the Quantities, add new lines or delete lines.

[[File:Req_pic_13.PNG]]

Then once ready you can submit your Requisition like in the example [[#Submitting your Requisitions|'''here''']] which was referenced above.

<h1>Tracking a Requisition Status</h1>

Once you have submitted a Requisition as described in the section above, the next step is a review by SkylogistiX. As previously described until that review takes place the Requisition will be at “Awaiting Approval” status. Once it has been reviewed by SkylogistiX the status will move to either “Rejected” or “Outstanding” and you will receive an email telling you that the Requisition has now been approved or rejected. If approved, it is possible that not all the items and quantities you requested have been approved and therefore some of the quantities you requested may have been altered. If you want to check what quantities have been approved follow the steps described below. The requisition will not stay at the “Outstanding” status very long because as soon as it reaches Outstanding status the system will automatically begin sending the instructions to the various warehouses and suppliers to begin preparing the shipments. Once all those instructions have been sent to warehouses and suppliers the Requisition will move to “Completed” status (for certain configurations there are other steps between Outstanding and Completed see earlier note in section 5.5) this does not mean that the shipments against this Requisition have been completed just that the Requisition processing step has completed. To track the individual status for the shipments generated as a result of the Requisition follow the steps described below.

<h2>Checking what Quantities/ Items have been approved</h2>

Once you receive the email telling you your Requisition has been approved you can go to the “Create/ Review Requisitions” page (see section 5 above for how to navigate to this page). Your requisition will now be a status “Complete” (or for certain configurations it may have another status such as “Fully Scheduled”, “Fully Agreed” etc. – see earlier notes above for details). To view the details, click the show icon.

[[File:Req_01.png]]

The following page will be displayed;

[[File:Req_02.png]]

The suggested Quantity is what was proposed by the system (this will be zero for manually created requisitions). The requested quantity is what was requested by the station and the approved quantity is what SkylogistiX has approved. You can make an excel copy of the confirmed quantities by pressing the excel icon button.

[[File:Req_002.png]]

<h2>Tracking the Individual Shipments against your Requisition</h2>

As previously described a single Requisition can generate multiple shipments depending on the source of supply and the stock availability. To view the individual shipments against your Requisition you should press the “Tracking” tab from the screen described above, or by clicking the drop down from the main ‘Create/ Review Requisitions’ page.

[[File:Req_03.png]]

'''OR'''

[[File:Req_04.png]]

This will show you all the shipment instructions generated as a result of your Requisition.

There are 3 different categories of shipment.

• '''Issue''' – Goods are to be issued from a Central/ Regional warehouse to your station.

• '''Purchase Order''' – The goods are being shipped directly from a supplier to your station.

• '''Return''' – Means you have a surplus and you should return these goods as instructed by SkylogistiX.

See below for an example of the screen you will see if you press the “Track” button as described above.

[[File:Req_05.png]]

In the above example the only type of shipments generated were Issues, there are three and the source in both cases is the Kuehne + Nagel Sutton Coldfield warehouse, we also see that have been fully received.

Against any issue you can view the details of the issue by pressing the “Show” icon against the Issue you want to view in more detail. This will then show you the status/ tracking details of the Issue plus all the items on the issue as illustrated below;

[[File:Req_06.png]]

In the above example on the header section we see that the issue has a Target Pick completion date of 24th November, and was actually picked and despatched on 24th November and arrived on the 25th November, a day late to the planned arrival date which was the 24th of November.

In the line details we see the Confirmed Requisition Quantity per item and as well as the quantity shipped and the quantity received.

Anything not shipped to you will go onto a back order and will be shipped via a separate issue which can be viewed in the same way as this the main issue.

SupplierCount Index

2021-07-28T17:15:39Z

Betsy:

Please use our [[http://wiki.skylogportal.com/index.php?title=Tips_and_Tricks '''Tips and Tricks''']] page for understanding how the SkySuite portal works and how to navigate faster and easier.

__TOC__

<h1>Supplier Inventory Counts</h1>

It contains the list of inventory counts already submitted (status complete), and due (status pending). The counts are listed with the most recent at the top, in the example above the top line show a count at “Pending” status which means it has not taken place yet but is expected to happen on the 7th of November (The expected date). Below this line you see all the previous counts will have all been completed or cancelled in the past. In case the count is not submitted before the next count is generated in the system, the count will be cancelled automatically.

You can view the detail of a report by pressing the Show Icon on the line you want to view.

[[File:Count_2.png]]

To report your stock levels, the due inventory counts will be in status pending, press on the edit option [[File:20200527 Edit.png|35px]]

[[File:20210728 Supplier stock count.png|796px]]

In this screen you are required to enter the “Actual Count Date” in which the inventory count took place

[[File:20210728 Suppliercount setdate.png|400px]]

Once you click “Save” you will be presented the page to enter the amount of stock you have counted against each item setup for your station, where you will be able to submit your count by entering the data directly in the portal or uploading from an Excel file upon configuration, if your location is setup for uploading the count details via an excel update you will be sent an email with it attached when the count is created.

The detail section will always display in pages of 10 at a time, you can move backwards and forwards through the pages with the arrow keys. You can also display everything on one screen by changing the drop down for “10” to “All” or select a certain number between 10 and 100 as well.

At the bottom of the page you will see the following buttons;

[[File:Count_9.png]]

• '''Upload Completed Count Sheet''' – If the supplier is setup to accept population of the count via an excel upload this will be presented to you, please follow the steps when clicked on uploading the completed document.

• '''View Uploaded File Errors''' – Again only visible for suppliers that upload counts via excel, this will detail any errors once you have attempted an upload.

• '''Save and Continue''' - Allows you to save what you have entered but will leave you in the screen.

• '''Save and Exit''' – Saves anything you have entered but will exit the page and return you to the main “Inventory Count” page.

• '''Submit''' - Will save your work and mark the count as complete and change the status to “Complete” after this you will no longer be able to change any of the figures.

<h2>Adding an Item to a Count</h2>

The list of items shown on the count detail page should include all the items you are expected to have at your location. If, however you have an item that is not showing you can add it with the add item button at the top of the page, provided there is a link between item an supplier. If the item does not appear on the list, please report to the Material Controller.

[[File:Count_10.png]]

This will display the following;

[[File:20210728 Additem Suppliercount.png|621px]]

Press the “Select Stock Item” button to search and choose the item you want to add. (Use the three dots under “Code” or “Description” to filter for a specific item) then click “Select”.

[[File:Count_12.png|700px]]

Once the item is added you can then fill in the “Float” and “Backup” quantities.

<h2>Submitting a Count</h2>

<h3><u>Submitting via the portal</u></h3>

As mentioned previously to submit a count to Skylogistix for review you simply press the Submit button at the bottom of the page, once you have entered quantities for all items. Until you do this the count is '''NOT''' marked as complete, and doesn’t move to the next stage thus you will continue to get email reminders that your count is overdue.

If you haven’t entered a figure for every item, you will see the message shown below and the count will not be submitted. You will then need to enter the missing figures and click submit again.

[[File:Count_13.png]]

Once you have successfully submitted the count you will be returned to the main page that lists all your counts and you should see that the count is now marked as “Complete”, You will now no longer be able to edit the count and you should receive an email confirming that the count has been submitted.

After a while the status will also change to “Under Review” and you will receive an email telling you that the count has been submitted successfully, which means SkylogistiX is reviewing the figures you entered.

<h3><u>Submitting via a count sheet</u></h3>

If decide to upload a count sheet instead of manually entering quantities you '''<u>MUST</u>''' download a copy from the actual count date page, or from the bottom bar of the count, as each excel document is unique to each count thus cannot be used on other counts.

You will be presented with the below sheet once you open the excel document, this is all the items associated with your station, and each line requires a quantity to be entered;

[[File:Stock_Count_Excel_1.PNG]]

There is also two other sheets in the document, 'User' and 'Item Reference'

[[File:Stock_Count_Excel_4.PNG]]

The 'User' sheet is to enter items not referenced on the main sheet, i.e. items that have been incorrectly sent to your location which you do not use but still need to recorded, simply enter the code and quantities.

[[File:Stock_Count_Excel_2.PNG]]

'Item Reference' sheet is just all the items the airline you are counting for has setup in the SkyLog system for you to locate item codes if required for the 'User' sheet.

Once the count document is completely filled out you can then upload it into the specific count you downloaded it from, in the 'Inventory Counts' page, click the pencil icon and select 'Upload Completed Count Sheet' where you can then select the document from your PC.

[[File:Stock_Count_Excel_5.PNG]]

Once uploaded all quantities will be listed against the items in the SkyLog screen, if they are not then you need to click 'View Uploaded File Errors' button at the bottom the count screen to idenify the issues with the sheet, fix and reupload.

File:20210728 Additem Suppliercount.png

2021-07-28T17:11:08Z

Betsy: Page displayed when adding an item to a stock count

== Summary ==
Page displayed when adding an item to a stock count

SupplierCount Index

2021-07-28T15:48:31Z

Betsy: Created page with "Please use our http://wiki.skylogportal.com/index.php?title=Tips_and_Tricks '''Tips and Tricks''' page for understanding how the SkySuite portal works and how to navigate..."

File:20210728 Suppliercount setdate.png

2021-07-28T15:06:50Z

Betsy: Set date on a supplier stock count

== Summary ==
Set date on a supplier stock count

File:20210728 Supplier stock count.png

2021-07-28T15:03:36Z

Betsy: SupplierCount page, to select the relevant count in pending status

== Summary ==
SupplierCount page, to select the relevant count in pending status

TransportOrder Index

2021-06-11T17:26:55Z

Betsy:

TransportOrder Index

2021-06-11T17:16:40Z

Betsy: Created page with "<!-- Status 1 – “Provisional” is where the order is still in the progress of creation. This step is typical if we are holding the order because we know there will be oth..."

WarehouseTransfer IWTTransportChainsIndex

2021-06-11T15:42:20Z

Betsy: Created page with "We have WarehouseTransferLink table which merely links two warehouses together (saying which one is From, which one is To and is the link is active). The actual transport para..."

We have WarehouseTransferLink table which merely links two warehouses together (saying which one is From, which one is To and is the link is active). The actual transport parameters are stored in table WarehouseTraqnsferTransport. Each record in the WarehouseTraqnsferTransport table needs to be linked to a record in the WarehouseTransferLink. Now the + button on the index page merely creates a record in the WarehouseTransferLink to which you then need to add actual transports. The confusion here is that the index grid shows combined data from both tables whilst the + button can only add to one of them (WarehouseTransferLink) and the other one (WarehouseTraqnsferTransport) needs to be populated from the edit page

StockItem Index

2021-03-29T16:24:37Z

Betsy:

'''Please use our [[Tips and Tricks]] page for understanding how the SkySuite portal works and how to navigate faster and easier.'''

__TOC__

<H1>Stock Item Summary</H1>

Stock Item creation can vary airline to airline so this page will detail the basic overview of stock item creation; for airline specific setup please refer to documentation which would have been supplied to your airline.

Stock Items within SkySuite are the products you order from suppliers, distribute and use onboard your fleet of aircraft, catering units or in lounges / stationery locations. Because of this these items require detailed setup to ensure the smooth operation of ordering and distributing the item into your network.

Once items are created only certain fields will be editable, so please ensure that the data entered is correct, if you experience any issues while setting up items please contact the SkySuite support via the ticketing system (located in the drop down of your user profile).

<h1>Setup of New Stock Items</h1>

To start the process of creating a stock item within SkySuite you will need to navigate to the main 'Stock Item' page in SkySuite, here you will be able to view and edit existing items or create a new one. In some airlines the creation of items is done in the airline master data system and the details are then sent via interface to SkySuite. Usually items created via an EDI interfaces will initially have a "Provisional" status because not all the information needed by SkySuite is available in the Interface. To complete the set up and set the Item to "Current" status you should click on the pencil/edit icon [[File:Count_4.png]]. For Airlines where there is no interface for the creation part parts, to create the new stock item click the add icon [[File:Count_10.png]];

Once clicked the following page will be displayed, the meaning of each field is detailed below.

[[File:Stock_Items_2.PNG|500px]]

'''Note: As you can see some fields are optional but these do depend on whether your Airline requires them so please check before leaving them blank.'''

<h2>Explanation of Fields</h2>

• '''Item Code''' – This is the Stock Items SKU, this must match the warehouses and the Airline's financial system item code setup. The Item code can be Alpha/Numeric and have up to a maximum of 20 characters.

• '''Item Description''' – A brief description of what the item is for ease of searching, identifying etc. Note: Maximum characters that can be used is 50.

• '''Technical Description''' – A detailed description of the item which could include manufacturing information and/or technical specifications. An unlimited amount of text can be entered here.

• '''Search Code''' – This is a Search code that can be used to ease searching for the item in SkySuite, up to a maximum of 20 characters be used.

• '''Item Status''' – This will be defaulted to 'Provisional' during setup, and it is not possible to edit until the item is fully set up. Later when you move the status from 'Provisional' to 'Current', the system will check and ensure that all mandatory information for the item has been entered, if this is not the case you cannnot change the status from 'Provisional'. Whilst in a 'Provisional' status the item cannot be ordered or used.

• '''No-Fly Item''' – Used by some airlines this identifies items which are required onboard and if not the flight is grounded thus maintaining sufficient inventory levels of this item are paramount.

• '''Item Group''' – The main group the item identifies under, these could be Alcohol, Chinaware etc. The Item Groups are generic and maintained by SkylogistiX and are not airline specific and cannot therefore be amended by you.

• '''Item Category''' – More detailed than the 'Item Group', these categories are defined by your airline ([[AnalysisCodes_ItemCategoriesIndex|Item Categories Setup]]) and could be used in any way the Airline see fit. They can be used to group/sort and report on items.

• '''Item Class''' – Another airline specific field which can be defined by your airline and could be used in any way the Airline see fit. They can be used to group/sort and report on items.

• '''Item Type''' – Another airline specific field which can be defined by your airline and could be used in any way the Airline see fit. They can be used to group/sort and report on items.

• '''Item Loading Group''' – This is to used by some airlines to split outbound orders for customs reasons or to split outbound container loading into different groups/types of materials.

• '''Disposable''' – Set to 'Yes' if the item can only be used one time and is either fully consumed or needs to be be thrown away after use? Set to 'No' if the item is Rotable and can be used more than once, for example some chinaware, glassware, metal cutlery or technical equipment such as trolleys/carts, Drawers etc.

> '''Number of Uses''' - If you selected 'No' for "Disposable" then you will need to identify how many times you expect that the item can be used before it is too worn or damaged and needs to be scrapped.

• '''Perishible''' – The shelf life of the product, note that this is not just food or drink this could be items such as toothpastes.

> '''Shelf Life (Days)''' - If you selected 'Yes' for "Perishible" then you will need to identify how long the item can be kept for before it reaches its expiry date and is no longer safe to use.

• '''Climate Requirements''' – Items requiring no special temperature control when stored should be set to 'Regular' otherwise set to 'Freezer' or 'Refrigerated'

• '''Country of Origin''' – The country that the item was manufactured in, note this may be used by your airline for proforma invoices and other customs documentation thus it is required to be accurate otherwise shipments may get delayed due to customs holding the import. This is the original country of manufacture and not the country where the goods are shipped from.

• '''Stock Unit''' – This is the base unit of measure for the item. All reports and transactions will be recorded in this unit.

• '''Loading Unit''' – When loaded onto the aircraft which unit of measure is the item identified as. This can be different to the stocking Unit. For example most USA based airlines have a stocking unit of 'Case' but their flight loading quantities and specifications are in 'Eaches'.

> '''Conversion Factor''' - This is the conversion factor from the specified stocking to loading unit you have selected for forecasting purposes.

• '''Stocking Unit Weight''' – The weight of one stocking unit of the item. If the stocking unit is a 'Case' or other unit that includes outer packaging then this weight is the gross weight including the weight of the packaging.

> '''Weight Unit''' - The unit weight used e.g. KG or LB.

• '''Free Of Charge''' – This is used to denote that the item is Free of Charge and therefore no costs are expected in any financial interfaces to the Airline.

• '''GL Account Category''' – GL (General ledger) Account Categories are used when there are interfaces between SkySuite and the Airline’s financial systems. The GL Account Category maps to the GL Account code in the airlines system to which transactions for that GL Category of item should be posted. Please follow this [[Station_AccountCategoryIndex|'''link''']] for more information about GL Account Categories.

• '''Item Cost''' – The cost of the item (Note: This price will be used in purchase orders if a contract price is not defined) and will also be used for all GL transactions posted to the Airlines financial systems. Depending on the Airline Attributes defined in SkySuite this cost can be updated, every time new inventory is received, based on a recalculated weighted average.

> '''Currency''' - The currency in which the item cost is expressed. This is not necessarily the currency in which the item is purchased. The currency recorded here will be the currency in which transactions posted to the Airlines's GL system will be made.

• '''Buyer''' – Responsible user that negotiates contracts (procurement activity) for this item.

• '''Material Controller''' – Responsible user that manages the inventory level and raises purchase orders for this item.

• '''Bonded''' – Identifies whether the item is held under bond in teh distribution centres..

• '''Item Replaces''' – If this item is new and will completely replace an already existing item you can select it here.

<h2>Submitting the new Stock Item</h2>

Once all the above fields are filled in correctly you can then save the item, any fields that were not filled in by accident but are mandatory will be flagged to you when attempting to save, but if successful the following will be displayed;

[[File:Stock_Items_3.PNG|500px]]

When saved the item still cannot be used for planning as additional data is required which will be presented once the 'Save' button is clicked.

[[File:Stock_Items_4.PNG|1000px]]

<h2>Additional Setup</h2>

<h3><u>Item Packs</U></h3>

Item packs define how the stock item is packed by the supplier and shipped to your stations or warehouses, setting this data up enables SkySuite to take the measurements and weights to calculate order weights and size when mixed with other items.

Depending on what 'Stock Unit' you selected in the above 'Explanation of Fields' section this will be pre-populated as the first record (Level 1) as shown in the screenshot above.

To add the remaining packs simply click the add icon [[File:Count_10.png]] and fill in the required data, for a detailed break down on how item packs work please see the [[StockItem_ItemPacksIndex|Item Packs Wiki page '''here''']].

[[File:Stock_Items_5.PNG|750px]]

• '''Item Pack Structure''' – Depending on how the airline purchases and distributes items they could have multiple pack combinations, this dropdown enables you to distinguish between them. It is possible that the same item is being procured from different suppliers, and pack structures are different per supplier. In that case you could use Structure A for the default supplier and B for the alternative supplier.

• '''Lower Level Qty''' – This is the quantity in the pack size below this i.e. an each (a single unit) would have a lower level quantity of 1 but for a case it could be 12 because 12 eaches create a case. Then for a pallet the lower level quantity might only be 10 as it is the number of cases in the pallet, not the number of eaches.

• '''Default For Issue''' - Only one of the item packs can be the default for issuing stock to a destination thus when orders are raised the quantity requested in Stocking Units would be rounded to this pack size.

• '''Pack Weight''' - The weight of the pack including packaging.

• '''Pack Volume''' - Prefered unit of measure to be used is CM. Pack dimensions are required to be filled in so a cubic volume is calculated.

Please see below example of a complete item pack setup;

[[File:Stock_Items_6.PNG|1000px]]

'''Note: The blue pin icon can be used to quickly change the 'default for issue', the red cross will remove that certain pack level and the pencil icon lets you edit the existing record.'''

<h3><u>Item Warehouses</u></h3>

The ItemWarehouse table defines the warehouses in which that item can be stored, every item must have at least one ItemWarehouse record but can have more. Until at least one ItemWarehouse records exists for the Item you will not be able to change the Status from 'Provisional'. To create a new ItemWarehouse record press the Add icon [[File:Count_10.png]]

[[File:Stock_Items_7.PNG|500px]]

The image above shows the fields requiring more data,

• '''Warehouse''' – The relevant warehouse where stock will be held. You will need to make multiple records if the stock is stored at more than one warehouse.

• '''Direct Delivery''' – Set to 'Yes' if stock is usually delivered to this warehouse directly from the supplier, if the Warehouse is usually replenished from another warehouse then set this field to 'No'.

> '''Parent Warehouse Code''' - If stock is not delivered directly to this warehouse and instead it is first delivered to a consolidation point or another warehouse then you will need to select the parent warehouse. For warehouses that are flagged as Direct delivered from teh Supplier then this field will not be visible.

• '''Security Stock (Days)''' – Minimum number of days of stock required at the warehouse, also know as buffer or safety stock.

• '''Is the Item Contracted''' – Is the item associated with a contractm, set to no if the item can be freely ordered without a PO Contract in place.

• '''Minimum Order Quantity''' – Minimum amount of stock that can be ordered from the Supplier is a single Purchase Order.

• '''Economic Order Quantity''' – The ideal order quantity that should be purchased to minimize inventory costs such as holding costs, shortage costs, and order costs. This then becomes the round up/down integer when stock is ordered.

• '''Targeted Days Between Orders''' – If a supplier delivers regularly then this field can be populated with the optimum or desired days between each order.

• '''No Days Total Lead Time''' – The time taken from the supplier to the warehouse, this is the total lead time (Manufacture plus transport) and is used as a default for planning if individual manufacture and transport lead times are not defined against the ItemSupplier or PO Contract..

• '''Item Status''' – Separate status to the stock item status but cannot be updated until setup is complete.

• '''Buyer''' – Same as the stock item setup but allows you to set a different buyer per warehouse.

• '''Material Controller''' – Same as the stock item setup but allows you to set a different planner per warehouse.

• '''Warehouse Demand Forecast Source''' – This is for defining which forecast source will be used in the MRP routines for the item at this specific warehouse, there are three options which will greatly affect planning if the wrong one is selected so please ensure you select the one that is most appropriate for this item/warehouse and your Airline set up.

• Auto-Calculated demand forecast based on historical transactions - As per the name this option uses historic transactions to calculate how much stock is required for the future.

• LogistiX Flight Schedule Network Analysis - The state of the art forecast algorithm developed by SkyLogistiX which takes your airlines flight schedule, passenger numbers, bill of material data and other complex data to accurately predict how much stock is required tfor the future.

• Third Party forecast loaded and editable by user via the portal - A manually crafted forecast can be created in Excel or any other 3rd party system capable to produce CSV file and then that file is uploaded into SkySuite for the item to forward plan.

Once all these fields are populated it can be saved and you can move onto the ItemSupplier setup.

<h3><U>Item Suppliers</U></h3>

Next is to setup the supplier that deliver stock of this item to either a warehouse or directly to a station, simply navigate to the 'Supplier' tab and click [[File:Count_10.png]] to create a new record.

[[File:Stock_Items_9.PNG|750px]]

• '''Supplier''' – Suppliers for your airline should be setup prior to an item being created so can be selected from the pop up.

• '''Supplier's Item Number''' – Your supplier may have a separate internal code for this item and if enetered here would be referenced on purchase order documents for supplier ease.

• '''Manufacturer''' – The manufacturer of the item might not be the supplier, who may instead just be a broker, thus for customs reasons the manufacturer should be selected.

• '''Manufacturing Lead Time (Days)''' – The number of days required by the supplier to completely manufacture this item from start to finish.

• '''Over-Receipt Threshold''' – Depending on if over receipting is enable for your airline then this threshold enables you to provide a maximum amount that can be over receipted.

• '''Supplier Held Buffer Stock''' – Your airline may have agreed with a vendor to hold in the supplier premises a specific number of units for this item as an emergency backup if required urgently.

• '''Current''' – Depending on whether the item is currently being supplied by this supplier it should be selected whether it is an active link or not.

Once this is filled out and saved, you are then required to complete further setup in the 'Item Suppliers' page for the record that now exists. Navigate to 'Reference Data' -> 'Stock Item' -> 'Item Suppliers' and search for your item and supplier combination, and click the pencil edit button.

[[File:Stock_Items_10.PNG|300]]

Please follow the [[ItemSupplier_Index|Item Supplier setup page here]] for a complete guide on this.

<h3><U>Images</U></h3>

SkySuite allows you to upload multiple pictures of your item, this can help identify stock for caterers in the 'Item Catalogue' page. To upload an image simply click the new record button and select a picture from your PC, you can then provide a description for the picture, and also set it to be the default if you are uploading multiple images.

[[File:Stock_Items_11.PNG|300]]



<h3><U>Customs Data</U></h3>

As the name suggest this data is used to fulfill requirements from customs autorities, and for airlines generating the proforma invoice in Skylog, the information would be used. you are able to confirm which exercise type the item falls under (if any).

[[File:Stock_Items_12.PNG|750px]]

• '''Excise Type''' – The tax type that is associated with the item, you will need to select the most relevant from the drop down.

• '''Alcohol %''' – Percentage of alcohol per single item.

• '''Sugar %''' – Percentage of sugar per single item.

• '''Sugar Weight''' – Weight of sugar per single item.

• '''Items Per Unit''' – The amount of items/components that are associated with the item.

• '''Item Size''' – Size of the item that could be relevant with customs authorities.

• '''Commodity Code''' – This would be a tax code associated with the item, most airlines record here the HS (Harmonized System code)

• '''Additional Customs Info''' – If there is any additional information that customs may require you can detail it here.

Once complete you can click save and the item is ready to be activated.

<h2>Activating the Stock Item</h2>

Now you have setup all the data associated with the stock item in SkySuite you will need to set the relevant status, if the item is not yet in circulation or does not need to be ordered from a supplier yet the status can stay as 'Provisional', but if the item needs to be purchased and/or distributed within the network immediately you need to set the status to 'Active'.

'''Note: There are two other statuses which are covered below in "Updating a Stock Item"'''

<h2>Updating a Stock Item</h2>

Once an item is active you can still update most information for that item, as and when data is required to be updated due to different circumstances.

One of these circumstances could be that the item is not going to be ordered anymore and will be replaced with another item, in this case if you still have stock at your warehouse to distribute but do not want to purchase more of it from a supplier you can set the status to 'Phase Out', but once the stock has run out at the warehouse and is not being used anywhere in the network you can set the status to 'Obsolete'.

PurchaseOrder POContractIndex

2021-03-05T17:19:26Z

Betsy:

<accesscontrol>SLXGLOBALADMIN,SLXLOCALADMIN,SLXOPERATIONAL,AIRLINEADMIN,AIRLINEOPS,AIRLINEMANAG</accesscontrol>

Please use our [[http://wiki.skylogportal.com/index.php?title=Tips_and_Tricks '''Tips and Tricks''']] page for understanding how the SkySuite portal works and how to navigate faster and easier.

__TOC__
<h1>PO Master Contract (POMC)</h1>

It is the base/master agreement against which multiple call-offs (CPOs) can be placed with the supplier. The contract will contain the commercial agreement applicable to all subsequent POs: agreed prices, length, INCOTERMS and quantities. The advantage is that once the POMC is setup by the customer’s buyer (or a SLX Control Tower and approved by the customer) the Material Controller can place Contracted POs (CPOs) against the contract without individual CPOs approval required, unless, there are other approval conditions like CPO being subject to further approval based on value.

<h1>Create a New Contract</h1>

To create a new contract go to Daily Activities / MRP & Purchase Ordering / Create/Review PO contracts.

[[File:20210305 Create Review PO Contracts.png|400px]]

Press [[File:PlusPlus.png]], then press [[File:20210305 Select supplier.png]].

Search for the supplier you are creating the contract for, you can use the filter options, and then press on '''Select'''

[[File:20210305 Select supplier screen.png|600px]]

<h2>Contract Header information</h2>

A new page will be displayed for you to complete general information about the contract:

[[File:20210305 New PO Contract header.png|400px]]

{| class="wikitable"
|-
! ''Parameter''
! ''Mandatory?''
! ''Description''
|-
| Contract Reference
| Yes
| This reference is manually entered, and must be unique. Will be printed on the PDF document (header). It is a free text of maximum 16 caracters
|-
| Previous Contract
| No
| You can select from all All existing Contract References to link to the contract being created. This information is for reference and it does does not trigger further actions in SkyLog.
|-
| Contract Start date
| Yes
| First day from which CPOs that reference to the Contract can be created.
|-
| Contract End date
| No
| Last day until which CPOs that reference to the Contract can be created. To be left blank, if a Contract should be valid for “indefinite”
time. Must be later than the ‘Contract Start Date’
|-
| Goods to be shipped to
| Yes
| A contract can be created for deliveries to:

• ‘Anywhere’ can be chosen if the CPOs referencing to the Contract can be created for all warehouses or stations setup for the customer, applying the same commercial conditions (prices, MOQ, etc)

• Warehouse: Select the relevant warehouse.

• Station: Select the relevant station
|-
| Terms and Conditions
| Yes
| Should include INCOTERMS and delivery point and any other commercial relevant conditions. It will be printed on PDF document.
|-
| Notes
| No
| Optional internal comments. They can be read by all users with ‘View Contract’ access rights. It can include details of combined MOQs.
|}

Once all mandatory fields have been entered press [[File:20210305 Save No disk.png|40px]]

It is important also to select the delivery terms, this are a requirement for operations with interfaces to the customer finance system.

[[File:20210305 Delivery terms.png|700px]]

<h2>Purchase Order Contract Details</h2>

Once the ‘Purchase Order Header Data’ is entered and ‘Save’ button is pressed, it will be possible to enter the ‘Purchase Order Contract Details’ meaning the item line information.

Note: It is only possible to add items to a POMC as long as it is in status ‘Provisional’ (for Airline Management users it is still possible in status ‘Awaiting Approval’, if the approval process applies).

By pressing [[File:PlusPlus.png]] new items can be added to the Contract. Select the item to be added, you can use the filters to find the relevant products. The window will display items that meet the following characteristics:

• Linked to the specific supplier

• (Stock Item) status ‘Provisional’ or ‘Current’

[[File:20210305 Select item.png|800px]]

After the item has been selected some purchase parameters need to be completed.

[[File:20210305 Add PO Contract Detail.png|500px]]

{| class="wikitable"
|-
! ''Parameter''
! ''Mandatory?''
! ''Selection Options''
! ''Description''
|-
| Maximum Quantity
| No
| Number (max.14 digits)
| Maximum quantity which can be called-off from the Contract with referenced CPOs. It refers to the maximum quantity that the supplier
committed to deliver under the agreed terms. The unit is always the ‘Stock Unit’ which is shown when selecting the item. Once the quantity on the referenced CPOs sum up the Maximum quantity, the contract will be terminated in the system.

If the maximum quantity is left blank, means there is no limit for the quantity to be ordered against the Contract. Normally POs with an end Date have no maximum quantity assigned.
|-
| Cost
| No
| Number (max. 6 decimal digits)
| It refers to the monetary value for the Stock Unit’. Select also the currency from the dropdown list.
|-
| Lead time
| No
| Number in days (max. 5 decimal digits)
| As agreed with the supplier. It refers to the time between the CPO is placed and the expected delivery date.
|-
| Minimum Order Quantity
| No
| Number (maximum 10 digits)
| As agreed with the supplier. POs will be created in multiples of the MOQ
|-
| Economic Order Quantity
| No
| Number (maximum 10 digits)
| As agreed with the supplier. For example, how many items will fit in a truck / sea container
|-
| Delivery Terms
| No
| Text (maximum 3 characters)
| INCOTERMS, as agreed with the supplier
|-
| Comment
| No
| Text (maximum 128 characters)
| Free text field for additional information
|}

Once all relevant fields have been completed and reflect the commercial agreement with the supplier, press [[File:SaveSave.png]] and repeat the process for all the items to be added to the contract.

<h2>Tax Categories</h2>

In some cases it will be required to assign tax categories to the different items within the Contract. The first step is to define the tax categories by pressing [[File:20210305 Tax Categories button.png]].

Press [[File:PlusPlus.png]] to add new categories. A new line will be displayed. Define a tax code easy to identify, a description and the percentage applicable. You can also remove lines by pressing [[File:20210305 X delete.png]]

[[File:20210305 Add Tax Categories.png|700px]]

Once you have added all the required Tax categories press [[File:20210305 Save changes.png|100px]]. You can then assign the tax categories created to the different items in the contract.

[[File:20210305 Assign tax categories.png]]

Once you have added all the items, and if required assigned all tax categories press [[File:20210120 submit.png|90px]].

<h1>Activate PO Contract</h1>

Depending on the role and the customer configuration, when you press [[File:20210120 submit.png|90px]], the contract will either go to a next approval stage, or change status to Approved. Once the contract is approved, Skylog will

Depending on the ‘Contract Start Date’ has already been reached the status will further change from ‘Approved’ to ‘Active’.

[[PurchaseOrder_ContractsAwaitingApproval|''For more details regarding PO Contracts Approval click this link'']]

<h1>Editing PO Contracts</h1>

Press [[File:EditEdit.png]] of the specific PO Contract at the ‘Create/Review PO Contracts’-page all header and line details can be amended / updated.

Note: Dependent on the user role the user might be able to edit POMC’s with status ‘Provisional’ only.

Once the PO contract is status Approved / Active, tracking notes can be added on the [[File:20210305 Tracking notes.png|90px]] tab. To create a new note use the ‘Add’-button and enter a value for ‘Summary’ and ‘Comment’ as those fields are mandatory.

Other than that files (with maximum upload size of 4 MB) can also get uploaded. There no restriction regarding the file type. Notes will be displayed at the ‘PO Tracking’-page and are used for internal purposes only.

To Download files attached to a tracking note press [[File:20210121 Download.png]].

<h1>View Existing Documents</h1>

Once the contract has been approve Skylog generates some documents depending on the customer configuration, such as a copy of the contract, tariffs and conditions. All documents can be downloaded from the Existing documents section, which can be accessed from the expand/collapse, view or edit icons.

[[File:20210305 Existing documents.png|900px]]

Once changes at the header and/or line level have been conducted an updated document can be created.
The document contains all the information regarding delivery terms, contact details, purchase order contract details, etc.
To create the document press [[File:20210305 Generate PDF.png|110px]] at the bottom of the page. If the PDF creation has been successful the
document can be viewed via the ‘Existing Documents’-button.

After the Document has been generated all existing documents will be listed and can get downloaded as a PDF (and send to the supplier
afterwards)

Note: The most current document will always be displayed at the top of the list.

<h1>PO Contract termination</h1>

A PO contract will be terminated if one or more of the following conditions is met:

• Maximum quantity has been reached

• Contract End date is in the past

• Contract is terminated through the portal

To terminate a PO Contract through the portal, press [[File:EditEdit.png]] on the relevant contract. Press [[File:20210305 Terminate contract.png]] at the bottom of the page. A dialog box will be displayed for you to add reason for termination and confirm the action.

File:20210305 Terminate contract.png

2021-03-05T17:18:42Z

Betsy: Terminate Contract button

== Summary ==
Terminate Contract button

File:20210305 Tracking notes.png

2021-03-05T17:05:53Z

Betsy: Tracking notes tab

== Summary ==
Tracking notes tab

File:20210305 Generate PDF.png

2021-03-05T17:00:40Z

Betsy: Generate PDF PO contracts

== Summary ==
Generate PDF PO contracts

PurchaseOrder POContractIndex

2021-03-05T16:57:20Z

Betsy:

<accesscontrol>SLXGLOBALADMIN,SLXLOCALADMIN,SLXOPERATIONAL,AIRLINEADMIN,AIRLINEOPS,AIRLINEMANAG</accesscontrol>

Please use our [[http://wiki.skylogportal.com/index.php?title=Tips_and_Tricks '''Tips and Tricks''']] page for understanding how the SkySuite portal works and how to navigate faster and easier.

__TOC__
<h1>PO Master Contract (POMC)</h1>

It is the base/master agreement against which multiple call-offs (CPOs) can be placed with the supplier. The contract will contain the commercial agreement applicable to all subsequent POs: agreed prices, length, INCOTERMS and quantities. The advantage is that once the POMC is setup by the customer’s buyer (or a SLX Control Tower and approved by the customer) the Material Controller can place Contracted POs (CPOs) against the contract without individual CPOs approval required, unless, there are other approval conditions like CPO being subject to further approval based on value.

<h1>Create a New Contract</h1>

To create a new contract go to Daily Activities / MRP & Purchase Ordering / Create/Review PO contracts.

[[File:20210305 Create Review PO Contracts.png|400px]]

Press [[File:PlusPlus.png]], then press [[File:20210305 Select supplier.png]].

Search for the supplier you are creating the contract for, you can use the filter options, and then press on '''Select'''

[[File:20210305 Select supplier screen.png|600px]]

<h2>Contract Header information</h2>

A new page will be displayed for you to complete general information about the contract:

[[File:20210305 New PO Contract header.png|400px]]

{| class="wikitable"
|-
! ''Parameter''
! ''Mandatory?''
! ''Description''
|-
| Contract Reference
| Yes
| This reference is manually entered, and must be unique. Will be printed on the PDF document (header). It is a free text of maximum 16 caracters
|-
| Previous Contract
| No
| You can select from all All existing Contract References to link to the contract being created. This information is for reference and it does does not trigger further actions in SkyLog.
|-
| Contract Start date
| Yes
| First day from which CPOs that reference to the Contract can be created.
|-
| Contract End date
| No
| Last day until which CPOs that reference to the Contract can be created. To be left blank, if a Contract should be valid for “indefinite”
time. Must be later than the ‘Contract Start Date’
|-
| Goods to be shipped to
| Yes
| A contract can be created for deliveries to:

• ‘Anywhere’ can be chosen if the CPOs referencing to the Contract can be created for all warehouses or stations setup for the customer, applying the same commercial conditions (prices, MOQ, etc)

• Warehouse: Select the relevant warehouse.

• Station: Select the relevant station
|-
| Terms and Conditions
| Yes
| Should include INCOTERMS and delivery point and any other commercial relevant conditions. It will be printed on PDF document.
|-
| Notes
| No
| Optional internal comments. They can be read by all users with ‘View Contract’ access rights. It can include details of combined MOQs.
|}

Once all mandatory fields have been entered press [[File:20210305 Save No disk.png|40px]]

It is important also to select the delivery terms, this are a requirement for operations with interfaces to the customer finance system.

[[File:20210305 Delivery terms.png|700px]]

<h2>Purchase Order Contract Details</h2>

Once the ‘Purchase Order Header Data’ is entered and ‘Save’ button is pressed, it will be possible to enter the ‘Purchase Order Contract Details’ meaning the item line information.

Note: It is only possible to add items to a POMC as long as it is in status ‘Provisional’ (for Airline Management users it is still possible in status ‘Awaiting Approval’, if the approval process applies).

By pressing [[File:PlusPlus.png]] new items can be added to the Contract. Select the item to be added, you can use the filters to find the relevant products. The window will display items that meet the following characteristics:

• Linked to the specific supplier

• (Stock Item) status ‘Provisional’ or ‘Current’

[[File:20210305 Select item.png|800px]]

After the item has been selected some purchase parameters need to be completed.

[[File:20210305 Add PO Contract Detail.png|500px]]

{| class="wikitable"
|-
! ''Parameter''
! ''Mandatory?''
! ''Selection Options''
! ''Description''
|-
| Maximum Quantity
| No
| Number (max.14 digits)
| Maximum quantity which can be called-off from the Contract with referenced CPOs. It refers to the maximum quantity that the supplier
committed to deliver under the agreed terms. The unit is always the ‘Stock Unit’ which is shown when selecting the item. Once the quantity on the referenced CPOs sum up the Maximum quantity, the contract will be terminated in the system.

If the maximum quantity is left blank, means there is no limit for the quantity to be ordered against the Contract. Normally POs with an end Date have no maximum quantity assigned.
|-
| Cost
| No
| Number (max. 6 decimal digits)
| It refers to the monetary value for the Stock Unit’. Select also the currency from the dropdown list.
|-
| Lead time
| No
| Number in days (max. 5 decimal digits)
| As agreed with the supplier. It refers to the time between the CPO is placed and the expected delivery date.
|-
| Minimum Order Quantity
| No
| Number (maximum 10 digits)
| As agreed with the supplier. POs will be created in multiples of the MOQ
|-
| Economic Order Quantity
| No
| Number (maximum 10 digits)
| As agreed with the supplier. For example, how many items will fit in a truck / sea container
|-
| Delivery Terms
| No
| Text (maximum 3 characters)
| INCOTERMS, as agreed with the supplier
|-
| Comment
| No
| Text (maximum 128 characters)
| Free text field for additional information
|}

Once all relevant fields have been completed and reflect the commercial agreement with the supplier, press [[File:SaveSave.png]] and repeat the process for all the items to be added to the contract.

<h2>Tax Categories</h2>

In some cases it will be required to assign tax categories to the different items within the Contract. The first step is to define the tax categories by pressing [[File:20210305 Tax Categories button.png]].

Press [[File:PlusPlus.png]] to add new categories. A new line will be displayed. Define a tax code easy to identify, a description and the percentage applicable. You can also remove lines by pressing [[File:20210305 X delete.png]]

[[File:20210305 Add Tax Categories.png|700px]]

Once you have added all the required Tax categories press [[File:20210305 Save changes.png|100px]]. You can then assign the tax categories created to the different items in the contract.

[[File:20210305 Assign tax categories.png]]

Once you have added all the items, and if required assigned all tax categories press [[File:20210120 submit.png|90px]].

<h1>Activate PO Contract</h1>

Depending on the role and the customer configuration, when you press [[File:20210120 submit.png|90px]], the contract will either go to a next approval stage, or change status to Approved. Once the contract is approved, Skylog will

Depending on the ‘Contract Start Date’ has already been reached the status will further change from ‘Approved’ to ‘Active’.

[[PurchaseOrder_ContractsAwaitingApproval|''For more details regarding PO Contracts Approval click this link'']]

<h1>View Existing Documents</h1>

Once the contract has been approve Skylog generates some documents depending on the customer configuration, such as a copy of the contract, tariffs and conditions. All documents can be downloaded from the Existing documents section.

[[File:20210305 Existing documents.png|900px]]

<h1>Editing PO Contracts</h1>

Press [[File:EditEdit.png]] of the specific PO Contract at the ‘Create/Review PO Contracts’-page all header and line details can be amended / updated.

Note: Dependent on the user role the user might be able to edit POMC’s with status ‘Provisional’ only.

PurchaseOrder POContractIndex

2021-03-05T16:34:07Z

Betsy:

<accesscontrol>SLXGLOBALADMIN,SLXLOCALADMIN,SLXOPERATIONAL,AIRLINEADMIN,AIRLINEOPS,AIRLINEMANAG</accesscontrol>

Please use our [[http://wiki.skylogportal.com/index.php?title=Tips_and_Tricks '''Tips and Tricks''']] page for understanding how the SkySuite portal works and how to navigate faster and easier.

__TOC__
<h1>PO Master Contract (POMC)</h1>

It is the base/master agreement against which multiple call-offs (CPOs) can be placed with the supplier. The contract will contain the commercial agreement applicable to all subsequent POs: agreed prices, length, INCOTERMS and quantities. The advantage is that once the POMC is setup by the customer’s buyer (or a SLX Control Tower and approved by the customer) the Material Controller can place Contracted POs (CPOs) against the contract without individual CPOs approval required, unless, there are other approval conditions like CPO being subject to further approval based on value.

<h1>Create a New Contract</h1>

To create a new contract go to Daily Activities / MRP & Purchase Ordering / Create/Review PO contracts.

[[File:20210305 Create Review PO Contracts.png|400px]]

Press [[File:PlusPlus.png]], then press [[File:20210305 Select supplier.png]].

Search for the supplier you are creating the contract for, you can use the filter options, and then press on '''Select'''

[[File:20210305 Select supplier screen.png|600px]]

<h2>Contract Header information</h2>

A new page will be displayed for you to complete general information about the contract:

[[File:20210305 New PO Contract header.png|400px]]

{| class="wikitable"
|-
! ''Parameter''
! ''Mandatory?''
! ''Description''
|-
| Contract Reference
| Yes
| This reference is manually entered, and must be unique. Will be printed on the PDF document (header). It is a free text of maximum 16 caracters
|-
| Previous Contract
| No
| You can select from all All existing Contract References to link to the contract being created. This information is for reference and it does does not trigger further actions in SkyLog.
|-
| Contract Start date
| Yes
| First day from which CPOs that reference to the Contract can be created.
|-
| Contract End date
| No
| Last day until which CPOs that reference to the Contract can be created. To be left blank, if a Contract should be valid for “indefinite”
time. Must be later than the ‘Contract Start Date’
|-
| Goods to be shipped to
| Yes
| A contract can be created for deliveries to:

• ‘Anywhere’ can be chosen if the CPOs referencing to the Contract can be created for all warehouses or stations setup for the customer, applying the same commercial conditions (prices, MOQ, etc)

• Warehouse: Select the relevant warehouse.

• Station: Select the relevant station
|-
| Terms and Conditions
| Yes
| Should include INCOTERMS and delivery point and any other commercial relevant conditions. It will be printed on PDF document.
|-
| Notes
| No
| Optional internal comments. They can be read by all users with ‘View Contract’ access rights. It can include details of combined MOQs.
|}

Once all mandatory fields have been entered press [[File:20210305 Save No disk.png|40px]]

It is important also to select the delivery terms, this are a requirement for operations with interfaces to the customer finance system.

[[File:20210305 Delivery terms.png|700px]]

<h2>Purchase Order Contract Details</h2>

Once the ‘Purchase Order Header Data’ is entered and ‘Save’ button is pressed, it will be possible to enter the ‘Purchase Order Contract Details’ meaning the item line information.

Note: It is only possible to add items to a POMC as long as it is in status ‘Provisional’ (for Airline Management users it is still possible in status ‘Awaiting Approval’, if the approval process applies).

By pressing [[File:PlusPlus.png]] new items can be added to the Contract. Select the item to be added, you can use the filters to find the relevant products. The window will display items that meet the following characteristics:

• Linked to the specific supplier

• (Stock Item) status ‘Provisional’ or ‘Current’

[[File:20210305 Select item.png|800px]]

After the item has been selected some purchase parameters need to be completed.

[[File:20210305 Add PO Contract Detail.png|500px]]

{| class="wikitable"
|-
! ''Parameter''
! ''Mandatory?''
! ''Selection Options''
! ''Description''
|-
| Maximum Quantity
| No
| Number (max.14 digits)
| Maximum quantity which can be called-off from the Contract with referenced CPOs. It refers to the maximum quantity that the supplier
committed to deliver under the agreed terms. The unit is always the ‘Stock Unit’ which is shown when selecting the item. Once the quantity on the referenced CPOs sum up the Maximum quantity, the contract will be terminated in the system.

If the maximum quantity is left blank, means there is no limit for the quantity to be ordered against the Contract. Normally POs with an end Date have no maximum quantity assigned.
|-
| Cost
| No
| Number (max. 6 decimal digits)
| It refers to the monetary value for the Stock Unit’. Select also the currency from the dropdown list.
|-
| Lead time
| No
| Number in days (max. 5 decimal digits)
| As agreed with the supplier. It refers to the time between the CPO is placed and the expected delivery date.
|-
| Minimum Order Quantity
| No
| Number (maximum 10 digits)
| As agreed with the supplier. POs will be created in multiples of the MOQ
|-
| Economic Order Quantity
| No
| Number (maximum 10 digits)
| As agreed with the supplier. For example, how many items will fit in a truck / sea container
|-
| Delivery Terms
| No
| Text (maximum 3 characters)
| INCOTERMS, as agreed with the supplier
|-
| Comment
| No
| Text (maximum 128 characters)
| Free text field for additional information
|}

Once all relevant fields have been completed and reflect the commercial agreement with the supplier, press [[File:SaveSave.png]] and repeat the process for all the items to be added to the contract.

<h2>Tax Categories</h2>

In some cases it will be required to assign tax categories to the different items within the Contract. The first step is to define the tax categories by pressing [[File:20210305 Tax Categories button.png]].

Press [[File:PlusPlus.png]] to add new categories. A new line will be displayed. Define a tax code easy to identify, a description and the percentage applicable. You can also remove lines by pressing [[File:20210305 X delete.png]]

[[File:20210305 Add Tax Categories.png|700px]]

Once you have added all the required Tax categories press [[File:20210305 Save changes.png|100px]]. You can then assign the tax categories created to the different items in the contract.

[[File:20210305 Assign tax categories.png]]

Once you have added all the items, and if required assigned all tax categories press [[File:20210120 submit.png|90px]].

<h1>Activate PO Contract</h1>

Depending on the role and the customer configuration, when you press [[File:20210120 submit.png|90px]], the contract will either go to a next approval stage, or change status to Approved. Once the contract is approved, Skylog will

Depending on the ‘Contract Start Date’ has already been reached the status will further change from ‘Approved’ to ‘Active’.

[[PurchaseOrder_ContractsAwaitingApproval|''For more details regarding PO Contracts Approval click this link'']]

<h1>View Existing Documents</h1>

Once the contract has been approve Skylog generates some documents depending on the customer configuration, such as a copy of the contract, tariffs and conditions. All documents can be downloaded from the Existing documents section.

[[File:20210305 Existing documents.png|900px]]

PurchaseOrder ContractsAwaitingApproval

2021-03-05T16:32:45Z

Betsy:

File:20210305 Existing documents.png

2021-03-05T16:21:56Z

Betsy: Where to find existing documents related to a PO contract

== Summary ==
Where to find existing documents related to a PO contract

File:20210305 Approve - Reject PO Contracts.png

2021-03-05T16:05:36Z

Betsy: Options for approval / rejection

== Summary ==
Options for approval / rejection

PurchaseOrder POContractIndex

2021-03-05T15:58:01Z

Betsy:

<accesscontrol>SLXGLOBALADMIN,SLXLOCALADMIN,SLXOPERATIONAL,AIRLINEADMIN,AIRLINEOPS,AIRLINEMANAG</accesscontrol>

Please use our [[http://wiki.skylogportal.com/index.php?title=Tips_and_Tricks '''Tips and Tricks''']] page for understanding how the SkySuite portal works and how to navigate faster and easier.

__TOC__
<h1>PO Master Contract (POMC)</h1>

It is the base/master agreement against which multiple call-offs (CPOs) can be placed with the supplier. The contract will contain the commercial agreement applicable to all subsequent POs: agreed prices, length, INCOTERMS and quantities. The advantage is that once the POMC is setup by the customer’s buyer (or a SLX Control Tower and approved by the customer) the Material Controller can place Contracted POs (CPOs) against the contract without individual CPOs approval required, unless, there are other approval conditions like CPO being subject to further approval based on value.

<h1>Create a New Contract</h1>

To create a new contract go to Daily Activities / MRP & Purchase Ordering / Create/Review PO contracts.

[[File:20210305 Create Review PO Contracts.png|400px]]

Press [[File:PlusPlus.png]], then press [[File:20210305 Select supplier.png]].

Search for the supplier you are creating the contract for, you can use the filter options, and then press on '''Select'''

[[File:20210305 Select supplier screen.png|600px]]

<h2>Contract Header information</h2>

A new page will be displayed for you to complete general information about the contract:

[[File:20210305 New PO Contract header.png|400px]]

{| class="wikitable"
|-
! ''Parameter''
! ''Mandatory?''
! ''Description''
|-
| Contract Reference
| Yes
| This reference is manually entered, and must be unique. Will be printed on the PDF document (header). It is a free text of maximum 16 caracters
|-
| Previous Contract
| No
| You can select from all All existing Contract References to link to the contract being created. This information is for reference and it does does not trigger further actions in SkyLog.
|-
| Contract Start date
| Yes
| First day from which CPOs that reference to the Contract can be created.
|-
| Contract End date
| No
| Last day until which CPOs that reference to the Contract can be created. To be left blank, if a Contract should be valid for “indefinite”
time. Must be later than the ‘Contract Start Date’
|-
| Goods to be shipped to
| Yes
| A contract can be created for deliveries to:

• ‘Anywhere’ can be chosen if the CPOs referencing to the Contract can be created for all warehouses or stations setup for the customer, applying the same commercial conditions (prices, MOQ, etc)

• Warehouse: Select the relevant warehouse.

• Station: Select the relevant station
|-
| Terms and Conditions
| Yes
| Should include INCOTERMS and delivery point and any other commercial relevant conditions. It will be printed on PDF document.
|-
| Notes
| No
| Optional internal comments. They can be read by all users with ‘View Contract’ access rights. It can include details of combined MOQs.
|}

Once all mandatory fields have been entered press [[File:20210305 Save No disk.png|40px]]

It is important also to select the delivery terms, this are a requirement for operations with interfaces to the customer finance system.

[[File:20210305 Delivery terms.png|700px]]

<h2>Purchase Order Contract Details</h2>

Once the ‘Purchase Order Header Data’ is entered and ‘Save’ button is pressed, it will be possible to enter the ‘Purchase Order Contract Details’ meaning the item line information.

Note: It is only possible to add items to a POMC as long as it is in status ‘Provisional’ (for Airline Management users it is still possible in status ‘Awaiting Approval’, if the approval process applies).

By pressing [[File:PlusPlus.png]] new items can be added to the Contract. Select the item to be added, you can use the filters to find the relevant products. The window will display items that meet the following characteristics:

• Linked to the specific supplier

• (Stock Item) status ‘Provisional’ or ‘Current’

[[File:20210305 Select item.png|800px]]

After the item has been selected some purchase parameters need to be completed.

[[File:20210305 Add PO Contract Detail.png|500px]]

{| class="wikitable"
|-
! ''Parameter''
! ''Mandatory?''
! ''Selection Options''
! ''Description''
|-
| Maximum Quantity
| No
| Number (max.14 digits)
| Maximum quantity which can be called-off from the Contract with referenced CPOs. It refers to the maximum quantity that the supplier
committed to deliver under the agreed terms. The unit is always the ‘Stock Unit’ which is shown when selecting the item. Once the quantity on the referenced CPOs sum up the Maximum quantity, the contract will be terminated in the system.

If the maximum quantity is left blank, means there is no limit for the quantity to be ordered against the Contract. Normally POs with an end Date have no maximum quantity assigned.
|-
| Cost
| No
| Number (max. 6 decimal digits)
| It refers to the monetary value for the Stock Unit’. Select also the currency from the dropdown list.
|-
| Lead time
| No
| Number in days (max. 5 decimal digits)
| As agreed with the supplier. It refers to the time between the CPO is placed and the expected delivery date.
|-
| Minimum Order Quantity
| No
| Number (maximum 10 digits)
| As agreed with the supplier. POs will be created in multiples of the MOQ
|-
| Economic Order Quantity
| No
| Number (maximum 10 digits)
| As agreed with the supplier. For example, how many items will fit in a truck / sea container
|-
| Delivery Terms
| No
| Text (maximum 3 characters)
| INCOTERMS, as agreed with the supplier
|-
| Comment
| No
| Text (maximum 128 characters)
| Free text field for additional information
|}

Once all relevant fields have been completed and reflect the commercial agreement with the supplier, press [[File:SaveSave.png]] and repeat the process for all the items to be added to the contract.

<h2>Tax Categories</h2>

In some cases it will be required to assign tax categories to the different items within the Contract. The first step is to define the tax categories by pressing [[File:20210305 Tax Categories button.png]].

Press [[File:PlusPlus.png]] to add new categories. A new line will be displayed. Define a tax code easy to identify, a description and the percentage applicable. You can also remove lines by pressing [[File:20210305 X delete.png]]

[[File:20210305 Add Tax Categories.png|700px]]

Once you have added all the required Tax categories press [[File:20210305 Save changes.png|100px]]. You can then assign the tax categories created to the different items in the contract.

[[File:20210305 Assign tax categories.png]]

Once you have added all the items, and if required assigned all tax categories press [[File:20210120 submit.png|90px]].

<h1>Create a New Contract</h1>

Depending on the role and the customer configuration, when you press [[File:20210120 submit.png|90px]], the contract will either go to a next approval stage, or change status to Approved.

Depending on the ‘Contract Start Date’ has already been reached the status will further change from ‘Approved’ to ‘Active’.

[[PurchaseOrder_ContractsAwaitingApproval|''For more details regarding PO Contracts Approval click this link'']]

File:20210305 Delivery terms.png

2021-03-05T15:44:07Z

Betsy: Delivery terms on PO contracts

== Summary ==
Delivery terms on PO contracts

File:20210305 Menu approve PO contract.png

2021-03-05T15:38:37Z

Betsy: Route to get to the approve PO contract page.

== Summary ==
Route to get to the approve PO contract page.

PurchaseOrder POContractIndex

2021-03-05T15:32:40Z

Betsy:

<accesscontrol>SLXGLOBALADMIN,SLXLOCALADMIN,SLXOPERATIONAL,AIRLINEADMIN,AIRLINEOPS,AIRLINEMANAG</accesscontrol>

Please use our [[http://wiki.skylogportal.com/index.php?title=Tips_and_Tricks '''Tips and Tricks''']] page for understanding how the SkySuite portal works and how to navigate faster and easier.

__TOC__
<h1>PO Master Contract (POMC)</h1>

It is the base/master agreement against which multiple call-offs (CPOs) can be placed with the supplier. The contract will contain the commercial agreement applicable to all subsequent POs: agreed prices, length, INCOTERMS and quantities. The advantage is that once the POMC is setup by the customer’s buyer (or a SLX Control Tower and approved by the customer) the Material Controller can place Contracted POs (CPOs) against the contract without individual CPOs approval required, unless, there are other approval conditions like CPO being subject to further approval based on value.

<h1>Create a New Contract</h1>

To create a new contract go to Daily Activities / MRP & Purchase Ordering / Create/Review PO contracts.

[[File:20210305 Create Review PO Contracts.png|400px]]

Press [[File:PlusPlus.png]], then press [[File:20210305 Select supplier.png]].

Search for the supplier you are creating the contract for, you can use the filter options, and then press on '''Select'''

[[File:20210305 Select supplier screen.png|600px]]

<h2>Contract Header information</h2>

A new page will be displayed for you to complete general information about the contract:

[[File:20210305 New PO Contract header.png|400px]]

{| class="wikitable"
|-
! ''Parameter''
! ''Mandatory?''
! ''Description''
|-
| Contract Reference
| Yes
| This reference is manually entered, and must be unique. Will be printed on the PDF document (header). It is a free text of maximum 16 caracters
|-
| Previous Contract
| No
| You can select from all All existing Contract References to link to the contract being created. This information is for reference and it does does not trigger further actions in SkyLog.
|-
| Contract Start date
| Yes
| First day from which CPOs that reference to the Contract can be created.
|-
| Contract End date
| No
| Last day until which CPOs that reference to the Contract can be created. To be left blank, if a Contract should be valid for “indefinite”
time. Must be later than the ‘Contract Start Date’
|-
| Goods to be shipped to
| Yes
| A contract can be created for deliveries to:

• ‘Anywhere’ can be chosen if the CPOs referencing to the Contract can be created for all warehouses or stations setup for the customer, applying the same commercial conditions (prices, MOQ, etc)

• Warehouse: Select the relevant warehouse.

• Station: Select the relevant station
|-
| Terms and Conditions
| Yes
| Should include INCOTERMS and delivery point. It will be printed on PDF document.
|-
| Notes
| No
| Optional internal comments. They can be read by all users with ‘View Contract’ access rights. It can include details of combined MOQs.
|}

Once all mandatory fields have been entered press [[File:20210305 Save No disk.png|40px]]

<h2>Purchase Order Contract Details</h2>

Once the ‘Purchase Order Header Data’ is entered and ‘Save’ button is pressed, it will be possible to enter the ‘Purchase Order Contract Details’ meaning the item line information.

Note: It is only possible to add items to a POMC as long as it is in status ‘Provisional’ (for Airline Management users it is still possible in status ‘Awaiting Approval’, if the approval process applies).

By pressing [[File:PlusPlus.png]] new items can be added to the Contract. Select the item to be added, you can use the filters to find the relevant products. The window will display items that meet the following characteristics:

• Linked to the specific supplier

• (Stock Item) status ‘Provisional’ or ‘Current’

[[File:20210305 Select item.png|800px]]

After the item has been selected some purchase parameters need to be completed.

[[File:20210305 Add PO Contract Detail.png|500px]]

{| class="wikitable"
|-
! ''Parameter''
! ''Mandatory?''
! ''Selection Options''
! ''Description''
|-
| Maximum Quantity
| No
| Number (max.14 digits)
| Maximum quantity which can be called-off from the Contract with referenced CPOs. It refers to the maximum quantity that the supplier
committed to deliver under the agreed terms. The unit is always the ‘Stock Unit’ which is shown when selecting the item. Once the quantity on the referenced CPOs sum up the Maximum quantity, the contract will be terminated in the system.

If the maximum quantity is left blank, means there is no limit for the quantity to be ordered against the Contract. Normally POs with an end Date have no maximum quantity assigned.
|-
| Cost
| No
| Number (max. 6 decimal digits)
| It refers to the monetary value for the Stock Unit’. Select also the currency from the dropdown list.
|-
| Lead time
| No
| Number in days (max. 5 decimal digits)
| As agreed with the supplier. It refers to the time between the CPO is placed and the expected delivery date.
|-
| Minimum Order Quantity
| No
| Number (maximum 10 digits)
| As agreed with the supplier. POs will be created in multiples of the MOQ
|-
| Economic Order Quantity
| No
| Number (maximum 10 digits)
| As agreed with the supplier. For example, how many items will fit in a truck / sea container
|-
| Delivery Terms
| No
| Text (maximum 3 characters)
| INCOTERMS, as agreed with the supplier
|-
| Comment
| No
| Text (maximum 128 characters)
| Free text field for additional information
|}

Once all relevant fields have been completed and reflect the commercial agreement with the supplier, press [[File:SaveSave.png]] and repeat the process for all the items to be added to the contract.

<h2>Tax Categories</h2>

In some cases it will be required to assign tax categories to the different items within the Contract. The first step is to define the tax categories by pressing [[File:20210305 Tax Categories button.png]].

Press [[File:PlusPlus.png]] to add new categories. A new line will be displayed. Define a tax code easy to identify, a description and the percentage applicable. You can also remove lines by pressing [[File:20210305 X delete.png]]

[[File:20210305 Add Tax Categories.png|700px]]

Once you have added all the required Tax categories press [[File:20210305 Save changes.png|100px]]. You can then assign the tax categories created to the different items in the contract.

[[File:20210305 Assign tax categories.png]]

Once you have added all the items, and if required assigned all tax categories press [[File:20210120 submit.png|90px]].

<h1>Create a New Contract</h1>

Depending on the role and the customer configuration, when you press [[File:20210120 submit.png|90px]], the contract will either go to a next approval stage, or change status to Approved.

Depending on the ‘Contract Start Date’ has already been reached the status will further change from ‘Approved’ to ‘Active’.

[[PurchaseOrder_ContractsAwaitingApproval|''For more details regarding PO Contracts Approval click this link'']]

PurchaseOrder POContractIndex

2021-03-05T15:30:57Z

Betsy:

<accesscontrol>SLXGLOBALADMIN,SLXLOCALADMIN,SLXOPERATIONAL,AIRLINEADMIN,AIRLINEOPS,AIRLINEMANAG</accesscontrol>

Please use our [[http://wiki.skylogportal.com/index.php?title=Tips_and_Tricks '''Tips and Tricks''']] page for understanding how the SkySuite portal works and how to navigate faster and easier.

__TOC__
<h1>PO Master Contract (POMC)</h1>

It is the base/master agreement against which multiple call-offs (CPOs) can be placed with the supplier. The contract will contain the commercial agreement applicable to all subsequent POs: agreed prices, length, INCOTERMS and quantities. The advantage is that once the POMC is setup by the customer’s buyer (or a SLX Control Tower and approved by the customer) the Material Controller can place Contracted POs (CPOs) against the contract without individual CPOs approval required, unless, there are other approval conditions like CPO being subject to further approval based on value.

<h1>Create a New Contract</h1>

To create a new contract go to Daily Activities / MRP & Purchase Ordering / Create/Review PO contracts.

[[File:20210305 Create Review PO Contracts.png|400px]]

Press [[File:PlusPlus.png]], then press [[File:20210305 Select supplier.png]].

Search for the supplier you are creating the contract for, you can use the filter options, and then press on '''Select'''

[[File:20210305 Select supplier screen.png|600px]]

<h2>Contract Header information</h2>

A new page will be displayed for you to complete general information about the contract:

[[File:20210305 New PO Contract header.png|400px]]

{| class="wikitable"
|-
! ''Parameter''
! ''Mandatory?''
! ''Description''
|-
| Contract Reference
| Yes
| This reference is manually entered, and must be unique. Will be printed on the PDF document (header). It is a free text of maximum 16 caracters
|-
| Previous Contract
| No
| You can select from all All existing Contract References to link to the contract being created. This information is for reference and it does does not trigger further actions in SkyLog.
|-
| Contract Start date
| Yes
| First day from which CPOs that reference to the Contract can be created.
|-
| Contract End date
| No
| Last day until which CPOs that reference to the Contract can be created. To be left blank, if a Contract should be valid for “indefinite”
time. Must be later than the ‘Contract Start Date’
|-
| Goods to be shipped to
| Yes
| A contract can be created for deliveries to:

• ‘Anywhere’ can be chosen if the CPOs referencing to the Contract can be created for all warehouses or stations setup for the customer, applying the same commercial conditions (prices, MOQ, etc)

• Warehouse: Select the relevant warehouse.

• Station: Select the relevant station
|-
| Terms and Conditions
| Yes
| Should include INCOTERMS and delivery point. It will be printed on PDF document.
|-
| Notes
| No
| Optional internal comments. They can be read by all users with ‘View Contract’ access rights. It can include details of combined MOQs.
|}

Once all mandatory fields have been entered press [[File:20210305 Save No disk.png|40px]]

<h2>Purchase Order Contract Details</h2>

Once the ‘Purchase Order Header Data’ is entered and ‘Save’ button is pressed, it will be possible to enter the ‘Purchase Order Contract Details’ meaning the item line information.

Note: It is only possible to add items to a POMC as long as it is in status ‘Provisional’ (for Airline Management users it is still possible in status ‘Awaiting Approval’, if the approval process applies).

By pressing [[File:PlusPlus.png]] new items can be added to the Contract. Select the item to be added, you can use the filters to find the relevant products. The window will display items that meet the following characteristics:

• Linked to the specific supplier

• (Stock Item) status ‘Provisional’ or ‘Current’

[[File:20210305 Select item.png|800px]]

After the item has been selected some purchase parameters need to be completed.

[[File:20210305 Add PO Contract Detail.png|500px]]

{| class="wikitable"
|-
! ''Parameter''
! ''Mandatory?''
! ''Selection Options''
! ''Description''
|-
| Maximum Quantity
| No
| Number (max.14 digits)
| Maximum quantity which can be called-off from the Contract with referenced CPOs. It refers to the maximum quantity that the supplier
committed to deliver under the agreed terms. The unit is always the ‘Stock Unit’ which is shown when selecting the item. Once the quantity on the referenced CPOs sum up the Maximum quantity, the contract will be terminated in the system.

If the maximum quantity is left blank, means there is no limit for the quantity to be ordered against the Contract. Normally POs with an end Date have no maximum quantity assigned.
|-
| Cost
| No
| Number (max. 6 decimal digits)
| It refers to the monetary value for the Stock Unit’. Select also the currency from the dropdown list.
|-
| Lead time
| No
| Number in days (max. 5 decimal digits)
| As agreed with the supplier. It refers to the time between the CPO is placed and the expected delivery date.
|-
| Minimum Order Quantity
| No
| Number (maximum 10 digits)
| As agreed with the supplier. POs will be created in multiples of the MOQ
|-
| Economic Order Quantity
| No
| Number (maximum 10 digits)
| As agreed with the supplier. For example, how many items will fit in a truck / sea container
|-
| Delivery Terms
| No
| Text (maximum 3 characters)
| INCOTERMS, as agreed with the supplier
|-
| Comment
| No
| Text (maximum 128 characters)
| Free text field for additional information
|}

Once all relevant fields have been completed and reflect the commercial agreement with the supplier, press [[File:SaveSave.png]] and repeat the process for all the items to be added to the contract.

<h2>Tax Categories</h2>

In some cases it will be required to assign tax categories to the different items within the Contract. The first step is to define the tax categories by pressing [[File:20210305 Tax Categories button.png]].

Press [[File:PlusPlus.png]] to add new categories. A new line will be displayed. Define a tax code easy to identify, a description and the percentage applicable. You can also remove lines by pressing [[File:20210305 X delete.png]]

[[File:20210305 Add Tax Categories.png|700px]]

Once you have added all the required Tax categories press [[File:20210305 Save changes.png|80px]]. You can then assign the tax categories created to the different items in the contract.

[[File:20210305 Assign tax categories.png]]

Once you have added all the items, and if required assigned all tax categories press [[File:20210120 submit.png]].

<h1>Create a New Contract</h1>

Depending on the role and the customer configuration, when you press [[File:20210120 submit.png]], the contract will either go to a next approval stage, or change status to Approved.

Depending on the ‘Contract Start Date’ has already been reached the status will further change from ‘Approved’ to ‘Active’.

[[PurchaseOrder_ContractsAwaitingApproval|''For more details regarding PO Contracts Approval click this link'']]

PurchaseOrder POContractIndex

2021-03-05T15:19:11Z

Betsy:

<accesscontrol>SLXGLOBALADMIN,SLXLOCALADMIN,SLXOPERATIONAL,AIRLINEADMIN,AIRLINEOPS,AIRLINEMANAG</accesscontrol>

Please use our [[http://wiki.skylogportal.com/index.php?title=Tips_and_Tricks '''Tips and Tricks''']] page for understanding how the SkySuite portal works and how to navigate faster and easier.

__TOC__
<h1>PO Master Contract (POMC)</h1>

It is the base/master agreement against which multiple call-offs (POs) can be placed with the supplier. The contract will contain the commercial agreement applicable to all subsequent POs: agreed prices, length, INCOTERMS and quantities. The advantage is that once the POMC is setup by the customer’s buyer (or a SLX Control Tower and approved by the customer) the Material Controller can place Contracted POs (CPOs) against the contract without individual CPOs approval required, unless, there are other approval conditions like CPO being subject to further approval based on value.

<h1>Create a New Contract</h1>

To create a new contract go to Daily Activities / MRP & Purchase Ordering / Create/Review PO contracts.

[[File:20210305 Create Review PO Contracts.png|400px]]

Press [[File:PlusPlus.png]], then press [[File:20210305 Select supplier.png]].

Search for the supplier you are creating the contract for, you can use the filter options, and then press on '''Select'''

[[File:20210305 Select supplier screen.png|600px]]

<h2>Contract Header information</h2>

A new page will be displayed for you to complete general information about the contract:

[[File:20210305 New PO Contract header.png|400px]]

{| class="wikitable"
|-
! ''Parameter''
! ''Mandatory?''
! ''Description''
|-
| Contract Reference
| Yes
| This reference is manually entered, and must be unique. Will be printed on the PDF document (header). It is a free text of maximum 16 caracters
|-
| Previous Contract
| No
| You can select from all All existing Contract References to link to the contract being created. This information is for reference and it does does not trigger further actions in SkyLog.
|-
| Contract Start date
| Yes
| First day from which CPOs that reference to the Contract can be created.
|-
| Contract End date
| No
| Last day until which CPOs that reference to the Contract can be created. To be left blank, if a Contract should be valid for “indefinite”
time. Must be later than the ‘Contract Start Date’
|-
| Goods to be shipped to
| Yes
| A contract can be created for deliveries to:

• ‘Anywhere’ can be chosen if the CPOs referencing to the Contract can be created for all warehouses or stations setup for the customer, applying the same commercial conditions (prices, MOQ, etc)

• Warehouse: Select the relevant warehouse.

• Station: Select the relevant station
|-
| Terms and Conditions
| Yes
| Should include INCOTERMS and delivery point. It will be printed on PDF document.
|-
| Notes
| No
| Optional internal comments. They can be read by all users with ‘View Contract’ access rights. It can include details of combined MOQs.
|}

Once all mandatory fields have been entered press [[File:20210305 Save No disk.png]]

<h2>Purchase Order Contract Details</h2>

Once the ‘Purchase Order Header Data’ is entered and ‘Save’ button is pressed, it will be possible to enter the ‘Purchase Order Contract Details’ meaning the item line information.
Note: It is only possible to add items to a POMC as long as it is in status ‘Provisional’ (for Airline Management users it is still possible in status ‘Awaiting Approval’, if the approval process applies).

By pressing [[File:PlusPlus.png]] new items can be added to the Contract. Select the item to be added, you can use the filters to find the relevant products. The window will display items that meet the following characteristics:

• Linked to the specific supplier
• (Stock Item) status ‘Provisional’ or ‘Current’

[[File:20210305 Select item.png|800px]]

After the item has been selected some purchase parameters need to be completed.

[[File:20210305 Add PO Contract Detail.png|500px]]

{| class="wikitable"
|-
! ''Parameter''
! ''Mandatory?''
! ''Selection Options''
! ''Description''
|-
| Maximum Quantity
| No
| Number (max.14 digits)
| Maximum quantity which can be called-off from the Contract with referenced CPOs. It refers to the maximum quantity that the supplier
committed to deliver under the agreed terms. The unit is always the ‘Stock Unit’ which is shown when selecting the item. Once the quantity on the referenced CPOs sum up the Maximum quantity, the contract will be terminated in the system.

If the maximum quantity is left blank, means there is no limit for the quantity to be ordered against the Contract. Normally POs with an end Date have no maximum quantity assigned.
|-
| Cost
| No
| Number (max. 6 decimal digits)
| It refers to the monetary value for the Stock Unit’. Select also the currency from the dropdown list.
|-
| Lead time
| No
| Number in days (max. 5 decimal digits)
| As agreed with the supplier. It refers to the time between the CPO is placed and the expected delivery date.
|-
| Minimum Order Quantity
| No
| Number (maximum 10 digits)
| As agreed with the supplier. POs will be created in multiples of the MOQ
|-
| Economic Order Quantity
| No
| Number (maximum 10 digits)
| As agreed with the supplier. For example, how many items will fit in a truck / sea container
|-
| Delivery Terms
| No
| Text (maximum 3 characters)
| INCOTERMS, as agreed with the supplier
|-
| Comment
| No
| Text (maximum 128 characters)
| Free text field for additional information
|}

Once all relevant fields have been completed and reflect the commercial agreement with the supplier, press [[File:SaveSave.png]] and repeat the process for all the items to be added to the contract.

<h2>Tax Categories</h2>

In some cases it will be required to assign tax categories to the different items within the Contract. the first step is to define the tax categories by pressing [[File:20210305 Tax Categories button.png]].

Press [[File:PlusPlus.png]] to add new categories. A new line will be displayed. Define a tax code easy to identify, a description and the percentage applicable. You can also remove lines by pressing [[File:20210305 X delete.png]]

[[File:20210305 Add Tax Categories.png|700px]]

Once you have added all the required Tax categories press [[File:20210305 Save changes.png]]. You can then assign the tax categories created to the different items in the contract.

[[File:20210305 Assign tax categories.png]]

Once you have added all the items, and if required assigned all tax categories press [[File:20210120 submit.png]].

<h1>Create a New Contract</h1>

Depending on the role and the customer configuration, when you press [[File:20210120 submit.png]], the contract will either go to a next approval stage, or change status to Approved.

Depending on the ‘Contract Start Date’ has already been reached the status will further change from ‘Approved’ to ‘Active’.

[[PurchaseOrder_ContractsAwaitingApproval|''For more details regarding PO Contracts Approval click this link'']]

PurchaseOrder ContractsAwaitingApproval

2021-03-05T15:17:26Z

Betsy: Created blank page

PurchaseOrder POContractIndex

2021-03-05T15:07:57Z

Betsy:

<accesscontrol>SLXGLOBALADMIN,SLXLOCALADMIN,SLXOPERATIONAL,AIRLINEADMIN,AIRLINEOPS,AIRLINEMANAG</accesscontrol>

Please use our [[http://wiki.skylogportal.com/index.php?title=Tips_and_Tricks '''Tips and Tricks''']] page for understanding how the SkySuite portal works and how to navigate faster and easier.

__TOC__
<h1>PO Master Contract (POMC)</h1>

It is the base/master agreement against which multiple call-offs (POs) can be placed with the supplier. The contract will contain the commercial agreement applicable to all subsequent POs: agreed prices, length, INCOTERMS and quantities. The advantage is that once the POMC is setup by the customer’s buyer (or a SLX Control Tower and approved by the customer) the Material Controller can place Contracted POs (CPOs) against the contract without individual CPOs approval required, unless, there are other approval conditions like CPO being subject to further approval based on value.

<h1>Create a New Contract</h1>

To create a new contract go to Daily Activities / MRP & Purchase Ordering / Create/Review PO contracts.

[[File:20210305 Create Review PO Contracts.png|400px]]

Press [[File:PlusPlus.png]], then press [[File:20210305 Select supplier.png]].

Search for the supplier you are creating the contract for, you can use the filter options, and then press on '''Select'''

[[File:20210305 Select supplier screen.png|600px]]

<h2>Contract Header information</h2>

A new page will be displayed for you to complete general information about the contract:

[[File:20210305 New PO Contract header.png|400px]]

{| class="wikitable"
|-
! ''Parameter''
! ''Mandatory?''
! ''Description''
|-
| Contract Reference
| Yes
| This reference is manually entered, and must be unique. Will be printed on the PDF document (header). It is a free text of maximum 16 caracters
|-
| Previous Contract
| No
| You can select from all All existing Contract References to link to the contract being created. This information is for reference and it does does not trigger further actions in SkyLog.
|-
| Contract Start date
| Yes
| First day from which CPOs that reference to the Contract can be created.
|-
| Contract End date
| No
| Last day until which CPOs that reference to the Contract can be created. To be left blank, if a Contract should be valid for “indefinite”
time. Must be later than the ‘Contract Start Date’
|-
| Goods to be shipped to
| Yes
| A contract can be created for deliveries to:

• ‘Anywhere’ can be chosen if the CPOs referencing to the Contract can be created for all warehouses or stations setup for the customer, applying the same commercial conditions (prices, MOQ, etc)

• Warehouse: Select the relevant warehouse.

• Station: Select the relevant station
|-
| Terms and Conditions
| Yes
| Should include INCOTERMS and delivery point. It will be printed on PDF document.
|-
| Notes
| No
| Optional internal comments. They can be read by all users with ‘View Contract’ access rights. It can include details of combined MOQs.
|}

Once all mandatory fields have been entered press [[File:20210305 Save No disk.png]]

<h2>Purchase Order Contract Details</h2>

Once the ‘Purchase Order Header Data’ is entered and ‘Save’ button is pressed, it will be possible to enter the ‘Purchase Order Contract Details’ meaning the item line information.
Note: It is only possible to add items to a POMC as long as it is in status ‘Provisional’ (for Airline Management users it is still possible in status ‘Awaiting Approval’, if the approval process applies).

By pressing [[File:PlusPlus.png]] new items can be added to the Contract. Select the item to be added, you can use the filters to find the relevant products. The window will display items that meet the following characteristics:

• Linked to the specific supplier
• (Stock Item) status ‘Provisional’ or ‘Current’

[[File:20210305 Select item.png|800px]]

After the item has been selected some purchase parameters need to be completed.

[[File:20210305 Add PO Contract Detail.png|500px]]

{| class="wikitable"
|-
! ''Parameter''
! ''Mandatory?''
! ''Selection Options''
! ''Description''
|-
| Maximum Quantity
| No
| Number (max.14 digits)
| Maximum quantity which can be called-off from the Contract with referenced CPOs. It refers to the maximum quantity that the supplier
committed to deliver under the agreed terms. The unit is always the ‘Stock Unit’ which is shown when selecting the item. Once the quantity on the referenced CPOs sum up the Maximum quantity, the contract will be terminated in the system.

If the maximum quantity is left blank, means there is no limit for the quantity to be ordered against the Contract. Normally POs with an end Date have no maximum quantity assigned.
|-
| Cost
| No
| Number (max. 6 decimal digits)
| It refers to the monetary value for the Stock Unit’. Select also the currency from the dropdown list.
|-
| Lead time
| No
| Number in days (max. 5 decimal digits)
| As agreed with the supplier. It refers to the time between the CPO is placed and the expected delivery date.
|-
| Minimum Order Quantity
| No
| Number (maximum 10 digits)
| As agreed with the supplier. POs will be created in multiples of the MOQ
|-
| Economic Order Quantity
| No
| Number (maximum 10 digits)
| As agreed with the supplier. For example, how many items will fit in a truck / sea container
|-
| Delivery Terms
| No
| Text (maximum 3 characters)
| INCOTERMS, as agreed with the supplier
|-
| Comment
| No
| Text (maximum 128 characters)
| Free text field for additional information
|}

Once all relevant fields have been completed and reflect the commercial agreement with the supplier, press [[File:SaveSave.png]] and repeat the process for all the items to be added to the contract.

<h2>Tax Categories</h2>

In some cases it will be required to assign tax categories to the different items within the Contract. the first step is to define the tax categories by pressing [[File:20210305 Tax Categories button.png]].

Press [[File:PlusPlus.png]] to add new categories. A new line will be displayed. Define a tax code easy to identify, a description and the percentage applicable. You can also remove lines by pressing [[File:20210305 X delete.png]]

[[File:20210305 Add Tax Categories.png|700px]]

Once you have added all the required Tax categories press [[File:20210305 Save changes.png]]. You can then assign the tax categories created to the different items in the contract.

[[File:20210305 Assign tax categories.png]]

Once you have added all the items, and if required assigned all tax categories press [[File:20210120 submit.png]].

<h1>Create a New Contract</h1>

Depending on the role and the customer configuration, when you press [[File:20210120 submit.png]], the contract will either go to a next approval stage, or change status to Approved.

Depending on the ‘Contract Start Date’ has already been reached the status will further change from ‘Approved’ to ‘Active’.

File:20210305 Save changes.png

2021-03-05T15:02:01Z

Betsy: Save changes in grey

== Summary ==
Save changes in grey

File:20210305 Assign tax categories.png

2021-03-05T15:01:11Z

Betsy: Dropdown selection of created tax categories

== Summary ==
Dropdown selection of created tax categories

File:20210305 X delete.png

2021-03-05T14:53:58Z

Betsy: Deletion symbol X

== Summary ==
Deletion symbol X

File:20210305 Add Tax Categories.png

2021-03-05T14:50:39Z

Betsy: Information to complete to add tax category in contract

== Summary ==
Information to complete to add tax category in contract

File:20210305 Tax Categories button.png

2021-03-05T14:45:14Z

Betsy: Tax categories in contracts

== Summary ==
Tax categories in contracts

PurchaseOrder POContractIndex

2021-03-05T14:17:17Z

Betsy:

PurchaseOrder POContractIndex

2021-03-05T13:25:02Z

Betsy:

File:20210305 Add PO Contract Detail.png

2021-03-05T13:00:06Z

Betsy: Screen once item is selected

== Summary ==
Screen once item is selected

PurchaseOrder POContractIndex

2021-03-05T12:57:38Z

Betsy:

File:20210305 Select item.png

2021-03-05T12:53:13Z

Betsy: Select item, shows the filter option

== Summary ==
Select item, shows the filter option

File:20210305 Save No disk.png

2021-03-05T12:22:12Z

Betsy: Save option without the disk picture

== Summary ==
Save option without the disk picture

PurchaseOrder POContractIndex

2021-03-05T12:13:56Z

Betsy:

PurchaseOrder POContractIndex

2021-03-05T12:00:13Z

Betsy:

File:20210305 New PO Contract header.png

2021-03-05T11:47:37Z

Betsy: Contract header parameters

== Summary ==
Contract header parameters

File:20210305 Select supplier screen.png

2021-03-05T11:36:29Z

Betsy: Select supplier screen / apply filter

== Summary ==
Select supplier screen / apply filter