General settings
Countries
T005 Countries
Currency
TCURC Currency codes
TCURR Wisselkoersen
TCURT Currency name
TCURX Decimal places for currencies.
Unit of measure
T006 Units of measure
Calendar functions
T247 Month names
TFACD Factory calendar definition
T015M Month names
TTZZ Time zones
TTZD Summer time rules
TTZDF Summer time rules (fixed annual dates)
TTZDV Summer time rules (variable dates)
TTZDT Summer time rules texts
TTZ5 Assign Time Tones to Countries
TTZ5S Assign time zones to regions
Dec 16, 2008
Dec 4, 2008
Fico Interview Questions
Sap Training Center California FICO Module
Click below link to find more about fico interview questions
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
Click below link to find more about fico interview questions
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
how transactions and balances are assigned to profit centres
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
Sap Training Center California FICO Module
How transactions and balances are assigned to profit centres Describing how transactions and balances are assigned to profit centres
Module
Element / Item
Comment
Default
any unassigned item
One of your first steps in PCA configuration is to define the dummy profit centre. If the system at any stage cannot identify a profit centre from your configuration, then it will post to the dummy profit centre instead.
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
CO
Controlling Area
The first time you do anything in CO (IMG or user menu), the system will prompt you to choose a controlling area. This defines the environment for all further CO work. All profit centres will therefore be created relative to one and only one controlling area.
MM
Plant / Material (see Sales Order substitutions too)
The profit centre is defined on the material master record in the Sales: General/Plant Data or Storage views. Don’t panic - there are tools to do ‘fast assignment’ of material masters by plant and then by material type, a material group or a product hierarchy. See IMG.
These assignments are used :
to propose a default profit centre when you create a sales order item or a production order (to eventually post the revenue or costs); or
to derive the profit center from the material master for internal goods movements (such as stock transfers or goods issues) and profit-related postings in Materials Management (such as inventory differences) if no other assignment is available; or
when material stocks (raw material, finished and semi-finished goods) are transferred to Profit Center Accounting (PCA can do some balance sheet item reporting at period end).
SD
Sales Order substitutions
The sales order default is taken from the profit centre on the delivering plant / material master combination. If you do not want this, you can define substitutions to override this. A substitution is basically where the system allows you to specify your own piece of conditional logic to determine which profit centre to post to. You can base your conditions on a variety of fields available on the Sales Order. Usually used if you want to base your mapping on Sales elements rather than on products.
Business Transactions - ignore !!
The next 4 menu options in the IMG are to do with assigning an individual business transaction to the profit centre. This is something that should happen at the time of entering the business transaction if it cannot be determined from the default. Therefore for configuration purposes, I suggest you ignore the “assign to sales orders, production orders, process orders, CO Production orders”.
Master data assignments:
The next 6 menu options in the IMG relate to master data assignment to a Profit centre. Basically the profit centre should be assigned when you create the master data record. Some special comments :
Cost Centre
If not done manually, there is a ‘create profit centres’ from cost centres program which will create an equivalent hierarchy for you - only really possible at start up of the system - thereafter manually maintained. I suggest that if you do have such a one to one mapping then the following is probable:
you have too many profit centres or not enough cost centres - their business definition should be different
if you are not using SD, then maybe you don’t need profit centres?
Fixed Assets
Implicitly assigned by assigning every asset to a cost centre.
Assignments needed for Balance Sheet Items in Profit centres
FI
AR Debt
System will determine from the assignments made on the Sales Order - similar to business area processing.
FI
AP Payables
are assigned to the profit center of the material ordered for purchase orders to warehouse and to the profit center of the posting for orders which receive direct postings.
FI
Other Balance Sheet Items not in a submodule
The profit centre is actually specified by individual GL journal line item (like the business area). It is not possible (other than by substitution) to assign a GL account to a profit centre.
CO
Work in process
Assigned via the relevant project or order.
AM/IM
Assets
Implicitly assigned by assigning every asset to a cost centre.
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
MM
Material stocks
Assigned to profit centers via their master records (see above)
What is CO-PA Profitability Analysis
Sap Training Center California FICO Module
In CO-PA it is possible to ‘derive’ relationships for use in CO-PA. This could be useful for groupings that are only required for CO-PA reporting.
The derivation could be of entirely new elements or fields that are not being used elsewhere, or perhaps using an existing SAP field that is not being used by other modules. The derivation can be based on any or a combination of fields in the data that is being passed to CO-PA. A sophisticated example might be a derivation based on the SD Customer hierarchy.
It is not a good idea to try ‘overwriting’ values assigned in other modules as this would be confusing and complicate any reconciliation attempts.
See the configuration documentation on CO-PA for more information. Note that there are ’standard derivations’ that the system does too. We were talking here about creating new derivations
In CO-PA it is possible to ‘derive’ relationships for use in CO-PA. This could be useful for groupings that are only required for CO-PA reporting.
The derivation could be of entirely new elements or fields that are not being used elsewhere, or perhaps using an existing SAP field that is not being used by other modules. The derivation can be based on any or a combination of fields in the data that is being passed to CO-PA. A sophisticated example might be a derivation based on the SD Customer hierarchy.
It is not a good idea to try ‘overwriting’ values assigned in other modules as this would be confusing and complicate any reconciliation attempts.
See the configuration documentation on CO-PA for more information. Note that there are ’standard derivations’ that the system does too. We were talking here about creating new derivations
basic configration of asset accounting setup sap fico
This article presents a very basic bare-bones asset accounting setup. It assumes familiarity with SAP configuration terms and concepts.
Setup company codes to be used for asset accounting.
1. Copy chart of depreciation. [Transaction EC08]
2. Set default tax codes for non-taxable transactions which require tax code. (Impt., errors often rise because this step is omitted)
3. Setup asset classes.
4. Set no posting to G/L for all classes except book depreciation (this is the typical setting)
5. Enable posting of unplanned depreciation and any other special postings (e.g. revaluation)
6. De-activate depreciation areas not required
7. Setup account assignments for all the asset classes. Note that the minimum accounts required are a balance sheet account for asset cost, for accumulated depreciation, and a P&L account for asset depreciation expense. [Transaction AO90]. Additional accounts that will be required are the gain/loss on sale and asset scrapping accounts. Note that more than 1 asset class can share the same account assignment.
8. Assign how depreciation posts to cost centers [Transaction OAYR]
9. Assign asset balance sheet A/Cs to profit centers if required [Transaction 3KEH]
10. Allow revaluation postings for selected company codes with revaluation [Transaction OAYR]
11. Run program RACHECK1 to eliminate inconsistencies between company code and asset management account data
12. Set document types for postings: (setting for transaction types). Suggested document types below:
AA Asset acquisition AS Asset disposal AT Asset transfer AX Asset reversal AF Asset depreciation [Transactions A071, OBA7]
13. Specify transfer of APC values [Transaction OABC]
14. Specify rounding of figures for net book value to nearest whole dollar [OAYO], table T093B
15. Setup depreciation keys as necessary: [Transactions AFAMA]
0000 No depreciation and no interest SLFD Str.line frm acq.value to 0 w/o int. frm start day
-Base method 11: Ordinary straight line using % from life to end of life
SLFM Str.line frm acq.value to 0 w/o int. frm start mth
-Base method 11: Ordinary straight line using % from life to end of life
16. Switch on only the required depreciation areas [Transaction OAYZ]
- Enter default depreciation keys for these 2 asset classes
17. Setup asset number ranges in production client [Transaction AS08]
Additionally, specify company independent number ranges that refer to a base company if necessary [Transaction AO11]
18. Check FI document number ranges for asset postings
19. Check that all asset G/L accounts have tax code and account groups correctly setup
20. Define screen layouts for each asset class as per user requirements
21. Set inter-co transfer methods (Maintain view [V_T093A_05])
Indicator: Transfer with historical values This indicator controls how the system treats transfers between affiliated companies. If this indicator is set, transfers in this depreciation area are not identified as acquisitions or retirements. Instead they are identified as transfers (particularly in the asset history sheet). In addition, posting of the transfer is gross (that is, with historical acquisition costs and depreciation).
Note:
This indicator has the affect described above only if it is used in combination with these two indicators in the definition of the transaction type: ‘post to affiliated company’ ‘gross’ Maintain view [V_T082I_01] for inter-company transfer settings
Optional-Revaluation Setup (Under special valuation section os AA IMG)
22. Set revaluation of cost and accumulated depn for all areas [OABW]
23. Define revaluation measures. (key, description, depreciation areas and posting data).
24. Specify G/L accounts for revaluation of asset acquisiton cost
25. Maintain transaction types for asset revaluation postings if necessary
Setup company codes to be used for asset accounting.
1. Copy chart of depreciation. [Transaction EC08]
2. Set default tax codes for non-taxable transactions which require tax code. (Impt., errors often rise because this step is omitted)
3. Setup asset classes.
4. Set no posting to G/L for all classes except book depreciation (this is the typical setting)
5. Enable posting of unplanned depreciation and any other special postings (e.g. revaluation)
6. De-activate depreciation areas not required
7. Setup account assignments for all the asset classes. Note that the minimum accounts required are a balance sheet account for asset cost, for accumulated depreciation, and a P&L account for asset depreciation expense. [Transaction AO90]. Additional accounts that will be required are the gain/loss on sale and asset scrapping accounts. Note that more than 1 asset class can share the same account assignment.
8. Assign how depreciation posts to cost centers [Transaction OAYR]
9. Assign asset balance sheet A/Cs to profit centers if required [Transaction 3KEH]
10. Allow revaluation postings for selected company codes with revaluation [Transaction OAYR]
11. Run program RACHECK1 to eliminate inconsistencies between company code and asset management account data
12. Set document types for postings: (setting for transaction types). Suggested document types below:
AA Asset acquisition AS Asset disposal AT Asset transfer AX Asset reversal AF Asset depreciation [Transactions A071, OBA7]
13. Specify transfer of APC values [Transaction OABC]
14. Specify rounding of figures for net book value to nearest whole dollar [OAYO], table T093B
15. Setup depreciation keys as necessary: [Transactions AFAMA]
0000 No depreciation and no interest SLFD Str.line frm acq.value to 0 w/o int. frm start day
-Base method 11: Ordinary straight line using % from life to end of life
SLFM Str.line frm acq.value to 0 w/o int. frm start mth
-Base method 11: Ordinary straight line using % from life to end of life
16. Switch on only the required depreciation areas [Transaction OAYZ]
- Enter default depreciation keys for these 2 asset classes
17. Setup asset number ranges in production client [Transaction AS08]
Additionally, specify company independent number ranges that refer to a base company if necessary [Transaction AO11]
18. Check FI document number ranges for asset postings
19. Check that all asset G/L accounts have tax code and account groups correctly setup
20. Define screen layouts for each asset class as per user requirements
21. Set inter-co transfer methods (Maintain view [V_T093A_05])
Indicator: Transfer with historical values This indicator controls how the system treats transfers between affiliated companies. If this indicator is set, transfers in this depreciation area are not identified as acquisitions or retirements. Instead they are identified as transfers (particularly in the asset history sheet). In addition, posting of the transfer is gross (that is, with historical acquisition costs and depreciation).
Note:
This indicator has the affect described above only if it is used in combination with these two indicators in the definition of the transaction type: ‘post to affiliated company’ ‘gross’ Maintain view [V_T082I_01] for inter-company transfer settings
Optional-Revaluation Setup (Under special valuation section os AA IMG)
22. Set revaluation of cost and accumulated depn for all areas [OABW]
23. Define revaluation measures. (key, description, depreciation areas and posting data).
24. Specify G/L accounts for revaluation of asset acquisiton cost
25. Maintain transaction types for asset revaluation postings if necessary
SD-FI Account Determination and Postings
SD-FI Account Determination and Postings
This is known in the IMG as "revenue account determination", but it covers a
lot more than that (discounts, taxes etc). This is what determines how the financial
impact of your SD Billing document is posted into the FI General Ledger.
The integration is controlled both in SD and in FI.
In SD there is a awesome area of configuration called the pricing procedures.
The pricing procedure determines the final price quoted to the customer for a particular
product. This could be a complicated calculation taking into account the base price,
any special prices or discounts that may apply to that scenario, taxes, freight charges
etc. These prices or charges are called ‘condition types’. This condition technique is used in
a number of areas of SAP.
For now all we need to know is that each condition type is assigned to an account key
(or in the case of rebates two account keys). You can assign multiple condition
types to the same account key. There are a number of account keys that are pre-defined in
the system. For example:
ERF freight revenues
ERL revenues
ERS sales deductions
EVV cash settlement
MWS sales tax
Now we start getting to the integration by mapping the account keys to GL
accounts. But it is not as simple as that. It can be as flexible (ie: as complex) as
you want. Start off with the most simple approach. Generally if one is using a good
sales / revenue reporting tool (eg: CO-PA) then one does not need a lot of flexibility and
variety in the GL accounts that are posted to. The level of detail that you need in
GL should be determined by your financial statement reporting requirements - you may end
up with only one Revenue account - it is a good bet!
So, taking the simple approach we would ignore most of the configuration possibilities
: procedures, access sequences, condition tables etc (Yes it is that ‘condition
technique’ kicking in again. Once you have worked through it once in one area and
encounter it in another then hopefully you will be comfortable in knowing that most of the
standard configuration can be left as is. )
We have to decide which access sequences we want to use (Five access sequences are
defined in the standard SAP R/3 System). To keep it simple, let us assume we just use one
- for example: the access sequence "chart of accounts/sales org./account keys".
The chart of accounts part is standard in all account determinations, so let us look at
the rest. This access sequence allows us to specify different GL accounts for
different Sales Organisations.
So if we had a billing document line item where the customer had some special
deductions for one of the products he purchased, we could map accounts by Sales
Organisation. To make it even simpler a document is within one Sales Organisation so
we have an overall mapping as follows:
SD Line Item Condition type SD Amount Account Key Sales Organisation GL Account
1 Sales deduction for being such a nice guy $10 ERS 1000 800010 - Sales deductions for 1000
Sales deduction for special promotion on particular product $15 ERS
Base Revenue $200 ERL 800000 - Revenue for Sales Org 1000
Total for item 1 $175
2 Base Revenue $100 ERL 1000 800000 - Revenue for Sales Org 1000
Total for item 2 $ 100
Document Total $ 275
So the invoice that the customer gets (and that you can view in SD) will look something
like:
Item (Note this is the SD Invoice line item) Amount
Item 1: $175
Item 2: $100
Total owing , 30 days terms etc: $275
The GL document posting that the system will make to FI will look something like this
though:
FI Line Item Debit / Credit Account Amount
1 Debit (PK=01) Customer (AR Account) $ 275
2 Credit (PK=50) Revenue (GL Account) -$ 300
3 Debit (PK=40) Sales Deduction (GL Account) $25
Balancing to 0 as all GL
documents must….
$0
Note : There is no direct relation between an SD Line item and an FI Line Item
- they are different things.
Other considerations:
Remember that if you are using business areas, then depending on your configuration
there, the system may create additional FI line items if it needs to post to different
business areas. This may be even more of a reason why you do not need additional GL
accounts. If your Sales Organisations already map to different business areas, you
could use the GL accounts for all Sales Organisations.
Different access sequences will allow a broader variety of GL accounts (for example: by
customer account) group. I strongly suggest having a good understanding of the reporting
requirements expected to be supported from the General Ledger vs the SIS (Sales
Information System) or CO-PA (Profitability Analysis) or (CO-PCA) Profit Centre
modules before you create too many GL accounts. At the risk of repeating myself, the
SD to FI account determination should only be as detailed as your statutory reporting
requirements. The reporting from other tools like Profitability Analysis are
so much more flexible and powerful, you may never look at the General Ledger for internal
profit reporting again except to do a reconciliation check.
This is known in the IMG as "revenue account determination", but it covers a
lot more than that (discounts, taxes etc). This is what determines how the financial
impact of your SD Billing document is posted into the FI General Ledger.
The integration is controlled both in SD and in FI.
In SD there is a awesome area of configuration called the pricing procedures.
The pricing procedure determines the final price quoted to the customer for a particular
product. This could be a complicated calculation taking into account the base price,
any special prices or discounts that may apply to that scenario, taxes, freight charges
etc. These prices or charges are called ‘condition types’. This condition technique is used in
a number of areas of SAP.
For now all we need to know is that each condition type is assigned to an account key
(or in the case of rebates two account keys). You can assign multiple condition
types to the same account key. There are a number of account keys that are pre-defined in
the system. For example:
ERF freight revenues
ERL revenues
ERS sales deductions
EVV cash settlement
MWS sales tax
Now we start getting to the integration by mapping the account keys to GL
accounts. But it is not as simple as that. It can be as flexible (ie: as complex) as
you want. Start off with the most simple approach. Generally if one is using a good
sales / revenue reporting tool (eg: CO-PA) then one does not need a lot of flexibility and
variety in the GL accounts that are posted to. The level of detail that you need in
GL should be determined by your financial statement reporting requirements - you may end
up with only one Revenue account - it is a good bet!
So, taking the simple approach we would ignore most of the configuration possibilities
: procedures, access sequences, condition tables etc (Yes it is that ‘condition
technique’ kicking in again. Once you have worked through it once in one area and
encounter it in another then hopefully you will be comfortable in knowing that most of the
standard configuration can be left as is. )
We have to decide which access sequences we want to use (Five access sequences are
defined in the standard SAP R/3 System). To keep it simple, let us assume we just use one
- for example: the access sequence "chart of accounts/sales org./account keys".
The chart of accounts part is standard in all account determinations, so let us look at
the rest. This access sequence allows us to specify different GL accounts for
different Sales Organisations.
So if we had a billing document line item where the customer had some special
deductions for one of the products he purchased, we could map accounts by Sales
Organisation. To make it even simpler a document is within one Sales Organisation so
we have an overall mapping as follows:
SD Line Item Condition type SD Amount Account Key Sales Organisation GL Account
1 Sales deduction for being such a nice guy $10 ERS 1000 800010 - Sales deductions for 1000
Sales deduction for special promotion on particular product $15 ERS
Base Revenue $200 ERL 800000 - Revenue for Sales Org 1000
Total for item 1 $175
2 Base Revenue $100 ERL 1000 800000 - Revenue for Sales Org 1000
Total for item 2 $ 100
Document Total $ 275
So the invoice that the customer gets (and that you can view in SD) will look something
like:
Item (Note this is the SD Invoice line item) Amount
Item 1: $175
Item 2: $100
Total owing , 30 days terms etc: $275
The GL document posting that the system will make to FI will look something like this
though:
FI Line Item Debit / Credit Account Amount
1 Debit (PK=01) Customer (AR Account) $ 275
2 Credit (PK=50) Revenue (GL Account) -$ 300
3 Debit (PK=40) Sales Deduction (GL Account) $25
Balancing to 0 as all GL
documents must….
$0
Note : There is no direct relation between an SD Line item and an FI Line Item
- they are different things.
Other considerations:
Remember that if you are using business areas, then depending on your configuration
there, the system may create additional FI line items if it needs to post to different
business areas. This may be even more of a reason why you do not need additional GL
accounts. If your Sales Organisations already map to different business areas, you
could use the GL accounts for all Sales Organisations.
Different access sequences will allow a broader variety of GL accounts (for example: by
customer account) group. I strongly suggest having a good understanding of the reporting
requirements expected to be supported from the General Ledger vs the SIS (Sales
Information System) or CO-PA (Profitability Analysis) or (CO-PCA) Profit Centre
modules before you create too many GL accounts. At the risk of repeating myself, the
SD to FI account determination should only be as detailed as your statutory reporting
requirements. The reporting from other tools like Profitability Analysis are
so much more flexible and powerful, you may never look at the General Ledger for internal
profit reporting again except to do a reconciliation check.
Sap Fico Automatic payment Run
sap learning centre sapskills.blogspot.com
How To Run Automatic Payment
Procedure on how to run automatic payment. Just follow these steps and you will be fine.
Automatic Payment program ( /nF110)
Db Inventory 100
Cr Vendor 100
Db Vendor 100
Cr Cash Clearing A/c 100
Db Cash Clearing A/c 100
Cr Bank A/c 100
1. To create a Cash clearing GL Account(A/c no. 113104) in (/nFS00)
- Make sure you check Open Item Manage and Line item Manage.
2. Goto /nF110
- in the Menu, Environment -> Maintain Config
then you will see:
- All company codes
- Paying company codes
- Payment methods in Country
- Payment methods in Company code
- Bank Determination
- House Banks
Do no changes for the All company codes, Paying comapany codes and Payment methods in country.
In the Payment methods in comapny code give your companies Address in the Form View field.
Then go to House Banks.
Give your Company Code and hit enter
Select the company code 3000 with Currency as USD and copy it give your own.
House bank:
Hit enter and then say copy all and then give your:
- Account ID
- Bank account Number (9 digits) :
- G/L account no:(cash account 113100)
Then save it and you will get 1 entries copied.
Select Bank Determination and then give your compnay Code and then select
- Ranking order with Pmt Type C and Currency USD , then change the House Bank from 3000 to your House bank no.
- Bank Account select 3000 C USD 3000 113101 and then copy it and give your information
vp02 C USD VP02 113104
and save it
-Available Amounts select 3000 3000 5 USD
999999 9999999 and then copy it to
vp02 vp02 5 USD
999999 9999999
and save it
Ignore Value date and Expense/Charges.
Next Step is to create Check Lot
Goto /nf110
Enviroment -> Check information -> Number Ranges
Give your information
Paying Comapany code:
House Bank:
Account ID:
and then click on change icon(pencile icon)
then click on create, give the following information
Lot Number:001
Check Number:
To:
Short Info:
and save it.
and next is to go to /nse38 and give the program name RFFOUS_C
Note:
RFFOUS_C(to remember, US-Check) is the one you compied in Payment Methods in country under the Environment -> Main Config
Then check on variant and click on change give your variant(VP02) and select copy from CHECK to your variant
(VP02)
and then click on change
and give the following information:
Program run date: (blank)
Identification Feature:(blank)
Paying Comapany Code: VP02
House Bank:VP02
Account ID: VP02
Check lot number:001
Printer: LP01 and check Print Immediately
give Number of sample printouts : 0
and then click on variant Attributes (give your own variant) then save it
Now give /nf110
Rundate:09/21/2006
identification:vp02
In the parameter tab,
Company code Pmt method Next P/date
VP02 C 09/30/2006
Vendor: 1 to 999999
In the Additional Log tab,
select check
Due date check
Pmnt methoed selection if not succesfull
Line items of hte payment documents
In the print out/data medium tab,
Program Variant
RFFOUS_C VP02
and then save it
and then go to status tab and you will see parameters have been
entered.
then click on proposal,
start date: check start immediatly
start time:
and then execute it
Hit enter key till you get started, running and created.
Go to edit -> proposal -> Proposal List
See whether your proposal is been executed without errors.
Note:
If there is error goto edit -> Proposal -> delete proposal.
Not due ones are not payed.
and then go back
and then click on payment run and execute it with start immediatly hit enter till it is 2 generated and 2 completed.
Then click on Printout execute it and then give your Job name(change the last ? to 1) in the status bar you will see your job name to be scheduled.
Make sure the payments are don in /nfb02
giving the document number(2000000000) and make sure
2000000000 ZP (amount)
2000000001 ZP (amount)
Then go to /nsp02, to see the print outs preview.
Its all done.
How To Run Automatic Payment
Procedure on how to run automatic payment. Just follow these steps and you will be fine.
Automatic Payment program ( /nF110)
Db Inventory 100
Cr Vendor 100
Db Vendor 100
Cr Cash Clearing A/c 100
Db Cash Clearing A/c 100
Cr Bank A/c 100
1. To create a Cash clearing GL Account(A/c no. 113104) in (/nFS00)
- Make sure you check Open Item Manage and Line item Manage.
2. Goto /nF110
- in the Menu, Environment -> Maintain Config
then you will see:
- All company codes
- Paying company codes
- Payment methods in Country
- Payment methods in Company code
- Bank Determination
- House Banks
Do no changes for the All company codes, Paying comapany codes and Payment methods in country.
In the Payment methods in comapny code give your companies Address in the Form View field.
Then go to House Banks.
Give your Company Code and hit enter
Select the company code 3000 with Currency as USD and copy it give your own.
House bank:
Hit enter and then say copy all and then give your:
- Account ID
- Bank account Number (9 digits) :
- G/L account no:(cash account 113100)
Then save it and you will get 1 entries copied.
Select Bank Determination and then give your compnay Code and then select
- Ranking order with Pmt Type C and Currency USD , then change the House Bank from 3000 to your House bank no.
- Bank Account select 3000 C USD 3000 113101 and then copy it and give your information
vp02 C USD VP02 113104
and save it
-Available Amounts select 3000 3000 5 USD
999999 9999999 and then copy it to
vp02 vp02 5 USD
999999 9999999
and save it
Ignore Value date and Expense/Charges.
Next Step is to create Check Lot
Goto /nf110
Enviroment -> Check information -> Number Ranges
Give your information
Paying Comapany code:
House Bank:
Account ID:
and then click on change icon(pencile icon)
then click on create, give the following information
Lot Number:001
Check Number:
To:
Short Info:
and save it.
and next is to go to /nse38 and give the program name RFFOUS_C
Note:
RFFOUS_C(to remember, US-Check) is the one you compied in Payment Methods in country under the Environment -> Main Config
Then check on variant and click on change give your variant(VP02) and select copy from CHECK to your variant
(VP02)
and then click on change
and give the following information:
Program run date: (blank)
Identification Feature:(blank)
Paying Comapany Code: VP02
House Bank:VP02
Account ID: VP02
Check lot number:001
Printer: LP01 and check Print Immediately
give Number of sample printouts : 0
and then click on variant Attributes (give your own variant) then save it
Now give /nf110
Rundate:09/21/2006
identification:vp02
In the parameter tab,
Company code Pmt method Next P/date
VP02 C 09/30/2006
Vendor: 1 to 999999
In the Additional Log tab,
select check
Due date check
Pmnt methoed selection if not succesfull
Line items of hte payment documents
In the print out/data medium tab,
Program Variant
RFFOUS_C VP02
and then save it
and then go to status tab and you will see parameters have been
entered.
then click on proposal,
start date: check start immediatly
start time:
and then execute it
Hit enter key till you get started, running and created.
Go to edit -> proposal -> Proposal List
See whether your proposal is been executed without errors.
Note:
If there is error goto edit -> Proposal -> delete proposal.
Not due ones are not payed.
and then go back
and then click on payment run and execute it with start immediatly hit enter till it is 2 generated and 2 completed.
Then click on Printout execute it and then give your Job name(change the last ? to 1) in the status bar you will see your job name to be scheduled.
Make sure the payments are don in /nfb02
giving the document number(2000000000) and make sure
2000000000 ZP (amount)
2000000001 ZP (amount)
Then go to /nsp02, to see the print outs preview.
Its all done.
Asset with zero Depreciation
Asset with zero depreciation
Would you mind telling me how to do if I want to create an asset with zero depreciation.
What customizing needed?
Many thanks in advance
Use a depreciation key in the book/depreciation area(s) that doesn't calculate depreciation. SAP delivers depreciation key
0000 No depreciation and no interest. When you create the asset and get to the section for depreciation keys, remaining useful life, depr start date...... Put 0000 in all the depr areas where you don't want depreciation to be calculated.
You can set the depreciation key to 0000 wich is one of the standard keys.
You don't have to make customizing.
regards
Would you mind telling me how to do if I want to create an asset with zero depreciation.
What customizing needed?
Many thanks in advance
Use a depreciation key in the book/depreciation area(s) that doesn't calculate depreciation. SAP delivers depreciation key
0000 No depreciation and no interest. When you create the asset and get to the section for depreciation keys, remaining useful life, depr start date...... Put 0000 in all the depr areas where you don't want depreciation to be calculated.
You can set the depreciation key to 0000 wich is one of the standard keys.
You don't have to make customizing.
regards
No Depreciation for a period of time
No depreciation for a period of time
If you have an asset which would not be used for production purposes for next six months as the plant is being closed.
Therefore you don't want to retire the asset and neither do you want depreciation to be carried out during these six months period.
Once the plant is opened, from then on, you want to execute the depreciation run.
You can utilize the Asset Shutdown feature on the Time-dependent tab of the asset master record.
Select the Asset Shutdown checkbox - create a time interval - Save.
If you cannot find the checkbox, it could be hidden :-
In AS02 click Environment -> Screen Layout -> Master data
Select the Screen Layout and click Logical Field groups
Select 3 - Time-dependent and click Field group rules
Tick Opt, Mnno and Sbno - Save
Optionally, you can set the Depreciation key in the Deprecation Area Tab.
You can also change the depreciation key to '0000' (No depreciation and no interest) for each of your depreciation books. Just make sure you have run depreciation up through the current month before doing so. When you are ready to put the asset back into service, reset the keys to their original values. The system will calculate no depreciation during the months where you have the key set to '0000'.
If you have an asset which would not be used for production purposes for next six months as the plant is being closed.
Therefore you don't want to retire the asset and neither do you want depreciation to be carried out during these six months period.
Once the plant is opened, from then on, you want to execute the depreciation run.
You can utilize the Asset Shutdown feature on the Time-dependent tab of the asset master record.
Select the Asset Shutdown checkbox - create a time interval - Save.
If you cannot find the checkbox, it could be hidden :-
In AS02 click Environment -> Screen Layout -> Master data
Select the Screen Layout and click Logical Field groups
Select 3 - Time-dependent and click Field group rules
Tick Opt, Mnno and Sbno - Save
Optionally, you can set the Depreciation key in the Deprecation Area Tab.
You can also change the depreciation key to '0000' (No depreciation and no interest) for each of your depreciation books. Just make sure you have run depreciation up through the current month before doing so. When you are ready to put the asset back into service, reset the keys to their original values. The system will calculate no depreciation during the months where you have the key set to '0000'.
Asset Accounting ABZU -write up
ABZU - Write-up
Allows you to adjust when you forgot to capitalize an asset in a fiscal year that is now closed.
Depreciation you calculated in the past were too high. You must now correct this error using a write-up in the current fiscal year.
Allows you to adjust when you forgot to capitalize an asset in a fiscal year that is now closed.
Depreciation you calculated in the past were too high. You must now correct this error using a write-up in the current fiscal year.
Posting of Depreciation Asset Accounting
sap skills.blogspot.com
Rules for posting depreciation
In transaction OAYR (double click the depreciation area), you can post the depreciation expense to Cost Centers by ticking the field 'Assign cost centers'. This option will let you post the depreciation to the cost centers
Rules for posting depreciation
In transaction OAYR (double click the depreciation area), you can post the depreciation expense to Cost Centers by ticking the field 'Assign cost centers'. This option will let you post the depreciation to the cost centers
Sap Fico Fixed Assets Configration Asset Accounting
Asset Accounting
The SAP Asset Accounting (FI-AA) component is used for managing and supervising fixed assets with the SAP R/3 System. In SAP R/3 Financial Accounting, it serves as a subsidiary ledger to the FI General Ledger, providing detailed information on transactions involving fixed assets
The SAP Asset Accounting (FI-AA) component is used for managing and supervising fixed assets with the SAP R/3 System. In SAP R/3 Financial Accounting, it serves as a subsidiary ledger to the FI General Ledger, providing detailed information on transactions involving fixed assets
Dec 2, 2008
business blue print project goals sap
I. Introduction and Project Goals
Introduction:
The overall Dummay Name project is in reality two projects:
1. the establishment of a Legacy Business Warehouse (DUMMAY NAME) to provide continuing comppter access to legacy master and detailed data not planned for conversion into PT’s new DUMMAY NAME OLTP system (the active SAP R/3 system); and
2. the establishment of an DUMMAY NAME Business Warehouse (IBW) providing full access to DUMMAY NAME financial and human resources data optimized for query and reporting , decision support system (DSS), and online analytical processing (OLAP).
While this Blueprint Specification will make mention of the IBW throughopt as fpture effort, the main subject of this Blueprint Specification is the immediate effort to establish a Legacy Business Warehouse (DUMMAY NAME). There is no intention at this point to specify the full scope or characteristics of the IBW effort with this specification.
A separate IBW Blueprint Specification will be issued at the appropriate time.
The planned “go live” for the DUMMAY NAME will correspond to the planned “go live” date for the DUMMAY NAME active R/3 system; namely, April 2, 2001. At point the legacy data content of the DUMMAY NAME will be frozen. An early, prototype system for training and end user evaluation is hoped for by the end of 2000.
It is critical to understand that the DUMMAY NAME project’s success is dependent not only on the delivered effort of the BW Project Team (both functional and technical) bpt also on support and delivered effort from the ABAP Team, the Basis Team, the Change Management Team and the Security Team. Support of the DUMMAY NAME project must be included in the overall plans of each of these teams. The active involvement of the FI and HR groups is required as well.
Goals:
The PT Business Warehouse project has two major goals designed to support and compliment the University’s primary R/3 implementation project. These are:
1. To extract both master and detail legacy data from mainframe databases and move it to a UNIX server, there to be used for both import into a Legacy Data Business Warehouse and for staging the conversion of data into PT’s active R/3 System.
2. To establish a PT Legacy Data Business Warehouse to accommodate comppter access to historical legacy detail data not planned for conversion into PT’s new, active R/3 system. Selected master legacy data will also be stored within this data warehouse to facilitate queries and reporting. These data will be frozen at a point in time corresponding to PT’s production implementation of the R/3 system. It is critically important to note that upon final loading, detailed legacy data in the Legacy Data Business Warehouse will no longer have any keyed relationship with the active R/3 System. The R/3 System will not have access to legacy detail data and vice-versa.
Objectives:
In achieving the above goals the PT’s BW project will accomplish many important objective along the way. Among these are:
1. The staging of extracted legacy (both master and detail) data for subsequent mapping and conversion to R/3;
2. The resolution of issues concerning distributed printing from SAP systems;
3. The evaluation and selection of appropriate end user query, DSS and OLAP tools for addressing needs that may be unmet by the primary BW Explorer warehouse access tool with implementation to be part of the IBW follow on project;
4. The engagement of a broad PT audience in deliberating the data content (both legacy and R/3) and tools to which they will have ready access.
5. The early establishment of operational standards, processes and procedures in the Business Warehouse environment which may have carryover into the R/3 environment.
6. An opportunity to work opt and test network and client distribution issues with campuses and business units statewide prior to the “go live” of the PT R/3 system;
7. An early, visible deliverable to selected campuses and business units statewide, in which they will have been involved and which will demonstrate the viability of the overall infrastructure.
Introduction:
The overall Dummay Name project is in reality two projects:
1. the establishment of a Legacy Business Warehouse (DUMMAY NAME) to provide continuing comppter access to legacy master and detailed data not planned for conversion into PT’s new DUMMAY NAME OLTP system (the active SAP R/3 system); and
2. the establishment of an DUMMAY NAME Business Warehouse (IBW) providing full access to DUMMAY NAME financial and human resources data optimized for query and reporting , decision support system (DSS), and online analytical processing (OLAP).
While this Blueprint Specification will make mention of the IBW throughopt as fpture effort, the main subject of this Blueprint Specification is the immediate effort to establish a Legacy Business Warehouse (DUMMAY NAME). There is no intention at this point to specify the full scope or characteristics of the IBW effort with this specification.
A separate IBW Blueprint Specification will be issued at the appropriate time.
The planned “go live” for the DUMMAY NAME will correspond to the planned “go live” date for the DUMMAY NAME active R/3 system; namely, April 2, 2001. At point the legacy data content of the DUMMAY NAME will be frozen. An early, prototype system for training and end user evaluation is hoped for by the end of 2000.
It is critical to understand that the DUMMAY NAME project’s success is dependent not only on the delivered effort of the BW Project Team (both functional and technical) bpt also on support and delivered effort from the ABAP Team, the Basis Team, the Change Management Team and the Security Team. Support of the DUMMAY NAME project must be included in the overall plans of each of these teams. The active involvement of the FI and HR groups is required as well.
Goals:
The PT Business Warehouse project has two major goals designed to support and compliment the University’s primary R/3 implementation project. These are:
1. To extract both master and detail legacy data from mainframe databases and move it to a UNIX server, there to be used for both import into a Legacy Data Business Warehouse and for staging the conversion of data into PT’s active R/3 System.
2. To establish a PT Legacy Data Business Warehouse to accommodate comppter access to historical legacy detail data not planned for conversion into PT’s new, active R/3 system. Selected master legacy data will also be stored within this data warehouse to facilitate queries and reporting. These data will be frozen at a point in time corresponding to PT’s production implementation of the R/3 system. It is critically important to note that upon final loading, detailed legacy data in the Legacy Data Business Warehouse will no longer have any keyed relationship with the active R/3 System. The R/3 System will not have access to legacy detail data and vice-versa.
Objectives:
In achieving the above goals the PT’s BW project will accomplish many important objective along the way. Among these are:
1. The staging of extracted legacy (both master and detail) data for subsequent mapping and conversion to R/3;
2. The resolution of issues concerning distributed printing from SAP systems;
3. The evaluation and selection of appropriate end user query, DSS and OLAP tools for addressing needs that may be unmet by the primary BW Explorer warehouse access tool with implementation to be part of the IBW follow on project;
4. The engagement of a broad PT audience in deliberating the data content (both legacy and R/3) and tools to which they will have ready access.
5. The early establishment of operational standards, processes and procedures in the Business Warehouse environment which may have carryover into the R/3 environment.
6. An opportunity to work opt and test network and client distribution issues with campuses and business units statewide prior to the “go live” of the PT R/3 system;
7. An early, visible deliverable to selected campuses and business units statewide, in which they will have been involved and which will demonstrate the viability of the overall infrastructure.
Sap Business blueprint dummy blueprint for learn project
DUMMAY NAME Business Warehouse
Legacy Business Warehouse Project
Blueprint Specification
Table of Contents:
Execptive Summary
I. Introduction and Project Goals
II. Project Scope
III. Data Content and Design Strategy
IV. Data Access and Reporting Strategy
V. Apthorization and Security Strategy
VI. Change Management and Training Strategy
VII. Technical Environment
VIII. Other Issues
Appendixes
A. Glossery of Business Warehouse Terms
B. Naming Conventions
C. Business Warehouse Project Team
D. Business Warehouse Technical Support Team
Execptive Summary
The Dummay Name project is in reality two projects: the establishment of a Legacy Business Warehouse (DUMMAY NAME) to preserve and provide continuing comppter access to legacy master and detail data; and, the establishment of an DUMMAY NAME Business Warehouse (IBW) providing full access to DUMMAY NAME financial and human resources data for query, reporting and decision support systems, once PT’s DUMMAY NAME transaction processing system has been implemented.
This “Blueprint” addresses only the DUMMAY NAME project. An IBW Blueprint will be developed later in the DUMMAY NAME project. The DUMMAY NAME will “go live” concurrent with the implementation of DUMMAY NAME (April 2, 2001) and DUMMAY NAME data will be frozen at that point in time. No keyed relationship is planned between DUMMAY NAME data and legacy data.
Within the scope of the DUMMAY NAME project is the extraction of legacy data from ten (10) mainframe based data sources, identified by the project team as important for preservation and continued access via comppter. These sources include the University’s financial, grant and contract, purchasing, human resources and payroll data, dating back as far as 1981. The “reverse conversion” of R/3 data, the retroactive adjustment of legacy data, and pre-defined reports beyond templates and examples are beyond the scope of the DUMMAY NAME project.
Data extracted from these sources will be manipulated optside of the BW framework for loading into the DUMMAY NAME as InfoCubes. The DUMMAY NAME will not use any SAP BW delivered structures; all InfoObjects will be designed and developed from scratch by the BW Technical Support team. Special data handling will be required to accommodate legacy data stored in non-positional arrays, situations where the interpretation of a data element is dependent upon the value of a related data element. Full normalization of transaction data in those situations will not be ensured.
The BW Explorer query, decision support and reporting tool will be the data access tool supported for the implementation of the DUMMAY NAME. Additional, non-SAP OLAP tools will be evaluated for selection and use with the DUMMAY NAME and IBW as the DUMMAY NAME project matures.
DUMMAY NAME security will be a “role based” security strategy consistent with DUMMAY NAME security. Four end user roles have been identified: financial query developer, human resources query developer, financial report developer and human resources report developer. Query developers are strategic users identified within the central administration of each business area who will have unrestricted access to all DUMMAY NAME data. These query developers will establish general query templates providing access to financial data that will enable a wide audience of report developers to develop end user queries and reports as they see fit.
End user training and change management will be provided in concert with the DUMMAY NAME Change Management team. Specific BW Explorer training will be provided to a population of DUMMAY NAME end users expected to be relatively small. Only a score or less strategic query developers are anticipated and no more than a two hundred report developers. User training will begin with the BW project team who will participate in the testing and quality assurance activities of the project and continue with the business area strategic users. Report developer end user training is expected to continue well beyond the implementation of the DUMMAY NAME system and encompass and compliment IBW training.
The DUMMAY NAME technical environment provides for development, quality assurance and production server platforms. These environments are UNIX based and structured for the staging of system modifications and changes by the SAP transport system. The production system DUMMAY NAME is on an independent and powerful, IBM RS/6000 S80 server, sized to accommodate many hundreds of users. At this point a BW specific SAPGUI client will be required on each desktop comppter needing access to the DUMMAY NAME as well as BW Explorer.
At least two remaining issues need to be addressed. A facility is needed for non-SAP University systems to have referential access to chart of accounts and payroll employment status data. The strategy is to provide this facility via the IBW, allowing users to extract needed referential data on demand. The second issue is the disposition of legacy data not planned for inclusion in the DUMMAY NAME. At some point this data must be either abandoned or archived.
Legacy Business Warehouse Project
Blueprint Specification
Table of Contents:
Execptive Summary
I. Introduction and Project Goals
II. Project Scope
III. Data Content and Design Strategy
IV. Data Access and Reporting Strategy
V. Apthorization and Security Strategy
VI. Change Management and Training Strategy
VII. Technical Environment
VIII. Other Issues
Appendixes
A. Glossery of Business Warehouse Terms
B. Naming Conventions
C. Business Warehouse Project Team
D. Business Warehouse Technical Support Team
Execptive Summary
The Dummay Name project is in reality two projects: the establishment of a Legacy Business Warehouse (DUMMAY NAME) to preserve and provide continuing comppter access to legacy master and detail data; and, the establishment of an DUMMAY NAME Business Warehouse (IBW) providing full access to DUMMAY NAME financial and human resources data for query, reporting and decision support systems, once PT’s DUMMAY NAME transaction processing system has been implemented.
This “Blueprint” addresses only the DUMMAY NAME project. An IBW Blueprint will be developed later in the DUMMAY NAME project. The DUMMAY NAME will “go live” concurrent with the implementation of DUMMAY NAME (April 2, 2001) and DUMMAY NAME data will be frozen at that point in time. No keyed relationship is planned between DUMMAY NAME data and legacy data.
Within the scope of the DUMMAY NAME project is the extraction of legacy data from ten (10) mainframe based data sources, identified by the project team as important for preservation and continued access via comppter. These sources include the University’s financial, grant and contract, purchasing, human resources and payroll data, dating back as far as 1981. The “reverse conversion” of R/3 data, the retroactive adjustment of legacy data, and pre-defined reports beyond templates and examples are beyond the scope of the DUMMAY NAME project.
Data extracted from these sources will be manipulated optside of the BW framework for loading into the DUMMAY NAME as InfoCubes. The DUMMAY NAME will not use any SAP BW delivered structures; all InfoObjects will be designed and developed from scratch by the BW Technical Support team. Special data handling will be required to accommodate legacy data stored in non-positional arrays, situations where the interpretation of a data element is dependent upon the value of a related data element. Full normalization of transaction data in those situations will not be ensured.
The BW Explorer query, decision support and reporting tool will be the data access tool supported for the implementation of the DUMMAY NAME. Additional, non-SAP OLAP tools will be evaluated for selection and use with the DUMMAY NAME and IBW as the DUMMAY NAME project matures.
DUMMAY NAME security will be a “role based” security strategy consistent with DUMMAY NAME security. Four end user roles have been identified: financial query developer, human resources query developer, financial report developer and human resources report developer. Query developers are strategic users identified within the central administration of each business area who will have unrestricted access to all DUMMAY NAME data. These query developers will establish general query templates providing access to financial data that will enable a wide audience of report developers to develop end user queries and reports as they see fit.
End user training and change management will be provided in concert with the DUMMAY NAME Change Management team. Specific BW Explorer training will be provided to a population of DUMMAY NAME end users expected to be relatively small. Only a score or less strategic query developers are anticipated and no more than a two hundred report developers. User training will begin with the BW project team who will participate in the testing and quality assurance activities of the project and continue with the business area strategic users. Report developer end user training is expected to continue well beyond the implementation of the DUMMAY NAME system and encompass and compliment IBW training.
The DUMMAY NAME technical environment provides for development, quality assurance and production server platforms. These environments are UNIX based and structured for the staging of system modifications and changes by the SAP transport system. The production system DUMMAY NAME is on an independent and powerful, IBM RS/6000 S80 server, sized to accommodate many hundreds of users. At this point a BW specific SAPGUI client will be required on each desktop comppter needing access to the DUMMAY NAME as well as BW Explorer.
At least two remaining issues need to be addressed. A facility is needed for non-SAP University systems to have referential access to chart of accounts and payroll employment status data. The strategy is to provide this facility via the IBW, allowing users to extract needed referential data on demand. The second issue is the disposition of legacy data not planned for inclusion in the DUMMAY NAME. At some point this data must be either abandoned or archived.
Lockbox Architecture
Lockbox Architecture
There are 3 general steps in the proessing:
Receive a file of check data from the bank. Some banks allow dial in and download.
Execute the Lockbox Import Program
Post the G/L transaction reflecting the receipt of cash
Creates a payment advice. Open items are automatically cleared/
Access the lockbox post-process transaction to process any checks that could not be fully applied by the Lockbox Import Program
What is Lockbox Sap and Processing
The basic operation of a lockbox system is fundamental to large businesses but is almost transparent to those without some knowledge of corporate treasury operations. The objective of a lockbox operation is to have the customer remit a payment check to a local post office box to minimize mail transit time. The checks are processed by the bank on a daily basis and the funds collected are usable by the receiving business much quicker than with the traditional process. The illustration below shows the basic operation of the lockbox and how SAP fits in.
Dunning Charges
Dunning Charges
Minimum Amounts:
This prevents the system from sending dunning notices for immaterial amounts
Once the balance of a dunning level exceeds the minimum amount, the corresponding dunning level is triggered and the customer is dunned
Dunning Texts: You can define a form for each dunning level or useone form for several dunning levels.
Once the dunning procedure is defined it can be assigned to a company in its master data.
Setting up dunning levels
The dunning level is determined by the number of days in arrears.
You can have the system print all items at a particular dunning level.
You can specify a payment deadline which is copied to the dunning text.
Dunning procedures parameters
The basic parameters for dunning are set up in the dunning procedure. You can define several different kinds of dunning procedures in the system
Only those customer that have a dunning procedure defined in their master record are included in the dunning run.
Dunning procedures are maintained at client level. You can set up and maintain forms individually for each company code.
Defining dunning procedures:
Sap Dunning level configration procedure
Dunning is the process of methodically communicating with customers to insure the collection of accounts receivable. It follows the process that progresses from gentle reminders to almost threatening letters as accounts become more past due. SAP has automated this process. Law in each country regulate the form that dunning can take. It is generally unlawful to harasss or threaten consumers. It is ok to issue firm reminders and to take all allowable collection options.
The chart below shows the major factors in the dunning configuration
Sep 23, 2008
Join Free B2B Marketplace to sell your products
Welcome to Cheap Price China .Com
Cheappricechina.com ! Why not Join free free free cheapprice china introduce a new technology to get new customers from google traffic for your products Cheap price china is New B2B market place where customers can find your products very easily because right now we don’t have too much data so its good chance for you to sell your product free of cost and grow your business with cheap price china from cheap price china represent your products all over the world and help you to get new buyers and sellers from entire would You just need to SIGN UP and post your sell offers and buy offers free with details description with image.
Cheappricechina.com ! Why not Join free free free cheapprice china introduce a new technology to get new customers from google traffic for your products Cheap price china is New B2B market place where customers can find your products very easily because right now we don’t have too much data so its good chance for you to sell your product free of cost and grow your business with cheap price china from cheap price china represent your products all over the world and help you to get new buyers and sellers from entire would You just need to SIGN UP and post your sell offers and buy offers free with details description with image.
Jun 4, 2008
Business Blueprint Sap project
Business Blueprint
This function documents the business processes in your company that you want to implement in the system. In a Business Blueprint for Projects, you create a project structure in which relevant business scenarios, business processes and process steps are organized in a hierarchical structure. You can also create project documentation and assign it to individual scenarios, processes or process steps. You then assign transactions to each process step, to specify how your business processes should run in your SAP systems.
The Business Blueprint is a detailed description of your business processes and system requirements. You can print it out.
Integration
You can continue to use the project documentation and the project structure that you create during the Business Blueprint, in the configuration and test organization phases.
When you configure your business processes, the system displays the Business Blueprint project structure. You can use the Business Blueprint project structure as a point of reference during configuration.
You can also display and edit the project documentation from the Business Blueprint phase, during configuration.
You base all test plans that you create during test organization, on the Business Blueprint project structure. The transactions that you assign to process steps in the Business Blueprint are put in test plans during test plan generation, and run as function tests to test the transactions.
Prerequisites
You have created a project of type implementation, template, or upgrade, in the project administration.
Features
Scope of the Business Blueprint Transaction Function
Tab
Create a project structure
Structure
Display the following documentation:
Documentation delivered by SAP, e.g. scenario descriptions
Documents from templates, e.g. from template projects
To be able to edit general documentation, copy it to the Project Documentation tab.
General Documentation
Assign documents to structure elements
Create, Change, Upload user documents
General Documentation in template projects
Project Documentation in all project types
Input administration data, e.g. project status, team members assigned, planned and actual resources
Administration
Assign transactions and programs to structure elements
Transactions
Create, Display and Edit issues und messages
Issues/Messages
Display and Create a process graphic
Graphics
Where-used list:
Use in user project
Use in other projects
Go to use by double-click
General Documentation
Project Documentation
Transactions
General Functions Function
Navigation
Change the sequence, hide or show tabs
Settings User-Specific
Translate project structure
For further information about translating document names for URLs, in your project, see Translating a Template
Goto Translation
Create/print a Business Blueprint document
Business Blueprint Create Blueprint Document
Assign document authorization
Assign authorizations in the Role (PFCG) and User Maintenance.
Activities
Create a Blueprint structure in the Structure tab, using predefined substructures.
Check the Business Blueprint structure, and the business scenarios, business processes and process steps it contains.
Decide which business scenarios, business processes and process steps you want to include in the Business Blueprint. You can enhance the processes and process steps, or adjust the names of individual processes to suit your company requirements.
Create project documentation to save in the Business Blueprint, in the Project Documentation tab.
Assign transactions to process steps in the Transactions tab. This specifies which transactions in the system correspond to the process steps in your enterprise.
Print the Business Blueprint document.
When the Business Blueprint is complete, you can start to set up the development system landscape.
Result
You have specified a Business Blueprint. You can reuse the Business Blueprint and the project structure to configure and test your business processes.
This function documents the business processes in your company that you want to implement in the system. In a Business Blueprint for Projects, you create a project structure in which relevant business scenarios, business processes and process steps are organized in a hierarchical structure. You can also create project documentation and assign it to individual scenarios, processes or process steps. You then assign transactions to each process step, to specify how your business processes should run in your SAP systems.
The Business Blueprint is a detailed description of your business processes and system requirements. You can print it out.
Integration
You can continue to use the project documentation and the project structure that you create during the Business Blueprint, in the configuration and test organization phases.
When you configure your business processes, the system displays the Business Blueprint project structure. You can use the Business Blueprint project structure as a point of reference during configuration.
You can also display and edit the project documentation from the Business Blueprint phase, during configuration.
You base all test plans that you create during test organization, on the Business Blueprint project structure. The transactions that you assign to process steps in the Business Blueprint are put in test plans during test plan generation, and run as function tests to test the transactions.
Prerequisites
You have created a project of type implementation, template, or upgrade, in the project administration.
Features
Scope of the Business Blueprint Transaction Function
Tab
Create a project structure
Structure
Display the following documentation:
Documentation delivered by SAP, e.g. scenario descriptions
Documents from templates, e.g. from template projects
To be able to edit general documentation, copy it to the Project Documentation tab.
General Documentation
Assign documents to structure elements
Create, Change, Upload user documents
General Documentation in template projects
Project Documentation in all project types
Input administration data, e.g. project status, team members assigned, planned and actual resources
Administration
Assign transactions and programs to structure elements
Transactions
Create, Display and Edit issues und messages
Issues/Messages
Display and Create a process graphic
Graphics
Where-used list:
Use in user project
Use in other projects
Go to use by double-click
General Documentation
Project Documentation
Transactions
General Functions Function
Navigation
Change the sequence, hide or show tabs
Settings User-Specific
Translate project structure
For further information about translating document names for URLs, in your project, see Translating a Template
Goto Translation
Create/print a Business Blueprint document
Business Blueprint Create Blueprint Document
Assign document authorization
Assign authorizations in the Role (PFCG) and User Maintenance.
Activities
Create a Blueprint structure in the Structure tab, using predefined substructures.
Check the Business Blueprint structure, and the business scenarios, business processes and process steps it contains.
Decide which business scenarios, business processes and process steps you want to include in the Business Blueprint. You can enhance the processes and process steps, or adjust the names of individual processes to suit your company requirements.
Create project documentation to save in the Business Blueprint, in the Project Documentation tab.
Assign transactions to process steps in the Transactions tab. This specifies which transactions in the system correspond to the process steps in your enterprise.
Print the Business Blueprint document.
When the Business Blueprint is complete, you can start to set up the development system landscape.
Result
You have specified a Business Blueprint. You can reuse the Business Blueprint and the project structure to configure and test your business processes.
May 31, 2008
Test Scripts FICO
Guide for Testing SAP Financial
TESTING
Unit Testing
When you test every single document is called unit testing.
String Testing
One transaction full activity is called string testing . For example Vendor invoice, goods received and vendor payment.
Integration Testing
It is purely with other modules and we have to check whether the FI testing is working with other related modules or not.
Regression Testing
Testing for whole database. Bring all the data into another server and do the testing is called regression.
UAT
When we test any particular document with the user and if it is ok immediately we have to take the signature on the document, which is signed off and can be forwarded to the immediate boss. There are some steps to be followed when we go for user acceptance testing.
Transaction – Script Writing – Expected Results – Compare with Actual Results
TPR (Transaction Problem Reporting)
While doing the user acceptance testing if we get any problems then there are some methodologies to be followed according to the company’s policy and normally as a tester we always need to write on Test Script itself.
Key Features
Understanding the business scenarios
Organization Structure to incorporate the tune of the script.
Preparation of test scripts
Execute and record results to see if it is fine before going to approval.
Make changes to your test script if required.
What is Test Script (Scenario Testing)
Header Data
Step in Process
Transaction Code / Program (FB60)
Menu Path
Description
Field Data and actions to complete
Expected Results
Actual Results
TPR
Closing Period
F.19 Clearing GR/IR Account
F.13 Adjustments GR/IR Account
Using of these above two accounts will help us in clearing the balances and adjustments to those respective clearing accounts so that the GR/IR account will be zero balance and the balances will appear in respective reconciliation accounts accordingly the balances will be carried forwarded to next fiscal year.
GR/IR Clears the following Documents
GL Document
Customer Documents
Vendor Documents
Assignment Field is important in any document (ZUONR), Amount (DMBTR)
Foreign Currency Valuation
Lowest Value Method, If we are in loss then only we will account for it.
GL Accounts which are important in Testing
Enjoy Transaction - FB50
Normal Transaction - FB01
Document Parking - FV50
Post with Clearing - F-04
Incoming Payment - F-06
Outgoing Payment - F-07
Document Related
Reset Cleared Items - FBRA
Parking Document Posting - FBVO
Reversal Documents - F-14
Company Code Clearing A/C
(Trial Balance purposes) reversal - (FBUB)
Clearing Account
Partial clearing Invoice - 100 - Open Item
Paid - 70 - Open Item
Balance - 30
In Partial Clearing you can see 100 and 70 are cleared line items and 30 as balance and if it is in Residual you can only 30 as balance as it creates new line item and you can’t see the other cleared line items.
As no company will use residual clearing as it affects on ageing reports.
Open Items in Foreign Currency in all Modules GL/AP/AR - F.05
Master Data
Company Code
Currency
Only Balances in local currencies
Reconciliation Account Type
Year End Scripts
Re Grouping Receivables / Payables - (F101)
Bad Debts Provisions – Scripts
We assume that the customer has not paid at the end of the year you doubt whether this receivable will ever be paid. So you make a transfer posting for the receivables to an account for individual value adjustments using special GL Indicator E and Transaction Code F-21
Carry forward Balances
Sub Ledgers and General Ledger balances to be forwarded to next Fiscal Year
Accounts Payables
Vendor Down Payments
Invoice
Parking
Reversal
Outgoing Payments
Automatic Clearing
Manual Clearing
Advance (Down Payment)
Post with Clearing
Post without Clearing
Reset Clearing
Carry forward
Regrouping
Foreign Currency Valuations
Accounts Receivables
Customer Down Payments
Invoice
Parking
Reversal
Incoming Payments
Manual Clearing
Advance (Down Payment)
Post with Clearing
Post without Clearing
Reset Clearing
Carry forward
Regrouping
Foreign Currency Valuations
TESTING
Unit Testing
When you test every single document is called unit testing.
String Testing
One transaction full activity is called string testing . For example Vendor invoice, goods received and vendor payment.
Integration Testing
It is purely with other modules and we have to check whether the FI testing is working with other related modules or not.
Regression Testing
Testing for whole database. Bring all the data into another server and do the testing is called regression.
UAT
When we test any particular document with the user and if it is ok immediately we have to take the signature on the document, which is signed off and can be forwarded to the immediate boss. There are some steps to be followed when we go for user acceptance testing.
Transaction – Script Writing – Expected Results – Compare with Actual Results
TPR (Transaction Problem Reporting)
While doing the user acceptance testing if we get any problems then there are some methodologies to be followed according to the company’s policy and normally as a tester we always need to write on Test Script itself.
Key Features
Understanding the business scenarios
Organization Structure to incorporate the tune of the script.
Preparation of test scripts
Execute and record results to see if it is fine before going to approval.
Make changes to your test script if required.
What is Test Script (Scenario Testing)
Header Data
Step in Process
Transaction Code / Program (FB60)
Menu Path
Description
Field Data and actions to complete
Expected Results
Actual Results
TPR
Closing Period
F.19 Clearing GR/IR Account
F.13 Adjustments GR/IR Account
Using of these above two accounts will help us in clearing the balances and adjustments to those respective clearing accounts so that the GR/IR account will be zero balance and the balances will appear in respective reconciliation accounts accordingly the balances will be carried forwarded to next fiscal year.
GR/IR Clears the following Documents
GL Document
Customer Documents
Vendor Documents
Assignment Field is important in any document (ZUONR), Amount (DMBTR)
Foreign Currency Valuation
Lowest Value Method, If we are in loss then only we will account for it.
GL Accounts which are important in Testing
Enjoy Transaction - FB50
Normal Transaction - FB01
Document Parking - FV50
Post with Clearing - F-04
Incoming Payment - F-06
Outgoing Payment - F-07
Document Related
Reset Cleared Items - FBRA
Parking Document Posting - FBVO
Reversal Documents - F-14
Company Code Clearing A/C
(Trial Balance purposes) reversal - (FBUB)
Clearing Account
Partial clearing Invoice - 100 - Open Item
Paid - 70 - Open Item
Balance - 30
In Partial Clearing you can see 100 and 70 are cleared line items and 30 as balance and if it is in Residual you can only 30 as balance as it creates new line item and you can’t see the other cleared line items.
As no company will use residual clearing as it affects on ageing reports.
Open Items in Foreign Currency in all Modules GL/AP/AR - F.05
Master Data
Company Code
Currency
Only Balances in local currencies
Reconciliation Account Type
Year End Scripts
Re Grouping Receivables / Payables - (F101)
Bad Debts Provisions – Scripts
We assume that the customer has not paid at the end of the year you doubt whether this receivable will ever be paid. So you make a transfer posting for the receivables to an account for individual value adjustments using special GL Indicator E and Transaction Code F-21
Carry forward Balances
Sub Ledgers and General Ledger balances to be forwarded to next Fiscal Year
Accounts Payables
Vendor Down Payments
Invoice
Parking
Reversal
Outgoing Payments
Automatic Clearing
Manual Clearing
Advance (Down Payment)
Post with Clearing
Post without Clearing
Reset Clearing
Carry forward
Regrouping
Foreign Currency Valuations
Accounts Receivables
Customer Down Payments
Invoice
Parking
Reversal
Incoming Payments
Manual Clearing
Advance (Down Payment)
Post with Clearing
Post without Clearing
Reset Clearing
Carry forward
Regrouping
Foreign Currency Valuations
May 29, 2008
GL ACCOUNT TYPE
G/L NO.---------LONG TEXT-----------ACCOUNT GROUP------ACCOUNT TYPE-----RECON ACCOUNT
100001----------EQUITY CAPITAL------SHARE CAPTIAL------BALANCE SHEET----- NO
100401---------A/P DOMESTIC---------CURRENT LIABILITY----BS SHEET-----VENDOR
100402----------ACCUMULATED DEPRECIATION CURRENT LIABILITY---BS-----------ASSETS
200000-----------PLANT AND MACHINERY------
100001----------EQUITY CAPITAL------SHARE CAPTIAL------BALANCE SHEET----- NO
100401---------A/P DOMESTIC---------CURRENT LIABILITY----BS SHEET-----VENDOR
100402----------ACCUMULATED DEPRECIATION CURRENT LIABILITY---BS-----------ASSETS
200000-----------PLANT AND MACHINERY------
Account Group
ACCOUNT GROUP------DESCRIPTION----------FROM----------------TO
SCPL-----------SHARE CAPITAL-----------100000------------100100
RSPL----------RESERVES & SURPLUS------100100-------------100200
SCLN----------SECURED LOANS-----------100200-------------100300
UNSC----------UNSECURED LOANS---------100301-------------100400
CLPS----------CURRENT LIABILITIES-----100401-------------100500
FXAT----------FIXED ASSET-------------200000-------------200100
CAST----------CURRENT ASSETS----------200101-------------200200
LNAN----------LOANS AND ADV-----------200201-------------200300
SALE----------SALE REVENUE------------300000-------------300100
OTIN----------OTHER REVENUE-----------300101-------------300200
RMCN----------RAW MAT CONSUMPTION-----400000-------------400100
PERN----------PERSONAL COST-----------400100-------------400200
ADMN----------ADMIN COST--------------400201-------------400300
SEDN----------SELLING DISTRU----------400301-------------400400
DEPN----------DEPRECIATION------------400401-------------400500
SCPL-----------SHARE CAPITAL-----------100000------------100100
RSPL----------RESERVES & SURPLUS------100100-------------100200
SCLN----------SECURED LOANS-----------100200-------------100300
UNSC----------UNSECURED LOANS---------100301-------------100400
CLPS----------CURRENT LIABILITIES-----100401-------------100500
FXAT----------FIXED ASSET-------------200000-------------200100
CAST----------CURRENT ASSETS----------200101-------------200200
LNAN----------LOANS AND ADV-----------200201-------------200300
SALE----------SALE REVENUE------------300000-------------300100
OTIN----------OTHER REVENUE-----------300101-------------300200
RMCN----------RAW MAT CONSUMPTION-----400000-------------400100
PERN----------PERSONAL COST-----------400100-------------400200
ADMN----------ADMIN COST--------------400201-------------400300
SEDN----------SELLING DISTRU----------400301-------------400400
DEPN----------DEPRECIATION------------400401-------------400500
May 22, 2008
Validation GGB0
Validation are used to check setting and return a message if the prerequisite check condition is met you can used validation to supplement existing sap logic to fit you business needs a validation is a valuable tool that can be used in many of the financial and controlling modules.
Fi validation to fulfill our requirement of allowing posting from company code 1200 to be posted to only business area EES to maintain the validation.
Fi validation to fulfill our requirement of allowing posting from company code 1200 to be posted to only business area EES to maintain the validation.
May 20, 2008
Variant
A variant is a particular setting when we post any transcations some data input screen allow us to save and execute variant we can create variant is a good way to save time because we already put some data for this and next time we just execute this variant so no need to enter all data.
May 15, 2008
Depreciation
When you do a midyear takeover of assets, as opposed to a yearend
takeover, you'll need to handle
current year transactions in a special way in order to have
correct info on acquisition reports for both
book and tax purposes. Assets acquired in the current fiscal
year will require an acquisition transaction
to load them correctly.
*
Assets acquired before the current fiscal year
The AS91 transaction looks for three amount fields:
KANSW
Asset cost as of the end of the last fiscal
year
KNAFA
Accumulated depreciation balance as of the
end of the last FY
NAFAG
Depreciation expense posted this FY
*
Assets with a capitalization date in the current fiscal year
The AS91 transaction grays out the cost and accumulated depreciation
fields (KANSW) and (KNAFA) and requires
the following:
NAFAG
Depreciation expense posted this FY
BZDAT
Acquisition date
BWASL
Transaction type - default 100
ANBTR
Asset cost
*
Current year acquisitions to prior year assets
Create old asset the normal way and add the current year transaction.
KANSW
Asset cost as of the end of the last fiscal year
KNAFA
Accumulated depreciation balance as of the end
of the last FY
NAFAG
Depreciation expense posted this FY
BZDAT
Acquisition date of current year posting
BWASL
Transaction type - default 152
ANBTR
Cost of additional asset posting
*
Current year retirements of prior year assets
DEAKT
Asset deactivation date, which is the retirement
transaction date
KANSW
Asset cost as of the end of the last fiscal year
KNAFA
Accumulated depreciation balance as of the end
of the last FY
NAFAG
Depreciation expense posted this FY
BZDAT
Transaction date of current year retirement
BWASL
Transaction type - default 200
ANBTR
Retirement amount. Should be current month NBV
for area 01 and prior year NBV for the tax areas.
takeover, you'll need to handle
current year transactions in a special way in order to have
correct info on acquisition reports for both
book and tax purposes. Assets acquired in the current fiscal
year will require an acquisition transaction
to load them correctly.
*
Assets acquired before the current fiscal year
The AS91 transaction looks for three amount fields:
KANSW
Asset cost as of the end of the last fiscal
year
KNAFA
Accumulated depreciation balance as of the
end of the last FY
NAFAG
Depreciation expense posted this FY
*
Assets with a capitalization date in the current fiscal year
The AS91 transaction grays out the cost and accumulated depreciation
fields (KANSW) and (KNAFA) and requires
the following:
NAFAG
Depreciation expense posted this FY
BZDAT
Acquisition date
BWASL
Transaction type - default 100
ANBTR
Asset cost
*
Current year acquisitions to prior year assets
Create old asset the normal way and add the current year transaction.
KANSW
Asset cost as of the end of the last fiscal year
KNAFA
Accumulated depreciation balance as of the end
of the last FY
NAFAG
Depreciation expense posted this FY
BZDAT
Acquisition date of current year posting
BWASL
Transaction type - default 152
ANBTR
Cost of additional asset posting
*
Current year retirements of prior year assets
DEAKT
Asset deactivation date, which is the retirement
transaction date
KANSW
Asset cost as of the end of the last fiscal year
KNAFA
Accumulated depreciation balance as of the end
of the last FY
NAFAG
Depreciation expense posted this FY
BZDAT
Transaction date of current year retirement
BWASL
Transaction type - default 200
ANBTR
Retirement amount. Should be current month NBV
for area 01 and prior year NBV for the tax areas.
Important Enteris FI
Inventory Accounting Entries
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
When the Goods are issued to the Production Order the following transactions takes place:
Consumption of Raw Materials - Dr
Stock A/c - Cr
When the Goods are received from the Production Order the following transactions takes place:
Inventory A/c - Dr
Cost of Goods Produced - Cr
Price difference - Dr/Cr
(depending on the difference between standard cost and actual cost)
When the Goods are dispatched to customer through delivery the following transactions takes place:
Cost of Goods Sold - Dr
Inventory A/c - Cr
When the Goods are issued to a Cost Center or charged off against expenses the following transactions takes place:
Repairs and Maintenance - Dr
Inventory A/c - Cr
When the Goods are stock transferred from one plant to another, the following transactions takes place:
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)
When the stocks are revalued, the following transactions takes place:
Stock A/c - Dr/Cr
Inventory Revaluation A/c - Cr / Dr
When the Work in Progress is calculated the following transaction takes place:
Work in Progress A/c - Dr
Change WIP A/c - Cr
Physical verification /shortages and excesses : Shortages/excesses on authorizations shall be adjusted using the physical inventory count transaction.
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
When the Goods are issued to the Production Order the following transactions takes place:
Consumption of Raw Materials - Dr
Stock A/c - Cr
When the Goods are received from the Production Order the following transactions takes place:
Inventory A/c - Dr
Cost of Goods Produced - Cr
Price difference - Dr/Cr
(depending on the difference between standard cost and actual cost)
When the Goods are dispatched to customer through delivery the following transactions takes place:
Cost of Goods Sold - Dr
Inventory A/c - Cr
When the Goods are issued to a Cost Center or charged off against expenses the following transactions takes place:
Repairs and Maintenance - Dr
Inventory A/c - Cr
When the Goods are stock transferred from one plant to another, the following transactions takes place:
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)
When the stocks are revalued, the following transactions takes place:
Stock A/c - Dr/Cr
Inventory Revaluation A/c - Cr / Dr
When the Work in Progress is calculated the following transaction takes place:
Work in Progress A/c - Dr
Change WIP A/c - Cr
Physical verification /shortages and excesses : Shortages/excesses on authorizations shall be adjusted using the physical inventory count transaction.
SAP CO TABLE NAME
Table Name Description Important Fields
AUSP Characteristic Values MANDT / OBJEK / ATINN / ATZHL
CO-KBAS Overhead Cost Controlling
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
CO-KBASCORE Overhead Cost Controlling: General Services
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
CO-OM (KACC) Overhead Cost Controlling
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
CO-OM-CEL (KKAL) Cost Element Accounting (Reconciliation Ledger)
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
CO-OM-CCA Cost Center Accounting (Cost Accounting Planning RK-S)
– What is RK-S
A138 Price per Company Code MANDT / KAPPL / KSCHL / KOKRS
A139 Price per Profit Center MANDT / KAPPL / KSCHL / KOKRS
CO-OM-OPA (KABR) Overhead Orders: Application Development R/3
Cost Accounting Settlement
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
CO-OM-OPA (KAUF) Overhead Orders: Cost Accounting Orders
AUFK Order Master Data MANDT / AUFNR
AUFLAY0 Enttity Table: Order Layouts MANDT / LAYOUT
EC-PCA (KE1) Profit Center Accounting
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
EC-PCA BS (KE1C) PCA Basic Settings: Customizing for
Profit Center Accounting
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
AUSP Characteristic Values MANDT / OBJEK / ATINN / ATZHL
CO-KBAS Overhead Cost Controlling
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
CO-KBASCORE Overhead Cost Controlling: General Services
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
CO-OM (KACC) Overhead Cost Controlling
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
CO-OM-CEL (KKAL) Cost Element Accounting (Reconciliation Ledger)
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
CO-OM-CCA Cost Center Accounting (Cost Accounting Planning RK-S)
– What is RK-S
A138 Price per Company Code MANDT / KAPPL / KSCHL / KOKRS
A139 Price per Profit Center MANDT / KAPPL / KSCHL / KOKRS
CO-OM-OPA (KABR) Overhead Orders: Application Development R/3
Cost Accounting Settlement
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
CO-OM-OPA (KAUF) Overhead Orders: Cost Accounting Orders
AUFK Order Master Data MANDT / AUFNR
AUFLAY0 Enttity Table: Order Layouts MANDT / LAYOUT
EC-PCA (KE1) Profit Center Accounting
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
EC-PCA BS (KE1C) PCA Basic Settings: Customizing for
Profit Center Accounting
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
SAP FICO TABLE NAME
Table Name Description Important Fields
Financial Accounting
FBAS Financial Accounting “Basis”
BKPF Accounting Document Header BUKRS / BELNR / GJAHR
BSEG Accounting Document Segment BUKRS / BELNR / GJAHR / BUZEI
BSIP Index for Vendor Validation BUKRS / LIFNR / WAERS / BLDAT /
of Double Documents XBLNR / WRBTR / BELNR / GJAHR
/ BUZEI
BVOR Inter Company Posting BVORG / BUKRS / GJAHR / BELNR
Procedure
EBKPF Accounting Document Header GLSBK / BELNR / GJHAR / GLEBK
(docs from 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 KUNNR / BUKRS / GJHAR
Figures
KNC3 Customer Master Special KUNNR / BUKRS / GJAHR / SHBKZ
GL Transactions Figures
LFB5 Vendor Master Dunning Data LIFNR / BUKRS / MABER
LFBK Vendor Master Bank Details LIFNR / BANKS / BANKL / BANKN
LFC1 Vendor Master Transaction LIFNR / BUKRS / GJHAR
Figures
LFC3 Vendor Master Special LIFNR / BUKRS / GJHAR / SHBKZ
GL Transactions Figures
VBKPF Document Header for AUSBK / BUKRS / BELNR / GJHAR
Document Parking
FBASCORE Financial Accounting General Services “Basis”
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 KOART / BUKRS / KONKO / MABER
Selection
MHNK Dunning Data LAUFD / LAUFI / KOART / BUKRS /
(Account Entries) KUNNR / LIFNR / CPDKY / SKNRZE /
SMABER / SMAHSK / BUSAB
FI-GL-GL (FBS) General Ledger Basic Functions-
G/L Accounts
SKAS G/L Account Master – SPRAS / KTOPL / SAKNR / SCHLW
(Chart of Accounts 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
FI-AR-AR (FBD) Accounts Receivable: Basic Functions - Customers
KNKA Customer Master Credit Management : KUNNR
Central Data
KNKK Customer Master Credit Management : KUNNR / KKBER
Control Area Data
KNKKF1 Credit Management : LOGSYS / KUNNR / KKBER / REGUL
FI Status data
RFRR Accounting Data – A/R and A/P RELID / SRTFD / SRTF2
Information System
FI-BL-PT Bank Accounting: Payment (BFIBL_CHECK_D)
Transactions – General Sections
PAYR Payment Medium File ZBUKR / HBKID / HKTID / RZAWE /
CHECT
PCEC Pre-numbered Check ZBUKR / HBKID / HKTID / STAPL
FI-BL-PT-AP(FMZA)Bank Accounting: Payment
Transactions – Automatic Payments
F111G Global Settings for Payment Program for MANDT
Payment Requests
FDZA Cash Management Line Items in Payment KEYNO
Requests
PAYRQ Payment Requests KEYNO
What is the table name for G/L Master data, when we create
centrally (T.Code - FS00)?
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
Financial Accounting
FBAS Financial Accounting “Basis”
BKPF Accounting Document Header BUKRS / BELNR / GJAHR
BSEG Accounting Document Segment BUKRS / BELNR / GJAHR / BUZEI
BSIP Index for Vendor Validation BUKRS / LIFNR / WAERS / BLDAT /
of Double Documents XBLNR / WRBTR / BELNR / GJAHR
/ BUZEI
BVOR Inter Company Posting BVORG / BUKRS / GJAHR / BELNR
Procedure
EBKPF Accounting Document Header GLSBK / BELNR / GJHAR / GLEBK
(docs from 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 KUNNR / BUKRS / GJHAR
Figures
KNC3 Customer Master Special KUNNR / BUKRS / GJAHR / SHBKZ
GL Transactions Figures
LFB5 Vendor Master Dunning Data LIFNR / BUKRS / MABER
LFBK Vendor Master Bank Details LIFNR / BANKS / BANKL / BANKN
LFC1 Vendor Master Transaction LIFNR / BUKRS / GJHAR
Figures
LFC3 Vendor Master Special LIFNR / BUKRS / GJHAR / SHBKZ
GL Transactions Figures
VBKPF Document Header for AUSBK / BUKRS / BELNR / GJHAR
Document Parking
FBASCORE Financial Accounting General Services “Basis”
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 KOART / BUKRS / KONKO / MABER
Selection
MHNK Dunning Data LAUFD / LAUFI / KOART / BUKRS /
(Account Entries) KUNNR / LIFNR / CPDKY / SKNRZE /
SMABER / SMAHSK / BUSAB
FI-GL-GL (FBS) General Ledger Basic Functions-
G/L Accounts
SKAS G/L Account Master – SPRAS / KTOPL / SAKNR / SCHLW
(Chart of Accounts 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
FI-AR-AR (FBD) Accounts Receivable: Basic Functions - Customers
KNKA Customer Master Credit Management : KUNNR
Central Data
KNKK Customer Master Credit Management : KUNNR / KKBER
Control Area Data
KNKKF1 Credit Management : LOGSYS / KUNNR / KKBER / REGUL
FI Status data
RFRR Accounting Data – A/R and A/P RELID / SRTFD / SRTF2
Information System
FI-BL-PT Bank Accounting: Payment (BFIBL_CHECK_D)
Transactions – General Sections
PAYR Payment Medium File ZBUKR / HBKID / HKTID / RZAWE /
CHECT
PCEC Pre-numbered Check ZBUKR / HBKID / HKTID / STAPL
FI-BL-PT-AP(FMZA)Bank Accounting: Payment
Transactions – Automatic Payments
F111G Global Settings for Payment Program for MANDT
Payment Requests
FDZA Cash Management Line Items in Payment KEYNO
Requests
PAYRQ Payment Requests KEYNO
What is the table name for G/L Master data, when we create
centrally (T.Code - FS00)?
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
May 11, 2008
Closing Activities
A) Month end year end closing processes
pre closing activities takes place in old month at month end level include
a)open new accounting period technical
b)Enter accrual/deferral bad debets depreciation, interest calculation fi
c)maintain GR/IR account clearing -mm
d)post payroll process HR
e)record goods issues for deliveries and invoice customers SD
f) co allocation and reposting locking old accounting period co
g)reconcilation posting to fi -co
h) foreign currency valuation
i) final closing of old period
in addition to pre closing activities at month end level following activitie are performed for year end closing
a) perform physical inventory-- MM
b)update product cost estimates pp/Co
c)valuation of materials on fifo/lifo -MM
d)assets valuation and investment support-AA
e)balance confirmation -a/p,Ar
f)fiscal year change AA
g)balance carried forward program-fi
pre closing activities takes place in old month at month end level include
a)open new accounting period technical
b)Enter accrual/deferral bad debets depreciation, interest calculation fi
c)maintain GR/IR account clearing -mm
d)post payroll process HR
e)record goods issues for deliveries and invoice customers SD
f) co allocation and reposting locking old accounting period co
g)reconcilation posting to fi -co
h) foreign currency valuation
i) final closing of old period
in addition to pre closing activities at month end level following activitie are performed for year end closing
a) perform physical inventory-- MM
b)update product cost estimates pp/Co
c)valuation of materials on fifo/lifo -MM
d)assets valuation and investment support-AA
e)balance confirmation -a/p,Ar
f)fiscal year change AA
g)balance carried forward program-fi
May 9, 2008
Dunning
SAP FICO WHAT IS DUNNING
Dunning is kind of reminder we mostly send to our customers and some time vendors as well to collect our bills and invoice on time its is statement which showing how much amount is due.
When we sending notice to our customers about payments due we define dunning level which level is best for that customer we can define 1 to 9 levels and final levels is kind of legal notice we sending to customers about his due amounts.
As dunning level getting higher the content of letter is changed.
Dunning configuration steps
1-Define Dunning Area
2-Define Dunning Key
3-Define Dunning Block Reasons
4-Define Dunning Procedures Tcode FBMP
Dunning procedure
a)Define dunning interval reminder may be weekly, fornightly,monthly etc.
b)Define no. of days is arrears after which dunning notice will be sent
c)grace period per line item
d)interest calculation indicator for calculation of dunning interest
e)dunning key for dunning procedure.
Dunning levels
a)the first dunning level included the line item grace period
b)if option always dun selected the dunning notice will still printed even not change have been made in account
c) in dunning notice total account balance or item wise details can be print
Expenses/Changes
a)dunning charges may be depending on dunning level
b)dunning charges is either fixed for percentage of amount dunned
c)you can either choose fixed or precentage of amount dunned
d)dunning charges are define for currency wise
Minimum amount or percentage must be specifying for dunning notice the dunning notice will not generate until overdue item reached up to dunning level.
Minimum amount can also be fixed for calculating interest on dunning amount
dunning text must be defined according to the dunning level
predefined form of dunning text is available in sap
dunning program can generate payment advice note dunning notice and payment form
Environment
a) company code
b)short field
s)sender details
d)dunning areas
e)dunning key
f)dunning block reason
g)interest
h)dunning grouping
Running of dunning program
enter parameters
a) run date
b)identification
c)selection of company codes may be single company or no of companies
d)range of customer/vendor account
e)document define up to which posting date include in dunning run
Dunning run
Dunning is kind of reminder we mostly send to our customers and some time vendors as well to collect our bills and invoice on time its is statement which showing how much amount is due.
When we sending notice to our customers about payments due we define dunning level which level is best for that customer we can define 1 to 9 levels and final levels is kind of legal notice we sending to customers about his due amounts.
As dunning level getting higher the content of letter is changed.
Dunning configuration steps
1-Define Dunning Area
2-Define Dunning Key
3-Define Dunning Block Reasons
4-Define Dunning Procedures Tcode FBMP
Dunning procedure
a)Define dunning interval reminder may be weekly, fornightly,monthly etc.
b)Define no. of days is arrears after which dunning notice will be sent
c)grace period per line item
d)interest calculation indicator for calculation of dunning interest
e)dunning key for dunning procedure.
Dunning levels
a)the first dunning level included the line item grace period
b)if option always dun selected the dunning notice will still printed even not change have been made in account
c) in dunning notice total account balance or item wise details can be print
Expenses/Changes
a)dunning charges may be depending on dunning level
b)dunning charges is either fixed for percentage of amount dunned
c)you can either choose fixed or precentage of amount dunned
d)dunning charges are define for currency wise
Minimum amount or percentage must be specifying for dunning notice the dunning notice will not generate until overdue item reached up to dunning level.
Minimum amount can also be fixed for calculating interest on dunning amount
dunning text must be defined according to the dunning level
predefined form of dunning text is available in sap
dunning program can generate payment advice note dunning notice and payment form
Environment
a) company code
b)short field
s)sender details
d)dunning areas
e)dunning key
f)dunning block reason
g)interest
h)dunning grouping
Running of dunning program
enter parameters
a) run date
b)identification
c)selection of company codes may be single company or no of companies
d)range of customer/vendor account
e)document define up to which posting date include in dunning run
Dunning run
May 8, 2008
Automatic Payments APP
SAP FI moudule we used automatic payment program.
APP we can used different payment methods such as check,transfers in printing a check or a electronic form
Account payable payment process
Create a financial accounting document to record the transaction it determines the following
Open items to be paid
when open items will be paid
bank from which payment will be made
payment medium to be used
to whom the payment will be made
Some tcode we used in automatic payment program
maintain paymet programm tcode-fbzp
setup all company code tcode-obvu
payment method country tcode-obvcu
define house bank tcode-fi12
Automatic payment configuration steps
------------------------------------
step 1
All company code:
a)inter company payment relationships
b) company code that process the payment
c)cash discount amount or percentage
d)tolerance days for payments
step -2
Paying company code
a)Minimum amount for incoming and outgoing payment
b)bills of exchange specification
c)Forms for payment advice EDI (payment advice format)
step-3
Payment methods/Country
a)payment methods eg. check bank transfer,bills of exchange
b)master record requirements address etc.
c)document type for posting
d) currencies if not set valid for all currencies
step -4
Payment method company code
a)Minimum and maximum payment amount
b)forign payment and foreign currencies allowed
d) postal code optimization
step -5
Bank selection
a)ranking if define the order of the various bank for payments
b)Amount- if define the available amount in bank account for payment
c)accounts
d) expenses/charges if any charges or amount short received the system post the amount in clearing account in case of outgoing payment and subtracts from incoming payment in case of payment received.
e)value date this is used for cash management if specify in how many days.
step 6
Maintain parameters (running payment program)
a)run date
b)identification
c)open item selection it defines that documents entered up to this date include in payment run
d)posting date this is the date on which general ledger is updated this is the default date from run date
e)company code selection maybe one company code or multiple company code in case of multiple company code,comma should be used between two company codes
Proposal Run
On the basis of parameters system run the proposal and if it found any incorrect in payment methods,bank data, payment block it adds these item exception list
On completion of proposal run system create two reports payment proposal list and exception list
Payment Block may configure in following ways
a) While invoice verification process
b)In Master records
c) During entering of account payable invoice
Editing Payment proposal
While editing the payment proposal a user can change the payment terms,
block of payment or remove the block
Start payment run
In this step we locked all the selected items for payment proposal for further posting updated the gl accounts and sub ledger accounts and clear open item.
Debit balance check if debit balance check carry out then transaction in exception list
I hope you will learn app
Syed Muzaffar
APP we can used different payment methods such as check,transfers in printing a check or a electronic form
Account payable payment process
Create a financial accounting document to record the transaction it determines the following
Open items to be paid
when open items will be paid
bank from which payment will be made
payment medium to be used
to whom the payment will be made
Some tcode we used in automatic payment program
maintain paymet programm tcode-fbzp
setup all company code tcode-obvu
payment method country tcode-obvcu
define house bank tcode-fi12
Automatic payment configuration steps
------------------------------------
step 1
All company code:
a)inter company payment relationships
b) company code that process the payment
c)cash discount amount or percentage
d)tolerance days for payments
step -2
Paying company code
a)Minimum amount for incoming and outgoing payment
b)bills of exchange specification
c)Forms for payment advice EDI (payment advice format)
step-3
Payment methods/Country
a)payment methods eg. check bank transfer,bills of exchange
b)master record requirements address etc.
c)document type for posting
d) currencies if not set valid for all currencies
step -4
Payment method company code
a)Minimum and maximum payment amount
b)forign payment and foreign currencies allowed
d) postal code optimization
step -5
Bank selection
a)ranking if define the order of the various bank for payments
b)Amount- if define the available amount in bank account for payment
c)accounts
d) expenses/charges if any charges or amount short received the system post the amount in clearing account in case of outgoing payment and subtracts from incoming payment in case of payment received.
e)value date this is used for cash management if specify in how many days.
step 6
Maintain parameters (running payment program)
a)run date
b)identification
c)open item selection it defines that documents entered up to this date include in payment run
d)posting date this is the date on which general ledger is updated this is the default date from run date
e)company code selection maybe one company code or multiple company code in case of multiple company code,comma should be used between two company codes
Proposal Run
On the basis of parameters system run the proposal and if it found any incorrect in payment methods,bank data, payment block it adds these item exception list
On completion of proposal run system create two reports payment proposal list and exception list
Payment Block may configure in following ways
a) While invoice verification process
b)In Master records
c) During entering of account payable invoice
Editing Payment proposal
While editing the payment proposal a user can change the payment terms,
block of payment or remove the block
Start payment run
In this step we locked all the selected items for payment proposal for further posting updated the gl accounts and sub ledger accounts and clear open item.
Debit balance check if debit balance check carry out then transaction in exception list
I hope you will learn app
Syed Muzaffar
Account Payable
Sap Financial accounting system Account payable
Account payable A/P, is sub ledger in Sap Fico and its used for vendor transctions and each transction create a documents with unique documents nos for audit trails purpose.
Step 1
Creation of vendor group
Menupath
Financial accounting-----–>account receivable and payble --->vendor accounts ---------master data---------->preparation -------->define accounts vendors
Assign nos rangs to vender accounts group
Financial accounting------->account receivable and payable ---master data-----preparation----assign nos ranges
Creation of vendor master data
Tcdoe FK01
Vendor Invoce posting TCODE FB60
vendor document type
Kr vendor invoice
KZ Vendor Payment
Posting key
Vendor debit 40
vendor credit 31
Menu path for account payable
SPRO--IMG--->accounting--->finanical accounting----->account payable---document entry account.
We can not post account payable transtions at fb50 tcode we have to post in specific vendor account and using vendor posting key
Vendor debit 40
vendor credit 31
We can post vendor invoice with purchase order and without purchase order
when invoice is posted MM material master record and PO History updated
Payable are paid by Automatic payment program APP
I cover in Next topic ....Automatic payment
Account payable A/P, is sub ledger in Sap Fico and its used for vendor transctions and each transction create a documents with unique documents nos for audit trails purpose.
Step 1
Creation of vendor group
Menupath
Financial accounting-----–>account receivable and payble --->vendor accounts ---------master data---------->preparation -------->define accounts vendors
Assign nos rangs to vender accounts group
Financial accounting------->account receivable and payable ---master data-----preparation----assign nos ranges
Creation of vendor master data
Tcdoe FK01
Vendor Invoce posting TCODE FB60
vendor document type
Kr vendor invoice
KZ Vendor Payment
Posting key
Vendor debit 40
vendor credit 31
Menu path for account payable
SPRO--IMG--->accounting--->finanical accounting----->account payable---document entry account.
We can not post account payable transtions at fb50 tcode we have to post in specific vendor account and using vendor posting key
Vendor debit 40
vendor credit 31
We can post vendor invoice with purchase order and without purchase order
when invoice is posted MM material master record and PO History updated
Payable are paid by Automatic payment program APP
I cover in Next topic ....Automatic payment
May 7, 2008
Lockbox
SAP Lockbox Process with Screen shot
Lockbox setting Segments
Define Lockbox
Define Control Parameters
Define Postind Data
tcode-ob10
tcode-obax
Q&A
What file used in Lockbox file extentions
Answrs is BAI or BAI2
Menu Paht
SPRO---->FININCIAL ACCOUNTING--->BANK ACCOUNTING--->BANK ACCOUNT-->DEFINE LOCKBOX FOR HOUSE BANK
Define control parameters
Menu path
spro-->financial accounting-->bank accounting--->business transactions--->payment transaction--->lockbox--->define control paramenters.
Define posting Data
Menu Path IMG
spro-->financial accounting-->bank accounting--->business transactions--->payment transaction--->lockbox--->define posting data
FBL1 UPLOAD LOCKBOX FILE DATA
FBL2 POSTING PRCOESSING OF LOCKBOX DATA
Lockbox setting Segments
Define Lockbox
Define Control Parameters
Define Postind Data
tcode-ob10
tcode-obax
Q&A
What file used in Lockbox file extentions
Answrs is BAI or BAI2
Menu Paht
SPRO---->FININCIAL ACCOUNTING--->BANK ACCOUNTING--->BANK ACCOUNT-->DEFINE LOCKBOX FOR HOUSE BANK
Define control parameters
Menu path
spro-->financial accounting-->bank accounting--->business transactions--->payment transaction--->lockbox--->define control paramenters.
Define posting Data
Menu Path IMG
spro-->financial accounting-->bank accounting--->business transactions--->payment transaction--->lockbox--->define posting data
FBL1 UPLOAD LOCKBOX FILE DATA
FBL2 POSTING PRCOESSING OF LOCKBOX DATA
House Bank
SAP FICO MODULE WHAT IS HOUSE BANK
House Bank Tcode FI12 Bank Directory
Question
1--What is House bank......?
Answers
House bank we call all accounts that belong to company. A house bank refers to the bank a company uses for receivables and/or payments. It is any bank with which your company code does business. Each house bank contains a company’s bank accounts. It also contains a bank key that defines address and control data for the bank. The house bank establishes a link between the various G/L cash accounts and the actual bank accounts.
2---What is bank directory.....?
Automatically, if master data exists for the Bank Directory on tape or disk. ). Data can also be manually entered when creating a customer or vendor master record, a one-time account, or by directly creating an account.
a---Bank Directory contain
a---Bank Directory contains complete details about each house bank.
3--where are bank master records created in SAP...?
Unlike customer, and vendor master records, the bank master records may be maintained on the configuration side in SAP. They are also created on the application side in the Banking and Treasury sections.
Bank configuration steps screen shot
House Bank Tcode FI12 Bank Directory
Question
1--What is House bank......?
Answers
House bank we call all accounts that belong to company. A house bank refers to the bank a company uses for receivables and/or payments. It is any bank with which your company code does business. Each house bank contains a company’s bank accounts. It also contains a bank key that defines address and control data for the bank. The house bank establishes a link between the various G/L cash accounts and the actual bank accounts.
2---What is bank directory.....?
Automatically, if master data exists for the Bank Directory on tape or disk. ). Data can also be manually entered when creating a customer or vendor master record, a one-time account, or by directly creating an account.
a---Bank Directory contain
a---Bank Directory contains complete details about each house bank.
3--where are bank master records created in SAP...?
Unlike customer, and vendor master records, the bank master records may be maintained on the configuration side in SAP. They are also created on the application side in the Banking and Treasury sections.
Bank configuration steps screen shot
May 5, 2008
Customer Master Record
ALL ABOUT CUSTOMER MASTER DATA RECORDS
Transctions code related to Customer accounts
Create customer master records TCODE FD01
Change customer master records TCODE FD02
Display customer master records Tcode fd03
Block/unblock customer master Tcode FD05
Mark customer master records for deletion fd06
Questions.
What is customer data record Segments.
Answers.
Customer master record has three segments
In General Data Account Name, Address
In Company code level payment terms
In Sales Data Shipping information, billing information
Customer master Data record in two levels
1- Client Level : Data at this level pertain to all companies in that client can open
2- Company Code Level Company specific data is entered at this level is for specific company.
Account receiveable is customer account in sap its a sub ledger accounts recon account and we cant post directly thought enjoy posting fb50,
Questions
How to prevent Duplicates of customer master records
Answers
Check for duplicates can be configured to prevent the creation of more then one master record for the same customers.
This check configured on address match when create new customer records.
Menu Path IMG SPRO-->Logistics -->Sales and Distribution---> Master Data---> Business Partner-----> Customer----> Create---> Complete
tcode is xd01 Create customer master record
Display xd03 display customer list
tcode FD32 customer credit management master record
Qustions
What is Payment terms
answers
Payments terms In payment terms define incentive which company give to there customers to pay invoice early and get some discounts and when due date is calculated to calculate due date we used baseline.
Baseline date is date when payment begin calculate from
Transctions code related to Customer accounts
Create customer master records TCODE FD01
Change customer master records TCODE FD02
Display customer master records Tcode fd03
Block/unblock customer master Tcode FD05
Mark customer master records for deletion fd06
Questions.
What is customer data record Segments.
Answers.
Customer master record has three segments
In General Data Account Name, Address
In Company code level payment terms
In Sales Data Shipping information, billing information
Customer master Data record in two levels
1- Client Level : Data at this level pertain to all companies in that client can open
2- Company Code Level Company specific data is entered at this level is for specific company.
Account receiveable is customer account in sap its a sub ledger accounts recon account and we cant post directly thought enjoy posting fb50,
Questions
How to prevent Duplicates of customer master records
Answers
Check for duplicates can be configured to prevent the creation of more then one master record for the same customers.
This check configured on address match when create new customer records.
Menu Path IMG SPRO-->Logistics -->Sales and Distribution---> Master Data---> Business Partner-----> Customer----> Create---> Complete
tcode is xd01 Create customer master record
Display xd03 display customer list
tcode FD32 customer credit management master record
Qustions
What is Payment terms
answers
Payments terms In payment terms define incentive which company give to there customers to pay invoice early and get some discounts and when due date is calculated to calculate due date we used baseline.
Baseline date is date when payment begin calculate from
May 4, 2008
Open Item Management
Q&A
What is open item managements
Answers
Open item management account is a offsetting accounts which can be settled automatically by manually
we can used for cheque clearing account when our cheque is debits from our account the open item clear account balance is zero GR & IR account is an example of an account that should be managed on an open item basis.
If I am not correct please correct me thanks
syed
What is open item managements
Answers
Open item management account is a offsetting accounts which can be settled automatically by manually
we can used for cheque clearing account when our cheque is debits from our account the open item clear account balance is zero GR & IR account is an example of an account that should be managed on an open item basis.
If I am not correct please correct me thanks
syed
Chart of Account COA
Q&A About SAP FI Chart of Account COA
Q&A
How many chart of account we can used for one company code
Three type of Chat of account we can used for one company code
1-Operation Chart of account
2-Country chart of account
3-Group chart of account we can used in company code
1-operational chat of account is record you daily transactions
2-country chart of account is used for country specific requirement
3-Group chart of account is used when we have two or many legal entities I mean company code and we need consolidation report of all companies combine report.
Company can share chart of accounts
and GL accounts as well if we create gl account at chart of account level we can create gl account at two levels in SAP FI Module we can create chart of account COA, Level then other companies can share gl accounts if they using the same chart of accounts but if we crate gl account at company code level we can used this gl accounts only for that company code where we created
What is Chart of accounts.
Chart of account is list of GL accounts, and creat at client level one client can have many chart of accounts, but one company can have only one operational chart of accounts.
COA segment contains information such as the Account Number, Account Name, and Account Group
Q&A
How many chart of account we can used for one company code
Three type of Chat of account we can used for one company code
1-Operation Chart of account
2-Country chart of account
3-Group chart of account we can used in company code
1-operational chat of account is record you daily transactions
2-country chart of account is used for country specific requirement
3-Group chart of account is used when we have two or many legal entities I mean company code and we need consolidation report of all companies combine report.
Company can share chart of accounts
and GL accounts as well if we create gl account at chart of account level we can create gl account at two levels in SAP FI Module we can create chart of account COA, Level then other companies can share gl accounts if they using the same chart of accounts but if we crate gl account at company code level we can used this gl accounts only for that company code where we created
What is Chart of accounts.
Chart of account is list of GL accounts, and creat at client level one client can have many chart of accounts, but one company can have only one operational chart of accounts.
COA segment contains information such as the Account Number, Account Name, and Account Group
May 3, 2008
Organizational Hierarchy
Major Organizational Hierarchy
The hierarchy, from the highest organizational unit to the lowest, is the
Client,
Chart of Accounts (COA),
Company Code
and the optional Business Areas (BA).
Two other optional areas include the Dunning Area and the Credit Control Area
(CCA). Credit Control Areas come above the Company Code, and Dunning Areas come below the Company Code.
There is only one Client and its values are the same across all Company Codes that are attached to it. Every Company Code is a legal independent entity. Business Areas can be shared among Company Codes (many-to-many relationship) and they are used for internal reporting purposes. Each Company Code is assigned a COA. The COA may be the same for multiple Company Codes, but each Company Code may only use one COA.
The hierarchy, from the highest organizational unit to the lowest, is the
Client,
Chart of Accounts (COA),
Company Code
and the optional Business Areas (BA).
Two other optional areas include the Dunning Area and the Credit Control Area
(CCA). Credit Control Areas come above the Company Code, and Dunning Areas come below the Company Code.
There is only one Client and its values are the same across all Company Codes that are attached to it. Every Company Code is a legal independent entity. Business Areas can be shared among Company Codes (many-to-many relationship) and they are used for internal reporting purposes. Each Company Code is assigned a COA. The COA may be the same for multiple Company Codes, but each Company Code may only use one COA.
Sap Conf & Org Struct
Sap Configuration and Application
Questions Give examples of activities performed on the configuration side in SAP? On the application side in SAP?
Answer
Configuration:
• Create Organizational structures
• Define foreign currencies
• Define financial statements
• Outline Credit Management functionality
Application:
• Post Accounting transactions
• Post Customer Invoice
• Post Vendor Invoice
• Create Master records
• Process financial statements
• Display accounting documents
Questions Give examples of activities performed on the configuration side in SAP? On the application side in SAP?
Answer
Configuration:
• Create Organizational structures
• Define foreign currencies
• Define financial statements
• Outline Credit Management functionality
Application:
• Post Accounting transactions
• Post Customer Invoice
• Post Vendor Invoice
• Create Master records
• Process financial statements
• Display accounting documents
Interview Q&A
SAP FICO Interview Questions
What is Client and Company code relation...
Answers
The Client is the highest level in the SAP organizational structure. Anything specified for a Client applies to all Company Codes that are attached to that Client. Clients have a one-to-many relationship with Company Codes. Clients are generally not reported on with balance sheet and P&L’s, the company codes are the legal entities and serve for this purpose. However, clients can be reported on as part of consolidation or extended G/L.
Questions
Major organizational hierarchy elements
Answer
The hierarchy, from the highest organizational unit to the lowest, is the
Client,
Chart of Accounts (COA),
Company Code
and the optional Business Areas (BA).
Two other optional areas include the Dunning Area and the Credit Control Area
(CCA). Credit Control Areas come above the Company Code, and Dunning Areas come below the Company Code.
There is only one Client and its values are the same across all Company Codes that are attached to it. Every Company Code is a legal independent entity. Business Areas can be shared among Company Codes (many-to-many relationship) and they are used for internal reporting purposes. Each Company Code is assigned a COA. The COA may be the same for multiple Company Codes, but each Company Code may only use one COA.
Question
What is the correction and transport system? Who operates this system?
Answers
Transport request tcode se01,T-code STMS ,se09
------------------
The Correction and Transport System provides a method to move configuration and program code from system to system or Client to Client. It would be used to move customized data from a development system to a test system, and then to a production system.
The Correction and Transport System is usually operated by the System Administrator.
You have the option to search with - User range , request range & date range. There are other selection criteria too if you want Here you can find ANY request ( prod, testing, devlp) - whether released or modifiable.
you can see list of old trans requests tcode SE01
Workbench transport request se09
For customising transport request tcode se10
Questions
What is organizational structure?
Answers
Company code
controlling area
buiness area
functional area
Credit control area
Sap structure levels
Client level ---Chart of accounts,controlling area,business area,
One clint can have many company code, controlling area.
But one Company code can not have many client,or many controlling area,
company code level gl accounts,vendor,customers for master data
company code is legal entity... reporting to external auditors...income tax dept..
business area is uses for internal report
Question
Who is usually responsible for establishing the organizational structure on an implementation
Answers
FI/CO Team
Question : What are the tables that are configured under global settings?
Answers : Calendar, Units of Measure, Country Table, and Currency & Exchange Rate Table
Questions :-Cash Management is a sub-module of which module..?
Answers :Treasury module
Questions :Can depreciation be processed from Asset Accounting sub-module directly to the FI and CO Modules?
Answers : YES
Question:What are the two major areas within the SAP environment? Describe each.
Answers : Configuration - Maintenance of settings in the system to support customized business requirements of the client.
&
Application - On going processes required to record and report business activity
Questions: What are the two methods available for accessing the configuration functions in FI? Describe each.
Answers :Implementation Guide (IMG) - leads you through the steps required for configuration in an implementation.
Transaction codes - takes you directly to the first screen of a transaction without the use of the IMG or menu paths
Questions
What is in Account Management....?
Answers
Open Item Management
Line Item Display
Sort Key
Questions:What are the four configuration areas of the IMG? Describe each.
Anwers :
General Settings - non-application dependent specifications
Enterprise Structure - definition of organizational units and their relationships
Cross-applications component
Functional Areas (e.g., Financial Accounting, Sales and Distribution)
Question
What is the highest level of information in SAP? Where is this configured?
Answers
General Settings, which is configured in the IMG
Questions
What is simple accounts
Anwers
A sample account kind of template that can be used to create GL accounts is not actual account in GL.
What is Client and Company code relation...
Answers
The Client is the highest level in the SAP organizational structure. Anything specified for a Client applies to all Company Codes that are attached to that Client. Clients have a one-to-many relationship with Company Codes. Clients are generally not reported on with balance sheet and P&L’s, the company codes are the legal entities and serve for this purpose. However, clients can be reported on as part of consolidation or extended G/L.
Questions
Major organizational hierarchy elements
Answer
The hierarchy, from the highest organizational unit to the lowest, is the
Client,
Chart of Accounts (COA),
Company Code
and the optional Business Areas (BA).
Two other optional areas include the Dunning Area and the Credit Control Area
(CCA). Credit Control Areas come above the Company Code, and Dunning Areas come below the Company Code.
There is only one Client and its values are the same across all Company Codes that are attached to it. Every Company Code is a legal independent entity. Business Areas can be shared among Company Codes (many-to-many relationship) and they are used for internal reporting purposes. Each Company Code is assigned a COA. The COA may be the same for multiple Company Codes, but each Company Code may only use one COA.
Question
What is the correction and transport system? Who operates this system?
Answers
Transport request tcode se01,T-code STMS ,se09
------------------
The Correction and Transport System provides a method to move configuration and program code from system to system or Client to Client. It would be used to move customized data from a development system to a test system, and then to a production system.
The Correction and Transport System is usually operated by the System Administrator.
You have the option to search with - User range , request range & date range. There are other selection criteria too if you want Here you can find ANY request ( prod, testing, devlp) - whether released or modifiable.
you can see list of old trans requests tcode SE01
Workbench transport request se09
For customising transport request tcode se10
Questions
What is organizational structure?
Answers
Company code
controlling area
buiness area
functional area
Credit control area
Sap structure levels
Client level ---Chart of accounts,controlling area,business area,
One clint can have many company code, controlling area.
But one Company code can not have many client,or many controlling area,
company code level gl accounts,vendor,customers for master data
company code is legal entity... reporting to external auditors...income tax dept..
business area is uses for internal report
Question
Who is usually responsible for establishing the organizational structure on an implementation
Answers
FI/CO Team
Question : What are the tables that are configured under global settings?
Answers : Calendar, Units of Measure, Country Table, and Currency & Exchange Rate Table
Questions :-Cash Management is a sub-module of which module..?
Answers :Treasury module
Questions :Can depreciation be processed from Asset Accounting sub-module directly to the FI and CO Modules?
Answers : YES
Question:What are the two major areas within the SAP environment? Describe each.
Answers : Configuration - Maintenance of settings in the system to support customized business requirements of the client.
&
Application - On going processes required to record and report business activity
Questions: What are the two methods available for accessing the configuration functions in FI? Describe each.
Answers :Implementation Guide (IMG) - leads you through the steps required for configuration in an implementation.
Transaction codes - takes you directly to the first screen of a transaction without the use of the IMG or menu paths
Questions
What is in Account Management....?
Answers
Open Item Management
Line Item Display
Sort Key
Questions:What are the four configuration areas of the IMG? Describe each.
Anwers :
General Settings - non-application dependent specifications
Enterprise Structure - definition of organizational units and their relationships
Cross-applications component
Functional Areas (e.g., Financial Accounting, Sales and Distribution)
Question
What is the highest level of information in SAP? Where is this configured?
Answers
General Settings, which is configured in the IMG
Questions
What is simple accounts
Anwers
A sample account kind of template that can be used to create GL accounts is not actual account in GL.
GL Accounts
Features of the FI GL Accounts module
Fi-GL accounts,
• Multiple currency capability
• Flexible real-time reporting
• Real-time transaction entry
Fi-GL accounts,
• Multiple currency capability
• Flexible real-time reporting
• Real-time transaction entry
Integrated FI-SD
FI-AR Integrated with Sales & distribution
Questions:-FI-AR is closely integrated with which other module(s) within SAP? Which cycle does this support?
The Accounts Receivable (FI-AR) module is closely integrated with the Sales & Distribution and Material Management modules. FI-AR supports the Sales cycle
Questions :-FI-AP is closely integrated with which other module(s) within SAP? Which cycle does this support?
The FI-AP module is a closely integrated with the Materials Management (MM) module. The Accounts Payable module supports the Procurement Cycle
Sap fi Finance GL Account integrate with sd sale and distributions We used tcode vkoa
But when sales order create no affect on FI
But when billing documents create its affect in FI
customer account dr
Sales and revenue account cr
and When payment received from customers
Bank account dr
customers account dr
Questions:-FI-AR is closely integrated with which other module(s) within SAP? Which cycle does this support?
The Accounts Receivable (FI-AR) module is closely integrated with the Sales & Distribution and Material Management modules. FI-AR supports the Sales cycle
Questions :-FI-AP is closely integrated with which other module(s) within SAP? Which cycle does this support?
The FI-AP module is a closely integrated with the Materials Management (MM) module. The Accounts Payable module supports the Procurement Cycle
Sap fi Finance GL Account integrate with sd sale and distributions We used tcode vkoa
But when sales order create no affect on FI
But when billing documents create its affect in FI
customer account dr
Sales and revenue account cr
and When payment received from customers
Bank account dr
customers account dr
SAP & ERP
What Is ERP and SAP
ERP is Enterprise resource planning.
In very simple way I can say that ERP is a system which help you to used one centerlised database which integrate with all department so you dont need to enter same data for other department you can save time and cost to entry data in two places and lot more.....
Sap is a ERP system.
SAP was founded in 1972 in Walldorf, Germany. It stands for Systems, Applications and Products.
ERP is Enterprise resource planning.
In very simple way I can say that ERP is a system which help you to used one centerlised database which integrate with all department so you dont need to enter same data for other department you can save time and cost to entry data in two places and lot more.....
Sap is a ERP system.
SAP was founded in 1972 in Walldorf, Germany. It stands for Systems, Applications and Products.
May 2, 2008
Integration SD,MM,PP
Integration With Other Modules SD,MM,PP
Integration is the process by which data entered in one module is used by or updates another module on a real-time basis.
SD=Sales and distributions
mm=Material Management
PP=Production planning
Integration is the process by which data entered in one module is used by or updates another module on a real-time basis.
SD=Sales and distributions
mm=Material Management
PP=Production planning
- Main questions in this topic is when FI -GL account data is update real time and how to connect with mm and what is the tcode uses for.......~
TCode for MM-FI- OBYC.
When PO Purchase order is issues No affect on FI
But When GR Goods Received is posted that affect in FI Inventory/Stock Account entry should
Inventory Account Dr
GRIR account Cr
But When IR/GR. Invoice Received is post entry is
GRIR account Dr
Vendor Account Cr
When you paid to vendor entry .....
Vendor account Dr.
Bank account CR.
Goods movement Goods Receipt, Goods Issue will affect the FI GL-accous and stock will update from MM to FI. Tcodes we used for OMJJ,OMWN,OMWB
Subscribe to:
Posts (Atom)
Subscribe To
Posts
All Comments