Tasks to be completed when documenting an SAP Transaction, Report or Message code.1. Title of the page = SAP Transaction code, SAP Report or SAP Message2. Add the following Labels, respectively :
3. On the left section, describe the steps. On the right section, insert respective print screens and additional guidelines, if needed (e.g. Main selections of the transaction...) |
Use transaction code:
|
Enter the transaction (FB01, F-02 or F-43) name in this field:
Complete the fields
The different field must/can be completed:
Document date | The document date is the date on which the original document was issued. |
Posting date | Date which is used when entering the document in Financial Accounting or Controlling. When entering documents, the system checks whether the posting date entered is allowed by means of the posting period permitted. The posting date can differ from both the entry date (day of entry into the system) and the document date (day of creation of the original document). |
Type | The document type classifies accounting documents. Attributes that control the entry of the document or which are themselves stored in the document are stipulated for each document type. In particular, the number range assigned to the relevant documents is determined on the basis of the document type. |
Company code | Select the company code. |
Currency/rate | Currency key for amounts in the system. Exchange rate Tax amounts are usually converted using the exchange rate defined by the tax base amounts. If you wish to enter an alternative exchange rate, or have the system default an alternative exchange rate, you make the setting here. As a result of the alternative exchange rate, the document now contains a balance in local currency, which is posted to a separate account by means of an automatically generated line item. |
Translation date | Translation date for determining the exchange rate which is to be used for translation. The exchange rates are stored in the system. You do not need to enter a date unless the date in question is not the same as the document entry date. |
Cross CC-no | Is done automatically. In cross-company code document entry, several documents are created in different company codes. A common transaction number indicates that the documents belong together logically. The transaction number can be assigned by the system or manually. The system creates the number from the document number, company code and fiscal year. |
Document number | Has to be empty. |
Reference | The reference document number can contain the document number of the customer/vendor. However it may contain a different value. The reference document number is used as a search criterion when displaying or changing documents. In correspondence, the reference document number is sometimes printed in place of the document number. |
Doc header text | The document header text contains explanations or notes which apply to the document as a whole, that is, not only for certain line items. For more information on how to fulfill this field depending on the posting to be done, please access the IOP Harmonizing Data Entered in the System. |
Trading part BA | Is not used. |
In the above menu, there is the possibility to insert various posting lines by clicking on the top of the page:
And the output is as followed. There is the possibility to change the layout, going:
Settings > Editing options > 
You can change to the layout SAP02.
You should come back to the transaction and change the layout SAP01, otherwise it will have consequences in some specific transactions (e.g. ZZF_GSBER_BREAKDOWN). I believe we are no longer using this transaction as it was replaced by ZZF_BFC_FI_FLOW_AN - BFC flow analysis! Please double check! |
Click 
and activate the new layout:
Posting key for the next Line Item
In this field, the posting key with which the next document line item should be entered is specified.
Example:
- 40 for debit
- 50 for credit
Account for the Next Line Item | Account number which is to be posted to with the next line item. |
Special G/L Indicator for the Next Line Item | Not possible for general ledger. |
Trans. type | This type is currently used only in ERP system to explain the flows/movements needed for provision and fixed assets. |
(please verify if this text below belongs to this step)
Important note: Posting Net vs. Gross Amounts
1) The most usual approach is to insert the Gross amount (net amount + tax amount) and to have the system calculate the tax. The financial document will look like this more or less: 
The Gross amount is 540, 85 (customer account) and if you deduct 20% according to tax code GL you will have the net amount of 450, 71.
2) Also usual, although transparent for most of you, are the postings using the Net amount. The financial document will look like this more or less: 
The Gross amount is 127, 34 (vendor account) but the tax calculation (tax code 8C) will be done using both 80 and 20 net amount values for account 6164000000.
FB01 transaction and in the first screen follow the menu path: Settings – Editing options.
In the screen that appears (for the first folder "Document entry") flag the option "Calculate taxes on net amount" and press the "Save" button for your changes to be effective.
After this operation, just post the document as usual, don't forget to always simulate the document and check all entries before saving.
Immediately after posting this kind of documents you should enter again on the editing options and remove the flag from the field "Calculate taxes on net amount" so your settings are replace as they were before. This is applicable to post documents manually using FB01, FB60 or other transaction. |
ZZF_POSTING FILE (please update the link) |
Add G/L account item
Follow the steps below:
1) The screen and the fields are different between the several SAP environments.
In PF1 it looks like this:
In WP1 it looks like this: 
2) Fill in the necessary information:
Amount | Enter the amount |
Tax code | The tax code represents a tax category which must be taken into consideration when making a tax return to the tax authorities. Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code. For tax-exempt or non-taxable transactions, you should use tax codes with a 0 percentage rate if the corresponding transactions are to be displayed in the tax returns. |
Business Area | Key identifying a business area. There are differences between the 3 systems (mandatory or not). For further information's see http://www.bxl.be.solvay.com/fichiers/scc/prc/ES_1030S_BUSINESS_AREA_EN.doc (update the path, give a name and link it) |
Cost Center | Key uniquely identifying a cost center. A cost center is one type of Cost Elements, which are mandatory for cost accounting. For more information about cost accounting see documentation of MB3 (update the link) |
Order |
|
Profit Center |
|
Cost Object |
|
WBS element |
|
Personnel no |
|
Sales Order |
|
Material Number/ Plant | If those information's are needed the person who asks for the posting should give the full information to SBS. |
Purchasing doc. |
|
Quantity |
|
Assignment |
|
Item Text | Contains an explanatory text on the line item. For any FI manual posting, a text explaining the operation is required in the text field. Please check that it is the case and reject the posting request otherwise. If you put "XX" the field of the previous item is taken |
Next line item | Posting key + account for next item |
Save the posting
Overview of the posting
And the end we can have an overview, click here.
Save the posting.
Enter the Barcode when needed.
The document is saved.
Check other possibilities
You can also book with reference to another document:
You can also cancel the booking if it is wrong: