BBPS_CTR_MM_ATT SAP (Contract Attachments Structure Without PHIO Content) Structure details
Description: Contract Attachments Structure Without PHIO Content
Related tables to BBPS_CTR_MM_ATT
Access table BBPS_CTR_MM_ATT
Structure field list including key, data, relationships and ABAP select examples
BBPS_CTR_MM_ATT 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 "Contract Attachments Structure Without PHIO Content" 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_BBPS_CTR_MM_ATT TYPE BBPS_CTR_MM_ATT.
The BBPS_CTR_MM_ATT table consists of various fields, each holding specific information or linking keys about Contract Attachments Structure Without PHIO Content data available in SAP. These include BE_OBJECT_ITEM_NO (Item Number of Purchasing Document), BE_OBJECT_TYPE (Document class), OBJECT_TYPE (Single-Character Indicator), CLIENT (Client).. 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 BBPS_CTR_MM_ATT 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 |
| BE_OBJECT_ID | Contract number | BBP_BAPI_EBELN_K | CHAR | 10 | ALPHA | BBP_BAPI_EBELN | |||
| BE_OBJECT_ITEM_NO | Item Number of Purchasing Document | EBELP | NUMC | 5 | Assigned to domain | EBELP | BSP | ||
| BE_OBJECT_TYPE | Document class | SDOK_CLASS | CHAR | 10 | Assigned to domain | SDOK_CLASS | |||
| OBJECT_TYPE | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| CLIENT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| LOGICAL_SYSTEM | Logical System of Template Document (empty if in local sys.) | BBP_SRC_LOGSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
| DOC_ID | Business Document Service: Document ID | BDS_DOCID | CHAR | 42 | CHAR42 | ||||
| DOC_VER_NO | Business Document Service: Document version number | BDS_DVERNO | NUMC | 8 | NUM08 | ||||
| DESCRIPTION | Business Document Service: Attribute value | BDS_PROPVA | CHAR | 64 | CHAR64 | ||||
| DOC_VAR_ID | Business Document Service: Document variant ID | BDS_DVARID | NUMC | 8 | NUM08 | ||||
| OBJKEY | Business Document Service: Object key | BDS_TYPEID | CHAR | 70 | SWO_TYPEID | ||||
| CLASSTYPE | Business Document Service: Class type | BDS_CLSTYP | CHAR | 2 | BDS_CLSTYP | ||||
| CLASSNAME | Business Document Service: Class name | BDS_CLSNAM | CHAR | 30 | CHAR30 | ||||
| TYPE | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| URL | Relative storage location of physical document | SDOK_FILNM | CHAR | 255 | SDOK_FILNM | ||||
| INTERNAL_IND | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| DEL_IND | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| CATEG | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| CREATIONTIME | Transaction was Created at this Time | BBP_CREATEDAT | DEC | 15 | TSTPS | BBP_BCOS_TSTMP | |||
| LOIO_CLASS | Document class | SDOK_CLASS | CHAR | 10 | Assigned to domain | SDOK_CLASS | |||
| LOIO_OBJID | ID for documents and relations | SDOK_DOCID | CHAR | 32 | SDOK_DOCID | ||||
| PHIO_CLASS | Document class | SDOK_CLASS | CHAR | 10 | Assigned to domain | SDOK_CLASS | |||
| PHIO_OBJID | ID for documents and relations | SDOK_DOCID | CHAR | 32 | SDOK_DOCID | ||||
| DISP_URL | Relative storage location of physical document | SDOK_FILNM | CHAR | 255 | SDOK_FILNM | ||||
| PHIO_EXT | Code for document class | SO_OBJ_TP | CHAR | 3 | Assigned to domain | SO_OBJ_TP | |||
| PHIO_FSIZE | File size (in bytes) | SDOK_FSIZE | NUMC | 12 | SDOK_FSIZE | ||||
| PHIO_MIME | HTML content type | W3CONTTYPE | CHAR | 128 | W3_CONTTYP | ||||
| PHIO_FNAME | Relative storage location of physical document | SDOK_FILNM | CHAR | 255 | SDOK_FILNM | ||||
| PHIO_PS_MIME | HTML content type | W3CONTTYPE | CHAR | 128 | W3_CONTTYP | ||||
| PHIO_PS_FSIZE | File size (in bytes) | SDOK_FSIZE | NUMC | 12 | SDOK_FSIZE | ||||
| XI_TYPE | Business Document Service: Attribute value | BDS_PROPVA | CHAR | 64 | CHAR64 | ||||
| XI_ID | Data Element Type CHAR Length 35 | CHAR35 | CHAR | 35 | CHAR35 | ||||
| XI_URL | Relative storage location of physical document | SDOK_FILNM | CHAR | 255 | SDOK_FILNM | ||||
| ATTACHMENT_INDEX | 5 Character Numeric NUMC | NUMC5 | NUMC | 5 | NUM5 |
| Key field | Non-key field |
How do I retrieve data from SAP structure BBPS_CTR_MM_ATT using ABAP code?
As BBPS_CTR_MM_ATT 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 BBPS_CTR_MM_ATT as there is no data to select.How to access SAP table BBPS_CTR_MM_ATT
Within an ECC or HANA version of SAP you can also view further information about BBPS_CTR_MM_ATT 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