Once “Prepare QDAS Data List” command is in the script (prerequisite), then based on customer needs, this com- mand provides the ability to add to the QDAS data list.
A comprehensive export option is to use Prepare QDAS Data List along with Add Ke-Field to QDAS Data List and finally
Export QDAS Data List to build a complete *.dfq file for your part.
0 |
String |
Field Name |
Optional info to simplify MP script Reading |
1 |
String |
K-Field |
Mandatory field in the following format: Kxxxx, where xxxx is a numeric value between 1-9999 |
2 |
Integer |
Characteristic Number |
Number to indicate to which characteristic it is applicable. |
3 |
Integer |
Value Max Length |
Mandatory field defined by QDAS Specifications |
4 |
QDAS Value Type |
Value Type |
Mandatory field defined by QDAS Specifications - Pick from List. |
5 |
String |
Value |
A Kxxxx field value in string format that should satisfy require- ments defined by A3 and A4 |
6 |
Integer |
Catalog Entry Identifier |
A Kxxxx field value as a reference to a catalog entry. |
None.
SUCCESS |
The K-Field was defined successfully. |
FAILURE |
The K-Field is invalid or one of its entries. |
Additional Kxxxx field can be added except the “structural info” K5xxx block. The structural information of logical groups in the output DFQ file is generated automatically based on the SA Tree structure. If it is needed user may re- organize SA tree in the desired groups before export.
The structural information of logical groups in the output DFQ file is generated automatically based on SA Tree struc- ture. If needed a user may re-organize the SA tree in the desired groups before initiating Q-DAS export.
Important Notes:
It is a responsibility of user to use Q-DAS specifications to properly define the required K-Field type, max length, and field type. According to entered information, SA will validate user input.
Either A5 or A6 argument must be defined, but not simultaneously. If both arguments have values by mistake, the A6 will define the field’s value.