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

Similar Messages

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

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 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 EXACTLY 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.
> ******************************************************
> *******************************
> EXIT_/SAPAPO/SAPLBOP_040 :
>
> 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.
> 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.
> The change only limits the maximum quantity you
> can allocate to a document.
> 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.
>
> ***************************************************
> 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

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

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

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

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 run always applies push rule

Hi,
For deployment run , I am using push rule - Q (Quota) and fair share rule - D (Distribution based on priority).
My expectation was if Supply is more than demand -push rule - Q should be used and if demand is more than supply fair share rule - D should be used.
I observed, even if demand is more than supply, system does deployment based on push rul - Q, ie, all the quantities are immediately depolyed on the current date.
Any thoughts why system is not deploying based on fair share rule, even though Demand is more than supply.
Thanks
Sharad

Hi Venkat,
I am trying to model the exact scenario where the ATD quantity is not being equally split but the whole chunk is being sent to one of the destination locations. Can you please let me know how you have setup the cost models.
Regards

Reg:lsmw

i created lsmw program for mm01 using direct input method .
i done upto defining source fields now i want to create the relation between structures ,In this step what to do can any body give suggetions
here i am sending what i have dine
Here I am defining source structures.this one is 2nd step
ZCPROJ - ZCSUB - ZCOBJ demo on object
Source Structures
|
|-----ZBSTRUC basic view structure
|-----ZMDES Material description
|-----ZALT ALT UOM Structure
|-----ZCLAS Classification structure
|-----ZSALV Sales view
|-----ZSALT sales taxes
|-----ZSALTX sales text
|-----ZPUR Purchasing
|-----ZPURT Purchasing text
|-----ZPLAN Plant data
|-----ZFORC forecasting
|-----ZWSH Work scheduling
|-----ZPLS plant data storage
|-----ZWMST WM Structure
|-----ZQMST QM Structure
|-----ZACCO account cost
3rd step defining source fields
ZCPROJ - ZCSUB - ZCOBJ demo on object
Source Fields
|
|--5 ZBSTRUC basic view structure
| |-----MATNR C(010) Material
| |-----MBRSH C(010) Industry sector
| |-----MTART C(010) Material type
| |-----AENNR C(010) Change number
| |-----MATNR1 C(010) material
| |-----MAKTX C(010) material description
| |-----MEINS C(010) asic unit of measure
| |-----MATKL C(010) Material group
| |-----BISMT C(010) old matrerial no
| |-----EXTWG C(010) External material group
| |-----SPART C(010) division
| |-----LABOR C(010) lab off
| |-----PRDHA C(010) product heirarchy
| |-----MSTAE C(010) material status
| |-----MSTDE C(010) valid from
| |-----MTPOS_MARA C(010) General item catogory group
| |-----FERTH C(010) Produc inspection memo
| |-----CADKZ C(010) cad indicator
| |-----WRKST C(010) basic material
| |-----KZUMW C(010) environmentally relevent indicator
| |-----ZZPCODE C(010) product code
| |-----ZZPMODEL C(010) product model
| |-----ZSWVER C(010) version
| |-----ZZMET C(010) meta class
| |-----ZEINR C(010) document
| |-----ZEIVR C(010) documentversion
| |-----ZEIAR C(010) document type
| |-----SATNR C(010) cross plat CM
| |-----BLATT C(010) page number
| |-----KZKFG C(010) material configurable
| |-----BRGEW C(010) gross weight
| |-----GEWEI C(010) weight unit
| |-----NTGEW C(010) net weight
| |-----VOLUM C(010) volume
| |-----VOLEH C(010) volme unit
| |-----GROES C(010) size/ deimension
| |-----MDZUO C(010) design documents attached
|
|--5 ZMDES Material description
| |-----MATNR C(010) material
| |-----SPRAS C(010) language
| |-----MAKTX C(010) material description
|
|--5 ZALT ALT UOM Structure
| |-----MATNR C(010) material
| |-----MAKTX C(010) material description
| |-----UMREN C(010) alt uom volume
| |-----MEINH C(010) alt uom
| |-----UMREZ C(010) base conversion factor
| |-----MEINS C(010) basic unit of measuer
|
|--5 ZCLAS Classification structure
| |-----MATNR C(010) material
| |-----MAKTX C(010) material description
| |-----KLART C(010) material type
| |-----CLASS C(010) mateial class
| |-----ATNAM C(010) internal charecteristic
| |-----ATWRT C(010) charecteristic value
|
|--5 ZSALV Sales view
| |-----MATNR C(010) material
| |-----MAKTX C(010) material description
| |-----VKORG C(010) sales organization
| |-----SPART C(010) division
| |-----MSTAV C(010) cross distribution channel status
| |-----MSTDV C(010) valid from
| |-----VMSTA C(010) Distribution channel specific status
| |-----VMSTD C(010) valid from
| |-----DWERK C(010) delivery plat
| |-----MATKL C(010) material group
| |-----SKTOF C(010) cash discount
| |-----AUMNG C(010) minimum order quantity
| |-----LFMNG C(010) min delivery quantity
| |-----SCMNG C(010) delivery unit quantity
| |-----RDPRF C(010) rounding frofile
| |-----VERSG C(010) material statistic group
| |-----KONDM C(010) material pricing group
| |-----KTGRM C(010) account assign ment group
| |-----MTPOS_MARA C(010) general item category group
| |-----MTPOS C(010) item category group
| |-----PMATN C(010) pricing material group
| |-----PRODH C(010) product heirarchy
| |-----MVGR1 C(010) material group1
| |-----MVGR2 C(010) material group2
| |-----MVGR3 C(010) material group3
| |-----MVGR4 C(010) material group4
| |-----MVGR5 C(010) material group5
| |-----ZMORT C(010) mat type
| |-----ZZCCODE C(010) char cdoe
| |-----ZZCVALU C(010) charecter value
|
|--5 ZSALT sales taxes
| |-----MATNR C(020) material
| |-----TALND C(003) tax country code
| |-----TAXKM C(010) taxclassification 1
| |-----TAXKM1 C(010) tax clasificaton 2
| |-----TAXKM2 C(010) tax classification3
| |-----TAXKM3 C(010) tax classification 4
| |-----TAXKM4 C(010) tax classification 5
| |-----TAXKM5 C(010) tax classification 6
| |-----TAXKM6 C(010) tax classification 7
| |-----TAXKM7 C(010) tax classification 8
| |-----TAXKM8 C(010) tax classification 9
|
|--5 ZSALTX sales text
| |-----RMATNR C(020) refrence material
| |-----MATNR C(020) material code
| |-----VKORG C(010) sales organization
| |-----VTWEG C(010) distribution channel
| |-----SPART C(010) division
| |-----DESC C(040) descrition
| |-----SPARS C(003) language
|
|--5 ZPUR Purchasing
| |-----MATKL C(010) material description
| |-----MMSTA C(010) plant specific material status
| |-----MMSTD C(008) valid from
| |-----KAUTB C(020) automatic purchase order
| |-----XCHPF C(020) batch management
| |-----EKWSL C(020) purchasing value key
| |-----WEBAZ C(020) goods receiving proc time
| |-----INSMK C(020) post into inspection stock
| |-----KZKRI C(020) critical part
| |-----USEQU C(020) quota arr usage
| |-----KORDB C(020) source list
| |-----FABKZ C(020) jit scheduling
|
|--5 ZPURT Purchasing text
| |-----REMATNR C(020) refrence material
| |-----MATNR C(020) material
| |-----WERKS C(010) plat
| |-----TEXT C(040) text line
| |-----SPRAS C(003) language
|
|--5 ZPLAN Plant data
| |-----MATNR C(020) material
| |-----WERKS C(010) plant
| |-----MEINS C(010) basic unit of measure
| |-----BRGEW C(010) gross weight
| |-----GEWEI C(010) weight unit
| |-----NTGEW C(010) net weight
| |-----MTVFP C(010) availability check
| |-----XCHPF C(010) batch management
| |-----TRAGR C(010) transportation group
| |-----LADGR C(010) loading group
| |-----XMCNG C(010) negative stocks
| |-----PRCTR C(010) profit center
| |-----SERNP C(010) serial number profile
| |-----STAWN C(010) commodity import code
| |-----MTVER C(010) export import group
| |-----CASNR C(010) cash number
| |-----HERKL C(010) contry of origin
| |-----HERKR C(010) regeion of orih\gin
| |-----PRENC C(010) excemption cert
| |-----PRENO C(010) excempton cert no
| |-----PREND C(010) issue date of cert no
| |-----ZDTCD C(010) import duty code
| |-----ZDTRT C(010) import date
| |-----DISGR C(010) mrp group
| |-----EKGRP C(010) purchasing group
| |-----MAABC C(010) abc indicator
| |-----MMSTA C(020) plant specific material status
| |-----MMSTD C(010) date of pim spe status
| |-----DISMM C(010) mrp type
| |-----MINBE C(010) reorder print
| |-----FXHOR C(010) planning time fence
| |-----LFRHY C(010) planing cycle
| |-----DISPO C(010) mrp controller
| |-----DISLS C(010) lot size key
| |-----BSTFE C(010) fixed lot size
| |-----MABST C(010) maximum stock level
| |-----BSTMI C(010) minimum lot size
| |-----BSTMA C(010) maximun lot size
| |-----BSTRF C(010) Rounding value
| |-----DIBER C(010) MRP area exists
| |-----BESKZ C(010) Procurement type
| |-----SOBSL C(010) Special procurement
| |-----LGPRO C(010) Prod. stor. location
| |-----USEQU C(010) Quota arr. usage
| |-----VSPVB C(010) Default supply area
| |-----RGEKZ C(010) Backflush
| |-----LGFSB C(010) Storage loc. for EP
| |-----FABKZ C(010) JIT sched. indicator
| |-----EPRIO C(010) Withdr. seq. group
| |-----SCHGT C(010) Bulk Material
| |-----DZEIT C(010) In-house production
| |-----PLIFZ C(010) Plnd delivery time
| |-----WEBAZ C(010) GR processing time
| |-----MRPPP C(010) Planning calendar
| |-----FHORI C(019) SchedMargin key
| |-----EISBE C(010) Safety stock
| |-----LGRAD C(010) Service level (%)
| |-----EISLO C(010) Min safety stock
| |-----RWPRO C(010) Coverage profile
| |-----SHFLG C(010) Safety time ind.
| |-----SHZET C(010) Safety time/act.cov.
| |-----SHPRO C(010) STime period profile
| |-----ZKROP C(010) ZKROP
| |-----ZZUSI C(010) ZZUSI
| |-----ZRPQT C(010) ZRPQT
| |-----ZZUS2 C(010) ZZUS2
| |-----ZRPCD C(010) ZRPCD
| |-----ZZUS3 C(010) ZZUS3
| |-----ZXKBR C(010) ZXKBR
| |-----ZZPACK C(010) ZZPACK
| |-----ZSKBR C(010) ZSKBR
| |-----ZRTRN C(019) ZRTRN
| |-----ZPDAY C(010) ZPDAY
| |-----ZRPRB C(010) ZRPRB
| |-----ZSTOP C(010) ZSTOP
| |-----ZZMCL C(010) ZZMCL
| |-----ZPRN_FLG1 C(010) ZPRN_FLG1
| |-----ZZSERIALIZED C(010) ZZSERIALIZED
| |-----ZPRN_FLG2 C(010) ZPRN_FLG2
| |-----ZZFRU C(010) ZZFRU
| |-----ZZMENGE C(010) ZZMENGE
| |-----PERKZ C(010) Period indicator
| |-----PERIV C(010) Fiscal Year Variant
| |-----STRGR C(010) Planning strategy group
| |-----VRMOD C(010) Consumption mode
| |-----VINT1 C(010) Bwd consumption per.
| |-----VINT2 C(010) Fwd consumption per.
| |-----MISKZ C(010) Mixed MRP
| |-----PRGRP C(010) Product group
| |-----PRWRK C(010) Production plant
| |-----UMREF C(010) Conversion factor
| |-----VPBME C(010) Planning matl BUnit
| |-----WZEIT C(010) Tot. repl. lead time
| |-----KZPSP C(010) Cross-project matl
| |-----STDPD C(010) ConfigurableMaterial
| |-----ALTSL C(001) Selection method
| |-----KAUSF C(010) Component scrap (%)
| |-----SBDKZ C(010) Individual/coll.
| |-----KZBED C(010) Requirements group
| |-----VERKZ C(010) Special stock maint.
| |-----AHDIS C(010) MRP dep.requirements
| |-----KZAUS C(010) Discontinuation ind.
| |-----AUSDT C(010) Effective-out date
| |-----NFMAT C(010) Follow-up material
| |-----SAUFT C(010) Sales value
| |-----SFEPR C(010) REM profile
| |-----MDACH C(010) Action control
| |-----DPLFS C(010) Fair share rule
| |-----DPLPU C(010) Push distribution
| |-----DPLHO C(010) Deployment horizon
|
|--5 ZFORC forecasting
| |-----MATNR C(020) Material_No
| |-----WERKS C(010) plant
| |-----PRMOD C(010) Forecast model
| |-----PERKZ C(010) Period indicator
| |-----PRDAT C(010) Last forecast
| |-----PERIV C(010) Fiscal Year Variant
| |-----VRBMT C(010) RefMatl: consumption
| |-----VRBWK C(010) RefPlant:consumption
| |-----VRBDT C(010) Date to
| |-----VRBFK C(010) Multiplier
| |-----PERAN C(010) Historical periods
| |-----ANZPR C(010) Forecast periods
| |-----PERIO C(010) Periods per season
| |-----PERIN C(010) Initialization pds
| |-----FIMON C(010) Fixed periods
| |-----KZINI C(010) Initialization
| |-----SIGGR C(010) Tracking limit
| |-----AUTRU C(010) Reset automatically
| |-----MODAW C(010) Model selection
| |-----MODAV C(010) Selection procedure
| |-----KZPAR C(010) Param.optimization
| |-----OPGRA C(010) Optimization level
| |-----GEWGR C(010) Weighting group
| |-----KZKFK C(010) Correction factors
| |-----ALPHA C(010) Alpha factor
| |-----BETA1 C(010) Beta factor
| |-----GAMMA C(010) Gamma factor
| |-----DELTA C(010) Delta factor
|
|--5 ZWSH Work scheduling
| |-----MATNR C(010) Material_No
| |-----WERKS C(010)
| |-----AUSME C(010) Unit of issue
| |-----FRTME C(010) Production unit
| |-----MMSTA C(010) Plant-sp.matl status
| |-----MMSTD C(019) Valid from
| |-----FEVOR C(010) Production scheduler
| |-----LGPRO C(010) Prod. stor. location
| |-----SFCPF C(010) SFCPF
| |-----MATGR C(010) MATGR
| |-----SERAIL C(010) Serial no. profile
| |-----OCMPF C(010) OCMPF
| |-----INSMK C(010) Stock type
| |-----KZKRI C(010) Critical part
| |-----VERKZ C(010) Special stock maint.
| |-----XCHPF C(010) Batch management
| |-----KZECH C(010) Batch entry
| |-----UNETO C(010) Underdely tolerance
| |-----UEETO C(010) Overdely tolerance
| |-----UEETK C(010) Unltd overdelivery
| |-----RUEZT C(010) Setup time
| |-----PRANZ C(010) Number of
| |-----DZEIT C(010) In-house production
| |-----EISBE C(010) Safety stock
| |-----BASMG C(010) Base quantity
|
|--5 ZPLS plant data storage
| |-----MATNR C(010) Material_No
| |-----WERKS C(010) plant
| |-----LGORT C(010) storage location
| |-----MEINS C(010) Base Unit of Measure
| |-----AUSME C(010) Unit of issue
| |-----LGPBE C(010) Storage bin
| |-----LWMKB C(010) LWMKB
| |-----TEMPB C(010) Temp. conditions
| |-----RAUBE C(010) Storage conditions
| |-----BEHVO C(010) Container reqmts
| |-----STOFF C(010) Haz. material number
| |-----ABCIN C(010) CC phys. inv. ind.
| |-----CCFIX C(010) CC indicator fixed
| |-----WESCH C(010) Number of GR slips
| |-----ETIAR C(010) Label type
| |-----ETIFO C(010) Label form
| |-----XCHPF C(010) Batch management
| |-----MAXLZ C(010) Max. storage period
| |-----LZEIH C(010) Time unit
| |-----MHDRZ C(010) Min. rem. shelf life
| |-----MHDHB C(010) Total shelf life
| |-----IPRKZ C(010) IPRKZ
| |-----RDMHD C(010) Rounding rule SLED
| |-----MHDLP C(010) Storage percentage
| |-----BRGEW C(010) Gross weight
| |-----GEWEI C(010) Weight unit
| |-----NTGEW C(010) Net weight
| |-----VOLUM C(010) Volume
| |-----VOLEH C(010) Volume unit
| |-----GROES C(010) Size/dimensions
| |-----XMCNG C(010) Neg. stocks in plant
| |-----LOGGR C(010) Log. handling group
| |-----SERAIL C(010) Serial no. profile
| |-----PRCTR C(010) Profit Center
| |-----EPRIO C(010) Withdr. seq. group
|
|--5 ZWMST WM Structure
| |-----MATNE C(010) MATNE
| |-----WERKS C(010)
| |-----LGNUM C(010) Warehouse Number
| |-----STOFF C(010) Haz. material number
| |-----LVSME C(010) LVSME
| |-----BRGEW C(010) Gross weight
| |-----GEWEI C(010) Weight unit
| |-----AUSME C(010) Unit of issue
| |-----VOLUM C(010) Volume
| |-----VOLEH C(010) Volume unit
| |-----VOMEM C(010) VOMEM
| |-----MKAPV C(010) MKAPV
| |-----BEZME C(010) BEZME
| |-----PLKPT C(010) PLKPT
| |-----XCHPF C(010) Batch management
| |-----LTKZA C(010) LTKZA
| |-----LTKZE C(010) LTKZE
| |-----LGBKZ C(010) LGBKZ
| |-----BLOCK C(010) Seq. blocked
| |-----BSSKZ C(010) BSSKZ
| |-----KZMBF C(010) Message to inv. mgmt
| |-----L2SKR C(010) L2SKR
| |-----KZZUL C(010) KZZUL
| |-----LHMG1 C(010) LHMG1
| |-----LHME1 C(010) LHME1
| |-----LETY1 C(010) LETY1
| |-----LHMG2 C(010) LHMG2
| |-----LHME2 C(010) LHME2
| |-----LETY2 C(010) LETY2
| |-----LHMG3 C(010) LHMG3
| |-----LHME3 C(010) LHME3
| |-----LETY3 C(010) LETY3
|
|--5 ZQMST QM Structure
| |-----MATNR C(010) Material_No
| |-----MEINS C(010) Base Unit of Measure
| |-----QMATV C(010) Inspection setup
| |-----AUSME C(010) Unit of issue
| |-----INSMK C(010) Stock type
| |-----QMATA C(010) QMATA
| |-----KZDKZ C(010) Documentation reqd
| |-----WEBAZ C(010) GR processing time
| |-----PRFRQ C(010) Inspection interval
| |-----RBNRM C(010) RBNRM
| |-----MMSTA C(010) Plant-sp.matl status
| |-----MMSTD C(010) Valid from
| |-----QMPUR C(010) QM proc. active
| |-----LANGU C(010) Language Key
| |-----ART C(010) ART
| |-----APA C(010) APA
| |-----AKTIV C(010) Total
|
|--5 ZACCO account cost
|
|-----MATNR C(010) Material_No
|-----WERKS C(019) plant
|-----BWTTY C(010)
|-----MLAST C(010) MLAST
|-----MLMAA C(010) MLMAA
|-----BKLAS C(010) Valuation Class
|-----EKLAS C(010) VC: Sales order stk
|-----QKLAS C(010) Proj. stk val. class
|-----VPRSV C(010) Price control
|-----PEINH C(010) Price unit
|-----VERPR C(010) Moving price
|-----STPRS C(010) Standard price
|-----LBKUM C(010) Total stock
|-----SALK3 C(010) Total value
|-----ZKPRS C(010) ZKPRS
|-----ZKDAT C(010) ZKDAT
|-----STPRV C(010) Previous price
|-----LAEPR C(010) Last price change
|-----BWPRS C(010) Tax price 1
|-----BWPS1 C(010) Tax price 2
|-----VJBWS C(010) Tax price 3
|-----BWPRH C(010) Commercial price 1
|-----BWPH1 C(010) Commercial price 2
|-----VJBWH C(010) Commercial price 3
|-----ABWKZ C(010) Devaluation ind.
|-----BWPEI C(010) Price unit
|-----XLIFO C(010) LIFO/FIFO-relevant
|-----MYPOL C(010) MYPOL
|-----NCOST C(010) NCOST
|-----EKALR C(010) EKALR
|-----HRKFT C(010) Origin group
|-----HKMAT C(010) Material origin
|-----KOSGR C(010) KOSGR
|-----AWSLS C(010) Variance Key
|-----SOBSK C(010) SOBSK
|-----LOSGR C(010) Planned lot size
|-----KZKUP C(010) Co-product
|-----FVIDK C(010) FVIDK
|-----PPRDZ C(010) Period
|-----PDATZ C(010) Fiscal year
|-----ZPLRP C(010) ZPLRP
|-----PPRDL C(010) PPRDL
|-----PDATL C(010) PDATL
|-----LPLPR C(010) LPLPR
|-----PPRDV C(010) PPRDV
|-----PDATV C(010) PDATV
|-----VPLPR C(010) PreviousPlannedPrice
|-----ZPLP1 C(010) ZPLP1
|-----ZPLD1 C(010) ZPLD1
|-----ZPLP2 C(010) ZPLP2
|-----ZPLD2 C(010) ZPLD2
|-----ZPLP3 C(010) ZPLP3
|-----ZPLD3 C(010) ZPLD3
In 4th step what to do could you pleas sggest me
ZCPROJ - ZCSUB - ZCOBJ demo on object
Structure Relations
|
|--5 BGR00 Batch Input Structure for Session Data
| Select Target Structure BGR00 .
|
|--5 BMM00 Material Master: Transaction Data for Batch Input
| Select Target Structure BMM00 .
|
|-----BMMH1 Material Master: Transfer of Main Data
| Select Target Structure BMMH1 .
|-----BMMH2 Material Master: Country Data for Batch Input (from 2nd Cty)
|-----BMMH3 Material Master: Forecast Values for Batch Input
|-----BMMH4 Material Master: Consumption Values for Batch Input
|-----BMMH5 Mat. Master: Descriptions for Batch Input (Except 1st Text)
|-----BMMH6 Material Master: Units of Measure for BTCI
|-----BMMH7 Material Master: Long Texts for Batch Input
|-----BMMH8 Material Master: Referential EANs for BTCI
in this step these structures are have some fields but in source structure which i created previous steps each structure have fields which are not there in these strcture
could you lease suggest me what to do
regard,
Chaitanya

>Place the cursor on Maintain Source Relations on the LSMW workbench screen and press the Execute button.
>Press the Display<->Change button to switch to Edit mode.
>Here you must map the fields of the source structure with the fields of the destination structure.
>This mapping is important as it will direct the data in the fields from the Source Structure (populated from flat file) to the appropriate fields in the Destination Structure.
Regards,
Pavan P.

Consignment without Deployment and TLB

Hello ,
We currently have DP and PPDS implemented in our system , we are planning to have consignment scenario implemented where the customer sends in the forecast to APO DP .
1) How would the process be if we do not want to implement SNP,Deployment , TLB . Can we still go ahead and implement it . How would the process be . The help document says that once the TLB shipment is sent to ECC an Consignment order is created , but in our case we do not want to implement SNP , Deployement , TLB can we still be able to do it .
Regards,
Nick

Thanks Senthil
We did try with the first option.. Fair share rule "A", But if we deploy based on the demand of the destinations and other destinations with lower demand would be left over. Our business works more on serviceability.
with the second option, As per my understanding Push by distribution is when demand < supply, so that we can push the supply. In my case the demand > supply.
Fair share rule "B" is working fine and Deployment is carried out at SKU level and when a TLB is run it can collate all the SKU for the specific destinations and form a truck.
I would need to perform the steps as per my earlier post. Could you suggest any customized developlment required this??
Regards
Nav

APO Deployment pushing stock in pull scenario

Hello experts,
Right now, I am having an issue with my client regarding the deployment optimizer results. Due to some business reasons, it is necessary to keep the stock in the plant for a certain group of products, instead of deploying it to the distribution centers. The only time the stock can be deployed to the DC is when there is a demand.
The current network is 1 plant and 3 DCs. Push distribution field is setup as blank (pull rule), the pull horizon is set to 10 days and the fair share rule is setup as B.
I have already tested these scenarios (several times with different values):
Non delivery penalty higher in the plant than in the DC:
Product A – plant NDP 2,000,000
Product A – DC 1 NDP 1,000,000
Product A – DC 2 NDP 1,000,000
Product A – DC 2 NDP 1,000,000
RESULT: the stock is deployed to the DC even when there is no demand at the DC.
Storage cost higher in the DC
Product A – plant SC 1
Product A – DC 1 SC 100,000,000
Product A – DC 2 SC 100,000,000
Product A – DC 3 SC 100,000,000
RESULT: the stock is deployed to the DC even when there is no demand at the DC.
If pull horizon is extended, the stock will be kept in the plant only if there is demand in the plant, if there is no demand, the stock is deployed to the DC (tested with previous cost definitions).
Something that is important to know is that max stock level in plant and in DCs is set to 1. This is because normally these products shouldn’t have available stock. Max stock level is a soft restriction (no cost that affects it), so it shouldn’t matter if it is exceeded at the plant (with the result I am getting, the stock is being exceeded at the DC).
What I find confusing about this whole situation is that when I review the Dep Opt Log, it seems to assume the costs implied in deploying the stock to the DC, even when they are way higher than keeping the stock in the plant.
Have anyone faced this same issue before? Any ideas on how can this be configured in the system using the Dep optimizer based on costs?
I would really appreciate your help.
Thanks in advance.

Hi Kenichi,
STO is not generated by a SNP heuristic. You can only generate STR's (Stock Transport Requisition) with SNP heuristic run.
You can generate STR's either by running SNP heuristics on Manfacturing Plant(Location B in your case). Or you can run Network SNP Heuristics on Location A.
Then, you can convert the generated STR to STO either in APO or R3. To do it in APO, you have to run Deployment,followed by TLB run. Or to do it in ECC, you may have to use t-codes like ME59 for converison of STR to STO etc.
Thank you,
Santosh KB.

Deployment after CTM or SNP

Dear Gurus:
We perform CTM run based a prioritized demand. For example: Fulfill sales order first then safty stock request. So, after CTM, system will try to fulfill sales order first and generate related SNP PR.
If we wanna use deployment when there is a supply shortage. But we wanna deployment stock transfer order to fulfill sales order first, not evenly distributed based on fair share rule.
Ex:
Required Qty of Destination Loc--
LOC A 100PC(Sales order) LOC B 100PC(Safety stock)
Supply Qty of Source Loc--
LOC C 50PC
Is this possible to let system generate a deployment order 50 PC to LOC A only because it's sales order request. Not evenlt distributed 50 to LOC A and 50 to LOCB. Is this possible in SAP APO?
Thanks Anyway!
Scott Chen

Well. not really. I was just wondering that if you want to do deployment for sales order driven demands, you may have to do some lite development. The way I would envision your requirement can be done is using the Forecast Horizon field in SNP 2 tab of Location Product. You can set it to a specific value, say 2 months. You may then then run CTM and deployment (in regenerative mode) subsequently.
Then programmatically remove the forecast horizon, run CTM and deployment (both in net-change mode) subsequently. This will ensure that the first pass of CTM and deployment does take care of sales order driven demands first. The second pass will try to plan for other kind of demands if supply is still available. Let me know how it works.

Deployment Optimizer - Modeling question

I am new to the Deployment/Optimizer area. I have modeled a scenario as described below.
And have a few questions on what I would like to happen during deployment.
Central DC: CDC1, Regional DCs: RDC1 & RDC2
Product gets deployed from Central CDC1 to RDC1 & RDC2. I have customer demand and forecasts at all the three locations.
I have defined ATD Receipts category group as just Stock on hand only (category CC) and ATD Issues includes AY, BH, BI,
BM, BR, EB etc. These two categories are assigned to the Location Master.
I have specified Fair Share Rule "A" in the Product master and location dependent penalty costs in SNP1 tab.
In the Deployment Optimizer profile I have mentioned that the Distribution is based on Lowest Costs for both Supply Shortage
and Supply Surplus. I have defined a Pull Depl. Horizon of 10 days, and blank for Push Deployment and SNP Checking Horizon.
When I run the deployment with all the three locations, what I notice is that the Customer orders and forecast of the Central DC are
satisfied before deploying anything to the Regional DCs.
My requirement is that the Central DC should deploy the available quantity at the Central equally among the Centrals and the Regional
DCs on a fair share basis for the Sales orders first, then the remainder of the stock should be deployed, again among Central and
Regional DCs on a fair share basis for the forecast and the safety stock is the last.
How can I achieve this equal deployment among central and regionals even though Central is the source location.
Could somebody let me know how to model this above requirement?
Thanks,
Venkat

Hi Venkat,
I am trying to model the exact scenario where the ATD quantity is not being equally split but the whole chunk is being sent to one of the destination locations. Can you please let me know how you have setup the cost models.
Regards

Fair Share Rule A & B

Similar Messages

Maybe you are looking for