Use
In order to transfer data from an R/3 system the work center defined there and the pooled capacity are both relevant.
Features
Question |
Answer |
Are the R/3 work center categories relevant for the transfer? |
The work center category determines which R/3 views may be maintained. It also determines the field selection and task list usage. In R/3 the basic data, capacity and scheduling views must be maintained. |
How is the area of validity regulated? |
The work center is plant-related. |
How is the validity period regulated? |
For the work center there are no changes using change numbers. Only the allocation of a cost center has a time reference. This is transferred along with the transfer of the current data. It is not necessary to carry out a transfer of changes. In general, all data relevant to planning in R/3 should be maintained in APO after the transfer has taken place, should this be necessary. This includes capacity data. |
Is task list usage taken into account? |
No. |
Which standard value keys are supported – only standard keys or also user-defined keys? |
Using the standard value keys up to six standard values can be defined for each work center. These are used for costing and for capacity requirement calculation in scheduling. For process industries the six standard values may also be used. The standard value key SAP4 for Process Industries (PI) only contains the duration and the standard formula SAPC00 is entered in the field Formula for In-House Production Requirements. If setup and processing are to be taken into account for a resource then your own profile must be defined in each case. This creates a setup phase and a processing phase in the recipe which will then be taken into account for the setup or processing time (see recipe maintenance). |
Which capacity categories are supported? |
The capacity category is created as a dedicated resource in APO. |
How are pooled capacities taken into account? |
The pooled capacity is contained in a capacity category in R/3. At the transfer of the work center a resource is created for each capacity category contained in the work center. However, if a pooled capacity is maintained in the capacity category only a resource with its own key is generated for the pooled capacity. |
Are capacities also taken into account that are not relevant for finite scheduling? |
Yes. |
Is capacity overload relevant for APO? |
The field Capacity Overload is only used for the bucket resource. The field Capacity Overload can be transferred from R/3 using a customer exit. |
How is the indicator Can be Used by Several Operations evaluated? |
This indicator is used in connection with the number of individual capacities for the resource type in order to choose Single or Multi. |
Is the standard capacity transferred on a one to one basis? |
Start date, end date, break duration, rate of resource utilization and operating time are transferred. |
Can reference capacities be taken into account? |
Yes. |
Are intervals and versions of available capacity transferred. |
No. |
What additional importance does the capacity category have to which the scheduling view in R/3 is assigned? |
The capacity category of the scheduling view is created during PPM generation as the primary resource. |
How are the interoperation times taken into account that result from the location group or the queue time? |
They are not taken into account. These times are not relevant for the process industry. |
Are work center hierarchies supported? |
No. |
What customer exits are available? Are there examples for how these should be used with example coding? |
If resources are supposed to be created as mixed resources in APO then the customer exit APOBP002 can be used in APO. In the include ZXAPOBAPIUSER02 you can then set which resources should be transferred as mixed resources. Single resources are transferred as standard. |