Setting Up Supplemental Data for Work Orders

Access the Data Type Revisions form.

Display Mode

Enter a user-defined code (H00/DS) that specifies the format of a data type. This code determines the display mode for supplemental data. Values are:

C: Code format. This mode displays the form for entering code-specific information. These codes might be associated with the F0005 table.

N: Narrative format. This mode displays the form for entering narrative text.

P: Program exit. This mode allows you to exit to the program that you specified in the Program ID field.

M: Message format. This mode displays the form for entering code-specific information. The system can validate the code values that you enter against values in the F00191 table. This code is not used by the Human Capital Management or Financial Management systems.

This is a required field for setting up any data type.

Type Data

Enter a code that you assign to supplemental data so that you can group data by categories. Values include:

A: Approval steps

B: Requisition requirements

C: Interview process

N: Requisition notes

This is a required field for setting up any data type. You can use an existing data type, or you can create a new data type by entering one or two characters for the code.

Display Sequence

Enter a number that specifies the order of a group of records on the form.

This is an optional field for setting up data types. You can specify a display sequence number for each data type. When you use the Work With Supplemental Data form, the data types appear in the order that you specified.

Data Class

Enter a user-defined code (00/CL) that identifies a group of data types in the Central Information File. Values include:

APP: Application call

NAR: Narrative

PUR: Products purchased

This is an optional field for setting up any data type. Data classifications must be set up in UDC Data Classifications (00/CL) before you can use them.

Complete this field to categorize data types by the kind of information that they contain. For example, if you have both narrative and code format data types that contain information about products purchased, you might want to assign the same data classification to both of these data types.

Search Type

Enter a user-defined code (01/ST) that specifies the kind of address book record to search for. Examples include:

E: Employees

X: Ex-employees

V: Suppliers

C: Customers

P: Prospects

M: Mail distribution lists

TAX: Tax authorities

This is an optional field for setting up any data type. Search types must be set up in UDC Search Type (01/ST) before you can use them.

UDC (user-defined code)

Displays a description of a supplemental data column that relates to a user-defined code. For example, if the supplemental data type relates to the educational degrees of employees (BA, MBA, Ph.D., and so on), the description could be Degree. This column contains user-defined codes.

Data that you enter in the UDC (alias GDC1) field overrides the UDC (alias KY) column heading name in the detail area on the General Description Entry form.

You can set up this field as a generic field or as a field that is associated with user-defined codes.

If you leave the corresponding Product Code (alias SY) and Record Type (alias RT) fields blank, then on the General Description Entry form, the system accepts any data (within the size constraints) that you enter in the data entry field for the UDC (alias KY) column.

If you complete the corresponding System Code (alias SY1) and Record Type (alias TR1) fields, then on the General Description Entry form, the system validates the data that you enter in the data entry field for the UDC (alias KY) column.

This is an optional field for setting up supplemental data types in code format.

System Code

Enter a user-defined code (98/SY) that identifies a JD Edwards EnterpriseOne system.

The System Code (alias SY1) and Record Type (alias RT1) fields work together to associate a user-defined codes table to the Remark 1 (alias GDC3) field.

The system uses the user-defined codes table to verify data that you enter in the Remark (alias RMK) field on the General Description Entry form.

For example, if you enter 08 in the System Code (alias SY1) field and SK in the Record Type (alias RT1) field, then on the General Description Entry form, the data that you enter in the Remark (alias RMK) field must exist in the Human Resources system (08), user-defined codes table Skills (SK).

If you leave the System Code (alias SY1) and Record Type (alias RT1) fields blank, then on the General Description Entry form, you can enter any data in the data entry field for the Remark (alias RMK) column.

This is an optional field for setting up supplemental data types in code format.

Record Type

Enter a code that identifies the table that contains user-defined codes. The table is also referred to as a UDC type.

The Record Type (alias RT) and Product Code (alias SY) fields work together to associate a UDC table to the UDC (alias GDC1) field. The system uses the UDC table to verify data that you enter in the UDC (alias KY) field on the General Description Entry form.

For example, if you enter08 in the Product Code (alias SY) field and SK in the Record Type (alias RT) field, then on the General Description Entry form, the data that you enter in the UDC (alias KY) field must exist in the Human Resources system (08), UDC table Skills (SK).

If you leave the Record Type (alias RT) and Product Code (alias SY) fields blank, then on the General Description Entry form, you can enter any data in the data entry field for the UDC (alias KY) column.

This is an optional field for setting up supplemental data types in code format.

Remark 1

Enter the title of a supplemental data column.

Data that you enter in the Remark 1 (alias GDC3) field overrides the Remark (alias RMK) column heading in the detail area on the General Description Entry form.

You can set up this field as a generic field or as a field that is edited against a UDC table.

If you leave the corresponding System Code (alias SY1) and Record Type (alias RT1) fields blank, then on the General Description Entry form, the system accepts any data (within the size constraints) that you enter in the data entry field for the Remark (alias RMK) column.

If you complete the corresponding System Code (alias SY1) and Record Type (alias RT1) fields, then on the General Description Entry form, the system validates the data that you enter in the data entry field for the Remark (alias RMK) column.

This is an optional field for setting up supplemental data types in code format.

Remark 2

Enter the title of a supplemental data column.

Data that you enter in the Remark 2 (alias GDC4) field overrides the Remarks Line 2 (RMK2) column heading in the detail area on the General Description Entry form. You can set up this field as a generic field or as a field that is edited against a UDC table.

If you leave the corresponding System Code (SY2) and Record Type (RT2) fields blank, then on the General Description Entry form, the system accepts any data (within the size constraints) that you enter in the data entry field for the Remarks Line 2 (alias RMK2) column.

If you complete the corresponding System Code (SY2) and Record Type (RT2) fields, then on the General Description Entry form, the system validates the data that you enter in the data entry field for the Remarks Line 2 (alias RMK2) column.

This is an optional field for setting up supplemental data types in code format.

Amount 1

Enter the title of a supplemental data column that relates to an amount. For example, if the data type relates to bid submittals, the heading could be Bid Amounts. This column contains statistical or measurable information.

Data that you enter in the Amount 1 (alias GDC1) field overrides the User Defined Amount (alias AMTU) column heading name in the detail area on the General Description Entry form.

This is an optional field for setting up supplemental data types in code format.

Amount 2

Enter the title of a supplemental data column that relates to an amount. For example, if the data type relates to stock options, the heading could be Strike Price. This column contains statistical or measurable information.

Data that you enter in the Amount 2 (alias GDC7) field overrides the User Defined Amount #2 (alias AMTV) column heading name in the detail area on the General Description Entry form.

This is an optional field for setting up supplemental data types in code format.

Quantity

Enter the title of a supplemental data column that relates to quantities. For example, if you want to track quantity to be scrapped, a column heading might be Scrapped.

Data that you enter in the Quantity (alias GDC0) field overrides the Quantity Ordered (alias UORG) column heading name in the detail area on the General Description Entry form.

This is an optional field for setting up supplemental data types in code format.

Effective From

Enter the title of a supplemental data column that relates to a date. For example, a possible column heading for the date field that is linked to a data type for education might be Graduation.

Data that you enter in the Effective From (alias GDC5) field overrides the Effective Date (alias EFT) column heading name in the detail area on the General Description Entry form.

This is an optional field for setting up supplemental data types in code format.

Effective Thru

Enter the title of a supplemental data column that relates to a date. For example, if you set up a record type for professional licenses, a possible column title for the date field might be Expires.

Data that you enter in the Effective Thru (alias GDC6) field overrides the Ending Date (alias EFTE) column heading name in the detail area on the General Description Entry form.

This is an optional field for setting up supplemental data types in code format.

User Date

Enter the title of a supplemental data column that relates to a date. For example, a possible column heading for the date field linked to the education data type might be Graduation.

Data that you enter in the User Date (alias GDCA) field overrides the User Def Days (alias DYUD) column heading name in the detail area on the General Description Entry form.

This is an optional field for setting up supplemental data types in code format.

User Days

Enter the title of a supplemental data column that relates to a heading of a supplemental data column heading for the User Defined Days field (DYUD). For example, a possible column heading for the days field that is linked to scheduling data type might be Lead Time. This column contains numbers.

Data that you enter in the User Days (GDCC) field overrides the User Def Days (alias DYUD) column heading name in the detail area on the General Description Entry form.

This is an optional field for setting up supplemental data types in code format.

User Address

Enter the title of a supplemental data column that relates to addresses. For example, a possible column heading for the address field linked to an education data type might be the College Address.

Data that you enter in the User Address (alias GDCD) field overrides the User Address (alias AN8) column heading name in the detail area on the General Description Entry form.

This is an optional field for setting up supplemental data types in code format.

User Document

Enter the title of a supplemental data field that relates to a document number. For example, if the company handles accounts receivables, a possible column heading might be Invoices. This column contains document numbers.

Data that you enter in the User Document (alias GDC8) field overrides the Related PO/SO No (alias RORN) column heading name in the detail area on the General Description Entry form.

This is an optional field for setting up supplemental data type in code format.