BPOBREL_VDGPO SAP (Partner-Object Relationship: Extended VZGPO Structure) Structure details
Description: Partner-Object Relationship: Extended VZGPO Structure
Related tables to BPOBREL_VDGPO
Access table BPOBREL_VDGPO
Structure field list including key, data, relationships and ABAP select examples
BPOBREL_VDGPO 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 "Partner-Object Relationship: Extended VZGPO Structure" 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_BPOBREL_VDGPO TYPE BPOBREL_VDGPO.
The BPOBREL_VDGPO table consists of various fields, each holding specific information or linking keys about Partner-Object Relationship: Extended VZGPO Structure data available in SAP. These include ASSI_TYP (Assignment Category), ASSI_NR (Allocation Number), PARTNER (Business Partner Number), RLTYP (BP Role).. 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 BPOBREL_VDGPO 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 |
| ASSI_TYP | Assignment Category | BP_ASSI_TYP | CHAR | 6 | TPR1 | BP_ASSI_TYP | |||
| ASSI_NR | Allocation Number | BP_ASSI_NR | CHAR | 30 | BP_ASSI_NR | ||||
| PARTNER | Business Partner Number | BU_PARTNER | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BPA | BUPA |
| RLTYP | BP Role | BU_PARTNERROLE | CHAR | 6 | TB003 | BU_ROLE | BUPA_ROLE | ||
| TRDATE | Sequence of Partner-Object Relationships | BU_DTRANS | DATS | 8 | DATUM | ||||
| MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| SNUMOBJ | Key for number range object | VVNUMOBJ | CHAR | 2 | VVNUMOBJ | ||||
| SOBJEKT | Internal key for object for business partner table | VVSOBJGPO | CHAR | 13 | CHAR13 | ||||
| PARTNR | Business Partner Number | BP_PARTNR_NEW | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BPA | BUPA |
| ROLETYP | BP Role | BU_PARTNERROLE | CHAR | 6 | Assigned to domain | BU_ROLE | BUPA_ROLE | ||
| DTRANS | Flow data key: System date | VVDTRANS | DATS | 8 | DATUM | ||||
| DBEBEZ | Date of start of relationship | DBEBEZ | DATS | 8 | DATUM | ||||
| DENBEZ | Date of end of relationship | DENBEZ | DATS | 8 | DATUM | ||||
| APPL | Application Category | BP_APPL | CHAR | 4 | TPZ12 | BP_APPL | H_TPZ12 | ||
| ADR_REF | Address ID | BP_ADR_REF_NEW | CHAR | 10 | Assigned to domain | BU_ADRKIND | |||
| ROLE | CML Correspondence Role Type of Recipient | TB_ROLE_CORR | CHAR | 4 | TDPZ6 | T_ROLE_CORR | |||
| PBEZ | Percentage rate of relationship | PBEZ | DEC | 10(7) | DEC3_7 | ||||
| BBEZ | Relationship amount | BBEZ | CURR | 13(2) | WERTV7 | ||||
| SBBEZ | Currency Key | WAERS | CUKY | 5 | TCURC | WAERS | FWS | ||
| KUNNR | Customer Numbers | KUNNR | CHAR | 10 | KNA1 | ALPHA | KUNNR | KUN | C_KUNNR |
| GZLSCH | Payment method for credit memos | VVGZLSCH | CHAR | 1 | Assigned to domain | ZLSCH | |||
| BVTYP | Partner Bank Type | BVTYP | CHAR | 4 | BVTYP | ||||
| ZLSCH | Payment Method | DZLSCH | CHAR | 1 | Assigned to domain | ZLSCH | |||
| SDUNNDOC | Type of Dunning Letter | SDUNNDOC | CHAR | 1 | SDUNNDOC | ||||
| SDUNNBUC | Post Dunning Charges and Interest to This Partner | SDUNNBUC | CHAR | 1 | XFELD | ||||
| NORDER | Order Number | NORDER | NUMC | 8 | NUM8 | ORD | |||
| MNDID | Unique Referene to Mandate per Payment Recipient | SEPA_MNDID | CHAR | 35 | ID035 | ||||
| MABER | Dunning Area | MABER | CHAR | 2 | Assigned to domain | MABER | |||
| SDEBZUSA | Customer indicator | KZDEB | CHAR | 1 | XFELD | ||||
| KNRZE | Head office account number (in branch accounts) | KNRZE | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | ||
| SANTART | Type of share in an object in partner role | VVSANTART | NUMC | 2 | Assigned to domain | VVSANTART | |||
| XDEBFI | Customer transferred from FI | VVXDEBFI | CHAR | 1 | XFELD | ||||
| PAY_DATA_C | Change payment method or bank cat. | PAY_DATA_C | CHAR | 1 | XFELD | ||||
| LIFNR | Account Number of Vendor or Creditor | LIFNR | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | KRED_C |
| XPARTNER | Short name of business partner | BU_DESCRIP | CHAR | 50 | BU_TEXT50 | ||||
| VDGPONEW | Indicator New Entry VDGPO | KZVDGNEW | CHAR | 1 | XFELD |
| Key field | Non-key field |
How do I retrieve data from SAP structure BPOBREL_VDGPO using ABAP code?
As BPOBREL_VDGPO 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 BPOBREL_VDGPO as there is no data to select.How to access SAP table BPOBREL_VDGPO
Within an ECC or HANA version of SAP you can also view further information about BPOBREL_VDGPO 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