BAPI_PO_HEADER_B SAP (Purchase Order Header Data Transfer to Backend) Structure details
Description: Purchase Order Header Data Transfer to Backend
Related tables to BAPI_PO_HEADER_B
Access table BAPI_PO_HEADER_B
Structure field list including key, data, relationships and ABAP select examples
BAPI_PO_HEADER_B 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 "Purchase Order Header Data Transfer to Backend" 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_BAPI_PO_HEADER_B TYPE BAPI_PO_HEADER_B.
The BAPI_PO_HEADER_B table consists of various fields, each holding specific information or linking keys about Purchase Order Header Data Transfer to Backend data available in SAP. These include PROCESS_TYPE (Business Transaction Type), DOC_NUMBER (Document Number), DOC_DATE (Document Date), DESCRIPTION (Purchase Order Description).. 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 BAPI_PO_HEADER_B 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 |
| BUSINESSPROCESS | Technical Key of Business Transaction (Char32-GUID) | BAPI_BUSINESSPROCESS | CHAR | 32 | SYSUUID_C | ||||
| PROCESS_TYPE | Business Transaction Type | CRMT_PROCESS_TYPE_DB | CHAR | 4 | Assigned to domain | CRM_PROCESS_TYPE | |||
| DOC_NUMBER | Document Number | BBP_DOC_NUMBER | CHAR | 10 | ALPHA | CRM_OBJECT_ID | |||
| DOC_DATE | Document Date | BBP_DOC_DATE | DATS | 8 | DATUM | ||||
| DESCRIPTION | Purchase Order Description | BBP_PO_DESCRIPTION | CHAR | 40 | CRM_PROCESS_DESCRIPTION | ||||
| LOGICAL_SYSTEM | Logical System | CRMT_LOGSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
| LOGSYS_FI | Logical System of FI System | BBP_LOGSYS_FI | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | BBP_BACKEND_DESTINATION_F4 | |
| CURRENCY | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
| CURRENCY_ISO | ISO Currency Code | BBP_ISOCD | CHAR | 3 | ISOCD | ||||
| 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 | ||||
| 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 | ||||
| CO_CODE | Company Code in FI System | BBP_CO_CODE | CHAR | 4 | Assigned to domain | BUKRS | |||
| VPER_START | Timeframe From | BBP_VPER_START | DATS | 8 | DATUM | ||||
| VPER_END | Timeframe To | BBP_VPER_END | DATS | 8 | DATUM | ||||
| CREATED_BY | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| CREATED_AT | Creation Date of Document | BAPI_CREATED_AT | DATS | 8 | DATUM | ||||
| CHANGED_BY | Name of Person Responsible for Changing Object | BBP_CHNAM | CHAR | 12 | USNAM | ||||
| CHANGED_AT | Date of Last Change to Document | BAPI_CHANGED_AT | DATS | 8 | DATUM | ||||
| EXT_DEM_LOGSYS | Logical System from where an External Requirement Comes | BBP_EXT_DEM_LOGSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
| LANGU_ISO | 2-Character SAP Language Code | LAISO | CHAR | 2 | LAISO | ||||
| BE_VENDOR_ID | Supplier Number | BBPELIFN_PI | CHAR | 10 | ALPHA | BBPELIFN_PI |
| Key field | Non-key field |
How do I retrieve data from SAP structure BAPI_PO_HEADER_B using ABAP code?
As BAPI_PO_HEADER_B 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 BAPI_PO_HEADER_B as there is no data to select.How to access SAP table BAPI_PO_HEADER_B
Within an ECC or HANA version of SAP you can also view further information about BAPI_PO_HEADER_B 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