topic Re: DI Studio, about physical work table names and Lookup transformation macros in SAS Data Management

DI Studio, about physical work table names and Lookup transformation macros

EinarRoed — Mon, 19 Nov 2012 07:31:07 GMT

Working in DI Studio I have a Lookup transformation that receives input from two Extract work tables. The precode of the Lookup transformation refers directly to the first input work table by means of its physical name, WORK.W66T81JT.

1) Can this create a problem when importing the job to another environment? I seem to recall that physical names of work tables may change under such circumstances, but even if that's the case, perhaps the reference automatically changes to match it.

2) Since &syslast or &input_1 can't be used to refer to the first input of a Lookup transformation, is there a different way that enables me to avoid using the physical table name?

Thanks.

Re: DI Studio, about physical work table names and Lookup transformation macros

LinusH — Mon, 19 Nov 2012 08:45:07 GMT

1) Correct. Whenever possible, avoid refer to physical table names. Use DIS macro variables instead.

2) What is the nature of this pre-code? Maybe it can be solved in a different way? One way is to assign your own macro variable from syslast in the post-code in your extracts.

Re: DI Studio, about physical work table names and Lookup transformation macros

EinarRoed — Mon, 19 Nov 2012 09:33:17 GMT

Thanks, you're absolutely right, it could be handled in the postcode.

Do you know if the Splitter transformation may be problematic? Can't see a way to prevent it from referencing physical table names.

Re: DI Studio, about physical work table names and Lookup transformation macros

LinusH — Mon, 19 Nov 2012 09:42:52 GMT

Since 4.2, I haven't use splitter. If you are in 9.2 or later, see if you can omit it.

But what is the scenario here about pre/post-code? The pre-code to splitter could use sylast.

The transformations that read each splitter output should as well be able to use syslast in their pre-code.