Plant as Valuation Area

You have several company codes and plants in your project.  You are setting the plant as valuation area.  How can you minimize the effort involved in account determination?

a. You can group plants assigned to different charts of accounts by using the account grouping code.
b. You can group plants assigned to the same chart of accounts by using the valuation grouping code.
c. You can group plants assigned to different charts of accounts by using the valuation grouping code.
d. You can group plants assigned to the same charts of accounts by using the account grouping code.

Which is the correct answer?

---

Answers:

Valuation Modifier / Valuation Grouping Code

  • It is assigned to valuation area in Tcode: OMWD (SPRO IMG -> Materials Management -> Valuation and Account Assignment -> Account Determination -> Account Determination without Wizard -> Group Together Valuation Areas)

  •  
  • Together with other factors, the valuation grouping code determines the G/L accounts to which goods movement is posted (automatic account determination).  For example, valuation areas 1000 and 2000 are required to be posted to the same G/L accounts, these are grouped to valuation grouping code 0001 and G/L is determined based on valuation grouping code and valuation class.
Correct answer is b.

SAP FI/CO Tips

See Also

Get help for your SAP FI/CO problems
SAP FICO Forum - Do you have a SAP FI/CO Question?

SAP Books
SAP FICO Books  - Certification, Interview Questions and Configuration

SAP FICO Tips
SAP FI/CO Tips and Financial Accounting/Controlling

Main Index
SAP ERP Modules, Basis, ABAP and Other IMG Stuff

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG. 
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk. 
 The content on this site may not be reproduced or redistributed without the express written permission of
www.erpgreat.com or the content authors.