PKORD_OUT SAP (Orders for Kanban In-House Production) Structure details
Description: Orders for Kanban In-House Production
Structure field list including key, data, relationships and ABAP select examples
PKORD_OUT 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 "Orders for Kanban In-House Production" 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_PKORD_OUT TYPE PKORD_OUT.
The PKORD_OUT table consists of various fields, each holding specific information or linking keys about Orders for Kanban In-House Production data available in SAP. These include AUFNR (Order Number), WERKS (Plant), MATNR (Material Number), PRVBE (Production Supply Area).. 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 PKORD_OUT 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 |
MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
AUFNR | Order Number | AUFNR | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | ANR | |
WERKS | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
PRVBE | Production Supply Area | PRVBE | CHAR | 10 | Assigned to domain | PRVBE | PVB | ||
PKNUM | Control cycle number | PKNUM | CHAR | 7 | Assigned to domain | ALPHA | PKNUM | PKNUM | |
PKPOS | Kanban item number / control cycle item | PKPOS | NUMC | 3 | PKPOS | ||||
PKKEY | Identification Number | PKKEY | NUMC | 10 | Assigned to domain | PKKEY | |||
PKBST | Kanban status | PKBST | CHAR | 1 | PKBST | ||||
BHSKT | Short text - container status Kanban | BHSKT | CHAR | 6 | BHSKT | ||||
DISPO | MRP Controller (Materials Planner) | DISPO | CHAR | 3 | Assigned to domain | DISPO | DGR | HS_T024D | |
PLWRK | Planning Plant | PLWRK | CHAR | 4 | Assigned to domain | WERKS | WRK | ||
PWWRK | Production plant in planned order | PWWRK | CHAR | 4 | Assigned to domain | WERKS | |||
GSMNG | Total order quantity | GAMNG | QUAN | 13(3) | MENG13 | ||||
MEINS | Base Unit of Measure | MEINS | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
TRMKZ | Scheduling indicator | TRMFL | CHAR | 1 | XFELD | ||||
AUFFX | Firming indicator for planned order data | PLAFX | CHAR | 1 | XFELD | ||||
GSTRP | Basic start date | CO_GSTRP | DATS | 8 | DATUM | ||||
GLTRP | Basic finish date | CO_GLTRP | DATS | 8 | DATUM | ||||
GSTRI | Scheduled start | CO_GSTRS | DATS | 8 | DATUM | ||||
GSUPS | Scheduled start time (Forecast) | CO_GSUPS | TIMS | 6 | UHRZT | ||||
GSTRS | Scheduled finish | CO_GLTRS | DATS | 8 | DATUM | ||||
GLUPS | Scheduled forecast finish time | CO_GLUPS | TIMS | 6 | UHRZT | ||||
VERID | Production Version | VERID | CHAR | 4 | Assigned to domain | VERID | VER | ||
PLGRP | Production Supervisor | FEVOR | CHAR | 3 | Assigned to domain | FEVOR | CFV | ||
BERID | MRP Area | BERID | CHAR | 10 | Assigned to domain | BERID | BERID | ||
KUNNR | Sold-to party | KUNAG | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | VAG | |
NAME1 | Name 1 | NAME1_GP | CHAR | 35 | NAME | ||||
ORT01 | City | ORT01_GP | CHAR | 35 | TEXT35 | ||||
BSTDK | Customer purchase order date | BSTDK | DATS | 8 | DATUM | ||||
KDAUF | Sales Order Number | KDAUF | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
KDPOS | Item Number in Sales Order | KDPOS | NUMC | 6 | NUM06 | KPO | |||
PLAFF | Checkbox | XFELD | CHAR | 1 | XFELD |
Key field | Non-key field |
How do I retrieve data from SAP structure PKORD_OUT using ABAP code?
As PKORD_OUT 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 PKORD_OUT as there is no data to select.How to access SAP table PKORD_OUT
Within an ECC or HANA version of SAP you can also view further information about PKORD_OUT 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