FITP_USER_DATA SAP (User-Dependent Information) Structure details
Dictionary Type: Structure
Description: User-Dependent Information
Description: User-Dependent Information
ABAP Code to SELECT data from FITP_USER_DATA
Related tables to FITP_USER_DATA
Access table FITP_USER_DATA
Related tables to FITP_USER_DATA
Access table FITP_USER_DATA
Structure field list including key, data, relationships and ABAP select examples
FITP_USER_DATA 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 "User-Dependent Information" 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_FITP_USER_DATA TYPE FITP_USER_DATA.
The FITP_USER_DATA table consists of various fields, each holding specific information or linking keys about User-Dependent Information data available in SAP. These include BNAME (User Name in User Master Record), PERSNUMBER (Person number), ADDRNUMBER (Address number), SO_KEY (SAP-Office key).. 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: Not classified
SAP FITP_USER_DATA 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 |
| BNAME | User Name in User Master Record | XUBNAME | CHAR | 12 | Assigned to domain | XUBNAME | XUS | ||
| PERSNUMBER | Person number | AD_PERSNUM | CHAR | 10 | Assigned to domain | ALPHA | AD_PERSNUM | CDT | ADDRESS |
| ADDRNUMBER | Address number | AD_ADDRNUM | CHAR | 10 | Assigned to domain | ALPHA | AD_ADDRNUM | ADR | |
| SO_KEY | SAP-Office key | AD_SO_KEY | CHAR | 10 | ALPHA | AD_SO_KEY | ADDRESS | ||
| BUILDING_C | Building (number or code) | AD_BLDNG_P | CHAR | 10 | TEXT10 | ||||
| IH_MAIL | Int. mail postal code | AD_IH_MAIL | CHAR | 10 | TEXT10 | ||||
| NAMCOUNTRY | Country for name format rule | AD_NAMCTRY | CHAR | 3 | T005 | LAND1 | |||
| PERSORIGIN | Personal data source (key) | AD_ORIGINP | CHAR | 4 | TSAD6 | AD_ORIGIN | |||
| ADDR_COMP | (not used) | AD_ADDRCOM | CHAR | 10 | ADRC | ALPHA | AD_ADDRNUM | ||
| CITY_CODE | City code for city/street file | AD_CITYNUM | CHAR | 12 | ADRCITY | ALPHA | CITY_CODE | ||
| CITYP_CODE | District code for City and Street file | AD_CITYPNM | CHAR | 8 | ADRCITYPRT | ALPHA | CITYP_CODE | ||
| CITYH_CODE | Different city for city/street file | AD_CITYHNM | CHAR | 12 | ADRCITY | ALPHA | CITY_CODE | ||
| REGIOGROUP | Regional structure grouping | REGIOGROUP | CHAR | 8 | ADRREGGRP | REGIOGROUP | |||
| POST_CODE1 | City postal code | AD_PSTCD1 | CHAR | 10 | CHAR10 | ||||
| POST_CODE2 | PO Box Postal Code | AD_PSTCD2 | CHAR | 10 | CHAR10 | ||||
| POST_CODE3 | Company Postal Code (for Large Customers) | AD_PSTCD3 | CHAR | 10 | CHAR10 | ||||
| PCODE1_EXT | (Not Supported)City Postal Code Extension, e.g. ZIP+4+2 Code | AD_PST1XT | CHAR | 10 | CHAR10 | ||||
| PCODE2_EXT | (Not Supported) PO Box Postal Code Extension | AD_PST2XT | CHAR | 10 | CHAR10 | ||||
| PCODE3_EXT | (Not Supported) Major Customer Postal Code Extension | AD_PST3XT | CHAR | 10 | CHAR10 | ||||
| PO_BOX | PO Box | AD_POBX | CHAR | 10 | CHAR10 | ||||
| CITY_CODE2 | City PO box code (City file) | AD_CIT2NUM | CHAR | 12 | ADRCITY | ALPHA | CITY_CODE | ||
| PO_BOX_REG | Region for PO Box (Country, State, Province, ...) | AD_POBXREG | CHAR | 3 | T005S | REGIO | |||
| PO_BOX_CTY | PO box country | AD_POBXCTY | CHAR | 3 | T005 | LAND1 | |||
| POSTALAREA | (Not Supported) Post Delivery District | AD_PSTLAR | CHAR | 15 | TEXT15 | ||||
| TRANSPZONE | Transportation zone to or from which the goods are delivered | LZONE | CHAR | 10 | TZONE | ZONE | |||
| COUNTRY | Country Key | LAND1 | CHAR | 3 | T005 | LAND1 | LND | ||
| REGION | STATE (State, Province, County) | REGIO | CHAR | 3 | T005S | REGIO | |||
| ADDRORIGIN | (Not Supported) Address Data Source (Key) | AD_ORIGINA | CHAR | 4 | TSAD6 | AD_ORIGIN | |||
| TIME_ZONE | Address time zone | AD_TZONE | CHAR | 6 | TTZZ | TZNZONE | |||
| TAXJURCODE | Tax Jurisdiction | AD_TXJCD | CHAR | 15 | AD_TXJCD | TXJ | |||
| ADDRESS_ID | (Not supported) Physical address ID | AD_ADDR_ID | CHAR | 10 | ALPHA | AD_ADDR_ID | |||
| PERS_GROUP | Person Group (Key) (Business Address Services) | AD_GROUP_P | CHAR | 4 | Assigned to domain | AD_GROUP_P | |||
| ADDR_GROUP | Address Group (Key) (Business Address Services) | AD_GROUP | CHAR | 4 | Assigned to domain | AD_GROUP | |||
| USERG | User Grouping for Travel Planning | EMPLOYEE_GROUP_TP | CHAR | 2 | Assigned to domain | FTPD_EMPLOYEE_GROUP |
| Key field | Non-key field |
How do I retrieve data from SAP structure FITP_USER_DATA using ABAP code?
As FITP_USER_DATA 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 FITP_USER_DATA as there is no data to select.How to access SAP table FITP_USER_DATA
Within an ECC or HANA version of SAP you can also view further information about FITP_USER_DATA 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