Unable to release the higher level WBS

Hi,
at  my system am having a user status  'review' and 'release' at wbs level.
Unless i review and release the subordinate WBS, am unable to release the higher level WBS.
is there a possibility to directly review and release my higher level WBS which results all  its subordinate WBS reviewed and released automatically.
Regards
Ahmedkhan

while setting user status use the set and pass on function

Similar Messages

  • Error: Maintain settlement rule of the sender for a higher level WBS

    Hi,
    I dont want to maintain the settlement rule for a higher level WBS. How can i configure this in such a way that i dont get the following error:" Maintain settlement rule of the sender" while doing CJ88. Maintaing a separate Settlement profile for a higher level WBS is an option but we are looking if something else could be done The problem is that there are no actuals booked against, say, level 2 WBS but when i execute CJ88, i get the aforesaid error. How can i ensure that only the lowest level WBS ask for the settlement rule and not the levels above it. I have already removed the Investment profile from the higher level WBS but still getting the same error.
    Regards,
    DPil

    Hi,
    It is a type Capex WBS and Biling element is not checked. In fact i get a warning while doing the settlement: WBS is neither a billing element nor an account assignment element.
    Diagnosis
    WBS element  is not indicated as either an account assignment element or as a billing element in the master record.
    System Response
    The WBS element cannot be assigned to an account.
    Procedure
    Correct your entries or add the missing indicator to the master record for the WBS element.
    But this is just a warning. On pressing enter i get the error :Maintain settlement rule of the sender "

  • Settlement Run on Higher Level WBS

    Hello Experts,
    Scenarios is that I need to run settlement on 2nd Level WBSE where I have assigned asset class but my activities are linked on 3rd OR 4th Level WBS Elements due to the requirement of detailed level project planning. Cost is posted against lower level WBS Elements and settlement is to be run on higher level WBS Element.
    Can I roll up the cost from lower level WBS to Higher level WBS so that settlement can be run against the asset class assigned with higher level WBS Element
    Please advise. Thanking you in anticipation...
    Warm Regards

    Hi,
        You can perform this kind of settlement in two ways based on different conditions:
    1. If there is only one asset to be created from project, then instead of hierarchical settlement you can use the line item settlement to the same asset maintained in the settlement rule of superior WBS, by using settlement strategy as in customization as ( Settlement rule generation: account assignment category........4)  Copy rule from superior object. So that settlement of all the object will be done to the same asset.
    2. Otherwise, if you want to have the settlment to the same asset of your project structure in hierarchy, then you can use SAP note number 211324, to have Settlement rule generation: account assignment category as 05 (Superior WBS element), in the customization of settlement strategy.
    I hope this should help you.
    Regards
    Avisek Bhardwaj

  • Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of '

    When I deploy the cube which is sitting on my PC (local) the following 4 errors come up:
    Error 1 The datasource , 'AdventureWorksDW', contains an ImpersonationMode that that is not supported for processing operations.  0 0 
    Error 2 Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Adventure Works DW', Name of 'AdventureWorksDW'.  0 0 
    Error 3 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Customer', Name of 'Customer' was being processed.  0 0 
    Error 4 Errors in the OLAP storage engine: An error occurred while the 'Customer Alternate Key' attribute of the 'Customer' dimension from the 'Analysis Services Tutorial' database was being processed.  0 0 

    Sorry hit the wrong button there. That is not entire solution and setting it to default would work when using a single box and not in a distributed application solution. If you are creating the analysis database manually or using the wizard then you can
    set the impersonation to your heart content as long as the right permission has been set on the analysis server.
    In my case I was using MS Project Server 2010 to create the database in the OLAP configuration section. The situation is that the underlying build script has been configured to use the default setting which is the SQL Service account and this account does
    not have permission in Project Server I believe.
    Changing the account to match the Project service account allowed for a successful build \ creation of the database. My verdict is that this is a bug in Project Server because it needs to include the option to choose impersonation when creating the Database
    this way it will not use the default which led to my error in the first place. I do not think there is a one fix for all in relations to this problem it is an environment by environment issue and should be resolved as such. But the idea around fixing it is
    if you are using the SQL Analysis server service account as the account creating the database and cubes then default or service account is fine. If you are using a custom account then set that custom account in the impersonation details after you have granted
    it SQL analysis administrator role. You can remove that role after the DB is created and harden it by creating a role with administrative permissions.
    Hope this helps.

  • Errors in the high-level relational engine. The data source view does not contain a definition for the table or view. The Source property may not have been set.

    Hi All,
    I have a cube in which i'm using the TIME DIM that i created in the warehouse. But now i wanted a new measure in the cube which is Average over time and when i wanted to created the new measure i got a message that no time dim was defined, so i created a
    new time dimension in the SSAS using wizard. But when i tried to process the new time dimension i'm getting the follwoing error message
    "Errors in the high-level relational engine. The data source view does not contain a definition for "SSASTIMEDIM" the table or view. The Source property may not have been set."
    Can anyone please tell me why i cannot create a new measure average over the time using my time dimension? Also what am i doing wrong with the SSASTIMEDIM, that i'm getting the error.
    Thanks

    Hi PMunshi,
    According to your description, you get the above error when processing the time dimension. Right?
    In this scenario, since you have updated the DSV, it should have no problem on the table existence. One possibility is that table has been specified for tracking in the notifications for proactive caching, but isn't available any more for some
    reason. Please change the setting in Proactive Caching into "MOLAP".
    Reference:
    How To Implement Proactive Caching in SQL Server Analysis Services SSAS
    If you have any question, please feel free to ask.
    Best Regards,
    Simon Hou
    TechNet Community Support

  • Errors in the high-level relational engine on Schedule Refresh Correlation ID: 7b159044-c719-41f9-8d0f-da6f73576d6e

    Connections are all valid and work when I setup the Refresh but when the schedule refresh occurs I get this error:
    Errors in the high-level relational engine. The following exception occurred while the managed IDataReader interface was being used: The Data Transfer Service has encountered a fatal error when performing the data upload. The remote server returned
    an error: (400) Bad Request. The remote server returned an error: (400) Bad Request. Transfer client has encountered a fatal error when performing the data transfer. The remote server returned an error: (400) Bad Request. The remote server returned an error:
    (400) Bad Request.;transfer service job status is invalid Response status code does not indicate success: 400 (Bad Request).. The current operation was cancelled because another operation in the transaction failed.
    It is trying to refresh 3 simple tables with less than 9,000 rows each.
    Also, i'd like to add that the refresh works right from excel as well...
    Another fact just in, it seems to work on one out of 3 tables sometimes, so first table gets a success on the log, but sometimes it fails (It succeed twice and failed once with the above error).  The second table never succeeds and gets the error above. 
    The 3rd table never even gets attempted.
    Am I running into some sort of timeout perhaps?
    loading
    Failure
    Correlation ID:
    7b159044-c719-41f9-8d0f-da6f73576d6e
    04/01/2015
    at 01:50 AM
    04/01/2015
    at 01:53 AM
     00:03:14
      Power Query - Sendout_Records Not tried
      Power Query - Positions Errors in the high-level relational engine. The following exception occurred while the managed IDataReader interface was being used: The Data Transfer Service has encountered a fatal error when performing the data upload. The
    remote server returned an error: (400) Bad Request. The remote server returned an error: (400) Bad Request. Transfer client has encountered a fatal error when performing the data transfer. The remote server returned an error: (400) Bad Request. The remote
    server returned an error: (400) Bad Request.;transfer service job status is invalid Response status code does not indicate success: 400 (Bad Request).. The current operation was cancelled because another operation in the transaction failed. 
      Power Query - Position_Activities Success.

    This is not because of the number of rows, instead its the execution time. The query takes more than 7 mins to execute and seems this fails the refresh process.
    Thank You

  • Summing up the price of the sub items and put it in the Higher level item

    Dear Experts,
            I have got one requirement from my customer.
    The requirement is while creating the Sales order (in VA01), in the line item the customer will enter the Material, Quantity and Higher level item for the line item.In Condition Tab page price and Condition will be entered.
    My requirement is at the time of saving the sales order the price of the lower level items has to be summed up and this price has to be put in condition tab page of the higher level item.
    This is my requirement.Is it possible?if yes please explian me how to do this.
    If anybody not able to understand my question please reply back to me.
    Thanks & Regards,
    Ashok.

    Hi
    Here u need to find user exit that suits ur requirement like user exit that will trigger while saving that sale order and in that user exit u are able to access that tables where all the lower level item prices stored and condition table where price stored. Then u can do sum and update that sum into condition price table. So search for user exit that suits ur requirement.
    Regards,
    KP.

  • How to make Default the Higher-Level Manager of the employee

    Dear experts,
    how to make Default the Higher-Level Manager of the employee as Further Participant in performance management ?
    Regards,
    TVS

    Hi,
    The delivered BAdI below defaults in both the appraiser and appraisee as part-appraisers//Default Further Participants.
    BAdI Area: Appraisal Enhancements
    BAdI Definition: HRHAP00_DOC_DEF_DO (Appraisal - Default Further Participants)
    App. Enhn.: DEFAULT_ALL_MANAGERS     
    Implementation: HRTMC_DEF_OTHERS
    Implementation short text: Determine All Managers
    Implement this BADI  in SE18/SE19 and  write the desired code in the  BADI methods
    Hope this will help u out.....
    Regards
    Lakhan

  • Basic  XML Publisher Question: How to access tags in the higher levels?

    Hi All,
    We have a basic question in XML Publisher.
    We have a xml hierarchy like below:
    <CD_CATALOG>
    <CATALOG>
    <CAT_NAME> CATALOG 1</CAT_NAME>
    <CD>
    <TITLE>TITLE1 </TITLE>
    <ARTIST>ARTIST1 </ARTIST>
    </CD>
    <CD>
    <TITLE> TITLE2</TITLE>
    <ARTIST>ARTIST2 </ARTIST>
    </CD>
    </CATALOG>
    <CATALOG>
    <CAT_NAME> CATALOG 2</CAT_NAME>
    <CD>
    <TITLE>TITLE3 </TITLE>
    <ARTIST>ARTIST3 </ARTIST>
    </CD>
    <CD>
    <TITLE> TITLE4</TITLE>
    <ARTIST>ARTIST4 </ARTIST>
    </CD>
    </CATALOG>
    </CD_CATALOG>
    We need to create a report like below:
    CATALOG_NAME     CD_TITLE     CD_ARTISTCATALOG 1     TITLE1     ARTIST1
    CATALOG 1     TITLE2     ARTIST2
    CATALOG 2     TITLE3     ARTIST3
    CATALOG 2     TITLE4     ARTIST4
    So we have to loop at the level of <CD> using for-each CD. But when we are inside this loop, we cannot access the value of CAT_NAME which is at a higher level.
    How can we solve this?
    Right now, we are using the work-around of set_variable and get_Variable. We are setting the value of CAT_NAME inside an outer loop, and using it inside the inner loop using get_variable.
    Is this the proper way to do this or are there better ways to do this? We are running into troubles when the data is inside tables.

    you can use
    <?../CAT_NAME?>copy past to your template
    <?for-each:CD?> <?../CAT_NAME?> <?TITLE?> <?ARTIST?> <?end for-each?>

  • Unable to release the change request from se01

    HI All,
    Recently i had applied Rsecnotes as per sap recommendation in EWA Report and I implemented successfully in DEV System. But, When i try to release the change requests from SE01 in (DEV System)
    it is giving the error message "Object Func<objectname> is inactive". I have unlocked all the request and checked but still problem exsist.
    Please help me to release the request and implement in the landscape.
    Thanks,
    Rajesh N

    Hi,
    Activate the object using se03 and then relaese the request
    thanks

  • Unable to release the Check-in status of a checked-out item.

    Dear all,
    I am using Portal 10.1.2 and now facing a problem that someone "A" has the privilege to add file items on a page where an approval process ("X", "Y", "Z", only one must approve) is defined.
    "A" add a new file to the page. He did it as usual. Go to the page, add the new file and press OK.
    But, neither "X", "Y" nor "Z" can see the pending file item shown in the "My Approval Status Portlet".
    So, the uploaded file is now checked-out by A and no one can move it.
    Can anyone help me?
    thanks a lot.
    George (HK)
    My blog at http://hktour.blogspot.com

    Thnx - the hint with the "My Notification" portlet did the trick.
    I had a HTML Portlet, that always displayed "draft" - but every user already saw the new content (!?).
    After putting a "My Notification" portlet on an extra page - I could access the page with the HTML portlet in mode 25 (preview pendiing items) were I could submit the portlet into approval. Using the "My Notification" portlet again, I was also able to approve the portlet.
    Now all pages that included this portlet are cleaned again (no more displaying "darft" in the edit mode).
    Thanks a lot!

  • Sometimes GPIB controller did not command the instrument to talk while the high-level program did have "READ" command.

    GPIB controller should send "UNL", "LA0", "TAxx" to command the instrument to talk. Though the program do have the "READ?" query, sometimes GPIB controller didn't send the above commands from NI Spy, resulting in the system is hanging there. It happens randomly.

    HI,
    It is not clear to me what is going on. I'd like to get more information.
    Could you specify what programming language are you using?. Also, what functions are you using?. What driver version are you using?.
    Include any information you think might be helpful. Also, attach the Spy capture.
    DiegoF.

  • Not to cancel whole release with 1st level without cancel with higher level

    Hi
    In case of release of PR or PO I have maintained Release Prerequisite. So I can't release with 2nd level of release code without releasing with 1st level of release code. In case of cancelling release reverse should happen. i.e. I can't cancel release with 1st level of release code without cancelling with 2nd level of release code. But I am able to cancel the whole release with 1st level of release code irrespective of whether I have cancelled release with higher level of release codes or not.
    I want this not to happen.
    Any suggestion ? Is there any customizing seting to be maintained.
    Points assured.
    Regds
    Amitava

    Hi,
    My question is still unanswered. Can anybody give any idea? this is urgent.

  • What are the steps (High level) needed to implement US Payroll?

    Hi,
    What are the (high level) steps needed to implement US Payroll?
    Please provide any relavent URLs for any steps if possible.
    Thanks,
    Prabakar

    Transaction Code:-OH00
    Personnel Management Personnel AdministrationOrganizational Data Organizational Assignment Define employee attributes
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationOrganizational Data Organizational Assignment Define employee attributes
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationOrganizational Data Organizational Assignment Define employee attributes
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationOrganizational Data Organizational Assignment Create payroll area
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationOrganizational Data Organizational Assignment Create payroll area
    Transaction Code:-PE03
    Personnel Management Personnel AdministrationOrganizational Data Organizational Assignment Check Default Payroll Area
    Transaction Code:-PA03
    Personnel Management Personnel AdministrationOrganizational Data Organizational Assignment Create control record
    Transaction Code:-PA03
    Personnel Management Personnel AdministrationOrganizational Data Organizational Assignment Create control record
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataBasic PayDefine EE Sub Group Grourping for PCR and Collective Agreement Provision
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataBasic PayDefine Reason for Change
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataBasic PayCheck PayScale Type
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataBasic PayCheck PayScale Area
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataBasic PayCheck Assignment of PayScale Structure to Enterprise Structure
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataBasic PayDetermine Default for PayScale Data
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataBasic PaySetup Payroll Period for Collective Agreement Provision
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataBasic PayDefine PayScale Salary ranges
    Transaction Code:-OH11
    Personnel Management Personnel AdministrationPayroll DataBasic PayWage Types Create Wage Type
    Transaction Code:-OH11
    Personnel Management Personnel AdministrationPayroll DataBasic PayWage Types Create Wage Type
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataBasic PayWage Types Check Wage Type Group u201CBasic Payu201D
    Personnel Management Personnel AdministrationPayroll DataBasic PayWage Types Check Wage Type CatalogCheck Wage Type Text
    Transaction Code:-OH13
    Personnel Management Personnel AdministrationPayroll DataBasic PayWage Types Check Wage Type CatalogCheck Entry Permissibility Per Infotype
    Transaction Code:-OH13
    Personnel Management Personnel AdministrationPayroll DataBasic PayWage Types Check Wage Type CatalogCheck Wage Type Characteristics
    Transaction Code:-OH13
    Personnel Management Personnel AdministrationPayroll DataBasic PayWage Types Check Wage Type CatalogCheck Wage Type Characteristics
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataBasic PayWage Types Employee Sub Group Grouping for Primary Wage
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataBasic PayWage Types Personnel Sub Area Grouping for Primary Wage Type
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataBasic PayWage Types Define Wage Type Permissibility for each PS and ESG
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataBasic PayWage Types Define Wage Type Permissibility for each PS and ESG
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataRecurring Payment and DeductionDefine Reason for Change
    Transaction Code:-OH11
    Personnel Management Personnel AdministrationPayroll DataRecurring Payment and DeductionWage TypesCreate Wage Type Catalog
    Transaction Code:-OH11
    Personnel Management Personnel AdministrationPayroll DataRecurring Payment and DeductionWage TypesCreate Wage Type Catalog
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataRecurring Payment and DeductionWage TypesCheck Wage Type Group u201C Recurring Payments and Deductionu201D
    Transaction Code:-OH13
    Personnel Management Personnel AdministrationPayroll DataRecurring Payment and DeductionWage TypesCheck Wage Type CatalogCheck Wage Type text
    Transaction Code:-OH13
    Personnel Management Personnel AdministrationPayroll DataRecurring Payment and DeductionWage TypesCheck Wage Type CatalogCheck Entry Permissibility Per Infotype
    Transaction Code:-OH13
    Personnel Management Personnel AdministrationPayroll DataRecurring Payment and DeductionWage TypesCheck Wage Type CatalogCheck Wage Type Characteristics
    Transaction Code:-OH13
    Personnel Management Personnel AdministrationPayroll DataRecurring Payment and DeductionWage TypesCheck Wage Type CatalogCheck Wage Type Characteristics
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataRecurring Payment and DeductionWage TypesDefine Employee Sub Group Grouping for Primary Wage Type.
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataRecurring Payment and DeductionWage TypesDefine Personnel Area Grouping for Primary Wage Type
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataRecurring Payment and DeductionWage TypesDefine Wage Type Permissibility for each PS and ESG
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataRecurring Payment and DeductionWage TypesDefine Wage Type Permissibility for each PS and ESG
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationaPPayroll DataAdditional Payments Define Reasons for Changes
    Transaction Code:-OH11
    Personnel Management Personnel AdministrationaPPayroll DataAdditional Payments Wage TypesCreate Wage Type Catalog
    Transaction Code:-OH11
    Personnel Management Personnel AdministrationPayroll DataAdditional Payments Wage TypesCreate Wage Type Catalog
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataAdditional Payments and DeductionWage TypesCheck Wage Type Group Additional Payments
    Transaction Code:-OH13
    Personnel Management Personnel AdministrationPayroll DataAdditional Payments and DeductionWage TypesCheck Wage Type CatalogCheck Wage Type
    Transaction Code:-OH13
    Personnel Management Personnel AdministrationPayroll DataAdditional PaymentsWage TypesCheck Wage Type CatalogCheck Entry Permissibility for Additional Payments
    Transaction Code:-OH13
    Personnel Management Personnel AdministrationPayroll DataAdditional PaymentsWage TypesCheck Wage Type CatalogCheck Wage Type Characteristics.
    Transaction Code:-OH13
    Personnel Management Personnel AdministrationPayroll DataAdditional PaymentsWage TypesCheck Wage Type CatalogCheck Wage Type Characteristics.
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataAdditional PaymentsWage TypesDefine Employee Sub Group Grouping for Primary Wage Type.
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataAdditional PaymentsWage TypesDefine Employee Sub Group Grouping for Primary Wage Type.
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataAdditional PaymentsWage TypesDefine Wage Type Permissibility for each PS and ESG
    Transaction Code:-OH00
    Personnel Management Personnel AdministrationPayroll DataAdditional PaymentsWage TypesDefine Wage Type Permissibility for each PS and ESG
    This is not the complete once just for reference purpose i have given it to u
    Edited by: Sikindar on Nov 19, 2008 9:19 AM

  • The volume will only go to the highest level and I am unable to lower the volume even when sliding the bar

    I am unable to adjust the volume level.  The slider bar goes to the maximum volume even after I try to adjust it lower.

    Try the standard fixes:
    - Reset:
    Reset iPod touch:  Press and hold the On/Off Sleep/Wake button and the Home
    button at the same time for at least ten seconds, until the Apple logo appears.
    - Restore the iPod from backup
    - Restore the iPod to factory defaults/new iPod.

Maybe you are looking for