ISU_BCONT_DOC SAP (IS-U Archiving: Business Partner Contact) Structure details
Description: IS-U Archiving: Business Partner Contact
Related tables to ISU_BCONT_DOC
Access table ISU_BCONT_DOC
Structure field list including key, data, relationships and ABAP select examples
ISU_BCONT_DOC 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 "IS-U Archiving: Business Partner Contact" 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_ISU_BCONT_DOC TYPE ISU_BCONT_DOC.
The ISU_BCONT_DOC table consists of various fields, each holding specific information or linking keys about IS-U Archiving: Business Partner Contact data available in SAP. These include MANDT (Client), BPCONTACT (Business Partner Contact), PCATEGORY (Business Partner Category of SAP System), PARTNER (Business Partner Number).. 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 (Deep)
SAP ISU_BCONT_DOC 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 |
| BCONT | 0 | ||||||||
| MANDT | Client | MANDT | CLNT | 3 | MANDT | ||||
| BPCONTACT | Business Partner Contact | CT_CONTACT | CHAR | 12 | ALPHA | CT_CONTACT | BPC | CT_BCONTACT | |
| PCATEGORY | Business Partner Category of SAP System | CT_PCATEG | CHAR | 1 | CT_PCATEG | ||||
| PARTNER | Business Partner Number | BU_PARTNER | CHAR | 10 | ALPHA | BU_PARTNER | BPA | BUPA | |
| ALTPARTNER | Contact Person | CT_ALTPART | CHAR | 10 | ALPHA | BU_PARTNER | BPA | ||
| RLTYP | BDT: Object part | BU_RLTYP | CHAR | 6 | BU_RLTYP | ||||
| CTYPE | Contact Type | CT_CTYPE | CHAR | 3 | ALPHA | CT_CTYPE | |||
| CCLASS | Contact Class | CT_CCLASS | CHAR | 4 | ALPHA | CT_CLASS | |||
| ACTIVITY | Contact Action | CT_ACTIVIT | CHAR | 4 | ALPHA | CT_ACTIVIT | |||
| F_COMING | Contact Direction (Incoming or Outgoing) | CT_COMING | CHAR | 1 | ALPHA | CT_COMING | |||
| ORIGIN | Technical Origin of Business Partner Contact | CT_ORIGIN | CHAR | 1 | CT_ORIGIN | ||||
| CTDATE | Date | DATUM | DATS | 8 | DATUM | ||||
| CTTIME | Time | TIME_ | TIMS | 6 | SYTIME | ||||
| ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
| ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| AEDAT | Changed On | AEDAT | DATS | 8 | DATUM | ||||
| AENAM | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM | ||||
| BEGRU | Authorization Group | BEGRU | CHAR | 4 | BEGRU | ||||
| LOEVM | Deletion Indicator | LOEVM | CHAR | 1 | XFELD | ||||
| WFID | Workflow ID | CT_WFID | NUMC | 12 | SWW_WIID | ||||
| ADDINFO | Additional Documents Are Available | CT_ADDINFO | CHAR | 2 | ALPHA | CT_ADDINFO | |||
| PRIORITY | Contact Priority | CT_PRIORITY | CHAR | 2 | ALPHA | CT_PRIORITY | |||
| CUSTINFO | Customer Information | CT_CUSTINFO | CHAR | 2 | ALPHA | CT_CUSTINFO | |||
| SPARTE | Division | SPARTE | CHAR | 2 | SPART | SPA | |||
| BUKRS | Company Code | BUKRS | CHAR | 4 | BUKRS | BUK | C_T001 | ||
| TOCHANGE_TAB | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure ISU_BCONT_DOC using ABAP code?
As ISU_BCONT_DOC 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 ISU_BCONT_DOC as there is no data to select.How to access SAP table ISU_BCONT_DOC
Within an ECC or HANA version of SAP you can also view further information about ISU_BCONT_DOC 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