Security Weaver’s Process Auditor - Developer's Observations (Part 2)

[robynhosby]

This post is a continuation of Security Weaver’s Process Auditor - Developer's Observations (Part 1)

g. How to Debug the Alert Generation

This section will show where areas of the generated program to focus on in case you need to debug the logic that reads the rules and contols.

As usual, enter /H in tcode to start the debug mode  and ENTER.

... Enter form FCODE_EXECUTE_CONTROL in include /PSYNG/SA_001F01...

Logic that reads the rules and controls
Include /PSYNG/SA_001F01’s form FCODE_EXECUTE_CONTROL contains that the logic that reads the rules and controls...

Logic that calls the Fetch Data Code

Continue to single step to here...

Fetch Code program is called here...

Here are where the parameters are read for the control.....

h. How to Import to a Target Systems

To assign objects to a transport to import Development to a target system, follow the processing steps.

1. Create transport request (manually or in SolMan ChaRM). Manually add the Control program and import into the target system.

2. Now download the Control Matrix files. Please follow the below steps to achieve the same.

a) Go to the source system.

b) Run the transaction /N/PSYNG/PA.  Go to Misc.Tab

c) Click on Upload Download (Backup)

e. Check the Download Radio button.

f. Check all check boxes and specify the file path.

Select EXECUTE to download the files checked.

3. In the Target system,  upload the files. Please follow the below steps:

a) Run the transaction /N/PSYNG/PA.  Go to Misc. Tab

b) Click on Upload Download (Backup)

c) Check the Upload Radio button.

d) Check all check box and specify the file paths that you downloaded to in the source system.

Select EXECUTE.

For some reason, in my Rule Details file, two empty records were created (for reason unknown).This caused an error on the upload.  I edited the file in Notepad to delete the empty records after the download and uploaded the modified file.

To confirm the target system is as expected, check the following areas:
• The tabs
• The user exit(s) (For me, in the target system, I needed to access the screen on the tab Misc, then the entry appeared in the table.)

i. Observations

• When code changes are made, programs and the CODE file need to be downloaded/uploaded.

• By standard, files downloaded/uploaded contain data/values for ALL controls and programs, not just the ones you modified.

j. Additional Controls

For our requirements, the code to process tcodes FB05 and FB50 are had the same ABAP, so I copy/pasted to the new controls. The only differences were the tcodes noted in the control rules and in the variants.

Thank you for reading!  I hope this post will help your developer in your implementation!   If you have any questions or if I missed some details, please let me know and I will update this post.  

Cheers! 