Statistical vs Real Postings

During posting, only a real account assignment object can be transferred. The only exception to this rule is the account assignment to a cost center, and an additional, real account assignment object. In this case, the system always updates the cost center statistically. If you specify a real order and a cost center in the posting row, then the real posting is made for the internal order. Statistical postings are entered for the cost center and the profit center. However, If the order is only statistical, then it is posted to as such, and the cost center receives real postings. You can only assign one object type to each posting row. This means that you cannot post the same transaction row to more than one cost center or order, and so on.

Cost Center + Real Internal Order --> posting goes to the Real Internal Order

Cost Center + Statistical internal order --> posting goes to the Cost Center

Revenues can only be posted as real postings to a profitability segment, sales order, sales project, or to a real order that can have revenues. Revenue postings to the profit center are statistical, the same as for cost  postings. Revenues can also be recorded as statistical values on cost centers.

Assessment vs Distribution

Both are used for internal allocation for costs that cannot be directly associated in the manufacturing of a product or service.

Can be used for Cost Centers, Profit Centers, Segments and Functional Areas.

In Assessment, you credit the cost center using a different Cost Element while Distribution will credit the cost center with the same cost element which means that every after assessment, the originating cost object is zeroed out.

In choosing between the two, assessment is more used because there are businesses who would like to trace the origin of costs.

Example of Distribution is that if you use a Cost Center which is just really a temporary cost holder.

You use assessment if you would like to transfer but still would like to trace where it came from?

Example of Allocation:

Electric Bill

There are 4 floors with 4 different departments. We can use a simple allocation that this is divided into 4 every billing period.

Another option is that there is a weighted percentage per department, example: 50% for Department 1, 20 % for dept 2, 15% each for dept 3 and 4.

F110 How to Do Payment Reset

For International Payment Medium - Correction of EDI Status

Note 103749 - RAJABS00: Error message AU069

To correct the incorrect fixed assets, a depreciation recalculation (Transaction AS02) must first be carried out for all outstanding fiscal years. During recalculation, the error indicator is first cancelled and reset if the detected incorrect status still exists. You receive a precise error message in this case. You should then eliminate the cause using the error message.
However, it is possible that the cause for the incorrect status lies in a fiscal year that is already closed. In this case, the error indicator is not cancelled by a recalculation in the open fiscal years. This case must not actually occur - it indicates a handling or program error in the past. Also check this fixed asset with regard to past years. If you cannot detect any errors and you agree with the values in the fixed asset, you can reset the error indicator on the fixed asset by means of the repair program RACORR52 and then repeat a recalculation of the fixed asset. Year-end closing should then be possible.
The repair program either already exists in your system or you can create it according to the attached advance correction.

Electronic Bank Statement

Electronic Bank Statement mapping reference

:20 statement date

:25:account number

:28C statement number

:NS:22account owner

:60F: opening balance

:61:transaction 1

:NS:19transaction 1 booking time

:86:transaction 1 details

:61:transaction 2

:NS:19transaction 2 booking time

:86:transaction 2 details

:61:transaction 3

:NS:19transaction 3 booking time

:86:transaction 3 details

:62F:closing balance

:64:available balance

:86:account information

J2GLPLOGPAPERSFIV

Transaction code J2GLPLOGPAPERSFIV

When there are documents that are posted via IDOC that cannot be printed via J2GPFI, it is due to GL Accounts being posted are not in the customizing table that is being read by the printing program. The transaction for this table is J2GLPLOGPAPERSFIV. .

Useful SAP Asset Correction Programs

Useful SAP Asset Accounting Correction Programs

RACORR46	This report changes the current fiscal year in table ANLB. It will be changed to the last open fiscal year from table ANLC.
RACORR20	The report corrects planned asset depreciation values in closed fiscal years through copying the posted value in the planned value field.
RACORR52	The report resets the error indicator on the fixed asset for closed fiscal years during year end closing.
RACORR39	This report updated fields BLDAT (document date) and BUDAT (posting date) in table ANEK (Header Asset Accounting Document) from corresponding fields of table BKPF (Header Financial Accounting Document).
Z_UPDATE_ANLB_XNEGA	Correction report that deactivates asset error indicator