Hierarchy

⤷

⤷

IMG Activity
ID | MSR_TRC_ARCH | Notes on Implementation |
Transaction Code | S_YDH_92000043 | (empty) |
Created on | 20071004 | |
Customizing Attributes | MSR_TRC_ARCH | Notes on Implementation |
Customizing Activity |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | MSR_TRC_ARCH |
Use
All Business Add-Ins (BAdIs) that are grouped under this structure node belong to enhancement spot MSR_TRC_ARCH.
All of the BAdIs in this enhancement spot belong to the process used to archive the tracking data associated with advanced returns. Each BAdI corresponds to one program in this process, so they can be grouped together logically and technically into an enhancement spot.
When implementing these BAdI definitions, you need to consider the structure definition of the archiving object and the logic of the archiving programs in order to customize the existing process for data archiving.
It is not mandatory to implement these BAdI definitions. They allow you to modify the existing archiving process with your own data-archiving functions. If you choose to do this, you should implement all of the BAdI definitions.
These BAdI definitions must be implemented in different classes because they belong to a different archiving program and are technically and logically different.
Requirements
Standard settings
Activities
Example
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
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 | MSR_TRC_ARCH | 0 | HLA0006433 | Logistics - General |
Maintenance Objects
Maintenance object type |
History
Last changed by/on | SAP | 20080116 |
SAP Release Created in | 100 |