SEM-BCS Version configurations

Dear Gurus:
I have the following scenario:
one parent company with 2 sub groups one on GAAP and another on AUS accounting technique.
a) I am creating 3 versions 1 for GAAP 1 AUS and 1 for consolidated parent group.
Is it the right way to do it?
b) Interunit elimination executed on Version1 for US Group cos Version 2 for Aus group cos and 3 for both US and AUS cos.
c) Can the client change the COI method - Purchase and Equity as and when they need? Is there any regulation restricting method changes?
Please respond at your earliest.
Thanks in advance.
Sri
Edited by: Bansidar Gunnia on Mar 30, 2008 9:07 PM

It may not be necessary for 3 versions depending on the differences between the requirements for each.
By GAAP to you mean USA Generally Accepted Accounting Principles (GAAP)? By AUS do you mean Australian GAAP?
If 3 versions is the solution, then eliminations should be executed for each version. In this case it may be better to have 3 cons group hierarchies as well. One hierarchy for GAAP, one for AUS, and another that combines GAAP and AUS. The monitor may be assigned the hierarchy according to the version requirements.
Changing accounting method between Purchase and Equity is simple, but there are GAAP guidelines for each. The GAAP depends on the country for which the reports are prepared.

Similar Messages

  • Doubts on implementation of SEM BCS in version 6.0

    Someone possessing the implementation model of SEM BCS in version 6.0?
    tks regards

    <div class="jive-quote">which notes to be applied initially</div>
    - OSS notes are used just to correct some errors found in the system. The system may have a  different core (SAP R/3, ERP, ECC etc), patch levels, service packages installed, components installed, their release/versions, EhP functionality (if any) and so on. Everything is very individual. 
    <div class="jive-quote">which is not setting standarts</div>
    <div class="jive-quote">if there is an implementation model step by step</div>
    - None that i'm aware of.

  • SEM-BCS configuration

    Hi Gurus,
    I am in the process of implementing SEM-BCS consolidation based on BW. I don't know where to start and how to start. Anu body can help me to do the necessary configurations

    Hi Latha,
    It is good that you are starting to learn SEM-BCS.  To do that you need to have the knowledge of Business Process.  Since you are FI certified understanding of Business Process should not be a problem.
    Add to this, it would be better to have knowledge also in BW.  As SEM-BCS is an application the storage of Data will be in BW and also the reporting.
    SAP provides enough documentation, at http://help.sap.com but initially you might not understand everthing at one shot.  Keep trying.
    Best of Luck.
    Regards
    Narayana Murty

  • SEM-BCS without carry forward

    Hi all,
    Has someone configured SEM-BCS without the carry forward task.
    And can you share the pros and cons of doing this?
    Thanks, Alvin

    Thanks Greg, Dan, Thibaud for your responses. he are very much appreciated.
    I wanted to attract some debate/discussion on the matter. Personally, I am not convinced that carry forward is not used.
    However a bit more context. My client is using SAP PBF and PBF can pass on Opening balances to BCS.  BTW this relates to budgets more than actuals.
    There are the usual related party eliminations and possibly consolidation of investments so that BCS can deal with them in a variety of reporting hierarchies.
    Other requirements include
    - budget may be increased/decreased 2-3 times a year
    - these increases/decreases are captured as adjustments for the relevant period. This changed budget (sometimes for the same fiscal year) is the authority for spending
    - there are 4 years of estimates (say Est1, Est2, Est3, Est4 representing each future year) and they do not roll on to each other.  In other words, Est1 do not roll into est 2 and est 2 do not roll into est 3 and so on.  Rather est 1 roll into est 1, est2 into est 2, either in the same fiscal year or the next fiscal year (it sounds confusing hence I hesitated to put that with my initial question)
    So far, based on other conversations, I have gathered the following:
    - Not generally done in BCS where opening balances are required
    - Documents posted in the previous year will not inverse
    - Consolidation adjustments relating to previous years will have to be re-posted in current period. Flexibility to report these adjustments for a particular period will be lost.
    - Additional items/subitems will be required for opening balances, as compared to opening balances captured in period 00,
    - Many BEx reports (probably some reclasses and allocations) that are looking for the beginning balances in the period 000 will start malfunctioning.
    - Copy Tasks (this will used for different consolidation versions) may end up with incorrect data if they require previous period results
    - Not being able to close book for the year?
    Anymore input would be appreciated.
    Cheers, A

  • Implementation of SEM-BCS

    Hi Experts,
    i am trying to implement SEM-BCS. I am still new in it. Are there any documentation about step by step to configure SEM-BCS?
    Thanks a lot for your help.

    Hi,
    https://www.sdn.sap.com/irj/sdn/advancedsearch?query=bw-bcs&cat=sdn_all
    Basics of BCS modelling -
    Key figures -
    You are generally not permitted to change any properties of the key figures used in SEM-BCS. The only exceptions to this are options that affect the display in Business Explorer and the "Characteristic is document property" setting.
    If you want to use your own InfoObjects as key figures for totals records in the InfoCube, consider the following conditions:
    1. SEM-BCS supports four roles for key figures in the data stream for totals records: Value in group currency, value in local currency, in transaction currency and quantity. You can assign a maximum of four key figures in the data basis accordingly. If you include additional key figures in the InfoCube, these cannot be processed in the consolidation. You are not permitted to assign other roles, such as 'subassignment,' to key figures either.
    2. In SEM-BCS, the values are always stored periodically in the database. Furthermore, year-to-date values or non-cumulative values are not managed separately but result from cumulation in each case over the periods of the current fiscal year up to the current period. (This is a purely technical restriction. The consolidation functions greatly support the process with year-to-date values.) Therefore, you must define InfoObjects as cumulative values. Proceed according to the 0CS_TRN_GC, 0CS_TRN_LC, 0CS_TRN_TC, 0QUANTITY InfoObjects that are delivered.
    3. You cannot use referencing key figures in SEM-BCS. If you want to define a key figure with a reference, to transfer the technical properties of the referenced InfoObject identically, you can simply create this with a template instead. However, if you want to use the special BW function linked with referencing key figures (see the online documentation in the BW), enter the referencing key figures in the InfoCube, but assign the referenced key figures to the data basis.
    Characteristics
    With the following characteristics, you are not permitted to make changes to the properties. Once again, the only exceptions here are the options that affect the display in Business Explorer:
    0AC_DOCLN, 0AC_DOCNR, 0AC_DOCTEXT, 0AC_IVDOCNR, 0AC_IVPER, 0AC_IVYEAR, 0AC_OIDOCNR, 0AC_OIPER, 0AC_OIYEAR, 0AC_ORDOCNR, 0AC_ORPER, 0AC_ORYEAR, 0AC_RVDOCNR, 0AC_RVPER, 0AC_RVYEAR, 0BCS_AREA, 0BCS_AUTODL, 0BCS_BGPER, 0BCS_BGYEAR, 0BCS_COIACT, 0BCS_COIFUT, 0BCS_COIINA, 0BCS_COINRT, 0BCS_COIPGW, 0BCS_COITOA, 0BCS_CTFLG, 0BCS_DPER, 0BCS_DTEQI, 0BCS_GWLC, 0BCS_GWMAN, 0BCS_GWNEG, 0BCS_GWPROC, 0BCS_LCCMU, 0BCS_LCIC, 0BCS_OBJNR1, 0BCS_OBJNR2, 0BCS_OBJNR3, 0BCS_OBJNR4, 0BCS_OBJNR5, 0BCS_OBJNR6, 0BCS_OBJNR7, 0BCS_OBJNR8, 0BCS_ORGCH, 0BCS_ORGCHL, 0BCS_PRGRP, 0BCS_REFPER, 0BCS_REFYR, 0BCS_SEQNM, 0BCS_TASK, 0BCS_TASKGR, 0BCS_TASKTY, 0BCS_TAXSUP, 0CS_COIAC, 0CS_COINR, 0CS_PLEVEL, 0CURRENCY, 0DATE, 0UNIT, 0USERNAME
    Compounding -
    When you define the compounding of an InfoObject, some compound relationships are not supported:
    You cannot compound subassignments to consolidation units.
    You are not permitted to compound the document type and the (0CS_PLEVEL) posting level.
    You cannot compound noncurrent assets and assets/liabilities to 0BCS_ALTYPE. In addition, you cannot compound to a characteristic from the totals cube, with the exception of consolidation units, partners, and so on, and their higher-level characteristics.
    ODS objects / Virtual InfoProvider -
    You can generate the ODS objects for additional financial data and the virtual InfoProvider from the data basis maintenance. However, you can also create these manually and enter them in the data basis. If you do this, create the ODS objects and virtual InfoProvider with the same characteristics and structure they would have had if generated by the data basis maintenance. You can only deviate very slightly from this.
    You are not permitted to include the following InfoObjects in any InfoProvider, unless they are generated by the data basis automatically:
    0BCS_AREA, 0BCS_REFPER, 0BCS_REFYR, 0BCS_TASK, 0BCS_TASKGR, 0BCSTASKTY
    The following InfoObjects must not be contained in the InfoObject catalog, which is defined in the data basis:
    0BCS_AREA, 0BCS_REFPER, 0BCS_REFYR, 0BCS_TASK, 0BCS_TASKGR, 0BCSTASKTY, 0FISCYEAR, 0FISCPER3
    Time characteristics -
    SAP consolidation SEM-BCS ignores changes with the 0FISCPER, 0FISCPER3, 0FISCVARNT and 0FISCYEAR time characteristics. If you make changes, for instance, if you create hierarchies or attributes, these are not taken into account by SEM-BCS. Therefore, there is no maintenance in the workbench, you cannot use the hierarchies or attributes in the functions of SEM-BCS for selections and so on, and you cannot use the attributes or hierarchies for selections in BW queries.
    Characteristic values
    The following InfoObjects may have the values set by default by SAP only . You are not permitted to change them, not even by using the BW master data maintenance:
    0BCS_AREA, 0BCS_AUTODL, 0BCS_COISRT, 0BCS_CTFLG, 0BCS_DIDIEL, 0BCS_GWMEM, 0BCS_GWPROC, 0BCS_IPAAC, 0BCS_IPATTY, 0BCS_OBJNR1, 0BCS_OBJNR2, 0BCS_OBJNR3, 0BCS_OBJNR4, 0BCS_OBJNR5, 0BCS_OBJNR6, 0BCS_OBJNR7, 0BCS_OBJNR8, 0BCS_REPMOD, 0BCS_TASK, 0BCS_TASKGR, 0BCS_TASKTY, 0BCS_TAXSUP, 0BCS_TIMMOD, 0CS_COIAC, 0CS_PLEVEL
    For these InfoObjects you can only use the tools of the master data service of the Financial Basis to synchronize master data, so the master data is transferred by the SEM-BCS tables to the BI tables, but not the other way round.
    Predefined InfoObjects for individual roles
    The system automatically uses most of the InfoObjects mentioned here to activate certain data streams. However, there also are some InfoObjects that you must manually enter in the cube for the totals records. Subsequently, you must assign certain roles to these InfoObjects. These roles are allowed for these InfoObjects only, you cannot assign these roles to other InfoObjects.
    These are:
    0CS_PLEVEL for the posting level role (required)
    0BCS_CTFLG for the conversion role (optional)
    0BCS_PRGRP for the product group role (optional)
    Activate characteristics and key figures from BW Content
    Before you create a data basis of SAP consolidation, you have to activate certain InfoObjects from BW Content.
    1. You must always activate the following: 0CS_PLEVEL, 0FISCPER, 0FISCPER3, 0FISCVARNT, 0FISCYEAR.
    2. If you use documents, you must also activate: 0AC_DOCLN, 0AC_DOCNR, 0AC_DOCTEXT, 0AC_IVDOCNR, 0AC_IVPER, 0AC_IVYEAR, 0AC_OIDOCNR, 0AC_OIPER, 0AC_OIYEAR, 0AC_ORDOCNR, 0AC_ORPER, 0AC_ORYEAR, 0AC_RVDOCNR, 0AC_RVPER, 0AC_RVYEAR
    3. If you use the virtual InfoProvider, activate: 0BCS_REFPER, 0BCS_REFYR, 0BCS_REPMOD, 0BCS_TIMMOD also
    4. If you use any data stream in addition to the totals records, also activate: 0BCS_OBJNR1, 0BCS_OBJNR2, 0BCS_OBJNR3, 0BCS_OBJNR4, 0BCS_OBJNR5, 0BCS_OBJNR6, 0BCS_OBJNR7, 0BCS_OBJNR8
    5. If you use the data streams of the consolidation of investments, activate: 0ACQ_PER, 0ACQ_YEAR, 00BCS_BGPER, 0BCS_BGYEAR, 0BCS_COIACT, 0BCS_COIFUT, 0BCS_COIINA, 0BCS_COINRT, 0BCS_COIPGW, 0BCS_COISRT, 0BCS_COITOA, 0BCS_DPER, 0BCS_DTEQI, 0BCS_GWLC, 0BCS_GWMAN, 0BCS_GWMEM, 0BCS_GWNEG, 0BCS_GWOFFS, 0BCS_GWPROC, 0BCS_GWRED, 0BCS_LCCMU, 0BCS_LCIC, 0BCS_SEQNUM, 0CS_COIAC, 0CS_COINR
    6. If you use organization changes, activate: 0BCS_ORGCH, 0BCS_ORGCHL
    7. If you use data streams for stock and delivery data, activate 0BCS_PRGRP.
    8. If you use data streams for assets/liabilities or noncurrent assets, activate: 0BCS_ALTYPE, 0BCS_DPER, 0BCS_DYEAR, 0BCS_IPADAU, 0BCS_IPALCM, 0BCS_IPATTY, 0BCS_RETBG
    The list of the InfoObjects varies depending on the release. Of course, you do not have to activate InfoObjects that do not exist in your release.
    You do not have to activate InfoObjects that are not explicitly specified. However, if you do not activate them, some functions may not be available to you. For example, if you do not activate the 0BCS_CTFLG InfoObject and do not use it for totals records in the InfoCube, the currency translation cannot display any currency translation differences on the initializing data records.
    Attributes When you define the InfoObjects in BW, attributes can be assigned to InfoObjects. This results in the following restrictions:
    In SEM-BCS 3.1B, 3.2 and 3.5, no InfoObjects that appear in the permanent parameters of a consolidation area or are fixed in a consolidation area may be attributes of an InfoObject used in SEM-BCS.
    InfoObjects that are used as a consolidation unit must not have 0FISCVARNT as an attribute.
    Note 727776 - Requirements of SEM-BCS for data model
    Hope it Helps
    Chetan
    @CP..
    Eugene Khusainov
    Re: BCS - Modelling requirements
    Posted: Feb 24, 2007 10:56 PM in response to: moini kembly Reply E-mail this post
    Hi,
    On this phase you should determine and describe the following:
    - sources of data to be consolidated (R/3, flat files, 3rd parties)
    - methods of receiving/uploading these data into BW
    - the appropriate BW objects (characteristics, key figures, cubes etc.)
    - time characteristics to be used (is it enough to have only fiscal chars? do you need the calendar ones too?)
    - is data upload to be directly into totals cube? if not - consider the intermediate cube. What kind of data transformation is to be done during upload of data from interim cube to the totals?
    - methods of getting data into totals cube (flexible upload, reading from datastream, manual entries)
    - will you need additional financial data? if yes, which ones and how will you load this data?
    - what types of data you need to consolidate (actual, plan, forecast etc.)
    - how many chars will be given the VERSION role?
    - plan the number of consolidation areas. The best way is to have the only one. it will minimize the customization.
    - how many consolidation units hierarchies do you have (for example, if you need consolidated reports according to management and IFRS structure of the group, then you have 2 hierarchies)?
    - determine the structure of the group hierarchies.
    - what is the group's currency? is it one currency or several ones?
    - determine the currency translation methods for each data type.
    - make sure that all consolidation units have the same chart of accounts. if not, consider the mapping or transformation of the numbering of accounts.
    - consider the currency translation types for different groups of accounts in the balanse sheet (for example, fixed assets and equity - historical rate, retairned earnings - everage rate, non-monetary items - current rate etc.).
    - consider the kind of translation - periodic/cumulative for different data types and reports.
    - determine the set of consolidated reports as an output.
    - which custom characteristics you need to bring to the totals cube in order to get the reports needed?
    - which standard chars you'll have to customize and how exactly (bringing new attributes, customizing the std or creating the custom chars)
    - if you'll replace a standard char with a custom one, consider that some another chars may depend on the char to be replaced. it's especially true for a company code. if you use a custom char for a company, then you have to use the reference chars for partner company, investee company, allocation company etc.
    - will your consolidation units be one-dimension structure (by company) or it is a matrix one? if the latter, what is the second cons unit?
    - will the BCS functionality cover all your consolidation needs? if not, consider the workarounds. reclassification is to be considered as a tool # 1.
    It's just an incomplete introduction to the issues to be determined during a blue-print phase.
    Re: BCS in NW2004s
    Re: BCS - Data modelling KF question
    Re: BCS - Virtual Cube Query error
    Re: BCS- data basis
    Re: BCS - Virtual Cube problem
    Re: BCS - Consolidation group data
    check these links...
    http://help.sap.com/saphelp_sem40bw/helpdata/en/67/f7e73ac6e7ec28e10000000a114084/frameset.htm
    Re: Synchronize Master Data between BCS and BW within the same SEM system
    /message/1508507#1508507 [original link is broken]
    http://sap.ittoolbox.com/groups/technical-functional/sap-sem/dataflow-from-r3-to-sem-bcs-950671
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/6e01a04e-0a01-0010-dfbe-951c2c39d169 [original link is broken]
    http://help.sap.com/saphelp_nw2004s/helpdata/en/c4/9057475ca611d4b2e30050dadfb23f/frameset.htm
    Hareesh

  • Multiple Fiscal Year Variant in the same client in SEM-BCS...

    I have already looked at some earlier threads relating to this but didn't get a convincing answer to what I would like to know.
    We have had a working SEM-BCS system with fiscal year variant K4. There was no need for defining leading fiscal year variant and none was defined. SAP, by default takes, K4 as the leading fiscal year variant.
    Now there is a requirement for going on a different fiscal year variant for which we have created another databasis (there were a few other reasons besides these) with the same InfoObjects that we used earlier but with different fixed parameters, one of which is fisc year variant V9. Soon, we started experiencing bizarre dumps in the configuration which ultimately convinced me to define a leading fiscal year variant. I was reluctant to do so because there is a lot of old data (which will become 'historical' from new data basis point of view) from the working system on K4 that would still need to be reported on even when we have new BCS solution in the new fiscal year variant V9. That is not going away. There is a need to keep the old data for reporting (hence the rationale for a different data basis among a few others).
    Since earlier Master Data was configured in the old fisc year variant K4, now I have defined the leading fiscal year variant as V9 so that MDF can appropriately identify the period dependency.
    I would like to know if any of you have had an unexpected behavior from the system going forward. Does the system dump out when you try to read the old data (from earlier K4).
    I have tried to explain the dilemma as clearly and succinctly as possible but if you need more clarifications, please do let me know.
    I would really appreciate your help in this.

    Is your requirement is that K4 to be changed to Z5.
    The best way you can do it is in the transformation. Instead of directmapping,
    Write a code like this in the trransformation to the cube
    If SOURCE FIELD - 0FISCVAR eq 'k4'.
    SOURCE FIELD - 0FISCVAR = 'Z5'.
    I dont think we can change th data in the query being displayed. we can change the keyfigure values in query by frmulas etc...
    but for a characteristic, i think we will be able to restrict bt not change the value.
    to obtain the requirement, w have to get the data change before query designer that is in the cube leve.
    Hope this helps,
    Sri...

  • SEM-BCS Short Dump while executing Manual Posting Task

    Hi SEM-BCS Colleagues,
    I am having a peculiar problem with relation to the settings for Manual Postings. I have three scenarios for which I have defined manual document types and tasks 1) Standardizing Entry (Data Collection) 2) Manual Document in IU for adjustment 3) COI Group level manual postings. I am just creating and not changing any settings for document field properties also. I have configured monthly consolidation frequency and period category and I am posting document type 1 in Local Currency and 2 and 3 in Group Currency since they are after currency translation.
    Have any of you faced similar problem and help me please?

    Hello,
    I am also getting short dump during data collection in BCS.
    we recently upgraded the system to SP20. Is it anyway related to upgrade.
    I also checked the MYSELF as a source system, but not found one.
    Could you please let me know how you have solved this issue.
    short dump:
    Runtime Errors         PERFORM_TOO_MANY_PARAMETERS
    Exception              CX_SY_DYN_CALL_PARAM_NOT_FOUND
    Date and Time          04.12.2009 05:21:11
    Short text
         Too many parameters specified with PERFORM.
    What happened?
         In a subroutine call, there were more parameters than in the
         routine definition.
         Error in the ABAP Application Program
         The current ABAP program "SAPLRSDRI" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_DYN_CALL_PARAM_NOT_FOUND', was
          not caught in
         procedure "RSDRI_CUBE_WRITE_PACKAGE_RFC" "(FUNCTION)", nor was it propagated by
          a RAISING clause.
         Since the caller of the procedure could not have anticipated that the
         exception would occur, the current program is terminated.
         The reason for the exception is:
         A PERFORM was used to call the routine "CUBE_WRITE_PACKAGE" of the program
          "GPD1S8520HM8UV0U2XBDVPADF03".
         This routine contains 7 formal parameters, but the current call
         contains 10 actual parameters.

  • Concept of Integrated Consolidation Unit of SEM BCS

    HI Experts,
    I'm now in the SEM BCS 4.0 and BW 3.5 implementation. Previously I was the ECCS specialist and before the FI and AM specialist.
    Now I'm in SEM BCS implementation.
    I have one question in connection to the integrated consolidation unit. As the reference, I take the concept of this using the ECCS.
    As you might know, the creation of integrated consolidation unit for using realtime update method in ECCS, is pulled from FI company ID.
    Meanings if I set the configuration properly, I can pull out the company master data as the consolidation unit master data in consolidation monitor.
    Now, in SEM BCS, I want to do the same thing. I mean, off course I can create company ID in R/3 and then create the consolidation unit manually using UCWB. But this scenario can create inconsistency, and I also think this is not the right concept of doing integration between R/3 and SEM BCS.
    My question is : what is the concept of this master data integration, and what is the proper way to do it?
    Any advise on this question is highly appreciated.
    Thank you in advance.
    regards,
    Halim

    Hi Halim,
    You need to build properly your data basis in data model.
    Assign your company to a consolidation unit role:
    http://help.sap.com/saphelp_sem350bw/helpdata/en/dd/f3783bcfef4a2de10000000a114084/frameset.htm
    I sent to you the file concerning BCS that you asked for in another thread.
    Best regards,
    Eugene

  • Copy data posting level 20 - 30 is not allowed SEM BCS

    Hi expert,
    We need to copy data from a version to another version, is very
    important for us to import documents with posting level 20/30. Copy
    task is only used for documents with posting level 01 - 10. But, in EC - CS we could to execute the copy program for this kind of documents,
    and we are migrating from Ec-cs to SEM BCS so, we need to keep the same
    funcionality.
    Any idea in order to solve it? Badi´s? user exits?
    Thanks in advance,
    Beatriz Bernardos

    Hi
    It is not possible to copy data at posting level 20 and 30 as they are group entries.
    Logically, it should not allow one to copy the entry at posting level 20 and 30.
    SAP doesnt support copying data at posting level 20 and 30.
    I had same kind of requirement in all of my BCS project but I believe logically it is not correct to copy group level entry.
    Alterntively, what you can do is,
    create export datasource to load the data back into BCS integration cube from BCS total records virtual cube by changing posting  level 20/30 to 01 or 10 in the update rule.
    It still believe it will give you the wrong result in the report.
    Please have a common understanding with customer that it is not possible copy posting level 20/30
    Regards,
    Manish

  • SEM BCS - BPC

    Hello All,
    Can you please let me know the differences between SEM BCS and SAP BPC. What I know is SEM BCS is an SAP product for Financial Consolidation (Legal and Management). SAP BPC is the new product taken over from Outlooksoft. It also features the consolidationa and planning functionalities. Can you please suggest which is a better product.
    Regards
    Vikram

    Hi Vikram
    Please use Search Functionality in the forum, there are many threads answering your question.
    Based on my experience, in current versions BPC 5.1 has lot of limitations to be used as full consolidation product.
    It has good features and will be developed in future releases as complete consoliation product.
    From my understanding, till then BCS will only be preferred for consolidation.
    Thanks and Regards
    Anurag

  • Differences between SEM BCS and SAP BPC

    Hello All,
    Can you please let me know the differences between SEM BCS and SAP BPC. What I know is SEM BCS is an SAP product for Financial Consolidation (Legal and Management). SAP BPC is the new product taken over from Outlooksoft. It also features the consolidationa and planning functionalities. Can you please suggest which is a better product.
    Regards
    Vikram

    There is nothing like better or worse product.
    BCS has some strong features like consolidation monitor, investment consolidation and for most consolidation functions, configuration is very easy. In BPC, you may have to write scripts.
    BCS has BW as the backbone  where for BPC 5.1 there is none. Howveer, in  BPC 7.0, the BPC will rest on BI and things will be much better.
    Ravi Thothadri

  • How unrealised sales is handled by SEM - BCS?

    Hi all,
    For intercompany transferred of inventory at profit, there are two elimination involved:-
    - Unrealised Sales
    - Unrealised Profit & Loss
    In SEM BCS, elimination of unrealised profit & loss is handled by IPI. How about unrealised sales?
    Many thanks.
    Regards, Renee

    Renee,
    You cannot post directly to clearing items. That's why you get the error. The only possibility is to do it with reclasses on 01-10 level of postings without the doc type assigned.
    But you don't need it. AFAIU, you try to make entries for unrealised profit in inventory? Then  the entries you make should be as following:
    DR COGS (or any other cost/expense account) in P&L
    CR Inventory (B/S)
    The system will automatically add:
    DR Clearing item in B/S
    CR Clearing item in P&L
    It's how the clearing items work.
    For an example of this functionality (maybe it'll help you to configure it properly) see here:
    Re: SEM-BCS Journal Posting for Elim.inventory

  • SEM BCS Q&DB

    Hi
    I am looking for Q&DB relevant to SEM BCS BW based. Can any one send the link. Appreciate your help.
    Regards
    Chrizz

    I doubt if there are updated version of 6.0 yet.  Your best bet is to look on the BCS section of
    service.sap.com/sem.
    They are more likely info on 3.x and 4.0.  There used to be an ASAP section with some questionaire on BPS and I think maybe something in BCS but things have moved around and I cannot find the ASAP section any more.
    Hope this helps,
    Mary

  • SEM-BCS  Enh 5.0 in SEM-BW 605 as per 1171344

    any rumors on when a new version ([currently 7|https://service.sap.com/sap/support/notes/1171344]) is coming to the market?
    looking at prior versions it should happen any time now.

    HI Greg,
    Are you trying to give us a clue on something about to happen?
    I'm very interested in EHP5 and by co-incidence I just checked again today:
    1171344 - last updated in July 2010, there is high level info on the two functions to be provided inside EHP5,
    There is also a little information here: https://websmp109.sap-ag.de/erp-ehp
    However, we are still lacking the low level details.
    1120848 - Restricted usage of SEM-BW 7.00 or FINBASIS 7.00 last updated December 2007 confirms that SEM-BW 7 is and FINBASIS 7 are specifically for "Banking Services" and not to be confused with upgrades to SEM-BCS, which will be release 605, EHP5 for BCS.
    NB By looking at some other OSS notes, I found this info on what looks like Support Pack (SP) 4 of SEM-BW 605:
    https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/spat/index.htm?sp1=SAPK-60504INSEMBW
    There are 15 OSS notes in there for BCS specifically, so this suggests that some people are on release 605.
    Thereafter a little fiddling with the address bar led me to the equivalent 60504 for FINBASIS, but there were no notes for BCS.
    I worked backwards to here:
    https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/spat/index.htm?sp1=SAPK-60503INFINBASIS
    There are two BCS notes here (drill down to FIN-FB-WB)
    So, this suggests that EHP5 is already live at various ramp up sites, and SPs are being created to address issues
    When will it be on general release is still my question
    - have you got some insider knowledge to share?

  • Remote Extractor and Real Time Infocube for SEM BCS

    Hi Experts,
    I have somes doubts about the integration between SEM and BW.
    There is a cycle that have the next processes:
    1.- begin in R/3 with the movements in FI, CO and/or general ledgers
    2.- Activate the extractors standards for replicate/extract data to BW. For example, 0FI_GL_XXXX.
    3.- Configure a method for take the information from BW to SEM.
    4.- My doubt begin here... For take the information from SEM to the real time infocube, where I configure?  What Have I for configure?
    The real time infocube, What is the proposal? Where take the data?  Here, Do the remote extractor begin to apply?
    Thank you very much for your collaboration.
    Regards,
    Jeysi Ascanio

    We're using 0FI_GL_20 to read directly from FAGLFLEXT into SEM-BCS via a BI remote cube.  There are some basic transformations in BI to "populate" the remote cube, then a standard Load from Data Stream in BCS to do final mappings.  In the BCS workbench, just create a source data basis off the remote cube.
    This works at my current project due to fairly low ECC data volumes.  If you are doing any complex mapping on the Company or Fiscal Year / Period infoobjects, you may need to create a inverse mapping routine in the remote cube to transfer selection criteria.  If you see messages in the monitor following a data load such as "xx,xxx of xxx,xxx records ignored", that means that you are reading too much data from ECC and it is only getting filtered on the BCS side.  We had this problem with a custom extractor and adding an inverse mapping routine cut the load from ~5min to 30sec.  (Basically, the custom, template-delivered, extractor only had 0FISCPER, not 0FISCPER3 and 0FISCYEAR, so we would read all 17 K4 periods into BI, map them into BCS, then BCS would throw out the unneeded periods.  Unfortunately, we did not have the option to change the extractor, so this was the best approach.).
    If I had large data volumes, I would use a regular BI basic cube for staging (or possibly a multi-cube with a mix of basic and realtime, depending on the load requirements to BCS).
    If you use 0FI_GL_20, I would strongly recommend you implement OSS Note 1245822, or be on SAP_APPL 603.0002 or later.
    Hope that helps,
    - Chris

Maybe you are looking for

  • How to generate 20 billion transactions for a POC

    Hi, I have a requirement to generate 20 billion transactions for a data warehouse proof of concept. There are a number of rules which will be required to be implemented to make analysis of the transactions seem realistic. Such as certain products are

  • HT5767 if i delete something in mail app, why does it now show deleted in iPhone?

    how can i get my mail that i delete on my mail app to show deleted in my iPhone effective immediately... it works perfectly fine with my hotmail account with my iPhone but not with the mail app..

  • What's this screen mean?

    My Mac throws up this screen from time to time and I have no idea what its significance is. My internet connection seems to be working fine at those times. Can anyone tell me whether this indicates a problem and what to do about it?

  • Help to get executed statement

    Hi!. I am going to sync remote databases with queues. I have already configured the queues, but now i need to get the statements that are executed to send them to the queues and then execute the same on the other side of the queue. So is there a way

  • Distributed Destination and multiple clusters

    We have two clusters; each consisting of two managed servers. Can I create a single distributed JMS destination for BOTH clusters? If yes, how? If no, what is the best alternative so that I do not have to change the application for JMSqueue name?