E1BPBUSISM007_SAPGP_PERSON SAP (IS-M: SAP BP: Personal Data (BAPIBUS1006_CENTRAL_PERSON)) IDoc segment structure details
Dictionary Type: IDoc segment structure
Description: IS-M: SAP BP: Personal Data (BAPIBUS1006_CENTRAL_PERSON)
Description: IS-M: SAP BP: Personal Data (BAPIBUS1006_CENTRAL_PERSON)
ABAP Code to SELECT data from E1BPBUSISM007_SAPGP_PERSON
Related tables to E1BPBUSISM007_SAPGP_PERSON
Access table E1BPBUSISM007_SAPGP_PERSON
Related tables to E1BPBUSISM007_SAPGP_PERSON
Access table E1BPBUSISM007_SAPGP_PERSON
IDoc segment structure field list including key, data, relationships and ABAP select examples
E1BPBUSISM007_SAPGP_PERSON is a standard SAP Structure which is used to define the field attributes of IDoc segment E1BPBUSISM007_SAPGP_PERSON. The segment is used within the below IDoc to send IS-M: SAP BP: Personal Data (BAPIBUS1006_CENTRAL_PERSON) information via the IDoc send process
ISMBPEX_SAVE01ISMBP_CHANGE01
ISMBP_CHANGE02
ISMBP_CREATE01
ISMBP_CREATE02
Below is the standard documentation available and a few details of the fields which make up this IDoc segment structure. To view further details checkout the IDoc links above or use relevant transactions such as WE30(IDoc development), WE31 (segment development)...Also check here for more IDoc related development help, or you can obviously also use standard dictionary object dev tcodes such as SE11, SE80 etc...
Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Not classified
SAP E1BPBUSISM007_SAPGP_PERSON idoc segment 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 |
| FIRSTNAME | 0 | ||||||||
| LASTNAME | 0 | ||||||||
| BIRTHNAME | 0 | ||||||||
| MIDDLENAME | 0 | ||||||||
| SECONDNAME | 0 | ||||||||
| TITLE_ACA1 | 0 | ||||||||
| TITLE_ACA2 | 0 | ||||||||
| TITLE_SPPL | 0 | ||||||||
| PREFIX1 | 0 | ||||||||
| PREFIX2 | 0 | ||||||||
| NICKNAME | 0 | ||||||||
| INITIALS | 0 | ||||||||
| NAMEFORMAT | 0 | ||||||||
| NAMCOUNTRY | 0 | ||||||||
| NAMCOUNTRYISO | 0 | ||||||||
| SEX | 0 | ||||||||
| BIRTHPLACE | 0 | ||||||||
| BIRTHDATE | 0 | ||||||||
| DEATHDATE | 0 | ||||||||
| MARITALSTATUS | 0 | ||||||||
| CORRESPONDLANGUAGE | 0 | ||||||||
| CORRESPONDLANGUAGEISO | 0 | ||||||||
| FULLNAME | 0 | ||||||||
| EMPLOYER | 0 | ||||||||
| OCCUPATION | 0 | ||||||||
| NATIONALITY | 0 | ||||||||
| NATIONALITYISO | 0 | ||||||||
| COUNTRYORIGIN | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure E1BPBUSISM007_SAPGP_PERSON using ABAP code?
As E1BPBUSISM007_SAPGP_PERSON 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 E1BPBUSISM007_SAPGP_PERSON as there is no data to select.How to access SAP table E1BPBUSISM007_SAPGP_PERSON
Within an ECC or HANA version of SAP you can also view further information about E1BPBUSISM007_SAPGP_PERSON 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