Docs / Outbound Messaging
Real-Time ATP (Inventory)
Real-time ATP requires trigger consolidation plus online availability calculation. ASAPIO provides the integration pattern and example implementation approach.
Overview: Real-Time Inventory for Materials
ATP is not a static database value. SAP calculates current availability from stock, reservations, inbound supply, and planned dates. Therefore, ATP integration needs:
- Detection of all relevant business changes
- Transformation into ATP calculation keys
- Online ATP calculation and outbound payload generation
Required Configuration
| Object Name | Object Type | Configuration |
|---|---|---|
| Sales Order | BUS2032 | Standard |
| Purchase Order | BUS2012 | Standard |
| Delivery | LIKP | Standard |
| Goods Movement | BUS2017 | BAdI (MB_DOCUMENT_UPDATE) |
| Material Reservation | ZBUS2093 | User Exit (MBCF0007) |
Create Outbound ATP Configuration (SAP GUI)
Create custom extractor function module (example: Z_ACI_EXTRACTOR_ATP) with ASAPIO extractor interface and ATP logic based on BAPI_MATERIAL_AVAILABILITY. The extractor should build payload lines from MATNR/MEINS/WERKS keys and include calculated quantity output.
- Transaction SE37: create FM
Z_ACI_EXTRACTOR_ATP. - Implement key parsing from BDCP entries and ATP calculation call.
- Create outbound object in /ASADEV/ACI_SETTINGS using this extractor.
Set-up Business Object Event Linkage
Implement BAdI /ASADEV/TRIGGER_BADI (method /ASADEV/TRIGGER_IF~SET_BDCP_LINES) to normalize trigger-specific keys into MATNR/MEINS/WERKS ATP keys.
Link relevant BO events in Event Linkage:
| Object Name | Object Type | Event | Tables | Transaction |
|---|---|---|---|---|
| Sales Order | BUS2032 | Created, Changed | VBAK, VBAP | VA01, VA02 |
| Purchase Order | BUS2012 | Created, Changed | EKKO, EKPO | ME21N, ME22N |
| Delivery | LIKP | Created, Changed | LIKP, LIPS | VL01, VL02 |
| Goods Movement | BUS2017 | Created | MKPF, MSEG | MB11 |
| Material Reservation | ZBUS2093 | Created, Changed | RKPF, RESB | MB21, MB22 |
Via Event Studio
Event Studio can be used for deployment governance and payload validation, while ATP-specific trigger normalization and custom extractor logic remain SAP GUI/ABAP implementation tasks.
Test Example
Typical ATP payload output:
{
"value": [
{
"objectType": "BUS2012",
"werks": "1200",
"matnr": "DPC1002",
"meins": "ST",
"date": "20221011",
"quantity": "4216.000"
}
]
}