Material consumable actual
- Last UpdatedJan 31, 2025
- 1 minute read
When the consumable command is triggered, the specified item is not added to the BOM, as the specified data is considered as a direct consumption. The specified data is added directly to the Item_Cons table.
When the update inventory Boolean flag is set to True, the quantity from the inventory is reduced.
The following table illustrates the functional data mapping between the attributes exposed in the UI and how the data is recorded in the MES database.
|
PEM Attribute |
Column in Item_Cons Table |
Comments |
|---|---|---|
|
ent_id |
The ID of the entity that triggers the middleware call. |
|
|
MaterialId |
item_id |
|
|
UnitOfMeasure |
The specified quantities are converted to the native units of the item, if the specified UOM is different from the native UOM of this item and a conversion factor exists for this item. Otherwise, an exception is logged. |
|
|
ProductionRequestId |
wo_id |
|
|
ProcessSegmentId |
oper_id |
|
|
ProductionScheduleId |
N/A |
Stored in the job_event.value1 column. |
|
SegmentRequirementId |
segment_requirement_id |
|
|
SegmentResponseId |
segment_response_id |
|
|
Comments |
comments |
|
|
Quantity |
qty_cons |
|
|
Location |
from_ent_id |
The from_ent_id is resolved by querying the Ent table using the specified entity name. |
|
SubsegmentId |
N/A |
Stored in the job_event.subsegment_id and identifies the consumable transaction in the Item_Cons table. |
|
PersonnelList |
user_id |
The other values that are recorded along with consumable are the extended attributes that are configured for this instance.