SAP ABAP Data Element FDLEV (Planning Level)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM-MD-PCT (Application Component) Product Catalog
     ⤷ FF (Package) Cash Management
Basic Data
Data Element FDLEV
Short Description Planning Level  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type FDLEV    
Data Type CHAR   Character String 
Length 2    
Decimal Places 0    
Output Length 2    
Value Table T036    
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID FFE  
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Plan. Lvl 
Medium 15 Planning Level 
Long 20 Planning Level 
Heading 5 Level 
Documentation

Definition

The planning level is used to control displays in Cash Management.

The following levels could be possible:

  • Only noted items in the cash position
  • Only noted items in the liquidity forecast
  • Purchase orders
  • Sales orders
  • Notified incoming payments
  • FI payment settlements (incoming checks, outgoing checks, bills of exchange, payments)
  • FI bank transactions (bank statement postings, cashed checks, bill of exchange payments)

You can freely choose the planning levels. You should, however, follow a naming convention:

To improve the display of the cash position and liquidity forecast, you should reserve levels that start with "F" or "B" for automatically updating data during posting. F levels should be used for bank accounts, customers, and vendors, and B levels for bank clearing accounts.

Examples:

  • F0: bank accounts
  • F1: purchasing/sales (customers/vendors)
  • FF: down payment requests
  • FW: bills of exchange
  • B1: bank clearing accounts, outgoing checks
  • B2: bank clearing accounts, outgoing bank transfers (domestic)
  • B3: bank clearing accounts, outgoing bank transfers (foreign country)
  • B4: bank clearing accounts, bank collection
  • and so on.

When displaying the cash position, you can then see because of level F0 that the amounts are posted to the bank account, whereas the other levels show planned bank account transactions, which include entered payment advices or postings to bank clearing accounts. You can then use the display to compare planned date with actual data.

In addition, you should reserve levels, for example, all levels beginning with X, to represent postings with payment blocking indicators in the liquidity forecast. When displaying the liquidity forecast, you can then see because of these levels that the displayed amounts are postings with payment blocking indicators.

General notes on accounts, or planning groups, and planning levels:

Accounts/groups and levels enable you to look at data two different ways.

Accounts/groups answer the who question.

  • Which (major) customers or suppliers?
  • Which customer or supplier group?
  • Which bank account or bank clearing account?

Levels answer the how question.

  • How information was entered into the system (posting or payment advice or planned item)?
  • How an amount is posted (normal posting or special G/L transaction)?
  • How accurate information is
    • With amounts in the "outgoing transfers" level, you know the exact date on which the account is debited, but with amounts in the "outgoing checks" level, the date on which the account is debited is uncertain.
    • In levels for MM and SD, both the amount and the planning date are more uncertain than the amount and date in FI postings, since the vendor may, for example, deliver only a subset or the delivery may be delayed. In addition, the system always displays MM amounts without taxes in the liquidity forecast (in purchase orders, tax is not displayed if it can be deducted; in purchase requisitions, it is never displayed).

Where are cash management levels assigned in the system?

In G/L accounts, you define the level in the company-code-specific part of the master record.

For accounts receivable and payable, you define a standard level in the cash management and forecast group.

At this time, you can define different levels for the following applications and activities:

  • Locked items
  • Special G/L transactions
  • Payment requests
  • Purchase orders and purchase requisitions
  • Orders
  • Agency deals
  • Loans
  • Securities
  • Money market, foreign exchange, derivatives
  • Real estate
  • Earmarked funds

The levels defined should be unique - meaning you must not define the same level for more than one application or activity as this may affect the clarity of the display in the cash position or liquidity forecast. It might also adversely affect the function for jumping from these transactions to the correct application or line item display.

Supplementary Documentation - FDLEV 0001

Use

Enter the level that is stored in the G/L master record.

Procedure

If a cash management update is made in the bank account, the fields "Level" and "Payment request level" have to be maintained. The field "Country" must also be maintained. The field "Payment method" must be left blank.

If the update is made in the bank clearing account because the payment method is already known, you do not have to maintain any entries. Instead, the update is then made at the level that is in the master record for the bank clearing account. If this is not required because postings and requests for payment are not differentiated in the cash management position, you can store a different level here so that all fields ready for input have to be maintained and the level of the bank clearing account has to be specified in the "Level" field. (The bank clearing account is determined in T042I and is found there in the column "Bank subaccount".)

Examples

Dependencies

History
Last changed by/on SAP  19981111 
SAP Release Created in