Scribd Logo
Upload

Welcome to Scribd!

  • 132 views

    Rest API

    Uploaded by

    Vishnu Vardhan
    The document outlines the steps to test retrieving reports via the REST API for an Hyperion Planning application: 1. Check the active API version by making a GET request and use version 1 for testing. 2. Make a POST request to the report endpoint, including the Content-Type and Authorization headers. 3. Provide the report details in the request body as a JSON object with the groupName, reportName, format, and module parameters to generate the specified report. 4. Send the request and check the response - a 200 status indicates successful report generation while a 400 response means invalid group name or lack of access to reports in that group.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Rest API

    Uploaded by

    Vishnu Vardhan
    132 views3 pages
    The document outlines the steps to test retrieving reports via the REST API for an Hyperion Planning application: 1. Check the active API version by making a GET request and use version 1 for testing. 2. Make a POST request to the report endpoint, including the Content-Type and Authorization headers. 3. Provide the report details in the request body as a JSON object with the groupName, reportName, format, and module parameters to generate the specified report. 4. Send the request and check the response - a 200 status indicates successful report generation while a 400 response means invalid group name or lack of access to reports in that group.

    Original Title

    Rest_API_.docx

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document outlines the steps to test retrieving reports via the REST API for an Hyperion Planning application: 1. Check the active API version by making a GET request and use version 1 for testing. 2. Make a POST request to the report endpoint, including the Content-Type and Authorization headers. 3. Provide the report details in the request body as a JSON object with the groupName, reportName, format, and module parameters to generate the specified report. 4. Send the request and check the response - a 200 status indicates successful report generation while a 400 response means invalid group name or lack of access to reports in that group.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    132 views3 pages

    Rest API

    Uploaded by

    Vishnu Vardhan
    The document outlines the steps to test retrieving reports via the REST API for an Hyperion Planning application: 1. Check the active API version by making a GET request and use version 1 for testing. 2. Make a POST request to the report endpoint, including the Content-Type and Authorization headers. 3. Provide the report details in the request body as a JSON object with the groupName, reportName, format, and module parameters to generate the specified report. 4. Send the request and check the response - a 200 status indicates successful report generation while a 400 response means invalid group name or lack of access to reports in that group.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 3

    Please find below the steps to test the REST Resource available to retrieve reports POST

    /HyperionPlanning/rest/fcmapi/{api_version}/report

    1. Pasted the below url in “Request URL” field with GET method to check for the active api
    versions in our application as shown in the below screenshot. V3 seems like the active
    one in the application but we use V1 to test the above API

    https://planning-test-ejlu.pbcs.us2.oraclecloud.com/HyperionPlanning/rest/

    2. Next, pasted the below URL in the “Request URL” field with POST method as shown in
    the screenshot
    The 2 headers used are :
    Header Name Header Value
    Content-Type application/json

    Authorization Basic
    ZWpsdS5yYW1pbGluZW5pQGRlbG9pdHRlLmNvbTpSdWtpQDY2Ng==

    https://planning-test-
    ejlu.pbcs.us2.oraclecloud.com/HyperionPlanning/rest/fcmapi/v1/report

    3. Navigated to Body section , selected Body content type as “application/json” and Editor
    View as Raw Input.
    a. Pasted the below JSON object if we want to obtain the Late Tasks report in the
    Task Manager group which is working as expected.
    {
    "groupName": "Task Manager",
    "reportName": "Late Tasks",
    "format": "XLS",
    "module": "FCCS"
    }
    b. Pasted the below JSON Object to obtain the Balance Sheet Consolidated
    Financial Report as shown in the below screenshot
    {
    "groupName": "Financial",
    "reportName": "Balance Sheet Consolidated",
    "format": "XLS",
    "module": "FCCS"
    }

    4. Clicked on SEND to send the request to the server.


    a. If the JSON Object in step 4.a is used ,we get a 200 SUCCESS response from the
    server and the Late Tasks Report is generated in the inbox/outbox folder of the
    FCCS Application in the format mentioned in the JSON object .
    b. If the JSON Object in step 4.b is used, we get a 400 Bad Request response from
    the server with the error mentioned as “Either the group name is invalid or you
    don't have access to any reports with in the group.” as seen in the below
    screenshot

    You might also like