SAP ABAP IMG Activity ISM_PUBL_MIG_DO (Execute Media Product Migration for Issues)
Hierarchy
☛
IS-M (Software Component) SAP MEDIA
⤷
IS-M (Application Component) SAP Media
⤷
JSDI (Package) IS-M/SD SD Integration
IS-M (Software Component) SAP MEDIA⤷
IS-M (Application Component) SAP Media⤷
JSDI (Package) IS-M/SD SD Integration
IMG Activity
| ID | ISM_PUBL_MIG_DO | Execute Media Product Migration for Issues |
| Transaction Code | S_KK4_82000459 | (empty) |
| Created on | 20001204 | |
| Customizing Attributes | ISM_PUBL_MIG_DO | Execute Media Product Migration |
| Customizing Activity | ISM_PUBL_MIG_DO | Execute Media Product Migration |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISM_PUBL_MIG_DO |
In this step, you perform media product migration.
In migration, the issues for each edition are deleted from the migration date and migrated initially to the issue sequence for the corresponding media issues as planning values.
The following attributes are copied from the issue to the issue sequence:
- Publication date
- Copy number
- Variant types
- Year number
- Number in year
All other attributes of the media issue are copied from the template issue you use in the issue sequence (in the next step).
Requirements
- The migration program is only executed if the publication/edition and media product family/media product data is consistent.
Further notes
- If issues are deleted in this step and migration is not yet completed for a publication, you cannot execute functions in Periodical Sales and Distribution that affect issues of this publication from the migration date. Check customer-specific and standard programs to ensure that functions that count issues, for example, in order and complaint processing, billing, revenue deferral and data transfer to Financial Accounting are not executed during migration. Processing is canceled for standard programs if issues are counted in the migration period while migration is active.
In addition, the following processes should not run parallel to this report:
- Processing of issue sequences for migrated media products
- Maintenance of generation triggers (if generation was used in the periodical product master)
For detailed information, see the documentation on report RJPMPMIGRATION.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | 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 | ISM_PUBL_MIG_DO | 0 | I170007112 A I500000230 |
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 |
| ISP_DUMMY | D - Dummy object | JPMPMIG |
History
| Last changed by/on | SAP | 20030409 |
| SAP Release Created in | 463 |
