SAP S/4HANA Integration Guide for SkyPlanner APS Production Scheduling

S/4HANA exposes its integration surface as released OData services, listed on the SAP Business Accelerator Hub (api.sap.com). The scheduling integration runs on OData V2 services. IDocs and BAPIs still exist, but this guide uses the released OData APIs.

Authentication by edition

• On-premise and Private Edition. The services are activated in SAP Gateway with transaction /IWFND/MAINT_SERVICE. The integration user needs the matching authorization objects, for example C_AFRU_AWK for confirmations, C_AFKO_AWK for the goods movement items posted with them, and M_PLAF_ORG for planned orders.
• Public Edition. Services are exposed only through communication arrangements. Following SAP’s inbound communication setup, you create a communication user, a communication system and a communication arrangement in the Communication Arrangements app, based on an SAP communication scenario (SAP_COM_xxxx). The scenario defines which services are exposed and which authentication methods are available:

– token-based: OAuth, SAML or OpenID Connect bearer flows, with principal propagation to a business user – client certificate – basic auth with a technical communication user

SAP recommends token or certificate authentication.

SkyPlanner’s counterpart is a REST API with JWT authentication, documented in Swagger/OpenAPI (API reference), so the middleware handles SAP auth on one side and a JWT on the other.

APIs for production scheduling

Service	Entities and actions used	Purpose
API_PRODUCTION_ORDER_2_SRV (Production Order, Version 2)	A_ProductionOrder_2, A_ProductionOrderItem_2, A_ProductionOrderOperation_2, A_ProductionOrderComponent_2, A_ProductionOrderStatus_2, A_ProductionRsceTools_2; actions ReleaseOrder, ReleaseOperation, ScheduleProductionOrderOperation	Orders, operations, components, PRTs, status, schedule write-back
API_WORK_CENTERS	A_WorkCenters, A_WorkCenterAllCapacity_2, A_WorkCenterCapacity, A_WorkCenterCapacityInterval_2, A_WorkCenterCapacityShift_2, A_WorkCenterCapPerBucket	Work centers, capacity categories, intervals and shifts
API_PRODUCTION_ROUTING	ProductionRoutingHeader, ProductionRoutingSequence, ProductionRoutingOperation, ProductionRoutingSubOperation, ProductionRoutingMatlAssgmt, ProductionRoutingOpCompAlloc	Standard routings for planning ahead of order creation
API_BILL_OF_MATERIAL_SRV;v=2	MaterialBOM, MaterialBOMItem, MaterialBOMSubItem	Multi-level product structure
API_PRODUCT_SRV (Product Master A2X)	A_Product	Materials (called Product in the API). SAP now recommends the Product (Version 2) API for most product entities
API_PLANNED_ORDERS	A_PlannedOrder, A_PlannedOrderComponent, A_PlannedOrderCapacity	MRP Live output before conversion
API_MATERIAL_STOCK_SRV	A_MaterialStock, A_MatlStkInAcctMod	Stock per plant and storage location, for material availability
API_PURCHASEORDER_PROCESS_SRV	A_PurchaseOrder, A_PurchaseOrderItem	Open purchase orders for incoming material
API_PROD_ORDER_CONFIRMATION_2_SRV	ProdnOrdConf2, ProdnOrdConfMatlDocItm; actions GetConfProposal, GetGdsMvtProposal, CancelProdnOrdConf	Confirmations and goods movements from the shop floor

In the production order API, operations are keyed by OrderInternalBillOfOperations plus OrderIntBillOfOperationsItem, not by the operation number the planner sees. The confirmation API’s GetConfProposal addresses the same operation by OrderID and OrderOperation. Store the internal keys and the operation number in SkyPlanner from the first load.

Events

S/4HANA raises Production Order Created and Production Order Changed business events with ManufacturingOrder, ProductionOrder, ProductionOrderType and ProductionPlant in the payload. The payload carries only keys, so the integration rereads the order and its operations. The Changed event fires on every change to the order, so debounce it. In the other direction, SkyPlanner webhooks push in real time when the schedule or job state changes.

File-based start

For the trial, export production orders and work centers from S/4HANA list reports to Excel or CSV and import them into SkyPlanner. This proves the schedule before anyone touches Gateway or communication arrangements.

1. Master data load. Load materials, BOMs, work centers with their capacity intervals and shifts, and routings. Decide here which system owns shifts. A split that works: the factory calendar stays in S/4HANA, and detailed shift patterns, absences and overtime live in SkyPlanner, where planners change them daily.

2. Order sync. Subscribe to Production Order Created/Changed, or poll A_ProductionOrder_2 by change timestamp where business events are not set up. Filter on plant, order type and status. Send orders at creation so SkyPlanner can plan ahead, and release them in S/4HANA (ReleaseOrder or ReleaseOperation) once SkyPlanner has scheduled them.

3. Schedule write-back. When a SkyPlanner webhook reports a schedule change, the integration calls ScheduleProductionOrderOperation in API_PRODUCTION_ORDER_2_SRV for each changed operation. It sends:

• ManufacturingOrder, OrderInternalBillOfOperations and OrderIntBillOfOperationsItem as keys
• OpSchedulingMode F (forward) with SkyPlanner’s start in OpSchedldStartDate and OpSchedldStartTime
• OpSchedulingStatus DISP (dispatch) and the mandatory OpSchedulingStrategy M
• the ETag in if-match

All operations of one order go in one change set, in SkyPlanner’s sequence order, so S/4HANA dispatches the order’s whole plan in one call. Mode K is never used: it keeps the original operation dates and ignores the dates sent.

SkyPlanner derives operation durations from the same routing standard values and work center capacity formulas that S/4HANA uses. The end date S/4HANA calculates from the dispatched start therefore lines up with the SkyPlanner plan. After each change set the integration rereads the operations and flags any date that differs, and the planner sees it before the next shift.

4. Shop floor confirmations. Each timelog from Mobile Confirmations or the Production Timer becomes an S/4HANA confirmation. SkyPlanner’s webhook triggers a ProdnOrdConf2 post with yield, scrap and activity times. The integration calls GetConfProposal first, so S/4HANA proposes quantities, activities, dates and personnel data. GetGdsMvtProposal proposes the goods movements.

Incoming material. Open purchase orders are part of the inbound sync. SkyPlanner treats ordered material as available on the PO’s expected delivery date. Jobs waiting for purchased components are scheduled to the day the material arrives, not blocked by today’s stock figure.

S/4HANA stays the source of truth for receipts: when a goods receipt posts, stock rises and the PO item’s open quantity falls. The next sync updates stock in SkyPlanner and marks a fully received PO as Delivered; after a partial receipt, the remaining open quantity stays incoming on its schedule-line date. SkyPlanner’s purchase order handling is described in the SkyPlanner docs.

5. Ownership rules. S/4HANA owns quantities, BOM, routing, costing and status. SkyPlanner owns sequence, workstation assignment and operation dates. Never let both write the same field. If planners still move operations in the Capacity Scheduling Board, decide what wins. Either the next order sync takes their change into SkyPlanner, or that work center stays outside SkyPlanner’s scope.

• Write-back is an action call with an ETag. The documented way to schedule an operation is ScheduleProductionOrderOperation, not a PATCH on A_ProductionOrderOperation_2. Mode F schedules forward from a start and B backward from an end, while K and S keep existing dates and ignore yours. The ETag in if-match is built from the order’s LastChangeDateTime (YYYYMMDDHHMMSS), so any change to the order makes it stale. Build read-before-write and a retry queue.
• Capacity is not on the work center header. Available capacity comes from the capacity category (001 machine, 002 labor), the factory calendar, and the intervals and shifts that override it. Capacity formulas turn routing standard values into setup, processing and teardown requirements. Read A_WorkCenterCapacityInterval_2 and the shift entities, and agree how formulas translate into SkyPlanner durations.
• Standard values need cleaning. Routings maintained for costing often carry averaged setup times, or setup booked on the wrong capacity category.
• Confirmation rules are strict. SAP recommends batch calls for mass posting. One change set is all-or-nothing, so one bad time ticket blocks the rest of that set. Cancellations in a batch must run in reverse ConfirmationCount order. You cannot mix confirmation types on one order, post goods movements without a confirmation, or confirm operations whose trigger points need a dialog box.
• Check whether PP/DS is active. Embedded PP/DS needs the Customizing activity Activate Advanced Planning and Scheduling and SAP HANA integrated liveCache. SAP sells it as a separate product, SAP S/4HANA Manufacturing for planning and scheduling. Where it is active, decide per material who schedules: materials flagged for advanced planning belong to PP/DS. SAP also states for the planned order API: “Automatic integration to PP/DS is not enabled from this API.”
• Units of measure. Operation quantities, routing base quantities and confirmation units can differ. Convert explicitly using the operation unit, not the material base unit.
• Edition drift. SAP Learning shows the classic CM21/CM22 planning table being replaced by Manage Work Center Capacity, Capacity Scheduling Table and Capacity Scheduling Board. Public Edition exposes APIs only through communication scenarios, and the service versions it offers can differ from on-premise. The routing API cannot delete routings or update material assignments. The SkyPlanner team pins the service versions per customer system during scoping, using the API Business Accelerator Hub entry for that release.
• Constraints routings do not hold. Keep sequence-dependent changeovers, tool conflicts and multi-operator operations in SkyPlanner, not in routing standard values. The setting time matrix holds changeover times per product pair. Tools from the order’s PRTs are finite, one workstation at a time, and an operation can require several people at once.