Skip to Content
author's profile photo Former Member
Former Member

Why at all setup table

Hello techies..

In case of logistic application, setup table concept is being used. WHy at all it is required? in case of FI or CO area, there is no setup table concepts. Can suggest a gud document on these areas?

Regards

Sriram

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Feb 15, 2005 at 02:34 PM

    There is no really good document on why different SAP applications use different extraction methods. Basically it goes down to the R/3 database design. CO and FI are both document driven and store line items with timestamps. This makes it easy to implement a delta based on the timestamp but makes it vulnerable to database deletes by ABAP. Logistics uses no clear line item concept but different tables that store the current status of the different LO objects. To enable a clear reporting the LIS was invented and this was the best source for BW extraction.

    Best regards

    Dirk

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 17, 2005 at 04:25 PM

    Hello Sriram,

    not a direct answer to your question but there is a document, that might be helpfull. There is an FAQ-Document 'Around SAP BW DeltaQueue (RSA7)' that explains some details. You can find it in the BW-Area under 'Services & Implementation'. It also directs you to some OSS-Notes that give you some good details.

    hth

    Stefanie Schaaf

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 17, 2005 at 04:54 PM

    You have to remember that FI and similar extractors suffer from the fact that they provide only after images necessitating an ODS layer in BW. They also generally require a safety interval therefore precluding extraction of current data (e.g. make a J/E in FI and pull it in right away). LO extractors are V1 or V3 updates and not "after-the-fact" pulls from the base R/3 tables. Even with FI extractors, the requirement for "quiet time" on R/3 does not go away, although there are workarounds to this in FI and LO. The LO set-up tables can be deleted after data validation in BW. They are cluster tables storing history in an optimal manner. Finally, if your R/3 and BW have simultaneous go-lives, you do not need the set-up table.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.