E-Recruting - Internal conversion WDA to BSP

Hi,
We enhanced WD component ‘HRRCF_C_WORK_EXP_UI’ with few new fields and it works fine in Internal/External Candidate UI.
When we go to Recruiter Start Page > Enter Internal (or External) Application > Save & Continue > Work Experience, my enhancement to WDA reflected there, however I’m seeing below differences.
1)     Radio button displayed as Drop Down.
2)     Order of the fields are not same.
3)     Colon ‘:’ is missing after field label.
4)     Candidate WDA calling Long text of data element but Recruiter BSP calls Medium Text of data element.
5)     It has BSP look and feel layout
Is SAP internally generating/converting WD Component to BSP application? If yes, how and where it is doing this conversion?
Do let me know, if you need anything else.
Regards,
...Naddy

Hi,
there is no link between WDA and BSP. It has something to do with the standard delivery in E-Recruiting.
You added some fields in E-Recruiting infotypes as customer includes I assume. Well in WDA front end of E-Recruiting, you
will not seem them automatically. Therefore you need to do enhancements.
The BSP interface within E-recruiting has a functionality instead. Fields within the customer includes are displayed automatically.
This is E-RECRUITUNG standard. Fields with domains or search helps are always displayed as DDLB.
Text fields as input fields, and date fields as date navigators.
You do not have the possibility to change the format of the fields. The sort order in BSP depends on the order in your CI.
So as you see there is no link between both front ends. Its just a difference in delivery by SAP.
Regards

Similar Messages

  • Calling WDA from BSP

    Hi all,
    Is it possible to call WDA from a BSP via a hyperlink and pass parameters that the WDA would need? How could I go about doing this?

    Hi Alexander,
       You can't pass the information(Context Data) from WDA to BSP directly so you just store the information in some variables or internal tables use the normal user paramenters like EXPORT & IMPORT or SET and GET parameters. Thgoruhg this way only you can communicate the data between these 2 technologies otherwise you need to save the data in some ztable and use the same table in both technoloes.
    you can also use Server Side Cookies.
    Perhaps take a look into this blog from Koen Labie:
    /people/koen.labie2/blog/2006/11/29/eating-cookies-with-webdynpro-and-bsp
    The blog shows how to pass the data from BSP to WD.
    Transfering data between WD and BSP via Server side Cookies can also be used for your requirement.
    For that you have to set the Data Cookie in the WD and then get the Cookie in the BSP.
    Please keep in mind that if you mix two different technologies you will have to deal with integration. WD and BSP will run in two different sessions at the server. Handling data exchange, login, logoff, data transfer at the server and client, etc can be challenging. You might end up with recreating enterprise portal-like software. So depending on the scope of the project, it might be more advisable to stay within the BSP environment or to reuse the SAP enterprise portal to integrate these two technologies at the client.
    Hope this will help you.
    Cheers,
    Darshna.

  • Internal Conversion error excel-SAP

    A request was made from our users if it was possible to make standard excel lay outs
    This moment when running a report, the filters and subtotals dissapear after downloading to excel.
    Apperantly it is possible to make a standard lay out in excel.
    For this I :
    - run my report
    - go to change view --> excel
    - select a standard excel lay out.
    But when I download then to my hard disk and open the file, no data is in the file.
    When I paste my data in it and save and try to upload it to SAP i get the problem internal conversion error
    Anybody has an answer for me how to proceed?
    many thanx,
    Stef

    Hi Amit,
    If you uncheck the "Calculate before aggregation" checkbox and activate the view, you will see in the generated log that a Calc scenario is created. (a view with /olap wrapper). Due to the calc scenario, the aggregation is defined as the default behavior for the KFs and hence the calculation cannot be done before aggregation.
    By the way, I did not understand why do you need calculate before aggregation for a KF which is just a copy of another KF. If you need Gross amount in Local currency and EUR, then just perform the currency conversion without "Calculate before aggregation" checkbox. It will work.
    Regards,
    Ravi

  • Passing internal table to a BSP Table view

    Hi All,
    I have a Function Module which returns an internal table
    with data from R/3.
    I would like to know is it possible to display it in a custom BSP Table view for Web IC.
    please help if anybody solved similar problem!.
    Thanks n Regards,
    sudeep v d.

    Hi,
    I am able to display a table view but here i am passing
    the table parameter in the .htm like this.,
    table           = "//Address/Table"
    where,
    'Address' is type ref to CL_CRM_IC_BUPAMOREADDRESS_CN01
    I created my  own implementation class (ZCL_CRM_IC_BUPAMOREADDRES_IMPL)
    and context class (ZCL_CRM_IC_BUPAMOREADDRES_CTXT)
    created!.
    here my question is .. is there anyway to pass an internal table to this view!.
    please help..
    Thanks n regards,
    sudeep v d.

  • How to use WD data into BSP??

    Hi All,
    i have senario as,
    in my BSP application i am calling WDA application passing url to iframe.
    now i want to use the data from WDA application into the BSP...for eg. context data.
    how can i use it into BSP application.
    please let me know.
    Regards,
    Chandra

    Hi Chandra,
    You can't pass the information(Context Data) from WDA to BSP directly so you just store the information in some variables or internal tables use the normal user paramenters like EXPORT & IMPORT or SET and GET parameters. Thgoruhg this way only you can communicate the data between these 2 technologies otherwise you need to save the data in some ztable and use the same table in both technoloes.
    I hope i make you clear.
    Warm Regards,
    Vijay

  • Future of BSP

    hi,
    with SAP introducing WEB dynpro, what is the future of BSP. Will BSP die in the near future or is it still a good choice for customer to implement web applications ?
    Elko

    I think that the role that BSP plays will change slightly, but I certainly don't see it dying.
    First of WDA is only available in NetWeaver04S and higher.  Looking at the vast majority of SAP solutions out there, many of them for years to come will only be on releases lower than that.  Talking to other customers that have made the move to ECC 5.0 or R/3 enterprise in the last year or two - many don't expect another major upgrade for 5-8 years.  For these customers BSP is there already and a perfectly fine tool to use.
    Second - WDA and BSP have some technical differences that set them appart.  WDA is stateful only.  BSP is stateful or stateless.  BSP allows pixel perfect rendering and the inclusion of any frontend rendering technology you want to code (custom HTML, JavaScript, ActiveX controls, AJAX, Flash, etc).  WDA on the other hand is a closed rendering system.  You have no access to the low level rendering - nor can you create your own UI elements (to be fare - you can create composit elements as WD components - an example being the SAP implementation of ALV Grid in WD - just not new elemental UI objects).  This is done to obscure the client delivery mechanism and future proof the technology (WebDynpro can be deployed to the browser or to a Smart client already - with very different rendering technologies - yet your code remains the same).  This approach is great for creating internal facing business transactions - but isn't necessarily flexible enough for everthing.  Internet facing applications which need greater rendering customization and statelessness would still be better served as BSP.

  • How to call BSP page in one frame from a webdynpro page in another frame?

    Dear experts,
    I have a scenario as follows:
    A BSP application which contains 5 frames. in the first frame I am calling a web Dynpro application. This is a tree and it is displayed correctly. on click of an item (node item) in the tree, a bsp page should be displayed in the second frame. I am not able to display this in the second frame. When I call the BSP page, it is getting displayed in the same frame (i.e, the first frame).
    Kindly help me out.
    Thanks & Warm Regards,
    Jenny

    From WDA you can't force the navigation of a different frame. Nor should you really be building an application with WDA running within a frame.  You will have session management problems. 
    SAP recommendation is to use the NetWeaver Portal. You could then place the WDA and BSP applications into separate iViews.  They can communicate with each other using Portal Eventing.

  • Calling a webdynpro URL in new window from BSP

    Hi experts,
      i am calling a URL from BSP application by creating a link and on the 'onclick'  event of the link ,using following code
    navigation->goto_page( URL = l_wd_url session = 'NEW' ).
    My problem is ,i have to open this page in a new window(the Page is basically a webdynpro URL) ,so far it is only opening in same window.I have tried different other options.
    navigation->next_page( URL = l_wd_url session = 'NEW' ).
    CALL METHOD runtime->server->response->redirect( url = l_wd_url ).
    navigation->call_application( URL = l_wd_url ).
    I tried using call_browser FM also but it is dumping.
    href tag will not work in my case as i have to capture the event and write some code inside  that event..
    Please suggest what i can do now?

    Hello Graham,
    I am trying to get the windows user id in webdynpro abap.
    I am unable to get,
    So I used BSP application to get the windows user id.
    I using java script to get that.
    After that I don,t know how to  assign that java variable to ABAP variable. the
    Insted of calling the WDA using the following way
    <a href="<%=l_wd_url%>" target="_blank">Click Here</a>
    is there any other way to call WDA from BSP based on some action.
    Regards
    Srini

  • Passing Internal tables between pages (in stateless appl.)

    hi BSP gurus,
    how do I pass internal tables from one BSP page to another. The problem is that the appl. is stateless and hence I am not able to use the appl. class.
    thanks in advance,
    Ashish Walke

    Hi Ashish,
    In the onInputProcessing event of the first page , write the following code...
    call method NAVIGATION->SET_PARAMETER exporting
    name = 'filled_table'
    value = filled_table.
    Here filled_table is internal table.
    NAVIGATION->GOTO_PAGE('second.htm').
    In the next page , you can make the internal table as auto in the attributes.
    Since you have made the itab as auto transfer , you can directly access the itab in the initialization event of the next page if it is stateless.
    Regards,
    Aashish Garg

  • Dynamic internal table assignment.

    I have few internal tables in my bsp application but at a time i need to show 1 internal table based on some criteria into tableview.
    can anybody guide me how to do so, its really urgent
    Thanx,
    Abhijeet

    Hi Abhijeet,
    Just use field-symbols and ur problem will be solved.
    Check out the following code:
    <% Field-symbols <var> type any .
    .......logic for internal table selection..
      assign it2 to <var>.
    %>
    <htmlb:tableView id="tab1" table="<%=<var>%>">
    </htmlb:tableView>
    Hope it'll help u.
    Thanks & Regards,
    Ankur

  • Using BSP IN ISR framework

    Hi all,
    Can someone tell me how to use a BSP in ISR. We try to use a sample BSP (ISR_DEM01) but this does not work. We googled on the internet, but we did not find any information or samples! We only found the ISR cookbook, but this did not give the correct informatie we need.  The BSP is activated in SICF and when we do a test the BSP works.
    Kind Regards,
    Richard

    >
    R. Middelburg wrote:
    > Hi all,
    >
    > Can someone tell me how to use a BSP in ISR. We try to use a sample BSP (ISR_DEM01) but this does not work. We googled on the internet, but we did not find any information or samples! We only found the ISR cookbook, but this did not give the correct informatie we need.  The BSP is activated in SICF and when we do a test the BSP works.
    >
    > Kind Regards,
    > Richard
    I'm not sure this is the best forum in which to post your question.  ISR is an application specific framework that mostly involves Adobe Interactive Forms. 
    I can tell that in general WDA doesn't necessarily support directly embedding BSP.  We have the iFrame UI element that can technically work, but that is depricated. Most of the time when you want to integrate BSP, you should use separate iViews in the portal and use portal eventing.  The other option is to simply navigate between the WDA and BSP applications using linkToURL or Navigation Plugs.
    You might want to consider having this thread moved to another forum.  If so, let me know and I have it moved.

  • Not able to retrive the recordset from oracle stored procedure in VC++

    Hi,
    I am trying to retrieve the records from the reference cursor which is an out parameter for an oracle 9i store procedure in VC++ application. But it is giving the record count as -1 always. Meanwhile i am able to get the required output in VB application from the same oracle 9i store procedure .
    Find the code below which i used.
    Thanks,
    Shenba
    //// Oracle Stored Procedure
    <PRE lang=sql>CREATE OR REPLACE
    PROCEDURE GetEmpRS1 (p_recordset1 OUT SYS_REFCURSOR,
    p_recordset2 OUT SYS_REFCURSOR,
    PARAM IN STRING) AS
    BEGIN
    OPEN p_recordset1 FOR
    SELECT RET1
    FROM MYTABLE
    WHERE LOOKUPVALUE > PARAM;
    OPEN p_recordset2 FOR
    SELECT RET2
    FROM MYTABLE
    WHERE LOOKUPVALUE >= PARAM;
    END GetEmpRS1;</PRE>
    ///// VC++ code
    <PRE lang=c++ id=pre1 style="MARGIN-TOP: 0px">ConnectionPtr mpConn;
    _RecordsetPtr pRecordset;
    _CommandPtr pCommand;
    _ParameterPtr pParam1;
    //We will use pParam1 for the sole input parameter.
    //NOTE: We must not append (hence need not create)
    //the REF CURSOR parameters. If your stored proc has
    //normal OUT parameters that are not REF CURSORS, you need
    //to create and append them too. But not the REF CURSOR ones!
    //Hardcoding the value of i/p paramter in this example...
    variantt vt;
    vt.SetString("2");
    m_pConn.CreateInstance (__uuidof (Connection));
    pCommand.CreateInstance (__uuidof (Command));
    //NOTE the "PLSQLRSet=1" part in
    //the connection string. You can either
    //do that or can set the property separately using
    //pCommand->Properties->GetItem("PLSQLRSet")->Value = true;
    //But beware if you are not working with ORACLE, trying to GetItem()
    //a property that does not exist
    //will throw the adErrItemNotFound exception.
    m_pConn->Open (
    bstrt ("Provider=OraOLEDB.Oracle;PLSQLRSet=1;Data Source=XXX"),
    bstrt ("CP"), bstrt ("CP"), adModeUnknown);
    pCommand->ActiveConnection = m_pConn;
    pParam1 = pCommand->CreateParameter( bstrt ("pParam1"),
    adSmallInt,adParamInput, sizeof(int),( VARIANT ) vt);
    pCommand->Parameters->Append(pParam1);
    pRecordset.CreateInstance (__uuidof (Recordset));
    //NOTE: We need to specify the stored procedure name as COMMANDTEXT
    //with proper ODBC escape sequence.
    //If we assign COMMANDTYPE to adCmdStoredProc and COMMANDTEXT
    //to stored procedure name, it will not work in this case.
    //NOTE that in the escape sequence, the number '?'-s correspond to the
    //number of parameters that are NOT REF CURSORS.
    pCommand->CommandText = "{CALL GetEmpRS1(?)}";
    //NOTE the options set for Execute. It did not work with most other
    //combinations. Note that we are using a _RecordsetPtr object
    //to trap the return value of Execute call. That single _RecordsetPtr
    //object will contain ALL the REF CURSOR outputs as adjacent recordsets.
    pRecordset = pCommand->Execute(NULL, NULL,
    adCmdStoredProc | adCmdUnspecified );
    //After this, traverse the pRecordset object to retrieve all
    //the adjacent recordsets. They will be in the order of the
    //REF CURSOR parameters of the stored procedure. In this example,
    //there will be 2 recordsets, as there were 2 REF CURSOR OUT params.
    while( pRecordset !=NULL ) )
    while( !pRecordset->GetadoEOF() )
    //traverse through all the records of current recordset...
    long lngRec = 0;
    pRecordset = pRecordset->NextRecordset((VARIANT *)lngRec);
    //Error handling and cleanup code (like closing recordset/ connection)
    //etc are not shown here.</PRE>

    It can be linked to internal conversion. In some case, the value of internal or extranal value is not the same.
    When you run SE16 (or transaction N), you have in option mode the possibility to use the exit conversion or not.
    Christophe

  • IMGBurn updated to 2.0.0.0

    See http://www.imgburn.com/
    All-new version of the popular freeware burn utility.
    Changelog:
    * Added: 'Build' mode for creating ISO's from files on your hard disk, or burning them direct to a disc.
    * Added: Capturing Processor usage is now optional.
    * Added: Option to change the thread priority of the 'Graph Data' thread. Might give more accurate results on some PC's.
    * Added: Workaround for Windows Vista where the system tray icon wouldn't display the initial (top most) 'Restore ImgBurn' item because it had the 'Default' flag set.
    * Added: Additional variations of the 'Send Cue Sheet' command when the initial attempt fails.
    * Added: If 'Send Cue Sheet' now fails because the drive is sooooo old it doesn't support SAO burning, the program will revert to TAO.
    * Added: Option to make Verify mode just test readability of the disc itself and not verify against an image file.
    * Added: Verify mode now reports (for all modes) the file mapped to any unreadable sector at a given LBA address.
    * Added: Buffer Recovery (+ user configurable threshold settings) for times when burning and hdd goes mental, meaning device buffer empties. This means less start / stopping for the drive.
    * Added: Option to set read speed for Verify mode (any type of verify, in the case where it's being done after burn etc).
    * Added: 32bit colour Icons to the icon used for 'default' file associations.
    * Added: When the program needs another disc as part of queued burns (and it's not the foreground window), it now flashes the taskbar button.
    * Added: A rating system to the layerbreak positions/screens. Should make it easier to pick the best one.
    * Added/Changed: The 'Wait For +RW Background Format' option into a 'Prefer Properly Formatted +RW' option. When checked, the program waits for background format to finish and will also prompt to format (before writing) any disc that's in the 'Formatted: No' or 'Formatted: No (Started)' states. When unchecked, it will only prompt when in the 'Formatted: No' state (i.e. when it really has to format).
    * Added: 'Mark as Burnt' to the Queue window context menu.
    * Added: New startup screen on OS's supporting layered windows.
    * Added: A new item to the main menu called 'Output'. This is visible in ISO Build mode and lets you switch between building to an image file or doing on-the-fly to a device (drive).
    * Added: '/VOLUMELABEL' CLI parameter for ISO Build mode.
    * Added: '/NOIMAGEDETAILS' CLI parameter for use in ISO Build mode. Does the same thing at ticking 'Don't Prompt Image Details' in the settings.
    * Added: '/OVERWRITE' CLI parameter for use in ISO Build mode.
    * Added: Support for detecting device arrival / removal.
    * Added: 'Copies' to the main window - as such, logic behind queue has had to change (as has the Queue window).
    * Added: '/COPIES' CLI command for use in ISOWRITE mode.
    * Added: Ability to load/save settings to a '.ini' file. File name passed via '/SETTINGS' CLI command or will default to 'ImgBurn.ini' in the exe's directory.
    * Added: 'Eject Tray' checkbox to all the transfer screens. Whatever that box is set to is now what the program does at the end of the burn (or burn + verify).
    * Added: Additional MD5 calculations to Build/Write/Verify modes where I thought they'd be handy - logged when operation completes successfully.
    * Added: Ability to eject the tray after write ONLY when there are additional images in the queue.
    * Added: Copies + speed info to the burn progress screen.
    * Added: Support for '.IBB' files - these are plain text backup project files. See 'ReadMe.txt' for additional information.
    * Added: Support for '/FILESYSTEM' CLI command for use in ISOBUILD mode.
    * Added: Support for CloneCD's updated version of my old '.dvd' file (from DVD Dec days) where it also contains layerbreak information.
    * Added: More image info to verify / write main screens (to fill empty space!) - due to additional real estate needed for 'Build' mode.
    * Added: Files > 1GB and that have sizes divisible (exactly) by 2048 are now just always accepted for burning - regardless of presence of 'supported' filesystems in the image.
    * Added: 'ImgBurn Statistics' to the 'Help' menu.
    * Added: '/LOG' CLI switch to auto save the log to specified file (overrides setting / filename in settings window).
    * Added: '/INFO' CLI switch to save Info panel information to specified file the first time a disc is fully recognised / checked.
    * Added: The installer now writes out the options (Desktop/Quick Launch icon etc) to the registry so those options are preserved if you install again.
    * Added: Ability to Load/Eject disc from Queue window.
    * Added: Improved file association removal code within the uninstaller.
    * Added: List of (supported!) file systems used within an image to the log and to the tooltip on the volume label.
    * Added: Ability to sort the queue asc/desc by clicking on the column header.
    * Added: Workaround for some old drives that wouldn't report a disc as being erasable.
    * Added: Option to ignore IFO/Filesystem layerbreak positions and revert to VOBU/ECC scanning.
    * Added: Option to set the chosen layerbreak position as 'seamless' via a checkbox in the 'select layer break position' / 'create layer break position' dialog boxes.
    * Added: Option to tell the program NOT to update the IFO/BUP files.
    * Added: Verify mode can now collect data / produce IBG files in its own right.
    * Added/Changed: Use of ComboBoxEx for device dropdown lists when running under Vista. The standard customdraw ComboBox didn't theme properly.
    * Changed: Processor performance counters are now initialised earlier to reduce the delay when the 'GraphData' thread starts.
    * Changed: Even when you load the ISO rather than the MDS file, the MDS (with the same name) will still be deleted if you opt to delete the image.
    * Changed: IBG files are now made to version 2 specs. You'll need an updated DVDInfoPro to view them.
    * Changed: Max speed can now be 33% larger than the average value (was 20%) - otherwise it's ignored - probably a spike.
    * Changed: Shortcut keys for modes/log window/queue window have been changed - forced due to nature of keypressing in new 'Build' mode. Old shortcuts do still work for Write/Verify/Discovery modes though.
    * Changed: 'L' and 'E' on Load/Eject buttons have been replaced by some pictures.
    * Changed: Updated 'ReadMe.txt' file with new CLI stuff.
    * Changed: The little picture of the drive in the device dropdown boxes is now greyed out for all devices except the active one.
    * Fixed: Drag + Drop of some items could look like it was going to work (going by the mouse cursor) but then didn't actually do anything (Effected Build mode's 'Source' box, the 'Queue' window and the 'Create DVD MDS File' window).
    * Fixed: When setting SPLIP flag in IFO/BUP files as a result of layerbreak stuff, it now checks the previous cell doesn't have a cell command before doing so.
    * Fixed: MSF values found in the 16 byte header of some CD sectors sizes (as part of internal conversion routines) were being calculated/stored in normal decimal format, not BCD (binary coded decimal).
    * Fixed: Selecting 'Incremental' and burning a CD meant all kinds of weird things happened. As Incremental doesn't work on CD (or at least not in ImgBurn), it'll always force SAO mode burning.
    * Fixed: Transparency problem with the 48x48x32 program icon.
    * Fixed: Unfinalised multisession discs where last session was empty were reported as being totally empty - meaning the program didn't prompt to erase them - meaning the burn then failed.
    * Fixed: Couldn't open read-only files (via the 'Open' dialog box) using Windows 98.
    * Fixed: Problem with non all-numeric OS 'short dates' in IBG files. The export function would bomb out because Borland's Date/Time functions wouldn't convert the string (taken from the IBG) back into a 'TDateTime' object. i.e. '2/July/2006 12:00:00' would fail where '2/7/2006 12:00:00' would work fine.
    * Fixed: Error message boxes shown from within threads did not stop other windows from becoming inactive.
    * Fixed: Problem where freshly formatted +RW media with unreadable sectors (not normal! - probably means burn will fail anyway) was not considered as writable.
    * Fixed: (Workaround) For a problem with Borlands resource compiler where icons have their index's messed up - this stopped the icon for file associations from working properly.
    * Fixed: Problem with Queue sort order not resetting when going between 'sort by name' and 'sort by name (ignore path)'.
    * Fixed: Unnecessary creation of reg keys for file types where association was disabled.
    * Fixed: 'Standard' user accounts got errors when closing the program down (failing to set file associations) - Maybe it is just visible in Vista?
    * Fixed: Problem updating volume labels in UDF filesystem if previously there was no volume label at all.
    * Fixed: Acceleration character (an '_') was shown in the Queue window for images containing an '&' in the volume label or file name.
    * Fixed: IBG CPU % usage stats on non English PC's.
    * Fixed: Incorrect 'Start In' property for shortcuts/icons created by the installer.
    * Fixed: Incorrect conversion of UDF revision field resulted in some weird values being reported.
    * Fixed: Problem where displaying IBG file with minimum required version of DVDInfoPro would show an error.
    * Fixed: IBQ files couldn't be loaded from the CLI and still keep all the correct settings - selected device info was lost.
    * Fixed: The Log window's open/save dialog boxes used the 'filename' path (part of internal structure) as the default folder, rather than the 'initialdir' path - so they didn't default to the correct 'Most Recently Used' folder.
    * Fixed: Compressing the exe with PECompact meant the 2nd application icon was compressed and so didn't show up for associated file extensions.
    * Fixed: Deferred errors caught by the 'WaitImmediateIO' function were not being correctly copied to the parent function - this could cause a crash.
    * Fixed: File Association code wasn't clearing up the registry properly.
    * Fixed: The filesystem parsing code as part of the verify stage could attempt to read beyond the end of the image file if it was a really small image.
    How can you possibly go wrong!

    Just for the heck of it, I went into Edge and was able to retrieve e-mail for one of my accounts. Don't really understand what 2.0.2 was designed to do.
    From my purely anecdotal experience, I think it's designed to display more bars on the screen Kind of like a Potemkin phone ...
    Well, it's been confirmed. As I type this, I have now received e-mail from both of my accounts ... on Edge ...
    I guess it's back to the drawing board for Apple and AT&T.

  • WEBI report on a Universe - Time Format

    Hi,
    I have a WEBI report built on a universe that uses a BW query as a datasource.
    In my BW report I have two time key figures of type DEC.
    Actual Time and Scheduled Time in format HH:MM:SS or -HH:MM:SS if it is a negative value. It works well in Bex and RSRT.
    There is a Universe report built on top of this report and my WEBI report is built on the universe.
    When I run the WEBI report the time key figures display in the format 10,000 in BO instead of 01:00:00 (HH:MM:SS) as it is in Bex. It is obviously doing some type of internal conversion and outputting the wrong result.
    Is there a way to convert the field in BO so that it outputs the same as Bw format?
    I have tried changing the universe format properties of the field from Number to Character and back again but it does not give me any different result and in some cases it displays as #DataType.
    Any suggestions welcome.
    BO Version 3.1
    BW Version 7.01
    Regards,
    John

    If you select "Date/Time" in the format then select the time field, does this work for you?
    It should be HH:mm:ss  (capitalization matters).
    I don't have a BW sample currently available to test so this screenshot is from an Oracle data source.
    Also, are you able to set the object to a Date type?
    - Carly

  • What is a Profile Mismatch and why does it always show up?

    b Question
    Every time I open a file I get a prompt which reads: Embedded Profile Mismatch.
    Embedded: Camera RGB Profile
    Working: Adobe RGB (1998)
    I always choose the default, which is the "embedded profile (instead of working space).
    I have no idea what any of this means. I know that it started doing this after I chose something recommended in a Photoshop book.
    Can someone please show me how to get rid of this prompt and point me in the direction of information that will help me choose the best profile?
    b Answer supplied by Richard Rose
    First the good news - your work flow is Color Managed.
    Now the bad news - You have no idea what that means, nor how you are achieving that desirable situation.
    You really need to start at the beginning and learn what color management is all about. For some reason lots of people get very confused and mislead trying to wrap their brains around the subject. It's really quite simple.
    There are many named "color spaces" in which to work in Photoshop. you have chosen Adobe RGB (1998). You chose that color space in Photoshop CS under "Color Settings."
    That's a good "general purpose" color space to use. It's very useful for workers preparing images intended for color reproduction in print (on a printing press). But it'll do for almost any use you have for your images. If your images are destined mostly for the Web, working in sRGB might be good. (I recommend just staying in Adobe RGB 1998)
    The "short answer" as to why Photoshop needs to work in some particular "color space" is that the program must "translate" colors from their source (a digital camera, a scanner, a a graphics program) into a destination (display on a computer monitor screen, a particular printer, output for printing press reproduction, etc).
    There are many compromises that take place in that translation process, and the requirements for all the possible conditions that must be satisfied (hue, saturation, how light or dark the image appears) cannot always be met. Something has to give somewhere.
    Named color spaces (Adobe RGB, sRGB, Color Match RGB, Ekta Space, etc) make a number of assumptions and decisions about how color translations (conversions) should be carried out before Photoshop ever gets its hands on the image, and makes it much easier for Photoshop to carry out the conversions and maintain accuracy in converting (for instance) from a digital camera's idea of an image to the needs of your computer monitor (so you can see an accurate resemblance of the image) to the needs of a printing press, so that the image looks correct in a magazine.
    The conversion process is carried out with the aid of "profiles." A profile is a set of data that is embedded in an image file that describes to any program that wants to read it, what the image data means in terms of color.
    Without the profile, your digital camera's RGB file simply contains arbitrary RGB values. Yes, a particular pixel with high R values will be reddish, and another pixel with high B values will be blue, but the actual red or blue of those pixels as they relate to the original scene is unknown. The camera profile embedded in your file lets Photoshop know, to a high level of accuracy, just what hue of red, and just how much saturation is present, and how light or dark the red was in the scene. The profile's coding of this information is based on a color measurement system called CIE which uses several different mathematical models to carry out some VERY complicated computations. There are CIE Lab models, CIE XYZ, and others. These models are as close to an "absolute" color reference system as we have.
    Thank God you are using camera files that actually have profiles! When you open such a file, Photoshop is "warning" you that the image information is in a color space other than the default Adobe RGB space. You told Photoshop to warn you about such "mismatch" when you set Color Management Policies in the Color Settings section.
    Photoshop is telling you that "something" needs to be done. It can honor the camera's color space, from it's own frame of reference (Adobe RGB 1998) and work on the image, accurately handling the color information for screen display and eventual output. That's what you tell it to do when you "accept" the embedded profile. That's not bad, everything will work correctly, because Photoshop will have made internal conversions that remain active as long as the file is open, but there is something you have to keep in mind - when you save the file, Photoshop will save the original camera profile with it. Then if you open the file again, the same "warning" will occur.
    That camera profile is as valid and useful as any other profile, but because it is not a commonly recognized color space may cause a problem in some other workflow. (Notice I said MAY. ICC color profiles SHOULD be ok in any program)
    It is probably better to choose "Convert to working profile" on opening the file. From that point on, nothing will appear different to you, because nothing has really changed. Photoshop will handle the file as it did before, internally converting the color information as necessary with regard to its working space. But when you save the file, the Adobe RGB 1998 profile will be embedded in it. If you re-open it, you will get no mismatch warning, and the file will be recognized by most other image handling programs as having a "standard" color space.

    Thanks! I still don't understand the concept of "saving power" in this context. Does that relate to a laptop running on battery, and some popups consume more battery power? Or does this refer to CPU capacity?  I have never had any issue that I know of in these areas. I would understand the warning if it cautioned me about insufficient bandwidth, but that doesn't seem to apply here. In any case, am glad to find that this is a feature and not a bug.
    Stan

Maybe you are looking for