Change Impact Analyser
Describe any SAP change in plain English. The engine identifies every impacted BAPI, Function Module, Table, Transaction and Report — upstream and downstream — and shows the live dependency graph with effort estimates.
Upload change request notes, BRD or TRD (PDF · DOCX · TXT · CSV · MD). The Landscape Knowledge Base is read automatically; uploaded text seeds the change description. The Landscape Intelligence knowledge base is treated as the primary context for this tool — if it is not loaded, please run the Landscape Intelligence Pack first, or paste context into the free-text box below.
Impact Ledger
| Object | Type | Direction | Days |
|---|---|---|---|
| LFB1 (Vendor Co. Code) · CHANGE POINT | |||
| BAPI_VENDOR_CHANGE | BAPI | Downstream | 2.5d |
| LFA1 (Vendor General) | Table | Upstream | 1d |
| T052 (Payment Terms) | Config | Upstream | 0.5d |
| XK02 (Change Vendor) | Transaction | Downstream | 0.5d |
| FK02 (FI Vendor) | Transaction | Downstream | 0.5d |
| F110 (Auto Payment) | Transaction | Downstream | 2d |
| BAPI_ACC_GL_POSTING | BAPI | Downstream | 1.5d |
| PAYR (Payment Doc) | Table | Downstream | 1d |
| FBL1N (Vendor Items) | Report | Downstream | 0.5d |
| MIRO (Invoice Entry) | Transaction | Upstream | 0.5d |
| Dunning Programme | Report | Downstream | 1d |
| Cash Flow Forecast | Report | Downstream | 1d |
| DPO KPI Dashboard | Report | Downstream | 0.5d |
Impact Summary
- Payment terms change in LFB1 affects ALL vendor accounts in the company code
- F110 will recalculate due dates for all open items
- Re-test required: MIRO invoice entry, F110 proposal, dunning
- Treasury cash flow forecast will show different payment timing
- Estimated total regression test effort: 4–6 days
Every A²AI recommendation is provisional until a senior SAP consultant signs it off. Use the buttons below to record the verdict, or flag it back to A²AI for more input.