Spec Types_decision

[former_member290536]

Hi All

During real time implementation as a usual practice,

1. On what basis or how we decide how many spec types we should group and how many recipe types we should group/create? Is there most common followed logic.

2.In real time do we define Spec type and receipe types starting Z*?

3. While creating spec is authorization group mandatory? What is the reason.

[christoph_bergemann]

Hello

we have a "SAP Standard delivery" for "Spec types". How you use them.. it is your decision; here you have lot of flexibility in set up and how you would like to use them.

You have two options: use the SAP standard ones or if you are not satisfied: use e.g. "Z*" ones; I would assume: in more than 80% or the cases you wil use SAP standard without "Z*". But it you can decide to use "Z*" (which is then much work for implementation etc.)

Regarding:

3. While creating spec is authorization group mandatory? What is the reason.

The "authorization group" is mandatory. This is by "design". Using the "Authorization group" you can steer/manage the authorizations of the user (display, write etc.).

For "recipe types": i can not help.

C.B.

E.G. check: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/ff6d35a34fbe4bea99e4ac41b0d5db03/4d936efaed6834b7e10...

or

https://help.sap.com/docs/SAP_S4HANA_CLOUD/f369b2eff700401494ba6e7c9a573288/726240f8596e4eaa9f7603f7...

May be https://blogs.sap.com/2016/08/14/sap-recipe-development-what-is-the-difference-between-sap-rm-and-sa...

could be of interest on top.