Implementation cycle

Hello Gurus
Please can u explain for me briefly the processes involved in the following cycles and will i be able to independently learn them or i need to be involved in a project?
Also if u get knowledge on these elements is it something u can add on your resume?
Project preparation, Blueprinting, Realisation, Final Preparation.
MM configurations for a transport industry
rash

Hello Rasham,
<b>Project phases</b>
During the implementation of project, the main activities involves as follow:
The implementation of your SAP System covers the following phases:
<b>Project Preparation</b>
In this phase you plan your project and lay the foundations for successful implementation. It is at this stage that you make the strategic decisions crucial to your project:
- Define your project goals and objectives
- Clarify the scope of your implementation
- Define your project schedule, budget plan, and implementation sequence
- Establish the project organization and relevant committees and assign resources
<b>Business Blueprint</b>
In this phase you create a blueprint using the Question & Answer database (Q&Adb), which documents your enterprise’s requirements and establishes how your business processes and organizational structure are to be represented in the SAP System. You also refine the original project goals and objectives and revise the overall project schedule in this phase.
<b>Realization</b>
In this phase, you configure the requirements contained in the Business Blueprint. Baseline configuration (major scope) is followed by final configuration (remaining scope), which can consist of up to four cycles. Other key focal areas of this phase are conducting integration tests and drawing up end user documentation.
<b>Final Preparation</b>
In this phase you complete your preparations, including testing, end user training, system management, and cutover activities. You also need to resolve all open issues in this phase. At this stage you need to ensure that all the prerequisites for your system to go live have been fulfilled.
<b>Go Live & Support</b>
In this phase you move from a pre-production environment to the live system. The most important elements include setting up production support, monitoring system transactions, and optimizing overall system performance.
Some more information you can find on the following link.
<b>SAP Help</b>
http://help.sap.com/saphelp_47x200/helpdata/en/48/623972d55a11d2bbf700105a5e5b3c/content.htm
<b>SAP Service Marketplace</b>
http://service.sap.com/asap & http://service.sap.com/roadmaps
http://www-rcf.usc.edu/~anthonyb/itp320/ASAP.ppt
http://www.tojet.net/e-book/SAPBook.pdf
http://www.uky.edu/IT/AdminApps/IRISTechPortal/Presentations/Presentations.htm
http://iris.tennessee.edu/sap_project.htm
<b>Preparing Resume</b>
Rasham, Getting knowledge through reading will help you a lot when you really work, but based on theorical knowledge only I suggest you not to put /show as experience in resume. Always keep in mind that Interviewer is smarter than the candidate, Only one-two question is enough to eveluate the candidate, but they will look at you as candidate with some theorical knowledge and ready to work on real if opportunity is provided. So make yourself clear.
Hope this helps.
Regards
Arif Mansuri

Similar Messages

  • What is the implementation cycle for Pharmaceuticals & Chemicals industry

    i am preparing for the interview. could anybody help me by telling the implementation cycle for Pharmaceuticals & Chemicals industry.
    i know the cycle of manufacturing company.
    thank you.

    ASAP Methodology:
    Project Preparation:
    The first step in ASAP is Project Preparation. In this step the Functional Consultant will analyse the business process and define the system for SAP and will give the time line for the project. The Manpower required and the budgets are also considered in this step.
    Blue Print Preparation:
    This is second step in ASAP Methodology. In this step the Project Preparation scenarios are finalised. A out line of the Project is given in this step.
    Realisation:
    In this step actual development is taken place. The ABAPer is responsible for this step.
    Testing:
    In this step the development done by the abaper is being tested. This is the area where the Unit Test Document is prepared (i.e. Positive Testing and Negative Testing).
    GO live and Support:
    This is the final stage where the project is running in the live environment. In this step the bugs if any that are found in the go live procedure are fixed and the project will be considered as support project.
    Rewards if useful.

  • No popup to select active implementation cycle, while creating change Request

    Hi,
    I have two active Implementation projects.
    While creating change requests, it is not giving any popup to select the specific cycle.
    It automatically assigns to newly activated Cycle.
    Please advise.
    Thanks & Best Regards,
    Kiran Sathyan

    Hi,
    if you would mention about sap solution manager version, this critical landscape transport and design before you state the problem, this would saved much time.
    Now I dont think so Popup functions applicable for implentation cycles.
    check out http://help.sap.com/saphelp_sm40/helpdata/en/1a/c39742042fc86ae10000000a155106/frameset.htm
    and regarding closing the project cycle check this out below informations,
    933705 - Closing inconsistent project cycles
    Change Request Management scenario: Usual questions and known errors
    question 10.
    Make sure you closed open tasks, chk in tcode scma
    Thanks
    Jansi

  • Cycle run performance is slow

    We have implemented cycle run group to enable parallel run for cycles which are under the same operating concern. But, the problem is it takes longer time to complete the cycle run. Any one knows how to solve this? ( We want to enable parallel run and at the same time keep the time spend to complete the cycle run). Thanks

    HI,
    search SAPNET, guess you will find for almost all mass process steps in SAP some relevant performance hints.
    Best regards, Christian

  • Authorization Role Practice in Implementation Project

    Gurus,
    Okay, I've been implementing SAP R/3 for around 5 implementation cycles, before realizing my method for creating role may be outdated. I need your advice regarding this.
    Here's my common scenario on every implementation project in realization phase:
    1) Functional Consultants hand over their authorization matrix to me
    The matrix will be the role name to created, along with its transaction code and authorization object.
    There's also user assignment to each role.
    2) I created the role in PFCG.
    Reference, single, composite role. Anything you can build in it.
    3) Map the SAP user to appropriate role
    Now here's the interesting part.
    Users will then be given their own SAP User on UAT phase.
    When they try to do transactions, almost every time, every one of them'll stumble upon "No authorization" error.
    What I do is, check their SU53 object, add corresponding object, then let them test again whether it fixes the error.
    The authorization matrix given by consultants will not have every needed auth. objects.
    It can't be helped. You can't also just put the Full Authorization (*) to object you don't familiar with.
    How do you usually do this?
    Any helpful tools?
    Thanks for help.
    Regards,

    Hi,
    Generally role matrxi should contains every info what eve they needed to create the Role for the functional folks.
    in you case there is some missing things that is interrupting you so better you can focus on Standard SAP roles and study that roles properly before you creating any Customizatio roles.
    so that you will get an idea what are all the objects you have to use to create MM roles and also what are all the objects you have to use to create SD roles etc etc....
    so please try to read the Standard role first before creating the custmoiztion roles.
    -Srini

  • Charms Process in Implementation Project

    Hello Gurus,
    I am part of an implementation project for where we are implementing various functionalities of Solution manager.
    Here we are in the process of implementing CHARMS in the Implementation Phase.
    So I have created a project of type 'Implementation' and has already activated Charms.
    Here the task list is already created and active
    Following are the issues which i am facing while creating a change request.
    1: If I create a change request of type 'SDCR' and authorize the change request, a normal correction of type 'SDMI' gets created automatically. But system throws an error 'No Maintenance cycle is open for the current system'
    I believe for a project of type 'Implementation' ,maintenance cycle doesnt get created, instead an implementation cycle gets created.
    So Let me know if  i have missed out any configuration. or if possible can u suggest me if there is any workaround for this?
    Regards,
    Anubhav

    Hi Raquel,
    Thanks for the reply.
    I have only activated BC Set 'SOLMAN40_CHARM_BASICFUNC_001' prior to activating CHARMS.
    After Activation Charms A project cycle of type 'SDDV' also got created along with the task list.
    But when I try to create a change request of type 'SDCR', it is automatically creating Correction of type 'SDMI'
    Also I had selected the correct Subject option 'Development (Implementation)' in Transaction SDCR
    Am I suppose to activate any other BC set?
    But why is it giving me error related to Maintenance cycle?
    Regards,
    Anubhav

  • Multiple Change Requests for project cycle

    I have a question.. if we have multiple chane requests/documents for a project cycle , how will the project cycle proceed??
    i have two CRs for my implementation cycle , now how should i proceed my implementation cycle, since all the changes are of type SDMJ and i want all my changes to be imported to PRD together??
    Please help

    Hello,
    i had the same problem few weeks ago. I couldn't find the Change request Tab in Solar_project_admin
    I fixed it by following : SAP note : 802793
    The note explain how to re assign the client to manage change request management.
    We folow the note, then the missing tab appear
    Regards

  • SAP R/3 implementation methodologies

    Hi,
    Can any one send me SAP R/3 implementation methodologies Documents and links.
    Thanks & Regards,
    Ram

    hi,
    1
    SAP R/3 Implementation
    at Geneva Pharmaceuticals1
    Company Background
    Geneva Pharmaceuticals, Inc., one of the world’s largest generic drug manufacturers, is the North
    American hub for the Generics division of Swiss pharmaceutical and life sciences company Novartis
    International AG. Originally founded by Detroit pharmacist Stanley Tutag in 1946, Geneva moved
    its headquarters to Broomfield, Colorado in 1974. The company was subsequently acquired by Ciba
    Corporation in 1979, which in 1996, merged with Sandoz Ltd. in the largest ever healthcare merger to
    form Novartis. Alex Krauer, Chairman of Novartis and former Chairman and CEO of Ciba,
    commented on the strengths of the merger:
    “Strategically, the new company moves into a worldwide leadership position in life
    sciences. Novartis holds the number two position in pharmaceuticals,
    number one in crop protection, and has tremendous development potential in
    nutrition.”
    The name “Novartis” comes from the Latin term novae artes or new arts, which eloquently captures
    the company’s corporate vision: “to develop new skills in the science of life.” Novartis inherited,
    from its parent companies, a 200-year heritage of serving consumers in three core business segments:
    healthcare, agribusiness, and nutrition. Business units organized under these divisions are listed in
    Exhibit 1. Today, the Basel (Switzerland) based life sciences company employs 82,500 employees
    worldwide, runs 275 affiliate operations in 142 countries, and generates annual revenues of 32 billion
    Swiss Francs. Novartis’ key financial data for the last five years (1994-98) are presented in Exhibit 2.
    The company’s American Depository Receipts trade on the New York Stock Exchange under the
    ticker symbol NVTSY.
    Novartis’ global leadership in branded pharmaceuticals is complemented by its generic drugs
    division, Novartis Generics. This division is headquartered in Kundl (Austria), and its U.S.
    operations are managed by Geneva Pharmaceuticals. In 1998, Geneva had revenues of $300 million,
    employed nearly 1000 employees, and manufactured over 4.6 billion dosage units of generic drugs.
    1 This “freeware” case was written by Dr. Anol Bhattacherjee to serve as a basis for class discussion rather than
    to demonstrate the effective or ineffective handling of an administrative or business situation. The author is
    grateful to Randy Weldon, CIO of Geneva Pharmaceuticals, and his coworkers for their unfailing help
    throughout the course of this project. This case can be downloaded and distributed free of charge for non-profit
    or academic use, provided the contents are unchanged and this copyright notice is clearly displayed. No part of
    this case can be used by for-profit organizations without the express written consent of the author. This case
    also cannot be archived on any web site that requires payment for access. Copyright © 1999 by Anol
    Bhattacherjee. All rights reserved.
    ERP Implementation at Geneva Pharmaceuticals 2
    Geneva portfolio currently includes over 200 products in over 500 package sizes, covering a wide
    range of therapeutic categories, such as nervous system disorders, cardio-vascular therapies, and
    nonsteroidal anti-inflammatory drugs. Its major products include ranitidine, atenolol, diclofenac
    sodium, ercaf, metoprolol tartrate, triamterene with hydrochlorothiazide, and trifluoperazine.
    Geneva’s business and product information can be obtained from the company web site at
    www.genevaRx.com.
    Generic drugs are pharmaceutically and therapeutically equivalent versions of brand name drugs with
    established safety and efficacy. For instance, acetaminophen is the equivalent of the registered brand
    name drug Tylenolâ, aspirin is equivalent of Ecotrinâ, and ranitidine HCl is equivalent of Zantacâ.
    This equivalence is tested and certified within the U.S. by the Food and Drug Administration (FDA),
    following successful completion of a “bioequivalence study,” in which the blood plasma levels of the
    active generic drug in healthy people are compared with that of the corresponding branded drug.
    Geneva’s business strategy has emphasized growth in two ways: (1) focused growth over a select
    range of product types, and (2) growth via acquisitions. Internal growth was 14 percent in 1998,
    primarily due to vigorous growth in the penicillin and cephalosporin businesses. In pursuit of further
    growth, Geneva spend $52 million in 1997 to upgrade its annual manufacturing capacity to its current
    capacity of 6 billion units, and another $23 million in 1998 in clinical trials and new product
    development.
    Industry and Competitive Position
    The generic drug manufacturing industry is fragmented and highly competitive. In 1998, Geneva was
    the fifth largest player in this industry, up from its eighth rank in 1997 but still below its second rank
    in 1996. The company’s prime competitors fall into three broad categories: (1) generic drugs
    divisions of major branded drug companies (e.g., Warrick – a division of Schering-Plough and
    Apothecon – a division of Bristol Myers Squibb), (2) independent generic drug manufacturers (e.g.,
    Mylan, Teva Pharmaceuticals, Barr Laboratories, and Watson Pharmaceuticals), and (3) drug
    distributors vertically integrating into generics manufacturing (e.g., AndRx). The industry also has
    about 200 smaller players specializing in the manufacture of niche generic products. While Geneva
    benefited from the financial strength of Novartis, independent companies typically used public stock
    markets for funding their growth strategies.
    In 1998, about 45 percent of prescriptions for medications in the U.S. were filled with generics. The
    trend toward generics can be attributed to the growth of managed care providers such as health
    maintenance organizations (HMO), who generally prefer lower cost generic drugs to more expensive
    brand name alternatives (generic drugs typically cost 30-50 less than equivalent brands). However,
    no single generics manufacturer has benefited from this trend, because distributors and pharmacies
    view generic products from different manufacturers as identical substitutes and tend to
    “autosubstitute” or freely replace generics from one company with those from another based on
    product availability and pricing at that time. Once substituted, it is very difficult to regain that
    customer account because pharmacies are disinclined to change product brand, color, and packaging,
    to avoid confusion among consumers. In addition, consumer trust toward generics has remained
    lower, following a generic drug scandal in the early 1990’s (of which Geneva was not a part).
    ERP Implementation at Geneva Pharmaceuticals 3
    Margins in the generics sector has therefore remained extremely low, and there is a continuous
    pressure on Geneva and its competitors to reduce costs of operations.
    Opportunities for international growth are limited because of two reasons. First, consumers in some
    countries such as Mexico are generally skeptical about the lack of branding because of their cultural
    background. Second, U.S. generics manufacturers are often undercut by competitors from India and
    China, where abundance of low-cost labor and less restrictive regulatory requirements (e.g., FDA
    approval) makes drug manufacturing even less expensive.
    Continuous price pressures has resulted in a number of recent industry mergers and acquisitions in the
    generic drugs sector in recent years, as the acquirers seek economies of scale as a means of reducing
    costs. The search for higher margins has also led some generics companies to venture into the
    branded drugs sector, providing clinical trials, research and development, and additional
    manufacturing capacity for branded drugs on an outsourced basis.
    Major Business Processes
    Geneva’s primary business processes are manufacturing and distribution. The company’s
    manufacturing operations are performed at a 600,000 square foot facility in Broomfield (Colorado),
    while its two large distribution centers are located in Broomfield and Knoxville (Tennessee).
    Geneva’s manufacturing process is scientific, controlled, and highly precise. A long and rigorous
    FDA approval process is required prior to commercial production of any drug, whereby the exact
    formulation of the drug or its “recipe” is documented. Raw materials are sourced from suppliers
    (sometimes from foreign countries such as China), tested for quality (per FDA requirements),
    weighed (based on dosage requirements), granulated (i.e., mixed, wetted, dried, milled to specific
    particle sizes, and blended to assure content uniformity), and compressed into a tablet or poured into a
    gelatinous capsule. Some products require additional coatings to help in digestion, stabilizing,
    regulating the release of active ingredients in the human body, or simply to improve taste. Tablets or
    capsules are then imprinted with the Geneva logo and a product identification number. Following a
    final inspection, the medications are packaged in childproof bottles with a distinctive Geneva label, or
    inserted into unit-dose blister packs for shipment.
    Manufacturing is done in batches, however, the same batch can be split into multiple product types
    such as tablets and capsules, or tablets of different dosages (e.g., 50 mg and 100 mg). Likewise,
    finished goods from a batch can be packaged in different types of bottles, based on customer needs.
    These variations add several layers of complexity to the standard manufacturing process and requires
    tracking of three types of inventory: raw materials, bulk materials, and finished goods, where bulk
    materials represent the intermediate stage prior to packaging. In some cases, additional intermediates
    such as coating solution is also tracked. Master production scheduling is focused on the manufacture
    of bulk materials, based on forecasted demand and replenishment of “safety stocks” at the two
    distribution centers. Finished goods production depends on the schedule-to-performance, plus
    availability of packaging materials (bottles and blister packs), which are sourced from outside
    vendors.
    ERP Implementation at Geneva Pharmaceuticals 4
    Bulk materials and finished goods are warehoused in Broomfield and Knoxville distribution centers
    (DC) prior to shipping. Since all manufacturing is done was done at Broomfield, inventory
    replenishment of manufactured products is done first at Broomfield and then at Knoxville. To meet
    additional customer demand, Geneva also purchases finished goods from smaller manufacturers, who
    manufacture and package generic drugs under Geneva’s level. Since most of these outsourcers are
    located along the east coast, and hence, they are distributed first to the Knoxville and then to
    Broomfield. Purchasing is simpler than manufacturing because it requires no bill of materials, no
    bulk materials management, and no master scheduling; Geneva simply converts planned orders to
    purchase requisitions, and then to purchase orders, that are invoiced upon delivery. However, the
    dual role of manufacturing and purchasing is a difficult balancing task, as explained by Joe Camargo,
    Director of Purchasing and Procurement:
    “Often times, we are dealing with more than a few decision variables. We have to
    look at our forecasts, safety stocks, inventory on hand, and generate a replenishment
    plan. Now we don’t want to stock too much of a finished good inventory because that
    will drive up our inventory holding costs. We tend to be a little more generous on the
    raw materials side, since they are less costly than finished goods and have longer
    shop lives. We also have to factor in packaging considerations, since we have a
    pretty short lead time on packaging materials, and capacity planning, to make sure
    that we are making efficient use of our available capacity. The entire process is
    partly automated and partly manual, and often times we are using our own
    experience and intuition as much as hard data to make a good business decision.”
    Geneva supplies to a total of about 250 customers, including distributors (e.g., McKesson, Cardinal,
    Bergen), drugstore chains (e.g., Walgreen, Rite-Aid), grocery chains with in-store pharmacies (e.g.,
    Safeway, Kroger), mail order pharmacies (e.g., Medco, Walgreen), HMOs (e.g., Pacificare, Cigna),
    hospitals (e.g., Columbia, St. Luke’s), independent retail pharmacies, and governmental agencies
    (e.g., U.S. Army, Veterans Administration, Federal prisons). About 70 percent of Geneva’s sales
    goes to distributors, another 20 percent goes to drugstore chains, while HMOs, government, retail
    pharmacies, and others account for the remaining 10 percent. Distributors purchase generic drugs
    wholesale from Geneva, and then resell them to retail and mail order pharmacies, who are sometimes
    direct customers of Geneva. The volume and dollar amount of transaction vary greatly from one
    customer to another, and while distributors are sometimes allow Geneva some lead time to fulfill in a
    large order, retail pharmacies typically are unwilling to make that concession.
    One emerging potential customer segment is Internet-based drug retailers such as Drugstore.com and
    PlanetRx.com. These online drugstores do not maintain any inventory of their own, but instead
    accept customer orders and pass on those orders to any wholesaler or manufacturer that can fill those
    orders in short notice. These small, customized, and unpredictable orders do not fit well with
    Geneva’s wholesale, high-volume production strategy, and hence, the company has decided against
    direct retailing to consumers via mail order or the Internet, at least for the near future.
    As is standard in the generics industry, Geneva uses a complex incentive system consisting of
    “rebates” and “chargebacks” to entice distributors and pharmacies to buy its products. Each drug is
    assigned a “published industry price” by industry associations, but Geneva rebates that price to
    distributors on their sales contracts. For instance, if the published price is $10, and the rebates
    assigned to a distributor is $3, then the contract price on that drug is $7. Rebate amounts are
    ERP Implementation at Geneva Pharmaceuticals 5
    determined by the sales management based on negotiations with customers. Often times, customers
    get proposals to buy the product cheaper from a different manufacturer and ask Geneva for a
    corresponding discount. Depending on how badly Geneva wants that particular customer or push that
    product, it may offer a rebate or increase an existing rebate. Rebates can vary from one product to
    another (for the same customer) and/or from one order volume to another (for the same product).
    Likewise, pharmacies ordering Geneva’s products are paid back a fraction of the sales proceeds as
    chargebacks.
    The majority of Geneva’s orders come through EDI. These orders are passed though multiple filters
    in an automated order processing system to check if the customer has an active customer number and
    sufficient credit, if the item ordered is correct and available in inventory. Customers are then
    assigned to either the Broomfield or Knoxville DC based on quantity ordered, delivery expiration
    dates, and whether the customer would accept split lots. If the quantity ordered is not available at the
    primary DC (say, Knoxville), a second allocation is made to the secondary DC (Broomfield, in this
    case). If the order cannot be filled immediately, a backorder will be generated and the Broomfield
    manufacturing unit informed of the same. Once filled, the distribution unit will print the order and
    ship it to the customer, and send order information to accounts receivable for invoicing. The overall
    effectiveness of the fulfillment process is measured by two customer service metrics: (1) the ratio
    between the number of lines on the order that can be filled immediately (partial fills allowed) to the
    total number of lines ordered by the customer (called “firstfill”), and (2) the percentage of items send
    from the primary DC. Fill patterns are important because customers typically prefer to get all items
    ordered in one shipment.
    Matching customer demand to production schedules is often difficult because of speculative buying
    on the part of customers. Prices of drugs are typically reassessed at the start of every fiscal year, and
    a distributor may place a very large order at the end of the previous year to escape a potential price
    increase at the start of the next year (these products would then be stockpiled for reselling at higher
    prices next year). Likewise, a distributor may place a large order at the end of its financial year to
    transfer cash-on-hand to cost-of-goods-sold, for tax purposes or to ward off a potential acquisition
    threat. Unfortunately, most generics companies do not have the built-in capacity to deliver such
    orders within short time frames, yet inability to fulfill orders may lead to the loss of an important
    customer. Safety stocks help meet some of these unforeseen demands, however maintaining such
    inventory consumes operating resources and reduce margins further.
    SAP R/3 Implementation
    Up until 1996, Geneva’s information systems (IS) consisted of a wide array of software programs for
    running procurement, manufacturing, accounting, sales, and other mission-critical processes. The
    primary hardware platform was IBM AS/400, running multiple operational databases (mostly DB/2)
    and connected to desktop microcomputers via a token-ring local area network (LAN). Each business
    unit had deployed applications in an ad hoc manner to meet its immediate needs, which were
    incompatible across business units. For instance, the manufacturing unit (e.g., materials requirements
    planning) utilized a manufacturing application called MacPac, financial accounting used
    Software/2000, and planning/budgeting used FYI-Planner. These systems were not interoperable,
    and data that were shared across systems (e.g., accounts receivable data was used by order
    ERP Implementation at Geneva Pharmaceuticals 6
    management and financial accounting packages, customer demand was used in both sales and
    manufacturing systems) had to be double-booked and rekeyed manually. This led to higher incidence
    of data entry errors, higher costs of error processing, and greater data inconsistency. Further, data
    was locked within “functional silos” and were unable to support processes that cut across multiple
    business units (e.g., end-to-end supply chain management). It was apparent that a common,
    integrated company-wide solution would not only improve data consistency and accuracy, but also
    reduce system maintenance costs (e.g., data reentry and error correction) and enable implementation
    of new value-added processes across business units.
    In view of these limitations, in 1996, corporate management at Geneva initiated a search for
    technology solutions that could streamline its internal processes, lower costs of operations, and
    strategically position the company to take advantage of new value-added processes. More
    specifically, it wanted an enterprise resource planning (ERP) software that could: (1) implement best
    practices in business processes, (2) provide operational efficiency by integrating data across business
    units, (3) reduce errors due to incorrect keying or rekeying of data, (4) reduce system maintenance
    costs by standardizing business data, (5) be flexible enough to integrate with new systems (as more
    companies are acquired), (6) support growth in product and customer categories, and (7) is Y2K (year
    2000) compliant. The worldwide divisions of Novartis were considering two ERP packages at that
    time: BPCS from Software Systems Associates and R/3 system from SAP. Eventually, branded drug
    divisions decided to standardize their data processing environment using BPCS, and generics agreed
    on deploying R/3.2 A brief description of the R/3 software is provided in the appendix.
    R/3 implementation at Geneva was planned in three phases (see Exhibit 3). Phase I focused on the
    supply side processes (e.g., manufacturing requirements planning, procurement planning), Phase II
    was concerned with demand side processes (e.g., order management, customer service), and the final
    phase was aimed at integrating supply side and demand side processes (e.g., supply chain
    management). Randy Weldon, Geneva’s Chief Information Officer, outlined the goals of each phase
    as:
    “In Phase I, we were trying to get better performance-to-master production schedule
    and maybe reduce our cost of operations. Our Phase II goals are to improve sales
    and operations planning, and as a result, reduce back orders and improve customer
    service. In Phase III, we hope to provide end-to-end supply chain integration, so that
    we can dynamically alter our production schedules to fluctuating demands from our
    customers.”
    For each phase, specific R/3 modules were identified for implementation. These modules along with
    implementation timelines are listed in Exhibit 3. The three phases are described in detail next.
    2 However, each generics subsidiary had its own SAP R/3 implementation, and therefore data sharing across
    these divisions remained problematic.
    ERP Implementation at Geneva Pharmaceuticals 7
    Phase I: Supply Side Processes
    The first phase of R/3 implementation started on November 1, 1997 with the goal of migrating all
    supply-side processes, such as purchasing management, capacity planning, master scheduling,
    inventory management, quality control, and accounts payable from diverse hardware/software
    platforms to a unified R/3 environment. These supply processes were previously very manual and
    labor intensive. A Macpac package running on an IBM AS/400 machine was used to control shop
    floor operations, prepare master schedules, and perform maintenance management. However, the
    system did not have simulation capability to run alternate production plans against the master
    schedule, and was therefore not used for estimation. The system also did not support a formal process
    for distribution resource planning (DRP), instead generated a simple replenishment schedule based on
    predefined economic order quantities. Materials requirements planning (MRP) was only partially
    supported in that the system generated production requirements and master schedule but did not
    support planned orders (e.g., generating planned orders, checking items in planned orders against the
    inventory or production plan, converting planned orders to purchase orders or manufacturing orders).
    Consequently, entering planned orders, checking for errors, and performing order conversion were all
    entered manually, item by item, by different sales personnel (which left room for rekeying error).
    Macpac did have a capacity resource planning (CRP) functionality, but this feature was not used since
    it required heavy custom programming and major enhancements to master data. The system had
    already been so heavily customized over the years, that even a routine system upgrade was considered
    too unwieldy and expensive. Most importantly, the existing system did not position Geneva well for
    the future, since it failed to accommodate consigned inventory, vendor-managed inventory, paperless
    purchasing, and other innovations in purchasing and procurement that Geneva wanted to implement.
    The objectives of Phase I were therefore to migrate existing processes from Macpac to R/3, automate
    supply side process not supported by MacPac, and integrate all supply-side data in a single, real-time
    database so that the synergies could be exploited across manufacturing and purchasing processes.
    System integration was also expected to reduce inventory and production costs, improve
    performance-to-master scheduling, and help managers make more optimal manufacturing and
    purchase decisions. Since R/3 would force all data to be entered only once (at source by the
    appropriate shop floor personnel), the need of data reentry would be eliminated, and hence costs of
    data reconciliation would be reduced. The processes to be migrated from MacPac (e.g., MRP,
    procurement) were fairly standardized and efficient, and were hence not targeted for redesign or
    enhancement. Three SAP modules were scheduled for deployment: materials management (MM),
    production planning (PP), and accounts payable component of financial accounting (FI). Exhibit A-1
    in Appendix provides brief descriptions of these and other commonly referenced R/3 modules.
    Phase I of R/3 implementation employed about ten IS personnel, ten full-time users, and ten part-time
    users from business units within Geneva. Whitman-Hart, a consulting company with prior experience
    in R/3 implementation, was contracted to assist with the migration effort. These external consultants
    consisted of one R/3 basis person (for implementing the technical core of the R/3 engine), three R/3
    configurators (for mapping R/3 configuration tables in MM, PP, and FI modules to Geneva’s needs),
    and two ABAP programmers (for custom coding unique requirements not supported by SAP). These
    consultants brought in valuable implementation experience, which was absolutely vital, given that
    Geneva had no in-house expertise in R/3 at that time. Verne Evans, Director of Supply Chain
    Management and a “super user” of MacPac, was assigned the project manager for this phase. SAP’s
    ERP Implementation at Geneva Pharmaceuticals 8
    rapid implementation methodology called Accelerated SAP (ASAP) was selected for deployment,
    because it promised a short implementation cycle of only six months.3
    Four months later, Geneva found that little progress had been made in the implementation process
    despite substantial investments on hardware, software, and consultants. System requirements were
    not defined correctly or in adequate detail, there was little communication or coordination of activities
    among consultants, IS personnel, and user groups, and the project manager was unable to identify or
    resolve problems because he had no prior R/3 experience. In the words of a senior manager, “The
    implementation was clearly spinning out of control.” Consultants employed by Whitman-Hart were
    technical specialists, and had little knowledge of the business domain. The ASAP methodology
    seemed to be failing, because although it allowed a quick canned implementation, it was not flexible
    enough to meet Geneva’s extensive customization needs, did not support process improvements, and
    alienated functional user groups from system implementation. To get the project back into track and
    give it leadership and direction, in February 1998, Geneva hired Randy Weldon as its new CIO.
    Weldon brought in valuable project management experience in R/3 from his previous employer,
    StorageTek.4
    From his prior R/3 experience, Weldon knew that ERP was fundamentally about people and process
    change, rather than about installing and configuring systems, and that successful implementation
    would require the commitment and collaboration of all three stakeholder groups: functional users, IS
    staff, and consultants. He instituted a new project management team, consisting of one IS manager,
    one functional manager, and one senior R/3 consultant. Because Geneva’s internal IS department had
    no R/3 implementation experience, a new team of R/3 professionals (including R/3 basis personnel
    and Oracle database administrators) was recruited. Anna Bourgeois, with over three years of R/3
    experience at Compaq Computers, was brought in to lead Geneva’s internal IS team. Weldon was not
    particularly in favor of Whitman-Hart or the ASAP methodology. However, for project expediency,
    he decided to continue with Whitman-Hart and ASAP for Phase 1, and explore other options for
    subsequent phases.
    By February 1999, the raw materials and manufacturing component of R/3’s MM module was “up
    and running.” But this module was not yet integrated with distribution (Phase II) and therefore did
    not have the capability to readjust production runs based on current sales data. However, several
    business metrics such as yield losses and key performance indicators showed performance
    improvement following R/3 implementation. For instance, the number of planning activities
    performed by a single individual was doubled. Job roles were streamlined, standardized, and
    consolidated, so that the same person could perform more “value-added” activities. Since R/3
    eliminated the need for data rekeying and validating, the portion of the inventory control unit that
    dealt with data entry and error checking was disbanded and these employees were taught new skills
    for reassignment to other purchasing and procurement processes. But R/3 also had its share of
    disappointments, as explained by Camargo:
    3 ASAP is SAP’s rapid implementation methodology that provides implementers a detailed roadmap of the
    implementation life cycle, grouped into five phases: project preparation, business blueprint, realization, final
    preparation, and go live. ASAP provides a detailed listing of activities to be performed in each phase,
    checklists, predefined templates (e.g., business processes, cutover plans), project management tools,
    questionnaires (e.g., to define business process requirements), and a Question & Answer Database
    4 StorageTek is a leading manufacturer of magnetic tape and disk components also based in Colorado.
    ERP Implementation at Geneva Pharmaceuticals 9
    “Ironically, one of the problems we have with SAP, that we did not have with
    Macpac, is for the job to carry the original due date and the current due date, and
    measure production completion against the original due date. SAP only allows us to
    capture one due date, and if we change the date to reflect our current due date, that
    throws our entire planning process into disarray. To measure how we are filling
    orders, we have to do that manually, offline, on a spreadsheet. And we can’t record
    that data either in SAP to measure performance improvements over time.”
    Bourgeois summed up the implementation process as:
    “Phase I, in my opinion, was not done in the most effective way. It was done as
    quickly as possible, but we did not modify the software, did not change the process,
    or did not write any custom report. Looking back, we should have done things
    differently. But we had some problems with the consultants, and by the time I came
    in, it was a little too late to really make a change. But we learned from these
    mistakes, and we hope to do a better job with Phases II and III.”
    Phase II: Demand Side Processes
    Beginning around October 1998, the goals of the second phase were to redesign demand-side
    processes such as marketing, order fulfillment, customer sales and service, and accounts receivable,
    and then implement the reengineered processes using R/3. Geneva was undergoing major business
    transformations especially in the areas of customer sales and service, and previous systems (Macpac,
    FYI Planner, etc.) were unable to accommodate these changes. For instance, in 1998, Geneva started
    a customer-based forecasting process for key customer accounts. It was expected that a better
    prediction of order patterns from major customers would help the company improve its master
    scheduling, while reducing safety stock and missed orders. The prior forecasting software, FYI
    Planner, did not allow forecasting on a customer-by-customer basis. Besides, demand-side processes
    suffered from similar lack of data integration and real-time access as supply side processes, and R/3
    implementation, by virtue of its real-time integration of all operational data would help manage crossfunctional
    processes better. Mark Mecca, Director of Customer Partnering, observed:
    “Before SAP, much of our customer sales and service were managed in batch mode
    using MacPac. EDI orders came in once a night, chargebacks came in once a day,
    invoicing is done overnight, shipments got posted once a day; so you don’t know
    what you shipped for the day until that data was entered the following day. SAP will
    allow us to have access to real-time data across the enterprise. There will be
    complete integration with accounting, so we will get accurate accounts receivable
    data at the time a customer initiates a sales transaction. Sometime in the future,
    hopefully, we will have enough integration with our manufacturing processes so that
    we can look at our manufacturing schedule and promise a customer exactly when we
    can fill his order.”
    However, the second phase was much more challenging than the first phase, given the non-standard
    and inherently complex nature of Geneva’s sales and service processes. For instance, customer rebate
    ERP Implementation at Geneva Pharmaceuticals 10
    percentages varied across customers, customer-product combinations, and customer-product-order
    volume combinations. Additionally, the same customer sometimes had multiple accounts with
    Geneva and had a different rebate percentage negotiated for each account.
    Bourgeois was assigned overall responsibility of the project, by virtue of her extensive knowledge of
    EDI, R/3 interface conversion, and sales and distribution processes, and ability to serve as a technical
    liaison between application and basis personnel. Whitman-Hart was replaced with a new consulting
    firm, Arthur Andersen Business Consulting, to assist Geneva with the second and third phases of R/3
    implementation. Oliver White, a consulting firm specializing in operational processes for
    manufacturing firms, was also hired to help redesign existing sales and distribution processes using
    “best practices,” prior to R/3 implementation. Weldon explained the reason for hiring two consulting
    groups:
    “Arthur Anderson was very knowledgeable in the technical and configurational
    aspects of SAP implementation, but Oliver White was the process guru. Unlike
    Phase I, we were clearly targeting process redesign and enhancement in Phases II
    and III, and Oliver White brought in ‘best practices’ by virtue of their extensive
    experience with process changes in manufacturing organizations. Since Phase I was
    somewhat of a disaster, we wanted to make sure that we did everything right in
    Phases II and III and not skimp on resources.”
    Technical implementation in Phase II proceeded in three stages: conceptual design, conference room
    pilot, and change management. In the conceptual design stage, key users most knowledgeable with
    the existing process were identified, assembled in a room, and interviewed, with assistance from
    Oliver White consultants. Process diagrams were constructed on “post-it” notes and stuck to the
    walls of a conference room for others to view, critique, and suggest modifications. The scope and
    boundaries of existing processes, inputs and deliverables of each process, system interfaces, extent of
    process customization, and required level of system flexibility were analyzed. An iterative process
    was employed to identify and eliminate activities that did not add value, and generate alternative
    process flows. The goal was to map the baseline or existing (“AS-IS”) processes, identify bottlenecks
    and problem areas, and thereby, to create reengineered (“TO-BE”) processes. This information
    became the basis for subsequent configuration of the R/3 system in the conference room pilot stage.
    A core team of 20 IS personnel, users, and consultants worked full-time on conceptual design for 2.5
    months (this team later expanded to 35 members in the conference room pilot stage). Another 30
    users were involved part-time in this effort; these individuals were brought in for focused periods of
    time (between 4 and 14 hours) to discuss, clarify, and agree on complex distribution-related issues.
    The core team was divided into five groups to examine different aspects of the distribution process:
    (1) product and business planning, (2) preorder (pricing, chargebacks, rebates, contracts, etc.), (3)
    order processing, (4) fulfillment (shipping, delivery confirmation, etc.), and (5) post-order (accounts
    receivable, credit management, customer service, etc.). Thirteen different improvement areas were
    identified, of which four key areas emerged repeatedly from cross-functional analysis by the five
    groups and were targeted for improvement: product destruction, customer dispute resolution, pricing
    strategy, and service level. Elaborate models were constructed (via fish bone approach) for each of
    these four areas to identify what factors drove these areas, what was the source of problems in these
    areas, and how could they be improved using policy initiatives.
    ERP Implementation at Geneva Pharmaceuticals 11
    The conceptual design results were used to configure and test prototype R/3 systems for each of the
    four key improvement areas in the conference room pilot stage. The purpose of the prototypes was to
    test and refine different aspects of the redesigned processes such as forecast planning, contract
    pricing, chargeback strategy determination, receivables creation, pre-transaction credit checking,
    basic reporting, and so forth in a simulated environment. The prototypes were modified several times
    based on user feedback, and the final versions were targeted for rollout using the ASAP methodology.
    In the change management stage, five training rooms were equipped with computers running the
    client version of the R/3 software to train users on the redesigned processes and the new R/3
    environment. An advisory committee was formed to oversee and coordinate the change management
    process. Reporting directly to the senior vice president level, this committee was given the mandate
    and resources to plan and implement any change strategies that they would consider beneficial. A
    change management professional and several trainers were brought in to assist with this effort.
    Multiple “brown bag luncheons” were organized to plan out the course of change and discuss what
    change strategies would be least disruptive. Super users and functional managers, who had the
    organizational position to influence the behaviors of colleagues or subordinates in their respective
    units, were identified and targeted as potential change agents. The idea was to seed individual
    business units with change agents they could trust and relate to, in an effort to drive a grassroots
    program for change.
    To stimulate employee awareness, prior to actual training, signs were put up throughout the company
    that said, “Do you know that your job is changing?” Company newsletters were used to enhance
    project visibility and to address employee questions or concerns about the impending change. A
    separate telephone line was created for employees to call anytime and inquire about the project and
    how their jobs would be affected. The human resources unit conducted an employee survey to
    understand how employees viewed the R/3 implementation and gauge their receptivity to changes in
    job roles as a result of this implementation.
    Training proceeded full-time for three weeks. Each user received an average of 3-5 days of training
    on process and system aspects. Training was hands-on, team-oriented, and continuously mentored,
    and was oriented around employees’ job roles such as how to process customer orders, how to move
    inventory around, and how to make general ledger entries, rather than how to use the R/3 system.
    Weldon described the rationale for this unique, non-traditional mode of training:
    “Traditional system training does not work very well for SAP implementation
    because this is not only a technology change but also a change in work process,
    culture, and habits, and these are very difficult things to change. You are talking
    about changing attitudes and job roles that have been ingrained in employees’ minds
    for years and in some cases, decades. System training will overwhelm less
    sophisticated users and they will think, ‘O my God, I have no clue what this computer
    thing is all about, I don’t know what to do if the screen freezes, I don’t know how to
    handle exceptions, I’m sure to fail.’ Training should not focus on how they should
    use the system, but on how they should do their own job using the system. In our
    case, it was a regular on-the-job training rather than a system training, and
    employees approached it as something that would help them do their job better.”
    ERP Implementation at Geneva Pharmaceuticals 12
    Several startling revelations were uncovered during the training process. First, there was a
    considerable degree of confusion among employees on what their exact job responsibilities were,
    even in the pre-R/3 era. Some training resources had to be expended in reconciling these differences,
    and to eliminate ambiguity about their post-implementation roles. Second, Geneva’s departments
    were very much functionally oriented and wanted the highest level of efficiency from their
    department, sometimes to the detriment of other departments or the overall process. This has been a
    sticky cultural problem, and at the time of the case, the advisory committee was working with senior
    management to see if any structural changes could be initiated within the company to affect a mindset
    change. Third, Geneva realized that change must also be initiated on the customer side, so that
    customers are aware of the system’s benefits and are able to use it appropriately. In the interest of
    project completion, customer education programs were postponed until the completion of Phase III of
    R/3 implementation.
    The primary business metric tracked for Phase II implementation was customer service level, while
    other metrics included days of inventory on hand, dollar amount in disputes, dollar amount destroyed,
    and so forth. Customer service was assessed by Geneva’s customers as: (1) whether the item ordered
    was in stock, (2) whether Geneva was able to fill the entire order in one shipment, and (3) if
    backordered, whether the backorder delivered on time. With a customer service levels in the 80’s,
    Geneva has lagged its industry competitors (mostly in the mid 90’s), but has set an aggressive goal to
    exceed 99.5 percent service level by year-end 1999. Camargo observed that there was some decrease
    in customer service, but this decrease was not due to R/3 implementation but because Geneva faced
    an impending capacity shortfall and the planners did not foresee the shortfall quickly enough to
    implement contingency plans. Camargo expected that such problems would be alleviated as
    performance-to-schedule and demand forecasting improved as a result of R/3 implementation. Given
    that Phase II implementation is still underway at the time of the case (“go live” date is February 1,
    2000), it is still too early to assess whether these targets are reached.
    Phase 3: Integrating Supply and Demand
    Geneva’s quest for integrating supply and demand side processes began in 1994 with its supply chain
    management (SCM) initiative. But the program was shelved for several years due to the nonintegrated
    nature of systems, immaturity of the discipline, and financial limitations. The initiative
    resurfaced on the planning boards in 1998 under the leadership of Verne Evans, Director of SCM, as
    R/3 promised to remove the technological bottlenecks that prevented successful SCM
    implementation. Though SCM theoretically extends beyond the company’s boundaries to include its
    suppliers and customers, Geneva targeted the mission-critical the manufacturing resource planning
    (MRP-II) component within SCM, and more specifically, the Sales and Operations Planning (SOP)
    process as the means of implementing “just-in-time” production scheduling. SOP dynamically linked
    planning activities in Geneva’s upstream (manufacturing) and downstream (sales) operations,
    allowing the company to continuously update its manufacturing capacity and scheduling in response
    to continuously changing customer demands (both planned and unanticipated). Geneva’s MRP-II and
    SOP processes are illustrated in Exhibits 5 and 6 respectively.
    Until the mid-1990’s, Geneva had no formal SOP process, either manual or automated.
    Manufacturing planning was isolated from demand data, and was primarily based on historical
    ERP Implementation at Geneva Pharmaceuticals 13
    demand patterns. If a customer (distributor) placed an unexpected order or requested a change in an
    existing order, the manufacturing unit was unable to adjust their production plan accordingly. This
    lack of flexibility led to unfilled orders or excess inventory and dissatisfied (and sometimes lost)
    customers. Prior sales and manufacturing systems were incompatible with each other, and did not
    allow the integration of supply and demand data, as required by SOP. In case production plans
    required modification to accommodate a request from a major customer, such decisions were made on
    an ad-hoc basis, based on intuition rather than business rationale, which sometimes had adverse
    repercussions on manufacturing operations.
    To remedy these problems, Geneva started a manual SOP process in 1997 (see Exhibit 6). In this
    approach, after the financial close of each month, sales planning and forecast data were aggregated
    from order entry and forecasting systems, validated, and manually keyed into master scheduling and
    production planning systems. Likewise, prior period production and inventory data were entered into
    order management systems. The supply planning team and demand analysis team arrived at their
    own independent analysis of what target production and target sales should be. These estimates
    (likely to be different) were subsequently reviewed in a joint meeting of demand analysts and master
    schedulers and reconciliated. Once an agreement was reached, senior executives (President of
    Geneva and Senior Vice Presidents), convened a business planning meeting, where the final
    production plan and demand schedule were analyzed based on business assumptions, key customers,
    key performance indicators, financial goals and projections (market share, revenues, profits), and
    other strategic initiatives (e.g., introduction of a new product). The purpose of this final meeting was
    not only to fine-tune the master schedule, but also to reexamine the corporate assumptions, growth
    estimates, and the like in light of the master schedule, and to develop a better understanding of the
    corporate business. The entire planning process took 20 business days (one month), of which the first
    10 days were spent in data reentry and validation across corporate systems, followed by five days of
    demand planning, two days of supply planning, and three days of reconciliation. The final business
    planning meeting was scheduled on the last Friday of the month to approve production plans for the
    following month. Interestingly, when the planning process was completed one month later, the
    planning team had a good idea of the production schedule one month prior. If Geneva decided to
    override the targeted production plans to accommodate a customer request, such changes undermined
    the utility of the SOP process.
    While the redesigned SOP process was a major improvement over the pre-SOP era, the manual
    process was itself limited by the time-lag and errors in data reentry and validation across sales,
    production, and financial systems. Further, the process took one month, and was not sensitive to
    changes in customer orders placed less than a month from their requested delivery dates. Since much
    of the planning time was consumed in reentering and validating data from one system to another,
    Evans estimated that if an automated system supported real-time integration of all supply and demand
    data in a single unified database, the planning cycle could be reduced to ten business days.
    Though SAP provided a SOP module with their R/3 package, Geneva’s R/3 project management team
    believed that this module lacked the “intelligence” required to generate an “optimal” production plan
    from continuously changing supply and demand data, even when all data were available in a common
    database. The R/3 system was originally designed as a data repository, not an analysis tool to solve
    ERP Implementation at Geneva Pharmaceuticals 14
    complex supply chain problems or provide simulation capabilities5. Subsequently, in 1999, when
    SAP added a new Advanced Purchase Optimizer (APO) module to help with data analysis, Geneva
    realized that the combination of R/3’s SOP and APO modules would be the answer to their unique
    SOP needs.
    At the time of the case, Geneva was in the initial requirements definition stage of SOP
    implementation. To aid in this effort, Oliver White had created a template that could aggregate all
    relevant data required for SOP from distribution, operations, purchasing, quality control, and other
    functional databases, and tie these data to their source processes. It was expected that the template
    would provide a common reference point for all individuals participating in the SOP process and
    synchronize their decision processes.
    The primary business metric targeted for improvement in Phase III implementation is “available to
    promise” (ATP), i.e., whether Geneva is able to fulfill a customer order by the promised time. ATP is
    an integration of customer service level and business performance, the erstwhile key business metrics
    in the pre-SOP era. Customers often placed orders too large to be fulfilled immediately, and ATP
    was expected to provide customers with reasonably accurate dates on when they should expect which
    part of their order to be filled. Generating and meeting these dates would enable Geneva improve its
    customer service levels that not providing any fulfillment dates at all. With declining profit margins,
    as the generics industry is forced to explore new means of cost reduction, Geneva expects that thin
    inventories, just-in-time manufacturing, and top quality customer service will eventually be the
    drivers of success, hence the importance of this metric. Evans explains the importance of ATP as a
    business metric as:
    “Most of our customers understand the dynamics of our business, and how difficult it
    is for us to fulfill a large order instantaneously with limited production capacity. But
    most of them are willing to bear with backorders if we can promise them a
    reasonable delivery date for their backorder and actually deliver on that date. That
    way, we take less of a customer service level hit than defaulting on the order or being
    unable to accommodate it. In commodity business such as ours, customer service is
    the king. Our customers may be willing to pay a little premium over the market for
    assured and reliable service, so that they can meet their obligations to their
    customers. Customer service may be a strategic way to build long-term relationships
    with our customers, but of course, we are far from proving or disproving that
    hypothesis.”
    Future Plans
    Despite some initial setbacks in Phase I, Geneva is now back on the road to a successful R/3
    implementation. The senior management, functional units, and IS personnel are all enthusiastic about
    the project and looking forward to its deployment in all operational areas of business and beyond.
    R/3 implementation has opened up new possibilities to Geneva and more means of competing in the
    5 Typically, manufacturing companies requiring SCM analysis used additional analysis tools from I2
    Technologies or Manugistics on top of ERP databases from SAP or Oracle for SCM purposes.
    ERP Implementation at Geneva Pharmaceuticals 15
    intensely competitive generic drugs industry. Weldon provided an overall assessment of the benefits
    achieved via R/3 implementation:
    “In my opinion, we are doing most of the same things, but we are doing them better,
    faster, and with fewer resources. We are able to better integrate our operational
    data, and are able to access that data in a timely manner for making critical business
    decisions. At the same time, SAP implementation has placed us in a position to
    leverage future technological improvements and process innovations, and we expect
    to grow with the system over time.”
    Currently, the primary focus of Geneva’s R/3 implementation is timely completion of Phase II and III
    by February 2000 and December 2000 respectively. Once completed, the implementation team can
    then turn to some of R/3’s additional capabilities that are not being utilized at Geneva. In particular,
    the quality control and human resource modules are earmarked for implementation after Phase III.
    Additionally, Geneva plans to strengthen relationships with key suppliers and customers by
    seamlessly integrating the entire supply chain. The first step in this direction is vendor managed
    inventory (VMI), that was initiated by Geneva in April 1998 for a grocery store chain and a major
    distributor. In this arrangement, Geneva obtains real-time, updated, electronic information about
    customers’ inventories, and replenish their inventories on a just-in-time basis without a formal
    ordering process, based on their demand patterns, sales forecast, and actual sales (effectively
    operating as customers’ purchasing unit).6 Geneva’s current VMI system, Score, was purchased from
    Supply Chain Solutions (SCS) in 1998. Though Mecca is satisfied with this system, he believes that
    Geneva can benefit more from R/3’s ATP module via a combination of VMI functionality and
    seamless company-wide data integration. Currently, some of Geneva’s customers are hesitant to
    adopt VMI because sharing of critical sales data may cause them to lose bargaining power vis-à-vis
    their suppliers or prevent them from speculative buying. But over the long-term, the inherent
    business need for cost reduction in the generics industry is expected to drive these and other
    customers toward VMI. Geneva wants to ensure that the company is ready if and when such
    opportunity arises.
    6 Real-time customer forecast and sales data is run through a VMI software (a mini-MRP system), which
    determines optimum safety stock levels and reorder points for customers, and a corresponding, more optimum
    production schedule for Geneva. Initial performance statistics at the grocery store chain indicated that customer
    service levels increased from 96 percent to 99.5 percent and on-hand inventory decreased from 8 weeks to six
    weeks as a result of VMI implementation. For the distributor, Geneva expects that VMI will reduce on-hand
    inventory from seven months to three months.
    ERP Implementation at Geneva Pharmaceuticals 16
    Exhibit 1. Novartis’ divisions
    Divisions Business Units
    Healthcare Pharmaceuticals
    Consumer Health
    Generics
    CIBA Vision
    Agribusiness Crop Protection
    Seeds
    Animal Health
    Nutrition Infant and Baby Nutrition
    Medical Nutrition
    Health Nutrition
    Exhibit 2. Novartis’ five-year financial summary
    1998 1997 1996 1995 1994
    Annual sales 31,702 31,180 36,233 35,943 37,919
    Sales from healthcare 17,535 16,987 14,048 12,906 14,408
    Sales from agribusiness 8,379 8,327 7,624 7,047 7,135
    Sales from consumer health 5,788 5,866 5,927 5,777 4,258
    Sales from industry - - 8,634 10,213 12,118
    Operating income 7,356 6,783 5,781 5,714 5,093
    Net income 6,064 5,211 2,304 4,216 3,647
    Cash flow from operations 5,886 4,679 4,741 5,729 5,048
    R&D expenditure 3,725 3,693 3,656 3,527 3,786
    Total assets 55,375 53,390 58,027 50,888 51,409
    Net operating assets 20,913 19,619 21,820 22,278 22,952
    Number of employees at year-end 82,449 87,239 116,178 133,959 144,284
    Sales per employee (Swiss Francs) 369,337 350,905 289,705 258,357 266,740
    Debt/equity ratio 0.28 0.41 0.46 0.46 0.57
    Current ratio 2.0 1.7 1.9 2.2 1.6
    Return on sales (%) 19.1 16.7 13.9 - -
    Return on equity (%) 21.0 20.7 16.7 - -
    Note: All figures in millions of Swiss Francs, except otherwise indicated.
    Pre-1996 data is on pro forma basis, based on pooled data from Ciba and Sandoz.
    ERP Implementation at Geneva Pharmaceuticals 17
    Exhibit 3. Phases in R/3 implementation at Geneva
    Phases1 Business processes R/3 modules Implementation timeline
    (inception to go-live)
    Phase I: Supply side
    management
    MRP, purchasing, inventory
    management
    MM2, PP,
    FI/CO3
    Nov 1997 – Feb 1999
    Phase II: Demand side
    management
    Order management, sales,
    customer service
    SD, MM4,
    FI/CO5
    Oct 1998 – Feb 2000
    Phase III: Supply/demand
    integration, business
    intelligence
    Sales & operations planning,
    supply chain management,
    data warehousing
    APO, MES,
    BIW
    Early 2000 – End 2000
    Note: 1Vendor selection took place in mid-1997
    2MM: Raw materials inventory
    4MM: Finished goods inventory
    3FI/CO: Accounts payable
    5FI/CO: Accounts receivable
    Vendor
    System
    Sales orders ATP
    Sales & Distribution
    Customer
    Inquiry Quotation
    Order
    Generation
    Goods
    Issue
    Billing
    Delivery Document
    Update
    Financials
    Inventory
    Management
    Update
    Demand
    Management
    Run
    MPS/MRP
    Production Planning Materials
    Management
    Finance &
    Controlling
    Exhibit 4. Geneva’s order management process
    ERP Implementation at Geneva Pharmaceuticals 18
    Business Planning
    Sales & Operations
    Planning
    DRP Master
    Scheduling
    Detailed Materials/
    Capacity Planning
    Plant & Supplier
    Scheduling
    Execution
    Demand
    Management
    Rough-Cut
    Capacity Planning
    Exhibit 5. Geneva’s manufacturing resource planning process
    Exhibit 6. Geneva’s sales & operations planning process
    Demand
    Planning
    Supply
    Planning
    Integration/
    Reconciliation
    Business Planning
    (S&OP)
    Key Activities:
    • Product planning
    • Forecasting
    • Sales planning
    • Performance
    management
    (prior period)
    • Master production
    scheduling
    • Capacity planning
    • Materials requirements
    planning
    • Consolidation of
    demand, supply,
    inventory, and
    financial plans
    • Feedback to
    demand and
    supply planning
    • Performance review
    • Key assumptions review
    • Product family review
    • Key customers review
    • Financial review
    • Approval/action items
    Current Planning Cycle (Monthly):
    Financial
    close
    (prior month)
    0 5 10 15 17 20 (Business
    days)
    Demand
    planning
    Supply
    planning
    Integration
    Business
    planning
    Goal:
    To reduce the planning cycle time from one month to 10 business days.
    ERP Implementation at Geneva Pharmaceuticals 19
    Appendix
    SAP (Systems, Applications, and Products in Data Processing) is the world’s fourth largest software
    company, and the largest enterprise resource planning (ERP) vendor. As of February 1999, the
    company employed 19,300 employees and had annual revenues of $5 billion, annual growth of 44
    percent, over 10,000 customers in 107 countries, and 36 percent of the ERP market. SAP AG was
    founded in 1972 by Dr. H.C. Hasso Plattner and Dr. Henning Kagermann in Walldorf, Germany with
    the goal of producing an integrated application software, that would run all mission-critical operations
    in corporations, from purchasing to manufacturing to order fulfillment and accounting. This
    integration would help companies optimize their supply chains, manage customer relationships, and
    make better management decisions. SAP brings in 26 years of leadership in process innovations and
    ERP, and invests 20 percent of its revenues back into research and development.
    SAP’s first breakthrough product was the R/2 system, which ran on mainframe computers. R/2 and
    its competitors were called ERP systems, to reflect the fact that they extended the functions of earlier
    materials requirements planning (MRP) systems in manufacturing firms to include other functions
    and business processes such as sales and accounting. In 1992, SAP released its R/3 system, the
    client/server variant of the earlier R/2 system, which was installed in 20,000 locations worldwide, and
    R/2 is installed in over 1,300 locations by mid-1999. Initially targeted at the world’s largest
    corporations such as AT&T, BBC, Deutsche Bank, IBM, KPMG, Merck, Microsoft, Nestle, Nike,
    and Siemens, R/3 has since been deployed by companies of all sizes, geographical locations, and
    industries. SAP solutions are available for 18 comprehensive industry solutions (“verticals”) for
    specific industry sectors such as banking, oil & gas, electronics, health care, and public sector.

  • Cycle Count Process

    Hi Everyone,
    We want to implement cycle count process in our ERP system.
    1) Which idoc(I beleive its WVINVE.WVINVE03)  can be used for this process, for sending data from POS (front end in stores) to ERP. Is there any field which can be used to freeze the count in ERP for a particular item ?
    2) How can we freeze the inventory in ERP ? Suppose i want to do cycle count in afternoon when sale is in process, is it possible to freeze the count of  particular item which i want to count? if yes How ?
    3) If i want to send the current count of items from ERP to some other system or our POS system, Which Outbound Idoc can be used ? How can we trigger that Idoc ? Any transation or program...
    Please provide me as much insight as you can, as i have no idea about this process and domain.
    Thanks
    Inder

    I am not sure about POS integration but if you want to freeze book inventory you need do a small configuration in SAP under Physical Inventory.
    IMG/ MM/ IM/ Physical Inventory/ Allow Freezing of Book Inventory (Select all sotrage locations for whcih you are doing Cycle count)
    Create PI Documents first with all materials which are sibject to count, and freeze the book inventory on the day you start counting.
    Regards
    Ronnie

  • Initial Load and Reconcile of IdM accounts vs Resources. Any advices?

    Hellos.
    Time is now to begin the initial startup of Idm where target resources already have entries.
    Is there anywhere an idiots guide explaining to a novice IdM user the steps involved in loading and linking IdM accounts for the first time? I have to stress the guide has to be designed to meet novices needs i.e. those doing it for the first time.
    We are fairly confident in running IdM from day 1. What I am unsure about is the best techniques to employ on day 0 so that the first FF Async run on day 1 will update IdM accounts rather than attempt to reinsert them.
    We have 3 target resources: 1 AD 2 LDAP and 1 input FF Async source (plus a form for manual adds/mods)
    The targets hold a mix of contract staff and employees. The FF source holds just employees, the contactor's data is entered by hand.
    Am I being stupid if I do the following:
    1. Load IdM Accounts from latest FF source (employees)
    2. reconcile matching AD accounts by name.
    3. reconcile matching LDAP1 accounts by name.
    4. reconcile matching LDAP2 accounts by name.
    5. from unmatched AD accounts since an AD account must exist for current staff make 2nd load file for contractors and load these accounts into IdM.
    6. reconcile matching AD accounts by name
    7. reconcile matching LDAP1 accounts by name
    8. reconcile matching LDAP2 accounts by name
    9 examine the leftovers and manually correct the mispelt or erroneous ones treating the rest as ghosts.
    I am unsure just what the reconciliation is doing, I hope it builds the links between IdM and the resource.
    What I am trying to achieve is a situation where I end up at the end of day0 where I have all the Idm accounts in my repository and are correctly linked to resource accounts so that the FF async can manage the bulk of them
    I believe this has to be done for every IdM implementation. What I am after is advice and pointers to guidance from those who have had the experience of going though the implementation cycle at least once.

    I had a similar problem although I was doing a load from file and I was linking the account to the resource.
    I noticed you had:
    <Field name='accounts[ISA].created'>
    <Default>
    <s>true</s>
    </Default>
    </Field>
    Try using the following instead:
    <Field name='waveset.accounts[GrandSlamXML].created'>
    <Expansion>
    <Boolean>true</Boolean>
    </Expansion>
    </Field>     
    That is what worked for me.

  • Hints on this Interview Question?

    Hints on this Interview Question?
    If after a failed BW interview, the interviewer hints to me, “getting another 2 to 3 full implementations under your belt in a R/3 environment”
    1. What do you really think she is referring to? Since this was for a BW position, is she referring to the extraction stuff on the side of R/3 to pull data to BW?
    2. Could she be referring to actually knowing R/3 say SD, MM, FI/CO, which has nothing to do with BW?
    If so, any hints on “getting another 2 to 3 full implementations under your belt in a R/3 environment” in the absence of internship or job to gain this experience?
    Any other way to pick this up?
    3. By the way, are there any blueprints or documented full cycle implementations which I can read and test on an R/3 system, which I have access to?
    Thanks.

    Hi Caud,
    obviously the interviewer was looking for "experience". No need for hinting at that.
    This means that you have done things before hands-on rather than just read about it. The easiest starting point is the BI content. Take some application area you or prospective clients are most interested in and activate the content. Then start extracting data and following the data flow until you get the reports working and the data reconciles.
    There are many books on SAP BW and all areas of R/3. But you can find many things online as well (help.sap.com).
    There's also the best practices area that covers the full implementation cycle: http://help.sap.com/content/bestpractices/crossindustry/bestp_crossindustry_bi.htm
    Happy learning,
    Marc
    SAP NetWeaver RIG

  • What is the role of Packaging Team

    Hi,
    I have around 4.5 yrs of experience in SAP FICO and a Certification in FICO. Have worked for 2 Full Implementation cycles and 1 partial Implementation Cycle, and 2 support projects as a FICO consultant. Now the project where I am working, its a support project for a global roll out. When Issues come which impact the Global Financial Template it is handled by the Level 3 team, while I am at L2 team, which looks after local changes. L 3 team has their own developement and quality clients.
    After L3 makes any changes which has an impact on the Global Financial Template, the Packaging team moves in and checks the impact of the changes on the Global financial template, stacks the transport request in a sequence and hands them over to the Release Team which then moves it to the local testing client.
    Now, this packaging team is being moved to India and I have been asked to lead this team. Now I am working as FICO Consultant.
    If anyone has worked or seen a Packaging team working, please let me know whether it will be a Good move to accept this role. I am worried because, I fear I will forget FICO and there wont be much of impact analysis also to be done in this role and when under pressure all we will be doing is bundling transport request and handing it over to the release team.
    It would be really nice of someone if someone can guide me through this critical phase.

    Hi Ram,
    This is not exactly Regression Testing. IN this role I will need to analyze the transport requests, do an impact analysis and give a go no-go decision whenever any change is going to impact the global template.
    Advice me please if it is a good idea to take up this assignment

  • What is the role of ABAP technical analyst?

    Dear Friends,
    I would like to know the roles and responsibilities of a ABAP technical analyst for MM ,SD,FI/Co modules.?
    Please tell me in detail what are the other roles or positions are there in an implementation or support project.
    Very curious to know about the implementation cycle in SAP projects.
    like I have heard of aggies,GAP analysis ,Blue print study....But dont have clear picture.
    So relying on Sdn experts completely....
    Thanks,
    Reshali.

    I disagree.  I think the coffee corner is the best place for this kind of general question.  So I've moved it here. Sure, you'll get some sarcastic or teasing answers, but you'll also get some helpful answers.
    However, a general question can only be answered generally.  And I'm not sure how helpful that is.  The role of ABAP technical analyst varies from site to site.
    For example, at one site, I had to:
    Take functional spec and write technical spec and unit test scripts.  If there were questions not addressed in the functional spec, I put it back to the functional analyst.  Once I'd completed the technical spec and unit test scripts, they were reviewed.  Once reviewed and found acceptable, I could code.  I would then run the test scripts, and record the results.  Again my work would be reviewed - the tech spec, the unit test scripts, the results, and the ABAP code.  Once accepted, the development would go into testing.  At any point in the cycle we could go back to an earlier point, get a review, carry on, make changes, get a review...
    So, my responsiblities there were:
    1. Write technical specs from functional spec.
    2. Write unit test scripts
    3. Develop programs
    4. Unit test the programs according to the scripts and record results
    5. Review other programmers technical specs and ensure they match the functional spec.
    6. Review other programmers test scripts and ensure that they are thorough enough
    7. Review other programmers testing and ensure it has been done properly
    8. Review other programmers code, ensure it matches the technical spec and conforms to standards of quality.
    ( This might sound like overkill, but this site was the ONLY site I've ever worked where the vast majority of programs worked correctly in production - the rigourous checks upfront saved that company a fortune in maintenance. ).
    At another site:
    Given a functional spec, write a program and a technical spec.
    btw - when you asked the question in the XI forum, Ramakrishna's answer was copy and paste from SAP Help. 
    matt

  • I'm having problems finding out some details regarding mySAP product.

    What is the current version, how long has it been out, when was the last
    version released
    3. How many companies are using the product (using, not bought)
    4. Is the product available world-wide
    5. How is it sold e.g., direct, channel partners, etc
    6. How is it delivered e.g., direct, partners, etc
    a - if partners, how many are there? are they available world-wide,
    is their a certification process in place? if yes, how do they distinguish
    those partners
    7. What languages is it available in?
    8. How can it be deployed, e.g., in-house or hosted. If hosted, are
    hosting partners restricted?
    9. What is a typical implementation cycle
    10. Technology
    a - what is the technology platform
    b - is it available on MS networks and does it use MS SQL server as
    the database
    c - is it fully integrated into MS Outlook and MS Office
    d - what reporting technology is used
    e - what interface protocals are supported
    f - are separate interface tools required
    g - are there any supporting technologies
    h - what is the recommended server architecture
    i - is it available via web, disconnected user and pda
    j - how is it configured
    i. is configuration limited
    ii. is customisation allowed
    iii. how is it customised
    11. Licensing
    a - how is the product licensed e.g., base plus modules, laundry
    list, etc
    b - are the licences perpetual use or rental
    c - what is the typical percentage of maintenance charged

    Hello Dyfed,
    first of all, it would be nice to know what "MySAP" product you are talking about. Then I would be able to answer some of your questions.
    But the information is also available all over SDN and you can find it there too.
    In case this is a formal product questionaire, I would recommend to contact your local SAP representative and get these questions answered there.
    Kind regards,
    Benny

  • In Change Request Making a default subject

    Dear all,
    We are using SOLMAN 4 and SCM functionality.When we create a change request from charm_create transcation,i want to set in the subject line Urgent correction as default.How can we this?please help
    Thanks in advance,
    Avinash

    Dear Henry,
    I was not able to find a straight way to do that,but found a way around.
    When you see the drop down menu of Subject,first it displays the codes of implementation cycle and then of Maintenance cycle.So to make the Urgent correction as the default one,i spro Soluman->Scenario-Specific Settings->Service Desk->Define code Groups and code for Catalogs (for catalog IB)changed the status of implementation in to "InProcess" from "Released".By this Urgent correction comes as the Default.In our case we are not using Maintenace Project for Change Management and so we are not having any problem by doing this.
    If you are not using Charm for Imple. proj, you can do this.But as i told you it is not the straight way to do this.
    Revert for any clarification.
    Thanks and Regards,
    Avinash.

Maybe you are looking for