Processing Intraday Bank Statements in SAP via FEB_FILE_HANDLING Without Postings
FEB_FILE_HANDLING allows you to import intraday bank statements into application 0004 without generating postings in FI. This updates cash management data through payment advices, solving the "black box" problem for intraday balance monitoring.
Activating this scheme requires setting the "Account Balance Statement" flag in the posting parameters. For intraday files, the X_INTRADAY "Bank Statement" flag is automatically set in the logical file bank information.
The process includes:
- Parsing the file into logical statements with bank data identification.
- Saving to application 0004 without FI postings.
- Creating payment advices to update financial disposition.
Configuring Disposition Types for Advices
There are two options for creating advices:
- All advices with a single disposition type—activated by the "Create Financial Disposition Advice" flag in the posting parameters. The type is set separately.
- Disposition types based on external transaction codes—without the flag, with mapping in the "Main Parameters of Electronic Bank Statement" configuration.
The second option is preferable for detailed breakdown: receipts (BC), statement payments (BD), bank charges (BW). This prevents duplication of outgoing payments from payment programs (B1) and statements (BD).
Example of duplication in the table:
| Disposition Level | Overdue | Today | Comment |
|--------------------|--------------|---------|-------------|
| Opening Balance | - | 100,000 | |
| B1 Outgoing Payments | 0 | -30,000 | |
| BC Receipts from Statements | 0 | 20,000 | |
| BD Statement Payments | 0 | -27,000 | |
| BW Bank Charges | 0 | -1,000 | |
| F0 Balance | 100,000 | 0 | |
| Closing Balance | 100,000 | 62,000 | Understated due to duplication |
Correct estimates: 89,000 (only B1) or 92,000 (only BD). The difference represents payments not yet confirmed by the bank.
Scenario for Importing Two Intraday Statements
Intraday identification is based on file attributes: matching creation, start, and end dates. In the "Client -> 1C" format, the external code equivalent is "DocumentSection" ("Payment Order" or "Bank Order").
Step 1: Import the First Statement
Run FEB_FILE_HANDLING. File selection identifies intraday by dates. The X_INTRADAY flag is set automatically. The message log confirms import without FI postings.
Step 2: Viewing Items
Transaction FEB_FEB_BSPROC/FEBAN does not support application 0004. Use QUE queries on FEB* tables to list items. Partner identification and purpose interpretation are visible, but advices are created before this stage.
Step 3: Analyzing Advices
Transaction FF65. Advices contain statement date/number, short key. Disposition types correspond to transaction codes.
Post-Processing and Visualization Features
- Post-processing in FEBAN is limited to application 0001; for 0004, use QUE queries.
- Visualization: FF7AN or Cash Flow Analyzer. Turnovers at BD/BW/B1 levels accurately reflect intraday changes.
Recommendation: Use the scenario without the "Financial Disposition Advice" flag for precise operation separation and minimizing duplicates in cash position.
Key Points
- "Account Balance Statement" flag + X_INTRADAY save statements to 0004 without FI postings.
- Mapping external codes to disposition types (BC/BD/BW) prevents B1/BD duplication.
- Intraday is determined by file dates; re-import the next day is treated as final.
- QUE queries for viewing 0004 items; FF65 for advices.
- Two balance estimates: based on payments (89k) or statements (92k).
— Editorial Team
No comments yet.