why the loading set-up tables only for LO extraction.why not
for other extractions like FI,CO-PA?plz gv me answer
clearly..very need
Answers were Sorted based on User's Feedback
Answer / haritha sidella
Setup tables sit on top of the application tables,Logistics Extractors do not allow accessing of the transaction tables directly(That's how they were designed by SAP in the early stages I guess)hence setup tables are used to extract data from ECC, where as with other applications there is no such restriction as the datasoures have to be generated as per user requirement.
Set up tables are only used for initial extraction, so its only a one time process unless you run into trouble with your data in your infoprovider and need to reload it again, once the data is initialized new records are updated using Delta mechanism.
There's tons of information on this around on the internet just google it !
Is This Answer Correct ? | 6 Yes | 2 No |
Answer / lakshmi prasad
using setup table concept in lo data will be loaded huge volume data load into table.some times data load to the target in this time all users are locked.business also stop.data fetch setup tables data not a stranded table.v1 job can run data record stored on db table and extraction Q,v2 job run to data records directly stored on db table and delta Q stored(lbwq)or sm13 v3 job run v3 triggers vl data will be stored on bw dela Q(rsa7).data will cumming full or delta records its no well time mechanism so lo concept using setup table
Is This Answer Correct ? | 3 Yes | 2 No |
Answer / devesh kpase
Reason being data volume. History data load for LO is loaded to setup tables first and then loaded to BW with full extraction. once full load is done then the current data is loaded using delta mode which uses delta queue.
Direct extraction on LO application tables is not allowed
Is This Answer Correct ? | 0 Yes | 3 No |
Answer / jeevitha reddy
In Lo extraction infopakage can't fetch the data from application tables directly ,soo wee need one intermediate tables those called setup tables.
in fi the data volumes will be large,so in this trascations will post at a time in the application tables and extraction structure ,from extraction structure info pakage can fetch the data ,soo no need setup tables
Is This Answer Correct ? | 0 Yes | 6 No |
What are the reporting performances can we do?
Where do you find which table is currently being populated (BIW1 or BIW2)?
What is the transaction to maintain services?
Where do we use write optimized dso?
What are the update modes available?
What is multiprovider.
What are the mathematical functions?
What is the licensing requirement you should be aware of?
What are the read modes for query?
What is NDIV0?
Can any one explain me....Before coming luw's into Extractor queue(Lbwq),What Update mode(v1 or v2) will execute?
What are time dependent text/attribute of characteristics?