|
The Enterprise Layer requires the tightest integration into key corporate functions. Typically this would be the case for owners of programs or of the assets that are being created or maintained using the project management tool. In an SAP context it is safe to assume that the following bullet points are being considered. Almost all enterprise functions are being performed in SAP. Other project management tools do not lend themselves to handle fully integrated key enterprise processes, not even in niche functional areas like project management. The key enterprise processes handled by SAP cover business functions like: Purchasing, MRP, Vendor Management and Accounts Payable, Customer Management and Accounts Receivable, General Ledger, Controlling (allocations, standard costing, and corporate budgeting), Production Planning, and Asset Management. At a minimum a high-level WBS should be in SAP, and SAP should be the system of records for this structure. This does not mean that not other structure aspects could or should also be handled by SAP. There may also be some feed-back of information from other systems into the WBS structure (like dates). Certain activities should be in SAP to allow for integration into MRP or Purchasing. Such activities could be network activities or operations on maintenance orders. In many cases all or nearly all activities will exist in SAP, even though sometimes duplicated in another project management package (like Primavera or MS Project). Besides these WBS elements and activities other project-specific functions should also be handled by SAP on the Enterprise Layer. Some of these are budgeting (in SAP terminology: approved financial budgets), settlements to FI (financial accounting), and the planning of activities that are supposed to be managed in-house (i.e., routine maintenance activities), occasionally even more.
See additional information in the following links. |
|
|
|
|
