MT101 message is a request to transfer fund from payer’s account to receiver’s. To make the transactions like this, MT101 message format is used to do the communication.

Below is the sample MT101 file format:

Why and where MT101 message type is used?

Well it can be understood if you look at the body of MT101 format. The body of SWIFT MT101 Message contains header, sender/ordering party details and customer/receiving party details. It means there will be blocks of each transaction in MT101 file and each transaction block will contain sender and receiver details.

Now let’s look at the other file formats, which body contains header, transaction details and footer. So these formats are specifically for sending payment from one bank to other receiver’s banks. But MT101 file is made for paying through multiple banks to many banks.

In easy words as mentioned above each transaction will have one sending bank and one receiving bank in MT101 format. So in single file there might be multiple sending banks and multiple receiving banks.

Hopefully now we understand use of MT101 message but now question arises is how a company/organization use this and how it can be helpful than other file formats?

To understand the answer of this question, We would like give you a scenario. Imagine a multinational company based in USA, who is spread across America having hundreds of company code and thousand bank accounts.

Now when in SAP you do the payment run from each bank account there should be a payment file configured for each bank. Imagine the efforts of having this much DME structures and payment files. It’s a huge activity of maintaining these file formats and matching the all requirements. This is where MT101 helps. With this you can use MT101 format for every bank. All the payment files from all banks will be created in MT101 format.And we know the structure of MT101 (header, sender details, receiver details). Now the trick here is, we don’t send MT101 directly to bank unlike in other file formats. Because we don’t know whether bank will understand MT101 or not.

So we send all the files to a middle man i.e. SWIFT which act as a middle-ware here and then SWIFT reads the MT101 and take call to which bank this file should go for payment. This is the reason in each transaction MT101 haves details of sending bank/company. This process is helpful to the organisations who use IHC (in house cash management). Who have worked on the IHC might be easily relate to this or find how useful is this.

Thanks for reading, if you want to learn more about bank payment files and DME in SAP then you can checkout this eBook.

Describe using BCset functionality to download SAP configuration and upload it in any other SAP system with specific limitation.

In this blog post we are going to explain:

1- The business cases that we may need to keep our configuration

2- Demo for how to use BC sets and upload and activate BC set files

3- Some limitations related to BC sets used

by End of this video you can use BCsets and keep a copy from your configuration

Get update of new blog posts

Name

Country Your country Afghanistan Aland Islands Albania Algeria American Samoa Andorra Angola Anguilla Antarctica Antigua and Barbuda Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas Bahrain Bangladesh Barbados Belarus Belgium Belize Benin Bermuda Bhutan Bolivia Bonaire, Saint Eustatius and Saba Bosnia and Herzegovina Botswana Bouvet Island Brazil British Indian Ocean Territory British Virgin Islands Brunei Bulgaria Burkina Faso Burundi Cambodia Cameroon Canada Cape Verde Cayman Islands Central African Republic Chad Chile China Christmas Island Cocos Islands Colombia Comoros Cook Islands Costa Rica Croatia Cuba Curacao Cyprus Czech Republic Democratic Republic of the Congo Denmark Djibouti Dominica Dominican Republic East Timor Ecuador Egypt El Salvador Equatorial Guinea Eritrea Estonia Ethiopia Falkland Islands Faroe Islands Fiji Finland France French Guiana French Polynesia French Southern Territories Gabon Gambia Georgia Germany Ghana Gibraltar Greece Greenland Grenada Guadeloupe Guam Guatemala Guernsey Guinea Guinea-Bissau Guyana Haiti Heard Island and McDonald Islands Honduras Hong Kong Hungary Iceland India Indonesia Iran Iraq Ireland Isle of Man Israel Italy Ivory Coast Jamaica Japan Jersey Jordan Kazakhstan Kenya Kiribati Kosovo Kuwait Kyrgyzstan Laos Latvia Lebanon Lesotho Liberia Libya Liechtenstein Lithuania Luxembourg Macao Macedonia Madagascar Malawi Malaysia Maldives Mali Malta Marshall Islands Martinique Mauritania Mauritius Mayotte Mexico Micronesia Moldova Monaco Mongolia Montenegro Montserrat Morocco Mozambique Myanmar Namibia Nauru Nepal Netherlands New Caledonia New Zealand Nicaragua Niger Nigeria Niue Norfolk Island North Korea Northern Mariana Islands Norway Oman Pakistan Palau Palestinian Territory Panama Papua New Guinea Paraguay Peru Philippines Pitcairn Poland Portugal Puerto Rico Qatar Republic of the Congo Reunion Romania Russia Rwanda Saint Barthelemy Saint Helena Saint Kitts and Nevis Saint Lucia Saint Martin Saint Pierre and Miquelon Saint Vincent and the Grenadines Samoa San Marino Sao Tome and Principe Saudi Arabia Senegal Serbia Seychelles Sierra Leone Singapore Sint Maarten Slovakia Slovenia Solomon Islands Somalia South Africa South Georgia and the South Sandwich Islands South Korea South Sudan Spain Sri Lanka Sudan Suriname Svalbard and Jan Mayen Swaziland Sweden Switzerland Syria Taiwan Tajikistan Tanzania Thailand Togo Tokelau Tonga Trinidad and Tobago Tunisia Turkey Turkmenistan Turks and Caicos Islands Tuvalu U.S. Virgin Islands Uganda Ukraine United Arab Emirates United Kingdom United States United States Minor Outlying Islands Uruguay Uzbekistan Vanuatu Vatican Venezuela Vietnam Wallis and Futuna Western Sahara Yemen Zambia Zimbabwe

Email address:

Leave this field empty if you're human:

Introduction

After working with SAP for more than 15 years and travelling across the Globe for SAP Projects one issue I always use to have how can I keep track of all the SAP Tables associated with different Modules. If you are working as a SAP ABAP Consultant you need to keep the name of tables in your Fingertips. Sometimes this you know from other Experts and sometimes you have to dig it out.

After exploring I found a very easy way to know the Tables that contains all the four fields or Data Element in the same table and has data in it.

SAP is just like an ocean and every droplet is like one SAP Table. This is one of the first program I create in any Project.

I have one request the .1% time you saved while implementing this Blog, help someone in need by doing Service. It can be as simple as playing with a Kid also.

This solution only does Table. I will do another blog  for Views also.

Solution

Go to SE38-> Create a Program and Paste this Code.

Here is the Execution. Just to let you know I have Excluded the Table Beginning with ‘/’. If you want to add it just tweak the code.

In the Below example I am looking for tables with these 2 fields/Data Element. EBELN and EBELP

And here is the Result

Lets be adventurous and try with 4 fields

Before this I never knew EKPO has all the above 4 Fields/Data Element.

Below is the Code that probably can fetch some serious Fun Time to learn something more.

TABLES: DD03L,

        BOOLE.

DATA:DREF TYPE REF TO DATA.

FIELD-SYMBOLS:<TABLE> TYPE STANDARD TABLE.

TYPE-POOLS: SLIS, ICON.

* Internal Tables

TYPES: BEGIN OF T_IALV,

         TABNAME TYPE DD03L-TABNAME,

         FIELD1  TYPE DD03L-FIELDNAME,

         FIELD2  TYPE DD03L-FIELDNAME,

         FIELD3  TYPE DD03L-FIELDNAME,

         FIELD4  TYPE DD03L-FIELDNAME,

       END OF T_IALV .

DATA: IALV   TYPE STANDARD TABLE OF T_IALV,

      WA_ALV TYPE T_IALV.

DATA: ALV_CONTAINER TYPE REF TO CL_GUI_CUSTOM_CONTAINER,

      ALV_GRID      TYPE REF TO CL_GUI_ALV_GRID,

      OK_CODE       LIKE SY-UCOMM,

      FIELDCAT      TYPE SLIS_T_FIELDCAT_ALV WITH HEADER LINE.

SELECT-OPTIONS:S_FIELD1 FOR DD03L-FIELDNAME NO-EXTENSION,

S_FIELD2 FOR DD03L-FIELDNAME NO-EXTENSION,

S_FIELD3 FOR DD03L-FIELDNAME NO-EXTENSION,

S_FIELD4 FOR DD03L-FIELDNAME NO-EXTENSION,

S_EXC FOR BOOLE-BOOLE.

FIELD-SYMBOLS:<FS-TAB13> TYPE MANDT.

DATA:WA_DD1      TYPE DD03L,

     WA_DD2      TYPE DD03L,

     WA_DD3      TYPE DD03L,

     WA_DD4      TYPE DD03L,

     LV_TAB      TYPE DD03L-TABNAME,

     WA_DD_FINAL TYPE DD03L.

IF S_EXC-LOW IS NOT INITIAL.

  LV_TAB = ‘/%’.

ENDIF.

IF S_FIELD1-LOW IS NOT INITIAL.

  SELECT C~TABNAME

    FROM ( ( DD03L AS C

         INNER JOIN DD02V AS P ON P~TABNAME  = C~TABNAME

                              AND P~TABCLASS = ‘TRANSP’)

*                              AND p~cityto   = @cityto )

         INNER JOIN DD09L AS F ON F~TABNAME = P~TABNAME )

    WHERE ( ( C~ROLLNAME EQ @S_FIELD1-LOW )

    OR ( C~FIELDNAME EQ @S_FIELD1-LOW  ) )

    AND P~TABNAME NOT LIKE @LV_TAB

       INTO TABLE @DATA(ITAB13).

ENDIF.

IF S_FIELD2-LOW IS NOT INITIAL.

  SELECT C~TABNAME

  FROM ( ( DD03L AS C

       INNER JOIN DD02V AS P ON P~TABNAME  = C~TABNAME

                            AND P~TABCLASS = ‘TRANSP’)

*                              AND p~cityto   = @cityto )

       INNER JOIN DD09L AS F ON F~TABNAME = P~TABNAME )

  WHERE ( ( C~ROLLNAME EQ @S_FIELD2-LOW )

  OR ( C~FIELDNAME EQ @S_FIELD2-LOW  )    )

  AND P~TABNAME NOT LIKE @LV_TAB

     INTO TABLE @DATA(ITAB14).

ENDIF.

IF S_FIELD3-LOW IS NOT INITIAL.

  SELECT C~TABNAME

  FROM ( ( DD03L AS C

       INNER JOIN DD02V AS P ON P~TABNAME  = C~TABNAME

                            AND P~TABCLASS = ‘TRANSP’)

       INNER JOIN DD09L AS F ON F~TABNAME = P~TABNAME )

  WHERE ( ( C~ROLLNAME EQ @S_FIELD3-LOW )

  OR ( C~FIELDNAME EQ @S_FIELD3-LOW  )    )

  AND P~TABNAME NOT LIKE @LV_TAB

     INTO TABLE @DATA(ITAB15).

ENDIF.

IF S_FIELD4-LOW IS NOT INITIAL.

  SELECT C~TABNAME

FROM ( ( DD03L AS C

     INNER JOIN DD02V AS P ON P~TABNAME  = C~TABNAME

                          AND P~TABCLASS = ‘TRANSP’)

*                              AND p~cityto   = @cityto )

     INNER JOIN DD09L AS F ON F~TABNAME = P~TABNAME )

WHERE ( ( C~ROLLNAME EQ @S_FIELD4-LOW )

OR ( C~FIELDNAME EQ @S_FIELD4-LOW  )

)

AND P~TABNAME NOT LIKE @LV_TAB

*                                AND f~connid = p~connid )

*       ORDER BY c~carrname, p~connid, f~fldate

   INTO TABLE @DATA(ITAB16).

ENDIF.

SORT ITAB13 BY TABNAME.

DELETE ADJACENT DUPLICATES FROM ITAB13 COMPARING TABNAME..

SORT ITAB14 BY TABNAME.

DELETE ADJACENT DUPLICATES FROM ITAB14 COMPARING TABNAME..

SORT ITAB15 BY TABNAME.

DELETE ADJACENT DUPLICATES FROM ITAB15 COMPARING TABNAME..

SORT ITAB16 BY TABNAME.

DELETE ADJACENT DUPLICATES FROM ITAB16 COMPARING TABNAME.

IF S_FIELD1-LOW IS NOT INITIAL.

  LOOP AT ITAB13 INTO DATA(WA_TAB133).

    IF ITAB14[] IS NOT INITIAL.

      READ TABLE ITAB14  INTO DATA(WA_TAB134) WITH KEY TABNAME = WA_TAB133-TABNAME.

      IF SY-SUBRC = 0.

        CREATE DATA DREF TYPE TABLE OF (WA_TAB134-TABNAME).

        IF ITAB15[] IS NOT INITIAL.

          READ TABLE ITAB15  INTO DATA(WA_TAB135) WITH KEY TABNAME = WA_TAB133-TABNAME.

          IF SY-SUBRC = 0.

            IF ITAB16[] IS NOT INITIAL.

              READ TABLE ITAB16  INTO DATA(WA_TAB136) WITH KEY TABNAME = WA_TAB133-TABNAME.

              IF SY-SUBRC = 0.

                ASSIGN DREF->* TO <TABLE>.

SELECT  *

              FROM (WA_TAB134-TABNAME)

                  INTO TABLE @<TABLE>.

                IF <TABLE> IS NOT INITIAL.

                  WA_ALV-TABNAME =  WA_TAB134-TABNAME.

                  WA_ALV-FIELD1 =  S_FIELD1-LOW.

                  WA_ALV-FIELD2 =  S_FIELD2-LOW.

                  WA_ALV-FIELD3 =  S_FIELD3-LOW.

                  WA_ALV-FIELD4 =  S_FIELD4-LOW.

                  APPEND WA_ALV TO IALV.

                  CLEAR WA_ALV.

*      exit.

                ENDIF.

              ELSE.

                ASSIGN DREF->* TO <TABLE>.

SELECT  *

              FROM (WA_TAB134-TABNAME)

                  INTO TABLE @<TABLE>.

                IF <TABLE> IS NOT INITIAL.

                  WA_ALV-TABNAME =  WA_TAB134-TABNAME.

                  WA_ALV-FIELD1 =  S_FIELD1-LOW.

                  WA_ALV-FIELD2 =  S_FIELD2-LOW.

                  WA_ALV-FIELD3 =  S_FIELD3-LOW.

*                  WA_ALV-FIELD4 =  S_FIELD4-LOW.

                  APPEND WA_ALV TO IALV.

                  CLEAR WA_ALV.

*      exit.

                ENDIF.

              ENDIF.

            ELSE.

              ASSIGN DREF->* TO <TABLE>.

SELECT  *

            FROM (WA_TAB134-TABNAME)

                INTO TABLE @<TABLE>.

              IF <TABLE> IS NOT INITIAL.

                WA_ALV-TABNAME =  WA_TAB134-TABNAME.

                WA_ALV-FIELD1 =  S_FIELD1-LOW.

                WA_ALV-FIELD2 =  S_FIELD2-LOW.

                WA_ALV-FIELD3 =  S_FIELD3-LOW.

                APPEND WA_ALV TO IALV.

                CLEAR WA_ALV.

              ENDIF.

            ENDIF.

          ELSE.

            ASSIGN DREF->* TO <TABLE>.

SELECT  *

          FROM (WA_TAB134-TABNAME)

              INTO TABLE @<TABLE>.

            IF <TABLE> IS NOT INITIAL.

              WA_ALV-TABNAME =  WA_TAB134-TABNAME.

              WA_ALV-FIELD1 =  S_FIELD1-LOW.

              WA_ALV-FIELD2 =  S_FIELD2-LOW.

              APPEND WA_ALV TO IALV.

              CLEAR WA_ALV.

            ENDIF.

          ENDIF.

        ELSE.

          ASSIGN DREF->* TO <TABLE>.

SELECT  *

        FROM (WA_TAB134-TABNAME)

            INTO TABLE @<TABLE>.

          IF <TABLE> IS NOT INITIAL.

            WA_ALV-TABNAME =  WA_TAB134-TABNAME.

            WA_ALV-FIELD1 =  S_FIELD1-LOW.

            WA_ALV-FIELD2 =  S_FIELD2-LOW.

            APPEND WA_ALV TO IALV.

            CLEAR WA_TAB134.

          ENDIF.

        ENDIF.

      ENDIF.

    ENDIF.

*  endif.

  ENDLOOP.

ENDIF.

*  Populate Field Catalog

PERFORM GET_FIELDCATALOG.

CALL FUNCTION ‘REUSE_ALV_GRID_DISPLAY’

  EXPORTING

    I_CALLBACK_PROGRAM = SY-REPID

*   is_layout          = w_layout

    IT_FIELDCAT        = FIELDCAT[]

*   it_events          = i_events

  TABLES

    T_OUTTAB           = IALV

  EXCEPTIONS

    PROGRAM_ERROR      = 1

    OTHERS             = 2.

IF SY-SUBRC <> 0.

* Implement suitable error handling here

ENDIF.

************************************************************************

*      Form  Get_Fieldcatalog – Set Up Columns/Headers

************************************************************************

FORM GET_FIELDCATALOG.

  CLEAR: FIELDCAT.

  FIELDCAT-SELTEXT_M    = ‘Tablename’.

  FIELDCAT-FIELDNAME  = ‘TABNAME’.

  FIELDCAT-OUTPUTLEN  = ’36’.

  APPEND FIELDCAT TO FIELDCAT.

  CLEAR: FIELDCAT.

  FIELDCAT-SELTEXT_M   = ‘Field1’.

  FIELDCAT-FIELDNAME  = ‘FIELD1’.

  FIELDCAT-OUTPUTLEN  = ’12’.

  APPEND FIELDCAT TO FIELDCAT.

  CLEAR: FIELDCAT.

  FIELDCAT-SELTEXT_M   = ‘Field2’.

  FIELDCAT-FIELDNAME  = ‘FIELD2’.

  FIELDCAT-OUTPUTLEN  = ’12’.

  APPEND FIELDCAT TO FIELDCAT.

  CLEAR: FIELDCAT.

  FIELDCAT-SELTEXT_M   = ‘Field3’.

  FIELDCAT-FIELDNAME  = ‘FIELD3’.

  FIELDCAT-OUTPUTLEN  = ’12’.

  APPEND FIELDCAT TO FIELDCAT.

  CLEAR: FIELDCAT.

  FIELDCAT-SELTEXT_M    = ‘Field4’.

  FIELDCAT-FIELDNAME  = ‘FIELD4’.

  FIELDCAT-OUTPUTLEN  = ’12’.

  APPEND FIELDCAT TO FIELDCAT.

ENDFORM.

Here is the Selection Screen Parameter label

Conclusion

This will work for both SAP ECC and SAP S/4 HANA

Below is the video version

Get update of new blog posts

Name

Country Your country Afghanistan Aland Islands Albania Algeria American Samoa Andorra Angola Anguilla Antarctica Antigua and Barbuda Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas Bahrain Bangladesh Barbados Belarus Belgium Belize Benin Bermuda Bhutan Bolivia Bonaire, Saint Eustatius and Saba Bosnia and Herzegovina Botswana Bouvet Island Brazil British Indian Ocean Territory British Virgin Islands Brunei Bulgaria Burkina Faso Burundi Cambodia Cameroon Canada Cape Verde Cayman Islands Central African Republic Chad Chile China Christmas Island Cocos Islands Colombia Comoros Cook Islands Costa Rica Croatia Cuba Curacao Cyprus Czech Republic Democratic Republic of the Congo Denmark Djibouti Dominica Dominican Republic East Timor Ecuador Egypt El Salvador Equatorial Guinea Eritrea Estonia Ethiopia Falkland Islands Faroe Islands Fiji Finland France French Guiana French Polynesia French Southern Territories Gabon Gambia Georgia Germany Ghana Gibraltar Greece Greenland Grenada Guadeloupe Guam Guatemala Guernsey Guinea Guinea-Bissau Guyana Haiti Heard Island and McDonald Islands Honduras Hong Kong Hungary Iceland India Indonesia Iran Iraq Ireland Isle of Man Israel Italy Ivory Coast Jamaica Japan Jersey Jordan Kazakhstan Kenya Kiribati Kosovo Kuwait Kyrgyzstan Laos Latvia Lebanon Lesotho Liberia Libya Liechtenstein Lithuania Luxembourg Macao Macedonia Madagascar Malawi Malaysia Maldives Mali Malta Marshall Islands Martinique Mauritania Mauritius Mayotte Mexico Micronesia Moldova Monaco Mongolia Montenegro Montserrat Morocco Mozambique Myanmar Namibia Nauru Nepal Netherlands New Caledonia New Zealand Nicaragua Niger Nigeria Niue Norfolk Island North Korea Northern Mariana Islands Norway Oman Pakistan Palau Palestinian Territory Panama Papua New Guinea Paraguay Peru Philippines Pitcairn Poland Portugal Puerto Rico Qatar Republic of the Congo Reunion Romania Russia Rwanda Saint Barthelemy Saint Helena Saint Kitts and Nevis Saint Lucia Saint Martin Saint Pierre and Miquelon Saint Vincent and the Grenadines Samoa San Marino Sao Tome and Principe Saudi Arabia Senegal Serbia Seychelles Sierra Leone Singapore Sint Maarten Slovakia Slovenia Solomon Islands Somalia South Africa South Georgia and the South Sandwich Islands South Korea South Sudan Spain Sri Lanka Sudan Suriname Svalbard and Jan Mayen Swaziland Sweden Switzerland Syria Taiwan Tajikistan Tanzania Thailand Togo Tokelau Tonga Trinidad and Tobago Tunisia Turkey Turkmenistan Turks and Caicos Islands Tuvalu U.S. Virgin Islands Uganda Ukraine United Arab Emirates United Kingdom United States United States Minor Outlying Islands Uruguay Uzbekistan Vanuatu Vatican Venezuela Vietnam Wallis and Futuna Western Sahara Yemen Zambia Zimbabwe

Email address:

Leave this field empty if you're human: