ConditionTo Execute Account Based Calculation ABC

Hi Experts,
We would like to run logic using ABC only when a certain condition is met.  For example, perform an account
adjustment when Account X >0. 
We added the following script to the script logic to execute the ABC.  However, this logic is limited to MS.  Is there an equivalent NetWeaver logic that does the same?
2)  Instead of this logic can
you guys suggest another way to condition the ABC?
Note we used the RUN_PROGRAM CALC_ACCOUNT statement works for us without using conditions.
We are aware of the following conditional syntax but does it work with RUN_PROGRAM CALC ACCOUNT?
REC(EXPRESSION=([ACCOUNT].[116000_R],[AUDITID].[AD3100]) >0 ?
-([ACCOUNT].[216000],[AUDITID].[AD3100]):([ACCOUNT].[116000],[AUDITID].[AD3100]),ACCOUNT="216110",AUDITID="AD3055")
Script added:
*WHEN CUENTA
    *IS
59IM90000
      *WHEN
GET(CUENTA="59IM90000()
      *IS
> 0
Initial script to execute the ABC:
*RUN_PROGRAM CALC_ACCOUNT
  CATEGORY = ACTUAL
  CURRENCY = LC,USD
  TID_RA = %TIME_SET%
  OTHER = [ENTITY = %ENTITY_SET%]
  OTHER=[ENTITY=%ENTITY_SET%;INTERCO=%INTERCO_SET%;BANK=%BANK_SET%;TC=%TC_SET%;COST_CENTER=%COST_CENTER_SET%;ACTIVITY=%ACTIVITY_SET%;SUBGLOBALRGN=%SUBGLOBALRGN_SET%;ACTIVE_INGREDIEN=%ACTIVE_INGREDIEN_SET%;COUNTRY=%COUNTRY_SET%]
CALC=7_115_GREAT
  *ENDRUN_PROGRAM
Thanks in advance.
Eyal Feiler

Hi
Vadim,
Thanks for your response.
Here is a fuller explanation of what we are doing.
We compare a set of asset accounts vs. liabilities in this case deferred assets vs. deferred liabilities. In
case A -> assets are < liabilities 3600 vs. -4560 (net -960).
Expected result we will use ABC logic DEF_ASSETS_LESS and reclass from an asset account -3600 and book to the liabilities 3600.
The result will be -960 on the liabilities side and 0 on assets.
The activity will be booked in a different datasource (AuditID in our model).
In case B assets > liabilities.  Use ABC logic ABC logic DEF_ASSETS_MORE 5000 vs. -4560 = 440 net.
Book
4560 to a liability offset account and 4560 to an asset.  
Result
is 440 in the assets. 0 liabilities.
col
column AD3100 shows results before reclassification.  Column AD3057 shows the adjustment taking the sum of the liabilities and shifting to assets.
ABC is effective because we can select multiple base members of data sources and the change affects all rows for the matching accounts with the various dimensions e.g. country, bank etc.
The problem is to use the condition, so that we can decide automatically whether to apply either logic.
The issue we had with the script you suggested earlier is that we could not select
multiple base member dimensions for data source and others (see thread - http://scn.sap.com/thread/3487307).
Any ideas as to script logic or ABC?
We want to stay with script logic.  Else we may need to go to ABAP.
Thanks
Eyal

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

  • Costing Based And Account based COPA - Need Assistance

    Hello All,
    In our project, with no other option we are planning to implement both costing based and account based COPA. I have been told that it is not recommended by SAP because for every entry there will two line items, one in cost based and another in account based (Correct me if I am wrong). But I could not understand why it is creating 2 line items in COPA. - Please help to understand this concept with an Example.
    Thanks
    PM

    Hi
    Costing based and account based COPA serve the same purpose...   analyze profitability of the product ....
    Costing based COPA should always be preferred over account based COPA, as it provides greater flexibility, some extra features, some extra planning mechanism and faster reports
    Following  are the point of differences between Costing based vs. Account based copa (ABC)
    1. Account based copa uses transaction tables (COEP, BSEG) and hence affects performance of CO transactions.CBC takes values from CE1XXXX to CE4XXXX tables. XXXX means Operating Concern name.
    2. Estimated / Statistical values not possible in ABC, say, calculating frieght upon invoice on a thumb rule basis to have better view of profitability per customer.. no valuation strategy in Accounts based COPA..
    3. Reports based on line items not possible in ABC.. possible in CBC.
    4 Actual Top Down distribution only available in CBC not in ABC .
    5. Revaluation of actual data to plan data is not available in ABC
    6. No key figure schemes are available in ABC
    7. In ABC, settlement cost elements are used to settle values to prof segments unlike value fields in CBC
    8. Production variance / COGS accounts shud be defined as cost element in ABC.
    System creates a document for each type of COPA as it stores values in different tables and what you can do with this data also differs like you can do TOP down in Costing Based Copa..
    Hence, you will have two COPA documents always......................
    Fot further clarifications .. please revert back..
    Regards
    Sarada

  • Differance between the Cost based costing and Account based costing

    Hi,
    What is the Differance between the Cost Based Costing and Account Based Costing ?

    You can check sap note 69384
    COSTING-BASED PROFITABILITY ACCOUNT-BASED PROFITABILITY
    ANALYSIS ANALYSIS
    OBJECTIVE
    o profitability and sales accounting
    o evaluation of market segments (for example,
    customers, product groups, sales areas) and corporate
    units (for example, division, sales organization) with
    regard to their profit or contribution margins
    o calculation of profits procedures
    - cost-of-sales accounting
    - interim and reconciled sales report
    - periodic and transaction-based allocation
    - Profitability Analysis on the basis of full and
    direct costs
    o posted and costing-based values o account-based values
    o can be reconciled with FI for o always reconciled with
    account groups (revenues, sales FI on account level
    deductions, costs of goods
    Note 69384 - Information: Account-based Profitability Analysis
    manufactured, and so on)
    DATA STRUCTURES
    o definition of operating concerns o definition of operating
    with fixed characteristics and concerns with fixed and useruser-
    defined characteristics defined characteristics
    and value fields
    o cumulative storage by posting o cumulative storage by
    periods and weeks posting periods
    o storage in operating concern o controlling area currency,
    currency (as of Release 4.0 also company code currency
    optional in company code currency and transaction currency
    if req.)
    o user-definable summarization levels
    FUNCTIONS
    o transfer of profit relevant o transfer of profit-relevant
    business transactions from SD, FI activities from SD, FI, CO, MM
    CO, MM (revenues, sales deductions (revenues, sales deductions and
    and costs organized by value fields) costs organized by accounts)
    o Derivation of characteristics from master
    data or using derivation rules
    o Realignments also for data that is already
    posted
    o Valuation
    (Costs of goods manufactured, imputed
    costs and sales deductions)
    o sales and profit planning o profit planning
    - flexible layout - flexible layout
    - periodic distribution - periodic distribution
    - valuation, revaluation - forecast procedure
    - forecast procedure - top-down distribution
    - top-down distribution - simulation
    - simulation
    o profit analysis by means of 'interactive drill-down
    reporting'
    - Report Painter
    - object list/ranking lists, database schema
    - drill-down
    - key figure systems
    - flexible hierarchies
    - navigation between reports
    - exception reporting
    - ABC analyses
    - Exporting (Excel, Winword, Mail)

  • G/L account interest calculation

    Hello Experts,
    I have an issue with F.52 interest calculation; we have calculating interest for the period 01.07.2011 to 31.07.2011. However, calculation went fine for all G/L account except two G/L account which has calculating interest for earlier periods also.
    We analyze the issue and found out a one possibility, because of field u201CDate of Last Interest Runu201D however this field applies only when there is posting to G/L account with earlier date for which interest already been calculated. I have seen the documents which were wrongly picked in the interest run, and entry date is in earlier monthly only.
    I do not understand why these two G/L accounts is picking the documents in the earlier periods to calculate the interest for the period 01.07.2011 to 31.07.2011.
    Thanks in advance.
    Regards,
    MM

    Hello Mauri,
    Thank you very much for your reply.
    First of all we are not using the G/L updation through this program.
    I have an issue with only for the period 01.07.2011 and 31.07.2011 for two G/L account, and calculation is asolutely fine for all the earlier periods and even for next period 01.08.2011 ot 31.08.2011.
    As per my understanding u201CDate of Last Interest Runu201D, applies only when there is posting to the G/L account with earlier date for which interest already been calculated.
    If I keep the Date of Last Interest Run field blank, it calculate interest only for the period 01.01.2011 to 31.07.2011, however I can.t propose this solution because in all earlier periods they executed F.52 transaction with similar input parameter and calculation is absolutely fine.
    Please let me know your view.
    Regards,
    MM

  • Out of memory Error while querying SQL Script based Calculation View

    Hi All,
    I wanted to test the performance of Graphical and SQL Script based Calculation views.
    Created Graphical (CA_GRPH) and SQL Script (CA_SQL) Calculation views.
    Analytic View (AN_GRPH) for both Calculation views are the same which is Graphical based (90 Attributes and 5 Measures)
    In Analytic View data foundation I have a Fact table which has 1.5 Billion records and 9 Dimension Tables –collectively 500 million records (7 Attribute Views). 9 Referential joins with cardinality N:1 and 1 Referential join with cardinality N:N.
    I wanted to keep (CA_GRPH) and (CA_SQL) as a base Calculation views and leverage those to create various calculation views (Will be creating different Calc views for respective Business segments)
    In order to test this I have created below calc views on top of base calc views.
    Graphical Based: Created (CA_GRAPH_XYZ) by having CA_GRPH in projection with 30 Calculated Columns. – This retrieves data in 13 secs
    SQL Script Based: Created (CA_GRPH_ABC) by having CA_SQL in projection view with 30 calculated columns – This errors out after 1.50 mins.
    Could not execute 'SELECT "COLUMN_A","COLUMN _B"," COLUMN _C"," COLUMN _D", SUM("COLUMN _REVENUE") AS ...' in 1:50.480 minutes .
    SAP DBTech JDBC: [2048]: column store error:  [2048] column store error: search table error: [1000002] Error executing physical plan: exception 1000002:
    ltt/impl/memory.cpp:63
    Out of memory ; $size$=1507711; $name$=ihm; $type$=pool; $inuse_count$=170104; $allocated_size$=219215007925
    exception 1000002:
    Any suggestion / help in fixing this issue will be greatly appreciated.
    Regards,
    Av

    Hi Raj,
    Thanks for your time, please find edited snap hot of Analytic View (AN_GRPH) below,
    Calculation view(CA_SQL)
            /********* Begin Procedure Script ************/
    BEGIN
           var_out =
         SELECT
                "COLUMN_1"
                "COLUMN_2",
                "COLUMN_84",
                "COLUMN_85;",
                SUM("REVN") AS "REVN",
                SUM("MGN") AS "MGN",
                SUM("ORD_QTY") AS "ORD_QTY",
                SUM("SYS_QTY1") AS "SYS_QTY1",
                SUM("SYS_QTY") AS "SYS_QTY"
    FROM
          "_SYS_BIC"."XYZ/AN_GRPH"
    GROUP BY
                "COLUMN_1"
                "COLUMN_2",
                "COLUMN_84",
                "COLUMN_85";
    END
    /********* End Procedure Script ************/
    Later i have built one more Calculation view(CA_GRPH_ABC) using (CA_SQL)in projection. i have 30 calculated measures in this final calc view. this final calc view is throwing above mentioned error.
    Not sure if i can use SQL script based calc view in graphical based calc views?
    Regards,
    AV

  • 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

  • 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.

  • PA - Costing-Based and Account-Based

    Hi All,
    Please tell me what is Costing based PA and Account-based PA.
    Thanks
    Vinu

    Hi,
    Costing-Based Profitability Analysis
    This type of Profitability Analysis is primarily designed to let you analyze profit quickly for the purpose of sales management. Its main features are, firstly, the use of value fields to group cost and revenue elements, and, secondly, automatic calculation of anticipated or accrual data (valuation). The advantage of this method is that data is always up‑to‑date and therefore provides an effective instrument for controlling sales.
    Account-Based Profitability Analysis
    This type of Profitability Analysis enables you to reconcile cost and financial accounting at any time using accounts. In contrast to costing‑based Profitability Analysis, this type uses cost and revenue elements, which gives you a unified structure for all of accounting.
    The system posts all revenues and costs to both Financial Accounting and Profitability Analysis at the same time and using the same valuation method. This means that the cost of sales is posted to Profitability Analysis at the point of goods issue.
    Regards,
    Eli

  • FI Bank Account Interest Calculation

    How to customize compound interest calculation on bank accounts in the Bank Account Interest Calculation?

    Hi,
    The process for configuring the system to calculate Interest on bank account is as follows:-
    1.Define reference Int Rates
    2.Enter Interest Values
    3.Prepare GL account balance interest calculation for interest posting
    Then you execute F.52 for calculating the interest by providing the required parameters
    Regards
    Phani

  • Please tell me a BAPI to get Closing balance of customer account based on Sales Organization?

    Hi Experts,
    A requirement has come up where I want to get Customer closing balance based on its sales organization as this particular customer is extented to 2 different sales organizations. I want to get the closing balance of individual sales organization vise.
    Please tell me a BAPI to get Closing balance of customer account based on Sales Organization?

    AFAIK there is no such BAPI, cause there is no database table with balance for customer per sales organisation. (No KNCx table for VKORG)
    First ask functionals (*) how to recover sales organisation from a FI document (I suppose for SD invoice it is easy if no merging between organisation) will be a little tricker for pure FI document like payment transactions (hope thet are quickly cleared...)  Then start from non cleared records of BSID (also BSAD if you use a past date of reference, in case you have to add the records of BSAD with clearing date greater than reference date) and cross it with SD information to break FI into sales organisation.
    Regards,
    Raymond
    (*) Ask for where do they store VKORG in FI documents

  • Posting to different GR/IR account based on purchase order type

    We are implementing cross company stock transport orders that require an AP invoice to be posted against the goods receipt.  Our AP department does not want the GR/IR postings to go to the account used for traded AP.  I cannot determine a method using OBYC to specify a different account based on purchase order type.  Is there a way to do this?

    Hi Jud
    You should make these posting to a cost center then..The only way you can control account postings via PO type is having a account assignement category. You can make this as mandatory filed for this PO type..
    Please let me know if your requirement is different..
    CHeers
    R K Bolla

  • 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

  • CO-PA Account Based enhancement : BELNR-CO

    Hi all,
    I have successfully implemented a CO-PA ETL for both Costing and account based CO-PA in my system.
    I enhanced the costing based Extraction with no major concern.
    However I now wish to enhance the CO-PA Accoutn BAsed, and here I struggle , because I cannot get the controlling document number - part of COEP key - in my extract.
    I need to use this controlling document number in order to conduct some logic in the extraction, but the creation of the account based datasoource in KEB0 does not provide the option to have this field as part of the extract structure ( as a sidenote, it will not be defined in KEQ3 either, as the granularity of the profitability segment would then be to fine)
    ... Any idea on how to collect the CO doc number in this scenario? I am missing something...
    I would very much appreciate some insight from experienced CO-PA - BW community members !
    Cheers
    Patrick

    Patrick,
    The link between COSP / COSS and CE4xxxx is the objnr of the tables COSP / COSS. The first 2 positions = 'EO'. The following positions, the name of the results area and rest of the objnr relates to the PAOBJNR of table CE4xxx. In the table CE4xxxx the field KNT_FRM_KZ = '1'. This means account based CO-PA object.
    For the standard extraction process you don't need to build things between these tables. The extractor knows the relationships already.
    Regards,
    Peter

Maybe you are looking for

  • Problem with Lenovo 3000 N200 0769 Laptop

    Hi all, I'm new here and hope someone can tell me whats wrong with my Lenovo 3000 N200 0769. Two days ago I got up in the morning and turned on my laptop, it started and shut off about 3 seconds later. It does it every time I try to start. I was able

  • Doubt regarding automatic statistics collection in Oracle 10g

    I am using Oracle 10g in Linux Does statistic collection for tables throughout the database happen automatically or should we manually analyze the tables using Analyze command or DBMS_STATS package ? AWR collects statistics(snapshots) every 1 hr but

  • Java/lang/NoClassDefFoundError: java/lang/Object

    Hi Experts, We are installing Java "1.6.0_31.We have updated the environment variables with the correct Java Path but which checking the java -version we are getting the following error. java -version Error occurred during initialization of VM java/l

  • Wireless issues when plugging into Mac display

    I have noticed that no matter where I am in the house, my Macbook Pro works with my Airport just fine. But when I plug the laptop into a 24" display, my wireless signal does one of two things: it drops a connection, going from full strength to nothin

  • Global Temp Tables in a Stored Proc

    Hi All, I'm trying to create a procedure that creates some tables and then creates global temporoay tables. This runs fine in a scrupt but when I place it in a proc, it fails with the following error Error(172,10): PLS-00103: Encountered the symbol "