Maintain Default OTR System Context

Hi All!
In my project we've just intalled EHP3 on ECC 6.0. Now when i check the table SOTR_TEXT there seems be to 2 active contexts but in the BSPs i'm getting always the standard context.
I want to set our 'Z' context as default.
I checked all the customizing and it is ok and the systems says to me that the 'Z' context is the default one.
I've run the report SOTR_DEFAULT_CONTEXT_FLAG_SET a couple of times and also de  /$OTR but it does nothing.
Does anyone knows what's the trick?
Many thanks!!

Hi there!
I had previously seen that posting. The problem is that i already have an active and well defined context with all the texts. And it was working fine till we install the EHP3.
The systems tells me that the 'Z' context is the active one but when i login in the BSPs it shows me that standard texts of the standard context.
Weird..

Similar Messages

  • Maintain Default Cost element in controlling Area

    I am getting the following error while working on Down payments :
    " CO down payment is active in the controlling area.You must therefore maintain default Cost elemnts and revenue elementsfor down payments.
    Maintain the default cost element for down payments for controlling area in the project system implementation guide.
    PS is not activated.
    How do we resolve the issue.?
    Cheers
    Kartik

    Hi Kalyan 
    Had a look , but why do we need to maintain default CE in OKEP ?
    We were able to raise PR then PO previously but something seems to have happened that we are getting this error message.
    Please advise.
    Cheers
    Kartik

  • Maintain default revenue element in controlling area 1000

    Hi Experts,
    I am doing Customer Down Payment T Code:F-29
    We had PS Module implemented.
    So at the time of DP i put the network and Operation/Activity Number and also put the Work Breakdown Structure Element (WBS Element)
    At the Customer line item.
    that time system gives me following error.
    Maintain default revenue element in controlling area 1000
    Message no. FI661
    Diagnosis
    CO down payment update is active in controlling area 1000. You must therefore maintain a default cost element and a default revenue element for down payments.
    Procedure
    Maintain the default cost elements for down payments for controlling area 1000 in the Project System implementation guide.
    More information.
    If i click on More information then it will goes to T Code: OKEP
    But i am unable to no the OKEP screen what i have to assign there ?
    waiting for reply.
    Regards,
    J

    Hi,
    I think you need to maintian the default cost element for DP to vendor for WBS (Capex). For controlling area specific you need to assign the cost element of category 1. This you have to maintian in Development and transport the change thu quality to production.
    Controlling are   name, cost element for Vend DP.....
    Thanks
    Dinabandhu

  • Maintain default revenue element in controlling area

    Hi Experts,
    I am doing Customer Down Payment T Code:F-29
    We had PS Module implemented.
    So at the time of DP i put the network and Operation/Activity Number and also put the Work Breakdown Structure Element (WBS Element)
    At the Customer line item.
    that time system gives me following error.
    Maintain default revenue element in controlling area 1000
    Message no. FI661
    Diagnosis
    CO down payment update is active in controlling area 1000.  You must therefore maintain a default cost element and a default revenue element for down payments.
    Procedure
    Maintain the default cost elements for down payments for controlling area 1000 in the Project System implementation guide.
    More information.
    If i click on More information then it will goes to T Code: OKEP
    But i am unable to no the OKEP screen what i have to assign  there ?
    waiting for reply.
    Regards,
    J

    Hello nagesh simhadri ,
    I have the answer for your problem, i think that you already solved it but the answer will be useful for the others, because i had the same problem and i found your post...
    In fact, there is a customizing parameter to set:
    SPRO -> PROJET SYSTEM -> Costs -> Actual costs and Forecast -> Update down payments -> Define default cost elements for down payments
    or simply you can use the transaction code OKEP.
    I hope that this will help someone...
    Best regards,
    Yassine NEJMY

  • Maintain default revenue element in controlling area   - Upadate was ter

    Hi Sap gurus,
    I am getting an error when i am doing VF01,
    Update was terminated
    System ID....   ABP
    Client.......   800
    User.....   SAPUSER
    Transaction..   VF01
    Update key...   DC6AEF938E974DF488974D703A452AE9
    Generated....   28.11.2008, 12:25:33
    Completed....   28.11.2008, 12:25:33
    +Error Info...   FI 661: Maintain default revenue element in controlling area +
    Can any one solve this error, and where to do customizing settings...
    Thanks in advance
    Nagesh

    Dear Nagesh
    Go to IMG Path -- Controlling --> Profitability Analysis --> Master Data --> Revenue Element / Cost Element.  There ensure that the relevant revenue element is maintained.
    thanks
    G. Lakshmipathi

  • Maintain default cost element in controlling area Message number FI660

    Hi All,
    We found the Down Pay Request (doc. booked by F-47)  cannot be picked up by F110. In Job log the error shown as Maintain default cost element in controlling area.
    Long text error details.
    Maintain default cost element in controlling area
    Message number FI660
    CO down payment update is active in controlling area WAPC. You  must  therefore maintain a default cost element and a revenue element  for down payments.
    Maintain the default cost element for dow payment for controlling area in the project system implementation guide.
    Kindly advice.
    Note
    In the define dafault cost elemens for down payments in Project system-OKEP  the CE for vendor and cusotmer downpayemnt  is missing

    hi srinivas
    OKEP configuration is necessary
    if while creating down payment request you have not assigned cost element
    maintain cost elements there.
    regards
    rohit

  • Changing Default logical system names of a model.

    Hi
        How could i change the
         Default logical system name for model instances:
         Default logical syatem name for RFC metadata:
        values for existing model? without recreating the model.
         Thanx

    Hi shah kond,
    you can change  rfc destinations of model in 2 differnet ways.
    firs one: right clcik on project
              from the context menu select propeties
              it will open a dialogbox from that select dynpro references then click on jco references tab
    by using add and remove buttons u can add and remove joc destnations
    2.expand ur model class double click output class.now seelct properties view.there u can change the jco destination
    hope this will use ful for u
    Regards
    Naidu

  • Dúvida -  NF-e: Maintain Connected Authority Systems - layout 3.10

    Boa noite!
    Estou realizando o customize da SPRO, porém notei que só posso inserir a seguinte entrada para um mesmo CNPJ:
    Ou seja, quando tento colocar os demais estados o erro de chave duplicada é retornado devido aos campos logical system e Company's Own CNPJ. Dessa maneira, quando executo o novo programa de status de serviço (/XNFE/NFE_CHECK_SRV_STATUS) relalizando o debug noto que existe uma verificação durante a execução da função (/XNFE/SRVSTA_READ_CUST) na qual, por mais que eu tenha cadastro todos os cUF na spro que ficam registrados na tabela (/xnfe/tcuf) o status de serviço acaba sendo executado apenas para o que existe na tabela (/xnfe/govpar) alimentada pela configuração da NF-e: Maintain Connected Authority Systems da imagem que enviei posteriormente. Sendo assim só é executado o status de serviço para SP e não para todas as cUF que estão na atividade NF-e: Define Service Status Request for Authority (SEFAZ). Abaixo segue trecho do código que verifiquei que realiza esse controle no debug:
    SELECT * FROM /xnfe/govpar INTO TABLE lt_govpar
                                  WHERE doctype = iv_doctype.
    *--- 2. Version determination
      IF lt_govpar IS NOT INITIAL.
        SELECT * FROM /xnfe/xmlversdet INTO TABLE lt_xmlversdet
                           FOR ALL ENTRIES IN lt_govpar
                                 WHERE doctype  = iv_doctype
                                   AND logsys   = lt_govpar-logsys
                                   AND ( cnpj     = lt_govpar-cnpj
                                    OR   cnpj     = ' ' )
                                   AND messtype = iv_messtype.
    *--- 3. Service status check parameter
        SELECT * FROM /xnfe/tcuf INTO TABLE lt_tcuf.
        LOOP AT lt_govpar ASSIGNING <ls_govpar>.
    *--- Get corresponding entry from version determination
          READ TABLE lt_xmlversdet WITH KEY doctype = <ls_govpar>-doctype
                                            logsys  = <ls_govpar>-logsys
                                            cnpj    = <ls_govpar>-cnpj
                                  ASSIGNING <ls_xmlversdet>.
          IF sy-subrc <> 0.
    *--- If nothing is found try with blank CNPJ
            READ TABLE lt_xmlversdet WITH KEY doctype = <ls_govpar>-doctype
                                              logsys  = <ls_govpar>-logsys
                                              cnpj    = ' '
                                    ASSIGNING <ls_xmlversdet>.
          ENDIF.
          IF sy-subrc IS INITIAL.
    *--- Get corresponding entry for service status check parameter
            READ TABLE lt_tcuf WITH KEY doctype = <ls_govpar>-doctype
                                        cuf     = <ls_govpar>-cuf
                                      ASSIGNING <ls_tcuf>.
            IF sy-subrc IS INITIAL.
              ls_stacheck-cuf       = <ls_govpar>-cuf.
              ls_stacheck-tpamb     = <ls_govpar>-tpamb.
              ls_stacheck-xmlvers   = <ls_xmlversdet>-xmlvers.
              ls_stacheck-sscperiod = <ls_tcuf>-sscperiod.
              ls_stacheck-tzone     = <ls_tcuf>-tzone.
              ls_stacheck-respcont  = <ls_tcuf>-respcont.
              ls_stacheck-checkcont = <ls_tcuf>-checkcont.
              APPEND ls_stacheck TO et_stacheck.
            ENDIF.
          ENDIF.
          CLEAR: ls_stacheck.
        ENDLOOP.
      ENDIF.
    Sendo assim, como faço para que na atividade NF-e: Maintain Connected Authority Systems eu possa inserir todos os cUF com para os quais executarei o status de serviço e posteriormente enviarei notas?
    Obrigado.,

    Bom dia Luís,
    Exatamente! De fato o que ocorreu foi uma confusão, pois na versão anterior era possível enviar o status de serviço mesmo se você não possuísse uma filial para o estado em questão. Quando fui fazer a migração do cliente todos os estados estavam configurados para emitir status de serviço, porém não há necessidade de enviar o status de serviço para um estado visto que você não possui uma filial para emissão de Nota no mesmo.
    Abs.,

  • NF-e: Maintain Connected Authority Systems - Já existe uma entrada com a mesma chave

    Bom dia!
    Estou tendo um problema para adicionar novas entradas na SPRO - OUTBOUND -NF-e: Maintain Connected Authority Systems para configuração do layout 3.10:
    Sendo assim, como devo configurar todos os estados para a SEFAZ se o sistema lógico e CNPJ são chaves da tabela /xnfe/govpar?
    Com isso, não consigo executar todos os status de serviço no layout novo através do report (/XNFE/NFE_CHECK_SRV_STATUS) depois de cadastrálos na atividade NF-e: Define Service Status Request for Authority (SEFAZ,) pois durante a execução do report  (/XNFE/NFE_CHECK_SRV_STATUS) além da tabela  /xnfe/tcuf a tabela /xnfe/govpar também é verificada.
    Grato.,

    Bom dia Luís,
    Exatamente! De fato o que ocorreu foi uma confusão, pois na versão anterior era possível enviar o status de serviço mesmo se você não possuísse uma filial para o estado em questão. Quando fui fazer a migração do cliente todos os estados estavam configurados para emitir status de serviço, porém não há necessidade de enviar o status de serviço para um estado visto que você não possui uma filial para emissão de Nota no mesmo.
    Abs.,

  • Unable to 'set the default source system' to Install Business Content

    Hi,
    Maars here. This is my first post hoping that in future ones I'll also be lending a helping hand.
    I am trying to 'Install Business Content' under the BUSINESS CONTENT section in txn RSA1. I am doing this after 'Transfer Data Sources' in R/3 and I can now see all the data sources (under the application component hierarchy) for the source system. But I am not able to see the Info Objects in the Business Content.
    When I try to set R/3 as the default source system (got this screen after clicking a icon in the standard tool bar), BW is not saving the settings ie., I set the R/3 as the default and then click on OK. If I go back to the same screen again, I find that my settings were NOT saved.
    Could you please help me out?
    Thank you.

    Hi,
    It seems to be a bug in version 3.5.
    Do like this:
    After you open the screen to <i>choose the dafault source system</i>
    Clcik on 3rd button(F6) available in the bottom of the scrreen.
    And then select teh tick mark for required system.
    And then click on Continue button
    You have do this step before you drop the cube to right side of the cube.
    Ok, even after all these steps , if you reopen the screen you would not see Tick mark u have done just before. DONOT WORRY ABT it.
    Drag and drop required cube with dat flow before.
    Now you can see the Transfer rules with selected Source system only in the collected Objects.
    With rgds,
    Anil Kumar Sharma .P

  • How can I get back to default in System pref/ displays/ color. iMac 10.9.5

    How can I get back to default in System pref/ displays/ color?  iMac 10.9.5

    Select the iMac option.
    27" i7 iMac (Mid 2011) refurb, OS X Yo (10.10), Mavs, ML & SL, G4 450 MP w/10.5 & 9.2.2

  • Finding "Default Logical System Name Model Instance" in DC Project

    Hi,
    While Creating an Adaptive RFCModel, one defines the
    Default Logical System Name for Model Instance & the
    Default Logical System Name for RFCMetadata.
    In which file can I find these settings at a later stage in the Project File Structure.
    Ofcourse, I can view them in the WedynproContentAdministrator under the Jco Destinations.
    But is there anyway to access them in the NWDS?
    Regards
    MK

    Hello MK,
    You'll find the Logical System Names of the JCo destinations in the file ".wdproperties" under the project structure.
    Bala

  • Default logical system names for application and metadata in models.

    hi,
    I have a dbt in web dynpro java. When we create a model, we give the logical system names. When our developement is over, do we have to change these names because in test system and subsequently production system, the backends will be oviously different than developement ?
    how do we change them and re import after changing? in abap we cant change our code in test and prod systems right  so how is it in web dynpro java ?
    thanks

    Hi Jeschael,
    thanks for the reponse.
    When I create the model, I give the default logical system names and on the next screen I give the
    ip address of the backend system, client , login, password etc
    Even though the logical system names wud be same in Dev, Test and Prod systems, the ip address, login password is different so how do I give it ?
    thanks
    B

  • Maintain default cost element in controlling area USD

    Hi All,
    I were trying to clear vendor down payment with vendor invoice ( error)required me to Maintain default cost element in controlling area USD.
    Is that a way to do without making to default cost elemnt
    Thank you for your help
    Regards
    bali

    Hi,
    As process you should clear the down payment first and then vendor thry F-44.
    It should not be asking you for default cost centre untill there is validation rule set.
    hope this helps you.
    Regards
    Bharat

  • Maintain default custom vendor

    Dear all,
    I want to maintain default vendor for some custom condition type. In case of import PO, we maintain custom vendor at item level of PO in condition type. i want that vendor code should come automatically, i have not to maintain multiple time at the time of PO creation.
    Maintaining a default vendor code for all customs related condition type.
    Does anybody have idea regarding this..Please share your views.....

    Dear,
    At the time of creation of PO adopt the old PO and values all other details follows automatically. If you want to change in the PO you can change easily and new will not show any reference of the old PO.
    Hope this will solve your problem
    Thanks & regards
    Varun Bisaria

Maybe you are looking for