on 05-14-2016 9:33 AM
Hello ME experts,
Are there any other explanations that we can find about the attachment point on ME link besides the links provided below?
Data Collection Maintenance - SAP Manufacturing Execution (SAP ME) - SAP Library
Work Instruction Maintenance - SAP Manufacturing Execution (SAP ME) - SAP Library
Data collection group for SFC is not supporting resource types, but Work instruction works fine.
Operation OP1 assigned resource type REST-OP1. Resource RES1 assigned resource type REST-OP1 and REST-DCG1. Data collection group DCG1 has an attachment point OP1 and Resource type REST-DCG1. When triggering the Data collection at OP1 and RES1, DCG1 will NOT be in the data collection group list. However, work instruction WI1 assigned an attachment point OP1 and Resource type REST-DCG1, while triggering the WI at OP1 and RES1, WI1 will show as EXPECTED.
Don’t know why, is it a BUG for DCG or just a WAD? Thanks very much for your help.
Best regards,
Eason Ling
PS. Checked the CORE code of WI_LIST_DISPLAY and DC_LIST_DISPLAY.
WorkInstructionGUIService.java Line 271 (findAttachmentsWithItemGroupAndResourceTypeCheck)
DCPluginService.java Line284~296 No resource type is used.
Customer has created an incident for following up.
Will update the result soon..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI Eason,
I don't see any reason why the behaviour should be inconsistent between DCG and WIs.
Not sure if the example you gave is real or just an example, but if you have attachment on operation, then you would not need the attachment point to include resource type too, since an operation must have exactly one resource type.
Andrew.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Andrew,
Thanks for your reply.
It is a real case that we meet at customer side.
Customer is rolling out their production lines, and more and more resources are set up in the system. But at the same operation, they are using different resources provided by different vendors, and resources are defined in the same resource type. ----Operation OP1 with resource type REST-OP1
Customer defined different DCGs for SFC produced by different resource at the same operation.--- DCG1 attahced MAT1 and OP1 and RES1, which means if customer has a huge number of resources. Then the maintenance work of DCGs will be unacceptable.
Then they kind of challenge us, why resource can have more then one resource type but it doesn't work for DCG attachment point?
I did a test in Work instruction and DCG with the scenario mentioned in original post, and result is different, so i get confused.
YES, I agree with you, once the operation is maintained, no need to specify resource type again. However, there are no other documents says we shouldn't maintain the resource type with operation in DCG attached tab.
If DCG for SFC supports resource type, it will be a big help for customer to maintain the attachment points. Since assigning resource to different resource type is more easy than assigning resources to work center.
Best regards,
Eason
Once the field is available at Attached tab, its assignment should be processed. So, it is a bug.
The point is that for the case of DC Group, resource might not be always initialized, in particular, if DC is called at for in queue SFC. Then such assignment might be just skipped.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Sergiy,
Thanks~
I agree with you.
Once the field is available at Attached tab, its assignment should be processed.
Otherwise, Customer will be confused by the system behavior.
I don't think so.
The point is that for the case of DC Group, resource might not be always initialized, in particular, if DC is called at for in queue SFC. Then such assignment might be just skipped.
The test result shows that even the SFC is in queue, DC list will show the DC attached SFC material, POD operation and POD resource. From the code level, system will retrieve the resource from the POD.
Best regards,
Eason
Eason
there is no other publically available documentaiton on this. But as an SAP employee, you could contact ME's product management directly and seek clarification if this is a bug or WAD.
Stuart
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
102 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
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.