PLM_ECM_SEARCH SAP (BUS1039 MyObjects: Search MiniApp External) Structure details
Dictionary Type: Structure
Description: BUS1039 MyObjects: Search MiniApp External
Description: BUS1039 MyObjects: Search MiniApp External
ABAP Code to SELECT data from PLM_ECM_SEARCH
Related tables to PLM_ECM_SEARCH
Access table PLM_ECM_SEARCH
Related tables to PLM_ECM_SEARCH
Access table PLM_ECM_SEARCH
Structure field list including key, data, relationships and ABAP select examples
PLM_ECM_SEARCH is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "BUS1039 MyObjects: Search MiniApp External" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_PLM_ECM_SEARCH TYPE PLM_ECM_SEARCH.
The PLM_ECM_SEARCH table consists of various fields, each holding specific information or linking keys about BUS1039 MyObjects: Search MiniApp External data available in SAP. These include PARENT (Nodes in MyObjects (key)), OBJKEY (Object Key), OBJTYPE (Object Type), LOGSYS (Logical System).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type or numeric)
SAP PLM_ECM_SEARCH structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| PARENT | Nodes in MyObjects (key) | PLM_AMYO_NODE | CHAR | 10 | PLM_AMYO_NODD | ||||
| OBJKEY | Object Key | PLM_SWO_TYPEID | CHAR | 70 | PLM_SWO_TYPEID | ||||
| OBJTYPE | Object Type | PLM_SWO_OBJTYP | CHAR | 10 | PLM_OJ_NAME | ||||
| LOGSYS | Logical System | PLM_LOGSYS | CHAR | 10 | ALPHA | PLM_LOGSYS | |||
| TEXT | Text of a MyObjects Entry | PLM_AMYO_TEXT | CHAR | 132 | PLM_PLM_AMYO_TEXT | ||||
| POSI | Position Within a Node | PLM_AMYO_POS | INT4 | 10 | INT4 | ||||
| TIMESTAMP | UTC Time Stamp in Short Form (YYYYMMDDhhmmss) | PLM_TIMESTAMP | DEC | 15 | PLM_TIMESTAMP | ||||
| MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| AENNR | Change Number | AENNR | CHAR | 12 | Assigned to domain | AENNR | AENNR | AEN | |
| AENST | Status of change number | AENST | NUMC | 2 | T419S | AENST | |||
| AENBE | Authorization group for change master record | CC_AENBE | CHAR | 4 | CC_BEGRU | ||||
| DATUV | Valid-From Date | CC_CCDAT | DATS | 8 | CC_DATUM | ||||
| TECHV | Technical status from | CC_TECHV | CHAR | 12 | CC_TECHS | ||||
| ANDAT | Date record created on | CC_ANDAT | DATS | 8 | CC_DATUM | ||||
| ANNAM | User who created record | CC_ANNAM | CHAR | 12 | CC_USNAM | ||||
| AEDAT | Date of Last Change | CC_AEDAT | DATS | 8 | CC_DATUM | ||||
| AENAM | Name of person who changed object | CC_AENAM | CHAR | 12 | CC_USNAM | ||||
| AETXT | Change Number Description | CC_AETXT | CHAR | 40 | CC_TEXT40 | ||||
| LTXSP | Language: The long text was stored in this language | CC_LTXSP | LANG | 1 | Assigned to domain | ISOLA | SPRAS | ||
| AEGRU | Reason for change | CC_AEGRU | CHAR | 40 | CC_TEXT40 | ||||
| CCART | Change type | CC_CCART | NUMC | 3 | Assigned to domain | CC_CCART | AENR_CCART | ||
| CCSTM | Maximum partial status keys in engineering change management | CCSTM_D | NUMC | 8 | CC_NUMC8 | ||||
| DYDAT | Indicator: change number with dynamic date | CC_DYDAT | CHAR | 1 | CC_XFELD | ||||
| CONT1 | Digital signature (process improvement) | CC_DSIGN | CHAR | 1 | CC_DSIGN | ||||
| AEFUN | Change number function | CC_AEFUN | CHAR | 1 | CC_AEFUN | ||||
| UESTR | Indicator: Overriding possible | CC_UESTR | CHAR | 1 | CC_XFELD | ||||
| RLKEY | Release Key for Change Master Record | CC_RLKEY | NUMC | 2 | TCC10 | CC_RLKEY | CC_RLKEY | ||
| LVORM | Deletion Flag for Change Number (Reorganization) | CC_LOEKZ | CHAR | 1 | CC_XFELD | ||||
| CLINT | Internal class number describing effectivity type | CC_CLINT | NUMC | 10 | Assigned to domain | CC_CLINT | |||
| AERNG | ECM: rank of change number | CC_AERNG | NUMC | 2 | CC_NUMC2 | ||||
| RLDAT | Date when the release key was changed | CC_RLDAT | DATS | 8 | CC_DATUM | ||||
| RLTIM | Time when the release key was changed | CC_RLTIM | TIMS | 6 | CC_UZEIT | ||||
| TEREL | Indicator: Technical release occurs | CC_TEREL | CHAR | 1 | CC_XFELD | ||||
| NACHT | Indicator: Change Package Created After Release | CC_NACHT | CHAR | 1 | CC_CHAR1 | ||||
| INDAT | Effective Date of Statutory Regulation | CC_INDAT | DATS | 8 | CC_DATUM | ||||
| AUDAT | End Date for Transitional Period (Prescribed by Law) | CC_AUDAT | DATS | 8 | CC_DATUM | ||||
| FLUSE | Change number has been used for data maintenance | CC_FLUSE | CHAR | 1 | CC_XFELD | ||||
| AEDIF | ECM: differentiate effectivity types | CC_AEDIF | NUMC | 10 | CC_NUMC10 | ||||
| ERLED | Indicator for basic change | CC_AEERL | CHAR | 1 | CC_XFELD |
| Key field | Non-key field |
How do I retrieve data from SAP structure PLM_ECM_SEARCH using ABAP code?
As PLM_ECM_SEARCH is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on PLM_ECM_SEARCH as there is no data to select.How to access SAP table PLM_ECM_SEARCH
Within an ECC or HANA version of SAP you can also view further information about PLM_ECM_SEARCH and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects