ML_Not Distributed Line in ML analysis

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

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

 

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.: 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.
   
   
   
2. 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

1. 
   
   General Ledger
   
   
   
   
2. 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.
  
  
  
  
  

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

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

 

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

 

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)
      

 

 

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

 

 

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

 

 

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

 

 

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

 

 

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

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

 

 

 

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:
    
  • 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.
    

 

 

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 doc. 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
  
• 
  
  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.
    

 

 

 

1. Assign Company code to Company
   

• Tcode: OX16
  

 

 

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

 

 

1. Define Tolerance groups for GL Accounts
   

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

 

 

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

 

 

 

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

 

 

 

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

 

 

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

 

 

 

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

 

 

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

 

 

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

• Tcode: FS15
  

 

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

 

 

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

 

 

1. Posting with Reference Document
   

• Tcode: FBR2
  
• 
  
  Explanation:
  • Allows you to post a new accounting document using a previously posted FI document as a reference
    

 

 

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

 

 

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

 

 

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

 

 

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

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

 

1. Change a posted GL document
   

• Tcode: FB02
  
• 
  
  Explanation:
  • To add more information to already created documents like change text or assignment field.
    
  
  
  

 

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

 

 

1. 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:
  
  • If you don't know the document number, click Find documents Button.
    
  • 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)
    
  • 
    
    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. 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
    

 

 

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

• Tcode: FB50 ( Post/Hold / Park)
  
• Tcode: FV50 ( Edit & Post Park documents)
  
• FB11 (To see Hold document)
  
• 
  
  Explanation:
  
  • Can hold a doc before posting it. Can be a single entry doc. Can be edited & posted.
    
  • Hold doc to be converted using. SE16-RFTMPBL4
    
  • To post a hold doc. - FB50 / FB11-Tree on- Select hold doc.-edit- post
    
  • 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
    
  • Table name to check MIRO held documents: RBKP
    
  • Press Push Button Editing Option- Here we can select doc type option and other master data options
    
  • 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.
    
  • 
    
    Can park a doc before posting it
    
    
     
    

 

1. Copying GL Accounts to Company Code
   

• Tcode: OBY2
  
• 
  
  Explanation:
  
  • Transfer GL A/C master data from source co. code to target co. code.
    
  • Create a batch to copy GL a/c from source co. code to target co. code
    
  • Execute batch in SM35
    

 

 

1. Create new company code by copying existing co. code
   

• Tcode: EC01
  
• 
  
  Explanation:
  
  • Imp all dependent tables get copied. Copy 0001/1000/3000
    

 

 

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

 

 

1. 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:
  
  • 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
    
  • 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.
    
  • 
    
    For automatic clearing there are 2 transaction codes :
    
    • F.13 - Without Specification of Clearing Currency
      
    • F13E - With Clearing Currency Specified.
      

 

 

1. GL account automatic clearing
   

• Tcode: F.13
  
• Tcode : F13E ( Automatic clearing with clearing currency specified)
  
• Configure F.13 : OB74
  
• 
  
  Explanation:
  
  • 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
    
  • 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.
    
  • The GL account for automatic clearing of items must be flagged as open item
    
  • Activate check box include tolerances if you want the system to clear the GL a/c line item balances within the tolerances defined
    
  • Check the tolerance group assigned to the GL a/c in FS00, under tolerance group.
    
  • Now check the GL a/c tolerance in OBA0
    
  • 
    
    The tolerances will be maintained in Tcodes as below.
    
    • GL: OBA0
      
    • Vendor/Customer - OBA3
      
    • Employee - OBA4
      
  • 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. 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
    

 

 

1. FBRA GL Reset Cleared items
   

• Tcode : FBRA
  
• 
  
  Explanation:
  
  • 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
    
  • 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
    
  • 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:
    
  • Click Items Button to display documents cleared by the clearing operation
    
  • You can choose to only reset cleared items or reset items and reverse the accounting document that is connected with clearing operation
    
  • Tables to check Clearing documents in SE16 / ZSE16N:
    

Table name	Category
BSAK	Vendor
BSAD	Customer
BSAS	GL

 

 

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

 

1. Enter translation rates
   

• Display forex exchange rates: OB08
  
• Tcode: S_BCE_68000174
  
• 
  
  Explanation:
  
  • 
    
    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
      
  • The exchange rates are defined by period ("valid from)
    
  • By default, the system uses the type M exchange rates for foreign currency translation when posting and clearing documents.
    

 

 

1. Enter accrual & deferral documents
   

• Tcode: FBS1
  
• 
  
  Explanation:
  
  • Accruals
    Expenditure/ Prepaid Expense: Any expenditure before the closing key date which represents an expense for any period after this date.
    
  • Deferrals Income: Deferred income is any receipts before the closing key date that represent revenue for any period after this date.
    
  • The accruals can be reversed later automatically or manually using F.81
    

 

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

 

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