Hierarchy
MDG_FND (Software Component) MDG Foundation⤷
CA-MDG-AF (Application Component) Application Framework⤷
MDG_TRANSPORT_TOOL (Package) Transport Tool
IMG Activity
| ID | MDG_TR_REORG | Table Entries for Transport Container |
| Transaction Code | S_SE3_50000216 | (empty) |
| Created on | 20040921 | |
| Customizing Attributes | MDG_TR_REORG | Reorganization of Transport Container Tables |
| Customizing Activity | MDG_TR_REORG | Reorganization of Transport Container Tables |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | MDG_TR_REORG |
Use
The tables for the transported data constantly increase in size through frequent Customizing transports with the transport tool of the Master Data Governance Application Framework. This may result in poor performance. With this activity, you reorganize these tables to delete table entries that are no longer required.
During the reorganization, the system deletes the table entries referenced by the transport requests in the transport tables (for example, MDG_MDFTRANS). Since this involves redundant data only, you can perform the reorganization without taking any risks. However, the detailed composition of the object list of a transport request can no longer be recognized after the reorganization.
The reorganization can be useful both in the source system and in the target system of the transports. You can delete table entries on successful exports (source system) or successful imports (target system) depending on in which system you perform the activity.
Note: This activity is optional. You only need to perform the reorganization when you think that the size of the transport tables makes this necessary.
Requirements
Standard settings
Activities
You can either start collective or single processing of transport requests:
- Collective Processing
All obsolete table entries are deleted, in particular entries on already deleted transport requests and on executed client copies. Collective processing with the standard option 'Delete Obsolete Entries' is suitable for periodic scheduling as a background job.
Optionally, you can delete entries on transport requests that still exist (successful imports or exports). All entries on the selected transport requests are deleted in this option. You can also delete these requests if the request status permits this. - Single Processing
You can specifically delete entries on individual transport requests. Optionally, the request can also be deleted (for example, test requests).
If entries are deleted during an update run, this is logged in the application log under the object MDG_TR (MDG: Transport Tool), subobject REORG (Reorganization).
In a test run, the system displays the number of data records to be deleted for each table.
Example
Business Attributes
| ASAP Roadmap ID | 306 | Establish System Administration |
| 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 | MDG_TR_REORG | 0 | BTD0000051 | Application Framework |
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 | MDG_TR_REORG |
History
| Last changed by/on | SAP | 20090225 |
| SAP Release Created in | 702 |
