EXAMPLES OF GAP ANALYSIS WITH SOLUTIONS RESPECT TO FOLLOWING

Hi,
Please send me the solution to following topics in SD.
1)material determination/product selection.
2)Creation of Customer Master Record and Customer Account Group.
3)Material Listing and Exclusion.
Please email me at [email protected]
Looking forward for your reply,
Thx,
Farhan.

Hi Suren,
AS-IS
you must interact closely with the super users and process owners for collecting requirements based on the Q&A db to understand their current business process like how they manufacture the parts, what steps they use for planning, production execution etc and what legacy systems or interfaces do they use and try to document all this information in the AS-IS processes either using flowcharts etc and get the sign off from the business process owners this is current business process WITHOUT SAP in place
TO-BE
This is what the business client intends to achieve in future WITH SAP implemented, so basically in this analysis, you need to identify what are the business processes that will run using SAP and how SAP will be managing thier day-to day activities and performing SAP Transactions. you also need o document it using either flowcharts and get a sign-off from the process owners as this will be the foundation based on which you will proceed further and develop your blueprint document and also start your realization activities
GAP
it is nothing but the difference between the AS-IS AND TO-BE analysis and here you identify the new changes or gaps between the business process without SAP and with SAP in place, it includes what types of configurations changes you need to make and developments and interfaces that will be needed to bridge the gap between the current state and the future state of business with SAP in place.
Examples of reports not in standard SAP, developments, application of user exits etc.., come under GAP
based on these three steps you then proceed to prepare your business blueprint document
Reward if useful and close the thread
Keerthi

Similar Messages

  • EXAMPLES OF GAP ANALYSIS & Workaround for the respective GAPs

    PP members:
    I  am looking for couple of <b>GAP Analysis  examples</b> which one might have come across during implementation & support projects and what was the work around for the respective <b>GAPs</b>
    If any one is interested in sharing documents related to AS_IS, TO-BE & GAP Analysis for PP module, I will be thankful
    email id: [email id removed]
    thanks in advance
    Please do not ask for documents to be sent to your email ids.
    Message was edited by:
            Somnath Manna

    Hi Suren,
    AS-IS
    you must interact closely with the super users and process owners for collecting requirements based on the Q&A db to understand their current business process like how they manufacture the parts, what steps they use for planning, production execution etc and what legacy systems or interfaces do they use and try to document all this information in the AS-IS processes either using flowcharts etc and get the sign off from the business process owners this is current business process WITHOUT SAP in place
    TO-BE
    This is what the business client intends to achieve in future WITH SAP implemented, so basically in this analysis, you need to identify what are the business processes that will run using SAP and how SAP will be managing thier day-to day activities and performing SAP Transactions. you also need o document it using either flowcharts and get a sign-off from the process owners as this will be the foundation based on which you will proceed further and develop your blueprint document and also start your realization activities
    GAP
    it is nothing but the difference between the AS-IS AND TO-BE analysis and here you identify the new changes or gaps between the business process without SAP and with SAP in place, it includes what types of configurations changes you need to make and developments and interfaces that will be needed to bridge the gap between the current state and the future state of business with SAP in place.
    Examples of reports not in standard SAP, developments, application of user exits etc.., come under GAP
    based on these three steps you then proceed to prepare your business blueprint document
    Reward if useful and close the thread
    Keerthi

  • Gap analysis with respect to chemical/paint/textil

    what are the gaps found in a Chemical/Paint manufacturing and a Textile company? can anyone explain that please

    Hi,
    Once you will start discussing with client, then only you can identify the Gaps in SAP for any kind of industry.
    It depands upon client requirement.
    Regards,
    manish

  • What are the GAP analysis? could you pls... explain with examples?

    hi everybody.....
    may i know what are the GAP analysis with examples?
    thanks in advance...
    and hope u will get it me that.

    Dear arunteja vasan ,
    GAP Analysis
    A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can can't do.   For each gap there will be one of three outcomes which must be recorded and actioned, GAP must be closed and customised software can be developed close the gap, GAP must be closed but software cannot be written therefore a workaround is required, GAP does not need to be closed.
    In simple terms: Gap means small cracks. In SAP world.  In information technology, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.
    Actual gap analysis is time consuming and it plays vital role in blue print stage.
    Cut Over Plans
    Detailed plans need to be developed for cutting over from the old system(s) to the new.   Parallel runs of what will happen over the conversion period using test data, convert and watch for a period after wards to ensure nothing unexpected happens.
    Train Users
    Well trained users will support and defend the system on site.  Unsupportive users will continually undermine the system and eventually it will be replaced.   Therefore the more effort you put into helping the users master the system early the better.
    Do award points if you found them useful.
    Regards,
    Rakesh

  • Very urgent-gap analysis -two examples

    please explain me with examples of gap analysis and how do you fill the gap
    and also there are two movement types in schedule line cat , what is the purpose of two
    early responders will be definitely rewarded
    thanks & regards

    GAP Analysis
    A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and actioned, GAP must be closed and customised software can be developed close the gap, GAP must be closed but software cannot be written therefore a workaround is required, GAP does not need to be closed.
    In simple terms: Gap means small cracks. In SAP world. In information technology, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.
    Actual gap analysis is time consuming and it plays vital role in blue print stage.
    Cut Over Plans
    Detailed plans need to be developed for cutting over from the old system(s) to the new. Parallel runs of what will happen over the conversion period using test data, convert and watch for a period after wards to ensure nothing unexpected happens.
    Train Users
    Well trained users will support and defend the system on site. Unsupportive users will continually undermine the system and eventually it will be replaced. Therefore the more effort you put into helping the users master the system early the better. Fit gap means, before implementing the SAP all the business data is in the form of documents, we cannot keep this data as is in the SAP. There should be a gap. So by filling this gap, we make configuration with the help of these documents. This is called as fit gap analysis.
    GAP Analysis
    A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and actioned, GAP must be closed and customised software can be developed close the gap, GAP must be closed but software cannot be written therefore a workaround is required, GAP does not need to be closed.
    In simple terms: Gap means small cracks. In SAP world. In information technology, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.
    Actual gap analysis is time consuming and it plays vital role in blue print stage
    The Gaps can differ from company to company. Most commonly, however, missing functionality is industry-specific.
    Examples:
    1. MGM Studios and Lycos sometime back worked with SAP to develop its new intellectual property management and media advertising management functionality, respectively.
    2. A leading Oral care product company wanted the promotion of free-goods where they wanted 'Buy one get 2 different products free'.
    through gap analysis will identify the gaps between how the business operates ad its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and actioned, GAP must be closed and customised software can be developed close the gap, GAP must be closed but software cannot be written therefore a workaround is required, GAP does not need to be closed.
    In simple terms: Gap means small cracks. In SAP world. In information technology, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.
    Actual gap analysis is time consuming and it plays vital role in blue print stage.
    Ex, The functionality that is not present in Standard SAP and adding it to suit the business requirements. In Credit memo request document type, creating Credit block automatically for those Credit memos above Rs 5000.
    ***reward if this helps**

  • Gap Analysis in BW/BI

    Guys!!
    Please Explain Gap Analysis with some examples in BW/BI.
    Thanks in Advance
    Venkat

    Hi Venkat,
    Gap Analysis is done to find the gaps between Client (User) requirements and existing Business Content in the SAP Business Intelligence Application.
    This gives so much of information about the  client existing Business Process and the required  reporting requirements clearly to customize the  application to satisfy the needs and demands.
    It also gives the effort estimation to plan the project effectively and deliver the required requirements clearly to the client.
    Technically, we can estimate the requirements clearly and have a clear road map to effectively deliver the project with out much hassles.
    Hope it has given some insight.....

  • A bit confused with your Gap Analysis example

    Hi Robert,
    As I analyzed your Gap Analysis example, I getting a bit confused.
    In your message below, with the 0 in the 0Customer, aren’t you already (by BW convention), assuming that 0Customer is a <b>standard business content object</b>?
    ... but you also in the same statement noted that “..and <b>std business content</b> doesn't provide it in your extractor…”
    I am thinking, it is a business content object already, why does he say the source system doesn’t provide it?
    Also, what were you referring to as “in your extractor” did you mean in  the “source system”?
    <b>Quote from Robert</b> “Gap analysis process has to be performed when you know that you can use a std business content extractor (or cube or something else) and you have to compare it yo your actual requirements: do you need 0CUSTOMER and std business content doesn't provide it in your extractor...well, now you have done a gap analysis !”
    ====

    Caud,
    sorry, but I think that Praveen explanation doesn't exactly match with what do you need to know...
    The Gap Analysis Fit is a step inside an ideal business blueprint of a BW project implementation (but, clearly, the same concept can be applied to several situation...).
    During this step, after having collected all the client's requirements, you have to higlight what you need (or what you can) to use to build what the user wants.
    In this analysis, you find that a business content datasource (found via help.sap.com or after the SDN's forum suggestion or...) can provide almost all the required fields (since a datasource is a collection of several fields..).
    Anyway, notwithstanding this, you realize that this datasource is good only for a 95%, because it's missing the info related to the customer (usually shown with 0CUSTOMER object, but you can use a ZCUSTOMER or something else...the only important thing is that you need this info!).
    Ok, you know that in order to fit this gap, you have to build your own enhancement with a little userexit to fill this missing field: THIS IS THE GAP ANALYSIS FIT !!!
    This explanation applies also to a std cube, to a std query and so on...
    Sure, you use std business content, but why you ask "why does he say the source system doesn’t provide it" ???
    The std objects can't provide always all we need, but only, if we are lucky, a part (more or less) of it...and at this point you need to perform this kind of analysis...
    Hope now is clearer...
    Bye,
    Roberto

  • Can you provide some real time example of Fit Gap analysis .

    Hi all,
    Can you provide some real time example of Fit Gap analysis related to Functional.
    Regards
    Reddy

    hi,
    In my opinion and experience both functional and technical staff playkey roles in the fit-gap meetings and in the subsequent review of thefit-gap deliverable (which lists business requirements, fits, gaps, andalternatives to fill the gaps). Ideally the technical staff possessessignificant functional / business experience at least with that moduleso that he/she can help determine the cost/effort/technical scope if acustomization or interface is the preferred way to fill a particulargap. The fit-gap goes a long way in determining the overall scope ofthe implementation or upgrade project and is a critical success factor.It also needs to be completed very early in the project so thatresulting customizations and interfaces can be designed, created, andunit tested before the system test phase.
    Thx,
    waseem

  • Example of SAP HR GAP analysis

    Hi all,
    Can anybody pls tell me an example of GAP found during GAP analysis in either SAP Payroll or TM? I did search the forum but there are mostly definitions of GAP analysis.
    Useful answers will be awarded.
    Thank you
    R S

    Hi,
    GAP is some thing where Software consultant give BEST business pratics to the client which is running across all over the world and which is also support SAP application and client is not accept the changes which is recommoanded by consulant. So this is GAP. All in broad way GAP is difference between software
    consultant view and client view clash at some point.
    GAP analysis is done in Blue Print stage. It aims to understand what can be done with the standard SAP and how the client actually wants a particular scenario to be processed. And to understand the GAP between the actual & required scenarios.
    Hope this helps,

  • GAP ANALYSIS AND TICKETS

    hi Gurus,
    I need some 6 real time examples relating to Gap Analysis and Tickets of SAP SD. Please could you send me all the details with the scenarios and solutions to my email if [email protected]
    Thanks,
    Farhan.

    Hi Farhan,
    Gap means small cracks. In SAP world or in Information Technology world, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be."
    Gap Analysis is undertaken as a means of bridging that space. Actual Gap Analysis is time consuming and it plays vital role in Business Blueprint [AS IS Process] stage.
    A through Gap Analysis will identify the gaps between how the business operates and its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and auctioned,
    1. GAP must be closed and customized software can be developed
    2. GAP must be closed but software cannot be written therefore a workaround is required
    3. GAP does not need to be closed.
    A point worth mentioning here is that at time people confuse between user-exits and Gap Analysis. User exits are standard gate ways provided by SAP to exit the standard code and we can write our own code with the help of ABAP workbench, its not new functionality which we are trying to build in sap but its slight enhancement within the same code.
    Gap analysis is start point of Realization and once business Blueprint is finished we have to find the realization of sap system for client requirement and there will be certain gaps when compared to system fit. Those gaps can be closed either by re-engineering of business process to fit with SAP or we have to use USER exits in case of small deviations or complete enhancements with the help of ABAP to fit with the SAP system.
    The Gaps can differ from company to company. Most commonly, however, missing functionality is industry-specific.
    Examples:
    1. MGM Studios and Lycos sometime back worked with SAP to develop its new intellectual property management and media advertising management functionality, respectively.
    2. A leading Oral care product company wanted the promotion of free-goods where they wanted 'Buy one get 2 different products free'.
    A2. A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can and can't do. For each gap there will be one of three outcomes which must be recorded and actioned.GAPs must be closed and therefore customized software can be developed to close the gap. In some cases GAP must be closed but software cannot be written therefore a workaround is required in other words a business process change is recommended to the client.
    In simple terms: Gap means small cracks. In SAP world. In information technology, gap analysis is the study of the differences between two different information systems or applications (ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.
    Actual gap analysis is time consuming and it plays vital role in blue print stage.
    Please Reward If Really Helpful,
    Thanks and Regards,
    Sateesh.Kandula

  • How to do GAP analysis ?

    Hi Experts,
    How to do GAP analysis ? I have a BW problem statement about SD module. I have to do a GAP analysis. I am doing it for the first time. So any suggestion about the approach to start it ?
    Thanks

    The gap analisys is the analisys on what are the difeerences between actul system and what the customer want to develop.
    GAP Analysis in simpler terms refers to study of existing state of system and desired state of system, there by identifying the gap between states. In the context of SAP, GAP analysis is very important before implementation of SAP system. The implementation team should study what is that an SAP system can provide for each business process and what is the actual business process. One should evaluate each such gap and should find out the ways to fill the gap. The gap might be filled in different ways: System enhancements, custom ABAP code development, interfaces with some other external systems. etc.
    In the Enterprise Systems field, GAP Analysis is a process done while bleprinting the solution and aimed to discover the gaps between the user requirements and the "off-the-shelf" (or packaged) solution. For example you want to implement an ERP system , you do a GAP Analysis to assess gaps between the processes supported by that System and the process as executed by the organization that will be implementing the solution.
    In the SAP BI area, we do a GAP Analysis to map between our logical and physical BI solution design and the Business Content that SAP offers. Business Content is a set of preconfigured BI objects aimed to save us valuable time when developing BI solutions by providing the "best practices" for that functional domain.
    The reason we do a GAP analysis in BI is to find out whether we can save ourselves a lot of time by implementing a Business Content solution instead of developing from scratch.
    In simple terms: Gap means small cracks. In SAP world or in Information Technology world, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be."
    Gap Analysis is undertaken as a means of bridging that space. Actual Gap Analysis is time consuming and it plays vital role in Business BlueprintAS IS Process stage.
    A through Gap Analysis will identify the gaps between how the business operates and its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and actioned,
    1. GAP must be closed and customised software can be developed
    2. GAP must be closed but software cannot be written therefore a workaround is required
    3. GAP does not need to be closed.
    A point worth mentioning here is that at time people confuse between user-exits and Gap Analysis. User exits are standard gate ways provided by SAP to exit the standard code and we can write our own code with the help of ABAP workbench, its not new functionality which we are trying to build in sap but its slight enhancement within the same code.
    Gap analysis is start point of Realization and once business Blueprint is finished we have to find the realization of sap system for client requirment and there will be certain gaps when compared to system fit. Those gaps can be closed either by re-engineering of business process to fit with SAP or we have to use USER exits in case of small deviations or complete enhancements with the help of ABAP to fit with the SAP system.
    The Gaps can differ from company to company. Most commonly, however, missing functionality is industry-specific.
    Examples:
    1. MGM Studios and Lycos sometime back worked with SAP to develop its new intellectual property management and media advertising management functionality, respectively.
    2. A leading Oral care product company wanted the promotion of free-goods where they wanted 'Buy one get 2 different products free'.
    for more info check these links
    Re: A bit confused with your Gap Analysis example
    http://www.9000resource.com/what_is_gap_analysis/what_is_an_iso_9001_gap_analys_1.php?gclid=CMKw-6fh0YoCFRsRQQodczGGew
    http://www.geocities.com/rmtiwari/main.html?http://www.geocities.com/rmtiwari/Resources/Management/ASAP_Links.html
    Re: gap analysis

  • GAP ANALYSIS URGENT INTERVIEW QUESTIONS PLEASE .

    Hi Everybody ,
    Tell me more about GAP analysis and business requirements ? why it is required ? why it is need and some really scenario .
    thanks - Sameer .

    Here is Some useful info given earlier on SDN Forum on GAP Analysis:
    Simply Gap Is Nothing But,
    Client Requirement Doesn’t Meet With The SAP Application,
    The Distance Between Actual And Existing/Supporting,
    E.g.: On Purchase Of Material-X, The Other Material Will Get 50% Discount, Which Sap Doesn’t Support,
    Commission Paid To The Agent Also , Not Supported In SAP,
    To Fill This Gap, We Use The Enhancements,
    These Enhancements Divided Into Exits,
    Like
    User exits,
    Field Exits
    Screen Exits &
    Menu Exits.
    These Enhancements Used To Update The Standard Program In Its Respective Business Transactions, Used As A Gateway To Meet The Client Requirements.
    Refer below
    In n simple terms: Gap means small cracks. In SAP world or in Information Technology world, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be."
    Gap Analysis is undertaken as a means of bridging that space. Actual Gap Analysis is time consuming and it plays vital role in Business BlueprintAS IS Process stage.
    A through Gap Analysis will identify the gaps between how the business operates and its needs against what the package can can't do. For each gap there will be one of three outcomes, which must be recorded and auctioned,
    1. GAP must be closed and customized software can be developed
    2. GAP must be closed but software cannot be written therefore a workaround is required
    3. GAP does not need to be closed.
    A point worth mentioning here is that at time people confuse between user-exits and Gap Analysis. User exits are standard gate ways provided by SAP to exit the standard code and we can write our own code with the help of ABAP workbench, its not new functionality which we are trying to build in sap but its slight enhancement within the same code.
    Gap analysis is start point of Realization and once business Blueprint is finished we have to find the realization of sap system for client requirement and there will be certain gaps when compared to system fit. Those gaps can be closed either by re-engineering of business process to fit with SAP or we have to use USER exits in case of small deviations or complete enhancements with the help of ABAP to fit with the SAP system.
    The Gaps can differ from company to company. Most commonly, however, missing functionality is industry-specific.
    Examples:
    1. MGM Studios and Lycos sometime back worked with SAP to develop its new intellectual property management and media advertising management functionality, respectively.
    2. A leading Oral care product company wanted the promotion of free-goods where they wanted 'Buy one get 2 different products free'.
    gap analysis
    Gap analysis?
    Gap Analysis
    Regards
    Bala

  • Sample tamplates on Gap analysis and Resolution

    Hi Gurus,
    Can any one send me sample tamplates on Gap analysis and Resolution. My Email ID [email protected]
    Thanks & Regards
    Sasikanth.Ch

    <b>mail sent reward if helps</b>
    <b>GAP Analysis</b>
    A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and actioned, GAP must be closed and customised software can be developed close the gap, GAP must be closed but software cannot be written therefore a workaround is required, GAP does not need to be closed.
    In simple terms: Gap means small cracks. In SAP world. In information technology, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.
    Actual gap analysis is time consuming and it plays vital role in blue print stage.
    Cut Over Plans
    Detailed plans need to be developed for cutting over from the old system(s) to the new. Parallel runs of what will happen over the conversion period using test data, convert and watch for a period after wards to ensure nothing unexpected happens.
    Train Users
    Well trained users will support and defend the system on site. Unsupportive users will continually undermine the system and eventually it will be replaced. Therefore the more effort you put into helping the users master the system early the better. Fit gap means, before implementing the SAP all the business data is in the form of documents, we cannot keep this data as is in the SAP. There should be a gap. So by filling this gap, we make configuration with the help of these documents. This is called as fit gap analysis.
    GAP Analysis
    A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and actioned, GAP must be closed and customised software can be developed close the gap, GAP must be closed but software cannot be written therefore a workaround is required, GAP does not need to be closed.
    In simple terms: Gap means small cracks. In SAP world. In information technology, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.
    Actual gap analysis is time consuming and it plays vital role in blue print stage
    The Gaps can differ from company to company. Most commonly, however, missing functionality is industry-specific.
    Examples:
    1. MGM Studios and Lycos sometime back worked with SAP to develop its new intellectual property management and media advertising management functionality, respectively.
    2. A leading Oral care product company wanted the promotion of free-goods where they wanted 'Buy one get 2 different products free'.
    2 gaps are,In customer master data the client requirement needs legacy customer number which can be solved with User exit.,
    In sales order we need customer Phone number,We can use userexit
    These 2 are gaps which we cant find in Standard SAP
    1. if client want new field in customer master like nearest fire station ..
    2. order will be uploaded directly with out va01. through BDC... bcoz lot of orders if they get daily, they can opt these...
    Movement type 1 uses when a material have two movement types.. like example 101 and 261.. one is incomeing raw material and and going for production...
    Message was edited by:
            SHESAGIRI.G

  • Unable to run code analysis with WDK 9926

    Hi,
    I am trying to run code analysis with WDK 9926 and seeing below issue? can anybody help me to resolve this ?
    Error:
    ====
    C:\sw\dev\T4\windows\Src\kernel\vbd>msbuild.exe cht4vbd.vcxproj /p:Configuration="Windows 8.1 Debug" /P:Platform=x64 /P:RunCodeAnalysisOnce=True
    Microsoft (R) Build Engine version 12.0.21005.1
    [Microsoft .NET Framework, version 4.0.30319.33440]
    Copyright (C) Microsoft Corporation. All rights reserved.
    Build started 4/7/2015 12:08:30 AM.
    Project "C:\sw\dev\T4\windows\Src\kernel\vbd\cht4vbd.vcxproj" on node 1 (defaul
    t targets).
    DriverBuildNotifications:
      Building 'cht4vbd' with toolset 'WindowsKernelModeDriver10.0' and the 'Deskto
      p' target platform.
      Using KMDF 1.11.
    PrepareForBuild:
      Creating directory "x64\Windows8.1Debug\".
      Creating directory "C:\sw\dev\T4\windows\Src\kernel\vbd\x64\Windows8.1Debug\c
      hk\x64\".
      Creating directory "x64\Windows8.1Debug\cht4vbd.tlog\".
    InitializeBuildStatus:
      Creating "x64\Windows8.1Debug\cht4vbd.tlog\unsuccessfulbuild" because "Always
      Create" was specified.
    StampInf:
      c:\Program Files (x86)\Windows Kits\10\bin\x86\stampinf.exe -d "*" -a "amd64"
       -k "1.11" -f x64\Windows8.1Debug\chvbdx64.inf
      Copying "C:\sw\dev\T4\windows\Src\kernel\vbd\chvbdx64.inf" to "x64\Windows8.1
      Debug\chvbdx64.inf" for stamping
      Using version information from c:\Program Files (x86)\Windows Kits\10\Include
      \shared\\ntverp.h
      Could not open version header file c:\Program Files (x86)\Windows Kits\10\Inc
      lude\shared\\bldnump.h. (0x00000002)
      Could not determine version information.  Please specify using -v option.
      Updates common INF file directives
            USAGE:
            stampinf -f filename [-s section] [-d <xx/yy/zzzz> | *]
                     -a architecture -n [-c catalogfile]
                                 [-v <w.x.y.z> | *]
                                 [-k nnnnn] [-u nnnnn]
                                 [-i path]
            -f  specifies the INF file to process
            -s  specifies the INF section to place the DriverVer= directive.  By
                default this directive is placed in the [Version] section.
            -d  specifies the date written in the DriverVer= directive.  Note that
                a '*' given for a date value means for stampinf to write the
                current date. If the date is not specified, the date is taken
                from the STAMPINF_DATE environment variable.
            -v  specifies the version written in the DriverVer= directive. Note
                that a '*' given for a version value means for stampinf to write
                the current time (h.m.s.ms).  This is useful during development
                in order to get increasing version numbers. If the version is not
                specified, its value is taken from the STAMPINF_VERSION
                environment variable.
            -a  specifies the architecture string to replace the $ARCH$ keyword.
                The $ARCH$ keyword is used to tailor a TargetOSVersion decoration
                in a [Manufacturer] section, as well as its respective section
                name, to a specific platform. If no value is specified, stampinf
                takes its value from the _BuildArch environment variable.
            -c  specifies the value to be written in the CatalogFile= directive
                in the [Version] section. By default, this directive is not
                written.
            -k  specifies the version of KMDF that this driver depends on.  This
                is used to tailor the KmdfLibraryVersion & KMDF co-installer name
                in the INF. This will replace the $KMDFVERSION$ and
                $KMDFCOINSTALLERVERSION$ keywords in the INF.  The string is of
                the format:
                    <major_version>.<minor_version>
                As an example, supplying 1.5 as the version string will result in
                values of 1.5 and 01005 for the two keywords (respectively).
            -u  specifies the version of UMDF that this driver depends on.  This
                is used to tailor the UmdfLibraryVersion & UMDF co-installer name
                in the INF. This will replace the $UMDFVERSION$ and
                $UMDFCOINSTALLERVERSION$ keywords in the INF.  The string is of
                the format:
                    <major_version>.<minor_version>.<service_version>
                (where service_version is generally zero)
                As an example, supplying 1.5.0 as the version string will result
                in values of 1.5.0 and 01005 for the two keywords (respectively).
            -i  specifies the location of ntverp.h file.
                path represent the fully qualified
                location of the directory containing ntverp.h.
            -n  noisy mode shows verbose stampinf output
              -x  removes the coinstaller tag from the file and replaces the line w
      ith a ";"
            NOTES:
            The environment variable PRIVATE_DRIVER_PACKAGE can be set to
            enable stampinf's 'developer mode' behavior. When this is
            set, the date and version used for DriverVer is set to the
            current date and time, regardless of the command line
            settings. Also, 'CatalogFile=delta.cat' is written to the
            version section, unless a catalog was already specified
            with '-c'.
    c:\Program Files (x86)\Windows Kits\10\build\WindowsDriver.common.targets(355,5
    ): error MSB6006: "stampinf.exe" exited with code 1. [C:\sw\dev\T4\windows\Src\
    kernel\vbd\cht4vbd.vcxproj]
    Done Building Project "C:\sw\dev\T4\windows\Src\kernel\vbd\cht4vbd.vcxproj" (de
    fault targets) -- FAILED.
    Build FAILED.
    "C:\sw\dev\T4\windows\Src\kernel\vbd\cht4vbd.vcxproj" (default target) (1) ->
    (StampInf target) ->
      c:\Program Files (x86)\Windows Kits\10\build\WindowsDriver.common.targets(355
    ,5): error MSB6006: "stampinf.exe" exited with code 1. [C:\sw\dev\T4\windows\Sr
    c\kernel\vbd\cht4vbd.vcxproj]
        0 Warning(s)
        1 Error(s)
    Time Elapsed 00:00:04.07
    Thanks, Krishna

    Hi,
    I am trying to run code analysis with WDK 9926 and seeing below issue? can anybody help me to resolve this ?
    Error:
    ====
    C:\sw\dev\T4\windows\Src\kernel\vbd>msbuild.exe cht4vbd.vcxproj /p:Configuration="Windows 8.1 Debug" /P:Platform=x64 /P:RunCodeAnalysisOnce=True
    Microsoft (R) Build Engine version 12.0.21005.1
    [Microsoft .NET Framework, version 4.0.30319.33440]
    Copyright (C) Microsoft Corporation. All rights reserved.
    Build started 4/7/2015 12:08:30 AM.
    Project "C:\sw\dev\T4\windows\Src\kernel\vbd\cht4vbd.vcxproj" on node 1 (defaul
    t targets).
    DriverBuildNotifications:
      Building 'cht4vbd' with toolset 'WindowsKernelModeDriver10.0' and the 'Deskto
      p' target platform.
      Using KMDF 1.11.
    PrepareForBuild:
      Creating directory "x64\Windows8.1Debug\".
      Creating directory "C:\sw\dev\T4\windows\Src\kernel\vbd\x64\Windows8.1Debug\c
      hk\x64\".
      Creating directory "x64\Windows8.1Debug\cht4vbd.tlog\".
    InitializeBuildStatus:
      Creating "x64\Windows8.1Debug\cht4vbd.tlog\unsuccessfulbuild" because "Always
      Create" was specified.
    StampInf:
      c:\Program Files (x86)\Windows Kits\10\bin\x86\stampinf.exe -d "*" -a "amd64"
       -k "1.11" -f x64\Windows8.1Debug\chvbdx64.inf
      Copying "C:\sw\dev\T4\windows\Src\kernel\vbd\chvbdx64.inf" to "x64\Windows8.1
      Debug\chvbdx64.inf" for stamping
      Using version information from c:\Program Files (x86)\Windows Kits\10\Include
      \shared\\ntverp.h
      Could not open version header file c:\Program Files (x86)\Windows Kits\10\Inc
      lude\shared\\bldnump.h. (0x00000002)
      Could not determine version information.  Please specify using -v option.
      Updates common INF file directives
            USAGE:
            stampinf -f filename [-s section] [-d <xx/yy/zzzz> | *]
                     -a architecture -n [-c catalogfile]
                                 [-v <w.x.y.z> | *]
                                 [-k nnnnn] [-u nnnnn]
                                 [-i path]
            -f  specifies the INF file to process
            -s  specifies the INF section to place the DriverVer= directive.  By
                default this directive is placed in the [Version] section.
            -d  specifies the date written in the DriverVer= directive.  Note that
                a '*' given for a date value means for stampinf to write the
                current date. If the date is not specified, the date is taken
                from the STAMPINF_DATE environment variable.
            -v  specifies the version written in the DriverVer= directive. Note
                that a '*' given for a version value means for stampinf to write
                the current time (h.m.s.ms).  This is useful during development
                in order to get increasing version numbers. If the version is not
                specified, its value is taken from the STAMPINF_VERSION
                environment variable.
            -a  specifies the architecture string to replace the $ARCH$ keyword.
                The $ARCH$ keyword is used to tailor a TargetOSVersion decoration
                in a [Manufacturer] section, as well as its respective section
                name, to a specific platform. If no value is specified, stampinf
                takes its value from the _BuildArch environment variable.
            -c  specifies the value to be written in the CatalogFile= directive
                in the [Version] section. By default, this directive is not
                written.
            -k  specifies the version of KMDF that this driver depends on.  This
                is used to tailor the KmdfLibraryVersion & KMDF co-installer name
                in the INF. This will replace the $KMDFVERSION$ and
                $KMDFCOINSTALLERVERSION$ keywords in the INF.  The string is of
                the format:
                    <major_version>.<minor_version>
                As an example, supplying 1.5 as the version string will result in
                values of 1.5 and 01005 for the two keywords (respectively).
            -u  specifies the version of UMDF that this driver depends on.  This
                is used to tailor the UmdfLibraryVersion & UMDF co-installer name
                in the INF. This will replace the $UMDFVERSION$ and
                $UMDFCOINSTALLERVERSION$ keywords in the INF.  The string is of
                the format:
                    <major_version>.<minor_version>.<service_version>
                (where service_version is generally zero)
                As an example, supplying 1.5.0 as the version string will result
                in values of 1.5.0 and 01005 for the two keywords (respectively).
            -i  specifies the location of ntverp.h file.
                path represent the fully qualified
                location of the directory containing ntverp.h.
            -n  noisy mode shows verbose stampinf output
              -x  removes the coinstaller tag from the file and replaces the line w
      ith a ";"
            NOTES:
            The environment variable PRIVATE_DRIVER_PACKAGE can be set to
            enable stampinf's 'developer mode' behavior. When this is
            set, the date and version used for DriverVer is set to the
            current date and time, regardless of the command line
            settings. Also, 'CatalogFile=delta.cat' is written to the
            version section, unless a catalog was already specified
            with '-c'.
    c:\Program Files (x86)\Windows Kits\10\build\WindowsDriver.common.targets(355,5
    ): error MSB6006: "stampinf.exe" exited with code 1. [C:\sw\dev\T4\windows\Src\
    kernel\vbd\cht4vbd.vcxproj]
    Done Building Project "C:\sw\dev\T4\windows\Src\kernel\vbd\cht4vbd.vcxproj" (de
    fault targets) -- FAILED.
    Build FAILED.
    "C:\sw\dev\T4\windows\Src\kernel\vbd\cht4vbd.vcxproj" (default target) (1) ->
    (StampInf target) ->
      c:\Program Files (x86)\Windows Kits\10\build\WindowsDriver.common.targets(355
    ,5): error MSB6006: "stampinf.exe" exited with code 1. [C:\sw\dev\T4\windows\Sr
    c\kernel\vbd\cht4vbd.vcxproj]
        0 Warning(s)
        1 Error(s)
    Time Elapsed 00:00:04.07
    Thanks, Krishna

  • AUC- Asset Under Construction - Gap Analysis

    Hi Guru's,
    I have a requirement to know the Gap Analysis on Asset Under Construction. 
    We are under Analysis Phase where i have to find out the Gaps related to business.
    I received a Reporting FD and asked to find out the data source.
    Please provide the Gap Analysis steps to over come on this specific requirement.  
    Based on my analysis i found multiple tables to derive the AUC - Asset Under Construction solution.
    Tables that involved to get the Asset Under Construction:ANLA, ANLZ, PRPS, ANEP, BPDY, T093B
    My Questions:
    Is there any SAP Standard Data Source for AUC- Asset Under Construction.
    Now in my high level requirement we are pulling the information from multiple tables.
    Please provide me suggestions how can i go ahead with the above requirement.
    Regards,
    Ganni

    Depends on how the FICO guys have configured AuC
    If they have chosen a separate asset class for this (as what tends to happen) - then the std asset data model will cater for this
    Just run the std content reports or build your own for the asset class of AuC

Maybe you are looking for