BBPX_ORDER_RESPONSE SAP (Proxy-Struktur (generiert)) Structure details
Description: Proxy-Struktur (generiert)
Related tables to BBPX_ORDER_RESPONSE
Access table BBPX_ORDER_RESPONSE
Structure field list including key, data, relationships and ABAP select examples
BBPX_ORDER_RESPONSE 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 "Proxy-Struktur (generiert)" 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_BBPX_ORDER_RESPONSE TYPE BBPX_ORDER_RESPONSE.
The BBPX_ORDER_RESPONSE table consists of various fields, each holding specific information or linking keys about Proxy-Struktur (generiert) data available in SAP. These include BODY (), CONTROLLER (), ORDER_RESPONSE_HEADER (), CONTROLLER ().. 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 BBPX_ORDER_RESPONSE 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 |
CONTROLLER | 0 | ||||||||
BODY | 0 | ||||||||
CONTROLLER | 0 | ||||||||
ORDER_RESPONSE_HEADER | 0 | ||||||||
CONTROLLER | 0 | ||||||||
PURCHASE_ORDER_ID | Purchase order, this document is refering to | 0 | |||||||
RESPONSE_CODE | 0 | ||||||||
CURRENCY | Proxy Data Element (generated) | BBPX_CURRENCY | CHAR | 3 | |||||
TRADING_PARTNERS | 0 | ||||||||
CONTROLLER | 0 | ||||||||
VENDOR | 0 | ||||||||
CONTROLLER | 0 | ||||||||
IDENTIFIER | 0 | ||||||||
CONTROLLER | 0 | ||||||||
PARTNER_ID | Business partner ID in EBP | 0 | |||||||
DUNS | Dun and Bradstreet standard ID for this partner (has to be m | 0 | |||||||
ADDRESS | 0 | ||||||||
CONTROLLER | 0 | ||||||||
COMPANY_NAME1 | Name 1 of organization | 0 | |||||||
COMPANY_NAME2 | Name 2 of organization | 0 | |||||||
CARE_OF_NAME | 0 | ||||||||
POBOX | PO Box | 0 | |||||||
POBOX_CITY | Used, if the city of the post-office box differs from city | 0 | |||||||
POBOX_POSTAL_CODE | Used, if the postal code of the post-office box differs from | 0 | |||||||
POBOX_COUNTRY | Proxy Data Element (generated) | BBPX_COUNTRY | CHAR | 2 | |||||
STREET_PREFIX | Prefix for the steet name, common in some countries | 0 | |||||||
STREET | Street | 0 | |||||||
STREET_SUFFIX | Suffix for the steet name, common in some countries | 0 | |||||||
HOUSE_NUMBER | House number | 0 | |||||||
CITY | City | 0 | |||||||
POSTAL_CODE | City postal code | 0 | |||||||
COMPANY_POSTAL_CODE | Used, if the postal code of the company differs from the pos | 0 | |||||||
REGION | Region (state, province, county) | 0 | |||||||
DISTRICT | District | 0 | |||||||
COUNTRY | Proxy Data Element (generated) | BBPX_COUNTRY | CHAR | 2 | |||||
PERSON_TITLE | 0 | ||||||||
FIRST_NAME | First name | 0 | |||||||
LAST_NAME | Last name | 0 | |||||||
DEPARTMENT | Department | 0 | |||||||
BUILDING | Building (number or code) | 0 | |||||||
FLOOR | Floor | 0 | |||||||
ROOM_NUMBER | Room or appartment number | 0 | |||||||
TELEPHONE_NUMBER | Telephone no.: Area code+number | 0 | |||||||
TELEPHONE_NUMBER_EXTENSION | Telephone no.: Extension | 0 | |||||||
FAX_NUMBER | Fax no.: Area code+number | 0 | |||||||
FAX_NUMBER_EXTENSION | Fax no.: Extension | 0 | |||||||
EMAIL_ADDRESS | E-mail address | 0 | |||||||
ORDERING_PARTY | 0 | ||||||||
CONTROLLER | 0 | ||||||||
IDENTIFIER | 0 | ||||||||
CONTROLLER | 0 | ||||||||
PARTNER_ID | Business partner ID in EBP | 0 | |||||||
DUNS | Dun and Bradstreet standard ID for this partner (has to be m | 0 | |||||||
PARTNER_IDVENDOR_ASSIGNED | Business partner ID assigned by the vendor (has to be mainta | 0 | |||||||
ADDRESS | 0 | ||||||||
CONTROLLER | 0 | ||||||||
COMPANY_NAME1 | Name 1 of organization | 0 | |||||||
COMPANY_NAME2 | Name 2 of organization | 0 | |||||||
CARE_OF_NAME | 0 | ||||||||
POBOX | PO Box | 0 | |||||||
POBOX_CITY | Used, if the city of the post-office box differs from city | 0 | |||||||
POBOX_POSTAL_CODE | Used, if the postal code of the post-office box differs from | 0 | |||||||
POBOX_COUNTRY | Proxy Data Element (generated) | BBPX_COUNTRY | CHAR | 2 | |||||
STREET_PREFIX | Prefix for the steet name, common in some countries | 0 | |||||||
STREET | Street | 0 | |||||||
STREET_SUFFIX | Suffix for the steet name, common in some countries | 0 | |||||||
HOUSE_NUMBER | House number | 0 | |||||||
CITY | City | 0 | |||||||
POSTAL_CODE | City postal code | 0 | |||||||
COMPANY_POSTAL_CODE | Used, if the postal code of the company differs from the pos | 0 | |||||||
REGION | Region (state, province, county) | 0 | |||||||
DISTRICT | District | 0 | |||||||
COUNTRY | Proxy Data Element (generated) | BBPX_COUNTRY | CHAR | 2 | |||||
PERSON_TITLE | 0 | ||||||||
FIRST_NAME | First name | 0 | |||||||
LAST_NAME | Last name | 0 | |||||||
DEPARTMENT | Department | 0 | |||||||
BUILDING | Building (number or code) | 0 | |||||||
FLOOR | Floor | 0 | |||||||
ROOM_NUMBER | Room or appartment number | 0 | |||||||
TELEPHONE_NUMBER | Telephone no.: Area code+number | 0 | |||||||
TELEPHONE_NUMBER_EXTENSION | Telephone no.: Extension | 0 | |||||||
FAX_NUMBER | Fax no.: Area code+number | 0 | |||||||
FAX_NUMBER_EXTENSION | Fax no.: Extension | 0 | |||||||
EMAIL_ADDRESS | E-mail address | 0 | |||||||
TEXT | 0 | ||||||||
CONTROLLER | 0 | ||||||||
CONTENT | The text itself | 0 | |||||||
LANGUAGE | Proxy Data Element (generated) | BBPX_LANGUAGE | CHAR | 2 | |||||
ORDER_RESPONSE_ITEM | 0 |
Key field | Non-key field |
How do I retrieve data from SAP structure BBPX_ORDER_RESPONSE using ABAP code?
As BBPX_ORDER_RESPONSE 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 BBPX_ORDER_RESPONSE as there is no data to select.How to access SAP table BBPX_ORDER_RESPONSE
Within an ECC or HANA version of SAP you can also view further information about BBPX_ORDER_RESPONSE 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