Support package upgrade / SPAU with multiple queues

Hello,  We are upgrading our support package level on our ECC 6.0 system.  I divided up the support packages into 4 different queues:
SAP_BASIS
SAP_ABA
PI_BASIS
ST-PI
SAP_BW
SAP_AP
SAP-HR
After importing each queue, I had a few things to do in SPDD and SPAU.  I created a new SPDD or SPAU transport request for each queue.  My question is now what is the recommended procedure to handle these SPAU/SPDD transport requests when you have multiple queues?  I plan to define the same queues when doing QA and PRD.  Do I mark all of the requests and then when I do each queue, I only specify that particular request?  Thank you in advance for your help.
Best regards,
Russ Cook

Hi Russ,
when did you export the different SPAU requests or didn't you export them at all?
If the export happens only after all queues are already imported, this final system state (component version + SP level) is stored in the requests.You are then not able to include e.g. the request for the SAP_BASIS SPs into the SAP_BASIS queue, because the other components are still on the old version, while according to the request they should be on the newer state.
So, the right procedure would be; import the SP queue, do the modification adjustment for this queue, mark the workbench request as modification adjustment transport request and export this request. Then you can import the next SP queue.
Best regards,
  Dirk

Similar Messages

  • R/3 Delta queues in support package upgrade

    Hi gurus,
    Our team needs to apply a support package upgrade to our BI 7.0 (without an upgrade in R/3 source system).
    Do I need to worry about SM13 and RSA7 in my source system R/3 or just my data marts inside 7.0?
    Or do I need to empty R/3 delta queues before BI upgrade to prevent data loss?
    Best regards,
    Enric

    You may wish to take a look at below for few insights -
    OSS notes 328181 and 762951 as a prerequisites.
    Failure to follow the instructions in those notes may probably result in data loss.
    https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002662832005E
    https://forums.sdn.sap.com/click.jspa?searchID=10299818&messageID=3221895
    Hope it Helps
    Chetan
    @CP..

  • Impact of Support Package Upgrade on languages

    Dear Experts,
    We have our client with SAP CRM enterprise, ISA and MSA implemented in various countries and many languages (HU, PL, CZ, N, GR etc). We would like to know if SP (Support Package) upgrade will have any impact on the languages.
    Any pointers or help would be grateful. Since we need this information urgently, any help in this regard would be of great help.
    Points will be rewarded for useful answers.
    Regards,
    Kathir

    There will be no impact of SP's on languages. We recently installed a few SP's for our CRM 4.0 system and did not have any impact.

  • Http to Abap Proxy communication with multiple queues generation in Recevr

    Dear SDNs,
    I need some help in the following scenario, appreciate your suggestions and help .
    I am receiving the messages from sender to PI on http posting, from PI  I am sending the message to SAP system using receiver xi communication channel ( receiver is abap proxy).
    Sender will send the messages in QOS=EOIO, QUEueID=XXXt_100 etc  parameters, when large volumes cases, it is getting delayed to process it using a single queue.
    We are thinking to dynamically  generate multiple queues in PI and send the same queue ids to receiver SAP system to process all the messages quickly in SAP System also.
    Help /Clarifications needed:
    1. XI receiver communication channel in  pi  does not provide any options to generate dynamic queue id based on payload content (using dynamic configuration) and sent it to SAP.
    2. Module Tab in receiver communication channel also got disabled to add  custom adapter modules, can we add custome adapter module on xi receiver channel to generate dynamic queue id ?
    Really appreciate your immediate help and suggestions.
    Thanks.
    Suraj.

    Dear Praveen,
    Thanks lot for the immediate reply, we need to use EOIO, as the messages need to be processed in the same order we send and receive, there is no flexibility in QOS=EOIO, Appreciate if there is any other thoughts?
    Thanks In Advance.
    Suraj.

  • Hwo to do scenario with multiple queues in jms sender

    Hi users,
    In my scenario jms to idoc i have requirement from two diffrerent queues  i need to pick the data.
    if its two sender communication channels then how to create two sender agreements?
    please help out to me
    Regards

    Hi,
    Use same Queue for same kind of data
    OR
    Create multiple sender agreement by checking the "Sender uses virtual receiver" Option

  • 10.9.4 Maverick Upgrade - Issue with multiple monitors

    I have just upgraded to Maverick and there seems to be a problem with my second monitor now going to a black screen every time I use the mouse or scroll up and down a page. Is there a fix for this? Any help would be appreciated as it is very annoying.

    This is being discussed in a number of threads - unfortunately there is no single thread, but this one is most recent: Second display problem with 10.9.4
    (More unfortunately, there is no fix and Apple generally hasn't been giving a scheiß about the issue since it first cropped up in 10.9.3...)

  • Custom application is not working after the support package upgrade.

    Hi SDN Folks,
    I have upgraded the portal from SP09 to SP25 successfully. But after the upgrade our custom application is not behaving as before. When we submit anything in the custom page its returning to home page. No error in the log files also.
    Custom application is a devoloped in webdynpro java.
    Kindly suggest.
    regards,
    Mahesh.N.R

    Hi Sita,
    Currently I canot take help form the developers, please let me know where i ca checkwhether the custom URLs are set to home page.
    regards,
    Mahesh.N.R

  • How to deal with delta queue when importing Support Package/Kernel Patch

    Hi,
    From my experience, when importing a Support Package for an installation, the system will issue an error message and get stuck if this Support Package is about to alter the structures used in delta loads.
    But I would like to double with you if there is possible that the support packet which is going to alter structure, but no error message. If so, the delta data will be lost.
    Do we need to clear down the delta queue every time we import support package?
    Anyway, is there anyone have any suggestions or steps regarding this question?
    Many Thanks
    Jonathan

    Hi,
    Delta queues during support package upgrade
    Its always better to drain the delta queues before an upgrade.
    As a standard practice we drain the delta queues by running the IP/ chain multiple times.
    As a prerequiste we cancel/reschedule the V3 jobs to a future date during this activity.
    The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss.
    V3 collector jobs should be suspended for the duration of the upgrade.
    They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
    See SAP Notes 506694 and 658992 for more details.
    Page 17
    Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
    The SAP BW Service SAPI, which is used for internal and ‘BW to BW’ data mart extraction, is
    upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the
    upgrade to avoid any possibility of data loss.
    upgrade preparation and postupgrade checklist
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
    /message/3221895#3221895
    OSS notes 328181 and 762951 as a prerequisites.
    Failure to follow the instructions in those notes may probably result in data loss.
    https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002662832005E
    /thread/804820
    Effect on BW of R/3 Upgrade   
    How To Tackle Upgrades to SAP ERP 6.0
    /people/community.user/blog/2008/03/20/how-to-tackle-upgrades-to-sap-erp-60
    Start with the Why — Not the How — When You Upgrade to SAP ERP 6.0
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/008dddd1-8775-2a10-ce97-f90b2ded0280
    Rapid SAP NetWeaver 7.0 BI Technical Upgrade
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0c9c8be-346f-2a10-2081-cd99177c1fb9
     https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c2b3a272-0b01-0010-b484-8fc7c068975e
    Hope this helps.
    Thanks,
    JituK

  • Import Basis Support Package 7.00 error

    Hi All,
    I wanted to apply Basis support package 9 for release 7.00 for our solution manager 4.0 system.
    When i started, it gave an error in the phase ADDON_CONFLICT? stage.. The message is as below:
    Phase ADDON_CONFLICTS_?: Explanation of Errors
    Conflicts were found between the Support Packages that you want to
    import and the Add-Ons installed in the system. To guarantee the
    consistency of your system, the import is interrupted until all Conflict
    Resolution Transports (CRTs) for the listed Support Packages are
    included in the queue.
    To include the CRTs in the queue, proceed as follows:
    - Write down the Support Packages and Add-Ons that have conflicts.
    - Leave this screen by choosing 'Cancel' (F12).
    - Load the CRTs for the Support Packages with conflicts from the SAP
      Service Marketplace or request them from your Add-On supplier.
    - Define the extended queue again in the Support Package Manager.
    - Import the queue. The Support Package Manager executes all steps from
      the beginning.
    If the problem involves an SAP Add-On, see SAP Note 53902, which tells
    you which CRTs resolve the conflicts. Otherwise contact the supplier of
    your Add-On for details on how to proceed.
    The following contains a table of Support Packages for each Add-On for
    which conflicts were detected. The column 'Information on the Conflict
    Resolution' specifies how you can resolve a conflict. For more
    information, select the corresponding 'Information for the Conflict
    Resolution'.
    Conflicts Between Add-On ST 400 and Support Packages
    Software Component   Release      Support Package        Information on
                                                             Conflict Resolution
    SAP_BASIS            700          SAPKB70009             Include CRT
    Can anyone guide me how to proceed.
    Thanks,
    Sailesh K

    Hi Shailesh,
    You are employing one or more Add-Ons in your system, apply patches regularly and want to know how the consistency of your Add-Ons is guaranteed. The list of Add-Ons installed in your system is stored in table AVERS.
    During patch application the SAP Patch Manager (SPAM) checks for conflicts between patches in the queue and the installed Add-Ons. A conflict occurs if an object delivered in a patch is also delivered in an Add-On. If conflicts are detected, SPAM stops processing at step ADDON_CONFLICTS_? and asks the user to load the corresponding CRTs into his system. The attributes of such CRTs match the Add-On id, Add-On release and patch predecessor (i.e. the patch in conflict).
    The patch application can only resume if all CRTs are selected in the patch queue. To resolve a conflict SPAM does not check if the conflicting object is contained in a CRT. It suffices that the corresponding CRT has been selected in the patch queue. All conflicts raised by its patch predecessor(s) are then resolved in one go.
    CRTs were introduced to protect the consistency of Add-Ons during the application of patches, such as Hot Packages and Legal Change Patches (LCP). There are two types of CRTs:
    1. Conflict Resolution Transports (CRT)
    A CRT resolves conflicts between one patch and one version of an Add-On including all previous versions. Example:
    Consider a system where Add-On IS-X is installed. During the application of patches P1 and P2 SPAM detected conflicts between the patches and the Add-On.
    To resolve these conflicts two separate CRTs are required, CRT1 and CRT2. A consistent patch queue looks like this:
        P1
        CRT1
        P2
        CRT2
    SPAM will only let you resume the patch application if you redefine the patch queue containing all four patches. You can see the name of the patch for which a CRT resolves a conflict in the "Predecessor" field in the patch queue dialog.
    2. Collective Conflict Resolution Transports (CCRT) are similar to CRTs but resolve conflicts between several patches and an Add-On. Example:
    Consider the previous example but this time the conflicts between patches P1, P2 and Add-On IS-X are resolved not by two CRTs but by one Collective CRT (CCRT) CCRT1. A consistent patch queue looks like this:
    P1
    P2
    CCRT1
    SPAM will only let you resume the patch application if you redefine the patch queue containing all three patches. The CCRT is added at the end of its highest predecessor, here P2. You can see the highest predecessor for a CCRT in field "Valid to patch#" when you scroll the patch queue dialog to the right.
    Keep in mind that a CCRT describes a range of patches for which conflicts are resolved, with the lower limit being the predecessor and higher limit the highest predecessor.
    Cheers,
    Shyam

  • Basis Support package level of ECC 6.0

    Dear All,
    I use SAP Version ECC 6.0 (700 Kernel, 64bit) Database SQL.
    My question is what should be the support package level of ECC 6.0? SAP recommends for the latest support package level always. But, whether the latest support package level will be stable?
    We are in the blue print stage now, I haven't received any requirement from the fuctionals for the support package upgrade.
    We have modules like, SD, MM, FI, FICO, HR, PS and CS.
    Anyone worked with these modules who can provide me, the particular components related to these modules with the stable support pack level.
    Thanks in Advance,
    Abu Sandeep

    Hi,
    Yes, for a new installation always go for the last support packages.
    After going live, NEVER, NEVER apply support packages without  qualifying them for YOUR company in a test system. It takes a lot of time to do non regression tests but it is mandatory IMHO.
    Regards,
    Olivier

  • When I go into full screen mode in Safari 5.1 on LION it switches to a new Space, making my other displays useless. Anyone else annoyed that Apple has completely left out those with multiple displays?

    I had a fear that this was going to be the case, but you can't have two full screen apps open in two different displays. At least that's how Safari fullscreen works. When switching over to full screen mode in safari, it automatically creats a new space, turns on four finger gesture to swipe through full screen apps which I had turned off in place of App Switcher.
    I don't use spaces because of the lack of support for using spaces with multiple displays. I would use spaces and mission control if I had control of each display's mission control separately.
    The fix would be to unlink the displays so they can scroll through full screen apps by themselves. I want this feature so I can mix and match the full screen apps on my three different displays. I see this beneficial for more people with multiple displays. in the future when thunderbolt display links, people will want better support too.
    I know I would use spaces and mission control more if I could have this ability. I'd be interested to know people's opinion.

    No no, if you read what I said, it would be that each individual display would be customizable to the user. The way you have it, it sounds like your second display will be dedicated to scrolling through fullscreen apps not allowing you to do it on the home screen. This is silly because with my concept, you could do that, by dragging apps to fullscreen in your second display, but if you want you could tell another display to scroll through fullscreen apps (independently) if you wanted. Each display will have it's own mission control with it's own set of desktops. I also can see how some people would still want them linked together, so this could just be a little check box made in mission control prefs to "link" or "unlink" desktops with link checked by default.
    With your solution you're limited to your setup. but what if the person has three or four displays? Well then your solution would limit them to one dedicated display that scrolls through fullscreen apps where mine lets a person customize their desktops depending on their preference and setup.
    further example: if you have safari, address book and mail in one display, you could still have ichat, PS and Illustrator in your second, and a text editor, FTP Client and iTunes in your third. Then you would mix and match these apps but it would promote the use of mulitple displays as well as benefit people with three or more, which thunderbolt, Cinema Display and Pro computers support.

  • RSPOR_SETUP  = Different ABAP and Java support packages.

    Hi all,
    We have an ECC 6.0 system with abap+java stacks. When we run the RSPOR_SETUP report we get this error:
    Different ABAP and Java support packages. Combination of support packages invalid
    And with some more clicking we find this:
    6. Compare version information of Java support package (com.sap.ip.bi classes) with ABAP support package (SAP BI)
       ABAP Support Package:                  13
       Java Support Package:                   0
    On the Java stack we see (among others) these components:
    sap.com        BI-IBC        7.00 SP12 (1000.7.00.12.0.20070509050058)
    sap.com        BI_MMR        7.00 SP12 (1000.7.00.12.0.20070507084106)
    sap.com        BI_UDI        7.00 SP12 (1000.7.00.12.0.20070507084125)
    sap.com        BI-BASE-S        7.00 SP12 (1000.7.00.12.11.20080324092518)
    sap.com        BI-WDALV        7.00 SP12 (1000.7.00.12.1.20071105133039)
    sap.com        BI-REPPLAN        7.00 SP12 (1000.7.00.12.3.20080104101916)
    So I believe all components are correctly installed.
    What are we doing wrong?

    Hello.
    Please be aware, that report RSPOR_SETUP should NOT be used with a Netweaver 04s system. This report has been replaced by the support desk tool. I request you to run the support desk tool as per note 937697 to check if there are any configuration issues in your system.You can resolve any red traffic lights that might be reported by the tool by following the corresponding actions suggested.
    I hope I can be helpful.
    Thanks,
    Walter Oliveira.

  • Support Package pre-requistis accross different landscapes

    I am struggling with which landscape but be patched before another since adding PI 711 into the mix.
    I am supporting ECC6 EHP4 with NW701, BI 70 at Netweaver 70, Solution Manager 70 Ehp1 and now PI 71 ehp1.
    I have been told PI must lead all other landscapes support package level but with it being at a later version of Netweaver than all other landscapes it is a far comparison or does it already lead them?
    My immediate need is to begin planning for a support package project on the ECC6 EHP4 landscape in the fall.  Since this landscape was last patch, about one year ago we add the PI landscape.
    It is a pretty safe bet I will be struggling with this same question in about 6 months when I start looking at a BI support package project.
    Any help that could be provided on this would be most appriciated.
    Bill

    I think we need to understand more why you feel certain systems need to be patched first or in a certain order
    - from what you say there must be technical concerns across more than one product area
    Perhaps it could be that --->
    Generally systems that interact with one another should be on the same BASIS level and SP stack - the general rule of thumb
    Products such as SLD definately have to be on systems with equivalent or higher BASIS version and SP stack than systems
    they interact with because the content created for a Netweaver 700 SLD
    may not be able to cope data supplier information from a Netweaver EHP1 system (this also raise other concerns regarding
    exporting data between SLDs - again equivalency - or higher for target system is recommended, sometimes with SLD lower BASIS version source systems may have limited export options as well)
    Products such a Solution Manager also as a rule of thumb have to be on equivalent or higher BASIS version or SP levels
    than the systems they interact with
    But PI also may have similiar concerns because they manage communication between systems e.g business systems
    However lets take say Payroll in ECC without any ESS or Legacy Systems, ALE
    - totally standalone payroll system - the only rules that apply there are that it works, has the latest fixes and required legal changes and follows a recommended stack - no BASIS equivalency level between other systems may exist in order for payroll to carry out its purpose
    Does this help clarify further ?
    Best wishes
    Stuart

  • Support Pack upgrade issue: Request deletion dose not work on CUBE

    Hi Gurus,
    We recently had a support package upgrade from SAPBW701 SP6 to SAPBW702 SP7.
    We have an Info package request stuck in yellow state for DSO Load in HR Data.
    We manually made it red and are trying to delete it manually/by creating a variant for Delete target contents in the process chain. It is not getting deleted.
    Rather if we use the Delete target contents variant previously created before the support package upgrade, it works fine.
    Please help me if any one can suggest any SAP NOTE or some other solution if possible.
    Thanks in advance,
    Sourabh Deo

    Hi,
    i think you have made it to red in request tab and tried deleting. Actually , you have to make the QM status red in Dataload monitor by  double clicking the TOTAl technical status.
    After the above activity, then try deleting.
    I don't think its a Service Pack problem.
    Regards,
    Suman

  • Unable to Login & Ececute any transaction after Applying Support Package

    Dear all,
    After applying SAP_BASIS Packs (SAPKB700..) support pack from level 15 to 18,  the it got cancelled and when i try to execute any transaction i am receiving ABAP dump "syntax_error".
    When i try to login i m getting the following msg. " Syntax error in program "SAPLSDOC ""..
    SAME MESSAGE IS POSTED IN 2007 BUT NO ANSWER
    Unable to login after applying patches
    could you help me to resolve this problem?
    Thanks and regards.
    Subbu

    Hi,
    Is Support Package upgrade failed in IMPORT_PROPER step ? then plesae refer
    support pack SAPKB70014 stuck at import _proper! Very urgent.
    http://www.sapfans.com/forums/viewtopic.php?f=12&t=309661&p=954180
    We also faced same issue in Solution manager and issue solved by running to r3i commad
    tp r3i <SP_name> <SID> pf=<transport profile> -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= tag=SPAM
    eg:
    D:\usr\sap\trans\bin>tp R3I SAPKB70014  SID pf=TP_DOMAIN_SID.PFL
    -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= tag=SPAM
    Note: Before executing above command please contact SAP (OSS message)
    Thanks,
    Preethish

Maybe you are looking for