Field Definitions
Field Name |
R/O/C |
Description |
R |
Independent accounting unit; in most cases is a legal entity. You can prepare a balance sheet and income statement for each company code. Several company codes can be set up to manage the accounts of independent companies simultaneously. Example: 1051 |
|
R |
First posting date for recurring entry. Date on which the entry should first be run. Example: 08/01/2005 |
|
R |
Used for setting up a recurring entry to determine the ending run date. Example: 01/01/2006 |
|
R |
Key that identifies to which group of documents this document will be assigned. Documents of the same type contain common information which is relevant to posting and update of the value fields in the data base. Example: SA |
|
R |
The rate of the currency as updated in the currency table. Example: USD |
|
O |
Allows for further clarification of an entry by referencing to other sources of information, either internal or external to SAP. Any SAP-posted document number can be used as a "reference" when entering a new document.
Example: Test for Recurring posting |
|
O |
Text field that will apply to entire document, as opposed to the line items. Example: Test for Recurring posting |
|
R |
Two-digit numerical key that controls how line items are posted. Example: 40 |
|
R |
Unique numeric identifier that is used in general ledger to identify and track natural expense items. Also used in subledgers such as A/R and A/P to identify customers and vendors. Example: 600030 |
|
C |
Field allows additional level of posting detail for customer, vendor, and asset related documents. Field is active when the appropriate posting key is selected.
Example: A |
|
R |
Interval, in months, between each run of a recurring entry. |
|
C |
Abbreviation for transaction type. The transaction type in Asset Accounting classifies the business transaction. The transaction type controls various system activities when business transactions are posted. Transaction type is defined at the line item
Example: 100 |