Openbravo Issue Tracking System - Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0034671ModulesFIFO Costing Algorithmpublic2016-12-01 18:142016-12-02 15:06
Reportermaite 
Assigned ToTriage Omni OMS 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Regression date
Regression introduced by commit
Regression level
Review Assigned Toaferraz
Support ticket44612
OBNetwork customerOBPS
Regression introduced in release
Summary0034671: "InventoryClosing" transaction type needs to be included in "isOutgoingTrx" method in FifoAlgorithm,java
DescriptionWhen using FIFO algorithm and trying to validate a different costing rule, following error is raised in the log : @OBWFA_NotOutgoingTransaction@ (by getOutgoingTransactionCost method). Problem is that "InventoryClosing" transaction type is not considering as outgoing transaction
Steps To Reproduce1. In an instance using FIFO algorithm
2. Access Costing Rule window and create new rule for Average algorithm
3. Run "Validate costing rule" process and realize that error is raised
4. Check the log and you will find '@OBWFA_NotOutgoingTransaction@'
Proposed Solutionprivate boolean isOutgoingTrx() {
    switch (trxType) {
    case Shipment:
    case ReceiptReturn:
    case ReceiptNegative:
    case InventoryDecrease:
    case IntMovementFrom:
    case InternalCons:
    case BOMPart:
    case ManufacturingConsumed:
    case InventoryClosing:
      return true;
    default:
      return false;
    }
  }
Additional Information
TagsNo tags attached.
Relationships
duplicate of defect 0033379 closed markmm82 Cannot validate a new Costing Rule after validating a costing rule with FIFO algorithm 
blocks defect 0034670 closed Triage Omni OMS CostingServer should check if current algorithm supports adjustments, when trying to adjust remainder value in inventory closing 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2016-12-01 18:14maiteNew Issue
2016-12-01 18:14maiteAssigned To => Triage Finance
2016-12-01 18:14maiteResolution time => 1482361200
2016-12-01 18:14maiteSupport ticket => 44612
2016-12-01 18:14maiteOBNetwork customer => Yes
2016-12-01 18:14maiteRelationship addedblocks 0034670
2016-12-01 19:51aferrazRelationship addedrelated to 0033379
2016-12-02 11:56aferrazReview Assigned To => aferraz
2016-12-02 11:56aferrazStatusnew => closed
2016-12-02 11:56aferrazResolutionopen => fixed
2016-12-02 15:06aferrazRelationship deletedrelated to 0033379
2016-12-02 15:06aferrazRelationship addedduplicate of 0033379

There are no notes attached to this issue.