Accounts Receivable in SAPLearn complete configuration steps of Accounts Receivable module of SAP FI. Understand Bill of Exchange, Dunning, Customer Master Records, Collection.
Preview Accounts Receivable in SAP courseView Course Curriculum Price Match Guarantee Full Lifetime Access Access on any Device Technical Support Secure Checkout   Course Completion Certificate
- 79% Started a new career
BUY THIS COURSE (
USD 17 GBP 29)
- 93% Got a pay increase and promotion
Students also bought -
- Bundle Course - SAP for Business (BPC and FICO)
- 60 Hours
- USD 23
- 323 Learners
- Financial Accounting & Reporting
- 75 Hours
- USD 17
- 2666 Learners
- SAP FICO (comprehensive)
- 35 Hours
- USD 17
- 2834 Learners
SAP Accounts Receivable, a module of SAP FI, is used to manage and record accounting data for all customers. It handles customer invoices, approvals, payments and other allied activities. Postings made in Accounts Receivable are updated in General Ledger G/L.
AR is also an integral part of sales management. AR process covers the area from Customer Master creation, through Collection, Dispute and Dunning Management to eventually booking of incoming payments of customers. Furthermore it covers the area of daily bank reconciliation (incoming and outgoing mutations on banks/bankstatements) plus invoice creation (invoices other than standard billing).
SAP Accounts Receivable deals with managing customer invoices and payments. It is an important part of the SAP Financial Accounting (FI) module, and allows companies to keep track of their accounts receivable (i.e. money owed to them by customers) in an organized and efficient way.
The important SAP Accounts Receivable (AR) Transaction codes are: FD11, FD10, FRCA, VD01, FD33. Important Accounts Receivable (AR) Tables are: KNA1, KNVV, BSIW, KNKA. Important Components of SAP AR are: Down Payments (FI-AR-AR-DP), Payment Transactions (FI-AR-AR-PT), Credit Management (FI-AR-CR), Information System (FI-AR-IS).
The main processes in SAP Accounts Receivable are:
a) Maintain Master Data
b) Credit Management
c) Invoice Processing
d) Cash Receipts and Payments
e) Accounts Analysis and Reconciliation
The SAP Accounts Receivable module includes various functionalities, such as:
1. Customer Master Data: This includes creating and maintaining customer master records, which contain important information about each customer, such as their name, address, payment terms, credit limit, and other relevant details.
2. Invoice Processing: This involves creating and processing invoices for customers, including generating invoices, posting them to the appropriate customer accounts, and tracking their status.
3. Payment Processing: This involves managing customer payments, including receiving payments, applying them to the appropriate customer accounts, and reconciling payments with invoices.
4. Credit Management: This involves setting credit limits for customers, monitoring their payment behavior, and taking appropriate actions if payments are not received on time.
5. Reporting: This includes generating reports on accounts receivable, such as aging reports, open item lists, and customer account balances.
In summary, the SAP Accounts Receivable module helps companies to manage their cash flow and reduce the risk of bad debt by ensuring that invoices are processed and payments are received in a timely manner.
Uplatz provides this comprehensive course on Accounts Receivable in SAP. You will learn each and every feature, functionality, configuration, and usage of SAP Accounts Receivable sub-module in this comprehensive SAP Accounts Receivable training with real-world scenarios and practical examples.
Course/Topic - Accounts Receivable in SAP - all lectures
In this first video on Accounts Receivable in SAP tutorial, you will learn about the different activities associated with the customer account such as defining account groups with screen layout and creating and assigning number ranges for customer account groups. This will be seen explained thoroughly by the instructor in the SAP system. Further, you will be seeing how to create different types of G/L accounts.
In this video tutorial, you will learn about the different terms associated with the customer payment such as maintaining terms of payment for a particular duration like 15, 30 or 45 days, assigning terms of payment to customer, creation of G/L account for cash discount granted and expenses, assignment of account for automatic posting, vendor invoice and the vendor payment. All these steps will be seen explained practically by the tutor in the SAP system.
In this tutorial, you will learn about the complete practical demonstration on the Dunning Procedure being used in the Accounts Receivable module like the scheduling of the dunning selection, dunning parameters and others. You will also learn about the Bill Discounting, along with getting the answers to questions like where and why this is used in the organizations.
In this video, you will understand how to work on the Cash Journal in respect to any financial accounting, along with the life cycle of fixed assets. You will also learn a complete overview of the Asset Accounting and a work around of it being used as a sub-ledger.
In this video, you will learn a complete practical demonstration on how to work on the amount depreciation in asset accounting and sorting and loss based on asset number. You will also learn the prerequisites for automatic posting which are Chart of Depreciation, Account Determination, Chart of accounts and G/L accounts.
In this final video of the tutorial, you will learn and understand the complete process of how to create individual assets under the Asset Master and linking the depreciation key to the same. This will be taught by practical and detailed explanation by the tutor through the Easy Path in the SAP system.
In this SAP Accounts Receivable course, you will learn how to:
1) Create customer account groups
2) Maintain number ranges for customer account groups
3) Assign number ranges to customer account groups
4) Define Risk Categories
5)Maintain tolerance group for customer accounts
6) Define sundry debtor account (G/L)
Other benefits of learning Accounts Receivable in SAP include:
• Improve your cash position
• Increase control over cash and working capital
• Increase Accounts Receivable management efficiency
• Improve customer communication
• Learn to work with customer records, balances and line items
• Post, search and display customer docs
• Post customer payments and process dunning runs
• Run financial reports such as A/R Info systems, Customer balances, Customer lists
· Creation of customer account groups
· Creation of number ranges for customer master records
· Assignment of number ranges for customer account groups
· Creation of tolerance group for customers
· Creation of customer master (display/change/block/unblock of vendor master)
· Posting of customer transactions (sales invoice posting, payment posting, debit memo)
· Display customer balances and G/L Balances
· Configuration Settings for advance payment from customers (down payment)
· Configuration settings for terms of payment to customers
· Configuration of settings for dunning
· Generating the dunning letters
· Defining correspondence and party statement of accounts
· Bills of exchange
· Posting of sales returns
This Accounts Receivable in SAP training course is designed for clearing the SAP Certified Accounts Receivable Associate exam. The Accounts Receivable in SAP is a sub-module of SAP FI which h is used for record and manage accounting for customers.
In Accounts Receivable in SAP Course module the participants can learn to manage the key activities such as master data maintenance, invoice processing, account analysis. In the Accounts Receivable in SAP course, the participants will learn the accounts receivable functions such as report creation, forecast features to track vendor or customer pending payments. This seems to be an essential learning for all SAP Finance Accounts module users.
The Accounts Receivable in SAP Certification is an important benchmark in becoming an expert Accounts Receivable Associate as the course covers accounts receivable overview, handling customer master records, account groups and sales return. Accounts Receivable in SAP tutorial helps the participants to learn all the key concepts of General-ledger accounting thus attaining a unique SAP certification. Accounts Receivable in SAP course offers complete information about accounts Receivable sub-module of SAP FICO thus making the participant an expert Accounts Receivable Associate.
Uplatz online training guarantees the participants to successfully go through the Accounts Receivable certification provided by SAP. Uplatz provides appropriate teaching and expertise training to equip the participants for implementing the learnt concepts in an organization.
Course Completion Certificate will be awarded by Uplatz upon successful completion of the Accounts Receivable in SAP course.
The Accounts Receivable in SAP certification exam verifies that the participants possess basic knowledge and can prove their skills in the area of SAP ERP Financial Accounting. This Accounts Receivable in SAP certification exam validates that the participant has an overall understanding about this Accounts Receivable Associate profile, and able to implement the knowledge practically in projects.
Below given are the Certification details of:
SAP Certified Application Associate - Financial Accounting with SAP ERP 6.0 EhP7
· Certification Level: Associate
· Exam Name: SAP Certified Application Associate - Financial Accounting with SAP ERP 6.0 EhP7
· Exam Code: C_TFIN52_67
· Exam Mode: Online
· Total Number of Questions: 80
· Pass Score: 60%
· Time Duration: 180 Minutes
· Exam Price: $550
The SAP Account Receivable Associate draws an average salary of $67,187 per year depending on the knowledge and hands-on experience. The SAP Account Receivable Associate job roles are in high demand and make a rewarding career.
SAP Account Receivable Associate are recognized across the globe. The increased usage of the finance processes in many companies help the participants to find a job opportunity easily. The leading companies hire SAP Account Receivable Associate considering the skill of handling finance and cash management in an organization. The Learners earn most beneficial Accounts Receivable in SAP certification through our expert training and course curriculum. Being SAP Accounts Receivable certified is definitely valuable credential and adds value to every organization.
The Accounts Receivable in SAP certification is targeted to those participants who are beginners or from finance accounting background and excel as SAP Accounts Receivable Associate.
The following are the job titles:
· SAP FICO Consultant / End user
· Accounts Receivable Specialist
· Accounts Receivable Associate
· Accounts Receivable Clerk
· SAP Accounts Manager
· Accounts Consultant
The course content, and the overall certification program helps the participants to get placed in reputed MNCs and organizations.
Q.1. WHAT IS SAP FI - ACCOUNTS RECEIVABLE?
SAP FI Accounts Receivable component records and manages accounting data of all customers. It is also an integral part of sales management.
All postings in Accounts Receivable are also recorded directly in the General Ledger. Different G/L accounts are updated depending on the transaction involved (for example, receivables, down payments, and bills of exchange). The system contains a range of tools that you can use to monitor open items such as account analyses, alarm reports, due date lists, and a flexible dunning program.
The correspondence linked to these tools can be individually formulated to suit your requirements. This is also the case for payment notices, balance confirmations, account statements, and interest calculations. Incoming payments can be assigned to due receivables using user-friendly screen functions or by electronic means such as EDI.
The payment program can automatically carry out direct debiting and down-payments.
We have a range of tools available for documenting the transactions that occur in Accounts Receivable, including balance lists, journals, balance audit trails, and other standard reports. When drawing up financial statements, the items in foreign currency are revalued, customers who are also vendors are listed, and the balances on the accounts are sorted by their remaining life.
Accounts Receivable is not merely one of the branches of accounting that forms the basis of adequate and orderly accounting. It also provides the data required for effective credit management (as a result of its close integration with the Sales and Distribution component) as well as important information for the optimization of liquidity planning.
Q.2. EXPLAIN WHAT ARE THE ISSUES RELATED WITH ACCOUNTS RECEIVABLE?
As the Accounts Receivable Supervisor, you will:
· Oversee and resolve all issues related to cash application to ensure accuracy.
· Reconcile daily cash receipts to payment register.
· Design and implement new Accounts Receivable processes and procedures.
· Process short payment and accounts receivable adjustment forms.
· Develop and maintain reports to assess team productivity.
· Invoice special customer accounts.
· Supervise five Accounts Receivable Associates.
· Other duties as may be assigned.
Q.3. WHAT IS THE 'DUNNING AREA?
The 'Dunning Area' is optional and is required only if dunning is not done at the Company Code level. The Dunning area can correspond to a sales division, sales organization, etc.
Q.4. WHAT DIFFERENTIATES ONE 'DUNNING LEVEL' FROM ANOTHER?
The 'Dunning Level' determines the 'dunning text' and (if one is required) a 'special dunning form'. The 'dunning program' determines what 'dunning level' should be used in the 'dunning run.' The dunning level so determined is stored in the master record of the account when the 'dunning letter' is printed. The dunning level may also determine whether there will be some 'dunning charges'.
Q.5. HOW MANY ‘DUNNING LEVELS’ CAN BE DEFINED?
You may define up to nine dunning levels. If there is only one dunning level, then it is called a ‘payment reminder.’
Q.6.CAN YOU ‘DUN’ CUSTOMERS ACROSS ‘CLIENTS’ IN A SINGLE ‘DUNNING RUN’?
No. All the data processing is carried out per Client.
Q.7. EXPLAIN CUSTOMER/VENDOR MASTER RECORDS?
There are three categories of data maintained in a typical master record for a customer:
Company Code Data
Sales Area Data (for customers)/Purchasing Organization Data (for vendors)
General Data includes general information such as account number, name, telephone, bank information, trading partner, vendor (if the customer is also a vendor), group key, bank key, bank account, alternate payee, etc., which are common to all the Company Codes using this master. Company Code Data comprises terms of payment, payment methods, tolerance group, clearing with vendor, dunning data (dunning procedure, dunning recipient, dunning block, dunning clerk, etc.), reconciliation account, sort key, sales area (purchasing organization in the case of vendor master), head office, etc. Except for sales (purchasing) related information, all other details are usually maintained for the finance people who can also access the sales data when the master is maintained ‘centrally.’
Sales Area Data in the Company Code area of a Customer master record contains the following:
Order-related data (sales district, sales office, sales group, customer group, etc.)
Price-related data (pricing group, pricing procedure, etc.)
Shipping data (shipping strategy, delivery priority, etc.)
Billing data (payment terms (different from the payment terms maintained at the
Company Code level), account assignment group, etc.)
Purchasing Organization Data in the Company Code area of a Vendor master record contains the following:
Conditions (order currency, payment terms, Incoterms, minimum order value, etc.)
Sales data (a/c with Vendor)
Control data (as in the screen shot below)
During creation of a master record, the system checks for ‘duplicates’ for the same customer which is achieved by the system through the ‘Search-Id’ (Match Code) configured on the customer’s address information.
As in the case of the GL account master record, the creation of the customer/ vendor master record is also controlled by the ‘Account Group,’ which is called ‘Customer Account Group/Vendor Account Group’ (CPD/CPDL/KREDI/LIEF) and controls the numbering of customer/vendor master records, field status, whether an account is a regular one or a ‘One Time’ account, etc.
Open table as spreadsheet Activity in Accounting Centrally
Customer Vendor Customer Vendor
Create FD01 FK01 XD01 XK01
Change FD02 FK02 XD02 XK02
Display FD03 FK03 XD03 XK03
Block/Unblock FD05 FK05 XD05 XK05
Mark for Deletion FD06 FK06 XD06 XK06
Q.8. WHO IS AN ‘ALTERNATE PAYEE’?
A customer who pays on behalf of another customer is known as an ‘Alternate Payee’ (or Alternate Payer). Though the alternate payee pays on behalf of another, the system maintains all the transaction details in the account of the original customer. Designating ‘alternate payee’ does not absolve the customer of his/her obligation for payment.
The ‘alternate payee’ can be maintained in Client-specific data or in the Company Code area. When maintained in the Company Code area you can use that payer only in that Company Code; if defined at the Client level you can use it across all Company Codes. There are three ways to ‘select’ the alternate payee when an invoice is processed:
1. The alternate payee (say, 1000) entered in the customer master record is the one
selected by the system as the default.
2. When there is more than one alternate payer (say, 1000, 1900, 2100, etc.) defined for a single customer in the master record (you will do this by clicking on the ‘allowed payer’ button and create more than one payer), you may select a payer (say, 2100) (other than the default, 1000) while processing the invoice. Now the system will ignore the alternate payer (1000) coming from the master record.
3. If you have put a check mark in the ‘individual entries’ check box in the ‘alternate payer in document’ section in the customer master record, then this will allow you to propose a new alternate payer, say, 3000 (other than those already defined in the system). Now, after defining this alternate payer you can use it to process the invoice. In this case, the alternate payer (3000) takes precedence over the payers (1000 and 2100) in step 1 and 2 above.
Q.9.WHAT IS THE ‘TRADING PARTNER’ CONCEPT?
The ‘Trading Partner’ concept is used to settle and reconcile ‘inter-company transactions,’ both sales and purchases. This is generally achieved by entering the Company-ID (not the Company Code) to which a customer belongs in the ‘trading partner’ field under the tab ‘Account Control’ in the customer master record. You can do a similar entry in the vendor master record.
Q.10.EXPLAIN ‘TOLERANCE’ IN TRANSACTION PROCESSING?
‘Tolerances’ are defined in the system to facilitate dealing with the differences arising out of accounting transactions and to instruct the system on how to proceed further. Normally, you define tolerances (either in ‘absolute terms’ or in ‘percentages’) beyond which the system will not allow you to post a document should there be a difference.
In SAP, tolerances are defined per Company Code and there are several types:
GL account clearing tolerance
You will define an ‘employee tolerance group’ in the system and assign the employees to these groups.
While defining the tolerance group you will specify:
1. Upper limits for various posting procedures
Amount per document
Amount per open account item
Cash discount, in percentage
2. Permitted payment differences
How much over or under payment an employee is allowed to process. This is defined both in absolute values and in percentages. Besides defining the above two, at the Company Code level, you will also define similar tolerances for customer/vendor tolerance group. Once defined, each of the customers (vendors) is assigned to one of these groups. Here also, you define the ‘permitted payment differences’:
While processing, the system compares the tolerance of an employee against the customer tolerance (or vendor tolerance or the GL) and applies the most restrictive of the two.
Q.11. WHAT IS ‘DUAL CONTROL’ IN MASTER RECORDS?
‘Dual Control’ helps to prevent unauthorized changes to the important and ‘sensitive’ fields in the master records in the system. (All such sensitive fields are defined in the Table T055F when customizing the application. And these fields are defined per Company Code and per Client.) Consider, for example, a sensitive field such as ‘payment block’ in a vendor master record. When a user changes this field’s content, the system requires another user (usually of higher authority) to approve this change and an audit trail is maintained of all such changes. Unless ‘ the change is approved, in this example, this particular master is blocked by the system for considering the same in the next ‘payment run.’
Open table as spreadsheet Activity Customer Vendor
Display changes (accounting area) FD04 FK04
Display changes (centrally) XD04 XK04
Confirm changes, individually FD08 FK08
Confirm changes, in a list FD09 FK09
Q.12.WHAT IS A ‘BANK DIRECTOR’ IN SAP?
SAP stores the master data (details such as bank key, bank name, bank country, bank address, and so on) relating to the banks in the ‘Bank Directory’ (Table: BNKA). Remember, the ‘bank masters’ are not created in the application but in the implementation side using the IMG. (Of course, you can also create the bank master in the application side in FI-TR and not in FI-GL or AP or AR.) However, if you are in the process of creating a master record for a vendor or a customer and you enter some bank details, which the system does not find in the ‘Bank Directory,’ then the system automatically brings in the relevant screens for you to maintain and update the bank details in the bank directory.
You may create the bank directory in two ways:
1. Manually (IMG path: Financial Accounting>Bank Accounting>Bank Accounts>Define ‘House Banks’)
2. Automatically (by importing the bank details using a special program)
Q.13.WHAT IS A ‘HOUSE BANK’?
A ‘House Bank’ is the bank (or financial institution) in which the Company Code in question keeps its money and does the transactions from. A house bank in SAP is identified by a 5 character alphanumeric code. You can have any number of house banks for your Company Code, and the details of all these house banks are available in the ‘bank directory.’
Each ‘house bank’ in the system is associated with a country key (U.S., IN, etc.) representing the country where the bank is located, and a unique country specific code called a ‘bank key.’ The system makes use of both the ‘country key’ and the ‘bank key’ to identify a ‘house bank.’
For each of the ‘house banks,’ you can maintain more than one bank account; each such account is identified by an account ID; i.e., Chek1, Check2, Pybl1, etc. Here, ‘Chek1’ may denote Checking account 1, ‘Pybl1’ may denote Payables account 1, and so on. You may name the accounts in a way that it is easily comprehensible. The ‘Account ID’ is referenced in the customer/vendor master record and it is used in the payment program by the system.
For each ‘account ID’ you will also specify the bank account number (maximum length of this identifier is 18 characters). You may name this in such a way that it is also easily comprehensible.
For each ‘bank account number’ so defined in the ‘house bank,’ you need to create a GL account master record, and while doing so you will incorporate the ‘house bank id’ and the ‘account id’ in that particular GL master record.
Q.14. EXPLAIN A ‘SALES CYCLE’ IN SAP?
A ‘Sales Cycle’ comprises all activities including quotation/inquiry, sales order, delivery, billing, and collection.
The following are the various processes within SAP that complete a sales cycle:
Typically, the following are the documents created during a sales cycle:
Q.15. EXPLAIN ‘AUTOMATIC ACCOUNT ASSIGNMENT’ IN SD?
During goods issue in the sales cycle, the system is usually configured to update the relevant GL accounts automatically and to create the relevant accounting documents. This customization in IMG is also called material account assignment and is achieved through a number of steps as detailed below:
1. Determine ‘valuation level’ (Company Code or plant).
2. Activate ‘valuation grouping code’ and link it with the ‘chart of accounts’ for each
3. Link ‘valuation class’ with ‘material type’ (FERT, HAWA, HALB, etc.) with the ‘account category reference’ (combination of valuation classes).
4. Maintain ‘account modification codes’ for ‘movement types.’
5. Link ‘account modification codes’ with ‘process keys’ (transaction/event keys).
6. Maintain a GL account for a given combination of ‘chart of accounts’+ ‘valuation grouping code ‘+’ account modification code ‘+’ valuation classes.’
The process of Automatic Account Determination is as follows:
1. Depending on the ‘plant’ entered during goods issue (GI), the ‘Company Code’ is
determined by the system which in turn determines the relevant ‘Chart of Accounts.’
2. The plant thus entered in goods issue determines the ‘valuation class’ and then the ‘valuation grouping code.’
3. The ‘valuation class’ is determined from the ‘material master.’
4. Since the ‘account modification code’ is assigned to a ‘process key’ which is already linked to a ‘movement type,’ the ‘transaction key’ (DIF, GBB, AUM, BSX, etc.) determines the ‘GL account’ as posting transactions are predefined for each ‘movement type’ in ‘inventory management.’
Q.16. OUTLINE ‘CREDIT MANAGEMENT’ IN SAP?
‘Credit Management’ helps to determine credit limits of customers, aids in the creation of ‘credit check’ policies, as well as helps companies monitor and evaluate their customers. This is a cross-functional responsibility in SAP, covering both the Sales and Distribution and Financial Accounting modules. As in the case of any automated process such as dunning, payment, etc., credit management in
SAP requires certain prerequisites be defined beforehand:
1. Customer master data has been created both in SD and FI.
2. Credit control area has been defined and assigned to a Company Code.
SAP makes use of the concept ‘credit control area’ for credit management. As explained elsewhere, the credit control area is an organizational element defined to which one or more Company Codes are attached. In the case of customers defined under more than one Company Code, they may fall under different credit control areas. But note that:
A Client can have more than one credit control area, but the converse is not true: one credit control area cannot be assigned to more than one Client.
A credit control area can be assigned to more than one Company Code, but the converse is not true: one Company Code cannot be assigned to more than one credit control area.
While defining the credit limit for a customer:
You will define a maximum limit per credit control area (Example: Credit Control
Area AAAA->USD 500,000, Credit Control Area BBBB ->USD 200,000)
You will define a global maximum limit for all credit control areas put together
3. Credit data (per credit control area ‘maximum limit’ as well as the ‘total’ for all areas, in the control data screen) for the customer has been created.
4. Risk categories have been defined and assigned to customers.
5. Credit groups (document credit group) for document types have been defined.
Document credit groups combine order types and delivery types for credit control.
6. Defined, in SD, at what time (when order is received or when a delivery is made, etc.) the credit check should happen.
The credit management process starts when a sales order is entered in SD. Imagine that this results in exceeding the credit limit defined for the customer. Now:
1. The system creates three comparison totals considering
(1) open receivables,
(2) sales order values, value of goods to be delivered and the billing document value from SD,
(3) special GL transactions (e.g., ‘down payments’ and ‘bills of exchange’).
1. Based on (a) above the system throws an
(1) error message and prevents saving the order or
(2) a warning message, and the system does not prevent saving, but the order is
1. The Credit representative, using information functions (SD information system, FI
information system, credit overview, credit master list, early warning list, oldest open item, last payment, customer master, account analysis, etc.), processes this blocked order either (1) from the ‘blocked SD documents list’ or (2) the mailbox, and releases the order, if necessary.
1. Delivery is created, the billing document is generated and posted, and A/R is updated.
2. Customer pays the invoice and A/R is posted.
Q.17. WHAT IS A ‘CREDIT CHECK?
A ‘Credit Check’ is defined for any valid combination of the following:
Credit control area
Document credit group
Q.18. DIFFERENTIATE ‘STATIC CREDIT CHECK’ FROM DYNAMIC CHECK?
Under ‘Static Credit Check,’ the system calculates the credit exposure of a particular customer as the total of:
Open order (delivery not yet done)
Open delivery (value of deliveries yet to be invoiced)
Open billing documents (not transferred to accounting)
Open items (AR item not yet settled by the customer)
Customer’s credit exposure is not to exceed the established credit limit.
The ‘Dynamic Credit Check’ is split into two parts:
Static limit: Total of open items, open billing, and open delivery values.
Dynamic limit (Open Order Value): The value of all undelivered and partially delivered orders totalled and stored on a time-scale in the future (10 days, 1 week, etc.) known as a ‘horizon date.’ During the ‘dynamic credit check,’ the system will ignore all orders beyond the ‘horizon date.’ The sum total of ‘static’ and ‘dynamic’ limits should not exceed the credit limit established for the customer.
Q.19. LIST THE REPORTS IN CREDIT MANAGEMENT?
SAP provides you with the following Reports in Credit Management:
· RFDKLI10 Customers with missing Credit Data
· RFDKLI20 Re-organization of Credit Limit for Customers
· RFDKLI30 Short Overview of Credit Limit
· RFDKLI40 Overview of Credit Limit
· RFDKLI41 Credit Master Sheet
· RFDKLI42 Early Warning List (of Critical Customers)
· RFDKLI43 Master Data List
· RFDKLI50 Mass change of Credit Limit Data
· RVKRED06 Checking Blocked Credit Documents
· RVKRED08 Checking Credit Documents which reach the Credit Horizon
· RVKRED09 Checking the Credit Documents from Credit View
· RVKRED77 Re-organization of SD Credit Data