CPO_SELLING_DOC_DATA_TYPE SAP (Create Collective PO: Communication Structure in Issue Doc.) Structure details
Description: Create Collective PO: Communication Structure in Issue Doc.
Related tables to CPO_SELLING_DOC_DATA_TYPE
Access table CPO_SELLING_DOC_DATA_TYPE
Structure field list including key, data, relationships and ABAP select examples
CPO_SELLING_DOC_DATA_TYPE 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 "Create Collective PO: Communication Structure in Issue Doc." 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_CPO_SELLING_DOC_DATA_TYPE TYPE CPO_SELLING_DOC_DATA_TYPE.
The CPO_SELLING_DOC_DATA_TYPE table consists of various fields, each holding specific information or linking keys about Create Collective PO: Communication Structure in Issue Doc. data available in SAP. These include BLNRA (Issue document number), BPOSA (Document item, issue), BETNA (Delivery Schedule Line Number), WERKA (Issuing plant).. 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 or numeric)
SAP CPO_SELLING_DOC_DATA_TYPE 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 |
| BTYPA | Category of issue document, Merchandise Distribution | BTYPA | CHAR | 1 | BELTV | ||||
| BLNRA | Issue document number | BLNRA | CHAR | 10 | ALPHA | BELNV | |||
| BPOSA | Document item, issue | BPOSA | NUMC | 6 | Assigned to domain | POSNR | |||
| BETNA | Delivery Schedule Line Number | ETENR | NUMC | 4 | Assigned to domain | ETENR | |||
| WERKA | Issuing plant | WERAB | CHAR | 4 | Assigned to domain | WERKS | |||
| MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
| MEINS | Base Unit of Measure | MEINS | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| PEINA | Unit of measure for planned quantity, issue | PEINA | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| UMREZ | Numerator for Conversion to Base Units of Measure | UMREZ | DEC | 5 | UMBSZ | ||||
| UMREN | Denominator for conversion to base units of measure | UMREN | DEC | 5 | UMBSN | ||||
| PMENA | Open quantity to be delivered (in sales unit) | OLFMNG | QUAN | 13(3) | MENG13 | ||||
| PMENA_B | Open Quantity to Be Delivered (in Base Unit of Measure) | OLFMNG_FLL | FLTP | 16(16) | FLTP | ||||
| EDTTS | Timestamp: Delivery Time for the PO to be Generated | CPO_EDTTS | DEC | 15 | TZNTSTMPS | ||||
| LFDTS | Timestamp: Delivery Creation Time | CPO_LFDTS | DEC | 15 | TZNTSTMPS | ||||
| EINTS | Timestamp: Delivery Time at Recipient | CPO_EINTS | DEC | 15 | TZNTSTMPS | ||||
| ABNNR | Number of recipient | NRABN | CHAR | 10 | ALPHA | ABNNR | |||
| LIFNR | Account Number of Vendor or Creditor | LIFNR | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | KRED_C |
| RESWK | Supplying (Issuing) Plant in Stock Transport Order | RESWK | CHAR | 4 | Assigned to domain | WERKS | |||
| UPTYP | Subitem Category, Purchasing Document | UPTYP | CHAR | 1 | Assigned to domain | UPTYP | |||
| UPVOR | Subitems Exist | UPVOR | CHAR | 1 | CHAR1 | ||||
| UEPOS | Higher-level item in bill of material structures | UEPOS | NUMC | 6 | Assigned to domain | POSNR | |||
| ADDNR | Document number for additional | ADDI_BELNR | CHAR | 10 | ALPHA | ADDI_BELNR | |||
| SATNR | Cross-Plant Configurable Material | SATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | ||
| ATTYP | Material Category | ATTYP | CHAR | 2 | ATTYP | MTY | |||
| KZ_NO_FRET | Boolian value: yes/no | FRM_FLAG | CHAR | 1 | FRM_FLAG | ||||
| SERVICE_DATA | SLS-related data | FRM_SERVICE_DATA | CHAR | 35 | |||||
| SORT_INDEX | Row Index of Internal Tables | SYTABIX | INT4 | 10 | SYST_LONG | ||||
| STATUS | Current Processing Status | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure CPO_SELLING_DOC_DATA_TYPE using ABAP code?
As CPO_SELLING_DOC_DATA_TYPE 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 CPO_SELLING_DOC_DATA_TYPE as there is no data to select.How to access SAP table CPO_SELLING_DOC_DATA_TYPE
Within an ECC or HANA version of SAP you can also view further information about CPO_SELLING_DOC_DATA_TYPE 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