SkySuite Wiki - User contributions [en-gb]

AirlineSupplier Index

2020-05-27T15:19:29Z

Arunas.milasius:

<accesscontrol>SLXGLOBALADMIN,SLXLOCALADMIN,SLXOPERATIONAL</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>Summary</h1>

An Airline Supplier in SkyLog is a supplier (Vendor) of product or services to the Airline. In order for an Airline Supplier to exist there must first be an Organization and OrganizationSite to which that Airline Supplier record can be linked. Airline Supplier records must exist if any of the purchase contracting or purchase ordering modules of SkySuite are used. If the airline is using SkySuite or an integrated 3rd party product such as Promeus to produce self billing catering invoices then an Airline Supplier record must also exist for every station where invoices will be generated.

<h1>Create Organization</h1>

Organization refers to 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 an Airline Supplier the Organization type must be "Supplier" or "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 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 support request. For more details on Organizations see link [[http://wiki.skylogportal.com/index.php?title=Organization_Index'''Organizations''']]

<h1>Create Organization Sites</h1>

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 time zone of that site. The site record must exist before you can create an Airline Supplier record or for that matter any other supply chain participant type such as stations, warehouses etc.

Firstly, please check if a site is already created in SkyLog with same address and linked to the same Organization, it is important not to duplicate organization sites. For more please see link [[http://wiki.skylogportal.com/index.php?title=OrganizationSite_Index'''Organization Sites''']]

<h1>Create Airline Suppliers</h1>

To create Airline Supplier record and to maintain it please follow below described steps. Some information held under Airline Supplier records such as Main Contact and Additional Contacts are prone to change as people move in and out different roles. It is important to maintain information up to date, especially if Airline is using Skylog Purchase Order, MRP and/or self invoicing functionalities that send automated emails to suppliers.

<h2>Creation of Airline Supplier Record</h2>

1. Airline supplier record can be found under Reference Data / Supply Chain Participants / Airline supplier.

[[File:AirlineSupplierLocationRef.png]]

In some airlines the creation of suppliers is done in the airline master data system and the details are then sent via interface to SkySuite, in that case, you can review the suppliers information in [[FileRegister_ExternalVendors|'''Review Vendor Master Details''']] page.

2. In top left corner click [[File:PlusPlus.png]] to create a new Airline Supplier record. An Airline Supplier Form will appear.
* If you have rights to access multiple Airlines data a window will be displayed for you to select the airline for which new Airline Supplier Record is required.
[[File:AirlineSupplierMultiAirline.png]]

3. Please fill all infomration in Airline Supplier Form. Below table describes each of the fields and their importance

{| class="wikitable"
|-
! Field
! Sample
! Description
|-
| Supplier Site
| Coca Cola Enterprises
| Supplier Site is a drop down list displaying all the Organization Sites linked to active Organizations categorized as Suppliers. It is key to select correct Organization Site with correct address as this information will appear on contracts, purchase orders and Invoices
|-
| Accounts Payable No.
| ABC123
| Code is usually provided by the Airline and refers to Supplier's unique ID number assigned in Airline's finance systems for Contracts, purchase order creation, goods receipt and invoice matching
|-
| Default Payment Terms
| D30
| Code is usually provided by customer and refers to customer's agreed payment terms with the supplier. Field is often used in interfaces between Skylog and customer's Finance systems.
|-
| Interface
| Yes/No
| it is a confirmation if Airline Supplier record is participating in interface transaction between airline IT systems and Skylog. If there is a direct interface for Purchase Orders or Vendor Details active, please select Yes.
|-
| Active
| Yes/No
| it is a confirmation if Vendor is presently active. Only Active vendors can have new items added to their portfolio and have contracts or purchase order placed in skylog.
|-
| Main Contact Details
| john.johnson@supplier.com
| it is best practice to keep Main contact information up to date for all Airline Suppliers.
|-
|}
4. click [[file:SaveSave.png]]

<h1>Additional Contacts</h1>
After supplier record is created additional information could be added such as Additional Contacts. Information from Additional Contacts is important and is used in automated email communications when purchase orders are raised, amended, cancelled or requires supplier to acknowledge or review or for self invoicing module. Note that different airlines may have different setup as per their custom requests, please consult your Local Administrator to confirm which communications have been automated for your operations.

To add new Additional Contact to specific supplier:
# Access supplier record by clicking on [[file:EditEdit.png]]
# Below basic Airline supplier details you provided you will see tab that says [[File:AdditionalContacts.png]]. Click on it.
# Use button [[file:plusplus]] to add a new contact record and fill up the form.
[[File:AdditionalContactForm.png]]

To remove no longer relevant records you have two options: either simply click on [[file:RemoveRemove.png]] next to a name and record will be deleted completely; or but edit Contact Details and mark them no longer active by clicking on [[file:EditEdit.png]] next to name and changing Active status to "No", that way records are still kept.

<h1>Adding Items to Supplier</h1>
Each stock items that is being procured reuqires a Item Supplier record to be created. A quick guide how to do that can be found following the [[StockItem_Index#Item_Suppliers|link to Stock Item page for more details]]. All Stock Items linked to specific supplier will appear under [[file:ItemsSupplied.png]] tab.

Support Index

2020-05-27T15:13:54Z

Arunas.milasius:

<h1>Summary</h1>

The Support Request page is used to raise open issues, questions and make requests to the SkySuite support team directly. All support requests are reviewed and acted upon. Note that SkySuite support addresses issues impacting operations with priority.

When raising a ticket it is important to select airline and SkySuite area affected, provide detailed description of the problem and attach all evidence collected. Once ticket is logged you will be receiving updates with each new post or status update.

<h1>Support Request and Types</h1>
Support Request are used contact for any problems that users may experience while using SkySuite. When ticket is raised emails notifications will follow with each update on the ticket or status change. Users should be alert and available to provide feedback to Support team in case of a follow up questions or request for more information.

<h1>Enhancement Request</h1>
SkySuite is always evolving and improving with new functionalities. Enhancement request is the way these improvement are discussed across different operations and developer team to agree design that could benefit all.

Enhancement request requires detail description of the problem and proposed solution or user experience to address it. Then it is reviewed and potential solutions are discussed to agree on viable design to hand over to developers to prioritize and implement.

Please note that enhancement request are more complex request and requires time to be reviewed and addressed,

<h1>How to log a ticket</h1>

When logging a ticket it is essential to provide as much information as possible about the issue you are facing. Please provide detailed description of the problem, what time it occurred, and what steps were taken. It is best practice to have either video recording of the problem, full screenshot including time stamp and URL, or even putting it in a presentation document with all details.

Once information has been collected you can raise support ticket by following below steps
1. Click on [[File:PlusPlus.png]] located in the top left corner to open a support request form.
[[File:SupportRequestForm.png]]
2. In a support request window please fill every window.
## <b>Area</b> - Choose from the list of options one best describing the area in which the are facing and issue (e.g. Forecasting, Interface, Requisitioning etc).
## <b>Project</b> - Choose airline name of your account.
## <b>Category</b> - Name the type of problem you are facing. For example, if some data is not correct or not showing - Data Issue, if there is an issue with an system interface with 3rd party systems - EDI Issue, SkySuite also has an option dedicated for SkySuite Functional Question in case questions arise on how SkySuite works.
## <b>Priority</b> - SkySuite request users to identify the priority of an a problem logged. However we trust users to follow below guidelines and respecting priorities suggested:
##* Low : Used for issues found in testing environment, or problems that have no effect on operations.
##* Standard :used for majority of cases, "standard" status review and action, but it is not something that affects operation immediately and has a workaround in place.
##* Important :Reserved for cases that are affecting selected area of operations and requires immediate IT involvement to address or support with a workaround.
##* Critical: is reserved for cases when operational is frozen and cannot conduct day to day tasks in multiple areas of operations.
## <b>Subject</b> - a header title of problem logged.
## <b>Detailed</b> - a more detailed description of the problem, time and situation it has occurred.

<h1>Tips and Tricks</h1>

<h2>Monitoring tickets </h2>

[[file:SupportOtherFunctions.png]]

SkySuite ticket system allows users to monitor relevant tickets. If you are interested to be kept up to date on Support request or Enhancement request, just open the ticket you are interested and click on a [[File:MonitorButton.png]].

If you, want to add someone to a ticket to receive all notifications and updates. You can do that by clicking on [[File:ViewDistributionList.png]] and [[File:PlusPlus.png]] to add at selected person

<h2>Link different tickets </h2>
You can also link different related tickets to provide more information and to make sure it is easier to track information related to request. To do so please open a ticket you an active ticket and click on [[File:LinkedTickets:png]], click on [[File:PlusPlus.png]], find relevant ticket and click to update.

Support Index

2020-05-27T12:15:01Z

Arunas.milasius:

<h1>Summary</h1>

The Support Request page is used to raise open issues, questions and make requests to the SkyLog support team directly. All support requests are reviewed and acted upon. Note that Skylog support addresses issues impacting operations with priority.

When raising a ticket it is important to select airline and Skylog area affected, provide detailed description of the problem and attach all evidence collected. Once ticket is logged you will be receiving updates with each new post or status update.

<h1>Support Request and Types</h1>
Support Request are used contact for any problems that users may experience while using Skylog. When ticket is raised emails notifications will follow with each update on the ticket or status change. Users should be alert and available to provide feedback to Support team in case of a follow up questions or request for more information.

<h1>Enhancement Request</h1>
Skylog is always evolving and improving with new functionalities. Enhancement request is the way these improvement are discussed across different operations and developer team to agree design that could benefit all.

Enhancement request requires detail description of the problem and proposed solution or user experience to address it. Then it is reviewed and potential solutions are discussed to agree on viable design to hand over to developers to prioritize and implement.

Please note that enhancement request are more complex request and requires time to be reviewed and addressed,

<h1>How to log a ticket</h1>

When logging a ticket it is essential to provide as much information as possible about the issue you are facing. Please provide detailed description of the problem, what time it occurred, and what steps were taken. It is best practice to have either video recording of the problem, full screenshot including time stamp and URL, or even putting it in a presentation document with all details.

Once information has been collected you can raise support ticket by following below steps
1. Click on [[File:PlusPlus.png]] located in the top left corner to open a support request form.
[[File:SupportRequestForm.png]]
2. In a support request window please fill every window.
## <b>Area</b> - Choose from the list of options one best describing the area in which the are facing and issue (e.g. Forecasting, Interface, Requisitioning etc).
## <b>Project</b> - Choose airline name of your account.
## <b>Category</b> - Name the type of problem you are facing. For example, if some data is not correct or not showing - Data Issue, if there is an issue with an system interface with 3rd party systems - EDI Issue, Skylog also has an option dedicated for Skylog Functional Question in case questions arise on how Skylog works.
## <b>Priority</b> - Skylog request users to identify the priority of an a problem logged. However we trust users to follow below guidelines and respecting priorities suggested:
##* Low : Used for issues found in testing environment, or problems that have no effect on operations.
##* Standard :used for majority of cases, "standard" status review and action, but it is not something that affects operation immediately and has a workaround in place.
##* Important :Reserved for cases that are affecting selected area of operations and requires immediate IT involvement to address or support with a workaround.
##* Critical: is reserved for cases when operational is frozen and cannot conduct day to day tasks in multiple areas of operations.
## <b>Subject</b> - a header title of problem logged.
## <b>Detailed</b> - a more detailed description of the problem, time and situation it has occurred.

<h1>Tips and Tricks</h1>

<h2>Monitoring tickets </h2>

[[file:SupportOtherFunctions.png]]

Skylog ticket system allows users to monitor relevant tickets. If you are interested to be kept up to date on Support request or Enhancement request, just open the ticket you are interested and click on a [[File:MonitorButton.png]].

If you, want to add someone to a ticket to receive all notifications and updates. You can do that by clicking on [[File:ViewDistributionList.png]] and [[File:PlusPlus.png]] to add at selected person

<h2>Link different tickets </h2>
You can also link different related tickets to provide more information and to make sure it is easier to track information related to request. To do so please open a ticket you an active ticket and click on [[File:LinkedTickets:png]], click on [[File:PlusPlus.png]], find relevant ticket and click to update.

AirlineSupplier Index

2020-05-27T11:58:06Z

Arunas.milasius:

<accesscontrol>SLXGLOBALADMIN,SLXLOCALADMIN,SLXOPERATIONAL</accesscontrol>

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

__TOC__
<h1>Summary</h1>

An Airline Supplier in SkyLog is a supplier (Vendor) of product or services to the Airline. In order for an Airline Supplier to exist there must first be an Organization and OrganizationSite to which that Airline Supplier record can be linked. Airline Supplier records must exist if any of the purchase contracting or purchase ordering modules of SkySuite are used. If the airline is using SkySuite or an integrated 3rd party product such as Promeus to produce self billing catering invoices then an Airline Supplier record must also exist for every station where invoices will be generated.

<h1>Create Organization</h1>

Organization refers to 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 an Airline Supplier the Organization type must be "Supplier" or "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 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 support request. For more details on Organizations see link [[http://wiki.skylogportal.com/index.php?title=Organization_Index'''Organizations''']]

<h1>Create Organization Sites</h1>

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 time zone of that site. The site record must exist before you can create an Airline Supplier record or for that matter any other supply chain participant type such as stations, warehouses etc.

Firstly, please check if a site is already created in SkyLog with same address and linked to the same Organization, it is important not to duplicate organization sites. For more please see link [[http://wiki.skylogportal.com/index.php?title=OrganizationSite_Index'''Organization Sites''']]

<h1>Create Airline Suppliers</h1>

To create Airline Supplier record and to maintain it please follow below described steps. Some information held under Airline Supplier records such as Main Contact and Additional Contacts are prone to change as people move in and out different roles. It is important to maintain information up to date, especially if Airline is using Skylog Purchase Order, MRP and/or self invoicing functionalities that send automated emails to suppliers.

<h2>Creation of Airline Supplier Record</h2>

1. Airline supplier record can be found under Reference Data / Supply Chain Participants / Airline supplier.

[[File:AirlineSupplierLocationRef.png]]

In some airlines the creation of suppliers is done in the airline master data system and the details are then sent via interface to SkySuite, in that case, you can review the suppliers information in [[FileRegister_ExternalVendors|'''Review Vendor Master Details''']] page.

2. In top left corner click [[File:PlusPlus.png]] to create a new Airline Supplier record. An Airline Supplier Form will appear.
* If you have rights to access multiple Airlines data a window will be displayed for you to select the airline for which new Airline Supplier Record is required.
[[File:AirlineSupplierMultiAirline.png]]

3. Please fill all infomration in Airline Supplier Form. Below table describes each of the fields and their importance

{| class="wikitable"
|-
! Field
! Sample
! Description
|-
| Supplier Site
| Coca Cola Enterprises
| Supplier Site is a drop down list displaying all the Organization Sites linked to active Organizations categorized as Suppliers. It is key to select correct Organization Site with correct address as this information will appear on contracts, purchase orders and Invoices
|-
| Accounts Payable No.
| ABC123
| Code is usually provided by the Airline and refers to Supplier's unique ID number assigned in Airline's finance systems for Contracts, purchase order creation, goods receipt and invoice matching
|-
| Default Payment Terms
| D30
| Code is usually provided by customer and refers to customer's agreed payment terms with the supplier. Field is often used in interfaces between Skylog and customer's Finance systems.
|-
| Interface
| Yes/No
| it is a confirmation if Airline Supplier record is participating in interface transaction between airline IT systems and Skylog. If there is a direct interface for Purchase Orders or Vendor Details active, please select Yes.
|-
| Active
| Yes/No
| it is a confirmation if Vendor is presently active. Only Active vendors can have new items added to their portfolio and have contracts or purchase order placed in skylog.
|-
| Main Contact Details
| john.johnson@supplier.com
| it is best practice to keep Main contact information up to date for all Airline Suppliers.
|-
|}
4. click [[file:SaveSave.png]]

<h1>Additional Contacts</h1>
After supplier record is created additional information could be added such as Additional Contacts. Information from Additional Contacts is important and is used in automated email communications when purchase orders are raised, amended, cancelled or requires supplier to acknowledge or review or for self invoicing module. Note that different airlines may have different setup as per their custom requests, please consult your Local Administrator to confirm which communications have been automated for your operations.

To add new Additional Contact to specific supplier:
# Access supplier record by clicking on [[file:EditEdit.png]]
# Below basic Airline supplier details you provided you will see tab that says [[File:AdditionalContacts.png]]. Click on it.
# Use button [[file:plusplus]] to add a new contact record and fill up the form.
[[File:AdditionalContactForm.png]]

To remove no longer relevant records you have two options: either simply click on [[file:RemoveRemove.png]] next to a name and record will be deleted completely; or but edit Contact Details and mark them no longer active by clicking on [[file:EditEdit.png]] next to name and changing Active status to "No", that way records are still kept.

<h1>Adding Items to Supplier</h1>
Each stock items that is being procured reuqires a Item Supplier record to be created. A quick guide how to do that can be found following the [[StockItem_Index#Item_Suppliers|link to Stock Item page for more details]]. All Stock Items linked to specific supplier will appear under [[file:ItemsSupplied.png]] tab.

File:AirlineSupplierLocationRef.png

2020-05-27T11:49:32Z

Arunas.milasius:

AirlineSupplier Index

2020-05-27T11:05:38Z

Arunas.milasius:

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

__TOC__
<h1>Summary</h1>

An Airline Supplier in SkyLog is a supplier (Vendor) of product or services to the Airline. In order for an Airline Supplier to exist there must first be an Organization and OrganizationSite to which that Airline Supplier record can be linked. Airline Supplier records must exist if any of the purchase contracting or purchase ordering modules of SkySuite are used. If the airline is using SkySuite or an integrated 3rd party product such as Promeus to produce self billing catering invoices then an Airline Supplier record must also exist for every station where invoices will be generated.

<h1>Create Organization</h1>

Organization refers to 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 an Airline Supplier the Organization type must be "Supplier" or "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 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 support request. For more details on Organizations see link [[http://wiki.skylogportal.com/index.php?title=Organization_Index'''Organizations''']]

<h1>Create Organization Sites</h1>

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 time zone of that site. The site record must exist before you can create an Airline Supplier record or for that matter any other supply chain participant type such as stations, warehouses etc.

Firstly, please check if a site is already created in SkyLog with same address and linked to the same Organization, it is important not to duplicate organization sites. For more please see link [[http://wiki.skylogportal.com/index.php?title=OrganizationSite_Index'''Organization Sites''']]

<h1>Create Airline Suppliers</h1>

To create Airline Supplier record and to maintain it please follow below described steps. Some information held under Airline Supplier records such as Main Contact and Additional Contacts are prone to change as people move in and out different roles. It is important to maintain information up to date, especially if Airline is using Skylog Purchase Order and MRP functionalities that send automated emails to suppliers when managing Purchase Orders or Contracts.

<h2>Creation of Airline Supplier Record</h2>

1. Airline supplier record can be found under Reference Data / Supply Chain Participants / Airline supplier
[[File:AirlineSupplierLocation.png]]

2. In top left corner click [[File:PlusPlus.png]] to create a new Airline Supplier record
* If you have rights to access multiple Airlines data you may have a window show up asking to select a single airline. Select airline for which new Airline Supplier Record is required.
[[File:AirlineSupplierMultiAirline.png]]

3. Airline Supplier for should be filled. Below table describes each of the fields and their importance

{| class="wikitable"
|-
! Field
! Sample
! Description
|-
| Supplier Site
| Coca Cola Enterprises
| Supplier Site is a drop down field listed with all Organization Sites linked to active Supplier records in Skylog. It is key to select correct Organization Site with correct address as this information will appear on contracts and purchase orders
|-
| Accounts Payable No.
| ABC123
| Code is usually provided by the Airline and refers to Supplier's unique ID number assigned in Airline's internal IT systems. It is essential piece for any operation that has purchase order, vendor master or any financial interfaces between customer systems and Skylog.
|-
| Default Payment Terms
| D30
| Code is usually provided by customer and refers to customer's agreed payment terms supplier. Field is often used in interfaces between Skylog and customer's systems.
|-
| Interface
| Yes/No
| it is a confirmation if Airline Supplier record is participating in interface transaction between customer IT systems and Skylog. If there is a direct interface for Purchase Orders or Vendor Details active, please select Yes.
|-
| Active
| Yes/No
| it is a confirmation if Vendor is presently active. Only Active vendors can have new items added to their portfolio and have contracts or purchase order placed in skylog.
|-
| Main Contact Details
| john.johnson@supplier.com
| it is best practice to keep Main contact information up to date for all Airline Suppliers.
|-
|}
4. click [[file:SaveSave.png]]

<h1>Additional Contacts</h1>
After supplier record is created additional information could be added such as Additional Contacts. Information from Additional Contacts is important and is used in automated email communications when purchase orders are raised, amended, cancelled or requires supplier to acknowledge or review. Note that different airlines may have different setup as per their custom requests, please consult your Local Administrator to confirm which communications have been automated for your operations.

To add new Additional Contact to specific supplier:
# Access supplier record by clicking on [[file:EditEdit.png]]
# Below basic Airline supplier details you provided you will see tab that says [[File:AdditionalContacts.png]]. Click on it.
# Use button [[file:plusplus]] to add a new contact record and fill up the form.
[[File:AdditionalContactForm.png]]

To remove no longer relevant records you have two options: either simply click on [[file:RemoveRemove.png]] next to a name and record will be deleted completely; or but edit Contact Details and mark them no longer active by clicking on [[file:EditEdit.png]] next to name and changing Active status to "No", that way records are still kept.

<h1>Adding Items to Supplier</h1>
Each stock items that is being procured reuqires a Item Supplier record to be created. A quick guide how to do that can be found following the [[StockItem_Index#Item_Suppliers|link to Stock Item page for more details]]. All Stock Items linked to specific supplier will appear under [[file:ItemsSupplied.png]] tab.

Support Index

2020-05-27T10:37:41Z

Arunas.milasius: Created page with " <h1>Summary</h1> Support Request page is used to raise open issues, questions and request to Skylog support team directly. All support requests are r..."

<h1>Summary</h1>

Support Request page is used to raise open issues, questions and request to Skylog support team directly. All support requests are reviewed and acted upon. Note that Skylog support addresses issues impacting operations with priority.

When raising a ticket it is important to select airline and Skylog area affected, provide detailed description of the problem and attach all evidence collected. Once ticket is logged you will be receiving updates with each new post or status update.

<h1>Support Request and Types</h1>
Support Request are used contact for any problems that users may experience while using Skylog. When ticket is raised emails notifications will follow with each update on the ticket or status change. Users should be alert and available to provide feedback to Support team in case of a follow up questions or request for more information.

<h1>Enhancement Request</h1>
Skylog is always evolving and improving with new functionalities. Enhancement request is the way these improvement are discussed across different operations and developer team to agree design that could benefit all.

Enhancement request requires detail description of the problem and proposed solution or user experience to address it. Then it is reviewed and potential solutions are discussed to agree on viable design to hand over to developers to prioritize and implement.

Please note that enhancement request are more complex request and requires time to be reviewed and addressed,

<h1>How to log a ticket</h1>

When logging a ticket it is essential to provide as much information as possible about the issue you are facing. Please provide detailed description of the problem, what time it occurred, and what steps were taken. It is best practice to have either video recording of the problem, full screenshot including time stamp and URL, or even putting it in a presentation document with all details.

Once information has been collected you can raise support ticket by following below steps
1. Click on [[File:PlusPlus.png]] located in the top left corner to open a support request form.
[[File:SupportRequestForm.png]]
2. In a support request window please fill every window.
## <b>Area</b> - Choose from the list of options one best describing the area in which the are facing and issue (e.g. Forecasting, Interface, Requisitioning etc).
## <b>Project</b> - Choose airline name of your account.
## <b>Category</b> - Name the type of problem you are facing. For example, if some data is not correct or not showing - Data Issue, if there is an issue with an system interface with 3rd party systems - EDI Issue, Skylog also has an option dedicated for Skylog Functional Question in case questions arise on how Skylog works.
## <b>Priority</b> - Skylog request users to identify the priority of an a problem logged. However we trust users to follow below guidelines and respecting priorities suggested:
##* Low : Used for issues found in testing environment, or problems that have no effect on operations.
##* Standard :used for majority of cases, "standard" status review and action, but it is not something that affects operation immediately and has a workaround in place.
##* Important :Reserved for cases that are affecting selected area of operations and requires immediate IT involvement to address or support with a workaround.
##* Critical: is reserved for cases when operational is frozen and cannot conduct day to day tasks in multiple areas of operations.
## <b>Subject</b> - a header title of problem logged.
## <b>Detailed</b> - a more detailed description of the problem, time and situation it has occurred.

<h1>Tips and Tricks</h1>

<h2>Monitoring tickets <h2>

[[file:SupportOtherFunctions.png]]

Skylog ticket system allows users to monitor relevant tickets. If you are interested to be kept up to date on Support request or Enhancement request, just open the ticket you are interested and click on a [[File:MonitorButton.png]].

If you, want to add someone to a ticket to receive all notifications and updates. You can do that by clicking on [[File:ViewDistributionList.png]] and [[File:PlusPlus.png]] to add at selected person

<h2>Link different tickets <h2>
You can also link different related tickets to provide more information and to make sure it is easier to track information related to request. To do so please open a ticket you an active ticket and click on [[File:LinkedTickets:png]], click on [[File:PlusPlus.png]], find relevant ticket and click to update.

AirlineSupplier Index

2020-05-27T10:09:38Z

Arunas.milasius:

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

__TOC__
<h1>Summary</h1>

An Airline Supplier in SkyLog is a supplier (Vendor) of product or services to the Airline. In order for an Airline Supplier to exist there must first be an Organization and OrganizationSite to which that Airline Supplier record can be linked. Airline Supplier records must exist if any of the purchase contracting or purchase ordering modules of SkySuite are used. If the airline is using SkySuite or an integrated 3rd party product such as Promeus to produce self billing catering invoices then an Airline Supplier record must also exist for every station where invoices will be generated.

<h1>Create Organization</h1>

Organization refers to 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 an Airline Supplier the Organization type must be "Supplier" or "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 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 support request. For more details on Organizations see link [[http://wiki.skylogportal.com/index.php?title=Organization_Index'''Organizations''']]

<h1>Create Organization Sites</h1>

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 time zone of that site. The site record must exist before you can create an Airline Supplier record or for that matter any other supply chain participant type such as stations, warehouses etc.

Firstly, please check if a site is already created in SkyLog with same address and linked to the same Organization, it is important not to duplicate organization sites. For more please see link [[http://wiki.skylogportal.com/index.php?title=OrganizationSite_Index'''Organization Sites''']]

<h1>Create Airline Suppliers</h1>

To create Airline Supplier record and to maintain it please follow below described steps. Some information held under Airline Supplier records such as Main Contact and Additional Contacts are prone to change as people move in and out different roles. It is important to maintain information up to date, especially if Airline is using Skylog Purchase Order and MRP functionalities that send automated emails to suppliers when managing Purchase Orders or Contracts.

<h2>Creation of Airline Supplier Record</h2>

1. Airline supplier record can be found under Reference Data / Supply Chain Participants / Airline supplier
[[File:Airline SupplierLocation.png]]

2. In top left corner click [[File:PlusPlus.png]] to create a new Airline Supplier record
* If you have rights to access multiple Airlines data you may have a window show up asking to select a single airline. Select airline for which new Airline Supplier Record is required.
[[File:AirlineSupplierMultiAirline.png]]

3. Airline Supplier for should be filled. Below table describes each of the fields and their importance

{| class="wikitable"
|-
! Field
! Sample
! Description
|-
| Supplier Site
| Coca Cola Enterprises
| Supplier Site is a drop down field listed with all Organization Sites linked to active Supplier records in Skylog. It is key to select correct Organization Site with correct address as this information will appear on contracts and purchase orders
|-
| Accounts Payable No.
| ABC123
| Code is usually provided by the Airline and refers to Supplier's unique ID number assigned in Airline's internal IT systems. It is essential piece for any operation that has purchase order, vendor master or any financial interfaces between customer systems and Skylog.
|-
| Default Payment Terms
| D30
| Code is usually provided by customer and refers to customer's agreed payment terms supplier. Field is often used in interfaces between Skylog and customer's systems.
|-
| Interface
| Yes/No
| it is a confirmation if Airline Supplier record is participating in interface transaction between customer IT systems and Skylog. If there is a direct interface for Purchase Orders or Vendor Details active, please select Yes.
|-
| Active
| Yes/No
| it is a confirmation if Vendor is presently active. Only Active vendors can have new items added to their portfolio and have contracts or purchase order placed in skylog.
|-
| Main Contact Details
| john.johnson@supplier.com
| it is best practice to keep Main contact information up to date for all Airline Suppliers.
|-
|}
4. click [[file:SaveSave.png]]

<h1>Additional Contacts</h1>
After supplier record is created additional information could be added such as Additional Contacts. Information from Additional Contacts is important and is used in automated email communications when purchase orders are raised, amended, cancelled or requires supplier to acknowledge or review. Note that different airlines may have different setup as per their custom requests, please consult your Local Administrator to confirm which communications have been automated for your operations.

To add new Additional Contact to specific supplier:
# Access supplier record by clicking on [[file:EditEdit.png]]
# Below basic Airline supplier details you provided you will see tab that says [[File:AdditionalContacts.png]]. Click on it.
# Use button [[file:plusplus]] to add a new contact record and fill up the form.
[[File:AdditionalContactForm.png]]

To remove no longer relevant records you have two options: either simply click on [[file:RemoveRemove.png]] next to a name and record will be deleted completely; or but edit Contact Details and mark them no longer active by clicking on [[file:EditEdit.png]] next to name and changing Active status to "No", that way records are still kept.

<h1>Adding Items to Supplier</h1>
Each stock items that is being procured reuqires a Item Supplier record to be created. A quick guide how to do that can be found following the [[StockItem_Index#Item_Suppliers|link to Stock Item page for more details]]. All Stock Items linked to specific supplier will appear under [[file:ItemsSupplied.png]] tab.

File:ItemsSupplied.png

2020-05-27T09:37:05Z

Arunas.milasius:

File:AdditionalContacts.png

2020-05-27T09:27:19Z

Arunas.milasius:

File:AdditionalContactForm.png

2020-05-27T09:26:21Z

Arunas.milasius:

File:EditEdit.png

2020-05-27T08:53:12Z

Arunas.milasius:

File:AirlineSupplierLocation.png

2020-05-27T08:51:10Z

Arunas.milasius: Arunas.milasius uploaded a new version of File:AirlineSupplierLocation.png

File:RemoveRemove.png

2020-05-27T08:50:01Z

Arunas.milasius:

File:SaveSave.png

2020-05-20T14:32:11Z

Arunas.milasius:

File:AirlineSupplierMultiAirline.png

2020-05-20T14:26:59Z

Arunas.milasius:

File:AirlineSupplierLocation.png

2020-05-20T14:26:43Z

Arunas.milasius:

Release:History

2020-05-20T11:07:24Z

Arunas.milasius:

<h1>Build 1.0.116.5</h1>
released to RS PROD on 20/05/2020
<br/>
* [New] Skylog now allows to approve requested delivery date even if lead-time is a few hours longer. More details [VSO1734/ER20933]
* [New] Warehouse Customer Services user role now allows users to raise IWTs - [VSO1956/ER15369]
* [New] Station Receipts Report now has column with Station Code in addition to OrgSite reference (United Airlines) - [VSO2012/ER23315]
[[File:StationReceipt.png]]

* [New] 2017 Provide UI option to Opt out from Enhanced requisition approval page delivered under - ER18383
* [New] Search window is now in top left corner to in Stock Item page [VSO2018], Critical Items page [VSO2019], 2023 General Search Function for Support / Enhancement Ticket page [VSO2023]
[[File:GeneralSearch.png]]

* [New] Enhanced download script applied for few more pages allowing to download up to 1 mil lines [VSO2027] NWA details.
* [New] Dashboard Configuration added to the main menu. NOTE: This is a WIP, and the grid is currently display-only. No editing. [ER23355]
<br/>

And a few bug fixes:
* [Bugfix] VSO2002 Support Project maintenance - missing some basic validations
* [Bugfix] VSO2011 SkyTrack related dashboards no longer working - [SR23349]
* [Bugfix] VSO2028 UI REQ Approval Page needs to perform a check to ensure that a Mode of Transport is selected/chosen prior to displaying the Order Qty Excess modal dialog - [SR15526]
* [Bugfix] ER15562 - Open up SSIM access to Skylog product users
* [Bugfix] ER15590 - Implemented ability to store StationCountDetail records on the ReviewDetail view
* [Bugfix] ER23283 - Fix - Abort not working for Provisional POs.
* [Bugfix] ER23435 - Fix - Not able to add attachments to a support ticket.



<h1>Build 1.0.115.5</h1>
released to RS PROD on 07/05/2020
* [Bugfix] 23655 - Unable to partially commit to a PO on RS Alpha
<br/>
<h1>Build 1.0.115.4</h1>
released to RS PROD on 28/04/2020
<br/>
released to LSY PROD on 05/05/2020
* [Bugfix] 23443 - Unable to Edit MRP
* [Bugfix] 23475 - Unable to receipt confirm
<br/>
<h1>Build 1.0.115.2</h1>
released to RS PROD on 22/04/2020
* [New] 1946 Improvements to the text and label handling on the trolley editor
* [New] 1971 Warehouse Stock Levels - All Transactions
* [New] 1994 See ticket #22991 - seems that the Provision Loading Errors page has been missed in the porting exercise
* [New] 22407 Re-instates a column that was erroneously removed from NetworkAnalysis\WarehouseDemandIndex.
<br/>
* [Bugfix] 1993 PurchaseInvoice/AwaitingApproval pages - Grid "drill-down" errors
* [Bugfix] 2002 Support Project maintenance - missing some basic validations
* [Bugfix] 15540 - Fixed Station Count Review page - the grid column 'Expected Count Qty' was taking value from the wrong column in the database view.
* [Bugfix] 23435 - error on adding attachement to support ticket.
<br/>
<h1>Build 1.0.114.1</h1>
released to RS PROD on 22/04/2020
* [New] 1904 Logging user on the Support tickets data grid - list options in alphabetical sequence please
* [New] 1931 Add Shipment tab to Inside RMA page 22863
* [New] 1957 Port maintenance pages
* [New] 1965 Request to port from legacy portal screen allowing to extend users access ER19109
* [New] 1982 See support ticket #23131 - it is not possible to endorse ERs in the MVC portal
* [New] 23075 - Added Ext. Ticket No. to support tickets.
* [New] 23227 - Added search panel to report grids.
<br/>
* [Bugfix] 21715 - Added new message for new db constraint CON_IssueHeader_Despatched.
* [Bugfix] 21835 - Ensure the Prov_POCntrctHdr_ID is set when auto-matching and finding a POMC match (for statuses up to and including Awaiting Approval).
* [Bugfix] 23139 - Requisition Approval - when only one Preferred Transport Mode record exists for the station, default to it and make the dropdown list read only.
* [Bugfix] 23163 - Changed filter configurations on Station Count Details KPI report to improve performance.
* [Bugfix] 23189 (Fix first user to be assigned to ticket wasn't added to distribution list)
<br/>
<h1>Build 1.0.113.4</h1>
released to RS PROD on 15/04/2020
* [New] 1780 Add total value to bar charts [primary charts]
* [New] 1781 Add total value to bar charts [secondary chart]
* [New] 1893 Provide Global updating capability for ItemLoss factor
* [New] 1932 Add a Shipment tab in RMA quick View 22863
* [New] 1952 add user firstName and lastName to header of skylogportal ER14637
* [New] 1961 Offer a button to make a cascading change of the Method of Transport at REQ Approval step ER16883
* [New] 1968 General Report - Station ITem KPI reports
* [New] 1969 General Reports - RMA Details
* [New] 1986 Born out of support ticket 23133, the authentication server should detect the browser being used by the end-user and if its the loathed IE, tell them to go use a better browser or suffer the consequences....
* [New] 22145 - Make WorkItem ID a filterable column in the System Errors index grid.
* [New] 22833 - Updated View_FlightLoadedItems to join to NetWorkAnalHeader and filter to return active forecasts only.
* [New] 23129 - PurchaseOrder/Show fixed to show Ultimate Warehouse destination (when applicable)
* [New] 23133 - removed client script that is not supported in IE11.
<br/>
* [Bugfix] 1973 Support Ticket #23077 - filtering by txn type is not possible.
<br/>
<h1>Build 1.0.112.4</h1>
released to RS PROD on 08/04/2020
* [New] 1767 ItemDemandForecast - Migrate View NWA Details
* [New] 1808 Support - Migrate Projects window
* [New] 1856 General Reports - Requisition Details (Performance improvements when filtering on that report)
* [New] 1903 Modify all CityPair related pages to incorporate 2 new fields (Mileage & KM's)
* [New] 1915 Urgent improvements required for the REQ approve and alter page in the MVC portal (see support ticket #22793) for details
* [New] 1916 Create pages to view the details in the new AircraftRouting table ()Changeset 34097: Changed tooltip position (removed blink effect)
* [New] 1921 Extend Airline Analytics User Profile - Supply Chain Participants/Stations
* [New] 1922 Extend Airline Analytics User Profile - StockItem/StockItem
* [New] 1923 Extend Airline Analytics User Profile - StockItem/ItemPack
* [New] 1924 Extend Airline Analytics User Profile - StockItem/ItemCatalogue
* [New] 1925 Extend Airline Analytics User Profile - StockItem/ItemSupplier
* [New] 1926 Extend Airline Analytics User Profile - StockItem/ItemWarehouse
* [New] 1937 Requisitions - tick boxes in Requisition Header pager with function to delete premanual submits
* [New] 1940 General Report - StationCountDetails report wired up for Enhanced Exporting
* [New] 1941 Add Children, Infant, Staff PAX details and diverted port detail to PAX pages developed under VSO task 1795
* [New] 1942 Add PNR code to the Special Meals window developed under VSO Task 1795
* [New] 22909 - Ensure column resizer is rendered for MRP/EditAlert (MRP Daily Figures grid)
<br/>
* [Bugfix] 1894 Suspected problem with automatic renewal of bearer token
* [Bugfix] 1943 Typo in the web.config for the Skylog MVC portal, Key = AuthenicatedRedirect
* [Bugfix] 22527 - Cosmetic issue on numerical columns when exporting to PDF
* [Bugfix] 22963 - Fix 'Awaiting Approval' Index grid - Status column is no longer hidden by default.
* [Bugfix] 22965 - Support notifications closing support related editor dialogues
* [Bugfix] 23037 - Item unit price rounding fixes for PO Contracts
<br/>
<h1>Build 1.0.111.5</h1>
released to RS PROD on 06/04/2020
* [Bugfix] 23197 - RMA Ship Confirmation - unable to save and continue Ship Qtys (gets set back to zero).
<br/>
<h1>Build 1.0.111.4</h1>
released on 01/04/2020
* [New] 1572 Porting task, (ER16499) - bring across back ordering for SAPCentric clients in to the MVC portal
* [New] 1801 Ensure the shipment linked to a Delivery change is updated with the new Expected date and inform the WMS of a date change via Receipt Advice message
* [New] 1803 UI to support two new fields that have been added to the AircraftConfiguration table - see ER #21965
* [New] 1855 Manufacturer details in Skylog - (ER20603)
* [New] 1879 Provide pages to maintain (Add or delete) Hub Airports for a particular airline
* [New] 1900 UI for planned substitution by region - (ER22245)
* [New] 1907 Create pages to view data in the BA BOM Staging tables via the portal
* [New] 1916 Create pages to view the details in the new AircraftRouting table
* [New] 1936 Bugs fixing & improvements
* [New] 22941 - Revise the enhanced requisitioning approval page to make it more flexible for operations other than Lufthansa
<br/>
* [Bugfix] 1947 (sr22999) - Planned Orders Report, when the Export to Excel button is clicked, nothing happens.
* [Bugfix] 1948 SAP Backorders functionality is ignoring Airline access rights - allowing users to view and edit requisition backorders for any airline.
* [Bugfix] 22073 - Changed the default filter operator globally for string values in Kendo grids
* [Bugfix] 22697 - Added Pick Instructions/Priority for provisional requisitions
* [Bugfix] 22887 - Fixed invalid Id reference in view.
* [Bugfix] 22925 - Removed SeqNo from POVendorDeliveryHeaderEdit viewModel
<br/>
<h1>Build 1.0.110.8</h1>
released on 26/03/2020
* [New] 22941 Revise the enhanced requisitioning approval page to make it more flexible for operations other than Lufthansa
* [Bugfix] 1947 Planned Orders Report is not downloading.
<br/>
<h1>Build 1.0.110.6</h1>
released on 19/03/2020
* [Bugfix] 1945 Enhanced report download job is not applying filters 22953
* [Bugfix] 22925 Unable to create additional vendor deliveries as a supplier for fully committed
<br/>
<h1>Build 1.0.110.3</h1>
released on 18/03/2020
* [New] 1486 Add a "waste Bin" feature - items on the aircraft layout galley canvass can be dragged to the waste bin to avoid using the delete button on users keyboard (ER 19673)
* [New] 1600 Shipments by mode of transport and on time % (drill tables) ER16865
* [New] 1689 Provide Station Executive Role Access to Station Performance dashboard
* [New] 1791 Save customized dashboard
* [New] 1795 Develop pages to display Actual PAX and Special meal quantities and request history
* [New] 1840 NWA Demand by Warehouse report 21407
* [New] 1874 General reports - Network inventory valuation
* [New] 1879 Provide pages to maintain (Add or delete) Hub Airports for a particular airline
* [New] 1889 ER22407 - Add Forecast ID to NWAD by warehouse screen
* [New] 1891 22225 - Enable Supplier relationship manager role to access to StockItem/ItemsIndex
* [New] 1895 Add Network Analysis Origin column to the View NWA pages
* [New] 1896 Reposition warehouse Inventory reporting to general reports menu
* [New] 1903 Modify all CityPair related pages to incorporate 2 new fields (Mileage & KM's)
* [New] 1905 Modify ProvioningRule pages incorporate selection by Distance of flight (Mileage) SCRIPT TO VSO!
* [New] 1913 Offer an "Add" (+) button to allow SPMs to tack-on additional materials to a REQ which is in status: Awaiting Approval (See support ticket #22273)
* [New] 1917 StockItem download contains skylog code over desc columns
<br/>
* [Bugfix] 22301 - Allowed requisition requested/approved qty > 99999 to be entered in the portal pages. Requires thorough requisition testing.
* [Bugfix] 22331 - Overcommitment warning for vendors creating delivery schedule
* [Bugfix] 22535 - Fixed inability to reassign ER's
* [Bugfix] 22793 - Added Req Status to Awaiting Approval index grid
* [Bugfix] 22805 - Dashboard chart - submitted counts. Fixed the monthly category display to show the correct month.
* [Bugfix] 22857 - Fixed infinite loop between client/authentication server for authenticated users accessing un-authorized actions.
<br/>
<h1>Build 1.0.109.3</h1>
released on 18/03/2020
* [New] 1251 Portal migration - Enhanced Requisition Approval page ##completely tested?##
* [New] 1830 Amend the Requisition Pop as per ticket request ER21997
* [New] 1835 Add alert when excel is uploaded for station stock count 20177
<br/>
* [Bugfix] 1882 Various reports of data download problems in the MVC portal, timing out if record set is more than a few thousand records (approx 10K)
* [Bugfix] 22157 - Enabled exporting all pages
* [Bugfix] 22331 - Show a warning to vendors if they try to submit a delivery schedule which over-commits to the order
* [Bugfix] 22535 - Fixed inability to reassign ER's ####close ticket on release.
* [Bugfix] 22561 - Fixes to REQ Excess Qty popup - now rounding values before sending them off to the DB
* [Bugfix] 22665 - Station Submitted Counts dashboard chart
* [Bugfix] 22887 - Fixed invalid Id reference in view.
<br/>
<h1>Build 1.0.108.2</h1>
released on 10/03/2020
* [Bugfix] 22793 - Important - /Requisition/AwaitingApproval page in the new portal doesn't show the REQ Header Status of the REQ
<br/>
<h1>Build 1.0.108.1</h1>
released on 06/03/2020
* [Bugfix] 22665 - Station Submitted Counts dashboard chart fix.
<br/>
<h1>Build 1.0.108.0</h1>
released on 02/03/2020
* [New] 1868 Improve SSIM error handling so you can set multiple records for re-run reg globally or by error nature rather than individually
* [New] 1870 Add a General Report to show Aircraft Provisioning Code Details
* [New] 1871 Add a General report to provide details of Module Contents
* [New] 1872 Add ability to maintain and view Module User Notes outside of the SkyLoad Canvases
* [New] 1873 Add a page to allow forecasting attributes to be viewed through portal
* [New] 1875 Add a page to show details in the FlightLink table
* [New] 1877 Add Exchange Rule field to Module detail Grid on view Provisioning pages
* [New] 1878 If the detail of a module is an item then disable the detail arrow to display module content as this only make sense for a module and not an item.
<br/>
* [Bugfix] 1883 Cannot read property 'weightUnit' or null
* [Bugfix] 22523 - Allow monthly negative financial consumption to display in chart.

<h1>Build 1.0.107.0</h1>
released on 02/03/2020
* [New] 1683 Adjust Module related View, Creation and Edit to accommodate new field ready for use and Share in Menu Plan
* [New] 1730 Requisitions - Migrate copy Template button
* [New] 1756 Ability to create records in AircraftContainerStowage (Stowage Rules)
* [New] 1759 Restrict SkyLoad only Aircraft related pages & menus to users with SkyLoad licenced
* [New] 1845 Station Stock Count chart sorting
* [New] 1857 Forecast Changes Approval page row upload date to be added
* [New] 1866 Restructure General reports menu in preparation for a lot more reports
* [New] 1869 Remove the Upload and Offload Offset (days) from Provision Loading Pages
<br/>
* [Bugfix] 1686 Position and move ability of picture window on canvasses is a problem (improve functionality)
* [Bugfix] 1849 Airline selector doesn't work after loading stored filters (multipage problem)
* [Bugfix] 22287 - Users with no restrictions on their ticket access should now be able to see ALL tickets.
    (No ticket) - Station Count Details report improved so that it automatically filters out data for stations the user doesn't have access to
<br/>
<h1>Build 1.0.106.3</h1>
Release date 26/02/2020
* [New] 1541 StationItem - Automatic Requisition Items
* [New] 1731 Purchase Order - PO Notes page
* [New] 1750 In full delivery - Supplier - ER18809 - [Drill down]
* [New] 1768 StockItem - Item Supplier Mapping
* [New] 1779 Add ability to download data in excel for All Chart-related data grids.
* [New] 1785 Hide empty Months in dashboards
* [New] 1790 Add button to reset filters
* [New] 1795 Develop pages to display Actual PAX and Special meal quantities and request history
* [New] 1847 Improve error handling for container type editing in the canvas.
* [New] 20095 - Re-added the SLX Dummy Airline's items to StockItem listing grids, and added SLX Dummy Airline as a grid filter option
* [New] 21833 - Internal (SLX Staff) URL links appear in the user account context menu (i.e. profile/support/ log out menu)
<br/>
* [Bugfix] 1788 Drill down chart for Warehouse Valuation needs to be populated
* [Bugfix] 1848 dashboard charts are showing Month+1
* [Bugfix] 22037 - Fixed a null reference error when cancelling a PO's balance from Receipt Confirmation page
* [Bugfix] 22053 - Check user role is authorized to approvde POMCs, at PO/Airline configuration level
* [Bugfix] 22103 - Fixed password reset functionality in AuthServer project (affects files in this project too though, hence the mention)
<br/>
<h1>Build 1.0.105.1</h1>
Release date 18/02/2020
* [Bugfix] 22241 User unable to access the bond station
<br/>
<h1>Build 1.0.105.0</h1>
Release date 13/02/2020
* [New] 1542 Atlas Chiller Icon required for Galley Editor
* [New] 1729 StockItem - pdf button to download Item catalogue list with pictures
* [New] 1736 Count Details Bespoke reports to display number values
* [New] 1756 Ability to create records in AircraftContainerStowage (Stowage Rules)
* [New] 1758 Create portal pages to show Stowage Types and related Container Compatibility
* [New] 1759 Restrict SkyLoad only Aircraft related pages & menus to users with SkyLoad licenced
* [New] 1780 Add total value to bar charts [primary charts]
* [New] 1782 add button to be able to filter bar charts timeline
* [New] 1786 Adjust Legend
* [New] 1787 Add Legend to Warehouse Valuation Chart
* [New] 1792 add country to station performance filter table
<br/>
* [Bugfix] 1800 PO Shipment Splitting - change to the expected date for an existing delivery is not sending an update ReceiptAdvice to the WMS
<h1>Build 1.0.104.2</h1>
Release date 13/02/2020
* [New] 1300 In Full delivery - Supplier - ER18809
* [New] 1548 UI functionality of splitting PO shipments
* [New] 1557 See Support ticket #20027 - improve Error handling when a PO is raised for materials with differing currencies.
    Prevent adding items to a PO if their currency doesn't match with the items already on the PO
* [New] 1567 Create UI for "No Fly" item status Yes/No in stockitem screen
    #1305 / #18801 Added No-Fly flag to the StockItem grid
* [New] 1597 Station Count - Breakages
* [New] 1662 M/T changes required for vendor shipment splitting
* [New] 1740 Restrict access to the galley canvas if a user doesn't have SSO grants.
* [New] 1752 City Pairs & Markets - Improve "Delete" functionality
* [New] 1753 All dashboard charts require the date value displayed in the X-Axis to be in "MMM-YY" date format
* [New] 1765 Improve filters and order by when displaying aircraft stowages from the flight schedule page
* [New] er19939 PO Splitting (PO Vendor Deliveries)
<br/>
* [Bugfix] 1737 Requisition Excess Ordering Thresholds - duplicate logs can be created quite easily
    Avoid having duplicate entries in the RequisitionDetailExcessOrderQtyLog with the addition of a new "Counter" field - attempting to approve the same excessive figures multiple times should now increase the counter field rather than insert a new (duplicate) record.
* [Bugfix] 1757 Item Demand Forecast - External Forecast Data -> Unable to delete row
* [Bugfix] 1762 Support Tickets - Watch List is showing too many records in the new portal.
* [Bugfix] 1772 Several Grids - not possible navigate across different pages of the grids
* [Bugfix] SR21531 - Contract Items report is not loading - fixed
* [Bugfix] sr21633 Changed sort order on Stock Unit DDL
* [Bugfix] sr21655 Fixed issue causing users to be unable to save changes to Station Count Categories (already patched)
<br/>
<h1>Build 1.0.103.6</h1>
Release date 29/01/2020
* [Bugfix] 1769 Error preventing access to Aircraft Layout Editor
<br/>
<h1>Build 1.0.103.5</h1>
Release date 27/01/2020
* [New] 1570 Stock Item - Item Catalog Portal
* [New] 1597 Station Count - Breakages
* [New] 1658 Porting issue - Purchase Order Contract content in the MVC Portal does not allow you to view a break-down of POCntrctDet_ConsQty; this is available in the legacy portal though
* [New] 1669 Allow access to General reports: Issue details, PO lines, contracted Items and Items on PO contracts to Supplier manager role
* [New] 1688 Provide functionality to add/edit and delete module content if SkyLoad is not enabled
* [New] 1741 Enhancements to the SSO Security token functionality.
* [New] 21353 - Make PO Master Contract PDF Generation and Existing documents listing available in Show page, Index Grid (Existing Docs grid on index page)
<br/>
* [Bugfix] 1650 Support Request #20625 - MVC UI is showing misleading information when viewing the break-down of Expected Receipts where the receipt is for a Partially Received PO.
* [Bugfix] 1686 Position and move ability of picture window on canvasses is a problem
* [Bugfix] 1727 When approving a req in MVCRSTEST you get a message ‘true’ pop up after it tells you orders will be create etc.
* [Bugfix] 1738 Unfriendly error is displayed when validation fails for new Aircraft Module creation
* [Bugfix] 20065 - Added SupplierManager roles to the authorised roles for PurchaseOrderDetailSummary_Read (listing of PO Details)
* [Bugfix] 20089 - Edit button hidden for non-SLX users on grids presented on: ItemWarehouse index, ItemPacks index, TransportChains index, and Count Category index views, show button also added which is always available and presents the same data in read-only form.
* [Bugfix] 20105 - Added a help / explain button on the Shipments grid on EditRestrictedPurchaseOrder view
* [Bugfix] 20467 - Fixed DDL population when creating a new PO (delivering to warehouse or warehouse via whse transfer)
* [Bugfix] 21393 - Fix POMC Lookup in PO Creation. (also tested and patched out to 1.0.102.x)
* [Bugfix] 21549 (add any New Airline Supplier records)
<br/>
<h1>Build 1.0.102.6</h1>
Release date 21/01/2020
* [New] 1567 Create UI for "No Fly" item status Yes/No in stockitem screen
* [New] 1598 Airline Supplier - additional contacts
* [New] 1643 Add new field to Contracted items general report
* [New] 1688 Provide functionality to add/edit and delete module content if SkyLoad is not enabled
* [New] 1706 Warehouse - Adjustments screen
* [New] 1710 Implement External order reference for SAP Requisitions
* [New] 1715 Stock count - Migrate columns 'Cancelled' and 'Complete' in Stock Count overview
<br/>
* [Bugfix] 1675 Problem with functionality to delete a stockitem (fix deletion logic)
* [Bugfix] 1701 Purchase Invoicing > All POs Grid shows incorrect value for 'Direct Delivery'.
* [Bugfix] 1727 When approving a requisition, you get a message ‘true’ pop up after it tells you orders will be create etc.
* [Bugfix] 20719 - StockItem edits - ensure Item Cost, Weight, and Item Pack Weight allow up to 6 decimal points precision.
* [Bugfix] 21275 - Fixed grid sorting bug on Stock Item Index grid
* [Bugfix] 21239 - Fixed several Back Order edit issues
* [Bugfix] 21287 - PO Lines report updated to initially sort on PO Creation Date descending.
* [Bugfix] 21393 - Fixed the Contract Reference lookup for PO Edits.
<br/>
<h1>Build 1.0.101.2</h1>
Release date 08/01/2020
* [New] 1568 StationItem - Select Station Items to be Updated using latest station defaults
* [New] 1569 Stock Item - Stock Item Replacements
* [New] 1638 StationItems - migration of station items page
* [New] 1656 Drill down on Open PO status dashboard chart
* [New] 1664 RMA - Ability to amend RMA ETA after RMA has been approved.
* [New] 1668 Bespoke MRP Batch Report amendment
* [New] 1680 Need the ability to create module details for a Miscellaneous Container Group
<br/>
* [Bugfix] 1532 Prevent ability to add disabled users to a ticket's distribution list.
* [Bugfix] 1650 Support Request #20625 - Portal is showing misleading information when viewing the break-down of Expected Receipts where the receipt is for a Partially Received PO.
* [Bugfix] 1647 Support Ticket #20635 - When adding a new Airline Supplier in the portal needs to auto-trim the Supplier Account Number.
* [Bugfix] 1674 Fixed several bugs in the Substitutions module.
* [Bugfix] 1677 Improved error handling in Item Pack maintenance pages.
* [Bugfix] 1685 Stock item editing. Exception if Pack levels have the same "Pack Description" value.
* [Bugfix] 1687 Default Image not showing in the Modules page.
* [Bugfix] 1713 Unable to edit provisional RMAs in v1.0.101.0
* [Bugfix] SR17939 - Disabled selection mode on Station Count items grid and adjusted control heights to hopefully improve the cell-selection issue (Changeset 33196)
* [Bugfix] SR20593 - KPI requisition detail - fixed filter behaviour for the 'Substitute' column.
* [Bugfix] SR21103 - Requisition editing (pre-approval and approval), Save and Continue now retains the Item Grid page number that the user was on.
* [Bugfix] SR21111 - SSIM Index Grid initial sort order now by created date descending.
<br/>
<h1>Build 1.0.100.3</h1>
Release date 03/01/2020
* [New] 1451 Support middle-tier upload function In Progress (Tidied margins and added upload button to change approval page)
* [New] 1496 Validation of supplier contact email
* [New] 1558 Waste Trolley shouldn't be chilled
* [New] 1588 MRP - Planner Orders - Additional columns for "Soft POs"
* [New] 1595 KPI receipt - station receipt report with additional columns
* [New] 1596 KPI report - IWT Details report
* [New] 1607 Supplier Performance Dashboard - Supplier On Time Commitment chart
* [New] 1610 Supplier Performance Dashboard - Dashboard Open POs Status chart
* [New] 1618 Validation needed when changing an Organization Type
* [New] 1648 Add Cost Centre Category Code to GL Account Category pages
* [New] 1649 Small changes and tidy up to GL Cost Centre category pages
* [New] 1652 Implemented ability to maintain Alternative Aircraft Codes
* [New] 1655 Better handled violations of Unique Index: IDX_RequisitionDetail_ReqHdr_ID__StkItem_ID__ReqDate__ExtLineRef, currently an unfriendly error message is presented to the user, which causes confusion
* [New] 1663 Implemented ability to resolve an SSIM that was burst with errors.
* [New] 1667 Release banner should come up at Home Screen and as a banner T-10 minutes
* [New] 20669 Quantity fields on Station Counts now only validated on submission (so users can save as they go)
* [New] 20923 Saving a station will now only validate Default Loading (and it's relation to other active caterer stations) if the user actually changed the value
<br/>
* [Bugifx] 1549 Portal doesn't display extended characters correctly on drop down lists
* [Bugfix] 1632 Non default pack quantity not enforced when adding items to back orders
* [Bugfix] 1633 AircraftStowagePositionList Report Error
* [Bugfix] 1654 Filtering on Aircraft Type page is not working as it should
<br/>
<h1>Build 1.0.99.4</h1>
Release date 18/12/2019
* [Bugfix] 1642 SkyLog tickets - responsible user needs to be included in the e-mail list
* [Bugfix] 1676 StockitemForecastLoadfactor decimal precision not being displayed correctly
* [Bugfix] 1678 Deletion of an AircraftModule logic when to activate the delete icon is wrong
<br/>
<h1>Build 1.0.99.2</h1>
Release date 12/12/2019
* [New] 1442 Display days coverage in MRP Daily figure
* [New] 1451 Support m/t upload function
* [New] 1527 When dragging a stowage position to the Galley canvas where is the default unit of Dims coming from? Also Min check needs explaining in terms of the unit
* [New] 1550 Implemented ability to review forecasts
* [New] 1601 Tidy up Aircraft Tail Number pages
* [New] 1605 Dashboard - Drill data implemented for the Late Open PO shipments chart.
* [New] 1609 Planned Orders - UI - General reports to display data from MRPSoftOrderDetail
* [New] 1615 Make SLX portal version identifier clickable - redirecting you to release history on the wiki
* [New] 1617 Add Organization Type to Airline Supplier pages
* [New] 1629 ER 20479 - Add External Line Number column to the PO lines KPI report
<br/>
* [Bugfix] 1446 SkylogistiX Wiki - Fix to improve the performance of the portal (reducing database reads).
* [Bugfix] 20515 - Improved error handling for bespoke reports
* [Bugfix] 20637 - Improved performance for loading items to add to Requisition
* [Bugfix] 1148 Add time stamp to error pop-ups
* [Bugfix] 1375 Enhance filters across all pages / grids = trimming numeric filter searches
* [Bugfix] 1470 Support Ticket #19505 - Unable to export Bespoke Reports to MS-Excel
* [Bugfix] 1639 SkyLog tickets - line breaks in the Detailed Description of the Problem
* [Bugfix] 1642 SkyLog tickets - responsible user needs to be included in the e-mail list
<br/>
<h1>Build 1.0.98.3</h1>
Release date 06/12/2019
* [New] 1218 Add a delete Icon to the StockItem/Index page to allow stock items to be deleted
* [New] 1492 Substitution Module / Unplanned Substitutions migrated to new portal
* [New] 1500 PO Lines data grid - files downloaded into csv/xls should have a date format adjusted to dd/mm/yyyy
* [New] 1511 ItemSupplier index grid updated to include new columns
* [New] 1580 Station Performance dashboard - Add "under review" and "recount" statuses to "Station Stock Count" chart.
* [New] 1593 Planned orders - UI - Add field forecasting period to Item supplier - Warehouse grid
* [New] 1622 Station KPI - Station late orders table need mode of transport
* [New] 1621 New Dashboard Group: 'Supplier Performance'
* [New] 1604 'Supplier Performance' Dashboard chart - Late Open PO shipments
<br/>
* [Bugfix] 1611 Consumption chart not rendering categories in the correct order when when filters are applied.
* [Bugfix] 1612 Station KPI dashboard - Station count chart refresh
* [Bugfix] 1470 Support Ticket #19505 - Unable to export Bespoke Reports to MS-Excel
* [Bugfix] 1562 Aircraft Config - Creation Date Failure
* [Bugfix] 1608 Module Copy & Delete Issues
* [Bugfix] 1619 "sortablejs" node modules call exception when canvas loading
* [Bugfix] 19133 - Sort order on Requisition Approval grid changes dependent on whether or not the airline is using Loading Groups.
* [Bugfix] 20289 - StationCountCategory Edit page improvements - fields for IncludeAllSPL and UpdateSPL are now read-only with appropriate values if Approval is not required.
* [Bugfix] 20375 - Changed option label for "Climate Requirements" on adding a stockitem
* [Bugfix] 20379 - Fixed incorrect field binding on Stock Allocated to Warehouse Transfers grid (outbound)
* [Bugfix] 20437 - Fixed method used to retrieve the blank count file - now returns the latest if there's multiple
* [Bugfix] 20465 - Export button added to non-SAP-centric BackOrder items grid
* [Bugfix] 20487 - Added Rule Sequence field to Provisioning Rules grid
* [Bugfix] 20489 - Changed query for Expected Warehouse Transfers (Stock Levels) grid so that it's based on WarehouseTransferReceipt rather than WarehouseTransferDetail.
* [Bugfix] 20515 - Fixed error handling on Bespoke Reports.
<br/>
<h1>Build 1.0.97.0</h1>
Release date 02/12/2019
* [New] 1297 - Dashboard Chart - Shipments by Mode of Transport and On Time % - ER16865
* [New] 1446 - SkylogistiX Wiki
* [New] 1492 - (minor errors) Substitution Module / unplanned substitutions website
* [New] 1520 - Port across functionality to allow the User Station Access table to be managed through the new portal
* [New] 1566 - When creating a new Station Par Level entry (Station Item record), we should check to see if the "new" material has been associated with the station previously
* [New] 1585 - Make the 'Network On Time Receipts' chart wider by default, and allow to be re-sizeable.
<br/>
* [Bugfix] 1499 - StationCount Detail 'Last Count Date' not being populated in some cases (19641)
* [Bugfix] 1613 - SR20423 - Build v1.0.96.0 has introduced a bug - problems editing ItemWarehouse records from page: /StockItem/Edit
* [Bugfix] 1623 - SR20433 - Back Order processing - it is not possible to ship from an alternate warehouse
* [Bugfix] 1626 - Unable to submit Requisitions in 1.0.97.x
* [Bugfix] 1631 - MRP Supply Parameters - Item Warehouse edit bug
<br/><h1>Build 1.0.96.0</h1>
Release date 20/11/2019
* [New] 1520 - Port across functionality to allow User Station Access to be managed in the new portal
* [New] 1555 - Added Planner Name column to the Stock Levels index grid
* [New] 20055 - MOQ and EOQ fields on Item Warehouse editor template
* [New] 1519 - Warehouse Inventory Valuations Report (KPI)
<br/>
* [Bugfix] 1563 - Duplicate Container Item Type
* [Bugfix] 1558 - Waste Trolley should not be chilled
* [Bugfix] 20133 - Transit Only field bug on editing Warehouse
* [Bugfix] 1453 - UI allows an MRP line to be submitted even if the Qty control is not showing a figure/value
* [Bugfix] 20171 - Problems adding Stock Item Packs

Release:History

2020-05-20T11:05:38Z

Arunas.milasius:

<h1>Build 1.0.116.5</h1>
released to RS PROD pending (original released date 13/05/2020 postponed)
<br/>
* [New] Skylog now allows to approve requested delivery date even if lead-time is a few hours longer. More details [VSO1734/ER20933]
* [New] Warehouse Customer Services user role now allows users to raise IWTs - [VSO1956/ER15369]
* [New] Station Receipts Report now has column with Station Code in addition to OrgSite reference (United Airlines) - [VSO2012/ER23315]
[[File:StationReceipt.png]]

* [New] 2017 Provide UI option to Opt out from Enhanced requisition approval page delivered under - ER18383
* [New] Search window is now in top left corner to in Stock Item page [VSO2018], Critical Items page [VSO2019], 2023 General Search Function for Support / Enhancement Ticket page [VSO2023]
[[File:GeneralSearch.png]]

* [New] Enhanced download script applied for few more pages allowing to download up to 1 mil lines [VSO2027] NWA details.
* [New] Dashboard Configuration added to the main menu. NOTE: This is a WIP, and the grid is currently display-only. No editing. [ER23355]
<br/>

And a few bug fixes:
* [Bugfix] VSO2002 Support Project maintenance - missing some basic validations
* [Bugfix] VSO2011 SkyTrack related dashboards no longer working - [SR23349]
* [Bugfix] VSO2028 UI REQ Approval Page needs to perform a check to ensure that a Mode of Transport is selected/chosen prior to displaying the Order Qty Excess modal dialog - [SR15526]
* [Bugfix] ER15562 - Open up SSIM access to Skylog product users
* [Bugfix] ER15590 - Implemented ability to store StationCountDetail records on the ReviewDetail view
* [Bugfix] ER23283 - Fix - Abort not working for Provisional POs.
* [Bugfix] ER23435 - Fix - Not able to add attachments to a support ticket.



<h1>Build 1.0.115.5</h1>
released to RS PROD on 07/05/2020
* [Bugfix] 23655 - Unable to partially commit to a PO on RS Alpha
<br/>
<h1>Build 1.0.115.4</h1>
released to RS PROD on 28/04/2020
<br/>
released to LSY PROD on 05/05/2020
* [Bugfix] 23443 - Unable to Edit MRP
* [Bugfix] 23475 - Unable to receipt confirm
<br/>
<h1>Build 1.0.115.2</h1>
released to RS PROD on 22/04/2020
* [New] 1946 Improvements to the text and label handling on the trolley editor
* [New] 1971 Warehouse Stock Levels - All Transactions
* [New] 1994 See ticket #22991 - seems that the Provision Loading Errors page has been missed in the porting exercise
* [New] 22407 Re-instates a column that was erroneously removed from NetworkAnalysis\WarehouseDemandIndex.
<br/>
* [Bugfix] 1993 PurchaseInvoice/AwaitingApproval pages - Grid "drill-down" errors
* [Bugfix] 2002 Support Project maintenance - missing some basic validations
* [Bugfix] 15540 - Fixed Station Count Review page - the grid column 'Expected Count Qty' was taking value from the wrong column in the database view.
* [Bugfix] 23435 - error on adding attachement to support ticket.
<br/>
<h1>Build 1.0.114.1</h1>
released to RS PROD on 22/04/2020
* [New] 1904 Logging user on the Support tickets data grid - list options in alphabetical sequence please
* [New] 1931 Add Shipment tab to Inside RMA page 22863
* [New] 1957 Port maintenance pages
* [New] 1965 Request to port from legacy portal screen allowing to extend users access ER19109
* [New] 1982 See support ticket #23131 - it is not possible to endorse ERs in the MVC portal
* [New] 23075 - Added Ext. Ticket No. to support tickets.
* [New] 23227 - Added search panel to report grids.
<br/>
* [Bugfix] 21715 - Added new message for new db constraint CON_IssueHeader_Despatched.
* [Bugfix] 21835 - Ensure the Prov_POCntrctHdr_ID is set when auto-matching and finding a POMC match (for statuses up to and including Awaiting Approval).
* [Bugfix] 23139 - Requisition Approval - when only one Preferred Transport Mode record exists for the station, default to it and make the dropdown list read only.
* [Bugfix] 23163 - Changed filter configurations on Station Count Details KPI report to improve performance.
* [Bugfix] 23189 (Fix first user to be assigned to ticket wasn't added to distribution list)
<br/>
<h1>Build 1.0.113.4</h1>
released to RS PROD on 15/04/2020
* [New] 1780 Add total value to bar charts [primary charts]
* [New] 1781 Add total value to bar charts [secondary chart]
* [New] 1893 Provide Global updating capability for ItemLoss factor
* [New] 1932 Add a Shipment tab in RMA quick View 22863
* [New] 1952 add user firstName and lastName to header of skylogportal ER14637
* [New] 1961 Offer a button to make a cascading change of the Method of Transport at REQ Approval step ER16883
* [New] 1968 General Report - Station ITem KPI reports
* [New] 1969 General Reports - RMA Details
* [New] 1986 Born out of support ticket 23133, the authentication server should detect the browser being used by the end-user and if its the loathed IE, tell them to go use a better browser or suffer the consequences....
* [New] 22145 - Make WorkItem ID a filterable column in the System Errors index grid.
* [New] 22833 - Updated View_FlightLoadedItems to join to NetWorkAnalHeader and filter to return active forecasts only.
* [New] 23129 - PurchaseOrder/Show fixed to show Ultimate Warehouse destination (when applicable)
* [New] 23133 - removed client script that is not supported in IE11.
<br/>
* [Bugfix] 1973 Support Ticket #23077 - filtering by txn type is not possible.
<br/>
<h1>Build 1.0.112.4</h1>
released to RS PROD on 08/04/2020
* [New] 1767 ItemDemandForecast - Migrate View NWA Details
* [New] 1808 Support - Migrate Projects window
* [New] 1856 General Reports - Requisition Details (Performance improvements when filtering on that report)
* [New] 1903 Modify all CityPair related pages to incorporate 2 new fields (Mileage & KM's)
* [New] 1915 Urgent improvements required for the REQ approve and alter page in the MVC portal (see support ticket #22793) for details
* [New] 1916 Create pages to view the details in the new AircraftRouting table ()Changeset 34097: Changed tooltip position (removed blink effect)
* [New] 1921 Extend Airline Analytics User Profile - Supply Chain Participants/Stations
* [New] 1922 Extend Airline Analytics User Profile - StockItem/StockItem
* [New] 1923 Extend Airline Analytics User Profile - StockItem/ItemPack
* [New] 1924 Extend Airline Analytics User Profile - StockItem/ItemCatalogue
* [New] 1925 Extend Airline Analytics User Profile - StockItem/ItemSupplier
* [New] 1926 Extend Airline Analytics User Profile - StockItem/ItemWarehouse
* [New] 1937 Requisitions - tick boxes in Requisition Header pager with function to delete premanual submits
* [New] 1940 General Report - StationCountDetails report wired up for Enhanced Exporting
* [New] 1941 Add Children, Infant, Staff PAX details and diverted port detail to PAX pages developed under VSO task 1795
* [New] 1942 Add PNR code to the Special Meals window developed under VSO Task 1795
* [New] 22909 - Ensure column resizer is rendered for MRP/EditAlert (MRP Daily Figures grid)
<br/>
* [Bugfix] 1894 Suspected problem with automatic renewal of bearer token
* [Bugfix] 1943 Typo in the web.config for the Skylog MVC portal, Key = AuthenicatedRedirect
* [Bugfix] 22527 - Cosmetic issue on numerical columns when exporting to PDF
* [Bugfix] 22963 - Fix 'Awaiting Approval' Index grid - Status column is no longer hidden by default.
* [Bugfix] 22965 - Support notifications closing support related editor dialogues
* [Bugfix] 23037 - Item unit price rounding fixes for PO Contracts
<br/>
<h1>Build 1.0.111.5</h1>
released to RS PROD on 06/04/2020
* [Bugfix] 23197 - RMA Ship Confirmation - unable to save and continue Ship Qtys (gets set back to zero).
<br/>
<h1>Build 1.0.111.4</h1>
released on 01/04/2020
* [New] 1572 Porting task, (ER16499) - bring across back ordering for SAPCentric clients in to the MVC portal
* [New] 1801 Ensure the shipment linked to a Delivery change is updated with the new Expected date and inform the WMS of a date change via Receipt Advice message
* [New] 1803 UI to support two new fields that have been added to the AircraftConfiguration table - see ER #21965
* [New] 1855 Manufacturer details in Skylog - (ER20603)
* [New] 1879 Provide pages to maintain (Add or delete) Hub Airports for a particular airline
* [New] 1900 UI for planned substitution by region - (ER22245)
* [New] 1907 Create pages to view data in the BA BOM Staging tables via the portal
* [New] 1916 Create pages to view the details in the new AircraftRouting table
* [New] 1936 Bugs fixing & improvements
* [New] 22941 - Revise the enhanced requisitioning approval page to make it more flexible for operations other than Lufthansa
<br/>
* [Bugfix] 1947 (sr22999) - Planned Orders Report, when the Export to Excel button is clicked, nothing happens.
* [Bugfix] 1948 SAP Backorders functionality is ignoring Airline access rights - allowing users to view and edit requisition backorders for any airline.
* [Bugfix] 22073 - Changed the default filter operator globally for string values in Kendo grids
* [Bugfix] 22697 - Added Pick Instructions/Priority for provisional requisitions
* [Bugfix] 22887 - Fixed invalid Id reference in view.
* [Bugfix] 22925 - Removed SeqNo from POVendorDeliveryHeaderEdit viewModel
<br/>
<h1>Build 1.0.110.8</h1>
released on 26/03/2020
* [New] 22941 Revise the enhanced requisitioning approval page to make it more flexible for operations other than Lufthansa
* [Bugfix] 1947 Planned Orders Report is not downloading.
<br/>
<h1>Build 1.0.110.6</h1>
released on 19/03/2020
* [Bugfix] 1945 Enhanced report download job is not applying filters 22953
* [Bugfix] 22925 Unable to create additional vendor deliveries as a supplier for fully committed
<br/>
<h1>Build 1.0.110.3</h1>
released on 18/03/2020
* [New] 1486 Add a "waste Bin" feature - items on the aircraft layout galley canvass can be dragged to the waste bin to avoid using the delete button on users keyboard (ER 19673)
* [New] 1600 Shipments by mode of transport and on time % (drill tables) ER16865
* [New] 1689 Provide Station Executive Role Access to Station Performance dashboard
* [New] 1791 Save customized dashboard
* [New] 1795 Develop pages to display Actual PAX and Special meal quantities and request history
* [New] 1840 NWA Demand by Warehouse report 21407
* [New] 1874 General reports - Network inventory valuation
* [New] 1879 Provide pages to maintain (Add or delete) Hub Airports for a particular airline
* [New] 1889 ER22407 - Add Forecast ID to NWAD by warehouse screen
* [New] 1891 22225 - Enable Supplier relationship manager role to access to StockItem/ItemsIndex
* [New] 1895 Add Network Analysis Origin column to the View NWA pages
* [New] 1896 Reposition warehouse Inventory reporting to general reports menu
* [New] 1903 Modify all CityPair related pages to incorporate 2 new fields (Mileage & KM's)
* [New] 1905 Modify ProvioningRule pages incorporate selection by Distance of flight (Mileage) SCRIPT TO VSO!
* [New] 1913 Offer an "Add" (+) button to allow SPMs to tack-on additional materials to a REQ which is in status: Awaiting Approval (See support ticket #22273)
* [New] 1917 StockItem download contains skylog code over desc columns
<br/>
* [Bugfix] 22301 - Allowed requisition requested/approved qty > 99999 to be entered in the portal pages. Requires thorough requisition testing.
* [Bugfix] 22331 - Overcommitment warning for vendors creating delivery schedule
* [Bugfix] 22535 - Fixed inability to reassign ER's
* [Bugfix] 22793 - Added Req Status to Awaiting Approval index grid
* [Bugfix] 22805 - Dashboard chart - submitted counts. Fixed the monthly category display to show the correct month.
* [Bugfix] 22857 - Fixed infinite loop between client/authentication server for authenticated users accessing un-authorized actions.
<br/>
<h1>Build 1.0.109.3</h1>
released on 18/03/2020
* [New] 1251 Portal migration - Enhanced Requisition Approval page ##completely tested?##
* [New] 1830 Amend the Requisition Pop as per ticket request ER21997
* [New] 1835 Add alert when excel is uploaded for station stock count 20177
<br/>
* [Bugfix] 1882 Various reports of data download problems in the MVC portal, timing out if record set is more than a few thousand records (approx 10K)
* [Bugfix] 22157 - Enabled exporting all pages
* [Bugfix] 22331 - Show a warning to vendors if they try to submit a delivery schedule which over-commits to the order
* [Bugfix] 22535 - Fixed inability to reassign ER's ####close ticket on release.
* [Bugfix] 22561 - Fixes to REQ Excess Qty popup - now rounding values before sending them off to the DB
* [Bugfix] 22665 - Station Submitted Counts dashboard chart
* [Bugfix] 22887 - Fixed invalid Id reference in view.
<br/>
<h1>Build 1.0.108.2</h1>
released on 10/03/2020
* [Bugfix] 22793 - Important - /Requisition/AwaitingApproval page in the new portal doesn't show the REQ Header Status of the REQ
<br/>
<h1>Build 1.0.108.1</h1>
released on 06/03/2020
* [Bugfix] 22665 - Station Submitted Counts dashboard chart fix.
<br/>
<h1>Build 1.0.108.0</h1>
released on 02/03/2020
* [New] 1868 Improve SSIM error handling so you can set multiple records for re-run reg globally or by error nature rather than individually
* [New] 1870 Add a General Report to show Aircraft Provisioning Code Details
* [New] 1871 Add a General report to provide details of Module Contents
* [New] 1872 Add ability to maintain and view Module User Notes outside of the SkyLoad Canvases
* [New] 1873 Add a page to allow forecasting attributes to be viewed through portal
* [New] 1875 Add a page to show details in the FlightLink table
* [New] 1877 Add Exchange Rule field to Module detail Grid on view Provisioning pages
* [New] 1878 If the detail of a module is an item then disable the detail arrow to display module content as this only make sense for a module and not an item.
<br/>
* [Bugfix] 1883 Cannot read property 'weightUnit' or null
* [Bugfix] 22523 - Allow monthly negative financial consumption to display in chart.

<h1>Build 1.0.107.0</h1>
released on 02/03/2020
* [New] 1683 Adjust Module related View, Creation and Edit to accommodate new field ready for use and Share in Menu Plan
* [New] 1730 Requisitions - Migrate copy Template button
* [New] 1756 Ability to create records in AircraftContainerStowage (Stowage Rules)
* [New] 1759 Restrict SkyLoad only Aircraft related pages & menus to users with SkyLoad licenced
* [New] 1845 Station Stock Count chart sorting
* [New] 1857 Forecast Changes Approval page row upload date to be added
* [New] 1866 Restructure General reports menu in preparation for a lot more reports
* [New] 1869 Remove the Upload and Offload Offset (days) from Provision Loading Pages
<br/>
* [Bugfix] 1686 Position and move ability of picture window on canvasses is a problem (improve functionality)
* [Bugfix] 1849 Airline selector doesn't work after loading stored filters (multipage problem)
* [Bugfix] 22287 - Users with no restrictions on their ticket access should now be able to see ALL tickets.
    (No ticket) - Station Count Details report improved so that it automatically filters out data for stations the user doesn't have access to
<br/>
<h1>Build 1.0.106.3</h1>
Release date 26/02/2020
* [New] 1541 StationItem - Automatic Requisition Items
* [New] 1731 Purchase Order - PO Notes page
* [New] 1750 In full delivery - Supplier - ER18809 - [Drill down]
* [New] 1768 StockItem - Item Supplier Mapping
* [New] 1779 Add ability to download data in excel for All Chart-related data grids.
* [New] 1785 Hide empty Months in dashboards
* [New] 1790 Add button to reset filters
* [New] 1795 Develop pages to display Actual PAX and Special meal quantities and request history
* [New] 1847 Improve error handling for container type editing in the canvas.
* [New] 20095 - Re-added the SLX Dummy Airline's items to StockItem listing grids, and added SLX Dummy Airline as a grid filter option
* [New] 21833 - Internal (SLX Staff) URL links appear in the user account context menu (i.e. profile/support/ log out menu)
<br/>
* [Bugfix] 1788 Drill down chart for Warehouse Valuation needs to be populated
* [Bugfix] 1848 dashboard charts are showing Month+1
* [Bugfix] 22037 - Fixed a null reference error when cancelling a PO's balance from Receipt Confirmation page
* [Bugfix] 22053 - Check user role is authorized to approvde POMCs, at PO/Airline configuration level
* [Bugfix] 22103 - Fixed password reset functionality in AuthServer project (affects files in this project too though, hence the mention)
<br/>
<h1>Build 1.0.105.1</h1>
Release date 18/02/2020
* [Bugfix] 22241 User unable to access the bond station
<br/>
<h1>Build 1.0.105.0</h1>
Release date 13/02/2020
* [New] 1542 Atlas Chiller Icon required for Galley Editor
* [New] 1729 StockItem - pdf button to download Item catalogue list with pictures
* [New] 1736 Count Details Bespoke reports to display number values
* [New] 1756 Ability to create records in AircraftContainerStowage (Stowage Rules)
* [New] 1758 Create portal pages to show Stowage Types and related Container Compatibility
* [New] 1759 Restrict SkyLoad only Aircraft related pages & menus to users with SkyLoad licenced
* [New] 1780 Add total value to bar charts [primary charts]
* [New] 1782 add button to be able to filter bar charts timeline
* [New] 1786 Adjust Legend
* [New] 1787 Add Legend to Warehouse Valuation Chart
* [New] 1792 add country to station performance filter table
<br/>
* [Bugfix] 1800 PO Shipment Splitting - change to the expected date for an existing delivery is not sending an update ReceiptAdvice to the WMS
<h1>Build 1.0.104.2</h1>
Release date 13/02/2020
* [New] 1300 In Full delivery - Supplier - ER18809
* [New] 1548 UI functionality of splitting PO shipments
* [New] 1557 See Support ticket #20027 - improve Error handling when a PO is raised for materials with differing currencies.
    Prevent adding items to a PO if their currency doesn't match with the items already on the PO
* [New] 1567 Create UI for "No Fly" item status Yes/No in stockitem screen
    #1305 / #18801 Added No-Fly flag to the StockItem grid
* [New] 1597 Station Count - Breakages
* [New] 1662 M/T changes required for vendor shipment splitting
* [New] 1740 Restrict access to the galley canvas if a user doesn't have SSO grants.
* [New] 1752 City Pairs & Markets - Improve "Delete" functionality
* [New] 1753 All dashboard charts require the date value displayed in the X-Axis to be in "MMM-YY" date format
* [New] 1765 Improve filters and order by when displaying aircraft stowages from the flight schedule page
* [New] er19939 PO Splitting (PO Vendor Deliveries)
<br/>
* [Bugfix] 1737 Requisition Excess Ordering Thresholds - duplicate logs can be created quite easily
    Avoid having duplicate entries in the RequisitionDetailExcessOrderQtyLog with the addition of a new "Counter" field - attempting to approve the same excessive figures multiple times should now increase the counter field rather than insert a new (duplicate) record.
* [Bugfix] 1757 Item Demand Forecast - External Forecast Data -> Unable to delete row
* [Bugfix] 1762 Support Tickets - Watch List is showing too many records in the new portal.
* [Bugfix] 1772 Several Grids - not possible navigate across different pages of the grids
* [Bugfix] SR21531 - Contract Items report is not loading - fixed
* [Bugfix] sr21633 Changed sort order on Stock Unit DDL
* [Bugfix] sr21655 Fixed issue causing users to be unable to save changes to Station Count Categories (already patched)
<br/>
<h1>Build 1.0.103.6</h1>
Release date 29/01/2020
* [Bugfix] 1769 Error preventing access to Aircraft Layout Editor
<br/>
<h1>Build 1.0.103.5</h1>
Release date 27/01/2020
* [New] 1570 Stock Item - Item Catalog Portal
* [New] 1597 Station Count - Breakages
* [New] 1658 Porting issue - Purchase Order Contract content in the MVC Portal does not allow you to view a break-down of POCntrctDet_ConsQty; this is available in the legacy portal though
* [New] 1669 Allow access to General reports: Issue details, PO lines, contracted Items and Items on PO contracts to Supplier manager role
* [New] 1688 Provide functionality to add/edit and delete module content if SkyLoad is not enabled
* [New] 1741 Enhancements to the SSO Security token functionality.
* [New] 21353 - Make PO Master Contract PDF Generation and Existing documents listing available in Show page, Index Grid (Existing Docs grid on index page)
<br/>
* [Bugfix] 1650 Support Request #20625 - MVC UI is showing misleading information when viewing the break-down of Expected Receipts where the receipt is for a Partially Received PO.
* [Bugfix] 1686 Position and move ability of picture window on canvasses is a problem
* [Bugfix] 1727 When approving a req in MVCRSTEST you get a message ‘true’ pop up after it tells you orders will be create etc.
* [Bugfix] 1738 Unfriendly error is displayed when validation fails for new Aircraft Module creation
* [Bugfix] 20065 - Added SupplierManager roles to the authorised roles for PurchaseOrderDetailSummary_Read (listing of PO Details)
* [Bugfix] 20089 - Edit button hidden for non-SLX users on grids presented on: ItemWarehouse index, ItemPacks index, TransportChains index, and Count Category index views, show button also added which is always available and presents the same data in read-only form.
* [Bugfix] 20105 - Added a help / explain button on the Shipments grid on EditRestrictedPurchaseOrder view
* [Bugfix] 20467 - Fixed DDL population when creating a new PO (delivering to warehouse or warehouse via whse transfer)
* [Bugfix] 21393 - Fix POMC Lookup in PO Creation. (also tested and patched out to 1.0.102.x)
* [Bugfix] 21549 (add any New Airline Supplier records)
<br/>
<h1>Build 1.0.102.6</h1>
Release date 21/01/2020
* [New] 1567 Create UI for "No Fly" item status Yes/No in stockitem screen
* [New] 1598 Airline Supplier - additional contacts
* [New] 1643 Add new field to Contracted items general report
* [New] 1688 Provide functionality to add/edit and delete module content if SkyLoad is not enabled
* [New] 1706 Warehouse - Adjustments screen
* [New] 1710 Implement External order reference for SAP Requisitions
* [New] 1715 Stock count - Migrate columns 'Cancelled' and 'Complete' in Stock Count overview
<br/>
* [Bugfix] 1675 Problem with functionality to delete a stockitem (fix deletion logic)
* [Bugfix] 1701 Purchase Invoicing > All POs Grid shows incorrect value for 'Direct Delivery'.
* [Bugfix] 1727 When approving a requisition, you get a message ‘true’ pop up after it tells you orders will be create etc.
* [Bugfix] 20719 - StockItem edits - ensure Item Cost, Weight, and Item Pack Weight allow up to 6 decimal points precision.
* [Bugfix] 21275 - Fixed grid sorting bug on Stock Item Index grid
* [Bugfix] 21239 - Fixed several Back Order edit issues
* [Bugfix] 21287 - PO Lines report updated to initially sort on PO Creation Date descending.
* [Bugfix] 21393 - Fixed the Contract Reference lookup for PO Edits.
<br/>
<h1>Build 1.0.101.2</h1>
Release date 08/01/2020
* [New] 1568 StationItem - Select Station Items to be Updated using latest station defaults
* [New] 1569 Stock Item - Stock Item Replacements
* [New] 1638 StationItems - migration of station items page
* [New] 1656 Drill down on Open PO status dashboard chart
* [New] 1664 RMA - Ability to amend RMA ETA after RMA has been approved.
* [New] 1668 Bespoke MRP Batch Report amendment
* [New] 1680 Need the ability to create module details for a Miscellaneous Container Group
<br/>
* [Bugfix] 1532 Prevent ability to add disabled users to a ticket's distribution list.
* [Bugfix] 1650 Support Request #20625 - Portal is showing misleading information when viewing the break-down of Expected Receipts where the receipt is for a Partially Received PO.
* [Bugfix] 1647 Support Ticket #20635 - When adding a new Airline Supplier in the portal needs to auto-trim the Supplier Account Number.
* [Bugfix] 1674 Fixed several bugs in the Substitutions module.
* [Bugfix] 1677 Improved error handling in Item Pack maintenance pages.
* [Bugfix] 1685 Stock item editing. Exception if Pack levels have the same "Pack Description" value.
* [Bugfix] 1687 Default Image not showing in the Modules page.
* [Bugfix] 1713 Unable to edit provisional RMAs in v1.0.101.0
* [Bugfix] SR17939 - Disabled selection mode on Station Count items grid and adjusted control heights to hopefully improve the cell-selection issue (Changeset 33196)
* [Bugfix] SR20593 - KPI requisition detail - fixed filter behaviour for the 'Substitute' column.
* [Bugfix] SR21103 - Requisition editing (pre-approval and approval), Save and Continue now retains the Item Grid page number that the user was on.
* [Bugfix] SR21111 - SSIM Index Grid initial sort order now by created date descending.
<br/>
<h1>Build 1.0.100.3</h1>
Release date 03/01/2020
* [New] 1451 Support middle-tier upload function In Progress (Tidied margins and added upload button to change approval page)
* [New] 1496 Validation of supplier contact email
* [New] 1558 Waste Trolley shouldn't be chilled
* [New] 1588 MRP - Planner Orders - Additional columns for "Soft POs"
* [New] 1595 KPI receipt - station receipt report with additional columns
* [New] 1596 KPI report - IWT Details report
* [New] 1607 Supplier Performance Dashboard - Supplier On Time Commitment chart
* [New] 1610 Supplier Performance Dashboard - Dashboard Open POs Status chart
* [New] 1618 Validation needed when changing an Organization Type
* [New] 1648 Add Cost Centre Category Code to GL Account Category pages
* [New] 1649 Small changes and tidy up to GL Cost Centre category pages
* [New] 1652 Implemented ability to maintain Alternative Aircraft Codes
* [New] 1655 Better handled violations of Unique Index: IDX_RequisitionDetail_ReqHdr_ID__StkItem_ID__ReqDate__ExtLineRef, currently an unfriendly error message is presented to the user, which causes confusion
* [New] 1663 Implemented ability to resolve an SSIM that was burst with errors.
* [New] 1667 Release banner should come up at Home Screen and as a banner T-10 minutes
* [New] 20669 Quantity fields on Station Counts now only validated on submission (so users can save as they go)
* [New] 20923 Saving a station will now only validate Default Loading (and it's relation to other active caterer stations) if the user actually changed the value
<br/>
* [Bugifx] 1549 Portal doesn't display extended characters correctly on drop down lists
* [Bugfix] 1632 Non default pack quantity not enforced when adding items to back orders
* [Bugfix] 1633 AircraftStowagePositionList Report Error
* [Bugfix] 1654 Filtering on Aircraft Type page is not working as it should
<br/>
<h1>Build 1.0.99.4</h1>
Release date 18/12/2019
* [Bugfix] 1642 SkyLog tickets - responsible user needs to be included in the e-mail list
* [Bugfix] 1676 StockitemForecastLoadfactor decimal precision not being displayed correctly
* [Bugfix] 1678 Deletion of an AircraftModule logic when to activate the delete icon is wrong
<br/>
<h1>Build 1.0.99.2</h1>
Release date 12/12/2019
* [New] 1442 Display days coverage in MRP Daily figure
* [New] 1451 Support m/t upload function
* [New] 1527 When dragging a stowage position to the Galley canvas where is the default unit of Dims coming from? Also Min check needs explaining in terms of the unit
* [New] 1550 Implemented ability to review forecasts
* [New] 1601 Tidy up Aircraft Tail Number pages
* [New] 1605 Dashboard - Drill data implemented for the Late Open PO shipments chart.
* [New] 1609 Planned Orders - UI - General reports to display data from MRPSoftOrderDetail
* [New] 1615 Make SLX portal version identifier clickable - redirecting you to release history on the wiki
* [New] 1617 Add Organization Type to Airline Supplier pages
* [New] 1629 ER 20479 - Add External Line Number column to the PO lines KPI report
<br/>
* [Bugfix] 1446 SkylogistiX Wiki - Fix to improve the performance of the portal (reducing database reads).
* [Bugfix] 20515 - Improved error handling for bespoke reports
* [Bugfix] 20637 - Improved performance for loading items to add to Requisition
* [Bugfix] 1148 Add time stamp to error pop-ups
* [Bugfix] 1375 Enhance filters across all pages / grids = trimming numeric filter searches
* [Bugfix] 1470 Support Ticket #19505 - Unable to export Bespoke Reports to MS-Excel
* [Bugfix] 1639 SkyLog tickets - line breaks in the Detailed Description of the Problem
* [Bugfix] 1642 SkyLog tickets - responsible user needs to be included in the e-mail list
<br/>
<h1>Build 1.0.98.3</h1>
Release date 06/12/2019
* [New] 1218 Add a delete Icon to the StockItem/Index page to allow stock items to be deleted
* [New] 1492 Substitution Module / Unplanned Substitutions migrated to new portal
* [New] 1500 PO Lines data grid - files downloaded into csv/xls should have a date format adjusted to dd/mm/yyyy
* [New] 1511 ItemSupplier index grid updated to include new columns
* [New] 1580 Station Performance dashboard - Add "under review" and "recount" statuses to "Station Stock Count" chart.
* [New] 1593 Planned orders - UI - Add field forecasting period to Item supplier - Warehouse grid
* [New] 1622 Station KPI - Station late orders table need mode of transport
* [New] 1621 New Dashboard Group: 'Supplier Performance'
* [New] 1604 'Supplier Performance' Dashboard chart - Late Open PO shipments
<br/>
* [Bugfix] 1611 Consumption chart not rendering categories in the correct order when when filters are applied.
* [Bugfix] 1612 Station KPI dashboard - Station count chart refresh
* [Bugfix] 1470 Support Ticket #19505 - Unable to export Bespoke Reports to MS-Excel
* [Bugfix] 1562 Aircraft Config - Creation Date Failure
* [Bugfix] 1608 Module Copy & Delete Issues
* [Bugfix] 1619 "sortablejs" node modules call exception when canvas loading
* [Bugfix] 19133 - Sort order on Requisition Approval grid changes dependent on whether or not the airline is using Loading Groups.
* [Bugfix] 20289 - StationCountCategory Edit page improvements - fields for IncludeAllSPL and UpdateSPL are now read-only with appropriate values if Approval is not required.
* [Bugfix] 20375 - Changed option label for "Climate Requirements" on adding a stockitem
* [Bugfix] 20379 - Fixed incorrect field binding on Stock Allocated to Warehouse Transfers grid (outbound)
* [Bugfix] 20437 - Fixed method used to retrieve the blank count file - now returns the latest if there's multiple
* [Bugfix] 20465 - Export button added to non-SAP-centric BackOrder items grid
* [Bugfix] 20487 - Added Rule Sequence field to Provisioning Rules grid
* [Bugfix] 20489 - Changed query for Expected Warehouse Transfers (Stock Levels) grid so that it's based on WarehouseTransferReceipt rather than WarehouseTransferDetail.
* [Bugfix] 20515 - Fixed error handling on Bespoke Reports.
<br/>
<h1>Build 1.0.97.0</h1>
Release date 02/12/2019
* [New] 1297 - Dashboard Chart - Shipments by Mode of Transport and On Time % - ER16865
* [New] 1446 - SkylogistiX Wiki
* [New] 1492 - (minor errors) Substitution Module / unplanned substitutions website
* [New] 1520 - Port across functionality to allow the User Station Access table to be managed through the new portal
* [New] 1566 - When creating a new Station Par Level entry (Station Item record), we should check to see if the "new" material has been associated with the station previously
* [New] 1585 - Make the 'Network On Time Receipts' chart wider by default, and allow to be re-sizeable.
<br/>
* [Bugfix] 1499 - StationCount Detail 'Last Count Date' not being populated in some cases (19641)
* [Bugfix] 1613 - SR20423 - Build v1.0.96.0 has introduced a bug - problems editing ItemWarehouse records from page: /StockItem/Edit
* [Bugfix] 1623 - SR20433 - Back Order processing - it is not possible to ship from an alternate warehouse
* [Bugfix] 1626 - Unable to submit Requisitions in 1.0.97.x
* [Bugfix] 1631 - MRP Supply Parameters - Item Warehouse edit bug
<br/><h1>Build 1.0.96.0</h1>
Release date 20/11/2019
* [New] 1520 - Port across functionality to allow User Station Access to be managed in the new portal
* [New] 1555 - Added Planner Name column to the Stock Levels index grid
* [New] 20055 - MOQ and EOQ fields on Item Warehouse editor template
* [New] 1519 - Warehouse Inventory Valuations Report (KPI)
<br/>
* [Bugfix] 1563 - Duplicate Container Item Type
* [Bugfix] 1558 - Waste Trolley should not be chilled
* [Bugfix] 20133 - Transit Only field bug on editing Warehouse
* [Bugfix] 1453 - UI allows an MRP line to be submitted even if the Qty control is not showing a figure/value
* [Bugfix] 20171 - Problems adding Stock Item Packs

Release:History

2020-05-20T11:04:23Z

Arunas.milasius:

<h1>Build 1.0.116.5</h1>
released to RS PROD pending (original released date 13/05/2020 postponed)
* [Bugfix] 2002 Support Project maintenance - missing some basic validations
* [Bugfix] 2011 SkyTrack related dashboards no longer working - SR23349
* [Bugfix] 2028 UI REQ Approval Page needs to perform a check to ensure that a Mode of Transport is selected/chosen prior to displaying the Order Qty Excess modal dialog - SR15526
* [Bugfix] 15562 - Open up SSIM access to Skylog product users
* [Bugfix] 15590 - Implemented ability to store StationCountDetail records on the ReviewDetail view
* [Bugfix] 23283 - Fix - Abort not working for Provisional POs.
* [Bugfix] 23435 - Fix - Not able to add attachments to a support ticket.
<br/>
* [New] 1734 Align how the system interprets the day when requisition is created - ER20933
* [New] 1956 Warehouse Customer Services to be able to raise IWTs - ER15369
* [New] 2012 Station Receipts Report missing Station Code in additiona to OrgSite (United Airlines) - ER23315
* [New] 2017 Provide UI option to Opt out from Enhanced requistion approval page delivered under - ER18383
* [New] 2018 General Search function for Stock Item page
* [New] 2019 General Search Function for Critical Items page
* [New] 2023 General Search Function for Support / Enhancement TIcket page
* [New] 2025 General Reports - IWT Details page enhanced download function
* [New] 2027 NWA details - Enhanced download
* [New] 23355 - Dashboard Configuration added to the main menu. NOTE: This is a WIP, and the grid is currently display-only. No editing.
<br/>

<h1>Build 1.0.115.5</h1>
released to RS PROD on 07/05/2020
* [Bugfix] 23655 - Unable to partially commit to a PO on RS Alpha
<br/>
<h1>Build 1.0.115.4</h1>
released to RS PROD on 28/04/2020
<br/>
released to LSY PROD on 05/05/2020
* [Bugfix] 23443 - Unable to Edit MRP
* [Bugfix] 23475 - Unable to receipt confirm
<br/>
<h1>Build 1.0.115.2</h1>
released to RS PROD on 22/04/2020
* [New] 1946 Improvements to the text and label handling on the trolley editor
* [New] 1971 Warehouse Stock Levels - All Transactions
* [New] 1994 See ticket #22991 - seems that the Provision Loading Errors page has been missed in the porting exercise
* [New] 22407 Re-instates a column that was erroneously removed from NetworkAnalysis\WarehouseDemandIndex.
<br/>
* [Bugfix] 1993 PurchaseInvoice/AwaitingApproval pages - Grid "drill-down" errors
* [Bugfix] 2002 Support Project maintenance - missing some basic validations
* [Bugfix] 15540 - Fixed Station Count Review page - the grid column 'Expected Count Qty' was taking value from the wrong column in the database view.
* [Bugfix] 23435 - error on adding attachement to support ticket.
<br/>
<h1>Build 1.0.114.1</h1>
released to RS PROD on 22/04/2020
* [New] 1904 Logging user on the Support tickets data grid - list options in alphabetical sequence please
* [New] 1931 Add Shipment tab to Inside RMA page 22863
* [New] 1957 Port maintenance pages
* [New] 1965 Request to port from legacy portal screen allowing to extend users access ER19109
* [New] 1982 See support ticket #23131 - it is not possible to endorse ERs in the MVC portal
* [New] 23075 - Added Ext. Ticket No. to support tickets.
* [New] 23227 - Added search panel to report grids.
<br/>
* [Bugfix] 21715 - Added new message for new db constraint CON_IssueHeader_Despatched.
* [Bugfix] 21835 - Ensure the Prov_POCntrctHdr_ID is set when auto-matching and finding a POMC match (for statuses up to and including Awaiting Approval).
* [Bugfix] 23139 - Requisition Approval - when only one Preferred Transport Mode record exists for the station, default to it and make the dropdown list read only.
* [Bugfix] 23163 - Changed filter configurations on Station Count Details KPI report to improve performance.
* [Bugfix] 23189 (Fix first user to be assigned to ticket wasn't added to distribution list)
<br/>
<h1>Build 1.0.113.4</h1>
released to RS PROD on 15/04/2020
* [New] 1780 Add total value to bar charts [primary charts]
* [New] 1781 Add total value to bar charts [secondary chart]
* [New] 1893 Provide Global updating capability for ItemLoss factor
* [New] 1932 Add a Shipment tab in RMA quick View 22863
* [New] 1952 add user firstName and lastName to header of skylogportal ER14637
* [New] 1961 Offer a button to make a cascading change of the Method of Transport at REQ Approval step ER16883
* [New] 1968 General Report - Station ITem KPI reports
* [New] 1969 General Reports - RMA Details
* [New] 1986 Born out of support ticket 23133, the authentication server should detect the browser being used by the end-user and if its the loathed IE, tell them to go use a better browser or suffer the consequences....
* [New] 22145 - Make WorkItem ID a filterable column in the System Errors index grid.
* [New] 22833 - Updated View_FlightLoadedItems to join to NetWorkAnalHeader and filter to return active forecasts only.
* [New] 23129 - PurchaseOrder/Show fixed to show Ultimate Warehouse destination (when applicable)
* [New] 23133 - removed client script that is not supported in IE11.
<br/>
* [Bugfix] 1973 Support Ticket #23077 - filtering by txn type is not possible.
<br/>
<h1>Build 1.0.112.4</h1>
released to RS PROD on 08/04/2020
* [New] 1767 ItemDemandForecast - Migrate View NWA Details
* [New] 1808 Support - Migrate Projects window
* [New] 1856 General Reports - Requisition Details (Performance improvements when filtering on that report)
* [New] 1903 Modify all CityPair related pages to incorporate 2 new fields (Mileage & KM's)
* [New] 1915 Urgent improvements required for the REQ approve and alter page in the MVC portal (see support ticket #22793) for details
* [New] 1916 Create pages to view the details in the new AircraftRouting table ()Changeset 34097: Changed tooltip position (removed blink effect)
* [New] 1921 Extend Airline Analytics User Profile - Supply Chain Participants/Stations
* [New] 1922 Extend Airline Analytics User Profile - StockItem/StockItem
* [New] 1923 Extend Airline Analytics User Profile - StockItem/ItemPack
* [New] 1924 Extend Airline Analytics User Profile - StockItem/ItemCatalogue
* [New] 1925 Extend Airline Analytics User Profile - StockItem/ItemSupplier
* [New] 1926 Extend Airline Analytics User Profile - StockItem/ItemWarehouse
* [New] 1937 Requisitions - tick boxes in Requisition Header pager with function to delete premanual submits
* [New] 1940 General Report - StationCountDetails report wired up for Enhanced Exporting
* [New] 1941 Add Children, Infant, Staff PAX details and diverted port detail to PAX pages developed under VSO task 1795
* [New] 1942 Add PNR code to the Special Meals window developed under VSO Task 1795
* [New] 22909 - Ensure column resizer is rendered for MRP/EditAlert (MRP Daily Figures grid)
<br/>
* [Bugfix] 1894 Suspected problem with automatic renewal of bearer token
* [Bugfix] 1943 Typo in the web.config for the Skylog MVC portal, Key = AuthenicatedRedirect
* [Bugfix] 22527 - Cosmetic issue on numerical columns when exporting to PDF
* [Bugfix] 22963 - Fix 'Awaiting Approval' Index grid - Status column is no longer hidden by default.
* [Bugfix] 22965 - Support notifications closing support related editor dialogues
* [Bugfix] 23037 - Item unit price rounding fixes for PO Contracts
<br/>
<h1>Build 1.0.111.5</h1>
released to RS PROD on 06/04/2020
* [Bugfix] 23197 - RMA Ship Confirmation - unable to save and continue Ship Qtys (gets set back to zero).
<br/>
<h1>Build 1.0.111.4</h1>
released on 01/04/2020
* [New] 1572 Porting task, (ER16499) - bring across back ordering for SAPCentric clients in to the MVC portal
* [New] 1801 Ensure the shipment linked to a Delivery change is updated with the new Expected date and inform the WMS of a date change via Receipt Advice message
* [New] 1803 UI to support two new fields that have been added to the AircraftConfiguration table - see ER #21965
* [New] 1855 Manufacturer details in Skylog - (ER20603)
* [New] 1879 Provide pages to maintain (Add or delete) Hub Airports for a particular airline
* [New] 1900 UI for planned substitution by region - (ER22245)
* [New] 1907 Create pages to view data in the BA BOM Staging tables via the portal
* [New] 1916 Create pages to view the details in the new AircraftRouting table
* [New] 1936 Bugs fixing & improvements
* [New] 22941 - Revise the enhanced requisitioning approval page to make it more flexible for operations other than Lufthansa
<br/>
* [Bugfix] 1947 (sr22999) - Planned Orders Report, when the Export to Excel button is clicked, nothing happens.
* [Bugfix] 1948 SAP Backorders functionality is ignoring Airline access rights - allowing users to view and edit requisition backorders for any airline.
* [Bugfix] 22073 - Changed the default filter operator globally for string values in Kendo grids
* [Bugfix] 22697 - Added Pick Instructions/Priority for provisional requisitions
* [Bugfix] 22887 - Fixed invalid Id reference in view.
* [Bugfix] 22925 - Removed SeqNo from POVendorDeliveryHeaderEdit viewModel
<br/>
<h1>Build 1.0.110.8</h1>
released on 26/03/2020
* [New] 22941 Revise the enhanced requisitioning approval page to make it more flexible for operations other than Lufthansa
* [Bugfix] 1947 Planned Orders Report is not downloading.
<br/>
<h1>Build 1.0.110.6</h1>
released on 19/03/2020
* [Bugfix] 1945 Enhanced report download job is not applying filters 22953
* [Bugfix] 22925 Unable to create additional vendor deliveries as a supplier for fully committed
<br/>
<h1>Build 1.0.110.3</h1>
released on 18/03/2020
* [New] 1486 Add a "waste Bin" feature - items on the aircraft layout galley canvass can be dragged to the waste bin to avoid using the delete button on users keyboard (ER 19673)
* [New] 1600 Shipments by mode of transport and on time % (drill tables) ER16865
* [New] 1689 Provide Station Executive Role Access to Station Performance dashboard
* [New] 1791 Save customized dashboard
* [New] 1795 Develop pages to display Actual PAX and Special meal quantities and request history
* [New] 1840 NWA Demand by Warehouse report 21407
* [New] 1874 General reports - Network inventory valuation
* [New] 1879 Provide pages to maintain (Add or delete) Hub Airports for a particular airline
* [New] 1889 ER22407 - Add Forecast ID to NWAD by warehouse screen
* [New] 1891 22225 - Enable Supplier relationship manager role to access to StockItem/ItemsIndex
* [New] 1895 Add Network Analysis Origin column to the View NWA pages
* [New] 1896 Reposition warehouse Inventory reporting to general reports menu
* [New] 1903 Modify all CityPair related pages to incorporate 2 new fields (Mileage & KM's)
* [New] 1905 Modify ProvioningRule pages incorporate selection by Distance of flight (Mileage) SCRIPT TO VSO!
* [New] 1913 Offer an "Add" (+) button to allow SPMs to tack-on additional materials to a REQ which is in status: Awaiting Approval (See support ticket #22273)
* [New] 1917 StockItem download contains skylog code over desc columns
<br/>
* [Bugfix] 22301 - Allowed requisition requested/approved qty > 99999 to be entered in the portal pages. Requires thorough requisition testing.
* [Bugfix] 22331 - Overcommitment warning for vendors creating delivery schedule
* [Bugfix] 22535 - Fixed inability to reassign ER's
* [Bugfix] 22793 - Added Req Status to Awaiting Approval index grid
* [Bugfix] 22805 - Dashboard chart - submitted counts. Fixed the monthly category display to show the correct month.
* [Bugfix] 22857 - Fixed infinite loop between client/authentication server for authenticated users accessing un-authorized actions.
<br/>
<h1>Build 1.0.109.3</h1>
released on 18/03/2020
* [New] 1251 Portal migration - Enhanced Requisition Approval page ##completely tested?##
* [New] 1830 Amend the Requisition Pop as per ticket request ER21997
* [New] 1835 Add alert when excel is uploaded for station stock count 20177
<br/>
* [Bugfix] 1882 Various reports of data download problems in the MVC portal, timing out if record set is more than a few thousand records (approx 10K)
* [Bugfix] 22157 - Enabled exporting all pages
* [Bugfix] 22331 - Show a warning to vendors if they try to submit a delivery schedule which over-commits to the order
* [Bugfix] 22535 - Fixed inability to reassign ER's ####close ticket on release.
* [Bugfix] 22561 - Fixes to REQ Excess Qty popup - now rounding values before sending them off to the DB
* [Bugfix] 22665 - Station Submitted Counts dashboard chart
* [Bugfix] 22887 - Fixed invalid Id reference in view.
<br/>
<h1>Build 1.0.108.2</h1>
released on 10/03/2020
* [Bugfix] 22793 - Important - /Requisition/AwaitingApproval page in the new portal doesn't show the REQ Header Status of the REQ
<br/>
<h1>Build 1.0.108.1</h1>
released on 06/03/2020
* [Bugfix] 22665 - Station Submitted Counts dashboard chart fix.
<br/>
<h1>Build 1.0.108.0</h1>
released on 02/03/2020
* [New] 1868 Improve SSIM error handling so you can set multiple records for re-run reg globally or by error nature rather than individually
* [New] 1870 Add a General Report to show Aircraft Provisioning Code Details
* [New] 1871 Add a General report to provide details of Module Contents
* [New] 1872 Add ability to maintain and view Module User Notes outside of the SkyLoad Canvases
* [New] 1873 Add a page to allow forecasting attributes to be viewed through portal
* [New] 1875 Add a page to show details in the FlightLink table
* [New] 1877 Add Exchange Rule field to Module detail Grid on view Provisioning pages
* [New] 1878 If the detail of a module is an item then disable the detail arrow to display module content as this only make sense for a module and not an item.
<br/>
* [Bugfix] 1883 Cannot read property 'weightUnit' or null
* [Bugfix] 22523 - Allow monthly negative financial consumption to display in chart.

<h1>Build 1.0.107.0</h1>
released on 02/03/2020
* [New] 1683 Adjust Module related View, Creation and Edit to accommodate new field ready for use and Share in Menu Plan
* [New] 1730 Requisitions - Migrate copy Template button
* [New] 1756 Ability to create records in AircraftContainerStowage (Stowage Rules)
* [New] 1759 Restrict SkyLoad only Aircraft related pages & menus to users with SkyLoad licenced
* [New] 1845 Station Stock Count chart sorting
* [New] 1857 Forecast Changes Approval page row upload date to be added
* [New] 1866 Restructure General reports menu in preparation for a lot more reports
* [New] 1869 Remove the Upload and Offload Offset (days) from Provision Loading Pages
<br/>
* [Bugfix] 1686 Position and move ability of picture window on canvasses is a problem (improve functionality)
* [Bugfix] 1849 Airline selector doesn't work after loading stored filters (multipage problem)
* [Bugfix] 22287 - Users with no restrictions on their ticket access should now be able to see ALL tickets.
    (No ticket) - Station Count Details report improved so that it automatically filters out data for stations the user doesn't have access to
<br/>
<h1>Build 1.0.106.3</h1>
Release date 26/02/2020
* [New] 1541 StationItem - Automatic Requisition Items
* [New] 1731 Purchase Order - PO Notes page
* [New] 1750 In full delivery - Supplier - ER18809 - [Drill down]
* [New] 1768 StockItem - Item Supplier Mapping
* [New] 1779 Add ability to download data in excel for All Chart-related data grids.
* [New] 1785 Hide empty Months in dashboards
* [New] 1790 Add button to reset filters
* [New] 1795 Develop pages to display Actual PAX and Special meal quantities and request history
* [New] 1847 Improve error handling for container type editing in the canvas.
* [New] 20095 - Re-added the SLX Dummy Airline's items to StockItem listing grids, and added SLX Dummy Airline as a grid filter option
* [New] 21833 - Internal (SLX Staff) URL links appear in the user account context menu (i.e. profile/support/ log out menu)
<br/>
* [Bugfix] 1788 Drill down chart for Warehouse Valuation needs to be populated
* [Bugfix] 1848 dashboard charts are showing Month+1
* [Bugfix] 22037 - Fixed a null reference error when cancelling a PO's balance from Receipt Confirmation page
* [Bugfix] 22053 - Check user role is authorized to approvde POMCs, at PO/Airline configuration level
* [Bugfix] 22103 - Fixed password reset functionality in AuthServer project (affects files in this project too though, hence the mention)
<br/>
<h1>Build 1.0.105.1</h1>
Release date 18/02/2020
* [Bugfix] 22241 User unable to access the bond station
<br/>
<h1>Build 1.0.105.0</h1>
Release date 13/02/2020
* [New] 1542 Atlas Chiller Icon required for Galley Editor
* [New] 1729 StockItem - pdf button to download Item catalogue list with pictures
* [New] 1736 Count Details Bespoke reports to display number values
* [New] 1756 Ability to create records in AircraftContainerStowage (Stowage Rules)
* [New] 1758 Create portal pages to show Stowage Types and related Container Compatibility
* [New] 1759 Restrict SkyLoad only Aircraft related pages & menus to users with SkyLoad licenced
* [New] 1780 Add total value to bar charts [primary charts]
* [New] 1782 add button to be able to filter bar charts timeline
* [New] 1786 Adjust Legend
* [New] 1787 Add Legend to Warehouse Valuation Chart
* [New] 1792 add country to station performance filter table
<br/>
* [Bugfix] 1800 PO Shipment Splitting - change to the expected date for an existing delivery is not sending an update ReceiptAdvice to the WMS
<h1>Build 1.0.104.2</h1>
Release date 13/02/2020
* [New] 1300 In Full delivery - Supplier - ER18809
* [New] 1548 UI functionality of splitting PO shipments
* [New] 1557 See Support ticket #20027 - improve Error handling when a PO is raised for materials with differing currencies.
    Prevent adding items to a PO if their currency doesn't match with the items already on the PO
* [New] 1567 Create UI for "No Fly" item status Yes/No in stockitem screen
    #1305 / #18801 Added No-Fly flag to the StockItem grid
* [New] 1597 Station Count - Breakages
* [New] 1662 M/T changes required for vendor shipment splitting
* [New] 1740 Restrict access to the galley canvas if a user doesn't have SSO grants.
* [New] 1752 City Pairs & Markets - Improve "Delete" functionality
* [New] 1753 All dashboard charts require the date value displayed in the X-Axis to be in "MMM-YY" date format
* [New] 1765 Improve filters and order by when displaying aircraft stowages from the flight schedule page
* [New] er19939 PO Splitting (PO Vendor Deliveries)
<br/>
* [Bugfix] 1737 Requisition Excess Ordering Thresholds - duplicate logs can be created quite easily
    Avoid having duplicate entries in the RequisitionDetailExcessOrderQtyLog with the addition of a new "Counter" field - attempting to approve the same excessive figures multiple times should now increase the counter field rather than insert a new (duplicate) record.
* [Bugfix] 1757 Item Demand Forecast - External Forecast Data -> Unable to delete row
* [Bugfix] 1762 Support Tickets - Watch List is showing too many records in the new portal.
* [Bugfix] 1772 Several Grids - not possible navigate across different pages of the grids
* [Bugfix] SR21531 - Contract Items report is not loading - fixed
* [Bugfix] sr21633 Changed sort order on Stock Unit DDL
* [Bugfix] sr21655 Fixed issue causing users to be unable to save changes to Station Count Categories (already patched)
<br/>
<h1>Build 1.0.103.6</h1>
Release date 29/01/2020
* [Bugfix] 1769 Error preventing access to Aircraft Layout Editor
<br/>
<h1>Build 1.0.103.5</h1>
Release date 27/01/2020
* [New] 1570 Stock Item - Item Catalog Portal
* [New] 1597 Station Count - Breakages
* [New] 1658 Porting issue - Purchase Order Contract content in the MVC Portal does not allow you to view a break-down of POCntrctDet_ConsQty; this is available in the legacy portal though
* [New] 1669 Allow access to General reports: Issue details, PO lines, contracted Items and Items on PO contracts to Supplier manager role
* [New] 1688 Provide functionality to add/edit and delete module content if SkyLoad is not enabled
* [New] 1741 Enhancements to the SSO Security token functionality.
* [New] 21353 - Make PO Master Contract PDF Generation and Existing documents listing available in Show page, Index Grid (Existing Docs grid on index page)
<br/>
* [Bugfix] 1650 Support Request #20625 - MVC UI is showing misleading information when viewing the break-down of Expected Receipts where the receipt is for a Partially Received PO.
* [Bugfix] 1686 Position and move ability of picture window on canvasses is a problem
* [Bugfix] 1727 When approving a req in MVCRSTEST you get a message ‘true’ pop up after it tells you orders will be create etc.
* [Bugfix] 1738 Unfriendly error is displayed when validation fails for new Aircraft Module creation
* [Bugfix] 20065 - Added SupplierManager roles to the authorised roles for PurchaseOrderDetailSummary_Read (listing of PO Details)
* [Bugfix] 20089 - Edit button hidden for non-SLX users on grids presented on: ItemWarehouse index, ItemPacks index, TransportChains index, and Count Category index views, show button also added which is always available and presents the same data in read-only form.
* [Bugfix] 20105 - Added a help / explain button on the Shipments grid on EditRestrictedPurchaseOrder view
* [Bugfix] 20467 - Fixed DDL population when creating a new PO (delivering to warehouse or warehouse via whse transfer)
* [Bugfix] 21393 - Fix POMC Lookup in PO Creation. (also tested and patched out to 1.0.102.x)
* [Bugfix] 21549 (add any New Airline Supplier records)
<br/>
<h1>Build 1.0.102.6</h1>
Release date 21/01/2020
* [New] 1567 Create UI for "No Fly" item status Yes/No in stockitem screen
* [New] 1598 Airline Supplier - additional contacts
* [New] 1643 Add new field to Contracted items general report
* [New] 1688 Provide functionality to add/edit and delete module content if SkyLoad is not enabled
* [New] 1706 Warehouse - Adjustments screen
* [New] 1710 Implement External order reference for SAP Requisitions
* [New] 1715 Stock count - Migrate columns 'Cancelled' and 'Complete' in Stock Count overview
<br/>
* [Bugfix] 1675 Problem with functionality to delete a stockitem (fix deletion logic)
* [Bugfix] 1701 Purchase Invoicing > All POs Grid shows incorrect value for 'Direct Delivery'.
* [Bugfix] 1727 When approving a requisition, you get a message ‘true’ pop up after it tells you orders will be create etc.
* [Bugfix] 20719 - StockItem edits - ensure Item Cost, Weight, and Item Pack Weight allow up to 6 decimal points precision.
* [Bugfix] 21275 - Fixed grid sorting bug on Stock Item Index grid
* [Bugfix] 21239 - Fixed several Back Order edit issues
* [Bugfix] 21287 - PO Lines report updated to initially sort on PO Creation Date descending.
* [Bugfix] 21393 - Fixed the Contract Reference lookup for PO Edits.
<br/>
<h1>Build 1.0.101.2</h1>
Release date 08/01/2020
* [New] 1568 StationItem - Select Station Items to be Updated using latest station defaults
* [New] 1569 Stock Item - Stock Item Replacements
* [New] 1638 StationItems - migration of station items page
* [New] 1656 Drill down on Open PO status dashboard chart
* [New] 1664 RMA - Ability to amend RMA ETA after RMA has been approved.
* [New] 1668 Bespoke MRP Batch Report amendment
* [New] 1680 Need the ability to create module details for a Miscellaneous Container Group
<br/>
* [Bugfix] 1532 Prevent ability to add disabled users to a ticket's distribution list.
* [Bugfix] 1650 Support Request #20625 - Portal is showing misleading information when viewing the break-down of Expected Receipts where the receipt is for a Partially Received PO.
* [Bugfix] 1647 Support Ticket #20635 - When adding a new Airline Supplier in the portal needs to auto-trim the Supplier Account Number.
* [Bugfix] 1674 Fixed several bugs in the Substitutions module.
* [Bugfix] 1677 Improved error handling in Item Pack maintenance pages.
* [Bugfix] 1685 Stock item editing. Exception if Pack levels have the same "Pack Description" value.
* [Bugfix] 1687 Default Image not showing in the Modules page.
* [Bugfix] 1713 Unable to edit provisional RMAs in v1.0.101.0
* [Bugfix] SR17939 - Disabled selection mode on Station Count items grid and adjusted control heights to hopefully improve the cell-selection issue (Changeset 33196)
* [Bugfix] SR20593 - KPI requisition detail - fixed filter behaviour for the 'Substitute' column.
* [Bugfix] SR21103 - Requisition editing (pre-approval and approval), Save and Continue now retains the Item Grid page number that the user was on.
* [Bugfix] SR21111 - SSIM Index Grid initial sort order now by created date descending.
<br/>
<h1>Build 1.0.100.3</h1>
Release date 03/01/2020
* [New] 1451 Support middle-tier upload function In Progress (Tidied margins and added upload button to change approval page)
* [New] 1496 Validation of supplier contact email
* [New] 1558 Waste Trolley shouldn't be chilled
* [New] 1588 MRP - Planner Orders - Additional columns for "Soft POs"
* [New] 1595 KPI receipt - station receipt report with additional columns
* [New] 1596 KPI report - IWT Details report
* [New] 1607 Supplier Performance Dashboard - Supplier On Time Commitment chart
* [New] 1610 Supplier Performance Dashboard - Dashboard Open POs Status chart
* [New] 1618 Validation needed when changing an Organization Type
* [New] 1648 Add Cost Centre Category Code to GL Account Category pages
* [New] 1649 Small changes and tidy up to GL Cost Centre category pages
* [New] 1652 Implemented ability to maintain Alternative Aircraft Codes
* [New] 1655 Better handled violations of Unique Index: IDX_RequisitionDetail_ReqHdr_ID__StkItem_ID__ReqDate__ExtLineRef, currently an unfriendly error message is presented to the user, which causes confusion
* [New] 1663 Implemented ability to resolve an SSIM that was burst with errors.
* [New] 1667 Release banner should come up at Home Screen and as a banner T-10 minutes
* [New] 20669 Quantity fields on Station Counts now only validated on submission (so users can save as they go)
* [New] 20923 Saving a station will now only validate Default Loading (and it's relation to other active caterer stations) if the user actually changed the value
<br/>
* [Bugifx] 1549 Portal doesn't display extended characters correctly on drop down lists
* [Bugfix] 1632 Non default pack quantity not enforced when adding items to back orders
* [Bugfix] 1633 AircraftStowagePositionList Report Error
* [Bugfix] 1654 Filtering on Aircraft Type page is not working as it should
<br/>
<h1>Build 1.0.99.4</h1>
Release date 18/12/2019
* [Bugfix] 1642 SkyLog tickets - responsible user needs to be included in the e-mail list
* [Bugfix] 1676 StockitemForecastLoadfactor decimal precision not being displayed correctly
* [Bugfix] 1678 Deletion of an AircraftModule logic when to activate the delete icon is wrong
<br/>
<h1>Build 1.0.99.2</h1>
Release date 12/12/2019
* [New] 1442 Display days coverage in MRP Daily figure
* [New] 1451 Support m/t upload function
* [New] 1527 When dragging a stowage position to the Galley canvas where is the default unit of Dims coming from? Also Min check needs explaining in terms of the unit
* [New] 1550 Implemented ability to review forecasts
* [New] 1601 Tidy up Aircraft Tail Number pages
* [New] 1605 Dashboard - Drill data implemented for the Late Open PO shipments chart.
* [New] 1609 Planned Orders - UI - General reports to display data from MRPSoftOrderDetail
* [New] 1615 Make SLX portal version identifier clickable - redirecting you to release history on the wiki
* [New] 1617 Add Organization Type to Airline Supplier pages
* [New] 1629 ER 20479 - Add External Line Number column to the PO lines KPI report
<br/>
* [Bugfix] 1446 SkylogistiX Wiki - Fix to improve the performance of the portal (reducing database reads).
* [Bugfix] 20515 - Improved error handling for bespoke reports
* [Bugfix] 20637 - Improved performance for loading items to add to Requisition
* [Bugfix] 1148 Add time stamp to error pop-ups
* [Bugfix] 1375 Enhance filters across all pages / grids = trimming numeric filter searches
* [Bugfix] 1470 Support Ticket #19505 - Unable to export Bespoke Reports to MS-Excel
* [Bugfix] 1639 SkyLog tickets - line breaks in the Detailed Description of the Problem
* [Bugfix] 1642 SkyLog tickets - responsible user needs to be included in the e-mail list
<br/>
<h1>Build 1.0.98.3</h1>
Release date 06/12/2019
* [New] 1218 Add a delete Icon to the StockItem/Index page to allow stock items to be deleted
* [New] 1492 Substitution Module / Unplanned Substitutions migrated to new portal
* [New] 1500 PO Lines data grid - files downloaded into csv/xls should have a date format adjusted to dd/mm/yyyy
* [New] 1511 ItemSupplier index grid updated to include new columns
* [New] 1580 Station Performance dashboard - Add "under review" and "recount" statuses to "Station Stock Count" chart.
* [New] 1593 Planned orders - UI - Add field forecasting period to Item supplier - Warehouse grid
* [New] 1622 Station KPI - Station late orders table need mode of transport
* [New] 1621 New Dashboard Group: 'Supplier Performance'
* [New] 1604 'Supplier Performance' Dashboard chart - Late Open PO shipments
<br/>
* [Bugfix] 1611 Consumption chart not rendering categories in the correct order when when filters are applied.
* [Bugfix] 1612 Station KPI dashboard - Station count chart refresh
* [Bugfix] 1470 Support Ticket #19505 - Unable to export Bespoke Reports to MS-Excel
* [Bugfix] 1562 Aircraft Config - Creation Date Failure
* [Bugfix] 1608 Module Copy & Delete Issues
* [Bugfix] 1619 "sortablejs" node modules call exception when canvas loading
* [Bugfix] 19133 - Sort order on Requisition Approval grid changes dependent on whether or not the airline is using Loading Groups.
* [Bugfix] 20289 - StationCountCategory Edit page improvements - fields for IncludeAllSPL and UpdateSPL are now read-only with appropriate values if Approval is not required.
* [Bugfix] 20375 - Changed option label for "Climate Requirements" on adding a stockitem
* [Bugfix] 20379 - Fixed incorrect field binding on Stock Allocated to Warehouse Transfers grid (outbound)
* [Bugfix] 20437 - Fixed method used to retrieve the blank count file - now returns the latest if there's multiple
* [Bugfix] 20465 - Export button added to non-SAP-centric BackOrder items grid
* [Bugfix] 20487 - Added Rule Sequence field to Provisioning Rules grid
* [Bugfix] 20489 - Changed query for Expected Warehouse Transfers (Stock Levels) grid so that it's based on WarehouseTransferReceipt rather than WarehouseTransferDetail.
* [Bugfix] 20515 - Fixed error handling on Bespoke Reports.
<br/>
<h1>Build 1.0.97.0</h1>
Release date 02/12/2019
* [New] 1297 - Dashboard Chart - Shipments by Mode of Transport and On Time % - ER16865
* [New] 1446 - SkylogistiX Wiki
* [New] 1492 - (minor errors) Substitution Module / unplanned substitutions website
* [New] 1520 - Port across functionality to allow the User Station Access table to be managed through the new portal
* [New] 1566 - When creating a new Station Par Level entry (Station Item record), we should check to see if the "new" material has been associated with the station previously
* [New] 1585 - Make the 'Network On Time Receipts' chart wider by default, and allow to be re-sizeable.
<br/>
* [Bugfix] 1499 - StationCount Detail 'Last Count Date' not being populated in some cases (19641)
* [Bugfix] 1613 - SR20423 - Build v1.0.96.0 has introduced a bug - problems editing ItemWarehouse records from page: /StockItem/Edit
* [Bugfix] 1623 - SR20433 - Back Order processing - it is not possible to ship from an alternate warehouse
* [Bugfix] 1626 - Unable to submit Requisitions in 1.0.97.x
* [Bugfix] 1631 - MRP Supply Parameters - Item Warehouse edit bug
<br/><h1>Build 1.0.96.0</h1>
Release date 20/11/2019
* [New] 1520 - Port across functionality to allow User Station Access to be managed in the new portal
* [New] 1555 - Added Planner Name column to the Stock Levels index grid
* [New] 20055 - MOQ and EOQ fields on Item Warehouse editor template
* [New] 1519 - Warehouse Inventory Valuations Report (KPI)
<br/>
* [Bugfix] 1563 - Duplicate Container Item Type
* [Bugfix] 1558 - Waste Trolley should not be chilled
* [Bugfix] 20133 - Transit Only field bug on editing Warehouse
* [Bugfix] 1453 - UI allows an MRP line to be submitted even if the Qty control is not showing a figure/value
* [Bugfix] 20171 - Problems adding Stock Item Packs

File:StationReceipt.png

2020-05-20T08:52:15Z

Arunas.milasius:

File:GeneralSearch.png

2020-05-20T08:51:32Z

Arunas.milasius:

Release:History

2020-05-19T07:43:48Z

Arunas.milasius:

<h1>Build 1.0.115.5</h1>
released to RS PROD on 07/05/2020
* [Bugfix] 23655 - Unable to partially commit to a PO on RS Alpha
<br/>
<h1>Build 1.0.115.4</h1>
released to RS PROD on 28/04/2020
<br/>
released to LSY PROD on 05/05/2020
* [Bugfix] 23443 - Unable to Edit MRP
* [Bugfix] 23475 - Unable to receipt confirm
<br/>
<h1>Build 1.0.115.2</h1>
released to RS PROD on 22/04/2020
* [New] 1946 Improvements to the text and label handling on the trolley editor
* [New] 1971 Warehouse Stock Levels - All Transactions
* [New] 1994 See ticket #22991 - seems that the Provision Loading Errors page has been missed in the porting exercise
* [New] 22407 Re-instates a column that was erroneously removed from NetworkAnalysis\WarehouseDemandIndex.
<br/>
* [Bugfix] 1993 PurchaseInvoice/AwaitingApproval pages - Grid "drill-down" errors
* [Bugfix] 2002 Support Project maintenance - missing some basic validations
* [Bugfix] 15540 - Fixed Station Count Review page - the grid column 'Expected Count Qty' was taking value from the wrong column in the database view.
* [Bugfix] 23435 - error on adding attachement to support ticket.
<br/>
<h1>Build 1.0.114.1</h1>
released to RS PROD on 22/04/2020
* [New] 1904 Logging user on the Support tickets data grid - list options in alphabetical sequence please
* [New] 1931 Add Shipment tab to Inside RMA page 22863
* [New] 1957 Port maintenance pages
* [New] 1965 Request to port from legacy portal screen allowing to extend users access ER19109
* [New] 1982 See support ticket #23131 - it is not possible to endorse ERs in the MVC portal
* [New] 23075 - Added Ext. Ticket No. to support tickets.
* [New] 23227 - Added search panel to report grids.
<br/>
* [Bugfix] 21715 - Added new message for new db constraint CON_IssueHeader_Despatched.
* [Bugfix] 21835 - Ensure the Prov_POCntrctHdr_ID is set when auto-matching and finding a POMC match (for statuses up to and including Awaiting Approval).
* [Bugfix] 23139 - Requisition Approval - when only one Preferred Transport Mode record exists for the station, default to it and make the dropdown list read only.
* [Bugfix] 23163 - Changed filter configurations on Station Count Details KPI report to improve performance.
* [Bugfix] 23189 (Fix first user to be assigned to ticket wasn't added to distribution list)
<br/>
<h1>Build 1.0.113.4</h1>
released to RS PROD on 15/04/2020
* [New] 1780 Add total value to bar charts [primary charts]
* [New] 1781 Add total value to bar charts [secondary chart]
* [New] 1893 Provide Global updating capability for ItemLoss factor
* [New] 1932 Add a Shipment tab in RMA quick View 22863
* [New] 1952 add user firstName and lastName to header of skylogportal ER14637
* [New] 1961 Offer a button to make a cascading change of the Method of Transport at REQ Approval step ER16883
* [New] 1968 General Report - Station ITem KPI reports
* [New] 1969 General Reports - RMA Details
* [New] 1986 Born out of support ticket 23133, the authentication server should detect the browser being used by the end-user and if its the loathed IE, tell them to go use a better browser or suffer the consequences....
* [New] 22145 - Make WorkItem ID a filterable column in the System Errors index grid.
* [New] 22833 - Updated View_FlightLoadedItems to join to NetWorkAnalHeader and filter to return active forecasts only.
* [New] 23129 - PurchaseOrder/Show fixed to show Ultimate Warehouse destination (when applicable)
* [New] 23133 - removed client script that is not supported in IE11.
<br/>
* [Bugfix] 1973 Support Ticket #23077 - filtering by txn type is not possible.
<br/>
<h1>Build 1.0.112.4</h1>
released to RS PROD on 08/04/2020
* [New] 1767 ItemDemandForecast - Migrate View NWA Details
* [New] 1808 Support - Migrate Projects window
* [New] 1856 General Reports - Requisition Details (Performance improvements when filtering on that report)
* [New] 1903 Modify all CityPair related pages to incorporate 2 new fields (Mileage & KM's)
* [New] 1915 Urgent improvements required for the REQ approve and alter page in the MVC portal (see support ticket #22793) for details
* [New] 1916 Create pages to view the details in the new AircraftRouting table ()Changeset 34097: Changed tooltip position (removed blink effect)
* [New] 1921 Extend Airline Analytics User Profile - Supply Chain Participants/Stations
* [New] 1922 Extend Airline Analytics User Profile - StockItem/StockItem
* [New] 1923 Extend Airline Analytics User Profile - StockItem/ItemPack
* [New] 1924 Extend Airline Analytics User Profile - StockItem/ItemCatalogue
* [New] 1925 Extend Airline Analytics User Profile - StockItem/ItemSupplier
* [New] 1926 Extend Airline Analytics User Profile - StockItem/ItemWarehouse
* [New] 1937 Requisitions - tick boxes in Requisition Header pager with function to delete premanual submits
* [New] 1940 General Report - StationCountDetails report wired up for Enhanced Exporting
* [New] 1941 Add Children, Infant, Staff PAX details and diverted port detail to PAX pages developed under VSO task 1795
* [New] 1942 Add PNR code to the Special Meals window developed under VSO Task 1795
* [New] 22909 - Ensure column resizer is rendered for MRP/EditAlert (MRP Daily Figures grid)
<br/>
* [Bugfix] 1894 Suspected problem with automatic renewal of bearer token
* [Bugfix] 1943 Typo in the web.config for the Skylog MVC portal, Key = AuthenicatedRedirect
* [Bugfix] 22527 - Cosmetic issue on numerical columns when exporting to PDF
* [Bugfix] 22963 - Fix 'Awaiting Approval' Index grid - Status column is no longer hidden by default.
* [Bugfix] 22965 - Support notifications closing support related editor dialogues
* [Bugfix] 23037 - Item unit price rounding fixes for PO Contracts
<br/>
<h1>Build 1.0.111.5</h1>
released to RS PROD on 06/04/2020
* [Bugfix] 23197 - RMA Ship Confirmation - unable to save and continue Ship Qtys (gets set back to zero).
<br/>
<h1>Build 1.0.111.4</h1>
released on 01/04/2020
* [New] 1572 Porting task, (ER16499) - bring across back ordering for SAPCentric clients in to the MVC portal
* [New] 1801 Ensure the shipment linked to a Delivery change is updated with the new Expected date and inform the WMS of a date change via Receipt Advice message
* [New] 1803 UI to support two new fields that have been added to the AircraftConfiguration table - see ER #21965
* [New] 1855 Manufacturer details in Skylog - (ER20603)
* [New] 1879 Provide pages to maintain (Add or delete) Hub Airports for a particular airline
* [New] 1900 UI for planned substitution by region - (ER22245)
* [New] 1907 Create pages to view data in the BA BOM Staging tables via the portal
* [New] 1916 Create pages to view the details in the new AircraftRouting table
* [New] 1936 Bugs fixing & improvements
* [New] 22941 - Revise the enhanced requisitioning approval page to make it more flexible for operations other than Lufthansa
<br/>
* [Bugfix] 1947 (sr22999) - Planned Orders Report, when the Export to Excel button is clicked, nothing happens.
* [Bugfix] 1948 SAP Backorders functionality is ignoring Airline access rights - allowing users to view and edit requisition backorders for any airline.
* [Bugfix] 22073 - Changed the default filter operator globally for string values in Kendo grids
* [Bugfix] 22697 - Added Pick Instructions/Priority for provisional requisitions
* [Bugfix] 22887 - Fixed invalid Id reference in view.
* [Bugfix] 22925 - Removed SeqNo from POVendorDeliveryHeaderEdit viewModel
<br/>
<h1>Build 1.0.110.8</h1>
released on 26/03/2020
* [New] 22941 Revise the enhanced requisitioning approval page to make it more flexible for operations other than Lufthansa
* [Bugfix] 1947 Planned Orders Report is not downloading.
<br/>
<h1>Build 1.0.110.6</h1>
released on 19/03/2020
* [Bugfix] 1945 Enhanced report download job is not applying filters 22953
* [Bugfix] 22925 Unable to create additional vendor deliveries as a supplier for fully committed
<br/>
<h1>Build 1.0.110.3</h1>
released on 18/03/2020
* [New] 1486 Add a "waste Bin" feature - items on the aircraft layout galley canvass can be dragged to the waste bin to avoid using the delete button on users keyboard (ER 19673)
* [New] 1600 Shipments by mode of transport and on time % (drill tables) ER16865
* [New] 1689 Provide Station Executive Role Access to Station Performance dashboard
* [New] 1791 Save customized dashboard
* [New] 1795 Develop pages to display Actual PAX and Special meal quantities and request history
* [New] 1840 NWA Demand by Warehouse report 21407
* [New] 1874 General reports - Network inventory valuation
* [New] 1879 Provide pages to maintain (Add or delete) Hub Airports for a particular airline
* [New] 1889 ER22407 - Add Forecast ID to NWAD by warehouse screen
* [New] 1891 22225 - Enable Supplier relationship manager role to access to StockItem/ItemsIndex
* [New] 1895 Add Network Analysis Origin column to the View NWA pages
* [New] 1896 Reposition warehouse Inventory reporting to general reports menu
* [New] 1903 Modify all CityPair related pages to incorporate 2 new fields (Mileage & KM's)
* [New] 1905 Modify ProvioningRule pages incorporate selection by Distance of flight (Mileage) SCRIPT TO VSO!
* [New] 1913 Offer an "Add" (+) button to allow SPMs to tack-on additional materials to a REQ which is in status: Awaiting Approval (See support ticket #22273)
* [New] 1917 StockItem download contains skylog code over desc columns
<br/>
* [Bugfix] 22301 - Allowed requisition requested/approved qty > 99999 to be entered in the portal pages. Requires thorough requisition testing.
* [Bugfix] 22331 - Overcommitment warning for vendors creating delivery schedule
* [Bugfix] 22535 - Fixed inability to reassign ER's
* [Bugfix] 22793 - Added Req Status to Awaiting Approval index grid
* [Bugfix] 22805 - Dashboard chart - submitted counts. Fixed the monthly category display to show the correct month.
* [Bugfix] 22857 - Fixed infinite loop between client/authentication server for authenticated users accessing un-authorized actions.
<br/>
<h1>Build 1.0.109.3</h1>
released on 18/03/2020
* [New] 1251 Portal migration - Enhanced Requisition Approval page ##completely tested?##
* [New] 1830 Amend the Requisition Pop as per ticket request ER21997
* [New] 1835 Add alert when excel is uploaded for station stock count 20177
<br/>
* [Bugfix] 1882 Various reports of data download problems in the MVC portal, timing out if record set is more than a few thousand records (approx 10K)
* [Bugfix] 22157 - Enabled exporting all pages
* [Bugfix] 22331 - Show a warning to vendors if they try to submit a delivery schedule which over-commits to the order
* [Bugfix] 22535 - Fixed inability to reassign ER's ####close ticket on release.
* [Bugfix] 22561 - Fixes to REQ Excess Qty popup - now rounding values before sending them off to the DB
* [Bugfix] 22665 - Station Submitted Counts dashboard chart
* [Bugfix] 22887 - Fixed invalid Id reference in view.
<br/>
<h1>Build 1.0.108.2</h1>
released on 10/03/2020
* [Bugfix] 22793 - Important - /Requisition/AwaitingApproval page in the new portal doesn't show the REQ Header Status of the REQ
<br/>
<h1>Build 1.0.108.1</h1>
released on 06/03/2020
* [Bugfix] 22665 - Station Submitted Counts dashboard chart fix.
<br/>
<h1>Build 1.0.108.0</h1>
released on 02/03/2020
* [New] 1868 Improve SSIM error handling so you can set multiple records for re-run reg globally or by error nature rather than individually
* [New] 1870 Add a General Report to show Aircraft Provisioning Code Details
* [New] 1871 Add a General report to provide details of Module Contents
* [New] 1872 Add ability to maintain and view Module User Notes outside of the SkyLoad Canvases
* [New] 1873 Add a page to allow forecasting attributes to be viewed through portal
* [New] 1875 Add a page to show details in the FlightLink table
* [New] 1877 Add Exchange Rule field to Module detail Grid on view Provisioning pages
* [New] 1878 If the detail of a module is an item then disable the detail arrow to display module content as this only make sense for a module and not an item.
<br/>
* [Bugfix] 1883 Cannot read property 'weightUnit' or null
* [Bugfix] 22523 - Allow monthly negative financial consumption to display in chart.

<h1>Build 1.0.107.0</h1>
released on 02/03/2020
* [New] 1683 Adjust Module related View, Creation and Edit to accommodate new field ready for use and Share in Menu Plan
* [New] 1730 Requisitions - Migrate copy Template button
* [New] 1756 Ability to create records in AircraftContainerStowage (Stowage Rules)
* [New] 1759 Restrict SkyLoad only Aircraft related pages & menus to users with SkyLoad licenced
* [New] 1845 Station Stock Count chart sorting
* [New] 1857 Forecast Changes Approval page row upload date to be added
* [New] 1866 Restructure General reports menu in preparation for a lot more reports
* [New] 1869 Remove the Upload and Offload Offset (days) from Provision Loading Pages
<br/>
* [Bugfix] 1686 Position and move ability of picture window on canvasses is a problem (improve functionality)
* [Bugfix] 1849 Airline selector doesn't work after loading stored filters (multipage problem)
* [Bugfix] 22287 - Users with no restrictions on their ticket access should now be able to see ALL tickets.
    (No ticket) - Station Count Details report improved so that it automatically filters out data for stations the user doesn't have access to
<br/>
<h1>Build 1.0.106.3</h1>
Release date 26/02/2020
* [New] 1541 StationItem - Automatic Requisition Items
* [New] 1731 Purchase Order - PO Notes page
* [New] 1750 In full delivery - Supplier - ER18809 - [Drill down]
* [New] 1768 StockItem - Item Supplier Mapping
* [New] 1779 Add ability to download data in excel for All Chart-related data grids.
* [New] 1785 Hide empty Months in dashboards
* [New] 1790 Add button to reset filters
* [New] 1795 Develop pages to display Actual PAX and Special meal quantities and request history
* [New] 1847 Improve error handling for container type editing in the canvas.
* [New] 20095 - Re-added the SLX Dummy Airline's items to StockItem listing grids, and added SLX Dummy Airline as a grid filter option
* [New] 21833 - Internal (SLX Staff) URL links appear in the user account context menu (i.e. profile/support/ log out menu)
<br/>
* [Bugfix] 1788 Drill down chart for Warehouse Valuation needs to be populated
* [Bugfix] 1848 dashboard charts are showing Month+1
* [Bugfix] 22037 - Fixed a null reference error when cancelling a PO's balance from Receipt Confirmation page
* [Bugfix] 22053 - Check user role is authorized to approvde POMCs, at PO/Airline configuration level
* [Bugfix] 22103 - Fixed password reset functionality in AuthServer project (affects files in this project too though, hence the mention)
<br/>
<h1>Build 1.0.105.1</h1>
Release date 18/02/2020
* [Bugfix] 22241 User unable to access the bond station
<br/>
<h1>Build 1.0.105.0</h1>
Release date 13/02/2020
* [New] 1542 Atlas Chiller Icon required for Galley Editor
* [New] 1729 StockItem - pdf button to download Item catalogue list with pictures
* [New] 1736 Count Details Bespoke reports to display number values
* [New] 1756 Ability to create records in AircraftContainerStowage (Stowage Rules)
* [New] 1758 Create portal pages to show Stowage Types and related Container Compatibility
* [New] 1759 Restrict SkyLoad only Aircraft related pages & menus to users with SkyLoad licenced
* [New] 1780 Add total value to bar charts [primary charts]
* [New] 1782 add button to be able to filter bar charts timeline
* [New] 1786 Adjust Legend
* [New] 1787 Add Legend to Warehouse Valuation Chart
* [New] 1792 add country to station performance filter table
<br/>
* [Bugfix] 1800 PO Shipment Splitting - change to the expected date for an existing delivery is not sending an update ReceiptAdvice to the WMS
<h1>Build 1.0.104.2</h1>
Release date 13/02/2020
* [New] 1300 In Full delivery - Supplier - ER18809
* [New] 1548 UI functionality of splitting PO shipments
* [New] 1557 See Support ticket #20027 - improve Error handling when a PO is raised for materials with differing currencies.
    Prevent adding items to a PO if their currency doesn't match with the items already on the PO
* [New] 1567 Create UI for "No Fly" item status Yes/No in stockitem screen
    #1305 / #18801 Added No-Fly flag to the StockItem grid
* [New] 1597 Station Count - Breakages
* [New] 1662 M/T changes required for vendor shipment splitting
* [New] 1740 Restrict access to the galley canvas if a user doesn't have SSO grants.
* [New] 1752 City Pairs & Markets - Improve "Delete" functionality
* [New] 1753 All dashboard charts require the date value displayed in the X-Axis to be in "MMM-YY" date format
* [New] 1765 Improve filters and order by when displaying aircraft stowages from the flight schedule page
* [New] er19939 PO Splitting (PO Vendor Deliveries)
<br/>
* [Bugfix] 1737 Requisition Excess Ordering Thresholds - duplicate logs can be created quite easily
    Avoid having duplicate entries in the RequisitionDetailExcessOrderQtyLog with the addition of a new "Counter" field - attempting to approve the same excessive figures multiple times should now increase the counter field rather than insert a new (duplicate) record.
* [Bugfix] 1757 Item Demand Forecast - External Forecast Data -> Unable to delete row
* [Bugfix] 1762 Support Tickets - Watch List is showing too many records in the new portal.
* [Bugfix] 1772 Several Grids - not possible navigate across different pages of the grids
* [Bugfix] SR21531 - Contract Items report is not loading - fixed
* [Bugfix] sr21633 Changed sort order on Stock Unit DDL
* [Bugfix] sr21655 Fixed issue causing users to be unable to save changes to Station Count Categories (already patched)
<br/>
<h1>Build 1.0.103.6</h1>
Release date 29/01/2020
* [Bugfix] 1769 Error preventing access to Aircraft Layout Editor
<br/>
<h1>Build 1.0.103.5</h1>
Release date 27/01/2020
* [New] 1570 Stock Item - Item Catalog Portal
* [New] 1597 Station Count - Breakages
* [New] 1658 Porting issue - Purchase Order Contract content in the MVC Portal does not allow you to view a break-down of POCntrctDet_ConsQty; this is available in the legacy portal though
* [New] 1669 Allow access to General reports: Issue details, PO lines, contracted Items and Items on PO contracts to Supplier manager role
* [New] 1688 Provide functionality to add/edit and delete module content if SkyLoad is not enabled
* [New] 1741 Enhancements to the SSO Security token functionality.
* [New] 21353 - Make PO Master Contract PDF Generation and Existing documents listing available in Show page, Index Grid (Existing Docs grid on index page)
<br/>
* [Bugfix] 1650 Support Request #20625 - MVC UI is showing misleading information when viewing the break-down of Expected Receipts where the receipt is for a Partially Received PO.
* [Bugfix] 1686 Position and move ability of picture window on canvasses is a problem
* [Bugfix] 1727 When approving a req in MVCRSTEST you get a message ‘true’ pop up after it tells you orders will be create etc.
* [Bugfix] 1738 Unfriendly error is displayed when validation fails for new Aircraft Module creation
* [Bugfix] 20065 - Added SupplierManager roles to the authorised roles for PurchaseOrderDetailSummary_Read (listing of PO Details)
* [Bugfix] 20089 - Edit button hidden for non-SLX users on grids presented on: ItemWarehouse index, ItemPacks index, TransportChains index, and Count Category index views, show button also added which is always available and presents the same data in read-only form.
* [Bugfix] 20105 - Added a help / explain button on the Shipments grid on EditRestrictedPurchaseOrder view
* [Bugfix] 20467 - Fixed DDL population when creating a new PO (delivering to warehouse or warehouse via whse transfer)
* [Bugfix] 21393 - Fix POMC Lookup in PO Creation. (also tested and patched out to 1.0.102.x)
* [Bugfix] 21549 (add any New Airline Supplier records)
<br/>
<h1>Build 1.0.102.6</h1>
Release date 21/01/2020
* [New] 1567 Create UI for "No Fly" item status Yes/No in stockitem screen
* [New] 1598 Airline Supplier - additional contacts
* [New] 1643 Add new field to Contracted items general report
* [New] 1688 Provide functionality to add/edit and delete module content if SkyLoad is not enabled
* [New] 1706 Warehouse - Adjustments screen
* [New] 1710 Implement External order reference for SAP Requisitions
* [New] 1715 Stock count - Migrate columns 'Cancelled' and 'Complete' in Stock Count overview
<br/>
* [Bugfix] 1675 Problem with functionality to delete a stockitem (fix deletion logic)
* [Bugfix] 1701 Purchase Invoicing > All POs Grid shows incorrect value for 'Direct Delivery'.
* [Bugfix] 1727 When approving a requisition, you get a message ‘true’ pop up after it tells you orders will be create etc.
* [Bugfix] 20719 - StockItem edits - ensure Item Cost, Weight, and Item Pack Weight allow up to 6 decimal points precision.
* [Bugfix] 21275 - Fixed grid sorting bug on Stock Item Index grid
* [Bugfix] 21239 - Fixed several Back Order edit issues
* [Bugfix] 21287 - PO Lines report updated to initially sort on PO Creation Date descending.
* [Bugfix] 21393 - Fixed the Contract Reference lookup for PO Edits.
<br/>
<h1>Build 1.0.101.2</h1>
Release date 08/01/2020
* [New] 1568 StationItem - Select Station Items to be Updated using latest station defaults
* [New] 1569 Stock Item - Stock Item Replacements
* [New] 1638 StationItems - migration of station items page
* [New] 1656 Drill down on Open PO status dashboard chart
* [New] 1664 RMA - Ability to amend RMA ETA after RMA has been approved.
* [New] 1668 Bespoke MRP Batch Report amendment
* [New] 1680 Need the ability to create module details for a Miscellaneous Container Group
<br/>
* [Bugfix] 1532 Prevent ability to add disabled users to a ticket's distribution list.
* [Bugfix] 1650 Support Request #20625 - Portal is showing misleading information when viewing the break-down of Expected Receipts where the receipt is for a Partially Received PO.
* [Bugfix] 1647 Support Ticket #20635 - When adding a new Airline Supplier in the portal needs to auto-trim the Supplier Account Number.
* [Bugfix] 1674 Fixed several bugs in the Substitutions module.
* [Bugfix] 1677 Improved error handling in Item Pack maintenance pages.
* [Bugfix] 1685 Stock item editing. Exception if Pack levels have the same "Pack Description" value.
* [Bugfix] 1687 Default Image not showing in the Modules page.
* [Bugfix] 1713 Unable to edit provisional RMAs in v1.0.101.0
* [Bugfix] SR17939 - Disabled selection mode on Station Count items grid and adjusted control heights to hopefully improve the cell-selection issue (Changeset 33196)
* [Bugfix] SR20593 - KPI requisition detail - fixed filter behaviour for the 'Substitute' column.
* [Bugfix] SR21103 - Requisition editing (pre-approval and approval), Save and Continue now retains the Item Grid page number that the user was on.
* [Bugfix] SR21111 - SSIM Index Grid initial sort order now by created date descending.
<br/>
<h1>Build 1.0.100.3</h1>
Release date 03/01/2020
* [New] 1451 Support middle-tier upload function In Progress (Tidied margins and added upload button to change approval page)
* [New] 1496 Validation of supplier contact email
* [New] 1558 Waste Trolley shouldn't be chilled
* [New] 1588 MRP - Planner Orders - Additional columns for "Soft POs"
* [New] 1595 KPI receipt - station receipt report with additional columns
* [New] 1596 KPI report - IWT Details report
* [New] 1607 Supplier Performance Dashboard - Supplier On Time Commitment chart
* [New] 1610 Supplier Performance Dashboard - Dashboard Open POs Status chart
* [New] 1618 Validation needed when changing an Organization Type
* [New] 1648 Add Cost Centre Category Code to GL Account Category pages
* [New] 1649 Small changes and tidy up to GL Cost Centre category pages
* [New] 1652 Implemented ability to maintain Alternative Aircraft Codes
* [New] 1655 Better handled violations of Unique Index: IDX_RequisitionDetail_ReqHdr_ID__StkItem_ID__ReqDate__ExtLineRef, currently an unfriendly error message is presented to the user, which causes confusion
* [New] 1663 Implemented ability to resolve an SSIM that was burst with errors.
* [New] 1667 Release banner should come up at Home Screen and as a banner T-10 minutes
* [New] 20669 Quantity fields on Station Counts now only validated on submission (so users can save as they go)
* [New] 20923 Saving a station will now only validate Default Loading (and it's relation to other active caterer stations) if the user actually changed the value
<br/>
* [Bugifx] 1549 Portal doesn't display extended characters correctly on drop down lists
* [Bugfix] 1632 Non default pack quantity not enforced when adding items to back orders
* [Bugfix] 1633 AircraftStowagePositionList Report Error
* [Bugfix] 1654 Filtering on Aircraft Type page is not working as it should
<br/>
<h1>Build 1.0.99.4</h1>
Release date 18/12/2019
* [Bugfix] 1642 SkyLog tickets - responsible user needs to be included in the e-mail list
* [Bugfix] 1676 StockitemForecastLoadfactor decimal precision not being displayed correctly
* [Bugfix] 1678 Deletion of an AircraftModule logic when to activate the delete icon is wrong
<br/>
<h1>Build 1.0.99.2</h1>
Release date 12/12/2019
* [New] 1442 Display days coverage in MRP Daily figure
* [New] 1451 Support m/t upload function
* [New] 1527 When dragging a stowage position to the Galley canvas where is the default unit of Dims coming from? Also Min check needs explaining in terms of the unit
* [New] 1550 Implemented ability to review forecasts
* [New] 1601 Tidy up Aircraft Tail Number pages
* [New] 1605 Dashboard - Drill data implemented for the Late Open PO shipments chart.
* [New] 1609 Planned Orders - UI - General reports to display data from MRPSoftOrderDetail
* [New] 1615 Make SLX portal version identifier clickable - redirecting you to release history on the wiki
* [New] 1617 Add Organization Type to Airline Supplier pages
* [New] 1629 ER 20479 - Add External Line Number column to the PO lines KPI report
<br/>
* [Bugfix] 1446 SkylogistiX Wiki - Fix to improve the performance of the portal (reducing database reads).
* [Bugfix] 20515 - Improved error handling for bespoke reports
* [Bugfix] 20637 - Improved performance for loading items to add to Requisition
* [Bugfix] 1148 Add time stamp to error pop-ups
* [Bugfix] 1375 Enhance filters across all pages / grids = trimming numeric filter searches
* [Bugfix] 1470 Support Ticket #19505 - Unable to export Bespoke Reports to MS-Excel
* [Bugfix] 1639 SkyLog tickets - line breaks in the Detailed Description of the Problem
* [Bugfix] 1642 SkyLog tickets - responsible user needs to be included in the e-mail list
<br/>
<h1>Build 1.0.98.3</h1>
Release date 06/12/2019
* [New] 1218 Add a delete Icon to the StockItem/Index page to allow stock items to be deleted
* [New] 1492 Substitution Module / Unplanned Substitutions migrated to new portal
* [New] 1500 PO Lines data grid - files downloaded into csv/xls should have a date format adjusted to dd/mm/yyyy
* [New] 1511 ItemSupplier index grid updated to include new columns
* [New] 1580 Station Performance dashboard - Add "under review" and "recount" statuses to "Station Stock Count" chart.
* [New] 1593 Planned orders - UI - Add field forecasting period to Item supplier - Warehouse grid
* [New] 1622 Station KPI - Station late orders table need mode of transport
* [New] 1621 New Dashboard Group: 'Supplier Performance'
* [New] 1604 'Supplier Performance' Dashboard chart - Late Open PO shipments
<br/>
* [Bugfix] 1611 Consumption chart not rendering categories in the correct order when when filters are applied.
* [Bugfix] 1612 Station KPI dashboard - Station count chart refresh
* [Bugfix] 1470 Support Ticket #19505 - Unable to export Bespoke Reports to MS-Excel
* [Bugfix] 1562 Aircraft Config - Creation Date Failure
* [Bugfix] 1608 Module Copy & Delete Issues
* [Bugfix] 1619 "sortablejs" node modules call exception when canvas loading
* [Bugfix] 19133 - Sort order on Requisition Approval grid changes dependent on whether or not the airline is using Loading Groups.
* [Bugfix] 20289 - StationCountCategory Edit page improvements - fields for IncludeAllSPL and UpdateSPL are now read-only with appropriate values if Approval is not required.
* [Bugfix] 20375 - Changed option label for "Climate Requirements" on adding a stockitem
* [Bugfix] 20379 - Fixed incorrect field binding on Stock Allocated to Warehouse Transfers grid (outbound)
* [Bugfix] 20437 - Fixed method used to retrieve the blank count file - now returns the latest if there's multiple
* [Bugfix] 20465 - Export button added to non-SAP-centric BackOrder items grid
* [Bugfix] 20487 - Added Rule Sequence field to Provisioning Rules grid
* [Bugfix] 20489 - Changed query for Expected Warehouse Transfers (Stock Levels) grid so that it's based on WarehouseTransferReceipt rather than WarehouseTransferDetail.
* [Bugfix] 20515 - Fixed error handling on Bespoke Reports.
<br/>
<h1>Build 1.0.97.0</h1>
Release date 02/12/2019
* [New] 1297 - Dashboard Chart - Shipments by Mode of Transport and On Time % - ER16865
* [New] 1446 - SkylogistiX Wiki
* [New] 1492 - (minor errors) Substitution Module / unplanned substitutions website
* [New] 1520 - Port across functionality to allow the User Station Access table to be managed through the new portal
* [New] 1566 - When creating a new Station Par Level entry (Station Item record), we should check to see if the "new" material has been associated with the station previously
* [New] 1585 - Make the 'Network On Time Receipts' chart wider by default, and allow to be re-sizeable.
<br/>
* [Bugfix] 1499 - StationCount Detail 'Last Count Date' not being populated in some cases (19641)
* [Bugfix] 1613 - SR20423 - Build v1.0.96.0 has introduced a bug - problems editing ItemWarehouse records from page: /StockItem/Edit
* [Bugfix] 1623 - SR20433 - Back Order processing - it is not possible to ship from an alternate warehouse
* [Bugfix] 1626 - Unable to submit Requisitions in 1.0.97.x
* [Bugfix] 1631 - MRP Supply Parameters - Item Warehouse edit bug
<br/><h1>Build 1.0.96.0</h1>
Release date 20/11/2019
* [New] 1520 - Port across functionality to allow User Station Access to be managed in the new portal
* [New] 1555 - Added Planner Name column to the Stock Levels index grid
* [New] 20055 - MOQ and EOQ fields on Item Warehouse editor template
* [New] 1519 - Warehouse Inventory Valuations Report (KPI)
<br/>
* [Bugfix] 1563 - Duplicate Container Item Type
* [Bugfix] 1558 - Waste Trolley should not be chilled
* [Bugfix] 20133 - Transit Only field bug on editing Warehouse
* [Bugfix] 1453 - UI allows an MRP line to be submitted even if the Qty control is not showing a figure/value
* [Bugfix] 20171 - Problems adding Stock Item Packs

Support Ticket

2020-05-14T16:49:04Z

Arunas.milasius: Created page with "<h1>Summary</h1> Support Request page is used to raise open issues, questions and request directly to SkylogistiX IT Support team. All support requests are reviewed and acted..."

<h1>Summary</h1>

Support Request page is used to raise open issues, questions and request directly to SkylogistiX IT Support team. All support requests are reviewed and acted upon. Note that SkylogistiX IT Support addresses issues impacting operations with priority.

When raising a ticket it is important to select airline and skylog area affected, provide detailed description of the problem and attached all evidence collected. Once ticket is logged you will be receiving updated each time ticket has a new post or status update.

<h1>Support Request and Types</h1>
Support Request are used contact for any problems that users may experience while using Skylog. When ticket is raised email notifications will follow with each update on a ticket or status change. Users should be alert and available to provide feedback to support team in case of a follow up questions or request for more information.

<h1>Enhancement Request</h1>
Skylog is always evolving and improving with new functionalities. Enhancement request is the way these improvement are discussed across different operations and IT Developer team to agree design that could benefit all.

Enhancement request requires detail description of the problem and proposed solution or user experience to address it. Proposal is reviewed and potential solutions are discussed to agree on viable design to hand over to developers to prioritize and implement.

Please note that enhancement request are more complex request then a support reuqest and requires time to be reviewed and addressed.

<h1>How to log a ticket</h1>

When logging a ticket it is essential to provide as much information as possible about the issue you are facing. Please provide detailed description of the problem, what time it occurred, and what steps were taken. It is best practice to have either video recording of the problem, full screenshot including time stamp and URL, or even putting it in a presentation document with all details.

Once information has been collected you can raise support ticket by following below steps

[[File:SupportRequestForm.png]]
# In a support request window please fill every window
## <b>Area</b> - Choose from the list of options one best describing the area in which the are facing and issue (e.g. Forecasting, Interface, Requisitioning etc)
## <b>Project</b> - Choose airline name of your account
## <b>Category</b> - Name the type of problem you are facing. For example, if some data is not correct or not showing - Data Issue, if there is an issue with an system interface with 3rd party systems - EDI Issue, Skylog also has an option dedicated for "Skylog Functional Question" in case questions arise regarding how certain Skylog processes work.
## <b>Priority</b> - Skylog request users to identify the priority of an a problem logged. We trust users to follow below guidelines and respecting priorities suggested:
##* Low - Used for issues found in testing environment, or problems that have no effect on operations
##* Standard - Used in majority of cases, it is used when particular part of Skylog is not functioning properly slowing down operation, but has workaround in place.
##* Important - Reserved for cases that are affecting selected area of operations and requires immediate IT involvement to address or support providing a workaround.
##* Critical- is reserved for cases when operation is frozen and cannot conduct day to day tasks in multiple areas of operations.
## <b>Subject</b> - a header title of problem logged
## <b>Detailed</b> - a more detailed description of the problem, time and situation it has occurred
# Click on [[File:Submit.png]].

<h1>Tips and Tricks</h1>
[[file:SupportOtherFunctions.png]]
<h2>Monitoring tickets <h2>
Skylog tickets system allows users to monitor relevant tickets. If you are interested to be kept up to date on Support request or Enhancement request, just open the ticket you are interested and click on a [[File:MonitorButton.png]].

If you, want to add someone to a ticket to receive all notifications and updates. You can do that by clicking on [[File:ViewDistributionList.png]] and [[File:Plusplus.png]] to add at selected person

<h2>Link different tickets <h2>
You can also link different related tickets to provide more information and to make sure it is easier to track information related to request. To do so please open a ticket you an active ticket and click on [[File:LinkedTickets:png]], click on [[File:Plusplus.png]], find relevant ticket and click to update.

File:SupportOtherFunctions.png

2020-05-14T16:36:25Z

Arunas.milasius:

File:ViewDistributionList.png

2020-05-14T16:35:58Z

Arunas.milasius:

File:MonitorButton.png

2020-05-14T16:35:33Z

Arunas.milasius:

File:LinkedTickets.png

2020-05-14T16:35:17Z

Arunas.milasius:

File:SupportRequestForm.png

2020-05-14T16:09:42Z

Arunas.milasius:

Station Index

2020-04-27T15:18:19Z

Arunas.milasius:

__TOC__

<h1>Summary</h1>

<h1>Create organization</h1>

Organization refers to company as a whole like Lufthansa or Gate Group, and contains Organization site locations under it in Skylog (e.g. Gate Group London T5). Organization defines company type and service it provides.
First, please check if Organization already exists in Skylog Organizations page [[https://rsprod.skylogportal.com/Organization'''link''']]. If Organization already exists please move to next step.

If Organization does not exist, there are 2 ways to create an Organization: [1] contact Global Administrator or raise support request. [[http://wiki.skylogportal.com/?title=Support_Index'''link''']]

<h1>Organization Sites</h1>

Organization sites determines address of the of a station, supplier or warehouse. These have to be set up if new station, supplier or warehouse needs to be added to Skylog and record does not exist.

Firstly Please check if a site is already created in skylog with same address and link to Same Organization. It is important not to duplicate organization sites entries if address assigned to organization already exists. For more please see link [[http://wiki.skylogportal.com/?title=OrganizationSite_Index'''link''']]

<h1>Stations</h1>

Station set up contains specification of stations operations (lead times, safety stocks etc.) and items (Par Levels) that it will be holding. Skylog allows advance ways to customize stations set up, from automatic stock count approvals, different ways of RMA management, and automation if process flows.

<h2>Stations creation</h2>
to create station few tings 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 advance customization of all stations. To deliver the most productive set up please consult guide below that 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 station address that is printed in invoices 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 airport it services. It is essential for enhanced forecasting and consumption calculations</p>
</td>
</tr>
<tr>
<td width="170">
<p>Service Type</p>
</td>
<td width="444">
<p>assign relevant station type</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 and forecast assigned to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Valid To</p>
</td>
<td width="444">
<p>date of station closure. Is not a mandatory field to be populated</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 provision of goods for the station (i.e. who will approve requisition requests, inventory reports, etc.)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="444">
<p>person to be assigned (from users register in Skylog) who will be responsible for stock counts. Selected person will be recipient of related notifications</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 with Skylog – if the station will raise requisitions and/or be expected to submit inventory reports then this setting should always be set as 'No'.</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 generated automatic requisitions after stock count, via schedule or even manually. If no, only manual orders will be allowed to be placed by station, more relevant 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. If the station wishes to see such temporary items on requisitions then this configuration flag should be set as 'Yes', otherwise, set as 'No'.</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 Skylog 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 Skylog. 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).</p>
</td>
</tr>
<tr>
<td width="170">
<p>Enforce RMA Qty</p>
</td>
<td width="444">
<p>if station is allowed to issue RMA for parts they haven't ordered from inbound flights etc. then No. If Yes, station will be allowed to return only stock qty that they counted in 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>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>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 intGL Cost Centre field links financial data with customer financial systems. for Catering units please select airport caterer supplies. For other operations like Lounges and Laundry Customer is to confirm which GL Code to be used in those exceptional cases. In case new GL Cost Centre require new set up please follow the link for guidance how to [[http://wiki.skylogportal.com/?title=Station_CostCentreCategoryIndex'''link''']].</p>
</td>
</tr>
</table>

<h1>Supply Source</h1>

Supply sources defines which warehouses will be supplying stations with goods and modes of transport used. It is possible for station 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.

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

<h2>Add Warehouse</h2>

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]]

<h2>Add Transport Methods</h2>

<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]]

<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 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]]

<h1>Station Count Category</h1>
[File:CreateStationCountCategory.png]

Station count category defines which items, how often need to be counted by station. It also allows to set the tolerances to count variances for automatic query process as well as define the level of automation in count and approval process – some counts can be set up as auto accepted after they are submitted, useful feature for stations like lounges, with little turn over. 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]]

<li>Fill the table. Fields are explained in table below with samples.</li>
</ol>
</li>

<table width="0">
<tr>
<td width="170">
<p><strong>Field</strong></p>
</td>
<td width="85">
<p><strong>Sample</strong></p>
</td>
<td width="387">
<p><strong>Description</strong></p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Category Description</p>
</td>
<td width="85">
<p>Full</p>
</td>
<td width="387">
<p>Description of the count. Station could have multiple counts with different parts under each, so name of the count is useful to avoid confusions</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Schedule Option</p>
</td>
<td width="85">
<p>Automatic Schedule</p>
</td>
<td width="387">
<p>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)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Automatic Schedule Options</p>
</td>
<td width="85">
<p>Specific Day/s of the Week</p>
</td>
<td width="387">
<p>can name days of the week or month for stock count to be automatically repeated</p>
</td>
</tr>
<tr>
<td width="170">
<p>Specific Day/s of the Week</p>
</td>
<td width="85"> </td>
<td width="387">
<p>tick/ select days when stock count should be triggered</p>
</td>
</tr>
<tr>
<td width="170">
<p>Weeks Between Counts</p>
</td>
<td width="85">
<p>1</p>
</td>
<td width="387">
<p>Nr of weeks in between counts</p>
</td>
</tr>
<tr>
<td width="170">
<p>Notify Days</p>
</td>
<td width="85">
<p>3</p>
</td>
<td width="387">
<p>Nr of days stock count will be generated before, and station will get a notification</p>
</td>
</tr>
<tr>
<td width="170">
<p>Next Count Generation Date</p>
</td>
<td width="85">
<p>September 28, 2019</p>
</td>
<td width="387">
<p>Select next/first stock count to be schedule for date</p>
</td>
</tr>
<tr>
<td width="170">
<p>Value Tolerance for Count Variances</p>
</td>
<td width="85"> </td>
<td width="387">
<p>not mandatory, select variances in value per line to tolerate as ok. Meaning if there is 100 GBP tolerance and discrepancy from expected sock count is 99, count will appear as ok. This could be changed later at the item level for exceptions</p>
</td>
</tr>
<tr>
<td width="170">
<p>% Quantity Tolerance for Count Variances</p>
</td>
<td width="85">
<p>10</p>
</td>
<td width="387">
<p>not mandatory, select variance in quantity % per line to be tolerated from expected count. Meaning if 5% discrepancy from expected stock count is allowed and will not appear as a query. Can be amended at the item level for exception items</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="85"> </td>
<td width="387">
<p>select person (out of assigned to this stations/organization site, that will be responsible for counts and will be receiving notifications related to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Floating Qty</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Float stock, is what is flown and/or kept in the kitchen. If selected yes, column will appear at the sock count to count both Backup stock and Float stock (back up stock is default and will always appear in stock count sheet)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Breakages</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will add a column for breakages to be filled by station during stock count.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Attach Count Sheet File When Notifying Station</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Advise to select Yes, that will have attached an excel file that when filled could be uploaded to stock count for submission. It is a good tool to avoid manual entries in the portal.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Consumption Trend Span (Days)</p>
</td>
<td width="85">
<p>180</p>
</td>
<td width="387">
<p>default value is 180, and if left blank it will generate value of 180 days.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Generate Automatic Requisitions Upon Count Approval</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if Yes, will post an option to generate automatic requisition after stock count is approved.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include All Items in Automatic Requisitions</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if yes, will include all active items in auto requisition (even if suggested order is 0)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Delay (Hours) For Automatic Requisition Generation</p>
</td>
<td width="85">
<p>0</p>
</td>
<td width="387"> </td>
</tr>
<tr>
<td width="170">
<p>Include All Station Par Levels In Counts</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will include all active items in stock count and phase out items that have nothing in transit and where counted previously.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Update Station Par Levels</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if new part is added to requisition, it will update station par levels</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Auto Approval Option</p>
</td>
<td width="85">
<p>Review</p>
</td>
<td width="387">
<p>Review Required - will request for Station Manager to do a full review of every stock count submitted by stations<br /> Auto-Approve When No Queries - stock count will be automatically approved by Skylog if no queries where generated by system;</p>
</td>
</tr>
</table>

<h2>Sample of complete Station Count Category setup</h2>
[[File:SampleCategoryCount.png]]

<h1>Station Defaults</h1>

Station defaults are used whenever doing a mass transaction, for example - mass import of items to station par level. The criteria in station defaults will be applied to all items imported.
<ol>
<li>In Stations screen (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 sock to be held a the station of item 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>days needed to get stock prepared for operation after it is receipted.</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>days needed to recycle stock from inbound flights to be ready for operations</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>based on Order frequency select</p>
</td>
</tr>
<tr>
<td width="217">
<p>% Loss at the Station</p>
</td>
<td width="81">
<p>0</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 sock count category (set up in previous chapter) to which items will be added</p>
</td>
</tr>
<tr>
<td width="217">
<p>Round Requisition Quantities?</p>
</td>
<td width="81">
<p>Yes</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>

<h1>Stock Items / Par Levels</h1>

Station Par levels refers to items station would be allowed to place orders for and receive stock. This can be done in a few ways: copy Par Levels from identical/similar station or do it one item at a time
<h2>Copy Par Level from existing station</h2>

<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 please find button Copy</li>
[[File:LocationOfCopyParLevelsButton.png]]

<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]]

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

</ol>

<h2>Adding Items to Par Levels</h2>

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

<h1>Closing Station</h1>

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

<h2>Stock In transit is accounted for</h2>
Any stock station has in transit needs to be receipted and moved via RMA, used up at the station or or scrapped with a scrap order, before station can be closed

<h2>Station Stock Counts are closed</h2>
All station stock counts need to be closed, and most importantly, last stock count needs to reflect empty warehouse - last stock count qty of each item needs to be 0. This is important to reflect correct consumption and asset valuations.

<h2>End of the forecast </h2>
For all stations to be closed all manual forecast uploaded in skylog related to this stations needs to be removed from skylog.

Station Index

2020-04-27T15:01:15Z

Arunas.milasius:

Station Index

2020-04-27T14:07:54Z

Arunas.milasius:

__TOC__

<h1>Summary</h1>

<h1>Create organization</h1>

Organization refers to company as a whole like Lufthansa or Gate Group, and contains Organization site locations under it in Skylog (e.g. Gate Group London T5). Organization defines company type and service it provides.
First, please check if Organization already exists in Skylog Organizations page [[https://rsprod.skylogportal.com/Organization'''link''']]. If Organization already exists please move to next step.

If Organization does not exist, there are 2 ways to create an Organization: [1] contact Global Administrator or raise support request. [[http://wiki.skylogportal.com/?title=Support_Index'''link''']]

<h1>Organization Sites</h1>

Organization sites determines address of the of a station, supplier or warehouse. These have to be set up if new station, supplier or warehouse needs to be added to Skylog and record does not exist.

Firstly Please check if a site is already created in skylog with same address and link to Same Organization. It is important not to duplicate organization sites entries if address assigned to organization already exists. For more please see link [[http://wiki.skylogportal.com/?title=OrganizationSite_Index'''link''']]

<h1>Stations</h1>

Station set up contains specification of stations operations (lead times, safety stocks etc.) and items (Par Levels) that it will be holding. Skylog allows advance ways to customize stations set up, from automatic stock count approvals, different ways of RMA management, and automation if process flows.

<h2>Stations creation</h2>
to create station few tings 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 advance customization of all stations. To deliver the most productive set up please consult guide below that 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 station address that is printed in invoices 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 airport it services. It is essential for enhanced forecasting and consumption calculations</p>
</td>
</tr>
<tr>
<td width="170">
<p>Service Type</p>
</td>
<td width="444">
<p>assign relevant station type</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 and forecast assigned to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Valid To</p>
</td>
<td width="444">
<p>date of station closure. Is not a mandatory field to be populated</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 provision of goods for the station (i.e. who will approve requisition requests, inventory reports, etc.)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="444">
<p>person to be assigned (from users register in Skylog) who will be responsible for stock counts. Selected person will be recipient of related notifications</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 with Skylog – if the station will raise requisitions and/or be expected to submit inventory reports then this setting should always be set as 'No'.</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 generated automatic requisitions after stock count, via schedule or even manually. If no, only manual orders will be allowed to be placed by station, more relevant 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. If the station wishes to see such temporary items on requisitions then this configuration flag should be set as 'Yes', otherwise, set as 'No'.</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 Skylog 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 Skylog. 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).</p>
</td>
</tr>
<tr>
<td width="170">
<p>Enforce RMA Qty</p>
</td>
<td width="444">
<p>if station is allowed to issue RMA for parts they haven't ordered from inbound flights etc. then No. If Yes, station will be allowed to return only stock qty that they counted in 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>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>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 intGL Cost Centre field links financial data with customer financial systems. for Catering units please select airport caterer supplies. For other operations like Lounges and Laundry Customer is to confirm which GL Code to be used in those exceptional cases. In case new GL Cost Centre require new set up please follow the link for guidance how to [[http://wiki.skylogportal.com/?title=Station_CostCentreCategoryIndex'''link''']].</p>
</td>
</tr>
</table>

<h1>Supply Source</h1>

Supply sources defines which warehouses will be supplying stations with goods and modes of transport used. It is possible for station 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.

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

<h2>Add Warehouse</h2>

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]]

<h2>Add Transport Methods</h2>

<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]]

<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 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:CompleteTransportSetup.png]]

<h1>Station Count Category</h1>
[File:CreateStationCountCategory.png]

Can be found under Daily Activities/Inventory Counts/Station Count Categories. Station count category defines which items, how often need to be counted by station. It also allows to set the tolerances to count variances for automatic query process as well as define the level of automation in count and approval process – some counts can be set up as auto accepted after they are submitted, useful feature for stations like lounges, with little turn over.
<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]]

<li>Fill the table. Fields are explained in table below with samples.</li>
</ol>
</li>

<table width="0">
<tr>
<td width="170">
<p><strong>Field</strong></p>
</td>
<td width="85">
<p><strong>Sample</strong></p>
</td>
<td width="387">
<p><strong>Description</strong></p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Category Description</p>
</td>
<td width="85">
<p>Full</p>
</td>
<td width="387">
<p>Description of the count. Station could have multiple counts with different parts under each, so name of the count is useful to avoid confusions</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Schedule Option</p>
</td>
<td width="85">
<p>Automatic Schedule</p>
</td>
<td width="387">
<p>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)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Automatic Schedule Options</p>
</td>
<td width="85">
<p>Specific Day/s of the Week</p>
</td>
<td width="387">
<p>can name days of the week or month for stock count to be automatically repeated</p>
</td>
</tr>
<tr>
<td width="170">
<p>Specific Day/s of the Week</p>
</td>
<td width="85"> </td>
<td width="387">
<p>tick/ select days when stock count should be triggered</p>
</td>
</tr>
<tr>
<td width="170">
<p>Weeks Between Counts</p>
</td>
<td width="85">
<p>1</p>
</td>
<td width="387">
<p>Nr of weeks in between counts</p>
</td>
</tr>
<tr>
<td width="170">
<p>Notify Days</p>
</td>
<td width="85">
<p>3</p>
</td>
<td width="387">
<p>Nr of days stock count will be generated before, and station will get a notification</p>
</td>
</tr>
<tr>
<td width="170">
<p>Next Count Generation Date</p>
</td>
<td width="85">
<p>September 28, 2019</p>
</td>
<td width="387">
<p>Select next/first stock count to be schedule for date</p>
</td>
</tr>
<tr>
<td width="170">
<p>Value Tolerance for Count Variances</p>
</td>
<td width="85"> </td>
<td width="387">
<p>not mandatory, select variances in value per line to tolerate as ok. Meaning if there is 100 GBP tolerance and discrepancy from expected sock count is 99, count will appear as ok. This could be changed later at the item level for exceptions</p>
</td>
</tr>
<tr>
<td width="170">
<p>% Quantity Tolerance for Count Variances</p>
</td>
<td width="85">
<p>10</p>
</td>
<td width="387">
<p>not mandatory, select variance in quantity % per line to be tolerated from expected count. Meaning if 5% discrepancy from expected stock count is allowed and will not appear as a query. Can be amended at the item level for exception items</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="85"> </td>
<td width="387">
<p>select person (out of assigned to this stations/organization site, that will be responsible for counts and will be receiving notifications related to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Floating Qty</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Float stock, is what is flown and/or kept in the kitchen. If selected yes, column will appear at the sock count to count both Backup stock and Float stock (back up stock is default and will always appear in stock count sheet)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Breakages</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will add a column for breakages to be filled by station during stock count.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Attach Count Sheet File When Notifying Station</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Advise to select Yes, that will have attached an excel file that when filled could be uploaded to stock count for submission. It is a good tool to avoid manual entries in the portal.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Consumption Trend Span (Days)</p>
</td>
<td width="85">
<p>180</p>
</td>
<td width="387">
<p>default value is 180, and if left blank it will generate value of 180 days.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Generate Automatic Requisitions Upon Count Approval</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if Yes, will post an option to generate automatic requisition after stock count is approved.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include All Items in Automatic Requisitions</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if yes, will include all active items in auto requisition (even if suggested order is 0)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Delay (Hours) For Automatic Requisition Generation</p>
</td>
<td width="85">
<p>0</p>
</td>
<td width="387"> </td>
</tr>
<tr>
<td width="170">
<p>Include All Station Par Levels In Counts</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will include all active items in stock count and phase out items that have nothing in transit and where counted previously.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Update Station Par Levels</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if new part is added to requisition, it will update station par levels</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Auto Approval Option</p>
</td>
<td width="85">
<p>Review</p>
</td>
<td width="387">
<p>Review Required - will request for Station Manager to do a full review of every stock count submitted by stations<br /> Auto-Approve When No Queries - stock count will be automatically approved by Skylog if no queries where generated by system;</p>
</td>
</tr>
</table>

<h2>Sample of complete Station Count Category setup</h2>
[[File:SampleCategoryCount.png]]

<h1>Station Defaults</h1>

Station defaults are used whenever doing a mass transaction, for example mass import of items to station par level. The criteria in station defaults will be applied to all items imported.
<ol>
<li>In Stations screen (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 sock to be held a the station of item 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>days needed to get stock prepared for operation after it is receipted.</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>days needed to recycle stock from inbound flights to be ready for operations</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>based on Order frequency select</p>
</td>
</tr>
<tr>
<td width="217">
<p>% Loss at the Station</p>
</td>
<td width="81">
<p>0</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 sock count category (set up in previous chapter) to which items will be added</p>
</td>
</tr>
<tr>
<td width="217">
<p>Round Requisition Quantities?</p>
</td>
<td width="81">
<p>Yes</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>

<h1>Stock Items / Par Levels</h1>

Station Par levels refers to items station would be allowed to place orders for and receive stock. This can be done in a few ways: copy Par Levels from identical/similar station or do it one item at a time
<h2>Copy Par Level from existing station</h2>

<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 please find button Copy</li>
[[File:LocationOfCopyParLevelsButton.png]]

<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]]

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

</ol>

Station Index

2020-04-27T14:03:20Z

Arunas.milasius:

__TOC__

<h1>Summary</h1>

<h1>Create organization</h1>

Organization refers to company as a whole like Lufthansa or Gate Group, and contains Organization site locations under it in Skylog (e.g. Gate Group London T5). Organization defines company type and service it provides.
First, please check if Organization already exists in Skylog Organizations page [[https://rsprod.skylogportal.com/Organization'''link''']]. If Organization already exists please move to next step.

If Organization does not exist, there are 2 ways to create an Organization: [1] contact Global Administrator or raise support request. [[http://wiki.skylogportal.com/?title=Support_Index'''link''']]

<h1>Organization Sites</h1>

Organization sites determines address of the of a station, supplier or warehouse. These have to be set up if new station, supplier or warehouse needs to be added to Skylog and record does not exist.

Firstly Please check if a site is already created in skylog with same address and link to Same Organization. It is important not to duplicate organization sites entries if address assigned to organization already exists. For more please see link [[http://wiki.skylogportal.com/?title=OrganizationSite_Index'''link''']]

<h1>Stations</h1>

Station set up contains specification of stations operations (lead times, safety stocks etc.) and items (Par Levels) that it will be holding. Skylog allows advance ways to customize stations set up, from automatic stock count approvals, different ways of RMA management, and automation if process flows.

<h2>Stations creation</h2>
to create station few tings 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 advance customization of all stations. To deliver the most productive set up please consult guide below that 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 station address that is printed in invoices 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 airport it services. It is essential for enhanced forecasting and consumption calculations</p>
</td>
</tr>
<tr>
<td width="170">
<p>Service Type</p>
</td>
<td width="444">
<p>assign relevant station type</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 and forecast assigned to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Valid To</p>
</td>
<td width="444">
<p>date of station closure. Is not a mandatory field to be populated</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 provision of goods for the station (i.e. who will approve requisition requests, inventory reports, etc.)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="444">
<p>person to be assigned (from users register in Skylog) who will be responsible for stock counts. Selected person will be recipient of related notifications</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 with Skylog – if the station will raise requisitions and/or be expected to submit inventory reports then this setting should always be set as 'No'.</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 generated automatic requisitions after stock count, via schedule or even manually. If no, only manual orders will be allowed to be placed by station, more relevant 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. If the station wishes to see such temporary items on requisitions then this configuration flag should be set as 'Yes', otherwise, set as 'No'.</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 Skylog 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 Skylog. 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).</p>
</td>
</tr>
<tr>
<td width="170">
<p>Enforce RMA Qty</p>
</td>
<td width="444">
<p>if station is allowed to issue RMA for parts they haven't ordered from inbound flights etc. then No. If Yes, station will be allowed to return only stock qty that they counted in 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>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>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 intGL Cost Centre field links financial data with customer financial systems. for Catering units please select airport caterer supplies. For other operations like Lounges and Laundry Customer is to confirm which GL Code to be used in those exceptional cases. In case new GL Cost Centre require new set up please follow the link for guidance how to [[http://wiki.skylogportal.com/?title=Station_CostCentreCategoryIndex'''link''']].</p>
</td>
</tr>
</table>

<h1>Supply Source</h1>

Supply sources defines supplying warehouse and modes of transport assigned. It is possible for station to be supplied by multiple warehouses and this could be defined at the item level is Station Item / Par Level tables. Multiple modes of transport could be assigned for each station with different lead-times

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

<h2>Add Warehouse</h2>
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]]

<h2>Add Transport Methods</h2>

<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]]

<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 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:CompleteTransportSetup.png]]

<h1>Station Count Category</h1>
[File:CreateStationCountCategory.png]

Can be found under Daily Activities/Inventory Counts/Station Count Categories. Station count category defines which items, how often need to be counted by station. It also allows to set the tolerances to count variances for automatic query process as well as define the level of automation in count and approval process – some counts can be set up as auto accepted after they are submitted, useful feature for stations like lounges, with little turn over.
<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]]

<li>Fill the table. Fields are explained in table below with samples.</li>
</ol>
</li>

<table width="0">
<tr>
<td width="170">
<p><strong>Field</strong></p>
</td>
<td width="85">
<p><strong>Sample</strong></p>
</td>
<td width="387">
<p><strong>Description</strong></p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Category Description</p>
</td>
<td width="85">
<p>Full</p>
</td>
<td width="387">
<p>Description of the count. Station could have multiple counts with different parts under each, so name of the count is useful to avoid confusions</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Schedule Option</p>
</td>
<td width="85">
<p>Automatic Schedule</p>
</td>
<td width="387">
<p>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)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Automatic Schedule Options</p>
</td>
<td width="85">
<p>Specific Day/s of the Week</p>
</td>
<td width="387">
<p>can name days of the week or month for stock count to be automatically repeated</p>
</td>
</tr>
<tr>
<td width="170">
<p>Specific Day/s of the Week</p>
</td>
<td width="85"> </td>
<td width="387">
<p>tick/ select days when stock count should be triggered</p>
</td>
</tr>
<tr>
<td width="170">
<p>Weeks Between Counts</p>
</td>
<td width="85">
<p>1</p>
</td>
<td width="387">
<p>Nr of weeks in between counts</p>
</td>
</tr>
<tr>
<td width="170">
<p>Notify Days</p>
</td>
<td width="85">
<p>3</p>
</td>
<td width="387">
<p>Nr of days stock count will be generated before, and station will get a notification</p>
</td>
</tr>
<tr>
<td width="170">
<p>Next Count Generation Date</p>
</td>
<td width="85">
<p>September 28, 2019</p>
</td>
<td width="387">
<p>Select next/first stock count to be schedule for date</p>
</td>
</tr>
<tr>
<td width="170">
<p>Value Tolerance for Count Variances</p>
</td>
<td width="85"> </td>
<td width="387">
<p>not mandatory, select variances in value per line to tolerate as ok. Meaning if there is 100 GBP tolerance and discrepancy from expected sock count is 99, count will appear as ok. This could be changed later at the item level for exceptions</p>
</td>
</tr>
<tr>
<td width="170">
<p>% Quantity Tolerance for Count Variances</p>
</td>
<td width="85">
<p>10</p>
</td>
<td width="387">
<p>not mandatory, select variance in quantity % per line to be tolerated from expected count. Meaning if 5% discrepancy from expected stock count is allowed and will not appear as a query. Can be amended at the item level for exception items</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="85"> </td>
<td width="387">
<p>select person (out of assigned to this stations/organization site, that will be responsible for counts and will be receiving notifications related to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Floating Qty</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Float stock, is what is flown and/or kept in the kitchen. If selected yes, column will appear at the sock count to count both Backup stock and Float stock (back up stock is default and will always appear in stock count sheet)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Breakages</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will add a column for breakages to be filled by station during stock count.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Attach Count Sheet File When Notifying Station</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Advise to select Yes, that will have attached an excel file that when filled could be uploaded to stock count for submission. It is a good tool to avoid manual entries in the portal.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Consumption Trend Span (Days)</p>
</td>
<td width="85">
<p>180</p>
</td>
<td width="387">
<p>default value is 180, and if left blank it will generate value of 180 days.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Generate Automatic Requisitions Upon Count Approval</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if Yes, will post an option to generate automatic requisition after stock count is approved.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include All Items in Automatic Requisitions</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if yes, will include all active items in auto requisition (even if suggested order is 0)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Delay (Hours) For Automatic Requisition Generation</p>
</td>
<td width="85">
<p>0</p>
</td>
<td width="387"> </td>
</tr>
<tr>
<td width="170">
<p>Include All Station Par Levels In Counts</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will include all active items in stock count and phase out items that have nothing in transit and where counted previously.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Update Station Par Levels</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if new part is added to requisition, it will update station par levels</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Auto Approval Option</p>
</td>
<td width="85">
<p>Review</p>
</td>
<td width="387">
<p>Review Required - will request for Station Manager to do a full review of every stock count submitted by stations<br /> Auto-Approve When No Queries - stock count will be automatically approved by Skylog if no queries where generated by system;</p>
</td>
</tr>
</table>

<h2>Sample of complete Station Count Category setup</h2>
[[File:SampleCategoryCount.png]]

<h1>Station Defaults</h1>

Station defaults are used whenever doing a mass transaction, for example mass import of items to station par level. The criteria in station defaults will be applied to all items imported.
<ol>
<li>In Stations screen (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 sock to be held a the station of item 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>days needed to get stock prepared for operation after it is receipted.</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>days needed to recycle stock from inbound flights to be ready for operations</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>based on Order frequency select</p>
</td>
</tr>
<tr>
<td width="217">
<p>% Loss at the Station</p>
</td>
<td width="81">
<p>0</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 sock count category (set up in previous chapter) to which items will be added</p>
</td>
</tr>
<tr>
<td width="217">
<p>Round Requisition Quantities?</p>
</td>
<td width="81">
<p>Yes</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>

<h1>Stock Items / Par Levels</h1>

Station Par levels refers to items station would be allowed to place orders for and receive stock. This can be done in a few ways: copy Par Levels from identical/similar station or do it one item at a time
<h2>Copy Par Level from existing station</h2>

<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 please find button Copy</li>
[[File:LocationOfCopyParLevelsButton.png]]

<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]]

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

</ol>

Station Index

2020-04-09T15:09:21Z

Arunas.milasius:

__TOC__

<h1>Summary</h1>

<h1>Create organization</h1>

Organization refers to company as a whole like Lufthansa or Gate Group, and contains Organization site locations under it in Skylog (e.g. Gate Group London T5). Organization defines company type and service it provides.
First, please check if Organization already exists in Skylog. You can find the list of all Organizations [[https://rsprod.skylogportal.com/Organization'''link''']]. If Organization already exists please move to next step.

If Organization does not exist, there are 2 ways to create an Organization: contact Global Administrator or raise support request. [[http://wiki.skylogportal.com/?title=Support_Index'''link''']]

<h1>Organization Sites</h1>

Organization sites determines address of the of a station, supplier or warehouse. These have to be set up if new station, supplier or warehouse needs to be added to Skylog and record does not exist.

Firstly Please check if a site is already created in skylog with same address and link to Same Organization. It is important not to duplicate organization sites entries if address assigned to organization already exists. For more please see link [[http://wiki.skylogportal.com/?title=OrganizationSite_Index'''link''']]

<h1>Stations</h1>

Station set up contains specification of stations operations (lead times, safety stocks etc.) and items (par levels) that it will have. Skylog alows advance ways to customize stations set up, from automatic stock count approvals, to RMA management.

<h2>Stations creation</h2>

You can create a new station by going to Reference Data/Airline Participants/Stations

[[File:CreateStationRef.png]]

Skylog allows advance customization of all stations. To deliver the most productive set up please consult guide below

[[File:StationSpec.png]]

<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 station address that is printed in invoices 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 airport it services. It is essential for enhanced forecasting and consumption calculations</p>
</td>
</tr>
<tr>
<td width="170">
<p>Service Type</p>
</td>
<td width="444">
<p>assign relevant station type</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 and forecast assigned to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Valid To</p>
</td>
<td width="444">
<p>date of station closure. Is not a mandatory field to be populated</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 provision of goods for the station (i.e. who will approve requisition requests, inventory reports, etc.)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="444">
<p>person to be assigned (from users register in Skylog) who will be responsible for stock counts. Selected person will be recipient of related notifications</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 with Skylog – if the station will raise requisitions and/or be expected to submit inventory reports then this setting should always be set as 'No'.</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 generated automatic requisitions after stock count, via schedule or even manually. If no, only manual orders will be allowed to be placed by station, more relevant 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. If the station wishes to see such temporary items on requisitions then this configuration flag should be set as 'Yes', otherwise, set as 'No'.</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 Skylog 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 Skylog. 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).</p>
</td>
</tr>
<tr>
<td width="170">
<p>Enforce RMA Qty</p>
</td>
<td width="444">
<p>if station is allowed to issue RMA for parts they haven't ordered from inbound flights etc. then No. If Yes, station will be allowed to return only stock qty that they counted in 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>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>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 intGL Cost Centre field links financial data with customer financial systems. for Catering units please select airport caterer supplies. For other operations like Lounges and Laundry Customer is to confirm which GL Code to be used in those exceptional cases. In case new GL Cost Centre require new set up please follow the link for guidance how to [[http://wiki.skylogportal.com/?title=Station_CostCentreCategoryIndex'''link''']].</p>
</td>
</tr>
</table>

<h1>Supply Source</h1>

Supply sources defines supplying warehouse and modes of transport assigned. It is possible for station to be supplied by multiple warehouses and this could be defined at the item level is Station Item / Par Level tables. Multiple modes of transport could be assigned for each station with different lead-times

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

<h2>Add Warehouse</h2>
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]]

<h2>Add Transport Methods</h2>

<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]]

<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 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:CompleteTransportSetup.png]]

<h1>Station Count Category</h1>
[File:CreateStationCountCategory.png]

Can be found under Daily Activities/Inventory Counts/Station Count Categories. Station count category defines which items, how often need to be counted by station. It also allows to set the tolerances to count variances for automatic query process as well as define the level of automation in count and approval process – some counts can be set up as auto accepted after they are submitted, useful feature for stations like lounges, with little turn over.
<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]]

<li>Fill the table. Fields are explained in table below with samples.</li>
</ol>
</li>

<table width="0">
<tr>
<td width="170">
<p><strong>Field</strong></p>
</td>
<td width="85">
<p><strong>Sample</strong></p>
</td>
<td width="387">
<p><strong>Description</strong></p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Category Description</p>
</td>
<td width="85">
<p>Full</p>
</td>
<td width="387">
<p>Description of the count. Station could have multiple counts with different parts under each, so name of the count is useful to avoid confusions</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Schedule Option</p>
</td>
<td width="85">
<p>Automatic Schedule</p>
</td>
<td width="387">
<p>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)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Automatic Schedule Options</p>
</td>
<td width="85">
<p>Specific Day/s of the Week</p>
</td>
<td width="387">
<p>can name days of the week or month for stock count to be automatically repeated</p>
</td>
</tr>
<tr>
<td width="170">
<p>Specific Day/s of the Week</p>
</td>
<td width="85"> </td>
<td width="387">
<p>tick/ select days when stock count should be triggered</p>
</td>
</tr>
<tr>
<td width="170">
<p>Weeks Between Counts</p>
</td>
<td width="85">
<p>1</p>
</td>
<td width="387">
<p>Nr of weeks in between counts</p>
</td>
</tr>
<tr>
<td width="170">
<p>Notify Days</p>
</td>
<td width="85">
<p>3</p>
</td>
<td width="387">
<p>Nr of days stock count will be generated before, and station will get a notification</p>
</td>
</tr>
<tr>
<td width="170">
<p>Next Count Generation Date</p>
</td>
<td width="85">
<p>September 28, 2019</p>
</td>
<td width="387">
<p>Select next/first stock count to be schedule for date</p>
</td>
</tr>
<tr>
<td width="170">
<p>Value Tolerance for Count Variances</p>
</td>
<td width="85"> </td>
<td width="387">
<p>not mandatory, select variances in value per line to tolerate as ok. Meaning if there is 100 GBP tolerance and discrepancy from expected sock count is 99, count will appear as ok. This could be changed later at the item level for exceptions</p>
</td>
</tr>
<tr>
<td width="170">
<p>% Quantity Tolerance for Count Variances</p>
</td>
<td width="85">
<p>10</p>
</td>
<td width="387">
<p>not mandatory, select variance in quantity % per line to be tolerated from expected count. Meaning if 5% discrepancy from expected stock count is allowed and will not appear as a query. Can be amended at the item level for exception items</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="85"> </td>
<td width="387">
<p>select person (out of assigned to this stations/organization site, that will be responsible for counts and will be receiving notifications related to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Floating Qty</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Float stock, is what is flown and/or kept in the kitchen. If selected yes, column will appear at the sock count to count both Backup stock and Float stock (back up stock is default and will always appear in stock count sheet)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Breakages</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will add a column for breakages to be filled by station during stock count.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Attach Count Sheet File When Notifying Station</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Advise to select Yes, that will have attached an excel file that when filled could be uploaded to stock count for submission. It is a good tool to avoid manual entries in the portal.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Consumption Trend Span (Days)</p>
</td>
<td width="85">
<p>180</p>
</td>
<td width="387">
<p>default value is 180, and if left blank it will generate value of 180 days.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Generate Automatic Requisitions Upon Count Approval</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if Yes, will post an option to generate automatic requisition after stock count is approved.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include All Items in Automatic Requisitions</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if yes, will include all active items in auto requisition (even if suggested order is 0)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Delay (Hours) For Automatic Requisition Generation</p>
</td>
<td width="85">
<p>0</p>
</td>
<td width="387"> </td>
</tr>
<tr>
<td width="170">
<p>Include All Station Par Levels In Counts</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will include all active items in stock count and phase out items that have nothing in transit and where counted previously.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Update Station Par Levels</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if new part is added to requisition, it will update station par levels</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Auto Approval Option</p>
</td>
<td width="85">
<p>Review</p>
</td>
<td width="387">
<p>Review Required - will request for Station Manager to do a full review of every stock count submitted by stations<br /> Auto-Approve When No Queries - stock count will be automatically approved by Skylog if no queries where generated by system;</p>
</td>
</tr>
</table>

<h2>Sample of complete Station Count Category setup</h2>
[[File:SampleCategoryCount.png]]

<h1>Station Defaults</h1>

Station defaults are used whenever doing a mass transaction, for example mass import of items to station par level. The criteria in station defaults will be applied to all items imported.
<ol>
<li>In Stations screen (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 sock to be held a the station of item 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>days needed to get stock prepared for operation after it is receipted.</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>days needed to recycle stock from inbound flights to be ready for operations</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>based on Order frequency select</p>
</td>
</tr>
<tr>
<td width="217">
<p>% Loss at the Station</p>
</td>
<td width="81">
<p>0</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 sock count category (set up in previous chapter) to which items will be added</p>
</td>
</tr>
<tr>
<td width="217">
<p>Round Requisition Quantities?</p>
</td>
<td width="81">
<p>Yes</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>

<h1>Stock Items / Par Levels</h1>

Station Par levels refers to items station would be allowed to place orders for and receive stock. This can be done in a few ways: copy Par Levels from identical/similar station or do it one item at a time
<h2>Copy Par Level from existing station</h2>

<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 please find button Copy</li>
[[File:LocationOfCopyParLevelsButton.png]]

<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]]

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

</ol>

Station Index

2020-04-08T13:50:11Z

Arunas.milasius:

__TOC__

<h1>Summary</h1>

<h1>Create organization</h1>

Organization refers to company as a whole like Lufthansa or Gate Group, and contains Organization site locations under it in Skylog (e.g. Gate Group London T5). Organization defines company type and service it provides.
First, please check if Organization already exists in Skylog. You can find the list of all Organizations [[https://rsprod.skylogportal.com/Organization'''link''']]. If Organization already exists please move to next step.

If Organization does not exist, there are 2 ways to create an Organization: contact Global Administrator or raise support request. [[http://wiki.skylogportal.com/?title=Support_Index'''link''']]

<h1>Organization Sites</h1>

Organization sites determines address of the of a station, supplier or warehouse. These have to be set up if new station, supplier or warehouse needs to be added to Skylog and record does not exist.

Firstly Please check if a site is already created in skylog with same address and link to Same Organization. It is important not to duplicate organization sites entries if address assigned to organization already exists. For more please see link [[http://wiki.skylogportal.com/?title=OrganizationSite_Index'''link''']]

<h1>Stations</h1>

Station set up contains specification of stations operations (lead times, safety stocks etc.) and items (par levels) that it will have. Skylog alows advance ways to customize stations set up, from automatic stock count approvals, to RMA management.

<h2>Stations creation</h2>

You can create a new station by going to Reference Data/Airline Participants/Stations

[[File:CreateStationRef.png]]

Skylog allows advance customization of all stations. To deliver the most productive set up please consult guide below

[[File:StationSpec.png]]

<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 station address that is printed in invoices 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 airport it services. It is essential for enhanced forecasting and consumption calculations</p>
</td>
</tr>
<tr>
<td width="170">
<p>Service Type</p>
</td>
<td width="444">
<p>assign relevant station type</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 and forecast assigned to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Valid To</p>
</td>
<td width="444">
<p>date of station closure. Is not a mandatory field to be populated</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 provision of goods for the station (i.e. who will approve requisition requests, inventory reports, etc.)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="444">
<p>person to be assigned (from users register in Skylog) who will be responsible for stock counts. Selected person will be recipient of related notifications</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 with Skylog – if the station will raise requisitions and/or be expected to submit inventory reports then this setting should always be set as 'No'.</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 generated automatic requisitions after stock count, via schedule or even manually. If no, only manual orders will be allowed to be placed by station, more relevant 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. If the station wishes to see such temporary items on requisitions then this configuration flag should be set as 'Yes', otherwise, set as 'No'.</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 Skylog 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 Skylog. 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).</p>
</td>
</tr>
<tr>
<td width="170">
<p>Enforce RMA Qty</p>
</td>
<td width="444">
<p>if station is allowed to issue RMA for parts they haven't ordered from inbound flights etc. then No. If Yes, station will be allowed to return only stock qty that they counted in 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>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>
</table>

<h1>Supply Source</h1>

Supply sources defines supplying warehouse and modes of transport assigned. It is possible for station to be supplied by multiple warehouses and this could be defined at the item level is Station Item / Par Level tables. Multiple modes of transport could be assigned for each station with different lead-times

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

<h2>Add Warehouse</h2>
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]]

<h2>Add Transport Methods</h2>

<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]]

<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 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:CompleteTransportSetup.png]]

<h1>Station Count Category</h1>
[File:CreateStationCountCategory.png]

Can be found under Daily Activities/Inventory Counts/Station Count Categories. Station count category defines which items, how often need to be counted by station. It also allows to set the tolerances to count variances for automatic query process as well as define the level of automation in count and approval process – some counts can be set up as auto accepted after they are submitted, useful feature for stations like lounges, with little turn over.
<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]]

<li>Fill the table. Fields are explained in table below with samples.</li>
</ol>
</li>

<table width="0">
<tr>
<td width="170">
<p><strong>Field</strong></p>
</td>
<td width="85">
<p><strong>Sample</strong></p>
</td>
<td width="387">
<p><strong>Description</strong></p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Category Description</p>
</td>
<td width="85">
<p>Full</p>
</td>
<td width="387">
<p>Description of the count. Station could have multiple counts with different parts under each, so name of the count is useful to avoid confusions</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Schedule Option</p>
</td>
<td width="85">
<p>Automatic Schedule</p>
</td>
<td width="387">
<p>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)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Automatic Schedule Options</p>
</td>
<td width="85">
<p>Specific Day/s of the Week</p>
</td>
<td width="387">
<p>can name days of the week or month for stock count to be automatically repeated</p>
</td>
</tr>
<tr>
<td width="170">
<p>Specific Day/s of the Week</p>
</td>
<td width="85"> </td>
<td width="387">
<p>tick/ select days when stock count should be triggered</p>
</td>
</tr>
<tr>
<td width="170">
<p>Weeks Between Counts</p>
</td>
<td width="85">
<p>1</p>
</td>
<td width="387">
<p>Nr of weeks in between counts</p>
</td>
</tr>
<tr>
<td width="170">
<p>Notify Days</p>
</td>
<td width="85">
<p>3</p>
</td>
<td width="387">
<p>Nr of days stock count will be generated before, and station will get a notification</p>
</td>
</tr>
<tr>
<td width="170">
<p>Next Count Generation Date</p>
</td>
<td width="85">
<p>September 28, 2019</p>
</td>
<td width="387">
<p>Select next/first stock count to be schedule for date</p>
</td>
</tr>
<tr>
<td width="170">
<p>Value Tolerance for Count Variances</p>
</td>
<td width="85"> </td>
<td width="387">
<p>not mandatory, select variances in value per line to tolerate as ok. Meaning if there is 100 GBP tolerance and discrepancy from expected sock count is 99, count will appear as ok. This could be changed later at the item level for exceptions</p>
</td>
</tr>
<tr>
<td width="170">
<p>% Quantity Tolerance for Count Variances</p>
</td>
<td width="85">
<p>10</p>
</td>
<td width="387">
<p>not mandatory, select variance in quantity % per line to be tolerated from expected count. Meaning if 5% discrepancy from expected stock count is allowed and will not appear as a query. Can be amended at the item level for exception items</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="85"> </td>
<td width="387">
<p>select person (out of assigned to this stations/organization site, that will be responsible for counts and will be receiving notifications related to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Floating Qty</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Float stock, is what is flown and/or kept in the kitchen. If selected yes, column will appear at the sock count to count both Backup stock and Float stock (back up stock is default and will always appear in stock count sheet)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Breakages</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will add a column for breakages to be filled by station during stock count.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Attach Count Sheet File When Notifying Station</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Advise to select Yes, that will have attached an excel file that when filled could be uploaded to stock count for submission. It is a good tool to avoid manual entries in the portal.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Consumption Trend Span (Days)</p>
</td>
<td width="85">
<p>180</p>
</td>
<td width="387">
<p>default value is 180, and if left blank it will generate value of 180 days.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Generate Automatic Requisitions Upon Count Approval</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if Yes, will post an option to generate automatic requisition after stock count is approved.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include All Items in Automatic Requisitions</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if yes, will include all active items in auto requisition (even if suggested order is 0)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Delay (Hours) For Automatic Requisition Generation</p>
</td>
<td width="85">
<p>0</p>
</td>
<td width="387"> </td>
</tr>
<tr>
<td width="170">
<p>Include All Station Par Levels In Counts</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will include all active items in stock count and phase out items that have nothing in transit and where counted previously.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Update Station Par Levels</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if new part is added to requisition, it will update station par levels</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Auto Approval Option</p>
</td>
<td width="85">
<p>Review</p>
</td>
<td width="387">
<p>Review Required - will request for Station Manager to do a full review of every stock count submitted by stations<br /> Auto-Approve When No Queries - stock count will be automatically approved by Skylog if no queries where generated by system;</p>
</td>
</tr>
</table>

<h2>Sample of complete Station Count Category setup</h2>
[[File:SampleCategoryCount.png]]

<h1>Station Defaults</h1>

Station defaults are used whenever doing a mass transaction, for example mass import of items to station par level. The criteria in station defaults will be applied to all items imported.
<ol>
<li>In Stations screen (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 sock to be held a the station of item 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>days needed to get stock prepared for operation after it is receipted.</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>days needed to recycle stock from inbound flights to be ready for operations</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>based on Order frequency select</p>
</td>
</tr>
<tr>
<td width="217">
<p>% Loss at the Station</p>
</td>
<td width="81">
<p>0</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 sock count category (set up in previous chapter) to which items will be added</p>
</td>
</tr>
<tr>
<td width="217">
<p>Round Requisition Quantities?</p>
</td>
<td width="81">
<p>Yes</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>

<h1>Stock Items / Par Levels</h1>

Station Par levels refers to items station would be allowed to place orders for and receive stock. This can be done in a few ways: copy Par Levels from identical/similar station or do it one item at a time
<h2>Copy Par Level from existing station</h2>

<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 please find button Copy</li>
[[File:LocationOfCopyParLevelsButton.png]]

<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]]

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

</ol>

Station Index

2020-04-08T13:31:14Z

Arunas.milasius:

__TOC__

<h1>Summary</h1>

<h1>Create organization</h1>

Organization refers to company as a whole like Lufthansa or Gate Group, and contains Organization site locations under it in Skylog (e.g. Gate Group London T5). Organization defines company type and service it provides.
First, please check if Organization already exists in Skylog. You can find the list of all Organizations [[https://rsprod.skylogportal.com/Organization'''link''']]. If Organization already exists please move to next step.

If Organization does not exist, there are 2 ways to create an Organization: contact Global Administrator or raise support request. [[http://wiki.skylogportal.com/?title=Organization_Index'link']]

<h1>Organization Sites</h1>

Organization sites determines address of the of a station, supplier or warehouse. These have to be set up if new station, supplier or warehouse needs to be added to Skylog and record does not exist.

Firstly Please check if a site is already created in skylog with same address and link to Same Organization. It is important not to duplicate organization sites entries if address assigned to organization already exists. For more please see link [[how to create organization sites]]

<h1>Stations</h1>

Station set up contains specification of stations operations (lead times, safety stocks etc.) and items (par levels) that it will have. Skylog alows advance ways to customize stations set up, from automatic stock count approvals, to RMA management.

<h2>Stations creation</h2>

You can create a new station by going to Reference Data/Airline Participants/Stations

[[File:CreateStationRef.png]]

Skylog allows advance customization of all stations. To deliver the most productive set up please consult guide below

[[File:StationSpec.png]]

<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 station address that is printed in invoices 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 airport it services. It is essential for enhanced forecasting and consumption calculations</p>
</td>
</tr>
<tr>
<td width="170">
<p>Service Type</p>
</td>
<td width="444">
<p>assign relevant station type</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 and forecast assigned to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Valid To</p>
</td>
<td width="444">
<p>date of station closure. Is not a mandatory field to be populated</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 provision of goods for the station (i.e. who will approve requisition requests, inventory reports, etc.)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="444">
<p>person to be assigned (from users register in Skylog) who will be responsible for stock counts. Selected person will be recipient of related notifications</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 with Skylog – if the station will raise requisitions and/or be expected to submit inventory reports then this setting should always be set as 'No'.</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 generated automatic requisitions after stock count, via schedule or even manually. If no, only manual orders will be allowed to be placed by station, more relevant 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. If the station wishes to see such temporary items on requisitions then this configuration flag should be set as 'Yes', otherwise, set as 'No'.</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 Skylog 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 Skylog. 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).</p>
</td>
</tr>
<tr>
<td width="170">
<p>Enforce RMA Qty</p>
</td>
<td width="444">
<p>if station is allowed to issue RMA for parts they haven't ordered from inbound flights etc. then No. If Yes, station will be allowed to return only stock qty that they counted in 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>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>
</table>

<h1>Supply Source</h1>

Supply sources defines supplying warehouse and modes of transport assigned. It is possible for station to be supplied by multiple warehouses and this could be defined at the item level is Station Item / Par Level tables. Multiple modes of transport could be assigned for each station with different lead-times

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

<h2>Add Warehouse</h2>
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]]

<h2>Add Transport Methods</h2>

<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]]

<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 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:CompleteTransportSetup.png]]

<h1>Station Count Category</h1>
[File:CreateStationCountCategory.png]

Can be found under Daily Activities/Inventory Counts/Station Count Categories. Station count category defines which items, how often need to be counted by station. It also allows to set the tolerances to count variances for automatic query process as well as define the level of automation in count and approval process – some counts can be set up as auto accepted after they are submitted, useful feature for stations like lounges, with little turn over.
<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]]

<li>Fill the table. Fields are explained in table below with samples.</li>
</ol>
</li>

<table width="0">
<tr>
<td width="170">
<p><strong>Field</strong></p>
</td>
<td width="85">
<p><strong>Sample</strong></p>
</td>
<td width="387">
<p><strong>Description</strong></p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Category Description</p>
</td>
<td width="85">
<p>Full</p>
</td>
<td width="387">
<p>Description of the count. Station could have multiple counts with different parts under each, so name of the count is useful to avoid confusions</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Schedule Option</p>
</td>
<td width="85">
<p>Automatic Schedule</p>
</td>
<td width="387">
<p>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)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Automatic Schedule Options</p>
</td>
<td width="85">
<p>Specific Day/s of the Week</p>
</td>
<td width="387">
<p>can name days of the week or month for stock count to be automatically repeated</p>
</td>
</tr>
<tr>
<td width="170">
<p>Specific Day/s of the Week</p>
</td>
<td width="85"> </td>
<td width="387">
<p>tick/ select days when stock count should be triggered</p>
</td>
</tr>
<tr>
<td width="170">
<p>Weeks Between Counts</p>
</td>
<td width="85">
<p>1</p>
</td>
<td width="387">
<p>Nr of weeks in between counts</p>
</td>
</tr>
<tr>
<td width="170">
<p>Notify Days</p>
</td>
<td width="85">
<p>3</p>
</td>
<td width="387">
<p>Nr of days stock count will be generated before, and station will get a notification</p>
</td>
</tr>
<tr>
<td width="170">
<p>Next Count Generation Date</p>
</td>
<td width="85">
<p>September 28, 2019</p>
</td>
<td width="387">
<p>Select next/first stock count to be schedule for date</p>
</td>
</tr>
<tr>
<td width="170">
<p>Value Tolerance for Count Variances</p>
</td>
<td width="85"> </td>
<td width="387">
<p>not mandatory, select variances in value per line to tolerate as ok. Meaning if there is 100 GBP tolerance and discrepancy from expected sock count is 99, count will appear as ok. This could be changed later at the item level for exceptions</p>
</td>
</tr>
<tr>
<td width="170">
<p>% Quantity Tolerance for Count Variances</p>
</td>
<td width="85">
<p>10</p>
</td>
<td width="387">
<p>not mandatory, select variance in quantity % per line to be tolerated from expected count. Meaning if 5% discrepancy from expected stock count is allowed and will not appear as a query. Can be amended at the item level for exception items</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="85"> </td>
<td width="387">
<p>select person (out of assigned to this stations/organization site, that will be responsible for counts and will be receiving notifications related to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Floating Qty</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Float stock, is what is flown and/or kept in the kitchen. If selected yes, column will appear at the sock count to count both Backup stock and Float stock (back up stock is default and will always appear in stock count sheet)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Breakages</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will add a column for breakages to be filled by station during stock count.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Attach Count Sheet File When Notifying Station</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Advise to select Yes, that will have attached an excel file that when filled could be uploaded to stock count for submission. It is a good tool to avoid manual entries in the portal.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Consumption Trend Span (Days)</p>
</td>
<td width="85">
<p>180</p>
</td>
<td width="387">
<p>default value is 180, and if left blank it will generate value of 180 days.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Generate Automatic Requisitions Upon Count Approval</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if Yes, will post an option to generate automatic requisition after stock count is approved.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include All Items in Automatic Requisitions</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if yes, will include all active items in auto requisition (even if suggested order is 0)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Delay (Hours) For Automatic Requisition Generation</p>
</td>
<td width="85">
<p>0</p>
</td>
<td width="387"> </td>
</tr>
<tr>
<td width="170">
<p>Include All Station Par Levels In Counts</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will include all active items in stock count and phase out items that have nothing in transit and where counted previously.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Update Station Par Levels</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if new part is added to requisition, it will update station par levels</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Auto Approval Option</p>
</td>
<td width="85">
<p>Review</p>
</td>
<td width="387">
<p>Review Required - will request for Station Manager to do a full review of every stock count submitted by stations<br /> Auto-Approve When No Queries - stock count will be automatically approved by Skylog if no queries where generated by system;</p>
</td>
</tr>
</table>

<h2>Sample of complete Station Count Category setup</h2>
[[File:SampleCategoryCount.png]]

<h1>Station Defaults</h1>

Station defaults are used whenever doing a mass transaction, for example mass import of items to station par level. The criteria in station defaults will be applied to all items imported.
<ol>
<li>In Stations screen (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 sock to be held a the station of item 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>days needed to get stock prepared for operation after it is receipted.</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>days needed to recycle stock from inbound flights to be ready for operations</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>based on Order frequency select</p>
</td>
</tr>
<tr>
<td width="217">
<p>% Loss at the Station</p>
</td>
<td width="81">
<p>0</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 sock count category (set up in previous chapter) to which items will be added</p>
</td>
</tr>
<tr>
<td width="217">
<p>Round Requisition Quantities?</p>
</td>
<td width="81">
<p>Yes</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>

<h1>Stock Items / Par Levels</h1>

Station Par levels refers to items station would be allowed to place orders for and receive stock. This can be done in a few ways: copy Par Levels from identical/similar station or do it one item at a time
<h2>Copy Par Level from existing station</h2>

<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 please find button Copy</li>
[[File:LocationOfCopyParLevelsButton.png]]

<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]]

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

</ol>

AirlineSupplier Index

2020-04-08T10:49:24Z

Arunas.milasius: Replaced content with "__TOC__ <h1>Summary</h1> <h1>Create organization</h1> Organization refers to company as a whole like Lufthansa or Gate Group, and contains Organization site locations..."

Station Index

2020-04-08T09:33:35Z

Arunas.milasius: Created page with "__TOC__ <h1>Summary</h1> <h1>Create organization</h1> Organization refers to company as a whole like Lufthansa or Gate Group, and contains Organization site locations und..."

__TOC__

<h1>Summary</h1>

<h1>Create organization</h1>

Organization refers to company as a whole like Lufthansa or Gate Group, and contains Organization site locations under it in Skylog (e.g. Gate Group London T5). Organization defines company type and service it provides.
First, please check if Organization already exists in Skylog. You can find the list of all Organizations [[https://rsprod.skylogportal.com/Organization'''link''']]. If Organization already exists please move to next step.

If Organization does not exist, there are 2 ways to create an Organization: contact Global Administrator or raise support request. [['link']]

<h1>Organization Sites</h1>

Organization sites determines address of the of a station, supplier or warehouse. These have to be set up if new station, supplier or warehouse needs to be added to Skylog and record does not exist.

Firstly Please check if a site is already created in skylog with same address and link to Same Organization. It is important not to duplicate organization sites entries if address assigned to organization already exists. For more please see link [[how to create organization sites]]

<h1>Stations</h1>

Station set up contains specification of stations operations (lead times, safety stocks etc.) and items (par levels) that it will have. Skylog alows advance ways to customize stations set up, from automatic stock count approvals, to RMA management.

<h2>Stations creation</h2>

You can create a new station by going to Reference Data/Airline Participants/Stations

[[File:CreateStationRef.png]]

Skylog allows advance customization of all stations. To deliver the most productive set up please consult guide below

[[File:StationSpec.png]]

<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 station address that is printed in invoices 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 airport it services. It is essential for enhanced forecasting and consumption calculations</p>
</td>
</tr>
<tr>
<td width="170">
<p>Service Type</p>
</td>
<td width="444">
<p>assign relevant station type</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 and forecast assigned to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Valid To</p>
</td>
<td width="444">
<p>date of station closure. Is not a mandatory field to be populated</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 provision of goods for the station (i.e. who will approve requisition requests, inventory reports, etc.)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="444">
<p>person to be assigned (from users register in Skylog) who will be responsible for stock counts. Selected person will be recipient of related notifications</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 with Skylog – if the station will raise requisitions and/or be expected to submit inventory reports then this setting should always be set as 'No'.</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 generated automatic requisitions after stock count, via schedule or even manually. If no, only manual orders will be allowed to be placed by station, more relevant 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. If the station wishes to see such temporary items on requisitions then this configuration flag should be set as 'Yes', otherwise, set as 'No'.</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 Skylog 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 Skylog. 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).</p>
</td>
</tr>
<tr>
<td width="170">
<p>Enforce RMA Qty</p>
</td>
<td width="444">
<p>if station is allowed to issue RMA for parts they haven't ordered from inbound flights etc. then No. If Yes, station will be allowed to return only stock qty that they counted in 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>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>
</table>

<h1>Supply Source</h1>

Supply sources defines supplying warehouse and modes of transport assigned. It is possible for station to be supplied by multiple warehouses and this could be defined at the item level is Station Item / Par Level tables. Multiple modes of transport could be assigned for each station with different lead-times

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

<h2>Add Warehouse</h2>
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]]

<h2>Add Transport Methods</h2>

<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]]

<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 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:CompleteTransportSetup.png]]

<h1>Station Count Category</h1>
[File:CreateStationCountCategory.png]

Can be found under Daily Activities/Inventory Counts/Station Count Categories. Station count category defines which items, how often need to be counted by station. It also allows to set the tolerances to count variances for automatic query process as well as define the level of automation in count and approval process – some counts can be set up as auto accepted after they are submitted, useful feature for stations like lounges, with little turn over.
<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]]

<li>Fill the table. Fields are explained in table below with samples.</li>
</ol>
</li>

<table width="0">
<tr>
<td width="170">
<p><strong>Field</strong></p>
</td>
<td width="85">
<p><strong>Sample</strong></p>
</td>
<td width="387">
<p><strong>Description</strong></p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Category Description</p>
</td>
<td width="85">
<p>Full</p>
</td>
<td width="387">
<p>Description of the count. Station could have multiple counts with different parts under each, so name of the count is useful to avoid confusions</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Schedule Option</p>
</td>
<td width="85">
<p>Automatic Schedule</p>
</td>
<td width="387">
<p>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)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Automatic Schedule Options</p>
</td>
<td width="85">
<p>Specific Day/s of the Week</p>
</td>
<td width="387">
<p>can name days of the week or month for stock count to be automatically repeated</p>
</td>
</tr>
<tr>
<td width="170">
<p>Specific Day/s of the Week</p>
</td>
<td width="85"> </td>
<td width="387">
<p>tick/ select days when stock count should be triggered</p>
</td>
</tr>
<tr>
<td width="170">
<p>Weeks Between Counts</p>
</td>
<td width="85">
<p>1</p>
</td>
<td width="387">
<p>Nr of weeks in between counts</p>
</td>
</tr>
<tr>
<td width="170">
<p>Notify Days</p>
</td>
<td width="85">
<p>3</p>
</td>
<td width="387">
<p>Nr of days stock count will be generated before, and station will get a notification</p>
</td>
</tr>
<tr>
<td width="170">
<p>Next Count Generation Date</p>
</td>
<td width="85">
<p>September 28, 2019</p>
</td>
<td width="387">
<p>Select next/first stock count to be schedule for date</p>
</td>
</tr>
<tr>
<td width="170">
<p>Value Tolerance for Count Variances</p>
</td>
<td width="85"> </td>
<td width="387">
<p>not mandatory, select variances in value per line to tolerate as ok. Meaning if there is 100 GBP tolerance and discrepancy from expected sock count is 99, count will appear as ok. This could be changed later at the item level for exceptions</p>
</td>
</tr>
<tr>
<td width="170">
<p>% Quantity Tolerance for Count Variances</p>
</td>
<td width="85">
<p>10</p>
</td>
<td width="387">
<p>not mandatory, select variance in quantity % per line to be tolerated from expected count. Meaning if 5% discrepancy from expected stock count is allowed and will not appear as a query. Can be amended at the item level for exception items</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="85"> </td>
<td width="387">
<p>select person (out of assigned to this stations/organization site, that will be responsible for counts and will be receiving notifications related to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Floating Qty</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Float stock, is what is flown and/or kept in the kitchen. If selected yes, column will appear at the sock count to count both Backup stock and Float stock (back up stock is default and will always appear in stock count sheet)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Breakages</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will add a column for breakages to be filled by station during stock count.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Attach Count Sheet File When Notifying Station</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Advise to select Yes, that will have attached an excel file that when filled could be uploaded to stock count for submission. It is a good tool to avoid manual entries in the portal.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Consumption Trend Span (Days)</p>
</td>
<td width="85">
<p>180</p>
</td>
<td width="387">
<p>default value is 180, and if left blank it will generate value of 180 days.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Generate Automatic Requisitions Upon Count Approval</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if Yes, will post an option to generate automatic requisition after stock count is approved.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include All Items in Automatic Requisitions</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if yes, will include all active items in auto requisition (even if suggested order is 0)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Delay (Hours) For Automatic Requisition Generation</p>
</td>
<td width="85">
<p>0</p>
</td>
<td width="387"> </td>
</tr>
<tr>
<td width="170">
<p>Include All Station Par Levels In Counts</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will include all active items in stock count and phase out items that have nothing in transit and where counted previously.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Update Station Par Levels</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if new part is added to requisition, it will update station par levels</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Auto Approval Option</p>
</td>
<td width="85">
<p>Review</p>
</td>
<td width="387">
<p>Review Required - will request for Station Manager to do a full review of every stock count submitted by stations<br /> Auto-Approve When No Queries - stock count will be automatically approved by Skylog if no queries where generated by system;</p>
</td>
</tr>
</table>

<h2>Sample of complete Station Count Category setup</h2>
[[File:SampleCategoryCount.png]]

<h1>Station Defaults</h1>

Station defaults are used whenever doing a mass transaction, for example mass import of items to station par level. The criteria in station defaults will be applied to all items imported.
<ol>
<li>In Stations screen (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 sock to be held a the station of item 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>days needed to get stock prepared for operation after it is receipted.</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>days needed to recycle stock from inbound flights to be ready for operations</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>based on Order frequency select</p>
</td>
</tr>
<tr>
<td width="217">
<p>% Loss at the Station</p>
</td>
<td width="81">
<p>0</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 sock count category (set up in previous chapter) to which items will be added</p>
</td>
</tr>
<tr>
<td width="217">
<p>Round Requisition Quantities?</p>
</td>
<td width="81">
<p>Yes</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>

<h1>Stock Items / Par Levels</h1>

Station Par levels refers to items station would be allowed to place orders for and receive stock. This can be done in a few ways: copy Par Levels from identical/similar station or do it one item at a time
<h2>Copy Par Level from existing station</h2>

<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 please find button Copy</li>
[[File:LocationOfCopyParLevelsButton.png]]

<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]]

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

</ol>

AirlineSupplier Index

2020-04-08T09:27:25Z

Arunas.milasius:

__TOC__

<h1>Summary</h1>

<h1>Create organization</h1>

Organization refers to company as a whole like Lufthansa or Gate Group, and contains Organization site locations under it in Skylog (e.g. Gate Group London T5). Organization defines company type and service it provides.
First, please check if Organization already exists in Skylog. You can find the list of all Organizations [[https://rsprod.skylogportal.com/Organization'''link''']]. If Organization already exists please move to next step.

If Organization does not exist, there are 2 ways to create an Organization: contact Global Administrator or raise support request. [['link']]

<h1>Organization Sites</h1>

Organization sites determines address of the of a station, supplier or warehouse. These have to be set up if new station, supplier or warehouse needs to be added to Skylog and record does not exist.

Firstly Please check if a site is already created in skylog with same address and link to Same Organization. It is important not to duplicate organization sites entries if address assigned to organization already exists. For more please see link [[how to create organization sites]]

<h1>Stations</h1>

Station set up contains specification of stations operations (lead times, safety stocks etc.) and items (par levels) that it will have. Skylog alows advance ways to customize stations set up, from automatic stock count approvals, to RMA management.

<h2>Stations creation</h2>

You can create a new station by going to Reference Data/Airline Participants/Stations

[[File:CreateStationRef.png]]

Skylog allows advance customization of all stations. To deliver the most productive set up please consult guide below

[[File:StationSpec.png]]

<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 station address that is printed in invoices 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 airport it services. It is essential for enhanced forecasting and consumption calculations</p>
</td>
</tr>
<tr>
<td width="170">
<p>Service Type</p>
</td>
<td width="444">
<p>assign relevant station type</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 and forecast assigned to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Valid To</p>
</td>
<td width="444">
<p>date of station closure. Is not a mandatory field to be populated</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 provision of goods for the station (i.e. who will approve requisition requests, inventory reports, etc.)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="444">
<p>person to be assigned (from users register in Skylog) who will be responsible for stock counts. Selected person will be recipient of related notifications</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 with Skylog – if the station will raise requisitions and/or be expected to submit inventory reports then this setting should always be set as 'No'.</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 generated automatic requisitions after stock count, via schedule or even manually. If no, only manual orders will be allowed to be placed by station, more relevant 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. If the station wishes to see such temporary items on requisitions then this configuration flag should be set as 'Yes', otherwise, set as 'No'.</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 Skylog 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 Skylog. 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).</p>
</td>
</tr>
<tr>
<td width="170">
<p>Enforce RMA Qty</p>
</td>
<td width="444">
<p>if station is allowed to issue RMA for parts they haven't ordered from inbound flights etc. then No. If Yes, station will be allowed to return only stock qty that they counted in 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>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>
</table>

<h1>Supply Source</h1>

Supply sources defines supplying warehouse and modes of transport assigned. It is possible for station to be supplied by multiple warehouses and this could be defined at the item level is Station Item / Par Level tables. Multiple modes of transport could be assigned for each station with different lead-times

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

<h2>Add Warehouse</h2>
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]]

<h2>Add Transport Methods</h2>

<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]]

<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 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:CompleteTransportSetup.png]]

<h1>Station Count Category</h1>
[File:CreateStationCountCategory.png]

Can be found under Daily Activities/Inventory Counts/Station Count Categories. Station count category defines which items, how often need to be counted by station. It also allows to set the tolerances to count variances for automatic query process as well as define the level of automation in count and approval process – some counts can be set up as auto accepted after they are submitted, useful feature for stations like lounges, with little turn over.
<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]]

<li>Fill the table. Fields are explained in table below with samples.</li>
</ol>
</li>

<table width="0">
<tr>
<td width="170">
<p><strong>Field</strong></p>
</td>
<td width="85">
<p><strong>Sample</strong></p>
</td>
<td width="387">
<p><strong>Description</strong></p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Category Description</p>
</td>
<td width="85">
<p>Full</p>
</td>
<td width="387">
<p>Description of the count. Station could have multiple counts with different parts under each, so name of the count is useful to avoid confusions</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Schedule Option</p>
</td>
<td width="85">
<p>Automatic Schedule</p>
</td>
<td width="387">
<p>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)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Automatic Schedule Options</p>
</td>
<td width="85">
<p>Specific Day/s of the Week</p>
</td>
<td width="387">
<p>can name days of the week or month for stock count to be automatically repeated</p>
</td>
</tr>
<tr>
<td width="170">
<p>Specific Day/s of the Week</p>
</td>
<td width="85"> </td>
<td width="387">
<p>tick/ select days when stock count should be triggered</p>
</td>
</tr>
<tr>
<td width="170">
<p>Weeks Between Counts</p>
</td>
<td width="85">
<p>1</p>
</td>
<td width="387">
<p>Nr of weeks in between counts</p>
</td>
</tr>
<tr>
<td width="170">
<p>Notify Days</p>
</td>
<td width="85">
<p>3</p>
</td>
<td width="387">
<p>Nr of days stock count will be generated before, and station will get a notification</p>
</td>
</tr>
<tr>
<td width="170">
<p>Next Count Generation Date</p>
</td>
<td width="85">
<p>September 28, 2019</p>
</td>
<td width="387">
<p>Select next/first stock count to be schedule for date</p>
</td>
</tr>
<tr>
<td width="170">
<p>Value Tolerance for Count Variances</p>
</td>
<td width="85"> </td>
<td width="387">
<p>not mandatory, select variances in value per line to tolerate as ok. Meaning if there is 100 GBP tolerance and discrepancy from expected sock count is 99, count will appear as ok. This could be changed later at the item level for exceptions</p>
</td>
</tr>
<tr>
<td width="170">
<p>% Quantity Tolerance for Count Variances</p>
</td>
<td width="85">
<p>10</p>
</td>
<td width="387">
<p>not mandatory, select variance in quantity % per line to be tolerated from expected count. Meaning if 5% discrepancy from expected stock count is allowed and will not appear as a query. Can be amended at the item level for exception items</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="85"> </td>
<td width="387">
<p>select person (out of assigned to this stations/organization site, that will be responsible for counts and will be receiving notifications related to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Floating Qty</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Float stock, is what is flown and/or kept in the kitchen. If selected yes, column will appear at the sock count to count both Backup stock and Float stock (back up stock is default and will always appear in stock count sheet)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Breakages</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will add a column for breakages to be filled by station during stock count.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Attach Count Sheet File When Notifying Station</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Advise to select Yes, that will have attached an excel file that when filled could be uploaded to stock count for submission. It is a good tool to avoid manual entries in the portal.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Consumption Trend Span (Days)</p>
</td>
<td width="85">
<p>180</p>
</td>
<td width="387">
<p>default value is 180, and if left blank it will generate value of 180 days.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Generate Automatic Requisitions Upon Count Approval</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if Yes, will post an option to generate automatic requisition after stock count is approved.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include All Items in Automatic Requisitions</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if yes, will include all active items in auto requisition (even if suggested order is 0)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Delay (Hours) For Automatic Requisition Generation</p>
</td>
<td width="85">
<p>0</p>
</td>
<td width="387"> </td>
</tr>
<tr>
<td width="170">
<p>Include All Station Par Levels In Counts</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will include all active items in stock count and phase out items that have nothing in transit and where counted previously.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Update Station Par Levels</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if new part is added to requisition, it will update station par levels</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Auto Approval Option</p>
</td>
<td width="85">
<p>Review</p>
</td>
<td width="387">
<p>Review Required - will request for Station Manager to do a full review of every stock count submitted by stations<br /> Auto-Approve When No Queries - stock count will be automatically approved by Skylog if no queries where generated by system;</p>
</td>
</tr>
</table>

<h2>Sample of complete Station Count Category setup</h2>
[[File:SampleCategoryCount.png]]

<h1>Station Defaults</h1>

Station defaults are used whenever doing a mass transaction, for example mass import of items to station par level. The criteria in station defaults will be applied to all items imported.
<ol>
<li>In Stations screen (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 sock to be held a the station of item 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>days needed to get stock prepared for operation after it is receipted.</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>days needed to recycle stock from inbound flights to be ready for operations</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>based on Order frequency select</p>
</td>
</tr>
<tr>
<td width="217">
<p>% Loss at the Station</p>
</td>
<td width="81">
<p>0</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 sock count category (set up in previous chapter) to which items will be added</p>
</td>
</tr>
<tr>
<td width="217">
<p>Round Requisition Quantities?</p>
</td>
<td width="81">
<p>Yes</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>

<h1>Stock Items / Par Levels</h1>

Station Par levels refers to items station would be allowed to place orders for and receive stock. This can be done in a few ways: copy Par Levels from identical/similar station or do it one item at a time
<h2>Copy Par Level from existing station</h2>

<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 please find button Copy</li>
[[File:LocationOfCopyParLevelsButton.png]]

<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]]

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

</ol>

AirlineSupplier Index

2020-04-08T09:26:02Z

Arunas.milasius:

__TOC__

<h1>Summary</h1>

<h1>Create organization</h1>

Organization refers to company as a whole like Lufthansa or Gate Group, and contains Organization site locations under it in Skylog (e.g. Gate Group London T5). Organization defines company type and service it provides.
First, please check if Organization already exists in Skylog. You can find the list of all Organizations [[https://rsprod.skylogportal.com/Organization'''link''']]. If Organization already exists please move to next step.

If Organization does not exist, there are 2 ways to create an Organization: contact Global Administrator or raise support request. [['link']]

<h1>Organization Sites</h1>

Organization sites determines address of the of a station, supplier or warehouse. These have to be set up if new station, supplier or warehouse needs to be added to Skylog and record does not exist.

Firstly Please check if a site is already created in skylog with same address and link to Same Organization. It is important not to duplicate organization sites entries if address assigned to organization already exists. For more please see link [[how to create organization sites]]

<h1>Stations</h1>

Station set up contains specification of stations operations (lead times, safety stocks etc.) and items (par levels) that it will have. Skylog alows advance ways to customize stations set up, from automatic stock count approvals, to RMA management.

<h2>Stations creation</h2>

You can create a new station by going to Reference Data/Airline Participants/Stations

[[File:CreateStationRef.png]]

Skylog allows advance customization of all stations. To deliver the most productive set up please consult guide below

[[File:StationSpec.png]]

<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 station address that is printed in invoices 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 airport it services. It is essential for enhanced forecasting and consumption calculations</p>
</td>
</tr>
<tr>
<td width="170">
<p>Service Type</p>
</td>
<td width="444">
<p>assign relevant station type</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 and forecast assigned to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Valid To</p>
</td>
<td width="444">
<p>date of station closure. Is not a mandatory field to be populated</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 provision of goods for the station (i.e. who will approve requisition requests, inventory reports, etc.)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="444">
<p>person to be assigned (from users register in Skylog) who will be responsible for stock counts. Selected person will be recipient of related notifications</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 with Skylog – if the station will raise requisitions and/or be expected to submit inventory reports then this setting should always be set as 'No'.</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 generated automatic requisitions after stock count, via schedule or even manually. If no, only manual orders will be allowed to be placed by station, more relevant 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. If the station wishes to see such temporary items on requisitions then this configuration flag should be set as 'Yes', otherwise, set as 'No'.</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 Skylog 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 Skylog. 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).</p>
</td>
</tr>
<tr>
<td width="170">
<p>Enforce RMA Qty</p>
</td>
<td width="444">
<p>if station is allowed to issue RMA for parts they haven't ordered from inbound flights etc. then No. If Yes, station will be allowed to return only stock qty that they counted in 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>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>
</table>

<h1>Supply Source</h1>

Supply sources defines supplying warehouse and modes of transport assigned. It is possible for station to be supplied by multiple warehouses and this could be defined at the item level is Station Item / Par Level tables. Multiple modes of transport could be assigned for each station with different lead-times

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

<h2>Add Warehouse</h2>
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]]

<h2>Add Transport Methods</h2>

<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]]

<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 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:CompleteTransportSetup.png]]

<h1>Station Count Category</h1>
[File:CreateStationCountCategory.png]

Can be found under Daily Activities/Inventory Counts/Station Count Categories. Station count category defines which items, how often need to be counted by station. It also allows to set the tolerances to count variances for automatic query process as well as define the level of automation in count and approval process – some counts can be set up as auto accepted after they are submitted, useful feature for stations like lounges, with little turn over.
<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]]

<li>Fill the table. Fields are explained in table below with samples.</li>
</ol>
</li>

<table width="0">
<tr>
<td width="170">
<p><strong>Field</strong></p>
</td>
<td width="85">
<p><strong>Sample</strong></p>
</td>
<td width="387">
<p><strong>Description</strong></p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Category Description</p>
</td>
<td width="85">
<p>Full</p>
</td>
<td width="387">
<p>Description of the count. Station could have multiple counts with different parts under each, so name of the count is useful to avoid confusions</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Schedule Option</p>
</td>
<td width="85">
<p>Automatic Schedule</p>
</td>
<td width="387">
<p>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)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Automatic Schedule Options</p>
</td>
<td width="85">
<p>Specific Day/s of the Week</p>
</td>
<td width="387">
<p>can name days of the week or month for stock count to be automatically repeated</p>
</td>
</tr>
<tr>
<td width="170">
<p>Specific Day/s of the Week</p>
</td>
<td width="85"> </td>
<td width="387">
<p>tick/ select days when stock count should be triggered</p>
</td>
</tr>
<tr>
<td width="170">
<p>Weeks Between Counts</p>
</td>
<td width="85">
<p>1</p>
</td>
<td width="387">
<p>Nr of weeks in between counts</p>
</td>
</tr>
<tr>
<td width="170">
<p>Notify Days</p>
</td>
<td width="85">
<p>3</p>
</td>
<td width="387">
<p>Nr of days stock count will be generated before, and station will get a notification</p>
</td>
</tr>
<tr>
<td width="170">
<p>Next Count Generation Date</p>
</td>
<td width="85">
<p>September 28, 2019</p>
</td>
<td width="387">
<p>Select next/first stock count to be schedule for date</p>
</td>
</tr>
<tr>
<td width="170">
<p>Value Tolerance for Count Variances</p>
</td>
<td width="85"> </td>
<td width="387">
<p>not mandatory, select variances in value per line to tolerate as ok. Meaning if there is 100 GBP tolerance and discrepancy from expected sock count is 99, count will appear as ok. This could be changed later at the item level for exceptions</p>
</td>
</tr>
<tr>
<td width="170">
<p>% Quantity Tolerance for Count Variances</p>
</td>
<td width="85">
<p>10</p>
</td>
<td width="387">
<p>not mandatory, select variance in quantity % per line to be tolerated from expected count. Meaning if 5% discrepancy from expected stock count is allowed and will not appear as a query. Can be amended at the item level for exception items</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="85"> </td>
<td width="387">
<p>select person (out of assigned to this stations/organization site, that will be responsible for counts and will be receiving notifications related to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Floating Qty</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Float stock, is what is flown and/or kept in the kitchen. If selected yes, column will appear at the sock count to count both Backup stock and Float stock (back up stock is default and will always appear in stock count sheet)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Breakages</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will add a column for breakages to be filled by station during stock count.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Attach Count Sheet File When Notifying Station</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Advise to select Yes, that will have attached an excel file that when filled could be uploaded to stock count for submission. It is a good tool to avoid manual entries in the portal.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Consumption Trend Span (Days)</p>
</td>
<td width="85">
<p>180</p>
</td>
<td width="387">
<p>default value is 180, and if left blank it will generate value of 180 days.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Generate Automatic Requisitions Upon Count Approval</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if Yes, will post an option to generate automatic requisition after stock count is approved.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include All Items in Automatic Requisitions</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if yes, will include all active items in auto requisition (even if suggested order is 0)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Delay (Hours) For Automatic Requisition Generation</p>
</td>
<td width="85">
<p>0</p>
</td>
<td width="387"> </td>
</tr>
<tr>
<td width="170">
<p>Include All Station Par Levels In Counts</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will include all active items in stock count and phase out items that have nothing in transit and where counted previously.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Update Station Par Levels</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if new part is added to requisition, it will update station par levels</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Auto Approval Option</p>
</td>
<td width="85">
<p>Review</p>
</td>
<td width="387">
<p>Review Required - will request for Station Manager to do a full review of every stock count submitted by stations<br /> Auto-Approve When No Queries - stock count will be automatically approved by Skylog if no queries where generated by system;</p>
</td>
</tr>
</table>

<h2>Sample of complete Station Count Category setup</h2>
[[File:SampleCountCategory.png]]

<h1>Station Defaults</h1>

Station defaults are used whenever doing a mass transaction, for example mass import of items to station par level. The criteria in station defaults will be applied to all items imported.
<ol>
<li>In Stations screen (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 sock to be held a the station of item 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>days needed to get stock prepared for operation after it is receipted.</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>days needed to recycle stock from inbound flights to be ready for operations</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>based on Order frequency select</p>
</td>
</tr>
<tr>
<td width="217">
<p>% Loss at the Station</p>
</td>
<td width="81">
<p>0</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 sock count category (set up in previous chapter) to which items will be added</p>
</td>
</tr>
<tr>
<td width="217">
<p>Round Requisition Quantities?</p>
</td>
<td width="81">
<p>Yes</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>

<h1>Stock Items / Par Levels</h1>

Station Par levels refers to items station would be allowed to place orders for and receive stock. This can be done in a few ways: copy Par Levels from identical/similar station or do it one item at a time
<h2>Copy Par Level from existing station</h2>

<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 please find button Copy</li>
[[File:LocationOfCopyParLevelsButton.png]]

<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]]

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

</ol>

File:LocationOfCopyParLevelsButton.png

2020-04-08T09:21:02Z

Arunas.milasius:

File:CopyParLevelToStationPage.png

2020-04-08T09:20:41Z

Arunas.milasius:

File:CopyParLevelsConfirmPage.png

2020-04-08T09:20:24Z

Arunas.milasius:

AirlineSupplier Index

2020-04-08T09:20:13Z

Arunas.milasius:

__TOC__

<h1>Create organization</h1>

Organization refers to company as a whole like Lufthansa or Gate Group, and contains Organization site locations under it in Skylog (e.g. Gate Group London T5). Organization defines company type and service it provides.
First, please check if Organization already exists in Skylog. You can find the list of all Organizations [[https://rsprod.skylogportal.com/Organization'''link''']]. If Organization already exists please move to next step.

If Organization does not exist, there are 2 ways to create an Organization: contact Global Administrator or raise support request. [['link']]

<h1>Organization Sites</h1>

Organization sites determines address of the of a station, supplier or warehouse. These have to be set up if new station, supplier or warehouse needs to be added to Skylog and record does not exist.

Firstly Please check if a site is already created in skylog with same address and link to Same Organization. It is important not to duplicate organization sites entries if address assigned to organization already exists. For more please see link [[how to create organization sites]]

<h1>Stations</h1>

Station set up contains specification of stations operations (lead times, safety stocks etc.) and items (par levels) that it will have. Skylog alows advance ways to customize stations set up, from automatic stock count approvals, to RMA management.

<h2>Stations creation</h2>

You can create a new station by going to Reference Data/Airline Participants/Stations

[[File:CreateStationRef.png]]

Skylog allows advance customization of all stations. To deliver the most productive set up please consult guide below

[[File:StationSpec.png]]

<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 station address that is printed in invoices 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 airport it services. It is essential for enhanced forecasting and consumption calculations</p>
</td>
</tr>
<tr>
<td width="170">
<p>Service Type</p>
</td>
<td width="444">
<p>assign relevant station type</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 and forecast assigned to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Valid To</p>
</td>
<td width="444">
<p>date of station closure. Is not a mandatory field to be populated</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 provision of goods for the station (i.e. who will approve requisition requests, inventory reports, etc.)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="444">
<p>person to be assigned (from users register in Skylog) who will be responsible for stock counts. Selected person will be recipient of related notifications</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 with Skylog – if the station will raise requisitions and/or be expected to submit inventory reports then this setting should always be set as 'No'.</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 generated automatic requisitions after stock count, via schedule or even manually. If no, only manual orders will be allowed to be placed by station, more relevant 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. If the station wishes to see such temporary items on requisitions then this configuration flag should be set as 'Yes', otherwise, set as 'No'.</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 Skylog 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 Skylog. 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).</p>
</td>
</tr>
<tr>
<td width="170">
<p>Enforce RMA Qty</p>
</td>
<td width="444">
<p>if station is allowed to issue RMA for parts they haven't ordered from inbound flights etc. then No. If Yes, station will be allowed to return only stock qty that they counted in 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>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>
</table>

<h1>Supply Source</h1>

Supply sources defines supplying warehouse and modes of transport assigned. It is possible for station to be supplied by multiple warehouses and this could be defined at the item level is Station Item / Par Level tables. Multiple modes of transport could be assigned for each station with different lead-times

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

<h2>Add Warehouse</h2>
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]]

<h2>Add Transport Methods</h2>

<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]]

<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 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:CompleteTransportSetup.png]]

<h1>Station Count Category</h1>
[File:CreateStationCountCategory.png]

Can be found under Daily Activities/Inventory Counts/Station Count Categories. Station count category defines which items, how often need to be counted by station. It also allows to set the tolerances to count variances for automatic query process as well as define the level of automation in count and approval process – some counts can be set up as auto accepted after they are submitted, useful feature for stations like lounges, with little turn over.
<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]]

<li>Fill the table. Fields are explained in table below with samples.</li>
</ol>
</li>

<table width="0">
<tr>
<td width="170">
<p><strong>Field</strong></p>
</td>
<td width="85">
<p><strong>Sample</strong></p>
</td>
<td width="387">
<p><strong>Description</strong></p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Category Description</p>
</td>
<td width="85">
<p>Full</p>
</td>
<td width="387">
<p>Description of the count. Station could have multiple counts with different parts under each, so name of the count is useful to avoid confusions</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Schedule Option</p>
</td>
<td width="85">
<p>Automatic Schedule</p>
</td>
<td width="387">
<p>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)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Automatic Schedule Options</p>
</td>
<td width="85">
<p>Specific Day/s of the Week</p>
</td>
<td width="387">
<p>can name days of the week or month for stock count to be automatically repeated</p>
</td>
</tr>
<tr>
<td width="170">
<p>Specific Day/s of the Week</p>
</td>
<td width="85"> </td>
<td width="387">
<p>tick/ select days when stock count should be triggered</p>
</td>
</tr>
<tr>
<td width="170">
<p>Weeks Between Counts</p>
</td>
<td width="85">
<p>1</p>
</td>
<td width="387">
<p>Nr of weeks in between counts</p>
</td>
</tr>
<tr>
<td width="170">
<p>Notify Days</p>
</td>
<td width="85">
<p>3</p>
</td>
<td width="387">
<p>Nr of days stock count will be generated before, and station will get a notification</p>
</td>
</tr>
<tr>
<td width="170">
<p>Next Count Generation Date</p>
</td>
<td width="85">
<p>September 28, 2019</p>
</td>
<td width="387">
<p>Select next/first stock count to be schedule for date</p>
</td>
</tr>
<tr>
<td width="170">
<p>Value Tolerance for Count Variances</p>
</td>
<td width="85"> </td>
<td width="387">
<p>not mandatory, select variances in value per line to tolerate as ok. Meaning if there is 100 GBP tolerance and discrepancy from expected sock count is 99, count will appear as ok. This could be changed later at the item level for exceptions</p>
</td>
</tr>
<tr>
<td width="170">
<p>% Quantity Tolerance for Count Variances</p>
</td>
<td width="85">
<p>10</p>
</td>
<td width="387">
<p>not mandatory, select variance in quantity % per line to be tolerated from expected count. Meaning if 5% discrepancy from expected stock count is allowed and will not appear as a query. Can be amended at the item level for exception items</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="85"> </td>
<td width="387">
<p>select person (out of assigned to this stations/organization site, that will be responsible for counts and will be receiving notifications related to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Floating Qty</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Float stock, is what is flown and/or kept in the kitchen. If selected yes, column will appear at the sock count to count both Backup stock and Float stock (back up stock is default and will always appear in stock count sheet)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Breakages</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will add a column for breakages to be filled by station during stock count.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Attach Count Sheet File When Notifying Station</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Advise to select Yes, that will have attached an excel file that when filled could be uploaded to stock count for submission. It is a good tool to avoid manual entries in the portal.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Consumption Trend Span (Days)</p>
</td>
<td width="85">
<p>180</p>
</td>
<td width="387">
<p>default value is 180, and if left blank it will generate value of 180 days.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Generate Automatic Requisitions Upon Count Approval</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if Yes, will post an option to generate automatic requisition after stock count is approved.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include All Items in Automatic Requisitions</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if yes, will include all active items in auto requisition (even if suggested order is 0)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Delay (Hours) For Automatic Requisition Generation</p>
</td>
<td width="85">
<p>0</p>
</td>
<td width="387"> </td>
</tr>
<tr>
<td width="170">
<p>Include All Station Par Levels In Counts</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will include all active items in stock count and phase out items that have nothing in transit and where counted previously.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Update Station Par Levels</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if new part is added to requisition, it will update station par levels</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Auto Approval Option</p>
</td>
<td width="85">
<p>Review</p>
</td>
<td width="387">
<p>Review Required - will request for Station Manager to do a full review of every stock count submitted by stations<br /> Auto-Approve When No Queries - stock count will be automatically approved by Skylog if no queries where generated by system;</p>
</td>
</tr>
</table>

<h2>Sample of complete Station Count Category setup</h2>
[[File:SampleCountCategory.png]]

<h1>Station Defaults</h1>

Station defaults are used whenever doing a mass transaction, for example mass import of items to station par level. The criteria in station defaults will be applied to all items imported.
<ol>
<li>In Stations screen (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 sock to be held a the station of item 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>days needed to get stock prepared for operation after it is receipted.</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>days needed to recycle stock from inbound flights to be ready for operations</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>based on Order frequency select</p>
</td>
</tr>
<tr>
<td width="217">
<p>% Loss at the Station</p>
</td>
<td width="81">
<p>0</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 sock count category (set up in previous chapter) to which items will be added</p>
</td>
</tr>
<tr>
<td width="217">
<p>Round Requisition Quantities?</p>
</td>
<td width="81">
<p>Yes</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>

<h1>Stock Items / Par Levels</h1>

Station Par levels refers to items station would be allowed to place orders for and receive stock. This can be done in a few ways: copy Par Levels from identical/similar station or do it one item at a time
<h2>Copy Par Level from existing station</h2>

<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 please find button Copy</li>
[[File:LocationOfCopyParLevelsButton.png]]

<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]]

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

</ol>

AirlineSupplier Index

2020-04-08T08:58:33Z

Arunas.milasius:

File:SampleCategoryCount.png

2020-04-08T08:51:40Z

Arunas.milasius:

AirlineSupplier Index

2020-04-08T08:50:28Z

Arunas.milasius:

__TOC__

<h1>Create organization</h1>

Organization refers to company as a whole like Lufthansa or Gate Group, and contains Organization site locations under it in Skylog (e.g. Gate Group London T5). Organization defines company type and service it provides.
First, please check if Organization already exists in Skylog. You can find the list of all Organizations [[https://rsprod.skylogportal.com/Organization'''link''']]. If Organization already exists please move to next step.

If Organization does not exist, there are 2 ways to create an Organization: contact Global Administrator or raise support request. [['link']]

<h1>Organization Sites</h1>

Organization sites determines address of the of a station, supplier or warehouse. These have to be set up if new station, supplier or warehouse needs to be added to Skylog and record does not exist.

Firstly Please check if a site is already created in skylog with same address and link to Same Organization. It is important not to duplicate organization sites entries if address assigned to organization already exists. For more please see link [[how to create organization sites]]

<h1>Stations</h1>

Station set up contains specification of stations operations (lead times, safety stocks etc.) and items (par levels) that it will have. Skylog alows advance ways to customize stations set up, from automatic stock count approvals, to RMA management.

<h2>Stations creation</h2>

You can create a new station by going to Reference Data/Airline Participants/Stations

[[File:CreateStationRef.png]]

Skylog allows advance customization of all stations. To deliver the most productive set up please consult guide below

[[File:StationSpec.png]]

<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 station address that is printed in invoices 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 airport it services. It is essential for enhanced forecasting and consumption calculations</p>
</td>
</tr>
<tr>
<td width="170">
<p>Service Type</p>
</td>
<td width="444">
<p>assign relevant station type</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 and forecast assigned to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Valid To</p>
</td>
<td width="444">
<p>date of station closure. Is not a mandatory field to be populated</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 provision of goods for the station (i.e. who will approve requisition requests, inventory reports, etc.)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="444">
<p>person to be assigned (from users register in Skylog) who will be responsible for stock counts. Selected person will be recipient of related notifications</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 with Skylog – if the station will raise requisitions and/or be expected to submit inventory reports then this setting should always be set as 'No'.</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 generated automatic requisitions after stock count, via schedule or even manually. If no, only manual orders will be allowed to be placed by station, more relevant 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. If the station wishes to see such temporary items on requisitions then this configuration flag should be set as 'Yes', otherwise, set as 'No'.</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 Skylog 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 Skylog. 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).</p>
</td>
</tr>
<tr>
<td width="170">
<p>Enforce RMA Qty</p>
</td>
<td width="444">
<p>if station is allowed to issue RMA for parts they haven't ordered from inbound flights etc. then No. If Yes, station will be allowed to return only stock qty that they counted in 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>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>
</table>

<h1>Supply Source</h1>

Supply sources defines supplying warehouse and modes of transport assigned. It is possible for station to be supplied by multiple warehouses and this could be defined at the item level is Station Item / Par Level tables. Multiple modes of transport could be assigned for each station with different lead-times

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

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

2. Select Warehouse

[[File:SelectWarehouse.png]]

3. Set as active

[[File:SetActiveWarehouse.png]]

<h2>Add Transport Methods</h2>

<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]]

<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 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:CompleteTransportSetup.png]]

<h1>Station Count Category</h1>
[File:CreateStationCountCategory.png]

Can be found under Daily Activities/Inventory Counts/Station Count Categories. Station count category defines which items, how often need to be counted by station. It also allows to set the tolerances to count variances for automatic query process as well as define the level of automation in count and approval process – some counts can be set up as auto accepted after they are submitted, useful feature for stations like lounges, with little turn over.
<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]]

<li>Fill the table. Fields are explained in table below with samples.</li>
</ol>
</li>

<table width="0">
<thead>
<tr>
<td width="170">
<p><strong>Field</strong></p>
</td>
<td width="85">
<p><strong>Sample</strong></p>
</td>
<td width="387">
<p><strong>Description</strong></p>
</td>
</tr>
</thead>
<tbody>
<tr>
<td width="170">
<p>Count Category Description</p>
</td>
<td width="85">
<p>Full</p>
</td>
<td width="387">
<p>Description of the count. Station could have multiple counts with different parts under each, so name of the count is useful to avoid confusions</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Schedule Option</p>
</td>
<td width="85">
<p>Automatic Schedule</p>
</td>
<td width="387">
<p>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)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Automatic Schedule Options</p>
</td>
<td width="85">
<p>Specific Day/s of the Week</p>
</td>
<td width="387">
<p>can name days of the week or month for stock count to be automatically repeated</p>
</td>
</tr>
<tr>
<td width="170">
<p>Specific Day/s of the Week</p>
</td>
<td width="85"> </td>
<td width="387">
<p>tick/ select days when stock count should be triggered</p>
</td>
</tr>
<tr>
<td width="170">
<p>Weeks Between Counts</p>
</td>
<td width="85">
<p>1</p>
</td>
<td width="387">
<p>Nr of weeks in between counts</p>
</td>
</tr>
<tr>
<td width="170">
<p>Notify Days</p>
</td>
<td width="85">
<p>3</p>
</td>
<td width="387">
<p>Nr of days stock count will be generated before, and station will get a notification</p>
</td>
</tr>
<tr>
<td width="170">
<p>Next Count Generation Date</p>
</td>
<td width="85">
<p>September 28, 2019</p>
</td>
<td width="387">
<p>Select next/first stock count to be schedule for date</p>
</td>
</tr>
<tr>
<td width="170">
<p>Value Tolerance for Count Variances</p>
</td>
<td width="85"> </td>
<td width="387">
<p>not mandatory, select variances in value per line to tolerate as ok. Meaning if there is 100 GBP tolerance and discrepancy from expected sock count is 99, count will appear as ok. This could be changed later at the item level for exceptions</p>
</td>
</tr>
<tr>
<td width="170">
<p>% Quantity Tolerance for Count Variances</p>
</td>
<td width="85">
<p>10</p>
</td>
<td width="387">
<p>not mandatory, select variance in quantity % per line to be tolerated from expected count. Meaning if 5% discrepancy from expected stock count is allowed and will not appear as a query. Can be amended at the item level for exception items</p>
</td>
</tr>
<tr>
<td width="170">
<p>Person Responsible for Counts</p>
</td>
<td width="85"> </td>
<td width="387">
<p>select person (out of assigned to this stations/organization site, that will be responsible for counts and will be receiving notifications related to it.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Floating Qty</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Float stock, is what is flown and/or kept in the kitchen. If selected yes, column will appear at the sock count to count both Backup stock and Float stock (back up stock is default and will always appear in stock count sheet)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include Breakages</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will add a column for breakages to be filled by station during stock count.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Attach Count Sheet File When Notifying Station</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>Advise to select Yes, that will have attached an excel file that when filled could be uploaded to stock count for submission. It is a good tool to avoid manual entries in the portal.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Consumption Trend Span (Days)</p>
</td>
<td width="85">
<p>180</p>
</td>
<td width="387">
<p>default value is 180, and if left blank it will generate value of 180 days.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Generate Automatic Requisitions Upon Count Approval</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if Yes, will post an option to generate automatic requisition after stock count is approved.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Include All Items in Automatic Requisitions</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if yes, will include all active items in auto requisition (even if suggested order is 0)</p>
</td>
</tr>
<tr>
<td width="170">
<p>Delay (Hours) For Automatic Requisition Generation</p>
</td>
<td width="85">
<p>0</p>
</td>
<td width="387"> </td>
</tr>
<tr>
<td width="170">
<p>Include All Station Par Levels In Counts</p>
</td>
<td width="85">
<p>No</p>
</td>
<td width="387">
<p>if yes, will include all active items in stock count and phase out items that have nothing in transit and where counted previously.</p>
</td>
</tr>
<tr>
<td width="170">
<p>Update Station Par Levels</p>
</td>
<td width="85">
<p>Yes</p>
</td>
<td width="387">
<p>if new part is added to requisition, it will update station par levels</p>
</td>
</tr>
<tr>
<td width="170">
<p>Count Auto Approval Option</p>
</td>
<td width="85">
<p>Review</p>
</td>
<td width="387">
<p>Review Required - will request for Station Manager to do a full review of every stock count submitted by stations<br /> Auto-Approve When No Queries - stock count will be automatically approved by Skylog if no queries where generated by system;</p>
</td>
</tr>
</tbody>
</table>

<h2>Sample of complete Station Count Category setup</h2>
[[File:SampleCountCategory.png]]

AirlineSupplier Index

2020-04-08T08:47:15Z

Arunas.milasius:

File:SelectStationRequiringNewStationCountCategory.png

2020-04-08T08:45:14Z

Arunas.milasius:

AirlineSupplier Index

2020-04-08T08:43:39Z

Arunas.milasius: