Transferring Stocks/Balances

Whereas the master data and transaction data have been corrected in the meantime, the balance sheet items in General Ledger Accounting still need to be corrected. To correct the relevant postings, you need to perform the reorganization activity Transfer Posting.

The transfer posting is made in all ledgers containing profit centers that are included in the reorganization.

Note Note

The following details apply in the case of all object types apart from fixed assets. For more information about fixed assets, see Reorganization of Fixed Assets.

End of the note.

Balances are only transferred in General Ledger Accounting. All other application components (such as Materials Management or subledgers) are not affected.

With the balance transfer, the system transfers the balances (such as material stocks and receivables balances) in aggregated form from the old account assignment to the new account assignment.

The transfer of balances is the last reorganization activity.

Transfer Posting Documents

Each transfer posting document (apart from the transfer posting documents from Asset Accounting) has the following details in the document header:

As document header text: The reorganization plan and the object type (using the following format: REORG <Plan-10stellig> / <Objektart>, such as REORG MYPLAN01 / MAT)
As reference key: The object type and the reorganization plan
As reference transaction: BKPFR

With the transfer posting, the standard posting keys (debit/credit) for transaction key “SAK” (G/L account posting) are applied in accordance with table T030B. With the standard settings, key 40 is used for debit postings and key 50 is used for credit postings.

For each company code and ledger, separate documents are posted. This means that balances that need to be corrected in different company codes or ledgers are transferred in separate documents. If, however, the values need to be corrected in the same way in all ledgers, a document is posted with the ledger group “space”.

Within a transfer posting document, balances that were posted to the same G/L accounts, the same profit centers, and in the same currency are generally summarized in one line item. When the following fields contain different values, separate line items are created:

Affiliated companies (field name VBUND)
Transaction type (field name RMVCT)
Fields that were added to customer include CI_FAGL_R_MAP_CUST

It may be specified in the implementation of the object types that specific fields are posted in unchanged form. In such cases, the following applies for the affected fields: The segment is not derived again. In this way, the transaction type is not taken from Customizing, and the partner fields are not swapped around (see the section “Preparations for Consolidation” below). In such cases, the corresponding fields in the object list under Transfer Posting are filled. Otherwise, as applies generally, the corresponding field remains empty there, as when the field is derived during the posting, for example.

Preparations for Consolidation

Provided that the object to be transferred does not specify that partner account assignments (partner profit center and partner segment) remain the same, the posting for the line item that decreases the balance uses the old account assignment and the new partner account assignment, whereas the posting for the line item that increases the balance uses the new account assignment and the old partner account assignment.

Example Example

The balance on profit center PCA is transferred to profit center PCB.

Amount	Currency	Profit Center	Partner Profit Center
40–	EUR	PCA	PCB
40	EUR	PCB	PCA

End of the example.

The system retains the partner account assignments for the object types Receivables and Payables. For more information, see Transferring Receivables and Payables.

Prerequisites

Before you can transfer the balances, the following prerequisites must be met:

You have performed the reassignment.
You need a reorganization document type for the transfer posting.
For more information, see Prerequisites and Customizing Settings for the Reorganization.
We recommend defining separate consolidation transaction types so that the reorganization transfer postings can be displayed separately in summary reports. In Customizing for the Reorganization, you have specified which consolidation transaction types the system uses for reorganization transfer postings for incoming and outgoing stock (for example, for transferring material stocks).
The system only uses the consolidation transaction types specified there if the object type does not impose a transaction type when the system determines the stock to be transferred.

For more information, see Prerequisites and Customizing Settings for the Reorganization.
The balances to be transferred are determined for each ledger. When transferring the balances, the system makes the posting using the ledger group of the same name. The ledger group of the same name must exist and must contain the ledger of the same name exclusively (that it, the ledger group must not contain any other ledger).

Note
If you want to make postings to a ledger group that contains more than one ledger, you can override the corresponding error message (FAGL_REORGANIZATION 072) by deploying it as a warning message. The system then makes postings to all ledgers of the ledger group. For this reason, you need to ensure that the balances in all affected ledgers actually need to be corrected.

End of the note.
Balances in ledgers to which postings cannot be made directly (such as day ledgers or week ledgers) cannot be corrected unless postings to the ledger are made using a ledger group for which the ledger of the same name is also corrected.

Note
In such cases, you need to deploy the error message FAGL_REORGANIZATION 072 as a warning message (see above).

Example: Ledger T1 is a day ledger; consequently, postings cannot be made directly to this ledger. Ledger L1 contains balances that need to be corrected. Ledger group L1 contains ledgers L1 and T1.

If message FAGL_REORGANIZATION 072 is issued as a warning message only, postings are made to ledger group L1, and the balances in ledgers L1 and T1 are corrected.

End of the note.
By default, the posting date is the reorganization date. Consequently, the reorganization period in Financial Accounting relating to the reorganization date must be open.
Some object types specify the period in which the balances need to be corrected.
If a balance needs to be corrected in all ledgers, the system applies as the posting date the first day of the period of the leading ledger (whereby the posting date never falls before the reorganization date).

If a balance needs to be corrected in only one specific ledger group, the system applies as posting date the first day of the period of the representative ledger of that ledger group. Here too, the posting date never falls before the reorganization date.
The posting date for the transfer posting is always the first day of one of the periods for the leading ledger (or the representative ledger). Other ledgers should use the same period in the fiscal year variants.
If, however, the fiscal year variants of the other ledgers have a period start that differs from the period start of the leading ledger or the representative ledger, the transfer posting in such ledgers might not be made to the correct period in certain circumstances, thereby creating distorted data.

Example
The reorganization date is the first day of the period of the leading ledger: 2010-04-01. Another ledger has a different fiscal year variant: Period 3 extends from 2010-03-05 through 2010-04-05. The reassignment is performed on 2010-04-10.

All balances that arose using the old account assignment up until this date are transferred in the step Transfer Posting on 2010-04-01. In this way, the transfer posting is made in period 4 for the leading ledger but in period 3 for the other ledger. Balances that arose between 2010-04-06 and the date of the reassignment (2010-04-10) but actually arose in period 4 are nevertheless transferred in period 3.

End of the example.
If you use customer fields, you can also fill them by means of transfer postings during the reorganization.
For this, you need to enter the fields in the customer include CI_FAGL_R_MAP_CUST.
- If the added field uses an SAP standard account assignment, the field is filled automatically by the system wherever possible.
- If the added field uses an account assignment defined by the customer, you have to fill the field in the BAdI implementation of the respective object types.
Example
You have added the fields ZZ_WERKS and ZZ_HUGO in the coding block. For this, you need to enter the fields in the customer include CI_FAGL_R_MAP_CUST. For the transfer of material stocks, the ZZ_WERKS field is filled automatically with the value from the WERKS field because an SAP standard account assignment is used. However, you have to fill the ZZ_HUGO field yourself in the BAdI implementation of the object type because this field uses a customer-defined account assignment.

End of the example.

Procedure

As reorganization manager, you proceed as follows:

Call the reorganization plan in the reorganization plan overview.
On the Object Lists tab page, navigate to the line for the desired object type (such as material) in the Transfer Posting area.
If you have large volumes of data, proceed as follows:

If the object type has dependent object types, expand the entry for the object type in the hierarchy display. For each dependent object type and for the first-level object type, proceed as follows:
1. Select the line for the desired object type and choose the Transfer pushbutton.
  Specify a time for the transfer.
2. If the balances to be transferred have not already been determined, the system determines them. (For some object types, the balances to be transferred are already determined by the system during the reassignment).
  When a balance has been determined successfully for an object, the system sets the status to Balance determination successful.
3. The system makes the transfer posting.
4. When an object has been transferred successfully, the system sets the status of the object to Reorganized Successfully.
You can display the result of the transfer posting for each object list by opening the object list and checking the balances determined on the Transfer Posting tab page. To check the transfer posting documents individually, you can navigate from the document number to the document display.

Result

The system outputs a list showing for each object the objects transferred or to be transferred and a link to the document with which the relevant balance was transferred (jump to document display).

The log contains error messages (as in the case of the preceding steps).

Once all object lists that needed to be generated have been generated, reassigned, and transferred, you can close the reorganization plan.