cancel
Showing results for 
Search instead for 
Did you mean: 

COMPUTE_FLOAT_ZERODIVIDE when display sales delivery

Former Member
0 Kudos

Hi All,

Before describing the issue will give you complete overview about the below requirement

Material X ( base UoM - PC) after certain duration becomes unusable & needs to be sold as scrap in alt

UoM MT (metric ton).

So we decided to create a dummy material let us say Y and then follow below steps:

1) Transfer the stock from 'X' to 'Y' through 309

2) Then create sales order .

3) Create the delivery and do the PGI

4) Then do the billing.

Then we had one more limitation that material 'X' weight (MT) will vary. So we decided

to activate batch management for dummy material 'Y' and go for batch specific UoM.

In standard when we add batch specifi UoM in BMA1 transaction , in the reference Unit column

we were not able to put PC , since PC is a dimensionless unit.

So we created a new dimensionless UoM, MTP (Metric ton per piece) and added this in BMA1 and

put reference unit as MT.

After this I added the configuration 'Define Calculation of Product Quantity from Base Quantity' in BMA3.

We were able to capture batch specific qty for the dummy material whenever transfer posting is done.

ISSUE:

But now the issue is that when we create sales order then delivery & PGI in single step, we are not facing any issue in

displaying the delivery document in VL03N.

While when we create delivery first & save and then do PGI and try to display the delivery document it is going

for dump

Runtime Errors COMPUTE_FLOAT_ZERODIVIDE

Exceptn CX_SY_ZERODIVIDE

For those deliveries with problem in LIPS table numerator field is updating with zero.

What could be reason for this issue? Please throw your valuable inputs.

Regards,

Partha

Accepted Solutions (1)

Accepted Solutions (1)

Lakshmipathi
Active Contributor
0 Kudos
Runtime Errors COMPUTE_FLOAT_ZERODIVIDE

Check note 888999 or 889334

thanks

G. Lakshmipathi

Former Member
0 Kudos

Hi ,

Thanks for input. We identified the issue. This was due to an user exit.

I am closing this thread.

Partha

Answers (0)