Message no. P0 568

Diagnosis

Cause 1:
The structure of the feature is not saved in the feature directory.

Cause 2:
The feature structure is not defined in the program that reads the feature.

Cause 3:

The feature that the program expects does not match the actual feature structure.
Procedure

Cause 1:
Please advise your system administrator that all features must be regenerated. 
Please note that this generation must take place in client 000 first, and then in all other clients (report RPUMKG00 or the Generation function in the feature maintenance transaction (transaction PE03)).

Cause 2:
The feature structure must always be defined in the program reading the feature (see documentation for program RPUMKC00).

Cause 3:
Please contact your system administrator
Generate features
Description
You can use this report to regenerate features and create new cross-references (set up predecessors).

Generating features:
You can use the following types of generation, which you specify in the Type of generation field:
Always generate the feature:
Choose this type when implementing an upgrade. Enter value 1 to set up the cross-reference (predecessor) and regenerate all features. Do not make any entries in the Features field. If you enter the value 2 in this field, only the features specified in the 
Features field are regenerated. 

Generate feature only if it has changed:
You can use this option, for example, if you have changed the structure or the field names for several features. Enter 3 in the Type of generation field.

Generate all features that have not been selected:
Use this option when transporting features. In the target system, the features that have already been transported are flagged. Transported features that have not been flagged are then imported. This report is started automatically after the import - it selects and generates all unselected features.

Generation is always based on the main features. If the list also contains subfeatures, the report determines the main features related to these and uses them in generating.

The report lists all main features together with a status message, and displays statistics on the features generated. 
What exactly happens during a generation run?

Reports with the name /1PAPA/FEATcccfffff are created when features are generated - ccc refers to the client and . fffff refers to the feature name. If a report already exists, the old report is overwritten. 

Setting up predecessors:
You can call up the subfeatures of a feature. When you save the feature, the system automatically enters the feature with this subfeature as the predecessor. You can set up a predecessor and create a cross-reference only in a generating run. You can execute a generating run by entering 2 in the Type of generation field. The predecessor must be set up after every update or release upgrade.

Dependencies
All selected features are used for the generation. The last update versions of the features are used.
When setting up new predecessors, do not delimit the feature range by specifying features.
 

Best regards,
SAP Basis, ABAP Programming and Other IMG Stuff
http://www.sap-img.com