SAP Treasury

1. Treasury / Bank
   

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

1. 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)
        

1. Make Global settings for EBS
   

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

1. Enter COA: CAUS
   
2. Create Account Symbols.
   
3. Assign these account symbols to GL accounts
   
4. Create keys for posting rule
   
5. 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

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

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

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

1. Create and assign business transactions;
   

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

1. Define Variant for check deposit
   

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

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

1. Cash Journal
   

• << Refer TFIN>>
  

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

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

1. 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" –
    
  • 
    

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

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

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

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

1. Adding VAT Codes
   

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

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

1. Check Access Sequences, Tax Condition Type
   

• Tcode: OBYZ
  

1. Tax Jurisdiction structure
   

• Tcode: OBCD
  

1. Sales & Use Tax Automatic assignment
   

• Tcode: OB40
  

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

1. 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):

1. 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)
   
2. Go to Tcode FTXP. Copy from the existing tax code, change the %, change the description, check the account mapping & save the new tax code
   
3. 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

1. 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.
      
2. Never change an existing account mapping as that will affect countries which are already using that code
   
3. 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
   

1. VAT new Tax code Creation Business Process:
   
2. A Kintana is always required.
   
3. Approval should be taken from Winco Rebergen before creating any tax code.
   
4. 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.
   
5. 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.
   

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

1. Tax Posting (AP/AR)
   

• Tcode: FB41
  

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

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

1. Next assign a country to a calculation procedure (AT Austria = TAXAT).
   
2. 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

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

1. 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.:
   
2. 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.
   
   
   
    
3. VAT Return configuration
   
4. 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.
   
5. 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

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

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

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

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

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

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

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

1. 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)
    

1. Assign Company code to Fiscal Year Variant
   

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

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

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

1. Assign Posting Period Variant to Company Code
   

• Tcode: OBBP
  

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

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

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

1. GL A/c default settings & layouts
   

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

1. 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. Define Rules to change data / text in a field:
   

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

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

1. Assign Field Status Variant to Company code
   

• Tcode: OBC5
  

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

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

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

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

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

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

1. Assign Company code to Company
   

• Tcode: OX16
  

1. Check SAP Note: SNOTE
   

• Tcode: snote
  

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

1. Create a Financial Statement version
   

• Tcode: OB58