지니 loves 소은

  CLEAR : bdc_tab, bdc_tab[].

  DATA: bdc_opts   LIKE ctu_params.
  bdc_opts-dismode = 'E'.
  bdc_opts-updmode = 'S'.
  bdc_opts-NOBINPT = 'X'.

  PERFORM bdc_dynpro USING :
      'SAPMQSDA'            '0100'              'X',
      'BDC_OKCODE'          '/00'               '',
      'QPMK-WERKS'          gs_alv-werks        '',
      'QPMK-MKMNR'          gs_alv-mkmnr        '',
*      'QPMK-GUELTIGAB'      gs_alv-datuv        '',

      'SAPMQSDA'            '0101'              'X',
      'BDC_OKCODE'          '/00'               ''.

  CALL TRANSACTION 'QS24' USING bdc_tab
                      OPTIONS FROM bdc_opts
                      MESSAGES INTO messtab.

https://wiki.scn.sap.com/wiki/display/Snippets/Step-by-step+New+Barcode+Technology+for+Smart+Forms

http://blog.daum.net/rightvoice/82

Field-Symbol 관련 예제 프로그램

NUGG_ZQMR0002_FIELD_SYMBOL.nugg

http://www.sapyard.com/lazy-and-smart-abapers/

http://boy0.tistory.com/96

T-code : SAAB

http://saptechnical.com/Tutorials/ABAP/CheckpointGroup/Index.htm

https://wiki.scn.sap.com/wiki/display/ABAP/Checkgroups

http://zevolving.com/2013/05/abap-check-point-group-transaction-saab-making-troubleshooting-easy/

http://www.apprisia.com/blog/sap-abap/sap-abap-checkpoint-group/

http://www.kodyaz.com/sap-abap/abap-debugging-using-checkpoint-goup-logpoint-breakpoint.aspx

https://www.google.co.kr/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0ahUKEwjv26O9sLzVAhXMNpQKHbX4CW4QFgglMAA&url=http%3A%2F%2Fwww.sapjoy.co.kr%2F%3Fmodule%3Dfile%26act%3DprocFileDownload%26file_srl%3D52129%26sid%3De6e79895f18a88cbc0ab168972f28650&usg=AFQjCNEZSsXXKSu_l2_H57Ijdk6LBMXOxQ

https://www.daniel-berlin.de/devel/sap-dev/decompress-abap-source-code/
Decompress ABAP source code from table REPOSRC

Howdy!
If you ever wondered, where SAP stores your report source code, you probably came across table REPOSRC – but the source code is stored in a compressed format, so there's no way to get hold of it directly.
I've been trying to figure out, how this compression works for some time now… fortunately, several people dealt with the SAP DIAG protocol recently – which got me off the ground.

Algorithm

The DIAG protocol uses a form of the Lempel-Ziv (LZ) compression algorithm and a bold attempt confirmed that this is also true for the source code compression.

The code stored in REPOSRC-DATA is actually compressed using the LZH algorithm (Lempel-Ziv plus Huffman coding), which is used by the SAP DB MaxDB database too (thanks to Dennis Yurichev for the idea).

Knowing this, I wrote a decompression tool around a small portion of the MaxDB code, which also takes care of some SAP specialties:

• The 1st byte of the compressed data seems to be junk (or might have a special meaning !?)
• The first 2 bytes of the decompressed source are junk, too ?!
• Lines are terminated with character code 0xFF, which has to be adjusted
• The 1st, 3rd, 5th … decompressed byte contains NUL (not sure, why !)

The decompressed source code has a fixed line length of 255 characters (blank-padded).

Usage

1. Download this archive (it contains the decompressor tool compiled for Win32 and an ABAP report to dump the binary source code). The source code is available here; you can easily compile it on Linux/BSD/Unix/Windows using the enclosed build script.
2. To extract the compressed source code from SAP, use the report "ZS_REPOSRC_DOWNLOAD". It reads the DATA field from table REPOSRC for a given report and stores it in a binary file on your workstation.
3. Decompress the file on the command line.

PS: Works for Kernel 7.x, no guarantee for older releases.
PS 2: The functionality on non-Unicode systems is unknown… I'll check this later.

테이블에 SINGLE 이라는 컬럼이 있을 경우, NW7.4 이젼 버젼에서는 문제 없이 동작했는데

NW7.4에서는 시스템 명령어로 등록되어 에러가 발생함

SELECT burks single from ~~

! 기호를 추가하여 다음과 같이 수정하면 에러가 발생하지 않음

SELECT burks !single from ~~