What is classical starschema and extended starschema.

Hi All,
What is classical starschema and extended starschema.Diff betwn both .
Thanks in advance.

Hi,
As per my knowledge there is no classical star schema.... It is jus the star schema and extended star schema...
Star Schema :
Star schema is nothing but Fact table in the center and surrounded by the master data tables...... In star schema we have some draw backs thats why we move accross to extended star schema.....
1. There is no usability of master data becoz it is inside the cube.
2. We can analyse only from 13 angles
3. Performance issue becoz data will be in alpha numerics....
We have come accross with these in Extended star schema
Extended star schema :
Fact table in the center surrounded by the Dimension tables.. And we have out the Master data tables from the cube to outside and these tables linked to the dimensions with the foreign key and primary key relationship... Between these Dimension and master data tables we have SID tables in which the data will be stored in numeric format..........
And final one is we can analyze the data in 13 * 248 angles.....
Khaja

Similar Messages

Classic wht and extended wht

hi,
may i know what is the difference between classic wht and extended wht? can advise what is the major difference between these two?
thanks

Hi,
Classic WHT- In some countries, the law provides that invoice recipients must withhold a certain portion of the payment amount and pay this to the tax authorities as withholding tax on behalf of the vendor. This requirement exists in the United Kingdom, for example. In other countries, withholding tax need only be reported to the tax authorities for certain vendors, such as self-employed people. Withholding tax is not posted in these countries. This is the case in France, for example.
Withholding tax amounts are reported to the tax authorities at regular intervals and a statement is also sent to the vendor periodically. These reporting periods vary from country to country.
The way in which withholding tax is calculated depends on the type of service. Transactions may:
Have a variable base for tax/SI contributions
Have different tax rates
Not relevant for withholding tax
EWHT-With extended withholding tax, you can process withholding tax from both the vendor and customer view.
In Accounts Payable, the vendor is the person subject to tax, and the company code is obligated to deduct withholding tax and pay this over to the tax authorities on the vendoru2019s behalf. In Accounts Receivable, the company code itself is subject to tax, and the customers that do business with this company code deduct withholding tax and pay this over to the tax authorities on the company codeu2019s behalf. In both cases, the business partner of the person/entity subject to tax deducts the tax and pays it over to the tax authorities.
Withholding tax is calculated and posted to the appropriate withholding tax accounts at different stages, depending on the legal requirements in each country. As a rule, withholding tax is posted at the same time that the payment is posted, in other words the outgoing payment (Accounts Payable) or incoming payment (Accounts Receivable), is reduced by the withholding tax amount.
In certain countries, such as Brazil, the Philippines, and Spain, withholding tax can or must be posted when the invoice is posted. This means that the amount receivable or payable is reduced by the withholding tax amount.
Extended withholding tax supports both concepts.
The key concept in extended withholding tax is the distinction between withholding tax type and withholding tax code. While withholding tax types represent basic calculation rules, specific features of these rules - in particular the percentage rate - are represented by the withholding tax code. You can define any number of withholding tax codes for a given withholding tax type.
If a particular transaction requires more than one kind of withholding tax, this is covered in the SAP System by defining more than one withholding tax type. When entering a line item, you can enter withholding tax data for each of these withholding tax types.
For more information about the functions of extended withholding tax (in comparison to classic withholding tax), see Withholding Tax
The following special features also exist:
In some countries, such as Argentina and Italy, other kinds of posting are required for certain business transactions. Instead of the payment amount being reduced by the withholding tax amount, the withholding tax is posted as an offsetting entry to an expense account You make the relevant settings in the withholding tax code.
Where cleared items are reset, the clearing document is automatically reversed if it contains withholding tax data. For withholding tax types with accumulation, the accumulation base amount is adjusted if the payment document is reversed.
Hope this helps.
Rgds
Manish

Difference between Classic Scenario and Extended Classic Scenario

Hi Expers,
I need your help again........:-)
I just want to know what is the differne between classic and Extended Classic Scenario.
Points will be rewarded
Thank you
sam

Hi Sam,
(explaination frm a previous thread)
Difference between scenarios
WIth classic scenario, the SC following document is to be created in your R/3 backend(s). Thus you can get an PO, a PR or a stock reservation in R/3.
With extended classic the following document is to be found in SRM itself. Thus from a SC item you can get a complete PO, an incomplete PO or depending on your customizing a Sourcing cockpit (now called Sourcing Application) requirement. Additional FM are called when you tick the box "Enable Extended classic" in the IMG activity, enabling you to get a local PD.
If you need to get a stock reservation in R/3 with extended classic, you will have to switch back to classic scenario for the particular category or product with a dedicated BADI ("Control extended classic ").
Be aware that with extended classic, the PO created in R/3 is not exactly a replication. That is a "copy" with that crucial difference that the SRM PO will use a different Purchase Organization that of R/3. It enables you to centralize your purchasing. In SRM you can create a "local" Purch. Org for EMEA zone for instance while in R/3 that is rare you can purchasing above a country (because in the backend you have to produce legal documents related to one company). Those "local" (=SRM) Purch. Org. are required to enable extended classic and it makes simpler Contract management for instance (in classic scenario contracts may need to be replicated to your R/3 back end and adjusted for each back end and each Purch Org in R/3, and even for each plants).
In a nutshell with extended classic you have a PO in SRM, and this PO is assigned to a different Purch Org that of R/3. Purch Org in R/3 are determined on the basis of the "LOcation" (R/3 plant you have replicated from your backent into SRM).
Extended classic is required for service purchasing when you want your requesters to be able to adjust the PO price while they can not access R3. In extended classic, PO is issued from SRM and not from R3.
Please check this too:
http://help.sap.com/saphelp_srm40/helpdata/en/e9/d0fc3729b5db48e10000009b38f842/content.htm
BR,
Disha.

Classic Scenanio and Extended Classic Scenario

Hi all,
I would implement on the same system 2 different scenario:
1. Classic Scenario for self service procurement
2. Extended Classic Scenario for the following business scenario:
a. PR from ECC is transfered into Sourcing Cockpit with Plan Driven Scenario
b. buyer convert the SC created in Sourcing Cockpit into a GOA or a PO that are transfered to ECC.
Can coexist this different scenario?
Can I address this different scenario only with organizational differences?
Thanks
Bye
Marco

Hi Marco,
I see 2 quick ways to realise your requirement.
The first is to create an attribute in t77omattr for a position and maintain that attribute in the organisational model. This attribute could just be filled with an X for example.
Then you have to implement BADI BBP_EXTLOCALPO_BADI and retrieve the attribute you created with FM BBP_READ_ATTRIBUTES (use sy-uname to retrieve the attribute for the current user).
The 2nd is to create a Z-table with the user-ids that you want to use the local (or ECS) scenario. Then again in BADI BBP_EXTLOCALPO_BADI you have to write the logic to retrieve and compare this.
Keep in mind that these are user-based distinctions and not based on scenario.

What is the difference between Classic and Extended Withholding Tax

Hi,
Can some please tell me what is the difference between Classic Withholding and Extended Withholding Tax. How can I look at the Withholding Tax deducted from a particular invoice?
Number Guaranteed.
Thanks.

Dear Prem,
Withholding tax is the basically a tax withheld during the Vendor payment. So when making the payment to vendor the amount will be deduct (i.e withheld tax)
from the invoice and paid. The customer is actually the tax to tax authorities.
you can visit for more info.
Withholding Tax
For the config steps you go to the IMG path FI > Financila accounting for the Global settings > Withholding Tax
Withholding tax configuration is done by FI person.
Hope this helps you
Prem

Classic Withholding Tax and Extended Withholding Tax

Hi,
What is the difference between Classic Withholding Tax and Extended Withholding Tax.
Regards
RKG.

Hi
Withholding tax is calculated and posted to the appropriate withholding tax accounts at different stages, depending on the legal requirements in each country. As a rule, withholding tax is posted at the same time that the payment is posted, in other words the outgoing payment (Accounts Payable) or incoming payment (Accounts Receivable), is reduced by the withholding tax amount.
In certain countries, such as Brazil, the Philippines, and Spain, withholding tax can or must be posted when the invoice is posted. This means that the amount receivable or payable is reduced by the withholding tax amount.
Extended withholding tax supports both concepts.
The key concept in extended withholding tax is the distinction between withholding tax type and withholding tax code. While withholding tax types represent basic calculation rules, specific features of these rules - in particular the percentage rate -
are represented by the withholding tax code. You can define any number of withholding tax codes for a given withholding tax type.
If a particular transaction requires more than one kind of withholding tax, this is covered in the SAP System by defining more than one withholding tax type.
When entering a line item, you can enter withholding tax data for each of these withholding tax types.
How To Configure Withholding Tax?
Steps for extended withholding tax :
1. Check withholding tax countries
2. Define Ex. Withholding tax types for invoice postings
3. Define Ex. Withholding tax codes
4. Formula for Ex. Withholding tax calculation
5. Assign Ex. Withholding tax types to Company code
6. Activate Ex. Withholding tax
8. Create a G/L a/C for Ex. Withholding tax
9. Define A/C for Ex. Withholding tax (DBWW)
10. Make changes in Vendor master (XK02)
11. Maintain Company Code Settings:
Path: IMG -> Logistic -> General -> Taxes on goods movement -> India -> Maintain company code settings
12. Activate country version for specific fiscal year position
Path: IMG -> FA -> -> **** -> Taxes on sales purchases -> Basic Setting -> India -> Activate country specific for fiscal year position
http://help.sap.com/saphelp_erp2005/helpdata/en/e5/0780914acd11d182b90000e829fbfe/content.htm
nagesh

Classic and Extended Withholding tax

Hi,
Can anybody explain me what is the differance between classic and extended withholding tax.
Rds,
javed

Hi
Text from SAP documentation
SAP provides you with two procedures for processing withholding tax:
"Standard" and extended withholding tax.
"Standard" withholding tax is the procedure that has always been supported by the system. It offers you the following features:
Withholding tax for accounts payable
Withholding tax calculation during payment
Withholding tax code per vendor line item
Extended withholding tax provides the following additional features:
Multiple withholding taxes per customer or vendor line item
Withholding tax calculation for partial payments
Thank You,

Classic and extended Classic.....

Hi Guru's
Can we have classic and extended classic together..If yes what settings need to be done and how based on what system will diffrentiate the follow on documents creation.
Thanks in Adv.
IS

Yes, this can be achieved. By default you have to activate Extended Classic Scenario in the system. But using the BADI BBP_EXTLOCALPO_BADI, you can switch to Classic Scenario based on your requirement.
For more details please check documentation here in your SRM system
SAP Implementation Guide ->
Supplier Relationship Management ->
SRM Server ->
   Business Add-Ins (BAdIs) ->
    Control Extended Classic Scenario ->
     Activate Extended Classic Scenario
Regards
Kathirvel

Reverting to classic scenario in SRM7.1, from PPS and extended classic

Hello Experts,
Recently we have moved from SRM7 to SRM 7.01, in which we can have PPS without Extended classic scenario.
As business wants classic scenario, How can we make the system as classic , in which PPS and extended classic is activated.
any badi is available for this? Please help.
Regards,
Raju

Raju,
Basically you have few points to keep in mind. (yes you need to activate the SPRO config for extended classic, apart from this).
1. switch between extended classic and classic is actually defined by the backend logical system of the document. if thats SRM itself then it follows the path of extended classic or if it is ECC then it follows classic.
because its basically creating a follow on document and that explains the scenario.
2. it also depends on what object are you expecting to be created. from a SC many documents can be created.
a. PO in SRM
b. PO in ECC
c. PR in ECC
d. Reservation in ECC
- so, if you can define at any point that where is your document to be created and what is to be created you can control the flow.
Now to do this. if you have few options.
Option1:
1. set the object types(2) for product categories (config, backend document type).
2. implement BBP_EXTLOCALPO_BADI to switch off extended classic
Options 2:
1. in doc change badi, change the backend destination to ECC
2. in Badi BBP_TARGET_OBJTYPE pass the object type you want your follow on document to be.
hope this explains

Can we use both Stand alone and Extended classic in one SRM system

Hi All,
Our client is now using Stand alone SRM system with back-end R/3 FI-CO system. Now they want to go Extended classic scenario for few product categories.
         Would it be possible to use both in one SRM system? If possible could you please provide what are the sequential steps to do this?
             Thanks in advance.
Regards,
Ram

Hi Ramesh,
How did you end up solving your problem, as i have the same scenario. Did you use this BADI (
SRM Server->Business Add-Ins->Control Extended Classic Scenario->Activate Extended Classic Scenario)? Based on my reading, it seems this BADI is relevant to switch between extended classic and classic scenarios.
From what i understand, we can control the standalone scenario via the define backend system configuration (SAP SRM -> SRM Server -> Technical Basic Settings -> Define Backend System for Product Category). In my scenario, I have one set of product categories, so i will likely need to implement this BADI (BBP_DETERMINE_LOGSYS, method:   DETERMINE_LOGSYS - SAP SRM -> SRM Server -> Business Add-Ins ->Shopping Carts and Requirement Items -> Determine Backend System / Company Code) in order to determine the correct backend system based on company/plant for example.
Did you then leave the extended classic scenario activated (IMG --> Supplier Relationship Management -> SRM Server-> Cross-Application Basic Settings->
Activate Extended Classic Scenario)?
Or how did you achieve both standalone and extended classic using one SRM server?
cheers,
AD

SRM standalone and extended classic

Hi Experts,
Configuration: ECC 6.0 (with Ehp4 installed - (not activated)
SRM 7.0
Just want to seek confirmation of my understanding re: SRM implementation scenarios. Is it possible to have a extended classic and standalone setup using the same SRM server with same client? Both will have the same product categories. These will be for two separate entities/companies.
Thanks in advance.
Regards.

Hi Mike,
How did you end up solving your problem, as i have the same scenario. Did you use this BADI (
SRM Server->Business Add-Ins->Control Extended Classic Scenario->Activate Extended Classic Scenario)? Based on my reading, it seems this BADI is relevant to switch between extended classic and classic scenarios.
From what i understand, we can control the standalone scenario via the define backend system configuration (SAP SRM -> SRM Server -> Technical Basic Settings -> Define Backend System for Product Category). In your scenario, you have one set of product categories, just like mine, so i assume you had to implement this BADI (BBP_DETERMINE_LOGSYS, method: DETERMINE_LOGSYS - SAP SRM -> SRM Server -> Business Add-Ins ->Shopping Carts and Requirement Items -> Determine Backend System / Company Code) in order to determine the correct backend system based on company/plant for example.
Did you then leave the extended classic scenario activated *
MG --> Supplier Relationship Management -> SRM Server-> Cross-Application Basic Settings->
Activate Extended Classic Scenario)?
Or how did you achieve both standalone and extended classic using one SRM server?
cheers,
AD

What is the diffrence between extends and creating new object?

HI ALL,
what is the diffrence between extends and creating new object?
meaning
class base{
class derived extends base{
class base{
class derived {
derived(){
base var = new base();
can u people tell me diffence from the above examples.
THANKS.
ANANDA

When you create a new object you have to supply the class to which that
object belongs. A class can extend from another class. If it does so
explicitly you can define the 'parent' class from which the class extends.
If you don't explicitly mention anything, the class will implicitly extend
from the absolute base class named 'Object'.
Your example is a bit convoluted: when you create a Derived object,
its constructor creates another object, i.e. an object from the class from
which the Derived class extends.
Extending from a class and creating an object don't have much in common.
kind regards,
Jos

TS1382 I have a ipod classic 160GB and it's not showing any music anymore, but there is still 7GB of memory being used, and I don't have it back up on my itunes, since I had to put a new hard drive on my computer. Any suggestion to find out whats on that

I have a ipod classic 160GB and it's not showing any music anymore, but there is still showing 7GB of memory being used, and I don't have it backed up on my itunes, since I had to put a new hard drive on my computer. Any suggestion to find out whats on that memory or to get it the music back, there is approximately over 1400 songs on it?

What is the memory being used by, is it Other? If it is, that means the iPod can no longer read the music, so it has put it all in "Other".
The usual fix for this is to allow the iPod to Sync with its iTunes Library. If that doesn't work, the next option is to Restore the iPod using the Restore command in iTunes, on the Device/Summary pane.
Unless you are very (very) lucky, I suspect that you are going to have to Restore your iPod. Restoring will remove everything form the iPod and put back onto it only what it finds in your iTunes Library, which you say is currently empty.
If you have to rebuild your Library after this issue, by adding all the music back again, this is going to be hard to hear, but for the future, you may want to consider always having a backup of your library. The easiset way to back the Library up is;
if the Library is small enough, burn it to a DVD, as digital files, not a "music CD".
If your Library is too large for a DVD, buy yourself an external hard drive and copy the Library onto the drive. Remember to update the backup every so often.

Classic and Extended classic scenario

Hi All,
Can we have classic scenario for Service procurement (MM-SRV) and Extended classic for direct material procurement in the same SRM system.
This is because Extended classic doesnot support service procurment where as Classic scenario supports
Does any body implemented like this. If so pls let me know Pros and cons
Abdul Raheem

Hi Laurent,
Thanks for reply.
Do we have any limitations if we go by this model like Service procurement by Classic and Direct procurement by Extended Classic.
If any thing breif on PRos and Cons of going by this model.
Abdul raheem

I tried to save a video to IPhoto, and then when I tried to open IPhoto it told me I can't open the application because classic environment is no longer supported. What does this mean, and how do I get back all my photos and fix this? thanks.

I tried to save a video to IPhoto, and then when I tried to open IPhoto it told me I can't open the application because classic environment is no longer supported. What does this mean, and how do I get back all my photos and fix this? thanks.

With the amount of information you've provided it's impossible to offer a potential solution. We can't see your computer so we need to know some details of your problem and setup, i.e.:
what version of iPhoto are you using?
what system version are you running?
what fixes have you tried?
where is you library located?
did you apply any updates or upgrades just prior to the problem occurring?
are you running a "managed" or "referenced" library?
what type of Mac?
how much free space on your boot drive?
OT

What is classical starschema and extended starschema.

Similar Messages

Maybe you are looking for