Symptom
You use App Manage Activity Types to extend Validity Period for existing Activity Type.
Example:
Valid From | Valid To | |
Existing | 2020.01.01 | 9999.12.31 |
Existing | 2019.01.01 | 2019.12.31 |
New | 2018.01.01 | 2018.12.31 |
However after you created above new Validity Period, you find row 2 and row 3 are combined into one Validity Period.
This happens also if you use API API_COSTCNTRACTIVITYTYPE_CRUD_SRV (SAP_COM_0357) to create the new Validity Period.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
Extend Validity Period with App Manage Activity Types.
Cause
If the newly created Validity Period has the same master data with existing Validity Period, and it has the continued date with the existing one, system will combine the 2 Validity Periods together.
Resolution
This is intended design. If you want to have new Validity Period created, please at least change anything in the master data for the new Validity Period.
Keywords
OData, SAP_BCR_FIN_OH_MD_CCA_PC, Activity Type (A2X) , KBA , CO-OM-CCA-A-2CL , Master Data (Public Cloud) , CO-FIO , Fiori UI for Overhead Cost Controlling , Problem