Alternative function to WM_CONCAT

Hi,
I am using eBusiness Suite 11g containing an Oracle financials 10 database. The schema WMSYS is missing and I am unable to use WM_CONCAT function. Are there any other alternative functions or SQL that can help with cross-tabbing comma seperated values to avoid queries returning multiple lines.
For example:
JE_HEADER_ID SOURCE INVOICE_NUM DESC PO_NO AMOUNT
14055 Payables 38761 Paperchase 10145 461.55
14055 Payables 38761 Paperchase 10148 461.55
I would like the PO_NO to be concatenated on one line so that the query returns only one line as below:
JE_HEADER_ID SOURCE INVOICE_NUM DESC PO_NO AMOUNT
14055 Payables 38761 Paperchase 10145, 10148 461.55
Your feedback will be appreciated.
Thanks

Hi,
Thanks for your help, rtrim(xmlagg(xmlelement(e,ph.segment1,',').extract('//text()')),',') segment1 seems to work best in eBusiness suite with database version 10. The function LISTAGG works from 11g onwards and STRAGG requires a functions to be created and called within a SQL query.
All of the above were useful to know.
Thanks again

Similar Messages

Alternative Function module in ECC 6.0

Hi,
The function module FI_DOCUMENT_ARCH_JUMP_HEAD_SGL and FI_DOCUMENT_ARCH_READ_DETAILS is available in 4.6c but is not available in ECC 6.0.
I have to import a progam from 4.6 to ECC 6.0.with uses this function module .
Please let me know alternative function module in ECC 6.0
Thanks
Deepa

That's why it's never recommended to use the FMs that have not been released to the customer... You might be able to copy FMs as Z... objects from 4.6 into ECC 6.0. However, it's possible that underlying functionality has changed a lot and it just won't work.
Instead of asking for a replacement FM you might want to explain what exactly you're trying to achieve, then someone might be able to provide an alternative (not necessarily an FM).

Any function like WM_CONCATE in webi 4.0?

Hi ,
I am trying to have different values coming from the same column in DB , to accumulate in one cell and also wanna concatenate it
For Example ,
Country
Projects
USA
111
USA
1222
USA
3333
want to show the above as in one cell
USA 111,1222,3333
I know it can be done at DB level by WM_CONCATE but how to do it in Webi 4.0?

Hello Usman,
PFB a useful link where a similar requirement has been explained well.
http://bi.srivatsakr.com/2011/08/converting-rows-into-single-cell-comma.html
Hope it helps
Regards,
Nikhil Joy

Calling alternating functions

I have two functions called functionA() and functinoB(). As
the play head travels down the timeline I'd like to call
functionA() on frame 100, functionB() on frame 200, functionA() on
300, functionB() on 400 and so on. However, instead of having to
type functionA() or functionB() in the keyframe, I'd like to just
type functionCaller() and have some logic in that function that
would call the appropriate function based on the last function
called. I've tried an if/else function based on a variable I change
back and forth as each function runs, but it just keeps choosing
functionA() over and over. Any suggestions?
--gw

You still want to put the functionCaller call in the keyframe
(not in an onEnterFrame handler) ? If so:
function functionCaller() {
if ((_currentframe/100)%2 !=0) {
functionA()
} else {
functionB()
}

Alternative function to WS_DELIVERY_UPDATE

Hi all,
I would like to Assign business partner & delivery to HU (Handling Unit).
I'm using fm : WS_DELIVERY_UPDATE but dont get the expected results.
Is there any other FM/Bapi that could do the job ?
Thanks
Ziv.

Hi,
Have a look at the documentation for the FM
Changes in supply
With this function module delivery are subject to change. The device can perform updates from picking on Kommissionierbelegflüsse (volumes & weights) when sitting UPDATE_PICKING parameters and quantities, weight and volume updates without Kommissionierflüsse if UPDATE_PICKING sits on SPACE. In this case, there is only one Einmalrückmeldung at any position. In VBPOK and VBKOK there are control parameters do, what changes will be implemented. Kommimengenänderungen are always in base unit number, quantity changes are always conducted in unit sales volume of the delivery position.
When not working on Kommissionierrückmeldung, all information must be given to a delivery position in the call, subsets and weight returns are not possible.
In the case of batches can be returned several records with different batches of VBPOK-POSNR_VL. The fields in the Include VBPOKKOMMI within the structure VBPOK) are only for the case of Kommissionierrückmeldung with the use of Kommissionierbelegflüssen relevant (eg WM transfer order confirmation.
The caller must evaluate both the log table PROT as well as the EXCEPTIONS OTHERS ERROR_MESSAHE and intercept.
Regards,
Lakshman.

Upload data from excel with vba by calling a function module

Hello all,
i have a problem with the function module "ALSM_EXCEL_TO_INTERNAL_TABLE". I will call this function module with vba to load data from excel to sap with a Buttonclick. I have copied this function module and set it remotable. But i can´t call it from excel.
Can you give me some tips how can i
upload data from excel with vba by click a button.
The problem seems the function: call method cl_gui_frontend_services=>clipboard_import in the function module, because when i comment this function call the vba-call is true but no results.
How can I call the function module correct with vba?
Thanks a lot for your tips!!!!
Chris
Message was edited by:
        Christoph Kirschner

HI
Uploading data directly from Excel file format
* Upload data direct from excel.xls file to SAP
REPORT ZEXCELUPLOAD.
PARAMETERS: filename LIKE rlgrap-filename MEMORY ID M01,
            begcol TYPE i DEFAULT 1 NO-DISPLAY,
            begrow TYPE i DEFAULT 1 NO-DISPLAY,
            endcol TYPE i DEFAULT 100 NO-DISPLAY,
            endrow TYPE i DEFAULT 32000 NO-DISPLAY.
* Tick don't append header
PARAMETERS: kzheader AS CHECKBOX.
DATA: BEGIN OF intern OCCURS 0.
        INCLUDE STRUCTURE alsmex_tabline.
DATA: END OF intern.
DATA: BEGIN OF intern1 OCCURS 0.
        INCLUDE STRUCTURE alsmex_tabline.
DATA: END OF intern1.
DATA: BEGIN OF t_col OCCURS 0,
       col LIKE alsmex_tabline-col,
       size TYPE i.
DATA: END OF t_col.
DATA: zwlen TYPE i,
      zwlines TYPE i.
DATA: BEGIN OF fieldnames OCCURS 3,
        title(60),
        table(6),
        field(10),
        kz(1),
      END OF fieldnames.
* No of columns
DATA: BEGIN OF data_tab OCCURS 0,
       value_0001(50),
       value_0002(50),
       value_0003(50),
       value_0004(50),
       value_0005(50),
       value_0006(50),
       value_0007(50),
       value_0008(50),
       value_0009(50),
       value_0010(50),
       value_0011(50),
       value_0012(50),
       value_0013(50),
       value_0014(50),
       value_0015(50),
       value_0016(50),
       value_0017(50),
       value_0018(50),
       value_0019(50),
       value_0020(50),
       value_0021(50),
       value_0022(50),
       value_0023(50),
       value_0024(50),
       value_0025(50),
       value_0026(50),
       value_0027(50),
       value_0028(50),
       value_0029(50),
       value_0030(50),
       value_0031(50),
       value_0032(50),
       value_0033(50),
       value_0034(50),
       value_0035(50),
       value_0036(50),
       value_0037(50),
       value_0038(50),
       value_0039(50),
       value_0040(50),
       value_0041(50),
       value_0042(50),
       value_0043(50),
       value_0044(50),
       value_0045(50),
       value_0046(50),
       value_0047(50),
       value_0048(50),
       value_0049(50),
       value_0050(50),
       value_0051(50),
       value_0052(50),
       value_0053(50),
       value_0054(50),
       value_0055(50),
       value_0056(50),
       value_0057(50),
       value_0058(50),
       value_0059(50),
       value_0060(50),
       value_0061(50),
       value_0062(50),
       value_0063(50),
       value_0064(50),
       value_0065(50),
       value_0066(50),
       value_0067(50),
       value_0068(50),
       value_0069(50),
       value_0070(50),
       value_0071(50),
       value_0072(50),
       value_0073(50),
       value_0074(50),
       value_0075(50),
       value_0076(50),
       value_0077(50),
       value_0078(50),
       value_0079(50),
       value_0080(50),
       value_0081(50),
       value_0082(50),
       value_0083(50),
       value_0084(50),
       value_0085(50),
       value_0086(50),
       value_0087(50),
       value_0088(50),
       value_0089(50),
       value_0090(50),
       value_0091(50),
       value_0092(50),
       value_0093(50),
       value_0094(50),
       value_0095(50),
       value_0096(50),
       value_0097(50),
       value_0098(50),
       value_0099(50),
       value_0100(50).
DATA: END OF data_tab.
DATA: tind(4) TYPE n.
DATA: zwfeld(19).
FIELD-SYMBOLS: <fs1>.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR filename.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
       EXPORTING
            mask      = '*.xls'
            static    = 'X'
       CHANGING
            file_name = filename.
START-OF-SELECTION.
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
       EXPORTING
            filename                = filename
            i_begin_col             = begcol
            i_begin_row             = begrow
            i_end_col               = endcol
            i_end_row               = endrow
       TABLES
            intern                  = intern
       EXCEPTIONS
            inconsistent_parameters = 1
            upload_ole              = 2
            OTHERS                  = 3.
IF sy-subrc <> 0.
    WRITE:/ 'Upload Error ', SY-SUBRC.
ENDIF.
END-OF-SELECTION.
LOOP AT intern.
    intern1 = intern.
    CLEAR intern1-row.
    APPEND intern1.
ENDLOOP.
SORT intern1 BY col.
LOOP AT intern1.
    AT NEW col.
      t_col-col = intern1-col.
      APPEND t_col.
    ENDAT.
    zwlen = strlen( intern1-value ).
    READ TABLE t_col WITH KEY col = intern1-col.
    IF sy-subrc EQ 0.
      IF zwlen > t_col-size.
        t_col-size = zwlen.
*                          Internal Table, Current Row Index
        MODIFY t_col INDEX sy-tabix.
      ENDIF.
    ENDIF.
ENDLOOP.
DESCRIBE TABLE t_col LINES zwlines.
SORT intern BY row col.
IF kzheader = 'X'.
    LOOP AT intern.
      fieldnames-title = intern-value.
      APPEND fieldnames.
      AT END OF row.
        EXIT.
      ENDAT.
    ENDLOOP.
ELSE.
    DO zwlines TIMES.
      WRITE sy-index TO fieldnames-title.
      APPEND fieldnames.
    ENDDO.
ENDIF.
SORT intern BY row col.
LOOP AT intern.
    IF kzheader = 'X'
    AND intern-row = 1.
      CONTINUE.
    ENDIF.
    tind = intern-col.
    CONCATENATE 'DATA_TAB-VALUE_' tind INTO zwfeld.
    ASSIGN (zwfeld) TO <fs1>.
    <fs1> = intern-value.
    AT END OF row.
      APPEND data_tab.
      CLEAR data_tab.
    ENDAT.
ENDLOOP.
CALL FUNCTION 'DISPLAY_BASIC_LIST'
       EXPORTING
            file_name     = filename
       TABLES
            data_tab      = data_tab
            fieldname_tab = fieldnames.
*-- End of Program
<b>Excel Upload Alternative - KCD_EXCEL_OLE_TO_INT_CONVERT</b>
*Title : Excel Uploading
TYPES:   BEGIN OF t_datatab,
         col1(25) TYPE c,
         col2(30) TYPE c,
         col3(30) TYPE c,
         col4(30) TYPE c,
         col5(30) TYPE c,
         col6(30) TYPE c,
         col7(30) TYPE c,
         col8(30) TYPE c,
         col9(30) TYPE c,
         col10(30) TYPE c,
         col11(30)    TYPE c,
       END OF t_datatab.
DATA: it_datatab TYPE STANDARD TABLE OF t_datatab INITIAL SIZE 0,
      wa_datatab TYPE t_datatab.
Data : p_table type t_datatab occurs 0 with header line.
DATA : gd_scol   TYPE i VALUE '1',
       gd_srow   TYPE i VALUE '1',
       gd_ecol   TYPE i VALUE '256',
       gd_erow   TYPE i VALUE '65536'.
DATA: it_tab TYPE filetable,
      gd_subrc TYPE i.
field-symbols : <fs>.
*Selection screen definition
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
PARAMETERS: p_file LIKE rlgrap-filename
               DEFAULT 'c:test.xls' OBLIGATORY.   " File Name
SELECTION-SCREEN END OF BLOCK b1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
REFRESH: it_tab.
CALL METHOD cl_gui_frontend_services=>file_open_dialog
    EXPORTING
      window_title     = 'Select File'
      default_filename = '*.xls'
      multiselection   = ' '
    CHANGING
      file_table       = it_tab
      rc               = gd_subrc.
LOOP AT it_tab INTO p_file.
*    so_fpath-sign = 'I'.
*    so_fpath-option = 'EQ'.
*    append so_fpath.
ENDLOOP.
START-OF-SELECTION.
PERFORM upload_excel_file TABLES   it_datatab
                             USING   p_file
                                     gd_scol
                                     gd_srow
                                     gd_ecol
                                     gd_erow.
* END-OF-SELECTION.
END-OF-SELECTION.
LOOP AT it_datatab INTO wa_datatab.
    WRITE:/ wa_datatab-col1,
            wa_datatab-col2,
            wa_datatab-col3,
            wa_datatab-col4,
            wa_datatab-col5,
            wa_datatab-col6,
            wa_datatab-col7,
            wa_datatab-col8,
            wa_datatab-col9,
            wa_datatab-col10,
            wa_datatab-col11.
ENDLOOP.
*&      Form UPLOAD_EXCEL_FILE
*       upload excel spreadsheet into internal table
*      -->P_TABLE    Table to return excel data into
*      -->P_FILE     file name and path
*      -->P_SCOL     start column
*      -->P_SROW     start row
*      -->P_ECOL     end column
*      -->P_EROW     end row
FORM upload_excel_file TABLES   p_table
                       USING    p_file
                                p_scol
                                p_srow
                                p_ecol
                                p_erow.
DATA : lt_intern TYPE kcde_cells OCCURS 0 WITH HEADER LINE.
* Has the following format:
*             Row number   | Colum Number   |   Value
*      i.e.     1                 1             Name1
*               2                 1             Joe
DATA : ld_index TYPE i.
* Note: Alternative function module - 'ALSM_EXCEL_TO_INTERNAL_TABLE'
CALL FUNCTION 'KCD_EXCEL_OLE_TO_INT_CONVERT'
    EXPORTING
      filename                = p_file
      i_begin_col             = p_scol
      i_begin_row             = p_srow
      i_end_col               = p_ecol
      i_end_row               = p_erow
    TABLES
      intern                  = LT_INTERN
    EXCEPTIONS
      inconsistent_parameters = 1
      upload_ole              = 2
      OTHERS                  = 3.
IF sy-subrc <> 0.
    FORMAT COLOR COL_BACKGROUND INTENSIFIED.
    WRITE:/ 'Error Uploading file'.
    EXIT.
ENDIF.
IF lt_intern[] IS INITIAL.
    FORMAT COLOR COL_BACKGROUND INTENSIFIED.
    WRITE:/ 'No Data Uploaded'.
    EXIT.
ELSE.
    SORT lt_intern BY row col.
    LOOP AT lt_intern.
     MOVE lt_intern-col TO ld_index.
     assign component ld_index of structure
     p_table to <fs>.
move : lt_intern-value to <fs>.
*     MOVE lt_intern-value TO p_table.
      AT END OF row.
        APPEND p_table.
        CLEAR p_table.
      ENDAT.
    ENDLOOP.
ENDIF.
ENDFORM.                    "UPLOAD_EXCEL_FILE
Regards
Pavan

MySAP replacements for Excel upload function modules?

I am doing some development in SRM 4.0 (WAS 640) and I notice that a few of my favorite function modules are no longer available. Specifically, I'm missing these the most:
KCD_EXCEL_OLE_TO_INT_CONVERT
ALSM_EXCEL_TO_INTERNAL_TABLE
Are there new equivalents? I know how to access XLS files by writing my own OLE calls, but sometimes it's just easier to use the standard function modules instead.
Yes, I've done a function module search, but I've found nothing that looks to the the same as my old friends.

Hi Chris,
I can't give you an alternative function module per say. Obviously, the downside of using SAP functions, that were probably never released for customer consumption anyway is that they can easily disappear. The suggestion I have is to use the features offered by DOI (desktop office integration). There in lies a set of classes and methods for generically accessing various documents (e.g. ms word, excel etc.) There is some examples in the re-use library (tcode se83). So here you don't need to be worried about the OLE either. Possibly in WAS there might also be some other classes that might access Excel sheets. Downside of finding a new function is that it might disappear in the next version you go to, whereas DOI is unlikey to disappear in a hurry. Best of luck.
p.s. there are a few other postings in the forum, maybe one will give you an answer, if you haven't search already.
Message was edited by: Michael Bennett

BAPI Function taking too much time

Hi,
One BAPI function BAPI_INCOMINGINVOICE_CREATE
taking too much time to process the data. do we have any alternative to reduce the time taken by the BAPI function ?
like by using any SAP Notes or any other alternative function or by any other way.
Thanks and regards,
Shailendra

HI,
Please apply the OSS Note 830717. I applied this note and ran transaction code FBZ0 and the "withholding tax code" changed from XX to 03.
Reward if helpful

How To Use Exported Function "CallInstrument" of LabView.exe ?

Hello!
I want to use the function "CallInstrument" to dynamically call VIs with LabView. Did anyone has experiences with this function?
All I kow is following:
The function is used by LabView Internals and its Runtime Library. Its exported by LabView.Exe and lvrt.dll.
Its prototype is maybe:
int CallInstrument(CPStr* VIPath, int controlcount, int indicatorcount, int options, [ Variable List of Control/Indicator Parameters ]... );
( CPStr Type is a StringArray of PStr (Short PascalStrings) as it is used by LabView to store Path datatypes. )
I whould be glad, if anyone has information about this function.

Dear Rolf Kalbermatter,
Thirst, thanks a lot for your answer! -
You sure right, It whould be much much more comfortable to use the VI Server.
And you're also right... using a undocumented dll-function is absolutly no longtime solution.
Currently I am using VI Server for my problem, but it doesn't fit my interesst so much.
But I will explain, what I'm trying to do.
I want to call a VI dynamically from LabView, giving Parameters to its Controls and receive Results from its Indicators.
Realy no big job, but VI Server only let you do this that easy if you have a VI Typedef. otherwise... with untyped VIs, its not that simple. Ok.. its not impossible, you can use "GetAllControlValues" and "SetControlValue" (functions from VI server) and the call "RunVi". But this can get slow (>100ms per call :/ )
I'm looking for a alternative function, which let me call a VI dynamically with userdefined Parameters. Maybe you know the ActiveX Interface IVirtualInstrument and its Function "Call2" - it is a nice example, what kind of function i want.
But this function is not directly available by the VI Server--- i don't know for what reason.
Then i tried to make use of "Call2" from within LabView, and it took me some time to find out the right Parametersyntax but finnaly i got it and it worked fine ... but it was no long time until problems occur. I cannot tell what really went wrong, but sometimes labview simply crashed or hang into a loop reseting some VIs. And its also impossible to stop a running vi, with has made a call to "Call2", if the call doesn't return by itself.
Next step is/was trying to take advantage of CallInstrument. So, yesterday... after hours of analysing assemblercode, i finnally found out the correct use of LabView.exe->CallInstrument and i'm very impressed about its speed (0-15ms per call). The prototype seem to be the same as you explained in your reply int CallInstrument(Path path, Bool modal, int32 nInputs, int32 nOutputs, ...)
But It has the same problem as its ActiveX derivat "Call2".. if you call an endless looping VI, LabView cannot stop your caller-vi. The other bad thing is, that this function is using dynamic paramterlist, which are placed directly onto the stack!
That means that the paramter count on the stack is NOT FIXED (printf makes it the same). LabVIews DLL InvokeNode doesn't support this.
At my current position, it looks like i have three possiblities but no one fits into my interesst.
(continued with next answer)

Using 'SYSDATE' function in ACCESS 2000?

'SYSDATE' function is not working in ACCESS 2000 , is there any other
alternative function available in access.
I use a select statement using SYSDATE, but it did not work.

I found it already.
use the now() function.

Obsolete Function Modules in ECC 6.0

hi all,
Can anyone provide me alternative function modules or Methods for below mentioned FM.
WS_QUERY
WS_ULDL_PATH
WLK1_CHECK
CARD_CHARACTERISTIC_READ
F4_SEARCH_HELP
WS_EXCEL
Regards,
Anurag

Go to SE37. Enter the name of the obsolete function module - e.g. WS_QUERY
Click on "Function Module Documentation". This will tell you where to find the replacement.
If that doesn't help, look at class CL_GUI_FRONTEND_SERVICES.
matt

Report to find function module names

Hi all,
My requirement is to get generate a report with the list of obsolete function modules and the SAP recommended function module equivalent to it. i have identified the table to get the obsolete function module . I m not able to get the function module equivalent to tithe obsolete function module.
Thanks
siva

Hi Sivaprasath,
U might have referred RODIR table for finding out function modules which are obsolete.
To find the replacement of obsolete function modules check OSS notes in service.sap.com with search string as the name
of the function module.
U will get Related notes where u can get the alternative FM.
Also check the documentation of obsolete FM,Else check the short description.It might be mentioned there itself for Alternative Function Module.
Regards,
Lakshman.

Function MM_DELIVERY_ADDRESS_READ in PO print program

Hello everybody,
I'm using the function module MM_DELIVERY_ADDRESS_READ in a copy of the PO printing function group MEDRUCK to get the address number or address handle of an PO item. This works well in the preview of the messages but the problem is, that the function module doesn't seem to work for new messages, which are inserted and saved in the PO?
Does anybody know a fix for this problem or an alternative function module I can use?
Thanks
Daniel

Hi
Analyse the Dump in ST22 transaction
difficult to say , as what was changed in the program is not known exactly
from the dump you have to know
Regards
Anji

Extended Rebates Manual Accruals alternative

Hello to all,
We are implementing extended rebates Solution in our Company.
After reading some threads and notes, the cocnlusio is that Manual accruals functionality should not used in the
extended rebates processing.
However we have also agreements active in our system that we are using manual accruals.
For example a case of agreements for fixed amount of 12000Eur per year to customer.
In this case we post manually acrruals of 1000Eur per month.
In the extended rebates solution we have not this function possible.
Do you know why and if any alternative functionality is available?
Thanks and Regards,

Hello to all,
We are implementing extended rebates Solution in our Company.
After reading some threads and notes, the cocnlusio is that Manual accruals functionality should not used in the
extended rebates processing.
However we have also agreements active in our system that we are using manual accruals.
For example a case of agreements for fixed amount of 12000Eur per year to customer.
In this case we post manually acrruals of 1000Eur per month.
In the extended rebates solution we have not this function possible.
Do you know why and if any alternative functionality is available?
Thanks and Regards,

Alternative fuvtion module for read_text

hi all,
is there any alternative function module for read_text
regards
siva

Hi,
Check out these related threads
Re: read_text
READ_TEXT function module

Alternative function to WM_CONCAT

Similar Messages

Maybe you are looking for