Ansicht
Dokumentation

FAGL_R_PREREQUISITES - Prerequisites for a Reorganization

FAGL_R_PREREQUISITES - Prerequisites for a Reorganization

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

Before you can perform a reorganization and/or reassignment , the following prerequisites need to be fulfilled:

I. System Prerequisites
II. Organizational Prerequisites
III. Settings in Customizing for the Reorganization

I. System Prerequisites

Specific System Prerequisites for a Profit Center Reorganization

III.
  • The system transfers balances as follows: In cases requiring a balance to be corrected in a specific ledger, at least one document is created for each ledger. The system then makes postings using the ledger group with the same name. The ledger group of the same name must exist and must contain the ledger of the same name exclusively (that is, 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 message FAGL_REORGANIZATION 072 by deploying it as a warning message, not an error message. In this way, the postings are made to all ledgers in the ledger group. However, you must first ensure that the balances in all affected ledgers actually need to be corrected.
This setting may be useful in cases where you do not want to correct balances directly in ledgers (such as day ledgers or week ledgers) to which you usually make postings by means of the ledger group during valuations.
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 the above-mentioned message is issued as a warning message only, postings are made to ledger group L1, and the balances in ledgers L1 and T1 are corrected.
  • Note: If you use fiscal year variants with different period limits in the ledgers that are affected by the reorganization, the transfer posting can lead to imprecision in the data. For more information, see SAP Library (for the path, see the section "Further Information").
  • The objects to be reorganized already have a profit center assignment.

Note: The reorganization does not affect classic Profit Center Accounting.

III.
  • If you want to reorganize the GR/IR clearing account as well as receivables and payables, you need to have implemented document splitting.
  • If you use document splitting, you are not required to have set the Zero Balance indicator.
  • Document splitting is not required for the reorganization of material stocks, work in process, and fixed assets.
III.

If you want to reorganize fixed assets, the following prerequisites must be met:

Besides General Ledger Accounting (FI-GL), you also use Asset Accounting (FI-AA) in your production system.

You have made the following Customizing settings specially for the reorganization of fixed assets within a profit center reorganization (reorganization plan type Profit Center):

  • You have activated segment reporting for fixed assets in Customizing for Asset Accounting with the activity Activate Segment Reporting.
The prerequisites stipulated there need to be met.
  • You have activated the account assignment objects Profit Center and Segment.

  • You have set the Acct Assignment Object Same in Asset Master and Posting indicator for both of these account assignment objects.

Note:
To transfer asset portfolios, the system applies a default transaction type from Asset Accounting. In the case of asset retirements, for example, the default transaction type is stored in Customizing for Asset Accounting under Specify Default Transaction Types.

III.

In the reorganization, only the distribution of master data (such as ALE) is supported for cost centers.

Master data distribution is not possible for orders.

Specific System Prerequisites for the Segment Reorganization

III.
  • The system transfers balances as follows: In cases requiring a balance to be corrected in a specific ledger, at least one document is created for each ledger. The system then makes postings using the ledger group with the same name. The ledger group of the same name must exist and must contain the ledger of the same name exclusively (that is, 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 message FAGL_REORGANIZATION 072 by deploying it as a warning message, not an error message. In this way, the postings are made to all ledgers in the ledger group. However, you must first ensure that the balances in all affected ledgers actually need to be corrected.
This setting may be useful in cases where you do not want to correct balances directly in ledgers (such as day ledgers or week ledgers) to which you usually make postings by means of the ledger group during valuations.
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 the above-mentioned message is issued as a warning message only, postings are made to ledger group L1, and the balances in ledgers L1 and T1 are corrected.
  • Note: If you use fiscal year variants with different period limits in the ledgers that are affected by the reorganization, the transfer posting can lead to imprecision in the data. For more information, see SAP Library (for the path, see the section "Further Information").
III.
  • If you want to reorganize receivables and payables or other open items, you need to have implemented document splitting.
  • Document splitting is not required for the reorganization of other object types.
  • If you use document splitting, you are not required to have set the Zero Balance indicator.
III.

If you want to reorganize fixed assets, the following prerequisites must be met:

Besides General Ledger Accounting (FI-GL), you also use Asset Accounting (FI-AA) in your production system.

You have made the following Customizing settings specially for the reorganization of fixed assets within a profit center reorganization (reorganization plan type Profit Center):

  • You have activated segment reporting for fixed assets in Customizing for Asset Accounting with the activity Activate Segment Reporting.
The prerequisites stipulated there need to be met.
  • You have activated the account assignment objects Profit Center and Segment.

  • You have set the Acct Assignment Object Same in Asset Master and Posting indicator for both of these account assignment objects.

Note:
To transfer asset portfolios, the system applies a default transaction type from Asset Accounting. In the case of asset retirements, for example, the default transaction type is stored in Customizing for Asset Accounting under Specify Default Transaction Types.

II. Organizational Prerequisites

Specific Organizational Prerequisites for a Profit Center Reorganization

III.

First consider which objects (such as material and work in process) need to be reorganized. Later on, you specify the scope of the reorganization in Customizing for the Reorganization (see the activities Remove Object Types from Derivation Hierarchy and Specify Restriction Characteristics for Reorganization Object Type mentioned below).

III.

Plan the process flow of the reorganization:

  • Note the following:
  • The reorganization date is always the first day of the posting period of the leading ledger.

  • There can only be one profit center reorganization per reorganization date (that is, per period) and per controlling area. The system runs a check to ensure that this is the case when you create a reorganization plan.

  • Before you can start the reassignment and the transfers, the closing operations of the previous period (including assessments, settlements, and so on) need to have been completed.

  • Before you start the reassignment, the posting periods preceding the reorganization period must be closed.

  • During the transfer, postings must not be made to objects included in the reorganization.

  • You cannot make any future postings and settlements that fall after the scheduled reorganization date.

Specific Organizational Prerequisites for the Segment Reorganization

III.

First consider which objects (such as payables and receivables) need to be reorganized. Later on, you specify the scope of the reorganization in Customizing for the Reorganization (see the activities Remove Object Types from Derivation Hierarchy and Specify Restriction Characteristics for Reorganization Object Type mentioned below).

III.

Plan the process flow of the reorganization:

  • Note the following:
  • The reorganization date is always the first day of the posting period of the leading ledger.

  • There can only be one segment reorganization per reorganization date (that is, per period) and per controlling area. The system runs a check to ensure that this is the case when you create a reorganization plan.

  • Before you can start the reassignment and the transfers, the closing operations of the previous period (including assessments, settlements, and so on) need to have been completed.

  • Before you start the reassignment, the posting periods preceding the reorganization period must be closed.

  • During the transfer, postings must not be made to objects included in the reorganization.

  • You cannot make any future postings and settlements that fall after the scheduled reorganization date.

Specific Organizational Prerequisites for Reassignments in Funds Management

For you to be able to perform reassignments in Funds Management using reorganization plan type 002, the following prerequisites need to be met:

Establish which scenario you are using. For information about the different scenarios, see SAP Library for SAP ERP Central Component on SAP Help Portal at http://help.sap.com under Accounting -> Public Sector Management -> Funds Management -> Closing Operations -> Reassignments with General Ledger Accounting.

Irrespective of the scenario used, you need to activate plan type 002; the additional settings in Customizing for the Reorganization are only necessary if you use scenario 1 (General Ledger Accounting is activated with document splitting, and at least one FM account assignment element for reassignment is updated in General Ledger Accounting).

General Ledger Accounting must not have been implemented with the same year change as the desired reassignment from Funds Management.

The fiscal year variant of the FM area must be the same as that of the company codes affected by the reassignment.

Document Splitting

Document splitting has been activated in General Ledger Accounting. The FM account assignment elements to be reassigned with the fiscal year change in FM (commitment carryforward) are defined as document splitting characteristics. Furthermore, you have defined the FI document reference (KNBELNR) as a technical document splitting characteristic in Customizing under Define Technical Document Splitting Characteristics.

Reassignment of Asset Portfolios

To transfer asset portfolios, the system applies a default transaction type from Asset Accounting. In the case of asset retirements, for example, the default transaction type is stored in Customizing for Asset Accounting under Specify Default Transaction Types.

Restrictions for Reassignments in Funds Management

The following restrictions apply to reassignments for Funds Management:

  • If you use a special purpose ledger, note the following: When an account assignment is reassigned, no balances are transferred in the special purpose ledgers. This produces an inconsistency between the ledgers.
  • If you use Grants Management, note the following:
For the purpose of avoiding inconsistencies, it is not possible to reassign the account assignment element Grant.
  • For technical reasons, adjustments cannot be made for FI-CA documents, down payments, or down payment clearing in General Ledger Accounting. For more information, see the SAP Library for SAP ERP Central Component on the SAP Help Portal at http://help.sap.com under Accounting -> Public Sector Management -> Funds Management -> Actual Update and Commitment Update -> Reassignment.

Process Flow for FM Reassignments with General Ledger Accounting (Scenario 1)

Plan the process flow of the reorganization.

Note the following:

  • Before you can perform commitment carryforward for invoices (value type 54) with a reassignment in Funds Management, you need to have created a valid reorganization plan of plan type 002 (FM reassignment).
  • They can only be one reorganization plan with plan type 002 (FM reassignment) per FM area and fiscal year. The system runs a check to ensure that this is the case when you create a reorganization plan.
  • The reorganization date is the first day of the new fiscal year of the FM area. Each company code that is assigned to the FM area must have the same fiscal year variant.
Example:
Your fiscal year is the calendar year, and you carry forward an open commitment in Funds Management from 2010 to 2011. The reorganization date is therefore 2011-01-01.
  • FM documents with an FI reference are determined and reassigned on the basis of the FM commitment carryforward. This obviates the need for this object type to be generated and reassigned separately within the reorganization plan. Only the FI balances are transferred by means of the reorganization plan.
  • You have the option of reassigning asset portfolios using the selections made for the reassignment of the budget. Fixed assets are generated and ressigned using the reorganization plan. The reassignment also entails the automatic transfer of the asset balances.

III. Settings in Customizing for the Reorganization

General Settings in Customizing for the Reorganization

III.

In Customizing for the Reorganization, you have to make at least the following settings:

Furthermore, we recommend that you also perform the following activities:

For more information, see the Implementation Guide for Reorganization under Remove Object Types from Derivation Hierarchy.
III.

The reorganization is available as a Web Dynpro application in the portal as well as being available as an application in the NetWeaver Business Client.

To be able to use the reorganization in the portal, you need to install the business package BP for Reorganization Management(BPERPREORG).

This business package does not contain any predefined roles; it is only intended for reuse. To facilitate the evaluation of the contents of the worksets by administrators, the worksets of this business packages are embedded by delta link in work center pool role 1.5 of the Business Package for Common Parts.

However, you can define your own roles (such as Reorganization Manager and Object Owner). You can then use the worksets of the business package BP for Reorganization Managementin your own roles:

Workset: -> Own Role
Overview of Reorganization Plans (Reorganization Plan Overview) -> Reorganization Manager
Overview of Object Lists (Object List Overview) -> Object Owner

For the use of the reorganization in the NetWeaver Business Client, there are similar PFCG roles:

  • Role for the reorganization manager: SAP_FI_GL_REORG_MANAGER
  • Role for the object owner: SAP_FI_GL_REORG_OBJLIST_OWNER

The report launchpad FAGL_REORG exists for the reorganization manager, both in the application in the portal as well as in the NetWeaver Business Client. It comprises all other programs that you need for the reorganization.

Further information

  • For more information on Profit Center Reorganization, see SAP Library under SAP ERP Central Component -> Accounting -> Financial Accounting (FI) -> General Ledger Accounting (FI-GL) -> Profit Center Reorganization.
  • For more information on Segment Reorganization, see SAP Library under SAP ERP Central Component -> Accounting -> Financial Accounting (FI) -> General Ledger Accounting (FI-GL) -> Segment Reorganization.
  • For more information on Reassignments in Funds Management, see SAP Library under SAP ERP Central Component -> Accounting-> Public Sector Management -> Funds Management -> Closing Operations -> Reassignments with General Ledger Accounting.






SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 25757 Date: 20240523 Time: 200923     sap01-206 ( 348 ms )