How to view the background transaction code

Post transferred from

Http://scnblogs.techweb.com.cn/frankyue2001/archives/category/sap-abap

1. Overview:

Directly entering the transaction code (t-Code) is the quickest way to enter the background configuration. Some configurations are frequently used, and the transaction code that remembers these configurations will undoubtedly greatly improve our efficiency.

This document describes several common methods.

2. Method 1: view the status bar

For example, to define a material group, we can directly view the transaction code omsf in the status bar of the screen that defines the material group.

This method is the simplest, but only applicable to some background configurations.

Method 2: view technical information

This method is also concise, but it is only valid for some background configurations.

We want to view the transaction code that defines the material type

1) Right-click the leftmost button of "define item type" and select display technical information

The technical information is as follows. The last four bits (oms2) of the Object ID in this example may be the transaction code that defines the material type.

Method 3: Search for the transaction code based on the OSS table

We know that most of the backend configurations are stored in a table. Therefore, we only need to find the table where the data is stored and then reverse query the transaction code based on the table.

Example 1: view the transaction code of the Condition Type configured for the purchase

As shown in, the interface that defines the condition type of procurement, through the above two methods we can not find the corresponding transaction code

On the current page, click the print button to query the data view (data table) corresponding to the current configuration)

In this example, vv_t685a_ma is used.

Note: SAP uses the default naming rules for tables (views). t685a is a table. a v is added for the maintenance view of the table. If you add a View to the view (such as maintaining the view) a v is added.

Run the transaction code se16n to view the table, input the table tstcp, and enter * t685a * in the parameter *.

You can query a series of transaction codes.

This is because these transaction codes operate on t685a. In this example, the condition type is widely used, and the condition type data in different application fields is stored in the table t685a, including sales, procurement, and retail

If you are familiar with the pricing function, you will know that the pricing application of purchasing pricing is m (from which we can also see). Therefore, the transaction code that defines the price type of purchasing is m/06.

Parameter Interpretation

Transaction code se93, view the definition method of transaction code M/06

It can be found that the execution of the transaction code M/06 is equivalent to the execution of the transaction code vkve, the execution parameters are three

(View: v_t685a, purpose V, application m), while skipping the initial Screen

Note: Most of the transaction code configured in the background uses another transaction code (sm30, sm31, and so on) and sets the default value to achieve the purpose of configuration.

This is because the data stored in the background configuration is relatively simple. Technically, the background configuration is actually to put the configuration result into a table (view.

Example 2: Transaction Code determined by the batch search policy

As shown in, in the batch search policy definition, we can see that the configuration is saved in the table t683c

In the same way, we find the transaction code v/C5, which is to call the transaction code sm30

Execute the transaction code sm30 and input the table/view v_t683c. The execution result is the same as the execution of the transaction code v/C5.

Method 4:

If you still cannot find it, refer to some posts

Http://blogold.chinaunix.net/u1/40527/showart.php? Id = 1071497

Http://scnblogs.techweb.com.cn/sapkevin/archives/1662.html

Summary:

There are still some methods to find the transaction code configured in the background. This article only lists the methods that are easier to query for function consultants, the key point is that we need to understand the definition method of the transaction code and its relationship with the table.

The configuration "batch confirmation" described above is used as an example. If the configuration is only required for testing, we can also directly enter the maintenance view v_t683c through sm30. If the configuration needs to be used by the production machine, further tests are required.

In actual projects, there may be thousands or more configuration records of a certain type. In this case, we can create a batch import program using the transaction Code such as sm30, A modification request can also be generated and transmitted to the production machine.