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)

SAP FI Certification Material

2010-10-27T08:32:00.002+05:30

Organizational Units

Client
- At highest level in ERP system
- Data entered at client level used for all organizational units
- Each client has its own set of master data
Important organizational units in FI
Company code:
- Independent legal entity
- For external purpose
Business Area
- For internal purpose
- Can be used across company codes
- Can have financial statement for each Business Area

Create company code steps
- Copy co. code
- Copies :
  - Definition (company name)
  - Global parameters (COA, Fiscal year, Co code default)
  - Tables
  - G/L a/c's
  - Account determination
- Now edit this data
  - Address
  - Company code currency: This is company code / local currency. All other currencies are foreign currencies.
  - Language Key
  - Country key: This is home country. All other countries are foreign countries

Exercise: Organizational Units

Copy company code
- Tcode: EC01
- Data : MR03

Change company code definition
Tcode: SPRO – ES- Def. – FA- Edit, copy, Del- Check co. code- Edit company code data
Data:

Co. code	MR03
Country	US
Currency	USD
Language	EN

Enter company code Global Parameters

Company code	MR03
Company	1000
COA	INT
Fiscal Year Variant	33
Field status variant	1000
Posting Period Variant	MR05

Variant Principle

Variant Principle: A 3 step method to assign properties to one / more objects
Steps:
- Define variant ( K4 Fiscal year variant)
- Determine values for the variant defined: Variant properties
- Assign variant to objects : Assign variant K4 to object company code

Fiscal Year

Fiscal Year Variant:
- Define a fiscal year with posting periods
- Fiscal year contain posting periods + Special posting periods
- Maximum periods = 16
- System derive period for a document from the posting date
- Special posting period:
- Used for yearend closing transactions. Posting date falls in last period, can post in special posting period
- E.g.: FY with PP = 12 and special period = 4. Transaction date falls in 12^th posting period can post in 4^th special (16^th) period.

Year Independent Fiscal Year Variant:
- FYV uses same number of periods each year
- Posting period start and ends on the same date every year
- Can be Calendar Year .Here PP = 12 months of the year
- Can be non calendar year
  - Here PP # 12 months of the year. PP can be from 1 to 16.
  - Need to assign end date for each posting period
  - Need to assign indicator -/+ as required
  - e.g Apr to Mar. For Jan, Feb & Mar year shift of -1 as belongs to old fiscal year

Exercise: Fiscal Year

When is the year specific fiscal year variant used?
- One fiscal year has fewer posting periods than others
- Start and End dates of posting periods differ from year to year
Maintain a Fiscal Year Variant
- Tcode: OB29
- Data: FYV : 33

Assign Fiscal Year Variant (33) to company code MR03
- Tcode: OB37
Create a FYV (Non calendar year FYV)
- Tcode: OB29
- Data:

FYV	64
Description	4 periods
Number of posting periods	4 ( Each period has 4 months)
Number of special periods	1
Provide necessary year shift

Define base currency:
- Tcode: SAP Net weaver – General settings – Currencies – Check Exchange Rate Type

Master Data:

General Ledger Accounts

Chart of Accounts:
- A variant that contain basic of GL a/c
- Has a 4 character ID
- Define properties of GL a/c like language, Length of GL accounts
- COA assigned to a company code

Definition of Chart of Accounts
- Tcode: OB13
- Define:
  - COA key
  - Description
  - Maintenance language
  - Length of GL a/c
  - Manual / Automatic creation of cost elements
  - Group chart of account
  - Blocked / unblocked. If COA blocked, no GL a/c can be created for this COA

Directory of GL a/c in COA:
- Tcode: SE38 – RFSKPL00

One COA can be assigned to one / more company codes (variant principle)

COA contain information about GL in Company code segment and COA segment
- Co. code Segment:
  - To use one of the GL account from COA need to create a company code segment
  - Control data
  - Bank / Interest
  - Information
- Chart of Account Segment:
  - Type / Description
  - Key word in COA
  - Information in COA

Balance sheet a/c
- Balance C/F to the same a/c

P/L a/c:
- Balance carried forward to retained earnings a/c and balance set to zero
- A key is assigned to RE a/c which is the entered in the P/L statement a/c type

Account Group for GL a/c
- Grouping of similar types of accounts. E.g. cash a/c, liquid funds a/c, fixed assets a/c, Expense a/c
- Account group has a number range. For G/L accounts it's always internal number assignment
- Account group controls the display of fields (Field status: Display/ Change ...) in the GL master (FS00)

Field Status
- Field status enable control and display of GL a/c' master data fields
- Field status ranking:

Status	Field Status	Rank
Hide	Not used	1
Display	Field display only	2
Required	Field required value	3
Optional		4

Reconciliation account
- This is a vendor / customer GL a/c in COA. Its corresponding account exist in vendor / customer sub ledger
- All postings to sub ledger posted to reconciliation GL a/c in GL
- Reconciliation a/c type: D: Customers, K: Vendors, Assets
- Cannot post directly to reconciliation a/c
- Details of customer / vendor reconciliation a/c: SE38 – RFDKVZ00

Line Item Display
- Show each transaction as a line in a GL a/c display
- Line Item display not possible in following cases:
- Reconciliation a/c (Line item display in sub ledger)
- Revenue a/c (Sales)
- Material Stock a/c
- Tax a/c (Tax amount per line item checked when document displayed)

Open Item Management:
- These a/c have line item display activated
- Open Item display mandatory for a/c with offsetting entries
- OI management used for following a/c types:
  - Bank clearing a/c
  - GRIR a/c
  - Salary clearing a/c

Account Currency
- Can select company code currency / Local currency as Account currency
- Can also select foreign currency as account currency
- Where LC = A/C currency, can post in any currency
- Where FC = A/C currency can post in only the FC to this GL a/c.

Only balance in Local currency:
- If selected transaction figures to this a/c posted in local currency only
- To be selected for clearing a/c like GRIR to avoid difference due to exchange rates fluctuation
- You would set this indicator for accounts in which you do not want the system to update transaction figures separately by currency.

GL account creation

FS00	One step centrally
FSP0	COA Segment
FSS0	Co. Code segment
OBY2	Copy co. code segment from another company code
OBY7	Copy COA Segment from another COA

Customer / Vendor Accounts

Customer / Vendor Master Data have 3 segments
- General data:
  - At client level
- Company code data:
  - Any company code that wishes to do business with customer / vendor has to have a company code segment
- Customer:
  - Sales area segment
- Vendor:
  - Purchasing org. Segment

SE38 – RFBIDE10 / RFBIKR10:
- To transfer customer / vendor master data from Source Company code to another company code

Can activate automatic duplication check

Account Group for customer / Vendor:
- Once a customer / vendor created cannot change its a/c group in FI
- Controls field status of customer / vendor master records
- Controls customer / vendor number range

Number Range:
- Can be internal / external
- Each number range can be assigned to one / more account group

Special Customer / Vendor master record
- These are one time customer / vendor
- No information about customer / vendor entered in the master record
- Customer / Vendor information entered at the time of document posting
- Special customer / vendor master record cam be used for more than one Customer / vendor

Dual Control Principle
- Can define certain customer / vendor fields in SPRO as sensitive. For e.g. vendor bank address
- Now if these fields are changed customer /vendor is blocked for payment
- Block removed when a second person with authorization confirms / reject such change

Exercise General Ledger, Customer, Vendor

Copy GL Account group
- Tcode: OBD4
- Data:

Copy from	Copy To
SAKO	CD05
ERG	AE05

Create a GL a/c in GL a/c group AE05
- Tcode: FS00
- Data: 176499 (Expense a/c)

Display COA:
- Tcode: SAP Easy – FA – GL – Info System – GL Reports – Master Data – GL a/c list

Reconciliation a/c (Vendor / Customer) contain total of sub ledger transaction figures

Create a/c group for customer
- Tcode: SPRO – FA – AR/AP – CA – MD – Preparation for creating CMD – Define a/c group with screen layout
- Data: Copy from KUNA to D05

Assign number range to a/c group (D05)
- Tcode: SPRO – FA – AR/AP – CA – MD – Preparation for creating CMD

Create customer A/C in the account group D05
- Tcode: FD01 / Sap Easy

Search term field in Vendor master record
- Controlled by field status group
- Search term A: Required entry so appear
- Search Term B: Suppressed entry so not appear

Define sensitive fields for dual control
- Tcode: SPRO – FA – AR/AP – Vendor a/c – Master data – Preparation for creating vendor master - Define sensitive fields for dual control

Confirm customer / vendor master changes (Dual control)
- Customer: FD09
- Vendor: FK09

Number Assignment
- GL a/c: Only external number assignment
- Customer / Vendor master Record: Can have either external / internal number assignment

Create a Vendor a/c group
- Tcode: SPRO- FA- AR/AP – MD – Preparation for creating vendor master record – Define screen layout

Assign number range to vendor a/c group

Create Vendor a/c:
- Tcode: FK01

Bank Accounts

Bank master Record
- Bank master record table: BNKA
- Change to bank master record / Display of bank changes: SE38 – RFBKABL0

House Bank
- House bank contain bank master data
- Bank account information for electronic payment
- GL a/c for each bank account in the HB

Bank Type:
- In customer / vendor master record field bank type is used to distinguish different banks
- While processing vendor invoice (MIRO/FB60) user can chose the bank to which payment will be made by APP by selecting bank type in partner bank field

Create Bank master record: FI01

Define HB: FI12

Create a saving a/c: FI12

Document Control

Document Structure

Document Principle:
- A document is saved for every posting
- Every document is identified by:
  - Document number
  - Company code
  - Fiscal Year (Tcode: FB03)

Document Segment
- Document Header
- Document Line Items (2- 999 line items)

Document Type
- Tcode : OBA7
- Document Type defined at client level & applicable for all company codes
- Document Types : AB (Post all GL ac), DG ( Customer and GL), RV (Customer Invoice), RE ( MM billing document)
- Document Type Controls:
  - Properties:
    - Number Range
    - Reverse Document Type
    - Authorization group
  - A/C Types Allowed:
    - Asset
    - Customer
    - Vendor
    - Material
    - GL
  - Control data:
    - Negative Postings permitted
    - Intercompany posting
    - Net document Type: system automatically deduct cash discounts from vendor invoices that are posted with this document type
  - Required during document Entry:
    - Reference Number
    - Document Header text

Document Number Range:
- Can be internal / external
- Up to a Future Fiscal Year : Beginning of next fiscal year system uses number following the last number of the current fiscal year
- For Each Fiscal Year: System starts with a new number each fiscal year
- A document number range can be assigned to (02) multiple document types

Posting Key
- PK defined at client level & so valid for all company codes
- PK Control:
  - D/C indicator
  - Account type that can be posted ( Customer / Vendor / GL/ Asset / Material)
  - Other Attributes
    - Whether line item connected with payment ( select where incoming / outgoing payment transactions)
    - Indicator whether PK used for entering special GL transactions
  - Maintain field status: (Field status : Suppress, Required, Optional)
    - General Data (Assignment number, Text, Invoice reference)
    - Additional a/c assignments (Cost center, PC, Sales Order)
    - Payment transactions (Due date, Value date, Payment terms, Reason code)

Field Status Variant
- FSV is a Group of Field status groups ( G001, G003, G004, G005)
- Field status group: Is a group of similar features. E.g FSG G001: general characteristic, G003: Material consumption a/c general data, additional a/c assignment etc master fields, G004 : Cost Account general data, payment transactions, additional a/c assignments etc
- FSG assigned to GL a/c in tcode FS00 to decide field status of these GL a/c during transactions
- FSV is assigned to a company code

Posting Periods

Posting Period
- PP is defined in Fiscal Year Variant
- Usually current PP is open and all other PP close to prevent posting to incorrect PP
- Can have as many PP open as required

Posting Period Variant
- Several company codes can use the same PPV

Posting period check
- PP for a document is determined by the posting date
- PPV must contain the a/c type +
- Other a/c types are for further control of accounts D/K/S/M.
- Account type + must always be open if posting to be made to any other a/c type

Year End Closing
- During year end 2 periods are open. Special PP for the last fiscal year and normal PP for the current fiscal year
- E.g. FY: Apr to Mar. In Apr Special PP 13 and normal PP 1 are open

Posting Authorizations

Tolerance Group
- Tcode: SPRO-FA-FAGS – Document – Line Item – Define tolerance group per employee
- Specify Upper limit for following:
  - Amount per document: Maximum permitted posting amount per document for this user group.
  - Amount per Open Item: Maximum posting amount permitted per customer or vendor item for this user group
  - Cash discount per Line Item: Maximum cash discount percentage rate which may be assigned by an employee of the user group. The percentage rate is checked during the entry, change and clearing of open items

Can create any number of tolerance group
Tolerance group "_____" blank applies to all user not assigned to any specific tolerance group

Exercises:

Simple document posting

GL a/c posting	FB50
Vendor Invoice	FB60
Vendor Credit Memo	FB65
Customer Invoice	FB70
Customer Credit Memo	FB75
Define/ Display / Copy document number range	FBN1
Display customer line item	FBL1N

Button Tree: Access screen variants, A/C assignments, Held documents

Make the text field mandatory for GL a/c
- At client level: GL a/c posting document type: AB. For document type AB in tcode OBA7 make the text field as required entry
- At company code level: Find out FSV for the company code in OBY6. For this FSV in field status group G001 (General) make the text field as required. Now assign this FSG to the GL a/c in FS00

Define variant for open PP
- Tcode: SPRO-FA-FAGS-Document-PP- Define variant for open posting period

Define which periods are open for a posting period variant
- Tcode: OB52

Assign PPV to a company code
- Tcode: SPRO-FA-FAGS-Document-PP- Define variant for open posting period

Create a tolerance group SUPV
- Tcode: SPRO-FA-FAGS – Document – Line Item – Define tolerance group per employee

Assign tolerance group SUPV to your ID SAPUSER
- Tcode: SPRO-FA-FAGS – Document – Line Item – Define tolerance group per employee

Posting Control
Default Values

Using editing option config screen for different views
- Document entry: Fields hidden (for specified user) if not relevant
- Document display: Use list viewer for different display options
- Open Items:

When user log in his ID has following properties:
- Language
- Date format
- Decimal notation

Can control:
- Whether fiscal year is proposed when document displayed / changed
- CPU date proposed as value date

Maximum exchange rate difference between exchange rate in document header and exchange rate in table TCURR. If it exceed warning display can be set

Change Control

Document Change
Document header: Only text and reference fields can be changed
Line Item: No change can be made to amount, account and PK

When a document is changed following information is logged
Fields that was changed
New and Old values
User who made changes
Time and date of change
Display changed documents
Tcode : SE38 – RFBABL00

Document Reversal

Can reverse GL, Customer, and vendor document

Document can be reversed by:
Normal reversal posting
Negative posting

Reversal Reasons:
The reason for the reverse posting is noted in the reversed document. The field is therefore used as information as to why a reversal was necessary. The reason for reversal also determines:
- Whether the reverse document is allowed to have an alternative posting date
- Whether the reverse document is to be created from negative postings

Documents with cleared items cannot be reversed. Reset the cleared items in FBRA

Payment Terms and Cash Discounts

Terms of payment
Enable the system to calculate cash discount and Invoice due date. To calculate Invoice due date and cash discount system needs following information:
Base Line Date: Date from which Invoice due date is calculated
Cash discount % and Cash discount Terms

Terms of payment can be specified in customer / vendor master record in:
Company code segment
Sales Area segment
Purchase Org. segment

Terms of Payment defaulted:
FI Invoice: Entered in company code segment
Sales Order: Entered in Sales Area Segment
Purchase Order: Entered in Purchase Org. Segment

Credit Memos
Credit Memos related to Invoices:
- Enter Invoice number in Invoice reference field under payment Tab during credit memo entry.
- Invoice Terms of Payment copied to the credit memo
- Invoice and credit memo due on the same date
Credit Memo not related to the Invoice
- For credit memo terms of payment to be valid enter V in invoice reference under payment Tab

Cross Company code Transactions

Cross company code transactions
Transactions involve 2/ more company codes. E.g.:
- 1 company code purchase for multiple company codes
- 1 company code pays for multiple company codes
- 1 company code sells for multiple company codes

One document can be posted in one company code so in cross company code transaction system post document in both company codes
The documents are linked by a clearing a/c
There are two or more documents linked with a common reference :
- 1^st company code + 1^st company code document number + Fiscal Year

Tax posting in cross company code transactions
Whole amount of tax posted to the company code of 1^st line
If tax is to be distributed use report: SE38 – RFBUST10

Exercise

Ensure document assignment field is not changed in tcode FB02( Restriction at company code level)
- Tcode : SPRO – FA – FAGS – Document – Line Item – Document change rules
- Ne w entries – Field name assignment (BSEG-ZUNOR) – Applicable for what a/c type (S/K/D/A) – Company code
Ensure document assignment field is not changed in tcode FB02( Restriction at client level)
- Tcode : OBA7
Prerequisite for negative reversal:
- Company code allow negative posting (OBY6)
- Reversal reason code allow negative posting ( SPRO- FA- GL – BT – Adjustment posting – Define reason for reversal)
FI Document reversal : FB08
Reset cleared items: FBRA
Create a new terms of Payment
- Tcode : SPRO – FA – AR/AP- BT – Incoming invoices / Credit Memos – Maintain terms of payment – New entries

Terms of payment	AC03
Customer Blank	Blank
Vendor	Select
Default base line date	Posting date
%	%%
No. of days	Blank
%	2%
No. of days	14
No. of days	30

Explanation area of payment terms automatically defaulted

Assign terms of payments to vendors
- Tcode: Easy – accounts – FA – AP – MR – Change – Company code data – Payment transactions
Baseline Date
- Date system uses to calculate vendor/ customer invoice due date and cash discount amount
Taxes steps:
- Create a new tax code (FTXP)
- Assign a GL A/C to tax code to enable automatic postings (FTXP)
- Define the tax code to be used in enjoy transaction ( OBZT, SPRO – FA – FAGS – AR/AP – BT – Outgoing invoice – Define tax code per transaction)
- Post a customer / vendor invoice to show automatic posting
Create a new tax code
- Tcode : FTXP

Country	GB
Tax code	03
Account Type	Output tax
Acct Key	MWS
Tax Percent	20%
COA	INT
Tax a/c	175000

Configure automatic postings for cross company code transactions
- Tcode: OBYA
Display cross company code documents
- Tcode: Easy – Accounts- FA – AP – Document – Cross company code transactions
- Tcode : FBU2 / FBU3 / FBU8

Clearing
Clearing

Two ways to clear OI
- Account clearing (F-32)
- Post with clearing

Documents with OI cannot be achieved
Post a customer Invoice
- Tcode: FB70

Customer a/c Dr	5000
To sales a/c	5000

Post a customer credit memo
- Tcode: FB75

Sales a/c Dr	5000
To Customer a/c	5000

Posting with Clearing
Invoice is posted to customer
Customer pays invoice and payment assigned to the Open Item
Invoice cleared with above payment & balance is zero

Clearing transaction creates a clearing document
Clearing document no line items as no account posting

Clearing Tcode:
Automatic: F.13
Manual: F-03

Automatic Clearing Program
Program groups items in a GL a/c where they have same entries in the following fields:
- GL a/c number
- Currency
- Special GL indicator
- Five definition criteria ( Assignment field)
If balance is Zero in Local currency, program clears the items
Account to be cleared defined in SPRO
Automatic Program does not clear following items:
- Noted Items (Only information)
- Statistical posting ( Same a/c both D/C posting)
- Down Payments
- Items with withholding tax entries
Assignment Field: Value comes from sort fields in FS00

Tolerances:

Tolerances:
Rules that define acceptable differences during posting

Types of Tolerances:
Employee Tolerance Group:
- Upper limit for posting transaction
- Permitted payment differences
GL a/c Tolerances
- Permitted payment differences (Clearing a/c, GRIR)
Customer / Vendor Tolerance Group provides for
- Permitted payment differences
- Posting residual item for payment differences

Tolerance Group defined in 2 steps:
Group Definition: Tolerance group defined by:
- Group key
- Company code
- Currency code
The Key "___" blank is required as minimum tolerance group

Tolerance Group Assignment:
Employee Tolerance Group: Assigned to employees
GL a/c Tolerance Group: Assigned to GL a/c in FS00
Customer / Vendor Tolerance Group: Assigned to customer / vendor in customer/ vendor master records
If no tolerance group assigned then blank tolerance group applies

Automatic clearing of Payment differences
Payment differences should be with in both tolerance (amount & %) to be cleared automatically
Entries in tolerance group always cleared in Local currency / company code currency

Manual Processing of Payment Differences
High payment differences can be manually processed as follows:
- Partial Payment: Post as partial payment. Document remains open
- Residual Item: Post payment differences as residual item. Original document and payments are cleared. A new document is created for the residual item
- Write off: The difference is w/off to an a/c. Manual a/c assignment for w/off

Reason Codes:

Reason codes used to analyze and post payment differences
To assign more than one reason code to a payment difference click distribute differences
Reason code functions:
- Control type of payment notice sent to the customer
- Control account to which residual item posted
- Exclusion of residual item from credit limit check

Exchange Rate Differences

When clearing open items against payment received exchange rate difference may occur due to exchange rate fluctuation. This is posted to exchange rate difference realized account
Exchange rate difference also occurs when valuating foreign currency open items for financial statements. These are posted to separate Exchange rate difference account and reverse in next period.

Create a Reason Code goods damaged in transit (Z03) to w/off difference to GL a/c mapped to this reason code
- Tcode: SPRO – FA – AR/AP – BT – Incoming payments – Incoming payments Global settings – Overpayment / Underpayment – Define Reason codes
- Data:

Reason code	Z03
Text	Damaged in Transit
C	Charge of difference via a separate a/c
Type of correspondence with customer

Map GL a/c to Reason code
Tcode: OBXL
Data: 881000

Cash Journal
Cash Journal

Cash Journal: A tool for managing cash. Supports posting cash receipt and payments
Features:
- Create separate cash journal for each currency
- Post to customer / vendor / GL account (D/K/S)
- Run several cash journal for a company code

Steps in creating a new cash Journal: Specify following
- Company code in which cash journal will be created
- GL a/c's to which CJ entries will be posted
- Currency in which CJ runs

Special GL Transactions

Types of Special GL transactions
- Down Payments:
  - Down Payment Request
  - Down Payment
- Bill of Exchange
  - BOE Request
  - BOE
- Other Transactions
  - Individual value Adjustments (PBDD)
  - Guarantee
  - Interest

Down payment Request
- Noted Items, Not included in GL
- Only 1 line
- Reminders
- Payment Program and Dunning Program can access noted items
- FBL5N : Noted Items
- DP Request – Down payment received – DP request considered – Customer Invoice received – DP cleared against customer Invoice

Down Payment
- Part of Financial statement. Create a proper posting in GL a/c
- FBL5N – Special GL items

Guarantee
- Automatic offsetting entries
- Displayed in Notes to accounts

Customer alternative Reconciliation a/c Dr

To Guarantee Clearing a/c

Guarantee Clearing a/c Dr

To Customer alternative reconciliation a/c

Configuration of Special GL Transactions: FBKP

Customer	Reconciliation a/c (FD03)	Alternative Reconciliation (FBKP)	Spl. Transaction Type
21003	140000	196100	G

A/C Type (D/K/S/A/M)	Spl GL Indicator	Description	Reconciliation a/c	Alternative Reconciliation a/c
D	F	Down Payment Request	140000	196000
D	A	Down Payment	140000	170000
D	E	Reserve for Bad Debt	140000	142000
D	G	Guarantee	140000	196100

Exercises
Enter a Guarantee:

Tcode: F-38
Tcode: easy – A/C – FA – AR – Document Entry – Other – Statistical Posting
Data:

Document Type	DA
PK	09
Customer	100196
Due on	After 3 months

Display Guarantee
- Tcode: FBL5N (Select special GL transaction)

Reverse Statistical Posting / Guarantee
- Tcode: F-19
- Tcode: easy – A/C – FA – AR – Document – Special GL Transaction – Reverse statistical posting

Create a Down Payment Request:

Tcode: F-37
Data:
- Special GL indicator: A

Display Down Payment Request of Customer
- Tcode: FBL5N
- Select Noted Items

Create a Down payment against the DP request created earlier
- Tcode: F-29

Post a Customer Invoice
- Tcode: FB70

Clear Customer Invoice against down payment
- Tcode: F-39

Customer	100196
Click process DP
Double click Transfer Posting
Save

Individual Adjustments (PBDD)

Use Special GL transaction E to make an individual value adjustment of 6000
Tcode: F-21
Tcode: Easy – A/C – FA – AR – DE – Other – Transfer w/o clearing
Data:

Posting date	Last day of current month
PK	19
Customer	100196
Special GL Indicator	E
PK	40
GL a/c ( Bad Debt / Uncollectible)	210100
A/C Entry
Bad Debt / Uncollectible Expense a/c (210100) Dr	6000
To Allowance for Bad debt (PBDD: 142000 alternative reconciliation a/c for customer 100196) B/S account	6000

Reverse Individual Value Adjustment / PBDD
- Tcode: FB08

Held / Park Documents

2 ways of saving FI documents w/o fully completing it:
Held document:
- Document is incomplete
- No document number is assigned
- No a/c balance are updated
- Not considered for reports
- Document can be found under only user ID

Park Document:
- Document number is assigned
- Considered for reports
- Document can be found with any user ID
- Can be used as part of principle of dual control

ML_Not Distributed Line in ML analysis

2010-07-17T11:04:00.006+05:30

Not distributed Line Item in ML analysis (CKM3)

PVTDJ3E75EN5

**'Not distributed' price differences can be due to four reasons:
A) System applied a 'Price limiter' logic (stock coverage check).
You can analyze this case using the value flow monitor transaction:
- for release 4.7 , transaction CKMVFM
- for release 4.6C, program SAPRCKM_VERIFY_PRICE_DET (note 324754 is required).
- for release < 4.6C: Program ZVERIFY_PRICE_DET (included in the note 324754) Or directly checking the field CKMLPP-PBPOPO manually.
In this case the value CKMLPP-PBPOPO is bigger than cumulative inventory.
If you still want these price differences to be distributed, you can switch off price limiter logic. Then all price differences are posted to stock, and the price difference account is cleared. You should decide for each material if you want to switch off price limiter logic or not. So you can achieve a compromise between realistic prices and clearing the balance of the price different account.
Price limiter logic can be switched off in the following way:
* Resetting the price limiter quantity
In release 4.7 this is done using transaction CKMVFM.
In release <= 46C using the program ZREMOVE_PRICE_LIMITER (see note 325406).
* Note 855387: Application of this note will create an additional selection parameter for step 'Single Level Price Determination' to switch on/off price limiter logic.
This option is the better way, as it simplifies the process and provides more flexibility (see the note for more information).

B) System applied a fallback strategy during price determination (see note 579216) to avoid a negative periodic unit price (PUP).
Please check the attached note 579216: If the regularly calculated PUP (based on 'Cumulative Inventory' line) would become negative, the system uses a different strategy to calculate the PUP:
The PUP is calculated with these priorities:
1. 'Cumulative Inventory' line (no fallback)
2. Receipts ('ZU') line (Info message C+ 135 in the log)
3. Beginning inventory ('AB') line (Info message C+ 138 in the log)
4. PUP-price of previous period (Info message C+ 136 in the log)
5. S-price (Info message C+ 137 in the log).
The fallback strategy is active by default for Single-Level price determination.
For multilevel price determination it must be activated with parameter 'Negative price: automatic error management'.
As a solution, you might check the postings of these materials if they really need to have such big negative price differences or if there is some kind of error in the posting or the production structure
If you find such errors, you might reverse the corresponding postings and post them in a correct way.
Or, you might use transaction MR22 (debit/credit material) in order to post an appropriate positive amount of differences to the concerned materials so that the resulting actual price would no longer be negative. This allows performing the period closing regularly. In the next period, you might remove this manual posted value from the materials (again with MR22) in order to correct the overall stock values back to their original amounts.

C) Execution of transaction CKMM.
The above situation may be produced because transaction CKMM was executed during the corresponding period.
When transaction CKMM is processed the system deletes the price differences for the material in the period and these differences are not longer in the period record tables.
See note 384553 for further details.
The fact is that the price differences are still visible in CKM3 (as not distributed). This is due to the missing reset of summarization records (MLCD).
This error is just a problem of CKM3 display, because the differences shown as 'not distributed' do not exist in the periodic records. The PUP of the material is calculated correctly.
The error is solved with note 838989:

D) A subsequent price change (LTPC).
In transaction CKM3 when a subsequent price change (LTPC) is carried out, the preliminary valuation and all differences are rescaled at category level. Additionally, the corresponding lines for price change documents are sorted and flagged with the text "Subsequent price change".
If a late price change is run with transaction MR21 and there were not a previous reversal of the consumptions already posted in the period, these documents cannot be rescaled by transaction MR21.
Therefore transaction CKM3 will show a "Not distributed line" although the PRDs are rescaled correctly. This is then a display side-effect in CKM3.

FI_VAT

2010-07-17T11:04:00.004+05:30

VAT Configuration

FI Global Settings

Tax on Sales/Purchases
		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
Assign country 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

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.
Create an Access Sequence (MWST Tax Indicator) and underneath it an access code (10 (Table 3) Tax Code).
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).
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.

FI_GL

2010-07-17T11:03:00.008+05:30

General Ledger

SAP FI Module

FI module receive posting from MM, SD & HR module. It feeds data to CO modules Cost center accounting, Profit center accounting & Profitability Analysis module. FI module is geared for external reporting BS & P/L.

Define Group Company

Tcode: OX15

Explanation

A company is an organization unit. A company can comprise one / more company codes.
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
Currency: This is local/ company code currency. All accounts are managed in this currency. All other currencies treated as FC.
Local currency: Currency defined in company code
Country Key: Specifies which country to be regarded as home country. System regards all other countries as foreign countries
Company code 1000 contains all necessary data. So copy and use company code 1000

Edit Chart of Accounts

Tcode: OB13

Tcode (Copy Chart of Accounts) : OBY7

Tcode ( Copy from an existing company code): EC01

Directory of GL Accts in COA: SE38 - RFSKPL00 / RFSKVZ00

Display COA: S_ALR_87012328

Explanation

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)
Directory of GL Accts in COA: SE38 - RFSKPL00 / RFSKVZ00
COA accts grouped under account groups.
Acct Group control number range, Field status
Reconciliation Acct.:
Open Item Management: To be used for
- Bank clearing acct,
- Salary clearing acct.,
- Goods / Invoice receipt clears acct.
- For these accts (clearing accounts) also select line item display
Only balances in local currency: Selected for clearing accounts
Group COA: Multiple CC. Some CC use different operational COA. Create a Group COA. Group COA contain a/c from all operation COA. This Group COA assigned to all operational COA. In FS00 enter group COA a/c number
Steps in creating a new COA:
- Define Chart of Account
- Define the properties of COA
- Assign COA to company code
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 statement 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
Reconciliation Account:
- All posting to sub ledger accts. (AP/AR/AA) are automatically posted to reconciliation GL accts. For this specify "Reconciliation Acct Type". There can be a same reconciliation account for a number of sub reconciliation accounts. Line items are managed in sub ledger accounts
- To see the business partner accounts assigned to reconciliation account: SE38-RFDKVZ00
- Note: You cannot post amounts directly to reconciliation accounts.
Internal Reporting:
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)

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

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 which periods the company code will post

Define Posting Period Variant

Tcode: OBBO

Explanation:

A separate variant for posting period is defined for every company code
One PPV can be assigned to multiple company codes
Total 16 periods. 12 normal periods & 4 special periods.
System derives posting period from posting date. If a transaction posting date falls in normal period can be posted in special posting period.
Variant Principle: Define Variant-Determine value for variant-Assign variant to object
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 (100). 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
At the end of each calendar month, this transaction is executed to close the sub ledgers (accounts receivable, accounts payable, fixed assets) so that the financial month-end close process can begin. 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
Assign one / more document types to each number range
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
Number range for doc. is company code dependent
Year dependent Number range: can specify same number interval with the same key again in different fiscal year
Year Independent Number Range: Enter 9999 in the to fiscal year field
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 an individual reverse doc. Type for each doc. type.
Required during doc. entry: Can specify whether Reference number / document header text are mandatory during doc. entry
Use standard sap doc. Types

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. Document type KR ( Vendor invoice) don't select D thus this document cannot be used for customers
Reversal Document Type	Can specify the reversal document type
Reference Number	Can select & make reference field mandatory in this document type
Document Header text	Can select & make reference field mandatory in this document type
Batch input only	Can select & ensure document type 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:

SAP Config. Allows you to use different posting keys per transaction type. Use default posting keys. Here we can Config additional posting keys

Explanation: Posting key determine:

To which type of account(S/D/K) line item can be posted
Whether item posted as debit / credit
Field status of additional fields

Maintain Field Status Variant

Tcode: OBC4

Data : 100

Co. code	PPV
1000	1000

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

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:
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.
User id's to be assigned to the tolerance group in the next step (OB57)
Can create as many tolerance groups as required (OBA4). 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 doc. 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

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 (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 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.
Index-Based Currency: Index-based currencies are used for statutory reporting purposes for subsidiaries in some countries that have extreme amount of inflation.
Ex. Rt. Type: The exchange rate type determines how foreign currencies are revalued at the time of foreign currency revaluation and translation. The number of possible entries is too numerous to list here J
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 current 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.

Assign Company code to Company

Tcode: OX16

Automatic clearing settings

Tcode: SPRO-FA-GL-BT-OI Clearing-Prepare Automatic clearing

Tcode : OB74

There are five criteria's you can mention. Normal practice is giving ZUONR (Assignment) as one criterion. The sort key in the vendor master defines the assignment field in the document. A meaningful sort key should be used to facilitate the automatic clearing process. Use tcode OB74 to check automatic clearing settings.
Clearing program clears open items grouped together if their balance is zero in local & foreign currency ( Check local currency & group currency)
Grouping criteria to be entered:
- Account Type ( D, K, S)
- Account Interval ( 1 to 999999)
- If possible also provide fields (ZUONR.) which are in table BSEG, BKPF, BSIS, BSID, and BSIK.

Define Tolerance groups for GL Accounts

Tcode: SPRO-FA-GL-BT-OI Clearing – Clearing diff. – Define tolerance group for G/L accounts

GL accts for clearing diff

Tcode: OBXZ

Explanation:

Tolerance group define the limit within which differences are accepted
Here assign the GL a/c to which these diff. are posted
SAP delivers an exp./ rev a/c in COA INT for this assignment

Data:

COA	Account
INT	230110, 280110

Define Foreign Currency Valuation Method

Tcode: OB59

Explanation:

Here we define foreign currency valuation method for the open item
SAP uses exchange rate type M to value all foreign currency items
In the valuation method we group together specifications used for valuation
Before every valuation run we specify the valuation method
M is the average rate of any FC

Assign GL Accts for foreign currency valuation difference

Tcode: OBA1

Explanation:

GL account to which exchange rate differences due to valuation are posted
Double click KDB:
- Exchange Rate difference key: It can be kept blank. If entered same has to be updated in the GL Account control data tab (Exchange rate difference key) to revalue the foreign currency account
- Expense Account: Enter GL Account for unrealized foreign exchange loss. Loss is unrealized and automatically reversed next month.
- E/R gains: GL Account for unrealized foreign exchange gain. Can be same as expense account
Exchange Rate difference in open items (A/R, A/P) KDF : Enter GL codes for accounts receivable/ accounts payable (reconciliation accounts)
- GL Account: GL account mapped to customer in customer master
- Loss : GL Account for exchange rate loss realized
- Gain: GL Account for exchange gain realized
- Val. Loss1: GL account for unrealized exchange loss on valuation of open items (AR, AP)
- Val. Gain 1 : GL account for unrealized exchange gain on valuation of open items (AR, AP)
- SAP system supports two valuation areas in parallel. This account used for first valuation area. First valuation shows local view of company code.
A currency key must be assigned to every currency used
For every combination of currencies there can be different exchange rate types (M...)
Exchange rate is maintained as translation ratio
Report RFTBFF00: Can update exchange rate table by uploading a exchange rate file in multicash form
Exchange rate tool: Use a Base currency for exchange rate M. Use the exchange rate spread (-) for buying & (+) for selling.
Direct Quotation: 1 unit of FC quoted for local currency. 1 USD = 47 INR
Indirect Quotation: 1 unit of LC quoted for FC.
Exchange rate table: TCURR

Define Adjustment for GR/IR clearing acct

Tcode: OBYP

Explanation:

Goods receipt / invoice receipt clearing account is a provisional account & is posted to when we receive goods not invoiced or receive invoice for goods not received.
Adjustment entries have to be made at the BS date.
Tcode F.19 analyze GR/IR clearing account and post adjustment entries for goods received but not invoiced & invoice received but goods not received.
- Reconciliation Account
- Adjustment Account
- Target Account

Create GL Acct centrally

Tcode: FS00

Explanation:

Create and Maintain (change, display, block and mark for deletion) GL Accounts Centrally
Activate the field "Recon. account for acct. type" for accounts considered as reconciliation account e.g. A/R select customer recon account type ,A/P select vendor recon account type ... etc,.
To lock/ unlock account: Select your account and click Lock/Unlock Button.
- Click Blocked for creation. ( At Chart Of Accounts Level )
- Click Blocked for posting. ( At Chart Of Accounts Level )
- Click Blocked for planning. ( At Chart Of Accounts Level )
- Click Blocked for posting. ( At Company Code Level)
The GL account may be deleted only if no posting has been made to this account. The GL account deletion process is performed be a special program
- Click Delete Button
- Click Mark for deletion. ( At Chart Of Accounts Level )
- Click Mark for deletion. ( At Company Code Level)

Explanation:

Create and maintain GL a/c centrally ( create, change, display, block & mark for deletion)
Can also create GL A/C with reference to sample a/c
Type / Description: Data at COA level.
Control data : At company code level
Recon a/c : AR select customer recon, AP select vendor recon
Block GL a/c: Click (lock) - block at COA / co. code level
Mark GL a/c for deletion: Click (del dustbin icon) - GL a/c deleted by a spl program
Maintenance / change of GL a/c

Create Sample account

Tcode: FSM1

Explanation:

A sample account is a master record containing data that is transferred when you create G/L account master records in the company code area.
Sample accounts are dependent on the chart of accounts.
You must not enter sample accounts in the chart of accounts as G/L account master records
Cannot post to a sample a/c
Change sample a/c : FSM2
Display sample a/c : FSM3
Delete sample a/c : FSM5

Copy GL master data from Source company code to Target company code

Tcode: FS15

Mass maintenance of GL a/c

Tcode: OB_GLACC11

Tcode: OB_GLACC12

Tcode: OB_GLACC13

Explanation:

If individual change in GL a/c use FS00
If mass change in GL a/c use OB_GLACC11. Can change a/c group, nature of a/c
Mass maintenance of GL a/c (FS00) company code data. i.e. Field status group, Currency, Tax category use OB_GLACC12
For name change OB_GLACC13

GL a/c posting

Tcode: F-02

Explanation:

Can post to any General Ledger & sub ledger (Vendor/Customer/AA) using proper posting key
PstKy Determine: This key determines several factors: account type (K, D, S, A) type of posting (debit or credit) and layout of entry screens. Fields : Type SA Identifying the type of doc. Posted

Posting with Reference Document

Tcode: FBR2

Explanation:

Allows you to post a new accounting document using a previously posted FI document as a reference

Incoming Payment

Tcode: F-06

Explanation:

Post incoming payment.
DR Bank A/c. CR Customer / Vendor / GL a/c.
Clear OI on this a/c
e.g.: payment received from customer, cleared against customer invoice. During clearing, the system enters a clearing document number and the clearing date in these items. In this way, invoices in a customer account are indicated as paid, and items in a bank clearing account are indicated as cleared
To post your entry, click Save Button. The system stored two documents:
- A payment document,
- A separated clearing document that contains the information about cleared documents.

GL Account line item analysis

Tcode: FBL3N

Explanation:

Report allows to display & change GL line items provided
- This G/L accounts is managed with line item display
- The account master is not defined as a Reconciliation account.
Double-click on the document number to display document details

GL Account analysis

Tcode: FS10N

Explanation:

The account balance displays:
The opening balance (the balance carried forward from the previous year)
The total of all transactions for each posting period, broken down into debit and credit postings (transaction figures)

GL manual a/c clearing

Tcode: F-03

Explanation:

There are some postings on GL account that are not cleared. You want to clear these postings manually
To clear open line items in GL accounts
You can clear also the transactions posted in different currencies. The system will automatically calculate and post exchange rate differences

Outgoing payment

Tcode: F-07

Explanation:

Post outgoing payment
You credit your bank account and on the debit side you can post a GL, Customer or Vendor account and clear open item(s) on this account.
Typical example of an open item is a vendor invoice that has not been settled
During clearing, the system enters a clearing document number and the clearing date in these items. In this way, invoices in a vendor account are indicated as paid, and items in a bank clearing account are indicated as cleared

Change a posted GL document

Tcode: FB02

Explanation:

To add more information to already created documents like change text or assignment field.

Display GL Document

Tcode: FB03

To find any document in the system: SE38 - RFBUEB00 and RFBUEB01

To find gaps in document number assignment: SE38 - RFBNUM00

Explanation:

Display a previously posted document and print it. You can display any document that was posted in FI module (including document that was created e.g. in Logistics, but it was followed by automatic FI document posting).
You can display your document in different currency. Click Display currency Button.
You can display also other document details, like e.g. who posted this document. Choose Document Header button. You can see that the user SBTP000197 posted this document on 18^th July 2002

Document type define following:

Number ranges for document
Account types(S/D/K/M) permitted for postings
The field status of the document header fields (Display, Hide...)

Document Type	Purpose
AB	Posting to all document types
DG	Posting to customer / GL accounts
RV	Sales Order billing
RE	Material Management billing

Individual Document Reversal

Reverse Individual Document: FB08

Check which reversal reasons can be used to perform reversal by negative postings / Alternative posting date allowed : SPRO- Financial Accounting→General Ledger Accounting -Business Transactions → Adjustment Posting/Reversal → Define Reasons for Reversal

Explanation:

Mass Reversal of Documents

Tcode: F.80

Explanation:

Document to be reversed cannot include already cleared items. If you want to reverse document that was already cleared, you need to reset all cleared items before posting a reversal

Post /Hold / Park/Edit / GL Doc.

Tcode: FB50 ( Post/Hold / Park)

Tcode: FV50 ( Edit & Post Park documents)

FB11 (To see Hold document)

Explanation:

Copying GL Accounts to Company Code

Tcode: OBY2

Explanation:

Create new company code by copying existing co. code

Tcode: EC01

Explanation:

Imp all dependent tables get copied. Copy 0001/1000/3000

Create reference document for GL entry

Tcode: FKMT

Explanation:

It can contain any number of G/L account items and can be changed at any time. In contrast to sample documents, the G/L account items for account assignment models may be incomplete

Posting with reference to Account assignment model:

FB50 – Environment - Complex posting - Act assgnmt model

GL post with clearing

Tcode: F-04

Explanation:

Using the posting with clearing function, you enter document line items and then select the open items to be cleared. Once you have fulfilled all the prerequisites for clearing, the system clears the open items

With manual clearing there are 3 way of clearing an open item (full , partial , residual)

Residual & Partial Clearing:

GL account automatic clearing

Tcode: F.13

Tcode : F13E ( Automatic clearing with clearing currency specified)

Configure F.13 : OB74

Explanation:

Accounting Editing Options

Tcode : FB00

Explanation:

You can set-up your system settings to speed up data processing or just to make the system more "friendly" for a user. All settings you enter here are stored in your user master data and are user-dependant

FBRA GL Reset Cleared items

Tcode : FBRA

Explanation:

Table name	Category
BSAK	Vendor
BSAD	Customer
BSAS	GL

Recurring Entry

Create Recurring Entry : FBD1

Display Recurring entry : FBD3

Change Recurring entry : FBD2

Explanation:

The recurring entry function helps to automate postings of transactions that repeat every months (with the same amount) e.g. Accruals / Deferrals postings. The system uses the recurring entry original document that you've entered as a reference. It is not an 'real' accounting document and therefore does not affect the account balance. However, at a specified date, when a recurring entry document will be processed, it will generate automatically the accounting documents and postings will affect account balances.

Enter translation rates

Display forex exchange rates: OB08

Tcode: S_BCE_68000174

Explanation:

Enter accrual & deferral documents

Tcode: FBS1

Explanation:

Reverse Accrual/Deferral documents

Tcode: F.81

Explanation:

Reverse previously posted accrual / deferral. The system posts a reversal by entering an identical amount to the opposite side of the account, thereby offsetting the original amount.

Cross Company Code Document

FBU2 - Cross Company Code Document – Change

FBU3 - Cross Company Code Document – Display

FBU8 - Cross Company Code Document – Reverse

Explanation:

These documents allow posting for more than one company code. It is possible to involve several companies in a cross-company code transaction. The system posts a separate document with its own document number in each of the company codes

FI_GL 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

FI_AR

2010-07-17T11:03:00.007+05:30

Accounts Receivables

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:

The interval for 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 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

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

Create Recon account for Customers

Tcode: FS00

Define Alternative Recon Account for Down Payment

Tcode: OBYR

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
Enter the currency for the total limit and maximum individual limit.
The credit limit is managed in a separate credit limit currency, which you determine for each control area. This currency is separate from the local (company code) currency. To update the credit limit data, the system converts the amounts. This has no effect on the updating of the transaction figures or on any postings.
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.

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.

Posting customer incoming payment manually

Tcode: F-28

Explanation:

Post customer incoming payment manually & clear OI

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

Similar to FB70

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 request : F-37

Customer Down Payment (customer advance) : F-29

Use spl GL indicator, thus post down payment to a diff GL a/c & not normal GL recon a/c
Doc type : DZ ( Customer payment)
Click request button to provide previously entered down payment request as reference
System post a DP ( customer advance) & clears one DP request

Display blocked SD documents / Customer Invoices

Tcode: VKM1

Table VBUK ( VKM1 display table)

Customer Dunning Notices

Tcode: FI50

Explanation:

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
Program determine: Customers to be dunned. Dunning level. Relevant dunning notice.

Customer due date analysis

Tcode: S_ALR_87012168

Due date analysis of customers (Invoices, credit memos)

Down Payment Received from customer

Tcode: OBXR

Explanation:

Down payment define GL acct to which posting is made in case of down payment received from customer, instead of normal customer receivable acct (RECON A/C)

Reason Codes:

Reason Codes: OBBE

Map Reason codes to GL Accounts: OBXL

Reason codes table: T053R

Explanation:

Define reason code for Overpayment/Underpayment
Classification of Payment Differences for underpayment and overpayment in AR line items.

With reason code, you can define whether the difference should be charged off to a G/L account or if a residual posting should be made

FI_AP

2010-07-17T11:03:00.006+05:30

Accounts Payable

AR & AP are sub ledgers of GL for managing customer & vendor balances. Most of AR comes from SD modules & AP data from MM module.

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:

The interval for vendor account number
Whether the vendor 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

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
For above we create 3 terms of payments. z

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 dis 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 Tolerance for Vendors and Customers

Tcode: OBA3

Down Payment Made to vendors

Tcode Down Payment made to vendor: OBYR

Tcode for Vendor Down payment Request: F-47

Tcode Post Vendor Down Payment: F-48

Creating a vendor master Record

Tcode:

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
To find duplicate customer master data: SE38 - RFDKAG00
To 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

A customer / Vendor Master data is maintained at following levels:

General data at the client level
- Vendor / Customer (Sub Ledger COA number is assigned at client level to ensure it is same for the customer / vendor for all company codes. This vendor / customer account number can be assigned also at company code level.
Company code segment
Sales area segment

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 payment 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

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

Clear Vendor Down payment

Tcode: F-54

Explanation:

Advance paid to vendor can be cleared against vendor invoice.

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:

Process both outgoing & incoming payments
Process O/S documents in both AP & AR
It creates payment doc. & supplies data to the payment medium program. Payment medium program either prints checks / creates data carriers like magnetic tape, iDoc etc
Clears OI in Vendor / Customer accounts
APP runs in 3 phases.
- Phase 1 Entering payment run parameters.
- Phase 2 Creation of payment proposal.
- Phase 3 a/c posting & creation of payment medium
Pre requisite:
- Vendor / Customer master data.
- Bank Details
- Payment Methods
- O/S invoices in AP / AR
Phase 1: Payment method: Check / wire transfer (I). Next/p date: Next payment run date. Vendor / Customer : Vendor / Customer whose O/S invoices to be paid
Phase 2 : Click Proposal button system looks for o/s documents that fulfill entered criteria
Edit Payment Proposal : Click proposal button- Click vendor button - to block any document double click & change payment block to A
Phase 3: Treasury

Tcode: FBZP

All company codes
Sending company code: Company code whose vendor invoices needs to be paid
Paying company code: company code whose bank a/c makes the payment
Paying company code can pay invoices of other company codes, if they are define as sending company codes here
EMEA : Paying company code = Sending company code = 730

Paying Company code
- Here we define for paying company code:
- Minimum amount for payment
- Forms to be used for remittance
- Sender details ( Details used by programmer while creating remittance advice)
Payment Method in Country:
- Select Outgoing / Incoming payment
- Master Records: Provide the bank information
- Posting details:
- Payment doc Type : TP ( Treasury document)
- Clearing doc Type: ZV
- Payment Medium: RFFOUS_T
Payment Method Per Company Code:
- These settings are useful if payment from more than one company code in a country
Bank Determination:
- To be configured for each paying company code
- Ranking Order: If more than one HB per payment method, ranking order of these HB
- Bank a/c: Bank a/c's of HB available for making payment
- Value Date: Average time for a payment to clear in bank

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. If you do not want the total quantity invoiced to be reduced, you must post the credit memo as a subsequent credit
Imp: Select Credit Memo on transaction drop down box on top of screen

Display/Change PO-Based Vendor Document : MIR4

Park Invoice: MIR7

FI_AP Tcodes Summary:

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

FI_PCA Reconciliation

2010-07-17T11:01:00.002+05:30

FI and PCA Reconciliation:

Discrepancies in these two reports (2KEE & ke5z) in case there are multiple SAP instances and you are using PCROLL to transfer PCA Amounts to the central SAP system. 2KEE report is based on GLPCA Table and KE5Z is based on GLPCT Table. If you have PCROLL IDOCS then they only update the GLPCT Table and not the GLPCA Table. Hence, causing the discrepancy.

Tcodes	Description
2KEE	Records from table GLPCT
KE5Z	Records from table GLPCA
FS10N
1KEK	Periodic data transfer program
S_ALR_87009822
GLPCT	2KEE
GLPCA	KE5Z
KE5T	Shows differences between FI-GL and PCA on the AR and AP reconciliation accounts.
2KES	Comparison Ledger update in period 0

2KEE: Report 2KEE fetches data from table GLPCT. This report reconcile with FI only if we take it from period 00. SAP note 180906

KE5Z: Takes data from table GLPCA. GLPCA gets updated with actual line items (OI)when we run 1KEK

F.5D: At month end we run F.5D. F.5D make profit centre posting for customer / vendor. This is not done when Vendor invoice is posted. Vendor Invoice posting to CC, which make posting to PC for the expense a/c. But no posting to PC for amount credited to vendor. This single entry posting is made by F.5D. This update Table BFOD_A or BFOK_A as the case may be

1KEK: This is a periodic data transfer program. Run at month end. It transfers data from table BFOD_A or BFOK_A to Profit centre ledger 8A.

In period 0 we run balance carried forward program (2KES) in PCA. The last year balances get's updated only in table GLPCT. Thus in period 0 there is balance in GLPCT (2KEE) but no balance in GLPCA (KE5Z).

In period 1, there is an open item balance in AP a/c of 800. Now when 1KEK is run to transfer balance from FI to PCA, Table GLPCA is updated with 800. But table GLPCT (2K3EE) is updated using delta technique. GLPCT is updated with (Current FI ending balance - Previous periods GLPCT balances). So if I have to reconcile FI with PCA (2KEE) in period 1 PCA total will be (GLPCT Period 0 + GLPCT period 1) = ( 600 + 200 ) = 800

Report 2KEE fetches data from table GLPCT. Whereas report KE5Z fetches data from table GLPCA. Please find below an illustration on FI & PCA reconciliation logic:

Period	FI Balances	GLPCA (KE5Z)	GLPCT (2KEE)
0	600	0	600
1	800	800	200
2	100	100	-700
3	0	0	100

In period 0 we run balance carried forward program (2KES) in PCA. The last year balances get updated only in table GLPCT. Thus in period 0 there is balance in GLPCT (600) but no balance in GLPCA (KE5Z). In period 1, there is open item balance in FI (800). Now when 1KEK is run table GLPCA (KE5Z) is updated with 800 but table GLPCT (2KEE) is updated using delta technique. GLPCT is updated with (Current FI ending balance - Previous periods GLPCT balances). So if I have to reconcile FI with PCA (2KEE) in period 1 PCA total will be (GLPCT Period 0 + GLPCT period 1) = (600 + 200) = 800.

Table GLPCT always has period 16. Following fields shows various periods in table GLPCT:

Fields	Period
TSLVT	O
TSL01	1
TSL02	2
HSLVT	0
HSL01	1
HSL02	2

FI-GL

2010-06-28T23:06:00.000+05:30

FI-GL

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

• FI module receive posting from MM, SD & HR module. It feeds data to CO modules Cost center accounting, Profit center accounting & Profitability Analysis module. FI module is geared for external reporting BS & P/L.

1.2 Define Group Company

• Tcode: OX15

• Explanation

o A company is an organization unit. A company can comprise one / more company codes.

o All company codes for a company must work with same Operational COA & Fiscal year

o Company codes can use different currencies

1.3 Define Company code

• Tcode: OX02

• Copy company code along with all data : EC01

• Explanation

o Legal entity. Separate BS & PL can be maintained

o Two options 1) Copy co. code 2) Edit co. code

o 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

o Currency: This is local/ company code currency. All accounts are managed in this currency. All other currencies treated as FC.

o Local currency: Currency defined in company code

o Country Key: Specifies which country to be regarded as home country. System regards all other countries as foreign countries

o Company code 1000 contains all necessary data. So copy and use company code 1000

1.4 Edit Chart of Accounts

• Tcode: OB13

• Tcode (Copy Chart of Accounts) : OBY7

• Tcode ( Copy from an existing company code): EC01

• Directory of GL Accts in COA: SE38 - RFSKPL00 / RFSKVZ00

• Display COA: S_ALR_87012328

• Explanation

o Copy CAUS

o 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)

o Directory of GL Accts in COA: SE38 - RFSKPL00 / RFSKVZ00

o COA accts grouped under account groups.

o Acct Group control number range, Field status

o Reconciliation Acct.:

o Open Item Management: To be used for

 Bank clearing acct,

 Salary clearing acct.,

 Goods / Invoice receipt clears acct.

 For these accts (clearing accounts) also select line item display

o Only balances in local currency: Selected for clearing accounts

o Group COA: Multiple CC. Some CC use different operational COA. Create a Group COA. Group COA contain a/c from all operation COA. This Group COA assigned to all operational COA. In FS00 enter group COA a/c number

o Steps in creating a new COA:

 Define Chart of Account

 Define the properties of COA

 Assign COA to company code

o If company codes intend to use cross-company code controlling, they must use the same chart of accounts.

o For balance sheet accounts, the balance is carried forward to the same account.

o For profit and loss statement 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.

o 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

o Reconciliation Account:

 All posting to sub ledger accts. (AP/AR/AA) are automatically posted to reconciliation GL accts. For this specify "Reconciliation Acct Type". There can be a same reconciliation account for a number of sub reconciliation accounts. Line items are managed in sub ledger accounts

 To see the business partner accounts assigned to reconciliation account: SE38-RFDKVZ00

 Note: You cannot post amounts directly to reconciliation accounts.

o Internal Reporting:

o If company codes want to use cross company code controlling, they must use the same operational chart of accounts

o 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.

o 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

1.5 Assign Company code to Chart of Accounts

• Tcode: OB62

• Explanation

o For each company code specify which COA to be used.

o Several company codes can use same COA.

o Operative COA : COA assigned to company code

o Country Specific COA: COA structures as per country legal requirements

o Group COA : COA structured as per consolidation requirements

1.6 Define Account Groups

• Tcode: OBD4

• Explanation

o Account group used to combine GL a/c's with similar functions. E.g. expenses, asset accounting, Cash etc

o Account Group determines:

 GL a/c number interval in FS00 for the GL A/C created

 Fields in GL master records (Required/ optional/hidden)

1.7 Define Retained Earnings
• Tcode: OB53

• Explanation

o 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.

o 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

1.8 Maintain Fiscal Year Variant

• Tcode: OB29

• Data : K4 ( Jan to Dec)

• Explanation

o Fiscal Year normally has 12 posting period & 4 special period for yearend closing transactions

o Fiscal year can be Calendar Year ( Jan to Dec) / Not Calendar Year ( Apr to March)

o Fiscal Year (Not Calendar Year) can be year dependent or Not year dependent

o 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)

o SAP standard FYV : K4 ( Jan to Dec), V3 ( Apr to March)

1.9 Assign Company code to Fiscal Year Variant

• Tcode: OB37

• Explanation:

o This control which periods the company code will post

1.10 Define Posting Period Variant

• Tcode: OBBO

• Explanation:

o A separate variant for posting period is defined for every company code

o One PPV can be assigned to multiple company codes

o Total 16 periods. 12 normal periods & 4 special periods.

o System derives posting period from posting date. If a transaction posting date falls in normal period can be posted in special posting period.

o Variant Principle: Define Variant-Determine value for variant-Assign variant to object

o 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.

o If the start & end date of period differ each year it is year dependent PPV

o 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.

o 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

1.11 Open & Close Posting Period

• Tcode: OB52

• Explanation:

o Here specify which periods (Jan, Feb, Mar ...) are open for posting for each variant (100). There are 2 time intervals for both specify lower limit period, Upper limit period & Fiscal year.

o 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

o At the end of each calendar month, this transaction is executed to close the sub ledgers (accounts receivable, accounts payable, fixed assets) so that the financial month-end close process can begin. 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.

1.12 Assign Posting Period Variant to Company Code

• Tcode: OBBP

1.13 Create number range for Company code

• Tcode: FBN1

• Explanation:

o Here we create number ranges

o Each number range specify a interval from which document numbers are selected

o Number range can be internal / external

o Assign one / more document types to each number range

o 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

o Number range for doc. is company code dependent

o Year dependent Number range: can specify same number interval with the same key again in different fiscal year

o Year Independent Number Range: Enter 9999 in the to fiscal year field

o Sample Doc's No. range Key: X2

o Recurring Entry Doc: No. range key: X1

o Transport: Interval – Transport

1.14 Define document type & assign document number range

• Tcode: OBA7

• Explanation:

o Create doc type for Customer, Vendor & GL business transactions

o 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.

o Doc. Types valid for all clients

o Assign an individual reverse doc. Type for each doc. type.

o Required during doc. entry: Can specify whether Reference number / document header text are mandatory during doc. entry

o Use standard sap doc. Types

• Key Document Types:

Sub Component Use Default Document Type

Asset Accounting Asset Posting AA

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. Document type KR ( Vendor invoice) don’t select D thus this document cannot be used for customers

Reversal Document Type Can specify the reversal document type

Reference Number Can select & make reference field mandatory in this document type

Document Header text Can select & make reference field mandatory in this document type

Batch input only Can select & ensure document type 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

1.15 Define Document Posting Keys

• Tcode: OB41

• Explanation:

o SAP Config. Allows you to use different posting keys per transaction type. Use default posting keys. Here we can Config additional posting keys

• Explanation: Posting key determine:

o To which type of account(S/D/K) line item can be posted

o Whether item posted as debit / credit

o Field status of additional fields

1.16 GL A/c default settings & layouts

• Tcode : OBU1

• Explanation:

o These values are populated when enter the Tcode initially.

1.17 Updating Layout for Document Entry Screen

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

1.18 Define Rules to change data / text in a field:

• Tcode: OB32

• Explanation:

o Here we define what can be changed in a field

1.19 Maintain Field Status Variant

• Tcode: OBC4

•
• Explanation:

o FS Group determine what fields are available for entry during GL posting

o Here define & edit Field status variant & Field status group

o Document screen fields are grouped under Field status group

o Several field status groups are grouped under Field Status variant

o Field Status Variant is assigned to company code

o Field Status Group determine which fields are Required/ Optional/ Hidden during document entry

o Copy FSV 0001

1.20 Assign Field Status Variant to Company code

• Tcode: OBC5

1.21 Define Tolerance groups for employees

• Tcode: OBA4

• Explanation:

o Here you define various amt. limits for your employees:

o Maximum document amt. employee is authorized to post

o Maxi amt. employee can enter as line item in Vendor/ Customer a/c

o Maxi cash dis. % an employee can grant in a line item

o Can also define tolerance w/o specifying tolerance group. Leave group field blank. Valid for all employees not allocated to a group.

o User id’s to be assigned to the tolerance group in the next step (OB57)

o Can create as many tolerance groups as required (OBA4). 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.

1.22 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.

1.23 Maximum Exchange Rate Difference

• Tcode: OB64

• Explanation:

o Specifications are company code dependent

o Here we define how much the exchange rate manually entered in the doc. Header may differ in terms of % from the one stored in the system

o If deviation occur a warning appear

1.24 Check co. code settings in global parameters
• Tcode: OBY6

• Explanation:

o Check important company code settings here

o No FC diff when clearing in LC: FC documents are cleared in the LC.

o Tax base is net value : Discount is deducted from the base amount in sales documents before calculating taxes

o 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

1.25 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:

o 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.

o Document header: Only the reference number and text fields can be changed

o 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.

1.26 Define Additional Local currencies

• Tcode: SPRO-FA-FAGS-Co. Code-

Currencies-Define Additional local currencies

• Tcode: OB22

• Explanation:

o Here we define additional currencies for company code

o Can define two more

currencies for a company code. Thus we can have three currencies for a company code.

o 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

o 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 (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:

o Company Code: Enter the four-digit identifier of the company code that you wish to configure.

o 1st Local Currency: These fields will fill in automatically with default information based on the currency defined in the company code definition.

o 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

o Curr. Type: The currency type field specifies which type of parallel currency you want to configure. The following options are available.

o Group Currency: Group currencies are defined at the client level in table T000. Group currencies are used to enable cross-company postings in controlling for company codes that use different company code currencies.

o 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.

o Index-Based Currency: Index-based currencies are used for statutory reporting purposes for subsidiaries in some countries that have extreme amount of inflation.

o Ex. Rt. Type: The exchange rate type determines how foreign currencies are revalued at the time of foreign currency revaluation and translation. The number of possible entries is too numerous to list here J

o Srce Curr: Enter the source currency that the foreign currency is to be translated against. The possible entries are as follows:

o Translation taking transaction currency as basis: This option always tries to translate the parallel current against the transaction currency of the document.

o Translation Taking First Local Currency as Basis: This option always translates the parallel currency against the first local currency (company code currency).

o TrsDte Typ: This setting is used to determine which date is used for foreign currency translations. The available options are as follows:

o 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.

o 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.

o 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.

1.27 Define Additional Local currencies for Ledgers( Revisit After CCA)

• Tcode: SPRO-FA-FAGS-Co. Code-

Currencies-Define Additional local currencies

• Explanation:

o Since valuation 1 & 2 selected earlier, need to configure additional ledgers

o Here we define additional currencies for company code

o Can define two more

currencies for a company code. Thus can have three currencies

o Currency Types :

 Group Currency: Currency Specified in the client table

 Hard Currency: Country specific 2nd currency used in countries with inflation

1.28 Assign Company code to Company

• Tcode: OX16

1.29 Automatic clearing settings

• Tcode: SPRO-FA-GL-BT-OI Clearing-Prepare Automatic clearing

• Tcode ;OB74

o There are five criteria’s you can mention. Normal practice is giving ZUONR (Assignment) as one criterion. The sort key in the vendor master defines the assignment field in the document. A meaningful sort key should be used to facilitate the automatic clearing process. Use tcode OB74 to check automatic clearing settings.

o Clearing program clears open items grouped together if their balance is zero in local & foreign currency ( Check local currency & group currency)

o Grouping criteria to be entered:

 Account Type ( D, K, S)

 Account Interval ( 1 to 999999)

 If possible also provide fields (ZUONR.) which are in table BSEG, BKPF, BSIS, BSID, and BSIK.

1.30 Define Tolerance groups for GL Accounts

• Tcode: SPRO-FA-GL-BT-OI Clearing – Clearing diff. – Define tolerance group for G/L accounts

1.31 GL accts for clearing diff

• Tcode: OBXZ

• Explanation:

o Tolerance group define the limit within which differences are accepted

o Here assign the GL a/c to which these diff. are posted

o SAP delivers an exp./ rev a/c in COA INT for this assignment

1.32 Define Foreign Currency Valuation Method

• Tcode: OB59

• Explanation:

o Here we define foreign currency valuation method for the open item

o SAP uses exchange rate type M to value all foreign currency items

o In the valuation method we group together specifications used for valuation

o Before every valuation run we specify the valuation method

o M is the average rate of any F

1.33 Assign GL Accts for foreign currency valuation difference

• Tcode: OBA1

• Explanation:

o GL account to which exchange rate differences due to valuation are posted

o Double click KDB:

 Exchange Rate difference key: It can be kept blank. If entered same has to be updated in the GL Account control data tab (Exchange rate difference key) to revalue the foreign currency account

 Expense Account: Enter GL Account for unrealized foreign exchange loss. Loss is unrealized and automatically reversed next month.

 E/R gains: GL Account for unrealized foreign exchange gain. Can be same as expense account

o Exchange Rate difference in open items (A/R, A/P) KDF : Enter GL codes for accounts receivable/ accounts payable (reconciliation accounts)

 GL Account: GL account mapped to customer in customer master

 Loss : GL Account for exchange rate loss realized

 Gain: GL Account for exchange gain realized

 Val. Loss1: GL account for unrealized exchange loss on valuation of open items (AR, AP)

 Val. Gain 1 : GL account for unrealized exchange gain on valuation of open items (AR, AP)

 Bal. sheet adj. 1: << Ask>>

 SAP system supports two valuation areas in parallel. This account used for first valuation area. First valuation shows local view of company code.

o A currency key must be assigned to every currency used

o For every combination of currencies there can be different exchange rate types (M...)

o Exchange rate is maintained as translation ratio

o Report RFTBFF00: Can update exchange rate table by uploading a exchange rate file in multicash form

o Exchange rate tool: Use a Base currency for exchange rate M. Use the exchange rate spread (-) for buying & (+) for selling.

o Direct Quotation: 1 unit of FC quoted for local currency. 1 USD = 47 INR

o Indirect Quotation: 1 unit of LC quoted for FC.

o Exchange rate table: TCURR

1.34 Define Adjustment for GR/IR clearing acct

• Tcode: OBYP

• Explanation:

o Goods receipt / invoice receipt clearing account is a provisional account & is posted to when we receive goods not invoiced or receive invoice for goods not received.

o Adjustment entries have to be made at the BS date.

o Tcode F.19 analyze GR/IR clearing account and post adjustment entries for goods received but not invoiced & invoice received but goods not received.

 Reconciliation Account

 Adjustment Account

 Target Account

1.35 Integration with OH Cost Controlling

• Tcode: OBYB

• Explanation:

o FI integration with CO, MM, SD

o Allocation happens between two company codes in the controlling module. No FI postings for this in both the company codes. For FI postings to take place following configuration required

o Here define GL a/c's in COA for controlling transactions (Actual CC accrual, Actual settlement, Actual Price calculation) for which no accounts exists in FI

1.36 Integration with material management

• Tcode: OBYC

• Data :

o BSX: Valuation Class (RM) : 3000

o BSX: Valuation Class (WIP) : 7900

o BSX: GL Account (RM) : 119400

o BSX: GL Account (WIP) : 119430

o GBB: Change in Raw Material: 400000

o GBB: Change in WIP: 462001

• Explanation:

o All transactions happening in the MM such as goods receipt, goods issue to cost centers & Production orders trigger FI posting

o Specify GL a/c for MM transactions used in automatic posting in FI

o Valuation Modiff: If selected can maintain GL codes plant wise

o Valuation Class: If selected can maintain GL codes valuation class wise. E.g.: RM, WIP, spare parts etc

o BSX: Here we need to update inventory GL codes.

o BSV : Here we update GL a/c for change in stock a/c

1.37 Integration with Sales & Distribution

• Tcode: VKOA

• Data: ERL : 800000 (Sales Revenue Dom),

• : 800500 ( Sales Revenue deferred)

• Explanation:

o All billing transactions in the SD module will trigger FI posting

o Here we assign GL a/c in COA for revenue a/c determination

1.38 Create GL Acct centrally

• Tcode: FS00

• Explanation:

o Create and Maintain (change, display, block and mark for deletion) GL Accounts Centrally

o Activate the field "Recon. account for acct. type" for accounts considered as reconciliation account e.g. A/R select customer recon account type ,A/P select vendor recon account type ... etc,.

o To lock/ unlock account: Select your account and click Lock/Unlock Button .

 Click Blocked for creation. ( At Chart Of Accounts Level )

 Click Blocked for posting. ( At Chart Of Accounts Level )

 Click Blocked for planning. ( At Chart Of Accounts Level )

 Click Blocked for posting. ( At Company Code Level)

o The GL account may be deleted only if no posting has been made to this account. The GL account deletion process is performed be a special program

 Click Delete Button

 Click Mark for deletion. ( At Chart Of Accounts Level )

 Click Mark for deletion. ( At Company Code Level)

• Explanation:

o Create and maintain GL a/c centrally ( create, change, display, block & mark for deletion)

o Can also create GL A/C with reference to sample a/c

o Type / Description: Data at COA level.

o Control data : At company code level

o Recon a/c : AR select customer recon, AP select vendor recon

o Block GL a/c: Click (lock) - block at COA / co. code level

o Mark GL a/c for deletion: Click (del dustbin icon) - GL a/c deleted by a spl program

o Maintenance / change of GL a/c

1.39 Create Sample account

• Tcode: FSM1

• Explanation:

o A sample account is a master record containing data that is transferred when you create G/L account master records in the company code area.

o Sample accounts are dependent on the chart of accounts.

o You must not enter sample accounts in the chart of accounts as G/L account master records

o Cannot post to a sample a/c

o Change sample a/c : FSM2

o Display sample a/c : FSM3

o Delete sample a/c : FSM5

1.40 Copy GL master data from Source company code to Target company code

• Tcode: FS15

1.41 Mass maintenance of GL a/c

• Tcode: OB_GLACC11

• Tcode: OB_GLACC12

• Tcode: OB_GLACC13

• Explanation:

o If individual change in GL a/c use FS00

o If mass change in GL a/c use OB_GLACC11. Can change a/c group, nature of a/c

o Mass maintenance of GL a/c (FS00) company code data. i.e. Field status group, Currency, Tax category use OB_GLACC12

o For name change OB_GLACC13

1.42 GL a/c posting

• Tcode: F-02

• Explanation:

o Can post to any General Ledger & sub ledger (Vendor/Customer/AA) using proper posting key

o PstKy Determine: This key determines several factors: account type (K, D, S, A) type of posting (debit or credit) and layout of entry screens. Fields : Type SA Identifying the type of doc. Posted

1.43 Posting with Reference Document

• Tcode: FBR2

• Explanation:

o Allows you to post a new accounting document using a previously posted FI document as a reference

1.44 Incoming Payment

• Tcode: F-06

• Explanation:

o Post incoming payment.

o DR Bank A/c. CR Customer / Vendor / GL a/c.

o Clear OI on this a/c

o e.g.: payment received from customer, cleared against customer invoice. During clearing, the system enters a clearing document number and the clearing date in these items. In this way, invoices in a customer account are indicated as paid, and items in a bank clearing account are indicated as cleared

o To post your entry, click Save Button. The system stored two documents:

 A payment document,

 A separated clearing document that contains the information about cleared documents.

1.45 GL Account line item analysis

• Tcode: FBL3N

• Explanation:

o Report allows to display & change GL line items provided

 This G/L accounts is managed with line item display

 The account master is not defined as a Reconciliation account.

o Double-click on the document number to display document details

1.46 GL Account analysis

• Tcode: FS10N

• Explanation:

o The account balance displays:

o The opening balance (the balance carried forward from the previous year)

o The total of all transactions for each posting period, broken down into debit and credit postings (transaction figures)

1.47 GL manual a/c clearing

• Tcode: F-03

• Explanation:

o There are some postings on GL account that are not cleared. You want to clear these postings manually

o To clear open line items in GL accounts

o You can clear also the transactions posted in different currencies. The system will automatically calculate and post exchange rate differences

1.48 Outgoing payment

• Tcode: F-07

• Explanation:

o Post outgoing payment

o You credit your bank account and on the debit side you can post a GL, Customer or Vendor account and clear open item(s) on this account.

o Typical example of an open item is a vendor invoice that has not been settled

o During clearing, the system enters a clearing document number and the clearing date in these items. In this way, invoices in a vendor account are indicated as paid, and items in a bank clearing account are indicated as cleared

1.49 Change a posted GL document

• Tcode: FB02

• Explanation:

o To add more information to already created documents like change text or assignment field.

1.50 Display GL Document

• Tcode: FB03

• To find any document in the system: SE38 - RFBUEB00 and RFBUEB01

• To find gaps in document number assignment: SE38 - RFBNUM00

• Explanation:

o Display a previously posted document and print it. You can display any document that was posted in FI module (including document that was created e.g. in Logistics, but it was followed by automatic FI document posting).

o You can display your document in different currency. Click Display currency Button.

o You can display also other document details, like e.g. who posted this document. Choose Document Header button. You can see that the user SBTP000197 posted this document on 18th July 2002

• Document type define following:

o Number ranges for document

o Account types(S/D/K/M) permitted for postings

o The field status of the document header fields (Display, Hide...)

Document Type Purpose

AB Posting to all document types

DG Posting to customer / GL accounts

RV Sales Order billing

RE Material Management billing

1.51 Individual Document Reversal

• Reverse Individual Document: FB08

• Check which reversal reasons can be used to perform reversal by negative postings / Alternative posting date allowed : SPRO- Financial Accounting→General Ledger Accounting -Business Transactions → Adjustment Posting/Reversal → Define Reasons for Reversal

• Explanation:

o If you don’t know the document number, click Find documents Button .

o The system provides a function to reverse G/L, customer, and vendor documents both individually or in a mass reversal. When you reverse a document, you have to enter a reversal reason that explains the reversal. Documents with cleared items cannot be reversed. The document must first be reset (FBRA)

o Reversal Reasons:

 01 Reversal in current period

 02 Reversal in closed period

 03 Actual reversal in current period

 04 Actual reversal in closed period

 05 Accrual/deferral posting

 Reasons 03 and 04 allow “negative” postings. To post a negative reversal, the following prerequisites must be fulfilled: The company code must be defined as allowing negative postings (OBY6). The document type must allow negative postings.

1.52 Mass Reversal of Documents

• Tcode: F.80

• Explanation:

o Document to be reversed cannot include already cleared items. If you want to reverse document that was already cleared, you need to reset all cleared items before posting a reversal

1.53 Post /Hold / Park/Edit / GL Doc.

• Tcode: FB50 ( Post/Hold / Park)

• Tcode: FV50 ( Edit & Post Park documents)

• FB11 (To see Hold document)

• Explanation:

o Can hold a doc before posting it. Can be a single entry doc. Can be edited & posted.

o Hold doc to be converted using. SE16-RFTMPBL4

o To post a hold doc. - FB50 / FB11-Tree on- Select hold doc.-edit- post

o Diff. between hold & Park doc.: Hold has user defined number & can be edited & posted by same user. Park has number range derived number & can be edited & posted by other users

o Table name to check MIRO held documents: RBKP

o Press Push Button Editing Option- Here we can select doc type option and other master data options

o Maximum Line item allowed is 999. For more line items need to create routine which will split the incoming entry into more than one document.

o Can park a doc before posting it

1.54 Copying GL Accounts to Company Code

• Tcode: OBY2

• Explanation:

o Transfer GL A/C master data from source co. code to target co. code.

o Create a batch to copy GL a/c from source co. code to target co. code

o Execute batch in SM35

1.55 Display T codes

• Tcode: SAP Easy access- Extras - Settings - Display technical names

1.56 Create new company code by copying existing co. code

• Tcode: EC01

• Explanation:

o Imp all dependent tables get copied. Copy 0001/1000/3000

1.57 Automatic Acct determination

• Tcode: FBKP

1.58 Create reference document for GL entry

• Tcode: FKMT

• Explanation:

o It can contain any number of G/L account items and can be changed at any time. In contrast to sample documents, the G/L account items for account assignment models may be incomplete

• Posting with reference to Account assignment model:

o FB50 – Environment - Complex posting - Act assgnmt model

1.59 GL post with clearing

• Tcode: F-04

• Explanation:

o Using the posting with clearing function, you enter document line items and then select the open items to be cleared. Once you have fulfilled all the prerequisites for clearing, the system clears the open items

• With manual clearing there are 3 way of clearing an open item (full , partial , residual)

• Residual & Partial Clearing:

o A residual item results when a payment is made for less than the actual amount outstanding. You clear the original open item, and the system posts a new open item. This new open item is for the same amount as the original open item minus the amount paid

o A partial payment is a payment that is posted to an account without any open items being cleared. You assign this partial payment to an open item. The original open item and the partial payment remain open.

o For automatic clearing there are 2 transaction codes :

 F.13 - Without Specification of Clearing Currency

 F13E - With Clearing Currency Specified.

1.60 GL account automatic clearing

• Tcode: F.13

• Tcode : F13E ( Automatic clearing with clearing currency specified)

• Configure F.13 : OB74

• Explanation:

o Automatic clearing allows you to clear many GL accounts in one transaction run. In customizing we can define up to three fields that are treated by the system as the sort criteria for clearing. For instance, we can decide that all the documents with the same value in the field “Assignment” can be cleared

o Automatic clearing is run through batch job nscfia3946_786-pgrir5. When we run F.13 for GR/IR acct 20802000 systems considers the matching amount for clearing. Then it matches the assignment field for these amounts. Further the sort key in the GL master defines the assignment field in the document. For GL acct 20802000 sort key is 014 (Purchase Order) thus if PO number matches for these two amounts the amounts are cleared against each other.

o The GL account for automatic clearing of items must be flagged as open item

o Activate check box include tolerances if you want the system to clear the GL a/c line item balances within the tolerances defined

o Check the tolerance group assigned to the GL a/c in FS00, under tolerance group.

o Now check the GL a/c tolerance in OBA0

o The tolerances will be maintained in Tcodes as below.

 GL: OBA0

 Vendor/Customer - OBA3

 Employee - OBA4

o There are five criteria’s you can mention. Normal practice is giving ZUONR (Assignment) as one criterion. The sort key in the vendor master defines the assignment field in the document. A meaningful sort key should be used to facilitate the automatic clearing process. Use tcode OB74 to check automatic clearing settings.

1.61 Accounting Editing Options

• Tcode : FB00

• Explanation:

o You can set-up your system settings to speed up data processing or just to make the system more “friendly” for a user. All settings you enter here are stored in your user master data and are user-dependant

1.62 FBRA GL Reset Cleared items

• Tcode : FBRA

• Explanation:

o The document that contains cleared items cannot be reversed directly. You need to first reset cleared items. During clearing open items the system always creates a clearing document

o If you don't know the clearing document number, open another SAP session, select transaction code FB03 (document display) and press List button to search for the required document

o You can display some details regarding the clearing document before resetting it. Click e.g. Accounts Button . The system will display all the accounts involved in clearing operation:

o Click Items Button to display documents cleared by the clearing operation

o You can choose to only reset cleared items or reset items and reverse the accounting document that is connected with clearing operation

o Tables to check Clearing documents in SE16 / ZSE16N:

Table name Category

BSAK Vendor

BSAD Customer

BSAS GL

1.63 Recurring Entry

• Create Recurring Entry : FBD1

• Display Recurring entry : FBD3

• Change Recurring entry : FBD2

• Explanation:

o The recurring entry function helps to automate postings of transactions that repeat every months (with the same amount) e.g. Accruals / Deferrals postings. The system uses the recurring entry original document that you’ve entered as a reference. It is not an ‘real’ accounting document and therefore does not affect the account balance. However, at a specified date, when a recurring entry document will be processed, it will generate automatically the accounting documents and postings will affect account balances.

1.64 Enter translation rates

• Display forex exchange rates: OB08

• Tcode: S_BCE_68000174

• Explanation:

o Exchange rates are defined in the system. Exchange rate is important because we have to:

 Translate foreign currency amounts when posting or clearing

 Determine the gain and loss from exchange rate differences

 Evaluate open items in foreign currency

o The exchange rates are defined by period ("valid from)

o By default, the system uses the type M exchange rates for foreign currency translation when posting and clearing documents.

1.65 Enter accrual & deferral documents

• Tcode: FBS1

• Explanation:

o Accruals Expenditure/ Prepaid Expense: Any expenditure before the closing key date which represents an expense for any period after this date.

o Deferrals Income: Deferred income is any receipts before the closing key date that represent revenue for any period after this date.

o The accruals can be reversed later automatically or manually using F.81

1.66 Reverse Accrual/Deferral documents

• Tcode: F.81

• Explanation:

o Reverse previously posted accrual / deferral. The system posts a reversal by entering an identical amount to the opposite side of the account, thereby offsetting the original amount.

1.67 Cross Company Code Document

• FBU2 - Cross Company Code Document – Change

• FBU3 - Cross Company Code Document – Display

• FBU8 - Cross Company Code Document – Reverse

• Explanation:

o These documents allow posting for more than one company code. It is possible to involve several companies in a cross-company code transaction. The system posts a separate document with its own document number in each of the company codes