RJKSDDEMANDCOPY SAP (IS-M: Structure for Quantity Update in Quantity Planning) Structure details
Description: IS-M: Structure for Quantity Update in Quantity Planning
Related tables to RJKSDDEMANDCOPY
Access table RJKSDDEMANDCOPY
Structure field list including key, data, relationships and ABAP select examples
RJKSDDEMANDCOPY 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 "IS-M: Structure for Quantity Update in Quantity Planning" 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_RJKSDDEMANDCOPY TYPE RJKSDDEMANDCOPY.
The RJKSDDEMANDCOPY table consists of various fields, each holding specific information or linking keys about IS-M: Structure for Quantity Update in Quantity Planning data available in SAP. These include SOURCE_DATE_FROM (IS-M: Start of Selection Period), SOURCE_ISSUE_TO (IS-M: End of Selection Period (in Issue Numbers)), SOURCE_DATE_TO (IS-M: End of Selection Period), TARGET_ISSUE_FROM (IS-M: Start of Selection Period (in Issue Numbers)).. 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 RJKSDDEMANDCOPY 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 |
SOURCE_ISSUE_FROM | IS-M: Start of Selection Period (in Issue Numbers) | JISSUE_FROM | CHAR | 18 | Assigned to domain | MATN1 | MATNR | ||
SOURCE_DATE_FROM | IS-M: Start of Selection Period | JDATE_FROM | DATS | 8 | DATUM | ||||
SOURCE_ISSUE_TO | IS-M: End of Selection Period (in Issue Numbers) | JISSUE_TO | CHAR | 18 | Assigned to domain | MATN1 | MATNR | ||
SOURCE_DATE_TO | IS-M: End of Selection Period | JDATE_TO | DATS | 8 | DATUM | ||||
TARGET_ISSUE_FROM | IS-M: Start of Selection Period (in Issue Numbers) | JISSUE_FROM | CHAR | 18 | Assigned to domain | MATN1 | MATNR | ||
TARGET_DATE_FROM | IS-M: Start of Selection Period | JDATE_FROM | DATS | 8 | DATUM | ||||
TARGET_ISSUE_TO | IS-M: End of Selection Period (in Issue Numbers) | JISSUE_TO | CHAR | 18 | Assigned to domain | MATN1 | MATNR | ||
TARGET_DATE_TO | IS-M: End of Selection Period | JDATE_TO | DATS | 8 | DATUM |
Key field | Non-key field |
How do I retrieve data from SAP structure RJKSDDEMANDCOPY using ABAP code?
As RJKSDDEMANDCOPY 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 RJKSDDEMANDCOPY as there is no data to select.How to access SAP table RJKSDDEMANDCOPY
Within an ECC or HANA version of SAP you can also view further information about RJKSDDEMANDCOPY 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