Process batch
Note: The X icon indicates Yes. In Mode columns, X indicates that the
fields are optional in the specified operation. Where noted as mandatory, the field is
required in the specified action.
Type | Length | PK | FK | Mode | Mandatory | Remarks | |||||
---|---|---|---|---|---|---|---|---|---|---|---|
Table | Field | Read | Write | Delete | Create | Update | |||||
any related order code | STRING | 80 | X | ||||||||
changeover | NUM | X | X | Maximum changeover time for jobs related to the process batch | |||||||
changeover cost | NUM | X | Maximum changeover cost for jobs related to the process batch | ||||||||
code | STRING | 80 | X | X | X | X | X | The batch code is the unique identifier of a batch. The batch code is automatically generated by Infor Production Scheduling at the time of batch creation or assigned by an external system. | |||
color | STRING | 80 | X | X | If the batch uses the color of the default process step, the "color" attribute exports the value of "-1". | ||||||
color2 | STRING | 80 | X | This attribute allows exporting the actual display color of the batch, as opposed to the "color" attribute. This attribute can only be exported. To modify the display color of a batch through the batch interface, use the "color" attribute. | |||||||
custom data 01 | STRING | 80 | X | X | |||||||
custom data 02 | STRING | 80 | X | X | |||||||
custom data 03 | STRING | 80 | X | X | |||||||
custom data 04 | STRING | 80 | X | X | |||||||
custom data 05 | STRING | 80 | X | X | |||||||
custom data 06 | STRING | 80 | X | X | |||||||
custom data 07 | STRING | 80 | X | X | |||||||
custom data 08 | STRING | 80 | X | X | |||||||
custom data 09 | STRING | 80 | X | X | |||||||
custom data 10 | STRING | 80 | X | X | |||||||
custom data 11 | STRING | 80 | X | X | |||||||
custom data 12 | STRING | 80 | X | X | |||||||
custom data 13 | STRING | 80 | X | X | |||||||
custom data 14 | STRING | 80 | X | X | |||||||
custom data 15 | STRING | 80 | X | X | |||||||
custom date+time 01 | DATE | X | X | ||||||||
custom date+time 02 | DATE | X | X | ||||||||
custom date+time 03 | DATE | X | X | ||||||||
custom date+time 04 | DATE | X | X | ||||||||
custom date+time 05 | DATE | X | X | ||||||||
custom date+time 06 | DATE | X | X | ||||||||
custom date+time 07 | DATE | X | X | ||||||||
custom date+time 08 | DATE | X | X | ||||||||
custom date+time 09 | DATE | X | X | ||||||||
custom date+time 10 | DATE | X | X | ||||||||
custom value 01 | REAL | X | X | ||||||||
custom value 02 | REAL | X | X | ||||||||
custom value 03 | REAL | X | X | ||||||||
custom value 04 | REAL | X | X | ||||||||
custom value 05 | REAL | X | X | ||||||||
custom value 06 | REAL | X | X | ||||||||
custom value 07 | REAL | X | X | ||||||||
custom value 08 | REAL | X | X | ||||||||
custom value 09 | REAL | X | X | ||||||||
custom value 10 | REAL | X | X | ||||||||
duration | TIME | X | X | ||||||||
earliest start | DATE | X | The earliest start time of a batch is the first point in time at which the batch can start, considering the time constraints imposed by coupled batches and orders. | ||||||||
efficiency | REAL | X | X | The efficiency concept helps account for the fact that a batch can run at a certain percentage of its theoretical outflow rate. When batches are created they are initially assigned the efficiency of the linked resource group. | |||||||
end inflow | DATE | X | The end inflow of a process batch is the point in time that the inflow segment ends. | ||||||||
end outflow | DATE | X | X | The end outflow of a process batch is the point in time that the outflow segment ends. | |||||||
external code | STRING | 80 | X | X | X | ||||||
external resource code | STRING | 80 | X | ||||||||
external version | STRING | 80 | X | ||||||||
filling/standing time | TIME | X | X | The filling or standing time is the offset (in minutes) between the inflow and the outflow segment of the batch. | |||||||
last modified | DATE | X | |||||||||
latest end time | DATE | X | The latest end of a process batch is the latest point in time at which the batch can end in order to ensure that the batch can be ready for the following coupled batches or orders. | ||||||||
main product | STRING | 80 | product | code | X | X | X | code for the product of the related pstep | |||
model name | STRING | 80 | X | resource, resource group, process step | model name | X | X | ||||
outflow rate | REAL | X | X | The outflow rate is the working rate or the turn-over rate of a batch expressed in units of the main product per hour. | |||||||
process step description | STRING | 80 | X | The description of the related process step. | |||||||
product unit | STRING | 80 | X | ||||||||
quantity | REAL | X | X | X | Batch quantity is the quantity of the main product that flows out of the batch, expressed in the units of that product. | ||||||
release duration | NUM | X | X | ||||||||
remarks | STRING | 80 | X | X | |||||||
resource | STRING | 80 | resource | code | X | X | For a Choice group there can be only one related resource. For a combination group all resourcesfrom the group is selected. | ||||
resource group | STRING | 80 | resource group | code | X | X | |||||
resource memo | STRING | 80 | X | X | For a Choice resource group there can be only one related resource. For a combination resource group one resource from the group is selected. | ||||||
setup | NUM | X | X | Maximum setup time for jobs that are related to the process batch. | |||||||
setup cost | NUM | X | Maximum setup cost for jobs that are related to the process batch | ||||||||
split link | STRING | 80 | X | X | Group name for linked split process batches. | ||||||
start inflow | DATE | X | X | The start inflow of a process batch is the point in time that the inflow segment starts. | |||||||
start outflow | DATE | X | X | The start outflow of a process batch is the point in time that the outflow segment starts. | |||||||
status | STRING | 80 | status | code | X | X | |||||
surplus quantity | REAL | X | The surplus quantity is the quantity of the process batch that is not linked as inflow for a following tank batch or order. | ||||||||
version | STRING | 80 | process step | version | X | X | version of the related process step | ||||
week of delivery | NUM | X | X | ||||||||
year of delivery | NUM | X | X | ||||||||
[order]custom data 01 | STRING | 80 | X | ||||||||
[order]custom data 02 | STRING | 80 | X | ||||||||
[order]custom data 03 | STRING | 80 | X | ||||||||
[order]custom data 04 | STRING | 80 | X | ||||||||
[order]custom data 05 | STRING | 80 | X | ||||||||
[order]custom data 06 | STRING | 80 | X | ||||||||
[order]custom data 07 | STRING | 80 | X | ||||||||
[order]custom data 08 | STRING | 80 | X | ||||||||
[order]custom data 09 | STRING | 80 | X | ||||||||
[order]custom data 10 | STRING | 80 | X | ||||||||
[order]custom data 11 | STRING | 80 | X | ||||||||
[order]custom data 12 | STRING | 80 | X | ||||||||
[order]custom data 13 | STRING | 80 | X | ||||||||
[order]custom data 14 | STRING | 80 | X | ||||||||
[order]custom data 15 | STRING | 80 | X | ||||||||
[order]custom date+time 01 | DATE | X | |||||||||
[order]custom date+time 02 | DATE | X | |||||||||
[order]custom date+time 03 | DATE | X | |||||||||
[order]custom date+time 04 | DATE | X | |||||||||
[order]custom date+time 05 | DATE | X | |||||||||
[order]custom date+time 06 | DATE | X | |||||||||
[order]custom date+time 07 | DATE | X | |||||||||
[order]custom date+time 08 | DATE | X | |||||||||
[order]custom date+time 09 | DATE | X | |||||||||
[order]custom date+time 10 | DATE | X | |||||||||
[order]custom value 01 | REAL | X | |||||||||
[order]custom value 02 | REAL | X | |||||||||
[order]custom value 03 | REAL | X | |||||||||
[order]custom value 04 | REAL | X | |||||||||
[order]custom value 05 | REAL | X | |||||||||
[order]custom value 06 | REAL | X | |||||||||
[order]custom value 07 | REAL | X | |||||||||
[order]custom value 08 | REAL | X | |||||||||
[order]custom value 09 | REAL | X | |||||||||
[order]custom value 10 | REAL | X | |||||||||
[process step]custom data 01 | STRING | 80 | X | ||||||||
[process step]custom data 02 | STRING | 80 | X | ||||||||
[process step]custom data 03 | STRING | 80 | X | ||||||||
[process step]custom data 04 | STRING | 80 | X | ||||||||
[process step]custom data 05 | STRING | 80 | X | ||||||||
[process step]custom data 06 | STRING | 80 | X | ||||||||
[process step]custom data 07 | STRING | 80 | X | ||||||||
[process step]custom data 08 | STRING | 80 | X | ||||||||
[process step]custom data 09 | STRING | 80 | X | ||||||||
[process step]custom data 10 | STRING | 80 | X | ||||||||
[process step]custom data 11 | STRING | 80 | X | ||||||||
[process step]custom data 12 | STRING | 80 | X | ||||||||
[process step]custom data 13 | STRING | 80 | X | ||||||||
[process step]custom data 14 | STRING | 80 | X | ||||||||
[process step]custom data 15 | STRING | 80 | X | ||||||||
[process step]custom date+time 01 | DATE | X | |||||||||
[process step]custom date+time 02 | DATE | X | |||||||||
[process step]custom date+time 03 | DATE | X | |||||||||
[process step]custom date+time 04 | DATE | X | |||||||||
[process step]custom date+time 05 | DATE | X | |||||||||
[process step]custom date+time 06 | DATE | X | |||||||||
[process step]custom date+time 07 | DATE | X | |||||||||
[process step]custom date+time 08 | DATE | X | |||||||||
[process step]custom date+time 09 | DATE | X | |||||||||
[process step]custom date+time 10 | DATE | X | |||||||||
[process step]custom value 01 | REAL | X | |||||||||
[process step]custom value 02 | REAL | X | |||||||||
[process step]custom value 03 | REAL | X | |||||||||
[process step]custom value 04 | REAL | X | |||||||||
[process step]custom value 05 | REAL | X | |||||||||
[process step]custom value 06 | REAL | X | |||||||||
[process step]custom value 07 | REAL | X | |||||||||
[process step]custom value 08 | REAL | X | |||||||||
[process step]custom value 09 | REAL | X | |||||||||
[process step]custom value 10 | REAL | X |