Incorrect Processing lead time showing in ASCP exception

Hi All,
We have a buy Item say TEST01 which is used in two Different organization A and B and its processing lead time at item level and ASL it 10 for Org A and 111 for Org B,
However issue is when we run collection plan for Org A and check for ASCP exception for item TEST01 for Org A its processing lead time is coming as 111,
Could you please help me with this.
Regards

Are you using Global or Local ASL because only global are supported. Plus do you see any demand pushed out because of a long lead time?
Also can show the screenshot of the lead times both at item level and asl level for all the orgs.
Thanks,
Abhishek Sharma

Similar Messages

  • Impact of not defining Processing Lead time at ASL

    Hi All,
    We have a scenario where we have defined Global ASLs for different Orgs with Same supplier site due to this ASCP is considering incorrect Lead time,
    So as to get the correct Lead time we are planning to remove Processing Lead time from ASL so that ASCP will consider correct Lead time from Item level,
    I wanted to know is there any other impact of disabling Processing lead time at ASL Level.
    Regards,
    Nilesh

    Check the PCR TE20......

  • Supplier Processing Lead Time with ASCP Unconstrained Plan

    Hi All,
    Is it possible for unconstrained plan to consider supplier lead time constrained which we define in ASL?
    I have defined an Unconstrained Plan & the plan is not considering Item Level , ASL Lead times & generating the planned Orders to meet demand due dates by compressing the Lead time.
    Constraint option is not checked in plan options.
    Appreciate your advise on this issue.
    Regards,
    Pranay Saxena

    Hi Pranay,
    An unconstrained plan cannot have ANY constraint.
    So it is not possible to have just the supplier lead time as constrained.
    Alternatively, if that is what is your requirement, you may run a constrained EDD plan with just the material constraints enabled and the "Enforce Purchasing Lead Time" Flag checked.
    If the supplier capacity is NOT set.. it will be treated like infinite..
    This way you will force the engine to respect the lead times from ASL and acheive a near unconstrained plan.
    Another alternative is use constrained plan as explained above and set the profile MSO: Lead Time Control to Do not Violate Minimum processing LT... in this case even the processing LTs for the MAKE items are also respected.
    Hope that helps.
    Regards,
    Mohan Balaji
    NOTE: Please mark the post as Helpful or Answered if the update has really helped you. This would also bring the thread to logical conclusion and will be helpful for the viewers.

  • How to include process lead time in an outside processing amount resource

    Problem:
    We have a two operation routing where the first operation is time based and the second operation is an amount based outside processing resource. The outside processing resource has an outside processing item associated with a fixed lead time. When we run an ascp plan, the generated planned orders only consider the first operation (the time based one) to calculate order completion date and excludes second operation lead time (the amount based one).
    Any ideas?
    Edited by: 785198 on 14-ene-2013 1:05

    This is fine if you raise exception from your code. It will be raised as a server fault only.

  • Item master - processing lead time vs po_asl_attributes - processing lead time

    hi.
    would greatly appreaciate if somebody can explain the relationshipship between mtl_system_items.processing_lead_time (item master) vs
    po_asl_attributes.processing_lead_time (approved suppliers list)
    which one takes precedence.
    thanks in advance
    zj

    The asl takes precedence

  • ASCP Taking Lead time to buy Item from Item Level and not from ASL

    Hi All.
    We have a buy Item Which is used at multiple Organization now we have defined processing Lead time for this Item at Item Level and ASL level (Global) However for different organization Like ABC and XYZ we have same supplier and Supplier Site for this item,
    Below is the details of Item
    Item's Processing Lead Time at Item Level
    Org - ABC - 35
    Org - XYZ - 15
    Item's Processing  Lead Time at ASL Level
    Org - ABC - 10
    Org - XYZ - 5
    Now when we run ASCP plan for org XYZ and check for exception, Item's Lead time is coming from Item Level (15) not from ASL Level (Does this is expected behavior from Oracle?)
    Regards.

    Hi Abhishek,
    I tested one more time with the same scenario, this time ASCP is considering Processing lead time form ASL only however it is considering processing lead time for another organization (When I am running ASCP plan for Org XYZ ASCP is considering Processing lead time for ABC).
    Does it is due to same supplier site for both the organization?
    Also it has an active sourcing rule for the same supplier
    Regards.

  • Planning time fence vs total lead time

    Hi Gurus,
    we have a scenario like the below in the unconstrained plan. Trying to understand various dates on the PWB. could you please explain.
    1. Item is a Make item and it's planning time fence attribute is set as Total Lead time.
    2. Processing lead time of the item is 25 and fixed lead time is 2
    3. ASCP is suggesting a planned order on PTF date which is exactly 25 days from now.
    4. But the suggested start date of the order is only 2 days less than the suggested due date. This is the point we are not able to understand. We have set the processing lead time as 25 so, isn't the planned order not supposed to have the start date as today?
    Thanks
    Mahesh

    Dear,
    Please refer this link,
    [Planning time Fence|Planning time fence]
    For sales order will convert to a specific production order use CO08 here define order type as ZP04.
    OPKP ( Production Scheduling Profile) whether ZP04 is assigned under Order Type or not.If not maintain the same and then assign the same Production Scheduling Profile in Material Master in Work Scheduling view.
    Also in In OPPQ or OPPR you have to define order type as ZP04 under conversation indicator use when in MRP run MD50.
    Please try and come back
    Regards,
    R.Brahmankar

  • LTP run ignoring GR processing time and Lead time

    Hi,
    I am trying to find out way to create a planning scenario (MS31) and run LTP (MS01) which will ignore the GR processing times and Lead times from Material master.
    I would like to use MCEC report (after running MS70 valuation) which will show the values only in my new fiscal year - for budgeting purposes. Currently because of the long GR processing times and Lead times in material master (sometimes even 60 days) - some planned values show in MCEC report 2 or 3 months before the new fiscal year and the last two periods of new fiscla year are empty.
    I would be grateful if you could help me with getting rid of these additional Times and adjusting the periods only for Report purpose. The desired final output should be that S012 table for this specific planning scenario has the values only in periods of the Fiscal year - without hitting previous Fiscal year last periods (due to lead /GR processing times).
    Thank you,
    Karol
    Edited by: Karol on Oct 12, 2010 2:50 PM

    Dear,
    Master data is taken from normal MRP views. there is no other setting is available. you can create a different matrerial number for LTP planning.
    Raj

  • PO output message (Fax) showing status- incorrectly processed.

    Hello,
    I'm unable to send the PO output through fax.
    Processing status shows- "2 incorrectly processed".
    I checked the fax number and necessary configs and are correct. Moreover there are two messages triggered for same Po. one is processed while the other one is getting error.
    Can anybody suggest what might be the issue?
    Regards,
    Nilesh
    Edited by: Nilesh B on Jun 1, 2010 12:23 PM
    Edited by: Nilesh B on Jun 1, 2010 3:56 PM

    Hi Nilesh,
    Can you see from SOST how many attempts were made to send the fax? Sounds like the fax number was busy at the time, preventing the fax from being sent. If 2 faxes were created from the same PO, were they both going to the same number? If so, this may be the cause as both would be trying to dial the same number at the same time.
    If you try and reprocess the message from SOST does it go through? If so, this is definitely an issue linked to the fax number being busy.
    Rob

  • Material report showing lead time & min order quantity?

    Hi,
    Is there a report which I can download which shows by material, the lead time and minimum order quantity?
    Thanks
    Keeley

    We don't have access to any query writing so if it's not possible to get both fields on one table, can I run two reports?
    OR...
    is it possible to change the ME1M report to display/export horizontally in a table type format rather than wrapped?
    Edited by: Keeley B on Sep 23, 2009 7:58 AM

  • Incorrect delivery dates and lead time in SC & PO for Internal Catalog

    Hi experts,
    In a scenario,
    In SRM 4.0 creating SC from Internal catalog and from that SC po is created.
    The information reflected in SAP is not accurate with the information in mysupply catalog.
    PO's related to a vendor catalog is supposed to be 45 days (lead time) but in some cases of POs the lead time is showing 2 days. There's no consistency in information because some PO's in 45 days and some POs having 2 days though the POs are in same dates.
    Can you please give me some solution to this problem.? And Also the details How to approach to find out with tech debug.
    Thanks,
    Charles.

    Hi experts,
    In a scenario,
    In SRM 4.0 creating SC from Internal catalog and from that SC po is created.
    The information reflected in SAP is not accurate with the information in mysupply catalog.
    PO's related to a vendor catalog is supposed to be 45 days (lead time) but in some cases of POs the lead time is showing 2 days. There's no consistency in information because some PO's in 45 days and some POs having 2 days though the POs are in same dates.
    Can you please give me some solution to this problem.? And Also the details How to approach to find out with tech debug.
    Thanks,
    Charles.

  • MD04 dates not showing lead time scheduled dates

    Hi experts,
    In my MD04 screen, dates are not showing lead time scheduled dates (showing only basic dates scheduling) even after MRP run with lead time scheduling.
    Please let me know if there is a way that the date column in MD04, shows the finish date from lead time scheduling.
    thanks
    Jay

    Hello
    Production dates are not displayed on MD04.
    You can include additional fields on MD04 using a BAdI and you can use your own logic to add the production dates.
    You will find the relevant BAdI on the following document:
    BAdIs for MRP
    BR
    Caetano

  • ASCP Yield and Resource Lead Times

    Hi,
    I am working on Advanced supply Chain Planning on R12. Both ERP Source and Planning are on different instances. We are also using Oracle Shop Floor Management. In the Network Routings we have included a lead time resources at step 10, 20, 30. The resources are as follows:
    These resources are defined as 'Machine'
    Resource for operation 10: ASSY-LT, 112 hours, Schedule 'yes'
    Resource for operation 20: TEST-LT, 64 hours, Schedule 'yes'
    Resource for operation 30: PACK-LT, 48 hours, Schedule 'yes'
    We also have only one shift with 8 hours. The resources are not available for 24 hours.
    We also have yield at each of the above operations.
    Lead time rollup calculates 28 days for the item correctly.
    We are encountering a problem with ASCP Plan. The start dates and yield calculations using constrained plan with Enforce Demand Due Dates constraint seems problematic. If we check 'Calculate Resource Requiremnents' option, the plan calculates yield but the lead time gets reduecd by one third and start and completion dates for a planned order (and ATP etc.) are not accurate.
    If we uncheck 'Calculate Resource Requiremnents'option in the plan, lead times are accurate but plan does not calculate yield.
    We are not sure what is causing the problem.
    Does anybody know what options or profiles control this behaviour?
    Your help is highly appreciated.
    Thanks.
    Vijay

    Hi Vijay,
    important for your lead time calculation is the setup of the calendar and shifts and what shifts are assigned to the resource.
    You say you do not have enabled the 'Available 24h' option. We are also using leadtime resources in certain cases, for example LT for Assembly. But in these cases we enable the 24H option. Next to this we set the Resource capacity to 'unlimited' by setting units to a very high number (1000 etc.) on resource level, to prevent that the system gets into capacity conflicts here.
    And the yield calculation indeed should be quite independent of the leadtime resource.
    best regards,
    David.

  • Addional lead time for Sales BOM kitting process

    When a Sales Order BOM Sales Order is scheduled, we would like to have a lead time added for the Shipping kitting step.  So the pick date will be X number of days before the ship date.
    Is there a way to do this is ?
    Thanks,
    Doug Karien.

    Hi DK,
    Go to Ent structure > Definition > LE > Define shipping point, choose your shipping point, click on detailsand check there, "Rounding work days" filed may provide you some soln.
    Regards
    SD

  • Sales order is not taking shipping transit lead time into consideration

    Hi,
    We have following scenario -
    1. Sales order is created in AT organization.
    2. There is no onhand in any of the organizations including AT.
    3. The scheduled ship date for sales order comes as order creation date + item lead time = 15-Sep-2011.
    3. PO for sufficient quantity is available at UK org with need-by date as 01-Jun-2011.
    5. Post processing item lead time for this item is 1 day.
    4. intransit shipment is setup between UK and AT.
    5. Shipment Transit lead times are also set up at 3 days between locations of UK and AT.
    6. ASCP plan is run.
    7. Sales Order is unscheduled and rescheduled via API MSC_ATP_PUB, which takes the ATP details from UK (based on the sourcing rules). The sheduled ship date comes as 02-Jun-2011 (PO need-by date + 1 day of post processing).
    8. Expectation is that API should also take transit lead time into consideration while calculating the ATP dates and hence the Expectation is that scheduled ship date should come as 05-Jun-2011 (PO need-by date + Transit lead time + 1 day of post processing).
    Please let me know
    a. if this is standard functionality of oracle or not.
    b. if this is standard functionality then what setups are missing required for the same to be achieved.
    UAT is held up for this issue. Please help urgently.
    Regards.

    Oracle is supposed to take the in-transit time into consideration.
    Are you running a constrained plan or an unconstrained one?
    Make sure you defined the inter-org network as described in http://download.oracle.com/docs/cd/A60725_05/html/comnls/us/inv/shipne01.htm.
    or go to Inventory > Setup > Organization > Inter-Location Transit Times and enter it there.
    Sandeep Gandhi

Maybe you are looking for