What is SAP FI_DOCUMNT?
FI_DOCUMNT is the SAP archiving object for financial accounting documents, covering BKPF, BSEG, ACDOCA and related tables.
FI_DOCUMNT is the SAP archiving object for financial accounting documents, archiving headers in BKPF, line items in BSEG and, in S/4HANA, matching ACDOCA entries. Only cleared documents past their residence times are archived, controlled by account type life in OBR7 and document type life in OBR8.
How FI_DOCUMNT works
FI_DOCUMNT runs through SARA in three main steps. The write program (FI_DOCUMNT_WRI) checks each document against residence times and clearing status and writes archivable ones to archive files. The delete program (FI_DOCUMNT_DEL) removes them from the database after reading the file back. Postprocessing (FI_DOCUMNT_PST) cleans up secondary index entries.
A document is archivable only when every line item is cleared and both minimum lives have passed. Open items, recurring entry originals and documents in blocked periods stay in the database.
- Tables archived: BKPF, BSEG, related tax and withholding data, and ACDOCA entries in S/4HANA.
- Read access: FB03 and line item reports via archive infostructures in SARI.
How to run FI_DOCUMNT archiving
- Set account type life in OBR7 per company code and account range.
- Set document type life in OBR8 per company code and document type.
- If tax authorities require extracts, run DART (FTW1A) before archiving, where used.
- In SARA, enter FI_DOCUMNT, create a write variant by company code and fiscal year and run test mode.
- Review the log for non-archivable documents and their reasons.
- Run production write, then delete, then postprocessing.
- Activate and build an FI_DOCUMNT infostructure in SARI for FB03 access.
Run during low posting load. Users need S_ARCHIVE for FI_DOCUMNT.
Key parameters
| Parameter or field | What it controls | Recommended setting or note |
|---|---|---|
| Account type life (OBR7) | Minimum age by account type | Keep at least the open audit years online |
| Document type life (OBR8) | Minimum age by document type | Review recurring and sample document types |
| Company code / fiscal year | Run scope | One company code per run is easier to reconcile |
| Test mode | Simulation | Always before production |
| Archive infostructure | Read access after deletion | Build before deletion |
FI_DOCUMNT vs related objects
| Object | Purpose | When to use it | Status |
|---|---|---|---|
| FI_DOCUMNT | FI document archiving | Cleared FI documents | Current |
| FI_TF_GLA | GL transaction figures | Totals archiving in ECC | Check release |
| SAP ILM | Retention and destruction | Regulated data | Current |
| DART | Tax audit data extracts | Before archiving, where required | Check release |
| MM_MATBEL | Material documents | Linked inventory postings | Current |
Common issues and troubleshooting
Why are FI documents not archived by FI_DOCUMNT?
The most common reasons are open items, residence times not met in OBR7 or OBR8, or the fiscal year excluded from the variant. The write log names the reason per document.
Why does FB03 not find an archived document?
No FI_DOCUMNT infostructure is active and built. Activate it in SARI and fill it for existing archive files.
Why is the delete run slow?
Large index fragmentation and missing statistics. Update statistics and run delete jobs in parallel by company code where supported.
FI_DOCUMNT in S/4HANA migration and decommissioning
FI_DOCUMNT archive files are statutory records. They hold the evidence behind closed years and fall under the longest retention rules in most jurisdictions, often eight to ten years for books of account.
The risk is that archive files depend on the system that wrote them. Retire ECC, and FB03 and infostructures go with it, leaving ADK files few tools can read. Plan read access before shutdown and archive closed years before conversion to cut ACDOCA load. Archon covers this in its SAP ECC approach.
- Inventory existing FI_DOCUMNT archive files and their years.
- Archive remaining closed years before conversion.
- Keep DART or equivalent tax extracts where required.
- Ensure archived documents stay searchable without ECC.
- Record retention end dates per company code.
Frequently asked questions
What is FI_DOCUMNT in SAP?
FI_DOCUMNT is the SAP archiving object for financial accounting documents. It archives document headers from BKPF, line items from BSEG and, in S/4HANA, related ACDOCA entries. Documents must be fully cleared and past their residence times, set in OBR7 and OBR8, before they qualify.
What are OBR7 and OBR8 used for?
OBR7 sets account type life, the minimum time documents must stay online for each account type and account range. OBR8 sets document type life, the minimum time for each document type. FI_DOCUMNT archives a document only after both periods have passed.
Can FI_DOCUMNT archive open items?
No. Any document with an open line item stays in the database regardless of age. Clear or reverse the open item first, then archive in a later run. The write log lists documents rejected because of open items. Clearing old open items is often a prerequisite project.
How do I read FI_DOCUMNT archives after decommissioning?
Inside SAP, FB03 reads archived documents through SARI infostructures, but that path disappears with the system. Before retirement, move archived documents into a platform that can search and display them independently, with headers, line items and links intact. Test that path with auditors first.
Further reading
See Also
Ready to put this into practice?
See how Archon helps organizations with compliant archiving and legacy decommissioning.