|
TRANSLATORS! Be sure to retain the original order of the numbered conditions and sequence of the variables. You want to assign the remote attribute &V3& to the role attribute &v2&of field &v1&. This is not possible because in this case the conditionV4 has been violated. The following conditions must be met before you can allocate the twoattributes to each other: To characteristic &v1& you need to assign a role that has a &V2&attribute. Characteristics &v1& and &v3& must be remote fields (for example,InfoObjects); and &v3& must be assigned as an attribute tocharacteristic &v1&. Attributes &v2& and &v3& must have the same . Attributes &v2& and &v3& must have the same Attributes &v2& and &v3& must have the same Attributes &v2& and &v3& must have the same time dependencies. Assignments of remote attributes to role attributes must be injective -that is, only one remote attribute can be assigned a given roleattribute, and only one role attribute can be assigned to a remoteattribute. The only exception to this is stated under condition 8. If role attribute &v2& has other kinds of dependencies besides possibletime dependencies, and these other dependencies cannot be modeled withremote attribute &v3&, you need to confine all of these additional keyfields to unique fixed values when assigning the attribute. In thiscase, the assignment only applies to these values of the independentcharacteristics. In a case as described here, you can also assignmultiple remote attributes to a single role attribute, but then you needto confine the respective additional key fields to different fixedvalues. Role attribute &V2& may not be mapped to a predefined fixed name of anInfoObject. This is because, in this specific case, an implicitassignment already exists. Thus, it is sufficient to assign, as anattribute, the InfoObject assigned to &V2& in table UGBW4000 toInfoObject &V1&. If you do this, the system will always automaticallytransfer any changes of role attribute &V2& to the SAP BW system, aswell. System Response Procedure |