Item Costing SetupIf the Standard Cost per Enterprise Unit check box in the Implemented Software Components (tccom0100s000) session is selected, the master data is automatically generation for the Item - Costing (ticpr0107m000) session, rather than by the item costing defaults you defined. The generation of the item costing data is triggered by the setup of the logistic flow of an item rather than by the item costing defaults you defined. Note The setup of the logistic flow of an item serves as a base. Automatic generation of costing data cannot be derived unambiguously in all scenarios. For example, item data by warehouse is essential for item costing data generation, but is not always created for an item. Or, an item may have insufficient data available to derive the costing source, in the case of item by warehouse not having a supply method defined, and the warehouse not being the ordering warehouse. Because the generation of item costing data is based on the setup of the logistic flow of an item, the existing item costing defaults for a particular enterprise unit do not automatically translate into actual item costing data for that enterprise unit. By defining how a product is produced, where an item is produces, between which locations it is transferred and how the product is sold the costing data is adapted to the situation. Costing data is adapted by: Note
Sites functionality not active Note If the Sites field in the Implemented Software Components (tccom0100s000) is set to either Inactive or Enterprise Model in Preparation, generation of costing data cannot be triggered by defining item sales data. The generation of item costing is triggered by:
Note All data is present only at company level. If the Sites field in the Implemented Software Components (tccom0100s000) is set to In Preparation, all processes use item data defined on Company level and item data by warehouse. If you have already defined item data by site, it is not yet in use. If you create new item data, item costing should be based on new item by site and item by office data present. The same triggers apply as when the sites functionality is active.
| |||