ARRANG_BI_ACTUAL_REV_STY SAP (BI Revenue Extractor - Actual & Potential Revenue) Structure details

Dictionary Type: Structure
Description: BI Revenue Extractor - Actual & Potential Revenue




ABAP Code to SELECT data from ARRANG_BI_ACTUAL_REV_STY
Related tables to ARRANG_BI_ACTUAL_REV_STY
Access table ARRANG_BI_ACTUAL_REV_STY




Structure field list including key, data, relationships and ABAP select examples

ARRANG_BI_ACTUAL_REV_STY 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 "BI Revenue Extractor - Actual & Potential Revenue" 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_ARRANG_BI_ACTUAL_REV_STY TYPE ARRANG_BI_ACTUAL_REV_STY.

The ARRANG_BI_ACTUAL_REV_STY table consists of various fields, each holding specific information or linking keys about BI Revenue Extractor - Actual & Potential Revenue data available in SAP. These include KNUMH (Condition record number), LOGSYS (Logical System), SB_AMT (Vendor busn. vol. value in scale curr.: settlement-relevant), SB_CURR (Currency of rebate arrangement).. 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 ARRANG_BI_ACTUAL_REV_STY 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
KNUMAAgreement (various conditions grouped together) KNUMACHAR10Assigned to domainALPHAKNUMAVMBO
KNUMHCondition record number KNUMHCHAR10KNUMB
LOGSYSLogical System LOGSYSTEMCHAR10Assigned to domainALPHALOGSYS
SB_AMTVendor busn. vol. value in scale curr.: settlement-relevant MC_BOUSTCURR17(2) WERTV9
SB_CURRCurrency of rebate arrangement ABSPWCUKY5Assigned to domainWAERS
SB_QTYQuantity QUAN3QUAN17(3) MENGE9
SB_UNITCondition unit KMEINUNIT3Assigned to domainCUNITMEINS
CB_AMTVendor busn. vol. value in scale curr.: settlement-relevant MC_BOUSTCURR17(2) WERTV9
CB_CURRCurrency of rebate arrangement ABSPWCUKY5Assigned to domainWAERS
CB_QTYQuantity QUAN3QUAN17(3) MENGE9
CB_UNITCondition unit KMEINUNIT3Assigned to domainCUNITMEINS
REV_SETTLEDVendor busn. vol. value in scale curr.: settlement-relevant MC_BOUSTCURR17(2) WERTV9
REV_POTENTIALVendor busn. vol. value in scale curr.: settlement-relevant MC_BOUSTCURR17(2) WERTV9
REV_SETT_CURRCurrency of rebate arrangement ABSPWCUKY5Assigned to domainWAERS
REV_ACCRUEDVendor busn. vol. value in scale curr.: settlement-relevant MC_BOUSTCURR17(2) WERTV9
REV_DISSOLVEDVendor busn. vol. value in scale curr.: settlement-relevant MC_BOUSTCURR17(2) WERTV9
REV_ACCR_CURRCurrency of rebate arrangement ABSPWCUKY5Assigned to domainWAERS

Key field Non-key field



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

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

How to access SAP table ARRANG_BI_ACTUAL_REV_STY

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

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


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!