Oracle Transactional Business Intelligence

Home› Oracle Analytics› Oracle Analytics Forums› More Solutions› Oracle Transactional Business Intelligence

Categories

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

Special characters not to be used for OTBI

Received Response
15
Views
4
Comments
Sunil Nukala2
Sunil Nukala2 Rank 1 - Community Starter
in Oracle Transactional Business Intelligence

Please suggest the special characters that are not to be used so that data will not be synced to view data in OTBI.

Answers

  • Nathan CCC
    Nathan CCC Rank 7 - Analytics Coach

    Hi Sunil, What do you mean synched? Please provide an example. Are you talking here about viewing data in either 1) a report in OTBI (yellow) from a data model with data source from one of the 3 application database FSCM/HCM/SCM or 2) an prompt/analysis in OTBI (blue) or a report in OTBI (yellow) from a data model with data source from subject area/analysis.

  • Sunil Nukala2
    Sunil Nukala2 Rank 1 - Community Starter

    H I am referring to the blue one OTBI for Finance

  • Gaurav Bharadwaj-Oracle
    Gaurav Bharadwaj-Oracle Rank 6 - Analytics Lead

    @Sunil Nukala2
    Please explain what you mean by synced, with an example.

    Regards,
    Gaurav

  • Riyaz Ali-Oracle
    Riyaz Ali-Oracle Rank 6 - Analytics Lead

    @Sunil Nukala2,

    Certain special characters can cause issues when syncing data in OTBI (Oracle Transactional Business Intelligence), leading to missing or improperly displayed values. Here are some characters that may disrupt data visibility:

    Characters to Avoid in OTBI Data Sync:

    Backslash () → Often ignored or misinterpreted in queries.

    Ampersand (&) → Can interfere with parameter passing.

    Single Quote (') → May cause SQL errors if not properly escaped.

    Double Quote (") → Can affect text parsing in reports.

    Percent (%) → Used as a wildcard in SQL, leading to unintended filtering.

    Underscore (_) → Functions as a single-character wildcard in some queries.

    Carriage Return / Line Breaks → Can cause formatting issues in reports.

    Special Unicode Characters → Some non-standard characters may not render correctly.

    Workaround:

    Use REPLACE functions in OTBI to strip unwanted characters.
    Ensure proper escaping when using special characters in queries.
    Validate data formatting before syncing to OTBI.

    If my response has answered your question or assisted you with your concern, please click"yes" below to accept the answer or comment with any additional queries.

    Thanks,
    Riyaz Ali