SAP Fix: Account Determination for Entry LNER EIN Not Possible
"Account determination for entry LNER EIN not possible" occurs when SAP cannot find the appropriate G/L (Purchase) account for the specified combination of valuation class and transaction key EIN during a goods receipt. This guide covers the exact fix using FS00 and OMWB, then goes deeper into what transaction key EIN and Purchase Account Management actually are, how EIN differs from freight/delivery cost keys and from WRX, a real business scenario, and a full prevention checklist.
✅ Common Error Message
"Account determination for entry LNER EIN not possible" in SAP occurs when the system cannot find the appropriate General Ledger (GL) purchase account for the specified combination of valuation class and transaction key (EIN) during inventory-related postings. This relates specifically to Purchase Account Management, an optional statutory posting requirement activated for certain company codes/countries during the Goods Receipt (GR) process.
🔧 Solution 1: Check or Create the Purchase Account G/L Account
Solution -Tcode: first check whether the G/L account exists -FS00.
Create G/L: Packing Purchase A/C -500099.
🔧 Solution 2: OMWB -Configure the EIN Account Mapping
Solution -Tcode: OMWB
Follow path: SPRO → Materials Management → Valuation and Account Assignment → Account Determination → Account Determination Without Wizard → Configure Automatic Postings -OMWB.
Select Account Assignment.
Check the material master valuation class and related settings.
Determine which combination of chart of accounts, valuation area, and valuation class needs to be mapped for EIN in OBYC.
Example Configuration in OBYC/OMWB
- Transaction Key -EIN, Valuation Class 3000 -Raw Material
- Transaction Key -EIN, Valuation Class 3050 -Packaging
Select Chart of Account -LNER, then select EIN -Purchase Account.
Example: Select Valuation Class -3000, Debit -500099, Credit -500099.
Example: Select Valuation Class -3050, Debit -500099, Credit -500099.
Note: the original configuration notes for this page referenced "transaction key EIC" and "WRX – GR/IR Clearing A/C" in a couple of spots -these were copy artifacts from a different account determination example. The screens and account (500099, chart of accounts LNER) shown here are for transaction key EIN – Purchase Account, not EIC or WRX.
Save.
🔍 What Purchase Account Management and Transaction Key EIN Actually Do
Purchase Account Management is an optional SAP FI/MM feature, activated per company code, that satisfies a statutory accounting requirement present in certain countries' commercial law (historically including France, Belgium, Italy, Portugal, and some others, and configurable for any company code that needs it). Where it's active, every goods receipt posts an additional entry -separate from the normal inventory debit and GR/IR credit -recording the value of the purchase in a dedicated Purchase Account in the profit and loss statement, alongside a corresponding offsetting entry.
Transaction key EIN specifically determines the Purchase Account itself (the debit side of this additional posting), while a related transaction key, EKG, determines the offsetting entry account. This dual-entry approach exists so that a company's purchase activity is visible directly in P&L reporting for statutory purposes, in addition to the standard balance sheet inventory movement that every SAP system already tracks regardless of whether Purchase Account Management is active.
📑 EIN vs Freight/Delivery Cost Keys vs WRX
Because several transaction keys can all be relevant on the same goods receipt, it's worth being clear about what each one actually represents -this is exactly the distinction the original page's copy-paste artifacts blurred.
| Transaction Key | Purpose | When It Applies |
|---|---|---|
| EIN | Purchase Account (statutory P&L posting) | Only when Purchase Account Management is activated for the company code |
| EKG | Offsetting entry for the Purchase Account | Paired with EIN whenever Purchase Account Management posts |
| WRX | GR/IR clearing account | Every standard goods receipt against a purchase order, regardless of Purchase Account Management status |
| FR1–FR4 | Freight and delivery cost clearing accounts | Only when the purchase order includes delivery cost conditions (freight, customs, etc.) |
| BSX | Inventory (balance sheet) account | Every goods receipt that changes stock value |
Notice that EIN has nothing to do with freight or delivery costs despite the original meta-description's framing -that's a genuinely separate concept covered by the FR1–FR4 keys. EIN only comes into play at all if your company code has Purchase Account Management switched on; if it isn't active, this specific error simply wouldn't occur, since EIN wouldn't be evaluated during the goods receipt in the first place.
💼 Real-World Scenario: Rolling Out a New Country Company Code
Pooja Mishra, an SAP FI consultant, was supporting a client expanding operations into a new country where local commercial law requires Purchase Account Management. The client's existing company codes elsewhere didn't have this feature active, so the MM configuration team initially copied OBYC/OMWB settings from an existing company code, unaware that Purchase Account Management introduced two additional transaction keys (EIN and EKG) that needed their own mapping entirely separate from what had been copied.
When the new country's warehouse team processed their first goods receipt, they hit this exact LNER EIN error. Pooja Mishraexplained that Purchase Account Management wasn't something the source company code used at all, so its OBYC configuration had never needed EIN/EKG mappings -there was nothing to copy in the first place. She walked the team through creating the Purchase Account G/L account in FS00 and mapping it for each relevant valuation class in OMWB, following the same pattern as this guide. Once complete, goods receipts for the new company code posted correctly, generating both the standard inventory/GR-IR entries and the additional statutory Purchase Account entry required locally.
❗ Common Mistakes When Fixing This Error
- Assuming EIN relates to freight or delivery costs, and looking in the wrong configuration area (FR1–FR4) instead of Purchase Account Management.
- Copying OBYC configuration from a company code that doesn't use Purchase Account Management, missing EIN/EKG mappings entirely for a new company code that does.
- Configuring EIN without also configuring its paired offsetting key, EKG, leaving the posting incomplete.
- Not confirming with local finance/legal teams whether Purchase Account Management is genuinely required for a new country before spending time configuring it.
- Reusing an inappropriate G/L account for the Purchase Account rather than a dedicated one aligned with statutory reporting requirements.
📈 Troubleshooting Decision Tree
- Confirm Purchase Account Management is intentionally active for the company code in question (check with FI/legal if unsure).
- Confirm the Purchase Account G/L exists in FS00, creating it if necessary.
- Go to OMWB and check EIN mapping for the specific chart of accounts and valuation class.
- Also check EKG mapping (the paired offsetting entry key), since EIN alone is usually incomplete.
- Retest the goods receipt to confirm both the standard postings and the Purchase Account entry post correctly.
📋 Related SAP Transactions
| Transaction | Purpose |
|---|---|
| FS00 | Create or display a G/L account, including the Purchase Account. |
| OMWB | Configure automatic account determination, including EIN and EKG for Purchase Account Management. |
| OBYC | Configure automatic account determination for all transaction keys directly. |
| OBY6 | Company code global parameters, including whether Purchase Account Management is activated. |
| MIGO | Post the goods receipt that triggers EIN/EKG postings when Purchase Account Management is active. |
| MIRO | Post the vendor invoice, part of the same purchase-to-pay cycle. |
🎓 Interview-Style Questions and Answers
Q: What is the purpose of Purchase Account Management in SAP?
It satisfies a statutory accounting requirement in certain countries by posting an additional P&L entry recording the value of purchases, alongside the standard balance sheet inventory posting, using transaction keys EIN (Purchase Account) and EKG (offsetting entry).
Q: Why would EIN account determination fail on a newly created company code but not on existing ones?
Because Purchase Account Management is activated per company code, and if it wasn't active on existing company codes, their OBYC configuration never needed EIN/EKG mappings -copying that configuration to a new company code that does require it leaves those mappings missing.
Q: Is EIN related to freight or delivery cost postings?
No. Freight and delivery costs use separate transaction keys (FR1 through FR4); EIN is exclusively the Purchase Account key under Purchase Account Management, an entirely different accounting concept.
📚 Quick Glossary of Terms Used in This Guide
- EIN: The transaction/event key for the Purchase Account under Purchase Account Management.
- EKG: The transaction/event key for the offsetting entry paired with EIN.
- Purchase Account Management: An optional, country-specific SAP feature posting an additional statutory P&L entry for purchase value.
- WRX: The GR/IR clearing transaction key, used on every standard goods receipt regardless of Purchase Account Management status.
- FR1–FR4: Transaction keys for freight and delivery cost clearing, unrelated to EIN.
🎯 Conclusion
"Account determination for entry LNER EIN not possible" specifically points to a missing Purchase Account Management mapping, not a freight or delivery cost issue as the error's name alone might suggest. By understanding that EIN is exclusively tied to this optional, country-specific feature, checking whether it's genuinely meant to be active for the company code in question, and configuring both EIN and its paired EKG offsetting key together, you can resolve this error confidently and correctly, without chasing the wrong configuration area.