SAP ABAP IMG Activity APOCIF_IMVARJOB (Schedule Generation and Activation as a Job)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ CA (Application Component) Cross-Application Components
     ⤷ CFD (Package) IMG for APO Core Interface
IMG Activity
ID APOCIF_IMVARJOB Schedule Generation and Activation as a Job  
Transaction Code S_AX7_68000207   (empty) 
Created on 20020828    
Customizing Attributes ATAPOCIF_IMVARJOB   Schedule Generation and Activation as a Job 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name APOCIF_IMVARJOB    

Use

Master data is constantly being changed in the ERP system. For this reason you should regularly update your integration model to the newest status and transfer the changes to SAP APO. You should also delete the old versions of the integration model on a regular basis because these can hinder performance. To do this, we recommend you create the following programs as periodic jobs:

  1. Generate new versions of the integration model (RIMODGEN)
  2. Activate the newest versions (RIMODAC2)
  3. Optional: Delete the old versions (RIMODEL)

This procedure offers the following advantages:

  • Master data that has been newly created and that corresponds to the filter objects in existing integration models is included in those integration models and transferred to SAP APO.
  • Master data that was changed in such a way that it no longer corresponds to the filter objects of the integration model is excluded from the transfer.
  • Master data (materials, customers, vendors, sources of supply, and planning product assignment) that has been changed since the last transfer is updated to the most recent status and transferred to SAP APO.

Example

Requirements

Standard settings

Recommendation

We recommend the following sequence of activities to prevent data inconsistencies that may arise if APO-relevant master data is created during the generation and activation of a related integration model:

Generation
1. Integration model for transaction data (for example, planned orders)
2. Integration model for master data with dependent objects (for example, production process models) 3. Integration model for master data (for example, material, plant)

Activation
1. Integration model for master data
2. Integration model for master data with dependent objects
3. Integration model for transaction data

Activities

  1. Create a variant for the relevant program:
    • Use transaction SE38 to call the ABAP/4 Editor.
    • Enter the name of the report for which you want to create a variant.
    • Under Subobjects choose the option Variants and then Create.
    • Enter a name for the variant and choose Create.
    • Fill the entry fields as required.
    • Save your entries.
    • Enter the attributes for the variant.
    • Save the variant.
  2. Schedule the program as a job:
    • Define a job using the program name and the variant you have maintained.
    • Schedule the job as a periodic job.
    • Save the job.
    • Create a job for each variant that you have previously defined.

Further notes

We recommend that you schedule this sequence of jobs for each integration model for which ALE change pointers are written for the objects. These objects include:

  • Material masters
  • Vendors
  • Customers
  • Planning product assignment
  • Sources of supply

    Note that for changes to conversion factors for currencies, all sources of supply have to be retransferred if you want to use cost optimization in SAP APO. To do this, you use program RIMODINI.

For more information, see Scheduling periodic transfers with change pointers.

Business Attributes
ASAP Roadmap ID 152   Design data acquisition 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20050404 
SAP Release Created in