BBP_PDS_CONF_HEADER_IC SAP (Header Data Confirmation Create/Check-Case Interface) Structure details
Dictionary Type: Structure
Description: Header Data Confirmation Create/Check-Case Interface
Description: Header Data Confirmation Create/Check-Case Interface
ABAP Code to SELECT data from BBP_PDS_CONF_HEADER_IC
Related tables to BBP_PDS_CONF_HEADER_IC
Access table BBP_PDS_CONF_HEADER_IC
Related tables to BBP_PDS_CONF_HEADER_IC
Access table BBP_PDS_CONF_HEADER_IC
Structure field list including key, data, relationships and ABAP select examples
BBP_PDS_CONF_HEADER_IC 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 "Header Data Confirmation Create/Check-Case Interface" 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_BBP_PDS_CONF_HEADER_IC TYPE BBP_PDS_CONF_HEADER_IC.
The BBP_PDS_CONF_HEADER_IC table consists of various fields, each holding specific information or linking keys about Header Data Confirmation Create/Check-Case Interface data available in SAP. These include GUID (Globally Unique identifier), DESCRIPTION (Name of SRM Document), DESCR_LANGUAGE (Language Key of Description), POSTING_DATE (Document Date (Posting Date of Log. Business Transaction)).. 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 BBP_PDS_CONF_HEADER_IC 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 |
| GUID | Globally Unique identifier | BBP_GUID | RAW | 16 | SYSUUID | ||||
| DESCRIPTION | Name of SRM Document | BBP_DOCNAME | CHAR | 40 | TEXT40 | ||||
| DESCR_LANGUAGE | Language Key of Description | CRMT_PROCESS_DESCRIPTION_LANGU | LANG | 1 | Assigned to domain | ISOLA | SPRAS | ||
| POSTING_DATE | Document Date (Posting Date of Log. Business Transaction) | BBP_POSTING_DATE | DATS | 8 | DATUM | ||||
| POSTING_DATE_FI | Transaction Posting Date in Accounting | POSTING_DATE_FI | DATS | 8 | DATUM | ||||
| REF_DOC_NO | Number of the Reference Document | BBP_REF_DOC | CHAR | 16 | CHAR16 | ||||
| GR_GI_SLIP_NO | Goods receipt/issue slip number | BBP_GRGI_SLIP_NO | CHAR | 10 | ALPHA | BELNR | |||
| BILL_OF_LADING | Bill of Lading Number | BBP_BILL_OF_LADING | CHAR | 16 | XBLNR | ||||
| TOL_GROUP | Tolerance Group | BBP_TOL_GROUP | CHAR | 4 | CHAR4 | ||||
| WFL_CREATOR_TYPE | Type/Role of the Person who Starts the Approval Workflow | BBP_WFL_CREATOR_TYPE | CHAR | 1 | BBP_WFL_CREATOR_TYPE | ||||
| REASON_CODE | Reason for Rejection | BBP_PD_REASON | CHAR | 4 | CHAR4 | ||||
| APPROVAL_IND | Approval Indicator | BBP_APPROVAL_IND | CHAR | 1 | BBP_APPROVAL_IND | ||||
| BE_LOG_SYSTEM | Logical System of Logistics Backend | BE_LOG_SYSTEM | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
| BE_OBJECT_TYPE | Follow-On Document Object Type in Back-End System | BE_OBJECT_TYPE | CHAR | 10 | Assigned to domain | OJ_NAME | |||
| BE_OBJECT_ID | Follow-On Document Object ID in Back-End System | BE_OBJECT_ID | CHAR | 20 | BBP_BE_OBJECT_ID | ||||
| BE_REFOBJ_TYPE | Reference Object Type in Back-End System | BE_REFOBJ_TYPE | CHAR | 10 | Assigned to domain | OJ_NAME | |||
| BE_REFOBJ | Reference Object in Back-End System | BE_REFOBJ | CHAR | 20 | BBP_BE_OBJECT_ID | ||||
| BE_PUR_GROUP | Purchasing Group | EKGRP | CHAR | 3 | Assigned to domain | EKGRP | EKG | ||
| BE_REFOBJ_ITEM | Reference Object Item in Back-End System | BE_REFOBJ_ITEM | CHAR | 10 | BBP_REF_ITEM | ||||
| BE_PUR_GROUP | Purchasing Group | EKGRP | CHAR | 3 | Assigned to domain | EKGRP | EKG | ||
| BE_PUR_ORG | Purchasing Organization | EKORG | CHAR | 4 | Assigned to domain | EKORG | EKO | ||
| SK_COUNTRY | Country ISO code | INTCA | CHAR | 2 | INTCA | F4_INTCA | |||
| SK_SCENARIO1 | Key of a Scenario for Field Extension | BBP_CUF_SCENARIO_KEY | CHAR | 3 | BBP_CUF_SCENARIO_KEY | ||||
| SK_SCENARIO2 | Key of a Scenario for Field Extension | BBP_CUF_SCENARIO_KEY | CHAR | 3 | BBP_CUF_SCENARIO_KEY | ||||
| SK_SCENARIO3 | Key of a Scenario for Field Extension | BBP_CUF_SCENARIO_KEY | CHAR | 3 | BBP_CUF_SCENARIO_KEY | ||||
| SK_SCENARIO4 | Key of a Scenario for Field Extension | BBP_CUF_SCENARIO_KEY | CHAR | 3 | BBP_CUF_SCENARIO_KEY | ||||
| SK_SCENARIO5 | Key of a Scenario for Field Extension | BBP_CUF_SCENARIO_KEY | CHAR | 3 | BBP_CUF_SCENARIO_KEY | ||||
| DUMMY_EEW_PDHSS_CONF | Dummy function in length 1 | DUMMY | CHAR | 1 | DUMMY | ||||
| .INCLU--AP | 0 | ||||||||
| LAM_SOL_KEY | Solution Key | CUF_SOL_KEY | CHAR | 10 | Assigned to domain | BBP_CUF_SOL_KEY | |||
| LAM_HDR_GAID | External Allocation Number | LAM_ALLOCATION_ID | CHAR | 16 | CHAR16 | ||||
| LAM_HDR_TEXT | Text (length 35) | TEXT35 | CHAR | 35 | TEXT35 | ||||
| DUMMY_EEW_PDHSC_CONF | Dummy function in length 1 | DUMMY | CHAR | 1 | DUMMY | ||||
| COPY_OF_GUID | GUID Object is a Copy of | BBP_COPY_OF_GUID | RAW | 16 | SYSUUID | ||||
| PROCESS_TYPE | Business Transaction Type | CRMT_PROCESS_TYPE_DB | CHAR | 4 | Assigned to domain | CRM_PROCESS_TYPE | |||
| OBJECT_ID | Transaction Number | CRMT_OBJECT_ID_DB | CHAR | 10 | ALPHA | CRM_OBJECT_ID | |||
| INP_TYPE | Creation Indictaor (Dialog, XML and so on) | BBP_INP_TYPE | CHAR | 1 | BBP_INP_TYPE | ||||
| CURRENCY | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
| LOGSYS_FI | Logical System of FI System | BBP_LOGSYS_FI | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | BBP_BACKEND_DESTINATION_F4 | |
| CO_CODE | Company Code in FI System | BBP_CO_CODE | CHAR | 4 | Assigned to domain | BUKRS | |||
| SUBTYPE | Specification of a Purchasing Doc.(e.g. Credit Memo/Invoice) | BBP_H_SUBTYPE | CHAR | 2 | BBP_H_SUBTYPE | ||||
| REF_OBJECT_ID | Reference Transaction Number | BBP_REF_OBJECT_ID | CHAR | 10 | BBP_OBJECT_ID | ||||
| SRC_OBJECT_TYPE | Object Type of Reference Document | BBP_SRC_H_OBJ_TYP | CHAR | 10 | Assigned to domain | OJ_NAME | |||
| SRC_GUID | Reference Document GUID | BBP_SRC_H_GUID | RAW | 16 | SYSUUID | ||||
| PURCHTEAM | Team Purchasing: Purchasing Team | BBP_PURCHTEAM | CHAR | 8 | BBP_PURCHTEAM |
| Key field | Non-key field |
How do I retrieve data from SAP structure BBP_PDS_CONF_HEADER_IC using ABAP code?
As BBP_PDS_CONF_HEADER_IC 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 BBP_PDS_CONF_HEADER_IC as there is no data to select.How to access SAP table BBP_PDS_CONF_HEADER_IC
Within an ECC or HANA version of SAP you can also view further information about BBP_PDS_CONF_HEADER_IC 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