ale-dp/sap-fiori-apps huggingface dataset:
Split Costs - Cost Centers - Plan
Application component: Activity Types
App type: SAP GUI
Description:   During plan cost splitting, the system splits the activity-independent plan costs of a cost center among the activity types of this cost center. You must split plan costs before executing: Price calculation:   Plan costs are split automatically during price calculation. The system determines the plan prices from the ratio of plan costs and plan activity. Splitting activity-independent plan costs on the cost center activity types helps to calculate the fixed price portion of the overall price. Plan cost splitting therefore ensures that all planned costs are considered during price calculation. Plan/Target/Actual Comparison   To view all costs at the cost center/activity type level and make plan/target/actual comparisons, you must split activity-independent actual and plan costs among the activity types. You use the same methods for actual and plan costs.   In the actual there is a an additional splitting step in which the actual data is adjusted to the plan data. Actual data is distributed to the activity types on the basis of target costs or target quantities and by cost element.  
Key features:   The activity-independent costs planned on a cost center are split on the activity types according to the splitting structure that you defined during Customizing and assigned to this cost center. A splitting structure contains one or more assignments in which you store splitting rules for the corresponding cost element(s) or cost element groups. You can restrict the selection of cost elements or cost element groups, as well the activity types on which the costs are split.   Splitting methods are assigned to the splitting rules. These methods specify how the costs are split. Based on the splitting methods, which are fixed in the system, you can split plan costs according to the following criteria:  Activity quantity  Equivalence number  Capacity  Output  Scheduled activity  Statistical key figure (quantity)  Statistical key figure (maximum quantity)  No splitting is executed   You can also use weighting indicators to control whether tracing factors are to be weighted for the cost splitting. Set the indicator if the individual tracing factor values use different units of measure. If the Conversion indicator is active, the values are multiplied with the equivalence numbers of the activity types. This enables you to compare the different units of measure of the tracing factor values.
Create Overhead Allocation Cycles - Cost Centers - Actual
Application component: Cost Center Accounting
App type: SAP GUI
Description:  Overhead allocation allocates primary and secondary costs in Cost Center Accounting and Activity-Based Costing. The following information is passed on to the receivers in this process: The original cost elements are assigned cumulatively, or in groups, to secondary cost elements. The original cost elements are not visible on the receivers.  Sender and receiver information (sender cost center, receiver cost center, or business process) appears in the controlling document.  Overhead allocation using secondary cost elements is useful when the composition of the costs is unimportant for the receiver. For example, cafeteria costs can be allocated to a cost center without the need for a detailed cost breakdown. Note In periodic reposting, distribution, and overhead allocation, line items are written for each sender and receiver. It is not technically possible to restrict the writing of line items. If you repeat period-based allocations within a period, the line items are reversed and overwritten. The posting date of the actual allocation is always the last day of a calendar month. The posting date for plan allocation is always the first day of the calendar month.You cannot allocate consumption quantities using overhead allocation. To allocate activity quantities, you need to use indirect activity allocation. 
Key features:  For overhead allocation, you can summarize all the cost elements into one secondary cost element. When you execute the allocation, all the costs allocated by the sender are included in this cost element. However, this method does not store any information on the receiver regarding the composition of the costs. Alternatively, you can use an allocation structure to define which cost elements are to be allocated under which secondary cost elements. You can assign individual cost elements, cost element groups, or intervals to an allocation cost element. The allocation structure can be stored during segment maintenance. Note Until now, if you wanted information regarding the composition of costs at a summarized level, you needed to create a large number of segments. These segments only differed in the assignment of the allocation cost elements to the secondary cost elements. Allocation structures enable you to reduce maintenance and the runtime of the cycle. 
Business roles: Cost Accountant - Overhead
Controller : 
Sets up and edits organizational structures so that all processes and reports are as accurate as possible. Edits master data, reorganizes company structures, and performs period-end functions.

Cost Accountant - Overhead : 
Defines overhead master data and the period-end allocation cycle. Implements period-end allocation and monitors overhead costs. Reports expenses on the income statement in the period in which they are incurred.
Edit Overhead Allocation Cycles - Cost Centers - Actual
Application component: Cost Center Accounting
App type: SAP GUI
Description:  Overhead allocation allocates primary and secondary costs in Cost Center Accounting and Activity-Based Costing. The following information is passed on to the receivers in this process: The original cost elements are assigned cumulatively, or in groups, to secondary cost elements. The original cost elements are not visible on the receivers.  Sender and receiver information (sender cost center, receiver cost center, or business process) appears in the controlling document.  Overhead allocation using secondary cost elements is useful when the composition of the costs is unimportant for the receiver. For example, cafeteria costs can be allocated to a cost center without the need for a detailed cost breakdown. Note In periodic reposting, distribution, and overhead allocation, line items are written for each sender and receiver. It is not technically possible to restrict the writing of line items. If you repeat period-based allocations within a period, the line items are reversed and overwritten. The posting date of the actual allocation is always the last day of a calendar month. The posting date for plan allocation is always the first day of the calendar month.You cannot allocate consumption quantities using overhead allocation. To allocate activity quantities, you need to use indirect activity allocation. 
Key features:  For overhead allocation, you can summarize all the cost elements into one secondary cost element. When you execute the allocation, all the costs allocated by the sender are included in this cost element. However, this method does not store any information on the receiver regarding the composition of the costs. Alternatively, you can use an allocation structure to define which cost elements are to be allocated under which secondary cost elements. You can assign individual cost elements, cost element groups, or intervals to an allocation cost element. The allocation structure can be stored during segment maintenance. Note Until now, if you wanted information regarding the composition of costs at a summarized level, you needed to create a large number of segments. These segments only differed in the assignment of the allocation cost elements to the secondary cost elements. Allocation structures enable you to reduce maintenance and the runtime of the cycle. 
Business roles: Cost Accountant - Overhead
Cost Accountant - Overhead : 
Defines overhead master data and the period-end allocation cycle. Implements period-end allocation and monitors overhead costs. Reports expenses on the income statement in the period in which they are incurred.

Controller : 
Sets up and edits organizational structures so that all processes and reports are as accurate as possible. Edits master data, reorganizes company structures, and performs period-end functions.
Display Overhead Allocation Cycles - Cost Centers - Actual
Application component: Cost Center Accounting
App type: SAP GUI
Description:  Overhead allocation allocates primary and secondary costs in Cost Center Accounting and Activity-Based Costing. The following information is passed on to the receivers in this process: The original cost elements are assigned cumulatively, or in groups, to secondary cost elements. The original cost elements are not visible on the receivers.  Sender and receiver information (sender cost center, receiver cost center, or business process) appears in the controlling document.  Overhead allocation using secondary cost elements is useful when the composition of the costs is unimportant for the receiver. For example, cafeteria costs can be allocated to a cost center without the need for a detailed cost breakdown. Note In periodic reposting, distribution, and overhead allocation, line items are written for each sender and receiver. It is not technically possible to restrict the writing of line items. If you repeat period-based allocations within a period, the line items are reversed and overwritten. The posting date of the actual allocation is always the last day of a calendar month. The posting date for plan allocation is always the first day of the calendar month.You cannot allocate consumption quantities using overhead allocation. To allocate activity quantities, you need to use indirect activity allocation. 
Key features:  For overhead allocation, you can summarize all the cost elements into one secondary cost element. When you execute the allocation, all the costs allocated by the sender are included in this cost element. However, this method does not store any information on the receiver regarding the composition of the costs. Alternatively, you can use an allocation structure to define which cost elements are to be allocated under which secondary cost elements. You can assign individual cost elements, cost element groups, or intervals to an allocation cost element. The allocation structure can be stored during segment maintenance. Note Until now, if you wanted information regarding the composition of costs at a summarized level, you needed to create a large number of segments. These segments only differed in the assignment of the allocation cost elements to the secondary cost elements. Allocation structures enable you to reduce maintenance and the runtime of the cycle. 
Business roles: Cost Accountant - Overhead
Controller : 
Sets up and edits organizational structures so that all processes and reports are as accurate as possible. Edits master data, reorganizes company structures, and performs period-end functions.

Cost Accountant - Overhead : 
Defines overhead master data and the period-end allocation cycle. Implements period-end allocation and monitors overhead costs. Reports expenses on the income statement in the period in which they are incurred.
Delete Overhead Allocation Cycles - Cost Centers - Actual
Application component: Cost Center Accounting
App type: SAP GUI
Description:  Overhead allocation allocates primary and secondary costs in Cost Center Accounting and Activity-Based Costing. The following information is passed on to the receivers in this process: The original cost elements are assigned cumulatively, or in groups, to secondary cost elements. The original cost elements are not visible on the receivers.  Sender and receiver information (sender cost center, receiver cost center, or business process) appears in the controlling document.  Overhead allocation using secondary cost elements is useful when the composition of the costs is unimportant for the receiver. For example, cafeteria costs can be allocated to a cost center without the need for a detailed cost breakdown. Note In periodic reposting, distribution, and overhead allocation, line items are written for each sender and receiver. It is not technically possible to restrict the writing of line items. If you repeat period-based allocations within a period, the line items are reversed and overwritten. The posting date of the actual allocation is always the last day of a calendar month. The posting date for plan allocation is always the first day of the calendar month.You cannot allocate consumption quantities using overhead allocation. To allocate activity quantities, you need to use indirect activity allocation. 
Key features:  For overhead allocation, you can summarize all the cost elements into one secondary cost element. When you execute the allocation, all the costs allocated by the sender are included in this cost element. However, this method does not store any information on the receiver regarding the composition of the costs. Alternatively, you can use an allocation structure to define which cost elements are to be allocated under which secondary cost elements. You can assign individual cost elements, cost element groups, or intervals to an allocation cost element. The allocation structure can be stored during segment maintenance. Note Until now, if you wanted information regarding the composition of costs at a summarized level, you needed to create a large number of segments. These segments only differed in the assignment of the allocation cost elements to the secondary cost elements. Allocation structures enable you to reduce maintenance and the runtime of the cycle. 
Business roles: Cost Accountant - Overhead
Controller : 
Sets up and edits organizational structures so that all processes and reports are as accurate as possible. Edits master data, reorganizes company structures, and performs period-end functions.

Cost Accountant - Overhead : 
Defines overhead master data and the period-end allocation cycle. Implements period-end allocation and monitors overhead costs. Reports expenses on the income statement in the period in which they are incurred.
Run Overhead Allocation - Cost Centers - Actual
Application component: Cost Center Accounting
App type: SAP GUI
Scope items: Overhead Cost Accounting|Period-End Closing - Plant
Description:  Overhead allocation allocates primary and secondary costs in Cost Center Accounting and Activity-Based Costing. The following information is passed on to the receivers in this process: The original cost elements are assigned cumulatively, or in groups, to secondary cost elements. The original cost elements are not visible on the receivers.  Sender and receiver information (sender cost center, receiver cost center, or business process) appears in the controlling document.  Overhead allocation using secondary cost elements is useful when the composition of the costs is unimportant for the receiver. For example, cafeteria costs can be allocated to a cost center without the need for a detailed cost breakdown. Note In periodic reposting, distribution, and overhead allocation, line items are written for each sender and receiver. It is not technically possible to restrict the writing of line items. If you repeat period-based allocations within a period, the line items are reversed and overwritten. The posting date of the actual allocation is always the last day of a calendar month. The posting date for plan allocation is always the first day of the calendar month.You cannot allocate consumption quantities using overhead allocation. To allocate activity quantities, you need to use indirect activity allocation. 
Key features:  For overhead allocation, you can summarize all the cost elements into one secondary cost element. When you execute the allocation, all the costs allocated by the sender are included in this cost element. However, this method does not store any information on the receiver regarding the composition of the costs. Alternatively, you can use an allocation structure to define which cost elements are to be allocated under which secondary cost elements. You can assign individual cost elements, cost element groups, or intervals to an allocation cost element. The allocation structure can be stored during segment maintenance. Note Until now, if you wanted information regarding the composition of costs at a summarized level, you needed to create a large number of segments. These segments only differed in the assignment of the allocation cost elements to the secondary cost elements. Allocation structures enable you to reduce maintenance and the runtime of the cycle. 
Business roles: Cost Accountant - Overhead
Cost Accountant - Overhead : 
Defines overhead master data and the period-end allocation cycle. Implements period-end allocation and monitors overhead costs. Reports expenses on the income statement in the period in which they are incurred.

Controller : 
Sets up and edits organizational structures so that all processes and reports are as accurate as possible. Edits master data, reorganizes company structures, and performs period-end functions.
Actual Assessment: Overview
Application component: Cost Center Accounting
App type: SAP GUI
Description:  Overhead allocation allocates primary and secondary costs in Cost Center Accounting and Activity-Based Costing. The following information is passed on to the receivers in this process: The original cost elements are assigned cumulatively, or in groups, to secondary cost elements. The original cost elements are not visible on the receivers.  Sender and receiver information (sender cost center, receiver cost center, or business process) appears in the controlling document.  Overhead allocation using secondary cost elements is useful when the composition of the costs is unimportant for the receiver. For example, cafeteria costs can be allocated to a cost center without the need for a detailed cost breakdown. Note In periodic reposting, distribution, and overhead allocation, line items are written for each sender and receiver. It is not technically possible to restrict the writing of line items. If you repeat period-based allocations within a period, the line items are reversed and overwritten. The posting date of the actual allocation is always the last day of a calendar month. The posting date for plan allocation is always the first day of the calendar month.You cannot allocate consumption quantities using overhead allocation. To allocate activity quantities, you need to use indirect activity allocation. 
Key features:  For overhead allocation, you can summarize all the cost elements into one secondary cost element. When you execute the allocation, all the costs allocated by the sender are included in this cost element. However, this method does not store any information on the receiver regarding the composition of the costs. Alternatively, you can use an allocation structure to define which cost elements are to be allocated under which secondary cost elements. You can assign individual cost elements, cost element groups, or intervals to an allocation cost element. The allocation structure can be stored during segment maintenance. Note Until now, if you wanted information regarding the composition of costs at a summarized level, you needed to create a large number of segments. These segments only differed in the assignment of the allocation cost elements to the secondary cost elements. Allocation structures enable you to reduce maintenance and the runtime of the cycle. 
Business roles: Cost Accountant - Overhead
Cost Accountant - Overhead : 
Defines overhead master data and the period-end allocation cycle. Implements period-end allocation and monitors overhead costs. Reports expenses on the income statement in the period in which they are incurred.
Create Distribution Cycles - Cost Centers - Actual
Application component: Cost Center Accounting
App type: SAP GUI
Description: Distribution is used to allocate primary costs. The following information is passed on to the receivers in this process: The original cost element (the primary cost element) remains.Sender and receiver information (sender cost center, receiver cost center, or business process) appears in the Controlling (CO) document. You can use the information system to analyze the distribution results according to sender and receiver relationships.
Edit Distribution Cycles - Cost Centers - Actual
Application component: Cost Center Accounting
App type: SAP GUI
Description: Distribution is used to allocate primary costs. The following information is passed on to the receivers in this process: The original cost element (the primary cost element) remains.Sender and receiver information (sender cost center, receiver cost center, or business process) appears in the Controlling (CO) document. You can use the information system to analyze the distribution results according to sender and receiver relationships.
Display Distribution Cycles - Cost Centers - Actual
Application component: Cost Center Accounting
App type: SAP GUI
Description: Distribution is used to allocate primary costs. The following information is passed on to the receivers in this process: The original cost element (the primary cost element) remains.Sender and receiver information (sender cost center, receiver cost center, or business process) appears in the Controlling (CO) document. You can use the information system to analyze the distribution results according to sender and receiver relationships.
Delete Distribution Cycles - Cost Centers - Actual
Application component: Cost Center Accounting
App type: SAP GUI
Description: Distribution is used to allocate primary costs. The following information is passed on to the receivers in this process: The original cost element (the primary cost element) remains.Sender and receiver information (sender cost center, receiver cost center, or business process) appears in the Controlling (CO) document. You can use the information system to analyze the distribution results according to sender and receiver relationships.
Run Cost Distribution - Cost Centers - Actual
Application component: Cost Center Accounting
App type: SAP GUI
Description: Distribution is used to allocate primary costs. The following information is passed on to the receivers in this process: The original cost element (the primary cost element) remains.Sender and receiver information (sender cost center, receiver cost center, or business process) appears in the Controlling (CO) document. You can use the information system to analyze the distribution results according to sender and receiver relationships.
Display Distribution Overview - Cost Centers - Actual
Application component: Cost Center Accounting
App type: SAP GUI
Description: Distribution is used to allocate primary costs. The following information is passed on to the receivers in this process: The original cost element (the primary cost element) remains.Sender and receiver information (sender cost center, receiver cost center, or business process) appears in the Controlling (CO) document. You can use the information system to analyze the distribution results according to sender and receiver relationships.
Create Periodic Reposting Cycles - Cost Centers - Actual
Application component: Cost Center Accounting
App type: SAP GUI
Description:  Periodic reposting is posting aid that enables you to adjust postings made to your cost centers or business processes, internal orders, or WBS elements. It has the same result as transaction-based reposting. The results of transaction-based repostings have a direct effect on the actual costs of the sender and the receiver, whereas periodic repostings have a one-time effect on actual costs at period-end closing. Postings relevant to Controlling (CO) such as telephone costs, postal charges, insurance, and so on are entered in Financial Accounting (FI) and posted to an allocation cost center or a business process. These are used exclusively for cost collection. This minimizes the number of different account assignments you have to make when entering data in FI. At the end of the period, the collected costs are reposted to the cost centers or business processes which incurred the costs by of means user-defined keys (fixed values or dynamic tracing factors). The original cost element (the primary cost element) is retained. Note During periodic repostings, you can allocate activity-dependent plan costs to receiver objects of the category "cost center" (sender activity type is retained) or "business process".You can allocate activity-independent costs to all receiver object categories, for example, cost centers, business processes, or orders. Note If you are working with transfer prices (multiple valuation approaches) the periodic reposting is executed in parallel in all valuations. The costs to be allocated are taken from the corresponding valuation. The tracing factor is always taken from the values of the operational valuation. The values allocated may differ in each of the valuation methods.Senders and receivers are displayed in the results list, differentiated according to the parallel actual versions of the various valuations.For more information on transfer prices, see the SAP Library under:Financials  Enterprise Controlling (EC)  Profit Center Accounting  Multiple Valuation Approaches/Transfer PricesFinancials  Controlling (CO)  Controlling  Overhead Cost-Controlling  Multiple Valuation Approaches in Overhead Cost Controlling
Edit Periodic Reposting Cycles - Cost Centers - Actual
Application component: Cost Center Accounting
App type: SAP GUI
Description:  Periodic reposting is posting aid that enables you to adjust postings made to your cost centers or business processes, internal orders, or WBS elements. It has the same result as transaction-based reposting. The results of transaction-based repostings have a direct effect on the actual costs of the sender and the receiver, whereas periodic repostings have a one-time effect on actual costs at period-end closing. Postings relevant to Controlling (CO) such as telephone costs, postal charges, insurance, and so on are entered in Financial Accounting (FI) and posted to an allocation cost center or a business process. These are used exclusively for cost collection. This minimizes the number of different account assignments you have to make when entering data in FI. At the end of the period, the collected costs are reposted to the cost centers or business processes which incurred the costs by of means user-defined keys (fixed values or dynamic tracing factors). The original cost element (the primary cost element) is retained. Note During periodic repostings, you can allocate activity-dependent plan costs to receiver objects of the category "cost center" (sender activity type is retained) or "business process".You can allocate activity-independent costs to all receiver object categories, for example, cost centers, business processes, or orders. Note If you are working with transfer prices (multiple valuation approaches) the periodic reposting is executed in parallel in all valuations. The costs to be allocated are taken from the corresponding valuation. The tracing factor is always taken from the values of the operational valuation. The values allocated may differ in each of the valuation methods.Senders and receivers are displayed in the results list, differentiated according to the parallel actual versions of the various valuations.For more information on transfer prices, see the SAP Library under:Financials  Enterprise Controlling (EC)  Profit Center Accounting  Multiple Valuation Approaches/Transfer PricesFinancials  Controlling (CO)  Controlling  Overhead Cost-Controlling  Multiple Valuation Approaches in Overhead Cost Controlling
Display Periodic Reposting Cycles - Cost Centers - Actual
Application component: Cost Center Accounting
App type: SAP GUI
Description:  Periodic reposting is posting aid that enables you to adjust postings made to your cost centers or business processes, internal orders, or WBS elements. It has the same result as transaction-based reposting. The results of transaction-based repostings have a direct effect on the actual costs of the sender and the receiver, whereas periodic repostings have a one-time effect on actual costs at period-end closing. Postings relevant to Controlling (CO) such as telephone costs, postal charges, insurance, and so on are entered in Financial Accounting (FI) and posted to an allocation cost center or a business process. These are used exclusively for cost collection. This minimizes the number of different account assignments you have to make when entering data in FI. At the end of the period, the collected costs are reposted to the cost centers or business processes which incurred the costs by of means user-defined keys (fixed values or dynamic tracing factors). The original cost element (the primary cost element) is retained. Note During periodic repostings, you can allocate activity-dependent plan costs to receiver objects of the category "cost center" (sender activity type is retained) or "business process".You can allocate activity-independent costs to all receiver object categories, for example, cost centers, business processes, or orders. Note If you are working with transfer prices (multiple valuation approaches) the periodic reposting is executed in parallel in all valuations. The costs to be allocated are taken from the corresponding valuation. The tracing factor is always taken from the values of the operational valuation. The values allocated may differ in each of the valuation methods.Senders and receivers are displayed in the results list, differentiated according to the parallel actual versions of the various valuations.For more information on transfer prices, see the SAP Library under:Financials  Enterprise Controlling (EC)  Profit Center Accounting  Multiple Valuation Approaches/Transfer PricesFinancials  Controlling (CO)  Controlling  Overhead Cost-Controlling  Multiple Valuation Approaches in Overhead Cost Controlling
Delete Periodic Reposting Cycles - Cost Centers - Actual
Application component: Cost Center Accounting
App type: SAP GUI
Description:  Periodic reposting is posting aid that enables you to adjust postings made to your cost centers or business processes, internal orders, or WBS elements. It has the same result as transaction-based reposting. The results of transaction-based repostings have a direct effect on the actual costs of the sender and the receiver, whereas periodic repostings have a one-time effect on actual costs at period-end closing. Postings relevant to Controlling (CO) such as telephone costs, postal charges, insurance, and so on are entered in Financial Accounting (FI) and posted to an allocation cost center or a business process. These are used exclusively for cost collection. This minimizes the number of different account assignments you have to make when entering data in FI. At the end of the period, the collected costs are reposted to the cost centers or business processes which incurred the costs by of means user-defined keys (fixed values or dynamic tracing factors). The original cost element (the primary cost element) is retained. Note During periodic repostings, you can allocate activity-dependent plan costs to receiver objects of the category "cost center" (sender activity type is retained) or "business process".You can allocate activity-independent costs to all receiver object categories, for example, cost centers, business processes, or orders. Note If you are working with transfer prices (multiple valuation approaches) the periodic reposting is executed in parallel in all valuations. The costs to be allocated are taken from the corresponding valuation. The tracing factor is always taken from the values of the operational valuation. The values allocated may differ in each of the valuation methods.Senders and receivers are displayed in the results list, differentiated according to the parallel actual versions of the various valuations.For more information on transfer prices, see the SAP Library under:Financials  Enterprise Controlling (EC)  Profit Center Accounting  Multiple Valuation Approaches/Transfer PricesFinancials  Controlling (CO)  Controlling  Overhead Cost-Controlling  Multiple Valuation Approaches in Overhead Cost Controlling
Run Periodic Reposting - Cost Centers - Actual
Application component: Cost Center Accounting
App type: SAP GUI
Description:  Periodic reposting is posting aid that enables you to adjust postings made to your cost centers or business processes, internal orders, or WBS elements. It has the same result as transaction-based reposting. The results of transaction-based repostings have a direct effect on the actual costs of the sender and the receiver, whereas periodic repostings have a one-time effect on actual costs at period-end closing. Postings relevant to Controlling (CO) such as telephone costs, postal charges, insurance, and so on are entered in Financial Accounting (FI) and posted to an allocation cost center or a business process. These are used exclusively for cost collection. This minimizes the number of different account assignments you have to make when entering data in FI. At the end of the period, the collected costs are reposted to the cost centers or business processes which incurred the costs by of means user-defined keys (fixed values or dynamic tracing factors). The original cost element (the primary cost element) is retained. Note During periodic repostings, you can allocate activity-dependent plan costs to receiver objects of the category "cost center" (sender activity type is retained) or "business process".You can allocate activity-independent costs to all receiver object categories, for example, cost centers, business processes, or orders. Note If you are working with transfer prices (multiple valuation approaches) the periodic reposting is executed in parallel in all valuations. The costs to be allocated are taken from the corresponding valuation. The tracing factor is always taken from the values of the operational valuation. The values allocated may differ in each of the valuation methods.Senders and receivers are displayed in the results list, differentiated according to the parallel actual versions of the various valuations.For more information on transfer prices, see the SAP Library under:Financials  Enterprise Controlling (EC)  Profit Center Accounting  Multiple Valuation Approaches/Transfer PricesFinancials  Controlling (CO)  Controlling  Overhead Cost-Controlling  Multiple Valuation Approaches in Overhead Cost Controlling
Display Actual Cost Line Items - Sales Orders
Application component: Information System
App type: SAP GUI
Description: Line item reports enable you to analyze posted values in detail. The line items in the reports are based on the items of documents generated by postings. Line item reports are available in the following areas: Product Cost by OrderProduct Cost by PeriodProduct Cost by Sales Order You can access the original documents (such as the FI or MM document) from the individual items in the report (Environment  Source Document / Accounting Document). In Cost Object Controlling, line item reports are of limited importance because the posting amounts from production confirmations are generally high, making analysis at the line item level worthwhile only in exceptional circumstances. You can restrict the line items displayed through the cost element or cost element group and by specifying a time frame. Line item reports are available for the following account assignment objects: Manufacturing Orders Line items actualLine items for WIP calculationLine items varianceLine items commitment  Product Cost Collectors Line items actualLine items WIP calculation (if the corresponding settings in the results analysis version were made, see also Prerequisites)Line items variance  Sales Document Item Line items actualLine items for results analysisLine items commitment Line item reports are supplied with a predefined layout. You can also create custom layouts so that you can see other fields of the CO line item, such as the value type. You can usually display all the fields of the Controlling document in the line item report. These fields are grouped into: Account assignmentTime characteristicsReferencesValue key figuresTechnical fieldsOrganizational unitsPartner account assignmentObjectOther objectsQuantity key figuresInvestment managementNot assigned  
Business roles: Cost Accountant - Sales
Controller : 
Sets up and edits organizational structures so that all processes and reports are as accurate as possible. Edits master data, reorganizes company structures, and performs period-end functions.

Cost Accountant - Sales : 
Analyzes markets, products, customers, distribution channels, and discount strategies. Reports and monitors KPIs for incoming orders, revenue, and margins. Contributes to fulfilling the organization’s sales strategy.
Display Sales Order Commitment Items - Sales Items
Application component: Overhead Cost Controlling
App type: SAP GUI
Description: Line item reports enable you to analyze posted values in detail. The line items in the reports are based on the items of documents generated by postings. Line item reports are available in the following areas: Product Cost by OrderProduct Cost by PeriodProduct Cost by Sales Order You can access the original documents (such as the FI or MM document) from the individual items in the report (Environment  Source Document / Accounting Document). In Cost Object Controlling, line item reports are of limited importance because the posting amounts from production confirmations are generally high, making analysis at the line item level worthwhile only in exceptional circumstances. You can restrict the line items displayed through the cost element or cost element group and by specifying a time frame. Line item reports are available for the following account assignment objects: Manufacturing Orders Line items actualLine items for WIP calculationLine items varianceLine items commitment  Product Cost Collectors Line items actualLine items WIP calculation (if the corresponding settings in the results analysis version were made, see also Prerequisites)Line items variance  Sales Document Item Line items actualLine items for results analysisLine items commitment Line item reports are supplied with a predefined layout. You can also create custom layouts so that you can see other fields of the CO line item, such as the value type. You can usually display all the fields of the Controlling document in the line item report. These fields are grouped into: Account assignmentTime characteristicsReferencesValue key figuresTechnical fieldsOrganizational unitsPartner account assignmentObjectOther objectsQuantity key figuresInvestment managementNot assigned
Process Withholding Tax Settlements - Kuwait
Application component: Kuwait
App type: SAP GUI
Business roles: General Ledger Accountant for Kuwait
General Ledger Accountant for Kuwait: (is an add-on role to the General Ledger Accountant)
Carries out the most important functions in general ledger accounting with a special focus on creation and execution for Kuwait.
Generate Subcontractor Payments Statement
Application component: Kuwait
App type: SAP GUI
Business roles: Accounts Payable Accountant for Kuwait
Accounts Payable Accountant for Kuwait: (is an add-on role to the Accounts Payable Accountant)
Carries out the most important functions in accounts payable accounting with a special focus on creation and execution for Kuwait.
Maintain Costing Sheet
Application component: Overhead Orders
App type: SAP GUI
Controller : 
Sets up and edits organizational structures so that all processes and reports are as accurate as possible. Edits master data, reorganizes company structures, and performs period-end functions.

Cost Accountant - Overhead : 
Defines overhead master data and the period-end allocation cycle. Implements period-end allocation and monitors overhead costs. Reports expenses on the income statement in the period in which they are incurred.
Create Transfer Requirement
Application component: Warehouse Management (for Extended WM please use SCM-EWM*)
App type: SAP GUI
Description:   Stock movements are planned and triggered via the transfer requirement. Transfer requirements form the basis for creation of transfer orders that are used to carry out physical goods movements.  
Key features:   You can create transfer requirements  Automatically by posting a goods movement in Inventory Management  Automatically by requesting materials using the Production Planning system  Manually using WM   You can create transfer requirements with or without reference to other system documents. Note  You can create a transfer requirement With reference...       to a material document    to move stock into or out of the warehouse     to a production order    to supply required materials to a production supply area    Without reference...    to move stock from one bin to another in the warehouse       to request crate parts and release order parts to replenish their assigned storage bins in production supply areas       to initiate the replenishment of fixed bins in WM     Transfer requirement updates   A transfer requirement is updated by the system  When you create, confirm or cancel a transfer order  Once you have confirmed the corresponding transfer order, the system updates the field for the open transfer order items in the transfer requirement. When the entire quantity of a transfer requirement has been processed by a transfer order, that is, all items have been processed, the system sets the Header status to E, meaning that the transfer requirement is completed.  When you cancel a goods receipt posting or a goods issue posting in Inventory Management  Sometimes when a goods receipt or goods issue posting is canceled in IM, an open transfer requirement exists for the quantity being canceled. This can happen if the goods have not yet been transferred in WM, that is, a transfer order has not been created. In this case, the system automatically determines if a corresponding transfer requirement exists. If it finds one, the system reduces the quantity in the transfer requirement by the quantity being canceled or deletes the transfer requirement if the entire quantity is to be canceled.
Print System Inventory Record
Application component: Warehouse Management (for Extended WM please use SCM-EWM*)
App type: SAP GUI
Description:   You use printouts of the physical inventory document to perform the physical inventory of the storage bins.
Inventory History for Storage Bin
Application component: Warehouse Management (for Extended WM please use SCM-EWM*)
App type: SAP GUI
Description:   You use the inventory to regularly carry out a physical inventory in your warehouse. You compare the material stocks that are physically present with the data managed in the Warehouse Management system (WMS). You enter inventory differences, as recorded in the results of the physical inventory, to update the accounting side of the stock data. The inventory is regarded as completed if an inventory was taken for every storage bin in the warehouse at least once during the fiscal year.  
Key features:   In the warehouse, you specify the appropriate inventory procedure for each storage type. You first need to decide whether you want to carry out the inventory as an annual inventory , or as a continuous inventory.  A warehouse managed using the WMS is basically suited for using continuous inventory , because the WMS ensures continuous updates of the storage bins and stock movements. The Warehouse Management system (WMS) supports the following inventory procedures for continuous inventory:  Continuous Inventory  Continuous Inventory During Putaway  Continuous Inventory During Stock Removal (Zero Stock Check)  Cycle Counting Inventory per Bin  Cycle Counting Inventory at Quant Level  Inventory Sampling (MM-IM-PI)   You can carry out the inventory sampling procedure in both Inventory Management (MM-IM) and the WMS.  The Inventory Overview function is a central access point into inventory processing for the WMS. From here you can monitor and process all essential activities for the inventory. In the SAP Menu, choose Logistics  Logistics Execution  Internal Whse Processes  Physical Inventory  In Warehouse Management  Physical Inventory Document   Overview .  Inventory of Handling Units   The inventory for handling units is based on the outermost handling unit. Because in the Warehouse Management System this is the same as a storage unit (SU), you carry out the inventory in the same way as for a normal inventory.  For more information on entering inventory differences for nested handling units (HUs), see Physical Inventory of Handling Units .  Inventory of Batches or Special Stocks   If you carry out an inventory for materials subject to batch management, or for special stocks, you do not only compare the material stock in the storage bin with the data managed in the system. You also check whether the batch or special stock information in the system matches the actual batch or special stock in the storage bin. For more information, see Inventory of Batches or Special Stocks . .
Start Inventory Recount
Application component: Warehouse Management (for Extended WM please use SCM-EWM*)
App type: SAP GUI
Description:   Entering inventory count results in the Warehouse Management system (WMS) causes differences to occur between the actual counted quantity and the inventory balance for the storage bin or quant. You store the inventory differences in the WMS in order to correct the inventory balance in the warehouse.  If the material has been lost, a negative quant appears in the interim storage area for differences.  If the material has been found, then a positive quant appears in the interim storage area for differences.   You clear these differences from the WMS and enter them in Inventory Management (MM-IM).
Clear Differences - Warehouse
Application component: Warehouse Management (for Extended WM please use SCM-EWM*)
App type: SAP GUI
Description:   Entering inventory count results in the Warehouse Management system (WMS) causes differences to occur between the actual counted quantity and the inventory balance for the storage bin or quant. You store the inventory differences in the WMS in order to correct the inventory balance in the warehouse.  If the material has been lost, a negative quant appears in the interim storage area for differences.  If the material has been found, then a positive quant appears in the interim storage area for differences.   You clear these differences from the WMS and enter them in Inventory Management (MM-IM).
Clear Differences - MM-IM
Application component: Warehouse Management (for Extended WM please use SCM-EWM*)
App type: SAP GUI
Description:   Entering inventory count results in the Warehouse Management system (WMS) causes differences to occur between the actual counted quantity and the inventory balance for the storage bin or quant. You store the inventory differences in the WMS in order to correct the inventory balance in the warehouse.  If the material has been lost, a negative quant appears in the interim storage area for differences.  If the material has been found, then a positive quant appears in the interim storage area for differences.   You clear these differences from the WMS and enter them in Inventory Management (MM-IM).