<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>SAP</title>
    <link rel="alternate" type="text/html" href="http://www.infosysblogs.com/sap/" />
    <link rel="self" type="application/atom+xml" href="http://www.infosysblogs.com/sap/atom.xml" />
   <id>tag:www.infosysblogs.com,2010:/sap/1</id>
    <link rel="service.post" type="application/atom+xml" href="http://www.infosysblogs.com/sap-mt/mt-atom.cgi/weblog/blog_id=1" title="SAP" />
    <updated>2010-02-01T09:19:31Z</updated>
    <subtitle>Discuss business intelligence, integration, compliance and a host of other SAP-related topics – implementation, best practices and resources to negotiate the world of SAP better!</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 3.2ysb5-20051201</generator>
 
<entry>
    <title>How can IT help in implementing Activity Based Costing?</title>
    <link rel="alternate" type="text/html" href="http://www.infosysblogs.com/sap/2010/01/how_can_it_help_in_implementin_1.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.infosysblogs.com/sap-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=100" title="How can IT help in implementing Activity Based Costing?" />
    <id>tag:www.infosysblogs.com,2010:/sap//1.100</id>
    
    <published>2010-01-31T12:18:52Z</published>
    <updated>2010-02-01T09:19:31Z</updated>
    
    <summary>This blog discusses the role of IT in implementing Activity Based Costing (ABC), comparison between buy versus build and options for off-the-shelf ABC softwares.</summary>
    <author>
        <name>Vivek Madhav</name>
        
    </author>
            <category term="Enterprise Performance Management" />
    
    <content type="html" xml:lang="en" xml:base="http://www.infosysblogs.com/sap/">
        <![CDATA[My previous blogs series- &ldquo;<a href="http://www.infosysblogs.com/sap/2009/10/why_need_profitability_analysi_1.html#more">Why do you need profitability analysis?</a>&rdquo; and &ldquo;<a href="http://www.infosysblogs.com/sap/2009/12/activity_based_costing_for_pro_1.html#more">Activity based costing for profitability analysis</a>&rdquo; highlights&nbsp; the need for profitability analysis and discusses the challenges expected in ABC implementation. As a next step, this blog discusses the role of IT in adoption of Activity Based Costing (ABC) methodology. ]]>
        <![CDATA[<p>Traditionally critics have argued that ABC is too costly and complex to implement and the cost involved in implementing and maintaining ABC based system exceeds the benefits gained. However the advancement in IT has significantly brought down the information processing cost. While the information processing cost has reduced, the cost of poor information leading to poor decision has significantly increased owing to the competitive pressure.</p><p>When it comes to IT, the first decision is usually between buy versus build. The ABC allocation model is more or less standard; the Off-the-shelf (OTS) ABC software have matured during the last decade; and building an advanced ABC model is too cumbersome - are the strong arguments in favor of buy option. The build option should be considered only when there is a very strong reason for this. Like - the ABC model is too simple or highly customized or is required to be monolithically integrated with other in-house systems etc.</p><p>Talking about the OTS option, the choice can be between specialized ABC software and ABC module of ERP packages. ABC module of ERP package is ideal where ABC is required for operational decision making and most of the data is available within ERP itself. &nbsp;</p><p>However, specialized ABC software should be considered in the following cases:<br />1)&nbsp;ABC is required for tactical or strategic decision making.<br />2)&nbsp;Multi-dimensional analysis of overheads are required<br />3)&nbsp;Underlying data is stored in heterogeneous systems<br />4)&nbsp;ABC model is required to be flexible as frequent changes are expected.</p><p>SAP suite of products has both the offerings - SAP ERP has a sub-module for ABC in SAP Controlling (SAP CO-ABC). SAP BusinessObjects Profitability and Cost Management (SAP PCM) is specialized software for ABC from SAP suite of products.</p><p>Right tool selection plays a very important role in the success of ABC. In the subsequent blogs let&rsquo;s look at some of the important evaluation criteria for ABC software selection, implementation methodology and other related topics. In the mean time, please leave your comments and suggestions <img title="Smile" alt="Smile" src="http://www.infosysblogs.com/sap-mt/mt-static/plugins/TinyMCE/jscripts/tiny_mce/plugins/emotions/images/smiley-smile.gif" border="0" />.</p>]]>
    </content>
</entry>
<entry>
    <title>How could digital marketing impact your company processes and systems? (part 2)</title>
    <link rel="alternate" type="text/html" href="http://www.infosysblogs.com/sap/2010/01/how_could_digital_marketing_im.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.infosysblogs.com/sap-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=97" title="How could digital marketing impact your company processes and systems? (part 2)" />
    <id>tag:www.infosysblogs.com,2010:/sap//1.97</id>
    
    <published>2010-01-28T13:50:10Z</published>
    <updated>2010-01-28T14:00:14Z</updated>
    
    <summary>The increasing spending in digital marketing pushes the companies to re-view its organization, processes and systems in order to sustain the growth and manage effectively the digital marketing initiative together with traditional advertising. In the previous blog I have highlighted...</summary>
    <author>
        <name>Lorenzo Pagani</name>
        
    </author>
            <category term="SAP Solutions" />
    
    <content type="html" xml:lang="en" xml:base="http://www.infosysblogs.com/sap/">
        <![CDATA[<p>The increasing spending in digital marketing pushes the companies to re-view its organization, processes and systems in order to sustain the growth and manage effectively the digital marketing initiative together with traditional advertising. </p><p>In the previous blog I have highlighted the reasons why the spending in digital marketing is accelerating and the areas in which an extensive use of digital marketing channels could mainly impact the organization.</p><p>Now let&rsquo;s look deeper at the impacts of digital marketing on the company information systems.</p>]]>
        <![CDATA[<p><br />I think that an effective implementation of digital marketing initiatives is going to impact first of all CRM, Web, reporting and analytics either in term of enrichment of functionalities or re-definition and implementation of new platforms:&nbsp; </p><p>&nbsp;CRM systems are requiring new functionalities for managing the campaign across multiple channels, capacity to gather from multiple sources new types and higher volumes of information regarding the consumer or the customer, tools and repositories to enable an effective digital asset management.</p><p>&nbsp;Web: the trend is to define and implement new platforms that facilitate the development and hosting of the web initiatives,&nbsp; increase the capacity to deliver personalized multimedia content, promote the reuse of existing assets for the initiative creation<br />&nbsp;<br />&nbsp;Reporting and analytics: here the&nbsp; key element is to develop and elaborate new indicator and scorecards to track the effectiveness of the web initiative, monitor consumer/customer behavior in the web and integrate these measures with the traditional marketing indicators.</p><p>How SAP is currently supporting these areas? </p><p>We need to look into mySAP CRM. <br />With the CRM suite SAP addresses multichannel campaign management and allows the interaction with the client via web making available some of the functionalities through the internet channel (e.g quotations and order management, actions)&nbsp; <br />But overall at the moment I think it does not provide very specialized E-marketing functionalities. </p><p>Campaign management <br />&nbsp;Marketing activities can be executed through different interaction channels: direct mail, e-mail, phone, web, fax, and SMS.<br />&nbsp;Online marketing channels to plan, develop, and execute e-mail marketing campaigns.</p><p>Web Channel management<br />&nbsp;Support campaign execution on the web. E.g. the system uses campaign IDs and coupon codes to determine products flagged for campaigns in SAP CRM and to determine campaign pricing in the Web shop. Also create private campaigns for specific target groups or public campaigns for all Web shop visitors.&nbsp; <br />&nbsp;Manage customer loyalty processes via Internet</p><p>Web channel analytics <br />&nbsp;Perform analysis on the use of web functionalities in order to track the behavior, target the customers and drive future marketing activities. </p><p>Digital Asset Management <br />&nbsp;Within the marketing resource management a central repository for the digital assets (photos, videos, or text documents) can be maintained. To each object properties and authorization concepts can be assigned to each object in order to manage it efficiently and secure direct web access. Besides the systems tracks the download information and provides specific reporting for each asset.</p><p>What is your point of view on this topic? Your thoughts would be highly appreciated and more than welcome.<br />Is SAP developing any innovative solution with the social CRM? <br />I will discuss on it in my next blog.</p>]]>
    </content>
</entry>
<entry>
    <title>Professional Hair Care business: The “STYLE” side of CPG retailing – Part-I</title>
    <link rel="alternate" type="text/html" href="http://www.infosysblogs.com/sap/2010/01/professional_hair_care_busines.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.infosysblogs.com/sap-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=95" title="Professional Hair Care business: The “STYLE” side of CPG retailing – Part-I" />
    <id>tag:www.infosysblogs.com,2010:/sap//1.95</id>
    
    <published>2010-01-27T12:16:13Z</published>
    <updated>2010-01-27T13:18:33Z</updated>
    
    <summary>There is another cousin, Professional Hair Care business, which technically shares the same categorization - CPG-retailing, but is altogether different ballgame when it comes to sales and retailing.</summary>
    <author>
        <name>Sameer Ahmed</name>
        
    </author>
            <category term="SAP Solutions" />
    
    <content type="html" xml:lang="en" xml:base="http://www.infosysblogs.com/sap/">
        <![CDATA[<p><strong>Professional Hair Care - Retailing with style !</strong></p><p>The first thought that always comes to mind whenever someone makes a mention of CPG industry - the traditional manufacturer-distributor-retailer business which works in tandem to deliver the goodies to the God in the entire chain - The Consumer! This traditional CPG-retailing is pretty well set over the ages and is perhaps one of the most revenue and employment generating businesses around the globe.</p>]]>
        <![CDATA[<p>There is another cousin, Professional Hair Care business, which technically shares the same categorization - CPG-retailing, but is altogether different ballgame when it comes to sales and retailing.</p><p>To many of us, hair care translates into an application of shampoo and conditioner in the bathroom! But the fact is that there is whole lot of art-work that can go on your head and translates into much bigger revenues than just shampoo and conditioners!</p><p>Professional Hair Care is more a multi-billion dollar global industry and growing steadily. This fact is realized by the major CPG manufacturers and they have acquired big stakes in the Professional Hair Care by way of acquisitions during the last few years. <br />While the Hair Care industry gets a boost from the major CPG players to ride on the well established volumes and scales of the CPG logistics, there is also a different approach that the manufacturers have to take when it comes to marketing and selling these products.<br /></p><p><br /><strong>Style matters!</strong> </p><p>Hair Care Salons are the place where the hair care products get consumed. But this consumption is not a simple &ldquo;buy&rdquo; from the end consumer, un-like the traditional retail store. These salons are run by artists who perform coloring and styling on the clients. The bottom line here is CLASS and STYLE! The more effective and customized the style for the client, the more repeat business and personal relationship it generates.</p><p>The same stands true for the manufacturer &ndash; salon relationship. It needs the personal touch. This is catered to by sales representatives from manufacturer / distributor paying scheduled visits to the salons and interacting with them constantly.</p><p>&nbsp;</p><p><strong>Incentives - Key business generators </strong></p><p>Promotions, in this industry, are an essential growth driver. Salons are not volume-based retailers. While class and quality remain their key areas, they also depend on the offerings and discounts to maximize the cost saving opportunities. Promotions, like buy-1 get-1 free, get discounts or bonus on meeting certain volume or targets, new launch initiatives, etc. contribute heavily towards the sales to salons. Salon setups and customizations, which are big investments for salon owners, are also provided by the manufacturers as a financial aid, thereby winning over customer loyalty for future product sales &ndash; a win-win solution for both.</p><p><br />......will look at this business from a technology enablemnet perspective in Part-II of this blog<br /></p>]]>
    </content>
</entry>
<entry>
    <title>Business Process – Adopting Industry Best Practices (Part 3 of 3)</title>
    <link rel="alternate" type="text/html" href="http://www.infosysblogs.com/sap/2010/01/business_process_adopting_indu_2.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.infosysblogs.com/sap-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=94" title="Business Process – Adopting Industry Best Practices (Part 3 of 3)" />
    <id>tag:www.infosysblogs.com,2010:/sap//1.94</id>
    
    <published>2010-01-27T11:35:12Z</published>
    <updated>2010-01-27T11:49:30Z</updated>
    
    <summary><![CDATA[Key Success factor-&nbsp;Visible Executive sponsorship-&nbsp;Effective communication in the organisation-&nbsp;Stakeholder heavy involvement-&nbsp;Effective knowledge management-&nbsp;Clearly defined measures of Success...]]></summary>
    <author>
        <name>Sathyanarayana Krishnamurthy</name>
        
    </author>
            <category term="Energy/Utility" />
    
    <content type="html" xml:lang="en" xml:base="http://www.infosysblogs.com/sap/">
        <![CDATA[<p>Key Success factor<br />-&nbsp;Visible Executive sponsorship<br />-&nbsp;Effective communication in the organisation<br />-&nbsp;Stakeholder heavy involvement<br />-&nbsp;Effective knowledge management<br />-&nbsp;Clearly defined measures of Success</p>]]>
        <![CDATA[<p>Benefit<br />Some of the global ERP vendors like SAP, are prepackaging the ERP solution to specific Industry verticals which include preconfigured and document Industry processes. Such approach can bring in some of the following benefits:</p><p>Save time and money:<br />And achieve predicted results<br />Fewer risks:<br />Avoid common e-Business beginners&lsquo; mistakes<br />Fast track:<br />To extending your business solution with new business processes<br />No trial runs:<br />Start straight off with a fully documented prototype that is fully reusable<br />Failure is not an option!<br />It works: what you see is what you get for implementation<br />Communication:<br />Among project team members and executives becomes more effective<br />Consistent approach:<br />Focusing on integrated end-to-end business processes</p><p><br />Conclusion<br />Adopt Industry Best Practices for better ROI, but ensure you do the home work during planning phases; else the project can be a financial and business disaster. </p>]]>
    </content>
</entry>
<entry>
    <title>Trade Promotion Management in Consumer Packaged Goods (CPG) business</title>
    <link rel="alternate" type="text/html" href="http://www.infosysblogs.com/sap/2010/01/trade_promotion_management_in.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.infosysblogs.com/sap-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=93" title="Trade Promotion Management in Consumer Packaged Goods (CPG) business" />
    <id>tag:www.infosysblogs.com,2010:/sap//1.93</id>
    
    <published>2010-01-21T04:45:32Z</published>
    <updated>2010-01-21T04:50:46Z</updated>
    
    <summary>Trade Promotion Management in Consumer Packaged Goods (CPG) business</summary>
    <author>
        <name>Shashi Jadhav</name>
        
    </author>
            <category term="Retail" />
    
    <content type="html" xml:lang="en" xml:base="http://www.infosysblogs.com/sap/">
        <![CDATA[<p class="MsoNormal" style="margin: 0in 0in 0pt; line-height: normal"><strong><span style="font-size: 10pt; color: #0070c0; font-family: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'">What is Trade Promotion Management (TPM)?</span></strong><span style="font-size: 10pt; color: #0070c0; font-family: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"> </span></p><span style="font-size: 10pt; color: #0070c0; font-family: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"><p>&nbsp;</p></span>&nbsp;<span style="font-size: 10pt; color: #0070c0; font-family: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'">A simple definition is a set of processes that aim to manage promotional spending so that it maximizes sales up-lift, brand awareness, market share, and return on investment. <p>&nbsp;</p></span>]]>
        <![CDATA[<strong><span>Why is improving trade promotion management important?</span></strong><span> <br /></span><span>Trade promotion management is the second largest expense in CPG businesses, and on average it represents 12-17% of revenue according to benchmark studies by the Trade Promotion Management Associates (TPMA). Yet most CPG companies acknowledge that their TPM activities are not effective at generating incremental sales volume and return on investment. Survey respondents indicated on <em>average</em> only 61% of trade promotions generate incremental volume, only 62% of promotions are being fully implemented at all locations, and&nbsp; promotions increase out of stock incidents 2.3%.<br /></span><span><span><span>&middot;<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span>The three kinds of promotions are: </span><span><br /></span><span><span>o<span>&nbsp;&nbsp;&nbsp; </span></span></span><span>Corporate Promotions are company-wide promotions of a product or a brand in which accounts can participate. They are run for a specific time period and contain the objective of the promotion, suggested tactics, and other information. For example, a beverage company decides to promote a new product by running a corporate promotion with the recommended tactics of a temporary price reduction (TPR) and in-store displays.</span><span> <br /></span><span><span>o<span>&nbsp;&nbsp;&nbsp; </span></span></span><span>Discretionary Promotions are promotion templates that can serve as the basis of an account promotion. After a discretionary promotion has been created, it is saved as a template. Other key account managers can use templates of existing promotions when establishing promotions at their accounts. </span><span><br /></span><span><span>o<span>&nbsp;&nbsp;&nbsp; </span></span></span><span>Account Promotions can be based on a corporate promotion or a discretionary promotion. A plan is a group of account promotions that depicts the aggregate results of account promotions, such as spending and volume.</span><span><br /></span><span><strong><span>How do you improve trade promotion management?</span></strong><span><br /></span><span><span>&middot;<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><u><span>Measure and analyze post program results</span></u><span> &ndash; companies need to understand why different trade activities are successful or not. By measuring and analyzing results companies can better understand the impact of various factors such as placement (checkout stand vs. end of aisle), spending type (off invoice, bill back, scan-based, etc), distribution channel, frequency of promotions, seasonality, and brand/category, on incremental volume and profitability. <br /></span><span><span><span>&middot;<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><u><span>Focus program spending</span></u><span> &ndash; companies need tend to spread trade dollars evenly across brands and categories instead of focusing on those with the highest trade returns and greatest growth prospects. Brands with high market share in premium categories generally merit high investment, whereas brands with low market share in value categories tend to be poor opportunities for trade investments.<br /></span><span><span><span>&middot;<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><u><span>Link promotions with stock planning</span></u><span> &ndash; companies need to ensure products are on the shelf during promotional events. Improving trading partner collaboration on forecasting and replenishment logistics helps maximize sales/margins by reducing out of stock incidences. It also helps improve customer satisfaction, loyalty and traffic during future promotions.<br /></span><span>&nbsp;<br /></span><span>The next frontier in the evolution of trade promotion management will involve the collaborative use by the retailer and manufacturer of the technology available today to manage trade promotion spending in real-time for mutual gain. Implementation of the technology is only scratching the surface; the real focus has to be on the words collaborative, mutual and paradigm shift. The combination of these powerful and attainable ideas could bring us back 180 degrees, to as time long ago when trade promotion resulted in mutual incremental sales volume and profit, for both concerned parties. <br /></span><span><span>In the next blog I will talk more about as how SAP is helping organizations in TPM space.</span><span><br /></span></span></span></span></span></span>]]>
    </content>
</entry>
<entry>
    <title>Activity based costing for profitability analysis (Part 2 of 2)</title>
    <link rel="alternate" type="text/html" href="http://www.infosysblogs.com/sap/2009/12/activity_based_costing_for_pro_1.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.infosysblogs.com/sap-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=92" title="Activity based costing for profitability analysis (Part 2 of 2)" />
    <id>tag:www.infosysblogs.com,2009:/sap//1.92</id>
    
    <published>2009-12-31T04:12:45Z</published>
    <updated>2010-02-01T10:25:07Z</updated>
    
    <summary>This blog discusses the challenges to expect in implementing Activity Based Costing (ABC). These challenges are categorized as business, behavioral and techncial.</summary>
    <author>
        <name>Vivek Madhav</name>
        
    </author>
            <category term="Enterprise Performance Management" />
    
    <content type="html" xml:lang="en" xml:base="http://www.infosysblogs.com/sap/">
        <![CDATA[<p align="justify">My previous blogs series &ldquo;<a title="Why do you need profitability analysis?" href="http://www.infosysblogs.com/sap/2009/10/why_need_profitability_analysi_1.html#more" target="_blank">Why do you need profitability analysis?</a>&rdquo; sets the context for profitability analysis. The next blog &ldquo;<a title="Activity based costing for profitability analysis" href="http://www.infosysblogs.com/sap/2009/12/why_do_you_need_profitability.html#more">Activity based costing for profitability analysis (Part 1)</a>&rdquo; highlights the need for Activity Based Costing (ABC) for profitability analysis. Once we are convinced about the need for profitability analysis and ABC, we have to figure out how to go about implementing ABC for our organization. This blog discusses the typical challenges in implementing ABC.</p>]]>
        <![CDATA[<p align="justify"><span><span><span><span>These challenges can be categorized in business, behavioral and technical challenges.</span></span></span></span></p><p align="justify"><span><span><span><span><strong>1. <u>Business Challenges:</u></strong></span></span></span></span></p><p align="justify">a)&nbsp;Identification of Purpose: The most important step towards implementing ABC is to identify the purpose of the Activity Based Costing (ABC) and Profitability analysis. The purpose can be operational, tactical, strategic or a combination there-of. We call it operational - if the profitability analysis has to support the day to day decisions like - is the sales order profitable or how much to charge the customer for a particular sales order?&nbsp; It can be tactical if it is to segment customers based on profitability or to identify the best product. We can call it strategic if it helps us identify the right investment opportunity.&nbsp;&nbsp;<br />b)&nbsp;Design the ABC process: The next important step is to design the ABC process that suits the needs and purpose of a particular organization. This involves identifying the resources, activities, drivers etc and defining the rules for allocating the cost. </p><p align="justify"><strong>2. <u>Behavioral Challenges:</u></strong></p><p align="justify">a)&nbsp;ABC system will affect different business units and staffs differently. It is wise to expect staff resistance and plan for handling this resistance. A proper change management&nbsp; and communication plan should help us address this challenge.<br />b)&nbsp;Starting with one unit and subsequently rolling out to the others will help us anticipate the challenges to expect and buy us time to prepare to address them.</p><p align="justify"><strong>3. <u>Technical Challenges:</u></strong> </p><p align="justify">a)&nbsp;Data Collection: ABC requires lot many additional data than traditional costing. This additional data needs to be captured by the system for processing.<br />b)&nbsp;Data Processing: ABC requires data processing based on complex rules and calculation.<br />c)&nbsp;Reporting: Finally, actionable information based on ABC must be presented to the decision makers in the form of reports and dashboards. </p><p align="justify">While business needs to focus on the&nbsp;Business and&nbsp;Behavioural&nbsp;challenges, the good news is IT can help them in addressing the third challenge. There are sophisticated software available for ABC and profitability analysis.</p><p align="justify">How IT can help in ABC implementation, what are the software available for this purpose and considerations in software selection. Please wait for the next blog.</p>]]>
    </content>
</entry>
<entry>
    <title>The new weapon for the CFO’s knights (Part 2 of 3) – Conquering IFRS</title>
    <link rel="alternate" type="text/html" href="http://www.infosysblogs.com/sap/2009/12/the_new_weapon_for_the_cfos_kn_1.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.infosysblogs.com/sap-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=91" title="The new weapon for the CFO’s knights (Part 2 of 3) – Conquering IFRS" />
    <id>tag:www.infosysblogs.com,2009:/sap//1.91</id>
    
    <published>2009-12-29T13:07:33Z</published>
    <updated>2009-12-29T13:22:55Z</updated>
    
    <summary>Second edition to the three part series on capabilities of SAP BO EPM financial consolidation offerings. </summary>
    <author>
        <name>Bharat Chadha</name>
        
    </author>
            <category term="Enterprise Performance Management" />
    
    <content type="html" xml:lang="en" xml:base="http://www.infosysblogs.com/sap/">
        <![CDATA[<span style="font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'"><span style="font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'"><span style="font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'"><p align="justify"><span style="line-height: 115%; font-family: 'Calibri','sans-serif'; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">In my previous blog of this series, I briefly spoke about the capabilities of SAP EPM financial consolidation tool(s) - inherent as well as the ones over and above legal &amp; management consolidation and reporting functionalities. In the following discussion, I&rsquo;ll talk about IFRS, the possible solutions for transition and finally share some of our learning&rsquo;s from an experiment we carried out involving US GAAP and IFRS.</span></p></span></span></span>]]>
        <![CDATA[<span style="font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'"><span style="line-height: 115%; font-family: 'Calibri','sans-serif'; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><p style="text-align: justify"><span style="font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'">Various regulators across the globe have either mandated, or are in the process of, the transition to IFRS. While some of these regulators are looking at a change from their current rule-based philosophy (such as US GAAP) to the principles-based IFRS, the others are looking at extending their present philosophy to incorporate a more fair value and componentized approach. The effect of this transition will be felt differently across industries, while some such as logistics, media &amp; entertainment etc. might not be drastically impacted, others such as consumer goods, automotive, banking, insurance etc. are expecting major implications. These implications, irrespective of intensity, are expected to impact a company at both the corporate and subsidiary levels, in its methods of valuating various business transactions, current IT transactional system landscape and also the governance and change management of human capital.&nbsp;</span>&nbsp; </p><p style="text-align: justify"><span style="font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'">It&rsquo;s been widely noted that technology can play a key enabler in transition to IFRS. This was further corroborated in a recent whitepaper from PWC &amp; SAP. It suggested, from experience in Australia, Asia and Europe, that companies that had underestimated the involvement of IT in their adoption of IFRS created for themselves a weakened control environment driven by increased risk and cost outlay. A phased landscape upgrade, encompassing a company&rsquo;s general ledger, sub-ledger and financial consolidation &amp; reporting systems, can provide not only an agile solution for transition but also an opportunity to reassess the current IT strategy supporting the financial processes and policies.&nbsp;</span> </p><p style="text-align: justify"><span style="font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'">Transition to IFRS is not only an accounting exercise but also entails additional responsibilities such as dual reporting, audit trail etc. The dual reporting period (for e.g. 2012 &ndash; 2014 for US GAAP and IFRS) is to enable historical comparisons between the local GAAP and IFRS prior to the transition, thus allowing companies to reconcile and explain the differences. In order to achieve this, companies can pilot their transition beginning with multi-GAAP reporting using a financial consolidation system while improvising their transactional systems for the final cutover to IFRS.&nbsp;</span>&nbsp; </p><p style="text-align: justify"><span style="font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'">Standard ERP applications available from SAP, such as SAP General Ledger, Asset Accounting etc., are capable of provisioning the final cutover for the local close (the final state/ long term solution); while applications from the SAP BusinessObjects stable, such as SAP BPC and SAP BO FC, provide dual reporting capabilities in conjunction with group close/ consolidated reporting functionalities, thus serving as a short term solution for transition to IFRS. The functionalities of the latter-mentioned tools can be extended to incorporate XBRL reporting (available using SAP BO XBRL publishing by UB Matrix) and also to provide preconfigured IFRS compliant content (available using SAP BO IFRS starter kit).</span>&nbsp; </p><p style="text-align: justify"><span style="font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'">In order to ascertain the complexities involved we started with a small experiment based on IAS 16 (Property, Plant and equipment) using SAP BPC 7.0 MS. During the course of the development, we extensively utilized functionalities for manual adjustments and business rules alongwith some scripting. The ability to use different hierarchical views or dimensionality allowed us to formulate reports and schedules for different standards (US GAAP and IFRS in our case). At the end of the experiment, we concluded that though this method is easier to implement, than the other approach involving the ledger, it is also poses systemic issues around performance and also falls short in flexibility.&nbsp;</span>&nbsp; </p><p style="text-align: justify"><span style="font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'">Well, this ends my discussion for the day. In the next and final post of this blog series, I&rsquo;ll discuss about XBRL and some other capabilities of the SAP BO financial consolidation offerings.&nbsp;</span>&nbsp; </p><p style="text-align: justify"><span style="font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'">Stay Tuned.</span>&nbsp; </p><p style="text-align: justify"><span style="font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'">Also, wishing you and your family a very happy new year. </span></p><span style="font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'"><p>&nbsp;</p></span><span style="font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'">PN: Abbreviations used - SAP BPC stands for SAP BusinessObjects Planning and Consolidation, SAP BO FC stands for SAP BusinessObjects Financial Consolidation <p>&nbsp;</p></span><p align="justify">&nbsp;</p></span></span>]]>
    </content>
</entry>
<entry>
    <title>“SAP BPC Owned by Business developed by IT” is it a reality or myth.</title>
    <link rel="alternate" type="text/html" href="http://www.infosysblogs.com/sap/2009/12/sap_bpc_owned_by_business_deve_1.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.infosysblogs.com/sap-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=90" title="“SAP BPC Owned by Business developed by IT” is it a reality or myth." />
    <id>tag:www.infosysblogs.com,2009:/sap//1.90</id>
    
    <published>2009-12-29T08:12:25Z</published>
    <updated>2009-12-29T08:31:30Z</updated>
    
    <summary>It is a general perception that SAP BPC can be easily managed or supported by Business which helps in reducing total cost of ownership and reducing dependency of business on IT dept....</summary>
    <author>
        <name>Aalok Kumar</name>
        
    </author>
            <category term="Enterprise Performance Management" />
    
    <content type="html" xml:lang="en" xml:base="http://www.infosysblogs.com/sap/">
        It is a general perception that SAP BPC can be easily managed or supported by Business which helps in reducing total cost of ownership and reducing dependency of business on IT dept.
        <![CDATA[<p><span><span>Let&rsquo;s try to further analyze this statement and find out task which can be independently managed by Business users.<br />1)<strong>&nbsp;Changing organization structure</strong>: SAP BPC admin console has excel embedded into it, administrator or super user or business user with admin task profile can open entity dimension member sheet and use native excel functionality to change the existing organization structure.<br />2)&nbsp;<strong>Changing master data</strong> : SAP BPC&nbsp; holds master data in various dimensions ,As stated above , we can use native excel functionality to add new dimension member and change attribute of any dimension member.<br />3)&nbsp;<strong>Loading transactional data</strong>: SAP BPC comes with unique feature of data manager packages, which are easy to use. Predefined data manage packages are used for following purpose<br />a.&nbsp;Loading of transactional data <br />b.&nbsp;Clearing data <br />c.&nbsp;Copy data<br />d.&nbsp;Move data<br />4)&nbsp;<strong>On demand reporting</strong>: SAP BPC offers flexibility to business user to create report using drag and drop functionality or using predefined report templates.<br />5)&nbsp;<strong>Security profile</strong> : SAP BPC offers wizard based security profile .Business user with security task profile&nbsp; can easily add&nbsp; any user assign a task profile , team and member access profile using wizard functionality.</span></span></p><p><span><span><br />SAP BPC is integrated with MS office (Excel, Word &amp; Powerpoint), it reduces training cost and gets easily adopted by business users. With the above examples and my project experience in SAP BPC, I can safely say that SAP BPC reduces maintenance effort considerably as compared to other SAP planning tool( IP &amp; BPS ) or any other third party tool.</span></span></p>]]>
    </content>
</entry>
<entry>
    <title>Fast Close – Business Challenges</title>
    <link rel="alternate" type="text/html" href="http://www.infosysblogs.com/sap/2009/12/fast_close_business_challenges_1.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.infosysblogs.com/sap-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=89" title="Fast Close – Business Challenges" />
    <id>tag:www.infosysblogs.com,2009:/sap//1.89</id>
    
    <published>2009-12-24T20:44:03Z</published>
    <updated>2009-12-24T20:53:55Z</updated>
    
    <summary>Understand the business challenges that hinder a fast close process. </summary>
    <author>
        <name>Akhilesh Mittal</name>
        
    </author>
            <category term="SAP Solutions" />
    
    <content type="html" xml:lang="en" xml:base="http://www.infosysblogs.com/sap/">
        <![CDATA[<!--[if gte mso 9]><xml>  <o:OfficeDocumentSettings>   <o:AllowPNG/>  </o:OfficeDocumentSettings> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:WordDocument>   <w:View>Normal</w:View>   <w:Zoom>0</w:Zoom>   <w:TrackMoves/>   <w:TrackFormatting/>   <w:PunctuationKerning/>   <w:ValidateAgainstSchemas/>   <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>   <w:IgnoreMixedContent>false</w:IgnoreMixedContent>   <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>   <w:DoNotPromoteQF/>   <w:LidThemeOther>EN-US</w:LidThemeOther>   <w:LidThemeAsian>X-NONE</w:LidThemeAsian>   <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>   <w:Compatibility>    <w:BreakWrappedTables/>    <w:SnapToGridInCell/>    <w:WrapTextWithPunct/>    <w:UseAsianBreakRules/>    <w:DontGrowAutofit/>    <w:SplitPgBreakAndParaMark/>    <w:DontVertAlignCellWithSp/>    <w:DontBreakConstrainedForcedTables/>    <w:DontVertAlignInTxbx/>    <w:Word11KerningPairs/>    <w:CachedColBalance/>    <w:UseFELayout/>   </w:Compatibility>   <m:mathPr>    <m:mathFont m:val="Cambria Math"/>    <m:brkBin m:val="before"/>    <m:brkBinSub m:val="&#45;-"/>    <m:smallFrac m:val="off"/>    <m:dispDef/>    <m:lMargin m:val="0"/>    <m:rMargin m:val="0"/>    <m:defJc m:val="centerGroup"/>    <m:wrapIndent m:val="1440"/>    <m:intLim m:val="subSup"/>    <m:naryLim m:val="undOvr"/>   </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"   DefSemiHidden="true" DefQFormat="false" DefPriority="99"   LatentStyleCount="267">   <w:LsdException Locked="false" Priority="0" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Normal"/>   <w:LsdException Locked="false" Priority="9" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="heading 1"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/>   <w:LsdException Locked="false" Priority="39" Name="toc 1"/>   <w:LsdException Locked="false" Priority="39" Name="toc 2"/>   <w:LsdException Locked="false" Priority="39" Name="toc 3"/>   <w:LsdException Locked="false" Priority="39" Name="toc 4"/>   <w:LsdException Locked="false" Priority="39" Name="toc 5"/>   <w:LsdException Locked="false" Priority="39" Name="toc 6"/>   <w:LsdException Locked="false" Priority="39" Name="toc 7"/>   <w:LsdException Locked="false" Priority="39" Name="toc 8"/>   <w:LsdException Locked="false" Priority="39" Name="toc 9"/>   <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/>   <w:LsdException Locked="false" Priority="10" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Title"/>   <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/>   <w:LsdException Locked="false" Priority="11" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/>   <w:LsdException Locked="false" Priority="0" Name="Hyperlink"/>   <w:LsdException Locked="false" Priority="22" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Strong"/>   <w:LsdException Locked="false" Priority="20" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/>   <w:LsdException Locked="false" Priority="59" SemiHidden="false"    UnhideWhenUsed="false" Name="Table Grid"/>   <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/>   <w:LsdException Locked="false" Priority="1" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 1"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 1"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 1"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/>   <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/>   <w:LsdException Locked="false" Priority="34" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/>   <w:LsdException Locked="false" Priority="29" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Quote"/>   <w:LsdException Locked="false" Priority="30" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 1"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 1"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 2"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 2"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 2"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 2"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 2"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 3"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 3"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 3"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 3"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 3"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 4"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 4"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 4"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 4"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 4"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 5"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 5"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 5"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 5"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 5"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 6"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 6"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 6"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 6"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 6"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/>   <w:LsdException Locked="false" Priority="19" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/>   <w:LsdException Locked="false" Priority="21" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/>   <w:LsdException Locked="false" Priority="31" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/>   <w:LsdException Locked="false" Priority="32" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/>   <w:LsdException Locked="false" Priority="33" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Book Title"/>   <w:LsdException Locked="false" Priority="37" Name="Bibliography"/>   <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/>  </w:LatentStyles> </xml><![endif]--> <!--[if gte mso 10]> <style>  /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-priority:99; 	mso-style-qformat:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin:0in; 	mso-para-margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:"Times New Roman"; 	mso-fareast-theme-font:minor-fareast; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} </style> <![endif]-->  <p style="text-align: justify" class="MsoNormal">Fast close increases trust and provides competitive advantage. I discussed the business drivers behind fast close in my previous post &ldquo;<a href="http://www.infosysblogs.com/sap-mt/../sap/2009/11/fast_close_business_drivers.html#more" target="_blank" title="http://www.infosysblogs.com/sap/2009/11/fast_close_business_drivers.html#more">Fast Close &ndash; Business Drivers</a>&rdquo;. If fast close is so useful then why it isn&rsquo;t the norm rather than exception? The answer to this question is in understanding the various business challenges that hinder the close process.</p>  ]]>
        <![CDATA[<!--[if gte mso 9]><xml>  <o:OfficeDocumentSettings>   <o:AllowPNG/>  </o:OfficeDocumentSettings> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:WordDocument>   <w:View>Normal</w:View>   <w:Zoom>0</w:Zoom>   <w:TrackMoves/>   <w:TrackFormatting/>   <w:PunctuationKerning/>   <w:ValidateAgainstSchemas/>   <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>   <w:IgnoreMixedContent>false</w:IgnoreMixedContent>   <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>   <w:DoNotPromoteQF/>   <w:LidThemeOther>EN-US</w:LidThemeOther>   <w:LidThemeAsian>X-NONE</w:LidThemeAsian>   <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>   <w:Compatibility>    <w:BreakWrappedTables/>    <w:SnapToGridInCell/>    <w:WrapTextWithPunct/>    <w:UseAsianBreakRules/>    <w:DontGrowAutofit/>    <w:SplitPgBreakAndParaMark/>    <w:DontVertAlignCellWithSp/>    <w:DontBreakConstrainedForcedTables/>    <w:DontVertAlignInTxbx/>    <w:Word11KerningPairs/>    <w:CachedColBalance/>    <w:UseFELayout/>   </w:Compatibility>   <m:mathPr>    <m:mathFont m:val="Cambria Math"/>    <m:brkBin m:val="before"/>    <m:brkBinSub m:val="&#45;-"/>    <m:smallFrac m:val="off"/>    <m:dispDef/>    <m:lMargin m:val="0"/>    <m:rMargin m:val="0"/>    <m:defJc m:val="centerGroup"/>    <m:wrapIndent m:val="1440"/>    <m:intLim m:val="subSup"/>    <m:naryLim m:val="undOvr"/>   </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"   DefSemiHidden="true" DefQFormat="false" DefPriority="99"   LatentStyleCount="267">   <w:LsdException Locked="false" Priority="0" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Normal"/>   <w:LsdException Locked="false" Priority="9" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="heading 1"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/>   <w:LsdException Locked="false" Priority="39" Name="toc 1"/>   <w:LsdException Locked="false" Priority="39" Name="toc 2"/>   <w:LsdException Locked="false" Priority="39" Name="toc 3"/>   <w:LsdException Locked="false" Priority="39" Name="toc 4"/>   <w:LsdException Locked="false" Priority="39" Name="toc 5"/>   <w:LsdException Locked="false" Priority="39" Name="toc 6"/>   <w:LsdException Locked="false" Priority="39" Name="toc 7"/>   <w:LsdException Locked="false" Priority="39" Name="toc 8"/>   <w:LsdException Locked="false" Priority="39" Name="toc 9"/>   <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/>   <w:LsdException Locked="false" Priority="10" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Title"/>   <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/>   <w:LsdException Locked="false" Priority="11" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/>   <w:LsdException Locked="false" Priority="0" Name="Hyperlink"/>   <w:LsdException Locked="false" Priority="22" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Strong"/>   <w:LsdException Locked="false" Priority="20" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/>   <w:LsdException Locked="false" Priority="59" SemiHidden="false"    UnhideWhenUsed="false" Name="Table Grid"/>   <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/>   <w:LsdException Locked="false" Priority="1" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 1"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 1"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 1"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/>   <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/>   <w:LsdException Locked="false" Priority="34" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/>   <w:LsdException Locked="false" Priority="29" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Quote"/>   <w:LsdException Locked="false" Priority="30" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 1"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 1"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 2"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 2"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 2"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 2"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 2"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 3"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 3"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 3"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 3"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 3"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 4"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 4"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 4"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 4"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 4"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 5"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 5"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 5"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 5"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 5"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 6"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 6"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 6"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 6"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 6"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/>   <w:LsdException Locked="false" Priority="19" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/>   <w:LsdException Locked="false" Priority="21" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/>   <w:LsdException Locked="false" Priority="31" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/>   <w:LsdException Locked="false" Priority="32" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/>   <w:LsdException Locked="false" Priority="33" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Book Title"/>   <w:LsdException Locked="false" Priority="37" Name="Bibliography"/>   <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/>  </w:LatentStyles> </xml><![endif]--> <!--[if gte mso 10]> <style>  /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-priority:99; 	mso-style-qformat:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin:0in; 	mso-para-margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:10.0pt; 	font-family:"Times New Roman","serif";} </style> <![endif]-->  <p style="text-align: justify" class="MsoNormal">Close process from data processing perspective can be split into data collection, data consolidation and data reporting. Each of these stages has their own unique challenges that impose a time bound hurdle towards fast close. Business and IT staff spend so much time during close cycle in resolving these issues that a targeted fast close becomes impossible to achieve. Let&rsquo;s discuss some of these challenges in detail.</p>  <p style="text-align: justify" class="MsoNormal">&nbsp;</p>  <p style="text-align: justify" class="MsoNormal"><strong>Data Collection</strong></p>  <p style="text-align: justify" class="MsoNormal">Data collection objective is to collect data from all the data sources and translate it into one common view (data normalization) on the basis of common set of definitions.</p>  <p style="margin-left: 0.5in; text-align: justify; text-indent: -0.25in" class="MsoNormal"><!--[if !supportLists]--><em><span><span>a)<span style="font-family: &quot;Times New Roman&quot;; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span></em><!--[endif]--><em>Mixed IT Environment</em></p>  <p style="margin-left: 0.5in; text-align: justify" class="MsoNormal">Global Organizations often utilize multiple ERP and legacy applications. The data across these applications is often not standardized (like GL Accounts, Plant codes, etc). Mixed IT environments with non-standardized data definitions result in data mapping, transfer and reconciliation effort.</p>  <p style="margin-left: 0.5in; text-align: justify; text-indent: -0.25in" class="MsoNormal"><!--[if !supportLists]--><em><span><span>b)<span style="font-family: &quot;Times New Roman&quot;; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span></em><!--[endif]--><em>Data Accuracy</em></p>  <p style="margin-left: 0.5in; text-align: justify" class="MsoNormal">Period close involves data from multiple functional areas (like financial, forecasting, budgeting, etc). A lot of organizations still maintain most of the non-financial data offline in excel spreadsheets. Offline maintenance and manual entry raises data accuracy concerns.</p>  <p style="margin-left: 0.5in; text-align: justify; text-indent: -0.25in" class="MsoNormal"><!--[if !supportLists]--><em><span><span>c)<span style="font-family: &quot;Times New Roman&quot;; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span></em><!--[endif]--><em>Complex Business Model</em></p>  <p style="margin-left: 0.5in; text-align: justify" class="MsoNormal">Complex business models and global operations lead to complexity in data collection by multiple teams. There can be processes that extend outside the organization to supply chain partners and customers that complicate the data collection process further.</p>  <p style="text-align: justify" class="MsoNormal">&nbsp;</p>  <p style="text-align: justify" class="MsoNormal"><strong>Data Consolidation</strong></p>  <p style="text-align: justify" class="MsoNormal">Data consolidation objective is to process the normalized data according to the accounting rules provided by the relevant accounting bodies. </p>  <p style="margin-left: 0.5in; text-align: justify; text-indent: -0.25in" class="MsoNormal"><!--[if !supportLists]--><em><span><span>a)<span style="font-family: &quot;Times New Roman&quot;; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span></em><!--[endif]--><em>Foreign Subsidiaries</em></p>  <p style="margin-left: 0.5in; text-align: justify" class="MsoNormal">Subsidiaries in different countries have different reporting needs that are based on currency translation.</p>  <p style="margin-left: 0.5in; text-align: justify; text-indent: -0.25in" class="MsoNormal"><!--[if !supportLists]--><em><span><span>b)<span style="font-family: &quot;Times New Roman&quot;; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span></em><!--[endif]--><em>Inter-company transactions</em></p>  <p style="margin-left: 0.5in; text-align: justify" class="MsoNormal">Inter-company reconciliation and eliminations is a time consuming task.</p>  <p style="margin-left: 0.5in; text-align: justify; text-indent: -0.25in" class="MsoNormal"><!--[if !supportLists]--><em><span><span>c)<span style="font-family: &quot;Times New Roman&quot;; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span></em><!--[endif]--><em>Accruals and other closing adjustments</em></p>  <p style="text-align: justify" class="MsoNormal">&nbsp;</p>  <p style="text-align: justify" class="MsoNormal"><strong>Data Reporting</strong></p>  <p style="text-align: justify" class="MsoNormal">Data reporting objective is to provide internal (management) and external (statutory) reports on the consolidated data. The data reporting complexity arises due to the diversity of reports (Financial statements, cash flow, tax, inventory, etc) that are required by various countries in different formats, currencies and according to different accounting standards.</p>  <p style="text-align: justify" class="MsoNormal">&nbsp;</p>  <p style="text-align: justify" class="MsoNormal">The various business challenges have a cumulative impact on close timelines. The reason why majority of the organizations have not been able to achieve fast close is because of the drain these challenges impose on resources and timelines. However, these challenges can be resolved from people, process and technology perspective. Wait for my next post on what SAP has to offer to automate and resolve these challenges.</p>  ]]>
    </content>
</entry>
<entry>
    <title>Food Safety and Traceability in CPG Industry (Part 2 of 2)</title>
    <link rel="alternate" type="text/html" href="http://www.infosysblogs.com/sap/2009/12/food_safety_and_traceability_i_1.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.infosysblogs.com/sap-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=88" title="Food Safety and Traceability in CPG Industry (Part 2 of 2)" />
    <id>tag:www.infosysblogs.com,2009:/sap//1.88</id>
    
    <published>2009-12-22T16:15:04Z</published>
    <updated>2009-12-22T16:28:57Z</updated>
    
    <summary>In my last post I outlined the various challenges faced by the CPG industry and specifically discussed the Food Safety and Traceability needs.In this post I will explain how the Food Safety and Traceability needs can be addressed by SAP....</summary>
    <author>
        <name>Abhishek Tare</name>
        
    </author>
            <category term="SAP Solutions" />
    
    <content type="html" xml:lang="en" xml:base="http://www.infosysblogs.com/sap/">
        <![CDATA[<p>In my last post I outlined the various challenges faced by the CPG industry and specifically discussed the Food Safety and Traceability needs.</p><p>In this post I will explain how the Food Safety and Traceability needs can be addressed by SAP.</p>]]>
        <![CDATA[<p>How SAP can help?</p><p>Today companies must increase efficiencies, reduce costs, and ensure compliance with food regulations over the whole supply chain. Hampered by a legacy of nonintegrated systems that impede visibility and perpetuate inefficiencies, many companies recognize the need to standardize on a single platform.</p><p>SAP has the necessary features already inbuilt for handling food safety and traceability. Safety measures can be implemented in the whole process chain, right from procurement of raw materials from supplier, during production of goods in the plant till the delivery of the finished product to the customer / end consumer.</p><p>SAP can help the CPG industry with:</p><ul><li>Track, monitor, and trace batches and inventory</li><li>Streamline procurement, production and sales processes</li><li>Manage sales returns</li><li>Enable targeted product recalls</li></ul><p>Lets take a look at the solutions available in SAP to address all of these challenges.</p><p>1) Batch Management: <br />Following are some of the features of batch management process in SAP:</p><ul><li>Batch Number Assignment: You use this function to assign a batch with a number that uniquely identifies it. </li><li>Batch Specification: You use this function to describe each batch uniquely using characteristics and characteristic values. You specify the permitted value range in the allocated material master record. </li><li>Batch Status Management: You use this function to indicate if the batch is usable or unusable, manually in the batch master record/during goods receipt or automatically in the usage decision in QM.</li><li>Batch Determination: With this function you can use various search criteria to search for batches that are in stock, eg. When posting goods issue, when creating a delivery, etc.</li><li>Batch Where-used List: The batch where-used list shows the path of the batch from its procurement to its delivery to the customer. </li><li>Active Ingredient Management: You use this function to administrate and process materials with active ingredients that are to be handled in batches. <br />&nbsp;</li></ul><p>2) Quality Management: <br />In order to align with legislation and regulations around food safety by FDA and other authorities (e.g., EU Dir. 178/2002, the U.S. Bioterrorism Act of 2002) SAP can help in maintaining quality standards on food safety.</p><p>In order to comply with HACCP (Hazard Analysis &amp; Critical Control Points) a regular planned SAP quality inspection of the food processing during procurement, production and delivery can ensure the safety of the food products.</p><p>SAP can help Food safety through Quality planning, Quality inspection, recording of laboratory analysis, Quality reporting and Quality improvement.</p><p>Benefits:</p><ul><li>Reduced penalty risk</li><li>Decreased risk of food-safety compensation payments </li><li>Reduced risk of bad reputation</li><li>Lower operating costs</li></ul><p>3) Handling Unit Management: <br />Due to the increased global networking of manufacturers, forwarding agents, merchants, and consumers, the communication between all those involved in the supply chain is becoming more and more important. A common numbering standard that is defined by the international standardization organizations (UCC, EAN International) forms the basis for efficient processing in this field.</p><p>These standards include the UCC/EAN128 and one of its sub-components, the Serial Shipping Container Code (SSCC), which can be used to identify the handling units that were shipped. Within the supply chain, handling unit data can be transferred from one section to the next, for example, through EDI with EDIFACT or EANCOM standards using the UCC/EAN128 and the SSCC.</p><p>A handling unit is a physical unit that consists of the packaging materials (load carrier / packaging material) and the goods contained therein. A handling unit is always a combination of materials and packaging materials.</p><p>In SAP Handling Unit Management (HUM) for Food Safety the SSCCs assigned as unique numbers as the handling unit is created. These numbers then serve to identify and track the handling units. The EAN128 numbering system is integrated in the SAP packing function (Handling Unit Management).</p><p>In SAP, Master Data can be maintained for packaging instructions and packaging instructions determination records. Handling units can be created at the time of packing in Process Order or at the time of creating a delivery in the sales cycle.</p><p>4) Batch Recall:</p><p>When a food item with a defect batch is identified then it must be recalled from customers and prospects who received / could receive the batch.</p><p>SAP has the functionality to find and recall a defective batch already delivered to a customer and trigger batch specific returns processing.</p><p>After the customer has received his order and he realizes that the batch is defective, he notifies the vendor. The vendor creates a sales activity to begin a direct mailing to all recipients of the defective batch. Once the mailing list is determined, the letters are printed. This action automatically completes the first sales activity and subsequently creates individual follow-up sales activities per customer, like creation of returns document and returns delivery.</p><p>The quality inspection takes place after the returned goods have been received and booked into Returns. During GR for returns a quality inspection lot is automatically created. After quality inspection, the further handling of the returned goods is decided, like transferring the goods to unrestricted used stock or blocked stock.</p><p>The origin of the defective batch can be identified all the way up to the vendor who supplied the raw material.</p><p>5) Customer Returns:</p><p>The process of Customer Returns or Sales Returns can also be handled in SAP. </p><p>The returns order and delivery are created while the goods are in blocked storage. The credit memo is created based on the analysis results of the lab. The optional credit memo or full goods depends on the analysis results. Thereafter, the subsequent order settlement is done. </p><p>Food Safety and Traceability&nbsp;is one of the key challenges in the CPG industry. To effectively compete in this environment, the CPG companies must address the food safety and traceability requirements of various markets/geographies. SAP being the market leader in the ERP technology space, addresses all the challenges posed by the food safety and traceability needs of the CPG industry.</p><p>Do share your views on this and also if you are from this Industry then let me know how you are addressing this issue.</p>]]>
    </content>
</entry>
<entry>
    <title>How could digital marketing impact your company processes and systems?</title>
    <link rel="alternate" type="text/html" href="http://www.infosysblogs.com/sap/2009/12/how_could_digital_marketing_im_1.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.infosysblogs.com/sap-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=86" title="How could digital marketing impact your company processes and systems?" />
    <id>tag:www.infosysblogs.com,2009:/sap//1.86</id>
    
    <published>2009-12-21T09:54:02Z</published>
    <updated>2009-12-21T21:00:41Z</updated>
    
    <summary>The blog talks about digital marketing and how digital marketing can impact company processes and information systems.</summary>
    <author>
        <name>Lorenzo Pagani</name>
        
    </author>
            <category term="SAP Solutions" />
    
    <content type="html" xml:lang="en" xml:base="http://www.infosysblogs.com/sap/">
        <![CDATA[<p>For the last months there have been huge debates regarding the use of digital communication channels for promoting products and services, and overall digital marketing seems to be in constant growth.<br />How this costant growth will impact your company in order to get best results?</p><p>&nbsp;</p>]]>
        <![CDATA[<p>Nowadays a huge spectrum of channels and sophisticated tools are available:</p><p>&nbsp;First of all the Internet has enriched its early phase tools (e.g. email, banner ads, dedicated websites, pop up ads, sponsored content, paid search) with emerging &ldquo;vehicles&rdquo; such as social media platforms, virtual worlds, blogs, online gaming, wikis, and widgets.<br /><br />&nbsp;Secondly Mobile channel is going beyond SMS and MMS allowing mobile web, video and content download, and dedicated applications.<br /><br />&nbsp;Finally we can also consider digital outdoors like digital video displays and interactive kiosks.</p><p>Market forecasts are confirming this growth, predicting that digital market spending should reach up to 20% of total advertising expenditure by 2012-2013 from the current 10-12 percent.</p><p>What is relevant is that the spend increase should come not only from the industries that have been until now the pioneers and big spenders in digital media (like financial services, computer and communication, and automobile) but also from industries that have dedicated until now limited resources and a small percentage of total spending. </p><p>Particularly CPG industries that are among the top advertisers in traditional media are now also going to focus on digital marketing and increase in a relevant way their investments.</p><p>What are the reasons that are accelerating the use of digital channels?<br />In my opinion there are four main reasons: </p><p>&nbsp;The economic downturn is pushing for innovation in an attempt to explore and adopt cheaper and more effective ways to reach the customers.<br /><br />&nbsp;Internet and mobile device population as well as the amount of time spent by the user on the Internet or using mobile applications are constantly increasing.&nbsp; <br />What&rsquo;s more, digital channels are going to represent the 1st choice of communication media among young people.<br /><br />&nbsp;The consumer is doing more and more pre-shopping on line: gathering information, consulting blogs, reading expert opinions and user feedbacks. <br /><br />&nbsp;Digital channels allow interacting with the customer in a very personalized and targeted way and, in case of the mobile, in real time. <br />These characteristics could allow for the development of very innovative approaches. <br />For instance through the mobile channel a CPG company could recognize the presence of its customer in the shop when he is buying and reach him with a timely and personalized instant message and promotion.</p><p>In which areas will an extensive use of digital marketing channels impact&nbsp;a CPG&nbsp;company, or which capabilities will&nbsp;the company need in order to obtain best results?<br /><br />&nbsp;Multichannel Campaign management: With digital marketing we see a proliferation of channels. The marketing campaign will be more and more executed across a mix of traditional and digital channels.<br />Therefore it will be critical to have processes and platforms that support preparation, execution and control of the campaign across channels and as well as tools that allow comparison of the effectiveness of each channel. </p><p>&nbsp;Customer data management: In the digital world quality and quantity of information available on the customer (e.g. demographic attributes) will dramatically increase. <br />Also the customer data will come from different sources because of the proliferation of communication channels.<br />A company needs, therefore, to improve its capability to collect, manage, and integrate the digital data with traditional media data and to make it available for sophisticated analysis. </p><p>&nbsp;Direct and personalized communication: Direct and personalized communication with the consumer such as the use of emails will constantly increase as will the possibility to provide other types of content (e.g. videos, gadgets, dedicated promotions) according to the specific characteristics of the customer.</p><p>&nbsp;Digital content creation and management: Content will be highly personalized, used and consumed faster, while being made available in different formats and through different channels. </p><p>&nbsp;Data analysis: Digital channels provide huge quantities of highly measurable customer data.&nbsp; On this subject, two aspects will be key. Firstly, specifically for the Internet channel, the capacity to analyze navigation behaviour of the customer on the web is critical. Secondly it is necessary to maximize the capacity to analyze customer data gathered from multiple sources in order to define a model of customer behaviour along the complete purchasing process.</p><p>What is your point of view on this? Your thoughts are highly appreciated and more than welcome.<br />I will blog again providing more thoughts on digital marketing impacts going deeper into the aspects related to information systems and how vendors are ready to support them.</p>]]>
    </content>
</entry>
<entry>
    <title>Food Safety and Traceability in CPG Industry (Part 1 of 2)</title>
    <link rel="alternate" type="text/html" href="http://www.infosysblogs.com/sap/2009/12/food_safety_and_traceability_i.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.infosysblogs.com/sap-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=85" title="Food Safety and Traceability in CPG Industry (Part 1 of 2)" />
    <id>tag:www.infosysblogs.com,2009:/sap//1.85</id>
    
    <published>2009-12-17T16:58:08Z</published>
    <updated>2009-12-18T04:13:25Z</updated>
    
    <summary>This post outlines the Food Safety and Traceability needs of the CPG industry.</summary>
    <author>
        <name>Abhishek Tare</name>
        
    </author>
            <category term="SAP Solutions" />
    
    <content type="html" xml:lang="en" xml:base="http://www.infosysblogs.com/sap/">
        <![CDATA[<p>These are challenging times for the Consumer Packaged Goods (CPG) industry. Food safety, traceability, health-conscious consumers, retailer power, new regulations and corporate social responsibility are some of the key challenges faced by the CPG industry. Fierce competition and industry consolidation are placing enormous pressure on food companies to cut costs. Meanwhile, increasingly sophisticated consumers are demanding greater levels of corporate accountability as well as constant product and service innovation. These forces are causing food companies to search for new ways to improve margins, increase asset efficiency, manage food safety risks, and grow revenues. This post outlines the Food Safety and Traceability needs of the CPG industry and in my next post I will explain how these needs can be addressed by SAP.</p>]]>
        <![CDATA[<p>Addressing consumer concerns over Food Safety, Integrating legislation and regulations around Food Safety and tracking, monitoring and tracing products are some of the key business requirements in the Food Safety and Traceability space.</p><p>Why is Food Safety a key issue today?</p><p>Food safety is a worldwide issue affecting hundreds of millions of people who suffer from diseases caused by contaminated food. The World Health Organization (WHO) calls it &quot;one of the most widespread health problems and an important cause of reduced economic productivity&quot;. </p><ul><li>Annually, over 3 million children under the age of 5 die of diarrheal diseases among approximately 1,500 million episodes of diarrhea in developing countries. 70% of these incidences are attributed to food borne illness. </li><li>6.5 million to 80 million cases of food borne illness occur annually in the United States. </li><li>About 13 million children under the age of 5 die each year from infections and malnutrition, most often attributable to contaminated food. </li><li>Serious and chronic health effects of food borne illness present an additional burden on the health care system, and affect an estimated 3 of every 1,000 prenatal infants. </li><li>The estimated annual medical costs/productivity losses due to the 7 major food borne pathogens range from $6.6 billion to $37.1 billion, according to USDA and Centers for Disease Control and Prevention (CDC) figures. </li></ul><p>You can refer to some of the most high profile news articles related to Food recall in US from the recent past:</p><p><a href="http://www.fda.gov/Safety/Recalls/MajorProductRecalls/Peanut/default.htm">http://www.fda.gov/Safety/Recalls/MajorProductRecalls/Peanut/default.htm</a></p><p><a href="http://www.fda.gov/Safety/Recalls/MajorProductRecalls/Milk/default.htm">http://www.fda.gov/Safety/Recalls/MajorProductRecalls/Milk/default.htm</a></p><p><a href="http://www.fda.gov/Safety/Recalls/MajorProductRecalls/Pistachio/default.htm">http://www.fda.gov/Safety/Recalls/MajorProductRecalls/Pistachio/default.htm</a></p><p>Having looked at Food Safety, lets understand what do we mean by Traceability in the food industry.</p><p>What is Traceability?</p><p>&ldquo;Traceability&rdquo; means the ability to track any food, feed, food-producing animal or substance that will be used for consumption, through all stages of production, processing and distribution.</p><p>Why is Traceability needed?</p><ul><li>Traceability is a way of responding to potential risks that can arise in food and feed.</li><li>It is vital that when national authorities or food businesses identify a risk they can trace it back to&nbsp;&nbsp;&nbsp; its source in order to swiftly isolate the problem and prevent contaminated products from reaching consumers.</li><li>In addition, traceability allows targeted withdrawals and the provision of accurate information to the public, thereby minimizing disruption to trade.</li><li>Safeguards against Bioterrorism.</li><li>Fights product counterfeiting.</li><li>Protects and serves brands through quick and accurate access to information.</li></ul><p>With food safety issues being identified almost every month in the EU countries and US, the authorities of EU and US have formulated some strict regulations to contain and eradicate the problem.</p><p>The European Union passed a General Food Law in 2002 &ndash; Regulation EC/178/2002. The details of it are available at the European Commission website - <a href="http://ec.europa.eu/food/food/index_en.htm">http://ec.europa.eu/food/food/index_en.htm</a>. They have also provided guidelines on the implementation of traceability in EU. It is published on their website: <a href="http://ec.europa.eu/food/food/foodlaw/guidance/index_en.htm">http://ec.europa.eu/food/food/foodlaw/guidance/index_en.htm</a>.</p><p>Similarly, US Food and Drug Administration (FDA) has comprehensive guidelines on product specific safety and traceability regulations. The guidelines are available at the FDA website - <a href="http://www.fda.gov/Food/FoodSafety/default.htm">http://www.fda.gov/Food/FoodSafety/default.htm</a>.</p><p>In my next post I will throw some light on how SAP can help address this issue.</p>]]>
    </content>
</entry>
<entry>
    <title>Business Process – Adopting Industry Best Practices (Part 2 of 3)</title>
    <link rel="alternate" type="text/html" href="http://www.infosysblogs.com/sap/2009/12/business_process_adopting_indu_1.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.infosysblogs.com/sap-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=84" title="Business Process – Adopting Industry Best Practices (Part 2 of 3)" />
    <id>tag:www.infosysblogs.com,2009:/sap//1.84</id>
    
    <published>2009-12-15T04:31:01Z</published>
    <updated>2009-12-18T04:13:25Z</updated>
    
    <summary>What ERP Vendors are saying?Sales pitch of many ERP Vendor is that they provide the Business solution based on the Best Practice in your Industry. Many of the Industry leading ERP Vendors are providing bolt-on Industry specific Business processes based...</summary>
    <author>
        <name>Sathyanarayana Krishnamurthy</name>
        
    </author>
            <category term="Energy/Utility" />
    
    <content type="html" xml:lang="en" xml:base="http://www.infosysblogs.com/sap/">
        <![CDATA[<p>What ERP Vendors are saying?</p><p>Sales pitch of many ERP Vendor is that they provide the Business solution based on the Best Practice in your Industry. Many of the Industry leading ERP Vendors are providing bolt-on Industry specific Business processes based on Best Practices in that industry. Some of the leading ERP Vendors provide Best practice base lines products which include Detailed System and process documentation along with pre-configured systems.</p>]]>
        <![CDATA[<p>What we suggest?</p><p>Because Wisdom can not be told; it is important to weigh the cost and benefit of adopting Industry Best practices. Especially in case of COTS products, any deviation from configurable process steps leads to Custom Development, which is always a costly proposition. In a away, when you adopt a COTS product, it is advisable to go with best practices inbuilt in the package. This reduces implementation time and subsequent maintenance cost. But this has to be compared with cost involved in organizational change management.</p><p>The success of your complex IT or ERP Projects primarily depends on the Project Initiation and Project Planning Phase. Unfortunately many companies rush through the Project Initiation &amp; Project Planning Phase. As part of adopting Best Practices from the industry, following are some of the key activities during the Initiation &amp; Planning face:<br />-&nbsp;define the future (TO-BE) business process keeping the strategic business objectives in mind<br />-&nbsp;using consulting support, identify the suitable IT/ ERP Vendor based on your unique needs<br />-&nbsp;Overlay the Business Best Practices to your proposed TO-BE processes and create an alternative fitment/ development needs need<br />-&nbsp;Considering high-value and High-impact processes, create Justification and Return on Investment for modifying the proposed TO-BE Process to converge to Best Practices<br />-&nbsp;Develop an organizational change management, communications, and training plan<br />-&nbsp;Forward looking implementation strategy with Project Plan including internal and external resource identification and deployment, project budgeting, contract negotiations, and quality assurance (QA) planning</p><p>In the third and final post we will see what are the key success factors and benefits that we can get out of it.<br /></p>]]>
    </content>
</entry>
<entry>
    <title>Taking the “giant leap” into the world of Business Objects reporting on SAP</title>
    <link rel="alternate" type="text/html" href="http://www.infosysblogs.com/sap/2009/12/taking_the_giant_leap_into_the.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.infosysblogs.com/sap-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=82" title="Taking the “giant leap” into the world of Business Objects reporting on SAP" />
    <id>tag:www.infosysblogs.com,2009:/sap//1.82</id>
    
    <published>2009-12-10T08:14:56Z</published>
    <updated>2009-12-18T04:13:25Z</updated>
    
    <summary>The blog analyzes the various questions that come up for enterprises which are running SAP BI technology suite and are looking at adopting some of the BO suite offerings. It also offers a thought process on some of considerations for selecting/adopting the BOBJ suite.</summary>
    <author>
        <name>Somnath Mukherjee</name>
        
    </author>
            <category term="Business intelligence" />
    
    <content type="html" xml:lang="en" xml:base="http://www.infosysblogs.com/sap/">
        <![CDATA[<span style="font-family: Arial; font-size: 10pt">The last couple of years have been exciting times in the SAP-Business Intelligence (SAP-BI) space with SAP making a flurry of acquisitions in the Business Intelligence and Enterprise Performance Management (EPM) areas with the big fish being the Business Objects acquisition in the middle of 2007. With the Business Objects acquisition came a host of applications in the area of reporting, data services and EPM, into SAP&rsquo;s kitty. <p>&nbsp;</p></span>]]>
        <![CDATA[<span>Now within the specific area of reporting and BI there were offerings for the various service lines like OLAP analysis, dash-boarding, enterprise, regulatory reporting and so on and so forth. Then SAP took the much predictable route of trying to provide a very tight integration road map of this product suite with its home grown datawarehouse solution, the SAP-BW. In the last two years SAP has also come up with an official roadmap of how each of these products in its enlarged suite would either be evolved or married with another product or retired altogether. <br /></span><span /><span>While this rationalization idea sounds quite logical and the natural way forward but it put quite a few questions and should I dare to say headaches in front of one person. And that is the IT Manager who was till now running his SAP-BI team using the home grown BI products and solutions from SAP. Over the last few months I have had the opportunity of meeting quite a few SAP-BI IT managers of some of our marquee clients and most of them are in a state of confusion. Their main dilemma is on whether to take the &ldquo;giant leap&rdquo; now or to wait and watch for some time to come.<span>&nbsp;</span><br /></span><span /><span>Some of the pertinent questions that are tormenting them at the moment are:<br /></span><span /><span><span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>i.<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span>Should I or should I not start looking at/adopting the BO tool set like WebI/XCelsius/Crystal for my reporting needs?<br /></span><span><span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>ii.<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span>With SAP talking about drawing the curtains for BEx by 2016, should I already start thinking about Pioneer (as and when it is released) or should I adopt a mix of WebI /Crystal/XCelsius, right away?<br /></span><span><span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>iii.<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span>The tools from the BO suite look good and have rich capabilities, how do I go about migrating my current reports on BEx to WebI/XCelsius? Should I go &quot;big-bang&quot; or should I take&nbsp;baby steps? Is a PoC/pilot really required?<br /></span><span><span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>iv.<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span>Last but not least how about my TCO?<span>&nbsp; </span>By paying an upfront license fees and doing a migration do I gain in my TCO over say a 5 years time scale? <br /></span><span /><span>If you are an IT manager running a SAP-BI unit for you organization, I am sure such questions would have definitely crossed your mind and if you have already not done anything&nbsp; about them yet, I am sure you must be thinking very hard by now.<br /></span><span /><p class="MsoNormal"><span>Wish I had a simple solution or a step by step approach to get to the bottom of this well.</span><span>However I would like to propose a thought process&nbsp;around trying to prepare or not to prepare for this &ldquo;giant leap&rdquo;.&nbsp; The following are some of the key considerations that someone should have while thinking about that giant leap.</span></p><span /><strong><span>Does the BO suite fill-in the gaps? </span></strong><span>: First try and see if the tool set that is on offer plugs those white spaces or gaps that exist in your current reporting NEEDS. The features that WebI, XCelsius, Crystal offer are indeed very rich and are positioned for specific needs like analytical reporting, dash-boarding, enterprise reporting respectively. Should your business have some such need(s) which it is not able to realize using BEx/WAD then it does make all the sense to look at the suite. For example a burning desire for power users to be able to create their own reports. However on the other&nbsp; hand should you have strong and compelling reason(s) to believe that your current tool set is largely able to address the business needs then possibly you need to put the considerations in the back burner for the moment. My <em>mantra</em> here is that one should not think of adopting this tool because it is the new gizmo in the block. The driver should rather be some strong business vacuum that&nbsp;this suite&nbsp;should try and fill.<br /></span><span /><strong><span>Test the waters: </span></strong><span><span>&nbsp;</span>Once you have decided that you really have that strong and compelling reasons to look at BO suite of products as they might be able to bridge some of the gaps that your current SAP reporting platform has, you need to test the waters. You could orrather should plan a Proof of Concept (POC) phase which would look at identifying some of your critical reports/dashboards in BEx or WAD and do a migration to WebI or XCelsius as the case may be. In our experience we have seen the PoC phases to be of an immense learning phase where we are able to de-risk, mitigate and plan work around for specific reports/functions. A PoC phase is definitely a MUST HAVE which will not only help you to understand the technical challenges and the magnitude of<span>&nbsp; </span>the same but also to help you get&nbsp;the necessary &ldquo;buy-in&rdquo; from your business community. It would serve as a good phase for business to also understand the nuances of the tool set and find out if it is indeed satisfying their needs and addressing their aspirations and much desired needs.<br /></span><span /><span>Also it is the right time to try and chart out a broad roadmap to perform the migration. This will help give you a clear idea of the detailed activities and an indicative time line to get this done. <br /></span><span /><span /><strong><span>Does it make &ldquo;business sense&rdquo; at<span>&nbsp; </span>the end of the day?: </span></strong><span>Before you actually cut that cheque to settle your license fees- you need to do some back of the envelope calculations as well. Now while all the benefits that you may derive out of your BO investments may not be quantifiable or tangible but you should not definitely look at what realizations you are going to get by saving on IT resources, increased development cycle time, ease of maintenance etc. <br /></span><span /><span>Once you are through with the above steps you should be more or less in a position to either take the plunge or retract your steps. As I said there is no one size that fits all and what makes sense to one organization may not make sense to another and deciding either way may be just alright. But what I have tried to bring to fore is a thought process which I believe should be adopted to decide on whether that giant leap is something worth taking or not. <br /></span>]]>
    </content>
</entry>
<entry>
    <title>Apparel &amp; Footwear Industry</title>
    <link rel="alternate" type="text/html" href="http://www.infosysblogs.com/sap/2009/12/apparel_footwear_industry.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.infosysblogs.com/sap-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=81" title="Apparel &amp; Footwear Industry" />
    <id>tag:www.infosysblogs.com,2009:/sap//1.81</id>
    
    <published>2009-12-08T08:38:27Z</published>
    <updated>2009-12-18T04:13:25Z</updated>
    
    <summary>The blog introduces an apparel and footwear company and talks about the specific characteristics of the industry.</summary>
    <author>
        <name>Arun Kumar Viswanathan</name>
        
    </author>
            <category term="SAP Solutions" />
    
    <content type="html" xml:lang="en" xml:base="http://www.infosysblogs.com/sap/">
        <![CDATA[<p>Even during these troubled economic times, when most of the industries are falling by the side, Apparel and Footwear industry has managed to come up with positive growth numbers year after year (at a global level). With a global market volume of about EUR 300 billion and an annual growth rate of 4 % Apparel and Footwear industry is poised for an exciting journey. The athletic apparel and footwear market, which caters mainly to the sports industry, is about 25% of the overall apparel and footwear market volume.</p>]]>
        <![CDATA[<p>So what exactly is an apparel and footwear company? These are companies that design, manufacture, market, and/or license brands for men's, women's, and/or children's clothing, footwear, and accessories. With increasing focus on cost reduction and the need for responding faster to the market needs, there has been a distinct split in the activities that companies perform in the apparel and footwear space. On one hand we have the brand leaders e.g. Nike, adidas etc.&nbsp; who are involved in design, marketing, and/or licensing brands for men's, women's, and/or children's clothing, footwear, and accessories. On the other hand we have the companies who manufacture the products. Having said that there still are many apparel and footwear companies who perform all the activities themselves. However the trend is to shift the manufacturing operations to a low cost location </p><p>So what is so specific about the industry?</p><p>Global setup: The supply chain of an apparel and footwear industry is truly global in nature. Different partners involved in the supply chain e.g. designers, marketing team, manufacturers, raw material suppliers, customers etc. are spread across the globe.</p><p>Focus on Design: There is a constant focus on design as there is a need to come up with cheaper and innovative products which meet the customer taste and requirement, in order to stay above the competition</p><p>Lead Time: Lead time for product development is high. However there is a constant pressure to shrink the lead time and respond faster to changing market demands</p><p>High Volumes: The product volumes handled are high. This comes from the fact that one single product may have multiple dimensions like different colors, sizes and styles.</p><p>Complex Forecasting: Long lead times, global setup and high volume of products make the forecasting process complex and long drawn. On the other hand growing market pressure forces the companies to reduce the lead time for a new product introduction into the market. In addition forecasting has to be accurate to the SKU level </p><p>Complex Customer Demand: Customer demands are complex and varies based on various criteria like geography, culture, Pricing, period of the year etc.</p><p>Seasonal: Demand is seasonal</p><p>Multiple Distribution Channels: Multiple distribution channels exist in the product distribution. Shrinking margins has forced many of the companies to come up with own retail shops. Web based ordering is also catching up </p><p>Samples Handling: With customer demand becoming complex and with increasing competition companies are having to come up with more and more new products each season. As a result companies have to procure a high number of samples each season. Also the fact that the percentage of samples which end up on the shelf for sale is low does not help the companies. </p><p>Collaboration &amp; Flexibility: The changing retail industry practices combined with the global nature of the supply chain necessitates high degree of shared information and systems integration, flexible manufacturing strategies, stronger planning systems and highly sophisticated order allocation capabilities to meet customer service requirements, both in terms of fill-rate and on-time delivery</p><p>Even with all these challenges and unique setup apparel and footwear industry is growing. Leading software companies like SAP have come up with industry specific solutions (SAP-AFS, SAP APO etc.) to cater to the specific needs of the industry. </p><p>Having said that the collaboration and flexibility requirements combined with the unique industry characteristics is putting pressure on apparel and footwear companies to move from their complex legacy applications based system architecture to a leaner and flexible system architecture which supports them in their growth. This in turn is putting pressure on software companies like SAP to constantly improve their products and also come up with new solutions.</p>]]>
    </content>
</entry>

</feed> 

