Has anyone encountered an error like this before? I find it rather cryptic. Any possible solutions would be appeciated.
157 + proc sql;
157 + create table QueryData54 as ( select DISTINCT 'INVLD CTR LVL ENT FACILITY EXCL INDICATOR
MISMATCH' as RULE_NM length = 58, b.actual_dlvry_date as AD_DT, b.imb_code length = 31, 54
as RULE_ORDER,
158 + b.spm_calc_batch_date from iv_ora.bi_spm_piece_recon a, bids_ora.bi_spm_piece_recon b
where a.spm_calc_batch_date = b.spm_calc_batch_date and a.imb_code = b.imb_code and COALESCE
NOTE: Line generated by the CALL EXECUTE routine.
159 +(A.ICOALESCED_CTR_LVL_ENT_FAC_EXCL_IND ,'T') <> COALESCE(B.ICOALESCED_CTR_LVL_ENT_FAC_EXCL_IND ,'T') );
----------------------------------- -----------------------------------
65 65
NOTE: The "<>" operator is interpreted as "not equals".
ERROR 65-58: Name 'ICOALESCED_CTR_LVL_ENT_FAC_EXCL_IND' is too long for a SAS name in this context.
NOTE: PROC SQL set option NOEXEC and will continue to check the syntax of statements.
NOTE: The SAS System stopped processing this step because of errors.
NOTE: PROCEDURE SQL used (Total process time):
real time 0.01 seconds
cpu time 0.00 seconds
ERROR: File WORK.QUERYDATA54.DATA does not exist.
NOTE: Statements not processed because of errors noted above.
Hello,
It is not weird at all - The length of ICOALESCED_CTR_LVL_ENT_FAC_EXCL_IND is greater than 32 which is the maximum length accepted by sas
Hello,
It is not weird at all - The length of ICOALESCED_CTR_LVL_ENT_FAC_EXCL_IND is greater than 32 which is the maximum length accepted by sas
But what is the solution of it
Build your skills. Make connections. Enjoy creative freedom. Maybe change the world. Registration is now open through August 30th. Visit the SAS Hackathon homepage.
Register today!Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.
Select SAS Training centers are offering in-person courses. View upcoming courses for: