Company code merge

Before merging a Company code B to Company code A, you have to check all open PO,GR
and Invoice for payment.

Please clear all purchasing documents before merging.

After that you can change the assignment of company code to plant and you have to update
all master data(i.e G/L master) belongs to company code B.

You define company code B plants under company code A.

You should deactivate all FI, MM and SD org elements from company B.

Activate them to company A ie chart of accounts, GL accounts, profit centres on FI side and
plants, purchase org in MM side also map them in sales org elements.

If you dont want to use company B for any other purpose then you should delink all FI, MM
and SD org elements from company B and link them to company A like chart of accounts,
GL accounts, profit centres on FI side, plants, purchase org if there on MM and sales org
elements.

Use
You can merge multiple company codes within a client. The objects of all SAP applications
concerned are converted consistently. The document flow is not affected by this, and the
continuation of all running processes is guaranteed.

You can also change the descriptions (texts) of the company codes during a company code
merge.

Note
The following adjustments may be necessary in connection with a company code merge:

 Structures (for example, controlling areas)

 Master data settings (Customizing of general ledger, vendor, or customer accounts)

 Related charts of accounts

 Existing number ranges

Recommendation
Use the project roadmap for company code merge.

Integration
If you use other transformation solutions in your project in addition to Company Code
Merge, you can combine these with each other. You can combine the following
transformation solutions with the company code merge:

 Controlling Area Merge

 Cost Center Merge

 Profit Center Merge

 Cost Center Conversion

 Profit Center Conversion

 Controlling Area Rename

 Company Code Rename

Prerequisites
You are using the SAP Landscape Transformation solution.

You have closed and documented the old fiscal year with balance sheet and profit and loss
statement.

You have discussed the concept and process as well as requirements of the documentation of
company code merge with your auditor.

A test system is available. This system is a recent copy of the production system and is very
similar to the production system with regard to the hardware.

The transports can be imported from the test system into the production system.

You have clarified whether and how authorizations must be converted within the merge.

You have performed the following analyses:

 Archive Analysis
  SAP NetWeaver Analysis

 SAP NetWeaver BW Analysis

 Coding Scan

 ECC Business Application Analysis

 Report Variant Analysis or Conversion

 Runtime Estimation

 Analysis for Company Code Merge

Once you have performed the analysis for company code merge, you have implemented the
harmonization requirements that were listed in the analysis log. The following data of the
company codes to be merged must match:

 Operating concern of both company codes

 Currency and currency indicator

 Chart of accounts

 Fiscal year variant

You have defined which company code is the leading company code, that is from which
company code the original settings of the master data records and the Customizing settings
should be transferred.

Note
Normally, only one master record can be used within a merge ("have priority"). Therefore,
you cannot transfer specific settings from one of the source records and other settings from
one of the other source records.

You have implemented the harmonization requirements that were listed in the analysis log.

More Information
Analysis for Company Code Merge

Changes to the Database

SAP Note 1589619

Analysis for Company Code Merge

Use
You use the analysis for company code merge to find out before the company code merge
whether the required scenario can be supported technically regarding the company codes
involved.

Prerequisites
You are using the SAP Landscape Transformation solution.

The company codes to be analyzed are in the same system and in the same client.

You have discussed the concept and process as well as requirements of the documentation
with your auditor.

You have set up and saved the system environment of the analysis.

An RFC connection exists between the sender and receiver system.

You must have created a project.

You have assigned a project template to the project.

You have created a project execution plan.

Features
The analysis for a company code merge examines the following areas:

 Affected company codes and their organizational structures (credit control areas,
business areas, functional areas, FM areas. companies, segments, profit centers,
controlling areas, company codes, valuation levels, plants, sales organizations,
purchasing organizations):
 Is the planned company code merge possible as desired or must other steps be
performed in the run-up to a company code merge, such as a controlling area
merge or chart of accounts conversion?
 Are there organizational units for which a mapping is required, such as credit
control areas or companies?
  Which steps are necessary when the conversion is complete, such as
restructuring the credit limit?
 Settings for company codes regarding chart of accounts, fiscal year variant, local
currencies, and country key
 Use of Consolidation, Special Purpose Ledgers, General Ledger (New), Joint Venture
Accounting, Cash Management and Forecast
 G/L account, customer, and vendor master records: Do conflicts in the G/L account,
customer, and vendor master records need to be resolved in the run-up to the company
code merge?
 Asset Accounting
 House banks and cash journals: Are there double entries regarding house banks and
cash journals that need to be handled separately using mapping?
 Customizing settings: Are central Customizing settings identical, such as the
valuation level, fiscal year variant, and currencies?
 Archive: Are archives used? – These can be converted with an additional service after
the merge has been completed.

You get a list of possible conflicts as the result of the analysis. These must be resolved before
the actual company code merge.

I want to know how doesSAP SLO(System Landscape Optimisation) work.I have following
questions

1.Which parameters of the SAP systems such as system I'd and others are copied and which
are not copied during data migration using SAP SLO?

2.Which SAP modules are supported by SAP SLO?

3.Is SAP PI supported? If not then why?

Thank in advance

 SAP Managed Tags:

 SAP Landscape Transformation

Show replies

Answer
Accepted Solutions (1)
11-06-2013
0 Kudos

1.Which parameters of the SAP systems such as system I'd and others are
copied and which are not copied during data migration using SAP SLO?

=> It depends what you want to achieve by copy scenario.

2.Which SAP modules are supported by SAP SLO?

==> Almost all modules of standard ERP are supported.

3.Is SAP PI supported? If not then why?

==> Some of the SLO technologies do support PI systems, again it purely depends on your scenario.
Regards,
Sandeep
Show replies

Transformation Ihrer Landschaft mit

Automatisierung
Unser SAP System Landscape Transformation (SAP SLT)-Ansatz kombiniert unsere SAP-
zertifizierte Data Sync Manager™ (DSM) Suite und spezialisierte Berater, für einen

schnelleren, flexibleren und sichereren Prozess.