Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
TR-CB (Application Component) Cash Budget Management⤷
FFCBC (Package) Cash Budget Management - Customizing
IMG Activity
| ID | SIMG_CFMENUOFTFFME4 | Transport Report |
| Transaction Code | S_ALR_87009251 | IMG Activity: SIMG_CFMENUOFTFFME4 |
| Created on | 19990225 | |
| Customizing Attributes | SIMG_CFMENUOFTFFME4 | Transport Report |
| Customizing Activity | SIMG_CFMENUOFTFFME4 | Transport Report |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOFTFFME4 |
In this step, you put together a transport request designed to transport the reports you have defined to a target system.
Requirements
The target and source systems must have the same put level.
Recommendation
The transport request is based on the current settings. For this reason, you should not create any new drilldown objects (reports, forms, key figures) while the transaction is running, nor should you enter any more settings. In the SAP transport system, a considerable time may elapse between the transport request's being put together (defining what is to be transported) and the actual export (when the data is extracted). If you enter further settings in drilldown reporting between these two points in time, the system does partly include the changed objects, but no new objects are included in the transport request. For this reason, we recommend that you do not enter any new settings during this period.
If you change any forms, you must regenerate the reports to which you have assigned the forms in the source system, then transport them again to the target system.
As it is not possible to test the transport request automatically when you put it together - that is, to determine which of the drilldown objects to be transported may already exist in the target system - drilldown objects created in the target system may be overwritten when you import from the source system. To avoid situations where important data is unintentionally overwritten, we recommend that you set up one source system only from which data can be sent to one or more target systems.
Activities
- Enter an FM area.
- Specify the report type (Funds Management or Cash Budget Management).
- Specify a transport request.
- Choose whether you want to run the request in the background.
- Select the objects you want to transport.
- Choose the dependent object classes.
- Use the transport system to carry out the transport request.
Further notes
For technical reasons, reports whose names contain special characters cannot be transported. To get around this problem, you must create a new report with no special characters in the name, using the old report as a reference.
For technical reasons, you only need to enter an FM area if you have already worked with the system but have not yet created an FM area at any other point. Since the defined reports and form do not reference a particular FM area, you can enter any of the FM areas which exist in your system. If you have already worked with an FM area, you do not have to enter one now.
Business Attributes
| ASAP Roadmap ID | 207 | Establish Reporting |
| 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 | SIMG_CFMENUOFTFFME4 | 0 | HLA0001380 | Information System |
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 | FME4 | 517 | Transport Report |
History
| Last changed by/on | SAP | 19990225 |
| SAP Release Created in |
