Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Query problem : invalid argument when saving report

I am having trouble with a query that worked on the previous edition of the Business Objects but once I imported the report into BusinessObjects Enterprise XI Release 3, I get the following error when saving a command : Invalid Argument when saving report. Details: The alias requested 'Command', contains a combination of characters which is not considered to be valid.

Here is the offending query :

SELECT DISTINCT US.user_id,

US.first_name,

US.last_name,

US.dob,

ST.grade,

ST.enrollment_date,

US.gender,

SI.site_id,

SI.site_name,

SI.site_start_date,

SI.site_end_date,

ST.program_id,

ST.year,

ST.semester,

ST.application_status,

BT.cf_fund,

ST.rate_id,

RT.rate_name,

CS.date,

CS.requirements_met,

CS.date_fulfilled,

BW.aug_hrs,

BW.sep_hrs,

BW.oct_hrs,

BW.nov_hrs,

BW.dec_hrs,

BW.jan_hrs,

BW.feb_hrs,

BW.mar_hrs,

BW.apr_hrs,

BW.may_hrs,

BW.jun_hrs,

BW.jul_hrs,

BW.aug_cs_hrs,

BW.sep_cs_hrs,

BW.oct_cs_hrs,

BW.nov_cs_hrs,

BW.dec_cs_hrs,

BW.jan_cs_hrs,

BW.feb_cs_hrs,

BW.mar_cs_hrs,

BW.apr_cs_hrs,

BW.may_cs_hrs,

BW.jun_cs_hrs,

BW.jul_cs_hrs,

BW.aug_hrs_goal,

BW.sep_hrs_goal,

BW.oct_hrs_goal,

BW.nov_hrs_goal,

BW.dec_hrs_goal,

BW.jan_hrs_goal,

BW.feb_hrs_goal,

BW.mar_hrs_goal,

BW.apr_hrs_goal,

BW.may_hrs_goal,

BW.jun_hrs_goal,

BW.jul_hrs_goal

FROM users US

INNER JOIN students ST ON US.user_id = ST.user_id

INNER JOIN sites SI ON ST.bssp_site_id = SI.site_id AND ST.year = SI.year AND ST.semester = SI.semester

INNER JOIN rate RT ON ST.rate_id = RT.rate_id

INNER JOIN bssp_tuition BT ON ST.student_id = BT.student_id

LEFT JOIN cas CS on ST.student_id = CS.student_id

LEFT JOIN bssp_work BW on ST.student_id = BW.student_id

WHERE ST.program_id = 1 AND ST.application_status = 'active' AND ST.year = 2007

replied

I would copy the whole query as you have it and run it in your database's client tool. If it runs correctly, I'd check the drivers you're using to access the DB from CR; otherwise, it should throw some exception in your query.

If you DB client has no problems executing it - (which is definately a better place to debug it), CR should have no issues unless you're connecting to the DB in a manner different than the DB client....

Will

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question