There are various methods this can be donea) Use the Function module MONTH_NAME_GET - This Function module is used to return all the month and names in the respective language.b) You can also use the below formula −cstr(monthname(month({inputdate})))where “inputdate” is the date for which month name is required.c) Find the numeric value of month and use if condition. For example -IF month = “01” THEN January

Try to use SqlFunctions.DateDiff method overload which requires 3 inputs as follows −var res = from a in db.Set() where SqlFunctions.DateDiff("dd", a.Date, "20161922") >= 0 && SqlFunctions.DateDiff("dd", a.Date, "20161122") < 0 select a

I am not sure what you are asking, reason being if you are saying that the report is running in the background, then how it will come to know where the file needs to be saved locally (where locally it should be saved).However assuming few things, what can you try out is you can generate the file (translating data into excel is not a big task and get snippets online easily) on AS.Once generated, you can move this file from report running location to location of your choice using any SHELL command. It’s not suggested that you make a connection ... Read More

An answer to your question is a big “YES”. You can execute queries against the tables either if you are using an ABAP program or also you can execute these queries from native SQL environment.For E.g.DATA: lt_TBL LIKE TABLE OF KNA1. SELECT * from KNA1 INTO lt_TBL up to 5 rows.The snippet above lets you get the 5 rows from table KNA1 table and store in an internal table for further use.

As you need to do mass maintenance involving user locking and unlocking, you can opt for using SU10 transaction.You can also access this from SAP Menu by navigating to this path −Tools → Administration → User Maintenance → User mass maintenance. In SAP system, you have different transactions under User Maintenance that you can use for different purpose.T-Code − SU10 User Mass MaintenanceYou can select multiple users at one time and lock/unlock them directly. To select multiple users, you need to select a checkbox and click on lock/unlock button.

As you said you are working in ABAP and SQL, so I would expect that you would be using OpenSQL for your SQL activities.You can get the unique records just by using a DISTINCT operator.SELECT DISTINCT Name from where

What I can understand from the problem is not type mismatch but the mismatch in size as defaults are different for each. If you change the size as per your needs, it should work.

I usually use REGEX in all such cases as it is faster and easily readable and would recommend the same to you.You can use something similar as the snippet to get your job done.DATA: lv_para TYPE string. lv_para = ' You &are like& kite &flying& in a &hurricane&'. REPLACE ALL OCCURRENCES OF REGEX '&[^&]+&' IN lv_para WITH ''. WRITE lv_para.Let me explain the regex for you. It should match the first ‘&’, then you can have any combination with multiple occurrences of ‘&’ and the last occurrence of ‘&’ must be matched.

 There are few ways in which you can identify the program for editing if you know the transaction code in advance.Firstly you can useSE93 for identifying the program on basis of the transaction.Secondly, you can run the TCode, and then drill down to program from menu. You can lead to program from System → Status → SAP Data → Repository Data →Program.Lastly, when you run the T-Code, in the SAP GUI you can see an arrow in the bottom of the editor, Just click on it to get more information about the transaction. You can get details including the program ... Read More

 I think if you would have done some easy research or gone through the available documentation, then you would have got the answer. The reason being you already know the partial answer (SQL example as you said).In SAP HANA database, we have an analogous table “SYS.M_TABLE_STATISTICS”. Just query the table for a table on the basis of last modified date by ordering it. With the use of “M_TABLE_STATISTICS” system view is not transactional. When a DML statement is rolled back, count values in the view remain unchanged.