Skip to Content
0

CT999 disabled -> BOM missing for splitted SFC

Apr 28, 2017 at 07:05 AM

33

avatar image
Former Member

Hi all,

when I disable the site hook CT999 and then split a SFC, the child SFC does not inherit the BOM. Is there a way to change this behaviour?

My scenario: I have a SFC and assemble a part of it with components of batch 1 and partial complete. For traceability I want to split the SFC when I change my component batch. When I disable the CT999 site hook the component traceability data is not copied to the child SFC on SFC split, as desired. Unfortunately also the BOM reference is lost and I end up with a child SFC without a BOM. So I cannot assemble any further required components.

If I enable the CT999 site hook, then on SFC split also the already assembled quantity is splitted and the component batch 1 is logged to the child SFC. This would therefore not fit my requirements.

Has anyone an idea how to solve the issue? Or is it maybe a bug in SAP ME?

Thanks and best regards,

Christian

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

avatar image
Former Member
May 09, 2017 at 11:12 AM
0

Hello Christian,

I'm not sure why the child SFC loses the BOM reference when you disable CT999, but pretty sure it is not something you can change; you could submit a support incident. You could use Change Production activity or PAPI to reinstate it.

Be aware that without CT999, the parent SFC's BOM Component Qty Required will still be adjusted down so could be less than the Qty Assembled. Also, if you split off 100% of the quantity, then you'll have lost the component traceability associated with the Invalid parent SFC.

I don't know your scenario, but possible alternative to splitting would be to release a new SFC so the child SFC would not inherit any data from the parent SFC, but take it from the shop order.

Regards,

Andrew.

Share
10 |10000 characters needed characters left characters exceeded