Jobs Queues – Best Practices

Objectives

This document reflects Isretail’s suggestions for the determination of work queues and the need that some jobs have to run in the same queue. This way we can avoid error situations, such as database locks, etc..

Determinação das filas de trabalho

The determination of the work queues is carried out in the transaction IG018:

Global → Instalattion → Base → Jobq Determination

Let’s segment what kind of jobs should run in the same queues. Priority information will be indicated in the summary table.

Queue A – Expedition

Objects->methods for which it is opportune to determine the dispatch queue:

  • FAPLOG102_dispatchContainers
  • FAPLOG201_closeProcDoc
  • FAPLOG510_checkDifQuant
  • FAPLOG520_createTravelDoc2Trans
  • FAPLOG520_createTravelDocBatch
  • FAPLOG520_printTravelDocBatch
  • FAPLOG520_printTravelDocument
  • FAPLOG940_dispatchVolumes
  • FAPLOG940_transferTourLeftovers

Queue B – Others

Objects->methods for which it is appropriate to determine a generic queue:

  • FAPLOG290_switchWarehouseStatistics
  • FAPLOG230_createArticleInvDocument
  • FAPLOG230_createArticleZeroDocument
  • FINADM03_timesJobsExtractor
  • FAPLOG290_loadContainerDiary
  • FAPLOG290_warehouseCostSpaceAnalisy
  • FINADM02_garbageCollection
  • FAPLOG290_warehouseMovementCostAnalisy
  • FINADM01_auxInterfaceIn
  • FAPLOG510_rePrintTransportationNote

Queue C – Processing

Objects->methods for which it is opportune to determine the processing queue:

  • FAPLOG220_completRequestProcessing
  • FAPLOG230_createDefiniteDocBatch
  • FAPLOG510_createTripBookBatch
  • FAPLOG401_autoPickProcRec
  • FAPLOG940_genExplodedRoutesBatch

Queue D – Posting

Objects->methods for which it is appropriate to determine the posting queue:

  • FAPLOG101_putAwayInRec
  • FAPLOG701_postGoodsDelivery
  • FAPLOG701_postGoodsReturn
  • FAPLOG701_postOtherMovements
  • FAPLOG910_confirmInventoryDocument
  • FAPLOG950_preInvPosting
  • FAPRFS002_closePhisicRecRF
  • FAPLOG601_putawayBySteps
  • FAPLOG310_autoAdminRec
  • FAPLOG101_closeIntMovement
  • FAPLOG410_recAdminBatch
  • FAPLOG103_resetRFqtt
  • FAPLOG701_postExternalDoc
  • FAPLOG101_closeExtMovement
  • FAPLOG401_endPhisicReceiving
  • FAPLOG910_prepareStock2Inventory

Resume

Below is the summary table with the queue and the suggested priority:

Object/Method JobQueuePriority
mandatory
Priority
suggested
FAPLOG102_dispatchContainersA90
FAPLOG201_closeProcDocA50
FAPLOG510_checkDifQuantA10
FAPLOG520_createTravelDoc2TransA90
FAPLOG520_createTravelDocBatchA50
FAPLOG520_printTravelDocBatchA50
FAPLOG520_printTravelDocumentA50
FAPLOG940_dispatchVolumesA90
FAPLOG940_transferTourLeftoversA90
FAPLOG290_switchWarehouseStatisticsB50
FAPLOG230_createArticleInvDocumentB50
FAPLOG230_createArticleZeroDocumentB50
FINADM03_timesJobsExtractorB50
FAPLOG290_loadContainerDiaryB50
FAPLOG290_warehouseCostSpaceAnalisyB50
FINADM02_garbageCollectionB50
FAPLOG290_warehouseMovementCostAnal
isy
B50
FINADM01_auxInterfaceInB50
FAPLOG510_rePrintTransportationNoteB50
FAPLOG220_completRequestProcessingC50
FAPLOG230_createDefiniteDocBatchC50
FAPLOG510_createTripBookBatchC50
FAPLOG401_autoPickProcRecC50
FAPLOG940_genExplodedRoutesBatchC50
FAPLOG101_putAwayInRecD50
FAPLOG701_postGoodsDeliveryD50
FAPLOG701_postGoodsReturnD50
FAPLOG701_postOtherMovementsD50
FAPLOG910_confirmInventoryDocumentD50
FAPLOG950_preInvPostingD50
FAPRFS002_closePhisicRecRFD50
FAPLOG601_putawayByStepsD50
FAPLOG310_autoAdminRecD50
FAPLOG101_closeIntMovementD50
FAPLOG410_recAdminBatchD50
FAPLOG103_resetRFqttD50
FAPLOG701_postExternalDocD50
FAPLOG101_closeExtMovementD50
FAPLOG401_endPhisicReceivingD50
FAPLOG910_prepareStock2InventoryD50

Filas de Trabalho – Best Practices

Objectivos e Âmbito

O presente documento, reflete as sugestões da Isretail para a determinação das filas de trabalho e a necessidade que alguns trabalhos têm como obrigatoriedade de correr na mesma fila para evitar situações de erro, tais como bloqueios de base de dados, etc..

Determinação das filas de trabalho

A determinação das filas de trabalho é efetuada na ação IG018:

Aplicação → Instalação → Base → Determinação Filas de
Trabalho

Vamos segmentar que tipo de trabalhos deverão correr na mesmas filas. A informação das prioridades será indicada no quadro resumo.

Fila A – Expedição

Objectos->métodos para os quais é oportuno determinar a fila das expedições:

  • FAPLOG102_dispatchContainers
  • FAPLOG201_closeProcDoc
  • FAPLOG510_checkDifQuant
  • FAPLOG520_createTravelDoc2Trans
  • FAPLOG520_createTravelDocBatch
  • FAPLOG520_printTravelDocBatch
  • FAPLOG520_printTravelDocument
  • FAPLOG940_dispatchVolumes
  • FAPLOG940_transferTourLeftovers

Fila B – Outros

Objectos->métodos para os quais é oportuno determinar uma fila generica:

  • FAPLOG290_switchWarehouseStatistics
  • FAPLOG230_createArticleInvDocument
  • FAPLOG230_createArticleZeroDocument
  • FINADM03_timesJobsExtractor
  • FAPLOG290_loadContainerDiary
  • FAPLOG290_warehouseCostSpaceAnalisy
  • FINADM02_garbageCollection
  • FAPLOG290_warehouseMovementCostAnalisy
  • FINADM01_auxInterfaceIn
  • FAPLOG510_rePrintTransportationNote

Fila C – Processamento

Objectos->métodos para os quais é oportuno determinar a fila de processamento:

  • FAPLOG220_completRequestProcessing
  • FAPLOG230_createDefiniteDocBatch
  • FAPLOG510_createTripBookBatch
  • FAPLOG401_autoPickProcRec
  • FAPLOG940_genExplodedRoutesBatch

Fila D – Posting

Objectos->métodos para os quais é oportuno determinar a fila dos posting:

  • FAPLOG101_putAwayInRec
  • FAPLOG701_postGoodsDelivery
  • FAPLOG701_postGoodsReturn
  • FAPLOG701_postOtherMovements
  • FAPLOG910_confirmInventoryDocument
  • FAPLOG950_preInvPosting
  • FAPRFS002_closePhisicRecRF
  • FAPLOG601_putawayBySteps
  • FAPLOG310_autoAdminRec
  • FAPLOG101_closeIntMovement
  • FAPLOG410_recAdminBatch
  • FAPLOG103_resetRFqtt
  • FAPLOG701_postExternalDoc
  • FAPLOG101_closeExtMovement
  • FAPLOG401_endPhisicReceiving
  • FAPLOG910_prepareStock2Inventory

Quadro resumo

Abaixo o quadro resumo com a fila e a prioridade sugerida:

Objecto/Método TrabalhoFilaPrioridade
Obrigatória
Prioridade
Sugerida
FAPLOG102_dispatchContainersA90
FAPLOG201_closeProcDocA50
FAPLOG510_checkDifQuantA10
FAPLOG520_createTravelDoc2TransA90
FAPLOG520_createTravelDocBatchA50
FAPLOG520_printTravelDocBatchA50
FAPLOG520_printTravelDocumentA50
FAPLOG940_dispatchVolumesA90
FAPLOG940_transferTourLeftoversA90
FAPLOG290_switchWarehouseStatisticsB50
FAPLOG230_createArticleInvDocumentB50
FAPLOG230_createArticleZeroDocumentB50
FINADM03_timesJobsExtractorB50
FAPLOG290_loadContainerDiaryB50
FAPLOG290_warehouseCostSpaceAnalisyB50
FINADM02_garbageCollectionB50
FAPLOG290_warehouseMovementCostAnal
isy
B50
FINADM01_auxInterfaceInB50
FAPLOG510_rePrintTransportationNoteB50
FAPLOG220_completRequestProcessingC50
FAPLOG230_createDefiniteDocBatchC50
FAPLOG510_createTripBookBatchC50
FAPLOG401_autoPickProcRecC50
FAPLOG940_genExplodedRoutesBatchC50
FAPLOG101_putAwayInRecD50
FAPLOG701_postGoodsDeliveryD50
FAPLOG701_postGoodsReturnD50
FAPLOG701_postOtherMovementsD50
FAPLOG910_confirmInventoryDocumentD50
FAPLOG950_preInvPostingD50
FAPRFS002_closePhisicRecRFD50
FAPLOG601_putawayByStepsD50
FAPLOG310_autoAdminRecD50
FAPLOG101_closeIntMovementD50
FAPLOG410_recAdminBatchD50
FAPLOG103_resetRFqttD50
FAPLOG701_postExternalDocD50
FAPLOG101_closeExtMovementD50
FAPLOG401_endPhisicReceivingD50
FAPLOG910_prepareStock2InventoryD50

Jobs monitoring

Objectives

Controlling the job duration times and monitoring the effectiveness of the services, gives insight about the status of the processes. Considering this, it is necessary to have a simple but effective tool to control this data.

The goal of this guide is to provide the user with understanding on how to obtain information about the duration of job times and job duration status, considering previous durations. This guide will explain the process of obtaining and controlling the information in a step-by-step fashion.

Monitoring job times statistics

Adding the job

To add and control the job times statistics the IA022 transaction was created. To add a job, you must check if it is running in batch on the IA005 transaction.

Global → Installation → Administration → Jobs [IA005]

Choose the proper time frame and click the List button to list the jobs (see the picture above).

Select the job you want to monitor and click on the View button (see the picture above).

Retrieve the Object and Method data (see the picture above). Go back and click on the Parameters button.

Retrieve the site parameter data and the search parameter data (see the picture above).

Next, go to the IA022 transaction:

Global → Installation → Administration → Jobs Statistics Monitor [IA022]

Click on the Add button.

Fill the fields with the data that you have retrieved. Select the proper temporal period. Check the box if you wish to display the job time status when listing jobs and services (explained in the next chapter) and fill the percentage boxes with the values with which you will monitor the job duration status (see the picture above).

In the example above, when listing jobs (or services), a green light will be displayed if the job duration is below the job duration average plus 5% of the job duration average. If the job as a priority of 50 or lower yellow light will be displayed when the job duration exceeds the job duration average plus 5% of the job duration average. If the job as a priority higher than 50 a yellow light will be displayed if the job duration is between the job duration average plus 5% of that job duration average and below the job duration average plus 10% of that job duration average. A red light will be displayed in cases where the job priority is higher than 50 and and the job duration exceeds the job duration average plus 10% of that job duration.

Click on the Confirm Data button.

Generating and monitoring the job data

To generate the job duration data go to the IA023 transaction:

Global → Installation → Administration → Statistics of Jobs [IA023]

Fill the box with the number of records that you want to generate and click the Generate button. In the example above, a 1000 records will be generated for each job that you are monitoring.

Now you can see the statistics of your job in the IA022 transaction:

Global → Installation → Administration → Jobs Statistics Monitor [IA022]

You can choose to monitor the jobs by Object, by Method, by Object and Method, or, if you want to monitor all jobs that you have added, just click on the List button (see the picture above). A view will appear with your configuration. Check the box(es) for the chosen configuration to view its job duration details and click the Next button (see the picture below).

Now you have access to the job duration statistics (the picture below represents part of the table displaying the job statistics data).

Controlling job times

Jobs

If you would like to check if your jobs are within a normal time range of execution, you can access that information in the IA005 transaction:

Global → Installation → Administration → Jobs [IA005]

Fill in the search criteria and click the List button (see the picture above). The following examples will provide you with insight on what you are expected to see:

In the example above, a green light is displayed. The job has a priority of 50 and the job duration is lower than the defined green light duration limit, which the user defined previously in the IA022 transaction (see sub chapter 3.1 for more information on the job duration limits).

In the example above, a yellow light is displayed. The job has a priority of 50 and the job duration is higher than the yellow light duration limit. The same behavior would be expected if the job had a priority higher than 50 and if the job duration was between the time range defined for the green light limit and the yellow light limit (see sub chapter 3.1).

In the example above a red light is displayed. The job has a priority higher than 50 and the job duration exceeded the job duration average plus the percentage of that job duration average for the yellow light (see sub chapter 3.1).

Services

If you would like to check if the jobs on your services list are within a normal time range of execution, you can access that information in the IA004 transaction:

Global → Installation → Administration → Services [IA004]

Choose a service to list it or leave the textbox blank to list all services. Click the List button (see the picture above). The following examples will provide you with insight on what you are expected to see:

Leaving the textbox blank, all services were listed (see the picture above). The service which has jobs in progress displays a green light and its duration. The conditions for the different light colors have been described earlier and will not be discussed further. If you check the box for this service and click the Next Operations button, all jobs of this service are displayed; you moved to the IA005 transaction (see the picture below).

The other cases (for yellow and red lights) follow the same rules and conditions described previously.