Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
cCacheActionCode | EV01 | char | REQ | OUTPUT |
An option that specifies the type of processing for an event.
|
nIndexNumber | INT01 | integer | REQ | OUTPUT |
Number of Days in Future to Query for Responses Due.
|
nNumberOfKeys | INT01 | integer | REQ | OUTPUT |
Number of Days in Future to Query for Responses Due.
|
cReturnCursor | EV01 | char | OPT | OUTPUT |
An option that specifies the type of processing for an event.
|
idCursor | GENLNG | ID | OPT | BOTH |
General purpose ID variable. |
cCacheCodeError | EV01 | char | OPT | INPUT |
An option that specifies the type of processing for an event.
|
cSuppressErrorMessages | EV01 | char | OPT | OUTPUT |
An option that specifies the type of processing for an event.
|
szErrorMessageID | DTAI | char | OPT | INPUT |
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.
|
mnJobnumber | JOBS | MATH_NUMERIC | REQ | OUTPUT |
The job number (work station ID) which executed the particular job. |
mnDocumentOrderInvoiceE | DOCO | MATH_NUMERIC | OPT | BOTH |
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. |
szOrderType | DCTO | char | OPT | BOTH |
A user defined code (00/DT) that identifies the type of document. This code also indicates the origin of the transaction. J.D. Edwards has
reserved document type codes for vouchers, invoices, receipts, and time sheets, which create automatic offset entries during the post
program. (These entries are not self-balancing when you originally enter them.)
The following document types are defined by J.D. Edwards and
should not be changed:
P
Accounts Payable documents
R
Accounts Receivable documents
T
Payroll documents
I
Inventory documents
O
Purchase Order Processing documents
J
General Accounting/Joint Interest Billing documents
S
Sales Order Processing documents
|
mnComponentShortItemNumber | ITM | MATH_NUMERIC | OPT | BOTH |
An inventory item number. The system provides three separate item numbers plus an extensive cross-reference capability to other item
numbers (see data item XRT) to accommodate substitute item numbers, replacements, bar codes, customer numbers, supplier numbers, and
so forth. The item numbers are as follows:
o Item Number (short) - An eight-digit, computer-assigned item number
o 2nd Item Number - The
25-digit, free-form, user defined alphanumeric item number
o 3rd Item Number - Another 25-digit, free-form, user defined alphanumeric item
number |
szComponent2ndItemNumber | LITM | char | OPT | BOTH |
A number that identifies the item. The system provides three separate item numbers plus an extensive cross-reference capability to
alternative item numbers. The three types of item numbers are:
Item Number (short)
An 8-digit, computer-assigned item number.
2nd Item Number
A
25-digit, user defined, alphanumeric item number.
3rd Item Number
Another 25-digit, user defined, alphanumeric item number.
In addition to
these three basic item numbers, the system provides an extensive cross-reference search capability. You can define numerous
cross-references to alternative part numbers. For example, you can define substitute item numbers, replacements, bar codes, customer numbers, or
supplier numbers.
|
szComponent3rdItemNumber | AITM | char | OPT | BOTH |
The system provides three separate item numbers plus an extensive cross-reference capability to alternate item numbers. These item
numbers are as follows:
1. Item Number (short) - An 8-digit, computer-assigned 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.
In addition to
these three basic item numbers, an extensive cross-reference search capability has been provided (see XRT). Numerous cross references to
alternate part numbers can be user defined, such as substitute item numbers, replacements, bar codes, customer numbers, or supplier
numbers. |
szComponentBranch | CMCU | char | OPT | BOTH |
A secondary or lower-level business unit. The system uses the value that you enter to indicate that a branch or plant contains several
subordinate departments or jobs. For example, assume that the component branch is named MMCU. The structure of MMCU might be as follows:
Branch/Plant - (MMCU)
Dept A - (MCU)
Dept B - (MCU)
Job 123 - (MCU) |
mnSequenceNoOperations | OPSQ | MATH_NUMERIC | OPT | BOTH |
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. |
mnSuccessiveOperation | OPSQ | MATH_NUMERIC | OPT | BOTH |
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. |
mnReverseSequenceNumber | OPSQ | MATH_NUMERIC | OPT | BOTH |
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. |
szTypeOperationCode | OPSC | char | OPT | BOTH |
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 |
szWorkCenter | 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.
|
mnConfiguratorMultiplier | MULT | MATH_NUMERIC | OPT | BOTH |
A multiple for rounding up planned order quantities in MPS/MRP. The system rounds up the planned order quantity to the nearest multiple
you enter in this field. |
mnRunMachineStandard | RUNM | MATH_NUMERIC | OPT | BOTH |
The standard machine hours that you expect to incur in the normal production of this item. |
mnRunLaborStandard | RUNL | MATH_NUMERIC | OPT | BOTH |
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. |
mnSetupLaborHrsStdr | SETL | MATH_NUMERIC | OPT | BOTH |
The standard setup hours that you expect to incur in the normal completion of this item. This value is not affected by crew size. |
mnQueueHours | QUED | MATH_NUMERIC | OPT | BOTH |
The total hours that an order is expected to be in queue at work centers and moving between work centers.
The system stores this value in
the Item Branch table (F4102). You can calculate this value using the Leadtime Rollup program or you can enter it manually. When you run the
Leadtime Rollup program, the system overrides manual entries and populates the table with calculated values. |
mnMoveHours | MOVD | MATH_NUMERIC | OPT | BOTH |
The planned hours that are required to move the order from this operation to the next operation in the same work center.
If the Routing
Master values are blank, the system retrieves the default value from the work order routing. However, the system uses these values only for
backscheduling variable leadtime items. |
mnCrewSize | SETC | MATH_NUMERIC | OPT | BOTH |
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. |
jdDateStart | STRT | JDEDATE | OPT | BOTH |
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.
|
cTimeBasisCode | TIMB | char | OPT | BOTH |
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. |
mnPercentOfOverlap | POVR | MATH_NUMERIC | OPT | BOTH |
A number that indicates the percentage that successive operations can overlap.
The actual overlap percentage entered for the operation
sequence is the percent by which that operation overlaps the prior operation. For example, if you enter 80%, this indicates that work can begin
on the overlapped operation when 20% of the prior operation is completed.
Notes:
1. Overlapping has no effect on move and queue
calculations.
2. The percent entered must be less than or equal to 100%.
Enter percents as whole numbers: 5% as 5.00 |
mnNewOperationCumYield | CPYP | MATH_NUMERIC | OPT | BOTH |
The cumulative planned output yield percent for a step. The system uses this value to adjust the operation step scrap percent for the
components at that operation step. This enables the MRP system to use the operation step scrap percent along with the existing component scrap
percent to plan component demand. |
cPrimeLoadCode | PILC | char | OPT | BOTH |
A code that determines if a work center is machine or labor intensive. The system also uses prime load codes in Resource Requirements
Planning and Capacity Requirements Planning calculations to develop load profiles.
Valid codes are:
L Run labor hours only
M Machine
hours only
B Run labor plus setup labor hours
C Machine plus setup hours
O Other (will not generate resource units) |
szEquipmentNumber | ASII | char | OPT | BOTH |
An identification code that represents an asset. You enter the identification code in one of the following formats:
1
Asset number (a
computer-assigned, 8-digit, numeric control number)
2
Unit number (a 12-character alphanumeric field)
3
Serial number (a 25-character alphanumeric
field)
Every asset has an asset number. You can use unit number and serial number to further identify assets. If this is a data entry field, the first
character you enter indicates whether you are entering the primary (default) format that is defined for your system, or one of the other two
formats. A special character (such as / or *) in the first position of this field indicates which asset number format you are using. You assign special
characters to asset number formats on the fixed assets system constants form. |
szPrecedenceType | DL01 | char | OPT | BOTH |
A user defined name or remark. |
mnPrecedenceOffset | MATH01 | MATH_NUMERIC | OPT | BOTH |
- - - Good Performance Low Value.
|
mnYieldPercent | OPYP | MATH_NUMERIC | OPT | BOTH |
The planned output yield percent for a step. The Planned Yield Update program uses this value to update the cumulative percent in the
routing and the operation scrap percent in the bill of material. Materials Requirements Planning uses the step scrap percent and the existing
component scrap percent to plan component demand. |
mnCumYieldPercent | CPYP | MATH_NUMERIC | OPT | BOTH |
The cumulative planned output yield percent for a step. The system uses this value to adjust the operation step scrap percent for the
components at that operation step. This enables the MRP system to use the operation step scrap percent along with the existing component scrap
percent to plan component demand. |
cActionType | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
jdRequestDate | DRQJ | JDEDATE | OPT | NONE |
The date that an item is scheduled to arrive or that an action is scheduled for completion.
|
mnRecordCount | MATH01 | MATH_NUMERIC | OPT | NONE |
- - - Good Performance Low Value.
|
mnNumberOfMachines | NOMA | MATH_NUMERIC | OPT | NONE |
The normal number of machines in this work center. When you run the Work Center Resource Units Refresh program, this number is
multiplied by the number of work hours per day from the Manufacturing Constants table (F3009) to generate the total gross machine hours available
in the work center each day. |
mnNumberOfEmployees | QMAD | MATH_NUMERIC | OPT | NONE |
The normal number of employees in this work center. When you run the Work Center Resource Units Refresh program, the system
multiplies this number by the Number of Work Hours Per Day from the Manufacturing Constants table (F3009) to generate the total gross labor hours
available in the work center each day. |
cRoutingActivity | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
cPrimaryOutputOnly | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
szLineIdentifier | LINE | char | OPT | NONE |
A number that defines a production line or cell. Detailed work center operations can be defined inside the line or cell. |