0016489: 3.0RC5.1: Problem with posting for activated table M_InOut

Openbravo Issue Tracking System - Openbravo ERP

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0016489

Openbravo ERP

09. Financial management

public

2011-03-25 12:45

2015-02-12 14:22

Reporter

RenateNieuwkoop

Assigned To

eduardo_Argal

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

closed

Resolution

out of date

Platform

OS Version

Product Version

3.0RC5

Target Version

Fixed in Version

Merge Request Status

Review Assigned To

OBNetwork customer

Web browser

Modules

Core

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0016489: 3.0RC5.1: Problem with posting for activated table M_InOut

Description

I activated the M_InOut table and executed a goods shipment. This went well in RC4, but now I get a post error in both RC5 and RC5.1

Steps To Reproduce

Using the F&B International Group Admin role:

    First we have to activate the table related to goods receipt and goods shipment
    Go to the Accounting Schema screen,
        Select F&B US, Inc. US/A/US Dollar
    Go to the [Account Schema Tables] tab
        Select the M_InOut (MaterialMgmtShipmentInOut) table
        Select the Active checkbox
        Save the record

Go to the Goods Shipment screen
Create a new record

    Organization = F&B US, Inc.,
    Movement Date = today's date,
    Accounting Date = today's date,
    Business Partner = Moon Light Restaurants, Co.,
    Warehouse = US West Coast,
    Save the record

Go to the [Lines] tab
Create a new record

    Organization = F&B US, Inc.,
    Product = Energy Drink,
    Storage Bin = WC-2-0-0,
    Movement Quantity = 10,
    Save the record

Go back to the main tab and complete the document
The posting will be done by the background process, when you refresh the screen after a couple of minutes the unpost button is visible.

The button is not unpost though, but Post:Error

Proposed Solution

Additional Information