BBPS_BADI_PO_ACCOUNT_1 SAP (Account Assignment Fields for PO BAPI_PO_CREATE1) Structure details
Description: Account Assignment Fields for PO BAPI_PO_CREATE1
Related tables to BBPS_BADI_PO_ACCOUNT_1
Access table BBPS_BADI_PO_ACCOUNT_1
Structure field list including key, data, relationships and ABAP select examples
BBPS_BADI_PO_ACCOUNT_1 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 "Account Assignment Fields for PO BAPI_PO_CREATE1" 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_BADI_PO_ACCOUNT_1 TYPE BBPS_BADI_PO_ACCOUNT_1.
The BBPS_BADI_PO_ACCOUNT_1 table consists of various fields, each holding specific information or linking keys about Account Assignment Fields for PO BAPI_PO_CREATE1 data available in SAP. These include PO_ITEM (Item Number of Purchasing Document), SERIAL_NO (Sequential number of account assignment), DELETE_IND (Deletion indicator: Purchasing document account assignment), CREAT_DATE (Date on Which Record Was Created).. 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 (Deep)
SAP BBPS_BADI_PO_ACCOUNT_1 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 |
ACC_GUID | Globally Unique identifier | BBP_GUID | RAW | 16 | SYSUUID | ||||
PO_ITEM | Item Number of Purchasing Document | EBELP | NUMC | 5 | Assigned to domain | EBELP | BSP | ||
SERIAL_NO | Sequential number of account assignment | BBP_DZEKKN | NUMC | 2 | NUM02 | ||||
DELETE_IND | Deletion indicator: Purchasing document account assignment | BBP_KLOEK | CHAR | 1 | XFELD | ||||
CREAT_DATE | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
QUANTITY | Quantity | MENGE_D | QUAN | 13(3) | MENG13 | ||||
DISTR_PERC | Distribution Percentage in Case of Multiple Account Assgt | VPROZ | DEC | 3(1) | VPROZ | ||||
NET_VALUE | Currency amount for BAPIS (with 9 decimal places) | BAPICUREXT | DEC | 28(9) | BAPICUREXT | ||||
GL_ACCOUNT | G/L Account Number | SAKNR | CHAR | 10 | Assigned to domain | ALPHA | SAKNR | SAK | C_SAKNR |
BUS_AREA | Business Area | GSBER | CHAR | 4 | Assigned to domain | GSBER | GSB | ||
COSTCENTER | Cost Center | KOSTL | CHAR | 10 | Assigned to domain | ALPHA | KOSTL | KOS | |
SD_DOC | Sales and Distribution Document Number | VBELN | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
ITM_NUMBER | Sales Document Item | POSNR_VA | NUMC | 6 | Assigned to domain | POSNR | APO | ||
SCHED_LINE | Delivery Schedule Line Number | ETENR | NUMC | 4 | Assigned to domain | ETENR | |||
ASSET_NO | Main Asset Number | ANLN1 | CHAR | 12 | Assigned to domain | ALPHA | ANLN1 | AN1 | |
SUB_NUMBER | Asset Subnumber | ANLN2 | CHAR | 4 | Assigned to domain | ALPHA | ANLN2 | AN2 | |
ORDERID | Order Number | AUFNR | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | ANR | |
GR_RCPT | Goods Recipient/Ship-To Party | WEMPF | CHAR | 12 | WEMPF | ||||
UNLOAD_PT | Unloading Point | ABLAD | CHAR | 25 | TEXT25 | ||||
CO_AREA | Controlling Area | KOKRS | CHAR | 4 | Assigned to domain | CACCD | CAC | ||
COSTOBJECT | Cost Object | KSTRG | CHAR | 12 | Assigned to domain | KSTRG | KTR | ||
PROFIT_CTR | Profit Center | PRCTR | CHAR | 10 | Assigned to domain | ALPHA | PRCTR | PRC | PRCTR_EMPTY |
WBS_ELEMENT | Work Breakdown Structure Element (WBS Element) | PS_POSID | CHAR | 24 | PROJN | PS_POSID | PRO | ||
NETWORK | Network Number for Account Assignment | NPLNR | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | NET | |
RL_EST_KEY | Internal Key for Real Estate Object | IMKEY | CHAR | 8 | IMKEY | ||||
PART_ACCT | Partner account number | JV_PART | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | ||
CMMT_ITEM | Commitment Item | FIPOS | CHAR | 14 | Assigned to domain | FIPOS | FIP | ||
REC_IND | Recovery Indicator | JV_RECIND | CHAR | 2 | Assigned to domain | ALPHA | JV_RECIND | ||
FUNDS_CTR | Funds Center | FISTL | CHAR | 16 | Assigned to domain | FISTL | FIS | ||
FUND | Fund | BP_GEBER | CHAR | 10 | Assigned to domain | BP_GEBER | FIC | ||
FUNC_AREA | Functional Area | FKBER_SHORT | CHAR | 4 | FKBER_SHORT | FBE | |||
REF_DATE | Reference Date for Settlement | DABRBEZ | DATS | 8 | DDAT | ||||
TAX_CODE | Tax on sales/purchases code | MWSKZ | CHAR | 2 | Assigned to domain | MWSKZ | |||
TAXJURCODE | Tax Jurisdiction | TXJCD | CHAR | 15 | Assigned to domain | TXJCD | TXJ | ||
NOND_ITAX | Currency amount for BAPIS (with 9 decimal places) | BAPICUREXT | DEC | 28(9) | BAPICUREXT | ||||
ACTTYPE | Activity Type | LSTAR | CHAR | 6 | Assigned to domain | LSTAR | LAR | LART_EMPTY | |
CO_BUSPROC | Business Process | CO_PRZNR | CHAR | 12 | Assigned to domain | ALPHA | CO_PRZNR | KWP | |
RES_DOC | Document number for earmarked funds | BBP_KBLNR | CHAR | 10 | Assigned to domain | ALPHA | KBLNR | KBL | |
RES_ITEM | Earmarked Funds: Document Item | KBLPOS | NUMC | 3 | Assigned to domain | KBLPOS | KBP | ||
ACTIVITY | Operation/Activity Number | VORNR | CHAR | 4 | NUMCV | VORNR | VGN | ||
GRANT_NBR | Grant | GM_GRANT_NBR | CHAR | 20 | ALPHA | GM_GRANT_NBR | GM_GRANT_NBR | GRANTS_GENERIC | |
CMMT_ITEM_LONG | Commitment Item | FM_FIPEX | CHAR | 24 | Assigned to domain | FM_FIPEX | FPS | ||
FUNC_AREA_LONG | Functional Area | FKBER | CHAR | 16 | Assigned to domain | FKBER | FBE | ||
BUDGET_PERIOD | FM: Budget Period | FM_BUDGET_PERIOD | CHAR | 10 | Assigned to domain | FM_BUDGET_PERIOD | BUDPER |
Key field | Non-key field |
How do I retrieve data from SAP structure BBPS_BADI_PO_ACCOUNT_1 using ABAP code?
As BBPS_BADI_PO_ACCOUNT_1 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_BADI_PO_ACCOUNT_1 as there is no data to select.How to access SAP table BBPS_BADI_PO_ACCOUNT_1
Within an ECC or HANA version of SAP you can also view further information about BBPS_BADI_PO_ACCOUNT_1 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