This document contains true/false questions about managerial and financial accounting concepts in SAP. Key points covered include:
- Chart of accounts can have different combinations of operating, group, and alternate COAs assigned to company codes.
- Group COAs map to operating COAs in many-to-one relationships.
- G/L account numbers are controlled at the chart of account level through account groups and field status.
- Documents are uniquely identified by combinations of document header, posting date, number and company code.
- Posting keys and field status groups control account types and field statuses allowed in documents.
The document discusses various concepts related to financial accounting in SAP. It covers topics like the vendor and customer master data, accounting documents, posting keys, number ranges, and financial statement generation. Key points include that the vendor master can contain data at multiple levels, the automatic payment program can process vendor and customer accounts, documents can be reversed, and financial statements can be generated for different organizational entities like company code and business area.
Account groups are used to control the field status of master fields, number range, and whether accounts are profit and loss or balance sheet. Posting transactions to an account in a currency other than the account currency is only allowed if the account currency is the same as the local currency of the company code. You can carry forward P&L account balances to multiple retained earnings accounts through period end processing.
This document discusses key concepts related to chart of accounts, account groups, document types, and customer and vendor masters in SAP. Some of the main points covered include:
- A company code can have one operating chart of accounts and one alternate chart of accounts, or multiple operating charts of accounts and one group and alternate chart of accounts.
- Account groups are defined at the client level and can include common general ledger account codes.
- Documents are uniquely identified by the document number, company code, fiscal year, document date, and period.
- Customer and vendor masters are defined at the client level and accounts can be blocked for certain purposes like posting in selected company codes.
- Changes
The document discusses key concepts related to SAP R/3 and financial accounting. It covers topics like the benefits of integration in R/3, the modules supported in R/3, components of financial accounting and cost accounting, master data creation, transaction processing, documents generated, account types, number ranges, posting keys, and more. The document contains 53 multiple choice questions testing understanding of these concepts.
The document contains questions and answers related to general ledger accounts, chart of accounts, and company codes in SAP. It addresses topics like the structure of GL account numbers, how GL accounts are linked to company codes and charts of accounts, controls over posting and master data for accounts, usage of exchange rates, and the relationship between banks, house banks, account IDs, and how they are mapped in SAP.
1. A business area can be used for many company codes, must be assigned to company codes in IMG, and are used for internal P&L and balance sheets. A company code can have many business areas.
2. A chart of accounts can be assigned to multiple company codes.
3. Balance sheets and profit and loss statements can be drawn up for business areas. A company code can have many business areas, and a business area can be across company codes.
4. The use of business area is optional in SAP.
The document discusses various topics related to accounting, including automatic payment programs, dunning procedures, financial accounting closing processes, cash journals, alternate charts of accounts, and document types. It provides 31 multiple choice questions about setting up and configuring these different accounting elements in SAP. The questions cover topics such as assigning payment company codes, grouping payments by method, minimum payment amounts, bank and postal code optimization, payment blocking indicators, dunning procedures, valuation methods, exchange rate accounts, cash journal setup including number ranges and tax codes, mapping cost elements between FI and CO modules, assigning alternate charts of accounts, and defining reverse document types.
This document discusses key concepts related to financial accounting in SAP such as document principles, payment processes, payment programs, dunning procedures, financial statement versions, and depreciation posting. Some true statements include that each business event creates an accounting document in SAP, payment proposals can be edited and recreated, interest can be posted during dunning, and financial statement versions are defined by entering them in the directory and defining hierarchy levels. False statements include that the sending and paying company codes are always the same and that financial statement versions are limited to 9 hierarchy levels.
The document discusses various concepts related to financial accounting in SAP. It covers topics like the vendor and customer master data, accounting documents, posting keys, number ranges, and financial statement generation. Key points include that the vendor master can contain data at multiple levels, the automatic payment program can process vendor and customer accounts, documents can be reversed, and financial statements can be generated for different organizational entities like company code and business area.
Account groups are used to control the field status of master fields, number range, and whether accounts are profit and loss or balance sheet. Posting transactions to an account in a currency other than the account currency is only allowed if the account currency is the same as the local currency of the company code. You can carry forward P&L account balances to multiple retained earnings accounts through period end processing.
This document discusses key concepts related to chart of accounts, account groups, document types, and customer and vendor masters in SAP. Some of the main points covered include:
- A company code can have one operating chart of accounts and one alternate chart of accounts, or multiple operating charts of accounts and one group and alternate chart of accounts.
- Account groups are defined at the client level and can include common general ledger account codes.
- Documents are uniquely identified by the document number, company code, fiscal year, document date, and period.
- Customer and vendor masters are defined at the client level and accounts can be blocked for certain purposes like posting in selected company codes.
- Changes
The document discusses key concepts related to SAP R/3 and financial accounting. It covers topics like the benefits of integration in R/3, the modules supported in R/3, components of financial accounting and cost accounting, master data creation, transaction processing, documents generated, account types, number ranges, posting keys, and more. The document contains 53 multiple choice questions testing understanding of these concepts.
The document contains questions and answers related to general ledger accounts, chart of accounts, and company codes in SAP. It addresses topics like the structure of GL account numbers, how GL accounts are linked to company codes and charts of accounts, controls over posting and master data for accounts, usage of exchange rates, and the relationship between banks, house banks, account IDs, and how they are mapped in SAP.
1. A business area can be used for many company codes, must be assigned to company codes in IMG, and are used for internal P&L and balance sheets. A company code can have many business areas.
2. A chart of accounts can be assigned to multiple company codes.
3. Balance sheets and profit and loss statements can be drawn up for business areas. A company code can have many business areas, and a business area can be across company codes.
4. The use of business area is optional in SAP.
The document discusses various topics related to accounting, including automatic payment programs, dunning procedures, financial accounting closing processes, cash journals, alternate charts of accounts, and document types. It provides 31 multiple choice questions about setting up and configuring these different accounting elements in SAP. The questions cover topics such as assigning payment company codes, grouping payments by method, minimum payment amounts, bank and postal code optimization, payment blocking indicators, dunning procedures, valuation methods, exchange rate accounts, cash journal setup including number ranges and tax codes, mapping cost elements between FI and CO modules, assigning alternate charts of accounts, and defining reverse document types.
This document discusses key concepts related to financial accounting in SAP such as document principles, payment processes, payment programs, dunning procedures, financial statement versions, and depreciation posting. Some true statements include that each business event creates an accounting document in SAP, payment proposals can be edited and recreated, interest can be posted during dunning, and financial statement versions are defined by entering them in the directory and defining hierarchy levels. False statements include that the sending and paying company codes are always the same and that financial statement versions are limited to 9 hierarchy levels.
This document discusses accounting concepts related to financial and managerial accounting in SAP such as document principles, payment processes, dunning programs, financial statement versions, and depreciation postings. Key points covered include that a business event can trigger more than one document, payment proposals can be edited but not deleted, the maximum dunning levels are nine, and depreciation postings can be done through either background processing or direct FI postings.
This document contains questions about financial accounting topics in SAP. It covers topics like charts of accounts, organizational structure, customer and vendor master data, bank account management, payment processing, and currencies. There are 43 multiple choice questions testing knowledge of how these different areas work together in the SAP system.
This document contains questions and answers related to concepts in SAP financial accounting. Some key points covered include:
- Company codes attached to the same controlling area have the same operational chart of accounts.
- Every transaction results in a document, but not all statements are completely true.
- The field status of text fields in document headers are controlled by the document type.
- Validation rules take priority over substitution rules if both are defined for the same field.
- Posting periods can be closed automatically by setting a deadline date.
This document contains 45 true/false questions related to managerial and financial accounting concepts in SAP. Some key points covered include:
- G/L master records apply to all company codes by default.
- Several elements like tax codes, payment terms, and reconciliation accounts can be defined at the company code level rather than globally.
- Functions like partial payments, down payments, and check issuance have standard links to original documents in SAP.
- Certain transactions like physical inventories and direct G/L postings for bank charges do not involve accounting entries.
- The document tests a wide range of topics on general ledger, accounts payable, accounts receivable, payments, and financial reporting in SAP
The document provides an overview of SAP's mySAP business suite and key financial accounting concepts and configurations in SAP. It discusses SAP's product strategy, the components of mySAP business suite, navigation and transactions in SAP, organizational structures like company codes and charts of accounts, master data including general ledger, customer, and vendor accounts, and basic accounting configurations including fiscal year variants, currencies, and exchange rates. It also addresses document principles, procurement processes, asset accounting, and consolidation requirements.
The document contains questions and answers related to SAP FI (Financial Accounting) module. It covers topics like the elements of R/3 system, data storage in SAP, ASAP methodology milestones, mySAP.com elements, transaction codes, document types, number ranges, posting keys, tax configuration, consolidation, and more.
While parking a document in SAP R/3, a temporary document number is created. When addressing cleared items, resetting them reinstates the original entries and clears the clearing entry. It is possible to book a vendor invoice with different payment due dates of 30%, 50%, and 20% on different dates. Customers can maintain standard text selections for G/L line items and receive warnings for posting to previous years at year-end.
sap fico interview question and answer part 1, ERPTAC is one of the oldest training institute to provide education on sap online and class room FICO, HCM, BI, BW, HANA, ABAP, BASIS, MM, SD
The document contains a set of multiple choice questions related to various SAP concepts and technologies. Specifically, it tests knowledge on topics like READ with BINARY SEARCH, F1 help functionality, R/3 configuration, background job output, Dynpro flow logic, Idoc process code, GUI components, RFC call types, transaction codes, ABAP Dictionary usage, internal table types, subroutine interfaces, function module parameters, and client-independent objects. It contains 50 questions in total to assess an individual's familiarity with fundamental SAP technical concepts.
The document contains multiple choice questions about concepts in SAP such as chart of accounts, company codes, document types, and vendor/customer master records. Key points covered include:
- Chart of accounts have a 1:n relationship with company codes.
- Tax codes are defined at the company code level.
- Document dates, posting dates, value dates, and baseline dates are available in finance documents.
- Document headers can contain fields like document date, posting date, document type, company code, and document currency.
- Period definitions are attached to company codes in a fiscal year variant.
- Account groups are used to select number ranges when creating master records.
This document contains 33 multiple choice questions from a financial accounting certification test. The questions cover topics such as special general ledger types, the new general ledger in SAP, document splitting, payment processes, and cost accounting elements like cost centers. The test is identifying the correct answers regarding accounting configuration and processes in SAP.
A company code is assigned organizational units like plants, purchasing organizations, and sales organizations. A controlling area can be assigned to one or many company codes and oversees activities like cost center accounting. A company code can only have one chart of accounts. There are two types of fiscal year variants: calendar year and year dependent. Year dependent variants have changing month end dates each year. Postings do not occur in special periods in materials management. A company code can have three currencies configured: the local currency and two parallel currencies. Additional ledgers are only needed for the third parallel currency if it is different than the second.
Prepare for your interview with these top SAP FICO Practice Exam questions. For more IT Profiles, Sample Resumes, Practice exams, Interview Questions, Live Training and more…visit ITLearnMore – Most Trusted Website for all Learning Needs by Students, Graduates and Working Professionals.
Looking to add weight to your resume? Check out for ITLearnmore for varied online IT courses at affordable prices intended for career boost. There is so much in store for both fresh graduates and professionals here. Hurry up..! Get updated with the current IT job market requirements and related courses.More information visit www.ITLearnMore.com
This document provides steps for setting up and running an interest calculation in SAP. It outlines 9 steps: 1) Define interest calculation types, 2) Prepare account balance interest calculation, 3) Define reference interest rates, 4) Define time dependent terms, 5) Enter reference interest rate values, 6) Creation of GL accounts, 7) Define automatic posting accounts, 8) Entry for a loan, and 9) Run the interest calculation. The document includes transaction codes, navigation paths, and example data for setting up interest calculation for balance and item types.
This program calculates and carries forward customer and vendor account balances from the previous fiscal year to the new year. To run the program, the user selects the company code, fiscal year to transfer balances to, and range of customer and vendor accounts. The program carries forward any remaining balances and stores them in the opening balances for the selected accounts in the new fiscal year. It should be run at the start of each new fiscal year and any time discrepancies arise between the prior year ending and current year opening balances for accounts.
This document provides instructions for using transaction FB50 in SAP to post cross-company code general ledger documents. Transaction FB50 allows a user to post entries that include data for multiple company codes. For example, an entry can be posted with company code 1000 in the header and include a line item for company code 5200. The system will then automatically generate offsetting line items to balance debits and credits across the company codes. The document outlines the steps to access and use transaction FB50, including entering header and line item information, simulating, and posting the journal entry.
This document provides instructions for changing information in a posted financial document in SAP. The key steps are:
1) Access transaction code FB02 and search for the posted document to change.
2) Fields like document text, assignment, and header text can be updated for individual document lines or the header.
3) Make the desired changes to fields displayed in red and save the changes. The changes are then saved to the original document.
This document provides instructions for using a previously posted financial (FI) document as a reference to quickly enter similar general ledger (GL) documents. It describes how to access the post with reference function in SAP, select the reference document, and copy over fields like document number, company code, and fiscal year while manually entering the amounts. The amounts can then be adjusted as needed for each new GL document before saving and posting the entries.
This document provides a 60 question mock test on SAP FI (Financial Accounting) concepts. The questions cover a range of topics including basic settings, master data, document control, posting control, clearing, cash journal, and special GL transactions. Correct answers are awarded points ranging from 1 to 0.125 based on the number of true/false options in the question. An overall percentage score can be calculated by multiplying the total points by 1.66.
This document provides step-by-step instructions for creating general ledger (GL) posting documents in SAP. It describes how to create single-entry and mass posting documents using transaction codes F-02 and FB50 respectively. Key steps include entering header information like document date and type, then adding line items with details such as account, amount, cost center, and debit/credit indicator. The document can be simulated and validated before final posting.
The document describes how to create a general ledger posting document in SAP. Key steps include selecting transaction code F-02 in SAP GUI, entering the document date, type, company code, and posting date on the header screen. Additional optional fields can be populated as well. Line items are then added that specify the account, amount, and other details. The system will update the specified accounts and assign a document number upon posting.
This document discusses accounting concepts related to financial and managerial accounting in SAP such as document principles, payment processes, dunning programs, financial statement versions, and depreciation postings. Key points covered include that a business event can trigger more than one document, payment proposals can be edited but not deleted, the maximum dunning levels are nine, and depreciation postings can be done through either background processing or direct FI postings.
This document contains questions about financial accounting topics in SAP. It covers topics like charts of accounts, organizational structure, customer and vendor master data, bank account management, payment processing, and currencies. There are 43 multiple choice questions testing knowledge of how these different areas work together in the SAP system.
This document contains questions and answers related to concepts in SAP financial accounting. Some key points covered include:
- Company codes attached to the same controlling area have the same operational chart of accounts.
- Every transaction results in a document, but not all statements are completely true.
- The field status of text fields in document headers are controlled by the document type.
- Validation rules take priority over substitution rules if both are defined for the same field.
- Posting periods can be closed automatically by setting a deadline date.
This document contains 45 true/false questions related to managerial and financial accounting concepts in SAP. Some key points covered include:
- G/L master records apply to all company codes by default.
- Several elements like tax codes, payment terms, and reconciliation accounts can be defined at the company code level rather than globally.
- Functions like partial payments, down payments, and check issuance have standard links to original documents in SAP.
- Certain transactions like physical inventories and direct G/L postings for bank charges do not involve accounting entries.
- The document tests a wide range of topics on general ledger, accounts payable, accounts receivable, payments, and financial reporting in SAP
The document provides an overview of SAP's mySAP business suite and key financial accounting concepts and configurations in SAP. It discusses SAP's product strategy, the components of mySAP business suite, navigation and transactions in SAP, organizational structures like company codes and charts of accounts, master data including general ledger, customer, and vendor accounts, and basic accounting configurations including fiscal year variants, currencies, and exchange rates. It also addresses document principles, procurement processes, asset accounting, and consolidation requirements.
The document contains questions and answers related to SAP FI (Financial Accounting) module. It covers topics like the elements of R/3 system, data storage in SAP, ASAP methodology milestones, mySAP.com elements, transaction codes, document types, number ranges, posting keys, tax configuration, consolidation, and more.
While parking a document in SAP R/3, a temporary document number is created. When addressing cleared items, resetting them reinstates the original entries and clears the clearing entry. It is possible to book a vendor invoice with different payment due dates of 30%, 50%, and 20% on different dates. Customers can maintain standard text selections for G/L line items and receive warnings for posting to previous years at year-end.
sap fico interview question and answer part 1, ERPTAC is one of the oldest training institute to provide education on sap online and class room FICO, HCM, BI, BW, HANA, ABAP, BASIS, MM, SD
The document contains a set of multiple choice questions related to various SAP concepts and technologies. Specifically, it tests knowledge on topics like READ with BINARY SEARCH, F1 help functionality, R/3 configuration, background job output, Dynpro flow logic, Idoc process code, GUI components, RFC call types, transaction codes, ABAP Dictionary usage, internal table types, subroutine interfaces, function module parameters, and client-independent objects. It contains 50 questions in total to assess an individual's familiarity with fundamental SAP technical concepts.
The document contains multiple choice questions about concepts in SAP such as chart of accounts, company codes, document types, and vendor/customer master records. Key points covered include:
- Chart of accounts have a 1:n relationship with company codes.
- Tax codes are defined at the company code level.
- Document dates, posting dates, value dates, and baseline dates are available in finance documents.
- Document headers can contain fields like document date, posting date, document type, company code, and document currency.
- Period definitions are attached to company codes in a fiscal year variant.
- Account groups are used to select number ranges when creating master records.
This document contains 33 multiple choice questions from a financial accounting certification test. The questions cover topics such as special general ledger types, the new general ledger in SAP, document splitting, payment processes, and cost accounting elements like cost centers. The test is identifying the correct answers regarding accounting configuration and processes in SAP.
A company code is assigned organizational units like plants, purchasing organizations, and sales organizations. A controlling area can be assigned to one or many company codes and oversees activities like cost center accounting. A company code can only have one chart of accounts. There are two types of fiscal year variants: calendar year and year dependent. Year dependent variants have changing month end dates each year. Postings do not occur in special periods in materials management. A company code can have three currencies configured: the local currency and two parallel currencies. Additional ledgers are only needed for the third parallel currency if it is different than the second.
Prepare for your interview with these top SAP FICO Practice Exam questions. For more IT Profiles, Sample Resumes, Practice exams, Interview Questions, Live Training and more…visit ITLearnMore – Most Trusted Website for all Learning Needs by Students, Graduates and Working Professionals.
Looking to add weight to your resume? Check out for ITLearnmore for varied online IT courses at affordable prices intended for career boost. There is so much in store for both fresh graduates and professionals here. Hurry up..! Get updated with the current IT job market requirements and related courses.More information visit www.ITLearnMore.com
This document provides steps for setting up and running an interest calculation in SAP. It outlines 9 steps: 1) Define interest calculation types, 2) Prepare account balance interest calculation, 3) Define reference interest rates, 4) Define time dependent terms, 5) Enter reference interest rate values, 6) Creation of GL accounts, 7) Define automatic posting accounts, 8) Entry for a loan, and 9) Run the interest calculation. The document includes transaction codes, navigation paths, and example data for setting up interest calculation for balance and item types.
This program calculates and carries forward customer and vendor account balances from the previous fiscal year to the new year. To run the program, the user selects the company code, fiscal year to transfer balances to, and range of customer and vendor accounts. The program carries forward any remaining balances and stores them in the opening balances for the selected accounts in the new fiscal year. It should be run at the start of each new fiscal year and any time discrepancies arise between the prior year ending and current year opening balances for accounts.
This document provides instructions for using transaction FB50 in SAP to post cross-company code general ledger documents. Transaction FB50 allows a user to post entries that include data for multiple company codes. For example, an entry can be posted with company code 1000 in the header and include a line item for company code 5200. The system will then automatically generate offsetting line items to balance debits and credits across the company codes. The document outlines the steps to access and use transaction FB50, including entering header and line item information, simulating, and posting the journal entry.
This document provides instructions for changing information in a posted financial document in SAP. The key steps are:
1) Access transaction code FB02 and search for the posted document to change.
2) Fields like document text, assignment, and header text can be updated for individual document lines or the header.
3) Make the desired changes to fields displayed in red and save the changes. The changes are then saved to the original document.
This document provides instructions for using a previously posted financial (FI) document as a reference to quickly enter similar general ledger (GL) documents. It describes how to access the post with reference function in SAP, select the reference document, and copy over fields like document number, company code, and fiscal year while manually entering the amounts. The amounts can then be adjusted as needed for each new GL document before saving and posting the entries.
This document provides a 60 question mock test on SAP FI (Financial Accounting) concepts. The questions cover a range of topics including basic settings, master data, document control, posting control, clearing, cash journal, and special GL transactions. Correct answers are awarded points ranging from 1 to 0.125 based on the number of true/false options in the question. An overall percentage score can be calculated by multiplying the total points by 1.66.
This document provides step-by-step instructions for creating general ledger (GL) posting documents in SAP. It describes how to create single-entry and mass posting documents using transaction codes F-02 and FB50 respectively. Key steps include entering header information like document date and type, then adding line items with details such as account, amount, cost center, and debit/credit indicator. The document can be simulated and validated before final posting.
The document describes how to create a general ledger posting document in SAP. Key steps include selecting transaction code F-02 in SAP GUI, entering the document date, type, company code, and posting date on the header screen. Additional optional fields can be populated as well. Line items are then added that specify the account, amount, and other details. The system will update the specified accounts and assign a document number upon posting.
This document provides training on general ledger accounting in SAP. It covers topics such as creating general ledger master records, making changes to master records, creating single and multiple line item posting documents, parking documents, reversing documents, changing documents, displaying document information, clearing accounts, recurring entries, and closing procedures. Step-by-step instructions are provided for key general ledger processes in SAP. Frequently used transaction codes for general ledger, accounts payable, withholding tax, and asset accounting are also listed.
This document provides configuration settings for asset accounting in SAP. It includes instructions on setting up charts of depreciation, general ledger indicators, parallel currencies, asset classes, screen layouts, and depreciation terms. Key steps include copying the reference chart of depreciation, creating general ledger accounts for fixed assets, depreciation, sales, and expenses, maintaining conversion factors and exchange rates, assigning tax codes, and defining asset classes and number ranges. The goal is to properly configure the asset accounting module according to the country's legal and business requirements.
TATA Group is implementing SAP across functions. As part of the Finance implementation, general ledger must be set up in SAP. This involves defining the length of general ledger accounts, assigning the chart of accounts to the company code "TATA", defining account groups based on requirements, creating retained earnings accounts, and creating general ledger accounts either manually or using reference data. Tolerance groups for transactions must also be defined to control posting limits.
1. This document provides training on how to use SAP's General Ledger (GL) functionality.
2. It covers topics such as creating and changing GL master records, posting documents, parking documents, recurring entries, and closing procedures.
3. Specific transaction codes are provided for activities like single-entry and mass posting of documents, parking documents, and displaying changes to master records.
APC stands for Acquisition and Production costs. Acquisition refers to externally purchased assets, including invoice price and related expenses. Production cost refers to internally created assets through the addition of expenses to AUC over time, such as additions to an office building. APC therefore includes both external and internal costs that need to be capitalized.
1. Accounts receivable is amounts a company is owed by customers for goods or services purchased on credit.
2. The SAP FI Accounts Receivable component records and manages accounting data for all customers. It is integrated with sales management and directly updates general ledger accounts.
3. Configuring organizational units such as company code, sales organization, and plant is required to execute the basic accounts receivable cycle in SAP, which includes processes like customer master data, material master data, sales order, delivery, invoice, and payment.
This document discusses key aspects of financial accounting in SAP, including the enterprise structure, chart of accounts, general ledger, account groups, and currencies. It explains that the enterprise structure forms the basis for other finance modules and includes elements like the chart of accounts and company code configuration. The chart of accounts contains all GL accounts and associated attributes. Account groups help categorize accounts. Multiple currencies can be defined and each company code uses one as its local currency.
This document discusses sample documents, recurring documents, accounts payable, vendor master data creation, terms of payment, and dunning in SAP. Sample documents provide default values for creating G/L account documents. Recurring documents are used for regularly repeated transactions like rent payments. Accounts payable records vendor transactions. Vendor master records can be created, including one-time vendors. Terms of payment and dunning procedures are also configured in SAP.
SAP ERP S4HANAFinanceMOTIVATIONThis material is an.docxtodd331
SAP ERP: S/4HANA
Finance
MOTIVATION
This material is an introduction to SAP S/4HANA financial functionality. It is aimed at students at universities and other educational institutions with limited experience with accounting
It can be used in the classroom or for self-study.
On completion of the course, students will be able to understand the basic concepts general ledger accounting.
The material also serves as a reference for occasional users of SAP systems.
LEARNING METHOD
The learning method used is “guided learning.” The benefit of this method is that knowledge is imparted quickly. Students also acquire practical skills and competencies. As with an exercise, this method explains a process or procedure in detail using the GBI case study
Exercises at the end enable students to put their knowledge into practice.Product
SAP S/4HANA
Level
Introductory
Focus
ERP Systems- Finance
Author
Dr. Paul Hawking
Dr. Susan Foster
Reviewed by
Urooj R. Khan
Version 1.2019
Table of Contents
Introduction3
Accounting3
Financial Accounting3
Process Overview4
General Ledger Master Records5
Task 1: Display the Chart of Accounts6
Task 2: The Chart of Accounts Applied to the General Ledger9
Task 3: Display General Ledger Account11
Task 4: Post Transfer of Funds to Alternate Bank Account13
Task 5: Display G/L Account Balance17
(a) Adding a Fiori Tile:17
(b) Displaying Account Balances:18
(c) Displaying Accounting Documents21
Task 6: Displaying Journal Entries22
Task 7: Post Purchase of Office Supplies24
Task 8: Display General Ledger Account Balances27
IntroductionScenario
Global Bikes Inc (GBI) was founded in 2001 following the merger of two bicycle manufacturers, one based in the US and the other in Germany. GBI has three lines of business: deluxe and professional touring bikes, men’s and women’s off-road bikes, and bike accessories. GBI sells its bikes to a network of specialized dealers throughout the world, and it procures its raw materials from a variety of suppliers globally.
GBI has two manufacturing facilities, one in the US and one in Germany. It also has three additional warehouses, two in the US and one in Germany. GBI has more than 100 employees globally. The organization uses SAP ERP to support its processes. The company has a new bicycle for sale- Mongoose Mountain Bike.
Accounting
The function of accounting is to provide financial documentation and information for an enterprise and other interested parties that are associated with it. There are basically two types of accounting:
· External accounting is oriented more towards satisfying the information requirements of external parties. This is referred to as Financial Accounting (FI).
· Internal accounting meets the reporting demands of internal enterprise groups. This is referred to as Cost Accounting (CO).
External Reporting
External Accounting
Internal Accounting
Product Cost s
Internal Reporting
Cost Centres
Profit Centres
Profit Margins
Retained Earnings
Liquidity Calc’n
Prof.
A financial statement version defines the financial statements (balance sheet and profit & loss statements) in SAP. It allows you to configure different hierarchy levels with account categories to display detailed or aggregated information. Annual closing involves carrying forward vendor, customer, and balance sheet account balances while closing profit/loss accounts to retained earnings. Ensuring correct financial statement balances requires properly assigning accounts to nodes, including setting debit or credit indicators at the account or node level.
The document provides training on SAP finance functions including:
[1] Processing general ledger accounts at both central and mass levels, including required fields.
[2] Entering and processing general ledger account documents and transactions like modifications, reversals and clearings.
[3] Displaying account balances and individual items, as well as clearing accounts and obtaining reports like trial balances and financial statements.
The document discusses how to configure foreign currency transactions in SAP. It explains that you can define account symbols to determine which general ledger accounts transactions in different currencies will post to. It also discusses how to assign external transaction codes from bank statements to internal posting rules to trigger the correct postings in SAP. Finally, it provides the recommended sequence for configuring foreign currency transaction processing which includes defining transaction types, assigning banks and transactions, and setting up posting rules and specifications.
The document discusses customer master data in SAP. It explains that customer master data contains key information about customers like addresses, payment terms, and delivery methods. It also describes the different account groups (such as sold-to party, bill-to party) and partner functions used to classify customer master records based on the business relationship. Steps are provided on how to create a new customer master record including entering required fields in the general, company code, and sales area data sections.
Here are some potential questions you may be asked in an SAP FI/CO interview:
Configuration:
- Walk through the steps to configure a basic chart of accounts
- Explain how to set up fields status variants and field status groups
- Describe the process of integrating FI with other modules like MM, SD, etc.
- Configure accounts receivable and accounts payable
- Set up special GL transactions like down payments
Functional:
- Explain the accounting principles in FI/CO like debits/credits, periodic vs. perpetual etc.
- Describe the different types of documents in FI like journal entries, invoices etc.
- Explain the purpose and usage of reconciliation accounts
- Disc
Understanding SAP Enterprise Structure in SAP FISAP XPERT
The document describes the company code and organizational structure of John Woolworths supermarket chain. It discusses that John Woolworths has four companies located in the US and Canada, and four business areas. It also provides steps to define the company code, company, business area, and segment in SAP using transaction codes.
Here are the steps to create the RFQ:
1. Enter your purchase requisition number
2. Select all items
3. Click "Adopt" to copy item details to RFQ
4. Click "Save" to save the RFQ
This will create the RFQ with the item details copied from the purchase requisition. Now you can generate quotations by adding vendors.
The document provides sample questions for the SAP Certified Application Associate – Financial Accounting with SAP ERP 6.0 EHP4 certification exam. It includes 10 multiple choice questions testing knowledge of topics like company code configuration, document parking, validation creation, cash journal usage, and report building in SAP. The document emphasizes that answering the sample questions correctly does not guarantee passing the actual certification exam, which covers a broader set of topics.
What is an RPA CoE? Session 1 – CoE VisionDianaGray10
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
AppSec PNW: Android and iOS Application Security with MobSFAjin Abraham
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.
The Microsoft 365 Migration Tutorial For Beginner.pptxoperationspcvita
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/how-axelera-ai-uses-digital-compute-in-memory-to-deliver-fast-and-energy-efficient-computer-vision-a-presentation-from-axelera-ai/
Bram Verhoef, Head of Machine Learning at Axelera AI, presents the “How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-efficient Computer Vision” tutorial at the May 2024 Embedded Vision Summit.
As artificial intelligence inference transitions from cloud environments to edge locations, computer vision applications achieve heightened responsiveness, reliability and privacy. This migration, however, introduces the challenge of operating within the stringent confines of resource constraints typical at the edge, including small form factors, low energy budgets and diminished memory and computational capacities. Axelera AI addresses these challenges through an innovative approach of performing digital computations within memory itself. This technique facilitates the realization of high-performance, energy-efficient and cost-effective computer vision capabilities at the thin and thick edge, extending the frontier of what is achievable with current technologies.
In this presentation, Verhoef unveils his company’s pioneering chip technology and demonstrates its capacity to deliver exceptional frames-per-second performance across a range of standard computer vision networks typical of applications in security, surveillance and the industrial sector. This shows that advanced computer vision can be accessible and efficient, even at the very edge of our technological ecosystem.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
"Choosing proper type of scaling", Olena SyrotaFwdays
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor IvaniukFwdays
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Digital Banking in the Cloud: How Citizens Bank Unlocked Their MainframePrecisely
Inconsistent user experience and siloed data, high costs, and changing customer expectations – Citizens Bank was experiencing these challenges while it was attempting to deliver a superior digital banking experience for its clients. Its core banking applications run on the mainframe and Citizens was using legacy utilities to get the critical mainframe data to feed customer-facing channels, like call centers, web, and mobile. Ultimately, this led to higher operating costs (MIPS), delayed response times, and longer time to market.
Ever-changing customer expectations demand more modern digital experiences, and the bank needed to find a solution that could provide real-time data to its customer channels with low latency and operating costs. Join this session to learn how Citizens is leveraging Precisely to replicate mainframe data to its customer channels and deliver on their “modern digital bank” experiences.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
1. ACADEMY: MANAGERIAL AND FINANCIAL ACCOUNTING
FI PAPER: 10
1. Every company code can have the following combination of Chart of Accounts
(COA)
(Y) (N) One operating COA and one group COA and one alternate COA
(Y) (N) One operating COA and no group COA and one alternate COA
(Y) (N) One operating COA and one group COA and no alternate COA
(Y) (N) One operating COA and one alternate COA
(Y) (N) One operating COA and one group COA
(Y) (N) One operating COA and many group COA
(Y) (N) One operating COA and no group COA and no alternate COA
2. Each G/L Account in Group COA can be mapped to the following no. of account
code
in Operating COA
(Y) (N) Is mapped to Operating Chart of Account
(Y) (N) It is not mapped to Operating G/L Account Number
(Y) (N) Only one Operating G/L Account Number
(Y) (N) The relationship is many To one
3. Various Account Groups in one COA cannot consist of common G/L Account Codes.
(Y) (N)
4. Following fields form a part of COA segment of a general ledger account master
(Y) (N) Currency of the G/L Account
(Y) (N) Account Group of the Sub Ledger
(Y) (N) Field Status Group of the G/L Account
(Y) (N) Option to state whether it is a B/S or P&L Account Type
(Y) (N) G/L Account Name & Description
(Y) (N) Group Chart of Account
(Y) (N) House Bank of the G/L account
5. Each Account Code in a COA is automatically available for use to all company
codes
using that COA
(Y) (N)
6. Which of the following statements are true with respect G/L Number Ranges
(Y) (N) G/L Number Ranges are defined at Client Level
(Y) (N) Number Ranges of G/L Account Groups can overlap
(Y) (N) To G/L accounts can have the same number as long as they belong to
different Account Groups
7. Which of the following statements are true with respect to documents
(Y) (N) One document type can have more than one number range interval
(Y) (N) Different number range codes can have the same number range
intervals
(Y) (N) Document No. range are defined at chart of account level
8. Which of the following statements are true with respect to Account groups
(Y) (N) G/L & AR/AP Account groups are defined at Client level
(Y) (N) G/L & AR/AP Account groups are defined at company code level
(Y) (N) G/L Account groups are defined at the Chart of Account level
1
2. ACADEMY: MANAGERIAL AND FINANCIAL ACCOUNTING
FI PAPER: 10
9. Which of the following statements are false with respect to reconciliation account
(Y) (N) One Customer account can have many normal reconciliation accounts
(Y) (N) Reconciliation A/C can be used for direct accounting entries
(Y) (N) Reconciliation A/C are G/L Accounts
10. Which of the following statements are true with respect to account groups
(Y) (N) The Account Group is a required entry in the G/L COA Segment
(Y) (N) The Account Group is a required entry in the AR General Segment
(Y) (N) All the Account Groups of customers can have one common number
range
11. Which of the following statement is true with respect to customer account
(Y) (N) One customer can have different customer codes in various company
codes
(Y) (N) Company codes following the same chart of accounts must have the
same
reconciliation account for the same customer
(Y) (N) Various company codes can have different payment terms with one
customer
(Y) (N) Group Account Number is mandatory while entering a customer master
12. Which of the following statement is true
(Y) (N) For creation of vendor master account group is optional
(Y) (N) General Date Segment of the Vendor master can be used across
(Y) (N) company codes within a client
(Y) (N) Purchase organization segment of the same Vendor can be different for
different
company codes
13. Customer Master has the following Segments
(Y) (N) Chart of account segment
(Y) (N) General data segment
(Y) (N) Purchase Organization segment
(Y) (N) Accounting data (company code) segment
(Y) (N) Sales Area Segment
14. A Document is uniquely identified by a combination of
(Y) (N) Document Header /Posting key
(Y) (N) Posting Date/Document Number/Company Code
15. Which of the following statements are true
(Y) (N) Document Numbers can be alphanumeric
(Y) (N) Field Status of Transaction entry is Activity dependent & Account
dependent
(Y) (N) Document Type controls Field Status Group and G/L accounts that can
be used in the document.
(Y) (N) Document Types are defined at the Chart of Account Level
16. The relationship between House Banks and Account ID is the following
(Y) (N) One to One
(Y) (N) One to Many
(Y) (N) Many to Many
2
3. ACADEMY: MANAGERIAL AND FINANCIAL ACCOUNTING
FI PAPER: 10
17. Business Area once defined is available for use to
(Y) (N) All company codes where BA Financial Statements are enabled
(Y) (N) Only the company code to which BA is assigned to
18. A G/L account can be blocked for the following purposes
(Y) (N) From creating in company code
(Y) (N) From posting in all company codes
(Y) (N) From posting in selected company codes
(Y) (N) Cannot be blocked
(Y) (N) If blocked, is blocked for all the purposes in all the company codes
19. A different field status can be achieved for different actions such as creation of
account or change in master records.
(Y) (N)
20. Chart of Accounts is the list of G/L Account. A G/L account is ready for input if COA
is assigned to company code
(Y) (N)
21. The field “Field Status Variant” in the company code segment of the G/L Master
can be suppressed
(Y) (N)
22. Which of the following entities can be assigned numbers both internally &
externally
(Y) (N) G/L Account
(Y) (N) Vendor
(Y) (N) Customer
(Y) (N) Document Type
23. The chart of account is maintained at
(Y) (N) Group Level
(Y) (N) Company code Level
(Y) (N) Client Level
(Y) (N) Country Level
(Y) (N) Group Chart of Account Level
24. A document number range is assigned to each document type. Document
number
ranges are defined at company code level.
(Y) (N)
25. Which of the statements are correct
(Y) (N) A House Bank and Account ID can be linked to one bank key
(Y) (N) A House Bank and Account ID can be linked to many bank key
(Y) (N) Many House Banks and Many Account ID can be linked to one bankkey
3
4. ACADEMY: MANAGERIAL AND FINANCIAL ACCOUNTING
FI PAPER: 10
(Y) (N) A House Bank can contain many account Ids which are represented
through Individual bank account numbers
26. Filed status of the line item can be controlled through Posting Key & Filed Status
Group in G/L Account. Thus the Filed Status of “Amount” “Posting key” and “Account”
can be suppressed
(Y) (N)
27. Which of the following is/are true
(Y) (N) The bank key of your house bank cannot be the bank key of your
customer
(Y) (N) The bank key of your customer cannot be used as your house bank’s
bank key
(Y) (N) The bank key of your vendors may be same as your house bank’s bank
key
(Y) (N) The bank key of your customer is entered through customizing
28. You cannot make a financial entry if filed status variant is not assigned to
company code
(Y) (N)
29. The G/L account for a bank is linked to
(Y) (N) A House bank
(Y) (N) Many House banks
(Y) (N) One House Bank plus one Account ID
(Y) (N) One house Bank + multiple account IDs different House Banks
(Y) (N) One house Bank + multiple account IDs in the same bank
(Y) (N) Many house banks and many account Ids
30. One Bank Account is mapped in SAP
(Y) (N) Account ID
(Y) (N) House Bank
(Y) (N) Bank Key
(Y) (N) G/L Account
(Y) (N) Country + Bank Key
31. The G/L Account Number is controlled through
(Y) (N) In G/L Account group
(Y) (N) Chart of account
(Y) (N) Field Status
(Y) (N) None of the above
32. The G/L account becomes a complete G/L account
(Y) (N) If we have added the company code to the chart of account
(Y) (N) If we have created both company code segment and chart of account
segment
(Y) (N) If we have created chart of account
(Y) (N) If we have copied the chart of account segment from another company
code
33. If we are using the same chart of account in more than one company code
(Y) (N) The company code segments are same in all company codes
4
5. ACADEMY: MANAGERIAL AND FINANCIAL ACCOUNTING
FI PAPER: 10
(Y) (N) The account name and account number is the same in all company
codes
(Y) (N) The currency in the company code segment in all company codes is
the same
(Y) (N) The group account number & the alternate Account Number can be
different in all company codes
34. The appearance of the company code segment of G/L account is based on
(Y) (N) The Account Group of Customer if it’s a reconciliation account
(Y) (N) The Posting Key
(Y) (N) Account group entered in the chart of account segment
(Y) (N) Group account number entered in the chart of account segment
(Y) (N) The Field Status Group in the G/L Master Record
35. Creation of Duplicate Accounts in AP can be prevented
(Y) (N) By using the match code before creating the new account
(Y) (N) By using sensitive dual control
(Y) (N) By switching on automatic duplication check
36. Major controls of Document Type include
(Y) (N) The Account Types allowed for posting
(Y) (N) The field status of header “text” & “reference numbers”
(Y) (N) The Posting Period
(Y) (N) Posting Keys
37. Which of the following statements are true
(Y) (N) Posting Keys are defined at the client level
(Y) (N) The account types allowed in line item posting based on posting key
(Y) (N) The field status definition “suppressed” & “required” cannot be
combined
38. Which of the following are true if we are using the same posting period variant for
several companies codes
(Y) (N) The same fiscal year variant has to be used to use same posting period
variant
(Y) (N) While Opening & Closing of periods of all company codes can be done
together his can also be done separately for each company codes as
long as
the definition and number of posting periods is same.
39. Which of the following statement is true
(Y) (N) We can open two period ranges during the time of closing process
(Y) (N) Document entry date determines the posting period and fiscal year
(Y) (N) If you display the balances of an account the transaction figures of the
posting
period are displayed.
40. By mentioning the baseline date, cash discount periods and cash discount
percentage
rate in the payment terms system will
5
6. ACADEMY: MANAGERIAL AND FINANCIAL ACCOUNTING
FI PAPER: 10
(Y) (N) Post the due date of invoice while posting the invoice
(Y) (N) Calculate the due date of the invoice and cash discount
(Y) (N) Calculate Cash discount in the payment term
41. When using the account clearing function the system chooses and matches those
existing items from the account that balances to 0. The system marks them as
cleared
and creates a clearing document.
(Y) (N)
42.Which of the following statements is true
(Y) (N) We cannot have a separate cash journal for each currency
(Y) (N) Special G/L indicators use the subsidiary ledger master records but are
connected to the general ledger via alternative reconciliation account
(Y) (N) A Down payment request is a noted item. It does not change any
account
balances. You can dun and pay automatically using down payment
requests
43. The specifications of permitted payment differences can be found in both types of
tolerance
groups. They control the automatic posting of cash discount adjustments and
unauthorized deductions
(Y) (N)
44. In Document header the reference field and the document header text are
modifiable.
(Y) (N)
45. All Reconciliation accounts and all general ledger accounts with open item
transactions
in foreign currency must be assigned to the revenue/expense accounts for realized
losses and gains(Y) (N)
46. Terms of payment are defaulted from master records when you post a document.
Terms
of Payment cannot be assigned at the time of posting the document or Entered
manually
if they are not assigned to the master record
(Y) (N)
47. R/3 system contains
(Y) (N) Database server only
(Y) (N) Application server only
(Y) (N) Presentation server only
(Y) (N) None of the above
(Y) (N) All of the above
48. Maximum Number of sessions a users can open when he logs on to SAP
(Y) (N) One
(Y) (N) Two
(Y) (N) Six
(Y) (N) Ten
(Y) (N) “N”
6
7. ACADEMY: MANAGERIAL AND FINANCIAL ACCOUNTING
FI PAPER: 10
49. Fiscal Year can be
(Y) (N) Year Dependent
(Y) (N) Year Independent
(Y) (N) Year Dependent & Year Independent
50. Fiscal year which is calendar year can have
(Y) (N) 12 Normal periods
(Y) (N) Less than 12 Normal periods
(Y) (N) More than 12 Normal periods
(Y) (N) User defined
51. Company code can have
(Y) (N) One local currency only
(Y) (N) Two local currencies
(Y) (N) Any Number of Local currencies if they have been defined in the
system
52. Posting in a company code are done in the G/L Account of
(Y) (N) Consolidated (Group) Chart of account
(Y) (N) Operative Chart of Account
(Y) (N) Country (alternate) Chart of Account
(Y) (N) All of the above
(Y) (N) None of the above
53. Retained Earnings Account is
(Y) (N) Specific to the Company code
(Y) (N) Specific to the Client
(Y) (N) Specific to the Chart of Account
(Y) (N) All of the above
54. Which of the following statement is true
(Y) (N) Company can use indirect exchange rate only
(Y) (N) Company can use direct exchange rate only
(Y) (N) Company can use both direct & indirect exchange rate
55. Which of the following statement is true
(Y) (N) Business areas are company code specific
(Y) (N) Business areas are assigned to assigned to company codes
(Y) (N) Business areas are assigned to assigned to group
(Y) (N) Business areas are activated and used for reporting across company
codes
(Y) (N) None of the above
56. No Terms of payment are proposed when you post a credit memo, you can default
them
from original invoice by entering the document number in the invoice reference field
else
enter “V” in the invoice reference field so that terms of payment entered in credit
memo are valid.
(Y) (N)
57. Payments can be blocked in during posting, in the customer/vendor master record
or in terms of payment.
(Y) (N)
7
8. ACADEMY: MANAGERIAL AND FINANCIAL ACCOUNTING
FI PAPER: 10
58. A block key and payment method from payment term is defaulted in the line item
when payment term is used.
(Y) (N)
59. Posting in a G/L account is controlled by
(Y) (N) Account group for the G/L account
(Y) (N) The Activity Type for the document
(Y) (N) Field status group in the company code segment
(Y) (N) All of the above
60. Which of the following is true
(Y) (N) Chart of account can have more than one retained earning account
(Y) (N) Chart of account can have one retained earning account only
(Y) (N) None of the above
61. Which of the following is true
(Y) (N) Account group control the document field status
(Y) (N) Account group control the number range of G/L A/c
(Y) (N) Account group control the master record field status in AR/AP
(Y) (N) All of the above
62. The vendor master contains data at
(Y) (N) General, Company code and Purchasing organization level
(Y) (N) Chart of Account level, Company code & Purchasing organization level
(Y) (N) Chart of Account level, Company code & Sales organization level
(Y) (N) General, Company code and Sales organization level
63. Posting using the special G/L indicator updates
(Y) (N) Sub-ledgers only
(Y) (N) G/L account only
(Y) (N) Both Sub-ledger and G/L account
(Y) (N) None of the above
64. The document date
(Y) (N) Has to be same as the posting date
(Y) (N) Must be in the same period as the posting date
(Y) (N) Can be in any period independent of the posting date
65. Vendor invoice can be entered in
(Y) (N) FI module only
(Y) (N) MM module only
(Y) (N) FI & MM modules
(Y) (N) FI, MM & SD modules
66. When the automatic clearing program is executed the base documents are
(Y) (N) Parked & Cleared in the system
(Y) (N) Posted and Cleared in the system
(Y) (N) Posted and Archived in the system
(Y) (N) Cleared in the system
(Y) (N) None of the above
8
9. ACADEMY: MANAGERIAL AND FINANCIAL ACCOUNTING
FI PAPER: 10
67. You can enter terms of payment in the company code segment or sales
area/purchasing
organization segment. The payment term defaulted depend on where the invoice is
posted.
The system does not check if the two are the same.
(Y) (N)
68. Where can the vendor master be created
(Y) (N) Centrally only
(Y) (N) In the MM module only
(Y) (N) In the FI module only
(Y) (N) Any of the above
69. A residual item posting in the vendor’s account
(Y) (N) Generates a new line item
(Y) (N) Reduces the value in the original invoice line item
(Y) (N) Reverses the original line item
(Y) (N) Generates a parking document
70. What is the maximum possible digit length of an internally generated vendor
number
(Y) (N) 6
(Y) (N) 10
(Y) (N) 12
(Y) (N) 18
(Y) (N) No limits
71. House Bank Ids can be
(Y) (N) Alphabets only
(Y) (N) Numeric only
(Y) (N) Alpha-numeric only
(Y) (N) Any of the above
72. Posting to an expense account normally needs
(Y) (N) A cost object assignment
(Y) (N) A revenue object assignment
(Y) (N) Either a cost or a revenue object assignment
(Y) (N) None of the above assignments
73. The customer master contains data at
(Y) (N) General, Company code and Purchasing organization level
(Y) (N) Chart of Account level, Company code & Purchasing organization level
(Y) (N) Chart of Account level, Company code & Sales organization level
(Y) (N) General, Company code and Sales organization level
74. When posting to a one time vendor or customer
(Y) (N) It is not possible to store the address details
(Y) (N) The address details have to be entered into the master before the
transaction is entered
(Y) (N) The address details are entered as part of the transaction
(Y) (N) None of the above
75. Which of the following sequence of creating a customer master account is
logically correct
(Y) (N) G/L, Bank, Customer
9
10. ACADEMY: MANAGERIAL AND FINANCIAL ACCOUNTING
FI PAPER: 10
(Y) (N) G/L, Customer, Bank
(Y) (N) Customer, G/L, Bank
(Y) (N) Any of the above
76. A down payment request makes
(Y) (N) A noted item posting in the vendor account
(Y) (N) An actual entry in the customer account
(Y) (N) A noted item posting in the customer account
(Y) (N) An actual entry in the vendor account
(Y) (N) An actual entry in the G/L account
(Y) (N) A noted entry in the G/L account
77. Where can a customer master be created
(Y) (N) Centrally only
(Y) (N) In the SD module only
(Y) (N) In the FI module only
(Y) (N) Any of the above
78. Incoming Payments
(Y) (N) Can post and clear vendor line items
(Y) (N) Can post and clear customer line items
(Y) (N) Can be cleared without posting
(Y) (N) Can be posted without clearing
(Y) (N) Can post, clear and reverse the base invoice
(Y) (N) None of the above
79. What is the maximum possible digit length of an internally generated customer
number
(Y) (N) 6
(Y) (N) 10
(Y) (N) 18
(Y) (N) 24
80. Which field on the customer master record controls whether we will accept an
incoming
payment for less than the amount invoiced
(Y) (N) Sort Key
(Y) (N) Tolerance Group
(Y) (N) Payment Term
(Y) (N) Payment Method
(Y) (N) Bank Key
81. What are the organizational entities for which the P&L and B/s can be generated
(Y) (N) Company Code & Business Area
(Y) (N) Company Code & Profit Center
(Y) (N) Company Code & Cost Center
(Y) (N) Profit Center & Business Area
(Y) (N) All the above
82. Which of the following statement is true
(Y) (N) One company code can use multiple chart of accounts
(Y) (N) One Chart of account can be used by multiple company codes
(Y) (N) One company code can use only one chart of accounts
(Y) (N) One chart of account can be used by only one company
10
11. ACADEMY: MANAGERIAL AND FINANCIAL ACCOUNTING
FI PAPER: 10
83. Which of the following fields can be changed in the document change mode
(Y) (N) Allocation
(Y) (N) Posting Date
(Y) (N) Document Date
(Y) (N) G/L Account Number
84. When a document is parked
(Y) (N) A temporary document number is generated and the document is not
posted
(Y) (N) The actual document number is generated and the document is not
posted
(Y) (N) The document is posted with a temporary document number
(Y) (N) The document is posted but can be reversed
85. What is the number of periods available in the calendar year
(Y) (N) 12
(Y) (N) 14
(Y) (N) 16
(Y) (N) 52
(Y) (N) 366
86. What is the maximum number of line items allowed in an accounting document
(Y) (N) 2
(Y) (N) 6
(Y) (N) 10
(Y) (N) 999
87. Which of the following statement is true
(Y) (N) One document type can use only one number range
(Y) (N) One document type can use multiple number ranges
(Y) (N) One number range cannot be used by multiple document types
88. What is the maximum possible length of a G/L account
(Y) (N) 6
(Y) (N) 10
(Y) (N) 18
(Y) (N) 999
89. The fields available for posting in a transaction are controlled through the field
status group at
(Y) (N) Posting key level only
(Y) (N) Posting key and G/L account level
(Y) (N) G/L account level only
(Y) (N) None of the above
90. A parked document can be
(Y) (N) Modified
(Y) (N) Deleted
(Y) (N) Posted
(Y) (N) All of the above
91. When is the business area level balance sheet self-balanced
11
12. ACADEMY: MANAGERIAL AND FINANCIAL ACCOUNTING
FI PAPER: 10
(Y) (N) Always
(Y) (N) It cannot be balanced
(Y) (N) When Business Area closing procedure is run
(Y) (N) When MM/PP/SD closing is completed
92. Which of the following statement is true
(Y) (N) Any accounting document can be reversed
(Y) (N) Only parked documents can be reversed
(Y) (N) Only cleared documents can be revered
(Y) (N) Once a document is posted it cannot be reversed
93. A transaction can span
(Y) (N) Multiple clients
(Y) (N) Multiple company codes
(Y) (N) Multiple business areas
(Y) (N) Multiple cost centers
(Y) (N) All of the above
(Y) (N) Only multiple company codes
94. The currency for a document is determined for
(Y) (N) The whole document
(Y) (N) Each line item
(Y) (N) Each Company code
(Y) (N) None of the above
95. The document currency
(Y) (N) Can be any currency
(Y) (N) Must be company code currency
(Y) (N) Must be same currency as the chart of account
(Y) (N) Must be the currency defined in the G/L master
96. The local currency of a transaction
(Y) (N) Can be entered by the user
(Y) (N) Is always the company code currency
(Y) (N) Is the currency of the chart of accounts
(Y) (N) Is determined by the country field in the customer/vendor master
97. What dictates whether a document line item requires a tax code
(Y) (N) Tax code in the vendor/customer master record
(Y) (N) Tax category in the G/L master
(Y) (N) Optional entry in every transaction
(Y) (N) None of the above
98. What sort key is used to sort line items by document currency amount
(Y) (N) 001
(Y) (N) 003
(Y) (N) 005
(Y) (N) 006
99. What is meant by the option open item management in the G/L account mater
record
(Y) (N) The items on the account are always open
12
13. ACADEMY: MANAGERIAL AND FINANCIAL ACCOUNTING
FI PAPER: 10
(Y) (N) The items on the account can never be cleared
(Y) (N) The items on the account can be cleared
(Y) (N) No balances are available for the account
100. What is meant by the option line item display in a G/L account master record
(Y) (N) Only the line items can be displayed
(Y) (N) Only balances can be displayed
(Y) (N) Line items and balances can be displayed
(Y) (N) Line items of reconciliation account are displayed
(Y) (N) None of the above
101. The sequence of business processes in MM can be described as
(Y) (N) Purchase requisition-MRP-Goods Receipt-Invoice-Payment
(Y) (N) Purchase requisition-Purchase order-Goods Receipt-Invoice
verification-Vendor Payment
(Y) (N) Purchase requisition-Purchase order-Invoice verification-
Vendor Payment
(Y) (N) Purchase requisition-Purchase order-Goods Receipt-Invoice
verification-Discount from Vendor-Vendor payment
102. It is must to create company code before any transaction processing in SAP
(Y) (N) True
(Y) (N) False
(Y) (N) Can’t Say
103. It is must to create company code before any transaction processing in SAP
(Y) (N) True
(Y) (N) False
(Y) (N) Can’t Say
104. Company codes & Business Area are legal entity for which you create B/s
(Y) (N) True
(Y) (N) False
(Y) (N) Can’t Say
105. Group is the highest level organization unit in R/3
(Y) (N) True
(Y) (N) False
(Y) (N) Can’t Say
106. The user specific defaults are possible if setting is done in
(Y) (N) User profile
(Y) (N) Company code parameters
(Y) (N) Session managers
(Y) (N) Terminal
107. Variant creation helps
(Y) (N) Calculating variance between actual & standard
(Y) (N) Processing repetitive transactions
(Y) (N) To copy repetitive field values in master creation
(Y) (N) To be standard selection criteria for repetitive use required to run
program
13
14. ACADEMY: MANAGERIAL AND FINANCIAL ACCOUNTING
FI PAPER: 10
108. Association between numbers from Group chart of account and country chart of
account can be established in
(Y) (N) Company code global parameters
(Y) (N) Master data of ledger a/c in operating chart of account
(Y) (N) Group company details
(Y) (N) Country details
109. For every transaction in SAP, system generates at least
(Y) (N) 4 documents
(Y) (N) 3 documents
(Y) (N) 2 documents
(Y) (N) 1 document
110. Document in SAP have the following sections
(Y) (N) Document Title & Line Items
(Y) (N) Document Header & Line Items
(Y) (N) Master Data & Transaction Data
111. Document Type is assigned to the Line Item section of document
(Y) (N) True
(Y) (N) False
(Y) (N) Can’t Say
112. Number Range ID is assigned to account type
(Y) (N) Document Type
(Y) (N) Account type
(Y) (N) Document Header
(Y) (N) Line Item
113. Document type allows more than one account types while processing the
particular document type
(Y) (N)
114. Following are account types
(Y) (N) A D M K S
(Y) (N) C D A M K
(Y) (N) S D M K T
(Y) (N) A D S K E
115. Document Numbers Can be
(Y) (N) System Generated
(Y) (N) User Defined
(Y) (N) Either System generated or User defined
(Y) (N) Can be created externally and internally at the same time
116. Posting key determines
(Y) (N) Account groups to which account numbers belong
(Y) (N) Debit/Credit, Account type and Field Status of the transaction
(Y) (N) Debit/Credit, Account group and Field Status of the transaction
(Y) (N) Debit/Credit, Account type and Field Status Group
(Y) (N) Debit/Credit, Document type & Field Status of the transaction
14
15. ACADEMY: MANAGERIAL AND FINANCIAL ACCOUNTING
FI PAPER: 10
117. Only one company code can be attached to posting period variant
(Y) (N) True
(Y) (N) False
(Y) (N) Can’t Say
118. Account type essentially controls
(Y) (N) Account type which can be assigned to the account code
(Y) (N) Which account – G/L, Customer, Vendor, Material or Asset can
be used in the line item of transaction posting
(Y) (N) Whether it has to be debit/credit posting
(Y) (N) Document type that can be sued
119. Account Group in context of G/L account determines status of fields in
(Y) (N) Transaction
(Y) (N) Chart of Account Segment
(Y) (N) Company Code Segment
(Y) (N) Does not control field status
120. For Negative posting, negative posting indicator needs to be checked
(Y) (N) In document type
(Y) (N) In company code global parameters
(Y) (N) In Reason Code properties
(Y) (N) In document type & company code global parameters
(Y) (N) In document type & Reason Code
(Y) (N) In document type & company code global parameters & reason code
121. Terms of payment can be assigned in
(Y) (N) G/L Master
(Y) (N) Customer or Vendor Master
(Y) (N) Transaction processing of Customer & Vendor Master
(Y) (N) None of the above
122.Baseline date is
(Y) (N) A date on which payment becomes due
(Y) (N) From which due date is calculated depending on the setting in
payment terms
(Y) (N) A base date after which document lapses
(Y) (N) None of the above
123. Due Date and cash discounts are dependent on
(Y) (N) Settings in company code
(Y) (N) Credit Management settings
(Y) (N) Payment Terms
(Y) (N) Payment Method
124. Currency assigned to company code master is
(Y) (N) Transaction currency
(Y) (N) Group currency
15
16. ACADEMY: MANAGERIAL AND FINANCIAL ACCOUNTING
FI PAPER: 10
(Y) (N) Local currency
125. Dunning process is used
(Y) (N) To make outgoing payments and clear documents
(Y) (N) To remind customers/vendor of account arrears
(Y) (N) To remit payments
126. Opening and closing of posting period is done
(Y) (N) In the customization of fiscal year
(Y) (N) In Special posting period
(Y) (N) In the Last normal posting period
(Y) (N) In customization related to opening and closing of posting period
(Y) (N) While defining posting period variant
127. Updating of Reconciliation account
(Y) (N) Happens at the end of the posting period
(Y) (N) Is run time update
(Y) (N) Happens only when closing a period
(Y) (N) Can be scheduled by the users
128. Posting key is defined at
(Y) (N) Document level
(Y) (N) Company code Level
(Y) (N) Chart of Account Level
(Y) (N) Client Level
129. Document Type is defined at
(Y) (N) Document level
(Y) (N) Company code Level
(Y) (N) Chart of Account Level
(Y) (N) Client Level
130. The Standard posting key used for G/L postings
(Y) (N) 40
(Y) (N) 19
(Y) (N) 39
(Y) (N) 31
(Y) (N) 1
(Y) (N) 50
131. In case of cross company code transactions
(Y) (N) One has to post two documents individually
(Y) (N) Posts document in once company and the system generates another
document in concerned company with common link of cross company
code transaction number
(Y) (N) System links documents based on user given number in cross-
company
code transaction field
(Y) (N) None of the above
16