T CODE related with IPC

Hi ,
  Please provide me the t codes associated with IPC.Also let me know whether CR 235 is enough to understand IPC or i need to refer some other CR.
Please provide me link of some useful documents related with IPC.
regards
PG

Hi,
Go through the below link:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/107adc1a-0501-0010-de8e-973e0fb4049b
Regards,
PePe

Similar Messages

  • T CODE related with CRM billing

    Hi folks,
       Please provide the t codes related with CRM billing.
    regards
    PG

    Hi,
    Here r some of the Tcodes:
    /BEA/CRMB01          Edit Billing Due List
    /BEA/CRMB02          Release Billing Due List for Billing
    /BEA/CRMB04          Analyze Incomplete Billing Due List
    /BEA/CRMB06          Schedule Background Jobs
    /BEA/CRMB07          Reject Incomplete Billing Due List
    /BEA/CRMB11          Maintain Billing Documents
    /BEA/CRMB12          Transfer Billing Docs to Accounting
    /BEA/CRMB13          Create Retroactive Billing
    /BEA/CRMB15          Display Collective Run Log
    Regards,
    PePe

  • Some codes related with connection and file upload

    This is for the connection to the smart card code. If there is sth wrong please inform this. And I do nt know why there is no pin verification while connecting to card....
         // show the list of available terminals
    TerminalFactory factory = TerminalFactory.getDefault();
    List<CardTerminal> terminals = factory.terminals().list();
    System.out.println("Terminals: " + terminals);
    // get the first terminal
    CardTerminal terminal = terminals.get(0);
    // establish a connection with the card
    Card card = terminal.connect("T=0");
    System.out.println("card: " + card);
    CardChannel channel = card.getBasicChannel();
    ResponseAPDU r = channel.transmit(new CommandAPDU(c1));
    System.out.println("response: " + toString(r.getBytes()));
         // Here do your processes     
    // disconnect
    card.disconnect(false);
    This is code of storing a file whose extension is p12 to the smart card. Is this for storing a existing certificate(C:file.p12 as an example) to smart card?
    CertificateFactory cf = CertificateFactory.getInstance("X.509");
    X509Certificate cert = (X509Certificate)
    cf.generateCertificate(new java.io.FileInputStream(certFile));
    dest.setKeyEntry(alias, key, kstorePassword, chain);
    dest.setCertificateEntry("cacert", cert);
    dest.store(new java.io.FileOutputStream(keystoreFile), storePassword);
    Thanks for your responses ....
    Best Regards,
    ilkay POLAT

    Authenticating with a PIN will depend on the applet on the card you are trying to authenticate to. If the applet is ISO7816, you should have a look at the ISO7816-4 specifications for the APDU command for VERIFY (used to verify user password or PIN).
    I guess it comes down to the applet. You may have to check the standard is was developed for (ISO7816, EMV, etc) for the APDU required to verify a users PIN.
    If you are having problems connecting (or are unsure what protocol to use) you can use the following line to connect. This will attempt to connect with any available protocol.
    Card card = terminal.connect("*");I hope this helps.
    Shane

  • Please provide me all the t codes related to direct invoices , SRM...

    Hi All,
    Please provide me all the t codes related to direct invoices , SRM and Manual Purchase orders
    Thanx in advance,
    Ravi.

    Dear Ravi,
    use Transaction Se16 and write the table name as TSTC what you will get is a list of all T-codes with there description.
    Another method is using the Transaction-SDMO here you enter the text and you will get all transactions related to the text you enter.
    Using these two transactions I hope you would be able to find out all the t-codes.
    Cheers,
    Prafulla
    Message was edited by:
            prafulla singh

  • Need all transaction codes related to SD and MM

    hi
    i am in need of need all transaction codes related to SD and MM.
    can anyone help me to get it.
    thanks in advance.

    Hi,
    The most frequently used transaction codes are as follows:
    1. VS00 - Master data
    2. VC00 - Sales Support
    3. VA00 - Sales
    4. VL00 - Shipping
    5. VT00 - Transportation
    6. VF00 - Billing
    Others as follows:
    At Configuration:
    1. VOV8 - Define Sales documents type (header)
    2. OVAZ - Assigning Sales area to sales documents type
    3. OVAU - Order reasons
    4. VOV4 - Assign Item categoreies(Item cat determination)
    5. VOV6 - Scedule line categories
    6. OVAL - To assign blocks to relevant sales documents type
    7. OVLK - Define delivery types
    8. V/06 - Pricing
    9. V/08 - Maintain pricing procedure
    10.OVKP - Pricing proc determination
    11.V/07 - Access sequence
    Enduser:
    1. Customer Master Creation-VD01 and XD01 (for full inclu company code)
        VD02 - Change Customer
        VD03 - Display Customer
        VD04 - Customer Account Changes
        VD06 - Flag for Deletion Customer
        XD01 - Create Customer
        XD02 - Modify Customer
        XD03 - Display Customer
    2. Create Other material -
    MM00
    3. VB11- To create material determination condition record
    4. CO09- Material availability Overview
    5. VL01 - Create outbound delivery with ref sales order
    6. VL04 - Collective processing of delivery
    7. VA11 - Create Inquiry
        VA12 - Change Inquiry
        VA13 - Display Inquiry
    Sales & Distribution
    Sales order / Quote / Sched Agreement / Contract
    · VA01 - Create Order
    · VA02 - Change Order
    · VA03 - Display Order
    · VA02 - Sales order change
    · VA05 - List of sales orders
    · VA32 - Scheduling agreement change
    · VA42 - Contract change
    · VA21 - Create Quotation
    · VA22 - Change Quotation
    · VA23 - Display Quotation
    Billing
    · VF02 - Change billing document
    · VF11 - Cancel Billing document
    · VF04 - Billing due list
    · FBL5N - Display Customer invoices by line
    · FBL1N - Display Vendor invoices by line
    Delivery
    · VL02N - Change delivery document
    · VL04 - Delivery due list
    · VKM5 - List of deliveries
    · VL06G - List of outbound deliveries for goods issue
    · VL06P - List of outbound deliveries for picking
    · VL09 - Cancel goods issue
    · VT02N - Change shipment
    · VT70 - Output for shipments
    General
    · VKM3, VKM4 - List of sales documents
    · VKM1 - List of blocked SD documents
    · VD52  - Material Determination
    MM Transaction Code
    All transaction are stored in table TSTC. 
    Transaction for MM module start with M. 
    IH09 - Display Material
    MM01 - Create Material 
    MM02 - Change Material 
    MM03 - Display Material
    MM50 - List Extendable Materials
    MMBE - Stock Overview
    MMI1 - Create Operating Supplies
    MMN1 - Create Non-Stock Material 
    MMS1 - Create Service
    MMU1 - Create Non-Valuated Material
    ME51N - Create Purchase Requisition
    ME52N - Change Purchase Requisition
    ME53N - Display Purchase Requisition
    ME5A - Purchase Requisitions: List Display
    ME5J - Purchase Requisitions for Project
    ME5K - Requisitions by Account Assignment
    MELB - Purch. Transactions by Tracking No.
    ME56 - Assign Source to Purch. Requisition
    ME57 - Assign and Process Requisitions
    ME58 - Ordering: Assigned Requisitions
    ME59 - Automatic Generation of POs
    ME54 - Release Purchase Requisition
    ME55 - Collective Release of Purchase Reqs.
    ME5F - Release Reminder: Purch. Requisition
    MB21 - Create Reservation
    MB22 - Change Reservation
    MB23 - Display Reservation
    MB24 - Reservations by Material
    MB25 - Reservations by Account Assignment
    MB1C - Other Goods Receipts
    MB90 - Output Processing for Mat. Documents
    MB21 - Create Reservation
    MB22 - Change Reservation
    MB23 - Display Reservation
    MB24 - Reservations by Material
    MB25 - Reservations by Account Assignment
    MBRL - Return Delivery per Mat. Document
    MB1C - Other Goods Receipts
    MB90 - Output Processing for Mat. Documents
    MB1B - Transfer Posting
    MIBC - ABC Analysis for Cycle Counting
    MI01 - Create Physical Inventory Document
    MI02 - Change Physical Inventory Document
    MI03 - Display Physical Inventory Document
    MI31 - Batch Input: Create Phys. Inv. Doc.
    MI32 - Batch Input: Block Material
    MI33 - Batch Input: Freeze Book Inv.Balance
    MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
    MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
    MIQ1 - Batch Input: PhInvDoc. Project Stock
    MI01 - Create Physical Inventory Document
    MI02 - Change Physical Inventory Document
    MI03 - Display Physical Inventory Document
    MI31 - Batch Input: Create Phys. Inv. Doc.
    MI32 - Batch Input: Block Material
    MI33 - Batch Input: Freeze Book Inv.Balance
    MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
    MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
    MIQ1 - Batch Input: PhInvDoc. Project Stock
    MI01 - Create Physical Inventory Document
    MI02 - Change Physical Inventory Document
    MI03 - Display Physical Inventory Document
    MI31 - Batch Input: Create Phys. Inv. Doc.
    MI32 - Batch Input: Block Material
    MI33 - Batch Input: Freeze Book Inv.Balance
    MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
    MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
    MIQ1 - Batch Input: PhInvDoc. Project Stock
    MI21 - Print physical inventory document
    MI04 - Enter Inventory Count with Document
    MI05 - Change Inventory Count
    MI06 - Display Inventory Count
    MI09 - Enter Inventory Count w/o Document
    MI34 - Batch Input: Enter Count
    MI35 - Batch Input: Post Zero Stock Balance
    MI38 - Batch Input: Count and Differences
    MI39 - Batch Input: Document and Count
    MI40 - Batch Input: Doc., Count and Diff.
    MI08 - Create List of Differences with Doc.
    MI10 - Create List of Differences w/o Doc.
    MI20 - Print List of Differences
    MI11 - Physical Inventory Document Recount
    MI07 - Process List of Differences
    MI37 - Batch Input: Post Differences
    CT01 - Create Characteristic
    CT02 - Change Characteristic
    CT03 - Display Characteristic
    CL01 - Create Class
    CL02 - Classes
    CL03 - Display Class
    CL04 - Delete Class
    CL2B - Class Types
    <REMOVED BY MODERATOR>
    Edited by: Alvaro Tejada Galindo on Apr 7, 2008 12:53 PM

  • Relation between IPC & Portlet Asynchronous rendering

    Hi,
    Can someone explain the relation between IPC & Portlet Asynchronous rendering.
    In the below URL, its written " IPC is not supported when asynchronous content rendering is enabled "
    But, when I go through the article below, its given that with IPC, portlet contents can be rendered asynchronously using custom event handling.
    http://blogs.oracle.com/gmurnock/entry/portalaware_xhr_and_ipc
    I'm bit confused here & need support in understanding with the help of suitable examples.
    Thanks,
    Uttam

    Hi,
    Thats the reason its not clear to me what does it mean by the statement " IPC is not supported when asynchronous content rendering is enabled "
    mentioned in the URL http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/portlets/performance.html#wp1028016
    But, to my understanding AJAX & IPC can be achieved between portlets only by making entire desktop property as Asynchronous on which these portlets reside, but not by making portlet property as asynchronous.
    Also, if I need to make only the contents of portlets refreshed (through AJAX) instead of entire portal page refresh, I've to make all the desktops property as asynchronous on which these portlets functionality appear.
    Please correct me if my understanding is wrong anywhere?
    Thanks,
    Uttam

  • Identifying relations to simulate M:N relation with attributes

    Hi,
    I'm always using 3.1.4
    In this version, M:N relations don't support attributes. In 3.3 it is supported. But sometimes, it's necessary in a logical model to have an entity which represent the relation. So I can add another relation between this "associative entity" and another entity. Like in Oracle Designer, if i want to create a M:N relation with attributes, I have to create an entity with two identifying relations
    So I created :
    Student, Registration and Stage entities
    Identifying relation between Student and Registration
    Identifying relation between Stage and Registration
    Registration with several attributes. So Registration is an "associative entity".
    But when I do this in DM :
    In Registration entity, there are two unique identifiers
    the first one (which is PUID) is correct, it references the two relations
    The second is incorrect. It should not to exist.
    is it right ?

    3° create entity Registration, with one column : dateRegistration (NOT primary UID)I assume there is a UID created (not set as PK) and it's over dateRegistration attribute
    2° create entity Stage, with 2 columns : Numero (primary UID), code, descriptionyou write 2 columns, but 3 are listed, the number is not important just to confirm that Primary UID is created on Numero attribute.
    So entity Registration has one UID before identifying relationships are created. You need to check setting in "Preferences>Data Modeler>Model>Logical>Use and set first unique key as primary key"
    One Primary UID only exists in Registration in case it's checked, and there is one Primary UID (over both relationships) and one UID over dateRegistration attribute in case it's not checked.
    Philip

  • Need Some Basics to go with IPC

    Hi,
    I am truing to get some knowledge on IPC, and I am not at all familiar with User Exits. I am going through this document. PricingUserexitManualV104.pdf, and it is really confusing, for a person who is not aware of user exits.
    Also lack of CRM knowledge is causing me trouble...
    So I am here for help...
    Can some one explain me these things...
    1. step/counter level
    2. condition access step level
    3. base value of a condition
    4. scale base value
    5. condition value
    6. pricing condition that can be fixed
    7. document copy
    And while going through types of user exits, I have the following doubts...
    What is the difference between Type A and Type C user exits? From the document, both are multiple active implementations, but Type A requires formula numbers for execution of userexit, and type B, we assign a dummy formula number....
    The doubt is what is the difference if both requires formula numbers, and if each userexit is considered as one formula, how do we assign formula number to userexit?
    It will be really helpful for me to go ahead with IPC... some one please help me with these doubts...
    Thanks and Regards,
    Chinnu

    Chinnu,
    pricing in CRM/IPC is very similar to pricing in ERP SD. You need to know the underlying concepts to be able to properly set up (or transfer) user exits.
    I suggesting starting with
    http://help.sap.com/saphelp_erp60/helpdata/en/dd/56168b545a11d1a7020000e829fd11/frameset.htm
    The IMG documentation might also be helpful.
    The number of user exits of scope A is not arbitrary, but relates to e.g. (type VAL) a formula number for a condition value in the pricing procedure. So the number is like an ID. For scope C, the numbers only define a sequence.
    Michael

  • Clarification related with Flexconnect solution

    Dear Folks, 
    I have a doubt related with the Cisco Flexconnect scenario . I have a scenario where i need to centralize my wireless to 50 other branches , as the main controllers will be located in DC .
    Well , these are the client requirements
    1. Every site will have their own data , voice and management vlan (for AP) .
    2. DHCP will be local
    Now my question is as follows
    1. In the main controller, i need to add for every site vlan (ie for 50 sites in total times 3 vlans ) in the controller and in the switch for SVI . ?
    2. Is it recommended to have centralized AP management for all 50 sites together , so that i can have one native vlan in the remote site, lets say vlan 100 ( for AP management) . Or is it recommended to have different IP for AP management , in this case, what would be the native vlan, will it be the AP management ?
    3. What happens when WAN link is down ? how long can the access point work without WAN connectivity ?
    Highly appreciate your kind help and support.
    Regards,
    SID                             

    Hi Siddarth,
    Not exactly correct.
    In the given scenario, you only required vlan 60,61,62 available to DC WLC. Vlan 99,101,102 are not required in DC-WLC (it is impossible to have those over there if you branch connected via WAN)
    In branch switch you only require vlan 99,101,102 & configure AP connected switchport as trunk port while keeping native vlan 99.
    Vlan mapping is specific to AP & once you convert an AP to FlexConnect & WLAN configured for FlexConnect local switching, you should be able to do the mapping (wlan to vlan for that AP)
    You can refer this post to understand the FlexConnect concept (H-REAP was the previous name for this feature & my sample config is based on WLC 7.0.x code)
    http://mrncciew.com/2013/03/12/h-reap-with-radius/
    Refer below CiscoLive presentation for latest code features & how to configure those.
    BRKEWN-2026 - Architecturing Network for Branch Offices with Cisco FlexConnect
    If you like to watch the recorded video session of the above you can register Ciscolive365.com for free. Here is the link to session details.
    https://www.ciscolive.com/online/connect/sessionDetail.ww?SESSION_ID=76360&backBtn=true
    If you still need any clarification pls let us know
    HTH
    Rasika
    *** Pls rate all useful responses ****

  • Relation with Master Recipe

    How Process order is related with master recipe?

    Hi Debasish,
    Master Recipe is a task list used in the process orders like routing in the production orders.
    In master recipe, we define operations and phases required for manufacturing a finish or semifinish product.T code for creation of master recipe is C201.
    Regards,
    Rajarao.

  • Regarding Menus & func code relation

    hey guys,
    Do we have any FM or Program to relate GUI_STATUS menu and Function code.
    I found FM RS_CUA_GET_FUNCTIONS  for Func code list but i want to know how it relate with Menus & func keys/application bars.
    one more FM also i found RS_CUA_INTERNAL_FETCH, but we could not map it properly with Menus and Function codes.
    I tried with relating output STA->ACTCODE->MENU->FUN. but seems its not correct. I checked SAPMF02D program having GUI STATUS 1020 no menu bar exist.but  FM says Menubar exists. I am confused here.
    Suggestion please.
    regards
    ambichan

    Hey guys,
    FM RS_CUA_INTERNAL_FETCH has this many Menu types.
    I can only see Dailog type 'D' menus for GUI status in SE80 tr-cd.
    How can i view the Menu type 'P'(POPUP menutype) and 'L' etc..
    CONSTANTS: CON_STDTYPE_DIAL       VALUE 'D',
               CON_STDTYPE_POPUP      VALUE 'P',
               CON_STDTYPE_LIST       VALUE 'L',
               CON_STDTYPE_LBOX       VALUE 'B',
               CON_STDTYPE_CONTEXT    VALUE 'C',
               CON_STDTYPE_MENU       VALUE 'M',
               CON_STDTYPE_EXEMPT     VALUE 'X',
               CON_STDTYPE_EXEMPT_RES VALUE 'Y',
               CON_STDTYPE_OBLIGATORY VALUE 'O',
               CON_STDTYPE_DEFAULT    VALUE 'F',
               CON_STDTYPE_SYSTEM     VALUE 'S',
               CON_STDTYPE_SBAR       VALUE 'I',
               CON_STDPFNO_CTX TYPE CUA_PFNO VALUE '94',
               CON_STDFUNC_CTX TYPE GUI_CODE VALUE '%CTX'.
    suggest me
    Regards
    Ambichan

  • VBA Code error with Adobe Acrobat 10 Type Library

    Hi,
    I have some code I created in Word VBA to combine several separate PDFs into a single PDF.  The code works fine with the Adobe Acrobat 9.0 Type Library and Adobe Reader 9.0 installed.
    But, with the Adobe Acrobat 10 Type Library and Adobe Reader 10 installed, the code fails at the marked code below.  Any suggestions??
        Dim acrobatApp As Acrobat.acroApp
        Set acrobatApp = CreateObject("AcroExch.App")
        Dim mainPDF As Acrobat.AcroPDDoc
        Set mainPDF = CreateObject("AcroExch.PDDoc")  ****THIS IS WHERE THE CODE STOPS WITH A "TYPE MISMATCH" ERROR****
        Dim nextPage As Acrobat.AcroPDDoc
        Set nextPage = CreateObject("AcroExch.PDDoc")
        Dim numPages As Integer
        'Loop through all selected VLS, and add each one to the end of the main PDF
        For i = 0 To lstSelected.ListCount - 1
            mainPDF.Open CurDir & "\" & Replace(ThisDocument.Name, ".doc", "") & ".pdf"
            numPages = mainPDF.GetNumPages
            nextPage.Open lstSelected.List(i)
            If mainPDF.InsertPages(numPages - 1, nextPage, 0, nextPage.GetNumPages, True) = False Then
                MsgBox "Cannot insert pages"
            End If
            If mainPDF.Save(PDSaveFull, CurDir & "\" & Replace(ThisDocument.Name, ".doc", "") & ".pdf") = False Then
                MsgBox "Cannot save"
            End If
            'MsgBox lstSelected.List(i)
            nextPage.Close
        Next i

    What if you start with a really simple VBA example? Take a look at this:
    Private Sub CommandButton1_Click()
        Dim AcroApp As Acrobat.CAcroApp
        Dim theDocument As Acrobat.CAcroPDDoc
        Dim bm As Acrobat.AcroPDBookmark
        Dim thePath As String
        thePath = "c:\temp\test.pdf"
        Set AcroApp = CreateObject("AcroExch.App")
        Set theDocument = CreateObject("AcroExch.PDDoc")
        theDocument.Open (thePath)
        MsgBox "Number of pages: " & theDocument.GetNumPages
        theDocument.Close
        AcroApp.Exit
        Set AcroApp = Nothing
        Set theDocument = Nothing
        Set bm = Nothing
        MsgBox "Done"
    End Sub
    If this still does not work, I would reinstall Acrobat to make sure that
    the TLB is not corrupt.
    Karl Heinz Kremer
    PDF Acrobatics Without a Net
    [email protected]
    http://www.khkonsulting.com

  • 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

  • How do I code relative links as function parameters within Templates?

    I am a newcomer looking for best practices for a "How Do I?" properly code relative links as function parameters within an Adobe template (DWT) which accomodates page creation at 2 different level of folders. Dreamweaver doesn't appear to handle auto-correction of relative links as function parameters as far as I can see.  It's not clear to me what the best practice I should be following.  While this is not exactly a SPRY question, I am hoping that someone using the Spry.Data.XMLDataSet had already found the best practice to use.
    My Site
    -- Multiple pages at this level    and the parameter needs to be "_includes/UnitSideNavigation.xml"
    SubFolder
    -- Other pages at this level.       and the parameter needs to be "../_includes/UnitSideNavigation.xml"
    And this is the particular code snippet within a non edtable template area I would like to work for 2 levels of pages created from the template.
    <script type="text/javascript">
    var dsItems1 = new Spry.Data.XMLDataSet("_includes/UnitSideNavigation.xml", "/links/firstlevel");
    var dslinks = new Spry.Data.NestedXMLDataSet(dsItems1, "secondlevels/secondlevel");
    </script>
    My environment is Windows/Vista using latest CS4 dreamweaver.
    Any pointers appreciated. This is learn time for me. Hope I have made myself clear. Andy

    I use serverside includes instead of DWT for exactly that reason. Not only that, if you change anything within the template you must re-upload all of the files affected by the change; only the modified include file needs to be uploaded.

  • Will the new 10.6.8 update fix SATA3 issues related with 2011 MacBook Pros?

    Will the new 10.6.8 update fix SATA3 issues related with 2011 MacBook Pros?

    It is against TOU to speculate on these message board.  Suggest you post your question on the Mac Rumors site.
    As I already stated, there is no 10.6.8 update.  If there was, it would be listed in Software Update.

Maybe you are looking for