1.Functional Description
for given short Item, Business Unit and Promised Delivery Date. If a record is found , then It
will update the Transaction Quantity field otherwise it will just insert a new record.
For an item with planning fence rule of "H" and with valid document type ( exists in UDC
40/CF) ,
this business function will add a record to F3462 Forecast Summary File when a record is not
found
for given promised delivery date . If there is a record then it will update the quantity
ordered field
with a new one.
1.2Setup Notes and Prerequisites
1.3Special Logic
2.Technical Specifications
2.4Processing
1.0 ADD mnQuatityShipped and mnQuantityOrdered to mnTransactionQuantity
1.2 if a record not found
else
^
D3401380 - Data Structure for N3401380
Data Item Data Structure DescriptionI/ORequiredNotes
ITM MnShortItemNumber IY
LITM MnThirdItemNumber IY
AITM MnSecondItemNumber IY
MCU SzBusinessUnit IY
CO SzCompany IY
SOQS MnQuantityShipped IY
UORG MnQuantityOrdered IY
PDDJ JdPromisedDeliveryDate IY
PID SzProgramID IY
UPMJ MnTimeUpdated IY
TDAY MnTimeofDay IY
USER SzUser IY
JOBN SzWorkStationID IY
^
Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
---|---|---|---|---|
szIdentifier3rdItem | AITM | char | OPT | INPUT |
The system provides three separate item numbers plus an extensive cross-reference capability to alternate item numbers. These item
| ||||
szIdentifier2ndItem | LITM | char | OPT | INPUT |
A number that identifies the item. The system provides three separate item numbers plus an extensive cross-reference capability to
| ||||
mnIdentifierShortItem | ITM | MATH_NUMERIC | OPT | INPUT |
An inventory item number. The system provides three separate item numbers plus an extensive cross-reference capability to other item
| ||||
szCostCenter | MCU | char | OPT | INPUT |
An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit
| ||||
szCompany | CO | char | OPT | INPUT |
A code that identifies a specific organization, fund, or other reporting entity. The company code must already exist in the Company
| ||||
mnUnitsQuantityShipped | SOQS | MATH_NUMERIC | OPT | INPUT |
The number of units committed for shipment in Sales Order Entry, using either the entered or the primary unit of measure defined for this
| ||||
mnUnitsTransactionQty | UORG | MATH_NUMERIC | OPT | INPUT |
The quantity of units affected by this transaction. | ||||
jdPromisedDeliveryDate | PDDJ | JDEDATE | OPT | INPUT |
The promised shipment date for either a sales order or purchase order. The Supply and Demand Programs use this date to calculate
| ||||
szProgramId | PID | char | OPT | INPUT |
The number that identifies the batch or interactive program (batch or interactive object). For example, the number of the Sales Order Entry
| ||||
jdDateUpdated | UPMJ | JDEDATE | OPT | INPUT |
The date that specifies the last update to the file record. | ||||
mnTimeOfDay | TDAY | MATH_NUMERIC | OPT | INPUT |
The computer clock in hours:minutes:seconds. | ||||
szUserId | USER | char | OPT | INPUT |
The code that identifies a user profile. | ||||
szWorkStationId | JOBN | char | OPT | INPUT |
The code that identifies the work station ID that executed a particular job. |
None |
None |