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 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:
If you have a problem in your ERP/CRM middleware, here are some handy places that you can set your breakpoints in:
When you're communicating with an external SAP system, you should use the released BAPIs if you can.
I don't use RFCs and BAPIs that often, so one thing that struck me today was that BAPIs don't refresh their buffer when you call them.
My expectation was: BAPIs are for external calls, so they should make sure you always get the most-up-to-date data and handle the buffer themselves.
I was wrong.
BAPIs will default to accessing the buffer, which makes sense performance-wise.