CRMT_COMPL_BEA_HEADER SAP (Billing Doc. Header Data (BE): Wrapper /1BEA/S_CRMB_BDH_WRK) Structure details
Description: Billing Doc. Header Data (BE): Wrapper /1BEA/S_CRMB_BDH_WRK
Related tables to CRMT_COMPL_BEA_HEADER
Access table CRMT_COMPL_BEA_HEADER
Structure field list including key, data, relationships and ABAP select examples
CRMT_COMPL_BEA_HEADER 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 "Billing Doc. Header Data (BE): Wrapper /1BEA/S_CRMB_BDH_WRK" 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_CRMT_COMPL_BEA_HEADER TYPE CRMT_COMPL_BEA_HEADER.
The CRMT_COMPL_BEA_HEADER table consists of various fields, each holding specific information or linking keys about Billing Doc. Header Data (BE): Wrapper /1BEA/S_CRMB_BDH_WRK data available in SAP. These include BDH_GUID (Unique Internal ID of a Billing Header), HEADNO_EXT (Billing Document), OBJTYPE (Object Type), LOGSYS (Logical system).. 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 CRMT_COMPL_BEA_HEADER 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 |
CLIENT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
BDH_GUID | Unique Internal ID of a Billing Header | BEA_BDH_GUID | RAW | 16 | SYSUUID | ||||
HEADNO_EXT | Billing Document | BEA_HEADNO_EXT | CHAR | 10 | ALPHA | BEA_HEADNO_EXT | BEA_HEADNO_EXT | ||
OBJTYPE | Object Type | BEA_OBJTYPE | CHAR | 10 | BEA_OBJTYPE | ||||
LOGSYS | Logical system | LOGSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
MWC_ERROR | Middleware Connection Errors | BEA_MWC_ERROR | CHAR | 1 | BEA_MWC_ERROR | ||||
PARSET_GUID | Partner Set GUID; GUID Fld.in CRMD_PARTNER(CRMT_OBJECT_GUID) | BEA_PARSET_GUID | RAW | 16 | SYSUUID | ||||
PRICING_ERROR | Pricing Status | BEA_PRICING_ERROR | CHAR | 1 | BEA_PRICING_ERROR | ||||
PRIDOC_GUID | ID of Pricing Document | BEA_PRIDOC_GUID | RAW | 16 | SYSUUID | ||||
TEXT_ERROR | Text Processing Status | BEA_TEXT_ERROR | CHAR | 1 | BEA_TEXT_ERROR | ||||
TRANSFER_ERROR | Accounting Transfer Status | BEA_TRANSFER_ERROR | CHAR | 1 | BEA_TRANSFER_ERROR | ||||
BILL_TYPE | Billing Type | BEA_BILL_TYPE | CHAR | 4 | Assigned to domain | BEA_BILL_TYPE | BEAC_BTY | ||
BILL_CATEGORY | Billing Document Category | BEA_BILL_CATEGORY | CHAR | 1 | Assigned to domain | BEA_BILL_CATEGORY | BEAC_BCA | ||
CANCEL_FLAG | Indicator: Cancellation Document | BEA_CANCEL_FLAG | CHAR | 1 | BEA_CANCEL_FLAG | ||||
PRIC_PROC | Pricing Procedure | BEA_PRIC_PROC | CHAR | 6 | Assigned to domain | PRC_PRIC_PROC | |||
CRP_GUID | Collective Run GUID | BEA_CRP_GUID | RAW | 16 | SYSUUID | ||||
BILL_ORG | Billing Unit | BEA_BILL_ORG | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BPA | BEAC_BILL_ORG |
TRANSFER_STATUS | Billing Status | BEA_TRANSFER_STATUS | CHAR | 1 | BEA_TRANSFER_STATUS | ||||
ARCHIVABLE | Indicator: Document is Archivable | BEA_ARCHIVABLE | CHAR | 1 | BEA_ARCHIVABLE | ||||
DOC_CURRENCY | Document Currency | BEA_DOC_CURRENCY | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
REF_CURRENCY | Reference Currency | BEA_REF_CURRENCY | CUKY | 5 | Assigned to domain | WAERS | |||
NET_VALUE | Net Value in Document Currency | BEA_NET_VALUE | CURR | 15(2) | WERTV8 | ||||
PAYER | Payer | BEA_PAYER | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BUPA | |
TERMS_OF_PAYMENT | Terms of Payment | BEA_TERMS_OF_PAYMENT | CHAR | 4 | Assigned to domain | CRM_PMNTTRMS | |||
BILL_DATE | Billing Date | BEA_BILL_DATE | DATS | 8 | SYDATS | ||||
TRANSFER_DATE | Value Date | BEA_TRANSFER_DATE | DATS | 8 | SYDATS | ||||
REFERENCE_NO | Reference Number | BEA_REFERENCE_NO | CHAR | 30 | CHAR30 | ||||
TAX_VALUE | Tax Amount in Document Currency | BEA_TAX_VALUE | CURR | 15(2) | WERTV8 | ||||
SPLIT_CRITERIA | Splitting Criterion | BEA_SPLIT_CRITERIA | CHAR | 32 | BEA_SPLIT_CRITERIA | ||||
MAINT_DATE | Processing Date | BEA_MAINT_DATE | DATS | 8 | SYDATS | ||||
MAINT_TIME | Processing Time | BEA_MAINT_TIME | TIMS | 6 | SYTIME | ||||
MAINT_USER | Created/Last Changed By | BEA_MAINT_USER | CHAR | 12 | USERNAME | USER_ADDR | |||
INCOTERMS1 | Incoterms (Part 1) | CRMT_INCOTERMS1 | CHAR | 3 | Assigned to domain | CRM_INCOTERMS1 | |||
INCOTERMS2 | Incoterms (Part 2) | CRMT_INCOTERMS2 | CHAR | 28 | CRM_INCOTERMS2 | ||||
PAYMENT_METHOD | Payment Method | DZLSCH | CHAR | 1 | Assigned to domain | ZLSCH | |||
UPD_TYPE | Type of Change | UPDATE_TYPE | CHAR | 1 | UPDATE_TYPE | ||||
ITEMNO_HI | Highest Billing Item | BEA_ITEMNO_HI | NUMC | 10 | NUMC10 | ||||
CANC_BDH_GUID | GUID of Cancelled Document Header | BEA_CANC_BDH_GUID | RAW | 16 | SYSUUID | ||||
MAX_ITEMS | Maximum Number of Items per Documetn | BEA_MAX_ITEMS | NUMC | 10 | NUMC10 | ||||
BILL_TO_GUID | Bill-to Party GUID | CRMT_BILL_TO_PARTY | RAW | 16 | SYSUUID | ||||
PAYER_GUID | Payer GUID | CRMT_PAYER | RAW | 16 | SYSUUID | ||||
PRC_SESSION_ID | ID of Pricing Activities | BEA_PRC_SESSION_ID | RAW | 16 | SYSUUID |
Key field | Non-key field |
How do I retrieve data from SAP structure CRMT_COMPL_BEA_HEADER using ABAP code?
As CRMT_COMPL_BEA_HEADER 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 CRMT_COMPL_BEA_HEADER as there is no data to select.How to access SAP table CRMT_COMPL_BEA_HEADER
Within an ECC or HANA version of SAP you can also view further information about CRMT_COMPL_BEA_HEADER 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