Skip to Content
avatar image
Former Member

Error: Output table '3_101' has no column 'W1SPCODENUM' in the signature of the main function


I have created PRODUCT master attribute Special Code. It is configured as a key / required along with PRDID i.e. the combination of PRDID + Special Code denotes my marketing product as I have the following situation:

PRDID  |   Special Code

100001  |   SC1

100001  |   SC2 a distinct product in my master data is a combination of PRDID & Special Code.

Steps followed:

  1. Copy SAP 2 , create a new planning area WTECH
  2. Add new attribute WSPCODE to WPRODUCT master data, also add it to those simple master data types which have PRDID
  3. Sequentially activate attributes and time profile
  4. Add WSPCODE manually to the planning area attributes
  5. Activate the planning area
  6. Add the forecasting parameters and add the Supply planning operator: SCM to the planning area WTECH
  7. Manually add the WSPCODE to those planning levels which have PRDID in them
  8. Re-activate the planning area : <Error encountered>

Error: E - Exception raised from InternalError: dberror(PreparedStatement.execute): 2048 - column store error: fail to create scenario:  [34011] Inconsistent calculation model;CalculationNode (3_101) -> operation (CustomLOp):Output table '3_101' has no column 'WSPCODENUM' in the signature of the main function,Details (Errors):

  - CalculationNode (3_101) -> operation (CustomLOp): Output table '3_101' has no column 'WSPCODENUM' in the signature of the main function

As I understand this error means that the forecasting / supply algorithms do not recognize WSPCODE as its a custom attribute.

Request your advice on how to resolve this error. Can I create a composite key for PRODUCT master data (PRDID + Special Code) in the first place? If not, then how do I address my issue where the client product master data has combination key with PRDID referring to marketing part num and Special Code to the different dies. the demand data is to be generated at marketing part num + Special code.

Thank you,


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Oct 26, 2015 at 09:15 AM

    Hi Alok,

    The supply planning algorithm will not work in case of custom planning level where PRDID and WSPCODE both are root attributes since it is not known to algorithm.You need to bring your demand data at PRODCUST level. You can try following steps-

    1) Create two different MDTs for PRODUCT and WSPCODE having PRDID and WSPCODE as primary key

    2) Create a compound master data using both the MDTs(not required if you do not have any additional attribute)

    3) Define your demand data at a planning level which has both the above attributes(lets say PERPRODCUSTWSP)

    4) Define a calculation step to calculate demand at PERPRODCUST

    5) Use this to enter value of CONSENSUSDEMAND@PERPRODCUST level for supply planning.



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Rohit,

      Thanks for your prompt replies. Yes, I had already added PERIODID as part of time profile to the PERPRODCUSTSPCODE planning level. (just like PERPRODCUST)

      And the O/P planning level is PERPRODCUST i.e. we are configuring to upload demand data (sales, mkting etc) at PERPRODCUSTSPCODE level and then aggregating the data to PERPRODCUST level.

      I have successfully configured all the demand data inputs at PERPRODCUSTSPCODE (Sum up to PERPRODCUST level) . I am trying to configure the demandplanningqty and then the consensusdemand at PERPRODCUSTSPCODE level. (and then aggregate them to PERPRODCUST level).