SAS Data Integration Studio, DataFlux Data Management Studio, SAS/ACCESS, SAS Data Loader for Hadoop and others

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

Accepted Solution Solved
Reply
Frequent Contributor
Posts: 90
Accepted Solution

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

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.


Accepted Solutions
Solution
‎11-19-2012 03:45 AM
Super User
Posts: 5,438

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

Posted in reply to EinarRoed

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.

Data never sleeps

View solution in original post


All Replies
Solution
‎11-19-2012 03:45 AM
Super User
Posts: 5,438

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

Posted in reply to EinarRoed

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.

Data never sleeps
Frequent Contributor
Posts: 90

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

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

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

Skjermbilde.PNG

Super User
Posts: 5,438

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

Posted in reply to EinarRoed

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.

Data never sleeps
🔒 This topic is solved and locked.

Need further help from the community? Please ask a new question.

Discussion stats
  • 3 replies
  • 318 views
  • 3 likes
  • 2 in conversation