You use the LogNC_Reject activity to log only primary NC codes for a selected SFC number at a selected operation, indicating that additional work must be performed at the same operation and automatically reopening all previously closed buyoffs. You can log only one reject code at an operation at one time.
Note that the Bypass Previous NC Routings system rule does not apply to this activity, because no disposition occurs in Log NC Reject (see Nonconformance Rules).
In the POD, the Log NC Reject activity is displayed as either a popover, a popup dialogue, or replaces one of the static panels.
Note
All primary NC codes must be set up to auto close.
To log NC codes for SFC number which is a member of SFC group in status Group Created or Sampling Active, use Log NC (see Log NC (NC Data Entry)).
The following table describes rules and settings that you can change for this activity in Activity Maintenance:
Rule |
Setting |
---|---|
DEFAULT_NC_CODE |
Required (default): Displays a red asterisk to indicate that an NC code is required for this activity Optional: Indicates that an NC code is optional None: Indicates that the Log NC Reject screen is not displayed. The reject happens automatically and the default NC code comment is logged. In addition, the system will automatically log the hardcoded comment Log NC Reject occurred automatically. For more information, see Default NC Code section in NC Code. |
PLUGIN_URL |
Specifies the plug-in location in the SAP ME folder structure Default value: /COM/SAP/ME/NONCONFORMANCE/CLIENT/LOGNCREJECT.JSP Caution Any changes to the PLUGIN_URL activity rule setting in Activity Maintenance may result in incorrect display of the plug-in in the POD. End of the caution. |