Create update package question

So we have a package:
Adobe_CS6-MasterCollection_en-US_20120912_install.pkg
A month later we want to create an update package that includes ONLY the updates released AFTER the above package was created.
Possible?
Don

Hi Don,
We can modify the package which will detects the previous updates and will show new updates available after that. But if you are  creating new update package then it will not have any knowledge of already created package, rather it will show all the latest available updates.
But point taken, we will analyse the feasibility of including this feature in AAMEE.
thanks,
Rahul | [email protected]

Similar Messages

  • Creating Software Update Packages - Best Practice?

    I am setting up our SCCM 2012 R2 environment to begin using it for Windows Updates, however I'm not sure 100% the best method of setting it up.
    Currently my plan is to break out the deployment packages by OS, but I read\told that I should avoid creating to many dynamic deployment packages, as every time it changes all the computers will re-scan that package.  So What I want to do is create
    various packages for OS and years, so I would have a package that contains all updates for Windows 7, older then January 31, 2013 (assuming the package doesn't have 1000+ updates), and are not superseded\Expired. Then I would create Packages for the 2014
    monthly updates each month, then at the end 2014, combine them all in 1 package, and restart the process for 2015.  Is this a sound plan or is there a better course of action?
    If this the best practice method, is there any way to automatically create these packages?  I tried the Automatic Deployment Rules, but I can not set a Year of release, only the a time frame of the release,(older then 9 Months), unless I am missing
    something.  The only way I can see doing this is going into All Software Updates, and filtering on my requirements, and then manually creating the package, but this would less desirable, as after each year I would like to remove the superseded and expired
    without having to recreate the package.
    Mark.

    First, please learn what the different objects are -- not trying to be rude, just stating that if you don't do this, you will have fundamental issues. Packages are effectively meaningless when it comes to deploying updates. Packages are simply a way of grouping
    the binary files so they can be distributed to DPs and in-turn made available to clients. The package an update is in is irrelevant. Also, you do not "deploy" update packages and packages are not scanned by clients. The terminology is very important because
    there are implications that go along with it).
    What you are actually talking about above are software update groups. These are separate and distinct objects from update packages. Software Update groups group updates (not the update binaries) into logical groups that can be in-turn deployed or used for
    compliance reporting.
    Thus, you have two different containers that you need to be concerned about, update packages and update groups. As mentioned, the update package an update is in is pretty meaningless as long as the update is in a package that is also available to the clients
    that need it. Thus, the best way (IMO) to organize packages is by calendar period. Yearly or semi-annually usually works well. This is done more less to avoid putting all the updates into a single package that could get corrupted or will be difficult to deploy
    to new DPs.
    As for update groups, IMO, the best way is to create a new group every month for each class of products. This typically equates to one for servers, one for workstations, and one for Office every month. Then at the end of every year (or some other timeframe),
    rolling these monthly updates into a larger update group. Keep in mind that a single update group can have no more than 1,000 updates in it though. (There is no explicit limit on packages at all except see my comments above about not wanting one huge package
    for all updates.)
    Initially populating packages (like 2009, 2010, 2011, etc) is a manual process as is populating the update groups. From then on, you can use an ADR (or really three: one for workstations, one for servers, and one for Office) that runs every month, scans
    for updates released in the past month, and creates a new update group.
    Depending upon your update process, you may have to go back and add additional deployments to each update group also, but that won't take too long. Also, always QC your update groups created by an ADR. You don't want IE11 slipping through if it will break
    your main LOB application.
    Jason | http://blog.configmgrftw.com

  • Update mode options while creating info package

    Hi all .
        while creating info package in update tab  we have different radio buttons as
       FULL UPDATE,DELTA UPDATE,INTIALIZE DELTA PROCESS. could you pls explain this optons.
    Thanks in advance.
    Cheers,
    sami.

    Hi Sami,
    We have two update modes 1)Full update 2)Init Load(to enable delta)
    Full Load --->Master data Load
    Init Load----->Transaction data Load.
    Full Update-To load Historical Data.
    Init-This is done to enable the Delta Upload.
    Delta will be done only if the Init has happened.
    For deltas they are Data source specific which are delta enabled.
    1. Full Load (Extracts whole data available in source)
    2. Initialization (without data transfer): Enables only delta and no data.
    3. Initialization with data: Extracts whole data from source and enables delta.
    4. Delta: Extracts only modified or new data.
    Above modes works for Master as well as Transaction also.
    For further information check this link:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/frameset.htm
    Cheers,
    Tanish.

  • Created a package with packager for updates and install failed

    Brand new iMac with CC2014 installed. Created a package of just updates. When running the update package, installation failed. Any ideas anyone?

    Moving the discussion to Enterprise Deployment for Creative Cloud, Creative Suite,
    Thanks,
    Atul Saini

  • Creating a NetInstall image OSX 10.6 with 10.6.2 combo update package

    Has anyone been successful creating a NetInstall image of OSX 10.6 with 10.6.2 combo update package included. Every time I attempt to do it, the image creation fails.

    I second that.
    You even have advanced group handling to determin which users should be allowed to perform which tasks.
    You can even image and restore Windows (both bootcamp on a mac AND pure PC:s)
    If you have a pure PC (god forbid) like an HP or Acer or something, they have to be able to netboot. Otherwise it works like a charm.
    Building a workflow in DeployStudio is pure "drag and drop". So it´s easy.

  • Client Update Packages (SCCM CUs)

    What is the proper way of deploying these?  I have the x64 package deployed to a dynamic collection which consists of x64 clients.  It's configured to install as soon as possible.  This is causing issues with new client installs since the
    SCEP install and client update seem to interfere with each other.  How can I ensure clients receive the client update in a timely manner but don't interfere with the SCEP  install?

    A common approach is to make collections with queries that target x86 and x64 OS architectures.
    Then deploy the x86 and x64 client update packages (that get created for you when applying the CU) to those collections.
    When you say new client installs do you mean during OSD? If this is the case then you should be patching your client at the point of installation during your OSD Task Sequence.
    If you mean that the Client Update package is attempting to install before the major client update - i.e. your on SCCM 2012 SP1 and you have upgraded to 2012 R2 CU1 - then you should be adjusting your queries so they only target clients with the R2 version.
    This way you will not have the Client Update package trying to run before the full client upgrade has occurred.
    As an example - this is the query I have used to upgrade my SCCM 2012 CU1 client to CU2:
    select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceID = SMS_R_System.ResourceId
    where SMS_R_System.Active = "1" and SMS_G_System_SYSTEM.SystemType = "X64-based PC" and SMS_R_System.ClientVersion < "5.00.7958.1303" and SMS_R_System.ClientVersion >= "5.00.7958.1000"
    There are plenty of blogs which talk about client updates using queries.
    Cheers
    Damon
    I have a dynamic collection built already.  I guess my question revolves around how  you should configure the available/deadline part of the deployment.  My issue is that the SCEP install after a client is upgraded from 2007 -> 2012 is kicking
    off at the same time as the client upgrade.  The FEP client gets uninstalled, the client upgrade gets stuck in "Waiting for install" and nothing continues until I restart the SMS service.

  • Create, Update & Save Functions

    Hi All,
    This is my code for the requirement to print sales order in ALV Grid Format using OOPS concept.
    Please tell me how i should add select button to the ALV Grid in the first column.
    Also when i click on CREATE button a new blank line should be added to the alv grid.
    when i click on UPDATE button the selected row should become editable & when i click on save then my Ztable should be update with the new values and all the changes made.
    The Ztable has fields as of the IT_FIANL table.
    I have gone through many links regarding this topic but cant implement it in my code.
    REPORT  z12darp_shad_so_alv_oops
            MESSAGE-ID z12darp1.
    *Class definition for handling double click
    CLASS event_class DEFINITION DEFERRED.
    *Class definition for ALV toolbar
    CLASS lcl_alv_toolbar   DEFINITION DEFERRED.
    *AUTHOR: Darpana. Ahire
    *DATE: 28/11/2008
    *DESCRIPTION: To printsales order as Interactive ALV using OOPS concept.
    *&               D A T A   D E C L R A T I O N
    type-pools: icon.
    INCLUDE z12darp_alv_oops.
    data: ok_code_2008 like sy-ucomm.
    *&  Include           Z12DARP_ALV_OOPS
    *Author: Darpana. Ahire
    *Date: 28/11/2008
    *Description: ALV Grid Using OOPS concept.
    tables: z12Darp_final.
    types: begin of ty_vbak,
             vbeln   type   vbeln_va,
             erdat   type   erdat,
             vkorg   type   vkorg,
             spart   type   spart,
          end of ty_vbak.
    types: begin of ty_vbap,
             vbeln   type   vbeln_va,
             posnr   type   posnr_va,
             matnr   type   matnr,
             netpr   type   netpr,
             netwr   type   netwr_ap,
           end of ty_vbap.
    types: begin of ty_final,
             vbeln   type   vbeln_va,
             erdat   type   erdat,
             vkorg   type   vkorg,
             spart   type   spart,
             posnr   type   posnr_va,
             matnr   type   matnr,
             netpr   type   netpr,
             netwr   type   netwr_ap,
           end of ty_final.
    data: wa_vbak   type   ty_vbak,
          wa_vbap   type   ty_vbap,
          wa_final  type   ty_final.
    data: it_vbak   type   standard table of   ty_vbak,
          it_vbap   type   standard table of   ty_vbap,
          it_final  type   standard table of   ty_final.
    data: v_vbeln   type   vbeln_va.
    data: cust   type   ref to     cl_gui_custom_container,
          alv    type   ref to     cl_gui_alv_grid,
          event_receiver TYPE REF TO event_class.
    data: wa_fcat       type    lvc_s_fcat,
          it_fcat       type    lvc_t_fcat,
          wa_layout     type    lvc_s_layo.
    *Declaration for toolbar buttons
    DATA : ty_toolbar TYPE stb_button.
    data: c_alv_toolbar    TYPE REF TO lcl_alv_toolbar.      "Alv toolbar
    *&               S E L E C T I O N     S C R E E N
    SELECT-OPTIONS: ss_vbeln FOR v_vbeln.
    *&                 I N I T I A L I Z A T I O N
    INITIALIZATION.
      PERFORM initial.
    *&               A T   S E L E C T I O N - S C R E E N
    AT SELECTION-SCREEN.
      PERFORM at_sel_scr.
    *&            S T A R T - O F - S E L E C T I O N
    START-OF-SELECTION.
      PERFORM sel_records.
      PERFORM join_tables.
      PERFORM alv_output.
    * CLASS lcl_event_receiver DEFINITION
    CLASS event_class DEFINITION.
    *Handling double click
      PUBLIC SECTION.
      METHODS:
        handle_double_click
        FOR EVENT double_click OF cl_gui_alv_grid
        IMPORTING e_row e_column.
    ENDCLASS. "lcl_event_receiver DEFINITION
    * CLASS lcl_event_receiver IMPLEMENTATION
    CLASS event_class IMPLEMENTATION.
    METHOD handle_double_click.
      case e_column.
        when 'MATNR'.
          read table it_final into wa_final index e_row-index.
          set parameter id 'MAT' field wa_final-matnr.
          call transaction 'MM03' and skip first screen.
       endcase.
    ENDMETHOD.           "handle_double_click
    endclass.
    *       CLASS lcl_alv_toolbar DEFINITION
    *       ALV event handler
    CLASS lcl_alv_toolbar DEFINITION.
      PUBLIC SECTION.
    *Event for toolbar
        on_toolbar
           FOR EVENT toolbar
           OF  cl_gui_alv_grid
           IMPORTING e_object e_interactive,
      handle_user_command
            for event user_command of cl_gui_alv_grid
                importing e_ucomm.
    endclass.
    *       CLASS lcl_alv_toolbar IMPLEMENTATION
    *       ALV event handler
    CLASS lcl_alv_toolbar IMPLEMENTATION.
    METHOD on_toolbar.
    *   Add customized toolbar buttons.
    *   variable for Toolbar Button
        clear ty_toolbar.
        ty_toolbar-icon      =  icon_create.
        ty_toolbar-butn_type = 0.
        ty_toolbar-text = 'CREATE'.
        APPEND ty_toolbar TO e_object->mt_toolbar.
        clear ty_toolbar.
        ty_toolbar-icon      =  icon_change.
        ty_toolbar-butn_type = 0.
        ty_toolbar-text = 'UPDATE'.
        APPEND ty_toolbar TO e_object->mt_toolbar.
        clear ty_toolbar.
        ty_toolbar-icon      =  icon_system_save.
        ty_toolbar-butn_type = 0.
        ty_toolbar-text = 'SAVE'.
        APPEND ty_toolbar TO e_object->mt_toolbar.
    ENDMETHOD.                    "on_toolbar
    method handle_user_command.
    case e_ucomm.
        when 'CREATE'.
        when 'UPDATE'.
    endcase.
    endmethod.                           "handle_user_command
    ENDCLASS.            "lcl_event_receiver IMPLEMENTATION
    *&      Module  STATUS_2008  OUTPUT
    *       text
    MODULE status_2008 OUTPUT.
      SET PF-STATUS 'MENU1'.
      SET TITLEBAR 'TITLE1'.
    ENDMODULE.                 " STATUS_2008  OUTPUT
    *&      Module  alv_display  OUTPUT
    *       text
    MODULE alv_display OUTPUT.
      IF cust IS INITIAL.
    *    Creating object of container
        CREATE OBJECT cust
        EXPORTING
          container_name              = 'CUSTOM'.
    *    Creating object of alv
        CREATE OBJECT alv
          EXPORTING
            i_parent          = cust.
    ** create ALV event handler
    *  CREATE OBJECT c_alv_toolbar
    *    EXPORTING
    *      io_alv_grid = alv.
    create object c_alv_toolbar.
    * Register event handler
      SET HANDLER c_alv_toolbar->on_toolbar FOR alv.
      set handler c_alv_toolbar->handle_user_command for alv.
    *    alv layout
        PERFORM alv_layout.
    *    alv field catalogue
        PERFORM fieldcatalog_display.
    *    Displaying the ALV grid
        CALL METHOD alv->set_table_for_first_display(
          EXPORTING
            is_layout                     = wa_layout
          CHANGING
            it_outtab                     = it_final
            it_fieldcatalog               = it_fcat ).
    *Create object of the event class and setting handler for double click
        CREATE OBJECT event_receiver.
        SET HANDLER event_receiver->handle_double_click FOR alv.
    ENDIF.
    ENDMODULE.                 " alv_display  OUTPUT
    *&      Module  USER_COMMAND_2008  INPUT
    *       text
    module USER_COMMAND_2008 input.
      case ok_code_2008.
        when 'EXT'.
          leave program.
        when 'BCK'.
          leave to screen 0.
        when 'UP'.
          leave program.
      endcase.
    endmodule.                 " USER_COMMAND_2008  INPUT
    *&                E N D   O F   M A I N   P R O G R A M
    *&      Form  initial
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM initial .
      CLEAR: wa_vbak,
             wa_vbap,
             wa_final.
      REFRESH: it_vbak,
               it_vbap,
               it_final.
    ENDFORM.                    " initial
    *&      Form  at_sel_scr
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM at_sel_scr .
      SELECT vbeln
        INTO TABLE it_vbak
        FROM vbak
        WHERE vbeln IN ss_vbeln.
      IF sy-subrc <> 0.
        MESSAGE e000.
      ENDIF.
    ENDFORM.                    " at_sel_scr
    *&      Form  sel_records
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM sel_records .
      SELECT vbeln
             erdat
             vkorg
             spart
      INTO TABLE it_vbak
      FROM vbak
      WHERE vbeln IN ss_vbeln.
      IF sy-subrc <> 0.
        MESSAGE e000.
      ENDIF.
      SELECT vbeln
             posnr
             matnr
             netpr
             netwr
      INTO TABLE it_vbap
      FROM vbap
      FOR ALL ENTRIES IN it_vbak
      WHERE vbeln = it_vbak-vbeln.
      IF sy-subrc <> 0.
        MESSAGE e000.
      ENDIF.
    ENDFORM.                    " sel_records
    *&      Form  join_tables
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM join_tables .
      SORT it_vbak BY vbeln.
      SORT it_vbap BY vbeln posnr.
      LOOP AT it_vbap INTO wa_vbap.
        READ TABLE it_vbak INTO wa_vbak WITH KEY vbeln = wa_vbap-vbeln
        BINARY SEARCH.
        wa_final-vbeln = wa_vbak-vbeln.
        wa_final-erdat = wa_vbak-erdat.
        wa_final-vkorg = wa_vbak-vkorg.
        wa_final-spart = wa_vbak-spart.
        wa_final-posnr = wa_vbap-posnr.
        wa_final-matnr = wa_vbap-matnr.
        wa_final-netpr = wa_vbap-netpr.
        wa_final-netwr = wa_vbap-netwr.
        APPEND wa_final TO it_final.
        CLEAR wa_final.
      ENDLOOP.
    ENDFORM.                    " join_tables
    *&      Form  alv_output
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM alv_output .
      CALL SCREEN 2008.
    ENDFORM.                    " alv_output
    *&      Form  alv_layout
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM alv_layout .
      wa_layout-grid_title = 'SALES ORDER'.
      wa_layout-zebra = 'X'.
    ENDFORM.                    " alv_layout
    *&      Form  fieldcatalog_display
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM fieldcatalog_display .
    *  IT_FINAL-VBELN.                    SALES ORDER NUMBER
      CLEAR wa_fcat.
      wa_fcat-col_pos  ='2'.
      wa_fcat-fieldname ='VBELN'.
      wa_fcat-tabname  ='IT_FINAL'.
      wa_fcat-key      = 'X'.
      wa_fcat-just     = 'L'.
      wa_fcat-hotspot  = ' '.
      wa_fcat-lzero    ='X'.
      wa_fcat-seltext ='SALES ORDER NO.'.
      wa_fcat-outputlen   = 15.
      wa_fcat-ref_table ='VBAK'.
      APPEND wa_fcat TO it_fcat.
    *  IT_FINAL-POSNR.                    SALES ITEM NUMBER
      CLEAR wa_fcat.
      wa_fcat-col_pos  ='3'.
      wa_fcat-fieldname ='POSNR'.
      wa_fcat-tabname  ='IT_FINAL'.
      wa_fcat-key      = 'X'.
      wa_fcat-just     = 'L'.
      wa_fcat-hotspot  = ' '.
      wa_fcat-lzero    ='X'.
      wa_fcat-seltext ='SALES ITEM NO'.
      wa_fcat-outputlen   = 15.
      wa_fcat-ref_table ='VBAP'.
      APPEND wa_fcat TO it_fcat.
    *  IT_FINAL-ERDAT.                    DATE ON WHICH DOCUMENT WAS CREATED
      CLEAR wa_fcat.
      wa_fcat-col_pos  ='4'.
      wa_fcat-fieldname ='ERDAT'.
      wa_fcat-tabname  ='IT_FINAL'.
      wa_fcat-key      = ' '.
      wa_fcat-just     = 'L'.
      wa_fcat-hotspot  = ' '.
      wa_fcat-lzero    ='X'.
      wa_fcat-seltext ='DATE OF CREATION'.
      wa_fcat-outputlen   = 10.
      wa_fcat-ref_table ='VBAK'.
      APPEND wa_fcat TO it_fcat.
    *  IT_FINAL-VKORG.                    SALES ORGANIZATION
      CLEAR wa_fcat.
      wa_fcat-col_pos  ='5'.
      wa_fcat-fieldname ='VKORG'.
      wa_fcat-tabname  ='IT_FINAL'.
      wa_fcat-key      = ' '.
      wa_fcat-just     = 'L'.
      wa_fcat-hotspot  = ' '.
      wa_fcat-lzero    ='X'.
      wa_fcat-seltext ='SALES ORG'.
      wa_fcat-outputlen   = 10.
      wa_fcat-ref_table ='VBAK'.
      APPEND wa_fcat TO it_fcat.
    *  IT_FINAL-SPART.                    DIVISION
      CLEAR wa_fcat.
      wa_fcat-col_pos  ='6'.
      wa_fcat-fieldname ='SPART'.
      wa_fcat-tabname  ='IT_FINAL'.
      wa_fcat-key      = ' '.
      wa_fcat-just     = 'L'.
      wa_fcat-hotspot  = ' '.
      wa_fcat-lzero    ='X'.
      wa_fcat-seltext ='DIVISION'.
      wa_fcat-outputlen   = 10.
      wa_fcat-ref_table ='VBAK'.
      APPEND wa_fcat TO it_fcat.
    *  IT_FINAL-MATNR.                    MATERIAL NUMBER
      CLEAR wa_fcat.
      wa_fcat-col_pos  ='7'.
      wa_fcat-fieldname ='MATNR'.
      wa_fcat-tabname  ='IT_FINAL'.
      wa_fcat-key      = ' '.
      wa_fcat-just     = 'L'.
      wa_fcat-hotspot  = ' '.
      wa_fcat-lzero    ='X'.
      wa_fcat-seltext ='MATERIAL NUMBER'.
      wa_fcat-outputlen   = 20.
      wa_fcat-ref_table ='VBAP'.
      APPEND wa_fcat TO it_fcat.
    *  IT_FINAL-NETPR.                    NET PRICE
      CLEAR wa_fcat.
      wa_fcat-col_pos  ='8'.
      wa_fcat-fieldname ='NETPR'.
      wa_fcat-tabname  ='IT_FINAL'.
      wa_fcat-key      = ' '.
      wa_fcat-just     = 'L'.
      wa_fcat-hotspot  = ' '.
      wa_fcat-lzero    ='X'.
      wa_fcat-seltext ='NET PRICE'.
      wa_fcat-outputlen   = 15.
      wa_fcat-ref_table ='VBAP'.
      APPEND wa_fcat TO it_fcat.
    *  IT_FINAL-NETWR.                    NAET VALUE
      CLEAR wa_fcat.
      wa_fcat-col_pos  ='9'.
      wa_fcat-fieldname ='NETWR'.
      wa_fcat-tabname  ='IT_FINAL'.
      wa_fcat-key      = ' '.
      wa_fcat-just     = 'L'.
      wa_fcat-hotspot  = ' '.
      wa_fcat-lzero    ='X'.
      wa_fcat-seltext ='NET VALUE'.
      wa_fcat-outputlen   = 15.
      wa_fcat-ref_table ='VBAP'.
      APPEND wa_fcat TO it_fcat.
    ENDFORM.                    " fieldcatalog_display
    Regards,
    Darpana.
    Edited by: Darpana Ahire on Dec 3, 2008 7:10 AM
    Edited by: Matt on Dec 4, 2008 12:04 PM - added  tags

    im99_chs wrote:
    I have created a package with some functions in it.Keep in mind that these functions requires PL/SQL code to be executed. Thus it needs a context switch from the SQL engine (executing your view code) to the PL/SQL engine (to do the function call).
    This may work fine for smaller data sets. But it does not scale well as context switches are expensive operations with inherent latency. The more switches there are, the bigger the execution time chunk required for context switching.
    The ideal is to rather use SQL to perform the work of the function. SQL code can implement if-then-else logic via the DECODE() SQL function and SQL CASE command. Analytical functions can be used for complex aggregation and calculation.
    If a user define (PL/SQL) function is needed, then ensure that the function is as fast as possible (minimal moving parts), and consider defining it as a deterministic function if the same input always produces the same output.

  • Cannot Create Update Rule from Infosource to Cube

    Hello;
    I am a beginner to BI and am learning. This may be a very basic question, but I got stuck.
    In the create update rule screen, I get an error message that says
    Data Source (whatever the name is) not maintained. (check your entries)
    Could some one help as to where I went wrong?
    Thx,
    Sushma
    Su

    Goto your InfoSource and open DataSource Structure and transfer structure. Check if the structure is correct, make the necessary changes if required and activate it. Then create update rules providing correct infosource name. Until you create /activate your transfer structure, you won't be able to create update rules.
    Reward point if helps.
    Regards,
    Ashok
    Message was edited by:
            ashok saha

  • Steps to create Info Packages in BI 7.0

    Please Give Steps top create new Info packages in BI7.0

    Hi,
    Steps to create Generic data source:
    If you want to extract the data from MM table in BI Please follow the below steps.
    1) Create a view on that table By going in to se11( Do this for future purpose, no need of joining conditon as of now why because view is containing only one table at this juncture)
    2) Go to RSO2, create generic data source based on view and designate this datasource under mm application component, it helps to replicate easily from the source system in BI side.
    3) While Creating datasource make sure that field selections and selection criteria for fields.
    4)Assign it to a package(specified by the team) for transportation purpose. Make sure the dependencies also will be going through request other wise the request may fail.
    5) Replicate the generic datasource in BI System(by going in to the mm appln comp under r/3 source system)
    6) After replication do create info package, transformations and dtp also.
    7) Trigger the Info package and then DTP.
    now data will be there in your data target in BI system
    Steps to create standard data source
    1> Go to RSA5 ,Select what data source u want , CLICK Transferstructure.
    2> After dooing this u can see the structure in RSA6 , if u want to do any customozation by adding extra fields u can do it her , if not no need.
    3> go to RSA3 and check if the structure is pulling data or not .
    BW SIDE
    4> Select Source system ->Replicate data source
    5> create Transfer rules , update rules and cube and u are done
    6> u can create a infopackage and schedule ur data load into the cube or ods.
    Hope this helps you
    Regards,
    Rakesh

  • Creating a Package for Constant Variables

    Hi
    I expect this should be an easy question for some of you, but I am fairly new to PL/SQL!
    Anyhow, I would like to create an PL/SQL Script as a package, which holds a list of Constant Variables, which will be common across a number of PL/SQL Packages rather than having to repeat the constants again and again over a number of files and then having the worry of trying to maintain them all.
    Can someone please advise me how to create such a package?
    Thanks

    You can create the package this way:
    create or replace package myconst is
    const1 number := 0;
    const2 number := 2;
    end;
    /And you can optionally initialize your constants this way:
    create table myconstTable  (c1 number, c2 number);
    insert into myconstTable values (1,2);
    create or replace package body myconst is
    begin
      Select c1,c2
        into const1,const2
        from myConstTable;
    end;
    /And finally you can use it this way:
    set serverout on
    exec dbms_output.put_line(myconst.const1);
    1Max
    [My Italian Oracle blog|http://oracleitalia.wordpress.com/2009/12/18/table-elimination-oppure-join-elimination-lottimizzatore-si-libera-della-zavorra/]

  • Windows CCP Failing to create a package successfully....

    Hi All,
    I have been trying to create a test package with CCP. I have limited it to include just Acrobat 11 and updates to make the logs easier to follow:
    OS: Windows 8 64bit
    9/10/2013 17:25:42[INFO] AdobePackageBuilder - Build Version - 1.2.0.4
    9/10/2013 17:25:42[INFO] AdobePackageBuilder - Logging Level verbosity Set  to 4
    9/10/2013 17:25:42 [INFO] AdobePackageBuilder - Successfully retrieved TargetName from OptionXML.
    9/10/2013 17:25:42 [WARN] AdobePackageBuilder - Error in creating file for 7z test output. Error code : 3
    9/10/2013 17:25:42 [WARN] AdobePackageBuilder - Preprocessing of 7z file failed!
    9/10/2013 17:25:44 [INFO] AdobePackageBuilder - Sucessfully extracted the product at C:\Users\tryhorn.tim\AppData\Local\Temp\{34378342-D2BE-465E-AF4E-313B6E4393A1}\ACCCx2_1_2 _232
    9/10/2013 17:25:44 [INFO] AdobePackageBuilder - Extraction completed with return code = 0
    9/10/2013 17:25:56 [INFO] AdobePackageBuilder - Copied File (payloads\Media_db.db)
    9/10/2013 17:25:56 [INFO] AdobePackageBuilder - Copied File (payloads\Media_db.sig)
    9/10/2013 17:25:56 [INFO] AdobePackageBuilder - ASU at Path (C:\Adobe Pack
    ages\Adobe Acrobat XI 32-bit\Build\Setup\Adobe Acrobat XI Pro_0\Set-up.exe) is not found. Skipping copying and renaming.
    9/10/2013 17:25:56 [INFO] AdobePackageBuilder - Copying the content of 1 disk
    9/10/2013 17:26:05 [INFO] AdobePackageBuilder - Successfully created Setup.ini file for Acrobat Customized Wizard.
    While a package is created if you try to execute it it crashes to desktop.
    Any Ideas?
    Thanks,
    Tim

    Hi Servite College,
    Could you please try a different network source to create a package.
    Additionally:
    The following host/port combinations may need to be whitelisted when logging in with an Adobe ID to download, install, and activate licensing for applications via a Creative Cloud membership.
    ccmdls.adobe.com:443
    ims-na1.adobelogin.com:443
    na1r.services.adobe.com:443
    prod-rel-ffc-ccm.oobesaas.adobe.com:443
    lm.licenses.adobe.com:443
    ccmdl.adobe.com:80
    swupmf.adobe.com:80
    swupdl.adobe.com:80
    Note: Please make 32 bit package on 32 bit machine and 64 bit package on 64 bit machine.
    Regards,
    Romit Sinha

  • Problem with update packages MDT

    Hi, when i build boot image with update packages the mdt it give me a error
    Error: 0x800f081e
    The specified package is not applicable to this image.
    Exit code = -2146498530
    The wim file is take from win 7 italian iso x64, the updates I push in mdt are the same that I install on test machine with italian iso.
    I think the problem is in some script of mdt when "update deployment share"

    The only update that I recall being required for WAIK 3 was the advanced format drive patch (Unless you have the WAIK 3.1 update in which case it is unneeded).
    So can you post the output that is failing?  Specifically when you choose Update Deployment Share and it is building the boot wims can you select 'Save Output' and post that output here?
    What version of MDT are you using?
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Local Update Publisher question

    I need to send MSXML 4.0 SP3 Parser out because for some reason WSUS says its not needed but another program that checks for vulnerabilities says its needed.  I created the package in Local Update Publisher but when I tested it a PC it was listed twice. 
    Is there a way for this to check its installed in Programs and Features?  I see it does by package ID but that doesn't help as this is a new package so no one will have it.  Looking at NOT MSI Product Installed rule I am not seeing how to do
    it.

    In the case of MSXML4, I'll believe the independent checker, since otherwise the only way to get SP3 is to manually download and install it.
    As for the product itself, there's only one file of interest, but it's in different locations depending on product architecure.
    For x86 systems, it's ~\system32\msxml4.dll
    For x64 systems it's ~\syswow64\msxml4.dll
    MSXML v4 is a 32-bit only system.
    What do you mean by "when I tested a PC it was listed twice"? What was listed twice? There may be multiple instances of MSXML v4 in Programs and Features, if different versions were installed at different times, but there can only be one MSXML4.DLL in the
    system folder.
    Testing by PackageID is one way to deal with this scenario, but I believe you'll find it much more reliable, and certainly a lot simpler, to just test the File Version on the MSXML4.DLL file. (The File Version of the SP3 file is 4.30.2100.0.)
    Also consider why MSXML4 is present on a system to begin with. Is the application that installed it still present, and still in use? If not, uninstalling MSXML v4 would be a preferable action to trying to maintain it.
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • Creating Query : Package required

    Hi Experts,
    We are creating and changing queries in PRD (BW 3.5, SP21) . Up to now, system works as designed, all elements were assigned to package $tmp automatically.
    But now users are complaining, that they are prompted to select a package when saving a query.
    I'm not aware that our team has changed any settings.
    Any ideas / suggestions ? Thanks in advance.
    Regards
    Joe

    Hi
    So is it necessary that it should prompt for the package once upgrade is done from 3.x to 7.0 when we change the query in 7.0 of 3.x copy queries???Could I know why it is prompting???where can I change the settings to prompt for it?
    Could I know how to create temporary package, as I dont see any option for $tmp ,whenever i do changes for objects,it opt for new request???
    hi JH, Thanks for bringing up this question as I face the same issue.
    BI Learner.

  • HTP package question

    I have a feeling I'm in the wrong place for this question but maybe someone can help.
    I'm not so good with Oracle configuration and setup issues but I have created a package with a few procedures that output info using the HTP package. At my old place of employment we had a web server set up and we could use
    http://ouraddress.com/packagename.procedurename?p_param1=123&p_param2=456
    We have a web-based application server set up for Oracle Forms (eBusiness Suite) but I don't know if I'm able to do something like this or not. Where/what do I need to set up to use this type of functionality?
    null

    PL/SQL Web Development Tools: Oracle Database provides built-in tools and technologies that enable you to deploy PL/SQL applications over the Web. Thus, PL/SQL serves as an alternative to Web application frameworks such as CGI.
    The PL/SQL Web Toolkit is a set of PL/SQL packages that you can use to develop stored procedures that can be invoked by a Web client. The PL/SQL Gateway enables an HTTP client to invoke a PL/SQL stored procedure through mod_plsql, which is a plug-in to Oracle HTTP Server. This module performs the following actions:
    - Translates a URL passed by a browser client
    - Calls an Oracle Database stored procedure with the parameters in the URL
    - Returns output (typically HTML) to the client
    You got to start from here:
    Developing Applications with the PL/SQL Web Toolkit
    http://download-east.oracle.com/docs/cd/B19306_01/appdev.102/b14251/adfns_web.htm#g1026380

Maybe you are looking for