SORSO SAP (SAPoffice: resubmission of a user (without MANDT)) Structure details
Description: SAPoffice: resubmission of a user (without MANDT)
Structure field list including key, data, relationships and ABAP select examples
SORSO 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 "SAPoffice: resubmission of a user (without MANDT)" 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_SORSO TYPE SORSO.
The SORSO table consists of various fields, each holding specific information or linking keys about SAPoffice: resubmission of a user (without MANDT) data available in SAP. These include OWNYR (Owner year from the ID), OWNNO (Owner number from the ID), OBJTP (Resubmission: Object type from ID), OBJYR (Resubmission: object year from the ID).. 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 SORSO 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 |
| OWNTP | Owner type from ID | SO_OWN_TP | CHAR | 3 | TSOTD | SO_OBJ_TP | |||
| OWNYR | Owner year from the ID | SO_OWN_YR | CHAR | 2 | SO_OBJ_YR | ||||
| OWNNO | Owner number from the ID | SO_OWN_NO | CHAR | 12 | Assigned to domain | SO_OBJ_NO | |||
| OBJTP | Resubmission: Object type from ID | SO_RSU_TP | CHAR | 3 | Assigned to domain | SO_OBJ_TP | |||
| OBJYR | Resubmission: object year from the ID | SO_RSU_YR | CHAR | 2 | SO_OBJ_YR | ||||
| OBJNO | Resubmission: object number from the ID | SO_RSU_NO | CHAR | 12 | Assigned to domain | SO_OBJ_NO | |||
| FORTP | Forwarder: Object type from ID | SO_FOR_TP | CHAR | 3 | TSOTD | SO_OBJ_TP | |||
| FORYR | Forwarder: year from the ID | SO_FOR_YR | CHAR | 2 | SO_OBJ_YR | ||||
| FORNO | Forwarder: number from the ID | SO_FOR_NO | CHAR | 12 | Assigned to domain | SO_OBJ_NO | |||
| RSCNT | Number of resubmissions for a document | SO_RSMCNT | NUMC | 2 | SO_COUNT1 | ||||
| RSDAT | Date On Which The Object Was Resubmitted | SO_DAT_RB | DATS | 8 | DATUM | ||||
| RSTIM | Resubmission: time | SO_TIM_RB | TIMS | 6 | UZEIT | ||||
| RSSPA | Intervals at which an object should be resubmitted | SO_RSSPA | NUMC | 2 | SO_COUNT1 | ||||
| RSFLG | Interpretation of the resubmission period (days/months) | SO_RSFLG | CHAR | 1 | SO_RSFU | ||||
| RSTIME | End of resubmission: time | SO_TIM_RBE | TIMS | 6 | UZEIT | ||||
| RSDATE | End of resubmission: date | SO_DAT_RBE | DATS | 8 | DATUM | ||||
| RSDAY | Day of resubmission (eg. every first Wednesday) | SO_RSDAY | CHAR | 1 | SO_RSFD | ||||
| ACINP | ToDo: status | SO_ACINP | CHAR | 4 | SO_TEXT004 | ||||
| OBJRD | Object has already been viewed | SO_OBJ_RD | CHAR | 1 | SO_FLAG | ||||
| OBJRS | The reply to this object has already been sent | SO_OBJ_RS | CHAR | 1 | SO_FLAG | ||||
| RSDATB | Start of resubmission: Date | SO_DAT_RBB | DATS | 8 | DATUM | ||||
| RSTIMB | Start of resubmission: time | SO_TIM_RBB | TIMS | 6 | UZEIT | ||||
| RSDATL | Lead time of the resubmission in days | SO_DAT_RSL | NUMC | 2 | SO_COUNT1 | ||||
| RSTIML | SAPoffice: lead time of resubmission in hours | SO_TIM_RSL | NUMC | 2 | SO_COUNT1 | ||||
| RSFLGL | SAPoffice: interpretation of lead time for the resubmission | SO_RSFLGL | CHAR | 1 | SO_RSFL | ||||
| CROTP | User who created object: Object type from ID | SO_CRO_TP | CHAR | 3 | TSOTD | SO_OBJ_TP | |||
| CROYR | User that created object: year from the ID | SO_CRO_YR | CHAR | 2 | SO_OBJ_YR | ||||
| CRONO | User that created object: number from the ID | SO_CRO_NO | CHAR | 12 | Assigned to domain | SO_OBJ_NO | |||
| CRODAT | Date created | SO_DAT_CR | DATS | 8 | DATUM | ||||
| CROTIM | Time created | SO_TIM_CR | TIMS | 6 | UZEIT | ||||
| CHOTP | User that changed the object: Object type from ID | SO_CHO_TP | CHAR | 3 | TSOTD | SO_OBJ_TP | |||
| CHOYR | User that changed the object: year from the ID | SO_CHO_YR | CHAR | 2 | SO_OBJ_YR | ||||
| CHONO | User that changed the object: number from the ID | SO_CHO_NO | CHAR | 12 | Assigned to domain | SO_OBJ_NO | |||
| CHODAT | Date of Last Change | SO_DAT_CH | DATS | 8 | DATUM | ||||
| CHOTIM | Time of Last Change | SO_TIM_CH | TIMS | 6 | UZEIT |
| Key field | Non-key field |
How do I retrieve data from SAP structure SORSO using ABAP code?
As SORSO 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 SORSO as there is no data to select.How to access SAP table SORSO
Within an ECC or HANA version of SAP you can also view further information about SORSO 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