Project Delivery Process D364

D364 - Configure Initial Model

DEFINITION

Set up essential initial master data, transaction data, periodic data, procedures, reports, etc.  Use preconfigured standard solutions where possible.

SUMMARY

Every Software Application System has many different functions that cover a client’s business requirements.  The correct selection of functions is the focus of the Software Application System implementation.  Therefore it is important to configure the initial model without misleading the client by either providing a system that is too complex for their operation or not detailed enough.  To provide a starting point for the prototyping work, essential initial master data, transaction data, periodic data, procedures, reports, etc need to be set up (except the organisational structure which was defined in Process D324).  Use preconfigured standard solutions where possible.

The initial setup should be based on the initial business model for the client organisation.  Normally, the starting point would be a standard model - see Process D354.

PATH PLANNING GUIDANCE

This process is optional.  It is normal practice when building integrated solutions using prototyping techniques.

DEPENDENCIES

Prerequisites (Finish-Finish):

• Create and maintain business enterprise model (R065)
• Define, agree and set up global parameters (D322)
• Define, agree and set up Software Application System organisational structures (D324)
• Select business processes from reference model (D354)

Dependent procedures (Finish-Finish):

• Build core testing data for prototyping (D383)
• Design/Prototyping (D400/D450)

RECEIVABLES

• Definition of Requirements (DoR)
• Delivery Approach Definition (DAD)
• Enterprise business model

DELIVERABLES

• Configured Base Software Application System.

TOOLS

• On-line Implementation Guide
• Software Application System Documentation
• Business process documentation
• Existing forms and reports

DETAILED DESCRIPTION OF TASKS

Initial needs to be addressed

The objective of the process is to provide an initial platform for prototyping as rapidly and effectively as possible.  Time should not be wasted in setting up the system to meet all the client organisation’s known requirements.  Examine known business needs that can easily be accommodated in the initial model.  In particular, use preconfigured business models and systems wherever possible.  Standard solutions may have already been selected from the Software Application System Reference Model - see Process D354.

Configuration

For each area, the configuration and customisation work should be reviewed according to specified guidelines.  Preliminary testing of the configured and customised applications should be conducted before entering the next customisation step.  It is best to configure the Software Application System system through an Image.  Additionally, textual documentation should be maintained detailing screen customisation.

• Set up Organisational Structures as previously defined.  Included are the settings of the client codes, company codes, plants, storage locations, valuation areas, sales organisations (if Sales Management is implemented), purchasing organisations (if Purchasing Management is implemented), and warehouses (if Warehouse Management is implemented). The organisational structure should have been set up previously. Review the documentation and customisation before continuing.
• Configure and Customise Master Data in terms of fields to be used, the numbering structure, type of number assignment, the numbering intervals, match code tables, and other options tables for master data.
• Configure and Customise Transaction Data in terms of fields to be used, types of number assignment, the numbering intervals, document flow, match code tables, and other option tables for transaction data.
• Configure Periodic Data, i.e. the batch processes and long-running transactions that are activated on a periodic basis:
• Review previously defined periodic processes
• Review the schedule timing of periodic processes
• Review the established backup procedures
• Integrate tune-up and reorganisation runs into the system
• Customise procedures such as purchasing authorisation process, availability check, etc.
• Configure and Customise Reports and Forms required by the various business functions.
• Customise standard reports using Software Application System utilities
• Update documentation on report usage
• Configure user master records and authorisation for persons who should use the Software Application System.
• Identify users
• Assign users to organisational structures
• Create user master records
• Set up user authorisations
• Approve user authorisations

Provide support for all configuration and customisation activities.  A quality assurance group should review the customisation carried out at various levels to assure optimality and correctness of all activities.