BPDACC1 SAP (Screen Structure: BP Account Correspondence Recipient (CoCd)) Structure details
Description: Screen Structure: BP Account Correspondence Recipient (CoCd)
Structure field list including key, data, relationships and ABAP select examples
BPDACC1 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 "Screen Structure: BP Account Correspondence Recipient (CoCd)" 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_BPDACC1 TYPE BPDACC1.
The BPDACC1 table consists of various fields, each holding specific information or linking keys about Screen Structure: BP Account Correspondence Recipient (CoCd) data available in SAP. These include PARTNR (Business Partner Number), BUKRS (Company Code), BUSAB (Accounting clerk), EIKTO (Shipper's (Our) Account Number at the Customer or Vendor).. 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)
SAP BPDACC1 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 |
MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
PARTNR | Business Partner Number | BP_PARTNR_OLD | CHAR | 10 | BP000 | ALPHA | BP_PARTNR | BPN | |
BUKRS | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
BUSAB | Accounting clerk | BUSAB | CHAR | 2 | T001S | BUSAB | |||
EIKTO | Shipper's (Our) Account Number at the Customer or Vendor | EIKTO | CHAR | 12 | CHAR12 | ||||
ZSABE | Accounting clerk at customer or vendor | DZSABE | CHAR | 15 | TEXT15 | ||||
KVERM | Memo | KVERM | CHAR | 30 | TEXT30 | ||||
PERKZ | Period Indicator | PERKZ | CHAR | 1 | PERKZ | PKZ | |||
XDEZV | Indicator: Local processing? | XDEZV | CHAR | 1 | XFELD | ||||
XAUSZ | Indicator for periodic account statements | XAUSZ | CHAR | 1 | T048K | AUSZG | |||
ZAMIM | Indicator: Payment notice to customer (with cleared items)? | DZAMIM | CHAR | 1 | XFELD | ||||
ZAMIV | Indicator: payment notice to sales department? | DZAMIV | CHAR | 1 | XFELD | ||||
ZAMIR | Indicator: payment notice to legal department? | DZAMIR | CHAR | 1 | XFELD | ||||
ZAMIB | Indicator: Payment notice to the accounting department ? | DZAMIB | CHAR | 1 | XFELD | ||||
ZAMIO | Indicator: payment notice to customer (w/o cleared items)? | DZAMIO | CHAR | 1 | XFELD |
Key field | Non-key field |
How do I retrieve data from SAP structure BPDACC1 using ABAP code?
As BPDACC1 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 BPDACC1 as there is no data to select.How to access SAP table BPDACC1
Within an ECC or HANA version of SAP you can also view further information about BPDACC1 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