SAP BBPS_CM_CTR_HEADER_D Contract Header Data Get Detail Case Interface (RFC) Table data and field list

BBPS_CM_CTR_HEADER_D 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 "Contract Header Data Get Detail Case Interface (RFC)" 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_CM_CTR_HEADER_D TYPE BBPS_CM_CTR_HEADER_D.

The BBPS_CM_CTR_HEADER_D table consists of various fields, each holding specific information or linking keys about Contract Header Data Get Detail Case Interface (RFC) data available in SAP. These include DESCRIPTION (Name of the Contract), CURRENCY (Currency Key), VPER_START (Validity Start Date of Contract), VPER_END (Validity End Date of Contract)... 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. .

BBPS_CM_CTR_HEADER_D structure Technical Details:

Delivery Class:
Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced


SAP BBPS_CM_CTR_HEADER_D structure fields - Full list of fields found in SAP data dictionary

Looking for S/4HANA specific information? Click here to explore the details, fields and extensibility available for this table in the SAP S/4HANA version of the BBPS_CM_CTR_HEADER_D table. Also check whether the table still exists or has been transformed into a CDS view as part of the HANA simplifications.
Field Description Data Element Data Type length (Dec) Check table Conversion Routine Domain Name MemoryID SHLP
GUIDGlobally Unique identifier BBP_GUIDRAW16SYSUUID
DESCRIPTIONName of the Contract BBP_DESCRIPTION_CTRCHAR40CRM_PROCESS_DESCRIPTION
CURRENCYCurrency Key WAERSCUKY5Assigned to domainWAERSFWS
VPER_STARTValidity Start Date of Contract BBP_VPER_START_CTRDATS8DATUM
VPER_ENDValidity End Date of Contract BBP_VPER_END_CTRDATS8DATUM
PMNTTRMSTerms of Payment Key DZTERMCHAR4ZTERM
INCOTERM_KEYIncoterm Key BBP_INCOTERM_KEYCHAR3Assigned to domainBBP_INCOTERM_KEY
INCOTERM_LOCIncoterm Location BBP_INCOTERM_LOCATIONCHAR28BBP_INCOTERM_LOCATION
POSTING_DATEDocument Date (Posting Date of Log. Business Transaction) BBP_POSTING_DATEDATS8DATUM
APPROVAL_INDApproval Indicator BBP_APPROVAL_INDCHAR1BBP_APPROVAL_IND
DELIV_DAYSDelivery Time in Days BBP_DELIV_DAYSNUMC3NUMC3
HIER_P_GUIDHeader GUID of the Parent Node BBP_HIER_PARENT_GUIDRAW16SYSUUID
HIER_P_IDObject ID of the Parent Node BBP_HIER_PARENT_OBJIDCHAR10ALPHACRM_OBJECT_ID
CO_CODECompany Code in FI System BBP_CO_CODECHAR4Assigned to domainBUKRS
LOGSYS_FILogical System of FI System BBP_LOGSYS_FICHAR10Assigned to domainALPHALOGSYSBBP_BACKEND_DESTINATION_F4
GUARANTEED_MINGuaranteed Purchase Value (Public Sector ONLY!!) BBP_GUARANTEED_MINCURR15(2) WERT8
SK_COUNTRYCountry ISO code INTCACHAR2INTCAF4_INTCA
SK_SCENARIO1Key of a Scenario for Field Extension BBP_CUF_SCENARIO_KEYCHAR3BBP_CUF_SCENARIO_KEY
SK_SCENARIO2Key of a Scenario for Field Extension BBP_CUF_SCENARIO_KEYCHAR3BBP_CUF_SCENARIO_KEY
SK_SCENARIO3Key of a Scenario for Field Extension BBP_CUF_SCENARIO_KEYCHAR3BBP_CUF_SCENARIO_KEY
SK_SCENARIO4Key of a Scenario for Field Extension BBP_CUF_SCENARIO_KEYCHAR3BBP_CUF_SCENARIO_KEY
SK_SCENARIO5Key of a Scenario for Field Extension BBP_CUF_SCENARIO_KEYCHAR3BBP_CUF_SCENARIO_KEY
TOTAL_VALUETarget Value of Contract BBP_TOTAL_VALUE_CTRCURR15(2) WERT8
CATALOG_INDDocument (Contract) Transferred to Catalog BBP_CATALOG_INDCHAR1XFELD
NO_ITEMS_ALLOWEDIndicator Header Contract BBP_HEADER_CTRCHAR1XFELD
SENSITIVEConfidential Level of the SRM Document BBP_SENSITIVECHAR1BBP_SENSITIVE
PROCESS_TYPEBusiness Transaction Type CRMT_PROCESS_TYPE_DBCHAR4Assigned to domainCRM_PROCESS_TYPE
OBJECT_IDContract No. BBP_OBJECT_ID_CTRCHAR10ALPHACRM_OBJECT_ID
DOC_LANGULanguage Key for Document / Vendor BBP_DOCUMENT_LANGULANG1ISOLASYLANGU
SUBTYPESpecification of a Purchasing Doc.(e.g. Credit Memo/Invoice) BBP_H_SUBTYPECHAR2BBP_H_SUBTYPE
TEMPLATE_TYPETemplate Type of CRM Transaction CRMT_TEMPLATE_TYPE_DBCHAR1CRM_TEMPLATE_TYPE
CREATED_BYName of Person who Created the Object ERNAMCHAR12USNAM
CREATED_ATTransaction was Created at this Time CRMT_CREATED_ATDEC15TSTPSBCOS_TSTMP
CHANGED_BYName of Person Responsible for Changing Object BBP_CHNAMCHAR12USNAM
CHANGED_ATTime of Last Change to the Transaction CRMT_CHANGED_ATDEC15TSTPSBCOS_TSTMP
TZONETime Zone for Date and Time Fields of Procurement Document BBP_TZONECHAR6BBP_TZONE
ROOT_INDis Root of a Hierarchy BBP_ROOT_INDCHAR1XFELD
VERSION_TYPEVersion Type (Active Document, 'Normal', Work Version) BBP_VERSION_TYPECHAR1BBP_VERSION_TYPE
ACTIVE_HEADERGlobally Unique identifier BBP_GUIDRAW16SYSUUID
CHANGE_LOCKChange Lock ('X': changes not allowed) BBP_CHANGE_LOCKCHAR1XFELD
VERSION_NOVersion Number BBP_VERSION_NOCHAR8CHAR08
VAL_PO_EValue of POs/Confirmations/Invoices Created for Contract BBP_PO_VALUE_ECURR15(2) WERT8
VAL_PO_E_AGGValue PO / Confirm. / Inv. for Contract Hierarchy BBP_AGG_VALUE_ECURR15(2) WERT8

Key field Non-key field



How do I retrieve data from SAP structure BBPS_CM_CTR_HEADER_D using ABAP code?

As BBPS_CM_CTR_HEADER_D 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_CM_CTR_HEADER_D as there is no data to select.

How to access SAP table BBPS_CM_CTR_HEADER_D

Within an ECC or HANA version of SAP you can also view further information about BBPS_CM_CTR_HEADER_D and the data within it using relevant transactions such as

SE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).