You are getting caught in the functional gap between Shop Floor Control and Repetitive Manufacturing. The shop floor programs use reason type "down" to validate down time reason codes and the repetitive programs use "downtime" to validate down time reason codes. Thus, creating down time transactions in shop floor (17.4 Non-Productive Labor Feedback -- sfoptr04.p) will not show up in the repetitive downtime reports (18.4.6 Downtime by Reason Report -- reporp24.p). And visa versa.
You are probably getting the warning message in 17.4 because the reason code "D04" does not exist as a valid Shop Floor downtime code, possibly only as a Repetitive down time code, but that is just a guess.

How can we fix this issue if we still wanna continue use 17.4?we can skip that warnning message ?

Thank you very much

You can define the downtime codes in Reason Code Maintenance using the type "down" (in addition to "downtime" that repetitive uses) and the warning message should not appear. Those transactions will still not appear on the 18.4.6 report though since that only looks for repetitive transaction codes.

Many thanks for your reply, Evan.

Hello Evan:
Thanks a lot for your kindly reply.
May i ask your help again:
Can we still use 18.22.10 to record downtime for special couple reason code but without financial impact and transaction amount is zero?
Normally we use 18.22.10 to record downtime but do have financial impact ,again my question is can we assign special reason code without financial impact?

Appreciate your help.

Do you generally use the Repetitive Menu items (Menu 18...) for production and labor reporting or the Shop Floor Transactions (Menu 17...) or a mixture of both? The Shop floor transactions are used for Work Order type production where labor and production are posted against specific work orders while the Repetitive transactions are used to report against the Repetitive schedule and are entered against the item and site without regard to the underlying repetitive schedule that drives material and capacity requirements. Usually, you would focus on one style of production scheduling and reporting or the other and I'm a little concerned if you are generally using work orders and shop floor control but wanting to report downtime using the repetitive transactions (or visa versa). Both styles of production reporting (Shop Floor and Repetitive) have functions for reporting downtime ("Non-Productive Labor Feedback" for Shop Floor and "Down Time Transaction" for Repetitive) and you should generally use the one that matches the style of production reporting you do. Is that consistent with what you are doing?

Thank you very much,Evan.