sapnote_0000357185
2
02.11.2009 Page 1 of 2 SAP Note 357185 - Short dump SAPSQL_INVALID_FIELDNAME in GDBPS000 Note Language: English Version: 2 Validity: Valid Since 10.08.2001 Summary Symptom When version data is read, program termination SAPSQL_INVALID_FIELDNAME occurs in program GDBPS000. More Terms CN41, CN71, CNE5, CJV4, CJV5, DBIF_NTAB_FIELD_NOT_FOUND Cause and Prerequisites Version data in the Project System is stored in separate tables.These tables are described as VSxxxx_CN, however, xxxx represents the name of the original table. Example:the version data for WBS elements is stored, for example, in table VSPRPS_CN. The logical database PSJ of the Project System expects that all fields which are included in the operative tables are also contained (in the same order) in the version tables. APPENDs are often used in order to extend R/3 tables.In this case, the system may try to read the new fields (which do not exist) from the version tables. This leads to the above-mentioned program termination. Solution You must add the fields from the APPENDs to the version tables too! Header Data Release Status: Released for Customer Released on: 09.08.2001 22:00:00 Master Language: German Priority: Recommendations/additional info Category: Consulting Primary Component: PS-IS Information System Additional Components: PS-SIM Simulation PS-VER Versions Valid Releases Software Component Release From Release To Release and Subsequent SAP_APPL 40 40A 40B SAP_APPL 45 45A 45B SAP_APPL 46 46A 46B SAP_APPL 46C 46C 46C SAP_APPL 470 470 470 SAP_APPL 500 500 500
-
Upload
huzaifahunaid -
Category
Documents
-
view
272 -
download
11
Transcript of sapnote_0000357185
02.11.2009 Page 1 of 2
SAP Note 357185 - Short dump SAPSQL_INVALID_FIELDNAME inGDBPS000
Note Language: English Version: 2 Validity: Valid Since 10.08.2001
Summary
SymptomWhen version data is read, program termination SAPSQL_INVALID_FIELDNAMEoccurs in program GDBPS000.
More TermsCN41, CN71, CNE5, CJV4, CJV5, DBIF_NTAB_FIELD_NOT_FOUND
Cause and PrerequisitesVersion data in the Project System is stored in separate tables.Thesetables are described as VSxxxx_CN, however, xxxx represents the name of theoriginal table.Example:the version data for WBS elements is stored, for example, in tableVSPRPS_CN.The logical database PSJ of the Project System expects that all fieldswhich are included in the operative tables are also contained (in the sameorder) in the version tables.APPENDs are often used in order to extend R/3 tables.In this case, thesystem may try to read the new fields (which do not exist) from the versiontables. This leads to the above-mentioned program termination.
SolutionYou must add the fields from the APPENDs to the version tables too!
Header Data
Release Status: Released for CustomerReleased on: 09.08.2001 22:00:00Master Language: GermanPriority: Recommendations/additional infoCategory: Consulting
Primary Component: PS-IS Information SystemAdditional Components:
PS-SIM Simulation
PS-VER Versions
Valid Releases
Software Component Release FromRelease
ToRelease
andSubsequent
SAP_APPL 40 40A 40B
SAP_APPL 45 45A 45B
SAP_APPL 46 46A 46B
SAP_APPL 46C 46C 46C
SAP_APPL 470 470 470
SAP_APPL 500 500 500
02.11.2009 Page 2 of 2
SAP Note 357185 - Short dump SAPSQL_INVALID_FIELDNAME inGDBPS000
Software Component Release FromRelease
ToRelease
andSubsequent
SAP_APPL 600 600 600
Related Notes
Number Short Text
992048 Enhancement VSRESB_CN append /ISDFPS/VSRESB_CN -> ADVCODE
991734 SIM+VER: Runtime error SAPSQL_INVALID_FIELDNAME
973006 CJV4: Runtime error SAPSQL_INVALID_FIELDNAME
948987 PSIS: CN47N terminates when version data are to be selected
925643 Regulatory indicator in CO object master data tables
442233 Missing fields VAPLZ,WAWRK in vers table VSAUFK_CN
