Regarding LDB

Hi Gurus....
Iam using Standard logical database DDF for customer payment. by using one print program. in my print program i wrote GET BKPF
after that i wrote CHECK BKPF-BELNR IN DOcument.
problem was wtaht ever i given document number is available in BKPF table but
ldb returns other than that velue....
how to debugg the logicaldatabases (LDB)
urgent please
nagaraju

Hi Nagaraju,
I think there is no way to debug LDBs.
Regards,
Satish

Similar Messages

Regarding LDB selection screen

Hi All,
I copied a standard LDB program "RCATSCMP".
I have a date fields in selection screen.
When i debuged the standard program i am getting the date values PN-BEGDA and PN-ENDDA.
but when iam debugging my program iam not getting any values for these fields.
How to get these values.
Thanks in Advance
kiran i

Hi Kiran,
Please check the attributes of the copied program
and see whether it has logical data base 'PNP' is
there are not.
Thanks & Regards,
Siri.

Regarding LDB pnpce

hi experts,
i m in need to create a report means i have to design the
screen,in which i have to use LDB pnpce for HR,but if i select
program type "module pool" in the report attributes the filed
LDB name is not coming means but when i select executable the LDB field is coming but when i select type module pool the it is not coming
....plz help me is there any way so that i can use ldb as well
as module pool report type...............

Hi
you can call even LDB by using FM LDB_PROCESS. then you can attach the report to screen that you have designed.
what you have to do is goto SE38---> Create a new report of type executable and don't select any LDB .
2. Call teh function module LDB_PROCESS from the report and pass teh LDb name to this Fm
[further Information|http://help.sap.com/saphelp_nw70/helpdata/en/64/237f8cd43711d1950b0000e8353423/content.htm]
Regards
Pavan

Regarding LDB in webdynpro

Hi,
like LDB(PNP,PCH,PAP etc) in se38 Report for HCM module is there any standard way to declar a LDB in webdypro report.Kindly help me if anybody knows...
Regards,
Raj.

Hi,
Post this in WebDynpro forum for the quick replies......

Regarding LDB screen

Hi,
I want to add some selection screen parameters and hide or remove some existing parameters while using the LDB : PNP.
I did a search on this and everyone talked about changing the report categories but i could not find how to change the report categories.
I am new to HR and it might be a simple answer but I am stucked up.
Please let me know.
thanks in adv.

Hi
Below are the steps to create report category,
     Create report category by using HR Report Category button, select Master data (info type) and click on Create Report Category button.
     Create new report category in customer namespace (starting with 9) and click on allowable selection criteria and add the required fields. These fields will be displayed on selection screen.
     Add personnel area, personnel subarea, employee group, employee subgroup and personnel number to report category.
     Save the report category and select the same on attributes screen.
Reward if useful

Regarding ldb pnp

hi experts,
i m developing a hr report using pnp ldb,no doubt with the help of this ldb we get standard selection screen but here what i want that in this selection screen only payroll area and personel number sud come for this what sud i do for changing the selection screen......plz help me...

Hi,
In at selection-screen output, you try loop at screen.Inside that if screen-name is
PNPABKRS, then make screen-active = 1 otherwise, screen-active = 0.Simlarly in debugging you find out the lables for the input fields and then make it as active.
tables pernr.
at selection-screen output.
loop at screen.
if screen-name CS 'PNPABKRS'.
screen-active = 1.
else.
screen-active = 0.
endif.
modify screen.
endloop.endloop.

Regarding ldb pch (include DBPCHSEL for selection screen)

hi experts,
i am developing report for training and event mgmt details for this i m using ldb pch and include DBPCHSEL for standard selection screen what i want that in this include extra parameters & select-options/selection fields for input are already declared but i dnt want all of these plz help me how to remove extra selection fields which i dnt want on my customized report i want only one to two selection fields.
plz help me how to remove these extra fields

dear amit,
ven ever u use ldb "pch" it is not asking for report category means it wnt allow u create a report category.then plz gve another solutions.

Regarding ldb pnpce and my customized infotype

i have created my own infotype name '9777' and with the help of
'hr_infotype_operation' i m inserting the data into this infotype
now i m creating a report in which i m using ldb pnpce,
but after the execution of GET PERAS the infotype table p9777
is not populating but except this other infotypes tables are populating
,plz help me to sort out this problem.

hi after the bapi did you used the commit .
use this for the creation of an employee
BAPI_EMPLCOMM_CREATE
o give your code here

Hi regarding ldb

gm gurus,
            i m seeing a report that is related to ldb ,in which some coding portion i m nt able to understand....i m sending dat coding portion ...plz help me n let me know...thnx in advance...
DATA mylist LIKE pc261 OCCURS 0 .
DATA pay TYPE REF TO cl_pay.
CREATE OBJECT pay.
CALL METHOD pay->read_result
IMPORTING
    list = mylist.
CALL METHOD pay->write_result
EXPORTING
    list = mylist.

Ravi,
This is Object oriented programming.
DATA pay TYPE REF TO cl_pay.
cl_pay -
this is class name..
DATA pay TYPE REF TO cl_pay.---Here pay is the reference variable of the class
This is pointer to the class.
CREATE OBJECT pay.
creating the object for the class.
Note reference variable name and object name should be same.
By this object you can call all variables and methods of class.
CALL METHOD pay->read_result
IMPORTING
list = mylist.
Here calling the method read_result by object "pay" by passing the parameters list.
CALL METHOD pay->write_result
EXPORTING
list = mylist.
Just like above.
Methods are some what like function modules .
Pls. mark if useful

Regarding LDB PCH

Hi,
i need to hide all the defualt select options for LDB PCH and add the custom select potions.
how to hide the default select options completely.
Thanks in advance.

Hi Ajay,
Go To Reports Attribute -
> You will see field Selection screen --- enter screen no 901 ..as empty selection screen.
~Bhawanidutt

Regarding LDB's

Hi All,
Can we make use of LDB's on any type Tables i.e transparent,cluster,pooled tables?
Thanks in Advance
Kishore

Hi
Refer this link
http://help.sap.com/saphelp_nw70/helpdata/en/9f/db9b5e35c111d1829f0000e829fbfe/content.htm
Thanks
Vasudha

Removing LDB from proram attribute

Hi experts,
My requirement is to convert a LDB (PCH) report into a normal report and to do some changes in the converted report.
Can anyone tell me how to remove the LDB name mentioned in the program attributes. I got the following error message when i tried to remove the LDB name from the program attribute.
"Unable to specify selection screen (no logical database given)"

Thanks. After removing the selection screen number, i can able to remove the LDB name also.
I have one more doubt regarding LDB. Is there any way to keep the LDB, but to hide the standard selection screen provided by the LDB.
I want to create my own selection screen by overriding the LDB selection screen (all selection screen fields need to be removed), but i want the GET objec coding to be triggered by the LDB.
Is there any way to acieve this?
Edited by: Jessica Rose on Dec 30, 2010 2:22 PM

LDB REPORT

HI FRIENDS
I NEED A HELP REGARDING LDB THAT I WANT TO USE IN MY REPORT FOR PERFORMANCE ENHANCEMENT . CAN YOU PLEASE SEND ME A REPORT THAT HAVE USED LDB .ACTUALLY I HAVE NEVER USED LDB .
THANKS IN ADVANCE

Hai manish,
Here is an LDB program....
TABLES SPFLI.
SELECT-OPTIONS S_CARR FOR SPFLI-CARRID.
TYPE-POOLS: RSDS, RSFS.
DATA: CALLBACK TYPE TABLE OF LDBCB,
 CALLBACK_WA LIKE LINE OF CALLBACK.
DATA: SELTAB TYPE TABLE OF RSPARAMS,
 SELTAB_WA LIKE LINE OF SELTAB.
DATA: TEXPR TYPE RSDS_TEXPR,
 FSEL TYPE RSFS_FIELDS.
CALLBACK_WA-LDBNODE = 'SPFLI'.
CALLBACK_WA-GET = 'X'.
CALLBACK_WA-GET_LATE = 'X'.
CALLBACK_WA-CB_PROG = SY-REPID.
CALLBACK_WA-CB_FORM = 'CALLBACK_SPFLI'.
APPEND CALLBACK_WA TO CALLBACK.
CLEAR CALLBACK_WA.
CALLBACK_WA-LDBNODE = 'SFLIGHT'.
CALLBACK_WA-GET = 'X'.
CALLBACK_WA-CB_PROG = SY-REPID.
CALLBACK_WA-CB_FORM = 'CALLBACK_SFLIGHT'.
APPEND CALLBACK_WA TO CALLBACK.
SELTAB_WA-KIND = 'S'.
SELTAB_WA-SELNAME = 'CARRID'.
LOOP AT S_CARR.
MOVE-CORRESPONDING S_CARR TO SELTAB_WA.
APPEND SELTAB_WA TO SELTAB.
ENDLOOP.
CALL FUNCTION 'LDB_PROCESS'
 EXPORTING
 LDBNAME = 'F1S'
 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_SPFLI USING NAME TYPE LDBN-LDBNODE
 WA TYPE SPFLI
 EVT TYPE C
 CHECK TYPE C.
CASE EVT.
 WHEN 'G'.
 WRITE: / WA-CARRID, WA-CONNID, WA-CITYFROM, WA-CITYTO.
 ULINE.
 WHEN 'L'.
 ULINE.
ENDCASE.
ENDFORM.
FORM CALLBACK_SFLIGHT USING NAME TYPE LDBN-LDBNODE
 WA TYPE SFLIGHT
 EVT TYPE C
 CHECK TYPE C.
WRITE: / WA-FLDATE, WA-SEATSOCC, WA-SEATSMAX.
ENDFORM.
The program is written to read data using the logical database F1S. The structure of F1S is:
A program-specific selection screen is defined at the beginning of the program. This requires the TABLES statement. Next, the required variables are defined for the interface.
The internal table CALLBACK is filled so that various callback routines are called in the program for the two nodes SPFLI and SFLIGHT. For SPFLI, the routine is to be called for GET and GET_LATE, for SFLIGHT, only at the GET event.
The internal table SELTAB is filled with values for the node SPFLI from the selection table S_CARR from the program-specific selection screen.
The program then calls the function module LDB_PROCESS with these parameters.
The subroutines CALLBACK_SPFLI and CALLBACK_SFLIGHT serve as callback routines. The interface parameter WA is fully typed, so you can address the individual components of the work areas. The events GET and GET LATE are handled differently in CALLBACK_SPFLI.
This link may help you...........
http://help.sap.com/saphelp_nw04/helpdata/en/64/237f8cd43711d1950b0000e8353423/frameset.htm
Regards,
Srikanth.
Reward points if at all it is useful.

Idea about Logical DataBase

Hi,
Can, programming with LDB, be considered as an object programming.. just VB, which is an object programming language.
That is we r creating an Object directly and using when ever we want. It is different from OOP where we create a class and instantiate the class to create an object.
My next question is:
There are 2 transactions which we will create, which are basically same except for a text field.
First transaction is posting. And the second one is a reverse posting. In the second transaction we have the reason for reverse posting.
I think in this case we can use LDB and it is the typical scenario where we can apply LDB concept.
Please evaluate me.
-Naveen.

Hi NaveenKumar,
 Logical databases are special ABAP programs that retrieve data and make it available to application programs. The most common use of logical databases is to read data from database tables by linking them to executable ABAP programs.
 However, from Release 4.5A, it has also been possible to call logical databases using the function module LDB_PROCESS. This allows you to call several logical databases from any ABAP program, nested in any way. It is also possible to call a logical database more than once in a program, if it has been programmed to allow this.
 Logical databases contain Open SQL statements that read data from the database. You do not therefore need to use SQL in your own programs. The logical database reads the program, stores them in the program if necessary, and then passes them line by line to the application program or the function module LDB_PROCESS using an interface work area.
Tasks of Logical Databases
1.Reading the same data for several programs.
2.Defining the same user interface for several programs.
3.Central authorization checks
4.Improving performance
First part of your question

 So,if i am not wrong, LDB cannot be completely considered as object oriented programmming.
 I have highlighted some important points above
For understanding this in detail you can go through the sap help .(if you donot know go through the below path
sap library
+ Basis Components
 -Abap Programing and runtime enviornment
 -BC-ABAP Programming(noe serach for ldb
Now your second part of question.
 In the scenario which you have mentioned we can use ldb.But i am not sure whether it is a typical scenario of ldb.LDB is just a specific access routine to support database access for some application (report generation) needs.We can define a logical database to shorten our ABAP coding .
 Here I am mentioning a link which shows a complete implementation of an LDB.
http://homepages.wmich.edu/~r2raviko/HandsOnQuest/HO9.doc
 I suppose after going through the reply(or sap help) and the link mentioned above all your doubts regarding LDB will be cleared.
Thanks & Regards
Pawan P. Khilari
*Please Mark Helpful Answer

Regarding Selection views in LDB

Hi Experts,
What is use of Selection Views in LDB ??
and how can we generate different Selection Views in LDB because i am getting only two Options either SAP or CUS for every LDB ??
I want to declare 4-5 and how to use Those Selection Views ( as by default it takes SAP one or newly generated one)
Thanks,
Regards,
Anil Sonesar

Hi Suny,
When I run the T-code FBL1N at my place and click on Dynamic selections button,what I see that there are all the three options--Vendor Master,Company Code and Documents available.
You need to observe that against Vendor number there is no input box available but all the fields available under it till Company Code belong to Vendor Master.Similarly,all the fields mentioned under Comaony Code belong to Company Code and likewise all the fields mentioned under Documents like Special G/L Indicator,Assignment,Document number etc. belong to Document.
In case you have any further clarifications,do let me know.
Regards,
Puneet Jhari.

Regarding LDB

Similar Messages

Maybe you are looking for