Batch Specific UOM - Rounding error

Hi All,
I just configured Batch Specific UOM to convert pipe material with base UOM of foot to alternate product UOM piece. Length of each piece varies from 30.000 to 35.000 feet.
When I post goods receipt with
1. Unit of entry is alternate UOM (pieces) - system converts qty to feet using planned conversion factor
2. Unit of entry is base UOM (foot) sytsem is rounding off qty in feet to zero decimals and then applying planned conversion factor. While removing decimal digits it gives message "Too many decimal plces for UOM foot" ( 100.78 feet will be changed to 101 feet)
When batch is changed to input correct correct conversion - it changes qty in pieces instead of changing it in base UOM. So now there is no way to enter qty correctly in base UOM with correct decimal places -such as 100.54 foot.
Any help will be appriciated.
Thanks,
Ashutosh
Edited by: Ashutosh_x on Dec 21, 2009 8:18 PM
Edited by: Ashutosh_x on Dec 21, 2009 8:19 PM

have you read this document, especially the Prerequisites?:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/7f/c23c08ddf411d285e20000e82013e8/frameset.htm
I think you have to use Conversion Factors from Object Dependencies instead of Conversion Factor from Two Units of Measure

Similar Messages

Having more than one Unit of Entry (Batch specific UOM)

Hello All
I am using Batch specific UOM (Product Qty Conversion), am working with SQM & NOS as batch specific UOM & the Base UOM of matereial is KG.
My requirement is that at the time of GR for the material I need both batch specific UOMs viz SQM & NOS as the Unit of entry alongwith Base UOM. Looking forward to your valuable inputs.
Regards,
J K Tharwani

Hello Jiteendra,
Could you pl share your findings? We here in Cheese manufacturing want to use multiple Batch specific UOM, while Milk receiving. Milk has components FAT, Protien, Other Solids and Water. I have created 3 Batch specific UOM AU1- FAT, AU2 - Protien and AU3 - Other Solids. When i receive Milk, i enter the percentages as the batch characteristics for all the 3 batch specific UOM and i can see the stock in each of those UOM's.
So far so good....I have all these 3 Batch Specific UOM's defined in the Cheese BOM, with the same Milk material number and batch specific UOM.
But when i try to consume the Milk Batch, i cannot consume the same Milk batch for all 3 components. Do you know how can i consume the same Milk Batch for all the 3 components in the process order for Cheese manufacturing?
Thanks in advance.
Regards,
Mangesh

Creating characterstics used in Batch specific UOM

Hello All
        I am trying to create a characterstic which I can use in Batch specifice UOM for "Product Unit", when am trying to maintain product unit in material master the system throws a message which says:
No characteristic of batch class CL_CUT_LENGTH has organizational area 'Substance / steel'
Message no. LB140
Diagnosis
You must assign the organizational area 'Substance / steel' to characteristics for which you want to maintain proportion or product units.
Procedure
Please assign organizational area 'Substance / steel' to the corresponding characteristics of class CL_CUT_LENGTH.
      Kindly give your inputs on this matter so that I can proceed further. I am unable to figure out how to assign a characterstic to the organizational area "Substance/Steel". Looking forward to your valuable inputs.
Regards,
J K Tharwani

Hello All
      I havent assigned organizational area to the class & when I did that system allowed me to assign the same to the characterstics as well. My issue is resolved & am closing this thread. I am hereby proceeding for "Batch-specific UOM Product qty" & if am again stuck up I would defeinitely look forward to the forum to help me out.
Regards,
J K Tharwani

Batch Specific UoM

Finished products goods receipt is made in litres(BaseUoM).WE also have batch specific unit of measure-Kg.Is there any standard report available to see the finished products batches along with the batch specific unit of measure quantity

hi,
check in MB51....just give your material and execute. After this there is a Detail List (CtrlShiftF12).
Then through Variant you can get Batches and Uom...
Regards,
Mridula.

BATCH SPECIFIC MATERIAL UOM

Dear All,
I created material, base unit of measure EA order unit BOX.1BOX = 40 EA
create PO ORDER 10BOX, 10*40=400ea.
now the problem while receiving GR, I will receive 10box but each box 41ea.so it mean i received 10*41=410ea.
I WANT TO CHANGE PACKING FACTOE IN GR ITSELF.
How to do this scenario?
i think it will work through batch specific UOM.
PLS HELP ME HOW TO CONFIGURE BATCH SPECIFIC UOM BY STEP BY STEP FOR THIS SCENARIO
THANKS,

Hi Bhaskar,
U definitely need batch specific unit of measure for ur scenario. do the following config
1) Activate batch specific unit of measure
2) Create a new batch specific unit of measure in "Edit batch specific unit of measure"
3) Define calculation of proportion quantity from base qty
4) Maintain the batch specific uom in material master
5) Create class with CL02 for batch specific uom - assign relevant characteristic in this class
6) Assign this class to material
At the time of MIGO select the class and assign the new conversion factor
U can change the conversion factor with MSC2N also
Hope this will help u
award points if found useful

Batch-specific Unit of Measure

Hi,
What is Batch specific UOM? How do we configure in ECC 5.0? My requirement is as follows -
1. GR qty should be in Base UOM (Kg) and Bags
2. The qty/bag = 95 Kg (standard / Alt UOM) for material
3. However, for shipment received Qty/Bag may very (90-99 Kg/bag)
4. system should capture Kg & Bags and adjust batch specific UOM accordingly
5 Reporting is required in Base UOM & bags across supply chain

Rajendra
Welcome to SDN
Please see if these links help
http://help.sap.com/saphelp_erp2005/helpdata/en/25/283d744f7811d18a150000e816ae6e/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/c8/3ad93f170f8f15e10000000a155106/frameset.htm
Thnaks
Sat

Batch-Specific Material Units of Measure

Hi all,
Can anybody guide me on Batch-Specific Material Units of Measure----Product/proportion units???
What are the settings required & how it works??
Regards,
Manish

Hi Manish,
The batch specific UoM is used in the process industry where you need to know a characteristic of a batch which is used in evaluating the batch, like concentration or potency. For example, in a sugar syrup, the concentration of sugar may vary and hence it is required to knoe how much sugar is there in the syrup. So you make sugar concentrate as a characteristic in the batch class and use it in the proportionate UoM. So whenever you fill the value of the sugar concentrate in the batch master, how much sugar is there in the syrup is known.
1.     Activate the use of batch-specific units of measure
                 Activate active ingredient management in Customizing using Transaction OMWS. Activate the use of batch-specific units of measure. This allows you to maintain proportion and product units in the material and use them in logistical processes.
2.     Set up the base and proportion/product unit
        In Customizing, the proportion/product unit needs to be created as a unit of measurement. Enter your active ingredient unit of measure under the menu path General Settings  Units of measurement
3. Create Batch Class and Characteristics
4. Assign the class to the material master.
Also set up proportion UoM in additional data of material master. Use the required batch char]acteristics.
So whenever you a Goods receipt you may enter the batch characteristics manually. Or if you are using QM, you may have to activate the link between batch characteristics and inspection characteristics.
Check the stock in proportionale UoM in MMBE
Reagrds
Vineet

Error in Batch Specific Unit of Measure

Dear Friends,
I am maintaining Batch Specific Unit of Measure with Usage as Product Unit for a Raw Material.
Base Unit of Measure : NOS
PO Unit : KG
Batch Specific Unit of Measure : KGP (KG Per Piece)
When I am doing GRN, I am entering
Quantity in Unit of Entry = 7181.7 KG
Quantity in Stock Keeping Unit = 6704 NOS
The System is giving an error:
The qty stored that was entered is adjusted
Message no. XU040
Plese Help me.
Thanks
Prashant Atri

Hello,
As you have different units of measure, review information on conversion with proportion/product unit in note 362932.
See also notes 312510 and 515187
Regards

Pblm in Converting BUOM to Batch specific unit of measure

Hi Gurus
I am Facing a Problem in converting the base unit of measure to batch specific unit of measure.
I have given BUOM in KG.Batch specific unit of measure is PC.
When i do GR for the material in KG with the average wt of the material in kg in the classification view
the system is increasing my GR KG to convert the material to PCS .
I dont want KG to be increased but the PCs to be rounded off to next integer.
How can i resolve this pblm??
NB:- All the settings are done correctly
and all the notes are applicable in ECC 604
Thanks and Regards
BS

Dear
Did you assing any Rounding value and Rouding Profile in MRP1-MM01 for this item ?? Do not maintained this option in MRP1 and check wether you have Kept rouing vadule against KG in CUNI ??
Basically , if you maintain the profile then it will rounds up to the next level based on the thresold valu as configuired in your case in Rouidng Profile in OWD1 .
Also check in MM-Purcahsing -Order Optimisation -Unit of Measure of Rounding rules for purchased item .This based on the control of optimisation of qty.
Hope it helps
Regards
JH

Mass deletion of Batch specific unit of measure

Dear Experts,
How to delete the batch specific unit of measure in the material master maintained in the additional data -unit of measure and proportional / production unit of measure in mass . We have some 1000 material for which we want to remove the datas related to batch specific unit of measure from the material master.

I have not yet seen an option to delete data with MM17, but I am open to be educated.
I would suggest you do it with LSMW or CATT.
However, test it first in MM02, before you waste your time with mass processing. You might receive errors if that material was already in use and batches exist.

Batch specific units of measure

Hi experts,
I've been reading about Batch specific units of measure and I've make some tests following the indications in this blog:
/people/raja.ramasamy/blog/2010/02/22/batch-specific-units-of-measure-step-by-step-configuration-for-steel-industry
In our scenario we work with kg, but we want to keep track of the number of pieces.
But we don't want to introduce the average weight of each batch, we would like to inform the total amount of kg and the number of pieces. Is possible?
Thanks

Hi,
You can maintain info record for the same by using Tcode-ME11 . you can find conversion factor under Purchasing Org1.
Example - Material XYZ, 50KG=1 BAG ,Base UOM in Material Master as BAG
then conversion factor in Info record as follows
Order Unit will be KG
And conversion factor will be 50KG=1BAG.
Regards,
Sandesh Sawant

Batch-specific Unit of Measures

Hi,
1. I have activating batch-specific Unit of Measures, but in MIGO don't show me field for input batch unit. Can you tell me how and where set up - for working with batch-specific Unit of measures.
2. Which tables link is between batch and classification, where I use class type 023-batch. (which fields can I join).
Thanks for your advice.

Batch Specific Unit of measures is what was originally called Active Ingredients Management.
You need to set up QM and classification for this, MIGO will not give you additional field for entering quantity in separate UOM
Lakshman

Batch Input Session - Display Error Only - SM35

Dear all,
Need to do material master extension in MM01 and considering batch input session using mode 'display error' only.
However,do have a concern on its performance or run time. In SM35, running in display error only mode - will there be any time out error like the ones encounter in abap reporting ?
This is because, we will be dealing with a huge volume of data (round 2,000). Therefore would like to know, if there would be any possibility that the bdc session in sm35 will experience a time out or not .
Appreciate it if you could shed some lights on this. Thanks in advance.

Hello there,
Executing MM01's batch job in background wasn't really an option. This is because, this error was encountered "Control Framework: Fatal error - GUI cannot be reached".
Had done a search on this -- and it indicates that in background mode there isn't GUI involved. Searched result also shows that this error appears when its comes to screens with text ie. Purchase Text or Sales text. Nope, no BDC on entering text involved.
http://www.sapfans.com/forums/viewtopic.php?f=13&t=164902&hilit=ControlFramework%3AFatalerrorGUIcannotbe+reached
Therefore the option am considering is executing the batch job in "Display Error Only". Nonetheless, am not too sure if this will cause time out. The other reason as to this option is that -- we initially introduced CALL TRANSACTION for extending material in MM01. However, functional feedback that it was slow.
Kindly advise - thanks in advance.

Flash is introducing insane rounding errors because of some arbitrary decision to round x and y coordinates to 0.05 increments

The data type for x and y properties is a double precision floating-point Number, so why is it rounding off values? Rounding is an unnecessary operation, and furthermore it's not saving any memory, because it just requires me to store a more precise value elsewhere, in addition to the lower-bit rounded value.
This rounding causing unnecessary additional work when coding against these values, because I have to round other values as well to make sure there aren't discrepancies when transforming coordinates.
So I was really surprised to discover that if I assign a value to a DisplayObject's x or y coordinates such as 10.3333333, and trace the value, it becomes 10.3.
If I assign 10.666666, it becomes 10.65. Apparently it's rounding everything to the nearest 20th of a unit. So now, I have to override the x and y properties to store the Number-type value, once again as a Number-type, which is not rounded.
Flash's arbitrary rounding of coordinates is causing erratic rounding errors when performing coordinate system transformations using localToGlobal and globalToLocal to find the composite scale of an object on the stage.
For example, suppose an object was laid out to occupy one third of the display, and it's width ends up being 200.3333333. One calculation of my docking framework involves obtaining the orthagonal bounding box of the child by transforming its corner points into stage coordinates using localToGlobal, which accounts for things like scaling and rotation. So despite everything having a scale of 1, and having zero rotation, you'd still end up with a rectangle with a width of 200.3 instead of the expected 200.3333333 in stage coordinates. So it would appear as though the composite scale is slightly smaller than 1, since 200.3 / 200.333333 is 0.99983361081528. But the composite scale is in fact 1, we just don't know that because Flash unexpectedly rounded some coordinates to an arbitrary 1/20 unit.
No game engine in existence does that with its transformation matrices, because it's retarded to round so early, and then allow those rounding errors to accumulate through a display hierarchy via functions like localToGlobal.
This rounding is causing jittering by a pixel or so when animating a drop down panel in my my docking framework, because it's constantly correcting for unexpected anomalies in the scaling factor on each frame. Despite the parent container having a constant fixed width, the child object, once its corner coordinates are passed through localToGlobal, end up reporting rounded widths, which ultimately leads to a series such as the following:
dockedChild.width: 538.3842482614723, parent.width: 558.3412118444024
dockedChild.width: 538.3754595467979, parent.width: 558.3412118444024
dockedChild.width: 538.3666709755926, parent.width: 558.3412118444024
dockedChild.width: 538.3578825478539, parent.width: 558.3412118444024
dockedChild.width: 538.3490942635798, parent.width: 558.3412118444024
dockedChild.width: 538.3903098666023, parent.width: 558.3412118444024
dockedChild.width: 538.3815210529766, parent.width: 558.3412118444024
dockedChild.width: 538.3727323828218, parent.width: 558.3412118444024
dockedChild.width: 538.3639438561353, parent.width: 558.3412118444024
dockedChild.width: 538.3551554729148, parent.width: 558.3412118444024
dockedChild.width: 538.346367233158, parent.width: 558.3412118444024
dockedChild.width: 538.3875826274011, parent.width: 558.3412118444024
dockedChild.width: 538.3787938582956, parent.width: 558.3412118444024
dockedChild.width: 538.37000523266, parent.width: 558.3412118444024
dockedChild.width: 538.3612167504922, parent.width: 558.3412118444024
dockedChild.width: 538.3524284117897, parent.width: 558.3412118444024
dockedChild.width: 538.3436402165502, parent.width: 558.3412118444024
dockedChild.width: 538.384855402015, parent.width: 558.3412118444024
dockedChild.width: 538.3760666774294, parent.width: 558.3412118444024
dockedChild.width: 538.3672780963132, parent.width: 558.3412118444024
dockedChild.width: 538.3584896586638, parent.width: 558.3412118444024
dockedChild.width: 538.349701364479, parent.width: 558.3412118444024
dockedChild.width: 538.3909170139807, parent.width: 558.3412118444024
Is there any way to turn off this rounding to 0.05 units?
To override the x and y values to have greater precision, I must do the following:
public class Control extends MovieClip
    public function Control()
        super(); //Flash performs timeline/graphics initialization here, which means after this call, the object may have non-zero x and y values
        _x = super.x; //acquire them immediately, so if we try to set x or y to zero, the 'if (_x != value)' check does not think it's already positioned at zero and ignore the call
        _y = super.y;
    private var _x:Number;
    private var _y:Number;
    override public function get x():Number { return _x; } //return precise value, rather than rounded super.x value
    override public function set x( value:Number ):void
        if (_x != value) //ensure value is actually changing before performing work
            _x = value; //store precise value in private variable
            super.x = value; //DisplayObject will round value to nearest 0.05
            if (stage != null)
                stage.invalidate(); //ensure RENDER event is dispatched to re-render anything that may need to account for a repositioned object
    override public function get y():Number { return _y; } //return precise value, rather than rounded super.y value
    override public function set y( value:Number ):void
            if (_y != value) //ensure value is actually changing before performing work
            _y = value; //store precise value in private variable
            super.y = value; //DisplayObject will round value to nearest 0.05
            if (stage != null)
                    stage.invalidate(); //ensure RENDER event is dispatched to re-render anything that may need to account for a repositioned object    }
Most importantly, you must initialize the _x and _y values to super.x and super.y in the constructor immediately after a call to super(), in order to acquire any non-zero values that the object instance may have been initialized with on the timeline.
I just cannot fathom why they didn't leave the x and y coordinates as-is, instead of rounding them, when it causes so many problems and complications, and requires overriding not only x and y, but functions like localToGlobal/globalToLocal/getRect.
This has been an issue for a while:
flash - AS3 x and y property precision - Stack Overflow specifically: flash - AS3 x and y property precision - Stack Overflow
http://www.actionscript.org/forums/showthread.php3?t=96510
Problems with Sub-pixel Coordinate Movement
In fact, that last link says: "
Running the code:
The motion is still jerky; and
The distance between the two squares diverges
However, the one benefit is that the distance does not diverge by more than 1 pixel."
That's precisely what I saw happening in my own code, as you can see from the series of widths I posted above, which seem to fluctuate randomly between 358.34 and 358.39.

Actually, there is a way.
If you simply activate the 3D transformation by setting z to zero, the matrix3D replaces the matrix and concatatedMatrix properties of the DisplayObject's transform object, and suddenly x and y values maintain a precision higher than a twip. It's not quite the double-precision value of the Number type, however, and looks more like a single-precision 32-bit floating point value.
For example, if you run the following code:
var mc:Sprite = new Sprite();
mc.x = 200.0 + (1/3); //assign high precision value to x
trace(mc.x); //traces 200.3 (rounded)
mc.z = 0; //activate 3D matrix
mc.x = 200.0 + (1/3);
trace(mc.x); //traces 200.33333740234374 (still rounded, but accurate to 5 decimal places)
Based on the traced output, it's clear that it is possible to force the DisplayObject to get and set higher precision values for x and y properties, without any modifications to the underlying classes. However, I'm not happy with that solution for 2 reasons. First, it activates stage 3D and introduces graphical glitches and unnecessary bitmap caching. Second, it's still not "Number" precision; it's something less than that.
Instead, I was able to successfully work around the issue by altering the overrides for properties x, y, scaleX, scaleY, and methods localToGlobal, globalToLocal, and getRect to use privately maintained values. I was already using privately maintained width and height values in order to decouple the size from the scaling factors. No need to override getBounds, since it accounts for stroke widths and will be non-exact anyway.
The consistent, high precision values are vital, and they increased the performance of my layout framework, because it's actually able to prevent unnecessary assignments to x, y, width, and height when the values aren't actually changing. #beginrant: Such detection is impossible when Flash internally rounds everything, because if you try to keep something at, for example, 1/3 of the screen, it will always think you're trying to assign a high precision value of 200.33333 over a less precise value of 200.3 as I had previously described. Alternatively, you'd have to pre-round any value you try to assign, which is more work than it's worth. It's sort of terrible that Flash rounds property values as it does, because the value you assign can never be read back the same. That's generally not how numerical properties should work when assigning values of the same data type and precision. #endrant
In particular, two optimizations were made in the getRect override. If the target coordinate system is null or "this", then it simply returns new Rectangle( 0, 0, _width, _height ), and more importantly, if the target coordinate system is "parent" (which is the case 99% of the time) and rotation is zero and scale is 1 (also the case 99% of the time for GUI elements), then it simply returns new Rectangle( _x, _y, _width, _height ), which is the internal, high-precision values for x, y, width, and height (resemblance to AS2 properties is purely coincidental; this is AS3 code). That allows me to skip the following code path 99% of the time, which would otherwise return the orthagonal bounding box of the element at any rotation in any coordinate system:
//These instance variables are used to accelerate calculations, see comments.
//Upper left is always an empty point, and these variables store upper right, lower right, and lower left corner points.
protected var p_UR:Point; //DO NOT ALTER p_UR.y; LEAVE AT ZERO ALWAYS
protected var p_LR:Point; //Lower right corner: x = width, y = height
protected var p_LL:Point; //DO NOT ALTER p_LL.x; LEAVE AT ZERO ALWAYS
//Returns the orthogonal bounding rectangle of the object in the specified target coordinate system
//based on its own internal height and width (actual contentRect may be larger).
//getContentRect function was added to replace the original functionality of this method
override public function getRect( targetCoordinateSpace:DisplayObject ):Rectangle
    switch (_scaleMode) //GUIControl allows decoupling of size and scale
        case SCALE_NOSYNC_SIZE:
            if (targetCoordinateSpace == null || targetCoordinateSpace == this)
                return new Rectangle( 0, 0, _width, _height );
            //UPDATE: Created this optimization to ensure rounding errors introduced by
            //Flash's tendency to round x and y coordinates to twips are not introduced
            //by localToGlobal/globalToLocal calls, so they are avoided if possible.
            if (targetCoordinateSpace == parent && rotation == 0 && scaleX == 1 && scaleY == 1)
                return new Rectangle( _x, _y, _width, _height );
            p_UR.x = _width; //note the p_UR.y is always zero
            p_LR.x = _width;
            p_LR.y = _height;
            p_LL.y = _height; //note the p_LL.x is always zero
            break;
        case SCALE_SYNC_SIZE:
            var contentRect:Rectangle = getContentRect( true ); //must use unscaled points when performing local/global transforms, since this object is scaled
            p_UR.x = contentRect.right; //note the p_UR.y is always zero
            p_LR.x = contentRect.right;
            p_LR.y = contentRect.bottom;
            p_LL.y = contentRect.bottom; //note the p_LL.x is always zero
            break;
    return calcOrthogonalBoundingBox(
        targetCoordinateSpace.globalToLocal( localToGlobal( EMPTY_POINT ) ),
        targetCoordinateSpace.globalToLocal( localToGlobal( p_UR ) ),
        targetCoordinateSpace.globalToLocal( localToGlobal( p_LR ) ),
        targetCoordinateSpace.globalToLocal( localToGlobal( p_LL ) )
protected function calcOrthogonalBoundingBox( p0:Point, p1:Point, p2:Point, p3:Point ):Rectangle
    //Assuming no rotation, points 0 and 3 are most likely to be min_x. This optimization minimizes the likely number of assignments.
    //Similar optimizations are in place for max_x, min_y, and max_y, all patterns are ordered 0,1,2,3... starting with the two most likely candidates in the sequence.
    var min_x:Number = p3.x;
    if (p0.x < min_x) min_x = p0.x;
    if (p1.x < min_x) min_x = p1.x;
    if (p2.x < min_x) min_x = p2.x;
    var max_x:Number = p1.x;
    if (p2.x > max_x) max_x = p2.x;
    if (p3.x > max_x) max_x = p3.x;
    if (p0.x > max_x) max_x = p0.x;
    var min_y:Number = p0.y;
    if (p1.y < min_y) min_y = p1.y;
    if (p2.y < min_y) min_y = p2.y;
    if (p3.y < min_y) min_y = p3.y;
    var max_y:Number = p2.y;
    if (p3.y > max_y) max_y = p3.y;
    if (p0.y > max_y) max_y = p0.y;
    if (p1.y > max_y) max_y = p1.y;
    return new Rectangle( min_x, min_y, max_x - min_x, max_y - min_y );
In this framework, particularly in SCALE_NOSYNC_SIZE mode (the default), the width and height are assigned and internally maintained, independently of the scaleX and scaleY values. The internally maintained values are used for performing layout and drawing operations such as backgrounds and borders. In the extremely rare occasion where the actual content needs to be measured, I just use getBounds, such as in the constructor when initializing the "original" size of the clip's content, if it has timeline content, or possibly bitmap methods for masked objects.
These changes have all increased the performance of my framework by an order of magnitude and have virtually eliminated 3rd layout passes, so I'm happy with it. I still wish the Flash runtime would be updated to simply stop rounding these values.

Activating batch-specific material unit of measure

Hi all,
my client has a SAP ECC 5.0 system with over 30 plants, which are currently using batch management. For a new plant we have the need to work with the batch-specific material unit of measure to have KG as base UOM and to calculate the quantity of bags regarding the batch specific conversion factor.
Does anybody now which impact will follow on the current batch management and stock in the other plants after activating the batch-specific material unit of measure in the Customizing?
Thanks in advance,
Robert

Hey all,
I found something in standard SAP... You can use a dependency on the level of the batch class and in there it is possible to write some calculation code.
Thanks for the input,
Philippe

Batch Specific UOM - Rounding error

Similar Messages

Maybe you are looking for