Copy ML POV Data

Copies model artifacts and data from a Source POV combination to a Destination POV combination for any application. Use with Management Ledger applications.

Required Roles

Service Administrator, Power User

REST Resource

POST /epm/rest/{api_version}/applications/{application}/povs/{srcPOVMemberGroup}/jobs/copyPOVJob/{destPOVMemberGroup}

Request

Supported Media Types: application/json

The following table summarizes the client request.

Table 15-11 Parameters

Name	Description	Type	Required	Default
`api_version`	Version of the API you are developing with	Path	Yes	None
`application`	Name of the application for which to deploy the cube	Path	Yes	None
`srcPOVMemberGroup`	Source POV member group, such as 2014_January_Actual	Path	Yes	None
`destPOVMemberGroup`	Destination POV member group, such as 2014_March_Actual	Path	Yes	None
`isManageRule`	Whether to copy the program rule details	Payload	Yes	None
`isInputData`	Whether to copy input data Note: Do not set the value of this parameter to true if the value of `isAllData` or `isAllInputData` is set to true.	Payload	Yes	None
`modelViewName`	Whether to copy a slice of data from source POV to destination POV	Payload	No	Nothing copied
`isAllInputData`	Whether to copy all input data at the NoRule member, including AdjustmentIn/Out	Form	No	False
`isAllData`	Whether to copy all POV data	Form	No	False
`createDestPOV`	Whether to create the destination POV if it does not already exist	Payload	Yes	None
`nonEmptyTupleEnabled`	Specifies whether to enable the Non Empty Tuple (NET). Valid values are true and false. In some cases, the default `nonEmptyTupleEnabled=true` does not perform well when copying the Essbase data. In those cases, use `nonEmptyTupleEnabled=false` to improve performance.	Payload	No	True
`stringDelimiter`	String delimiter for POV group members	Payload	Yes	None

Example URL and Payload

https://<SERVICE_NAME>-<TENANT_NAME>.<SERVICE_TYPE>.<dcX>.oraclecloud.com/epm/rest/v1/applications/LM1T2/povs/2014_January_Actual/jobs/copyPOVJob/2014_March_Actual

{"isManageRule":"true","isInputData":"true","modelViewName":"Operating Expenses","createDestPOV":"true","nonEmptyTupleEnabled":"true","stringDelimiter":"_"}

Response Body

Supported Media Types: application/json

Table 15-12 Parameters

Name	Description
`details`	Task ID, such as `LM1T2_LM1T2_CopyMLPOV_D20160113T065943_75b_1`
`status`	See Migration Status Codes
`statusMessage`	Message about the status, such as `In Progress`
`type`	Profitability
`links`	Detailed information about the link
`href`	Links to API call
`action`	The HTTP call type
`rel`	Relationship type
`data`	Parameters as key value pairs passed in the request

Example of Response Body

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

{
   "type":"Profitability",
   "status":-1,
   "statusMessage":"In Progress",
   "details":"BksML30_CopyMLPOV_D20220511T114800_7ad",
   "links":[
      {
         "href":"http:// <SERVICE_NAME>-<TENANT_NAME>.<SERVICE_TYPE>.<dcX>.oraclecloud.com/epm/rest/v1/applications/jobs/ChecktaskStatusJob/BksML30_CopyMLPOV_D20220511T114800_7ad",
         "action":"GET",
         "rel":"Job Status"
      }
   ]
}