3802109 - Excel import rejects all rows with DATA_LOCKING when Measures is a Data Locking driving dimension (SAP Analytics Cloud)

• Importing an Excel file via End-User File Upload to a planning model results in all rows being rejected.
• Rejection reason shown in the rejected rows file: DATA_LOCKING.
• Data Locking is reported as open for the relevant dimensions and measures.

• SAP Analytics Cloud
• Planning

1. Run the End-User File Upload (Excel Import Job) to import data into the planning model.
2. Observe that the import rejects all the rows with the reason DATA_LOCKING.

• When the Measures dimension is configured as a Data Locking driving dimension, any combination of Version + Date + another driving dimension that has mixed lock states across Measures cannot be changed via import. End-User File Upload rejects such rows during Data Locking validation with reason DATA_LOCKING.

In some cases when figuring out whether a value has changed or remained the same, the software doesn’t distinguish between different measures for a specific set of leaf members.

This happens because models with measures store the values for each measure on the same row in the fact table. (Each row is associated with a combination of leaf members from all dimensions.)

This issue occurs in the following situations:

When you enter data for two measures that belong to the same set of leaf members, a message appears showing that one database record was changed.

When data locks are applied with measures as a driving dimension, this issue affects importing or deleting values in the modeler. For any set of dimension members with a mix of locked and unlocked measure values, you won’t be able to change any of the measure values by importing or deleting data in the modeler. (Appending unbooked values to these measures is allowed, since it doesn’t change the data.) For details about data locking, see Configuring Data Locking.

When you copy a public version and publish the resulting private version to a different public version, you can choose to only publish the changed dimension combinations (Publish member combinations with changed data). In this case, all measures will be published for each set of leaf members where any measure was changed.

• Refer to: Treatment of measures from the same set of dimension members — Help
• Configuring Data Locking

data locking, excel import, end-user file upload, planning model, measures driving dimension, mixed lock states, DATA_LOCKING, rejected rows, import job, sac planning, import validation, locked measure, driving dimensions, data management, modeler deletion , KBA , LOD-ANA-PL , Planning , Problem