MCS - User contributions [en-gb]

Main Page

2025-12-19T11:40:20Z

Anw: Minor correction

<div style="text-align: center;">[[File:calidus-mcs-logo.png]]</div>

<center><font size="5">Welcome to the ''CALIDUS'' MCS Assist help pages.</font></center>

Here you will find all kinds of guides, from simple to advanced, from user guides to technical implementation guides, all to provide as much information on how to get the best out of your ''CALIDUS'' MCS implementation.

Assuming you are now up and running with your system, why not try to find something you didn't know? Try clicking the 'Did You Know' link below.

<center><font size="5">[[Did You Know]]</font></center>

That's how Assist works - help broken down into bite-sized chunks, designed to help you make the most of your system. If you're familiar with the web and familiar with Wiki, you're going to find it easy to get around in Assist.

If you're coming here as a new user without a clear idea of how ''CALIDUS'' MCS works or what it does, you should start with the overview and glossary of terms - that will give you enough information so that you're clear on what we're achieving with this application. You'll find them first in the list below [[#CALIDUS MCS Overview|here]].

If you're more comfortable with documents rather than web pages, we've got you covered.

Every page here can be downloaded as a PDF (including this one) by clicking the ''Download as PDF'' link in the toolbar, typically on the left of your browser window. That will give you the PDF of just that page, but if you want something more formal, see the heading below called [[#Documents|Documents]] - downloading those as PDFs will give you the formal Aptean document. On this page, we've also provided direct links to those document versions - click the {{DocLink|Main Page}} link next to the page.

As you can see, some of the guides are multi-page, so we organise those into categories of pages. Where those pages form a guide themselves (like the Device User Guide), you can use that ''Download as PDF'' link again from the category to get all the pages in one handy guide.

We keep these pages up to date based on the latest available version of ''CALIDUS'' MCS - if you see something you like here, but aren't sure whether your version supports it, why not give our team a call? We can advise you on the steps you need to take to upgrade your system to the latest and greatest.

We're constantly updating the system, and that means that we're constantly updating the documentation too. One of the great things about Wiki pages is that the history is kept, so you can click the ''View History'' link (usually at the top of the page) to see all previous versions of the help page. So, although all the guides are the latest version, you can still access the older pages for reference.

The same is true of any of the pictures that we've uploaded in these guides - click on them and you can see the whole history of that picture. You can download them as well, if you like.

Of course, we also keep PDF copies of the previous version of the documentation when we've finished it, so we can always provide them to you. We've generated them from these Assist pages just like you can - because it's that easy to use.

Below you'll find a link to all the guides in this Assist system.

== ''CALIDUS'' MCS Overview ==
''CALIDUS'' MCS is a mobile website application designed to extend ''CALIDUS'' TMS.

* [[Overview]]
* [[Template: MCS_Glossary|Glossary of Terms]]
* [[Did You Know]]

== [[:Category:Guides|Guides]] ==
* [[:Category:UG 320722 CALIDUS MCS Device User Guide|Device User Guide]] {{DocLink|Category:UG 320722 CALIDUS MCS Device User Guide}}
* [[:Category:UG 320722 CALIDUS MCS C-TMS User Guide|C-TMS User Guide]] {{DocLink|Category:UG 320722 CALIDUS MCS C-TMS User Guide}}
* [[Setup and Configuration]] {{DocLink|Category:OV 320722 CALIDUS MCS Setup Guide}}
* [[OV 320722 CALIDUS MCS Device Advanced Guide]] {{DocLink|Category:OV 320722 CALIDUS MCS Device Advanced Guide}} comprising:
** [[MCS Device Cleardown|Device Cleardown]]
** [[Refresh MCS]]

==[[:Category:Documents|Documents]]==
All documents can be found here:
* [[:Category:Documents]]

[[:Category:UG 320722 CALIDUS MCS Device User Guide|UG 320722 CALIDUS MCS Device User Guide]] {{DocLink|Category:UG 320722 CALIDUS MCS Device User Guide}}

[[:Category:UG 320722 CALIDUS MCS C-TMS User Guide|UG 320722 CALIDUS MCS C-TMS User Guide]] {{DocLink|Category:UG 320722 CALIDUS MCS C-TMS User Guide}}

[[OV 320722 CALIDUS MCS Installation Guide]] {{DocLink|OV 320722 CALIDUS MCS Installation Guide}}

[[OV 320722 CALIDUS MCS Technical Guide]] {{DocLink|OV 320722 CALIDUS MCS Technical Guide}}

[[OV 320722 CALIDUS MCS Processes]] {{DocLink|OV 320722 CALIDUS MCS Processes}}

[[OV 320722 CALIDUS MCS Setup Guide]] {{DocLink|Category:OV 320722 CALIDUS MCS Setup Guide}}

[[OV 320722 CALIDUS MCS Device Advanced Guide]] {{DocLink|Category:OV 320722 CALIDUS MCS Device Advanced Guide}}

==[[:Category:Releases|Releases]]==
All of the release notes for the system can be found here:
* [[:Category:Releases|Releases]]

== Coming Soon ==
This section contains guides that are in progress. Typically, they might be incomplete or less detailed than needed.
We'll link our new guides here, whether we've finished them or not. That way you can see what's around the corner.

*

We also categorise any pages that are considered incomplete. These pages may not be listed above, as they are not new or upcoming guides, but they generally need a little more work to get them to their full potential.

You can find the list here:
* [[:Category:Incomplete|Incomplete Pages]]

== [[:Category:Technical|Technical Details‎]] ==
* [[:Category:Developer Guides‎]]
* [[MCS Process Flows]] {{DocLink|OV 320722 CALIDUS MCS Processes}}

== New Users ==
{{Note}} For new users of ''CALIDUS'' Assist:

Go to the [[Special:Preferences|My Preferences]] link and click on the Editing tab. Check the "Prompt me when entering a blank edit summary" check box and save the settings.

Setup and Configuration

2025-09-16T11:52:28Z

Anw: Added details of MCS Scanning changes

{{Note}} This guide assumes familiarity with C-TMS processes for the following actions:
* Creating users.
* Creating and configuring user groups.
* Adding users to a group.
* Creating label printers.
* Changing user-definable system parameters.
* Finding and amending locations.
* Creating or amending reason codes.
* Running Oracle Reporting Suite data extracts.

== Pre-Requisites ==
The MCS system must be configured and available.

Default cost centre must be configured.

Pallet Label format must be configured for the system.

You will be advised of these details by your OBS Logistics implementation team.

== Access Control ==
=== MCS Users ===
Create MCS users and place them in their own group.

Set up each user with the default pallet label printer. This is dependent on the pallet label format, and should either be a Laser printer or label printer.

You will be advised of the printer type by your OBS Logistics implementation team.

[[File:CTMS_AccessControl3.png|border|600px]]

=== C-TMS Users ===
Provide access to the Shipment Pallets screen from the users' groups.

Set up each user with the default pallet label printer. This is dependent on the pallet label format, and should either be a Laser printer or label printer.

You will be advised of the printer type by your OBS Logistics implementation team.

The group for these users must have additional tabs and screens set up:
* Tabs:
** LOCATION/MCS
* Screens:
** Shipment Pallets

[[File:CTMS_AccessControl1.png|border|600px]]

[[File:CTMS_AccessControl2.png|border|600px]]

== System Parameters ==
These will be initially created and configured by your Aptean implementation team.

[[File:CTMS_Parameters1.png|border|600px]]

You may modify all of these parameters using the system parameters maintenance screen in CTMS.

{{Note}} Each of the parameters you can configure here are system-wide parameters and affect the functioning of MCS in your entire operation. You should take care in changing these parameters. Other configuration exists against the specific location, to affect functionality at that location alone.

{| class="wikitable apt-searchable" border="1" width="100%"
|- bgcolor="silver"
!Parameter !! Description !! Level !! Notes
|-
| MCS_AWB_REQUIRED || This flag control whether the AWB (Air Way Bill) is requested during the pallet building and despatch processes in C-MCS. || SYSTEM ||
|-
| MCS_DESPATCH_DISPLAY_DROP || Display the Drop Number in the Despatch Screen || SYSTEM ||
|-
| MCS_DESPATCH_TO_PLAN || Enforce the despatch scanning of packages and pallets to the planned trips? (Y/N) || SYSTEM ||
|-
| MCS_DISPLAY_ADDITIONAL || Display items scanned from different trips in MCS despatch? (Y/N) || SYSTEM ||
|-
| MCS_DISPLAY_COMMTYPE_HAZ || This flag controls whether commodity code and hazardous information is displayed against items and pallets in C MCS pallet building. || SYSTEM ||
|-
| MCS_DISPLAY_PROD_TYPE || This flag controls whether the Product Type is displayed against items and pallets in C- MCS in receipt, despatch and pallet building. || SYSTEM ||
|-
| MCS_DYNAMIC_PALLET_BUILDING || This flag controls whether to allow pallet building to occur while scanning items for despatch in the items screen || SYSTEM ||
|-
| MCS_EXCEPTIONS_DAMAGED || MCS exceptions at Receipt (excluding FNR and LATE) and Despatch will be marked as damaged items and be removed from onward trips (Y/N). || SYSTEM ||
|-
| MCS_FAST || This parameter will control the level of validation performed during MCS scanning. || SYSTEM ||
|-
| MCS_FAST_VALIDATION || Is fast validation enabled || SYSTEM ||
|-
| MCS_ITEM_DISPLAY_DU || This flag controls whether the DU type is displayed instead of the item type on item lists in MCS. || SYSTEM ||
|-
| MCS_LOCATION_PROMPT || Prompt for Receipt Location at Receipt || SYSTEM ||
|-
| MCS_MOVE_FULL_CONSIGNMENT || Move all items for an order during MCS split scanning. || SYSTEM ||
|-
| MCS_NEW_DESPATCH_MODE || This flag controls whether the new Despatch screen is run || SYSTEM ||
|-
| MCS_PALLET_LABEL_FORMAT || The format of pallet label produced by the pallet building option when printing pallet labels. || SYSTEM ||
|-
| MCS_PREVENT_UNPLANNED || Prevent unplanned items being scanned for pallet building, despatch and receipt although expected for the route (Y/N)? || SYSTEM ||
|-
| MCS_RECEIVE_TO_PLAN || Enforce the receipt scanning of packages and pallets to the planned trips? (Y/N) || SYSTEM ||
|-
| MCS_SET_PALLET_ID || MCS set item Pallet Id || SYSTEM ||
|-
| MCS_TEMPERATURE_SCAN || Prompt for Temperature Type at MCS Despatch || SYSTEM ||
|-
| MCS_TENDERED_ITEMS || This flag controls whether MCS items are generated at the change to TENDERED status as well as at ACCEPTED status, or just ACCEPTED status. || SYSTEM ||
|-
| MCS_UPDATE_SCAN_IMMEDIATELY || Allow items to count as despatched immediately after scanning? (Y/N) || SYSTEM ||
|-
| MSC_STD_STATUS_CHANGES || Do trips go to EN-ROUTE and COMPLETED auto? || SYSTEM || Affects Despatch only. N means set to ACCEPTED if at PLANNED or TENDERED, otherwise EN-ROUTE. Any other value means set to EN-ROUTE status.
|}

== MCS Control Parameters ==
This will be set up by your Aptean implementation team.

This controls which cost centre is used for MCS reason codes.

{| class="wikitable apt-searchable" border="1" width="100%"
|-
!CTP_KEY !!CTP_VALUE !!CTP_UPDATE_COUNTER !!CTP_SITE_ID !!CTP_SYNC_IND !!CTP_DEVICE_SETTING_IND
|-
|DEFAULT_COST_CENTRE ||CONTRACT ||1 ||_ALL_ ||0 ||0
|}

== Standing Data ==
=== Reason Codes ===
Set up for the default cost centre - you will be advised of the cost centre that by your OBS Logistics implementation team.

[[File:CTMS_ReasonCodes.png|border|600px]]

{{Note}} You should set up the standard MCS reasons under your cost centre "+" for reason codes, so that they can be properly displayed on your TMS screens and reports, and so that they are not displayed as reason codes for a user to select on the device. See the recommendations and notes below.

{| class="wikitable" border="1"
|- bgcolor="silver"
! Code !! Description !! Cost Centre !! Notes
|-
| SL || Successfully Loaded || "+" ||  
|-
| SU || Successfully Unloaded || "+" ||  
|-
| ML || Missing Load || MCS CC || 
|-
| NL || Not Loaded || "+" || 
|-
| MI || Moved Item || "+" ||  
|-
| OP || On Pallet || "+" ||  
|-
| FNR || Freight not Received || MCS CC || Only configure if you want Freight Not Received functionality enabled.
|-
| UP || Unpacked Item || "+" ||  
|}

{{Note|
* You should set up these reason codes against the MCS cost centre (set up above in the in the MCS Control Parameters by your implementation team) for the reasons you want to select for damages and exceptions processing only. You should have the Cust Group set to "+" (recommended) or the cust group for which these reason codes apply.
* Any other reason codes that you want displayed on the Item History (on the CTMS Orders screens and extracts) should be set to Cost Centre "+" - these will then not display on the MCS device.
* Reason codes will NOT display descriptions in the MCS Orders screen if the cost centre or cust group do not match the order, or the values of these settings against the reason code are not "+".
* Any reason code that begins with the word "Damaged" (in any case, upper, lower or mixed case) is considered a damages reason code and, regardless of where it is used, will automatically remove the items from any subsequent planned trips.
* Any reason code with action "LATE" can be used to make items available for despatch on other loads. Only configure this action if this is part of your process.
}}

=== Depot Location Configuration ===
Each location to be enabled for C-MCS functionality must be set up as depot type "RDC".

[[File:CTMS_Locations.png|border|600px]]

The following flags may be configured:
* ''MCS Active'' - this flag controls whether C-MCS is used at this location.
* ''MCS Identifier'' - this is an identifier of the depot, used by MCS. This is displayed against items in receipt, so the user can see from which depot the items originated, to aid in unloading.
* ''Receipt Only'' - this flag controls whether the onward stops on this trip (and subsequent trips to the next RDC) are automatically debriefed with the time this stop is debriefed. If set, only the stop being receipted will be debriefed.
* ''Despatch Only'' - this flag controls whether the previous stops on this trip (and prior trips back to the previous RDC) are automatically debriefed with the time this stop is debriefed. If set, only the stop being despatched will be debriefed.
* ''Print Pallet Label'' - this flag controls whether pallets built through C-MCS at this location will use pre-printed stationary (when unchecked), or will print the label from C-MCS (when checked).
* ''Pallet Building validation'' - this flag controls the validation of pallets built through MCS. In all cases, pallets are retained until the pallet is received at the next depot location, whether this is an MCS-enabled location or not. Values are:
** "To Next RDC" - items built onto pallets at this location will be validated that they are all going to the same next depot location;
** "To Final RDC" - items built onto pallets at this location will be validated that they are all going to the same final delivery depot;
** "By Final RDC Trip" - items built onto pallets at this location will be validated that they are all being delivered on the same final delivery trip.

* ''Pallet Building Process'' - values are:
** "Continuous"
** "Single"
* ''Pallet Closure'' - this flag controls whether pallet closure is an option for the C-MCS mobile device users.
* ''Pallet Seal at Closure'' - this option controls whether Seal number will be prompted for at pallet closure. Seal numbers are stored against a pallet in the AWB/Cons reference.
* ''Trans-ship Enabled'' - this flag enables the Trans-Ship process at this location. Trans-ship processing will identify whether the item is planned out of this location on a trip and, if so, will show the user the trip and vehicle and ask them to confirm by entering the vehicle registration. For pallets on the received trip, all items on the pallet must be planned out on the same trip. Successfully trans-shipped items will be marked as despatched on the outbound trip. if any item is not planned out of this location, or not all items on a pallet are planned together, the system will inform the user that trans-ship can't be completed and the items must be despatched separately.
* ''Debrief Stop Times'' - this flag controls whether C-MCS loading or unloading will debrief the stop times at that location.
* ''Set Trip Status at Receipt'' - if checked, the system will attempt to automatically move the trip to COMPLETED status when it is completed in C-MCS.
* ''Set Trip Status at Despatch'' - if checked, the system will attempt to automatically move the trip onto the next applicable status when it is completed in C-MCS. For PLANNED or TENDERED trips, this will be ACCEPTED status. For ACCEPTED trips, this will be EN-ROUTE.

== MCS/WCS Locations ==
If using location confirmation in MCS, then WCS locations must be configured, as well as Locations matching those WCS locations.

WCS Locations are configured in the [[obs:WCS Maintenance|WCS Maintenance]] screen, on the Locations tab.

[[File:Wcs_location.png|border|800px]]

Additionally, the locations should be set up as normal locations.

This is through the standard Locations maintenance screen as above.

Only minor information is required here:
* Location ID - the same as the WCS Location ID.
* Location Type - by convention "WCS", but can be set to any valid location type. Avoid "RDC", "BRANCH", etc.
* Name - set to the name describing the location e.g. "Depot Ambient Receipt", "Depot Chilled Quarantine", etc.

== Reports ==
Extract Suite reports can be configured for your system:
* MCS_DTLS/MCS DETAILS - the items and pallets that are awaiting scanning in your system.
* REASONS/ORD_ITEM_REASON - the reasons against order items, including scan reasons.
* TRIP SCANS/TRIP SCANS - Items scanned for a trip.
* O/S SCANS/MISSING_SCANS - Items not scanned.

[[Category:Guides]]

Despatch

2025-09-16T11:06:56Z

Anw: Added details of MCS Scanning changes

Clicking 'Despatch' from the menu will take you to the despatch screen.

The application will prompt you to enter the Trip ID that is to be loaded and despatched.

If configured to do so, the application will also ask whether an Airway bill or Consignment reference is required. The default is yes. If you select no and the carrier does require a Consignment or AWB's to be entered, the application will display a warning message prompting you that it is required

<gallery widths=200px heights=320px perrow=3>
Image:MCS_Despatch1.png|''Despatch Trip Entry''
Image:MCS_Despatch2.png|''AWB/Consignment Select''
Image:MCS_Despatch3.png|''AWB Entry''
</gallery>

Once the AWB/Cons is entered, or if one is not required or prompted for, the application will retrieve a list of all the items that require loading onto that trip.

<gallery widths=200px heights=320px perrow=3>
Image:MCS_Despatch4.png|''Items to Despatch''
</gallery>

The application will display the trip details and a summary of the items planned to be despatched on this trip in a header at the top of the screen by default. If the trip has an AWB or Consignment number, this will be displayed here with a button to enter a new number if required.

{{Note}} If you want more room on the screen to display the list of items, click on the list. The header will be set so that it can scroll off the screen (rather than floating at the top).

The item list will display the following information for each item that is planned to be loaded on this trip:
* ''Item ID'' - this can be either the individual package ID or the pallet ID.
* ''Item type'' - this is normally either PACKAGE for individual items or PALLET for palletised items. This can be configured so that the transport system's transport unit (or DU type) is displayed here instead of PACKAGE.
* ''Item status'' - for items that have not yet been scanned, this will be "Pending".
* ''Product type'' - the system can be configured to display the product type of packages here.
* ''AWB/Consignment ID'' - if the pallet has been updated with an AWB or consignment number in the transport system, this will be displayed here, along with an indicator as to whether this is an AWB (A) or Consignment (C) number. An '''AWB/Con''' button is also present to change this reference here.
* ''Drop No'' - if configured to use drop sequence in despatch, the drop number will be displayed after the item.

If configured to do so, the items will be displayed in ascending product type, then reverse drop sequence.

For example, if there are AMBIENT and CHILLED items, and 2 drops, each with 2 orders and 2 items, the item list will look like this:
* AMBIENT, Drop 2, Order 1, item 1
* AMBIENT, Drop 2, Order 1, item 2
* AMBIENT, Drop 2, Order 2, item 1
* AMBIENT, Drop 2, Order 2, item 2
* AMBIENT, Drop 1, Order 1, item 1
* AMBIENT, Drop 1, Order 1, item 2
* AMBIENT, Drop 1, Order 2, item 1
* AMBIENT, Drop 1, Order 2, item 2
* CHILLED, Drop 2, Order 1, item 1
* CHILLED, Drop 2, Order 1, item 2
* CHILLED, Drop 2, Order 2, item 1
* CHILLED, Drop 2, Order 2, item 2
* CHILLED, Drop 1, Order 1, item 1
* CHILLED, Drop 1, Order 1, item 2
* CHILLED, Drop 1, Order 2, item 1
* CHILLED, Drop 1, Order 2, item 2

The application will display a number of buttons and actions at the bottom of the screen.
* '''ITM/EXC''' mode selector (described below).
* '''Load''' - mark the item as Loaded (in ITM mode) or as an exception (in EXC mode).
* '''Show/Hide''' - show all items (including Loaded items) or just Pending/Error items.
* '''Rfsh''' - refresh the planned items on the list from the transport system.
* '''EXC''' - mark all pending items as exceptions.
* '''Comp''' - complete the trip and despatch it.
* '''LIM/ALL''' slider - show a limited number of items in the screen (which improves performance) or show all items on the trip.

The screen operates in two modes, signified by the ITM slider in the bottom-right of the screen:
* ''ITM'' - each item you scan will be marked as Loaded.
* ''EXC'' - each item you scan will be marked as an Exception - you will be shown the [[Damages]] screen to see the details on enter the reason.

The screen always starts in item loading mode (ITM), but you can switch at any time by clicking this slider to the other mode, and back again.

When you scan an item that is planned on this trip, the screen will automatically mark it as loaded. If you enter the item manually and hit return or click the '''Load''' button, this will also mark the item as loaded.

{{Note}} If you are using MCS Location Scanning at despatch, the device will prompt for confirmation of the correct vehicle and compartment, matching the product type of the item. The user will be shown the name of the vehicle and temperature, and prompted to confirm. The user can scan or enter the vehicle ID and product type combined together to confirm this. For example "TRAILER123AMBIENT", "AB75XYZCHILLED". It is recommended that these are barcodes and attached to the vehicles/trailers/compartments.

When you scan an item that is not planned on this trip, the screen will add this item to the list and mark it as pending validation with the system. If the device has a data connection, this will be immediately validated. If not, this additional item will be validated when the device has a data connection.

If the system is configured not to allow additional items, the device will inform you when validating the item that unplanned items are not allowed. Otherwise, if the item is not planned to move through the location that is a destination on this trip, then the device will inform you that this item is not allowed onto this trip. In both cases, they will be marked as Error status.

If the item is planned, or the system allows additional unplanned items and this item is valid for this trip, the status will be set to 'Loaded'.

By default, the screen displays only items that have not yet been loaded (i.e. status Pending) and any error items (status Error). The screen header shows the amount of items scanned so far, and the amount remaining. If you want to see details of all the items on the trip, you can click the '''Show''' button on the screen footer. You can then hide them again using the '''Hide''' button.

<gallery widths=200px heights=320px perrow=3>
Image:MCS_Despatch5.png|''Partial Complete Despatch''
</gallery>

If an items is scanned and a 3rd party label is required then the user will be prompted to enter a 3rd party label ID. This can be entered by either scanning the 3rd party label barcode or manually keying the label ID

<gallery widths=200px heights=320px perrow=3>
Image:MCS_Despatch6.png|''3rd Party Label Entry''
</gallery>

For items that have been scanned as loaded, the following information may be displayed:
* ''3rd-party label'' - if the item required a 3rd-party label when loading, it is displayed on the list.
* ''Item status'' - for successfully-loaded items, the status will be "Loaded". For additional items (i.e. items that were not planned on this trip), the status will be "Validating" if this has not yet been completed, "Loaded" if they are allowed on this trip, or "Error" if there has been an issue with this item. A description of the problem will also be displayed, and a '''DEL''' button to remove this item from the trip once the physical item has been removed.

All items will then be scanned to confirm despatch.

If at any point an item is damaged, you can click the '''ITM/EXC''' slider to move into Exception mode - any items you scan in this mode will take you to the [[Damages]] screen to enter the exception reason.

Once all items are scanned you can click '''Complete''' to confirm the trip as despatched.

{{Note}} All items planned on the trip must be confirmed as either Loaded or have an exception reason code assigned to them. If not, the application will inform you and will not despatch the trip. You can use the '''EXC''' button on the footer to mark all remaining pending items with an exception reason through the [[Damages]] screen.

<gallery widths=200px heights=320px perrow=3>
Image:MCS_Despatch7.png|''Ready for Despatch''
Image:MCS_Despatch8.png|''Despatch Confirmed''
</gallery>

{{Note}} Only once a trip is confirmed will TMS be informed of the successful scans and complete the trip.

[[Category:UG 320722 CALIDUS MCS Device User Guide|300]]

Damages

2025-09-16T10:38:43Z

Anw: Added details of MCS Scanning changes

If the damages screen is accessed from another screen (through the damages or exceptions processes), the item is populated in the damages screen. If the Damages screen is accessed from the menu (adhoc), the damaged item must be scanned or entered to populate the Damages screen.

<gallery widths=200px heights=320px perrow=3>
Image:MCS_Damages1.png|''Adhoc - Scan Damaged Item''
</gallery>

The damages screen contains:
* ''Item ID'' - this can be either the individual package ID or the pallet ID.
* ''Item Piece Type'' - either PACKAGE for individual items or PALLET for palletised items.
* ''Item Status''.
* ''Item Description'' - if this is a package, any description against the package is shown here.
* ''Damages Reason'' - a drop-down list of reasons for marking this item as an exception.

<gallery widths=200px heights=320px perrow=3>
Image:MCS_Damages2.png|''Damaged Item''
</gallery>

To mark an item as an exception, you must select a reason code from the drop down list:

<gallery widths=200px heights=320px perrow=3>
Image:MCS_Damages3.png|''Reason Code Selection''
</gallery>

Once you have entered the reason code, you can click '''Confirm''' to mark the item as an exception.

{{Note}} If you are using MCS Location Scanning, and the location is the device will prompt for the quarantine location at this depot, matching the product type of the item. The user will be shown the name of the location, and prompted to confirm. The user can scan or enter the location ID or any check digits associated to that location.

Once an item (package or pallet) has been marked as an exception, the item will be updated in the transport system (either immediately through the Damages menu option, or when the receipt or despatch is confirmed).

If this is through the Damages option, ''no matter what reason code is selected'', this item will be taken off this trip and this package or packages on this pallet will be taken off all onward trips, and will be audited with the reason code you entered against the order item. If this item requires re-delivery, the item must be re-booked on a new order.

If this is through the Despatch option, this item will be taken off this trip, for despatch ''and'' for receipt at the next location. This package or packages on this pallet will be taken off all onward trips, and will be audited with the reason code you entered against the order item. If these items require re-delivery, they must be re-booked on a new order. If the reason code begins with "Damaged" or the system is configured to consider all exceptions as damages, this reason code will be passed to these items, otherwise they will simply be classed as missing items.

If this is through the Receipt option, any LATE action reason codes or the FNR reason code will ''not'' automatically unplan the items.

You can back out of damaging an item by clicking the '''Cancel''' button instead. If you came to this screen from another screen, you will be returned there and the item will not have been affected. If you came to this screen from the menu, you will be returned to the item scanning prompt.

[[Category:UG 320722 CALIDUS MCS Device User Guide|500]]

Receipt

2025-09-16T10:37:12Z

Anw: Added details of MCS Scanning changes

Clicking 'Receipt' from the menu will take you to the receipt screen.

The application will prompt you to enter the Trip ID that is to be unloaded and received.

<gallery widths=200px heights=320px perrow=3>
Image:MCS_Receipt1.png|''Receipt''
</gallery>

The application will retrieve a list of all the items that require unloading from that trip.

<gallery widths=200px heights=320px perrow=3>
Image:MCS_Receipt2.png|''Receipt Items''
</gallery>

The application will display the trip details and a summary of the items to be received on this trip in a header at the top of the screen by default.

{{Note}} If you want more room on the screen to display the list of items, click on the list. The header will be set so that it can scroll off the screen (rather than floating at the top).

The item list will display the following information for each item that is planned to be unloaded on this trip:
* ''Item ID'' - this can be either the individual package ID or the pallet ID. The despatching depot is shown in brackets after the ID to help with identifying the items in the vehicle.
* ''Item type'' - this is normally either PACKAGE for individual items or PALLET for palletised items. This can be configured so that the transport system's transport unit (or DU type) is displayed here instead of PACKAGE.
* ''Item status'' - for items that have not yet been scanned, this will be "Pending".
* ''Product type'' - the system can be configured to display the product type of packages here.

The application will display a number of buttons and actions at the bottom of the screen.
* '''ITM/EXC''' mode selector (described below).
* '''Unload''' - mark the item as Unloaded (in ITM mode) or as an exception (in EXC mode).
* '''Show/Hide''' - show all items (including unloaded items) or just Pending/Error items.
* '''EXC''' - mark all pending items as exceptions.
* '''Comp''' - complete the trip and receive it.
* '''LIM/ALL''' slider - show a limited number of items in the screen (which improves performance) or show all items on the trip.

The screen operates in two modes, signified by the ITM slider in the bottom-right of the screen:
* ''ITM'' - each item you scan will be marked as Unloaded.
* ''EXC'' - each item you scan will be marked as an Exception - you will be shown the [[Damages]] screen to see the details on enter the reason.

The screen always starts in item unloading mode (ITM), but you can switch at any time by clicking this slider to the other mode, and back again.

When you scan an item, the screen will automatically mark it as unloaded. If you enter the item manually and hit return or click the '''Unload''' button, this will also mark the item as unloaded.

<gallery widths=200px heights=320px perrow=3>
Image:MCS_Receipt3.png|''Item Receipted''
</gallery>

{{Note}} If you are using MCS Location Scanning, the device will prompt for the receipt location at this depot, matching the product type of the item. The user will be shown the name of the location, and prompted to confirm. The user can scan or enter the location ID or any check digits associated to that location.

If your depot is configured as a trans-ship location, the application will check whether the item is planned out of this location. If this is a pallet, the process will check that all items are planned out of this location on the same trip. If so, the application will display the trans-ship information and request confirmation:
* ''Item ID'' - this can be either the individual package ID or the pallet ID.
* ''Item Piece Type'' - either PACKAGE for individual items or PALLET for palletised items.
* ''Item Description'' - if this is a package, any description against the package is shown here.
* ''Onward Trip'' - the outbound trip for this item.
* ''Driver Name'' - the driver of the outbound trip.
* ''Vehicle Reg'' - the registration of the vehicle of the outbound trip.

<gallery widths=200px heights=320px perrow=3>
Image:MCS_Receipt5.png|''Trans-shipping an item''
</gallery>

You will be prompted to confirm the outbound vehicle by entering the registration of the vehicle and clicking '''Confirm'''. You can cancel the receipt of the item using the '''Cancel''' button.

When you confirm trans-ship of an item in this way, the item is confirmed as unloaded on the inbound trip ''and'' loaded on the outbound trip.

{{Note}} If the item is not planned out of this location, or all items on a pallet are not planned out of that location on the same trip, the application cannot trans-ship the item and will tell you that these items must be scanned for despatch.

Once an item is received, the status will be set to 'Unloaded'. By default, the screen displays only items that have not yet been unloaded (i.e. status Pending) and any error items (status Error). The screen header shows the amount of items scanned so far, and the amount remaining. If you want to see details of all the items on the trip, you can click the '''Show''' button on the screen footer. You can then hide them again using the '''Hide''' button.

For items that have been scanned as unloaded, the following information may be displayed:
* ''Item status'' - for successfully-unloaded items, the status will be "Unloaded". For additional items (i.e. items that were not planned on this trip), the status will be "Validating" if this has not yet been completed, "Unloaded" if they are allowed on this trip, or "Error" if there has been an issue with this item. A description of the problem will also be displayed, and a '''DEL''' button to remove this item from the trip once the physical item has been removed.

All items will then be scanned to confirm receipt.

If at any point an item is damaged, you can click the '''ITM/EXC''' slider to move into Exception mode - any items you scan in this mode will take you to the [[Damages]] screen to enter the exception reason.

Once all items are scanned you can click '''Complete''' to confirm the trip as received.

{{Note}} All items planned on the trip must be confirmed as either Unloaded or have an exception reason code assigned to them. If not, the application will inform you and will not receive the trip. You can use the '''EXC''' button on the footer to mark all remaining pending items with an exception reason through the [[Damages]] screen.

<gallery widths=200px heights=320px perrow=3>
Image:MCS_Receipt4.png|''Receipt Confirmed''
</gallery>

{{Note}} Only once a trip is confirmed will TMS be informed of the successful scans and complete the trip.

[[Category:UG 320722 CALIDUS MCS Device User Guide|400]]

Setup and Configuration

2025-09-16T10:33:42Z

Anw: Updated with new MCS development

{{Note}} This guide assumes familiarity with C-TMS processes for the following actions:
* Creating users.
* Creating and configuring user groups.
* Adding users to a group.
* Creating label printers.
* Changing user-definable system parameters.
* Finding and amending locations.
* Creating or amending reason codes.
* Running Oracle Reporting Suite data extracts.

== Pre-Requisites ==
The MCS system must be configured and available.

Default cost centre must be configured.

Pallet Label format must be configured for the system.

You will be advised of these details by your OBS Logistics implementation team.

== Access Control ==
=== MCS Users ===
Create MCS users and place them in their own group.

Set up each user with the default pallet label printer. This is dependent on the pallet label format, and should either be a Laser printer or label printer.

You will be advised of the printer type by your OBS Logistics implementation team.

[[File:CTMS_AccessControl3.png|border|600px]]

=== C-TMS Users ===
Provide access to the Shipment Pallets screen from the users' groups.

Set up each user with the default pallet label printer. This is dependent on the pallet label format, and should either be a Laser printer or label printer.

You will be advised of the printer type by your OBS Logistics implementation team.

The group for these users must have additional tabs and screens set up:
* Tabs:
** LOCATION/MCS
* Screens:
** Shipment Pallets

[[File:CTMS_AccessControl1.png|border|600px]]

[[File:CTMS_AccessControl2.png|border|600px]]

== System Parameters ==
These will be initially created and configured by your Aptean implementation team.

[[File:CTMS_Parameters1.png|border|600px]]

You may modify all of these parameters using the system parameters maintenance screen in CTMS.

{{Note}} Each of the parameters you can configure here are system-wide parameters and affect the functioning of MCS in your entire operation. You should take care in changing these parameters. Other configuration exists against the specific location, to affect functionality at that location alone.

{| class="wikitable apt-searchable" border="1" width="100%"
|- bgcolor="silver"
!Parameter !! Description !! Level !! Notes
| MCS_AWB_REQUIRED || This flag control whether the AWB (Air Way Bill) is requested during the pallet building and despatch processes in C-MCS. || SYSTEM ||
|-
| MCS_DESPATCH_DISPLAY_DROP || Display the Drop Number in the Despatch Screen || SYSTEM ||
|-
| MCS_DESPATCH_TO_PLAN || Enforce the despatch scanning of packages and pallets to the planned trips? (Y/N) || SYSTEM ||
|-
| MCS_DISPLAY_ADDITIONAL || Display items scanned from different trips in MCS despatch? (Y/N) || SYSTEM ||
|-
| MCS_DISPLAY_COMMTYPE_HAZ || This flag controls whether commodity code and hazardous information is displayed against items and pallets in C MCS pallet building. || SYSTEM ||
|-
| MCS_DISPLAY_PROD_TYPE || This flag controls whether the Product Type is displayed against items and pallets in C- MCS in receipt, despatch and pallet building. || SYSTEM ||
|-
| MCS_DYNAMIC_PALLET_BUILDING || This flag controls whether to allow pallet building to occur while scanning items for despatch in the items screen || SYSTEM ||
|-
| MCS_EXCEPTIONS_DAMAGED || MCS exceptions at Receipt (excluding FNR and LATE) and Despatch will be marked as damaged items and be removed from onward trips (Y/N). || SYSTEM ||
|-
| MCS_FAST || This parameter will control the level of validation performed during MCS scanning. || SYSTEM ||
|-
| MCS_FAST_VALIDATION || Is fast validation enabled || SYSTEM ||
|-
| MCS_ITEM_DISPLAY_DU || This flag controls whether the DU type is displayed instead of the item type on item lists in MCS. || SYSTEM ||
|-
| MCS_LOCATION_PROMPT || Prompt for Receipt Location at Receipt || SYSTEM ||
|-
| MCS_MOVE_FULL_CONSIGNMENT || Move all items for an order during MCS split scanning. || SYSTEM ||
|-
| MCS_NEW_DESPATCH_MODE || This flag controls whether the new Despatch screen is run || SYSTEM ||
|-
| MCS_PALLET_LABEL_FORMAT || The format of pallet label produced by the pallet building option when printing pallet labels. || SYSTEM ||
|-
| MCS_PREVENT_UNPLANNED || Prevent unplanned items being scanned for pallet building, despatch and receipt although expected for the route (Y/N)? || SYSTEM ||
|-
| MCS_RECEIVE_TO_PLAN || Enforce the receipt scanning of packages and pallets to the planned trips? (Y/N) || SYSTEM ||
|-
| MCS_SET_PALLET_ID || MCS set item Pallet Id || SYSTEM ||
|-
| MCS_TEMPERATURE_SCAN || Prompt for Temperature Type at MCS Despatch || SYSTEM ||
|-
| MCS_TENDERED_ITEMS || This flag controls whether MCS items are generated at the change to TENDERED status as well as at ACCEPTED status, or just ACCEPTED status. || SYSTEM ||
|-
| MCS_UPDATE_SCAN_IMMEDIATELY || Allow items to count as despatched immediately after scanning? (Y/N) || SYSTEM ||
|}

== MCS Control Parameters ==
This will be set up by your Aptean implementation team.

This controls which cost centre is used for MCS reason codes.

{| class="wikitable apt-searchable" border="1" width="100%"
|-
!CTP_KEY !!CTP_VALUE !!CTP_UPDATE_COUNTER !!CTP_SITE_ID !!CTP_SYNC_IND !!CTP_DEVICE_SETTING_IND
|-
|DEFAULT_COST_CENTRE ||CONTRACT ||1 ||_ALL_ ||0 ||0
|}

== Standing Data ==
=== Reason Codes ===
Set up for the default cost centre - you will be advised of the cost centre that by your OBS Logistics implementation team.

[[File:CTMS_ReasonCodes.png|border|600px]]

{{Note}} You should set up the standard MCS reasons under your cost centre "+" for reason codes, so that they can be properly displayed on your TMS screens and reports, and so that they are not displayed as reason codes for a user to select on the device. See the recommendations and notes below.

{| class="wikitable" border="1"
|- bgcolor="silver"
! Code !! Description !! Cost Centre !! Notes
|-
| SL || Successfully Loaded || "+" ||  
|-
| SU || Successfully Unloaded || "+" ||  
|-
| ML || Missing Load || MCS CC || 
|-
| NL || Not Loaded || "+" || 
|-
| MI || Moved Item || "+" ||  
|-
| OP || On Pallet || "+" ||  
|-
| FNR || Freight not Received || MCS CC || Only configure if you want Freight Not Received functionality enabled.
|-
| UP || Unpacked Item || "+" ||  
|}

{{Note|
* You should set up these reason codes against the MCS cost centre (set up above in the in the MCS Control Parameters by your implementation team) for the reasons you want to select for damages and exceptions processing only. You should have the Cust Group set to "+" (recommended) or the cust group for which these reason codes apply.
* Any other reason codes that you want displayed on the Item History (on the CTMS Orders screens and extracts) should be set to Cost Centre "+" - these will then not display on the MCS device.
* Reason codes will NOT display descriptions in the MCS Orders screen if the cost centre or cust group do not match the order, or the values of these settings against the reason code are not "+".
* Any reason code that begins with the word "Damaged" (in any case, upper, lower or mixed case) is considered a damages reason code and, regardless of where it is used, will automatically remove the items from any subsequent planned trips.
* Any reason code with action "LATE" can be used to make items available for despatch on other loads. Only configure this action if this is part of your process.
}}

=== Depot Location Configuration ===
Each location to be enabled for C-MCS functionality must be set up as depot type "RDC".

[[File:CTMS_Locations.png|border|600px]]

The following flags may be configured:
* ''MCS Active'' - this flag controls whether C-MCS is used at this location.
* ''MCS Identifier'' - this is an identifier of the depot, used by MCS. This is displayed against items in receipt, so the user can see from which depot the items originated, to aid in unloading.
* ''Receipt Only'' - this flag controls whether the onward stops on this trip (and subsequent trips to the next RDC) are automatically debriefed with the time this stop is debriefed. If set, only the stop being receipted will be debriefed.
* ''Despatch Only'' - this flag controls whether the previous stops on this trip (and prior trips back to the previous RDC) are automatically debriefed with the time this stop is debriefed. If set, only the stop being despatched will be debriefed.
* ''Print Pallet Label'' - this flag controls whether pallets built through C-MCS at this location will use pre-printed stationary (when unchecked), or will print the label from C-MCS (when checked).
* ''Pallet Building validation'' - this flag controls the validation of pallets built through MCS. In all cases, pallets are retained until the pallet is received at the next depot location, whether this is an MCS-enabled location or not. Values are:
** "To Next RDC" - items built onto pallets at this location will be validated that they are all going to the same next depot location;
** "To Final RDC" - items built onto pallets at this location will be validated that they are all going to the same final delivery depot;
** "By Final RDC Trip" - items built onto pallets at this location will be validated that they are all being delivered on the same final delivery trip.

* ''Pallet Building Process'' - values are:
** "Continuous"
** "Single"
* ''Pallet Closure'' - this flag controls whether pallet closure is an option for the C-MCS mobile device users.
* ''Pallet Seal at Closure'' - this option controls whether Seal number will be prompted for at pallet closure. Seal numbers are stored against a pallet in the AWB/Cons reference.
* ''Trans-ship Enabled'' - this flag enables the Trans-Ship process at this location. Trans-ship processing will identify whether the item is planned out of this location on a trip and, if so, will show the user the trip and vehicle and ask them to confirm by entering the vehicle registration. For pallets on the received trip, all items on the pallet must be planned out on the same trip. Successfully trans-shipped items will be marked as despatched on the outbound trip. if any item is not planned out of this location, or not all items on a pallet are planned together, the system will inform the user that trans-ship can't be completed and the items must be despatched separately.
* ''Debrief Stop Times'' - this flag controls whether C-MCS loading or unloading will debrief the stop times at that location.
* ''Set Trip Status at Receipt'' - if checked, the system will attempt to automatically move the trip to COMPLETED status when it is completed in C-MCS.
* ''Set Trip Status at Despatch'' - if checked, the system will attempt to automatically move the trip onto the next applicable status when it is completed in C-MCS. For PLANNED or TENDERED trips, this will be ACCEPTED status. For ACCEPTED trips, this will be EN-ROUTE.

== MCS/WCS Locations ==
If using location confirmation in MCS, then WCS locations must be configured, as well as Locations matching those WCS locations.

WCS Locations are configured in the [[obs:WCS Maintenance|WCS Maintenance]] screen, on the Locations tab.

[[File:Wcs_location.png|border|800px]]

Additionally, the locations should be set up as normal locations.

This is through the standard Locations maintenance screen as above.

Only minor information is required here:
* Location ID - the same as the WCS Location ID.
* Location Type - by convention "WCS", but can be set to any valid location type. Avoid "RDC", "BRANCH", etc.
* Name - set to the name describing the location e.g. "Depot Ambient Receipt", "Depot Chilled Quarantine", etc.

== Reports ==
Extract Suite reports can be configured for your system:
* MCS_DTLS/MCS DETAILS - the items and pallets that are awaiting scanning in your system.
* REASONS/ORD_ITEM_REASON - the reasons against order items, including scan reasons.
* TRIP SCANS/TRIP SCANS - Items scanned for a trip.
* O/S SCANS/MISSING_SCANS - Items not scanned.

[[Category:Guides]]

File:Wcs location.png

2025-09-16T10:30:09Z

Anw:

Setup and Configuration

2025-09-01T10:03:38Z

Anw: Updated

{{Note}} This guide assumes familiarity with C-TMS processes for the following actions:
* Creating users.
* Creating and configuring user groups.
* Adding users to a group.
* Creating label printers.
* Changing user-definable system parameters.
* Finding and amending locations.
* Creating or amending reason codes.
* Running Oracle Reporting Suite data extracts.

== Pre-Requisites ==
The MCS system must be configured and available.

Default cost centre must be configured.

Pallet Label format must be configured for the system.

You will be advised of these details by your OBS Logistics implementation team.

== Access Control ==
=== MCS Users ===
Create MCS users and place them in their own group.

Set up each user with the default pallet label printer. This is dependent on the pallet label format, and should either be a Laser printer or label printer.

You will be advised of the printer type by your OBS Logistics implementation team.

[[File:CTMS_AccessControl3.png|border|600px]]

=== C-TMS Users ===
Provide access to the Shipment Pallets screen from the users' groups.

Set up each user with the default pallet label printer. This is dependent on the pallet label format, and should either be a Laser printer or label printer.

You will be advised of the printer type by your OBS Logistics implementation team.

The group for these users must have additional tabs and screens set up:
* Tabs:
** LOCATION/MCS
* Screens:
** Shipment Pallets

[[File:CTMS_AccessControl1.png|border|600px]]

[[File:CTMS_AccessControl2.png|border|600px]]

== System Parameters ==
These will be initially created and configured by your Aptean implementation team.

[[File:CTMS_Parameters1.png|border|600px]]

You may modify all of these parameters using the system parameters maintenance screen in CTMS.

{{Note}} Each of the parameters you can configure here are system-wide parameters and affect the functioning of MCS in your entire operation. You should take care in changing these parameters. Other configuration exists against the specific location, to affect functionality at that location alone.

{| class="wikitable apt-searchable" border="1" width="100%"
|- bgcolor="silver"
!Parameter !! Description !! Level !! Notes
|-
| MCS_AWB_REQUIRED || This flag control whether the AWB (Air Way Bill) is requested during the pallet building and despatch processes in C-MCS. || SYSTEM ||
|-
| MCS_DESPATCH_DISPLAY_DROP || Display the Drop Number in the Despatch Screen || SYSTEM ||
|-
| MCS_DESPATCH_TO_PLAN || Enforce the despatch scanning of packages and pallets to the planned trips? (Y/N) || SYSTEM ||
|-
| MCS_DISPLAY_COMMTYPE_HAZ || This flag controls whether commodity code and hazardous information is displayed against items and pallets in C MCS pallet building. || SYSTEM ||
|-
| MCS_DISPLAY_PROD_TYPE || This flag controls whether the Product Type is displayed against items and pallets in C- MCS in receipt, despatch and pallet building. || SYSTEM ||
|-
| MCS_EXCEPTIONS_DAMAGED || MCS exceptions at Receipt (excluding FNR and LATE) and Despatch will be marked as damaged items and be removed from onward trips (Y/N). || SYSTEM ||
|-
| MCS_FAST || This parameter will control the level of validation performed during MCS scanning. || SYSTEM ||
|-
| MCS_ITEM_DISPLAY_DU || This flag controls whether the DU type is displayed instead of the item type on item lists in MCS. || SYSTEM ||
|-
| MCS_LOCATION_PROMPT || Prompt for Receipt Location at Receipt || SYSTEM ||
|-
| MCS_PALLET_LABEL_FORMAT || The format of pallet label produced by the pallet building option when printing pallet labels. || SYSTEM ||
|-
| MCS_PREVENT_UNPLANNED || Prevent unplanned items being scanned for pallet building, despatch and receipt although expected for the route (Y/N)? || SYSTEM ||
|-
| MCS_RECEIVE_TO_PLAN || Enforce the receipt scanning of packages and pallets to the planned trips? (Y/N) || SYSTEM ||
|-
| MCS_SET_PALLET_ID || MCS set item Pallet Id || SYSTEM ||
|-
| MCS_TEMPERATURE_SCAN || Prompt for Temperature Type at MCS Despatch || SYSTEM ||
|-
| MCS_TENDERED_ITEMS || This flag controls whether MCS items are generated at the change to TENDERED status as well as at ACCEPTED status, or just ACCEPTED status. || SYSTEM ||
|-
| MCS_UPDATE_SCAN_IMMEDIATELY || Allow items to count as despatched immediately after scanning? (Y/N) || SYSTEM ||
|}

== MCS Control Parameters ==
This will be set up by your Aptean implementation team.

This controls which cost centre is used for MCS reason codes.

{| class="wikitable apt-searchable" border="1" width="100%"
|-
!CTP_KEY !!CTP_VALUE !!CTP_UPDATE_COUNTER !!CTP_SITE_ID !!CTP_SYNC_IND !!CTP_DEVICE_SETTING_IND
|-
|DEFAULT_COST_CENTRE ||CONTRACT ||1 ||_ALL_ ||0 ||0
|}

== Standing Data ==
=== Reason Codes ===
Set up for the default cost centre - you will be advised of the cost centre that by your OBS Logistics implementation team.

[[File:CTMS_ReasonCodes.png|border|600px]]

{{Note}} You should set up the standard MCS reasons under your cost centre "+" for reason codes, so that they can be properly displayed on your TMS screens and reports, and so that they are not displayed as reason codes for a user to select on the device. See the recommendations and notes below.

{| class="wikitable" border="1"
|- bgcolor="silver"
! Code !! Description !! Cost Centre !! Notes
|-
| SL || Successfully Loaded || "+" ||  
|-
| SU || Successfully Unloaded || "+" ||  
|-
| ML || Missing Load || MCS CC || 
|-
| NL || Not Loaded || "+" || 
|-
| MI || Moved Item || "+" ||  
|-
| OP || On Pallet || "+" ||  
|-
| FNR || Freight not Received || MCS CC || Only configure if you want Freight Not Received functionality enabled.
|-
| UP || Unpacked Item || "+" ||  
|}

{{Note|
* You should set up these reason codes against the MCS cost centre (set up above in the in the MCS Control Parameters by your implementation team) for the reasons you want to select for damages and exceptions processing only. You should have the Cust Group set to "+" (recommended) or the cust group for which these reason codes apply.
* Any other reason codes that you want displayed on the Item History (on the CTMS Orders screens and extracts) should be set to Cost Centre "+" - these will then not display on the MCS device.
* Reason codes will NOT display descriptions in the MCS Orders screen if the cost centre or cust group do not match the order, or the values of these settings against the reason code are not "+".
* Any reason code that begins with the word "Damaged" (in any case, upper, lower or mixed case) is considered a damages reason code and, regardless of where it is used, will automatically remove the items from any subsequent planned trips.
* Any reason code with action "LATE" can be used to make items available for despatch on other loads. Only configure this action if this is part of your process.
}}

=== Location Configuration ===
Each location to be enabled for C-MCS functionality must be set up as depot type "RDC".

[[File:CTMS_Locations.png|border|600px]]

The following flags may be configured:
* ''MCS Active'' - this flag controls whether C-MCS is used at this location.
* ''MCS Identifier'' - this is an identifier of the depot, used by MCS. This is displayed against items in receipt, so the user can see from which depot the items originated, to aid in unloading.
* ''Receipt Only'' - this flag controls whether the onward stops on this trip (and subsequent trips to the next RDC) are automatically debriefed with the time this stop is debriefed. If set, only the stop being receipted will be debriefed.
* ''Despatch Only'' - this flag controls whether the previous stops on this trip (and prior trips back to the previous RDC) are automatically debriefed with the time this stop is debriefed. If set, only the stop being despatched will be debriefed.
* ''Print Pallet Label'' - this flag controls whether pallets built through C-MCS at this location will use pre-printed stationary (when unchecked), or will print the label from C-MCS (when checked).
* ''Pallet Building validation'' - this flag controls the validation of pallets built through MCS. In all cases, pallets are retained until the pallet is received at the next depot location, whether this is an MCS-enabled location or not. Values are:
** "To Next RDC" - items built onto pallets at this location will be validated that they are all going to the same next depot location;
** "To Final RDC" - items built onto pallets at this location will be validated that they are all going to the same final delivery depot;
** "By Final RDC Trip" - items built onto pallets at this location will be validated that they are all being delivered on the same final delivery trip.

* ''Pallet Building Process'' - values are:
** "Continuous"
** "Single"
* ''Pallet Closure'' - this flag controls whether pallet closure is an option for the C-MCS mobile device users.
* ''Pallet Seal at Closure'' - this option controls whether Seal number will be prompted for at pallet closure. Seal numbers are stored against a pallet in the AWB/Cons reference.
* ''Trans-ship Enabled'' - this flag enables the Trans-Ship process at this location. Trans-ship processing will identify whether the item is planned out of this location on a trip and, if so, will show the user the trip and vehicle and ask them to confirm by entering the vehicle registration. For pallets on the received trip, all items on the pallet must be planned out on the same trip. Successfully trans-shipped items will be marked as despatched on the outbound trip. if any item is not planned out of this location, or not all items on a pallet are planned together, the system will inform the user that trans-ship can't be completed and the items must be despatched separately.
* ''Debrief Stop Times'' - this flag controls whether C-MCS loading or unloading will debrief the stop times at that location.
* ''Set Trip Status at Receipt'' - if checked, the system will attempt to automatically move the trip to COMPLETED status when it is completed in C-MCS.
* ''Set Trip Status at Despatch'' - if checked, the system will attempt to automatically move the trip onto the next applicable status when it is completed in C-MCS. For PLANNED or TENDERED trips, this will be ACCEPTED status. For ACCEPTED trips, this will be EN-ROUTE.

== Reports ==
Extract Suite reports can be configured for your system:
* MCS_DTLS/MCS DETAILS - the items and pallets that are awaiting scanning in your system.
* REASONS/ORD_ITEM_REASON - the reasons against order items, including scan reasons.
* TRIP SCANS/TRIP SCANS - Items scanned for a trip.
* O/S SCANS/MISSING_SCANS - Items not scanned.

[[Category:Guides]]

Template:MCS Glossary

2025-07-22T11:16:46Z

Anw: Categorisation

{{obs:MCS_Glossary}}

<noinclude>
[[Category:Templates|{{PAGENAME}}]]
[[Category:Glossaries]]
</noinclude>

Template:CTMS Glossary

2025-07-22T11:16:31Z

Anw: Categorisation

{{obs:CTMS_Glossary}}

<noinclude>
[[Category:Templates|{{PAGENAME}}]]
[[Category:Glossaries]]
</noinclude>

Template:EPOD Glossary

2025-07-22T11:16:12Z

Anw: Categorisation

{{obs:EPOD_Glossary_Full}}
<noinclude>
[[Category:Templates|{{PAGENAME}}]]
[[Category:Glossaries]]
</noinclude>

Template:WMS Glossary

2025-07-22T11:15:53Z

Anw: Categorisation

{{obs:WMS_Glossary}}

<noinclude>
[[Category:Templates|{{PAGENAME}}]]
[[Category:Glossaries]]
</noinclude>

Category:Glossaries

2025-07-22T11:15:14Z

Anw: Initial Creation

This page contains all glossaries associated to the product inn this Assist

{{Note}} All glossaries are now held and maintained centrally within the CALIDUS Hub Assist.

Template:WCS Glossary

2025-07-22T11:13:48Z

Anw: Categorisation

{{obs:WCS_Glossary}}

<noinclude>
[[Category:Templates|{{PAGENAME}}]]
[[Category:Glossaries]]
</noinclude>

Template:MCS Glossary

2025-07-18T13:43:48Z

Anw: Interwiki

{{obs:MCS_Glossary}}

<noinclude>
[[Category:Templates|{{PAGENAME}}]]
</noinclude>

Template:CTMS Glossary

2025-07-18T13:42:57Z

Anw: Interwiki

{{obs:CTMS_Glossary}}

<noinclude>
[[Category:Templates|{{PAGENAME}}]]
</noinclude>

Template:EPOD Glossary

2025-07-18T13:42:04Z

Anw: Interwiki

{{obs:EPOD_Glossary_Full}}
<noinclude>
[[Category:Templates|{{PAGENAME}}]]
</noinclude>

Template:WMS Glossary

2025-07-18T13:41:00Z

Anw: Interwiki

{{obs:WMS_Glossary}}

<noinclude>
[[Category:Templates|{{PAGENAME}}]]
</noinclude>

Template:WCS Glossary

2025-07-18T13:40:09Z

Anw: Interwiki

{{obs:WCS_Glossary}}

<noinclude>
[[Category:Templates|{{PAGENAME}}]]
</noinclude>

Setup and Configuration

2025-07-14T14:27:01Z

Anw: Updated to latest version

{{Note}} This guide assumes familiarity with C-TMS processes for the following actions:
* Creating users.
* Creating and configuring user groups.
* Adding users to a group.
* Creating label printers.
* Changing user-definable system parameters.
* Finding and amending locations.
* Creating or amending reason codes.
* Running Oracle Reporting Suite data extracts.

== Pre-Requisites ==
The MCS system must be configured and available.

Default cost centre must be configured.

Pallet Label format must be configured for the system.

You will be advised of these details by your OBS Logistics implementation team.

== Access Control ==
=== MCS Users ===
Create MCS users and place them in their own group.

Set up each user with the default pallet label printer. This is dependent on the pallet label format, and should either be a Laser printer or label printer.

You will be advised of the printer type by your OBS Logistics implementation team.

[[File:CTMS_AccessControl3.png|border|600px]]

=== C-TMS Users ===
Provide access to the Shipment Pallets screen from the users' groups.

Set up each user with the default pallet label printer. This is dependent on the pallet label format, and should either be a Laser printer or label printer.

You will be advised of the printer type by your OBS Logistics implementation team.

The group for these users must have additional tabs and screens set up:
* Tabs:
** LOCATION/MCS
* Screens:
** Shipment Pallets

[[File:CTMS_AccessControl1.png|border|600px]]

[[File:CTMS_AccessControl2.png|border|600px]]

== System Parameters ==
These will be initially created and configured by your Aptean implementation team.

[[File:CTMS_Parameters1.png|border|600px]]

You may modify all of these parameters using the system parameters maintenance screen in CTMS.

{{Note}} Each of the parameters you can configure here are system-wide parameters and affect the functioning of MCS in your entire operation. You should take care in changing these parameters. Other configuration exists against the specific location, to affect functionality at that location alone.

{| class="wikitable apt-searchable" border="1" width="100%"
|- bgcolor="silver"
!Parameter !! Description !! Level !! Notes
|-
| MCS_AWB_REQUIRED || This flag control whether the AWB (Air Way Bill) is requested during the pallet building and despatch processes in C-MCS. || SYSTEM ||
|-
| MCS_DESPATCH_DISPLAY_DROP || Display the Drop Number in the Despatch Screen || SYSTEM ||
|-
| MCS_DESPATCH_TO_PLAN || Enforce the despatch scanning of packages and pallets to the planned trips? (Y/N) || SYSTEM ||
|-
| MCS_DISPLAY_COMMTYPE_HAZ || This flag controls whether commodity code and hazardous information is displayed against items and pallets in C MCS pallet building. || SYSTEM ||
|-
| MCS_DISPLAY_PROD_TYPE || This flag controls whether the Product Type is displayed against items and pallets in C- MCS in receipt, despatch and pallet building. || SYSTEM ||
|-
| MCS_EXCEPTIONS_DAMAGED || MCS exceptions at Receipt (excluding FNR and LATE) and Despatch will be marked as damaged items and be removed from onward trips (Y/N). || SYSTEM ||
|-
| MCS_FAST || This parameter will control the level of validation performed during MCS scanning. || SYSTEM ||
|-
| MCS_ITEM_DISPLAY_DU || This flag controls whether the DU type is displayed instead of the item type on item lists in MCS. || SYSTEM ||
|-
| MCS_LOCATION_PROMPT || Prompt for Receipt Location at Receipt || SYSTEM ||
|-
| MCS_PALLET_LABEL_FORMAT || The format of pallet label produced by the pallet building option when printing pallet labels. || SYSTEM ||
|-
| MCS_PREVENT_UNPLANNED || Prevent unplanned items being scanned for pallet building, despatch and receipt although expected for the route (Y/N)? || SYSTEM ||
|-
| MCS_RECEIVE_TO_PLAN || Enforce the receipt scanning of packages and pallets to the planned trips? (Y/N) || SYSTEM ||
|-
| MCS_SET_PALLET_ID || MCS set item Pallet Id || SYSTEM ||
|-
| MCS_TEMPERATURE_SCAN || Prompt for Temperature Type at MCS Despatch || SYSTEM ||
|-
| MCS_TENDERED_ITEMS || This flag controls whether MCS items are generated at the change to TENDERED status as well as at ACCEPTED status, or just ACCEPTED status. || SYSTEM ||
|-
| MCS_UPDATE_SCAN_IMMEDIATELY || Allow items to count as despatched immediately after scanning? (Y/N) || SYSTEM ||
|}

== MCS Control Parameters ==
This will be set up by your Aptean implementation team.

This controls which cost centre is used for MCS reason codes.

{| class="wikitable apt-searchable" border="1" width="100%"
|-
!CTP_KEY !!CTP_VALUE !!CTP_UPDATE_COUNTER !!CTP_SITE_ID !!CTP_SYNC_IND !!CTP_DEVICE_SETTING_IND
|-
|DEFAULT_COST_CENTRE ||CONTRACT ||1 ||_ALL_ ||0 ||0
|}

== Standing Data ==
=== Reason Codes ===
Set up for the default cost centre - you will be advised of the cost centre that by your OBS Logistics implementation team.

[[File:CTMS_ReasonCodes.png|border|600px]]

{{Note}} You should set up the standard MCS reasons under your standard cost centre for reason codes, so that they can be properly displayed on your TMS screens and reports.

{| class="wikitable" border="1"
|- bgcolor="silver"
! Code !! Description !! Notes
|-
| SL || Successfully Loaded ||  
|-
| SU || Successfully Unloaded ||  
|-
| ML || Missing Load ||  
|-
| NL || Not Loaded ||  
|-
| MI || Moved Item ||  
|-
| OP || On Pallet ||  
|-
| FNR || Freight not Received || Only configure if you want Freight Not Received functionality enabled.
|-
| UP || Unpacked Item ||  
|}

You should set up reason codes against the MCS cost centre for the reasons you want to select for damages and exceptions processing only.
* Any reason code that begins with the word "Damaged" (in any case, upper, lower or mixed case) is considered a damages reason code and, regardless of where it is used, will automatically remove the items from any subsequent planned trips.
* Any reason code with action "LATE" can be used to make items available for despatch on other loads. Only configure this action if this is part of your process.

=== Location Configuration ===
Each location to be enabled for C-MCS functionality must be set up as depot type "RDC".

[[File:CTMS_Locations.png|border|600px]]

The following flags may be configured:
* ''MCS Active'' - this flag controls whether C-MCS is used at this location.
* ''MCS Identifier'' - this is an identifier of the depot, used by MCS. This is displayed against items in receipt, so the user can see from which depot the items originated, to aid in unloading.
* ''Receipt Only'' - this flag controls whether the onward stops on this trip (and subsequent trips to the next RDC) are automatically debriefed with the time this stop is debriefed. If set, only the stop being receipted will be debriefed.
* ''Despatch Only'' - this flag controls whether the previous stops on this trip (and prior trips back to the previous RDC) are automatically debriefed with the time this stop is debriefed. If set, only the stop being despatched will be debriefed.
* ''Print Pallet Label'' - this flag controls whether pallets built through C-MCS at this location will use pre-printed stationary (when unchecked), or will print the label from C-MCS (when checked).
* ''Pallet Building validation'' - this flag controls the validation of pallets built through MCS. In all cases, pallets are retained until the pallet is received at the next depot location, whether this is an MCS-enabled location or not. Values are:
** "To Next RDC" - items built onto pallets at this location will be validated that they are all going to the same next depot location;
** "To Final RDC" - items built onto pallets at this location will be validated that they are all going to the same final delivery depot;
** "By Final RDC Trip" - items built onto pallets at this location will be validated that they are all being delivered on the same final delivery trip.

* ''Pallet Building Process'' - values are:
** "Continuous"
** "Single"
* ''Pallet Closure'' - this flag controls whether pallet closure is an option for the C-MCS mobile device users.
* ''Pallet Seal at Closure'' - this option controls whether Seal number will be prompted for at pallet closure. Seal numbers are stored against a pallet in the AWB/Cons reference.
* ''Trans-ship Enabled'' - this flag enables the Trans-Ship process at this location. Trans-ship processing will identify whether the item is planned out of this location on a trip and, if so, will show the user the trip and vehicle and ask them to confirm by entering the vehicle registration. For pallets on the received trip, all items on the pallet must be planned out on the same trip. Successfully trans-shipped items will be marked as despatched on the outbound trip. if any item is not planned out of this location, or not all items on a pallet are planned together, the system will inform the user that trans-ship can't be completed and the items must be despatched separately.
* ''Debrief Stop Times'' - this flag controls whether C-MCS loading or unloading will debrief the stop times at that location.
* ''Set Trip Status at Receipt'' - if checked, the system will attempt to automatically move the trip to COMPLETED status when it is completed in C-MCS.
* ''Set Trip Status at Despatch'' - if checked, the system will attempt to automatically move the trip onto the next applicable status when it is completed in C-MCS. For PLANNED or TENDERED trips, this will be ACCEPTED status. For ACCEPTED trips, this will be EN-ROUTE.

== Reports ==
Extract Suite reports can be configured for your system:
* MCS_DTLS/MCS DETAILS - the items and pallets that are awaiting scanning in your system.
* REASONS/ORD_ITEM_REASON - the reasons against order items, including scan reasons.
* TRIP SCANS/TRIP SCANS - Items scanned for a trip.
* O/S SCANS/MISSING_SCANS - Items not scanned.

[[Category:Guides]]

Main Page

2025-05-15T07:46:04Z

Anw: Minor correction

<div style="text-align: center;">[[File:calidus-mcs-logo.png]]</div>

<center><font size="5">Welcome to the ''CALIDUS'' MCS Assist help pages.</font></center>

Here you will find all kinds of guides, from simple to advanced, from user guides to technical implementation guides, all to provide as much information on how to get the best out of your ''CALIDUS'' MCS implementation.

Assuming you are now up and running with your system, why not try to find something you didn't know? Try clicking the 'Did You Know' link below.

<center><font size="5">[[Did You Know]]</font></center>

That's how Assist works - help broken down into bite-sized chunks, designed to help you make the most of your system. If you're familiar with the web and familiar with Wiki, you're going to find it easy to get around in Assist.

If you're coming here as a new user without a clear idea of how ''CALIDUS'' MCS works or what it does, you should start with the overview and glossary of terms - that will give you enough information so that you're clear on what we're achieving with this application. You'll find them first in the list below [[#CALIDUS MCS Overview|here]].

If you're more comfortable with documents rather than web pages, we've got you covered.

Every page here can be downloaded as a PDF (including this one) by clicking the ''Download as PDF'' link in the toolbar, typically on the left of your browser window. That will give you the PDF of just that page, but if you want something more formal, see the heading below called [[#Documents|Documents]] - downloading those as PDFs will give you the formal OBS document. On this page, we've also provided direct links to those document versions - click the {{DocLink|Main Page}} link next to the page.

As you can see, some of the guides are multi-page, so we organise those into categories of pages. Where those pages form a guide themselves (like the Device User Guide), you can use that ''Download as PDF'' link again from the category to get all the pages in one handy guide.

We keep these pages up to date based on the latest available version of ''CALIDUS'' MCS - if you see something you like here, but aren't sure whether your version supports it, why not give our team a call? We can advise you on the steps you need to take to upgrade your system to the latest and greatest.

We're constantly updating the system, and that means that we're constantly updating the documentation too. One of the great things about Wiki pages is that the history is kept, so you can click the ''View History'' link (usually at the top of the page) to see all previous versions of the help page. So, although all the guides are the latest version, you can still access the older pages for reference.

The same is true of any of the pictures that we've uploaded in these guides - click on them and you can see the whole history of that picture. You can download them as well, if you like.

Of course, we also keep PDF copies of the previous version of the documentation when we've finished it, so we can always provide them to you. We've generated them from these Assist pages just like you can - because it's that easy to use.

Below you'll find a link to all the guides in this Assist system.

== ''CALIDUS'' MCS Overview ==
''CALIDUS'' MCS is a mobile website application designed to extend ''CALIDUS'' TMS.

* [[Overview]]
* [[Template: MCS_Glossary|Glossary of Terms]]
* [[Did You Know]]

== [[:Category:Guides|Guides]] ==
* [[:Category:UG 320722 CALIDUS MCS Device User Guide|Device User Guide]] {{DocLink|Category:UG 320722 CALIDUS MCS Device User Guide}}
* [[:Category:UG 320722 CALIDUS MCS C-TMS User Guide|C-TMS User Guide]] {{DocLink|Category:UG 320722 CALIDUS MCS C-TMS User Guide}}
* [[Setup and Configuration]] {{DocLink|Category:OV 320722 CALIDUS MCS Setup Guide}}
* [[OV 320722 CALIDUS MCS Device Advanced Guide]] {{DocLink|Category:OV 320722 CALIDUS MCS Device Advanced Guide}} comprising:
** [[MCS Device Cleardown|Device Cleardown]]
** [[Refresh MCS]]

==[[:Category:Documents|Documents]]==
All documents can be found here:
* [[:Category:Documents]]

[[:Category:UG 320722 CALIDUS MCS Device User Guide|UG 320722 CALIDUS MCS Device User Guide]] {{DocLink|Category:UG 320722 CALIDUS MCS Device User Guide}}

[[:Category:UG 320722 CALIDUS MCS C-TMS User Guide|UG 320722 CALIDUS MCS C-TMS User Guide]] {{DocLink|Category:UG 320722 CALIDUS MCS C-TMS User Guide}}

[[OV 320722 CALIDUS MCS Installation Guide]] {{DocLink|OV 320722 CALIDUS MCS Installation Guide}}

[[OV 320722 CALIDUS MCS Technical Guide]] {{DocLink|OV 320722 CALIDUS MCS Technical Guide}}

[[OV 320722 CALIDUS MCS Processes]] {{DocLink|OV 320722 CALIDUS MCS Processes}}

[[OV 320722 CALIDUS MCS Setup Guide]] {{DocLink|Category:OV 320722 CALIDUS MCS Setup Guide}}

[[OV 320722 CALIDUS MCS Device Advanced Guide]] {{DocLink|Category:OV 320722 CALIDUS MCS Device Advanced Guide}}

==[[:Category:Releases|Releases]]==
All of the release notes for the system can be found here:
* [[:Category:Releases|Releases]]

== Coming Soon ==
This section contains guides that are in progress. Typically, they might be incomplete or less detailed than needed.
We'll link our new guides here, whether we've finished them or not. That way you can see what's around the corner.

*

We also categorise any pages that are considered incomplete. These pages may not be listed above, as they are not new or upcoming guides, but they generally need a little more work to get them to their full potential.

You can find the list here:
* [[:Category:Incomplete|Incomplete Pages]]

== [[:Category:Technical|Technical Details‎]] ==
* [[:Category:Developer Guides‎]]
* [[MCS Process Flows]] {{DocLink|OV 320722 CALIDUS MCS Processes}}

== New Users ==
{{Note}} For new users of ''CALIDUS'' Assist:

Go to the [[Special:Preferences|My Preferences]] link and click on the Editing tab. Check the "Prompt me when entering a blank edit summary" check box and save the settings.

Did You Know

2025-04-24T11:29:32Z

Anw: Added tips on searching Assist

This guide is intended to help you discover features delivered with the ''CALIDUS'' MCS Mobile Control System.

== ''CALIDUS'' MCS ==
=== Configuring the MCS Mobile Application Display ===
Did you know that you can change what is displayed on the monile device in certain screens?

You can change the following against items on the Receipt and Despatch Item list:
* whether to display "PACKAGE"/"PALLET" or the actual TU/DU type is displayed on the second line.
* whether to display the product type on the second line.

You can change the following displayed pallet details when building pallets:
* Product Type.
* Commodity Code.
* Hazardous Type.

Your system administrator can do this through control parameters within your TMS.

=== Look & Feel ===
The mobile device application look and feel can be tailored for your organisation - contact your implementation team for the available styles. Alternatively, OBS can tailor the style just for your organisation.

<gallery widths="200px" heights="320px" perrow="3">
Image:MCS_Login1.png|''Dark mode''
Image:MCS_Login1_redgold.png|''Red/Gold''
Image:MCS_Login1_green.png|''Green''
</gallery>

=== Pallet Labels ===
When you are building pallets up from individual packages, did you know that you can either use your own pre-printed labels instead of printing a label directly from C-MCS?

If you do that, we recommend that the label should have a barcode and human-readable pallet ID, and leave a little bit of space on the label - that way there's some room for you to write on some routing information for the pallet, to help you identify what the eventual destination is.

The C-MCS label that is produced automatically is tailored for the existing operations (meaning that it will include specific transport company headers). Contact OBS Logistics if you want your own customised version. This label format already contains most of the relevant information you would need to successfully route the pallet and to see what kind of products are on the pallet, like:
* Origin - the location where the pallet was built.
* Destination - the next location for the pallet.
* Pallet ID and Barcode.
For those building by final ROC trip, consider the following information:
* Radial Trip - the radial trip ID.
* Driver - the assigned driver of the radial trip.
* Vehicle - the assigned vehicle (tractor) of the radial trip.
For those who operate temperature-controlled or hazardous products, consider the following information:
* Temperature.
* Hazardous information.

Here's an example of what a C-MCS-produced label might look like from a label printer:

<gallery widths="200px" heights="320px" perrow="3">
Image:MCS_Pallet_Label1.png
</gallery>

See also:
* [[Pallet Building]]

== ''CALIDUS'' Assist ==
=== Searching for Help ===
Although all pages from your ''CALIDUS'' system link directly to the appropriate page in this ''CALIDUS'' Assist guide, you can search for help on anything in the system using the search bar. It depends on how you have ''CALIDUS'' Assist configured, but this search bar is normally either in the title at the top of the screen or in the toolbar on the left.

Did you know that you can activate this search at any time using a shortcut key combination of ALT-F? Be aware that these shortcuts are dependent on the browser that you are using, so check for compatibility first.

If you know the name of the page, just type it there and click the '''Go''' button. If you want to search for any text in the page, click the '''Search''' button instead, or just hit enter for ''CALIDUS'' Assist to do it for you.

Some tips on searching:

* If you enter multiple words (like "fixed drop scheduling") without quotes, the search routine will find you pages that match any of the words, but ordered in the most likely order (i.e. with most matches of most words)
* If there is a page called "fixed drop scheduling", you will be taken straight to it.
* If you enter your search with quotes i.e. "fixed drop scheduling", it will find that specific phrase in the pages, rather than any of the words.
* If you enter plus instead of space i.e. fixed+drop+scheduling, you will only get pages in the results that have all 3 words in them, anywhere in the page, in any order.
* You can also control partial word matching with as asterisk. So let's say you are searching for a parameter called AUTO_SCHED something-or-other. Searching for AUTO_SCHED will not bring back any results, as there are no full words or phrases like that. But if you enter AUTO_SCHED_* instead, it will search for words ''starting with'' "AUTO_SCHED" and bring you back some matches.

=== Printing and Exporting ===
You can export pages from ''CALIDUS'' Assist using the ''Download as PDF'' link in the ''Toolbox'' menu, typically on the left.

You can export categories as a full document in the same way - all pages in that category will be included in the PDF in the order in which they are listed in the category.

MediaWiki:Editundo

2024-08-29T07:15:06Z

Anw: Minor correction

undo

Template:Note

2024-08-28T08:26:44Z

Anw: Minor formatting change

<includeonly>{{#if: {{{1|}}}|<div class="block-note"><span class="block-contents">|}}[[Image:Bulbgraph.png|18px|Note|link=]] '''Note:''' {{#if: {{{1|}}}|{{{1}}}</span></div>}}</includeonly><noinclude>
<templatedata>
{
"description": "The following displays the noteicon and the word 'Note:'. You can follow this with whatever text/images/markup you like. {{note}} Try this!. Alternatively, you can pass the warning text as the parameter, for example {{Note|Try this!}}.",
"params": {
"1": {
"label": "Text to be included",
"description": "Note text to be displayed in-line and indented.",
"type": "string"
}
},
"paramOrder": [
"1"
]
}
</templatedata>
[[Category:Templates|{{PAGENAME}}]]
</noinclude>

MediaWiki:Common.js

2024-08-28T08:02:38Z

Anw: Added autofocus back to search when clearing table searches

/* Any JavaScript here will be loaded for all users on every page load. */

// Javascript/jQuery code for searching tables
function search_table(tableID, value){
$('#'+tableID+' tr').each(function(){
var found = 'false';
if (!$(this).hasClass('non-searchable')) {
$(this).each(function(){
if ($(this).find('td.non-searchable').length > 0) {
found = 'true';
} else if (!$(this).find('th').length > 0) {
if($(this).text().toLowerCase().indexOf(value.toLowerCase()) >= 0)
{
found = 'true';
}
} else {
// Always keep the header row
found = 'true';
}
});
if(found == 'true')
{
$(this).show();
}
else
{
$(this).hide();
}
}
});
}
$(document).ready(function(){
// Alternative method - makes all tables with 10 or more rows (including header) searchable automatically
// $("table > tbody > tr:nth-child(10)").closest("table").each(function(index, element) {
$("table.apt-searchable").each(function(index, element) {
var tableID = this.id;
if (tableID == '') {
tableID = "aptSearchableTable_" + (index + 1);
$(this).attr("id", tableID);
}
$('<input type="text" id="'+tableID+'_'+index+'" onkeyup="search_table(\''+tableID+'\',$(this).val())" placeholder="Search the table..."><input type="button" onclick="$(\'#'+tableID+'_'+index+'\').val(\'\');search_table(\''+tableID+'\',\'\');search_table(\''+tableID+'\',\'\');$(\'#'+tableID+'_'+index+'\').focus();" title="Clear Entry" class="apt-search-clear">').insertBefore($(this));
});
});

MCS:Copyrights

2024-08-21T16:49:17Z

Anw: Initial Creation

== Content ==
{{:{{NAMESPACE}}:General_disclaimer}}

== MediaWiki ==
You can find the MediaWiki license, contributors, FOSS attributions and components here:
* [[Special:Version]].

DocTemplate

2024-08-21T09:41:25Z

Anw: 1 revision imported

{{Doc_Title
|System=Calidus TMS
|Title=Execution - Asset Management
|Reference=EXECUTION
|Version=2.0
|Date=11th July 2024
|Sysver=12.45
|Client=Aptean
}}


= Introduction =





{{Note}} Remember this!

{{Warning}} Don't do this!





[[Image:ACCESS_11.png]]

<center>[[Image:ACCESS_11.png]]</center>

<center>[[Image:ACCESS_11.png|800px]]</center>



{| class="wikitable" border="1" width="100%"
|- bgcolor="silver"
!Term or Acronym !! Meaning
|-
|Ad Hoc Collection || Ad Hoc Collections are collections at a consignee or other point, where the actual items to be collected have not been defined, allowing for a free-form scanning of items.
|-
|Another term || Another definition.
|}

{| class="wikitable" border="1" width="100%"
|- bgcolor="silver"
!width="20%"|Term or Acronym !! Meaning
|-
|Ad Hoc Collection || Ad Hoc Collections are collections at a consignee or other point, where the actual items to be collected have not been defined, allowing for a free-form scanning of items.
|-
|Another term || Another definition.
|}



{| class="wikitable apt-searchable" border="1" id="cust_onboard_customer_tags"
|- bgcolor="silver"
!width="20%"|Term or Acronym !! Meaning
|-
|Ad Hoc Collection || Ad Hoc Collections are collections at a consignee or other point, where the actual items to be collected have not been defined, allowing for a free-form scanning of items.
|-
|Another term || Another definition.
|}

== Logon ==

{{:Logon}}

PageTemplate

2024-08-21T09:41:25Z

Anw: 1 revision imported

{{Note}} Remember this!

{{Warning}} Don't do this!







[[Image:ACCESS_11.png]]

<center>[[Image:ACCESS_11.png]]</center>

<center>[[Image:ACCESS_11.png|800px]]</center>



{| class="wikitable" border="1" width="100%"
|- bgcolor="silver"
!Term or Acronym !! Meaning
|-
|Ad Hoc Collection || Ad Hoc Collections are collections at a consignee or other point, where the actual items to be collected have not been defined, allowing for a free-form scanning of items.
|-
|Another term || Another definition.
|}

{| class="wikitable" border="1" width="100%"
|- bgcolor="silver"
!width="20%"|Term or Acronym !! Meaning
|-
|Ad Hoc Collection || Ad Hoc Collections are collections at a consignee or other point, where the actual items to be collected have not been defined, allowing for a free-form scanning of items.
|-
|Another term || Another definition.
|}



{| class="wikitable apt-searchable" border="1" id="cust_onboard_customer_tags"
|- bgcolor="silver"
!width="20%"|Term or Acronym !! Meaning
|-
|Ad Hoc Collection || Ad Hoc Collections are collections at a consignee or other point, where the actual items to be collected have not been defined, allowing for a free-form scanning of items.
|-
|Another term || Another definition.
|}

Template:Xref

2024-08-21T09:41:24Z

Anw: 1 revision imported

<includeonly>
'''{{{Type}}} {{{Num}}}''': ''{{{Text|}}}''
</includeonly><noinclude>
== Usage ==

The following includes the type, number and text passed to the template. The example shows how this may be used within an document template. If not, replace the parameters with literals.
<nowiki>
{{#vardefine:Example|0}}
{{Xref
|Num={{ #vardefineecho: Example | {{ #expr: {{ #var: Example }} + 1 }} }}
|Text=The text describing the cross-reference
}}</nowiki>

{{Xref
|Type=Example
|Num=1
|Text=The text describing the cross-reference
}}

[[Category:Templates|{{PAGENAME}}]]
<templatedata>
{
"params": {
"Type": {
"aliases": [
"1"
],
"label": "Type",
"description": "The cross reference type e.g. Example, Table, etc",
"type": "string",
"required": true
},
"Num": {
"aliases": [
"2"
],
"label": "Num",
"description": "The cross-reference number",
"type": "number",
"required": true
},
"Text": {
"aliases": [
"3"
],
"label": "Text",
"description": "The text to describe the cross reference.",
"type": "string",
"required": true
}
},
"description": "The following includes the type, number and text passed to the template. The example shows how this may be used within an document template. If not, replace the parameters with literals. \n <nowiki>\n{{#vardefine:Example|0}}\n{{Xref\n|Num={{ #vardefineecho: Example | {{ #expr: {{ #var: Example }} + 1 }} }}\n|Text=The text describing the cross-reference\n}}</nowiki> "
}
</templatedata></noinclude>

Template:Warning

2024-08-21T09:41:24Z

Anw: 1 revision imported

<includeonly>{{#if: {{{1|}}}|<table cellspacing="0" cellpadding="0" border="0" style="background: transparent;"><tr><td nowrap="nowrap" valign="top">}}<span style="position: relative; top: -2px;">[[Image:Attention niels epting.png|18px|Warning|link=]]</span> '''Warning''': {{#if: {{{1|}}}|</td><td valign="top" style="padding-left:0.5em;">{{{1|}}}</td></tr></table>}}</includeonly><noinclude>
<templatedata>
{
"description": "The following displays the warning icon and the word 'Warning:'. You can follow this with whatever text/images/markup you like. {{warning}} Don't do that!. Alternatively, you can pass the warning text as the parameter, for example {{Warning|Don't do that!}}.",
"params": {
"1": {
"label": "Text to be included",
"description": "Warning text to be displayed in-line and indented.",
"type": "string"
}
},
"paramOrder": [
"1"
]
}
</templatedata>
[[Category:Templates|{{PAGENAME}}]]
</noinclude>

Template:Note

2024-08-21T09:41:24Z

Anw: 1 revision imported

<includeonly>{{#if: {{{1|}}}|<div class="block-note"><span class="block-contents">|[[Image:Bulbgraph.png|18px|Note|link=]]}} '''Note:''' {{#if: {{{1|}}}|{{{1}}}</span></div>}}</includeonly><noinclude>
<templatedata>
{
"description": "The following displays the noteicon and the word 'Note:'. You can follow this with whatever text/images/markup you like. {{note}} Try this!. Alternatively, you can pass the warning text as the parameter, for example {{Note|Try this!}}.",
"params": {
"1": {
"label": "Text to be included",
"description": "Note text to be displayed in-line and indented.",
"type": "string"
}
},
"paramOrder": [
"1"
]
}
</templatedata>
[[Category:Templates|{{PAGENAME}}]]
</noinclude>

Template:Incomplete

2024-08-21T09:41:24Z

Anw: 1 revision imported

<includeonly>{{Warning}} This is an incomplete guide.
[[Category:Incomplete]]</includeonly>
<noinclude>
<templatedata>
{
"params": {},
"description": "Inserts a warning stating that the page in incomplete, and adds the page to the Incomplete category."
}
</templatedata>
</noinclude>
<noinclude>
[[Category:Templates|{{PAGENAME}}]]
</noinclude>

Template:Comment

2024-08-21T09:41:24Z

Anw: 1 revision imported

<noinclude>
; Wikitext:
<code><nowiki>{{quote|text=Cry “Havoc,” and let slip the dogs of war.|sign=[[William Shakespeare]]|date=01/01/1889}}</nowiki></code>

; Result:
{{comment|text=Cry “Havoc,” and let slip the dogs of war.|sign=William Shakespeare|date=01/01/1889}}

=== Restrictions ===

If you do not provide quoted text, the template generates a parser error message, which will appear in red text in the rendered page.

If any parameter's actual value contains an equals sign (=), you '''''must''''' use named parameters. (The equals sign gets interpreted as a named parameter otherwise.)

If any parameter's actual value contains characters used for wiki markup syntax (such as vertical bar, brackets, single quotation marks, etc.), you may need to escape it. See [[Template:!]] and friends.

Be wary of URLs which contain restricted characters. The equals sign is especially common.
[[Category:Templates|{{PAGENAME}}]]
<templatedata>
{
"params": {
"text": {
"aliases": [
"1"
],
"label": "Text",
"description": "Quoted/commented text",
"type": "string",
"required": true
},
"sign": {
"aliases": [
"2"
],
"label": "Person",
"description": "Quoted/commenting person",
"type": "wiki-user-name",
"required": true
},
"date": {
"aliases": [
"3"
],
"label": "Date",
"description": "Date of comment",
"type": "date",
"required": true
}
},
"description": "Inserts a comment or quote callout."
}
</templatedata>
</noinclude><includeonly>
<blockquote class="templatequote"><div>{{{text|{{{1|<noinclude>Your comment here</noinclude><includeonly>{{error|Error: No text given for quotation (or equals sign used in the actual argument to an unnamed parameter)}}</includeonly>}}}}}}
</div>{{#if:{{{sign|{{{2|<noinclude>TRUE</noinclude>}}}}}}|<div class="templatequotecite">—{{{sign|{{{2|<noinclude>Someone</noinclude>}}}}}}{{#if:{{{date|{{{3|<noinclude>TRUE</noinclude>}}}}}}|, <cite>{{{date|{{{3|<noinclude>''Date''</noinclude>}}}}}}</cite>}}</div >}}</blockquote><noinclude>
</noinclude>

Template:Doc Title

2024-08-21T09:41:24Z

Anw: 1 revision imported

<includeonly>[[Image:Aptean Logo.png|150px]]
<br /><br /><br />
<br /><br /><br />
<br /><br />
<font size="4">
{{{Client}}}
</font>
<font size="7">
<br /><br />
{{{Title}}}
</font>
<br /><br />
<font size="5">
{{{System}}} {{#ifeq: {{{Sysver|}}} | | | - {{{Sysver}}} }}
</font>
<br /><br />
<font size="3">
{{{Date}}} {{#ifeq: {{{Version|}}} | | | - <span id="obs_docvers">{{{Version}}}</span> }}
<br />
Reference: {{{Reference}}}
</font>
<br />
<br /><br /><br /><br /><br /><br /><br />
<br /><br /><br /><br /><br /><br /><br />
<br /><br /><br /><br /><br /><br /><br />
<br /><br /><br /><br /><br /><br /><br />
<br /><br /><br /><br /><br /><br /><br />
<br /><br /><br /><br /><br /><br /><br />

</includeonly><noinclude>
<templatedata>
{
"description": "A first document page. Use {{Doc_Title}} passing in the parameters below.",
"params": {
"Client": {
"label": "Client",
"description": "The client, customer or Aptean",
"example": "Aptean",
"type": "string",
"default": "Aptean",
"required": true
},
"Title": {
"label": "Title",
"description": "The title of the document this title is for.",
"example": "Administration - Access Control Guide",
"type": "string",
"required": true
},
"System": {
"label": "System",
"description": "The system to which this document pertains",
"example": "C-TMS",
"type": "string",
"suggestedvalues": [
"C-TMS",
"CALIDUS",
"C-ePOD",
"C-MCS",
"C-Portal",
"C-Portal TTM",
"C-WMS"
],
"default": "C-TMS",
"required": true
},
"Date": {
"label": "Date",
"description": "The date of production",
"example": "31st December 2024",
"type": "string",
"required": true,
"autovalue": "",
"default": "31st December 2024"
},
"Version": {
"label": "Version",
"description": "The version number of the document, e.g. v0.01, v1.00, v2.01. Include the v.",
"example": "v0.01",
"type": "string",
"suggested": true
},
"Reference": {
"label": "Reference",
"description": "A reference for the document. This could be a SalesForce or DevOps reference e.g. SCR-CTMS-12345678-01, or a general reference e.g. ADMINISTRATION",
"type": "string",
"required": true
},
"Sysver": {
"label": "Sysver",
"description": "System Version",
"example": "12.45",
"type": "number",
"suggested": true
}
},
"format": "block"
}
</templatedata>
[[Category:Templates|{{PAGENAME}}]]
</noinclude>

Template:DocLink

2024-08-21T09:41:24Z

Anw: 1 revision imported

<noinclude>
[[Category:Templates|{{PAGENAME}}]]
<templatedata>
{
"description": "This is a template to create a link to a PDF document export for a particular page. \n\nThis is achieved with {{DocLink|MyPage}}",
"params": {
"1": {
"label": "Page name",
"type": "wiki-page-name",
"required": true,
"description": "The name of the page that the document will be produced from. Can also be the name of a category by specifying the Category namespace e.g. Did You Know, or Category:Accounts"
}
}
}
</templatedata>
</noinclude><includeonly><span class="apt-doclink">[{{fullurl:{{{1}}}}}?action=pdfbook&format=singlebook&notitle DOC]</span></includeonly>

MCS:Privacy policy

2024-08-21T09:40:49Z

Anw: Initial Creation

All content submitted to this documentation is the property of Aptean and will be made available to all customers of Aptean.

MCS:General disclaimer

2024-08-21T09:40:34Z

Anw: Initial Creation

Copyright Aptean © 2011-{{CURRENTYEAR}}

The information contained herein is the property of Aptean and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied.

MediaWiki:Common.js

2024-08-21T09:39:36Z

Anw: Added searchable tables

/* Any JavaScript here will be loaded for all users on every page load. */

// Javascript/jQuery code for searching tables
function search_table(tableID, value){
$('#'+tableID+' tr').each(function(){
var found = 'false';
if (!$(this).hasClass('non-searchable')) {
$(this).each(function(){
if ($(this).find('td.non-searchable').length > 0) {
found = 'true';
} else if (!$(this).find('th').length > 0) {
if($(this).text().toLowerCase().indexOf(value.toLowerCase()) >= 0)
{
found = 'true';
}
} else {
// Always keep the header row
found = 'true';
}
});
if(found == 'true')
{
$(this).show();
}
else
{
$(this).hide();
}
}
});
}
$(document).ready(function(){
// Alternative method - makes all tables with 10 or more rows (including header) searchable automatically
// $("table > tbody > tr:nth-child(10)").closest("table").each(function(index, element) {
$("table.apt-searchable").each(function(index, element) {
var tableID = this.id;
if (tableID == '') {
tableID = "aptSearchableTable_" + (index + 1);
$(this).attr("id", tableID);
}
$('<input type="text" id="'+tableID+'_'+index+'" onkeyup="search_table(\''+tableID+'\',$(this).val())" placeholder="Search the table..."><input type="button" onclick="$(\'#'+tableID+'_'+index+'\').val(\'\');search_table(\''+tableID+'\',\'\')" title="Clear Entry" class="apt-search-clear">').insertBefore($(this));
});
});

MediaWiki:Gadgets-definition

Anw: 1 revision imported

/* CSS placed here will affect registered users only */
.apt-user-show {display: block !important;}

MediaWiki:Common.js

2024-08-17T07:14:21Z

Anw: 1 revision imported

/* Any JavaScript here will be loaded for all users on every page load. */

// Javascript/jQuery code for searching tables
function search_table(tableID, value){
$('#'+tableID+' tr').each(function(){
var found = 'false';
if (!$(this).hasClass('non-searchable')) {
$(this).each(function(){
if ($(this).find('td.non-searchable').length > 0) {
found = 'true';
} else if (!$(this).find('th').length > 0) {
if($(this).text().toLowerCase().indexOf(value.toLowerCase()) >= 0)
{
found = 'true';
}
} else {
// Always keep the header row
found = 'true';
}
});
if(found == 'true')
{
$(this).show();
}
else
{
$(this).hide();
}
}
});
}
$(document).ready(function(){
$("table.apt-searchable").each(function(index, element) {
if (this.id !== '') {
$('<input type="text" id="'+this.id+'_'+index+'" onkeyup="search_table(\''+this.id+'\',$(this).val())" placeholder="Search the table..."><input type="button" onclick="$(\'#'+this.id+'_'+index+'\').val(\'\');search_table(\''+this.id+'\',\'\')" title="Clear Entry" class="apt-search-clear">').insertBefore($(this));
}
});
});