Custom ItemTypes in Universal Worklist

Hi Comunity,
I have created two views in the Universal Worklist configuration that work just fine. Now I want to have certain items to only show up in one of those views. Therefore I have set the supported itemtypes parameter to the itemtype I want to show up in this view. Unfortunatelly the item type is none of the standard types. I have added one level of hirarchy by adding staff to the standard uwl.task.webflow item type. I have also tried to add an item type uw.task.webflow.staff into the file but this does not work either, there is no item showing up in my UWL.
Please have a look at the xml, I have inserted some snippets.
Any hint is welcome.
Regards Nicolas
Edited by: Nicolas Löwe on Oct 8, 2009 11:59 AM

Hi I found the solution myself.
I have done the configuration correctly. But the new Item Types do only appear when there are no other items in the cache.
Cheers Nicolas

Similar Messages

  • Show Custom Attributes of GP Tasks in the Universal Worklist

    Hello,
    I have created a GP Process and i can see and execute its task in the universal worklist.
    But it only shows standart propertys like : Process,From, Sent, Due, Status.
    I want to add Custom specific task propertys, but i couldn`t find the way. Reading javadoc documentation :
    [https://help.sap.com/javadocs/NW04S/current/uw/com/sap/netweaver/bc/uwl/doc-files/uwldtd.html#ItemType|https://help.sap.com/javadocs/NW04S/current/uw/com/sap/netweaver/bc/uwl/doc-files/uwldtd.html#ItemType]
    It says de we only can retrieve custom propertys from this connectors:
    ABAP_BOR - for SAP Business Object Repository
    WEBFLOW_CONTAINER - for Business Workflow container
    UM - for Portal user attributes from user management
    ALERT_CONTAINER - for alert container 
    GP_Connector is not in the list.... this means that it won`t be possible to show specific task attributes in the UWL if the tasks belong to a Guided Procedure Process?
    Thanks in advance!
    Marco.

    Hello Chittya,
    As I explained, my problem is not showing the GP tasks in the UWL ( in fact i have created a GP connector, and my GP tasks are correctly shown in my UWL ). The problem is that i can´t manage to show custom properties of this GP tasks in the universal worklist.
    Regards.
    Marco.

  • Customizing of Universal Worklist (UWL) Preview

    Hello,
    i have to customize the UWL preview, that is shown in the portal for every work item below the list view.
    The customization shall be done only for the current project, so there are only a few worksteps involved that should use the customized preview.
    I already read the UWV configuration documentation, but i hav absolutely no clue how i can do the customization if it is possible at all.
    What i have to achieve:
    - remove Buttons from the workitem preview (e.g. forward)
    - remove attributes from the workitem preview (e.g. priority)
    - the configuration shall only be done for specific work items because other projects want to see the preview.
    Can you please help or point me to some documentation/ guide?

    have a look at these weblogs
    Customizing Default actions of items in UWL
    Customizing Default actions of items in UWL
    Launching WebDynpro from Universal Worklist
    Launching WebDynpro from Universal Worklist
    ALERTS
    Integrating Alerts into UWL - it's no problem!
    Integrating Alerts into UWL - it's no problem!
    Support for secondary methods in UWL!
    Support for secondary methods in UWL!
    Innovative ways to use alerts
    Innovative ways to use alerts
    Universal Worklist - when you only need a single tab
    Universal Worklist - when you only need a single tab
    Swathi
    Do offer points:-)

  • Universal Worklist items open in new window instead of existing frame

    After our recent upgrade we noticed that workitems in Universal Worklist open in new window instead of existing frame.  Do you know if there is a system or universal setting to make all the workitems open in existing frame?  I know we can change the settings for parameters launchInNewWindow and openInNewWindow to "no" in XML files to fix this.   However, my concern is that I would need to do this for each and every task we use.  (still doable but wondering if there is simpler solution)
    Example: 
        <ItemType name="uwl.task.webflow.TS12300097.SAP_R3_CUSTOM_DEV" connector="WebFlowConnector" defaultView="DefaultView" defaultAction="launchWebDynPro" executionMode="default">
          <ItemTypeCriteria systemId="SAP_R3_CUSTOM_DEV" externalType="TS12300097" connector="WebFlowConnector"/>
          <Actions>
            <Action name="launchWebDynPro" groupAction="" handler="SAPWebDynproLauncher" returnToDetailViewAllowed="yes" launchInNewWindow="yes" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
              <Properties>
                <Property name="WebDynproApplication" value="LeaveRequestApprover"/>
                <Property name="WebDynproDeployableObject" value="sap.com/ess~lea"/>
                <Property name="newWindowFeatures" value="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no"/>
                <Property name="openInNewWindow" value="yes"/>
                <Property name="display_order_priority" value="5"/>
              </Properties>
              <Descriptions default=""/>
            </Action>
          </Actions>
        </ItemType>

    We downloaded uwl.standard.xml from UWL admin.  Made a copy and renamed file.  Changed all "launchInNewWindow" from "yes" to "no".  Uploaded new file in UWL admin.  Re-registered systems, cleared cache.  Not sure what exact line changed the behavior but the workitems no longer open in new window.
    We are still experimenting with file in our sandbox environment.

  • Cannot open GP process task in universal worklist.

    Hi all,
        I cannot open GP process task in universal worklist.It says:"Could not retrieve process instance: contact your system administrator".But i can open the task in Runtime task.
    i configure the universal worklist by following this link:
    http://help.sap.com/saphelp_nw04s/helpdata/en/43/ef06a7860c7061e10000000a1553f6/frameset.htm
    I also create a simple GuidedProceduresConnector and doesn't change the xml file,but it doesn't work,either.
    our portal is SP11.
    Can anyone help me?
    Thank you~!
    Best regards
    delma

    Hello Delma,
    Check out SAP note  1104652.    It discusses some changes for the uwl configuration file.   I just did this on a local installation of CE and used the following XML for my GP actions.  I just uploaded a paper on this  - it should be on SDN within a couple of days and I can get you the link.  
    The trick is that the name of your GP alias in UWL administration must be included in the XML.  The note explains this and there is an example to download.  Also, in my example the iView for the portal content to start the GP had to be changed - but that could be due to my local installation.
    Check out this note and this XML and let me know if it helps.
    Best regards
    Ginger
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE UWLConfiguration PUBLIC '-//SAP//UWL1.0//EN' 'uwl_configuration.dtd'
      >
    <UWLConfiguration version="2.0">
      <ItemTypes>
        <!-- configuration node for local system gp portal,
         where SystemAliasfor_local_system_ is the alias of the local system -->
        <ItemType name="uwl.task.gp.GPSystem" connector="GuidedProceduresConnector" defaultView="uwlTaskGPView" defaultAction="launchGP" executionMode="default">
          <Actions>
            <Action name="launchGP" groupAction="no" handler="IViewLauncher" referenceBundle="launch_sap" returnToDetailViewAllowed="yes" launchInNewWindow="no"
    launchNewWindowName="GPWindow" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
              <Properties>
                <Property name="page" value="pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.caf.eu.gp.folders.gp/com.sap.caf.eu.gp.folders.pages/com.sap.caf.eu.gp.pages.procinstance2"/>
                <Property name="DynamicParameter" value="app.processId=${item.processID}&amp;app.taskId=${item.activityID}&amp;"/>
                <Property name="System" value="SAP_LocalSystem"/>
              </Properties>
            </Action>
          </Actions>
        </ItemType>  
      </ItemTypes>
      <Views>
        <View name="uwlTaskGPView" selectionMode="SINGLESELECT" width="98%" supportedItemTypes="uwl.task.gp.GPSystem" columnOrder="subject, process, creatorId, createdDate, dueDate, status" sortby="dueDate:ascend, createdDate:descend" tableDesign="STANDARD" visibleRowCount="10" headerVisible="no" queryRange="undefined" tableNavigationFooterVisible="yes" tableNavigationType="CUSTOMNAV" actionRef="" refresh="300" dueDateSevere="86400000" dueDateWarning="259200000" emphasizedItems="new" displayOnlyDefinedAttributes="yes" dynamicCreationAllowed="yes" actionPosition="bottom">
          <Descriptions default="Guided Procedures">
            <ShortDescriptions>
              <Description Language="de" Description="Guided Procedures"/>
              <Description Language="en" Description="Guided Procedures"/>
            </ShortDescriptions>
          </Descriptions>
          <DisplayAttributes>
            <DisplayAttribute name="phase" type="string" width="" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
              <Descriptions default="Phase">
                <ShortDescriptions>
                  <Description Language="de" Description="Phase"/>
                  <Description Language="en" Description="Phase"/>
                </ShortDescriptions>
              </Descriptions>
            </DisplayAttribute>
            <DisplayAttribute name="process" type="string" width="" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
              <Descriptions default="Process">
                <ShortDescriptions>
                  <Description Language="de" Description="Process"/>
                  <Description Language="en" Description="Process"/>
                </ShortDescriptions>
              </Descriptions>
            </DisplayAttribute>
          </DisplayAttributes>
        </View>
      </Views>
    </UWLConfiguration>

  • Workitem not getting accessed in universal worklist

    Hi all
    i have configured a customized workflow and its working nice in GUI,now the problem is that when a workitem is send to the person ,it is getting displayed in the person's universal worklist but it can not be accessed
    like in SWEFVISU i have maintained both the task and object' visual parameters settings
    like
    task ---the task id used in workflow
    visualization parameter for task--
    object
    object's visualisation parameters
    i mean these 4 settings are there
    from my understanding i have set every entry but its not working
    can any one please advise what settings i have to maintain pertaining to SWEFVISU
    so that i can access my workitem in the persons universal worklist
    any help will be highly appreciated
    best regards
    ashish

    done

  • SAP Press book on Universal Worklist

    Hi all,
    I have just started writing a book for SAP Press on the Universal Worklist, to pass along some of what I have learned when working with the portal these past 5 years or so (anyone else remember EP 4.5?)
    I've put up a blog entry at
    <a href="http://www.fortybeans.com/">http://www.fortybeans.com/</a> and if you click the <a href="http://fortybeans.wishconsultants.co.uk/item/2007/2/6/universal-worklist-book-for-sap-press">Read more</a> link you can see the proposed chapters and sections I will be writing.
    I'd really appreciate any feedback any of you can give me - I want to make this the best possible book of its kind, and the only way to do that is to find out what people want from the book and then to give it to them. Maybe this could be the first book from SAP Press with "Powered by SDN" on the cover?
    Let me know what you think,
    Darren

    First off....EP4.5?....yep...when it was a Top Tier product. I was working on Workplace 3.0 (bootcamp) at the time....one week later, SAP and Top Tier announce the joint formation of the company "SAP Enterprise Portals" with their flagship product EP 5.0. Ahhh those were the days. I really want to meet the person who came up with calling it "portal-S" because I spent countless time explaining why the product was "Enterprise Portal" and not "Enterprise Portals". That was only compounded once SAP bought Top Tier outright, brought EP5.0 back into SAP proper and folded the "SAP Enterprise Portals" company. Ugg....anyways...
    The book sounds great. I too have fought in the trenches and wrestled with the UWL. It is great when it is used strictly as intended and with the limitations it might have. Past that....let the fun begin!
    I read your rough outline. Some chapters/content I would really like to see....
    - some basic coverage on Workflow (what it is, how it works, etc).
    - some explaination of "webflow", how it got started and where it is today
    - how workflow correlates to what the user sees in the UWL
    - limitations of the UWL based on support package level ( this is a big one!!! trying to use attachments now...nope...can't until the next SP level unless we backport our own custom webdynpro...that's not fun to find out 2 months in! haha)
    - really good examples of customizing items to launch one way in the portal versus another way within the backend inbox (ie. uwl xml config vs. config in the backend) and show ways to launch various SAP apps (dialog in SAP GUI, ITS service, webdynpro, etc). from UWL items.
    - same as above but show how to launch NON-SAP apps (we have a situation now where we have a UWL item that launches a Flex application and passes an order number to it)
    - similar to the above two, what's possible to pass across from the UWL to whatever through the portal (like UWL to an iView and on to the underlying application)...figuring out how "DynamicParameters" works is new to lots of people who might not have web dev background and/or understand the construction/structure of a URL query string
    - some information along the lines of "UWL launched an item/action out to some app, but how does the workflow status get updated to that fact?" ie. what makes the round trip complete?
    - a really good BIG, real world example showing multi-system (CRM-to-ECC-to-APO-to-SRM-to- etc) workflow and how the UWL makes it all much easier and fluid (in theory...haha)
    That's just a few off the top of my head that seem to always be sooo much fun with the UWL.
    Good luck on the book! Looking forward to it already!

  • Launching WebDynpro from Universal Worklist

    Hello All,
        am trying to launch a Web Dynpro Application from the UWL but was not able to open the application.
    We are following the Launching WebDynpro from Universal Worklist blog. But we are not able to open. Can any one help on this?
    Thanks
    Gopal

    Hi ,
    check the defaultAction assigned to launchWebdynpro or not?
    <ItemType name="uwl.task.webflow.TS91000129.UWL" connector="WebFlowConnector"
    defaultView="Test" executionMode="default" defaultAction="launchWebdynpro">
    after modifying did you upload with previous name of xml file? If you give different name to xml file , set highest priority such that uwl will consider this xml file
    Koti Reddy

  • Universal Worklist Configuration

    Hey guys
    Please can someone tell me where I can find a universal wordlist config guide for EP7.0?
    Many thanks in advance
    Jo-lize

    Hi
    This are the steps need to be followed.please do give full points
    The Universal Worklist (UWL) gives users unified and centralized way to access their work and the relevant information in the Enterprise Portal. It collects tasks and notifications from multiple provider systems – SAP Business Workflow, Collaboration Task, Alert Framework and Knowledge Management Recent Notifications - in one list for one-stop access.
    Administration and configuration for the Universal Worklist (UWL) is described.
    General Prerequisites
    1.     As an administrator, you have full administration rights for the Portal and the required business workflow rights in back end system (reference roles such as SAP_BC_BMT_WFM_UWL_ADMIN and SAP_BC_UWL_ADMIN_USER). Refer to SAP note 941589.
    Summary
    Symptom
    UWL administrative and/or end users are not allowed to perform or look up business workflow functions or data in the backend system.
    Reason and Prerequisites
    Corresponding adminsitrative and end users in the backend systems are created from scratch and have zero initial authorization.
    These roles are provided as an option to enable UWL administrative and end user authorization to readily utitlize the APIs of the SAP Business Workflow and relevant basis components remotely.
    (Note: Usually these roles are not needed as backend user is already assigned with roles that have sufficient authorization.)
    Also refer to BWF note 938717 for the corresponding roles required by business workflow.
    SAP_BC_UWL_ADMIN_USER
    For UWL administrative user who mainly deals with business workflow system registration.
    SAP_BC_UWL_END_USER
    For UWL end user to carry out all business workflow actions currently supported in UWL.
    Solution
    The roles can only be imported with a support package
    Header Data
    Release Status:     Released for Customer
    Released on:     25.04.2006  04:57:52
    Priority:     Recommendations/additional info
    Category:     Advance development
    Primary Component:     EP-BC-UWL Universal Worklist
    Releases
    SoftwareComponent     Release     FromRelease     ToRelease     AndsubsequentSAP_BASIS     60     640     640      SAP_BASIS     70     700     700     
    Highest Implemented Support Package
    SupportPackages     Release     PackageNameSAP_BASIS     640     SAPKB64017SAP_BASIS     640     SAPKB64019SAP_BASIS     700     SAPKB70008SAP_BASIS          
    Summary
    Symptom
    This note delivers two roles (PFCG) with the authorizations required to display and edit Business Workflow work items in the universal worklist.
    SAP_BC_BMT_WFM_UWL_ADMIN
    This role has the workflow authorizations required to perform the configuration for the Business Workflow connection in the universal worklist. These are authorizations for Business Workflow interfaces on the back-end system. The role does not have any authorizations for the portal or other interfaces used by the universal worklist.
    SAP_BC_BMT_WFM_UWL_END_USER
    This role has all workflow authorizations required by end users to be able to edit Business Workflow work items with the universal worklist. The role does not have any authorizations for the portal or other interfaces used by the universal worklist.
    You can either use the two roles directly or as templates for your own roles.
    Note 941589 contains more information about roles with authorizations for the universal worklist.
    Other terms
    Universal worklist
    Solution
    The roles can only be imported with the relevant Support Package.
    Header Data
    Release Status:     Released for Customer
    Released on:     20.04.2006  07:43:26
    Priority:     Recommendations/additional info
    Category:     Advance development
    Primary Component:     BC-BMT-WFM Business Workflow
    Secondary Components:     EP-BC-UWL Universal Worklist
    Releases
    SoftwareComponent     Release     FromRelease     ToRelease     AndsubsequentSAP_BASIS     60     640     640      SAP_BASIS     70     700     700     
    Highest Implemented Support Package
    SupportPackages     Release     PackageNameSAP_BASIS     640     SAPKB64017SAP_BASIS     700     SAPKB70008
    Related Notes
    941589 - UWL: administrative and end user roles
    Attributes
    1.     Make sure that each user is known to all connected SAP systems as per role requirement (make sure that there is one-to-one mapping between the portal user and the backend user)
    If an iView is based on a system object defined in your system landscape, you must assign user permission for the relevant user, group, or role to the system object, as well. User permissions assigned to a system permits the iView to retrieve data from the respective back end application through the system object at runtime.
    2.      Each connected SAP system for back end system (below release 7.0, WP-PI plug-in 6.0) has the connection to its respective SAP Internet Transaction Server (ITS)
    Authorizations needed for working with Business Workflow
    Normally, when the corresponding back end system user already has the correct authorization to work on the Business Workflow directly, no additional setup is required when working in UWL. However, manual configuration to assign RFC access authorization to the following function groups may be needed (Note: this is not common):
    1.     &#9679;      Function group and transaction SWK1 (for back end systems using WP-PI plug-in)
    2.     &#9679;      Function group SWN_UWL_WL (for back end system on release 6.40 and above, without the need of WP-PI plug-in)
    3.     &#9679;      Function group SWRC, SSCV (for all cases)
    4.     &#9679;      Authorization rights for SDTX
    User Mapping:
    1.      Navigate to User Administration ®&#61472;&#61513;identity Managementà User Mapping.
           2.      There are three scenarios:
    &#9675;     Portal user ID is different than the back end SAP user ID and back end SAP user IDs are different in all back end SAP systems connected to the portal (UIDPW)
    1.      Maintain the user mapping for each portal user corresponding to all the respective back end systems
    2.      Portal user ID is different than the back end SAP user ID and backend SAP user ids are the same in all back end SAP systems connected to the portal (logon ticket)
      Maintain the user mapping for each portal user to the reference system
    3.     Portal user ID is the same as the back end SAP user and back end SAP user IDs are the same in all back end SAP systems connected to the portal (logon ticket)
    1.       No user mapping is necessary
    User Permissions
    According to the prerequisites, if an iView is based on a system object defined in your system landscape, you must assign user permission for the relevant user, group, or role to the system object, as well.
    User permissions assigned to a system permits the iView to retrieve data from the respective back end application through the system object at runtime.
         Procedure
           1.      Navigate to System Administration  ® System Configuration  ® Portal Content. Open the folder where the existing systems were created.
           2.      From the available system list, click with the secondary mouse button on the system name and choose Open  ® Permissions.
           3.      Assign permissions. Make sure that under the Administrator column you assign Read permissions for the assigned role (for example for role eu_role). Also mark the check box End User.
           4.      Choose Save.
         Registering the Provider Systems
    Each UWL iView can retrieve work items from multiple Business Workflow back end systems. Register each back-end connection to be used with the following procedure:
    On the port...
           1.      On the portal, choose System Administration ® System Configuration ® Universal Worklist and Workflow ® Universal Worklist Administration.
    The Universal Worklist Systems list appears. Here you can define connectors and systems as item providers for the Universal Worklist.
           2.      To add a new entry, choose New. To edit existing information, select (highlight) the row and choose Edit.
           3.      To save the current system registration, choose Ok.
           4.      Multiple system connections are defined by repeating the above steps 1 to 3.
    Table describing the parameters
    Parameter     Description and Use
    Connector     This is the identifier with which the connector is registered. It indicates the type of items retrieved through the connection. For example: WebFlowConnector.For connector types WebFlowConnector or Alert Connector item types have to be registered with the UWL service after defining a new system connection.
    Configuration Groups     Leave this blank, when working with the default UWL iView. You can add a number of configuration groups separated by commas but only one configuration group per iView. first installed, one UWL iView is defined.  The System Configuration Group property for that iView is empty (blank). This means that no System Configuration Group is named, but in effect there is only a single group. The default behavior for the blank setting is this: when any user logs onto the UWL iView, UWL tries to log that user onto all registered back end systems. There is a limitation with the blank setting. When a large number of systems are accessed during log on, the overall portal load is increased. Also, the user receives error messages from those back end systems that have no user account for the particular UWL user. For large system landscapes do the following:...       1.      Partition back end systems into groups. This is accomplished by creating additional UWL iView instances, each of which refers to a specific group of backend systems. The group is defined, using the System Configuration Group iView property.       2.      Then use the value of the System Configuration Group property when registering back end systems by placing it in parameter Configuration Group, when you register the SAP system.
    System alias     The name of the alias for the back end system, as defined in the system landscape. The length cannot exceed 25 characters.If Web Dynpro applications are configured on a SAP NetWeaver Application Server which is different from the SAP NetWeaver Application Server of the system alias, then specify that system alias as a Web Dynpro system
    Web Dynpro Launch System     Enter the Web Dynpro system name if the SAP NetWeaver Application Server for the system is not the same as that running the Web Dynpro.Leave empty otherwise
    User Roles     Restricts who can get work items via the user role. For example, you can assign a portal role here, such as buyer. Only users with the role buyer will see items from the provider system in UWL.You can have multiple user roles separated by semi-colon. By specifying user roles for the portal users, it can be restricted as to who gets the work items in UWL.  For example, you can assign a portal role to a user, such as buyer.  Only users with the role buyer will see items from a system, for example, B7QCLNT000 in UWL.
    Pull Channel Delta Refresh Period (in Seconds)     Delta Pull mechanism of UWL enables new items to be fetched from the back end SAP systems every minute by default every 60 seconds, and every 30 seconds for alerts. However, this can be configured. The user does not need to use the refresh function to update the inbox. Once items are retrieved, timestamps are updated for the users whose items are successfully retrieved. These retrieved items are updated in the UWL cache. Setup necessary from Business Workflow to enable Delta Pull MechanismSome configuration settings are required if you use the UWL and the Extended Notifications for SAP Business Workflow. Define the following two batch jobs:...&#9679;      Background job (for example UWL_DELTA_PULL_1), consisting of a single step of ABAP report RSWNUWLSEL in FULL mode, using a report variant.Run the job once a day.1.     &#9679;      A background job (for example UWL_DELTA_PULL_2), consisting of a single step of ABAP report RSWNUWLSEL in DELTA mode (default mode is delta, so report variant is optional).Run the job every one to three minutes (depending on the performance of the back end SAP system).Setup necessary from UWL to enable Delta Pull Mechanism The UWL service user in portal, with user id uwl_service, has to be granted access to the corresponding back end systems. This is a predefined service user provided by UWL. When the back end system is configured in the UWL administration page, an automated process is triggered to create a corresponding UWL service user in the back end system.Check role assignments and profiles status of this automated generated UWL service user and perform user comparison if necessary.&#9679;      If SAPLogon ticket is used (without using user mapping), you first create the system entry. A message about uwl_service user appears. Then in the back-end system give the uwl_service user an initial password. Now edit the system entry.&#9679;      If user mapping is used, you can first configure the back end system in the UWL administration page. Then access the respective back end system to initialize the password for the user uwl_service. Then, do user mapping in the portal as usual for service user uwl_service.In case uwl_service fails to be created in the back end and does not exist, you can manually create a back end user with the id uwl_service and assign the role SAP_BC_UWL_SERVICE and the rights as other end users.ORMap uwl_service to an existing back end user. Make sure that there is no multiple user mapping (there must not be two portal users mapped to the same back end user). This back end user must have the role SAP_BC_UWL_SERVICE.
    Snapshot Refresh Period (in minutes)     All items at the current time are fetched from the backend (for example from the SAP Business Workflow). The cache is synchronized thereafter. New / modified / deleted / updated items are fetched every session (every log on) if you leave the field value empty or enter a negative number.To specify a particular time frame for which the refresh occurs, enter the number of minutes
    The above registration procedure is usually sufficient to use a UWL iView. Item type retrieval and registration requires a connection to the systems and may take a couple of minutes.
    For each system, they are generated as the configuration named uwl.webflow..
    In Manager Self-Service (MSS), the Universal Worklist groups together in Workset: Work
    Overview the various workflow tasks and alerts that are relevant for a manager.
    The standard MSS delivery includes the configuration file com.sap.pct.erp.mss.001.xml for the universal worklist.
    1. In the portal, choose System Administration →&#61472;System Configuration →&#61472;Universal
    Worklist and Workflow →&#61472;Universal Worklist →&#61472;UWL Systems Configuration.
    2. Create the following system connections:
    If you have already registered a suitable connector to the system connected to
    the system alias, the existing connector is sufficient and you do not have to
    register an additional one.
    &#9675; System alias: SAP_ECC_Financials
    Connection types:
    &#9632; WebFlowConnector
    &#9632; AlertConnector
    &#9675; System alias: SAP_ECC_HumanResources
    Connection type WebFlowConnector
    &#9675; System alias: SAP_SRM
    Connection type WebFlowConnector
    Leave the Web Dynpro Launch System field blank for all system connections.
    With regards
    subrato kundu

  • Create new attribute in the universal worklist

    hi,
    Anyone knows how to create new attribute in the universal worklist ?
    I try:
    in the UWL administration iview -->
    Click to Configure Item Types and Customize Views Using a Wizard-->
    Define custom attributes and customize the corresponding view-->
    here i choose an existing configuration(uwl.webflow.SAP_CRM)-->
    SAP_CRM-->
    add attribute-->
    and now in the window "personalize task" in the table
    Current display attributes appear my new attribute called "prof" > save>
    Select the systems that you want to search for the attributes--> SAP_CRM -->
    apply to systems.
    but this attribute not save..any idea??
    thank you.

    Hi,
    have you took a look at :
    http://help.sap.com/saphelp_nw04/helpdata/en/39/a1bb5c4c0d4ab4a417e87ef35f1efa/frameset.htm
    Fabien.

  • Java Web DynPro and Universal Worklist Interaction

    HI ESS/MSS Gurus,
    Good day!
    I am a workflow consultant who is working on an ESS/MSS project. I have already completed and tested (successfully) all of the workflows needed in the backend using the PTARQ and PTCOR applications. We are also successful in showing the work items in the universal worklist.
    Now the question is, whenever we click on the work item, we encounter an error in the portal. Now, I need to determine the following:
    1. How are we going to integrate the ESS/MSS portal with the execution of the work item in the universal worklist?
    2. Do we need to develop custom Java web dynpro applications for the approval process of the leaves, or is there a standard offering from the ESS/MSS packages?
    Your inputs are very much welcome.
    Regards,

    Hi Gurus,
    Here is what we have done so far:
    1. Implemented the details as indicated in note 779075 and changed the parameters defined in SWFVISU
    2. Upon re-registering and clearing the cache from the UWL, we tested if the task will call the standard application for leave request approval. It returns the error Internal error. :
    Item is null for action acknowledge, and for item type uwl
    It seems that the xmls files are not being generated or read successfully. although when we check uwl.webflow.SAP_ECC_HumanResources, there is an updated xml file for the task
    Questions are:
    1. What checks do we need to execute between the back end, UWL and portal?
    2. Whenever changes in SWFVISU are made, what items do we need to check to ensure that the changes are reflected in the UWL? I have read that SWFVISU helps the user do away with the tedious xml creation. How can we verify that the changes are implemented/updated in the xmls generated?
    3. Any other items we need to look into?
    Regards,

  • Launch URL/BSP from attachments link in workitem in Universal Worklist

    Background info:
    We have a custom business object.  Default method on object in SWO1 is a custom display method.  This display method returns a URL to a BSP.  
    When I open my workitem in SBWP and click the attachments link, it properly launches the URL which opens the BSP.
    However, when I open same workitem in Universal worklist and click the attachments link, it does not properly open the BSP.  It looks like it's trying to open a SAP GUI version of the object but nothing is displayed.  When our developer puts a breakpoint in the ABAP code and we click the workitem link in UWL, the URL/BSP opens fine.   So, UWL config must be doing something extra (added code?  redirect?) that clobbers the URL/BSP launch.   Anyone have any ideas/suggestions?
    Thanks,
    Matt
    *Reminder, We are not trying to launch the BSP when you click the workitem link in the UWL list.  This is the attachments link inside the workitem itself.

    G'Day Matthew,
    The reason this works from SBWP and not from UWL is because you have an ABAP session in between. You don't mention the type of attachment, but usually what gets executed is the default method of the object. Thus the UWL has to initiate an ITS/WebGUI session to execute the default object method - this method may contain code to launch a BSP but it still needs to get to the code to start with.
    You need to find alternatives, see if Karri's suggestion does what you're after.
    Cheers,
    Mike

  • Customising Universal Worklist

    Hello All,
    I am attempting to customize the Universal Worklist for MSS.  There are various buttons such as 'Launch Web Dynpro' , 'Resubmit', 'Forward' and 'Assign to me' that appears for the manager when authorizing a leave request.
    Any Ideas on how I remove these buttons?
    Many Thanks,
    Nick

    hi,
    If you want to customise the UWL then, first you have to make a copy of the UWL iviews from Content Administration >Portal Content > Content Provided by SAP >End User Content >
    Standard Portal Users >iViews > Universal Worklist.
    From there you have select the iviews, copy it to your own folder , say 'Custom'. Apply the changes over there. Now Create an workset, set the entry points of the ivews and workset to true. Now create a role. Assign the workset to the role. Add the role to the user. Hence you can personalise your universal worklist.The below given link will explain all in detail:
    [http://help.sap.com/saphelp_nw70/helpdata/en/57/c223be82104792a15c2df11377b9ed/frameset.htm]
    However to customise, you have to make the changes in the folder Content Provided by SAP itself, and then apply it. However this is not desired, since all the users added to the Enduser and Standard user role will be affected. For further information look into the file:
    [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/904ca240-63bc-2a10-1c98-de81b6a045bf]

  • Custom Filter in Universe on top of BEX Query is not working in BO Explorer?

    Hi,
    I have created Condition(Filter) for an Dimension Object "Submitted by Group Hierarchy" in Universe designer tool on top of SAP BEx Query and then exported the universe to Repository.
    <FILTER KEY="@Select(Submitted By Group Hierarchy\L01 Submitted By Group Hierarchy).[TECH_NAME]"><CONDITION OPERATORCONDITION="InList"><CONSTANT CAPTION="@Prompt('Submitted By Group ','A',' Submitted By Group Hierarchy\L01 Submitted By Group Hierarchy',multi,primary_key,,{‘Direct Sales’)"/></CONDITION></FILTER>
    To test my custom filter , I have created WEBI report and its allowing input entry in my custom filter and output is also coming .
    where as in Explorer, i am not able to enter input values for my custom filter as below.
    Can anyone suggest me how to create custom filter in universe and use it in explorer.
    Thanks in advance.
    Regards,
    Ramana.

    Hi Ramana,
    Please try using 'mono' in place of multi in @prompt syntax and then test.
    Regards,
    Pranay Sharma

  • Runtime error in Universal Worklist in portal

    Hi!
    An error occurs when I open the page Universal Worklist -
    Administration under System Administration > System Configuration >
    Universal Worklist & Workflow. The error message is:
    Portal runtime error.
    An exception occurred while processing your request. Send the exception
    ID to your portal administrator.
    Exception ID: 09:44_02/10/08_0004_221082950
    Refer to the log file for details about this exception.
    This error is also displayed when opening the page Portal Eventing,
    Portal Navigation under System Administration > Support > Web Dynpro
    Test Tools > Application Integrator Tests.
    The portal UME is configured with ADS as data source and we are using
    the dataSourceConfiguration_ads_readonly_db_with_krb5.xml configuration
    file. Single Sign-On using SAP logon tickets with user mapping to
    reference system is also implemented.
    Users have different users IDs in the SAP System than in the portal,
    and scenario 2 from SAP Help "Single Sign-On to SAP Systems"
    (http://help.sap.com/saphelp_nw04/helpdata/en/4d/dd9b9ce80311d5995500508b6b8b11/frameset.htm) is implemented
    "Scenario 2: Single Sign-On using SAP logon tickets with user mapping."
    The problem occurred after changing the UME with ADS and implemented
    Single Sign-on.
    Error messages from log:
    Date : 10/03/2008
    Time : 10:08:56:057
    Message : Content pass of Application Integrator failed.
    Component Name:       com.sap.portal.appintegrator.sap.WebDynpro,
    Context Name (iView): pcd:portal_content/every_user/general/uwl/com.sap.netweaver.bc.uwl.uwlSapWebDynproLaunch,
    Top Layer:            WebDynpro/TopLayer,
    Producer ID (FPN):    null,
    System Alias:         SAP_LocalSystem,
    [EXCEPTION]
    com.sapportals.portal.appintegrator.ApplicationIntegratorException: ApplicationIntegratorException
         at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:104)
         at com.sapportals.portal.appintegrator.accessor.system.SAP_LocalSystemAccessor.getAuthenticationData(SAP_LocalSystemAccessor.java:91)
         at com.sapportals.portal.appintegrator.layer.authenticationmethod.AbstractAuthenticationMethod.getUserCredentials(AbstractAuthenticationMethod.java:54)
         at com.sapportals.portal.appintegrator.layer.authenticationmethod.SAPLogonTicket.computeAuthentication(SAPLogonTicket.java:31)
         at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:45)
         at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:159)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
         at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
         at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
         at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.security.api.umap.NoLogonDataAvailableException: (No text available)
         at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:329)
         at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:99)
         ... 33 more
    Severity : Error
    Category : /System/Server
    Location : com.sap.portal.sapapplication
    Application : sap.com/irj
    Thread : SAPEngine_Application_Thread[impl:3]_18
    Datasource : 1223021485930:N:\usr\sap\DPN\JC32\j2ee\cluster\server0\log\defaultTrace.trc
    Message ID : 00145ED7E6460061000007830000B6B800045854D84A3E79
    Source Name : com.sap.portal.sapapplication
    Argument Objs : com.sapportals.portal.appintegrator.ApplicationIntegratorException: ApplicationIntegratorException
         at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:104)
         at com.sapportals.portal.appintegrator.accessor.system.SAP_LocalSystemAccessor.getAuthenticationData(SAP_LocalSystemAccessor.java:91)
         at com.sapportals.portal.appintegrator.layer.authenticationmethod.AbstractAuthenticationMethod.getUserCredentials(AbstractAuthenticationMethod.java:54)
         at com.sapportals.portal.appintegrator.layer.authenticationmethod.SAPLogonTicket.computeAuthentication(SAPLogonTicket.java:31)
         at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:45)
         at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:159)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
         at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
         at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
         at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.security.api.umap.NoLogonDataAvailableException: (No text available)
         at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:329)
         at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:99)
         ... 33 more
    Arguments : com.sapportals.portal.appintegrator.ApplicationIntegratorException: ApplicationIntegratorException
         at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:104)
         at com.sapportals.portal.appintegrator.accessor.system.SAP_LocalSystemAccessor.getAuthenticationData(SAP_LocalSystemAccessor.java:91)
         at com.sapportals.portal.appintegrator.layer.authenticationmethod.AbstractAuthenticationMethod.getUserCredentials(AbstractAuthenticationMethod.java:54)
         at com.sapportals.portal.appintegrator.layer.authenticationmethod.SAPLogonTicket.computeAuthentication(SAPLogonTicket.java:31)
         at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:45)
         at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:159)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
         at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
         at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
         at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.security.api.umap.NoLogonDataAvailableException: (No text available)
         at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:329)
         at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:99)
         ... 33 more
    Dsr Component : n/a
    Dsr Transaction : f52708e0912011ddb1e200145ed7e646
    Dsr User :
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 1
    Relatives : /System/Server
    Resource Bundlename :
    Session : 32121
    Source : com.sap.portal.sapapplication
    ThreadObject : SAPEngine_Application_Thread[impl:3]_18
    Transaction :
    User : Asle.Gaarder
    Date : 10/03/2008
    Time : 10:08:56:026
    Message : Cannot provide backend user ID and password for user "Asle Gaarder" (unique ID: "USER.CORP_LDAP.asle.gaarder") for system "SAP_ECC_REFERENCE" because these credentials could not be found in the user mapping data.
    Severity : Info
    Category :
    Location : com.sap.security.core.umap.imp.UserMappingDataImp.enrich(Properties)
    Application : sap.com/irj
    Thread : SAPEngine_Application_Thread[impl:3]_18
    Datasource : 1223021485930:N:\usr\sap\DPN\JC32\j2ee\cluster\server0\log\defaultTrace.trc
    Message ID : 00145ED7E6460061000007820000B6B800045854D849CB92
    Source Name : com.sap.security.core.umap.imp.UserMappingDataImp
    Argument Objs : "Asle Gaarder" (unique ID: "USER.CORP_LDAP.asle.gaarder"),"SAP_ECC_REFERENCE",
    Arguments : "Asle Gaarder" (unique ID: "USER.CORP_LDAP.asle.gaarder"),"SAP_ECC_REFERENCE",
    Dsr Component : n/a
    Dsr Transaction : f52708e0912011ddb1e200145ed7e646
    Dsr User :
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 1
    Relatives :
    Resource Bundlename :
    Session : 32121
    Source : com.sap.security.core.umap.imp.UserMappingDataImp
    ThreadObject : SAPEngine_Application_Thread[impl:3]_18
    Transaction :
    User : Asle.Gaarder

    Hi,
    Check the logon type for systems SAP_LocalSystem and SAP_ECC_REFERENCE which must be set to SAPLOGONTICKET not UIDPWD.
    It basically fails since the password doesn't exist for the mapping, as it is only dependent on trust.
    There was a change in a recent SP which added an extra check in this area.
    Dagfinn

Maybe you are looking for

  • Drop ship

    Hi, I'm pretty sure there isn't an option for what I want to do, but I thought I'd ask just in case. Is there an option in Presort to only assign drop ship level to pallets and leave trays as local entry.  So, for instance, if I put BMC St Louis as a

  • EP 7 with ESS/MSS errors

    Hi Guys We are using EP 7 sp13 with ECC 6 (sp13 ) we currently have ESS/MSS sp11 on it. All the ESS links work except EMPLOYEE SEARCH> CHANGE OWN DATA. it gives me the following error. com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: fail

  • Hierarchy Authorizations in BW

    Hello all, Is there a way to restrict the access to create/modify hierarchies to a specific application (or Info)area? I see that giving RSA1 and S_RS_HIER with 03, 23 and 71 gives access to ALL InfoObjects. "Hierarchy Name" is after the fact, and G.

  • Whether Web Platform Installer 5.0 can be installed in production SharePoint 2010 mysites machine

    Dear all, I have sharepoint 2010 and VisualStudio 2010SP1 in my production machine. mysites is running in this box.  My doubt is; I am trying to open a project which was created in VS 2012 - which was saved to framework 4.0. When i am trying to open

  • Apple push notification service certificates

    I buy a server app to create my own network at my home business. the apple push notification service certificates have additional cost? I enter my pass but the app do not show me a price for a device. Normally all apple in-app upgrade show an alert.