Copy Operator between 2 Planning Areas: entry doesn't exist in root attribute - Workaround?

[vincentverheyen]

Let's assume we have a "Copy Operator Profile (Copy Key Figure Values Between Two Planning Areas)".

Question on the side: do I understand it correctly that this is not a standard "Copy Operator", but in fact is a "Copy and Disaggregate Key Figure Operator"? I assume so, since, in an Application Jobs Template, one can not locate the Copy Operators (Between Two Planning Areas) in a "Step: Template: Copy Operator"? Instead, one must choose: "Step: Template: Copy and Disaggregate Key Figure Operator"?

My actual question pertains to the necessity for Master Data in the target Planning Level of the target Key Figure in the target Planning Area.

I have noticed the error "Entry doesn't exist for root attribute CUSTID in MD TSPA_CUSTOMER for planning level MTH...[...]...CUST".

Notice this concerns a Copy Operator (Between Two Planning Areas) with an attribute mapping from CUSTOMERID (OBP Planning Area) to CUSTID (TS Planning Area).

Indeed, there is no such Master Data entry (in the target Planning Area) for the concerned "Planning Objects which could not be created for the Planning Level".

Note 2742072 - IBP data integration: Entry doesn't exist for root attribute... mentions:

"There are two options for you to avoid this error.

1. Load the master data that is missing;
2. or disable the attribute check in the master data types definition."

Regarding 1: Is there a way to use "Rules for Master Data Maintenance" to copy Master Data from OBP Planning Area's OBPA_CUSTOMER into TS Planning Area's TSPA_CUSTOMER Master Data?

Would another possible workaround be to have a second Planning Level "MTH...[...]...CUSTCOPY" where CUSTID is no longer the root, to perform the Copy Operator without any issues? In other words: was the issue merely the fact that the missing Master Data entry was on a root attribute in the target Planning Level? If so, we can, after having performed the trans-Planning Areas copy operator, perform a second copy operator within the Planning Area, to get the desired Key Figure values back on the default "MTH...[...]...CUST" Planning Level which does have root attribute CUSTID? Would such work?

See also Controlling Planning Objects:

"By controlling the creation of planning objects, you can ensure that only those planning objects exist that also exist as master data records in the master data type; that is, you can control the superset of planning objects. [...]

"If you want to ensure that only those products are planned that are actually sold to your customers, you need to restrict the planning objects that can be created. This can be achieved by assigning the Customer-Product master data type to the Customer-Product planning level. This way, planning objects are only created for attribute combinations that exist as entries in the master data type."

----------------------------------------

Note: the above is assuming that there is no integration of Master Data into the Time-Series Planning Area via for example RTI or CI/DS.