4 Answers

• 00

  

  Martin Munzel 10/23/23, 6:43 PM

  Hello Uwe,
  The cost component structure in version maintenance is used to stratify the activity prices during plan price calculation. The settings in OKTZ only refer to the company codes in which the cost component structure is to be used for product costing.
  Greetings, Martin
  ----------------
  Martin Munzel
  SAP consultant, trainer, author http://www.martin-munzel.com

  report
• 00

  

  Schnipsi 10/23/23, 6:43 PM

  I dig out this thread...
  Do I have then at all the possibility to carry out the tariff stratification in 2 company codes in the plan version "0" on the basis of different cost component structures?
  Concrete example:
  *) we have X company codes in one controlling area on the system.
  *) all use only plan version "0" for budgeting of production cost centers / activity planning. For this, the cost component structure "01" is stored in the fiscal year customizing.
  *) Company code 1 now wants - as a "trendsetter" so to speak - to carry out the cost component split for material costing (standard price calculations, with quantity structure) with the new cost component structure "02" - in OKTZ this structure is stored for the company code.
  Result: the plan costs from the price are not "stratified", but displayed under the "unassigned" cost elements.
  If I change the cost component structure in version customizing to "02", it works. But this is not an option, because all other company codes still want to stratify according to the cost component structure "01".
  Can my wish here be realized at all with standard means? Or do we have to reach into the bag of tricks = modification in the CK11N / CK40N process?

  report
• 00

  

  Schnipsi 10/23/23, 6:43 PM

  Side note: for the trick box - SQL trace & debugger have already run hot:
  Function blocks K_UC_TKA07_READ & K_VERSN_READ would apparently have to be bored out to "bend" the ELEHK (from TKA07) at runtime. CK11N/CK40N would then do what I want them to do
  oh yes: our system:
  SAP ERP 6.0 Release 2005 SP33, EHP8
  SAP_FIN 618 SP16
  Additional info:
  Switch schema/transfer schema does not work, because no 1:1 assignment of cost components (components) between the two schemas is possible.
  

  Last edited on 29.07.21 14:32

  report
• 00

  

  Schnipsi 10/23/23, 6:43 PM

  Update (for all who have a similar issue).
  Last year, we finally implemented it as described above (modification of 2 FuBas).
  In the tariff calculation (KSPI) I have then checked on a user parameter, which element schema is stored - only so it was possible to catch the "right" schema, because I had in the KSPI at the necessary time no access to plant / company code to read out the settings of the OKTZ (table TKC07).
  Worked fine, does what I wanted.
  Soon the review will take place, where it will be decided, which cost component structure should be used in the future :-) one can be curious... :-)

  report