Showing results for 
Search instead for 
Did you mean: 

Use of CT999 in Siterule for POST-SPLIT

Former Member
0 Kudos


We use PSN-Split at one step of the router.

for the steps after PSN-split, the former time-based components are not of interest and should be left away, so I wanted to deactivate the siterule CT999 for POST-SPLIT. But unfortunately, this leads to SFC without BOM. Is this reacting as designed?

We use SAP ME 6.0

Kind regards and thanks in advance to any who can answer.


Accepted Solutions (0)

Answers (1)

Answers (1)

Active Contributor
0 Kudos


As I remember the ages before CT999, SFC Split devided the existing CT data between the parent and the child SFCs proportionally, by default. And, I guess, to make this behavior configurable, CT999 was introduced. Thus, I believe that BOM should be inherited by a child SFC by default once the child remains to belong to the same Shop Order which defines the BOM of the parent SFC at release, however, whether the child inherits collected assembly data of the parent or not should be controlled by CT999.

In later releases there was a fix of SAP Note 2164161 which might be relevant to this issue. So, it would be good to test it there.