Find data in your SAP system and know which tables do what

updated Oct 8, 2012 9:28 am | 148,059 views

Contents

[edit]

[Hide TOC] 1 Introduction 2 Steps 3 Examples 4 Conclusion 4.1 Links

Introduction
Many people ask where they can find data in their SAP system. Because SAP is so often highly customised, the best answer is "Ask your SAP system itself" Which leads on to the question "How do I do that?"
[edit]

Steps
If you do not know the transaction code in which the data is used: then use the Data Dictionary tables, in particular, DD02L and DD02T. Accounts Payable. See examples below. If you do know any transaction in which (related) data is used: 1) start the transaction 2) position the cursor on the field you want to have info about 3) press F1, then F9 4) now you see the technical information of the data element, such as table name and field name. 5) if the table mentioned is what you're looking for, you're done. It is also possible that the data element is in a structure and not in a table. Now you can either analyze the structure via trx SE11, or you can double click on the 'data element' field. In the next screen, use the 'Where used' button to find the tables in which this data element is used. Additional tip: if you have found the table name, you can use trx SE36 or SLDB or ALDD ( also u can click on the help u will get information about logical data base tables)to see the relationships of this table to other tables. You can use these relationships when defining queries, designing custom ABAP programs, etc. If you're lucky, one or more standard SAP logical database exist which contain the table you found in the previous steps. Proceed as follows: 1) start trx SE36 2) use the search help for the logical database name 3) enter the name of the table in the search help 4) press enter and, if you're lucky, you'll see a list of logical databases. Select one, press enter, select the radio button 'Structure' and press the view button. Now you'll see how this table is related to other tables. Another method is to use the SQL tracing that comes with SAP. you can activate this in a secondary session, preferably just before you launch a step in a transaction (like saving, or pushing a button, or before you do a F4 help function). You then immediately switch the tracing back off. If you then analyze the trace, you should find the embedded SQL transactions that access the different tables. This works fine for example if you want to know in which table the configuration is stored. you can use the name of the table to launch SM30 or SM31 to find the SPRO activity related to the specific table.
[edit]

Examples
The following is a (theorectically) complete ABAP dic list.

DD0102V | Generated table for view DD0102V | DD01D | Dynpro fields for domain | DD01L | Domains | DD01LV | Generated table for view DD01LV | DD01T | R/3 DD: domain texts | DD01TV | Versioning: foreign languages for domains | DD01V | Generated table for view DD01V | DD01VD | Version display: Domain | DD01VV | Generated table for view DD01VV | DD01V_OLD | DD01V with old names | DD02ALL | Table Parameters for ALLBASE | DD02D | Screen Fields for Table | DD02DB2 | DB2/390: Table Parameters | DD02DB6 | Table Parameters for DB2 Version 2 | DD02INF | Table Parameters for INFORMIX, Version 6 | DD02L | SAP tables | DD02MSS | Table Parameters for Microsoft SQL Server | DD02ORA | Table parameters for ORACLE, version 6 | DD02SYB | Storage Parameters for Tables in SYBASE | DD02T | R/3 DD: SAP table texts | DD02TV | Versioning: foreign languages for tables | DD02V | Generated table for view DD02V | DD02VD | Version display: table header | DD02VV | Generated table for view DD02VV | DD02V_OLD | DD02V with old names |

DD03D | Dynpro fields for table fields | DD03K | Generated table for view DD03K | DD03L | Table Fields | DD03L_F | BAPI field names for update | DD03M | Generated table for view DD03M | DD03MI | Index structure for view DD03M | DD03N | Generated table for view DD03N | DD03P | Structure | DD03P_D | Dictionary Maintenance: Attributes of Structure Fields | DD03T | DD: Texts for fields (language dependent) | DD03TV | Versioning: foreign languages for fields | DD03V | Table fields view | DD03VT | Generated Table for View DD03VT | DD03VV | Generated Table for View DD03VV | DD04D | Dynpro fields for Data Element | DD04L | Data elements | DD04T | R/3 DD: Data element texts | DD04TV | Versioning: foreign languages for data elements | DD04V | Generated Table for View DD04V | DD04VD | Version display: Data element | DD04VV | Generated table for view DD04VV | DD04VVL | Generated table for view DD04VVL | DD04VVT | Generated table for view DD04VVT | DD05M | Interface Structure for DD_TBFK_GET | DD05P | Generated Table for the View DD05P |

DD05Q | Generated Table for the View DD05Q | DD05S | Foreign key fields | DD05V | View on foreign key fields | DD05VD | Version display: Foreign key fields | DD06D | Screen fields for SQL table | DD06L | Pool/cluster structures | DD06T | R/3 DD: texts on SQL tables | DD06TV | Versioning: foreign languages for SQL tables | DD06V | Generated table for view DD06V | DD06VD | Version display: SQL table | DD06VV | Generated table for view DD06VV | DD07D | Screen fields for domain values | DD07L | R/3 DD: values for the domains | DD07T | DD: Texts for Domain Fixed Values (Language-Dependent) | DD07TV | Versioning: foreign languages for domain fixed values | DD07V | Generated Table for View DD07V | DD07VD | Version display: Domain fixed values | DD07VT | DD: Temp. Replacement Structure for VIEW DD07TV | DD08D | Screen Fields for Foreign Keys | DD08L | R/3 DD: relationship definitions | DD08T | Texts on the relationship definitions | DD08TV | Texts on the relationship definitions | DD08V | Generated table for view DD08V | DD08VD | Version display: foreign key | DD08VV | Generated table for view DD08VV |

DD08VVT | Generated table for view DD08VVT | DD092526V | Generated table for view DD092526V | DD09C | ABAP/4: Sytem-dependent attributes of tech. settings | DD09L | DD: Technical settings of tables | DD09V | Interface: Technical Settings Table/View | DD09VD | Version display: Technical settings | DD09VV | Generated table for View DD09VV | DD09VVT | Generated table for view DD09VVT | DD10L | Lock table for DD activation | DD12D | Screen fields for index maintenance | DD12DB2 | DB2/390: Index Parameters | DD12DB6 | Index Parameters for DB2 Universal Database Version 2 | DD12INF | Index parameter for INFORMIX | DD12L | R/3 S_SECINDEX: secondary indexes, header; | DD12MSS | Index Parameters for MS SQL Server | DD12ORA | Index Parameters for ORACLE | DD12SYB | Index Parameters for SYBASE System_10 | DD12T | Text Table for DD12L (Short Descriptions of Sec. Indexes) | DD12TV | Versioning: foreign languages for secondary indexes | DD12V | Generated Table for View DD12V | DD12VD | Version display: index | DD12VVT | ABAP/4 Repository Information System: Index work structure | DD14S | R/3 DD: components of SAP objects | DD14V | R/3 DD: view on SAP object structure | DD15L | R/3 DD: SAP objects |

DD15T | R/3 DD: texts on SAP objects | DD15V | R/3 DD: view on SAP objects | DD16D | Screen fields for SQL table fields | DD16S | R/3 DD: SQL table fields | DD16V | Generated table for view DD16V | DD16VD | Version display: Fields of SQL tables | DD17S | R/3 S_SECINDEX: secondary indexes, fields | DD17V | Secondary index fields with language key | DD20L | Matchcode objects | DD20T | AS400-T_MCOBJECT: MC Object Texts | DD20TV | AS400-T_MCOBJECT: MC Object Texts | DD20V | Generated table for DD20V view | DD20VD | Version display: matchcode objects | DD20VVT | Generated table for view DD20VVT | DD21S | S-MCIDTABLE: Tables for a MC ID | DD21V | V-MCIDTABLE: View of Tables for a MC ID | DD21V_VAR1 | Special View on DD21V Tailored to Matchcode ID Generation | DD22V | Generated table for view DD22V | DD22VD | Version display: Lock object header | DD23H | Generated table for view DD23H | DD23L | Matchcode ID | DD23LS | Generated table for View DD23LS | DD23T | AS400_L-MCID: Matchcode ID Texts | DD23TV | Versioning: foreign languages for matchcode IDs | DD23V | Generated table for view DD23V |

DD23VD | Matchcode ID | DD23VVT | Generated table for view DD23VVT | DD24A | Generated table for view DD24A | DD24H | Help System View on Fields of a MC ID | DD24S | Fields of a matchcode ID | DD24V | S-MCIDFIELD: View of MC ID Fields | DD2526V | Generated table for view DD2526V | DD25D | Screen fields for view | DD25L | Aggregate Header (Views, MC Objects, Lock Objects) | DD25LS | Generated table for view DD25LS | DD25T | Short Texts for Views and Lock Objects | DD25TV | Versioning: foreign languages for views and lock objects | DD25V | Generated table for view DD25V | DD25VD | Version display: View header | DD25VV | Generated table for view DD25VV | DD25VVT | Generated table for view DD25VVT | DD25Z | Assignment of superview to subview - no longer required - | DD26D | Screen fields for lock object maintenance | DD26E | Interface Structure for Base Tables of a Lock Object | DD26EVD | Version display: base tables of a lock object | DD26I | Generated table for view DD26I | DD26S | Base tables and foreign key relationships for a view | DD26V | V-VIEWTABLE: View of Base Tables of a View | DD26VD | Version display: Base tables | DD27D | Screen fields for view fields |

DD27I | Generated table for view DD27I | DD27M | Generated table for view DD27M | DD27P | View of Fields in an SAP Table View | DD27S | Fields in an Aggregate (View, MC Object, Lock Object) | DD27SV | Generated table for view DD27SV | DD27V | V-VIEWFIELD: View of Fields in an SAP View | DD27VD | Version display: View fields, lock arguments, matchcode fld. | DD27VV | Generated table for view DD27VV | DD27VVT | Generated table for view DD27VVT | DD27VVTSTR | Repository Infosystem: Structure via DD27VVT: View fields | DD28J | Internal structure for joins of views | DD28JVD | Version display: Joins of views | DD28S | Lines of a selection condition | DD28V | View on a Selection Condition | DD28VD | Version display: Selection conditions | DD29L | Selection Condition for Views and MC IDs | DD29T | AS400_L-SELCOND: Selection Condition Texts | DD29V | V-SELCOND: View on Header for a Selection Condition | DD30L | Search helps | DD30T | Search help texts | DD30TV | Versioning: foreign languages for search helps | DD30V | Generated table for view DD30V | DD30VD | Version Display: General Attributes of Search Helps | DD30VV | Generated table for view DD30VV | DD31D | Search help inclusions with texts of included |

DD31S | Assignment of search helps to collective search helps | DD31V | Assignment of search helps to collective search helps | DD32P | Interface structure for search help parameters | DD32S | Search Help Parameter | DD32V | Search help fields | DD32VD | Search help fields | DD33S | Assignment of search help fields | DD33V | Assignment of search help parameters for srch help inclusion | DD35L | Search help attachments to structures: Headers | DD35V | Assignment of structure fields and search helps: Headers | DD35VD | Version display: search help attachm. to structures: header | DD35VV | Generated table for view DD35VV | DD36M | Interface structure for field assignments table-search help | DD36Q | Generated table for view DD36Q | DD36S | Parameter-field assignments for search help attachment | DD36V | Assignment of structure fields and search helps: Fields | DD36VD | Version display: parameter-field assignm. for s.h. attachm. | DD40D | Screen Fields for Table Types | DD40L | Table types (internal tables defined in DD) | DD40T | Text on table types | DD40TV | Versioning: foreign languages for table types | DD40V | DD: Interface structure for table types | DD40VD | Version display: table types | DD40VV | Generated table for view DD40VV | DD41V | Generated table for view DD41V |

DD42S | Key fields for table types (internal tab. defined in DD) | DD42V | DD: Interface structure for table type key fields (TTKF) | DD42VD | Version display: table type key fields (TTKF) | DD42V_EXT | DD: Key Field of a Table Incl. Further Information | DD50D | Screen Fields for Type Groups | DD51D | Screen Fields for Lock Objects (Same Fields: DD25D Views) | DD52D | Interface Structure for Base Tables of a Lock Object | DD53D | Screen Fields for Lock Object Fields | DD90L | Header Information for External Index | DD90T | R/3-DD: Text for External Index | DD90V | Generated Table for View DD90V | DD91S | DocID Key Definition of External Index | DD91V | DocID Key Definition of External Index | DD92S | Mapping of R/3 Data on External Index | DD92V | Mapping of R/3 Data on External Index | DD93S | Attribute of an External Index | DD93V | Attribute of an External Index | DD94S | Languages of an Index Category | DD94V | Languages of an Index Category | DD96S | Synchronization Tables | DD96V | Synchronization Tables of an External Index | DD97S | Statements for Trigger and Stored Procedures | DDACL | Exclusion times for ABAP/4 Dictionary actions | DDACTIONS | DD: Structure for display ACTION -> text | DDACTRES | DD: Activation result incl. dependent propagation |

DDALIAS | DD: Second name for accessing tables | DDALTER | Information about Reasons for ALTER TABLE | DDAPPSRC | SE11: Append origin of for. keys and src. help attachments | DDART | DD: Data Class in Technical Settings | DDATCHK | Field structure for screen 100 RUTATCHK | DDAUTHCTRL | Control structure for authorization checks | DDAUTHTAB | ABAP/4: database actions and flag if this is permitted | DDBOOK | Output control table manual | DDBOOL | Reference Structure for Interfaces | DDBTCMPTIT | Column information for comparison of repeat groups | DDBT_CFLD | Description of a non-elementary component of a structure | DDBT_DATA | Information about a component of a complex data object | DDBT_DATD | Type for packing complex data | DDBT_FDDES | Type and position of contents of a field | DDBT_FLD | Information about an elementary component | DDBT_STDEF | Description of a structured type | DDBUF | DD: For transferring the new buffering parameters | DDBYTE | DD: X-fields for each bit of a byte | DDB_AST | Table Structure for Author. Segm. Trigger | DDB_AW | Configuration Transac. Data: Fact for Simple Characteristic | DDB_AZW | Configuration Transaction Data: Fact for Restrictable Char. | DDB_C00 | Transaction Data: DDDB_HAS_INST | DDB_C01 | Transaction Data: DDDB_HAS_VAL | DDB_C02 | DDB Change Messages (Configuration) | DDB_C03 | Configuration Transac. Data: General Value Set |

DDB_C04 | Value Structure for Reading Characteristic Values from DDB | DDB_C05 | Presentation Messages for DDB Instances | DDB_C06 | Describes a characteristic value, as in priority tables | DDB_C07 | Price Factors for Variant Conditions | DDB_ITP | DDB: General Object Type | DDB_PO | Part-of Structure in Configuration (DDB) | DDB_TO | DDB Configuration: TYPE_OF-Fakt | DDCACHE | DD: Control String for Read Routines | DDCCOND | Conditions for Status Switch during Conversion | DDCCURRSTA | DD: Conversion, statistics, intermediate values | DDCDIM | DD: Conversion, number of table lines | DDCHKMESS | ABAP/4 Dict.: contains messages for NA checks | DDCHK_CNT | DD: Mass Check Statistics Counter | DDCHK_CTRL | DD: Parameter for (Parallel) Mass Check Program | DDCLASSES | DD: Structure for mapping CLASS -> text | DDCLAUSE | SQL clause | DDCLIENT | Structure for Clients | DDCNODE | DD: Nodes in Status Graphs of Conversion | DDCNV | Information why Conversion | DDCNVBODY | DD: Definition of conversion steps - local attribute | DDCNVCTRL | DD: Structure for parameters of ICNV | DDCNVDEFS | DD: Definition of Conversion Steps | DDCNVEXIT | DD: External conversion methods | DDCNVKEY | Definition of Conversion Scenario - Key | DDCNVOPT | Stsructure for Conversion Options |

DDCNVREF | DD: Reference structure for conversion requirements | DDCNVRESS | DD: Structure for results of FB DD_ICNV_UPGRADE | DDCNVSTAT | DD: Statistical Data for Conversion | DDCNVTABL | DD: Contains incr. conv. tables depend. on release/component | DDCNVTIMES | DD: Exclusion times for conversion | DDCNVUPGR | DD: Control structure for ICNV steps during upgrade | DDCNVUSR | DD: Exception table of converter | DDCOMPARE | Return from generic comparison tool: RS_VERS_COMPARE_TAB | DDCOMTOTAB | Comment on the Table Rows | DDCON | Condition for IN operator | DDCONH | Storage Parameter (condition) | DDCPRO | DD: Conversion projects | DDCPROGRES | DD: Conversion, statistics, intermediate values | DDCPROT | DD: Text on conversion projects | DDCPROTAB | DD: Table for conversion projects | DDCPYSTAT | DD: Statistics data for table copy | DDCQUEUE | DD: Queue for CNV Operations | DDCSCANSTA | DD: Conversion, scan history | DDCSTA | DD: Conversion, number of table lines | DDCSTAT | DD: Statistics table for conversions | DDCSTAT_I | DD: Statistics Data for Conversions | DDCSTAT_K | DD: Statistics Data for Conversions - Key Part | DDCSTAT_T | DD: Statistics Data for Conversions | DDCT_TYPE | Type Information for LOW and High of a Range Type | DDCURSOR | DD: Reference structure for cursor area |

DDCVERTIC | Link of Status Graph of Conversion Program | DDDBOPERA | Virtual table of outstanding DB operations | DDDBOPS | Virtual table of outstanding DB operations | DDDBSPACE | Structure for DBSpaces/Tablespaces | DDDBUTMREQ | Interface for mass processing requests | DDDBUTREFS | DD: Database utility reference fields | DDDECIDE | Information about Structure Changes to DB Objects | DDDEPDESCR | Internal Description of a Dependent Object | DDDEPRES | DD: result of handling of dependent objects | DDDEPTAB | DD: Dependencies Sorted By Dependent Objects | DDDOACTRES | DD: Status of domains (activation result) | DDDOMSTATE | DD: Status of domains | DDDOSTATE | Status of Objects | DDDTRENUPG | DD: Table for Renaming Data Elements During Upgrade | DDDTSTATE | DD: Status of Data Elements | DDENA | Lock argument fields | DDENQS | Lock object structure for Dictionary objects (inc. index) | DDENQ_LIKE | Ref. Fields for Parameters of the ENQUEUE Function Module | DDERR | R/3 DDIC: Error Code From Modules | DDERR_O | Return code structure in consistency layer of the DD | DDEXTIDXS2 | DocID Key Definition of External Index | DDEXTIDXS3 | Mapping of R/3 Data on External Index | DDEXTIDXS4 | Attribute of an External Index | DDEXTIDXS5 | Synchronization Tables with Stored Proc. for External Index | DDF4ATTRVA | Document Attribute with Value for Indexing/De-indexing |

DDF4DBTRIG | Tables and Triggers | DDF4EXIXS3 | Mapping of R/3 Data on External Index | DDF4IDCTRL | Control Structure for Data Selection for an External Index | DDF4IDPROT | Structure for Log Table for Updating External Indexes | DDF4IDXCON | Document Contents for External Index | DDF4KEYTAB | Key for Selection Module / Search Engines | DDF4LBBUF1 | List Box Buffer: GUID and Time Stamp for a Table | DDF4PSALLS | Structure for General Personalization of Search Helps | DDF4PSINDX | Contains Information for Personalizing the F4 Help | DDF4SEKEYS | Structure for Document Key of Log Table | DDF4SERFC | RFC Destinations of a Search Server Relation | DDF4SYNCIV | Synchronization Interval for External Index | DDF4TRACE | INDX Structure for Holding F4 Trace (List Box) | DDF4TRADAT | Data to be Stored in DDF4TRACE | DDF4TRIGTR | Structure for Tree Representation of DB Trigger | DDFIELD | DB-relevant description of DD table fields | DDFIXVALUE | Description of a Fixed Value | DDFKEYRC | DD: Message numbers for foreign key violations | DDFLDNAM | Name of a DD table field | DDFLDSPATH | DD: field information and field name with entire path | DDFLG1 | Flag byte 1 of nametab for field attributes | DDFLG2 | Flag byte 2 in nametab for field attributes | DDFLG3 | Flag Byte 3 of Nametab for Field Attributes | DDFLG4 | Flag byte 4 of nametab for field attributes? | DDFLGBYTE | Table attributes in nametab header |

DDFTX | Run-time object with Screen Painter texts | DDFTYP | DD: Structure to test fields without data elements | DDGENTAB | DD: Structure of Gentab (Mass Activation Program) | DDGR_NAME | DD: Names of DD objects for graphic algorithms | DDGR_OBJ | DD: Object lists for graphic algorithms | DDGR_REL | DD: Relations list for graphic algorithms | DDGR_RELIX | DD: Relation over object index for graphic algorithms | DDHDFLG3 | DD: Header flag 3 expanded | DDHDFLG4 | DD: Header flag 4 expanded | DDHDFLG5 | DD: Header flag 5 expanded | DDHDFLG6 | DD: Header flag 6 expanded | DDHELPSTRT | Table Fields for Reference | DDICNVCHE | DD: Condition variables for incremental conversion | DDICNVCTRL | Control String for Transaction ICNV | DDICNVDAYS | DD: Days of Week | DDICNVDIST | Distribution of data records of base tables | DDICNVENQ | DD: Structure to lock the ICNV | DDICNVLST | Contains information on converter exits | DDICNVMON | DD: Structure for ICNV monitor | DDICNVPREP | DD: Control Structure for ICNV in Upgrade | DDICNVPROS | Process information for incremental conversion | DDICNVREF | Reference structure for interfaces of ICNV | DDICNVRES | DD: Results of ICNV Checks in Upgrade | DDICNVUPGR | DD: ICNV Control for Upgrade Phase PREPARE | DDIDELCHK | Control String for Check Whether Fields May Be Deleted |

DDIKEYCHK | Control String for Checking the Key | DDILTYCHK | Control String for Checking Long Fields | DDINDEX | Information for indexes | DDINDXACT | Information what kind of Index is Required in DB | DDINFO | DD: Info Part of the Navigation Table for DD Objects | DDINNUCHK | Control String for Checking NOT NULL Flags | DDIPCLCHK | Control String for Table Type Test with Pool/Cluster | DDIPOOCHK | Control String for Additional Tests for Pooled Table | DDIREFCHK | Control String for Checking Reference Fields | DDIREL | Relation Source and Target Tables in the ICNV | DDISAACHK | Control String for Checking Fields for SAA Standard | DDISAHCHK | Control String for Checking Header for SAA Standard | DDITANCHK | Control String for Table Name Tests (Except SAA) | DDITEHCHK | Control String for Checking DD02L <-> DD09L/Header Checks | DDITESCHK | Control String for Checking DD02L <-> DD09L/Field Checks | DDIVAHCHK | Control String for Checking the Fixed Values (Header) | DDIVALCHK | Control String for Checking the Fixed Values (Fields) | DDKONTEXT | Context of DD Maintenance | DDLBBUFTST | Test: Recognize Access to Buffered Tables | DDLCH | Logical Channel Info from the R/3 Repos. - Standard Version | DDLOAD | DD: Reference structure for loading/unloading tables | DDLOADD | R3load-data table for migration | DDLOADH | R3load-header table for migration | DDLOGDEF | DD: Formal definition of log and trace output | DDLREF | Log Reference in Dictionary - Standard Output |

DDMASS | DD: Structure for mass activator parameters | DDMASSAC | DD: Control operations for DD objects during mass activation | DDMASSCTRL | DD: Control Input Par. for DD_MASS_ACT_PARALLEL | DDMASSTST | DD: Control Structure for Test Mode Mass Activation Program | DDMATASKCT | DD: Control Parameter for Mass Act. for Each Task | DDMESS | Message in non-expanded form | DDMSACTRC | DD: Return Information about Activation | DDMSCHK | Structure for screen variables of mass checks | DDMSG | DD: Structure for Messages | DDMUTEX | DD: Table for implementing reciprocal exclusions | DDNAMECONF | Return structure for function module DD_NAME_CONFLICT_AREA | DDNAMES | Structure for Dictionary Checks | DDNAMETAB | Structure for Display Nametab | DDNMB | DD: Data records per extent (minimum/maximum number) | DDNTFLAG | Structure for Explaining Nametab Flags | DDNTHEADER | Structure for Nametab Header | DDNTHIST | DD: history nametabs in time interval | DDNTSACT | DD: Possible actions on nametab byte | DDNTTHISTS | Nametab history: table information on DB table DDNTT_HIST | DDNUMFVAL | DD: Structure for numeric fixed values | DDOBJ | DD: Name of an ABAP Dictionary object | DDOBJCLASS | Classification of ABAP Dictionary objects | DDOBJCOST | DD: Relative costs per DD object type | DDOBJDIR | DD: Structure for Objects in Mass Checks | DDOBJKEY | DD: Key of DD Objects (Type Name) |

DDOBJPOS | DD: Position of an object | DDOBJTEXT | Dictionary Objects: Texts | DDOCC | Occurrence of Table/Field in Aggregates or as Reference | DDOP | DD: Specification of DDL Operations | DDOPADMIN | DD: Management Information on an DD/DB Operation | DDOPER | Lock arguments for DD processes | DDOPKEY | DD: Key of a DD/DB Operation | DDOPOBJ | DD: Object on which a DD/DB Operation is Performed | DDOPTIME | DD: Time of a DD/DB Operation | DDPAMSCTRL | DD: Controls Parallel Handling during Mass Activation | DDPAR | R/3 Dict: table of internal parameters | DDPARLIST | Control structure for outputting parameter values | DDPART | DD: Partitioned form of TBATG | DDPARTKEY | DD: Global attributes of table DDPART | DDPATH | DD: Definition of access paths | DDPCH | Physical Channel Info from the R3/Repos. - Standard Version | DDPOPUPT2F | DD: Description of a dialog box with 2 columns and 1 flag | DDPRH | R/3 DD: Log header | DDPRH_ALV | Structure for DDPRH for Display with ALV Grid | DDPRID | DD: Representation of a list of log IDs | DDPRLOCK | DD: Lock granularity for standard output | DDPRMASQUE | DD: Mask for overlaying a log line | DDPROF | DD: Settings for DDIC programs | DDPROPVAL | DD: Attribute value pairs | DDPROTOBJ | DD: Object Table for Log Entries in DDPRH, DDPRS |

DDPRS | R/3 DD: log lines | DDPRT | Structure of ABAP/4 Dictionary logs | DDPRTENQ | Control string: print lock objects | DDPRTGEN | Interface: general print options | DDPRTLIST | Input list for printing DD objects | DDPRTMC | Control string: print option for matchcodes | DDPRTPARA | Parameter for print editing | DDPRTSHLP | Control string: print options for search helps | DDPRTTAB | Control string: print options for tables | DDPRTUVAR | User settings for printing DD objects | DDPRTVIEW | Control string: print options for views | DDPRTXT | R/3 DD: Log texts | DDPRT_FRM | Format Definitions for Printing Dictionary Objects | DDPRT_I | Interface for ABAP/4 Dictionary logger | DDRANGE | Reference structure for ranges in the ABAP Dictionary | DDREF | Table/Field and Associated Reference Table/Field | DDREFSTRUC | DD: General Reference Structure in ABAP Dictionary | DDREFTAB | ABAP/4 D: Dependencies Sorted by Referenced Objects | DDRELSTRUC | DD: Relationships between DD objects | DDRELTAB | DD Dict.: structure for relations | DDSCR | DD Interface: View of Field Attributes in the Nametab | DDSECHKKEY | Structure for Comparing Definition of Log Table | DDSECHKPRT | Log Display Admin. Search Index | DDSERVERIF | DD: Info for Application Server for Parallel Processing | DDSERVPERF | DD: Performance Key Figures of Server for Par. Execution |

DDSESELOPT | Selopt Structure for the F4 Help with Search Engines | DDSETSTATE | Status of Objects | DDSETYPTAB | Search Type Search Engine | DDSEVMAP | DD: Map severity for level/STDO | DDSEVSUM | DD: | DDSHBUTTON | Buttons on the Hit List | DDSHCUMAR | Information on Cursor Position and Markings | DDSHDEFLT | Description of a default value for search help fields | DDSHDEFSH | Default value - search help per user and collective s.h. | DDSHDESCR | Interface: elementary search helps of a search help | DDSHENTITY | Table of data elements which need the value table help | DDSHEXMPL1 | Structure for F4 help example RUTSHEXP | DDSHF4CTRL | Control Structure for F4 Process with Search Help Exit | DDSHF4ENV | Program Environment for F4 Field | DDSHFPROP | Characteristics of search help parameters | DDSHHVALUE | Historic Help Values | DDSHICON | Management of Icon Information | DDSHIFACE | Interface description of a F4 help method | DDSHLDB1 | Interface structure search help <-> logical DBs | DDSHLPVERS | Current Version of Search Help Activator | DDSHOCXINT | Communications between F4 process and search help OCX | DDSHOFFLD | Shared buffer for search help for a DDIC field | DDSHOUTFLD | Interface structure for FM to search help selection | DDSHPVALUE | Personal Help Values | DDSHRETVAL | Interface Structure Search Help <-> Help System |

DDSHSELOPT | Selection options for value selection with search help | DDSHTECINF | Technical information about a search help | DDSPAR | Storage clause for tables and indexes | DDSPAR1 | Storage clause for tables and indexes | DDSPAR2 | Storage clause for tables and indexes | DDSTATE | Status of Objects | DDSTATHIST | DD: Statistical Data for Conversion | DDSTEXTIDX | Header Information of External Index | DDSTORAGE | Storage clause for tables and indexes | DDSTORAGE1 | Storage clause for tables and indexes | DDSTORAGE2 | Storage clause for tables and indexes | DDSYM10TAB | Symbol table (CHAR10) | DDSYMTAB | Symbol table (as reference structure) | DDSYN | Parameters for Buffer Synchronization | DDTABFDS | DD: Structure/table name - field name with lengths | DDTABLE | Structure for Table Information | DDTABNAME | Only table name | DDTABTVAL | DD: Control string for TABT values checks | DDTBCLASS | DD: Control String for Checking TABCLASS <-> SQLTAB | DDTBFD | DD: Table Name, Field Assignment | DDTBFDCHK | Control String for Table Checks (Fields) | DDTBFKCHK | Control String for Foreign Key Checks in Table Activator | DDTBHDCHK | Control String for Table Checks (Header) | DDTBIXCHK | Control String for the Index Checks | DDTCCT | DD: Cluster Tables -> Table Clsuter - Assignment |

DDTEMPL | DD: Structure for mapping SKIND -> text | DDTEXTDATA | Data cluster as text | DDTIMER | DD: Basic tools, timer structure | DDTRKORR | DD: Structure for Transport Requests | DDTTACTRES | DD: Status of Table Types (Activator Results) | DDTTSTATE | DD: Result when reading the TABT activation set | DDTYPEDESC | Description of an ABAP Dictionary Type | DDTYPEGET | Control structure for DD_TYPEINFO_GET | DDTYPES | Table of all Dictionary types and classes | DDTYPET | ABAP/4 Dictionary: Texts for type groups | DDUDMPAR | Parameters for attribute maintenance / partial objects | DDUDT | DD: Include for user, date, time | DDVAL | Generated table for view DDVAL | DDVE1 | Value Table for Domain DDVERINT4 | DDVEPR | Check Table with Two Key Fields | DDWHERECND | DD: Lines of where condition | DDXTF | Nametab field structure for delayed writing | DDXTT | Nametab header structure for delayed writing | DDYN | Interface Between ABAPhelp and Help Processor | DDYTF | Substitution Nametab (shadow-shadow-nametab for DDXTF) | DDYTT | Substitution Nametab (shadow-shadow-nametab for DDXTT) | DD_LB_TEST | Generated Table for View DD_LB_TEST |
[edit]

Conclusion
It is thus possible to use these tables. Please feel free to add or correct any of the above.

Who and/or what is SAP? How popular is it? Wow! SAP the company was founded in Germany in 1972 by five ex-IBM engineers. In case youre ever asked, SAP standsfor Systeme, Andwendungen, Produkte in der Datenverarbeitung which - translated to English - means Systems, Applications, Products in Data Processing . So now you know! Being incorporated in Germany, the full name of the parent company is SAP AG. It is located in Walldorf, Germany which is close to the beautiful town of Heidelberg. SAP has subsidiaries in over 50 countries around the world from Argentina to Venezuela (and pretty much everything in between). SAP America (with responsibility for North America, South America and Australia go figure!) is located just outside Philadelphia, PA. The original five founders have been so successful that they have multiplied many times over such that SAP AG is now the third largest software maker in the world, with over 17,500 customers (including more than half of the world's 500 top companies). SAP employs over 27,000 people worldwide today, and had revenues of $7.34 billion and Net Income of $581 million in FY01. SAP is listed in Germany (where it is one of the 30 stocks which make up the DAX) and on the NYSE (ticker:SAP). There are now 44,500 installations of SAP, in 120 countries, with more then 10 million users! So what made this company so successful? Back in 1979 SAP released SAP R/2 (which runs on mainframes) into the German market. SAP R/2 was the first integrated, enterprise wide package and was an immediate success. For years SAP stayed within the German borders until it had penetrated practically every large German company. Looking for more growth, SAP expanded into the remainder of Europe during the 80's. Towards the end of the 80's, client-server architecture became popular and SAP responded with the release of SAP R/3 (in 1992). This turned out to be a killer app for SAP, especially in the North American region into which SAP expanded in 1988. The success of SAP R/3 in North America has been nothing short of stunning. Within a 5 year period, the North American market went from virtually zero to 44% of total SAP worldwide sales. SAP America alone employs more than 3,000 people and has added the names of many of the Fortune 500 to its customer list (8 of the top 10 semiconductor companies, 7 of the top 10 pharmaceutical companies etc). SAP today is available in 46 country-specific versions, incorporating 28 languages including Kanji and other double-byte character languages. SAP also comes in 21 industry-specific versions. SAP R/3 is delivered to a customer with selected standard process turned on, and many many other optional processes and features turned off. At the heart of

SAP R/3 are about 10,000 tables which control the way the processes are executed. Configuration is the process of adjusting the settings of these tables to get SAP to run the way you want it to. Think of a radio with 10,000 dials to tune and youll get the picture. Functionality included is truly enterprise wide including: Financial Accounting (e.g. general ledger, accounts receivable etc), Management Accounting (e.g. cost centers, profitability analysis etc), Sales, Distribution, Manufacturing, Production Planning, Purchasing, Human Resources, Payroll etc etc etc. For a full description of the modules included in SAP, see the related articles. All of these modules are tightly integrated which as you will find out is a huge blessing ... but brings with it special challenges. SAP are maintaining and increasing their dominance over their competitors through a combination of - embracing the internet with mySAP.com (a confusing name we believe) to head off i2 etc - extending their solutions with CRM to head off Siebel - adding functionality to their industry solutions Article 2 Who is it made for? Why might I need it? We have all heard about the large (and very large) companies who have implemented (or are still busy implementing) SAP R/3. But SAP is gaining acceptance by smaller companies too. There are many reasons a company selects and implements SAP some are good and some are bad. The good ones include replacing an out-dated and inefficient IT Architecture (including the CIOs nemesis the burning platform), enabling business process change, and to gain competitive advantage. The bad ones are too numerous to go into here but would include the "why are we the only semiconductor company without SAP" question. More on the good reasons follows: 1. Replacing an out-dated and inefficient IT Architecture: In the beginning, computer systems were developed by individual departments to satisfy the requirements of that particular department. When someone finally realized that benefits could be had by linking these systems together, interface heaven was born. There are some companies today with literally thousands of interfaces, each of which needs to be maintained (assuming of course that there is someone around who understands how they work!). Sweeping them away and replacing them with an integrated

system such as SAP can save much money in support. Of course, if you have a burning platform as well the question becomes even easier. 2. Enabling business process change From the start, SAP was built on a foundation of process best practices. Although it sounds absurd, it is probably easier (and less expensive) to change your companies processes to adapt to SAP than the other way around. Many companies have reported good success from combining a SAP implementation with a BPR project. 3. Competitive advantage The CFO types around have heard this old saying from the CIO types for many years now. The question still has to be asked can you gain competitive advantage from implementing SAP? The answer, of course, depends on the company. It seems to us, however, that:

being able to accurately provide delivery promise dates for manufactured products (and meet them) doesnt hurt ... and being able to consolidate purchase decisions from around the globe and use that leverage when negotiating with vendors has gotta help and being able to place kiosks in stores where individual customers can enter their product specifications and then feed this data directly into its production planning process is pretty neat etc etc

Ok. So you want SAP, you need SAP, you gotta have SAP. Article 3 How much does it cost? What will it take to implement it? Wow! There is a defining moment in the journey of all companies on the road to SAP nirvana. This moment comes just after the company has concluded that it wants SAP, it needs SAP, its gotta have SAP then comes the question so what does it take to implement it? This is the question which separates those who are ready from the wannabees. Before being accused of being too negative, let me remind you that at the heart of every good business decision lies a cost benefit analysis. If this cannot be complete with a positive outcome, the initiative (whatever it is) should probably not be launched. Same goes for a SAP implementation. Implementing SAP is expensive. No doubt about it. But the potential rewards can dwarf the costs (and have for many existing customers already). One customer reportedly made enough savings on the procurement of a single raw material to pay for the entire enterprise-wide SAP implementation! Of course

these are hard to substantiate, but visit SAPs website and take a look at the customer testimonials. SAP sells its R/3 product on a price per user basis. The actual price is negotiated between SAP and the customer and therefore depends on numerous factors which include number of users and modules (and other factors which are present in any negotiation). You should check with SAP, but for a ballpark planning number you could do worse than starting with $4000 per user. There is also an annual support cost of about 10% which includes periodic upgrades. Again, check with SAP. Then there is the implementation cost. Yowser. It is about now that you need to get the business case out again and remind yourself why you need to do this. The major drivers of the total implementation cost are the Timeframe, Resource Requirements and Hardware. 1. Timeframe - The absolute quickest implementation we have ever heard of is 45 days but this was for a tiny company with very few users and no changes to the delivered SAP processes. At the other end of the scale you get the multi-nationals who are implementing SAP over 5 to 10 years. These are not necessarily failures many of them are planned as successive global deployments (which seem to roll around the globe forever). Of course the really expensive ones are those we dont hear about! For the most part, you should be able to get your (single instance) project completed in a 9 to 18 month period. 2. People The smallest of SAP implementations can get done on a parttime basis without outside help. The largest swallow up hundreds of people (sometimes over a thousand) and include whole armies of consultants. This adds up fast. Again, get that business case out. The types of people you will need run the range from heavy duty techies to project managers. 3. Hardware The smallest of SAP implementations probably use only three instances (boxes) one for the production system, one for test, and one for development. The largest implementations have well over 100 instances, especially if they involve multiple parallel projects (otherwise known as a program). Adding all this up, your SAP project can run anywhere from $400,000 to hundreds of millions of $$$s. As you can see, SAP can be all things to all companies so its best to talk to them (or your consulting firm) about your specific requirements.

Article 4 Is there any help out there? What should I do next? Help From SAP AG There is a ton of help available out there - depending on your companies budget and culture to help you along your journey beginning with your strategy and ending up when you reach that hallowed (and sometimes distant) ground of post-implementation. This article concentrates on the help available from SAP AG. Article 5discusses other sources of help. SAP AG As you read in article 1 of this series, SAP AG employs around 22,000 people. Although they re-organize as often as most other companies, you can think of them as being organized into the following four areas: Pre-Sales, Consulting, Training and Developers.

Pre-Sales. These are people with heavy-duty functional knowledge of one or more SAP modules and one or more industries. They give really excellent system demonstrations on particular areas of the system which while thick with pre-sales features are an extremely valuable source of information about SAP. Im sure they have many other responsibilities as well, but if you can, get a demo from them. For an even more useful demo, ask if you can provide them with business process scenarios that are pertinent to your business or industry prior to the demo. Consulting. While also knowledgeable in SAP (of course), these are mostly consulting types like those that can be found in the major consulting firms. Often a team will consist of consultants from SAP and a partner consulting firm and you will not know the difference. Expect them to have business process and/or industry knowledge in addition to detailed SAP knowledge. They are not readily available to noncustomers as they are usually assigned to one or more customers. Training. In 1999 SAP opened up their training programs to noncustomers and non-partners. This opens up a whole world of top-rate training programs at SAPs facilities around the globe. These can be expensive, however, and up to three weeks are usually required to gain a sufficiently deep understanding of a particular module or subject. If you have lots of time and money, you could register for one of SAPs academies which are five-week crash courses (emphasis on crash as in burn) in one of the following areas: FI/CO, MM/SD, and HR/ABAP. These end with an examination and 'certification' in your chosen area.

More information on SAP training courses can be found on SAPs website. Developers. These heavy-duty techies are off limits to non-customers. Customers can sometimes get a message to them via the OSS system which is an automated trouble ticket type system. If you ever actually see one, or have one on the phone, ask all the questions you can think of, as you may never have the chance again! Article 5 Is there any help out there? What should I do next? Help From Other Sources

Article 4 i n this series covered the help that is available from SAP AG. Here we will cover the help that is available from other sources, including: Consulting Companies, SAPPHIRE and other SAP Events, ASUG, and this website.
1. Consulting Companies

One of SAPs key strategies has been to develop partnerships with the Consulting Companies. This has contributed enormously to the widespread adoption of SAP due to the fact that there are literally thousands of consultants (SAP estimate 55,000) ready to help with all aspects of your SAP implementation from strategy to completion. There are two types of consulting partners: 1. Global consulting partners (13 of these at last count) are the largest of the consulting firms who are able to provide global assistance to global companies, and 2. National consulting partners who are accredited by country Your need of a consulting partner depends on your project scope and complexity, your project budget, company culture, and prior SAP implementation experience in your company. Suffice to say that without heavy prior SAP experience in your company, all but the simplest SAP implementations would benefit from the involvement of experienced individuals who have done it before. Rates depend on your negotiations with the consulting company, of course, but you could do worse than use an estimate of $200 per person per hour. Consulting styles differ from firm to firm, so make sure your company culture is compatible with the typical approach of your chosen consulting partner. In addition, spend some time on their websites to get an idea of their

approach, experience and capabilities.

2. SAPPHIRE and other SAP events

SAPPHIRE is the name given to SAPs annual user conference. Multiple SAPPHIREs can be found around the globe each year, and are usually sold out in advance. North American SAPPHIRE's are typically held in hot cities (off season) and attract upwards of 14,000 prospects, customers and partners. SAPPHIRE is a great place to go explore, but is quite expensive at around $2,200 for three days (food, lodging, travel etc is at your own expense). Even so, it is well worth the time and expense. Note: SAP holds other events throughout the year (TechEd, for example, is aimed at the more technical users) See their website for additional details.
3. ASUG (Americas SAP User Group)

As the name suggests, ASUG is a forum for users of SAP. Non-users (prospects and consultants) and not usually found lurking here. ASUG actually comprises of multiple sub-ASUGs each focusing on a particular area of SAP, for example there is an ASUG for High Tech companies, and an ASUG for companies using ALE etc. Leadership of these sub-ASUGs (for lack of a better description) usually rotates between members of the user community. ASUG provides opportunities for networking, learning and influencing SAP (for example joining forces with other users to convince SAP to include a particular modification in their standard software). In addition to meetings within the sub-ASUGs, there is an annual conference (which attracted nearly 6,000 users and vendors in 1999). 4. If you have read all five of the articles in this series, well done! If you have the time, we would really appreciate some feedback. Article 6 SAP AG Corporate Overview 3rd - SAP is the 3rd largest software company in the world 30,000 - Total number of people employed by SAP 5,400 - Number of programmers employed by SAP $7.024 billion - FY03 Revenue $1.077 million - FY03 Net Income

12,000 - Number of companies using SAP 79,800 - Number of SAP installations 12,000,000 - Number of people using SAP 120,000,000 - Total number of people in the 12,000 companies who are using SAP 28 - Number of languages supported by SAP 46 - Number of country-specific versions of SAP 22 - Number of industry-specific versions of SAP 1,000 - Number of pre-defined best practices contained in the SAP system 10,000 - Number of tables requiring configuration in a full SAP implementation 55,000 - Number of SAP experienced consultants worldwide 28 - Number of years ago SAP was started 5 - Number of people who started SAP
Financial Summary

Article 7 SAP Modules and Solutions Overview

In the past when people were discussing SAP, the conversation very quickly boiled down to modules, for example:

SAPs courses were structured along module lines so that you would attend MM 101, 102 and 103. While at the course you would learn many things about MM, but not much about the rest of the SAP system and how MM fits into it. A conversation with a SAP recruiter might go something like this:

Recruiter which modules do you work with? Candidate well, I have a lot of purchasing process experience Recruiter yes, but which modules do you work with? Candidate well, its purchasing functionality so that would be, umm, MM, FI and CO mainly Recruiter great I have just the job for you Candidate fantastic, is it purchasing? Recruiter well it says here that they want an MM, FI and CO person and thats you, right? Not necessarily! A MM, FI, CO role might include Inventory Management (MM), Accounts Receivable (FI) and Profitability Analysis (CO) none of which a purchasing person is guaranteed to have Many programme teams were organised along module lines, so that you would have a FI/CO, an MM and a HR team, for example. Training courses were (therefore) often prepared and delivered along module lines too. The result of this was that solutions were frequently optimised along module lines, and less often well integratred, and as for users, well, they were pretty much trained up in a module and left to get on with it post go-live. Fortunately those days are mostly passed, and more and more programmes (from design to build to training) are being organised along process lines such as: Order to Cash (including parts of SD, FI-AR and probably TY as well) Purchase to Pay (including MM-Purchasing and FI-AP) Record to Report (FI-GL etc) SAP now are moving away from describing their system as a set of modules, and now are using the term solutions, which is much better. If you visit SAP's website (as we urge you to do) you will find that they have structured their Solutions tab as follows:

Financials Human Resources Customer Relationship Management Supplier Relationship Management Product Lifecycle Management Supply Chain Management Business Intelligence

If youre still looking for that list of modules, here they are: FI Financial Accounting essentially your regulatory books of record, including

General ledger Book close Tax Accounts receivable Accounts payable Consolidation Special ledgers

CO Controlling basically your internal cost/management accounting, including

Cost elements Cost centres Profit centres Internal orders Activity based costing Product costing

AM Asset Management track, value and depreciate your assets, including

Purchase Sale Depreciation Tracking

PS Project Systems manage your projects, large and small, including

Make to order Plant shut downs (as a project) Third party billing (on the back of a project)

HR Human Resources ah yes, people, including

Employment history Payroll Training Career management Succession planning

PM Plant Maintenance maintain your equipment (e.g. a machine, an oil rig, an aircraft etc), including

Labour Material Down time and outages

MM Materials Management underpins the supply chain, including

Requisitions Purchase orders Goods receipts Accounts payable Inventory management BOMs Master raw materials, finished goods etc

QM Quality Management improve the quality of your goods, including

Planning Execution Inspections Certificates

PP Production Planning manages your production process, including

Capacity planning Master production scheduling Material requirements planning Shop floor

SD Sales and Distribution from order to delivery, including

RFQ

Sales orders Pricing Picking (and other warehouse processes) Packing Shipping

CA Cross Application these lie on top of the individual modules, and include

WF workflow BW business information warehouse Office for email Workplace Industry solutions New Dimension products such as CRM, PLM, SRM, APO etc Article 8 15 Things You Need To Know About mySAP.com

1. What is mySAP.com?

In SAP's words "mySAP.com is an open collaborative business environment of personalized solutions on demand"
2. Ok, really now. What is mySAP.com?

In our words, mySAP.com is actually a collection of three things. a) The Marketplace is a website where buyers and sellers can register themselves, and then buy and sell from each other. b) The Workplace is a piece of software which sits on your desktop, and allows you (after ity is setup correctly) to gain access to all of the systems you use in your company. It is, naturally, tightly integrated with both SAP and the Marketplace. c) mySAP.com is also the umbrella name for all of SAP's internetenabled applications.
3. What is SAP's competitive advantage over other e-Business vendors?

In a word, integration - especially for SAP's 20,000 customers. SAP have termed it "three-dimensional integration"
4. What is "three-dimensional integration"?

a) Integration of core business systems within an organization - frontend to back-end b) Seamless flow of data between two organizations who transact with

each other c) Ability for participants in an industry to use any systems, and still communicate with other participants in that industry
5. Does the Marketplace exist now?

Yes.
6. Is the Workplace available now?

Yes. It was available 3rd quarter 1999.

7. Do you have to be a SAP customer to use the Marketplace?

No. Anyone can register as a buyer or seller on the marketplace. But if you use SAP, it is much easier to transact with another party who also uses SAP - it's called a one-step transaction.
8. What's a one-step transaction?

If both parties to a transaction use SAP, then all purchase orders, sales orders, etc etc are automatically entered into both parties' systems with one click (i.e. on approval of the purchase).
9. Does mySAP.com replace R/3?

No. If you have SAP R/3 implemented, then mySAP.com sits "on top" of R/3.
10. Is this actually R/4?

No. mySAP.com sits "on top" of R/3. 11.What is R/3's future? R/3, along with all other current SAP products, will become 'components' of mySAP.com.
12. Can mySAP.com run by itself?

Yes. The Workplace, Marketplace and Internet-enabled applications can run without SAP R/3 as the back-office system.
13. How is mySAP.com priced?

Not an easy question. Talk is of "pay per name", "pay per record" and "pay per transaction". Stay tuned.
14. Let's get technical. Does mySAP.com use XML?

Yes. We understand it is in close co-operation with webMethods and

Microsoft's BixTalk.
15. Which standards (W3C, OAG etc) are mySAP.com in compliance with?

No clear answer yet. Their response is "mySAP.com will be compliant with all relevant content and protocol standards" Article 9 Industry Solutions Or, "Advantage SAP" As mentioned in our Take a closer look ' article (first published July 2002), we believe that Industry Solutions are one of three major advantages that SAP have built up over their competition. Here we provide more information about SAP's industry solutions. As you know, SAP started many years ago with a single, integrated, solution. For many years they continued along this 'one size fits all' until about 1994/5 when at SAPPHIRE they launched their industry solutions initiative promising that now they understood that industries were different (surely not!) and so they would release versions of their software which were customised for particular industries. SAP have been working on it for around 7 years now, and we think they have a fine job. Here then are the 21 Industry Solutions together with an SAP written overview document you can download. If you want to know more about any of them, use the links to the SAP Industry Solution page. As you read through the list below take a look at some of the key features we extracted (not by any means a comprehensive list). What an incredible competitive advantage. Can you imagine the integration meetings required to keep all these parallel developments in check and integrated with the core? The answer to the 'how do they keep all this integrated with the core' question we posed at the top of the article lies, we think, in keeping a tight grip on the data ... and there is a lesson in there for everyone working on enterprise systems.