Transfer Subcontracting Accounts to COPA

we need to transfer Subcontracting Accounts to CO-PA during the MIGO Transaction we have Three Cost Elements Generated During the Posting (Material Consumption Account , Subcontracting Charges , Semi finished output ) which of these Accounts Shall be Transferred to CO-PA And how can we maintain it to be able to transfer them to CO-PA ?
Thanks,

Hi mazen
None of these should post to COPA upon MIGO
You must have a separate cost center for subcon and all these GLs must post to this CC. You do this setting in OKB9.
Only if you have activated price diff postings for sub con, that should post to COPA. GL is assigned in PRD in obyc and default assignment to PSG in okb9
Br. Ajay M

Similar Messages

Reconcile Accounts Based COPA with FI

Dear Experts,
My client needs material wise, customer wise, Sales Area-wise, region wise etc profitability report. The only way to achieve this is through COPA.I have confusion whether to go for Costing based COPA (CBC) or Accounts based COPA (ABC).
I am afraid of CBC because reports from CBC do not automatically reconcile with FI and I will have a life long task of explaining the difference to management. I have seen clients scarpping CBC because at the end CBC works on calculated values which cannot inherently tally with FI and soon management stops trusting CBC. Moreover Gross Profit level figures for each characteristics can be obtained straight from LIS instead of going for CBC.
I am sure that ABC will reconcile with FI. I presume that this will happen ONLY if field status group of all cost and revenue accounts have been configured to mandate posting to PSG. Else even ABC will not reconicle with FI. My question is If I mandate PSG for all cost/revenue posting then I fear that automatic postings coming from MM/HR will go into error. How do we handle this and achieve ABC = FI.
If anyone has come across ABC to FI reconcilation error/issues I would like take their guidance before I move forward.
Regards
Deepak Saxena

Hi..!
You can use either activate Costing Based CO PA nor Accounting Based CO PA.
1.Costing based CO-PA - it will be difficult to reconcile FI with CO PA as lot of time it will take to reconcile.
For this you need to do assessment - settlements and direct postings from FI-MM-SD to CO PA thru PA transfer structure.
You can find the Differences of FI -CO PA in KEAT t-code and based on the you can understand why it is showing difference (If any). This T-code will help you to reconcile.
2.Accounting Based CO-PA it is easy to reconcile and here the reconciliation happens between GL Account and Cost element level. So you wont get many issues while reconciling.
In Costing based CO-PA you can draw a report at COGS Level where as you wont get it in Account Based CO-PA.
Thanks,
Anil

MM subcontracting Account determination

Hi All,
Any one knows MM subcontracting Account determination in OBYC?
any help is appreciated..
Thanks,
Rau

Hi,
Hi,
For Account Determination 5 major characteru2019s are as follow:
1.Chart of Account,
2.Valuation Class,
3.Transaction Event Key,
4.Valuation Grouping Code,
5.Account Grouping Code/Account Modifier.
Configuration of Automatic Account Determination with T.Code are as follow:
1.OMSK: valuation Class with Account category reference,
2.OMWM: Active Valuation Grouping Code,
3.OMWN: Active Movement type with G/L account,
4.OMWD: Active Valuation Area,
5.OMWB: Active Chart of account,Valuation Grouping Code,Account Grouping Code,Valuation Class and G/L acocounts
In OMWB or OBYC
Click TE key and enter Chart of account and then save the Roles 1st for
1.Debit/Credit
2.General modification
3.Valuation Modif
4.Vakuation class
And then enter respective critetia for that TE key and save.
If assignment(Chart of account,Valuation Grouping Code,Account Grouping Code,Valuation Class and G/L acocounts
are correct and u would not face any problems in G/GI/IV.
The TE keys are:
Expense/revenue from consumption of consignment material (AKO)
This transaction is used in Inventory Management in the case of
withdrawals from consignment stock or when consignment stock is
transferred to own stock if the material is subject to standard
price control and the consignment price differs from the standard
price.
u2022 Expenditure/income from transfer posting (AUM)
This transaction is used for transfer postings from one material to
another if the complete value of the issuing material cannot be
posted to the value of the receiving material. This applies both to
materials with standard price control and to materials with moving
average price control. Price differences can arise for materials
with moving average price if stock levels are negative and the stock
value becomes unrealistic as a result of the posting. Transaction
AUM can be used irrespective of whether the transfer posting
involves a transfer between plants. The expenditure/income is added
to the receiving material.
u2022 Provisions for subsequent (end-of-period rebate) settlement (BO1)
If you use the "subsequent settlement" function with regard to
conditions (e.g. for period-end volume-based rebates), provisions
for accrued income are set up when goods receipts are recorded
against purchase orders if this is defined for the condition type.
u2022 Income from subsequent settlement (BO2)
The rebate income generated in the course of "subsequent settlement"
(end-of-period rebate settlement) is posted via this transaction.
u2022 Income from subsequent settlement after actual settlement (BO3)
If a goods receipt occurs after settlement accounting has been
effected for a rebate arrangement, no further provisions for accrued
rebate income can be managed by the "subsequent settlement"
facility. No postings should be made to the account normally used
for such provisions. As an alternative, you can use this transaction
to post provisions for accrued rebate income to a separate account
in cases such as the one described.
u2022 Change in stock (BSV)
Changes in stocks are posted in Inventory Management at the time
goods receipts are recorded or subsequent adjustments made with
regard to subcontract orders.
If the account assigned here is defined as a cost element, you must
specify a preliminary account assignment for the account in the
table of automatic account assignment specification (Customizing for
Controlling) in order to be able to post goods receipts against
subcontract orders. In the standard system, cost center SC-1 is
defined for this purpose.
Stock posting (BSX)
This transaction is used for all postings to stock accounts. Such
postings are effected, for example:
In inventory management in the case of goods receipts to own
stock and goods issues from own stock
In invoice verification, if price differences occur in
connection with incoming invoices for materials valuated at
moving average price and there is adequate stock coverage
In order settlement, if the order is assigned to a material with
moving average price and the actual costs at the time of
settlement vary from the actual costs at the time of goods
receipt
Because this transaction is dependent on the valuation class, it is
possible to manage materials with different valuation classes in
separate stock accounts.
Caution :
Take care to ensure that:
A stock account is not used for any transaction other than BSX
Postings are not made to the account manually
The account is not changed in the productive system before all
stock has been booked out of it
Otherwise differences would arise between the total stock value of
the material master records and the balance on the stock account.
Revaluation of "other" consumptions (COC)
This transaction/event key is only relevant to Brazil. It is used if
a revaluation report is used for company codes in Brazil.
The revaluation report uses the actual prices determined by the
material ledger/actual costing to:
Revaluate costs on the basis of actual prices
Post the price differences arising from "other" consumptions
(e.g. consumption to cost center) to a collective account
This transaction/event key is needed to post the price differences.
The account specified here is posted with the price differences for
"other" consumptions.
o documentation currently available.
Small differences, Materials Management (DIF)
This transaction is used in Invoice Verification if you define a
tolerance for minor differences and the balance of an invoice does
not exceed the tolerance.
Purchase account(EIN), purchase offsetting account (EKG), freight
purchase account (FRE)
These transactions are used only if Purchase Account Management is
active in the company code.
Freight clearing (FR1), provision for freight charges (FR2), customs
duty clearing (FR3), provision for customs duty (FR4)
These transactions are used to post delivery costs (incidental
procurement costs) in the case of goods receipts against purchase
orders and incoming invoices. Which transaction is used for which
delivery costs depends on the condition types defined in the
purchase order.
You can also enter your own transactions for delivery costs in
condition types.
External service (FRL)
The transaction is used for goods and invoice receipts in connection
with subcontract orders.
If the account assigned here is defined as a cost element, you must
specify a preliminary account assignment for the account in the
table of automatic account assignment specification (Customizing for
Controlling) in order to be able to post goods receipts against
subcontract orders. In the standard system, cost center SC-1 is
defined for this purpose.
External service, delivery costs (FRN)
This transaction is used for delivery costs (incidental costs of
procurement) in connection with subcontract orders.
If the account assigned here is defined as a cost element, you must
Offsetting entry for stock posting (GBB)
Offsetting entries for stock postings are used in Inventory
Management. They are dependent on the account grouping to which each
movement type is assigned. The following account groupings are
defined in the standard system:
AUA: for order settlement
AUF: for goods receipts for orders (without account
assignment)
and for order settlement if AUA is not maintained
AUI: Subsequent adjustment of actual price from cost center
directly
to material (with account assignment)
BSA: for initial entry of stock balances
INV: for expenditure/income from inventory differences
VAX: for goods issues for sales orders without
account assignment object (the account is not a cost
element)
VAY: for goods issues for sales orders with
account assignment object (account is a cost element)
VBO: for consumption from stock of material provided to
vendor
VBR: for internal goods issues (for example, for cost
center)
VKA: for sales order account assignment
(for example, for individual purchase order)
VKP: for project account assignment (for example, for
individual PO)
VNG: for scrapping/destruction
VQP: for sample withdrawals without account assignment
VQY: for sample withdrawals with account assignment
ZOB: for goods receipts without purchase orders (mvt type
501)
ZOF: for goods receipts without production orders
(mvt types 521 and 531)
You can also define your own account groupings. If you intend to
post goods issues for cost centers (mvt type 201) and goods issues
for orders (mvt type 261) to separate consumption accounts, you can
assign the account grouping ZZZ to movement type 201 and account
grouping YYY to movement type 261.
Caution
If you use goods receipts without a purchase order in your system
(movement type 501), you have to check to which accounts the account
groupings are assigned ZOB
If you expect invoices for the goods receipts, and these invoices
can only be posted in Accounting, you can enter a clearing account
(similar to a GR/IR clearing account though without open item
management), which is cleared in Accounting when you post the vendor
invoice.
Note that the goods movement is valuated with the valuation price of
the material if no external amount has been entered.
As no account assignment has been entered in the standard system,
the assigned account is not defined as a cost element. If you assign
a cost element, you have to enter an account assignment via the
field selection or maintain an automatic account assignment for the
cost element.
Purchase order with account assignment (KBS)
You cannot assign this transaction/event key to an account. It means
that the account assignment is adopted from the purchase order and
is used for the purpose of determining the posting keys for the
goods receipt.
Exchange rate differences in the case of open items (KDM)
Exchange rate differences in the case of open items arise when an
invoice relating to a purchase order is posted with a different
exchange rate to that of the goods receipt and the material cannot
be debited or credited due to standard price control or stock
undercoverage/shortage.
Differences due to exchange rate rounding, Materials Management
(KDR)
An exchange rate rounding difference can arise in the case of an
invoice made out in a foreign currency. If a difference arises when
the posting lines are translated into local currency (as a result of
rounding), the system automatically generates a posting line for
this rounding difference.
Consignment liabilities (KON)
Consignment liabilities arise in the case of withdrawals from
consignment stock or from a pipeline or when consignment stock is
transferred to own stock.
Depending on the settings for the posting rules for the
transaction/event key KON, it is possible to work with or without
account modification. If you work with account modification, the
following modifications are available in the standard system:
None for consignment liabilities
PIP for pipeline liabilities
Offsetting entry for price differences in cost object hierarchies
(KTR)
The contra entry for price difference postings (transaction PRK)
arising through settlement via material account determination is
carried out with transaction KTR.
Price differences (PRD)
Price differences arise for materials valuated at standard price in
the case of all movements and invoices with a value that differs
from the standard price. Examples: goods receipts against purchase
orders (if the PO price differs from the standard pricedardpreis),
goods issues in respect of which an external amount is entered,
invoices (if the invoice price differs from the PO price and the
standard price).
Price differences can also arise in the case of materials with
moving average price if there is not enough stock to cover the
invoiced quantity. In the case of goods movements in the negative
range, the moving average price is not changed. Instead, any price
differences arising are posted to a price difference account.
Depending on the settings for the posting rules for
transaction/event key PRD, it is possible to work with or without
account modification. If you use account modification, the following
modifications are available in the standard system:
None for goods and invoice receipts against purchase orders
PRF for goods receipts against production orders and
order settlement
PRA for goods issues and other movements
PRU for transfer postings (price differences in the case
of external amounts)
Provision for delivery costs (RUE)
Provisions are created for accrued delivery costs if a condition
type for provisions is entered in the purchase order. They must be
cleared manually at the time of invoice verification.
Taxes in case of transfer posting GI/GR (TXO)
This transaction/event key is only relevant to Brazil (nota fiscal).
Revenue/expense from revaluation (UMB)
This transaction/event key is used both in Inventory Management and
in Invoice Verification if the standard price of a material has been
changed and a movement or an invoice is posted to the previous
period (at the previous price).
Unplanned delivery costs (UPF)
Unplanned delivery costs are delivery costs (incidental procurement
costs) that were not planned in a purchase order (e.g. freight,
customs duty). In the SAP posting transaction in Logistics Invoice
Verification, instead of distributing these unplanned delivery costs
among all invoice items as hitherto, you have the option of posting
them to a special account. A separate tax code can be used for this
account.
Input tax, Purchasing (VST)
Transaction/event key for tax account determination within the
"subsequent settlement" facility for debit-side settlement types.
The key is needed in the settlement schema for tax conditions.
Goods issue, revaluation (inflation) (WGI)
This transaction/event key is used if already-posted goods issues
have to be revaluated following the determination of a new market
price within the framework of inflation handling.
Goods receipt, revaluation (inflation) (WGR)
This transaction/event key is used if already-effected transfer
postings have to be revaluated following the determination of a new
market price within the framework of inflation handling. This
transaction is used for the receiving plant, whereas transaction WGI
(goods receipt, revaluation (inflation)) is used for the plant at
which the goods are issued.
GR/IR clearing (WRX)
Postings to the GR/IR clearing account occur in the case of goods
and invoice receipts against purchase orders. For more on the GR/IR
clearing account, refer to the SAP Library (documentation MM
Material Valuation).
Caution
You must set the Balances in local currency only indicator for the
GR/IR clearing account to enable the open items to be cleared. For
more on this topic, see the field documentation.
Thanks,
Raja

Quantity in Account Based COPA upon WBS Settlement

Hi All
I am facing an issue with the quantity flow into Account Based COPA.
We have activated account based COPA and we use sales orders/billing and also Projects.
When I am creating sales order (no reference to WBS), delivery against sales order and billing from delivery, I see that
quantity posted in Delivery document and quantity from billing document are transferred to account based COPA along with GL postings.
But when I am creating sales orders with account assignment of WBS, then all the delivered quantity and billed quantity
are posted to WBS elements along with the FI postings. Receiver on my WBS is COPA segment.
When I settle the WBS that carry both revenues and costs (COGS to be sepcific), I see that amounts are settled correctly with
right GL accounts into account based COPA, but I do not see that quantities getting transferred.
I know how we can transfer quantities using costing based COPA during settlement (using PA Transfer structure with Qty setting), but
not sure how it works in account based COPA for settlements.
Any thoughts on how to transfer quantities from WBS settlement to account based COPA.
Your help is much appreciated
Thanks
Rama

Hello Rama,
First of all, I want to give you with note 352610 some general
information about the update of quantities in CO. For further
analyses I would recommand you report RKACSHOW where you can
find the relevant tables you can take a look, f.e. table COKA,
COSS(A) and COSS(A). Probabely in table COKA the field 'MEINH'
is not filled.
Furthermore I want to provide you note 27922 which explains in detail
the system behaviour for settlements in this case.
https://service.sap.com/sap/support/notes/352610
https://service.sap.com/sap/support/notes/27922
Thanks and best regards,
Ronghua Fan

I have set up a second iTunes user account on my PC, but when I create the new iTunes account it copies the music, videos etc from the original account and they seem to be linked. What am I doing wrong?

I have set up a second iTunes user account on my PC, but when I create the new iTunes account it copies the music, videos etc from the original account and they seem to be linked, so that when I delete a song from one library it deletes from the other one.
On the online tutorials I've seen it shows that when you create a new iTunes library it should open as a blank account, but that isn't happening.
What am I doing wrong?

If you have iTunes 11 turn on the Sidebar. Go to iTunes>View and click on Show Sidebar. You can also do a Crtl+S to show the sidebar. The sidebar is where Devices appears. and Control+B to show the Menu bar
If necessary:
iOS: Device not recognized in iTunes for Windows
or
iOS: Device not recognized in iTunes for Mac OS X

How do I transfer my account To my new ipad?

I have a new Mini/Retina that I want to replace my iPad 2 with. I want to use my same old AT&T account for cellular/data connection, so how do I transfer my account To my new iPad?
The guy at the AT&T store (where I bought the Mini) said I would have to start it as a backup from the old machine, and I might have to switch SIM cards (believable), but there must be more to it than that. At what point shoud I shut off the old iPad account? If I do it at the wrong time it seems like there should be a conflict (perhaps the SIM card). Is there a procedure posted anywhere? (He also gave me a 1-800 number to call for help - so I suspect I'll need it. But you guys are so good, I'll start here.)
TIA

If your iPad 2 has a newer iOS version than your new iPad Air then you'll need to update the iPad Air to newest iOS before you can restore it from the iPad 2's backup. Its conceivable that being in the store the new iPad air does not have the most recent iOS installed.
Anyway as to the AT&T service. you should not have to anything on the old iPad.
Simply remove the sim card, go to your AT&T store and ask for a new sim that fits your new iPad with your current service on it. Then simply insert the new sim card into the new iPad. In the process of setting up the new sim card, the old one will be deactivated by AT&T.
Without a sim card the old iPad will have no cell service.

How do i transfer old account to new desk top

how do i transfer old account to new desk top

Welcome to the Apple Community.
The following article(s) may help you.
Moving your iTunes library to a new computer

Account-based COPA and having Cost Center as Real Object in Sales Order

Hi,
We have recently activated account-based COPA and in our SO, we realized the Profitability Segment being populated- that is not a problem in normal scenarios.
However, in some cases, we would like to charge to a cost center instead of COPA. We have tried the 2 ways mentioned in the forum/on the web to include Cost Center in Sales Order:
1. Go to OVF3 t-code and configure a default cost center for the order reason
2. Change the SD Document Category under 'Define Sales Document Types' to 'I- Order w/o charge'.
However both ways only open the Cost center field but still populates the COPA. At accounting entries, cost center will become a statistical object and COPA, the real object- which is not what we want.
Is there a way to stop the auto-populating of Profitabiltiy Segment in SO when cost center is being entered?
Thanks very much in advance for any suggestions.
Regards,
Huimin

Solved by myself, with help of OSS Note: 44381 - Profitability Segment Not Required in SD Postings. Have a CO substitution rule to clear away the Profitability Segment number based on certain conditions. Thanks!

Activating Account based Copa in the existing Cost-based COPA

Hi Sap CO gurus!
Please advise me for the following issue.
Presently, My client using Cost-based COPA for segment wise reporting.( Already activated).
Now they wanted the reports in Account Based. Is it possible to activate the Account based now? Will the system allow us to activate or not?
If yes, What will be the implications? I want to know the pros and cons for that.
If not, How Can I edit the COPA settings( Operating concern)? Or shall I delete the Operating concern and create one new one?
Can you please explain the impact of each situation?
Thanks a lot in advance
Rama

Hi Joe
You can deactivate Account Based COPA, but you will have to do a thorough testing so that you are aware of the issues that can crop up
The IMG Menu is SPRO > Controlling > Prof Analysis
You will have to do a testing of how the open sales orders would behave... The open sales orders mean Sales Orders where PGI has been done, but billing is pending AS WELL AS Sales orders which are just created, but no Logistics movement (PGI) has taken place... You will have to do testing on both types of sales orders
- When you do PGI after deactivating the account based COPA, you may face error. Because, COGS GL account is a cost element in Account based COPA, where as in Costing based COPA, it is usually not a Cost Element
- Also do a billing from an open sales order and see if you get any error there...
Similar issue can arise during variance settlement also, because the variance account is not a cost ele in Costing Based COPA.
Test out the above scenarios and do share your experiences
Regards
Ajay M

Account Based COPA Cost of goods sold and Revenue Split

Dear Experts,
We are using account based copa in a automobile company.
As per the requirement when a car is sold, depending on the customer request the car goes for a conversion. like adding Radio, Seat cover, etc
As per our setup we have different profit centers for vehicle and Parts(radio, seat cover etc) and in this case radio, seat cover, etc are the classes of the material vehicle(not separate material).
After the vehicle conversion there is a sales order raised which goes to profit center derived from vehicle material master.
As per the reporting requirement I need to spit the Cost of good sold and revenue by vehicle profit center and parts profit center for COPA reporting purpose
Is there any way to do this in standard SAP? Or I need an exit?
Appreciate your response and please let me know in case of any clarification.
Many thanks
Roy
Edited by: roy001 on Aug 4, 2011 4:52 PM

For those who may need an answer to this, our solution was the following:
1)       Created new types for SO, SO Item, Sched. Line, Delivery, Delivery Item, Billing type
2)       Created new Pricing procedure
3)       Created new movement type Y61/Y62 modeled after 601/602
4)       Mapped Y61/Y62 to account modifier ZAX.
5)       Mapped GBB/ZAX to the new account.
Benefits, they now have better view of the orders going inter-company. It is flexible enough to adjusting prices for intercompany separate from standard orders, even though for now it is a straight copy of cost. They are able to remove the sales/use tax, from the calculations. They are able to plan with these orders separated out. Plus, this will standardize their process for inter-company.
Hope this helps someone.
Cheers!
Rick

What is the purpose of account based COPA when we have FSVs

Hi,
I noted the information we can get from account based copa is exactly the same as the information we can get from financial statement version reports. As such why do we need account based copa for?
What info i can get in account based copa that i cannot get from FSV reports?
help.sap.com

Hi,
   Information gets passed to account based COPA if the relevant G/L account is a cost element.
   However account based COPA uses PA segments. This information contained in the PA segment can be viewed via KE24
   To test this post a billing document using account based COPA. After that go to KE24 for account based COPA and check the report. You will see all the details which would not be available in any FI report. Basically the information available for reporting makes it worth using for account based COPA
regards
Waman

COST ELEMENTS IN ACCOUNT BASED COPA

Hi all,
1. I understand that all FI/GL accounts correspond to COST   ELEMENTS in COPA.
2. I also understand that there are NO value fields in an Account Based Profitability Analysis.So there is no VALUE FIELD to KEY FIGURE mapping.
3. My question is: how do we map each individual GL account into BI?
4. If we dont map each individual GL account, how do we report these accounts in BI?
This part of Account based has been very confusing. I have searched numerous posts, but they all have the same answers, none that explains how we handle the numeric fields of account based profitability analysis.
Cheers
TJ

You will have a KF lets say amount
In account based COPA your Cost and revenue elements will identify what does the value in this KF corresponds to.
your report will look something like below:
Ex:
Cost and Revenue Element #     Amount
800 - Revenues                     1,000,000
808 - Sales deductions             100,000
800 - 808 = Net Revenue            900,000
893 - Cost of Sales               90,000
231 - Price Difference              10,000
Total                               1,000,000
You may get amount from source system in 2-3 diff currencies like controlling area curr, transaction curr...
Sometimes range of accounts correspond to a value. Ex: Accounts 800-900 resemble revenue.
In such a case you may create Text node in hierarchy called revenue and use it in report (if no hierarchy available from the source system) or create selection in the report.,

Account based COPA datsource taking long time to extract data

Hi
We have created a Account based COPA datasource but it is not extracting data in RSA3 even though the underlying tables have data in it.
If the COPA datasource is created using fields only from CE4 (segment ) and not CE1 (line items ) table then it extracts data but tat too after very long time.
If the COPA datasource is created using fields from CE4 (segment ) and CE1 (line items ) table then it does not extarct any records and RSA3 gives a time out error..
Also job scheduled from BW side for extracting data goes on for days but does not fetch any data and neither gives any error.
The COPA tables have huge amount of data and so performance could be a issue. But we have also created the indexes on them. Still it is not helping.
Please suggest a solution to this...
Thanks
Gaurav

Hi Gaurav
Check this note 392635 ,,might be usefull
Regards
Jagadish
Symptom
The process of selecting the data source (line item, totals table or summarization level) by the extractor is unclear.
More Terms
Extraction, CO-PA, CE3XXXX, CE1XXXX, CE2XXXX, costing-based, account-based,profitability analysis, reporting, BW reporting, extractor, plug-in, COEP,performance, upload, delta method, full update, CO-PAextractor, read, datasource, summarization level, init, DeltaInit, Delta Init Cause and Prerequisites
At the time of the data request from BW, the extractor determines the data source that should be read. In this case, the data source to be used depends on the update mode (full initialization of the deltamethod or delta update), and on the definition of the DataSources (line item characteristics (except for REC_WAERS FIELD) or calculated key figures) and the existing summarization levels.
Solution
The extractor always tries to select the most favorable source, that is,the one with the lowest dataset. The following restrictions apply:
o Only the 'Full' update mode from summarization levels is
supported during extraction from the account-based profitability
analysis up to and including Release PI2001.1. Therefore, you can
only everload individual periods for a controlling area. You can
also use the delta method as of Release PI2001.2. However, the
delta process is only possible as of Release 4.0. The delta method
must still be initialized from a summarization level. The following
delta updates then read line items. In the InfoPackage, you must
continue to select the controlling area as a mandatory field. You
then no longer need to make a selection on individual periods.
However, the period remains a mandatory field for the selection. If
you do not want this, you can proceed as described in note 546238.
o To enable reading from a summarization level, all characteristics
that are to be extracted with the DataSource must also be contained
in this level (entry * in the KEDV maintenance transaction). In
addition, the summarization level must have status 'ACTIVE' (this
also applies to the search function in the maintenance transaction
for CO-PA data sources, KEB0).
o For DataSources of the costing-based profitability analysis,
30.03.2009 Page 2 of 3
SAP Note 392635 - Information: Sources with BW extraction from the CO-PA
data can only be read from a summarization level if no other
characteristics of the line item were selected (the exception here
is the 'record currency' (REC_WAERS) field, which is always
selected).
o An extraction from the object level, that is, from the combination
of tables CE3XXXX/CE4XXXX ('XXXX' is the name of the result area),
is only performed for full updates if (as with summarization
levels) no line item characteristics were selected. During the
initialization of the delta method this is very difficult to do
because of the requirements for a consistent dataset (see below).
o During initialization of the delta method and subsequent delta
update, the data needs to be read up to a defined time. There are
two possible sources for the initialization of the delta method:
- Summarization levels manage the time of the last update/data
reconstruction. If no line item characteristics were selected
and if a suitable, active summarization level (see above)
exists, the DataSource 'inherits' the time information of the
summarization level. However, time information can only be
'inherited' for the delta method of the old logic (time stamp
administration in the profitability analysis). As of PlugIn
Release PI2004.1 (Release 4.0 and higher), a new logic is
available for the delta process (generic delta). For
DataSources with the new logic (converted DataSources or
DataSources recreated as of Plug-In Release PI2004.1), the line
items that appear between the time stamp of the summarization
level and the current time minus the security delta (usually 30
minutes) are also read after the suitable summarization level
is read. The current time minus the security delta is set as
the time stamp.
- The system reads line items If it cannot read from a
summarization level. Since data can continue to be updated
during the extraction, the object level is not a suitable
source because other updates can be made on profitability
segments that were already updated. The system would have to
recalculate these values by reading of line items, which would
result in a considerable extension of the extraction time.
In the case of delta updates, the system always reads from line
items.
o During extraction from line items, the CE4XXXX object table is read
as an additional table for the initialization of the delta method
and full update so that possible realignments can be taken into
account. In principle, the CE4XXXX object table is not read for
delta updates. If a realignment is performed in the OLTP, no
further delta updates are possible as they would make the data
inconsistent between OLTP and BW. In this case, a new
initialization of the delta method is required.
o When the system reads data from the line items, make sure that the
30.03.2009 Page 3 of 3
SAP Note 392635 - Information: Sources with BW extraction from the CO-PA
indexes from note 210219 for both the CE1XXXX (actual data) and
CE2XXXX (planning data) line item tables have been created.
Otherwise, you may encounter long-running selections. For
archiving, appropriate indexes are delivered in the dictionary as
of Release 4.5. These indexes are delivered with the SAP standard
system but still have to be created on the database.

KE24 - no line items in account-based COPA

Hello,
I am trying to configure Account-based COPA. I did all the configuration and create a report with a form assigned. The account I have posted is a revenue cost element and has profitability segment as an optional field and is updated with segment data.
Since account-based COPA updates only COEP and CE4XXXX tables I am able to see the record being updated in these tables. But when I run KE24 and COPA report both of them yield no results.
Please see attached for the detailed configuration and copa report set up.
Note: I replicated the exact same scenario in another system with same config and also using the same accounts I was able to generate the KE24 and also COPA report. The only difference between these two systems being the database. System where COPA is working is on SQL DB and where it is not is on HANA DB.

Pablo,
My issue was because of HANA Database. So I had run a report called RKE_HDB_EXTEND_COEX which extends the COEP/COEJ tables into HDB. After running this the issue was resolved.
Not sure if you have the same cause. Let me know.
Thanks,
Raj

Account based copa does not tie with GL

Hello All,
I have created a report in acccount based copa that shows me the balance of a GL account (XYZ). However, the balance only pertains to postings that have associated profitability segments entered (table CE4XXXX). However, the purpose of account based COPA is to tie FI GL accounts to COPA. Postings that do not have associated profitability segments do not appear in the profitability report, hence the balance of account in FBL3N and the copa report do not match up..this defeats the purpose of employing account based copa that permanently reconciles FI with COPA.
Ofcourse, there are instances where a profitability segment is not required or cannot be generated but it should show up on the report in order for a user to see FI and COPA balances matching (COEP table is getting updated with the currency value even if a profitability segment is not generated).
I need to see the total balance of the GL account in COPA divided in the following way:
Sales                                                                                YYYY
Cost of Good Sold (Cost element XYZ-assigned to Psg)                   YYYY
Cost of Good Sold (Cost element XYZ-not assigned to Psg)              YYYY

You should change your field status in FI to require the proper COPA segment when posting an FI document. In account based no postings should be made to COPA without it.
pls assign points to say thanks.

Transfer Subcontracting Accounts to COPA

Similar Messages

Maybe you are looking for