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

Similar Messages

About Logical Database

Hi gurus,
How to restrict the retrieving of data using logical database? I mean, i have a requirement of retrieving Open transaction data only for my program. i used CHECK keyword as well as IF statement but it doesnt work...can anyone tells me those commands that i could use for logical database?? then pls give me some idea also for summation of data (Quantity)
thanks,
nips

Hi,
You simply add the check in the relevant GET event of the LDB.
For example, you may have an event for DOCUMENT as follows.
GET DOCUMENT.
check document-ref in s_ref.
S_REF being your new select option.
a®

Problem about logical database programming

Dear all,
I have a logical database PRPS_R which contail PRPS and some additional fields.
In my abap report, I call this logical database by "GET PRPS_R". Can I ask how to perform sorting to the logical database in ABAP report?
Thanks
Sunny

PRPS_R is a structure of logical database PSJ
there is a user-exit available EXIT_FDBPS000_001

How to retrieve data using logical database and custom select options

Hi all,
I have a selection screen which is displayed by logical database PSJ and I have two select options of my own. I need to retrieve data based on both selection screen of logical database and my own select options. How can I do it?
Thanks in advance.

Hai Gupta
Check the following Document & Links
1. A logical database is in fact
a program only.
2. This LDB provides two main things :
a) a pre-defined selection screen
which handles all user inputs and validations
b) pre defined set of data
based upon the user selection.
3. So we dont have to worry about from
which tables to fetch data.
4. Moreover, this LDB Program,
handles all user-authorisations
and is efficient in all respects.
5. tcode is SLDB
good info about Logical Database. you can check the link.
http://www.geekinterview.com/question_details/1506
http://help.sap.com/saphelp_46c/helpdata/EN/35/2cd77bd7705394e10000009b387c12/frameset.htm
Re: How to Create and Use ldb in reports?
Re: Logical databases
http://help.sap.com/saphelp_46c/helpdata/en/9f/db9bed35c111d1829f0000e829fbfe/frameset.htm
Functions for displaying and changing logical databases:
Call Transaction SE36 or
Choose ABAP Workbench -> Development -> Programming environ. -> Logical databases
Interaction between database program and report:
During program processing, subroutines are performed in the database program and events are executed in the report.
To read data from a database tables we use logical database.
A logical database provides read-only access to a group of related tables to an ABAP/4 program.
advantages:-
The programmer need not worry about the primary key for each table.Because Logical database knows how the different tables relate to each other,and can issue the SELECT command with proper where clause to retrieve the data.
i)An easy-to-use standard user interface.
ii)check functions which check that user input is complete,correct,and plausible.
iii)meaningful data selection.
iv)central authorization checks for database accesses.
v)good read access performance while retaining the hierarchical data view determined by the application logic.
disadvantages:-
i)If you donot specify a logical database in the program attributes,the GET events never occur.
ii)There is no ENDGET command,so the code block associated with an event ends with the next event
statement (such as another GET or an END-OF-SELECTION).
1. transaction code SLDB.
2.enter name z<ldb-name>
3.create
4.short text
5.create
6. name of root node (here Ekko)
7. enter short text (f6)
8.node type -> data base table.
9.create
10 change logical DB
riht click on ekko and insert node
here node name ekpo
11.create
12. click on selections
13. press no Should the changed structure of Z<ldb name> be saved first.
14.select tables which you want to join.
15.transfer
16 now you have to o to coding part.
17. save
activate.
19.click to src code
double click on first include and activate
Regards
Sreeni

Selection part of Logical Database

I read about logical database somewhere on the net but it was not so clear. Can anyone explain to me about the selection part of the logical database???

Logical databases are special ABAP programs that retrieve data and make it available to application programs. The most common use of logical databases is still to read data from database tables and linking them to executable ABAP programs while setting the program contents. You edit logical databases using the Logical Database Builder in the ABAP Workbench.
However, since Release 4.5A, it has also been possible to call logical databases independently of this tool 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. This is particularly useful for executable programs, allowing them to use more than one logical database and process a database more than once.
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.
http://help.sap.com/saphelp_nw2004s/helpdata/en/9f/db9b5e35c111d1829f0000e829fbfe/content.htm
A logical database is a special ABAP/4 program which combines the contents of certain database tables. You can link a logical database to an ABAP/4 report program as an attribute. The logical database then supplies the report program with a set of hierarchically structured table lines which can be taken from different database tables.
GO THROUGH LINKS -
http://www.sap-basis-abap.com/saptab.htm
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9bfa35c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9b5e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c6/8a15381b80436ce10000009b38f8cf/frameset.htm
/people/srivijaya.gutala/blog/2007/03/05/why-not-logical-databases
Re: **LDB**
www.sapbrain.com/FAQs/TECHNICAL/SAP_ABAP_Logical_Database_FAQ.html
www.sap-img.com/abap/abap-interview-question.htm
www.sap-img.com/abap/quick-note-on-design-of-secondary-database-indexes-and-logical-databases.htm
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9b5e35c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/9f/db9bb935c111d1829f0000e829fbfe/content.htm
Logical databases are SAP standard programs that are desinged with selections screens that helps easy retrival and access of data from various tables in and efficient manner.
You can get to know more about the logical databases from the SAP documentation or the following links.
A logical database is a special ABAP/4 program which combines the contents of certain database tables. You can link a logical database to an ABAP/4 report program as an attribute. The logical database then supplies the report program with a set of hierarchically structured table lines which can be taken from different database tables.
Advantages of Logical database -
1) No need of programming for retrieval , meaning for data selection
2) Easy to use standard user interface, have check completeness of user input.
Disadvantages
1) Fast in case of lesser no. of tables But if the table is in the lowest level of hierarchy, all upper level tables should be read so performance is slower.
GO THROUGH LINKS -
http://www.sap-basis-abap.com/saptab.htm
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9bfa35c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9b5e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c6/8a15381b80436ce10000009b38f8cf/frameset.htm
1. A logical database is in fact
a program only.
2. This LDB provides two main things :
a) a pre-defined selection screen
which handles all user inputs and validations
b) pre defined set of data
based upon the user selection.
3. So we dont have to worry about from
which tables to fetch data.
4. Moreover, this LDB Program,
handles all user-authorisations
and is efficient in all respects.
5. tcode is SLDB
good info about Logical Database. you can check the link.
http://www.geekinterview.com/question_details/1506
http://help.sap.com/saphelp_46c/helpdata/EN/35/2cd77bd7705394e10000009b387c12/frameset.htm
Re: How to Create and Use ldb in reports?
Re: Logical databases
http://help.sap.com/saphelp_46c/helpdata/en/9f/db9bed35c111d1829f0000e829fbfe/frameset.htm
Functions for displaying and changing logical databases:
Call Transaction SE36 or
Choose ABAP Workbench -> Development -> Programming environ. -> Logical databases
Interaction between database program and report:
During program processing, subroutines are performed in the database program and events are executed in the report.
To read data from a database tables we use logical database.
A logical database provides read-only access to a group of related tables to an ABAP/4 program.
advantages:-
The programmer need not worry about the primary key for each table.Because Logical database knows how the different tables relate to each other,and can issue the SELECT command with proper where clause to retrieve the data.
i)An easy-to-use standard user interface.
ii)check functions which check that user input is complete,correct,and plausible.
iii)meaningful data selection.
iv)central authorization checks for database accesses.
v)good read access performance while retaining the hierarchical data view determined by the application logic.
disadvantages:-
i)If you donot specify a logical database in the program attributes,the GET events never occur.
ii)There is no ENDGET command,so the code block associated with an event ends with the next event
statement (such as another GET or an END-OF-SELECTION).
1. transaction code SLDB.
2.enter name z<ldb-name>
3.create
4.short text
5.create
6. name of root node (here Ekko)
7. enter short text (f6)
8.node type -> data base table.
9.create
10 change logical DB
riht click on ekko and insert node
here node name ekpo
11.create
12. click on selections
13. press no Should the changed structure of Z<ldb name> be saved first.
14.select tables which you want to join.
15.transfer
16 now you have to o to coding part.
17. save
activate.
19.click to src code
double click on first include and activate
Regards
Vasu

Your experience about Standby Database (Logical).

Hi,
As expressed in the subject of the thread, I'd like to get some feedback about Logical Standby.
One of the databases (A) here has a setup with a Physical Standby (B). In order to lighten the workload on A, i want to "upgrade" B to a Logical Standby. The procedure is already defined, tested and functionnal. But as I never managed a Logical Standby, it would be great if you could share your experience about:
1/ A's workload: Will there be a big overhead due to log treatments (and supplemental log data)?
2/ LAS: Will it take longer to apply an archived redo log to Logical B than it takes on the Physical B?
3/ I can't set the hardware on B's host to the same level as it's on A's host.
A has (6cpu, 20GiB RAM, half for SGA)
Physical B has (2cp, 9GiB RAM, 5GiB for SGA)
Logical B will have (3cpu, 12GiB RAM, xxxGiB SGA)
The load on B will be very very less than it is on A. Knowing A perfs is O.K., will B perf on reporting be O.K.?
4/ my target for backup is now B. When the "upgrade" will be finished, would you advise to continue the backup on the Logical Standby, or to switch to a backup via (RMAN/HotBackup/...) ?
5/ Any other advice you could give :-)
Thanks,
Yoann.

Hi Yoann,
Some time ago I created a logical database for Oracle 9.2.0.4 db on RH Linux then on 9.2.0.6 ver (same OS). It was very tempting to decrease loading on primary database through using logical standby, but It was not moved to production. I stuck with some problems when transactions stopped because of some inconsistency (I used transaction consistency set to NONE because of performance) and there were a couple of them between a hundred of tables. After that I tried to create a database link upon the primary database, but it was not apt to use with the same procedures to execute.
Regarding questions:
1. I did not find the big overhead, but a lot of additional actions should be done due to maintenance tables w/o PK on LGSTBY
2. Difficult to say ...
3. I had LGSTBY half of power of primary
4. I will not you advise to backup LGSTBY because of some possible problems with transactions, maintenance etc. better to use RMAN on primary or physical standby
5. Try to test 10g logical standby (I have read that there is no need to freeze the primary database during logical standby creation)
Hope this helps,
Andrey

Regarding Logical database and select statement..

Hi
Experts.
i would like to know the diff b/w logical data base & select statement while using report.
wt is the use of logical databases in R/3. is there   any   advantage used in the reports.
Thanks & Regards..
Spandana.

Dear Spandana,
Go through the below description of LDB. I hope you wil get a fair amount of idea.
SAP comes loaded with all the extras. Among the extras that are most helpful to IT managers are all the access routines needed to pull any business object that managers can think of out of SAP databases. However, SAP has not thought of everything where your particular applications are concerned. SAP organizes its standard database tables to service business units based on conventional business applications. Itu2019s likely your business requires something new, perhaps even something exotic. In that case, you will need to create a new database, using information from different places. Basically, you need a logical database. You need to create a virtual business data object repository consisting of a new kind of record or table that suits your purposes. In addition, the repository should be composed of information that is actually stored in a number of different locations, none of them necessarily logically associated with one another. Letu2019s take a closer look at creating logical databases.
A case for a logical database
Suppose my company manufactures widgets of the most obscure variety, and they are components of other widgets. I sell my widgets as raw material for the more sophisticated widgets built by others, but in some cases I actually partner with other manufacturers in creating yet another class of widget. Now, in my world, I consequently have customers who are also partners. I sell to them and I partner with them in manufacturing and distribution. Also, I need an application that uses both of these dual-use relationships.
Essentially, I have a customer database and a partner database. Neither contains records that are structured to contain the identifying particulars of the other. Thus, I need a hybrid database that gives me tables detailing these hybrid relationships. What can I do? I can go the long way around and write a new database, pulling information from both and creating new objects with a customized program that I write by hand. However, this process is cumbersome and contains maintenance issues. On the other hand, I can use SAPu2019s logical database facility, create my logical database in a couple of minutes, and have no maintenance issues at all.
Logical database structures
There are three defining entities in an SAP logical database. You must be clear on all three in order to create and use one.
u2022     Table structure: Your logical database includes data from specified tables in SAP. There is a hierarchy among these tables defined by their foreign keys (all known to SAP), and you are going to define a customized relationship between select tables. This structure is unique and must be defined and saved.
u2022     Data selection: You may not want or need every item in the referenced tables that contributes to your customized database. There is a selection screen that permits you to pick and choose.
u2022     Database access programming: Once youu2019ve defined your logical database, SAP will generate the access subroutines needed to pull the data in the way you want it pulled.
Creating your own logical database
ABAP/4 (Advanced Business Application Programming language, version 4) is the language created by SAP for implementation and customization of its R/3 system. ABAP/4 comes loaded with many predefined logical databases that can construct and table just about any conventional business objects you might need in any canned SAP application. However, you can also create your own logical databases to construct any custom objects you care to define, as your application requires in ABAP/4. Hereu2019s a step-by-step guide:
1.     Call up transaction SLDB (or transaction SE36). The path you want is Tools | ABAP Workbench | Development | Programming Environment | Logical Databases. This screen is called Logical Database Builder.
2.     Enter an appropriate name in the logical database name field. You have three options on this screen: Create, Display, and Change. Choose Create.
3.     Youu2019ll be prompted for a short text description of your new logical database. Enter one. Youu2019ll then be prompted to specify a development class.
4.     Now comes the fun part! You must specify a root node, or a parent table, as the basis of your logical database structure. You can now place subsequent tables under the root table as needed to assemble the data object you want. You can access this tree from this point forward, to add additional tables, by selecting that root node and following the path Edit | Node | Create. Once youu2019ve saved the structure you define in this step, the system will generate the programming necessary to access your logical database. The best part is you donu2019t have to write a single line of code.
Watch out!
The use of very large tables will degrade the performance of a logical database, so be aware of that trade-off. Remember that some tables in SAP are very complex, so they will be problematic in any user-defined logical database.
Declaring a logical database
Hereu2019s another surprising feature of logical databases: You do not assign them in your ABAP/4 Code. Instead, the system requires that you specify logical databases as attributes. So when you are creating a report, have your logical database identifier (the name you gave it) on hand when you are defining its attributes on the Program Attributes screen. The Attributes section of the screen (the lower half) will include a Logical database field, where you can declare your logical database.
Logical databases for increasing efficiency
Why else would you want to create a logical database? Consider that the logical databases already available to you begin with a root node and proceed downward from there. If the data object you wish to construct consists of items that are all below the root node, you can use an existing logical database program to extract the data, then trim away what you donu2019t want using SELECT statementsu2014or you can increase the speed of the logical database program considerably by redefining the logical database for your object and starting with a table down in the chain. Either way, youu2019ll eliminate a great deal of overhead.
Regards
Arindam

Logical database EQI (equipment) .. I dont want to use the default selecti

i am using Logical database EQI (equipment) its realated to PM module.....
i dont want to use the default selection screen.
instead i want to process my own selection screen inputs..
(ie..) i want to fetch the data using the GET event using my own selection screen inputs.
my selection screen inputs is   equipmentnumber (equnr)
and the output list : 1.equnr      "equipment number
                              2.shtxt       "Equipment Description
                              3.tplnr        "Functional Location
                              4.pltxt        "Functional Location Description
                              5.qmnum    "Notification Number
                              6.qmtxt      "Notification Description
             and so on ..........
how to do this ... can any one give sample code... or logic

Hi Victor,
I have a simple solution for this.i think it will help you.Do u have any idea about query designer in SAP.
by using it we can satisfy u r reuqirement.follow the below steps.
1)Go to SQ01
2)In the screen click on QuickViewer option.then you will go to another screen.
3)In that screen give any name starting with 'Z' in the QuickView box and then click on create.
4)In the dialogbox enter title and comments and then select LogicalDatabase as the DATASOURCE and give DataSourceLogicalDatabase as EQI.check the radio button Basis Mode and then click on ok.
5)then on the screen in the first half of leftside you will get another screen with the columns DATAFIELDS,LISTFIELDS,SELECTIONFIELDS,TECHNICALNAME.
6)In the DATAFIELDS column expand the tree,then u can see the fields what we have,and what you want.and also you can see the check boxes in front of the columns LISTFIELDS,SELECTIONFIELDS.
7)LISTFIELDS means the output fields,SELECTIONFIELDS means the selection screen fields(equnr).
check the checkboxes as per u r requirement and click on execute.
8)then a progam will be created.to know the program name after executing the program GO TO
SYSTEM->STATUS.then u can see the program name there.
If u know all these,let me know so that i can try for another solution.
Thanks,
N.K.C

Asset Reporting - Copying Logical Database ADA

Can you please assist with the following query? Im trying to include the following standard R3 ffields within standard R3 reports AR01 (Asset Balances) & AR18 (Depreciation Simulation):
                                Table            Field Name            Data Element
Serial Number            ANLA            SERNR                AM_SERNR
Inventory Number       ANLA            IVNR                   INVNR_ANLA
To date I have been unsuccessful in my endeavours.
I have been discussing with an ABAPer and have been discussing the creation of Z transactions to give me the information Im looking for.
Im looking for help, assistance and expertise whether the following would be recommended or even technically feasible.
·     Is it possible to copy logical database ADA to say ZADA (if yes how would I or the ABAPer go about this)?
·     Is there a way to link existing R3 reports to the new logical database
As the majority of the R3 reports appear to be linked to ADA the aim is to amend this once and not require creating lots of Z reports.
Any help you could provide would be greatly appreciated
Best regards,
Paul

Hi Paul,
this is strange, what release are you on?
I have just checked AR01 on ECC 6.0, and it offers everything you need. On the selection screen of AR01, you can add selection criteria on both Serial number and Inventory number. Plus, you can display both fields in the ALV list.
The data may be stored on table ANLA physically, but the logical database ADA is using a structure (ANLAV) instead. Both SERNR and INVNR are available in that structure. On the selection screen, you have to use the Dynamic selections button. And in the ALV list, you simply add the 2 columns, best idea wold be to save it as a variant for future use.
Anyway, logical databases can be copied in SE36, you simply have to press the Copy button The more critical issue is how to link standard reports to the new LDB. The answer is, no way. Instead, you should copy some of your favorite standard reports, and change the LDB in the copies.
But, I really do not think you need this, as ADA can provide you with the information required out of the box.
Hope that helps, points welcome
Csaba

Problem with logical database ADA

I am trying to create query with asset values and master data fields but when trying to use logical database ADA I am getting error No component exists with the name "VALUE0". .InfoSet Cannot be Used for InfoSet Query.
Does anyone have an idea about such problem?

Hi,
The message "No component exists with the name "VALUE0"" created when you omit to edit the field group only happens if no field is assigned to a fieldgroup, it should not appear if you add at least one field to a field group.
regards Bernhard

Any logical database including BKPF table

Hi,
please write me about the logical database that includes BKPF table in it.
Thanks.
deniz.

Hi Deniz,
The following LDBs have included BKPF table in E6S IDES.
BMM                    Documents for Number
BRF                    Document Database
BRM                    Accounting Documents
DDF                    CUSTOMER DATABASE
KDF                    Vendor Database
SDF                    G/L Account Database.
by
Prasad GVK.

Change selection screen in LDB (KDF logical database - NOT HR)

Hi All,
Iu2019d like to use KDF logical database to keep the dynamic selections since user wants to use it but I need to change the selection screen itself. The existing variants for KDF donu2019t meet the user requirements. Some fields I need to hide some add. Like I want to u201Cremoveu201D the field u2018Posting periodu2019 (MONAT) (which is available in dynamic selection screen) and put it on the u201Cmainu201D selection screen.
Do I need to create my own logical database or there is a way around?
Could someone give me a practical advice or sample of solution?
Thanks a lot.

Thanks Himanshu,
I did as you suggested but problem is that it does not allow me to hide the whole block.
I have 3 filelds actually on block KD_0 I need to hide (its from selection screen of KDF logical database.)
SELECT-OPTIONS: KD_LIFNR FOR LFA1-LIFNR MATCHCODE OBJECT KRED.
SELECT-OPTIONS: KD_BUKRS    FOR LFB1-BUKRS.
SELECTION-SCREEN END OF BLOCK KD_0.
PARAMETERS KD_INDEX AS SEARCH PATTERN FOR TABLE LFA1.
What I did is below. I used sp instead of u201C=u201D since it has many screen for field KD_LIFNR(for frame, text etc).
And when I did just for KD_LIFNR it was hidden but when I did the same for KD_BUKRS it was not hidden . The field has stars u201C*********u201D in it.
Same happen with KD_INDEX. The name of the field is hidden but field not and it filled with ********. Do you have any ideas what it can be?
I debugged it to catch all screen names but no luck
loop at screen.
    if screen-name cp 'KD_LIFNR' or
    screen-name cp 'KD_BUKRS' or
    screen-name cp 'KD_INDEX' or
    screen-name = '%B000003_BLOCK_1000' or
    screen-name = 'SSCRTEXTS-FRAME_TEXT' or
    screen-name = 'SSCRTEXTS-MCID_TEXT' or
    screen-name = 'SSCRTEXTS-STRNG_TEXT' or
    screen-name = 'SSCRFIELDS-SEARCH_BTN' or
    screen-name = '%B025008_BLOCK_1000' or
    screen-name = '%F021010_1000' or
    screen-name = 'ALCUR' or
    screen-name = '%F022012_1000' or
    screen-name = 'EXCDT' or
    screen-name = 'SSCRFIELDS-UCOMM'.
      screen-invisible = '1'.
      modify screen.
    endif.
endloop.

Logical Database PNP. HR and Unicode

Hi,
currently we are checking all programs to make them unicode compliant. Using the logical database PNP a lot of macros is loaded automatically. One of them is
rp_provide_from_last (or rp_provide_from_frst) to get the last record in a specifed time-interval. The existance is stated in varaible named pnp-sw-found, it is 0 if no record was found and 1 if there is one in existance.
Checking the program (normal syntach check and extended syntax check) leads to the warning that varaibale names with a hyphen are no longer allowed in unicode programs if its not a structure (and pnp-sw-found is not). The program is doing well, and transaction UCCHECK does not mention this error/warning at all. Has someone experience with that issue and perhaps a solution?
cu
Rainer

Thanks for the answers so far. Using PNPCE does not resolve my problem, cause we have a lot of own written reports and i just want to avoid to change them all.
And using PNPCE idoes not solve the problem, that i have to use pnp-sw-found, this one is still in existance and gives still the warning that thois is not unicode compliant.
Switching off the unicode flag is no good idea if we wanna go for unicode.
Anyone else with experience in unicode in the HR Area?

Selection Screen of PNP Logical database

Experts,
I am stuck up in filtering of data.
I am using PNP logical database in Adhoc Query, if I select Current Month as data selection than also it is giving all list of data..
Can anyone give Input to me.
it is urgent.
Point will revert for useful answer.
Hetal.

how about if u do this step
1. Goto- Attribute.
2. Click "Change"
3. Click 'HR Report Category'
4. Click 'Create Report Category'
5. Click 'new entries' for careating Report Category
5. Select newly create report category
6. Click the folder 'Definition of Organizational Selection'.
7. Click 'New entries'.
8. Here you assign the required fields to be displayed, for eg pywerks - personal area.
9. finally assign this newly created 'report category' in the screen you will get upon clicking 'HR report Category' button in the Program attribute screen.
Hope this may help you. I am not much into hr abap. but sharing the info which i am aware.

Logical Database - PNP, PCH, PNPCE

Hi Experts,
Im New to ABAP HR,
I would like to know about the logical databases we are using .
Logical Database - PNP, PCH, PNPCE, basic principles
If any body cud let me know about the differences , requiremnts , associated with these Logical databses will be much helpful for me.
Thanks
Rohini Devi
[email protected]

Hi Rohini...
Global Employee Programming
Thanks
Message was edited by:
Aslam Riaz

Idea about Logical DataBase

Similar Messages

Maybe you are looking for