SAP ABAP Data Element KPP_NOBUFFORMS (CO Planning Indicator: No buffering for forms in kpp1)
Hierarchy
☛
SAP_FIN (Software Component) SAP_FIN
⤷ CO-OM-CCA (Application Component) Cost Center Accounting
⤷ KPP (Package) Cost Accounting, planning processor
⤷ CO-OM-CCA (Application Component) Cost Center Accounting
⤷ KPP (Package) Cost Accounting, planning processor
Basic Data
Data Element | KPP_NOBUFFORMS |
Short Description | CO Planning Indicator: No buffering for forms in kpp1 |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR1 | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Buffer frm |
Medium | 15 | Buffer forms? |
Long | 20 | Buffer forms? |
Heading | 15 | Buffer forms? |
Documentation
Definition
Up to this point, the planning processor buffers layouts which have already been read are buffered into internal tables when these layouts are called up. If you do not want this buffering to take place, you can set the nobufforms parameter in structure kpp0s. If you do this, the planning layouts will always be read again from the database. From Release 4.6A, function module k_plan_screen_structure_get also has an optional parameter (i_nobufforms) which switches off buffering.
Generates an application layout and makes it possible during planning to go to the planning layout maintenance screen. It can therefore make sense to set this parameter.
History
Last changed by/on | SAP | 19990326 |
SAP Release Created in |