FI QADB to collect data from the client

Question

Hi,
Can anybody send me FI QADB to collect data from client?

Answer 1

QADB is old.Now with solution manager you need to take the data using CI template.
You need to discuss the processess that you are configuring along with the org structures and also need to explain in detail about the features.
A sample CI templat is given for your refernce.
*Requirements/Expectations *
XXXX has to receive during the course of their business, payments from various parties like
u2022     Customers
u2022     Against sale of used assets
For the goods or services availed supplied/made to them.
These payments need to be mapped in SAP system identifying against a customer document.
*General explanations  *
Describes in as much detail as possible how this particular business scenario or process will be used in your business. Key business processes should have considerable detail in this section.
*Explanation of functions and events *
Payment is received against an invoice. Accounts receivable makes an entry and sends the same to cashier. After accounting the payment, the balance in the customer account open item is cleared and the balance outstanding is reduced.
Note: System doesnu2019t propose the invoice to which it should be set off. It proposes all invoices that are due. Payment to a particular invoice should be made on manual judgment.
At the time of document entry, the appropriate Invoice needs to be chosen.
*Special organizational considerations *
SAP gives 3 types of clearing.
Post with clearing, Post and then clear at a later date, Automatic Clearing.
Explanation of Post with clearing:
While at the time of receiving a payment, the user knows that this payment need to be adjusted against a specific invoice and adjusts the same and posts this is called post with clearing.
The entry will be
Cash/Bank account                                        Dr
Customer Account                                        Cr
This will set the open item status to u201CClearedu201D
Explanation of Post and then clear:
While at the time of making a payment, the user doesnu2019t know against which invoice this payment need to be adjusted, and there exists some Debit/Credit notes of customers he simply posts without clearing the Open item of customer.
Later accounts receivable department identifies and knocks of these adjustments against a vendor Invoice, this is called post and clear.
The entry will be at the time of posting
Cash/Bank account                                        Dr
Customer Account                                        Cr
This will not set the open item status to u201CClearedu201D
The entry at the time of clearing
No entry is passed except the status of the open item to u201CCleared.
Automatic Clearing:
This is an extension of Post and clear. Here instead of selecting manually user instructs the system to clear for a specific range of customer account on predefined user criteria.
The entry at the time of clearing
No entry is passed except the status of the open item to u201CCleared.
Clearing is having three Concepts.
1)     Standard Clearing: One to one payment against a Customer document.
2)     Partial Clearing: Part payment against a Customer document.
3)     Residual Clearing: You make a part payment, and select the residual clearing method, the system clears of the original Customer document and generates a separate customer document, with the number that of the customer payment document type.
Business Model
*Changes to existing organization *
As per the proposed organizational structure this process will remain constant for the above discussed scenarios.
Due to the new processes of u201CVendor Paymentu201D against an Invoice, all payments to vendors, Employees, are tracked against a Posted Invoice.
If the open Items are not cleared on a regular basis, the system performance may come down.
As a best practice, business need to clear these u201CPaymentsu201D against the invoice so as to make less number of open items failing which the system performance may drop.
As per the understanding of the current business process, XXXX is new to the concepts of Open Item management, Post with Clearing, Automatic Clearing. Adoption and understanding of these processes may take some time.
*Description of improvements *
Payment against an Invoice or Posted document in SAP is an improvement to the process. Usage of u201CAutomatic Payment Programu201D is recommended with identification of vendors against the payment terms which will reduce the process load.
*Description of functional deficits *
None are apparent at this time.
Approaches to covering functional deficits
None.
*Notes on further improvements *
As per the current practice though there exists payment terms, they are not followed as such in practice. Business user wants the process as manual payment only till they stream line transactions. Usage of Automatic Payment Program will be taken up in the next phase.
*System configuration considerations *
F-28, FF67,
File Conversion Considerations
All Customer payments need to be identified against Company Code and Per Profit Center.
Interface Considerations
None
Reporting Considerations
FBL5N     :     
Customer Aging analysis.
Authorization and user roles
Authorizations for F-28, FF67 transaction codes need to be identified based on the user duties.
This is one process. Like this you need to create for each and every one.
Reward if useful
Sarma