Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian auto-component Tier-1 manufacturers on SAP S/4HANA all end up building the same 8-12 custom ABAP Z-reports because standard SAP does not run the auto-component reconciliation streams as standing exception processes. The Z-report family forks per OEM customer over time, the maintenance burden compounds to ₹50-80 lakh per year at a 4-OEM Tier-1, and the rebuild-backlog estimates exceed the original build effort by year 3-4. The result is a no-end-state custom-ABAP run-rate that drives the build-vs-buy reconsideration at OEM customer number three.
Enumerate the recurring Z-report list (CUM drift, ASN ageing, OEM debit-note decomposition, RMPV claim, ITC-04 generation, free-issue reconciliation, tonnage-rate billing, Section 393 / 394 deduction split), document the source SAP tables and IDoc message types each Z-report consumes, quantify the build effort and the ongoing per-Z-report maintenance burden, identify the OEM-customer-count threshold at which the custom-ABAP economics break, and frame the companion-product alternative that consumes SAP standard extracts and runs the standing-exception streams externally.
SAP S/4HANA install with auto-component-specific MM and SD configuration, Z-namespace ABAP development for ZSAR_CUM_DRIFT, ZSAR_ASN_AGEING, ZSAR_DEBIT_NOTE_DECOMP (typically forked per OEM by year 2), ZSAR_RMPV_CLAIM, ZSAR_ITC04_GEN, ZSAR_FREE_ISSUE_RECON, ZSAR_TONNAGE_BILL, ZSAR_TDS_SECTION_393, source-table catalogue (EKKO / EKPO / EKES / EKBE for procurement, VBAK / VBAP / LIKP / LIPS / VBRK / VBRP for sales, MARM / MARC / MCHB for material and batch, J_1IG and J_1IS family for India localisation, WITH_ITEM for withholding tax), IDoc message-type registry, scheduled job framework for nightly Z-report execution.
A custom-ABAP Z-report inventory typically counting 8-12 reports at a mid-Tier-1, annual maintenance run-rate of ₹50-80 lakh fully-loaded, forking pattern per OEM customer that compounds maintenance burden non-linearly, and a build-vs-buy boundary at OEM customer number three beyond which a unified reconciliation companion product replaces the Z-report family with substantially lower run-rate and faster cycle time.
A ₹600 crore Indian Tier-1 stamping-and-sub-assembly supplier in Pune runs SAP S/4HANA, live since 2022, supplying five OEM customers — Maruti Suzuki, Tata Motors, Mahindra & Mahindra, Hero MotoCorp and a JCB / John Deere construction-equipment OEM. The Tier-1’s internal SAP centre of excellence runs a three-developer ABAP team. The current Z-report inventory in production: 11 ZSAR_ prefixed reports covering CUM drift, ASN ageing, OEM debit-note decomposition (forked per OEM into four parallel codebases), RMPV claim generation, ITC-04 multi-hop generation, free-issue stock reconciliation, tonnage-rate billing for the steel-stamping product line, Section 393 / 394 TDS / TCS deduction split, supplementary-invoice register reconciliation, tooling cap monitor and KLT bin float register. The annual fully-loaded ABAP maintenance run-rate on this Z-report family is ₹68 lakh. The CTO has commissioned a build-vs-buy review.
This is the structural reality of every Indian auto-component Tier-1 on SAP S/4HANA. The Z-report list above is remarkably consistent across Tier-1s — every Tier-1 hits the same gaps and builds substantially the same set of ABAP custom reports. This is the SAP ABAP custom reports auto component reconciliation India operating reference, with the build economics, the maintenance pattern and the build-vs-buy trigger.
Quick reference
| Z-report | Purpose | Build effort | Annual maintenance |
|---|---|---|---|
| ZSAR_CUM_DRIFT | CUM-shipped vs CUM-received drift exception | 6-10 weeks | ₹5-7 lakh |
| ZSAR_ASN_AGEING | ASN-to-GRN ageing per OEM | 4-6 weeks | ₹4-5 lakh |
| ZSAR_DEBIT_NOTE_DECOMP | OEM debit-note decomposition (forks per OEM) | 10-14 weeks initial | ₹8-12 lakh (consolidated across forks) |
| ZSAR_RMPV_CLAIM | RMPV claim generation against commodity index | 8-12 weeks per OEM | ₹6-8 lakh |
| ZSAR_ITC04_GEN | ITC-04 JSON generation including multi-hop | 6-10 weeks | ₹4-6 lakh |
| ZSAR_FREE_ISSUE_RECON | Free-issue steel / coil reconciliation | 4-6 weeks | ₹4-5 lakh |
| ZSAR_TONNAGE_BILL | Tonnage-rate billing for stamping product lines | 5-8 weeks | ₹4-5 lakh |
| ZSAR_TDS_SECTION_393 | Section 393(1)(a) / (k) deduction split + cross-era | 6-10 weeks | ₹5-7 lakh |
| ZSAR_TOOLING_CAP | Tooling amortisation cap monitor | 4-6 weeks | ₹4-5 lakh |
| ZSAR_KLT_BIN_FLOAT | KLT bin float position with Section 143 exposure | 5-8 weeks | ₹4-5 lakh |
| ZSAR_SUPP_INVOICE_RECON | Supplementary-invoice register reconciliation | 4-6 weeks | ₹4-5 lakh |
| ZSAR_FORM168_RECON | Form 168 TDS challan reconciliation | 4-6 weeks | ₹4-5 lakh |
Why every Tier-1 builds substantially the same Z-report family
SAP S/4HANA’s standard MM, SD and FI modules cover the document mechanics of scheduling-agreement supply comprehensively — EDI IDoc processing through ORDERS / DELFOR / DESADV / INVOIC / GSVERF, delivery creation through VL10A / VL10B, GRN through MIGO, three-way match through MM-LIV, withholding tax through the standard tax configuration. What standard SAP does NOT do is run the auto-component reconciliation streams as standing exception processes — CUM drift as a tracked exception (not just a displayed position), OEM debit-note decomposition into reason-coded categories, RMPV claim computation against external commodity indices, ITC-04 multi-hop chain logic, free-issue stock with Section 143 exposure tracking. These are the gaps that the Z-report family fills.
The list above is the canonical inventory observed across mid-Tier-1s (₹400-800 crore revenue, 4-6 OEM customers). A particular Tier-1 may add a Z-report or two specific to its product mix — a forging Tier-1 will have ZSAR_HEAT_TREATMENT_LOSS, a casting Tier-1 will have ZSAR_REJECTION_COST_RECON — but the core 8-12 are universal.
Z-report 1 — ZSAR_CUM_DRIFT
Purpose: detect and age the drift between supplier CUM-shipped position (from ASN outbound IDocs / DESADV) and OEM CUM-received position (from GRN postings + OEM portal confirmation feeds).
Source SAP tables: EKES (scheduling agreement releases), EKBE (purchase order history), VBAK / VBAP / LIKP / LIPS (sales-side delivery), MKPF / MSEG (material movements). The Z-report joins these against an external OEM portal export typically dropped on SFTP.
Logic: nightly delta extract, drift calculation per scheduling-agreement-line, classify drift type (missed ASN, duplicate ASN, out-of-sequence dispatch, OEM GRN-posting delay), age by drift-detected date, push to a custom Z-table with workflow status.
Maintenance pattern: ABAP support requests typically focus on edge cases — partial-receipt postings, batch-level vs item-level reconciliation, IDoc retry handling, OEM portal feed format changes. ₹5-7 lakh per year sustained.
Z-report 2 — ZSAR_ASN_AGEING
Purpose: ASN-to-GRN ageing per OEM, with exception flags for ASNs not GRN-confirmed within the contractual window.
Source SAP tables: VBAK / VBAP / LIKP / LIPS (delivery), VBRK / VBRP (billing), MKPF (goods movements), plus OEM portal GRN export feeds.
Logic: join supplier-side ASN despatch records with OEM-side GRN confirmation, compute days-ageing per ASN, flag exceptions at thresholds (typically 3 / 5 / 7 days for short-haul OEMs).
Maintenance pattern: relatively stable. ₹4-5 lakh per year.
Z-report 3 — ZSAR_DEBIT_NOTE_DECOMP (the highest-maintenance Z-report)
Purpose: parse OEM payment advice, decompose short-pay residuals into reason-coded categories (FOMP, JIT shortage, quality reject, line-stop, tooling, technical service, transport), tie each debit to source invoice via claim ID, classify accept vs contest.
Source SAP tables: BSEG / BSID / BSAD (FI document items), BKPF (FI header), VBRK / VBRP (billing), WITH_ITEM (withholding tax), plus OEM payment advice feeds.
Logic: parse OEM-specific payment-advice format (e-Nagare for Maruti, TML SRM for Tata, M&M Supplier Portal for Mahindra, SupplyOn for Bosch), map reason codes to internal taxonomy, tie to source invoice via claim ID, output reason-classified debit register, calculate the running per-OEM FOMP account.
Why this forks per OEM: every OEM has a different debit reason code taxonomy (Maruti 80-100 codes, Tata 50-60, Mahindra 40-50), a different payment-advice format, a different debit-note number scheme. By year 2-3 of operations, this Z-report is typically forked into four parallel codebases. Cumulative maintenance: ₹8-12 lakh per year across the family.
See OEM short-pay handling auto component India for the underlying short-pay workflow that this Z-report serves.
Z-report 4 — ZSAR_RMPV_CLAIM
Purpose: compute RMPV (Raw-Material-Price-Variation) claim per part per period against external commodity index movement, output the supplementary invoice (upward) or Section 34 credit note (downward).
Source SAP tables: EKKO / EKPO (purchase agreement), MARC / MARA (material master), VBRK / VBRP (billing for quantity supplied), plus external commodity-index feed (JPC HR / CR coil, LME aluminium / copper / zinc, polymer / resin index).
Logic: pull index value per period from external feed, multiply by index coefficient (typically 0.7 or 0.8 — partial pass-through), multiply by part weight, multiply by quantity supplied in the period, output net RMPV claim. The claim posting then drops through SD-Billing as a supplementary invoice with HSN-tagged ledger.
Why this forks per OEM: every OEM’s RMPV formula differs — coefficient, lookback period, pass-through percentage, settlement frequency. Build typically runs ₹8-12 lakh per OEM customer. See RMPV calculation formula auto component India.
Z-report 5 — ZSAR_ITC04_GEN
Purpose: ITC-04 quarterly return generation including the multi-hop job-work cases that the standard SAP India Localisation Subcontracting module does not handle.
Source SAP tables: J_1IG family (India localisation), the subcontracting challan tables, plus a custom Z-table holding the multi-hop chain logic.
Logic: aggregate outbound challans (Table 4), inbound returns from job-worker (Table 5A), onward dispatch to another job-worker (Table 5B), lost / written off (Table 6), output the GSTN-acceptable JSON.
Maintenance pattern: moderate. ₹4-6 lakh per year. See ITC-04 filing auto component step-by-step India.
Z-report 6 — ZSAR_FREE_ISSUE_RECON
Purpose: reconcile OEM-supplied free-issue stock (steel coil, inserts, components shipped at no charge) against consumption-into-finished-part, with Section 143 deemed-supply exposure tracking.
Source SAP tables: MKPF / MSEG (material movements), MCHB (batch stocks), MARC (plant stocks), plus inbound Rule 55 challan register from the OEM.
Logic: net free-issue position per OEM per material per Rule 55 challan, Section 143 countdown clock (12 months for inputs, 3 years for capital goods), alerting at thresholds.
Maintenance: ₹4-5 lakh per year.
Z-report 7 — ZSAR_TONNAGE_BILL
Purpose: tonnage-rate billing reconciliation for product lines billed on weight-out-of-stamping rather than per-part-shipped (common for stamping suppliers).
Source SAP tables: VBRK / VBRP (billing), MARM (material units of measure), plus the weight-conversion master.
Logic: convert per-part billing to per-tonne reconciliation, identify under-billing or over-billing on weight basis.
Maintenance: ₹4-5 lakh per year.
Z-report 8 — ZSAR_TDS_SECTION_393 (Income Tax Act 2025 cross-era)
Purpose: split TDS deduction across Section 393(1)(a) code 1002 (contractor), Section 393(1)(k) code 1012 (purchase goods), Section 394 code 1071 (scrap TCS), Section 413 code 1062 (non-resident pay-leg), and reconcile cross-era transactions started under legacy 194C / 194Q / 206C(1) before 1 April 2026 and settled under new codes after.
Source SAP tables: WITH_ITEM (withholding tax line items), BSEG (FI document items), J_1IEWT family (extended withholding tax), plus the Form 168 challan register.
Logic: classify by payment code, reconcile against Form 168 challan deposits, output discrepancy register.
Maintenance: ₹5-7 lakh per year. See TDS payment code 1002 — Section 393(1)(a) contractor and TDS payment code 1012 — Section 393(1)(k) purchase goods.
Three-Way Match Exception Cost Calculator
Compare the cumulative annual ABAP maintenance run-rate across the Z-report family with the unified reconciliation tool replacement cost — surface the build-vs-buy break-even at a Tier-1 with three, four or five OEM customers on SAP S/4HANA.
Open the Three-Way Match Calculator →Worked example — ₹600 crore Tier-1 with 11 Z-reports
The Pune stamping Tier-1 introduced earlier:
Z-report inventory and annual maintenance
- ZSAR_CUM_DRIFT — ₹6 lakh
- ZSAR_ASN_AGEING — ₹4 lakh
- ZSAR_DEBIT_NOTE_DECOMP (4 forked codebases — Maruti / Tata / Mahindra / Bosch) — ₹11 lakh
- ZSAR_RMPV_CLAIM (per-OEM forks for 3 OEMs) — ₹10 lakh
- ZSAR_ITC04_GEN — ₹5 lakh
- ZSAR_FREE_ISSUE_RECON — ₹4 lakh
- ZSAR_TONNAGE_BILL — ₹4 lakh
- ZSAR_TDS_SECTION_393 — ₹6 lakh
- ZSAR_TOOLING_CAP — ₹4 lakh
- ZSAR_KLT_BIN_FLOAT — ₹4 lakh
- ZSAR_SUPP_INVOICE_RECON — ₹4 lakh
Total annual ABAP maintenance run-rate: ₹62 lakh, plus ₹6 lakh for SAP support-pack regression testing and Note-application impact across the Z-report family. Grand total: ₹68 lakh.
Build effort sunk to date: roughly ₹185 lakh over four years across initial builds, OEM-specific forks, format changes and incremental enhancements.
Rebuild backlog: the new ABAP lead estimates 9 months of effort to refactor the 11-report family into a cleaner architecture with shared utility functions, with no functional gain — purely a maintainability investment. Estimated cost: ₹70 lakh.
Build-vs-buy comparison
- Continue build: ₹68 lakh per year sustained, plus ₹70 lakh rebuild investment over 9 months; net 5-year cost ₹410 lakh, end-state unchanged.
- Buy companion product: 2-4 weeks implementation on AWS Mumbai, ongoing licence at industry-typical SaaS subscription, ABAP team redirected from Z-report maintenance to core SAP roadmap (Tax / S/4HANA upgrade / EWM). The Z-report family is decommissioned in tranches as the companion product takes over each stream.
The CTO’s recommendation to the CFO: halt the rebuild, do not commission new Z-reports, evaluate a companion product, decommission the Z-report family over a 12-month transition.
Tax overlay — the Section 393 / 394 / 413 effect on the Z-report family
The Income Tax Act 2025 effective from 1 April 2026 changed the TDS / TCS code framework that ZSAR_TDS_SECTION_393 implements. The cross-era reconciliation (legacy 194C / 194Q / 206C(1) before 1 April 2026 versus codes 1002 / 1012 / 1071 / 1062 after) is handled in the Z-report through parallel ledger logic with the cut-over date governing which code set applies. Real-world maintenance: the Income Tax Department’s clarifications and code-table updates through FY 25-26 and FY 26-27 each trigger Z-report maintenance cycles of 1-2 person-weeks. SAP’s standard withholding tax module handles the codes through configuration but the cross-era reconciliation as a standing exception is left to the Z-report.
GST law (Section 17(5), Section 34, Section 143, Rule 37, Rule 43, Rule 55) is unchanged by the Income Tax Act 2025. The ZSAR_FREE_ISSUE_RECON Z-report continues to handle Section 143 exposure tracking as before. The Section 34 GST credit-note calendar (30-November-of-next-FY cutoff) and Rule 37 ITC reversal ageing are typically tracked through additional small Z-reports or extensions to the debit-decomposition Z-report.
Where this leaves a Tier-1 on SAP S/4HANA
The Z-report family is unavoidable in the first 12-18 months — every Tier-1 on SAP needs at minimum CUM drift, ASN ageing, debit decomposition, RMPV claim and ITC-04 generation to operate. The question is whether the family expands to 11-12 reports and forks per OEM, or whether the build is capped at the irreducible minimum and the standing-exception streams move to a companion product. The economics break around OEM customer number three; the rebuild-backlog estimate becomes the trigger event for the build-vs-buy reconsideration.
What automated reconciliation changes for an SAP Tier-1
Purpose-built auto-component reconciliation software India consumes SAP standard extracts (IDoc DELFOR / DESADV / INVOIC, scheduled custom report exports, file drops via SFTP) and runs the standing-exception streams as continuous reconciliations. TransactIG’s auto-component industry preset covers CUM drift, ASN ageing, debit-note decomposition (per OEM payment-advice format), RMPV claim, ITC-04 multi-hop, free-issue stock with Section 143 exposure, tooling cap monitor and KLT bin float — all the streams covered by the Z-report family. Customer outcomes include match-rate improvement from 51% to 88% and exception rates moving into the sub-15% band. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022). For the procurement-side three-way match see three-way matching software India.
Continue reading
Sibling articles in the auto-component cluster:
- SAP scheduling agreement reconciliation auto India
- OEM short-pay handling auto component India
- ITC-04 filing auto component step-by-step India
Up the chain: