Creating Inheritance Relationships Between Specifications

Use

This procedure describes how you create inheritance relationships between specifications. To do this, you have the following options:

In the header data of a specification, you can create inheritance relationships in which the specification is the target or source specification. In other words, you specify in the specification header data the specifications from which the specification inherits data or to which the specification passes on data.
From the hit list , you can create inheritance relationships in which specifications that you have selected in the hit list are target specifications. In other words, you specify the specification (source specification) from which the selected specifications inherit data. You can create an inheritance relationship for one source specification in one step for as many selected specifications as you like.

In both cases, the specification from which you create the inheritance relationship is the requester. In other words, this specification requests the inheritance.

Prerequisites

See Inheritance .

Procedure

Creating Inheritance Relationships in Specification Header Data

Search for the specification that is the requester in the inheritance relationship you want to create. To do this, use one of the following procedures:
- Searching Manually for Specifications
- Executing Queries
- Loading Sets of Hits
  
  A set of specifications appears in the form of a hit list if the SAP system finds data records matching the search criteria of the manual search or query or if the set of hits loaded contains specifications that exist in the system.
Note
If the specifications you are searching for are not contained in the hit list or if the search result contains too many hits, you can fine-tune the hit list (see also Basic Functions in the Hit List ).

End of the note.
In the hit list, choose the specification that you want to edit by double-clicking it.

The Edit Specification: Header Data screen appears.
Choose the Relationships tab page.
On the tab page, select a blank row in one of the tables as follows:
- Select a blank row in the upper table if the current specification is to inherit data from another specification, in other words, if the current specification is the target specification in the inheritance relationship.
- Select a blank row in the lower table if the current specification is to pass data on to another specification, in other words, if the current specification is the source specification in the inheritance relationship.
Choose with the quick info text Create inheritance rel.
Enter the inheritance template and the source or target specification. When choosing the inheritance template, note that you can only assign inheritance templates to a target specification if their value assignment types and identifiers do not overlap. Value assignment types and identifiers only overlap if the usages specified in the inheritance templates overlap at the same time.

Creating Inheritance Relationships from the Hit List

Search for the specifications that are the requester and target specifications in the inheritance relationships you want to create. To do this, use one of the following procedures:
- Searching Manually for Specifications
- Executing Queries
- Loading Sets of Hits
  
  A set of specifications appears in the form of a hit list if the SAP system finds data records matching the search criteria of the manual search or query or if the set of hits loaded contains specifications that exist in the system.
Note
If the specifications you are searching for are not contained in the hit list or if the search result contains too many hits, you can fine-tune the hit list (see also Basic Functions in the Hit List ).

End of the note.
Select the required specifications and choose Specification Inheritance Inherit from Source.
Enter the inheritance template and the source specification. When choosing the inheritance template, note that you can only assign inheritance templates to a target specification if their value assignment types and identifiers do not overlap. Value assignment types and identifiers only overlap if the usages specified in the inheritance templates overlap at the same time.

Result

The inheritance relationship is assigned the approval status Requested ( ) and the status Initial ( ). If you have the authorizations described under Inheritance , the inheritance relationship is automatically assigned the approval status Approved ( ) and the status Ready to inherit ( ). If you do not have the authorizations, an authorized user must approve the inheritance request .

After an inheritance relationship has been assigned the status Ready to inherit , the background job transfers the data from the source specification to the target specification for the inheritance. The approval status remains Approved ( ) and the status changes to Consistent ( ) or, if there are errors, to Incorrect ( ).