Skip to Content
author's profile photo Former Member
Former Member

SNP Heuristics order creation date


Below is the model, current results and expected results.

Business scenario- At the time of PR creation by APO, business does not know which vendor to assign. Vendor selection happens later in ECC based on many factors. When there is a requirement, the necessary PR should be created with a date which is 45 days before the requirement (forecast) date as the delivery lead time for the product is 45 days. Client will change this PR to PO and assign the required vendor 45 days ahead of the requirement.

Model- a product P at location L. P has a forecast on 1st Nov 2012 (01.11.2012).

Proc type- F

Planned del time- 45 days

No vendor maintained in APO

No T Lane maintained for the product P @ L

Current Result- When I run SNP heuristics on P @ L, a PR is created on 16th Nov 2012 (16.11.2012). If I go into order details in RRP3 view, I see order start date- 16.11.2012, order end date- 16.11.2012, order opening date-02.10.2012

Expected result- PR should be created at L on mid of sep'12. Availability date for the PR should be 15.09.2012

I tried by maintaining GR processing time at L as 45 days. But still the same result.

Need some light on the system behavior and what needs to be done to get the desired results.



Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on Jun 06, 2012 at 07:07 AM

    Hi Manotosh,

    Only Finished Goods Planned without BOM explosion in APO

    Any order created through SNP planning run in APO has a pegging characteristic, i.e it has an attachment of supply node with demand node. This pegging occurs only in a relevant t-lane with means-of-transport is maintained between the two locations (MFG vs DC)

    Hence the Pur.Rqs-order at DC location with procurement type = F (External Procurement) will have a supply node, which would have a demand node at the MFG location, here at MFG location this same order would become a STO-order order, but only if the t-lane exists between MFG & DC.

    This order which if required on say 01-Nov-12 would have three dates :start-date, available-date & end-date. It would only consider the GR+GI (of both MFG & DC) +Transport Duration {this is maintained in Means-of-Transportation} to cascade the start date.

    ex : Transportation Duration = 24 hrs GI= 0 for both MGF & DC GR=10 days for MFG & GR=0 for DC, then this order would be created as below:

    Order-XXXXXXX | start date :21-Oct-12 {24 hrs + 10 days = 11 days prior to 01-Nov-12} | available date : 01-Nov-12 | End Date : 01-Nov-12

    Finished Goods Planning with BOM explosion

    This would then include the PPM/PDS & include many additional times to calculate the start date.

    Please check the product-location master for GR+GI & try again. In case no T-lane is maintained then I guess it boils down to just planning for one-material at only one location. Right? It should then only take the GR time to generate the Pur.Rqs-order's time.

    I hope this helps.


    MFG= Manufacturing Plant

    DC= Distribution Center

    Message was edited by: Blue Lotus

    Message was edited by: Blue Lotus

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Sandeep,

      The catch here is that I dont have a source location while creating PR. Hence need the PR availability date at the destination location as 45 days before the requirement date. Currently with period factor and with PDT, the PR availability date comes as equal to requirement date and the order opening date comes 45 days before the requirement date. Order opening date is visible only when you open the order from RRP3 or RRP4 and not in the product view elements. Hence the user has to open each order to see the order opening date. Other way is to create a report and display the details there.

      To avoid it, I am looking to get the PR availability date as equal to 45 days before the requirement date. These PRs would be edited and converted to PO in ECC where the vendor will be assigned.



Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.