SAP BW release versus SEM release

Hello,
I am currently on BW 3.1 version and R/3 Enterprise. I want to install SEM for SEM-BCS BW based implementation. Are all the SEM versions "compatible" with BW 3.1? If not, which is the most recent SEM release that is?
Which SEM version is recomendable for SEM BCS BW based implementation if I can't go for the last one?
Would I get a huge benefit if upgrade 3.1 to Netweaver 2004/s before think about SEM BCS BW based implementation?

Hi,
I would rather look for this information in OSS notes.
What I know is:
Q: Are all the SEM versions "compatible" with BW 3.1
-- No, the latest version of SEM (particularly, SEM-BCS 6.0) is not compatible.
Q: Which SEM version is recomendable for SEM BCS BW based implementation if I can't go for the last one?
-- The SEM-BCS 4.0 is mature and stable release.
Q: Would I get a huge benefit if upgrade 3.1 to Netweaver 2004/s before think about SEM BCS BW based implementation?
-- Actually, NW 2004s already works with SEM-BCS 6.0. So, the question is irrelevant.
Correct me if I'm wrong.

Similar Messages

Stack file is invalid: 'SEM-BW' (stack release 600 source release 602)

Hi experts,
I encountered the following error while patching my BCS SEM system using EHPi.
Servere error(s) occured in phase PREP_EXTENSION/EHP_INCLUSION!
Last error code set: Stack file is invalid: component 'SEM-BW' (stack release 600 < source release 602)
The BCS SEM system is currently installed with SEM-BW 602. But the xml stack file generated by solution manager contains SEM-BW 600. From SMSY, under the Software Components tab, the release for software component SEM-BW is 602.
Where does solution manager obtain the data when calculating the xml stack? How can I generate a xml stack with SEM-BW release 602?
Thanks,
Tzyy Ming

Hi.
When installing this system you have used an installation guide. If i were you i would try to configure the system described in the guide. SAP note 852447 talks about an IInstallation SEM-BW 600 on SAP NW 2004s AS ABAP;
So why not try to configure this system as netweaver as abap in smsy and add the add-ons as relevant. But i am not completely sure - i am at home and can not look to our SolMan system.
I do not think that the configured system should be the problem. You said, the smsy contains the correct data. Did you refresh the product data in your solution manager. That could be the reason why the queue ist not calculated correct ly.
regards,
Martin

SAP R/3 different versions, release years

HI SAP Gurus,
Can any body please can give me the details of SAP R/3 releases and its release years .
Example : in 2004 or 205 ECC5 is released and in 2006 ECC6 is released,
This also i am not sure i am just giving as an example.
I just want to know from 4.5B to till ECC6, whe each version is released by SAP.
Thanks in advance,
Vinay.

Hi vinay,
Please go through link,
http://solutionbrowser.erp.sap.fmpmedia.com/
SAP R/3 Enterprise Release 4.0B
Release Date June 1998
SAP R/3 Enterprise Release 4.5B
Release Date March 1999
SAP R/3 Enterprise Release 4.6C
December 1999
SAP R/3 Enterprise Release 4.6C
April 2001
SAP R/3 and R/3 Enterprise 4.70 SR1
Release Date March - December 2003
ERP Central Component
Release 5.0 SR1
Release Date August 2005
ERP Central Component
Online Update April 2007
Release 6.0 SR1 SP08
Release Date June 2006
SAP enhancement package 1 for SAP ERP 6.0
Release Date December 2006
ERP Central Component
Release SAP enhancement package 2 for SAP ERP 6.0
Release Date July 2007
SAP NetWeaver 2004 (SPS 20)
File Type HTML (PlainHTML)
Release Date May 2007
Knowledge Center for SAP NetWeaver 7.0 (2004s)Support Package Stack 13, September 2007
SAP NetWeaver Mobile 7.1 SPS 02
Release Date July 2007
reward if useful.
Regards,
sunil kairam.

Find sap user id from release code and release group

does anyone know any FM that can get sap user id from certain release code and release group?
ex: if i input rel code 40, rel group N1 , then it should be sap user id A
i would prefer FM rather than tables and tcode.

Hello,
Please find attached list of tables
T16FB                          Release Indicator: Purchasing Document
T16FC                          Release Codes
T16FD                          Description of Release Codes
T16FE                          Descriptions of Release Indicators: Purcha
T16FG                          Release Groups
T16FH                          Descriptions of Release Groups
T16FK                          Release Statuses
T16FL                          Release Indicators: Service Entry Sheet
T16FM                          Descriptions of Release Indicators for Ser
T16FS                          Release Strategies
T16FT                          Descriptions of Release Strategies
T16FV                          Release Prerequisites
T16FW                          Assignment of Role to Release Code
Thanks & Regards,
Mihir Popat

When is the SAP ERP 6.0 EHP3 Release Date???

Dear Expert:
I need to know when is the SAP ERP 6.0 EHP Release Date?
Please Tell me~
Regards
Jack Lee

Jack ,
EHP4 has been released for ECC6.0 .below link will guide you more all yor queries::
https://websmp108.sap-ag.de/erp-ehp
Thanks..
Mohit

Mail to Buyers SAP inbox once PR is released

Hi All,
How to configure the system so that a mail will be triggered to buyers SAP inbox once PR is released.
Thanks in Advance
Pavan H S

Hi,
Found this in SAP Note 365604 for release strategies in purchasing:
"3. User exit
During the individual release for purchase requisitions, the user exit
is called in function module ME_REL_STRATEGIE_EBAN, in the overall
release, it is called in function module ME_REL_GENERAL_STRATEGY_EBAN.
(Enhancement M06B0002, EXIT_SAPLEBND_001, ZXM06U13)"
You may be able to get a programmer to insert some code in this customer exit to initiate the mail message.
Regards

SEM releases

Hi,
I'am working in a implementation proyect. We are installaing ECC6 and BI 7.0.
I just checked the SEM release and I see:
Component: SEM-BW
Release: 600
Level: 0012
Support Package: SAPKGS6012
Description: SEM-BW 600 : Add-On Installation
When looking for a note in the marketplace, I see that there are releases 602, 603 and 700.
does any body knows any reazon for us to be installing an older SEM version?? have we made a mistake???

Hi Mauricio,
I think you have installed the SEM6.0 version. If you SEM BI engine is on the Netweaver 2004s then you can have the SEM 7.0 version installed in place of SEM-BW 600 .
Regards
Vijay

BUS2012 releaser RELEASE - BAPI_PO_RELEASE, saving releaser

Hi all,
I know, this kind of topic was already processed a couple of times, however I did not find a suitable solution for our problem.
Customer wants to be able to save (and report later) releasers of the PO. There is a new processed being implemented, which uses the (slightly modified) BUS2012 object and it's RELEASE method to release the step of the PO in the workflow. Now this calls BAPI BAPI_PO_RELEASE, but it's interface does not incorporate the RELEASER.
We can't use change documents for this purpose, as, from workflow-orientated releases there will only be WF-BATCH users releasing everything. We would be able to find the place, where CDHEAD and CDPOS are filled, but however this could be not only one place and the added value would be very low, as customer wants a transparent reporting on who and when did which release. For this purpose we enhanced the EKKO table with 16 fields (combinations of uname + date), which will serve the purpose of saving releaser / date of release for every step.
We can get the actual agent of the workflow, but I do not know how to pass him / her to the BAPI. Of course we can redefine the RELEASE method (and we also will have to), but whatever I put to a e.g. Z_BAPI_PO_RELEASE, will need to be accessed somewhere deeper (maybe in FM ME_REL_SET, maybe in ME_PURCHASE_DOCUMENT_DATA_SAVE)...
I believe this was already solved by somebody and we do have something like a best-practise to work with it. Can anybody guide me? Of course, the whole process should be ready to accept releases also from ME29N, should also be implemented for the cancellation of the release and for rejection. But this first step would be a good kick for me.
Thanks in advance.

I can give you one option:
define a new 'release' method, still calling the BAPI_PO_RELEASE but define it as dialog not background
place the task calling the new method directly after the decision task , transfer the WI_actual_agent of the decision task as the executing agent of the new task.
This way the BAPI_PO_RELEASE will be executed with the RELEASER user and not WF-BACTH.
however, this solution has a few limitations:
this will work only in SAP GUI
the user will need to have authorizations to release the PO.
But, I have created many reports simply reading the workflow logs, this is not more complected then the change documents logs. you can use function modules:
SAP_WAPI_READ_CONTAINER
SAP_WAPI_DECISION_READ
SAP_WAPI_WORKITEMS_TO_OBJECT
And the logs themselves can be much clearer to the user then the change documents release status has changed from XXX to XXXX logs.

Release strategy for Release POs

Hi Every one,
We have a requirement.
A contract is created and approved as per the regular strategy.
The releases (POs) are created against it and sent directly to the vendor.
As the Contract is already approved, standard SAP does not apply the release strategy for the POs created for the contract.
But the business wants the PO releases too to follow the release strategy.
Can you please look in to this and let me what changes we need to make this happen.
Regards
Pavan

As the Contract is already approved, standard SAP does not apply the release strategy for the POs created for the contract
This statement is not correct, it's upto you to use or Not to use Release Process for release Orders (PO) created w.r.to Contract.
As the table & fields are Common for both Contract & PO release ..you need to choose the PO relevant fields & values in the Release Strategy..
So that the Release Process is applicable to PO's created w.r.to Contract also..
For ex: if you use the field purchase Doc category as a Character in the Release , it differentiates whether it is PO or Contract..
So that you can define different Release Strategy for PO & Contract
Or if you maintain the Doc type of PO in the Contract Release Strategy in CL20N / CL24N trxn code..
then the release strategy applies to PO also..

How we can find BAPI Release dependent OR Release indipendent

Hi Every one,
I want to find some BAPIs which are release dependent or release independent
->how we can find BAPI Release dependent OR Release indipendent
Regards,
Kmr.

Hello,
Maybe the following link can help you :
[http://help.sap.com/saphelp_46c/helpdata/en/d2/42f955cafe11d1ad0c080009b0fb56/content.htm|http://help.sap.com/saphelp_46c/helpdata/en/d2/42f955cafe11d1ad0c080009b0fb56/content.htm]
Also take a look at the SAP Notes and related SAP Notes of obsolete BAPIs in the link.
Success.
Wim

PO released dates by releases ?

Dear MM gurus,
Request pl let me know is there any Standard Report to see the PO Releases along with dates & release levels with sap user id. (PO releases history)
Pl help
thanx in advance
regards
Srihari

Hi
As u know ME28 and ME29N used to release PO's
U can check release date from CDHDR table in SE16/SE11
follow the path
T code SE16 -Table CDHDR -->enter PO number in Document Number -->enter Trnx ( click yellow arrow in front of it enter both trnx code i.e me28/me29n execute)
Now execute the report u will able to see release date for ur PO
Also u can check Release date/user ID in ME23N
Go to Environment-->Header changes
here ur able to see release date
Vishal...

MM:Release Strategy for Release Order again Approved Contract

Hi,
Release strategy for Release Order is required or not against approved contrat??
As fas as I know once the contract is approved, release order is not required to approve again.
This is the standard setting from SAP or We need to do some setting for this??
In my support project I have studied the release procedure and found that, same release strategy and release Group has been used for Purchase Order and Contract.
Please let me know if anyone have faced this rquirement or I have to go for Z development for this requirement.
Thanks you.

Hi Lalita,
Thank you for your quick suggestion.
yes definitely the release stratergy and release group should be set up separately but here both are same
that is the reason this is picking of the same release procedure again evenif the contract is approved.
we have following release characterstic for the release procedure.
1) Purchasing Group
2)Total Net Order Value
3)Order Type
4)Purchase Organisation
5)Material Group.
I think for the above characterstic we must a separater value for PO and Contract but Currently all are merge
in this only
But Can you tell me "Release Order should be subjected to release procedure" this is correct or not .
If yes then what is the base for this, I mean is it working on the concept that " If do relevent
release characterstic value is found then no release procedure and this is treated as autorelease in sap"
Thanks you.

Release indicator in release strategy

Hye,
I need to change release indicator in release strategies. can anyone let me know how to do the same
I have done this in confi -> sap - >mm -> purchasing - >PO - >release strategy and i changed indicator as x to y in release strategy, but i have nearly 500
Is there any other way where i can change directly
Thx

HI Raj,
This could be done using a BDC program. Else you can go for any testing tool or SCAT for solving ur purpose.
My understanding is...u r not going to create 500 new release indicators. U r going to change rel indicators in *relase statuses*
Cheers
Arun.

ME55 error - Release via individual release

Hi I have a question,..
We are using overall release strategy.
Now I have 2 line item in a same purchase requisition, and when run ME55 it show me the message "Release Possible".
Then after that, using ME52N we change the requisition and cancel 1 of those items, of couse a new release strategy was defined by the amount we defined.
But now, when go to ME55 now the messahe said "Release via individual release"... ann with ME55 cannot be release.. I need to go to ME54 and ME54N.
Do you know why SAP do that? what is the reason of this?

Dear,
As available in SAP NOTES 668940
Program error.
This problem occurs after deleting one item of a purchase requisition. The consequence is that all documents created afterwards will no longer be releasable via ME55.
Check the corrective information.
Please also check: Note 69792 - ME55->ME54 Changes from ind.release updated wrongly
Note 92315 - Call individual release - call transaction
Note 72100 - Individual release - only allowed items
Regards,
Syed Hussain.

Release date and release no of Scheduling Agreement

Hi All,
I have a problem with Scheduling agreement.
I have created a scheduling agreement with long validity period.
I maintained delivery schedules within that validity period.
I have generated forecast schedules. then using ME84, creating a releases.
the problem is occurs here.
it was not updating the release no and release date for the schedule line.
still it is showing a *yellow light* .
where is the problem and why it was not updating.
and can u please explain the process and significance of those lights.
Thanks in Advance.
Regards
Kishore

Verify the table T161M has the values
kvewe = 'B'
kappl = 'EL'
druvo = 1
kschl = LHPA
as mentioned in the code.
The solution is add in SPAD the

SAP BW release versus SEM release

Similar Messages

Maybe you are looking for