SAF FI Frequently Asked Questions 1

1. Whether any FI doccument will be created during PO(Purchase order)? If please mention the entry also. 
2. What factors differentiates from one dunning level and other dunning level?
3.  APP There will be many banks in a house bank. If the payment should be maid from particular bank GL account.  Where it is need to configured.
4. What are various types of servers in SAP R/3
5. Can anybody explain me FI-MM integartion.pl explain in detail 
i.   movement types
ii.  account class
iii. material types
6. Maximum no. of dunning levels are created?
7. In how many ways APP  is configured
8. What is diff between AAM, Recurring entries, Sample doccument?

Find here with the answers for your questions

1.Whether any FI document will be created during PO(Purchase order)?If pl mention the entry also?

Ans: There is no document that is created in FI side during PO. But in controlling there can  be a commitment posting to a Cost Center. The offsetting entry is posted at the time of GR.

2.What factors differentiates from one dunning level and other dunning level

Ans: The most important thing that differentiates the dunning levels are the dunning texts. The dunning text defines the urgency of the dunning notice. The other things can be the dunning charges, minimum & maximum amounts etc. 

3.APP

There will be many banks in a house bank. If the payment should be maid from particular bank GL account. Where it is configured.

Ans: There can be several accounts in the same house bank. We should assign the GL accounts exclusively at the time of creating the Bank master data and the bank accounts. Accordingly we can do the bank determination in FBZP for the individual banks and the corresponding sub accounts. 

Tr code for Defining bank : FI12. 

4.What are various types of servers in SAP R/3?

Ans: The Typical SAP landscape looks something like figure 1.4 below:
 

5.can anybody explain me FI-MM integartion.pl explain in detail

i. Movement types: 

Classification key indicating the type of material movement (for example, goods receipt, goods issue, physical stock transfer).

The movement type enables the system to find predefined posting rules determining how the accounts of the financial accounting system (stock and consumption accounts) are to be posted and how the stock fields in the material master record are to be updated. 

ii. Valuation class

Assignment of a material to a group of G/L accounts

Along with other factors, the valuation class determines the G/L accounts that are updated as a result of a valuation-relevant transaction or event, such as a goods movement.

The valuation class makes it possible to:

- Post the stock values of materials of the same material type to different G/L accounts 
- Post the stock values of materials of different material types to the same G/L account 

iii. Transaction/Event Key

Key allowing the user to differentiate between the various transactions and events (such as physical inventory transactions and goods movements) that occur within the field of inventory management. 

The transaction/event type controls the filing/storage of documents and the assignment of document numbers. 

iv.  Material Type

Groups together materials with the same basic attributes, for example, raw materials, semifinished products, or finished products.

When creating a material master record, you must assign the material to a material type. The material type you choose determines:

- Whether the material is intended for a specific purpose, for example, as a configurable 
  material or process material 
- Whether the material number can be assigned internally or externally 
- The number range from which the material number is drawn 
- Which screens appear and in what sequence 
- Which user department data you may enter 
- What procurement type the material has; that is, whether it is manufactured in-house or 
  procured externally, or both 

Together with the plant, the material type determines the material's inventory management requirement, that is:

- Whether changes in quantity are updated in the material master record 
- Whether changes in value are also updated in the stock accounts in financial accounting 

6.Maximum no. of dunning levels are created?

Ans: 9 levels maximum.

7.In how many ways APP  is configured?

Tr Code: FBZP

8.What is diff between AAM,Recurring entries,Sample doccument?

Account Assignment Model:

A reference for document entry that provides default values for posting business transactions. An account assignment model can contain any number of G/L account items and can be changed or supplemented at any time. In contrast to sample documents, the G/L account items for account assignment models may be incomplete.

Recurring Entries:

A periodically recurring posting made by the recurring entry program on the basis of recurring entry original documents.

The procedure is comparable with a standing order by which banks are authorized to debit rent payments, payment contributions or loan repayments.

Sample Documents:

Special type of reference document. Data from this document is used to create default entries on the accounting document entry screen.

Unlike an accounting document, a sample document does not update transaction figures but merely serves as a data source for an accounting document.

Swarajya.

More Financial Questions

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

SAP FI Books
SAP Financial and Controlling Certification, Interview Questions and Configurations Reference Books

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

Best regards,
SAP Basis, ABAP Programming and Other IMG Stuff
http://www.erpgreat.com

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.