![]() "append statt collect, beinhaltet refresh ot. Plog1_perform plog_check_rule_performed(h99plog0). Plog4_perform plog_header_cycle(h99plog0) To know what operation is it, display the structured field OP.īy the way, if a WT is set to a specific value in a PIT rule and instead of setting the watchpoint at OT table you do it at IT table, the watchpoint will stop at the end of the rule as you can see in the code below: To see which rule is it, look internal table AS header. If you do so, the program will be stopped at the relevant operation within the rule. In that case, you'd better set the condition for table OT (OT-LGART, OT-BETRG.). Many times, WTs are created within a rule operated by function PIT or PRT. Sometimes, WTs are directly created in table RT so in that cases, setting the condition for table RT might be useful. If I had set the same condition for table RT, the program would have stopped later on in the schema when WT /341 is collected to be stored in table RT which is useless. You'll notice that in the watchpoint condition I used WT table IT instead of table RT. The program will stop when the watchpoint condition is fulfilled. Now both condition have to be linked by the "And" operator. Then press F8 to start the program.Ĭreate a second watchpoint because the condition is: it-lgart = /341 and it-betrg = 1.375,00 Start payroll in debugging mode by going to the payroll driver selection-screen and setting /H at the ok-code. If for example you find that WT /341 equals 1.375,00 EUR at the final payroll results and you want to know where in the payroll schema WT /341 amount was set to 1.375,00 EUR. Watch-points will help you a lot on this. Find out at which point of the payroll Schema, a Wage Type is generated or a WT is set to a specific value When you start payroll again you'll be able to debug the code that triggered the rejection which will help you identifying the cause of the error. Then press F8 so that the command "Reject" is reached:įORM NEW_ABLEHNUNG FORM FILL_MSGTAB_FINAL_STEP FORM FILL_MSGTAB FORM ERRORSĪre common to all the rejections so they will not add any value info, so we go to the first relevant form:ĭouble-clicking on it we get to the ABAP code and set a break-point just before the error process is triggered (Or maybe analyzing the ABAP code that triggers the error is enough): Now you are debugging the payroll and you need to reach the point of rejection: Go back to the selection-screen and start payroll in debugging mode with /H. ![]() For example, you run the payroll drive and get a log like this: After that you have to take a look at "Calls" to guess where the error is coming from. finally press F8 key, you'll reach the reject command. Start payroll processing in debugging mode /H, then go to. Just set a break-point in the command "reject". When a pernr is rejected in the payroll log. For this you'll use the payroll operation BREAK, followed by your ABAP prefix. You can set a break-point in a payroll rule, as well. Of course you could have set a soft break-point directly at function P0092- pe04. In this case the function code to be debugged is very short. In this case, you are about to debug function P0092. Now you can stop right before next function to be processed in schema by pressing F8. Table AS contains the Schema and its header contains the current function in the schema being processed (AS-FUNCO). You can display the current function to be processed by displaying in your debugger screen table AS (Header). Then press key F5 and set a soft break-point at PERFORM as-funktion. ![]() Now you can go to the next payroll function by exiting function break (F7). If you run your payroll driver, the debugger will stop just before EANT schema. For this you'll use the payroll function BREAK followed by your ABAP prefix.Įxample: Set a break-point in Schema E000: Once you have a prefix of your own, you can set a break-point at a certain point in a Schema by editing the Schema (Trx PE01). you are debugging a development system), and you have authorization to modify rules and schemas you can set a hard break-point.įor this, you have to modify your user-profile and set an ABAP prefix (AB4). Whenever you can modify the system you are analyzing (e.g. Using hard break-points to debug the Schema.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |