SAP ABAP IMG Activity COM_PROD_DX_JOB (Schedule Data Exchange of Changes to Mini-Templates)
Hierarchy
SAP_ABA (Software Component) Cross-Application Component
   AP-MD-BF-TFW (Application Component) Templates
     BTFW (Package) Template Framework
IMG Activity
ID COM_PROD_DX_JOB Schedule Data Exchange of Changes to Mini-Templates  
Transaction Code S_S7B_68000047   IMG Activity: COM_PROD_DX_JOB 
Created on 20050622    
Customizing Attributes COM_PROD_DX_JOB   Schedule Data Exchange of Changes to Mini-Templates 
Customizing Activity COM_PROD_DX_JOB   Schedule Data Exchange of Changes to Mini-Templates 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name COM_PROD_DX_JOB    

Use

In this IMG activity you define how you want to schedule the distribution of mass changes, caused by changing mini-templates, to external systems, such as a connected BI system. You distribute mass changes that affect your template framework application object by scheduling a variant of the report TFW_DX_TEMPLATE_CHANGES.

Requirements

You should maintain this view only if the report TFW_DX_TEMPLATE_CHANGES is used to distribute data in your template framework application object. This is the case for the application object Product.

Standard settings

Activities

On the initial screen of this IMG activity you choose your application object. You then proceed to the details screen, where you can make entries in the following fields:

In the field Job Scheduling you choose how you want to schedule the job for carrying out your variant of report TFW_DX_TEMPLATE_CHANGES. You have the following options:

  • Manual

    This means that the system will always ask you to schedule the job manually when you make distribution-relevant changes to mini-templates. You should note, however, that manual scheduling is not recommended for the application object Product.

  • Periodic

    This means that you have already scheduled a regular job for carrying out your variant of report TFW_DX_TEMPLATE_CHANGES. The system does not take any action in this case.

  • Automatic

    This means that the system schedules a job for carrying out your variant of report TFW_DX_TEMPLATE_CHANGES whenever you make distribution-relevant changes to mini-templates.

The field Variant Name is relevant only for automatic job scheduling. Here you enter the name of the variant of report TFW_DX_TEMPLATE_CHANGES that you want to be carried out. You may not enter the variants of any other reports in this field.

The field Start Time is also relevant only for automatic job scheduling. Here you enter the time you want the job to start.

In order to avoid unnecessary batch jobs, we recommend that you make the following settings, according to your requirements:

  • In the case of regular changes to Customizing that have a great impact on the application objects, you schedule a periodic job.
  • In the case of Customizing changes that have a limited impact on the application objects, you schedule an automatic job.

When changes to mini-templates are transported, they are cascaded into all the relevant clients in the target system. However, this does not mean that the changes are automatically distributed to external systems, such as BI or ERP systems. If distribution is required, you should schedule the relevant variant of report TFW_DX_TEMPLATE_CHANGES in the appropriate clients of the target system.

Example

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
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 COM_PROD_DX_JOB 0 PAB0000025 Templates 
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
V_TFW_DX_JOB V - View SM30  
History
Last changed by/on SAP  20050623 
SAP Release Created in