BCS Functions

Hi,
For regional consolidation we need to execute the BCS functions once in 6 months, since the consolidated reports are required only once in 6 months.
In this case we have only few consolidation frequency. The first execution of consolidation will be done at the end of June.
So in this case should  the balance carryforward functions, be done at the June period ?
Please share your experience/thought.

Hi Gokul,
I recommend to use "period category" 20 (if you have the standard...) for the periods 6 and 12 with Consolidation Frequenzy 3 (periods 6,12)
Otherwise your Period Initialization maybe won't work correctly.
Carry forward is always displayed in the first period of a year and this period depends on the period category and consolidation frequenzy.
If you want to consolidate in 6 and 12, and you use consolidation frequenzy 3 (periods 6 and 12) then you get the carry forward in 6.
I hope this is understandable...
BR

Similar Messages

  • Hierarchy Function Modules (or Methods)?

    I am trying to retrieve all hierarchies, and their children nodes, below a main node. Is there a function module in SEM/BCS for doing this?
    Are there other function modules that come in handy with hierarchies?
          Thank-You.

    There isn't a single FM that I'm aware of.  You can piggy back the standard BCS functionality and acheive something similar.
    You need to know period, year, version and fiscal year variant. 
    Then...for this structure:
    CG1
    - CG2
    - CG3
    - - CG4
    you can pass CG1 as your "parent" and retreive CG2, CG3, and CG4 as selections (according to date-from date-to in your CG master data).
    I'll try to include the relevant section for this (it's from a number of methods in a class I created for an outbound interface)....I'm sure I don't have all the data declarations, and I might have a few unnecessary sections.
    global variables
      data DO_AREA type ref to IF_UC_AREA .
      data DO_MODEL type ref to IF_UC_MODEL .
      data DO_MD_FACTORY type ref to IF_UG_MD_FACTORY .
    initialize objects
    *** method for initialize objects
      DATA:
      lo_factory        TYPE REF TO if_ug_md_factory,
      lo_char           TYPE REF TO if_ug_md_char,
      lo_value          TYPE REF TO if_ug_md_char_value,
      lt_field_val      TYPE ugmd_ts_field_val,
      ls_field_val      TYPE ugmd_s_field_val.
    * Initialize master data factory
      CALL METHOD cl_uc_area=>if_uc_area~get_md_factory
        EXPORTING
          i_area        = c_cons_area
        IMPORTING
          eo_md_factory = lo_factory.
      do_md_factory = lo_factory.
    * get area object, if it's not set
      IF do_area IS NOT BOUND.
        lo_char = do_md_factory->get_char_instance(
            i_fieldname = uc00_cs_fld-area ).
        ls_field_val-fieldname = uc00_cs_fld-area.
        ls_field_val-value     = c_cons_area.
        INSERT ls_field_val INTO TABLE lt_field_val.
        lo_value = lo_char->get_value_instance(
           it_value = lt_field_val ).
        do_area   ?= lo_value.
    *   get data model
        IF do_model IS NOT BOUND.
          CALL METHOD do_area->get_model
            IMPORTING
              eo_model = do_model.
        ENDIF.
      ENDIF.
    determine lower level consolidation groups
    **Include lower level consolidation group nodes in cube selection.
      DATA:
      lo_context           TYPE REF TO if_uc_context,
      lt_value             TYPE uc0_ts_value,
      ls_value             TYPE uc0_s_value,
      ls_o_sel             TYPE uct_sx_sel,
      lt_sel               TYPE uc0_ts_sel,
      ls_sel               TYPE uc0_s_sel,
      ls_sid               TYPE ucd_s_sid,
      ls_sel_node          TYPE uc0_s_sel_node_sid,
      lt_sel_node          TYPE uc0_ts_sel_node_sid,
      lt_o_sel             TYPE uct_t_sel.
      CLEAR lt_value.
      ls_value-fieldname = c_cgcomp_fieldname. ' /1FB/SEM_CGCOMP
      ls_value-value = i_sem_cgcomp.           ' "parent" consolidation group
      APPEND ls_value TO lt_value.
      CALL METHOD do_model->do_sidmap->convert_value_to_sid
        EXPORTING
          i_fieldname = c_cgcomp_fieldname
          it_value    = lt_value
        IMPORTING
          es_sid      = ls_sid
        EXCEPTIONS
          not_found   = 1
          OTHERS      = 2.
      CLEAR lt_sel_node.
      ls_sel_node-fieldname =  c_cgcomp_fieldname.
      ls_sel_node-sign      = uc00_cs_ra-sign_i.
      ls_sel_node-s_node    = ls_sid.
      INSERT ls_sel_node INTO TABLE lt_sel_node.
      CLEAR lt_sel.
      CLEAR lt_value.
      CALL METHOD do_model->do_data_factory->create_sel
        EXPORTING
          it_node_sid = lt_sel_node
        RECEIVING
          eo_sel      = ls_o_sel-o_sel.
      APPEND ls_o_sel TO lt_o_sel.
      CLEAR ls_value.
      ls_value-fieldname = '/1FB/CS_VERSION'.     " CS Version
      ls_value-value = g_cs_version.
      APPEND ls_value TO lt_value.
      CLEAR ls_value.
      ls_value-fieldname = '/BIC/BCS_VERS'.          " Custom Version
      ls_value-value = g_bcs_vers.
      APPEND ls_value TO lt_value.
      CLEAR ls_value.
      ls_value-fieldname = 'FISCPERIOD'.
      ls_value-value = g_fiscperiod.
      APPEND ls_value TO lt_value.
      CLEAR ls_value.
      ls_value-fieldname = 'FISCVARNT'.
      ls_value-value = g_fiscvarnt.
      APPEND ls_value TO lt_value.
      CLEAR ls_value.
      ls_value-fieldname = 'FISCYEAR'.
      ls_value-value = g_fiscyear.
      APPEND ls_value TO lt_value.
      CALL METHOD do_model->derive_context
        EXPORTING
          it_value     = lt_value
        IMPORTING
          eo_context   = lo_context
        EXCEPTIONS
          info_missing = 1
          OTHERS       = 2.
      CALL METHOD ls_o_sel-o_sel->set_context
        EXPORTING
          io_context = lo_context.
      CALL METHOD ls_o_sel-o_sel->get_sel
        IMPORTING
          et_sel = lt_sel.
    * lt_sel will contain the lower-level consolidation groups, beneath the "parent" consolidation group (i_sem_cgcomp)
    * Add cons groups to selection criteria
      DELETE gt_range WHERE chanm = c_objnm_cgcomp.   ' 0SEM_CGCOMP
      LOOP AT lt_sel INTO ls_sel.
        CLEAR  gs_range.
        gs_range-chanm  = c_objnm_cgcomp.   ' 0SEM_CGCOMP
        gs_range-sign   = ls_sel-sign.
        gs_range-compop = ls_sel-option.
        gs_range-low    = ls_sel-low.
        gs_range-high   = ls_sel-high.
        APPEND gs_range TO gt_range.
      ENDLOOP.
    Hope that helps...if not, you might be able to do a find for some of the sections of the code to find exactly how SAP is doing (I can only say that this functionality worked in my situation, not sure it works in all consolidation scenarios).  FYI - I was using this to read from the virtual cube in a custom task in order to outbound consolidated results.
    - Chris

  • COPA vs. BCS design decisions (ex. profitability by customer in BCS)

    We are trying to meet a business goal of identifying gross profit by customer.
    We realize "customer" as a field in BCS is problematic, so we are thinking of only storing certain customers in BCS with a catch-all "Others" customer - with the goal of keeping the BCS data volume reasonable.
    Consider the scenario: US company sells material X qty 1 to Spain company for 100 with cost of 30 (therefore profit of 70)
    Spain sells same material X qty 1 to third-party customer for 120.
    Spain from a local perspective profits 20, however the group from an overall perspective profits 90 ( the US revenues of 100 eliminate against the Spain COGS of 100 so you are left with revenue of 120, COGS 30, profit 90 - from the group perspective ).
    We want to know how to see, on a customer level, the 90 profit from these transactions. 
    We do not believe COPA can do this, can this may be accomplished in BCS? 
    If you do a "one-sided" elimination (elimination driven by the revenue side only) of the intercompany revenue the system would not be able to reference customer on the elimination. We are wondering if this scenario of analyzing overall profit by customer can be accomplished by BCS functionality and are particularly interested in knowing what functionality you used to accomplish this requirement and in what sequence within the BCS close (BCS monitor).
    Thank you in advance for any input you may have.
    Also we are interested in any opinions/comments anyone may have about design decisions regarding BCS vs. COPA in BW.  BCS business content identifies a sample design for a BCS data model including item, company, movement type, trading partner, functional area, etc.  COPA (as configured in R3/ECC and extracted to BW) commonly features analysis by customer, material, etc.  Considering BCS features elimination functionality, what design concerns have people faced with respect to fields that they include in both reporting systems?  Obviously a prominent concern is sizing of the systems, but what common characteristics has anyone decided to feature in both systems? What considerations drove the decisions as to what common characteristics to feature in both BCS and COPA?

    Hi John,
    Reg, your last question - might be useful info in here, if you have not seen it yet:
    Re: Reports using COPA cube, BCS Cube

  • BCS Using a Recipient list

    Hello,
    I use the BCS Interface to send a mail to SAPOffice and external recipients ... .. While doing this with the API functions it was possible to set a predefined SAPOffice recipient list.
    Can I do this also with the BCS functions and how ?
    Thank you,
    Sven

    Figured it out.

  • 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

  • Grantor Managment solutions and BCS problem after technical upgrade.

    Hello every one,
    The current release SAP installation was upgraded to ECC 6.0; this was a technical upgrade and did not replace functionality such as "Former Budgeting" with the new BCS functionality.  SAP developed the Grantor Management solution utilizing BCS.  BCS utilizes a different table structure from the Former Budgeting functionality.  The current tables do not contain the BCS reference points to each other which limits the implementation of Grantor Management in the same instance. There are no plans to upgrade to BCS functionality at this point in time.
    what are my options? How can we work around this issue?
    Regards
    K

    Hi,
    Thanks for the resposnse.
    But when i go through the OSS notes it is provided that there will be performance problem in executing the report.
    How to get it solved?
    Thanks,
    Regards
    M.A

  • I want to set up SEM BCS system

    I want to set up SEM BCS 6.0 system.  I've  found  a note 855383 which mentions how to set up SEM 6.0. 
    SInce we only want to use SEM BCS function, which component shall I  install , FINBASIS 600 or SEM-BW  6.0 or both ?
    Could anyone help me ?
    Thank you.

    Hi Kahoh Ko,
    We need to install FINBASIS, SEM-BCS  & PI Basis as well.
    Thanks

  • BCS Blueprint

    Hi all,
    Can anyone provide me BCS blueprint and design documents? My company is planning to implement BCS in near future, and we are working on the sandbox for different scenarios.
    Best Regards,
    Kaan

    Dear BCS Gurus..
    I am currently on the BCS blue printing and requirement gathering project ,need some real good tips or links or documents which talks abt these phase and the important points to know...
    thanks
    Moini..
       Re: BCS - Modelling requirements   
    Posted: Feb 24, 2007 4:49 PM    in response to: moini kembly       Reply      E-mail this post 
    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.
    Hope it helps.
    Best regards,
    Eugene

  • Indirect act alloc Vs BCS Activation

    Hello,
    The customization documentation to BCS component assignment - Fund and Func area tells that BCS is not supported for indirect activity allocation (RKIL).
    I cannot understand - "is not supported" means that this operation never works with BCS active or it works correctly just some BCS functions are not available?
    Has someone used RKIL (KSC5) with Fund and Func area active in 6.0?
    Thanks,

    Thanks a lot, its good news for us
    Have you used IAA with BCS Active? Maybe we forgot some customizing?
    FMDERIVE shows that all BCS assignments are derived, the Func area in cost center master data is present, but the F6804 error message (BLANK value of Fund) comes

  • Send an SAP object (BUS****) as attachment with SAP Mail

    Hi all,
    I'd like to send a internal SAP(express)-mail
    with a purchase order as business object (BO) attached. (here BO = BUS2012).
    It's the same thing you can do with generic object services, GOS, to send a SAP business object as mail notification
    attachment.
    Can I use the function 'SO_DOCUMENT_SEND_API1' or
    do I have to use the BCS-functions?
    All the reports BCS_EXAMPLE* don't send a
    business object.
    Thanks in advance,
    Markus

    Hi Markus,
    Seems as if FM 'SO_DYNP_DOCUMENT_TRANSFER_API1' may popup a window. Below is a working program. Have fun!!
    Cheers,
    Ramki.
    REPORT  zramki_send_mail_bor                    .
    *& Report  ZRAMKI_SEND_MAIL_BOR
    *&  Send document with BOR Object as attachment
    DATA: docdata    LIKE sodocchgi1,
          objpack    LIKE sopcklsti1 OCCURS 10 WITH HEADER LINE,
          objhead    LIKE solisti1   OCCURS 10 WITH HEADER LINE,
          objtxt     LIKE solisti1   OCCURS 10 WITH HEADER LINE,
          objbin     LIKE solisti1   OCCURS 10 WITH HEADER LINE,
          objhex     LIKE solix      OCCURS 10 WITH HEADER LINE,
          reclist    LIKE somlreci1  OCCURS  1 WITH HEADER LINE.
    DATA: tab_lines  TYPE i,
          doc_size   TYPE i,
          objdes(100).
    * For the BOR attachment
    CONSTANTS:
      c_object_describe LIKE swotobjid-describe VALUE '*<OBJECT>*'.
    DATA:
      l_object      TYPE swotobjid,
      l_objheader   LIKE soxobj.
    PARAMETERS:
      p_objtyp TYPE swo_objtyp OBLIGATORY,
      p_objkey TYPE swo_typeid OBLIGATORY.
    * Create Message Body
    *   Main Text
    objtxt = 'Test Document.'.
    APPEND objtxt.
    objtxt = 'You will find a BOR object attachment in message.'.
    APPEND objtxt.
    objtxt = 'Have a nice day.'.
    APPEND objtxt.
    *   Title and Description
    DESCRIBE TABLE objtxt LINES tab_lines.
    READ     TABLE objtxt INDEX tab_lines.
    docdata-doc_size = ( tab_lines - 1 ) * 255 + STRLEN( objtxt ).
    docdata-obj_name  = 'BOR Object'.
    Concatenate p_objtyp '-' p_objkey into objdes.
    Concatenate 'BOR Object' objdes 'as Attachment'
           into docdata-obj_descr separated by space.
    condense docdata-obj_descr.
    *   Write Packing List (Main)
    CLEAR objpack-transf_bin.
    objpack-head_start = 0.
    objpack-head_num   = 0.
    objpack-body_start = 1.
    objpack-body_num   = tab_lines.
    objpack-doc_type   = 'RAW'.
    APPEND objpack.
    * Create OBJ attachment
    l_object-describe = c_object_describe.
    l_object-objtype  = p_objtyp.
    l_object-objkey   = p_objkey.
    CALL FUNCTION 'OWN_LOGICAL_SYSTEM_GET'
      IMPORTING
        own_logical_system             = l_object-logsys
      EXCEPTIONS
        own_logical_system_not_defined = 1
        OTHERS                         = 2.
    IF sy-subrc <> 0.
      MESSAGE e398(00) WITH 'No Log Sys Found'.
    ENDIF.
    MOVE-CORRESPONDING l_object TO l_objheader.
    APPEND l_objheader TO objhead.
    *   Write Packing List (Attachment)
    CLEAR objpack.
    objpack-head_start = 1.
    objpack-head_num   = 1.
    objpack-body_start = 0.
    objpack-body_num   = 0.
    objpack-doc_type   = 'OBJ'.
    objpack-obj_name   = p_objtyp.
    objpack-obj_descr  = Objdes.
    APPEND objpack.
    * Create receiver list
    reclist-receiver = sy-uname.
    reclist-rec_type = 'B'.
    APPEND reclist.
    * Send Message
    CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
      EXPORTING
        document_data              = docdata
        put_in_outbox              = 'X'
        commit_work                = 'X'   
      TABLES
        packing_list               = objpack
        object_header              = objhead
        contents_bin               = objbin
        contents_txt               = objtxt
        receivers                  = reclist
      EXCEPTIONS
        too_many_receivers         = 1
        document_not_sent          = 2
        document_type_not_exist    = 3
        operation_no_authorization = 4
        parameter_error            = 5
        x_error                    = 6
        enqueue_error              = 7
        OTHERS                     = 8.
    IF sy-subrc <> 0.
      MESSAGE ID 'SO' TYPE 'S' NUMBER '023'
              WITH docdata-obj_name.
    ENDIF.
    WRITE: / 'End of Program'.

  • Using Sender Address in Email sending process

    Hi all,
             I have a requirement that we are sending mail to multiple people. Here i am able to maintain TO Addresses but my requirement is i want to maintain From_address(i.e sender address)
    Problem is by default SAP sends by using SY-UNAME as per person looged in.
    Can we send From_address(sendera ddress) by using variable but not sy-uname.
    Thanks,
    Rajesh
    Edited by: rajesh pattnaik on Apr 21, 2009 5:24 PM

    Hi,
    If you use BCS functionality for sending mails, you can find your answer in demo program BCS_EXAMPLE_1
    *     --------- set sender -------------------------------------------
    *     note: this is necessary only if you want to set the sender
    *           different from actual user (SY-UNAME). Otherwise sender is
    *           set automatically with actual user.
          sender = cl_sapuser_bcs=>create( sy-uname ).
          CALL METHOD send_request->set_sender
            EXPORTING i_sender = sender.
    Enjoy!

  • SEM-BPS: Transporting allocations

    Hi,
    I have used UPC_TRANSPORT_BPS_ALL to transport a planning function (Allocation) that contains several parameter groups. When going to target system I see the transported parameter groups but cannot process these. I get error message about missing consolidation methods. When I take a look at table e.g. ucf001c I see these parameter groups in source system but not in target system. This table is one of the consolidation methods. Does someone know is there any specific trick to transport planning functions for allocations?
    Thanks!
    Br
    J

    Hello,
    I use for transport BPS0 instead or the report you have used.
    I have developed Allocations (e. g. yesterday) and have transported it also. I had no problems, can execute it and I also had never these kind of error message.
    One thing: Allocation is a BCS-Function and consolidation groups are BCS groups. I guess there must be something wrong in your system, because BPS allocation wants to check BCS customising, which does not make any sense here.
    regards
    Eckhard Lewin

  • Allocation of expenses

    Hello All,
    I had one interesting scenario from my client on allocation of expenses. This was possible using standard BCS functionality but was not straightforward. So would like to listen from you all on your solution before we discuss mine. The solution I proposed has one drawback but fulfills the requirements.
    Requirement is to allocate certain expenses(X,Y and Z) to one particular item (A) for multiple "products".(Product is a sub assignment) .  X,Y and Z expenses have no values for sub assignment "Product.
    Rules of the game are:
    1. Value in items X,Y and Z should remain as it is i.e.,no negation / reversal of these values
    2.Allocation should happen based on Turnover Transaction data in combination with "Product"
    2A. If source values (X,Y and Z) are in Posting Level (PL) 00,01, it should happen based on Company Turnover
    2B. If source values (X,Y and Z) are in PL00,01, and there is no Company Turnover available in transaction data, it should happen based on Group Turnover
    2C. If source values (X,Y and Z) are in PL10, allocation should happen based on Group Turnover.
    Let me know if the scenario is not clear and needs more explanation. Looking forward for your response.
    Thanks
    Sreekanth
    Edited by: Sreekanth on Jun 20, 2011 8:56 AM

    I am much more familiar with reclassifications than allocations, but am certain the results from either can usually be obtained.
    A method layout with trigger of items X,Y and Z, then different source and target is necessary. Then the specifics may be defined as needed.
    It is most likely 2 allocations or reclassifications are needed because for group level allocations or reclassifications it is necessary to use posting level 30 document.

  • Error Code FMUP047 (Define a default account assignment for ....)

    Hello Folks,
    Is there anyone that face above error message when you clear bank clearing account with bank account in F-03 transaction?
    When I look into the content of above error, SAP recommend to make a constant, AKONT for document splitting.
    Then I have created AKONT entry for our document splitting.
    However, the error message won't disappear.
    Is there anyone can help me?
    Even though I have looked into SAP Notes, I couldn't find anything helpful.
    Thank for your help in advance.
    BR,
    Chris Kim
    PS: FYI, online split and FM BCS function have been activated in our system.
          Additionally, there is no FM derivation rule for blank fund center in FM module.

    Hi Chris Kim  ,
    Please give the solution for the same issue I also facing the same problem.
    Amol Rugge

  • Reclassification where target/source does not equal trigger?

    A challenge for reclassification, allocation or other BCS functionality:
    Requirement:
    Where two accounts net to either an asset or a liability, then the accounts that show the opposite sign to the net result must be reclassified to asset or liability.
    Example:
    Load from Data Stream:
    Acct 1000 (asset) = +$1000
    Acct 2000 (liability) = -$500
    Net result = +$500 (asset)
    -This is a positive number, therefore Acct 2000 (liability) value must be reclassified to Acct 1000 (asset):
    and vice versa
    Desired BCS reclasification:
    Acct 1000 (asset) = -$500
    Acct 2000 (liability) = +$500
    BCS data after reclassification:
    Acct 1000 (asset) = +$500
    Acct 2000 (liability) = 0
    Net result = +$500 (asset)
    Standard reclassification
    Standard Reclassifications don't seem to work because the source/target is always equal to the trigger (unless you add a percentage, which would not help this requirement)
    Two steps would be required:
    step 1. the trigger condition that the sum of both Acct 1000 and Acct 2000 = >0
    Source is Acct 2000
    Target is Acct 1000
    but how do we reclassify only the Acct 1000 value NOT the whole amount?
    step 2 would be the opposite:  the trigger condition that the sum of both Acct 1000 and Acct 2000 <0
    Source is Acct 1000
    Target is Acct 2000
    Again, how do we reclassify only the Act 2000 value?
    Allocations
    Allocation functionality contains a few options but I can't see any that would succeed:
    - A specific fixed distribution wouldn't help because the values will change each period
    - A distribution by ratio of existing results (usually used to allocate eg costs by proportion of sales) doesn't seem helpful either
    Next steps
    There might be some combination of (one-sided) reclassifications to statistical accounts, which then become a condition for a subsequent reclassificition or allocation but I haven't got anywhere.
    Any suggestions?

    Thansk Marsy, here it is here:
    Dr/Cr Sign-triggered Reclassification
    I hadn't realised (due to not having used it before) that once selected, the condition selections can be independent of the trigger selections.
    Looks like this should give me what I need:
    Example 1:
    Load from Data Stream:
    Acct 1000 (asset) = +$1000
    Acct 2000 (liability) = -$500
    Net result = +$500 (asset)
    -This is a positive number, therefore Acct 2000 (liability) value must be reclassified to Acct 1000 (asset)
    Example 2
    Load from Data Stream:
    Acct 1000 (asset) = +$1000
    Acct 2000 (liability) = -$1500
    Net result = -$500 (liability)
    -This is a negative number, therefore Acct 1000 (asset) value must be reclassified to Acct 2000 (liability)
    BCS reclassification setup (step 1 - net result is an asset)
    Trigger = Accounts 2000
    Condition = Acct 1000+2000 >0
    Source = Acct 2000
    Target = Acct 1000
    BCS reclassification setup (step 2 - net result is a liability)
    Trigger = Accounts 1000
    Condition = Acct 1000+2000 <0
    Source = Acct 1000
    Target = Acct 2000
    BCS data after reclassification - example 1:
    Acct 1000 (asset) = +$500
    Acct 2000 (liability) = $0
    Net result = +$500 (asset)
    BCS data after reclassification - example 2:
    Acct 1000 (asset) = $0
    Acct 2000 (liability) = -$500
    Net result = -$500 (liability)

Maybe you are looking for

  • List of Released POs

    Hi everyone, How do i get the list of released(final release) Purchase orders? Please can anybody help me with this .. Regards Vikrant....

  • Should I dump Classic now that I'm running 10.4.6?

    I just upgraded to Tiger to support my middle-schooler's new iPod. With the sluggish performance that followed (I was running 10.3.4 before), I searched the forums and ran across a suggestion to dump Classic if your system runs slower than before. No

  • How to open/change an iPhone App

    I'm trying to develop my first app but with ZERO coding/programing experience it's been really difficult to understand all the coding language that goes into an app - even with the great tools from Apple. One of the things that I've been wanting to d

  • Clean Install / Cloning to an second internal drive?

    My boot drive is full and now seems slower - is it file fragmentation which slows a full drive? Here's my set up - I've just added a second internal 1TB drive and want to clean install the original boot drive (350gb) which is almost full and seems to

  • Hi I cannot update my iPad 2 to 5.1

    Hi I cannot update my iPad 2 to 5.1