1. Time event confirmations in ERP manufacturing (PP) are used to record the start and end times of processing events, rather than confirming full orders or operations.
2. The transaction CO19 is used to enter time event confirmations by recording the start and end times of setup, processing, and teardown.
3. Calculations of confirmed times can be incorrect if the work center is not properly configured with intervals and shifts to exclude break times from the calculation. Defining shifts avoids having break times incorrectly applied.
1. Time event confirmations in ERP manufacturing (PP) are used to record the start and end times of processing events, rather than confirming full orders or operations.
2. The transaction CO19 is used to enter time event confirmations by recording the start and end times of setup, processing, and teardown.
3. Calculations of confirmed times can be incorrect if the work center is not properly configured with intervals and shifts to exclude break times from the calculation. Defining shifts avoids having break times incorrectly applied.
1. Time event confirmations in ERP manufacturing (PP) are used to record the start and end times of processing events, rather than confirming full orders or operations.
2. The transaction CO19 is used to enter time event confirmations by recording the start and end times of setup, processing, and teardown.
3. Calculations of confirmed times can be incorrect if the work center is not properly configured with intervals and shifts to exclude break times from the calculation. Defining shifts avoids having break times incorrectly applied.
1. Time event confirmations in ERP manufacturing (PP) are used to record the start and end times of processing events, rather than confirming full orders or operations.
2. The transaction CO19 is used to enter time event confirmations by recording the start and end times of setup, processing, and teardown.
3. Calculations of confirmed times can be incorrect if the work center is not properly configured with intervals and shifts to exclude break times from the calculation. Defining shifts avoids having break times incorrectly applied.
Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt
You are on page 1/ 17
Former M emb er
March 5, 2014 2 mi nute read
Capture Production Idle time through
Notification FollowRSS feed 0 Li kes 420 Views 1 C omment
Idle time can be captured during confirmations or through PM Breakdown notifications.This Blog is regarding a workaround solution for capturing the production idle time by production department.
Requirement:
During production process machine is idle for various reasons like machine repairs,no power etc. With reference to the machine and reason code machine total idle time needs to be recorded along with start date, start time, end date and end time.
Approach:
Each Machine is created as Equipment. Production Work center is assigned to equipment and PM Notification concept is used to capture the Idle time with required reason codes and times.
Configuration:
Path: Plant Maintenance and Customer Service – Maintenance and Service Processing – Maintenance and Service Notifications -Overview of Notification Type
Created Notification IT of type 01 -Maintenance Notification as displayed below
Included only two tabs as given below
Changed the Tab header description as required to be displayed. Here option to add icon is also available. QS41 – Reason codes Master Data:
Assigning Work Center to Equipment.
Equipment created in IE01 and production work center assigned as shown below in IE02 (Change Equipment)
Process Steps: Create and Complete Notification ( IW21):
Below screen appears. Select Notification of Type IT
Enter the Equipment Number and put F4 under Code group to display the reason codes.
Select the reason code
Enter the Total Idle Hours under Activity text, Start Date, Start Time, End Date and End Time as displayed below If we click on Location data Tab Production Work Center assigned to the equipment will be displayed.
Click on Release Flag to release the notification.
Click on Complete Flag to complete the notification.
Enter the reference date, time and click on continue.
Notification 100000023 got created, Idle Time got recorded and Notification completed in system.
Once Notification is completed status changed to NOCO and further changes are not allowed as displayed below.
Reports:
IW64 – List of Notifications with Type IT will display all the idle time notifications. 1. ERP Manufacturing (PP) 2. … 3. Order Confirmation (EXE-CON)
Time event confirmation
Skip to end of metadata
Created by Former Member, last modified on Feb 19, 2016
Go to start of metadata
Purpose In this section we will see through the basics of time event confirmation.
Overview In the first part it will be described how to make a time event confirmation, then an example calculation related to KBA 1576702 (see below) will be shown.
Time event confirmation
Transaction: CO19 this type of confirmation does not confirm the whole order or operation, its main focus is the processing itself it must be added, at which point the processing started and ended
Setting of the standard values
Transaction CO02 - operation overview-details -> StandardVals tab -> Setup time has been defined Entering the confirmation CO19 -> Start of setup and insert order number + operation CO19 -> Actual data -> Personnel No.: effect on HR update or on documentation; it is possible to insert here a number without handing over to HR
CO19 -> Actual data -> Start setup: it is set automatically to system date, but it can be set to a past date
CO19-> Finish setup and insert order number + operation -> Save Displaying the confirmation
Transaction CO14 - choose the confirmations-details -> Start of setup >>> next page: Finish setup Characteristics of time event confirmation CO19 -> Start processing and insert order number + operation
- start processing is always a partial confirmation (PCNF)
- by end processing there is a possibility to set partial or final confirmation (it is possible to post additional confirmations even if the confirmation is final confirmed)
CO19 -> Finish processing and insert order number + operation
- it is not possible to post in the future!
- it is possible to add more than one start and finish processing (e.g. 3 different workers , waiting time)
- yields and quantities can only be inserted in (finish) processing, but in the setup and teardown not
Status of the order in time event confirmation
Transaction CO03-operation details -> System status: PCNF (because the start of processing was posted with status partial) the system uses always the last confirmation to check which status the operation needs to get (CO14: we can see whether the confirmations are finally confirmed, the last confirmation is partial confirmed, that’s why the system status in CO03 is PCNF)
Example: the highest confirmation needs to be reflected in the status
Solution: it is NOT possible in standard; customers need to add an own logic
Calculation for KBA 1576702
Example: start and end processing are set and normally the system calculates between the start and the end date, but it is not correct
e.g. start setup was at 10:00:00 and finish setup was at 11:00:00
Solution: problem is in the work center! Transaction CR02-header -> Standard available capacity
e.g. there are machines which run 8 hours, it cannot be stopped, the worker can define when would like to have a break, for example half an hour at 10 and half an hour at 1 or 1 hour at lunchtime but there is a requirement to define I have not fixed break time and it is displayed here: CR02-header -> Standard available capacity -> Intervals and shifts button (huge and detailed timeframe); if customer doesn’t have intervals and shifts, then it cannot be said when there should be exactly the break and this leads to calculation 53,33 >>> the break time is always divided to the confirmed hours
If the customer doesn’t want, that the break time calculated, a shift model is need to be defined. Example with numbers
in CO19 confirm:
Start of Setup 13.08.2013 10:00:00
Finish Setup 13.08.2013 10:30:00
And then:
Start of Proc. 13.08.2013 10:45:00
Fin. Processing 13.08.2013 11:26:34
in CO03 the results:
If we calculate
Start of Proc. 13.08.2013 10:45:00
Fin. Processing 13.08.2013 11:26:34
we have 41 min 34 sec, this is 2494 sec = 41,5666 min = 0,6927 hrs.
The system calculates 0,616 hr as in work center, where 8-17 and 1 hour break is definied. So calculation: 540 min need 60 min break (work center base) and confirmed was 41,566 min >>> 60*41,566 / 540 = 4,618 min break
So the 41,566 min confirmed has a calculated break time of 4,618 min, so we have real time without break 41,566 – 4,618 = 36,984 min = 0,616 hrs
Related Content Related Documents SAP Help Entering a Confirmation for a Time Event
Related SAP Notes/KBAs
SAP KBA 1576702: Confirmed activity times not displayed correctly in transaction CO19
