Export Data Mapping

Member mappings are used to derive the target members for each dimension based on source value. Member mappings are referenced during the data load, enabling Data Management to determine how to dimensionalize the data that is loaded to the target application. Member mappings define relationships between source members and target dimension members within a single dimension. You must create a member mapping for each target dimension.

You can export member mappings to a selected file of format .csv, .txt, .xls, or .xlsx.

REST Resource

POST /aif/rest/{api_version}/jobs

Request

Supported Media Types: application/json

The following table summarizes the client request.

Table 10-11 Parameters

Name Description Type Required Default
api_version Version of the API you are working with, such as V1 Path Yes None
jobType The job type, MAPPINGEXPORT Path Yes None
jobName

The dimension name for a specific dimension to import, such as ACCOUNT, or ALL to import all dimensions

Path Yes None
fileName The file and path from which to export mappings. The file format can be .CSV, .TXT, .XLS, or .XLSX. Include the outbox in the file path, for example, outbox/BESSAPPJan-06.csv Path Yes None
locationName The name of the location, such as BESSAPP Path Yes None

Example of Request Body

The following shows an example of the request body in JSON format.

{
"jobType":"MAPPINGEXPORT",
"jobName":"ACCOUNT",
"fileName":"outbox/BESSAPPJan-06.csv",
"locationName":"BESSAPP"
}

For sample code, see the code samples included in Running Data Rules.

Response

The following table summarizes the response parameters.

Table 10-12 Parameters

Name Description

jobId

The process ID generated in Data Management for the job, such as 1881

jobStatus

The job status, such as SUCCESS

logFileName

Log file containing entries for this execution, such as outbox/logs/BESSAPP-DB_1881.log

outputFileName

Name of the output file generated, such asoutbox/BESSAPPJan-06.csv

processType

The type of process executed, EXPORT_MAPPING

executedBy

Login name of the user used to execute the rule, such as admin

details

Returns the exception stack trace in case of an application error, or else null

Supported Media Types: application/json

Example of Response Body

The following shows an example of the response body in JSON format.

{
"links": 
[
0]
"status":"0",
"details":"null",
"jobId":"1881",
"jobStatus":"SUCCESS",
"logFileName":"outbox/logs/BESSAPP-DB_1881.log",
"outputFileName":"outbox/BESSAPPJan-06.csv",
"processType":"EXPORT_MAPPING",
"executedBy":"admin"
}

For sample code, see the code samples included in Running Data Rules.