Inversion of postings at level 10

hi,
maybe itu2019s a simple question, but Iu2019m a bit confused about the inversion of document types at posting level 10. We do the following posting in period 12:
p/l-acc 100
balance-acc -100
Now I have the problem whether to use the inversion for the next year or not.
If I do, the result in period 1 of the following year is the following:
balance-acc -100 (carryforward)
balance-acc 100 (inversion)
p/l-acc 0 (carryforward)
p/l-acc 100 (inversion)
If I donu2019t invert the posting document, the result in period 1 of the following year is the following:
balance-acc -100 (carryforward)
p/l-acc 0 (carryforward)
No matter which setting I use, I only see three possible solutions:
1.     Carrying forward all p/l-accounts and inverting the posting document
2.     Not using the inversion and doing a new (balance- or p/l-)manual posting in period 1 of the new year
3.     Not mixing up balance and p/l-accounts in one posting
All three options are not really satisfying u2013 maybe you have some other suggestions? It would be really great!
Thanks,
B

Hi BickBee and welcome to SDN.
Actually mixing up with B/S and P&L items is a usual thing in accounting and SEM-BCS. In order to balance FS reports (B/S and P&L) the system the system uses special (clearing) items.
Journal entries in your case will look like follows:
P&L -> 100
P&L Clearing -> -100
B/S -> -100
B/S Clearing (= CY R/E) -> 100
After BCF we have:
P&L -> 0
P&L Clearing -> 0
B/S -> -100
B/S Clearing goes to Prev Year R/E -> 100
And, finally, after inversion:
P&L -> -100
P&L Clearing -> 100
B/S -> 100
B/S Clearing -> -100 (will appear during inversion)
Prev Year R/E -> 100
Taking into account that P&L Clearing is an artificial (not accounting) item we got additional income in P&L, right? However, from accounting point of view we also got additional CY R/E in B/S. Which is right.
Considering also that P&L items are usually not BCFed, the situation you faced looks for me like a methodological problem.
Proposed solution: do not invert these J/Es. Actually, shouldn't be such entries. Could you give us more info, what kind of entries you have?
P.S. Your proposed slution #2 will not work at all. - You'll not be able to break consistensy between R/E in B/S and NI in P&L (if not  to do it by 1-sided reclass without DocType).

Similar Messages

  • Substitution - Pass all postings from level 1 WBS to lower WBS

    Dear All,
    I have defined project type X.
    For this particular project type, i want to pass on all the postings from 1st level WBS element to following level WBS elements.
    I think this is possible with Substitution. Can you please guide me how do i do this?
    Thanks
    Regards,
    Smile

    Hi Sarang, Hi Abhishek,
    Thanks for reply!
    I am sorry that i was not very clear with the question.
    In my organisation, projects are defined like this, 1st level WBS is billing element and all revenues are posted to this WBS.
    There are further levels 2,3 to each projects and i would like to distribute the revnues per WBS.
    Example: project A is defined as  - level1 WBS
    Level 2 - each of the depts working on the project.
    The man hours are booked per dept to level 2 WBS elements.
    I would like to distribute the revenues also to each of the depts from level 1 WBS by using substitutions.
    Is this possible? How?
    Regards,
    Smile

  • Why Levels mid-point slider and Exposure Gamma Correction slider not the same?

    Both the mid-point slider in Levels and the Gamma Correction slider in Exposure adjustment appear to modify Gamma.  They even use the same numeric scale.
    When Gamma <= 1, both sliders appear to produce the same results (confirmed with a couple of random sample settings and using the Difference blend mode).
    When Gamma > 1, however, the results are very different.  Levels produces more what one would expect in terms of moving the Gamma curve without moving the white and black points but the Exposure Gamma Correction slider seems to do something very different, either moving the black point or applying a very different curve the produces much brighter tones in the dark shadows.
    Can anyone explain why and how these two adjustments produce different results?
    Is this a bug with the Exposure adjustment?
    By the way, in my limited tests of this I was just using a standard RGB file in 16-bit mode - nothing fancy like 32-bit or LAB or anything like that.  Also, Photoshop CS6 Extended.  Both 32- and 64-bit versions show the same behavior.
    Thanks.

    The differing gamma adjustment results also occur in the OS X version of Ps 13.0.1
    The situation is worse than you realize, Dennis. Test with a linear grayscale gradient in 16-bit or 8-bit RGB mode instead of arbitrary images. Remember to view at 100% zoom for an accurate display.
    Gamma adjustments of less than 1 performed by Levels adjustment layer and Exposure adjustment layer do differ but to a less obvious extent than when the adjustment is greater than 1. Differences can be seen in histograms, and low level differences when differencing layers can be made more obvious by adding an Exposure adjustment layer with the exposure increased.
    You'll get further different results by using the gamma adjustment in the "Exposure and Gamma" method of Image > Adjustment > HDR Toning. Notice that the gamma value there has to be specified as the inverse of that in Levels and Exposure.
    I haven't bothered to calculate which, if any, of the three gamma adjustment controls gives correct results because that is Adobe's responsibility.
    It's quite ridiculous that a common routine giving consistent and correct results isn't being used for all these gamma adjustments. Code re-use makes software more robust, simpler to test, simpler to correct, leaner and overall easier to manage. But what do I know.

  • Field Only and Inversion

    Hello SDNers,
    I would like to ask you in the datasource there are 2 option si would liek to know when are they used.
    1) Inversion
    2) Field Only
    And Field only does this need to be checked when its custom enhancement t structure or can be checked for other reasons aswell.Please explain.
    Thanks.
    Krrish.

    Hi,
    usually inversion feature is useful for DS carrying customized Keyfigures which has -ve sign
    before loading to BW ,the value will be mulitplied by -1 and goes to BW
    check this SAP note:
    Inversion
    Reverse postings are possible for customer-defined key figures. For this reason, inversion is only possible for certain transaction data DataSources. These include DataSources that have a field that is indicated as an inversion field, for example, the field update mode in the DataSource 0FI_AP_3. If this field has a value, then the data records are interpreted as reverse records in BW.
    Set the Inversion indicator if you want to carry out a reverse posting for a customer-defined field (key figure). The value of the key figure is then transferred in inverted form (multiplied by –1) into BW.
    filed only..
    it is useful when you are enhancing the DS with the userdefined fields and has wriiten the code in CMOD
    Sap note:
    Field only known in exit
    You can enhance data by extending the extract structure for a DataSource using fields in append structures.
    The indicator Field only known in Exit is set for fields of an append structure. In other words, by default these fields are not passed onto the extractor from the field list and selection table.
    Deselect the indicator Field Only Known in Exit to enable the Service API to pass on the append structure field to the extractor together with the fields of the delivered extract structures in the field list as well as in the selection table.
    Cheers,
    Swapna.G

  • Question on reading one character at a time.

    Hi. I am assigned a program where I have to read a series of bits (for example: 01010101). Using this I have to make a "graph out of it". The way I am supposed to make a graph is as follows:
    Each bit interval will be represented in the output as a field taht is two characters wide.
    The value of the signal is represented using either + (to represent +voltage) or - (to represent - voltage) and is always the second character in the output field.
    The first character in the output field is either:
    ' . ' = to indicate no change from the previous signal value or
    ' / ' = to indicate a negative to positive transition or else
    ' \ ' = to indicate a positive to negative transition
    Example for input: 01010101 and the output would be . + \ - . - / + \ - . - / + . + \ - / +
    The code that I got so far is that I read the input from the command line as a argument which I know is nothing but I would just like to know how to read the character one by one and make a graph which is totally boggling my mind because I have no idea how I can do it. Thank you for your help.
    import javax.swing.*;
    import java.awt.*;
    import java.awt.event.*;
    public class Encoder
         public static void main(String[] args)
              int b = Integer.parseInt(args[0].trim());
              System.out.println("You spit out --> "+b);

    Alright I sorta got what you were sayin'. The code that I have now is:
    import javax.swing.*;
    import java.awt.*;
    import java.awt.event.*;
    public class Encoder
         public static void main(String[] args)
              String toEncode = String.valueOf(args[0]);
              StringBuffer result = new StringBuffer();
              char lastChar = toEncode.charAt(0);
              char curChar = '0';
              char lastSign = '+';
              int length = toEncode.length();
              for (int i = 0; i < length; i++)
              curChar = toEncode.charAt(i);
              if (curChar != lastChar)
              if (curChar == '0')
              result.append("\\-");
              lastSign = '-';
              else
              result.append("/+");
              lastSign = '+';
              lastChar = curChar;
              else
              result.append(".");
              result.append(lastSign);
              System.out.println("You spit out --> "+result);
    But it doens't work according to what I want it to do. What I need it to do is the following: Lets say we have the input of 01010101, the result we will get is ". + \ - . - / + \ - . - / + . + \ - / +". The reason for this is because of the following: The graph starts on the v all the time. When there is a 0 bit there is no change and when there is a 1 bit there is an inversion of the voltage level so since we started with a 0 bit at v, when we hit 1 bit we would make a inversion to -v and when we hit 0 bit there would be no change. I don't know of what I said is clear to you or not. For this program, what it does for the input of 01010101, the output is
    " . + / + \ - / + \ - / + \ - / + ". Thank you very much.

  • Generic Extraction (or) How to use table in R/3 system as datasource in BW?

    Hi all,
    Hope all are having a great day
    Can any1 tell me the steps, for Generic Extraction.
    It will be very helpful, if the steps are as much as simpler as posible.
    I know to create a simple cube in BW.
    I have this much knowledge, depending on this can any1 tell me the steps for Generic Extraction from R/3.
    examples wud be vry useful
    Regards,
    Sourav

    hi,
    Maintaining Generic DataSources 
    Use
    Independently of application, you can create and maintain generic DataSources for transaction data, master data attributes or texts from any kinds of transparent tables, database views, InfoSets of the SAP query or using a function module. As a result, you can make use of the generic extraction of data.
    Procedure
    Creating a Generic DataSource(RSO2)
           1.      Select the DataSource type and give it a technical name.
           2.      Choose Create.
    The creating a generic DataSource screen appears.
           3.      Choose an application component to which the DataSource is to be assigned.
           4.      Enter the descriptive texts. You can choose any text.
           5.      Choose from which datasets the generic DataSource is to be filled.
                                a.      Choose Extraction from View, if you want to extract data from a transparent table or a database view. Enter the name of the table or the database view.
    After generation, you get a DataSource whose extract structure is congruent with the database view or the transparent table view.
    For more information about creating and maintaining database views and tables, see the ABAP Dictionary Documentation.
                                b.      Choose Extraction from Query, if you want to use a SAP query InfoSet as the data source. Select the required InfoSet from the InfoSet catalog.
    Notes on Extraction Using SAP Query
    After generation, you now have a DataSource whose extract structure matches the InfoSet.
    For more information about maintaining the InfoSet, see the System Administration documentation.
                                c.      Choose Extraction using FM, if you want to extract data using a function module. Enter the function module and extract structure.
    The data must be transferred by the function module in an interface table E_T_DATA.
    Interface Description and Extraction Process Flow
    For information about the function library, see the ABAP Workbench: Tools documentation.
                                d.      With texts, you also have the option of extraction from domain fixed values.
           6.      Maintain the settings for delta transfer where appropriate.
           7.      Choose Save.
    When extracting, look at SAP Query: Assigning to a User Group.
    Note when extracting from a transparent table or view:
    If the extract structure contains a key figure field, that references to a unit of measure or currency unit field, this unit field must appear in the same extract structure as the key figure field.
    A screen appears in which you can edit the fields of the extract structure.
           8.      Editing the DataSource:
    &#61601;        Selection
    When scheduling a data  request in the BW Scheduler, you can enter the selection criteria for the data transfer. For example, you may want to determine that data requests are only to apply to data from the previous month.
    If you set the Selection indicator for a field within the extract structure, the data for this field is transferred in correspondence with the selection criteria in the scheduler.
    &#61601;        Hide field
    You should set this indicator to exclude an extract structure field from the data transfer. As a result of your action, the field is no longer made available in BW when setting the transfer rules and generating the transfer structure.
    &#61601;        Inversion
    Reverse postings are possible for customer-defined key figures. For this reason, inversion is only possible for certain transaction data DataSources. These include DataSources that have a field that is indicated as an inversion field, for example, the field update mode in the DataSource 0FI_AP_3. If this field has a value, then the data records are interpreted as reverse records in BW.
    Set the Inversion indicator if you want to carry out a reverse posting for a customer-defined field (key figure). The value of the key figure is then transferred in inverted form (multiplied by –1) into BW.
    &#61601;        Field only known in exit
    You can enhance data by extending the extract structure for a DataSource using fields in append structures.
    The indicator Field only known in Exit is set for fields of an append structure. In other words, by default these fields are not passed onto the extractor from the field list and selection table.
    Deselect the indicator Field Only Known in Exit to enable the Service API to pass on the append structure field to the extractor together with the fields of the delivered extract structures in the field list as well as in the selection table.
    9. Choose DataSource ® Generate.
    The DataSource is now saved in the source system.
    Maintaining Generic DataSources
    •        Change the DataSource
    To change a generic DataSource, in the initial screen of DataSource maintenance, enter the name of the DataSource and choose Change.
    You can change the assignment of a DataSource to an application component as well as the texts of a DataSource. Double-clicking on the name of the table, view, InfoSet or extract structure takes you to the appropriate maintenance screen. Here you can make changes required to add new fields. You can fully swap transparent tables and database views, but not InfoSets. If you return to the DataSource maintenance and choose Create, the screen for editing a DataSource appears. To save the DataSource in the SAP source system, choose DataSource  ® Generate.
    If you want to test extraction in the source system independently of a BW system, choose DataSource  ®  Test Extraction.
    •        Delta DataSource
    In the Change Generic DataSource screen, you can delete any DataSources that are no longer relevant. If you are extracting data from an InfoSet, delete the associated query. If you want to delete a DataSource, this must not be connected to a BW system.
    For more information about extracting using SAP Query, see Extraction using the SAP Query.
    hope this helps.
    assign point if so
    partha

  • Generic example

    Please tell me a generic datasource with scenario. I want to learn how to put join condition.

    Hi deepthi,
    Independently of application, you can create and maintain generic DataSources for transaction data, master data attributes or texts from any kinds of transparent tables, database views, InfoSets of the SAP query or using a function module. As a result, you can make use of the generic extraction of data.
    Procedure
    Creating a Generic DataSource
    1. Select the DataSource type and give it a technical name.
    2. Choose Create.
    The creating a generic DataSource screen appears.
    3. Choose an application component to which the DataSource is to be assigned.
    4. Enter the descriptive texts. You can choose any text.
    5. Choose from which datasets the generic DataSource is to be filled.
    a. Choose Extraction from View, if you want to extract data from a transparent table or a database view. Enter the name of the table or the database view.
    After generation, you get a DataSource whose extract structure is congruent with the database view or the transparent table view.
    For more information about creating and maintaining database views and tables, see the ABAP Dictionary Documentation.
    b. Choose Extraction from Query, if you want to use a SAP query InfoSet as the data source. Select the required InfoSet from the InfoSet catalog.
    Notes on Extraction Using SAP Query
    After generation, you now have a DataSource whose extract structure matches the InfoSet.
    For more information about maintaining the InfoSet, see the System Administration documentation.
    c. Choose Extraction using FM, if you want to extract data using a function module. Enter the function module and extract structure.
    The data must be transferred by the function module in an interface table E_T_DATA.
    Interface Description and Extraction Process Flow
    For information about the function library, see the ABAP Workbench: Tools documentation.
    d. With texts, you also have the option of extraction from domain fixed values.
    6. Maintain the settings for delta transfer where appropriate.
    7. Choose Save.
    When extracting, look at SAP Query: Assigning to a User Group.
    Note when extracting from a transparent table or view:
    If the extract structure contains a key figure field, that references to a unit of measure or currency unit field, this unit field must appear in the same extract structure as the key figure field.
    A screen appears in which you can edit the fields of the extract structure.
    8. Editing the DataSource:
    &#61601; Selection
    When scheduling a data request in the BW Scheduler, you can enter the selection criteria for the data transfer. For example, you may want to determine that data requests are only to apply to data from the previous month.
    If you set the Selection indicator for a field within the extract structure, the data for this field is transferred in correspondence with the selection criteria in the scheduler.
    Hide field&#61601;
    You should set this indicator to exclude an extract structure field from the data transfer. As a result of your action, the field is no longer made available in BW when setting the transfer rules and generating the transfer structure.
    &#61601; Inversion
    Reverse postings are possible for customer-defined key figures. For this reason, inversion is only possible for certain transaction data DataSources. These include DataSources that have a field that is indicated as an inversion field, for example, the field update mode in the DataSource 0FI_AP_3. If this field has a value, then the data records are interpreted as reverse records in BW.
    Set the Inversion indicator if you want to carry out a reverse posting for a customer-defined field (key figure). The value of the key figure is then transferred in inverted form (multiplied by –1) into BW.
    Field only&#61601; known in exit
    You can enhance data by extending the extract structure for a DataSource using fields in append structures.
    The indicator Field only known in Exit is set for fields of an append structure. In other words, by default these fields are not passed onto the extractor from the field list and selection table.
    Deselect the indicator Field Only Known in Exit to enable the Service API to pass on the append structure field to the extractor together with the fields of the delivered extract structures in the field list as well as in the selection table.
    9. Choose DataSource ® Generate.
    The DataSource is now saved in the source system.
    Maintaining Generic DataSources
    • Change the DataSource
    To change a generic DataSource, in the initial screen of DataSource maintenance, enter the name of the DataSource and choose Change.
    You can change the assignment of a DataSource to an application component as well as the texts of a DataSource. Double-clicking on the name of the table, view, InfoSet or extract structure takes you to the appropriate maintenance screen. Here you can make changes required to add new fields. You can fully swap transparent tables and database views, but not InfoSets. If you return to the DataSource maintenance and choose Create, the screen for editing a DataSource appears. To save the DataSource in the SAP source system, choose DataSource ® Generate.
    If you want to test extraction in the source system independently of a BW system, choose DataSource ® Test Extraction.
    • Delta DataSource
    In the Change Generic DataSource screen, you can delete any DataSources that are no longer relevant. If you are extracting data from an InfoSet, delete the associated query. If you want to delete a DataSource, this must not be connected to a BW system.
    For more information about extracting using SAP Query, see Extraction using the SAP Query.
    Plz assign points if helpful. This is the only way to say thanks.
    And give me ur ID i send u some helpful documents...
    Regards
    Rakesh Jangir

  • Generic Extraction business Requirement, through function module,

    Generic Extraction business Requirement, specifically through function module and source code in function module.

    Dear Karthik,
    Go to transaction SBIW -> Generic Datasource -> Maintain Generic Datasources -> Choose Master/Transaction Data -> Maintain proper entries (Application Component, Descriptions) -> Extraction by FM if you want to extract using FM.
    Maintaining Generic DataSources - Independently of application, you can create and maintain generic DataSources for transaction data, master data attributes or texts from any kinds of transparent tables, database views, InfoSets of the SAP query or using a function module. As a result, you can make use of the generic extraction of data.
    Creating a Generic DataSource
           1.      Select the DataSource type and give it a technical name.
           2.      Choose Create. The creating a generic DataSource screen appears.
           3.      Choose an application component to which the DataSource is to be assigned.
           4.      Enter the descriptive texts. You can choose any text.
           5.      Choose from which datasets the generic DataSource is to be filled.
                                a.      Choose Extraction from View, if you want to extract data from a transparent table or a database view. Enter the name of the table or the database view.
    After generation, you get a DataSource whose extract structure is congruent with the database view or the transparent table view.
    For more information about creating and maintaining database views and tables, see the ABAP Dictionary Documentation.
                                b.      Choose Extraction from Query, if you want to use a SAP query InfoSet as the data source. Select the required InfoSet from the InfoSet catalog.
    After generation, you now have a DataSource whose extract structure matches the InfoSet.
    For more information about maintaining the InfoSet, see the System Administration documentation.
                                c.      Choose Extraction using FM, if you want to extract data using a function module. Enter the function module and extract structure.
    The data must be transferred by the function module in an interface table E_T_DATA.
    For information about the function library, see the ABAP Workbench: Tools documentation.
                                d.      With texts, you also have the option of extraction from domain fixed values.
    Maintain the settings for delta transfer where appropriate.
           7.      Choose Save.
    Note when extracting from a transparent table or view:
    If the extract structure contains a key figure field, that references to a unit of measure or currency unit field, this unit field must appear in the same extract structure as the key figure field.
    A screen appears in which you can edit the fields of the extract structure.
           8.      Editing the DataSource:
           Selection
    When scheduling a data  request in the BW Scheduler, you can enter the selection criteria for the data transfer. For example, you may want to determine that data requests are only to apply to data from the previous month.
    If you set the Selection indicator for a field within the extract structure, the data for this field is transferred in correspondence with the selection criteria in the scheduler.
           Hide field
    You should set this indicator to exclude an extract structure field from the data transfer. As a result of your action, the field is no longer made available in BW when setting the transfer rules and generating the transfer structure.
           Inversion
    Reverse postings are possible for customer-defined key figures. For this reason, inversion is only possible for certain transaction data DataSources. These include DataSources that have a field that is indicated as an inversion field, for example, the field update mode in the DataSource 0FI_AP_3. If this field has a value, then the data records are interpreted as reverse records in BW.
    Set the Inversion indicator if you want to carry out a reverse posting for a customer-defined field (key figure). The value of the key figure is then transferred in inverted form (multiplied by –1) into BW.
           Field only known in exit
    You can enhance data by extending the extract structure for a DataSource using fields in append structures.
    The indicator Field only known in Exit is set for fields of an append structure. In other words, by default these fields are not passed onto the extractor from the field list and selection table.
    Deselect the indicator Field Only Known in Exit to enable the Service API to pass on the append structure field to the extractor together with the fields of the delivered extract structures in the field list as well as in the selection table.
    9. Choose DataSource -> Generate.
    The DataSource is now saved in the source system.
    Maintaining Generic DataSources
    ·        Change the DataSource
    To change a generic DataSource, in the initial screen of DataSource maintenance, enter the name of the DataSource and choose Change.
    You can change the assignment of a DataSource to an application component as well as the texts of a DataSource. Double-clicking on the name of the table, view, InfoSet or extract structure takes you to the appropriate maintenance screen. Here you can make changes required to add new fields. You can fully swap transparent tables and database views, but not InfoSets. If you return to the DataSource maintenance and choose Create, the screen for editing a DataSource appears. To save the DataSource in the SAP source system, choose DataSource  -> Generate.
    If you want to test extraction in the source system independently of a BW system, choose DataSource  ->  Test Extraction.
    ·        Delta DataSource
    In the Change Generic DataSource screen, you can delete any DataSources that are no longer relevant. If you are extracting data from an InfoSet, delete the associated query. If you want to delete a DataSource, this must not be connected to a BW system.
    Also visit :[Data Extraction from SAP Source System | http://help.sap.com/saphelp_nw04/helpdata/en/28/4c553c42360a40e10000000a114084/content.htm]
    Regards,
    Naveen.

  • How to  extract  master data  attribute from  r/3 to bw give steps details

    how to  extract  master data  attribute from  r/3 to bw give steps details screenshots

    Hi
    Go through the below process to extract Master Data Attribute from R/3
    Hi,
    Maintaining Generic DataSources
    Use
    Regardless of the application, you can create and maintain generic DataSources for transaction data, master data attributes or texts from any transparent table, database view or SAP Query InfoSet, or using a function module. This allows you to extract data generically.
    Procedure
    Creating Generic DataSources
    1. Select the DataSource type and specify a technical name.
    2. Choose Create.
    The screen for creating a generic DataSource appears.
    3. Choose the application component to which you want to assign the DataSource.
    4. Enter the descriptive texts. You can choose any text.
    5. Select the datasets from which you want to fill the generic DataSource.
    a. Choose Extraction from View if you want to extract data from a transparent table or a database view. Enter the name of the table or the database view.
    After you generate the DataSource, you have a DataSource with an extraction structure that corresponds to the database view or transparent table.
    For more information about creating and maintaining database views and tables, see the ABAP Dictionary Documentation.
    b. Choose Extraction from Query if you want to use a SAP Query InfoSet as the data source. Select the required InfoSet from the InfoSet catalog.
    Notes on Extraction Using SAP Query
    After you generate the DataSource, you have a DataSource with an extraction structure that corresponds to the InfoSet.
    For more information about maintaining the InfoSet, see the System Administration documentation.
    c. Choose Extraction Using FM if you want to extract data using a function module. Enter the function module and extraction structure.
    The data must be transferred by the function module in an interface table E_T_DATA.
    Interface Description and Extraction Process
    For information about the function library, see the ABAP Workbench: Tools documentation.
    d. With texts you also have the option of extracting from fixed values for domains.
    6. Maintain the settings for delta transfer, as required.
    7. Choose Save.
    When performing extraction, note SAP Query: Assigning to a User Group.
    Note when extracting from a transparent table or view:
    If the extraction structure contains a key figure field that references a unit of measure or a currency unit field, this unit field has to be included in the same extraction structure as the key figure field.
    A screen appears on which you can edit the fields of the extraction structure.
    8. Edit the DataSource:
    &#9675; Selection
    When you schedule a data request in the BI scheduler, you can enter the selection criteria for the data transfer. For example, you can determine that data requests are only to apply to data from the previous month.
    If you set the Selection indicator for a field within the extraction structure, the data for this field is transferred in correspondence with the selection criteria in the scheduler.
    &#9675; Hide field
    You set this indicator to exclude an extraction structure field from the data transfer. The field is no longer available in BI when you set the transfer rules or generate the transfer structure.
    &#9675; Inversion
    Reverse postings are possible for customer-defined key figures. Therefore inversion is only active for certain transaction data DataSources. These include DataSources that have a field that is marked as an inversion field, for example, the update mode field in DataSource 0FI_AP_3. If this field has a value, the data records are interpreted as reverse records in BI.
    If you want to carry out a reverse posting for a customer-defined field (key figure), set the Inversion indicator. The value of the key figure is transferred to BI in inverted form (multiplied by –1).
    &#9675; Field only known in exit
    You can enhance data by extending the extraction structure for a DataSource by adding fields in append structures.
    The Field Only Known in Exit indicator is set for the fields of an append structure; by default these fields are not passed to the extractor from the field list and selection table.
    Deselect the Field Only Known in Exit indicator to enable the Service API to pass on the append structure field to the extractor together with the fields of the delivered extract structures in the field list and in the selection table.
    9. Choose DataSource ® Generate.
    The DataSource is saved in the source system.
    Maintaining Generic DataSources
    &#9679; Change DataSource
    To change a generic DataSource, in the initial screen of DataSource maintenance, enter the name of the DataSource and choose Change.
    You can change the assignment of a DataSource to an application component or change the texts of a DataSource. Double-click on the name of the table, view, InfoSet or extraction structure to get to the appropriate maintenance screen. Here you make the changes to add new fields. You can also completely swap transparent tables and database views, though this is not possible with InfoSets. Return to DataSource maintenance and choose Create. The screen for editing a DataSource appears. To save the DataSource in the SAP source system, choose DataSource ® Generate.
    If you want to test extraction in the source system independently of a BI system, choose DataSource ® Test Extraction.
    &#9679; Delta DataSource
    On the Change Generic DataSource screen, you can delete any DataSources that are no longer relevant. If you are extracting data from an InfoSet, delete the corresponding query. If you want to delete a DataSource, make sure it is not connected to a BI system.
    NR

  • About Generic Extraction

    Hi all,
                  I would like to have some links r docs to mail about DB view extraction. I am stuck in it. I would like to know it from  how to create a view and till how do i recognize a delta field in the given 2 tables.
    my mail ID is [email protected]
    Thanks and regards.

    hi pradeep,
      Maintaining Generic DataSources 
    Use
    Independently of application, you can create and maintain generic DataSources for transaction data, master data attributes or texts from any kinds of transparent tables, database views, InfoSets of the SAP query or using a function module. As a result, you can make use of the generic extraction of data.
    Procedure
    Creating a Generic DataSource
           1.      Select the DataSource type and give it a technical name.
           2.      Choose Create.
    The creating a generic DataSource screen appears.
           3.      Choose an application component to which the DataSource is to be assigned.
           4.      Enter the descriptive texts. You can choose any text.
           5.      Choose from which datasets the generic DataSource is to be filled.
                                a.      Choose Extraction from View, if you want to extract data from a transparent table or a database view. Enter the name of the table or the database view.
    After generation, you get a DataSource whose extract structure is congruent with the database view or the transparent table view.
    For more information about creating and maintaining database views and tables, see the ABAP Dictionary Documentation.
                                b.      Choose Extraction from Query, if you want to use a SAP query InfoSet as the data source. Select the required InfoSet from the InfoSet catalog.
    Notes on Extraction Using SAP Query
    After generation, you now have a DataSource whose extract structure matches the InfoSet.
    For more information about maintaining the InfoSet, see the System Administration documentation.
                                c.      Choose Extraction using FM, if you want to extract data using a function module. Enter the function module and extract structure.
    The data must be transferred by the function module in an interface table E_T_DATA.
    Interface Description and Extraction Process Flow
    For information about the function library, see the ABAP Workbench: Tools documentation.
                                d.      With texts, you also have the option of extraction from domain fixed values.
           6.      Maintain the settings for delta transfer where appropriate.
           7.      Choose Save.
    When extracting, look at SAP Query: Assigning to a User Group.
    Note when extracting from a transparent table or view:
    If the extract structure contains a key figure field, that references to a unit of measure or currency unit field, this unit field must appear in the same extract structure as the key figure field.
    A screen appears in which you can edit the fields of the extract structure.
           8.      Editing the DataSource:
    &#61601;        Selection
    When scheduling a data  request in the BW Scheduler, you can enter the selection criteria for the data transfer. For example, you may want to determine that data requests are only to apply to data from the previous month.
    If you set the Selection indicator for a field within the extract structure, the data for this field is transferred in correspondence with the selection criteria in the scheduler.
    &#61601;        Hide field
    You should set this indicator to exclude an extract structure field from the data transfer. As a result of your action, the field is no longer made available in BW when setting the transfer rules and generating the transfer structure.
    &#61601;        Inversion
    Reverse postings are possible for customer-defined key figures. For this reason, inversion is only possible for certain transaction data DataSources. These include DataSources that have a field that is indicated as an inversion field, for example, the field update mode in the DataSource 0FI_AP_3. If this field has a value, then the data records are interpreted as reverse records in BW.
    Set the Inversion indicator if you want to carry out a reverse posting for a customer-defined field (key figure). The value of the key figure is then transferred in inverted form (multiplied by –1) into BW.
    &#61601;        Field only known in exit
    You can enhance data by extending the extract structure for a DataSource using fields in append structures.
    The indicator Field only known in Exit is set for fields of an append structure. In other words, by default these fields are not passed onto the extractor from the field list and selection table.
    Deselect the indicator Field Only Known in Exit to enable the Service API to pass on the append structure field to the extractor together with the fields of the delivered extract structures in the field list as well as in the selection table.
    9. Choose DataSource ® Generate.
    The DataSource is now saved in the source system.
    Maintaining Generic DataSources
    •        Change the DataSource
    To change a generic DataSource, in the initial screen of DataSource maintenance, enter the name of the DataSource and choose Change.
    You can change the assignment of a DataSource to an application component as well as the texts of a DataSource. Double-clicking on the name of the table, view, InfoSet or extract structure takes you to the appropriate maintenance screen. Here you can make changes required to add new fields. You can fully swap transparent tables and database views, but not InfoSets. If you return to the DataSource maintenance and choose Create, the screen for editing a DataSource appears. To save the DataSource in the SAP source system, choose DataSource  ® Generate.
    If you want to test extraction in the source system independently of a BW system, choose DataSource  ®  Test Extraction.
    •        Delta DataSource
    In the Change Generic DataSource screen, you can delete any DataSources that are no longer relevant. If you are extracting data from an InfoSet, delete the associated query. If you want to delete a DataSource, this must not be connected to a BW system.
    For more information about extracting using SAP Query, see Extraction using the SAP Query.
    if helpfull assign points
    regards,
    yunus

  • How to write an inverse routine for an info object at field level.

    Hi All,
    Our requirement is as follows:
    Need to populate 0MAT_PLANT in a virtual provider. But during query performance it is like -
    If someone were to add a filter to the BW query on 0MAT_PLANT, it would take the system awhile to search the APO database for that 18 CHAR material number because the data in APO is stored differently (40 CHARs).  The point of the  inverse routine is to convert the 18 CHAR to be 40 CHAR for those times when someone selects on 0MAT_PLANT.  That way, the field types match and finding the data in APO is much quicker.
    Hence if we need selection on the selection scree of the query for 0MAT_PLANT, we are trying for inverse routine which will convert 18 chars to 40 chars in the query level and the performance will be quicker.
    See, 0MAT_PLANT is of 18 Char length. We are mapping it from ZMATNR in source which is of 40 chars. Thus initially in the field routine we will write a code to convert 0MAT_PLANT to 18 from 40.
    Below is the code and the place we now we also need to write inverse routine to convert it to 40 from 18 chars.
    *****Code to convert from 40 chars to 18******
    *In APO if the material contains all integers values the material will
    * come over as a 40 byte field.  It needs to be shortened.
      IF SOURCE_FIELDS-/BIC/ZMATNR CO '0123456789'.
        short_material = SOURCE_FIELDS-/BIC/ZMATNR+22(18).
    *In APO if the material contains any character fields the material will
    * not be zero filled and will be left alligned. Take the 1st 18 bytes.
      ELSE.
        short_material = SOURCE_FIELDS-/BIC/ZMATNR(18).
      ENDIF.
    *add leading zeros to numeric only value
      IF short_material CO '0123456789 '.
         w_num18 = short_material.
         short_material = w_num18.
      ENDIF.
      RESULT = short_material.
    *$*$ end of routine -
    ***********here the iverse routine need to write************
    *       Method invert_0MATERIAL
    *       This subroutine needs to be implemented only for direct access
    *       (for better performance) and for the Report/Report Interface
    *       (drill through).
    *       The inverse routine should transform a projection and
    *       a selection for the target to a projection and a selection
    *       for the source, respectively.
    *       If the implementation remains empty all fields are filled and
    *       all values are selected.
      METHOD invert_0MATERIAL.
    *$*$ begin of inverse routine - insert your code only below this line*-*... "insert your code here
    Here you would write logic in 0MAT_PLANT to do the opposite of the above,
    convert 18 back to 40 characters.
    *$*$ end of inverse routine - insert your code only before this line *-*
      The articulated form above in RED says that the subroutine i.e. the inverse routine is implemented for direct access and report to report interface.
    Could anybody please help me or let me know any idea related to this.

    Hi All,
    Our requirement is as follows:
    Need to populate 0MAT_PLANT in a virtual provider. But during query performance it is like -
    If someone were to add a filter to the BW query on 0MAT_PLANT, it would take the system awhile to search the APO database for that 18 CHAR material number because the data in APO is stored differently (40 CHARs).  The point of the  inverse routine is to convert the 18 CHAR to be 40 CHAR for those times when someone selects on 0MAT_PLANT.  That way, the field types match and finding the data in APO is much quicker.
    Hence if we need selection on the selection scree of the query for 0MAT_PLANT, we are trying for inverse routine which will convert 18 chars to 40 chars in the query level and the performance will be quicker.
    See, 0MAT_PLANT is of 18 Char length. We are mapping it from ZMATNR in source which is of 40 chars. Thus initially in the field routine we will write a code to convert 0MAT_PLANT to 18 from 40.
    Below is the code and the place we now we also need to write inverse routine to convert it to 40 from 18 chars.
    *****Code to convert from 40 chars to 18******
    *In APO if the material contains all integers values the material will
    * come over as a 40 byte field.  It needs to be shortened.
      IF SOURCE_FIELDS-/BIC/ZMATNR CO '0123456789'.
        short_material = SOURCE_FIELDS-/BIC/ZMATNR+22(18).
    *In APO if the material contains any character fields the material will
    * not be zero filled and will be left alligned. Take the 1st 18 bytes.
      ELSE.
        short_material = SOURCE_FIELDS-/BIC/ZMATNR(18).
      ENDIF.
    *add leading zeros to numeric only value
      IF short_material CO '0123456789 '.
         w_num18 = short_material.
         short_material = w_num18.
      ENDIF.
      RESULT = short_material.
    *$*$ end of routine -
    ***********here the iverse routine need to write************
    *       Method invert_0MATERIAL
    *       This subroutine needs to be implemented only for direct access
    *       (for better performance) and for the Report/Report Interface
    *       (drill through).
    *       The inverse routine should transform a projection and
    *       a selection for the target to a projection and a selection
    *       for the source, respectively.
    *       If the implementation remains empty all fields are filled and
    *       all values are selected.
      METHOD invert_0MATERIAL.
    *$*$ begin of inverse routine - insert your code only below this line*-*... "insert your code here
    Here you would write logic in 0MAT_PLANT to do the opposite of the above,
    convert 18 back to 40 characters.
    *$*$ end of inverse routine - insert your code only before this line *-*
      The articulated form above in RED says that the subroutine i.e. the inverse routine is implemented for direct access and report to report interface.
    Could anybody please help me or let me know any idea related to this.

  • Restrict FI postings from FB60 at vendor account group level

    Hi Experts,
    We have a requirement whereby the authorization for posting from T-Code FB60 should be controlled at vendor account group level (LFA1-KTOKK).
    We are also fine with restrictions at vendor master authorization group level (LFA1-BEGRU/BRGRU).
    So a particular user should be able to post to a vendor in acct grp A but not acct grp B from FB60.
    However, it seems that T-Code FB60 checks only objects BKPFBLA, F_BKPF_BUK, F_BKPF_GSB, F_BKPF_KOA.
    Neither of the above 2 fields are available in these 4 objects.
    In case you have a solution for restricting FB60 postings, please reply.

    Hi.
    In vendor maser data you can maintain LFB1-BEGRU='vendor group', and check it in F_BKPF_BEK-BRGRU

  • Posting Level 01 documents allow cross company postings - unexpected

    hi,
    Previously users could not enter a PL01 document that crossed companies.
    Now they can.
    I had previously thought that this was not possible for PL01 but what is happening is
    when they enter cross-company postings (2 lines, one each to a different cons unit)
    the system creates 2 documents,
    with 2 balancing entry lines (one to each unit) to the clearing item
    - just as can happen when a PL20 or PL30 manual posting is to the same company but cross-profit centres.
    So my question;
    is this normal behaviour in BCS?
    was this always possible but the users just hadn't achieved it until now
    NB they are adamant that this was not possible previously, until the Support Packs were implemented sometime last year
    Finally, is there a way to stop it from happening?

    Concur with Dan.
    Most likely, that you've met the 2nd case: the DocType with configured  clearing ConsUnit was  attached to manual entry task. It might be not easily seen. Just check it out and remove if find.
    Edited by: Eugene Khusainov on Jan 28, 2010 11:13 PM

  • Inversions at posting level 20

    Hi Greg,
    i like the look of your blog and I will read it when I get some more time (probably after my current project).
    At first glance I have a question for you, why would the following impact the I/S?
    Dr intercompany payable                110
    Cr intercompany receivable            100
    Cr intercompany netting                  10
    (I assume that yourfor a payables/receviables elimination your IC difference account (intercompany netting) would be in the Balance Sheet).
    However, I accept that the same example with IC Income v IC expense would cause the impact on Retained earnigns prior year at year end.
    This is a good reason make sure that IC is reviewed at year end, especially where the amounts are considered "material".
    I haven't read the whole example yet but surely regardless of whether the IC is matched before year end or after year end, the net reserves (prior year + current year) will be correct?

    Hi Greg,
    I have the same question as TheScotsman: why you consider impact on I/S of such entries (and their reversals) as A/R - A/P?
    Impact (during posting and during inversion) may be considered in my example from the other recent discussion:
    Depreciation accrual (B/S) - Depreciation expense (I/S)
    i'm not sure how my eliminations from prior year "disappear" and don't get inverted with the the new FY.
    May happen if you used (or configured and do not use) special periods (13-16 for K4 FYV). Inversion might be scheduled in one of this special periods in which you didin't run period inizialization. 
    i also have doubts on netting as it may contain more than actual float. e.g. foreign exchange translation difference.
    This C/T difference is a part of the real difference in GC.

  • Document type with posting level 12 not being carryforward

    Hi gurus,
    We are now implementing SEM-BCS 6.0 in the BI 7.0 server.
    We have a document type u201CMIu201D which properties are:
    Posting level: 12
    Balance check: 0 error when balance note equal to zero
    Application: Other
    Posting: Manual posting
    Inversion: No automatic inversion
    The problem is that when we execute the Balance Carryforward in the subsequent year this is the only document type that is not being carryforward.
    Why is this happening?
    Thanks for your help.
    Best regards.

    This is by design
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/0c/ab0240536fe369e10000000a155106/content.htm
    "Data records for preparatory postings for consolidation group changes are neither translated nor carried forward."
    I'll try an example...
    Company A is sold from company 1 to company 2 in June (EoP)
    For periods 0 - 6:
    BCS reports company A's balance sheet under company 1
    BCS reports company A's income statement under company 1
    starting period 7
    BCS reports company A's balance sheet under company 2
    BCS reports company A's 0 - 6 income statement under company 1
    BCS reports company A's 7 income statement under company 2
    this is managed through the posting level 02 12 and 22 document types, as well as PL30 if using CoI.
    Assuming the period of first consolidation and period of divestiture were set correctly in the groups for company 1 and company 2, BCS wants to read all 0 - 6 data under group 1 and all 7 + data under group 2.  This is obviously incorrect from an accounting standpoint and the PCC postings correct that.
    So BCS books a PL02/12/22 in group 1 to zero out the balance sheet.  It then books another set of entries in group 2 to write up the entire balance sheet in the new group.
    However, once you get to the end of the year and run your BCF, the entire balance sheet is now sitting in period 0. The system is able to report company A's balance sheet under group 2 withou the aid of the PCC documents.  Therefore, the system does not roll these documents forward into the new year.
    The PCC documents were only required because of the periodic nature of the BCS data storage vs. the LTD nature of the balance sheet for reporting.  Once the full LTD balance is available in a single period, as is the case just after a BCF, the PCC documents are no longer required.
    Anyway, hope that made some sense.  If not, I'd encourange you to create an Excel sheet replicating how BCS stores the data in the cube, perfrom a divestiture, and see why the system is not carrying forward the documents.  This is how I came to understand it.
    Now, if you're doing something "non-standard" with the PL12, all bets are off
    Good luck,
    Chris

Maybe you are looking for

  • I would like upgrade a 16-bit dll that was developed for 16-bit windows to a 32-bit dll

    I have an 16-bit dll library that was used for talking to a DAQ through Labview version 4 for windows 3.1. I would like to upgrade it so that I can make these calls through Labview version 4.0.1(32-bit). Can anybody do it for me Attachments: Megadac.

  • Using iPhone in France

    I will be going to France later this year and wanted to be able to use GPS and offline maps on the iPhone for navigation on streets and the Metro while walking around (I have a 3G ATT iPad, but that is too bulky to carry around while walking). I do n

  • Marketing Planner - PCUI Question

    Within the Marketing Planner, we would like to remove the default values of <b>Campaign Element and Campaign Element Copy</b> from the "New" button of the MKT_PL_OIP toolbar.  Can anyone tell me how this can be done?  Possibly through security or thr

  • Iphoto for free download anywhere ?

    I have just got a new macbook pro to replace my old white macbook. On the new laptop there is no ilife/no iphoto ( have checked applications, finder and spotlight. All I need is something like iphoto 6. Downloads from the camera, easy to store, can t

  • Fireworks CS5 buttons don't export into Dreamweaver S5 correctly

    I'm very new to fireworks, I've created a design layout in Fireworks CS5 which I've sliced up but when I export the design to Dreamweaver CS5 HTML, the buttons which I've created in Fireworks lose their functionality apart form seeing them as a link,