GetRoutingInstructionsData

Get Routing Instructions Data

Minor Business Rule

Object Name: B3100510

Parent DLL: CMFGBASE

Location: Client/Server

Language: C

•
•
•

•
•

Data Structure

D3100510 - Get Routing Instructions Data

Parameter Name Data Item Data Type Req/Opt I/O/Both

mnOrderNumber DOCO MATH_NUMERIC NONE NONE

A number that identifies an original document. This document can be a voucher, a sales order, an invoice, unapplied cash, a journal entry,
and so on.

mnOperationSequence OPSQ MATH_NUMERIC NONE NONE

A number used to indicate an order of succession. In routing instructions, a number that sequences the fabrication or assembly steps in the
manufacture of an item. You can track costs and charge time by operation. In bills of material, a number that designates the routing step in the
fabrication or assembly process that requires a specified component part. You define the operation sequence after you create the routing
instructions for the item. The Shop Floor Management system uses this number in the backflush/preflush by operation process. In engineering
change orders, a number that sequences the assembly steps for the engineering change. For repetitive manufacturing, a number that
identifies the sequence in which an item is scheduled to be produced. Skip To fields allow you to enter an operation sequence that you want to begin
the display of information. You can use decimals to add steps between existing steps. For example, use 12.5 to add a step between steps
12 and 13.

szBusinessUnit MCU char NONE NONE

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.

szTypeOperationCode OPSC char NONE NONE

A user defined code (30/OT) that indicates the type of operation. Valid values include: A Alternate routing   TT Travel time   IT Idle time   T Text

jdStartDate STRT JDEDATE NONE NONE

The start date for the order. You can enter this date manually, or have the system calculate it using a backscheduling routine. The routine
starts with the required date and offsets the total leadtime to calculate the appropriate start date.

jdRequestedDate DRQJ JDEDATE NONE NONE

The date that an item is scheduled to arrive or that an action is scheduled for completion.

szBranch MMCU char NONE NONE

A code that represents a high-level business unit. Use this code to refer to a branch or plant that might have departments or jobs, which
represent lower-level business units, subordinate to it. For example:     o Branch/Plant (MMCU)     o Dept A (MCU)     o Dept B (MCU)     o Job 123
(MCU) Business unit security is based on the higher-level business unit.

mnAddressNumber AN8 MATH_NUMERIC NONE NONE

A number that identifies an entry in the Address Book system, such as employee, applicant, participant, customer, supplier, tenant, or
location.

mnParentItemNumber KIT MATH_NUMERIC NONE NONE

The system provides for three separate item numbers.    1.   Item Number (short) - An eight-digit, computer assigned, completely
non-significant item number.    2.   2nd Item Number - The 25-digit, free form, user defined alphanumeric item number.    3.   3rd Item Number - Another
25-digit, free form, user defined alphanumeric item number.

idPointerToF3112 GENLNG ID NONE NONE

General purpose ID variable.

cSuppressErrorMessages EV01 char NONE NONE

An option that specifies the type of processing for an event.

szErrorMessageID DTAI char NONE NONE

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.

szIndex DTAI char NONE NONE

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.

szKeys DTAI char NONE NONE

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.

sz3rdItemNumber KITA char NONE NONE

The system provides three separate item numbers:    1. Item Number (short) - An eight-digit, computer assigned, completely non-significant
item number.    2. 2nd Item Number - The 25-digit, free form, user defined alphanumeric item number.    3. 3rd Item Number - Another 25-digit,
free form, user defined alphanumeric item number.

sz2ndItemNumber KITL char NONE NONE

The system provides for three separate item numbers.    1.   Item Number (short) - An eight-digit, computer assigned, completely
non-significant item number.    2.   2nd Item Number - The 25-digit, free form, user defined alphanumeric item number.    3.   3rd Item Number - Another
25-digit, free form, user defined alphanumeric item number. This is used in a parts list as either a parent or component number. In the Equipment
Management system, this item is used for memo purposes only.

szDescription DSC1 char NONE NONE

Brief information about an item; a remark or an explanation.

mnRunLabor RUNL MATH_NUMERIC NONE NONE

The standard hours of labor that you expect to incur in the normal production of this item. The run labor hours in the Routing Master table
(F3003) are the total hours that it takes the specified crew size to complete the operation. The hours are multiplied by the crew size during shop
floor release and product costing.

mnSetupLaborHrs SETL MATH_NUMERIC NONE NONE

The standard setup hours that you expect to incur in the normal completion of this item. This value is not affected by crew size.

mnCrewSize SETC MATH_NUMERIC NONE NONE

The number of people who work in the specified work center or routing operation. The system multiplies the Run Labor value in the Routing
Master table (F3003) by crew size during costing to generate total labor amounts. If the Prime Load Code is L or B, the system uses the total
labor hours for backscheduling. If the Prime Load Code is C or M, the system uses the total machine hours for backscheduling without
modification by crew size.

cTimeBasisCode TIMB char NONE NONE

A user defined code (30/TB) that indicates how machine or labor hours are expressed for a product. Time basis codes identify the time
basis or rate to be used for machine or labor hours entered for every routing step. For example, 25 hours per 1,000 pieces or 15 hours per
10,000 pieces. You can maintain the time basis codes in Time Basis Codes. The system uses the values in the Description-2 field on the User
Defined Codes form for costing and scheduling calculations. The description is what the code represents, but is not used in calculations.

szWorkcenterBranch WMCU char OPT NONE

This is the branch/plant to which the work center belongs and must exist in the business unit master (F0006) and branch plant constants file
(F41001).

Related Functions

None

Related Tables

F3112 Work Order Routing

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
mnOrderNumber	DOCO	MATH_NUMERIC	NONE	NONE
A number that identifies an original document. This document can be a voucher, a sales order, an invoice, unapplied cash, a journal entry, and so on.
mnOperationSequence	OPSQ	MATH_NUMERIC	NONE	NONE
A number used to indicate an order of succession. In routing instructions, a number that sequences the fabrication or assembly steps in the manufacture of an item. You can track costs and charge time by operation. In bills of material, a number that designates the routing step in the fabrication or assembly process that requires a specified component part. You define the operation sequence after you create the routing instructions for the item. The Shop Floor Management system uses this number in the backflush/preflush by operation process. In engineering change orders, a number that sequences the assembly steps for the engineering change. For repetitive manufacturing, a number that identifies the sequence in which an item is scheduled to be produced. Skip To fields allow you to enter an operation sequence that you want to begin the display of information. You can use decimals to add steps between existing steps. For example, use 12.5 to add a step between steps 12 and 13.
szBusinessUnit	MCU	char	NONE	NONE
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.
szTypeOperationCode	OPSC	char	NONE	NONE
A user defined code (30/OT) that indicates the type of operation. Valid values include: A Alternate routing TT Travel time IT Idle time T Text
jdStartDate	STRT	JDEDATE	NONE	NONE
The start date for the order. You can enter this date manually, or have the system calculate it using a backscheduling routine. The routine starts with the required date and offsets the total leadtime to calculate the appropriate start date.
jdRequestedDate	DRQJ	JDEDATE	NONE	NONE
The date that an item is scheduled to arrive or that an action is scheduled for completion.
szBranch	MMCU	char	NONE	NONE
A code that represents a high-level business unit. Use this code to refer to a branch or plant that might have departments or jobs, which represent lower-level business units, subordinate to it. For example: o Branch/Plant (MMCU) o Dept A (MCU) o Dept B (MCU) o Job 123 (MCU) Business unit security is based on the higher-level business unit.
mnAddressNumber	AN8	MATH_NUMERIC	NONE	NONE
A number that identifies an entry in the Address Book system, such as employee, applicant, participant, customer, supplier, tenant, or location.
mnParentItemNumber	KIT	MATH_NUMERIC	NONE	NONE
The system provides for three separate item numbers. 1. Item Number (short) - An eight-digit, computer assigned, completely non-significant item number. 2. 2nd Item Number - The 25-digit, free form, user defined alphanumeric item number. 3. 3rd Item Number - Another 25-digit, free form, user defined alphanumeric item number.
idPointerToF3112	GENLNG	ID	NONE	NONE
General purpose ID variable.
cSuppressErrorMessages	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
szErrorMessageID	DTAI	char	NONE	NONE
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.
szIndex	DTAI	char	NONE	NONE
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.
szKeys	DTAI	char	NONE	NONE
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.
sz3rdItemNumber	KITA	char	NONE	NONE
The system provides three separate item numbers: 1. Item Number (short) - An eight-digit, computer assigned, completely non-significant item number. 2. 2nd Item Number - The 25-digit, free form, user defined alphanumeric item number. 3. 3rd Item Number - Another 25-digit, free form, user defined alphanumeric item number.
sz2ndItemNumber	KITL	char	NONE	NONE
The system provides for three separate item numbers. 1. Item Number (short) - An eight-digit, computer assigned, completely non-significant item number. 2. 2nd Item Number - The 25-digit, free form, user defined alphanumeric item number. 3. 3rd Item Number - Another 25-digit, free form, user defined alphanumeric item number. This is used in a parts list as either a parent or component number. In the Equipment Management system, this item is used for memo purposes only.
szDescription	DSC1	char	NONE	NONE
Brief information about an item; a remark or an explanation.
mnRunLabor	RUNL	MATH_NUMERIC	NONE	NONE
The standard hours of labor that you expect to incur in the normal production of this item. The run labor hours in the Routing Master table (F3003) are the total hours that it takes the specified crew size to complete the operation. The hours are multiplied by the crew size during shop floor release and product costing.
mnSetupLaborHrs	SETL	MATH_NUMERIC	NONE	NONE
The standard setup hours that you expect to incur in the normal completion of this item. This value is not affected by crew size.
mnCrewSize	SETC	MATH_NUMERIC	NONE	NONE
The number of people who work in the specified work center or routing operation. The system multiplies the Run Labor value in the Routing Master table (F3003) by crew size during costing to generate total labor amounts. If the Prime Load Code is L or B, the system uses the total labor hours for backscheduling. If the Prime Load Code is C or M, the system uses the total machine hours for backscheduling without modification by crew size.
cTimeBasisCode	TIMB	char	NONE	NONE
A user defined code (30/TB) that indicates how machine or labor hours are expressed for a product. Time basis codes identify the time basis or rate to be used for machine or labor hours entered for every routing step. For example, 25 hours per 1,000 pieces or 15 hours per 10,000 pieces. You can maintain the time basis codes in Time Basis Codes. The system uses the values in the Description-2 field on the User Defined Codes form for costing and scheduling calculations. The description is what the code represents, but is not used in calculations.
szWorkcenterBranch	WMCU	char	OPT	NONE
This is the branch/plant to which the work center belongs and must exist in the business unit master (F0006) and branch plant constants file (F41001).