SAP Knowledge Base Article - Preview

2478360 - MIRO/MIR7-Posting logic for planned delivery cost with account assignment and item category

Symptom

A PO has planned delivery cost for which GR has not been posted. During invoice processing (Transaction code MIRO), system does not derive the corresponding G/L account that you have maintainned in transaction code OBYC with corresponding posting key and accrual key. Instead, system derives the G/L from PO.


Read more...

Environment

  • Materials Management (MM)
  • SAP R/3
  • SAP R/3 Enterprise 4.7
  • SAP ERP Core Component
  • SAP ERP
  • SAP enhancement package for SAP ERP
  • SAP enhancement package for SAP ERP, version for SAP HANA

Product

SAP ERP Central Component all versions ; SAP ERP all versions ; SAP R/3 Enterprise all versions ; SAP R/3 all versions ; SAP enhancement package for SAP ERP all versions ; SAP enhancement package for SAP ERP, version for SAP HANA all versions

Keywords

planned delivery cost, T163K, XBNSB, account assignment, item category, MIRO, MIR7, G/L account, M/08, pricing procedure, FRE, FR2, accrual, condition, condition type, delivery cost, Del. cost seperate, DCosts separate, KBS , KBA , kbs , miro , account assignment , t163k , g/l account , dcosts separate , item category , xbnsb , third party , planned delivery cost , accrual , mir7 , MM-IV-GF-VAL , Valuation, Account determination, Postings , MM-PUR-GF-ACC , Account assignment , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.