| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| mnSequenceNumber | MATH01 | MATH_NUMERIC | OPT | BOTH |
- - - Good Performance Low Value.
|
| szTestID | QTST | char | OPT | BOTH |
The unique identification for a test to be performed on an item. For example:
COL Color test
DENS Density Test
CL-2 Clarity Test |
| szBusinessUnit | MCU | char | OPT | BOTH |
An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit
might be a warehouse location, job, project, work center, branch, or plant.
You can assign a business unit to a document, entity, or person for
purposes of responsibility reporting. For example, the system provides reports of open accounts payable and accounts receivable by
business unit to track equipment by responsible department.
Business unit security might prevent you from viewing information about business units
for which you have no authority.
|
| jdEffectiveThruDate | EFFT | JDEDATE | OPT | BOTH |
A date that indicates one of the following:
o When a component part is no longer in effect on a bill of material
o When a routing step is no
longer in effect as a sequence on the routing for an item
o When a rate schedule is no longer active The default is December 31 of the
default year defined in the Data Dictionary for Century Change Year. You can enter future effective dates so that the system plans for upcoming
changes. Items that are no longer effective in the future can still be recorded and recognized in Product Costing, Shop Floor Management,
and Capacity Requirements Planning. The Material Requirements Planning system determines valid components by effectivity dates, not by
the bill of material revision level. Some forms display data based on the effectivity dates you enter. |
| jdEffectiveFromDate | EFFF | JDEDATE | OPT | BOTH |
A date that indicates one of the following:
o When a component part goes into effect on a bill of material
o When a routing step goes into
effect as a sequence on the routing for an item
o When a rate schedule is in effect The default is the current system date. You can enter
future effective dates so that the system plans for upcoming changes. Items that are no longer effective in the future can still be recorded and
recognized in Product Costing, Shop Floor Management, and Capacity Requirements Planning. The Material Requirements Planning system
determines valid components by effectivity dates, not by the bill of material revision level. Some forms display data based on the effectivity
dates you enter. |
| cTestType | TTTY | char | OPT | BOTH |
A value that specifies how the system processes tests as you enter test results. Valid values are:
R Required. Result values must be
within the allowable range for the test to pass. The system does not allow an item to pass quality inspection until you enter results for each
required test.
O Optional. Result values are optional during results entry. The system does not require the entry of a result for each optional test.
However, if you enter failing results, the item fails quality inspection.
G Guaranteed. Result values are optional during results entry. You can
control whether Guaranteed tests appear as you enter test results with the Display Test field on Test Revisions. In addition, guaranteed tests
print on the Certificate of Analysis. |
| szAllowableMinimumValue | AMIN | char | OPT | BOTH |
The lowest value for a passing test result. |
| szPreferableMinimumValue | PMIN | char | OPT | BOTH |
The lowest value for the preferred test result. This value must be greater than or equal to the allowed minimum value. Use the preferred
minimum value to measure quality to a more precise specification than a customer requests.
Processing options for the Certificate of Analysis
program allow you to print the preferred value on the Certificate of Analysis report. Processing options for the Test Revisions program allow you
to evaluate samples against the preferred values. |
| szTargetValue | QTRG | char | OPT | BOTH |
The preferable or target test result within the test results range. As the system does not test against a target value, this field is for your
information only. |
| szPreferableMaximumValue | PMAX | char | OPT | BOTH |
The highest value for the preferred test result. This value must be less than or equal to the allowed maximum value. Use the preferred
maximum value to measure quality to a more precise specification than a customer requests.
Processing options for the Certificate of Analysis
program allow you to print the preferred value on the Certificate of Analysis report. Processing options for the Test Revisions program allow you
to evaluate samples against the preferred values. |
| szAllowableMaximumValue | AMAX | char | OPT | BOTH |
The highest value for a passing test result. |
| szProperty | QPRP | char | OPT | BOTH |
The item attribute that is being tested. |
| szTestMethod | TMHD | char | OPT | BOTH |
A description of how to run a quality test. The test method is useful to both your company's Quality Control department and your customers.
For example:
Test: Viscosity
Method: RVF #4 @10RPM
Text: Run the viscosity test on a RVF viscometer with a number 4 spindle
at 10 revolutions per minute. |
| cNumeric10 | NUMT | char | OPT | BOTH |
Determines whether a test result value will be numeric or alphanumeric.
Valid values are:
1 Indicates that the result value is numeric and
should be right justified.
0 Indicates that the result value is alphanumeric and should be left justified. Tests that are using alphanumeric result
values can have User Defined Code tables setup that contain alpha to numeric translations. The purpose of these tables is to supply result
evaluations with a way of determining whether a result is within the range of the minimum and maximum values. |
| szProductCode | SY | char | OPT | BOTH |
A user defined code (98/SY) that identifies a system. Valid values include:
01
Address Book
03B
Accounts Receivable
04
Accounts
Payable
09
General Accounting
11
Multicurrency
|
| szUserDefinedCodes | RT | char | OPT | BOTH |
A code that identifies the table that contains user defined codes. The table is also referred to as a UDC type. |
| szResultUnitofMeasure | RSUM | char | OPT | BOTH |
A user defined code (37/UM) that identifies the unit of measure for a test result. Examples of units of measure include barrels, boxes, cubic
yards, gallons, and hours. |
| mnAcceptQuantity | ACQT | MATH_NUMERIC | OPT | BOTH |
A flag that indicates the quantity of tests that must pass in order for the test sample to pass quality control. The system evaluates this value
when the sample percentage is not equal to 100. To use this accept quantity value, you must complete the following fields on Test Definitions
accordingly:
1 Display/Evaluate
Blank Accept Percentage |
| mnSamplePercentage | SMPC | MATH_NUMERIC | OPT | BOTH |
The percentage of an order quantity that determines the number of samples to create in Test Results Revisions. For example, if the sample
percentage is 50 percent and the order quantity is 10, then 5 samples will be created in Test Results Revisions. Use either this field or
Number of Samples to control how many samples to create. You can use this field only with the order mode of Test Results Revisions.
If the
sample percentage is 100 percent, then testing is required for every unit on the order. You cannot use Accept Percentage or Accept Quantity,
since all units on the order must pass for the lot to pass. |
| cPrintTest | PTTS | char | OPT | BOTH |
A code used to determine whether or not a test will be printed on the Certificate of Analysis. The valid values are:
0 The test will not be
printed on the Certificate of Analysis.
1 Print all occurrences of a test on the Certificate of Analysis.
2 Print just the average test result record
when printing the Certificate of Analysis.
3 Print the last occurrence of a test when printing the Certificate of Analysis. The last occurrence will
be the test results record that was entered last using Test Results Revisions. |
| mnNumberofSamples | QSMP | MATH_NUMERIC | OPT | BOTH |
The number of samples to be taken for the test. |
| cDataDisplayDecimals | CDEC | char | OPT | BOTH |
A value that designates the number of decimals in the currency, amount, or quantity fields the system displays. For example, U.S. Dollars
would be 2 decimals, Japanese Yen would be no decimals, and Cameroon Francs would be 3 decimals. |
| cRecordSelected | EV01 | char | OPT | BOTH |
An option that specifies the type of processing for an event.
|
| mnJobnumber | JOBS | MATH_NUMERIC | OPT | INPUT |
The job number (work station ID) which executed the particular job. |
| cCacheActionCode | ACTN | char | OPT | INPUT |
A code that specifies the action that is performed. Valid values are:
A
Add
C
Change
|
| cReturnCacheCursor | EV01 | char | OPT | INPUT |
An option that specifies the type of processing for an event.
|
| idCacheCursor | GENLNG | ID | OPT | BOTH |
General purpose ID variable. |
| cErrorCodeStatus | ERRC | char | OPT | OUTPUT |
This error code indicates if any errors occurred during the creation of the Trip Document Detail (F4914) records by the Delivery Document
Set Server program (XT4914). |
| cSuppressErrorMessages | EV01 | char | OPT | INPUT |
An option that specifies the type of processing for an event.
|
| szErrorMessage | DTAI | char | OPT | OUTPUT |
A code that identifies and defines a unit of information. It is an alphanumeric code up to 8 characters long that does not allow blanks or
special characters such as %, &, or +. You create new data items using system codes 55-59. You cannot change the alias.
|
| nNumberOfKeys | INT01 | integer | OPT | INPUT |
Number of Days in Future to Query for Responses Due.
|