Sap General Setting Tables names

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

The Best SAP Books Reviewed

The Best SAP Books Reviewed

Fico Interview Questions

Sap Training Center California FICO Module
Click below link to find more about fico interview questions

how transactions and balances are assigned to profit centres

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.



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.



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

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

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.

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.

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

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

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.

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

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

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.

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.

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 File Extention or File name Type

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