Hierarchy
⤷ CA-BFA-ABL (Application Component) ALE Business Process Library
⤷ DALE (Package) ALE Application
IMG Activity
ID | SIMG_OALE_LOPSP_011 | Distribution of Work Breakdown Structure |
Transaction Code | S_ALR_87008578 | IMG Activity: SIMG_OALE_LOPSP_011 |
Created on | 19990115 | |
Customizing Attributes | SIMG_OALE_LOPSP_011 | Distribution of Work Breakdown Structure |
Customizing Activity | SIMG_OALE_LOPSP_011 | Distribution of Work Breakdown Structure |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_OALE_LOPSP_011 |
You use this step to make the settings required for work breakdown structure (WBS) distribution.
These settings area required if you want to create WBSs in a (master) system and distribute it to a number of (receiver) systems.
The ALE business process ensures that a WBS created and saved in a master system is automatically created in one or more receiver systems too.
You can use controlling areas and the project profile as filters to control whether the WBS is distributed when you save it and in which receiver system it is created.
Activities
Determine a system in which you want to make all the cross-system settings.
- Maintain logical systems
Determine all the systems to be included in the distribution.
- Maintain distribution model
Define the master and receiver systems and choose the filter objects.
Object name: WorkBreakdownStructure
Method: SaveReplica
- Generate partner agreements
Determine the time at which the data is to be exchanged between systems.
- Activate object types in inbox/outbox
In the inbox and outbox, activet the serialized distribution using object types.
Object type: BUS2054
Archiving Recommendations
WBSs are only archived in the master system. They are deleted in the receiver systems as soon as you set the deletion indicator in the master system and save this change to the receiver system.
The "deletion flag" status must have been transferred to all the receiver systems before you activate the internal deletion indicator in the master system.
Further notes
A WBS created in a master system and distributed to a receiver system can only be overwritten in the receiver system with data from the same master system.
If you are using more than one system as master systems, we recommend you define different project number ranges for each system. You can use an additional locking indicator to prevent the same project number in another system.
For more information, go the Project System IMG and read Define project coding for project.
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 1 | 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_OALE_LOPSP_011 | 0 | HLA0006677 | Work Breakdown Structure |
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_TBDLS | V - View | SM30 | 001 LR | Logical Systems | ||
BD82 | T - Individual transaction object | BD82 | 001 LR | Generate Partner Profiles | ||
BD64 | T - Individual transaction object | BD64 | 001 LR | Maintain Distribution Model | ||
TBD56 | S - Table (with text table) | SM30 | 0012 LR | Activate Outbound Object Types | ||
TBD55 | S - Table (with text table) | SM30 | 0011 LR | Activate Inbound Object Types |
History
Last changed by/on | SAP | 19990115 |
SAP Release Created in |