Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
PP-BD-RTG (Application Component) Routing⤷
CP0C (Package) R/3 Appl. devt.: Customizing PP Task Lists / PP Work Centers
IMG Activity
| ID | SIMG_CFMENUOLPSOP77 | Edit Working Areas |
| Transaction Code | S_ALR_87004344 | IMG Activity: SIMG_CFMENUOLPSOP77 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUOLPSOP77 | Edit Working Environments |
| Customizing Activity | SIMG_CFMENUOLPSOP77 | Edit Working Environments |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOLPSOP77 |
In this work step you define for the working environments in the Engineering Workbench,
- Which usage area is envisaged (for example general production)
- Which Focus is used
The focus determines, which object type are referred to by the selection criteria that the user enters.
- Which object types should be included in the working area
Only those object types that are included in the working area can be displayed and edited in the Engineering Workbench. A tab page is available for these object types on the selection criteria screen.
- Whether and which default values should be proposed
In doing this the default values are summarized by a profile
Requirements
Profiles that you want to use already have to exist in the system.
Activities
- When you are creating the working area: enter its usage area.
- If default values should be proposed to the users of the working area: enter a profile.
- Select the focus.
- Select the object types that should be included in the working area.
In doing this you should note that the object hierarchy forces particular combinations. For example: If you want to include the operation object type in the working area, you also have to include the sequence and task list header object types (see also: "further notes")
- Save the working area.
Further notes
The following rules apply for including object types in the working area:
- You have to include at least one of the task list header and BOM header object types in the working area.
- If an object type in a routing (for example: operation) is included in the working area, the hierarchically superior object types in a routing (for example: sequence) must also be included in the working area. The same correspondingly applies for an object type in a bill of material.
- If both the task list header and BOM header object types are included in the working area, the material-routing allocation object type must be included in the working area (and vice versa).
- If both the operation and item object types are included in the working area, the component assignment object type must be included in the working area (and vice versa).
Business Attributes
| ASAP Roadmap ID | 105 | Define functions and processes |
| Mandatory / Optional | 1 | Mandatory 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 | SIMG_CFMENUOLPSOP77 | 0 | HLA0006403 | Bills of Material (See LO-MD-BOM) |
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_T410 | V - View | OP77 | 0000000000 | Generated table maintenance: V_T410 |
History
| Last changed by/on | SAP | 19981223 |
| SAP Release Created in |
