How to retrieve url attributes in a bsp ?

Question

Hi,
I would like to create a BSP and then to be able to get and use an attribute from an url in it. Below an example because i think i'm not clear enough:
I create a bsp ztest. And i want to access to this bsp with the following url:
http(s)://
Then, in the bsp i want to retrieve the parameter pmsgnb to be able to use it.
Is this possible ? How can i do that ?
Thanks in advance.
Best regards,
Stéphane.

Answer 1

Hi Stef,
because you are just starting out with ABAP I would like to give you a few tips. You may of course already know about some of this.
When in that ABAP editor you can hit F1 at any time to get online help on the ABAP language. This is context-sensitive so if you place your cursor on an ABAP statement F1 will take you to the online help for that statement. The online help often contains sample syntax so you can see how to use the statements in your code.
Inside the ABAP Workbench (transaction SE80) you can navigate to Environment->Examples to see a lot of ABAP coding samples with supporting documentation. For example under "Environment->Examples->ABAP Examples->ABAP Database Access->Open SQL->Read data" are over 20 sample programs showing various ways of retrieving data from the database.
If possible go on an Introduction to ABAP training course. If not, at least buy some books on the subject. The ones that are published most recently will be more focused towards object-oriented programming and so they are more relevant than the older ones which tend to focus on SAPGUI programming and reporting.
When learning the ABAP language remember that BSP is a special use-case for ABAP and therefore has characteristics and behaviours that are unique to it. Essentially BSP combines two different development techniques - namely ABAP and the web.
In the SDN forums it is not a great idea to ask too many "newbie" questions. For a while you will get responses but later on the useful people will put you on their "do not respond" list. When using the SDN forums make sure you search for an anwser to your problem before posting, make sure you post in the correct forum and beware the "points junkies". These people just blast you with a huge copy and paste from their "knowledge base" in the hope you will allocate them points. They often don't really bother to read your question.
For your specific issue I think the INTO clause needs to come before the WHERE clause.
Try..
SELECT GUID FROM CRMD_ORDERADM_H  INTO ls_guid_ticket WHERE PROCESS_TYPE = pmsgnb.
Your question does raise another issue. You should try and avoid directly reading, and especially updating, the SAP database tables. This is how traditional ABAP programmers had to work, but contemporary SAP developments expose persistent data through classes, methods, function modules, etc. When trying to manipulate SAP data you should always try and find the proper way to do it, the way SAP does it, rather than directly accessing the database. This ensures you process any configured "business rules" that apply to that data, makes your program more maintainable, and minimised the chances of other changes to the system effecting the reliability of your program.
By way of example, lets say you wanted to change a user's class to 'TESTER'. You could write code to directly modify the field CLASS in the table USR02 to do this. But the correct way to do it would be to call the BAPI for this purpose, like this.
username = 'MUSTER'.
logondata-class = 'TESTER'.
logondatax-class = 'X'.
call function 'BAPI_USER_CHANGE'
      exporting
          username          = username
          LOGONDATA         = logondata
          LOGONDATAX        = logondatax
     tables
           return           = return .
Now, if SAP change the data model for user master records in any way you can be sure that your code will still work because they will also maintain the standard interfaces to the data model, in this case the suite of BAPI_USER* function modules.
The other by-product of this strategy is that you maximise code-reuse and minimise the amount of code you have to write. Of course sometimes direct database access is unavoidable, even with the latest SAP delivered code. For example I am currently working for a customer in the Auto industry and I have found the SAP delivered code around Warranty Claims to be so inefficient that I have to use direct database access to get reasonable performance.
I hope this helps you. Good luck with your ABAP.
Cheers
Graham Robbo