cancel
Showing results for 
Search instead for 
Did you mean: 

Not able to start the SFC again after logging the NC

former_member209133
Participant
0 Kudos

Hi,

We want to log a non conformance which gets auto close  and again put the SFC from active to inqueue status.

This is require to capture the data collect multiple times at the same work center.

To achieve this we have created NC code as "AutoClose" having type as Defect.

In deposition routing we have added only one block i.e. return to original. SO once the NC gets logged, it will come back to original operation(same work center).

But after the logging the nc we are not able to start the opeartion even its status become inqueue until we refresh the page/POD

We are performing following steps:

1. Provide a work centre and retrieve

2. Start the SFC

3. Perform inspection lot and perform data collection with a value out of limit which ask for the logging non conformance.

4. Log a Non conformance "AutoClose". It will change the status of sfc in operation_list plugin again as inQueue.

5. Try to Start the SFC through button, its giving always error as "Please select the operation in operation list"

even after selecting the operation in operation list grid or even after retrieving the Work center again.

It only works when we are refreshing the POD link. Please suggest any alternative or fix to solve this issue.

Thanks & Regards,

Kshitiz Shrivastava

Accepted Solutions (0)

Answers (1)

Answers (1)

stuarta1
Active Participant
0 Kudos

Kshitiz

Define the NC code's Disposition Group as "LOCAL_REWORK", since that seems to be what your business process seems to be doing: the SFC remains where it is and can be processed further at the current step. With the disposition as Local Rework, the SFC will still remain in work, so there is no need to restart the SFC or refresh the POD.

Stuart

former_member209133
Participant
0 Kudos

Thanks Stuart for the response.

We have tried this approach also but its keep the SFC in work. If SFC is in work it will not allow to perform the data collection again until we make it as in queue.

First time we have done the data collection with out of tolerance limit hence require to log a NC.

Before completing the SFC after NC need to do data collection again under tolerance limit.

Regards,

Kshitiz

stuarta1
Active Participant
0 Kudos

You should be able to collect the data when it is in work. How is your data collection defined?

0 Kudos

You can try playing either with USEABLE_AS_IS disposition function which returns SFC back in queue or with "Allow Multiple Data Collection" system rule.

former_member209133
Participant
0 Kudos

Hi Stuart,

We are not able to perform data collection in POD. After logging the NC, if we click on inspection lot button, nothing is coming in inspection plugin. If we refresh the page and then click on inspection lot then it shows the dc group and we can click on OK. On clicking OK button, data collection entry will come which is blank hence we are not able to perform again data collection in POD.

In data collection maintenance -Over ride min/max & soft limit check on min/max both check box are selected.


Regards,

Kshitiz

former_member209133
Participant
0 Kudos

Thanks Sergiy for the response.

USEABLE_AS_IS is it a disposition group? I am not able to find it. We are working on SAP ME 15.0 version.


Allow Multiple Data Collection is already true, it is not allowing to do multiple data collection through configuring inspection lot and data collection plugin in POD.


Regards,

Kshitiz

stuarta1
Active Participant
0 Kudos

This sounds like a bug to me, and you should perhaps get this addressed rather than trying work around the issue. Placing the SFC in queue should be unnecessary to re-collect data if the system rule is set to allow re-collection.

stuarta1
Active Participant
0 Kudos

USEABLE_AS_IS is a disposition function and is in 15.0. So you can create a disposition group from that and reference it in your NC. However, all it does is "return to original", as you have already tried.

0 Kudos

It looks as if you are talking about Quality Inspection integrated with ERP. If so, then re-collecting the data is available only after disposition from the current operation. If the rule is turned off, then re-collection is not allowed at all.

This is a difference between basic process of Data Collection and ERP Quality Inspection process.

former_member209133
Participant
0 Kudos

Yes Sergiy, you are right. We are doing quality inspection integrated with ERP.

To perform inspection again at same operation, we are logging the NC which is attaached with a routing only having return to original block.

Everything is working only when we refresh the POD after logging the NC.

When we are using LOCAL_REWORK disposition group. It is not allowing it to perform inspection again at same operation.

Regards,

Kshitiz