Recipe Development missing in the symbol tree

[Former Member]

Hi Experts,

I could not find the Recipe Development under the symbol tree in transaction CG42 , as shown in the screenshot below.

Can anyone help me out with this?

Thanks & best regards,

Yogesh

[Former Member · Accepted solution]

Hello Yogesh,

Standard SAP delivery include Recipe Management/Recipe Development Property tree such as

RM_Specifi, RM_Nutrient, CCK_RM, RM_Diet and so on. You have option to choose Change Symbol Tree in CG42 and select the tree. Standard Property tree is mainly used for regulatory purpose where other property tree are more like used for different purposes.

For some reason if you do not have drop down for Recipe Property tree than consider them importing from 000 Client.

Hope this helps.

Gopi Dadheech

[Ralph_P]

Hi Yogesh,

which tree is chosen in CG42? Does this tree include the Recipe Development properties (check in CG02 or customizing)?. If not, maintain them or in CG42 switch to a tree that includes these properties.

Ralph

[Former Member]

Hi Ralph,

Thank you for the quick reply.

The symbol tree chosen is "STANDARD". This tree is supposed to include Recipe Development.

I checked in all the other trees and i could'nt find Recipe development.

Is there any place that i need to check in SPRO(Logistics)

Thanks,

Yogesh

[Ralph_P]

Hi Yogesh,

That simply means that your standard tree does not include the properties for Recipe Development. For including these properties in all trees where you need them, g into SPRO-->EH&S-->Basic Data & Tools-->Specification Management-->Specification Database Structure-->Settings for Value Assignment-->Set up Property Trees.

There you can define which properties should be included in which property tree. Once done, you will find the RD properties in the trees where you included them both in CG02 and CG42.

One important note, though: Never ever change the standard property tree! As soon as you bring in a service pack, your changes will be overwritten and your standard tree is a mess. Better to copy the standard tree, call the new one standard tree Yogesh (or whatever you want to call it) and do your changes in this new tree.

Ralph

[christoph_bergemann]

Dear Yogesh

data base set up for EHS classic and Recipe (classes etc.) is refereced a little bit here:

Check subchapter "

Standard Data base Structure"

C.B.

PS: Please check marketplace. There is one important OSS consulting not available to discuss "STANDARD" tree (and options how to handle that). This is a quite "new" one (may be 1 or 2 years old). It is a "must to read" OSS note.