Do you have any question about this error?
Message type: E = Error
Message class: RS_HCPR_MODEL - Messages related to the HANA Composite Provider Backend
Message number: 016
Message text: Temporal join: &1, &2 not allowed
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
When a temporal join is used<(>,<)> only the following TLOGO objects areRemove all unsupported TLOGO objects
Switch off the time-dependency of all joined time-dependent
PartProviders (ScenarioTab, SourceTree)
InfoObjects: Hide time-dependent fields
Advanced/classic DataStore Objects, InfoCubes: Remove time-dependency
Error message extract from SAP system. Copyright SAP SE.
RS_HCPR_MODEL016
- Temporal join: &1, &2 not allowed ?The SAP error message RS_HCPR_MODEL016, which states "Temporal join: &1, &2 not allowed," typically occurs in the context of SAP HANA or SAP BW when working with data models that involve temporal joins. This error indicates that there is an issue with the way temporal joins are being defined or used in your data model.
Cause:
Incompatible Time Characteristics: The error often arises when the time characteristics of the two tables or data sources being joined are not compatible. For example, one table may have a time dimension defined as a "validity period," while the other may not have a corresponding time dimension.
Incorrect Join Type: The join type specified may not be appropriate for the temporal data being used. Temporal joins require specific conditions to be met regarding the time attributes.
Missing Time Attributes: One or both of the tables involved in the join may be missing the necessary time attributes that are required for a temporal join.
Modeling Errors: There may be errors in the data model configuration, such as incorrect settings in the data flow or model definition.
Solution:
Check Time Attributes: Ensure that both tables involved in the temporal join have compatible time attributes. Verify that they both have the necessary time characteristics defined.
Review Join Conditions: Examine the join conditions to ensure that they are appropriate for a temporal join. Make sure that the join type is suitable for the data being processed.
Adjust Data Model: If necessary, adjust the data model to ensure that the time attributes are correctly defined and that the tables are set up to allow for a temporal join.
Consult Documentation: Refer to SAP documentation or help resources for guidance on how to properly configure temporal joins in your specific version of SAP HANA or BW.
Testing: After making adjustments, test the data model again to see if the error persists. If it does, further investigation into the specific configurations of the tables may be required.
Related Information:
By following these steps, you should be able to identify the cause of the RS_HCPR_MODEL016 error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
RS_HCPR_MODEL015
Temporal join: No Union allowed
What causes this issue? The HANA CompositeProvider contains a UNION node and at least one JOIN node. At least one joined PartProvider is time-depende...
RS_HCPR_MODEL014
Compounding parent '&1' for nav. attribute '&2' missing (field '&3')
What causes this issue? The compounding parent of the navigation attribute cannot be found in the field list of the CompositeProvider. Either no fiel...
RS_HCPR_MODEL017
Temporal join: SAP HANA objects not allowed (&2, &1)
What causes this issue? When a temporal join is used<(>,<)> only the following TLOGO objects are supported: ADSO: Advanced DataStore Obje...
RS_HCPR_MODEL018
Temporal join: Unassigned target field &1
What causes this issue? The CompositeProvider contains target fields without being assigned to a source field. The system issues an error message and...
Click on this link to search all SAP messages.