SGEN objects Generation Errors/Syntax Errors

[raheelqaiser]

SGEN issue (objects Generation Errors/Syntax Errors) after upgrade from SAP ECC6 EHP4 (NetWeaver 7.01, Kernel 7.22-PL 500) to EHP7 (NetWeaver 740, Kernel 753-PL 1400) through SUM. (100% complete)

When run SGEN (All components) after the successful completion of SUM upgrade process, 

SGEN report shows a No. of generation errors (1541) in SGEN report. After Re-run SGEN, the Number is reduced and lastly no generation error (Unexpected behavior) but syntax errors (45) remain the same. 

Detailed screenshots attached.

During SGEN run, Multiple dumps appeared in ST22

DB Table "GENSETM" > SE16

if we check any program mentioned in the above screenshot (GENSETM) through SE38 > SAPLSCPRVALLH

All SPAU/SPDD modifications are already adjusted.

Please share any solution to fix this issue!

Regards.

[Sandra_Rossi]

Why posting the question twice?

[qwertie]

Hello Raheel,

check in se11 for structure PTP02, it seems the ddic is not in synch with the db. Also in your screenshot is mentioned that VSCPRVALL is not active, so also check this object with se11 and try to activate.

best regards 

[raheelqaiser]

Thanks for the response rsnit. Actually there are lot of other inconsistency dumps in different objects, i shared a one for sample. And you know it is not the right way to activate every object specially for standard objects....

[qwertie]

Hello Raheel,

you can check versioning of these objects. Maybe you can get a hint why they are inconsistent. 

br

[raheelqaiser]

Hello rsnit, versioning of the objects couldn't help me to get the reason of Syntax errors! These syntax errors are also found in SAP_BASIS components which can't be ignore!

[qwertie]

Hello Raheel,

like mentioned it would be necessary to clarify why ddic is inconsistent with your db , see sap note 

2418500 - Dump "DDIC_TYPE_INCONSISTENCY " in MAIN_NEWBAS/XPRAS_AIMMRG phse of upgrade

1248769 - Inconsistency between database and ABAP Dictionary

You can verify an inconsistency using one of the following methods:

• - Call SE11 and in the menu, choose "Utilities -> Database Object -> Check".
• - Call SE14 and in the menu, choose "Check -> Database Object".
• - Call SE14 and in the menu, choose "Extras -> Database Object -> Check" (F6)

Please proceed as follows to eliminate the table inconsistency:

1. Check the prerequisites mentioned above: The table must exist in the database and the database object of the table itself (not only its indexes) must be displayed as inconsistent.
   The ABAP Dictionary performs database actions that fail because they are based on an incorrect assumption about the table in the database.
2. Log on as the user DDIC.
3. Call transaction SE14.
4. Enter the name of the table and choose "Edit".
5. In the menu, choose: "Table" -> "Reconstruct".
6. Confirm the execution as an emergency repair.
7. The system outputs a log of the reconstruction as a list. In the final summary, check if the reconstruction was successful.
8. Call transaction SE11.
9. Enter the name of the table and choose "Activate". 

br