Changing version of a package

How do I change the version of package without creating a new instance?
I have a package installed:
PKG = ABCDmypkg
VERSION = 2.3
I would like to change the package such that when the new version is pkgadd'ed, then its version number changes to 3.1 without doing a pkgrm.
The technique described in "Upgrading Packages" section of the Application Packaging Developer's Guide is not usable because, if I create a package with
PKG=ABCDmypkg
VERSION=3.1
then when I do pkgadd, it installs a second instance
named ABCDmypkg.2 which I don't want.
I want to change (upgrade) the package so that it
remains ABCDmypkg but the VERSION becomes 3.1
How do I do that?
Thank you.

You'll probably get best answer at one of the Solaris forums,
http://forum.sun.com/category.jspa?categoryID=2

Similar Messages

  • Version of the package

    hi
    i am opening old package into new ssis.
    i need to know in which version package build like 2005 ,2008 etc
    how to see it

    Hi coool_sweet,
    To find out the version our SSIS Package, we need to read the .dtsx file itself. We can open the file by using different programs such as Notepad. The .dtsx files are xml files and the property we need to look for is "PackageFormatVersion".
    Based on my research, in SQL Server 2005 Integration Services, the PackageFormatVersion property of a .dtsx file is set to 2; in SSIS 2008 and SSIS 2008 R2, the PackageFormatVersion value is to set to 3. In SSIS 2012, the value of the PackageFormatVersion
    property is 6; in SSIS 2014, the value of the PackageFormatVersion property is 8.
    For more details, please refer to the following article:
    http://blogs.msdn.com/b/mattm/archive/2011/08/10/package-format-changes-in-sql-server-denali.aspx
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Undoing changes made by support package application

    Hi
    Is there a way to undo changes made to repository objects and dictionay objects after you have imported a support package.
    Let us consider this with an example. Let us assume that there is a standard SAP report called S1 v1. Which after a support package application and after confirming the queue it becomes S1 v2. Now if for some reason after say 2-3 days we are not comfortable with S1 v2 and want S1 v1 again can we get back the old standard SAP report. If so then how?
    Also if there is a change made in a Dictionary object, is there a way to revert these changes on a similar line? Id so then how.
    Thanks
    Rohan

    Hi Lokesh,
    If you have maintained versions for perticular report then you can revert it back to the previous version.
    Ask your ABAPer for the same.
    You can always retrieve the previous version if you have maintained the version.
    It is applicable for the dictionary objects too, but you may loose data in case of changing version for database tables.
    Regards,
    Payal

  • I would need several version of a package

    I think I saw this somewhere on Arch web site : only one version of each package, latest one.
    But, I need several version of some packages.
    I'm a developer, and I need apache tomcat 4 & 5 (web server mostly use version 4).
    The same for php, I need version 4 as I have to use this version for some project.
    I would also need mysql version 4.0 (and latest 3;XX) because I have to use them at work for various resons.
    There are many example. I know I can install these manually, but it's a shame as there is a powerful package manager.
    I don"t say that every packages sould have several version, but some obviously need.
    Is there any plan on adding such a feature ?

    you have the tools to host local repositories with the olser packages you need. you can get old build from the web interface to the CVS and all you would have to do is change some destination locations so that the older or newer packages are not replacing each other.
    As for official Arch support ... it may someday happen but only if there are the people who need and one of them want sto maintain the packages

  • How to delete an active change version of a PO?

    Hi all mates,
    question: given a PO number, assuming that the active version is a change one and the previous version has been ordered (I don't know if this is the proper word: I mean "transferred to the backend" (R/3))... is there a simple way, e.g, a FM, to delete the last version of a PO, so that this goes definitely lost and the previous version is restored and set to active?
    As usual, thanks in advance
    Matteo
    EDIT:
    after reading a bit, I'd like to add further details:
    - what I call a "change version" is actually a new version of the purchase order which is in status "HELD";
    - 'transferred to the backend' -> the current version of the purchase order is in status "ORDERED".
    Then, if i click on the "version" tab in SRM, i can see that an order modified after distribution has a previous version (status "ORDERED") and a current version (in status "HELD").
    I'd like to know if there's a way to delete the current active version and restore the previous, ORDERED version. The question arises because I'm creating a report that makes an update of a Purchase order, but to do so the order must be in status 'ORDERED' so if an HELD version is active I should "rollback" to the previous one... or alternatively, I must manage overwriting the HELD version currently active ( I wasted a lot of time but I wasn't able to do it ).
    Edited by: Matteo Montalto on Apr 8, 2009 12:45 PM

    Hi, I have the same problem. Can you tell me the solution that you have find ??

  • How can you ignore one specific version of a package when upgrading?

    Hi all,
    Due to a rather nasty bug in mplayer, the current version in the Arch repositories is unusable for me.  I am currently running the previous version without any problems, but every time I try to upgrade, pacman wants to reinstall this broken version.
    I don't want to list mplayer in the IgnorePkgs option, because then I won't get any new versions.  Since the bug has long been fixed, the next Arch version should work fine - it's just the current Arch version (35014) that is broken and I want to ignore.
    Is there some way I can blacklist this specific version of the package, so although it won't ever be installed, any newer version will?
    I tried adding "mplayer-35014" and "mplayer-35014-1" to IgnorePkgs but it didn't work.
    Any suggestions?

    Hmm, I hadn't thought of that.  I didn't actually build a package from it, because I didn't know where the problem was.  So I just compiled a bunch of things the old fashioned way and ran them without installing anything until I had narrowed down the problem.  But I'm sure there's an mplayer-svn in AUR I could use - good idea.

  • PDO Layer Error while approving a changed version of PO

    Hi,
    We are in SRM7.0 , EC Scenario , ECC 6.0
    In SAP SRM system am experiencing a workflow issue , second level approver is not able to approve/receive the workitem of a changed PO. Moment we try to open the PO (changed version) and navigate to Approval tab, the approval flow is missing and showing the error as
    PDO Layer Error
    An Exception has occured
    Every time we must restart the workflow due to which the approval needs to be done again from 1st approver.
    We have raised an OSS Message and following is the response from SAP
    " The second approver does not get an workitem because the workflow got the status error. The cause of this error is your BADI implementation
    ZCL_SRMWF_AGENT_PO_BUYER method /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_AREA_TO_ITEM_MAP. This method returns an initial table LT_AREA_TO_ITEM_MAP.
    Run method CREATE_DECISION_SETS (/SAPSRM/CL_WF_PROCESS_MGR_SBWF) with
    parameter IV_PROCESS_GUID = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx "
    When i executed this method CREATE_DECISION_SETS (/SAPSRM/CL_WF_PROCESS_MGR_SBWF) with
    parameter IV_PROCESS_GUID = Changed version PO GUID , i got the following error
    Exception CX_BO_ABORT triggered
    Termination triggered in '' - Rollback required
    Can anyone please help !!
    Thanks & Regards,
    Venkat

    Hi ,
       can you please share your Badi code?
    Saravanan

  • Buffer Table Not Up To Date Short Dump When Publishing Change Version of Bid Invitation

    Hi experts,
    We are running SRM 5.5 with Support Level 16.
    We have a bid invitation for which a user is trying to publish a Change Version. This bid contains two bid outlines, with one line item in each bid outline:
    ITEM 1: HIER (Bid Outline)
    ITEM 2: Line Item
    ITEM 3: HIER (Bid Outline)
    ITEM 4: Line Item
    However, upon clicking on the Check or Publish button, the system throws a CX_BBP_PD_ABORT exception short dump. The reason for the exception given in ST22 is "Buffer table not up to date".
    Due to organisational system security restrictions, I am unable to copy-paste the dump from ST22, so I will be typing out some of the details here.
    Transaction: BBP_BID_INV
    Program: SAPLBBP_PDH
    Screen: SAPLBBP_BID_INV_1000
    Termination occurred in the ABAP program "SAPLBBP_PDH" - in "BBP_PD_ABORT". The main program was "SAPLBBP_BID_INV".
    In the source code you have the termination point in line 73.
    Active Calls/Events
    (formatted below as "No: Type: Name")
    24: Function: BBP_PD_ABORT
    23: Form: ABORT
    22: Form: ITMADM_UPDATE
    21: Form: ITMADM_MAINTAIN_SINGLE
    20: Form: ITEM_F_CHECK_FROM_WTAB
    19: Form: ITEMLIST_F_CHECK
    18: Function: BBP_ITEMLIST_CHECK
    17: Form: PROCDOC_DB_CHECK
    16: Form: PROCDOC_CHECK
    15: Function: BBP_PROCDOC_CHECK
    14: Form: SSIS_DOCUMENT_CHECK_COMPLETE
    13: Form: STATUS_SET_AND_INTERNAL_SAVE
    12: Form: PROCDOC_UPDATE
    11: Function: BBP_PROCDOC_UPDATE
    10: Form: CHANGE_VERSION_UPDATES_ACTIVE
    9: Function: BBP_PDCV_UPDATE_ACTIVE
    8: Form: PROCDOC_CHECK
    7: Function: BBP_PROCDOC_CHECK
    6: Function: BBP_PD_BID_CHECK
    5: Form: FCODE_DOCUMENT_CHECK
    4: Form: FCODE
    3: Function: BBP_BID_PROCESS
    2: Form: PROCESS
    1: Module (PAI): PROCESS
    The ABORT subroutine is being called in Step 22 (ITMADM_UPDATE), at the following line:
    * parent guids have to be identical ...
    if gt_itmadm-parent <> w_itmadm-parent.
      perform abort.
    endif.
    Upon tracing the variable values in the ST22 dump, it appears the program terminates when processing line 3 (i.e. the second Bid Outline). It appears that the first Bid Outline processes fine.
    In the iteration for Line 3, the dump provides that gt_itmadm-parent contains the GUID to the Change Version document header, whereas w_itmadm-parent contains the GUID to the original Bid Invitation document header, resulting in a mismatch and subsequently program termination.
    We have tried to replicate this bid invitation in our Development environment, but when executing, both gt_itmadm-parent and w_itmadm-parent contain GUIDs to the Change Version document header, hence the program does not abort.
    Any suggestions would be greatly appreciated.
    Thanks!
    Best regards,
    Kwong How

    Hi Janu,
    For Note 1561750, I have looked at the Correction Details and observed that it makes changes to an IF-ELSE block, but will result in the same path of code execution as before. I.e., the Note changes the code from "IF a THEN b, ELSE c" to just "c", but according to my code trace, we are already executing the "ELSE c" block in its current state.
    We will look further into Note 1877600. The unfortunate situation here is that since we are unable to replicate this issue in our Development/QA environment, and the Note description does not explicitly fit the situation we are facing, we need to be very sure that the Note can address the issue before bringing it into Production.
    Otherwise, we will raise a message as suggested.
    Thank you so much for your help!
    Best regards,
    Kwong How

  • PO change version Approval/Rejection notification to requester

    Dear SRM Gurus,
    We are in stand alone scenarion of SRM 7.0 using process controlled WF.
    We have received an request to send out notification on approval / rejection of and PO change version.
    The PO's are created automaticaly from approved SC's and only the PO change triggers the approval WF.
    I've already checked the IMG: SRM server > cross application > Event and event schema for alert management.
    1. Define events: BUS2201 Purchase order is present with APPROVAL_PROCESS_DOC_APPROVED and APPROVAL_PROCESS_DOC_REJECTED
    2. Define event schema for obj. type BUS2201 event schema PO the APPROVAL_PROCESS_DOC_APPROVED and APPROVAL_PROCESS_DOC_REJECTED with subcategory event APPROVAL_RESULT_NOTIFIC_NEW are set to event category NOTIFIC Message.
    3. Define Recipient of notifications: PM Approve change version of purchase order - User Role CR contact person the options rejection and approval of application object are selected.
    The users I'am using to test are the same as those who receive notifications for SC rejection/approval so I guess it's not connected to SU01 or PPOMA settings.
    Still I don't see notification sent via SOST.
    Any ides what I could check next please?
    Thanks in advance for you help.
    Michal

    Hello Michal,
    did you give the event schema created to corresponding transaction type ?
    If you are expecting to receive notification during approval workflow, check OSS note [1395980 - No notifications of approval sent during approval process|https://websmp101.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1395980&_NLANG=E]
    For PO, you can also check OSS note [1572957 - PO change version reject notification not sent|https://websmp101.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1572957&_NLANG=E]
    Regards.
    Laurent.

  • Output for changes versions in SRM

    Hello,
    We are currently trying to control when our SRM (server 550)system is to send output to our vendors, but the output is only to be sent if specific elements in an order is changed.
    To do this we are using the table BBPD_COMP_FIELDS.
    This works very well, there is just one problem that we cant seem to understand why.
    If you created an order, then change the order with something that was not suppost to send output (because it is set in the table above) it sends the output. If you then change the same again it will not send out put (which is correct).
    So what it does is for changes that shouldent send output when changed:
    order --> output (correct)
    change1 --> output (Wrong)
    change2 --> no output (correct)
    it should of been:
    order --> output
    change1 --> no output
    change2 --> no output
    Question is why and how do we get it to stop doing this?
    Hope someone can help us.
    Best Regards
    Lisa M Simonsen

    Hi
    Use the PO version control BADi to change the version for the PO on identified field changes. In SPRO, out put conditions, trigger the change output when there is a change version of the document. This should work.
    BBPD_COMP_FIELDS (with SM30). There is something mentioned about which fields to compare for PO output, you have to scroll some way down to get there.
    Re: Changed PO output
    Also, Please go through the following pointers, which might help you out.
    Re: PO output fields
    Re: Control PO output to vendor
    Re: No Output Condition on Purchase Orders
    Version Details
    Do let me know.
    Regards
    - Atul

  • Action not possible because change version exist

    Dear All,
    We are at SRM5.0- Extended Classic scenario and facing issues for changing some of the PO documents.
    When the buyers are trying to change the PO, error is getting populated as 'Action not possible because change version exist'. This error is not allowing us to change the PO.
    These POs are changed in the past and all the relevant changes are reflected to backend system with no issues. In other words Change Versions do exists for these POs. Flags for Change Version completion is also set and all historical versions can be seen but without change history.
    Additional information -
    1. No approval workflows are implemented for PO.
    2. No locks are active for these documents.
    Appreciate your help!
    Regards,
    Sagar

    Hi Sagar and thanks for your response,
    well, actually the active change version won't be preserved in any case. It would be overwritten in the first scenario, and deleted in the second one. The reason why I'd like to have this "brute force" method is to face an eventual human error. Suppose that a disalignment between R3 and SRM has been created; my report basically "alligns" the SRM version to the corresponding R3 one. And suppose also that the user made a mistake so that the program must be used a second time. I'd like to provide a way to "UNDO" the first execution of the program, that is to say: i'd like to provide a way to OVERWRITE the actual active, change version, or alternatively delete the change version that the report did create the first time it has been launched.
    Hope it's a bit clearer now
    Thanks for any hint/suggestion you can give me
    EDIT: Oh, and please... can you provide me further information about your solution? I mean, use of that FM to unlock an active version of the PO and then the proper call to BBP_PD_PO_UPDATE specifying how you managed input params. Thanks a lot
    Edited by: Matteo Montalto on Apr 9, 2009 11:43 AM

  • Changed version of Data Entry Profile imported results in empty worklist

    Hi,
    We've just moved, among other things, changed versions of all of the data entry profiles to our production server. Everything went well however all users get an empty worklist to start with.
    Do you maybe know why this is? Is this standard behaviourd? And is/would there be any way to overcome this and do not have users start with a 'fresh' worklist?
    Your help and input is very much appreciated.
    Kind regards,
    Tim

    Hi,
    The worklist is the one available in HR transaction CAT2. Source would be HR?
    Kind regards,
    Tim

  • Changing in standard Business Package

    Hi
    I need to change the web dynpro component supplied in stanadard business package. These web dynpro component are called from portal Iviews.
    Should i make the Z copy of the webdynpro or starightway change to standard business package.
    How will it effect during upgrade or modification by SAP
    Best Regards
    Naresh

    Hi Naresh,
    when you create a z copy you must change the business package at least at the point where the WD application is called. So there are two points where SAP modifications will impact your changes.
    My suggestion: if you can't avoid using the portal at all, avoid at least making modifications.
    In the backend use the enhancement framework in order to be independent of SAP modifications. I put an example in the WD4A book, that shows how to work with the enhancement framework.
    regards, Ulli

  • PDO Layer Error in change version PO

    Hi,
    We are in SRM7.0 , EC Scenario
    In SAP SRM system am experiencing a workflow issue , second level approver is not able to approve/receive the workitem of a changed PO. Moment 1st approver approve it and when requester try to open the PO (changed version) and navigate to Approval tab, the approval flow is missing and showing the error as
    PDO Layer Error
    An Exception has occured
    Every time we must restart the workflow due to which the approval needs to be done again from 1st approver.
    We have raised an OSS Message and following is the response from SAP
    " The second approver does not get a workitem because the workflow got the status error. The cause of this error is your BADI implementation ZCL_SRMWF_AGENT_PO_BUYER method
    /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_AREA_TO_ITEM_MAP. This method returns an initial table LT_AREA_TO_ITEM_MAP.
    Run method CREATE_DECISION_SETS (/SAPSRM/CL_WF_PROCESS_MGR_SBWF) with
    parameter IV_PROCESS_GUID = change version guid xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx "
    When i executed this method CREATE_DECISION_SETS (/SAPSRM/CL_WF_PROCESS_MGR_SBWF) with
    parameter IV_PROCESS_GUID = Changed version PO GUID , i got the following error
    Exception CX_BO_ABORT triggered
    Termination triggered in '' - Rollback required
    Can anyone please help !!
    Thanks & Regards,
    Venkat

    Hi Sarvanan,
    I am a functional consultant and completely unaware of this technical stuff. Since this is SRM BRF workflows, none of our workflow consultants also are able to help me out on this issue. So, if possible could you please let me your contact number to so that i can contact you directly on this issue.
    This is the issue which i am facing from last 7 months and none of the person is able to help me out. So, i kindly request you to please help me out on this issue.
    As requested following is the code for the process level class
    ZCL_SRMWF_PRC_CONF_BUYER_PO --> GET_BUYER_APPROVERS
    METHOD get_buyer_approvers.
      DATA :  ls_header TYPE  bbp_pds_po_header_d,
              lt_item TYPE TABLE OF  bbp_pds_po_item_d,
              lw_item TYPE  bbp_pds_po_item_d,
              lt_buyer  TYPE TABLE OF zgtm_buyer,
              lw_buyer  TYPE zgtm_buyer,
              lt_limit TYPE TABLE OF  bbp_pds_limit,
              lw_approver_item TYPE zgswf_item_buyer_map,
              lv_requester_mgr    TYPE uname,
              lv_requester        TYPE uname,
              lv_appr_reqd        TYPE c.
      CALL FUNCTION 'BBP_PD_PO_GETDETAIL'
        EXPORTING
          i_guid   = iv_doc_guid
        IMPORTING
          e_header = ls_header
        TABLES
          e_item   = lt_item
          e_limit  = lt_limit.
      DELETE lt_item WHERE del_ind = 'X'.
      DELETE lt_limit WHERE del_ind = 'X'.
      CHECK lt_item IS NOT INITIAL.
      SELECT * FROM zgtm_buyer
               INTO TABLE lt_buyer
               FOR ALL ENTRIES IN lt_item
               WHERE bukrs = ls_header-co_code
               AND  matkl =  lt_item-category_id.
      LOOP AT lt_item INTO lw_item.
    *CHECK IF APPROVAL IS REQUIRED
        CALL METHOD approval_level_required
          EXPORTING
            is_header   = ls_header
            is_item     = lw_item
            it_buyer    = lt_buyer
            it_limit    = lt_limit
          RECEIVING
            rv_reqd_ind = lv_appr_reqd.
        CHECK lv_appr_reqd IS NOT INITIAL.
    *IF APPROVAL IS REQUIRED FIND THE BUYER
        READ TABLE lt_buyer INTO lw_buyer
                            WITH KEY bukrs = ls_header-co_code
                                     matkl = lw_item-category_id.
        IF sy-subrc = 0.
          lw_approver_item-owner  = lw_buyer-bname.
        ELSE.
          CLEAR lw_approver_item-owner.
        ENDIF.
        lw_approver_item-itm_no = lw_item-number_int.
        lw_approver_item-co_code = ls_header-co_code.
        lw_approver_item-matkl = lw_item-category_id.
        lw_approver_item-itm_guid = lw_item-guid.
        APPEND lw_approver_item TO rt_approver_item.
        CLEAR lw_approver_item.
      ENDLOOP.
    ENDMETHOD.
    KINDLY HELP ME OUT AND DO LET ME KNOW IF ANYTHING NEEDED FURTHER FROM MY END.
    THANKS IN ADVANCE,
    VENKAT

  • How to prevent downgrading of the app in meta package using package versioning feature of package maker tool?

    Hi,
    Created  an installer i.e, meta package using package maker tool. I want  to prevent downgrading of the application or package on the target/installed volume. 
    Problem is, if there is a newer version of app and when I try to install any older version, then it does not throw any error message to the end user and replaces the existing newer version with the older version of app, which should not happen. But, if I check the package version using version comparison of Package  maker tool, that works fine with flat packages i.e, with the .pkg files. So, I need the solution for metapackages(.mpkg) and want to prevent downgrading of app for metapackages. I am not getting any solutions for this. Can someone guide me on this?
    Thanks for the help provided.
     

    Hi,
    Created  an installer i.e, meta package using package maker tool. I want  to prevent downgrading of the application or package on the target/installed volume. 
    Problem is, if there is a newer version of app and when I try to install any older version, then it does not throw any error message to the end user and replaces the existing newer version with the older version of app, which should not happen. But, if I check the package version using version comparison of Package  maker tool, that works fine with flat packages i.e, with the .pkg files. So, I need the solution for metapackages(.mpkg) and want to prevent downgrading of app for metapackages. I am not getting any solutions for this. Can someone guide me on this?
    Thanks for the help provided.
     

Maybe you are looking for