Lsmw sap tool

1. LSMWstep by step?
LSMW isa tool usedtotranferdata from legacysystemtoR/3 periodicallyoronce. Itsupports
conversionof dataand Batch Input, BAPI, IDOCor DirectInput can be usedas the methodfortransferof
data. Total of 26 processingstepsare availableinLSMW, In case of data transferusingBatch Inputonly
14 stepsare required.
Execute the transactionLSMW to start transferof data, Before usingthe LSMW we shouldhave good
knowledge aboutthe businessobjectandthe fieldsthatwill be transferred.
The main screenof LSMW provides wizard-likestep-by-steptasks, To complete yourdataconversion,
youneedto execute thesestepsinsequence. Once astepis executed,the cursorisautomatically
positionedtothe nextstep.
Note that these stepsmaylookdifferentdependinguponyourPersonal menusettings.Youcouldmake
stepnumbersvisible by‘Numberson’iconorhiddenby‘Numbersoff’icon.Youcan execute astepby
double-clickingonthe row.Toggle icon‘Doubleclick=Display’or‘Doubleclick=Edit’,makesthe stepin
‘display’mode or‘change’mode.
There are 14 stepsthatare normallyusedandthese are.
1) MaintainObjectAttributes.
2) MaintainSource Structures.
3) MaintainSource Fields.
4) MaintainStructure Relations
5) MaintainFieldMappingandconversionrules.
6) MaintainFixedValues,translations,userdefinedroutines.
7) SpecifyFiles.
8) AssignFiles.
9) ReadDATA.
10) DisplayReadData.
11) ConvertData.
12) DisplayConvertedData.
13) Create Batch InputSession.
14) RunBatch InputSesion.
1) Maintain ObjectAttributes.
In thisexample,youwill be updatingthe customermasterrecordswiththe helpof recordinga
transaction(XD02).

2. a.Choose radiobutton Batch Input Recordingand
bclickon the recording overviewicon to record the R/3 transaction.
c.Enter the Recording nameasXD02_REC,the descriptionasCustomerMaster UpdatesRecording, and
d.the transactioncode as XD02(FS00 incase of gl accounts)
Once the transactionis completed,R/3recordsthe flow of screensandfieldsandsavesthe information,
2) Maintain Source Structures.
Give a name and a descriptiontothe source structure
3) Maintain Source Fields.
In thisstep,youneedto list whatfieldsare present in the source structure. The easiestwayisto click
on ‘Table Maintenance’ iconto enterFieldname,Type andLength for each field
Note that your inputfile willhave fourfieldsaskeyfieldsandyouneedtoupdate three fieldsinthe
system
4) Maintain Structure Relations
Execute a stepto ‘MaintainStructure Relations’.Since,there isonly oneSourceand Target Structure,
the relationship is defaultedautomatically
5) Maintain FieldMappingand conversionrules.
In thisstep, source/legacy fieldsineachstructure are assignedto R/3 fields.Itmay be done individually
for eachR/3 field,whichbeingtime-consumingforcomplexstructuresorwe can use automatic
mappingutility(Extras>Auto-Fieldmapping).
We can specifythe conversionrule tobe usedtoconvertan LS fieldintothe correspondingR/3field.For
this,use predefinedconversionrulesorcreate yourownconversionrulesinthe editor.
You may use the buttons‘Initial’,‘Constant’,‘Move’&‘FixedValue’toassigndifferentvalues.Youmay
alsoassigndifferentrulesbyusingthe button‘Rule’.automaticmappingutility(Extras>Auto-Field
mapping).
6) Maintain FixedValues,translations,userdefinedroutines.
7) SpecifyFiles.
In thisstep,we define howthe layoutoftheinput fileis.The inputfile isa[Tab] delimitedwiththe first
row as fieldnames. Itispresent on my PC (local drive)
Create an Excel file withyourdataandsave itas a Tab-delimitedtextfile onyourlocal drive.
8) AssignFiles.

3. Execute step‘AssignFiles’andthe systemautomatically defaultsthefilenameto the source structure.
9) Read DATA.
In thisstep,LSMW reads the data from the source file (fromyourPC’slocal drive).
10) Display Read Data.
Thisstepis optional.If required,youcanreview the fieldcontentsforthe rowsof data read
11) Convert Data.
Thisis the stepthat actually convertsthe source data(in source format) to a target format. Basedon
the conversionrulesdefined, sourcefieldsaremapped to target fields.
12) Display ConvertedData.
Againthisisan optional stepto viewhow the source datais convertedtointernal SAPformat
13) Create Batch Input Session.
Once the source data isconvertedinaninternal format,youcan create a batch sessiontoprocess
updates.
14) Run Batch Input Sesion.
You can execute the BDCsessionbyRunBatch inputsession.Executingabatchinputsessionisa
standardSM35 transactionformanagingBDC sessions.Once youhave successfullyexecutedthe batch
inputsession,the customermasterrecordsare updatedinthe system.Youcanconfirmthisby viewing
the customermasterrecords(XD03).
Note! Browsingthruthese 14 steps,youmay geta feelingthatthisisa verylengthyandtime-consuming
activity.However,forthe purposesof demonstration,Ihave made itdetailed.Althoughitlookslengthy,
actuallyittakeshardlyfewhoursfromstart-to-finish!Afterplayingaroundwithfew simple LSMW
scripts,youwill finditsoeasyto change and create more complex ones.
What is the LSM workbench?

4. The LSMW (Legacy System Migration Workbench) is a tool based on SAP software that supports single
or periodic data transfer from non-SAP to SAP systems (and with restriction from SAP to SAP system).
Its core functions are:
 Importing legacy data from PC spreadsheet tables or sequential files
 Converting data from its original (legacy system) format to the target (SAP) format
 Importing the data using the standard interfaces of SAP (IDoc inbound processing, Batch Input,
Direct Input)
Which data can be migrated using the LSMW?
 By means of standard transfer programs: a wide range of master data (e.g. G/L accounts, customer
master,vendor master,material master, bills of material) and transaction data (e.g. financial
documents, sales orders)
 By means of recording of transactions: further data objects (if the transaction can be run in batch
input mode)
Is the imported data consistent?
Yes. The data is loaded via the standard interfaces of the applications. This will include all checks that are
run for online transactions. Invalid data will be rejected.
Are conversions carried out identically across the applications?
Yes. The LSMW works on the principle of central(reusable) rules. This approach guarantees that, for
example, the material number is converted in the same way
wherever the reusable rule is used for conversion.
Is an extensive knowledge of ABAP necessary to use the LSMW?
No. The LSMW provides the main conversion techniques at the push of a button. For complex
conversions, individual ABAP coding can be added.
Do I have to migrate table by table?
No. Business objects such as material master,customer master, or FI document are migrated.
Can I transfer data that is on my PC?
Yes. The LSMW can read the data directly from your PC. Only when using the periodic interface,the
data has to be on a server accessible by the SAP system.

5. Is the LSMW part of the standard SAP system?
It depends on the release of the SAP system:
 As of SAP Web Application Server Release 6.20, the LSMW is integrated in the SAP system.
Therefore,if you are using a SAP system of this release or higher, you use the system-integrated
LSMW 'out of the box'.
 Only for releases lower than SAP Web AS 6.20, you have to install the standalone LSMW as
add-on. You can download the LSMW as add-on from the SWDC (Software Download Center)
of the SAP Service Marketplace.
Is there an extra charge for the LSMW?
No, both the integrated and standalone LSMW versions are free of charge to SAP's customers and
partners. For an explanation on 'integrated' versus 'standalone', see question above.
For which sap releases is the LSMW available?
There is an LSMW available for all SAP releases. However,it is important to make sure to use the correct
LSMW version. Newer SAP system releases (as of SAP Web AS 6.20) come with an 'integrated' LSMW.
Thus, there is no need to install an LSMW as add-on because it is already available in the system. On the
contrary, an installation of an add-on could lead to problems in this case. Only for releases older than SAP
Web AS 6.20, it is necessary to install the LSMW extra as add-on.The following table contains an
overview of the LSMW versions and the SAP releases they refer to:
LSWM
Version
SAP System Release
LSMW
4.0
As of SAP Web Application Server Release 6.20, the LSMW is
integrated in the SAP system. This integrated version is referred to
as 'LSMW 4.0'. Therefore, if you are using a SAP system as of
release SAP Web AS 6.20 or higher, you use this system-
integrated LSMW 4.0 'out of the box'.
LSMW
3.0
LSMW 3.0 is the last standalone or add-on version of the LSMW.
LSMW 3.0 is used for SAP systems with release SAP Web
Application Server 6.10.
LSMW
1.8
LSMW 1.8 is the standalone or add-on version of the LSMW used
for SAP systems with SAP Basis release 4.6.
LSMW
1.7
LSMW 1.7 is the standalone or add-on version of the LSMW used
with SAP systems with SAP Basis releases 4.0 and 4.5.
LSMW
1.0
LSMW 1.0 is the standalone or add-on version of the LSMW used
with SAP systems with SAP Basis releases 3.0 F and 3.1x.
Is there an LSM training course?

6. There is no specific training course for LSMW:
 LSMW is part of the 5-day standard training BC420
 workshops at customer site are done at customers charge
LSMW, DX, third party tools: which do we recommend to our customers?
Do you already use a third-party tool for data mapping and data conversion (e.g. for ALE) ?
 If yes: Continue using the tool (if possible).
 If no: Can you and do you wish to convert data yourself (either in the legacy system or in the SAP
system)? If yes: Use the DX Workbench. If no: Use the LSM Workbench / combination of LSM
Workbench and DX Workbench
(or a third party tool).
What support is available for LSMW?
The usual support via component BC-SRV-DX-LSM .
Can I migrate data from SAP system to SAP system via LSMW?
Generally, the LSMW is used to transfer data from legacy Non-SAP systems into SAP systems. However,
with a few restrictions, it is also possible to migrate from SAP system to SAP system:
 The export has be programmed.
 The source structures have to be defined. The fields of the source structures can be loaded from
the dictionary.
 Automatic field mapping is possible.
 The import can take a lot of time, since the data amount when migrating from SAP system to
SAP system is mostly higher than for migration from legacy systems.
 History data often cannot be built up.
Can I build periodic interfaces using LSMW?
Yes. It is possible to build periodic interfaces using the LSMW framework program /SAPDMC/SAP_LSMW_INTERFACE.
SAP123
 Articles

7. Startingwith LSMW(LegacySystem MigrationWorkbench)
By WillemHoek
INTRODUCTION
Legacy SystemMigrationWorkbenchorLSMW is SAPstandardprogram that can be usedto easilyload/
change masterdata or transactionsinSAP withoutanyprogrammingatall.It can be usedto uploaddata
at cutover,such as: openorders,contracts,materials,vendors,stockonhand,.......Itcan alsobe usedin
a productionsystemtomake changesto existingdata.Verylimitedauthorizationchecksare available on
the transaction,sothe use of it mustbe verywell controlled.
The functionalityisverywelldocumentedinthe SAPhelpfiles [help.sap.com].Below isasimple
example wherevendormastersare loadedusingrecordinginLSMW.
(Foran example onhowto loadmaterialsusingDirectInputmethodinLSMW,see thispost)
In our example,we willfollowthesesteps.
 Start program andcreate a project
 Recordthe transactiontobe usedinthe load
 Define the fieldstobe loaded
 Define conversionrulestotake place
 Define the file name
 Uploadthe file fromPCtoSAP
 Convertto correctformat
 Create and runbatch inputsession
---------------- DETAIL-----------------
Start it all byexecutingtransactionLSWM(program/SAPDMC/SAPMLSMW).Define Project/subproject
/ Object.Itis alsopossible toexportthe projecttoa textfile,tobe importedintoanothersystem.

8. Variousmethodscanbe usedto loadthe file (BAPI,ALE,recording….).We will be usingarecorded
transaction.To recordthe transaction,we give the recordinga name andtype in the transactioncode
that will be used.

9. Stepthroughthe screensas youwouldhave done itmanually.

10. A screenwill be shownwithall the fieldsthatwasrecorded.Everyfieldneedsaname.To keepitsimple,
allocate the defaultSAPname tothe fields.Make sure all the fieldsyouwanttoload/change are inthe
list.If not,re-recordthe transactionandensure youdo a dropdownor type invaluesinthe correctfield.

11. Here is a listof all the processstepsthatavailable.Inourexample,notall will be used.Those tobe used
inexample are markwitha red dot.So, we will be usingProcessStep1,3, 4, 5, 7, 8, 9, 11, 12, 13.

12. The nextscreensare the processstepsasin screenabove.
NB: Everytime youselecta processstep,youwill be indisplaymode -- firstthingtodofor everystepis
to switchto change mode byclickingthe "Display<->Change"button.
ProcessStep 1 - MaintainObject Attributes
Here the methodto be usedto load the informationisdefined.We will be usingaBDC sesssion/
recordedtransaction.Thismethodisquicktodo butnot the fastest.Forexample,if youwanttoloada
huge amountof materials,atheruse directinputmethod.

13. ProcessStep 3 - MaintainSource Fields
The nextstepisto ensure yourinputfile iscreated.The inputfile (tobe loadedinSAP) isatextfile.The
textfile caneasilybe createdfromExcel orotherdata tool.Againto keepitsimple,use same field
namesas inrecording.A settinginProcessStepXXwill ensure thatorderof columnsisnot important.

14. As can be seen– in our case we usedcomma delimitedtext.Itisgenerallybettertouse tabdelimited
formatto avoiderrors (example wheretextfieldsmaycontaincommas). If youwill be usingLSMWquite
a lot,it isbetterto geta bettertexteditorandnotusedNotepad(asshowninscreenbelow).
Back in LSMW, the fieldsinexternalfileisdefined,somake themthe same asin txtfile.

15. ProcessStep 4 - MaintainStructure Relationship
Linkbetweenrecordedfieldsandexternalfields.

16. ProcessStep 5 - MaintainFieldMappingand ConversionRules
In thisstepthe rule on where the value of the recordedfieldswill come fromisspesified.Example:
valuescancome froman external fileora constantcan be defined(forfieldsthatwill notchange).

18. Vendoraccountgroup will notbe readfromexternal file.Letsmake the fieldaconstantvalue of LIEF..

19. ProcessStep 7 - SpecifyFiles

20. Before loadingthe filefromPC,one specifiesthe structure.Inthiscase commadelimitedwereused
(although,tabdelimitedare more common).Alsothatthe firstrow containsthe header.

21. ProcessStep 9 - Read Data
Load the file intoSAPfromyourPC.
ProcessStep 11 - Convert Data
Thisappliesthe conversionrulesthatwassetup inProcessStep5. So afterthis,all the fieldstobe
loadedmustbe presentandall rulesapplied.

22. ProcessStep 12 - Display ConvertedData
It isa goodideaat thisstage to viewa sample setof the data to ensure thateverythingisok.

23. ProcessStep 13 - Create Batch Input Session
Generate a batchinputsession

24. Andprocessthe batch inputsession.
Thats it,the data shouldbe inSAP!

25. To confirmthat the data was loadedcorrectly,verifythatvendorswere loadedcorrectly.
SAPversionusedforthispost: SAPECC (ERPCentral Component) 5.0
LSMW versionused: version 4.0.0 of the LSMWorkbench from31.08.2004 (Menu:Extras> Display
Displayversion)
FREE subscription to new articles
When we publish a new acticle, get it directly in your inbox. It will be infrequent but of high
quality.

26. Oh, and as with any well managed email list, you can un-subsubscribe anytime with with just
one click.
POPULARPOSTS
SplitValuation
SAPMM Tables
Settingupsimple Release Procedure forPurchase Requisitions
LoadingMaterial Masters withLSMW Direct Inputmethod
Verybasicsof SAPExternal Service Management
Change SAPdocuments -- tablesCDHDRand CDPOS
SAPFinance Tables
SAPSD Tables
Website built by Willem Hoek
SAP is a registered trademark of SAP AG - This website is not affiliated to SAP AG or any of its
subsidiaries
What is ASAP Methodology
ASAP: Accelerated Systems Application and Products in Data Processing
All implementation projects have the the following phases:
Scoping - What is to be implemented i.e. which submodules are to be implemented some clients
may not require credit management for example. Look at the project scope document carefully it
will tell you what SAP sub-modules in SAP you should be prepared for. Usually the sales people
along with project manager do it.
As is - Here you understand the existing business processes of the client . Your BPOcollect all
the ISO-documentation (if client is ISO certified), reports and forms at this stage and you analyse
how and when the reports/forms are generated, where the data is coming from. You also do a
Level -2 training for your BPO so he is made aware of all the required transactions in SAP.

27. Once this is over BPO can start learning with the consultants help more about SAP. This is
crucial because if you miss out any transactions the BPO may forget about some of his Business
processes which may come up later. It is a good practice to ask the BPO to make flow charts to
explain business processes.
To-Be - Parallely you map these processes to SAP. Processes that you are not sure of as to
whether they are present in SAP or not you try to do a configuration of those processes, and
along with the BPO(Business process owner he is the clients employee who knows about the
clients business processes probably a middle management guy, ther can more than one), BPO
involvement is required as he may be able to tell you his requirements better. Once you do the
business modelling you will also be made aware of the gaps between as-is and to-be , here
decisons have to be made as to wether a ABAP development/system modification is required or
not and so on. Involve the BPO as much as possible and document everything it is good practice
do not be lazy about it.
Business blueprint: Here the as-is and to-be and gap analysis is explained. This is the document
that you will be using to do your configuration in the realization phase.
Realization phase: Here you do the configuration in the development server (there are three
clients -development,quality, production). You also decide on the master data format, so that
BPO can go collect the master data. You also gove ABAP specifications for forms, reports etc,
system modifications etc. Unit testing: Your BPOs and a few key users sit down and test your
configuration in your module only. It is good to test the BDCs that you need for uploading data
at this stage so you have more realistic data and your BDCs are tested.
Integration testing:
Once all modules unit testing is over then the configuration is trasported to the Quality server,
where testing for all the modules is done by BPOs and end user, this is to check if any problems
are there in integration between various modules. Once all is okay from the QA server config is
transported to the production server.
Go live preparation
Data uploading: The collected master data is checked and the uploaded into production
server(sever and client I have used interchangeably). Now you are ready for go live i.e. users can
now use the production server.
ASAP methodoligy means nothing but standard process for implementation of SAP, It consists
of 5 phases.
1. Project preperation - consists of identifying team members and developing strategy as how to
go.
2. Business Blue print - consists of identifying the client current process, reqeirement and how
SAP provides solution.
Consists of detailed documentaion

28. 3. Realization -The purpose of this phase is to implement all the business and process
requirements based on the
Business Blueprint.
4. Final Preparation - The purpose of this phase is to complete testing, end-user training,
5. Go Live and Support
All the functinal consultatns need good rapo with Abapers. right from uploading of legacy data,
devoloping customised reports, BDC's, Forms etc, here functinal consultatns need to give
guidence as to get the requried data for reports and all.. like the table name, fields etc
What is baseline configuration in sap?
Base line and Final config is the third phase in ASAP methadology. The purpose of this phase is
to implement all the business & process requirements based on business blue print. You
customize the system step by step in 2 work packages: Base Line Configuration & Final
Configuration.
- Base Line Configuration: this phase comprises the priority requirements of the enterprise,
ensuring that they can be implemented quickly. This phase can be completed without
programming or enhancements to SAP systems.
- Final Configuration: in this phase you confirm that all your requirements are met in the R/3
system. Final configuration is a transportation process that expands that base line solution.
What is a special G/Ltransaction?
Special G/L transactions are transactions that are not normal business
transactions with your business partners. These are generally shown in
different control ledgers and are not grouped with the normal transactions.
They include bills of exchange, down payments, bank guarantees, and
provisions for doubtful debts.
 Special General Ledger Transactions are transactions that logically belong to accounts in the sub-ledger (Customer /
Vendor) but are not to be posted to the corresponding G/L ReconciliationAccount defined in the master
record. Instead alternate G/L Reconciliation Accounts allow these transactions to be reported separately on the
Balance Sheet.
 Special General Ledger Transactions can be grouped into 3 basic categories.
o Bill of Exchange Related: Bill of Exchange processing is used to handle country specific requirements. R/3 provides
special reconfigured programs and screens that use the Special G/L Transaction Functionality to meet these requirements.

29. o Down Payment Related: R/3 provides special reconfigured programs and screens that handle the requests, receipt and
application of down payments. They can be used in the A/R or A/P modules and are contained on the standard R/3 A/R
and A/P menus. Down payment processing has also been integrated into the R/3 Dunning and Payment Processing
Programs.
o Other: Miscellaneous types of business transactions use Special G/L Transactions Functionality.
 There are three ways that Special General Ledger entries can be recorded in the system. The processing of these entries is
controlled by the G/L indicator on the line item being entered.
o Real Postings are part of the balance sheet. They are postings with a
freely definable offsetting entry (e.g. a down payments receipt posting).
o Statistical Postings are transactions that always post to the same offsetting account. They are typically part of the
balance sheet appendix (e.g., a guarantee).
o Noted Items (e.g., a down payment request) are postings that are intended to serve as reminders of outstanding
payments due or to be made. They are not displayed in the financial statements
 The Special G/L Indicator must be entered when the transaction is created. This enables the system to recognize the
transaction as a Special G/L Transaction.
 Posting keys and Special G/L Indicators are predefined in the system and do not need to be defined in advance. However,
they can be changed or added to satisfy the requirements of the organization.
 The posting keys 09, 19, 29 and 39 are allocated to Special General Ledger Transactions in the standard system.
 Special G/L Accounts should be specified as Reconciliation G/L Accounts for the following Account Types:
o D (Customer)
o K (Vendor)
 The Line Item Display option should be used in the alternate Reconciliation G/L Accounts but not in the regular
Reconciliation G/L Accounts (Accounts Receivable/ Accounts Payable Accounts).
 The Down Payment Request belongs to the Special G/L Class Down Payments, but is merely a noted item (i.e., a memo
entry).
 When a Down Payment Request is posted, the system creates a document containing a one-sided memo entry recorded in
the Customer or Vendor Account. A document is created, but no financial accounting entry is posted to the general ledger.
 Note that although the Special G/L Indicator for a Down Payment Request is F, the Target Special G/L Indicator is A (Down
Payment), which must be entered on the Down Payment Request entry screen
 All Down Payment Requests can be displayed in the Customer account display screen.
 If an uncleared Down Payment exists for a customer, the system will issue a warning message, which alerts the user that
the customer has made a prepayment, when a new open item is posted to that customer's account.
 As is the case with Down Payment Requests, Down Payments may also be displayed in the customer account line item
display.
 The above slide depicts the G/L Accounts to which there are postings when creating a customer down payment. The
Customer (sub-ledger) Account is also posted with the same entries as shown above in the G/L A/R Account.
 The procedure for posting down payments to vendors is similar to the one presented above.
 If the system is configured to do so, a Down Payment Request will trigger either the Dunning Program (to remind the
customer to pay) or the Payment Program (to make the payment to the vendor). In this case, the down payments are
created and posted automatically.
 The down payment is managed as a payment on account (i.e., a liability) until the open items are cleared from the invoice.
 The down payment is cleared with the final invoice. This clearing can be done automatically via the Payment Program.
 Special General Ledger Transactions - Multi-step transactions, which for reporting purposes, the system will post to a
G/L Reconciliation Account other than that defined in the Customer or Vendor master record for which the transaction is
being processed.
 Special G/L Indicator - An indictor that identifies the transaction being created as a Special G/L Transaction. It is
configured to include the alternate G/L Reconciliation Account to which the transaction should be posted.
 Alternate G/L Reconciliation Account - The G/L Reconciliation Account to which a Special General Ledger Transaction
is posted. This account is not the same as the one defined in the Customer / Vendor master record.

30.  Real Postings are part of the balance sheet. They are postings with a
freely definable offsetting entry (e.g. a down payments receipt posting).
 Statistical Postings are transactions that always post to the same offsetting account. They are typically part of the
balance sheet appendix (e.g., a guarantee).
Noted Items (e.g., a down payment request) are postings that are intended to serve as reminders of outstanding
payments due or to be made. They are not displayed in the financial statements
DepreciationKeys?
Ans)Depreciationkeys=depreciationmethod+depreciationrate.
depreciationmethodcouldbe slm(straightline method),
wdv(writtendownvalue method)etc
depreciation rate isnothingbutthe percentate like 5%,6%,etc
hence depkey= slm+ 5 %
A Depreciationkeycanbe consideredasa
box whichhousesall the depreciationmethods
You are aware that everyfixedassetkeepslosingvalueas
time progressesandthe loss of value iscalledasdepreciation.
DepreciationKeysare pre-definedmathematical functions
whichperformnumbercrunchingsoas to reduce the value of
asset(usually) withthe passage of time.
A DepreciationKeyisabundle of variousmethodsof
standardizeddepreciation. A depreciationkeycontains
a. Base method (suchas straightline depreciationetc.)
b. DecliningBalance Method ( more affectionatelyknownas
WDV method,WrittenDownValue Method)
thismenthodincludesboththe declineingbalance methodsumof the yearsdigitsmethod.the normar
decliningbalance methodof depmutipliesthe straightline% bya givenfactorusuallythe factorwould
be 2/2.5/3 whichmeansthat yourdepreciationwouldbe 2/2.5/3timesmore underthismethodas
comparedto SLM thisisjustto accelerate the intial depreciationsothatyou have earmarkedasizable
portionof your intial profits.
c. Maximum Amount Method( an arbitrarypre-defined amount
up to whichdepreciationof anassetcan be carriedout)

31. d. Multi-levelmethod( whichisa mixedbagof one or more
of the aforesaidmethods) .Usuallyithas been
mathematicallyprovedthatthe DecliningBalance Method
cannot be effectiveinwritingoff the valueof anassetin
full ( viz.reduce tozero balance) ina finite periodof
time.Inorderto avoidthiscomplication,youcanuse
multi-level methodwhicheffectsachange-overfrom
decliningbalance methodtostraightline methodunder
certainconditionspre-definedinthe depreciationmethods/
keys)
each level representsavalidityperiodforagivenpercentage rate.
e.PeriodControl Method( thistellsyouthe date on which
capitalization/de-activation,startof depreciationcould
commence withregardtoasset acquisition,additionstoit,
retirementandtransfer).
All these depreciationmethodsare bundledintoa
depreciationkeywhichisassignedtothe assetmasterrecord.
inthe class fieldof depkeywe selectthe actual method
There are manydepreciationkeysavailable andyoucan
create themtoo. Usuallytheyare country-specific.
Assignmentof asuitable depreciationkeytothe asset
masterhelpsinthe fairvaluationof assetsandprofits/
losses( throughfairestimationof depreciationof assets).
Hope it isclear.Please feel freetoshare withanyother
informationthatImighthave missedout
Functional Spec?
Functional Spec is mainly prepared for the purpose of developing the new reports(this happens only w henSAPstandard report not
achieve the client purpose) using the ABAPProgram. for ABAPers you need to give the details of the Tables , Fields and the logic
how to pickthe value and get the report.
The information contains in the functionalspecs are:
a)Document segment (BSEG): w hich contains the company code,posting keys, vendors,etc.

32. b)the line items(BKPF) consists of document type, etc.
for example: fromBSEG table you have to go to the field of BUKRS for company code, BSCHL for Posting Keys.
From BKPF table you have to go to the field of BELNR for document Number, etc.
Based on your functionalspecification the Abaper willdesign the report using his technicalspecifications.
The above are examples only to understand. There are plenty of tables & fields for FI, CO and Assets separately.
Please assign points, if the above are useful.
Functional specare basedonthe businessrequirmentandcontainsdetailsof enduserexpectationsof
the product Functionality
 documentdescribesrequestedpropertiesof inputsandoutputs
 the blueprintforhowyouwanta particularapplicationtolookandwork
 it detailswhatthe finishedproductwill do
 whoa userwill interactwithitand
 whatit will looklike
the keybenefitof writingupafuntional specisstreamliningthe developmentprocess.time and
productivityare savedduringdevelopmentstage because the programmerscanprograminsteadof also
workingoutthe logicof the userexperience
S/W or program will be developedbasedonthe functionalspecs
it consistof
1. businessrequirments- brief detail aboutthe businessprocessandthe needof yourcutomized
program/report
2. securityconsideration- whoall canhave accessto thisprogram andlevel of securitywhetherit
isat co.code level orcountrylevel
3. businessdependences- whetheristhere anyotherprocess/program shouldhave been
completedbeforethe executionof thisprogram
4. Data requirement
5. priority- whetherthe failure leadtoproductionstoppage oranyworkaround
6. error management
7. howthe program retrive the dataif itis a reportprogram
Eg:-
The requirement w as to add the vendor name to the fbl3n screen, we couldnt add this so w e w ewent fora new report with allthe
fbl3n fields + vendor name. This is a spec for the program.
DEV ID Sales tax report
Functional Team Zaid Azam
(phone)

33. SAP Dev. Team (lead) Zaid Azam (phone #)
(member) (phone #)
Phase / Priority Phase 1
Medium
The above part is just a header, w hich systemthe report is in w hat report is it i.e sales report, material reprot etc, then the
consultants name, lead name etc.
how important it is medium , low , high
Revisions
Rev. Id Rev. date Author Description
00 Initial release
1 Report definition
Basic Information
Report type 1 A/P
Report type 2 Printed
Language requirem.
Printer requirement Local printer / systemprinter
Paper requirement Landscape
Source environment: R/3
Module: FI
Suggested technique ALV / other
Triggered: Manually
Frequency: On-demand
Volume: Daily
Then in the report definition
you specify what module it is in i.e FI, MM etc
w hat subledger AP/ARetc
how often it w illbe printed etc etc ( nothing really usefullhere, just giving a business touch)
2.Functional Requirements

34. Functional Requirements
Selection Posting Date, G/l account
Narrative flow The report should list the all the transactions of the G/l account( allitems i.e open and cleared) selected on the initial
screen. It should list the vendor name and number w hen a G/l transaction is of a vendor
Assumptions / issues
Should have the capability of being exported to excell
This is the important part
here you tell w hat are the fields on the selection screen.
Then in the narative flow you should tellthe abapper w hat thre report should do like its mentioned above, eg apart fromabove get
the sales for customers who reside in California betw een the date range specified on the selection screen
3.Processinglogic
Processing logic
Step 1 Enter g/l account (HKONT) on the selection screen and run w ith or w ithout a date range Or run by a date
range only w ithout specifying a G/L
Step 2 Get the G/L number from BSIS that w as selected on the initial screen Or get all the G/ls that had postings in the posting date
( BUDAT) specified on the initial screen.
Step 3 Get the amount ( WRBTR) fromBSIS ( Open and cleared both are in BSIS)
Step 4 Take the Document Number (BELNR) fromBSIS and get the vendor number for that doc number fromBSIK ( open item),
fromBSAK ( cleared) if item is paid.
Step 8 Should get the vendor name fromLFA1 for the vendor number fromBSIK or BSAK
Step 9
Step 10
Processing Logic tells him in detail about w hich fields should come and fromw hich table( not necessary to give technicalnames and
tables, he could find that out, depends on the abbapper)
4.Output
Output
4.1 Layout
FORMAT
G/L Posting date Amount Doc type Text Doc number Pk Vendor # Name
650100 12/03/2006 500 SA Test for report 19000042342 40 10229 GMC
In the format i put an excellview of how the finalreport should look like

35. 4.2 Header elements
SAP Field Report Field Comment
BSAK _LIFNR,BSIK_LIFNR Vendor number
LFA1_NAME1 Vendor Name
BSIS_BUDAT Posting Date
BSIS_HKONT G/l account
4.3 Line item
SAP Field Report Field Comment
BSIS_WRBTR amount
BSIS_BLART Document type
BSIS_SGTXT Item text
BSIS_BSCHL Posting Key
Then i enter the fields that should be there in the report first the table name is liste then the technicalname and then the english
name. Both header and line items are sprecified.
Additional topics
Unit Test Suggestions: Same as the standard SAP report FBL3N. Only addition is the vendor name and number
Security/ Authorizations: .
Error handling
Dependencies
References
Out of scope requirements NA
2.Eg
I need one new report like in the output i need only company code, Vendor number and recon.account assigned. like as below :
Company Code Vendor Recon account
1000 90000001 156001
1000 90000002 156001
2000 90000001 156002
for the above requirement w ith the input selection criteria like as below
Company Code ( ) ( )
Vendor ( ) ( )
if you give input selection as above as required you w illget the output as given above

36. Logic should be as below :
for input selection
Company Code - BUKRS is the ABAPfield for the company code
Vendor - LIFNR
for the output
Company Code - LFB1-BUKRS
Vendor - LFB1-LIFNR
Recon account - LFB1-HKONT
You w illget the recon account details in the LFB1 table , if you give the logic as above , ABAPer w illw rite the programfor the
same.
What is subledger?Howisit linkedto GL?
A sub ledger is used for tracking individual items and
transactions separate to the General Ledger (GL). Sub-
ledgers may exist for, but are not limited to Accounts
Receivable (AR), Accounts Payable (AP), Inventory and Fixed
Assets etc. Without a sub-ledger individual customers or
inventory items would require their own GL code making the
GL unnecessarily large. Sub-ledgers also allow for more
specific detail to be included in transaction details. Each
sub-ledger links to the GL by way of a control account
(e.g. Debtors control the AR sub-ledger etc.). The total of
the sub-ledger account should equal the balabce in the
control account at all times. Individual transactions
should be posted via sub-ledger not directly to the control
account. Reconciliations should be performed between the
sub-ledger and control account on at least a monthly basis
to ensure this is the case.
GL accountpostautomaticallyonlycheckBox?
When you post documents in SAP, there are instances where the systemalso adds some more line items (such as tax, cash
discount, gain/loss fromforeign exchange transactions, etc.) besides the ones you have entered in the document. This helps to
reduce your w ork as the systemcalculates these automatically. How ever, you need to define accounts you w ant the systemto
automatically post to; this will ensure that no manual posting is allowed to any of these accounts.
Post automatically checkbox is valid for only actual postings.
You can choose post automatically for w ithholding tax accounts, GR/IR clearing accounts, all sales tax accounts, discount accounts,
consumption accounts. etc
for all these accounts you are only posting automatically, means you are not giving the posting key and GL account w hile posting

37. any transactions.
In the GL master record a checkbox exists w here in the automatic posting option is selected called " Post automatically only".
Stock and consumption accounts of GL accounts that should be automatically posted.
Stock and Consumption accounts (Inventary Raw Materials) you can select post automatically.
If you set this indicator this account can only be posted to by the systemusing account determination tables.
What is a Sortkey?What r the differenttpesof SortKeys u havein SAP(FICO)
sort Key: When u post the line item in GL account, the field
called Assignment is populated, and when u run the report of
the GL Account ( GL account line item report), the system by
default sort the value specified assignment field.
`001 Posting Date
`012 vendor no
`014 Purchase order
`018 Asset number
`031 Customer number
Why we are using sort keys.
Straight answer to this is sort key offers great help in
Automatic Clearing.
First we understand how does it function. If you have
created Bank GL and there you have used 001 (posting date)
as sort key then whenever you make entry for that bank Gl
your sort key "Posting date" is automatically updated
in "Assignment" field unless you manually insert anything
in assignment field.
Let's take a simple example for why sort keys are helpful.
Suppose, there is GR/IR account created with sort key 014
(Purchase Order) so at the time of
1. Goods receipt Purchase order with item no will
automatically filled in assignment field.
Inventory dr. 15000
GR/IR cr 15000.

38. In GR/IR account item Assignment would be 150000 10.
2. Invoice through MIRO will also feed Purchase Order with
item no in assignment field.
GR/IR dr . 15000
Tax dr. 5000
Vendot cr. 20000
In GR/IR account item Assignment would be 150000 10.
Now your entry is over. There are large number of such
entries posted in the period for the GR/IR account.
So, manual clearing becomes very tedious for GR/IR clearing
account. In order to avoid that Automatic Clearing program
is configured in OB74, where you give field ZUONR i.e.
assignment in first criterion. So, line items with same
assignment and amount will be cleared automatically upon
F.13 transaction.
AccountAssignmentModel?
‘Account Assignment Model’ is a ‘reference method’ used in document entry when the same
distribution of amounts to several Company Codes, cost centers, accounts, etc., is frequently
used. Instead of manually distributing the amount among accounts or Company Codes, you
may use equivalence numbers for distributing both the credit and debit amounts. A cross-
Company Code account assignment model can also be created.
The account assignment model may contain any number of GL accounts. The GL account items
need not be complete. The model can be used across several Company Codes, and can even
include Company Codes from non-SAP systems.

39. Figure 31: Account Assignment Model
 You can use the account assignment model while ‘parking’ a document (but you cannot use a
‘reference document’ for ‘parking’).
 The use of account assignment models is limited to GL accounts.
Unlike a ‘Sample Document,’ an account assignment model may be incomplete and can be
completed during document entry by adding or deleting or changing the data already saved in
the model.
What are the MonthEndClosingActivitiesinFinance?
1. Recurring Documents.
a) Create Recurring documents
b) Create Batch Input for Posting Recurring Documents
c) Run the Batch Input Session
2. Posting Accruals or Provisions entries at month end

40. 3. Managing the GR/IR Account-Run the GR/Ir Automatic Clearing
4. Foreign Currency Open Item Revaluation-Revalue Open Items in
AR.AP
5. Maintain Exchange Rates
6. Run Balance Sheets –Run Financial Statement Version
7. Reclassify Payables and Receivablesif necessary
8. Run the Depreciation Calculation
9. Fiscal Year Change of Asset Accounting if it is year end
10. Run the Bank Reconciliation
11. Open Next Accounting Period