Screen Change when using LDB - pnp

Hi ,
I am facing a strange problem.
I am using LDB -> pnp and HRIN0013 as Master data rep ,
in one of the programs that i developed.
The Screen and program behave fine in the development server.
Once i transport it to the production server, the Screen changes to something completely different.
What i noticed is that in attributes -->'Report category assignment' , HRIN0013 is not present.
This means that HRIN0013 has not been transported?
What can the problem be and how can i fix it?? I need to get this in by tommorow. Help will be highly appreciated.

Hi Sanchit,
when I change the report class in an HR report, the system tells me for the change request number.
This change request, introduces, I think, a new record in some customize tables, like t599C.
There must be a record in this table, for the report class that you create.
Hope this helps you,
Carles

Similar Messages

Adding a Button in the Application toolbar when using LDB for HR programs

Hi Experts,
I have a requirement to add a new button after execute button in the Application tool bar for the HR programs when using LDB PNP.
Normally when we are using LDB in our program we will get a extra button provided by SAP after the execyte button. When we are creating a new button for this by using the table fields sscrfields with the function key as 2 we are not able to see the new button.
can any one help me in this issue.

please post your relevant coding with respect to the button
A.

Filter Data using LDB PNP

Hi,
I'm looking to filter data in a report which uses LDB PNP.
When i enter the 'start dates' and 'end dates' the values goes into PN-BEGDA and PN-ENDDA respectively.
I want to know whether the GET PERNR statement will filter out the data based on 'start dates' and 'end dates'
or do i have to loop at each infotype and manually filter out.
varun

>
Rajesh Paruchuru wrote:
> [Here is the answer from SAP|http://help.sap.com/saphelp_47x200/helpdata/en/4f/d527ba575e11d189270000e8322f96/content.htm]
>
>
GET PERNR fills the internal tables of infotypes that are declared for
> each employee using the INFOTYPES statement. The internal infotype table
> is filled with all records existing between the lowest and highest
> system date. The internal table has the name Pnnnn, where nnnn is the
> infotype number
>
> - Rajesh.
That means its useless to give a selection criteria on the selection screen.
GET PERNR will get all records, means it will just filter the employee numbers nothing else, everything you will have to do manually by using loops.
Varun

Coding ABAP using LDB PNP and authorizations problems

This post requires a blend of ABAP and HCM skills.
When coding my own ABAP using LDB PNP, the LDB will provide me with the employees selected but will skip those for which I do not have access (regarding Authorizations settings) to one or more of the infotypes declared in the program.
As a programmer I would like to receive from the LDB the information that an employee is skipped so that I can handle the exception.
Do you know how can I get this information from the LDB?
Thanks

I dont know if PNP can do it but PNPCE can:
at END-OF-SELECTION call macro PNP_GET_AUTH_SKIPPED_PERNRS
it will provide a list of skiped PERNRs
for further info see docu PNPCE

Reading Locked records from HR table using LDB PNP

Hi,
I am trying to read the table pa0168 using LDB PNP.
But the problem is that get pernr staement does not retrieve locked records i.e where PA0168-sprps eq "X'.
Can anybody help me with this.
I have to use LDB so i don't want a solution of writing a select * for the pa0168 table.
hence i have to use get pernr statement but it should also retrieve locked records.
how can i achieve that.? please help
Thanks
GT
Message was edited by: GT

Hi GT,
In the START-OF-SELECTION event, set the parameter value
pnp-sw-ignorelockedrecords = 'N'.
Good Luck,
Suresh Datti
( Pl award points if the answer helps you )

IPhoto 6 Unable to Zoom in Full Screen Mode when using projector

When in full screen mode in iPhoto 6 I am able to zoom quite nicely but when I attach a projector I lose the slide for zooming. How do I zoom in full screen mode when using a projector?
Mac Book Mac OS X (10.4.9)

ParkerT
Given that the zoom works normally, this is not an iPhoto issue. The problem lies in the interaction between your MacBook and the Projector. You might have more luck posting on the MacBook forum
Regards
TD

Record selection in IT0000 (Actions) using LDB PNP

Hi Guys,
I am writing a report using LDB PNP, where I need to EXCLUDE the employees, if an action has been done on IT0000 for the reporting start date and end date.
Can anybody share the logic to do this using HR Macros or FM?
Thanks,
mini

Hi miniSAP!
I think this tip can help you.
You can make your job at follow form:
at "infotypes" declaration, use:
INFOTYPES: 0000 MODE N.
Inside "GET PERNR" event, you can get the informations using directly fm: HR_READ_INFOTYPE, because using "MODE N" at infotype declaration the standard system will not return any information about employee. In this form, you can make de filter of informations from fm HR_READ_INFOTYPE.
Best regards!

Look for a progarm that will let me have 2 moniters but one will lock on and will not change when using spaces

look for a progarm that will let me have 2 moniters but one will lock on and will not change when using spaces

ok so i have one moniter to the right of me and i want to keep my google chrome on that one but still be abel to use space on the many monter. cuz when you go to spaces it movies both moniter i hope that help and i hope that you can help me.

Obsolete statements while using LDB PNP

Hi,
I am using LDB PNP, while extended program check it is showing many obsolete statements like-
tables : PERNR.
infotypes
RP_PROVIDE_FROM_LAST.
What is the alternate to all these above statements.
I searched the forum, but could not found anything. Please provide example.
Thanks,

That will bevary from system settings, In the standard reports, it will never give you the error/warning/informaton messages. But custom programs it will give as a absolete, But i can see many experts will use the these Macro's, We are doing world largest HR implemetation, Still we are using the same, Not a problem, you can avoid those messages.
Only one way of avoiding is Using Provide statements.
Regards,
Mallikarjuna

Is it possible to ignore "Rigid relationships between attributes cannot be changed" when using ProcessUpdate for Dimension?

As per the title is it possible to ignore "Rigid relationships between attributes cannot be changed" when using ProcessUpdate for Dimension?
We have a case where very rarely an item might have been miscategorised so the brand is manually changed. We want this dimension to be rigid to speed up ProcessUpdate.
We do a ProcessFull each night, so it will get corrected then, but during the hourly updates we would just like to ignore this error if possible?

Hello,
The rigid relationship should be defined when the members will not change over time. Here are some threads regarding rigid relationship for your reference, please see:
Processing OLAP Cube: http://social.technet.microsoft.com/Forums/sqlserver/en-US/17a55593-9543-404e-a579-0a011965585d/processing-olap-cube?forum=sqlanalysisservices
Flexible and rigid relationship: http://social.msdn.microsoft.com/Forums/sqlserver/en-US/2d8f5443-065d-4485-9385-6f0b5fa417da/flexible-and-rigid-relationship?forum=sqlanalysisservices
If you have any feedback on our support, please click
here.
Regards,
Elvis Long
TechNet Community Support

Not being able to hear application audio on quicktime screen recording when using headset

Can someone tell me how to still hear the computer audio (like the application sound) on while using quicktime screen recording when using headset?
Someone help me please or tell me another application to do this with.

hi paula
your problem could be hardware/software. lets hope its software issue first and i'd like you to do these:
if you have personal files on volume c, copy/backup them. shut down your computer, press one key recover button to perform clean windows installation. then check if the issue still persists.
if you don,t want to use okr, you can use windows restore to restore your computer to previous restore points but if it's windows/virus issue, it may not help.

HOW TO KEEP SCREEN ON WHEN USING GPS OR SHOOTING THE VIDEO

I was wondering if there any setting I could leave the screen on when using GPS or shooting the video, I'm currently set backlight timeout is 2 mins. After 2 mins device will automatically out and I have to reenter the password for continue my video, This is very inconvenience when using GPS or shooting the video.
Is there any one out there can assist? thanks in advance.

Did you get an answer?

Our ipad 1 goes to a black screen periodically when using the internet.

Our iPad 1 goes to a black screen periodically when using the internet. We have to hit the home button and hope we end up back at the site we were previously at. We have updated the iPad, but it still happens. Any suggestions on a solution?

Try This...
Close All Open Apps... Sign Out of your Account... Perform a Reset... Try again...
Reset ( No Data will be Lost )
Press and Hold the Sleep/Wake Button and the Home Button at the Same Time...
Wait for the Apple logo to Appear...
Usually takes about 15 - 20 Seconds... ( But can take Longer...)
Release the Buttons...

Selection screen validation when using PNP LDB

Hi guys,
I want to validate my selection screen parameters.Thats is if somebody wants to run the program without giving any input parameters to the selection screen(trying to run the report with a blank screen) I want to pop up an error/information message so that it will return the selection screen.I am using PNP Logical database for my selection screen.Please help.Thanks in advance.
Thanks,
Karthik.

Welcome to SDN.
If you are using PNP logical data base then validating the fields will be little tricky...
You canc check all the other fields in START-OF-SELECTION and if they are empty return eroor. Remember all the field s on the scree... so I will suggest you to choose HR report Category accordingly.
Also,when it comes to date field then you need to check for the start and end dates rather than blank fields as SAP defaulted them to system start and end date.
Still, I will prefer to create a HE Report Category for the PNP database and use the screen while validating....that will be easy...

Change existence report LDB PNP to PNPCE

Hi HR experts !!!
We want to convert all the existence reports which are using <b>PNP</b> to <b>PNPCE</b>? Do you guys have idea how much time itll take? As we have around 1000 reports.
I need your input guys
Cheers
Usman

Usman,
I am also on HR project . Were also discussing the same thing !! but it looks like it need another project to change the LDB to PNPCE as reason being lots of reports are written using PNP logic in mind.
But PNPCE Behaves different . Well I must say its another project to change 1000 reports
FYI...
It is better to go in for PNPCE even if you do not have Concurrent Employment to take advantage of the new lDB. The one thing PNPCE does do is when the GET executes only the infotype records retrieved for the interval requested will be retrieved. Whereas PNP by default, will retrieve all infotype records for a given PERNR.
SAP recommends to use PNPCE for all new development. But all the features are not available as of now. The Time Management functions for concurrent employment have not been released for all customers. They are activated for selected pilot customers only. Can get some info in SAP Note : 518520 , 516489..
OSS Note # 561645 ( LDB PNPCE: compatibility with PNP )
Symptom
In some respects, logical database PNPCE responds differently from logical database PNP. This may cause errors in applications that do not know this difference.
Other terms
PNP, PNPCE, payroll period, PNPTIMR9, PNPTIMRA, error message, information message
Reason and Prerequisites
There are the following differences between logical databases PNP and PNPCE:
Unlike PNP, logical database PNPCE does not have two radio buttons you can use to set the payroll period (parameters PNPTIMR9 and PNPTIMRA). Instead, the payroll period is set via parameter PNPTIMED (displayed as a dropdown box on the selection screen). This difference must be taken into account when you call a PNPCE report from another program. Otherwise, in incorrect system response occurs in the PNPCE report called. Problems may also occur if you convert an existing PNP report to PNPCE and want to use an old (PNP) variant.
If you enter an invalid payroll arear or an invalid payroll period, PNP issues an error message whereas PNPCE only issues an information message. This causes problems if you run a PNPCE report in the background because in this case the program runs into an endless loop instead of terminating.
Solution
Implement the attached corrections or import the corresponding support package.
This changes PNPCE in such a way that it responds like PNP
Moreover, also look at OSS
PNPCE: Performance improvement ( OSS note # 687004)
Symptom
You use a report that is based on logical database PNPCE. Either the performance of the report is poor, or the program terminates due to a memory overflow.
Other terms
Performance, PNPCE, 0000, 0001, buffer, memory space, memory space consumption, partitioning, FILL_0000_0001_BUFFER, T77S0, LDB, PCEPS, PNP mode
Reason and Prerequisites
The PNPCE can be used in a PNP-compatible mode. The mode is 'PNP-compatible' if the report does not program on events GET PERSON and GET GROUP and does not use the 'AS PERSON TABLE' extension for the INFOTYPES statements (for more details refer to the documentation of logical database PNPCE in Transaction SE36).
In this mode the performance is worse, as if logical database PNP is used. After the implementation of the correction from this note, the performance is significantly improved.
Another problem is that all personnel numbers that meet the entered selection criteria are internally selected during the execution of the report. Then the system imports all data records of infotypes 0000 and 0001 for all these personnel numbers because they are needed for the internal processing for different reasons. If the amount of personnel numbers or the amount of data records per personnel number is very large, memory problems can occur. The attached correction solves the memory problems.
Solution
Implement the correction according to the correction instructions or import the corresponding Support Package. If you implement the correction manually, you first have to implement Note 705870.
A part of the correction causes the internal processing of the persons/personnel numbers in blocks. If logical database PNPCE runs in PNP mode, the block-by-block processing is executed based on personnel numbers. Otherwise (in CE mode) it is executed based on persons. In PNP mode, logical database PNPCE behaves exactly like logical database PNP concerning the block processing. The settings are also made along the lines of logical database PNP. For a more detailed description refer to Note 705870.
Standard setting of the block size
In CE mode the block size is set to 10,000 persons by default. That is, as long as the number of selected persons does not exceed this value, no block processing is executed at all. A memory space analyses showed that this does not cause problems with the memory space in a system with an average number of infotype 0000 and infotype 0001 data records. However, if the amount of data records (= splits) is very large in your system, you have to reduce the maximum block size manually.
Manual setting of the block size
There are two different options to set the block size manually: a) report-specific by means of a switch which you have to set in the source code of the report, and b) cross-system by means of a switch in switch table T77S0.
The report-specific switch is called PNP_MAX_PARTITION_SIZE. It has priority (if switch T77S0 is activated) and must be set in the source code of the report at event START-OF-SELECTION at the latest.
Example: Set the maximum block size (number of persons that can be processed together) to 250:
START-OF-SELECTION.
PNP_MAX_PARTITION_SIZE = 250.
The switch is recommended for customer-specific reports requiring a lot of memory and therefore need to minimize the additional memory space of logical database PNPCE. It is not suited for SAP standard reports because the report would have to be modified in that case.
The cross-system switch is maintained in table T77S0. It affects all reports that are based on logical database PNPCE and do not use the report-specific switch PNP_MAX_PARTITION_SIZE.
The switch belongs to the LDB group and is called PCEPS. The switch is maintained in Transaction SM30 (enter table 'T77S0' and choose 'Maintain'). The switch is delivered (for Release 4.70 in a Support Package) with initial value (0). An initial value causes the switch to be ignored and the standard setting to be used instead. If you want to set the switch, set it to a numeric value. This value specifies the maximum number of persons that are processed together in a block.
Example:
LDB PCEPS 250
For more information on the procedure of a system upgrade refer to Note 317722
Thanks
Saquib
Message was edited by: Saquib Khan

Screen Change when using LDB - pnp

Similar Messages

Maybe you are looking for