BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
buechler66
Barite | Level 11

Hi. Can I use a dataset Where condition during a Merge?  And if so, how can I change 'is not null' to reflect SAS missing values?

 

Any help would be greatly appreciated.

 

data QueryData;
  merge bids_ora.bi_spm_piece_recon (in=a)
        iv_ora.bi_spm_piece_recon (in=b) (where excl_sts_code is not null);
  by imb_code spm_calc_batch_date;
  if a and b;
run;
1 ACCEPTED SOLUTION

Accepted Solutions
LinusH
Tourmaline | Level 20

I guess you could, but I've never tried it with merge.

No need to to change NULL keyword, SAS treats that as MISSING if you are using SAS data.

But you are not using the correct ds option syntax, you need to write (where=(filter condition)).

Data never sleeps

View solution in original post

3 REPLIES 3
LinusH
Tourmaline | Level 20

I guess you could, but I've never tried it with merge.

No need to to change NULL keyword, SAS treats that as MISSING if you are using SAS data.

But you are not using the correct ds option syntax, you need to write (where=(filter condition)).

Data never sleeps
buechler66
Barite | Level 11
Thanks very much.
FreelanceReinh
Jade | Level 19

Hi @buechler66,

 

This is no problem. Just use the correct syntax as mentioned by @LinusH:

iv_ora.bi_spm_piece_recon (in=b where=(excl_sts_code is not null));

sas-innovate-2024.png

Available on demand!

Missed SAS Innovate Las Vegas? Watch all the action for free! View the keynotes, general sessions and 22 breakouts on demand.

 

Register now!

How to Concatenate Values

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.

Click image to register for webinarClick image to register for webinar

Classroom Training Available!

Select SAS Training centers are offering in-person courses. View upcoming courses for:

View all other training opportunities.

Discussion stats
  • 3 replies
  • 19655 views
  • 1 like
  • 3 in conversation