Q1.

SAP AA : - Legacy Asset data transfer Configuration Steps

Ans : Following steps are there for asset data transfer
1. Set Company code status : SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer > Set
Company Code Status
Test status - You can change values by transferring asset data from a previous system, or by
posting.
Transfer status - You can enter and change values by transferring asset data from a previous
system, but posting is not possible.
Production status - The asset data transfer is complete. You can only change values by
posting.
Before the system goes live, it is essential that you set the system status to "production" (not test).
This rule applies even if you transfer asset data from your previous system in several phases over the
course of time. If you do transfer data in this way, you have to temporarily remove the "production"
setting of the the company code status. Company code status is generally set to '2' for conversion
purposes. This identifies the company code as being in test with data transfer always allowed. This
should be the start-up position for the asset company codes. Once the SAP company code has had at
least one Quarter end reported and verified after go-live, and the assets data is deemed stable, the
company code status will be set to '0'.
0 Asset data transfer completed 1 Asset data transfer not yet completed 2 Test company code
with data transfer always allowed 3 Company code deactivated - reporting allowed
2. Specify sequence of depreciation areas :SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer > Specify
Sequence of Depreciation Areas
In this field you define the order in which you want to update depreciation areas with values
during legacy data transfer. You determine this sequence by entering a relative number in this
field.
During the transfer of legacy data, the first depreciation area to be transferred is generally the
book depreciation area.
In this step, the sequence of the depreciation areas for the data takeover transaction is
specified. If there are additional depreciation areas for local / fiscal purposes, the sequence
for the depreciation areas may be impacted.
3. Specify Transfer date / last closed fiscal year : SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer >
Parameters for Data Transfer > Date Specifications > Specify Transfer Date/Last Closed Fiscal
Year Status
Q1.1 What is Asset take over date :- value date for legacy asset data transferred
Calendar date establishing the effective date of the legacy data transfer of fixed assets to the
SAP System. This is the date as of which the transferred assets are managed in SAP Asset Accounting.
You have to enter this date before starting the asset data transfer. In most cases, the transfer date will
be the last day of a fiscal year. All transactions starting in the new fiscal year are then carried out only
in SAP Asset Accounting. The values transferred are the cumulative values at the end of the fiscal year.

The transfer date can also be during the fiscal year. When the transfer date is within the fiscal year,
the values transferred are the values as they stand at the end of the last closed fiscal year before the
transfer date. The transactions since the start of the current fiscal year, however, also have to be
transferred. This is necessary in order to create the asset history sheet. This field is only ready for
input if the company code is not yet live. The system uses this date to determine the last closed fiscal
year.
4. Specify Last period posted in previous system ( transfer during FY ) :-SAP Reference IMG >
Financial Accounting > Asset Accounting > Asset Data Transfer > Parameters for Data Transfer >
Date Specifications > Specify Last Period Posted in Prv. System (Transf. During FY)

The following step is only necessary if you want to perform an old assets data takeover during the fiscal
year. In this case, you must specify the period up to which depreciation was posted in the previous
system. This period refers to the posted depreciation that is to be transferred during old assets data
takeover.
In this field, the system enters the period, for which depreciation was last posted. If the legacy data
transfer is carried out during the fiscal year, you must update this field manually.
This field is not available for input if there is no legacy data transfer during the fiscal year, or if
depreciation is not posted in this depreciation area.
If the asset takeover date is during a fiscal year, e.g. 31.03.2006, then the last period in which
depreciation postings were made in the legacy system must be specified. This setting is maintained in
each client. This configuration is maintained directly in each client
5. Transfer Foreign Currency Areas Manually :- SAP Reference IMG > Financial Accounting >
Asset Accounting > Asset Data Transfer > Options > Transfer Foreign Currency Areas.

You only need to carry out this step if you manage depreciation areas in foreign currencies.
In this step, you determine that foreign currency areas can receive values during old assets data
takeover. Then the depreciation areas are not supplied with values from another area by the system,
although they are defined as dependent areas by the Customizing settings. This specification can only
be made for areas that are managed in foreign currency.
Using this indicator, you specify that you will provide values for the foreign currency area during the
legacy data transfer. The system then does not provide values itself for the area (by taking over values
from another area, with no changes allowed) as it normally would.
You can only make an entry in this field for an area which is managed in foreign currency.
For any Depreciation area with foregin currency values fixed at the Group Rate as at the takeover date,
the takeover values for this depreciation area is calculated manually/automation tool.
Please note that if any change to depreciation area sequence is undertaken, that the manually input
flag will change position and will require updating.
6. Recalculate Depreciations for previous year :- SAP Reference IMG > Financial Accounting >
Asset Accounting > Asset Data Transfer > Parameters for Data Transfer > Options > Recalculate
Depreciation for Previous Years

Set this indicator if you want the system to newly calculate accumulated depreciation from past years
during the legacy asset data transfer.
You can recalculate the accumulated depreciation from the past, based on SAP depreciation rules,
when a depreciation area is newly entered the values from a depreciation area should be recalculated
in the R/3 system.for example, conversion data is not available for this depreciation area for these

assets. This recalculation is based on the condition that the acquisition value was acquired completely
at the time of capitalization. However, for the book depreciation area, this is only possible in company
codes that are still in test mode. You can also recalculate accumulated past depreciation for individual
assets using the transaction "change old assets" (Function: recalculate values) after the takeover of
data from your previous system.
7. Set Reconciliation Account manually :- SAP Reference IMG > Financial
Accounting > Asset Accounting > Preparing for Production Startup > Set Reconciliation
Accounts - TCODE: OAMK (OAK5 - for automatically set)
This step is required for conversion purposes. Carried out directly in client during cutover. By default
the relevant GL accounts will have been created as reconciliation accounts. As part of the conversion,
the flag is removed from the GL accounts per asset class per company code. After the balances have
been loaded, the reconciliation flag is reset. OAMK allows this to be carried out manually. Once they
are set as reconciliation accounts, the system will only post to them via Asset Accounting from this
point onwards. This is maintainable in each client except production where this step is managed by
the cutover strategy.
Q2 Difference between Revised schedule 6 and schedule 6 Reporting ?

Ans :- 1. In revised schedule 6 , there is clear distinction between current ( less

than 1year ) and non-current asset & liabilities. 2.There used to be proposed
dividends and tax on dividends in P/L stmt in schedule 6 but in revised schedule 6
both are under the head of reserve and surplus in balancesheet 3. In schedule 6,
capital advance and CWIP are under fixed assets but in revised schedule 6, Capital
advance is under loan and advance section and CWIP is under fixed asset. 4. In
revised schedule 6 there is clear distinction between investment in mutual fund as
current asset ( less than 1year ) and non-current asset ( more than 1 year )
Q3. Duplicate invoice check in SAP ??

Ans :- The Duplicate Invoice check carried out by the system will depend upon
whether the invoice is :- FI Document or Logistics Invoice document

1. FI invoice :- 1.1 Whether reference document number is not filled up in such

cases fields checked are : Company code, Currency, vendor, invoice date,
amount in document currency
1.2 Whether reference document number is filled up in such
cases fields checked are : Company code, Currency, vendor, invoice date,
reference document number
2. Logistic Invoice verification :- Following fields are checked to check
duplicate invoices : Company code, Currency, vendor, invoice date, reference
document number, Gross invoice amount.
Q4. Bad debt configuration in SAP??
Ans :- There are 3 ways of doing adjustment for bad debt.

1. Individual value adjustment special G/L transaction E -> Transaction is

entered in customer account with special G/L E which is transferred to
individual value adjustment for receivable ( BS account managed on open
item basis ) using tax code of zero percent for posting to expense from
individual value adjustment ( P/L Account ).If debt is irrecoverable the
receivable is cleared from customer account and the amount is posted to
account for depreciation of receivable. The sales tax is adjusted in the
posting
2. Flat rate individual value adjustment
Following are steps for bad debt configuration.
2.1Define Method :- SPRO > IMG > Financial Accounting > Accounts Receivable and
Accounts Payable > Business Transaction > Closing > Valuate > Reserve for Bad Debt >
Define Methods.
2.2Define accounts for reserve for bad debt :- SPRO > Financial Accounting >
Accounts Receivables and Payables > Business transactions > Closing > Valuate > Define
Accounts for Reserve and Bad debts
Transaction Code: OBXD

Enter Chart of accounts and press enter and Select Debit/credit and
provision method under accounts are determined based on.
2.3 Special G/L account for bad debt - FBKP :- Select account type, Special G/L
indicator and enter reconciliation account and special G/L account
2.4 Transfer posting for doubtful receivable :- Tcode :- F103
3. Flat rate value adjustment- JV
Expense from flat rate value adjustment
To value adjustment
Q5.

FI SD Integration part ( Order to Cash process ) ??

Ans :- In this part, we learn about SD and FI integration point.

Whenever we sale a finish material to customer, then the customer have to pay for
that. We send a bill to customer. In that position all billing document which is
happens to sales and distribution module will be posted into FI module. The account
entry of respect to the billing always have two sides
One side is Customer account and other side will be revenue account.
For example:

Customer A/c Debit Revenue A/c Credit.

As per SD module, the customer account will be picked from customer master data,
which is maintained from SD module. We just need to configure the revenue
account and if there any discount and surcharges account. We have to do that via
access sequence, access sequence is just a SAP terminology to determine the G/L
accounts. SAP provides 5 ways to determine G/L account in SD modules.

These are
1

Cust. Group /Material Grp /Acct Key

Cust. Group /Account Key

Material Grp/Acct Key

General

5 Acct Key
The assigned G/L accounts are used to post the discount and revenue and any kind
of surcharges.
To configure this
Go to Path = SPRO-IMG-Sales and Distribution-Basic Functions-Account
Assignment/Costing-Revenue Account Determination-Assign G/L Accounts or T-code
= VKOA
You can see the below screen and you can also see the default table and description
for above 5 ways.
First system checks the first table entry Cust.Grp/MaterialGrp/AcctKey. If any G/L
maintained here then system will go to the transaction and the particular billing
document, then system search the combination of customer group and material
group. If system will find any G/L, then system will go through the G/L, if system
doesn't find the G/L, then it will search the next table.
Customer group is maintained in Customer master Data, Material Group is
maintained in Material Master Data, Account key is maintained for condition type in
pricing procedure.
The account keys are also maintained in calculation schema in Pricing procedure.
The accounting entries with respect to the billing will generally result in

o
o

Debit Customer account

Debit Freight-out account

Credit Revenue account

Credit Excise Duty Payable account

Credit Sales Tax Payable account

Hence, primarily, one side of the account is a Customer and the other is a revenue account. The customer
account gets picked up from the customer master data and the revenue account is configured based on certain
inputs so that correct account is hit during FI posting. This automatic account determination is configured not
only for revenue, but also, other elements like Freight, surcharges, sales deductions etc.
The account determination can be done to be based on the following criteria:

Application

Condition Type

Chart of Accounts of Company Code

Sales Organization

Customer Account Assignment Group

Material Account Assignment Group

Account Key

http://scn.sap.com/docs/DOC-46903

Q6. FI MM Integration part ( procure to pay process )??

Ans :- Every movement of goods is followed by movement type only and without movement type use /
without help of movement type - no goods movement is possible in SAP. During goods movement of
transaction posting, movement type trigger transaction event key and G/L account assignment triggers
based transaction event key (OBYC) with valuation class where valuation class determines the valuation
class available in material master which is used for transaction posting. For automatic account
determination, the vital direct parameters involves are movement type, valuation class, chart of account,
valuation area, business key (transaction key), valuation grouping code{ valuation modification or
valuation modifier}, account grouping code{general modification or general modifier },nature of G/L
account ,posting keys and value string. The valuation class (in accounting 1 view) is most important

for automatic account posting purpose. Valuation class is used to group together several material
with their same attributes, so that we can carry the same account determination for various
material. Every material has a valuation class, many materials can contain same valuation class.
As we know the valuation class is link with material type via account category reference. The
valuation class will be for Raw material, Semi-finished, finished goods. We can differentiate
valuation class as per our business requirement. Valuation class and Movement type is used for
the G/L determination. Movement type is used for all types of material movement. Suppose if
you receive a material from a vendor, a movement is happens for the movement. If we transfer a
material from one location to another, a movement type is happens for the movement. It means,
whenever we do a off-setting entry, a movement type will be created for that. For various
movement type, SAP defines a G/L account for the material movement. We know about these
account, Inventory a/c for material master and GR/IR account is a provision account for vendor.
Direct t-code OBYC :- For different different movement type, the account entry is done via
different transaction event key.
If any movement type hits the inventory entry then it will hit the BSX transaction event
key..If any movement type hits the off-settings entry then its hit the GBB transaction event
key.If any movement type hits the provision entry then its hit the WRX transaction event
key.

From MM side its Valuation class and for FI side its G/L account. When we do a movement type,
the movement type finds the valuation class for the material, and post the amount to this G/L
account which is assigned to this particular valuation class.
Q7. Difference between assessment and distribution cycle in SAP ??

Ans :- Distribution:- 1. Reposting of primary costs 2. Sender cost centers are credited
with a primary cost element 3. Receiver cost centers are debited with a primary cost
element 4. Information on senders and receivers contained in the document 5. List of
origins not maintained in the CO document
Assessment: 1.Reposting of primary and secondary costs 2. Sender cost centers are
credited with a special secondary cost element (assessment cost element) 3. Receiver
cost centers are debited with the same assessment cost element 4. Information on senders
and receivers is contained in the document 5. List of origins is not maintained in the cost
accounting document. 6. The original cost element is lost during the allocation procedure.

1. Assessment is method of allocating primary and secondary costs in cost

center accounting and activity based costing
Example : Common cost incurred for factory cafeteria are booked to cost center
Z using primary cost element 400100 ( amt $100 ). During period end closing
costs are to be allocated to cost centers A,B and C in the ratio 50% , 20% and
30% resp.
Distribution :
Sender Rule : Posted Amt
Sender Cost Center : Z
Receiver Cost Centers : A,B and C
Receiver Tracing Factor : %for each cost center
When distribution cycle is executed cost center Z will be credited by $100 and
cost centers A,B and C will be debited with $50, $30 and $20. All the posting
made using primary cost element 400100
Assessment :
Assessment Cost Element : 600100
Sender Rule : Posted Amt.
Sender Cost Centers : Z
Receiver Cost Ceneters : A,B and C

Receiver Tracing Factor : %for each cost center

When assessment cycle is executed cost center Z will be credited by $100 and
cost centers A,B and C will be debited with $50, $30 and $20.
In assessment all the posting made using secondary cost elements.
The advantage of assessment cycle is original posting made to primary
cost elements are retained.
Flow of data in 2 stages
1. From FI to CO and
2. Flow of data within CO
For second one take example from internal order to cost center using
secondary cost elements.. Sometimes also called assessment cost element to
settle your internal order to cost center.
The posting date of actual allocation is always the last day of calendar month
and posting date of plan allocation is always first day of calendar month

Q8. MIS Development ???

Ans :- It was for managerial reporting wherein several matrix reports were issued
on monthly basis to management. As TOI being Media Company, the source of
revenue is ad which we normally see in papers. The revenue is directly allocated to
brands TOI,ET etc. Requirement to have reporting on each individual
publications,branch etc We have made provision to allocate this revenue to
individual publication based on their contributions to sales as fixed percentage.
Using tcode 9KE0 (To move $ between profit centers on the same GL Account/Cost Element

Note: you can move $ between GL accounts/cost elements as well, but

this will cause Profit Center accounting to disagree with the General
Ledger

When it is not necessary to update Profitability Analysis, GL, or Cost Center

Accounting ) . On similar line we have the cost of brands eg ink and material be
allocated to individual publications, branch etc. Using tcode KB11N ( KB11N is
manual reposting of costs between cost objects. you can correct the CO
postings by reversing the original postings. It will not accept secondary cost
element reposting.If your requirement is to allocate the costs to the
Secondary cost element, use transaction code KB15N.)

Pages printed SKF posting waste paper sales profit centerwise on plant wise
to 9KE5 and ink material machine plant cost center wise KB31N

KAH3 HIERARCHY CCREATED Pl STMT WISE

IN COST DVC PAPER INK MATERIAL

AFC STAFF COST CORPORATE ENTAINMENT EXP.

SVC DISTRIBUTION EXP AND DIRECT MARKETING COST

COST ALLOCATION CYCLE RUN KSU5

Q9. What are the important fields to be updated in the vendor master in
order to make a vendor payment via NEFT or RTGS?
Ans :- Update Reference field in bank details of payment transaction tab in vendor
master data with IFSC code and bank account number of vendor in bank details
Q10. BankAccounting
Q10. 1. What are the types of Bank Accounts created in SAP, how many bank
accounts are required in order to carry out bank reconciliation in SAP?
Ans :- We normally have bank accounts for collection and payment
Q2. What are the types of Bank reconciliation available in SAP?
Q3. What are the Universal formats accepted for Auto BRS?
Ans : MT940
Q4. Explain the configuration for Auto BRS.
Q5. What journal entries are posted after bank reconciliation?
Q11 . General Ledger
Q11.1. What is a GL accounts, explain the Tabs and the field contained in the master
data? What are the types of GL account?
Q2. How is the foreign currency valuation done in SAP? What is the configuration
required?
Q3. What is the significance of Post automatically only tick in a GL account?

Q4. How is the service tax payment and TDS payment managed in SAP?
Q5. What are the Month End and Year End activities carried out in SAP?
Q11.6. What is the standard method used for clear the GRIR clearing
account?
Ans : - Configure automatic clearing of GR/IR / Regrouping of items at
balance sheet date.
1. Define adjustment accounts for GR/IR clearing
Path: IMG-F/A-G/L/A-Business Transactions-Closing-Reclassify-Define adjustment
accounts for GR/IR clearing
Double Click on BNG Transaction Key
System will ask you chart of accounts update it.
Again update the following
Reconciliation account: Enter the GL code i.e. GR/IR clearing account (Goods
Receipt/Invoice receipt)
Adjustment account: Enter the GL code i.e. GR/IR correction account
Targ. Acct : Enter the GL code GR/IR Invoiced but goods not yet received
Again Double click on GNB Transaction Key
System will ask you chart of accounts update it.
Update the following: Reconciliation account: Enter the GL code i.e. GR/IR clearing account (Goods
Receipt/Invoice receipt)
Adjustment account: Enter the GL code i.e. GR/IR correction account
Targ. Acct : Enter the GL code GR/IR Shipped not invoiced

Do the above steps.

The goods receipt/invoice receipt (GR/IR) clearing account is a provision account, and is posted
to whenever you receive goods that have not been invoiced yet or whenever you receive invoices
for goods that have not been delivered yet.
In this activity you define the numbers of the adjustment and target accounts for the automatic
postings for the GR/IR clearing account.
Transfer postings have to be made at the balance sheet date to reflect the goods invoiced but not
delivered and the goods delivered but not invoiced.

Transaction code F.19 analyzes the GR/IR clearing account and posts adjustments entries for
outstanding amounts to adjustment accounts. It makes the offsetting entry to the account for
goods delivered but not invoiced or to the account for goods invoiced but not delivered (target
account).
Automatic clearing F.13 ( Criteria for automatic clearing is maintained in tcode OB74 )
and manual clearing are F-03

Q7. What are primary and secondary cost elements?

Q11.8. What is the transaction used to post to a specific ledger (leading
ledger or non-leading ledger), what are the limitations while posting such
entries?

Ans :- You use clearing specific to ledger groups if you perform parallel accounting using the ledger approach (and not the account
approach). Clearing specific to ledger groups and making postings specific to ledger groups You can use the function for all items that, due to
parallel accounting, are posted to multiple ledgers and valuated differently in those ledgers, in particular for provisions (such as provisions for
commission, rebates, or process risks, or provisions for creating and checking year-end closing). If you set the Clearing Specific to Ledger
Groups indicator for a G/L account managed on an open item basis, ledger group-specific postings can be made to this account. In this way,
you have a ledger group-specific view of the account. Clearing is also performed for specific ledger groups. This means that items that you
have posted in a specific ledger group can only be processed further within the same ledger group. If you have posted provisions, for
example, to specific ledger groups, you also clear those provisions for those specific ledger groups.
If you set this indicator, it replaces the following indicators:

Open Item Management

Line Item Display

Consequently, once you have set the Clearing Specific to Ledger Groups indicator, you cannot set either of the other indicators. You can only
set the Clearing Specific to Ledger Groups indicator for balance sheet accounts. The indicator is only visible if you have activated new
General Ledger Accounting in the current client and if you have defined more than one ledger for the company code.
As with the previous transactions, you can now post documents for specific ledger groups using the transactions Enter G/L Account
Document for Ledger Group (FB50L) and General Posting for Ledger Group (FB01L).
Furthermore, you can use the following new transactions:

For clearing: Transactions Clear G/L Account for Ledger Group (FB1SL) and Post with Clearing for Ledger Group (FB05L)

For automatic clearing: Transaction Automatic Clearing Specific to Ledger Groups (F13L)

Q11.9.what is the transaction to post to Tax accounts directly?

Ans :- The tcode to post to tax account ( created with tax category input or
output ) that does not require tax code entry is FB41- Post tax payable
Q12. What is purchase price variance ??
Ans : - Accounting entries during MIGO :- If there is price difference between
standard price in material master and Purchase order price, the difference is
identified as purchase price variance and the accounting entry during GR :
Material A/c Dr
To GR/IR clearing a/c Cr
Debit / Credit Purchasing price variance A/c
During invoice receipt if there is difference between purchase order price and
invoice receipt accounting entries are as follows:GR/IR clearing a/c Dr
To Vendor a/c
Debit / Credit Purchasing price variance A/c
The purchase price variance in the SAP system is mapped to the PRD transaction
key for account determination. The general ledger account for the PRD transaction
key is determined on the basis of valuation class and valuation area. Hence, there
can only be one purchase price variance general ledger account for a material type
in a plant
Q13. Intercompany Transaction configuration
Ans :- 1. Check for document type allowing for intercompany posting

tcode :

OBA7
2. Create clearing G/L account in both company codes using tcode FS00

3. Prepare cross company code transactions using tcode OBYA

4. Prepare cross company code for manual payments using tcode OB60
5. Prepare cross company code for automatic payments using tcode FBZP
6. Display intercompany transaction using tcode FBU3