Reg:New GL Concept

Hi Gurus,
What is the Difference Between Leading Ledger and Non-Leading Ledger conecpt in New Gl concept.
regards
JK

Hi
Leading Ledger & Non Leading Ledger the difference can be summarized as
1. Different Fiscal year can be mapped ( Suppose you need a reporting in two Fiscal year like Jan-Dec & Apr-Mar, we can have on leading ledger (Jan-Dec) & on NonLeading ledger (Apr-Mar). It means when I am posting in Dec-07 on Leading ledger the period will be 12 (Jan-Dec) & in Nonleading ledger the period would be 9 (Apr-Mar). So that We can take Balance sheet for two seperate fiscal year Jan-Dec & APr-Mar.
2. Apart from above we can have different currency also.
In short prallel ledger (non leading ledger) had replace Special Purpose Ledger.
Thanks
Colin Thomas

Similar Messages

  • New OO concepts introduced in ECC 6.0

    Hi All,
    I  want to know what all new object oriented concepts introduced into ECC 6.0 when compared to 4.7C version. Please provide the useful information.
    Thanks

    Re: New OO concepts introduced in ECC 6.0
    Regards
    Anbu B

  • Major differences between GL and New GL concepts

    Hai,
    Please let me know the major differences between old and new gl concepts and if possible explain with few examples....
    Thanks in advance.....
    Regards
    Moderator: Please, read and respect SDN rules

    Hi
    Refer to the link below-
    http://www.sap.com/solutions/business-suite/erp/financials/pdf/BWP_New_Gen_Ledger_Acct_Functions.pdf
    Regards
    Milind

  • New GL concepts, Document splitting and how teh system behaves in different

    Hi gurus,
    I need this NEW GL Concepts
    Thanks
    Srinivas

    Hi,
    Please go thru the below mentioned details:
    New GL Configuration:
    1 Define Currencies for Leading Ledger:
    Financial Accounting (New)>**** (New)>Ledgers>Ledger>Define
    currencies of the leading ledger
    2.Define Ledger for General Ledger Accounting
    F/A (New) > ****/ (New) > Ledgers >Ledger > Define Ledgers for
    General Ledger Accounting
    3.Assigning Scenarios to Ledger
    Financial Accounting (New)>****(New)>Ledgers>Ledger>Assign
    scenarios & Customer fields to ledger
    4.Defining Segment
    Enterprise Structure>Definition>Financial Accounting >Define segment
    5.Activate Document Splitting :
    FA(N)>GLA(N)Business Transactions> Doc.Splitting >Activate Doc
    Splitting Spl Note: Always see that the tick is on inheritance
    6.Classify G/L Accts for Document Splitting :
    Financial Accounting (New)>General Ledger Accounting (New)>Business Transactions>Document splitting> Classify G/L Accts for Document Splitting
    7.Classify Document Types For Document Splitting :
    Financial Accounting (New)>General Ledger Accounting (New)>Business Transactions>Document Splitting> Classify Documents Types for Document Splitting
    Define Zero Balancing Clearing Account: Financial Accounting (New)>General Ledger Accounting (New)>Business Transactions>Document splitting>Define Zero Balance Clearing Account
    8.DEFINE DOCUMENT SPLITTING CHARACTERISTICS FOR GENERAL LEDGER ACCOUNTING:
    Financial Accounting (New)>General Ledger Accounting (New)>Business Transactions>Document splitting>Define Doc Splitting Characteristic for General Ledger Accounting
    Define Zero Balancing Clearing Account: Financial Accounting (New)>General Ledger Accounting (New)>Business Transactions>Document splitting>Define Zero Balance Clearing Account
    10.DEFINE DOCUMENT SPLITTING CHARACTERISTICS FOR CONTROLLING.
    Financial Accounting (New)>General Ledger Accounting (New)>Business Transactions>Document splitting>Define Doc Splitting Characteristic for Controlling
    11.FI- Co Real Time Integration
    Financial Accounting (New)>**** (New)>ledgers>real time integration of Controlling with financial Accounting>Define variants for Real time integration
    12.Assign variants for Real Time Integration to Company Codes: Financial Accounting (New)>**** (New)>ledgers>real time integration of Controlling with financial Accounting>Assign variants for Real time integration to Co Codes
    1.Activate the New General Ledger Accounting by a single click on the clock icon
    2.You will reach to change view "activation of New GL A/cg" detail screen and tick the checkbox and save.
    3. After activation of New General Ledger Accounting, you exit the IMG screen When you re-enter , you find that a new node is added Financial Accounting (New)
    4.After activation of New General Ledger Accounting , a new sub node appears in the IMG structure.
    This sub node is Define Segment
    The menu path is:
    SAP Customizing IMG ---> Enterprise Structure -
    > Definition ---> Financial Accounting ---> Define Segment
    In this IMG activity, you define your segments.
    If you then define your profit centers, you can enter an associated segment in the master record of a profit center. The segment is then derived from the assigned profit center during posting.
    5.Activation has created a new field in Profit Center Master Record : the SEGMENT
    6.Leading and Non- Leading Ledgers
    In General Ledger Accounting , you can use several Ledgers in parallel. This allows you to produce financial statements according to different accounting principles. A ledger uses several dimensions from the totals table it is based upon. When defining Ledgers , one must be defined as the Leading Ledger . The Leading Ledger is based on the same accounting principles as that of the consolidated financial statements. It is integrated with all subsidiary ledgers and is updated in all company codes. This means that it is automatically assigned to all company codes. In each company code, the Leading Ledger receives exactly the same settings that apply to that company code : the currencies, the fiscal year variant and posting period variant .
    You must designate one of your ledgers as the Leading Ledger. It is not possible to designate more than one ledger as the leading ledger.
    The menu path is :
    SAP Customizing IMG -
    > Financial Accounting ( New ) -
    > Financial Accounting Basic Settings (New) -
    > Ledgers -
    > Ledger -
    > Define Ledgers for General Ledger Accounting
    Clicking on the checkbox identifies one of your ledgers as the Leading Ledger.
    7. Activation of Non Leading Ledgers
    Non Leading Ledgers are parallel ledgers to the Leading Ledger . They can be based on local accounting principle, for example. You have to activate a non- Leading Ledger for individual company codes. Non- Leading Ledgers can have different fiscal year variants and posting period variants per company code to the Leading Ledger of this company code.
    The menu path is :
    SAP Customizing IMG -
    > Financial Accounting ( New ) -
    > Financial Accounting Basic Settings (New) -
    > Ledgers -
    > Ledger -
    > Define and Activate Non u2013Leading Ledgers
    8.Assign scenarios to ledgers
    A Scenario combines Customizing settings from different business views. Each business view specifies which posting data is transferred from different application components in General Ledger Accounting, such as cost Center update or Profit Center update .You assign the desired scenarios to your ledgers. For each ledger, you define which fields are filled with posting data from other application components.
    SAP delivers a number of scenarios in the standard system. It is not possible to create additional scenarios.
    The menu path is:
    SAP Customizing IMG -
    > Financial Accounting ( New ) -
    > Financial Accounting Basic Settings (New) -
    > Ledgers -
    >Fields -
    > Display Scenarios for General Ledger Accounting.
    9. Cost of sales accounting
    Cost of sales accounting is a way to create a profit and loss statement (P&L) for a company by comparing the revenues to the costs or expenses incurred to obtain these revenues.
    The expenses are mainly divided by functional area such as:
    Manufacturing
    Administration
    Sales
    Research and Development
    We can activate Cost of Sales Accounting by the following menu path :
    SAP Customizing IMG -
    > Financial Accounting ( New ) -
    > Financial Accounting Basic Settings (New) -
    > Ledgers -
    >Ledger------> Activate Cost of Sales Accounting
    Thanks,
    Prithwiraj.

  • New Authorization concept

    Hi experts,
    what is new Authorization concept in NW2004s.
    All of our queries are created in Query Designer 3.x and our generic Authorization objects are created in RSSM.
    Is it necessary to use new Auth.concept ?
    What are the advantages or disadvantages of new concept?
    Thanks

    Hi there again,
    If you have that entry in RSCUSTV23 it means you're using the old concept of RSSM authorization not mantained anymore by SAP:
    I recommend (as well as SAP) to use the new concept. For that, since you've already the old authorizations, you can do a migration of authorizations with a standard report (transaction se38) called RSEC_MIGRATION.
    This report is of ease to use and does the migration of the old concept to the new one, therefore you can after running the migration use the new concept.
    The worst part, is that is recommended (and you should) do an exaustive battery test, to ensure, no errors are encountered with the new authorization concept after migration.
    You can also read about the migration of authorizations (and the detal of how to use the standard migration report) in here:
    [http://www.sdn.sap.com/irj/scn/events?rid=/library/uuid/659fa0a2-0a01-0010-b39c-8f92b19fbfea&overridelayout=true]
    Diogo.

  • New GL Concept in ECC 6

    Hi Friends,
    Could you please can any  one explain me new GL concept in ECC6
    Thanks & Regards,
    Vas
    Moderator: Please, search SDN

    Hi,
    Please go thru the below mentioned link.
    http://help.sap.com/saphelp_erp60/helpdata/en/29/830e405c538f5ce10000000a155106/content.htm
    Also you can refer the document AC210 - New General Ledger Accounting
    Best Regards,
    Madhu

  • Change dummy profit center to original in New GL Concept

    Hello experts
    We have implemented New GL Concept in ECC6.0. However, some of the documents posted into various GL accounts had gone to Dummy profit center. Is there any way such that already posted documents with dummy profit center can be assigned corresponding original profit center? As of now due to the common dummy profit center has been assigned to various entries, the plant wise reports are not able to display correct figures because dummy profit center is not apportioned to respective plants.
    Similar case is also with Vendor and Customer account balances.
    We had already gone trough few notes and one of them (1164356) suggests using a BAdI FAGL_MIGR_SUBST, but its scope / use is somewhat ambiguous. (It suggests some ABAP work in VALIDATE_ITEM method, although this method is not present in its interface.)
    Kindly help as early as possible...
    Thanks and Regards,
    Srinivas

    Hi
    You are not clear on your post
    1) whether you have implemented Document Slitting or not?
    2) Mapped Zero Balance account or not and
    3) Profit Center and Zero Balance account are checked  in document soplitting charactreristiocs or not?
    I am posting this reply based on the assumption that you have mapped the above configuration.
    If You have assigned Dummy Profit center in FAGL_3KEH, this always overrides the profit center derived, and the system posts with a dummy profit center. Remove the FAGL_3KEH assignment if any so that the system posts to the correct profit Centers.
    Now If you have made the configuration as discussed in points 1,2 3  and other document splitting configurations, then removing FAGL_3KEH will force system to look for the profit centers in all the line items and posts only when this is satisfied.
    A pre requisite will be "Assign Scenarios and Customer Fields to Ledgers" in FA global Settings(New)> Ledgers>Ledger which should be "Profit Center".
    As a concept you may not need assignment of FAGL_3KEH once you have implemented document Splitting.
    Hope this clarifies your situation.
    Don't Forget to award points
    Sarma

  • New authorization concept - Access to data

    Hello, i'm new in SAP BW and i'm in migration process to the new authorization concept.
    Here is what happening:
    I have a role with all access to a company (*) of a provider X.
    I have another role with restricted access to a company (ex: COMPANY1, COMPANY2 and COMPANY3) of a provider Y.
    When i attribute those 2 roles to a user and access a query of the provider Y, i can see all the companies when it was supposed to only see the 1, 2 and 3.
    What am i doing wrong?
    Thank you in advance.
    João Gonçalves

    Hi friend,
    The Authorization concept works on sets concept of mathematics.
    Explanation to your scenario:
    For user A you apply company (*) on provider X and company 1, 2, 3 on provider Y. i.e. u are collectively applying All company codes for provider X and Y. as Company (*) set is a bigger set and the providers set is extended to 2 elements X and Y to get her and not separately.
    Way to check the actual set by which authorization is getting applied:
    RSECADMIN -> Analysis tab -> Execute as user (check with load check box, and RSRT radio button) ->  Execute -> Put a query on which you need to check authorizations (the query must have authorization variable if relevant) -> execute the query -> return back after execution -> on the Execute as user screen hit on Display log option.
    You will get a detailed log for your query execution. Here you will also get a log where what set is applied for the query execution is displayed. You will get an understanding of your issue there.
    Regards,
    Sourabh Deo

  • New GL Concept -Pre requisites & consequences

    Hi,
    Right now my client doesnot have New GL Concept,Now they wanted to plan at GL Account level and see the variancce report GL Account wise.
    If i activate the New GL Concept now,what will happen? any conflicts between existing setup? what are the steps do i need to do if i wanted to do New GL Concept? Please guide me what are the Do's and Don's?
    Kindly advice me..
    Thanks
    Supriya

    hii..
    Check this link
    www.saptechies.com/ecc-60-new-gl-functionality-and-general-faq/
    Regards,
    Aakash

  • New ledger concept replaces the entire special ledger

    Hi Guru's,
    can any tell me the difference between New GL concept with comparision to special ledfer?
    Do New GL totally replces the special ledger?
    rgds,

    Hi Srikanth,
    Could you please throw some light  how can we go for another additional currency with the help of FI-Special Purpose Ledger.
    In our case hard currency (USD) and group currency (INR) are fix.and for additional currency we have only option i.e. Currency type. Is there any another way for creating additional currency in FI-SPL
    We have stuck here on this point. Any answer would be highly appreciable.
    Regards,
    Nilesh

  • New Authorisation Concept

    Hi,
    I have a question about the new Authorisation Concept. In the old concept, we have to mark per infoobject and infocube as authorisation relevant. In the new concept, we only marked in the Infoobject (or navigation attribute) setting.
    My question is if we marked for example characteristics Company Code as Authorisation relevant. All infocubes having Company Code will be check against for authorisation? even though in some cubes according to business logic, the authorisation check is on other characteristics and not on company code. Is the same behaviour for marking authorisation relevant for Navigation attribute.
    Thanks in advance for any advice.

    Hi,
    If the behaviour is as descibed. Then everytime I marked a char or navigational attribute as Authorisation relevant for a new infocube because of some new business logic, I would have to look for all existing infocubes that contains the char/navigational attribute I have marked and apply the changes to their roles (even though they do not require that char as authorisation check)? Otherwise, when user access the reports of existing infocubes, they will get no authorisation. I would think this could happen for example, between infoproviders in a logistic area and finance area where they usually shared the same characteristics/navigational attributes but not the roles and authorisations (characteristics).
    In the old concept, we are able to select on the infoproviders that should be check against the authorisation object. Is the new authorisation concept not able to have this option?
    Cheers,
    CK

  • Doc Splitting & New GL Concepts

    Hi Experts,
    Can any one help me, Document splitting and New GL Concepts...?
    Pls guide me asap.?
    Thanks,
    Lakshmipathi.
    help.sap.com

    Hi Experts,
    Can any one help me, Document splitting and New GL Concepts...?
    Pls guide me asap.?
    Thanks,
    Lakshmipathi.
    help.sap.com

  • Reg.Double click concept in classes

    Hello,
            I  had developed a program  which is extracting data from kna1 and vbak table.Now i am facing a problem when iam using a concept called doubleclick.In my first screen data from kna1 table is displayed.Now i want to see respective data from vbak table when i double click one particular custnumber.How can i use concept doubleclick for that.can anybody explain me in detail.

    Hello Priyanka
    The sample report ZUS_SDN_TWO_ALV_GRIDS_0 shows how to display sales orders per customer using two ALV grids.
    *& Report  ZUS_SDN_TWO_ALV_GRIDS_0
    *& Description: Display KNA1 in 1st ALV grid,
    *&              select VBAK data by double-clicking
    *& SDN: Reg.Double click concept in classes
    *& Screen '0100' contains no elements.
    *& ok_code -> assigned to GD_OKCODE
    *& Flow logic:
    PROCESS BEFORE OUTPUT.
       MODULE STATUS_0100.
    PROCESS AFTER INPUT.
       MODULE USER_COMMAND_0100.
    REPORT  zus_sdn_two_alv_grids.
    DATA:
      gd_repid         TYPE syrepid,
      gd_okcode        TYPE ui_func,
      go_docking       TYPE REF TO cl_gui_docking_container,
      go_splitter      TYPE REF TO cl_gui_splitter_container,
      go_cell_top      TYPE REF TO cl_gui_container,
      go_cell_bottom   TYPE REF TO cl_gui_container,
      go_grid1         TYPE REF TO cl_gui_alv_grid,
      go_grid2         TYPE REF TO cl_gui_alv_grid,
      gs_layout        TYPE lvc_s_layo.
    DATA:
      gs_knb1          TYPE knb1,
      gt_header        TYPE STANDARD TABLE OF kna1,
      gt_position      TYPE STANDARD TABLE OF vbak.
          CLASS lcl_eventhandler DEFINITION
    CLASS lcl_eventhandler DEFINITION.
      PUBLIC SECTION.
        CLASS-DATA:
          md_customer    TYPE kunnr  READ-ONLY.
        CLASS-METHODS:
          handle_double_click FOR EVENT double_click OF cl_gui_alv_grid
            IMPORTING
              e_row
              e_column
              es_row_no
              sender.
    ENDCLASS.                    "lcl_eventhandler DEFINITION
          CLASS lcl_eventhandler IMPLEMENTATION
    CLASS lcl_eventhandler IMPLEMENTATION.
      METHOD handle_double_click.
      define local data
        DATA:
          ls_header    LIKE LINE OF gt_header.
        CHECK ( sender = go_grid1 ).
        READ TABLE gt_header INTO ls_header INDEX e_row-index.
        CHECK ( ls_header-kunnr IS NOT INITIAL ).
        md_customer = ls_header-kunnr.
      Triggers PAI of the dynpro with the specified ok-code
       cl_gui_cfw=>set_new_ok_code( 'DETAIL' ).  " not 4.6c
        CALL METHOD cl_gui_cfw=>set_new_ok_code
          EXPORTING
            new_code = 'DETAIL'
         IMPORTING
           RC       =
      ENDMETHOD.                    "handle_double_click
    ENDCLASS.                    "lcl_eventhandler IMPLEMENTATION
    START-OF-SELECTION.
      SELECT        * FROM  kna1 INTO TABLE gt_header  UP TO 500 ROWS.
    Create docking container
      CREATE OBJECT go_docking
        EXPORTING
          parent                      = cl_gui_container=>screen0
          ratio                       = 90
        EXCEPTIONS
          OTHERS                      = 6.
      IF sy-subrc <> 0.
      MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      CALL METHOD go_docking->set_extension
        EXPORTING
          extension  = 99999  " full-screen
        EXCEPTIONS
          cntl_error = 1
          OTHERS     = 2.
      IF sy-subrc <> 0.
      MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    Create splitter container
      CREATE OBJECT go_splitter
        EXPORTING
          parent            = go_docking
          rows              = 2
          columns           = 1
         NO_AUTODEF_PROGID_DYNNR =
         NAME              =
        EXCEPTIONS
          cntl_error        = 1
          cntl_system_error = 2
          OTHERS            = 3.
      IF sy-subrc <> 0.
      MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    Get cell container
      CALL METHOD go_splitter->get_container
        EXPORTING
          row       = 1
          column    = 1
        RECEIVING
          container = go_cell_top.
      CALL METHOD go_splitter->get_container
        EXPORTING
          row       = 2
          column    = 1
        RECEIVING
          container = go_cell_bottom.
    Create ALV grids
      CREATE OBJECT go_grid1
        EXPORTING
          i_parent          = go_cell_top
        EXCEPTIONS
          OTHERS            = 5.
      IF sy-subrc <> 0.
      MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    Set event handler
      SET HANDLER: lcl_eventhandler=>handle_double_click FOR go_grid1.
      CREATE OBJECT go_grid2
        EXPORTING
          i_parent          = go_cell_bottom
        EXCEPTIONS
          OTHERS            = 5.
      IF sy-subrc <> 0.
      MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    Display data
      gs_layout-grid_title = 'Customers'.
      CALL METHOD go_grid1->set_table_for_first_display
        EXPORTING
          i_structure_name = 'KNA1'
          is_layout        = gs_layout
        CHANGING
          it_outtab        = gt_header
        EXCEPTIONS
          OTHERS           = 4.
      IF sy-subrc <> 0.
      MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      gs_layout-grid_title = 'Sales Order per Customer'.
      CALL METHOD go_grid2->set_table_for_first_display
        EXPORTING
          i_structure_name = 'VBAK'
          is_layout        = gs_layout
        CHANGING
          it_outtab        = gt_position  " empty !!!
        EXCEPTIONS
          OTHERS           = 4.
      IF sy-subrc <> 0.
      MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    Link the docking container to the target dynpro
      gd_repid = syst-repid.
      CALL METHOD go_docking->link
        EXPORTING
          repid                       = gd_repid
          dynnr                       = '0100'
         CONTAINER                   =
        EXCEPTIONS
          OTHERS                      = 4.
      IF sy-subrc <> 0.
      MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    NOTE: dynpro does not contain any elements
      CALL SCREEN '0100'.
    Flow logic of dynpro (does not contain any dynpro elements):
    *PROCESS BEFORE OUTPUT.
    MODULE STATUS_0100.
    *PROCESS AFTER INPUT.
    MODULE USER_COMMAND_0100.
    END-OF-SELECTION.
    *&      Module  STATUS_0100  OUTPUT
          text
    MODULE status_0100 OUTPUT.
      SET PF-STATUS 'STATUS_0100'.  " contains push button "DETAIL"
    SET TITLEBAR 'xxx'.
    Refresh display of detail ALV list
      CALL METHOD go_grid2->refresh_table_display
       EXPORTING
         IS_STABLE      =
         I_SOFT_REFRESH =
        EXCEPTIONS
          OTHERS         = 2.
      IF sy-subrc <> 0.
      MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDMODULE.                 " STATUS_0100  OUTPUT
    *&      Module  USER_COMMAND_0100  INPUT
          text
    MODULE user_command_0100 INPUT.
      CASE gd_okcode.
        WHEN 'BACK' OR
             'END'  OR
             'CANC'.
          SET SCREEN 0. LEAVE SCREEN.
      User has pushed button "Display Details"
        WHEN 'DETAIL'.
          PERFORM entry_show_details.
        WHEN OTHERS.
      ENDCASE.
      CLEAR: gd_okcode.
    ENDMODULE.                 " USER_COMMAND_0100  INPUT
    *&      Form  ENTRY_SHOW_DETAILS
          text
    -->  p1        text
    <--  p2        text
    FORM entry_show_details .
    define local data
      DATA:
        ld_title    TYPE lvc_title.
      SELECT        * FROM  vbak INTO TABLE gt_position
             WHERE  kunnr  = lcl_eventhandler=>md_customer. " Sold-to-party
      CONCATENATE 'Sales Order of customer' lcl_eventhandler=>md_customer
        INTO ld_title
        SEPARATED BY space.
      CALL METHOD go_grid2->set_gridtitle
        EXPORTING
          i_gridtitle = ld_title.
    ENDFORM.                    " ENTRY_SHOW_DETAILS
    Regards
       Uwe

  • New BADI concept in ECC 6.0

    I am trying to gain an understanding of how I would implement one of the new BADIs in ECC 6.0 (badis implmented through and enhancement spot , get badi, call badi concept).
    I am  not looking for information on how to implement a classic badi through se18/se19.
    I have also ready through the SAP help on the new badis and it is still not clear to me. So, please do not provide links to the standard SAP help. I have that.
    I am wondering if anybody has a whitepaper, example, etc.  that explains the details of how to implement, use, trigger the  new badis linked to an enhancement spot.

    Hi  J.J,
    enhancement spot
    A repository object for the administration of explicitly created enhancement options. Enhancement spots are components of a tree structure hierarchy, of which the branches represent composite enhancement spots and the leaves are simple enhancement spots. Implicitly available enhancement options do not have any enhancement spots.
    composite enhancement spot
    Semantic combination of simple and other composite enhancement spots with the aim of providing structure.
    simple enhancement spot
    Reference to a set of enhancement spot element definitions. A simple enhancement spot can occur independently or as a component of a composite enhancement spot.
    ENHANCEMENT-POINT
    Defines a position in an ABAP program as an enhancement option,
    at which one or more source code plug-ins can be inserted.
    the syntax will be like
    ENHANCEMENT-POINT enh_id SPOTS spot1 spot2 ...
    STATIC
    INCLUDE BOUND.
    Enhancement Options
    Definition
    Enhancement options are positions in Repository objects where enhancements can be made. These options are either explicitly defined (by the developer) or exist implicitly. Explicit enhancement options are generally defined in a central initial system. Enhancements are made in follow-on systems.
    Use
    Explicit enhancement options can currently be defined by:
    1. Explicitly flagging source code points or sections in ABAP programs. For an enhancement, these can be enhanced or replaced by source code plug-ins.
    2. Including Business Add-Ins (BAdIs) in ABAP programs. These programs are then enhanced by object plug-ins with predefined interfaces.
    Explicit enhancement options are managed by enhancement spots and enhanced by enhancement implementations.
    Currently, implicit enhancement options are:
    1. Specific options in ABAP programs – such as the end of the program – which can be enhanced by source code plug-ins.
    2. Parameter interfaces of function modules, which can be enhanced with parameters.
    3. Attributes and parameter interfaces of global classes, which can be enhanced with attributes or parameters.
    Implicit enhancement options always exist and do not require enhancement spots. They are also enhanced by enhancement implementations.
    BAdIs Embedded in the Enhancement Concept
    Use
    The definition of BAdIs is managed by enhancement spots. A simple enhancement spot for BAdIs can contain several BAdI definitions as enhancement spot element definitions. BAdIs that would otherwise be spread out in the system can be grouped together semantically.
    This structuring is mirrored on the implementation side through the enhancement implementations. A BAdI can be implemented by several BAdI implementations that are managed by enhancement implementations. A simple enhancement implementation for object plug-ins can contain several BAdI implementations of an enhancement spot as enhancement implementation elements and can implement a BAdI multiple times. Therefore, several enhancement implementations can be assigned to one enhancement spot.
    A BAdI is always assigned to the same package, like the enhancement spot, to which it belongs.
    Example
    The structuring features of BAdIs in enhancement spots can be of a technical or a subject nature.
    If, in the definition of several BAdIs, you have the provision that they are to be used in the same context (this is a feature known only by the person who defines the BAdIs), they must be used by the same simple enhancement spot.
    From a subject point of view, all BAdIs must then be grouped together by affiliation to functional units – for example, payroll – in combined enhancement spots.
    Thanks and regards
    suma sailaja pvn

  • New gl concept

    hi frnds
    I need the concept of new gl. Can anyone tell me what is advantage in new gl in ECC 6.0 rather than 4.7 version?
    What is the purpose to configure SPECIAL PURPOSE LEDGER?
    Thanks
    Moderator: Please, search SDN

    Hello,
    Objective of New GL
    SAP has the following objectives behind the introduction of the New General Ledger:
    Efficiently handle Financial Reporting, according to both local and international accounting principles
    Facilitate increased convergence between financial and management accounting
    Considerably accelerate your period-end closings
    Flexibly perform reporting tasks based on data reconciled in real time
    An unified accounting structure that combines individual ledgers, cost-of-sales, profit-center-accounting & Consolidation-staging ledgers.
    Advantages of New GL
    Introduction and portrayal of new business models within a single solution, thus avoiding separate ledgers like Cost of Sales Ledger, Profit Center Ledger, special purpose ledger etc.
    Data is stored in a single totals table eliminating data redundancy.
    No need for additional reconciliation activities during closing
    Easy to make adjustments to business specific requirements, such as the introduction of customer fields as part of flexible reporting.
    Please REALLY check this link:
    https://wiki.sdn.sap.com/wiki/display/ERPFI/NewGeneralLedger?showChildren=true#children
    Please check the links below:
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/2d/830e405c538f5ce10000000a155106/frameset.htm
    http://help.sap.com/bp_bl603/BBLibrary/HTML/102_EN_US.htm
    What is New GL im FICO ?
    Last, but not least:
    Read the rules of the forum before posting.
    REGARDS,
    RENAN

Maybe you are looking for