cancel
Showing results for 
Search instead for 
Did you mean: 

KKBC_HOE hierarchy reporting

former_member271158
Discoverer
0 Kudos

Hi All,

I am looking for some advice on report KKBC_HOE.

We are a food manufacturer and use production orders with order type ZM01. Alot of times they have an experimental production version (bom/routing) to test the production of a material before they have an actual production version to produce the material. So in essence a material can have several production versions for experiment which happen to begin with Exxx or regular production versions reflecting actual changes in the production process (ex. 1001, 2001 etc....). All the production versions are assigned to the same order type ZM01.

Example: Company 1111, Plant 2222, Order type ZM01, Material 12345, production version E001, 1001, 2001

We have configured a couple summarization hierarchies in transaction OKTO. One is ZPRODDET (Detail Production Variance Analysis) and the other is ZPRODEXP (Experimental Detailed variance Analysis). Problem is when we run KKBC_HOE for hierarchy type OR (order summarization) and hierarchy ZPRODEXP it reports all the variances experimental and regular. (ZPRODEXP and ZPRODDET).

Is there a way to tell hierarchy ZPRODEXP to only look production versions Exxx? Or is the only way to define a separate order type for experimental production? they want to see all the variances incurred from Experiment production separate from normal production.

Any suggestions would be greatly appreciated!

Thanks,

Sheila

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member271158
Discoverer
0 Kudos

Thanks Ajay - just wanted to confirm that I was not missing something.

ajaycwa1981
Active Contributor
0 Kudos

Hi Sheila

I guess in OKTO you dont have option to specify Prod version in your Summarization Hier definition.. Do you?

From a control perspective also, its advisable to have separate order type.. Thats also the ideally followed practice.. Coincidentally, it helps you in reporting as well

Had you been using Cost Object Hoerarchy, you can have separate Cost Obj code for each Prod Version and hence it becomes possible to display costs in the way you want

br, Ajay M