cancel
Showing results for 
Search instead for 
Did you mean: 

Can we have two attributes of a Simple Master Data as root in a Planning Level

achal_gautam2
Explorer
0 Kudos

Hi,

We are using IBP 6.1. We have a requirement of to create a Planning level in which 2 attributes of a simple master data should be root attribute. e.g- I want to add PRODUCTID & XX (another attribute of Product Master Data) and CUSTID and YY (another attribute of Customer Master Data) as root attribute in planning level. Is it possible ?

I tried to create a Planning Level like this and I got following errors-


E - Procedure creation failed for Planning Set: SAPIBP1Y1SAPIBP1 with error: An exception of type 'CX_AMDP_EXECUTION_FAILED' occurred, that was not caught anywhere in the call hierarchy. It was not handled locally or declared using a RAISING clause.

E - Error when activating planning set SAPIBP1Y1SAPIBP1

E - An exception was raised.

E - An exception of type 'CX_AMDP_EXECUTION_FAILED' occurred, that was not caught anywhere in the call hierarchy. It was not handled locally or declared using a RAISING clause.

E - An error occurred when the database procedure    /IBP/CL_SAP_SFND_SOPINTEG=>SOPINTEG_GPRC_GPLOBJID_BPL_PLS  was called. Potentially, the procedure    /IBP/CL_SAP_SFND_SOPINTEG=>SOPINTEG_GPRC_GPLOBJID_BPL_PLS  was called by another database procedure. The method called from ABAP is    /IBP/CL_SAP_SFND_SOPINTEG=>SOPINTEG_GPRC_GPLOBJID_BPL_PLS  Database connection used: "" (default connection if empty)  SQL error on the database: "129"  SQL message on the database: "transaction rolled back by an internal error:  [129] "SAPHANADB"."/IBP/CL_SAP_SFND_SOPINTEG=>SOPINTEG_GPRC_GPLOBJID_BPL_PLS#stb2#20160416122626": line 11 col 3 (at pos 302): [129] (range 3): transaction rolled back by an internal error: transaction rolled back by an internal error:  [129] "SAPHANADB"."/IBP/CL_SAP_SFND_SOPINTEG=>SOPINTEG_GPRC_GPLOBJID_BPL_PLS": line 1108 col 9 (at pos 78366): [129] (range 3): transaction rolled back by an internal error: transaction rolled back by an internal error: "SAPHANADB"."/IBP/CL_SAP_SFND_SOPDM=>SOPDM_CREA_DROP_PROC_AS_SAPSOP": line 39 col 13 (at pos 1506): [129] (range 3): transaction rolled back by an internal error: invalid column name: CLOCALPRODUCTDESCR: line 78 col 230 (at pos 14998)"

E -  Error at: /IBP/CL_SAP_SFND_SOPINTEG=====CP, /IBP/CL_SAP_SFND_SOPINTEG=====CM011:1

Regards,

Achal

Accepted Solutions (1)

Accepted Solutions (1)

Irmi_Kuntze
Advisor
Advisor
0 Kudos

Hi Achal

You cannot have more than one key in a simple MD type, that is just the definition of SIMPLE, you can only mark the addtional attribute as required. For additional key, you would need a compound MD type.

But you can have it simple MD type with just product ID as key, but add the addtional attributes to the planning level as root.

Yours

Irmi

Answers (0)