Skip to end of metadata
Go to start of metadata

Sometimes in different activities we need to utilize different replaceable parameters in order to get the same entity. For example %UNIT_SFC% parameter must be used as common parameter with Events to get SFC number, but %SFCBO.(2)%  as Nonconformance-related.

  • Common Replaceable Parameters You Can Use with Events

The following table describes common replaceable parameters you can use with Events:

Replaceable Parameter

Value the system supplies

%SITE%

The site for the event.

%EVENT_DATE%

The date the event occurred.

%ALARM_TYPE%

The type of event.

%MESSAGE_TEXT%

The text provided by the application that creates the event.

%SEVERITY%

The severity of the event.

%RESRCE%

The resource from which the event originated.

%SIG_USER_BO%

The user from whom the event originated.

%UNIT_OPERATION%

The operation during which the event occurred.

%UNIT_ITEM%

The item associated with the event.

%UNIT_SFC%

The SFC associated with the event.

%WORK_CENTER%

The work center where the event occurred.

%UNIT_SHIFTID%

The shift when the event was triggered.


  • Nonconformance-Related Replaceable Parameters You Can Use with Events

The following table describes nonconformance-related replaceable parameters you can use with Events:

Replaceable Parameter

Value the system supplies

%COMMENTS%

Text entered by the operator.

%COMP_CONTEXT_GBO.(1)%

If the identifier associated with the NC entry is an SFC, the site of the SFC.
If the identifier associated with the NC entry is an Inventory ID, the inventory ID of the SFC.

%COMP_CONTEXT_GBO.(2)%

The NC entry's SFC number. Use only when the identifier associated with the NC entry is SFCBO.

%COMPONENT_BO.(1)%

The site of the component that was nonconformed.

%COMPONENT_BO.(2)%

The component that was nonconformed.

%COMPONENT_BO.(3)%

The component revision.

%DATE_TIME.[timepatternstring]%

The date/time the entity (typically SFC) was acted upon in the form and format specified by timepatternstring.
For example: On January 2 in 2001, %DATE_TIME.[yddd]% generates 01002.

%DEFECT_COUNT%

The count of defects.

%FAILURE_ID%

The failure ID associated with the nonconformance.

%IDENTIFIER%

The component or inventory ID against which the nonconformance was logged.

%INCIDENT_DATE_TIME.[timepatternstring]%

The date and time the original incident was logged.

%INVENTORY_BO.(1)%

The inventory ID of the SFC.

%ITEM_BO.(1)%

The site of the item produced by the SFC, or the component being nonconformed.

%ITEM_BO.(2)%

The item produced by the SFC, or the component being nonconformed.

%ITEM_BO.(3)%

The revision of the item or nonconformed component.

%NC_CODE_BO.(1)%

The site where the NC code is defined.

%NC_CODE_BO.(2)%

The NC code.

%NC_CONTEXT_GBO.(1)%

The site of the SFC against which the NC was logged.

%NC_CONTEXT_GBO.(2)%

The SFC against which the NC was logged.

%OPERATION_BO.(1)%

The site of the operation at which the NC was logged.

%OPERATION_BO.(2)%

The operation at which the NC was logged.

%QTY%

The number of pieces of the SFC that were nonconformed.

%REF_DES%

The reference designator of the nonconformed component.

%RESOURCE_BO.(1)%

The site of the resource at which the NC was logged.

%RESOURCE_BO.(2)%

The resource at which the NC was logged.

%SFC_BO.(1)%

The site of the SFC against which the NC was logged.

%SFC_BO.(2)%

The SFC against which the NC was logged.

%WORK_CENTER_BO(1)%

The site of the work center from which the SFC was nonconformed.

%WORK_CENTER_BO(2)%

The work center from which the SFC was nonconformed.


  • The following table describes replaceable parameters you can use as prefixes and suffixes to create a numbering pattern in Next Number Maintenance:

Replaceable Parameter

Value the system supplies

%ACTIVITY%

The ID or the activity that released the SFC.

%DATE_TIME.[timepatternstring]%

The date/time the entity (usually, SFC) was acted upon (released, nonconformed, and so forth), in the form and format specified by timepatternstring.
For example: On January 2 in 2001, %DATE_TIME.[yddd]% generates 01002.

%ITEM_BO.(1)%

The site where the item is being released.

%ITEM_BO.(2)%

The item being released.

%ITEM_GROUP_BO.(1)%

The site where the item group for the item being released.

%ITEM_GROUP_BO.(2)%

The item group for the item being released.

%ONEDIGITYEAR%

The last digit of the current year.

%WEEKOFYEAR%

The current week of the current year.
For example: On January 19, 2003, %WEEKOFYEAR% generates week 4.

%PARENT_SHOP_ORDER_BO.(1)%

The site of the shop order's immediate parent.

%PARENT_SHOP_ORDER_BO.(2)%

The shop order's immediate parent.

%PRIORITY%

The priority of the shop order.

%SHOP_ORDER_BO.(2)%

The shop order of the SFC.

%SITE%

The site at which the release is taking place.

%USER_BO.(1)%

The site of the user ID of the person performing the action.

%USER_BO.(2)%

The user ID of the person performing the action (release, logging of the nonconformance, and so forth).