Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KC (Package) Cost Accounting Controlling EIS
IMG Activity
| ID | CFOKCMOKXB | Transport Settings |
| Transaction Code | S_ALR_87000382 | IMG Activity: CFOKCMOKXB |
| Created on | 19981222 | |
| Customizing Attributes | CFOKCMOKXB | Transport settings |
| Customizing Activity | CFOKCMOKXB | Transport settings |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | CFOKCMOKXB |
In this step, you create a transport request for transporting into a target system.
After you have made the EC-EIS or EC-BP settings, you can place all the objects which belong to these settings (table entries, data elements, domains, tables etc.) onto one transport request.
The source system collects all the dependent objects and places them onto a transport request. After they have been imported into the target system, the necessary generations are carried out automatically to activate the settings from the source system.
Requirements
The source and target systems must have the same SAP release (maintenance upgrade).
Recommendation
In this step, you create a transport request which is based on the current settings. For this reason, you should not add any new SAP-EIS objects or make any other settings while the transaction is running. It is possible to perform the following two steps separately: 'Create transport request' (what is to be transported) and 'Export' (database copy). If you make further settings between the time you create the transport request and perform the export, the changed objects will be processed, however, no new objects will be accepted in the transport request. This can lead to inconsistencies in the target system after the import.
You are therefore recommended not to make further changes to settings in EC-EIS or EC-BP between these two steps.
When the objects are collected for the transport request, the system cannot test which of the objects to be exported already exist in the target system. This means that objects can sometimes be imported and overwrite objects created in the target system. To avoid such problems, you are recommended to set up a single source system from where you can send to one or more target systems. However, you should not create any new EC-EIS or EC-BP objects (aspect, characteristic, key figure etc.) in the target system.
Activities
- Make the basic settings for the transport (see "Further notes" below).
- Choose a transport object class.
- Enter a transport request.
- Choose the objects to be transported.
- Choose the dependent object classes.
- Transport the request.
Further notes
You can use the transport tool more effectively if you make certain basic settings to begin with. Choose Goto -> Settings. You can determine the request type, ask for a splitting of the transport into Workbench and Customizing requests, set a simultaneous transport of all language versions of the objects to be transported, and have the system create the required transport requests automatically. After you have carried out and saved these basic settings, the settings remain effective for all future transports - until you change the settings again.
Reports whose names contain special characters cannot be transported for technical reasons. To transport such reports, you need to create a new report without special characters using the original report as a reference (Copy from).
To guarantee the consistency of the entire system, some of the tables and table entries which are referenced in EC-EIS and EC-BP are not transported. Only those ABAP/4 development workbench objects generated in EC-EIS or EC-BP, and the table entries administrated in EC-EIS or EC-BP, and changed during configuration are transported. Any settings which can be made in EC-EIS or EC-BP but which also have effects outside the application are not transported. This is to protect the consistency of the target system.
The following lists contains the objects which are not transported:
- All non-EC-EIS/EC-BP master data tables
- Fiscal year variants
- Authorization objects
- Distribution keys
- Revaluation factors
- Forecast profiles
- Weighting groups
- Object dependent parameters
- Planning aid accesses
Transaction data is not transported either.
Business Attributes
| ASAP Roadmap ID | 308 | Transfer Data to Live System |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | CFOKCMOKXB | 0 | HLA0009491 O HLA0009492 O HLA0009493 |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| IMGDUMMY | D - Dummy object | OKXB | 567 |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
