se19 BADI 생성

se20 BADI 조회/수정

/SHCM/RH_SYNC_BUPA_EMPL_SINGLE : S/4HANA BUPA 동기화

/SHCM/RH_SYNC_BUPA_FROM_EMPL  :  S/4HANA BUPA 동기화

SAP LT

HR Pernr <-> BP Partner No Relation : BUT0ID

Vendor <-> BP Partner No Relation : CVI_VEND_LINK

Customer <-> BP Partner No Relation : CVI_CUST_LINK

HANA 에서 지정한 Data보다 큰 200000 개의 Data 읽어오기

3개의 필드를 비교하여 Max 값

select z.*'

  from ZFIT_AUDIT02 as z

where mandt = '100'

   and gjahr = i_gjahr

   and bukrs = i_bukrs

   and budat >= i_budat

   and ( belnr >= i_belnr or budat > i_budat )

   and ( buzei >= i_buzei or belnr > i_belnr or budat > i_budat )

order by bukrs, gjahr, budat, belnr, buzei' INTO sql_str

limit 200000

4개의 필드를 비교하여 Max 값

select *
    into CORRESPONDING FIELDS OF table lt_konv
    from konv
      up to 200000 rows
   where KDATU between '20120101' and '20151231'
     and KNUMV >= lv_knumv
     and ( KPOSN >= lv_kposn or KNUMV > lv_knumv )
     and ( STUNR >= lv_stunr or KPOSN > lv_kposn or KNUMV > lv_knumv )
     and ( ZAEHK >= lv_zaehk or STUNR > lv_stunr or KPOSN > lv_kposn or KNUMV > lv_knumv )
     ORDER BY PRIMARY KEY.

https://blogs.sap.com/2015/10/25/abap-740-quick-reference/

So you’re an experienced ABAP programmer wanting to leverage off the fantastic new functionality available to you in ABAP 7.40!

However, searching for information on this topic leads you to fragmented pages or blogs that refer to only a couple of the new features available to you.

What you need is a quick reference guide which gives you the essentials you need and shows you how the code you are familiar with can be improved with ABAP 7.40.

The below document contains exactly this!

It gives examples of “classic” ABAP and its 740 equivalent. It goes into more details on the more difficult topics normally via examples. This allows the reader to dive in to the level they desire. While this document does not contain everything pertaining to ABAP 740 it certainly covers the most useful parts in the experience of the author.

The document has been compiled by drawing on existing material available online as well as trial and error by the author. In particular the blogs by Horst Keller have been useful and are the best reference I have found (prior to this document ). He has a landing page of sorts for his various blogs on the topic here:

ABAP Language News for Release 7.40

Credit also goes to Naimesh Patel for his useful explanations and examples on ABAP 7.40. Here is his example of the “FOR iteration expression” which I leaned on (links to his other 740 articles can be found at the bottom of the link):

http://zevolving.com/2015/05/abap-740-for-iteration-expression/

I compiled the below document to make the transition to using ABAP 740 easier for myself and my project team. It has worked well for us and I hope it will do the same for you.

Regards,

Jeff Towell

ABAP 7.40 Quick Reference  

Contents

1. Inline Declarations

2. Table Expressions

3. Conversion Operator CONV

     I.  Definition

     II. Example

4. Value Operator VALUE

     I.   Definition

     II.  Example for structures

     III. Examples for internal tables

5. FOR operator

     I.   Definition

     II.  Explanation

     III. Example 1

     IV. Example 2

     V. FOR with THEN and UNTIL|WHILE

6. Reduction operator REDUCE

     I.   Definition

     II.  Note

     III. Example 1

     IV. Example 2

     V.  Example 3

7. Conditional operators COND and SWITCH

     I.   Definition

     II.  Example for COND

     III. Example for SWITCH

8. CORRESPONDING operator

     I.   Definition

     II.  Example Code

     III. Output

     IV. Explanation

     V.  Additions MAPPING and EXCEPT

9.Strings

     I.   String Templates

     II.  Concatenation

     III. Width/Alignment/Padding.

     IV. Case

     V.  ALPHA conversion

     VI.  Date conversion

10. Loop at Group By

     I.   Definition

     II.  Explanation

     III. Example

     IV. Output

11. Classes/Methods

     I.   Referencing fields within returned structures

     II.  Methods that return a type BOOLEAN

     III. NEW operator

12. Meshes

     I.   Problem

     II.  Solution

     III. Output

13. Filter

     I.   Definition

     II.  Problem

     III. Solution

1. Inline Declarations

2. Table Expressions

If a table line is not found, the exception CX_SY_ITAB_LINE_NOT_FOUND is raised. No sy-subrc.

NB: There will be a short dump if you use an inline expression that references a non-existent record.

        SAP says you should therefore assign a field symbol and check sy-subrc.

ASSIGN lt_tab[ 1 ] to FIELD–SYMBOL(<ls_tab>).
IF sy–subrc = 0.
…
ENDIF.

NB: Use itab [ table_line = … ] for untyped tables.

3. Conversion Operator CONV

I.  Definition

CONV dtype|#( … )

dtype = Type you want to convert to (explicit)

#     = compiler must use the context to decide the type to convert to (implicit)

II. Example

Method cl_abap_codepage=>convert_to expects a string

4. Value Operator VALUE

I. Definition

     Variables:    VALUE dtype|#( )

     Structures:  VALUE dtype|#( comp1 = a1 comp2 = a2 … )

     Tables:         VALUE dtype|#( ( … ) ( … ) … ) …

II. Example for structures

     TYPES:  BEGIN OF ty_columns1, “Simple structure
                     cols1 TYPE i, 
                     cols2 TYPE i, 
                   END OF ty_columns1.

      TYPES: BEGIN OF ty_columnns2,  “Nested structure
                     coln1 TYPE i, 
                     coln2 TYPE ty_columns1, 
                  END OF ty_columns2.

      DATA: struc_simple TYPE ty_columns1, 
                struc_nest    TYPE ty_columns2.

     struct_nest   = VALUE t_struct(coln1 = 1 
                                                  coln2-cols1 = 1 
                                                  coln2-cols2 = 2 ).

     OR

     struct_nest   = VALUE t_struct(coln1 = 1 
                                                   coln2 = VALUE #( cols1 = 1 
                                                   cols2 = 2 ) ).

III. Examples for internal tables

Elementary line type:

TYPES t_itab TYPE TABLE OF i WITH EMPTY KEY.

DATA itab TYPE t_itab.

itab = VALUE #( ( ) ( 1 ) ( 2 ) ).

Structured line type (RANGES table):

DATA itab TYPE RANGE OF i.

itab = VALUE #( sign = ‘I’  option = ‘BT’ ( low = 1  high = 10 ) 
( low = 21 high = 30 ) 
( low = 41 high = 50 ) 
option = ‘GE’ ( low = 61 )  ).

5. FOR operator

I. Definition

     FOR wa|<fs> IN itab [INDEX INTO idx] [cond]

II. Explanation

This effectively causes a loop at itab. For each loop the row read is assigned to a work area (wa) or field-symbol(<fs>).

This wa or <fs> is local to the expression i.e. if declared in a subrourine the variable wa or <fs> is a local variable of

that subroutine. Index like SY-TABIX in loop.

Given: 

TYPES: BEGIN OF ty_ship,
           tknum TYPE tknum,     “Shipment Number
           name  TYPE ernam,     “Name of Person who Created the Object
           city  TYPE ort01,     “Starting city
           route TYPE route,     “Shipment route
       END OF ty_ship.
TYPES: ty_ships TYPE SORTED TABLE OF ty_ship WITH UNIQUE KEY tknum.
TYPES: ty_citys TYPE STANDARD TABLE OF ort01 WITH EMPTY KEY.

GT_SHIPS type ty_ships. -> has been populated as follows:

III. Example 1

Populate internal table GT_CITYS with the cities from GT_SHIPS.

IV. Example 2

Populate internal table GT_CITYS with the cities from GT_SHIPS where the route is R0001.

Note: ls_ship does not appear to have been declared but it is declared implicitly.

V. FOR with THEN and UNTIL|WHILE

FOR i = … [THEN expr] UNTIL|WHILE log_exp

Populate an internal table as follows:

TYPES:
  BEGIN OF ty_line,
    col1 TYPE i,
    col2 TYPE i,
    col3 TYPE i,
  END OF ty_line,
  ty_tab TYPE STANDARD TABLE OF ty_line WITH EMPTY KEY.

6. Reduction operator REDUCE

I. Definition

… REDUCE type(

INIT result = start_value

           …

FOR for_exp1

FOR for_exp2

…

NEXT …

           result = iterated_value

… )

II. Note

     While VALUE and NEW expressions can include FOR expressions, REDUCE must include at least one FOR expression. You can use all kinds      of FOR expressions in REDUCE:

• with IN for iterating internal tables
• with UNTIL or WHILE for conditional iterations

III. Example 1

Count lines of table that meet a condition (field F1 contains “XYZ”).

IV. Example 2

Sum the values 1 to 10 stored in the column of a table defined as follows

DATA gt_itab TYPE STANDARD TABLE OF i WITH EMPTY KEY.
gt_itab = VALUE #( FOR j = 1 WHILE j <= 10 ( j ) ).

V. Example 3

Using a class reference – works because “write” method returns reference to instance object

7. Conditional operators COND and SWITCH

I. Definition

… COND dtype|#( WHEN log_exp1 THEN result1 
[ WHEN log_exp2 THEN result2 ] 
… 
[ ELSE resultn ] ) …

… SWITCH dtype|#( operand 
WHEN const1 THEN result1 
[ WHEN const2 THEN result2 ] 
… 
[ ELSE resultn ] ) …

II. Example for COND

DATA(time) =

  COND string(

    WHEN sy-timlo < ‘120000’ THEN

      |{ sy-timlo TIME = ISO } AM|

    WHEN sy-timlo > ‘120000’ THEN

      |{ CONV t( sy-timlo – 12 * 3600 )

TIME = ISO } PM|

    WHEN sy-timlo = ‘120000’ THEN

      |High Noon|

    ELSE

      THROW cx_cant_be( ) ).

III. Example for SWITCH

DATA(text) =
NEW class( )->meth(
                     SWITCH #( sy-langu
                              WHEN ‘D’ THEN `DE`
                              WHEN ‘E’ THEN `EN`
                               ELSE THROW cx_langu_not_supported( ) ) ).

8. Corresponding Operator

I. Definition

… CORRESPONDING type( [BASE ( base )] struct|itab [mapping|except] )

II. Example Code

III. Output

IV. Explanation

Given structures ls_line1 & ls_line2 defined and populated as above.

1.   The contents of ls_line1 are moved to ls_line2 where there is a matching column name. Where there is no

            match the column of ls_line2 is initialised.

  2. This uses the existing contents of ls_line2 as a base and overwrites the matching columns from ls_line1.

            This is exactly like MOVE-CORRESPONDING.

  3. This creates a third and new structure (ls_line3) which is based on ls_line2 but overwritten by matching

             columns of ls_line1.

V. Additions MAPPING and EXCEPT

   MAPPING allows you to map fields with non-identically named components to qualify for the data transfer.

   … MAPPING  t1 = s1 t2 = s2

   EXCEPT allows you to list fields that must be excluded from the data transfer

   … EXCEPT  {t1 t2 …}

9. Strings

I. String Templates

A string template is enclosed by two characters “|” and creates a character string.

Literal text consists of all characters that are not in braces {}. The braces can contain:

• data objects,

• calculation expressions,

• constructor expressions,

• table expressions,

• predefined functions, or

• functional methods and method chainings

II. Concatenation

III. Width/Alignment/Padding

WRITE / |{ ‘Left’     WIDTH = 20 ALIGN = LEFT   PAD = ‘0’ }|.
WRITE / |{ ‘Centre’   WIDTH = 20 ALIGN = CENTER PAD = ‘0’ }|.
WRITE / |{ ‘Right’    WIDTH = 20 ALIGN = RIGHT  PAD = ‘0’ }|.

IV. Case

WRITE / |{ ‘Text’ CASE = (cl_abap_format=>c_raw) }|.
WRITE / |{ ‘Text’ CASE = (cl_abap_format=>c_upper) }|.
WRITE / |{ ‘Text’ CASE = (cl_abap_format=>c_lower) }|.

V. ALPHA conversion

DATA(lv_vbeln) = ‘0000012345’.
WRITE / |{ lv_vbeln  ALPHA = OUT }|.     “or use ALPHA = IN to go in other direction

VI. Date conversion

WRITE / |{ pa_date DATE = ISO }|.           “Date Format YYYY-MM-DD
WRITE / |{ pa_date DATE = User }|.          “As per user settings
WRITE / |{ pa_date DATE = Environment }|.   “Formatting setting of language environment

10. Loop at Group By

I. Definition

LOOP AT itab result [cond] GROUP BY key ( key1 = dobj1 key2 = dobj2 … 
      [gs = GROUP SIZE] [gi = GROUP INDEX] ) 
      [ASCENDING|DESCENDING [AS TEXT]] 
      [WITHOUT MEMBERS] 
      [{INTO group}|{ASSIGNING <group>}]
      … 
      [LOOP AT GROUP group|<group> 
      … 
      ENDLOOP.] 
      …

ENDLOOP.

II. Explanation

The outer loop will do one iteration per key. So if 3 records match the key there will only be one iteration for these 3 records. The structure “group” (or

“<group>” ) is unusual in that it can be looped over using the “LOOP AT GROUP” statement. This will loop over the 3 records (members) of the group. The

structure “group” also contains the current key as well as the size of the group and index of the group ( if GROUP SIZE and GROUP INDEX have been

assigned a field name). This is best understood by an example.

III. Example

IV. Output

Group: 1    Role: ABAP guru           Number in this role: 3

                 John

                 Barry

                 Arthur

Average age: 40.66666666666666666666666666666667

Group: 2    Role: FI Consultant       Number in this role: 2

                  Alice

                  Mary

Average age: 39.5

Group: 3    Role: SD Consultant       Number in this role: 1

                  Mandy

Average age: 64

11. Classes/Methods

I. Referencing fields within returned structures

II. Methods that return a type BOOLEAN

NB: The type “BOOLEAN” is not a true Boolean but a char1 with allowed values X,- and <blank>.

       Using type “FLAG” or “WDY_BOOLEAN” works just as well.

III. NEW operator

This operator can be used to instantiate an object.

12. Meshes

Allows an association to be set up between related data groups.

I. Problem

Given the following 2 internal tables:

TYPES: BEGIN OF t_manager,
name   TYPE char10,
salary TYPE int4,
END OF t_manager,
tt_manager TYPE SORTED TABLE OF t_manager WITH UNIQUE KEY name.

TYPES: BEGIN OF t_developer,
name    TYPE char10,
salary  TYPE int4,
manager TYPE char10,   “Name of manager
END OF t_developer,
tt_developer TYPE SORTED TABLE OF t_developer WITH UNIQUE KEY name.

Populated as follows:

Get the details of Jerry’s manager and all developers managed by Thomas.

II. Solution

III. Output

     Jerry’s manager: Jason          Salary: 3000

     Thomas’ developers:

     Employee name: David

     Employee name: Jack

     Employee name: John

13. Filter

Filter the records in a table based on records in another table.

I. Definition

… FILTER type( itab [EXCEPT] [IN ftab] [USING KEY keyname] 
           WHERE c1 op f1 [AND c2 op f2 […]] )

II. Problem

Filter an internal table of Flight Schedules (SPFLI) to only those flights based on a filter table that contains the fields Cityfrom and CityTo.

III. Solution

Note: using the keyword “EXCEPT” (see definition above) would have returned the exact opposite records i.e all records EXCEPT for those those returned above.

CDS View를 재활용하여 CDS view를 만들때에는 association을 이용하여 만들어주어야 한다.

@AbapCatalog.sqlViewName: 'ZQMCV_SQLV_0001'

@AbapCatalog.compiler.compareFilter: true

@AccessControl.authorizationCheck: #CHECK

@ClientDependent: true

@EndUserText.label: 'MCHBH cds view test'

define view ZQMCV_0001Z as 

select from nsdm_e_mchbh as hbh

association [1] to nsdm_e_mchb as hb

    on hb.matnr = hbh.matnr

   and hb.werks = hbh.werks

   and hb.lgort = hbh.lgort

   and hb.charg = hbh.charg

{    

    key hbh.matnr,

    key hbh.werks,

    key hbh.lgort,

    key hbh.charg,

    key concat(hbh.lfgja, hbh.lfmon) as h_yearmon,

    concat(hb.lfgja,  hb.lfmon)  as yearmon,

    hbh.clabs as h_CLABS,

    hbh.cumlm as h_CUMLM,

    hbh.cinsm as h_CINSM,

    hbh.ceinm as h_CEINM,

    hbh.cspem as h_CSPEM,

    hbh.cretm as h_CRETM,

    hb.clabs,

    hb.cumlm,

    hb.cinsm,

    hb.ceinm,

    hb.cspem,

    hb.cretm

} 

4개의 cds view를 이용하여 max h_yearmon의 값을 한꺼번에 가져오는 CDS view 생성

=======================================================================

** MCHB와 MCHBH의 data join

@AbapCatalog.sqlViewName: 'ycds_ass_trest01'

@AbapCatalog.compiler.compareFilter: true

@AccessControl.authorizationCheck: #CHECK

@EndUserText.label: 'cds association test'

define view yass_cds_test01_01 as 

select from nsdm_e_mchbh as hbh

association [1] to nsdm_e_mchb as hb

    on hb.matnr = hbh.matnr

   and hb.werks = hbh.werks

   and hb.lgort = hbh.lgort

   and hb.charg = hbh.charg 

   {

    key hbh.matnr,

    key hbh.werks,

    key hbh.lgort,

    key hbh.charg,

    key concat(hbh.lfgja, hbh.lfmon) as h_yearmon,

    concat(hb.lfgja,  hb.lfmon)  as yearmon,

    hbh.clabs as h_CLABS,

    hbh.cumlm as h_CUMLM,

    hbh.cinsm as h_CINSM,

    hbh.ceinm as h_CEINM,

    hbh.cspem as h_CSPEM,

    hbh.cretm as h_CRETM,

    hb.clabs,

    hb.cumlm,

    hb.cinsm,

    hb.ceinm,

    hb.cspem,

    hb.cretm

}  

=======================================================================

** MCHBH의 hbh.lfgja, hbh.lfmon concat

@AbapCatalog.sqlViewName: 'ycds_ass_trest02'

@AbapCatalog.compiler.compareFilter: true

@AccessControl.authorizationCheck: #CHECK

@EndUserText.label: 'cds association test 2'

define view yass_cds_test01_02 as 

select  

    key hbh.matnr,

    key hbh.werks,

    key hbh.lgort,

    key hbh.charg,    

    concat(hbh.lfgja, hbh.lfmon) as h_yearmon

from nsdm_e_mchbh as hbh

group by hbh.matnr,

    hbh.werks,

    hbh.lgort,

    hbh.charg,

    hbh.lfgja, hbh.lfmon

========================================================================

** MCHBH의 max h_yearmon data table

@AbapCatalog.sqlViewName: 'ycds_ass_trest04'

@AbapCatalog.compiler.compareFilter: true

@AccessControl.authorizationCheck: #CHECK

@EndUserText.label: 'cds association test 4'

define view yass_cds_test01_04 as

select   

    key hbh.matnr,

    key hbh.werks,

    key hbh.lgort,

    key hbh.charg,    

    max(h_yearmon) as h_yearmon

from yass_cds_test01_02 as hbh

group by hbh.matnr,

    hbh.werks,

    hbh.lgort,

    hbh.charg 

=======================================================================

** MCHB와 MCHBH 중 h_yearmon 값이 max 인 데이타 select

@AbapCatalog.sqlViewName: 'ycds_ass_trest03'

@AbapCatalog.compiler.compareFilter: true

@AccessControl.authorizationCheck: #CHECK

@EndUserText.label: 'cds association test 3'

define view yass_cds_test01_03 as 

select from yass_cds_test01_01 as hbh

   inner join yass_cds_test01_04 as hbm

    on hbh.matnr = hbm.matnr

   and hbh.werks = hbm.werks

   and hbh.lgort = hbm.lgort

   and hbh.charg = hbm.charg 

   and hbh.h_yearmon = hbm.h_yearmon {

    key hbh.matnr,

    key hbh.werks,

    key hbh.lgort,

    key hbh.charg,

    key hbm.h_yearmon,

    hbh.yearmon,

    hbh.h_CLABS,

    hbh.h_CUMLM,

    hbh.h_CINSM,

    hbh.h_CEINM,

    hbh.h_CSPEM,

    hbh.h_CRETM,

    hbh.clabs,

    hbh.cumlm,

    hbh.cinsm,

    hbh.ceinm,

    hbh.cspem,

    hbh.cretm

}

When I mentioned CTEs one year ago, the reaction was that I’m “teasing“. But well, here we are. The Open SQL boys are really a hard-working bunch.

The wish was to have a SELECT … FROM subquery in Open SQL. That’s one thing, you can use CTEs for:

    WITH
      +conns AS (
        SELECT carrname, connid, cityfrom, cityto
              FROM spfli
                JOIN scarr ON spfli~carrid = scarr~carrid
              WHERE spfli~carrid = @carrid ),
      +cnts AS (
        SELECT COUNT(*) AS cnt
               FROM +conns )
      SELECT *
             FROM +cnts
               CROSS JOIN +conns
             ORDER BY carrname, connid
             INTO CORRESPONDING FIELDS of TABLE @itab.

The new SQL keyword WITH introduces the definition of one or more CTEs. Each CTE is a kind of subquery that produces a tabular result that can be used as a data source in all subsequent queries of the same WITH statement. In the example, a general table expression +conns (where the + is a mandatory prefix of the name) creates a table of flight connections. A further expression, +cnts, determines the number of entries in the result set of +conns. The closing mainquery combines the result sets of both general table expressions using a cross join (also new in ABAP 7.51).

WITH 
  +cities AS ( 
    SELECT cityfrom AS city 
           FROM spfli 
           WHERE carrid = @carrid 
    UNION DISTINCT 
    SELECT cityto AS city 
           FROM spfli 
           WHERE carrid = @carrid ) 
  SELECT * 
         FROM sgeocity 
         WHERE city IN ( SELECT city 
                                FROM +cities ) 
         INTO TABLE @DATA(result). 

In this example, there is one CTE +cities defining a subquery including a UNION. The result set of the CTE is evaluated as the data source of the subquery of the WHERE condition of the main query of the WITH statement.

The general CTE syntax is as follows:

WITH 
  +cte1[( name1, name2, ... )] AS ( SELECT subquery_clauses ... ), 
  +cte2[( name1, name2, ... )] AS ( SELECT subquery_clauses ... ), 
   ... 
  SELECT mainquery_clauses 
         ...
         INTO ...
       ... 
[ENDWITH]. 

Each WITH statement must be completed by a mainquery that uses at least one of its CTEs as a data source and each CTE must be used in at least one other subsequent query. Up to now a CTE cannot use itself as a data source. WITH can be used as a standalone statement or after the statement OPEN CURSOR. 

The ENDWITH is an ABAP specialty that fulfills the same task as ENDSELECT. If you don’t write in to an internal table behind INTO of the main query, you open a WITH loop that must be closed with ENDWITH.

With  ( name1, name2, … ) you can redefine the column names of the tabular result sets of a CTE, e.g.

WITH 
  +connections AS ( 
    SELECT spfli~carrid, carrname, connid, cityfrom, cityto 
           FROM spfli 
           INNER JOIN scarr 
             ON scarr~carrid = spfli~carrid 
           WHERE spfli~carrid BETWEEN @from_id AND @to_id ), 
  +sum_seats AS ( 
    SELECT carrid, connid, SUM( seatsocc ) AS sum_seats 
           FROM sflight 
           WHERE carrid BETWEEN @from_id AND @to_id 
           GROUP BY carrid, connid ), 
  +result( name, connection, departure, arrival, occupied ) AS ( 
    SELECT carrname, c~connid, cityfrom, cityto, sum_seats 
           FROM +connections AS c 
             INNER JOIN +sum_seats AS s 
               ON c~carrid = s~carrid AND 
                  c~connid = s~connid ) 
  SELECT * 
         FROM +result 
         ORDER BY name, connection 
         INTO TABLE @DATA(result).

The result sets of both general table expressions +connections and +sum_seats are merged in the subquery of the general table expression +result in a join expression. An explicit name list assigns names to the resulting columns. These names are used in the mainquery to sort the results.

With the introduction of WITH, the standalone statement SELECT suddenly lost a bit of its peculiarity. In fact it can be seen as a special case of a mainquery without WITH. Therefore the terminology of queries was generalized in Open SQL: Each language element SELECT implements a query and we distinguish between mainqueries and subqueries.

• A mainquery is either a standalone SELECT statement, the final query of a WITH statement, or the final query of an OPEN CURSOR statement.
• A subquery is possible in a WHERE condition, after WITH for the definition of a CTE, or as a data source of an INSERT statement.

All queries can be combined with UNION and the most clauses are common for all queries except the ABAP specific INTO that can be used for the mainqueries of a standalone WITH and a standalone SELECT and behind a FETCH only.

so_object_send function을 이용하면 sender에 internet email을 지정하여 전송할 수 있다.

FUNCTION zcm_send_mail.
*"----------------------------------------------------------------------
*"*"Local interface:
*"  IMPORTING
*"     VALUE(IS_SENDER) TYPE  ZQMS_038
*"     VALUE(IV_TITLE) TYPE  ZWF_TITLECO
*"     VALUE(IV_RETURN) TYPE  CHAR1 OPTIONAL
*"  EXPORTING
*"     VALUE(EV_RESULT) TYPE  CHAR1
*"     VALUE(EV_ERR_MSG) TYPE  STRING
*"  TABLES
*"      T_RECEIVER TYPE  ZQMY_0001
*"      T_BODY STRUCTURE  W3HTML
*"  EXCEPTIONS
*"      INVALID_USER_ERROR
*"      NO_EMAILID
*"      INVALID_EMPLOYEE_NUMBER
*"      INVALID_MYSINGLEID
*"      INVALID_ID_TYPE
*"      INVALID_WF_OBJECT
*"----------------------------------------------------------------------

  DATA lv_object_hd     TYPE sood1.
  DATA lv_object_type          TYPE sood-objtp.
  DATA : lv_originator  TYPE soos1-recextnam,
         lv_origin_type TYPE soos1-recesc.

  DATA lt_objcont       TYPE STANDARD TABLE OF soli WITH HEADER LINE.
  DATA lt_receivers     TYPE STANDARD TABLE OF soos1 WITH HEADER LINE.
  DATA lt_packing_list  TYPE STANDARD TABLE OF soxpl WITH HEADER LINE.
*
  DATA: lv_lines     TYPE i,
        lo_ex_system TYPE REF TO cx_ai_system_fault,
        lo_ex_app    TYPE REF TO cx_ai_application_fault.

  CLEAR : ev_result, ev_err_msg. ", ls_en_request.

*--------------------------------------------------------------------*
* 0. Check Input Value
*--------------------------------------------------------------------*
  IF ( t_receiver[] IS INITIAL ).
    ev_err_msg = 'Enter mail receiver (required field)'.
    ev_result  = 'E'.
    EXIT.
  ELSEIF ( t_body[] IS INITIAL ).
    ev_err_msg = 'Enter mail body (required field)'.
    ev_result  = 'E'.
    EXIT.
  ENDIF.

*  PERFORM check_mailuser USING    is_sender  iv_return
*                         CHANGING ev_err_msg.
*  IF ev_err_msg IS NOT INITIAL.
*    ev_result = c_e.  EXIT.
*  ENDIF.

*--------------------------------------------------------------------*
* 3. Set Mail Body
*--------------------------------------------------------------------*
  CLEAR : lv_object_hd.
  lv_object_hd-objla  = sy-langu.
  lv_object_hd-objdes = iv_title.
  lv_object_hd-objnam = 'MESSAGE'.
  lv_object_hd-objsns = 'O'.
  lv_object_hd-file_ext = 'HTM'.
  lv_object_hd-objpri = '1'.
  lv_object_hd-objcp  = 'X'.

  lv_object_type = 'RAW'.

  LOOP AT t_body.

    lt_objcont-line = t_body.
    APPEND lt_objcont. CLEAR lt_objcont.

  ENDLOOP.

*  READ TABLE t_body INDEX 1.
*  SEARCH t_body FOR '<HTML>' IN CHARACTER MODE STARTING AT 1 ENDING AT 10.
*  IF sy-subrc EQ 0.
*    ls_en_request-header_helper_csvo-b_html_content_check = 'true'.
*  ENDIF.


*--------------------------------------------------------------------*
* 4. Set Recipient Info
*--------------------------------------------------------------------*
*   i_seq_id (필수값) - 일련번호 (0부터 순차적으로 증가)
*   rec_type (필수값) - 수신형태 (t : 수신, c : 참조, b : 비밀참조)
*   rec_addr (필수값) - 수신자메일주소

  CLEAR: lt_receivers, lt_receivers[].
  LOOP AT t_receiver.

*    PERFORM check_mailuser USING    t_receiver  iv_return
*                           CHANGING ev_err_msg.
*    IF ev_err_msg IS NOT INITIAL  AND iv_return IS INITIAL.
*      ev_result = 'E'.
*      EXIT.
*    ENDIF.

    TRANSLATE  t_receiver-emailid TO LOWER CASE.
    lt_receivers-recextnam  = t_receiver-emailid.
    lt_receivers-sndart = 'INT'.
    lt_receivers-sndpri = '1'.
    lt_receivers-recesc = 'U'.

    APPEND lt_receivers. CLEAR lt_receivers.
  ENDLOOP.

  lv_originator = is_sender-emailid.
  lv_origin_type = 'U'.

  CHECK ev_result NE 'E'.

*--------------------------------------------------------------------*
* 5. Set Resource Info
*--------------------------------------------------------------------*
*   email    (필수값) - 발신자메일주소
*   locale   (필수값) - 로케일정보 (ko_KR : 한국, 중국 : zh_CN, 일본 : ja_JP, 나머지 : en_US)
*   encoding (필수값) - 메일인코딩정보 (euc-kr 또는 utf-8)

*--------------------------------------------------------------------*
* 6. Send Mail
*--------------------------------------------------------------------*
*************************&&메일을 전송하는 FUNCTION.....

  TRY.

      CALL FUNCTION 'SO_OBJECT_SEND'
        EXPORTING
          object_hd_change           = lv_object_hd
          object_type                = lv_object_type
          owner                      = sy-uname
          originator                 = lv_originator
          originator_type            = lv_origin_type
        TABLES
          objcont                    = lt_objcont
          receivers                  = lt_receivers
        EXCEPTIONS
          active_user_not_exist      = 1
          communication_failure      = 2
          component_not_available    = 3
          folder_not_exist           = 4
          folder_no_authorization    = 5
          forwarder_not_exist        = 6
          note_not_exist             = 7
          object_not_exist           = 8
          object_not_sent            = 9
          object_no_authorization    = 10
          object_type_not_exist      = 11
          operation_no_authorization = 12
          owner_not_exist            = 13
          parameter_error            = 14
          substitute_not_active      = 15
          substitute_not_defined     = 16
          system_failure             = 17
          too_much_receivers         = 18
          user_not_exist             = 19
          originator_not_exist       = 20
          x_error                    = 21.
    CATCH cx_ai_system_fault INTO lo_ex_system.
      ev_result  = 'E'.
      ev_err_msg = lo_ex_system->if_message~get_text( ).
    CATCH cx_ai_application_fault INTO lo_ex_app.
      ev_result  = 'E'.
      ev_err_msg = lo_ex_app->if_message~get_text( ).
  ENDTRY.

  IF sy-subrc = 0.
    "SO_OBJECT_SEND 사용시에는 commit work 해줘야 함.
    COMMIT WORK.

    ev_result = 'S'.
    EXIT.
  ELSE.
    ev_result = sy-subrc.
    EXIT.
  ENDIF.

ENDFUNCTION.

  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.