See table T158 for specifying the transactions for the MM activities RMWx.
The link between invoice verification transactions and activities is described in T169.
Only actual data or planning data is transferred for CO activities, but not statistical line items.
The specified menu paths serve only as examples. The activity can be called up various other ways as well.
------------------------------------------------------------------------
GLU1 Transfer from external system ->FI-SL
Sending application: SL Sending transaction: Program RGUREC00
Menu: Cannot be reached via the menu
Meaning:
The activity can be used to transfer external data to SL with the help of a
program analogous to RGUREC00 (only an example program/main program).
Special features:
The activity is not used by any standard applications
------------------------------------------------------------------------
JVA0 Joint Venture Accounting
Sending application: -- Sending transaction: --
Menu: Cannot be reached via the menu
Meaning:
The activity is set and used specifically by Joint Venture Accounting
Special features:
The activity may only be used for the Joint Venture ledger, not for FI-SL
ledgers.
------------------------------------------------------------------------
KAZI CO Actual calculation of imputed costs
Sending application: CO Sending transaction: KSA3
Menu:
Cost center acctg -> Actual postings -> Period-end closing -> Calc.
imputed costs
Meaning:
Calculation of imputed costs for cost centers' actual data
------------------------------------------------------------------------
KAZP CO Plan calculation of imputed costs
Sending application: CO Sending transaction: KSA8
Menu:
Cost center acctg -> Planning -> Allocations -> Calc. imputed
costs
Meaning:
Calculation of imputed costs for cost centers' plan data
------------------------------------------------------------------------
KFPP
A fixed price for a service to be provided can be specified between two WBS
elements in 3.0 (under certain conditions). A separate document is created for
this. This activity is similar to planning costs (on ordering element) or
sales revenues (on supplying element). Therefore, this data is also updated in
CO (activity 'KFPP').
The fixed price agreements are cleared by fixed price allocations. Separate
documents are also written for this. From a CO point of view costs and sales
revenues arise. For this reason, a CO document is also created (activity
'KFPI').
Behind the fixed price agreement/fixed price allocation is the concept of
local project processing with customer-vendor relationship within a project.
This is an additional view to the ones previously available (total view). For
this reason, the CO data created here is also kept in a separate CO
version.
------------------------------------------------------------------------
KFPI
see above
------------------------------------------------------------------------
KOAE Actual Settlement CO-external
Sending application: CO Sending transaction: KOA5 / KO88
Menu:
Internal orders -> Actual postings -> Period closing ->
Settlement
Meaning:
Order settlement - The FI document is created here
------------------------------------------------------------------------
KOAO Order settlement
Sending application: CO Sending transaction: KOA5 / KO88
Menu:
Internal orders -> Actual postings -> Period closing ->
Settlement
Meaning:
Order settlement - The CO document is created here
------------------------------------------------------------------------
KOAP Settlement of planned costs
Sending application: CO-OM-OPA Sending transaction: KO9E / KO9G
Menu:
Meaning:
Description: The following functionality is available as of Release 3.0: the
indicator 'Planning integration' can be set for internal orders. All planning
data of the order is then transferred to SL or profit center accounting
together with the planning data of cost center accounting (TKA07-RWINKZ = X).
If such orders use an activity from a cost center, the scheduled activity is
updated on the sender cost center. These orders can then also be settled to a
receiver cost center. If the activity KOAP (plan settlement) is not
transferred to SL, the planned cost flow would be interrupted. (Note: In
Release 3.0, only the receiver cost center and the sender internal order are
supported).
------------------------------------------------------------------------
KPIV Cost Apportionment within the cost object hierarchy
Sending application: COPC Sending transaction: KKPX, KKPY
Menu:
Controlling -> Product cost acctg -> Repetitive mfg. -> Actual
postings ->Period-end closing -> Distribution
Meaning:
Distribution of the actual costs of the cost object ID numbers to the assigned
single objects in the cost object hierarchy.
------------------------------------------------------------------------
KSII Actual activity price computation
Sending application: CO-CCA Sending transaction: KSII
Menu:
Cost Center Accounting menu Actual postings -> Period-end closing ->
Calc. activity price
Meaning:
Actual activity prices are determined with the transaction; it is the
counterpart of plan activity price computation (KSPI). However, unlike plan
activity price computation, activity price and cost records are written using
activity KSII. The cost records (COSS) then contain the delta value for the
valuation made during quantity posting. These records are only created if a
valuation for actual data is defined for actual activity prices.
------------------------------------------------------------------------
KSP1 Splitting plan primary
Sending application: CO-CCA, CO-ABC Sending transaction:
Menu:
Meaning:
Meaning: Splitting the primary activity-independent planned costs over the
activity types of the cost center. Special features: Data is posted with value
type 02. In order to avoid internal business volume on the cost center, the
debit and credit records are written with the same BEKNZ.
------------------------------------------------------------------------
KSP2 Splitting planned secondary
Sending application: CO-CCA, CO-ABC Sending transaction:
Menu:
Meaning: Splitting the primary activity-independent planned costs on the
activity types of the cost center.
Special features: It is posted with value type 02. To avoid internal business
volume on the cost center, the debit and credit records are written with the
same BEKNZ.
------------------------------------------------------------------------
KSP3 Splitting planILV
Sending application: CO-CCA, CO-ABC Sending transaction:
Menu:
Meaning:
Meaning: Splitting the activity-independent planned costs from ILV over the
activity types of the cost center.
Special features: Data is posted with value type 02. To avoid internal
business volume on the cost center, the debit and credit records are written
with the same BEKNZ.
------------------------------------------------------------------------
KSPA Assessment of cost center costs actual in profitability analysis
Sending application: CO-PA Sending transaction: KEU5
Menu:
Accounting -> Controlling -> Profit. analysis -> -> Actual
postings -> Assess cst-ctr costs
Meaning:
Crediting the cost centers and debiting the reconciliation
object/profitability segment is carried out with this activity.
------------------------------------------------------------------------
KSI1 Splitting ACTUAL primary
Sending application: CO-CCA, CO-ABC Sending transaction: KSS1, KSS2
Menu:
Meaning:
Meaning: Splitting the primary activity-independent actual costs over the
activity types of the cost center.
Special features: Data is posted with value type 03. To avoid internal
business volume on the cost center, the debit and credit records are written
with the same BEKNZ.
------------------------------------------------------------------------
KSI2 Splitting ACTUAL secondary
Sending application: CO-CCA, CO-ABC Sending transaction: KSS1, KSS2
Menu:
Meaning:
Meaning: Splitting the secondary activity-independent actual costs over the
activity types of the cost center.
Special features: Data is posted with value type 03. To avoid internal
business volume on the cost center, the debit records and credit records are
written with the same BEKNZ.
------------------------------------------------------------------------
KSPA Assessment to profitability analysis
------------------------------------------------------------------------
KZPI Actual periodic overhead
Sending application: CO, PS, PP Sending transaction: KGI2, CJ44
Menu:
Accounting -> Controlling -> Internal orders -> Actual postings ->
Period closing -> Overhead
Accounting -> Project management -> Execution -> Period closing -> Overhead costs
Logistics -> Production -> Production control -> Environment ->
Periodic allocations -> Calculate overheads
Meaning:
Calculation of periodic overhead rates for actual data on orders, projects,
networks
------------------------------------------------------------------------
KZPP Planned periodic overhead
Sending application: CO, PS Sending transaction: KGP2, CJ46
Menu:
Accounting -> Controlling -> Internal orders -> Planning ->
Period closing -> Overhead
Accounting -> Project management -> Planning -> Costs/Revenues ->
Overhead costs -> Indiv. processing
Meaning:
Calculation of periodic overhead rates in planning on orders, projects,
networks
------------------------------------------------------------------------
KZRI Interest calculation projects
Sending application: PS (Project System) Sending transaction: CJZ1
Menu:
Accounting -> Project management -> Execution -> Period closing ->
Interest calculation
Meaning:
Daily account balance interest calculation for the project. The balance
calculation is carried out on the basis of payment documents, down payment
documents and internal activity documents. The method used for FI-SL account
interest calculation is used to calculate the interest. As a result, the same
functions are available as in FI: mananging backdated value dates, recognition
of interest rate changes, interest indicator account determination for the
update, different calendars ... . The result of the interest calculation is
posted via an accounting document. The project is then debited with the
interest costs via a corresponding posting to expense account (or credited to
the revenues). The document selection, the interest calculation and the
interest posting is carried out technically separately or each affected
account assignment object (WBS element, order..) of the project hierarchy.
This document (accounting document) also updates the general ledger.
------------------------------------------------------------------------
LIS0 SD billing document - not for SL
Sending application: SD Sending transaction: VF01 / VF04
Menu:
Logistics -> Sales/distribution -> Billing
Meaning:
Billing document
Special features:
Only for profit center accounting; not to be used for SL ledgers
The SL already receives the data via FI via the activity RFBU.
As of Release 3.0, the activity is replaced by SD00.
------------------------------------------------------------------------
PAPL Sales planning and profit planning
Sending application:
Profitability analysis (CO-PA)
Sales and profit planning for ledger-based profitability ananlysis
(CO-PA-SPL).
Transaction:
KE11 (profit planning), KE1A (total planning) and further transactions
Menu:
Profit. analysis -> Planning
Meaning:
The activity PAPL is used for updating the planned costs, sales revenues and
quantities within ledger-based profitability analysis ("profibility analysis
account form"). Planning is carried out at account level for profitability
segments which are defined by characterisitics such as customer, material,
product group, sales district, division, and so on..
Example: Sales and profit planning
Sales district 0023 California
Account 800000 Sales revenues
Product group Sales volume Sales revenue
001 Power saws 2000 pc 6,000,000 DM
002 Drilling mach. 4000 pc 4.000.000 DM
003 Keyhole saws 3000 pc 3.000.000 DM
...
In contrast to the costing-cased profitability analysis, the data for the
ledger-based profitability is stored in the tables of the CO object. tables
COBK, COEJ and COSP are updated. The activity PAPL controls the number
assignment of the plan line items as well as the forwarding of the data.
------------------------------------------------------------------------
PRC1 Transfer of planned data to PrCtr
This activity is only for Profit Center Accounting. It may not be assigned to
a SL ledger.
------------------------------------------------------------------------
PCAP Direct planning in Profit Center planning (not integrated)
This activity is only for Profit Center Accounting. It may not be assigned to
a SL ledger.
------------------------------------------------------------------------
PRC2 EC-PCA (currently without application)
This activity is only for Profit Center Accounting. It may not be assigned to
a SL ledger.
------------------------------------------------------------------------
PRC3 FI transfer of data to EC-PCA
This activity is only for Profir Center Accounting. It may not be assigned to
a SL ledger.
------------------------------------------------------------------------
PRCU Transfer of actual data PrCtr
This activity is only for Profit Center Accounting. It may be not assigned to
a SL ledger.
------------------------------------------------------------------------
RFBU FI postings
Sending application: FI Sending transaction:
Menu:
Meaning:
Postings in Financial Accounting
Special features:
With this activity, all documents from FI are posted directly to SL, providing
they update the general ledger (ledger 00). Even if FI is started via a
preliminary application (for example, billing document), FI provides this
activity.
------------------------------------------------------------------------
RFIG FI memo postings
Sending application: FI Sending transaction:
Menu:
Meaning:
Memo postings in FI
Special features:
This activity is not posted directly to SL and also should not be assigned to
a ledger.
------------------------------------------------------------------------
RFLC FI postings Business area cons.
This activity is derived and used internally for consolidation. It may not be
assigned to a SL ledger since SL already receives the data from FI via
activity RFBU.
------------------------------------------------------------------------
RFRK FI reconciliation posting to a P+L account
Sending application: CO Sending transaction:
Menu:
Meaning:
Due to the reconciliation ledger, CO adjustment postings of CO are passed on
to FI. These are posted to FI under this activity.
Note:
This activity can only be assigned to a ledger if no CO data is transferred
into that ledger. If the CO data are also transferred to the the ledger
already has this information.
------------------------------------------------------------------------
RFST FI statistical postings
Sending application: FI Sending transaction:
Menu:
Meaning:
Statistical postings in Financial Accounting
Special features:
This activity is NOT posted directly to SL and also should not be assigned to
a ledger.
------------------------------------------------------------------------
RGG0 FI-SL actual global posting (GB11)
Sending application: SL Sending transaction: GB11
Menu:
Spec. Purpose Ledger -> Actual posting -> Global documents
Meaning:
SL document entry for global ledgers (actual data)
------------------------------------------------------------------------
RGG1 FI-SL plan global posting (GB11)
Sending application: SL Sending transaction: GB11
Menu:
Spec. Purpose Ledger -> Actual posting -> Global documents
Meaning:
SL document entry for global ledgers (planning data)
------------------------------------------------------------------------
RGL0 FI-SL actual local posting (GB01)
Sending application: SL Sending transaction: GB01
Menu:
Spec. Purpose Ledger -> Actual posting -> Local documents
Meaning:
SL document entry for local and global ledgers (actual data)
------------------------------------------------------------------------
RGL1 FI-SL plan local posting (GB01)
Sending application: SL Sending transaction: GB01
Menu:
Spec. Purpose Ledger -> Actual posting -> Local documents
Meaning:
SL document entry for local and global ledgers (planning data)
------------------------------------------------------------------------
RKAL Restructure reconciliation ledger
Sending application: CORCL Sending transaction: KAL1
Menu:
Accounting -> Controlling -> Cost element acctg -> Tools ->
Reconcil. ledger -> Follow-up posting
This activity is internally derived and used for the reconciliation ledger. It
may be not be assigned to a SL ledger since GL already receives the data with
other activities.
This activity is used internally for the reconciliation ledger. Summary
records of the reconciliation ledger (table COFIT) which were written by the
function 'Follow-up posting' are indicated with the activity (ACTIV) RKAL.
------------------------------------------------------------------------
RKIB CO actual periodic transfer postings
Sending application: CO Sending transaction: KSW5
Menu:
Cost center acctg -> Actual postings -> Period-end closing ->
Periodic repostings
Meaning:
Periodic transfer postings
------------------------------------------------------------------------
RKIL CO actual inverse activity allocation
Sending application: CO-CCA Sending transaction: KSC5/KSC6
Menu:
Cost center acctg -> Planning -> Allocation -> Inv. activity
alloc.
Meaning:
1. Activity quantities posted to senders are distributed to the valid
receivers according to the receiver definition in the segment (similar to
"distribution", only there with costs)
2. Receivers specify reference activities. Sender is credited inversely with
the total of the receiver activity quantities.
------------------------------------------------------------------------
RKIU CO actual assessment
Sending application: CO Sending transaction: KSU5
Menu:
Cost center acctg -> Actual post. -> Period-end closing ->
Assessment
Meaning:
Assessments in Cost Center Accounting
------------------------------------------------------------------------
RKIV CO actual distribution
Sending application: CO Sending transaction: KSV5
Menu:
Cost center acctg -> Actual post. -> Period-end closing ->
Distribution
Meaning:
Distributions in Cost Center Accounting
------------------------------------------------------------------------
RKL CO actual activity allocation
Sending application: CO Sending transaction: KB21
Menu:
Cost center acctg -> Actual posting -> Activity allocation
Meaning:
Activity allocations in Cost Center Accounting
------------------------------------------------------------------------
RKN Not relevant for SL
------------------------------------------------------------------------
RKP1 CO primary cost planning
Sending application: CO Sending transaction: KP12
Menu:
Cost center acctg -> Planning -> Primary costs ->
Activity-independent
Meaning:
Activity-independent primary cost planning
------------------------------------------------------------------------
RKP2 CO activity planning
Sending application: CO Sending transaction: KP22
Menu:
Cost center acctg -> Planning -> Activity types
Meaning:
Activity type planning
------------------------------------------------------------------------
RKP3 CO activity inputs
Sending application: CO Sending transaction: KP32
Menu:
Cost center acctg -> Planning -> Cost elements -> Secondary
Meaning:
Activity-independent planning of activity input
------------------------------------------------------------------------
RKP4 CO statistical key figure planning
Sending application: CO Sending transaction: KP42
Menu:
Cost center acctg -> Planning -> Stat. key figures
Meaning:
Planning the statistical key figures
------------------------------------------------------------------------
RKP5 CO revenue planning
Sending application: CO Sending transaction: KP52
Menu:
Cost center acctg -> Planning -> Cost elements -> Revenue
Meaning:
Revenue planning
Since this activity only writes statistical documents, it will not update the
SL.
------------------------------------------------------------------------
RKP6 CO activity-dependent primary cost planning
Sending application: CO Sending transaction: KP62
Menu:
Cost center acctg -> Planning -> Cost elements -> Primary
Meaning:
Activity-dependent primary cost planning
------------------------------------------------------------------------
RKP7 CO activity dependent activity input planning
Sending application: CO Sending transaction: KP72
Menu:
Cost center acctg -> Planning -> Cost elements -> Primary
Meaning:
Activity-dependent input planning
------------------------------------------------------------------------
RKP8 CO order costs
See RKP1 - this function can provide both activities
------------------------------------------------------------------------
RKP9 CO plan activity-dependent job costs
See RKP6 - this function can provide both activities
------------------------------------------------------------------------
RKPA CO Planung actual-dependent statistical key figures
Sending application: CO Sending transaction: KP46
Menu:
Cost center acctg -> Planning -> ...
Meaning:
Planning of statistical key figures on cost center/activity type combinations.
The activity is similar to RKP4 from an update point of view. Cost and
activity objects appear here as object numbers. These statistical key figures
can, for example, be used for splitting activity-independent planned costs on
the activity types of a cost center.
------------------------------------------------------------------------
RKPB CO periodic transfer posting in the plan - Planning aids
Sending application: CO-CCA Sending transaction: KSWB/KSWC
Menu:
Cost center acctg -> Planning -> Planning aids -> Periodic
repostings
Meaning:
Like RKIB (periodic transfer posting), only in plan here
------------------------------------------------------------------------
RKPL CO plan inverse activity allocation
Sending application: CO-CCA Sending transaction: KSCB/KSCC
Menu:
Cost center acctg -> Actual postings -> Period-end closing -> Inverse
actvty alloc.
Meaning:
1. Activity quantities posted to senders are distributed to the valid
receivers according to receiver definition in the segment (similar to
"distribution", only there with costs)
2. Receivers specify reference activities. Sender is credited inversely with
the total of the receiver activity quantities
------------------------------------------------------------------------
RKPQ Manual cost planning
Not relevant for SL
------------------------------------------------------------------------
RKPU CO planning assessment
Sending application: CO Sending transaction: KSUB
Menu:
Cost center acctg -> Planning -> Allocation -> Assessment
Meaning:
Plan assessment
------------------------------------------------------------------------
RKPV CO planning distribution
Sending application: CO Sending transaction: KSUV
Menu:
Cost center acctg -> Planning -> Allocation -> Distribution
Meaning:
Plan distribution
------------------------------------------------------------------------
RKPW CO secondary order cost planning
Sending application: CO Sending transaction: KPW2
Menu:
Cost center acctg -> Planning -> Cost elements -> Secondary
Meaning:
Planning of activity-independent secondary order cost planning
------------------------------------------------------------------------
RKPX CO activity-dependent secondary order cost planning
Sending application: CO Sending transaction: KPX2
Menu:
Cost center acctg -> Planning -> Cost elements -> Secondary
Meaning:
Planning activity-dependent secondary order cost planning
------------------------------------------------------------------------
RKPZ CO Planned credti for overheads
Sending application: CO Sending transaction:
Menu:
Meaning:
With orders, you can calculate overhead rates for actual data. In this case an
order is charged overhead and a cost center possibly credited when an
offsetting entry is made. Since these surcharges are not calculated in the
plan on the orders, but the costs can be planned on the cost centers, you can
now plan the credits manually on the cost centers. This allows you to carry
out a plan/actual comparison for these overhead cost elements.
------------------------------------------------------------------------
RKRF Write control record to the reconciliation ledger via Financial
Accounting reconciliation posting
Sending application: CORCL Sending transaction: KALC
Menu:
Accounting -> Controlling -> Cost element acctg -> Actual postings
-> Recon. posting CO-FI
Meaning:
With the activity RKRF, recordsd are written to the reconciliation ledger,
which were confirmed to FI as reconciliation postings of the intercompany or
cross-business area CO allocations.
The reconciliation ledger creates separate documents for FI reconciliation
postings. These are only stored in the reconciliation ledger.
Note:
Since it is only reconciliation ledger data, this activity is not supported
for SL and thus should not be assigned to a ledger.
------------------------------------------------------------------------
RKS CO Actual statistical key figures
Sending application: CO Sending transaction: KB31
Menu:
Cost center acctg -> Actual posting -> Stat. key figures
Meaning:
Posting statistical key figures in Cost Center Accounting
------------------------------------------------------------------------
RKU1 CO Actual primary cost transfer posting
Sending application: CO Sending transaction: KB11
Menu:
Cost center acctg -> Actual posting -> Repost costs
Meaning:
Reposting costs in cost center accounting
------------------------------------------------------------------------
RKU2 CO Actual revenue transfer posting
Sending application: CO Sending transaction: KB41
Menu:
Cost center acctg -> Actual posting -> Repost revenues
Meaning:
Reposting revenues in Cost Center Accounting
Since this activity provides only statistical documents, this data is not
transferred to SL.
------------------------------------------------------------------------
RKU3 CO reposting of CO line items with FI reference
Sending application: CO Sending transaction: KB61, KB64
Menu:
(per application), Actual postings -> Repost line items
Meaning:
The activity RKU3 describes a new reposting transaction in CO in which
selected line items from CO documents can be reposted. In this case, the CO
documents must have a reference to an accounting document in FI. For an FI
document, the user chooses the line items of the respective CO document which
are to be reposted. The selected line items are then transferred so that the
amount is assigned by the account assignment object of the line item as a
sender to a receiver cost-object to be entered again. Here, the amount to be
reposted can be distributed to several new receivers. The debits/credits
indicator is transferred from the line item and updated immediately for sender
and receiver. These repostings create new CO documents which always contain
the reference to the respective FI document, in contrast to the existing
reposting documents.
------------------------------------------------------------------------
RMBL MM material debit / crediting
Sending application: MM Sending transaction:
Menu:
Meaning:
------------------------------------------------------------------------
RMM1 MM Material ledger closing
Sending application: MM Sending transaction: CKM4
Menu:
Logistics -> Materials Management -> Valuation -> Material ledger
-> Closing -> Material
Meaning:
The activities since the last closing of the material now take when the price
is determinged for the new period price. The new period price is valid until
the material is closed again. The resulting necessary postings to the
inventory stock account and its offsetting entries are made via the newly
created SL activity RMM1, where the currencies are calculated by the sender
and passed to the RW-interface.
------------------------------------------------------------------------
RMPR MM material price change
Sending application: MM Sending transaction: MR21, CK21
Menu:
Meaning:
------------------------------------------------------------------------
RMRP MM incoming invoice
Sending application: MM Sending transaction: MR01, MR02, MR1M
MR11, MRHG, MR21
MR41, MR42
Menu:
Meaning:
------------------------------------------------------------------------
RMRU MM Goods movement for completion confirmation
Sending application: MM Sending transaction:
Menu:
Meaning:
The material consumption to be posted as backflush was up to now posted with
confirmations for production orders via automatically generated material
documents. These material documents were indicated with the transaction type
'WA' and the SL activity 'RMWA', like a goods movement entered directly via a
goods issue transaction. On the other hand, goods received for production
orders were indicated with the transaction type 'WF' and the SL activity
'RMWF'. With this enhancement, it is now also possible to post goods received
as backflush for production orders from the confirmation. Nevertheless, if
both withdrawals and goods received are now posted to a material document from
a confirmation, only one transaction type and one SL activity can be assigned
for it. For this reason, all goods movements posted via the confirmation are
indicated with the transaction type 'WR' and the G/L activity 'RMRU'. In this
respect, withdrawals posted as backflush are indicated differently as
previously as of Release 2.2.
------------------------------------------------------------------------
RMUM MM revaluations
Sending application: MM Sending transaction:
Menu:
Meaning:
If revaluations resulted for postings based on the activities RMWA, RMWE,
RMWF, RMWI or RMWL, they are sent with the activity RMWU. The activity does
not apply to Release 3.0. Revaluations are then sent with the original
activity again.
------------------------------------------------------------------------
RMWA MM Goods movement
Sending application: MM Sending transaction:
Menu:
Meaning:
------------------------------------------------------------------------
RMWE MM Goods receipts purchase order
Sending application: MM Sending transaction:
Menu:
Meaning:
------------------------------------------------------------------------
RMWF MM Goods receipts production order
Sending application: MM Sending transaction:
Menu:
Meaning:
------------------------------------------------------------------------
RMWI MM Inventory difference
Sending application: MM Sending transaction:
Menu:
Meaning:
------------------------------------------------------------------------
RMWL MM goods issue delivery
Sending application: MM Sending transaction:
Menu:
Meaning:
------------------------------------------------------------------------
RMWQ MM goods movement usage decision
Sending application: MM Sending transaction:
Menu:
Meaning:
When deciding to use inspection lots, the material transfer postings were in
previous releases posted via automatically generated material documents. These
material documents were indicated with the transaction type 'GI' and the SL
activity 'RMWA', like a goods movement entered directly via a goods issue
transaction. Return deliveries for the purchase order could not, however, be
carried out in the inspection lot only with the transaction type 'BE' and the
SL activity 'RMWE'. With this enhancement, it is now also possible to post
return deliveries for the purchase order from the usage decision.
Nevertheless, if both material transfer postings and a return delivery are now
posted to a material document for a usage decision, only one transaction type
and one SL activity can be assigned for it. For this reason, all goods
movements posted via the usage decision are indicated with the transaction
type 'WQ' and the SL activity 'RMWQ'. In this respect, material transfer
postings for the usage decision and return deliveries for the purchase order
are indicated differently than previous to Release 2.2.
------------------------------------------------------------------------
SD00 Billing document or collective billing
Sending application: SD Sending transaction: VF01 / VF04
Menu:
Logistics -> Sales/distribution -> Billing
Meaning:
Billing document or collective billing in SD
Special features:
This activity also updates the general ledger. It replaces activity LIS0.
However, the data of this activity is forwarded to SL via activity RFBU.
------------------------------------------------------------------------ Activities which are not posted on to the SL:
CPIS Splitting actual ABC
CPPS Splitting plan ABC
CPIL Inverse activity allocation actual ABC
CPPL Inverse activity allocation plan ABC
CPRA Resource assessment actual ABC
CPRP Resource assessment plan ABC
CPPA Process assessment actual ABC
CPPP Process assessment plan ABC
KEXX, KPPx