GetContainerData

The
GETCONTAINERDATA
 execute retrieves a list of container and lot data entries that specify container binding options for the phase to be run using manual phase control.
The format and return for this execute includes:
Execute Format
A
FactoryTalk Batch
 Server supports an execute with this format:
[GETCONTAINERDATA(
Item,UserID,UnitID,EqModID, FeedType, MaterialName
)]
where:
Item
Item name as specified by the client.
UserID
User identification associated with this event.
UnitID
Unit Resource ID containing the phase to be run.
EqModID
Resource ID for the phase to be run.
FeedType
Type of feed the phase will be performing. This is the literal value "ADDITION" or "DISTRIBUTION".
MaterialName
Name of the material that the step adds or distributes.
Action
A successful GETCONTAINERDATA execute returns a list of container and lot entries that may be legally bound to.
Return Format
The item populates with this data:
SUCCESS:
<ContainerData>
| FAIL:
<message>
where:
<ContainerData>
is
<NullList>
|
<ContainerList>
<ContainerList>
is
<BindEntry>
|
<BindEntry><ContainerList>
<BindEntry>
is
<ContainerName>
\t
<ContainerControllerID>
\t
<Capacity>
\t
<CEU>
\t
<LotName>
\t
<Label>
\t
where:
Field Name
Format
Description
<ContainerName>
ASCII
Container name.
<Container
ControllerID>
ASCII
ID for the container.
<Capacity>
ASCII
For an addition, this is the quantity of material in the container.
For a distribution, this is the remaining (available) volume of the container.
<CEU>
ASCII
Engineering units used to measure a container’s volume.
<LotName>
ASCII
Name of the lot.
<LabelName>
ASCII
Label assigned the quantity of material.
The following table shows an example of the return on this execute.
Example:
An execute string:
GETCONTAINERDATA(DATA,STATION5/
Operator,55,70,ADDITION,EGG_YOLK)
Requesting data from DATA returns:
SUCCESS:TEMP_EGG \t 27 \t 660916 \t KG \t EGG_LOT3 \t EGGS3 \crlf
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal