Skip to Content
avatar image
Former Member

Getting error while running Heuristic "Two different planning object IDs are used for the same keys"

Hello,

I have already checked existing discussion on the same topic and it was not helpful to me.

We are facing the error "Two different planning object IDs are used for the same keys" while running supply heuristic. We are using unified planning area and there is no custom key figure added. I have already checked the planning parameter for Heuristic is (INFINITE_WITHOUT_SHORTAGE) also checked required master data and transactional data is loaded to the planning area. But still getting this error.

Regards

Ankur

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    Aug 02, 2016 at 02:04 PM

    Hi Ankur,

    Please submit an OSS ticket. SAP needs to check the issue from backend.

    Best regards

    Rinju

    Add comment
    10|10000 characters needed characters exceeded

  • Aug 02, 2016 at 02:57 PM

    Hi Ankur,

    Could you please check if you have customized some Key Figures and marked it as "Input for Supply"?

    It was the same issue that I had faced previously while executing Supply and this was the Root Cause of the issue.

    Regards,

    Sourojit

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Sourojit

      As I mentioned in my post, we are using unified planning area and have not changed any KF or added custom KF 😊

      Regards

      Ankur

  • avatar image
    Former Member
    Sep 15, 2016 at 11:14 AM

    Hi Ankur,

    We are facing same issues in Unified planning area. Have not added any custom KF as input for supply planning.

    Is the issue resolved for you? Also if the issue got resolved, would you please share the steps to resolve this issue.

    Thanks,

    Samiksha

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Samiksha

      Yes, we raised OSS Message for this issue and SAP fixed it as a hot fix applied to our system as it was product bug.

      Please raise the oss message for the same.

      Regards

      Ankur