SLS_SALES_ORDER_PROXY SAP (Structure SalesOrder for proxies) Structure details
Description: Structure SalesOrder for proxies
Related tables to SLS_SALES_ORDER_PROXY
Access table SLS_SALES_ORDER_PROXY
Structure field list including key, data, relationships and ABAP select examples
SLS_SALES_ORDER_PROXY 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 "Structure SalesOrder for proxies" 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_SLS_SALES_ORDER_PROXY TYPE SLS_SALES_ORDER_PROXY.
The SLS_SALES_ORDER_PROXY table consists of various fields, each holding specific information or linking keys about Structure SalesOrder for proxies data available in SAP. These include AUDAT (Document Date (Date Received/Sent)), AUART (Sales Document Type), AUGRU (Order reason (reason for the business transaction)), BSTKD (Customer purchase order number).. 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 SLS_SALES_ORDER_PROXY 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 |
| VBELN | Sales and Distribution Document Number | VBELN | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
| AUDAT | Document Date (Date Received/Sent) | AUDAT | DATS | 8 | DATUM | ||||
| AUART | Sales Document Type | AUART | CHAR | 4 | Assigned to domain | AUART | AUART | AAT | |
| AUGRU | Order reason (reason for the business transaction) | AUGRU | CHAR | 3 | Assigned to domain | AUGRU | |||
| BSTKD | Customer purchase order number | BSTKD | CHAR | 35 | BSTKD | ||||
| BSTDK | Customer purchase order date | BSTDK | DATS | 8 | DATUM | ||||
| LIFSK | Delivery block (document header) | LIFSK | CHAR | 2 | Assigned to domain | LIFSP | |||
| FAKSK | Billing block in SD document | FAKSK | CHAR | 2 | Assigned to domain | FAKSP | |||
| PARTY | 0 | ||||||||
| BUYER | Sold-to party | KUNAG | CHAR | 10 | ALPHA | KUNNR | VAG | ||
| BUYER_NAME | Name | NAME1 | CHAR | 30 | TEXT30 | ||||
| GOODS_RECIPIENT | Ship-to party | KUNWE | CHAR | 10 | ALPHA | KUNNR | |||
| GOODS_RECIPIENT_NAME | Name | NAME1 | CHAR | 30 | TEXT30 | ||||
| BILL_TO | Bill-to party | KUNRE | CHAR | 10 | ALPHA | KUNNR | KUN | ||
| BILL_TO_NAME | Name | NAME1 | CHAR | 30 | TEXT30 | ||||
| PAYER | Payer | KUNRG | CHAR | 10 | ALPHA | KUNNR | |||
| PAYER_NAME | Name | NAME1 | CHAR | 30 | TEXT30 | ||||
| RESP_EMPLOYEE | Customer Numbers | KUNNR | CHAR | 10 | ALPHA | KUNNR | KUN | C_KUNNR | |
| RESP_EMPLOYEE_NAME | Name | NAME1 | CHAR | 30 | TEXT30 | ||||
| SALES_ORGANISATION | Sales Organization | VKORG | CHAR | 4 | VKORG | VKO | C_VKORG | ||
| VTWEG | Distribution Channel | VTWEG | CHAR | 2 | Assigned to domain | VTWEG | VTW | C_VTWEG | |
| SPART | Division | SPART | CHAR | 2 | Assigned to domain | SPART | SPA | C_SPART | |
| KETDAT | Requested delivery date of the document | KETDAT | CHAR | 10 | ETDAT | ||||
| WAERK | SD Document Currency | WAERK | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
| PRSDT | Date for pricing and exchange rate | PRSDT | DATS | 8 | DATUM | ||||
| BTGEW | Total Weight | GSGEW | QUAN | 15(3) | MENG15 | ||||
| GEWEI | Weight Unit | GEWEI | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| NETWR | Net Value of the Sales Order in Document Currency | NETWR_AK | CURR | 15(2) | WERTV8 | ||||
| INCO1 | Incoterms (Part 1) | INCO1 | CHAR | 3 | Assigned to domain | INCO1 | |||
| INCO2 | Incoterms (Part 2) | INCO2 | CHAR | 28 | INCO2 | ||||
| AUTLF | Complete delivery defined for each sales order? | AUTLF | CHAR | 1 | XFELD | ||||
| FKDAT | Billing date for billing index and printout | FKDAT | DATS | 8 | DATUM | ||||
| ITEM | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure SLS_SALES_ORDER_PROXY using ABAP code?
As SLS_SALES_ORDER_PROXY 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 SLS_SALES_ORDER_PROXY as there is no data to select.How to access SAP table SLS_SALES_ORDER_PROXY
Within an ECC or HANA version of SAP you can also view further information about SLS_SALES_ORDER_PROXY 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