MRPWriteCoByProductTransferQty

MRP, Write CoBy Product Transfer Qty

Master Business Function

Object Name: B3500080

Parent DLL: CMFG

Location: Client/Server

Language: C

1.Functional Description
This Business function will write Planned Orders due to transfers for co or by products prior to
calling B3400500. This function can only be called if the item is a co or by product and the consolidation
method used is '2'.

1.1Purpose
This function is used to write 'PLQ' quantities (Planned Orders) when co or by products can be
transferred out to another branch. These 'PLQ' quantities will be detected by B3400500 and will reduce the
total requirements for the item.

1.2Setup Notes and Prerequisites
The Manufacturing Data from the Item Balance table must be obtained and all other data must be loaded
in the MRP Bucketless Date Cache and MRP Item Quantity Cache. Please note that this is almost the
final process in planning and care must be taken while making changes in the code.

1.3Special Logic
None

2.Technical Specifications

Data Structure

D3500080 - MRP, Write CoBy Product Transfer Quantity

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

szJobNumber JOB char NONE NONE

Job Number

szBranch 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.

mnShortItemNumber ITM MATH_NUMERIC NONE NONE

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

cLeadtimeType MRPP char NONE NONE

A code that determines whether the system uses fixed or variable leadtimes. This code works in conjunction with the value from either the
Level Leadtime field or the Leadtime Per Unit field. Valid codes are:    F Fixed leadtime - The system calculates work order start dates using the
value from the Leadtime Level field.    V Variable leadtime - The system calculates work order start dates using the value from the Leadtime
Per Unit field.

mnLeadtimeLevel LTLV MATH_NUMERIC NONE NONE

A value that represents the leadtime for an item at its assigned level in the production process, as defined on Plant Manufacturing Data.
The system uses this value to calculate the start dates for work orders using fixed leadtimes. Level leadtime is different for purchased and
manufactured items: Purchased - The number of calendar days required for the item to arrive at your branch/plant after the supplier receives your
purchase order. Manufactured - The number of workdays required to complete the fabrication or assembly of an item after all the
components are available. You can enter level leadtime manually on Manufacturing Values Entry, or you can use the Leadtime Rollup program to
calculate it. To calculate level leadtime using the Leadtime Rollup program, you must first enter a quantity in the Manufacturing Leadtime Quantity
field in the Item Branch table (F4102).

mnLeadtimePerUnit LTPU MATH_NUMERIC NONE NONE

The total number of hours required to build one unit as specified on the routing. This value is factored by the time basis code. You can enter
this value manually or you can have the system calculate it when you run the Leadtime Rollup program. The system overwrites this value
when you run the Leadtime Rollup program. The system uses this field to calculate start dates for work orders when you use variable leadtimes.

c2ndStockType STKT char NONE NONE

A user defined code (41/I) that indicates how you stock an item, for example, as finished goods or as raw materials. The following stocking
types are hard-coded and you should not change them:    0   Phantom item    B Bulk floor stock    C Configured item    E Emergency/corrective
maintenance    F Feature    K Kit parent item    N Nonstock The first character of Description 2 in the user defined code table indicates if the item
is purchased (P) or manufactured (M).

cPlanningCode MPST char NONE NONE

A code that indicates how Master Production Schedule (MPS), Material Requirements Planning (MRP), or Distribution Requirements
Planning (DRP) processes this item. Valid codes are:    0   Not Planned by MPS, MRP, or DRP    1   Planned by MPS or DRP    2   Planned by MRP
3   Planned by MRP with additional independent forecast    4   Planned by MPS, Parent in Planning Bill    5   Planned by MPS, Component in
Planning Bill These codes are hard coded.

mnFromPotency FRMP MATH_NUMERIC NONE NONE

A number that indicates the minimum potency or percentage of active ingredients acceptable for an item. The system displays a warning
message if you try to purchase or issue items that do not meet the minimum acceptable potency. The system does not allow you to sell items
that do not meet the minimum acceptable potency.

mnThruPotency THRP MATH_NUMERIC NONE NONE

A number that indicates the maximum potency or percentage of active ingredients that is acceptable for an item. The system displays a
warning message if you try to purchase or issue items that have a potency that exceeds the maximum potency acceptable. The system does
not allow you to sell items that have a potency that exceeds the maximum potency acceptable.

szFromGrade FRGD char NONE NONE

A user defined code (40/LG) that indicates the minimum grade that is acceptable for an item. The system displays a warning message if
you try to purchase or issue items with grades that do not meet the minimum grade acceptable. The system does not allow you to sell items
with grades that do not meet the minimum acceptable level.

szThruGrade THGD char NONE NONE

A user defined code (40/LG) that indicates the maximum grade that is acceptable for an item. The system displays a warning message if
you try to purchase or issue items with grades that exceed the maximum grade acceptable. The system does not allow you to sell items with
grades that exceed the maximum grade acceptable.

mnVendorNumber VEND MATH_NUMERIC NONE NONE

The address book number of the preferred provider of this item.

mnWorkHourPerDay WRHR MATH_NUMERIC NONE NONE

The number of work hours that the manufacturing plant operates per day.

szUnitOfMeasurePrimary UOM1 char NONE NONE

A user defined code (00/UM) that identifies the unit of measure that the system uses to express the quantity of an item, for example, EA
(each) or KG (kilogram).

cRoundingFlag SNS char NONE NONE

A code that determines whether the system performs rounding for planning purposes. Valid values are:    R Round either up or down to the
nearest whole number.    U Round up to the nearest whole number.    Blank Do not round. Example of value R: If the calculated requirements for
an item are 4.6, the system rounds the quantity required to 5.0. If the calculated requirements are 4.4, the system rounds the quantity required
to 4.0. Example of value U: If the calculated requirements for an item are greater than 4.0 and less than or equal to 5.0, the system rounds the
quantity required to 5.0.

cCostLevel CLEV char NONE NONE

A code that indicates whether the system maintains one overall inventory cost for the item, a different cost for each branch/plant, or a
different cost for each location and lot within a branch/plant. The system maintains inventory costs in the Inventory Cost table (F4105). Valid codes
are:    1   Item level    2   Item/Branch level    3   Item/Branch/Location level

szDateErrorMsg DSC1 char NONE NONE

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

cWorkOrderFlag EV04 char NONE NONE

PeopleSoft event point processing flag 04.

cPurchOrderFlag EV04 char NONE NONE

PeopleSoft event point processing flag 04.

cProcessOrderExistFlag EV04 char NONE NONE

PeopleSoft event point processing flag 04.

jdFrozenDate DATE01 JDEDATE NONE NONE

Event point for JDE Date.

jdMessageDate DATE01 JDEDATE NONE NONE

Event point for JDE Date.

jdBeginningDate DATE01 JDEDATE NONE NONE

Event point for JDE Date.

jdStartDate DATE01 JDEDATE NONE NONE

Event point for JDE Date.

jdEndDate DATE01 JDEDATE NONE NONE

Event point for JDE Date.

cDateErrorFlag EV01 char NONE NONE

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

cLotExpirationFlag EV01 char NONE NONE

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

cGenerationType EV01 char NONE NONE

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

nMfgSafetyLeadtime INT01 integer NONE NONE

Number of Days in Future to Query for Responses Due.

nPurcSafetyLeadtime INT01 integer NONE NONE

Number of Days in Future to Query for Responses Due.

szPurchOrderDocType DCTO char NONE NONE

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

szWorkOrderDocType DCTO char NONE NONE

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

nNumberOfBuckelessDates INT01 integer NONE NONE

Number of Days in Future to Query for Responses Due.

cSuppressErrorMessages EV01 char NONE NONE

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

cErrorCode ERRC char NONE NONE

This error code indicates if any errors occurred during the creation of the Trip Document Detail (F4914) records by the Delivery Document
Set Server program (XT4914).

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.

mnF3411UniqueID UKID MATH_NUMERIC NONE NONE

This field is a unique number used to identify a record in a file.

mnF3412UniqueID UKID MATH_NUMERIC NONE NONE

This field is a unique number used to identify a record in a file.

szProgramID PID char NONE NONE

The number that identifies the batch or interactive program (batch or interactive object). For example, the number of the Sales Order Entry
interactive program is P4210, and the number of the Print Invoices batch process report is R42565. The program ID is a variable length value.
It is assigned according to a structured syntax in the form TSSXXX, where: T The first character of the number is alphabetic and identifies the
type, such as P for Program, R for Report, and so on. For example, the value P in the number P4210 indicates that the object is a
program. SS The second and third characters of the number are numeric and identify the system code. For example, the value 42 in the number P4210
indicates that this program belongs to system 42, which is the Sales Order Processing system. XXX The remaining characters of the numer are
numeric and identify a unique program or report. For example, the value 10 in the number P4210 indicates that this is the Sales Order Entry
program.

cMakeMfgItemsInOrigin EV01 char NONE NONE

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

cProcessEachBranch EV01 char NONE NONE

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

szTransferOrderDocType DCTO char NONE NONE

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

szStdUOMConversion TFLA char NONE NONE

Allows you to bypass the item-specific unit of measure and use the standard unit of measure. Valid values are:    blank Use the item-specific
unit of measure    1       Bypass the item-specific unit of measure and use the standard unit of measure

mnStandardPotency STDP MATH_NUMERIC NONE NONE

The percentage of active ingredients normally found in an item.

cPotencyControl OT1Y char NONE NONE

A code that indicates whether you control the item by potency.

szDateBranch 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.

szCategoryCode PRPX char NONE NONE

A user defined code (system 41, type P4) under which you can organize logically related items. You can simplify the master planning
process by concentrating on only the top 10% of the inventory value. This is similar to using the ABC Analysis, except that you can use this code to
allow exceptions to ABC rules. Generally, you should only include items with high inventory investment in Master Planning. Excess stock can
be carried for inventory items with little financial impact.

mnJobNumber JOBS MATH_NUMERIC NONE NONE

The job number (work station ID) which executed the particular job.

szComputerID CTID char NONE NONE

cUseForecastConsumption EV01 char NONE NONE

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

mnUniqueKeyIDOffset MATH01 MATH_NUMERIC OPT NONE

- - - Good Performance Low Value.

cSupplyDemandExists EV01 char OPT NONE

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

Related Functions

B3400540 MRP, Calculate Schedule Dates for Planning

B3401270 Cache, Process MRP Bucketless Dates

B3401280 Cache, Process MRP Co/By Products

B3401290 Cache, Process MRP Item Quantities

B3401300 Cache, Process MRP Inclusion Rules

B3401310 Cache, Process MRP Work Orders

B3401320 Cache, Process MRP Purchase Orders

B3500030 MRP, Get Supply Branch

B3500040 MRP, Calculate Available Transfer Qty from Cache

B4000520 Get Item UoM Conversion Factor

B9800100 Get Audit Information

B9800420 Get Data Dictionary Definition

Related Tables

F3002 Bill of Material Master File

F3111 Work Order Parts List

F3411 MPS/MRP/DRP Message File

F35UI001 MPS/MRP Planning - Multiple Plant User Index

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
szJobNumber	JOB	char	NONE	NONE
Job Number
szBranch	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.
mnShortItemNumber	ITM	MATH_NUMERIC	NONE	NONE
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
cLeadtimeType	MRPP	char	NONE	NONE
A code that determines whether the system uses fixed or variable leadtimes. This code works in conjunction with the value from either the Level Leadtime field or the Leadtime Per Unit field. Valid codes are: F Fixed leadtime - The system calculates work order start dates using the value from the Leadtime Level field. V Variable leadtime - The system calculates work order start dates using the value from the Leadtime Per Unit field.
mnLeadtimeLevel	LTLV	MATH_NUMERIC	NONE	NONE
A value that represents the leadtime for an item at its assigned level in the production process, as defined on Plant Manufacturing Data. The system uses this value to calculate the start dates for work orders using fixed leadtimes. Level leadtime is different for purchased and manufactured items: Purchased - The number of calendar days required for the item to arrive at your branch/plant after the supplier receives your purchase order. Manufactured - The number of workdays required to complete the fabrication or assembly of an item after all the components are available. You can enter level leadtime manually on Manufacturing Values Entry, or you can use the Leadtime Rollup program to calculate it. To calculate level leadtime using the Leadtime Rollup program, you must first enter a quantity in the Manufacturing Leadtime Quantity field in the Item Branch table (F4102).
mnLeadtimePerUnit	LTPU	MATH_NUMERIC	NONE	NONE
The total number of hours required to build one unit as specified on the routing. This value is factored by the time basis code. You can enter this value manually or you can have the system calculate it when you run the Leadtime Rollup program. The system overwrites this value when you run the Leadtime Rollup program. The system uses this field to calculate start dates for work orders when you use variable leadtimes.
c2ndStockType	STKT	char	NONE	NONE
A user defined code (41/I) that indicates how you stock an item, for example, as finished goods or as raw materials. The following stocking types are hard-coded and you should not change them: 0 Phantom item B Bulk floor stock C Configured item E Emergency/corrective maintenance F Feature K Kit parent item N Nonstock The first character of Description 2 in the user defined code table indicates if the item is purchased (P) or manufactured (M).
cPlanningCode	MPST	char	NONE	NONE
A code that indicates how Master Production Schedule (MPS), Material Requirements Planning (MRP), or Distribution Requirements Planning (DRP) processes this item. Valid codes are: 0 Not Planned by MPS, MRP, or DRP 1 Planned by MPS or DRP 2 Planned by MRP 3 Planned by MRP with additional independent forecast 4 Planned by MPS, Parent in Planning Bill 5 Planned by MPS, Component in Planning Bill These codes are hard coded.
mnFromPotency	FRMP	MATH_NUMERIC	NONE	NONE
A number that indicates the minimum potency or percentage of active ingredients acceptable for an item. The system displays a warning message if you try to purchase or issue items that do not meet the minimum acceptable potency. The system does not allow you to sell items that do not meet the minimum acceptable potency.
mnThruPotency	THRP	MATH_NUMERIC	NONE	NONE
A number that indicates the maximum potency or percentage of active ingredients that is acceptable for an item. The system displays a warning message if you try to purchase or issue items that have a potency that exceeds the maximum potency acceptable. The system does not allow you to sell items that have a potency that exceeds the maximum potency acceptable.
szFromGrade	FRGD	char	NONE	NONE
A user defined code (40/LG) that indicates the minimum grade that is acceptable for an item. The system displays a warning message if you try to purchase or issue items with grades that do not meet the minimum grade acceptable. The system does not allow you to sell items with grades that do not meet the minimum acceptable level.
szThruGrade	THGD	char	NONE	NONE
A user defined code (40/LG) that indicates the maximum grade that is acceptable for an item. The system displays a warning message if you try to purchase or issue items with grades that exceed the maximum grade acceptable. The system does not allow you to sell items with grades that exceed the maximum grade acceptable.
mnVendorNumber	VEND	MATH_NUMERIC	NONE	NONE
The address book number of the preferred provider of this item.
mnWorkHourPerDay	WRHR	MATH_NUMERIC	NONE	NONE
The number of work hours that the manufacturing plant operates per day.
szUnitOfMeasurePrimary	UOM1	char	NONE	NONE
A user defined code (00/UM) that identifies the unit of measure that the system uses to express the quantity of an item, for example, EA (each) or KG (kilogram).
cRoundingFlag	SNS	char	NONE	NONE
A code that determines whether the system performs rounding for planning purposes. Valid values are: R Round either up or down to the nearest whole number. U Round up to the nearest whole number. Blank Do not round. Example of value R: If the calculated requirements for an item are 4.6, the system rounds the quantity required to 5.0. If the calculated requirements are 4.4, the system rounds the quantity required to 4.0. Example of value U: If the calculated requirements for an item are greater than 4.0 and less than or equal to 5.0, the system rounds the quantity required to 5.0.
cCostLevel	CLEV	char	NONE	NONE
A code that indicates whether the system maintains one overall inventory cost for the item, a different cost for each branch/plant, or a different cost for each location and lot within a branch/plant. The system maintains inventory costs in the Inventory Cost table (F4105). Valid codes are: 1 Item level 2 Item/Branch level 3 Item/Branch/Location level
szDateErrorMsg	DSC1	char	NONE	NONE
Brief information about an item; a remark or an explanation.
cWorkOrderFlag	EV04	char	NONE	NONE
PeopleSoft event point processing flag 04.
cPurchOrderFlag	EV04	char	NONE	NONE
PeopleSoft event point processing flag 04.
cProcessOrderExistFlag	EV04	char	NONE	NONE
PeopleSoft event point processing flag 04.
jdFrozenDate	DATE01	JDEDATE	NONE	NONE
Event point for JDE Date.
jdMessageDate	DATE01	JDEDATE	NONE	NONE
Event point for JDE Date.
jdBeginningDate	DATE01	JDEDATE	NONE	NONE
Event point for JDE Date.
jdStartDate	DATE01	JDEDATE	NONE	NONE
Event point for JDE Date.
jdEndDate	DATE01	JDEDATE	NONE	NONE
Event point for JDE Date.
cDateErrorFlag	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
cLotExpirationFlag	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
cGenerationType	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
nMfgSafetyLeadtime	INT01	integer	NONE	NONE
Number of Days in Future to Query for Responses Due.
nPurcSafetyLeadtime	INT01	integer	NONE	NONE
Number of Days in Future to Query for Responses Due.
szPurchOrderDocType	DCTO	char	NONE	NONE
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
szWorkOrderDocType	DCTO	char	NONE	NONE
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
nNumberOfBuckelessDates	INT01	integer	NONE	NONE
Number of Days in Future to Query for Responses Due.
cSuppressErrorMessages	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
cErrorCode	ERRC	char	NONE	NONE
This error code indicates if any errors occurred during the creation of the Trip Document Detail (F4914) records by the Delivery Document Set Server program (XT4914).
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.
mnF3411UniqueID	UKID	MATH_NUMERIC	NONE	NONE
This field is a unique number used to identify a record in a file.
mnF3412UniqueID	UKID	MATH_NUMERIC	NONE	NONE
This field is a unique number used to identify a record in a file.
szProgramID	PID	char	NONE	NONE
The number that identifies the batch or interactive program (batch or interactive object). For example, the number of the Sales Order Entry interactive program is P4210, and the number of the Print Invoices batch process report is R42565. The program ID is a variable length value. It is assigned according to a structured syntax in the form TSSXXX, where: T The first character of the number is alphabetic and identifies the type, such as P for Program, R for Report, and so on. For example, the value P in the number P4210 indicates that the object is a program. SS The second and third characters of the number are numeric and identify the system code. For example, the value 42 in the number P4210 indicates that this program belongs to system 42, which is the Sales Order Processing system. XXX The remaining characters of the numer are numeric and identify a unique program or report. For example, the value 10 in the number P4210 indicates that this is the Sales Order Entry program.
cMakeMfgItemsInOrigin	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
cProcessEachBranch	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
szTransferOrderDocType	DCTO	char	NONE	NONE
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
szStdUOMConversion	TFLA	char	NONE	NONE
Allows you to bypass the item-specific unit of measure and use the standard unit of measure. Valid values are: blank Use the item-specific unit of measure 1 Bypass the item-specific unit of measure and use the standard unit of measure
mnStandardPotency	STDP	MATH_NUMERIC	NONE	NONE
The percentage of active ingredients normally found in an item.
cPotencyControl	OT1Y	char	NONE	NONE
A code that indicates whether you control the item by potency.
szDateBranch	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.
szCategoryCode	PRPX	char	NONE	NONE
A user defined code (system 41, type P4) under which you can organize logically related items. You can simplify the master planning process by concentrating on only the top 10% of the inventory value. This is similar to using the ABC Analysis, except that you can use this code to allow exceptions to ABC rules. Generally, you should only include items with high inventory investment in Master Planning. Excess stock can be carried for inventory items with little financial impact.
mnJobNumber	JOBS	MATH_NUMERIC	NONE	NONE
The job number (work station ID) which executed the particular job.
szComputerID	CTID	char	NONE	NONE

cUseForecastConsumption	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
mnUniqueKeyIDOffset	MATH01	MATH_NUMERIC	OPT	NONE
- - - Good Performance Low Value.
cSupplyDemandExists	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.

B3400540 MRP, Calculate Schedule Dates for Planning
B3401270 Cache, Process MRP Bucketless Dates
B3401280 Cache, Process MRP Co/By Products
B3401290 Cache, Process MRP Item Quantities
B3401300 Cache, Process MRP Inclusion Rules
B3401310 Cache, Process MRP Work Orders
B3401320 Cache, Process MRP Purchase Orders
B3500030 MRP, Get Supply Branch
B3500040 MRP, Calculate Available Transfer Qty from Cache
B4000520 Get Item UoM Conversion Factor
B9800100 Get Audit Information
B9800420 Get Data Dictionary Definition

F3002 Bill of Material Master File
F3111 Work Order Parts List
F3411 MPS/MRP/DRP Message File
F35UI001 MPS/MRP Planning - Multiple Plant User Index