LoadSupplyAndDemandData

Load Supply And Demand Data

Minor Business Rule

Object Name: B3400310

Parent DLL: CMFG

Location: Client/Server

Language: C

Data Structure

D3400310 - Load Supply And Demand Data

Data Item Data Structure DescriptionI/ORequiredNotes
ITM            Item Number                        IY
MCU            Branch                        IY
UOM1            Primary Unit of Measure       IY
MVER            Include Rule Version            IY
EFFF            From Date                        I      Default = 0
EFFT            Thru Date                        I      Default = High Values
EV01            Planned Order flag                 I      '1' - Include Planned Orders
EV02            Lot Expiration flag            I      '1' - Do Lot Expiration
Processing
EV03            Standard Potency flag            I       '1' - Calculate in Std
Potency
EV04            Bulk Stocking Type             I       '1' - Omit Bulk Stkg Type
EV05            Transit flag                  I       '1' - Include Transit Qty
EV06            Inspect flag                  I      '1' - Include Inspect Qty
EV07            Other1 flag                      I          '1' - Include Other1 Qty
EV08            Other2 flag                        I          '1' - Include Other2 Qty
EV09            Rec Routing Summary            I      '1' - Summarise Rec Rtg
OT1Y            Potency Control flag            I        From F4102 Item Balance
STDP            Standars Potency Value            I       Std Potency from Item Balance
EV01            Potent Unit flag                  I       Potent Unit flag
TYPF            Forecast Type 1                I
TYPF            Forecast Type 2                  I
TYPF            Forecast Type 3                  I
TYPF            Forecast Type 4                  I
TYPF            Forecast Type 5                  I
SCHT            Schedule Type                  I       For Rate Based Processing
EV05            Location Summary flag            I       Location Summary flag
EV01            Mode                               IY      1 - Open all tables 2 - Read
tables                                                                         and Add data to table 3
- Release the                                                                         request and
globals
EV02            Suppress Error Message            I      ' ' - Display Errors '1' -
Suppress                                                                         Error Messages
ERRC            Error Code                        O       '0' - Success (Default) '1' -
Errors                                                                         in Loading Data
DTAI            Error Message Id                  O       ' ' - Success  '3143' -
Errors
EV02            Forecast flag                  O       ' ' - If forecast data loaded
'1' -                                                                         No forecast loaded
STRT            Forecast Start Date            IY      Forecast Start Date to Pass
to                                                                         B3400290. Added by T.Chan
1/30/96.
TFLA            Std UOM Conversion            IY      Required for UOM Conversion

^

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
cMode	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
mnShortItemNumber	ITM	MATH_NUMERIC	OPT	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
szBranch	MCU	char	OPT	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.
szPrimaryUnitOfMeasure	UOM1	char	OPT	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).
szStandardUOMConversion	TFLA	char	OPT	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
szInclusionRuleVersion	MVER	char	OPT	NONE
A user defined code (40/RV) that identifies an inclusion rule that you want the system to use for this branch/plant. The Manufacturing and Warehouse Management systems use inclusion rules as follows: o For Manufacturing: Allows multiple versions of resource rules for running MPS, MRP, or DRP. o For Warehouse Management: Allows multiple versions of inclusion rules for running putaway and picking. The system processes only those order lines that match the inclusion rule for a specified branch/plant.
jdEffectiveFromDate	EFFF	JDEDATE	OPT	NONE
A date that indicates one of the following: o When a component part goes into effect on a bill of material o When a routing step goes into effect as a sequence on the routing for an item o When a rate schedule is in effect The default is the current system date. You can enter future effective dates so that the system plans for upcoming changes. Items that are no longer effective in the future can still be recorded and recognized in Product Costing, Shop Floor Management, and Capacity Requirements Planning. The Material Requirements Planning system determines valid components by effectivity dates, not by the bill of material revision level. Some forms display data based on the effectivity dates you enter.
jdEffectiveThruDate	EFFT	JDEDATE	OPT	NONE
A date that indicates one of the following: o When a component part is no longer in effect on a bill of material o When a routing step is no longer in effect as a sequence on the routing for an item o When a rate schedule is no longer active The default is December 31 of the default year defined in the Data Dictionary for Century Change Year. You can enter future effective dates so that the system plans for upcoming changes. Items that are no longer effective in the future can still be recorded and recognized in Product Costing, Shop Floor Management, and Capacity Requirements Planning. The Material Requirements Planning system determines valid components by effectivity dates, not by the bill of material revision level. Some forms display data based on the effectivity dates you enter.
jdForecastStartDate	STRT	JDEDATE	OPT	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.
szForecastType1	TYPF	char	OPT	NONE
A user defined code (34/DF) that indicates one of the following: o The forecasting method used to calculate the numbers displayed about the item o The actual historical information about the item
szForecastType2	TYPF	char	OPT	NONE
A user defined code (34/DF) that indicates one of the following: o The forecasting method used to calculate the numbers displayed about the item o The actual historical information about the item
szForecastType3	TYPF	char	OPT	NONE
A user defined code (34/DF) that indicates one of the following: o The forecasting method used to calculate the numbers displayed about the item o The actual historical information about the item
szForecastType4	TYPF	char	OPT	NONE
A user defined code (34/DF) that indicates one of the following: o The forecasting method used to calculate the numbers displayed about the item o The actual historical information about the item
szForecastType5	TYPF	char	OPT	NONE
A user defined code (34/DF) that indicates one of the following: o The forecasting method used to calculate the numbers displayed about the item o The actual historical information about the item
cLotStatusCode1	LOTS	char	OPT	NONE
A user defined code (41/L) that indicates the status of the lot. If you leave this field blank, it indicates that the lot is approved. All other codes indicate that the lot is on hold. You can assign a different status code to each location in which a lot resides on Item/Location Information or Location Lot Status Change.
cLotStatusCode2	LOTS	char	OPT	NONE
A user defined code (41/L) that indicates the status of the lot. If you leave this field blank, it indicates that the lot is approved. All other codes indicate that the lot is on hold. You can assign a different status code to each location in which a lot resides on Item/Location Information or Location Lot Status Change.
cLotStatusCode3	LOTS	char	OPT	NONE
A user defined code (41/L) that indicates the status of the lot. If you leave this field blank, it indicates that the lot is approved. All other codes indicate that the lot is on hold. You can assign a different status code to each location in which a lot resides on Item/Location Information or Location Lot Status Change.
cLotStatusCode4	LOTS	char	OPT	NONE
A user defined code (41/L) that indicates the status of the lot. If you leave this field blank, it indicates that the lot is approved. All other codes indicate that the lot is on hold. You can assign a different status code to each location in which a lot resides on Item/Location Information or Location Lot Status Change.
cLotStatusCode5	LOTS	char	OPT	NONE
A user defined code (41/L) that indicates the status of the lot. If you leave this field blank, it indicates that the lot is approved. All other codes indicate that the lot is on hold. You can assign a different status code to each location in which a lot resides on Item/Location Information or Location Lot Status Change.
szScheduleType	SCHT	char	OPT	NONE
A user defined code (system 31, type ST) that identifies the type of schedule, for example, AC for actual schedule and PL for planned schedule.
cPlannedOrderFlag	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
cLotExpirationFlag	EV02	char	OPT	NONE
An option that specifies the type of processing for an event.
cStandardPotencyFlag	EV03	char	OPT	NONE
A radio button that specifies the level at which trace/track result is to be displayed. Select the Detail to display all transactions except IB, IX, and IZ types. Or, select Derivative Lots Only to display only those transactions that may have created new derivative lot.
cBulkStockingType	EV04	char	OPT	NONE
PeopleSoft event point processing flag 04.
cTransitFlag	EV05	char	OPT	NONE
A flag that indicates whether automatic spell check is turned on.
cInspectFlag	EV06	char	OPT	NONE
An option that specifies the type of processing for an event.
cReceiptRoutingSummary	EV09	char	OPT	NONE
An option that specifies the type of processing for an event.
cForecastFlag	EV02	char	OPT	NONE
An option that specifies the type of processing for an event.
cPotencyControlFlag	OT1Y	char	OPT	NONE
A code that indicates whether you control the item by potency.
mnStandardPotencyValue	STDP	MATH_NUMERIC	OPT	NONE
The percentage of active ingredients normally found in an item.
cPotentUnitFlag	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
cLocationSummaryFlag	EV10	char	OPT	NONE
An option that specifies the type of processing for an event.
cPastDueRatesFlag	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
cCrossDockingFlag	XDCK	char	OPT	NONE
A code that associates items or order lines with cross-dock processing. This code might indicate whether an item or an order line is eligible for cross-docking, whether it was cross-docked, or whether it needs to be cross-docked. When it is assigned to an item or item-branch, this code indicates that the item or the item in the branch/plant is eligible for cross-docking. When it is assigned to an order line, this code indicates that the order line needs to be cross docked. Valid values are: 1 Yes, cross-docking is on 0 (blank) No, cross-docking is off
cPurchaseFlag	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
cRecRtgFlag	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
cMfgFlag	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
cRateFlag	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
cOther1Flag	EV07	char	OPT	NONE
An option that specifies the type of processing for an event.
cOther2Flag	EV08	char	OPT	NONE
An option that specifies the type of processing for an event.
szSDCacheJobNumber	JOB	char	OPT	NONE
Job Number
mnhReqCacheJobNumber	JOBS	MATH_NUMERIC	OPT	NONE
The job number (work station ID) which executed the particular job.
cSuppressErrorMessages	EV02	char	OPT	NONE
An option that specifies the type of processing for an event.
cErrorCode	ERRC	char	OPT	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	OPT	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.
szUserId	USER	char	OPT	NONE
The code that identifies a user profile.
szComputerID	CTID	char	OPT	NONE

cPeggingPartsListSumFlag	EV14	char	OPT	NONE
An option that specifies the type of processing for an event.
cEnableMPM	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
cDualUnitOfMeasureItem	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
szDispUnitOfMeasure	UOM1	char	OPT	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).

Related Functions

B3400100 Verify Supply and Demand Rule Exists
B3400300 Get Reciept Routing Data

Related Tables

None