Question:
Hello all!
I got this error back in October '02, after we applied patches 23-26 to our 2.0B, for a transfer routine to populate an attribute of 0MATERIAL (This routine was written when we were on SP16.)
An OSS message did not help, because they could not reproduce the error in their/our systems. It happened in our QA system.
The SPs were successfully applied to the production environment without any problems, and the error did not show up.
Now our marketing people need to see some info which is a subset of product hierarchy, so I created an InfoObject, put it in 0MATERIAL as an attribute, and went to the TR to write the routine. It showed a warning that D type fields have no length specification (old message). So I deleted the length specification for ERSDA and saved the routine. On activating the TR, the error message said that there was a syntax error for the routine for the older object(like in OCtober). This is in our development system.
I tried a trick, deleted the old object and reactivated the TR. The error message now referred to the new object (again!).
OSS search for notes showed up only a note for 3.0A/3.0B with a similar error message. Other notes applied to systems on SP 22 or less.
I am posting this here since I know OSS will take a very long time to respond, and BWE fans are much quicker to help.
TIA.
_________________
Keep smiling
Answer:
To prevent this from holding you up, you could assign the additional attributes to a new object keyed on the same value as 0MATERIAL...
MATERIAL_EXTENSION (assign 0MATERIAL in update rules)
Attribute_1
...
Attribute_n
You just have to add this to your cube to make the navigable attributes available in reporting (obviously the object itself is not used, and it has no text associated).
Answer:
The point is, I have to derive it from an attribute of 0MATERIAL. 0PROD_HIER (type C, length 18 ).
ZBASEMOD = 0PROD_HIER+3(15).
So how would this be derived in your scenario? This and a few other problems have dirven me to the edge, so can you please explain with some examples?
Thanks, Robert
_________________
Keep smiling
Answer:
Sorry for delayed response.
To load the new master in this case I think you would need to generate a new (BW) data source from 0MATERIAL; I don't think BW lets you reuse the R/3 data source. You then have access to all the existing material attributes in the rules to derive your new attribute.
Maybe I didn't explain what I meant very well. If this is still a problem let me know if you would like me to try to elaborate.
Good luck!