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

[Former Member]

Hi,

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

....so 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,

Alok

[Former Member · Accepted solution]

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.

Thanks,

Rohit

[Former Member · Accepted solution]

Thanks Rohit,

This is very insightful. So I am deriving my CDP at CDP@PERPRODCUSTSPCODE level then  aggregating it to the CDP@PERPRODCUST level. This handles my demand.

For supply planning, how do I convert the CDP@PERPRODCUST level when my CRATIO is defined at PERPRODCUSTLOC level and not at PERPRODCUSTSPCODELOC.

Do I follow the same approach as I did for Demand i.e. enter a calculation logic: DEPENDENTCUSTOMERDEMAND@PERPRODCUSTSPCODELOC = CRATIO@PERPRODCUSTSPCODELOC  * CDP@PERPRODCUSTSPCODE

then DEPENDENTCUSTOMERDEMAND@PERPRODCUSTLOC  = SUM ( DEPENDENTCUSTOMERDEMAND@PERPRODCUSTSPCODELOC)

Is it mandatory to define CRATIO@PERPRODCUSTLOC  level only or can I do it at CRATIO@PERPRODCUSTSPCODELOC. As the Supply Planning algorithm can automatically compute my dependent customer demand , location demand etc. (using the SCM operators) , will this not create a conflict. How do I perform my supply planning considering the PROD-SPCODE combination.

Appreciate your thoughts in this regard.

Thanks,

Alok

[Former Member · Accepted solution]

Hi Alok,

Yes, CRATIO should be at PERPRODLOCCUST level only. Also, supply planning will calculate all other upstream key figures at their standard planning levels. Once you have demand data at PEPRODCUST level, other key figures like dependent customer demand, net demand etc will be calculated by the algorithm at their defined planning levels.

Another way i could think of is to concatenate PRDID and WSPCODE to generate unique PRDID. Not sure if this would be a feasible option for you since it requires changing master data.

Thanks,

Rohit

[Former Member · Accepted solution]

Hi Rohit,

Thanks for your inputs. I am trying to follow your inputs and configure accordingly. I have done the following :

1. as advised created new mdt for special code and then compound mdt with PRDID and SPCODE

2. created planning level PERPRODCUSTSPCODE

3. added calculation logic for all the PERPRODCUST demand key figures as data is to be loaded at SPCODE level. i.e. the new calculation logic is <key demand fig>@PERPRODCUST = SUM(<key demand fig>@PERPRODCUSTSPCODE)

I face an error while doing this for DEMANDPLANNINGQTY. As per the calc logic :

I am trying to add DEMANDPLANNINGQTY@PERPRODCUST = SUM(DEMANDPLANNINGQTY@PERPRODCUSTSPCODE)

Followed by:

IF("PERIODID" >= "$$PERIODIDCU$$", IF(ISNULL("DEMANDPLANNINGQTY@PERPRODCUSTSPCODE"),"MKTGPROMOTIONFCSTQTY@PERPRODCUSTSPCODE","DEMANDPLANNINGQTY@PERPRODCUSTSPCODE"),"ACTUALSQTY@PERPRODCUSTSPCODE")

I get an error that PERIODID is not available at PERPRODCUSTSPCODE level. (please note: all the other key figures used here such as MKTGPROMOTIONFCSTQTY , ACTUALSQTY etc are configured at PERPRODCUSTSPCODE level)

Request your guidance in this regard.

[Former Member · Accepted solution]

Hi Alok,

I think the message is self explainatory. Please check if PERIODID is selected in planning level PERPRODCUSTSPCODE. If not, then using drop down 'available attributes' select the PERIODID and assign it to the planning level.

You would also need to assign periodid in all those output planning levels where PERPRODCUSTSPCODE is used in input.

Thanks,

Rohit

[Former Member · Accepted solution]

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).