SLDOC_ATP SAP (ATP: APO Interface with SD Documents) Structure details
Description: ATP: APO Interface with SD Documents
Structure field list including key, data, relationships and ABAP select examples
SLDOC_ATP 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 "ATP: APO Interface with SD Documents" 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_SLDOC_ATP TYPE SLDOC_ATP.
The SLDOC_ATP table consists of various fields, each holding specific information or linking keys about ATP: APO Interface with SD Documents data available in SAP. These include ATPCAT (ATP: Category of Stock / Receipts / Issues), DOC_NUMBER (Sales and Distribution Document Number), DOC_TYPE (SD document category), ORD_TYPE (Sales Document Type).. 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 SLDOC_ATP 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 |
METHOD | APO: Methods (add/change/delete...) | SL_METHOD_ATP | CHAR | 1 | CHAR1 | ||||
ATPCAT | ATP: Category of Stock / Receipts / Issues | ATPCAT | CHAR | 2 | ATPCAT | ||||
DOC_NUMBER | Sales and Distribution Document Number | VBELN | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
DOC_TYPE | SD document category | VBTYP | CHAR | 1 | VBTYP | ||||
ORD_TYPE | Sales Document Type | AUART | CHAR | 4 | Assigned to domain | AUART | AUART | AAT | |
SALES_ORG | Sales Organization | VKORG | CHAR | 4 | Assigned to domain | VKORG | VKO | C_VKORG | |
DIVISION | Division | SPART | CHAR | 2 | Assigned to domain | SPART | SPA | C_SPART | |
DISTR_CHAN | Distribution Channel | VTWEG | CHAR | 2 | Assigned to domain | VTWEG | VTW | C_VTWEG | |
SLSOFF | Sales Office | VKBUR | CHAR | 4 | Assigned to domain | VKBUR | VKB | ||
SLSGRP | Sales Group | VKGRP | CHAR | 3 | Assigned to domain | VKGRP | VKG | ||
SOLD_TO | Sold-to party with length 20 for APO | KUNAG_20 | CHAR | 20 | CHAR20 | ||||
COMPL_DLV | Complete delivery defined for each sales order? | AUTLF | CHAR | 1 | XFELD | ||||
ITM_NUMBER | Item number of the SD document | POSNR | NUMC | 6 | Assigned to domain | POSNR | |||
ITEM_CATEG | Sales document item category | PSTYV | CHAR | 4 | Assigned to domain | PSTYV | |||
RBACONTROL | Control of Rules-Based ATP Check | RBACONTROL | CHAR | 1 | RBACONTROL | ||||
CREATOR | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
PRODUCT | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
LOCATION | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
STORE_LOC | Storage Location | LGORT_D | CHAR | 4 | Assigned to domain | LGORT | LAG | ||
BATCH | Batch Number | CHARG_D | CHAR | 10 | Assigned to domain | CHARG | CHA | ||
SHIP_TO | Sold-to party with length 20 for APO | KUNAG_20 | CHAR | 20 | CHAR20 | ||||
SHIP_POINT | Shipping Point/Receiving Point | VSTEL | CHAR | 4 | Assigned to domain | VSTEL | VST | ||
ROUTE | Route | ROUTE | CHAR | 6 | Assigned to domain | ROUTE | |||
SHP_COND | Shipping Conditions | VSBED | CHAR | 2 | Assigned to domain | VSBED | |||
DLV_PRIO | Delivery Priority | LPRIO | NUMC | 2 | Assigned to domain | LPRIO | |||
PART_DLV | Partial delivery at item level | KZTLF | CHAR | 1 | KZTLF | ||||
MAX_PL_DLV | Maximum Number of Partial Deliveries Allowed Per Item | ANTLF | DEC | 1 | ANTLF | ||||
ALLOC | Product allocation determination procedure | KOSCH | CHAR | 18 | Assigned to domain | KOSCH | |||
LOGSYS | Logical system | LOGSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
BSTNK | Customer purchase order number | BSTNK | CHAR | 20 | BSTNK | ||||
POSNR | Item number of the SD document | POSNR | NUMC | 6 | Assigned to domain | POSNR | |||
LOCTYPE | Type of Executing Location | ELOCTYPE | CHAR | 4 | LOCTYP | ||||
ITEM_TYPE_USAGE | Item usage | VWPOS | CHAR | 4 | Assigned to domain | VWPOS | |||
ITM_ANCHOR | Leading Order Item (Main Item) | ITM_ANCHOR | NUMC | 6 | Assigned to domain | POSNR | |||
OVERRIDE_LOCATION | External Location Identifier | EXT_LOCNO | CHAR | 20 | LOCNR | ||||
OVERRIDE_LOCTYPE | Location Type | EXT_LOCTYP | CHAR | 4 | LOCTYP |
Key field | Non-key field |
How do I retrieve data from SAP structure SLDOC_ATP using ABAP code?
As SLDOC_ATP 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 SLDOC_ATP as there is no data to select.How to access SAP table SLDOC_ATP
Within an ECC or HANA version of SAP you can also view further information about SLDOC_ATP 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