Heuristics shifts SNP Planned Orders to today.

Hi,
I am facing a situation where, for a demand in 2011, when i take a manual heuristics(interactively in SDP94), planned orders are created correctly (using Lot-for-lot procedure).
However, during the daily heuristics job, all these planned orders are shifted to "right now"- with start date today and ending 4 days hence as per master data. This is within the SNP Production horizon of 21 days.
Please guide me to what setting could be causing this.
Regards,
Shivaditya Singh

HI
DO you running the Determination of low code level (/n/sapapo/snpllc) before running the SNP Heuristics.
Run this program , Low level define the planning sequence for location product.
Regards,
MJ

Similar Messages

  • SNP Planned order start and end dates are not calculated correctly

    Hello SNP Guru's
    The SNP planned orders generated after the Heuristics run, have a start and end date based on the Activity Duration (Fixed), while the resource consumption is based on the Bucket Consumption (Variable), which is correct.
    The Activity Duration (Fixed) is based on the BOM Base Quantity. So if the Activity Duration = 1 day, and if the order quantity is more than a day, the start and end dates, still shows as 1 day. So no matter what is the order quantity, the start and end dates is always = 1 day.
    Does anyone have any experience in implementing any code to change the start and end dates on SNP Planned Order?
    Seems like it should work as standard.
    Am i missing something?
    Thanks,
    Mangesh

    Dear Mangesh,
    SNP is a infinite planning tool. If you have defined fixed duration to be 1 DAY in the activity, no matter how many quantity you input for your planned order, the order will last for one day. If the resourced is overloaded, you then run capacity levelling to
    banlance the capacity. What your expected beahavior happens in PPDS planning.
    Claire

  • SNP Planned order not following resource bucket capacity/factory calendar

    Hi gurus,
    SCM 5.0
    I am running SNP heuristics for a product and expecting planned orders for it.  It has corresponding production data structure and multimixed resource.  The resource has an assignd factory calendar and SNP bucket capacity.  The bucket capactiy availablity dates of the resouce is consistent with the factory calendar workdays/holidays.  Using simple lot for lot strategy, I am expecting heuristics to schedule the planned orders on the dates of the demand in compliance with teh SNP bucket capacity availability of the resource.  APO does not schedule on holidays consistent with bucket capactiy.  This is true until...
    We have a public holiday in factory calendar that needs to become a workday. To remedy this, we put a special rule for the factory calendar and explicitly made that holiday into a workday.  The changes were synchronized with APO, and this is also reflected in the bucket capacity of the resourc: former holiday now has bucket capacity after the calendar change.  However, when running heuristics, it still does not create SNP planned order on that former holiday that has been changed into workday.  Even if it is a public holiday, there is already a special rule for the factory calendar and the resource bucket capacity reflects this correctly. But SNP heuristics seems not to follow this change.
    Any ideas on this? looks like a bug.

    Hi Edgar,
    Yes, when your resource reflects the addional capacity of the holiday turned working day, then it is expected to be considered for the SNP planned order.
    Instead of SNP heuristics, you may try to check interactively in SNP planning book, if manual order creation in the bucket works out.
    Since this is a mutlimix  resource , it can also be checked if in PPDS planned order can be created on the day.
    The above checking may not solve your problem , but will get to know if at least manully the bucket is being considered or not.
    regards
    Datta

  • SNP Planned Order

    Hello Experts,
    Scenario: we plan finished goods in SNP & for component level we run MRP in ECC.
    I need to understand how MRP does planning in ECC based on SNP Planned order. Why MRP run does detailed scheduling on Finished goods planned order which released from SNP?
    I am not getting why MRP in ECC considers material which has X0 MRP type & it does detailed scheduling on finished good planned order & it changes start date & time of planned order which push back or forward sometime in SNP.
    Can anyone explain why MRP does detailed scheduling on finished good planned order? And after sheduling why it changes start Date & Time?
    Thanks in Advance
    Regards
    Sujay Joshi

    Dear manimaran
    I am going through the same scenario as joshi....component planning is done by MRP and planning for final product is done by SNP and PP/DS......say i have planned order from SNP and PP/DS
    1. can i subject those planned orders to MRP run again by bringing back to ECC
    2.If its is possible how do i see what is the screen wherein i will see that planned orders from SCM has arrived to ECC
    3.what tcode do i use to subject those scm planned orders to MRP run
    I have detailed a implentation procedure i would be happy if you can say if it is logically correct,if it is not correct then which is the correct logic.
    Planning will be divided into two parts ,Plant level planning and supply chain planning, for Plant level planning traditional MRP run is mandatory to determine the requirements at the plant level.
    DMS (Distributor management system ) to be used by all customers
    Capture the demand from all the market segment  into DMS and upload the demand in SCM
    Create a demand plan in APO and release it in SAP R/3 Demand management after confirming the demand.
    Maintain material master for all the materials on demand.
    Maintain relevant production version in C223
    Run traditional MRP
    Calculate exact  quantities by creating production order in R/3.
    Transfer the quantities  required for specific time period alone to APO,for example if you want to allocate capacity to run 4 shifts transfer the approximate value of quantity alone to APO, the time period may be for 7 shifts or 1 month ,which is industry specific. 
    Perform simultaneous capacity and material planning in PP/DS  (or)
    After rough cut planning in APO, SNP perform simultaneous planning in APO , PP/DS ,using any one of standard heuristic like PP_001 or MRP_001 or PP_002
    Adopt planning procedure =3
    Confirm the production order in R/3
    thanks
    Saravanan

  • Creation of SNP planned order based on PDS

    Hi,
    I'm a APO developer and I have the following problem:
    I would like to create a SNP planned order based on a PDS (like e. g. in the planning book when you input a number into a cell in the "Production (Planned)" line).
    Up to now I've only managed to create such an order without using the PDS.
    Can you name me a function module which allowes me to do that?
    Thanks in advance.

    Hi,
    I've now managed to create this kind of order.
    I set a breakpoint at the function module /SAPAPO/DM_PROD_ORDER_CHANGE and checked how it was filled in the planning book.
    For those who want to know:
      INCLUDE /sapapo/constants_om.
      CONSTANTS:
        lc_order_type_1f        TYPE /sapapo/om_order_type VALUE '1F'.
      DATA:
        ls_prod               TYPE /sapapo/msnp_prod,
        lt_prod               TYPE /sapapo/msnp_prod_tab,
        ls_sources            TYPE /sapapo/sources,
        lt_sources            TYPE /sapapo/sources_tab,
        lv_matid              TYPE /sapapo/matid,
        lv_locid              TYPE /sapapo/locid,
        lv_vrsioid            TYPE /sapapo/vrsioid,
        lv_tstfr              TYPE /sapapo/timestamp,
        lv_tstto              TYPE /sapapo/timestamp,
        lv_simsession         TYPE /sapapo/om_simsession.
    lv_vrsioid = '000'.
    * Create SimSession
    CALL FUNCTION '/SAPAPO/TSIM_SIMULATION_CONTRL'
        EXPORTING
          iv_simversion              = lv_vrsioid
          iv_simsession             = lv_simsession
          iv_simsession_method = 'N'
          iv_perform_commit       = space
        EXCEPTIONS
          lc_connect_failed        = 1
          lc_com_error             = 2
          lc_appl_error            = 3
          multi_tasim_registration = 4.
      IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    * Get PDS
      CALL FUNCTION '/SAPAPO/MSDP_SNP_PPM_VALIDITY'
        EXPORTING
          iv_vrsioid      = lv_vrsioid
          iv_matid        = lv_matid
          iv_locid        = lv_locid
          iv_tstfr        = lv_tstfr
          iv_tstto        = lv_tstto
          iv_planstart    = lv_tstfr
          iv_planend      = lv_tstto
        CHANGING
          ct_sources      = lt_sources
        EXCEPTIONS
          wrong_interface = 1
          error_occured   = 2
          OTHERS          = 3.
      IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      READ TABLE lt_sources INTO ls_sources INDEX 1.
      ls_prod-version       = lv_vrsioid.
      ls_prod-matid         = lv_matid.
      ls_prod-locid         = lv_locid.
      ls_prod-plobid        = '9AMALO'.
      ls_prod-tstmp         = lv_tstfr.
      ls_prod-catgr         = 'PP1'.
      ls_prod-categ         = 'EE'.
      ls_prod-categ_prku    = 'EE'.
      ls_prod-categ_prse    = 'EL'.
      ls_prod-kz_prod       = '9APPROD'.
      ls_prod-kz_prku       = '9APPROD'.
      ls_prod-kz_prse       = '9ADMDSE'.
      ls_prod-produ         = '1000'.
      ls_prod-proid         = ls_sources-trpid.
      ls_prod-mosta         = gc_new.
      ls_prod-order_type    = lc_order_type_1f.
      ls_prod-is_fixed      = 'X'.
      ls_prod-snp_is_header = 'X'.
      APPEND ls_prod TO lt_prod.
      CALL FUNCTION '/SAPAPO/DM_PROD_ORDER_CHANGE'
        EXPORTING
          ic_database           = 'LC'
          ic_application        = '4'
          iv_simsession         = lv_simsession
          it_prod               = lt_prod
          iv_netch              = 'X'
        EXCEPTIONS
          material_not_supplied = 1
          location_not_supplied = 2
          OTHERS                = 3.
    * Merge simulation version (to commit order changes)
      CALL FUNCTION '/SAPAPO/TSIM_SIMULATION_CONTRL'
        EXPORTING
          iv_simversion                = lv_vrsioid
          iv_simsession                = lv_simsession
          iv_simsession_method         = 'M'
        EXCEPTIONS
          lc_connect_failed            = 1
          lc_com_error                 = 2
          lc_appl_error                = 3
          multi_tasim_registration     = 4
          target_deleted_saveas_failed = 5
          OTHERS                       = 6.
      IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.

  • Bapi for sfg dependent dem,snp planned order qty, and ppds planned orde qty

    Hi Gurus,
    I am not much familiar with APO, so please help me,
    Input details:
    Field                         Value     
    Planning Version     000     
    Source Location *     1001     Single/Multi Value
    Product *                          1000061     Single/Multi Value
    Production Planner *     PRC     Single/Multi Value
    Start Date *          
    End Date *          
    o/p:
    Source Location     Date     Semi-Finished Material     Material Description     SFG Dependent Demand     SNP Planned Orders qty     PPDS Planned order Qty     Total SFG Variance due to Lot size     Total SFG Variance reference to dependent demand
    1001     15-Jul-10     1000041PP     PRIMARY FF MILK  3% FAT     340     412     420     8     80
    1001     15-Jul-10     1000041PP     PRIMARY FF MILK  3% FAT                         
    1001     15-Jul-10     1000041PP     PRIMARY FF MILK  3% FAT                         
    Is there any bapi to fetch the data as shown in o/p.
    Thanks

    Hi Phani,
    Tryout the below BAPIs
    IF10503 (object)
    BUS10503
    Regards
    R. Senthil Mareeswaran.

  • To build query related to SNP: Planned Order

    Hi,
    System: SCM 5.0
    Scenario: SO received at plant and planning creates PR against SO at plant and accordingly SNP:Planned Order at Vendor location. If SO is cancelled/deleted (manually), sometime only the PR gets cancelled/deleted (automatically during planning run) but corresponding SNP:Planned Orders still remains at vendor location and so the dependent requirements. PR and Planned Orders are pegged to SO so one-to-one relation is maintained.
    I could not find any reason why system is not deleting Planned Order at vendor location despite SO and PR is deleted at plant location. So I am planning to build query where SNP:Planned Orders are not pegged to any PR or SO.
    Can anyone help with list of SNP:Planned Order tables so that I can build query around it to identify ghost Planned Orders.
    Hope I was clear with my query but let me know if any further information is require.
    Thanks and regards,
    Devang

    HI Marius,
    Sorry for delay reply.
    I was working on on some other more critical issues to business.
    Finally we decided to built report to identify obsolete Planned Orders for which PR is not available in ordering plant. I have listed below logic for that report:
    Get Location ID from table /SAPAPO/LOC based on Location entered in selection screen
    Get PEGIDs from FM /SAPAPO/DM_MATLOC_GET_PEGIDS based on IV_SIMID as 000 and location id from step 1
    In FM /SAPAPO/OM_PEG_CAT_GET_ORDERS, use SIMVERSION as 000 and in Import Para IS_GEN_PARAMS insert all PEGIDs from step 2.
    From Export Para ET_PEG_INPNODE take From_OrderID and store in internal table.
    Execute T.Code /SAPAPO/RRP4 with following selection (Use Selection Variant: OBSOLETE PR and add Location as entered in Selection Screen)
    Planning Version: 000
    From: Current date – 60 days
    To: Current date +180 days
    Location: 0000201328
    Product: *
    Order Type: 1F
        6. Compare output of step 4 and step 5 and display result.
    From FM /SAPAPO/DM_MATLOC_GET_PEGIDS the output (step 4) will be Order ID (22 characters) while step 5 (T.Code /SAPAPO/RRP4) will give Planned Order number (8 character). I am not sure how to compare Internal Order ID (22 characters) for corresponding Planned Order Nos. (8 characters).
    I have not marked your post as correct answer as still need to find answer of above query.
    Thank you in advance for your guidance.
    Regards,
    Devang Shah

  • Unable to convert SNP planned order to PP/DS planned order in RRP3

    Hi,
    This is an in-house production scenario. SNP planned order are created based on forecast, now i want to convert those SNP planned orders to PP/DS planned orders in product view. While converting i am getting the following error message.
    Conversion canceled with error
    Message no. /SAPAPO/RRP707
    I have checked the SNP, PP/DS PDS, it looks good.
    Regards,
    LV

    Hi Lingaiah,
    Conversion SNP -> PP/DS SAP002 is scheduling heuristic
    Heuristic for Conversion SNP->PP/DS  as SAP_SNP_SNGL used for order conversion.
    Regards,
    R.Brahmankar

  • Issue in Deployment of SNP Planned orders

    Hi Experts,
    I am trying to deploy SNP Planned orders and I have made relevant settings in SNP2 i.e. ATP category in ATD Receipt.
    When I run deployment, it creats deployment stock transfer (DEP: PReq / DEP:ConRl) based on available stock first. When I run deployment second time, then it creats deployment stock transfer( DEP: PReq / DEP:ConRl)  for SNP Planned order with the same quantity of stock & not for entire quantity of SNP Planned order. Please refer below example to make it clear
    Total Demand at destination location = 600
    Stock at supply location = 100
    After planning run, Purchase requsition of 600 is generated at destination location.
    At supply location, SNP Planned order of 500 is generated considering 100 stock is available against PReqRel of 600.
    When I run Deployment first time, it forms DEP: PReq / DEP:ConRl  of 100 based on available quantity of 100.
    After running Deployment second time it forms again DEP: PReq / DEP:ConRl  of 100 and it continues to create deployment stock transfer till it completes the quantity of SNP planned order.
    So all together it creates 6 deployment stock transfers instead of forming one deployment stock transfer (stock+ SNP Planned order).
    There is no lot size setting for product master.
    Can anyone suggest whether I need to do some settings to get one deployment order instead of 6.
    Thanks & Regards,
    Chetan
    Edited by: Chetan Patil on Nov 10, 2010 4:45 PM

    Hi Chetan,
    It looks the SNP planned order is not being considered in the receipts quantities  to be available for deploying against requirements.
    Please check SNP order  ATP type( it  is normally EE)  is included in the appropriate Categroy group
    IMG >> APO > Supply Chain Planning  > SNP > Basic Settings > Maintain Category Groups
    Example :  ATD Receipts:   ATR
    Typical values :    AI, AJ, BF, CC,EE,EF, EI
    Secondly, in the transaction /SAPAPO/MSDP_ADMIN, in the Key Figure detailed  tab, ATD Receipts should have assigned the Category Group(say  ATR).
    Regards
    Datta

  • Converting SNP Planned Order /Purch Req to Prod.Order/Purch.Order

    Guys
    What is the standard process to Convert the SNP Planned Order /Purch Req. into a Prod.Order/Purch.Order ?
    Can the conversion indicator be set in APO for SNP Planned Order /Purch Req.and then transferred to R3 as Prod.Order/Purch.Order  or can the convesrion of Planned Order /Purch Req to Prod.Order/Purch.Order  can be done in R3 itself ?
    I am not clear on how exactly this works. Would appreicate if you could provide me with the standard process and any config involved in the same such as Number Ranges and how to set the conversion indicator automatically through SNP planning runs ?
    Thanks

    When you set this indicator for a planned order or a purchase
    requisition, the system automatically converts the order into a
    Production order or purchase order after the transfer to the
    connected SAP R/3 system.
    The converted orders are then retransferred to the SAP APO system with a
    different category; a purchase requisition with category BS-ANF becomes
    a purchase order delivery schedule line with category BS-EIN.
    Please check configuration setting in SPro for transfer setting to R/3.
    1. Configure Transfer to OLTP Systems(SNP)
    2.Maintain Global Parameters and Defaults(PPDS)
    Also on R/3 side you can see it in MD04/MD07 collectively for a product . or individually on
    MD13 : planned order
    MB51n: PR
    Manish

  • Deployment of SNP Planned orders

    Dear Expert,
    We have one scenario where there is a requirement to deploy SNP Planned orders. How much it is advisable to deploy SNP Planned orders?
    What will be the impact on the dates of shipment proposals made by TLB, when SNP Planned order will get converted in Planned order and production order.
    Also I observed one strange behaviour of deployment, when I try to deploy planned order by putting ATD receipts as planned order in SNP2 tab, some times it considers the planned order for deployment but many time it doesn't.
    Is there any specific settings other than ATD reciepts in SNP2 tab of product location master data?
    Thanks & Regards

    Dear Samuel/Amol,
    Thanks for your reply. Let me frame this question again
    Letu2019s consider that I have maintained SNP planned orders in ATD Receipts. After running deployment, system will look for SNP Planned order as receipt element in Pull deployment horizon and create DepConRel .  TLB only considers DepConRel for conversion into STO, irrespective of stock is available or not.
    Now consider the situation where STO is ready with some specific Delivery & committed dates but there is no stock. When SNP Planned order will get converted into planned order and Production order, its date will change and actual stock may not be ready on that specific committed date.
    So my entire intension is to know how much it is advisable to deploy SNP Planned order.
    Samuel/Amol, did you get a chance to work on SNP Planned order deployment and its impact on the dates of STO?
    Thanks & Regards,
    Chetan

  • Creating SNP planned order using ''BAPI_MOSRVAPS_SAVEMULTI3'

    Hi Experts,
                      I am new to SAP-APO, kindly clarify my question. I am using 'BAPI_MOSRVAPS_SAVEMULTI3' with source of supply PDS for creating SNP planned order by passing 'EE' in the  table parameters 'ORDER_HEAD-MASTER_ATPCAT'. It is creating a planned order which is PPDS planned order with number range starting from '1000...' rather than creating SNP planned order with number range starting from '8000..'. Please let me know what might be the reason for the BAPI misbehaving incorrectly. Also kindly let meknow what are specific parameters to pass to above bapi to create SNP planned order.

    Hi,
    The BAPI BAPI_MOSRVAPS_SAVEMULTI3 is used for creating PPDS inhouse orders.
    You will have to use BAPI_MOSRVAPS_CREATESNPORDER for SNP inhouse orders creation from SNP PPMs( there is no explict mention of SNP PDS- you may please check).
    Regards
    Datta

  • Source of Supply for SNP Planned Order

    Hi All,
    I have a situation where we are feeding SNP planned orders using /sapapo/lcin (Time series to Order Network). When we use this transaction SNP planned orders are created in SNP but PDS is not attached to such orders. I would like to know how can I get PDSs attached to SNP planned orders created?
    Regards,
    Harshil Desai

    Thanks for reply Nandha,
    PDS is active & Valid also SNP planned order indicator is set. Just to clarify that planned orders are not created by SNP. We are creating planned orders using /sapapo/lcin (Time series to Order Network) transaction.
    Regards,
    Harshil Desai

  • How to Change Component on a SNP Planned Order ( Just 1 time )

    Hello,
    We are trying to change a component on a SNP Planned Order just 1 time.
    So we do not want to change the PDS since this is one time change only.
    We tried changing it in R/3. Once we do that, R/3 shows new component but APO still shows dependant demand on old component ( May be because APO SNP Planned order is still connected with the PDS ) .
    Then we went to APO and tried to change the component in /sapapo/rrp3. Here you can delete the old component but doesn't let me add new component.
    Next thing we tried was to convert it to PPDS Order. Once converted, we went to change mode and tried to remove old component and add new component. It lets me do this. Only issue with this route is that, it puts correct start and end dates on the order dependning on the order quantity and so order moves the dates which we do not like.
    Is there any other better way to fix this issue ?.
    Thanks.
    Ketan Doshi.

    This being a very unique requirement, I would use one-off approaches usually not followed. You may need to explore the use of BAPI BAPI_MOSRVAPS_CREATESNPORDER. This will help you point the source of planned order to a PPM or a PDS that you may want to create in APO system on a one-off basis. PPMs can be maintained in APO, however PDS are usually CIFed from R3. You can try to create PDS (based on the new component) in APO system only using backend tables. Try do some little research on /sapapo/curto tables to create the PDS in APO. Then use the BAPI to point the source to this new PDS. (better you also try the PPM approach since there are no issues keeping the PPM in APO)

  • SNP Planned Order Date

    Hi Experts,
    May I ask for your help. I have a gr processing time of 1 and In-house production of 1 day as well. But whenever I run heuristic, it results in 4 days from start date to availability date. Say April 16 start date and availability date is April 20. Are there other factors on how this is computed?really hoping for a reply from you.
    Thanks! Sincerely, Ria

    Hello Ria,
    Have you maintained any GR time in ECC?
    I faced a similar issue (in PPDS order though) in which it was computing the availability date
    first based on the GR processing time maintained in APO, when the order goes to ECC it would pick up the GR processing time maintained in ECC, and move the availability date of the order in APO.
    We are working on code to stop this transfer back to APO.
    Note 508993 gives more details about the FM.
    You may try an option to stop the transfer from SAP R/3 since you are working with SNP planned orders:
    https://help.sap.com/saphelp_scm50/helpdata/en/80/e8bc0f629af14db213108bb6fa7515/content.htm?frameset=/en/b3/32c5d32970834dadf53cac0aa2b5b4/frameset.htm&current_toc=/en/9b/954d3baf755b67e10000000a114084/plain.htm&node_id=147
    Hope this helps you!
    Regards,
    Subhash

Maybe you are looking for