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

Similar Messages

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

  • BAPI to create SNP planned order based on start date

    Hi,
    I am looking for a BAPI to create SNP planned order based on the order start date. There is BAPI BAPI_MOSRVAPS_CREATESNPORDER which can be used to create SNP planned order based on the end date but not based on the start date.
    Also would be great if some one can share how do they create SNP Planned orders using BAPI BAPI_MOSRVAPS_CREATESNPORDER in case if GR processing time is defined in the product master and workdays for GR to be respected according to the calendar.
    Regards,
    Venkat

    Hello Mr.Venkat,
    Hope you recognize me.
    Please check out the BAdi below.
    BAdi - APO_BAPI_BUS10503 (this is the BAdi for ManufactOrderAPS  BAPI which contains the SNPorder BAPI)
    Method - CHANGE_SAVEMULTIPLE2
    In this method parameter IT_ORDER_HEAD contains Order start date input option.
    For GR time please check this (not sure if it will help).
    Same BAdi/ same method
    Parameter IV_PLANNING_MODE_USAGE contains field PLANNING_MODE.
    Value 1 for PLANNING_MODE corresponds to "Observance of parameters from the product master".
    This may make it respect the GR time in product master
    Good luck with the above
    Regards,
    Ashok

  • When I create a Planned order using PDS, the Setup time is coming as 0.

    We have been using PPMs for a long time, and now we are trying to migrate to PDS.
    We are currently in SCM 7.0.
    I successfully created the PDS in APO (using CIF from R/3). In the PDS (in APO), for a particular activity, I see the  activity type is "S", and the Activity Duratiion (Fixed) is 43,200 Seconds.
    However, when I create a planned order using this PDS, the activity time is zero (End time = Start Time).
    When we use the PPM the setup time comes correctly.
    Any help will be appreciated..

    Senthil,
    Thanks for your views.
    I have checked all that you have suggested, and it is okay. The issue still persists.
    One thing that I noticed was that it is working fine in the old SCM 5.0 environment - the setup time is coming correctly in the planned order.
    However, we have this issue in the new SCM 7.0 environment. Is there something that is different in SCM 7.0 in terms order explosion ?
    Reagrds,
    Sastry

  • 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

  • SNP Planned Order without PPM

    Hi Gurus,
    I have a small confusion, Some of my products in a Production Plant donot have a  SNP PPM. and when i run network heuristic on that location product. It creates SNP Planned orders.
    Just for information the product location master has procurement type E (In House Production).
    Please help me out if this is a normal behavior of the system.
    Thanks,
    M

    Default behavior is to generate Orders without a source of supply.
    "If there is neither a valid transportation lane (for procurement type F; external procurement) nor valid PPM/PDS (for procurement type E; in-house production), the system creates an SNP stock transfer or SNP planned order with no reference to a source of supply. The same applies if there is no product at the source location of the transportation lane"
    if you dont want planned orders there,
    Try using the SDP relevance indicator for the location - product . Am not sure but you can use option 1 in it (though it sounds like it will not plan in DP too)

  • 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

  • Delete SNP Planned Order to reflect at R3 (C5 or CCR)

    Hi,
    I deleted some SNP planned order using rlcdel, should i use a C5 or CCR to transfer to deletion toR3 to reflect the changes . ? what situation should i used C5  or CC5
    many thanks

    Hi,
                     RLCDELETE has the radio buttons "In APO" and "In APO and R/3". if you check the "In APO and R/3", the deletion is immediately sent to R/3. No need to run C5. If not then you just deleted the order only in APO and did not delete in R/3. You can either run C5 and select the change pointer with "R"- delete or run CCR report or delete these orders manually in MD16 in R/3.
    what situation should i used C5 or CC5
    C5: When you sent periodic transfer in SPRO, then create an order and push it to R/3. You can also delete an order and push the delete change pointer (R) to R/3
    CCR: When the orders in APO and R/3 donot match.

  • 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

  • Need Automatic Lead-time scheduling in Planned Order using MD11

    All,
    Our users have a requirement that when they create a planned order using MD11, they would like system to do automatic lead-time scheduling based on the "basic finish date" entered by the user. Currently the system is taking 3 days from the in-house time maintained in material master to calculate the basic start date. But users want to use the 100 days that have been maintained in the routing.
    Currently users have to click on "manual scheduling" on the planned order for system to pick up 100 days from routing which is an additional step for the users. Hence users want an automatic way in which system would do lead-time schedule when they enter the basic finish date.
    Thanks,
    Swapnil

    Dear Swapnil,
    In my understanding it is the standard SAP behaviour even if you have made the necessary settings in OPU5 for the planned
    order type.
    If my understanding is correct, then as per this setting the MRP behaves for the particular plant and order type combination.
    Whenever you create a planned order manually you have to do a detailed scheduling and then you get the production dates
    for the planned order.(This might be because generally when a planned order is converted into production order the system
    carries out a lead time scheduling.- Check the same and correct me if I'm wrong)
    Even if you update the material master through CA97,you will not get the detailed scheduling done along with the production
    dates.So you have to perform this manual activity during MD11.
    What is the reason of setting the in-house production time as 3 days,if the exact production time is going to be more?
    Check and revert
    Regards
    S Mangalraj

  • Creating planned orders with BAPI_MOSRVAPS_SAVEMULTI3

    Dear all,
    I have to create planned orders in our APO-system ... This works fine with function BAPI_MOSRVAPS_SAVEMULTI3, until I try to create a planned order with a configurable material ... I added values to the following tables: cfg_headers, cfg_instances and cfg_values but still I am not able to create a planned order ... Maybe I don't fill the correct fields in the mentioned tables ? Can anyone tell me which fields they fill to create planned orders with configurable materials ? I used the fields that are required according to the SAP-help, but it seems that my values are possibly wrong ... Maybe an example can help me too ?
    Thanks in advance !!!
    Greetz,
    Kurt.

    Hello Babu,
    I am facing the same error in BAPI_PIRSRVAPS_DELMULTI. Could you revert with the solution if you have got one.
    Thanks,
    Ankit

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

  • 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

Maybe you are looking for