ROS_S_COMPANY_SE_MAIL_STAGING SAP (Staging Structure for Company Self-Edit E-Mail Data) Structure details
Description: Staging Structure for Company Self-Edit E-Mail Data
Related tables to ROS_S_COMPANY_SE_MAIL_STAGING
Access table ROS_S_COMPANY_SE_MAIL_STAGING
Structure field list including key, data, relationships and ABAP select examples
ROS_S_COMPANY_SE_MAIL_STAGING 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 "Staging Structure for Company Self-Edit E-Mail Data" 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_ROS_S_COMPANY_SE_MAIL_STAGING TYPE ROS_S_COMPANY_SE_MAIL_STAGING.
The ROS_S_COMPANY_SE_MAIL_STAGING table consists of various fields, each holding specific information or linking keys about Staging Structure for Company Self-Edit E-Mail Data data available in SAP. These include PARTNER_ID (Business Partner Number), STD_NO (Standard Sender Address in this Communication Type), E_MAIL (E-Mail Address), EMAIL_SRCH (E-Mail Address Search Field).. 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 ROS_S_COMPANY_SE_MAIL_STAGING 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 |
| CLIENT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| PARTNER_ID | Business Partner Number | BU_PARTNER | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BPA | BUPA |
| STD_NO | Standard Sender Address in this Communication Type | AD_FLGDFNR | CHAR | 1 | XFELD | ||||
| E_MAIL | E-Mail Address | AD_SMTPADR | CHAR | 241 | SXIDN | AD_SMTPADR | |||
| EMAIL_SRCH | E-Mail Address Search Field | AD_SMTPAD2 | CHAR | 20 | CHAR20 | ||||
| STD_RECIP | Flag: Recipient is standard recipient for this number | AD_DFTRCNR | CHAR | 1 | XFELD | ||||
| R_3_USER | Flag: Connected to an SAP System | AD_R3_USER | CHAR | 1 | XFELD | ||||
| ENCODE | Desired Data Coding (E-Mail) | AD_ENCODE | CHAR | 1 | AD_ENCODE | ||||
| TNEF | Flag: Receiver can receive TNEF coding via SMTP | AD_TNEF6 | 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 | ||||
| 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 ROS_S_COMPANY_SE_MAIL_STAGING using ABAP code?
As ROS_S_COMPANY_SE_MAIL_STAGING 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 ROS_S_COMPANY_SE_MAIL_STAGING as there is no data to select.How to access SAP table ROS_S_COMPANY_SE_MAIL_STAGING
Within an ECC or HANA version of SAP you can also view further information about ROS_S_COMPANY_SE_MAIL_STAGING 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