Release strategy past actual forecasted demand

I only receive 10 weeks of forecast from my customer, is there a parementer that will create schedule lines past the 10 weeks based on historical data?

please check at MP80 whather you can create a profile and assign  to material master forcasting view?.

Similar Messages

  • Issue with retriggering Release Strategy

    Hi all,
    We have a one off situation here. We had already 10 release staragies in our system. We added 2 more release strategies with a new characteristic. We updated the characteristic value only for the new 2 release strategues and did not update the rest 10. Although now we had updated the characteristic value for remaiining strategies, the purchase documents created in the mean tme is not subjected to release strategy. To ensure business control we need to retrigger back the release strategy for almost 1000's of documents.
    As any change to purcahsing document will retrigger it when done manually, but given the number of documents and as per Note 493900 we cannot trigger it by any backgoriund job to modify as below:
    16. Question :
    Why is there no release strategy determination when a program changes in
    background a purchasing document which corresponds to the classification of
    a release strategy ?
    Answer :
    This is the system design that a release strategy determination can only be
    triggered through a user action and not by changes made in background
    process.
    If you create a document (e.g. PO, Contract, etc), the determination of the
    release strategy takes place only in case of a user event like checking or
    saving the document.
    Kindly suggest any best practise to retrigger release strategy  for the missing documents to ensure business control. Any easy and time savig measure to get it resolved will be appreciated.
    Regards,
    Anand Sampath

    Hi Arnand,
    After investigation by searching customer messages database ,I found              
    other customer has  similar problem as the release strategy has changed           
    after creation of the SES please review the  explanation from developer           
    :(whose release code is 03 )                                                                               
    When you try to revoke the acceptance of the service entry sheets                 
    in ML81N or ML81, the 'Enter release code' pop  up window appears, but            
    entering the code that is determined via the menu path Goto -> Entry              
    Sheet -> Release Strategy (which is the 03), the SES remains the same.            
    Nothing changes. The status does not vary and no error or warning                 
    message is issued.                                                                               
    Checking the customizing for the release strategy, the release code               
    03 should have never been assigned to the SES 800024272 as the values             
    for the relevant characteristics were not included under that code.               
    I do not know how it was managed to accept the SES.                                                                               
    Now, when you try to revoke it, it seems that no release                          
    strategy can be determined, not even including the values RCARESANO               
    and 012 between the valid values for the characteristics of the release           
    code 03 (RCARESANO as valid value for SUPERVISOR_SERVICIOS                        
    (CESSR-ERNAM)and 012 as valid value for GRUPO_COMPRAS (CESSR-EKGRP)).                                                                               
    The only Possibility is to change now the SES so that the release                 
    strategy can be re-determined by the system.This is the Only possible             
    way that the system can  redetermine the Release Strategy , but it will           
    not be possible to do so as the SES is already accepted with the Old              
    strategy and it does not admit any further changes.                               
    To be able to change it you would need to revoke the SES first,                   
    but this Will also not be possible as the Release Strategy was changed            
    and the system still applies the old rules for determining the Release.           
    Solution to our Problem                                                                               
    The Only way to revoke the SES is to Restore back the Old Strategy that           
    was prior to 03 in the customizing.So now what will happen is that by             
    applying the Old Rules the System will be able to revoke the SES that#s           
    using the Old one. Once the necessary SES are revoked then go back to             
    customizing and apply the new strategy as it was did now, and                     
    Change the SES and save , the new value of the Release Strategy will get          
    updated in the table ESSR and the field frgsx will now have 03.                                                                               
    Problems associated if the Release strategy is changed                                                                               
    Actually the release strategy is not supposed to be changed when there     
    are some documents in the System that uses it and even if you change the   
    Strategy the Old records will not get AUTOMATICALLY UPDATED by the        
    system.The Release Strategy routine has to run again to update the         
    values. This is Possible by changing the document SES ,                    
    This change will happen only if the SES is not accepted and if its         
    accepted then you need to revoke and to revoke you need to restore the     
    old strategy , revoke and then change the SES , and have to go back to     
    customizing and Start using the New strategy from now on by doing so the   
    Routine will update the old record with the new strategy.                 
    b) You may want to use CEKKO-BADAT(Requisition Date) or any other
    structure in CEBAN or CEKKO and create a new release strategy    
    to differentiate the old release strategy.
    Hope this helps,
    Kind Regards,
    Matthew

  • How to Display PO Release Strategy in Enjoy Screen

    Dear all,
    I have a PO with a release strategy, which contain several release codes to release the PO (i.e. M1 & V1).
    However, I am only able to display the release code (i.e. M1 & V1) in t-code ME23. I could not do the same in the enjoy screen t-code ME23N for the same PO number.
    In the item level, there should be a tab with release strategy to display the PO release strategy (similar to PR), but it is not appearing.
    Could anyone tell me what is the problem here? I just could not find the tab or menu to view the release strategy of a PO in the enjoy screen. Similar goes to other PO. I could not view it as well. But in the old screen, I could view it.
    Thanks a lot.

    Thanks 4 the reply Rahul.
    I understand that it is only possible to release at header level. What my problem is that I am unable to view the release strategy (which code to release and who to release) for the PO in enjoy screen.
    In my earlier thread replying to Ankur, I am simply describing that I could just select a line item, click on the release strategy button and the release strategy is displayed. A different line item with different value generated a different release strategy of course. Different amount require different set of release strategies, usually more level of approvals.
    So, actually this question is not about where or how I can release a PO, but actually I could not view who is releasing for a PO in ME23N.
    I even simulate it in the development server and still the same thing happen. Is it the same for everyone else? If yes, how to view who is releasing the PO in ME23N? Version of system is 4.7.
    Thanks and appreciate if anyone could help.

  • Precautions to be taken before going for new PR Release strategy

    Dear all,
    We are going to implement release strategy with classification at item level release. Current process in our company release strategy without classification at item level release was implemented and its Production for past 3 years.
    Need your advice on
    1)If we go for new release strategy as off  with existing release strategy -what are the precautions to be taken before implementing new strategy - any problem will happen to existing data with old releases, which already release, yet to release?
    2)Once after implementing the new releases, the PR with old release strategy (which is not release yet)u2026does this will trigger new release?
    3)Any other which I missed out, please suggest me
    Thanks
    RS

    Hi,
    It is better to release all existing PRs using your current procedure without classificaton and clean up.
    If you impliment procedure with classification, It depends on the parameters like Plant, value, purchasing group you are going to use in the strategy. Also you may decide whether to have overall req release or item level release of PR by having diffrent release groups.
    REgards
    Ram
    Edited by: ramachandran subramanian on Feb 18, 2009 7:00 AM

  • How to get Forecast demand data from R/3?

    Hello,
    I am working on an xApp development project which interfaces with ERP.
    Does anyone know if there is a BAPI to extract forecast demand data for each customer/product combination in R/3? 
    Also, is there a BAPI to extract the total number of shipments from each site to each customer or some way to come up with actual demand for the current period. If there is one number that totals the unit shipments to each customer, that would be easiest. Otherwise, if there is a way to get the shipments and we process them that would work also.
    Is there a BAPI to create a Safety Stock for each site?  We are going to put the calculated safety stock values back into R/3.
    Thanks for your help.
    Brayden.

    Byaden,
    To upload the SAFETY STOCK into R/3 Im using the BAPI: StandardMaterial Method: SaveData and works fine.
    If you need detailed information write me to [email protected]
    Regards,
    Byron Milian

  • Graphical view in Purchase order release strategy

    Hi Experts,
    I have added new position in existing Purchase order release strategy which is running properly.
    I am facing the problem of visual display in header on tab release stratege for the PO which are already released by respective authority.
    It is showing final release balance all though release indicator set to "1".
    For e.g.
    PO number 123 was released by 4 persons in past.
    As per new modification release agencies are 5 nos.
    for this PO release flag set to "1"
    As 4 persons involved in PO release the graphical display shows 5 agencies for release but release tick infront of these show only 4.
    My Problem is client wants correction in this graphical display.
    Please help me on this.
    Regards
    Dhananjay

    TELL THE SOLUTION DEAR ..SO ANOTHER WOULD GET HELP IN FUTURE.
    REGRDS
    MANOJ

  • Change in Purchase Order Release Strategy Values

    Dear All,
    I am in process of changing Purchase Order release strategy values.
    I have following release strategy -
                           Current Value                  (Proposed Value)
    Level 1 -         Upto INR 0.1 Mn               (Proposed value - Upto 1.0 Mn)
    Level 2 -         From 0.11 Mn to 0.5 Mn   (Proposed Value - From 1.01 Mn to 5.00 Mn)
    Level 3 -         From 0.51 Mn to 1.0 Mn   (Proposed Value - From 5.01 Mn to 10.0 Mn)
    Level 4 -         Above 1.0 Mn                  (Proposed Value - Above 10.0 Mn)
    My questions are -
    1) Will this change affect the existing Purchase Orders (already created) which are not yet released?
    2) Will this change affect the existing Purchase Orders (already created) which are released?
    3) Are there any risk factors?
    Can you pl. put light on above questions?
    Regards,
    Prashant Kolhatkar

    Hi,
    Actually, what you had given is not enough to determine if the existing PO will be impacted or not
    If you are just changing the classification but not changing the number of release level of the release code in the release strategy, the partial released PO will not be impacted unless there's PO changes. PO that are released will definitely not be impacted unless there are changed.
    In general, after a release strategy is determined for PO, SAP will retrieve the latest list of release code of that release strategy for display for that PO. If this list never change (mean you only change classification of the release strategy), then they will not be apparent to the user. But if this list change (you add new release code, replace existing release code or remove release code), then you will see some discrepency on screen as you will only see the modified list of release code and not the old list of release code
    Hope this help

  • Purchase Order Release Strategy didn't trigger

    Hi Gurus and SAP People!
    Good Day!
    I currently have a problem regarding one purchase order which didn't trigger a release strategy. I checked the classification/conditions/classes and it's all satisfied. I tried replicating the scenario in our Development server and I always end up triggering a release strategy.
    Moreover, as far as i know, the release procedure is not locked as it is one of the most commonly used release group and code. Can anyone have any ideas why that certain PO didn't trigger any release procedure upon saving?
    More details that might help.
    1. PO was initially on hold status then saved. (tried to replicate this as well and yet a release strategy was triggered)
    2. Upon saving, PO triggered an IDoc successfully. (my replication results always stayed "yellow" as it is still waiting to be released/approved before the actual Idoc generation (green)).
    3. Line item details had been changed between the PO being on hold and the actual saving. (but yet it still satisfies the release classifications)
    4. Line items came from PRs, Contracts, RFQs.
    Will greatly appreciate your help.
    Thank you very much!
    Regards,
    JV

    Hi Suzy!
    Thanks for the answer.
    I already checked the classification and searched our documentation repository if there were changes made and did not find any. Development and Production environment customization are the same.
    I forgot to include that after a few days the PO was created, they deleted one line item. That deletion made the PO trigger a release strategy.
    Nevertheless, the question still remains - why the PO didn't trigger any release procedure upon the initial saving.
    Regards,
    JV

  • Purchase order release strategy with a characteristic value as a variable

    Hi all,
    We have Purchase order release strategy based on the following characteristics:
    Total Net Order Value
    Purchasing Organization
    a few other custom fields
    We would like to add a characteristic based on the creator of the PO. In the purchasing department there are two person which have the authorization to create an release POs. The goal is now to check if the actual user, who release the PO, is different from the PO creator. The value of this characteristic may not be a fix value, it must be contain the name of the actual user name.
    Is there are a possibility to insert the characteristic value as a variable such as SY-UNAME instead a fix value?
    Thanks,
    Charles

    this is verymuch possible.  You can use unsed fields user1, user2 etc in CEKKO or (ii) insert a new field in CEKKOZZ and use the new field.  You need to build up logic in user-exit such that this field will take the value of person who had logged in. This can be done by ABAPer.
    Hope this resolves ur problem

  • User Exit for Purchase Order Release Strategy

    Hi,
    I am a little new to this, how do I search for a user exit for purchase order release strategy (TCode ME29N).
    Thanks in advance.
    Mick

    Hi
    Check the following Exits and BADI for Pur Requisition
    Enhancement
    MEVME001 WE default quantity calc. and over/ underdelivery tolerance
    MM06E001 User exits for EDI inbound and outbound purchasing documents
    MM06E003 Number range and document number
    MM06E004 Control import data screens in purchase order
    MM06E005 Customer fields in purchasing document
    MM06E007 Change document for requisitions upon conversion into PO
    MM06E008 Monitoring of contr. target value in case of release orders
    MM06E009 Relevant texts for "Texts exist" indicator
    MM06E010 Field selection for vendor address
    MM06E011 Activate PReq Block
    MMAL0001 ALE source list distribution: Outbound processing
    MMAL0002 ALE source list distribution: Inbound processing
    MMAL0003 ALE purcasing info record distribution: Outbound processing
    MMAL0004 ALE purchasing info record distribution: Inbound processing
    MMDA0001 Default delivery addresses
    MMFAB001 User exit for generation of release order
    MRFLB001 Control Items for Contract Release Order
    AMPL0001 User subscreen for additional data on AMPL
    LMEDR001 Enhancements to print program
    LMELA002 Adopt batch no. from shipping notification when posting a GR
    LMELA010 Inbound shipping notification: Transfer item data from IDOC
    LMEQR001 User exit for source determination
    LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001 Customer-Specific Source Determination in Retail
    M06B0001 Role determination for purchase requisition release
    M06B0002 Changes to comm. structure for purchase requisition release
    M06B0003 Number range and document number
    MEQUERY1 Enhancement to Document Overview ME21N/ME51N
    MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
    MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
    MEETA001 Define schedule line type (backlog, immed. req., preview)
    ME590001 Grouping of requsitions for PO split in ME59
    M06E0005 Role determination for release of purchasing documents
    M06E0004 Changes to communication structure for release purch. doc.
    M06B0005 Changes to comm. structure for overall release of requisn.
    M06B0004 Number range and document number
    Business Add-in
    ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
    ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
    ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Custome
    ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
    ME_PO_PRICING Enhancements to Price Determination: Internal
    ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
    ME_PURCHDOC_POSTED Purchasing Document Posted
    SMOD_MRFLB001 Control Items for Contract Release Order
    EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
    MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP Determination of Delivery Address
    ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
    ME_REQ_POSTED Purchase Requisition Posted
    ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
    ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
    ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
    ME_BSART_DET Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
    ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
    ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN Commitment for return item
    ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO Copy PO data for use by Country version India
    ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
    ME_CHECK_OA Check BAdI for Contracts
    Reward points if useful
    Rgds,
    Naren

  • PR/PO Release Strategy

    Hi All,
    Actually there is a requirement where i need for options in PR/PO release strategy.
    The four options that i need are
    >Approve
    >Cancel
    >Recommend to approve
    >Recommend to reject
    The SAP provided standard options are approve and cancel.
    How can i add the two other options in the standard workflow?
    pls let me know.
    Thanks n Regards,
    Raj

    The standard workflow does not have any user decision step having two buttons approve and reject
    but it directly opens up ME29N.
    so first you wil have to remove this dialog step from the workflow which opens ME29N
    then keep your decision step with four buttons and handle the outcomes

  • PR Release Strategy- transport of charact/class/ values using ALE

    Does anyone have the information relative to ALE set up for release strategy-
    I am using transactions BD91 for characteristics; BD 92 for Class and BD 93 for the actual values into release strategy.
    I need the information as to what needs to be set up in Development client and receiving clients ( Q and Prod) for these transactions i.e., RFC destinations, define ports, Identify Message types & setup partner profile configurations etc
    This will be a great help.
    Thanks
    Raj

    Hi Raj,
    Please check the below notes for more inrofmation:
      86900 -  Transport of Release strategies (OMGQ,OMGS)
      799345    Transport of release strategy disabled
      10745     Copying classification data to another client
      45951     Transporting class data: system / client. - has details of what you are looking for.
    Hope this helps.
    Regards,
    Ashwini.

  • Release Strategy of Procurement in BI Content?

    Hi,
    Is there any standard datasource about Release Strategy of Procurement in BI Content?
    Any helpful suggestion, I will give points.
    Thanks.
    Stephen

    There are couple of approaches that can be taken with this issue since there are delivered extracters exclusively for Purchasing Requisitions.
    1) Piggy back on PO ITEM Extracter (2LIS_02_ITM) or PO Schedule Line Extracter (2LIS_02_SCL).
    Purchasing Requisition/Items (Table EBAN, TCODE ME53) are uniquely linked to PO/Item (Tables EKPO, TCODE ME23N).
    PO Item (EKPO-EBELN & EKPO-EBELP) are linked to (EBAN-BANFN & EBAN-BNFPO).
    Based on this you can extract the required fields from EBAN in the User Exit for PO ITM or PO SCL extracter.
    This is what I did but my case was not same as yours. We primarily need PO Item/SCL information with some pertinent attributes from the requisitions
    Pros: No need to write a seperate extracter.
    Cons: If there are any requisitions that are not converted to PO's they will not be included in extraction till such time they are actually converted to PO's
    2) As Bala indicated , Create a Custom extracter based on Table EBAN.
    Pros: All Requisitions are extracted regardless of whether they have been converted to PO's.
    Cons:
    1) I am not certain if Generic Delta will successfully trigger all Changes to the Requisitions (depending on how the P2P process is configured for your Project).
    2) If Delta does'ent work in all scenarios then a FULL load might be very difficult to manage based on the Data Volume.
    Hope this helps.
    Thanks
    Vasu

  • Release Strategy should be effected even if the PO Price is lowered?

    Hi users,
    Another doubt of mine is based on the release strategy (the Purchase order goes for rerelease) only in case of the increase in the PO Order Price (that is if the price is manually increased in a PO or if it indirectly increased by the increase in quantity)
    Requiremnent: the current requirement is the po should go for a rerelease even if there is a decrease in the po price. alternately any change in the PO effecting a rerelease would also be acceptable.
    anticipating an rearly answer.
    thanks and regards
    vinay

    This is standard SAP. Release strategy will be reset only on increase in value.  You have to make the release strategy think that the value has increased (even if it has decreased).
    Please see (the second part of) my comment in
    Re: release strategy is not reset in PO?
    Reproduced here for your ease:
    You can use the release user exit. If the PO is in change mode and Save option is selected, then increase the value in the user exit (This does not increase the PO value actually, just fools the release strategy into thinking that the value has increased).
    Hope this resolves.
    Lakshman

  • ME54N Release strategy question over delivery tolerance limits

    I set up a release strategy base on the over delivery tolerance level. My problem is when a Purchase requisition is saved as rejected, and i click on the button cancel reject it deletes the last release strategy level because now it is looking at the actual total value disregarding the over delivery tolerance level.
    It works fine when the Purchase requisition is not rejected, and i can cancel or reject the purchase requisition without saving it and it does not delete the last line of the release strategy taking into account the over delivery tolerance level. I am using the user exit ZXM06U13.
    Can someone give me some insight into this ? Thanks.

    Hi Siva:
    You should request the development key for this structure under your SAP system, then you can add the extra fields in CEKKO.
    Good luck
    Z.T

Maybe you are looking for

  • Can I delete LR2 after upgrading to LR4?

    I just upgraded from LR2.7 to LR4.2.     LR2.7  is still on my computer....  The upgrade transferred my old presets OK. So, can I delete LR2.7 without any problems? Ed in Florida

  • Opening a jar file

    hey all, i only have one class that i want to make a jar file. i make sure the msdos prompt is focused on the right folder, and i use the following command line... jar cf writer.jar writer.class it makes a jar file without any problems, but when i go

  • SQL Statement using LIKE and Subquery?

    Hi, I have two tables, one table is called "Restricted_Words", the other table is called "Content" .   I have a field called "short_desc" in the Content table and a field called "word" in the Restricted Words table. I want to write a query that will

  • Windows Azure and Exchange Server

    Hi, Do Azure VMs support installation of Exchange Server 2010 or 2013. I am sure technically you can install. QUESTION IS: But is that a supported scenario (like sql server 2012)? -Phani Technical Architect | BrainScale Consulting | AllThingsAzure.co

  • Help battery problem

    Hello to everyone! The battery of my ipod touch 5 was damaged. So I decided to change the battery by myself because the warranty was expired. My friend told me that he was able to change it. But after the change, ipod will not turn on.. Only if it is