Você está na página 1de 274

c 


  

By: Kunal

Landscape is like a server system or like a layout of the servers or some may even call
it the architecture of the server viz. SAP is divided into three different landscapes
DEV, QAS and PROD.

u DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, and 180-
Unit Test.
u QAS may again have multiple clients for ex: 300- Integration Test, 700 to 710
Training.
u PROD may have something like a 200 Production.

These names and numbers are the implementer's discreet on how they want it or they
have been using in their previous implementations or how is the client's business
scenario.

Now whatever you do in the Sandbox doesn't affect the other servers or clients.
Whenever you think you are satisfied with your configuration and you think you can
use it moving forward, you RE-DO it in the golden client (remember, this is a very
neat and clean client and you cannot use it for rough usage). As you re-do everything
that you had thought was important and usable, you get a transport request pop up
upon saving every time. You save it under a transport request and give your
description to it. Thus the configuration is transported to the Unit Test client (180 in
this example).

You don't run any transaction or even use the SAP Easy Access screen on the 100
(golden) client. This is a configuration only client. Now upon a successful transport
by the Basis guy, you have all the configuration in the Testing client, just as it is in the
Golden client. The configuration remains in sync between these two clients.

But in the Testing client you cannot even access SPRO (Display IMG) screen. It's a
transaction only client where you perform the unit test. Upon a satisfactory unit test,
you move the good configuration to the next SERVER (DEV). The incorrect or
unsatisfactory configuration is corrected in Golden (may again as well be practiced in
the sandbox prior to Golden) and accordingly transported back to 180 (Unit Test) until
the unit test affected by that particular configuration is satisfactory.

The Golden client remains the 'database' (if you want to call it that) or you may rather
call it the 'ultimate' reference client for all the good, complete and final configuration
that is being used in the implementation.
Ñ


Landscape: is the arrangement for the servers

IDES : is purely for education purpose and is NOT INCLUDED in the landscape.

DEVELOPMENT ---> QUALITY ----> PRODUCTION

DEVELOPMENT: is where the consultants do the customization as per the company's


requirement.

QUALITY: is where the core team members and other members test the
customization.

PRODUCTION: is where the live data of the company is recorded.

A request will flow from Dev->Qual->Prod and not backwards.

1. Sandbox server: In the initial stages of any implementation project, you are
given a sandbox server where you do all the configuration/customization as per
the company¶s business process.
2. Development Server: - Once the BBP gets signed off, the configuration is done
is development server and saved in workbench requests, to be transported to
Production server.
3. Production Server: This is the last/ most refined client where the user will work
after project GO LIVE. Any changes/ new development is done is development
client and the request is transported to production.

These three are landscape of any Company. They organized their office in these three
ways. Developer develops their program in Development server and then transports it
to test server. In testing server tester check/test the program and then transport it to
Production Server. Later it will deploy to client from production server.

u Presentation Server- Where SAP GUI has.


u Application Server - Where SAP Installed.
u Database Server - Where Database installed.

 
c  




R/3 stands for real-time three tier architecture. This is the kind of architecture SAP
R/3 system has.

R/3 means three layers are installed in Different system/server and they are connected
with each other.

1) Presentation
2) Application
3) Database

c    


 
 


Golden client contains all the configuration data and master data so some extent. All
the configuration settings are done in golden clients and then moved to other clients.
Hence this client acts as a master record for all transaction settings, hence the name
"Golden Client".

 Ñ 



Implementing a package can be a traumatic affair for both the customer and the
vendor. Get it wrong and the vendor may get paid late or have to resort to lawyers to
get paid and tarnish their reputation. For the company the new package may not
work the way they expected, be late or cost a more than budgeted for and take
management will take their eye off running their business.

Recently a client asked me what I would consider to be the five most important things
one should consider before embarking on an implementation. This isn't a simple
question, although there are many factors to think about after some consideration for
me the top five are way ahead of the others.

My top five factors to consider would be:

1. Set up a Project Board,


2. Secure the resources,
3. Complete the GAP Analysis,
4. Have detailed Cut Over Plans,
5. Train the users.

Taking each one in turn:


Π   
The correct set up and operation of the Project Board in my view is major factor in the
success failure of the project. The Project Board will consist of the stakeholders, key
users and the vendor. The Project Board is part of the governance of the project.
The Project Board will meet regularly to ensure that the project plans are created and
being executed as planned, moves from stage to stage with all the deliverables being
signed off is resourced properly.

Π  
Three types of resources are absolutely necessary -- end users, change team and
technicians.

Early involvement by the end users is absolutely necessary, as they will be the ones
living with the system for hopefully many years to come. They will want to feel
involved in its implementation. Buy in from the end users of the system is absolutely
essential if the system is to have a long and stable life in any organisation.

The Change Team will identify the gaps between the package and the business
requirements, re-engineer some of the businesses process to cope with the package,
train the users to ensure implementations is smooth as possible into the business.

The Technical Team will prepare the systems environment for the package, apply any
software fixes from the vendor, implement the software in the best way possible for
the organisation set up and tune the software for the particular technical environment.

! 

A through gap analysis will identify the gaps between how the business operates ad its
needs against what the package can can't do. For each gap there will be one of three
outcomes which must be recorded and actioned, GAP must be closed and customised
software can be developed close the gap, GAP must be closed but software cannot be
written therefore a workaround is required, GAP does not need to be closed.

In simple terms: Gap means small cracks. In SAP world. In information technology,
gap analysis is the study of the differences between two different information systems
or applications( ex; existing system or legacy system with Client and new is SAP),
often for the purpose of determining how to get from one state to a new state. A gap is
sometimes spoken of as "the space between where we are and where we want to be."
Gap analysis is undertaken as a means of bridging that space.
Actual gap analysis is time consuming and it plays vital role in blue print stage.

" #$ 



Detailed plans need to be developed for cutting over from the old system(s) to the
new. Parallel runs of what will happen over the conversion period using test data,
convert and watch for a period after wards to ensure nothing unexpected happens.

Œ
 %
Well trained users will support and defend the system on site. Unsupportive users
will continually undermine the system and eventually it will be replaced. Therefore
the more effort you put into helping the users master the system early the better.

&Ñ"#" 
 '


"
   
 
 
  (  )
*   
)

'

c   

  

A More than one chart of accounts can be created for each client
B The chart of accounts contains all the G/L accounts, vendor accounts and customer
accounts
C More than one company code can be allocated to the same chart of accounts
D The chart of accounts controls all the customizing settings in the R/3 system
E All accounts within a chart of accounts must have the same tax code

Answer : A

'

c   " +


 

 

A. Cash management position


B. Liquidity forecast
C. Credit limit report
D. G/L account balances
E. Bill holdings

'

c   
 
   
 
 $(

A. Incoming payment
B. Down payment request
C. Credit memo
D. Transfer posting
'

c 
 

#$  "# ,  

  
(
 

A. Order status
B. Order type
C. Settlement type
D. Curreny
E. Classification code

'

c 
 

#$  "# , 
(
 

  
 )
c  
 $$(

 

A. Cost center
B. Orders
C. General ledger accounts
D. Asset
E. Vendor

'

Ñ
"

, 

 (
 , 


,  

   

 )
c   
 (
"



A. G/L account
B. Work center
C. Cost center
D. Activity type
E. Supplier

'

c 
#$  ""

 $   )
 $

  -).$,

 $ (

 )
c   
 (

*(



A. Sender. Cost Center, Order, Project


Receiver. Cost Center, Order, Project
B. Sender. Order
Receiver. Cost Center, Project
C Sender. Cost Center
Receiver. Cost Center, Order, Project, Cost Object

'

  
 $  
"

)Π  




 /) c      
  +Ñ Ñ+%+  ( 
*
    


A. The posting period has been closed.


B. Materials have been withdrawn.
C. Personnel costs have been incurred.
D. Overhead has been incurred.
E. An order was closed.

&ь &
" 

I passed my SAP FI certification ECC 6.0. I want to thank each one of them in the
group for their support.

People who are going to attend the certification exam kindly concentrate on the
TFIN50 and TFIN52

Tips for people who are going to attend the exam:

u Understand the concepts. Don't memorize.


u If possible kindly practice the configuration part (Not mandatory).
u Do the preparation based on the syllabus not based on books. {You will be
getting 99% from the syllabus}
u You have to cover all the chapters.
u No straight Questions.
u You will be getting chapter wise questions like AA, Masters, APP, NEW GL
and so on..............

³But one thing I can say if you are through with syllabus 'YOU' can easily pass´.

Take the certification date only once you finish one round of study of all books.

Two types of Questions:

u Single answer questions {SAQ will be around 10 - 15 questions and remaining


will be True/False}
u A statement will be given. Based on that 4 to 6 options. You have to select each
option is True or False.

( 0 /


  -
(/
* 
2 questions on depreciation area, 3 questions on asset
Asset Accounting - 13
class, 4 questions on asset transactions and
questions
depreciation
Closing Operations in 1 question on M/E closing, 3 on Balance
Financial Accounting - 5 confirmations
Main questions on cash discount, 1Q on Cross
Co.Code, 1Q Doc Reversal, 2Q on Foreign currency,
Document and Posting Control
1Q on authorisation, 1Q on FSG, 1Q on posting
- 14
period, 1Q on tolerance group, NO questions on
TAX.
Evaluation Options in 2 Q on list viewer and 3 questions on drill down
Reporting - 7 report
Financial Accounting Master 3Q on Bank, 4Q on Customer, 3Q on Vendor, 2Q on
Data - 15 GL
Payment Program, Dunning
Program, Correspondence, 3 questions on payment program
Interest Calculation - 6
SAP Overview - 5 2 Questions related to MM, 1 on navigation
SAP Solution Manager - 4 2Q on Roadmap
Special General Ledger
Transactions, Document 1Q on Park & Post, 2Q on Splgl, 2Q on Substitution
Parking, Validation & & Validation
Substitution - 6
The New General Ledger -5 1 on Basics, 2 on document split, 1 on reports

&ь &
" 

c "

APC stands for Acquisition and Production costs. Acquisition means any asset which
you may acquire/ purchase externally. It includes invoice price and other related exp.
Associated with it like customs, octroi, freight which you add and arrive at total cost
of acquisition for capitalization of the asset. For ex Say a computer. The total cost
which you incur for the acquisition of the computer including installation will be your
APC

Production cost means any asset which is created internally within the organization.
This is normally created by means of AUC and you go on adding cost to the AUC as
and when you incur exp. for the same. For ex. say addition to the office building.
Therefore APC incudes any external acquisition or internal construction of exp. which
needs to be capitalised.

In OADB under 01 deprn area Acquisition & prod Cost tick is activated. *--
+1(
2)2

Œ     , Ñ $ 


$ ,  
(  $ *
 
$
  
  
, *
   *
     /
    ( *
,
  (   
$) .   /
  ( 
 

,
 

 
 /
 1))  )

Pl. prepares you on the following broad lines:

Implementation exp.:

Brief about the project you did: w.r.t. the main activity of the client, How many plants
they had, What modules were implemented, Who were the implementers, What¶s the
implementation team size, How many were in your module team, What¶s your role in
the project with respect to the activities you partook in the project, The Enterprise
Structure with regard to the no. of Company Codes, any Business Areas or Profit
Centers defined, Cost Centers defined, What¶s the period of the project, When did
they Go-Live?, Any issues you¶d solved during µSupport¶ phase?

Questions on conceptual understanding:


a) SAP R/3 definition and 3-Tier Architecture
b) µReal time integration¶ advantage of SAP
c) ASAP methodology
d) Solution Manager
e) Client / Company / Company Code / Business Area
f) Business Area vs Profit Center Approach
g) How effective will be the Financial Statements generated through Business
Areas
h) With Holding Taxes vs Extended WHT
i) Field Status Concepts (G/L master fields controlled through Account Group and
Document entry through Field Status Group set in the G/L master)
j) Special G/L transactions
k) Open item management
l) Reconciliation Accounts
m) Subsidiary Ledgers
n) Sort key
o) Negative Postings Allowed
p) Special periods
q) Only balances in local currency
r) Important Posting keys for G/L, A/R, A/P, AA, Stock Entries
s) Assessment vs Distribution
t) Org. Structure for FI
u) Org. Structure for CO
v) Product Costing: How the values flow in the system

Configuration:
a) Extended With Holding Taxes configuration steps ± right from creation of WH
Tax Types, Codes to Annual Return
b) FI-MM Integration (OBYC configuration with particular reference to Off-
Setting entries)
c) FI-SD integration
d) Down Payments transactions
e) Interest ± Balances / Arrears
f) Asset Accounting: Asset Class, Main Asset, Sub-Asset, Group Asset, Dep.
Areas, Dep. Key, Transaction No.s (100- External acquisition, 210 ± Retirement with
Revenue, etc.), Imp. Transaction Codes.

General questions:
a) Educational Background
b) What influenced you to go in for SAP career?
c) Functional Career
d) Present earnings vs Expected pay
e) Inclination to relocate

&&ь
 Ñ
$'
3

3) Œ  ( &Ñ #


1
  
Ans: Client
|
Operating Concern
|
Controlling area1 Controlling Area 2
|
Co. Code 1 Co. Code 2
|
Bus area 1 Bus area2 Bus Area3 Bus Area 4

ÿ).
 
    ( 
 ,   
     
Ans: 12 Normal posting period and 4 special periods are in the fiscal year which can
be used for posting tax and audit adjustments to a closed fiscal year.

)c     


 
   
Ans: PPV is used to open and close the periods based on a/c types considering GL
Accounts. Tr. Code. OB52.

4)c    


 
 " 
   !( 

Ans: 4 digit Alphanumeric key.
Name of the company
City
Country
Currency
Language
Address

5)c    


  , 
     
 6- )
Ans: Document type is nothing vouchers containing line items. Several business
transac! tions can be identified within a particular document type.
It controls the document number ranges.
It controls the Header part of document
IT controls the line item level of the document
Helps filing of physical document

7) c   


 * 
     

Ans: These are special classification keys. Two character numerical key it controls the
entry of line items.
Posting key determines Account type, Debit/credit posting, Field status of transaction.

8) c       ,     



Ans: FSG is mandatory field in ! GL Creation. You use this field to define which
fields are displayed when you post business transactions to a G/L account.
A field may have one of the following statuses.
- Suppressed
- Display
- Optional
- Required

^)c   



 
  
 
(
 
  

Ans: Chart of account is a list of all G/L accounts used by one or several company
codes.

For each G/L account, the chart of accounts contains the account number, account
name, and the information that controls how an account functions and how a G/L
account is created in a Company code.

You have to assign a chart of accounts to each company code. This chart of accounts
is the Operating chart of accounts and is used for the daily postings in this company
code.

You have the following options when using multiple company codes.
You can use the same chart of accounts for all company codes

If the company codes all have the same requirements for the chart of accounts set up,
assign all of the individual company codes to the same chart of accounts. This could
be the case if all company codes are in the same country.

In addition to the operating chart of accounts, you can use two additional charts of
accounts If the individual company codes need different charts of accounts, you can
assign up to two charts of accounts in addition to the operating chart of accounts. This
could be the case if company codes lie in multiple countries.

The use of different charts of accounts has no effect on the balance sheet and profit
and loss statement. When creating the balance sheet or the profit and loss statement,
you can choose whether to balance the co! mpany codes which use different charts of
accounts together or separately.

9) c   



      
 


Ans: chart of account key
Name
Maintenance language
Length of the GL Account Number
Controlling Integration
Group chart of accounts (Consolidation)
Block Indicator
3) "
 
 "# ( 
   $  

Ans: yes. One COA can be assigned to several companies.

33: c    


   
     

Ans: Account group determines which fields you can configure on the G/L master
record. It is necessary to have at least two one for B/S and another one for P&L a/c.
It controls the Number ranges of GL A/C.
The status of fields of the master record of GL belongs to company code area.

3ÿ:c  

 
; 
  
  

  
Ans: When you p! ost items to a subsidiary ledger, the system automatically posts the
same data to the general ledger. Each subsidiary ledger has one or more reconciliation
accounts in the general ledger.
We can¶t use reconciliation account for direct postings.

3:.  
 !   
  

<
Ans: Field status variant is maintained all FSGs.

34: c     


  !     
Ans:
- COA Segment
A/C group
Nature of account
Short text
GL a/c long text
Trading partner
Group Account Number
- Company code segment
Account currency
Tax
Reconciliation a/c for a/c type
OIM,LID,FSG.

35: c   &     


    !      

Ans: It controls the account assignments that are made to the account. Specifically the
field status group controls whether postings to cost centers, internal orders,
profitability segments and so on are required, not allowed (suppressed), or optional.

37: c   "


 
  
    
 c      
   

Ans: Operational chart of account ± Day to day activities It is mandatory.
Country COA ± It¶s used for legal specific requirement of each country. It¶s additional
and optional.
Group COA used for consolidation of Company codes. This is for group consolidation
purpose.

38: c      


 
  "=
    
Ans: Segments in Customer Segments in Vendor
- General Data segment General data segment
- Company code segment Company code segment
- Sales area segment Purchasing organization Segment

3^: c    


 
  

 c    
 ( 
  


 
Ans: Open item management is further reconciliation function. OIM allows you to
display the open and cleared items and amounts in an account. OIM should be used if
an offsetting entry is made for every line item posted in the account. The a/c is
reconciled and cleared against another account. Ex. Salary clearing account and
GR/IR Clearing account.

39: c     


 
  

Ans: Residual payment it clears original invoice with incoming amount and create
new line item for remaining outstanding amount.
Partial payment it leaves the original invoice amount and creates new
line item for incoming amount.

ÿ: c   



 
 -

( 

Ans: Internal Number Ranges: Doc. No will be provided by the system automatically
in serial order allotting the next available progressive number. The number must be in
numerical.
External Number ranges: Doc. No will be given manually by the end user. System
will not lock no automatically in this case. User can pick the number randomly.
Number may be an alpha numeric. >00 

 )

&&ь
 Ñ
$'
ÿ

Questions are answer best of my knowledge, if I am wrong, please correct


me..anyone««««

3). 
(
 (
  

 



The Baseline date is used to calculate the due date by taking into account the payment
terms. On the APP, the baseline date helps to pick the relevant invoices for payment.
During the APP run when invoices are pulled into the run, the system checks the
µNext Payment Date¶ before picking the invoices to be paid.

ÿ)   
   *

Procurement cycle ± a sales order is placed on a requirement made by a customer,


after which it is passed on to create a purchase order (this could either happen based
on the requirements on the SO, or a planned SO). the value flow gets passed on to FI
at the time of goods movement. In the case of SD, the impact on FI happens only at
the time of billing.

) 2
 (
 2  
 ,   2  
 
 "
c "

Depreciation ± a decrease in the value of an asset due to wear and tear


Accumulated Depreciation ± the total amount of depreciation calculated on a
particular asset.
APC ± refers to Asset transactions other than depreciation

4)c !Ñc 



    

The GR/IR ± the goods receipt/Invoice Receipt account is used to post to whenever
goods that are not yet invoiced have been received or when invoices arrive b4 the the
delivery of goods.

During the time between the invoice being created and delivery of goods, there can be
a timing difference, in order to accommodate this timing difference, a GR/IR account
is maintained temporarily to record the flow .

5)c   




*  
++
2

Value from MM to FI is defined in OBYC«. on the material master the flow of


values are assigned on the Costing, acctg, etc tabs where the system helps to post the
necessary stock values into the appropriate GL accounts. helps to determine, the GL
accounts updated when there is a movement of goods.

SD-FI - VKOA
7)"


"

 
" 
" ?( 
 
   $
 

  
 


Company code should have same financial year, may have different currencies.

You can assign 2 or more company codes to one controlling area as long as the chart
of accounts are same. Furthermore, if you have different fiscal year variant in the
company code, then make sure that the number of period remain the same.

8)c  



 
, 
$  
   
 )

Yes it is posiiable , but in such situation cost centre will be real and production order
is stastical.

If you assign both cost center and Prd Order then since Prod. Order are real co object,
Cost center entry would be statistical.

^)c  +   ( 




The question is not very clear. If you are talking about CO Master data. Then Cost
center need to be uploaded. You can use Data Transfer Workbench or write abap for
it.

9)"


$
?.  $
 :"(
*



 

Yes can be possible , this can resolved through ranking order and bank optimization in
FBZP.

You use use further selection in proposal paramater, if you would like to filter the
open item based on the city

3)c    


   


Field status.

33)  

   
 
     
 "
  
  
 

c   @ 

 
 

Document header cannont be changed, after posting the document you cannot
change. only if you want to change the document the reseversal entry.
3ÿ)c   ! 
 


The transaction other than A/P and A/R is called the special g/l transaction for ex:
Bills of exchange, Interest payable , aqusition

3). $    




By doing reversal posting.

34)c (
 c   "
 ( 
 

For paymentterms it is used. base line date is the due date.

35) . 
   (  
 (    
  
   
 &Ñ
 

c "",",#+ $

&Ñ"#Ñ
$'


c  /
* /

&Ñ"#Ñ
$'


3)c   


c  $
 

  


A. It is the top level financial structure, contains the GL Accounts we define the all
the accounts and one chart of accounts assign to company code and one chart of
accounts will assign to many company codes . It is list of Gl accounts and it contains
account no , account name, language, length, cost element, blocking information that
controls the how an account functions and how a gl account created in company code .
COA Key.

ÿ)c  
 c   


A. IT determines the which fields you need to configure on the GL master record. It is
necessary to have at least 2, one for B/S and another one for P&L accounts. It controls
the number ranges of GL. The Status fields of the master record of GL Belong to
company code area.

)c  


*c 

A. It controls the line item of GL entry debit and credit.

4)c (

A. Organizational unit of external accounting that corresponds to a specific business
segment or area of responsibility in a company. Financial statements can be created
for business areas for internal purposes. They are primarily used to facilitate external
segment reporting across company codes covering the main operation of a company
(product line, Branches). The Business area may be the branch of the company or
product lines it deals with

5)   



    
,       
 
  

 
   
   
)    
A. Generally when ever we are creating cost elements we can create some of
exependitures manually some automatically so we can create manually cost elements
in defining chart of accounts.

7) 
 $
,  
  * 
   

  $ 
   $


A. We can check through customer group and vendor group it was created by ours
when we are creating vendor and customer groups.

8). *
   
  

A. Yes the system will find out april was first posting period. While configuring fiscal
year we giving april to 1 may to 2, june to 3, like this system will identify april was
the first posting period.

^) 2
       ,  
   $
 A    
$
)

A. FSGV controls the additional account assignments and other fields that can be
posted at the line item level for GL a/c. FSGV can be control at three level i.e.,
1) In OBC4 (ch of a/c¶s) - which controls the screen for a particular GL a/c group,

2) Posting Keys - which controls the screen for a particular posting key transaction is
taken, &

3) Accounting Groups - which controls the screen for a particular account group i.e.,
customer group or vendor group.

A. Posting period variant which controls posting periods, both normal and special
periods are open for each company code. The posting period is independent of fiscal
year variant.
A. Fiscal year is controls the which type year we are following like calendar year,
year dependent year,.

&Ñ"# '


3

1. About evolution in the world of business, we can affirmate that (Please choose the
correct sentence):

a) [ ] The internet revolution could turn available to companies the use of ERP
functionality.
b) [ ] The next generation of ³new dimension´ products appeared taking
functionality out of the company, to bring value through extending the Internet
Revolution.
c) [ ] The internet has driven to a collaborative environment where value is created
through collaboration within business comunities.
d) [ ] In the first the companies were looking at Cost reduction and efficiency through
integration of business comunities.

2. About the definition of ERP and e-business functionalities, we can say that (Note:
we can have more than one correct sentence. Please select the sentences you think
they are correct):

a) [ ] ERP offers enterprise centric functionality (general ledger, payroll, order entry)
to integrate core, internal processes.
b) [ ] ERP is mySAP Financials and mySAP HR.
c) [ ] ERP is SAP R/3, while e-business is mySAP.com.
d) [ ] About Business Model, ERP can be considered as enterprise centric and e-
business, as extended and collaborative.
e) [ ] About Architecture, ERP can be considered as an integrated system and e-
business, as an integrated system and an open integration platform.
f) [ ] About Processes, ERP can have them integrated, core within enterprises and
collaborative, beyond company boundaries.

3. What is a SAP Business Object (Please choose the correct sentence)?

a) [ ] It is all the transaction data generated via transactions.


b) [ ] It is the instancied class of the Class Builder.
c) [ ] It is composed of tables that are related in a business context, including the
related appplication programs and it is maintained in the Class Repository.
d) [ ] It is the representation of a central business object in the real world, such as an
employee, sales order, purchase requisition, invoice and so on.
e) [ ] It is a sequence of dialog steps that are consistent in a business context and that
belong together logically.

4. About BAPI (Business Application Programming Interface), what is true (Note: we


can have more than one correct sentence. Please select the sentences you think they
are correct)?

a) [ ] It is a well-defined interface providing access to processes and data of business


application systems.
b) [ ] BAPIs offer a stable, standardized interface for integrating third-party
applications and components in the Business Framework.
c) [ ] A BAPI is assigned to one and only one business object.
d) [ ] In the R/3 Enterprise version (4.7) we can use BAPI to create an internal order
inside a customized ABAP program.
e) [ ] A business object in the Business Object Repository (BOR) can have many
methods from which one or several are implemented as BAPIs.

5. What can we say about ALE (Application Link Enabling, Note: we can have more
than one correct sentence. Please select the sentences you think they are correct)?

a) [ ] Business processes cannot be distributed using ALE.


b) [ ] The ALE concept is related to an enterprise structure with areas that have
central tasks and areas with tasks that are decentralized.
c) [ ] The applications are integrated via a central database.
d) [ ] The applications are integrated via the message exchange.
e) [ ] The ALE concept supports the implementation and operation of distributed SAP
applications.

6. A company code is:

a) [ ] an independent accounting entity (the smallest organization element for which a


complete self-contained set of accounts can be drawn up).
b) [ ] an organizational unit in an enterprise that represents a closed system used for
cost accounting purposes.
c) [ ] an organizational unit that provides an additional evaluation level for the
purpose of segment reporting, for example.
d) [ ] a dependent accounting entity, according to Fiscal Year.
e) [ ] the highest level in the R/3 system hierarchy.

7. Consider the following sentences:


7.1. The variant principle is a three-step method used in R/3 to assign special
properties to one or more R/3 objects.
7.2. One of the disadvantages to use variants is that it can't deal with the maintenance
of properties, which are common among several business objects.
7.3. For using the variant principle, you must define the variant, populate it with
values and assign it to the R/3 objects.
7.4. This principle is used for Fiscal Years, Posting Periods and so on.

Which of them is false?


a) [ ] 7.1 and 7.2.
b) [ ] 7.1 and 7.3.
c) [ ] 7.1.
d) [ ] 7.2.
e) [ ] 7.3.

8. Consider the following sentences:

8.1. A fiscal year has to be defined by means of separating business transactions into
different periods.
8.2. Special periods are used for postings, which are related to the process of the year-
end closing. In total, 16 special periods can be used.
8.3. The Fiscal Year variant only defines the amount of periods and their start and
finish dates.
8.4. The Fiscal Year is defined as a variant, which is assigned to the chart of accounts.

Which of them are true?

a) [ ] 8.1 and 8.2.


b) [ ] 8.1 and 8.3.
c) [ ] 8.2 and 8.3.
d) [ ] 8.2 and 8.4.
e) [ ] 8.3 and 8.4.

9. What is an independent fiscal year variant (Please choose the correct sentence)?

a) [ ] It is a variant which the postings periods are only equal to the months of the
year.
b) [ ] It is a variant which you can define different number of periods, according to
the year.
c) [ ] It is a variant which each own fiscal year uses the same number of periods, and
the postings periods always start and end at the same day of the year.
d) [ ] It is a variant which allows the use of different number of posting periods.
e) [ ] It is a variant not normally used because of its particularity.

10. Consider the following statements about currencies concepts:

10.1. The currency code identifies each currrency that will be used into R/3 system.
10.2. You have to define all the world¶s currency into R/3 system
10.3. Exchange rate types distinguishes the exchange rates to be considered for
various purposes, such as valuation, translation, conversion, planning, etc.

Which of them is true (Note: we can have more than one correct sentence. Please
select the sentences you think they are correct)?

a) [ ] 10.1.
b) [ ] 10.2.
c) [ ] 10.3.
d) [ ] none of them.
e) [ ] all of them.

11. Consider the following sentences:

11.1. A base currency can be assigned to an exchange rate type.


11.2. To deal with exchange rate spreads, two very efficient combinations of the
exchange rate tools are using a base currency for the average rate (M) and using the
exchange rate spreads to calculate the buying and selling rates (B and G).
11.3. A base currency can be used for an average, a buying or a selling rate.
11.4. The relations between currencies have to be maintained per exchange rate type
and currency pair in the translation factors.

Which of these combinations is true?

a) [ ] 11.1, 11.3 and 11.4.


b) [ ] 11.1, 11.2 and 11.4.
c) [ ] 11.2, 11.3 and 11.4.
d) [ ] 11.1, 11.2 and 11.3.
e) [ ] 11.1, 11.2, 11.3 and 11.4.

12. Consider the following sentences about the direct quotation:

12.1. It is also known as price notation.


12.2. The currency value is expressed in units of the foreign currency per unit of local
currency.
12.3. For direct quotation, the prefix to indicate the rate is ³/´.

What is the correct option?

a) [ ] 12.1.
b) [ ] 12.2.
c) [ ] 12.3.
d) [ ] none of them.
e) [ ] all of them.

13. Consider the following sentences about the indirect quotation:

13.1. It is also known as volume notation.


13.2. The currency value is expressed in the local currency per unit of foreign
currency.
13.3. For indirect quotation, there is no prefix to difference between direct quotation.

What is the correct option?

a) [ ] all of them.
b) [ ] none of them.
c) [ ] 12.3.
d) [ ] 12.2.
e) [ ] 12.1.

14. What of these alternatives are considered master data (Note: we can have more
than one correct sentence. Please select the sentences you think they are correct)?

a) [ ] Chart of Accounts.
b) [ ] G/L Accounts.
c) [ ] Vendor.
d) [ ] Customer.
e) [ ] Asset.

15. What can we define into the chart of accounts customizing transaction (OB13
transaction, Note: we can have more than one correct sentence. Please select the
sentences you think they are correct)?

a) [ ] Description.
b) [ ] Maintenance language.
c) [ ] Length of the company code.
d) [ ] Length of the G/L account number.
e) [ ] Blocking / unblocking chart of accounts.

16. Consider the following sentences about the chart of accounts segment:

16.1. It contains the Company Code, Account number and the field status group.
16.2. Whenever you need to enter information for a company code for an account
number, you have to type again the information related to chart of accounts segment.
16.3. Texts can be displayed using the program ³Account assignment
manual´(RFSKTH00).
16.4. Key words facilitate the search for account numbers.

Which of these combinations are false (Note: we can have more than one correct
sentence. Please select the sentences you think they are correct)?

a) [ ] 16.1.
b) [ ] 16.2.
c) [ ] 16.3.
d) [ ] 16.4.
e) [ ] none of them.

17. True or false?

17.1. Every company code that needs to use an account from the assigned chart of
accounts has to create its own company code segment.
a) [ ] True b) [ ] False

17.2. For P+L statement accounts, the balance is carried forward to the same account.
a) [ ] True b) [ ] False

17.3. In the chart of accounts segment, it is necessary to indicate whether the account
will be a balance sheet or a profit+loss statement account.
a) [ ] True b) [ ] False

17.4. Number intervals for G/L account master records can overlap.
a) [ ] True b) [ ] False

17.5. It is not possible to influence the appearance of an account¶s master data.


a) [ ] True b) [ ] False

18. Consider the following sentences about field status:


18.1. Fields which are _____________ can be ____________.
18.2. Fields which have an entry that ________________ can be set to
_________ only (even in change mode).

Which of the options below matches the blank spaces of those sentences?

a) [ ] used/supressed for 18.1; must be changed/display for 18.2.


b) [ ] not used/supressed for 18.1; must be changed/display for 18.2.
c) [ ] not used/optional for 18.1; should not be changed/supressed for 18.2.
d) [ ] not used/supressed for 18.1; should not be changed /display for 18.2.
e) [ ] used/optional for 18.1; must be changed/display for 18.2.

19. Consider the following sentences about field status:

19.1. Fields which _____________ can be made ____________.


19.2. Fields that can be entered, but are not required, can be set to _________ entry.

Which of the options below matches the blank spaces of those sentences?

a) [ ] must not have an entry/optional for 19.1; suppresed for 19.2.


b) [ ] must have an entry/supressed for 19.1; suppresed for 19.2.
c) [ ] must have an entry/optional for 19.1; optional for 19.2.
d) [ ] must have an entry/required for 19.1; optional for 19.2.
e) [ ] must not have an entry/required for 19.1; optional for 19.2.

20. Consider the following sentences:

20.1. Reconciliation accounts are general ledger accounts assigned to the business
partner master records to record all transactions in the sub-ledger.
20.2. For accounts without line item display, the most important data from the posted
line items is stored in a special index table.
20.3. The account currency must be in the local currency.
20.4. Items in accounts with open item management means the G/L accounts should
have a offsetting posting for a given business transaction.

Which of these are true (Please choose the correct sentence)?

a) [ ] 20.1 and 20.3.


b) [ ] 20.2 and 20.4.
c) [ ] 20.1 and 20.2.
d) [ ] 20.2 and 20.3.
e) [ ] 20.1 and 20.4.


1. C
2. A, C, D, E.
3. D
4. A, B, C, D, E.
5. B, D, E.
6. A

Item ³B´ is the definition of controlling area.


Item ³C´ is the definition of business area.
Item ³D´ is not any definition.
Item ³E´ is the definition of client.

7. D
In fact, the main advantage of using variants is that it is easier to
maintain properties, which are common among several business objects.

8. B
9. C
10. A, C.
Most of the world¶s currencies are already defined into R/3 system.

11. B
Be careful: A base currency can only be used for an average rate, not for a selling or a
buying rate.

12. A
13. E
14. B, C, D, E.
A chart of accounts is a variant, which contains the structure and the basic information
about general ledger accounts.

15. A, B, D, E.
16. A, B.
17. True or false:

17.1. True.
17.2. False. For P+L statement accounts the balance is carried forward to a retained
earnings account and the P+L statement account is set to zero.
17.3. True.
17.4. True.
17.5. False. It is possible to influence the appearance of an account¶s master data
using the field status.

18. D
19. D
20. E

&Ñ"# '


ÿ

1. Since the line item display takes up additional system resources, you should only
use it if there is no other way of looking at the line items. So, you should not activate
the line item display for the following accounts (Note: we can have more than one
correct sentence. Please select the sentences you think they are correct):

a) [ ] P+L Statement.
b) [ ] Reconciliation.
c) [ ] Revenue.
d) [ ] Material Stock.
e) [ ] Tax.

2. Consider the following statements:

2.1. Accounts with open item management must have line item display activated.
2.2. You can activate or deactivate open item management everytime, even if the
account hasn¶t a zero balance.
2.3. You can select both local and foreign currencies as account currency.
2.4. If the account is the local currency, the account can only be posted to this
currency.
2.5. When using the ³Only Balances in Local Currency´ indicator in the master
data record, transaction figures are only managed for amounts translated into local
currency.

Which of the above statements are true (Note: we can have more than one correct
sentence. Please select the sentences you think they are correct)?
a) [ ] 2.1.
b) [ ] 2.2.
c) [ ] 2.3.
d) [ ] 2.4.
e) [ ] 2.5.

3. True or false?
3.1. The ³Only Balances in Local Currency´ indicator must not be set in
reconciliation accounts for customers or vendors.
a) [ ] True. b) [ ] False.

3.2. The ³Only Balances in Local Currency´ indicator is usually set in balance sheet
accounts that are not managed in foreign currencies and not managed on an open item
basis.
a) [ ] True. b) [ ] False.

3.3. Accounts with a foreign currency as an account currency can be posted to any
currency.
a) [ ] True. b) [ ] False.

3.4. You can use a group chart of accounts for internal purposes.
a) [ ] True. b) [ ] False.

3.5. The usage of a financial statement version for the group chart of accounts is
optional.
a) [ ] True. b) [ ] False.

4. What is the disadvantage of using the group chart of accounts (Please choose the
correct sentence)?

a) [ ] Because changes to existing G/L Accounts are effective as soon as they have
been saved and could have extensive consequences.
b) [ ] Because accounts with the account currency as local currency can only be
posted to this local currency.
c) [ ] Because the company codes use different operational chart of accounts, you
cannot carry out cross-company code controlling.
d) [ ] Because the group chart of accounts must be assigned to each operational chart
of accounts.
e) [ ] Because you must enter the group account number in the chart of acounts
segment of the operational account.

5. Consider the following statements:

5.1. You cannot use the country chart of accounts if you desire to use the cross-
company code controlling.
5.2. The disadvantage of using country chart of accounts is the accounting clerks who
may be familiar with the country chart of accounts first have to get used to using the
operational chart of accounts.
5.3. Reconciliation accounts are updated on a daily basis.
Which of them are false (Please choose the correct sentence)?

a) [ ] 5.1 and 5.2.


b) [ ] 5.1 and 5.3.
c) [ ] 5.2 and 5.3.
d) [ ] all of them.
e) [ ] none of them.

6. Which are the segments of the SD view of the customer account master data (Note:
we can have more than one correct sentence. Please select the sentences you think
they are correct)?

a) [ ] Client.
b) [ ] Company Code.
c) [ ] Controlling Area.
d) [ ] Sales Area.
e) [ ] Purchasing Organization.

7. Which are the segments of the MM view of the customer account master data
(Note: we can have more than one correct sentence. Please select the sentences you
think they are correct)?

a) [ ] Client.
b) [ ] Company Code.
c) [ ] Controlling Area.
d) [ ] Sales Area.
e) [ ] Purchasing Organization.

8. What is the segment that makes complete both customer and vendor accounts
(Please choose the correct sentence)?

a) [ ] Client.
b) [ ] Company Code.
c) [ ] Controlling Area.
d) [ ] Sales Area.
e) [ ] Purchasing Organization.

9. What characteristics are configured as standard for every customer/vendor account


(Note: we can have more than one correct sentence. Please select the sentences you
think they are correct)?
a) [ ] Line Item Display.
b) [ ] Company Code.
c) [ ] Currency.
d) [ ] Open Item Management.
e) [ ] Purchasing Organization.

10. Consider the following statements:

10.1. Number ranges for customer/vendor accounts can overlap.


10.2. An one-time account is a special customer/vendor master record which a
company rarely do business.
10.3. The account group is used to control the fields displayed in the master record.
10.4. If you enter an alternative payer, the amount to clear the open items due in the
account is paid by the alternative payer.
10.5. One number range can only be assigned to one account group.

Which of the above statements are true (Note: we can have more than one correct
sentence. Please select the sentences you think they are correct)?

a) [ ] 10.1.
b) [ ] 10.2.
c) [ ] 10.3.
d) [ ] 10.4.
e) [ ] 10.5.

11. True or false?

11.1. For every bank that is used in the system (for example, as a house bank or as a
customer/vendor bank) you have to create a bank master record.
a) [ ] True. b) [ ] False.

11.2. Banks that are used by your company are defined as house banks.a) [ ] True. b)
[ ] False.

11.3. You cannot create bank master data when entering bank information in the
customer or vendor master record.
a) [ ] True. b) [ ] False.

11.4. Bank Account and G/L Account are the same master data object.
a) [ ] True. b) [ ] False.
11.5. Customers that use the lockbox function can create a batch input session that
automatically updates customer banking information in the master record.
a) [ ] True. b) [ ] False.

12. Consider the following statements:

12.1. The system can assign the document numbers or the user can assign
the number during document entry.
12.1. A business transaction creates only one document.
12.3. Document types are defined at company code level.
12.4. Number ranges for document numbers and account types defined for postings
are defined by the document types.
12.5. Document types also define whether invoices are posted with the net procedure.

Choose the correct option:

a) [ ] 12.1, 12.4 and 12.5 are correct.


b) [ ] 12.2, 12.4 and 12.5 are correct.
c) [ ] 12.3, 12.4 and 12.5 are correct.
d) [ ] 12.1, 12.3 and 12.4 are correct.
e) [ ] 12.1, 12.2 and 12.5 are correct.

13. What do the posting keys specify (Note: we can have more than one correct
sentence. Please select the sentences you think they are correct)?

a) [ ] Whether the line item is connected to a payment transaction or not.


b) [ ] Whether the posting is sales-relevant and the sales figure of the account is to be
updated by the transaction, for example, by the posting of a customer invoice.
c) [ ] Whether the line items contain ³credit´ or ³debit´ values.
d) [ ] Whether the line items are valid for a business transaction.
e) [ ] Whether the accounts are allowed for posting.

14. Consider the following statements:

14.1. A company code must be assigned to a posting period variant to have the control
for posting periods.
14.2.µ+¶ symbol represents all account types in the posting period customizing screen.
14.3. The account interval in the posting period customizing screen can be both G/L
and subledger accounts.
14.4. The maximum amounts are defined per company code in ³tolerance groups´.
14.5. It is not possible to assign tolerance groups to user logon ID¶s.
Choose the correct option:

a) [ ] 14.1, 14.4 and 14.5 are correct.


b) [ ] 14.2, 14.4 and 14.5 are correct.
c) [ ] 14.3, 14.4 and 14.5 are correct.
d) [ ] 14.1, 14.2 and 14.4 are correct.
e) [ ] 14.1, 14.2 and 14.5 are correct.

15. What fields of a FI Document Header section can be changed after a document has
already been posted (Note: we can have more than one correct sentence. Please select
the sentences you think they are correct)?

a) [ ] Fiscal Year.
b) [ ] Reference Number.
c) [ ] Text fields.
d) [ ] Header text.
e) [ ] Posting date.

16. About the change control, what conditions below are applicable (Note: we can
have more than one correct sentence. Please select the sentences you think they are
correct)?

16.1. The posting period is already closed.


16.2. The line item is not yet cleared.
16.3. The document is a credit memo for an invoice.
16.4. The document is not a credit memo from a down payment.
16.5. The line item is either a debit in a customer account or a credit in a vendor
account.

a) [ ] 16.1.
b) [ ] 16.2.
c) [ ] 16.3.
d) [ ] 16.4.
e) [ ] 16.5.

17. What are the prerequisites to enable negative postings (Note: we can have more
than one correct sentence. Please select the sentences you think they are correct)?

a) [ ] You have to define reversal reasons for negative reversal.


b) [ ] You have to ensure company code permits negative postings.
c) [ ] You have to define the document type that explicitly allows negative postings.
d) [ ] You have to use cleared items.
e) [ ] You have to reset cleared items.

18. What is the purpose of the terms of payment (Please choose the correct sentence)?

a) [ ] Calculate a cash discount and invoice due date.


b) [ ] Calculate the tax amounts.
c) [ ] Enable the cross-company code transactions.
d) [ ] Define the baseline date.
e) [ ] Calculate only the required conditions for SD invoices.

19. Consider the following statements:

19.1. Terms of payments are copied from invoice to credit memos when they are
linked to.
19.2. Inserting a ³V´ in the invoice reference field during document entry means
the terms of payment are activated in the
non-invoice-related credit memos.
19.3. The account type field in terms of payment basic data screen should be defined
separately, to prevent any done change in the term of payment.
19.4. The system cannot define the splitment of an installment payment, at least you
define it in the terms of payment.
19.5. The day limits define the dates of the cash discount periods.

Which of the statements above is false (Please choose the correct sentence)?

a) [ ] 19.1.
b) [ ] 19.2.
c) [ ] 19.3.
d) [ ] 19.4.
e) [ ] 19.5.

20. True or false?


20.1. SAP supports tax on sales and purchases, US sales tax, additional taxes and
withholding tax as tax systems for different countries.
a) [ ] True. b) [ ] False.
20.2. Only national level of taxation is allowed in the R/3 system.
a) [ ] True. b) [ ] False.
20.3. A tax calculation procedure is assigned to every company code for carrying out
tax calculations.
a) [ ] True. b) [ ] False.
20.4.A jurisdiction code is a combination of the codes of tax authorities that tax
movements of goods and use their own tax rates.
a) [ ] True. b) [ ] False.
20.5. If you desire to post manual tax postings, you have to flag the ³Post
Automatically Only´ field of the account master record.
a) [ ] True. b) [ ] False.

&Ñ6# 2#  6# %ŒÑ# 

These are some of the issue for which probable solutions are given, hope they are
helpful :

 
 3
Ñ $ 
 & B,&3ÿ (
*)  
Ñ 
 



&33Ñ



" 
  C3DBC3DB 
 
  5ÿ76+Ñÿ)

2

  -        
  
   C3DB 
      


  
  C3DB
 
  5ÿ76+Ñÿ)

  

Π 
   

(  )

  
"  *      
 
    
    
    
     
  
 

 
   

Solution :
* That¶s generic error for payment run, check whether there are any due items as on
date (tcode fbl1n). You can also change the baseline date there and rerun it. if you still
get same error.. Check the proposal log, you will find the reason.

* Try to see first whether any open items exist. By using FBL1N.

 
 ÿ
.*  
    
 ,  &033
)c   /

Solution :
For Down payments to be paid using APP we have create a Down Payment request F-
47.
 
 
c  
 , ,    
    (
     
     ,Ñ
 " 
   " " 

 
   

Solution :
This type of error comes when your Payment proposal doesn't have any items to
process. Check the parameters and ensure invoices are due as on run date.

 
 4 
c  
 
$ ?& 8: *!  
 
 

  ( 
" 

    
 
 (
(** 
)c 
!  

 
 
 ,     

Solution :
* Entry gets posted to Customer a/c through reconciliation account. You have to give
a GL a/c for revenue.

Your entry would be


Customer (Reconciliation a/c) Dr
To Revenue Cr

* Reconciliation is a fictious entry so you cannot consider as an entry to be entered by


the user. This rule is derived from the fact that 'we cannot enter/post directly to
RECON account'.

That is why system needs a GL account to make the account balance as zero. Manual
entry could be:

Customer a/c Dr
To Domestic Sales a/c
(Sales invoiced posted)

Recon entry is automatically made once you post this entry since you have configured
your RECON in the IMG.

 
 5 
Ñ  
(         !   
    
  
E       
, $  
  
  , 
    

    
F)
Solution :
You can attach the GL Accounts by just filling the details in the company code
segment of the GL A/c. Hence you can use that gl a/c for your co code.
But that would be individually creating the accounts. Right?? How about creating all
accounts at one shot. Create in FS00

 
 7 
2
(

 . 

. )

Solution :
Standard Hierarchy is basic structure of company but alternative hierarchy is just for
reporting or temporary usage.

 
 8
Ñ $     
 * ? 
 
 (
: 
 
   
   $)         
    * 
%         


    
 
 
 (

   ,  
 
 )

Solution :
Useful life is required for depreciation change. Normally a company with WDV
depreciation may want to write off its assets which have crossed their useful life in 2
or 3 installments. This is achieved by depreciation change, where after useful life, a
new method takes over.

 
 ^ 
Ñ $ 
  (


# )

Solution :
Internal order can only take a statistical posting & cost centre shall take a true posting
when the relevant internal order is defined as statistical I/O IN T. code
KO01(CONTROL DATA ) tab. So while making a posting in FB50 and assigning
both I/O & COST CENTRE as relevant cost object in the transaction you shall get the
stated status of these 2 cost object.

 
 9 
Ñ
(5,
  (,
Ñ *G  -G -   )
# 
   
?( :,))  
 
 *
     
 
) Ñ   
    ( 
    -  
  
Solution :
Even now you are not clear. T_Code FB50 is used for posting GL account only. I fail
to understand how you can calculate tax which is generally from purchase / vendor or
Sales / Customer oriented through FB50.

In case of local distribution, if we forget to pay taxes on certain items and we need to
pass tax entries, then such a case is needed. This can be achieved thru default
parameter id for that particular user through transaction code SU3.

In SU3, in Parameters Tab put "XTX" in Parameter ID column and in Parameter


Value column put "X".

 
 3 
c $
  (   
 -

$ 
 
-(
).  
 -(
Ñ 
-=6Œ6C
  
 )c    
 -(


$ 
  
Ñ 
)

Solution :
Kindly check this:
spro - financial accounting - f.a global setting - with holding setting - extended with
holding setting -- calculation -- with holding tax type .

Check your withholding tax type, go in it and check the setting.

Ñ 
Œ  &Ñ! 
Œ" 2
&

 


SPRO Enter IMG
OX02 Company Code - Create, Check, Delete
OX03 Create Business Area
OKBD Functional Areas
OB45 Create Credit Control Area
OB29 Maintain Fiscal Year Variant
OB37 Assign Co. Code to Fiscal Year Variant
OB13 Creation of Chart of Account (CoA)
OBY7 Copy Chart of Account (CoA)
OBY9 Transport Chart of Account
OBD4 Define Account Group
OBY2 Copy GL Accounts from the Chart to Co. Code
OB53 Define Retained Earnings
OB58 Maintain Financial Statement Versions
OBC4 Maintain Field Status Variant
OBBO Define Posting Period Variant
OBA7 Define Document Type & Number Ranges
OB41 Maintain Posting Keys
OBA4 Create Tolerance Groups
FBN1 Create GL Number Ranges
OBL1 Automatic Posting Documentation
FBKP Automatic Account Assignment
OBYC MM Automatic Account Assignment
OBY6 Enter Global Parameters
FS00 Creation of GL Master Records
(F-02) Posting of GL Transactions
(FB03) Display of GL Document
(FS10N) Display of GL Accounts
OB46 Define Interest Calculation Types
OBD3 Define Vendor Account Group
(XK01) Creation of Vendor Master
(F-43) Purchase Invoice Posting
(FK10N) Display Vendor Account
F112 Define House Bank
OBB8 Maintain Terms of Payment (ToP)
OBD2 Creation of Customer Account Group
OBA3 Customer Tolerance Groups
(XD01) Creation of Customer Master
(FD10N) Display Customer Account
(F-28) Incoming Payment Posting
OB61 Define Dunning Area
EC08 Copy Reference Chart of Depreciation (CoD)
OADB Define Depreciation Area
OAOB Assign Chart of Depreciation to Co. Code
OAOA Define Asset Class
AO90 Assignment of Account in Asset Class
OAY2 Determination of Depreciation Area in Asset Class
(AS01) Creation of Asset Master
(AS11) Creation of Sub Asset
(F-90) Asset Purchase Posting
(AFAB) Depreciation Run
(F-92) Asset Sale Posting
(AW01N) Asset Explorer

6- 
  
(
Ñ =#Ñ"6
 Ñ Ñ !
)
Both are same in SD point of view.
- In SD terminology we call as Billing Document and
- In FI terminology we call as INVOICE.
- In MM again only INVOICE will be there for Vendors.

Invoice is document indicating to delivery goods and Billing is a receipt of payment.

If we receive the goods from vendors that is called bill if we give the goods to
customer that is called invoice.

Bill means we have to pay the amount against bill invoice means we have to receive
the amount against invoice.

Invoice is for both : Vendor Invoice and Customer Invoice.


 Π 
- VF01 create billing document. The delivery order comes up auto.
- VF02 the billing doc comes up auto . View the accounting enteries

Ñ
$  Π 
- FB60 Create invoice with respect to rawmaterial and tax.
- FB70 Invoice entries with respect to sales and tax

&ь
 
"  3

.  $     



The following procedure is to be followed to reverse the cleared document.
1. Reset the cleared document and reverse the document.
Path # Accounting --> financial Accounting --> C/L --> Document--> Reset Cleared
items - T. code : FBRA
In this screen select resetting and reverse radio button and give the reversal reason. :
01 and save the settings.
*-- Maddipati

F-01 Enter Sample Document


F-02 Enter G/L Account Posting
F-03 Clear G/L Account
F-04 Post with Clearing
F-05 Post Foreign Currency Valuation
F-06 Post Incoming Payments
F-07 Post Outgoing Payments
F-18 Payment with Printout
F-19 Reverse Statistical Posting
F-20 Reverse Bill Liability
F-21 Enter Transfer Posting
F-22 Enter Customer Invoice
F-23 Return Bill of Exchange Pmt Request
F-25 Reverse Check/Bill of Exch.
F-26 Incoming Payments Fast Entry
F-27 Enter Customer Credit Memo
F-28 Post Incoming Payments
F-29 Post Customer Down Payment
F-30 Post with Clearing
F-31 Post Outgoing Payments
F-32 Clear Customer
F-33 Post Bill of Exchange Usage
F-34 Post Collection
F-35 Post Forfaiting
F-36 Bill of Exchange Payment
F-37 Customer Down Payment Request
F-38 Enter Statistical Posting
F-39 Clear Customer Down Payment
F-40 Bill of Exchange Payment
F-41 Enter Vendor Credit Memo
F-42 Enter Transfer Posting
F-43 Enter Vendor Invoice
F-44 Clear Vendor
F-46 Reverse Refinancing Acceptance
F-47 Down Payment Request
F-48 Post Vendor Down Payment
F-49 Customer Noted Item
F-51 Post with Clearing
F-52 Post Incoming Payments
F-53 Post Outgoing Payments
F-54 Clear Vendor Down Payment
F-55 Enter Statistical Posting
F-56 Reverse Statistical Posting
F-57 Vendor Noted Item
F-58 Payment with Printout
F-59 Payment Request
F-60 Maintain Table: Posting Periods
F-62 Maintain Table: Exchange Rates
F-63 Park Vendor Invoice
F-64 Park Customer Invoice
F-65 Preliminary Posting
F-66 Park Vendor Credit Memo
F-67 Park Customer Credit Memo
F-90 Acquisition from purchase w. vendor
F-91 Asset acquis. to clearing account
F-92 Asset Retire. frm Sale w/ Customer
F.01 ABAP/4 Report: Balance Sheet
F.02 Compact Journal
F.03 Reconciliation
F.04 G/L: Create Foreign Trade Report
F.05 Foreign Currency Val.: Open Items
F.06 Foreign Currency Valuation:G/L Assts
F.07 G/L: Balance Carried Forward
F.08 G/L: Account Balances
F.09 G/L: Account List
F.0A G/L: FTR Report on Disk
F.0B G/L: Create Z2 to Z4
F.10 G/L: Chart of Accounts
F.11 G/L: General Ledger from Doc.File
F.12 Advance Tax Return
F.13 ABAP/4 Report: Automatic Clearing
F.14 ABAP/4 Report: Recurring Entries
F.15 ABAP/4 Report: List Recurr.Entries
F.16 ABAP/4 Report: G/L Bal.Carried Fwd
F.17 ABAP/4 Report: Cust.Bal.Confirmation
F.18 ABAP/4 Report: Vend.Bal.Confirmation
F.19 G/L: Goods/Invoice Received Clearing
F.1A Customer/Vendor Statistics
F.1B Head Office and Branch Index
F.20 A/R: Account List
F.21 A/R: Open Items
F.22 A/R: Open Item Sorted List
F.23 A/R: Account Balances
F.24 A/R: Interest for Days Overdue
F.25 Bill of Exchange List
F.26 A/R: Balance Interest Calculation
F.27 A/R: Periodic Account Statements
F.28 Customers: Reset Credit Limit
F.29 A/R: Set Up Info System 1
F.2A Calc.cust.int.on arr.: Post (w/o OI)
F.2B Calc.cust.int.on arr.: Post(with OI)
F.2C Calc.cust.int.on arr.: w/o postings
F.2D Customrs: FI-SD mast.data comparison
F.2E Reconciliation Btwn Affiliated Comps
F.2F Management Acct Group Reconciliation
F.2G Create Account Group Reconcil. G/L
F.30 A/R: Evaluate Info System
F.31 Credit Management - Overview
F.32 Credit Management - Missing Data
F.33 Credit Management - Brief Overview
F.34 Credit Management - Mass Change
F.35 Credit Master Sheet
F.36 Adv.Ret.on Sls/Pur.Form Printout(DE)
F.37 Adv.rept.tx sls/purch.form print (BE
F.38 Transfer Posting of Deferred Tax
F.39 C FI Maint. table T042Z (BillExcTyp)
F.40 A/P: Account List
F.41 A/P: Open Items
F.42 A/P: Account Balances
F.44 A/P: Balance Interest Calculation
F.45 A/P: Set Up Info System 1
F.46 A/P: Evaluate Info System
F.47 Vendors: calc.of interest on arrears
F.48 Vendors: FI-MM mast.data comparison
F.4A Calc.vend.int.on arr.: Post (w/o OI)
F.4B Calc.vend.int.on arr.: Post(with OI)
F.4C Calc.vend.int.on arr.: w/o postings
F.50 G/L: Profitability Segment Adjustmnt
F.51 G/L: Open Items
F.52 G/L: Acct Bal.Interest Calculation
F.53 G/L: Account Assignment Manual
F.54 G/L: Structured Account Balances
F.56 Delete Recurring Document
F.57 G/L: Delete Sample Documents
F.58 OI Bal.Audit Trail: fr.Document File
F.59 Accum.Clas.Aud.Trail: Create Extract
F.5A Accum.Clas.Aud.Trail: Eval.Extract
F.5B Accum.OI Aud.Trail: Create Extract
F.5C Accum.OI Audit Trail: Display Extr.
F.5D G/L: Update Bal. Sheet Adjustment
F.5E G/L: Post Balance Sheet Adjustment
F.5F G/L: Balance Sheet Adjustment Log
F.5G G/L: Subseq.Adjustment(BA/PC) Sp.ErA
F.5I G/L: Adv.Rep.f.Tx on Sls/Purch.w.Jur
F.61 Correspondence: Print Requests
F.62 Correspondence: Print Int.Documents
F.63 Correspondence: Delete Requests
F.64 Correspondence: Maintain Requests
F.65 Correspondence: Print Letters (Cust)
F.66 Correspondence: Print Letters (Vend)
F.70 Bill/Exchange Pmnt Request Dunning
F.71 DME with Disk: B/Excha. Presentation
F.75 Extended Bill/Exchange Information
F.77 C FI Maintain Table T045D
F.78 C FI Maintain Table T045B
F.79 C FI Maintain Table T045G
F.80 Mass Reversal of Documents
F.81 Reverse Posting for Accr./Defer.Docs
F.90 C FI Maintain Table T045F
F.91 C FI Maintain Table T045L
F.92 C FI Maintain T012K (Bill/Exch.)
F.93 Maintain Bill Liability and Rem.Risk
F.97 General Ledger: Report Selection
F.98 Vendors: Report Selection
F.99 Customers: Report Selection
F/LA Create Pricing Report
F/LB Change pricing reports
F/LC Display pricing reports
F/LD Execute pricing reports
F00 SAPoffice: Short Message
F000 Accounting
F010 ABAP/4 Reporting: Fiscal Year Change
F01N Debit position RA single reversal
F01O Vacancy RU single reversal
F01P Accruals/deferrals single reversal
F01Q Debit position MC single reversal
F01R MC settlement single reversal
F01S Reverse Periodic Posting
F01T Reverse Acc./Def. General Contract
F040 Reorganization
F041 Bank Master Data Archiving
F042 G/L Accounts Archiving
F043 Customer Archiving
F044 Vendor Archiving
F045 Document Archiving
F046 Transaction Figures Archiving
F101 ABAP/4 Reporting: Balance Sheet Adj.
F103 ABAP/4 Reporting: Transfer Receivbls
F104 ABAP/4 Reporting: Receivbls Provisn
F107 FI Valuation Run
F110 Parameters for Automatic Payment
F111 Parameters for Payment of PRequest
F13E ABAP/4 Report: Automatic Clearing
F150 Dunning Run
F48A Document Archiving
F53A Archiving of G/L Accounts
F53V Management of G/L Account Archives
F56A Customer Archiving
F58A Archiving of Vendors
F61A Bank archiving
F64A Transaction Figure Archiving
F66A Archiving of Bank Data Storage
F8+0 Display FI Main Role Definition
F8+1 Maintain FI Main Role Definition
F8+2 Display FI Amount Groups
F8+3 Maintain FI Amount Groups
F8B4 C FI Maintain Table TBKDC
F8B6N C FI Maintain Table TBKPV
F8BC C FI Maintain Table TBKFK
F8BF C FI Maintain Table T042Y
F8BG Maintain Global Data for F111
F8BH Inconsistencies T042I and T042Y
F8BJ Maintain Clearing Accts (Rec.Bank)
F8BK Maintain ALE-Compatible Pmnt Methods
F8BM Maintain numb.range: Payment request
F8BN Corr.Acctg Documents Payment Block
F8BO Payment request archiving
F8BR Levels for Payment Requests
F8BS Detail display of payment requests
F8BT Display Payment Requests
F8BU Create payment runs automatically
F8BV Reversal of Bank-to-Bank Transfers
F8BW Reset Cleared Items: Payt Requests
F8BZ F111 Customizing
F8XX Payment Request No. Ranges KI3-F8BM
FA39 Call up report with report variant
FAKA Config.: Show Display Format
FAKP Config.: Maintain Display Format
FAR1 S FI-ARI Maint. table T061A
FARA S FI-ARI Maint. table T061P/Q
FARB C FI-ARI Maint. table T061R
FARI AR Interface: Third-party applicatns
FARY Table T061S
FARZ Table T061V
FAX1 BC sample SAP DE 2.1
FAX2 BC sample 2 SAP DE 2.1
FB00 Accounting Editing Options
FB01 Post Document
FB02 Change Document
FB03 Display Document
FB03Z Display Document/Payment Usage
FB04 Document Changes
FB05 Post with Clearing
FB05_OLD Post with clearing
FB07 Control Totals
FB08 Reverse Document
FB09 Change Line Items
FB10 Invoice/Credit Fast Entry
FB11 Post Held Document
FB12 Request from Correspondence
FB13 Release for Payments
FB1D Clear Customer
FB1K Clear Vendor
FB1S Clear G/L Account
FB21 Enter Statistical Posting
FB22 Reverse Statistical Posting
FB31 Enter Noted Item
FB41 Post Tax Payable
FB50 G/L Acct Pstg: Single Screen Trans.
FB60 Enter Incoming Invoices
FB65 Enter Incoming Credit Memos
FB70 Enter Outgoing Invoices
FB75 Enter Outgoing Credit Memos
FB99 Check if Documents can be Archived
FBA1 Customer Down Payment Request
FBA2 Post Customer Down Payment
FBA3 Clear Customer Down Payment
FBA6 Vendor Down Payment Request
FBA7 Post Vendor Down Payment
FBA7_OLD Post Vendor Down Payment
FBA8 Clear Vendor Down Payment
FBA8_OLD Clear Vendor Down Payment
FBB1 Post Foreign Currency Valn
FBBA Display Acct Determination Config.
FBBP Maintain Acct Determination Config.
FBCJ Cash Journal
FBCJC0 C FI Maintain Tables TCJ_C_JOURNALS
FBCJC1 Cash Journal Document Number Range
FBCJC2 C FI Maint. Tables TCJ_TRANSACTIONS
FBCJC3 C FI Maintain Tables TCJ_PRINT
FBCOPY Copy Function Module
FBD1 Enter Recurring Entry
FBD2 Change Recurring Entry
FBD3 Display Recurring Entry
FBD4 Display Recurring Entry Changes
FBD5 Realize Recurring Entry
FBD9 Enter Recurring Entry
FBDF Menu Banque de France
FBE1 Create Payment Advice
FBE2 Change Payment Advice
FBE3 Display Payment Advice
FBE6 Delete Payment Advice
FBE7 Add to Payment Advice Account
FBF1 C80 Reporting Minus Sp.G/L Ind.
FBF2 Financial Transactions
FBF3 Control Report
FBF4 Download Documents
FBF5 Reports Minus Vendor Accounts
FBF6 Document Changes
FBF7 C80 Reports Minus Sp.G/L Ind.
FBF8 C84 Reports
FBFT Customizing BDF
FBIPU Maintain bank chains for partner
FBKA Display Accounting Configuration
FBKF FBKP/Carry Out Function (Internal)
FBKP Maintain Accounting Configuration
FBL1 Display Vendor Line Items
FBL1N Vendor Line Items
FBL2 Change Vendor Line Items
FBL2N Vendor Line Items
FBL3 Display G/L Account Line Items
FBL3N G/L Account Line Items
FBL4 Change G/L Account Line Items
FBL4N G/L Account Line Items
FBL5 Display Customer Line Items
FBL5N Customer Line Items
FBL6 Change Customer Line Items
FBL6N Customer Line Items
FBM1 Enter Sample Document
FBM2 Change Sample Document
FBM3 Display Sample Document
FBM4 Display Sample Document Changes
FBMA Display Dunning Procedure
FBME Banks
FBMP Maintain Dunning Procedure
FBN1 Accounting Document Number Ranges
FBN2 Number Range Maintenance: FI_PYORD
FBP1 Enter Payment Request
FBR1 Post with Reference Document
FBR2 Post Document
FBRA Reset Cleared Items
FBRC Reset Cleared Items (Payment Cards)
FBS1 Enter Accrual/Deferral Doc.
FBTA Display Text Determin.Configuration
FBTP Maintain Text Determin.Configuration
FBU2 Change Intercompany Document
FBU3 Display Intercompany Document
FBU8 Reverse Cross-Company Code Document
FBV0 Post Parked Document
FBV1 Park Document
FBV2 Change Parked Document
FBV3 Display Parked Document
FBV4 Change Parked Document (Header)
FBV5 Document Changes of Parked Documents
FBV6 Parked Document $
FBVB Post Parked Document
FBW1 Enter Bill of Exchange Pmnt Request
FBW2 Post Bill of Exch.acc.to Pmt Request
FBW3 Post Bill of Exchange Usage
FBW4 Reverse Bill Liability
FBW5 Customer Check/Bill of Exchange
FBW6 Vendor Check/Bill of Exchange
FBW7 Bank file to file system (for FBWD)
FBW8 File to Bank (for Transaction FBWD)
FBW9 C FI Maintain Table T045DTA
FBWA C FI Maintain Table T046a
FBWD Returned Bills of Exchange Payable
FBWD2 Parameter Transaction for FBWD
FBWE Bill/Exch.Presentatn - International
FBWQ C FI Maintain Table T045T
FBWR C FI Maintain Table T045W
FBWS C FI Maintain Table T046s
FBZ0 Display/Edit Payment Proposal
FBZ1 Post Incoming Payments
FBZ2 Post Outgoing Payments
FBZ3 Incoming Payments Fast Entry
FBZ4 Payment with Printout
FBZ5 Print Check For Payment Document
FBZ8 Display Payment Run
FBZA Display Pmnt Program Configuration
FBZG Failed Customer Payments
FBZP Maintain Pmnt Program Configuration
FC10 Financial Statements Comparison
FC11 Data Extract for FI Transfer
FC80 Document C80
FC82 Document C82
FCAA Check Archiving
FCC1 Payment Cards: Settlement
FCC2 Payment Cards: Repeat Settlement
FCC3 Payment Cards: Delete Logs
FCC4 Payment Cards: Display Logs
FCCR Payment Card Evaluations
FCH1 Display Check Information
FCH2 Display Payment Document Checks
FCH3 Void Checks
FCH4 Renumber Checks
FCH5 Create Check Information
FCH6 Change Check Information/Cash Check
FCH7 Reprint Check
FCH8 Reverse Check Payment
FCH9 Void Issued Check
FCHA Check archiving
FCHB Check retrieval
FCHD Delete Payment Run Check Information
FCHE Delete Voided Checks
FCHF Delete Manual Checks
FCHG Delete cashing/extract data
FCHI Check Lots
FCHK Check Tracing Initial Menu
FCHN Check Register
FCHR Online Cashed Checks
FCHT Change check/payment allocation
FCHU Create Reference for Check
FCHV C FI Maintain Table TVOID
FCHX Check Extract - Creation
FCIWCU BW Customizing for CS
FCIWD00 Download InfoObject text
FCIWD10 Download InfoObject hierarchies
FCKR International cashed checks
FCMM C FI Preparations for consolidation
FCMN FI Initial Consolidation Menu
FCV1 Create A/R Summary
FCV2 Delete A/R Summary
FCV3 Early Warning List
FC_BW_BEX Business Explorer Analyser
FC_BW_RSA1 BW Administrator Workbench
FC_BW_RSZDELETE Delete BW Query Objects
FC_BW_RSZV Maintain BW Variables
FD-1 Number range maintenance: FVVD_RANL
FD01 Create Customer (Accounting)
FD02 Change Customer (Accounting)
FD02CORE Maintain customer
FD03 Display Customer (Accounting)
FD04 Customer Changes (Accounting)
FD05 Block Customer (Accounting)
FD06 Mark Customer for Deletion (Acctng)
FD08 Confirm Customer Individually(Actng)
FD09 Confirm Customer List (Accounting)
FD10 Customer Account Balance
FD10N Customer Balance Display
FD10NA Customer Bal. Display with Worklist
FD11 Customer Account Analysis
FD15 Transfer customer changes: send
FD16 Transfer customer changes: receive
FD24 Credit Limit Changes
FD32 Change Customer Credit Management
FD33 Display Customer Credit Management
FD37 Credit Management Mass Change
FDCU Loans customizing menu
FDFD Cash Management Implementation Tool
FDI0 Execute Report
FDI1 Create Report
FDI2 Change Report
FDI3 Display Report
FDI4 Create Form
FDI5 Change Form
FDI6 Display Form
FDIB Background Processing
FDIC Maintain Currency Translation Type
FDIK Maintain Key Figures
FDIM Report Monitor
FDIO Transport Reports
FDIP Transport Forms
FDIQ Import Reports from Client 000
FDIR Import Forms from Client 000
FDIT Translation Tool - Drilldown Report
FDIV Maintain Global Variable
FDIX Reorganize Drilldown Reports
FDIY Reorganize Report Data
FDIZ Reorganize Forms
FDK43 Credit Management - Master Data List
FDMN
FDOO Borrower's notes order overview
FDTA TemSe/REGUT Data Administration
FDTT Treasury Data Medium Administration
FEBA Postprocess Electronic Bank Statmt
FEBC Generate Multicash format
FEBMSG Display Internet Messages
FEBOAS Request Account Statement via OFX
FEBOFX OFX Functions
FEBP Post Electronic Bank Statement
FEBSTS Search String Search Simulation
FESR Importing of POR File (Switzerland)
FEUB Adjust VIBEPP after EURO conversion
FEUI Real Estate Implementation Guide
FF$3 Send planning data to central system
FF$4 Retrieve planning data
FF$5 Retrieve transmission results
FF$6 Check settings
FF$7 Check all external systems
FF$A Maintain TR-CM subsystems
FF$B Convert Planning Group
FF$C Convert planning level
FF$D Convert business areas
FF$L Display transmission information
FF$S Display transmission information
FF$X Configure the central TR-CM system
FF-1 Outstanding Checks
FF-2 Outstanding Bills of Exchange
FF-3 Cash Management Summary Records
FF-4 CMF Data In Accounting Documents
FF-5 CMF Records fr.Materials Management
FF-6 CMF Records from Sales
FF-7 Forecast Item Journal
FF-8 Payment Advice Journal
FF-9 Journal
FF.1 Standard G/L Account Interest Scale
FF.3 G/L Account Cashed Checks
FF.4 Vendor Cashed Checks
FF.5 Import Electronic Bank Statement
FF.6 Display Electronic Bank Statement
FF.7 Payment Advice Comparison
FF.8 Print Payment Orders
FF.9 Post Payment Orders
FF.D Generate payt req. from advices
FF/1 Compare Bank Terms
FF/2 Compare value date
FF/3 Archive advices from bank statements
FF/4 Import electronic check deposit list
FF/5 Post electronic check deposit list
FF/6 Deposit/loan mgmt analysis/posting
FF/7 Deposit/loan management int accruals
FF/8 Import Bank Statement into Cash Mgmt
FF/9 Compare Advices with Bank Statement
FF63 Create Planning Memo Record
FF65 List of Cash Management Memo Records
FF67 Manual Bank Statement
FF68 Manual Check Deposit Transaction
FF6A Edit Cash Mgmt Pos Payment Advices
FF6B Edit liquidity forecast planned item
FF70 Cash Mgmt Posit./Liquidity Forecast
FF71 Cash Position
FF72 Liquidity forecast
FF73 Cash Concentration
FF74 Use Program to Access Cash Concntn
FF7A Cash Position
FF7B Liquidity forecast
FF:1 Maintain exchange rates
FFB4 Import electronic check deposit list
FFB5 Post electronic check deposit list
FFL_OLD Display Transmission Information
FFS_OLD Display Transmission Information
FFTL Telephone list
FFW1 Wire Authorization
FFWR Post Payment Requests from Advice
FFWR_REQUESTS Create Payment Requests from Advice
FF_1 Standard G/L Account Interest Scale
FF_3 G/L Account Cashed Checks
FF_4 Vendor Cashed Checks
FF_5 Import Electronic Bank Statement
FF_6 Display Electronic Bank Statement

&ь
 
"  ÿ

FG99 Flexible G/L: Report Selection


FGI0 Execute Report
FGI1 Create Report
FGI2 Change Report
FGI3 Display Report
FGI4 Create Form
FGI5 Change Form
FGI6 Display Form
FGIB Background Processing
FGIC Maintain Currency Translation Type
FGIK Maintain Key Figures
FGIM Report Monitor
FGIO Transport Reports
FGIP Transport Forms
FGIQ Import Reports from Client 000
FGIR Import Forms from Client 000
FGIT Translation Tool - Drilldown Report.
FGIV Maintain Global Variable
FGIX Reorganize Drilldown Reports
FGIY Reorganize Report Data
FGIZ Reorganize Forms
FGM0 Special Purpose Ledger Menu
FGRP Report Painter
FGRW Report Writer Menu
FI01 Create Bank
FI02 Change Bank
FI03 Display Bank
FI04 Display Bank Changes
FI06 Mark Bank for Deletion
FI07 Change Current Number Range Number
FI12 Change House Banks/Bank Accounts
FI12CORE Change House Banks/Bank Accounts
FI13 Display House Banks/Bank Accounts
FIBB Bank chain determination
FIBC Scenarios for Bank Chain Determin.
FIBD Allocation client
FIBF Maintenance transaction BTE
FIBHS Display bank chains for house banks
FIBHU Maintain bank chains for house banks
FIBL1 Control Origin Indicator
FIBL2 Assign Origin
FIBL3 Group of House Bank Accounts
FIBPS Display bank chians for partners
FIBPU Maintain bank chains for partner
FIBTS Dis. bank chains for acct carry over
FIBTU Main. bank chains for acctCarry over
FIHC Create Inhouse Cash Center
FILAUF_WF_CUST Store Order: Workflow Customizing
FILE Cross-Client File Names/Paths
FILINV_WF_CUST Store Inventory:Workflow Customizing
FINA Branch to Financial Accounting
FINF Info System Events
FINP Info System Processes
FITP_RESPO Contact Partner Responsibilities
FITP_SETTINGS Settings for Travel Planning
FITP_SETTINGS_TREE Tree Maintenance Current Settings
FITVFELD Tree
FJA1 Inflation Adjustment of G/L Accounts
FJA2 Reset Transaction Data G/L Acc.Infl.
FJA3 Balance Sheet/P&L with Inflation
FJA4 Infl. Adjustment of Open Items (FC)
FJA5 Infl. Adj. of Open Receivables (LC)
FJA6 Infl. Adj. of Open Payables (LC)
FJEE Exercise Subscription Right
FK01 Create Vendor (Accounting)
FK02 Change Vendor (Accounting)
FK02CORE Maintain vendor
FK03 Display Vendor (Accounting)
FK04 Vendor Changes (Accounting)
FK05 Block Vendor (Accounting)
FK06 Mark Vendor for Deletion (Acctng)
FK08 Confirm Vendor Individually (Acctng)
FK09 Confirm Vendor List (Accounting)
FK10 Vendor Account Balance
FK10N Vendor Balance Display
FK10NA Vendor Balance Display
FK15 Transfer vendor changes: receive
FK16 Transfer vendor changes: receive
FKI0 Execute Report
FKI1 Create Report
FKI2 Change Report
FKI3 Display Report
FKI4 Create Form
FKI5 Change Form
FKI6 Display Form
FKIB Background Processing
FKIC Maintain Currency Translation Type
FKIK Maintain Key Figures
FKIM Report Monitor
FKIO Transport Reports
FKIP Transport Forms
FKIQ Import Reports from Client 000
FKIR Import Forms from Client 000
FKIT Translation Tool - Drilldown Report.
FKIV Maintain Global Variable
FKIX Reorganize Drilldown Reports
FKIY Reorganize Report Data
FKIZ Reorganize Forms
FKMN
FKMT FI Acct Assignment Model Management
FLB1 Postprocessing Lockbox Data
FLB2 Import Lockbox File
FLBP Post Lockbox Data
FLCV Create/Edit Document Template WF
FM+0 Display FM Main Role Definition
FM+1 Maintain FM Main Role Definition
FM+2 Display FM Amount Groups
FM+3 Maintain FM Amount Groups
FM+4 Display FM Budget Line Groups
FM+5 Maintain FM Budget Line Groups
FM+6 Display FM Document Classes
FM+7 Maintain FM Document Classes
FM+8 Display FM Activity Categories
FM+9 Maintain FM Activity Categories
FM+A Display Doc.Class->Doc.Cat. Assgmt
FM+B Maintain Doc.Clase->Doc.Cat.Assgmt
FM03 Display FM Document
FM21 Change Original Budget
FM22 Display Original Budget
FM25 Change Supplement
FM26 Display Supplement
FM27 Change Return
FM28 Transfer Budget
FM29 Display Return
FM2D Display Funds Center Hierarchy
FM2E Change Budget Document
FM2F Display Budget Document
FM2G Funds Center Hierarchy
FM2H Maintain Funds Center Hierarchy
FM2I Create Funds Center
FM2S Display Funds Center
FM2T Change Releases
FM2U Change Funds Center
FM2V Display Releases
FM3D Display Commitment Item Hierarchy
FM3G Commitment Item Hierarchy
FM3H Maintain Commitment Item Hierarchy
FM3I Create Commitment Item
FM3N Commitment Items for G/L Accounts
FM3S Display Commitment Item
FM3U Change Commitment Item
FM48 Change Financial Budget: Initial Scn
FM48_1 PS-CM: Create Planning Layout
FM48_2 PS-CM: Change Planning Layout
FM48_3 PS-CM: Display Planning Layout
FM49 Display Financial Budget: Init.Scrn
FM4G Budget Structure Element Hierarchy
FM5I Create Fund
FM5S Display Fund
FM5U Change Fund
FM5_DEL Delete fund preselection
FM5_DISP Display fund preselection
FM5_SEL Preselection Fund
FM6I Create Application of Funds
FM6S Display Application of Funds
FM6U Change Application of Funds
FM71 Maintain Cover Pools
FM72 Assign FM Acct Asst to Cover Pool
FM78 Charact.Groups for Cover Pools
FM79 Grouping Chars for Cover Pool
FM7A Display Cover Eligibility Rules
FM7I Create Attributes for FM Acct Asst
FM7P Maintain Cover Eligibility Rules
FM7S Display Cover Eligibility Rules
FM7U Maintain Cover Eligibility Rules
FM9B Copy Budget Version
FM9C Plan Data Transfer from CO
FM9D Lock Budget Version
FM9E Unlock Budget Version
FM9F Delete Budget Version
FM9G Roll Up Supplement
FM9H Roll up Original Budget
FM9I Roll Up Return
FM9J Roll Up Releases
FM9K Change Budget Structure
FM9L Display Budget Structure
FM9M Delete Budget Structure
FM9N Generate Budget Object
FM9P Reconstruct Budget Distrbtd Values
FM9Q Total Up Budget
FM9W Adjust Funds Management Budget
FMA1 Matching: Totals and Balances (CBM)
FMA2 Matching: CBM Line Items and Totals
FMA3 Matching: FI Line Items (CBM)
FMA4 Matching: FI Bank Line Items (CBM)
FMAA Matching: Line Items and Totals (FM)
FMAB Matching: FI FM Line Items
FMAC Leveling: FM Commitment Line Items
FMAD Leveling: FI-FM Totals Records
FMAE Display Change Documents
FMAF Level Line Items and Totals Items
FMB0 CO Document Transfer
FMB1 Display Security Prices-Collect.
FMBI Use Revenues to Increase Expend.Bdgt
FMBUD005 FIFM Budget Data Export
FMBUD006 FIFM Budget Data Import
FMBV Activate Availability Control
FMC2 Customizing in Day-to-Day Business
FMCB Reassignment: Document Selection
FMCC Reassignment: FM-CO Assignment
FMCD Reassignment: Delete Work List
FMCG Reassignment: Overall Assignment
FMCN Reassignment: Supplement.Acct Assgt
FMCR Reassignment: Display Work List
FMCT Reassignment: Transfer
FMD1 Change Carryforward Rules
FMD2 Display Carryforward Rules
FMDM Monitor Closing Operations
FMDS Copy Carryforward Rules
FMDT Display Carryforward Rules
FME1 Import Forms from Client 000
FME2 Import Reports from Client 000
FME3 Transport Forms
FME4 Transport Reports
FME5 Reorganize Forms
FME6 Reorganize Drilldown Reports
FME7 Reorganize Report Data
FME8 Maintain Batch Variants
FME9 Translation Tool - Drilldown
FMEB Structure Report Backgrnd Processing
FMEH SAP-EIS: Hierarchy Maintenance
FMEK FMCA: Create Drilldown Report
FMEL FMCA: Change Drilldown Report
FMEM FMCA: Display Drilldown Report
FMEN FMCA: Create Form
FMEO FMCA: Change Form
FMEP FMCA: Display Form
FMEQ FMCA: Run Drilldown Report
FMER FMCA: Drilldown Tool Test Monitor
FMEURO1 Create Euro FM Area
FMEURO2 Refresh Euro Master Data
FMEURO3 Display Euro FM Areas
FMEURO4 Deactivate Euro FM Areas
FMEV Maintain Global Variable
FMF0 Payment Selection
FMF1 Revenue Transfer
FMG1 FM: Create Commitment Item Group
FMG2 FM: Change Commitment Item Group
FMG3 FM: Display Commitment Item Group
FMG4 FM: Delete Commitment Item Group
FMG5 Generate BS Objects fr.Cmmt Item Grp
FMHC Check Bdgt Structure Elements in HR
FMHG Generate Bdgt Struc Elements in HR
FMHGG Generate BS Elements f. Several Fnds
FMHH Master Data Check
FMHIST Apportion Document in FM
FMHV Budget Memo Texts
FMIA Display Rules for Revs.Incr.Budget
FMIB Increase Budget by Revenues
FMIC Generate Additional Budget Incr.Data
FMIL Delete Rules for Revs Incr. Budget
FMIP Maintain Rules for Revs.Incr.Budget
FMIS Display Rules for Revs.Incr.Budget
FMIU Maintain Rules for Revs.Incr.Budget
FMJ1 Fiscal Year Close: Select Commitment
FMJ1_TR Settlement: Select Commitment
FMJ2 Fiscal Year Close: Carr.Fwd Commts
FMJ2_TR Settlement: Transfer Commitment
FMJ3 Reverse Commitments Carryforward
FMJA Budget Fiscal Year Close: Prepare
FMJA_TR Budget Settlement: Prepare
FMJB Determine Budget Year-End Closing
FMJB_TR Budget Settlement: Determine
FMJC Budget Fiscal-Year Close: Carry Fwd
FMJC_TR Budget Settlement: Transfer
FMJD Reverse Fiscal Year Close: Budget
FMLD Ledger Deletion
FMLF Classify Movement Types
FMN0 Subsequent Posting of FI Documents
FMN1 Subsequent Posting of MM Documents
FMN2 Subsequent Posting of Billing Docs
FMN3 Transfer Purchase Req. Documents
FMN4 Transfer Purchase Order Documents
FMN5 Transfer Funds Reservation Documents
FMN8 Simulation Lists Debit Position
FMN8_OLD Simulation Lists Debit Position
FMN9 Posted Debit Position List
FMN9_OLD Posted Debit Position List
FMNA Display CBA Rules
FMNP Maintain CBA Rules
FMNR Assign SN-BUSTL to CBA
FMNS Display CBA Rules
FMNU Maintain CBA Rules
FMP0 Maintain Financial Budget
FMP1 Display Financial Budget
FMP2 Delete Financial Budget Version
FMR0 Reconstruct Parked Documents
FMR1 Actual/Commitment Report
FMR2 Actual/Commitment per Company Code
FMR3 Plan/Actual/Commitment Report
FMR4 Plan/Commitment Report w.Hierarchy
FMR5A 12 Period Forecast: Actual and Plan
FMR6A Three Period Display: Plan/Actual
FMRA Access Report Tree
FMRB Access Report Tree
FMRE_ARCH Archive Earmarked Funds
FMRE_EWU01 Earmarked Funds: Euro Preprocessing
FMRE_EWU02 Earmarked Funds: Euro Postprocessing
FMRE_SERLK Close Earmarked Funds
FMRP18 Clear Subsequent Postings
FMSS Display Status Assignment
FMSU Change Assigned Status
FMU0 Display Funds Reservation Doc.Types
FMU1 Maintain Funds Reservation Doc.Types
FMU2 Display Funds Reservtn Fld Variants
FMU3 Maintain Funds Resvtn Field Variants
FMU4 Display Funds Reservation Fld Groups
FMU5 Maintain Funds Reservatn Fld Groups
FMU6 Display Funds Reservtn Field Selctn
FMU7 Maintain Funds Resvtn Field Selctn
FMU8 Display Template Type for Fds Resvtn
FMU9 Maintain Template Type for Fds Resvn
FMUA Dispay Fds Res.Template Type Fields
FMUB Maintain Fds Res.Template Type Flds
FMUC Display Funds Res. Reference Type
FMUD Maintain Funds Res.Reference Type
FMUE Display Funds Res.Ref.Type Fields
FMUF Maintaine Fds Rsvtn Ref.Type Fields
FMUG Display Reasons for Decision
FMUH Maintain Reasons for Decisions
FMUI Display Groups for Workflow Fields
FMUJ Maintain Groups for Workflow Fields
FMUK Display Fields in Groups for WF
FMUL Maintain Fields in Groups for WF
FMUM Display Field Selctn ->Variant/Group
FMUN Display Field Seln->Variant/Group
FMUV Funds Resvtn Field Status Var.Asst
FMV1 Create Forecast of Revenue
FMV2 Change Forecast of Revenue
FMV3 Display Forecast of Revenue
FMV4 Approve Forecast of Revenue
FMV5 Change FM Acct Asst in Fcst of Rev.
FMV6 Reduce Forecast of Revenue Manually
FMVI Create Summarization Item
FMVO Fund Balance Carryforward
FMVS Display Summarization Item
FMVT Carry Forward Fund Balance
FMVU Change Summarization Item
FMW1 Create Funds Blocking
FMW2 Change Funds Blocking
FMW3 Display Funds Blocking
FMW4 Approve Funds Blocking
FMW5 Change FM Acct Asst in Funds Blkg
FMWA Create Funds Transfer
FMWAZ Payment Transfer
FMWB Change Funds Transfer
FMWC Display Funds Transfer
FMWD Approve Funds Transfer
FMWE Change FM Acct Asst in Funds Trsfr
FMX1 Create Funds Reservation
FMX2 Change Funds Reservation
FMX3 Display Funds Reservation
FMX4 Approve Funds Reservation
FMX5 Change FM Acct Asst in Funds Resvn
FMX6 Funds Reservation: Manual Reduction
FMY1 Create Funds Commitment
FMY2 Change Funds Commitment
FMY3 Display Funds Precommitment
FMY4 Approve Funds Precommitment
FMY5 Change FM Acct Asst in Funds Prcmmt
FMY6 Reduce Funds Precommitment Manually
FMZ1 Create Funds Commitment
FMZ2 Change Funds Commitment
FMZ3 Display Funds Commitment
FMZ4 Approve Funds Commitment
FMZ5 Change FM Acct Asst in Funds Commt
FMZ6 Reduce Funds Commitment Manually
FMZBVT Carry Forward Balance
FMZZ Revalue Funds Commitments
FM_DL07 Delete Worklist
FM_DLFI Deletes FI Documnts Transferred from
FM_DLFM Deletes all FM Data (fast)
FM_DLOI Deletes Cmmts Transferred from FM
FM_EURO_M Parameter maintenance for euro conv.
FM_RC06 Reconcile FI Paymts-> FM Totals Itms
FM_RC07 Reconcile FI Paymts-> FM Line Items
FM_RC08 Reconcile FM Paymts -> FM Line Items
FM_RC11 Select Old Payments
FM_S123 GR/IR: Post OIs to FM Again
FM_S201 Post Payments on Account to FIFM
FM_SD07 Display Worklist
FN-1 No.range: FVVD_RANL (Loan number)
FN-4 Number range maintenance: FVVD_PNNR
FN-5 Number range maintenance: FVVD_SNBNR
FN-6 Number range maintenance: FVVD_RPNR
FN09 Create Borrower's Note Order
FN11 Change borrower's note order
FN12 Display borrower's note order
FN13 Delete borrower's note order
FN15 Create borrower's note contract
FN16 Change borrower's note contract
FN17 Display borrower's note contract
FN18 Payoff borrower's note contract
FN19 Reverse borrower's note contract
FN1A Create other loan contract
FN1V Create other loan contract
FN20 Create borrower's note offer
FN21 Change borrower's note offer
FN22 Display borrower's note offer
FN23 Delete borrower's note offer
FN24 Activate borrower's note offer
FN2A Change other loan application
FN2V Change other loan contract
FN30 Create policy interested party
FN31 Change policy interested party
FN32 Display policy interested party
FN33 Delete policy interested party
FN34 Policy interested party in applic.
FN35 Policy interested party in contract
FN37 Loan Reversal Chain
FN3A Display other loan application
FN3V Display other loan contract
FN40 Create other loan interested party
FN41 Change other loan interested party
FN42 Display other loan interested party
FN43 Delete other loan interested party
FN44 Other loan interest.party in applic.
FN45 Other loan interested prty in cntrct
FN4A Delete other loan application
FN4V Delete other loan contract
FN5A Other loan application in contract
FN5V Payoff other loan contract
FN61 Create collateral value
FN62 Change collateral value
FN63 Display collateral value
FN70 List 25
FN72 List 54
FN80 Enter manual debit position
FN81 Change manual debit position
FN82 Display manual debit position
FN83 Create waiver
FN84 Change waiver
FN85 Display waiver
FN86 Enter debit position depreciation
FN87 Change debit position depreciation
FN88 Display debit position depreciation
FN8A Manual Entry: Unsched. Repayment
FN8B Manual Entry: Other Bus. Operations
FN8C Manual Entry: Charges
FN8D Post Planned Records
FNA0 Policy application in contract
FNA1 Create mortgage application
FNA2 Change mortgage application
FNA3 Display mortgage application
FNA4 Complete mortgage application
FNA5 Mortgage application in contract
FNA6 Create policy application
FNA7 Change policy application
FNA8 Display policy application
FNA9 Delete policy application
FNAA Reactivate deleted mortgage applic.
FNAB Reactivate deleted mortg. int.party
FNAC Reactivate deleted mortgage contract
FNAD Reactivate deleted policy applicat.
FNAE Reactivate deleted policy contract
FNAG Reactivate deleted other loan applic
FNAH Reactivate del. other loan int.party
FNAI Reactivate deleted other loan cntrct
FNAK Select file character
FNAL Reactivate deleted BNL contract
FNAM Reactivate deleted policy contract
FNASL Loans: Account Analysis
FNB1 Transfer to a Loan
FNB2 Transfer from a Loan
FNB3 Document Reversal - Loans
FNB8 BAV Information
FNB9 BAV transfer
FNBD Loans-Automatic bal.sheet transfer
FNBG Guarantee charges list
FNBU DARWIN- Loans accounting menu
FNCD Transfer Customizing for Dunning
FNCW1 Maintain Standard Role
FNCW2 Transaction Release: Adjust Workflow
FNDD Convert Dunning Data in Dunn.History
FNEN Create Loan
FNENALG Create General Loan
FNENHYP Create Mortgage Loan
FNENPOL Create Policy Loan
FNENSSD Create Borrower's Note Loan
FNF1 Rollover: Create file
FNF2 Rollover: Change file
FNF3 Rollover: Display file
FNF4 Rollover: Fill file
FNF9 Rollover: Evaluations
FNFO ISIS: Create file
FNFP ISIS: Change file
FNFQ ISIS: Display file
FNFR ISIS: Fill file
FNFT Rollover: File evaluation
FNFU Rollover: Update file
FNG2 Total Loan Commitment
FNG3 Total Commitment
FNI0
FNI1 Create mortgage application
FNI2 Change mortgage application
FNI3 Display mortgage application
FNI4 Delete mortgage application
FNI5 Mortgage application to offer
FNI6 Mortgage application in contract
FNIA Create interested party
FNIB Change interested party
FNIC Display interested party
FNID Delete interested party
FNIE Reactivate interested party
FNIH Decision-making
FNIJ Create credit standing
FNIK Change credit standing
FNIL Display credit standing
FNIN Create collateral value
FNIO Change collateral value
FNIP Display collateral value
FNK0 Multimillion Loan Display (GBA14)
FNK1 Loans to Managers (GBA15)
FNKO Cond.types - Cond.groups allocation
FNL1 Rollover: Create Main File
FNL2 Rollover: Change Main File
FNL3 Rollover: Displ. Main File Structure
FNL4 New business
FNL5 New business
FNL6 New business
FNM1 Automatic Posting
FNM1S Automatic Posting - Single
FNM2 Balance sheet transfer
FNM3 Loans reversal module
FNM4 Undisclosed assignment
FNM5 Automatic debit position simulation
FNM6 Post dunning charges/int.on arrears
FNM7 Loan reversal chain
FNMA Partner data: Settings menu
FNMD Submenu General Loans
FNME Loans management menu
FNMEC Loans Management Menu
FNMH Loans management menu
FNMI Loans information system
FNMO Loans Menu Policy Loans
FNMP Rollover
FNMS Loans Menu Borrower's Notes
FNN4 Display general file
FNN5 Edit general file
FNN6 Display general main file
FNN7 Edit general main file
FNN8 Display general main file
FNN9 Edit general overall file
FNO1 Create Object
FNO2 Change Object
FNO3 Display Object
FNO5 Create collateral
FNO6 Change collateral
FNO7 Display collateral
FNO8 Create Objects from File
FNO9 Create Collateral from File
FNP0 Edit rollover manually
FNP4 Rollover: Display file
FNP5 Rollover: Edit File
FNP6 Rollover: Display main file
FNP7 Rollover: Edit main file
FNP8 Rollover: Display overall file
FNP9 Rollover: Edit overall file
FNQ2 New Business Statistics
FNQ3 Postprocessing IP rejection
FNQ4 Customer Inc. Payment Postprocessing
FNQ5 Transact.type - Acct determinat.adj.
FNQ6 Compare Flow Type/Account Determin.
FNQ7 Generate flow type
FNQ8 Automatic Clearing for Overpayments
FNQ9 Int. adjustment run
FNQF Swiss interest adjustment run
FNQG Swiss special interest run
FNR0 Loans: Posting Journal
FNR6 Insur.prtfolio trends - NEW
FNR7 Totals and Balance List
FNR8 Account statement
FNR9 Planning list
FNRA Other accruals/deferrals
FNRB Memo record update
FNRC Accruals/deferrals reset
FNRD Display incoming payments
FNRE Reverse incoming payments
FNRI Portfolio Analysis Discount/Premium
FNRS Reversal Accrual/Deferral
FNS1 Collateral number range
FNS4 Cust. list parameters for loan order
FNS6 Installation parameter lists
FNS7 Loan Portfolio Trend Customizing
FNSA Foreign currency valuation
FNSB Master data summary
FNSL Balance reconciliation list
FNT0 Loan correspondence (Switzerland)
FNT1 Autom. deadline monitoring
FNT2 Copy text modules to client
FNUB Treasury transfer
FNV0 Payoff policy contract
FNV1 Create mortgage contract
FNV2 Change mortgage contract
FNV3 Display mortgage contract
FNV4 Delete mortgage contract
FNV5 Payoff mortgage contract
FNV6 Create policy contract
FNV7 Change policy contract
FNV8 Display policy contract
FNV9 Delete policy contract
FNVA Create paid off contracts
FNVCOMPRESSION Loans: Document Data Summarization
FNVD Disburse Contract
FNVI Loans: General Overview
FNVM Change Contract
FNVR Reactivate Contract
FNVS Display Contract
FNVW Waive Contract
FNWF WF Loans Release: List of Work Items
FNWF_REP Release Workflow: Synchronization
FNWO Loans: Fast Processing
FNWS Housing statistics
FNX1 Rollover: Create Table
FNX2 Rollover: Change Table
FNX3 Rollover: Display Table
FNX6 Rollover: Delete Table
FNX7 Rollover: Deactivate Table
FNX8 Rollover: Print Table
FNXD TR-EDT: Documentation
FNXG List of Bus. Partners Transferred
FNXU List of Imported Loans
FNY1 New Business: Create Table
FNY2 New Business: Change Table
FNY3 New Business: Display Table
FNY6 New Business: Delete Table
FNY7 New Business: Deactivate Table
FNY8 New Business: Print Table
FNZ0 Rejections report
FNZ1 Postprocessing payment transactions
FNZA Account Determination Customizing
FN_1 Table maint. transferred loans
FN_2 Table maintenance transf. partner
FN_UPD_FELDAUSW Update Program for Field Selection

% Π 


&

 


GENERAL LEDGER

Information Systems

1. Structured Account Balances (Balance Sheet & P&L Account in FS Version


Format)

S_ALR_87012279
2. GL Account Balances (Totals & Balances ) S_ALR_87012301
3. GL Line Items S_ALR_87012282
4. Statements for GL Accounts, Customers & Vendors S_ALR_87012332
5. Document Journal S_ALR_87012287
6. Compact Document Journal S_ALR_87012289
7. Line Item Journal S_ALR_87012291
8. Display of Changed Documents S_ALR_87012293
9. Invoice Numbers assigned Twice S_ALR_87012341
10. Gaps in Document Number Assignments S_ALR_87012342
11. Posting Totals Document Type wise S_ALR_87012344
12. Recurring Entry Documents S_ALR_87012346

Master Data

13. Chart of Accounts S_AL:R_87012326


14. GL Account List S_AL:R_87012328
15. Display Changes to GL Accounts S_ALR_87012308
16. Financial Statement Version FSE2
CASH & BANK REPORTS

1. Check Information List FCH6


2. Check Register FCHN
3. Check Number Ranges S_P99_41000102

TAX REPORTS & REGISTERS

1. List of Internally generated Excise Invoices J1I7

2. Capital Goods Transfer of Credit J2I8


3. List of GRs without Excise Invoice J1IGR

4. List of SubContract Challans J1IFR

5. CENVAT Register J2I9


(Monthly Return under Rule 57AE of the Central excise Rules from
which Monthly Return under Rule 7 of the CENVAT Credit Rules 2001)

6. Registers : RG 23A/C Part I &II , RG1, PLA J1I5,J2I5,J2I6


ACCOUNTS RECEIVABLE

Information Systems

1. Bill Holdings (Bill of Exchange Receivable List with ALV facility)


S-ALR_87009987
2. Customer Balances in Local Currency S_ALR_87012172
3. Customer Line Items S_ALR_87012197
4. Due Dates Analysis for Open Items S_ALR_87012168
5. List of Customer Open Items S_ALR_87012173
6. Customer Evaluation with Open Item Sorted List S_ALR_87012176
7. Customer Payment History S_ALR_87012177
8. Customer Open Item Analysis (Overdue Items Balance) S_ALR_87012178
9. List of Customer Cleared Line Items S_ALR_87012198
10.List of Down Payments open at key date S_ALR_87012199
11. Debit & Credit Notes Register ± Monthly S_ALR_87012287
12. Customer wise Sales S_ALR_87012186

ACCOUNTS PAYABLE
(Note : Similar Reports available for A/R are available for A/P also)

1. Vendor Balances S_ALR_87012082


2. Vendor Debit/Credit Memo Register S_ALR_87012287
Ñ    
+ , $
 

,
 , 

  , ?$ 
($
:)Ñ 
 * 
 G
  (
   
$
 )

Go to this menu:
Financial Accounting -> Accounts Payable -> Information System -> Reports for AP
accounting -> Master Data.

. c  
Œ-
 =
 )c  Œ0
"    

You can get the withholding tax report for vendor by using these t.codes:
S_P00_07000134 - Generic Withholding Tax Reporting
S_PL0_09000447 - Withholding tax report for the vendor

c    
  $((  * 
 (

Go to SAP Easy Access main menu.


Go To Accounting -> FI Acc -> customer(receivables) -> information system ->
reports .
Here you can get all the standard reports for receivables.

Π&


"
Π 

1. Maintain Financial Statement Versions

IMG -> Financial Accounting -> General Ledger Accounting -> Business
Transactions -> Closing -> Documenting -> Define Financial Statement Versions -
OB58

2. Execute a Balance Sheet (RFBILA00)

Information Systems -> Accounting -> Financial Accounting -> General ledger ->
Information System-> Balance Sheet

or
Accounting -> Financial accounting -> General ledger -> Information system ->
General LedgerReports -> Balance Sheet/Profit and Loss Statement/Cash Flow ->
General -> Actual/Actual Comparisons -> Balance Sheet/P+L - F.01

3. Execute a Balance Sheet Drill Down Report

Accounting -> Financial accounting -> General ledger -> Information system ->
General LedgerReports -> Balance Sheet/Profit and Loss Statement/Cash Flow ->
General - Various

4. Execute a Cost-of-Sales Profit and Loss Report

Accounting -> Financial accounting -> Special Purpose Ledger -> Tools -> Report
Painter -> Report -> Display -> Library 0F1, Report 0F-GUV1 -> Display -> Execute
- GRR3


 "
Π 

1. Capital Investment Projects ± Settle Order to AUC


Accounting -> Investment management -> Internal orders -> Period-end closing ->
Single functions -> Settlement ->« Various

2. Capital Investment Projects ± Settle AUC to asset in service


Accounting -> Investment management -> Fixed assets -> Postings -> Cap. asset u.
const. -> Settle AIBU

3. PP/CO Period-End Closing


Logistics -> Production -> Production Control -> Period-end closing ->«

or

Accounting -> Controlling -> Product Cost Controlling -> Cost Object Controlling ->
Product Cost by Order -> Period-End Closing -> Single Functions ->« Various

4. Internal Order Period-End Closing


Accounting -> Controlling -> Internal Orders -> Period-end closing -> Single
functions ->« Various

5. Cost Center Accounting Period-End Closing


Accounting -> Controlling -> Cost Center Accounting -> Period-end closing -> Single
functions ->« Various
6. Profitability Analysis Period-End Closing
Accounting -> Controlling -> Profitability Analysis -> Actual Postings -> Cost Center
Costs/Process Costs ->« KEU5, KEG5, CPAE

7. Lock Controlling Transactions


Accounting -> Controlling -> Cost Center Accounting -> Environment -> Period lock
-> Change OKP1

8. Reconciliation Ledger
Accounting -> Controlling -> Cost Element Accounting -> Actual postings ->
Reconciliation withFI KALC

9. Reconciliation Ledger Follow Up Postings


Accounting -> Controlling -> Cost Element Accounting -> Environment ->
Reconciliation ledger -> Follow up posting KAL1

10. Reconciliation Ledger Configuration


IMG -> Controlling -> Overhead Cost Controlling -> Cost and Revenue Element
Accounting -> Reconciliation Ledger Various

11. Post payroll information to accounting


Human Resources -> Payroll -> (Country-specific) PC00_ M99_ CIPE

12. Configure Payroll for posting to accounting


IMG -> Payroll -> Payroll: (country-specific) Various Customizing Technical,
Organizational and Documentary Steps

13. Define fiscal year variants


IMG -> Financial Accounting -> Financial Accounting Global Settings -> Fiscal Year
-> Maintain Fiscal Year Variant (Maintain Shortened Fisc. Year) OB29

14. Allocate fiscal year variant to a company code


IMG -> Financial Accounting -> Financial Accounting Global Settings -> Fiscal Year
-> Assign Company Code to a Fiscal Year Variant OB37

15. Define Variants for Open Posting Periods


IMG -> Financial Accounting -> Financial Accounting Global Settings -> Document -
> Posting Periods -> Define Variants for Open Posting Periods OBBO

16. Allocate Posting Period Variant to Company Code


IMG -> Financial Accounting -> Financial Accounting Global Settings -> Document -
> Posting Periods -> Assign Variants to Company Code OBBP
17. Open and Close Posting Periods
Accounting -> Financial accounting -> General ledger -> Environment -> Current
settings -> Open and Close Posting Periods OB52

18. Carry Forward Balance to New Fiscal Year


Accounting -> Financial accounting -> General ledger -> Periodic processing ->
Closing -> Carry Forward -> Balances F.16

19. Define Retained Earning account


IMG -> Financial Accounting -> General Ledger Accounting -> Business
Transactions -> Closing -> Carrying Forward -> Define Retained Rarnings Account
OB53

20. Schedule Manager


Accounting -> Financial accounting -> General ledger -> Periodic processing ->
Schedule Manager SCMA

21. Subsequent Business Area/Profit Center Adjustment ± Calculate


Accounting -> Financial accounting -> General ledger -> Periodic processing ->
Closing -> Regroup -> Balance Sheet Readjustment -> Calculate F.5D

22. Subsequent Business Area/Profit Center Adjustment ± Post


Accounting -> Financial accounting -> General ledger -> Periodic processing ->
Closing -> Regroup -> Balance Sheet Readjustment -> Post F.5E

23. Transfer B/S Items to Profit Center Accounting


Accounting -> Enterprise Controlling -> Profit Center Accounting -> Actual Postings
-> Period-End Closing -> Transfer Payables/Receivables 1KEK

24. PCA Balance Carried Forward


Accounting -> Enterprise Controlling -> Profit Center Accounting -> Actual Postings
-> Period-End Closing -> Carrying Forward of Balances 2KES

25. Profit and Loss Adjustment


Accounting -> Financial accounting -> General ledger -> Periodic processing ->
Closing -> Regroup -> Profit and Loss Adjustment F.50

26. Run Compact Document Journal


Accounting -> Financial accounting -> General ledger -> Information system ->
General Ledger Reports -> Document -> General -> Compact Document Journal
27. Create Balance Audit Work Files
IMG -> Financial Accounting -> General Ledger Accounting -> Business
Transactions -> Closing -> Documenting -> Define Accumulated Work Files for
Balance Audit Trail OBBQ

28. Run Monthly Balance Audit Trail for Open Item Accounts
Accounting -> Financial accounting -> General ledger -> Periodic processing ->
Closing -> Document -> Balance audit trail -> Open item accounts -> Open Item
Account Balance Audit Trail from the Document File

29. Run Monthly Balance Audit Trail for Other Accounts


Accounting -> Financial accounting -> General ledger -> Periodic processing ->
Closing -> Document -> Balance audit trail -> All accounts -> General Ledger from
the Document File

30. Create Extract for Accumulated Open Item Balance Audit Trail
Accounting -> Financial accounting -> General ledger -> Periodic processing ->
Closing -> Document -> Balance audit trail -> Open item accounts -> From balance
audit trail -> Extract for Accumulated Open Item Audit Trail

31. Run Accumulated Open Item Balance Audit Trail


Accounting -> Financial accounting -> General ledger -> Periodic processing ->
Closing -> Document -> Balance audit trail -> Open item accounts -> From balance
audit trail -> Accts Detailed Listing from Open Item Account Accumulated Audit
Trail

32. Create Extract for Accumulated Balance Audit Trail for Other Accounts
Accounting -> Financial accounting -> General ledger -> Periodic processing ->
Closing -> Document -> Balance audit trail -> All accounts -> From balance audit
trail -> Extract for the Accumulated Historical Balance Audit Trail

33. Run Accumulated Balance Audit Trail for Other Accounts


Accounting -> Financial accounting -> General ledger -> Periodic processing ->
Closing -> Document -> Balance audit trail -> All accounts -> From balance audit
trail -> Account Details from Historical Accumulated Balance Audit Trail


 ("
Π 

1. Process Depreciation Run


Accounting -> Financial accounting -> Fixed assets -> Periodic processing ->
Depreciation run -> Execute - AFAB
2. Process Investment Grant
Accounting -> Financial accounting -> Fixed assets -> Periodic processing ->
Investment grant
- AR11

3. Process Revaluation
Accounting -> Financial accounting -> Fixed assets -> Periodic processing ->
Revaluation for the balance sheet -> Post revaluation - AR29

4. AA Fiscal Year Change


Accounting -> Financial accounting -> Fixed assets -> Periodic processing -> Fiscal
year change - AJRW

5. AA Fiscal Year Close ± Account Reconciliation


Accounting -> Financial accounting -> Fixed assets -> Periodic processing -> Year-
end closing -> Account reconciliation - ABST2

6. AA Fiscal Year Close


Accounting -> Financial accounting -> Fixed assets -> Periodic processing -> Year-
end closing -> Execute - AJAB

7. Produce Asset History Sheet


Accounting -> Financial accounting -> Fixed assets -> Info system -> Reports on
Asset Accounting -> Balance Sheet Explanations -> International -> Asset History
Sheet

or

Accounting -> Financial accounting -> Fixed assets -> Info system -> Reports on
Asset Accounting -> Balance Sheet Explanations -> Country Specifics - various

8. Produce GR/IR Balance Report


Logistics -> Materials Management -> Inventory Management -> Environment ->
Balances Display -> List of GR/IR Bals. - MB5S

9. Maintain GR/IR Clearing Account


Logistics -> Materials Management -> Invoice Verification -> Invoice Verification ->
Further processing -> Maintain GR/IR acct - MR11

10. Material Revaluations ± Price Changes (manual)


Logistics -> Materials Management -> Valuation -> Valuation -> Price Determination
-> Change price - MR21
11. Material Revaluations ± Debit/Credit Material
Logistics -> Materials Management -> Valuation -> Valuation -> Price Determination
-> Debit/cred. material - MR22

12. Product Costing Material Price Change


Accounting -> Controlling -> Product Cost Controlling -> Product Cost Planning ->
Material Costing -> Price Update - CK24

13. Material Ledger Closing


Logistics -> Materials Management -> Valuation -> Actual Costing/Material Ledger -
> Periodic material valuation -> Post closing - CKMI

14. Materials Management Closing


Logistics -> Materials Management -> Material Master -> Other -> Close period -
MMPV

15. Materials Management Closing ± Control Posting to Prior Period


Logistics -> Materials Management -> Material Master -> Other -> Allow posting to
previous period - MMRV

16. Lowest Value Determination ± Market Prices


Logistics -> Materials Management -> Valuation -> Valuation -> Bal. sheet valuation
-> Determ. lowest values -> Market prices - MRN0

17. Lowest Value Determination ± Range of Coverage


Logistics -> Materials Management -> Valuation -> Valuation -> Bal. sheet valuation
-> Determ. lowest values -> Range of coverage - MRN1

18. Lowest Value Determination ± Movement Rate


Logistics -> Materials Management -> Valuation -> Valuation -> Bal. sheet valuation
-> Determ. lowest values -> Movement rate - MRN2

19. Lowest Value Determination ± Loss-Free Valuation


Logistics -> Materials Management -> Valuation -> Valuation -> Bal. sheet valuation
-> Determ. lowest values -> Loss-free valuation - MRN3

20. LIFO Valuation


Logistics -> Materials Management -> Valuation -> Valuation -> Bal. sheet valuation
-> LIFO Valuation - Various
21. FIFO Valuation
Logistics -> Materials Management -> Valuation -> Valuation -> Bal. sheet valuation
-> FIFO Valuation - Various

22. Physical Inventory Processing


Logistics -> Materials Management -> Physical Inventory - Various

23. Analyze GR/IR Clearing Accounts and Display Acquisition Tax


Accounting -> Financial accounting -> General ledger -> Periodic processing ->
Closing -> Regroup -> GR/IR clearing - F.19

24. Define Adjustment Accounts for GR/IR Clearing


IMG -> Financial Accounting -> General Ledger Accounting -> Business
Transactions -> Closing -> Regrouping -> Define Adjustment Accounts for GR/IR
Clearing - OBYP

25. Print Balance Confirmation


Accounting -> Financial accounting -> A/P or A/R -> Periodic processing -> Closing
-> Check/count -> Balance confirmation: Print

or

Accounting -> Financial accounting -> A/P or A/R -> Periodic processing -> Print
correspondence -> Balance confirmation -> Print letters - F.17

26. Configure Balance Confirmation


Accounting -> Financial accounting -> A/P or A/R -> Periodic processing -> Closing
-> Check/count ->«

or

Accounting -> Financial accounting -> A/P or A/R -> Periodic processing -> Print
correspondence -> Balance confirmation - F.1B, F.1A

27. Post Individual Value Adjustment


Accounting -> Financial accounting -> Accounts receivable -> Document entry ->
Other -> Intern. trans. posting -> Without clearing - F-21

28. Define Account Determination for Flat-Rate Individual Value Adjustment


IMG -> Financial Accounting -> Accounts Receivable and Accounts Payable ->
Business Transactions -> Closing -> Valuate -> Valuations -> Define Accounts
OBB0
29. Configure Flat-Rate Individual Value Adjustment
IMG -> Financial Accounting -> Accounts Receivable and Accounts Payable ->
Business Transactions -> Closing -> Valuate -> Valuations ->« SPRO

30. Calculate Flat-Rate Individual Value Adjustment


Accounting -> Financial accounting -> Accounts receivable -> Periodic processing ->
Closing -> Valuate -> Further valuations - F107

31. Writing-Off Doubtful Receivables


Accounting -> Financial accounting -> Accounts receivable -> Document entry ->
Other -> Intern. trans. psting -> With clearing - F-30

32. Customizing Exchange Rates


IMG -> General Settings -> Currencies - Various

33. Maintaining Exchange Rates


Accounting -> Financial accounting -> General ledger -> Environment -> Current
settings -> Enter exchange rates - OB08

34. Customizing Valuation Methods


IMG -> Financial Accounting -> General Ledger Accounting -> Business
Transactions -> Closing -> Valuating -> Foreign Currency Valuation -> Define
Valuation Methods - OB59

35. Foreign Currency Open Item Valuation


Accounting -> Financial accounting -> General ledger -> Periodic processing ->
Closing>>Valuate -> Valuation of Open Items in Foreign Currency - F.05

36. Account Determination for Exchange Rate Differences


IMG -> Financial Accounting -> General Ledger Accounting -> Business
Transactions -> Closing -> Valuating -> Foreign Currency Valuation -> Prepare
automatic postings for foreign currency valuation - OBA1

37. Regroup Receivables and Payables


Accounting -> Financial accounting -> A/P or A/R -> Periodic processing -> Closing
-> Regroup -> Receivables/ Payables - F101

38. Account Determination for Regrouping Receivables and Payables


IMG -> Financial Accounting -> Accounts Receivable and Accounts Payable ->
Business Transactions -> Closing -> Regrouping - OBBV, OBBW, OBBX
39. Revalue Foreign Currency G/L Account Balances
Accounting -> Financial accounting -> General ledger -> Periodic processing ->
Closing -> Valuate -> Foreign Currency Valuation of Inventory - F.06

40. Posting Accruals/Deferrals


Accounting -> Financial accounting -> General ledger -> Periodic processing ->
Closing -> Valuate -> Enter Accrual/Deferral Doc. - FBS1

41. Posting Accrual/Deferral Reversal


Accounting -> Financial accounting -> General ledger -> Periodic processing ->
Closing -> Valuate -> Reverse Accrual/Deferral Document - F.81

42. Generate Recurring Entry Posting


Accounting -> Financial accounting -> General ledger -> Periodic processing ->
Recurring Entries -> Execute - F.14

"

Œ
 
"  3

Business Area Sub-Grouping Transaction Code

Acct. Pay. MK03 Display Vendor Master


FK10 Display Vendor Account Balance
FBL1 Display Vendor Account Line Irems
FB03 Invoice Retrieval FI
MR3M Invoice Retrieval MM
ME23 Display Purchase Order History
MR02 View Blocked Invoices
ZMRXRR055 GR/IR Reconciliation - Material Account

Acct. Rec. VF03 Display an Invoice v45b

Cost Accounting Cost Accounting - CCA/PCA Master/Date

KSH1 Create Cost Center Group


KSH2 Delete/Change Cost Center Group
FSP3 Display G/L Account Posting COA
FSS3 Display Account in Company Code
KS03 Display Cost Center
KSH3 Display Cost Center Group
KA03 Display Cost Element
KAH3 Display Cost Element Group
KE53 Display Profit Center
KCH3 Display Profit Standard Hierarchy
KK03 Display Stat Key Figure
KBH3 Stat Key Figure Group

Cost Accounting - Cost & Profit Center Planning

KP06 CC-Input/Change Budget Plan(Cost Element Planning


KP46 CC-Input/Change Budget Plan(Cost Element Planning
KP26 Input or Chg Activity Type or Price Planning
KSU7 CC-Create Plan Assessment Cycle
KSU8 CC Planned Assessment Cycle/ Change
KSU9 CC Planned Assessment Cycle/ Display
KSUA CC Planned Assessment Cycle Delete
KSUB CC Execute/Reverse Plan Assessment Cycle
KSV7 CC Planned Distribution Cycle - Create
KSV8 CC Planned Distribution Cycle - Change
KSV9 CC Planned Distribution Cycle - Display
KSVA CC Planned Distribution Cycle - Delete
KSVB CC Planned Dist. Cycle - Execute/Reverse.
KP97 CC Copy Plan Version
KPMN CC Set Planner Profile
KSMN Define Report Currency
KSMN Define Selection Criteria for Cost Center Reports
7KE1 CC Input/Change Budget Plans(Acctg. Planning.)
7KE5 CC Stat Key Figure Planning.

Cost Accounting - Period End Accounting.

F-02 Create various types of Journals.


FB11 Display/Complete/Post a Parked or Held Doc
FB08 Reverse an Incividual GL Posted Document
FB04 Display Changes to a Document
FB02 Change Document Header
FB09 Change Document Line Iems
FBS1 Create Accrual/Deferral w/out a Reference Doc.
F.81 Create an Accrual Reversal Entry
F.80 Mass Reversal of Documents.
FB03 Display a Document
FS10 Create Worklist and/or Display Gen Ledger Bal
FYLS """"
FBL3 Display General Ledger Line Items
KSH1 "CC Create a ""Local"" Cost Center Group"
KSH2 "CC Change a :Local"" Cost Center Group"
KSV1 CC Create an Actual Distribution Cycle
KSV2 CC Change Actual Distribution Cycle
KSV3 Display Actual Cost Center Distribution cycle
KSV4 Delete Actual Distribution Cycle
KSV5 CC Execute or Reverse Actual Dist. Cycle
KSU1 CC Create an Actual Assessment Cycle
KSU2 CC Change Actual Assessment cycle
KSU3 CC Display Actual Assessment Cycle
KSU4 CC Delete cost Center Actual Assessment Cycle
KSU5 CC Execute/Reverse Actual Assessment Cycles
4KE1 PC Create Actual Distribution Cycle
4KE2 PC Change Actual Distribution Assessment Cycle
4KE3 PC Display Actual Distribution Cycle
4KE4 PC Delete Actual Distribution Cycle
4KE5 PC Actual distribution Cycle Execute
3KE1 PC Create Actual Assessment Cycle
3KE2 PC Change Actual Assessment Cycle
3KE5 PC Execute Actual Assessment Cycle
KB31 CC Post Actual Statistical Key Figures
3KED PC Post Actual Statistical Key Figures
F.5D Calculate BS Readjustment for PCA
1KEK Transfer Payables & Receivables.
KE5T Reconcile FI to PCA
ZFAF Create Affiliate Invoice
KOK5 Create/Maintain Storeroom & Maint. Order Group
K086 Settle Maint. Orders
CO88 Settle Process Order - Collective Process
KOB1 Report-Generate Actual Cost Line Item Rpt. Oreders
KSB1 Report-Generate Actual Cost Line Item Rpt. Cost Centers
KE5Z Report-Genrate an Actual Line Item Rpt. for PCA
SARP Generate Transit Maqterials from Custom Reports
Generate a Purchase Price & Exchange Rate Variance Report
Generate Production Order variance Report
SART Generate a COPS Reclassification Report
Generate a FPLC Mix-Adjustment Report
Generate a COC Cost Element Actual vs. Budget Report
Generate a COC Cost Center Actual vs. Budget Report
Generate a Cost Center Actual/Plan/Variqnce Report
Generate an EC-PCA Actual Line Items Report
Generate a TDC PCA Analysis Report
GR55 Generate a PCA Actuals Report
SART Generate a COPS Reclassification for Carrier Sales Report
SA38 Generate a FPLC Mix Adjusted Report
c Œ Œ  Œ2
 Ñ
H6

c       


  
*

c  
-   
*,
$

 
(

  
 

In COPA, before creating report, you have to define forms.

For forms check this t.codes:

KE34 - Define Forms for Profitability Reports

KE94 - Define Forms for Reports Based on Line Items

Reports check this t.codes.

KE31 - Create Profitability Report

KE91 - Create Report Based on Line Items

KE32 - Change Report

Ñ
H6(
 ,  Ñ
 

""  


 
!+!3"A!+!4

These are custom reports created in your Op Co.

Option 1. Call the form using KE35 and check if the Company Code is assigned to
any of the columns or rows by double-clicking these. If it has been assigned and if
there is a Fixed Value, rather than a Variable, you may then have to change that to a
variable. The Company Code will then appear on your selection screen by default.

Option 2. Call KE35 and check if the Company Code has been assigned in the
General Selections screen. chances are it is not. In which case, include it from the list
of Characteristics to your right. Provide a variable value, so the system prompts for an
entry while running the report.

Option 3. Call up the report using KE32 and check if the Company Code
characteristic appears under "Variables". Make sure that small box next to it is
checked (Entry at Execution). This should bring up the field during report run.

In KE96 pick the form that relates to your report. Then EDIT- Gen. Data Selection- .
Move the Characteristic you want to the left in the selected characteristics.

c   
   
 
 (     ?:    
   
H6

PA transparent tables are in the following;

xxxx = operating concern

Table COEP CE1xxxx = actual line items

table COEJ CE2xxxx = plan line items

tables COSP COSS CE3xxxx = segment level

CE4xxxx = Profitability segment.

Check individual data for KE30

KE24 - Display Actual Line Items

 
Ñ 
Œ(
&Ñ

&

 



Œ( 2  


Ñ 
& 
&

 


FBAS Financial Accounting ³Basis´
BKPF Accounting Document Header BUKRS / BELNR / GJAHR
BSEG Accounting Document Segment BUKRS / BELNR / GJAHR /
BUZEI
BSIP Index for Vendor Validation of Double BUKRS / LIFNR / WAERS /
BLDAT /
Documents XBLNR / WRBTR / BELNR / GJAHR /
BUZEI
BVOR Inter Company Posting Procedure BVORG / BUKRS / GJAHR /
BELNR
EBKPF Accounting Document Header (docs from GLSBK / BELNR /
GJHAR / GLEBK
External Systems)
FRUN Run Date of a Program PRGID
KLPA Customer / Vendor Linking NKULI / NBUKR / NKOAR /
PNTYP
/ VKULI / VBUKR / VKOAR

KNB4 Customer Payment History KUNNR / BUKRS


KNB5 Customer Master Dunning Data KUNNR / BUKRS / MABER
KNBK Customer Master Bank Details KUNNR / BANKS / BANKL /
BANKN
KNC1 Customer Master Transaction Figures KUNNR / BUKRS / GJHAR
KNC3 Customer Master Special GL Transactions KUNNR / BUKRS /
GJAHR / SHBKZ
Figures
LFB5 Vendor Master Dunning Data LIFNR / BUKRS / MABER
LFBK Vendor Master Bank Details LIFNR / BANKS / BANKL /
BANKN
LFC1 Vendor Master Transaction Figures LIFNR / BUKRS / GJHAR
LFC3 Vendor Master Special GL Transactions LIFNR / BUKRS / GJHAR /
SHBKZ
Figures
VBKPF Document Header for Document Parking AUSBK / BUKRS /
BELNR / GJHAR
& "#6&

 

!
$ I J
KNB1 Customer Master (Company Code) KUNNR / BUKRS
LFA1 Vendor Master (General Section) LIFNR
LFB1 Vendor Master (company Code Section) LIFNR / BUKRS
SKA1 G/L Account Master (Chart of Accounts) KTOPL / SAKNR
SKAT G/L Account Master (Chart of Accounts ± SPRAS / KTOPL / SAKNR
Description)
MAHNS Accounts Blocked by Dunning Selection KOART / BUKRS /
KONKO / MABER
MHNK Dunning Data (Account Entries) LAUFD / LAUFI / KOART /
BUKRS /
KUNNR / LIFNR / CPDKY / SKNRZE /
SMABER / SMAHSK / BUSAB
&Ñ0! 0! ?& :!
   

  &

0!  

SKAS G/L Account Master (Chart of Accounts ± SPRAS / KTOPL / SAKNR
/ SCHLW
Key Word list)
SKB1 G/L Account Master (Company Code) BUKRS / SAKNR
FI-GL-GL (FBSC) General Ledger Accounting: Basic
Functions - R/3 Customizing for G/L Accounts
FIGLREP Settings for G/L Posting Reports MANDT
TSAKR Create G/L account with reference BUKRS / SAKNR
FI-GL-GL (FFE) General Ledger Accounting: Basic
Functions - Fast Data Entry
KOMU Account Assignment Templates for G/L KMNAM / KMZEI
Account items
&Ñ00?& 2: 
 $(  &

0"

KNKA Customer Master Credit Management : KUNNR


Central Data
KNKK Customer Master Credit Management : KUNNR / KKBER
Control Area Data
KNKKF1 Credit Management : FI Status data LOGSYS / KUNNR /
KKBER / REGUL
RFRR Accounting Data ± A/R and A/P RELID / SRTFD / SRTF2
Information System
&Ñ0 0Œ 
* 


? &Ñ K".6"HK2:Œ
 
L
!
 

PAYR Payment Medium File ZBUKR / HBKID / HKTID /
RZAWE /
CHECT
PCEC Pre-numbered Check ZBUKR / HBKID / HKTID /
STAPL
&Ñ0 0Œ0?&+B: 
*  

 
 Œ
 
 L  



F111G Global Settings for Payment Program for MANDT


Payment Requests
FDZA Cash Management Line Items in Payment KEYNO
Requests
PAYRQ Payment Requests KEYNO

c  (
! + , 
  
?Œ)" 0
&:

As far as general ledger master data is concerned, the following tables are involved :

Table name : SKB1 : G/L Account Master ( Company Code)


Fields:
BUKRS : Company Code
SAKNR : G/L Account

Table name : SKA1 : G/L Account Master ( Chart of Accounts )


Fields:
KTOPL : Char of Accounts
SAKNR : G/L Account

Table name : SKAT : G/L Account Master Record ( Chart of Accounts : Description
)
Fields:
SPRAS : Language
KTOPL : Char of Accounts
SAKNR : G/L Account >00= *


Ñ 
Œ(
"#

"



Œ( 2  


Ñ 
& 
AUSP Characteristic Values MANDT / OBJEK / ATINN / ATZHL
"#0H #$  ""


A132 Price per Cost Center MANDT / KAPPL / KSCHL / KOKRS
A136 Price per Controlling Area MANDT / KAPPL / KSCHL /
KOKRS
A137 Price per Country / Region MANDT / KAPPL / KSCHL /
KOKRS
COSC CO Objects: Assignment of Origina MANDT / OBJNR / SCTYP /
VERSN
CSSK Cost Center / Cost Element MANDT / VERSN / KOKRS /
GJAHR
CSSL Cost Center / Activity Type MANDT / KOKRS / KOSTL /
LSTAR
KAPS CO Period Locks MANDT / KOKRS / GJAHR / VERSN

"#0H "#6#$  ""



!
$ 
CSKA Cost Elements (Data Dependent on MANDT / KTOPL / KSTAR
CSKB Cost Elements (Data Dependent on MANDT / KOKRS / KSTAR /
DATBI
CSKS Cost Center Master Data MANDT / KOKRS / KOSTL /
DATBI
CSLA Activity Master MANDT / KOKRS / LSTAR / DATBI
"#0#+?H"":#$  ""


COBK CO Object: Document Header MANDT / KOKRS / BELNR
COEJ CO Object: Line Items (by Fiscal MANDT / KOKRS / BELNR /
BUZEI
COEJL CO Object: Line Items for Activit MANDT / KOKRS / BELNR /
BUZEI
COEJR CO Object: Line Items for SKF (by MANDT / KOKRS / BELNR /
BUZEI
COEJT CO Object: Line Items for Prices MANDT / KOKRS / BELNR /
BUZEI
COEP CO Object: Line Items (by Period) MANDT / KOKRS / BELNR /
BUZEI
COEPL CO Object: Line Items for Activit MANDT / KOKRS / BELNR /
BUZEI
COEPR CO Object: Line Items for SKF (by MANDT / KOKRS / BELNR /
BUZEI
COEPT CO Object: Line Items for Prices MANDT / KOKRS / BELNR /
BUZEI
COKA CO Object: Control Data for Cost MANDT / OBJNR / GJAHR /
KSTAR
COKL CO Object: Control Data for Activ MANDT / LEDNR / OBJNR /
GJAHR
COKP CO Object: Control Data for Prima MANDT / LEDNR / OBJNR /
GJAHR
COKR CO Object: Control Data for Stati MANDT / LEDNR / OBJNR /
GJAHR
COKS CO Object: Control Data for Secon MANDT / LEDNR / OBJNR /
GJAHR
"#0#+0"6 ?HH :"6
 

? 

  :
COFI01 Object Table for Reconciliation L MANDT / OBJNR
COFI02 Transaction Dependent Fields for MANDT / OBJNR
COFIP Single Plan Items for Reconciliat RCLNT / GL_SIRID
COFIS Actual Line Items for Reconciliat RCLNT / GL_SIRID

"#0#+0"" ""
  

?" 




H0:
Lc H0
A138 Price per Company Code MANDT / KAPPL / KSCHL /
KOKRS
A139 Price per Profit Center MANDT / KAPPL / KSCHL / KOKRS
"#0#+0# ?H : #$   #    
 2$ 
  "
 



AUAA Settlement Document: Receiver Seg MANDT / BELNR / LFDNR
AUAB Settlement Document: Distribution MANDT / BELNR / BUREG /
LFDNR
AUAI Settlement Rules per Depreciation MANDT / BELNR / LFDNR /
AFABE
AUAK Document Header for Settlement MANDT / BELNR
AUAO Document Segment: CO Objects to b MANDT / BELNR / LFDNR
AUAV Document Segment: Transactions MANDT / BELNR / LFDNR
COBRA Settlement Rule for Order Settlem MANDT / OBJNR
COBRB Distribution Rules Settlement Rul MANDT / OBJNR / BUREG /
LFDNR
"#0#+0#?H%&:#$  # " 

# 
AUFK Order Master Data MANDT / AUFNR
AUFLAY0 Enttity Table: Order Layouts MANDT / LAYOUT
6"0"?H63:"
 


CEPC Profit Center Master Data Table MANDT / PRCTR / DATBI /
KOKRS
CEPCT Texts for Profit Center Master Da MANDT / SPRAS / PRCTR /
DATBI
CEPC_BUKRS Assignment of Profit Center to a MANDT / KOKRS / PRCTR
/ BUKRS
GLPCA EC-PCA: Actual Line Items RCLNT / GL_SIRID
GLPCC EC-PCA: Transaction Attributes MANDT / OBJNR
GLPCO EC-PCA: Object Table for Account MANDT / OBJNR
GLPCP EC-PCA: Plan Line Items RCLNT / GL_SIRID

6"0"  ?H63": "   


 "1
   "

 


A141 Dependent on Material and Receive MANDT / KAPPL / KSCHL /
KOKRS
A142 Dependent on Material MANDT / KAPPL / KSCHL /
WERKS
A143 Dependent on Material Group MANDT / KAPPL / KSCHL /
WERKS

Ñ 
Œ(


&Ñ00?: 

  &

L+2

ANKA Asset Classes: General Data ANLKL


ANKP Asset Classes: Fld Cont Dpndnt on Chart ANLKL / AFAPL
of Depreciation
ANKT Asset Classes: Description SPRAS / ANLKL
ANKV Asset Classes: Insurance Types ANLKL / VRSLFD
ANLA Asset Master Record Segment BUKRS / ANLN1 / ANLN2
ANLB Depreciation Terms BUKRS / ANLN1 / ANLN2 /
AFABE
/ BDATU
ANLT Asset Texts SPRAS / BUKRS / ANLN1 / ANLN2

ANLU Asset Master Record User Fields .INCLUDE / BUKRS / ANLN1


/ ANLN2
ANLW Insurable Values (Year Dependent) BUKRS / ANLN1 / ANLN2 /
VRSLFD /
GJAHR
ANLX Asset Master Record Segment BUKRS / ANLN1 / ANLN2
ANLZ Time Dependent Asset Allocations BUKRS / ANLN1 / ANLN2 /
BDATU
&Ñ00?ÿ: 

  &

L+2ÿ)

ANAR Asset Types ANLAR


ANAT Asset Type Text SPRAS / ANLAR
FI-AA-AA (AB) Asset Accounting: Basic Functions ±
Asset Accounting
ANEK Document Header Asset Posting BUKRS / ANLN1 / ANLN2 /
GJAHR /
LNRAN
ANEP Asset Line Items BUKRS / ANLN1 / ANLN2 / GJAHR /
LNRAN / AFABE
ANEV Asset Downpymt Settlement BUKRS / ANLN1 / ANLN2 /
GJAHR /
LNRANS
ANKB Asset Class: Depreciation Area ANLKL / AFAPL / AFABE /
BDATU
ANLC Asset value Fields BUKRS / ANLN1 / ANLN2 / GJAHR
/
AFABE
ANLH Main Asset Number BUKRS / ANLN1
ANLP Asset Periodic Values BUKRS / GJAHR / PERAF /
AFBNR /
ANLN1 / ANLN2 / AFABER
&Ñ0 0=?!= :     = 
,(



GB03 Validation / Substitution User VALUSER


GB92 Substitutions SUBSTID
GB93 Validation VALID

Ñ
$
 

6


   Ñ
$
 
 
  *    $
  
  
 

 !) )  
 
 
  $ 
   !)   
)

For Example: during Goods Receipt

Stock Account - Dr
G/R I/R Account - Cr
Freight Clearing account - Cr
Other expenses payable - Cr

During Invoice Verification

G/R I/R Account - Dr


Vendor - Cr
c 
   !          
 #    
 
 

*  

Consumption of Raw Materials - Dr


Stock A/c - Cr

c 
   !    $       
 #    


 
*  

Inventory A/c - Dr
Cost of Goods Produced - Cr
Price difference - Dr/Cr
(depending on the difference between standard cost and actual cost)

c 
   !            $   


 
*  

Cost of Goods Sold - Dr


Inventory A/c - Cr

c 
 !  ""
  
- 
 


 
*  

Repairs and Maintenance - Dr


Inventory A/c - Cr

c 
 !  *
 
 

 , 


 
*  

Stock A/c - Dr (Receiving location)


Stock A/c - Cr (Sending location)
Price difference - Dr/Cr
(due to any difference between the standard costs between the two locations)

c 
  *$ , 

 
*  

Stock A/c - Dr/Cr


Inventory Revaluation A/c - Cr / Dr

c 
 c*
    

 
*  

Work in Progress A/c - Dr


Change WIP A/c - Cr
   $ 
   
 -    -  

 1
   (    
     
$
 


 
)

 

2(
 

6


Ñ =#Ñ"6 !6 6ŒÑ#
Invoices will be generated at the Smelters and stock points. The accounting entries
for the sale of goods despatched will flow from the Sales invoice generated in SAP
Sales and Distribution module. The following entries shall be passed
Customer Account Dr
Revenue Cr
Excise Duty Payable Cr
Sales Tax Payable (local or central) Cr

Note: As mentioned above in the FI document, which is created in the background,


the SD invoice number shall be captured. However as per the current accounting
procedure the accounting entry passed is as follows :-
Customer Account Dr
Revenue Cr
Excise Duty Billed Cr
Sales Tax Payable (local or central) Cr

Excise duty paid a/c Dr


Excise duty payable a/c Cr

6C#Π 6
There have been very few export transactions in the past. SAP system will be
designed to handle export business. Exports are mainly from the mines and will be
handled at the mines, however the documentation part will be taken care at the Head
Office. The accounting entry is:
Customer Account Dr
Revenue (Exports) Cr

The realisation of export sales will be directly credited to the bank. The accounting
entries will be as follow:
Bank Dr
Customer Cr
Exchange Fluctuation Dr/ Cr

The accounting entries will be:


Rebates/Discounts Dr
Customer Cr

26 ь +6+#
Debit Memos shall be issued in case of price difference, sale tax difference and
interest on usance period and overdue payments.

The accounting entries for two possible scenarios are as follows:


Price Undercharged:
Customer Account Dr.
Revenue Cr.
Sales tax payable Cr.
Sales tax undercharged
Customer Account Dr.
Sales tax adjustment Cr.

Interest on delayed payments/usance period and other charges


Customer Account Dr.
Interest Others Cr.

In case of HZL a complete retirement or a partial retirement of asset is done. The


system uses the asset retirement date to determine the amount to be charged off for
each depreciation area. The existing accounting policy is to provide depreciation for
the full quarter in which the asset is sold/discarded, recommended that the
depreciation be provided from the date of acquisition on prorata basis .

Accounting entry for sale of Asset to customers:


Customer Account Dr
Asset Sale Cr
Accumulated Depreciation Dr
Loss on Sale (if applicable) Dr
Asset Sale account Dr
Asset account Cr
Profit on sale (if applicable) Cr

Note: In case of any Sales Tax /Excise duty applicable for this transaction, SAP will
calculate the Sales Tax/Excise Duty based on the Tax Code selected the entry is
posted to the GL Account (Sales Tax Payable)

Accounting entry for sale without a customer:


Accumulated Depreciation Dr
Loss on Sale (if applicable) Dr
Asset Sale account Dr
Asset account Cr
Profit on sale (if applicable) Cr
Accounting entry for scrap
Accumulated Depreciation Dr
Loss on Sale of Assets Dr
Asset account Cr

 6 #& "
The sale of scrap (non-stock) shall be mapped as a direct manual FI entry. The
customer will be created as a FI customer. No Logistics module will be involved in
the process.

A FI Invoice will be prepared for the sale of scrap with the following entries:
Customer Dr
Sale of Scrap Cr
Excise Duty Payable Cr

2= "6 &#+ "%Œ#+6


Advances are received from the customers against delivery. These advances will be
recorded in a special general ledger account. The accounting entry for the same will
be:
Bank Account Dr
Advance Customer Payments Cr

These advances will be later on adjusted against the invoices raised on the customers.
Advances can be adjusted against more than one invoice at the time of clearing of the
invoices against advances.

Adjustment of Advances
Customer Account Cr
Advance Customer Payments Dr

A financial document would be created for each Bank Guarantee received and this
document number will be referred to in the Sales Order which would then monitor the
value and the validity of the of the Bank Guarantee instrument wise while doing the
billing.The letter of credit /Bank guarantee given will be recorded as a noted item.

Accounting Entry for Goods receipt


Stock/Inventory account Dr
GR/IR account Cr
Freight clearing account Cr
Accounting Entry on invoice verification of supplier
GR/IR Dr
Vendor account Cr

Accounting Entry on invoice verification of freight vendor


Freight clearing account Dr
Freight Vendor account Cr

!##2 6"6ь
Based on the Purchase order and the Quantity actually received Goods Receipts (GR)
will be done. Based on the GR done the following accounting entry will be passed in
the Financial Accounts
RM/PM Stock Account Dr
GR/IR Account Cr
Freight Clearing Account Cr

6C"Ñ6 Ñ =#Ñ"6 =6Ñ&Ñ"ŒÑ#


On receipt of the excise invoice cum gate pass the following entry will be passed
RG 23 A / RG 23 C Part 2 Account Dr
Cenvat Clearing Account Cr

=
Ñ
$ = 
 

6


=6 2#Ñ =#Ñ"6=6Ñ&Ñ"ŒÑ#

The detail process related to invoice verification is documented in Materials


Management Document.
On receipt of vendor bill the following entry will be passed:

GR/IR Account DR
Freight Clearing Account DR
Cenvat Clearing Account DR
Vendor Account CR

Invoice Verification for Foreign Vendor


On receipt of vendor bill the following entry will be passed:

GR/IR Account DR
Vendor Account CR

Invoice Verification for Custom vendor


On receipt of Vendor bill the follo wing entry will be passed:
1) RG 23A/RG 23C Part 2 A/c (CVD) A/c DR
Cenvat Clearing A/c CR
2) G/R I/R A/c DR
Cenvat Clearing A/c DR
Vendor A/c CR
3) Cost of Material A/c DR
Vendor A/c (Customs) CR

Invoice Verification for Freight / Clearing Agent


Cost of Material A/c DR
Vendor A/c (Clearing Agent) CR

Invoice Verification for Octroi Expenses


Cost of Material DR
Vendor A/c (Octroi) CR

TDS (Work Contract Tax) for Service Orders shall be calculated and deducted
accordingly.
The following entry will be passed on bill passing:

Expenses Account DR
Vendor Account CR
TDS Account CR

The material shall be returned to the vendor using the


Return to vendor movement type in SAP
Creating a Return PO

These transactions will be processed in the MM module.


The accounting entries will be :

Returns after GRN


GR/IR A/c Dr
Stock A/c Cr

The accounting in respect of debit / credit memos for FI vendors, the process will be
similar to that of invoice processing. The accounting entries will be:
On issue of debit note
Vendor Account DR
Expenses Account CR
In respect of import vendor - capital goods exchange differences are to be accounted
manually through a Journal Voucher for capitalization.
Exchange rate differences will be accounted at HO. An example of the accounting
entry in this case shall be:
Invoice entry @ 40 INR: 1 USD

Asset / Expense A/c DR 100


Vendor A/c CR 100

Payment Entry @ 41 INR: 1 USD


Vendor A/c DR 100
Bank A/c CR 110
Exchange rate loss Capital A/c DR 10

Asset A/c DR 10
Exchange rate loss Capital A/c CR 10

A new G/L account shall be created for the special G/L transactions.
The accounting entry for making the down payment shall be:
Advance to supplier account Debit
Bank A/c Credit

When the invoice is booked the following entry is passed


GR/IR account Debit
Vendor account Credit
Clearing of Invoice against Down Payment
Vendor A/c Debit
Vendor down payment account Credit

Wherever, TDS is applicable, the TDS will be deducted at the time of down-payment
to the vendor.
Down Payment for Capital (tangible) Assets

Down payment to vendors for capital acquisitions is to be reported separately in the


Balance Sheet under the head Capital Work in Progress. Hence down payment for
capital goods would be tracked through a separate special general ledger indicator.

The procedure to be followed is:


Definition of alternative reconciliation accounts for Accounts Payable for posting
down payments made for Capital assets
Clearing the down payment in Accounts Payable with the closing invoice.
A new G/L account shall be created for the special G/L transactions.
The accounting entry for making the down payment shall be:

Vendor Advance for Capital Goods Account Debit


Bank A/c Credit
When the invoice is booked the following entry is passed
Asset A/c / Asset WIP Debit
Vendor A/c Credit
Clearing of Invoice against Down Payment
Vendor A/c Debit
Vendor Advance for Capital Goods Account Credit

The Following are the TDS Rates (to be confirmed with the recent changes)
Particulars Tax Rate Surcharge Rate Total
Contractors ± 194 C 2% 5% 2.10%
Advertising ± 194 C 1% 5% 1.05%
Prof. Fees ± 194 J 5% 5% 5.25%
Rent ± Others ± 194 I 15% 5% 15.75%
Rent ± Company ± 194 I 20% 5% 21%
Commission ± 194H 5% 5% 5.25%
Interest - Others ± 194 A 10% 5% 10.50%
Interest ± Company ± 194 A 20% 5% 21%
Special Concessional Tax
Works Contract Tax

SECURITY DEPOSITS /EARNEST MONEY DEPOSIT RECEIVED FROM


VENDORS
Bank A/c DR
Security Deposit Vendor CR

EMD to give the age so as to enable the same to be transferred to unclaimed EMD
account.
PAYMENT OF TOUR ADVANCE DOMESTIC TOURS

Employee Advances will be paid by the Accounts Department unit wise based on the
requisition or recommendation of the respective departmental head.
Employee Travel Advance A/c DR
Cash / Bank Account CR >00   *
  Π0
*M ) )

 
$6
Ñ
 



c   $


At times some incorrect documents might have been entered in the systems.

If you have entered an incorrect document, you can reverse it. Note that R/3 can
reverse a document only if the following conditions are met:

- Contains no cleared items


- Contains only vendor, customer, or G/L line items
- Was posted within the FI system
- Contains only valid values, such as business areas, cost centers, and tax codes

Ordinarily, you post a reversing document in the same period you posted the original
document. The period of the original document must be open to post a reversing
document. If the period is not open, you can overwrite the posting date field with a
date in an open period, such as the current period.

Reversal can be done individually - FB08 or Mass F.80.

If the document to be reveresed contain cleared items, then cleared item must be reset
before the reversal of document.


*
Œ
 
&

 

6



 # Π $
 2 &

1) Settlement of advance will be done by the Accounts Department based on the


Travel Expense Statement submitted by the employee, which is approved by the
Concerned Department Head.

2) Expenses Account DR
Cash/Bank Account DR (if, refund)
Employee Advance Account CR
Cash/Bank Sub ledger Account CR (if, payable)

3) Banking Operations - Maintenance Of Bank Master

4) A House Bank is a combination of a Bank and a Branch. Account id is the account


number. A house bank can have multiple account IDs.. There could be a main account
as also payable account, which will be defined as separate account ids. General
Ledger accounts have to be created for each combination of a house bank and account
ID. The bank master details are to be provided by HZL.

5) General Ledger accounts have to be created for each account ID in the house bank.
Bank Account Master data will be maintained by the Finance Department centrally.

6) Each house bank and account ID combination shall have one main general ledger
account and several sub accounts mainly based on broad transaction types. These sub
accounts are necessary to facilitate automatic bank reconciliation process in R/3
system.


*  


7) The accounting entries will be generated automatically according to the posting
rules attached to the Transaction type. The following accounting entry is passed by the
system in respect of cheque deposit on account of collection from domestic
customers.

Bank cheque deposit account Debit


Customer account Credit

8) In this case, a bank sub account is selected based on the transaction code entered
by the user. The customer account is cleared i.e. invoice is cleared against the receipt.
In respect of any other deposits, the relevant accounts to be credited will depend on
the nature of transaction.

9) Payment against bills for collection. Based on the bank advices falling due on a
particular day one payment advice is made debiting the vendors and crediting bank.

" / 2  0 "   


10) All cheques received from customers shall be accounted at the point of receipt.
The entry posted shall be

Bank Sub account Dr


Customer Account Cr

" / 2  0 #  Π


 "   
11) All other receipts will be accounted through the Incoming Payment Transaction
of the Accounts Receivables module.

" / 

L# Π
"  
12) Based on the information of cheque bounced from the Bank, the accounts
Department will pass accounting entries for the cheque that have been bounced. The
procedure to handle bouncing of a cheque has been discussed under the following

13) Reset the clearing document ± If the document has been cleared i.e. an open
outstanding item has been cleared against an incoming receipt, then the clearing
document has to be reset to its original status of open item. This process is known as
reset of cleared document.

14) Reverse the entry passed for cheque deposited earlier ± Once the document has
been reset it will be reversed. The following accounting entry will be passed.
FI Customer DR
Bank cheque deposit account CR

15) In case of cheques being damaged while printing, the concerned cheques no. has
to be voided and the payment will be rerun.


*  


16) The Bank reconciliation process is based on the entries passed through the Bank
sub account and main account. The process is dependent on the Bank Statement
received from the Bank that will be entered into SAP. Accounting rules are to be
defined for each transaction type and posting rule for posting accounting entries as per
bank statement. Bank statements to be uploaded into SAP.

17) Bank Main account balance is the actual balance as per the bank statement
whereas the Bank sub accounts denote the reconciliation items. These sub accounts
show those entries, which will flow from the sub account which are not cleared in the
bank statement.

18) Adding or subtracting the Bank sub accounts will help in preparing the Bank
reconciliation statement.

19) The following scenarios would explain the reconciliation process:


- Cheque received from customer
- Cheque issued to vendors
- Cheque received from Other than Customers
- Direct Debits in Bank Statement
- Direct Credits in Bank Statement
- Fund Transfer between Bank Accounts

" /  $  & "


20) Accounting entry at the time of cheque deposit entry
Bank Cheque deposit account Debit
Customer Credit

21) Accounting entry after cheque has been cleared in the Bank statement Main Bank
account
Debit Bank
Cheque deposit account Credit

22) The clearing criteria for updating the bank main account and bank sub account
will be amount and document number which will be captured in the allocation field
of the bank sub account. The items, which have not been cleared in the bank
statement, will remain open in the bank sub account and will form part of the bank
reconciliation statement.

" / Ñ  Œ =



23) Accounting entry at the time of cheque issue
Vendor account Debit
Bank cheque payment account Credit

24) Accounting entry after cheque has been presented in the Bank
Bank cheque payment account Debit
Main Bank account Credit

25) The clearing criteria used for updating vendor account and Bank cheque payment
account will be amount and cheque number. The cheques presented to the bank and
are cleared are transferred to the bank main account. The remaining cheque issued
will form part of the bank reconciliation statement.

2  2( Ñ
 
*
26) Direct debit instructions will be given to the bank for example, LC payments or
certain bank charges are directly debited in the Bank Statement. In this case
accounting entry is passed only after the entry is passed in the bank statement.
Vendor / Expense Account Debit
Bank clearing account Credit

2  "  Ñ


 
*
27) Customer receipts are sometimes directly credited in Bank. E.g. export receipts. In
this scenario accounting entry is passed only at the time of bank statement entry. The
following accounting entry is passed
Bank clearing account Debit
Customer account Credit
Main Bank A/c Debit
Bank Clearing A/c Credit


* &-  2 
28) HZL has a practice of converting any amount above Rs. 1 crore in its Main bank
account, to a fixed deposit subject to a minimum of Rs. 1.01 crores. The FDR number
can be filled in one of the fields available in the accounting document.

" / +

  " / 

 "  $ 
29) The function of cheque management will enable printing of cheque through SAP.
Cheque series will be defined for a combination of a Company code and Bank
Account. Cheque numbering will be sequential order.

30) Cheque series for automatic payment has to be in sequential order. Cheque
printing facility will be available for the bank account.

"  +

  /  

31) The day-to-day treasury process in a company includes a number of transactions.
This includes determining the current liquidity using bank account balances (cash
position), determining open receivables and liabilities (liquidity forecast), manually
entering planned cash flows (payment advice notes), through to clearing bank
accounts, that is, collecting multiple bank account balances on one target account.

32) The main objective is to ensure liquidity for all due payment obligations. It is also
important to control and monitor effectively the incoming and outgoing cash flows.

33) This section shows you the overall liquidity status of your company by displaying
together the cash position and the liquidity forecast. The cash position is used in Cash
Management to show the value-date-dependent bank accounts and bank clearing
accounts, as well as the planned cash flows (payment advice notes). The liquidity
forecast comprises the incoming and outgoing cash flows, as well as the planned items
on the sub-ledger accounts.

"#2  . 
*Ñ


c    
           
            
     

   
        
  



It is possible to delete a house bank. First de-assign the GL account assigned to the
account id.

Delete all the account IDs.

Then delete the Bank ID.

By this way you can delete the house bank. The values are stored under the GL
account and not under the house bank. Hence it is possible to delete the house bank
once you de assign the GL account from the account ID.

Do not delete the house bank directly.

You need to do the below things:-

(1) First make the GL account balance as zero for the duplicate house bank, e.g. by
transferring to the original house bank.

(2) Then block this GL master.

(3) Then remove all the assignment of this duplicate house bank and account ID in
FBZP

(4) Close the check lot information for this house bank.

Then this house bank will become ineffective, you can change the description of this
house bank to ³Obsolete´ etc.

If you delete this house bank, the effect will be that for check information, it will
show with incorrect house bank. If not important in your case, then you can delete the
house bank.

c Π
H&,A!

Below given is the recommended posting key to be used for particular transaction by
SAP. If we use posting key according to this then standard reports set /given by SAP
will come with accuracy. This is for information

By: Abhijit

1-19 customer
20-39 Vendor
40 & 50 GL
70 debit Asset
75 credit Asset

Posting key Name Credit /Debit Account type


21 Credit memo Debit Vendor
22 Reverse invoice Debit Vendor
24 Other receivables Debit Vendor
25 Outgoing payment Debit Vendor
26 Payment difference Debit Vendor
27 Clearing Debit Vendor
28 Payment clearing Debit Vendor
29 Special G/L debit Debit Vendor
31 Invoice Credit Vendor
32 Reverse credit memo Credit Vendor
34 Other payables Credit Vendor
35 Incoming payment Credit Vendor
36 Payment difference Credit Vendor
37 Other clearing Credit Vendor
38 Payment clearing Credit Vendor
39 Special G/L credit Credit Vendor

Posting key Name Account type


01 Invoice Debit Customer
02 Reverse credit memo Debit Customer
03 Bank charges Debit Customer
04 Other receivables Debit Customer
05 Outgoing payment Debit Customer
06 Payment difference Debit Customer
07 Other clearing Debit Customer
08 Payment clearing Debit Customer
09 Special G/L debit Debit Customer
11 Credit memo Credit Customer
12 Reverse invoice Credit Customer
13 Reverse charges Credit Customer
14 Other payables Credit Customer
15 Incoming payment Credit Customer
16 Payment difference Credit Customer
17 Other clearing Credit Customer
18 Payment clearing Credit Customer
19 Special G/L credit Credit Customer
Posting key Name Credit /Debit Account type
40 Debit entry Debit G/L account
50 Credit entry Credit G/L account

Œ
 
=
"
  

. 
 Ñ 
 (
  , $
 
    $
 

 
$


1. Prepare the Balance Sheet at one cut off date.

2. Classify the Accounts into Group.

3. Create Group wise clearing GL (You should create clearing account through
OBD4)
for eg. Capital General Clearing A/c
Capital Initial Clearing A/c

Expenditure General Clearing A/c


Expenditure initial clearing A/c

Customer General Clearing A/c


Customer initial Clearing A/c

Create the GL each Account Group.

4. Create one Doc.Type "LD" for upload Legacy Data.

5. Post the Balance Sheet Figures through T.Code F-02 use Doc.Type "LD"
for eg. Sundry Debtors Balance Rs,5 lac in Balance Sheet. This fig was arrived
from 5
customers Mr.A - Rs.75,000 Mr.B Rs.25,000 Mr.C Rs. 400000

Post

Customer General Clg A/c Cr.5,00,000


Customer Initial Clg A/c Dr.5,00,000

Like that post all the Balance Figures in SAP group wise. Maintain one XL
Sheet. Carefully maintain this sheet.
All the General Clg GL figures are opposit to BS, only for controlling

Then post

Customer Inital Clg A/c Cr. 5,00,000

Mr.A A/c Dr. 75,000


Mr.B A/c Dr. 25,000
Mr.C A/c Dr. 4,00,000

After completed the posting all the inital accounts are "0" Value and all the General
Clg A/c are "0".

If you want to post the Customer open item line by line, prepare the XL sheet upload
through LSMW.

If you want to check the TB in SAP to Tally, select all the document and filter the
Doc.Type "LD" the debit balance and credit balance are "Zero".

Ñ+!Œ
 
  # D"Ñ


Œ   Œ)   #( , Ñ 
   C H  Ñ
$
 +)
"
 =
 ", 
 =
 +  
 !$
 !) )  

( 
 $)
 

   ,       
 (  Ñ $ (

Ñ
$ ( /

Ñ 
G*
 
- )

Transaction code : OBYC (in easy access)


In this transcation we have to specify GL account codes for material valuation created
by MM consultants.

The process in MM is here below:


1) Purchase Order : Tr code ME21N - here no integration required with FI
2) Goods Issue : Tr Code MIGO - here no integratinwith FI
3) Invoice Reciept - Tr Code MIRO - here when the invoice is recieved & MM
process the transaction based on OBYC configuration system will generate FI
document. System also generates Material document as well
4) Payment : Tr code F110 - Here also the the transcation affects FI
FI-SD integation:
This integration done using Tr Code VKOA. here we have to define GL account
codes to Condition types.

Process :
1) SD Raises Sales Order - No implication in FI
2) SD raises Delivery doc - No implication in FI
3) SD processes billing - no implication in FI
4) SD releases billing doc to FI - FI document gets generated (Tr Code VFX3)

Π  ++ $  




Each movement type has quantity and value string, which decides what to update.
Also each movement type has transaction event key (account modifier) which in turn
depending upon valuation grouping code and valuation class decides which G/L
account to post.

The flow is as follows:

Material type --> Account Category reference --> Valuation class -->Material.
Movement type -->Transaction event key-->Account modifier.

You have to do the configuration settings using Tr. code OBYC.

Try with Tr.code OMBW to check which G/L accounts are being hit on Plant,
Material and movement type.

# D"2

 
* C,! 

 * 
 ? C:- This transaction is used for all postings to stock accounts.
Such postings are effected, for example:
In inventory management in the case of goods receipts to own stock and goods issues
from own stock.
In invoice verification, if price differences occur in connection with incoming
invoices for materials valuated at moving average price and there is adequate stock
coverage.
In order settlement, if the order is assigned to a material with moving average price
and the actual costs at the time of settlement vary from the actual costs at the time of
goods receiptBecause this transaction is dependent on the valuation class, it is
possible to manage materials with different valuation classes in separate stock
accounts.
Caution:
Take care to ensure that:
A stock account is not used for any transaction other than BSX.
Postings are not made to the account manually.
The account is not changed in the productive system before all stock has been booked
out of it.

Otherwise differences would arise between the total stock value of the material master
records and the balance on the stock account.

#

 * 
?! :0Offsetting entries for stock postings are
used in Inventory Management. They are dependent on the account grouping to which
each movement type is assigned. The following account groupings are defined in the
standard system:

u AUA: for order settlement


u AUF: for goods receipts for orders (without account assignment) and for order
settlement if AUA is not maintained
u AUI: Subsequent adjustment of actual price from cost center directly to
material (with account assignment)
u BSA: for initial entry of stock balances
u INV: for expenditure/income from inventory differences
u VAX: for goods issues for sales orders without account assignment object (the
account is not a cost element)
u VAY: for goods issues for sales orders with account assignment object
(account is a cost element)
u VBO: for consumption from stock of material provided to vendor
u VBR: for internal goods issues (for example, for cost center)
u VKA: for sales order account assignment (for example, for individual purchase
order)
u VKP: for project account assignment (for example, for individual PO)
u VNG: for scrapping/destruction
u VQP: for sample withdrawals without account assignment
u VQY: for sample withdrawals with account assignment
u ZOB: for goods receipts without purchase orders (mvt type 501)
u ZOF: for goods receipts without production orders (mvt types 521 and 531)

You can also define your own account groupings. If you intend to post goods issues
for cost centers (mvt type 201) and goods issues for orders (mvt type 261) to separate
consumption accounts, you can assign the account grouping ZZZ to movement type
201 and account grouping YYY to movement type 261.
Caution:
If you use goods receipts without a purchase order in your system (movement type
501), you have to check to which accounts the account groupings are assigned ZOB.
If you expect invoices for the goods receipts, and these invoices can only be posted in
Accounting, you can enter a clearing account (similar to a GR/IR clearing account
though without open item management), which is cleared in Accounting when you
post the vendor invoice.
Note that the goods movement is valuated with the valuation price of the material if
no external amount has been entered.
As no account assignment has been entered in the standard system, the assigned
account is not defined as a cost element. If you assign a cost element, you have to
enter an account assignment via the field selection or maintain an automatic account
assignment for the cost element.

!Ñ 
?cC:- Postings to the GR/IR clearing account occur in the case of
goods and invoice receipts against purchase orders.
Caution:
You must set the Balances in local currency only indicator for the GR/IR clearing
account to enable the open items to be cleared.

  
 ?2: - Price differences arise for materials valuated at standard
price in the case of all movements and invoices with a value that differs from the
standard price. Examples: goods receipts against purchase orders (if the PO price
differs from the standard pricedardpreis), goods issues in respect of which an external
amount is entered, invoices (if the invoice price differs from the PO price and the
standard price).

Price differences can also arise in the case of materials with moving average price if
there is not enough stock to cover the invoiced quantity. In the case of goods
movements in the negative range, the moving average price is not changed. Instead,
any price differences arising are posted to a price difference account.
Depending on the settings for the posting rules for transaction/event key PRD, it is
possible to work with or without account modification. If you use account
modification, the following modifications are available in the standard system:
None for goods and invoice receipts against purchase orders.

   
?6Ñ :,   
  
 ?6H!:,    
 
 ?&6:
These transactions are used only if Purchase Account Management is active in the
company code.
Note
Due to special legal requirements, this function was developed specially for certain
countries (Belgium, Spain , Portugal, France, Italy, and Finland).
Before you use this function, check whether you need to use it in your country.

&Ñ&'

3)Π  
 
 " 
" (
)Π  
 (
  
 
)c 
! "  

    )
c     
 
     
c  
(
  
A  
  

ÿ)c 
   "#,

&
=
(
   )"# 

$
&
=
)c   
"#

&
=

)c  



 
   
  
   

   
  

4)c  
   
 
(
 ÿ# 
 )
&6)Ñ Œ
Ñ Œ (
 (   
#")c  
!"! 
(
 Ñ Œ
Ñ Œ 

1A). " 
  
 
1
 
     
   
   

 
     

 
  $  
  )A
company can include one or more company codes. If we are going for Consolidation ,
we need to enter the 6 character alphanumeric company identifier that relates to this
company code.

Company Codes within a Company must use the same chart of accounts and fiscal
year. And for consolidation purpose we use Group COA wherein we link the
Operating COA thru entering the GL account no. of the Group COA in the GL
Account of the Operating COA.

2A). A financial statement version corresponds to the chart of accounts and wherein
Individual (operational) accounts are assigned to the corresponding FS item on the
lowest level of this version. But as for the rollup of Accounts is not possible in all the
FSV which can be copied, n rather can update manually n create multiple FSVs if
necessary depending on the Financial Statements which are necessary for the
Organisation.
3A). All the Organizational units (Global Data) for a company code will b copied to
new company code upon using the copy function except for the transactional data.

4A). Yes, Group COA can be assigned i.e., the GL A/c.No. is linked to the GL
Accounts of the both Operating COA . That means Group COA consists of Unique
set of Accounts which can be linked to Op.COA ±1 and Op.COA ±2.

&Ñ"#Œ (
  

Ans: Q.No.1. In the SAP system, consolidation functions in financial accounting are
based on companies. A company can comprise one or more company codes. for
example: Company A have 4 company codes which is existing in different state and /
or country. When Company A wants to consolidated the accounts, it will give the
common list of accounts which in turn called group chart of accounts. Group chart of
account is used to define/ list the GL account uniformly for all company codes.

Ans: Q.No.2. In SAP R/3 system, will allow only one financial statement version for
single COA which you need to assign the same while copying the COA. T.code
OBY7

Ans: Q.No.3. When you want to create FYV, PPV, COA etc for new company code
which is as same as existing company code, then you can copy all the information
from the source company code to the target company else whatever is required as per
the new company code requirement you can only copy the same, rest you can create
as per the requirement. for example Fiscal year for new company code may be
shortented fiscal year which is differ from the existing company code. In this case,
fiscal year for new company code you have to create and assign it to company code.

Ans: Q.No.4. Operational chart of accounts is something differ from the Group chart
of accounts but Group chart of account can be assigned to Operating chart of account
1 and 2 through GL account no.

Operating chart of accounts: The operating chart of accounts contains the GL


accounts that you use for posting in your company code during daily activities.
Financial accounting and controlling both use this chart of accounts. You have to
assign an operating chart of account to a company code.

Group chart of accounts: The group chart of accounts contains the GL accounts that
are used by the entire corporate group. This allows the company to provide reports for
the entire corporate group.
 &Ñ"# Œ  (
$ 6
$

. Ñ*
   $



To find out which version is used for your Target Cost, try this menu path

IMG > Controlling -> Product Cost Controlling -> Cost Object Controlling -> Product
Cost by Order -> Period-end Closing -> Variance Calculation -> Define Target Cost
Versions (tcode OKV6).

.  
 Ñ
-  0 
-$
 
 
   

 Œ
 ,    
  
+cHB= 
(Œ9"ŒÑ)

You can used transaction 'OBCL'.

Via customizing: Asset accounting -> Integration with general ledger -> Assign input
tax indicator for non-taxable acquisitions

/!AÑ= 

Ñ 
 
! 

Ñ=

You could try executing program RFWERE00, without postings.


This is the same program which is used for period end closing- regrouping of
GR/IR...but for only a report do not create postings.

or

May be transaction MB5S can help you out.


  


  
   !  (
   ,  
 
  *
  
(
   
   
( 
G  
      
)D $ 
 
 ( 
G

   
  )
The balance carried forward is only a 'calculated' figure and not a 'posted' figure. The
break-up of the retained earnings figure is available when you run the balance carried
forward report.
You can also derive the balance by selecting only the P&L Accounts for the relevant
period. The net balance of these accounts should equal the retained earnings account.

". 
 


 
4) )Ñ ( 
 ". 
 

   

You can use RFFOUS_T to produce an ACH file. You may have to use user exits to
write header and trailer records. Please read documentation on this program and it is
self-explanatory.

 *



2
"
 



. * 


 
  
 

)

In 4.6 b the transaction is S_ALR_87004395 - Maintain Versions you can lock


versions for each fiscal year

" 

$


Ñ           


 
 $
  )


*+H4CH4(
* 

$

  )
?  ( 
  
#=53:

You can used report "RFKABL00".

In the accounts payable reporting menu this program can be found via:
Accounts payable -> Adequacy and documentation -> Master data -> Display of
vendor changes

(depending on your SAP version of course)


*
% 
.   &6 HŒCŒ  ŒŒ6)ŒCŒ

ь6+)ŒCŒ)
.   


Try using program RFEBKA00 to upload the two files.

- one is the header file containing the House bank & account information along with
the date and the statement number
- the other is the item details.

&&Ñ&/
* '
3

3) c   
 &Ñ  
  (   
 #?   : Ñ
 

   
 )
ÿ)c   

 


$
  


$
)  Π  ( 
 (
* 
   (
*) Ñ   
    (
     (
* !   
) c   
   
 )
4) c   $    $ 
  
5) "
 
(  - 
  &Ñ0++ 

)  - 
 
 
) $
  
)  
 
)   
7) +-
)  


 $   
8) Ñ
  
    

^)c  (
+, 

,   


Find here with the answers for your questions

1.Whether any FI document will be created during PO(Purchase order)?If pl mention


the entry also?

Ans: There is no document that is created in FI side during PO. But in controlling
there can be a commitment posting to a Cost Center. The offsetting entry is posted at
the time of GR.

2.What factors differentiates from one dunning level and other dunning level

Ans: The most important thing that differentiates the dunning levels are the dunning
texts. The dunning text defines the urgency of the dunning notice. The other things
can be the dunning charges, minimum & maximum amounts etc.

3.APP
There will be many banks in a house bank. If the payment should be maid from
particular bank GL account. Where it is configured.

Ans: There can be several accounts in the same house bank. We should assign the GL
accounts exclusively at the time of creating the Bank master data and the bank
accounts. Accordingly we can do the bank determination in FBZP for the individual
banks and the corresponding sub accounts.

Tr code for Defining bank : FI12.

4.What are various types of servers in SAP R/3?

Ans: The Typical SAP landscape looks something like figure 1.4 below:

5.can anybody explain me FI-MM integartion.pl explain in detail

i. Movement types:

Classification key indicating the type of material movement (for example, goods
receipt, goods issue, physical stock transfer).

The movement type enables the system to find predefined posting rules determining
how the accounts of the financial accounting system (stock and consumption
accounts) are to be posted and how the stock fields in the material master record are to
be updated.

ii. Valuation class

Assignment of a material to a group of G/L accounts

Along with other factors, the valuation class determines the G/L accounts that are
updated as a result of a valuation-relevant transaction or event, such as a goods
movement.

The valuation class makes it possible to:

- Post the stock values of materials of the same material type to different G/L
accounts
- Post the stock values of materials of different material types to the same G/L
account

iii. Transaction/Event Key


Key allowing the user to differentiate between the various transactions and events
(such as physical inventory transactions and goods movements) that occur within the
field of inventory management.

The transaction/event type controls the filing/storage of documents and the


assignment of document numbers.

iv. Material Type

Groups together materials with the same basic attributes, for example, raw materials,
semifinished products, or finished products.

When creating a material master record, you must assign the material to a material
type. The material type you choose determines:

- Whether the material is intended for a specific purpose, for example, as a


configurable
material or process material
- Whether the material number can be assigned internally or externally
- The number range from which the material number is drawn
- Which screens appear and in what sequence
- Which user department data you may enter
- What procurement type the material has; that is, whether it is manufactured in-house
or
procured externally, or both

Together with the plant, the material type determines the material's inventory
management requirement, that is:

- Whether changes in quantity are updated in the material master record


- Whether changes in value are also updated in the stock accounts in financial
accounting

6.Maximum no. of dunning levels are created?

Ans: 9 levels maximum.

7.In how many ways APP is configured?

Tr Code: FBZP

8.What is diff between AAM,Recurring entries,Sample doccument?


Account Assignment Model:

A reference for document entry that provides default values for posting business
transactions. An account assignment model can contain any number of G/L account
items and can be changed or supplemented at any time. In contrast to sample
documents, the G/L account items for account assignment models may be incomplete.

Recurring Entries:

A periodically recurring posting made by the recurring entry program on the basis of
recurring entry original documents.

The procedure is comparable with a standing order by which banks are authorized to
debit rent payments, payment contributions or loan repayments.

Sample Documents:

Special type of reference document. Data from this document is used to create default
entries on the accounting document entry screen.

Unlike an accounting document, a sample document does not update transaction


figures but merely serves as a data source for an accounting document.

&&Ñ&/
* '
ÿ

3)c 
 $ 
  
# 
*  
A
 $ 

>> There is no direct assignment. You plan the output for a cost center first in kp26.
Then you've to plan the value of that cost center which you budget for a period in
kp06. Planned Activity expenditure / Planned Actvty qty gives yoa planned act rate
which you can use to valuate your activity confirmations in mfg ordrs. You can also
define your own prices,but you have to run the price revaluation if you want to
revaluate your actual activity prices.

ÿ)&)*  


 

A $ 

A  


>> Stat key fig are not real account assignments. In simple traditionl terms it is the
base to allocate or define praportions with which the cost is allocated. SKFs are used
to calculate the debit on a receiver object. These values can be used for assessing
common costs which are used by all the other cost centers.
).H&*))H
$Œ" )

>> You create & plan SKF.


Create using KK01 & PLAN the parameters of SKF in KP46

Π(2 

3)2 

*
    , /
* 



$)

ÿ) Ñ
 !    $   
  
 
   
 
  


)c  


) Ñ
 $
  ?++:,    $ A /
 
 Ñ *
   
$ 
 /
 
 !    -  $$
 , 
 
 *
 
!  )   * 
 
$ 

4)Ñ
&Ñ 
 
  ! 
 
  
  
  

   $
 
 ()Ñ 
 
( 
 H    
  
         
  
  ! 
 (
  

Q: Software Life Cycle,

Ans: it is nothing but Road Map - five phases like, Project Preparation, Blue print,
Realisation, Final preparation and Go-live support.

Q: In GL master we have a option "Balance in local currency" and "Account


currency".What does it mean?

Ans: Account currency is that the GL account in which currency do you want to
maintain. if you decided that you want maintain in company code currency, you can
post any currency in that account.
If not, you want to maintain separate currency for that GL then exchange rate
difference will come because the conversion rate.

Balance in local currency - some GL account can't be maintain on open item basis and
can't in foreign currency like clearing account and discount account etc., in such case
you can assign this indicator to show the balance in local currency.
Q. In movement type(MM), what is value & quantity string I know it updates values
and quantities in GL with mix of valuvation class, transaction key modifier and GL
A/c. But how does it work when doing a mvt type?

Ans: Basically, the system does not know which GL has to be updated with what.
here, we are giving a direction to the system to update the data.

What you said is correct, the system will update the value and qty in the material
master. You would have seen some more fields also, like Movement indicator,
consumption, value string and transaction event key etc.,

While creating a PO, the system will take the Movement type as a base, with MT, it
will identify the MI(movement indicator - used to define whether it is goods
movement for production order, purchase order, delivery note etc), and it will identify
the consumption,( like it is assets, or consumption or sales order) and it will identify
the value string ( it is must to assigned to movement type, through allocation of value
string to movement type, system will automatically identify the GL ) and it will post
the entry (dr/cr)in the GL based on the transaction and event key figure which is used
to determine the debit and credit entry of a GL

Π(6
$

4. In Field Status Group there are options like Suppress, optional, Required, Display.
So that it is followed by so many screens and it is determined by posting key. Its both
debit (or) (Both) credit.

'

 
&Ñ

c     


 (
  
 
  
  
A company is the organizational unit used in the legal consolidation module to roll up
financial statements of several company codes.
The Company Code is the smallest organizational ! unit for which a complete self-
contained set of accounts can be drawn up for purposes of external reporting.

. 
    
 
 (       
  
One or more Operative Chart of Accounts can be assigned to a company code.

A COA must be aasigned to a company code. This COA is the operative COA and is
used in both FI and CO. One Chart of Account can be assigned to many Company
codes i.e., Multiple company codes can either share the same or have separate COA.
But a company code (Country specific Company code or International Company
code) can have a country specific COA also along with Operative COA. The link
between the regular COA and the country COA appears in the alternate number field
of the G/L master record.

Eg: If a company's subdidiaries are located in both US & Mexico. We need to


configure 2 Company codes - one for US and another for Mexico,for eg U100 and
M100. The same way we create 2 COA's one for US & one for Mexico, USCA and
MXCA. Mexico has different govt reporting requirements than the US so we will
need to define a company code specific to Country Mexico and also create a country
specific COA to be used, in addition to normal COA. In tcode OBY6(Comp Code
Global Parameters) of CC M100 we define normal COA i.e.,USCA in Chart of
Accounts field and MXCA in Country Chart/Accts field.

c   (


 
 $ 
 c       

Validations are used to check settings and return a message if the prerequisite check
condition is met.
Substitutions are similar to validations; they actually replace and fill in field values
behind the scenes without the user¶s knowledge unlike validations that create on-
screen msgs to the user.

c    

 
The Controlling Area is the central organizational unit within CO module. It is
representative of a contained Cost Accounting envt where costs and revenues can be
managed.

2
 
   (
 

  
  
  
A controlling area may include one or more company codes which must use the same
operative chart of accounts as the controlling area. A Controlling Area can contain
multiple company code assignments but a single company code can be assigned to
only one controlling area.

c       $



Fiscal Year is a period of 12 months and SAP provides 4 special periods to posting
adjustment Entries. Fiscal year determines posting periods. Posting periods are used to
assign business transactions. Fiscal year may be year dependent or year independent.

c          


The Special periods in a fiscal year variant can be used for things like posting audit or
tax adjustments to a closed fiscal year.

c    


 (   

 
    $

Year Dependent: the financial year is same as calendar year. Starting from 1st Jan to
31st Dec (where posting periods and the calendar months are equal)
Year Independent: the financial year is different from calendar year Starting from 1st
April to 31st March (where the posting period months are not equal to calendar year
months)

c    


     c 
     
Shortened Fiscal Year: a financial year, which has less than 12 periods.

c   


  
The Posting period variant controls which posting periods, both normal and special,
are open for each company code. It is possible to have a different posting period
variant for each company code in the organization. The posting period is independent
of the fiscal year variant.

c    


   
        
Document type is the identifier of differentt account transactions like SA for G/L,AA
for Asset Accounting etc.The doc. Types controls things like type of the account that
can be posted to, the number range assigned to it, and required doc header fields.

.  


       
Tolerance group stores Posting amount defaults. Tolerance groups are assigned to
User ID¶s that ensures only authorized persons can make postings.

c   


 *       

 
 *
Posting keys determine whether a line item entry is a debit or a credit as well as the
possible field status for the transaction. Posting keys are SAP delivered. If u want
changes like making additional fields optional on payment type posting keys then the
best possible action is to copy the posting key that needs to be modified and then
modify it.

c       


Field status groups control the additional account assignments and other fields that
can be posted at the line item level for a G/L account.

&

Π(H

'

 
&Ñ

'30c  


 

!$)  
   (

Answer: fb50,f-02 and others could be used for adjustments. These adjustments are to
correct any financial representation that has already been booked into the accounts.
'ÿ0  Ñ $       3 
?   0
  
 : 3$
? :
  
 
)  
   
 
  ,   ($     
 
 $,
/
       $

Ñ
$   
 3
?)3:)

Answer: If you have a GRN against these materials, then the same can be return
delivered. An appropriate movement type needs to be configured for the same. As for
the payment, raise a credit note on the vendor.

* Using Debit Memo you can get the money for defective 3 units. *-- Gnan Eswari

')0c    
   
 
Ñ (
$
)

Answer: There are loads of tables that get copied over when copying co codes. This
might be incomplete in a manual copy, and hence the manual route is not advisable.

')40Ñ
 , 
(
*   

')50  
 ÿ4 Ñ $   
 * G A
 ÿ5   
 * Ñ
$ 
 "2)Ñ
 (
 (  *(

   
,     
, )

Answer: The difference in the depreciation that is posted already, and what should be
posted with historical effect will be posted in the current accounting period.

')7.
  
 
(
   
   


 
    
  # 7ÿ /

 
  
 
         
   
   
 


 
  ?Ñ (
 1  :

Answer: Three, although the group and country chart of accounts are optional. The
group chart of accounts is assigned to the
operational chart of accounts, and the only mandatory CoA is the Operational CoA.

')8.



$
 
(
  )  

Answer: As many FSVs as you want can be assigned to the co code i.e. 1:n as of Co
Code: FSV.
Ñ $  " 
" 
  

  "" )
 
 ++ Ñ $      ,   $
,   ) Ñ

G $ #  

 

3) +Ñ ŒÑ  Œ# 6 "6 Ñ+ь &# Œ# 6 "6 H6D 6
""#% Œ Ñ! +6 Œ
ÿ)"# Œ# Ñ 2Ñ"Œ#&#"# Œ# Ñ !62# #Œ6CÑŒ)

Ñ $
  

  
  
Ñ    



-
$
$ 
)

1. MAINTAIN TOLERANCE LIMITS FOR TOLERANCE KEY PE ACCOUNT


ASSIGNMENT ----> Please follow this link --> SPRO ---> MM---> Purchasing -->
Purchase Order --> Set Tolerance limits for price variance --> Here you have to set for
Tolerance keys PE and SE. Just copy them from std co. code.

2. CONTROL INDICATORS FOR CONTROLLING AREA DO NOT EXIST. ----


>

In Controlling --> General Controlling --> Maintain Controlling Area --> Maintain
Controlling Area --> Activate Components/Control Indicators --> You need to check
if you want to activate the order management/activity based costing/commitment
management etc.

Ñ

&Ñ"# # + 

c   



&Ñ"#   2,++ )

Some basic information :

&Ñ0++Œ 

(
&Ñ0++  

Œ0  # D")

1. When PO is created :

---- No Entry -----

2. When GR is posted

Inventory Account dr (Transaction Key BSX in OBYC)


To GRIR account (T.Key WRX in T-code OBYC)

3. When Invoice is posted


GRIR account Dr.
Vendor account Cr.

4. Payment made to Vendor

Vendor A/c Dr
To Bank Clearing A/c Cr.

Points to know : Movement Types, Assignment of Movement types to T-keys (T-code


OMJJ), Value string (I also need some information on this) , OMWN and OMWB
transactions.

---

There is a close integration b/w FI & MM, actually document flows from MM to FI in
the following areas such as,

1. Movement Types:

Used to enable the system to find the predefined posting rules determining how the
accounts of financial accounting system are to be posted & to update the stock fields
in the matrl master data.(Goods Receipt, Goods Issue, etc)

2. Valuation Class:

Assignment of material to grp of gl account, used to determine the gl accounts that are
updated as a result of goods movement.

3. Transaction/Event key:

Used to control the storage or filing of documents & assignment of documents.Used


to differeniate b/w various transactions such as goods movement tht occur in
inventory.

4. Material Type:

Each material should assign mtrl type in mtrl master record used to update whether
changes made in qty are updated in material master record & change in value also
updated in stock account.

&Ñ02Ñ

Π

 

Œ0  =H#
1. Sales Order Created

---No Entry---

2. PGI done (Goods issue)

Cost of Goods Sold Dr (Configured in OBYC GBB T-Key)


To Inventory Account

3. Billing document released to Accounting

Customer Account Dr.


To Sales Revenue Account (ERL T-key in Pricing procedure)

Note : The GL account is assigned to this ERL in VKOA

4. Payment Received

Bank Clearing A/c Dr


Customer A/c Cr.

Points to Know : Good to understand the pricing procedure and how the different
transaction keys are used like ERL, ERS etc.

# 

"
 

Define the posting company code variant in + - =KŒ3#

Assign the company code variant in + - =K3K

Maintain the open and close posting period with # 5ÿ.

You can control period by : -

1. G/L number range.

2. Company code.

3. Company code and G/L range.


 # 5ÿ( 
  
  

If you have several company codes and want your users only to be able to open and
close periods
(transaction OB52) belonging to their posting period variant (=company code).

First you configure the Posting Variant :-

1) FI- FI Global Settings - Document - Posting Periods - Define Variants for Posting
Periods

2) FI- FI Global Settings - Document - Posting Periods - Assign Variants to Company


Code

Second Step:-

Goto SE11 copy the view V_T001B to ZV_T001B_000X (000X indicate the Posting
Variant)

In Change mode, tabstrips Selection Conditions Insert line 2 with

Œ( &   #  " $ =  2#


T001B BUKRS EQ '000X' AND

Save your entries

Third Step :-

Goto SE54, Options Generated Objects -> Create

Authorizations Group FC31


Function Group Z00F0
Maintenance Type One Type
Overview Screen 65
Single Screen 0

Final Step :-

Goto SE93, Create a new transaction code ZOB52_000X

Start object - Transaction with parameters (parameter transaction)

Transaction SM30, Tick Skip initial screen


   
   =
VIEWNAME ZV_T001B_000X
UPDATE X

Save your entries.

Now, test your new transaction code ZOB52_000X which will only display the
Posting Variant that you have define in your table view.

=

# 5ÿ+ ŒB


Ñ 
 
  
  $

# 5ÿ 
1
&- , %
  
   
 $
(
   
1


2
Œ*

In T-code OBBO you can create, if you are need, for every company code a posting
period variant which must assign to company code - T-code OBBP. With OB52 you
can determine for every posting period variant a posting period for every account type
(A,S,D,K,M and +).

Important: In FI it is possibile only two period ranges have to be open at the same
time, during of the closing procedure, one for posting period of fiscal year (1-12) and
one for special posting period (13-16).

If my answer it is not sufficient, please give me a example for what you want to say
with "to use multiple time zones".

6

The Last column in OB52 Screen for authorisation group.


I think this field can be effectively to restrict the posting by different users situated in
different time zones. Of course if a user is travelling from one time zone to other, this
option may not work unless authorisation group in his user Id is changed.

 
ь 
 ++=


+ "



Π 
 Ñ  *
    
    

 
) Π 


   
 $(ÿ4)Ñ $/


3) 2 

 *
          
 
     
$ 

 
  $)G4
 )

ÿ)Ñ 
    
(  
 
  
  $


$
 
++=)

In IMG, you can go to Logistics - General => Material Master => Basic Settings =>
Maintain Company Codes for Materials Management. You can then enter the periods
that you need to have open.

As far as running something monthly, if you are working only in one general region of
the world, you can run program RMMMPERI from SE38 at 00:01:00 on day 1 of each
period. You'll need to create a selection variant with a variable to tell it which period
to use.

We run into problems with MMPV/RMMMPERI, and have to actually manually


schedule it each month. I run it three times - one to open the periods for our Asian
plants (at 09:00:00 my time, on the last day of my month), one to open periods for our
European plants (at 16:00:00 my time, on the last day of my month), and one to open
periods for our US plants (at 00:01:00 my time, on the first day of my month). I've
not been able to schedule recurring jobs for the Asian and European plants, because I
can't figure out a way to set up a recurrence for the last day of the month. I can do it
on day 1, or day 28, or something specific like that, but since the last day of the month
can fall on day 28, 30, or 31, I'm not able to do that.

"  * &ÑD6
"


1 Execute Report for InterCompany Activity & Journal Entries


2 Open posting period for next yr
3 Run Business Area's Assignment report.
4 Review list of recurring journal entries
5 Execute Recurring Entries for A/R, A/P, G/L
6 Process Parked A/R, A/P, G/L accounting documents
7 Final Cutoff for the Maintenance of Fixed Asset- Add Transfer and Retire
8 Run Depreciation in Test Run and post
9 Verify Display Log for Depreciation Test Run
10 Capitalize AUC Assets if needed
11 Enter Payroll Data to SAP
12 Verify Depreciation Balances with GL balances
13 Post Depreciation
14 Execute Asset History Report, and retire assets if needed
15 Adjust specific depreciation areas if necessary
16 Reconcile AM subledger with GL
17 Check Bank Data
18 Review AR Open Items
19 Review AP Open Items
20 Execute Pending Invoices
21 Clear Open Item for GRIR, freight
22 Reconciliation of Financial Documents and transactional figures
23 Open new CO Posting Period
24 Compare current (cost estimates) with last current price (Moving Avg)
25 Update current cost price to material master price field.
26 Process Freight charges, Match SD freight to actual
27 Review Internal Order Postings
28 Settle All Orders
29 Verify All Post Goods Issue have been Invoiced (Billing Due List)
30 Review SD Billng Doc from prior mth that have not yet been released to
accounting
31 Reconciliation of MM movements in Transit Intra-SAP to NonSAP
32 Reconcile PI Inventory with SAP
33 Perform Manual Adjustment if needed
34 Verify balance of the GR/IR account
35 Post Accruals and Deferrals
36 Clearing of Cancelled Documents
37 Check Profitability Segment Adjustment
38 Aging Report-Reconcile GL balances with subledger balances AP
39 Check the check run numbers
40 Bank reconciliation Data
41 Enter Tax Journal Entry
42 Reconcile GL balances with subledger balances AR/MM/AP
43 Display Balance Sheet Adjustments
44 Post Balance Sheet Adjustments
45 Post Foreign Currency Valuation (foreign exchange)
46 Check generic cost centers for posting with wrong accounts
47 Correct wrong postings on generic cost centers
48 Check Validation dates for Cost Centers, Cost Elements, CO area
49 Check COGI--for both month end and year end
50 Doubtful receiviables
51 Verify In-transist Inventory
52 Reconcile PA to G/L
53 Post Cost Centre Assessments and Distributions
54 Run CO-FI Reconciliation to balance
55 Run BW reports P&L and Balance Sheet
56 Maintain CO yr variant
57 Fiscal Yr Balance carryforward AP/AR/AM
58 Fiscal Yr Balance carryforward CO
59 Fiscal Yr balance carryforward FI
60 Fiscal Yr balance carryforward PCA
61 Set Document number ranges - FI - new year
62 Set Document number ranges AP/AR - new year
63 Generate Financial statement Reports
64 Change Fiscal Year For Assets
65 Year end Closing-- Asset Accounting--final for year end
66 Close CO Posting Period
67 Close Prior A/R Posting Period
68 Close Prior A/P Posting Period
69 Close Prior MM Posting Period
70 Reverse accruals and deferrals for the new month
71 Reconciliation of Financial Documents from old fiscal year and new fiscal year
72 Load Balances, Budget Data for Cost centers, sales
73 Update Retained Earning Account , balance carry fwd

 &Ñ& D 

Π 

 (+3L ( 4,4,5
 

   

 $
 

 &  

 ) Ñ  
  ÿ70ÿ8)   *
,   &D=    ( 
 

,  
   ( )

In IMG go to financial accounting global setting then go to fiscal year variant and set
the fiscal year variant on year dependent year and follow the following procedure:

1. enter name of month started from may and end on april


2. enter the number of days in a month you want to close for example in may number
of days is 28 instead of 31
3. enter period from 01 to 12 started from may to april
4. enter -1 against the month from jan to april

For Example :

 +
  (  2   D  
May06 28 01 0
June 35 02 0
July 28 03 0
Aug 28 04 0
Sep 35 05 0
Oct 28 06 0
Nov 28 07 0
Dec 35 08 0
Jan07 28 09 -1
Feb 28 10 -1
Mar 35 11 -1
Apr 31 12 -1




 
& D=
A
 =


c G   
 (
 (
    $
 A 
  
$
)

By : Rams

Fiscal year variant determines if you are using calendar dependent year or year
dependent (where you can create your own periods) eg you want your period 1 to be
April period 2 to be May and so on.

Posting period determines which period is open. Your company code is tied to a
posting period variant. Each posting period variant is tied to an account type (GL,
vendor Asset etc)

Here you determine if period 1 should be open or period 2 etc.

Fiscal year variant and Posting period variant are differentiated based on their
purpose. While fiscal year variant is to define no of posting a period allowed and is
assigned to co code, posting period variant is to decide which periods can be opened
at particular point of time for posting. Separate rules can be defined for each type of
account. This is used for control purpose.

There isn't relation between Fiscal year variant and Posting period variant. But there is
relation between Fical year and Posting Periods. Fiscal year structure contains posting
periods. For each posting period we have specified day end. To process business
transactions these posting periods must be in open status. You can open all the posting
periods (or) you can restrict the posting periods by Account Type wise and Account
No wise and Authorization group wise.

To restrict the posting periods by Account Types wise first you need to open the
posting periods for all Account Types (³+´ symbol).

c    


 

 
  )

This depends upon the client requirement. Generally Fiscal year will be defined once.
But in some cases (where business will run for certain period means business will run
for 6 months or 8 months) evry year they will define fiscal year.

Independent Fiscal Year: In any year the starting period and ending period will be
same and same posting periods for continues years. It is called as INDEPENDANT
F.Y.
Dependant Fiscal Year: In any year the starting period and ending period may be
different (or) if you have less than 12months, that fiscal year must be define as a
DEPENDANT FISCAL YEAR (or) SHORT END FISCAL YEAR.

"  


It defines the structure of G/L accounts. It is a list of G/L accounts used by one or
more company codes. In that Chart of account you have to specify the length of G/L
accounts.

In SAP all the entries are document oriented. so from the balance sheet of any entry
you can identify the root of an entry. so it's like a flow chart in computer terms.

There are threee types of Chart of Account are there.

1.Operative Chart of Accounts


2.Group of Chart of Accounts
3.Country Chart of Accounts.

1.Operative Chart of Accounts is a Chart of Account you use for the company code.

2.For different chart of accounts(operative COA) for different company code, you can
group the chart of account into one chart of account for internal reporting, but cross
company code controlling is not possible, because of different chart of account for
different company code.

3.For different country you can have different reporting system. so for different
company code you can have different company code, but can have same Operative
Chart of account, so cross company code controlling is possible.

Π(N

c     


 (
 
     
 
    

   
 c     
 (
 "     
 
,# 
  

!   


To summarise, here is the COA setup in SAP:-

1. Operative chart of account - It is the main chart of account assigned to each


company code in OBY6.
2. Group chart of accounts - This is structured in accordance with requirements
pertaining to Consolidation

3. Country-specific charts of accounts - These are structured in accordance with legal


requirements of the country in question.

Standard COA is a sample COAs provided by SAP. like INT, CAUS etc. You can use
them as your operative COA or can create your own operative COA from these
standard COA.

Corporate Group COA is same as Group COA.

"6

  !
   


. 
 Ñ 
    !   
   A        "
6
 $
 (
  
Ñ    
         -  

c     ( 
  
    
      - 

 
 
 ! 

Well, the first thing that comes to mind is just download the GL Accounts, download
Cost Elements and do a quick VLookup in Excel. That will tell you. That'll take you
about 5 minutes or so.

or

You could try this respective transactions:


OKB2;
OKB3; and
SM35

To prevent creating of GL P&L items without creating the cost elements on 4.6 / 4.7
there is an option to allow the automatic creation of Cost Elements whenever a G/L
account is created in a Company Code. i.e. It does not create when an account is
created at the Chart of Accounts Level, only when it is created in a Company Code.

To do this;
// Financial Accounting // General ledger Accounting // G/L Accounts // Master
Records // Preparations // Edit Chart of Accounts List // Select the Chart of Accounts
then;
Integration // Controlling Integration // then I'll let you guess.
Also, you need to specify within controlling which account ranges should be created
under which Cost Element Category;
// Controlling // Cost Element Accounting // Master Data // Cost Elements //
Automatic Creation of Primary and Secondary Cost Elements // *.*

If this was configured, you could also create a batch file now that would catch up with
any cost elements not yet created.

c ! " 
 $
"  


- 
 
(
   
  $
 
 
$

General Ledger has two segments i.e.,

1. Chart of Accounts Data (T.Code= FSPO)and


2. Company Code Data (T.Code =FSSO)

GL account master records are divided into two areas to that company code with the
same chart of account can use the same GL account. The chart of account area
contains the data valid for all company codes, such as Account Number.

The Company code specific area contains data that may vary from one company code
to another, such as the currency in which the account may be posted.

Lets, suppose there are not segment both the segments are combined, at that time it
will become difficult to copy the Company Code data because the fields may vary in
company code. for example Currency, though you have same Chart of Account Data.

Because, GL Accounts has two segments, it will be easy to copy Chart of Accounts
data from A company code which matches your requirement and Company Code data
of B Company code and you can create a separate chart of account in C company
code.

To copy Chart of account data and Company code data seperately, see Alternative
method of creating GL Master in IMG screen.

" 
 

 
"+

There is no problem to change the account number in the vendor or customer master
data, that is :
All Document Items that were created in the old account will be posted in the same
old account when you have a payment posting, compensations, etc.

All document created after the change will be posted in the new account as well as the
payment postings, compensations and others.

The system will separate the postings in accordance with the moment at the
documents were created.

You can do a test in the development client before you do the change in the
production.

For example :-

You can create a new reconciliation account because you want the G/L accounts to
separate out sales. Just switched the setting in Customer Master and off you go. SAP
will recognized the old account for the old postings and used the new account for any
new postings.

Here is the official SAP help on the subject:-

You should run balance sheet adjustment program after any reconciliation account
change.

The system performs any adjustments required due to the change of reconciliation
accounts or G/L accounts. The items from the old reconciliation accounts are
allocated to the new accounts.

Since you cannot post to the reconciliation accounts directly, the postings are made to
temporary adjustment accounts.

These adjustment accounts should be displayed along with the relevant reconciliation
account in the balance sheet. The postings are then reversed after the balance sheet
has been created.

The program for sorting the payables and receivables makes the necessary
adjustments automatically. This means that you have to define the adjustment account
numbers and the posting keys for these postings in the system.

If you purchase and install the FI-LC Consolidation application and have bought up a
previous customer or vendor (thus also taking on his/her payables and receivables),
please refer to the note in the report documentation on changed reconciliation
accounts. To define the account numbers, select the activity Define adjustment
accounts for changed reconciliation accounts in the Accounts Receivable and
Accounts Payable Implementation Guide.

You should only run this program if your new reconciliation account is classified
differently from the original in your FS. e.g.. AR to Intercompany accounts. It will
just reclassify the existing balance. The line items will not be transferred. If not then
no need to run the program at all.

."
&Ñ"# 


In Co, we create Recon accts to keep Fi gl in balance with CO. Not all transactions
affect FI gls, best example of it is internal order settlements, they use secondary cost
elements and does not affect your G/l accts. To update FI side of it we maintain recon
accts. These are primarily for cross company, cross functional and cross business area
transactions.

The number of recon accts to be defined is dependant on various factors, like how
your management wants to see the reports.. whether they want to classify the cost
based on CO object class or by Co types etc..

However the basic config you got to follow is:

1. Activate Recon accts (if you have created CO area newly, it would be active).
use T.code: H 

2. Assignment of Recon document type to the Controlling area.


T.code: #HH

3. Creating clearing accts (that you want to us! e for reconciliation. During FI-Co
recon.. inter company clearing accounts will be automatically credited or debited and
now you need to create offset acct which will show up in P&l acct).
Acct determination set up thru T.code: # D

4. Maintain accts for Automatic Recon posting.


T.code # D

5. Assign Number ranges to Recon activity.


Tcode #H3*-- Radha
Krishna
c  
 

 
, 
  $
c  
 



Customer and vendor accounts are sub ledger GL's. We will have to create two
reconciliation GLs in viz. Reconciliation GL for Customer and Vendor in chart of
accounts.

After, while creating customer and vendor master records, we have to mention
respective reconciliation GL in their company code segment details. This recon a/c
will show you the net balances in GL for customer and vendor a/cs.

Without creating Vendor you can still create individual GL for each customer and
vendor , but then
1) Your list of GL's in chart of account will be very lengthy.
2) Duplication of work as SD/ MM people are also required to create their own list.
3) Cross company code consolidation will not be possible as the chart of accounts will
be different.
4) Very difficult to keep track of individual customer/ vendor a/cs.
5) Not advisable even in real time accounting system i.e. manual book keeping. *-
- Mahajan

 0(0      "1


 
 6 
  
*  





To set up Electronic Bank Statements (EBS)

Processing in SAP for most customers in North America.

1. Create House Bank and Account ID (FI12)

2. Setup EDI Partner Profile for FINSTA Message Type (WE20)

3. Configure Global Settings for EBS (IMG)


- Create Account Symbols
- Assign Accounts to Account Symbols
- Create Keys for Posting Rules
- Define Posting Rules
- Create Transaction Types
- Assign External Transaction Types to Posting Rules
- Assign Bank Accounts to Transaction Types
4. Define Search String for EBS(Optional)
- Search String Definition
- Search String Use

5. Define Program and Variant Selection

Additional information is also available in the SAP Library under:


Financial Accounting > Bank Accounting (FI-BL) > Electronic Bank Statement >
Electronic Account Statement Customizing.

&ь (


* 




The following are the steps for BRS:

Create Bank Master Data - This can be created through T.Code FI01 or you can also
create the house bank through IMG/FA/Bank accounting/Bank account

2. Define House Bank

3. Set up Bank selection payment programe- IMG/FA/ARAP/BT/AUTOIP/PM/Bank


selection for payment prg.

a. setup all co codes for payment transaction - Customer and vendors

b.setup paying co codes for payment transactions

c.setup payment method per country

d.setup payment method per co code for payment transaction

e.setup bank determination for payment transaction

Please go for Cheque mangement using T code FCHI


(IMG/FA/ARAP/BT/OP/AutoOp/PaymentMedia/CheckManagement) and for void
reasons FCHV. You can create Bank Reconcilliation statement by TC FF67
(SAP/AC/Treasury/CashManagement/Incomings/ManualBankStatement) . Don't
forget to keep the opening Balance as zero. Use FBEA for post process.

All the steps together will lead to (FF67) Bank reconciliation statement.

6- 
 

 
&Ñ *A"# *
c  

  

The purpose of Recon Ledger is to display the summarized balances of cost ledger. It
is a ledger used for summarized display of values that appear in more detailed form in
the transaction form. It has the following functions:

1) Reconciles controlling with Financial accounting.


a) The recon ledger provide the reports for monitoring the reco of CO with FI by
accounts.
b) It can identify & display value flows in Controlling across Company codes,
functional area or business area boundaries.
c) Value flows can be used in FI as a basis for summarized reco. postings.

2) Provides an overview of all costs incurred.


Updation of Recon ledger can be done online or periodically. To update online, you
need to activate the recon ledger. For periodical updation, proceed as follows :
a) During month end, activate the recon ledger. (T Code-KALA)
b) Do follow up postings.
c) Deactivate the Recon ledger. (T Code-KALB).

6"# "Ñ ÑŒÑ#  62!66C+ 63

When you need to drill back from the FI G/L to find which cost center was Posted to
on an expense account, the reconciliation ledger is accessed.

The need to have a CO to FI reconciliation process is a result of cross company Code,


cross-business area, or cross functional area activity that may occur in the CO module.
Order settlement or confirmation, cost center assessment, or other internal CO
movement may initiate these postings. When costs moved internally within CO, the FI
G/L is not updated because of CO use of secondary Cost elements to facilitate the
postings.

The first two steps in reconciliation ledger configuration are to activate the Ledger
within the controlling area and assign a document type. If you have an Existing
controlling area that does not have the reconciliation ledger activated.

Activate the reconciliation ledger:

Controlling -> Overhead Cost Controlling -> Cost and Revenue Element ->
Accounting -> Reconciliation Ledger -> Activate Reconciliation Ledger (KALA)

6"# "Ñ ÑŒÑ#  62!66C+ 6ÿ


A good receipt posting of Rs.100 has occurred on internal order 1, which is assigned
to company code

One hundred percent of the value of internal order No.1 is settled to internal order 2.
Which is assigned to company code 2.

A Settlement cost element is used for the settlement posting. When an order
Settlement is run, internal order 1 is credited with Rs.100 and internal order 2 is
debited with Rs.100. The balances of internal order 1 and internal order 2 are 0 and
Rs.100, respectively. However, the balances of company code 1 and 2 remain as they
were prior to settlement. The reason: settlement activity was internal to CO. No FI
update occurred.

To place the FI company codes back in balance, the CO-FI reconciliation posting
transaction should be run. The resulting FI postings would credit company code 1 for
Rs.100 and debit company code 2 for Rs.100. The internal CO activity will now have
been accounted for in FI and company codes are now in balance.

2 
 


&Ñ

Ñ $  ( 


 (   
 *    
  
  
 )c 
 
 
$  ( ( (  
  
,
  

      
 (      ! 

    $  
   (       

 

  0 *
  
  Π  
      !  ) Ñ 
G   

 

 (  
ÿ ((  

 (0  
 
  )

  
(
 ! ,   
  
 
 
 )

Customer and Vendor accounts are maintained in a subledger. Posting to these


accounts will also be posted to the A/R and A/P reconciliation accounts. All
Reconciliation accouints are GL accounts.

All G/L accounts are not reconciliation accounts.

Why is this done?

In large businesses, there will be hundreds/thousands of customers/vendors. All these


are personalaccounts (there are three types of accounts: nominal, personal and real).
These personal accounts are grouped in to sub-ledgers and any posting to them is
reconciled to the G/L
via the reconciliation accounts.

*

For fulfilling completing the double entry system accounting the Reconciliation
accounts i.e., Accounts Receivable and Accounts Payable are used. All the Vendors
are grouped under Acounts Payable & Customers are grouped under Accounts
Receivable. And also always any time the balance in reconciliation account shows as
zero.

Ex: 1) Vendors transaction:


For Invoice posting:
Inventory A/c Dr
To Vendor A/c................Accounts Payable A/c (Reconciliation Ledger)
(In SAP since we are linking in the G/L Master Accounts Payable with the
Reconciliation Accounts type setting as Vendors. Hence, with one entry 3 Accounts
are automatically updated)

Accounts Payable is Liability & Inventory is Current Assets.


For Payment to Vendor:
Vendor A/c Dr.....Accounts Payable A/c
To Bank/ Cash A/c

Ex:2) Customer Transaction:


Sales Invoice Posting:
Customer A/c Dr...Accounts Receivable A/c (Reconciliation A/c)
To Sales A/c

Receipt Posting:
Bank A/c Dr
To Customer A/c...........Accounts Receivable A/c

In Normal Accounting the Reconciliation Accounts are called as Control Accounts


and we pass 2 entries for each transaction i.e., Sale, as following:
1) Customer A/c Dr (Sales Ledger / Accounts Receivable A/c)
To Sales A/c (General Ledger)
2) Accounts Receivable A/c Dr (General Ledger)
To Customer A/c (Sales Ledger Adjustment A/c)
Hence, any time the Control A/c balance is zero.

I hope I am clear and now your confusion problem gets resolved.

 *

These are basic accounting differentiation for different types of accoutns. This is a
basic accounting concept and is not specifically mentioned anywhere in SAP
terminology.

Personal accounts:

Accounts in the name of individuals, organizations etc.


For example, Company A A/c, XYZ limited co A/C, Suresh A/C, Indian Bank A/C
etc

Real Accounts:

These are accounts related to assets, both real and tangible.


example, furniture a/c, machinery a/c, accounts receivables a/c etc

Nominal Accounts:

These are related to incomes/expenditures and profit/losses.


for example, sales A/c, salary a/c etc

I hope this clears your doubts

c ΄



c 

 $


c     "


  Ñ

 
 .   
    

( *


Real time integration is nothing but the data posting to all the affected areas instantly
when an activity is performed. For E.g. When you do a FI-SD integration, when a PGI
is posted, the following entry is affected :

1. Cost of Goods Sold Dr 100


To Inventory Account Cr 100
Here the Cost of Goods Sold is an FI entry and Inventory Account related to MM but
both of them gets affected immediately when you post a PGI in SD.

The updation of these entries when PGI is done is called Real Time Integration. The
affect is shown in all FI, MM and SD modules once you save the entry.

The configuration for the below entry is done in OBYC

1. Cost of Goods Sold Dr 100 (T-Key GBB)


To Inventory Account Cr 100 (T-Key BSX)

The automatic entries are posted to inventory accounts through T-keys to which GL
accounts are assigned. These T-keys are assigned to movement types in MM. Please
refer to T-code OMWN and OMWB for proper understanding.

"

     

 &Ñ '



c           
c   


 *

We are using the Special Purpose Ledger for statutory reporting or mangement
reporting purpose. It also help us in doing single entry, adjstment posting like income
tax deperication.

Steps for cofig.


- Define Table Group
Financial Accounting -> Special Purpose Ledger -> Basic Settings -> Tables ->
Definition -> Define Table Group

- Maintain Field Movement


GCF2
IMG Menu Path :
Financial Accounting -> Special Purpose Ledger -> Basic Settings -> Master Data ->
Maintain Field Movements

- Maintain Ledger for statutory ledger


GCL2
IMG Menu Path :
Financial Accounting -> Special Purpose Ledger -> Basic Settings -> Master Data ->
Maintain Ledgers -> Copy Ledger
Assign Co Code
Assign Activities

- Define Versions
GCW1
IMG Menu Path :
Financial Accounting -> Special Purpose Ledger -> Periodic Processing -> Currency
Translation -> Define Versions

- Set Up Exchange Rate Type


OC47
IMG Menu Path :
Financial Accounting -> Special Purpose Ledger ® Periodic Processing -> Currency
Translation -> Set Up Exchange Rate Type

- Create Number ranges


GC04
IMG Menu Path :
Financial Accounting -> Special Purpose Ledger -> Actual Posting -> Number
Ranges -> Maintain Local Number Ranges

- Create Currency Translation document type


GCBX
IMG Menu Path :
Financial Accounting -> Special Purpose Ledger -> Actual Posting -> Maintain Valid
Document Type

- Create Posting period variant


GCP1
IMG Menu Path :
Financial Accounting -> Special Purpose Ledger -> Actual Posting -> Posting Period
-> Maintain Local Posting Period

c . 
*
2 


.  2 
 It is for short term and is used when tranaction Dr or Cr is
uncertained and generally its is used for external purpose. eg: Advance from potential
customer

*
2 
Its is for longer period generally used for internal purpose. eg:
Advance made for employes.
c  
     
)c 
 

&Ñ
.

Parking documents is used when we need to get any clarification regarding some
account.

We can temporarily park or store this document till we get it cleared or approved.

Then we can post it.

Remember.... parking does not update the accounts....... it just stores the document.....
whereas posting will update the accounts....( for example.... the reducing/increasing of
the account balances).

The TC for Parking Documents is F-02 -> enter the required details ->go to the menu
(at top ) ->Document-> Park.

To post a parked document : FBV0-> go to the menu Document-> Post.

Other TCs used pertaining to Parking of Documents are :

FV50 : Post / Delete : Single Screen Transaction


FBV2 : Change
FBV3 : Display
FBV4 : Change Header
FBV5 : Display Changes
FBV6 : Refuse

 &Ñ Œ  (  = *




&07*2 
0#



  
 )

$ 

Ñ
 &07,      *(- #
 
 
 
  
 ) 
$ ,
 Ñ *
            *(- A 
    

   *(-)

"Only transfer amounts in document curr. in invoice"

If we sets this indicator it translates the doc. currency into local currency at the time of
parked document.
If we not set this indicator it translates the doc. currency into local currency when
posting of document.

Eg: We are parking a document with doc. currency in USD @40- the next day we are
posted that document then it is @42- the system takes the exchange rate from the
header which was specified in the parked document @40- only. If we not set this
indicator it will take at the time of posting of document @42-

2
(

H
& =


c  & =


)c / 

c   
(

H=

& =
)
c  (     
  /   
  (  
    ) c 
     
   )

'Posting Key Variant ' Controls- fields of Posting Key and 'Field Status Variant'
controls fields of G/L Account.Fields of G/L Account which are controlled by FSV
can see in T.Code OBC4 and Fields of Posting Keys in SPRO-FAGS-Document- Line
Item. Both can controls common fields, then SAP applies 'SDRO' rule.

2#)Π  
(  ,2  ,/ ,# 
)

Posting is key controls


- which type of accounts can be posted to
- whether the line item is debit or credit
- and the field status of the document line item

Where as FSG (group into Field status Variant) controls only the the document line
item for that account.

There are only three field status options during document entry:
- Suppressed
- Required
- Optional

If both Posting key and FSV has the same field as Required and optional, system uses
the link rules, takes the one which has the highest priority(in this case required).

But in case of Master record Field status which is controlled by Account Group, there
are 4 options of field status:
- Suppressed
- Display
- Required
- Optional

Account group defines:


a. length of gl account number
b. no. ranges of the gl account numbers
c. field status of the GL account master data in the company code segment.(which
fields to appear when you create a gl account) (to control...double click on your GL
account group in Screen transaction code OBD4)

Posting key defines:


a. whether the line item is a debit or credit
b. to which type of account the amount should be posted to(ex: when you use posting
key 40, you will be able to post to gl accounts. When you use Posting key 01, you
will be only able to post to customer account.
c. document screen layout during posting of a document. (which fields to appear in a
document...double click on the posting key and select field status and make the entries
as required /optional etc)

Field status group defines:


Document screen layout during posting of a document. (which fields to appear in a
document...double click on the field status group and select fields and make the
entries as required /optional etc)

LOGIC: you assign field status variant to the company code, FSV is a bundle of field
status groups.

ex: in FSG G001 you have made the text as required entry...you assigned the field
status group g001 to cash account..so when you use cash account and try to post a
document it will definitely prompt you to enter the text (text made as required.)

Both FSG and PK control the same feilds in a document.There is no dominance


between FSG and Posting keys..but we should know the allowed combinations....

If text is made required in PK and suppressed in FSG..the system will issue a error
msg..Rules for PK...and FSG....is set incorrectly for SGTXT field.

Permissable combinations:

Pk R/S O/S R/o R S O


FSG S/R S/O o/r R S O

Result e SD RD NP NP NP

R = required
s = suppressed
e = error
SD = Suppressed dominates
Rd = required dominates
np = no problem.

=
ŒŒ !  



During various postings, the GL account postings will be taken place as follows:

For Domestic Procurement of Raw Material


During GR
Material Stock Dr.
GR/IR clearing Cr.
During Excise Invoice Credit
Cenvat Account Dr.
Cenvat Clearing Cr.
During Invoice Verification
Cenvat Clearing Dr.
GR/IR Clearing Dr.
Vendor Payable Cr.

For Domestic proceurement of Capital Goods


During GR
Material Stock Dr.
GR/IR clearing Cr.
During Excise Invoice Credit
Cenvat Account Dr. (50%)
Cenvat On-hold Dr. (50%)
Cenvat Clearing Cr.
During Invoice Verification
Cenvat Clearing Dr.
GR/IR Clearing Dr.
Vendor Payable Cr
Subsequent of Capital Goods
Cenvat Account Dr. (50%)
Cenvat On-hold Cr. (50%)

For Import Procurement of Raw Material


During Customs Duty Clearing invoice
Custom Clearing Dr.
Custom Payable Cr.
During GR
Material Stock Dr.
GR/IR clearing Cr.
During Excise Invoice Credit
Cenvat Account Dr.
Custom Clearing Cr.
During Invoice Verification
GR/IR Clearing Dr.
Vendor Payable Cr.

For Excise Duty Credit of Raw Material without PO

Cenvat Account Dr.


Cenvat Clearing Cr.

For Excise Duty Reversal through Excise JV

Cenvat Clearing Dr.


Cenvat Account Cr.

During Excise Invoice Creation


Cenvat Suspense Account Dr.

Cenvat payable Cr.

For TR6C Challan


PLA Account Dr.
PLA on hold Account Cr.

During Fortnightly Utilization


Cenvat payable Dr.
Cenvat Account Cr.
PLA Account Cr.
c 2(

" 


2(+ - It is a sales document used in complaints processing to request a debit


memo for a customer. If the prices calculated for the customer were too low, for
example, calculated with the wrong scaled prices, you can create a debit memo
request. The debit memo request can be blocked so that it can be checked. When it has
been approved, you can remove the block. It is like a standard order. The system uses
the debit memo request to create a debit memo.

" + - A transaction that reduces Amounts Receivable from a customer is a


credit memo. For eg. The customer could return damaged goods. A debit memo is a
transaction that reduces Amounts Payable to a vendor because, you send damaged
goods back to your vendor.

Credit memo request is a sales document used in complaints processing to request a


credit memo for a customer. If the price calculated for the customer is too high, for
example, because the wrong scale prices were used or a discount was forgotten, you
can create a credit memo request. The credit memo request is blocked for further
processing so that it can be checked. If the request is approved, you can remove the
block. The system uses the credit memo request to create a credit memo.

As mentioned above, creating a credit or debit memo request enables you to create
credit or debit memos based on a complaint. For this first create a sales document with
the order type for a credit or debit memo request. You can create the debit or credit
memo requests in the following ways:
± Without reference to an order
± With reference to an existing order
Here you enter which order the complaint refers to.
± With reference to an invoice
Here you enter which invoice the complaint refers to.
In all cases, you specify the value or quantity that should be in the credit or debit
memo

You can block the credit or debit memo request from being billed in Customizing. Go
to Sales -> Sales Documents -> Sales document header -> Define sales document type
and select the billing block field in the billing section. This request can later be
reviewed along with similar ones, - if necessary, by another department. The request
for a credit or debit memo can then be approved or rejected.

Π "   2( + /


- Use the same procedure that you use for Creating Sales Orders i.d T Code VA01
- Give Order Type as CR for Credit Memo and DR for Debit Memo reuest
While creating the request you have to enter Customer Number, Reason for the
request. and Material and its quantity. Once the credit or debit memo request is
released you can create credit or debit memo. The credit memo request will be
automatically blocked for checking with Billing Block 08 (to check credit memo) &
09 (to check debit memo) for the sales order type ³CR´ .

If it is not so you can customize the block for credit memo requests in Customizing
for SD when you define the order type Sales and Distribution -> Sales -> Sales
Documents -> Sales Document Header -> Define sales document types. The release
of block is allowed to be removed only by the people who are authorized for it. If the
amount is within acceptable limit the block is automatically released otherwise all the
people assigned to this job receive a work item in their integrated inbox for release.

If the complaint is not automatically blocked by the settings in Customizing, you can
set a delivery or billing block manually.
- Logistics -> Sales and distribution -> Sales.
- Choose Order -> Change.
- Enter the number of the sales document, or use a matchcode to search for it.
- Choose Enter.
- If all the items have been blocked, choose Select all.
- If only some items should be blocked, select the corresponding items.
- Choose Edit -> Fast change of... -> Delivery block or Billing block.
- Enter the delivery or billing block for the header or individual items.
- Choose Copy.
- The system copies (or deletes) the delivery or billing block in all the selected items.
- Save your document

  



!  


c       



&)Ñ    

- 
 
    ) Ñ
  
   
  
 
)  Ñ  

We define Sample account at OB15 and the path is SAP Ref:


IMG\Financial
Accounting\GLAccounting\GLAccounts\MasterRecords\Preparations\Additional
Activities\Sample Accounts

 3+

  

In this step you just create a code for your Sample Account
Create a New Entry
XXXX Sample account for Pleasecontact1 then save

 ÿ2
2Œ
&Hÿ

In this step you define the data tranfer rule i.e., whether it can be editable or only
display etc after a Master recored is created with Sample Account.

Selects the fields that you want to transfer (check boxes)and can be changed and can't
be changed etc., then save.

 
" 
" Π

In this step you will assign your sample account to your company code.

Just select your company and select your Sample account and assing then save.

 4"  


)&+3

Now create Sample Account same as you create at FS00, then Save.

Now Sample account is created. Now you can find Sample account field in FS00 (if
you assign it company code it won't be displayed) enter Sample account no, and press
enter all the fiels that you have selected in Step 2 will be copied (transferred) accrding
the the rule (checkboxes) you have selected there.

Π &

At FS00 you can see/Edit/Create a GL Master Record which is maintained by the


Company Code. Where as Sample Account is not GL Master Record but it is a set of
settings/rules which are easily available to create a GL Master Record (understand this
point clearly) This sample account does not hold your transaction data nor you can
edit or view at FS00.

To use your Sample Account:


1. Go to FS00, give a GL account no (other than Sample account no ofcourse). Select
create
2. Then check all fields, whether any field is filled like Currency, Open Item
Management, etc *for your confirmation* (obviously every field is empty)
3. Now enter Sample Account no in Sample Account field and give Account Group.
press Enter. U will get a message that "Data from changed Sample account was
accepted", check data.
4. Now chek all fields again. Now u will find some fields filled with values which you
have defined in Data Transfer Rules while creating Sample Account.

"

 & 
! "

6- 
    
!  
)

By : Naidu

Check all the configuration steps for preparation of GL a/c:

1. Define company T.code ox15 (its is necessary for consolidation purpose)

2. Define Company code t.code ox02

3. Assign company code to company t.code ox16

4. Edit chart of account t.code ob13

5. Assign company code to chart of account t.code ob62

6. Maintain fiscal year variant t.code ob29

7. Assign company code to fiscal year variant t.code ob37

8. Define posting period variant t.code obbo

9. Open and close posting period t.code ob52

10. Assign posting period variant to company code t.code obbp

11. Define document type and number range t.code oba7

12. Define field status variant t.code obc4

13. Assign company code to field status variant


Go to SPRO --> Financial accouting -> Global settings --> Select your company
code and double click. You can see the field status variant field there.

 
Œ   &&Ñ  2("


.  
(  (
&Ñ 

By: Prakash Sharma

Π      ( 

0

Define Methods: SPRO / Financial Accounting / Accounts Receivables & Payables /


Business transactions / Closing / Valuate / Reserve for bad debts
- OB04
- Double click define methods
- Select New entries button

Prov Period Months Percent1 M Percent2 M Percent3 M


Percent4
SAI 1 10 2 20 3 30 4 100
Save
Creation of Bad Debts Account: FS00

Co.code: XXXX
- Select with template button G/L A/c:XXXXXX Co.Code : XXXX
Account group: Administration
- Select P & L Radio button
Short text: Bad debts Long text: Bad debts
- Select control tab button Current currency: INR
- Select only local currency check box
- Select line item check box, Sort key:001 Field status variant:
G001
- Save

Define Accounts for Reserve & Bad Debts:


- OBXD

SPRO / Financial Accounting / Accounts Receivables & Payables / Business


transactions / Closing / Valuate / Define Accounts for Reserve & Bad debts
Chart of Accounts: XXXX

PROVISION METHOD DEBIT CREDIT


XXX XXXXXX XXX XXX
Select rules tab button Accounts are determined based on
- Select Debit/Credit check box 40/50
- Select provision method check box
- Save

Special G/L Account:


- FBKP

Double click Special G/L


Account Type Special G/L Special G/L Indicator Description
D E Reserve Reserve for Bad debts

Double click Reserve


- Chart of Accounts: SAI (Enter)
Account Assignment
Reconciliation A/c:XXXXXX (SD) Spl.G/L-XXXXXX Save

Receivable Transfer posting (Gross):


- F103

Accounting / Financial Accounting / Accounts Receivable / Periodic processing /


Closing / Value / Receivable transfer posting (Gross)

Customer A/c:XXXXXX Provision method: XXXX


Special G/L Indicator for Debit Rec: E (Reserve for bad debts)
- Select create batch input session check box
- Batch input session name: SAPF103
- Posting Key:09 Posting document: DA
- F8
From the menu Select -> System -> Batch Input -> Session
- Select batch input session: SAPF103 Select process
- Select display errors only V
- Select process button
- Exit Batch input

Reserve for bad debts (Gross):


Customer A/c:XXXXXX Co.Code: XXXX G/L Account: XXXXXX Co.code:
XXXX
Accounts group: reserves and surplus
- Select balance sheet option button
Short text: Provision for Bad Debts Long text: Provision for bad debts
A/c Currency: INR Rec.Accounts for account type: Customer
- Select line item display check box
Sort key: 031 Field status group: G067
- Save

c Ñ !
   



6Ñ
OOP&Ñ"#

Π (


 ! 
6- 
 
! 

General Ledger Accounting (FI-GL) (New)

The central task of G/L accounting is to provide a comprehensive picture of external


accounting and accounts. Recording all business transactions (primary postings as
well as settlements from internal accounting) in a software system that is fully
integrated with all the other operational areas of a company ensures that the
accounting data is always complete and accurate.

Beyond fulfilling the legal requirements, General Ledger Accounting also fulfills
other requirements for modern accounting:

- Parallel Accounting

General Ledger Accounting allows you to perform parallel accounting by managing


several parallel ledgers for different accounting principles.

- Integration of Legal and Management Reporting

In General Ledger Accounting, you can perform internal management reporting in


parallel with legal reporting. For this purpose, the Profit Center Accounting functions
are integrated with General Ledger Accounting. Furthermore, you can generate
financial statements for any dimension (such as profit center).

- Segment Reporting

General Ledger Accounting supports the segment reports required by the accounting
principles IFRS (International Financial Reporting Standards) and US GAAP
(Generally Accepted Accounting Principles). For this purpose, General Ledger
Accounting contains the Segment dimension.

- Cost of Sales Accounting


You can perform cost of sales accounting in General Ledger Accounting. For this
purpose, General Ledger Accounting contains the Functional Area dimension.

Features
General Ledger Accounting comprises the following functions for entering and
evaluating posting data:

- Choice between group level or company level

- Automatic and simultaneous posting of all subledger items in the appropriate general
ledger accounts (reconciliation accounts)

- Simultaneous updating of the parallel general ledgers and of the cost accounting
areas

- Real-time evaluation of and reporting on current posting data, in the form of account
displays, financial statements with different balance sheet versions, and additional
analyses.

In this way, General Ledger Accounting automatically serves as a complete record of


all business transactions. It is the central and up-to-date component for reporting.
Individual transactions can be checked at any time in real time by displaying the
original documents, line items, and monthly debits and credits at various levels such
as:

- Account information

- Journals

- Totals/transaction figures

- Balance sheet/profit and loss evaluations

However, SAP still offers to choose between the New GL and the old Classic GL way
of accounting.
There are certain limitations in the new GL and clients are adopting to the new gl
concept.

 
2 
 
&$(
 !
  

c      


  $( 
  !
      
$( $
6""5)
 

By: Manjeera

Ñ


2 
 


You can use the document splitting procedure to split up line items for selected
dimensions (such as receivable lines by profit center) or to effect a zero balance
setting in the document for selected dimensions (such as segment). This generates
additional clearing lines in the document. Using the document splitting procedure
ensures that you can draw up complete financial statements for the selected
dimensions at any time.

You can choose between displaying the document with the generated clearing lines
either in its original form in the entry view or from the perspective of a ledger in the
general ledger view. For document splitting to be possible, the individual document
items and the documents must be classified. Each classification corresponds to a rule
in which it is specified how document splitting is to occur and for which line items.

SAP delivers a set of standard rules that should usually prove sufficient. If not, you
can define your own set of rules and adapt these according to your needs.

6-  3 Ñ


$ 
Suppose a vendor invoice containing the following items is entered:

Posting Key Account Segment Amount


31 Payables -100
40 Expense 0001 40
40 Expense 0002 60

Document splitting then creates the following document in the General Ledger view:

Posting Key Account Segment Amount


31 Payables 0001 -40
31 Payables 0002 -60
40 Expense 0001 40
40 Expense 0002 60
Example 2: Payment
The payment for the above vendor invoice then contains the following items when
entered:

Posting Key Account Segment Amount


50 Bank -95
25 Payables 100
50 Cash Discount Received -5

Document splitting then creates the following document in the General Ledger view:

Posting Key Account Segment Amount


50 Bank 0001 -38
50 Bank 0002 -57
25 Payables 0001 40
25 Payables 0002 60
50 Cash Discount Received 0001 -2
50 Cash Discount Received 0002 -3

%


 

2$"Ñ
 *
!  


3: Ñ Ñ 



   
 

 &3  &ÿ  
 
   ,  

(/
Ñ  

  $ 
, ,  

Ans: Yes.

Planned delivery cost --- Maintain FRA1 and FRA2 in PO Details with same or
different vendor.

Select Goods receipt/service +planned delivery

ÿ:

  $ 

  c (  

Ans: If you want to see other costs, then choose Goods items+planned delivery costs

:c 


  $ 
  


Ans: In MIRO, after entering PO as a reference, choose delivery tab in header and
enter any unplanned delivery costs amount in the field Unplanned dely costs. You can
customize to post the unplanned dely costs to separate G/L Account or stock account.

Enter MIRO --Header details ----Enter unplanned delivery cost.


---

Planned delivery costs, if you want to capture for different vendor in PO than go to -
Conditions in item level, select the delivery condition to be captured and go to
condition detail wherein you can mention different vendor to capture delivery cost,,

In MIRO Transaction Select Delivery tab.

If you are posting the Delivery costs & Other costs as Unplanned delivery cost.

Unplanned delivery costs are posted in a separate line. You must enter a specific tax
code for the posting.

Maintain in MIRO ---Transaction Enter unplanned delivery cost.

While doing MIRO, in the header ( details tab ) there is a field for Unplanned delivery
cost ( Unpl. Del. Csts ). Here you can enter extra delivery charges that are not in the
conditions on the Purchase Order.

---

Unplanned delivery costs are delivery costs that were not specified in the purchase
order and are only entered when you enter the invoice. They are posted in exactly the
same manner as subsequent debits/credits.

For a material subject to moving average price control, unplanned delivery costs are
posted to the stock account, provided that there is sufficient stock coverage. For a
material subject to standard price control, unplanned delivery costs are posted to a
price difference account.

Unplanned delivery costs were not agreed on in the purchase order and are not entered
until the invoice is received.

You can enter the unplanned delivery costs in the invoice document alongside the
costs incurred. You can post unplanned delivery costs as follows:

Distribute them prorated to calculated invoice items

Post them to separate G/L accounts

You can use the Business Add-In MRM_UDC_DISTRIBUTE to define your own
rules for distributing unplanned delivery costs. For more information, see the
documentation for the Business Add-In
You want to distribute unplanned delivery costs prorated when you post the
document. - (Incoming Invoice-- Posting Unplanned Delivery Costs).

You want to post unplanned delivery costs to a separate G/L account. - Incoming
Invoice ® Maintain Default Values for Tax Codes.

Planned costs are costs which are entered directly in the PO.

Planned delivery costs are agreed upon with the vendor, a carrier, or a customs office
before the purchase order is created. You enter them in the purchase order.

Planned delivery costs can be differentiated as follows:

u Origin of Costs
u Freight charges
u Customs charges
u Calculation of Costs
u Fixed amount, irrespective of delivered quantity
u Quantity-dependent amount
u Percentage of value of the goods

2
 
# 
Ñ
# 
Ñ+



u c   
(
 

 



u Open item: open item is an item which has to be cleared with another line item.
u Open item management: how you want to manage all the open item in particular
GL A/C.
u Open item management is the setting which allows the setting to maintain the open
items for the particular GL account.
u Use of open item : Processing open items involves choosing and then activating
the open items. Processing is the last step before posting a clearing document.
When posting clearing documents, the system takes tolerances into account.
Tolerances are acceptable payment differences.
u When the line item(s) you enter and the open item(s) you process have been
cleared, you can post a clearing document.
u For example, if you enter a vendor payment for $1000, you must choose and
process vendor open items that equal $1000. If your system permits a 1%
tolerance, then you can clear open items with a value from $990 to $1010.
u When you process open items, you can:
u - Activate or deactivate open items
- Activate or deactivate cash discount
- Maintain cash discount amounts
- Enter partial payments or residual items
u  $  
(  )
u To process open items, on the screen for selecting open items, choose Goto -->
Open items.
u You can process open items using the following:
u - Menus or function keys
- Commands
- Mouse
u To clear open items with commands or with the mouse, you select and process an
item in one step.
u % 



u Defining "Open Item Management"
u If you set the "Open item management" indicator in the master record for an
account, the line items in this account is marked as open or cleared.
u The balance of an account with open item management is equal to the balance of
the open items. General ledger accounts are kept with open item management if
you need to check whether there is an offsetting posting for a given business
transaction.
u You should use open item management for bank clearing accounts, clearing
accounts for goods receipt/invoice receipt, and salary clearing accounts. Bank
accounts, however, do not use open item management.
u If you subsequently define open item management for a G/L account, this entry
only applies to the items which are posted afterwards. At the date of the change,
the account must display a zero balance.
u Also, when canceling this indicator, the balance must be zero. You therefore have
to clear the remaining open items before making the change in the master record.
u # 

u Take an example of misc. purchases.
u When you purchase from vendor you pass the following entry.
u Dr. Material / Expenses A/c.
Cr. Vendor account (if it is credit purchase)
u Now the vendor account is showing credit balance till you make payment to the
vendor. This in SAP they call is open item.
u While making payment
u Dr. Vendor account
Cr. Cash / Bank account
u If once you make the payment to vendor, while making the payment to the vendor,
you need to link the payment with lying open item of above purchase. System
automatically changes the status of above open item (red colour ball) to cleared
item (green colour ball) in the vendor account.
! # 
Ñ+



u Ñ $
   !Ñ 
     


 )  
* 
( 
 

$)Ñ(

)    



 
 
  


 
 
  

 -  
 !Ñ  
    )

.$  
,(   
 
"
 
)Π3,

 ).


 

 
)Ñ 
  

* 
)
u 

u For old line items, you can't enter. Before changing the account master for open
line item management the account balance should be 0 (ZERO). You can try
doing the following:
u 1. Pass one JV transferring the balance to some suspense account.
2. By doing above the balance will become 0 (zero). So change the account
master & tick on Open line item management.
3. Again pass the reversal entry of the first one.

For doing the above, you may have to first remove the tick of automatic line
item.

u    ! # 


Ñ+


u Any GL account has a balance standard SAP will not allow to change status to
open item managed, if the GL account is not an open item managed earlier. "Z"
Program (ZRFSEPA02) will make it an open item managed.
u We have created an OSS Message and SAP told us to copy RFSEPA02 to Z
program (ZRFSEPA02) and Follow the steps to enable Open Item Management
for GL accounts.
u   Q 3
Create a Dummy or Temporary clearing account to move balance from clearing
accounts.
Use T.code FS01

  Q ÿ
Move balance from clearing account (Ex: 113073) to Dummy account.
Post a journal entry using T.code F-02 or FB50.
u   Q 
Lock Clearing account for any postings.
Use T.code FS01 and Lock the account.
u   Q 4
Run Z program
To go T.code SA38 and enter program: ZRFSEPA02 and Execute.
Enter Company Code: 1000
GL account: 113073 and Execute (F8).
u   Q 5
Go to T.code FS01 and validate GL account Open Item Management check box
and unlock account for postings.
u   Q 7
Move balance from Dummy account to clearing account (Ex: 113073).
Post a journal entry using T.code F-02 or FB50.
u   Q 8
Validate Clearing account (Ex: 113073) and Dummy account balances.
Use T.code FBL3N
u   Q ^
Clear dummy account balance using T.code F-03
u Please execute each step carefully and follow aforementioned steps to convert
non open item management GL accounts to open item Management GL
accounts.

2!
   
AÑ! 

u $    

 A -      
  
 
A 
u By: Dasharathi Bejugama
u The central task of G/L accounting is to provide a comprehensive picture for
external accounting and accounts. Recording all business transactions (primary
postings as well as settlements from internal accounting) in a software system
that is fully integrated with all the other operational areas of a company ensures
that the accounting data is always complete and accurate.
u  
    $ 
 "  
?"#:
u COA is a list of all G/L accounts used by one or several company codes.
u For each G/L account, the chart of accounts contains the account number,
account name, and the information that controls how an account functions and
how a G/L account is created in a company code.
u You have to assign a chart of accounts to each company code. This chart of
accounts is the operating chart of accounts and is used for the daily postings in
this company code.
u You have the following options when using multiple company codes:
u You can use the same chart of accounts for all company codes If the company
codes all have the same requirements for the chart of accounts set up, assign all
of the individual company codes to the same chart of accounts. This could be
the case if all company codes are in the same country.
u In addition to the operating chart of accounts, you can use two additional charts
of accounts If the individual company codes need different charts of accounts,
you can assign up to two charts of accounts in addition to the operating chart of
accounts. This could be the case if company codes lie in multiple countries.
u The use of different charts of accounts has no effect on the balance sheet and
profit and loss statement. When creating the balance sheet or the profit and loss
statement, you can choose whether to balance the company codes which use
different charts of accounts together or separately.
u "  
 
 $  



 
u # 
  

u The operating chart of accounts contains the G/L accounts that you use for
posting in your company code during daily activities. Financial Accounting and
Controlling both use this chart of accounts.
u You have to assign an operating chart of accounts to a company code.
u !   

u The group chart of accounts contains the G/L accounts that are used by the
entire corporate group. This allows the company to provide reports for the
entire corporate group.
u The assigning of an corporate group chart of accounts to a company code is
optional.
u "
0     

u The country-specific chart of accounts contains the G/L accounts needed to
meet the country's legal requirements. This allows you to provide statements
for the country's legal requirements.
u The assigning of an country-specific chart of accounts to a company code is
optional.
u You can find the function for creating G/L account master records in Financial
Accounting Customizing under General Ledger Accounting -> G/L Accounts -
> Master Data -> Creating G/L Accounts.
u Create your G/L accounts.
u You have two options:
u If you want to use a chart of accounts included in the standard system as a
reference, or if a chart of accounts is already in your system, use the create with
reference method. To do this, use the Create G/L Accounts with Reference
activity.
u You can copy the G/L accounts and the related account assignments. Before
creating the G/L accounts, you can change the account numbers and names.
u If you have G/L accounts in a non-SAP system, you can transfer these G/L
accounts to your SAP System. To do so, select the Data Transfer Workbench.
u You can modify the G/L account master records that were created or
transferred.
u The following functions are available for doing this:
You can carry out systematic changes to multiple G/L accounts, such as
changing the P&L account type of several P&L accounts. To do so, select the
desired function under Change G/L Accounts Collectively.
u You can change the master record of a single G/L account. To do so, select the
desired function under Edit G/L Account.

= Œ"
2




u c  


 
u Dunning is nothing but payment or collection remainder.

The SAP Financial Accounting component is delivered with the dunning


procedure and all further specifications for dunning. Check whether you can
use the predefined settings or whether you have to make changes. Assign the
required dunning procedures and areas (if used) required to your business
partners.

The most important thing that differentiates the dunning levels is the dunning
texts. The dunning text defines the urgency of the dunning notice. The other
things can be the dunning charges, minimum & maximum amounts etc.

Maximum no. of dunning levels is 9 levels.


u ."
2



u The dunning wizard enables you to create and send letters to customers that
have not paid their debts within a given time range and to remind them of their
overdue payments.
u In addition, the dunning wizard keeps track of a customer¶s "payment
behavior" in the database to deliver this important information to appropriate
organizations.
u The dunning wizard considers the following transactions and documents:
u 1. Open A/R invoices (including partially paid and partially credited)
u 2. A/R credit memos
u 3. Manual journal entries with at least one row posted to a customer
u 4. Opening and closing balance transactions
u 5. Incoming payments
u To access the wizard, choose Sales ± A/R Dunning Wizard .
u To run the Dunning Wizard, you have defined the dunning levels and the
dunning terms as follows:
u 1. You have defined the dunning levels by choosing Administration > Setup
Business Partners > Dunning Levels.
u 2. You have defined dunning terms in Administration > Setup> Business
Partners > Dunning Terms. The dunning terms are based on dunning levels,
and contain parameters and values required for the dunning process run.
u 3. You have defined the default dunning terms in Administration > General
Settings > BP tab > Default Cust. Dunning Terms .
u You have defined dunning terms for customers. (Choose Business Partners
Business Partner Master Data Payment Terms tab Dunning Term field.)
u You have used the following options to exclude any relevant A/R invoices from
the dunning process:
u - To exclude a specific invoice, display it before you run the wizard. On the
Logistic stab, select Block Dunning Letters. You can deselect the option later to
include the invoice in the future dunning process.
u - To exclude all invoices created for a specific customer from the dunning
process, display the Business Partner Master Data record for that customer. On
the Accounting tab, select Block Dunning Letters.
u Process:
u You choose Sales ± A/R > Dunning Wizard
u and follow the steps listed below. In each step you choose Next to proceed to
the next step of the Dunning Wizard, choose Back to return to the previous
step, or choose Cancel to cancel the Dunning Wizard creation
u Step 1: Wizard Options. You select whether to run a new Dunning Wizard or to
load a saved one.
u Step 2: General Parameters. In this window, you modify a name of the default
Dunning Wizard and choose a dunning level.
u Step 3: Business Partners ± Selection Criteria. You choose a range of customer
codes for the Dunning Wizard.
u Step 4: Document Parameters. In this window, you enter the range of the
posting dates to include in the Dunning Wizard. In addition, select the relevant
document types.
u Step 5: Recommendation Report. In this window, you enter a new due date and
select invoices that are included in the Dunning Wizard for each customer.
u Step 6: Processing. In this window, you select one of the following options to
process the Dunning Wizard:
u - Save Selection Parameters and Exit
u - Save Recommendation Report as Draft and Exit
u - Print Dunning Letter and Exit
u Result:
u If you print dunning letters, SAP Business One creates the dunning letters and
saves the dunning run. In addition, the dunning level and the last date of the
dunning letter are updated for invoices included in the dunning run. When a
dunning letter is created for a customer, the business partner master data record
is updated. On the Accounting tab, the Dunning Date field displays the date on
which the dunning letters were created for the last time.
u To view the history of dunning letters and the list of all invoices, choose
Business Partners > Business Partners Reports > Dunning History Report

2
 
 


2


"*

u '


c   
      
    
     




This is usually referred to depict the responsibility.

Accounting clerk you will find in G/L account master in FS00 who is assigned
responsibility to maintain and clear this account, he/she has track every
movement in the account.

Dunning clerk is the clerk who is responsible to dun the particular customer
and send notices.

Dunning Clerk is responsible for running the process of Dunning.

The name of Dunning Clerk is printed on Dunning Notice whereas the


Accounting Clerk is responsible for running the Automatic payment run
program and his name can be printed in foot notes of Payment cheques etc.

c 
 "
 Π  Π 

There can be scenario when both dunning and accounting clerk are same.
In some organization, the Accounting Clerk and Dunning Clerk may be same
but in system, there must be two separate persons but you can assign same IDs
and name.

"


You can configure the Dunning clerk in the same place where you had
configured the Accounting Clerk.

Both the field names are BUSAB, but Accounting Clerk is maintained in table
KNB1 and the Dunning Clerk from KNB5.

Master table for the both is T001S.


u "
 2+ 6- 
*
 

u . 
Ñ 
 2+ 6- 
*
 

. 
Ñ
*?&33: 
 A +Œ3(

 (
*
u When configuring the payment methods for the country (transaction OBVCU),
choose the payment medium program as &&#+3.
u From ^, pls read the documentation for the program, which will give you
the various options & the required config too.
u You would also need to configure the instructions keys as required.
u To generate the DME file, you have to run the automatic payment program
with this payment method.
u After the payments have been successfully posted, you can go to DME
administration and with the help of dme manager download files on your PC.
u SAP has determined that the standard print programs for automatic payments
will no longer be supported, and will be replaced by transfer structures created
by a tool called the DME Engine.
u This tool enables the business to create DME output files without ABAP
development, and can be attached to a print program and form for the creation
of Payment Advices.
u Outside of the DME Engine (DMEE), the majority of the configuration takes
place within the following IMG menu path:
IMG Path: Financial Accounting -> Accounts Receivable and Accounts
Payable -> Business Transactions -> Outgoing Payments -> Automatic
Outgoing Payments -> Payment Media -> Make Settings for Payment Media
Formats from Payment Medium Workbench
u "

Assign Selection Variants
IMG -> Financial Accounting -> Accounts Receivable and Accounts Payable -
> Business Transactions -> Outgoing Payments -> Automatic Outgoing
Payments -> Payment Media -> Make Settings for Payment Medium Formats
from Payment Medium Workbench -> Create / Assign Selection Variants or
transaction
u OBPM4..select your format that you are using
u Check in FBZP config that all is linked!
u Although this is bitty but you need to work through it!
u Start with FBZP, create all there than go to DMEE either to create your own
format or use the standard ones.. than go to the menu path above and work
through from create to assign...

 (
 OÑ
$  

u Through payment terms, you can set the baseline date=Invoice date.
u The payment term is entered in the Vendor Master Record and it will be
defaulted in +Ñ#.
u If payment term in Purchase Order is different from the Vendor Master Data, it
will have preference over the Vendor Master Data.
u & 5,& 7,   

(  
u On the first day of business after the basis people apply an upgrade to a kernel,
over the weekend, we lost visibility to the document numbers in the status bar
after we posted transactions & 5 and & 7.
u An OSS message was created and the reply was that it was an issue with a
kernel patch level.
u They refer us to OSS note 510815, and kernel patch level 1121.
u +Ñ# &Ñ  
  
4)7-
u When we upgrad to 4.6x, users was not willing to access the FI document
through Invoice display :-
u +Ñ4 -> Follow on documents
u I agreed with them because it is really troublesome to go through such a long
steps in order to find out the FI document number.
u In 4.6x, SAP only display the Invoice document number after posting.
u In order to display both the Invoice and FI document number at the same time,
you have to apply OSS notes ÿ3795 and 3ÿ3.
u You need to changed the programs in order to get the message

$ 2 

)A
&Ñ2 

)A  )"
u The following messages which were modified as per the OSS note to get the FI
document number.
u +

- #  -
060 Document no. & created
Invoice Document no. & and FI Document no. & created
u 075 Document no. & created (blocked for payment)
Invoice Document no. & and FI Document no.& created (blocked for
payment)
u 282 Document reversed with no. &: Please
manually clear FI documents (No change done in
the message text). But it will display FI
document number after changes.
u 392 Invoice document & has been posted (Now this
displays Invoice document number.
After changes,it will display FI document
number).
u After these changes you will be able to see the FI document number and
Invoice document number displayed in the message bar after executing
the +Ñ#Transaction.
u You will need authorizations and access key to do the modification.

2
 

,"



u Posting occurs with many different types of documents. It indicates that all
sides of the FI entry are in balance. Posting actually writes the document to the
G/L.
u Payment on the other hand is the actual issuing of a check. Payments can also
be processed in accounts receivable.
u In that case, you are posting (updating your books to reflect) the receipt of a
check from a customer and the deposit of said check in the bank.
u Accounts payable is processing the money your company owes to a vendor for
goods and services received. Account Payable is a liability on the balance
sheet.
u Accounts receivable is collecting the money that other companies/customers
owe you. It is an asset on the balance sheet.
u SAP is integrated. In most instances, there isn't a "link." The transaction
directly updates the tables involved. There is a semi-severance between
FI/Payment to allow checks to be issued even if there's a minor imbalance in
the FI side of the posting.
u Asset depreciation and physical inventory are some example that don't update
FI (CO/FM) as soon as the document is saved.
u Modules that appear in more than one place is caused by SAP trying to be
flexible in where it places things on its menu, so that different users/companies
find it easy to locate a given transaction within the confines of the module they
work in. This has become more pronounced since the change to role based
authorization management. That's why you can reach Create a
requisition from 4 different pathways, why Project Systems is in both Logistics
and FI, and why Travel Management is in both HR and FI.
u In some organizations, travel authorization and tracking is an HR function, in
some it is an FI function.
u 2
(
"


u     
  
 ,      
 (

3) 

00P&00P00P2 

00PÑ

 
P&0ÿ^


ÿ)  

00P&00P00P 
00P" &0ÿ 
   

(
&05
&044
)
u When you post a transaction, you will get a Accounting document. If you are
creating a payment document through F-53 or F-58 without linking the
Accounting document, than we have to create a link between the accounting
document and payment document and that can be done through F-32 (for GL)
and F-44 (for AP). An good example is when we make down payment, a
payment document is created. If we post the invoice, an accounting document
is created. To clear this payment document and accounting document, F-44 is
used.
u - F-28 will be used to make trasactions for income payments.
Eg: If you receive from a customer by using above T code will be passed
necessary entries.
- F-32 will used used for clear the Customer line items.
- F-53 will be used for making payments to vendors.
- F-44 will be used for clearing the Vendor Line items.
u =

  
    
u ----Original Message----
Subject: vendors not used within a specified period
u Hi,
u Wondering if any one can help me?
A while back I found a report which listed vendors not used within a
specified period i.e. list all vendors with no movement over the past 6
months. I can't seem to locate this report/programme?
u Regards
u -----Reply Message----
Subject: RE: vendors not used within a specified period
u Try report S_ALR_87010043 - Vendor Business. Within the report, under the
Output Control section, select the indicator "Accounts With No Purchases"
and run the report for the time period which you wish to evaluate. Hope
this helps
u -----End of Message-----
u 2
*" /

2 

u Ñ 
  
* /
( 3  
   45ÿ3)
Ñ 
  $   
   45ÿ3 
  
 
  
45ÿÿ
 ? 
*:  /
(3 
 

 45ÿÿ)
u Note the follwoing functionality :
u Cheque Voiding ( same as cheque cancellation as we call it )
u FCH3 - For unused Cheques i.e. cheques that are not yet assigned to Payment
docs.
u FCH9 - For issued cheques i.e. cheques assigned to payment docs.
u The above will only void the cheque and the payment doc will stand as it is.
After voiding the cheque the related payment doc can be reassigned to a new
cheque.
u If you reverse a Payment document itself ( T.Code FB08 ) then the system will
ask for a void reason if a cheque is already assigned. The voiding of cheque
will be done automatically if you reverse the payment doc and enter a void
reason code. You cannot reverse a payment doc that has been assigned a
cheuqes unless you enter a void reason code.
u There is a nother transaction available for Payment Cancellation - FCH8
u The cheque that has been voided is blocked for further use. If you still want to
use it you need to first delete the cheque information. T.Code FCHE.
u Also cheque related t.codes in this aspect. related T.Codes start with FCH* and
can be found in the Area Menu Cheque Information.


% +
A 


u Ñ 
  

) 
 (




  
 )   Ñ $  (
   3 

 (
*  
 
   Ñ  


    
 
)
Π
    
   35)   
 Ñ 
  

 
  
 $
 
  ) c       
()
u Ñ
 
$  $ $ 
)

*(
(
*
 
 
 
   ) Ñ   (
    
    


 
  (  )
u The Automatic Payment Program does not check the Balance of your Bank
Account.(GL A/c. Bal.)
u What it does check is the min & max amounts that you have maintained in your
customisation.
u In FBZP Transaction (type in easy access screen), you have to maintain the
config for your automatic payment runs.
u In Bank determination (in FBZP), you have to fill in the available amounts for
each Bank. This is the maximum amount up to which payments will be
generated by the Auto. Pay. Run.
u So if you want to ensure that on any single day the payment run does not pay
more than bank balance, you have to update on a daily basis available balance
to match with your bank balance .
u In SPRO you can find the customisation for A P Run, but FBZP is the old
transaction for the same thing. Plus it lets you do all the related customisation,
in one place.
u As far as I know, there is no direct way of linking your GL account balance to
the A P Run. *-- %

u Ñ 

  
  GG,
    
  
  
 ( G G 
   

  
    ( GG)  Ñ $ 

( 

  
)
u " /

 
u 3) & 0  
 
    Ñ $   
 
  



)
u ÿ)Ñ


 
,+ 
  ?
$ 

 
: 
   
    
  , G


   

  
  ). 
Ñ  )
u In Customizing Maintain Payment Program : Transaction code FBZP
1) define your company code'A" & "B" both in section tab (All Company
code)

2) Define Paying company Code for example "A" paying company

3) Payment Method in country in tab


Country IN (India) - Name of Country - Payment Method "C" is for Cheque
"D" for Demand Draft etc

4) Payment Method in Company code - for example "A" is paying company


define payment method in same section

5) In Bank Determination Section - define Ranking Order, Bank Accounts,


Available Amount, Value Date, Expences/ Charges

6) Define House Bank : HB Name , Account ID Bank Account Text,


While runing APP (F110) user should select paying Co Code "A" in maintain
variant, >00

  




c     $      


  A  


 

u %Œ#+ŒÑ" D+6 Œ #!+

1. Creation of House Bank:


SPRO-Reference IMG-Financial Accounting-Bank Accounting ± Bank
Accounts ± Define House Banks ± FI12
u 2. Creation of Cheques issue account in assets side with sort key 001 and FSV
is G005 and assign house bank and bank account no.
u 3. Creation of Cheque lots:
SPRO-Reference IMG- Financial Accounting ± AR/AP ± Business
Transactions ± Outgoing payments ± automatic outgoing payments ± payment
media ± cheque management ± Define no ranges for cheque management ±
FCHI
u 4. Giving mini and max amounts to payment:
SPRO-Reference IMG-Financial Accounting ± AP/AR-Business Transactions ±
Outgoing payments ± automatic outgoing payments program ± payment
methods/bank selection for payments program ± set up all company codes for
payment transaction ± T042
u 5. Set up paying company code for payment transaction:
SPRO-Reference IMG ± Financial Accounting ± AP/AR ± Business
Transactions ± Outgoing payments ± automatic outgoing payments program ±
payment method/Bank Selection for payment transactions ± set up paying
company codes for payment transactions ± 042B
u 6. Set up payment methods per country for payment transactions:
SPRO ± Reference IMG ± Financial Accounting ± AP/AR ± Business
Transactions ± Outgoing payments ± automatic outgoing payments ± payment
methods/bank selection for payment program ± TO42ZL
u 7. Set up payment methods per company code for payment transactions:
SPRO ± Reference IMG ± Financial Accounting ± AP/AR ± Business
Transactions ± Outgoing payments ± Automatic outgoing payments ± Payment
method/bank selection for payment program ± set up payment methods per
company code for payment transactions ± T042E
u 8. Set up bank determination for payment transactions:
SPRO ± Reference IMG ± Financial Accounting ± AP/AR ± Business
Transactions ± Outgoing payments ± automatic outgoing payments ± payment
method/bank selection for payment program ± set up bank determination for
payment transactions ± BA NKDET
u 9. Assign payment method to vendor Master record:
SAP menu ± Financial Accounting ± AP ± Master Records ± Change ± FK02
u 10. Automatic payment program running:
Sap Menu ± Financial Accounting ± Accounts Payable ± Periodic processing ±
Payments ± F110
u 11. Running the app program:
First give the parameters. Company code and payment method and next date. It
means the next date the running the program. And go to additional log in that
we need to select due date check, payment selection in all cases, line items of
the payment documents and save it.
u Click on the schedule proposal, next payment run in the last it has to display
one generated and one completed. Next go to new session click on systems
services and reporting in that give RFFOUS_C
u Then give the run rate, identification methods, company code, house bank,
bank id, check lot no, and save it and then execute it. And come back f110 and
give that identification in printout and save it.

&Ñ'
(!Ñ

u 3) .      &Ñ 


 
  
 +Ñ!#
2 +
&Ñ 
 
   
)
 Ñ    
      Œ)"    )
ÿ) .   $ 
 Ñ
$ 
 c    
 
    )
.   $

u In SAP, the moment you save the MIGO transaction, it automatically generates
FI document. It will create following entry:-
Raw Material Stock A/c Dr
To GR/IR Clearing A/c
u In MIGO transaction itself, you can post Excise by choosing Capture and Post
Excise Invoice. The FI document will be as follows:
RG23A Basic Excise Duty A/c Dr
RG23A Education Cess A/c Dr
To CENVAT Clearing A/c
u After doing MIGO, you execute MIRO. In this transaction also, SAP will
generate FI document automatically. The entry will be as follows:-
GR/IR Clearing A/c Dr
CENVAT Clearing A/c Dr
VAT Setoff A/c Dr
To AP-Vendor A/c
u Reversion of entry of material purchase can be in entered on rejection of
material partially or wholly. In this case, you will
have to raise a debit note on the vendor. But before raising debit note, you have
to first ensure that the Invoice verification of the material (to be rejected) is
complete at the time of purchase.
u Purchase documents cannot be reversed directly like pure financial document
entry. To reverse the material document,
following procedure should be followed.
1) Create Return Delivery (MIGO)
2) Reverse the Excise Duty Posted (J1IS)
3) Raise the debit Note. (MIRO) >00  
u "
Ñ
$ Ñ
+^+
u c  

 
$  
 ^, ÑG 
     &Ñ
 
( 
 
)c   

u If the cancellation / reversal of MIRO invoice is done through MR8M, only the
MM invoice / documents gets reversed but the FI document will not be
reversed or cancelled.

We have to follow the following procedure.

1. Goto T.Code MIRO


2. Select Credit Memo in the transaction field.
3. Fill up all the details in the fields for the invoice to be reversed.
4. Give the P.O. no
5. Select the line item to be reversed.
6. Simulate and save.

The impact will be as CR - GR/IR clearing a/c


DR - Vendor a/c

By this procedure, the purchase order history in P.O. will also get updated and
there is no requirement of any manual clearing. Only in the Vendor a/c, the DR.
and CR should be knock off.
u
"
 "
!Ñ

u . 
 "
!Ñ
u by: Narasimham
u Follow the following steps:
u Define Adjustment accounts for GR/IR Clearing

Path: IMG-F/A-G/L/A-Business Transactions-Closing-Regrouping-Define


adjustment accounts for GR/IR clearing

Double Click on BNG Transaction Key

System will ask you chart of accounts update it.

Again update the following

Reconciliation account: Enter the GL code i.e. GR/IR clearing account (Goods
Receipt/Invoice receipt)
Adjustment account: Enter the GL code i.e. GR/IR correction account
Targ. Acct : Enter the GL code GR/IR Invoiced but goods not yet received

Again Double click on GNB Transaction Key

System will ask you chart of accounts update it.

Update the following: -


Reconciliation account: Enter the GL code i.e. GR/IR clearing account (Goods
Receipt/Invoice receipt)
Adjustment account: Enter the GL code i.e. GR/IR correction account
Targ. Acct : Enter the GL code GR/IR Shipped not invoiced

Do the above steps.

The goods receipt/invoice receipt (GR/IR) clearing account is a provision


account, and is posted to whenever you receive goods that have not been
invoiced yet or whenever you receive invoices for goods that have not been
delivered yet.
u In this activity you define the numbers of the adjustment and target accounts
for the automatic postings for the GR/IR clearing account.
u Transfer postings have to be made at the balance sheet date to reflect the goods
invoiced but not delivered and the goods delivered but not invoiced.
u Transaction code F.19 analyzes the GR/IR clearing account and posts
adjustments entries for outstanding amounts to adjustment accounts. It makes
the offsetting entry to the account for goods delivered but not invoiced or to the
account for goods invoiced but not delivered (target account).

 
6
A 2

u By : Prabha K.
u 6- 
  

A   (  

)
u  2 
 : It is a special type of reference document. It does not
update transaction figures. Data from this document is used to create default
entries on the accounting document entry screen.
u  
 6
 : A periodically recurring posting made by the recurring
entry program on the basis of recurring entry original documents
u  
 6
 2 
 : A document containing the fixed data for
every recurring posting (for example -> posting key, -> account, -> amount«.
These 3 never change).
u You set up recurring entry documents for business transactions that occur on a
regular basis, such as rental payments and insurance premiums.
u It does not update transaction figures. To store, system used number range
"X1"
u Cross Co-Code transaction cannot be posted with recurring entry program.
u  
6

u For postings that recur on a regular basis, such as payments for rent, interest,
legal fees, property taxes, you can use the "Recurring Entry Program" to have
the necessary documents generated automatically.
u ?3:" 
6
#
  

u It contains«««The date of the first & last posting
The frequency at which the posting should be made,
The date of the next planned posting
u ?ÿ: Œ   
 6
  must be run at regular intervals within a
specified period. The program selects all recurring entry original documents in
which the date of the next posting falls within the specified period, and then
generates a Batch Input Session
u ?: c 
   
    , an FI original document is posted. The
date of the next posting is changed accordingly in the "Recurring Entry
Original Doc"
u You can create recurring entries and execute at month end by using these
t.codes..

- FBD1 - Create
- FBD2 - Change
- FBD3 - Display
- F.56 - Deleting Recurring entries
- F.15 - Executing for a period
- F.14 - Posting doc from recurring doc
- SM35 - Execute ur session

% Π

&  2 


u Ñ
 & 5 & 3 , Ñ $  *       
 
 
  

 
 $
GΠ

G   H)Ñ
 

 Π


   
  ).Ñ $
  
    Π
 
    2Ñ 62 
 
 Ñ  
( 

 $
    )
u Ñ  
*  Ñ 
     
 
       /  $  
 
 
(  )
u . 
 Ñ *   Œ 
 
    $) Ñ
    
  

H?  : G6
Π

G# )Ñ $
 *   &   
    
 H   Π


)
u Solution:
u On the first hand it is not possible to update the trading partner field for posted
documents, as per SAP Standard. There are two alternatives to this:
u Alternative 1:
u REVERSE AND DOCUMENTS CAUSING THE PROBLEM AND
RECREATE THEM AFREASH
u 1. Find out if there are any clearing documents within the main document in
question which is not getting cleared due the trading partner field.
2. Goto FBRA: Reset and reverse the clearing documents if any as found in
step 1.
3. Goto F-02 give the main document number; then goto "Document>Reverse"
menu or press CTRL+SHIFT+F12 to reverse the document.
4. Goto F-02: Recreate the main document using "Post with reference" function
of document header which gets automatically populated (with correct Trading
Partner field )as per setting defined in the customer/vendor master data once the
document is saved.
5. Goto F-44/F-32 and then try clearing the vendor/customer.
6. Dont forget the post the clearing documents which were reversed in Step 2.
u Alternative 2: This shall be taken as the worst case which shall not be
recommended as normal practice.
u To develop an ABAP which shall update the trading partner field VBUND in
Table BSEG, BSIK, BSID and then try clearing the documents.
u &

Π(H
u c Π


u In Business Terms Trading partner is your business partner within Group with
whom you are doing business.In order to identify Inter Company transactions
Trading partner field is used. You need to define all the Group Companies as
company in SAP and all the defined Companies will be available for selection
in Trading partner field. Trading partner can be defaulted in GL, Customer or
Vendor Master. If you need you can populate trading partner at Document
level too by doing settings in Document Type Master in T Code OBA7. *--
Suresh
u Trading partner is normally used to control (payment/transaction)
vendor/customer business with the group. Something like group/inter group
business. You have to go to master record. for eg, in customer master, go to
CONTROL DATA tab so see Acccount Control, in which you have provide
trading partner number/reference. *-- N B
u  # " Ñ 
u 1. The Clearing agent ask for amount, the person who receive the product will
give Letter of Authority to Clearing Agent. The clearing agent move to bank
and take check.
u For this purpose, we just issue LA.
u 2. Prepare Purchase for the Vendor from whom we are going to receive the
product. There may be 2 or more Vendors.
u 1. Product cost to be transferred to Vendor A
2. Freight or Other Charges to Vendor B
3. Customs Duty and Others to Vendor C
u Tcode : Me21n
u 3. First We have to pay Customs Duty to Commissioner of Customs after LA
issued.
u Entry : Customs Clearing a/c Dr
Cess on Custom a/c Dr
CVD Clearing a/c Dr
Cess on CVD a/c Dr
Special CVD a/c Dr

Vendor C a/c Cr.


u T-code :MIRO or YMIROOTH
u 4. Cenvat credit for the product will be taken by person who handling Excise in
that company
u Entry : Cenvat Clearing a/c Cr.
RG23A Part II a/c Dr.

5. Clearing of Cenvat Credit


u Entry : Cenvat Clearing a/c Dr.
CVD clearing a/c Cr.
Cess on CVD a/c Cr.
Special CVD a/c Cr.

6. After Bank payment they will transfter to us


u Entry : Vendor a/c - Dr.
Bank a/c - Cr.
u Π(N
)")
u #6- 
"
 Ñ

u By : Cisko
u ((- 
 
 
 
()
u Bills of exchange may be defined as a commitment subscribed by your
customer to pay a certain amount on a given date upon presentation of the bill
of exchange. They can be used to materialize installment payments.
u For example, you have accepted that your customer pays the invoice amount in
3 monthly installments of 1000 USD each. You will issue 3 bills of exhange of
1000 usd each and maturing in month in month m, m+1 and m+2. The bills of
exchange will be sent to your customer for acceptance(customer signs them).
u Once accepted they will be returned to you. You will have to post accounting
entries. But note that even though the accepted bills of exchange can be
considered as payment, you cannot clear the outstanding customer invoice until
the bills are effectively paid at maturity date. You then have to post the bills of
exchange as a special GL transaction.
u Again once you have received the bills of exchange you may decide to discount
them right away with your bank and this is done with or without recourse.
Depending on the option choosen, accounting entries are different. by
discounting the bills you receive payment of the bill and this can be used to
clear the outstanding customer invoice.
u But note that until the bill is finally paid by the customer at maturity date you
remain liable. You account for this liability by making postings which will
show the discounted bills of exchange as a contingent liability. They do not
show in the balance sheet itself but appear in an appendix of the balance sheet.

 
2 


" 

u .    


  
   .  
  

 
 
      
   
  
     
 Ñ
" 

u For Recurring document template you can use the following T.Codes
u FBD1 - Creation of recurring document
FBD2 - Change recurring document (This is for changing of amount and
recurring periods)
FBD3 - Display recurring document
F.14 - Posting of recurring document
F.15 - Display of recurring document
u For Diff. run schedule recurring documents you can use this T.Codes
u OBC1 - Creation of Diff. Run schedule Recurring document
OBC2 - Enter run dates for Recurring document
F.14 & F.15 steps are same
u Steps For Interest Calculation you can use this following T.Codes :
u OB59 - Define valuation method
OBA1 - Preapare automatinc postings for foreign currency valuation
FS00 - Assign exchange rate different key in loan a/c
F.05 - Foreign currencty revaluation
OBAA - Prepare account balance interest calculation
OBAc - Define reference interest rate
OB81 - Define time dependent terms
OB83 - Enter interest value
OBV2 - Assignmen of accounts for automatic
F.52 - Interest calculation
u nterest calculation:
u 1. Define terms of payments:
T.code: OBB8
path: img ->fin. accting -> AP AR :-> Business transactions :->outgoing
invoice and credit memo :->
maintain terms of payment
u 2. Define Interest Cal indicators / type:
T.code: ob46
path: img ->fin. accting -> AP AR :-> Business transactions :-> interest
calculation global settings :-> define interest cal types
Here in int cal type select 'p' for int cal on line items
u 3. Make Interest Indicator Available to Interest Run
Program:
T.Code: ob82
path: img ->fin. accting -> AP AR :-> Business transactions :-> interest
calculation global settings :-> prepare int. on arreas
u 4. Create Reference Interest Rate:
T.code: OBAC
path: img ->fin. accting -> AP AR :-> Business transactions :-> interest
calculation :-> interest calculation -> define reference interest rate
u 5. Assign interest indicators to ref. int rate
or define time dependant terms:
T.code: ob81
path: img ->fin. accting -> AP AR :-> Business transactions :-> interest
calculation :-> interest calculation -> define time dependant terms
Here in sequence # always use 1 for line item interest
u 6. Interest calculation account assignment:
Here we will mention how and which accounts the interest program should
post.
T.code: obv1
path: img ->fin. accting -> AP AR :-> Business transactions :-> interest
calculation :-> interest posting -> prepare interest on arreas calculation
(customers)
u Œ  &Ñ
" 
 
*
u c       
$$      
  
  (
* 

  

u By : Vicent
u Yes, you can do that, but there is no report available for you to give that
information. You can go for balance interest calculation.
u You can run the balance interest calculation and not process the batch input
session. The posting happens only when you process the batch input session.
u This configuration allows you to charge interest on overdue customer accounts.
Interest can be calculated by using the line items or overall account balances.
SAP keep tracks of the date of the last interest run and stores it in the customer
master record.
u First create an Interest Indicator.
u OB46 - Interest Settlement Calculation Type
Int Calc. Type
P - calculate interest based on line items.
S - calculate interest based on account balances.
Secornd, make it avaliable to the interest run program.
u OB82 - Interest Terms
u Third, determine the interest rate that will be used by the calculation.
u OBAC - Define Reference Interest Rates
OB83 - Enter the Reference Interest Rates Value
Fourth, assign the interest indicator to the reference interest rate.
OB81 - Define Time Dependent Terms
Finally, determine the how and to which accounts the interest program will
post.
OBV1 - Prepare Interest on Arrears Calculation
u
.Œ+* 
Œ=


By : Preveen Kumar

  "


 ± full amount is cleared for the remaining amount system will
generate one more line item as open item (or) due item.

3 #Œ 6 #c Ñ =#Ñ"6


PstKy ± 31 Account ± ****** (WELL) & press enter
Amount ± 45,000/- Business Area ± 830B, Payt terms ± 0001
Text ± Goods purchased

PstKy ± 40 Account ± 401000 (Material Purchased) & press enter


Amount ± * Business Area ± 830B (Under MORE button you will find it)
Text ± + & press enter. Select menu item DOCUMENT ±> SIMULATE &
POST.

#%Œ!#Ñ ! D+6 Œ ?


 
 " :
Accounting ±> Financial Accounting ±> Accounts Payable ±> Document Entry ±>
Outgoing Payment ±> Post (or) &05

  



Document Date ± **/**/**** Document Type ± KZ
Company Code ± 8301 Currency/Rate ± INR

Account± 211000 (ABN Bank A/C) Business Area ± 830B


Amount± 43,000/-,
Text ± Part payment,
Account± ****** (WELL) And enter & select RESIDUAL tab and double click in
the RESIDUAL ITEMS column and select DR (Discount Received) reason code.
Go to menu item DOCUMENT ±> SIMULATE & press POST button.


- 

While processing thru &05^, First enter the payable amount.


Next Go To Process open items. Go to Res. Items tab and double click on the
Residual items.

Œ$ 
 
 $

$ 

You can check "& (


$   " on Vendor master data.

In &Hÿ, Company code data -> Options Payment transactions.

Tick Check double invoice.


 
#
Œ=

c  
 

$
, 
  


$ 

 

by: Rams

%#
0Œ0=
+

In one time vendor we are not maintaing master data. Because the details of the
vendor is entered only at the time of entering invoice. After that we can't use the
details of the one time vendor. But you can post more than one transactions for that
one time vendor. In Normal vendor, we key in all vendor details at the time of vendor
creation. But it is not possible to convert one time vendor to normal vendor.

You can create special vendor master records for vendors from whom you procure
goods only once or rarely, so-called One-Time Vendor Master Records. For example,
suppose you order goods from a vendor with whom you usually do not place orders,
because your main vendor was not able to supply the required items. In this case, you
would use a "one-time vendor" master record.

When creating a "one-time vendor" master record, you must assign a one-time
account group. This account group determines that the vendor-specific fields are
suppressed. You don¶t need to enter this data until the time a purchasing document
(e.g. a PO) is created.

When you create a purchasing document with a one-time vendor, you will be asked to
enter the vendor address. Enter the vendor¶s name and address. Like all other master
records, you can display, block, or delete one-time vendor master records.

#
0Π
?&Ñ:

An account in which transaction figures are recorded for a group of


customers/vendors with whom you conduct business once or rarely. One time account
requires a special master record. For all customers / vendors with whom you rarely do
business, a special customer/vendor master record should be created. No data specific
to a single customer/vendor is stored in this One Time master record, since this
account is used for more than one customer/vendor. Therefore fields like address,
communication, bank data are suppressed.

You invoice a customer who purchased goods from you because his main vendor
could not supply them. In this case, you post the invoice to a one-time vendor account
instead of creating a separate master record.
When you post to a one-time account, the system automatically goes to a master data
screen. On this screen, you enter the specific master data for the customer, which is
stored separately in the document. This includes name, address, and bank data, for
example.

You process the master record for a one-time account in the same way as you process
all other customer master records. You can dun open items from it with the dunning
program or pay items using the payment program. The functions for one-time
customers are only different in a few aspects. For example, you cannot clear amounts
with a vendor.

Reconciliation Accounts
To create one-time master records, you have to specify a reconciliation account. If
you differentiate between reconciliation accounts in your company, you will need to
take this into account when creating one-time master records. You may, for instance,
have different reconciliation accounts for domestic and foreign receivables. You
would then have to create two one-time master records.

Line Item Display


For line item display, you should enter a key for sorting line items in the Sort key
field. Keys 022 and 023 are provided in the standard system. You may define other
keys that are specific to your company. Keys 022 and 023 have the following
meanings:

- Enter 022 to have the system sort and display line items by name and city.
- Enter 023 to have the system sort and display line items by city and name. The line
items of customers in the same city are displayed together.

Sort criteria can also be specified when entering a document. These criteria will
override the sort keys specified in the master record.

When creating a one-time account, use the appropriate account group (such as "one-
time account" in the standard system).


ŒŒ =


Ñ 
  * 
  
 (     $
 .!3ÿ 
G -)
c  
 
 Ñ 
    $
)

You need to maintained the following settings before you can post:

1. Creation of Vendor Account Groups(OBD3)


2. Create Number Ranges For Vendor Account Group(XKN1)

3. Assign Number Ranges For Vendor Account Group(OBAS)

4. Define Tolerance Groups For Vendor/Customer Groups(OBA3)

5. Creation of Sundry Creiditors Accounts(FS00)

6. Creation of Vendor Master(XK01)

7. Define Number Ranges For Postings(FBN1)

.  $   ,   *


  
  $
) Ñ $ 
$ 

  
    $
 
 (  
  
  ( 
$
, 
 
 
  , 
     6
  

  

 
)

You can do any of the following:

1. Delete the existing payment proposal. Clear the debit, credit by offsetting which
will create a new net due document. Then run F110.

or

2. Delete the existing payment proposal. Configure and incoming payment method for
the company code and then run F110.

.2

"


The following Customizing settings have to be made for down payment processing:

Settings for the billing plan - To activate the billing plan function, maintain the
materials, for which you wish to process down payments, with item category group
0005 (milestone billing). This gives the item type TAO via item type determination.
The item type TAO calls up the billing plan function.

You need to implement the following activities in the billing plan for down payments:

Maintain deadline category - This determines the billing rule (percentage or value
down payment) for the down payment request. The system assigns billing type FAZ
(payment request) defined in the standard system with billing category P. (For the
billing type FAZ there is the cancellation billing document type FAS in the standard
system).

Maintain the deadline proposal - Use the down payments that are due for the proposed
deadlines.

Maintaining a Pricing Procedure with the Condition Type AZWR:

In the standard system the condition type AZWR is delivered for the down payment
value already provided but which has not yet been calculated. You must include this
condition type in the relevant pricing procedure before output tax.

Enter condition 2 (item with pricing) and the calculation formula 48 (down payment
clearing value must not be bigger than the item value) for the condition type AZWR.

Before the condition AZWR you can create a subtotal with the base value calculation
formula 2 (net value). If the condition AZWR is changed manually, you can get
information on the original system proposal from the subtotal.

Maintain the printing indicator - The pricing procedure can not be marked as a
transaction-specific pricing procedure (field Spec.proc.) The condition type AZWR
has the calculation type B (fixed amount) and the condition category E (down
payment request / clearing).

Maintaining the Billing Document - In the standard system there is the billing type
FAZ (down payment request) and the billing type FAS for canceling . The down
payment is controlled using the billing category P of the billing type. A billing type
becomes a down payment request when the billing category P is assigned. You have
to maintain blocking reason 02 (complete confirmation missing) for the billing
documents and assign it to billing type FAZ.

Copying control - Copying requirement 20 must be entered in copying control at item


level for the down payment request. In the standard system the order type TA for
copying control is set up according to the billing type FAZ for the item category TAO.

Copying requirement 23 must be entered in copying control at item level for down
payment clearing. In the standard system the order type TA for copying control is set
up according to the billing type F2 for the item category TAO.

Financial Accounting settings - A prerequisite for down payment processing is that


the account is assigned to the underlying sales document. To do this, change the field
status settings in Customizing as follows:
Set reconciliation accounts (transaction OBXR) - For the `received down payments'
and `down payment requests' from
the G/L accounts you have selected, you should assign the field status definition
G031.

Maintain accounting configuration (transaction OBXB) - For the down payments


(posting key ANZ in the standard system) and the output tax clearing (posting key
MVA in the standard system), you must maintain the posting key.

You must also carry out a G/L account number assignment for the tax account.

Maintain the posting key (transaction OB41) - For posting key 19, set the sales order
as an optional field !!!

Maintain the field status definition (transaction OB14) - For field status variant 0001,
field status group G031, set the
sales order as an optional field !!!

Assign the company code to the field status variants (transaction OBC5)

Π2

  

.   
 
  *


by: Satish

I will try to give you a very good explanation how down payments work.

Down Payment recieved from a customer.

Tcode F-29 :

You post the customer down payment. You can see that the indicator for
downpayment A is assigned.

You can also see the report at FBL5N which is line item display for customers. You
will have to tick the special G.L indicator A for noted items to view down payments
recieved from customers

Tcode FB70 :
You make the customer invoice in FB70, remember that you make the invoice for the
total item and not minus the down payment amount for the customer. For example if
you have posted a down payment for 500$ in F-29 and the invoice amount is 1000,
you will post 1000 and not 500 as the customer invoice.

Tcode F-22 :

You transfer from special G.L as it is a downpayment to normal item as it is no more


a current liability for the company.

Tcode F-39 :

You give the invoice reference number and process the down payment and double
click on transfer posting. You can see the balane A has been nullified.

Tcode F-28 :

Finally when you recieve the payment from the customer you clear the open items for
the customer.

%
   * -&
&Ñ

Ñ  
  
 A - 
   
    * (-) .$, Ñ 
G
$ 
      Ñ 
    
    *) 2 

 $

   (
*  
 
    Ñ 
 ) Ñ      


    )

Lockbox is a process provided by a bank where the customer remits his payment to a
PO Box at your bank, the bank deposits the check in your account and enters the
remittance data from the customer. Then the bank sends the data to you electronically
for you to import and apply in SAP-AR.

The structure that the bank uses is usually one of two formats. BAI will provide you
the customer information and the check amount but no invoice remittance data.
Usually cheaper and works well for a business where customers are paying only one
invoice at a time.

BAI-2 offers remittance data but the bank charges more for the service because they
have to enter more info.

Look at structures FLB** to see the transfer data.


When the bank sends the customer payment data you use Treasury function FLB2 to
import and then process the payments. This process attempts to determine where to
apply the payment and will post directly against an invoice, an account to a customer
or if it can't even determine the customer it posts into a clearing account (configured)
to be resolved.

&ь (* N 
 


Π&#  * - 




6OOP&Ñ"#

c   *(-  




By: Aparna

Lockboxes are a procedure used mainly in the USA to enable checks to be deposited
more quickly. The checks the bank sends to you are entered as credits by the bank,
and the information entered is sent to the payee using File Transfer. The lockbox files
must be formatted per the BAI standard format.

Under certain circumstances, the bank transmits a data carrier to the payee several
times a day; the carrier bears the important check information.

From this data carrier, postings are then generated for accounts receivable and G/L
accounting.

Lockbox service has the following advantages for the payee:

- Better liquidity, thanks to faster collection, depositing, and crediting of checks.


- Reduced processing workload

To import lockbox data, proceed as follows:


Choose Incomings -> Lockbox -> Import.
You reach the initial screen.
Specify the path and file name of the lockbox file.
Specify the import options.
Choose Program -> Execute.

From the SAP Easy Access Screen select Accounting -> Treasury -> Cash
Management -> Incomings -> Lockbox -> Postprocess or Accounting -> Banking ->
Incomings -> Lockbox -> Postprocess.
Enter the required data and choose Execute.

The selected lockbox data is displayed in a hierarchy. The icons in front of each line
show the status of the check. The following are possible status entries:
- Posted
- Posted on account
- Partially applied
- Not posted

Proceed as follows to display the check status:


a. Choose View -> Other Display
The screen for displaying lists appears.

b. Click on the ALV icon Layout settings and choose Change layout.

c. Select the Check Status field in the dialog window under Column List.

d. If you want to use the field in the column list, click on the left arrow and choose
Copy.
The system displays the check status.

Edit Payment Advice

In order to edit the payment advice, double-click on the Payment Advice field in the
list display. Change the data you want to correct, save and choose Back.

If you want to change the account or account type, show the Account and Account
Type fields as described for the Check Status field. Both fields are shown in the list
display and you can change them directly. Choose Enter to save the changed data.

If you want to ensure that your changes have been saved, double-click on the Payment
Advice field and choose Payment Advice -> Header.

Choose Checks -> Post to resume the automatic posting of changed checks.

 * -"



c    *(- 





 * - "

Master Data Settings

General Ledger Accounts:


XXXXX has three lockbox clearing accounts:
Company Code 1000 ± G/L account 1201005, First Union Bank
Company Code 1000 ± G/L account 1201006, PNC, Bank
Company Code 2000 ± G/L account 1201008, Wachovia, Bank

General Ledger Account Master Record Settings:


Cash G/L accounts exist for each bank. For example account 1105012 is for PNC
Bank. If you look at the G/L account master record for this account (Accounting ->
Financial Accounting -> General Ledger -> General Ledger -> Master Records ->
Display, transaction FS03) you will notice the 'Relevant to Cash Flow' field is
checked.

Customer Master Record Settings:


In order for the lockbox program to identify a customer the payment MICR must be
populated on the customer master record in the General Data: Payment Transactions
screen. The remit-to lockbox assignment must also be specified. Regarding the
tolerance group assignment, XXXXX only has one configured that is a blank
customer tolerance. By defining a blank tolerance group the tolerance group field may
remain blank on each customer master record but the tolerance settings are applicable.
The tolerance configuration will be reviewed in the next few slides. Finally an
alternative payer should be entered on a customer master record if another customer
account will pay the bills for the customer.

Lockbox Assignment on Customer Master Lockboxes are assigned on customer


master records and determine which remit to address is printed on the customer's
invoices

Tolerance Settings

When an incoming cash payment does not exactly pay the referenced open item(s),
the system will create a residual item back on the customer's account or write-off the
difference if tolerance limits are configured.

In SAP tolerance limits are set for users and customer accounts with the stricter limits
applying.
SPRO -> Financial Accounting -> Accounts Receivable and Accounts Payable ->
Business Transactions -> Manual Payment Receipt -> Define Tolerance Groups for
Employees

Transaction: OBA4
This transaction is used to create tolerance groups for users. The tolerances are
defined by company code and at a minimum there must be one assigned to each
company code otherwise no postings can occur in the company code.

Company Code
Currency
Amount per Document ± The maximum amount that can be posted in an accounting
document.
Amount per Open Item Account Item ± the maximum amount that can be posted to a
customer or vendor account.
Cash Discount per Line Item ± the maximum cash discount percentage that can be
applied to a line item.
Amount, Percent, Cash Discnt Adj. To (Both Revenue and Expense) ± the amount
field contains the maximum amount of a customer overpayment
(Revenue)/underpayment (Expense). The percent field is the maximum percentage
rate difference posted by the system. The lower limit between the amount and
percentage applies.

Configuration: Define Tolerances (Customers/Vendors)

SPRO -> Financial Accounting -> Accounts Receivable and Accounts Payable ->
Business Transactions -> Incoming Payments -> Define Tolerances
(Customers/Vendors)

OR

SPRO -> Financial Accounting -> Accounts Receivable and Accounts Payable ->
Business Transactions -> Outgoing Payments -> Manual Outgoing Payments ->
Overpayment/Underpayment ->Define Tolerances (Customers/Vendors)

Transaction: OBA3
This transaction is used to configure customer tolerances. To change a tolerance select
the company code then press the Details icon.

Configuration: Define Reason Codes


Transaction OBBE is used to configure reason codes by company code. All new
reason codes must be configured in each company code.

Configuration: Define Text : Transaction OB56 is used to configure the text that
appears on a line item based on the reason code entered.
Configuration: Define Accounts for Overpayments/Underpayments : Transaction
OBXL is part of the automatic account assignment. The GL account for
overpayments/underpayments is maintained here.

Configuration: Define Posting Keys : Transaction OB41 is used to configure posting


keys. Posting keys are two-digit numeric keys that control the entry of document line
items. Specifically it controls the account type, debit/credit posting, and layout of
entry screens.

 * -


c    *(-




 * - 

There are three lockbox settings:

u Defining lockboxes
u Defining control parameters
u Defining posting data

Define Lockboxes:
Financial Accounting -> General Ledger Accounting -> Bank-Related Accounting ->
Bank Accounts -> Define Lockbox Accounts at House Banks

Transaction: OB10
In this transaction, you define your lockbox accounts at the house banks. Thus, on the
outgoing invoice you can inform your customer of the lockbox to which payment is to
be made. By specifying this, you can optimize the payment transactions.

To configure the lockboxes first specify the lockbox links (company code; key of the
lockbox to which the customer is to pay; house bank ID; lockbox number at your
house bank). Second enter a remit to address that will appear on the customer invoice.

Define Control Parameters:


SPRO -> Treasury -> Cash Management > Business Transactions -> Lockbox ->
Define Control Parameters

Transaction: OBAY
The top "Record format' settings are unnecessary for BAI2 format, and should be left
blank.

Procedure - LOCKBOX (currently the only supported procedure in standard system)


Record Format - BAI or BAI2

Record Format Parameters: (Required for BAI Only)


Document # length - length of the document # used to locate the open item
Number of document numbers in record type 6 - maximum # of documents in detail
record
Number of document numbers in record type 4 - maximum # of documents in
overflow record

Posting Parameters:
G/L Account Postings: Identifies whether G/L Posting is created.

G/L Account Posting Type: (1) = Posting / Check or (2) Posting / Lockbox
Incoming Customer Payments: Identifies whether to post to customer accounts also.

Insert Bank Details: Create batch session to update customer record with new bank
details.
ADDBNKDETAIL ± creates batch input session that if executed will update the
MICR number information on customer master records.

Define Posting Data:


Treasury -> Cash Management -> Business Transactions -> Lockbox -> Define
Posting Data

Transaction: OBAX
The lockbox is defined with respect to a 'Destination' and 'Origin" identifier
combination. Each lockbox must have its own unique Destination and Origin
combination, and also must be defined for a single company code in configuration.
The bank must transmit the file with the Destination, Origin and Lockbox identifiers
in the exact format as they have been created in SAP lockbox configuration.
Otherwise, the file will be improperly read by the lockbox and posting will not
properly occur.

General Data
Company Code - enter the company code for which the lockbox transmission applies
Bank Account Number - enter the bank (g/l) account for bank account posting
Bank (Payment) Clearing Account - enter the lockbox clearing account

Posting Parameters
Bank Posting Doc Type - enter the document type for bank account postings (e.g.
SA)
Cust. Posting Doc Type - enter the document type for customer (A/R) postings (e.g.
DZ)

Posting Key: debit G/L - enter the PK related to g/l postings (i.e. 40)
Posting Key: credit G/L - enter the PK related to g/l postings (i.e. 50)
Posting Key: credit Customer - enter the PK related to customer postings (i.e. 15)
Posting Key: debit Customer - enter the PK related to posting residual items (i.e. 06)

Execution of Lockbox Program


The lockbox program can be accessed using transaction FLB2 or program
RFEBLB00.

In the PRD environment a variant exists for each lockbox file. For test purposes it is
easiest to copy the PRD variants, changing only the location of the lockbox file.
However, Before executing the lockbox program please confirm that each of the fields
in the above slide is completed as indicated.

Import into Bank Data Storage ± this field should be selected so the lockbox file will
be imported into the bank storage data. This ensures that the same lockbox file cannot
be accidentally imported more than once (based on Origin, Destination, Date and
Time values).

PC Upload ± this field should be selected if the lockbox file resides on the users PC
rather than in a UNIX directory.

Lockbox File ± enter the location of the lockbox file in this field. The location may be
either on the users PC or in the UNIX directory.

Procedure ± this field should always be populated with LOCKBOX.

Input Record Format ± this field should always be populated with BAI2.

Invoice Numbers ± this field should always be populated with a '1'. This field offers
four standard open item identification algorithms.
1 ± match on document number (BELNR)
2 ± match on reference number (XBLNR)
3 ± match on document number first, if not found then on reference number
4 ± match on reference number first, if not found then on document number

Enhanced Invoice No. Check ± this field should not be selected. If selected it allows
postings to be made across customer worklists.
Algorithm: checks with advice and Algorithm: checks without advice ± these fields
should be populated with 001. These fields determine whether cash that does not find
an appropriate open item should be posted as 'On Account cash', or be applied against
oldest open items on the account.

Account assignment fields ± these fields should be left blank. The values entered in
the fields are defaulted on the postings created by the lockbox program.

Print Control ± this field should be selected so the lockbox reports will be output.

Π "

 



) Œ"#26ŒÑ"% 
1 EC08 COPY CHART OF DEPRECIATION
2 FTXP CREATION OF 0% TAX CODES
3 OBCL ASSIGN TAX CODES FOR NON-TAXABLE TRANSACTIONS
4 OAOB ASSIGN CHART OF DEP. TO COMPANY CODE
5 SPECIFY ACCOUNT DETERMINATION
6 CREATE SCREEN LAYOUT RULES
7 OAOA DEFINE ASSET CLASSES
8 AS08 DEFINE NUMBER RANGES FOR MASTER CLASSES
9 AO90 INTEGRATION WITH GL
10 OAYZ DETERMINE DEPRECIATION AREAS IN ASSET CLASSES
11 DEFINE SCREEN LAYOUT FOR ASSET MASTER DATA
12 AO21 DEFINE SCREEN LAYOURS FOR ASSET DEP. AREAS
13 FBN1 DEFINE NUMBER RANGES FOR DEP. POSTINGS
14 OAYR SPECIFY INTERVALS AND POSTING RULES
15 OAYO SPECIFY ROUND UP NET BOOK VALUATION
16 DEPRECIATION KEYS
17 DEFINE BASE METHOD
18 AFAMD DEFINE DECLINING BALANCE METHODS
19 AFAMS DEFINE MULTI LEVEL METHODS
20 AFAMP DEFINE PERIOD CONTROL METHODS
21 AFAMA DEFINE DEPRECIATION KEY
22 AS01 ASSET MASTER CREATION
23 AS11 CREATION OF SUB-ASSET
24 F-90 ASSET PURCHASE POSTING
25 AW01 ASSET EXPLORER
26 AFAB DEPRECIATION RUN
27 F-92 SALE OF ASSET
28 ABUMN TRANSFER OF ASSET
29 ABAVN SCRAPPING OF ASSET
2 ( Π  
 

 )

By: Aparna Sekhar

 3L"#D".Œ#&266"ÑŒÑ# 

EC08 ± IMG>Financial Accounting > Asset Accounting > FI-AA Implementation


Guide (Simplified Version) > Organizational Structures and Master Data > Copy
reference chart of depreciation/depreciation area

 ÿLÑ! "#+ D"#26Œ#".Œ#&266"ÑŒÑ#

OAOB ± IMG > Financial Accounting > Asset Accounting > FI-AA Implementation
Guide (Simplified Version) > Organizational Structures and Master Data > Assign
chart of depreciation to company code

   L Ñ!  &Ñ  "Ñ  ŒŒ6+6 Œ =6Ñ#  Œ# 6=6D


266"ÑŒÑ# 6

OAYN ± IMG >Financial Accounting > Asset Accounting > FI-AA Implementation
Guide (Simplified Version) > Organizational Structures and Master Data > Specify
statemement version for asset reports

 4LÑ26 ŒÑ&DD#%6Œ" 6

  5 L Ñ26 ŒÑ&D D#% ""#% Œ 26Œ6+Ñ ŒÑ#  A "66 


D#%Œ&#D#%6Œ" 6

SPRO ± IMG > Financial Accounting > Asset Accounting > FI-AA Implementation
Guide (Simplified Version) > Organizational Structures and Master Data > Asset
Classes > Specify required entries for asset master data

 7LÑ26 ŒÑ&DD#%! ""#% Œ&#D#%6Œ" 6

 8026&Ñ 6D#% %+ 6 !6

AS08 ± IMG > Financial Accounting > Asset Accounting > Organizational Structures
> Asset Classes > Define number range interval

  ^ 0 26Œ6+Ñ 6 266"ÑŒÑ#  6 Ñ  6Œ " 6  2


"66  D#%Œ
A021 ± IMG > Financial Accounting > Asset Accounting > Master Data > Screen
Layout > Define screen layout for asset depreciation areas

OAYZ ± IMG > Financial Accounting > Asset Accounting > Valuation > Determine
depreciation areas in the asset class

 9L!6 6Œ66Œ" 6&#+! ""#% Œ

ANKL ± IMG ± Financial Accounting > Asset Accounting > FI-AA Implementation
Guide (Simplified Version) > Organizational Structures and Master Data > Asset
Classes > Generate Asset Classes from G/L Accounts

  3 L "#+ 6Œ6 2Œ &# 6Œ " 6 6ŒŒÑ ! 6'%Ñ62
6 ŒD&Ñ6 2

SPRO ± IMG > Financial Accounting > Asset Accounting > FI-AA Implementation
Guide (Simplified Version) > Organization Structures and Master Data > Asset
Classes > Specify requires entries for asset master data

OAYZ ± IMG > Financial Accounting > asset Accounting > FI-AA Implementation
Guide (Simplified Version) Organizational Structures and Master Data > Asset
Classes > Enter default values in asset classes

AO90 ± IMG > Financial Accounting > Asset Accounting > FI-AA Implementation
Guide (Simplified Version) > Organizational Structures and Master Data > Assign
additional G/L accounts for transactions/depreciation

 33L6ŒŒÑ !%6"Ñ 6Œ" 6

OAYK ± IMG > Financial Accounting > Asset Accounting > Valuation > Specify
max amount for LVA + asset classes > Specify amount for low value assets

OAY2 ± IMG > Financial Accounting > Asset Accounting > Valuation > Specify max
amount for LVA + asset classes > Specify LVA asset classes

 3ÿL6"Ñ&DÑ Œ6=  2#ŒÑ !% 6

OAYR ± IMG > Financial Accounting > Asset Accounting > FI-AA Implementation
Guide (Simplified Version) > Organizational Structures and Master Data > Specify
intervals and posting rules


""



# 
If you have added the field Internal order in the Asset Master as a statistical order and
you want your depreciation
posted not only to the cost center but also to this order.

In transaction #D in the IMG you define how depreciation posts to the
depreciation posting rules - there is a CO assignment box where you have to tick both
cost centres and internal orders.

c   

   6- 
   -  
       

)

An internal order is used to accumulate cost for a specific project or task for a specific
time period. An internal order is therefore used for a short period with a specific
deadline.

Your internal order will usually settle to cost centers (and not visa versa) according to
the settlement rule in the order setup.

An internal order can therefore be used to group all the expenses incurred to plan and
hold a conference over a 3 month period. The order can be settled on a monthly basis
to cost centers. When the conference is finished the order can be settled finally. The
cost of the conference will then be spread over 2 or more cost centers, but can be
viewed in total on the internal order when needed.

Internal Orders - It is an instrument used to monitor costs and, in some instances, the
revenues of an organization.

Uses of Internal orders


- Monitoring the costs of short-term jobs
- Monitoring the costs and revenues of a specific service
- On going cost control

Internal order categories


- Overhead Orders
- Investment Orders
- Accrual Orders
- Orders with revenue

Cost centers are not for specific job. e.g If you have open Trade-fair / exhibition (1
month period), then to allocate cost, you can use Internal Orders (Say IO) you can
post to IO, and from their to various cost centers. If management were to ask you the
cost of that exhibition, Internal Order will help you
Cost center is a responsible center in SAP. It cannot be defined as statistical but in
transactions it may become as per other co objects.You will be able to find out the
performance of the cost center using activities and plan values with actual value. This
is lowest cost object in SAP. This will become a statistical object when you allocate
the cost to other higher objects. Cost can be allocated to other cost centers or co
objects but not fi objects like GL,assets, inventory etc. can be defaulted in transactions
through cost element. It cannot be a cost object for a revenue element, revenues are
always taken for other higher CO objects. No budget functionality is available but
planning functionality is available and is always measured for a year in business.

Internal order is the second CO object - which can be defined as statistical or real.
You will be able to define Budget and planning figures - more than one year also. Can
control the postings of FI through budget controls. You can have the report of Plan vs
actual including commitment. Cost cannot be allocated but settled through settlement
rules and profiles. The receiver of the values can be any object not like Cost center -
can be CO objects and FI objects. Ideal for R&D expenses capitalisations, etc. Status
profile is linked to this which controls many individual transactions in each status
which is a part of this Internal order. It can also receive postings of activities from
Cost center. Settlement profile is an wonderful tool for variety of settlement - needed
for FI and CO - legal requirements also and Revenue requirements also for any
country.

All SAP CO orders like Production order, Plant maintenance order, etc will behave
like Internal order with more functinalities.

 &- 2  

Every asset transaction immediately causes a change of the forecasted depreciation.


However, it does not immediately cause an update of the depreciation and value
adjustment accounts for the balance sheet and profit and loss statements. The planned
depreciation is posted to the general ledger when you run the periodic depreciation
posting run. This posting run uses a batch input session to post the planned
depreciation for each posting level for each individual asset as a lump sum amount.

The calculation and scheduling of depreciation, interest and revaluation are


automatically controlled by keys in the system, or you can control them manually
using a special posting transaction. In both cases, planned depreciation from Asset
Accounting must be periodically posted to the corresponding asset and expense
accounts of the general ledger. You carry out this posting using a batch input session.
In addition to the various depreciation types, interest and revaluation, this batch input
session also posts the allocation and writing off of special reserves.
When the system posts depreciation, it creates collective documents. It does not create
separate documents for each asset.

Depreciation Posting Run is done via transaction code '& '.

The program creates batch input sessions for posting depreciation and interest to the
G/L accounts in Financial Accounting and/or to Controlling.

& 2  


0

Company code : Your Company Code

Fiscal Year : Your fiscal year

Posting period : Your depreciation period

Reason for posting run (choose one)

Planned posting run : X (default)

List assets : (tick if you want to see the detail)

Test run : (tick if you run in test mode else untick for production run)

Main asset number : (you can specify certain asset number if you click repeat run or
test run)

Note :
Click the execute button if this is a test run.
Click the menu bar -> Program -> Execute in background if this is a production run.

You should get this message :


B


 BU 
      

Release and Process the Batch Input Session in transaction code '+5'.

Process Session RABUCH00


X - Display errors only
Additional functions
X - Dynpro standard size

Click the Process button


If there is error, the system will pop up the error message.

Correct the error and recreate the session in transaction '& 2'.

& 2  


0

Company code : Enter your company code

Fiscal year : Enter your fiscal year

Posting period : Enter your posting period

List assets : (tick if you want to see the detail)

Test run : (tick if you run in test mode else untick for production run)

Note :
Click the execute button if this is a test run.
Click the menu bar -> Program -> Execute in background if this is a production run.

You should get this message :


B


 BU 
      

D0
"


The year-end closing enable the company to produced the final balance sheet and
profit and loss statement for its annual report, which has to be created to meet the
particular legal obligations in each country.

Once the fiscal year is closed, you can no longer post or change values within Asset
Accounting (for example, by recalculating depreciation). The fiscal year that is closed
is always the year following the last closed fiscal year. You cannot close the current
fiscal year.

N - Year-End Closing Asset Accounting

" 
   : Your Company code

  ) 


) : Optional

&  : Last closed fiscal year

Uncheck 'Œ
' if this is a production run
At menu bar, click Program -> Execute in background.

&  - )

c  
Œ
,     
(  
(  
   
   )Ñ  #  6) Ñ 
 ( 
 
   6  ()

,Ñ $  * Ñ
 (  )
   


    %=     (   
  , 



   

 
( )

You can check and edit Asset accounting closing status using tcode OAAQ.

But you seem to be not clear on process.

AJAB is for closing Asset Accounting books.


AJRW is a technical step of changing fiscal year in system. If not done, it will not
allow you to view asset reports in current fiscal.

Now, your error says incomplete asset. Please run ajab in test mode, check for details.
It will give you asset details and error details as well. Go to asset explorere and check
if the asst in question has been fully depreciated for the year.

If not run repeat deprecation for the asset in period 12 and then try closing asset
books. You can also check asset and GL inconsitency using tcode
ABST.

$D06
"


If you closed a fiscal year too soon, and still need to make corrections, you can reset
the last closed fiscal year in Customizing for :-

Asset Accounting (    


0PD0
 
0P$).

Using this function, you can re-open the last closed fiscal year, either for selected
depreciation areas in a company code, or for all depreciation areas in a company code.
You do this by changing the field for the last closed fiscal year.

Be careful if you re-open a fiscal year only for certain depreciation areas, and you
need to make adjustment postings only in these areas. You cannot use the standard
transaction types for these postings, since the standard transaction types post to all
depreciation areas. Instead, you have to define your own transaction types in
Customizing for Asset Accounting (Transactions), limiting them to the required
depreciation areas.

#' - Reverse year-end closing for deprciation area

At the desired company code, change the fiscal year in '"  ' column.

Save entries and create a new request.

Change Asset fiscal year

Nc - Asset fiscal year change

Company code : Your Company code

New fiscal year : Last closed fiscal year

Uncheck 'Œ
' if this is a production run

At menu bar, click Program -> Execute in background.

" 1
? $
G(
 
   :

If you realized that there are some fixed assets that haven't been post in a closed fiscal
year,

Do the following steps :-

1. Reverse fiscal year closed by following the 'Reverse Year-end Closing' procedure.

2. Open the accounting fiscal year via transactin '# 5ÿ'.

3. Post the fixed asset acquistions in the re-open fiscal year.

4. Repeat depreciation run for the last period of that closed fiscal year.

5. Repeat depreciation run for the last period depreciation run of the current fiscal
year.
6. Closed fiscal year by following the 'Year-end closing' procedure.

7. Closed the accounting fiscal year via transactin '# 5ÿ'.

+" 
&
2

.2

You can reset the entire AA data from Img->FA-> AA-> Preparing for production
startup ->Tools -> Reset
company code.

This will reset only the asset accounting data from the company code. But before you
perform this you have to make sure that you reverse all the transaction you have
posted and have gone to the FI. As this reset will not effect FI GL data.

You can then reset the depreciation posted and then the recon accounts.

When you reset the recon accounts, it will enable you to post directly to the account
like normal GL. Then you have to post JV and rectify you GL(recon account).

Then upload the correct data. After the data is uploaded set the recon accounts. this
will reconcile the amount with the assets and activate the company code (in asset
area). >00 * 

+ 


I am experiencing problems in OA02, Asset Mass Change. I am using 4.6C.

What happened was that I created the Substitution, then created the Step, and I then
SAVED. I am not sure if I need to create a RULE or not. I have already defined in a
STEP, (using Formula Builder) that most assets belonging to a certain asset class,
9011 with a current Cost centre, Z01, are to be assigned to another Cost Centre Z02,
within the same Co.
Code. I then saved the Substitution, although I noticed that there was a "?" icon next
to the RULES folder. I am well aware that for Time Dependent Data, we would need
to specify a "Valid From" date. (ADATU, in Table ANLZ) But, do we need to
specify a "Valid To" date as well ?

My data is like this.....

PREREQUISITES: Asset Class =3D '9011'


SUBSTITUTION: Valid From is substituted by Constant '19.08.2001'
Cost Centre is substituted by Constant 'ZB02'

If I need to create a Rule, What would I need to enter ? I then created a WorkList, and
assigned the Substitution to it. After this, I generated the Worklist in Background
using AR31. Everything seems ok, but when I check the Assets, I still see the old
Cost Centre, NOT the New Cost Centre.

--------------

Rules are not required. You get a ? because you probably started to create one and did
not finish.

For a Cost centre mass change, if you want to have it time dependent, you must
specify 'valid from' and 'valid to' in the substitution rule. In config you determine if
you want to use the time dependency or not (default is : Yes)

+2% 

Ñ 
    

   Ñ $  
 (      
 

 
ÿ)&  
$  
(

 


?( 
 ( 
:, 
    

  
 /)

Ñ   ( 


 ÑK&ÑC626ŒK". !6  

) c  ( Ñ
 *
-  /
 

To make a mass change, you have two options:

1. If the change of the field can be put into an algorithm (e.g., enter XYZ as a super
number for all assets in class 1234), you can use a mass change rule. You first define
the mass change rule in the same way as you would define an asset substitution (IF
something, THEN something else), then you go into the mass change transaction,
select the right assets, the proper change rule ... and hit Execute.

2. Very often, it is easier to prepare the data in Excel and use transaction AS02 for the
upload. Here, I can recommend transaction LSMW - you simulate (and record) the
AS02 transaction on one fixed asset master, then follow all the steps proposed by the
system (define fixed values, variables, etc.) and finally upload the Excel (.csv).
System will automatically generate a batch input for all assets. It may take some time
for you if you do it for the first time, but it is the best way if you would otherwise
need to define complex algorithms.
So - use option 1 if you have a simple algorithm for many assets, and option 2 if "each
case is different" or if you feel more comfortable in Excel than ABAP. Option 2 is
simple, but of course takes some time to generate the upload and then run the batch
sessions (while option 1 changes everything instantly in a matter of seconds).

Ñ@$   


 - 



 

 
    
)

Ñ  


 +c ?  :ÿ
 
,
    (   #(
  $

- R

Here are the details:

I. To use mass change:

1. First, define a mass change rule in transaction OA02 (Accounting - Financial


accounting - Fixed assets - Environment - Mass change rule). For each company code,
you can define one rule (or a sequence of them). However, all of them will always be
executed at the same time. Therefore, if you need to define different rules for different
assets, you will have to do this repeatedly. Technically, this is done in the same way
as AA substititution.

2. Once the rule is defined, you need to select assets for mass change. Go to
transaction AR01 (Accounting - Financial accounting - Fixed assets - Environment -
Worklist - Generate). Enter selection criteria like on any standard AA report, and run
Execute. I cannot simulate this now on my system (we do not have AA), but it should
ask what you want to do (mass change, mass retirement, etc.) and ask for a name of
the worklist (write anything - e.g., Super number change). The system will show you a
list of selected assets in a report format. Check it and make sure that it is correct. You
may add or remove single assets from this (now cannot tell you how, but it is
possible). If you are happy with the list, save it.

3. The last step is execution of the change. Go to transaction AR31 (same path as
above), execute the report and if you are happy with the list (same as in step 2), press
Save. System will show you a log of change (what went through, which errors
occured). You are done.

II. LSMW
LSMW is a transaction, which will let you mass upload almost any other transaction
(FB01, FD01, AS91, etc.). You do it in the following way:
1. Enter into transaction LSMW (no menu path), possibly in a development / test
system
2. First, define a project, subproject and object (relatively formal task).
3. On the horizontal menu, go to Goto -> Recordings. Click on "Create recording".
4. Enter the name and description of recording (freely definable).
5. I cannot simulate this now in my system, but SAP will ask you about transaction
code (AS02) and will take you into the AS02 transaction. In this step, do the change
manually. Make sure you "touch" (change / write something) in all fields which you
want to update.
6. Once you are done, save the recording and return on the start page of LSMW. Click
"Execute".
7. You will see a list of tasks. Do them one by one. They should be relatively simple
(and I cannot help you with them). Important is step 3 (maintain source fields) - here
you define the columns of your excel (csv) file in the particular order. In step 5 (field
mapping and conversion rule), you assign file columns to SAP fields (note that you
will see only those fields which you "touched" during recording). You need to go
through all the steps. In the end, you get (and run) a batch session.
8. If you did this in a development system, transport the LSMW object (menu Extras -
Export project, Extras - Import project). You have to do it via file, not via standard
transports of configuration (it is perhaps more simple).

Make sure you test it first in development or quality system!

& D=



 
 

 $  3ÿ7

&   N
 0 2 (,    (   ( 
c (( 
 
 &  02 ÿ7
 

& #2
&  
ÿ7

&D

Normally, the best way is to keep it simple and leave the first year "normal" (12 + 4
months starting January). You convert old data as of August 31 (unless the client
requests opening balance as of December 31, 2005 and then monthly movements - I
have experienced both options) and then start normal bookings in month 9 on
September 1.

We never tried shortened fiscal year in this context and it is surely not needed here. It
just adds complexity.

Ñ    


 N
02  &  D  ÿ7 ,    

  
$
# ÿ72  (*$ 
     (* $  N
 ÿ7 
    
    
N
 (

The ordinary way is to load fixed assets which exist on September 30 (if you go live
with AA module on October 1) with trans. AS91.
- First, you need to set in configuration that the last closed fiscal year for legacy data
upload is 31.12.2005 and the last period for depreciation will be 9/2006. (Do it in
IMG: Financial accounting - Asset accounting - Asset data transfer - Parameters for
data transfer - Date specifications)

Within trans. AS91, you enter the following values:


- acquisition value and accummulated depreciation as of 01 January 2006
- all asset movements (acquisitions, retirements, but not ordinary depreciations)
between January 1 and September 30 with their respective dates
- already posted depreciation in 2006 until September 30

Then you enter GL movements per month (either you temporarily change the asset
reconciliation accounts for direct booking with trans. OAMK, then book with FB01
and finally reset with OAK5, or you book there directly with trans. OASV). This way,
your asset accounts (acquisition value and accummulated depreciation) are the same
as asset module as of September 30.

You can also let the system recalculate the depreciation from the beginning of the
year, but then you may end up with a different value as of September 30 than your
legacy system calculated. So, I would not recommend it unless there is no reliable
source data.

  $




6- 
 $

c $
)



* Without customer - Transaction ABAON


- in case that a sale invoice is issued and posted in SD (or FI) and asset retirement is
posted in FI-AA - Transaction ABAON.

* Between affiliated companies - Transaction ABT1N - asset transfer between


company codes
* With customer known - Transaction F-92
- in case that a sale invoice is not issued and book through SD
but in FI-AA - Transaction F-92.

* The sale invoice posted in FI-AA - document posted in AA or FI (document type


ZN) and issued (printed) by transaction what has to be modiffied.

   - transaction ABAON (old t - ABAO)

In case you want system to calculate Gain/loss from sale for you enter Manual value
(revenue amount) in specification for revenue. It is not allowed from the legal point of
view for France.

If you want the asset to be retired in NBV choose which depreciation area (e.g.01 -
management reporting area required) net book value should be posted.

Enter transaction type to specify the business operation you want to make.

(e.g. Retirement with revenue 210,

Retirement of new acquisition with revenue 260)

An asset retirement can refer to an entire fixed asset (complete retirement) or part of a
fixed asset (partial retirement).

In case of partial retirement enter amount posted, percentage rate or quantity.

System calculates the gain/loss from the asset sale and makes posting on gain/loss on
sales asset account.

The difference (gain/loss) is counted from NBV of the asset and the revenue amount
(clearing account e.g.5700990)


 $
 - Transaction ABAVN

Retirement due to scrapping, donation, deficit, damage

Retirement without revenue is a removal of an asset from the asset portfolio without
any revenue, for example, by scrapping. When you use this posting option, the system
does not create revenue and gain/loss postings. Instead it creates a loss from an asset
retirement without revenue posting in the amount of the net book value being retired.
Retirement without revenue transaction posts NBV to one account specified in
account determination for each reason of disposal.

Additional account assignments with specific transaction types can be created to


fullfill requirements of posting on different accounts for each or some of disposal
reasons (e.g. different account for scrapping than for donation). This specific posting
is allowed only for book legal depreciation area, for management area account for
retirement due to all reasons is the same (e.g.5700000).

*-- Milada

+
2 

&

+ OOP&Ñ"#

6- 
+
)

When an enterprise sells a large portion of its fixed assets (such as a plant or a
building), it is necessary to post the retirement of all the individual assets which make
up the whole. Since the number of affected assets can be very large, the Asset
Accounting (FI-AA) component makes it possible to make the necessary postings
using mass processing.

c 


Asset retirement is the removal of an asset or part of an asset from the asset portfolio.
This removal of an asset (or part of an asset) is posted from a bookkeeping
perspective as an asset retirement. Depending on organizational considerations, or the
business transaction which leads to the retirement, you can distinguish the following
types of retirement:

- An asset is sold, resulting in revenue being earned. The sale is posted with a
customer.
- An asset is sold, resulting in revenue being earned. The sale is posted against a
clearing account.
- An asset has to be scrapped, with no revenue earned.
- An asset is sold to an affiliated company (refer to Manual Posting of Intercompany
Asset Transfer/Retirement)

Π/
  9S)"

 *

      
 $( Ñ    (  &09ÿ 0  

  (   
()
If it¶s a mass retirement, it¶s possible - but I doubt mass physical deletion of assets.

Follow the steps below if you want to do mass retirement :

1] AR01 -> Give your company code -> and the asset numbers
Now press F8 to execute the same

2] At this point -> Go to the work list -> create -> Enter in the mandatory tab and
select the retirement without revenue -> Enter

3] Enter dates / transaction type -> now you will get a work queue number

4] Go to AR31 and execute the work queue -> Then click the Release button

This will work as a mass scrapping of assets.

.
 A 



There is no specific configuration for asset retirement. For retirement there are 3 ways
as following:

1. Scrapping Asset - ABAVN

2. Sale of asset with revenue - F-92

3. Asset retirement without revenue - ABAON

Asset retirement is an integral part of asset management. An asset can be retired in


following ways :-

1. By Scrap - T.Code ABAV/ABAVN

2. By sale. In sale there can be following cases :-

a. with revenue -

b. without revenue

c. with customer - T Code F-92

d. without customer - T Code ABAON

.Œ"


 


&Ñ
These are the steps that you need to do to create Asset Accounting (tested in 4.7
version) :

Copy Reference Chart of Depreciation/ Depreciation Areas


Menu Path is: IMG> Finanacial Accounting> Asset Accounting> Organization
Structures> Copy Reference Chart Of Depreciation/ Depreciation Areas,
- Double click on Copy Reference Chart Of Depreciation
- Click on Copy Icon and update it from ODE to your Chart Of Depreciation and
change the description too.

Assign Input tax Indicator for Non-Taxable Acquisitions:


IMG> Finanacial Accounting> Asset Accounting> Integrate With the General
Ledger> Assign Input Tax Indicator for Non-Taxable Acquisition
- Save this.

Assign Chart of Deprecaition to your Company Code :


If Co Code is not properly Done then it will give Problems but still save it.

Specify Account Determination:


IMG> Finanacial Accounting> Asset Accounting> Organization Structures>Asset
Classes> Specify Account Determination
- Make the GL Accounts for this and those GL accounts to be specified here,
Example for Land, Building, Plant & Machinery, Vehicles And Asset Under
Construction then again
- Save it.

Create Screen Layout Rules:


IMG> Finanacial Accounting> Asset Accounting> Organization Structures>Asset
Classes> Create Screen Layout Rules:
- Here we copy the screen Layouts from the standard Co Code 1000
We will copy for each Asset Class like Land, Building, Plant & Machinery, Vehicles
And Asset Under Construction,
- Now save it again.

Define Number Range Interval:


IMG> Finanacial Accounting> Asset Accounting> Organization Structures>Asset
Classes> Define Number Range Intervals
- Click On Intervals
- Click On Interval and update the following:
- For all the Five Asset Classes
- Save It.
Now Define the Asset Classes:
IMG> Finanacial Accounting> Asset Accounting> Organization Structures>Asset
Classes> Define Asset Classes
- Click on New Entries and fillout the Page in the blank space where Asset Class is
given give the Asset Class GL number and in Description give the name in long and
short form,
- Go to next level and give the Screen layout Rule number
- Give the number ranges 01 and in Status Of AuC click the first Radio button: No
Auc Or Summary Management of Auc
and in History Status click Manage Historically and save it.
- Likewise Create for Building, Plant & Machinery and Vehicles and in case of Asset
under Construction Update in Status of - Auc the second Radio Button: Line Item
Settlement and
- Save it now.

Integrate with General Ledger:


IMG> Financial Accounting> Asset Accounting> Integration with the General
Legder> Define how Depreciation Areas Post to General Ledger
and then Assign the General Ledger Accounts

IMG> Financial Accounting> Asset Accounting> Integration with the General


Legder> Assign G/L Accounts
and then Specify Document Type AF and specify intervals

1 Monthly
3 Quaterly Posting
6 Semi- Annually
12 Annually.

 
+" 
%
c*

Ñ
 
c  
    
 


*

Selection of field and data to change: (" (


 , #ÿ). This
transaction must be run prior to ceating a work list and performing mass changes.

Selection of the Assets Involved: ("c* ,3). This transaction for


creating the work list must be performed after OA02 and prior to running AR31.

Access the ³Process Asset Mass Change´ transaction by:


u Via Menus Accounting -> Financial Accounting -> Fixed Assets -> Tools ->
Work list -> Edit
u Via Transaction Code AR31

c*

The work list that is created opens a workflow. By means of the definition of the
workflow, the system determines which workers should carry out the following steps:

u Manually checking and possibly adding to the work list


u Releasing the work list and posting the changes.

The system automatically sends the work list to the specified employees. They
receive the work list as a task in their R/3 Mailbox.

u Process the work list (Tools -> Work list -> Edit).
u Select the work list in your mail in box ("Edit and release work list")
u Check the assets in the work list created (Process)
u Release the work list (Release).
u It is also possible to distribute the steps "Edit work list" and "Release work list"
in the workflow to different users. This is possible when carrying out a bulk
change by selecting the corresponding work flows when creating the work list.
u Check the results using the document change list (Assets -> Change).

NOTES: Please note that when you make a change to time-dependent data (such as
the assignment to a cost center), you always have to enter the time interval (valid
from/to date) in the substitution rule.

u When you enter a new "valid from" date in the substitution, the system
automatically opens a new time interval.
u You can only change one time interval in each bulk change. It is not possible
to change several time intervals in parallel.
u When you make changes to the depreciation terms, you must also enter the
depreciation area (AFABE) in the condition.

 
  
LH 

 ( *

    
Π H

By: Syed Saleem

In order to use the ASKBN transaction, you have activate the SAP R3 Enterprise
Extension.

First option in the IMG menu.

Requirements: See SAP Note 588364.

This allows you to post directly to the ledger without without having to generate a
batch-input session.

In addition, you can post directly online to the general ledger from the dialog posting
transaction from depreciation areas other than the master depreciation area 01. Or you
can update the values from a depreciation area to a special ledger using a different
accounting principle.

I tested the ASKB last year before we discovered that we could activiate the SAP R3
Enterprise and use the ASKBN. Once activated, you will see the ASKBN listed in the
menu.

This transaction is much, much better to use than the ASKB. Plus it works similar to
your deprecaition posting. The only complaint that I have is that you get a "log" in test
mode, but it does not create an actual posting log when executed like the depreciation
postings creates.

In order to use this transaction, you must configure the depreciation area where you
are capturing the non-US GAAP asset requirements to post to the ledger in addition to
the Area 01 that will automatically post.

You will also have to establish an external document type, document number range
and a reverse document type (OBA7) with account types allowed for Assets and G/L
Accounts.

The document type needs to be different from the document type used for the standard
depreciation posting (AF) and AA postings (AA). We used AZ. We are also using a
number range outside of our standard AA and depreciation document numbers.
We assigned the AZ to number range A4 which is viewed via FBN1.

c 
c 
 


"

(  
(

 

( ,Ñ*
  
 
 



"!)! 


Business Areas in SAP are used to differentiate transactions originating from different
points/lines/locations in business. Let me give some examples to elucidiate:-

A company (say, ABC) is a huge company and has a variety of businesses under it.
Let us say that it typically operates in 3 different domains like machinery
manufacturing, trading and assembling of machine parts.

There are 2 options here now -


1. Either create different company codes for the 3 business operations (which would
be the easiest and require no creativity)

or

2.) Create each of these business lines into business areas (the better option).
The advantages of using the second option is:
1. You can use these business areas if other company codes require the same areas
2. The configuration is simpler as in case of company code, you would require to go
through the entire configuration of creating Chart of Accounts, Fiscal Year variants,
posting periods variants and so on. In the business area option, you just need to attach
it to the company code and the rest of the details in Business area is attached by
default from the company code you are using it in.

3. Using the options in controlling (EC-PCA, Enterprise Controlling, Profit Centre


Accounting), you can even draw up Balance Sheets and PL statements for your
business areas and hence this is used for management accounting in some companies
(like HP, Dell, etc) when it wants to know the operating profits for different business
areas/lines.

The above was an example when the company wanted to separate entries according to
the lines it operates in... the other case could be when it wants to find out profitability
during its operations in cities and differentiates these cities into Business
Areas...
Business Areas are not much relevant in FI but are much more relevant in CO.

Hope this clears.

N (N

D $$
$ -  
)Ñ $/
)

Ñ Ñ 
    
 A   
  
  , Ñ 
 * ) ,
. (   
 
    
 
  
 (
  

   

)

H


Let me first be sure of what you are asking. Is it:

1) You want the B/S and P/L statements of transactions carried out in areas other than
the business areas defined by you? or

2) You only want to view the transactions that were not carried out in any business
area?

Whatever were your doubts, let me clarify.

If your doubt was the first one, then, in that case, the financial statements will not be
available. There are reasons for the same. All transactions in FI pass through G/L
accounts. The data in FI is then passed to CO through primary cost elements.
According to the settings that you have configured for your controlling area and
operating concern, the costs are distributed to the various cost centers (Cost Center
Accounting & CO-PA). The costs are then apportioned to the various cost centers
(which may or may not be a part of your business areas or may be independent cost
centers). Now, with this data, financial statements of the business area are drawn up.
For transactions not part of business area, they are transferred to independent cost
centers (e.g. like Head Office Salaries, HR, etc) and hence, cannot be drawn up as a
financial statement but just as line item displays in your reconciliation ledger (if you
have activated it in the CO-OM-CEL {Cost Element Accounting})

[The answer to your second doubt, I hope].

Financial statements of Business areas are unbalanced because not always does the
debit and credit entries of a transaction lie in the same business area/cost center; but
for cost accounting purposes, they are reasonably sufficient.
I hope this clears.

N (N

Π
*      ) Ñ 

 Ñ
   $   ( 
()

Ñ 
  
 &Ñ 
     
   
 "#   



) Ñ 
 
 

   
  
(
)

  ,   (


  
 ( 
  ($  (  
  
$)

Ñ ( Ñ


)

H
$H

In order to generate BS and P&L at business area level you should carry out the
following:

1. You should have activated " Enable BA balance sheet" under enter global
parametets in FA global settings.

2. You should do configuration under the transaction code "OBXM"

3. You also have run the transaction codes f.50 for P&L and 5.d & 5.e for Balance
sheet readjustment.

System automatically posts the taxes and reconciliation accounts of NIL BA


transactions to BA and tally the trial balance of all B. areas

D

D - 

  - 
 
  , ( Ñ $  / * /
  
 
(

  
(
 
$
 

(
  $(

 
 )
 
 (( (  

(
 

 

Why would I use business area against a profit center?" is a very pertinent one and
conceptually necessary. Let me explain to you what a profit center exactly means,
both in SAP terminology and in management accounting.

In management accounting, a profit center is an area or department from where the


management wants to find out the return on investment or ROI, as the accountants
know it. The concept in SAP is similar as it is used by management to find out the
ROI. On the other hand, business areas are just segregation of business transaction
origins. So, a certain business area can have more than one profit center within it.
Both have their unique uses and both have their unique features.

Using the above understanding, you can easily work out where you would use
business centers and where you would use profit centers.

Hope this clears,

N (N

Thanks for the explanation its good thanks

(
 

 


"

+

 


You can set up several business areas for each client so that the system can assign the
postings made in all company codes defined in this client.

To ensure consistency in document entry, you should give business areas the same
name in all company codes.

Goto transaction + and specify the view =KŒ!

To maintain to business area click the +



button.

& " 
" 

SAP recommends that you used 6"3 to copy an existing company code to a new
one.

This has the advantage that you also copy the existing company code-specific
parameters.

If necessary, you can then change certain data in the relevant application.
This is much less time-consuming than creating a new company code.

&
   
  
  0

Use EC01 to copy an existing company code. This will ensure that you will not
missed out any customizing settings.

Tcode is OX02 or Goto tcode SPRO


SPRO -> SAP Ref IMG -> Enterprise Structure-> Definition -> Financial Accounting
-> Edit,Copy, Delete, Check Company code

OKKP - Assign company code to the controlling area


OBY6 - Define company code global parameters
OB62 - Assign company code to chart of accounts

Then check the following if needed, there may be other areas depending on your
needs:

OBA4 - FI Tolerance Group for Users


FBZP - Maintain Payment program
OBYA - Inter Company code clearing if being used

+


"
" 
  

c      (        


  )
0  
-
  
    
 
 )

c    
$$ 
  
 
 )

For configuring SAP, generally three steps are required

1) create company name and address


2) creation of company code
3) currency and country setting
4) Assign company code to company

In same organisation i.e. in one company more than two company codes are
maintaing, then its better to copy from other company code from ec01, later on you
can customised/change specific settings according to client requirements.

If your want seperate setting in your own company code, that time its better to
configure by creation rather than copy
In above that is your choice and need for reqirement.

Otherwise you can upload certain data by creating company code.

 H


Now my doubt is c  2


(
" 

" 
" 

Company is the smallest organizational unit for which individual financial statement
can be drawn according to the relevant commercial law.

Company code is the smallest organizational unit for which complete, self-contained
set of accounts can be drawn up for external reporting purposes

 

Company - A company is a legal entity or a organisation which is to carry out a


business and under a company you have lot of sub companies.

For Example
Tata is a company
TCS,Tata Power,Tata Steel, is a company code under a company TATA
Under Company code you have business area associated with it where the business
areas may be scattered in different parts of the world where you can have reporting
done for different business area or you can also call it as Profit Centre.

* 


A company is the Group of company and company code is the all the companies for
which u want seperate books of accounts. Company codes are assigned to company
for consolidation purpose.

example :- reliance is the company

and RIL,Reliance infocomm,Reliance Petrochem etc are the company codes.

All these co.codes are assigned to reliance company for consolidation purpose.

!

Along with that technical difference is COMPANY cosists of 6 digit alphanumeric


key where as COMPANY CODE cosists of 4 digit alphanumeric key.

+  

Company means group company for example : Tata Group

Company code means one of the company of its group ex:


Tata Chemicals, TCS, Tata Steels etc.

H

c =

=
"

By: Tulsi

c   =


  .   
*    =
 " c    

 
=


Valuation areas are nothing but the level at which you want to valuate your materials.
SAP provides two levels of valuation Plant level and company code level.

For example:

Valuation at plant level: Suppose you have two plants one in Hissar and one in
Andhra Pradesh, Then of course you would like to valuate the rawmaterials at plant
level as because you have got transportation cost and taxes etc to account for.

Valuation at company code level:Here you valuate all your material in same way.

In One client valuation areas can either be set to plant level or company code level.
Once you have made this setting this cant be changed

Valuation classes are linked to valuation class in Tcode OBYC

If your valuation area is at plant level then in OBYC you will find a coloumn for
Valuation modifier you can provide your plant there.

For example:

Valuation Mod Valuation class Account


plant 1 3000 200130
c $
 

Valuation class it is used in FI and MM integration. It determines the g/l accounts to


be posted automatically (Ex Raw materail or Finised goods).

In material master we specify valuation class:


- for valuation class, we assign g/l accounts based on nature of transaction,
- at the time of goods receipt/ issue, stores person enters movement type,
- our a/c's will be updated automatically based on account assignment to valuation
class which is specified in material master.

c Ñ=
",+$
Œ ,Œ
 
H

Valuation class for example: Raw material, finished goods, semi-finished goods and
maintenance parts.

Movement types:
Good receipt movement type=101
Good issue to production movement type=261
Scrapping of Good movement type=551
Good delivered to customer movement type=601
Initial uploading of sctock movement type=561

Transaction key Example BSX inventory posting and GBB


Use the tcode OBYC or OMWB to get the configuration screen for MM account
assignments.

1) Good receipt against purchase order=101


Accounting entry
Inventory raw material (Debit)
GR/IR(good receipt/Invoice receipt) (Credit)

SAP entry
Tcode OBYC or OMWB
you need to update transaction key BSX with the GL code inventory of raw material
account.
Double clik to BSX and select valuation modif.and valuation class.
For GR/IR you need to select the transaction key WRX

2) Good issue to order movement type=261


Accounting entry
Raw material consumption(Debit)
Inventory of raw material (Credit)

SAP entry
The transaction key GBB need to be updated, is issued for various offsetting posting
entries. Select debit/credit indicator, general modification indicator, valuation modif
and valuation class indicator. In this case you need to update the transaction key VBR
with the raw material consumption account.

3) Good receipt is made for finished good against production order


Accounting entry
Finished good (Debit)
Change in finished good (Credit)

SAP entry
in transactionkey BSX the valuation class finished good will attach with the finished
good GL code. For change in finished good you update transaction key GBB and
general modification key AUF

4) Good issues are posted for sales movement type=601


Accounting entry
Cost of Good Sold (Debit)
inventory of Finished Goods (Credit)

SAP entry
For cost of good sold transaction key GBB is updated with general modification key
VAX

5) Good issues for Sampling Quality movement type=331


Accounting entry
Raw material consumption (Debit)
Inventory raw material (Credit)

SAP Entry
Raw material consumption is attached to transaction key GBB and general
modification key VQP is used.

6) FI-SD Account determination


Accounting entry
Customer/AR (Debit)
Revenue Account (credit)
you have to bear in mind that the customer account gets from customer master data,
all you need is to configurate the revenue account. SAP provides following 6 ways of
determining the GL accounts in SD.
- Appliation (key for sd application)
- account determination types
- chart of accounts(from FI system)
- Customer account assignment group
- Material account assignment group
- Account key

Tcode=VKOA
Maintain the GL account for the combination of Material group/account key
Double click and select new entry.
enter GL account
enter chart of account
enter material group
enter account key
enter condition type
enter application
enter sales org
click save.

That's the system look into this table see the combination and if the relevant
combination exists in tne transaction it will debit the customer account and credit the
revenue account defined.

Ñ
0  
"
 "=

H

- 
  
  
0  
(
  
   

6""
 
$
 
*)

You can post the cross company code postings even between two controlling areas.
The system does not prevent to post documents between two company codes in two
controlling area. Need not necessarily they should be under one operating concern.
Provided you have to make sure that you have followed the following points:

In OBY6 - To company codes must be assigned to same Company, meaning that you
mus thave created a Company and that company must have been assigned to these two
company codes.

OBYA - You should maintain the clearing accounts in both the company codes.
Meaning that you are posting one leg in one company code and the other leg in the
other company. Therefore, it is required to have the missing legs in each company
code.

Company Code1 - Posting Key 40 - Clearing Account

Company Code1 - Posting Key 50 - Clearing Account

Company Code2 - Positng Key 40 - Clearing Account

Company Code2 - Posting Key 50 - Clearing Account

NOTE: Need not necessarily you have to use posting keys 40 and 50, you can use the
posting keys related to vendor and customer also.

OB08 - In case if the two company codes have different local (company code)
currencies, you may maintain the exchange rates.

You can now go to F-02 and post a cross company code transaction giving the first leg
in first company code and the second leg in second company code.

Missing leg in the first company code will be posted to the GL Account mentioned in
OBYA and the missing leg in the second company code will be posted to the GL
Account mentioned in OBYA. That means you will have four line items overall.

The system will post three document.

Document 1 in First Company Code

Document 2 in Second Company Code

and

Document3 - Cross Company Code Document.

The cross company code document consists of the first company code document
number plus company code plus last two digits of the fiscal year.

" 
"  
 "


!
 
    
 !     &##)
Π 6  " 
  
 
   
  
   

  )
Do the Following Customisation :

Step 1: Check Calculation Procedure


IMG >Financial Accounting>Financial Accounting Global Settings >Tax on
Sales/Purchases>Basic Settings >Check Calculation Procedure

Tax procedures are available in SAP for most of the countries. In case a tax procedure
is not defined for your country proceed as follows:

In this go to Define Procedures Check for TaxINJ or TaxIN

If it does not exist create a new one by copying it from TaxGB

Step 2: Assign Country to CalculationProcedure


IMG >Financial Accounting>Financial Accounting Global Settings >Tax on Sales /
Purchases > Basic Settings >Check Calculation Procedure

In this step we assign the calculation procedure created in the earlier step to the
country. The country is the country of the company code.

If you are living in India, then your country of the company code is India.

Step 3. Define TaxCodes for Sales and Purchases


IMG>Financial Accounting>Financial Accounting Global Settings >Tax for Sales and
on Sales/Purchases >Calculation>Define Tax Codes

Update the following:-

Define two Zero Tax Codes input and Output Tax codes.

Go to OB40 Transaction code and Assign GL Account.

Do this your problem will be solved.

  
 ""


c    
   
   
  

 

Used tr code : H 3

On screen ³Display Actual Cost Line Items for Cost Centers´, enter cost criteria to
limit the report. To further restrict the information in the report choose the ³Further
Selection Criteria´ button.

The following screen will appear:


Under org. unit double click Business Area.
6

6- 


You used # ^ to enter the exchange rate ratio (from) and ration (to).

There are three type of Exchange rate :-

1. EURO Euro Dollar

2. M Standard translation at average rate

3. R Exchange rate for currency revaluation

" 

" 
" "


D$
" 

  
   
+ )Π 

  *  
     ND) .   $    
  
   

This will be a big task for you.

We did the same project before.

What's your strategy?

You`ll use the same client for the new currency, or you`ll have a brand new one.

What we`ve done before was creating a brand new environtment.

These were our strategies :


1. copied all the customization in a new client, no transactions and no master datas. so
you`ll have the same settings
with your live system.

2. created a new company code with the new currency, and copy all the
customization. this step was to minimize our
step in recustomization.

3. uploaded all the master datas...and started to do a new transaction. thats what we
did. and fortunately our client
was satisfied w our job:D

The suggestion is don't do that in a live system or else you`ll have a big problem then.
6- 
Π2
Ñ
"


6- 
  
(
  
,  
,   



-(  
)6- 
  
-
   )

Definition for different currencies:

Object currency - CO - A currency defined in the master record of a Controlling


object (cost center, internal order, and
so on). When you create a Controlling object, the controlling area currency is
defaulted as the object currency. You can change this.

Transaction Currency - the currency in which a business transaction is processed and


booked. The business transaction can be posted in the transaction currency as well as
in the local currency. This can occur when the trading partners use different local
currencies. The transaction currency can differ from the controlling area currency and
the object currency. The SAP system can perform currency translations using a
predefined average exchange rate.

Hard currency - Hard Currencies are used in countries with high inflation to improve
the value of transaction. When a
hard currency is selected, the document is automatically updated in the local currency
and the hard currency. The config for hard currency is done at the country level

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.

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

Parallel currency - For company code, we may have one local currency and up to two
parallel currencies in the system. All
documents are posted in both the local and parallel currencies. A hard currency is one
type of parallel currency.

 
"
2 2
 


c       


 
     
 $   
  



By : Norman

Depending upon client's requirement, you can set the control of currency decimals in
oy04.

In the DB, SAP stores all amount values with 2 decimal places. But when SAP reads
it, it interprets it based on the currency associated with the amount field.

Try the FM BAPI_CURRENCY_CONV_TO_EXTERNAL. Pass the amount


obtained from DB and the currency. This will give you back the actual interpreted
value.

c  ( 
 
(       

 
6 %2  ÿ  
ND   

Check the table TCURX.

Based on user profile you can get the currency format from USR01.

Use This Code: It takes care of decimal notation based on user profile.

What ever may be the user profile for decimal notation.

FIELD_NUM = 1,233.50

OR

FIELD_NUM = 1.233,50

OR

FIELD_NUM = 1 233,50

***************************************
SELECT SINGLE DCPFM FROM USR01
INTO VAR_DCPFM WHERE BNAME EQ SY-UNAME.

IF VAR_DCPFM EQ 'X'.
REPLACE ALL OCCURRENCES OF ',' IN: FIELD_NUM WITH ''.

TRANSLATE FIELD_NUM USING ','.


ELSEIF VAR_DCPFM EQ ''.
REPLACE ALL OCCURRENCES OF '.' IN: FIELD_NUM WITH ''.

TRANSLATE FIELD_NUM USING '.'.


TRANSLATE FIELD_NUM USING ',.'.
ELSEIF VAR_DCPFM EQ 'Y'.
TRANSLATE FIELD_NUM USING ',.'.
ENDIF.

***************************************

This code will result into :


FIELD_NUM = 1233.50

.Œ+ "
&" 
" ! 

Go to OY01

Select your country key and double click on it.

In that mention your hard currency key and index based currency keys.

Then go to ob22

IMG Menu Path: Financial Accounting --> Financial Accounting Global Settings -->
Company Code --> Parallel Currencies --> Define Additional Local Currencies

Give currencies for 2nd and 3rd local currencies.

Here you need to give 40 in the 2nd local currency and 50 for the 3rd local currency.

Exch Rate type: M


Source Curency : 1
Type of transalation: 2

SAVE
*
I am going through a decision process right now with my client regarding this
configuration. When my client first came up on SAP 9 yrs. ago, they only had 1
currency. Since then they have made acquisitions and now have multiple company
codes with different currencies. What I have found out is that once you set up a
Company code for only one currency you cannot turn on Multiple/Parallel currencies
in that company code. Fixed Assets are affected and so are all the AP & AR
transactions. AR & AP can run into issues when it attempt to create and additional
posting to the Group Currency because of Exchange Rate differences.

In my opinion, I beieve it was a major mistake not to have turned on Additional Local
Currencies from the beginning. What this does is allows you to establish a "Group
Currency" in the FI Module. In table GLT0 you can see that there are columns way
out to the right when you view postings via SE16 in columns titled AMOUNT. These
are the group currency postings. You can then generate reports that pull this detail for
consolidated reporting.

Œ&
"
$


6- 
 (   
      
  
  
 

$
)

By: Murthy

Let me explain the process in Detail. First you need to understand Process of
Revaluation. I am not going into Customisation Paths.

Valuating Foreign Currency Balance Sheet Accounts Your foreign currency balance
sheet accounts are valuated as part of the foreign currency valuation:
- The balance of the foreign currency balance sheet account, that is, the balance of the
G/L account managed in a foreign currency, forms the basis of the valuation.
- The result of the valuation is posted to the valuated account.
- The exchange rate profit or loss from the valuation is posted to a separate expense or
revenue account for exchange rate differences as an offsetting posting.

Ñ

The balance of your fixed term deposit account (foreign currency balance sheet
account) has a balance of 1000 USD and 1700 DEM (see the following illustration,
1).
An exchange rate devaluation occurs at the time of the valuation.
The account balance is now valuated with an exchange rate of 1.6300.
The valuation programs posts the exchange rate difference to the fixed term deposit
account and to the account for exchange rate differences (see following illustration,
2).

As a result of the valuation, a difference arises in your local currency. However, only
postings in the foreign currency specified in the master record (account currency) are
permitted to foreign currency balance sheet accounts. The exchange rate difference is
therefore posted with a foreign currency amount of zero, and a local currency amount
equal to the exchange rate difference.

To valuate your foreign currency balance sheet accounts, you must define expense
and revenue accounts for exchange rate differences.

=
   
  
 
 

All open items in foreign currency are valuated as part of the foreign currency
valuation:
- The individual open items of an account in foreign currency form the basis of the
valuation, that is, every open item of an account in foreign currency is valuated
individually.
- The total difference from all the open items in an account is posted to a financial
statement adjustment account. The account therefore retains its original balance.
- The exchange rate profit or loss from the valuation is posted to a separate expense or
revenue account for exchange rate differences as an offsetting posting.

Ñ

You have posted a receivable in the amount of 1000 USD, at an exchange rate of
1.7000. The local currency is DEM. The system saves the receivable in local currency
in the customer and receivables accounts (1700 DEM) (see following illustration, 1).

An exchange rate devaluation occurs at the time of the valuation and the exchange
rate is now 1.6300. The receivable in the amount of 1700 DEM remains in the
receivables account. The program posts the reduction to the receivable (70 DEM) to a
financial statement adjustment account and the exchange rate difference to the
account for exchange rate differences from the valuation as an offsetting posting (see
following illustration, 2).

The receivables account and the relevant financial statement adjustment account are
reported in one item in the financial statements. This means that the amount of the
receivable in the financial statements is the valuated amount (1630 DEM).
To valuate your foreign currency balance sheet accounts, you must define certain
accounts.
You define these accounts per reconciliation account:
- Expense and revenue accounts for the exchange rate differences from the valuation.
- A financial statement adjustment account, reported in one financial statement item
with the valuated account. The valuation is therefore not carried out in the account
itself; instead, it is posted to a separate account. This is necessary for example, since
the accounts for receivables and payables are only updated by postings to the
customer and vendor accounts. However, the valuation must be carried out in the G/L
account area for the relevant reconciliation accounts.

When carrying out a valuation of open items, you can configure account
determination according to the currency type, so that, for example, currency gains in
the local currency and in the group currency are posted to separate accounts.

You have the following options for valuating open items in foreign currency:
- Saving the exchange rate difference per document
You can define that in addition to being posted, the exchange rate differences are
saved per document.

To do this, select the indicator Valuation for FS preparations on the Postings tab.

The exchange rate differences saved in the document are taken into account for
payment clearing:

- Unrealized exchange rate differences


When you valuate open items in foreign currency, the exchange rate difference
determined is posted as an unrealized exchange rate difference.
- Realized exchange rate differences
For an incoming payment, that is, when you are clearing the open items, the current
exchange rate is determined. The unrealized exchange rate difference determined
from the line item is taken into account.

6- 
If the first valuation results in an exchange rate difference of 30 DEM, and the current
valuation results in an exchange rate difference of 10 DEM, an exchange rate
difference of 20 DEM is posted and 10 DEM is saved in the line item as the final
valuation difference.

- Reversing exchange rate difference postings


You can define that the exchange rate differences posted are automatically reversed
one day after the valuation run by an inverse posting.
You therefore have the option of determining exchange rate differences at any point in
time without this valuation being taken into account for the creation of financial
statements or for payment clearing.

To do this, select the indicator Reverse postings on the Postings tab.

&Ñ2 
 % Œ



To analyze the FI update error posting, make use of report &= 6, FI
Document: list of update termination.

Execute the report with transaction code ^ or 6^.

"#0Œ
Ñ

# 

-----Original Message-----
Subject: CO-PA Transfer of Incoming Sales Orders
From: sarita

Hi,

In IMG, I assigned
1. value fields
2. quantity fields
and activated transfer of incoming sales orders for "CO-PA transfer of Incoming Sales
Orders".

In CO-PA information system, I defined and executed a report (record type A, actual
data). The actual line item showed revenue amount 36,000. But when I drilled down
to the value fields. The system showed revenue = 0.

Do I miss something in Configuration?

Best regards,
Sarita

P.S As we are not implement PP/PC, I do not maintain "valuation using prodcut cost
estimates" in CO-PA configuration.

-----Reply Message-----
Subject: Re: CO-PA Transfer of Incoming Sales Orders
From: Peter Fisher
Sarita...

As the data is appearing in the PA tables but not on yr report. One last thing that you
can check is the whether the report is looking at current data or a 'summarisation
level'. If you are only looking at the data fm summarisation levels , then you will need
to refresh the data in the summarisation levels by running transaction KEDU.
Otherwise any new delta items will not appear in yr report.

Check this in Report change / extras / performance (v4.0a) or summarisation in V3.

Peter Fisher

-----Reply Message-----
Subject: Re: CO-PA Transfer of Incoming Sales Orders
From: Izi Rozov

Dear Sarita,

Is your operating concern costing based or account based ?


I can't think of anything else.

just to make sure lets go step by step:


1. There are transactions in the system.
2. The report is created as follows:
characteristic = customer
Key figure = revenue, COGS, order qty
variables = period from = xx.199x
period to = xx.199x
Plan/act.ind. = 0
version = not
applicable for actual
record type = A

3. Value and quantity fields were assigned in IMG under ACTUAL POSTING --> SD
INTERFACE.

If all the above is true and it still doesn't work, you should kick the computer in the
b...

Izi
-----Reply Message-----
Subject: Re: CO-PA Transfer of Incoming Sales Orders
From: sarita

Dear Izi,

Thanks for your help.

You mean, on your report , it also does not work with record type "A"? On my report,
no matter with record type "A" or "F", it does not work. For you information, I
created a new report on IDEA (SAP demo system) with the same settings, it works
with record type "A" and "F". So it might not cause by the record type.

Sarita

-----Reply Message-----
Subject: Re: CO-PA Transfer of Incoming Sales Orders
From: Izi Rozov

Hi Sarita,

The problems lies in the way you created the report. It is obvious that the system
works. You did pick up the revenue.
Did you create a basic report or a form report ? If the problem persists, send me a
detailed description of each line and
each column and I'll try to find the solution.

Izi Rozow

2
(
c  
Œ-
6-
 Œ-

c     


 (
 c  
 Œ- 
 6-
  c  

Œ-

Please read this for the same. I have mentioned prominant difference between the two.

Withholding Tax

Classic Withholding Tax (All release)


Extended Withholding Tax (from release 4)

Difference between the two


S.No Individual Function Classic
Extended
1 Withholding Tax on Outgoing payment
Yes Yes
2 TDS on Incoming
payment Yes
3 TDS at the time of
Invoice Yes
4 TDS on partial payment Yes
5 No. of withholding tax from each document Max
1 Several
6 TDS basis
- Net amount Yes
Yes
-Gross amount
Yes Yes
-Tax amount
x Yes
7 Rounding
rule Yes
8 Cash discount
consideration Yes
9
Accumulation Yes
10 Minimum/Maximum amt and
exemption Yes
11 Certification
Numbering Yes
12 Calculation Formula
Yes Yes

&ь (H 

Withholding tax is calculated and posted to the appropriate withholding tax accounts
at different stages, depending on the legal requirements in each country. As a rule,
withholding tax is posted at the same time that the payment is posted, in other words
the outgoing payment (Accounts Payable) or incoming payment (Accounts
Receivable), is reduced by the withholding tax amount.

In certain countries, such as Brazil, the Philippines, and Spain, withholding tax can or
must be posted when the invoice is posted. This means that the amount receivable or
payable is reduced by the withholding tax amount.
Extended withholding tax supports both concepts.

The key concept in extended withholding tax is the distinction between withholding
tax type and withholding tax code. While withholding tax types represent basic
calculation rules, specific features of these rules - in particular the percentage rate -
are represented by the withholding tax code. You can define any number of
withholding tax codes for a given withholding tax type.

If a particular transaction requires more than one kind of withholding tax, this is
covered in the SAP System by defining more than one withholding tax type.

When entering a line item, you can enter withholding tax data for each of these
withholding tax types.

&ь ( ! 

.Œ"
c  
Œ-

Steps for extended withholding tax :


1. Check withholding tax countries
2. Define Ex. Withholding tax types for invoice postings
3. Define Ex. Withholding tax codes
4. Formula for Ex. Withholding tax calculation
5. Assign Ex. Withholding tax types to Company code
6. Activate Ex. Withholding tax
8. Create a G/L a/C for Ex. Withholding tax
9. Define A/C for Ex. Withholding tax (DBWW)
10. Make changes in Vendor master (XK02)
11. Maintain Company Code Settings:
Path: IMG -> Logistic -> General -> Taxes on goods movement -> India -> Maintain
company code settings
12. Activate country version for specific fiscal year position
Path: IMG -> FA -> -> FAGS -> Taxes on sales purchases -> Basic Setting -> India -
> Activate country specific for fiscal year position

Π(* 

c "
=0  Œ-
  
 

c "6 =Œ?"
=0  Œ-:
  
 



Before I am going to explain what is cenvat, you have to under stand the Indian tax
Central Excise Duty (BED). It is called as basic excise duty. Every manufacturer is
liable to pay the excise duty in various kinds namely Basic Excise Duty, Special
Excise Duty, Additional Excise Duty etc.,

Just think over a product which is reached to a end user, how many manufacturing
activities are done. So to reduce the tax burden of the end user, the Govt. of India
introduce the MODVAT scheme which is now called CENVAT scheme.

Based on this, if any manufacturer purchased a material, which is duty paid, and if it
is used for his further manufacturing activity, he can avail this as credit in his book
based on the Central Excise Invoice. At the time of selling his manufactured goods,
he is liable to pay the excise duty. He can adjust the credit which he has taken into his
book and pay the rest. For example:

CENVAT availed at the time purchased various goods Rs.20,000 (EXcise duty
alone)
CENVAT payable for his product at the time sales Rs.25,000
He will pay only Rs.5000 through cash deposit in PLA.

This customizing are in SAP CIN Module. If you are having the CIN CD, go
through.

H)% 2

Good Explanation. In addition to this. The CENVAT means, Tax on Value Addition
on the goods manufactured according to Central Excise & Customs Act Difinition.
Here the value addition means the Additional Services/Activities etc. which converts
the Input in to Output, and the output is newly recognised as per the this act as
Exciseble goods. Like this the discussion
is goes on for definition.

In 4.7 SAP version, there is no CIN version seperately, it is available with Standard
SAP it self.

I hope Mr. Anil Gurjar's query is completely answered.

H
$H

6

Ñ
$   #
The Invoice Verification component is part of the Materials Management (MM)
system. It provides the link between the MM component and the Financial
Accounting, Controlling, and Asset Accounting components.

Invoice Verification in Materials Management serves the following purposes:

- It completes the materials procurement process - which starts with the purchase
requisition, continues with purchasing and
goods receipt and ends with the invoice receipt
- It allows invoices that do not originate in materials procurement (for example,
services, expenses, course costs, etc.) to be
processed
- It allows credit memos to be processed, either as invoice cancellations or discounts

Invoice Verification does not handle the payment or the analysis of invoices. The
information required for these processes is passed on to other departments.

Invoice Verification tasks include:

- Entering invoices and credit memos that have been received


- Checking the accuracy of invoices with respect to contents, prices, and arithmetic
- Executing the account postings resulting from an invoice
- Updating certain data in the SAP system, for example, open items and material
prices
- Checking invoices that were blocked because they varied too greatly from the
purchase order

An example on how to enter an Invoice Receipts :-

Transaction code +. - MM Invoice Verification and Material Valuation

X 

Document date : Date of PO Company code :

Document type : There are two standard document types in the standard system:
6 - The invoice is posted gross
 - The invoice is posted net

Posting date : Date of open period Currency :

Purchase Order : PO Number


 


  

Amount : Enter the gross invoice amount Tax code :

Enter and then click  button

Click  

 button

Click 6 0P 0P!  




a) Enter the !  
 Number and click whether 2( or " 

b) Enter the 


 and ""


Repeat Step a) and b) if you have additional G/L Account Number

There must be no Variance and Balance must always be ZERO before you can save
the entries.

%
399+Ñ" 


In order to use 1099 MISC reporting is something that needs to be configured or set
up in the vendor master records? I am trying to run the report and I don't get
anything.

To flag a vendor in SAP as a 1099 vendor, two fields need to be populated.

1. On the Control screen of the vendor master, populate either "Tax Code 1" field with
his social security number if his social security number is his tax id. or "Tax Code 2"
field with his corporate tax id. if he has been issued a corporate tax id. Input either of
the two in their correct format i.e. social security as xxx-xx-xxxx or corporate id as
xx-xxxxxxx.

2. On the Accounting Info. screen, populate the "W.tax code" field under the
"Withholding Tax" box with the value "07" if it is a US vendor or "42" if it is a
foreign vendor.

These are the two fields that specify a vendor as being a 1099 vendor.
Any posts done before this changes were implemented will not show on 1099.

You will need to run program RFWT0020 to flag 1099 items retroactively.

...and/or you can change the "Document Change rules" for BSEG-QSSHB and BESG-
QSSKZ for account type "K" so that you can change the Withholding tax code after
the line item has been cleared (i.e. after entering the required information in the
vendor master record as the user above has recommended) (Refer to OSS Note:
363650).

But if you use MIRO to post invoices, you might want to look at Note 482245 too...

In SAP v40b, the new 1099 report is RFW1099M. It is a neat report since it merges
all the three reports that are listed in the AP info system under the withholding tax.

In my system the witholding tax code field shows only one option Y (back-Up
Witholding) instead of 7 and 42. ALso it gives me message "Extended witholding tax
functionality is not active".
Do I miss some settings on the global level, or I just need to update the vendor master
records?

We are on 40b. If you do not have any w.tax code, you can create them in Tcode
OBC7. But I have seen standard w.tax code on this screen provided by SAP. Pl. note
that you may only be able to see the w.tax code on the vendor master if you are in
change mode. For some unknown reason, when you are in display mode, SAP tells
you that there are no w.tax codes.

The first report in 4.0b gives all the correct 1099 vendor numbers as well as the error
list of incorrect vendor numbers.

The second report gives all the 1099 line items by vendor posted during the year.

The third report lets you print the actual form for IRS/vendors and also lets you send
the file electronically to IRS.

You mentioned running RFWT0020 - what exactly does this do? I have the same
problem that our A/P staff did not update some vendors with the appropriate 1099
data. Now we are getting the data needed - I usually have someone in our IT dept.
create a spool manually for those vendors. Will the program above update our
vendors' transactions with 1099 info (assuming the vendor master has been updated)?

Yes. This report flags all the past vendor line items as 1099 items retroactively. FYI,
we're on 4.0b. One thing that is peculiar about this report is that on the selection
screen, you need to put 00000000 to zzzzzzzzz in the vendor number field otherwise it
does not flag any records (at least that's what it did with our records).

 #$$  "




SAP Product Costing deals with Plan Costing + Actual Costing of Finish products or
Services.

CO comprises Product Costing + cost accounting integrated with FI.

It uses Integrated Cost Accounting.

Product costing also has 2 phases depending on the Mfg Scenarios. If you are a
normal mfg comp, making goods to stock & sale, you have to first do planning of the
costs of products initilally as a STD COST of a product. This is used in many phases
in SAP CO acounting. In simple terms, you cost a product by different methods
depending on different LIFE CYCLE phases of product. These are Development of
new product. Growth stage by modifying it. Mature stage (mass prod). Decline
Retirement of that product from Mfg+Mktng)

The whole CO process starts with this PLANNED costs of products & ends with
totalling the STD Costs for Actual Production.

This is a simple Std cost Accounting system, in which the end result is calculating
Variance bet Planned & Actual & analysing those for further corrective actions.

Product costing is well integrated to FI, but only where overhead cost accounting is
used. Otherwise normally it used only for settlement.

All these actual costs of Prod are finally settled/offset to FI or Profitability segments.

SAP CO is a very vast & complicated module of all. It needs deep understanding of
the subject.

This give you an overview glimpse of SAP CO.

2
(
""



# 
c  
 
     
3) c     (  
 (
 " "
 
 Ñ

  
ÿ)Ñ

  

*
, (
 )
 
      $   
 " "
 
 Ñ

  
).  ""



# 

Ñ

  
""
= $  

 

 


4)2




 
  
 (
  
 $  
  
 

  
5). 
  
#  
  
"

#  
 

A cost center as you will know is for fixed reporting for a long time span as part of
your company structure (cost center usually = department or work center).

An internal order is used to accumulate cost for a specific project or task for a specific
time period. An internal order is therefore used for a short period with a specific
deadline.

Your internal order will usually settle to cost centers (and not visa versa) according to
the settlement rule in the order setup.

An internal order can therefore be used to group all the expenses incurred to plan and
hold a conference over a 3 month period. The order can be settled on a monthly basis
to cost centers.

When the conference is finished the order can be settled finally. The cost of the
conference will then be spread over 2 or more cost centers, but can be viewed in total
on the internal order when needed.

It is important to understand the difference between a settlement and an assessment


cycle. An assessment cycle distributes costs from one cost center to various other cost
centers. You cannot assess from a cost center to an internal order nor visa versa.
Assessment cycles are only between cost centers.

Settlements are used for orders. In the setup of each order is a "settlement rule". In
this settlement rule you tell the system to which cost centers the cost in the order must
be settled.
Typically, you will execute the following procedure at month-ends:
1. Settle all orders - this will settle all costs on orders to cost centers.
2. Run assessment cycles - Now that you have al costs against cost centers from your
orders, you can start distributing costs between cost centers with assessments.

Costs are posted to an order. When you process a purchase order you post to the
internal order and not to a cost center. The same applies to journals in FI. You will
post the costs to the order and not to a cost center. You will then settle the order on
month-ends to post to the relevant cost centers. It is very important to settle these
orders otherwise FI and CO will not
balance on your system.

Internal orders can also be used as "statistical" orders. This is also specified in the
setup of the order. You do not have to settle statistical orders. When posting costs, you
will post to the cost center and the order simultaneously. Both have to be specified
when posting journals or purchase orders against statistical orders.

 
Œ
 
Π 
# 


D $ 
 

      
     (
    
)
Π 
 * 
 
 ? 6!0 6c:/ )
2
 
   $   &5 ^^ 
       
 
 (      / ) Π   
 $(   
  

 

)Ñ (     D  

 
  /)D  $ 

  (
         
 
    ) .$,

- 
  
  (* 
 
 -).
$  

You can change the requirement of the field in the "Field Status" of the account
(Financial Accounting -> General Ledger Accounting -> Business Transaction -> G/L
Account Posting -> Carry Out and Check Documents Settings -> Maintain Field
Status Variants)

or

In transaction OB41 where you define posting keys and its "Field status". Both "Field
Status" are maybe differents, but if in one of them the field is like "required entry"
you have to change it. But if you are posting a fixed asset account, you will need this
field completed because it defines the movement you are making.

c   
# 

Settlement is nothing but offsetting the costs to the FI portion. CO objects carry costs,
which needs to be re-assignd to the G/L accounts where it comes from.

CO never generates any data, it only tracks the same onto some objects which are
analysed for definite purpose of tracking the resources which are debits in FI as costs
in G/L).

In simple words, the flow is like following -

1. Direct Costs are incurred ( like material consuption ) in form of issues to prod
orders. These are captured in G/L. Whenever you issue, consumption account is
debited. But are also debited to prod order as

Consumption...Dr
Inventory.......Cr

2. Indirect costs are incurred in form of debits to Cost centers in G/Ls. These are
actually to be allocated & absorbed in Products via Prod Orders. So it is allocated to
prod orders via diff media like costing sheet or Indirect activity allocations.
Here again Prod order is debited with some amount.

When the costs are incurred these should be transffered futher when the order is
closed or deliverd to stock.
So whenever you deliver the order, the follwing entry is generated-

Inventory....Dr
Cost of Prod /Mfg Variance.....Cr

If your Fin Goods' predetermined cost are same as that of actual costs incurred, there
will no price difference account affected. But when your plan cost ( target cost ) &
actual costs are differnet, the difference is OFFSET or SETTELLED
to price diff accout as-

Cost of Prod / Mfg Var....Dr


Price diff acc..........Cr

Note that Price diff accont is not created as COST ELEMENT.

If actual cost is less than target cost, entry would be reverse.

. 
2 $""

. 
2 $""


Ñ 

   $

 $
(  Ñ  $"")#
 Ñ 

)))

+

Go to KS02- Change Cost Center. Go to the Control Tab. Tick on the checkbox for
desired transaction activity you want to lock. Any postings made against the cost
center under locked activity/ies will not be allowed.

Œ
 ,N12)

Thank you, I knew I could block the postings but I want to somehow make the Cost
Center Look Inactive.

To explain:
In transaction OKEON (Change Standard Hierarchy) I have Green Dots for Active
CC's. The legend (attached) says a Red Dot is for Inactive CC's.

How do you do that?

+

Hi Marios, If you want to change the status to inactive, the only optioin as far as my
knowledge is concerned is to change the validity period. when you double click the
cost centre, details of cost centre will be displayed at the bottom by T code OKEON
and you will find the status of cost centre there, just right of that you will find button
to change the validity period, change the period to some future date then it turns to
inactive status.

H

Excellent! It works.

Thank you very much.

I had changed the Validity Period before but I set it to start right where the previous
time horizon ended so looking in the future this was always active.

/


"##( 
Π    
 ^ÿÿ9  
   
 &Ñ    - 
)
      
    
 "#     
 - 
 
 


    
   
 ^ÿÿ9 / 
 

   "#
( 

'
.    
( *&Ñ


 
 

 
 
 ^ÿÿ9 / 
 

   "# ( 
+
)HÑÿ5

2

D $
 
 "# 



 
 $

 

)

  

 
 ^ÿÿ9  
     
)
Π
   "# 


)

  
6

 
"# 




# 
" 
   
  $  
    ?      $
:
   c  

" (  ?  
 
:
* *  $

  
( 

  ( 
Π 
      ,  
 ^ÿÿ9)

First, if G/L account was created in FI, you can only create primary cost element in
CO.

Secondary cost element can only be created if no account exists in FI.

Second, if you created the primary or secondary cost element in CO, you have to
assign CO account assignment.
You can delete cost element in CO (KO04) if dependent objects found.

Third, when you create cost element in CO, documents would be also created in µCost
center accounting¶ and µProfit center accounting¶ when posing in FI. If no cost
element exists in CO, no related documents would be created in CCA and PCA.

2
 

 
"6


6- 
   
 (
  
  
  
 c  

- )

Primary cost elements are like materail costs, personnel costs, energy costs... where a
corresponding GL account exists in FI..to allow costs to flow...

Secondary cost elements are like production costs, material overheads, production
overheads, they can be created and administered in only CO. These are used in
internal cost allocation, overhead calculation, settlement transactions., it does not flow
to FI...

General - Cost Element


----------------------------------
Basically, cost element are carriers of costs.

Primary Cost Element


--------------------------------
When cost element carriers cost between FI and CO they are called Primary, the link
is established GL A/c = Cost element(Primary). A question may arise as to whether all
GL accounts are cost element, it again depends upon the business requirement, where
COPA is active then revenue account (GL) are also cost elements, where COPA is not
active then revenue account (GL) should not be made as an cost element.

Example....
Again cost of goods sold particularly in VAX (make to stock) is not an cost element,
where the same COGS in VAY (make to order) is a cost element. Price Difference
account should not be made as cost element.

Entry while booking expenses


Travel Expenses A/c - with Cost Centre Dr. Rs.YY
(will be a GL A/c and cost element) - entries flows to CO thru FI
To Cash A/c Cr. Rs.YY
Secondary Cost Element
-------------------------------------
When cost element carries cost with in CO, then they are called secondary cost
element.

Example.... - Take Product Costing


---------------------------------------------------
On manufacture of the goods the cost of the above product (production order) is
arrived at accumulating material cost + operational cost + overheads (%), additive
cost if any.

The cost of operation is accumulated in cost centre be it production / production


service / service cost centres, while booking FI entries.

Those operational cost has to be allocated to production order based on operational


activities carried on and its cost involved in it. Those operation activities in CO are
termed as activity types and has to link the same in KP26 with rates and cost centre
(ie., sender cost centre and receiver production order).

In order to find the production order cost, the allocation of cost from sender cost
centre to production order for the operational activities carried on and its cost
associated with it, have to be loaded, hence in CO the cost centre allocate that portion
of operational cost to production order, and this cost is carried by a cost element
(since there are no FI involvement and entries are flowing within CO by crediting
sender cost centre and debiting receiver production order a cost element has to be
created.... say "Operational Cost - Activity" the entry will be

Operational Cost - Activity (Production Order) Dr Rs.XX


To Operational Cost - Activity (Cost Centre) Cr Rs.XX
The entries are with in CO. And the cost element created is secondary since it does
not has an link with GL Account in FI correspondingly.

In CO the production order and cost centre are co object including but not limited to.

"

&'

"# Œ# Ñ !

Controlling: Controlling provides you with information for management decision-


making. If facilitates co-ordination, monitoring and optimization of all process in an
organization.
Features of Controlling: Cost Center Accounting, Activity Based Accounting, Internal
Orders, Product Costing, & Profitability Analysis.

Controlling Area: Organization unit that represents a closed system Used for
accounting purposes.

You can assign one or more company codes to one controlling area.

If you assign more than one company code to one controlling area, then you need to
note the following.

1) Consistent Chart of a/c¶s (Treat each cost element in all company codes in same
way).
2) The Operative fiscal year variants in the company codes must match the fiscal year
variant in controlling area.
3) You should execute period end closing in controlling for all company codes at
same time.
4) The system only post reconciliation posting across company codes without taxes,
which means that it cannot automatically create invoice.
5) Maintain controlling area - OKKP .
6) Maintain no. ranges for controlling documents - KANK
7) Maintain versions - OKEQ

"#Œ6 6+6 Œ""#% ŒÑ !

Cost Elements: Cost Elements Describe the origin of costs. Cost element classifies the
organization valuated consumption of production factors within a controlling area.

Primary Cost Elements: These arise through the consumption of productions factors
that are sourced externally. Primary cost elements are used for direct posting and must
be accompanied in GL a/c¶s in FI.

T-code : KA02 : The categories are follows 1) General primary cost element, 03 -
Imputed cost element percentage method 4 - Imputed cost element, target = Actual
Method, 11- Revenue elements, & 12 - sales deductions.

Secondary Cost Elements: Cost elements arise through the consumption of production
factor¶s that are provided internally i.e., by enterprise itself. Secondary cost elements
are used strictly for internal controlling posting like assessments and settlements. T-
code - ka06
Category: 12 - internal settlements, 31 - Result analyses, 41 - overhead¶s, 42 -
assessments etc. Cost Element Group - kah1

"#Œ"6 Œ6@

Cost Center¶s: Organizational Unit within a controlling area that represents a defined
location of cost incurrence. The definition can be based on 1) Functional
Requirement, 2) Allocation criteria, 3) Physical location and 4) Responsibilities for
cost.

Change Cost center hierarchy - OKEON


Creation of Cost Center - KS01

Distribution: Was created to transfer primary costs from a sender cost center to
receiving controlling objects. Distribution is primary cost elements.
Define Distribution - KSV1
Execute ³´ - KSV5

Assessment: Was created to transfer primary and secondary costs from a sender cost
center to receiving controlling objects.
During assessment, the original cost elements are summarized into assessment cost
elements (secondary cost element, category=42).

Define Assessment - KSU1


Execute Assessment - KSU5

Activity Types: Categorizes productions and services activities provided by a cost


center to the organization and used for allocating costs for internal activities to the
originates of the costs.

Creation of Allocation Cost elements - KA06


Creating/Maintaining the Activity types - KL01

Statistical key figures: Are used as the basis (tracing factor) on which to make
allocations (assessments & distributions) and to analyze structural key figures.

"" 

 Ñ
&Ñ"#

"

(    

 c  
( 

In addition to standard iteration, price calculation enables you to calculate prices as a
cost component split. This means that the output price of an activity type can be split
into a maximum of 40 cost components. These cost components represent either:

Individual cost components (such as wages, salaries, or operating supplies) or the


costs of complete cost centers (such as energy or maintenance cost centers).

The cost component split enables you to analyze which cost components are contained
in the output prices of the activity types.

You can then control cost elements, cost element groups, and also entire cost centers
in cost component splits. The corresponding cost center costs and the costs of the cost
centers providing the activity are channeled into this cost component split. For
example, if you have assigned the salary cost element to component 1 (salaries), then
the system displays the salaries (for example, for a production cost center) in this cost
component. If a plant maintenance cost center provides services to the production
center, then the salaries for the plant maintenance cost center are assigned to this cost
component.

Cost center splitting apportions activity independent costs to the activity types of the
cost center. It does this by multiplying the total of the activity independent costs by
the equivalence number of the activity type, and then dividing by the sum of the
equivalence numbers. So if there are two activities, one with equivalence number 1
and the second activity has an eqivalence number of 2, then 1/3 of the activity
independent costs will be apportioned to activity one, and 2/3 will be apportioned to
activity two.

Activity independent costs are always fixed, so any variable costs will need to be
planned as activity dependent costs.

Planned cost center splitting happens automatically when calculating the activity
price. You can view what costs will be apportioned during activity price calculation
by clicking on the Splitting menu item.

ÑG$ 
   
 
 
  
) &    
 Ñ *
  


   $  ?  : 


   

  /
 ?
 : (  
      $  
  
   )

Ñ   


   

Planned act. qty in period @ planned act. rate for period = target costs
If you have only one Activity for the cost center, then you do not need to run splitting.
Just run activity price calculation. Splitting is required only if you are allocating the
same costs to 2 or more activities.

The calculation is generally right. The other thing to check will be rounding of the
time (mins/hours) and value.

c  $Π


 H&

 $Π

u The activity type classifies the specific activities that are provided by one or
more cost centers within a company.
u If a cost center provides activities for other cost centers, orders, processes, and
so on, then this means that its resources are being used. The costs of these
resources need to be allocated to the receivers of the activity. Activity types
serve as tracing factors for this cost allocation.
u In an internal activity allocation, the quantity of the activity, such as the
number of repair hours, is entered into the R/3 System. The system calculates
the associated cost based on the activity price and generates a debit to the
receiver and a credit to the sender for both the quantity and costs. Internal
activity is allocated using secondary cost elements , which are stored in the
master data of the activity types as default values.
u You can restrict the use of the activity type to certain types of cost centers by
entering the allowed cost center categories in the activity type master record.
You can enter up to eight allowed cost center categories, or leave the
assignments "unrestricted" by entering an asterisk (*).
u The activity type category is used to determine whether, and how and activity
type is entered and allocated. For example, you can allow some activities to be
allocated directly, but specify for others that they are either not allocated, or
allocated indirectly only.

To enable internal activity allocation, you need to specify which cost centers provide
which activity types at what price. You do this in the R/3 System by planning the
activity output/prices for a cost center. Cost center/activity output planning functions
here in the same way as an additional master record.

For direct activity allocation, you enter the quantity of the activity to be allocated
manually. To enable both costs and activity to be allocated, the R/3 System has to
valuate the activity quantity allocated at the price specified by the sender for this
activity type. For a direct activity allocation, the plan price for the combination "cost
center/activity type" is used for this calculation.
You can enter the planned price either manually, or have it calculated by the system
automatically within planning. If you want to set the price manually, you need to set
the price indicator to 3 (manual). You can use this procedure if your price calculation
is not complex, for example where the prices required for your rates are determined
within your organization and do not depend on internally produced activities, or
where the rate depends on the prices of external suppliers and not on the costs of the
cost center. Automatic calculation of plan prices is covered in course AC412.

 H&

u Statistical key figures such as number of employees or length of phone calls,


are statistical values that describe cost centers, profit centers, and overhead
orders. They can also describe a value for a particular activity provided by a
cost center, such as the number of employees who make repairs at the transport
cost center (an activity-dependent statistical key figure).
u You can post both plan and actual statistical key figures.
u You can use statistical key figures as the tracing factor for periodic transactions
such as distribution or assessment, and for key figure analysis.
u You define statistical key figures as a fixed value or as a totals value:
u The fixed value (such as "employees") is carried over from the period in which
it is entered to all subsequent periods of the same fiscal year. You need enter a
new posting only if the value changes. The fiscal year total is the average of the
period totals.
u You post the totals value (for example "telephone calls") only to the period in
which it was entered. For totals values, the fiscal year total is the total of all
period values.
u You can transfer statistical key figures from the Logistical Information System
(LIS) by assigning a key figure from the LIS to a statistical key figure in Cost
Center Accounting.

"  
 

 

6- 
   


3) c 
       
, 
 
   



  
 
  ) 2)
   *  ) ")

ÿ) c 
   $   &!      
,

&
   !   * 2)
"    
 ")

Ñ
 ,    
 "  

)
Π
         
 )      &!    
, " 
  
  

  )

By Ravi :

Let¶s assume you are in a scenario where std cost = actual cost..

A. Say, RM cost is 100, labor cost is 30.. So your FG cost is 130.

B. When you issue RM, Cons a/c is Dr and Inventory a/c is Cr for 100

Labor cost is debited to prod order via a secondary cost element. This does not result
in a FI entry.

C. Now, when you do GR, entry is FG Inventory a/c is Dr for 130 and cost of
production is credit for 130 again.

This cost of prod is nothing but your sum total of RM inventory cost and labor cost....

The accounting logic here is, you have consumed one inventory (Charged to P&L)
and made another inventory....

When you consumed (RM), it is charged to P&L... So, now that you have made
another inventory (FG), the charged made to P&L is reversed and again the inventory
is Debited...

The charge reversal is done using another P&L account which is Cost of Prod a/c
instead of individual RM consumption a/c.

The idea is to show in P&L, RM consumption separately and at the same time reduce
the charge and bring back the inventory consumed in its processed form (FG)...

That¶s why, RM consumption, Cost of prod a.c, COGS a/c all are mapped to the same
group in Financial Statement version in FI and are reported together.

0
 "6&+
'


Ñ 
            
 
 
  
       

B    
   
  
Ñ 
              

!      

    "#$%$&  
''''     ''''    
   "

   Ñ                  c     
 ( 
    Ñ   '                 




There are how you can try to re-run the release cost estimate:

Reverse the cost estimate with "H3.. Select "Current cost estimate", enter Plant/Mat
No and execute.

Re-run from "H33 once reversed.

or

Use transaction "H3 to delete the Standard Cost created. In Control Parameters ,
using " Current Std Cost Estimate Tab". and execute.

After that run "H4 / "H33 again and mark and release the material.

Notes:

1. You can cancel the cost estimation through "H3 and recreate cost estimation
through "H33 .

2. But system won't allow you to release the cost twice in the same period
through "Hÿ4. That's the standard behavior of system.

3. You need to change the price manually through +ÿ3 (this is not recommended
but it is a work around).

 
,.$S0

-----Original Message-----
Subject: Report Painter, How to reverse +/- signs

Dear Report Painter gurus,

I am trying to reverse the +/- signs in my P/L statement, which I


created using Report Painter. Could someone please help me out ?

Regds,

-----Reply Message-----
Subject: Report Painter, How to reverse +/- signs

Try using the Absolute value in your formula as follows:

Ex: (X003 / ABS X002)) * 100, or whatever variables you need to use.

I find that this usually reverses the appropriate signs.

In the report, there is also formatting available that will reverse the
signs.
Do: In Report Writer: Change report screen, (transaction GRR2),
Formatting-->Row-->reverse signs.

However, this will reverse all signs in the statement. You may not want
that.

Try both to see what happens.

Hope this helps.

-----End of Message-----

( 
c

-----Original Message-----
Subject: Library for Report Painter/Writer

Hi Sappers
I just have one question regarding Report Writer/Painter
Is it possible to create new library based on whatever table we want which
is not SAP installed. For exmaple, in PCA, there is standard library
8A2 which si based on GLPCT. Is it possible to create new library based on
table say GLPCA? If so, what's menu path to add table in Library?
I am on 3.1H.

TIA

-----Reply Message-----
Subject: RE: Library for Report Painter/Writer

As consultants always say:


"Do you really want to create reports on table GLPCA?".
All the information is in GLPCT and in addition performance with reporting
on GLPCA would probably be very bad.

I wanted to get period information form PCA. And it looks like GLPCT does
not give records per period (period field is 16 or other value) but only the
cumulative values per period are stored in specific fields. So i thought I
needed a report on GLPCA, but I use libraries based on GLPTC to get the
information from GLPCA. Apparently by selecting periods (RPMAX) in reports,
SAP will show all the GLPCA records for that period, but it will get it from
the summary record in GLPCT. Don't ask me how, but it works.

hope this helps.

Regards,

-----Reply Message-----
Subject: RE: Library for Report Painter/Writer

You should be able to make a dd table available to Report Painter / Writer if you can
create an
Evaluation structure for the table.

To create an Eval structure In Logistics:


Tran MCS7 - Create evaluation Structure.
(Path: Logistics >Sales & Distribution >Sales Info System >Flexible Analysis
>Evaluation
Structure >Create)

You could name the Eval Structure "ZFGLPCA", (must begin with "ZF").
Then click <DD table ref> ( if this is a table and not another Eval structure.)
Enter the DD table "GLPCA". And click the check mark.
Then click <Characteristics> and mark all the characteristic fields you want to report
on, (if
you right click
you can <select all>), then <copy + close> <copy>.
Do the same for <Key figures>
Then generate the Eval structure <back> <yes> or <Evaluation structure> <Generate>

After you created the Eval structure, you can create a library with this Eval structure
(table) in it.

GLPCA worked for me. We are on 3.1H P47

Good Luck

-----Reply Message-----
Subject: RE: Library for Report Painter/Writer

The 'tables' that are available for use in Report Painter/Writer are stored in
client-independent table T804A. As far as I know, there is no customizing transaction
for this table (at least not in
3.1H).

Please note that the "tables" defined here are not necessarily physical tables; they can
also
be 'logical' tables which contain several physical tables, as defined in table T804E
(also
client-independent). In your example, the table delivered for PCA report Library 8A2,
'GLPCT' is actually defined in
table T804E to include data from physical tables GLPCT, GLPCA, and GLPCP.

You actually define the Library using transaction GR21/GR22. I have never actually
customized a
table definition for use in Report Painter/Writer; but it can be done through tables
T804A/T804E.

-----End of Message-----

 
, 

 (
 (

-----Original Message-----
Subject: Report Painter, changing the tables assigned to libraries

Dear Report Painter folks,


If I assign the wrong table to a Library, how
do I correct this mistake ?

Regds,

-----Reply Message-----
Subject: RE: Report Painter, changing the tables assigned to libraries

If you just created the Library and assigned an existing table to it, you
can delete the Library using Report Writer, and start over.

-----End of Message-----

 
,
  (
 ! 
 

-----Original Message-----
Subject: Report Painter,Relationship between Report Groups and Reports

Dear Report painter gurus,

What is the relationship between Report Groups and the


Reports assigned to them ? My problem is that, when I leave EMPTY
characteristics in one Report, I cannot Execute ALL other reports
assigned to the same Report Group as the First Report (the report with
the empty characteristics)

So it seems that whatever mistakes I make in one report, affects


ALL the other reports within the same Report Group. Can someone verify
this for me ?

Thanks in advance !

-----Reply Message-----
Subject: RE: Report Painter,Relationship between Report Groups and Reports

I have found that by far the safest way to proceed is to have a one to one
relation ship between a report group and a report. otherwise all sorts of
strange things start to happen.

Cheersy cheers
-----End of Message----

&Ñ&

"

 
(

c  

&Ñ"#&


&Ñ"#Œ
 

SAP FICO Functional means functional knowledge, by which one can proceed in
terms of functional process with FICO area as well as FICO configuration knowledge.

Whereas SAP FICO Technical consultant may be an ABAPER, who have short of
knowledge of FICO configuration and functional knowledge as well and can proceed
for technical jobs e.g. reports development, client requirement, system modification
etc.

Œ( . "&Ñ



 



'"
$Œ)" & 3 ( 
$
  


 


     )

Plant is not a field for finance or in sap it is FI module - this is for PP and MM
module, In case required, please define that as FI object for FI reports - like BA and
so on. Configure the plant as a BA and in all FI places you can capture BA in line
items of vendors.

Spent little time on going through various standard reports of SAP which are very rich
in itself - for each report it has options of all fields of master data , all fields of FI
document means around in my opinion around 400+ options to select. Hence we
should first get an idea of fields in masters and documents and how they are updated.

Œ(   

))))6$ 
  - but we
always look for FAST FOOD without understanding the quality of how standard is
the solutions..

Spent time in understanding - there are lot of chapters available for reading .
Suggestions ... Understand the Finance function first upto closing of books and
management reportings done in a practical way. Go to sap img screen - you will find
all options are there... If you go reverse way , sitting inside the car and asking -
anyone can help me in understanding what is the wheel in front of driver used and
how to use it??

All the best - take it in the right spirit for a successful future

& $
&

 

2

c   

  $
 c     c  c    
  

Ñ+!

There are both technical and legal reasons for archiving Financial Accounting data.

Archiving:
1) Reduces storage and runtime problems caused by the constant growth of
transaction data.
2) Makes master data easier to manage and to keep up to date.
3) Enables data to be accessed at a later date.

You can archive data no longer required in the online system using certain standard
functions. This data is then stored in archive files and deleted from the online
system. For legal and commercial reasons, it is important that you are able to access
archived data files online again, and the reloading function allows you to do this.

Data must meet certain conditions before it can be archived. Some of these controls
are already defined in the system, for instance the fact that you cannot archive
documents that contain open items. Certain other controls are user-defined.
Every archiving function can be accessed from archive management (SARA).

To reach archive management, choose:


Tools --> Administration --> Archiving or from the Accounting --> Financial
Accounting --> General Ledger, Accounts
Receivable, Accounts Payable or Banks menus --> Periodic processing Archiving
<Archiving object> .

When you access archive management from these menus, the archiving object is
defaulted by the system in the field Object name. Otherwise you must enter the name
of the archiving object manually.