PPC_SEND_CONF_DATA SAP (Posted Backflushes) Structure details
Description: Posted Backflushes
Related tables to PPC_SEND_CONF_DATA
Access table PPC_SEND_CONF_DATA
Structure field list including key, data, relationships and ABAP select examples
PPC_SEND_CONF_DATA 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 "Posted Backflushes" 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_PPC_SEND_CONF_DATA TYPE PPC_SEND_CONF_DATA.
The PPC_SEND_CONF_DATA table consists of various fields, each holding specific information or linking keys about Posted Backflushes data available in SAP. These include ASYNC_IND (Status of Asynchronous Material Posting), ACT_IND (Status of Activity Posting (Always Asynchronous)), MANDT (Client), HEADID (Internal backflush header key (GUID, format RAW16)).. 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 PPC_SEND_CONF_DATA 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 |
| SYNC_IND | Status of Synchronous Material Posting | PPC_SYNC_POSTED | CHAR | 1 | PPC_PROCESS_STATUS | ||||
| ASYNC_IND | Status of Asynchronous Material Posting | PPC_ASYNC_POSTED | CHAR | 1 | PPC_PROCESS_STATUS | ||||
| ACT_IND | Status of Activity Posting (Always Asynchronous) | PPC_ACT_POSTED | CHAR | 1 | PPC_PROCESS_STATUS | ||||
| MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| HEADID | Internal backflush header key (GUID, format RAW16) | PPC_HEADID_INT | RAW | 16 | SYSUUID | ||||
| ORDERID | Key (UID) for an order | PPC_ORDERID | CHAR | 22 | PPC_ORD_INF | SYSUUID_22 | |||
| ACCASSOBJ | Internal account assignment object (GUID 16 Byte) | PPC_ACCASSOBJ_INT | RAW | 16 | SYSUUID | ||||
| REPPOINT | Internal reporting point (GIUD 16 Byte) | PPC_REPPOINT_INT | RAW | 16 | Assigned to domain | SYSUUID | |||
| CONFTIME | Backflush data entry time | PPC_CONFTIME | DEC | 15 | TZNTSTMPS | ||||
| POSTDATE | Posting Date in the Document | BUDAT | DATS | 8 | DATUM | ||||
| CONFUNAME | Backflush Created by | PPC_CONFUNAME | CHAR | 12 | UNAME | ||||
| CONFLOGSYS | System for entering backflush data | PPC_CONFLOGSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
| CONFQUANT | Backflush Quantity - Header Material | PPC_HEADCONFQUANT | QUAN | 13(3) | MENG13 | ||||
| CONFUNIT | Unit of measure of backflushed quantity | PPC_CONFUNIT | UNIT | 3 | T006 | CUNIT | MEINS | ||
| KZBWS | Valuation of Special Stock | KZBWS | CHAR | 1 | KZBWS | ||||
| KDAUF | Sales Order Number | KDAUF | CHAR | 10 | VBUK | ALPHA | VBELN | AUN | |
| KDPOS | Item Number in Sales Order | KDPOS | NUMC | 6 | NUM06 | KPO | |||
| PSPNR | Work Breakdown Structure Element (WBS Element) | PS_PSP_PNR | NUMC | 8 | Assigned to domain | KONPR | PS_POSNR | ||
| FLG_SCRAP | Scrap indicator | PPC_FLG_SCRAP | CHAR | 1 | AS4FLAG | ||||
| FLG_DEL | Indicator: Backflush deleted | PPC_FLG_DEL | CHAR | 1 | AS4FLAG | ||||
| FLG_SYNCH | Status of Synchronous Material Posting | PPC_SYNC_POSTED | CHAR | 1 | PPC_PROCESS_STATUS | ||||
| FLG_ASYNCH | Status of Asynchronous Material Posting | PPC_ASYNC_POSTED | CHAR | 1 | PPC_PROCESS_STATUS | ||||
| FLG_REVERSAL | Reversal Backflush (Document-Neutral) | PPC_FLG_REV | CHAR | 1 | AS4FLAG | ||||
| FLG_GR_HEAD | Goods receipt for header material | PPC_FLG_GR_HEAD | CHAR | 1 | AS4FLAG | ||||
| FLG_INFO_DEST | Target system for subsequent processing | PPC_FLG_INFO_DEST | CHAR | 1 | PPC_FLG_INFO_DEST | ||||
| FLG_BW_GI | Transfer goods issues to BW | PPC_FLG_BW_GI | CHAR | 1 | PPC_BW_FLAG | ||||
| FLG_BW_CONF | Transfer backflushes to BW | PPC_FLG_BW_CONF | CHAR | 1 | PPC_BW_FLAG | ||||
| FLG_MAT_VAR | Variances Exist for the Component Withdrawal | PPC_FLG_MAT_VAR | CHAR | 1 | AS4FLAG | ||||
| FLG_ACT_VAR | Variances Exist for the Activity Consumption | PPC_FLG_ACT_VAR | CHAR | 1 | AS4FLAG | ||||
| FLG_ASYNCH_A | Status of Activity Posting (Always Asynchronous) | PPC_ACT_POSTED | CHAR | 1 | PPC_PROCESS_STATUS | ||||
| CRTIME | Backflush data entry time | PPC_CONFTIME | DEC | 15 | TZNTSTMPS |
| Key field | Non-key field |
How do I retrieve data from SAP structure PPC_SEND_CONF_DATA using ABAP code?
As PPC_SEND_CONF_DATA 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 PPC_SEND_CONF_DATA as there is no data to select.How to access SAP table PPC_SEND_CONF_DATA
Within an ECC or HANA version of SAP you can also view further information about PPC_SEND_CONF_DATA 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