PIATPCS_RET SAP (Sales Requirements After Backorder Processing (ATPCS_RET)) Structure details
Description: Sales Requirements After Backorder Processing (ATPCS_RET)
Structure field list including key, data, relationships and ABAP select examples
PIATPCS_RET 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 "Sales Requirements After Backorder Processing (ATPCS_RET)" 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_PIATPCS_RET TYPE PIATPCS_RET.
The PIATPCS_RET table consists of various fields, each holding specific information or linking keys about Sales Requirements After Backorder Processing (ATPCS_RET) data available in SAP. These include DELPS (MRP element item), DELET (Schedule Line Number MRP Element), XLINE (Line index for internal table processing), YLINE (Line index for internal table processing).. 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: Not classified
SAP PIATPCS_RET 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 |
DELNR | MRP element number | DELNR | CHAR | 10 | DELNR | ||||
DELPS | MRP element item | DELPS | NUMC | 6 | DELPS | ||||
DELET | Schedule Line Number MRP Element | DELET | NUMC | 4 | DELET | ||||
XLINE | Line index for internal table processing | XLINE | INT4 | 10 | XLINE | ||||
YLINE | Line index for internal table processing | XLINE | INT4 | 10 | XLINE | ||||
LOGQS | Business logical system | LOGQS | CHAR | 8 | LOGQS | ||||
LOGSYS | Logical system | LOGSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
ORDID | Internal number (GUID) for an order in APO | APOORDID | CHAR | 22 | SYSUUID_22 | ||||
TMPFLG | ATP: Temporary order number (ORDNUM) (y/n) | TMPFLG | CHAR | 1 | XFELD | ||||
POSGUID | ATP: Encryption of DELNR and DELPS | POSGUID | CHAR | 22 | SYSUUID_22 | ||||
BDMNG | Requirement Quantity | BDMNG | QUAN | 13(3) | MENG13 | ||||
VMENG | ATP Server: confirmed qty | BESTMNG | QUAN | 15(3) | MENGV15 | ||||
FIXMG | Delivery date and quantity fixed | FIXMG | CHAR | 1 | XFELD | ||||
APOREL | SAP Release | SAPRL | CHAR | 4 | SAPRL | ||||
ATPM1 | ATP Server: ATP quantity | ATPMNG | QUAN | 15(3) | MENGV15 | ||||
ATPMG | ATP Server: ATP quantity | ATPMNG | QUAN | 15(3) | MENGV15 | ||||
RPFLG | ATP Server: receipts in the past included | RPFLG | CHAR | 1 | XFELD | ||||
SYSIND | ATP: Indicator for system | SYSIND | CHAR | 1 | SYSIND | ||||
MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
WERKS | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
LOCNO | Location number in APO | APOLOCNO | CHAR | 20 | APOLOCNO | ||||
LOCTYPE | APO location type | APOLOCTYPE | CHAR | 4 | APOLOCTYPE | ||||
SOBKZ | Special Stock Indicator | SOBKZ | CHAR | 1 | Assigned to domain | SOBKZ | |||
KDAUF | Sales Order Number | KDAUF | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
KDPOS | Item Number in Sales Order | KDPOS | NUMC | 6 | NUM06 | KPO | |||
PSPEL | WBS Element | PS_POSNR | NUMC | 8 | Assigned to domain | ABPSP | PS_POSNR | ||
LGORT | Storage Location | LGORT_D | CHAR | 4 | Assigned to domain | LGORT | LAG | ||
CHARG | Batch Number | CHARG_D | CHAR | 10 | Assigned to domain | CHARG | CHA | ||
ERRKZ | ATP Server: Error flag | ERRORKZ | CHAR | 1 | XFELD | ||||
BDTER | Requirement Date for the Component | BDTER | DATS | 8 | DATUM | ||||
REMFLG | ATP: Remaining requirements (yes/no)? | RRFLG | CHAR | 1 | XFELD | ||||
SUREA | ATP: Substitution reason for rules-based ATP | SUREA | CHAR | 4 | SUREA | ||||
CHMOD | ATP: Check mode | CHMOD | CHAR | 3 | CHMOD | ||||
KOSCH | Product allocation determination procedure | KOSCH | CHAR | 18 | Assigned to domain | KOSCH | |||
PRREG | Checking Rule for Availability Check | PRREG | CHAR | 2 | Assigned to domain | PRREG | PRR | ||
TTYPE | Character Field Length = 10 | CHAR10 | CHAR | 10 | CHAR10 | ||||
PERSIST_ID | Character field, length 32 | CHAR32 | CHAR | 32 | CHAR32 | ||||
ACTIME | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 |
Key field | Non-key field |
How do I retrieve data from SAP structure PIATPCS_RET using ABAP code?
As PIATPCS_RET 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 PIATPCS_RET as there is no data to select.How to access SAP table PIATPCS_RET
Within an ECC or HANA version of SAP you can also view further information about PIATPCS_RET 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