Setting Up the Work Order System

This chapter provides an overview of user-defined codes for work orders and discusses how to:

Set up standard procedures.
Set up default managers and supervisors.
Set up activity rules for work orders.
Set up record type formats.
Set up supplemental data for work orders.
Set up accounting rules for work orders.

Understanding User-Defined Codes for Work Orders

User-defined codes (UDCs) enable you to customize JD Edwards EnterpriseOne Work Orders for particular business needs. Although a number of predefined codes are provided with the Work Orders system, you can revise them and set up new codes.

After you set up user-defined codes, you can assign them to work orders. You can set processing options for the Work With Work Orders program (P48201) so that the system assigns default values for user-defined codes on work orders.

Type Codes (00/TY)

Use these codes to group work orders by type, such as emergency work order or preventive maintenance work order. The system displays this classification code field in the Planning Workbench program.

The Work Order Processing system includes predefined type code values. If these type codes do not meet business needs, you can modify them or create new ones.

Priority Codes (00/PR)

Use these codes to group work orders by priority, such as urgent or low. The system displays this classification code field in the Work with Work Orders program.

Priority codes classify work orders by priority, such as H for high priority and 1 for emergency priority. These codes are for reference only and do not affect the scheduling or planning of work.

When you display work orders using the Work with Work Orders program, the Priority processing option on the Process tab controls whether the program displays the Priority field in a specific color. The values for the colors, which are hard-coded in the Special Handling field of UDC 00/PR, are:

1: Red
2: Yellow
3: Blue

Status Codes (00/SS)

Use these codes to group work orders by current condition. You can update the status code for a work order as work progresses. The system displays this classification code field on a variety of forms related to the life cycle of a work order, such as Work With Work Orders and Work Order Details.

Status codes classify work orders by current status in the work order life cycle, such as A for approved and AP for approval pending. You can update the status code for a work order as work progresses.

Category Code 01 (00/W1)

Category code 01 is a special four-character, user-defined code that appears on all work order forms and reports. You can use category code 01 for the work order phase or matter codes. Use phase or matter codes to:

Group families of work orders into phases or subcategories for project management and cost account purposes.
Group families of work orders on invoices by special matter or explanation code.

If you do not want to use category code 01 for phase and matter codes, you can modify the predefined codes or create new ones.

Phase or matter codes indicate the implementation phase of the work order, such as 2 for project phase 2. You can use phase codes to group work orders for project management and cost accounting purposes.

Category Codes (00/W2 - 00/W0)

Use category codes 02–10 to customize and further define the work orders. (Category code 10 is UDC table 00/W0.) Category codes 02–10 have no predefined values; they can represent any category or description by which you want to group work orders. For example, you can set up a category code to represent types of problems that you encounter in the work order process, such as improper installation or design flaws. Another code might represent locations where work is taking place.

The system displays the first ten category codes in the Planning Workbench program. You can set up these codes to help you limit the search for work orders.

For example, you can set up category code 2 as a work order failure code to indicate reasons for equipment failure. You can then set up codes to indicate equipment failure due to:

Operator error.
Design flaw.
Lubrication or cooling problem.

Detail Specifications Codes (00/RT)

Use work order detail specifications codes to organize the descriptive information that you enter and track for the work orders. Work order detail specifications codes organize the descriptive information that you enter for the work orders, such as S for safety provisions and E for equipment downtime. For example, you might set up work order detail specifications to include these types of information:

Tool and equipment instructions.
Safety provisions.
Equipment downtime.

Work Order Databases (00/WD)

Work order databases group supplemental data types for work orders, such as E for engineering change orders.

Setting Up Standard Procedures

This section provides an overview of standard procedures and discusses how to:

Set processing options for Generic Message/Rates Records (P00191).
Define standard procedures for work orders.

Understanding Standard Procedures

You can set up codes and text to describe standard procedures for work orders. For example, you can:

Designate a specific procedure for a work order or group of work orders.
Provide a list of instructions to complete a work order.
Include messages for work orders.

For example, you might set up code 1000 for a 1000-hour maintenance inspection. For the 1000 code, you can enter text to describe procedures, such as checking coolant levels and adjusting belt tension.

To avoid retyping similar procedures for every work order, you can also copy the appropriate message text from another procedure.

After you set up standard procedures, you can assign them to the appropriate work orders.

Forms Used to Set Up Standard Procedures

Form Name	FormID	Navigation	Usage
Work With Generic Message/Rate Types	W00191A	Use one of these navigations: Work Order Setup (G4841), Standard Procedures Product Data Management Setup (G3041), Std. Procedure Descriptions Shop Floor Management Setup (G3141), Standard Procedures	Review standard procedures for Work Orders, Product Data Management, and Shop Floor Management.
Enter Generic Message/Rates	W00191D	On Work With Generic Message/Rate Types, click Add.	Set up standard procedures. On Enter Generic Message/Rates, enter a code and description on the first available blank line.
General Message	W00191E	On Enter Generic Message/Rates, select the record, and then select General Message from the Row menu.	Add message text to standard procedure.
Standard Text Search	W00192SC	On General Message, select Search from the Row menu. Locate the message number, select the rows of text to copy, and click Select.	Copy message text from one procedure to another

Setting Processing Options for Generic Message/Rates Records (P00191)

Use these processing options to supply the default values for the Generic Message/Rates Records program.

Defaults

1. System Code

Enter a user-defined code (98/SY) that identifies a system. Values include:

01: Address Book

03B: Accounts Receivable

04: Accounts Payable

09: General Accounting

11: Multicurrency

2. Record Type

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

Display

1. Text Type

Specify the type of text that the system displays. Values are:

1: Rate text

2: Message text

2. Text Column Display

Use this processing option to specify the width, in characters, of the text column that the system displays. Values are:

1: 60 characters

2: 80 characters

Defining Standard Procedures for Work Orders

Access the Enter Generic Message/Rates form.

Setting Up Default Managers and Supervisors

This section provides an overview of default managers and supervisors, lists prerequisites, and discusses how to define work order default managers and supervisors.

Understanding Default Managers and Supervisors

You can set up address book information so that certain managers and supervisors appear by default on work orders. This default information is based on any combination of the first three work order category codes that appear on the Enter Work Orders form. The system automatically enters address book values in these fields:

ANPA (Supervisor)
ANSA (Manager)

You can set up as many versions of default managers and supervisors as you need. For example, assume that you have defined work order category code 02 as the failure code. You can assign a specific manager and supervisor to every work order that has a failure code of F1: Improper Start-up or Operation. You can assign another manager and supervisor to every work order that has a failure code of F2: Improper Installation or Repair.

Prerequisites

To use default values for the manager and supervisor address book numbers, set processing options for these programs:

Work Order Entry
Project Setup (P48015)

Forms Used to Set Up Default Managers and Supervisors

Form Name	FormID	Navigation	Usage
Work With Word Order Default Codes	W48001A	Work Order Setup (G4841), Work With Work Order Default Codes	Review work order managers and supervisors.
Default Supervisor and Manager	W48001B	On Work With Work Order Default Codes, click Add.	Define work order default managers and supervisors.

Defining Work Order Default Managers and Supervisors

Access the Default Supervisor and Manager form.

Note. To set up the default information, you must complete at least one user-defined code field and either or both fields associated with a supervisor or a manager.

Phase/System	Enter a user-defined code (00/W1) that indicates the current stage or phase of development for a work order. You can assign a work order to only one phase code at a time. Note. Certain forms contain a processing option that allows you to enter a default value for this field. If you enter a default value on a form for which you have set this processing option, the system displays the value in the appropriate fields on any work orders that you create. The system also displays the value on the Project Setup form. You can either accept or override the default value.
Computer	Enter a user-defined code (00/W3) that indicates the type or category of the work order. Note. A processing option for some forms allows you to enter a default value for this field. The system enters the default value automatically in the appropriate fields on any work orders that you create on those forms and on the Project Setup form. You can either accept or override the default value.
Release	Enter a user-defined code (00/W2) that indicates the type or category of a work order. Note. A processing option for some forms allows you to enter a default value for this field. The system enters the default value automatically in the appropriate fields on any work orders that you create on those forms and on the Project Setup form. You can either accept or override the default value.
Supervisor	Enter the address book number of the supervisor. For some programs, you can use a processing option to specify a default value for this field based on values for category codes (phases) 1, 2 and 3. You can set up the default values in the Work with Work Order Default Codes program (P48001). The system automatically displays the information that you specify on all work orders that you create, provided that you meet the category code criterion. You can override the default value.
Manager	Enter the address book number of a manager or planner. Note. A processing option for some forms allows you to enter a default value for this field based on values for category codes 1 (Phase), 2, and 3. You set up the default values on the Default Managers and Supervisors form. After you set up the default values and the processing option, the default information displays automatically on any work orders that you create if the category code criterion is met. You can either accept or override the default value.

Setting Up Activity Rules for Work Orders

This section provides an overview of work order activity rules and discusses how to:

Set up activity rules.
Define approval routes.
Set processing options for Distribution List Control (P02150).
Set up user profiles.

Understanding Work Order Activity Rules

This section provides overviews of:

Activity rules
Approval routes
User profiles

Activity Rules

Use activity rules to specify the status of a work order at any point in the life cycle. In addition, you use activity rules to:

Select work orders for certain procedures.
Prepare reports that are based on the current status of a work order.
Change the PM (preventive maintenance) status when the work order changes status.
Specify whether the work order is active or inactive at a particular status.
Specify who has the authority to update claims at a certain status (for warranty claims and supplier recovery claims).

You can define activity rules that differ by document type (such as engineering change orders) and classification (such as rework orders).

You must set up a reject code as the last status for any set of activity rules that use an approval process.

Approval Routes

Use approval routing to notify individuals when a work order requires their approval. You can use address book numbers to create various approval routes for individuals who need to be notified when a work order requires approval. You can establish specific approval routes based on approval type and monetary amount. You can also establish specific approval routes based on:

Organizational structure
Work order amount

Note. For Capital Asset Management, approval routes for work orders are available only with a JD Edwards EnterpriseOne workflow process.

User Profiles

You must set up user profiles for all individuals who are designated to approve work orders. When an approver enters a password to complete the approval process, the system validates the password against the employee address book number that you set up in the approver's user profile. The system uses the user ID number to verify that the address book number is valid for the approver.

The system uses the approver's address book number to send electronic mail messages that are associated with work order approvals and to define the work order approval routing.

Forms Used to Set Up Activity Rules for Work Orders

Form Name	FormID	Navigation	Usage
Work with Work Order Activity Rules	W4826C	For the Work Orders system and the Capital Asset Management system: Work Order Setup menu (G4841), Work Order Activity Rules For the Service Management system: Warranty Claim Setup menu (G1747) or Supplier Recovery Setup menu (G1748), Work Order Activity Rules	Add or review activity rules for work orders.
Work Order Activity Rules	W4826D	On Work With Work Order Activity Rules, click Add.	Set up activity rules for work orders.
Reject Status	W4826E	On Work Order Activity Rules, select Reject Status from the Row menu.	Assign a reject status to a rule. This status is necessary only if you use an approval process.
Work With Distribution Lists	W02150A	Workflow Management Setup (G0241), Group Revisions	Define approval routes.
Address Parent/Child Revisions	W0150A	On Work With Distribution Lists, click Add.	Set up approval routes for work orders.
User Profile Revisions	W0092A	System Administration Tools (GH9011), User Profiles On Work With User / Role Profiles, select the user and click Select.	Define user profiles.

Setting Up Activity Rules

Access the Work Order Activity Rules form.

To set up activity rules for work orders :

Complete the fields on the Work Order Activity Rules form.
To define the activity rules for this classification of work orders, complete any of the fields for each activity rule that you need to define.

Note. You must set up status codes for work orders on Work Order Activity Rules before you can use them in the Next Status field or Allowed Status fields.
For each rule that you defined, complete the Edit Authority field.
For each rule that you defined, complete any of the remaining fields.
To assign a reject status to a rule, select the appropriate rule, and then elect Reject Status from the Row menu.

Note. Reject status is necessary only if you will use an approval process.
On Reject Status, complete the Reject Status field and click OK twice.
On Work Order Activity Rules, click OK.

Order Type	Enter a user-defined code (00/DT) that identifies the document type and indicates how the general ledger processes transactions. The Engineering Change Management system uses type EN for engineering change orders.
WO Type (work order type)	Enter a user-defined code (00/TY) that indicates the classification of a work order, such as maintenance work orders, or engineering change orders. You can use work order type as a selection criterion for work order approvals.
WO Status (work order status)	Enter a user-defined code (00/SS) that describes the status of a work order, rate schedule, or engineering change order. Any status change from 90 through 99 triggers the system to automatically update the completion date. You must set up status codes for work orders before you can use them in the Next Status field or Allowed Status field. Do not delete a status code that you have also defined as a next status or other allowed status.
Next Status	Enter the next status for a work order, according to the work order activity rules, as the work order moves through the approval route. You must define a status code as a work order status in the Work Order Activity Rules table before you can use it as a next status.
Allowed Status 1 (Optional)	Indicate a status that can be assigned as the next step in the order process. Although this is not the preferred or expected next step, this status is an allowed override. The system does not allow you to initiate an order line step or status that is not defined as either the expected next status or an allowed status. Other allowed status codes let you bypass processing steps. In processing options, these codes are often referred to as override next status codes. You must define a status code as a work order status in the Work Order Activity Rules table before you can use it as a next status or another allowed status.
Maint. Status (maintenance status)	Enter a user-defined code (12/MS) that indicates the maintenance status of a piece of equipment, such as 50 for maintenance due or 60 for waiting for parts. This UDC is used only in Equipment Management. Note. Status code 98 is reserved for canceled maintenance. Status code 99 is reserved for completed maintenance. Status code 01 (default) is reserved for initial maintenance setup.
Lock Flag	Enter a code that determines whether a work order can be changed at a particular status. The lock applies to records in both the F4801 table and the F4802 table. Values are: Blank: Do not lock the work order. 1: Lock the work order. 2: Lock the work order with a completion date. 3: Do not lock the work order with a completion date. 4: Lock the work order, the parts list, and the routings. 5: Lock the work order, the parts list, and the routings with a completion date. 6: Lock the order type and the work order type only.
Edit Authority	Complete this field for each rule that you define. For warranty claims and supplier recovery claims, the value in this field specifies who has the authority to update claims that have a certain status.
Reject Status	Enter the status that the work order will assume if an approver rejects a work order.

Defining Approval Routes

Access the Address Parent/Child Revisions form.

Parent Number

Enter the address book number of the parent company. The system uses this number to associate a particular address with a parent company or location. Any value that you enter in this field updates the F0150 table for the blank structure type. This address number must exist in the F0101 table for validation purposes. Examples of address book records that would have a parent number include:

Subsidiaries with parent companies.

Branches with a home office.

Job sites with a general contractor.

The address book number of the primary level in a hierarchy, or reporting relationship. A parent in one hierarchy can be a child in another hierarchy. You can organize a hierarchy by business unit, employee, or position. For example, you can create a hierarchy that displays the reporting relationships between employees and supervisors.

Structure Type

Enter a user-defined code (01/TS) that identifies a type of organizational structure that has its own hierarchy in the Address Book system (for example, email). Enter WFS in this field.

When you create a parent/child relationship for the Accounts Receivable system, the structure type must be blank.

On this form, Structure Type identifies the type of distribution list, such as WFS for workflow, ORG for group, and EML for email.

Associated Data Item

Specify the data item that the system uses to retrieve the formatting information on the threshold value. Enter AMTO in this field.

First Response

Review this option to determine how the system handles the first response. If this option is enabled, only one member of a distribution list must respond to the workflow message. When the first response is received by the workflow system, the system cancels the messages that were sent to the other members of the group and marks the task as complete.

If this option is disabled, all members of the group to which the workflow message was sent must respond before the system marks the task as complete.

Higher Level Override

Review this option. If this option is enabled and a person in a higher level group manually approves a workflow transaction (by a workbench program), then the system marks all lower level groups as bypassed.

If this option is disabled and a person in a higher level group manually approves the transaction, the action is logged and all lower level groups are still required to approve the transaction.

Authorization Required

Review this option. If this option is enabled and a person in the distribution list enters a workflow transaction that goes through the distribution list, the system sends the message to the next highest person, even if the threshold has not been reached for the higher person.

If this option is disabled, no higher person is required to see the message as long as it is below the threshold.

Threshold Value

Enter a value that is assigned to individuals within a distribution list to determine if the system includes the individuals in the approval of a workflow task. This value can be any numeric value, such as an amount, quantity, or percentage.

Escalation Hours

Enter the amount of time that must elapse before a message is escalated.

Remark

Enter a remark, description, name, or address.

Begin Eff Date (beginning effective date)

Enter the date on which the address number appears in the structure. The Beginning Effective Date field prevents the address number from occurring in the structure until the beginning effective date is the same as the current date.

If you leave this field blank, the address number always occurs in a structure unless an ending effective date is specified.

End Eff Date (ending effective date)

Enter the date on which the address book record will cease to exist in the structure

Setting Processing Options for Distribution List Control (P02150)

Use these processing options to supply default values for the Distribution List Control program.

Defaults

These processing options specify the default values for the structure type and the version.

1.) Enter the default Structure Type.	Enter a user-defined code (01/TS) that identifies a type of organizational structure that has its own hierarchy in the Address Book system (for example, email). When you create a parent/child relationship for the Accounts Receivable system, the structure type must be blank.
2.) Enter the Version of Organizational Structure Revisions to call. If left blank, version ZJDE0001 is used.	Enter the version to use for the Organizational Structure Revisions program. If you leave this processing option blank, the system uses the ZJDE0001 version.

Setting Up User Profiles

Access the User Profile Revisions form.

Setting Up Record Type Formats

This section provides an overview of record type formats and discusses how to define record type formats for work orders.

Understanding Record Type Formats

You use record types to organize the detail information that you track for work orders. For example, you can organize information such as original task description, tools required, and safety provisions.

The format that you set up determines how the system displays the information. For each record type that you use, you can specify a text format or a format that includes text with three columns. The columnar format is particularly useful when you need to organize and track more than one type of information within a record type. For example, you can set up a record type for required tools and select a three-column format to distinguish tools that are needed for different procedures:

Setup
Production
Tear-down and cleanup

When you use the format for text plus three columns, you must specify at least one of the column headings. Formats that are all text do not include headings. If you specify even one column heading for a record type, the system changes the format to text plus three columns. If you change the format of a record type after you assign it to one or more work orders, the system updates the format of that record type for all work orders.

You can review record types, formats, and column headings using either of these methods:

From the Project Task Details program (P48014), select Record Type from the Form menu on the Enter Work Orders form
From the Enter/Change Order program (P48013), select Record Type Review from the Form menu on the Work Order Details form.

Note. You must set up these record types for Capital Asset Management:

Maintenance Loops

Associated PMs

Forms Used to Set Up Formats for Record Types

Form Name	FormID	Navigation	Usage
Work With Record Types	W4802E	Work Order Setup (G4841), Detail Spec. (Specifications) Over Titles	Review record type formats for work orders.
Record Type Revisions	W4802C	On Work With Record Types, click Add.	Set up record type formats for work orders.

Defining Record Type Formats for Work Orders

Access the Record Type Revisions form.

Record Type

Enter the detail specification record type. Record types are user-defined. You can set them up on the Detail Specification Types form and use them to describe certain types of work order or engineering change order information.

Subtitle 1, Subtitle 2, Subtitle 3

Enter a subtitle, description, remark, name, or address.

The text that you enter in this field appears as a column heading on the Work Order Detail Entry form for the record type that you indicate.

Setting Up Supplemental Data for Work Orders

This section provides an overview of supplemental data and discusses how to set up supplemental data for work orders.

Understanding Supplemental Data

You can enter supplemental data to further define the work orders in the system. Such supplemental data is useful for reporting and tracking work order details that are not included in the record types, such as safety procedures.

You set up and maintain supplemental data in work order databases. Work order databases are user-defined codes (00/WD). For example, you might set up supplemental data for an engineering change order database. The data types might include detail types, pending orders, and so on. You can set up the system to validate that the values that you enter on supplemental data forms match the values that you set up in user-defined code tables.

If the specification data type does not relate to an existing user-defined code or generic message code, you can set up a new user-defined code table. It is recommended that you use systems 55 through 59, inclusive, to set up the new tables. User-defined code tables that you set up for these systems are not modified during any reinstall processes.

Forms Used to Set Up Supplemental Data for Work Orders

Form Name	FormID	Navigation	Usage
Work With Supplemental Database Setup	W00091B	Work Order Setup (G4841), Supplemental Data Setup	Review existing supplemental data.
Data Type Revisions	W00091D	On Work With Supplemental Database Setup, select the database and select Work With Data Type from the Row menu. On Work With Data Types, click Add.	Define supplemental data.

Form Name

FormID

Navigation

Usage

Work With Supplemental Database Setup

W00091B

Work Order Setup (G4841), Supplemental Data Setup

Review existing supplemental data.

Data Type Revisions

W00091D

On Work With Supplemental Database Setup, select the database and select Work With Data Type from the Row menu.

On Work With Data Types, click Add.

Define supplemental data.

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.

Setting Up Accounting Rules for Work Orders

If you apply charges to work orders using the speed entry code on JD Edwards EnterpriseOne Time Accounting or Payroll forms, you must set up the system to distribute the charges to the proper object account. You set up these object accounts in the Accounting JE Rules - Labor/Billings/Equipment program (P069043).

At a minimum, you must set up an object account for default company 00000. You can set up object accounts for other companies, as well. The system always searches for accounting rules by a specific company. If it does not find a company, the system applies rules according to the default company.

Make sure that you have installed at least one of these JD Edwards EnterpriseOne systems:

Workforce Management Foundation (system 05).
Time Accounting (system 05T).
Payroll (system 07).
Canadian Payroll (system 77).

Parent Number	Enter the address book number of the parent company. The system uses this number to associate a particular address with a parent company or location. Any value that you enter in this field updates the F0150 table for the blank structure type. This address number must exist in the F0101 table for validation purposes. Examples of address book records that would have a parent number include: Subsidiaries with parent companies. Branches with a home office. Job sites with a general contractor. The address book number of the primary level in a hierarchy, or reporting relationship. A parent in one hierarchy can be a child in another hierarchy. You can organize a hierarchy by business unit, employee, or position. For example, you can create a hierarchy that displays the reporting relationships between employees and supervisors.
Structure Type	Enter a user-defined code (01/TS) that identifies a type of organizational structure that has its own hierarchy in the Address Book system (for example, email). Enter WFS in this field. When you create a parent/child relationship for the Accounts Receivable system, the structure type must be blank. On this form, Structure Type identifies the type of distribution list, such as WFS for workflow, ORG for group, and EML for email.
Associated Data Item	Specify the data item that the system uses to retrieve the formatting information on the threshold value. Enter AMTO in this field.
First Response	Review this option to determine how the system handles the first response. If this option is enabled, only one member of a distribution list must respond to the workflow message. When the first response is received by the workflow system, the system cancels the messages that were sent to the other members of the group and marks the task as complete. If this option is disabled, all members of the group to which the workflow message was sent must respond before the system marks the task as complete.
Higher Level Override	Review this option. If this option is enabled and a person in a higher level group manually approves a workflow transaction (by a workbench program), then the system marks all lower level groups as bypassed. If this option is disabled and a person in a higher level group manually approves the transaction, the action is logged and all lower level groups are still required to approve the transaction.
Authorization Required	Review this option. If this option is enabled and a person in the distribution list enters a workflow transaction that goes through the distribution list, the system sends the message to the next highest person, even if the threshold has not been reached for the higher person. If this option is disabled, no higher person is required to see the message as long as it is below the threshold.
Threshold Value	Enter a value that is assigned to individuals within a distribution list to determine if the system includes the individuals in the approval of a workflow task. This value can be any numeric value, such as an amount, quantity, or percentage.
Escalation Hours	Enter the amount of time that must elapse before a message is escalated.
Remark	Enter a remark, description, name, or address.
Begin Eff Date (beginning effective date)	Enter the date on which the address number appears in the structure. The Beginning Effective Date field prevents the address number from occurring in the structure until the beginning effective date is the same as the current date. If you leave this field blank, the address number always occurs in a structure unless an ending effective date is specified.
End Eff Date (ending effective date)	Enter the date on which the address book record will cease to exist in the structure

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.