Question:
Any difference in terms of functionality with regard to 3.5 sem bcs to 3.2 sem bcs.
thanks
Answer:
There are no differences in functionality.
Answer:
THERE IS!
Why would SAP name as version 3.5 than 3.2 if it contains same functionaliy, a guest this guy does not know what he is talking.
Answer:
SAP has stated that there are no differences within BCS and I have taken this at face value.
If you know something I don't, I'd be delighted to hear your words of wisdom.
THERE IS!
Why would SAP name as version 3.5 than 3.2 if it contains same functionaliy, a guest this guy does not know what he is talking.
Answer:
There are differences!!
1) New business content
2) Possibility to do a pre-matching of IG-transactions before posting
3) Period initialization
4) And more .....
The list with the new funczionalities can be found under http://service.sap.com/sem
Georg
Answer:
THERE IS!
Why would SAP name as version 3.5 than 3.2 if it contains same functionaliy, a guest this guy does not know what he is talking.
If you don't agree with someone you don't need to be agressive. Please refrain from doing that!
Thanks,
ZZ
Answer:
Thanks for the info. Business content I knew but it is not functionality.
According to SAP "New Features by Release" in SapNet points 2 and 3 are common to both releases 3.2 and 3.5. There's only one document that covers both of these releases.
There are differences!!
1) New business content
2) Possibility to do a pre-matching of IG-transactions before posting
3) Period initialization
4) And more .....
The list with the new funczionalities can be found under http://service.sap.com/sem
Georg
Answer:
Semophile,
you're right! I just had a call with a guy from the BCS development department.
Equal functionalities!
erp4you
Answer:
Well done- there is no change in terms of functionality - 4.0 of course is the log awaited COI and more (including copy functions to other versions). There are some early client specific mods being done for 3.2 if your client wants to pay for this.
Would be nice to see some constructive SEM-BCS queries for a change....
By the way - see note 720668 for 3.2, 3.5 an 3.51 - must be immediately implemented!!!!
Cheers
J
Answer:
Georg
You have too much time on your hands.......
Answer:
I haven't seen 3.5 version as I have worked on 3.2 but if it includes functionality to copy versions then that's a big plus and also what is missing in 3.2 is complete functionalities for COI.
Answer:
We have been recommended by our consultants that BW based BCS is 'not all there' and therfore we whould use R/3 based. Can anyone summarise what you can not do in BW based that you can do in R/3 based that justifies still using R/3 based (I'm intrigued especially as some of you are using BW based - have you had to do lots of custom work? is it problematic? would you recommend waiting for 4.0 or is it really usable now?).
Many thanks for sharing your wisdom.
Answer:
In terms of flexibility and some functionality, the BW based consolidation is already superior to the R/3 based consolidation.
C/I is one of the few areas where the R/3 based one offers some functionality still missing in the BW based consolidation. Fair value adjustments and proportional consolidation are the most obvious ones.
There is no single reason to choose either module. It all boils down to your needs and specific circumstances.
We have been recommended by our consultants that BW based BCS is 'not all there' and therfore we whould use R/3 based. Can anyone summarise what you can not do in BW based that you can do in R/3 based that justifies still using R/3 based (I'm intrigued especially as some of you are using BW based - have you had to do lots of custom work? is it problematic? would you recommend waiting for 4.0 or is it really usable now?).
Many thanks for sharing your wisdom.
Answer:
Very interesting and surprised to hear that 'BW based consolidation is already superior to the R/3 based consolidation' !
Sorry for my ignorance but can you tell me what you mean by C/I
Thanks.
Answer:
Some advantages already offered by BW based consolidation:
- The most obvious advantage is the fact that it allows much more flexibility for data modelling. In EC-CS, you can only use 5 custom defined fields (even that is actually more you find in e.g. Hyperion's newest product).
- Allocation enables you to do things that are not easy to implement under R/3 based consolidation.
- No period restriction! You can consolidate daily if you like.
- Matrix organization within the same data model.
C/I = Consolidation of Investments.