OM SAP

SAP Treasury

2010-12-31T09:46:00.007+05:30

Treasury / Bank

Define House Bank

Tcode: FI12
Display all bank master records: SE16 – BNKA
Display Changes to all Bank Master data : SE8- RFBKABL0
Explanation:
- House bank: A HB is identified by a unique bank key. A HB is tied to a company code.
- Bank key: Enter the bank key. Available in US, Europe
- Bank Account number: Bank a/c number given in the bank statement
- GL a/c: GL account from COA to which this bank a/c is tied up
- Control Key: Used for US bank to identify whether a checking a/c (01) or a saving account (02). If no entry system defaults to checking account (01)
- The payment program uses the House bank ID and Account ID to determine the bank to be used for payment to customer / vendor
- Bank GL a/c in FS00 : Account ID together with the ID for the house bank uniquely defines a bank account

Data:

Company code	HB	A/C ID	GL A/C	Currency	Bank
1000	3200	3200	113600	EUR	Citibank
1000	1000	1000	113100	EUR	Deutsche	Use
1000	1000	1050	113150	USD	Deutsche

Electronic and Manual Bank statement:

EBS: It is an electronic statement sent by the bank which gives details of transactions done by the account holder. The EBS can be in the format SWIFT, BAI, Multicash etc. This statement is uploaded in SAP and it clears the various clearing account such as check out, check in to the main bank account
GL codes in our scenario:

Particulars	Main	Check In	Check Out	Bank Charges
HB	ANSH	ANSH	ANSH
Account ID	MAIN
Bank a/c number	13579	10002	10003
GL a/c number	113400	113108	113101	479000

Accounting Entries:
- Check Issues to Vendors:
  - Vendor a/c Dr.
    - To Check Out ( 113101)
- Check Received from Vendors:
  - Check In ( 113108) Dr
    - To Vendor a/c
When Bank statement (EBS) is uploaded in SAP following entries passed:
- For checks issues to vendors:
  - Check out (113101) Dr
    - To Main a/c ( 113400)
- For checks received from Vendors:
  - Main a/c (113400) Dr
    - To Check In (113108)

Make Global settings for EBS

Tcode: SPRO – Financial accounting – Bank Accounting – Business Transactions- Payment Transactions – EBS – Make Global settings for EBS
Explanation:

Enter COA: CAUS
Create Account Symbols.
Assign these account symbols to GL accounts
Create keys for posting rule
Define Posting Rule: Here assign posting rules to the accounts symbols created. For define posting rule refer to Top jobs Bank config.

Data:

COA	CAUS	GL account	Posting Rule
MAINBANK	Main Bank Account	113400
BANKCHGS	BANK CHARGES	479000	A105
CHECKIN	Check Received In	113108	A104
CHECKOUT	Check Issued Out	113101	A101

Additional steps for manual settings:

Tcode: SPRO – Financial accounting – Bank Accounting – Business Transactions- Payment Transactions- Manual Bank Statement – Create & assign business transactions
Explanation:
- Create Account Symbols.
- Assign these account symbols to GL accounts
- Create keys for posting rule
- Define Posting Rule: Here assign posting rules to the accounts symbols created. For define posting rule refer to Top jobs Bank config
Data:

Transaction	Posting rule	Text
CHIN	A104	Check received in
CHOU	A101	Check Issued Out
BKCH	A105	Bank Charges

Define variants for manual Bank statement

Tcode: SPRO – Financial accounting – Bank Accounting – Business Transactions- Payment Transactions- Manual Bank Statement- Define variants for manual bank statement

Define Posting keys and posting rule for check deposit

Tcode: SPRO – Financial accounting – Bank Accounting – Business Transactions- Check deposit – Define posting keys and posting rule for check deposit
Data:
- ACHKDEPOSIT
- ACHK

Create and assign business transactions;

Tcode: SPRO – Financial accounting – Bank Accounting – Business Transactions- Check deposit – Create and assign business transactions

Define Variant for check deposit

Tcode: SPRO – Financial accounting – Bank Accounting – Business Transactions- Check deposit – Define variant for check deposit
Data:
- A0001

Define number range for checks

Tcode: FCHI
- Checks can be printed on site using MICR (Micro encoding printer). MICR should be configured only to PRA / PRD. To avoid misuse of checks

Cash Journal

<< Refer TFIN>>

Manual Check Deposit

Tcode: FF68
Explanation:
- Before entering checks you need to define what entry variant you'd like to use and how do you want to post process the checks. Select from the menu path Settings – Specifications
- In the field Processing type you can also use key 4 – Further processing online, instead of 2 – Further processing as batch input (generate batch). In such case, after posting of checks, the system will not create batch input session, but will post the documents automatically. However, to complete the process you need to use the transaction code FEBA (Post process) to check the results of this automatic posting and eventually complete the postings
- Click Transfer value date
- Click <checkbox> Int. bank determin. . Instead of entering full bank account number, you can now use short bank name, defined in the system
- When you enter the check data and save your statement, the system will display a report (log) presenting which items have been cleared automatically and what is the number of items that still need to be cleared manually. This report shows postings separately for GL account and for sub-ledger (AR). In the column Errors you can see how many transactions needs to be processed manually. In this example
- Also refer the end user documentation
Accounting ® Financial Accounting ® Banks ® Incomings ® Check Deposit ® FEBA - Post process

Field Name	Description	Values
Start variant	You can change the variants at any time during memo record processing.	Example: A0001
Customer matchcode ID	Using this matchcode ID, the system searches for customers	Example: D
Processing type	Use this field to control whether postings via batch input are carried out online or as a background job.	Example: 4

FEBA Table:
- FEBKO

Import Electronic Bank Statement (FF_5)

Tcode: FF_5
Explanation:
- Using this function you can import bank statements into the system and then process them. This report can perform automatic postings or create batch input session. It posts to G/L accounts and to sub-ledger accounts
- For incoming payments, the notes to payee lines of the account statement can be searched either for document numbers or reference document numbers by specifying the selection field (BELNR or XBELNR). Thus, the relevant information for clearing customer payments is obtained.
- If you do not specify a selection field, the note to payee fields are not interpreted and you need to clear open items manually (use transaction FEBA – Post process)
- For outgoing payments, the system always searches for the document number
- BELNR number interval: Specify search criteria for incoming payments. The account statement will be searched for FI document numbers. This information is necessary for clearing customer payments.
- After posting electronic bank statement use transaction FEBA Post process account statement to check have all the documents been posted and post / clear manually some documents, if necessary

Create Bank Master Record (FI01)

Tcode: FI01
Explanation:
- Bank Master Records are stored in the bank directory. Their details are stored also in Customer / Vendor Master Data and are used by payment program to prepare payment documents. You can create new Bank Master Record using transaction FI01
- Bank Key: Bank key is the bank code. This field is country specific. Usually the bank key consists of first 8 digits of your full bank account number and is followed by "hyphen" –

Change Bank Master Data

Change Bank Master Data: FI02
Display Bank Master Data: FI03
Display Bank Master Data Changes : FI04
Explanation:
- On this screen system usually displays all the fields that were changed. In our example the value of the field Name of Bank was changed. To display more details regarding changes, double-click on this field. To check who is "responsible" for these changes, click Bank name field

Mark for Deletion Bank Master Data

Mark for Deletion Bank Master Data : FI06
Explanation:
- Cannot delete your bank master directly. Can only mark bank master for deletion. To completely remove the bank master from the database need to run a special archiving program

Edit Bank Chain

Edit Bank Chain : FIBPU
Display Bank Chain for Creditors/Debtors: FIBPS
Explanation:
- Bank chains are used to make payment via more than one bank, for example via the correspondence banks of the house bank, the recipient bank, or the intermediary banks. This document describes how to create a bank chain for customers and vendors
- Prerequisite: Customer / Vendor master records need to contain bank data: bank account & bank key
- Refer to top job documentation on FIBU

FEBA Post process

Explanation:

The transactions (line items) marked with green ticks have been processed automatically – system has found the relevant open items, based on reference document number and customer name and cleared them automatically. The transactions marked with red ticks need to be processed manually

Double-click the required check statement. System will display a document overview

To process this document, select from the menu path: Line items-Post

Account: Code identifying the Customer account

Select the required open item and click Save

S_ALR_87009895	VAT Report	Use this SAP transaction to view VAT reporting and to post VAT settlement. Transaction is run at month end after transactions have been completed. When settlement is run the balances of the 11005001 output tax and 22010000 input tax accounts are zeroed out and the balance of each is moved to the 12600000 VAT Settlement account.
SM35	Batch Input Monitoring	Use this SAP transaction to monitor and process batch input sessions to post all the applicable documents and perform all the database updates.

SAP VAT

2010-12-31T09:46:00.006+05:30

Adding VAT Codes

Check Calculation Procedure

Tcode: IMG - Financial Accounting- Financial Accounting Global Settings- Tax on Sales/Purchases- Basic Settings - Check Calculation Procedure – Define Procedure
Tcode : OBYZ
Explanation:
- Copy tax procedure TAXGB. Change it to TAXIN
- These are standard Tax calculation procedure provided by SAP.

Assign Country to calculation procedure (Check country assigned to a tax calculation procedure)

Tcode: OBBG
Tcode: IMG - Financial Accounting- Financial Accounting Global Settings- Tax on Sales/Purchases- Basic Settings - Check Calculation Procedure – Assign country to calculation procedure
Explanation:
- Each country has a tax calculation procedure assigned to it.
- Here we can check what tax calculation procedure has been assigned to the concerned company code.

Check Access Sequences, Tax Condition Type

Tcode: OBYZ

Tax Jurisdiction structure

Tcode: OBCD

Sales & Use Tax Automatic assignment

Tcode: OB40

Define Tax codes for Sales and Purchases

Tcode: IMG - Financial Accounting- Financial Accounting Global Settings- Tax on Sales/Purchases- Calculation – Define tax code for sales and purchases
Tcode: FTXP
Explanation:
- Here we define the tax rate for the tax code. Also map the G/L account to which tax amount postings are made
- Easiest way to create a new tax code is to copy the existing tax code whose tax rate has to be changed in FTXP. Change description & rate

Steps in SAP for creating a new VAT code : EMEA

(For Company code 730 Neon & reporting country XX say PT (say tax procedure TAX_NB):

Check for the gaps in the table T007A for the new tax code to be created. (We need to check that a 2 digit tax code can be created, & it does not exist already)
Go to Tcode FTXP. Copy from the existing tax code, change the %, change the description, check the account mapping & save the new tax code
Please note the following before creating the tax codes

Tax procedure	Tax code	Transaction Key	Account
TAXAR	1V	ESA	10002001
		ESE	10002002
TAXPT	1V	MWS	20001065
TAX_NB	1V	VST	11005000
Different	Same	Should be same

In different tax procedures, same tax code can be created. However the mapping of Transaction Key& Account should NOT change.
1. For example:
2. Tax code1V can be created in Tax Procedure TAXAR, TAXPT & TAX_NB. However, Transaction Key VST = 11005000 in all the tax procedures.
Never change an existing account mapping as that will affect countries which are already using that code
A tax code like 1V can have different tax rates in different tax procedures but ACCOUNT MAPPING remain the same. To check all tax rates used for a tax code use report S_ALR_87012365

VAT new Tax code Creation Business Process:
A Kintana is always required.
Approval should be taken from Winco Rebergen before creating any tax code.
We first create the tax codes in PSQ and ask the user to test them in PSQ. At testing stage also, Winco Rebergen, Florence ten Cate and Matti Uoti should be kept informed.
Once user tests the tax codes successfully, attach the sign off to the Kintana, create the new tax codes in PRD and inform all the parties mentioned above.

Advance Return for Tax on Sales/ Purchase

Tcode: S_ALR_87012357
Explanation:
- Page 1 shows totals for Output tax by Tax Code.
- Page 2 shows totals for Input tax by Tax Code.
- Page 3 shows totals for each company code selected, by Tax Code.
- Page 4 shows totals for all company codes selected, by Tax Code.
- It is necessary to clear the amounts in the Tax Clearing account to ensure that the tax payable/receivable to Accounts Payable or Accounts Receivable, is created in order to be paid via the automatic payment program (F110) or paid and cleared via the Incoming Payments (F-28) procedure. Although the above procedure calculates and posts the tax payable/receivable to the tax payable/receivable account, this account needs to be cleared and paid.
- The tax payable/receivable Account is managed as 'Open Item' and as such a clearing procedure needs to occur in order to pay the values to the Statutory Authorities. Therefore, the value of Tax to be paid needs to be identified. This can be achieved by an inquiry on the tax payable/receivable account in the general ledger by posting dates and unclear items.

Tax Posting (AP/AR)

Tcode: FB41

VAT Configuration

Tax on Sales/Purchases
	Description	Tcode
Basic Settings
Check calculation procedure	Check calculation procedure - condition types	OBQ1
Check calculation procedure	Check calculation procedure - access sequences	OBQ2
Check calculation procedure	Check calculation procedure - procedures	OBQ3
Check country assigned to calculation procedure		OBBG
Check and change settings for tax processing		OBCN
Fiscal Regional Codes	Define fiscal regional codes for Italy/Spain	OBAD
Fiscal Regional Codes	Define fiscal regional codes for other countries	OBAE
Calculation
Define taxes on sales/purchases codes		FTXP
Specify base amount		OB69
Posting
Define tax accounts		OB40
Define account for exchange rate difference posting		OBYY
Allocate tax codes for non-taxable transactions		OBCL

Configuration steps : Basic Settings, Calculation, and Posting
1. SAP uses condition types (e.g., MWAS sales tax and MWVS input tax) as the basis of a calculation procedure, which enables integration between the SD, MM, and FI modules.
2. Create an Access Sequence (MWST Tax Indicator) and underneath it an access code (10 (Table 3) Tax Code).
3. Create a calculation procedure for each country or jurisdiction for which you need one (for example, TAXF = sales tax for France and TAXIT = sales tax for Italy). Behind this you put a control procedure, which defines the calculation steps (TAXF).
4. Procedure TAXF Sales Tax – France:

Steps	Control	Condition Type	Description	From
100	0	BASB	Base Amount
110	0	MWAS	Sales Tax	100
120	0	MWVS	Input Tax	100
140	0	MWVN	Non Deductible input tax	100
150	0	NLXA	Acquisition tax credit	100
160	0	NLXV	Acquit ion tax debit	150

Next assign a country to a calculation procedure (AT Austria = TAXAT).
Check and change settings for tax processing as follows:

Process	MWS
Text	Output Tax
Tax Type	1 Output Tax
Not deductible	Not used here
Posting indicator	2 Separate line item

Define tax codes, which will be used in transactions. (Tcode: FTXP)

Country key	FR
Tax code	D1
Procedure	TAXF
Tax Type	V

Behind the VAT code define its properties
Tax code	D1 Deferred input tax - standard rate 19,6%
Tax Type	V Input tax
Check	Select if SAP to check calculation
Target tax code V1	This tax code transfer input tax to code V1 when related invoices area paid
Assign GL a/c to the tax code	Tcode FTXP / OB40. Maintained in table T030K When entering tax codes with no tax rate, entering 0 rate allows accessing them. Also need to assign GL a/c to these tax codes.

Finally, tax codes have to be allocated for non-taxable transactions, outside the scope of VAT (e.g., general ledger journal entries between accounts which require a valid tax code) – e.g.:
Input VN and Output AN. The codes are created in the normal way first, but with a zero percentage rate. Use Tcode OBCL to jump directly to where these tax codes are defined.
VAT Return configuration
When configuring VAT processing it is also necessary to maintain Table TRVOR (with transaction code SM31) and enter the company code and fiscal year against the ABAP which runs the advance tax return (e.g., RFUMSV20 for Italy and Spain prior to Release 4.6C) and against the ABAP which runs the document journal (RFBELJ10). Otherwise the report will not run and the error report does not tell you much except to point you towards Table TRVOR.
This table links the company codes to the ABAP used to run the document journal RFBELJ10 and to the ABAP used to generate the advance tax return RFUMSV00 (and previously RFUMSV20). It is essential to maintain it or the advance tax return will not run.

SAP General Ledger

2010-12-31T09:45:00.003+05:30

General Ledger
FICO Summary

Description	Tcode
Define Group Company	OX15
Define Company code	OX02
Edit COA	OB13
Copy COA	OBY7
Assign Company code to COA	Ob62
Define account group	OBD4
Define Retained earnings	OB53
Maintain Fiscal Year Variant	OB29
Assign Company code to FYV	OB37
Define Posting Period Variant	OBBO
Change Fiscal Period	OB52
Assign PPV to company code	OBBP
Create number range for company code	FBN1
Define document type	OBA7
Define document posting keys	OB41
G/L a/c default setting	OBU1
Define rules to change text in a field	OB32
Maintain Field Status Variant	OBC4
Assign Field status variant to company code	OBC5
Define Tolerance Group for employees	OBA4
Maximum Exchange Rate difference	OB64
Company code Global parameters	OBY6
Document Change	SE38- RFBABL00
Define Additional Local currencies	OB22
Assign Company code to Company	OX16
Check Tax calculation procedure	OBYZ
Assign Tax Procedure to Company code	OBBG
Check Access sequence	OBYZ
Define Tax code for sales & purchase	FTXP
Configure automatic (F.13) clearing	OB74
GL a/c for clearing differences	OBXZ
Define Foreign Currency valuation method	OB59
Define Adjustment a/c for GRIR clearing	OBYP
FI integration with CO	OBYB
FI integration with MM	OBYC
FI integration with SD	VKOA
Create GL a/c centrally	FS00
Copy GL a/c from source company code to target company code	FS15
GL a/c posting	F-02
Post incoming payments	F-06
G/L a/c line item display	FBL3N
G/L a/c analysis display	FS10N
G/L a/c MANUAL CLEARING	F-03
Post outgoing payment	F-07
Change posted GL document	FB02
Display GL document	FB03
Individual document reversal	FB08
Mass document reversal	F.80
Post / Park / Hold GL a/c document	FB50 FV50
Display GL hold document	FB11
Copy GL a/c to company code	OBY2
Automatic a/c determination	FBKP
GL post with clearing	F-04
Automatic clearing	F.13
User master data settings	FB00
Reset cleared items	FBRA
Recurring entry documents	FBD1 / FBD2 / FBD3
Display forex exchange rate	OB08
Post Accruals (Prepaid expense/ Accrual Income)	FBS1
Reverse accruals, if automatic reversal not selected	F.81
Cross company code documents display	FBU3
View / Change iDoc	WE02
GRIR a/c maintenance	MR11
Foreign Currency Valuation	F.05
GRIR Configuration	OBYC WRX
GRIR Regrouping	F.19
Carry forward of receivables / Payables in FI	F.07
Balance c/f of GL a/c	F.16
Define a/c group screen layout Vendor	OBD3
Create number range for Vendor	XKN1
Assign number to vendor	OBAS
Delete Vendor Master data	OBR2
Maintain Terms of Payment	OBB8
Create / Display / Change Vendor master	XK01 XK03 XK02
Block / Unblock Vendor master	XK05
Post Vendor Invoice	FB60
Post Manual payment	F-53
Displaying / Releasing vendor a/c balance	FK10N
APP	FBZP F110
Manual clearing of vendor invoices against payments	F-44
Display PO	ME23N
Change PO	ME22N
Search for PO	ME2B
PO Based Vendor Invoice / Credit Memo / Planned delivery cost	MIRO
Display PO based vendor invoice	MIR4
GLPCT table report	2KEE
GLPCA table report	KE5Z
AP/AR posting to PCA (One leg posting). This update table BFOD_A or BFOK_A as the case may be	F.5D
Periodic data transfer from FI- AP/AR (OI) to PCA	1KEK
Update PCA comparison ledger in period 0	2KES
Compare GL a/c's in FI with a/c in PCA	KE5T
Define a/c with screen layout for customers	OBD2
Create number range for customer a/c	XDN1
Assign number range to customer a/c	OBAR
Define alternative a/c for down payment	OBYR
Create / Change / Display customer master data	FD01 FD02 FD03 XD03 VD03
Display customer credit management	FD33
Change customer credit management	FD32
Display customer a/c balance	FD10N
Display and change customer line items	FBL5N
Manual clearing of customer invoices against payments	F-32
Manual clearing of customer down payments against customer invoices	F-39
Post a customer Invoice	FB70 F-22
Park customer Invoices	FV70
Post customer park invoices	FBV0
Post customer incoming payments	F-52
Customer down payment request	F-37
Customer down payment	F-29
Display blocked SD / customer invoices	VKM1
Customer Reason codes	OBBE
Reason codes table	T053R
Map reason codes to GL a/c	OBXL

Define Group Company

Tcode: OX15
Explanation
- A company is an organization unit. A company can comprise one / more company codes (For which separate FS can be prepared)
- All company codes for a company must work with same Operational COA & Fiscal year
- Company codes can use different currencies

Define Company code

Tcode: OX02
Copy company code along with all data : EC01
Explanation
- Legal entity. Separate BS & PL can be maintained
- Two options 1) Copy co. code 2) Edit co. code
- In copy co. code all Config, tables, assignments get copied. Edit them as per need. Copy co. code 0001. In 2nd option manually configure all assignments
- Local currency: Currency defined in company code. All accounts are managed in this currency. All other currencies treated as FC.
- Country Key: Specifies which country to be regarded as home country. System regards all other countries as foreign countries

Edit Chart of Accounts

Tcode: OB13
Copy Chart of Accounts : OBY7
Copy from an existing company code: EC01
Directory of GL Accts in COA: SE38 - RFSKPL00 / RFSKVZ00
Explanation
- GL accounts created at COA and then extended to company codes in which they are used
- Copy CAUS
- Define : COA key, Maintenance Language (English), Length of GL acct number(1-10), Manual / Automatic creation of CE, Group COA, Blocked ( A COA that is not completed can be blocked)
- COA grouped under account groups.
- Acct Group control number range, Field status of GL accounts in FS00
- Open Item Management: To be used for
  - Bank clearing acct,
  - Salary clearing acct.,
  - GRIR account
  - For these clearing accounts also select line item display
- Only balances in local currency: Selected for clearing accounts. This avoid gain / loss due to exchange rate difference
- If company codes intend to use cross-company code controlling, they must use the same chart of accounts.
- For balance sheet accounts, the balance is carried forward to the same account.
- For profit and loss accounts, the balance is carried forward to a retained earnings account and the profit and loss statement account is set to zero. A key (for example, X) is assigned to the account to which the balance is carried forward. You enter this key in the field "P&L Statement Type" in the chart of accounts segment.
- The field status enables you to control the display and maintenance of an account's master data.
  - You can assign fields that you do not use the status Hide.
  - Fields whose values must not be changed can have the status Display
  - For fields where you must enter a value, you can define the status Required Entry.
  - Fields that can contain an entry, but are not required, can be set to Optional Entry
- Cross company code controlling:
  - If company codes want to use cross company code controlling, they must use the same operational chart of accounts
- Group COA:
  - If company codes use different operational chart of accounts they can have group chart of accounts for consolidated reporting.
  - The group chart of accounts must be assigned to each operational chart of accounts. After you have done this, the Group Account Number field in the operational charts of accounts becomes a required entry field.
- Country COA:
  - Company codes use same operational COA. But they have local reporting requirements. So use country COA. Country COA GL a/c number is assigned in alternative reconciliation account no. Also since all company codes use same operational COA we can have cross company code controlling

Assign Company code to Chart of Accounts

Tcode: OB62
Explanation
- For each company code specify which COA to be used.
- Several company codes can use same COA.
- Operative COA : COA assigned to company code
- Country Specific COA: COA structures as per country legal requirements
- Group COA : COA structured as per consolidation requirements

Define Account Groups

Tcode: OBD4
Explanation
- Account group used to combine GL a/c's with similar functions. E.g. expenses, asset accounting, Cash etc
- Account Group determines:
  - GL a/c number interval in FS00 for the GL A/C created
  - Fields in GL master records (Required/ optional/hidden)
  - Can configure field status for the account group by selecting it and clicking field status icon

Define Retained Earnings

Tcode: OB53
Explanation
- At the end of Fiscal year system carries P/L balance to retained earnings a/c. This account appears in BS as P/L carry forward.
- For this you define one/more P/L statement a/c type (X, Y, Z…) & assign these PL statement a/c types to GL a/c ( retained earnings a/c) in the COA

Maintain Fiscal Year Variant

Tcode: OB29
Data : K4 ( Jan to Dec)
Explanation
- Sap allows up to 16 posting periods which reflect 12 months of the year & 4 special periods used for adjustments
- Fiscal Year normally has 12 posting period & 4 special period for yearend closing transactions
- Fiscal year can be Calendar Year ( Jan to Dec) / Not Calendar Year ( Apr to March)
- Fiscal Year (Not Calendar Year) can be year dependent or Not year dependent
- Year dependent fiscal year variant are used: If the start and end date of the posting periods differ from year to year. If one fiscal year has fewer posting periods than the others (shortened fiscal year)
- SAP standard FYV : K4 ( Jan to Dec), V3 ( Apr to March)

Assign Company code to Fiscal Year Variant

Tcode: OB37
Explanation:
- This control periods in which the company code will post

Define Posting Period Variant

Tcode: OBBO
Explanation:
- Here you decide which posting period is open for posting
- A separate variant for posting period is defined for every company code
- One PPV can be assigned to multiple company codes
- System derives posting period from posting date. If posting date falls in normal period can be posted in special posting period.
- If start & end date of each period is same every year, it is year independent PPV. If the period reconcile with calendar months it is calendar year PPV else non calendar year PPV.
- If the start & end date of period differ each year it is year dependent PPV
- To prevent documents from being posted to an incorrect posting period, we can close certain posting periods. We can have as many posting periods open as desired. Several company codes can use the same posting period variant.
- The account type + must be open for all periods that are supposed to be open for all other account types. However a/c type (S/D/K/M) may / may not be open

Open & Close Posting Period

Tcode: OB52
Explanation:
- Here specify which periods (Jan, Feb, Mar ...) are open for posting for each variant. There are 2 time intervals for both specify lower limit period, Upper limit period & Fiscal year.
- First enter periods permitted for posting for all variants. Next add entries for a/c type (D, K, A...) if periods to be restricted for specific a/c's
- Once the financial month-end close process is completed and statutory and management reports have been published, this transaction is executed a second time to close the general ledger for the period. This transaction is also used to reopen fiscal periods in the event that prior period adjustments are necessary. Once the fiscal periods are changed, the inventory accounting period must also be changed to allow posting of goods issues and goods receipts in the new fiscal period.

Assign Posting Period Variant to Company Code

Tcode: OBBP

Create number range for Company code

Tcode: FBN1
Explanation:
- Here we create number ranges
- Each number range specify a interval from which document numbers are selected
- Number range can be internal / external
- Number range assigned to document types. Doc types specified during doc. entry. Thus number range for this doc. type becomes effective for this document entry
- Sample Doc's No. range Key: X2
- Recurring Entry Doc: No. range key: X1
- Transport: Interval – Transport

Define document type & assign document number range

Tcode: OBA7
Explanation:
- Create doc type for Customer, Vendor & GL business transactions
- Specify a number range for each document type. Can use one number range key for several doc. types? Document numbers are chosen from this number range.
- Doc. Types valid for all clients
- Assign reverse doc. Type for each doc. type.
- Required during doc. entry: Can specify whether Reference number / document header text are mandatory during doc. entry
Key Document Types:

Sub Component	Use	Default Document Type
Asset Accounting	Asset Posting	AA
Asset Accounting	Depreciation	AF
General Ledger	Journal	SA
Accounts Receivable	Customer Invoice	DR
	Customer Payment	DZ
	Internal Transfer from billing	RV
	Payment Clearing	ZV
Accounts Payable	Vendor Invoice	KR
	Vendor Payment	KZ
	Goods Issue	WA
	Goods Receipt	WE

Key fields in Document Types Screen

Field	Usage
Account Types	Select account type that uses this document type. GL/CUSTOMER/ VENDOR / ASSET
Reversal Document Type	Can specify the reversal document type
Net document Type	For vendor invoice related type document. Restrict the document type to be used only for a single customer / vendor
Inter Company posting	Restrict the document type that can be used for cross company postings
Trading Partner	Trading partner value comes from vendor master. If selected in this doc. Type this value can be override
Reference Number	Can select & make reference field mandatory in this document type
Document Header text	Can select & make document header field mandatory in this document type
Batch input only	Can select & ensure document type is used only through batch
Ex. Rate for foreign crncy docs.	If not specified here transaction in FC for this document types will be according to avg rate M

Define Document Posting Keys

Tcode: OB41
Explanation: Posting key determine:
- Debit / Credit Posting key
- To which type of account(S/D/K/A) line item can be posted
- Whether item posted as debit / credit
- Special GL: Indicate posting key used for special GL transaction (Down Payment…)
- Payment Transaction : Indicate that posting key is used for payment transaction
- Field status of additional fields

GL A/c default settings & layouts

Tcode : OBU1
Explanation:
- These values are populated when enter the Tcode initially.

Updating Layout for Document Entry Screen

Tcode: Enter the Tcode Say FB60. Now select change screen layout button – Administrator – Do the changes – Transport button

Define Rules to change data / text in a field:

Tcode: OB32
Explanation:
- Here we define what can be changed in a field

Maintain Field Status Variant

Tcode: OBC4
Explanation:
- FS Group determine what fields are available for entry during GL posting
- Here define & edit Field status variant & Field status group
- Document screen fields are grouped under Field status group
- Several field status groups are grouped under Field Status variant
- Field Status Variant is assigned to company code
- Field Status Group determine which fields are Required/ Optional/ Hidden during document entry
- Copy FSV 0001
- Field status group assigned to GL a/c in FS00

Type of Posting	Primary Object	Possible Account Assignment
Balance Sheet	GL Account	Profit Center
Income	GL Account Revenue element	Profit center Profitability analysis Revenue project
Expenditure	GL account Cost element	Cost center Internal order
Internal settlement	Secondary cost element	Cost center Profit Center Internal Order

Assign Field Status Variant to Company code

Tcode: OBC5

Define Tolerance groups for employees

Tcode: OBA4
Explanation:
- Here you define various amt. limits for your employees:
- Applies to all FI documents
- Maximum document amt. employee is authorized to post
- Maxi amt. employee can enter as line item in Vendor/ Customer a/c
- Maxi cash dis. % an employee can grant in a line item
- Can also define tolerance w/o specifying tolerance group. Leave group field blank. Valid for all employees not allocated to a group.
- Can create as many tolerance groups as required (OBA4).
- User id's to be assigned to the tolerance group in the next step (OB57).Every user can be explicitly assigned to a tolerance group (OB57). If a user is not assigned to any special tolerance group, then entries in the blank tolerance group are valid for him.

Assign user Tolerance group

Tcode: OB57
In our example we have define blank tolerance group for company code 100. Thus all unassigned users will be able to post this company code.

Maximum Exchange Rate Difference

Tcode: OB64
Explanation:
- Specifications are company code dependent
- Here we define how much the exchange rate manually entered in the document Header may differ in terms of % from the one stored in the system. If deviation occur a warning appear

Check co. code settings in global parameters

Tcode: OBY6
Explanation:
- Check important company code settings here
- No FC diff when clearing in LC: FC documents are cleared in the LC.
- Tax base is net value : Discount is deducted from the base amount in sales documents before calculating taxes
- Discount base net value: Tax on sale/purchase not included in amount for calculating discount
Data:

Company code	Currency	COA	Credit control Area	FYV	FSV	PPV
1000	EUR	INT	1000	K4	1000	1000

Document Change

Display document changes for all documents: SE38 - RFBABL00
Create new document change rule: SPRO - Financial Accounting → Financial Accounting Global Settings → Document → Line Item → Document Change Rules, Line Item → New Entries
Explanation:
- Users can change documents that have already been posted. However, based on different rules, only certain fields can be changed. These rules can either be predefined by the system or be user-specific.
- Document header: Only the reference number and text fields can be changed
- Line items: The system does not permit changes to the amount, the posting key, the account, or any other fields that would affect the reconciliation of a posting.

Define Additional Local currencies

Tcode: SPRO-FA-FAGS-Co. Code- || Currencies-Define Additional local currencies
Tcode: OB22
Data

Co. code	Co. code currency	Group Currency	Hard Currency
1000	EUR	EUR	USD

Explanation:
- Here we define additional currencies for company code
- Can define two more || currencies for a company code. Thus we can have three currencies for a company code.
- Currency Types :
  - Group Currency: Currency Specified in the client table
  - Hard Currency: Country specific 2nd currency used in countries with inflation
  - Global Co. currency: Currency used for an internal trading partner
- For Addl currencies define following data:
  - Currency Type: Define role of the currency. e.g.: Group currency/ hard currency
  - Exchange rate type for translation: Define which exchange rate stored in the system is used for calculating additional amount field (additional local currency). e.g.: M (average exchange rate) or any other exchange rate.
  - Base Currency: The amount in the additional currencies can be calculated based on the document currency (USD, INR...) or local currency / company code (INR).
  - Date for translation: Date on which exchange rate translation is done. Can be document date, Posting date, Translation date.
  - Valuation: Can select valuation 1 only if currency and valuation profile configured in the controlling area. Can select valuation 2 if there is profit center valuation view. Valuation 1 & 2 require two additional ledgers to store data
OB22 Explanation:
- Company Code: Enter the four-digit identifier of the company code that you wish to configure.
- 1st Local Currency: These fields will fill in automatically with default information based on the currency defined in the company code definition.
- 2nd and 3rd Local Currency: As explained earlier, each company code can have two additional parallel currencies that can be used in conjunction with local currency defined for the company code
- Curr. Type: The currency type field specifies which type of parallel currency you want to configure. The following options are available.
  - Group Currency: Group currencies are defined at the client level in table T000. Group currencies are used to enable cross-company code postings in controlling for company codes that use different company code currencies.
  - Hard Currency: Hard currencies are used for subsidiaries in countries with a lot of inflation. Hard currencies allow you to better valuate transactions in an inflationary economic environment.
- Ex. Rt. Type: The exchange rate type determines how foreign currencies are revalued at the time of foreign currency revaluation and translation.
- Srce Curr: Enter the source currency that the foreign currency is to be translated against. The possible entries are as follows:
  - Translation taking transaction currency as basis: This option always tries to translate the parallel curreny against the transaction currency of the document.
  - Translation Taking First Local Currency as Basis: This option always translates the parallel currency against the first local currency (company code currency).
- TrsDte Typ: This setting is used to determine which date is used for foreign currency translations. The available options are as follows:
  - 1. Document Date: Select this option if you want the translation calculation to use the exchange rate that was In effect on the day the document was dated.
  - 2. Posting Date: Select this option if you want the translation calculation to use the exchange rate that was in effect on the posting date in the document.
  - 3. Translation Date: Select this option if you want the translation calculation to use the exchange rate that is in effect on the date of the foreign currency translation.

Define Additional Local currencies for Ledgers

Tcode: SPRO-FA-FAGS-Co. Code- || Currencies-Define Additional local currencies
Explanation:
- Since valuation 1 & 2 selected earlier, need to configure additional ledgers
- Here we define additional currencies for company code
- Can define two more || currencies for a company code. Thus can have three currencies

Assign Company code to Company

Tcode: OX16

Check SAP Note: SNOTE

Tcode: snote

Change message control for posting to GL accounts

Explanation:
- You can change status of system error message from error to warning or even turn off the message
Tcode: FA (NEW) – FAGS – DOCUMENT – DEFAULT VALUES – Change message Control for Document processing

Create a Financial Statement version

Tcode: OB58

SAP Account Receivable

2010-12-31T09:44:00.004+05:30

Accounts Receivables

Sales Order	Captures sales information ( Material, Quantity, Price, Delivery dates)
Delivery Note	Entered based on SO information. It initiates picking and packing associated with delivering material to customer. Each delivery initiates goods issue transaction for recording goods stock change ( COGS Debit and Inventory Credit)
Billing Document	Last document in SD. GL accounts decided based on account determination
Vendor Invoice	Triggered by billing document

Define Acct group with screen layout (Customers)

Tcode: OBD2
Explanation:
When creating a customer master need to specify customer account group
Customer account group determine:
- Customer account number
- Whether the customer number is assigned internally by the system or externally by the user
- Whether it's a onetime account
- Which fields are ready for input when creating & changing customer master (Field status)

Enter Accounting clerk identification code for customers

Tcode: SPRO – FA – ARAP – CA – MR – Preparation for creating customer master record – Enter accounting clerk identification code
Explanation:
- Enter identification code (01) & clerk name (Mohit) for a company code (100)
- Code entered in customer master record
- Helpful in evaluation

Define Industries

Tcode: Tcode: SPRO – FA – ARAP – CA – MR – Preparation for creating customer master record – Define industries
Explanation:
- Define industry
- Specify what industry a business partner belongs to by entering industry key in customer master record.
- Helpful in evaluation, e.g. generate customer list for a industry

Sales order to Cash Cycle

Sales Order – Delivery Note – Picking & Packing – Goods Issues (COGS Dr to Inventory Credit) – Billing document (Triggers AR Invoice in FI) – AR Invoice (Customer Dr to Sales Cr, Dunning Letters) – Customer Payments

Create number range for customer accounts

Tcode: XDN1
Explanation:
- Can create internal or external number range.
- Internal : System automatically allot the number
- External: User assigns the number in the specified range.

Assign number range to Customer Acct group

Tcode: OBAR
Explanation:
- We assign number ranges created in (XDN1) to customer account group (OBD2). Thus customer number for this customer a/c group can be selected from this range

Alternative Recon Account for Down Payment: Refer TFIN Notes

Extending Customers to Other company code

Tcode: FD15
Explanation:
- Similar to Vendors discussed earlier

Create customer master record

Create Customer Master : FD01
Display Customer Master : FD03
Display Customer Master : XD03
Display Customer Master : VD03
Display customer Credit Management : FD33
Change customer credit management : FD32
- Choose the Central data screen and enter the following data:
  - Total amount
  - Individual limit
  - Currency
- You can enter the central data in any currency you choose, independently of the currencies of the control areas.
- The fields in the section entitled Current credit limit assigned show to what extent (as a percentage) the customer has exhausted the amount of credit granted to him and in which credit control area the maximum individual credit limit has been exhausted to the greatest extent.
- - The Last general info field displays when the last information on the customer was obtained.
- Now access the Customer Credit Management Change: Status screen and enter the individual credit limit for the customer.
Data:

Company code	Customer	Recon A/C
1000	3471	140000
1000	T-L69B09	140000

Posting a Customer Invoice

Tcode: FB70
Explanation:
- Allows entering of customer invoices
- If one time customer, required to enter customer name & address also

Posting a credit memo with ref. to Invoice

Tcode: FB75
Explanation:
- Business scenario: Customer overcharged & requested refund.
  - Exp/ Sales DR
  - To Customer CR

Posting customer incoming payment manually

Tcode: F-28
Explanation:
- Post customer incoming payment manually & clear OI
- This transaction allows posting customer payments by referencing against a customer Invoice. This process is known as clearing. Where only a partial payment against customer invoice is received following options exist:
  - Partial Payment: Customer Invoice untouched. Payment on account created with reference to this invoice. In dunning both original unpaid invoice & payments are identified.
  - Residual Item: Here SAP system clears the original invoice but creates a new Invoice for the balance payment with reference to the original invoice

Displaying customer account balances.

Tcode: FD10N

Displaying and changing line items in a customer account

Tcode : FBL5N
Explanation:
- Report can be exported to excel/ word
- Can display / change line items
- Can set filter to define additional search criteria for documents displayed. E.g. doc type

Manual Clearing

Tcode: F-32
Explanation
- Some customer invoices & payments received from customers, balance not zero. Use to clear these transactions. Clearing document generated with no real posting

Clear customer down payment against customer invoice

Tcode: F-39
Explanation:
- For installment payment of vendor invoice select payment term Z910
- To block 2nd installment : Put payment block in maintain terms of payment of 2nd installment

Customer Invoices

Park Customer Invoice : FV70
Post parked customer invoice : FBV0
Enter Customer invoice : F-22 / FB70
- Use this SAP transaction to create a customer invoice or chargeback manually
Post customer incoming payment : F-52
- Post incoming payments on both customer/ vendor
- Allows to clear OI
- Doc type : DZ ( Customer payment)
Customer down Payment life cycle : << Refer TFIN>>

Display blocked SD documents

Tcode: VKM1
Table VBUK ( VKM1 display table)

Customer Dunning Notices

Tcode: FI50
Explanation:
- << Refer TFIN>>
- A customer does not settle dues on time. Payment reminders to customers are known as dunning notices
- Can send dunning notices to individual customers or a list of customers

Customer due date analysis

Tcode: S_ALR_87012168
- Due date analysis of customers (Invoices, credit memos)

Configure Down Payment Received from customer

Tcode: OBXR / FBKP
Explanation:
- Refer TFIN

Reason Codes:

Tcode :OBBE
Tcode: FA – AR/AP – BT – Outgoing Payments – Manual outgoing payments – Overpayments/ Underpayments – Define Reason codes
Map Reason codes to GL Accounts: OBXL
Reason codes table: T053R
Explanation:
- << Refer TFIN>>
- RC explains the reason for diff between vendor invoice & payment doc amt. diff. Also this diff. amt. gets posted to different G/L accounts based on RC assigned
- DescriptionReason CodeShort text of RCCorrespondence TypeHere we send notice to the customer for short payment. Can specify the type of notice that has to be associated with this RCCharge off diff. via separate a/cIf selected diff. charged off to the GL a/c selected for this RCDDisputed Item

Define Accounts for payment Differences

Tcode: FA – AR/AP – BT – Outgoing Payments – Manual outgoing payments – Overpayments/ Underpayments – Define Accounts for payment differences
Explanation:
- If no reason codes only a single entry is required, else separate accounts for various reason codes

S_ALR_87009895	VAT Report	Use this SAP transaction to view VAT reporting and to post VAT settlement. Transaction is run at month end after transactions have been completed. When settlement is run the balances of the 11005001 output tax and 22010000 input tax accounts are zeroed out and the balance of each is moved to the 12600000 VAT Settlement account.
SM35	Batch Input Monitoring	Use this SAP transaction to monitor and process batch input sessions to post all the applicable documents and perform all the database updates.

SAP Account Payable

2010-12-31T09:42:00.003+05:30

Accounts Payable

Define Acct group with screen layout (Vendors)

Tcode: OBD3
Explanation:
When creating a vendor master need to specify vendor account group
Vendor account group determine:
- Vendor account number
- vendor number is assigned or externally by the user
- Whether it's a onetime account
- Which fields are ready for input when creating & changing customer master (Field status)

Enter Accounting clerk identification code for customers

Tcode: SPRO – FA – ARAP – CA – MR – Preparation for creating customer master record – Enter accounting clerk identification code
Data: 01 (Mohit)
Explanation:
- Enter identification code (01) & clerk name (Mohit) for a company code (100)
- Code entered in customer master record
- Helpful in evaluation

Define Industries

Tcode: Tcode: SPRO – FA – ARAP – CA – MR – Preparation for creating customer master record – Define industries
Explanation:
- Define industry
- Specify what industry a business partner belongs to by entering industry key in customer master record.
- Helpful in evaluation, e.g. generate customer list for a industry

Vendor Match Codes

Tcode: OB50
Path: FA- AR/AP – Vendor a/c – Master Data – Match codes – Maintain match codes for vendor
Explanation:
- Match codes used to find vendor in the database
- Can define our own match codes

Extending Vendors to Additional Company codes:

Tcode: FK15 (if same client)
Tcode: FK15 + FK16 (if different client)
Explanation
- Multiple company code scenarios. Some vendors shared by company codes. Need to extend a vendor say existing in 730 to company code 766

Define Sensitive fields

Sensitive fields like vendor bank details. Changes to these fields should be confirmed by another user
Confirmation of vendor master changes: FK08 and FK09
Path: FA – AR/AP – Vendor a/c – Master data – Preparation for creating vendor master data

Payment Block Reasons for Vendor Invoices

Path: FA-AR/AP – BT- OP- OP Global settings – Payment block reasons
Explanation:
- Vendor invoices can be blocked for payment. Here we define reason for blocking vendor invoices for payment
- To block Invoice : FB02

Payment block on a Vendor invoice by Payment terms

Path: FA – AR/AP – BT – OP – OPGS – Payment block reasons – Define default values for payment block

Release vendor Invoices blocked for payment

Tcode: MRBR

Create number range for vendor accts

Tcode: XKN1
Explanation:
- Can create internal or external number range.
- Internal : System automatically allot the number
- External: User assigns the number in the specified range.

Assign number range to Vendor Acct group

Tcode: OBAS
Explanation:
- We assign number ranges created in (XKN1) to vendor account group (OBD3). Thus vendor number for this vendor a/c group can be selected from this range

Delete Vendor / Customer Master Data

Tcode: OBR2
Explanation:
- Used to delete customer master data
- Can be deleted only for company codes not flagged as productive
- Can delete customer master record only if no transaction exists in it

Maintain terms of Payment for vendors and customers

Tcode: SPRO-FA-AR/AP-BT-Out going Invoices-Maintain Terms of Payment
Tcode: OBB8
Explanation:
- Payment term assign to Vendor master record
- Payment term proposed when entering a vendor document
- E.g.: 60 days, 5% cash discount if paid in 30 days
- Can also define default payment block for some payment terms

Define terms of payment for installment payment

Tcode: OBB9
Tcode: SPRO-FA-AR/AP-BT-Out going Invoices-Maintain Terms of Payment
Explanation:
- Installment payment to vendor invoice.
- Define three terms of payment in (maintain terms of payment). Now map two of them to one of them in OBB9

Define Accts for cash discount taken

Tcode: OBXU
Tcode : SPRO-FA-AR/AP-BT-Out going Invoices-Define cash discount base for outgoing Invoices
Tcode: Cash discount granted: OBXI
Explanation
- Cash discount received from vendors posted here

Define Accts for exchange rate diff

Tcode: OB09

Define Accts for rounding differences

Tcode: OB00

Define acct for bank charges (vendors)

Tcode: OBXK

Define acct for payment diff ( manual outgoing)

Tcode: OBXL

Down Payment Made to vendors

Configure Down Payment made to vendor: OBYR / FBKP
Vendor Down payment Request: F-47
Post Vendor Down Payment: F-48
Post Non PO Vendor invoice : FB60
Clear Vendor Down payment : F-54

Duplicate Invoice Check

Tcode: SPRO – MM – LIV – Incoming Income – Set check for duplicate Invoice

Creating a vendor master Record

Create Vendor Master: FK01
Transfer customer/ Vendor master data from source company code to target company code: SE38 - RFBIDE10/RFBIKR10
Display changes to customer / vendor master data: SE38- RFDABL00 or RFKABL00
Find duplicate customer master data: SE38 - RFDKAG00
Find duplicate vendor master data: SE38- RFKKAG00
Create vendor master record centrally : XK01
Change Vendor Master record: XK02
Display Vendor Master record: XK03
Block /Unblock Vendor Master : XK05
Mark vendor for deletion (Deleted by a special program) : XK06
Explanation << Refer TFIN notes>>
Account Group:
While creating customer / vendor we have to provide account group. Account group controls:
- Number range of the accounts
- Status of the fields in the master records
- If the account is a onetime account
If a customer is also a vendor the APP and the dunning program can clear open items against each other. For this :
- Enter the vendor account number in the customer account, or vice versa.
- Select the field clearing with customer / vendor

Previous Acct	Legacy system acct number
Sort Key	Assignment field value
Tolerance Group	Tolerances with in which this vendor can transact
Payment Method	Method by which this vendor accept payment

Post Non PO based Vendor Invoice

Tcode: FB60
Explanation:
- To post no PO based vendor invoices

Post Manual Payment to Vendor and not generate payment media (iDoc, check)

Tcode: F-53
Explanation:
- Vendor outstanding invoices are paid in APP (F110). Some invoice not paid can be paid manually in Tcode F-53

Displaying Vendor Account balance

Tcode: FK10N
Explanation:
- To display vendor a/c balance

Displaying / Releasing Vendor Invoices

Tcode: FBL1N
Explanation:
- To display vendor a/c line items, Invoices, credit memos, payments etc
- In SAP we can block / release documents for payments
- Block invoice for payment @ FB60. Release invoice for payment FBL1N. Double click invoice - click to change mode - remove payment block

Automatic Payment Program (Incoming & Outgoing Payments)

Tcode: F110
Explanation:
<< Refer TFIN>>

I have tested the proposed configuration change, please find below my findings:

Option 1:

Payment Method	House bank	Ranking	Currency	Comments
I	HSB21	1	EUR	For payment method I all EURO payments from HSB21
I	HSB22	2	Blank	For payment method I, all payments other than EURO from HSB22
I	HSB23	3	USD	For payment method I, USD payments from HSB22

Define Number Range for Checks

Tcode: FA(N) – AR/ AP – BT – Outgoing Payments – Automatic outgoing payments – Payment Media – Check Management
Explanation:
- Can think of each check lot as a Check Book

Manual Clearing of Vendor open Items

Tcode: F-44
Explanation:
- Manually clear vendor documents ( Invoice, Credit Memos etc)
- Double click & deselect all - Select 2/more documents to be cleared. - Save
- No real posting but a clearing document is created

Display Purchase Order

Tcode: ME23N
Change PO : ZMMME22 or ME22N
Search for a PO : ME2B

PO-based Vendor invoice/credit memo/Planned Delivery Cost

Tcode: MIRO
Explanation:
- You enter the data from the vendor invoice in the system. As you do this, you compare the data with the suggested quantities and values for each item. If differences occur, you make any necessary corrections
- Planned Delivery Costs are costs incurred over and above the cost of the material and include such costs as freight, handling and customs duties. Costs will be classified into categories posted to a separate GL account - Freight and Customs Duties, for example. Planned delivery costs have the advantage that delivery costs are included in the valuation of the material at time of Goods Receipt.
- In PO Reference select: + Planned Delivery cost
- A Credit Memo is received from a trade vendor and the Credit Memo is posted with reference to a Purchase Order and serves as a cancellation of the Invoice Receipt. Posting a credit memo always leads to a debit posting on the vendor account. When you post a credit memo, the total quantity in the purchase order history is reduced by the credit memo quantity.
- Imp: Select Credit Memo on transaction drop down box on top of screen
Display/Change PO-Based Vendor Document : MIR4
Park Invoice: MIR7

S_ALR_87009895	VAT Report	Use this SAP transaction to view VAT reporting and to post VAT settlement. Transaction is run at month end after transactions have been completed. When settlement is run the balances of the 11005001 output tax and 22010000 input tax accounts are zeroed out and the balance of each is moved to the 12600000 VAT Settlement account.
SM35	Batch Input Monitoring	Use this SAP transaction to monitor and process batch input sessions to post all the applicable documents and perform all the database updates.

SAP_Asset Accounting

2010-12-31T09:41:00.003+05:30

Asset Accounting

SAP Asset Accounting Configuration

Copy Reference Chart of Depreciation	OAP1
Change Name of Chart of Depreciation Delete Depreciation Areas not needed	OAP1
Assign chart of Depreciation to Company code	OAB1
Specify number assignment across company codes (optional)	AO11
Specify Account Determination Explanation : Enter account determination key & it's description	Tcode: SPRO – FA(N)- AA – Org structure – Asset Classes – Specify account determination
Create Screen Layout Rule	Tcode : SPRO – FA(N) –AA – Org Structure – Asset Class – Create screen layout rule
Define screen Layout rule for Asset Master Data Explanation : Screen layout defined for each key created in earlier step	Tcode: OA77
Define Asset Number Range Interval	AS08
Asset Class Explanation: Asset Class defined at client level They apply to all company codes Assign: Account Determination, Screen Layout rule, Number Range Assignment, Whether AC is blocked	Tcode : OAOA
Define Depreciation Areas Explanation: Define type of value managed for acquition / net book value. Some options only +ve value / zero allowed etc	Tcode: SPRO – FA(N) – AA- Valuation – Depreciation areas – Define Depreciation Areas
Specify transfer of APC ( Acquition & Production cost) values Explanation: Transfer asset values from specified depreciation area to another depreciation area	Tcode : OABC
Specify Transfer of Depreciation Terms	Tcode: OABD
Determine Depreciation Term for the Asset Class Explanation: Determine depreciation terms ( Depreciation Key + Useful Life + Screen Layout rule) for the Asset Class	Tcode : OAYZ
Deactivate Asset Class at client Level	Tcode: AM05
Define how depreciation areas post to GL Explanation: Options: Depreciation post to GL a/c in real time No depreciation posted to GL Post Depreciation & APPC periodically Post depreciation only	Tcode: SPRO – FA(N) – AA – Integration with GL – Define how depreciation areas post to GL
Maintain Depreciation Key Activate Account assignment objects	Tcode: SPRO- FA(N) – AA – Integration with GL – Additional account assignment activate account assignment objects
Specify Account assignment type	ACSET
Assign GL account	Tcode: AO90

Copy reference chart of depreciation

Tcode: EC08
Explanation:
- COD is a list of depreciation areas
- COD must be assigned to a company code
- SAP provides ref. COD which we need to copy & create our own COD
- Can delete depreciation areas not used

Specify description of chart of depreciation

Tcode: SPRO-FA - AA-Org structure-Copy Ref. COD

Copy / Delete Depreciation areas

Tcode: SPRO-FA- AA-Org structure-Copy ref. COD
Explanation:
- Delete unwanted depreciation areas

Assign Input tax indicator for Non taxable acquition

Tcode: OBCL
Explanation:
- Assign input tax indicator to company code. System uses the indicator for non taxable transactions ( asset acquit ion) posted to taxable a/c

Assign Chart of Depreciation to Company code

Tcode: OAOB

Specify Account Determination

Tcode: SPRO-FA-AA-Org. Structure-Asset Classes-Specify a/c determination
Explanation:<< Refer TFIN>>
- Account determination link an Asset Master Record to the GL using the Asset class

Create screen layout rule

Tcode: SPRO-FA-AA-Org structure-Asset Classes-Create Screen layout rules
Explanation:
- Screen layout rules determine fields to be displayed ( required/ optional/hidden) in AMR

Define Asset number range interval

Tcode: AS08

Define Asset Classes

Tcode: OAOA
Explanation: << Refer TFIN>>
- Every asset to be assigned to exactly one Asset Class

Integration with GL

Tcode: SPRO-FA-AA-Integration with GL-Define how depreciation areas post to GL
Explanation:
- System can post APC (Acquition & Production Cost) of one depreciation area online. Usually this is Book Dep. 01
- Transactions from other depreciation areas can be posted periodically to GL if required

Assign G/L accounts

Tcode: A090
Explanation: << Refer TFIN>>

Specify financial statement versions for asset reports

Tcode: OAYN

Specify Document Type for Posting of Depreciation

Tcode: AO71
Explanation:
- Standard doc. type AF is used for depreciation posting
- <, Refer TFIN>>

Specify intervals & posting rules

Tcode: OAYR
Explanation:
- Define how often ( monthly, quarterly, semi annually, annually) depreciation is posted
- Account Assignment (Cost Center Posting …) rule for the depreciation posting run

Define depreciation areas

Tcode: SPRO-FA-AA-Valuation-Depreciation Areas- Define Depreciation areas
Explanation:
- As COD is copied. Depreciation areas defined in COD are used

Specify transfer of APC values

Tcode: OABC
Explanation:
- In this field, you specify the reference depreciation area that provides values to another depreciation area. The system transfers the posting amounts of any transactions that affect acquisition and production costs from this area to the dependent area. A depreciation area can only adopt values from an area which has a smaller key than itself. No transfer is therefore possible to area 01

Determine Depreciation areas in the Asset class

Tcode: OAYZ
Explanation:
- << Refer TFIN>>

Specify Memo Value

Tcode: OAYI
Explanation:
- Here define memo value for each dep area / company code
- Memo value is the amount that is not depreciated to have value of an asset that has exceeded its useful life
- Memo value activated by an indicator in the asset class
- Memo value ensure fully depreciated assets with NBU of zero are shown in all legal reports

Specify asset classes which will not take memo value into account

Tcode: OAAW

Define Depreciation Area currency

Tcode: OAYH

Calculation sequence for depreciation

Tcode: AOBK
Explanation:

Unplanned Depreciation

Tcode: OABU
Explanation:
- Specify depreciation areas where unplanned depreciation can be allowed

Define base method

Tcode: SPRO-FA-AA-Dep-Valuation Method-Dep Key- Calculation Method- Define base Method / Define declining balance method / Define Maximum amount method / Define multilevel method / Period Control Method
Tcode : AFAMP
Explanation:
- Define declining balance method.
- Assign declining balance method to the depreciation keys

Maintain depreciation key

Tcode: AFAMA
Explanation:
- <<Refer TFIN>>

Assign Accounts

Tcode: AO99

Asset Accounting:

Create Asset: AS01
Explanation:
- General Master Data: This part of the master record contains concrete information about the fixed asset.
- Data for Calculating Asset Values: You can specify depreciation terms in the asset master record for each depreciation area in the chart of depreciation.
- Use the reference field if you'd like to create an asset master record that is similar to another asset master record.
- Number of similar assets; this function enables you to create multiple similar assets in one master transaction. These assets initially differ from each other only by their main and/or sub-number
- Capitalized on: This date is the default for the asset value date when the first acquisition is posted

Change AMR : AS02

Explanation:
- To change asset master record created in AS01
- To update asset scrap value
- No depreciation calculation during asset shut down: Click time dependent data - Select asset shutdown- click further intervals – click new intervals – Back & save. To re- commission the asset - simply repeat the above step entering the date for the recommencement of asset and deactivate the shutdown before saving. Accordingly the depreciation will not be calculated from the period between the date of the first interval and the date of the second interval

Display AMR : AS03

Lock AMR : AS05
Explanation:
- Set this indicator, if you want to prevent further acquisitions from being posted to this asset. Once the blocking indicator is set, you can no longer post acquisitions to this asset. Asset transfers and asset retirement postings to blocked fixed assets are still possible.

Delete AMR : AS06
Explanation:
- You can delete an asset master record to which no postings have been made.

Create Sub Asset : AS11
Explanation:
- The main asset number represents the asset as a whole. Parts of assets can be represented by different sub-numbers

Create Group Asset Master Record: AS21

Asset Explorer : AW01N
Explanation:
- This function shows all the values of a fixed asset. Planned values are displayed, as well as values already posted
Choose the pushbutton above the overview tree, to reach the display transaction for asset master data.
To navigate between depreciation areas in the overview tree, select the depreciation area you want. Icons indicate the type of depreciation area. The icon indicates a real depreciation area, and the icon indicates a derived depreciation area.
Select a transaction line (bottom of screen) and choose display FI document in order to see the associated document in Financial Accounting. In the financial document, using menu option Environment ® Original Document you will see the purchase order that was used to purchase the asset.

NoteThe Parameters tab page contains information such as the depreciation key, useful life and index specifications used.

Note: More Functions:

You can use Call asset reports (for example, asset list, asset history sheet).

You can choose Translate currency amounts to have the system translate currencies. If you call reports in Asset Accounting after using this function, the reports are displayed in the currency you selected.

Create Down Payment for Asset: F-48
Explanation:
- Posting the down payment.
- Posting the corresponding closing invoice
- Clearing the down payment with the closing invoice

Asset Acquition from Vendor : F-90

Asset acquit ion with automatic offsetting entry : ABZON
- Explanation: << Check Top Jobs>>
Asset Retirement with revenue to customers : F-92
Retirement with Revenue without Customer : ABAON
Retirement due to Asset Scrapping : ABAVN
Intracompany Transfers : ABUMN
- Explanation: There are basically three reasons why you might need to carry out an Intracompany transfer within a company code. One reason is if changes are made to organizational structures (reclassification of asset classes, changes to business areas or profit centers, and so on). Second, an Intracompany transfer might be necessary if account assignments are incorrect (for example, incorrect asset class).
Post the Post-Capitalization : ABNAN
- Explanation: Post-capitalization represents subsequent corrections to the acquisition and production costs (APC) of a fixed asset. An example of when you need this type of correction is if you neglect to add expenditures and costs linked with the acquisition or assembly of an asset to its APC in a fiscal year that is now closed. This example can apply to both part assets and entire complex fixed assets

Write-Ups

Tcode: ABZU

Explanation: A write-up is generally understood to be a subsequent change to the valuation of an asset (reversal of depreciation). Write-ups increase the book value of a fixed asse

FI ECC 6 Part-4

2010-11-21T15:42:00.002+05:30

Customer / Vendor Master Record Segments
Customer / Vendor Master Record Segments
1. General data ( Client Level)
  1. Address
  2. Control Data
2. Company code Data
  1. Account management
  2. Payment Transactions
  3. W/H Tax
3. Sales Area
4. Purchase Org
Field status in MR : Controlled by account group
Alternate Payee / Payer
1. Can be defined at client level / Company code level
2. Customer : Amount received from alternate payee
3. Vendor : Amount paid to alternate payee
4. Report
  : SE38 – RFDKVZ00 / RFKKVZ00: Shows alternate payee for all customer / vendor

Document is uniquely identified by: FB03
1. Document number
2. Fiscal Year
3. Company code
A document can have lines : 1 – 999 line
Document is controlled by :
1. Document Type
2. Posting Key
Running APP:
1. Run date : Date to identify the run
2. Posting Date : Date on which posting made to the GL
3. Doc's entered up to : All documents entered up to this date included in the payment run
4. Multiple company codes : Can enter multiple company codes separated by comma in the same country
5. Payment Method: Select payment method applicable for the country. Can enter more than one payment method. Considered in the order entered.
Ways to configure a payment block:
1. Payment block applied by a credit check
2. Payment block during invoice entry (FB60)
3. Payment block in the vendor Master record
Payment Run:
1. Post payment documents
2. Clear Open Item
3. Supply the print program with necessary data
Print Run:
1. Transfer DME payment data to DME administration
2. Transfer payment medium / payment advice note and payment summary to print administration
3. Create intermediate document (iDoc) for selected payments which can be forwarded to EDI

FI ECC 6 Certification Part-3

2010-11-16T12:22:00.002+05:30

Dunning
Dunning Run
1. System check account for items that is overdue
2. Check whether dunning notice to be sent
3. Dunning level to be assigned
4. Dunning proposal can be edited / deleted
5. Dunning Notices printed
6. Dunning data updated in:
  1. Document
  2. Customer / Vendor master record
4 steps of dunning process
1. Maintain parameters
2. Proposal Run
3. Edit dunning proposal
4. Print dunning notices

Customer without dunning procedure in Master Record cannot be dunned
Dunning notices can be sent both to customer and vendor
Dunning Program Configuration
Maintain Dunning Procedure
1. Controls how dunning is done
2. Every customer / vendor that needs to be dunned needs to have a dunning procedure
3. Dunning procedure can process both standard & special GL transactions
For each dunning procedure define
1. Dunning procedure key
2. Dunning Procedure description
3. Interval in days at which accounts have to be dunned. System check dunning date is after the number of days specified here from the last dunning run date
4. Minimum days in arrears for which an item in an account must be overdue for dunning notices to be created for the account
5. Grace period per line item: Grace period >= minimum days in arrear for an item to be dunned
6. Number of dunning levels: The highest dunning level possible in this procedure
7. Grace Period: Not considered for calculating dunning level. Thus an item whose days in arrears <= Grace period is not due for dunning notice
8. Interest Indicator : If selected interest is calculated for this account
Dunning Levels
1. Days in Arrear: Item dunning Level = (Item due date + Days in arrear)
2. Calculate Interest : Can specify whether interest is to be calculated for each dunning level
3. Print Parameters :
  1. Always Dun: If selected a dunning notice is sent even if no changes have been made to the dunning proposal since last Dun
  2. A Dun proposal changes: At least one item in the account reaches next level or/and a new item is added.
4. Print All Items: All open items printed in the dunning notice. Dunning notice has dunning level of the item with highest dunning level
Dunning Charges
1. Dunning charges defined for each dunning level
2. Dunning charges can be fixed amount or % of dunned amount
Minimum Amount:
1. Minimum amount of an overdue item necessary for dunning notice at this dunning level
2. Minimum Amount for Interest : Minimum amount of interest necessary for dunning at the dunning level
Dunning Texts:
1. SAP Forms / scripts to be used for dunning at each dunning level

Parameters for Dunning run
Run Date: Any Date
Identification: Any 6 digit to identify the dunning run
Parameters:
1. Dunning Date: Issue date for dunning note. Basis for calculating days in arrears
2. Document Posted Up to: Items posted up to this date are included in the proposal
3. Company code
4. Vendor / Customer
5. Additional Log: Activate if more details required
The Dunning Run

Dunning Run has 3 steps
1. Account Selection: Program selects customer / vendor accounts as per parameters
2. Dun Line Items: Program selects line item for dunning, i.e. overdue line items

Account Selection Criteria
1. Dunning procedure entered in customer / vendor master record
2. (Date of last dunning run entered in customer / vendor master record by the system + Dunning interval ) > dunning date in the dunning procedure

Due Line Items
1. Customer Invoices: Due on date for net payment. Due date is date after missing all cash discount periods
2. Credit memos: If a credit memo refers to an invoice then invoice due date applies to the credit memo
Clearing with credit memos & vendor line items
1. Customers net due debit items cleared with net due credit items ( credit memos)
2. Where customer = vendor. Customer net due credit item cleared against vendor net due debit item. Same dunning procedure assigned to both the customer & vendor.
Dunning Dates:
1. Due Date: Date by which Item must be paid
2. Item Overdue: After deducting grace period from days in arrears
Dunning block in Item / a/c's
1. If a dunning block exist in customer / vendor master records system add these accounts to blocked account list
2. Similarly for items
Each dunning procedure can have:
1. Up to 9 levels
2. Each line item assigned it's dunning level according to its days in arrear in Dunning procedure
3. No dunning procedure can be skipped
Payment Reminder : Dunning Procedure with one dunning level
Dunning Keys:
1. Can assign dunning keys to the line item to restrict maximum dunning level for the line item ( FB03 – Customer line item – Change)
Minimum days in arrears:
1. Customer / Vendor account can only be dunned if at least one line item has reached the minimum days in arrears
Dunning run updates master record with dunning level

Exercises : Dunning
Reason why overdue items may not be dunned
1. Customer / Vendor account not in dunning parameters
2. Item w/I grace period
3. Item / account blocked for dunning
4. Overdue amount < Minimum amount in dunning procedure
5. Net due item can be cleared with due on credit side
6. None of the item in the account exceed minimum days in arrears
7. (Dunning data has not changed since last dunning run + Always DUN not selected)
Dunning run does not update dunning data in line item account. Dunning data is updated when dunning notices are printed
Dunning proposal can be edited as many times as required. Dunning database not changed. Dunning database is changed when DUN notice is printed

Automatic Payment Program

APP Config: FBZP

FBZP: All company codes
1. Sending Company code : Company code whose invoices are paid
2. Paying company code: Company code responsible for outgoing payments. Normally same but can be different
3. Vendor / Customer special GL transaction: Specify which special GL transaction can be paid / considered during APP run. E.g.: A (Down Payment), F (DP request), G (Guarantee)
FBZP : Paying Company code: For each company code define:
1. Minimum amount for incoming and outgoing payments
2. Forms used for payment advice & EDI
3. BOE Specification : You should flag the field if you wish to use bills of exchange, bill of exchange payment requests in the paying company code
FBZP: Payment Method per Country: For each country define:
1. Payment method to be used (I, W, C...)
2. Vendor / Customer master record requirements (Bank details, Vendor address..)
3. Payment & Clearing document type
4. Payment Medium ( Classic payment medium / PMWB)
5. Permitted currencies:
  1. Currencies specified: Payment restricted in these currencies
  2. Currency not specified: Payment in any currency
Payment Method in Company code
1. A line item whose payment method differ from one specified here are excluded
2. Specify minim um and maximum amount of payment that can be made for this payment method and company code
3. Foreign business partner: If selected payment can be made to customer / vendor outside paying company code country
4. Foreign Currency Allowed: If selected payment can be made in FC.
5. Form for the payment medium : Form to be used by payment medium program entered in Payment method in Country
6. Payment Advice Control: Whether a payment advice to be permitted or not permitted

Bank Determination
1. Ranking Order: HB rank in which APP picks them up for payment
2. Bank Accounts: Entry for paying company code. GL account to which posting made by this HB. If currency field is blank any currency can be used
3. Available Amounts: Maximum amount available for outgoing payments
4. Expenses / Charges: If applicable deducted from incoming payment and added to the outgoing payment
House Bank: HB Config FI12

Reasons for Exception List
1. Invoice blocked / Vendor blocked for payments
2. Bank details / Address missing in vendor / customer master record
3. Payment method not defined in the customer / vendor master records
4. Debit balance (Not due)
5. Payment amount < minimum permitted payment amount in FBZP
6. Invalid House bank

FI ECC 6 Certification Part-2

2010-11-04T09:21:00.002+05:30

Assignment

Client:
- Highest level in hierarchy
- Specifications apply to all company codes under it

Company code:
- Independent unit
- Legal B/S, P/L for company code

Business Area:
- Separate financial unit
- Can prepare separate B/S & P/L

Chart of Depreciation:
- Country Specific
- SAP Provides model COD
- COD contains depreciation area
- Each depreciation area represents Book depreciation, Tax depreciation etc
- One COA and COD can be assigned to one / more company codes
- Depreciation area defined by two digit numeric code

Assignment:
- Assign COD to company code

Cost Accounting Assignment

In Asset accounting master record can assign following cost accounting objects
- Cost center
- Internal Order
- Activity Type
- WBS Elements
- Real Estate Objects
An asset (AMR) can be assigned to only one cost center

Exercises

Create a Chart of Depreciation
- Tcode: EC08
- Data:
  - Copy 1DE to MR03
Change Description of Chart of Depreciation
- Tcode: SPRO – FA – AA – Org. Structure – Copy Reference COD – Specify description of COD
Delete depreciation Areas not required
- Tcode: SPRO – FA – AA – Org. Structure – Copy Reference COD – Copy / Delete Depreciation Areas
Assign COD to Company code
- Tcode: SPRO – FA – AA – Org. structures – Assign COD to Company code
- Tcode: OAOB
Activate account assignment object
- Tcode: SPRO – FA – AA – Integration with GL – Additional a/c assignment object – Activate a/c assignment object

Asset Classes

Asset Classes:
- Fixed asset classified into Asset classes. E.g.: Furniture, Vehicles
- Asset Class created a client level
- Asset class can be assigned to 1 / more COD
- Can suppress individual depreciation areas (01, 02) in chart of depreciation in each Asset class if required (Tcode: ….)
- Each asset can be assigned to only one Asset Class
- Special Asset Classes: AuC, Low value Asset

Depreciation Areas:

Chart of Depreciation:
- Country Specific catalog of Depreciation Areas
- Copy COD supplied by SAP
- Delete Depreciation Areas not required
- Now assign this COD to the company code
- COD defined at client level
- Various company codes can be assigned at to the COD

Depreciation Areas post to GL accounts in any of the following options:

Particulars	Depreciation Area
Post asset values (APC) : Online Depreciation : Periodically	01
Post Asset value (APC) : Periodically Depreciation : Periodically
Do Not Post any values	Reporting purpose only
Only Post Depreciation : Periodically

Depreciation always posted on periodic basis

Exercises:

Define that the asset values in Depreciation areas is displayed in USD
- Tcode: SPRO – FA – AA- Valuation – Currencies – Define depreciation areas for foreign currencies
- Tcode: OAYH

Check How Depreciation areas post values to GL
- Tcode: SPRO – FA – AA – Integration with GL – Define how Depreciation Area Post to GL

0	Area does not post
1	Area post in Real Time
2	Area Post APC & Depreciation on Periodic basis

Enter a financial statement structure for the depreciation area for which B/S is prepared
- Tcode: OAYN

Master Data

Functions of Asset Class

Screen layout
- Determine fields Displayed/ Optional/ Required in AMR
- Tcode: FA – AA – MD – Screen layout – Define screen layout for Asset Master Data
- Here decide what fields are Required / Optional / Suppressed / Displayed only in AMR
- Copy Check Box: If this indicator is set, if this asset is used as a reference to create another asset it's values copied to the other asset
- Screen layout rule assigned to Asset Class in OAOA
- Screen layout rule assigned to Depreciation areas in OAYZ

Asset Master Record Tab Layout:
- Tcode: AOLA
- Here we define AMR Tab Layout
- Also can define New Tabs

Activate Account assignment Objects:
- Tcode: SPRO – AA – Integration with GL – Additional account assignment – Activate a/c assignment
- Can Post depreciation and APC to these objects

Asset Class:
- Tcode: OAOA
- Assign Account Determination : Account determination determine the GL accounts to which depreciation & APC values posted for the AMR
- Assign Screen layout
- Assign Number range
- Status of AuC: Select Line Item Settlement in case of AuC
- Check Box : Asset Classes blocked for Posting

Account Determination:
- Tcode: AO90
- Select your COA INT
- Select the Account Determination
- One Account Determination can be assigned to several Asset Classes provided they use the same COA
- Select Depreciation Area 01 : Assign GL accounts for Acquisition, Retirement, Depreciation

Mass Master Data Change for Asset Class
- Display list of Assets : AR01
- Create a Work List : AR01
- Task Selection: Retirement w/o revenue, Retirement with revenue, Mass Change(Substitution Rule), Inter Company Asset Transfer
- Create a Substitution rule for the Mass Asset Transfer
- Release Work List : AR31

Asset Master Records

Create AMR
- Enter company code and Asset Class
- Use existing AMR as reference

Can create multiple similar Assets

Time Dependent Data
- AMR information managed on time basis in Cost center
- Time Dependent Tab – Further Interval – Enter from date and Cost center

Tcode:

View Changes to AMR	AS04
Create Asset Sub Number	AS11
Create AMR	AS01
Change AMR	AS02
Display AMR	AS03

Mass Changes
Create a work list: AR01
Select Substitution Rule for mass Changes
Release Work List: AR31
Check Assets for changes

Exercises – Master Data

Make number range assignments for Asset Accounting for your company code MR03. Two options:
1. Define a separate number range interval. Copy from company code 1000 : AS08
2. Chose cross company code number range interval. Here find company code MR03 and enter company code 1000 so both company code use same number range interval for Asset Accounting: AO11

Call up transaction that provide overview of all Asset Classes: OAOA
1. Tcode: OAOA
2. Account Determination: Determine the reconciliation a/c in GL to which posting has to be made
3. Screen Layout: Determine for AMR which fields are Required/ Optional / Suppressed
4. Number range assigned to the Asset Class
5. Can block Asset class from posting

Set Chart of Depreciation: OAPL

Which B/S a/c system post for an Asset Acquit ion
1. From AMR get Account determination. For this find GL a/c in AO90
2. Tcode: AO90
Show how field description & cost center of AMR defined ( R/O/S)
1. Tcode: SPRO – FA – AA – Master Data – Screen Layout – Define Screen layout for Asset Master Data – Select layout rule 2000 – Select Logical Field group – General / Time Dependent data – Field group rules
2. Copy : If selected this field is copied is used as reference asset
Determine Depreciation Areas in the Asset Class
1. Tcode : OAYZ
2. Determine Depreciation areas for an Asset Class
3. Depreciation Areas active for the Asset Class
4. Depreciation Keys assigned to the Depreciation areas. Can be changed
5. Screen layout assigned to the depreciation area
6. Use: If a useful life is not entered in the asset class, and depreciation key is not 0000, this field is a required entry regardless of the settings in the screen layout control.
Create an Asset Class (MA03) by copying another Asset Class 2100
1. Tcode : OAOA
2. When you copy Asset Class you get Asset class Master Data + Depreciation Data
Define Maximum value for LVA (Low Value Asset) for company code MR03
1. Tcode : OAYK
2. Tcode: SPRO – FA – AA – Valuation – Amount Specification – Specify Maximum amount for LVA and Asset Class – Specify Asset Class (Here specify LVA Asset Class) / Specify Amount for LVA (Here specify Amount for LVA Asset Class)
3. LVA : 0 : No LVA check for this AC
4. LVA : 1 : Each LVA with its own asset master record
Create Asset master Record (AMR) : AS01

Account Determination	Depreciation Key	Asset
2100		2000
1100		1000
2100		2100
3000	LINS	3007
4000 (AuC)	0000	7000 7001
5000 (LVA)	GWG	5000

Create similar Asset: AS01
1. Enter 5 in similar records

Create Sub Assets: AS11

List all AMR created in a company code
1. Tcode: AA- Information System – Report on AA – Day to Day Activities – International – Directory of un posted Assets
Create a Vendor master: FK01

Post Asset Acquition to Vendor: F-90
1. Tcode: Easy – FA – AA- Posting – Acquition – External Acquition with vendor

Check asset value using Asset Explorer:
1. Tcode: AW01N
2. Check B/S GL a/c to which asset acquition value posted: Double click on transaction
3. GOTO – Call up Reports – Acquition / History
4. GOTO – master data

Post Asset acquition with automatic offsetting entry
1. Tcode: ABZON
2. Easy – FA – AA – Posting – Acquition – External Acquition – Acquition w/automatic offsetting entry

Post acquition in current year w/o first creating AMR
1. Tcode: ABZON
2. Select new Asset radio button

Post Acquition to multiple assets
1. Tcode; ABZON
2. Select Tab Multiple Assets – Enter main Asset number in asset – click sub number – list of assets populated – Add Amount and save

Reverse Asset Acquition: AB08
1. Tcode: Easy – FA – AA – Posting – Reverse Document – Other Asset Document
Post an acquition to LVA: F-90

Ensure / restrict that only certain depreciation areas are posted with values
1. Tcode: SPRO – FA – AA- Transaction – Acquition – Define Transaction types for Acquition – Limit transaction type to Depreciation Areas
2. Tcode: AO73
3. Tcode: OAYA

Asset Transactions – Retirement

Post Asset Retirement with revenue with customer
1. Tcode: F-92
2. Tcode: Easy – AA – Posting – Retirement – Retirement with revenue – with customer
3. Data:

PK	01
PK	50
A/C	820000
Select Asset Retirement	Check box
Select complete retirement check box
TT (For retirement with revenue)	210
On complete retirement AMR is de activated

Scrapping the Asset
1. Tcode: ABAVN
2. Tcode: Easy – AA – Posting – Retirement – Asset Retirement by scrapping
3. AMR deactivated on scrapping

Asset Transactions – Intra/ Inter Company
Perform an Intra company transfer between asset Class 3000 (Furniture) and AC 3100 (Vehicle)
1. Tcode: ABUMN
2. Tcode: Easy – FA – AA – Posting – Transfer – Transfer within company code

Transfer between company codes belonging to the same Company (Group)
1. Tcode: ABT1N
2. Tcode: FA – AA – Posting – Transfer – Intercompany asset transfer
3. Data:

Both company codes in same group company
Transfer variant Used	1
Transfer Variant : Specify Asset valuation method in the receiving company code Transaction Type (Retirement/ Acquit ion) used for transfer

Copy start date of depreciation to the New Asset
1. Tcode: AA – Transaction – Intercompany asset transfer – Automatic Intercompany Asset Transfer – Define transfer variant

Asset Transactions – AuC

Assign a settlement profile (AI) to your company code
1. Tcode: SPRO – FA – AA – Transactions – Capitalization of AuC -
  Assign Settlement Profile
Acquition to AuC:
1. Tcode: ABZON

Distribute AuC (7000) Acquition document to Final Assets (2005, 2006)
1. Tcode : AIAB
2. Tcode: FA – Posting – Capitalize AuC – Distribute
3. Steps : Chose Documents – Execute – Edit – Enter Distribution rules – Save
Execute Settlement
1. Tcode: FA – Posting – Capitalize – AuC - Settlement

Unplanned Depreciation: ABAA

Summary of Asset Accounting Tcode

Particulars	Tcode
Overview of Asset Class	OAOA
Account Determination	AO90
Define Screen Layout	SPRO – FA – AA – MD – Screen Layout
TAB Layout for AMR	AOLA
View Changes to AMR	AS04
External Asset Acquition with Vendor	F-90
External Asset acquition without vendor	ABZON
Asset Explorer	AW01N
Activate / Deactivate Depreciation areas for Asset Class in Chart of Depreciation	OAYZ
Create Sub Assets	AS11
Create / Change / Display AMR	AS01 / AS02 / AS03
Reverse Asset Document	AS08
Asset Transaction Type Details	AO73
Retire Asset to Customer	F-92
Asset Class Change	ABUMN
Inter Company Asset Transfer	ABT1N
AuC Settlement	AIAB
Define Asset Number Range	AS08
Share Asset Number Range with other company codes	AO11

Validation / Substitutions

Validation & Substitution General
To Validate or Substitute an entry
Steps in Validation & substitution:
1. Identify area of application
2. Call up point for validation / Substitution
3. Define Validation / Substitution
4. Assign Validation / Substitution to company code (An Org. unit)
5. Activate validation / substitution
Application Area: Area where validation / substitution rule is used. e.g.
1. FI
2. CO
3. Asset Management
4. Special Purpose ledger
5. PCA
Application Area Key: Specify Application area where validation / substitution is used

Call Up Point: Point at which Validation / Substitution processing starts

Call Up Point for FI
1. Document Header : Call up point 1
2. Document Line Item : Call up point 2
3. Complete Document : Call up point 3
4. At this call up point can use only numeric field, used for mathematical calculation
Formula Editor:
1. Interface for editing arithmetic & Logical statements
Assign Validation / Substitution to Organization Unit (Company code, Controlling area...)
1. A validation / Substitution can be valid for several company codes

Activate Validation / Substitution
1. 0 : Inactive
2. 1: Active (Dialog + batch)
3. 2: Active (Dialog but not Batch)

Only one validation / Substitution can be activated for a company code for 1 call up point

Validation Execution

Validation has following 3 parts
1. Prerequisite
2. Check
3. Message
If prerequisite is true :
1. Check performed
2. If check false, message displayed

Message Type

I	Information
W	Warning
E	Error
A	Cancel

Can use predefined message or create own message

Validation Can do following Logical Statements
1. Compare fields with one another. BKFP-BUDAT <>BKPF-BLDAT. Statement true if date in field BUDAT is not equal to date in field BLDAT
2. Validate field contents for certain values. BKPF-BLART = "SA". Statement true if document type = SA
3. Check / compare only a part of the field. Details refer notes

Substitution Execution
Substitution steps has two parts
1. Prerequisite: If prerequisite is true substitution is performed
2. Replacement: Substitution
3. Substitution Methods:
  1. Constant Values
  2. User Exit: Name of the Exit to be carried at Run Time
  3. Field-Field Assignment: Name of field whose content can be used for Substitution

Rule:
1. A Rule is a prerequisite or a check of validation
2. A rule is normally created for a prerequisite that is frequently used. Rule can be used repeatedly
Set:
1. A data structure having a range of GL accounts

Exercise: Validation / Substitution

Create a validation rule that for GL a/c (telephone expense) 473110 / 473120 cost center must be 3336
1. Tcode: OB28
2. Steps:
3. Double click on call up point 2 for company code MR03
4. Click on validation create
5. Data:

Validation	G03
Description	Telephone Cost

Click on step Insert
Data:
Double click BSEG-HKON- click = - Click constant and enter 473110 – click OR – Double click BSEG-HKONT – click = - Click constant and enter 473120 – Double click on BSEG-KOSTL – click = and enter 3336
Define the required message "Assign cc 3336"
Activate Validation – Go to Step 1 for call up point 2 select Validation G03 and activate it

Create a Substitution rule that when customer invoice posted and Sales a/c = 810301 and Segment = SEG03 Then Substitute PC = PC05
1. Tcode: SPRO –FA – FAGS – Document – Line Item – Define Substitution in account document
2. For company code MR03 & call up point 02 create substitution rule G03
3. Chose Insert – Select BSEG-PRCTR – Continue
4. Enter the prerequisite
5. Select Substitution and Enter PC as PC05
6. Save and Activate

The New GL
Total tables when classic FI component used are:
1. Classic FI: GLTO
2. Cost of Sales Ledger: GLFUNCT
3. Reconciliation Ledger: COFIT
4. EX-PCA: GLPCT

New GL Advantage
1. It has an extended data structure. Thus new fields like cost center, Segment etc can be added to GL total table
2. Balance sheet can be created for entities called segment. Real time document splitting between segment
3. Real time FI & CO reconciliation

New GL is optional for existing customer during a release upgrade
In a new installation new GL is active
Setting up System for New GL : SAP Note 756146
Features of Leading Ledger:
1. Manages additional local currencies assigned to a company code
2. Uses Fiscal Year variant assigned to a company code
3. Uses Posting Period Variant assigned to a company code
4. Only Leading Ledger values posted to controlling
Define additional currencies for leading ledger for a company code
1. Tcode: SPRO – FA(N)- FAGS(N)- Ledger – Ledger – Define currencies of Leading Ledger
Assign Fiscal Year variant and Posting Period to company code and Leading Ledger
1. Tcode: SPRO – FA(N) – FAGS(N) – Ledger – Fiscal Year and Posting Period
There are non leading ledger: Can be assigned currencies and Fiscal Year variant different from leading ledger
New GL Total Tables:
1. New GL total table: FAGLFLEXT
2. Classic GL Total Table : GLTO
3. New fields in new GL total table:
  1. Cost Center
  2. Profit Center
  3. Segment
  4. Can also add new fields predefined / new custom fields

What is a scenario
1. A scenario defines which fields are updated in ledger (Leading and non leading ledger) during posting
2. Cannot define own scenario
3. Scenarios provided by SAP:
  1. Cost Center update ( Update sender / receiver cost center)
  2. Profit Center Update ( Update Profit Center / Partner PC field)
  3. Segmentation ( Update segment, Partner segment and PC fields)
  4. Preparation for consolidation
4. Display available scenarios
  1. Tcode: SPRO – FA(N) – FAGS(N) – Ledger – Fields – Display scenario for GL
5. Assign scenarios to ledger:
  1. Tcode: SPRO – FA(N) – FAGS (N) – Leading ledger – Ledger - Assign
Multiple non leading ledgers useful to show accounts as per different accounting principles
In new GL FA documents has two views : FB03
1. Entry View: In account field vendor number appear
2. GL View: In account field vendor reconciliation account number appear
Segment Field
1. It is one of the standard account assignment object
2. Enable analysis below company code level
3. Alternative account assignment used earlier
  1. Profit Center
  2. Business Area
  3. Profit Segment
4. A segment is assigned to master record of Profit Center. Posting is made to segment when profit center is posted
5. Derive Segment from PC. Can have own rules through user exist (BADI). BADI is FAGL_DERIVE_SEGMENT
Document Splitting
1st define for which FI characteristic document splitting is performed. FI characteristic:
1. Business Area
2. Profit Center
3. Segment
4. Tcode: SPRO – FA(N) – GL (N) – BT – Document splitting – Define document splitting characteristic for GL
5. Zero Balance indicator: Useful if balance sheet is to be prepared for a characteristic
Activate Document splitting
1. Document splitting activated at client level
2. Tcode: SPRO – FI (N) – GL(N) – BT – Document splitting – Activate document splitting
3. Inheritance: In entry view 2 accounts (purchase services and travelling cost) plus 1 tax a/c. In GL view tax a/c amount split in two in the proportion of amount in purchase service and travelling cost
Configuring New GL

Activate New GL
1. Tcode: SPRO – FA – FAGS – Activate New GL
Check ID of Leading ledger
1. Tcode: SPRO – FA(N) – FAGS(N) – Ledger – Ledger – Define Ledger for GL
2. Data: OL
Check scenarios assigned to leading ledger OL
1. Tcode: SPRO – FA(N) – FAGS(N)- Ledger – Ledger – Assign Scenarios to Ledger
2. Scenarios assigned
  1. Cost Center update
  2. Preparation for consolidation
  3. Profit Center Update
  4. Segmentation
  5. Cost of Sales account
Create a new Segment SEG03
1. Tcode: ES – Definition – FA – Define Segment

Create a Profit Center
1. Tcode: KE51
2. Data: PC04
Update Cost center 3336 with Profit Center PC04
1. Tcode: KS02
Check that cost center / Profit Center / Segment defined as OPTIONAL in Field Status Group of GL a/c 417000
1. Tcode: FS00 – Enter a/c 417000 – Create Bank – Double click FSG G033
Check Segment splitting defined for GL
1. Tcode: SPRO – FA (N) – GL(N) – BT – Document Splitting – Define Document splitting …. GL
2. Zero balance indicators checked: System checks that the balance of the characteristic (Segment) is zero during posting. If not system creates additional line item to achieve zero balance
3. Mandatory indicator checked : System checks that all line items in the posting are assigned appropriate characteristic (Segment) after split
Activate document splitting for company code MR03
1. Tcode: SPRO – FA(N) – GL(N) – BT – Document splitting – Activate document splitting
Assign Item category to GL a/c
Assign Segment SEG03 to PC04
1. Tcode: KE52
Enter Vendor Invoice & split to cost center 3336 and 3338 so post to different characteristics
Create segment SEGA and assign to cost center
1. Create PC PC05 : KE51
2. Create a new segment : SEGA
3. Assign SEGA to PC05
4. Create a CC 3339 and assign PC PC05 to it
Assign company code MR03 to controlling area 1000
1. Maintain controlling area
2. Create cost center, Profit Center, Segment
3. Assign Segment to Profit Center
4. Assign Profit center to Cost Center
Create a variant for Real time FI and CO integration
1. Tcode: SPRO – FI (N) – FAGS(N) – Ledger – Real time integration of controlling with Financial Accounting – Define variant for real time integration
2. Data:

Variant	V03
Real time integration	Select
Account Determination	Select
Document Type	AB
Ledger Group	0L

Assign Variant to company code (MR03)
1. Tcode: SPRO – FI(N) – FAGS (N) – Ledger – Real time integration of controlling with FI – Assign variant for real time integration

Repost a line item in controlling from cost center 3338 to cost center 3339
1. Tcode: Easy – Accounting – Controlling – CCA – Actual Posting – Repost line items – Enter

Tcode: KB61 ( It's reversal KB64)