SNP Planned order creation

Iu2019ve a material M1 at plant P1 with procurement type X. There is no SNP PDS/PPM for this material/plant. If there is a demand of 100 on this material/location and I run heuristics, it creates a planned order even though there is a transportation lane between vendor V1 and location P1. Why would it not create a Purchase Req in this case?

system switches over to external procurement in place of in house production only when you use optimizer.
Heuristic will do this only if there is a SNP PPM/PDS and the resource calendar prevents timely production.
Regards
Nitin Thatte

Similar Messages

  • SAP APO SNP planned order

    Hi,
    I am basically from PP background and just started working in APO SNP. after running SNP optimzer,not able to see the operation details in SNP planned order ( SNP planned order has only receipts, requirements ). could you please help me how to get operation details in SNP planned order.
    Thanks
    Krishna.

    Hi,
    SNP Planned Order:
    1 . SNP Planned Orders wil give details about Order start date and finish date .
    2.  During  SNP Planned Order creation a basic scheduling will happen.
    PPDS Planned Order
    1.  PPDS Planned Orders will give details about when the actual production is start and finish.
    2.  During PPDS Planned creation the Machine time details defined in the routing routing or recepie will be take into account.
    3.  Leadtime scheduling will be carried out to calculate the exact production start date and finish date.
    Thanks,
    nandha

  • 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.

  • Creation of SNP Planned Orders using Optimizer

    Dear Experts .....
    I am facing some problems while creating SNP Planned orders using Optmizer ( Discret Optimization).....
    For eg.
    I am using 3 months horizon ... the first two months is daily buckets with 12 hours capacity each one and the last month is weekly buckets.
    The product minimun lot size exceed the daily capacity .... this way planned order have been created in the weekly buckets at the end of the horizon.
    I need the system to create orders in the correct date avoiding use of safety stock .....
    Regards
    Mauricio

    Those other 2 settings was already done .....
    It is still not working .... iI am receiving the following message ...
    Production process model/PDS 00000000000001011301001             S: Cannot be executed
    Message no. /SAPAPO/SNPOPT159
    Diagnosis
    Production process model 00000000000001011301001             S at location 0100 is intended for cross-period lot size planning. It can be started in bucket 20110404->20110404. However, it does not then end in the same bucket.
    Thanks for your effort trying to help me with this issue.

  • Deletion and creation of SNP Planned order

    Hi,
    I need to delete the SNP Planned order i.e ATP category of type 'EE' and I have to create the orders of ATP category EE  through programetically. Please let me know if any BAPI's or Function modules are existed for the same.
    Appriciate your help.
    Regards,
    Ratna

    Hi Ratna.
    To delete orders in SNP use transaction:
    /SAPAPO/RLCDEL
    BAPI to create planned orders:
    BAPI_MOSRVAPS_SAVEMULTI3
    There is also a BAPI to delete planned orders if this is more suitable.
    BAPI_MOSRVAPS_DELEMULTI
    Hope this helps, M

  • Creation of SNP planned order in Monthly Bucket though CTM plan

    Hi,
    Can anyone advise how to aggregate the SNP planned order generated after CTM run in Monthly bucket.
    Can it be done through customizing?
    Regards.
    Punit

    system switches over to external procurement in place of in house production only when you use optimizer.
    Heuristic will do this only if there is a SNP PPM/PDS and the resource calendar prevents timely production.
    Regards
    Nitin Thatte

  • 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

  • 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 - Doesnt get the complete BOM when CIFd to ECC

    Hello,
    When we create SNP Planned order in APO and sent to ECC, the Planned order doesn’t get the complete BOM, it works for the most part, except if we have Materials from multiple plants within the same BOM (sourcing from multiple plants).
    Do we have to do any separate Configuration for this scenario?
    We are planning only the End item in SNP, and we are generating the production version and PDS transfer to APO. We are not transferring all the materials to APO.
    if we go to the Change mode of the Planned order in ECC and re-explode the BOM, I get all the components from the BOM, its just that when the planned order gets created thru the CIF we have this issue.
    Any help would be appreciated.
    Regards
    Gk

    Hello Marius
    Thank you for your quick response.
    I looked at the SAP note you mentioned, the description seems to be matching with the issue we are having. Recently we had SNC implemented, and the note states that that can be the case why the components are getting deleted during planned order creation.
    The only thing about this note is its very old, and we are having the SAP 6.0 and SCM 7.2 ,
    Do you think this would be still applicable.
    I will look into the details and let you know whether the note is applicable for us.
    Regards
    Gk

  • Optmizer Planned Orders Creation

    Dear SAP Experts ,
    I am facing some problems with Planned Orders creation. I am executing discret optimization but it is creating planned order without taking into account minimum lot size.
    For i.e
    For one product with forecast 500 pc and minimum lot size 150 .
    Optmizer should create 4 orders with 150 pc taking into account minimum lot size but it is creating 3 orders with 150 and 1 order with 50 pc to fullfil demand .
    Some one can help me ?
    Nice Regards
    Mauricio Filho

    Hi,
    What is PPM/PDS max lot size? it seems due PPM max lot size you are getting these results.
    SNP Optimizer can't respect max lot size defined in product master.
    it can respect only min lot size and rounding value from product-location master for that
    in optimizer profile must be discrete and on discrete consraints tab define Mini PPM/PDS lot size and Integral PPMs/PDS horizon.
    If data view has weekly as well as month buckets, define 12 Months (don't define 52W) in discrete constraints tab if you want to respect these constraints for one year.
    Regards,
    Vipul

  • 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

Maybe you are looking for