BUP_S_RELA_MODIFICATION_API SAP (BP-API: Changes - Relationship Addresses) Structure details
Dictionary Type: Structure
Description: BP-API: Changes - Relationship Addresses
Description: BP-API: Changes - Relationship Addresses
ABAP Code to SELECT data from BUP_S_RELA_MODIFICATION_API
Related tables to BUP_S_RELA_MODIFICATION_API
Access table BUP_S_RELA_MODIFICATION_API
Related tables to BUP_S_RELA_MODIFICATION_API
Access table BUP_S_RELA_MODIFICATION_API
Structure field list including key, data, relationships and ABAP select examples
BUP_S_RELA_MODIFICATION_API 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 "BP-API: Changes - Relationship Addresses" 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_BUP_S_RELA_MODIFICATION_API TYPE BUP_S_RELA_MODIFICATION_API.
The BUP_S_RELA_MODIFICATION_API table consists of various fields, each holding specific information or linking keys about BP-API: Changes - Relationship Addresses data available in SAP. These include PARTNER2_UUID (GUID of a Business Partner in CHAR 32 Format for BAPIs), CREATE_HANDLE (Handle for Creating a New Record), MOD_KEY (), PARTNER1 (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 BUP_S_RELA_MODIFICATION_API 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 |
| PARTNER1_UUID | GUID of a Business Partner in CHAR 32 Format for BAPIs | BU_PARTNER_GUID_BAPI | CHAR | 32 | SYSUUID_C | ||||
| PARTNER2_UUID | GUID of a Business Partner in CHAR 32 Format for BAPIs | BU_PARTNER_GUID_BAPI | CHAR | 32 | SYSUUID_C | ||||
| CREATE_HANDLE | Handle for Creating a New Record | BUP_CREATE_HANDLE | SSTR | 70 | |||||
| MOD_KEY | 0 | ||||||||
| PARTNER1 | Business Partner Number | BU_PARTNER | CHAR | 10 | ALPHA | BU_PARTNER | BPA | BUPA | |
| PARTNER2 | Business Partner Number | BU_PARTNER | CHAR | 10 | ALPHA | BU_PARTNER | BPA | BUPA | |
| ADDRNUMBER | Address number | AD_ADDRNUM | CHAR | 10 | Assigned to domain | ALPHA | AD_ADDRNUM | ADR | |
| RELDIR | BP Rel.: Detailed Indicator for Direction of a Relationship | BUP_RELDIR | CHAR | 1 | BUP_RELDIR | ||||
| ORG_ADDRESS_ID | Node Id as in the ESA-model | ADDR_NODE_ID | CHAR | 70 | ADDR_NODE_ID | ||||
| CHANGE_MODE | BP: Change Mode | BUP_CHANGE_MODE | CHAR | 1 | BUP_CHANGE_MODE | ||||
| MOD_DATA | 0 | ||||||||
| PARTNER1 | Business Partner Number | BU_PARTNER | CHAR | 10 | ALPHA | BU_PARTNER | BPA | BUPA | |
| PARTNER2 | Business Partner Number | BU_PARTNER | CHAR | 10 | ALPHA | BU_PARTNER | BPA | BUPA | |
| ADDRNUMBER | Address number | AD_ADDRNUM | CHAR | 10 | Assigned to domain | ALPHA | AD_ADDRNUM | ADR | |
| RELDIR | BP Rel.: Detailed Indicator for Direction of a Relationship | BUP_RELDIR | CHAR | 1 | BUP_RELDIR | ||||
| ORG_ADDRESS_ID | Node Id as in the ESA-model | ADDR_NODE_ID | CHAR | 70 | ADDR_NODE_ID | ||||
| CLIENT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| RELNR | BP Relationship Number | BU_RELNR | CHAR | 12 | Assigned to domain | ALPHA | BU_RELNR | ||
| DATE_TO | Validity Date (Valid To) | BU_DATTO | DATS | 8 | DATUM | ||||
| XDFADR | Indicator: Address is standard address | BU_XDFADR | CHAR | 1 | XFELD | ||||
| DATE_FROM | Valid-from date - in current Release only 00010101 possible | AD_DATE_FR | DATS | 8 | DATUM | ||||
| CHANGED_FIELDS | 0 | ||||||||
| WORKPLACE | 0 | ||||||||
| DEPARTMENT | Department | AD_DPRTMNT | CHAR | 40 | TEXT40 | ||||
| FUNCTION | Function | AD_FNCTN | CHAR | 40 | TEXT40 | ||||
| BUILDING | Building (number or code) | AD_BLDNG_P | CHAR | 10 | TEXT10 | ||||
| FLOOR | Floor in building | AD_FLOOR | CHAR | 10 | TEXT10 | ||||
| ROOMNUMBER | Room or Appartment Number | AD_ROOMNUM | CHAR | 10 | TEXT10 | ||||
| ID_CODE | Short name for correspondence | AD_ID_CODE | CHAR | 10 | TEXT10 | ||||
| IH_MAIL | Int. mail postal code | AD_IH_MAIL | CHAR | 10 | TEXT10 | ||||
| COMMUNICATION_PREFERENCE | 0 | ||||||||
| LANGU | Language Key | SPRAS | LANG | 1 | ISOLA | SPRAS | SPR | H_T002 | |
| DEFLT_COMM | Communication Method (Key) (Business Address Services) | AD_COMM | CHAR | 3 | AD_COMM | ||||
| CHANGE_MODE_BAS | Change operation code ('I'nsert, 'U'pdate, 'D'elete) | AD_OP_CODE | CHAR | 1 | AD_OP_CODE | ||||
| CHANGED_FIELDS_BAS | 0 | ||||||||
| COMMDATA | 0 | ||||||||
| TELEPHONE | 0 | ||||||||
| FACSIMILE | 0 | ||||||||
| 0 | |||||||||
| WEB | 0 | ||||||||
| TELEX | 0 | ||||||||
| TELETEX | 0 | ||||||||
| RML | 0 | ||||||||
| X400 | 0 | ||||||||
| PRINTER | 0 | ||||||||
| SSF | 0 | ||||||||
| PAGER | 0 | ||||||||
| CURRENT_STATE_COMMDATA | 0 | ||||||||
| CURRENT_STATE_TEL | Indicator: Ignore updateflags during update | ADDR_CURRENT_STATE | CHAR | 1 | ADDR_CURRENT_STATE | ||||
| CURRENT_STATE_FAX | Indicator: Ignore updateflags during update | ADDR_CURRENT_STATE | CHAR | 1 | ADDR_CURRENT_STATE | ||||
| CURRENT_STATE_EMAIL | Indicator: Ignore updateflags during update | ADDR_CURRENT_STATE | CHAR | 1 | ADDR_CURRENT_STATE | ||||
| CURRENT_STATE_WEB | Indicator: Ignore updateflags during update | ADDR_CURRENT_STATE | CHAR | 1 | ADDR_CURRENT_STATE | ||||
| CURRENT_STATE_TELEX | Indicator: Ignore updateflags during update | ADDR_CURRENT_STATE | CHAR | 1 | ADDR_CURRENT_STATE | ||||
| CURRENT_STATE_TELETEX | Indicator: Ignore updateflags during update | ADDR_CURRENT_STATE | CHAR | 1 | ADDR_CURRENT_STATE | ||||
| CURRENT_STATE_X400 | Indicator: Ignore updateflags during update | ADDR_CURRENT_STATE | CHAR | 1 | ADDR_CURRENT_STATE | ||||
| CURRENT_STATE_RML | Indicator: Ignore updateflags during update | ADDR_CURRENT_STATE | CHAR | 1 | ADDR_CURRENT_STATE | ||||
| CURRENT_STATE_PRINTER | Indicator: Ignore updateflags during update | ADDR_CURRENT_STATE | CHAR | 1 | ADDR_CURRENT_STATE | ||||
| CURRENT_STATE_SSF | Indicator: Ignore updateflags during update | ADDR_CURRENT_STATE | CHAR | 1 | ADDR_CURRENT_STATE | ||||
| CURRENT_STATE_PAGER | Indicator: Ignore updateflags during update | ADDR_CURRENT_STATE | CHAR | 1 | ADDR_CURRENT_STATE |
| Key field | Non-key field |
How do I retrieve data from SAP structure BUP_S_RELA_MODIFICATION_API using ABAP code?
As BUP_S_RELA_MODIFICATION_API 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 BUP_S_RELA_MODIFICATION_API as there is no data to select.How to access SAP table BUP_S_RELA_MODIFICATION_API
Within an ECC or HANA version of SAP you can also view further information about BUP_S_RELA_MODIFICATION_API 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