Fiar2 130611232511-phpapp02 (1)

Editor's Notes

• #2: www.indiantaxhome.com
• #8: A Ltd has decided to maintain Master Data centrally.
• #13: A business partner is a person or an organization with whom you have a business relationship. The system automatically creates one ship-to party, bill-to party, and payer when you create a new sold-to party record. The partner function describes the relationship you have with that business partner. For example, the business partner can be a: Sold-to party who places an order. Ship-to party who receives the order. Bill-to party is simply the address on the invoice. Payer who is responsible for paying the invoice and records this payment in their books. Additional partner functions and business partners can be added to the customer master records. You can define alternative ship-to parties, bill-to parties and payers records for a sold-to party. This allows, for example, one sold-to party to place an order for more than one ship-to location yet have another location receive the invoice. A customer master record must be created for an alternative partner using the correct account group. For example, an alternative ship to party is created using account group 0002 (Ship-to Party). A customer master record must be created for an alternative partner using the correct account group. For example, an alternative ship to party is created using account group 0002 (Ship-to Party).
• #14: To create a master record, you have to specify an account group. The account group cannot be changed after you created the master record. The account group determines: How the account is numbered. A number interval from which the account number is chosen, Which fields are displayed when you create or maintain Customer master data and whether the entry is optional or required (field status) when you enter or change Customer master data. E.g. when setting up an Employee as a Customer, purchasing data is not required. Whether the account is a one-time account.
• #15: If internal numbering is assigned to an account group, then SAP R/3 will automatically assign an internal number within the defined interval. Most customer master records created in SAP R/3 will be created using account group 0001 (Sold-to Party) If external numbering is assigned, then the user must enter a number within the defined interval. The last number issued (internally or externally) is displayed by clicking on the Account group Overview button
• #17: One-time Customers are used for Customers with whom we rarely or only once perform business with. In contrast to other Customer master records, a one-time Customer master record is used for several Customers, so that you do not have to create a large number of Customer master records that are used only once. As a result, you do not store any Customer-specific data in the Customer master record for one-time accounts. When you post an invoice to a one-time account, SAP R\3 automatically goes to a master data screen. In this screen, you enter the specific master data for the Customer, e.g. name, address, which is stored separately in the document. You create, display, block, and delete one-time Customer master records in the same way as all other Customer master records. The sort key used for One-Time Customers is 023
• #18: Depending on the reasons for blocking a customer master record, you can select all sales areas or only a specific sales area. If a sales area is not entered in the initial screen, then SAP R/3 assumes that the master record is to be blocked for all sales areas. A customer master record can be blocked for: sales order processing delivery processing billing processing
• #19: Customer master records can be flagged for deletion: If there is a duplication of records for a sales organization of for the company as a whole Redundancy of use Once the records have been flagged for deletion, then the relevant person within the sales organizations affected, must be notified.
• #21: Customer master records that are no longer used or have been created in duplication should be archived by flagging them for deletion. Archived records are extracted from the SAP database, deleted and placed in a file and then transferred to an archive system. To archive a record, the following prerequisites must be met: The account cannot contain any transaction figures in the system Transaction figures from prior years that have not been archived will prevent the system from deleting the account master record The account must be marked for deletion in its master record Block an account for posting before you mark it for deletion. The only effect this deletion indicator has is to cause a warning to be issued every time someone tries try to post to this account. You can reset a deletion flag at any time as long as the master record has not been physically deleted from the system.
• #23: Each credit control area carries out credit control for one or more company codes and, to enable it to do this, you must assign the respective credit control area to the company codes
• #24: Credit control areas are defined at regional level. A central credit control limit will be defined at CHQ The individual limits for each credit control area may not exceed the total at group level e.g. $1,000,000 The maximum individual limit is defined at group level e.g. $450,000 Some companies e.g Exon Mobil can be managed at the group level. The credit limits will be defined at group and individual credit control area
• #26: A customer’s credit exposure is the total combined value of the following documents: Open orders (Sales orders not yet delivered) Open deliveries (Deliveries not yet invoiced) Open billing documents (Not yet posted to Financial Accounting) Open items (accounts receivable) (Forwarded to FI, but not yet cleared)
• #32: If the invoice is blocked, the payment terms will go as usual. No effect on payment terms.
• #35: Except of “normal” special GL transactions, in the system there may be defined “noted items”. If the special GL transaction is defined as “noted item” than postings with this indicator do not lead to an update of the transaction figures. Typical example is “Down Payment Request”: a posting done with this indicator stores only an information in the system that is used later to post automatically a down payment.
• #37: The billing document is the final process that is performed in the Sales cycle in the sales and distribution module. The creation of a billing document has the following effects: Document flow and document statuses are updated Documents are automatically created in Financial Accounting and Controlling that update the general ledger account for revenue The Sales Information System is updated Accounts receivable is increased The customers credit record / limit is decreased Controlling elements such as profitability analysis and profit centre accounting are update
• #38: In display mode, no changes can be made to a billing document. When a billing document is created, the system automatically creates all the relevant accounting documents for: General ledger Profit center Profitability Analysis Cost Accounting Accounting
• #39: Credit and debit memo requests are created by referencing the invoice. The system transfer the correct amount from the preceding document. Enter an order reason (reason for adjustment) for evaluation purposes. The credit memo request is automaticall blocked for billing, whereas the debit memo request does not contain a billing block. Once approved, the billing block is removed and a credit note is created. The credit memo request has a credit check assigned to it, which will block the credit memo request for further processing if the customer has credit problems. During posting of the billing documents (credit memo or debit memo), accounting documents are created which posts the correct amounts against the customer's A/R account.
• #41: You can enter an invoice (or a credit memo) without posting it and simply "park" it. You enter the data in the system and save it in a document. The system does not, however, make any postings. A parked document can be changed as often as you like. When data is added or changed, the changes are noted by the system. When no further changes are required, you can post the parked document. Only then does the system carry out the normal account movements and make the necessary updates. The preliminary posting function can be of great advantage if: You are interrupted when entering an invoice. You can park the document and continue processing it later on. This saves you time having to enter the data twice. You wish to clear up some questions before you post an invoice. You can park the document and continue processing it later on. You wish to split the invoice verification process. One employee can, for example, park an invoice without checking it, while another carries out the actual checks and posts the document after making any necessary corrections.
• #43: If you know the parked document’s details, enter the document number, company code and fiscal year on the Initial screen. Alternatively, click the List button, which takes you to a selection screen. On the Document List screen, enter the selection criteria, then click the Execute button
• #45: When you post a invoice in a foreign currency, you enter the appropriate foreign currency key in place of the local currency key, USD that is defaulted by the SAP R/3. The system stores the amount in both local currency and foreign currency in each line item and checks whether the currency key has been defined and is therefore permitted. The amount is entered in only one currency, as the system translates this amount into the other currency automatically. Normally you will use the exchange rate defined in the exchange rate table. If the exchange rate on the invoice is different than default daily rate the currency exchange rate table can be overridden by entering an exchange rate manually (in the document header), or entering the local/foreign currency amount at line item level.
• #49: To process checks manually: 1. Enter checks. Remember to include clearing information: in A Ltd as a clearing information was chosen Customer short name and an invoice number (from SD Module). Create a batch input session or choose direct processing. 2. Run the sub-ledger session. Postings to bank clearing accounts (incoming checks) and to sub-ledger accounting (customer clearing). 3. Print the check deposit list and give it to the bank, along with the checks. 4. Process the bank postings.
• #50: This is the start variant and determines which fields are displayed when you are actually entering checks. You can change the account assignment variant at any time during processing. If you select internal bank determination, the system identifies the bank using the internal name instead of the bank number and external account number. You can use either, according to what is usual in your company. The match code ID D and the contents of the customer match code field on the next screen make up the match code of the customer account the system searches for (account determination for payment settlement). The further processing type determines whether the postings in the batch input session are made online or in the background. Transfer value date: The value date from the check entry is copied into the postings. Specify a form ID if you want to use a form that differs from the standard form for the check deposit list. For A Group we use start variant Z0001
• #51: The postings can be done immediately or processed in the batch input sessions. The Post option generates postings immediately or the batch input sessions, including postings for sub-ledger accounts. You can process the sessions individually or together, online or in the background (batch). The log displays the processing statistics and any incorrect transactions. Incorrect transactions, which were not processed due to inadequate clearing information, must be post processed:  If you are using batch input sessions, you must run these again online.  If you are using immediate postings, you need to use a transaction FEBA to clear the open items.
• #56: Open items are incomplete transactions, such as an invoice for which goods or services have not yet been received. In order for an open item transaction to be considered complete, the transaction must be cleared. A transaction is considered cleared when an offset value is posted to it, so that the resulting balance of the items is zero. In the above example: Two invoices are posted to the Customer account. These invoices are regarded as the open items because at this point the corresponding payment has not been received. The payment is received and the invoices are set off against it. The transaction is now cleared and the resulting balance is zero.
• #57: If you select a Customer who is also a Vendor when processing a clearing transaction, such as an incoming/outgoing payment or account maintenance, the system will also select the open customer items automatically, provided that: The vendor number was entered in the Customer master record. The “Clearing with Vendor / Customer” indicator has been set in both master records. When posting payments to these Customers, the system will display the vendor open items in addition to the Customer open items. You must have authorisation to post in both Accounts Receivable and Accounts receivable transactions, in order to clear vendors and Customers against each other.
• #59: “Nobody’s perfect”. As a result, the document created may contain incorrect information.  The system provides a function to reverse G/L, A/R and A/P documents both individually or in mass process.  A document may be reversed either by:  entering a standard reversal posting or  entering a negative posting. To reverse a document user must enter the reason code.   Documents with cleared items cannot be reversed. The clearing document must first be reset. To enable negative postings, you need to set the relevant indicators: for the company code and a relevant document type.
• #69: Additionally, SAP offers a number of reports that meet country-specific requirements. There is a list of country-specific reports for completing VAT tax forms and reports for additional legal reporting requirements
• #71: The accounts receivable information system enables you to access different evaluations already defined in the system. Because these evaluations are stored in an information database, system response times are accelerated. The results stored in the information database are based on the last evaluation carried out. You can update the evaluations at regular intervals. In customizing, there are defined various parameters for selecting and summarizing evaluation data according to your own needs.