Forecast Quantity Reduced to 0 by ASCP

Hi,
I'm running a Un-Constrained ASCP plan in 11.5.10 version.I have a forecast defined at Source for qty-300 in bucket-october-2010.I'm able to see this forecast entry in Collection workbench for 300 nos.
After running ASCP plan , the plan has shifted the sugg due date to plan start date.This is expected as the customer runs a customization to back-off the forecast date by Leadtimes.
But the qty is changed to 0 from 300.I'm not able to see any consumption details for this forecast entry.And even the 'Consumed Forecast' field in the PWB doesnot show any value , it is blank.But I have a SO , for qty-300 on the same date.if this SO has consumed the forecast , this should be visible in the consumption details.
Is there any other method to check the consumption in ASCP plan, other that the PWB-UI.
Even forecast expiration is not happening as it is a un-Constrained plan( ASCP userguide states that Forecast Expiration happens in a Optimized ECC plan , and again i dont see any value in the 'Expired Forecast' field in the PWB.
What are the other functionalities , that would reduce the Forecast qty.
Has anybody faced this similar issue earlier.
Thanks in Advance
Edited by: Bhubalan Mani on Aug 16, 2010 8:59 PM

Hi Partha,
Pls find the detrails below.
The Hook runs after Data collection and before Plan.SO the due date of the foreast is over written in the collected data.
In source the Due date of the forecast was in October'10.Due to the Intransit LT of 42 days , the due date was pulled in to August-10.
And the MRP parameters,
Include MDS Days
Include Past Due Forecast ,
both are blank.If its blank , what i understand is, there is no restriction to the Past Due forecast that is considered in the plan.
Please let me know , If You need any additional information.
Thanks

Similar Messages

  • Forecast Consumption Reduces Planned Quantity

    All, I would appreciate the Community's feedback with regards to why we are seeing the forecast (Planned Qty in RRP3) reduced.
    A number of examples have been identified where the forecast quantity has been reduced by the withdrawn quantity and the Remaining Quantity reflects the Planned Quantity.
    We are more used to seeing the forecast remain as per the DP forecast but Remaining Quantity reducing by the sum of allocated quantity and withdrawal quantity.
    Columns represent From and To dates, Plan Qty (Forecast from DP), Withdrawals, Allocated, Remaining Plan Qty.
    Row 1 is the reduced forecast which when released to SNP = 516 for the w/c 04.08.2014
    04.08.2014
    10.08.2014
    342
    174
    0
    342
    11.08.2014
    17.08.2014
    26
    0
    0
    26
    18.08.2014
    24.08.2014
    1,209
    0
    0
    1,209
    25.08.2014
    31.08.2014
    184
    0
    0
    184
    01.09.2014
    07.09.2014
    561
    0
    0
    561
    08.09.2014
    14.09.2014
    1,499
    0
    0
    1,499
    15.09.2014
    21.09.2014
    956
    0
    0
    956
    We have a number of examples like this but the more conventional reduction of Remaining Planned Quanity is the norm'.
    Thanks for any feedback.

    Hi Chris,
    Take a look of this old SAP note (it for R/3, but maybe you can find the reason):
    772857
    - FAQ: Independent requirements reduction/withdrawal quantity
    Question 9: What are common reasons for the reduction not  occurring?
    Response:
    For planning strategies with planned independent requirements consumption: Have the prerequisites for the consumption been fulfilled (see Note 772856)? Were there independent requirements quantities to be reduced at the time of the goods movement in the forward/backward consumption periods (planning quantity > 0)?
    For goods movements from inventory management (MM): Is the 'Independent requirements reduction' (PABKZ) indicator set for the movement type (transaction OMJJ)?
    For goods movements from SD (for example, transaction VL02) for reducing the make-to-stock production (requirements type LSF): Is the 'Requirement reduction' (PABKZ) indicator set in the requirements class of the customer requirement (transaction OVZG)?
    For stock transfers/transfer postings: A reduction does not occur for stock transfers in a planning segment. Only stock transfers between different plants, MRP areas and planning segments can reduce planned independent requirements.
    Is an MRP type that provides 'Reorder point planning', 'Forecast-based planning' or 'No material requirements planning' set for the material? See the modification of Note 68641 if you want to allow the reduction for these materials.
    Hope this helps,
    Kind Regards,
    Mariano

  • FM : For reduction of PIR forecast quantity

    Hi.
    Is there any FM for reduction of PIR <Forecast> quantity for consumption mode forward/backward>

    Dear,
    Please note that with stg 70, PIR will get reduced when you get dependent requirementa nd not on issue of material.
    I hope you must have changed the std setting.
    example
    PIR for 100 for assembly
    After running MRP
    PIR -100
    Planned order +100
    Now you have run MRP for final product, which gave the dependent requirement to assembly of say 75.
    Then in MD04 you will see following entry
    PIR    -25
    Dep req from final assembly -75
    Planned order +100
    This is nothing to do with consumption with 261/201.
    pl simulate the above scenario and come back

  • WM - TR & Open quantity reduced by available stock

    Dear All,
    The problem is:
    PrdOrds were released, TRs were generated and partially delivered (processed). After that inventory (stock counting) took place.
    Having finished the inventory we wanted to process the partially delivered TRs (LB10 > 'TO in foregr.') but SAP set the 'selected qty' in LT04 to 0 and gave the message: "Open quantity reduced by available stock" .
    We use dynamic bins, and all TOs have been confirmed. I've checked (in LT22) and I've found that the necessary quantities haven't been fully supplied for the dynamic bins of PrdOrds.
    Why SAP considers the quantities fully supplied? What is the reason? (During the inventory no differences were booked for the related materials) Shouldn't we create inventory doc. for dynamic bins?
    Thanks,
    Csaba

    Hi Jürgen,
    Thanks for your reply.
    This is the short history of this issue:
    1.
    total TR quantity was 30 pcs (originally)
    2.
    partially delivery, TO qty 16 pcs (TR reference)
    3.
    inventory - no inventory difference for that dynamic bin, qty was 16 pcs both before & after inventory
    4.
    problem detected - /WH couldn't process the TR as I said that's why they manually created a TO to post the goods to the dynamic bin/
    5.
    partial delivery, TO qty 14 pcs (w/o TR reference)
    (after point '4' we tried to process the TR in foreground as I said > problem discussed above. After that I processed it in background > result: TR quantity 30, open qty in TR 0, number of TO items 1 - no TO was generated)
    Thanks,
    Csaba

  • FORECAST QUANTITY

    Hi
    I am using Oracle Apps 11.5.10.2.
    I am developing an interface for sending forecast details to some external system.
    Here I want to send forecast quantity plus some other information. Forecast quantity is stored in the MRP_FORECAST_DATES table.
    Here comes the problem. single record in this table corresponds to multiple forecast entries. A single record in this table is created with following column values.
    FORECAST_DATE --forecast start date     26-APR-99
    RATE_END_DATE --end date of the forecast       19-JULY-99
    ORIGIONAL_FORECAST_QUANTITY --per bucket quantity    1000
    CURRENT_FORECAST_QUANTITY --Remaining forecast quantity after consumption      1000
    Now This record shows a total forecast quantity of 13000.
    If I want to fetch data for specific date range for this entry then it will create problem.
    Please give me some suggestion for fetching total quantity for desired period.

    please make it more clear. put some example data as in a single record and multiple entries belonging to that particular entry.

  • What is the significance of Quantity reduced  in confirmation tab of a PO

    I have a PO created for a foreign vendor.
    after creating a PO ibd is done and then GRN.
    after GRN user found that he prepared grn against wrong IBD so he cancelled all the GRN he preapred and creates new grn.
    Now in po The open quantity showing as 85 Tons but while creating GRN it is taking only 20 tons.
    After putting all my efforts i found that the difference in the quantity reduced column in Confirmation tab of a PO.
    so Plz let me know how the quantity in this (quantity reduced column in Confirmation tab of a PO.) is updated?????????/
    Or suggest me the solution for preparing the GRN of Open quantity of PO (85 Tons)

    Basically both total GRN and confirmation qty need to be the same, if one of the value is different, than the system will take the highest value and reduce the open PO qty as you can see in MD04.
    if the confirmation qty is to big, then you need to change the confirmation qty, it will then update the open PO qty.
    You may also check to below link ,there's some explanation and example
    path> Vendor ConfirmationsConfirmations from Materials Planning Viewpoint
    http://help.sap.com/saphelp_erp60/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm

  • Quantity reducing second  time- part1register if Excise invoice cancelled

    Hi,
    GR posted, part1 and part2 posted. Later due to  some problem GR reversed. Observed part1 register quantity reduced already. Excise invoice posted again to reverse the part1 entries in j1is, observed debit entries in part2 register.
    Upto here it is fine, now if we canel the Excise invoice, the quantity again getting reduced in part1 register. How can we avoid this please advice
    Regards,
    Sattuj

    Hi All,
    Any other views?
    Regards,
    Sattuj

  • Forecast consumption against CTO item in ASCP

    In source side module (OM, MRP) , following is the observation:
    i) we define a forecast set with consume check box checked for ATO model
    ii) create a sales order for ATO model , configure it .
    The sales order quantity for configured item is consumed against forecast of ATO model.
    I want to do same type(as source) of consumption in ASCP for configured item. Is this possible? I was trying to check this scenario in R12. Following is the setup:
    i) created forecast set with consume check box Unchecked for ATO model
    ii) create sales order for ATO model and configure it .
    iii) run collection
    iv) define plan with plan options ;
    consume by forecast bucket checked and explode forecast check box checked.
    In this above setup, the sales order quantity for configured item is not getting consumed against forecast of ATO model. Is there any thing wrong in setup ? please let me know.

    Abhishek,
    I would revisit this part of your setup for ASCP:
    "created forecast set with consume check box Unchecked for ATO model"
    You just instructed ASCP not to consume this forecast. The source side forecast set must have "consume forecast" selected.
    Starting in 11.5.10 release, Oracle implemented very significant improvements for CTO model forecast consumption. The old MRP process supported forecast consumption for one level in the sales order organization only. Oracle ASCP 11.5.7 through 11.5.9 supported multi-level, multi-org forecast consumption for one source of organizations only.
    So yes, your requirement is supported in 11.5.10 and later releases. ASCP will perform forecast consumption in this order:
    1. Consume the forecast for that specific Configured item (if entered)
    2. Consume the forecast for any remaining sales order demand for the referenced ATO Model.
    3. Explode the bill and consume the forecast for lower level options, subassembly configured items, and ATO models as needed.
    To support this in a multi-org environment you will need to provide a global forecast and appropriate sourcing assignments.
    Regards,
    Kevin Creel
    Come visit us at www.inspirage.com

  • Quantity reduced in PO confirmations

    Hi,
    My problem is that I cannot understand the logic of reduced quantites for PO confirmation when we deal with combinations of partial GRs and partial confirmations.
    We use confirmation control key 0001 with AB order acknowledgement (MRP rel, not GR rel, no GR ***) and LA shipping notification (MRP rel, GR rel, no GR ***).
    We have 2 cases:
    1. GR to WM warehouse
    GR is always done through delivery and LA is used. If we have partial AB, then it is reduced by the GR if the AB delivery date is earlier than the PO schedule line. If AB date is the same or later than schedule line delivery date then the schedule line quantity is reduced and AB is not reduced. This is logical and it works like described in the note 75495 - always the earliest MRP element is reduced.
    2. GR to non-WM warehouse
    GR is done without delivery and there is no LA. In this case no matter what is the delivery date for AB, the AB is ALWAYS reduced with GR. The schedule line is never reduced, even if it is earlier than AB. And this is a mistery for me because it is not according to the note 75495.
    I have configured a new confirmation control key with only order ackowlededgment AB (MRP rel, GR rel, no GR ***) but in this case also always the AB is reduced even though the schedule line has earlier date.
    Can somebody please explain this to me?
    We would like to program upload of order acknowledgments from file and the mixed logic is a problem.
    By the way, could you please advise the best way to upload order acknowledgments AB? As far as I understand from documentation EDI is only suitable for LA upload.
    Thanks in advance for any help,
    Ewa

    Hi,Ewa:
    Please check out SAP note 75495 which talks about the reduction logic in confirmations. Hope this will solve your queries.
    Dick Hua

  • Component quantity reducable in backflush

    Hi All,
    If a materail is not available in stock, users are deleting or reducing a component and saving in confirmation/Backflush.
    How can we controll this, that a component quantity cannot be reduced in business transactions.
    Regards
    Prashant Atri

    Dear Friend,
    Another way it to use the transaction variant. Through transaction variant you can hide the delete icon from confirmation screen.
    If you want further control than through transaction variant the component quantity in confirmation screen you can change to display mode only.
    Hence this way user will not be able to delete or change the component at the time of confirmation.
    Transaction code for creating transaction variant is SHDO.
    Advantage of using the transaction variant is that you don't need the help of Abaper.
    Thanks and Regards,
    Jitendra Chauhan

  • Actual sales qty forecast quantity in a single period calculation

    hi experts,
    i have a report requirement to display the report in below format in bex.
    Jan-05     Feb-05     Mar-05     Apr-05     May-05     Jun-05     Jul-05     Aug-05     Sep-05     Oct-05               
    ACT     ACT+FC     FC     FC     FC     FC     FC     FC     FC     FC               
    3,361       3,807       4,833       4,069       4,491       5,935       4,776       4,926       6,386       6,898            
    312       342       457       381       393       544       439       445       634       676                                                          4,340       5,029       5,132            4,890           5,011             4,910             4,111            2,367             4,432
    say for example we are february
    in the bex report it has to display Actual sales qty for jan and act+forecast for feb and remaining months till december it has to display forecast quantities.
    how can i achieve that in bex?
    NOTE: ACTUAL SALES QTY, FORECAST QTY are two different keyfigures.
    regards

    ******Actuals
      when 'ACC_SAL'.
          if i_step = 2.
            loop at i_t_var_range into st_var_range where
                                        vnam = 'UV_CAL'.
              st_range-sign = 'I'.
              st_range-opt  = 'BT'.
              st_range-low  = st_var_range-low. "cper.
    **** Get Current Week.
    *DT = DT - 27.
              CALL FUNCTION 'DATE_GET_WEEK'
                EXPORTING
                  DATE         = DT     "SY-DATUM
                IMPORTING
                  WEEK         = week
                EXCEPTIONS
                  DATE_INVALID = 1
                  OTHERS       = 2.
    **** Get previous week
              DT = DT - 7.
              CALL FUNCTION 'DATE_GET_WEEK'
                EXPORTING
                  DATE         = DT   "SY-DATUM - 7.
                IMPORTING
                  WEEK         = PRV_WK
                EXCEPTIONS
                  DATE_INVALID = 1
                  OTHERS       = 2.
              if  week+4(2) = 01.
                st_range-low  = PRV_WK.
                st_range-high = PRV_WK.
              else.
                st_range-high = PRV_WK.
              endif.
              append st_range to e_t_range.
            endloop.
          endif.
    *******Forecast
        when 'UNCONDDP'.
          if i_step = 2.
            clear: st_range, st_var_range.
            loop at i_t_var_range into st_var_range where vnam = 'UV_CAL'.
              st_range-sign = 'I'.
              st_range-opt  = 'BT'.
              CALL FUNCTION 'DATE_GET_WEEK'
                EXPORTING
                  DATE         = SY-DATUM
                IMPORTING
                  WEEK         = week
                EXCEPTIONS
                  DATE_INVALID = 1
                  OTHERS       = 2.
              st_range-low  = week.
              st_range-high = st_var_range-high.
              append st_range to e_t_range.
            endloop.
          endif.

  • ASCP Plan Is Not Able To Read Global Forecast For Options Published By Demantra

    ASCP plan is not able to read global forecast for options published by Demantra
    ASCP plan is not able to read global forecast for options published by Demantra. Only Model Forecast is being read into ASCP plan. 
    1) We are publishing global forecast from Demantra at CTO/Zone/Week level and it is getting published properly to ASCP denorm table. 
    2)There is no forecast explosion being done in ascp (plan option explode forecast is not checked) 
    3)The sourcing rule is set at zone level for the model saying source from an organization (org code 11) 
    4) The profile: msc:-Organization containing generic BOM for global forecasting is set to 22 which is a reference org 
    5) Now when we run the plan the model forecast goes to org 11  but the option forecasts do not go properly 
    6) We have just one line created for the option (production forecast) with a wrong quantity
    7) Demantra has forecasts for both Model and options

    Looking at the error message "The Network Adapter could not establish the connection" , It appears hostname and port may be incorrect. Review the targets.xml under E:\oracle\product\10.2.0\db_1\SAP_solman_SDB\emd and
    emoms.properties under E:\oracle\product\10.2.0\db_1\SAP_solman_SDB\config folder to make sure host ( sap_solman) and port (1527) are correct.
    As far as setting the environment variables goes, you can go to control panel -> system -> advanced -> environment variables and set the ORACLE_HOME and ORACLE_SID
    -Ramesh

  • Forecast delivery schedules incorrect cumulative release quantity.

    Hi Gurus,
    We implemented the standard LZM - Scheduling agreement with delivery orders solution for component suppliers.
    The entire SAP standard configuration activated and the functionality is working correct.
    u2022     Scheduling agreement type LZM  / Item category LZMA / Schedule line category  L2
    u2022     Order Type TAM  / / Item category TAMA / Schedule line category  CP
    Example:
    Scheduling agreement forecast delivery schedule for 1000 units./ Md04 show SchAgr of 1000 units
    Delivery order for 250 units (MD04 Shows Order for 250 units and SchAgr for 750 Units)
    Created delivery for the order (MD04 shows Deliv. For 250 units SchAgr for 750 Units)
    Goods issue the delivery / MD04 shows the SchAgr for 750 units.
    *Issue:*
    When we update the Cumulative quantity received by the customer it is summing up with the forecast quantity (double counting the shipped quantity).
    When the Cumulative quantity received by the customer updated to remove the in-transit quantity, the forecast is adding by 250 units and   MD04 shows SchAgr for 1000 units.
    Thanks & Regards
    Suresh

    Hi Suresh
    The *** issued qty gets updated when the PGI for the delivery happens. There is a field called *** received by customer and it gets updated when customer sends the *** back in the 830 or 862 as the case may be.
    The difference between the *** issued and the *** recieved is always shown in transit.
    If you do not want the schedule line to be opened up, then in *** recd change it to the *** issued or ideal option is populate the last delivery PGI'd on the delivery number field next to *** recd field. Hope this helps and let me know if you need any more informataion
    Regards

  • Question on Inline forecast consumption in ASCP

    Hi,
    We are trying to test the option of cosuming the forecast in ASCP.
    We currently have the forecasts consumed in the source i.e. at the forecast set by the planning manager. But we have new requirement that for some of the organizations, we would like the forecast to consumed in the plan NOT at the forecast set.
    So, can you please suggest how we can do that? And what are necessary setup steps or profile option settings that we need to do the forecast consumtion in the ASCP plan.
    Below are couple steps that I tried but the forecast consumption does not happen in ASCP.
    1. Stoppped planning manager
    2. Checked "Consume by Forecast bucket" on the Main tab of the plan options
    3. Set the values for Backward and forward days as 5 and 5
    4. Turn off the "Consume" option on the forecast set.
    I really appreciate you review and suggestions on this.
    Regards,
    Anand.

    Hi
    4. Turn off the "Consume" option on the forecast set. -- I did nt test recently but this in source FC set should be checked is wht I remember..
    also It does nt mater it gets consumed in source or not you will anyway collect orig FC qty and ascp will consume accoridng to plan options.
    Thnx
    Partha

  • Unrestricted quantity not reducing in MMBE

    When we are reserving materials through maintenance order (IW31),
    we can see the reserved quantity through MMBE.
    but the unrestricted quantity remains the same and does not reduce.
    This is not correct. If we are reserving a material in the maintenance
    order, then its unrestricted quantity should reduce and the reserved
    quantity should increase.
    This is not happening in our current scenario.
    For e.g
    if there is a material A and it has unrestricted quantity as 2.
    If i reserve 1 quantity through maintenance order.
    Then its unrestricted quantity should reduce to 1 and reserved quantity should increase to 1.
    but when we view the MMBE transaction, it shows quantity 2 in unrestricted and 1 in reserved.
    Shouldn't the unrestricted quantity reduce to 1??
    Please advise.

    Hi,
    I have done further investigation and found something further wrong with this.
    E.g, Material A has unrestricted stock as 5.
    I createa a reservation for 1 through maintenance order.
    So, effectively, unrestricted stock = 4 and reserved  stock = 1 (total = 5)
    But SAP (MMBE) is showing unrestricted stock = 5 an reserved stock = 1 (That means I have quantity 6 in total !!!!!!!!!! which is wrong)
    Now, I do an unplanned goods withdrawal agains cost center for quantity 5. SAP lets me do it. Ideally, it should give me altleast a warning that quantity 1 is reserved.
    Now when i do my planned goods issue for the maintenance order, it gives error 'deficit stock'.
    This is wrong business process!! If i have reserved quantity 1, how can somebody else issue it??
    Please advise,
    Many thanks.

Maybe you are looking for