User Tools

Site Tools


implementation:quality:complete

Produmex Quality

Produmex Quality works as an extension of Produmex WMS. The tool can be used for collecting shopfloor quality assurance data. The quality control task is triggered only if there is a requirement set, otherwise the standard WMS workflow is executed.

1. Installation

1.1. Produmex Suite Installer

Produmex Quality can be installed through Produmex WMS Suite installer.

Follow the steps described in Produmex WMS Installation Guide.

Install Produmex Quality before the configuration of Produmex Tools. The installation steps of Produmex Quality are identical to other Produmex components.
Go to the tab of the server. Press the ‘Install’ button on the line of Produmex Quality. For more information about installing Produmex components please see: Select required components for server

Then run the Produmex Tools configuration as described in 3.2.1. Produmex tools configuration.
Make sure that you upload the Produmex Quality file among the other Produmex Suite add-on files on the AddOnUploaderForm.

1.2. Install Add-On Loader

Install the Add-On Loader as described here: 3.4. Registering the Produmex add-on

1.3. Database setup

The system will set up the database and add the user defined fields when the add-on loader starts the first time after the installation.
A system message will open up to ask the user whether to upgrade the database or not. Click on the ‘Yes’ button to upgrade the database.

Upgrade database

Please note: On MSSQL, the system will check whether there is a backup created within an hour. If no such backup is detected, a warning will be shown and the add-on exists. Create a backup of the database then restart the add-on.

Create backup

On the next screen set up the database connection. Enter the database user name and the database password. After the DB Connection is set up, the system will upgrade the database.

DB connection setup

After the database structure has been modified, another system message is displayed. Click on the ‘Yes’ button to add the user-defined fields.

Add user defined fields

After the user-defined fields have been added, another system message is displayed. Acknowledge the message then restart SAP Business One to apply the changes.

Database upgraded

1.4. Enable Produmex Quality

Open the Organizational Structure from the Produmex module. On the General tab tick the ‘Use Produmex Quality’ checkbox in order to enable Produmex Quality. If Produmex Quality is enabled, the quality capture is triggered based on the set Quality Test Templates and the batch and resource testing workflows are accessible on the fat client.

Use Produmex Quality

2. Setup parameters to test

In order to use Produmex Quality, create quality test templates, parameters and valid values. The test templates contain the quality parameters for evaluation and define the triggering conditions. Valid value type parameters can have predefined values.

2.1. Valid Value Library

Define valid values (define values for valid value type parameters) on the Valid Value Library form. Open the form from Administration > Setup > Quality > Valid Value Library.

  • Code: Unique code that identifies the value. The code is modifiable as long as the value is not in use.
  • Name: The name of the value.
  • Name Translation Key: The localization key that is used for translation. For more information about localization please see: Localization.
    If there is no translation, the key itself is displayed as the value name on the terminal.
  • Remark: Internal remark.
  • Cancelled (Y/N): Indicates whether the valid value is cancelled or not. Cancelled values cannot be linked to a parameter.

To cancel a value, select the ‘Cancel’ option from the right-click menu. Referenced values cannot be cancelled.
To remove a value, select the ‘Remove’ option from the right-click menu. Referenced values cannot be removed.
To restore a cancelled value, select the ‘Restore’ option from the right-click menu. It is not possible to restore removed values.

2.2. Parameters

Define quality parameters to evaluate on the Quality Parameters form. Open the form from Administration > Setup > Quality > Parameters.

  • Code: Unique code that identifies the value. The code is modifiable as long as the parameter is not in use.
  • Name: The name of the parameter. The parameter name must be unique.
  • Cancelled (Y/N): Indicates whether the parameter is cancelled or not. Cancelled parameters cannot be added to a test template.
  • UoM: The unit of measurement of the parameter. It is possible to enter any value as the UoM is not validated against the SBO UoMs. Only meaningful used for float and integer type parameters.
  • Value type: Defines the value type. Supported value types:
    • (1) String: The user can add a sequence of alphanumeric characters as the value. The maximum length is 100 characters.
    • (2) Float: The user can add a number with decimals as the value.
    • (3) Integer: The user can add a whole number as the value.
    • (4) Boolean: The parameter can have a Yes or No value. Please note: Currently this parameter type is not supported.
    • (6) Date: The parameter can have a date value.
    • (7) Time: The parameter can have a time value. Please note: Currently this parameter type is not supported.
    • (8) Valid values: The user can select the value from a list of predefined values.
  • Display Transition Translation: The localization key that is used for translation. For more information about localization please see: Localization.
    If there is no translation, the key itself is displayed as the parameter name on the terminal.
  • Comment: Short description of the parameter that is displayed on the Quality Test Template form.
  • Remark: On this field the user can enter the extended description of the parameter.

To cancel a parameter, select the ‘Cancel’ option from the right-click menu. Referenced parameters cannot be cancelled.
To remove a parameter, select the ‘Remove’ option from the right-click menu. Referenced parameters cannot be removed.
To restore a cancelled parameter, select the ‘Restore’ option from the right-click menu. It is not possible to restore removed parameters.

2.2.1. Settings for Valid value type parameters only

If the parameter value type is ‘Valid Values’, an additional ‘List of Valid Values’ grid is displayed on the screen. At least one valid value must be defined for the parameter in order to create it.

Add a new row to the grid by selecting the ‘Add Row’ option from the right-click menu. After the row is added, select the valid value code on the VV Code field. After the valid value code is filled, the VV Name and Display Translation fields are automatically filled with the Name and the Name Translation Key of the valid value. A valid value can only be added once to a single parameter, but it is possible to add it to multiple different parameters.

To set a valid value as the default, check the ‘Default’ checkbox on the row of the value. It is not possible to set multiple default values.

2.3. Test Template

Create the test templates on the Quality Test Template form. Open the form from Quality > Test Template.

  • Code: Unique code that identifies the test template. The code is modifiable as long as the test template is not in use.
  • Name: The name of the test template. The test template name must be unique.

2.3.1. Rules

Define the triggering conditions for the template on the header.

WMS Workflow Event
First define the WMS workflow event where the template is used. Possible values:

  • None: The Quality capture is not assigned to a workflow event.
  • Release: This setting is reserved for future use.
  • Purchase End: The quality capture is triggered after the Goods Receipt PO document is created in the Reception flow.
  • *Start: The Quality capture is triggered when the production order is started on the terminal. Please note: Quality capture will not be triggered if the production order is started from the Production manager.
  • On Hold: The Quality capture is triggered when the production order is put on hold.
  • Stop: The Quality capture is triggered when the production order is finished.
  • Received: The Quality capture is triggered when the product is received. The action is linked to the Receipt from production document.
  • Issued: The Quality capture is triggered after the materials are issued.
  • Batch: The quality capture can be initiated on the fat client. To test the batch on a scanner, go to Logistics > Inventory > Quality > Batch testing. To test the batch on a touchscreen, go to Quality > Batch testing.
  • Resource: The quality capture can be initiated on the fat client. To test the resource on a scanner, go to Logistics > Inventory > Quality > Resource testing. To test the resource on a touchscreen, go to Quality > Resource testing.
  • Purchase Start: The quality capture is triggered in the following step:
    • GS1/EAN Barcode: After the purchase order is selected.
    • Order: After the purchase order is selected.
    • No PO: After the supplier is selected.
    • Container: After the container is selected.

Failed Quality Status Code
This setting is reserved for future use.

Restrictions
Restriction checkboxes are reserved for future use.

SAP Doc Type
This setting is reserved for future use.

Remark
On this field an internal remark can be added for the test template.

Cancelled
This checkbox indicates whether the template is cancelled or not.

It is possible that multiple templates are defined for a certain item/resource during a WMS workflow event. For example, there is a template defined for the item and the item group it belongs to for the same WMS workflow event. In this case every defined test template is triggered.

Test templates are listed in ascending/alphabetical order based on their Quality Test Template Code.

2.3.2. Parameters

On the grid the parameters that needs to be tested on the run are listed.

Add a new row by selecting the ‘Add Row’ option from the right-click menu.
To remove a row, select the line and choose the ‘Delete Row’ option from the right-click menu.

Click in the Code field and enter the parameter code or select the parameter from a list after clicking on the icon.

After the parameter code is added, the system automatically fills the Name, Value Type, UoM, Display Translation and Comment fields with data from the Parameters form. A parameter can be added more than once to a test template.

Based on the value type of the selected parameter, a different tab is active on the bottom of the screen.

By default columns for every parameter type are displayed on the matrix, but only the Code field is editable. To hide certain columns from the matrix, use the Form settings SBO form.

Other fields of the matrix can be edited on the bottom section of the form. The type of the selected quality parameter determines which tab is active on this section. Users cannot navigate between the tab pages.

To cancel a template, select the ‘Cancel’ option from the right-click menu. Cancelled templates are inactive and are not triggered even when every condition is met.
To remove a template, select the ‘Remove’ option from the right-click menu. Removed templates are deleted and cannot be restored.
To restore a canceled template, select the ‘Restore’ option from the right-click menu.
To create a copy from the template, select the ‘Duplicate’ option from the right-click menu. Add a new test template code and name.

2.3.2.1. Date and Time type parameters

Frequency

  • Minutes: The period in minutes after which the testing of the given parameter must be repeated. If the parameter was tested for the item (group)/ resource (group) within the defined period when the quality control is triggered, the parameter does not have to be tested.
    If no frequency is defined, the parameter must be tested each time the test template is triggered.
2.3.2.2. String type parameters

Frequency

  • Minutes: The period in minutes after which the testing of the given parameter must be repeated. If the parameter was tested for the item (group)/ resource (group) within the defined period when the quality control is triggered, the parameter does not have to be tested.
    If no frequency is defined, the parameter must be tested each time the test template is triggered.

Default value

  • Value: The default value displayed during the quality test.
2.3.2.3. Numeric type parameters

Default value

  • Value: The default value displayed during the quality test.
  • Min Entry: Defines the minimum value that can be entered during the quality control.
  • Max Entry: Defines the maximum value that can be entered during the quality control.

For Float type parameters two additional fields are displayed in the Default value section:

  • Decimals: The number of decimals for the value.
  • Is Weight (Y/N): Indicates whether the parameter is weight or not. This setting is for information only.

Tolerances

  • Min Failure: Defines the minimum value that can be accepted if certain conditions are met and further tests are conducted. If the measured value is equal or greater than the Min Entry and less than the Min Failure, the test for the parameter counts as a failure.
  • Min Tolerance: Defines the minimum value that can be accepted. If the measured value is equal or greater than the Min Failure and less than the Min Tolerance, the test for the parameter counts neither as failure, nor as pass. If the measured value is equal or greater than the Min Tolerance and equal or less than the Max Tolerance, the test for the parameter counts as a pass.
  • Nominal Value: The nominal value for the parameter. This parameter is for information only.
  • Max Tolerance: Defines the maximum value that can be accepted. If the measured value is equal or less than the Max Failure and greater than the Max Tolerance, the test for the parameter counts neither as failure, nor as pass.
  • Max Failure: Defines the maximum value that can be accepted if certain conditions are met and further test are conducted. If the measured value is equal or less than the Max Entry and greater than the Max Failure, the test for the parameter counts as a failure.

Frequency

  • Minutes: The period in minutes after which the testing of the given parameter must be repeated. If the parameter was tested for the item (group)/ resource (group) within the defined period when the quality control is triggered, the parameter does not have to be tested.
    If no frequency is defined, the parameter must be tested each time the test template is triggered.
2.3.2.4. Valid Values type parameters

Default value

  • Value: The default value for the parameter. Every valid value defined for the parameter can be selected, regardless of which value is set as Default for the parameter.

Frequency

  • Minutes: The period in minutes after which the testing of the given parameter must be repeated. If the parameter was tested for the item (group)/ resource (group) within the defined period when the quality control is triggered, the parameter does not have to be tested.
    If no frequency is defined, the parameter must be tested each time the test template is triggered.

3. Basic quality control processes

3.1. Resource testing

To test a resource, start the Resource testing workflow.
The workflow can be initiated from:

  • Scanner: Logistics > Inventory > Quality > Resource testing
  • Touch screen: Quality > Resource testing

Please note: The workflow button is only displayed if the ‘Use Produmex Quality’ option is enabled on the General tab of the Organizational Structure.

If there is a Quality Test Template with 'Resource' type WMS workfow event, the quality testing starts. Otherwise the Scan a resource barcode screen reloads.

3.2. Batch testing

To test a batch, start the Batch testing workflow.
The workflow can be initiated from:

  • Scanner: Logistics > Inventory > Quality > Batch testing
  • Touch screen: Quality > Batch testing

Please note: The workflow button is only displayed if the ‘Use Produmex Quality’ option is enabled on the General tab of the Organizational Structure.

Scan the barcode of the item to test or the SSCC where the item is stored. It is also possible to select the item from a list after pressing the ‘Select item’ button. On the next screen every item that is in stock is listed.

If an SSCC is scanned, it is possible that there are multiple items stored on the logistic unit. In this case scan or select the item after the SSCC has been scanned.

After the item is identified, select the batch from a list. Every batch for the item that is on stock is listed. Displayed information: Batch number, second batch number, best before date, quality status. This screen is automatically skipped if the scanned GTIN contains the batch number or there is only one batch for the selected item on the scanned SSCC.

After the item and batch is identified, the quality testing starts if there is a Quality Test Template that meets the following conditions:

  • The WMS workflow event of the test template is ‘Batch’.
  • The batch rule is enabled.

If there is no such template, the system goes back to the Scan a product screen.

3.3. Reception

It is possible to configure the quality control for the following steps of the reception:

  • After the purchase order is selected in the Reception flow if the following conditions are met:
    • The WMS event is ‘Purchase Start’
  • After the supplier is selected when receiving without a purchase order if the following conditions are met:
    • The WMS event is ‘Purchase Start’
  • After the Goods Receipt PO document is created in the end of the Reception WMS workflow, if the following conditions are met:
    • The WMS event is ‘Purchase End’

Please note: The Failed Quality Status Code set for the test template does not affect the quality status of the received stock by default even if the test result is Fail. Set the quality status with a Produmex Quality user query. If there is no user query that sets the quality status, the quality status is calculated as described in: Quality status at the reception.

Quality Capture triggering points in the Reception flow:

3.4. Production

It is possible to configure the quality control for the following steps of the production:

  • After the Start button is pressed in the Production and the Disassembly flow, if the WMS event is ‘Started’. Please note: If the ‘Allow starting production order on production receipt flow?’ option is enabled on the Production controller, quality capture is triggered when the production order is started in the Production receipt flow.
  • After the produced quantity is entered in the Production, Production receipt and Disassembly flow if the WMS event is ‘Received’.
  • When the production is put on hold in the Production or Disassembly flow, if the WMS event is ‘On hold’.
  • When the production is stopped in the Production or Disassembly flow, if the WMS event is ‘Stop’ and the main product of the production order belongs to the defined item group or is the item set.
  • After the materials are issued in the Production and the Disassembly flow, if the WMS event is ‘Issued’ and the material belongs to the defined item group or is the item set.

Please note: The Failed Quality Status Code set for the test template does not affect the quality status of the received stock by default even if the test result is Fail. Set the quality status with a Produmex Quality user query. If there is no user query that sets the quality status, the quality status of the received product depends on the ‘Quality status production’ setting on the Production tab of the Organizational Structure.

Quality Capture triggering points in the Production flow:

4. Quality Capture screens

The translated parameter name defined on the ‘Display Transition’ field is displayed as the title of the screen.

If a test template contains multiple parameters, the sequence of the parameters is the same as the sequence of the parameters on the grid of the Quality Test Template form.

4.1. String

Enter the string to the input field. You can use the on-screen keyboard to enter the value.

The default value is the Default Value defined on the Quality Test Template form for the parameter. If there is no default value, the field is empty by default.

4.2. Numeric (Float and Integer)

Enter the quantity with the +/- buttons or with the numeric keypad.

In the case of ‘Float’ type parameters, the added value depends on the number of the Decimals defined for the parameter on the Quality Test Template form. Eg.: If the Decimal value is 2 for the parameter, then the added value will be 0.01. If there is an UoM specified for the parameter, it is displayed under the quantity field.

The default value is the Default Value defined on the Quality Test Template form for the parameter. If there is no default value defined, 1 is displayed by default.

Please note: It is possible to enter values outside the Min Entry – Max Entry range.

4.3. Date

Enter the date to the respective field. By default, the system displays the current date.

4.4. Valid Value

Every valid value defined for the parameter is listed on the screen. Valid values are listed in the same sequence as they were defined for the parameter on the Quality Parameters form.

To select a value, press on the line of the value. It is also possible to select a value with the up and down arrows of the keyboard. The selected value is highlighted with blue. The value set as Default Value on the Quality Test Template form is selected by default. If no value is set as default on the Quality Test Template form, then the valid value marked as Default on the Quality Parameters form is selected by default. If there is no default value set on either form, the first value listed on the Quality Parameters grid is selected by default.

When the list is too long to be displayed on one screen, use the green up and down arrows to scroll through the list. It is possible to filter the list. Enter text to the filter field, and the system only lists elements whose name includes the text that has been entered.

5. Quality control results

The result of the quality tests is displayed on the Quality Test Results form. Open the form from: Quality>Test Results.

The header fields work as filters. Fill in the field you would like to use for filtering then click on the ‘Find’ button to display the results.

5.1. Filter fields

  • Document Number: Filters the results based on the document number of test results.
  • Quality Template: Filters the results based on the code of the used Quality Test Template.
  • Item: Filters the result for the tested item only.
  • Item Group: This filter is reserved for future use.
  • Supplier: Filters based on the supplier.
  • Supplier Group: This filter is reserved for future use.
  • Resource: Enter the barcode of the resource to filter the results for the given resource only.
  • Resource Group: This filter is reserved for future use.
  • Batch Number: This filter is reserved for future use.
  • Container number: Filters the results for the added WMS Container code only.
  • SAP Doc Type: This filter is reserved for future use.
  • (SAP) Document number: Filters the results based on the document number of the related SAP document.
  • Date: This filter is reserved for future use.
  • WMS Workflow event: Filters results by the workflow event type.
  • Quality Status Code: This filter is reserved for future use.
  • Warehouse: This filter is reserved for future use.
  • Production line This filter is reserved for future use.
  • User Name: Filters the results by the user who performed the quality control task.

Press the ‘Find’ button to see the results that match the set filters.

5.2. Test results

Every quality test result that matches the set criteria is listed on the grid. The system also fills in every header field that has identical value for each displayed test result.

Additional header fields that are read only:

  • Supervisor: The code of the last user who modified the quality status.
  • Passed (Document): If every displayed test has Passed result, this checkbox is checked.

The displayed results are sorted based on their document number and parameter sequence. If a parameter was evaluated more than once for a document, the results for that parameter are displayed on a single, consolidated line.

  • Document number: The document number of the related test result document.
  • Quality Test Template: The code of the test template that was used during the quality control.
  • Code: The code of the tested parameter.
  • Parameter: The name of the tested parameter.
  • Value type: The value type of the tested parameter.
  • Default value: The default value of the tested parameter.
  • Result: The test result that was entered during quality testing.
  • Passed: If it is checked, the test result of the parameter for the document on the line is passed, otherwise the test is failed. If the parameter was evaluated more than once for the document, then the test is only passed if the parameter passed in every evaluation.
    For numeric values, the result of the first test on the row is indicated with the background coloring:
    • The red color indicates that the entered value falls either between the Max Entry and Max Failure or between the Min Entry and Min Failure set on the Quality Test Template form.
    • The orange color indicates that the entered value falls either between the Max Failure and the Max Tolerance or between the Min Failure and the Min Tolerance set on the Quality Test Template form.
    • The green color indicates that the entered value falls between the Min and Max Tolerance values.
  • Number of Readings: Indicates how many times the parameter was tested for the document on the line.
  • Number of Pass: The number of passed tests for the given parameter and document.
  • Pass %: The percentage of the passed tests for the given parameter and document.
  • Number of Fail: The number of failed tests for the given parameter and document.
  • Fail %: The percentage of the failed tests for the given parameter and document.
  • Decimals: The parameter’s number of decimals. Only meaningful for Float type parameters.
  • User Name: The name of the user who performed the quality test.
  • Transaction date: The date of the test event transaction.

5.2.1. Details

To see the details of a test result, select the line of the result and press the Multiple Results button or double-click on the line. The ‘Multiple Results’ screen opens.

On the header the document number of the test result, the number of readings and the number and percentage of passes and fails for the given document and parameter is listed.

The results of each test for the given parameter and document are displayed on separate lines:

  • LineID: The line number in the test result document. Shows the sequence number of the parameter.
  • Result: The test result that was entered during quality capture.
  • Quality Status: If the quality status of the test result row was changed, this field is filled with the new quality status.
  • Passed (Y/N): If this checkbox is checked, the test is considered as ‘Passed’, otherwise it is considered as ‘Failed’.
  • Reason Code: If the qualification of the result was changed, then the reason for the quality status change is displayed on this field.
  • User Name: The name of the user who performed the quality test.
  • Transaction Date: The date of the test event transaction.

5.2.2. Change Qualification

Select whether you would like to change the qualification for a document or a row.

Set the button to Change Qualification (Document) to change the qualification of the document. The qualification change of a document does not affect the qualification of the rows in the document.

Set the button to Change Qualification (Row) to change the qualification of a row. The qualification change does not affect the qualification of the document.

Select a line and press the corresponding button.

The Change Qualification screen opens. Displayed information:

  • Item Code: The code of the tested item.
  • Batch number: This field is reserved for future use.
  • Document Number: The document number of the test result.
  • Parameter: The code of the tested Quality Parameter. This field is only filled when changing the qualification of a row.

Only users who belong to an authorized user group can change the qualification. User groups can be authorized on the Link usergroup to authorization UDT. Enter the user name to the Supervisor field and the password to the Password field. The Supervisor field is filled with the user name of the logged in user by default.

You can change the result on the Pass/Fail dropdown list.

It is required to select a reason for the qualification change. Select the reason on the Reason Code dropdown list. Every WMS reason that is set for Quality can be selected.

It is also possible to add a remark on the Remark field.

Click on the Change Qualification button to change the qualification or click on the Cancel button to close the screen without saving.

5.2.3. Certificate of Conformity

The Certificate of Conformity button is reserved for future use only.

6. Produmex Quality user queries

The Produmex Quality user queries have the following input parameters:

  • [%1] actionType
  • [%2] objectType
  • [%3] docEntry

6.1. Get QC data to capture

Validation before the QC capture starts. If the query has no result or the result is empty, the Quality Capture is triggered, otherwise the QC will not be triggered and the standard flow proceeds.

Query name: PMXQC_UQ_GETQCDATATOCAPTURE

6.2. Add QC data

Validation after the captured data is saved. If the query has no result or the result is empty, the flow can proceed after the Quality Capture, otherwise the flow will be blocked.

Query name: PMXQC_UQ_ADDQCDATA

6.3. Get quality status

A custom query that determines the quality status based on the captured data. The query is invoked after the quality capture data is saved.

Query name: PMXQC_UQ_GETQUALITYSTATUS

The user query returns the following:

  • Quality status code
  • Update full batch (Y/N)

Please note: The quality status after a receipt can only be updated if the following verifies:

  • The default quality status can be transitioned into the new quality status
  • If the output location is a pick location, the quality status must be allowed on a pick location
implementation/quality/complete.txt · Last modified: 2018/07/19 12:56 by csuhaa