Skip to Content
avatar image
Former Member

SRM MDM, Error, "Table with Code 'null' does not exist in repository"

Hi experts,

We has SRM MDM scenario, while doing OCI settings, we are able to connect with MDM repository but getting follwoing error message in portal, "java.lang.IllegalArgumentException: Table with Code 'null' does not exist in the repository 'Repository' or is one of the system table (e.g. Workflows) that is not exposed in repository schema"

Can You please suggest,

Thanks and Regards,

Munish

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Oct 04, 2010 at 12:54 PM

    Hi,

    I think you have chose dwrong table while creating iviews.

    You have to chose Catalog Items table from tha available tables.

    Check at yr end and revert back with your findings.

    Thanks,

    Sudhanshu

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 04, 2010 at 08:02 PM

    Hi Munish,

    This kind of error generally comes when you have deleted a table/field from the repository and you are calling that table/field in MDM UI configuration. For example, you created a custom field in MDM repository and you are calling that field through OCI in OCI configuration. If you modified/deleted the field code/field, you will get this kind of error.

    To resolve this issue, download youu MDM configUI. Open it in XML editor and remove the unwanted field.

    Thanks,

    Anshuk Saxena

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Munish,

      Try to login to

      http:// : /webdynpro/dispatcher/ sap.com/tc mdmsrmcat~uisearch/MDM_SRM_UI_App

      with user ID Master.

      Master is a standard user provided by SAP which has UIConfiguration role assigned. Download your XML configuration and open in XML editor. It seems like you have a field with no code assigned and system is taking its value as NULL.

      Thanks,

      Anshuk Saxena