To carry out actual postings in distributed systems for internal orders and work breakdown structures, you can distribute the master data and status information of internal orders and work breakdown structures to more than one system.
All functions for internal orders and work breakdown structures are available. However, in the master system you cannot call up the corresponding line items from line item reports if the line items all come from one receiving system.
You create the internal orders or the work breakdown structures in the master system. When you save them, the system distributes them automatically to one or more receiving systems. Through the filter objects Controlling area and order type or project profile, you control whether, and in which system the internal orders or work breakdown structures are to be distributed.
You can also send released internal orders and work breakdown structures at a later date.
·
Master data
and status information display
You can only make changes in the original master system. These changes are transferred to the
receiving systems.
· Postings from other R/3 components (such as FI, MM)
· Assessment
· Distribution
· Periodic transfers
· Manual reposting (costs, revenues, line items)
· Direct and indirect activity allocation
· Reposting internal activity allocation
· Accrual calculation
· Settlement debits
· Line item reports
· You cannot distribute WBS elements individually Only complete work breakdown structures are distributed.
· If a WBS element is assigned to an internal order, the system does not automatically distribute this WBS element to the receiving system. This means that the assignment of the WBS element to the internal order is not known in the receiving system.
If required, you can distribute the work breakdown structure first to the receiving system and then later or distribute the internal order.
· If you settle activities of cost centers that do not exist in the master system, you can only settle the internal order or work breakdown structure using settlement type FUL.
The following business transactions are not possible in the receiving system:
· Planning of internal orders, costs, and dates on work breakdown structures
· Budgeting and availability control
· Commitment postings
· Overhead costing
· Settlement of internal orders and WBS elements
· Assignments of orders and networks to the work breakdown structure
If you set the deletion indicator in the master system for an internal order or a work breakdown structure and this change was adopted in the receiving system, the system also deletes the given internal order or work breakdown structure in the receiving system. To ensure that in the receiving system you cannot make postings to deleted objects, you should choose a time period corresponding to the setting of the deletion flag and the setting of the deletion indicator (for example, for internal orders by setting residence time 1). You must make sure that the Deletion flag status has been adopted in all receiving system before you set the deletion indicator in the master system.
The
data flow between distributed systems is identical for internal orders and
work breakdown structures. This is described using the example of an internal
order: If you
create or change internal order 10001 in system 1, it is automatically
distributed to the receiving systems (in this case: system 2, system 3) and
created or changed there using the same order number. System 1 is the master
system of internal order 10001.
·
Postings made
in the master system are only available in the master system (CO document
10101 in this case).
·
Postings made
in other receiving system (in this case, system 3) are sent vial ALE to the
master system. They are available in both the receiving system and in the
master system (in this case, CO document 30001 from system 3 is given its own
number CO document 10102 in the master system).
Whenever possible, you should carry out all
cross-system Customizing settings in one system.
·
The
organizational units (for example, controlling area, company code) are
defined identically in the master system and the receiving
systems.
·
The order
type or the project profile is defined identically in the
master system and in the receiving systems.
·
The status
selection profiles are defined identically in the master system and
in the receiving system.
·
For internal
orders: The number ranges are defined separately in the master
system and in the receiving system. This is because a distributed internal
order in the receiving system is given the same number as in the master
system. For work breakdown structures: The project edit
screens are defined identically in the master system and in the
receiving system. In the receiving systems you should include a lock indicator
for the project edit screens, so that these project numbers cannot be used for
new projects. In
Customizing, choose Cross-Application Components
® Predefined
ALE Business Processes
® Accounting
® Master Data
Distribution
® Distribution of Internal Orders or Cross-Application Components
® Predefined
ALE Business Processes
® Logistics
® Master Data
Distribution
® Distribution of Work Breakdown Structure. Use
the following objects: Business object WorkBreakdownStructure InternalOrder Distribution method SaveReplica SaveReplica Message type INTERNAL_ORDER To
send internal orders and work breakdown structures at a later time, choose
Tools
® Business Framework
® ALE
® Master Data
Distribution
® Accounting
® Internal
Order or Projects
® Send. For
more information about ALE see the SAP Library under Basis
® Middleware
® ALE
Introduction and Administration.
Prerequisites
Activities