Ansicht
Dokumentation

RMS_RCP_1111 - Recipe Settings

RFUMSV00 - Advance Return for Tax on Sales/Purchases   General Material Data  
This documentation is copyright by SAP AG.

In this IMG activity, you make many settings that affect recipes.

• You have specified the required recipe types in Customizing for the Environment, Health and Safety (EH&S) component in the IMG activity Specify Specification Types. Enter number range intervals here. You can also copy intervals from existing recipe types.

• You have specified the user status profiles you require for recipes in Customizing for Recipe Management in the IMG activity Set Up User Status Profile.

1. Specify the ratings with which the data for the general recipe can be transferred to a master recipe.

Example:

A general recipe was created with the rating PUBLIC (released without restriction). Its data can only be transferred to the master recipe if you have specified PUBLIC or * (all ratings) as the permitted rating in this IMG activity.

1. Define the views for recipes. For more information, see Define Views.
2. Specify the language-dependent descriptions for the views. For more information, see Specify Language-Specific View Names.
3. Specify the properties for the recipe types that you defined in EH&S Customizing (see Prerequisites). Under the properties, you define the following:

• Whether and how you use status management for recipes

• How formulas and production versions are linked to your recipes

• How you use change management in the recipe

• Whether you archive messages, and for how long

• Which process parameter profile is to be used as a basis (standard: DEFAULT)

Depending on which properties you want to define for your recipes, you must also process the following IMG activities:

• Set Up Link to Distributed Production Versions

• Maintain Profile (Customizing for Engineering Change Management)

• Set Up Name Assignment for Change States

1. Assign views to the recipe types and specify the order in which the system is to display the views in the recipe workbench. The view with the lowest number appears first. If you do not assign a view to a recipe type, no views are displayed for recipes of this recipe type in the recipe workbench.

Note:

With some recipe types, certain views are not required. The system does not display these views, even if you have assigned the views to the recipe type here. Examples:

• Master recipes only use the views BASIC, CLASS, DOCU1, HIERA, CHG, ADMIN, and CUST1 through CUST4.

• The CHG view is only displayed if the change state property has been assigned to the recipe type.

• The DOCU2 view is only displayed if you have defined the properties so that documents are used after release. The view is only displayed as of the status Released.

1. Specify the user statuses. You can specify different user status configurations for different recipe types, that is, you can restrict the user statuses to particular system statuses in the recipe status network, depending on the recipe type.

The following rules apply for the user status concept:

• Only one user status can be valid at a time.

• If a user sets a different system status, the system deletes the active user status.

• The user cannot go back in the user status sequence.

• In this IMG activity you can define a sequence of user statuses by using sequence numbers.

• In this IMG activity you can restrict various system status changes. To do this, you use status management processing (see Set Up User Status Profile).

• In this IMG activity, you can specify that the user cannot set the user statuses manually, whereas the workflow allows this.

By specifying an authorization key for a user status under Set Up User Status Profile, you can make sure that the user status can only be changed by users in a particular group. The system checks the user's authorization when the user status is set or deleted. The system checks the status profile, the object type, and the authorization key that affect the user status.

You use the authorization object B_USERSTAT to assign authorizations for this authorization key.

The user status pushbutton is not available on the Basic Data tab page for the recipe in the following cases:

• If only user statuses are assigned to the current system status of the recipe in this IMG activity for which the Workflow indicator is set

• If no user status is assigned to the current system status of the recipe in this IMG activity

If you choose the user status pushbutton in recipe editing, you change to status management processing in the following cases:

• If a user status profile is assigned to the recipe type but no entries have been made in this IMG activity

• If several user statuses are active for the current recipe

• If a user status is active for the current recipe but was not specified in Customizing for this recipe type

BAL Application Log Documentation   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 7346 Date: 20240523 Time: 193441     sap01-206 ( 85 ms )