Scribd
Upload
7 views

BUILT IN Variable Feature Compatibility

Uploaded by

J Pablo Guadamuz Zuñiga
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
7 views

BUILT IN Variable Feature Compatibility

Uploaded by

J Pablo Guadamuz Zuñiga
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

1

MIGRATION FACTORY
TRAINING GUIDE

PowerCenter to CDI
BUILT-IN Variable Features Compatibility

Global Technical Alliance


2

Revision History
Version Number Version Date Added By Revision Description

1.0 6/6/2022 Swetha Kothamasu Initial Version


3

Table of Content:

1. BUILT-IN VARIABLES ............................................................................................................................. 4

2. CONFIGURE BUILT-IN VARIABLES IN IICS.......................................................................................... 6

Global Technical Alliance


4

1. BUILT IN Variables
The transformation language provides built-in variables. Built-in variables return either run-time or
system information. Run-time variables return information such as source and target table name,
folder name, session run mode, and workflow run instance name. System variables return
session start time, system date, and workflow start time.

You can use built-in variables in expressions in the Designer or Workflow Manager. For example,
you can use the system variable SYSDATE in a DATE_DIFF function. You can use run-time
variables in expressions and in input fields that accept mapping or workflow variables. For
example, you can use the run-time variable $PMWorkflowRunInstanceName as part of a target
output file name.

The PowerCenter Integration Service sets the values of built-in variables. You cannot define
values for built-in variables in a workflow or session parameter file.

You can use built-in variables in expressions. For example, you can use the system variable
SYSDATE in a DATE_DIFF function.

The following built-in variables provide run-time information:

• $PM<SourceName>@TableName, $PM<TargetName>@TableName

• $PMFolderName

• $PMIntegrationServiceName

• $PMMappingName

• $PMRepositoryServiceName

• $PMRepositoryUserName

• $PMSessionName

• $PMSessionRunMode

• $PMWorkflowName

• $PMWorkflowRunId

• $PMWorkflowRunInstanceName

The following built-in variables provide system information:

• $$$SessStartTime

• SESSSTARTTIME
5

• SYSDATE

• WORKFLOWSTARTTIME

Below table lists the Power center Variables and their equivalent feature compatibility in IICS.

PowerCenter Variables Cloud Data Integration

$PM<SourceName>@TableName, Not supported. Need to be hardcoded in the


$PM<TargetName>@TableName mapping/taskflow.

$PMFolderName Not Supported. Create In/Out Parameter


($$PMFolderName) in Mapping and pass the
value from Taskflow: util:getAssetLocation()

$PMIntegrationServiceName Not Supported. One option- Create In/Out


Parameter ($$PMIntegrationServiceName) in
Mapping and pass the value from Taskflow.
Value depends on customer requirement.

$PMMappingName '$CurrentMappingName' (with Quotes)

$PMRepositoryServiceName Not Supported. One option - Create In/Out


Parameter ($$PMRepositoryServiceName) in
Mapping and pass the value from
Taskflow: util:getOrganizationId() or any other
value.

$PMRepositoryUserName Not Supported. Create In/Out Parameter


($$PMRepositoryUserName) in Mapping and
pass the value from
Taskflow: util:getUserName()

$PMSessionName '$CurrentTaskName’ (with Quotes)

$PMSessionRunMode Not Supported. Can be Hard coded to ‘Normal’


as there is no recovery.

Global Technical Alliance


6

$PMWorkflowName Not Supported. Create In/Out Parameter


($$PMWorkflowName) in Mapping and pass
the value from Taskflow: util:getAssetName()

$PMWorkflowRunId Not Supported. One Option - '$CurrentRunId'


gives system generated run id for currently
running mapping task. Other option is to Create
In/Out Parameter ($$PMWorkflowRunId) in
Mapping and pass the value from
Taskflow: util:getProcessId()

$PMWorkflowRunInstanceName Not Supported. Create In/Out Parameter


($$PMWorkflowRunInstanceName) in Mapping
and pass the value from Taskflow. Value
depends on customer requirement.

$$$SessStartTime SESSSTARTTIME

SESSSTARTTIME SESSSTARTTIME

SYSDATE SYSDATE

At Taskflow, you can use: fn:current-date()

WORKFLOWSTARTTIME Not Supported. Create In/Out Parameter


($$WORKFLOWSTARTTIME) in Mapping and
pass the value from
Taskflow: util:getInstanceStartTime()

2. Configure Built-In Variables in IICS


In the Expression transformation click on Configure.
7

Choose System Variables and add the respective System variables to the Expression Panel.

Below are the System Variables available in the mapping level.

Global Technical Alliance


8

The rest of the variables need to be created as In-Out parameters at the mapping level and
the values can be passed from the Taskflow level.

You might also like