ABAP

05 02 2018

Protected: EWM: Change spool request name

Ruslan ABAP EWM Enter your password to view comments.

08 06 2017

Важные слова не важны

В процессе написания кода по заданной спецификации неожижанно обнаружилось, что ключевые слова ABAP не являюся зарезервированными.
Поэтому нижеследующий код компилируется и даже выполняется:

TYPES TYPE.

DATA USING TYPE TYPE.

PERFORM FORM USING USING USING USING.

FORM FORM USING USING TYPE TYPE DATA LIKE USING TYPE TYPE TYPE.

  DATA = TYPE.

  DATA TO TYPE I.
  DATA ADD LIKE TO.

  ADD ADD TO TO.

  DATA IF.
  DATA EQ.
  DATA ENDIF.
  IF IF EQ EQ.
    MOVE TO TO ENDIF.
  ENDIF.

ENDFORM.

TYPES TYPE.

DATA USING TYPE TYPE.

PERFORM FORM USING USING USING USING.

FORM FORM USING USING TYPE TYPE DATA LIKE USING TYPE TYPE TYPE.

DATA = TYPE.

DATA TO TYPE I.

DATA ADD LIKE TO.

ADD ADD TO TO.

DATA IF.

DATA EQ.

DATA ENDIF.

IF IF EQ EQ.

MOVE TO TO ENDIF.

ENDIF.

ENDFORM.

Даже если так писать и можно, то этого делать всё-таки не следует:

Усложняет восприятие, хотя есть и подсветка кода и uppercase/lowercase
Name-conventions
Ограничения при работе с БД
Это не смешно

Зато есть служебная таблица TRESE, в которой перечисляются разные наименования полей, которые нельзя создавать из-за ограниченний в разных БД.
© Иван Болховитинов

14 04 2017

Protected: WMS: propose next empty bin

Ruslan ABAP ABAP Enter your password to view comments.

01 12 2016

On distribution – is delivery packed?

Ruslan ABAP ABAP, Enhancement 0

FM WS_LM_CHANGE_DLV_DISTRIB_STATE

ENHANCEMENT 1  YDISTRIBUTE.
if ( sy-tcode eq 'VL06I' or sy-tcode eq 'VL06ID' ) and  ( if_d_proctype eq proctype_inbdist ).
"VL06I - do not process the enhancement if it distributes via other ways"
"proctype_inbdist - checking only inbound deliveries"
 types: begin of t_params,
  paramval like yparamconst-paramval,
 end of t_params.
 data: lt_params type standard table of t_params,
       wa_params like line of lt_params, "work area (header line)"
       is_zles type boolean.  "default abap_false."
"which delivery types for checking/processing are defined in our Z-table?"
 select paramval from yparamconst into corresponding fields of table lt_params where paramid  = 'LIEFERUNGSNUMMER'.
 if sy-subrc eq 0.
  field-symbols: <ls_lfart> type lipov.
  loop at ct_worktab assigning <ls_lfart>.
    read table lt_params with key paramval = <ls_lfart>-lfart transporting no fields.
   if sy-subrc eq 0.
    is_zles = abap_true.
"all the selected delivery [types] are in yparamconst"
   endif.
  endloop.
 if is_zles eq abap_true.
  data: lt_wahl like gs_select occurs 0 with header line,
        begin of lt_wahl2 occurs 0,
          vbeln like likp-vbeln,
          verur like likp-verur,
        end of lt_wahl2,
        l_msg type c length 50,
        ans type char1.
  field-symbols: <ls_arbeit> type lipov,
                 <ls_wahl2> like line of lt_wahl2.
  loop at ct_worktab assigning <ls_arbeit>.
    lt_wahl-vbeln = <ls_arbeit>-vbeln.
    collect lt_wahl.
  endloop.

  check not lt_wahl[] is initial.
  select vbeln verur from likp
               into table lt_wahl2
               for all entries in lt_wahl
               where vbeln eq lt_wahl-vbeln.
"in addition we checking if the field External ID isn't empty"
  loop at lt_wahl2 transporting no fields
    where verur eq space.
  endloop.

  if sy-subrc eq 0.
   message s000(Y_YSD) into l_msg.
   call function 'POPUP_TO_CONFIRM'
    exporting
      titlebar       = 'Confirm'
      text_question  = l_msg
      text_button_1  = 'Yes'
      text_button_2  = 'No'
      display_cancel_button = ''
      default_button = '2'
    importing
      answer         = ans.
   if ans eq 2.
    return.
   endif.
  endif.

  clear l_msg.

  field-symbols: <ls_vepo> type lipov.
  data lt_vepo like VEPO occurs 0.

  loop at ct_worktab assigning <ls_vepo>.
    select vbeln from vepo into corresponding fields of table lt_vepo where vbeln eq <ls_vepo>-vbeln.
     if sy-subrc ne 0.
       message s001(Y_YSD) into l_msg.
       call function 'POPUP_TO_CONFIRM'
        exporting
          titlebar       = 'Confirm'
          text_question  = l_msg
          text_button_1  = 'Yes'
          text_button_2  = 'No'
          display_cancel_button = ''
          default_button = '2'
        importing
          answer         = ans.
       if ans eq 2.
        return.
   endif.
   endif.
  endloop.

 endif. "is_zles"

 endif.
endif.
ENDENHANCEMENT.

ENHANCEMENT 1 YDISTRIBUTE.

if ( sy-tcode eq 'VL06I' or sy-tcode eq 'VL06ID' ) and ( if_d_proctype eq proctype_inbdist ).

"VL06I - do not process the enhancement if it distributes via other ways"

"proctype_inbdist - checking only inbound deliveries"

types: begin of t_params,

paramval like yparamconst-paramval,

end of t_params.

data: lt_params type standard table of t_params,

wa_params like line of lt_params, "work area (header line)"

is_zles type boolean. "default abap_false."

"which delivery types for checking/processing are defined in our Z-table?"

select paramval from yparamconst into corresponding fields of table lt_params where paramid = 'LIEFERUNGSNUMMER'.

if sy-subrc eq 0.

field-symbols: <ls_lfart> type lipov.

loop at ct_worktab assigning <ls_lfart>.

read table lt_params with key paramval = <ls_lfart>-lfart transporting no fields.

if sy-subrc eq 0.

is_zles = abap_true.

"all the selected delivery [types] are in yparamconst"

endif.

endloop.

if is_zles eq abap_true.

data: lt_wahl like gs_select occurs 0 with header line,

begin of lt_wahl2 occurs 0,

vbeln like likp-vbeln,

verur like likp-verur,

end of lt_wahl2,

l_msg type c length 50,

ans type char1.

field-symbols: <ls_arbeit> type lipov,

<ls_wahl2> like line of lt_wahl2.

loop at ct_worktab assigning <ls_arbeit>.

lt_wahl-vbeln = <ls_arbeit>-vbeln.

collect lt_wahl.

endloop.

check not lt_wahl[] is initial.

select vbeln verur from likp

into table lt_wahl2

for all entries in lt_wahl

where vbeln eq lt_wahl-vbeln.

"in addition we checking if the field External ID isn't empty"

loop at lt_wahl2 transporting no fields

where verur eq space.

endloop.

if sy-subrc eq 0.

message s000(Y_YSD) into l_msg.

call function 'POPUP_TO_CONFIRM'

exporting

titlebar = 'Confirm'

text_question = l_msg

text_button_1 = 'Yes'

text_button_2 = 'No'

display_cancel_button = ''

default_button = '2'

importing

answer = ans.

if ans eq 2.

return.

endif.

clear l_msg.

field-symbols: <ls_vepo> type lipov.

data lt_vepo like VEPO occurs 0.

loop at ct_worktab assigning <ls_vepo>.

select vbeln from vepo into corresponding fields of table lt_vepo where vbeln eq <ls_vepo>-vbeln.

if sy-subrc ne 0.

message s001(Y_YSD) into l_msg.

call function 'POPUP_TO_CONFIRM'

exporting

titlebar = 'Confirm'

text_question = l_msg

text_button_1 = 'Yes'

text_button_2 = 'No'

display_cancel_button = ''

default_button = '2'

importing

answer = ans.

if ans eq 2.

return.

endif.

endloop.

endif. "is_zles"

endif.

ENDENHANCEMENT.

24 09 2015

ZTOAD – alternate SQL builder (SAPLink)

Ruslan ABAP SQL 0

ZTOAD – is an alternate SQL builder (SAPLink). It can be installed using SAPLink (SAPLink should be installed as well).

SAPLink is a tool for importing and exporting ABAP developments from one system to another. The main terms of SAPLink are nuggets and slinkies:
a) a slinkee file (.slnk) is used for single objects to be imported or exported. Slinkees are very quick and easy to use and recommended for single object collaboration. They can be imported and exported from the “Object” tab.
b) SAPLink nuggets are the SAPLink packaging system that enables multiple objects to be imported/exported in one handy dandy file (.nugg). Nuggets can be imported, created, and displayed from the “Nugget” tab.

With ZTOAD (called ZTOAD in reference of a famous query builder in the SQL) you can write and execute queries, in OpenSQL format (the format used in ABAP programs). Result is displayed in an ALV at bottom part of the screen:

The order is next:
1. Install SAPLink
2. Install DDic plugin (just import NUGG_SAPLINK_DDIC.nugg nugget file).
3. Install ZTOAD
4. Launch SE38 -> ZTOAD

P.S. In case of error “CLASS ZSAPLINK DEFINITION LOAD statement is missing.” just add the string

class zsaplink DEFINITION load. " Convenience for older SAP-Releases

1	class zsaplink DEFINITION load. " Convenience for older SAP-Releases

after the string

REPORT  zsaplink.

1	REPORT zsaplink.

in the ZSAPLINK program.

P.P.S. “Plugin for object type TRAN is not installed on this system”: CLAS_ZSAPLINK_TRANSACTIONS.slnk,
“Plugin for object type DEVC is not installed on this system”: CLAS_ZSAPLINK_DEVC.slnk
and activate “Inactive local objects” in SE80.

10 04 2015

Smart Forms vs Adobe PDF-based forms

Ruslan ABAP, Allgemein PDF, smartforms 1

Here is a comparison between the two largest print form formats.
All new forms delivered with the ERP will be PDF-based. So, it’s probably better to get ready to change.

Knowing those two print forms possibilities offered by SAP, you want to know more about what is the best technology to use.

Hopefully I’ll provide you some answers in this paper. I’ll probably write more complete comparisons as experiences with PDF forms grows.

Smart Forms architecture

The application program retrieves data from the database and is passed to the function module generated by the Smart Form. The application program, which collects data, has to be written. In many cases, a standard print program is copied, modified and then reused.

The Smart Form needs to be defined. With transaction SMARTFORMS, you can setup the layout you want. This is a powerful but quite old tool and its usage is requires some learning time.

PDF-based print forms architecture

At runtime, we notice the architecture is very close of the previous one.

In this case, a print program also needs to be written. The PDF form template, consuming data from its interface, is called by the generated function module. The call to the web service and the PDF is physically built during runtime.

The ADS component runs on the J2EE stack and exposes a web service allowing the rendering of PDF forms. This means extra calls between both stacks.

Note that you can use this web service to build other PDF forms.

Comparison: pro et contra

Development

Every form has layout problems at some point in time. Text is too low the page; the first name is not aligned with the last name, tables don’t display correctly etc. In both cases, there are a lot of tests (“chipotages”, for the French-speaking people) to perform before a form version can be released.

There is a first advantage of PDF in comparison with Smart Forms. The Adobe LiveCycle Designer (ALD) is at first sight simple, yet powerful and comprehensive. So to build a layout is easier with PDF forms for people with limited experience.

When you have lots of forms to develop, you can enhance the custom objects in the ALD: you can add multiple UI objects and group them in one element which you can easily reuse. For instance, a ‘UserData’ element that contains firstname, lastname, street, postal code and city. Element types as well as the layout are stored locally (in folder C:\Users\\AppData\Adobe\Designer\en\objects\), so exchange with other forms developers is quick and easy.

So, bottom line is that development time can be reduced by using PDF forms. Of course, this also depends on your developers’ skills.

Performance

As you know, every object-oriented language has performance problems. So does Java… The ADS component is also heavy and the rendering time of a very complex PDF form, with lots of scripting logic and data to display, can take some time. This may result in heavy documents. Another reason for the sometimes slow performance is the web service connection.

This performance issue must be taken into account when considering high volume printing and complex forms.

Of course, be aware there are possibilities to improve PDF rendering time. Form bundling is one of them (the bundling principle is to send multiple forms in one call to ADS); another one, valid as of NetWeaver 2004s SP12, is described in SAP Note 993612.

Smart Forms, which run fully on the ABAP side, can be faster than PDF… for the moment. I’ll probably post more about performance comparisons in the future.

Regarding stability, both technologies are equivalent and I personally never had problems regarding this. Feel free to provide your input!

Architecture

As said earlier, PDF requires a J2EE stack with ADS properly configured and with connections between both systems up and running. This is done in standard as of NetWeaver 2004 SR1 so don’t panic! Every recent SAP solution includes the J2EE stack including ADS.

There are web services calls between the ABAP and J2EE stacks, which makes for additional connections to handle.

In terms of architecture, the PDF seems to require more attention. Although, the J2EE stack with ADS is installed and configured in standard as of the ERP2004 so there should be no particular worries about this.

Front-end and clients

The PDF requires Adobe Reader to display PDF forms. Nowadays, almost every workstation has Adobe Reader installed on it. Reader is not required to print forms: hopefully, the normal PDF drivers are supported in SAP systems as well as most of standard printer drivers.

Smart Forms require no additional installations on top of the standard SAPGUI.

Compatibility

Customer examples

In this case, everything depends on your scenarios. Some examples for PDF: you need to respect a legal template, which is provided in PDF; PDF is already widely used in your company; you have all the other Adobe products; you need to send printed invoices to your customers automatically via mail with PDF format etc.

On the other hand, you can choose to use Smart Forms for various reasons: your SAP system printing documents is R/3 4.7; you have plenty of qualified developers who know Smart Forms very well; you need very high performance rather than flexibility etc.

Courses

One reference course for Smart Forms: BC470 – Form printing with SmartForms.

The Adobe LiveCycle Designer embedded in an SAP environment offers a lot of possibilities. More information can be found in SAP course BC480 – PDF based print forms (3 days).

Conclusion

Smart Forms is the faithful technology for those who know it. Still useful and reliable as well as very powerful.

On the other hand, the PDF-based print forms is highly appreciated for its comprehensiveness, compatibility, design possibilities. It’s also the future for form output in SAP solutions.

So, the choice is now yours. Personally (but as you may know, I’m not the most objective person when speaking about forms), my choice goes to the PDF for the reasons mentioned above.

16 11 2014

ABAP programming tips

Ruslan ABAP ABAP 5

Q: How to convert sy-datum type type to string DD.MM.YYYY?
A: write sy-datum using edit mask ‘==PDATE’ to lv_datestring.

Q: How to convert CHAR type to RAW type?
A:

  types: begin of c16,
           aaa(16) type c, "CHAR(16)
         end of c16.
  types: begin of r16,
           aaa type guid_16, "RAW(16)
         end of r16.
  data: it_chars type table of c16,
        it_raws type table  of r16,
        c1(16) type c.
  c1 = '1234567890123456'.
  append c1 to it_chars.
  call method CL_RSZ_WWW_DB_INTERFACE=>CONVERT_CHAR_TO_RAW
    exporting
      I_T_IN  = IT_chars
    importing
      E_T_OUT = it_raws

types: begin of c16,

aaa(16) type c, "CHAR(16)

end of c16.

types: begin of r16,

aaa type guid_16, "RAW(16)

end of r16.

data: it_chars type table of c16,

it_raws type table of r16,

c1(16) type c.

c1 = '1234567890123456'.

append c1 to it_chars.

call method CL_RSZ_WWW_DB_INTERFACE=>CONVERT_CHAR_TO_RAW

exporting

I_T_IN = IT_chars

importing

E_T_OUT = it_raws

Q: What does mean asterisk in front of the name?
A: EKPO and *EKPO are usually defined in TABLES statement, and both use the DDIC structure of EKPO. Classical usage is to distinguish between old and new value of the record.
SELECT SINGLE * FROM *bkpf is equal to SELECT SINGLE * FROM bkpf into *bkpf
the same as SELECT SINGLE * FROM bkpf is equal to SELECT SINGLE * FROM bkpf into bkpf

While declaring variables, always follow the naming conventions through out your code. Your variable names talks a lot about its usage.
Make sure your variables are of the form:

{Prefix1}{Prefix2}_{Name} where:

Prefix1:
L – Local
I – Import
E – Export
G – Global
T – Table Type

Prefix2:
V – Single Value
S – Structure
T – Table
R – Type ref to Data
O – Type ref to Object
E – Type ref to Exception objects

Name – name of the variable.
e.g.:
lt_sel – local table
lo_rvs – local object
and so on.

Before changing the parameters (type or name), make sure that you run “Where used”, make a note and change them as well.
While working on ABAP Classes and Interfaces, Never change a super class of a framework. It could potentially bring all applications down. Double check to make sure that the code you change is in your class only.

Ctrl + D Duplicate any line.
Ctrl + . & Ctrl + , Comment and Un-Comment selected lines.
Ctrl+Shift+X Deletes the whole line.
Ctrl+Shift+V Gives All Paste options.
To assist in locating codes, can be a bookmark, using a combination: CTRL + ALT + (0 to 9).
To go to bookmark created, use combination CTRL + (0 to 9).

Q: How to debug IDOCs inbound processing (most first FMs on receiver system (under ALEREMOTE non dialog user)?
A: Simple and stupid solution is to put eternal loop in form FA5_DOCUMENT_SYNTAX_CHECK (program LEDI1FA5):

data: x type flag. *if sy-uname eq 'SAPSD'. while x is initial. endwhile. "endif.

1
2
3
4
5

data: x type flag.
*if sy-uname eq 'SAPSD'.
while x is initial.
endwhile.
"endif.

Then the process will be available for debugging in the transaction SM50.
Please create lock objects on the header tables and make sure that you obtain a lock before changes and release the lock after changes.
Make sure that you transactions are atomic. Either commit your work after all changes are successful or Rollback in case of error. If you rollback, make sure that you have released the locks.

Q: How to pass dynamic varable into SELECT … WHERE IN clause?
A:

data: lv_pabprfs type string,
         qry type string.
  select single param from zparam into lv_pabprfs where paramid  = 'PAPROFIL'.
  "lv_pabprfs = 'M033', 'M833', 'M843'
  qry = 'b~pabprf in (' && lv_pabprfs && ')'.

  select single baset into myvar from jitoco where outpo = '3' and (qry).

data: lv_pabprfs type string,

qry type string.

select single param from zparam into lv_pabprfs where paramid = 'PAPROFIL'.

"lv_pabprfs = 'M033', 'M833', 'M843'

qry = 'b~pabprf in (' && lv_pabprfs && ')'.

select single baset into myvar from jitoco where outpo = '3' and (qry).

During save, please make sure that entries in all the text (_T_*) tables that relate to your modules are also saved. If no data exists, treat it as an error. (As across check, you can verify the same by executing the view and making sure that the data is returned correctly)
The Function should be RFC Enabled. Never raise an exception. Always return errors in the ET_RETURN (Type BAPIRET2) structure.
Never hardcode text strings. Make sure that you use a text element. But use it with text reference.
E.g. If you have an error during validating the email, use it as “Email ID is required”(001) instead of using text-001. This will ensure that error messages are displayed regardless of user logon language.
At the end of the function, Always call “get details” and return the values as export/table values. This will serve the purpose of reflecting the data as-is in the DB back to the user and will save another round trip to retrieve it again.

Q: How to get variable value from another running program?
A:

"in case of needed programm isn't in the memory area, we can to call it via
PERFORM change_control_record IN PROGRAM SAPMV50A.
  ld_mem = '(SAPMV50A)XLIPS[]'.
  ASSIGN (ld_mem) TO <mem>.
  IF sy-subrc = 0. "if ld_mem is assigned
    lt_xlips[] = <mem>.
  ENDIF.

"in case of needed programm isn't in the memory area, we can to call it via

PERFORM change_control_record IN PROGRAM SAPMV50A.

ld_mem = '(SAPMV50A)XLIPS[]'.

ASSIGN (ld_mem) TO <mem>.

IF sy-subrc = 0. "if ld_mem is assigned

lt_xlips[] = <mem>.

ENDIF.

Update audit fields created by, created date, created time only during create.
Please ensure that IV_UNAME (SY-UNAME) and IV_LANGUAGE (SY_LANGU) are mandatory for all modules. Extract the data for the language specified.
Q: Where are the packing handling units data stored during execution of transaction VL01/VL02/VL32N”? CVEKP table is always empty.
A: The variable is (SAPLV51G)IVEKP[]

17 08 2014

Debug ABAP programs which are executed in background

Ruslan ABAP Debug 0

If you have got a program which calls another program in background e.g. Smartforms print routine, you may need to debug it or get it to stop at a break-point set in the background program. To do this all you need to do is turn update debugging on from the ABAP debugger (Settings->Change debugger profile->Update debugging).

06 07 2014

Error SSFCOMPOSER 152 solution

Ruslan ABAP Debug 0

Last week we have found an error in our Z-Smartform, which says nothing except “SSFCOMPOSER 152: Events are already defined.”
It didn’t say what data related to the error, or even which part of the smartform acted wrong.

After a bit debugging we’ve found the module with the proper position for a breakpoint:

1. Open SE80 and “Function groups” inside it.
2. Functional group STXBC.
3. Open the subroutines folder.
4. Set a breakpoint in ERR_WRITE routine.

Now, carry out the smartform and we will get all the data related to the error with all the parameters.

24 05 2013

Набор полезных программ

Ruslan ABAP, nützlich ABAP 0

Получить внешние вызовы ФМ, транзакций и многого другого внутри программы можно с помощью программы — RSINCL00.

Транзакция ABAPDOCU — ABAP документация и примеры.

Транзакция BIBS — примеры пользовательского интерфейса для ABAP программ.

Транзакция DWDM — демо примеры с использованием Enjoy контролов.

Программа ADBC_DEMO — демо программа ADBC API (для подключения к внешним базам данных).

Транзакция SE83 — библиотека примеров с ALV и прочими контролами.

Программа BALVBT01 — демонстрация множественного использования ALV.

Программа SHOWICON — список всех иконок.

Программа SHOWCOLO — все цвета используемые во WRITE или ALV.

Программа SHOWLINE — всевозможные линии во write отчётах.

Программа SHOWSYMB — символы.

Программа AFX_CODE_SCANNER (или RPR_ABAP_SOURCE_SCAN) — поиск в исходных кодах.

Программа RSBDCOS0 — выполнение системных команд на сервере.

Программа REPTRAN — массовая выгрузка исходников.

1 2 3