The reading function behind the SAP ABAP transmission request and the storage database table explain the trial version

In the previous article of this tutorial, we introduced the basics of SAP ABAP system transmission requests:

A friend asked:

Hello, I have a question to ask, the configuration table of the transmission request will be generated in the development system through SM30 maintenance, where is the modified content corresponding to this transmission request? SE09-related CRs only contain keyword-related information in the configuration table, and you cannot see specific changes. Tables such as E070, E071, and E71k can only store approximate information, and do not record specific modified non-keyword value information, and the change log of the configuration table is not checked and cannot be searched through the change docment, thank you.

In order to answer this question, we first need to understand which ABAP Function Modules can return information related to transmission requests.

We enter in the transaction code SE37 TRINT, and we can see more than 200one Function Module beginning with this keyword. TR is the abbreviation of Transport Request, and INT can be understood as the abbreviation of Interface, that is, these functions are used to read the interface of the detailed data of the transmission request.

Let's take a look at TRINT_SELECT_REQUESTSthis function. Press F8 directly in SE37 to execute this function, and IV_USERNAME_PATTERNthe default value of the input parameter SY-UNAMEis the current login user.

Among them, the data type of the IS_SELECTION parameter is , if we do not specify any value for this input parameter, after executing the function, we can see the transmission requests TRWBO_SELECTIONowned by the current login user in this system :全部

Let's take a closer look at IS_SELECTIONthe data type of this input parameter TRWBO_SELECTION.

After double-clicking, you can see its detailed type definition. This is a huge structure, which contains many fields. The data types of these fields are defined using keywords, followed by actual database LIKEtables LIKEor database table fields in the ABAP data dictionary, as shown in the figure below E070, E070A, E070Cand so on.

Based on the above clues, we can use the following little trick to put the database table related to the transmission request 一网打尽.

The transaction code SE11 is opened E070, and then click the toolbar button of this hierarchy:

Navigate to E070the ABAP development package where the database table is located E070, which contains all other database tables related to the transmission request besides :

Let's take a brief look at these database tables one by one .

Guess you like

Origin blog.csdn.net/i042416/article/details/131805138