SAP TCodes · LessonBy Anitha M, SAP Trainer, 13 yrs · Published · SAP S/4HANA 2023 · all levels
FB50
FB50 is the SAP transaction code for Post G/L Document (FI). It posts a general-ledger document (the enjoy single-screen transaction), used for direct G/L journal entries such as accruals and adjustments.
Quick answer
FB50 posts a general-ledger document (the enjoy single-screen transaction), used for direct G/L journal entries such as accruals and adjustments.
Key takeaways
- Company code, document date, posting date.
- G/L account lines with debit/credit amounts.
- Cost assignment (cost center/order) for P&L accounts.
- Watch out: Using the wrong variant (e.g. create vs change vs display).
Purpose
It posts a general-ledger document (the enjoy single-screen transaction), used for direct G/L journal entries such as accruals and adjustments.
Key fields and screen
- Company code, document date, posting date.
- G/L account lines with debit/credit amounts.
- Cost assignment (cost center/order) for P&L accounts.
- Document type and text.
Tips
- Debits must equal credits (balanced document).
- Use for manual G/L entries; sub-ledger postings use FB60/FB70.
- Save as held/parked if not ready to post.
Common errors
- "Posting period not open", closed period for the posting date.
- Unbalanced document.
- Missing cost assignment for a P&L account.
Common pitfalls
- Using the wrong variant (e.g. create vs change vs display).
- Missing prerequisite master data or config.
- Not checking the resulting document/postings.
Practice challenge
+0 XPStreak ×0
Question 1 of 2
Which statement is true of FB50?
Frequently asked questions
What does FB50 stand for in SAP?
FB50 is the SAP transaction code for Post G/L Document (FI). It posts a general-ledger document (the enjoy single-screen transaction), used for direct G/L journal entries such as accruals and adjustments.
Which related transactions work alongside FB50?
Debits must equal credits (balanced document). Use for manual G/L entries; sub-ledger postings use FB60/FB70. Save as held/parked if not ready to post.
What is another point to note about FB50?
Company code, document date, posting date. G/L account lines with debit/credit amounts. Cost assignment (cost center/order) for P&L accounts.
What tends to go wrong with FB50?
Using the wrong variant (e.g. create vs change vs display). Missing prerequisite master data or config. Not checking the resulting document/postings.