Forum Stats

  • 3,853,765 Users
  • 2,264,266 Discussions
  • 7,905,444 Comments

Discussions

EBS to Hyperion Planning Metadata Rule Failed

user12143649
user12143649 Member Posts: 24 Red Ribbon
edited Oct 14, 2019 8:48AM in Financial Data Management

Hi Gurus,

We are doing the integration to push the EBS Account hierarchy to Hyperion Planning.

It's failing during EPMA import steps.

pastedImage_0.png

Process Log:-

2019-10-02 10:45:38,807 DEBUG [AIF]: Load Dimension:693_Account

2019-10-02 10:45:38,871 DEBUG [AIF]: Count of all dimension: 20

2019-10-02 10:45:38,871 DEBUG [AIF]: Count of load dimensions:{1}

2019-10-02 10:45:38,901 ERROR [AIF]: error encountered

2019-10-02 10:45:38,901 ERROR [AIF]: Error encountered

2019-10-02 10:45:38,904 INFO  [AIF]: [exportMetadataToEPMA: 693 ] End ( java.lang.Exception: javax.xml.rpc.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.NullReferenceException: Object reference not set to an instance of an object.

ERP Integrator Log:-

[2019-10-02T09:25:42.310+03:00] [ErpIntegrator0] [NOTIFICATION] com.hyperion.aif.servlet.ODIServlet] [SRC_METHOD: doPost] response msg:java.lang.Exception: javax.xml.rpc.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.NullReferenceException: Object reference not set to an instance of an object.[[

Please advise if anyone has any clue on this issue to debug.

Best Answer

  • user12143649
    user12143649 Member Posts: 24 Red Ribbon
    edited Oct 14, 2019 8:48AM Answer ✓

    This issue is resolved after we use fdmee schema as the  data source for epma interface table.

    Still don't know why it didn't work with dedicated schema created for EPMA interface table, May be some bug.

Answers

  • user12143649
    user12143649 Member Posts: 24 Red Ribbon
    edited Oct 14, 2019 8:48AM Answer ✓

    This issue is resolved after we use fdmee schema as the  data source for epma interface table.

    Still don't know why it didn't work with dedicated schema created for EPMA interface table, May be some bug.