While migrating an AD361 installation to iD5.1 I get the mentioned error in a report based on RV_BPartner. It is related to the column ad_user_c_bpartner_location_id which has a length of exactly 30 chars which seems ok. But the DataEngine is then constructing longer identifiers like for example
(SELECT C_BPartner_Location.Name FROM C_BPartner_Location C_BPartner_Location
WHERE RV_BPartner.AD_User_C_BPartner_Location_ID=C_BPartner_Location.C_BPartner_Location_ID
) AS IAD_User_C_BPartner_Location_ID,
where IAD_User_C_BPartner_Location_ID has 31 characters.
I read somewhere that Oracle solved this with version 12c where identifiers could be 128 bytes long but the system is on 11gXE.
Some other views use the same identifier like C_Order_Header_V/_VT, C_Invoice_Header_V/_VT, C_Dunning_Header_V/_VT. Looks as it has been introduced already in i1.0b
While migrating an AD361 installation to iD5.1 I get the mentioned error in a report based on RV_BPartner. It is related to the column ad_user_c_bpartner_location_id which has a length of exactly 30 chars which seems ok.
But the DataEngine is then constructing longer identifiers like for example
(SELECT C_BPartner_Location.Name FROM C_BPartner_Location C_BPartner_Location WHERE RV_BPartner.AD_User_C_BPartner_Location_ID=C_BPartner_Location.C_BPartner_Location_ID ) AS IAD_User_C_BPartner_Location_ID,where IAD_User_C_BPartner_Location_ID has 31 characters.
I read somewhere that Oracle solved this with version 12c where identifiers could be 128 bytes long but the system is on 11gXE.
Some other views use the same identifier like C_Order_Header_V/_VT, C_Invoice_Header_V/_VT, C_Dunning_Header_V/_VT. Looks as it has been introduced already in i1.0b