Integration of Resources 
Use
You can use the
SAP APO Core Interface (SAP APO CIF) to transfer work centers from the
R/3 system to SAP APO. In SAP APO, the system creates 
resources for each
capacity category of the work center (such as employee or machine).
Prerequisites
· You can only transfer capacities that are assigned to a work center (or, for the process industry, to a resource) in SAP R/3. The Basic Data, Scheduling, and Capacity views must be defined in the master data of the work center and the work center must be contained in an active integration model.
· You have checked the IMG activity for transferring resources. You can find this IMG activity in the R/3 Implementation Guide under Integration With Other mySAP.com Components ® Advanced Planning and Optimization ® Application-Specific Settings and Enhancements ® Settings for Resources ® Set the Transfer of Resources to SAP APO.
Features
SAP APO CIF creates a resource in SAP APO for each capacity. In SAP R/3, you can define parameters (such as the resource category), which are not available in SAP R/3 but which are required in SAP APO. You can also include them in the first capacity transfer. However, this is only possible when using a Plug-In from 2003.1 in combination with SCM 4.0 or higher.
When the data is transferred, SAP APO CIF creates the resources in the database in SAP APO immediately (synchronously) but at a later point in time in SAP liveCache (asynchronously). If a large number of resources are transferred at the same time, a resource might be displayed in SAP APO that is not yet available for planning (for the creation of orders) because it does not yet exist in SAP liveCache.
The system transfers the following parameters unchanged:
· Short text
In SAP APO, you can create texts in different languages. If a short text is not defined in SAP R/3, the system enters the name of the work center and capacity category here (for example, AP1_001).
· The active version from SAP R/3 is adopted as the active capacity variant.
· The standard available capacity, determined through start, finish, break duration, rate of utilization, and operating time, or productive time.
·
If a reference
available capacity is defined for a capacity in SAP R/3, the system
creates another resource during the transfer and identifies this as the reference
resource.
The following parameters are converted into parameters specific to SAP APO:
· The resource name is regenerated from the following data:
¡ For a pool or reference capacity, the name of the capacity; or for an individual capacity “W” and the name of the work center (“W” stands for “work center”).
¡ The associated plant in SAP R/3.
¡ The capacity category.
¡ SAP R/3 source system with client number.
The personnel pool capacity POOL1 (capacity category 002) and the machine capacity (capacity category 001) of work center AP1 in plant WERK1 in the SAP R/3 system xxxCLNTxxx are created in SAP APO as the resources POOL1_WERK1_003@xxxCLNTxxx and WAP1_WERK1_001@xxxCLNTxxx.
· As location, the location is used that corresponds to the plant in SAP R/3 (for example, plant 0001 in SAP R/3 corresponds to SAP APO location PL0001@xxxCLNTxxx).
· You can define the resource type that is assigned when transferring the resource in the IMG activity Set the Transfer of Resources to SAP APO in the R/3 system. You can choose between the following resource types:
¡
Single-activity or
multiactivity resources
¡
Single mixed or
multimixed resources
¡
Calendar resources or
calendar mixed resources
You cannot create bucket, vehicle, and transportation resources in SAP APO through a transfer.
· As standard, a pool capacity with several individual capacities, or one capacity that can be used by several operations, is mapped to a multiactivity resource. Individual capacities without this indicator are mapped to single-activity resources. You cannot change the resource category in SAP APO.
·
If the capacity in
SAP R/3 is relevant to finite scheduling, the
resource is finite in SAP APO,
meaning that it can only be scheduled up to 100% utilization.
· Information about which factory calendar is valid for the resource is taken from SAP R/3. You have to create the factory calendar manually in SAP APO or by using a Customizing transport.
Creating and transferring APO resource data in R/3
You can create APO resource data directly in the R/3 work center and then transfer the work center.
You can use the APO Resource function key in the header data of the work center capacity. If you choose this function key, the system calls the following tab pages for the APO resource.
· General Data
· Planning Parameters
· Standard Capacity
Here, you can
directly specify the resource type and resource category with which the
capacity of the work center is created in SAP APO. You can also define the
capacity and planning parameters for the time-continuous
capacity, the PP/DS bucket
capacity, and the SNP bucket
capacity.
The following parameters are not transferred:
Task list usage
· Intervals
· Versions
· Hierarchies
· Definitions (shifts, break patterns, shift sequences)
You can choose
if you want to manage the relevant data for determining the available capacity
for each resource in SAP R/3 or in SAP APO. If you want SAP APO to determine
the resource capacity from SAP R/3, use the external capacity
for this resource.
· Scheduling formulas are only taken into account during the transfer of a production process model (PPM) to determine the duration of activities.
· The capacity category is also only taken into account when the PPM and PDS is generated. Capacity relevant to scheduling is assigned to the modes of the associated activities as a primary resource. All other capacities are assigned as secondary resources.
Change Transfer
The system automatically transfer the CIF changes to the header data of the resources. In the IMG activity Define Settings for Resources in the R/3 system, you define the resource copies for which the CIF changes are effective in SAP APO. You can choose between the following:
· Planning-version-independent resource
· Planning-version-independent copy of the resource, and the copy of the resource assigned to planning version 000
· Planning-version-independent copy of the resource, and all copies of the resource assigned to a planning version of model 000