Configuring Customized Values

You can customize some of the default values for a node as per your requirement.

SAP OEE Configurations CTC configures the names of Customizations. Customization values are specific to a node, therefore the default values of the customizations are configured when you send a plant hierarchy IDoc from SAP ERP to ERP-Shop Floor Integration framework.

For more information, see SAP OEE Configuration CTC.

Procedure

On the SAP MII main menu screen, choose Worker UI Management General Configuration . The General Configuration screen appears.

On the Customization Configuration tab, you can maintain the customized values for the following:

Customization	Default Values	Description
UoM Conversion Transaction	SAPMPM/apps/common/MaterialUOMConversion	Allows conversion of quantity in particular for a given material, quantity, and UoM.
Allowed Modification Limit	120 mins	Duration from the current time within which order related data already reported can be modified.
Default Data Collection Element ‑ Scheduled Downtime	SCHEDULED_DOWN	If you use your own custom data collection elements for scheduled downtime, then map those custom data collection elements here instead.
Default Data Collection Element ‑ Unscheduled Downtime	UNSCHEDULED_DOWN	If you use your own custom data collection elements for unscheduled downtime, then map those custom data collection elements here instead.
Default Data Collection Element ‑ Scrap	SCRAP	If you use your own custom data collection elements for scrap, then map those custom data collection elements here instead.
Default Data Collection Element ‑ Speed Loss	SPEED_LOSS	If you use your own custom data collection elements for speed loss, then map those custom data collection elements here instead.
Allowed Time Limit for Starting Order in the Past	1440 mins (1 day)	Duration within which an order in the past can be started for reporting purposes.
Allow Modification of Automation Records	Yes	If set to no, system does not allow any modifications to be made to data reported through automation. If set to yes, you can modify the records from the dashboard.
Minor Stoppage Limit	10 mins	Duration of a downtime that is considered by the system to be a minor stoppage. Downtimes classified as minor stoppages do not have an impact on KPI calculations.
Irrelevant for OEE Calculations	No	System does not consider data reported at the line for KPI calculations.
Relevant Production Activity	No default value is set	User should maintain the production activities that are needed for the line while maintaining customizations for the plant hierarchy in SAP MII.
Retention Time for SAP HANA Replicated Tables	No default value is set	Duration for which data in SAP HANA replicated tables to be retained. If you want to retain data for a particular period, then run transaction SAPMPM/apps/DataArchive/ArchiveHANAReplicatedTables Caution Data will be deleted after the specified retention time. End of the caution.
Retention time for non-SAP HANA replicated tables	No default value is set	Duration for which data in non-SAP HANA replicated tables to be retained. If you want to retain data for a particular period, then run transaction SAPMPM/apps/DataArchive/ArchiveNonHANAReplicatedTables Caution Data will be deleted after the specified retention time. End of the caution.
Batch Number is Mandatory for Batch Managed Material	No	If set to yes, system does not allow reporting of production without batch number.
Serial Number is Mandatory for Reporting Production	No	If set to yes, system does not allow reporting of production without serial number.
Decimal Value Precision	2	Applicable for all reported quantity and fields that require quantity on the OEE dashboard.
Shift Handover Available Before Shift End	15 mins	Duration before the end of a shift from when shift handover option is available.
Date Range for Order Selection	2880 mins	This is the duration in the past and future from the current date, within which if the scheduled start date of an order lies, the order is shown in the new, hold, or completed orders list. Example If the date range for order selection is set to 2880 mins, and the current date is November 20, 2013, then the system displays all the orders that have a scheduled start date between November 18, 2013 and November 22, 2013 in the new, hold, or completed orders list. End of the example.
Unaccounted Speed Loss Limit	Allowed	Order can be completed even when unaccounted time exists.
Enable Periodic Confirmations	No	If set to yes OEE periodically confirms production data to SAP ERP.
Performance Strip Duration in the Future	4 hours	Duration in the future for which the performance strip displays scheduled downtimes.
Performance strip duration in the past	4 hours	Duration in the past for which the performance strip displays scheduled and unscheduled downtimes.
Minor Stoppages Should be Included in Availability	No	If set to yes, the system considers minor stoppages in OEE KPI calculations.
Shrinking Order Duration Allowed	No	If set to yes, order execution duration can be reduced. Example The operator reports the start of an order-operation as 10:00 am, and later realizes that the correct time is 11:00 am. If this customization is set to yes, the option to change the time is available on the dashboard. However, all the production data and downtime events reported in the duration between 10:00 and 11:00 am is lost. End of the example.

Default values can be set at the plant node level of the hierarchy and are cascaded to the lower nodes. If a customization value already exists at the lower nodes, then that value takes precedence over the customization value maintained at the plant node level.

Depending on the selected plant hierarchy node, system displays the relevant values that can be customized.

Customized values can be maintained for all materials or can be material-specific.

Line Behavior Customizations

The customization of line behavior and the corresponding system behavior is as follows:

Line Behavior	Mark Line Down if any bottleneck machine is down	Mark line down if all bottleneck machines are down	Multi-capacity single-line	Multi-capacity multi-line
Order release and download	On line level	On line level	On line level Prerequisite: Ensure that the workflow for IDoc LOIPRO01 is modified and a partner or customer XSLT overrides the standard delivered XSLT. The partner or customer XSLT should map the segment productionOrderProcesses to the number of capacities to be used for executing an order. This would depend on the IDoc in use.	On line level and capacity. Order is released on work unit capacities depending upon the quantities assigned to the individual capacities on order release in SAP ERP.
Order-operation execution	Production is reported at line level. Operator dashboard operates at line level.	Production is reported at line level. Operator dashboard operates at line level.	Production is reported at line level. Operator dashboard operates at line level. When starting an order, the operator has to select `n`number of capacities where `n` is the number of capacities required for executing the order as maintained during order release. If capacities are not selected order-operation is run on the work unit.	Order start and production reporting is allowed at the work unit capacity. Operator dashboard operates the work unit capacity with each capacity acting as a selectable work unit on the operator dashboard.
Downtime behavior	System considers the line to be down even if one bottle neck machine is down.	System considers the line to be down only if all the bottle neck machines are down.	Production and downtime can be reported on any of the capacity associated with the work unit. System considers the reported data collectively on the work unit.	Production and downtime data can be reported on the work unit or on the individual capacities associated with the order-operation. System considers the reported data separately for each capacity.
Downtime behavior	You can override the default line behavior. Choose Mark Line Down option when reporting downtime; this will mark the line down irrespective of the default line behavior setting. Downtime can be reported on the work units: line, bottleneck machine, and non‑bottleneck machine		Downtime can be reported on the work units: line, bottleneck machine, non‑bottleneck machine, and work unit capacity.
KPI calculation	Availability KPI is impacted when: Downtime is reported on the work unit representing the line. Any downtime is reported on a bottleneck machine. Downtime is reported on a non‑bottleneck machine with the Mark Line Down option selected.	Availability KPI is impacted when: Downtime is reported on the work unit representing the line. A downtime on a bottleneck machine impacts the availability of the line if all the bottlenecks are down. If any of the bottleneck machines is up during the time period, there is no impact on the availability of the line Downtime is reported on a non‑bottleneck machine with the Mark Line Down option selected.	KPIs are calculated by considering the number of capacities to be used. Example If an order executes for 60 mins and uses 5 capacities, then the loading time would be 60 * 5 = 300 mins. End of the example. Availability KPI is impacted when: Downtime is reported on the work unit representing the line. Any downtime is reported on a bottleneck machine. Downtime is reported on a non‑bottleneck machine with the Mark Line Down option selected. Downtime reported on a work unit capacity.	Availability KPI is impacted when: Downtime is reported on the work unit representing the line. Any downtime is reported on a bottleneck machine. Downtime is reported on a non‑bottleneck machine with the Mark Line Down option selected. Downtime is reported on a work unit capacity.