SAP ABAP Data Element ESE_ICON_APPRV_STAT (Approval Status of Relationship)
Hierarchy
☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ EHS-SAF (Application Component) Product Safety
     ⤷ CBUI (Package) Company Environment Information System
Basic Data
Data Element ESE_ICON_APPRV_STAT
Short Description Approval Status of Relationship  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type SYCHAR132    
Data Type CHAR   Character String 
Length 132    
Decimal Places 0    
Output Length 132    
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 Approval 
Medium 15 Approval 
Long 20 Approval status 
Heading 6 Apprvl 
Documentation

Definition

Specifies the approval status.

The approval status occurs only in the following combinations with the status of the inheritance relationship:

Inheritance Status         Approval Status   

Initial     |@BZ@    Requested     |@9Y@

Ready to inherit     |@5D@    Approved     |@01@

Consistent     |@5B@    Approved     |@01@

Incorrect     |@5C@    Approved     |@01@

Initial     |@BZ@    Rejected     |@02@

Only when an inheritance status is approved can the status of the inheritance relationship switch from Initial to Ready to inherit. If source data is changed in an inheritance relationship that is already consistent, the status also changes from Consistent to Ready to inherit.

After the status has changed to Ready to inherit the data is updated by the background job for the inheritance. The approval status remains as Approved and the inheritance status switches to Consistent (or switches to Incorrect if errors occur). See also IMG activity Set Up Job for Inheritance.

Note:

On the Relationships tab page in the header data you can

  • use the Addit. info. pushbutton to check whether the job is running for the background job for data inheritance
  • use the Restart inheritance pushbutton to manually restart the inheritance

Dependencies

The combinations depend on which authorization the user who created the inheritance relationship has.

Other Information

In inheritance, the SAP System records whether the inheritance request was created by the source specification or the target specification, so that the source specification or the target specification can have the task of being the requester or the acceptor. Only employees with the relevant authorization can request or approve inheritances.

  • To request inheritance, you require change authorization for the requester specification with regard to the data in the inheritance template, independent of whether you are requesting inheritance for a target specification or for a source specification.

  • To be able to approve an inheritance request in the acceptor specification, you require the following authorizations for the acceptor:
    • Change authorization to be able to approve the inheritance request from the source specification in the target specification (the acceptor). The data read from the source specification must be able to be created in the target specification.
    • Display authorization to be able to approve the inheritance request from target specification in the source specification (the acceptor). The data to be created in the target specification must be able to be read in the source specification.

      Note:

      You specify the change or display authorization in the authorization objects C_SHES_TVH (specification value assignment with specification reference) and C_SHES_TRH (specification header).

If you have the required authorization for the acceptor specification, the approval status is automatically set to the status Approved. If you do not have the required authorization, the approval status remains in the status Requested until an authorized user approves the request manually.

The entity responsible for the specification is informed when an inheritance relationship is requested, approved, or rejected. The responsible entity is determined by means of the usage of the inheritance template from the specification status. If no suitable status entry is available, the responsible entity specified as the default in the IMG activity Specify Authorization Groups is informed.


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