3708477 - Missing API for Purchase Scheduling Agreement condition creation in SAP S/4HANA Cloud Public Edition

• The OData API `API_PURGPRCGCONDITIONRECORD_SRV` successfully creates condition records in the system, but the item net price is not updated in the scheduling agreement item.
• Using the RAP Business Object `i_schedgagrmthdrtp_2` results in a warning during processing, impacting bulk condition creation/updates.
• Despite successful persistence of condition records, pricing is not recalculated or reflected at the item level.
• Error message: “Start of Validity Period is in the Past.”

SAP S/4HANA Cloud Public Edition

1. Create scheduling agreement pricing conditions via OData API `API_PURGPRCGCONDITIONRECORD_SRV` or RAP Business Object `i_schedgagrmthdrtp_2`.
2. Observe that the API successfully creates condition records, but the item net price is not updated in the scheduling agreement item.
3. Use the RAP Business Object `i_schedgagrmthdrtp_2` for bulk condition creation/updates.
4. Observe a warning during processing and note that pricing is not recalculated or reflected at the item level.

1. Schedule a job using the app: Schedule Update of Price for Purchasing Documents.
2. Use the template: Determine and Update Price of Scheduling Agreement Item (RM06ENP1).
3. Ensure that the Unit of Measure (UoM) value is maintained correctly while creating a new condition record through the OData API.

API_PURGPRCGCONDITIONRECORD_SRV, scheduling agreement, pricing conditions, net price update, RAP Business Object, i_schedgagrmthdrtp_2, validity period warning, SAP S/4HANA Cloud Public Edition, condition record creation, bulk updates. , KBA , MM-PUR-OA-SCH-2CL , Scheduling Agreement (Public Cloud) , Problem