Profit Center
Accounting: Assignment Monitor
This transaction
is used to monitor the assignment of master data to profit centers. Internal
orders, business processes, cost centers, cost objects, materials and work
breakdown structure lists can be displayed for master data that has been
assigned a profit center and for non assignments to a profit center. Profit
centers are posted via these assignments, so it is important to ensure that all
master data has been assigned.
Profit Center
Accounting: Transfer Payables/Receivables
This transaction
is used to pull accounts payable and receivable line items into profit center
accounting. The line items are created from the profit center accounting
assignment on the offset posting to the accounts payable and accounts
receivable posting. Select the period and fiscal year to be posted and the
relevant company codes and then execute.
Copy Cost Center
Groups
Use this
transaction to copy cost center groups to profit center groups within the same
controlling area. This is a useful utility if your cost center groups are
similar to your profit center groups. Enter the cost center group and execute.
Once created, the profit centers within the profit center group can be changed.
The utility also gives you the ability to select the standard hierarchy only
and then assign the profit centers into groups in a second step.
Copy Cost Centers
Use this
transaction to create profit centers from cost centers within the same
controlling area. Select the cost center group and execute. This transaction
will create profit centers for all the cost centers within the cost center
group selected.
Display Profit
Center Change Documents
This transaction
will report on changes made to the profit center master. A date range can be
selected. The changes are date and time stamped and you can drill down to
review the old/new field value input.
Change Plan Costs/Revenues:
Characteristics
This transaction is used to plan costs and revenue elements
at the profit center level. Enter the version of the plan, the period range,
the fiscal year, the company code, the profit center and the account for a
default planning layout. The layout can be changed via the menu path
Go to • Next Layout. Select Enter in free form input mode and you can enter the plan by period.
Display Plan
Costs/Revenues: Characteristics can
be changed via the menu path Go to • Next Layout. Select Enter to
display the plan by period.
Display Document
Use this
transaction to display a profit center accounting document. Select one of the
standard delivered layouts, the document number range, fiscal year, leave the
document type as the default and click Execute to display the document data.
Create Cost
Estimate with Quantity Structure
This transaction
is used to create a standard cost estimate for a material with a quantity
structure. Enter the material and plant for the cost estimate. Then enter the
costing variant, which controls the type/cost components to be included in the
estimate and the quantity structure (i.e., BOM's and Routings). Enter the
costing version and the costing lot size (if left blank, the material master
will determine the costing lot size) and click Enter. The standard cost estimate will be calculated which can be analyzed
by cost component or by cost element.
Display Cost
Estimate with Quantity Structure
Use this
transaction to display the cost estimate for a material with a quantity
structure. Enter the material and plant for the cost estimate, the costing variant,
version and click Enter.
The standard cost estimate will be displayed which can be analyzed by cost
component or by cost element.
Price Update
This transaction
is used to mark and release a standard cost estimate for a material that has
been created using transaction CK11N. Before marking can take place, the period
for marking must be activated. Enter the posting period, fiscal year and
activate marking. Then choose the company code and plant for the update; you
can further restrict the selection by entering a material number range. Then
execute marking, which typically is for a future period and then follow up with
releasing the standard cost, which typically results in a revaluation of the
materials inventory.
Edit Costing Run
This transaction
is used to create a standard cost estimate, report, mark and release for a
range of materials with a quantity structure. This transaction is the same as
transaction CK11N and CK24 but for multiple materials at the same time. Enter a
costing run number and date, click Create and enter a description. Then proceed to enter the control
settings (e.g., costing variant) in the General sub area, then run the cost estimate, mark and release in the
Processing
sub area and review the results in the Costing
Results area.
Create Additive
Cost
This transaction is used to create a manual cost estimate for
a material, save it and have it be included in a standard cost estimate using
transaction CK11N. Enter the material and plant, the costing variant and click Enter. Then various costing methods can be chosen and then saved.
Note that to have the additive cost estimates included in the standard cost
estimate using transaction CK11N, the cost variant must be customized to allow
it to accept additive cost estimates.
CK75N
Change Additive
Cost
Use this
transaction to change a manual cost estimate for a material. Enter the material
and plant, the costing variant and click Enter. Then various costing methods can be chosen and then saved.
Note that to have the additive cost estimate included in the standard cost
estimate using transaction CK11N, the cost variant must be customized to allow
it to accept additive cost estimates.
CK76N
Display Additive
Cost
Use this
transaction to display a manual cost estimate for a material. Enter the
material and plant for the cost estimate, the costing variant and click Enter.
CO43
Actual Overhead
Calculation: Collective Processing
This transaction
is used to apply overhead costs to multiple production orders based upon an
overhead costing sheet as part of the product costing period end closing
process. The overhead costing sheet will calculate the overhead cost based on a
base cost element and an overhead rate. The production order will typically be
debited and a cost center (defined on the costing sheet) will be credited.
Enter the plant, the type of production object, period, fiscal year and execute
to apply the overhead. To execute the function for one production order use
transaction KGI2.
KA01
Create Cost Element
This transaction
is used to create a primary cost element. There are two types of cost element.
First, a primary cost element, which is typically a one to one match to a
general ledger profit and loss account and relates to costs and revenues that
are incurred externally to the organization. Additionally, there are secondary
cost elements, which are costs incurred internal to the organization and are
represented by transactions that exist only in the controlling module. You can
create the primary cost elements directly from the profit and loss general
ledger master record or you can use this transaction but you first must create
a general ledger account. Enter the name and description and then ensure that
the correct cost element category is selected (i.e., different cost element
categories relate to primary costs, assessments, overhead cost etc.) and then
click Save.
KA02
Change Cost
Element
This transaction
is used to change a cost element. There are two types of cost element. First, a
primary cost element, which is typically a one to one match to a general ledger
profit and loss account and relates to costs and revenues that are incurred
externally to the organization. In addition, there are secondary cost elements,
which are costs incurred internally to the organization and are represented by
transactions that exist only in the controlling module.
KA03
Display Cost
Element
This transaction is used to display a cost element. There are
two types of cost element. First, a primary cost element, which is typically a
one to one match to a general ledger profit and loss account and relates to
costs and revenues that are incurred externally to the organization. In
addition, there are secondary cost elements, which are costs incurred
internally to the organization and are represented by transactions that exist
only in the controlling module.
KA04
Delete Cost
Element
This transaction
is used to delete a cost element however you can only delete a cost element if
no postings have been made to it in the productive client. If postings have
been made to the cost element then you must set the deletion flag on the cost
element and then execute the archiving process.
KA05
Display Cost
Element Changes
Use this
transaction to display changes to the cost element master data. A change date
from can be selected and/or the user ID, both of which can be left blank to
display all changes. Once in the report you can drill down on any changes to
display the old/new field value, date of change and the user ID of the
individual making the change.
KA06
Create Secondary
Cost Element
This transaction
is used to create a secondary cost element. There are two types of cost
element. First, a primary cost element, which is typically a one to one match
to a general ledger profit and loss account and relates to costs and revenues
that are incurred externally to the organization. In addition, there are
secondary cost elements, which are costs incurred internally to the
organization and are represented by transactions that exist only in the controlling
module. Enter the name and description and then ensure that the correct cost
element category is selected (i.e., different cost element categories relate to
primary costs, assessments, overhead cost etc.) and then click Save.
KA23
Display Cost Element
Collective
Use this
transaction to display/report on multiple cost elements. You have the option to
select cost elements individually, by cost element group, by a selection
variant or all cost elements within a controlling area within a certain validity
period. The list displays the master data information and you have the option
to drill down into the actual master record.
KA24
Delete Cost
Elements Collective
Use this
transaction to delete multiple cost element master record. However, you can
only delete a cost element if no postings have been made to it in the
productive client. If postings have been made to the cost element then you must
set the deletion flag on the cost element and then execute the archiving
process. You have the option to select cost elements individually, by cost
element group, by a selection variant or all cost elements within a controlling
area within a certain validity period.
KABL
Planning Report
Use this
transaction to report on overall planning for an internal order. Select an
individual internal order, fiscal year, period from/to and plan version. The
report can also be displayed in ALV format. The default layout will display
plan data by cost element with drill down capability.
KAH1
Create Cost
Element Group data.
KAH2
Change Cost
Element Group
This transaction
can be used to change a cost element group. The cost element group can be
created in a hierarchy with nodes and sub nodes with the cost element assigned
to the lowest level. Cost element groups can be used for reporting purpose in
order to summarize data.
KAH3
Display Cost
Element Group
Use this
transaction to display a cost element group. The cost element group can be
created and displayed in a hierarchy with nodes and sub nodes with the cost
elements assigned to the lowest level. Cost element groups can be used for
reporting purpose in order to summarize data.
KAK2
Change View
"Statistical Key Figures”: Overview
This transaction
is used to change multiple statistical key figure master records at one time. A
statistical key figure is part of cost center accounting master data and is
used in key figure analysis and as a basis for internal allocation such as
distributions and assessments. You can also create new statistical key figures
using this transaction. Furthermore, you can change existing statistical key
figures text, unit of measure and category.
KAK3
Display View
"Statistical Key Figures”: Overview
This transaction
is used to display multiple statistical key figure master records. A
statistical key figure is part of cost center accounting master data and is
used in key figure analysis and as a basis for internal allocations such as
distributions and assessments. You can display existing statistical key figures
text, unit of measure and category.
KB11N
Enter Manual
Reposting of Costs
This transaction
is used to repost costs manually whereby the original cost element is always
retained. This function is designed mainly to adjust posting errors. You should
normally adjust posting errors in the application component where they
originally occurred. This transaction ensures that external and internal
accounting postings are reconciled. You can only adjust posting errors
involving one cost accounting object (a cost center or internal order for
example) using a transaction-based reposting. Enter the document date, posting
date, select the screen variant, the cost object, the receiving cost object and
the amount to be posted and save.
KB13N
Display Manual
Reposting of Costs
Use this
transaction to display a reposting of costs. Correction postings are normally
adjusted in the application component where they originally occurred. This
transaction ensures that external and internal accounting postings are always
reconciled. The adjusted posting errors involve one cost accounting object (a
cost center or internal order for example) using a transaction-based reposting.
Enter the document number and click Enter.
KB14N
Reverse Manual Reposting of Costs
Use this
transaction to reverse a reposting of cost. Correction postings are normally
adjusted in the application component where they originally occurred. This
transaction ensures that external and internal accounting postings are always
reconciled. The adjusted posting errors involve one cost accounting object (a
cost center or internal order for example) using a transaction-based reposting.
Input the document number and click Enter. The reposting sending and receiving cost objects are
reversed and then save the document.
KB21N
Enter Direct
Activity Allocation
Use this
transaction for direct activity allocation, which involves the measuring,
recording, and allocating of business services performed. To do this, you must
create the appropriate cost activities and tracing factors (allocation bases,
which can be used as cost drivers). These are known as activity types in cost
center accounting. Activity allocation occurs, for example, when business
transactions are confirmed or activities are recorded. The system multiplies
the activity produced by the activity price of the activity type.
KB23N
Display Direct
Activity Allocation
Use this
transaction to display an activity allocation. Activity allocation involves the
measuring, recording, and allocating of business services performed. To do
this, you must create appropriate cost activities and tracing factors
(allocation bases, which can be used as cost drivers). These are known as
activity types in cost center accounting. Input the document number and click Enter.
KB24N
Reverse Direct
Activity Allocation
This transaction
is used to reverse a direct activity allocation made using transaction KB21N.
Enter the document date, posting date and document number of the transaction
you want to reverse. Execute the transaction and the reverse activity
allocation will be displayed. Save the posting and a new document number will
be issued for the reversal.
KB31N
Enter Statistical
Key Figures
This transaction
is used to enter actual statistical key figures, which can be used as a basis
for internal allocations, such as distributions and assessments and key figure
analysis. Statistical key figures can be planned and actuals posted on a cost
center, internal order, or other cost object. Enter actual statistical key
figures to cost centers or internal orders using this transaction. Enter the
document date, posting date, select the screen variant, the statistical key
figure, the receiving cost center or internal order and the quantity to be
posted and save.
KB33N
Display
Statistical Key Figures
This transaction
is used to display the actual statistical key figures entered, which can be
used as a basis for internal allocations, such as distributions and assessments
and key figure analysis. Statistical key figures can be planned and actuals
posted on a cost center, internal order, or other cost object. Input the
document number and click Enter to
display the posting.
KB34N
Reverse
Statistical Key Figures reverse. Click Enter
to display the reverse statistical key figure posting. Click Save
to post the new document number for the reversal.
KB41N
Enter Manual
Reposting of Revenues
This transaction
is used to repost revenues whereby the original cost element is always
retained. This function is designed mainly to adjust posting errors. You should
normally adjust posting errors in the application component where they
originally occurred. This transaction ensures that external and internal
accounting postings are always reconciled. You can only adjust posting errors
involving one cost accounting object (a cost center or internal order for
example) using a transaction-based reposting. Enter the document date, posting
date, select the screen variant, the cost object, the receiving cost object and
the amount to be posted and save.
KB43N
Display Manual
Reposting of Revenues
Use this
transaction to display a reposting of revenues. Correction postings are
normally adjusted in the application component where they originally occurred.
This transaction ensures that external and internal accounting postings are
always reconciled. The adjusted posting errors involve one cost accounting
object (a cost center or internal order for example) using a transaction-based
reposting. Input the document number and click Enter.
KB44N
Reverse Manual
Reposting of Revenues
Use this
transaction to reverse a reposting of revenues. Correction postings are
normally adjusted in the application component where they originally occurred.
This transaction ensures that external and internal accounting postings are
always reconciled. The adjusted posting errors involve one cost accounting
object (a cost center or internal order for example) using a transaction-based
reposting. Input the document number and click Enter. The reposting sending and receiving cost object reversal is
then displayed, click Save to
post the document.
KB65
Enter IAA
Reposting: Document Row Selection
Use this
transaction to repost cost from one cost object to another that has previously
been posted using activity allocation. This function is designed mainly to
adjust posting errors. You should normally adjust posting errors in the
application component where they originally occurred. When reposting a line
item, the full amount and quantity is reposted. Note: once a document has been
"reposted" it cannot be corrected by another reposting transaction.
Input the original document number that needs to be corrected, click Enter
to display and correct and then save the document.
KB66
Display IAA
Reposting: Document Row Selection
Use this
transaction to display a reposting of an internal activity allocation.
Correction postings are normally adjusted in the application component where
they originally occurred. This transaction ensures that external and internal
accounting postings are always reconciled. The adjusted posting errors involve
one cost accounting object (a cost center or internal order for example) using
a transaction-based reposting. Enter the document number and click Enter.
KB67
Reverse IAA Reposting: Document Row Selection
Use this
transaction to reverse a reposting of an internal activity allocation. Input
the document number and click Enter.
The reposting sending and receiving cost objects are reversed and then save the
document to post the reversal.
KBH1
Create Statistical
Key Figure Group
This transaction
is used to create a statistical key figure group. When several statistical key
figures have been created, a statistical key figure group may be necessary for
reporting and monitoring the contents of the group. For example, a statistical
key figure (SKF) type group could be created for all SKFs managed by
manufacturing or all SKFs managed by finance, etc. This will help assign
responsibility for large numbers of SKFs. Enter the SKF group name, click Enter, assign the SKF's to nodes in the group and save.
KBH2
Change
Statistical Key Figure Group
Use this
transaction to change a statistical key figure group. Enter the SKF group name,
click Enter, change the SKF assignment and save your changes.
KBH3
Display
Statistical Key Figure Group
Use this
transaction to display a statistical key figure group. Enter the SKF group
name, click Enter,
and review the SKF assignment.
KCH1
Create Profit
Center Group
This transaction
is used to create a profit center group, which is a hierarchy structure of
profit centers. Profit center groups are used for profit reporting, allocations
or in various planning functions, where it is desirable to display profit data
at a high level of detail. Enter the profit center group key, which will be the
top level of the hierarchy, click Enter, create lower level nodes, assign profit centers to the
lowest node and click Save.
KCH2
Change Profit
Center Group
Use this transaction to change a profit center group, which
is a hierarchy structure of profit centers. Profit center groups are used for
profit reporting, allocations or in various planning functions, where it is
desirable to display profit data at a high level of detail. Enter the profit
center group key, which will be the top level of the hierarchy, click Enter, create or change lower level nodes, assign/reassign profit
centers to nodes and click Save.
KCH3
Display Profit
Center Group
Use this
transaction to display a profit center group, which is a hierarchy structure of
profit centers. Profit center groups are used for profit reporting, allocations
or in various planning functions, where it is desirable to display profit data
at a high level of detail. Enter the profit center group key and click Enter
to display the hierarchical structure.
KCH5N
Standard Hierarchy for Profit Centers Change
to change it,
first, when maintaining the profit center master data and second, using this
transaction you can also maintain the profit centers master data.
KCH6N
Standard
Hierarchy for Profit Centers Display
Use this
transaction to change the standard hierarchy for profit centers, which is a
special type of profit center group that contains all the profit centers in a
controlling area. Profit center master data is required to be assigned to at
least one level in the profit center standard hierarchy. Input the profit
center group key and click Enter to
display the hierarchical structure.
KE21N
CO-PA Line Item
Entry
This transaction
is typically only used in exception circumstances since data is usually
transferred to Profitability Analysis (CO-PA) automatically. However, if a
correction posting is required then use this transaction. Enter the appropriate
document type, the posting date, select the valuation type, currency setting,
click Enter, input the characteristics, value fields and origin data, if
necessary and then click Save.
KE24
Line Item Display
- Actual Data
This transaction
is used to report on actual line item postings in Profitability Analysis
(CO-PA). Selection criteria include record type, which will narrow the list to
the origin of the posting. The layout display can be changed to suit user
requirements.
KE25
Line Item Display
- Plan Data
This transaction
is used to report on plan line item postings in Profitability Analysis (CO-PA).
Selection criteria include record type, which will narrow the list to the
origin of the posting. The layout display can be changed to suit user
requirements.
KE27
Periodic
Valuation
Use this transaction
is used to periodically valuate actual data, which has previously been posted
to Profitability Analysis (CO-PA). The system posts the difference between the
original values of the line item and the new values in a new, separate line
item. For valuation using material cost estimates, you can choose the
alternative option of displaying the periodically calculated values separately
from the original values. This function is available for the record types A
(incoming sales orders) and F (billing data) as well as user-defined record
types, which you select on the initial screen. Also, at execution time select
the period for valuation. The program can be executed in update or test mode.
Once you have performed periodic valuation in update mode, you can display the
new values in the information systems reports.
KE2B
Subsequent
Posting Incoming Sales Orders
Use this
transaction to retransfer incoming sales order from SD to Profitability
Analysis (CO- PA). Errors may occur for example, if the standard cost valuation
of a material has not been released at the time of the transfer. The system
saves the "original" records that contain errors in a separate table,
which can be viewed using this transaction. Once the error has been corrected
you can use this transaction to retransfer the sales order to CO-PA.
KE2C
Delete Incoming
Sales Orders Containing Errors
Use this
transaction to delete any errors from the transfer of incoming sales orders
from SD to Profitability Analysis (CO-PA). The system saves the "original"
records that contain errors in a separate table, which can be viewed using
transaction KE2D. Once the error has been corrected and retransferred using
transaction KE2B you can use this transaction to delete the sales order from
the error table.
KE2D
Display Incoming
Sales Orders Containing Errors
This transaction
is used to analyze errors from the transfer of incoming sales orders from SD to
Profitability Analysis (CO-PA). You can value incoming sales orders (as
expected revenues) and transfer them from SD to CO-PA in order to obtain an
early estimate of anticipated profits. Errors may occur for example, if the
standard cost valuation of a material has not been released at the time of the
transfer. The system saves the "original" records that contain errors
in a separate table, which can be viewed using this transaction. Once the error
has been corrected you can use transaction KE2B to retransfer the sales order.
KE30
Execute
Profitability Report
This transaction
is used to access and execute Profitability Analysis (CO-PA) reports. When you
call up a drill-down report, you can have the system either select new data or
read saved report data that was selected and saved at an earlier point in time.
In order to make it as easy as possible for users to execute a report, SAP lets
you make most of the settings when you define the report. When you execute the
report, you can also determine how the report is displayed and make the
appropriate settings. Select the report, click Execute, input section criteria and then execute the report.
KE31
Create
Profitability Report
Use this
transaction to create a Profitability Analysis (CO-PA) report. CO-PA allows the
user to "slice and dice" information derived from other SAP modules
(customer billing, internal orders, direct FI postings) to provide a view of
customer and product profitability. When creating a report, the user will
select which variables, characteristics and value fields are contained in the
report. A CO-PA report can be created without or with a form. A form will allow
the user, to create separately, a form/report layout that can be standardized
and used across multiple reports.
KE32
Change
Profitability Report
Use this
transaction to change a Profitability Analysis (CO-PA) report. CO-PA allows the
user to "slice and dice" information derived from other SAP modules
(customer billing, internal orders, direct FI postings) to provide a view of
customer and product profitability. The user can change which variables,
characteristics and value fields are contained in the report.
KE41
Create Condition
Records
This transaction is used to create condition records for use
in Profitability Analysis (CO-PA) for valuation purposes. For example, when
transferring SD Billing documents for SD to CO-PA a valuation for sales
commission or freight expense can be calculated and added to the valuation of
the CO-PA posted line item. Enter the condition type, click Enter, select the key combination for the condition record, enter
your selection criteria, click Enter and then maintain the condition record.
KE42
Change Condition
Records
Use this
transaction to change a condition record which is used for valuation purposes
in Profitability Analysis (CO-PA). For example, when transferring SD Billing
documents from SD to CO-PA a valuation for sales commission or freight expense
can be calculated and added to the valuation of the CO-PA posted line item.
Enter the condition type, click Enter, select the key combination for the condition record, enter
your selection criteria, click Enter and then maintain the condition record.
KE4L
Create Pricing
Report
Use this
transaction to create a report on the condition records you created using
transaction KE41. Enter the two-character code and name of the report and click
Select
Fields. Select the fields for the report and then select the tables
that contain the condition records. Lastly, select the format and save the
report. You can execute the report using transaction KE4Q.
KE4N
Change Pricing
Report
This transaction
is used to change a report on the condition records that were created using
transaction KE4L. Enter the two-character code and name of the report and click
Enter. Select the fields to be deleted or add new fields for the
report and the tables that contain the condition records. Lastly, select the
format and save the report. You can execute the report using transaction KE4Q.
KE4Q
Execute Pricing
Report
Use this
transaction to execute a report created using transaction KE4L. Input the
2-character report code and execute.
KE51
Create Profit
Center
This transaction
is used to create a profit center, which classifies income and expense
transactions according to the internal responsibility of the organization, for
example, by product lines, geography, division etc. To accomplish this, all
internal orders and cost centers are attached to a single profit center, while
all revenue-related items (including cost of goods sold at standard) are posted
directly to a single profit center. Apart from the profit center number itself,
the following fields are also maintained as part of the profit center master
data: analysis period from/to, name, user responsible, lock indicator and
assignment to company codes.
KE52
Change Profit
Center
Use this
transaction to change a profit center. The following fields are maintained as
part of the profit center master data: analysis period from/to, name, user
responsible, lock indicator and assignment to company codes.
KE53
Display Profit Center
KE54
Delete Profit
Centers
This transaction
is used to delete a profit center but before the system can do this it carries
out the following checks; the profit center cannot be deleted if transaction
data has already been posted to it and/or the profit center is assigned to the
following objects: cost center, material and/or business processes.
KE56
Assignment of
Profit Centers to Company Codes - Change
This transaction
allows you to change the company code assignments for a large quantity of
profit centers without having to access master data maintenance for each single
profit center. If you do not change the company code assignments the profit
center is assigned to all the company codes. A column is inserted for each
company code selected indicating for each profit center whether or not it is
assigned to the company code in question. Note that you can select no more than
20 company codes at a time. To process any further company codes, repeat the
transaction. Note that a company code assignment cannot be undone if the profit
center has cost centers assigned to it, which are contained in the company code
in question or the profit center has materials assigned to it, which are
contained in the company code in question.
KE5Y
Profit Center:
Plan Line Items
Use this
transaction to provide a list of all profit center plan posting documents and
line items matching the user's selection criteria. This report can be used as
an aid in researching problems driven by postings in particular accounts and
profit centers. The list layout can be changed to suit business requirements.
KE5Z
Profit Center:
Actual Line Items
Use this
transaction to provide a list of all profit center actual posting documents and
line items matching the user's selection criteria. This report can be used as
an aid in researching problems driven by postings in particular accounts and
profit centers. The list layout can be change to suit business requirements.
KEDE
Maintain
Derivation Rules
This transaction
is used to maintain the rules for deriving a Profitability Analysis (CO-PA)
characteristic to be used in CO-PA postings. The characteristics value is
maintained using transaction KES1.
KEPM
CO-PA Planning
This transaction
contains a user friendly way of executing the process for revenue planning
including the ability to copy the plan values from last year's sales data,
display the data, increase or decrease the plan amounts using a %, integrate
plan quantities with manufacturing (i.e., LIS /spreadsheets), perform top down
planning, manual manipulation for customer/product plan sales quantities and
save a copied version of the plan.
KES1
Change
Characteristic Values
Use this transaction to maintain characteristic values for
new characteristics defined in Profitability Analysis (CO-PA). Once maintained
you can define derivation rules using transaction KEDE to assign these
characteristics to postings in CO-PA. Double-click the
KEU1
Create CO-PA
Actual Assessment Cycle
This transaction
is used to create an assessment cycle that can be used transfer actual overhead
costs to Profitability Analysis (CO-PA) for customer product profitability
analysis below the contribution margin line. Enter the cycle name and the start
date and click Enter.
Then enter the controlling area and the type of CO-PA analysis used, i.e.,
costing or account based. Then create a segment for the assessment, which
involves selecting the sender objects and receiving CO-PA segments and the
method of assessment. Execute the assessment cycle using transaction KEU5.
KEU2
Change CO-PA
Actual Assessment Cycle
Use this
transaction to change the assessment cycle created using transaction KEU1.
KEU4
Delete CO-PA
Actual Assessment Cycle
Use this
transaction the delete the assessment cycle created using transaction KEU1.
KEU5
Execute CO-PA
Actual Assessment Cycle
This transaction
is used to transfer overhead costs to Profitability Analysis (CO-PA) for
customer product profitability analysis below the contribution margin line.
Enter the period start from/to, fiscal year and enter the cycle name and start
date. The program can be run in test mode and/or in background. Leave the Detail
List Selection checked to see
the details of the sender and receiver posted amounts in the program output.
KEU7
Create CO-PA Plan
Assessment Cycle
This transaction
is used to create an assessment cycle that can be used to transfer plan
overhead costs to Profitability Analysis (CO-PA) for customer product
profitability analysis below the contribution margin line. Enter the cycle
name, start date and click Enter.
Then enter the controlling area and the type of CO-PA analysis used, i.e.,
costing or account based. Then create a segment for the assessment, which
involves selecting the sender objects and receiving CO-PA segments and the
method of assessment. Execute the assessment cycle using transaction KEUB.
KEU8
Change CO-PA Plan
Assessment Cycle
Use this
transaction to change the assessment cycle created using transaction KEU7.
KEUA
Delete CO-PA Plan
Assessment Cycle
Use this
transaction the delete the assessment cycle created using transaction KEU7.
KEUB
Execute CO-PA
Plan Assessment Cycle
This transaction is used to transfer plan overhead costs to
Profitability Analysis (CO-PA) for customer product profitability analysis
below the contribution margin line. Enter the period start from/to, fiscal
year, cycle name and the start date. The program can be run in test
mode and/or in
background. Leave the detail list selection checked to see the detail of the
sender and receiver posted amounts in the program output.
KGI2
Actual Overhead
Calculation: Order
This transaction
is used to apply overhead costs to an individual production order based upon an
overhead costing sheet as part of the product costing period end closing
process. The overhead costing sheet will calculate the overhead cost based on a
base cost element and an overhead rate. The production order will typically be
debited and a cost center (defined on the costing sheet) will be credited.
Enter the production order, period, fiscal year and execute to apply the overhead.
To execute the function for multiple production orders, use transaction CO43.
KK01
Create
Statistical Key Figure
This transaction
is used to create a statistical key figure (SKF) master data, which can be used
as the basis for internal allocations. For example, you assess the costs for
the cafeteria to the individual cost centers, based on the number of employees
in each cost center. To do this, you need to enter the number of employees in
each cost center as a statistical key figure. Input the SKF name and click Enter. Then enter the name of the SKF, the unit of measure, and
the SKF category, i.e., if the SKF is fixed and will be stored in each period
until changed or if the SKF is specific to individual periods.
KK02
Change
Statistical Key Figure
Use this
transaction to change the statistical key figure (SKF) master data, which is
used as the basis for internal allocations. Input the SKF name and click Enter
to make an update.
KK03
Display
Statistical Key Figure
Use this
transaction to display the statistical key figure (SKF) master data, which is
used as the basis for internal allocations. Input the SKF name and click Enter
to display the master data details.
KK04
Master Data
Report: Statistical Key Figures
This transaction
is used to display a report of statistical key figures (SKF). Selection
criteria include the SKF name, SKF group, unit of measure and SKF category.
KK87
Actual
Settlement: Product Cost Collector
This transaction
is used for actual settlement of a single product cost collector, which is part
of the period end closing process. A product cost collector is used in product
costing by period and so the cost object in this case is the material. This
transaction is used after other period end processes have been executed, such
as applying overhead, WIP calculation, and variance calculation. The settlement
will clear the cost object at period end. Use transaction CO88 for the
settlement of multiple cost collectors.
KK88
Actual
Settlement: Cost Object
This transaction
is used for actual settlement of a single cost object, which is part of the
period end closing process. A cost object is used in product costing but does
not control the costs at the production order level or material level; rather
it uses as a CO cost object such as an internal order. This transaction is used
after other period end processes have taken place such as applying overhead,
WIP calculation and variance calculation. The settlement will clear the cost
object at period end. Use transaction KK89 for the settlement of multiple cost
objects.
KK89
Actual
Settlement: Cost Object Collective
This transaction
is used for actual settlement of multiple cost objects, which is part of the
period end closing process. A cost object is used in product costing but does
not control the costs at the production order or material level; rather, it
uses a CO cost object such as an internal order. This transaction is used after
other period end processes have been executed such as applying overhead, WIP
calculation, and variance calculation. The settlement will clear the cost
object at period end.
KKA0
Change Cutoff
Period
Use this
transaction to establish the cut off period for the work in progress (WIP)
calculation. Work in process is the difference between the debits and credits
of a cost object that has not been fully delivered. When it calculates the work
in process, the system does not overwrite the results analysis data that
proceeds the cutoff period. Enter the results analysis version, click Enter, change the cut off period and click Save.
KKA3
Results Analysis
for Sales Order
This transaction
calculates results analysis for a single sales order line item (i.e., the sales
order line item is the cost object). The valuation for each sales order item
can be used to capitalize costs, create reserves or reconcile postings made in
FI and Profitability Analysis (CO-PA). Enter the sales order, the item number
on the sales order, period, fiscal year, results analysis version and execute
to run the calculation.
KKA6
Results Analysis
for Sales Order: Enter Data
Use this
transaction to manually enter results analysis data when transferring legacy
data. Enter the sales order, the item number on the sales order, period, fiscal
year, results analysis version and click enter.
KKAK
Actual Results
Analysis: Sales Orders
This transaction
calculates results analysis for multiple sales order line items (i.e., the
sales order line item is a cost object). The valuation for each sales order
item can be used to capitalize costs, create reserves or reconcile postings
made in FI and Profitability Analysis (CO-PA). Enter the sales order, the item
number on the sales order, period, fiscal year, results analysis version and
execute to run the calculation.
KKAO
Calculate Work in
Progress: Collective Processing
This transaction is used to calculate work in progress (WIP)
on multiple open production orders/process orders/product cost collectors. The
WIP calculation is based on actual costs and is the difference between the
debits and credits posted to the order/cost collector. Enter the plant, the
cost object type, WIP calculation period, fiscal year, results analysis version
and execute the calculation.
KKAS
Calculate Work in
Progress: Individual Processing; Material
This transaction
is used to calculate work in progress on an individual material. In this case
cost object controlling is conducted by period at the product cost
collector/material level. The WIP calculation is based on actual costs and is
the difference between the debits and credits posted to that period by product
cost collector. Enter the material, plant, WIP calculation period, fiscal year,
results analysis version and execute the calculation. Use transaction KKAO for
multiple materials.
KKAX
Calculate Work in
Progress: Individual Processing; Order
Use this
transaction to calculate work in progress (WIP) on an individual open
production order/process order. The WIP calculation is based on actual costs
and is the difference between the debits and credits posted to the order. Enter
the order, WIP calculation period, the fiscal year, the results analysis
version and execute the calculation. Use transaction KKAO for multiple
production/process orders.
KKC1
Create Cost
Object
This transaction
is used to create a general cost object that is not represented by a cost
object generated by other SAP applications like production orders or sales
order line items. A cost object may be created, for example, to track resources
used to create an intangible asset. Creating a general cost object will enable
you to calculate planned costs and actual costs, transfer costs to other SAP
cost objects and analyze plan vs. actual costs. The master data contains the
following information: text/naming of the cost object, object currency, name of
person responsible, control parameters for the calculation of overhead and a
deletion indicator flag.
KKC2
Change Cost
Object
Use this
transaction to change a cost object previously created using transaction KKC1.
The master data contains the following information, text/naming of the cost
object, object currency, name of person responsible, control parameters for the
calculation of overhead and a deletion indicator flag.
KKC3
Display Cost
Object
Use this
transaction to display a cost object previously create using transaction KKC1.
The master data contains the following information, text/naming of the cost
object, object currency, name of person responsible, control parameters for the
calculation of overhead and a deletion indictor flag.
KKC7
Create Product
Group
This transaction
is used to create a product group for drill down and summarization reporting
analysis. You may choose to use the product group/hierarchy created in the
logistics modules for CO reporting but, in addition, you may create a separate
product group just for product cost controlling use only using this
transaction. Create the product group number and then proceed to assign
materials to hierarchy nodes. Note: each material can only be assigned to one
CO product group.
KKC8
Change Product Group
Use this
transaction to change the product group that is used solely in the CO product
cost controlling application. Enter the product group number and then proceed
to change/add materials to hierarchy nodes. Note: each material can only be
assigned to one CO product group.
KKC9
Display Product
Group
Use this
transaction to display the product group that is used solely in the CO product
cost controlling application. Enter the product group number and then proceed
to display materials to hierarchy nodes. Note: each material can only be
assigned to one CO product group.
KKCS
Display Actual
Cost Line Items for Cost Objects
Use this
transaction to report on cost object line items, which provides a detailed
analysis of the posted documents. Furthermore, drill-down capability enables a
review of the actual document posted.
KKF1
Create CO
Production Order
This transaction
is used to create a CO production order for use with other master data in the
CO module. You can create a CO production order without a quantity structure
and enter the costs using unit costing. Unit costing is a type of spreadsheet
that, due to its integration, can be used with existing master data and prices,
such as activity prices from cost center accounting. Enter the order type,
material number and plant and click Enter. Then enter data such as text, assignments to organizational
units and control data such as currency, a statistical indicator and plan
integration indicator.
KKF2
Change CO
Production Order/QM Order
Use this
transaction to change a CO production order for use with other master data in
the CO module. Input the order number and click Enter. Review the material number and plant and enter/change data
such as text, assignments to organizational units and control data such as
currency, a statistical indicator and plan integration indicator.
KKF3
Display CO
Production Order/QM Order
Use this
transaction to display a CO production order. Input the order number and click Enter. Then display data such as material, plant, text,
assignments to organizational units and control data such as currency, a
statistical indicator and plan integration indicator.
KKF4
Change Order
Planning
This transaction
is used to plan the CO production order without a quantity structure using unit
costing. Unit costing is a type of spreadsheet that, due to its integration,
can be used with existing master data and prices, such as activity prices from
cost center accounting. Enter the CO production order, click Enter,
and then proceed to manually plan the order.
KKF6M
Create Multiple Product Cost Collectors for Production
Versions
a production order
costing object but is not limited in lifespan. Enter the plant, material(s) and
product cost collector order type and execute.
KKF6N
Display Product
Cost Collector
Use this
transaction to display multiple product cost collectors that are typically used
in a repetitive manufacturing environment/period costing scenario. A product
cost collector is like a production order costing object but is not limited in
lifespan. Input the plant and material(s), click Enter and use the left hand window pane to navigate the product
cost collector list.
KKFB
Display Variance
Line Items for Orders
This transaction
is a report online items that are based on the variance calculation. The
variances calculated represent the difference between target costs and control
costs (the control costs can be the net actual costs, for example). The report
will show the lines related to the variances categories, which are the causes
for the variances.
KKG1
Order: Enter Cost
of Sales
This transaction
is useful in a scenario where you want to input the cost of sales amount
calculated from a non SAP system. Results analysis can then calculate work in
progress and reserves for unrealized costs using the actual costs and the cost
of sales you entered.
KKG2
Project: Enter
Cost of Sales
This transaction
is useful in a scenario where you want to input the cost of sales amount
calculated from a non SAP system. Results analysis can then calculate work in
progress and reserves for unrealized costs using the actual costs and the cost
of sales you entered.
KKG3
Sales Order:
Enter Cost of Sales
This transaction
is useful in a scenario where you want to input the cost of sales amount
calculated from a non SAP system. Results analysis can then calculate work in
progress and reserves for unrealized costs using the actual costs and the cost
of sales you entered.
KKH1
Create Cost
Object Group
Use this
transaction to create a cost object group using general cost objects created
via transaction KKC1, for example, on the basis of responsibility. This is
useful for grouping cost objects for reporting purposes. Enter the cost object
group number and then change/add cost objects to hierarchy nodes.
KKH2
Change Cost
Object Group
This transaction
is used to change a cost object group. Enter the cost object group number and
then change/add cost objects to hierarchy nodes.
KKH3
Display Cost
Object Group
This transaction is used to display a cost object group.
Enter the cost object group number
KKPH
Fast Entry for
Cost Object Hierarchy
Use this transaction
to create a cost object hierarchy that can be used to analyze target costs,
actual costs, and variances in situations where costs are not collected at the
level of orders or materials. With the fast entry function, you create the cost
object nodes of a cost object hierarchy in a list screen. You can specify the
level of the cost object nodes and define the top of the hierarchy.
KKPHIE
Edit: Cost Object
Hierarchy
Use this
transaction to create a cost object hierarchy that can be used to analyze target
costs, actual costs, and variances in situations where costs are not collected
at the level of orders or materials. With the structured entry method, the cost
object hierarchy is shown as a graphic. You can specify the levels of the cost
object nodes, define the top of the hierarchy, and assign single objects.
KKR0
Create
Summarization Hierarchy
This transaction
is used to create a summarization hierarchy, which is an analysis tool you can
use to summarize values upwards in a hierarchical structure that you define.
This makes it possible to analyze values and quantities at higher levels, such
as at a plant level. Values in object currency are only summarized if the
summarization hierarchy contains a plant or company code node. Summarized data
can include planned, actual, target costs, variances and work in progress.
Click the Create
icon, enter the name and description of the summarization and
then proceed to define the object types, the totals records and hierarchy to be
summarized. Fill the summarization with data using transaction KKRC.
KKRC
Summarization: CO
Object
Use this
transaction to fill the summarization tables created using transaction KKR0.
The data collection run is usually carried out for each summarization hierarchy
after period-end closing in cost object controlling. The system reads the
quantities and values of the selected objects as defined by the summarization
hierarchy for the period being closed. This data is summarized upwards
according to the structure of the hierarchy, and it is updated by period and
cost element in the summarization objects. A summarization object is built for
each field characteristic for all fields in a summarization hierarchy.
KKS1
Variance
Calculation Cost Object Controlling by Order; Collective
This transaction
is used to calculate production variances for a whole plant at one time.
Production orders are the mechanism used to monitor the consumption of raw
materials and plant expenses in the production of other inventories such as
finished goods. Once overhead has been applied to a production order,
production order variances can be calculated and then settled. Variances are
calculated and reported in eight categories divided by input and output
variances, such as price and quantity variance on the input side and lot size
and output price variance on the output side.
KKS2
Variance
Calculation Cost Object Controlling by Order; Individual
Use this transaction to calculate production variances for an
individual production order. Production orders are the mechanism used to
monitor the consumption of raw materials and
plant expenses in
the production of other inventories such as finished goods. Once overhead has
been applied to a production order, production order variances can be calculated
and then settled. Variances are calculated and reported in eight categories
divided by input and output variances, such as price and quantity variance on
the input side and lot size and output price variance on the output side.
KKS5
Variance Calculation
Cost Object Controlling by Period; Collective
This transaction
is used to calculate production variances for a whole plant at one time. This
transaction is used to calculate variances for product cost collectors in a
period based cost object controlling scenario typically at the material level
in a repetitive manufacturing environment. Once overhead has been applied to a
product cost collector for the period, production variances can be calculated
and then settled. Variances are calculated and reported in eight categories
divided by input and output variances, such as price and quantity variance on
the input side and lot size and output price variance on the output side.
KKS6
Variance
Calculation Cost Object Controlling by Period; Individual
Use this
transaction to calculate production variances for an individual product cost
collector/material. This transaction is used to calculate variances for a
product cost collector in a period based cost object controlling scenario
typically at the material level in a repetitive manufacturing environment. Once
overhead has been applied to a product cost collector for the period,
production variances can be calculated and then settled. Variances are
calculated and reported in eight categories divided by input and output
variances, such as price and quantity variance on the input side and lot size
and output price variance on the output side.
KL01
Create Activity
Type
This transaction
is used to create an activity type master record, which can be used, for example,
in routings and production orders for machine time. These quantities of time
(both planned quantities and actual quantities confirmed), when combined with
activity prices drive the application of direct machine costs for product
costing and production orders. Activity types are assigned to one controlling
area and have a valid from/to date. Activity types typically contain a name,
person responsible and category, which determines the method of activity
quantity planning and activity allocation
KL02
Change Activity
Type
Use this
transaction to change the activity type master record. When combined with
activity prices, activity types drive the application of activity costs for
product costing and production orders.
KL03
Display Activity
Type
Use this transaction
to display the activity type master record. When combined with activity prices,
activity types drive the application of activity costs for product costing and
production orders.
KL04
Delete Activity
Type
Use this transaction to delete an activity type master record
individually. Note that there must be no plant transactional data existing in
the controlling area.
KL05
Display Change
Documents: Activity Type
Use this
transaction to report all changes to an activity type. There is an option to
select from a specific date, time and user ID of the individual making the
change. The report output will display the fields changed with the option to
drill down and display the old/new field value and date changed.
KL13
Display Activity
Types
This transaction
is used to display a list of activity types with the list being all activity
types, an activity type group or an individual activity type.
KL14
Delete Activity
Types
Use this
transaction to delete an activity type master record individually, collectively
or in a group. Note that there must be no plant transactional data exiting in
the controlling area.
KLH1
Create Activity
Type Group
This transaction
is used to create an activity type group, which is a hierarchy structure of
activity types. Activity type groups are used for reporting, allocations and/or
in various planning functions, where it is desirable to display data at a high
level of detail. Input the profit center group key and then click Enter
to create the hierarchical structure with activity types
assigned to the lowest level node.
KLH2
Change Activity
Type Group
This transaction
is used to change an activity type group, which is a hierarchy structure of
activity types. Activity type groups are used for reporting, allocations and/or
in various planning functions, where it is desirable to display data at a high
level of detail. Input the profit center group key and click Enter
to change the hierarchical structure.
KLH3
Display Activity
Type Group
This transaction
is used to display an activity type group, which is a hierarchy structure of
activity types. Activity type groups are used for reporting, allocations and/or
in various planning functions, where it is desirable to display data at a high
level of detail. Input the profit center group key and click Enter
to display the hierarchical structure.
KO01
Create Internal
Order
Use this
transaction to create an internal order/cost object that collects actual and
plan revenues and costs, statistical and activity data. Internal orders
typically collect and analyze actual and planned costs related to a specific
project, event or asset under construction. The project/event will span several
accounting periods and all costs can be settled in the period they were
incurred. Internal orders typically contain a name, person responsible,
assignment to an organizational unit and an order type, which determines the
method of settlement.
KO02
Change Internal
Order
This transaction
is used to change an internal order/cost object that collects actual and plan
revenues and costs, statistical and activity data. Internal orders typically
collect and analyze actual and planned costs related to a specific project,
event or asset under construction. Input the internal order number, click Enter
and update the internal master record data fields.
KO03
Display Internal
Order
This transaction
is used to display an internal order/cost object that collects actual and plan
revenues and costs, statistical and activity data. Internal orders typically
collect and analyze actual and planned costs related to a specific project,
event or asset under construction. Enter the internal order number, click Enter
and display the internal master record data fields.
KO04
Order Manager
This transaction
is used to create/change an internal order using a graphical user interface. An
internal order worklist can be created and used to facilitate changes to
multiple orders at the same time. You can also create new orders or copy an
existing order in the worklist. You can also select single orders and process
them using collective processing for orders, which enables multiple changes at
one time.
KO12
Change Overall
Planning
Use this
transaction to input an overall plan for the internal order. This type of
planning is performed independently from cost elements. You can enter the plan
for the lifetime of the order or an annual plan in each fiscal year. Note: An
overall plan can be changed using this transaction; however, the original
values are not maintained separately.
KO13
Display Overall
Planning
This transaction
is used to display an overall plan for an internal order. This type of planning
is performed independently from cost elements. The plan may be for the lifetime
of the order or an annual plan entered in each fiscal year.
KO14
Copy Planning
Use this
transaction to create a new plan for internal orders by copying an existing
plan version. You can copy primary costs, revenues, secondary costs, activity
data, fiscal year dependent and independent overall planning values, unit cost
values, detailed planning and statistical key figure values together or in any
combination. Additionally, data can be copied period by period, several periods
at a time or for an entire year. Before a version can be referenced, the
"copying allowed" parameter must be activated in the planning version
parameters.
KO15
Copy Actual to
Plan
This transaction
is similar to transaction KO14 but allows you to create an internal order plan
from actual costs. All data types can be copied individually, all together or
in many combinations. Additionally, data can be copied period by period,
several periods at a time or for an entire year.
KO22
Change Original Budget
Use this
transaction to change the original budget, which is an approved cost structure
for an internal order or an order group. A budget is more controlled and
binding than a plan and can be subject to availability control. The original
budget should be changed, using this transaction, with the best estimation of
costs. Unforeseen events, such as price increases, and so on, may require
corrections to the original budget, which can be maintained using supplements
(transaction code KO24) and returns (KO26). Use a supplement to increase the
current budget or a return to decrease the current budget.
KO23
Display Original
Budget
This transaction
is used to display the original budget. A budget is more controlled and binding
than a plan and can be subject to availability control. Input the internal
order or internal order group and internal order type and click the Original
Budget icon.
KO24
Change Supplement
Use this
transaction to make changes to the original budget. If the funds provided in
the original budget are not sufficient, the system enables you to use budget
supplements. Changes are managed as line items in the system and are therefore
managed separately from the original budget. The time to lock down a budget as
an original budget, and to update it with supplements, returns and transfers
depends on when you want to log data origins, in other words the
sender-receiver relationships for the updates. You therefore use budget updates
to prove where supplements and returns originated, and where they are to be
used. You do this using status management.
KO25
Display
Supplement
This transaction is used to display changes to the original
budget. If the funds provided in the original budget are not sufficient, the
system enables you to use budget supplements. Changes are managed as line items
in the system and are therefore managed separately from the original budget.
Input the internal order or internal order group and type and click
the Supplement
icon.
KO26
Change Return
Use this
transaction to make changes to the original budget. Using this transaction you
can return funds, i.e., reduce the original budget for unused funds. Changes
are managed as line items in the system and are therefore managed separately
from the original budget. You therefore use budget updates to prove where
supplements and returns originated, and where they are to be used.
KO27
Display Return
This transaction
is used to display changes to the original budget. Using this transaction you
can display reductions to the original budget for unused funds. Changes are
managed as line items in the system and are therefore managed separately from
the original budget. You therefore use budget updates to prove where
supplements and returns originated, and where they are to be used.
KO30
Activate Availability
Control exceeded (either by actual costs or commitments). When
purchase requisitions or purchase orders, for example, are posted to an
investment order that has been budgeted, the system checks whether the posting
causes the predefined tolerance limits to be exceeded. If it does, then the
system automatically issues either a warning or error message (depending on
customizing settings).
KO32
Deactivate
Availability Control
Use this
transaction to deactivate availability control previously activated using
transaction KO30.
KO88
Actual
Settlement: Order
Use this
transaction to settle actual primary and secondary costs and revenues (if
applicable) to the receivers established in a production/internal order's
settlement rules. In costing, production/internal orders are interim cost
collectors that are used to plan, record actual costs and monitor costs until
certain activities have been completed and the costs move to their final
destination. This movement of the costs to their final destination is called
settlement. The order's settlement rules are dependent on the parameters
established in the settlement structure, settlement profile, and order type
(all defined in customizing and in the master data itself).
KO8B
Display
Settlement Document
Use this
transaction if you know the settlement document number posted via transaction
KO88. However, an alternative way to review the settlement posting is going to
transaction KO88, inputting your selection criteria and via the menu path
selecting Go
to • Previous Settlement. Either way, the
information about the settlement is displayed such as the settlement
senders/receivers, the amount calculated and distributed.
KO8G
Actual
Settlement: Orders
This transaction is used to settle actual costs of multiple
internal orders at the same time. A selection variant has to be created
beforehand in order to select the internal order range. The selection method
can be changed to internal orders used in CRM or cProjects order if these
components are being used. Select the settlement period and fiscal year variant
and click
Execute.
KO9E
Planned
Settlement: Internal Orders; Individual
Use this
transaction to settle plan primary and secondary costs and revenues to the
receivers established in an internal order's settlement rules. In costing,
production/internal orders are interim cost collectors that are used to plan,
record actual costs and monitor costs until certain activities have been
completed and the costs move to their final destination. This movement of the costs
to their final destination is called settlement. This transaction is the plan
cost (as opposed to actual cost) equivalent of transaction KO88.
KO9G
Planned Settlement: Internal Orders; Collective
Execute.
This transaction is the plan cost (as opposed to actual cost) equivalent of
transaction KO8G.
KOB1
Display Actual
Cost Line Items for Orders
Use this
transaction to display detailed line items for internal order actual posting
documents. Actual line items are created with every posting of actual costs.
They contain information about the posted amount, the posting date, and the
user who posted the line item. When you start an actual line item report, you
need to limit the line items to be read by entering an order (or order group),
a cost element (or cost element group), and a posting period. Additionally, you
can configure different layouts to control the appearance of the report.
KOB2
Display
Commitment Line Items for Orders
Use this
transaction to display the details for commitment line items that are created
as a commitment in the set up, for example, for a purchase order. The line item
contains information about the posted amount, the posting date, and the user
who posted the item. When you start a line item report, you need to limit the
line items to be read by entering an order (or order group), a cost element (or
cost element group) and a posting period. Additionally, you can configure
different layouts to control the appearance of the report.
KOB3
Display Variance
Line Items for Orders
Use this
transaction to display details for variance line items created via the variance
calculation function (transaction KKS1 and KKS2). The line items can display,
by target cost version the variance categories calculated. The line item
contains information about the posted amount, the posting date, and the user
who posted the item. When you start a line item report, you need to limit the
line items to be read by entering an order (or order group), a cost element (or
cost element group) and a posting period. Additionally, you can configure
different layouts to control the appearance of the report.
KOB4
Display Budget
Line Items for Orders
This transaction
displays budgeting documents in ascending order. This way you can see how a
particular budget came about. This report is therefore particularly suitable
for monitoring the budgeting process. However, it cannot be used to display how
much budget a particular funds management account assignment actually has.
KOB8
Display Results
Analysis Line Items for Orders
Use this
transaction to display the line items generated from the results analysis/work
in progress calculation via transaction KKAX or KKAO. Results analysis valuates
the relationship between the costs and a measure of the order's progress toward
completion and thus the amount that can be capitalized as work in progress.
This transaction displays the results of the results analysis execution. Note:
In customizing the Generate Line Item indicator must be turned on for the results analysis version
report to display the line items.
KOC4
Order Selection
This transaction is used to generate a list of orders with
the associated master data fields and key figures. The results list has a
number of navigation and formatting options and can be modified by the user.
From the results list in the detailed report, you can branch off to
single orders or
to a comparison of two orders, in order to examine these orders more closely.
You can also go to the master data display for characteristics from the results
list. Furthermore, you can drill down into the material master record for an
order to be analyzed. Order selection is not a summarized analysis and is not
based on classification. It mainly serves to answer specific questions/queries
that arise in cost object controlling.
KOCF
Fiscal Year
Close: Carry Forward Commitment
Use this
transaction to carry forward commitments (for example, purchase requisitions,
purchase orders, earmarked funds) posted in the current fiscal year but not
reduced until the following fiscal year. The commitment carried forward then
debits the budget in the new fiscal year.
KOCO
Budget Carry
Forward for Orders
This transaction
enables you to carry forward budget remainders from projects, internal orders,
and plant maintenance orders to the following fiscal year. A budget that has
not been used up is mainly defined here as the difference between the planned
budget and incurred actual costs. Budgets carried forward to the following year
can also be posted to the previous year in certain circumstances.
KOH1
Create Order
Group
Use this
transaction to create internal order groups. Internal order groups are very
flexible structures and can be used in collective processing (master data and
transactional data), reporting, allocations, and authorization objects. Each
sub group represents a level of summarization. Internal order groups are unique
within a controlling area.
KOH2
Change Order
Group
Use this
transaction to change an internal order group. Internal order groups as well as
orders can be added, deleted or reassigned using this transaction. Order groups
are very flexible structures and can be used in other order groups, collective
processing (master data and transactional data), reporting, allocations, and
authorization objects. Each sub group represents a level of summarization.
Internal order groups are unique within a controlling area, but client
dependent.
KOH3
Display Order
Group
This transaction
is used to display an internal order group. Internal order groups are very
flexible structures and can be used in collective processing (master data and
transactional data), reporting, allocations, and authorization objects. Each
sub group represents a level of summarization. Internal order groups are unique
within a controlling area.
KOK2
Collective
Processing for Internal Orders
KOK3
Collective Display for Internal Orders
Use this
transaction to display multiple internal order master records using manual
collective processing. The user can toggle between available line display
variants or drill down to the specific internal order master data and
settlement rule.
KOK4
Automatic
Collective Processing for Internal Orders
Use this
transaction to make changes to multiple internal order master records using
automatic collective processing. This transaction differs from the manual
collective processing using transaction KOK2 in that both the order selection
and the change function are performed within one transaction.
KP04
Set Planner
Profile
This transaction
is used to set the default planner profile to be used with transactions such as
KP06 and KP26. Perform this procedure when the planner profile default needs to
be changed to accommodate subsequent planning activities. When planning in cost
center accounting and profit center accounting, a planning profile is used to
direct the kind of information the user enters. The planning template aids the
user's planning process since not all fields need to be available for every
planning activity.
KP06
Change
CElem/Activity Input Planning
Use this
transaction for primary cost planning, i.e., costs due to external procurement
or material withdrawals. Activity-independent (only to cost center) and
activity-specific (to cost center/activity type) primary costs can be planned.
In order to calculate activity prices automatically you have to plan
activity-specific primary costs with corresponding activity outputs that have
been planned for the sender cost center. In other words, within an agreed
activity plan, the sender cost centers provide activity quantities because
other cost centers have planned to consume them. You use transaction KSC6 to calculate
activity prices automatically.
KP07
Display Planning
CElem/Act. Input
Use this
transaction to display primary cost planning, i.e., costs due to external
procurement or material withdrawals. Activity-independent (only to cost center)
and activity-specific (to cost center/activity type) primary costs can be
planned.
KP26
Change Activity
Type/Price Planning
Use this
transaction to plan activity prices manually for cost centers. You plan the
activity price of an activity type of a sender cost center, which can be used
as the basis for cost allocations to receiver cost objects via a secondary cost
element posting. If you have not manually planned the prices during activity
type planning, SAP can calculate the debit for the receiver cost centers using
an iteratively calculated price via transaction KSC6.
KP27
Display Activity
Type/Price Planning
KP46
Change Statistical Key Figure Planning
This transaction
is used to plan for statistical key figures. For example, as a key figure, you
can plan costs per the number of employees using this transaction. Furthermore,
you can use the number of employees as an allocation base, i.e., to allocate
cafeteria costs among cost centers based on number of employees in that cost
center.
KP47
Display Statistical
Key Figure Planning
This transaction
is used to display a plan for statistical key figures.
KP90
Delete Planned
Costs (All Integrated Planning Objects)
Use this
transaction to delete particular planning data (including very large amounts)
from the CO tables. This deletes the planning data on objects that are
integrated with planning. This includes the following objects, cost centers,
business processes, internal orders and projects, for which planning
integration is active in both the version and the master data.
KP98
Copy Actual to
Plan
This transaction
is used during the planning process and offers a method of reusing large parts
of your actual data to generate plan data. It allows actual data to be
transferred to plan values within a fiscal year, across different periods or
within different versions. You can copy within fiscal years, periods, versions,
and cost centers. Try to avoid using the Reset and Overwrite option because the system needs to read all the data in the
target version in order to clear it.
KP9R
Copy CO Resource
Prices
Use this
transaction to copy resource prices, which are the equivalent of activity
prices but for external activities. Resource prices are used to plan/valuate
the cost of consuming business activities by cost object such as cost centers.
The transaction enables you to copy resource prices from one target plan
version/fiscal year to another.
KPD6
Change
Statistical Key Figure Planning
This transaction
is used to enter plan statistical key figure data for internal orders, which
can be used as a basis for internal allocations, such as distributions and
assessments and key figure analysis. Statistical key figures can be planned on
a cost center, internal order, or other cost objects. Enter the document date,
posting date, select the screen variant, the statistical key figure, the
receiving cost center or internal order and quantity to be posted and save.
KPD7
Display
Statistical Key Figure Planning
This transaction
is used to display plan data for statistical key figures for internal orders,
which can be used as a basis for internal allocations, such as distributions
and assessments and key figure analysis. Statistical key figures can be planned
on a cost center, internal order, or other cost objects. Input the document
number, click Enter and
the posting is displayed.
KPF6
Planning
CEIem/Activity Input
Use this
transaction to plan primary costs for internal orders. You can plan an overall
value
for the internal
order or plan annual values. Enter a plan version, from/to period, fiscal year,
internal order from/to or internal order group and cost element from/to or cost
element group, click Overview and proceed to the planning screen.
KPF7
Display
CEIem./Acty Input Planning
This transaction
is used to display plan primary costs of for internal orders. You can display
the plan at an overall plan for the internal order or for an annual plan. Enter
a plan version, from/to period, fiscal year, internal order from/to or an internal
order group and cost element from/to or cost element group, click Overview
and proceed to the planning screen.
KPG5
Report Painter:
Create Orders: Planning Layout for Cost Elements/Active
Use this
transaction to create a planning layout for internal order planning. The
planning layout can be customized to suit your planning requirements. This
involves selecting a lead column, typically the cost element characteristic,
and then the planning key figures, such as the total plan in the controlling
area currency or total plan in the transaction currency. Furthermore, a number
of formatting options are also available. Once saved, the planning layout can
then be used via transaction KPF6 (Change CEIem/Activity Input Planning).
KPG6
Report Painter:
Change Orders: Planning Layout for Cost Elements/Active
This transaction
can be used to change the planning layout, previously created using transaction
KPG5.
KPSI
Execute Plan
Reconciliation
Use this
transaction to reconcile plan activity input and output. Because activity
output and input can be planned separately there can be differences if, for
example, only the activity output is changed. In this case the planning
networked has to be reconciled again. This transaction will show how the
planning change affects the planning network.
KRMI
Display Actual
Cost Line Items for Orders
Use this
transaction to display detailed line items for product cost collector actual
postings. Actual line items are created with every posting of actual costs.
They contain information about the posted amount, posting date, and the user
who posted the item. Enter the material, plant, production process and date
from/to an order and execute. Additionally, you can configure different layouts
to control the appearance of the report.
KSOl
Create Cost
Center
This transaction
is used to create a cost center, which is part of the controlling module master
data. Cost centers are distinct cost objects/cost collectors that can sub
divide the organization by function, process and responsibility. Cost centers
can be planned, actual postings recorded and used for cost allocations. Cost
centers can be grouped for summarization and hierarchically structured for
drill down reporting. Enter the cost center number, valid from/to dates, click Enter
and maintain master data fields such as description/name,
cost center category and person responsible. Note that one easy way to create a
new cost center is to use an existing cost center as a reference and then
change the few fields required for the new cost center and save it.
KS02
Use this
transaction to change a cost center previously created using transaction KS01.
KS03
Display Cost
Center
Use this
transaction to display a cost center previously created using transaction KS01.
KS04
Delete Cost
Center; Individual
This transaction
is used to delete a cost center but deletion is only effective if there are no
postings to the cost center. In other words, it is simply not enough to reverse
any postings to the cost center in order to delete it. One option, as an
alternative to deleting the cost center, would be to render the cost center
inactive by shortening its effective to date, so that the cost center cannot be
posted to from that date onwards.
KS05
Display Change
Documents: Cost Center
Use this
transaction to report all changes to a cost center. There is an option to
select from a specific date and the user ID of the individual making the
change. The report output will display the fields changed with the option to
drill down and display the old/new field value and date changed.
KS12
Change Cost
Centers
This transaction
can be used to change multiple cost centers at one time. Select cost centers in
a specific valid from/to period and then change the cost centers to overwrite
the entries in the available for input fields and save your entries.
KS13
Display Cost
Centers
Use this report
to display a list of cost centers that may have been changed using transaction
KS12.
KS14
Delete Cost
Centers; Collective
This transaction
is used to delete multiple cost centers at the same time but is effective only
if there are no postings to the cost center. In other words, it is simply not
enough to reverse any postings to the cost center in order to delete it. One
option, as an alternative to deleting the cost center, would be to render the
cost center inactive by shortening its effective to date, so that the cost
center cannot be posted to from that date onwards.
KSB1
Display Actual
Cost Line Items for Cost Centers
Use this
transaction to display detailed line items for cost center actual postings.
Actual line items are created with every posting of actual costs. They contain
information about the posted amount, the posting date, and the user who posted
the item. When you start an actual line item report, you need to limit the line
items to be read by entering a cost center (or cost center group), a cost
element (or cost element group) and a posting period. Additionally, you can
configure different layouts to control the appearance of the report.
KSB2
Display
Commitment Line Items for Cost Centers
Use this
transaction to display detailed line items for commitment line item postings on
a cost center that has been created for commitments, for example, for a
purchase order. The line item contains information about the posted amount, the
posting date, and the user who posted the item. When you start a line item
report, you need to limit the line items to be read by entering a cost center
(or cost center group), a cost element (or cost element group) and a posting
period. Additionally, you can configure different layouts to control the
appearance of the report.
KSBP
Display Plan Cost
Line Items for Cost Centers
Use this
transaction to display detailed line items for cost center plan postings. The
line item displays information about the planned amount, the posting date, and
the user who posted the item. When you start a plan line item report, you need
to limit the line items to be read by entering a cost center (or cost center
group), a cost element (or cost element group) and a posting period.
Additionally, you can configure different layouts to control the appearance of
the report.
KSBT
Activity Type
Price Report
Use this
transaction to report on cost center activity prices created automatically by
activity price calculation or manually created by activity price input planning
using transaction KP26. Input the cost center, activity type, planning version,
fiscal year, from period and click Execute to display the results.
KSC1
Create Cycle for
Actual Indirect Activity Allocation
Use this transaction
to create a cost allocation cycle for actual indirect activity allocation,
which is a method of allocating total activity quantity from senders cost
centers to the receiver cost centers based on the receiver activity posted in
the receiver cost center. For example, in manufacturing, you can allocate
overhead costs from a cost center from which the expenses are posted, to a
production cost center that uses the overhead.
KSC2
Change Cycle for
Actual Indirect Activity Allocation
This transaction
is used to change an actual indirect activity allocation cycle previously
created using transaction KSC1.
KSC3
Display Cycle for
Actual Indirect Activity Allocation
This transaction
is used to display an actual indirect activity allocation cycle previously created
using transaction KSC1.
KSC4
Delete Cycle for
Actual Indirect Activity Allocation
This transaction
is used to delete an actual indirect activity allocation cycle previously
created using transaction KSC1.
KSC5
Execute Cycle for
Actual Indirect Activity Allocation
on the receiver
activity posted in the receiver cost center. For example, in manufacturing, you
can allocate overhead costs from a cost center from which the expenses are
posted, to a production cost center that uses the overhead. Enter the period
you want to run the allocation for, the cycle created using transaction KSC1
and execute. The program can also run in test mode with or without a detail
list showing the allocation in the output.
KSC6
Act. Indirect
Acty Alloc.: Overview
This transaction
can be used to list an overview of the indirect activity allocation postings
executed using transaction KSC5.
KSC7
Create Cycle for
Planned Indirect Activity Allocation
Use this
transaction to create an allocation cycle for plan cost indirect activity
allocation, which is a method of allocating total activity quantity from
senders cost centers to the receiver cost centers based on the receiver
activity planned in the receiver cost center. For example, in manufacturing,
you can allocate plan overhead costs from a cost center from which the expenses
are posted, to a production cost center that uses the overhead.
KSC8
Change Cycle for
Planned Indirect Activity Allocation
This transaction
is used to change a plan cost indirect activity allocation cycle previously
created using transaction KSC7.
KSC9
Display Cycle for
Planned Indirect Activity Allocation
This transaction
is used to display a plan cost indirect activity allocation cycle previously
created using transaction KSC7.
KSCB
Execute Plan
Indirect Acty Alloc.
Use this
transaction to execute an allocation cycle for plan cost indirect activity
allocation, which is a method of allocating total activity quantity from
senders cost centers to the receiver cost centers based on the receiver
activity planned in the receiver cost center. For example, in manufacturing,
you can allocate plan overhead costs from a cost center from which the expenses
are posted, to a production cost center that uses the overhead. Enter the
period you want to run the allocation for and the cycle created using
transaction KSC7 and execute. The program can also run in test mode with or
without a detail list showing the allocation in the output.
KSCC
Document List for
Selected Cycle
This transaction
can be used to list an overview of the indirect activity allocation postings
executed using transaction KSCB.
KSH1
Create Cost Center Croup
KSH2
Change Cost
Center Croup
KSH3
Display Cost
Center Croup
Use this
transaction to display a cost center group previously created using transaction
KSH1.
KSII
Actual Price
Calculation
This transaction
calculates an activity price by taking into account the exchange of activity
between cost centers. Actual price calculation, which you can carry out during
planning, is based on planned costs and activity. The resulting prices are used
to valuate actual activity. After running actual price calculation, you can
choose to recalculate actual activity based on actual prices.
KSS2
Actual Cost Splitting
This transaction
is used to split activity independent costs into activity type dependent costs
if more than one activity type exists on the cost center. Costs can be split
according to costs from the cost center to different activities based on equivalence
numbers or actual activity. You must split plan costs before executing activity
price calculation and plan/target/actual comparison reporting.
KSS4
Plan Cost
Splitting
Use this
transaction to split the activity-independent plan costs of a cost center among
the activity types of this cost center. You must split plan costs before
executing plan activity price calculation and plan/target/actual comparison
reporting. To split plan costs, you must first plan the corresponding values in
activity type planning.
KSU1N
Create Actual
Assessment Cycle
This transaction
is used to set up the senders, receivers and distribution rules for an actual
assessment posting using transaction KSU5. Assessments apportion costs
collected within a cost center during the accounting period to receiver cost
centers according to user-defined distribution rules. The difference between a
distribution and an assessment is that assessments use a secondary cost element
to post to the receiver cost center, which leaves the original posting visible
in the sender cost center.
KSU2N
Change Actual
Assessment Cycle
Use this
transaction to change an assessment cycle previously created using transaction
KSU1N.
KSU3N
Display Actual
Assessment Cycle
Use this transaction to display an assessment cycle
previously created using transaction KSU1N.
KSU4N
Delete Actual
Assessment Cycle
KSU5
Execute Actual
Assessment
This transaction
is used to allocate/apportion actual costs collected within a cost center
during the accounting period to receiver cost centers according to user-defined
distribution rules. The difference between a distribution and an assessment is
that assessments use a secondary cost element to post actual costs to the
receiver cost centers, which leaves the original posting visible in the sender
cost center.
KSU6
Document List for
Selected Cycle
Use this
transaction to review the controlling documents posted as a result of executing
KSU5 in update mode.
KSU7N
Create Plan
Assessment Cycle
This transaction
is used to set up the senders, receivers and distribution rules for a plan
assessment posting using transaction KSUB. Assessments apportion plan costs
within a cost center in a period to receiver cost centers according to
user-defined distribution rules. The difference between a distribution and an
assessment is that assessments use a secondary cost element to post plan costs
to the receiver cost centers, which leaves the original plan posting visible in
the sender cost center.
KSU8N
Change Plan
Assessment Cycle
Use this
transaction to change a plan assessment cycle previously created using
transaction KSU7N.
KSU9N
Display Plan
Assessment Cycle
Use this
transaction to display a plan assessment cycle previously created using
transaction KSU7N.
KSUAN
Delete Plan Assessment
Cycle
Use this
transaction to delete a plan assessment cycle previously created using
transaction KSU7N.
KSUB
Execute Plan
Assessment
This transaction
is used to allocate/apportion plan costs within a cost center during an
accounting period to receiver cost centers according to user-defined
distribution rules. The difference between a distribution and an assessment is
that assessments use a secondary cost element to post plan costs to the
receiver cost centers, which leaves the original plan posting visible in the
sender cost center.
KSUCN
Use this
transaction to review the controlling documents posted as a result of executing
KSUB in update mode.
KSPI
Plan Price
Calculation
This transaction
is used to determine prices for the plan activity types of each cost center.
The system calculates the prices iteratively by dividing the plan costs by the
plan activity quantity. It is also possible to determine the fixed portion of
the price as the quotient (ratio) of plan costs and capacity.
KSV1N
Create Actual
Distribution Cycle
This transaction
is used to set up the senders, receivers and distribution rules for a
distribution actual posting using transaction KSV5. Distributions allocate
primary costs collected within a cost center during the accounting period to
receiver cost centers according to user-defined distribution rules. The
difference between a distribution and an assessment is that a distribution
posts using the primary cost element, which means the original cost gets posted
into the receiving cost centers.
KSV2N
Change Actual
Distribution Cycle
Use this
transaction to change an actual distribution cycle previously created using
transaction KSV1N.
KSV3N
Display Actual
Distribution Cycle
Use this
transaction to display an actual distribution cycle previously created using
transaction KSV1N.
KSV4N
Delete Actual
Distribution Cycle
Use this
transaction to delete an actual distribution cycle previously created using
transaction KSV1N.
KSV5
Execute Actual
Distribution
This transaction is
used to allocate/apportion actual costs collected within a cost center during
the accounting period to receiver cost centers according to user-defined
distribution rules. Distributions allocate primary costs collected within a
cost center during the accounting period to receiver cost centers according to
user-defined distribution rules. The difference between a distribution and an
assessment is that a distribution posts costs using the primary cost element,
which means the original cost gets posted into the receiving cost centers.
KSV6N
Actual
Distribution: Overview
Use this
transaction to review the controlling documents posted as a result of executing
KSV5 in update mode.
KSV7N
This transaction
is used to set up the senders, receivers and distribution rules for a plan
distribution posting using transaction KSVB. Distributions allocate plan costs
posted within a cost center during the accounting period to receiver cost
centers according to user-defined distribution rules. The difference between a
distribution and an assessment is that a distribution posts plan costs using
the primary cost element, which means the original plan gets posted into the
receiving cost centers.
KSV8N
Change Plan
Distribution Cycle
Use this
transaction to change a plan distribution cycle previously created using
transaction KSV7N.
KSV9N
Display Plan
Distribution Cycle
Use this
transaction to display a plan distribution cycle previously created using
transaction KSV7N.
KSVAN
Delete Plan
Distribution Cycle
Use this transaction
to delete a plan distribution cycle previously created using transaction KSV7N.
KSVB
Execute Plan Cost
Distribution
This transaction
is used to allocate/apportion plan costs within a cost center to receiver cost
centers according to user-defined distribution rules. The difference between a
distribution and an assessment is that a distribution posts plan costs using
the primary cost element, which means the original cost gets posted into the
receiving cost centers.
KSVC
Plan
Distribution: Overview
Use this
transaction to review the controlling documents posted as a result of executing
KSVB in update mode.
KSW1
Create Actual
Periodic Reposting Cycle
This transaction
is used to create a cycle for reposting actual costs. Reporting costs is an
easy way to repost costs from, for example, an administration cost center to
cost centers that consume the costs, such as manufacturing departments. The
sender cost center is not updated with this method. To define a periodic
reposting, create a cycle, create segments for the cycle to specify the
sender/receiver cost center relationship and specify the tracing factors for
the apportionment.
KSW2
Change Actual
Periodic Reposting Cycle
Use this
transaction to change the reposting cycle created using transaction KSW1.
KSW3
Display Actual
Periodic Reposting Cycle
Use this transaction to display the reposting cycle created
using transaction KSW1.
KSW5
Execute Actual
Periodic Reposting Cycle
This transaction
is typically used as an easy way to repost actual costs from, for example, an
administration cost center to cost centers that consume the costs, such as
manufacturing departments. Periodic reposting uses the original cost element,
meaning the primary cost element remains intact. When you allocate telephone
costs, for example, the allocating cost center is unimportant for the receiving
cost centers. The system therefore stores data records for periodic reposting
in a way that uses less memory than a distribution. The sender cost center is
not updated with this method. To define a periodic reposting, use the cycle
created via transaction KSW1 with segments for the cycle and also tracing
factors for the apportionment.
KSW7
Create Plan
Periodic Reposting Cycle
This transaction
is used to create a cycle for reposting plan costs. Reposting costs is an easy
way to repost costs from, for example, an administration cost center to cost
centers that consume the costs, such as manufacturing departments. The sender
cost center is not updated with this method. To define a periodic reposting,
you create segments and tracing factors for the apportionment. Use transaction
KSWB to execute the reposting.
KSW8
Change Plan
Periodic Reposting Cycle
Use this
transaction to change the reposting cycle created using transaction KSW7.
KSW9
Display Plan Periodic
Reposting Cycle
Use this
transaction to display the reposting cycle created using transaction KSW7.
KSWA
Delete Plan
Periodic Reposting Cycle
Use this
transaction to delete the reposting cycle created using transaction KSW7.
KSWB
Execute Plan Periodic
Reposting
This transaction
is used as an easy way to repost plan costs from, for example, an
administration cost center to cost centers that consume the costs, such as
manufacturing departments. Periodic reposting uses the original cost element, meaning
the primary cost element remains intact. When you allocate plan telephone
costs, for example, the allocating cost center is unimportant for the receiving
cost centers. The system therefore stores data records for periodic reposting
in a way that uses less memory than a distribution. The sender cost center is
not updated with this method. To define a periodic reposting, use the cycle
created via transaction KSW7 with segments for the cycle and also tracing
factors for the apportionment.
KVA5
Transfer Actual
Data from LIS Activity-Independent Statistical Key Figures, US
This transaction is used to transfer statistical key figure
data collected in the logistics information system to cost center accounting.
This data can then be used, for example, in
allocations. This
transaction transfers data that is not linked to any particular activity type.
KVD5
Transfer Actual
Data from LIS Activity-Dependent Statistical Key Figures, US
This transaction
is used to transfer statistical key figure data collected in the logistics
information system to cost center accounting. This data can then be used, for
example, in allocations. This transaction transfers activity dependent
statistical key figures.
OKP1
Maintain Period
Lock
This transaction
is used to open and close the controlling area posting periods. This is a
separate table from the finance posting period table maintained via transaction
OB52. The period lock in the controlling module can be maintained for both
actual and plan postings.
OKP2
Display Period
Lock
Use this transaction to display the controlling period lock
table maintained via transaction OKP1.
No comments:
Post a Comment