Monitoring Tool (Daily Jobs)

Value

This tool provides the following value:

• Visibility on daily jobs status

• Access to ingested data (including data source and ignored lines file!)

• WH Cut-off set in the platform

• Awareness on the email addresses used for alert notifications

• Duration on data ingestion and replenishment executions separately

​ Main page

This page provides the following information about the daily jobs activated in the tenant:

• Name of the daily job (DIO, Daily process or DC intake)

• Status of the daily jobs

• Number of replenishment executions linked to that job

• Scheduled time

• Completed time

• Author

• Expected duration

• Duration

A date filter is available, so the user can check each day separately. It is possible to check the information of the last 10 days only.

It is also possible to filter (with multi-selection!) via status type.

The page can automatically be refreshed every 1 , 5 , 15 or 30 minutes. This can be selected on the page. However, this functionality is automatically off. A “Refresh” button is available for the user to refresh the page as needed.

 

 

By clicking on the job name, the “job details” page shows up to provide extra information.

Different types of status

To understand the different types of status, it is important to clarify the following concepts:

• Expected duration time: The median execution time for that job over the last two months

• Expected completion time: It is the result of adding the expected duration to the start date and time of the DIO process.

 Job details page

Within each daily job, the user can deep dive to get the following information:

• ID: For NX use only

• Job type: only if it is daily process

• Scheduled: Date and time at which this job should start

• Author: Automatic

• Started: Date and time this job actually started

• Completed: Date and time this job actually finished

 

By clicking on “More details”, the user can get more information:

• Elapsed time: How much time this job has taken to complete. Also the user can see if the job finished earlier or later than expected.

• Deadline: Provides visibility about the WH cut-off time agreed with the customer. If you want to review this deadline, please contact your customer success manager.

• Alert notification email: By clicking on the ​ symbol, it provides visibility on the emails used when an error is triggered. If you need to modify any of the email addresses, please contact your customer success manager.

 

 

Steps section (inside job details page)

Additionally, it is possible visualize the status of each step of the daily jobs: Data extraction, Data transformation (AKA data ingestion), Business Intelligence, Replenishment Executions and Send Waybills.

Each step has a colour coding to monitor their status:

• Pending (white)

• Skipped (grey)

• Running (blue)

• Completed (green)

• Failed (red)

The user can get more information on the data transformation and replenishment executions steps by clicking on the ​ℹ️ symbol

 

 

Data Transformation se‍‍‍ction (inside the Steps section)

It provides a list of the data types expected on the daily job. Within each data type, the user can get different pieces of information

• Product Master:

  • Processed lines: Number of lines processed in the ingested file

  • Ignored lines: Number of lines ignored in the ingested file and a link to download the ignored lines if any

  • Processed sources: Link to download the ingested file

• Product Master Categorization:

  • Processed lines: Number of lines processed in the ingested file

  • Ignored lines: Number of lines ignored in the ingested file and a link to download the ignored lines if any

  • Processed sources: Link to download the ingested file

• Store Master:

  • Processed lines: Number of lines processed in the ingested file

  • Ignored lines: Number of lines ignored in the ingested file and a link to download the ignored lines if any

  • Processed sources: Link to download the ingested file

• Store Master Categorization:

  • Processed lines: Number of lines processed in the ingested file

  • Ignored lines: Number of lines ignored in the ingested file and a link to download the ignored lines if any

  • Processed sources: Link to download the ingested file

• Warehouse Stock:

  • * Full mode strategy: Only available for customers with this feature activated. Full_mode_by_date means that the system will set previous warehouse stock information in the database to 0 considering the dates available in the new file ingested

  • Processed lines: Number of lines processed in the ingested file

  • Ignored lines: Number of lines ignored in the ingested file and a link to download the ignored lines if any

  • Min date: Min date in the ingested file

  • Max date: Max date in the ingested file

  • Total dates: Total number of dates within the ingested file

  • Total SKUs: Total number of SKUs in the file

  • Total Warehouses: Total number of warehouses in the file

  • Processed sources: Link to download the ingested file

• Sales:

  • Processed lines: Number of lines processed in the ingested file

  • Ignored lines: Number of lines ignored in the ingested file and a link to download the ignored lines if any

  • Min date: Min date in the ingested file

  • Max date: Max date in the ingested file

  • Total dates: Total number of dates within the ingested file

  • Total SKUs: Total number of SKUs in the file

  • Total Stores Total number of stores in the file

  • Processed sources: Link to download the ingested file

• Store Stocks:

  • Processed lines: Number of lines processed in the ingested file

  • Ignored lines: Number of lines ignored in the ingested file and a link to download the ignored lines if any

  • Min date: Min date in the ingested file

  • Max date: Max date in the ingested file

  • Total dates: Total number of dates within the ingested file

  • Total SKUs: Total number of SKUs in the file

  • Total Stores Total number of stores in the file

  • Processed sources: Link to download the ingested file

• Linked lines:

  • Processed lines: Number of lines processed in the ingested file

  • Ignored lines: Number of lines ignored in the ingested file and a link to download the ignored lines if any

  • Processed sources: Link to download the ingested file

• Pending Orders:

  • Processed lines: Number of lines processed in the ingested file

  • Ignored lines: Number of lines ignored in the ingested file and a link to download the ignored lines if any

  • Processed sources: Link to download the ingested file

• Product Purchase:

  • Processed lines: Number of lines processed in the ingested file

  • Ignored lines: Number of lines ignored in the ingested file and a link to download the ignored lines if any

  • Processed sources: Link to download the ingested file

• Transit stocks:

  • Processed lines: Number of lines processed in the ingested file

  • Ignored lines: Number of lines ignored in the ingested file and a link to download the ignored lines if any

  • Processed sources: Link to download the ingested file(s)

 

 

Replenishment executions section (inside the Steps section)

 

The Replenishment executions section provides a list of all the replenishment executions linked to that job. A dedicated status for each replenishment is also visible, following the same color coding described in the “Steps section.”

Inside of each replenishment, the user can see:

• Correlation ID: for NX use only

• Replenishment ID: for NX use only

• Waybill sent: Whether a waybill has been generated or not

• Started: Date and time the replenishment scenario started

• Elapsed time: How much time the scenario has taken to complete vs the expected time

• Completed: Time of completion

 

If the scenario is not empty, the user can also see the following information:

• SKU stores: Number of SKU-Store combinations in that scenario

• Product stores: Number of Product-Store combinations in that scenario