POS_INBOUND SAP (POS interface monitor : inbound processing messages) Structure details
Description: POS interface monitor : inbound processing messages
Structure field list including key, data, relationships and ABAP select examples
POS_INBOUND 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 "POS interface monitor : inbound processing messages" 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_POS_INBOUND TYPE POS_INBOUND.
The POS_INBOUND table consists of various fields, each holding specific information or linking keys about POS interface monitor : inbound processing messages data available in SAP. These include MESTYP (Message Type), SNDPRN (Partner Number of Sender), CREDAT (Date status record was created), STATUS (Status of IDoc).. 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 (character-type)
SAP POS_INBOUND 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 |
| DOCNUM | IDoc number | EDI_DOCNUM | NUMC | 16 | EDI_DOCNUM | DCN | |||
| MESTYP | Message Type | EDI_MESTYP | CHAR | 30 | Assigned to domain | EDI_MESTYP | MES | ||
| SNDPRN | Partner Number of Sender | EDI_SNDPRN | CHAR | 10 | Assigned to domain | ALPHA | EDI_PARNUM | ||
| CREDAT | Date status record was created | EDI_CREDAT | DATS | 8 | DATUM | ||||
| STATUS | Status of IDoc | EDI_STATUS | CHAR | 2 | Assigned to domain | EDI_STATUS | |||
| FOLDOC_KEY1 | Object key | SWO_TYPEID | CHAR | 70 | SWO_TYPEID | ||||
| REFNR | External reference no. (GR/I slip) | POSREFNR | CHAR | 15 | CHAR15 | ||||
| KEY | 0 | ||||||||
| OBJTYPE | Object Type | SWO_OBJTYP | CHAR | 10 | Assigned to domain | OJ_NAME | OBJ | ||
| MESTYPNR | 0 | ||||||||
| SEGNUM | Number of SAP segment | EDI_SEGNUM | NUMC | 6 | EDI_NUMBER | ||||
| SEGNUM_END | Number of SAP segment | EDI_SEGNUM | NUMC | 6 | EDI_NUMBER | ||||
| POSTED | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure POS_INBOUND using ABAP code?
As POS_INBOUND 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 POS_INBOUND as there is no data to select.How to access SAP table POS_INBOUND
Within an ECC or HANA version of SAP you can also view further information about POS_INBOUND 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