Attribute behavior during run time
- Last UpdatedNov 05, 2024
- 3 minute read
The following table lists the PEM instance attributes and indicates whether they can be created at run time if they do not exist and whether a new data entry job can be created if the value changes.
Production attributes are not updated when using an input source until the object is triggered.
|
PEM Instance Attributes |
Create if does not exist |
Create new data entry job if changed |
Comments |
|---|---|---|---|
|
Comments |
No |
No |
The value is logged when the production or consumption transaction is reported. |
|
Equipment ID |
No |
No |
The value is logged when the production or consumption transaction is reported. |
|
Event Date Time |
No |
No |
If this attribute supports input source, the value is always read from the input source. If the Auto Generate option is set to True, a date time value is generated at run time when the trigger command is triggered. If the Auto Generate and Use Input Source options are set to True, the value is read from the input source. If none of the options are selected, a blank datetime value is sent to the middleware at run time. |
|
Event ID |
No |
No |
This value is logged when the production transaction is reported (item_prod.event_id). |
|
Event Link ID |
No |
No |
This value is logged when the consumption transaction is reported (item_cons.upstream_event_id). |
|
Event Name |
No |
No |
The event_name value is stored in the job_event.value3 column. |
|
Location |
No |
No |
This value is logged when the production or consumption or subsegment transaction is reported. |
|
Lot |
No |
No |
This value is logged when the production or consumption or subsegment transaction is reported. |
|
Material ID |
Yes |
No |
Create new item if the specified value is not null and it does not exist in the database. |
|
Material Type |
No |
No |
This value is logged when a production transaction is reported. The material_type is also logged in the job_event.value9 column. This attribute is applicable only to Material Produced Event. |
|
Personnel List |
No |
No |
The value is logged against the current production or consumption in the job_event.value4. There is no validation on the data received for personnel list, so the format of the list is completely open. For example, Jack, David Miller, etc. |
|
Process Segment ID |
Yes |
Yes |
Create new job for this work order if the value is not blank and it does not exist in the database. |
|
Production Request ID |
Yes |
Yes |
Create new work order if the value is not blank and it does not exist in the database. |
|
Production Schedule ID |
No |
No |
Update the existing production schedule ID for this work order if the production schedule ID is not same in the work order. |
|
Quantity |
No |
No |
The value is logged when the production or consumption transaction is reported. |
|
Segment Requirement ID |
No |
No |
This value is used to log data to:
|
|
Segment Response ID |
No |
No |
This value is used to log data to:
|
|
Serial Number List |
No |
No |
This value is logged against the current production or consumption in the job_event.value5. There is no validation on the data received for the serial number list, so the format of the list is completely open. For example: 00123, SNO1, etc. |
|
Sublot |
No |
No |
This value is logged when the production or consumption or subsegment transaction is reported. |
|
Subsegment ID |
No |
No |
This value is logged when the production or consumption or subsegment transaction is reported. |
|
Unit Of Measure |
Yes |
No |
Create new UOM if the specified value is not blank and it does not exist in the database. The UOM is logged in the job_event.value7 column. |