Cutovers strategies

Hi
How we can mange the cutovers strategies in this scenario
If I am starting data migration is coming 10th and it will end 20th of this month and I am planning to take the datau2019s up to 10th. of this month
So wt can I do the open sale orders and new MD datau2019s during the period of 10 to 20th.
How I can plan these data uploads.
Regards
Ishikesh

Hello Friend,
Cutover strategy is a stage/activity in Project, referred while transferring the data from the legacy system to the SAP. At this Junction the billing will be stopped, all the open orders, contracts, pricing data will be transferred as per the cutover plan which is provided by the implementation partner. All the activities are freezed and pending tasks to be done before or after this activity.
So the message is very clear Cut Over Strategy means no business and in your case for 10 days no business would be there.So the question of data doesnt arise at all.

Similar Messages

PO release strategies with Contract

Hi,
implementing a PO release strategy (SAP-MM module)I need to consider the case in which a PO is assigned to a Contract.
If so, different release strategies should be selected according to the PO value.
Possible cases:
S0-strategy 0: Contract does not exist, PO value>=0eur
S1-strategy 1: Contract exists, PO value>=100eur
S2-strategy 2: Contract exists, PO value>=200eur
Is someone aware if it is possible to activate such release strategy without defining manually in the characteristic for CEKKO-KONNR field all possible contract single values (entire range)?
Thanks a lot for helping!
Regards,
Elisabetta Rizza
Please contact me at following mail addresses:
[email protected]
[email protected]
Hi Elisabetta,
I've moved this here because it is a more appropriate thread. BPX is the place for discussing the role of the buisness process expert. This is a MM question
Message was edited by: Marilyn Pratt

Dear Amit,
Requirement: If GR posting date exceeded 45 days than delivery date set in PO, then delivery date in PO has to be changed to current system date and at the same time New Release Strategy (B1) has to be triggered with one release code (02) automatically.
So in that case the values in Release Strategy (A1) and (B1) would remain same,,, as you suggested we will assign the value 01 u2013 USRC1 to Rel Strategy (A1) and 02 u2013 USRC1 to Rel Strategy (B1) and the same we will try to incorporate in the coding of Exit u2018'M06E0004'
We will check the process and confirm the same.
Thanks for your suggestion.
regards,
Urendra Kumar

Migration Strategies

HI Gurus,
You might help us,weI need your strategical inputs.
We have our 2nd company code SAP Roll-out, however the project stop. Migration was done way back July 2011.. and now 2012 they wanted to continue.
What would be the best strategy to do in here? As users wanted to trash back all the data that has been uploaded last july 2011.. and upload a fresh start/new data as of 31 dec 2011 since its 2012.
Can be the data uploaded last july 2011 be reverse totally? GL AR AP (balance and Open Items).. We suggest to just upload the missing months and reconcile to be balance, but user donu2019t want
Any inputs? Appreciate you help
Thank so much

Hi Friend,
cannot, as we have another company code that is existing and running..
any inputs?

Transfer between storage types and putaway strategies

Dear All,
Here is my scenario and please guide me on as detailes as you gurus can on how to proceed achieve this:
When receiving good from a PO the materials are received in 902: How to move them to my Raw materials storage type?
Note: I have defined 4 storages types, one for raw materials, one for production, one for Finished goods and one for spare parts.
And once I move the materials into the warehouse, what strategies do I have to define in order to place the materials in specific bins? Here's an explanation on how I need the putaway:
I have 5 different racks or stacks but I need all materials to be placed in a specific row of the first level, lets say material A in 01-A-01 the first 2 digits are stack then level then row(SS-L-RR); Material B should be placed 01-A-02 Material C 01-A-03; meaning all the materials should be placed in the level A of stack 1 but if there is another recepit of material A and it is already full then the system should propose another bin doesn't matter which one as long as it is not in the first level (because this positions are reserved for other materials).
This is the same for materials D, E, F but those are to be placed in stack 02 in level A
I need this because that's the way my client work right now, it is like Lean manufacturing strategy, so whenever they need to pick materials they always have them available at the lowest level
Is there an automatic bin to bin TO creation for when the picking empty the bin at the lowest level then a TO should be triggered automaticaly saying move from whatever bin the material is available to the "fixed" bin assigned in level A
Stack 1                         Stack 2
Level     1     2     3          Level     1     2     3
D     free     free     free          D     free     free     free
C     free     free     free          C     free     free     free
B     free     free     free          B     free     free     free
A     A     B     C          A     D     E     F
The variable here is that as I said before I have 5 Racks so in the other 3 stacks doesn't matter the levels, the materials can be placed wherever, and this will happen when receiving material A but all stack 1 is full then system should try to place it in the nearest bin available of stack 2 (only levels B, C, D) or if this is also full, then goes to stack 3 ( all levels available)
Please advise on how to map this, and the transactions and mvt types involved, and also please explain how should I make the picking or removal strategy to propose the picking always from the specific lower level bin, if not enough qty available then go and pick from other bin (and if it is possible at this point to create a TO to refill the fixed lower bin)
Thanks in advande to all.
Julio

Hi,
Try using movement type 313 and 315
313 -- Transfer posting SL to SL --- Remove from issuing SL
315 -- Transfer posting SL to SL -- Placing in Receiving SL
Regards

Block creation of PO if the release strategies is not applicable

HI SAP,
Can we block creation of PO if the release strategies is no applicable ?
My release strategies is on the PO header. It's only work if the PO have one Plant only. If the user put more then one plant
my release strategies will not work. how to solve this problem ?

Hi,
Check on it:-
http://www.sapfans.com/forums/viewtopic.php?f=6&t=205684&start=0&st=0&sk=t&sd=a
Re: Release Strategies in Purchase Order - possible values of caracteristics
PO Release strategy question
pherasath

Release Strategies in Purchase Order - possible values of caracteristics

Hello,
I have the following situation at hand.
We use in a company code a release strategy for POs. One of the caracteristics is the "plant" (CEKKO-WERKS, multiple values). Strategy is working fine.
Now I have to implement in another company code- in the same Client - the PO release strategy but this company code has about 800 Plants asociated! moreover, the release strategies in this new company are not dependent on the "plant"!
I can not change the caracteristics in the Release strateg because this would affect the already working strategies and SAP does not allow to asign another Class to the PO release groups.
Is there any way I can prevent that I have to create release strategies with each of them 800 Plants in the caracteristics "Plant" ?
Can I use something generic in the caracteristics field of the strategy?
Thanks for any help. It would save me a lot of time!
Aart

Note 493900 - FAQ: Release Strategy
1. Question :
Why is the release strategy not determined?
Answer :
Please check the following points :
You can not use Release without classification and Release with classification.
If there is an entry present in Release Group table (T16FG-FRGOT) only release with classification can be used.
If you use version management, the determination of the release strategy starts when the version is completed.
You complete a version by setting the "version completed" indicator in the version tab.
Cost Center values (CEBAN-KOSTL) and Vendor values (CEBAN-LIFNR) in the release strategy characteristics should be entered with leading zeros.
This is true for the other structures as well (CEKKO and CESSR). See note 52225.
For OVERALL RELEASE (purchase order and purchase requisition) the item fields such as Plant and Material Group will be aggregated to header level.
For example you use Plant as one of your characteristics. If all items do not belong to the same plant then the relase strategy will not be found unless you have maintained a blank value as one of your allowed values for the characteristic Plant. If all items belong to the same plant then that plant is aggregated to the header; if one or more is different then a blank is aggregated to the header. See note 47089.

Reporting on Strategic Skills Priority from table T5W8P (SAP-HR)

Hi all,
I have a requirement to report on Strategic Skills Priority which is held in table T5W8P in ECC6.
So I need to load this through to BW somehow, and I guess create it as an attribute of the Qualification.
However I cannot see this field in any of the standard extractors and don't seem to be able to create this table as a datasource using RSO2.
Can anyone tell me how I can bring this field through to BW?
Many thanks
Mischa

Hi,
I tried that and get an error message "Entry T5W8P does not exist in DD02L (check entry)"
I am not sure if this is something that has to be done on the SAP side, or if this is something specific to our system. Has anyone seen this error before?
Thanks again
Mischa

Purchase Order Release Strategies for Changed Amount

Hi Gurus,
We have a unique request from the business to set the release strategies for POs based on the Still to Deliver amount, not the Net Total Amount of the PO.
Example: Configuration is PO total amount <$5K requires only L1 approval. PO total amount >$5K requires L1 and L2 approval. PO was created for $8K and was release using L1 and L2 approvals. Receipts were posted to PO in the amount of $7K. Now the buyer has added an additional line item for $1K. The PO total amount now shows $9K ($8K + $1K), the Still to Deliver field shows only $2K ($1K from original remaining amount + $1K from new line item). Business wants the release strategy for this change order to go through L1 only since the Still to Deliver amount is <$5K.
Has anyone done this before? Any ideas??
Thanks,
Gabe

from http://help.sap.com/saphelp_40b/helpdata/fr/dd/2d547bb435d1118b3f0060b03ca329/content.htm
User exit M06E0004 is provided to enable you to adapt the release strategy determination process to meet your requirements.
This user exit allows you to change the communication structure for determining the release strategy for purchasing documents.
The following user fields are available:
USRC1
USRC2
USRN1
USRN2
In addition, communication structure CEKKOZZ is available, allowing you to use your own fields.

Are these requisition release strategies common?

All,
I’m designing new requisition release strategies for indirect requisitions at a chemical industry client. I’d like to know how often you have seen the following sorts of design before:
Existing design: Item-based release with workflow, with three dollar levels. At the lowest levels, two strategies for each cost center approver (the one used is based on whether the desired vendor is foreign or domestic). Characteristics assign several cost centers to each approver. Strategies and codes are named for users, so we change configuration whenever someone changes jobs. The codes are linked to positions, which are attached to user IDs. Result: about 80 release codes and 140 strategies, taking a lot of time to maintain.
Current redesign: Overall release, using 6 strategies and 6 codes based on dollar level and foreign vs. domestic. A user exit selects the approver for each code from a custom table that stores the user IDs for each cost center, with a custom maintenance transaction for the table.
Now the client wants both individual approval by cost center owner and items with different cost centers on a single requisition combined with approval of the overall purchase. I’m considering item-based approval of requisitions, with the user exit and custom table, and adding overall approval of indirect POs with the overall approvers.
Thanks for your help!

Hi,
No-Requisition release strategies are not common, one need to design release strategies based on business requirement. Release strategies looks simple after designing but its design needs creating thought to it.
In your case, you can go for designing redesigning release strategies for Overall release with using 6 strategies and 6 release codes. Considering you have configured release strategies with all release values for PO document type ,PO value and Purchasing group. Now design a custom table and go for followings:
Client---Pur Group--Rel Code1-- Rel Code2-- Rel Code3-- Rel Code4-- Rel Code5-- Rel Code6
The search help is required to pull in purchasing group details from T024 table and SAP user ID from Table USR01
Concept: Create Purchasing Group (OME4) as Department & assign the Department name to Cost center (KS01).
For more refer a discussion:
PR release: place holder for Cost center and Material grp
NOTE: User training required crate requisition for one department only where only one cost center involved- No requisition creation allowed for multiple cost center.
You can also go for other concept designing of your Requisition release strategies
Regards,
Biju K

How to get Auction No. from RFX in SAP SRM strategic sourcing

Hello experts,
We are using SAP SRM7.0 strategic sourcing.
We are converting the RFx to Auction. All the thing we needed is if there is any function module to get the auction number with the RFx number.
I've tried with a few but couldn't found.
Thanks & best regards,
Ramana

Hi Ramana,
You should check following link:
http://wiki.scn.sap.com/wiki/display/SRM/Live+Auction+tables+structures+classes+function+groups+and+function+modules
I hope it helps.
Regards,

Release Strategies not works - When multiple material group in a single P.O

Hai,
This related to Release Strategies in SAP- IS -Retail.
The Material group was one of the character in the Rel Strgy.
1) If i create a P.O for the item which is related to " X" material group , Rel Strgy been set to P.O
2) If i create a P.O for the item which is related to " Y" material group , Rel Strgy been set to P.O
If I combine material group "X' & "y" in a same Purchase order , then RELEASE STRATGY NOT BEEN SET TO P.O .
How to make this as possible in SAP -IS-Retail - Version 6.0
Thanks,
PS

Hi,
Generally it is not advisable to use item level characteristics for overall release . Please refer the sap note 493900
Cost Center values (CEBAN-KOSTL) and Vendor values (CEBAN-LIFNR) in the release strategy characteristics should be entered with leading zeros.
This is true for the other structures as well (CEKKO and CESSR). See note 52225.
For OVERALL RELEASE (purchase order and purchase requisition) the item fields such as Plant and Material Group will be aggregated to header level.
For example you use Plant as one of your characteristics. If all items do not belong to the same plant then the relase strategy will not be found unless you have maintained a blank value as one of your allowed values for the characteristic Plant. If all items belong to the same plant then that plant is aggregated to the header; if one or more is different then a blank is aggregated to the header. See note 47089.
you have to maintain blank value in CT04 for material group and the same thing must be maintained for all strategies.
The release procedure for purchasing documents is carried out on header level. For this, the following values are aggregated from the items on header level:
item value
plant
material group
Example WERK:
The plant is only aggregated on header level if all items contain the same plant. If only one alternative plant exists, ' ' is aggregated on header level.
A release strategy is then searched for with this value.
Of course, a corresponding strategy is only found if the value ' ' was maintained for the characteristic 'Value' as an object value.
The same functionality applies to the plant

Purchase requisition : problem with check release Strategies

Hi all,
i created a new class, new release group, new release codes etc. I think all is ok but when i launch the transaction OMGQCK for check release Strategies the system give me an error in node 'Check re release indicators' : Define a release indicator for the status "released".
But how can i do that, i created two release indicator : 'X' for blocked and 'V' for launched but what are the options for purchase requisition ?
Is there a special value to give the release indicator 'released' ?
Thanks for your help.
Edited by: ToraTora on Mar 31, 2011 5:46 PM

Hi,
Goto SPRO -> Materials Management -> Purchasing -> Purchase Requisition -> Release Procedure -> Procedure with classification -> Setup Procedure with Classification
select release indicator
by default, you will be having the following release indicators in the system,
1     Request for quotation
2     RFQ/purchase order
3     RFQ/PO no change of date
4     RFQ/PO no changes
A     Fixed RFQ
B     Fixed RFQ/purchase order
X     Blocked
please check whether you have got these or else create and then assign them to the release strategies.

Tables for Release strategies

Hi ...
I was referring to MM table doc , in that it is mentioned table EBELN & EBELP are for Purchase Order header / Line and BANFN & BNFPO are for PR header/ Line.
But for release strategy ...people told me to refer CEKKO for PO and CEBAN for PR.
does it mean that release strategy refers to different tables for execution ( and I believe these tables are used for release strategy purpose only and if Yes then at what point PO / PR data gets updated in these tables)
Regards
Suresh

Hi,
Please find release tables used in MM.
EKAB       Release Documentation
EKEH        Scheduling Agreement Release Documentation
EKEK        Header Data for Scheduling Agreement Releases
T161E       Release Codes
T161F       Release Point Assignment for Purchase Requisition
T161G       Release Prerequisite, Purchase Requisition
T161H       Fields for Release Procedure, Purchase Requisitio
T161I        Determination of Release Strategy
T161S       Release Indicator, Purchase Requisition
T161U      Texts for Release Indicator
T163P        Release Creation Profile
T163S        Description for Release Creation Profile
T16FB        Release Indicators: Purchasing Document
T16FC        Release Codes
T16FD        Description of Release Codes
T16FE        Descriptions of Release Indicators: Purchasing Do
T16FG        Release Groups
T16FH        Descriptions of Release Groups
T16FK        Release Statuses
T16FS        Release Strategies
I think, it will help u.
Ishu

Stop Re-triggering of PR release strategies for closed PR's.

Hi,
Scenario is like, PR raised and converted it into PO and material has been received.
After Receipt of material, system is allowing to change the quantities by un-releasing the release strategies.
Once material receipt is completed, system should not allow to change in / revoke the release strategies.
Please suggest.
Thanks in advance.
njs

hi
plz check ur release indicator in spro >mm>pur>pr>rel>
here select the rel indicator and check the changability option in bottom it has to be 6
hope it help
regards
kunal

OBIEE 11g patching strategies (or lack thereof)

I'm very interested to know how people are patching production instances of OBIEE 11g. I've been very frustrated by the fact that Oracle releases tons of "one off" patches (which aren't guaranteed not to screw up other things), but no "production ready" patches that have been fully regression tested, etc. I don't think they EVER released a production patchset for 11.1.1.3, I think everyone had to wait for 11.1.1.5 (which was almost a year later)...
I can understand this for the 10.1.3.4.x series, because that seems basically "mature" - but OBIEE 11g has a TON of bugs in it.
So my question is - what strategies are people using to test patches and decide whether to put them in or not? I just installed a patch that is crashing the server when trying to save repository variables and init blocks. I don't have time to spend a day testing each and every "controlled" patch out there.
What to do? Is Oracle ever going to start releasing monthly or quarterly "patchsets" that have all patches bundled and tested together?
Thx,
Scott

Hi Dpka, that's exactly what I was afraid of. I've gone from being a data mart and OBIEE developer to spending literally half my time working on Oracle SRs for OBIEE 11.1.1.5. I'm hitting the exact same issues as you - lots of untested one-off patches that break other items, with no fully integration tested patchsets ever being released (11.1.1.3 was out for over a year...never saw a patchset for that...I can't wait another year for an integrated set of 11.1.1.5 patches).
Here's my high level complaint - Oracle USED to put together patchsets, which were groups of patches tested to work together. These would come out every few months. But for the last two years or so, I don't see Oracle doing that any more - not just for OBIEE - I see this for almost everything (for example, we also use OWB - trying to do the upgrade to 10.2.0.5 but there are literally a hundred patches to apply).
In general - has Oracle simply stopped producing patchsets? If so - I really demand a refund for the support we're paying. My job is not to spend two weeks applying 100 patches on something because Oracle can't do basic integration testing on their patches.
Uggg, sorry, really really frustrated with Oracle right now. I wish they would stop working on "new features" and crap on 11g OBIEE and get the basic tool to work properly. I really get the feeling a lot of what went into 11g was glitz and glamour, but it was implemented by people that had never used the tool "real life". Just a guess, but some of the bugs are so basic that I refuse to believe that anyone that ever actually implemented and used the tool could have made those mistakes.
Scott

Cutovers strategies

Similar Messages

Maybe you are looking for