Profitability and Cost Management

Get Involved. Join the Conversation.

Comments

  • Thejas Shetty

    Yes, there is direct integration between EPBCS & PCMCS. The file(s) generated in the intermediate step is system driven & you shouldn't worry about it, as the DM adapter knows what to do with those files.

    One doesn't need to know the location/structure/contents of the file.

  • Thejas Shetty

    It is unclear from your statement if you want to use REST API or want an alternative to using REST API to update dimensions.

    Please clarify.

  • Don Bean

    Deleted the comment you flagged for best answer - try again.

  • Evan Leffler

    A new idea perhaps wink

  • Matt Treml

    Thanks! Looks like I can't change best answer, sorry for the lost points. 

  • Don Bean

    Ofelia;  can you explain what the REST api 'Execute Update Dimension' won't allow you to do?

  • Evan Leffler

    Here is the response I gave over in the Idea Lab for reference:

    Matt, this functionality already exists. Just change your selection from the following

    <<Attribute Dim Name>> = <<Attribute Dim Member>>

    to instead read 

    <<Attribute Dim Name>> IN <<Attribute Dim Member Hierarchy>>

    this will select any member under that hierarchy

  • Don Bean

    Amit

    I don't see a way to do that in Web Reporting Studio.  I confirmed this with a colleague in Product Management.

    There is a new forum for the EPM platform where you can raise enhancement ideas that are for the common components in the platform.

  • Wayne Paffhausen

    Ofelia,

    To directly answer your question:  Yes.  I have many times loaded metadata to PCMCS via the RESTAPI.  I have done it via many different orchestrators and scripting technologies.


    Others have already provided the links to several key pieces of documentation on how to make that happen.  So I am not sure on where the gap still remains in the knowledge processes.  Please feel free to start another topic thread for other questions/concerns that you may have.

    Thank you,
    Wayne

  • Ofelia Ladao

    Has anyone successfully implemented the automation of the integration process of loading metadata to PCMCS using REST API ?  We are looking into using MuleSoft that will make the web service calls to PCMCS using REST API. 

  • Ankit kumar Shrivastava

     Updating dimensions in PCMCS can be achieved using the REST API. Based on how you want to automate the integration process -  FDMEE, Bat scripts, Groovy etc this can be accomplished using the endpoints available here:

    https://docs.oracle.com/en/cloud/saas/enterprise-performance-management-common/prest/pcmc_update_dimensions_as_a_job.html

    Thanks

    Ankit Shrivastava

  • Don Bean

    Have you looked through the online documentation in the PCMCS Help Center?

    https://docs.oracle.com/en/cloud/saas/profit-cost-cloud/books.html

    REST API for Enterprise Performance Management Cloud is at the bottom of the list. See Chapter 13 - update file based application topic.

     

  • Alecsandra Mlynarzek

    Hi there Parmit,

    One small correction to your above post. Any data movement in PCM will always have a record ID/ rule ID associated with it. The Offset of an amount, whether on Source intersections or otherwise, will always carry with itself the Rule ID reference. In other words, regardless of how you do the offset, source or alternate offset, it will always be populated against the Rule ID, never against the NoRule member. 

    I hope this helps.

    Kind regards,

    Alecs 

  • Parmit Choudhury

    Hi Don,

    As you mentioned that "If the offset setting in the rule is 'Source' then AllocationOut is posted to the source". In this case will AllocationOut member will be populated against the Source intersection of the allocation rule and the corresponding Rule ID member or NoRule Member. The data will show with a negative sign

    If the offset setting is 'Alternate Location' then the AllocationOffsetAmount is posted to the source- Here can we understand that AllocationOffsetAmount member will be populated against the Source intersection of the allocation rule and the corresponding Rule ID member or NoRule Member.The data will show with a negative sign

  • Don Bean

    AllocationOut and AllocationOffsetAmount both refer to the source intersections.  They allow the remainder amount to be reduced by amounts corresponding to the AllocationIn amounts sent to destinations.

    Only one of these members is used for porsting to a source intersection.   If the offset setting in the rule is 'Source' then AllocationOut is posted to the source and AllocationOffsetAmount is not used.  If the offset setting is 'Alternate Location' then the AllocationOffsetAmount is posted to the source and AllocationOut is posted to the alternate offset location.