Authorization Object: F_FDES_BUK

Cash Management And Forecast: Company Code Memo Records

Category: Basic Functions

 

Definition

Object F_FDES_BUK (Cash management and forecast: company code memo
records) controls the authorizations to maintain Cash Management
and Forecast payment advices and planned items in a company code.
At this level you define whether a user may create, change or display
individual payment advices or planned items of a company code.

Click on the objects below, to expand data.

Object Fields

The list below includes the object’s fields, ordered by industry-standard importance:

ACTVT Activity Filled in 100% of cases
BUKRS Company Code Filled in 99% of cases

 

Popularity Statistics

Average popularity of F_FDES_BUK in roles: 1% (What does this mean?)
Average popularity of F_FDES_BUK by users: 21% (What does this mean?)

Object F_FDES_BUK is frequently used by users in the following areas:
FI:Financial Accounting
BC:Basis Components

Environmental Analysis

1. Common authorization objects used with F_FDES_BUK:

F_LFA1_BUK Vendor: Authorization For Company Codes Objects appear together in 88% of cases
F_KNA1_BUK Customer: Authorization For Company Codes Objects appear together in 87% of cases
F_PAYRQ Authorization Object For Payment Requests Objects appear together in 81% of cases
F_FDSB_GSB Cash Position: Business Area Summary Records Objects appear together in 73% of cases
F_FDSR_BUK Liquidity Forecast: Company Code Summary Records Objects appear together in 73% of cases
F_FDSR_GSB Liquidity Forecast: Business Area Summary Records Objects appear together in 73% of cases
F_T_TRANSB Treasury: Transaction Authorization Objects appear together in 73% of cases
F_FDES_GSB Cash Management And Forecast: Business Area Memo Records Objects appear together in 71% of cases
F_FEBB_BUK Company Code Bank Statement Objects appear together in 47% of cases
F_SKA1_BUK G/L Account: Authorization For Company Codes Objects appear together in 43% of cases
F_BKPF_BUK Accounting Document: Authorization For Company Codes Objects appear together in 39% of cases
F_BKPF_KOA Accounting Document: Authorization For Account Types Objects appear together in 39% of cases
F_FDSB_BUK Cash Position: Company Code Summary Records Objects appear together in 37% of cases

  2. Appearance of F_FDES_BUK in T-Codes:

FF/6 Deposit/loan mgmt analysis/posting Used in 100% of cases
FF/7 Deposit/loan management int accruals Used in 100% of cases
FF65 List of Cash Management Memo Records Used in 100% of cases
FF71 Cash Position Used in 100% of cases
FF72 Liquidity forecast Used in 100% of cases
FF-9 Journal Used in 100% of cases
FRFT2 Repetitive fast entry form Used in 100% of cases
TB11 Create Object Hedge Used in 100% of cases
TB12 Change object hedge Used in 100% of cases
TB13 Display object hedge Used in 100% of cases
TB14 Reverse object hedge Used in 100% of cases
FF70 Cash Mgmt Posit./Liquidity Forecast Used in 98% of cases
OT48 C FT CMF reorganization Used in 98% of cases
FF.7 Payment Advice Comparison Used in 97% of cases
FF.8 Print Payment Orders Used in 97% of cases
FF/3 Archive advices from bank statements Used in 97% of cases
FF/9 Compare Advices with Bank Statement Used in 97% of cases
FF6A Edit Cash Mgmt Pos Payment Advices Used in 97% of cases
FF73 Cash Concentration Used in 97% of cases
FFWR Post Payment Requests from Advice Used in 97% of cases
FFWR_REQUESTS Create Payment Requests from Advice Used in 97% of cases
FPS3 Intraday Statment Used in 97% of cases
FRFT Rapid Entry with Repetitive Code Used in 97% of cases
FFW1 Wire Authorization Used in 95% of cases
FPS2 Generate Payment Advice from Polling Used in 95% of cases
FF63 Create Planning Memo Record Used in 94% of cases
FF6B Edit liquidity forecast planned item Used in 94% of cases
FF.9 Post Payment Orders Used in 92% of cases
FF.D Generate payt req. from advices Used in 92% of cases
FF-7 Forecast Item Journal Used in 90% of cases
FF-8 Payment Advice Journal Used in 90% of cases
FF-3 Cash Management Summary Records Used in 87% of cases

Leave a Reply

Your email address will not be published.