Problem in the function module HAZMAT_PRI_DATA_GET

hi all ,
This is related to the shipment.
we are trying to print a form with details of dangerous goods
but function module HAZMAT_PRI_DATA_GET not returning values of the dangerous goods details when the MOT is 05 ie; air .
The function module is a standard one,Is there any SAP-note for this ?
thanks in advance,
Naval Bhatt

Dear All,
When i am using the Function module Table Parameters in the Tab strip, i am getting this error, " Table Parameters are obsolete". My requirement is to get the list of employees which will be more than one. so how can i catch the employee list.
Thanks
Yogesh

Similar Messages

Problem with the function module SO_DOCUMENT_SEND_API1

Hi Friends,
I am facing the problem wiht the function module SO_DOCUMENT_SEND_API1,
My actull requirement is : - i need to send the sap data to my externa mail id (Like as XYZ@) with out the any attachment , So i have implemented the code with the function module SO_DOCUMENT_SEND_API1.
The mail has successfully sent the sap inbox (SOST) but the mail are not reached to the external mail ID'S( XYZ@GMAIL)
i Have maintained my code lines same as below.
CALL FUNCTION 'SO_DOCUMENT_SEND_API1'
    EXPORTING
      document_data = wa_doc_data
      put_in_outbox = ca_x
      commit_work   = ca_x
    TABLES
      packing_list = tb_packing_list
      contents_txt = tb_mailbody
      receivers     = tb_receiver.
Can you please tell me soultion ,
Thanks
charan.

Hi charan,
                  If u r able to see the mail in sost, then i think ur code has worked fine. if the mail is not going to outside domains from sost u need to do some configurations for that, u can find lots of configuration docs regarding mail setup in sap.
once try to pass below parameter also.
t_receivers1-rec_type = 'U'.
For configuring mail setup u need to sit with ur basis guy.
Moderator message: please do not use SMS speak.
Edited by: Thomas Zloch on Nov 23, 2010 5:51 PM

Problem in the Function module

Dear All,
I am using the ECC 6.0 with all the service packs applied. when i am creating a function module, i am getting an error like " Tables parameters are obsolete". My requirement is to get the internal table structure what should i do???
Thanks in Advance.
Yogesh.

Dear All,
When i am using the Function module Table Parameters in the Tab strip, i am getting this error, " Table Parameters are obsolete". My requirement is to get the list of employees which will be more than one. so how can i catch the employee list.
Thanks
Yogesh

Problem in the function module RS_SET_SELSCREEN_STATUS-urgent

HI ALL,
my rewuirement is i need to display my own pf status in selection screen.
when i am using below code i getting two buttons only.anybody can tell me where i made a mistake.
i am sendingf my code below.
TABLES : ZUSER_SECOBJECTS, SSCRFIELDS.
DATA : IT_sECOBJECTS LIKE ZUSER_SECOBJECTS OCCURS 0 WITH HEADER LINE.
data: begin of exclude occurs 0,
        func(10) type c,
      end of exclude.
PARAMETER : P_KUNNR LIKE KNA1-KUNNR.
CASE sscrfields-ucomm.
WHEN 'BACK' or 'EXIT'.
SET SCREEN 0.
LEAVE SCREEN.
WHEN 'EXECUTE'.
LEAVE TO LIST-PROCESSING .    "<--- RIGHT HERE
SELECT * FROM ZUSER_SECOBJECTS
INTO TABLE IT_SECOBJECTS.
*CHECK SY-SUBRC EQ 0.
*LOOP AT IT_SECOBJECTS.
*WRITE : IT_SECOBJECTS.
*ENDLOOP.
ENDCASE.
at selection-screen output.
if sy-dynnr eq '1000'.
call function 'RS_SET_SELSCREEN_STATUS'
    exporting
      p_status = 'SELK1'
    tables
      p_exclude = exclude
    exceptions
      others    = 1.
ENDIF.
thanks,
maheedhar.t

Hi,
check this....
REPORT demo_sel_screen_status.
DATA itab TYPE TABLE OF sy-ucomm.
PARAMETERS test(10) TYPE c.
AT SELECTION-SCREEN OUTPUT.
APPEND: 'PRIN' TO itab,
          'SPOS' TO itab.
CALL FUNCTION 'RS_SET_SELSCREEN_STATUS'
       EXPORTING
            p_status = sy-pfkey
       TABLES
            p_exclude = itab.
regards,
navjot
reawrd if helpfull

Problem in using function module parameters in abap program

i want to use the coding present in on one of the function module 'AS_API_INFOSTRUC_FIND' i got the problem using the function module parameters in my abap program.
these are the parameters inside fm
""Lokale Schnittstelle:
*"       IMPORTING
*"             VALUE(I_FIELDCAT) TYPE AIND_FCAT
*"             VALUE(I_FIELDS) TYPE TABLE OPTIONAL
*"             VALUE(I_OBLIGATORY_FIELDS) TYPE TABLE OPTIONAL
*"       EXPORTING
*"             VALUE(E_INFOSTRUC) TYPE AIND_DESC
*"             REFERENCE(E_ALL_FIELDS) TYPE TABLE
*"             REFERENCE(E_MATCHING_FIELDS) TYPE TABLE
*"       EXCEPTIONS
*"              NO_INFOSTRUC_FOUND
i want to declare     E_ALL_FIELDS parameter    in my abap program,
i have declared as
data: E_ALL_FIELDS TYPE TABLE.
but   the system throws error that
'type of field 'TABLE' is generic .no table line has been specified'.
i want to use it in my abap program how can i declare in my abap program .

You have to declare the table using any specific type.
The type table in the FM is generic so you can pass any type you need.
For instance:
TYPES: BEGIN OF ty_fields,
         fieldname LIKE dfies-fieldname,
       END OF ty_fields,
TYPES: TY_T_GLU1              LIKE GLU1                     OCCURS 0,
       ty_t_fields            type ty_fields                occurs 0.
DATA: lt_info_struct_fields TYPE ty_t_fields WITH HEADER LINE,
        lt_matching_fields    TYPE ty_t_fields WITH HEADER LINE.
    CALL FUNCTION 'AS_API_INFOSTRUC_FIND'
         EXPORTING
              i_fieldcat         = ft_fieldcat-fieldcat
              i_fields           = ft_fields_filled[]
         IMPORTING
              e_infostruc        = lv_info_struct_name
              e_all_fields       = lt_info_struct_fields[]
              e_matching_fields = lt_matching_fields[]
         EXCEPTIONS
              no_infostruc_found = 1.

Problem in transfer rules-- Calling the function module.

Hi All,
when we r extracting the data from r3, the infoobject 0wbs_elem the data pulled is in internal format in which wbs element is stored.
wbs element gets stored in a different way compared to front end.
Eg. The external format is /abc/123 the internal format is 00012300.
I have written a transfer routine using the function module CONVERSION_EXIT_ABPSP_OUTPUT.
the code goes like this
data ifield(30) type c.
call function CONVERSION_EXIT_ABPSP_OUTPUT
Exporting
input = tran_structure-wbselem (Field in transfer structure---name of the field in source system) .
Importing
output = ifield.
result = ifield.
End of code.
Problem
When I am Scheduling the package the job doesnt get completed for a long time and fails.Is there a problem with the code. When trying for the Simulation of the datapackets, the system says no data package number could be determined.
Please help me out...
Thank You
Mahesh

Hi Mahesh,
Could you please check ST22 and see if there is any short dumps ?
try to do test run for the FMs using SE37 and see what is the output for your input.
Do you have PSA for the load ? It may also have been deleted. You get this message when there is no PSA available.
hope it helps
Thanks
Soumya

Problem with i_buffer_active in the function module

i_buffer_active in the function module "REUSE_ALV_FIELDCATALOG_MERGE"
hi folks,
i am using this function module "REUSE_ALV_FIELDCATALOG_MERGE" to develop a field catalog....but teh problem is that when i use this i_buffer_active and if a assign value 'X' to that parameter .......teh entire structure is not getting copied in to teh field catalog ...........and when i comment the line i_buffer active ........teh entire structure i sgetting copied ..........so can u guys please with ur valuable suggestion, the program name is RFITEMAP

Hi!
Check out the program BCALV_TEST_BUFFER.
Regards
Tamá

Problem in copying the function module.

Hi All,
I have to Copy the standard function modules "FI_ITEMS_DISPLAY" and "ITEM_DERIVE_FIELDS".
The Function group for both of above FM is "FI_ITEMS".
What i did is I went to SE80 ,I copied down the Function Group 'FI_ITEMS' to 'ZFI_ITEMS'.
later on i copied the standard function modules 'FI_ITEMS_DISPLAY' and 'ITEM_DERIVE_FIELDS'
to the 'ZFI_ITEMS_DISPLAY' and 'ZITEM_DERIVE_FIELDS' resp.in the same function group 'ZFI_ITEMS'.
Then i made some changes to these copied modules (I did change the structure of it_items from RFPOSXEXT to ZRFPOSXEXT in ZFI_ITEM_ITEM_DISPLAY,and same change in ZITEM_DERIVE_FIELDS but for the parameter s_item).
And finally i activated these FM..and it got activated also.
But later on when i used these FM in my report...error occured saying that -
"The name of the function module to be called is "ZITEM_DERIVE_FIELDS".
but "ZITEM_DERIVE_FIELDS" cannot be found in its function group. "
hence i thought of activating the function group ZFI_ITEMS,which was inactive before to this...but when i tried activatin this FM it was giving hell lot of errors showing conflict occured at diffrent places,I think just because of the change (structure of IT_ITEM chnged from RFPOSEXT to customised ZZRFPOSXEXT).
I am helpless in removing all this errors ...
Can anybody suggest where did i go wrong?
And what is the right way to copy the function module.?
If possible reply me ASAP.
Thanx in advance.

Hello Sanjay,
First, delete your new function group and
Do like this:
1. copy FI_ITEMS_DISPLAY to zFI_ITEMS_DISPLAY from Se37. here you find a button on the application toolbar to do it. It also asks about the Function group. GIve the FG as
ZFI_ITEMS.
Activate all the related objects
2. same for the other FM. Use the same FG. and activate the related objects.
Regards,
Naimesh

Error during generation of the function module..need help urgently

Hello everyone,
m trying to generate data source in BWDevelopment.
After mapping all the BW fields to Source Object elements I click on Generate DataSource(for UD Connect) so following error comes
'An error occurred in step 1 during generation of the function module'
RFC connection is fine, error free and extractor is also fine.
Where could be the problem?
Thanks & Regards,
Priyanka

Hello everybody,
my problem is solved.For the UDConnect, whatever DATA SOURCES you create gets registered in a FUNCTION MODULE which has a capacity of only 99 enties, so to increase it implement the SAP NOTE 876340 - UDC Error available on SERVICE MARKET PLACE.
This problem occurs with BW version 3.5 level 17 or below.
Regards,
Priyanka
Edited by: Priyanka Joshi on Jun 10, 2008 11:03 AM

Not able to use Commit after the function module STATUS_OBJECT_CREATE

I am using function module   STATUS_OBJECT_CREATE
   CALL FUNCTION 'STATUS_OBJECT_CREATE'
          EXPORTING
           CHGKZ         = 'X'
           CLIENT        = SY-MANDT
            OBJNR         = LV_OBJNR3
            OBTYP         = 'IWE'
            STSMA         = 'ZS_RE_01'
          IMPORTING
            OBJNR         = LV_OBJNR3.
            STONR                        = LV_STONR.
        IF SY-SUBRC = 0.
            COMMIT WORK.
        ENDIF.
i am getting error after the COMMIT WORK .
I am not getting any issue in the function module .after the function module i am using the COMMIT WORK and i am getting the following error message
Category               ABAP Programming Error
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Except.                CX_SY_OPEN_SQL_DB
ABAP Program           SAPLBSVU
Application Component CA-GTF-TS-SMT
Date and Time          03/17/2014 07:01:29
|Short text                                                                                        |
|    The ABAP/4 Open SQL array insert results in duplicate database records.                       |
|What happened?                                                                                    |
|    Error in the ABAP Application Program                                                         |
|                                                                                                  |
|    The current ABAP program "SAPLBSVU" had to be terminated because it has                       |
|    come across a statement that unfortunately cannot be executed.                                |
|What can you do?                                                                                  |
|    Note down which actions and inputs caused the error.                                          |
|                                                                                                  |
|                                                                                                  |
|    To process the problem further, contact you SAP system                                        |
|    administrator.                                                                                |
|                                                                                                  |
|    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   |
|    at and manage termination messages, and you can also                                          |
|    keep them for a long time.                                                                    |
|Error analysis                                                                                    |
|    An exception occurred that is explained in detail below.                                      |
|    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught                 |
|     in                                                                                           |
|    procedure "STATUS_UPDATE" "(FUNCTION)", nor was it propagated by a RAISING                    |
|     clause.                                                                                      |
|    Since the caller of the procedure could not have anticipated that the                         |
|    exception would occur, the current program is terminated.                                     |
|    The reason for the exception is:                                                              |
|    If you use an ABAP/4 Open SQL array insert to insert a record in                              |
|    the database and that record already exists with the same key,                                |
|    this results in a termination.                                                                |
|                                                                                                  |
|    (With an ABAP/4 Open SQL single record insert in the same error                               |
|    situation, processing does not terminate, but SY-SUBRC is set to 4.)                          |
|How to correct the error                                                                          |
|    Use an ABAP/4 Open SQL array insert only if you are sure that none of                         |
|    the records passed already exists in the database.                                            |
|                                                                                                  |
|    If the error occures in a non-modified SAP program, you may be able to                        |
|    find an interim solution in an SAP Note.                                                      |
|    If you have access to SAP Notes, carry out a search with the following                        |
|    keywords:                                                                                     |
|                                                                                                  |
|    "SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"                                              |
|    "SAPLBSVU" or "LBSVUU01"                                                                      |
|    "STATUS_UPDATE"                                                                               |
|                                                                                                  |
|    If you cannot solve the problem yourself and want to send an error                            |
|    notification to SAP, include the following information:                                       |
|                                                                                                  |
|    1. The description of the current problem (short dump)                                        |
|                                                                                                  |
|       To save the description, choose "System->List->Save->Local File                            |
|    (Unconverted)".                                                                               |
|                                                                                                  |
|    2. Corresponding system log                                                                   |
|                                                                                                  |
|       Display the system log by calling transaction SM21.                                        |
|       Restrict the time interval to 10 minutes before and five minutes                           |
|    after the short dump. Then choose "System->List->Save->Local File                             |
|    (Unconverted)".                                                                               |
|                                                                                                  |
|    3. If the problem occurs in a problem of your own or a modified SAP                           |
|    program: The source code of the program                                                       |
|       In the editor, choose "Utilities->More                                                     |
|    Utilities->Upload/Download->Download".                                                        |
|                                                                                                  |
|    4. Details about the conditions under which the error occurred or which                       |
|    actions and input led to the error.                                                           |
|                                                                                                  |
|    The exception must either be prevented, caught within proedure                                |
|    "STATUS_UPDATE" "(FUNCTION)", or its possible occurrence must be declared in                  |
|     the                                                                                          |
|    RAISING clause of the procedure.                                                              |
|    To prevent the exception, note the following:                                                 |
|System environment                                                                                |
|    SAP Release..... 702                                                                          |
|    SAP Basis Level. 0010                                                                         |
|                                                                                                  |
|    Application server... "sds6ci"                                                                |
|    Network address...... "11.224.101.53"                                                         |
|    Operating system..... "Linux"                                                                 |
|    Release.............. "2.6.18-194.el5"                                                        |
|    Hardware type........ "x86_64"                                                                |
|    Character length.... 16 Bits                                                                  |
|    Pointer length....... 64 Bits                                                                 |
|    Work process number.. 17                                                                      |
|    Shortdump setting.... "full"                                                                  |
|                                                                                                  |
|    Database server... "gctsdb01lds.hsi.hugh"                                                     |
|    Database type..... "ORACLE"                                                                   |
|    Database name..... "DS6"                                                                      |
|    Database user ID.. "SAPDS4"                                                                   |
|                                                                                                  |
|    Terminal.......... "GCTEMP02VDI"                                                              |
|                                                                                                  |
|    Char.set.... "C"                                                                              |
|                                                                                                  |
|    SAP kernel....... 720                                                                         |
|    created (date)... "Sep 14 2013 05:28:14"                                                      |
|    create on........ "Linux GNU SLES-9 x86_64 cc4.1.2 use-pr130820"                              |
|    Database version. "OCI_102, 10.2.0.5.0, V2, default"                                          |
|                                                                                                  |
|    Patch level. 500                                                                              |
|    Patch text.. " "                                                                              |
|                                                                                                  |
|    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"               |
|    SAP database version. 720                                                                     |
|    Operating system..... "Linux 2.6, Linux 3"                                                    |
|                                                                                                  |
|    Memory consumption                                                                            |
|    Roll.... 1317248                                                                              |
|    EM...... 0                                                                                    |
|    Heap.... 0                                                                                    |
|    Page.... 0                                                                                    |
|    MM Used. 1242912                                                                              |
|    MM Free. 53400                                                                                |
|User and Transaction                                                                              |
|    Client.............. 160                                                                      |
|    User................ "DV018458"                                                               |
|    Language key........ "E"                                                                      |
|    Transaction......... "SE38 "                                                                  |
|    Transaction ID...... "5323C30FC9364665E10000000BE06533"                                       |
|                                                                                                  |
|    EPP Whole Context ID.... "002655EE0F241ED3ABB7D81260A28C44"                                   |
|    EPP Connection ID....... 00000000000000000000000000000000                                     |
|    EPP Caller Counter...... 0                                                                    |
|                                                                                                  |
|    Program............. "SAPLBSVU"                                                               |
|    Screen.............. "RSM13000 3000"                                                          |
|    Screen Line......... 2                                                                        |
|    Debugger Active..... "none"                                                                   |
|Information on where terminated                                                                   |
|    Termination occurred in the ABAP program "SAPLBSVU" - in "STATUS_UPDATE".                     |
|    The main program was "RSM13000 ".                                                             |
|                                                                                                  |
|    In the source code you have the termination point in line 60                                  |
|    of the (Include) program "LBSVUU01".                                                          |
|    The program "SAPLBSVU" was started in the update system.                                      |
|    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in                   |
|    procedure "STATUS_UPDATE" "(FUNCTION)", but it was neither handled locally nor                |
|     declared                                                                                     |
|    in the RAISING clause of its signature.                                                       |
|                                                                                                  |
|    The procedure is in program "SAPLBSVU "; its source code begins in line                       |
|    1 of the (Include program "LBSVUU01 ".                                                        |
|Source Code Extract                                                                               |
|Line |SourceCde                                                                                   |
|   30| LOOP AT jsto_upd WHERE chgkz = 'X'.                                                       |
|   31|    CHECK: jsto_upd-chgnr > '000',                                                          |
|   32|           jsto_upd-stsma NE jsto_upd-stsma_old.                                            |
|   33|    CLEAR jcdo_tab.                                                                         |
|   34|    MOVE-CORRESPONDING jsto_upd TO jcdo_tab.                                                |
|   35|    MOVE-CORRESPONDING chdat    TO jcdo_tab.                                                |
|   36|    jcdo_tab-stsma_new = jsto_upd-stsma.                                                    |
|   37|    APPEND jcdo_tab.                                                                        |
|   38| ENDLOOP.                                                                                  |
|   39|* Änderungen zu Einzelstatus (Insert)                                                       |
|   40| LOOP AT jest_ins WHERE chgkz = 'X'.                                                       |
|   41|    CHECK jest_ins-chgnr > '000'.                                                           |
|   42|    CLEAR jcds_tab.                                                                         |
|   43|    MOVE-CORRESPONDING jest_ins TO jcds_tab.                                                |
|   44|    MOVE-CORRESPONDING chdat    TO jcds_tab.                                                |
|   45|    jcds_tab-chind = 'I'.                                                                   |
|   46|    APPEND jcds_tab.                                                                        |
|   47| ENDLOOP.                                                                                  |
|   48|* Änderungen zu Einzelstatus (Update)                                                       |
|   49| LOOP AT jest_upd WHERE chgkz = 'X'.                                                       |
|   50|    CHECK jest_upd-chgnr > '000'.                                                           |
|   51|    CLEAR jcds_tab.                                                                         |
|   52|    MOVE-CORRESPONDING jest_upd TO jcds_tab.                                                |
|   53|    MOVE-CORRESPONDING chdat    TO jcds_tab.                                                |
|   54|    jcds_tab-chind = 'U'.                                                                   |
|   55|    APPEND jcds_tab.                                                                        |
|   56| ENDLOOP.                                                                                  |
|   57|* Verbuchung Statusobjekte                                                                  |
|   58| DESCRIBE TABLE jsto_ins LINES sy-tabix.                                                   |
|   59| IF sy-tabix > 0.                                                                          |
|>>>>>|    INSERT jsto CLIENT SPECIFIED                                                            |
|   61|                FROM TABLE jsto_ins.                                                        |
|   62| ENDIF.                                                                                    |
|   63| DESCRIBE TABLE jsto_upd LINES sy-tabix.                                                   |
|   64| IF sy-tabix > 0.                                                                          |
|   65|    field-symbols <fs_jsto_line> like jsto_upd.                                             |
|   66|    loop at jsto_upd assigning <fs_jsto_line>.                                              |
|   67|      IF <fs_jsto_line>-chgnr = '000'.                                                      |
|   68|        <fs_jsto_line>-chgnr = '999'.                                                       |
|   69|      ENDIF.                                                                                |
|   70|* on change of status profile delete user status related to old profile                     |
|   71|      IF <fs_jsto_line>-STSMA NE <fs_jsto_line>-STSMA_OLD.                                  |
|   72|        DELETE FROM JEST CLIENT SPECIFIED WHERE                                             |
|   73|               MANDT = <fs_jsto_line>-MANDT AND                                             |
|   74|               OBJNR = <fs_jsto_line>-OBJNR AND                                             |
|   75|               STAT LIKE 'E%'.                                                             |
|   76|        DELETE FROM JCDS CLIENT SPECIFIED WHERE                                             |
|   77|               MANDT = <fs_jsto_line>-MANDT AND                                             |
|   78|               OBJNR = <fs_jsto_line>-OBJNR AND                                             |
|   79|               STAT LIKE 'E%'.                                                             |

i tried with out using commmit but it is not creating Status.
When i see the function module help and they are trying to COMMIT
FU STATUS_OBJECT_CREATE
Short Text
Create Status Object
Functionality
The function module generates a status object.
Take the object number from the object number management (function modules OBJECT_NUMNBER_GET_xx).
If no object number is given, the module takes a temporary object number that must be replaced later (function module STATUS_OBJECT_SWITCH_NUMBER).
Example
Creating an internal order with number 100123 (object type "ORC") for status profile "STATSCHEM" with final object number
call function 'OBJECT_NUMBER_GET_OR'
exporting
    aufnr = '100123'
importing objnr = objektnummer.
call function 'STATUS_OBJECT_CREATE'
exporting
    objnr = objektnummer
    obtyp = 'ORC'
    stsma = 'STATSCHEM'.
commit work.
Creating the same order with a temporary object number
data: objectkey like ionra.
* TBO00-REFSTRUCT for object type 'OR' is 'IONRA'
objectkey-aufnr = '100123'.
call function 'STATUS_OBJECT_CREATE'
exporting
    i_objectkey = objectkey
    obtyp       = 'ORC'
    stsma       = 'STATSCHEM'.
importing
    objnr       = objektnummer.
call function 'OBJECT_NUMBER_GET_OR'
exporting
    aufnr = '100123'
importing objnr = objektnummer_neu.
call function 'STATUS_OBJECT_SWITCH_NUMBER'
exporting
    objnr_old = objektnummer
    objnr_new = objektnummer_neu.
commit work.
Notes

How to create a secondary list of alv grid inside the function module

Hi All,
My requirement is to create a RFC function module to display the alv grid of one table.
i have created that.
while clicking on the records of the alv it should open the secondary list of another table.
My problem is it is not fetching the records of the internal table of the primary list since it is created inside the function module(FUNCTION...ENDFUNCTION).
pls help me on this.
Thanks in Advance.

hi,
READ TABLE sel_sheet INTO wa_sheet INDEX rs_selfield-tabindex.
here sel_sheet is the internal table for the primary list..
i called the function module "reuse_lav_grid_display" inside Function...Endfunction.
so when i am using READ TABLE sel_sheet INTO wa_sheet INDEX rs_selfield-tabindex.
inside the user command perform therecords in this internal table is not populating..
pls help me on this.
thanks in advance.

Reference-Problem in RFC-Function Module

Hello,
I am new to ABAP. As an introduction I read the book "ABAP Objects" from SAP Press.
I need a web service which returns a before uncertain number of objects.
First I have written a class representing my object. Then I added a new table type to the DDIC which has as "line type" simply my class as referenced type.
Afterwards I have implemented a function module which has an export parameter with the TYPE of my table type. The whole thing works fine, if I configure the function module as a normal function module. As soon as I click on RFC, I get the error message "Reference parameters are not allowed with RFC ". However, I have already clicked "pass by value" for the export- and import-parameters. The problem seems to be the table type with my class as referenced type.
Is the approach in general correct, to create a web service?
How can I fix the problem with the reference?
Best regards
Philipp

Ok, I understand the problem is that I can not export any reference. And therefore no objects because the declaration has to be done with TYPE REF TO...
Can you tell me a little more detailed about the usage of the interface IF_SERIALIZABLE_OBJECT?
Is it possible to serialize the whole internal table which has to exported?
Would it have the same effect like a table type based on a structure with attributes like my object?
Best regards
Philipp

Problem when calling function module CV120_DOC_CHECKOUT_VIEW in background

Hi ,
I'm currently developping an abap program which extract document from KPRO for printing into a windows Folder.
For this I use standard function module CV120_DOC_CHECKOUT_VIEW.
When i run my program in foreground task there's no problem, but when i run it in background task the extract doesn't work. It seems that the system cannot connect to the Windows Network.
Whe the program is running in foreground task, the function module user SAPHHTP RFC destination, when it runs in background task it use SAPFTP destination .
Does somebody can help me ?
thanks in advance

Hi Ajay,
The program extract document into a folder on Windows Network that means on a server not on a PC .
I know that in background task ther's no connection with sapgui.
For example when i want to create a file on network n background task i use OPEN_DATASET instruction and that works fine.
My problem is the use of the standard function module CV120_DOC_CHECKOUT_VIEW in background task because when this function module is running in background task it use the SAPFTP rfc destination instead of SAPHHTP rfc destination in foreground task . I check the RFC destination , thoses works both . SO i think the problem comes from parameters given to the function module.
Regards.

RFC_ERROR_SYSTEM_FAILURE: The function module "DD_DTEL_GET" cannot be used.

Hi there,
I´m trying to launch NWCE 7.1 Webdynpro applications accessing ABAP function with no success.
The landscape consists of an SAP NWCE 7.1 EHP1 (Trial) and an SAP NW 2004s ABAP (Licensed). NW2004s is configured as Gateway and Message Server for the SLD. I can ping/test JCOs successfully and the SLD seems to work fine. RZ70 and SM59 show no errors in the "R3" side and both systems seem to be well-registered as Technical Systems.
I have done some simple examples in Developer Studio to ensure that the conection between both stacks is going well, but I have allways the same issue regardless using ARFC/ARFC2, new projects/old existing projects, etc.
When I test for first time the application, the following exception is thrown:
Caused by: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: The function module "DD_DTEL_GET" cannot be used for 'remote' calls.
     at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:456)
     at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1416)
     at com.sap.mw.jco.JCO$Client.execute(JCO.java:4168)
     at com.sap.mw.jco.JCO$Client.execute(JCO.java:3596)
     at com.sap.mdi.jco6.Destination.execute(Destination.java:29)
     ... 136 more
If I refresh the page the last exception disappears and a new one is thrown:
#2# local/prjWD_Acceso_ABAP/FlightListApp#java.lang.NullPointerException
     at com.sap.mdi.ddtypes.DDDataelement.getDescription(DDDataelement.java:305)
     at com.sap.dictionary.types.mdi.util.TextServices.getDescription(TextServices.java:165)
     at com.sap.dictionary.types.mdi.util.TextServices.getQuickInfo(TextServices.java:145)
     at com.sap.dictionary.runtime.DdDataType$TextService.getQuickInfo(DdDataType.java:220)
     at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.getDisplayText(DataAttributeInfo.java:385)
     at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.getDisplayText(DataAttributeInfo.java:355)
     at com.sap.tc.webdynpro.progmodel.context.MappedAttributeInfo.getDisplayText(MappedAttributeInfo.java:292)
     at com.sap.tc.webdynpro.progmodel.view.ViewElement._getText(ViewElement.java:818)
     at com.sap.tc.webdynpro.progmodel.view.UIElement.getTooltip(UIElement.java:515)
     at com.sap.tc.webdynpro.clientserver.uielib.standard.uradapter.InputFieldAdapter$OrdinaryField.getTooltip(InputFieldAdapter.java:8201)
     at com.sap.tc.webdynpro.clientserver.uielib.standard.uradapter.InputFieldAdapter$OrdinaryField.getParameter(InputFieldAdapter.java:7496)
     at com.sap.tc.ls.renderer.ie6.LSInputFieldRenderer.render(LSInputFieldRenderer.java:160)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.lightspeed.base.LSRenderManager.render(LSRenderManager.java:152)
     at com.sap.tc.webdynpro.clientimpl.html.client.RenderManager.render(RenderManager.java:519)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.lightspeed.base.LSRenderManager.render(LSRenderManager.java:130)
     at com.sap.tc.ls.renderer.ie6.LSColumnLayoutRenderer.renderColumnLayoutCellFragment(LSColumnLayoutRenderer.java:1882)
     at com.sap.tc.ls.renderer.ie6.LSColumnLayoutRenderer.renderColumnLayoutRowFragment(LSColumnLayoutRenderer.java:1715)
     at com.sap.tc.ls.renderer.ie6.LSColumnLayoutRenderer.renderColumnLayoutFragment(LSColumnLayoutRenderer.java:1600)
Then, editing the application in Dev. Studio, if I delete tables and/or single fields binded to model context, the last exception doesn´t appear any more but the application enter in the catch section executing the BAPI call:
     try
          wdContext.currentBapi_Flight_Getlist_InputElement().modelObject().execute();
     catch(Exception ex)
          wdComponentAPI.getMessageManager().reportException("Execute error."+ex.toString()+ex.getMessage());
          StackTraceElement errores[] = ex.getStackTrace();
          String errorSTR = new String();
          for (int i = 0; i < errores.length; i++){
               errorSTR += errores<i>.toString() + "
          wdComponentAPI.getMessageManager().reportException(errorSTR);
     wdComponentAPI.getMessageManager().reportSuccess("After catch.");
     // Resynchronise the data in the context with the data in the model
     wdContext.nodeOutput().invalidate();
The first two exception seem to be related each other, and it is true that FM "DD_DTEL_GET" is not RFC enabled in R3. Should it be RFC enabled?
As far as I know, one of the JCO conectors is used for retrieving metadata, that is, data related to types, lenghts, etc. The FM "DD_DTEL_GET" is used for that kind of operations and the second exception is related to that aswell (com.sap.mdi.ddtypes.DDDataelement.getDescription).
I don´t know what else should I test in order to launch an RFC function from WDJ and the trial version is about to expire!
Does anyone know about any oss note or any other tips related to this issue, please?
I am going to test the conectivity via Visual Composer and see whether it´s possible :S
Let me know if you need anymore info about the situation.
Thanks a lot!

Hi again,
The issue hasn´t been solved yet :(.
After applying Note 1244067 the function module has the RFC flag checked but the Null Pointer exception are still there.
java.lang.NullPointerException
at com.sap.mdi.ddtypes.DDDataelement.getReptext(DDDataelement.java:166)
at com.sap.dictionary.types.mdi.util.TextServices.getColumnLabel(TextServices.java:115)
at com.sap.dictionary.runtime.DdDataType$TextService.getColumnLabel(DdDataType.java:212)
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.getDisplayText(DataAttributeInfo.java:379)
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.getDisplayText(DataAttributeInfo.java:355)
at com.sap.tc.webdynpro.progmodel.view.ViewElement._getText(ViewElement.java:818)
at com.sap.tc.webdynpro.clientserver.uielib.standard.impl.Caption.getText(Caption.java:369)
at com.sap.tc.webdynpro.clientserver.uielib.standard.uradapter.TableAdapter$HeaderCell.getHeaderText(TableAdapter.java:11441)
at com.sap.tc.webdynpro.clientserver.uielib.standard.uradapter.TableAdapter$HeaderCell.getParameter(TableAdapter.java:11043)
at com.sap.tc.ls.renderer.ie6.LSSapTableHeaderCellRenderer.renderSapTableHeaderCellFragment_iteration(LSSapTableHeaderCellRenderer.java:2421)
at com.sap.tc.ls.renderer.ie6.LSSapTableRowRenderer.renderSapTableRowFragment(LSSapTableRowRenderer.java:223)
at com.sap.tc.ls.renderer.ie6.LSSapTableRowRenderer.render(LSSapTableRowRenderer.java:122)
at com.sap.tc.webdynpro.clientimpl.html.renderer.lightspeed.base.LSRenderManager.render(LSRenderManager.java:152)
at com.sap.tc.webdynpro.clientimpl.html.client.RenderManager.render(RenderManager.java:519)
at com.sap.tc.webdynpro.clientimpl.html.renderer.lightspeed.base.LSRenderManager.render(LSRenderManager.java:130)
at com.sap.tc.ls.renderer.ie6.LSSapTableDefaultBodyRenderer.renderSapTableDefaultBodyFragment(LSSapTableDefaultBodyRenderer.java:301)
at com.sap.tc.ls.renderer.ie6.LSSapTableDefaultBodyRenderer.render(LSSapTableDefaultBodyRenderer.java:119)
at com.sap.tc.webdynpro.clientimpl.html.renderer.lightspeed.base.LSRenderManager.render(LSRenderManager.java:152)
at com.sap.tc.webdynpro.clientimpl.html.client.RenderManager.render(RenderManager.java:519)
at com.sap.tc.webdynpro.clientimpl.html.renderer.lightspeed.base.LSRenderManager.render(LSRenderManager.java:130)
Language resources data in the webdynpro are: Current locale = "es", Default VM locale = "es_ES". The backend default language is "EN". Could this be a problem in order to retrieve descriptions or any other language dependent data?
Thank you
Vicente.

How to findout the Function module for a particular object

Hello friends,
   Related to my thread, there was one thread in the forum,to find out the function module for a particular object.I tried the solution provided my our experts but couldn't got the results.Thats why i am putting this thread again.
I want to find out the function modules used for the particular object, i.e. Production order.
   solution i tried is, first go to T.C SE37, then in function module field put the object name like Production order and enter, than it will show another screen, there also put object name in function module field and than press enter, it will show all the function modules available for that object.
    So could you guys help me out to find out where i am wrong in the process of finding out the function module for a particular object.
                       Plz don't bother abt the point.Helpful answers will definitely get awarded.
                            Thanking you guys for your valuable support till now and hoping to get in future too.

Dear
When the problem is solved please give points too. Otherwise why people will help others, give time and share their valuable knowledge. This will build up self confidence.
If not solved and closing, then mention the difficulties what u exactly looking for. Simpy closing is not enough because who ever is providing solution will not able to know the real problem.
How to give points I believe u already know that and need not explain.
I had seen many times this problem with others too. Even if the problem is totally resolved they give 2 in stead of 10.
Edited by: BNR on Sep 21, 2008 6:10 PM

Problem in the function module HAZMAT_PRI_DATA_GET

Similar Messages

Maybe you are looking for