COLANS (Collection Answer)
Retention period : 8 days including current day
BU > FT: data sent from BusinessUnit to Fasttrack
Research criteria
- BU (depending your access): BU (or application) that send information to Fasttrack
- Date based on the integration date & time it has been integrated in Fasttrack.
- You can select one day or a period of day
- If you select more the 5 BUs you will be force to pick up only 1 day
Chart
- COLANS Integration: Provide evolution of the integration over the selected period
- Rule number raised: Provide the top 5 of functional and routing rules raised based on criterias. We are searching for CLS and RTG
- Functional errors & Routed errors (by clicking on the chart you will be redirected to functional error screen):
- Errors: Rejected COLANS (ERROR CLS) / Sent in FT
- Warn: Warnings COLANS (WARN CLR) / Sent in FT
- Routed errors: Rejected COLANS (ERROR RTG) / Sent in FT
Grid - Default Breakdown level (learn how to modify their position here)
- Collecting BU
- Collecting BU / Integration Date
- Collecting BU / Integration Date / Requesting BU
Grid - Column description
| Column Title | Column Description |
|---|---|
| Collecting BU | BU that answer for collection request |
| Integration Date | Date & time when the event has been integrated in FastTrack |
| Requesting BU | BU which made the collection request |
| Status Type | Collection status |
| Sent in FT | This is the number of COLANS that FastTrack receivedfrom your Business Unit on a specific date |
| Warnings checked | Number of COLANS that went through the Warning Functional validation. |
| Warnings | Number of COLANS which raised at least one warning from the functional validation rules in FastTrack |
| Warning ratio | Percentage of COLANS which raised at least one warning from the functional rules. Formula: Warnings/Warnings Checked |
| Rejected | Number of COLANS which raised at least one error from the functional validation rules in FastTrack and were consequently not routed. Unlike the Warnings, CLS-ERROR are all tested |
| Rejected Ratio | Percentage of COLANS which raised at least one error from the functional rules. Formula: Rejected/Sent in FT |
| Routing.Errors | Number of COLANS which raised at least on routing error from the routing rules and were consequently not routed |
| Routing.Errors Ratio | Percentage of COLANS which raised at least one error from the routing rules. Formula: Rounting.Errors/Sent in FT |
| Routed | Count of COLANS which were successfully routed from FastTrack to a Destination BU |
FT > BU: data sent from Fasttrack to Business Unit
Research criteria
- BU (depending your access): BU (or application) where event has been routed
- Date based on the integration date & time it has been integrated in Fasttrack.
- You can select one day or a period of day
- If you select more the 5 BUs you will be force to pick up only 1 day
Grid - Default Breakdown level (learn how to modify their position here)
- Destination BU
- Destination BU / Integration Date
Grid - Column description
| Column Title | Column Description |
|---|---|
| Destination BU | Business that received the COLANS (source: OUT topic) |
| Integration Date | Date & time when the event has been integrated in FastTrack |
| Origin BU | Business Unit from which the COLANS routed to your BU is coming from |
| Received | Count of COLANS that were successfully routed to your Business Unit |
COLREQ pairing: data sent from Fasttrack to Business Unit
Description: This dashboard helps to validate that my selected BU has answered all COLREQ it received Scope:
- Only Cross BU parcel will be checked - First 3 digits of recipientDepot is different from First 3 digits of requestingDepot
- If recipientDepot = null then we ignore this COLANS
- Version 4.x only
- the pairing key is the following:
- COLREQ: requestInfos.crReOrderNr+requestingDepot
- COLANS: ansReOrderNr+requestingDepot
- We can have more than 1 COLANS with the same key, only the first one matter
Research criteria
- BU (depending your access): BU (or application) that send information to Fasttrack
- Date based on the integration date & time it has been integrated in Fasttrack.
- You can select one day or a period of day
- If you select more the 5 BUs you will be force to pick up only 1 day
Grid - Column description
| Column Title | Column Description |
|---|---|
| Collecting BU | BU which answer the collection request |
| Requesting BU | BU which made the collection request |
| Integration Date | Date & time when the event has been integrated in FastTrack |
| CRQ Count | Count the number of COLREQ in the OUT topic of the selected BU |
| CLS Count | Count the number of COLANS that match the COLREQ key in the OUT topic of the selected BU |
| Difference | Count of COLANS that were successfully routed to your Business Unit. |