on 2024 Oct 30 12:00 AM
Dear DM users,
This post is to ask whether SFCs' status can be returned to 'open' or 'in queue' since it has been completed on POD.
When defects or failures are detected, we can post nonconformance codes and return to a previous operation activity.
Q) What if a defect is detected after the SFC completed the whole routing? I wonder we have any ways to recall it to POD with available status, or only should create a rework order.
I look forward to your comment.
BR,
Wonpyo
Request clarification before answering.
Hi, you can evaluate the following options:
1 - Create a Special Operation, which automatically creates a Special Routing, then use Operation Activity POD to load the Special Operation and the respective Resource, where you should be able to type-in 'Done' SFCs, start them in the Special Routing and complete them again. See more details in SAP Help:
https://help.sap.com/docs/sap-digital-manufacturing/execution/manage-operation-activities
https://help.sap.com/docs/sap-digital-manufacturing/execution/pulling-sfc-into-special-operation-act...
2 - Create a 'NC Routing', assign it as a 'Disposition Routing' to a Nonconformance code, and then use a POD of Type 'Standalone Nonconformance' to browse and select 'Done' SFCs, raise the Nonconformance to disposition 'Done' SFCs to this NC Routing and complete them again. See more details in SAP Help:
https://help.sap.com/docs/sap-digital-manufacturing/execution/nonconformance-disposition-routings
https://help.sap.com/docs/sap-digital-manufacturing/execution/nc-disposition-routings
Keep in mind that, as all these Operations and Routings are created directly in SAP Digital Manufacturing itself, therefore nothing is reported back to ERP in these cases.
Hope it helps,
Manoel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I tried to describe these options in more detail at: https://community.sap.com/t5/supply-chain-management-blogs-by-sap/bring-done-sfcs-back-to-work/ba-p/...
Thanks for your comment, Manoel!
I think your solution is a great way, but... unfortunately, my practice is not going well.
As you guided in the link, I created a special operation activity, and a routing was automatically generated including the activity. On Operation Activity POD, I put a 'Done' type SFC's number, the special activity, and the respective resource; and pressed 'Enter' instead of 'Go'. I had expected the SFC comes out with open status, but system said, no records found.
On the other hand, I created a nonconformance code, its group, NC routing and put it as a nonconformance disposition routing. However any SFCs and operation activities were not visible on Standalone Nonconformance POD.
Would you please give me more details?
BR,
Wonpyo
Hi,
For scenario 1, as described in the blog, you must enter a done SFC, Special Operation and Resource first, then press Enter and then press Start. Only after you Start the special operation, the SFC will show up. Pressing 'Go' button will show 'No records found' message, as the SFC is currently in 'Done' status until you start it in the special operation.
For scenario 2, as described in the blog, you must first browse and select a done SFC. Once you select it, other fields like Operation, Work Center and Resource will not populate, as the SFC is currently DONE. In this POD, Operation Activity is SFC-specific and will not populate unless you select an In Work SFC. With the done SFC selected, you can Add the nonconformance code and use Done to trigger the disposition, and only after that the raised nonconformances will show in NC Data Tree plugin.
I suggest you review your setup and execution steps in detail based on my blog post, and put some extra effort into investigating the scenarios I tested and described in detail, as they should work just fine.
Br,
Manoel
Hi, @ManoelCosta!
I apriciate your reply. My work has gone well with your guidance.
By the way, for the second scenario, Standalone Nonconformance POD is not able to publish onto my fiori launch-pad even though it does not exist on launch-pad in default. So I tried the process on POD preview.
Furthermore, you wrote in your blog:
In my thoughts, "are (not) known by or mapped back to ERP" sounds more correct, doesn't it?
Best regards,
Wonpyo
User | Count |
---|---|
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.