13
Jul
2011
SAP: Configuring a Trust Relationship for SAP Assertion Tickets
Some useful reading material about configuring trust relationships between different SAP instances.
http://help.sap.com/saphelp_nwpi71/helpdata/en/45/341a2176b74002e10000000a155369/content.htm
27
Jun
2011
SAP: scan ABAP programs
Useful little program that can help you scan other SAP programs RPR_ABAP_SOURCE_SCAN.
21
Jan
2011
SAP: ABAP: Subroutine does not exist – bug
Scenario: you’re editing your code and when you try to double click on a previously defined subroutine you get a popup stating that it doesn’t exist. You check and confirm that the subroutine is included, the report compiles and runs properly.
Resolution: to fix the problem do the following steps:
- Click Utilities
- Click Update Navigation Index
The report will be regenerated and your problem should be solved.
27
Nov
2010
SAP: re-generate OBBH substitution rules
Sometimes its worth regenerating your substitution rules – to do this execute program RGUGBR00.
25
Nov
2010
SAP: Workflow Diagnostic Tool
You can test your workflow task by executing transaction SWUD
17
Nov
2010
SAP: BeX Exception Broadcasting
Interesting article summarizing the process of sending out email messages based on exception filters in a query.
17
Nov
2010
SAP: logging table changes
When a table is configured there is an option to log the changes that are done to the information.
You can then check who mad the changes and when the change took place by running report RSVTPROT.
14
Nov
2010
SAP Portal [object is currently locked by user]
If you are working with an SAP portal and get to a point that you are unable to edit an object because it is locked by a user [most likely your own user] you have the option to release the lock by performing the following action:
- Select System Administration
- Select Monitoring
- Expand Portal menu on the left hand side
- Select Object Locking
- Select the locked object and click the Unlock button
8
Nov
2010
ABAP Runtime Analysis – variant setup
Runtime analysis can be used to quickly get to the bottom of which tables are referenced during a transaction/program/function-module call.
I like running SM30 over ST22 because you get a nicer presentation of what tables were hit. ST22 tends to bee too detailed in majority of my scenarios.
By default the report is initialized with the DEFAULT variant. This is limiting and will not give you as much information as you might want. Typically on a new system I set up my own variant that allows me to access more information.
Steps to set up your own variant:
Select the drop down option in the Variant selector panel- Click the green check-box on the next screen without changing the parameters of the Selection Criteria for Variants pop-up
- You will be presented with two default Variants – DEFAULT and TMP; ignore those and click on the Create button
- Type in the name and continue
Here’s the most important part of this trick. When you get to the main configuration page of the variant go to the third tab [Duratn/type] and in the Aggregation pick the None option.- Once done click Save as… button and you are ready to run your Analysis.
23
Apr
2010
SAP: WE20 partner set up “Please enter a permitted partner number”
A new inbound IDOC failed to process with a “EDI: Partner profile not available” error.
I’ve attempted to set up a new partner but failed to do so due to the “Please enter a permitted partner number” error when using WE20 transaction and setting up a new LS partner.
A quick debugging session revealed that the program was checking a TBDLS table [Logical Systems].
After this I’ve simply used SPRO transaction to update the:
Spro – IMG – Basis Components – Application Link Enabling (ALE) - Sending and Receiving Systems – Logical Systems – Define Logical System
Add the new logical system and you will be able to set up the new partner now.
