Oracle Fusion Data Intelligence Idea Lab

Home› Oracle Analytics› Oracle Analytics Idea Labs› Oracle Fusion Data Intelligence Idea Lab

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

API to reset the last extract date in BICC PVOs

Needs Votes
500
Views
10
Comments
Sumit Sohan-Oracle
Sumit Sohan-Oracle Rank 1 - Community Starter
edited September 26 in Oracle Fusion Data Intelligence Idea Lab

API to reset the last extract date in BICC PVOs.

Use Case and Business Need (Required): We have created data sync integration from SaaS to PaaS for BICC PVOs. But sometimes we need to sync the full extract in case the integration errors out due to any reason. So we need an API through which we can reset the last extract date in BICC PVOs.

Tagged:
20
Up
20 votes

Needs Votes · Last Updated

Comments

  • Sahithi Kolasani-Oracle
    Sahithi Kolasani-Oracle Rank 5 - Community Champion

    Agreed. We are manually resetting the last extract date from fusion BIACM whenever we need to do a full load.

  • Kyle M.
    Kyle M. Rank 1 - Community Starter

    If any error occurs in PVOs extract while fetching the data other than configuration issue then how it will be resolved? Can it only be resolved manually?

  • Dave Kekish
    Dave Kekish Rank 5 - Community Champion

    This is long needed. The BICC interface is fine, however it is not the ideal way to deal with things imo.

  • CPavan
    CPavan Rank 1 - Community Starter

    Hi,

    Do we have any solution for this?

    Thanks & Regards,

    Pavan

  • Dave Kekish
    Dave Kekish Rank 5 - Community Champion

    I haven't seen or heard anything on this idea.

  • Harishma
    Harishma Rank 3 - Community Apprentice

    Hi team, Is there an update on this request? We were attempting to update the lastExtractDate of data stores in the BICC job using the Create or Update Job API documented here ( https://docs.oracle.com/en/cloud/saas/applications-common/24c/biacc/manage-meta-data-rest-api1-vo-attributes-for-sdm-vo-and-non-sdm.html#u00180700 ). However, when doing this, we received a "Success_with_warning" response with the message "Last Extract date provided was ignored for updating job".

    Assuming this request was raised for the same use case, I wanted to follow up and check for any updates. Thank you.

  • Dave Kekish
    Dave Kekish Rank 5 - Community Champion

    I got a notice that the voting on this idea is open, considering it was open, I'm not sure what that means, but I'm hopeful once more.

  • Joshua Snitzer
    Joshua Snitzer Rank 1 - Community Starter

    Would be very useful for automating certain business processes on our team: ensuring accurate and up-to-date data for our in-house processes that use data from BICC.

  • Joshua Snitzer
    Joshua Snitzer Rank 1 - Community Starter

  • Sumit Sohan-Oracle
    Sumit Sohan-Oracle Rank 1 - Community Starter

    Hi Team, there is a workaround for this issue,

    If suppose there are 3 PVO's (PVO1, PVO2 and PVO3) in a job and we want to update the last extract date as null for PVO3, then we have to call the BICC REST API (BIACM REST API) with PUT operation by passing the payload for only two PVO's (PVO1 and PVO2 in our case) and then again calling the REST API (BIACM REST API) with PUT operation by passing the payload for all three PVO's (PVO1, PVO2 and PVO3).

    In this way the last extract date of 3rd PVO (PVO3) will be set as null.

    This means we are first removing the 3rd PVO from the job and then re-adding that. Hope this helps.