Phase 1 reference material · Mid-level Business Analyst · Read before starting Phase 2
SAP
SAP Fiori Launchpad · Vinexa Retail GroupVCHEN (S.Chen) ▾
Sales & Distribution (SD)
📋
Create Sales Order
VA01
2,847
Orders this month
📦
Manage Outbound Deliveries
VL02N
2,304
Dispatched
🧾
Create Billing Document
VF01
543
⚠ Pending billing
⚠️
Billing Due List
VF04
543
Overdue
Finance & Accounting (FI)
💳
Post Incoming Payments
F-28
£614.8k
Collected this month
🔴
Open Items — Accounts Receivable
FBL5N
£156.4k
Outstanding (this month)
📊
Display Customer Balances
FD10N
AR
Accounts Receivable
📝
G/L Account Document
FB03
BSEG
Accounting segment
🎓 What you're looking at: This is the SAP Fiori Launchpad — the home screen for SAP S/4HANA users. Each tile launches a transaction. The red tiles show where Vinexa's problem is visible right now: 543 billing documents are pending, and £156,400 is sitting as uncollected open items in FI. Your job is to find out WHY.
SAP
Order-to-Cash Process Flow · Vinexa Retail GroupReference Only
📊 Vinexa O2C End-to-End Flow — SAP S/4HANA
🛒
Customer Order
VA01
VBAK / VBAP
SD
→
✅
Credit Check + Confirm
VA02
VBAK-CMGST
SD
→
🚚
Delivery + Goods Issue
VL02N
LIKP / LIPS
MM
→
🧾
Billing Document
VF01
VBRK / VBRP
SD
⚠→
⚙️
SD → FI Handoff
VF02
CONFIG_GAP ⚠
FI
→
💳
Payment Processing
F-28
BSEG_NULL ⚠
FI
→
📊
Financial Posting
FB03
BKPF / BSEG
FI
⚠️ WHERE THE PROBLEM IS: The flashing stages above show the two failure points. Billing documents are being created in SD (VBRK) but the SD→FI handoff is producing CONFIG_GAP errors — the parameters passed to FI are incorrect. This causes BSEG_NULL entries in FI (null payment amounts), meaning the payment never posts. This has been happening since Week 9.
📖 External reference: For real SAP screenshots of this flow, see the SAP Community tutorial: blogs.sap.com/2020/03/02/step-by-step-to-run-a-simple-order-to-cash-process — this shows real VA01, VF01, and release-to-FI screens with photos from a live SAP S/4HANA system.
SAP
Standard Order — Display: VA03 · Order ORD-001095VCHENBA ▾
Home › Sales › Sales Orders › ORD-001095
Standard Order ORD-001095 FAILED
VBAK-VBELN: 0000001095 · Created: 05 Dec 2025 · Week 9
▼ Header Data (VBAK)
Order Number (VBELN)
0000001095
Customer (KUNNR)
CUST-0109
Order Date (AUDAT)
05.12.2025
Net Value (NETWR)
£73.11
Sales Channel
WEB
Order Status
FAILED — Payment not posted
Sales Org (VKORG)
VNX-UK
Distribution Channel
10 — Online Retail
Week
WK-09
▼ Item Overview (VBAP)
#
Material (MATNR)
Description
Qty
Unit Price
Net Value
Status
10
VNX-WOM-JKT-042
Women's Quilted Jacket — Navy
1
£49.99
£49.99
FAIL
20
VNX-ACC-SCF-017
Wool Scarf — Camel
1
£23.12
£23.12
FAIL
⚠ System message: Billing document created (VBRK-0000093471) but FI payment posting failed — CONFIG_GAP error. SD→FI interface parameter mismatch. See operational report ESC_IT log.
🎓 What you're looking at: This is a Sales Order record — the VBAK table stores the header (one row per order). The VBAP table stores the items (one row per line item). Notice the status bar at the bottom — the billing document WAS created (VBRK), but the FI payment posting FAILED with a CONFIG_GAP error. This is the problem. The order exists. The billing doc exists. But the money never arrived.
VBRK record · Sales Order ref: ORD-001095 · 05 Dec 2025
▼ Billing Header (VBRK)
Billing Doc (VBELN)
0000093471
Billing Type (FKART)
F2 — Invoice
Billing Date (FKDAT)
05.12.2025
Net Value (NETWR)
£73.11
Payer Customer
CUST-0109
Posting Status (RFBSK)
C — Not transferred to FI
▼ FI Accounting Document (BSEG) — FAILED
Accounting Doc (BELNR)
NOT CREATED
Payment Amount (WRBTR)
NULL — BSEG_NULL error
Error Code
CONFIG_GAP · SD→FI
G/L Account (HKONT)
UNDETERMINED
Reconciliation Account
MISSING — VKOA not maintained
PII Flag
Y — ICO retention applies
⚠ Release to FI Accounting failed: G/L account cannot be determined (VKOA). CONFIG_GAP — SD→FI interface parameter missing since patch 04-Oct-2025. Manual ESC_IT raised. BSEG entry not created. Payment NOT collected. Revenue NOT recognised.
⚠️ This is the failure point: The billing document (VBRK) was created correctly in SD. But when it tried to release to FI Accounting, it failed — because the SD→FI interface configuration is missing the G/L account determination rules (VKOA). This means BSEG never gets a record, no payment posts, and Vinexa's revenue disappears. The CONFIG_GAP and BSEG_NULL codes in your operational_report.csv are THIS error, happening hundreds of times per week.
SAP
SAP Table Reference — Vinexa O2C · Data Dictionary (SE11)Reference
📋 How to read this: Each card below shows a real SAP database table used in the O2C process. The columns on the left (FNAME) are the real SAP field names. On the right are the equivalent columns in Vinexa's datasets. Use this mapping when you write SQL queries — your vinexa_orders.csv mimics VBAK/VBAP. Your vinexa_payments.csv mimics BSEG.
VBAK
Sales Order Header
SD
VBELN
Sales Order Number
KEY
KUNNR
Customer Number
CHAR
AUDAT
Order Date
DATS
NETWR
Net Order Value
CURR
CMGST
Credit Check Status
CHAR
📎 Vinexa equivalent: vinexa_orders.csv — ord_id, cust_id, ord_dt, ord_val, status
VBRK
Billing Document Header
SD
VBELN
Billing Document Number
KEY
FKART
Billing Type (F2=Invoice)
CHAR
FKDAT
Billing Date
DATS
NETWR
Net Billing Value
CURR
RFBSK
Posting Status to FI
CHAR
📎 Vinexa equivalent: referenced in vinexa_payments.csv via ord_ref
BSEG
Accounting Document Segment
FI
BELNR
Accounting Document Number
KEY
HKONT
G/L Account
CHAR
WRBTR
Amount in Document Currency
CURR
ZLSCH
Payment Method
CHAR
AUGDT
Clearing Date
DATS
⚠ Vinexa issue: BSEG_NULL — WRBTR = NULL because HKONT cannot be determined (CONFIG_GAP). Equivalent in vinexa_payments.csv: pay_status = FAIL, fail_cd = BSEG_NULL
VBAP
Sales Order Item
SD
VBELN
Sales Order Number (ref VBAK)
KEY
POSNR
Item Number (10, 20, 30…)
KEY
MATNR
Material Number (SKU)
CHAR
KWMENG
Confirmed Order Quantity
QUAN
NETWR
Net Value of Item
CURR
📎 Vinexa equivalent: item_ct in orders.csv counts VBAP rows per order