In APO, reduction data is coming from ECC, so if reduction happens in ECC based on ECC settings, reduction will be CIFed and saved in APO (though there's still some setting, e.g. order category, controlls this.) However the root should be in ECC.
Not only SO consumes forecast, based on category group settings, any requirement may consume forecast. What is the corresponding order category in APO?
↧
Re: Forecast consumption by Movement Type 311
↧