Deployment fair share rule B

hi,
I have gone through following example of fair share rule B in one of the earlier posts.
Destination location A Dest. Location B
Demand in bucket P1 1000 1600
Available stock 200 600
Target Stck levels (as derived from safety stock levels) 800 1500
Stock required from source 1600 2500
% of target stock before deployment 25 % 40%
Stock available to deploy at production site - 1200 qty
Deployment qty as per fair share rule B 496 704
Available stock after depöloyment 696 1304
% of target stock level after deployment 87% 87%
based on the values above, can anyone please tell me how exactly the deployment quantity 496 is calculated?
Regards,
YR

Hi sap_apo1,
What clarie has written is absolutely fine. I have deduced a working formula. It is as follows:--
If Da1, Da2 .....Dan are deployed quantities in destination locations a1, a2... an
If Stka1, stka2....Stkan are actual stocks at destination locations on day of receipt of deployed quantity in locations a1, a2... an
If Tstka1, Tstka2,Tstka3.....Tskan are target stock quantities as per SS days n day of receipt of deployed quantity* in locations a1, a2... an
Then , the following formula works
(Da1Stka1)/Tstka1=(Da2Stka2)/Tstka2=...................................=(Dan+Stkan)/Tstkan
Da1Da2.......+Dan= Total quantity available to be deployed by the source location
Conditions: it takes the transportaion lane duration into account.Therefore, take into account the stk  quantities on the day of recipt at destination locations.It can differ as tlane durations can be different to different destination locations.
The formula applies only when it is possible to equate the percentages. If the stock distribution is already eavily skewed to a location, and the fair share cannot bring the other locations to this level due to insufficient quantity to deploy.
Regards,
Samir Baruah

Similar Messages

  • Fair Share Rule A & B

    Hi Experts,
    can you explain the logic with examples on how Fair share Rule A & B works in APO deployment.
    Best Regards,
    Anandharaj

    Hi Anandharaj,
    I have seen you are new in SCN. According to the SCN Rules we should search before posting a new thread. Take a look of the Rules:
    The SCN Rules of Engagement
    I have found lot of threads and different documentation and examples in google explaining the Fair Share Rules A & B. Including examples. Here you have a couple:
    deployment fair share rules
    SNP Deployment and Fair Share - SAP Planning
    Thanks and Regards,
    Mariano

  • Fair share rule B

    hi,
    Can any one explain about fair share rule B with target stk level method 4.  and how % of fullfillment calculated with respect to target stk level in destination location.

    Hi,
    I assume you are using safety stock also, so all the requiremnts will have two parts Forecast and Safety Stock required.
    For example the requirement propagated to a source location S1 from two destination location is D1 = 100 & D2 = 130.
    Now out of this for D1 50 is forecast and 50 is safety stock req and for D2 70 is forecast and 60 is safety stock.
    Now S1 will first give 20 to D2 from its supply and make demands at both location equal, after that it will supply to both the location such that forecast requirement at both location remains equal.
    for example if available supply is 100 it will give 20 to D1 and remaining 80 it will divide as 40 & 40 between D1 & D2.
    So d1 will get 40 and D2 will get 60.
    now assume if supply is 180 it will first meet demand of 50 & 70 at D1 & D2 and remaining 60 it will distribute between D1 and D2 such that the perecentage of safety stock requirement is equal i.e. x/50 = (60-x)/60.
    I think you will get the bhavior if you use the above eg and try on ur system.
    Thanks & Regards,
    Sanjog

  • Fair Share B with Interchangeability

    Hello All,
           Is to possible to use the Fair Share rule B with Interchangeability in SNP Deployment (SCM 7.0)???
    Thanks,
    Siva.

    Hi Sivaprakash,
    A short answer to your question is NO.
    The deployment heuristic and the deployment optimizer take into account SNP product substitution orders that were created during heuristic-based or optimization-based planning in Supply Network Planning (SNP).
    The fair share rule A (Proportional Distribution Based on Demands) or one of the push rules, Pull, Pull/Push, or Push by Demands as the distribution rules for the deployment heuristic in the product master data is respected . The other distribution rules are not supported.
    Therefore  the Fair Share Rule B: Proportional Distribution Based on Target Stock  will NOT be respected with product substitution.
    Please find additonal document help on following URL:
    http://help.sap.com/saphelp_scm70/helpdata/en/1c/4d7a375f0dbc7fe10000009b38f8cf/frameset.htm
    Please also refer to OSS note 1405636  SCM 7.0 Implementation recommendations SNPCTMVMI.
    I hope this gives you insight.
    Please confirm.
    Regards
    Datta

  • Fair share logic in Backorder Processing - APOBO040 -

    We are thinking to use backorder processing in GATP process. However, one of the expectations of our customer is "fair share logic" during the confirmation of sales orders. Let me clarify what I mean:
    1- We have following sales orders in hand with the mentioned sorting.
    _________Req. Quantity
    SO1________20 pieces
    SO2________20 pieces
    SO3_________1 piece
    SO4_________1 piece
    2 - Assume that the total of our stocks and planned orders are 40 pieces. Then the system will give confirmation to the orders as follows:
    __________Req. Quantity______Confirmed Quantity
    SO1________20 pieces___________20 pieces
    SO2________20 pieces___________20 pieces
    SO3_________1 piece____________No confirmation  
    SO4_________1 piece____________No confirmation
    3 - However we want to achieve such a confirmation distribution.
    __________Req. Quantity______Confirmed Quantity
    SO1________20 pieces___________19 pieces
    SO2________20 pieces___________19 pieces
    SO3_________1 piece_____________1 piece 
    SO4_________1 piece_____________1 piece
    As we have seen from the in the customizing of APO this is somehow possible with the user exit "EXIT_/SAPAPO/SAPLBOP_040" - scope of check-
    (APO Customizing / GATP / Enhancements / Backorder Processing / Define Scope of Check for Batch Backorder Processing)
    Do you have information about this topic, have you tried this solution before, is it working???
    If anybody can help, we really appreciate.
    Thanks in advance and Best Regards

    Hello there, This is in refrence to the doc posted in the link
    Re: Fair share logic in Backorder Processing - APOBO040 -
    I actually have the same requirement and want to implement the fair share logic by using the below mentioned User Exit...  .But the last line in the documentation below says that "This is only possible for the basic methods product availability check and product allocation.""  ....
    Can I implement the  same for Rules Based ATP ..  actually we are using Rules Bases Sustn in cunjunction with BOP.
    Please let me know if you any idea about this fair share ?? Can this be done ??
    Regards,
    Amit --  [email protected]
    > I dont know If you have gone through this document:
    > The lines in bold explains clearly uptill what extent
    > you can do the FAIR SHARE RULE.
    >
    > I believe we cannot do <b>EXACTLY</b> what you have
    > stated in your example.
    > Availability Check is the core for comfirmation of a
    > sales order.
    >
    > Whatever customizing you do in the user exit, donot
    > attemp to do your own availability check logic...
    >
    > GOOD LUCK and let us know when you have done the
    > coding.
    > ******************************************************
    > *******************************
    > <b>EXIT_/SAPAPO/SAPLBOP_040 :</b>
    >
    > ATP, BOP: Scope of Check for Backorder Processing
    > Functionality
    > The user exit is called in backorder processing
    > before the availability check is called.
    >
    > The requirements to be checked and the correction
    > quantities of the separate basic methods are
    > transferred to the function module.
    >
    > Depending on the settings for backorder processing,
    > the requirements to be checked are either the
    > original requirement (requirement check) or the
    > current confirmation of the document (confirmation
    > check). Scheduling has already been performed
    > (according to the settings for the check
    > parameters).
    > The requirements are transferred into four tables.
    > The contents of these tables are linked to each other
    > by indexes.
    > <b>The requirements to be checked can be changed, for
    > example, if you want to implement a fair share logic.
    > Changing the requirements has no effect on the
    > quantities originally required in the documents.
    > <u><i>The change only limits the maximum quantity you
    > can allocate to a document.</i></u>
    > The correction quantities are determined for each
    > basic method. By reducing the correction quantities
    > you can prevent the total quantity being divided
    > between the documents to be checked.
    > You must not change the adjustment entries for
    > planning.</b>
    >
    > ***************************************************
    > APOBO040 scope of check:
    >
    > Scope of Check for Batch Backorder Processing
    > The function module EXIT_/SAPAPO/SAPLBOP_040 is
    > called before the availability check in backorder
    > processing. The documents have already been selected
    > (filter) and sorted.
    >
    > Environment
    > The requirements to be checked and the corresponding
    > correction quantities of the individual basic methods
    > are transferred to the function module.
    >
    > By changing (reducing) the requirements, a fair share
    > logic can be implemented using this function module.
    >
    > By changing (reducing) the correction quantities,
    > quantities can be protected from distribution via
    > backorder processing. This is only possible for the
    > basic methods product availability check and product
    > allocation.
    >
    > Message was edited by:
    >         Kumar Ayyagari

  • Issue Deployment rounding value & Fair Share

    Hello All,
           I have tested the deployment (SCM 7.0) with the rounding values and observed some strange results. Please find my cases below. And the deployment was executed on the production plant.
    Case 1:
    Location = DC1
    Demand = 5000
    Rounding Value= 1
    Location = DC2
    Demand = 3000
    Rounding Value= 1
    Location = PP
    Demand =0
    Stock= 1000
    Rounding Value= 1
    Location = DC3
    Demand = 2000
    Rounding Value= 1000
    Deployment Result:
    700 on DC1 and 300 on DC2
    Expected Result:
    625 on DC1 and 375 on DC2
    Case 2:
    Location = DC1
    Demand = 5000
    Rounding Value= 2
    Location = DC2
    Demand = 3000
    Rounding Value= 2
    Location = PP
    Demand =0
    Stock= 1000
    Rounding Value= 2
    Location = DC3
    Demand = 2000
    Rounding Value= 1000
    Deployment Result:
    700 on DC1 and 300 on DC2
    Expected Result:
    626 on DC1 and 374 on DC2
    Case 3:
    Location = DC1
    Demand = 5000
    Rounding Value= 1
    Location = DC2
    Demand = 3000
    Rounding Value= 1
    Location = PP
    Demand =0
    Stock= 1000
    Rounding Value= 1
    Location = DC3
    Demand = 2000
    Rounding Value= 1
    Deployment Result:
    500 on DC1, 300 on DC2 and 200 on DC3
    Expected Result:
    500 on DC1, 300 on DC2 and 200 on DC3
    Case 4:
    Location = DC1
    Demand = 5000
    Rounding Value= 1000
    Location = DC2
    Demand = 3000
    Rounding Value= 1000
    Location = PP
    Demand =0
    Stock= 1000
    Rounding Value= 1000
    Location = DC3
    Demand = 2000
    Rounding Value= 1000
    Deployment Result:
    1000 on DC1
    Expected Result:
    1000 on PP
    Master Data:
    Pull Deployment Horizon           : 28
    Fair Share               : A
    Push Deployment Horizon          : 999
    Only case 3 works as expected.
    Please let me know if I missing somethning.
    Thanks,
    Siva.
    Edited by: sivaprakash pandian on Nov 18, 2009 9:34 PM
    Edited by: sivaprakash pandian on Nov 18, 2009 9:52 PM

    Hi,
    I have compared the product location combination in MAT1 for DC2 and DC3, all of settings are same except Rounding value and Minimum Lot Size in subview Lot Size. Do you think it's because of the Rounding Value?
    I also checked the TL for DC1->DC2 and DC1->DC3, TLB Profile is difference between each other, but the total volume and total weight calculated with the value distributed proportionally from ATD Quantity is below than the constraint in  TLB profile. therefore I think TLB is no issue.
    Thanks & Regards,
    Quanyin Su

  • How to deploy Oracel Business Rule (11 TP4) from within JDeveloper?

    Hello,
    I'm testing the Oracle Business Rules functionality provided in JDeveloper 11TP4.
    Development looks nice. I'd like to test the rules, wether it be from within a Java Class or as a Web Service.
    - How can I test the Business Rule 11G in Jdev TP4?
    - How can I deploy the Business Rules to an Application Server?
    Who's got ideas?
    Thanks in advance,
    Regards Léon Smiers

    Leon,
    Try the business rules sample for TP4. It includes instructions on how to build the rule and deploy it from JDev.
    http://www.oracle.com/technology/products/ias/bpel/techpreview/index.html
    Heidi.

  • Fair share priority

    Hi there,
    I have a situation where several WorkManagers have same fair share and one common max thread constraint but one component may have irregular high workload. My task is to provide some minimum resources for each component without changing their fair share during periods of normal request count.
    I was trying to search for scheduler’s algorithm and found out that it is a priority fair queue. It uses parameter ‘virtual time’ for each WorkManager that can be observed in RequestClassRuntimeMBean.
    Is someone familiar with internal WorkManager structure? Is virtual time internal priority of thread queue and can it be modified in runtime to change WorkManager behavior?
    Best wishes,
    Eugene

    Hi,
    I assume you are using safety stock also, so all the requiremnts will have two parts Forecast and Safety Stock required.
    For example the requirement propagated to a source location S1 from two destination location is D1 = 100 & D2 = 130.
    Now out of this for D1 50 is forecast and 50 is safety stock req and for D2 70 is forecast and 60 is safety stock.
    Now S1 will first give 20 to D2 from its supply and make demands at both location equal, after that it will supply to both the location such that forecast requirement at both location remains equal.
    for example if available supply is 100 it will give 20 to D1 and remaining 80 it will divide as 40 & 40 between D1 & D2.
    So d1 will get 40 and D2 will get 60.
    now assume if supply is 180 it will first meet demand of 50 & 70 at D1 & D2 and remaining 60 it will distribute between D1 and D2 such that the perecentage of safety stock requirement is equal i.e. x/50 = (60-x)/60.
    I think you will get the bhavior if you use the above eg and try on ur system.
    Thanks & Regards,
    Sanjog

  • Deployment with fairshare rule B

    Hi Gurus,
    Could anyone please explain me with a example(easily understandable) about the SNP Deployment with fairshare rule B..with an example and how the calculation is done..
    Thanks

    Hi,
    Two cases are explained below to demonstrate FS B behavior.
    DC1 :
    Demand : 100
    Target stock level : 200
    Stock : 30
    DC2 :
    Demand : 120
    Target stock level : 100
    Stock : 10
    Case 1:
    Source : ATD qty 100
    In this case Deployment will confirm as follows
    DC1: 30
    DC2: 70
    By deploying stocks as above the demand shortfall in both locations is equal (50 nos).
    Case 2:
    Source : ATD qty 240
    In this case Deployment will confirm as follows
    DC1:  110 (70 for demand + 40 for SS)
    DC2: 130  (110  for demand+ 20 for SS)
    Demand met:  DC1 = DC2 = 100%
    Target stock level: DC1 = DC2 = 20%
    In this the demand is first met 100 % for deploying stocks and the rest of the ATD qty (240 - [110+70] = 60) is distributed in such a way that the % target stock level in both locations is the same.
    Hope this is clear. Pls let me know if you need further calrifications
    regards,
    Ashok

  • Can you deploy Oracle Business Rules to the other App servers

    Can you deploy Oracle Business Rules to the other App servers such as Websphere and Jboss

    Yes. Please see the Appendix C in the documentation at:
    http://download-west.oracle.com/docs/cd/B31017_01/web.1013/b28965.pdf
    For WebSphere, updated instructions will be released soon that allow all RuleAuthor features to be used.

  • Weblogic work manager - Control min./max. threads & fair share

    I have an application which is running on Weblogic 10.3.2. I need to be able to control the number of threads the server assigns to this application. The application has 3 MDBs and for each of these MDBs, we need to assign a weight so that that the available threads are distributed among the 3 MDBs according to the weight.
    After going through the Weblogic documentation, it looks like I could create 3 work managers with the min. threads, max. threads and fair share. These work managers could be assigned to each of the MDBs. But, this does not control the total number of threads the server assigns to the application.
    Question:
    Is there a way we can create a work manager with the min. threads and max. threads and assign it to the whole application? This could be used to control the min./max. threads assigned to the application. Then we could define 3 work managers with the fair share and assign them to the individual MDBs.

    Hi ,
    You can create a work manager with min. threads and max. threads constraints defined. Check this:
    http://www.oracle.com/technetwork/articles/entarch/workload-management3-087769.html
    Thanks,
    Sharmela

  • Fair share request class usage

    Hi,
    Here are my doubts regarding the fair share request class usage
    1->I have only one custom work manager with fair share value configured as 100 (value between 1 to 1000 as per oracle docs), will the remaining request share goes to default work manager ? or the fair share request class should be configured only with multiple custom work manager as to be shared between them ?
    2->If i have 2 custom work manager with fare share value 100, 50. whats the meaning with respect to sharing the request ? again will default work manager comes into picture for remaining share ?
    Please help
    Thanks,
    Sandeep

    Maybe this is of some help: Re: SelfTuningWorkManager

  • Deployment Issue with Rules file

    Hi,
    We have Rules file issue after the deployment in Development and Re7 environment.
    We have modified/created the rules file and after the deployment if we execute the rules file from the treatment then we got the error message like mentioned below.
    MAXL> Import database PGC_CHE.Pgc_che data from data_file
    "/pgcre701/pgc/subsidiary/che/tfi/pgc_nature_for_data_che.txt" using server rules_file "DO_MX_05" on error
    write to "/pgcre701/pgc/trc/PGC_150310_103739_pgc_nature_for_data_che.err";
       ERROR - 1019006 - Unable to Read
    [/logiciel/epm11/user_projects/epm_inst4/EssbaseServer/app/PGC_CHE/Pgc_che/DO_MX_05.rul], Created Using A
    Previous Version.
       ERROR - 1241101 - Unexpected Essbase error 1019006.
    If the same rules file opened through EAS console from SVN trunk or local and save as this rule file into Essbase server(through EAS console) then the rules file working correctly from the treatment process launch like mentioned below.
    MAXL> Import database PGC_CHE.Pgc_che data from data_file "/pgcre701/pgc/subsidiary/che/tfi/pgc_nature_for_data_che.txt" using server rules_file "DO_MX_05" on error write to "/pgcre701/pgc/trc/PGC_150310_134622_pgc_nature_for_data_che.err";
    OK/INFO - 1019061 - Reading Rule SQL Information For Database [Pgc_che].
    OK/INFO - 1019025 - Reading Rules From Rule Object For Database [Pgc_che].
    OK/INFO - 1003040 - Parallel dataload enabled: [1] block prepare threads, [1] block write threads..
    OK/INFO - 1003037 - Data Load Updated [18800] cells.
    OK/INFO - 1003053 - Data Load Elapsed Time with [DO_MX_05.rul] : [1.16] seconds.
    OK/INFO - 1241113 - Database import completed ['PGC_CHE'.'Pgc_che'].
    Could you please help us on this point ?
    Thanks in advance for your help.
    Essbase server 11.1.2.3.501 server LINUX red hat

    Hi John,
    it's not quite that
    I will provide more detail:
    In fact, we are 3 server Essbase : development, acceptance and operational there are a lot the new version of Essbase 11.1.2.3.501.
    The maxl treatment are launch since a other server : a treatment server that are a client maxl and ESSCMD in the same version.
    Before that, I'm migrate all the application and database from all alder server Essbase to this new architecture Essbase.
    All application and DATABASE (in BSO) was migrated by expot-import process, the all object (csc, rul, rep ...) was transfer by copy in each directories of database.
    The test after migration are very  satisfying.
    Now, we are on process of life on the Essbase server 11.1.2.3.501.
    The back office of India used the usually process to developed the lot.
    They take the source on SVN application (take the rule), deployed the rule on the development server, modify the rule and have this error.
    This error not appear after migration with the same rule ...
    I am skeptical
    Tx to your help on this subject.

  • MDT: deploy from share which is not in domain?

    Hi,
    I'm trying to deploy a task sequence from a share which is hosted on a nas (not in a domain).
    When it tries to connect to the share it says it needs a domain name but there is none. If I fill in a dummy name the connection fails.
    Pls advise.
    J.
    Jan Hoedt

    The MDT litetouch scripts will attempt to connect the DeployRoot network share. If it can't connect it will use the credentials supplied, if you have not yet supplied credentials, then MDT will prompt you for the credentials.
    How does MDT attempt to connect, using SMB network shares. It's essentially the same as going to a command prompt and running:
    net.exe use * \\Server\DeploymentShare$ /u:Domain\UserName Password
    Where domain *can* be the servername if the server is not connected to a domain.
    I do not have a Synology NAS so I can't tell you how to connect to it using SMB. That's up to you. Once you have determined the procedures necessary to connect up to the NAS using SMB, use those credentials in MDT.
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • Unable to deploy calc manager rule with Attributes in 11.1.2.1

    I am unable to validate/deploy a calc manager rule in 11.1.2.1. This rule is also developed as a calc script and gets validated/executed successfully.
    This is a custom currency conversion script
    Sample
    Jan (
    IF(@ISMBR(@ATTRIBUTE("b_CNY")))
    "USD" = "LocalCurrency" / "Avg_Rate"->"CNY" ;
    ELSEIF ......
    ELSEIF.....
    ENDIF
    Does any one know if this a known bug ?
    Thanks

    It used to be a bug that @attribute could not be validated, maybe worth checking the patches to see if it is fixed yet.
    Cheers
    John
    http://john-goodwin.blogspot.com/

Maybe you are looking for