TFIN50_1 UNIT III

Documents in SAP ERP Financials solutions contain the following details: Document Header: This component contains information that applies to the entire document. Roles and Authorization. Line items: Each posted accounting document has at least two lines (for example, debit and credit) and a maximum of 999 line items. This information is specific to the line item. When you post documents using an AC interface, such as Sales Order Management, or Purchasing Management, the AC interface creates items in the accounting document that are identical in almost all of the fields.

Each posted accounting document has at least two lines (for example, debit and credit) and a maximum of 9999 line items. True. False.

The SAP ERP application is based on the document principle, which implies the following course of action: A document is saved for every business transaction posting. The document remains as a complete unit in the system until it is archived. Posting Control. Every document is uniquely identified by Document No, Company Code & Fiscal year.

Every document is uniquely identified by the following fields: Document Number. Fiscal year Variant. Company Code. Fiscal Year. Company.

There are two important control keys: Document type for the document header. Posting Variant. Fiscal Year. Posting key for the line items.

The SAP ERP application generates at least one document for every business transaction. True. False.

Each document is assigned a unique document number. During internal number assignment, the document number is assigned by the SAP ERP application. During external number assignment, the user assigns the document number in the Document Number field. False. True.

A business transaction can create one or more documents. For example, when goods arrive from a vendor, the SAP ERP application creates a material document to record data that is important for inventory management. An accounting document is created to record financially relevant information, such as accounts data and amounts related to the general ledger. True. False.

In the SAP ERP application, documents are generated for various business transactions without an accounting document being generated at the same time because accounting is not affected by document generation. An example of this is the generation of a purchase order in Materials Management, which does not result in the generation of an accounting document. False. True.

Document types are defined at the company level, they are not valid for all company codes. The SAP ERP application is delivered with document types that can not be changed or copied. True. False.

To transfer billing documents from the SAP ERP billing application, you need one of the following document types: RV: The default document type for Sales Order Management billing documents (customer invoices). ZP: The default document type for GL Posting in FI. RE: The default document type for Materials Management billing documents (vendor invoices). RT: The default document type for automatic payment.

The payment program uses the document type ZP for most of its automatic postings. True. False.

Document type AB allows postings to all account types. False. True.

Document type DZ allows you to post to customer (D) and general ledger accounts (S) only. False. True.

The following types of number assignments are possible in the SAP ERP application: Internal numbering. Alphanumeric Range. External number assignment.

In Internal Number Assignment , the SAP ERP application saves the last document number taken from the number range in the Current Number field. The application then assigns the number following the current number as the next document number. False. True.

In External Number Assignment, the user enters the number of the original document or the number is automatically transferred from another system. Since the numbers are not assigned in sequence, the SAP ERP application cannot store a current number.The numbering can be alphanumeric. True. False.

The document number range defines the range of numbers that is assigned to document numbers. These number ranges can be overlapped. False. True.

The following options are available for defining the document range: Continuous : At the beginning of a new fiscal year, the SAP ERP application continues to use the number after the current number as the next number. The application does not restart at the first number of the number range. Company : A continuous number series for a company irrespective of fiscal year. For every Fiscal Year : At the beginning of a new fiscal year, the SAP ERP application starts with the first number of the number range. This ensures that the number range is sufficient.

One number range can not be assigned to several document types. You can not copy the intervals of document number ranges from one company code to another or copy intervals from one fiscal year to another. True. False.

Document types define the following elements: Number range for Document Type. Reverse Document Type. Account Types allowed for posting. Control Data. Required during document entry.

"Control Data" element of Document Type consists of the following parameters: Net Document Type Field - Valid for document types used for vendor invoices (This indicator reduces the total amount due by the cash discount amount specified by the payment terms on the invoices). Customer/Vendor Check. Negative Posting Permitted. Inter Company Postings. Enter Trading Partner.

Similar to document types, posting keys are also defined at client level. True. False.

Posting Key has control functions within the Line items. In controls : The Account Type to which the Line Item can be posted to. If the Line Item is posted as Debit or Credit. The Field Status of additional details. Posting Varaint.

The following default values for posting keys are provided in Customizing for the SAP ERP application: For GL account posting: Debit is posting key 40, credit is posting key 50. For customer invoices: Debit is posting key 01, credit is posting key 11. For Vendor invoices: Debit is posting key 21, credit is posting key 31. For Purchase Orders: Debit is posting key 51, credit is posting key 61.

Various field status groups are available in the standard SAP ERP application. It is recommended that you copy the standard field status groups and modify them as necessary. True. False.

For each group of general ledger accounts (such as cash accounts and expense accounts) you do not need to define the status of every document entry field. True. False.

When you enter the documents for general ledger accounts, you must decide if the text field is required, optional, or hidden. False. True.

When you enter the documents for general ledger accounts, you need to decide if the cost center field is required, optional, or hidden. True. False.

You assign field status groups to the respective general ledger accounts in the general ledger accounts master records.The field status groups are summarized in one field status variant. True. False.

The field status variant is assigned to your company code(s). You cannot make a posting until the field status variant is complete. Typically, you assign the same field status variant to all your company codes so that the same field status information applies across the company codes. False. True.

If a document is posted to a sub ledger account, the field status group of the sub ledger account will be used. True. False.

SAP recommends that you use the standard posting keys delivered. If you change them or define new posting keys, any tables containing a reference to these keys must also be updated. False. True.

Posting keys for assets and materials may only be used if the corresponding SAP components are configured. True. False.

You can change the field status definitions of posting keys and the field status group to make the field status: Transaction dependent. Client dependent. Company dependent. Account-dependent.

Since sub ledger accounts do not have a field status group, postings are differentiated by means of different posting keys. For this reason, there are numerous posting keys for sub ledger accounts. False. True.

Postings to general ledger accounts are differentiated by means of different field status groups. As a result, only two posting keys, 40 and 50, are required for general ledger account postings. True. False.

Posting periods are defined in the fiscal year variant.To prevent documents from being posted to an incorrect posting period, you can close certain posting periods. True. False.

Usually the current posting period is open and all other periods are closed. At the end of a period, this period is closed and the next period is opened. You open a posting period by entering a range in the posting period variant that encompasses this period. You can have as many posting periods open as desired. False. True.

During fiscal year closing, you can not open special periods for closing postings. False. True.

Several company codes can use the same posting period variant. Thereby, the posting periods are opened and closed simultaneously for all company codes to which the posting period variant is assigned (Variant Principle). This simplifies posting period maintenance and enables a group-wide posting closing with minimal requirement of manpower. False. True.

Posting periods can be handled differently for different account types. For a certain posting period, postings to customer accounts may be permitted while postings vendor accounts may be restricted. False. True.

At the line item level, the SAP ERP application checks the account type of the posting key to ensure that the period is open for the assigned account type. False. True.

During closing, two period intervals must be open at the same time. Therefore, you can enter two period intervals in the posting period table.You can assign an authorization group to the first period interval. Users belonging to this authorization group have the permission to post in this interval. False. True.

When you want special periods with authorization check, use the first range for these periods. Authorize only those accountants, who are involved in the closing, to post in the special periods. False. True.

When entering a document, you enter the posting date. The SAP ERP application automatically determines the posting period and the fiscal year based on the posting date entered. False. True.

The SAP ERP application determines the posting period and updates the transaction figures for each posting period. If you display the balance of an account, the transactions figures for the special periods are displayed. True. False.

Define the maximum tolerance for payment differences to determine the following aspects during a transaction posting and processing clearing transactions: What is the maximum document amount the employee is authorized to post? (Amount per document - A total of all the debit line items or credit line items in a document.). What is the maximum amount the employee can enter as a line item in a customer or vendor account? (Amount per open item.). What is the maximum cash discount percentage the employee can grant in a line item? (Cash discount per line item.). What is the maximum acceptable tolerance for payment differences (over payment or under payment) for the employee? (Revenue – Over payment, Expense – Under payment.). What is the maximum acceptable tolerance for a Company.

The maximum amounts are defined per company code in Tolerance Group. This is also where the processing of payment difference is controlled. False. True.

If you do not assign users to any special tolerance group, then the entries in the standard tolerance group are valid for them. False. True.

You can create as many tolerance groups as you need. Every user can be explicitly assigned to a tolerance group. The blank tolerance group usually contains values that apply to most employees. True. False.

For employees, who have especially high or low limits, you need to create a special tolerance group. You can then assign the special group to their user logon IDs. True. False.

The SAP Financial Accounting component uses one posting transaction for the following types of postings: General ledger account postings. Customer invoice postings. Customer credit memo postings. Vendor invoice postings. Vendor credit memo postings.

Once the balance is zero, you can select one of the following tasks to complete the document entry transaction: Hold. Park. Delete. Post.

You can use the Tree pushbutton to access and select the following templates: Screen Variants. Account assignment templates. Posted Documents. Held Documents.

You can enter the following fields in the document header: Invoice date. Tolerance Group. Posting date. Text.

Using the ENJOY Posting Screen: The important input fields are in the foreground on the initial tab and the fields used less frequently are on the subsequent tabs. False. True.