PARTNER_ADDRESS_USAGE SAP (Data for Address Usage) Structure details
Description: Data for Address Usage
Related tables to PARTNER_ADDRESS_USAGE
Access table PARTNER_ADDRESS_USAGE
Structure field list including key, data, relationships and ABAP select examples
PARTNER_ADDRESS_USAGE 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 "Data for Address Usage" 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_PARTNER_ADDRESS_USAGE TYPE PARTNER_ADDRESS_USAGE.
The PARTNER_ADDRESS_USAGE table consists of various fields, each holding specific information or linking keys about Data for Address Usage data available in SAP. These include TASK_CODE (Change Indicator Role (I = Insert, D=Delete etc. )), ADDRESS_USAGE_DATA_KEY (), CONTROLLER (), ADDRESS_TYPE_CODE ().. 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 PARTNER_ADDRESS_USAGE 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 |
| CONTROLLER | 0 | ||||||||
| TASK_CODE | Change Indicator Role (I = Insert, D=Delete etc. ) | PARTY_TASK_CODE | CHAR | 1 | |||||
| ADDRESS_USAGE_DATA_KEY | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| ADDRESS_TYPE_CODE | 0 | ||||||||
| ADDRESS_USAGE_VALID_TO | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| UPDATE_INDICATOR | Indicator whether an element carries an updated value or not | UPDATE_INDICATOR | CHAR | 5 | |||||
| VALUE | Proxy Data Element (Generated) | GDT_DATE | DATS | 8 | |||||
| ADDRESS_USAGE_DATA | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| STANDARD_ADDRESS_INDICATOR | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| UPDATE_INDICATOR | Indicator whether an element carries an updated value or not | UPDATE_INDICATOR | CHAR | 5 | |||||
| VALUE | 0 | ||||||||
| ADDRESS_USAGE_VALID_FROM | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| UPDATE_INDICATOR | Indicator whether an element carries an updated value or not | UPDATE_INDICATOR | CHAR | 5 | |||||
| VALUE | Proxy Data Element (Generated) | GDT_DATE | DATS | 8 | |||||
| CURRENTLY_VALID | Proxy Data Element (generated) | PARTNER_CURRENTLY_VALID | CHAR | 1 |
| Key field | Non-key field |
How do I retrieve data from SAP structure PARTNER_ADDRESS_USAGE using ABAP code?
As PARTNER_ADDRESS_USAGE 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 PARTNER_ADDRESS_USAGE as there is no data to select.How to access SAP table PARTNER_ADDRESS_USAGE
Within an ECC or HANA version of SAP you can also view further information about PARTNER_ADDRESS_USAGE 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