1.1Purpose
This business function is designed specifically for Load Disposition programs. It will perform the validation of load disposition header information and
write cache records that will be used by the application.
1.2Setup Notes and Prerequisites
This function will not actually write or update to the Load Header file, you must call
DispositionLoadEndDoc for that to happen.
1.3Special Logic
2.Technical Specifications
2.1Parameters
Parameters
CData Item Data Structure DescriptionI/OReqNotes
SUPPScSuppressErrorMessageIY
DTAIszErrorMessageIDOY
JOBSmnTransportationJobNumberI/OY
VMCUszPlanningDepotIY
LDNMmnLoadNumberI
EV01cBatchModeIY
which would normally been done by the interactive application.
EV02cDispositionRequiredO'0' Auto Disposition can be performed '1' = The disposition application must be called to
perform the disposition.
TRDJjdDateTransactionI/O
TRTMmnTransactionTimeI/O
MCUszBusinessUnitInvI/O
PIDszProgramIdI
VERSszVersionI
^
D4900730A - Disposition Load Begin Doc
Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
---|---|---|---|---|
cSuppressErrorMessage | SUPPS | char | OPT | INPUT |
A flag indicating whether or not runtime error messaging will occur when an error message is issued from a business function.
0 = allow
| ||||
szErrorMessageID | DTAI | char | OPT | OUTPUT |
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
| ||||
mnTransportationJobNumber | JOBS | MATH_NUMERIC | OPT | BOTH |
The job number (work station ID) which executed the particular job. | ||||
szPlanningDepot | VMCU | char | REQ | INPUT |
Indicates the depot from which a trip originates. The Trip Depot and the Trip Number fields identify the unique combination of vehicle,
| ||||
mnLoadNumber | LDNM | MATH_NUMERIC | REQ | INPUT |
1 | ||||
cBatchMode | EV01 | char | OPT | INPUT |
An option that specifies the type of processing for an event. | ||||
cDispositionRequired | EV02 | char | OPT | OUTPUT |
An option that specifies the type of processing for an event. | ||||
jdDateTransaction | TRDJ | JDEDATE | OPT | BOTH |
The date that an order was entered into the system. This date determines which effective level the system uses for inventory pricing. | ||||
mnTimeTransaction | TRTM | MATH_NUMERIC | OPT | BOTH |
The time that the transaction occurred. It is used by reconciliations when reconciling all transactions through a given date and time. | ||||
szBusinessUnitInv | 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
| ||||
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
| ||||
szVersion | VERS | char | OPT | INPUT |
A user-defined set of specifications that control how applications and reports run. You use versions to group and save a set of user-defined
|
None |
None |