● CASE STUDY / SAP SD/FI · ABAP · INTERCOMPANY · E-FATURA · PRICING · MENDERES (AKÇA HOLDING)

Intercompany Reconciliation & Control Application.

A SAP SD/FI control application that reconciles OA subcontracting, OA export and Menderes settlement flows — linking delivery, billing, accounting document, e-invoice and pricing conditions into a single intercompany reconciliation ALV. Three document chains. One row.

#	Dlv	Item	Batch	Material	Qty	Invoice	AccDoc	E-Invoice	OA Dlv	Customer	Invoice	Incoterms	FOB	Freight	Total	Mahsup Inv	AccDoc	E-Invoice	Qty	FOB Unit	Total
	OA FASON BLOCK								OA EXPORT BLOCK							MENDERES MAHSUP BLOCK
1	800004521	10	MT240312A	000000201887	2.400 M	9010042311	100000841	EFT-2024-0831	800009874	501277-IKEA	9010048820	CFR	28.160,00	1.200,00	29.360,00	9010051144	200000312	EFT-2024-1102	2.400 M	11,73	28.160,00
2	800004618	10	MT240319B	000000204530	1.850 M	9010042488	100000902	EFT-2024-0847	800009941	501285-MÜŞTERI	9010048975	FOB	23.125,00	—	23.125,00	9010051220	200000388	EFT-2024-1118	1.850 M	12,50	23.125,00
3	800004702	10	MT240401C	000000198741	3.100 M	9010042699	100001055	pending...	800010114	501292-AKÇA	9010049201	CIF	37.820,00	1.550,00	39.890,00	—	—	—	—	—	OPEN

SAP GUI · Intercompany Reconciliation ALV — three-block document chain per row (illustrative)

Role: SAP Developer
Domain: SD / FI · Intercompany
Program: ZSD_049
Manual Entry: ZSD_049_T_INTC_M
Scope: 3-flow reconciliation

01OVERVIEW

Three document chains. One reconciliation row.

SAP ABAP ALV Grid SD / FI E-Fatura Pricing Conditions FOB Calculation Intercompany

The Intercompany Reconciliation & Control Report is a custom SAP SD/FI application developed to control the full document chain between OA subcontracting (Fason), OA export and Menderes settlement processes in a single ALV screen. Each report row represents one complete intercompany event — from the subcontracting delivery to the final settlement invoice.

The report starts from ZF30 subcontracting invoices and their completed deliveries. Using batch and material information from the subcontracting delivery as the matching key, it locates the corresponding OA export deliveries. From those deliveries it reads the linked billing documents — separating IV billing-type documents as the Menderes settlement side and non-ZF30 cancelled invoices as the OA export side. E-invoice records, accounting documents, pricing conditions, freight, insurance and discount values are then read to complete each row.

The result is a single operational view where a user can verify subcontracting delivery quantities, export invoice amounts, settlement matching, e-invoice generation and FOB accuracy — without navigating between VL03N, VF03 and FB03 separately.

02THE CHALLENGE

Fifteen control questions. Scattered across SAP.

For a single intercompany transaction, an operations user needed answers to these questions — from different transactions, tables and modules. No single SAP screen provided them together.

// CONTROL QUESTIONS BEFORE THIS REPORT

Which delivery is linked to the subcontracting invoice?

Is the subcontracting e-invoice generated?

Did the same batch/material reach OA export delivery?

Is the OA export invoice created?

Does the OA invoice have an accounting document?

Is the OA e-invoice number and date available?

Has the customs clearance date been recorded?

Are the OA freight and insurance amounts correct?

Is the FOB value calculated correctly?

Is the Menderes settlement invoice created?

Does the settlement have an accounting document?

Is the settlement e-invoice available?

Are the settlement FOB unit price and discount correct?

Do fason, OA and settlement quantities match?

Are the currencies consistent across all three sides?

The problem

VL03N, VF03, FB03 — plus e-invoice tables, pricing conditions, batch data.

All answers existed in SAP. But fragmented across different transactions, modules and custom tables with no joined view.

The solution

One ALV row = the full lifecycle of one intercompany transaction.

All fifteen control questions answered in a single screen, with hotspot navigation to VL03N, VF03 and FB03 when needed.

03DOCUMENT FLOW ARCHITECTURE

How the report builds each row.

STEP 01

ZF30 Fason Invoices

Completed deliveries + billing documents as starting anchor

→

STEP 02

Batch + Material Match

Subcontracting delivery batch & material = reconciliation key

→

STEP 03

OA Export Delivery

Same batch/material locates the corresponding OA delivery

→

STEP 04

Billing Type Split

IV → Menderes settlement · ≠ZF30, active → OA export invoice

→

STEPS 05–07

Enrich + Calculate

E-invoice, accounting doc, pricing conditions (ZNET, ZN01, ZSIG, ZI08), FOB

→

OUTPUT

Reconciliation ALV

Three-block row: Fason | OA Export | Mahsup

ZF30 subcontracting invoices and deliveries are the starting anchor.

The report reads billing documents of type ZF30 with completed subcontracting deliveries. These become the base rows — each representing a subcontracting shipment to be reconciled.

Batch and material from the subcontracting delivery are the matching key.

The batch number and material from the fason delivery line are used to locate OA export deliveries. This cross-delivery batch matching is the core reconciliation logic.

OA export deliveries are found using that key.

OA-side deliveries sharing the same batch and material reference are matched to each fason row, establishing the export leg of the document chain.

Billing documents from OA deliveries are split by type.

IV billing-type invoices go to the Menderes settlement column group. Non-ZF30 active (non-cancelled) invoices become the OA export invoice. The billing type logic ensures each column is populated with the correct document.

IV → Menderes Mahsup · ≠ZF30 + not reversed → OA Export

E-invoice and accounting documents are retrieved for all three sides.

E-invoice numbers and dates are read for subcontracting, OA export and settlement invoices and their accounting documents. The e-invoice table is joined to billing and accounting document numbers.

Pricing conditions populate freight, insurance, unit price and discount.

Condition types ZNET, ZN01, ZSIG and ZI08 are read from the condition records linked to each invoice. Unit prices, total amounts, freight and insurance values are surfaced per row.

ZNET · ZN01 (freight) · ZSIG (insurance) · ZI08 (discount)

OA FOB amount is calculated by subtracting freight and insurance.

FOB = OA total amount − freight (ZN01) − insurance (ZSIG). This derived field gives users a directly comparable FOB value without manual calculation. Settlement side FOB unit price and discount are shown for cross-check.

Manual exception records are merged into the main output.

Records maintained via the manual entry program (ZSD_049_T_INTC_M table) are included alongside automatically matched rows so the full reconciliation picture is available in one view.

04THREE COLUMN BLOCKS

Each block answers a different business question.

A single ALV row holds three contiguous column families. Together they let a user audit the full intercompany document lifecycle without leaving the screen.

OA Fason Block

Origin of the transaction. "Where did this material come from and what document was raised?"

Subcontracting delivery & item
Batch number
Material & material description
Quantity & unit
Subcontracting invoice
Accounting document
E-invoice number
E-invoice date
Unit price
Total amount
Currency

"Was the subcontracting invoice posted and is the e-invoice generated?"

OA Export Block

Export leg. "How did the material leave, to whom, at what value and terms?"

OA export delivery
Batch number (cross-check)
Incoterms
Material & quantity
Customer & customer name
Export invoice
Accounting document
E-invoice number & date
Customs clearance date
Unit price
Freight (ZN01)
Insurance (ZSIG)
FOB amount (Total − Freight − Insurance)
Total amount
Currency

"Is FOB correct? Is the e-invoice present? Has clearance been recorded?"

Menderes Mahsup Block

Group settlement. "Is the intercompany offset correctly created and does it agree?"

Settlement invoice
Accounting document
E-invoice number & date
Material & quantity
Unit
FOB unit price
Discount (ZI08)
Total amount
Currency

"Does the settlement total agree with the OA FOB? Is the discount as expected?"

05SCOPE & IMPACT

What this replaces.

Separate document flows consolidated into one ALV screen

15+

Business control questions answered per row from a single view

ALV column blocks — Fason, OA Export, Menderes Settlement

Programs — main reconciliation report + manual exception maintenance

06MANUAL EXCEPTION MANAGEMENT

Real processes don't always auto-match.

Automatic batch-and-material matching covers the majority of cases. But in real enterprise operations, edge cases always exist: retroactive corrections, system gaps, cross-period transactions. A separate exception maintenance program handles these.

// MANUAL EXCEPTION MAINTENANCE · ZSD_049_T_INTC_M

Editable ALV exception screen — integrated into the main report.

Records that cannot be matched automatically are maintained via a dedicated editable ALV program. The program reads the ZSD_049_T_INTC_M table, presents it as an inline-editable grid, and persists user changes back to the table on save.

The main reconciliation report includes these manual records alongside the automatically matched rows — so the operational view is always complete, regardless of whether a record was system-matched or manually maintained.

→ Reads ZSD_049_T_INTC_M and displays as an editable ALV grid.

→ Users can add, edit and save intercompany exception records directly in SAP.

→ Main report merges manual and automatic records into a unified reconciliation view.

→ Exception management turns the report from a read-only view into an operational tool.

07TECHNICAL CONTRIBUTIONS

What was built.

Custom SAP SD/FI intercompany reconciliation report — full ZSD_049 program with three-block selection screen for OA Fason, OA Export and Menderes settlement filters.
Batch and material based cross-delivery matching — subcontracting delivery batch/material used as reconciliation key to locate OA export deliveries.
Billing type split logic — IV-type invoices routed to Menderes settlement block; non-ZF30 active invoices to OA export block from the same delivery.
E-invoice enrichment for all three document sides — e-invoice numbers and dates read for subcontracting, OA export and settlement documents via accounting document join.
Pricing condition read — ZNET, ZN01, ZSIG, ZI08 — unit price, freight, insurance and discount values pulled from condition records per invoice.
FOB calculation on the OA export side — FOB = OA total − freight (ZN01) − insurance (ZSIG); settlement FOB unit price and discount exposed for cross-check.
Document hotspot navigation — VL03N for deliveries, VF03 for invoices, FB03 for accounting documents accessible directly from ALV rows.
Manual exception maintenance program — editable ALV over ZSD_049_T_INTC_M table; manual records integrated into the main reconciliation output.
ALV field catalog grouped by three-block layout — Fason, OA Export and Menderes Settlement sections with column-level grouping and ALV layout variant support.
Three-block selection screen — separate filter areas for subcontracting billing, OA export delivery and settlement date ranges enabling targeted reconciliation runs.

"I built a SAP SD/FI intercompany reconciliation application that links subcontracting, export and settlement documents through batch and material matching, enriches them with e-invoice, accounting and pricing data, and supports manual exception handling for unmatched cases."

— Fatih Şengül · SAP SD/FI Developer · Menderes Tekstil (Akça Holding)