3646000 - Activity Units Proposals Not Determined Based on Yield Quantity When Confirming Production/Process Orders via API

• When confirming production/process orders via API (API API_PROC_ORDER_CONFIRMATION_2_SRV/ProcOrdConf2), the activity units proposals (Machine and Time) are not determined based on the yield quantity.
• The issue does not occur when confirmations are posted manually using the Confirm Production Order Operation app (CO11n) or Confirm Process Order Phase (COR6n) app.

SAP S/4HANA Cloud Public Edition.

• This is standard system behavior.
• Activity proposals during confirmation differ depending on whether you use:
  • The standard Fiori apps (Confirm Process Order Phase)
  • Or APIs.
• For API-based scenarios, activity proposals must be explicitly fetched before posting the confirmation.

• For API confirmations, use the “Fetch Proposals” functionality to manage activity proposals.
• This allows you to retrieve proposal data for:
  • Quantities
  • Activities
  • Dates and Times
  • Personnel Data
• The process is:
  1. Call the service via HTTP method POST to call GetConfProposal function.
  2. Use the response data to create the time ticket confirmation (with or without material document postings).

For detailed guidance, please refer to the SAP Help documentation:

• Fetch Proposals for Quantities, Activities, Dates and Times, Personnel Data

• Fetch Proposals for Quantities, Activities, Dates and Times, Personnel Data | SAP Help Portal

sap_03, labor time, automatic calculation, odata api, prodordconf2, co11n, routing, work center, sap cloud integration, time ticket confirmation, getconfproposal, sap s/4hana public cloud, enterprise services, shop floor control , KBA , PP-SFC-ES-2CL , Enterprise Services in Shop Floor Control (Public Cloud) , Problem