RDM_S_API_ALLOC_CREATE SAP (API parameters for Allocation create) Structure details
Description: API parameters for Allocation create
Related tables to RDM_S_API_ALLOC_CREATE
Access table RDM_S_API_ALLOC_CREATE
Structure field list including key, data, relationships and ABAP select examples
RDM_S_API_ALLOC_CREATE 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 "API parameters for Allocation create" 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_RDM_S_API_ALLOC_CREATE TYPE RDM_S_API_ALLOC_CREATE.
The RDM_S_API_ALLOC_CREATE table consists of various fields, each holding specific information or linking keys about API parameters for Allocation create data available in SAP. These include MANDT (Client), ABELN (Allocation Table Number), AUFAR (Allocation Table Type), BEZCH (Description).. 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 RDM_S_API_ALLOC_CREATE 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 |
| HEADER | 0 | ||||||||
| MANDT | Client | MANDT | CLNT | 3 | MANDT | ||||
| ABELN | Allocation Table Number | ABELN | CHAR | 10 | ALPHA | ABELN | ABE | ||
| AUFAR | Allocation Table Type | AUFAR | CHAR | 4 | AUFAR | ATG | |||
| BEZCH | Description | BEZEI40 | CHAR | 40 | TEXT40 | ||||
| EKORG | Purchasing Organization | EKORG | CHAR | 4 | EKORG | EKO | |||
| EKGRP | Purchasing Group | EKGRP | CHAR | 3 | EKGRP | EKG | |||
| ASTAK | Activity status allocation tbl (header) | ASTAK | CHAR | 1 | ASTAK | ||||
| PSTAK | Maintenance status of allocation table | PSTAK | CHAR | 1 | PSTAK | ||||
| SPERR | Blocking flag: allocation table | SPKPF | CHAR | 1 | SPERR_A | ||||
| ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
| AEDAT | Changed On | AEDAT | DATS | 8 | DATUM | ||||
| ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| AENAM | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM | ||||
| LEPOS | Last item number | LEPOS | NUMC | 5 | ABELP | ||||
| PINCR | Item Number Interval | PINCR | NUMC | 5 | PINCR | ||||
| AFDAT | Confirmation request date | AFIDT | DATS | 8 | DATUM | ||||
| AFDTP | Date type (day, week, month, interval) | PRGRS | CHAR | 1 | PRGRS | ||||
| FBDAT | Release date of PO generation | FBIDT | DATS | 8 | DATUM | ||||
| FBDTP | Date type (day, week, month, interval) | PRGRS | CHAR | 1 | PRGRS | ||||
| FLDAT | Release date for generation of delivery note | FLIDT | DATS | 8 | DATUM | ||||
| FLDTP | Date type (day, week, month, interval) | PRGRS | CHAR | 1 | PRGRS | ||||
| FUDAT | Release date for generation of stock transfer | FUIDT | DATS | 8 | DATUM | ||||
| FUDTP | Date type (day, week, month, interval) | PRGRS | CHAR | 1 | PRGRS | ||||
| VKSDT | Date of start of sales at plant | VKIDT | DATS | 8 | DATUM | ||||
| VKSTP | Date type (day, week, month, interval) | PRGRS | CHAR | 1 | PRGRS | ||||
| RFCDEST | Logical Destination (Specified in Function Call) | RFCDEST | CHAR | 32 | RFCDEST | RFC | F4_RFCDESTYPEALL | ||
| ERVON | Application creating allocation table | ERVON | CHAR | 1 | ERVON | ||||
| ITEM | 0 | ||||||||
| PLANT | 0 | ||||||||
| DC | 0 | ||||||||
| PLANT_DP | 0 | ||||||||
| DC_DP | 0 | ||||||||
| MARKDOWN_REASON_CODE | Markdown Type of an External System | RDM_EXT_MARKDOWN_TYPE | CHAR | 4 | RDM_EXT_MARKDOWN_TYPE |
| Key field | Non-key field |
How do I retrieve data from SAP structure RDM_S_API_ALLOC_CREATE using ABAP code?
As RDM_S_API_ALLOC_CREATE 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 RDM_S_API_ALLOC_CREATE as there is no data to select.How to access SAP table RDM_S_API_ALLOC_CREATE
Within an ECC or HANA version of SAP you can also view further information about RDM_S_API_ALLOC_CREATE 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