BBPS_PO_HEADER_IC_PA_BADI SAP (Header Data Purchase Order (BBP_PGRP_ASSIGN_BADI)) Structure details
Description: Header Data Purchase Order (BBP_PGRP_ASSIGN_BADI)
Related tables to BBPS_PO_HEADER_IC_PA_BADI
Access table BBPS_PO_HEADER_IC_PA_BADI
Structure field list including key, data, relationships and ABAP select examples
BBPS_PO_HEADER_IC_PA_BADI 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 Purchase Order (BBP_PGRP_ASSIGN_BADI)" 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_BBPS_PO_HEADER_IC_PA_BADI TYPE BBPS_PO_HEADER_IC_PA_BADI.
The BBPS_PO_HEADER_IC_PA_BADI table consists of various fields, each holding specific information or linking keys about Header Data Purchase Order (BBP_PGRP_ASSIGN_BADI) data available in SAP. These include DESCRIPTION (Name of SRM Document), CURRENCY (Currency Key), PMNTTRMS (Terms of Payment Key), DSCNT1_TO (Cash discount days 1).. 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 BBPS_PO_HEADER_IC_PA_BADI 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 | ||||
CURRENCY | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
PMNTTRMS | Terms of Payment Key | DZTERM | CHAR | 4 | ZTERM | ||||
DSCNT1_TO | Cash discount days 1 | BBP_BDET1BAPI | DEC | 3 | ZBDXT | ||||
DSCNT2_TO | Cash discount days 2 | BBP_BDET2BAPI | DEC | 3 | ZBDXT | ||||
DSCNT3_TO | Cash discount days 3 | BBP_BDET3BAPI | DEC | 3 | ZBDXT | ||||
CASH_DISC1 | Cash Discount Percentage 1 | DZBD1P | DEC | 5(3) | PRZ23 | ||||
CASH_DISC2 | Cash Discount Percentage 2 | DZBD2P | DEC | 5(3) | PRZ23 | ||||
ERS | Evaluated Receipt Settlement (ERS) | BBP_XERSY | CHAR | 1 | XFELD | ||||
PCINS | Procurement card company | BBPPCINS | CHAR | 4 | Assigned to domain | BBPPCINS | PCI | ||
PCNUM | Procurement card number | BBPPCNUM | CHAR | 25 | Assigned to domain | BBPPCNUM | PCC | BBP_PCMAS | |
PCNAME | Name of procurement cardholder | BBPPCNAME | CHAR | 40 | CHAR40 | ||||
PCDAT_TO | Procurement Card Validity Date | BBPPCDAT_TO | DATS | 8 | DATUM | ||||
GR_IND | Goods Receipt Indicator | WEPOS | CHAR | 1 | XFELD | ||||
IR_IND | Invoice Receipt Indicator | REPOS | CHAR | 1 | XFELD | ||||
GR_BASEDIV | Indicator: GR-Based Invoice Verification | BBP_WEBRE | CHAR | 1 | XFELD | ||||
INCOTERM_KEY | Incoterm Key | BBP_INCOTERM_KEY | CHAR | 3 | Assigned to domain | BBP_INCOTERM_KEY | |||
INCOTERM_LOC | Incoterm Location | BBP_INCOTERM_LOCATION | CHAR | 28 | BBP_INCOTERM_LOCATION | ||||
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_REFOBJ_ITEM | Reference Object Item in Back-End System | BE_REFOBJ_ITEM | CHAR | 10 | BBP_REF_ITEM | ||||
APPROVAL_IND | Approval Indicator | BBP_APPROVAL_IND | CHAR | 1 | BBP_APPROVAL_IND | ||||
OR_IND | PO Response Expected (ORDER_RESP_EXP in Vendor Master) | BBP_OR_IND | CHAR | 1 | XFELD | ||||
ASN_IND | Shipping Notification Exptd (ASN_EXPECTED in Vendor Master) | BBP_ASN_IND | CHAR | 1 | XFELD | ||||
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 | |||
POSTING_DATE | Document Date (Posting Date of Log. Business Transaction) | BBP_POSTING_DATE | DATS | 8 | DATUM | ||||
CO_CODE | Company Code in FI System | BBP_CO_CODE | CHAR | 4 | Assigned to domain | BUKRS | |||
LOGSYS_FI | Logical System of FI System | BBP_LOGSYS_FI | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | BBP_BACKEND_DESTINATION_F4 | |
EXT_DEM_LOGSYS | Logical System from where an External Requirement Comes | BBP_EXT_DEM_LOGSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
SUBTYPE | Specification of a Purchasing Doc.(e.g. Credit Memo/Invoice) | BBP_H_SUBTYPE | CHAR | 2 | BBP_H_SUBTYPE |
Key field | Non-key field |
How do I retrieve data from SAP structure BBPS_PO_HEADER_IC_PA_BADI using ABAP code?
As BBPS_PO_HEADER_IC_PA_BADI 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 BBPS_PO_HEADER_IC_PA_BADI as there is no data to select.How to access SAP table BBPS_PO_HEADER_IC_PA_BADI
Within an ECC or HANA version of SAP you can also view further information about BBPS_PO_HEADER_IC_PA_BADI 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