Upper/Lower limit for delta extractor

Hi Experts,
Where can I see the configuration of the upper/lower safety limit for a delta extractor (tcode)?  I would like to determine the configuration of one of our FI extractors.
Regards
Mark

Hi Chandra,
When checking the source system the extractor is extracted using FM RKE_BIW_GET_DATA_API.  When we display the datasource and click on generic delta, we are getting an error "Specified table does not exist."
Forgot to mention this is a SAP delivered extractor for CO-PA.
Regards
Mark

Similar Messages

  • Safety Upper/Lower limit in delta extraction

    hi all
    since i am new,just i want to know
    what is the diff between safety lower limit and upper limit
    and how these are used in delta.
    thankq in advance

    I do see that you are new - but the topic of safety limits has been discussed many a time on the forums - please search the forums before you post...

  • Define upper/lower limits for shipment cost condition

    Hi people, help please!
    How can I define upper/lower limit for shipment cost conditions?.
    The transaction TK11 has the functionality for upper/lower limits, but I can't find how to define it in customizing.
    I follow the path Logistic Execution>Transportation>Pricing>Pricing Control>Define Condition Types, but is not like the transaction for pricing elements in condition types for sales.
    How can I do it?
    Regards.

    The problem is on the class condition import limits.
    I can’t customize upper and lower prices for the shipment cost class condition and i cant find how define it or what else can I do.
    The customizing transaction for shipment cost lass condition is not like sales price class condition, please look this:
    For the shipment cost class condition follow the path SPRO>Logistic Execution>Transportation>Shipment Cost>Pricing>Pricing Control>Define Condition Types.
    For the sales price class condition follow the path SPRO>Sales and Distribution>Basic Function>Pricing>Pricing Control>Define Condition Types, and take a look in Define upper/lower limits for conditions.
    So then, when I go to functional transaction VK11 for the sales price condition y can’t assign an import out of the limits defined. I need the same for shipment cost condition, transaction TK11, but I can’t find where define the limits, as result, user can load any import without limits.
    I hope the explanation is useful.

  • Tolerance Upper & Lower limit in MIRO

    Dear All,
    my scenario is when i am doing MIRO that Vendor bill amount is 1000/- & SAP Amount 990 so i want set tolerance for upper limit 10/- rupees & lower limit for 100/- rupees.
    is it possible & please suggest me what can i do.?
    Thanks
    Sachin Deshmukh

    Hi,
    As per your suggestion i hvae set Activate item Amount check tick For Company Code. After that i set tol key PP for upper 10val & lower 100Val.
    after i create new MIRO & check my scenario but it is not working. its working only lower limit & it shows Warning message.
    its my company csenario.
    please help me.
    Thanks

  • Regd Safety Interval Lower Limit for Generic Delta

    Hi All,
    Safety Interval Upper Limit =1  for a Generic Delta would get Delta based on yesterday's BW data.
    What would Safety Interval Lower Limit would do for a Generic Delta .
    Your inputs please
    Sree

    Hi,
    just a short example:
    you run a init today --> 20070525  (internal date format).
    for the next delta tomorrow the system takes the last extraction date - 1 day so 20070524 for data selection and will store 20070526 as last extraction date and so on.
    This is to make sure that you will get all additional records extracted which were changed or created on each extraction date, but after last extraction. OK, you will get some records twice, but therefore you normally post the data to a ods via overwrite mode and this will take care about the 'real' delta while doing the further posting to the cube.
    Hope this helps
    kind regards
    Siggi

  • How to set upper and lower limit for service notification in SPRO

    Hello everyone,
    Good morning....!!
    I am new to SAP PM and to SCN as well.
    I have a question on Service notification user status.
    I  have notification profile configured in SAP as below:
    Status no      Status          Short text              Lower limit          Upper limit
    5                  REGD          Registered                1                          70
    10                PCKS            Pack sent                  1                          70
    20                APRC            Application received  1                        70
    etc..
    I want the statusesto be set as  navigation should only allow to go back one by one...like from APRC -->PCKS not to REGD.From PCKS -->REGD etc..not vice versa.
    Can enayone explain me to how to set lower and upper limits for these according ot the above requirement.
    for more details please check my attachment.
    Thanks in advance..!!
    Regards,
    Sudha.

    Once you change the status to previous status, just save the order. Then again open the order & try to change the user status.
    Just I made replica of your profile. I could able to change (even without saving the order).

  • Maintaining two values for upper & lower specification for a MIC

    Hi gurus,
    My client requirement is that they want to maintain two values for upper specification and lower specification for a quantitative characteristic.
    For eg. Master inspection characteristic is carbon %
    & for this characteristic they want to maintain values as follows
    lower specification:0.00   upper specification:0.32
    lower specification:0.37   upper specification:0.60
    The requirement is that both these limits should be maintained for the same MIC and system should not allow values between 0.32-0.37
    Is this possible in standard scenario.If possible pls. provide me the solution.
    Thanks in advance.

    No, not possible in standard SAP.  A test can only have one set of limts.
    What you describe sounds more like specs anyway rather then test limits. 
    Your client isn't maintaining specs for materials in MIC's are they?  This would be the least desirable method and not really the way SAP designed it to be.
    Craig

  • Upper Lower Case for Input Fields of ALV

    Hi,
    i have an ALV has some input fields columns. All values of input fields are upper case after entering something into that input fields (etc. airline -> AIRLINE).
    how to add upper lower case control to ALV? (etc. airline -> airline, AIRLINE -> AIRLINE)
    Thanks.

    Dear Narullah,
    The elements of your table consists of data types you can maintain in the SE11.
    The data type are based on a domain which you can maintain in SE11 as well.
    Just go to SE11 and check the domain which is behind the table field. On the tab "Definition" of the domain just checkmark "Lower Case". Afterwards the system does not translate your input to upper case automatically.
    If you use a SAP domain, you need to copy it to customer namespace, set the lower case flag, create a new data type based on your own domain and use it in the structure of your internal table.
    Does this help?
    Regards,
    Hendrik

  • Define Upper and Lower Limit for condition type

    Hi dear All,
    I´ve defined a new condition type with calculation rule = percentage and when I created the entry in the PER column and UoM column the system does not allow me to put any value.
    Does anybody know how to solve this issue?
    Thanks a  lot,
    Petterson

    Once you change the status to previous status, just save the order. Then again open the order & try to change the user status.
    Just I made replica of your profile. I could able to change (even without saving the order).

  • Purchase net price condition - Upper, lower limit!

    Hi SAPients,
    Please help me on this one.
    While creating a PO, I want the system to throw an error when the net price entered in the PO is 10% more or 20% less than the price I have maintained in the Purchasing info record. Is there a way of configuring this somehow? Any other work around or suggestions also welcome. Thank you!
    Thanks and regards,
    Arun

    Hi Arun,
    I think you might have a couple of options here:
    1,Check out T-code OLME   > condition   >define price
    determination   > define limits
    However  here you are required to give a unit of measure, if in a info
    record which has a different unit of measure than here, then the price
    variance check will not performed,
    Perhaps, you may insert several entries for PB00 but with different unit
    of measures
    once the price in info record (me12)exceed the variance limit, error
    message VK 038 will appear .
    2.IMG   >MM-Purchasing  >PO  >Set Tolerance Limits for Price Variance.
    Here you can maintain the varaince limit then in me21n the effective
    price will be checked against the valuation price in mm03, if it exceed
    the tolerence, Effective price higher than material price will be issued,
    However,this check will not perform directly in the me12
    it will be checked in me21n later.
    Hope this helps.
    Best regards,
    Adam.

  • Need for locking system for delta initialization (BW-R3-LO)

    Hello all,
    Could someone please help me with the following,
    Please be kind, don't get impatient for the lengthy post
    1. Do we need to lock the system (or posting-free the system) to do early delta initialization or not? If yes, please explain me how that work?
    2. Someone somewhere mentioned that early delta initialization is not preferable compared to normal delta initialization, even though early delta initialization is advantageous. Why is that so?
    3. Imagine, while scheduling Queued Delta Init or un-serialized V3 delta Init, if I choose certain end date and time (say, 10pm, 12-31-2007) for the records, then all the records till that point would be loaded to setup tables and all the records after that point of time will be moved to extraction queue or update tables. My question is, if this is true why would we ever need to lock the system during setup tables filling?
        If you say the records after that particular time and date (10pm, 12-31-2007) will not be collected in extraction queue and update tables, why don't we do the following
                 a). say, I do full load with end date and time (10pm 12-31-2007)
                 b). Next, I do delta init with start date and time (10pm 12-31-2007) (this time I lock the postings)
             If we do this way, we can actually reduce the down time of the system. Is my conclusion right?
             If you say it's not practicable as some transactions' saving time differs from time stamp and some transactions' delta is even measured by pointer.......if this is the case we can use Delta offset. What do you say about this?
    4. How this scenario differs to early delta initialization?
    Your responses would be greatly appreciated
    Thank you

    Hello,
    1 
    >
    curious maven wrote:
    > Do we need to lock the system (or posting-free the system) to do early delta initialization or not? If yes, please explain me how that work?
    No,you don't need to lock the Source System which is the advantage of Early Delta Init.
    With early delta initialization, you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the posting of data in the source system. The option of executing an early delta initialization is only available if the DataSource extractor called in the source system with this data request supports this.
    [Business Information Warehouse 3.0 Overview Presentation|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9a0e9990-0201-0010-629b-dc2735cb9c81]
    2
    >
    curious maven wrote:
    > 2. Someone somewhere mentioned that early delta initialization is not preferable compared to normal delta initialization, even though early delta initialization is advantageous. Why is that so?
    Early delta is not supported by all the extractors. See Lo Extraction
    3
    >
    curious maven wrote:
    Imagine, while scheduling Queued Delta Init or un-serialized V3 delta Init, if I choose certain end date and time (say, 10pm, 12-31-2007) for the records, then all the records till that point would be loaded to setup tables and all the records after that point of time will be moved to extraction queue or update tables. My question is, if this is true why would we ever need to lock the system during setup tables filling?
    >
    >     If you say the records after that particular time and date (10pm, 12-31-2007) will not be collected in extraction queue and update tables, why don't we do the following
    >            
    >              a). say, I do full load with end date and time (10pm 12-31-2007)
    >              b). Next, I do delta init with start date and time (10pm 12-31-2007) (this time I lock the postings)
    >
    >          If we do this way, we can actually reduce the down time of the system. Is my conclusion right?
    >
    >          If you say it's not practicable as some transactions' saving time differs from time stamp and some transactions' delta is even measured by pointer.......if this is the case we can use Delta offset. What do you say about this?
    This is applicable to Generic Delta where you can set the Safety Interval (Upper Limit and lower Limit) for the extractor based on ALE Pointer, or Time Stamp or Calendar day.
    If you excute a extractor with early delta init, during the setup table fill, the delta records will be directly written to the delta queue. The delta management handles these functionality.
    [How to Create Generic Delta|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33]
    [SAP BI Generic Extraction Using a Function Module|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8df33]
    4
    >
    curious maven wrote:
    How this scenario differs to early delta initialization?
    If you do a Init without Early Delta init, then the user cannot post new documents and you have to either schedule in the weekend or request for a Source System downtime.
    But if you use Early delta , then you don't need the source system down time and the user can post new records during the init, which will be written to the delta queue directly.
    [How to Minimize Effects of Planned Downtime (NW7.0)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/901c5703-f197-2910-e290-a2851d1bf3bb]
    [How to Minimize Downtime for Delta Initialization (NW2004)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5d51aa90-0201-0010-749e-d6b993c7a0d6]
    Thanks
    Chandran

  • Numeric Pointer for delta

    Hi guys,
    can any key field be a numeric pointer will that be missing any deltas for the extractor and also what should be the safety lower limit for this.
    Thanks,
    Your help will be rightly appreciated

    HI,
    Time stamp - The field is a DEC15 field which always contains the time stamp of the last change to a record in the local time format.
    So you can use any time related filed in this column.
    Using timestamp we can run delta multiple times per day but we need to use the safety lower limit and safety upper limit with minimum of 5 minutes.
    Thanks and Regards
    Rajesh

  • HR Benefits - Age limit  for Life Insurance,

    Hi,
    If we want to create an upper age limit for spousal life insurance and employee life insurance plans that already exist, what is the best method for each?
    For the spousal insurance, the Define Dependent Eligibility Rules seems to only apply to medical plans.  Looks like you can only create beneficiary eligibility for insurance plans.
    Thanks Terry

    Hi,
    Jay - "Define Dependent Eligibility Rules" is where I could only find medical plans.  The life insurance only seems to allow beneficiary criteria.
    Ram - I had tried the Age grouping, but it looks like it's controlling coverage costs.  So if I create an addtional age range with a cost of $0, they could still have the plan. But they really shouldn't have it any longer.  I want them to show up on the participation monitor.  At least this was my interpretation.   I thought this may be a pretty common requirement. 
    Terry

  • Amending the mic upper lower limits at the time of RR

    Hi, Please advise how to change the upper lower limit of the mic during resultts recording? Also advise how to cancel the recorded values of the results recording so that the lot status becomes REL? Can we change REL to CRTD status. Thank you every one supporting the beginners.

    please advise how to change the upper lower limit of the mic during resultts recording?
    Its really not possible
    Also advise how to cancel the recorded values of the results recording so that the lot status becomes REL?
    You can not cancel but change the values .This is possible if you declare all char as "Long term " char in control indicator.
    This will give status LTIN to char which allows you to change the RR values at any times
    Can we change REL to CRTD status.
    In QA02-->click on "Reset"-->save -->this will change status from REL to CRTD.
    but this is only possible when UD is not taken

  • Sales price upper/lower conditions

    hi,
    I would like to know if it's possible to set a warning message, if we set a sales prices upper or lower (in % or not) then a default value.
    I have already defined upper/lower limits for the sales conditions but does not work.
    Thank you very much
    Pedro Barros

    Hey Ines,
    LSMW is probably your best bet. The only tricky part is ensuring your key combination string e.g. Sales Area, Customer, Article is included for SAP to figure out which pricing table to update. If you create an LSMW object using a recording, it calls tcode VK15 (for what its worth...).
    The other option you could try is CATT (Computer Aided Test Tool). You can access that via transaction SCAT. That will do the trick for as well.
    Good luck!
    Cheers,
    Paul...

Maybe you are looking for