RSEBANI SAP (Additional data fields relevant to purchasing) Structure details
Description: Additional data fields relevant to purchasing
Structure field list including key, data, relationships and ABAP select examples
RSEBANI 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 "Additional data fields relevant to purchasing" 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_RSEBANI TYPE RSEBANI.
The RSEBANI table consists of various fields, each holding specific information or linking keys about Additional data fields relevant to purchasing data available in SAP. These include BEDNR (Requirement Tracking Number), KZFIX (Indicator: Purchasing info record data are fixed), KUNNR (Customer), EMLIF (Vendor to be supplied/who is to receive delivery).. 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 RSEBANI 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 |
AFNAM | Name of Requisitioner/Requester | AFNAM | CHAR | 12 | AFNAM | ||||
BEDNR | Requirement Tracking Number | BEDNR | CHAR | 10 | CHAR10 | ||||
KZFIX | Indicator: Purchasing info record data are fixed | CN_KZFIX | CHAR | 1 | XFELD | ||||
KUNNR | Customer | EKUNNR | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | |
EMLIF | Vendor to be supplied/who is to receive delivery | EMLIF | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | ||
ADRN2 | Address number | AD_ADDRNUM | CHAR | 10 | Assigned to domain | ALPHA | AD_ADDRNUM | ADR | |
KALNR | Cost Estimate Number for Cost Est. w/o Qty Structure | CK_KALNR | NUMC | 12 | Assigned to domain | CK_KALNR | KNR | ||
KLVAR | Costing Variant | CK_KLVAR | CHAR | 4 | Assigned to domain | KLVAR | KRT | ||
WKURS | Exchange Rate | WKURS | DEC | 9(5) | EXCRT | KURSP | |||
RSCOMP | Spare Part Indicator | RSCOMP | CHAR | 1 | XFELD | ||||
MFLIC | Procurement indicator | CN_MFLIC | CHAR | 3 | TCNMF | CN_MFLIC | |||
FPLNR | Billing plan number / invoicing plan number | FPLNR | CHAR | 10 | Assigned to domain | FPLNR | |||
FLIEF | Fixed Vendor | FLIEF | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | ||
BSTLN | Bill of material | STNUM | CHAR | 8 | NUMCV | STNUM | STLNR | ||
BSTLT | BOM category | STLTY | CHAR | 1 | STLTY | ||||
STKAN | Edge in the exploded BOM tree | STKAN | NUMC | 6 | STKAN | ||||
GUID | UUID in compressed form (22 character UUENCODEd) | SYSUUID_22 | CHAR | 22 | SYSUUID_22 | ||||
GUID_16 | GUID in 'RAW' format | GUID_16 | RAW | 16 | SYSUUID | ||||
EKORG | Purchasing Organization | EKORG | CHAR | 4 | T024E | EKORG | EKO | ||
SOBSL | Special procurement type | SOBSL | CHAR | 2 | T460A | SOBSL | |||
STRECKE | Ind.: Third-party requisition | STRECKE | CHAR | 1 | XFELD | ||||
CREADAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
CREABY | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
PPE_EXTERN_KEY | Char63 | CHAR63 | CHAR | 63 | CHAR63 | ||||
CHANGEBY | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM | ||||
CHANGEDAT | Changed On | AEDAT | DATS | 8 | DATUM | ||||
BRTDATE | Fixed key date | BRUTR | DATS | 8 | DATUM | ||||
IDNLF | Material Number Used by Vendor | IDNLF | CHAR | 35 | IDNEX | ||||
MFRPN | Manufacturer Part Number | MFRPN | CHAR | 40 | CHAR40 | ||||
MFRNR | Number of a Manufacturer | MFRNR | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | ||
CATALOGID | Identifier for allowed catalogs | KATALOGID | CHAR | 20 | Assigned to domain | KATALOGID | |||
CATALOG_PROD_ID | Product ID in Catalog | CATALOG_PROD_ID | CHAR | 40 | CATALOG_PROD_ID | ||||
MCN33 | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
.INCLU--AP | 0 | ||||||||
ADPIC_REF_RSPOS | Reference item | ADPIC_D_REF_RSPOS | NUMC | 4 | RSPOS |
Key field | Non-key field |
How do I retrieve data from SAP structure RSEBANI using ABAP code?
As RSEBANI 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 RSEBANI as there is no data to select.How to access SAP table RSEBANI
Within an ECC or HANA version of SAP you can also view further information about RSEBANI 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