SAP FI Qu- Ans
SAP FI Qu- Ans
SAP FI Qu- Ans
SAP ERP addresses the core business software requirements of midsize and large
organizations in all industries and sectors. SAP ERP includes four individual solutions that
support key areas of enterprise resource planning: human capital management,
financials, operations, corporate services.
All the SAP Finance (FI) related business transactions and evaluations
are represented at the company code level. Because company codes
are the central organizational units of an external accounting system.
You must define at least one company code (per client) to implement
the FI component in SAP S4 HANA Financials for your organization. If
you want to manage the accounting for several independent
companies simultaneously, you can set up several company codes for
the same client.
When you implement other components of SAP along with FI, you
need to create assignments between the company codes and other
organizational units to ensure data transfer between them. For
example, you need to assign one or more company codes to a
company, credit control area, controlling area and so on.
If you want to create financial statements for business areas, you must
make sure that the Business area field is ready for input in all the line
items.
To post items in a business area, enter the business area when you
enter the business transaction. However, the business area can also
be derived from other account assignments, such as the cost center.
To enable the system to do this, you must define the business area in
the cost center master record.
The field status enables us to control the display and maintenance of the
master data of an account. We can set any one of the following as the status of a
field:
Hide: For fields that you do not use
Display: For fields whose values must not be changed
Required Entry: For fields in which you must enter a value
Optional Entry: For fields that can contain an entry, but are not required
You can set a common field status for all fields of a group.
The field status is generally controlled by the account group. You usually only
use transaction specific controls to specify what can be edited when changing
master data.
There may be instances when you do not want specific fields to be modified by
anyone after the master record has been created. For example, you set the currency
of your cash account to INR, and
you do not want anyone to be able to modify it. In this case, in Customizing for
G/L Accounting, under Define Screen Layout for Each Transaction → Change assign
the status Display to the relevant
field.
For each field, SAP S/4HANA takes the field status definitions from the
account group and the transaction into consideration and uses the one with a higher
priority.
The following order applies in SAP S/4HANA, with decreasing priority:
● Hide
● Display
● Required Entry
● Optional Entry
We can use the following methods to create the G/L account, chart of accounts
segment,and company code segment:
1. Create both segments simultaneously (centrally).
2. Create a chart of accounts segment followed by the company code segment.
3. Copy the following components:
- Copy an individual G/L account: Copy it with reference to another G/L
account.
- Copy the company code segment: Copy the entire company code
segment.
4. Transfer Data: S4/HANA Migration
A sort key is a field in your table that determines the order in which the
data is physically stored in the database. Sort Keys are used to populate the
Assignment number field in the line items
of customers or vendors or general ledgers. The content of this Assignment
number field can be populated in a customer or vendor or general ledger document
when the document is created: either
manually. or automatically by the system. Whenever a document is created,
the Assignment number field in the document line items will be populated
automatically, if the requisite sort keys are
assigned to the customers or vendors or general ledgers master record. For
example, if the sort key is set Posting Date in the business partner master record,
then the assignment field in the
business partner line item is filled with the Posting Date. Similarly, if the sort
key is set to the purchase order number in the business partner master record, then
the assignment field in the business
partner line item is filled with the purchase order number.
Posting Periods are define in Fiscal year Variant. Posting period is a period
within a fiscal year for which transactions are posted. When posting a
transaction, transaction dates will be required to
be in an open posting period. When entering a document, among other items,
you enter the posting date – the system automatically determines the posting period
and fiscal year based on the posting
date entered. To prevent documents from being posted to an incorrect posting
period, you can close certain posting periods.
Usually, the current posting period is open and all other periods are closed. At
the end of a period this period is usually closed and the next period is opened.
During period closing, you open special periods for closing postings. During
closing, two period intervals must be open at the same time. Therefore, two period
intervals can be entered in the
posting period table. In the document header, the periods assigned to the
account type "+" are checked.
This is the first check. The account type.+. must therefore be open for all
periods that are supposed to be open for all other account types. The posting period
variant must contain at least the account
type +.
Posting periods can be handled differently for different account types, that is,
for a certain posting period, postings to customer accounts may be permitted while
postings to vendor accounts may not.
Secondary Cost Elements are those which are created only in controlling and
does not affect the financials of the company. It is used for internal reporting only.
The postings to these accounts do not
affect the Profit or Loss of the company. It can be used for internal allocation
purpose. Cost Elements track the type of costs or spend.
The following cost element categories can be used for secondary cost
elements :
21: Internal
settlement. ...
31: Order/project
results analysis. ...
41: Overhead rates. ...
42: Assessment. ...
43: Allocation of
activities/processes. ...
50: Incoming orders:
sales revenues. ...
51: Incoming orders:
other revenues. ...
52: Incoming orders:
costs.
Open item management ensures that all items that have not yet been
cleared are available in the system. Open items arise from every posting
transaction and reflect unfinished business
transactions. For example, an invoice item that has not yet been paid is
recorded as an open item in the account until it is paid and cleared. Open item
management
enables you to check which receivables and payables are outstanding. In
You can only move a document to the cold area of the database after all the open
items have been
cleared. You can see whether an item has been cleared in the line item
display or document display. The total of the items involved in the clearing
transaction must be zero. The account balance is
therefore always the total of the open items. Customer and vendor accounts
are always managed in this way. This allows you to monitor your outstanding
receivables and payables at any time. You
have to define open item management for G/L accounts in the master record.
Open items arise from every posting transaction in a contract account and
reflect unfinished business transactions.
Open item management enables you to check which receivables and payables
are outstanding.
Fallow Answer 7.
In SAP S/4 HANA, the business partner is the master record with which you
manage customers and vendors. The system offers a single point of entry to create,
edit, and display master data for
business partners, customers, and vendors.
Business Partner Categories
The term “business partner category” is used to classify a business partner as
a natura person (for example, a private individual), group (for example, community of
heirs), or
organization (legal entity or part of a legal entity, such as a department of a
company). When a business partner is created, the business partner category must
be selected (required entry).
Assignment of the business partner category is static and cannotbe changed
once the business partner has been created.
Business Partner Roles
A business partner can have several roles, such as a contract partner (FI-
CA), FI Vendor (FIAP), FI Customer (FI-AR), Customer (SD), Supplier (MM),
prospect (potential customer), or
business partner (general). In general, a business partner (BP) role
corresponds to a business context in which a business partner can appear and
provides the application-specific data.
You can create a business partner in one or more BP roles. Central data such
as name, address and bank details only have to be created once.
Business Partner Role Grouping
Using the SAP Business Partner, it is possible to group roles. If the roles are
grouped, one person can create, in one step, one customer or business partner in
different roles, for
example FI (FI-Customer) and SD (Customer). With this functionality a
centralized maintenance of Business Partners is feasible. Data records for all areas,
for example Financial Accounting, Sales
and Distribution, and Materials Management can be created at once.
Business Partner Grouping
Each business partner has to be assigned to a grouping when you create the
business partner. The grouping determines the number range (external or internal).
You cannot change
the assignment afterwards. You can define the groupings, their descriptions,
and the associated number range in customizing.
Tcode is FBZP.
Here you make specifications for all company codes involved in payment
transactions.
For each company code, you make the following specifications:
· Paying company code- You assign a paying company code to each
company code. This means that you can have one company code process payment
transactions centrally for several company codes.
· Cash discount and tolerance- The payment program uses these
entries to determine the cash discount strategy for the company code.
· Special G/L transactions- Specify which special G/L transactions
are to be settled for customers and vendors.
F = Down payment request
A = Down payment on current assets
Here you make the following specifications for the paying company codes:
Data for controlling the payment program- Here we specify the minimum
amount for which an incoming or outgoing payment is created. If you do not
want exchange rate difference to be generated when
the payment is in foreign currency you need to select the parameter. If you
want to make separate payment for each reference you need to select the
parameter.
Here you specify which payment methods are to be used in each country.
The following parameters are entered:-
1) whether it is an outgoing payment or incoming payment
2) payment classification – check, bank transfer
3) What master data specification required – address required, bank details
required etc.
4) Document type is attached
5) Which currencies are to be permitted?
Value date
You specify how many days elapse between the posting date of the payment run
and the value date at the bank, dependent on the payment method, bank account,
payment amount and currency.
Park Document- SAP provides the functionality to park and hold documents
in Financial Module. A parked document in SAP is a document saved but not yet
posted to general ledger accounts. Parked documents can be edited. SAP puts a
limit on the fields that can be edited in a parked document. SAP document parking
allows dual control of the document hence dual principle can be applied. Two
separate users can be involved in the processing of a document. The first user will
park and then the superior will verify and post.
The system will generate a document number using a document type the same way
it does for posted documents.
Hold Document- When you are entering data, you may be interrupted, or you
may not have all the data you need for entering a document, for example bank
charges or the appropriate cost center.
In this case, you can temporarily save the data you have
entered, and then continue with the document entry at a later time. If you want the
system to hold a document, it does not
have to be complete. Account balances are not updated
and the document data is not available for evaluation. A document number is not
assigned.
Organizational Levels
The structure of an enterprise is represented in the SAP R/3 System by the
following organizational levels:
Client - A grouping or combination of legal, organizational, business
and/or administrative units with a common purpose. Example: a corporate group.
Company code- This level represents an independent accounting unit within a
client. Each company code has its own balance sheet and its own profit and
loss statement.Example: a subsidiary company, member of a corporate
group.
Plant- Operational unit within a company code. Example: production facility,
branch office.
SALES DIVISION- In the SAP System you can define a division specific
sales organization. Product groups, i.e. divisions, can be defined for a wide-
ranging spectrum of products. Function of Distribution Channel: •Represents a
product line, Ex: Motorcycles, Spare parts, Services and so on.
SAP GROUP - The staff of a sales office may be subdivided into sales
groups. For example, sales groups can be defined for individual divisions.
Function of Sales Group: •They can be used for reporting purposes.
SAP SHIPPING POINT- Shipping points, are responsible for scheduling and
processing deliveries to customers, as well as replenishment deliveries to our
own warehouses. Function of Shipping Point: •Shipping is an integrated
module of SD processing. •The shipping point is the highest-level
organizational unit of shipping, that controls the shipping activities. •Each
outbound delivery is processed by exactly one shipping point.
130. What is chart of accounts? How many are there? Same as answer 7
Required: Document can not be posted without providing input in the field.
Optional: Document can be posted with or without providing input in the field.