SAP ABAP Data Element PVS_CHANGES_ALLOWED (Permissibility of Change Master Record Usage)
Hierarchy
☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ PLM-RM (Application Component) Recipe Management
     ⤷ CPPERCP (Package) RMS-RCP: iPPE Objects for Appl. Type RCP (Recipe, Header)
Basic Data
Data Element PVS_CHANGES_ALLOWED
Short Description Permissibility of Change Master Record Usage  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type PVS_RECIPE_MAINTAINANCE    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Change No. 
Medium 18 Change Master Rec. 
Long 30 Change Number Usage 
Heading 18 Change No. Usage 
Documentation

Definition

You use this key to specify whether a change master record is prohibited, optional, or mandatory for processing recipes.

Use

Change master records are identified by a change number. You can use the processing type to control change management in the recipe as follows:

  • Recipe processing without a change number:

    Using this processing type, you can create exactly one change status for each recipe. When you change a recipe, you use a key date to select a change status and edit it without changing its validity period.

  • Recipe processing with a change number:

    Using this processing type, you create a separate change status for each change number. You use the same change number to edit the statuses of different objects (for example, recipe and formula) that belong together. You specify the date of the validity period globally in the change master record. You can later change this date.

  • Recipe processing with or without a change number:

    The first change status can have a change number, but this is not mandatory. All subsequent change statuses must have change numbers.

    Note:
    Recipe management only supports change master records with date validity but not with parameter effectivity.

Irrespective of whether you process your recipes with or without a change number, changes are logged using change documents.

Dependencies

If you have assigned scopes of application to the change statuses of your recipes, the validity periods defined there apply.

Example

History
Last changed by/on SAP  20031212 
SAP Release Created in