Hierarchy
⤷ MM-PUR (Application Component) Purchasing
⤷ WRF_BUDGET (Package) Framework: Budget Processes
Basic Data
Data Element | WRF_BUDG_TYPE |
Short Description | Budget Type |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | WRF_BUDG_TYPE | |
Data Type | CHAR | Character String |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
Value Table |
Further Characteristics
Search Help: Name | WRF_POTB_BUDGET_TYPE_F4 | |
Search Help: Parameters | TYPE | |
Parameter ID | ||
Default Component name | BUDGETTYPE | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Bdgt Type |
Medium | 20 | Budget Type |
Long | 40 | Budget Type |
Heading | 65 | Budget Type |
Documentation
Definition
Grouping of control parameters for the budget processes in the Price Planning and Open-to- Buy applications.
Use
Dependencies
You define the budget type in SAP BI and transfer it to SAP ECC. You assign the budget type to the budget level and key figure set.
In the OTB application, you can use multiple budget types to model different processes. If you use the OTB function with multiple budget types, you have to define the Customizing for extending the budget type, by assigning a BAdI implementation and the prioritization to determine how SAP ECC can determine the budget type uniquely.
Only one budget type is allowed in the PPW.
Example
In the OTB application, you can use multiple budget types to model a process, or use individual budget types assigned to different budget levels:
- Process A
Centralized purchasing; the store is not part of the assigned budget level. - Process B
Decentralized purchasing; the store is part of the assigned budget level.
History
Last changed by/on | SAP | 20060703 |
SAP Release Created in | 111 |