FM LDB_PROCESS

Hi Friends,
I am using LDB 'SD_SALES_DOCUMENTS' 'for SD in my program. I am calling FM LDB_PROCESS and want to pass dynamic selection screen to this FM. it is passing but it is taking only single value.
Let us suppose, i am passing sales order as dynamic selection. but only single value it will accepy. If i put mutiple entry, it is not going to accept.
Please suggest me.
Thanks & Regards,
Manoj

Take a look at the Std Report RVKUSTA1 & you will know how to pass the Sle scr.
~Suresh

Similar Messages

Logical databse call using FM LDB_PROCESS in ABAP WD

hi
i want to use LDB in a webdynpro application to read the data. i came to know that we can use LDB_PROCESS FM to achieve this. we need to pass callback routines to this FM. as we can not write subroutines in ABAP OO, how do i do this. do i need a wrapper FM around LDB_PROCESS and call that in turn in the webdynpro method or is there any better way to do that.
thanksl
Edited by: sudhakar murthy on Oct 20, 2009 4:10 PM

hi
if you go through that help link you will find an example at the bottom where we need define some call back routines using FORM and ENDFORM. I can not do that in ABAP WD as WD is based on ABAP OO.
thanks

Define selection screen for ldb_process

Hi I'm using the call function ldb_process for KDF(lfa1, lfb1, bsik), the trouble is that the information its different than if i do it on a normal report defining the logical database kdf and selection screen 903.
I find that the difference is because the selection screen, this is because the default selection screen for the kdf database is 1000, and this selection has the "Open items at key date" selection with the current date.
The question is:
How can i define the selection screen 903 using the call function ldb_proces?
Thanks
Pablo Santos

Hi,
You cannot define screen version 903 using function LDB_PROCESS. Instead use table "SELECTIONS" of the function module .
Cheers.

Func Module : LDB_PROCESS and Logical Database ADA

Hi All,
How to get 'ANLB' data from logical database 'ADA' using the
function module 'LDB_PROCESS'?
Is there any other way to done this without getting into SELECTION SCREEN of this LOGICAL DATABASE?
With Thanls & Regards,
R.Nagarajan.
We can -

Hi,
Using LDB_PROCESS will made all the fields of this LDB available to you......this is the way ..you can use n number of LDB's in your program apart from the one that u mention in Program attributes....
for more details and Function call..use..
Re: How to hide the selection screen of a Logical datebase?

LDB_PROCESS selections problem

Hi there dear ABAP'ers.
I've got such a question
I've got a standard report F.05, which doesn't do BD SELECTs directly, but instead it calls LDB_PROCESS FModule and processes a 'SDF' LDBase.
    call function 'LDB_PROCESS'
       exporting
            ldbname                     = 'SDF'
*          VARIANT                     =
           EXPRESSIONS                 = sdf_expressions
*          FIELD_SELECTION             =
*          DYN_NODE_TYPES              =
       tables
            callback                    = gt_callback
           SELECTIONS                  = seltab
       exceptions
F.05 for G/L accounts valuation returns some 'aggregated' values, and I would like to debug it somehow.
When I debug the place in code where LDB_PROCESS is calleg, I see that FM's parameter 'SELECTIONS' contains an itab:
SELNAME KIND SIGN OPTION LOW
D_SAKNR|S   |I   |EQ    |3110000000
X_CURTP|S   |I   |EQ    |60
D_BUKRS|S   |I   |EQ    |TCLZ
D_GJAHR|S   |I   |EQ    |2009
I try to edit a 'SDF' LDbase in SE36 transaction. I am launching a SELECTIONS screen, then try to insert into screen fields values as in FModule's parameter itab, and when I wish to launch LDB program I got an error message, that one more parameter is missed (key date for open items).
So how does it work that LDB_PROCESS doesn't pass the key date parameter and it fetches data from LDBase correctly, whilst when I launch LDB manually from SE36 - it needs one more additional parameter?
Another thing is ... why when I set a breakpoint in LDB program, after launching F.05 - debugger does not stop at LDB's breakpoint ... I thought that when launching LDB_PROCESS sap launches a LDB's program to gather appropriate data ...
Greetings. P.
Edited by: Piotr Wojciechowski on Oct 30, 2009 2:12 PM
Edited by: Piotr Wojciechowski on Oct 30, 2009 2:12 PM

try transaction FBL3N with use LDB SDF, it uses flags to select cleared, non cleared or all items, depending on the flag selected some different dates are to be provided.
Regards,
Raymond

LDB_PROCESS for PNP

Hi all,
I am trying to use LDB_PROCESS function module for logical database PNP but am not sucessful in it.
I am pasting my code below:
Moderator message - Please respect the 2,500 character maximum when posting. Post only the relevant portions of code
The problem i am facing is that the FM is processed perfectly but callback routine is not called.
Kindly help...
Seema Peswani
ABAP HR
Edited by: Rob Burbank on Nov 13, 2009 9:43 AM

CALLBACK_WA-LDBNODE = 'PERNR'.
CALLBACK_WA-GET = 'X'.
*CALLBACK_WA-GET_LATE = 'X'.
CALLBACK_WA-CB_PROG = SY-REPID.
CALLBACK_WA-CB_FORM = 'CALLBACK_LFB1'.
APPEND CALLBACK_WA TO CALLBACK.
SELTAB_WA-KIND = 'S'.
SELTAB_WA-SELNAME = 'KD_ABKRS'.
LOOP AT S_ABKRS.
MOVE-CORRESPONDING S_ABKRS TO SELTAB_WA.
APPEND SELTAB_WA TO SELTAB.
ENDLOOP.
CALL FUNCTION 'LDB_PROCESS'
EXPORTING
    LDBNAME                     = 'PNP'
    VARIANT                     = ' '
    EXPRESSIONS                 = TEXPR
    FIELD_SELECTION             = FSEL
    DYN_NODE_TYPES              = DYN_NODE_TYPES
TABLES
    CALLBACK                    = CALLBACK
    SELECTIONS                  = SELTAB
EXCEPTIONS
    LDB_NOT_REENTRANT           = 1
    LDB_INCORRECT               = 2
    LDB_ALREADY_RUNNING         = 3
    LDB_ERROR                   = 4
    LDB_SELECTIONS_ERROR        = 5
    LDB_SELECTIONS_NOT_ACCEPTED = 6
    VARIANT_NOT_EXISTENT        = 7
    VARIANT_OBSOLETE            = 8
    VARIANT_ERROR               = 9
    FREE_SELECTIONS_ERROR       = 10
    CALLBACK_NO_EVENT           = 11
    CALLBACK_NODE_DUPLICATE     = 12
    CALLBACK_NO_PROGRAM         = 13
    CALLBACK_NO_CBFORM          = 14
    DYN_NODE_NO_TYPE            = 15
    DYN_NODE_INVALID_TYPE       = 16
    OTHERS                      = 17.
IF SY-SUBRC NE 0.
WRITE: 'Exception with SY-SUBRC', SY-SUBRC.
ENDIF.
FORM CALLBACK_LFB1 USING NAME TYPE LDBN-LDBNODE
                         WA TYPE PERNR
                         EVT TYPE C
                         CHECK TYPE C.
CASE EVT.
    WHEN 'G'.
      WRITE: / WA-PERNR.
   WHEN 'L'.
     ULINE.
ENDCASE.
ENDFORM.                    "CALLBACK_PERNR

Ldb_process and PNP

Hi,
could you give me a working example of using FM LDB_PROCESS with logical dabase PNP, please? Every example, which I found there dont work and I dont know why.
Thanks in advance
Krzysztof

hi,
Have you solved this problem yet or not? Please do reply. I am stuck with the same problem
would appreciate your effort.
thank you for your time and support.
Regards,
Seema Peswani

How to pass dynamic selection to logical databse using ldb_process function

dear friends,
can anybode tell me how to pass dynamic selection to the logical database when i m using LDB_PROCESS function module. however, in EXPRESSIONS paramter of the function module i m passing the selecti-option, it is passing their also but when i used more than two select-option or paramter it throw an exception FREE_SELECTIONS_ERROR.
SO PLEASE GUIDE ME HOW TO PASS MORE THAN TWO SELECT-OPTION IN LOGICAL DATANSE DYNAMICALLY USING LDB_PROCESS.

would be nice if you post the answer to all

LDB CMC with LDB_PROCESS FM ?

Dear All,
1. I'm calling the Function Module LDB_PROCESS in my Program.
2. I'm passing CMC LDB to the above FM.
3. I've built the Necessary params to pass onto the FM.
4. But my Form is not getting triggered.
Please let me know the reason !
Enclosed is the code :
Data: wa_mastb like mastb.
SELECT-OPTIONS: s_matnr for wa_mastb-matnr.
DATA: CALLBACK    TYPE TABLE OF LDBCB,
            CALLBACK_WA LIKE LINE OF CALLBACK.
DATA: gt_SELTAB TYPE TABLE OF RSPARAMS,
            gwa_SELTAB LIKE LINE OF gt_SELTAB.
CLEAR CALLBACK_WA.
CALLBACK_WA-LDBNODE     = 'MASTB'.
CALLBACK_WA-GET         = 'X'.
CALLBACK_WA-GET_LATE    = ' '.
CALLBACK_WA-CB_PROG     = SY-REPID.
CALLBACK_WA-CB_FORM     = 'CALL_MASTB'.
APPEND CALLBACK_WA TO CALLBACK.
gwa_SELTAB-KIND    = 'S'.
gwa_SELTAB-SELNAME = 'MATNR'.
Loop at s_matnr.
MOVE-CORRESPONDING s_matnr to gwa_SELTAB.
append gwa_SELTAB to gt_seltab.
endloop.
START-OF-SELECTION.
CALL FUNCTION 'LDB_PROCESS'
EXPORTING
    LDBNAME                           = 'CMC'
*   VARIANT                           =
*   EXPRESSIONS                       =
*   FIELD_SELECTION                   =
*   DYN_NODE_TYPES                    =
TABLES
    CALLBACK                          = CALLBACK
    SELECTIONS                        = gt_SELTAB.
IF SY-SUBRC <> 0.
Write:/ 'Error in the Call of the LDB FM'.
ENDIF.
end-of-SELECTION.
FORM CALL_MASTB USING PD_NODE LIKE LDBN-LDBNODE
                                              PD_WORKAREA like mastb
                                              PD_MODE     TYPE C
                                              PD_SELECTED TYPE C.
data: ls_mastb like mastb.
CASE PD_NODE.
    WHEN 'MASTB'.
      LS_mastb = PD_WORKAREA.
      write:/ ls_mastb-matnr, ls_mastb-werks.
ENDCASE.
ENDFORM.
Regards,
Deepu.K

Hi!
for CMC LDB you must add parameter:
PARAMETERS :
         datuv LIKE stko-datuv DEFAULT sy-datum.
and fill it
CLEAR gwa_seltab.
gwa_seltab-kind    = 'P'.
gwa_seltab-selname = 'DATUV'.
gwa_seltab-sign    = 'I'.
gwa_seltab-option = 'EQ'.
gwa_seltab-low = datuv .
APPEND gwa_seltab TO gt_seltab.

FM LDB_PROCESS doesn't work fine

Hi everyone,
I need to access the logical database EHS_OH001 from a function, and I using the FM LDB_PROCESS to do this.
But when I've compared teh results using this LDB via a report (selection screen and GET event) and this function I noticed that the results don't match, I mean, the report resulted 1 record while the function didn't bring any record at all.
The code is below...thanks in advance!
report zteste_ldb_process.
tables: ehs_pernr.
type-pools: rsds, rsfs.
data: texpr type rsds_texpr,
      fsel type rsfs_fields.
data : ti_pernr   type standard table of ehs_pernr with header line.
data: t_callback type table of ldbcb.
data:callback_wa like line of t_callback.
data: seltab type table of rsparams,
      seltab_wa like line of seltab.
select-options: s_pernr for ehs_pernr-person_id.
*parameters: p_pernr type ehs_pernr.
*parameters: p_plans type plans.
parameters: p_bukrs like ehs_pernr-bukrs obligatory modif id sel.
*parameters: zpgroup like hrp9904-zpgroup.
*parameters: znumber like hrp9904-zpnumber.
start-of-selection.
loop at s_pernr.
    move-corresponding s_pernr to seltab_wa.
    seltab_wa-kind = 'S'.
    seltab_wa-selname = 'EHSPERNR'.
    append seltab_wa to seltab.
endloop.
    seltab_wa-sign = 'I'.
    seltab_wa-option = 'EQ'.
    seltab_wa-kind = 'P'.
    seltab_wa-low = p_bukrs.
    seltab_wa-selname = 'EHSBUKRS'.
    append seltab_wa to seltab.
callback_wa-ldbnode = 'EHS_PERNR'.
callback_wa-get = 'X'.
callback_wa-get_late    = 'X'.
callback_wa-cb_prog = sy-repid.
callback_wa-cb_form = 'CALLBACK_EHS_PERNR'.
append callback_wa to t_callback.
call function 'LDB_PROCESS'
    exporting
      ldbname                           = 'EHS_OH001'
    variant                           = ' '
    expressions                       = texpr
    field_selection                   = fsel
DYN_NODE_TYPES                    =
    tables
      callback                          = t_callback
     selections                        = seltab
exceptions
   ldb_not_reentrant                 = 1
   ldb_incorrect                     = 2
   ldb_already_running               = 3
   ldb_error                         = 4
   ldb_selections_error              = 5
   ldb_selections_not_accepted       = 6
   variant_not_existent              = 7
   variant_obsolete                  = 8
   variant_error                     = 9
   free_selections_error             = 10
   callback_no_event                 = 11
   callback_node_duplicate           = 12
   callback_no_program               = 13
   callback_no_cbform                = 14
   dyn_node_no_type                  = 15
   dyn_node_invalid_type             = 16
   others                            = 17
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
*&      Form CALLBACK_EHS_PERNR
      Função usada por LDB_PROCESS para processar os nodes.
     -->P_EHS_PERNR text
     -->P_WA text
     -->P_EVT text
     -->P_CHECK text
form callback_ehs_pernr using    p_ehs_pernr type ldbcb-ldbnode
                                  p_wa type ehs_pernr
                                  p_evt type c
                                  p_check type c.
append p_wa to ti_pernr.
endform.                    " CALLBACK_EHS_PERNR

Hi Dave,
Pls. refer to the earlier posted forum. This may be helpful for ya..
Delta load from ODS to Cube
You may also look into
Delta Update from ODS is invalidated
this has been mentioned in the previous forum link .
Hope this helps...
Thanks,
Raj

FM LDB_PROCESS slow extraction

Hi all,
I'm using FM LDB_PROCESS to access logical database FTI_TR_PERIODS to extract records from there, and following is how I call my FM:
CALL FUNCTION 'LDB_PROCESS'
     EXPORTING
          ldbname                     = 'FTI_TR_PERIODS'
          variant                     = ' '
*          EXPRESSIONS                 = TEXPR
          field_selection             = i_fsel
     TABLES
          callback                    = i_callback
          selections                  = i_sel
     EXCEPTIONS
          ldb_not_reentrant           = 1
          ldb_incorrect               = 2
          ldb_already_running         = 3
          ldb_error                   = 4
          ldb_selections_error        = 5
          ldb_selections_not_accepted = 6
          variant_not_existent        = 7
          variant_obsolete            = 8
          variant_error               = 9
          free_selections_error       = 10
          callback_no_event           = 11
          callback_node_duplicate     = 12
          OTHERS                      = 13.
However, I found that the extraction process is very slow (approximately 15,000 records to be extracted) when executing my report. Due to this, I have filled up field_selection parameter to improve performance, after reading this FM documentation. Consequently, it didn't help much on the performance.
Can anyone suggest are there any other ways to improve the extraction process when accessing Logical Database?
Best regards,
Patrick

Take a look at the Std Report RVKUSTA1 & you will know how to pass the Sle scr.
~Suresh

How to add dynamic selection in LDB_PROCESS

Hi All,
We are calling LDB_PROCESS from our report. and we are sending callback events and selections and we are calling LDB KDF.
We enabled housebank (HBKID) in Dynamic Selection of the LDB. Could you please help us how we can send value of field HBKID (House Bank) from LDB_Process to narrow down the selection process.
Thanks and best regards,
Niteeshrai

And the setClientAttributes() takes Set object, so i added ClientAttributeTag and then set it in HashSet. Is this the way to do it ??
and how can i set string value in ClientAttributeTag.setValue() ??
Please help.
Sudeep

Help on FM LDB_PROCESS for LDB FTI_TR_PL_CF

Hi everyone,
Good day!
I am currently working on INFOSETS for Treasury Module and there's a requirement to use function module LDB_PROCESS for logical database FTI_TR_PL_CF.
I have not worked on the said function module before and i am not familiar with the logical database.
In this regard, I would like to ask you good Sirs and Madams to give me an overview or any input that would give me a clear picture on what needs to be done for this requirement.
Thanks so much in advance.
God bless!
Regards,
Mike

Hi Suresh,
Thanks for your help.
Does anyone know a link that shows how to create infoset query using the FM LDB_PROCESS? I have been working on this for days now and I'm still kind of puzzled. The requirement is to add output fields to the query but the fields to be displayed are to be retrieved from an outside Logical database. Hope you guys can also help me on this.
Thanks so much in advance. God bless!
Regards,
Mike

LDB_PROCESS

HI,
I want to learn the usages of LDB_PROCESS
Iam using 2 logical database in report.
one in attributes and other one is in LDB_PROCESS
getting output in 2 blocks But i don't want like blocks.
hope u understood my requirement.
can any one plz post the sample code for my requirement .
like<b> vbeln, posnr, matnr</b>(for one logical database)
<b>Maktx</b> (from other Logial database, Related info)
Thanx in Advance
Santhosh reddy

I dint go thru the entire explantion but i have some sample code and i have pasted it below:
create CALLBACK:
lt_callback-ldbnode     = i_ldbnode.
lt_callback-get         = i_callback_get.
lt_callback-get_late    = i_callback_get_late.
lt_callback-cb_prog     = i_callback_prog.
lt_callback-cb_form     = i_callback_form.
APPEND lt_callback.
CLEAR lt_callback.
CALL FUNCTION 'LDB_PROCESS'
    EXPORTING
      ldbname                           = i_ldbname
    VARIANT                           =
    EXPRESSIONS                       =
      field_selection                   = lt_fields_sorted
    DYN_NODE_TYPES                    =
    TABLES
      callback                          = lt_callback
      selections                        = lt_seltab
    EXCEPTIONS
      ldb_not_reentrant                 = 1
      ldb_incorrect                     = 2
      ldb_already_running               = 3
      ldb_error                         = 4
      ldb_selections_error              = 5
      ldb_selections_not_accepted       = 6
      variant_not_existent              = 7
      variant_obsolete                  = 8
      variant_error                     = 9
      free_selections_error             = 10
      callback_no_event                 = 11
      callback_node_duplicate           = 12
      callback_no_program               = 13
      callback_no_cbform                = 14
      dyn_node_no_type                  = 15
      dyn_node_invalid_type             = 16
      OTHERS                            = 17.
Callback form
FORM callback_form                                          "#EC CALLED
     USING name     TYPE ldbn-ldbnode
           workarea TYPE fti_ldb_tr_positions
           mode     TYPE c
           selected TYPE c.
MOVE-CORRESPONDING workarea TO g_wrk_ldb_result.
APPEND g_wrk_ldb_result TO g_tab_ldb_result[].
ENDFORM.

LDB_PROCESS - In Object Oriented Concept

Is there any equivalent method/class that can allow to process logical database ??
If not how could we use this function module within Class/method?
Thanks in advance for your ansewrs

Hi Stephen,
A where-used-list of the FM 'LDB_PROCESS' returned the method
CALL_LDB_PROCESS of the class CL_DROB_LOGDB, please check if this can be of some help to you.
Regards
Rajesh

Problem when using LDB_PROCESS

REPORT ZFI_IF0005_NEW.
NODES: LFB1,BSIK.
GET LFB1.
WRITE: / LFB1-BUKRS,LFB1-LIFNR.
GET BSIK.
WRITE: / BSIK-BELNR.
returns:
ZFI_IF0005_NEW
2001 300000638
1900000006
1500000209
5100000072
1500000012
1900000005
REPORT ZFI_IF0005_NEW.
CALL FUNCTION 'LDB_PROCESS'
     EXPORTING
          LDBNAME                     = 'KDF'
          VARIANT                     = ' '
          EXPRESSIONS                 = TEXPR
          FIELD_SELECTION             = FSEL
     TABLES
          CALLBACK                    = CALLBACK
          SELECTIONS                  = SELTAB
     EXCEPTIONS
          LDB_NOT_REENTRANT           = 1
          LDB_INCORRECT               = 2
          LDB_ALREADY_RUNNING         = 3
          LDB_ERROR                   = 4
          LDB_SELECTIONS_ERROR        = 5
          LDB_SELECTIONS_NOT_ACCEPTED = 6
          VARIANT_NOT_EXISTENT        = 7
          VARIANT_OBSOLETE            = 8
          VARIANT_ERROR               = 9
          FREE_SELECTIONS_ERROR       = 10
          CALLBACK_NO_EVENT           = 11
          CALLBACK_NODE_DUPLICATE     = 12
          OTHERS                      = 13.
IF SY-SUBRC <> 0.
WRITE: 'Exception with SY-SUBRC', SY-SUBRC.
ENDIF.
FORM CALLBACK_LFB1 USING NAME TYPE LDBN-LDBNODE
                          WA    TYPE LFB1
                          EVT   TYPE C
                          CHECK TYPE C.
CASE EVT.
   WHEN 'G'.
      WRITE: / WA-BUKRS, WA-LIFNR.
      ULINE.
    WHEN 'L'.
      ULINE.
ENDCASE.
ENDFORM.
FORM CALLBACK_BSIK USING NAME TYPE LDBN-LDBNODE
                            WA    TYPE BSIK
                            EVT   TYPE C
                            CHECK TYPE C.
WRITE: / WA-BELNR.
ENDFORM.
returns:
ZFI_IF0005_NEW
2001 300000638
1900000006
Why the results are not same? I use the same para.

Hi,
Please format your code and paste it again.
KR Jaideep,

FM LDB_PROCESS

Similar Messages

Maybe you are looking for