SAP相关数据库表

第1章SAP相关数据库表

1.1 Tcode代码表

Tstc

1.2预算相关表

1.3作业相关表

1.4预留

RESB是物料类

1.5发票计划

涉及到的表：FPLT, PFLA

根据项目取得对应开票金额和开票计划的逻辑:

2.1.根据项目编号取得WBS的出具（发票）计划编号，取数逻辑：select

prPS-FPLNR where prps- FAKKZ = ‘ X' and prps-psphi =项目定义号。

22根据2.1中取得发票计划编号取得合同金额：select fpla-BASISWRT where fpla-FPLNR =上步骤中取得的发票号

2.3.根据发票计划编号取得具体的发票记录，取数逻辑：select fplt-afdat、fplt-fakwr、fplt- TETXT from fplt where fplt-FPLNR IN （上步中取得的发票计划号）。

根据fplt- TETXT取得对应的描述，取数逻辑：select TVTBT- TEBEZ from

Tvtbt where tvtbt- TETBE = fplt- TETXT。

1.6里程碑信息

在WBS上创建的里程碑，只可在WBS之间移动在作业上创建的里程碑，只可在作业之间移动。

相关表：MLST-重大事件，MLTX-重大事件描述

1.7数据库列表

PP

SAP数据库(数据表)相关知识

(2010-11-05 11:28:52)

转载▼

标分类：ABAP-Basic 签：

杂

谈

Delivery class

The delivery class controls the transport of table data when installing or upgrading, in a clie nt copy and whe n tran sport ing betwee n customer systems. The delivery class is a lso used in the exte nded table maintenan ce.

There are the follow ing delivery classes: A: Applicati on table (master and tran sacti on data).

C: Customer table, data is maintained by the customer only.

L: Table for stori ng temporary data.

G: Customer table, SAP may insert new data records, but may not overwrite or delete existi ng data records.

E: System table with its own n amespaces for customer en tries. The customer n amespa ce must be defined in table TRESC.

S: System table, data cha nges have the same status as program cha nges.

W: System table (e.g. table of the development environment) whose data is transporte d with its own tran sport objects (e.g. R3TR PROGR3TR TABL, etc.). Behavior duri ng clie nt copy

Only the data of clie nt-specific tables is copied.

Classes C, GE, S: The data records of the table are copied to the target clie nt. Classes W, L: The data records of the table are not copied to the target clie nt. Class A: Data records are on ly copied to the target clie nt if explicitly requested (para meter option). Normally it does not make sense to transport such data, but is supporte d to permit you to copy an en tire clie nt en vir onment. Behavior duri ng in stallati on, upgrade and Ian guage import

The behavior differs here for client-specific and cross-client tables.

Clie nt-specific tables

Classes A and C: Data is only imported into client 000. Existing data records are over writte n.

Classes E, S and W: Data is imported into all clients. Existing data records are overwr itte n.

Class G: Existing data records are overwritten in client 000. In all other clients, new d ata records are in serted, but existi ng data records are not overwritte n.

Class L: No data is imported.

Cross-clie nt tables

Classes A, L and C: No data is imported.

Classes E, S, and W: Data is imported. Exisitng data records with the same key are ov erwritte n.

Classe G: Data records that do not exist are in serted, but existi ng data records are not overwrite n.

Behavior duri ng tran sport betwee n customer systems