Oracle Fusion Data Intelligence

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Fusion Data Intelligence› Oracle Fusion Data Intelligence

Categories

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

Semantic Model Status "Skipped" on Oracle EPM Data Augmentation

Received Response
24
Views
2
Comments
esabsse
esabsse Rank 1 - Community Starter
in Oracle Fusion Data Intelligence

I preface this with I know relatively little about this process because my background is on the EPM side of the house. I'm just looking for a little guidance on any trouble shooting steps I can employ. The issue I'm having is that after I execute my data augmentation job, the semantic model shows as "skipped" as seen here:

image.png

I've followed all the documented steps here :

https://docs.oracle.com/en/cloud/saas/analytics/25r3/fawag/load-data-from-epm-export-data-instance-into-fusion-data-intelligence-preview.html

This included:

  1. Enabled "preview" features
  2. Successfully created an epm data exchange job and ran it to produce the data file
  3. Created a data connection to the EPM Export Data instance (refresh metadata toggle is on) and tested the connection successfully
  4. Created a data augmentation job, chose file, I see my columns and chose my primary key columns
  5. We run the augmentation and get the "semantic model skipped" issue noted above

Any tips would be greatly appreciated. Thanks

Tagged:

Answers

  • Rob Toogood
    Rob Toogood Rank 4 - Community Specialist

    Hi @esabsse

    Usually when the Semantic Model step says skipped - it means that the file has not been applied to the semantic model extensions because of an issue - usually it will be something like incompatible joins.

    First, I would check that your semantic model customisation is referencing the correct table name in the correct schema (I assume it will be DW_PBCS_X_EPM in the OAX_USER schema)

    Second, once you have verified it is the correct table, check the joins. Some common issues will be around the data type - e.g. Joining and Integer data type to a VARCHAR data type - the model will not like that. If it is a data type mismatch, this can be handled in the 3rd screen of the create data augmentation.

    Hopefully the above is useful.

  • esabsse
    esabsse Rank 1 - Community Starter
    https://community.oracle.com/products/oracleanalytics/discussion/comment/71876#Comment_71876

    Great feedback Rob, we'll test your suggestions.

    Thanks