Monthly Archives: January 2008

Reserve Fields

Reserve fields in the customer master record

The customer master includes reserve fields that are not assigned to any particular function. You can assign value to these fields and use them. To maintain the fields, select “Environment -> Additional data” on a customer master maintenance screen. The general data and the sales area data contain different fields:

    1. Ten fields were included in table KNA1 (general part of customer master record):
    Five two-digit fields:
    • KATR 1 (Attribute 1)
    • KATR 2 (Attribute 2)
    • KATR 3 (Attribute 3)
    • KATR 4 (Attribute 4)
    • KATR 5 (Attribute 5)
    Five three-digit fields:
    • KATR 6 (Attribute 1)
    • KATR 7 (Attribute 2)
    • KATR 8 (Attribute 3)
    • KATR 9 (Attribute 4)
    • KATR 10 (Atrribute 5)
    Check tables TVKO – TVK9 and the corresponding maintenance views
    V_TVV1 – V_TVK9 exist for the fields.
    2. Five three-digit fields were included in table KNVV (Sales data of the customer master record):
    • KVGR1 (Customer group 1)
    • KVGR2 (Customer group 2)
    • KVGR3 (Customer group 3)
    • KVGR4 (Customer group 4)
    • KVGR5 (Customer group 5)
    Check tables TVV1 – TVV5 and the corresponding maintenance views V_TVV1 – V_TVV5 exist for the fields. The fields were included in tables VBAK, VRRP, LIPS, KUAGVZ. Value is also assigned to them in the tables, which means that they were copied from the master record of the sold-party and used in the sales and distribution transaction.


In the standard system, the views are not included in the user interface. However, it is possible for you to include them in the user interface.

Using reserve fields

To use a reserve field of the customer master according to your requirements, proceed as follows:

    1. Change the short descriptions of the data elements by using the SAP enhancement.
    2. Choose Tools -> ABAB Workbench -> Utilities -> Enhancements -> Project management -> Text enhancements -> Key words -> Change.
    3. Maintain the corresponding entity tables TVKO-TVK9 or TVV1-TVV5.


You want to use the reserve fields of the customer master (general part) to store the liquidity level of your customer to use for statistical analyses. Proceed as follows:

    1. Change data element KATR1:
    • Change the short description “Attribute 1” to “Customer liquidity”.
    • Change the corresponding key words.
    2. Aktivate data element KATR1.
    3. Maintain entity table TVK1, by defining the following values:
    • “01” good liquidity
    • “02” average liquidity
    • “03” poor liquidity
    4. Use the same procedure for the remaining reserve fields KATR2-KATR10.

Reserve fields in the material master

Five three-digit fields were also included in material master MVKE. The entity tables TVM1 – TVM5 and the corresponding maintenance views V_TVM1 -V_TVM5 exist for these fields. The fields were included in the tables VBAP, VRRP, LIPS, MAAPV, where value is assigned to them. However, you cannot yet enter the fields in the material master maintenance. To use the reserve fields, proceed as described above for customer master maintenance.

Reserve fields in the sales order

In the sales order, the additional fields VBAK-KVGR1 – VBAK-KVGR5 were included at header level, to which value is assigned from the fields KNVV-KVGR1 – KNVV-KVGR5.

In the sales order, the additional fields VBAP-KVGR1 – VBAP-KVGR5 were included at item level, to which value is assigned from the fields MVKE-MVGR1 – MVKE-MVGR5.

To reach the additional fields in the sales document, select Header -> Additional data or Item -> Additional data.

New Fields For Material Determination

  • The following communication structures are relevant for material determination
    • KOMKD (Material determination – communication header)
    • KOMPD (Material determination – communication item)
    • KOMGD (Material determination – allowed fields)
    • For technical reasons, the communication structure KOMGD is used, which combines KOMKD and KOMPD, and which contains all fields that can generally be used for material determination. When entering new fields in KOMKD or KOMPD, the fields are also automatically included in KOMGD.

New fields for material determination are included in the following INCLUDES:

    • Header data: KOMKDZ (INCLUDE in KOMKD, KOMGD)
    • Item data: KOMPDZ (INCLUDE in KOMPD, KOMGD)

The routines for assigning values to the new fields in order processing are in member MV45AFZA. Use the following user exits:

    • USEREXIT_MOVE_FIELD_TO_KOMKD (header fields)
    • USEREXIT_MOVE_FIELD_TO_KOMPD (item fields)

New Fields For Output Control

  • The following communication structures are relevant for output control:
    • KOMKBK1  (Output Determination Communication Area CAS Appl. K1)
    • KOMKBV1  (Output Determination Communication Area Header Appl. V1)
    • KOMKBV2  (Output Determination Communication Area Header Appl. V2)
    • KOMKBV3  (Output Determination Communication Area Header Appl. V3)
    • KOMKBV5  (Communication Structure for Output Control Groups Appl. V5)
    • KOMKBV7  (Output Determination Communication Area Shipment Appl. V7)
    • KOMPBV1  (Output Determination Communication Area Item Appl. V1)
    • KOMPBV2  (Output Determination Communication Area Item Appl. V2)
    • KOMPBV3  (Output Determination Communication Area Item Appl. V3)
    • KOMB     (Field Catalog for Condition Keys: Output Control)
  • New fields for output control are entered in the following INCLUDEs:
    • Sales activities: KOMKBZ1 (in KOMKBK1)
    • Sales document header: KOMKBZ3 (in KOMKBV1)
    • Delivery header: KOMKBZ4 (in KOMKBV2)
    • Groups header: KOMKBZF (in KOMKBV5)
    • Billing document header: KOMKBZ5 (in KOMKBV3)
    • Sales document item: KOMPBZ1 (in KOMPBV1)
    • Delivery item: KOMPBZ3 (in KOMPBV2)
    • Billing document item: KOMKBZ5 (in KOMPBV3)
    • Shipment: KOMKBZH (in KOMKBV7)
    If you also want to use a new field for the setup of condition tables (key field) it must also be included in the structure KOMBZ (contained in KOMB).
  • The routines and user exits for assigning values to the new fields are found in the programs RVCOMFZZ, RVCOMFZ1, RVCOMFZ4, and LVCOMFZ1. It is also possible to copy partners here.
    The following user exits exist in member RVCOMFZ1:
    • USEREXIT_KOMPBV2_FILL (item fields in delivery)
    • USEREXIT_KOMPBV2_PARTNER (item fields for partners in delivery)
    • USEREXIT_KOMPBV3_FILL (item fields in billing document)
    • USEREXIT_KOMPBV3_PARTNER (item fields for partners in billing document)
    The following user exits exist in member RVCOMFZZ:
    • USEREXIT_KOMKBK1_FILL (header fields in sales activities)
    • USEREXIT_KOMKBK1_PARTNER (header fields for partners in sales activ.)
    • USEREXIT_KOMKBV1_FILL (header fields for sales documents)
    • USEREXIT_KOMKBV1_PARTNER (header fields for partners in sales documents)
    • USEREXIT_KOMKBV2_FILL (header fields in delivery)
    • USEREXIT_KOMKBV2_PARTNER (header fields for partners in delivery)
    • USEREXIT_KOMKBV3_FILL (header fields in billing document)
    • USEREXIT_KOMKBV3_PARTNER (header fields for partners in billing doc.)
    The following user exit exists in member RVCOMFZ4:
    • USEREXIT_KOMKBV5_FILL (header field for groups)
    The following user exits exist in member LVCOMFZ1:
    • USEREXIT_KOMPBV7_FILL (Shipment fields for header and stage)
    • USEREXIT_KOMPBV7_PARTNER (Shipment fields for partners)

In output determination, communication table KOMB contains all key fields that can be used for conditions for output determination.

When you create new fields for output determination, you can distinguish between two types of fields:

  • Fields that are used in condition tables
  • Fields that are only used to query conditions.

Both types of field have to be included in KOMKBV1. Fields which are only used to query conditions do not have to be included in KOMB and T681F or in the field catalog.

Note concerning name assignment

There are two possibilities for naming the field:

    • If the field is identical to the field in the communication table (e.g. VBAK), a value is assigned to it automatically by MOVE-CORRESPONDING. If SAP delivers the field in a subsequent system version, no generation errors will be caused.
    • If the field is not identical with the field in the communication table,you have to assign a value to it using the MOVE command. Begin the field name with the letters ZZ. This will avoid generation errors if the field is later delivered by SAP in a subsequent system version.

Example 1: Creating a new key field in output control

If, for example, you want to use the field ERNAM (name of sales employee) from the sales order (table VBAK) for output determination, proceed as follows:

    1. Enter the field ZZERNAM in communication structure KOMKBV1 in INCLUDE KOMKBZ3 in the Data Dictionary.
    By entering the field in KOMKBZ3, you automatically include it in communication table KOMKBV1.
    2. Enter ZZERNAM in the communication table KOMB (in KOMBZ).
    3. Assign values to the fields
    Values are  assigned to the fields in function module KOMKBV1_FILL. You have to enter the field and assign value to it manually in user exit USEREXIT_KOMKBV1_FILL. You will find the statements that you can use as a reference in the user exits.
    Copying partner numbers is a special case and will be explained in Example 3.
    4. Include ZZERNAM in the field catalog for the condition table for sales documents. The field catalogs must contain all the fields which you want to use to structure condition tables.

Example 2: Entering a condition field in the communication block

If you want to use condition field VBAK-AUDAT for output determination, proceed as described in Example 1. Remember that it is not necessary to include the new field in KOMBZ (KOMB) or to maintain table T681F or the field catalog.

Example 3: Entering a partner number in the communication block

Example 3 presupposes that there is a new partner function for buyer ZY in the sales document and that the number of this partner is to be copied.

When entering partner numbers in the communication block, proceed as described in the examples above. Partner function ZY is assigned to partner type AP in this example.

Remember to use a different routine to assign values to the new fields. If, for example, you want to copy the partner function ZY into the new field ZZEINKA, for example, the statement is:



The VBPA field used to assign a value to the new field depends on the partner function determined in the sales order. Each partner function is assigned to a partner type (e.g. partner function LF – partner type LI), which controls the assignment. Other source fields should be used for other partner types: COM_VBPA-KUNNR, COM_VBPA-LIFNR, COM_VBPA-PERNR and COM_VBPA-PARNR.

The following assignments exist:



1.1 Customized ASAP Methodology

Company ABC follows the ASAP Methodology for SAP Implementation and Rollout programs. However the methodology is customized to leverage the Company ABC Global Delivery Model (GDM) and the requirements of the engagement. For the purpose of this engagement, only the Project Preparation and Business Blueprint stages are in scope. However the complete methodology is presented for a complete overview.

Company ABC has categorized the rollout track-wise as the Business Process Design, Technical Requirements, Data Migration and Training Tracks. The Rollout Track will be governed by the Company ABC Project Management Methodology. The subsequent sections explain the various phases of project as proposed by Company ABC.

ASAP Implementation Methodology for Implementation and Rollouts

The proposed Company ABC approach involves appropriate pieces of the project work being done at our offshore facilities. This approach differentiates Company ABC in that our mature Global Delivery Model (GDM) allows us to do the work where it makes the most sense. Our experience in delivering projects in this manner acknowledges that many ERP implementation project activities require hands-on, face-to-face interaction onsite. There are, however, other tasks which do lend themselves very readily to a combined onsite – offshore delivery model. The Company ABC Global Delivery Model lowers cost, enhances quality and speeds time to completion.

Phase 1: Project Preparation

The objectives of the Program Preparation phase involve aligning the program to the overall organization strategy, drafting overall project plan, resources for various phases, and conducting fit- gap analysis. The participants for this phase would be Company ABC and the client Team, Business Process Owners and super users.




· Conduct stakeholder interviews

· Identify drivers for rollout

· Understand existing systems landscape

· Discuss and agree on scope and detailed project-plan

· Finalize roles and team structure for project tasks

· Develop roadmap

· Identify Milestones

· Formalized Resource Requirements

· Project Team Roles and Responsibilities

· Project Standards

· Preliminary Training and/or Overviews

· Finalize Project Plan

· Finalize Budget

· Experience from past rollouts projects enables quick problem definition and roadmap preparation tailored to the client’s needs.

· Conduct workshops and interviews with project stakeholders

· Questionnaires for interviews and workshops to help determine scope and key pain points

Table 1. Project Preparation Snapshot

Phase 2: Business Blueprint

The objectives of the Business Blueprint phase are to lock down scope, define functional specifications, define required customizations and prepare data migration plan.

Activities during the Business blueprinting stage




· Define to-be business processes

· Develop reference template for US and Canada

· Conduct an as-is business process study

· Develop future IT landscape

· Prioritize customizations

· Finalize scope, gather requirements for conversion, customization and reporting

· Prepare Training Material and impart training

· Plan for development and documentation of requirements for data mapping, cleansing, conversion and validation

· Organizational and Master Data Design

· Detailed Process Analysis

· Gap Resolution

· Process and Solution Documentation

· Authorization Design and Approach

· Development Request Documentation

· Test Strategy

· Templates for gap analysis, functional requirements, high-level design and detailed-design documents

· Knowledge of industry best-practices

Table 2. Business Blueprinting Snapshot

Phase 3: Business Realization

The realization phase includes developing functional and technical specifications, work flow, system test plans, baseline and the final configuration. Additional activities also include creation of reports, forms; data cleansing, data migration and integration testing.

Activities during the Business Realization stage




· Complete custom development

· Final system configuration

· Functional/unit testing

· Conduct data clean-up activities

· Finalize cutover strategy

· Develop test plans and test cases

· Build integration test environment

· Build UAT environment

· Develop security roles


· RICE objects, forms and workflows

· Baseline and final configuration

· Converted data

· Unit test plans/scripts

· Cutover strategy and high-level plan

· Integration testing

· Security roles and profiles

· Performance monitoring plan

· Detailed strategy/plan for final prep and UAT

· Company ABC development methodology

· Best practices from Company ABC consultants

· SAP Solution Manager (optional)

· Templates for creating knowledge repository for specific industry.

· Experience in client system and business processes

· CMM Level 5 Quality Processes

Table 3. Business Realization Snapshot

Phase 4: Final Preparation

The final preparation involves validation of the solution design and development, extensive testing across the complete business cycle, user acceptance testing and preparation for Go–live & Support.

Activities during the Final Preparation stage




· Lead UAT

· Assist UAT activities

· Trial cutover

· Prepare for Go-Live including, security profile setup, helpdesk process

· Complete production data conversion

· Completed UAT; including documented test cases/scenarios

· Organization prepared for cutover

· Final configuration guide and support structure

· Impact analysis for “Go/No-Go” decision, including Go-Live success criteria

· Security roles/profile in production environment

· Production data conversion completed


· Company ABC consultants best practices

· Templates from Company ABC

· Checklists

· Use of testing tools like CATT for stress/ volume testing

· Test script templates enabling efficient remote execution

· Online Web-based issue tracker with context search

Table 4. Business Realization Snapshot

Phase 5: Go-live & Support

Go live & support involves transporting the customized system to the production environment and monitoring the live system.

Activities during Go-Live stage




· Execute business and systems cutover

· Activate helpdesk

· Transition to post go-live warranty support

· Finalize project documentation

· Handover to support organization

· Begin continuous improvement process

· Live production system

· Business and systems cutover

· Final configuration guide

· Service model

· Stable production system – acceptance documentation and go-live success checklist

· Production hand-off completed

· Established Procedures to ensure flawless cutover and data migration

· Extended business hours leveraging GDM to provide system support

· Proven handover methodology

Table 5. Go-Live Snapshot

1.2 Company ABC Training Methodology

Training Methodology is an integral part of the ASAP methodology at different phases of the project, namely Blue print, Realization, Final preparation & Go-Live support phases. Company ABC facilitates the Training process for the project but the client is responsible for training the users.

Provided below is the training methodology, that Company ABC follows for all its SAP Implementation/ Rollout engagements. Company ABC proposes a Training spanning across the entire SAP Rollout engagement. However considering the small number of users and already existing template in Dubai, the training activities will be redefined after discussions with Mittal Steel.

Training Project Phases Deliverables



Design Program

Audience analysis

Existing materials review

Hardware/software requirements

Identify tools

Identify standards

Work plan

Training strategy

Team onboarding



Develop Program

Pilot Program

Design Program

Course materials


Job aids

Training environment

Training data

Course schedule

Role/course mapping

Course pilots

Facilities/software tests


End-user registration

Course evaluation form

Administer training data base

Deliver courses

Course evaluations

Post Appraise Program

Provide Ongoing Support

Course evaluation summaries

Recommendations for improvement

Maintenance processes

Maintenance of training materials and data bases

Transition to permanent owners