on 02-25-2015 8:12 AM
Hello Experts,
There is an issue with NC Logging and QM notification sent for the same order but from a different operation which is failing in MEINT.
The NC logging and QM notification sent from ME was successful say for operation 0010. This notification in ECC was processed and closed. Then for the same shop order but for a different SFC and on the next operation say 0020, I logged the same NC code. This time the only difference being that I had assigned data type to NC code to capture component number also.
But the error I am getting in MEINT is - "New entry not possible since notification already completed".
I was expecting that a new notification will be created since SFC and operation references are different in original document in trace report.
How is this supposed to work in such a scenario which is quite possible in a shop floor?
Would be thankful to for any inputs.
Thanks in advance.
Srinivas
The logic here is derived from the QualityNotificationHandler.
By default the logic is checking for any QN raised for the order that the NC is logged against. If it doesn't exist it creates one and if one does exist then it updates it.
Within the handler above there is a sequence number 9 called 'if QN Does not Exist'. Within the configure links of this there is the following:
stringlength(GetQualityNotifDetail.qualityNotification)<=0
Save a copy of this handler to a new folder and try changing the 0 to a something like 10 then click update and save to a different location. Change the QN workflow parameters to reference this new file. Log a few NC's against the same Order and each should create a new QN. This will stop the issue you are seeing when the QN is closed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
104 | |
12 | |
11 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.