在sap开发的过程中，经常需要自定义数据表，对于简单的数据表，我们可以通过sap的表维护工具生成维护代码，并建立自定义的TCODE来维护其数据。具体步骤如下：

一、建立自定义表（TCODE ：SE11）
1 在“Delivery and Maintenance”Tab屏幕设置“Data Browser/Table view Maint.”属性为“允许通过标准表格维护工具维护”
2 设计表格字段
3 设置表格技术设置，菜单：转到－》技术设置
4 保存激活。

二、生成维护代码
生成维护代码代码有两个途径：
1、se11界面的菜单：实用程序－》Table Maintenance Generator其实这里就是调用SE54
2、通过TCODE： SE54

三、建立自定义CODE（TCODE：SE93）
有三种方法来建立自己的TCODE来维护自定义表；
1 通过SM30维护
进入TCODE：SE93建立新TCODE，tcode类型选择为：“Transaction with parameters（parameter transaction）”；事务栏输入“SM30”；选中“跳过起始屏幕”；选中“Inherit GUI attribute”；输入默认字段：VIEWNAME = '自定义的表名' 和UPDATE ＝ 'X'；保存激活即可；
2 通过RS_TABLE_LIST_CREATE函数建立新程序来建立TCODE
新程序代码如下

report  zjwec026  .

  call function 'RS_TABLE_LIST_CREATE'
         exporting
              action     = 'ANLE'
              table_name = 'ZJW_CC_GZJSQ'
              generation_forced = ' '.
3通过View_Maintenance_Call 函数建立新程序来建立TCODE，代码可以参见SAP的标准程序RFT042D_CALL
代码如下
report  rft042d_call.

call function 'VIEW_MAINTENANCE_CALL'
     exporting
          action         = 'S'
          view_name      = 'V_T042D'.

一 Profiles路径
SAP profiles are stored in a special file directory. This directory can be made accessible from all hosts depending on current needs:
UNIX systems : /usr/sap/<SID>/SYS/profile
Windows NT systems: \usr\<SID>\sys\profile\
( <SID> = SAP system name and <SAPGLOBALHOST> = name of the NT machine on which the global profile directory is physically located)

二 Profiles命名规则
In R/3 Releases 2.1x / 2.2x, the profiles were generated with the names:
START_<instancename>and <SID>_<instancename>.
From Release 3.0A, the profiles are generated with the names: START_<instancename>_<hostname>and <SID>_<instancename>_<hostname>.
The 'startsap'script first looks for profiles that end with_<hostname>. If these profiles do not exist, the names from the Releases 2.1x / 2.2x are used.

三 Profiles类型
3.1 Default Profiles Definition

If you want to assign the same parameter value for all application servers (such as the name of the database host, or the host on which the message server is running), enter it in the default profile. In general, you can list any parameter you like here.

SAP recommends that you use the following values:

You cannot choose a name for the default profile. It is always called DEFAULT.PFL. The default profile, like all other profiles, is located in the global profile directory of the SAP System. For example, under UNIX it is located in the directory/usr/sap/<SID>/SYS/profile(<SID>= SAP System name). There is always one active default profile.

SAPDBHOST = hs0011

DIR_ORAHOME = /oracle/BIN

rdisp/mshost = hs0311

rdisp/vbname = hs0311_BIN_53

rdisp/enqname = hs0311_BIN_53

rdisp/btcname = hs0002_BIN_53

rdisp/sna_gateway = is0001

rdisp/sna_gw_service = sapgw00

3.2 Start Profiles  

When you start an SAP instance on a host, the start profile defines which SAP services are started (message server, dialog, gateway or enqueue process. for example). The startsap program is responsible for starting these service processes,

The processes that can be started include:

• Application server

• Message server

• SNA Gateway

• System log send demon

• System log receive demon

Apart from the general profile parameters, such as the name of the SAP System (SAPSYSTEMNAME), instance number (SAPSYSTEM) and name of the SAP instance (INSTANCE_NAME), the only parameter names that are permitted in a start profile are: 

Execute_xx (xx = 00-99) : To start operating system commands, which prepare the SAP System start. For example, you can use this parameter to start the SAP-related database or to set up links to executables on UNIX platforms.

Start_Program_xx (xx = 00-99) : To start an SAP instance, for example, on an application server.
Stop_Program_xx (xx = 00-99) : To start an operating system command or SAP program after the SAP instance was stopped. For example, the halting or removal of shared memory areas that were used by the SAP System.
The number xx defines the execution sequence. The programs specified in Execute_ parameters are executed before the programs listed in the Start_Program parameters. After the SAP instance has been stopped, the programs specified in the Stop_Program parameters are started. Here is an example of a start profile used to start a message server, an application server and an SNA gateway:
#.***************************************************************
#.* Start profile START_DVEBMG47
#.*
#.* Version = 000003
#.* last changed by = WATT
#.* last changed on = 21.03.1995, 15:05:19
#.***************************************************************
SAPSYSTEMNAME = K11
INSTANCE_NAME = DVEBMG47
#----------------------------------------------------------------
# start message server
#----------------------------------------------------------------
_MS = ms.sapK11_DVEBMG47
Execute_01 = local ln -s -f $(DIR_EXECUTABLE)/msg_server $(_MS)
Start_Program_01 = local $(_MS) pf=$(DIR_PROFILE)/K11_DVEBMG47
#----------------------------------------------------------------
# start application server
#----------------------------------------------------------------
_DW = dw.sapK11_DVEBMG47
Execute_02 = local ln -s -f $(DIR_EXECUTABLE)/disp+work $(_DW)
Start_Program_02 = local $(_DW) pf=$(DIR_PROFILE)/K11_DVEBMG47
#----------------------------------------------------------------
# start SNA-Gateway
#----------------------------------------------------------------

 3.3 Instance Profiles 
Instance profiles provide an application server with additional configuration parameters to complement the settings values from the default profile. Typically, these parameter settings adapt the instance according to the desired resources. They also define the available instance resources (main memory, shared memory, roll memory and so on), and how to allocate memory to the SAP application buffers.
To start application servers on several computers using identical parameter settings, you can use a single instance profile. It is generally not necessary for each application server to have its own instance profile. Instance profiles are also called system profiles.

Below is a typical instance profile:
#.*************************************************
#.* Instance profile BIN_DVEBMG53 *
#.* Version = 000005 *
#.* Generated by user = BLOCHING *
#.* Date generated = 04.08.1995, 11:10:35 *
#.*************************************************
INSTANCE_NAME = DVEBMG53
SAPSYSTEM = 53
SAPSYSTEMNAME = BIN
abap/buffersize = 40000
abap/programs = 600
ipc/shm_psize_10 = 15000000
ipc/shm_psize_14 = 0
ipc/shm_psize_17 = 0
ipc/shm_psize_18 = 0
ipc/shm_psize_19 = 0
ipc/shm_psize_40 = 17000000
rdisp/PG_MAXFS = 4096
rdisp/PG_SHM = 1000
rdisp/ROLL_MAXFS = 16384
rdisp/ROLL_SHM = 200
rdisp/btctime = 60
rdisp/wp_no_dia = 5
rdisp/wp_no_enq = 1
rdisp/wp_no_vb = 1
rdisp/wp_no_vb2 = 1