ODSC - Batch to Stream workshop - integration of Apache Spark, Cassandra, Pos...Christina Lin
More Related Content
Similar to Appendix a description of the sap delivered tables used in the hands-on exercises - sap abap- hands-on test projects with business scenarios
Similar to Appendix a description of the sap delivered tables used in the hands-on exercises - sap abap- hands-on test projects with business scenarios (20)
Appendix a description of the sap delivered tables used in the hands-on exercises - sap abap- hands-on test projects with business scenarios
1. 1/5/2016 Appendix A: Description of the SAPDelivered Tables Used in the HandsOn Exercises SAP ABAP: HandsOn Test Projects with Business Scenarios
https://www.safaribooksonline.com/library/view/sapabaphandson/9781430248040/9781430248033_AppA.xhtml 1/7
APPENDIX A
Description of the SAPDelivered Tables Used in the HandsOn
Exercises
SAPDelivered Tables Used in the HandsOn Exercises of the
Book – Categories and Subcategories
This appendix contains descriptions of SAPdelivered tables, which you
will use in the handson exercises of the book. Using an SAPdelivered
table means that (i) some feature of the table is being highlighted in the
book; (ii) the table is being used in the creation of ABAP dictionary
objects such as views or search helps, etc., as part of handson exercise/s;
and (iii) the table is used to access data in handson exercises on ABAP
program/s (SELECT…).
You will relate better to the SAPdelivered table descriptions in this
appendix after studying the two chapters on the ABAP dictionary —
Chapters 2 and 3 .
The phrase “SAP delivered” is being dropped from the subsequent text in
the appendix because it is implicit. The tables described in this appendix
are SAPdelivered tables only.
You will be using the following categories and subcategories of tables:
The “T” series tables. The table names start with the letter “T.” The
“T” series tables contain:
1. Universal nature of data such as country codes, country texts,
currency codes, currency texts, etc. When SAP is installed,
these tables are automatically populated with the universal
data.
2. Configuring data. In a reallife scenario, the configuring
data tables get populated when configurations are performed
by functional consultants. A simple example of configuring a
table is the table T001 storing company codes. When
company codes are created, typically by a finance functional
module consultant, the table T001 gets populated.
The “T” series tables containing universal data or
configuring data are client dependent. That is, the first field
in these tables is of DDIC data type CLNT.
3. There are tables whose names start with the letter “T,”
containing other than universal or configuring information.
These tables are cross client or client independent. An
example of this table subcategory: TRDIRT storing ABAP
source program title.
The master data tables: These tables contain customer, vendor,
material, and other information. Each of the master data
information resides mostly in multiple tables. The customer,
vendor, and material tables contain many fields; you will confine
yourself to using a few essential fields.
The master data tables are client dependent. That is, the first field in
these tables is of DDIC data type CLNT.
The transaction data tables: The transaction data tables contain
business document information. You will use these in most hands
on exercises — in the four business document tables relating to
PREV
Chapter 14: Screen Programming
⏮
NEXT
Index
⏭
ὐ
SAP ABAP: Hands-On Test Projects with Business Scenarios
Recent
Topics
Highlights
Settings
Feedback
Sign Out
Settings
10 days left in your trial. Subscribe.
Feedback
Sign Out
Tutorials
⚙
Enjoy Safari? Subscribe Today