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

Similar Messages

BADI for Changing Deployment Rounding Value

Hello All,
During my Deployment run I need to consider the rounding value from the /sapapo/marm table and not from the product master. So I need a badi or user exit to change the rounding value for deployment run. Do let me know how I can achieve this.
Thanks,
Siva.

Dear Tiemin,
Thanks for your reply. But I need a BADI which needs to work when there is no Fair Share situation. It will be great if you provide me which suits for it.
Thanks,
Siva.

Rounding Value in Excise in Purchasing and Invoice Verification

Hi,
We need to round the values in PO on BED, Ecess (2%) & SEcess (1%) but the value is not getting rounded.
Similarly in Financial Invoice Verification (FB60), the values of Service Tax is also not being rounded.
In Configuration
IMG u2013 Log Gen u2013 Tax on Goods Movm u2013 India u2013 Basic Setting u2013 Company Code Settings u2026u2026u2026u2026u2026u2026.. Rounding Rules have been ticked for procurement & removal
But the values are not getting rounded off in ME21N & FB60 and subsequent transactions
Can anyone give some idea to resolve this?
Thanks in advance

Thanks Sanil
It's working now. But we are facing an issue with rounding value in case of Vendor Return. When we are posting Vendor Return Excise Invoice through TCode J1IS then system is rounding the value whereas when we are posting Vendor Return Excise Invoice through TCode MIGO then system is not rounding the values.
Can you provide any idea to resolve this?
Thanks in advance

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

Deployment rounding issue

Dear Friends,
After running deployment for purchase requisitions coming from PP/DS I am getting message:
Deployment stock transfer was not confirmed ( 11,000 < 40,000 (rounding value))
Here 11 is PR quantity and 40 is rounding value. Some PRs are not getting converted in deployment orders and so getting material shortage. We want system to upsize PR(purchase requisition) qty to rounding value in this case.
Please suggest any note,setting,user exit or BAdi to do this.
Thanks in advance.
Best regards,
Shirish

Hi Amol,
Thanks for reply. My problem is diffrent I have sufficient ATD quantity and all settings are maintained properly. Say purchase requisition quantity is 130 EA and rounding value is 50. Then after deployment run I am getting order of 100EA and for remaining 30EA we are getting open PR which will not get convert in to deployment order. So there will be always shortage of 30 in ECC. I want system to round up quantity to 150EA.
Hope you have understand issue. Kindly let me know fir more information.
Thanks,
Shirish

Issue in Decimal value round off

Hi All, I am facing an issue wherein Decimal value of 0.01 is getting converted to 0.00. Let me brief you about Source-target Types - Source - Flat FileTarget - DB2Powercenter Version - 9.6.1 HF2 Issue - Field in Source File is defined as Number(5,2).Corrosponding field from Db2 Target Table is defined as Decimal(5,2). Mapping is simple straight forward mapping with 1:1 loading from Source to target. Now, my Source File contain data as below - 0.010.020.0312.01 When I execute mapping, DB2 target Table gets loaded with all records.Value from corrosponding DB2 Target Table is - 0.000.020.0312.01 As you can see value of 0.01 is getting converted to 0.00 whereas all other values are working fine as expected. As a quick fix, I have applied to_decimal(source_field,2) before loading it to target. Could anyone please explain if this is an issue with Powercenter or there's some other issue. If I think it's a rounding issue then how come value of 0.02 is working fine? Please advise.

Hi All, I have one scenario to read the source file . The file delimiter is '|' . The no of pipeline for each line is 17. So if a line containing more than 17 , send an error email. For this first i am printing tota pipeline in ecah line to afile called pipelinecount.txt . Then i will read this file and send each value to while loop /for loop , where it will get > 17 , it will exit the process and send an email. But here in script i am getting error at while line. Could anyone help. #! /bin/kshset -x SOURCE_DIR=/vp01/SrcFilessed 's/[^|]//g' /vp01/SrcFiles/Test.txt | awk '{ print length }'> /vp01/SrcFiles/pipelinecount.txtcd $SOURCE_DIRwhile line in `cat pipelinecount.txt`; do if [ $line -eq 17 ];thenecho "No issue in pipeline"exit 0;fiif [ $line -gt 17 ];thenecho "No of pipelines exceeded the expected. Please verify the source file." | mailx -s "WKFS Load: Failed" [email protected]

Re: Issue in Decimal value round off in DB2

Hi All, It is happening only only when the decimal separator of source is ',' and behaving normally when decimal separator is '.'. Some how ..we casted the incoming field to TO_DECIMAL(IN_FIELD,2) ..in that case it is working fine. Regards,Srinivas

Hi All, I am facing an issue wherein Decimal value of 0.01 is getting converted to 0.00. Let me brief you about Source-target Types - Source - Flat FileTarget - DB2Powercenter Version - 9.6.1 HF2 Issue - Field in Source File is defined as Number(5,2).Corrosponding field from Db2 Target Table is defined as Decimal(5,2). Mapping is simple straight forward mapping with 1:1 loading from Source to target. Now, my Source File contain data as below - 0.010.020.0312.01 When I execute mapping, DB2 target Table gets loaded with all records.Value from corrosponding DB2 Target Table is - 0.000.020.0312.01 As you can see value of 0.01 is getting converted to 0.00 whereas all other values are working fine as expected. As a quick fix, I have applied to_decimal(source_field,2) before loading it to target. Could anyone please explain if this is an issue with Powercenter or there's some other issue. If I think it's a rounding issue then how come value of 0.02 is working fine? Please advise.

How to cancel rounding value check when convert pr to po use me59n or me59

hello every one,
        I have a requisition that,customer want to cancel rounding value check when converting purchase requisition to purchase order use me59n or me59,but they want keep the function of check rounding value when create purchase requisition as mrp run.
        does anyone happen to meet samiler question?Is there any way to solve it?
        thanks
Edited by: p y on Aug 3, 2010 5:14 AM
Edited by: p y on Aug 3, 2010 10:07 AM
Edited by: p y on Aug 3, 2010 10:56 AM
Edited by: p y on Aug 3, 2010 10:57 AM

what do you think based on what SAP should know whether it has to do rounding or not?
Why should SAP not round if a rounding rule is entered?
when a human is converting the PR to a PO, then a warning message is issued, if the user then enters the old quantity again, SAP accepts it.
A background program cannot do such decisions, it has to rely on given master data.

Issues with Rounding in Scriptlogic

All,
I am currently on BPC 7.0 MS and I am updating script logic in our Finance Application. The logic's intent is to spread an amount (total) to 12 periods evenly. This is working just fine. Where I run into my issue is my numbers come back with several decimal places so I need a way to round it. Below is a piece of the code but I have not found a good way to round the =%VALUE%/12.
Any suggestions?
WHEN DATASRC
*IS *
*WHEN TIME
*IS %YEAR%.INP
      *REC(EXPRESSION=%VALUE%/12,TIME=%YEAR%.001,DATASRC="INPUT")

Hi Vineet,
What was suggested to you earlier were 2 options for rounding up your values:
1. Changing the appset parameter: If you use this option, then all the data in your database, will have the exact structure in terms of number of decimal places. If you say 25,2, then all the transactional records will have only 2 places of decimal.
2. The other option, as suggested by man_noel, you can use the ROUND keyword in your script logic. This way, you are just rounding off the results, only. The other data remains the same as it was earlier.
ROUND((%VALUE%/12),n)
The above statement will rounf off the result to n places of decimal.
Hope this helps.

Min Lot Size and Rounding value

Hello MM Gurus
need a small help!
I m a bit confused regarding the use of Min lot size and Rounding value in material master "MRP 1" view..
can some body teach me a detailed functionlity for both..
As both serve the purpose ..for e.g. my requirement is 7 and min lot is 10 system will create proc.proposal for 10
in similar way if i use rounding value as 10 , then als system will create proc.proposal for 10 only even if requirement is 7.
grateful if you could pl expain me the functionality of both...
another query..if I use Min lot size in material master will the same will serve the puspose of <b>min order qty ( maintained in PIRs)</b>
i'lll appriciate with good reward points...thanks in advnace
Br
Sumit

Helo Guys..
Thanks for valuable inputs..
i have assigned the appropriate rewards ..
pl clear my this doubt also
e.g. for a materials
Min Lot size - 40
Rounding value 25
requirement is for - 35
will it be 40 or 50 ..i understand 50..
j
ust anothe rquery..pl treat this separate issue..and separate rewards will be given
<b>can I use max stock level w/o use of lot size "HB"</b>
e.g. if my max stock level is 80
and min lot size is 30 and current stock is 60
what'll be my proc proposal created by MRP , i dont want system to cross 60 stck,,
Thanks in advance
BR
Sumit

How to change PR Qty before rounding value is applied during MRP run?

Hi, SAP gurus~
I have an inquiry about how to change the PR qty of specific raw material before rounding value was applied during MPR run.
Here is a simple example for what I needed.
-SAP Original Logic
1. Original requirement Qty: 190
2. Rounding value at Material Master (MRP1 View): 200
     System will suggest PR Qty 200 at MD04.
-My Customer Requested Logic
1. Original requirement Qty: 190
2. Additional buffer Qty for C/S purpose: 10 % of Original requirement.
3. Rounding value at Material Master (MRP1 View): 2000020
     Requirement Qty would be 209 (190 + (190 x 10%) ) before rounding value is applied and system should suggest PR Qty 400 at MD04.
-     I input assembly/component scrap rates (10 %) at Material master for above purpose, but it doesn`t not work for raw material.
-     I tested the BADI (MD_PURREQ_CHANGE/ method: CHANGE_BEFORE_SAVE_MRP), but I can only change the PR Qty, which rounding value already applied.
How can I change the PR qty during MRP run before rounding value is applied? Is there any other method or User-exit possible to solve above problem?
Thanks in advance.

Dear ,
How can I change the PR qty during MRP run before rounding value is applied? :
Simple way is goto MD04 with your material and plant code -Select the PR-Hit the pencil (change mode ) -Choose qty field and change , SAVE at individual level .Or Use : MEMASSRQ - Mass Maintenance
If you want to use User Exit , then you try a work around :
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition release
Try and let us know if u have any issue .
Regards
JH

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

How to use rounded values in BEx Formulas

Hello,
I have the following question. Is it possible to use rounded values up to a certain # of decimal points in BEx Formulas?
I have the following problem.
Consider this:
keyfigure val 1 = 0.416666667
keyfigure val 2 = 72
val 3 (BEx Formula) = val 2 / val 1 = 172.799999862
However, what I need to do is this.
val 1 & val 3 should rounded up to 2 decimal points. So, I really need the report to show this:
val1 = 0.42
val2 - 72
val 3 = val 2 /val 1 = 171.43
I changed the number of decimal places on val 1 and val3 to be 0.00. However, it appears that these rounded values are not taken into account in the Formulas, as if the OLAP still uses the original values from the backend with 9 decimal points. So, no matter how many decimal points I use on the Display tab for a key figure, my val3 or result of my formula is always taking into account the 9 digit decimal values, not rounded values that I want. So in the example above, my val 3 comes to 172.80, which it should be 171.43 instead of you use the rounded values in the calculation.
Please let me know if there is any workaround where I could force my BEx Formula to utilize the rounded values and not actual values from the backend DSO. Or any other solution.
Thank you

If you create a Formula in BEx Query Designer like the one below, it works:
val3 = val2 / ( TRUNC ( ( val1 * 100 + 0.5 ) ) / 100 )
The TRUNC function (among other things) actually ensures that your formula takes into account the rounded values that you want.

Issue Deployment rounding value & Fair Share

Similar Messages

Maybe you are looking for