"#" in the ODS active data view

Hi all,
I have a question. I load data (text strings) into ODS object. Then I look into new or active data and I can see symbols "#" on the places in strings, where occurs any special character (for example from any language). I do not know wheteher it is stored in SAP (database) in this bad format or wheteher it is only represented in this bad format due to my different encoding ?? Normally special characters are represented in GUI well. Thanks
JJ

Hi JJ,
as you can see them in the middle of the texts, it just the way BW displays these characters.
Siggi

Similar Messages

  • To find the latest active date in case if any gap occurs

    Hi Experts,
               I've to find the active date if employee is on leave, any kind, and joined again.
               Is there any FM exist to find out the last active date before the gap??
    Regards,
    Jyoti Shankar

    It would be worth chatting to someone functional in the HR area of the company that you are trying to do this for, as there are many different ways that have been implemented at different sites to say when exactly an employee started/finished.
    Many companies will use IT0041 rather than relying on IT0000 because of the payroll complications that occur with making changes to IT0000 - not to mention that it is rare that a company has been on SAP HR so long that the IT0000 start dates actually reflect employee hire dates (normally a large part of them will reflect system cut-over date).
    Also, many companies have taken the approach of using a new employee number when a person re-joins the company and just using a reference personnel number to copy the common data. In this case using IT0000 is not very useful.
    Like was mentioned above, you're going to have to code something yourself, but it's worth finding out what the local processes for your company are first!
    Hope this is helpful,
    Chris

  • The determined activity date 03/24/2009 must be later than the system date

    Hello everyone!
    I am creating a contract but this error message appears when I put a validity date: "The determined activity date 03/24/2009 must be later than the system date". Where in IMG can I adjust this? Thank you.

    no one responded.

  • Where will the portal activity data reside in SolMan?

    Hi,
         I have activated the portal activity data reporting feature in the portal and the portal activity extractors in SolMan. Now where will the portal activity data reside in SolMan?
    Will the portal activity data be present in the SolMan BI (i.e infocubes such as 0SMD_ADCD, 0SMD_ADCH)?
    thans and regards,
    Divya.

    Hi
    seems it stores ADC datafiles files in file system of portal, from there its fetching ad reporting data time to time
    pleare read this guide [PADC_Activation_Guide.pdf|https://websmp110.sap-ag.de/~sapidb/012003146900000606822009E/PADC_Activation_Guide.pdf]
    and check this [How PAR works?|http://help.sap.com/saphelp_nw04/helpdata/en/b5/c652070d474533a18a930112a4b926/content.htm]
    Jansi

  • How to get rid of the "mil" in Data View's large Display meter

    Hi, there!   I have two analog voltage inputs that I am having signal express V2.5 to collect data on.   The first input is scaled to inches while the second input is scaled to pounds.   For some reason, as i bring up the large display in Data View, the meter will show this "mil" thing.   It won't go away until the scale reaches 1.0000.   For instance, if the scaled signal is less than 1.0000, it will indicate 900mil, 800mil, 50mil 1mil, and so on.....   This really created alot of confusion for my lab.  
    I am hoping if you guys can tell me a way to make 900mil to become 0.900, 50mil to 0.050, and 1mil to 0.001
    Thanks in advance!
    Kin

    Hi Kin,
    Sorry about this. I don't believe there is a way for you to change this in SignalExpress 2.5. However we did add this ability in SignalExpress 3.0. Most displays now have a property page, including the Large Display, which allows you to specify the format and precision shown, including to remove the SI notation. By right-clicking on the Large Display and select Properties, go to the Format & Precision tab, and select the Floating Point option (instead of SI notation).
    Again, I'm sorry to say that this option is only available in SignalExpress 3.0+.
    Phil

  • Pricing conditions for the articles are getting triggered one day before the actual activation date to 3rd party systems through job WPMU.

    Hi SAP Guru´s,
    Currently we are sending the pricing, promotions & article master data delta load to 3rd party system from SAP ECC via SAP XI through IDOCS using daily scheduled batch jobs WPMU. IDOC segment - WP_PLU.
    Here the issue is the promotion & pricing data are sent to 3rd party system one day before the actual start date.
    Eg: Promotion 123456 which has start date as 15/05/2014 & ending on 30/05/2014 & was created & activated on 13/05/2014.
    This promotion 123456 is getting triggered from SAP ECC through batch job on 14/05/2014 morning & 3rd party system receives the data on 14/05/2014 & the promotion are getting activated at 3rd party system end on 14/05/2014 itself which actually gets active from 15/05/2014.
    Same in the case for Standard Pricing data which needs to be active from 31/05/2014 once the promotion 123456 ends on 30/05/2014.
    The standard pricing data gets triggered from SAP ECC on 30/05/2014 through batch job & reaching 3rd party system on 30/05/2014 & getting activate on 30/05/2014 itself.
    This creates more issues at the store end as well as affecting business.
    We checked at 3rd party system end & they replied that their system considers the updated time stamp & date to activate the prices & it does not considers the actual active from & active to date. They need the data to be sent from SAP ECC on the effective date of the pricing & promotions.
    Can any one help me how to change the pricing conditions beign triggered through batch job in SAP ECC based on the actual promotion & pricing conditons start date or is there any other process to trigger the data through the batch job on the actual promotion & pricing data activation date.
    Thanks in Advance.
    Thanks & Regards,
    P.P.Shankar

    Hello Shankar,
    Change the lead time in the POS Outbound Profile. You can't put less than 2 days there so data for today and tomorrow will be transferred which also means you need to adjust your batch timing accordingly.
    Sales and Distribution -> POS Interface -> Outbound -> Maintain Profile for POS Outbound.
    See if it helps. The best option would still be that the 3rd part system considers the activtion date.
    Kind Regards
    Kaizad

  • The ODS activation is taking long time

    Hi,
    We are on SAP NetWeaver BI 701 (Support Package 5).
    We create a Z ODS, it will contain a lot of data (180.000.000 month-end) and we want to generate specific reports about it.
    The activation is taking long time, I assume is because we checked the flag "SIDs Generation upon Activation". I am confused about this check. I really need it? is this check the only problem.
    Thanks for you help.
    Victoria

    Hi Victoria:
       If your Z DSO is used only for staging purposes (you don't have queries based on this DSO and you send the data to another DSO or to an InfoCube) then you don't need to check the "SIDs Generation Upon Activation" box.
    Even more, to achieve better performance during data loads in this scenario, you might consider using a Write Optimized DSO instead of a Standard DSO, but if you decide to take this alternative don't forget to select the "Do Not check Uniqueness of Data" box if you need to write several records with the same Semantic Key.
    Regards,
    Francisco Milán.

  • The Job Failed Due to  MAX-Time at ODS Activation Step

    Hi
            I'm getting these errors "The Job Failed Due to  MAX-Time at ODS Activation Step" and
             "Max-time Failure"
    How to resolve this failure?

    Hi ,
    You can check the ODs activation logs in ODs batch montior >> click on taht job >>> job log
    for this first you check in sm37 how many jobs are running if there are many otehr long running jobs then . the ODs activation will happen very slowly as the system is overloaded .. due to the long running jobs ..this causes the poor performance of system ..
    for checking the performance of system .. you first check the lock waits in ST04..and check wether they are progressing or nt ..
    check sm66 .. for the no of process running on system ..
    check st22 >> for short dumps ..
    check Os07> to check the cpu idle tiem if its less tehn 20% . then it means the cpu is overlaoded .
    check sm21 ...
    check the table space avilable in st04..
    see if the system is overlaoded then the ODS wont get enough work process to create the backgorund jobs for that like(Bi_BCTL*)..jobs .the updation will happen but very slowly ..
    in this case you can kill few long running jobs which are not important .. and kill few ODs activations also ..
    Dont run 23 ODs activation all at a time .. run some of them at a time ..
    And as for checking the key points for data loading is check st22,cehck job in R/3 , check sm58 for trfc,check sm59 for Rfc connections
    Regards,
    Shikha

  • Activating the ODS in the background

    We have just applied secondary indexes to a very large ODS object in our Production environment.  The system allows me to save the changes to the ODS, however, when I try to activate the ODS object, it is timing out.  I assume this is because the system is creating the indexes upon activation.  How do I activate the ODS object in the background?  Since the original activation timed out, do I need to do any cleanup before attempting to activate the ODS in the background?  Any help is very appreciated.

    HI,
    Activate you ODS when the server load is relatively low.
    Following things are to be considered when ODS activation fails:
    1. If your ODS activation fails, in BW SM37, job will fail. This doesnot mean that you reactivate it immediately. There are some chances that it will fail again.
    <b>Reason:</b>
       It will take some time to rollback all the activated records (as activation of some records might have happened).
    <b>HOW to know Rollback taken place or not..?</b>
    1. In SM37 Double Click on (Failed) Job
    2. Click on "Job Details" button
    3. Pop-up window will be displayed
    4. Note down "Executing Server Name" & WP Number/PID
    5. Go to Tcode: SM51, You can see Application server names
    6. Find your Servername and click on the server
    7. You will navigate to another screen
    8. In that PID (3rd Column) you click on the PID# (that you have noted)
    9. If the PID is still running with records, then it means that records are still rolling back.
    10. Once the rollback is over, all that data will be displayed with "0 (zero)" records.
    Then you activate your ODS. Now the ODS activation will run on new PID#.
    <b>Note:</b>
    If you start running immediately after ODS activation failure, then ODS activation will run on the same PID# which it previously ran and activation makes slower (and timeout might happen).
    Check stpes from 1 to 10 when any ODS activation takes place you can know how the records are updating.
    Hope this helps you....
    Thanks,
    Shyam

  • To extract portal activity data from the portal into Solution manager.

    HI all,
          I need to extract the portal activity data from the portal into Solution  Manager BI and then later on into the SAP BW in order to generate BEx reports on the portal activity data. I need to know about the configuartions that are needed to be done on the portal side and the solution manager side so as to get the data into SolMan from portal.  Waiting for a response.
    Thanks and regards,
    Divya.

    Hi
    In solution manager you can do the  analysis of the ADC data files (Portal activity reporting) as as part of the End-to-End Diagnostics (Portal Activity Reporting tab in the End-to-End Workload Analysis).
    Will you see the Portal Activity Reporting tab under End-to-End Workload Analysis?
    by default PAR in SAP Solution Manager 7.0 EHP1 is deactivated ,since we requires
    some manual configuration of the Activity Data Collector.
    please follow the attached config guide in the SAP note for configuration.
    Jansi

  • I want to know the activation date. IMEI: *******. Please, thank a lot!

    I want to know the activation date. IMEI: *******. Please, thank a lot!
    <edited by host>

    Ductri wrote:
    I want to know "THE FIRST" activation date. IMEI: 990002776219774. Please, thank a lot!
    iPhone 5, iOS 6.1.4
    Please help me!
    You've already been told that nobody here can help you.  These are user to user forums.  You are not addressing Apple by posting here, so I don't know why you think anyone here would have access to Apple's systems in order to check for such information.

  • No msg from process chain on ODS activ failure

    All,
    We are loading and activating a CRM ODS (0CRM_PROH) in a process chain.  The process chain is set up to deliver a message if the ODS activation fails, but this is not happening reliably.
    For instance, yesterday a hex character came over from the source system causing ODS activation failure.  Strangely enough, the overall status of the request in the monitor was green.  Also, the activation step in the RSPC planning view was blue, not red as I would expect.  You could really only see the failure by switching to log view in RSPC, where it was clear the ODS activation had failed.
    Any thoughts on why the overall status of the request is green instead of red or yellow when the ODS activation fails?  Or, any thoughts on why no message is going out?  It's probably obvious that I'm new at interpreting the RSPC screens, so any general references on this topic would be helpful.
    Thanks,
    Bob
    P.S.  The ODS in question is set for automatic activation and automatic updating of data targets.  We are running BW 3.10.21, BI_CONT 3.30.16.

    Hello Diane
    We also had this issue, but with an older version (30B patch 7, works OK w/ patch 14).
    Anyway, to fix it:
    - create a new variant (let's call it V1 as an example) for the SAP program RSODSACT1
    - in your process chain, insert an ABAP call after the ODS load. Punch it RSODSACT1 as program and V1 for the variant
    It worked for us
    Good luck
    Ioan

  • Sort order in ODS active table ?

    Hello BW Experts,
    What sort order is data stored in the ODS active table.
    Thanks,
    BWer

    Bwer
    Check this link and hope this helps
    Thanks
    Sat
    http://help.sap.com/saphelp_nw04/helpdata/en/10/54853b175d214ee10000000a11402f/frameset.htm

  • Active Data Service DataUpdateManager is NULL

    Hello,
    I have two pages that make use of the ADF Active Data Service, and sporadically when one of the pages loads it abruptly refreshes itself and loads again. I haven't been able to reproduce this on demand, but when it happens its very distracting, and the following information is logged:
    <LongPollingChannelHandler> <handleError> Active Data Service DataUpdateManager is NULL
    <RichExceptionHandler> <_logUnhandledException> ADF_FACES-60098:Faces lifecycle receives unhandled exceptions in phase RESTORE_VIEW 1
    oracle.adfinternal.view.faces.activedata.IllegalActiveDataStateException: ADF_FACES-60078:Forcing the client to reload the page, because component with ID: pt1:r1:0:pt1:aot1 was not registered for Active Data.
         at oracle.adfinternal.view.faces.activedata.PageDataUpdateManager._startActiveData(PageDataUpdateManager.java:562)
         at oracle.adfinternal.view.faces.activedata.PageDataUpdateManager.startActiveData(PageDataUpdateManager.java:541)
         at oracle.adfinternal.view.faces.context.RichPhaseListener$StartStopADSContextCallback.invokeContextCallback(RichPhaseListener.java:740)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1735)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1750)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1750)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
         at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.invokeOnComponent(ContextSwitchingComponent.java:222)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1750)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1750)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
         at oracle.adf.view.rich.component.fragment.UIXInclude.invokeOnComponent(UIXInclude.java:161)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnNamingContainerComponent(UIXComponentBase.java:1693)
         at oracle.adf.view.rich.component.fragment.UIXRegion.invokeOnComponent(UIXRegion.java:625)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
         at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.invokeOnComponent(ContextSwitchingComponent.java:222)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1750)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
         at oracle.adf.view.rich.component.fragment.UIXInclude.invokeOnComponent(UIXInclude.java:161)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1750)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1750)
         at org.apache.myfaces.trinidad.component.UIXDocument.invokeOnComponent(UIXDocument.java:106)
         at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:1321)
         at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:678)
         at oracle.adfinternal.view.faces.context.RichPhaseListener.handleStartAndStopActiveData(RichPhaseListener.java:452)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:487)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:202)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:508)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:173)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:125)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:468)
         at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:468)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:293)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:199)
         at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at com.sps.regression.servlet.ApplicationSessionExpiryFilter.doFilter(ApplicationSessionExpiryFilter.java:55)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    <RegistrationConfigurator> <handleError> ADF_FACES-60096:Server Exception during PPR, #1
    I haven't been able to find any useful information online about what causes this error or how to correct it.
    Additionally, sometimes a backing bean used in each of these task flows is constructed twice, and the following is logged in between the constructions:
    <RichWindowManager> <updateCurrentWindowIdForPartialRequest> No window specified in request
    <SessionDataUpdateManager> <__getPageDataUpdateManager> cannot register active data when window has no name
    Neither of these things happen 100% of the time. Has anyone else experienced either of these issues?
    Thanks,
    Evan Gilbert

    Hi Evan,
    Did you find out what was the cause of the issue ? We have the exact same problem and was looking for a solution. Please let me know if you have found any pointers.
    thanks,
    Jaseer

  • ODS Activation Issue in Prod - Critical

    We are in BI 7. We have a huge ods ZXYZ in Prod. It has more than 400 million records. BEx reporting - off.
    Over the last weekend some data was added the requests were being activated and there was master data activity in parallel. The ODS activation failed with SYSTEM_EXCEPTION. Unfortunately not investigating the root cause, the ODS activation was resumed and it returned SYSTEM_CANCELED again as there was master data activity going on.
    The problem is that request is now partially activated and it became in faulty status. When trying to activate, we get the following error message.
    <i>Activation of M records from DataStore object ZXYZ terminated
    'A' and 'U' entries exist in RSODSACTREQ for request REQU_CTAKWUIM6ZAWBQC1K6Q5TVL8M - termination</i>
    When trying to delete that request which was partially activated, it fails complaining about Faulty status of the ODS.
    The problem is we are not moving forward as the request cannot be deleted/activated due to this.
    RSODSACTREQ table has Activation status 2  - Activate failed for this request.
    Can you experts please advice.

    Hi,
    I see that your message was not answered and you may not have this issue any more. But for future reference you could refer to note 947481. You might be able to use step 1 from this note to clean the failed request and reload your data.
    Hope it will help some day. It did work for us.
    Sameer Gandhi

Maybe you are looking for