Mappings in a SAS Data Integration Studio job might be lost when the job is imported into your environment using a package (SPK) file. The issue occurs when importing the package file into an environment in which the metadata already exists and the package file contains the following:

• at least one deployed job
• the entire folder tree structure
• all dependent metadata objects for the jobs in the folder tree

When you promote a job from the package file and omit the job dependencies, column mappings can be missing in the job that is imported in SAS Data Integration Studio. There might be no indication of a problem with the job.  

A workaround is to create a package file with only the job object when possible. Promoting the metadata content from a package file containing only the job prevents the issue from occurring.  

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Management Console 9.4_M5 is available at:

A fix for this issue for Data Integration Studio 4.7_M5 is available at:

A fix for this issue for Data Integration Studio 4.903 is available at:

A fix for this issue for SAS Management Console 9.4_M4 is available at:

A fix for this issue for Data Integration Studio 4.902 is available at: