BAPIBUS1006_ADSSF SAP (Business Partner: Address Data SSF) Structure details
Description: Business Partner: Address Data SSF
Related tables to BAPIBUS1006_ADSSF
Access table BAPIBUS1006_ADSSF
Structure field list including key, data, relationships and ABAP select examples
BAPIBUS1006_ADSSF 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 "Business Partner: Address Data SSF" 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_BAPIBUS1006_ADSSF TYPE BAPIBUS1006_ADSSF.
The BAPIBUS1006_ADSSF table consists of various fields, each holding specific information or linking keys about Business Partner: Address Data SSF data available in SAP. These include STD_NO (Standard Sender Address in this Communication Type), DUMMY (Single-Character Indicator), STD_RECIP (Flag: Recipient is standard recipient for this number), HOME_FLAG (Recipient address in this communication type (mail sys.grp)).. 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: Cannot Be Enhanced
SAP BAPIBUS1006_ADSSF 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 |
ADDRESS_GUID | UUID in character form | SYSUUID_C | CHAR | 32 | SYSUUID_C | ||||
STD_NO | Standard Sender Address in this Communication Type | AD_FLGDFNR | CHAR | 1 | XFELD | ||||
DUMMY | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
STD_RECIP | Flag: Recipient is standard recipient for this number | AD_DFTRCNR | CHAR | 1 | XFELD | ||||
HOME_FLAG | Recipient address in this communication type (mail sys.grp) | AD_FLGHOME | CHAR | 1 | XFELD | ||||
CONSNUMBER | Sequence Number | AD_CONSNUM | NUMC | 3 | NUMC3 | ||||
RFCDEST | Logical Destination (Specified in Function Call) | RFCDEST | CHAR | 32 | Assigned to domain | RFCDEST | RFC | F4_RFCDESTYPEALL | |
SSFIDSHORT | SSFID field for screen display | AD_SSFSCR | CHAR | 132 | AD_SSFSCR | ||||
SSF_NS | SSF Namespace label | SSFNS | CHAR | 10 | SSFNSD | ||||
SSF_PROF | SSF profile name | SSFPROF | CHAR | 132 | TEXT132 | ||||
SSFIDPART1 | SSF name signatory/recipient: Parts 1-8 | AD_SSFID_1 | CHAR | 250 | AD_SSFID_1 | ||||
SSFIDPART2 | SSF name signatory/recipient: Parts 1-8 | AD_SSFID_1 | CHAR | 250 | AD_SSFID_1 | ||||
SSFIDPART3 | SSF name signatory/recipient: Parts 1-8 | AD_SSFID_1 | CHAR | 250 | AD_SSFID_1 | ||||
SSFIDPART4 | SSF name signatory/recipient: Parts 1-8 | AD_SSFID_1 | CHAR | 250 | AD_SSFID_1 | ||||
SSFIDPART5 | SSF name signatory/recipient: Parts 1-8 | AD_SSFID_1 | CHAR | 250 | AD_SSFID_1 | ||||
SSFIDPART6 | SSF name signatory/recipient: Parts 1-8 | AD_SSFID_1 | CHAR | 250 | AD_SSFID_1 | ||||
SSFIDPART7 | SSF name signatory/recipient: Parts 1-8 | AD_SSFID_1 | CHAR | 250 | AD_SSFID_1 | ||||
SSFIDPART8 | SSF name signatory/recipient: Parts 1-8 | AD_SSFID_1 | CHAR | 250 | AD_SSFID_1 | ||||
SSFIDPART9 | SSF name signatory/recipient - part 9 | AD_SSFID_9 | CHAR | 48 | TEXT48 | ||||
ERRORFLAG | Flag: Record not processed | AD_ERRBAPI | CHAR | 1 | XFELD | ||||
FLG_NOUSE | Flag: This Communication Number is Not Used | AD_FLNOUSE | CHAR | 1 | XFELD | ||||
VALID_FROM | Communication Data: Valid From (YYYYMMDDHHMMSS) | AD_VALFROM | CHAR | 14 | TIMESTMP | ||||
VALID_TO | Communication Data: Valid To (YYYYMMDDHHMMSS) | AD_VALTO | CHAR | 14 | TIMESTAMP |
Key field | Non-key field |
How do I retrieve data from SAP structure BAPIBUS1006_ADSSF using ABAP code?
As BAPIBUS1006_ADSSF 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 BAPIBUS1006_ADSSF as there is no data to select.How to access SAP table BAPIBUS1006_ADSSF
Within an ECC or HANA version of SAP you can also view further information about BAPIBUS1006_ADSSF 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