PIBA_BTC SAP (Transfer structure for external production requirements) IDoc segment structure details
Dictionary Type: IDoc segment structure
Description: Transfer structure for external production requirements
Description: Transfer structure for external production requirements
IDoc segment structure field list including key, data, relationships and ABAP select examples
PIBA_BTC is a standard SAP Structure which is used to define the field attributes of IDoc segment PIBA_BTC. The segment is used within the below IDoc to send Transfer structure for external production requirements information via the IDoc send process
BTC_ID02Below is the standard documentation available and a few details of the fields which make up this IDoc segment structure. To view further details checkout the IDoc links above or use relevant transactions such as WE30(IDoc development), WE31 (segment development)...Also check here for more IDoc related development help, or you can obviously also use standard dictionary object dev tcodes such as SE11, SE80 etc...
Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type)
SAP PIBA_BTC idoc segment 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 | |||
| ADRNR | Address of the higher-level system | PI_ADRNR | CHAR | 10 | PIBA | CHAR10 | |||
| PEGREQ | Pegged requirements in external system | DI_PEGREQ | CHAR | 30 | PIBA | PICHAR30 | CIA | ||
| CREDAT | Date record created on | ANDAT | DATS | 8 | DATUM | ||||
| CRENAM | User who created record | ANNAM | CHAR | 12 | USNAM | ||||
| CHADAT | Changed On | AEDAT | DATS | 8 | DATUM | ||||
| CHANAM | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM | ||||
| REQMAT | Material Number | MATNR | CHAR | 18 | MARA | MATN1 | MATNR | MAT | S_MAT1 |
| WERKS | Plant | WERKS_D | CHAR | 4 | T001W | WERKS | WRK | H_T001W_C | |
| REQQUAN | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
| REQUNIT | 3-Byte field | CHAR3 | CHAR | 3 | CHAR3 | ||||
| REQDATE | Requirement date | DATUMA | DATS | 8 | DATUM | ||||
| FLGCLLOC | Indicator: Allocations completed | DI_FLGALLO | CHAR | 1 | XFELD | ||||
| PLNTY | Task List Type | PLNTY | CHAR | 1 | TCA01 | PLNTY | PTY | H_TCA01 | |
| PLNNR | Key for Task List Group | PLNNR | CHAR | 8 | ALPHA | PLNNR | PLN | PLKS | |
| PLNAL | Group Counter | PLNAL | CHAR | 2 | ALPHA | ALTNR | PAL | ||
| DBEKZ | Processing indicator | DBEKZ | CHAR | 1 | CHAR1 | ||||
| REQMAT_EXTERNAL | 0 | ||||||||
| REQMAT_VERSION | 0 | ||||||||
| REQMAT_GUID | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure PIBA_BTC using ABAP code?
As PIBA_BTC 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 PIBA_BTC as there is no data to select.How to access SAP table PIBA_BTC
Within an ECC or HANA version of SAP you can also view further information about PIBA_BTC 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