Ansicht
Dokumentation

OALE_DSTSCN_ACCCO - Cost Center Accounting

CL_GUI_FRONTEND_SERVICES - Frontend Services   ABAP Short Reference  
This documentation is copyright by SAP AG.

In this activity, you make settings required for distribution in Cost Center Accounting.

There is a difference between settings for distribution method one (centralized Cost Center Accounting), and those for method two (decentralized Cost Center Accounting).

Consistency Check

The function in this section carries out a consistency check of the settings made here. We recommend you use this consistency check to make the relevant settings.

Execute the function in the decentralized systems. Then you can check whether the settings between the systems for the required message types have been correctly maintained.

Double-click on a line in the consistency check log to make the required settings.

You must have maintained the partner profiles in all the systems.

Notes on Overhead Cost Controlling

You make Overhead Cost Controlling settings in Customizing, under Controlling.

The following settings are required to distribute a controlling area:

• The distribution method must be defined in the controlling area for the basic data in the "Distribution method" field. You can choose between distribution method one or two.

• The logical system name of the central controlling system must be defined in the controlling area for the basic data in the "Logical system" field. The logical system name is defined in the installation and in the client settings. (In IMG under:
  Basis Components
  Distribution (ALE)
  Sending and Receiving Systems
  Logical Systems
  Assign Logical System to a Client

• If you use distribution method two, you also assign all cost centers to a master system, which is the logical system for the cost center.

• If you want to use the profit center accounting, read section Distribution scenarios -> Profit Center Accounting

• If you want to use profitablitity analysis, read section Distribution scenarios -> Profitablitity Analysis.

Synchronization of settings using the transport system

Some settings for overhead cost controlling need to be in all systems in the same form.

The easiest way to ensure this, is by doing your customizing in a centralized system, and then distributing the data to all systems affected.

The transport system is normally used for the first time that decentralized controlling is provided with customizing data.

For information on compiling the transport orders for decentralized controlling systems, see the Implementation Guide (IMG), under the section on Controlling -> General Controlling -> Productive Start Preparation -> Transport System Settings.

Individual setting synchronization

If you do not make the settings for overhead cost controlling centrally in a Customizing system, but individually in each of the affected systems, then ensure that they all contain the following data in the same form:

• Data for all controlling areas:

• Currencies

• Charts of accounts

• Attributes for the controlling area: Basic data

• Distribution method

• Logical system

• Currency type

• Currency

• Chart of accounts

• Fiscal year variant

• Standard hierarchy for cost centers

• Activated reconciliation ledger indicator

• Attributes of the controlling area: Control indicators

• Cost Center Accounting activated

• Indicator for all currencies

• Indicator for company code validation

Assignment of controlling area - company code

Assignmeents between controlling areas and company codes can only be maintained centrally and distributed, if the assignments between local and global company codes match.

Otherwise, you need to make the assignments individually in each system.

The concept of global company codes is explained in Customizing, under the following path:
Predefined ALE Business Processes
Accounting
Financial Accounting

Notes on Distributing Plan Prices

Plan prices for the cost center/activity type combination are distributed using the "COACTV" message category. Before you do this, you need to activate the integration for each planning version used and fiscal year.
To do this in the menu Cost Center Accounting,
choose Planning -> Planning aids -> Integration active in

For distribution method one, you need to activate the integration in the centralized system. For method two, you need activate integration in both the centralized and the decentralized systems.

Notes on Distributing the Reconciliation Ledger

When Cost Center Accounting is distributed, you also need to distribute the reconciliation ledger.

If centralized Cost Center Accounting is used in a system other than the centralized general ledger, then you also need to make some more settings in Customizing in addition to the setting for the message flow between decentralized and centralized cost accounting. This is for the distribution of the reconciliation ledger.

• The "RCLROL" message dispatch (from decentralized and centralized Cost Center Accounting to the centralized general ledger) must also be inserted in your distribution model with the company code filter object.

• You need to maintain these two message flows in the communication parameters.

• There is a restriction, whereby reconciliation postings can only be made on company code level.

Distribution Method One: Partner profiles

Partner profiles in the centralized cost accounting system

In the centralized cost accounting system, you need to maintain outbound partner profiles for each decentralized cost accounting system.

Message type	Meaning
COSMAS	Cost centers
COELEM	Cost elements
COAMAS	Activity types
COGRP1	Cost center groups
COGRP2	Cost element groups
COGRP5	Activity type groups
COCOKA	Control data object/cost element
COACTV	Prices for cost center/activity type
(RCLROL	Roll-up reconciliation ledger
if the centralized system
for the controlling area and
the company code are different)

You need to maintain the inbound partner profiles for the each decentralized cost accounting system for the following message types:

Message type	Meaning
COSFET	Requesting cost centers
COAFET	Requesting activity types
CODCMT	CO document
RCLROL	Roll-up reconciliation ledger
(RCLROL	Roll-up reconciliation ledger,
in the centralized system for
the company code
if the centralized system for
the controlling area and
the company code are different)

Partner profiles in the decentralized cost accounting system

In each decentralized cost accounting system, you need to maintain outbound partner profiles for the centralized cost accounting system for the following message types:

Message type	Meaning
COSFET	Requesting cost centers
COAFET	Requesting activity types
CODCMT	CO-Beleg
RCLROL	Roll-up reconciliation ledger
(RCLROL	Roll-Up reconciliation ledger
in the centralized system for
the company code
if the centralized system for
the controlling area and
the company code are different).

You need to maintain inbound partner profiles for the centralized cost accounting system for the following message types:

Message type	Meaning
COSMAS	Cost centers
COELEM	Cost elements
COAMAS	Activity types
COGRP1	Cost center groups
COGRP2	Cost element groups
COGRP5	Activity type groups
COCOKA	Control data object/cost element
COACTV	Prices for cost center/activity type
(RCLROL	Roll-up reconciliation ledger,
if the centralized system for
the controlling area and
the company code are different).

Note

The COSCOR (cost centers (core)) and COACOR (activity types (core) message types are obsolete, and should not be used any more. Under no circumstances should they be used with the ZH>COSMAS (cost centers) and COAMAS (activity types) message types.

Distribution Method Two: Partner profiles

Partner profiles in the centralized cost accounting system

You need to maintain outbound partner profiles for each decentralized cost accounting system for the following message types:

Message type	Meaning
COSMAS	Cost centers
COELEM	Cost elements
COAMAS	Activity types
COGRP1	Cost center groups
COGRP2	Cost element groups
COGRP5	Activity type groups
COCOKA	Control data object/cost element
COACTV	Prices for cost center/activity type
CODCMT	CO document
(RCLROL	Roll-up reconciliation ledger
if the centralized system for
the controlling area and
the company code are different).

You need to maintain the inbound partner profiles for each decentralized cost accounting system for the following message types:

Message type	Meaning
COSFET	Requesting cost centers
COAFET	Requesting activity types
COCOKA	Control data object/cost element
COACTV	Prices for cost center/activity type
COTOTL	Totals records
CODCMT	CO document
RCLROL	Roll-up reconciliation ledger
(RCLROL	Roll-up reconciliation ledger,
in the centralized system of
the company code,
if the centralized system for
the controlling area and
the company code are different).

Partner profiles in the decentralized cost accounting system

In each decentralized cost accounting system, you need to maintain outgoing partner profiles for the centralized cost accounting system for the following message types:

Message type	Meaning
COSFET	Requesting cost centers
COAFET	Requesting activity types
COCOKA	Control data object/cost element
COACTV	Prices for cost center/activity type
COTOTL	Totals records
CODCMT	CO document
RCLROL	Roll-up reconciliation ledger
(RCLROL	Roll-up reconciliation ledger,
in the centralized system for
the company code,
if the centralized system for
the controlling area and
the company code are different).
You need to maintain outgoing partner profiles for the centralized cost accounting system for the following message types:
Message type	Meaning
COSMAS	Cost centers
COELEM	Cost elements
COAMAS	Activity types
COGRP1	Cost center groups
COGRP2	Cost element groups
COGRP5	Activity type groups
COCOKA	Control data object/cost element
COACTV	Prices for cost center/activity type
CODCMT	CO document
(RCLROL	Roll-up reconciliation ledger,
if the centralized system for
the controlling area and
the company code are different).

Note

The COSCOR (cost centers (core)) and COACOR (activity types (core)) message types are obsolete and should no longer be used. Under no circumstances should they be used with the COSMAS (cost centers) and COAMAS (activity types) message types.

Error handling

Specifying responsibilities for workflow error processing in the distribution environment.

Workflows are created to problems in cost accounting in the distribution environment. You need to specify employees who are responsible for the errors. You can use ALE-customizing for maintenance:
Basis Components
Distribution (ALE)
Error Handling

Distribution Method One:

Specifying responsibility in the centralized cost accounting system

Maintain assignments for the following standard tasks:

Standard task: Identifier	Name
COSFET_Error	COSFET Inbound error
COAFET_Error	COAFET Inbound error
CODCMT_Error	CODCMT Inbound error
RCLROL_Error	RCLROL Inbound error

Specifying responsibility in the decentralized system

Maintain assignments for the following standard tasks:

Standard task: Identifier	Name
COSMAS_Error	COSMAS Inbound error
COELEM_Error	COELEM Inbound error
COAMAS_Error	COAMAS Inbound error
COGRP1_Error	COGRP1 Inbound error
COGRP2_Error	COGRP2 Inbound error
COGRP5_Error	COGRP5 Inbound error
COCOKA_Error	COCOKA Inbound error
COACTV_Error	COACTV Inbound error

Distribution Method Two:

Specifying responsibility in the centralized cost accounting system

Maintain assignments for the following standard tasks:

Standard task: Identifier	Name
COSFET_Error	COSFET Inbound error
COAFET_Error	COAFET Inbound error
COTOTL_error	COTOTL Inbound error
COCOKA_Error	COCOKA Inbound error
COACTV_Error	COACTV Inbound error
CODCMT_Error	CODCMT Inbound error
RCLROL_Error	RCLROL Inbound error

Specifying responsibility in the decentralized system

Maintain assignments for the following standard tasks:

Standard task: Identifier	Name
COSMAS_Error	COSMAS Inbound error
COELEM_Error	COELEM Inbound error
COAMAS_Error	COAMAS Inbound error
COGRP1_Error	COGRP1 Inbound error
COGRP2_Error	COGRP1 Inbound error
COGRP5_Error	COGRP1 Inbound error
COCOKA_Error	COCOKA Inbound error
COACTV_Error	COACTV Inbound error
CODCMT_Error	CODCMT Inbound error

Note

In the distribution model, you must maintain a company code or a controlling area as a filter object for the "RCLROL" message type.

Check consistency

After you have made the settings for distributed Cost Center Accounting, you can check the settings for consistency (see Set up Communication , Partner Profiles, and Check Model Settings).

BAL Application Log Documentation   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 24338 Date: 20240523 Time: 194626     sap01-206 ( 166 ms )