Skip to Content
avatar image
Former Member

Planning area activation error


While planning area activation, I get the following error. I'm not able to tell if it is because of a key figure or attribute or master data type. There is no entity named CUSTNUM in the planning area, so I'm not sure what the error is referring to?

E - Exception raised from InternalError: dberror(PreparedStatement.execute): 2048 - column store error: fail to create scenario: [34011] Inconsistent calculation model;CalculationNode (3_87) -> operation (CustomLOp):Input table '3_86' has no column 'CUSTNUM' in the model at ptime/query/plan_executor/trex_wrapper/trex_wrapper_body/

Detailed log attached.

Please guide.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    Jun 04, 2015 at 11:22 AM

    Hi Suchita,

    That error looks like there is something wrong with a key figure that is using LCODE.

    If you have implemented some LCODE, check it, PRODNUM, LOCNUM, CUSTNUM are normally used in LCODES.

    By your log, I assume that your are activating a planning area that is a copy of SAP1, that planning area contains some keyfigures with LCODE, maybe the error comes from there.

    Kind Regards.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thanks! This helped!

      I'd made a copy of SAP2 and a pre-existing L-script was where the CUSTNUM appeared, like you mentioned. I was able to fix it and get the planning area active.

  • Jun 03, 2015 at 08:15 AM


    I cannot answer your question, but just give an idea on where to check:

    if you search in your document for CUSTNUM, you will find entries in lines 36, 48 and 53, and they all refer to the CUSTOMER, CUSTOMERPRODUCT and SOURCECUSTOMER.

    Check if you have those master data active and consistent.

    If you don't have that master data, but your planning area as a copy if one of the standard models, you may want to follow the chat

    It has at the first glance nothing to do with your topic, but it works on a question on other master data that cannot be seen such as SM1PRDNUM which you could see only in HANA tables.

    I may be completely wrong, but it does not harm to read the other question ...



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thanks for the direction Irmi!

      As you suggested, I did look through the connected master data types, and fixed some inconsistency there. That was part of the issue.

      However, the rela issue was with a pre-existing L-script where the CUSTNUM made an appearance.

  • avatar image
    Former Member
    Jun 03, 2015 at 09:11 AM

    Hello Shuchita

    I would recommend creating an OSS message for this issue. As it would require a deeper look into your configuration to find out the exact root cause.

    You can try following the suggestion from Irmi. If it doesn't help, then kindly create an OSS message.

    Parveen Kumar

    Add comment
    10|10000 characters needed characters exceeded