1. Quality Management Implementation Guide
  2. Understanding Testing

Understanding Testing

After you activate JD Edwards EnterpriseOne Quality Management, you define the tests to perform for a specific branch/plant or for all branch/plants. For example, you can define a test for syrup concentration levels for a soft drink.

You provide this information for each test:

  • Test description.

  • Test effective and expiration dates.

  • Method for recording results.

  • Number of test samples.

  • Method for evaluating results.

  • Information to print on the certificate of analysis.

  • Methods and reference numbers of the American Society of Testing Material (ASTM).

For each test that you set up, you can define whether it is required, optional, or guaranteed. The test type indicates whether you have to enter test results for this test.

This table shows each type of test:

Test Type

Explanation

Required

When you define a test as required, you must enter test results for this test. If the test results indicate failing values, the lot fails and is set to the status that you indicated in the processing options of the Enter Test Results program (P3711). When you do not enter values for a required test, those blank records are considered failing values, and the lot is dispositioned, based on the information in the Accept Quantity or Accept Percentage field for that test.

Optional

When you define a test as optional, you do not have to enter test results for this test. When you do not enter results, the lot does not fail. When you enter failing values for optional tests, however, the lot might fail, based on the information in the Accept Quantity or Accept Percentage field for that test.

Guaranteed

When you define a test as guaranteed, you must enter test results for this test. Guaranteed tests are tests that you certify as being a part of the quality assurance methodology of the organization. You can set the Display/Evaluate Test option in the test definition to not display test results at test results entry, but guaranteed tests always print on certificates of analysis.

You can use generic text to add information or instructions related to a specific test, such as sampling methods to be used. The system automatically copies generic text from tests to preferences. When you enter test results, you can select a processing option to copy information or instructions from tests or preferences to test results.

Preferences enable you to customize tests and specifications for any combination of:

  • Customer

  • Customer group

  • Item (product)

  • Item group

If you set up alphanumeric test result values, you can set up a UDC list that contains the alphanumeric results and their corresponding numeric values. The system uses this list to determine whether an alphanumeric test result is within the range of minimum and maximum values.

You can also set up alphanumeric test result values without UDCs, which enable you to enter free-form test results. For example, you might set up a test to calibrate equipment and record when the test is performed. In this case, you are not concerned with a test result value.

In addition, you can use the Equipment Row or Form exit to access the Test Equipment Revisions form. You use this form to set up equipment that you use in conjunction with a test. For example, if you use a meter to perform a pH test on a lot of wine, you enter the data about the meter in the system. The system stores equipment data in the Test Equipment (F37011) table. Additionally, you can use the Consumables Row or Form exit to access the Consumables Revisions form. You use this form to set up consumables that you use in conjunction with a test. For example, if you use litmus paper or latex gloves when performing a pH test, you must set up these consumable items in the system. You can then attach these consumables to a test definition. The system stores the information for these items in the Test Consumables (F37012) table.

If you use the JD Edwards EnterpriseOne Blend Management system you perform various quality tests on each lot of wine. You can set up test result names to group similar tests with different test definitions (a set of test specifications). For example, you might have a pH test with a test definition that requires you to use a test strip and another pH test with a test definition that requires you to use a meter. The test definitions are different, but the result from both tests is a pH result.

Note:

When you set up test result names, it is recommended that you do not use a user-defined character in the Test Result           Name field. For example, do not use any user-defined characters that you set on the Pricing Constants form or special characters, such as &, %, !, ?, @, $, | or #. When you use test result names in conjunction with formulas in the JD Edwards  EnterpriseOne Advanced Pricing system, the system does not interpret this symbol in both the formula and the test result name. For example, you want to reduce the purchase price of grapes by 10 percent for every Brix test result below 23. A Brix test result of 22 reduces the price by 10 percent, a Brix test result of 21 reduces the price by 20 percent, and so forth. For example, the formula in Advanced Pricing might be:((23-@BRIX)*-.1)*#UPRC

In this example, the @ symbol is part of the formula to determine the price of the grapes based on the Brix test result. If you use a symbol in the formula and add a test result name with a symbol, the system does not distinguish between the two symbols.

See "Setting Up Quality Management" in the JD Edwards EnterpriseOne Applications Blend Management Implementation Guide.

After you set up tests, you can review and revise them. You can also print a Test Definition report (R37410).