I'm a friend of keeping my SAP systems tidy and avoiding the need of "expert knowledge" on how certain system functionality works, especially which transactions or tables are involved.
An ideal way of killing those 3 birds with 1 stone is the extension of the IMG (or SAP Customizing or IMG).
It allows you to:
belonging to a functionality.
When you debug the function modules that read the org structure you quickly notice that no DB access takes place. This is because the org data is stored in an internal buffer (cluster table).
So whenever you changed the org structure, make sure you run report HRBCI_ATTRIBUTES_BUFFER_UPDATE to refresh the buffer.
Org structure attributes are stored in tables HRP1222 and HRT1222.
Simply fill HRP1222-OBJID with the ORG Unit ID and execute. From the result, take the content of field HRP1222-TABNR and use it to select from table HRT1222 (key field is TABNR).
In my previous post I complained about people not using the message statement to output error messages. But sometimes Where-used does indeed fail because it is not up-to-date.
A little known transaction (at least I hardly read about it) comes to help: CODE_SCANNER.
It allows you to input a package and a search string and will find you all lines of code that contain that string.
Imagine you see an error message in WebUI or in some other interface. You manage to identify the message class and number, go to SE91, do a Where-used and find - nothing. The reason is that either Where-used was not updated correctly or (most likely) somebody did not both to use the message command to output the message but just hardcoded the message ID, number and type.
The questions and answers of a (returned) CRM survey can be easily accessed via database tables. But if you want to access the section belonging to a question, you need to get your hands dirty and access the Survey XML.
This can be done as follows:
The BOL model defines the TEL_NOMOB field of the Account -> BuilStandardAddress relation as changeable:
However, if you change this property via BOL, the update will not persist.
To create an account in CRM using BOL, proceed as follows:
A bit old, but still valid, SAP's R/3 style guide for message texts often comes in handy.
Like:
If you have a problem in your ERP/CRM middleware, here are some handy places that you can set your breakpoints in: