BBP_PDS_DEMAND SAP (Demand with List of Allowed Vendors) Structure details
Description: Demand with List of Allowed Vendors
Related tables to BBP_PDS_DEMAND
Access table BBP_PDS_DEMAND
Structure field list including key, data, relationships and ABAP select examples
BBP_PDS_DEMAND 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 "Demand with List of Allowed Vendors" 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_BBP_PDS_DEMAND TYPE BBP_PDS_DEMAND.
The BBP_PDS_DEMAND table consists of various fields, each holding specific information or linking keys about Demand with List of Allowed Vendors data available in SAP. These include EXT_DEM_LOGSYS (Logical System from where an External Requirement Comes), EXT_DEMID (External Requirement Number), EXT_DEM_POSID (External Requirement Tracking Number), CTR_NUMBER (Document Number).. 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 BBP_PDS_DEMAND 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 |
| EXT_DEM_LOGSYS | Logical System from where an External Requirement Comes | BBP_EXT_DEM_LOGSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
| EXT_DEMID | External Requirement Number | BBP_EXT_DEMID | CHAR | 32 | CHAR32 | ||||
| EXT_DEM_POSID | External Requirement Tracking Number | BBP_EXT_DEM_POSID | CHAR | 32 | CHAR32 | ||||
| CTR_NUMBER | Document Number | BBP_DOC_NUMBER | CHAR | 10 | ALPHA | CRM_OBJECT_ID | |||
| CTR_ITEM_NUMBER | Item Number | BBP_ITEM_NO | NUMC | 10 | CRM_ITEM_NO | ||||
| CTR_ITEM_GUID | Contract Template Item GUID | BBP_CTR_I_GUID_C | CHAR | 32 | CHAR32 | ||||
| BUP_VENDOR_ID | Business Partner Number | BU_PARTNER | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BPA | BUPA |
| BUP_VENDOR_GUID | Business Partner GUID | BBP_PARTNER_GUID | CHAR | 32 | SYSUUID_C | ||||
| BUP_LOCATION_ID | Business Partner Number | BU_PARTNER | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BPA | BUPA |
| BUP_LOCATION_GUID | Business Partner GUID | BBP_PARTNER_GUID | CHAR | 32 | SYSUUID_C | ||||
| SUBTYPE | Specification Purchase Item (e.g. Direct Material/Hierarch.) | BBP_I_SUBTYPE | CHAR | 2 | BBP_I_SUBTYPE | ||||
| PRODUCT_GUID | Internal Unique ID of Product | COMT_PRODUCT_GUID_BAPI | CHAR | 32 | SYSUUID_C | ||||
| PRODUCT_ID | Product Number | BAPI_PRODUCT_ID | CHAR | 40 | PRID1 | COM_PRODUCT_ID | |||
| QUANTITY | Quantity in Order Unit | BBP_MNG | QUAN | 13(3) | MENG13 | ||||
| UNIT | Unit of Measurement | BBP_UNIT | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| DELIV_DATE | Item Delivery Date | EINDT | DATS | 8 | DATUM | ||||
| DELIV_TIME | Delivery Time of the Item | BBP_DELIV_TIME | TIMS | 6 | TIME | ||||
| DP_STGE_LOC | Storage Location | LGORT_D | CHAR | 4 | Assigned to domain | LGORT | LAG | ||
| DP_SP_STK_IND | Special Stock Indicator | BBPCIF_CIFSPECSTO | CHAR | 1 | Assigned to domain | SOBKZ | |||
| ACC_CAT | Account Assignment Category in SRM | BBP_ACC_CAT | CHAR | 5 | BBP_ACCCAT | ||||
| SD_DOC | Sales and Distribution Document Number | BBP_VBELN | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
| SDOC_ITEM | Sales Document Item | BBP_POSNR_VA | NUMC | 6 | Assigned to domain | POSNR | APO | ||
| SCHED_LINE | Schedule Line Number | BBP_ETENR | NUMC | 4 | Assigned to domain | ETENR | |||
| WBS_ELEM_E | Work Breakdown Structure Element (WBS element) | BBP_WBS_ELEM | CHAR | 24 | ABPSN | PS_POSID | |||
| PRODUCT_SRC_SYS | Business Document Service: ID of Logical System | BBP_LOGSYS | CHAR | 10 | CHAR10 | ||||
| APPR_VENDOR_IDS | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure BBP_PDS_DEMAND using ABAP code?
As BBP_PDS_DEMAND 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 BBP_PDS_DEMAND as there is no data to select.How to access SAP table BBP_PDS_DEMAND
Within an ECC or HANA version of SAP you can also view further information about BBP_PDS_DEMAND 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