SAP Table Fields

RBKP-FDLEV Planning level SAP Table field attribute values such as data element, length, datatype







FDLEV is a standard field within SAP Table RBKP that stores Planning level information. LI>FW: bills of exchange beginning with X, to represent postings with payment blocking indicators postings with payment blocking indicators.

  • Securities


  • To improve the display of the cash position and liquidity forecast, you
  • Payment requests

  • and so on.

  • Purchase orders


  • Examples:
  • B2: bank clearing accounts, outgoing bank transfers (domestic) updating data during posting. F levels should be used for bank


  • The levels defined should be unique - meaning you must not define the


  • FI bank transactions (bank statement postings, cashed checks, bill of in the liquidity forecast. When displaying the liquidity forecast, you exchange payments)


  • When displaying the cash position, you can then see because of level F0

    You can freely choose the planning levels. You should, however, follow a liquidity forecast (in purchase orders, tax is not displayed if it can ways. accounts, customers, and vendors, and B levels for bank clearing can then see because of these levels that the displayed amounts are uncertain than the amount and date in FI postings, since the vendor may, or planned item)?
  • Orders


  • The following levels could be possible: checks" level, the date on which the account is debited is uncertain.

    For accounts receivable and payable, you define a standard level in the
  • How information was entered into the system (posting or payment advice

  • Which (major) customers or suppliers?

  • F0: bank accounts

  • B1: bank clearing accounts, outgoing checks the clarity of the display in the cash position or liquidity forecast.

  • Only noted items in the liquidity forecast the display to compare planned date with actual data. addition, the system always displays MM amounts without taxes in the

  • Real estate accounts. should reserve levels that start with "F" or "B" for automatically


  • In G/L accounts, you define the level in the company-code-specific part

    Accounts/groups and levels enable you to look at data two different
  • Which bank account or bank clearing account?

  • Money market, foreign exchange, derivatives

  • B4: bank clearing accounts, bank collection exchange, payments)

    Below is the list of attribute values for this field including its length, data type, description text, associated , search help etc... You could also view this information on your SAP system if you enter the table name RBKP or data element FDLEV into the relevant SAP transaction such as SE11 or SE80.

    Also check out the Contributions section below to add and view useful hints, tips and screen shots specific to this SAP table field. These details can also be found quickly in the future by simply searching on the SAP object name RBKP-FDLEV or its description.

    Main Table: RBKP

    Example ABAP code to select data from table RBKP field FDLEV

    DATA: LD_FDLEV TYPE RBKP-FDLEV.

    SELECT single FDLEV
    FROM RBKP
    INTO LD_FDLEV
    WHERE...

    Attributes from SAP Table field RBKP-FDLEV





    Short Description:Planning level...See data element details
    Position of field in table:122
    Keyfield:No
    Mandatory:No
    Check table:
    *
    The check table for this field is assigned via the Domain's value table . This means there isn't a specific foreign key definition for it but will be based on the primary key of the check/value table.
    Internal type(i.e. C,I,N):Assigned at Data Element level, See FDLEV
    Internal Length(in Bytes):Assigned at Data Element level, See FDLEV
    Reference table:
    Can field have NULL value?:Yes
    Data Element / Component Type:FDLEV
    Domain name:FDLEV
    Reference field for currency/qty fields:
    Data type/ Length / Decimals See data element details
    Origin of Search help:No input help exists
    No input help exists for this field.


    Search help attached to field:
    Is field a table (i.e. nested table):Yes
    Depth for structured types:N/A
    Component Type:Built-in type
    Is allocated Language Field?:N/A
    If a table/structure contains more than 1 language field (i.e. data type LANG) this flag denotes which one is used for the text language


    Object Referenced type:No Information stored