BUS_OPI SAP (Business Partner OPI Interface) Structure details
Description: Business Partner OPI Interface
Structure field list including key, data, relationships and ABAP select examples
BUS_OPI 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 "Business Partner OPI Interface" 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_BUS_OPI TYPE BUS_OPI.
The BUS_OPI table consists of various fields, each holding specific information or linking keys about Business Partner OPI Interface data available in SAP. These include NAME2 (Name 2 of organization), LANGUAGE (2-Character SAP Language Code), STD_COMM_TYPE (BP Standard Communication Type for OPI Interface), CO_NAME (c/o name).. 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)
SAP BUS_OPI 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 |
| NAME1 | Name 1 of organization | BU_NAMEOR1 | CHAR | 40 | BU_NAME | ||||
| NAME2 | Name 2 of organization | BU_NAMEOR2 | CHAR | 40 | BU_NAME | ||||
| LANGUAGE | 2-Character SAP Language Code | LAISO | CHAR | 2 | LAISO | ||||
| STD_COMM_TYPE | BP Standard Communication Type for OPI Interface | BU_OPI_STD_COMM_TYPE | CHAR | 3 | BU_OPI_COMM_TYPE | ||||
| CO_NAME | c/o name | AD_NAME_CO | CHAR | 40 | TEXT40 | ||||
| CITY | City | AD_CITY1 | CHAR | 40 | TEXT40 | CLCITYNAME | |||
| DISTRICT | District | AD_CITY2 | CHAR | 40 | TEXT40 | CITY_PART | |||
| POSTAL_CODE | City postal code | AD_PSTCD1 | CHAR | 10 | CHAR10 | ||||
| POSTL_COD_PO_BOX | PO Box Postal Code | AD_PSTCD2 | CHAR | 10 | CHAR10 | ||||
| POSTL_COD_COMP | Company Postal Code (for Large Customers) | AD_PSTCD3 | CHAR | 10 | CHAR10 | ||||
| PO_BOX | PO Box | AD_POBX | CHAR | 10 | CHAR10 | ||||
| PO_BOX_CITY | PO Box city | AD_POBXLOC | CHAR | 40 | TEXT40 | CITY_NAME | |||
| PO_BOX_COUNTRY | PO box country | AD_POBXCTY | CHAR | 3 | Assigned to domain | LAND1 | |||
| STREET_PREFIX | Street 2 | AD_STRSPP1 | CHAR | 40 | TEXT40 | ||||
| STREET | Street | AD_STREET | CHAR | 60 | TEXT60 | CLSTRTNAME | |||
| STREET_SUFFIX | Street 4 | AD_STRSPP3 | CHAR | 40 | TEXT40 | ||||
| HOUSE_NUMBER | House Number | AD_HSNM1 | CHAR | 10 | TEXT10 | ||||
| BUILDING | Building (Number or Code) | AD_BLDNG | CHAR | 20 | TEXT20 | ||||
| FLOOR | Floor in building | AD_FLOOR | CHAR | 10 | TEXT10 | ||||
| ROOM_NUMBER | Room or Appartment Number | AD_ROOMNUM | CHAR | 10 | TEXT10 | ||||
| COUNTRY | Country ISO code | INTCA | CHAR | 2 | INTCA | F4_INTCA | |||
| TAX_JUR_CODE | Tax Jurisdiction | AD_TXJCD | CHAR | 15 | AD_TXJCD | TXJ | |||
| PHONE_NUMBER | Telephone no.: dialling code+number | AD_TLNMBR | CHAR | 30 | CHAR30 | ||||
| PHONE_EXTENS | Telephone no.: Extension | AD_TLXTNS | CHAR | 10 | CHAR10 | ||||
| FAX_NUMBER | Fax number: dialling code+number | AD_FXNMBR | CHAR | 30 | CHAR30 | ||||
| FAX_EXTENSION | Fax no.: Extension | AD_FXXTNS | CHAR | 10 | CHAR10 | ||||
| EMAIL_ADDRESS | E-Mail Address | AD_SMTPADR | CHAR | 241 | SXIDN | AD_SMTPADR | |||
| ATTACHMENT_URL | URL for Attachments in OPI Interface | BU_OPI_ATTACHMENT_URL | CHAR | 255 | CHAR255 | ||||
| ATTACHMENT_TITEL | Attachment Title | BU_OPI_ATTACHMENT_TITEL | CHAR | 255 | CHAR255 | ||||
| EXT_PARTNER_ID | Identification Number | BU_ID_NUMBER | CHAR | 60 | CHAR60 |
| Key field | Non-key field |
How do I retrieve data from SAP structure BUS_OPI using ABAP code?
As BUS_OPI 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 BUS_OPI as there is no data to select.How to access SAP table BUS_OPI
Within an ECC or HANA version of SAP you can also view further information about BUS_OPI 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