This needs to be configured to enable the users to be able to run the customer specific reports.The transaction code to change this is:ORET: Configure Report Tree - Initial ScreenThis involves roles, profiles, authorisations etc and should be done by the person responsible for that area in the system.Transport Request created after saving infotype 1Whenever infotype 1 was saved, the dialogue box prompting a transport request appeared on the screen.The automatic transport indicator was switched off in PD.Long messages on footerClick on the message and hold the mouse button. After moving the mouse to the left side.Alternatively, you can use transaction code SERP to create and modify a report tree. Choose a name for the tree (preferable to start it with a Z...) Add in the reports that you wish to include - with pertinent nodes and sub-nodes. You can then run any of the reports using the transaction code SARP.
User exits are useful enhancements to the system. More importantly, you can configure the system to meet your precise requirements. The transaction code to use is SMOD. If you wish to default certain values into an infotype, you could use a Customer Enhancement PBAS0001 and more specifically component EXIT_SAPFP50M_001. You would then need to insert the relevant code. These changes will be undertaken by an ABAP programmer.After entering a value in a field, it can be checked through a field exit. The system makes the field value available to be checked and changed in an ABAP/4 function.
User ExitPoints previously set in the system that let you evaluate data. The fields available are also previously defined by SAP. All fields value available can be checked in an ABAP/4 program.
Validation It allows solid data entry regarding special rules. According to previous rules, the system can evaluate an entry and a message can appear on the user's terminal if a check statement is not met. A validation step contains prerequisite statement and check statement. Both of them are defined using Boolean Logic or calling an ABAP/4 form.
Substitution Fields contents can be changed using substitution. When data are being entered, the data can be substituted by another value regarding rules previously defined. A substitution step contains prerequisite statement, substitution value and substitution exit. All of them are defined using Boolean Logic or calling an ABAP/4 form.
Set Values or ranges of values are specified under a set name. Sets are easier to create and maintain instead of using tables. They give you more flexibility when maintaining your system.
Key words It allows changes on field description according to data element. The short key word used on most screen to identify the corresponding field contents can be changed too.
Requirements & formulas ABAP/4 forms that can be used to handle pricing procedures, rounding rules, copy and data transport Sales activities.
HR User Exits Commonly used "user exits" in HR are ZXPADU01 and ZXPADU02. ZXPADU01 is called before entry into an infotype. It is commonly used to automatically populate fields on the infotype by reading data already on the employee's data record. ZXPADU02 is called after data entry into an infotype. It is commonly used to validate data that has been entered, which could not be validated by SAP standard functionality on the infotype.
Extended help under windows does not link correctly
Check the file sapdoccd.ini under your presentation server. It must be present in the main windows directory and should assign to help files directory.
SAP Documentation - Report: RPDSYS00
If unable to view documentation using the above report then do the following:
- Change the feature DSYSL.
- Enter &DSYSL=X instead of &DSYSL=.
- Save and generate the feature.
- Run report RPDIND00 specifying the language in which the texts for features, schemas and rules should be displayed.
For searching on all available help, use the menu path Help 
On the green/red/blue icon on the front screen (3 circles using 4.5 GUI or screen with the 3 coloured vertical lines on 4.6 GUI), you can do a screen print using the hardcopy option. By activating the "Quick Cut and Paste" you just need to highlight a field to have it placed on the clipboard.
If you are wishing to register a developers key for a particular user, you need to go to the OSS (transaction code OSS1). When registering the developer's key (also called access key) you need to stipulate the SAP installation number. To find this out, go to the ABAP workbench and try and copy a program. The system will request a developers key for the user. The dialogue box will also have the installation number which you will need when registering.
You can set up RFC connections to other SAP clients and boxes, using transaction code SM59. You can enter the target host details or the IP address of the client.
To create customised transactions use the menu path:
Tools
or use transaction code: SE93.Note: You need to create the transactions before you create the Area Menus. The area menus are linked to transactions which in turn are linked to reports etc.When you create a transaction you have to choose one of the 5 radio buttons offered. Usually choose one of the first 2 options which are program and selection screen for reports in either dialogue or report selection mode. You then enter the details for transaction - name, report associated to the transaction, screen number and a development class. Choose local if you do not wish to promote the transaction in a transport. If you do want to promote it, then choose a transaction class which is transportable.
To create customised transactions use the menu path:
Tools
or use transaction code: SE43.Choose and name for your area menu and a description for it. In the menu bar, enter the menu headings as you wish to see them. Once entered, double-click on them to enter the details on the drop down menu. Enter the transaction code and the associated text for each.In the application toolbar enter the transaction codes in the relevant places. The function text can be either static or dynamic. Enter the function text (the actual text on the icon) in the next dialogue box and then choose an icon from any of the SAP standard ones in the dropdown. The information text is the text displayed when you hover over the icon. You then have the option of entering a function key.Area menus are no longer used in version 4.6. You can extend the SAP menu using transaction code SE43. Add the new menu by using EXTEND S000.
Customising Cross-System Viewer
This is commonly known as OY19 (you can also use SCU0) which is its transaction code. It allows you to compare IMG activities, application components, transports or a manual selection of items, between different clients on separate servers. The manual selections could be tables, structures, reports etc. The resultant view then allows to filter the results. The color legend then gives you an idea as to where the differences are.
The transaction code for this piece of functionality is SCMP. This allows you to compare tables in different systems. The comparison is made using RFC's which link the clients and then allows the system to compare the tables. It is very similar to the compare option found on the Utilities menu of the table maintenance screen (SM30). In SCMP you have the option of entering selection criteria, displaying only the differences, whether you wish to execute the query in background or whether you wish to restrict the fields which are to be compared. It is a very useful tool.If you wish to copy entries or contents of a table from one client to another you can do so in SM30. In the target client , choose the table and then go into the maintenance option. Use the menu path Utilities
The transaction code for this functionality is SE39. It allows you to compare 2 program either in the same client or in 2 different clients. The resultant screen offers both programs and their differences. You can step through the differences.
Transaction code SE80 takes you to the repository browser. This is quite a useful tool to see all the reports, function groups, local objects or fields associated with a particular development class. If you have used only a few development classes on a project, you can specify them here. You will then be able to view, for example, all the reports associated with those development classes.
Use transaction code SE38 to go to the ABAP editor. Place a breakpoint (stop icon) on the relevant line. Execute the program from the main screen. The program will then stop at the relevant point. Double-click on a line to allow you to see what is being passed through the program at that point.
To use this functionality, you need to use transaction code SE37. This allows you to view and run function modules individually, before they are run in other programs.
You can change text elements in a number of different ways. Use transaction code SE11 and input your Data Element - to find out the data element go to the screen on which it is held and use F1
Period Selections on SAP standard Reports
The selection screen in SAP standard reports and ABAP Queries can be a bit confusing when selecting "Other Period" as your selection criteria. You will note 2 lines with "From" and "To" values for input. The first set relates to the data that is to be output, whilst the second set called "Person selection period" relates to the actual selection parameters. Consequently, if you wanted to query and output all data in a specific period, you should enter the start and end dates in both the output and selection parameters.
ABAP Reporting on Payroll Results
It is possible to write ABAP reports that pull data from the payroll clusters. This is a fairly complex task made trickier by the fact that retroactive calculations will have to be included.
It is possible to configure and store payroll results for an employee in the following infotypes:
| Infotype | Infotype Description |
|---|---|
| 0402 | Payroll Results |
| 0403 | Payroll Results 2 |
| 0458 | Accounting infotype |
| 0459 | Quarterly Cumulation |
| 0460 | Annual Cumulation |
Once the data has been stored on the infotypes, it is possible to include these infotypes in a functional area and interrogate them, using SAP Query and Ad Hoc Query. For the configuration of payroll results in the above infotypes, see the relevant page under Personnel Administration.
Reading Data from Payroll Clusters
You can use the reports RPCLSTRx to read specific payroll results - where "x" is the country-specific identifier. Replace the 'x' with your country-specific letter.You can convert certain clusters using the reports RPUCB*** where *** relates to the different clusters.You can copy these reports or modify them to write your own reports that interrogate the payroll results clusters.
You can use report RPUP2D00 to remove employee data from cluster B2. Use Relation ID = B2 and Sort Field (use *99999999*, where 99999999 is employee number to see the exact format e.g. 999999992001091, which means employee number year - 2001 pay period - 09 and cluster type - 1).If you wish to update the data held in the variouse clusters, you can do so by using the different macros held in table TRMAC. Use the macros RP-EXP-... and RP-IMP-... to export and import the data.
Data Migration - Available Tools
You can upload old master data info into SAP by using the report, RPUSTD00, use this interface as a model and modify it to suit your needs. Transaction Code SXDA takes you to the Data Transfer Workbench. Use object 0555 for Personnel Administration and 0777 for HR Planning. 0555 uses the program RPUSTD00 whilst 0777 uses RHALTD00 (Legacy Data Transfer). The documentation on SAP will give you a good start.You can use the legacy system migration workbench - transaction code LSMW. It is a standard tool delivered with the SAP system.Wanting to move Personnel Administration data from one client to another? You can use CATT procedures to do this quite easily. SAP designed Computer Aided Test Tool for repetitive testing on the system, but it can be used effectively for data migration exercises. You would need to export all the required data into Excel and then write a CATT procedure to load up the data into the other client.
Setting breakpoints:Before version 4.0:The internal table AS tells you where you are in the exploded schemas/sub-schemas. It is an exploded version of table T52C0, which contains all schemas/subschemas.Schema Lines: Use the BREAK Function with your "rosco" as parameter one in the Schema. Rosco is your unique identifier, as set up in the payroll parameters (Parameter name is AB4).Features: Break at form RE549D until you get the right Feature.Rules: Use a BREAK function on the line before the Rule is called using your rosco.Functions: Set a Breakpoint on the function, remembering to put FU at the beginning of the form. Use OP for operations.After version 4.0:Schema Lines: Set a Watchpoint* on AS-parameters with a value the same as your schema line. Press Continue after it stops for the first time as this is just the AS table loadingFeatures: Set a Watchpoint at T549D-NAMEN with the Feature name you want.Rules: Set a Watchpoint* on AS-PARM1 with a value the same as your rule. Press Continue after it stops for the first time as this is just the AS table loading. Then continue to Form REGEL.Functions: Set a Breakpoint on the function, remembering to put FU at the beginning of the form. Use OP first for Operations.
An easy way to identify reports is to go to ABAP workbench, select the object (e.g. table) and click on the "where-used" icon. This will give you a list of all the reports that contain this object. You then can filter out certain reports and look in detail at them. Alternatively you can search for a string value in any specific report using the report RPINCL10.
Programming Macros - RMAC Modules
Macros in HR are quite a useful ABAP feature. You can find them in the table TRMAC and all the HR macros should start with RPThe online help is quite good. It can be found following the path:
HRin the HR Standard System
ABAP Programs - Version Management
The version management functionality is quite useful. Use the menu path:
Tools
Alternatively you can use transaction code SE38, enter the program name and then use the menu path: Utilities
It is possible to capture text that has been entered against an infotype, during the running of a report. The example below gives an extract of the code required to extract text, which has been maintained against infotype 0019.loop at p0019 where begda le pn-endda and endda ge pn-begda. move-corresponding p0019 to cprel. move '0019' to cprel-infty. move cprel to tx-key. rp-imp-c1-tx. loop at ptext. ... ... ... endloop. endloop.
If you would like to subtract one day from a date in infotype 41 when a person is terminated you can do so by carrying out a mathmatical operation directly in T588Z - which holds the configuration relating to dynamic actions. Table T588Z allows you to do a direct mathematical operation only in IT 0019. An example from SAP Help is inserted:INS,0019,30W P0019-TERMN=P0028-BEGDAW P0019-VTRAN='1'W P0019-VTRZH='013'W P0019-VTROP='+'But after that you can populate dates in infotype 0041 using the date from infotype 0019. It would be preferable though to write a user exit - you could provide additional date(s) validation calling table RP50D.
If you would like to display the contents of a structure, then you can do so using transaction code SE11. Enter the structure in the field titled "Data Type" and click on the display icon. This will give you all the available fields within a structure. You can also use this field to search for:
- data elementsstrucuresdatabase tablestable typesclass andinterface
Changing the development class
To change the development class from $TMP, use transaction code SE80 - click to Local Objects, find your ABAP program or other object, right click on it - more functions - change development class on 4.6c.
Wishing to set a default value in particular field in an infotype.There are certain features which can do this. For fields that are not covered by SAP standard features.
- You can use a dynamic action whilst in the personnel action. You can create a feature.
- Otherwise you can use the user exit available for infotypes - ZXPADU01
Remember that they have to be activated first, and you will have to have ABAP knowledge to make adjustments.
No comments:
Post a Comment