Open Source ERP Openbravo

M_Transaction / 在庫状況

2009-06-11T16:55:00.006+09:00

Stck Report

-- SQL --

SELECT
M_PRODUCT_CATEGORY.NAME                                                         AS CATEGORYNAME,
M_PRODUCT.VALUE||'-'||M_PRODUCT.NAME                                        AS NAME,
SUM(MOVEMENTQTY)                            AS MOVEMENTQTY,
             M_LOCATOR.X,
             M_LOCATOR.Y,
AD_COLUMN_IDENTIFIER('M_WAREHOUSE', to_char(M_LOCATOR.M_WAREHOUSE_ID), :1)   AS WAREHOUSE,
M_LOCATOR.Z, C1.NAME                        AS UOMMOVEMENTQTY,
M_ATTRIBUTESETINSTANCE.M_ATTRIBUTESETINSTANCE_ID,
M_ATTRIBUTESETINSTANCE.DESCRIPTION,
(CASE WHEN M_TRANSACTION.M_PRODUCT_UOM_ID IS NULL THEN (CASE M_PRODUCT.WEIGHT*SUM(M_TRANSACTION.MOVEMENTQTY)
     WHEN 0 THEN NULL ELSE M_PRODUCT.WEIGHT*SUM(M_TRANSACTION.MOVEMENTQTY) END) ELSE SUM(M_TRANSACTION.QUANTITYORDER) END  )                     AS WEIGHT,
(CASE WHEN M_TRANSACTION.M_PRODUCT_UOM_ID IS NULL   THEN (CASE WHEN M_PRODUCT.WEIGHT = 0 THEN ''  WHEN M_PRODUCT.WEIGHT IS NULL THEN '' ELSE 'Kgs' END) ELSE TO_CHAR(C2.NAME) END) AS UOMWEIGHT,
           '' as id
FROM M_PRODUCT
left  join M_PRODUCT_CATEGORY on M_PRODUCT.M_PRODUCT_CATEGORY_ID = M_PRODUCT_CATEGORY.M_PRODUCT_CATEGORY_ID,
     M_PRODUCT_UOM
right join M_TRANSACTION      on M_TRANSACTION.M_PRODUCT_UOM_ID  = M_PRODUCT_UOM.M_PRODUCT_UOM_ID                       
left  join C_UOM C2           on M_PRODUCT_UOM.C_UOM_ID          = C2.C_UOM_ID,
     M_LOCATOR, C_UOM C1,
     M_ATTRIBUTESETINSTANCE
WHERE M_TRANSACTION.M_PRODUCT_ID              = M_PRODUCT.M_PRODUCT_ID    
AND  M_TRANSACTION.M_ATTRIBUTESETINSTANCE_ID = M_ATTRIBUTESETINSTANCE.M_ATTRIBUTESETINSTANCE_ID
AND  M_TRANSACTION.M_LOCATOR_ID              = M_LOCATOR.M_LOCATOR_ID     
AND  M_TRANSACTION.C_UOM_ID                  = C1.C_UOM_ID    
AND  M_TRANSACTION.AD_CLIENT_ID IN (0,1000000)        AND  M_TRANSACTION.AD_ORG_ID IN (0,1000000)       AND  1=1
AND  M_TRANSACTION.MOVEMENTDATE <> 0    
ORDER BY  M_PRODUCT_CATEGORY.NAME,M_PRODUCT.VALUE, M_PRODUCT.NAME,     M_ATTRIBUTESETINSTANCE.DESCRIPTION,M_LOCATOR.X, M_LOCATOR.Y,
  M_LOCATOR.ZSELECT M_PRODUCT_CATEGORY.NAME AS CATEGORYNAME, M_PRODUCT.VALUE||'-'||M_PRODUCT.NAME AS NAME,
  SUM(MOVEMENTQTY) AS MOVEMENTQTY,
  M_LOCATOR.X,     M_LOCATOR.Y,     
  AD_COLUMN_IDENTIFIER('M_WAREHOUSE', to_char(M_LOCATOR.M_WAREHOUSE_ID), :1) AS WAREHOUSE,
  M_LOCATOR.Z, C1.NAME AS UOMMOVEMENTQTY,
  M_ATTRIBUTESETINSTANCE.M_ATTRIBUTESETINSTANCE_ID,
  M_ATTRIBUTESETINSTANCE.DESCRIPTION,
  (CASE WHEN M_TRANSACTION.M_PRODUCT_UOM_ID IS NULL THEN (CASE M_PRODUCT.WEIGHT*SUM(M_TRANSACTION.MOVEMENTQTY)
    WHEN 0 THEN NULL ELSE M_PRODUCT.WEIGHT*SUM(M_TRANSACTION.MOVEMENTQTY) END) ELSE SUM(M_TRANSACTION.QUANTITYORDER) END) AS WEIGHT,     
  (CASE WHEN M_TRANSACTION.M_PRODUCT_UOM_ID IS NULL THEN (CASE WHEN M_PRODUCT.WEIGHT = 0 THEN '' WHEN M_PRODUCT.WEIGHT IS NULL THEN '' ELSE 'Kgs' END) ELSE TO_CHAR(C2.NAME) END) AS UOMWEIGHT, '' as id
    FROM M_PRODUCT
    left join M_PRODUCT_CATEGORY on M_PRODUCT.M_PRODUCT_CATEGORY_ID = M_PRODUCT_CATEGORY.M_PRODUCT_CATEGORY_ID,
         M_PRODUCT_UOM
    right join M_TRANSACTION     on M_TRANSACTION.M_PRODUCT_UOM_ID  = M_PRODUCT_UOM.M_PRODUCT_UOM_ID    
    left join C_UOM C2           on M_PRODUCT_UOM.C_UOM_ID          = C2.C_UOM_ID,
         M_LOCATOR, C_UOM C1,
         M_ATTRIBUTESETINSTANCE    
           WHERE M_TRANSACTION.M_PRODUCT_ID = M_PRODUCT.M_PRODUCT_ID
           AND M_TRANSACTION.M_ATTRIBUTESETINSTANCE_ID = M_ATTRIBUTESETINSTANCE.M_ATTRIBUTESETINSTANCE_ID
           AND M_TRANSACTION.M_LOCATOR_ID = M_LOCATOR.M_LOCATOR_ID
           AND M_TRANSACTION.C_UOM_ID = C1.C_UOM_ID 
           AND M_TRANSACTION.AD_CLIENT_ID IN (0,1000000)   AND M_TRANSACTION.AD_ORG_ID IN (0,1000000)                   AND 1=1
           AND M_TRANSACTION.MOVEMENTDATE <> 0    
 ORDER BY  M_PRODUCT_CATEGORY.NAME,M_PRODUCT.VALUE, M_PRODUCT.NAME, M_ATTRIBUTESETINSTANCE.DESCRIPTION,M_LOCATOR.X, M_LOCATOR.Y, M_LOCATOR.Z

How-to MRP / Create Requisitions and Work Requirements

2009-06-10T16:54:00.009+09:00

Create Requisitions and Work Requirements

Once the results are checked it is possible to Create the Material Requirements (or Requisitions) and the Work Requirement with the correspondent buttons of the header.

Purchasing Plan

http://wiki.openbravo.com/wiki/Functional_Documentation/Procurement_Management

Requisition
Functionality available in version 2.40
Users can initiate the procurement flow by entering requisitions rather than purchase orders. This enables a clear separation of roles and duties between:
The Requestor who expresses a demand for goods or services through a requisition.
The Purchasing Specialist who selects the most appropriate supplier based on the organization strategic procurement objectives and generates the purchase order, either manually or automatically based on rules.

Create Purchase Orders

http://wiki.openbravo.com/wiki/User_Manual_2.40/Procurement_Management

How-to MRP / After processing the plan

2009-06-10T15:13:00.008+09:00

Manufacturing Plan

Create a new Manufacturing Plan.

Name: Manufacturing Plan 1

Document Date: 2008-06-15

Time Horizon: 60

Lead Time: 1

Planner: Planner 1

After processing the plan 10 lines are inserted in the Lines tab.

実行後、Lines に１０行データが作成されている。

We can see how it has considered the Sales Order,

Salse Order が考慮されているのがわかるが、

but not the Work Requirement because its Launch WR Date (2008-08-05) is later than the 30 days limit set in the Planning Method.

Work Requirement は実行日が Plan で設定したの３０日以降なので考慮されていない。

On the Document Date we can see the 2 lines related to the stock of the products that are being planned,

Document Date: 2008-06-15 に製造品の在庫設定により２レコードのデータが作成されているのがわかる

in this case only the Usb Cable, as the Raw Materials are purchased.

今回の場合　Usb Cable のみ、なので原材料関係だけが購入される。

If the USB Cable had an intermediate product that was produced in a different Process plan it would have appeared here with its own Work Requirement suggestion if necessary.

仮に　USB Cable が仕掛品をもっていた場合、別の Process Plan がその Work Requirement suggestion ともに必要に応じて表示される。

The remaining lines are related to the sales order.

残りの行は Sales order 関連のものである。

As the order is promised for July 7th and the Lead Time is 1 the MRP suggest a Work Requirement that would finish on July 6th.

７月７日が出荷予定でリードタイムが１日なのでMRPは７月６日に製造完了するように指示している。

This Work Requirement is of 600 units because it is considering also the Minimum stock of 100 units.

今回の Work Requirement の数　600 unit には最小在庫数１００が考慮されている。

This Work Requirement consumes some raw materials at June 30th that is when is expected to start the production.

今回の製造で原材料が６月３０日に消費されるが、これは製造開始時に考慮されている。

This leads to material requirements suggestions for the day before.

原材料のリードタイムについては事前に指示。

In the requirements in the Planned Order date is also calculated when should be ordered this products to arrive on time.

Planned Order Date も製造品の order に従い算出される。

MRP Run

2009-06-09T16:05:00.017+09:00

ようやく MRP を実行することができた。

以下のSQLの検索結果がえら得るように画面を操作したが、一度動作すると、M_Product_ID = 100000 関連のデータを元に戻しても問題なく動作する。

SELECT
P.M_PRODUCT_ID,
M_PRODUCT_CATEGORY_ID,
COALESCE(SD.QTYONHAND,0) AS QTYONHAND,
COALESCE(PO.STOCKMIN, P.STOCKMIN, 0) AS STOCKMIN,
COALESCE(PO.MRP_PLANNINGMETHOD_ID, P.MRP_PLANNINGMETHOD_ID) AS MRP_PLANNINGMETHOD_ID
FROM M_PRODUCT P
LEFT JOIN M_PRODUCT_ORG PO ON P.M_PRODUCT_ID = PO.M_PRODUCT_ID
AND PO.AD_ORG_ID = 1000000
LEFT JOIN ( SELECT M_PRODUCT_ID, SUM(QTYONHAND) AS QTYONHAND
FROM M_STORAGE_DETAIL GROUP BY M_PRODUCT_ID) SD ON P.M_PRODUCT_ID = SD.M_PRODUCT_ID
WHERE (1000014  IS NULL OR P.M_PRODUCT_ID = 1000000   )
AND (1000004  IS NULL OR P.M_PRODUCT_CATEGORY_ID = 1000004  )
AND COALESCE(PO.MRP_PLANNER_ID, P.MRP_PLANNER_ID) = 1000000
/

F_Doc/Process Manufacturing Plan Logic

2009-06-08T14:45:00.006+09:00

Process Manufacturing Plan Logic

The manufacturing plan process is structured in three different steps.

製造計画は３つのステップからなる。

Before starting these steps the manufacturing plan lines that are not fixed are deleted, normally these lines are the proposals created in previous execution of the process.

ステップ開始時、fix していない製造計画詳細(MRP_Run_Productionlines)のデータは削除される。

And all the remaining lines are set as not exploded except the lines of products that are manufactured in a work requirement in progress as the lines of the products that are consumed in that work requirements will already exist.

Initialization

Once the lines are prepared begins the process, the first step is the initialization.

まず初期化。

The initialization consists on including in the process all the transactions expected to happen during the defined time period and that fulfills the planning method of each product.

期間をチェック

In this step are considered all the products that fulfills the filters set in the manufacturing plan.

To know if a product has been initialized or not, the existence of inserted stock lines is checked. The stock lines are always included. For the purchase plan process are considered the purchase and sales orders, the sales forecasts and work requirements in progress.

Explode product tree

In the second step is exploded the tree of products that are manufactured. The explosion is performed in a recursive manner while not exploded lines exist. On each iteration all not exploded lines are considered. If the quantity of the line is negative it is a demand so a new line is inserted with opposite quantity. If the product of the line is purchased the new line is a Material Requirement proposal with planned and order date a number of days before defined by the lead time, the line is inserted as exploded as the purchases are managed in the purchasing plan. When the product is not purchased the new line is a Work Requirement proposal. The planned date is calculated using the lead time as the previous case, the order date that states the beginning of the needed production is calculated based on the capacity, minimum delay and needed quantity. When the quantity of the line is positive it is assumed that the line is of a product that is needed to produce and is not exploded. In this case is necessary to insert a line for each product related with in the production, all the raw materials and also the secondary products that can be produced in the default process plan of the product. The new lines of raw materials are inserted as not exploded and their planned date is the calculated date in which the production should start. If the product of the line that is being exploded is used as raw material to produce other products those products are initialized to be also considered in the manufacturing plan. Finally the line is set as exploded. When all the lines are exploded is checked if there still are not exploded lines to repeat the loop until all lines are exploded.

Process plan

Lastly each product is planned calculating the necessary quantities and dates. This section is still to be completed.

Create Work Requirements Logic

The work Requirement creation process creates a work requirement header for each proposal generated in the Manufacturing Plan process. The ending date is the need by date calculated in the proposal and the start date is also calculated in the proposal based on the capacity and minimum delay defined for the product. The creation date is defaulted to the current date.
Conversion rate and process unit are not filled by this process.

Work Requirements are created without processing them in order to allow a final review before initiating production.

Each proposal is then linked with the created work requirement for traceability purposes.

Create Material Requirements Logic

This section is still to be completed.

F_Doc/Manufacturing Plan

2009-06-08T14:44:00.003+09:00

Manufacturing Plan

Openbravo's manufacturing plan consists in creating work requirements and material requirements based on product demand. This process explodes all the product tree so all related products are planned. The source of material demand can be sales orders and sales forecasts. During the planning process it also takes into account current stock, minimum stocks, unreceived purchase orders and open work requirements.

When processing the plan, the products to be planned can be selected using several filters:

Product
Product category: all products in the category
Planner: all the products associated with the planner
Customer: all the products purchased by the customers
Partner group: all the products purchased by the customers of the group.

Please notice that this filter is only used at the beginning of the process but product selection grows as the product tree is exploded.
For example, in the following image, all the products will be planned when at least one of them fulfills the filter. When product C is planned it is necessary to plan the demand of its intermediate product F. The demand for F is driven by C but also by product B, which is then also planned. Similarly, to plan F it is necessary to also plan the raw materials product I and product J.
Continuing with this explosion process, we see that all the products in the tree need to be planned.

When the product tree is exploded, the planning process generates proposal lines that are linked to each other with a parent-child relationship.
Every product demand has its own work requirement proposal or material requirement proposal. Each work requirement proposal has different child lines, the main one is to manufacture the correspondent material requirement, and the children are for the products that are used and that might be created in the work requirement.

After the Manufacturing Planning process, it is possible to manually adjust the work requirement or material requirement recommended by MRP by editing quantities and dates.
When editing a work requirement, you only need to change the main line; you can then recalculate the dates and quantities of all the children lines by pressing the Recalculate button.

To put the manufacturing plan into execution, it is necessary to create the work requirement and material requirements from all the proposals using the correspondent processes.
The created Work Requirements only have the header so it is necessary to process it to create the operations and products. This is to allow a final review before initiating production.

Fl_Doc/Configuring MRP in Openbravo

2009-06-07T16:15:00.004+09:00

Configuring MRP in Openbravo

For the planning processes to work correctly, you have to properly configure the products and the vendors.

Planning Process には　Products と Vendors の設定が必須。

Before starting it is needed to create the necessary planning methods and planners as they are required in the product configuration.

Planning 関連の設定の前提として、Procudts の設定が必要。

It is very important to pay attention to the organizations where the products and vendors are being configured.

Products と Vendors の設定には　organizations の設定が重要であるので注意すること。

Product Configuration

The products have to be configured for each organization that performs manufacturing or purchase planning. You can do this in the Product definition window, in the Org Specific tab. The relevant attributes are:

Default Process Plan: required for manufactured products.
Planning Method: the planning method to use.
Planner: the planner responsible for the product in the organization.
Capacity: the maximum daily capacity for the product, to purchase or to produce. If the demand exceeds the capacity, the proposal will extend beyond one day.
Min. Quantity: the minimum quantity that can be purchased or to produced.
Qty. Type: defines how the quantity of the proposals is calculated.
- Exact, each proposal is for this exact quantity and MRP recommends as many purchase or work requirements as necessary to fulfill the demand. For example, if this value is 10 and the demand is for 55, 6 proposals for 10 each are recommended.
- Multiple, the proposal quantity is a multiple of this quantity. For example, if this value is 10 and the demand is 55, one proposal for 60 is recommended.
- If no type is defined the proposals are created with the needed quantity.
Minimum lead time: minimum lead time in days to complete the proposal. For example, if this value is 10 and a product is needed for October 30th, MRP suggests initiating purchasing or production on October 20th.
Safety stock: minimum stock level to maintain during the planning processes. For example, if this value is 50 and the quantity on hand is 100, for a demand of 60, MRP suggests to purchase or produce 10.

Vendor Configuration

Further, to process the purchase plan it is necessary to set at least one current vendor for the products. For each product and vendor, you can specify:

Minimum purchase quantity
Promised delivery time (in days)
Minimum order quantity
Quantity type
Capacity.

In the purchase plan process, if these data is not defined for the selected vendor, it is defaulted from the values specified at product and organization level.

Process Plan Configuration

The correct definition of a process plan is essential for the correct execution of MRP as the process plans is needed to explode the product demand.

MRP, however, does not have any additional configuration options for process plans beyond what is required for Production Management.

F_Doc/MRP Concepts

2009-06-07T13:22:00.004+09:00

http://wiki.openbravo.com/wiki/Functional_Documentation/MRP

http://wiki.openbravo.com/wiki/User_Manual_2.40/Materials_Requirement_Planning_(MRP)

http://wiki.openbravo.com/wiki/ERP/2.50/User_Manual/Materials_Requirement_Planning_(MRP)

MRP Concepts

Material Requisitions

Material Requisitions are demands for products to be purchased.

Material Requisitions　: 製造のためにどのような部材を購入（仕入れ）する必要があるか。

They are the output of the Production Plan process - which creates demand for raw material - and a possible input of the Purchase Plan process.

Material Requisitions : Production Plan process の raw material の需用、あるいは Purchase Plan Process からも作成される、

Each requirement is identified by a document number and it is composed of one or more lines, one per needed product and date combination. For each line, the following attributes are specified:

Product
Need by date
Requested quantity
Vendor (optional)
Price list (optional)
Price (optional)
Currency (optional)

Sales Forecast

Sales Forecasts are a projection of customer demand for a given product or expected sales for customers. They can be used as inputs in theManufacturing Plan and in the Purchasing Plan.

The key attributes of a sales forecast are:

Business partner: the customer to whom you forecast the sale
Date (optional): the date on which you enter the forecast - you can use this attribute to version the forecast.

A forecast is made of several lines; each line specifies the product for which you expect demand, the date when you expect the sale to occur, and the quantity expected be sold.

Planning method

The planning method is used to set the different transaction types that are considered during the planning process, as either supply or demand.

The planning method is a property of the product so different products can have a different planning method.

The available transaction classes for the planning method are:

Requisitions (Material Forecast)
Purchase Orders in progress
Sales Forecasts
Sales Orders in progress
Work Requirement in progress

For each transaction type, it is also possible to define whether transactions are considered for the whole time horizon or just for a portion:

Days from start: the number of days from the beginning of the planning period to the start of the transaction time frame being considered.
Days to end: the number of days from the beginning of the planning horizon up to which transactions are considered.

You can also specify the percentage of quantity to be considered using the Weighting attribute. For example, if you specify a weight of 0.9 for Sales Forecast, if you provide a forecast of 100 units for a specific product, the planning method will only consider 90 units.

Planner

The Planner is an entity used to filter the products considered in the planning processes. On each purchase or manufacturing plan is possible to select a planner so only products associated with that planner are considered.

Typically, in an enterprise, different people are responsible for planning manufacturing and purchasing of different products. You can usePlanners to model that practice.

Please notice that in the manufacturing plan process other products can be included when the product tree is exploded, see Manufacturing Plan section.

How-to MRP / MRP Execution

2009-06-06T13:22:00.007+09:00

MRP Execution

Once the MRP has been set up it is possible to start running the MRP processes.

MRP のセットアップが完了させたら、MRP　を実行する。

In this example is created a Sales Order of USB cables and a Work Requirement for USB Cables that it is not enough to fulfill the Sales Order.

今回の例の　Sales Order "USB cables" と Work Requirement "USB Cables" は Sales Order には十分ではない。

Insert demand見込み

Create and complete a Sales Order using a document type that does not generate the corresponding shipment, in this case is used the Standard Order and a Scheduled delivery date 2008-07-07. The order has a unique line for 500 USB Cables.

USB　Cables を５００本　見込む。

Create and process a Work Requirement for 100 Usb Cable. The three dates are the same 2008-08-05.

Manufacturing Plan

Create a new Manufacturing Plan.

Name: Manufacturing Plan 1
Document Date: 2008-06-15
Time Horizon: 60
Lead Time: 1
Planner: Planner 1

After processing the plan 10 lines are inserted in the Lines tab. We can see how it has considered the Sales Order, but not the Work Requirement because its Launch WR Date (2008-08-05) is later than the 30 days limit set in the Planning Method.

How-to MRP / Process Plan

2009-06-06T12:33:00.003+09:00

Process Plan

Prior to create the Process Plan it is necessary to properly setup the manufacturing module, in this example are created just 2 Activities, Build cable and Ensemble USB Cable.

Build cable と　Ensemble Cable の２つからなる Proces Plan を作成する。

It is created the Process Plan 'Usb Cables', with one version valid from 2008-01-01 to 2008-12-31. The Process plan has 2 operations defined using the following table.

今回作成する Proces Plan 'Usb Cables' は以下の２つのオペレーションから構成される。

Activity	Multiplier	P- product (qty)	P+ product (qty)
Build cable	1	Copper (0.1 units) Plastic (0.1 units)	Cable (1 unit)
Ensemble cable	1	Cable (1 unit) Plug (2 units)	Usb Cable (1 unit)

How-to MRP / Products

2009-06-06T12:01:00.018+09:00

Products

All the products are created under the new product category Cables

製造品カテゴリ"Cables"を作成し、製造品にはこのカテゴリを使用

and are checked as production products.

製造品は"Production"をチェック。

In the following table is shown all the relevant configuration of the products, the process plan has to be updated on the product later when it is created. The MRP specifics are defined in the Org specific tab, for raw materials are also inserted in the Purchasing tab (it is used Anghet ,Company as current vendor).

部品(M_Product)は Org specific タブで組織(M_Product_Org)と紐付けされている。

また row materials (Copper, Plastic,Plugs) は Purchasing タブで仕入先( vendor )を紐付けされている。

The intermediate product Cable is not considered in the MRP as all the cable created in the process plan is consumed in the same process plan to produce the usb cable.

仕掛品 Cable はMRP対象外　（usb cable の process plan による）

The raw materials and the finished products are also included in a price list: 01-01-2005 Special nº1 for the Usb cable and01/01/2005 Purchase for Copper, Plastic and Plugs

原料と完成品はそれぞれ上記のprice listに登録されていること。

Name	Purchase	Sale	Process PlanPlanningMethod	Org specific	Capacity	Safety Stock	Min. Qty/ Min.Order Qty.	Prom. Delivery Time
Copper	Y	N		California		1	10	10
Plastic	Y	N		California		1	5	15
Cable	N	N
Plugs	Y	N		California		100
Usb cable	N	Y	Usb Cables	California	100	100	1

How-to MRP

2009-06-05T14:30:00.013+09:00

http://wiki.openbravo.com/wiki/How-to_MRP

MRP Setup

Planner

Planner Planner 1.

Typically, in an enterprise, different people are responsible for planning manufacturing and purchasing of different products. You can use Planners to model that practice.
企業内では生産を計画する担当者とその生産に必要な資材の購入を担当する人は別々であるため、こうした Planner が必要となる。

Planning Method

Material Requirement Planning (MRP) || Setup || Planning Method || Header >> Lines

Products

How-to MRP / Products

Configuring the default date and time formats

2009-05-31T20:19:00.003+09:00

日付書式　Date Format を変更するにはやはり再コンパイルが必要

やはり　YYYY/MM/DD に関連した不具合があるため、 DD-MM-YYYY にしようとしたが
Openbravo.properties の NLS_DATE_FORMAT の変更だけでは対応できない。

Configuring the default date and time formats

To change the default Openbravo ERP date format launch the setup tool inside the config/setup-tool directory.

Once all the changes are done, recompile and deploy Openbravo ERP:

ant compile.complete

ant war

ant deploy

Configuring the default numbering format

You can modify the default numbering format by editing the Format.xml file inside config directory. You should have decimal="." grouping="," for every category. Once this is done you will have to restart Tomcat and the reports will show as you wish.

http://wiki.openbravo.com/wiki/Openbravo_ERP_installation#Configuring_the_default_date_and_time_formats

2.6 Sales Management

2009-05-29T22:01:00.001+09:00

Pay the Purchase Invoice

2009-05-29T21:53:00.005+09:00

5. Pay the Purchase Invoice

Short description:Test the cash journal using the payment that is above

Steps:
- Login as userA
- Go to Financial management->Receivables and Payments->Transactions->Cash journal
- Click New, fill the mandatory fields and save
- Move to Lines Tab
- Click New and select Cash Type: Debt-Payment
- Click on Payment icon and:
  - Business partner: VENDOR A
  - Unmark Receipt check
  - Be carefully with the dates. You will only see the payment within the correct ranges
  - Click Search and mark the payment. Click OK
- Verify the Amount field is filled with the amount of the payment
- Go back to header and process
- Click "Not posted"
- Verify the journal entry is correct

Issues to verify:When you process a Cash journal, a Settlement is created in order to cancel the payment. To verify this:
- From the Cash journal window move to Lines tab
- Select one line and click "Linked Items"
- You must see the link "Settlement - Cancelled Payments". Click it
- You must see the link of the payment. Click it
- You must browse to Cancelled Payments tab

ora-6508　が発生するケースあり。( C_CASH_POST )

Accounting Purchase Invoice 仕入仕訳

2009-05-29T21:46:00.007+09:00

4. Accounting Purchase Invoice

Short description:Accounting the above purchase invoice

Steps:
- Login as userA
- Go to Procurement management->Transactions->Purchase invoice
- Being in edit mode click "Not Posted" and click OK
- Verify the created journal is correct

Additional data: If you cannot see the button "Not Posted" please go to General setup->Application->Session Preferences. Mark "Show accounting tabs" and then click "Save preferences". Doing this you will be able to enter in the book

Create Purchase Invoice 仕入れ明細請求

2009-05-29T21:21:00.009+09:00

Short description: Testing the button 'Create lines from' and the way of creating purchase invoices

Steps:
- Login as userA
- Go to Procurement management->Transactions->Purchase invoice
- Click New and select Transaction Document= AP Invoice[買掛]
- Select the business partner using two possibilities:
- A.- Click on the bp icon and verify:
  - When you click the bp icon a pop-up window must show up and the radio button 'provider' must be checked. Please select VENDOR A
- B.- Or write in the bp box VA and verify:
  - A pop-up window doesn't show up and the bp box is filled with the name VENDOR A
- For both cases verify:
  - Invoice from: "Pamplona, Street Purchase center nº1"
  - The combo box User/Contact must have the value: John
  - Price list: PURCHASE
  - Form of payment: Wire Transfer
  - Payment terms: 90 days
- Click on button 'Create lines from' and verify:
  - Business partner: VENDOR A
  - In the "Order" combo box there is the purchase order
  - In the "Shipment" combo box there is the good receipt
- Select the good receipt and click OK
- Move to Lines and verify:
  - Product: A Raw material
  - Taxes: VAT 10%
  - The box "Purchase Order Line" is filled properly
  - The box "Shipment/Receipt Line" is filled properly
- Go back to Header and click Complete
- Move to Payments and verify:
  - Due Date 90 days after the invoice date
  - Form of Payment: Wire transfer

ORA-6508 で完了できず。　データの問題か？
0005111: Oracle error after completing a purchase invoice

https://issues.openbravo.com/view.php?id=5111

C_INVOICE_POST.xml の改訂履歴　を確認した範囲でもこの不具合は報告されていない。

C_INVOICE_POST Procedure の再作成により動作するようになる。

Create Goods receipt 入庫処理

2009-05-29T21:09:00.004+09:00

2. Create Goods receipt

Short description: Testing the button 'Create lines from' and the way of creating goods receipt

Steps:
- Login as userA
- Go to Procurement management->Transactions->Goods receipt
- Click new and select VENDOR A as a business partner. Save
- Click on button 'Create lines from' and verify:
  - Business partner: VENDOR A
  - In the "Order" combo box there is the purchase order
- Select the purchase order
- Select a warehouse position
- Select the purchase order line
- Click OK
- Move to Lines
- Click on Attribute set value icon and fill the values and click OK
- Go back to header and Complete

Create a purchase order

2009-05-29T20:29:00.008+09:00

1. Create a purchase order

Short description:Create an order to be used when creates a good receipt

Steps:
- Login as userA
- Go to Procurement management->Transactions->Purchase Order
- Click New and two possibilities:
- A.- Click on the bp icon and verify:
  - When you click the bp icon a pop-up window must show up and the radio button 'provider' must be checked. Please select VENDOR A
- B.- Or write in the bp box VA and verify:
  - A pop-up window doesn't show up and the bp box is filled with the name VENDOR A
- For both cases verify:
  - Invoice from: "Pamplona, Street Purchase center nº1"
  - The combo box User/Contact must have the value: John
  - Price list: PURCHASE
  - Form of payment: Wire Transfer
  - Payment terms: 90 days

Vendor が設定されていないと Business Partner に表示されない。

Product を選択する際の Price List は "Pruchase -EUR" を選択しないと　A Raw material が表示されない。

Move to tab Lines and click New. There are two possibilities:
A.- Click on the product icon and verify:
- When you click the product icon a pop-up window must show up.
- The price list combo must be filled with the value Purchase
- When click Search only 3 products must appear: A Raw material, B Raw material, C Raw material. Select A Raw material
B.- Or write in the product box RMA and verify:
- A pop-up window doesn't show up and the product box is filled with the name Raw material
For both cases verify:
- UOM:Unit
- Unit price:2
- List price:2
- Tax:VAT 10%
Fill in Ordered quantity= 1
Move to header and complete. Verify:
- Summed Line Amount= 2
- Grand Total Amount= 2.2

Complete しても　Grand Total Amount= 2　となり 2.2 とはならず。

2.5 Procurement management

2009-05-29T19:24:00.000+09:00

2.5 Procurement management

Create Bank

2009-05-29T19:06:00.004+09:00

2. Create Bank

Short description:Create a bank and related to a business partner. The goal of relating a business partner with the bank is to be able to use the remittance window

Steps:
- Login as userA
- Go to Financial management->Receivables & Payables->Setup->Bank
- Click New
- Fill the mandatory fields:
  - Name: SampleBank
  - Bank code: 1234
  - Branch code: 0001
  - Control Digit: 0
  - Address:
    - 1st Line:Sample Street
    - Postal Code:31010
    - City:Pamplona
    - Region:Navarra
    - Country:Spain
- Save
- Move to Account and fill the mandatory fields:
  - Partial Account No.:1111111111
  - Control Digit:0
  - Mark "Show Spanish"
- Save

Go to Master Data->Business partner
Click New and fill
- Search Key:BANK
- Name:Bank
Go back to Bank click on Bpartner icon and, after marking the option "All", select the business partner

Create remittance type

2009-05-29T17:39:00.003+09:00

1. Create remittance type

Short description:Create a remittance to test other features

Steps:
- Login as userA
- Go to Financial management->Receivables & Payables->Setup->Remittance type
- Click New and fill:
  - Name:'Remittance 19'
  - Mark Consolidate
  - Payment Rule Consolidated:Bank Remittance
  - Final Status:In Remittance
  - Returned Status: Returned
- Move to Parameter tab
- Click New
- Fill Name=Contract, content=001 and save
- Click New
- Fill Name=Cuaderno, content=19 and save

Aditional data:Please write the names as it is explained. Both, Contract and Cuaderno, are parameters that OB uses

2.4 Administration financial data

2009-05-29T17:35:00.001+09:00

2.4 Administration financial data

Update Business partner to add a business partner tax category

2009-05-29T17:32:00.001+09:00

4. Update Business partner to add a business partner tax category

Short description: Create business partner tax category to test taxes in transactional documents. Add the new category to Customer A

Steps:
- Login as userA
- Go to Master Data management->Business partner
- Select "CUSTOMER A" and, inside Customer tab, select "SO BP Tax Category"=Vat 3%+Charge 0.5%

Create G/L Item

2009-05-29T17:25:00.002+09:00

3. Create G/L Item

Short description: Create a GL/Item to test other features

Steps:
- Login as userA
- Go to Financial management->Accounting->Setup->G/L Item
- Click New and fill name=G/L Item A
- Move to Accounting tab
- Create a new record
- Select an expense account (i.e 649 using ESAccounts) for both debit and credit
  - If the account combination does not exist first find the account then select the organization and press Save

Editing Document sequence

2009-05-29T17:17:00.003+09:00

2. Editing Document sequence

Short description: Edit the document sequences for AR Invoice

Steps:
- Login as userA
- Go to Financial management->Accounting->Setup->Document type
- Select "AR Invoice" record in edit mode
- Click link Document Sequence
- Fill Prefix=I/ ,Next Assigned Number=1

Create fiscal calendar

2009-05-29T17:05:00.002+09:00

1. Create fiscal calendar

会計期間を開く

Short description: Create periods and open document for each period

Steps:
- Login as userA
- Go to Financial management->Accounting->Setup->Fiscal calendar->Year
- Click button create periods
- Move to each period and click button Open/Close All

Issues to verify: For any period move to Period control tab and verify the documents are open

import.sample.data ( V2.50MP1)

2009-05-26T20:28:00.005+09:00

３月２日のファイルでも以下のエラーとなる

https://code.openbravo.com/erp/devel/pi/log/cbbf45c0800c/referencedata/sampledata/Accounting_Test.xml

https://code.openbravo.com/erp/devel/pi/file/cbbf45c0800c/referencedata/sampledata/SmallBazaar.xml

https://code.openbravo.com/erp/devel/pi/log/cbbf45c0800c/referencedata/sampledata/SmallBazaar.xml

import.sample.data:
[echo] Importing sample reference data
[importsampledata] 2 [main] ERROR org.openbravo.base.util.CheckException - Property shipmentReceiptLine does not exi
st for entity MaterialMgmtMaterialTransaction
[importsampledata] org.openbravo.base.util.CheckException: Property shipmentReceiptLine does not exist for entity Materi
alMgmtMaterialTransaction
[importsampledata] at org.openbravo.base.util.Check.isNotNull(Check.java:72)

2.50 tar ball

2009-05-26T16:43:00.005+09:00

2.50 の tar ball をダウンロードして ant install.source すると
Database が Oracle でも PostgreSQL でも接続エラーとなる。

compile:
   [javac] Compiling 68 source files to C:\Openbravo\OpenbravoERP-2.50MP1\src-core\build\classes
   [javac] C:\Openbravo\OpenbravoERP-2.50MP1\src-core\src\org\openbravo\database\ConnectionPool.java:83: シンボルを見つけられません。
   [javac] シンボル: クラス OpenbravoDriverManagerConnectionFactory
   [javac] 場所 : org.openbravo.database.ConnectionPool のクラス
   [javac] ConnectionFactory connectionFactory = new OpenbravoDriverManagerConnectionFactory(_server,
   [javac] ^
   [javac] C:\Openbravo\OpenbravoERP-2.50MP1\src-core\src\org\openbravo\database\ConnectionProviderImpl.java:150: シンボルを見つけられません。
   [javac] シンボル: クラス OpenbravoDriverManagerConnectionFactory
   [javac] 場所 : org.openbravo.database.ConnectionProviderImpl のクラス
   [javac] ConnectionFactory connectionFactory = new OpenbravoDriverManagerConnectionFactory(dbServer,

Virtual Machine Appliance の /opt/AppsOpenbravo 以下のソースを
もってきて ant すると、エラーとはならない様子。

sample data

2009-05-26T16:15:00.003+09:00

2.50MP1 環境でも sample data のインストールは失敗する。

0007899: Build Failed in ant target import.sample.data

https://issues.openbravo.com/view.php?id=7899

# cd /opt/AppsOpenbravo

# ant install.source

.

clean.src.gen:

generate.entities:
[workflow] Adding param: /opt/AppsOpenbravo/src/org/openbravo/base/gen/gen_entity.oaw
[workflow] Adding param: -pob.properties.location=/opt/AppsOpenbravo/config/Openbravo.properties
[workflow] Adding param: -pbase.src.gen=/opt/AppsOpenbravo/src-gen
[workflow] Adding param: --ant
[javac] Compiling 441 source files to /opt/AppsOpenbravo/build/classes

import.sample.data:
[echo] Importing sample reference data

BUILD FAILED
/opt/AppsOpenbravo/build.xml:494: The following error occurred while executing this line:
/opt/AppsOpenbravo/build.xml:398: The following error occurred while executing this line:
/opt/AppsOpenbravo/src/build.xml:180: org.openbravo.base.exception.OBException: No import files present in the import directory: /opt/AppsOpenbravo/referencedata/sampledata

Total time: 27 minutes 3 seconds

Openbravo ERP: 2.50MP1 available

2009-05-25T21:45:00.006+09:00

Openbravo ERP: 2.50MP1 available
http://forge.openbravo.com/plugins/espnews/browse.php?group_id=100&news_id=112

- ダウンロードしたファイルを Module Management より実行する。

注意:

bug in the 2.50 appliance delete the /opt/AppsOpenbravo/README file before launching the upgrade.

/opt/AppsOpenbravo/README ファイルを手動で削除してからパッチを適用すること

一部適用でエラー

update.database:
Database connection: jdbc:postgresql://localhost:5432/openbravo. User: tad
Database has local changes. Update.database will not be done. If you want to force the update.database, do: ant update.database -Dforce=yes (you will lose all your changes in the application dictionary if you do it)
The following error occurred while executing this line:
/opt/AppsOpenbravo/src-db/database/build.xml:126: Database has local changes. Update.database not done.

手動にて強制実行

[root@localhost AppsOpenbravo]# pwd
/opt/AppsOpenbravo
[root@localhost AppsOpenbravo]# ant update.database -Dforce=yes
...

BUILD SUCCESSFUL
Total time: 7 minutes 13 seconds
[root@localhost AppsOpenbravo]# pwd

Product Import / Error

2009-05-25T19:47:00.005+09:00

2.50 では Procuct の Import を実行する前に default tax code の設定が必要。
エラーが表示される。　default tax code 設定後、　再度 Import を実行すると
ハングアップする。

強制的に

# service postgresql restart 　した後は必ず
# service tomcat restart 　　　が必要

PostgreSQL だけ再起動し、 Tomcat を再起動しない場合、以下のようなエラーとなる。

HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.hibernate.TransactionException: JDBC rollback failed
org.hibernate.transaction.JDBCTransaction.rollback(JDBCTransaction.java:170)
org.openbravo.dal.core.SessionHandler.rollback(SessionHandler.java:226)
org.openbravo.dal.core.DalThreadHandler.doFinal(DalThreadHandler.java:48)
org.openbravo.dal.core.ThreadHandler.run(ThreadHandler.java:70)
org.openbravo.dal.core.DalRequestFilter.doFilter(DalRequestFilter.java:85)
root cause
org.postgresql.util.PSQLException: An I/O error occured while sending to the backend.
Exception: java.net.SocketException: Broken pipe
Stack Trace:
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)

Ver.2.50 Virtual Machine Appliance

2009-05-25T15:32:00.001+09:00

Virtual Machine Appliance

SVN から取得した最新バージョン 2.50 で　

http://localhost:8088/openbravo/

にてアクセス可能となったので　Acceptance Test をこの環境で実行。

最初の client (このERPソフトを使う会社名のこと）の登録で

Currency(通貨）を設定する必要があるのだが、この List of Values に値が表示されない。　

c_currency テーブルに値が insert されていない。 Seed Data 未登録。

コマンドラインから ant で　creata database する方法はわかったが ...

C:\pleiades\workspace\openbravo>ant create.database -Dapply.on.create=true

にてまず、　dopr user xxx cascade; 　してから、再作成を開始する。
ただ、 Tomcat が起動したままだと　”接続中のユーザーは削除できません”ので注意。

sampledata や　reference data の登録の部分は動作しないようなので、 2.40 の環境から
c_currency テーブルの内容を exp して　imp table=c_currency ignore=y することで
currency は表示されるようにはなったが、 client の登録で失敗する。

新方式　2.50 の Virtual Machine Appliance のインストール形式を利用すること。

これは実に簡単にインストールが完了する。

VMware Player がインストールされていれば、これようのファイルをダウロードして

解凍してえられる　ｖｍｘ　ファイルを　 VMware Player で開くと窓のなかで　OS　が

起動し、　プロンプトに表示される　URL にアクセスすると

OpenBravo の ERP ソフトを利用できるようになっている。

Port 80 で起動しているのでこれまでだめだった Heartbeat テストもクリア。

Tera Term などで　Virtual Machine (192.168.1.2:22 でユーザー openbravo) に Loginできる。

# su - postgres
$ psql -l
List of databases
Name | Owner | Encoding
----------+----------+----------
openbravo | tad | UTF8
postgres | postgres | UTF8
template0 | postgres | UTF8
template1 | postgres | UTF8
(4 rows)

\i xxx.sql
\q

$ psql openbravo -f xxx.sql

ファイル名を指定して PostgresSQL で　SQLを実行するため、ファイル共有に

VMware Player のフォルダ共有機能を利用しようとしたが、 Windows 2008 Server の

共有機能とのからみか、なかなかうまくいかず、また時間を費やしてしまった。

/usr/bin/vmware-config-tools.pl

にてVMware Player の表示画面のサイズを変更して大きくする方法がわかったことは成果としてある。
設定変更の反映には再起動が必要。
ただし、今回の Virtual Machine では X11R6 は含まれないため、画面表示のサイズ変更にはメリットはなし。

　$ sftp ユーザー名@ホスト名　

にて Linux 側の設定なしでファイル転送は可能であったので、

cygwin に　Net - OpenSSH と OpenSSL　をいれて、 sftp を使用することに。

FileZilla では sftp://192.168.1.2@openbravo

2.10 Assets: Create Amortization Plan

2009-05-20T11:41:00.001+09:00

2.10 Assets: Create Amortization Plan

Skip

2.9 Accounting processes

2009-05-20T11:40:00.001+09:00

2.9 Accounting processes

Skip

2.8 Project and Service management

2009-05-20T11:39:00.000+09:00

2.8 Project and Service management

Skip

Create Work effort

2009-05-20T11:24:00.005+09:00

7. Create Work effort

Short description: Test the way of creating a work effort

Steps:
- Login as userA
- Go to Production management->Transactions->Work Effort
- Click New and fill:
  - Movement date= Current date
  - Starting Time: 08:00:00, Ending time: 16:00:00
- Move to Production Run tab and click new
- Select the "WR Phase" and verify:
  - The fields "Required quantity", "Process unit" and "Conversion Rate" are filled based on the WR phase
- Fill Done quantity=2 and save

Click on button "Create Standards"
- The field "Cost centre used" is calculated well depending on you what configure on the Cost Centre. For this case should be 8
Move to Product tab and verify:
- You have three lines: A BOM:(P-), B BOM(P-), A Final Goods(P+)
- The ones for P- must have filled the attribute set value
- The quantity for the three must be 200 as a result of "Done quantity" x "Quantity" (I/O Products tab)
For the A Final Goods product fill the attribute set value
Move back to Work effort tab
Click on button "Validate Work effort"

設定ミスのためエラー

Create Work requirement

2009-05-20T11:12:00.004+09:00

6. Create Work requirement

Short description: Create a work requirement to use in the Work effort window

Steps:
- Login as userA
- Go to Production management->Transactions->Work requirement->Header
- Click New and fill:
  - Select Production Final goods A as process plan
  - Quantity=10
  - Starting Date= The current day
  - Ending Date= The following date
- Save and click on button "Process Work Requirement"
- Move to Operation tab and verify:
  - The quantity field has the same value as in Header tab
  - The fields "Cost Center Use Time", "Empty Cells are Zero", "Outsourced" and "Global Use" have the same value as in Operation tab (Process plan window)
- Move to Product tab and verify:
  - We have three lines: A BOM(P-), B BOM(P-) and A final goods(P+)
  - Each line quantity=100
- Move back to Operation tab and click New again
- Select the sequence "Assamble" and verify:
  - The quantity field has the same value as in Header tab
  - The fields "Cost Center Use Time", "Empty Cells are Zero", "Outsourced" and "Global Use" have the same value as in Operation tab (Process plan window)
- Don´t save

Additional data:

The field Quantity on Header tab indicates the number of times that we want to process the process plan

Create a process plan

2009-05-20T10:33:00.006+09:00

5. Create a process plan

Short description: Create a process plan to use in Work Requirement

Preconditions:
- Products Final Goods A, A BOM and B BOM must have the production check marked.

Steps:
- Login as userA
- Go to Production management->Transactions->Process plan
- Click New and fill:
  - Search Key=FGA
  - Name=Production Final Goods A
  - Process unit=FGA unit
  - Conversion rate=100
  - "Insert phase" marked
- Move to Version tab
- Click New and fill the dates for the whole year
- Move to Operation. Click New and fill:
  - Search key=assa
  - Name=Assamble
  - Process=Assamble
  - Cost Center Use Time=10
- Move to I/O Product
- Click New and select the product A Final goods as P+
- Click New twice and select the product A BOM and B BOM as P-
- Quantities for each three 100

I/O Product の LOV に表示されない場合、Production をチェックを確認。

Additional data:
- Process plan tab
  - Insert phases:Indicates if the work requirement phases will be generated automatically
- Operation tab
  - Cost Center Use Time:Time used to do the operation once
  - Empty cells are Zero:When creating a production run (Work effort window), by running the "generating standards" process required input and output product quantities are automatically filled in as specified in the work requirement phases (Work requirement window)

Create a Process/Activit

2009-05-20T10:30:00.003+09:00

4. Create a Process/Activity

Steps:
- Login as userA
- Go to Production management->Setup->Activity
- Click New and fill the mandatory fields:
  - Name=Assamble
- Select the cost centre

Additional data: A process/activity is mandatory in order to create a process plan

Create Cost centre

2009-05-20T10:19:00.004+09:00

3. Create Cost centre

Short description:

Create a cost centre to use for calculate costs based on the work effort

Steps:
- Login as userA
- Go to Production management->Setup->Cost Center
- Click New and fill the mandatory fields
- Mark the check "Calculated"
- Not mark "By default"

Move to Version tab, click New and fill

"Valid from date" with the 1st of January of the current year
Cost=100
And select "per Produced Units" for Cost UOM

Additional data

Tab Cost centre
- If "Calculated" is marked but not "By default", when process the Work effort, OB will calculate the hours used for the sequence based on the initial time and final time
- If "By default" is marked, OB will calculate the hours used for the sequence based on the process plan
- If any is marked, OB will do nothing
Tab Version
- Per hour: Based on the cost centre unit that is in the tab Operation (Window process plan)
- Per Kilogram: Based on the weight of product window. Produced units x Weight
- Per percentage: This is only for Indirect cost purposes
- Per Produced Units: Based on produced units

Installation and setup of Eclipse IDE

2009-05-19T15:43:00.011+09:00

http://wiki.openbravo.com/wiki/Installation_and_setup_of_Eclipse_IDE

2.40 でが Buildの構成が以下のように設定されているが、

http://wiki.openbravo.com/wiki/Installation_and_setup_of_Eclipse_IDE#Compiling_and_building_Openbravo_ERP

2.50 以降では以下のファイルが自動作成されると書かれているが...

org.eclipse.wst.common.component 　

http://wiki.openbravo.com/wiki/ERP/2.50/ReleaseNotes

http://wiki.openbravo.com/wiki/Mercurial_Manual_for_Openbravo_Developers

http://wiki.openbravo.com/wiki/Projects/Modularity/Reference_Data

http://wiki.openbravo.com/wiki/ERP/2.50/ModularityVideos

ant create.database -Dapply.on.create=true

c_doctype,c_uom,c_currency,ad_impformat,ad_impformat_row,c_region,c_country

select count(*) from c_doctype ;

select count(*) from c_uom;

select count(*) from c_currency;

select count(*) from ad_impformat;

select count(*) from ad_impformat_row;

select count(*) from c_region;

select count(*) from c_country;

Create BOM production

2009-05-18T14:10:00.014+09:00

2. Create BOM production

Short description: Create a bill of materials production

Steps:
- Login as userA
- Go to Warehouse management->Transactions->Bill of materials production
- Click New. Fill Name = BOM A. Save

Move to Production Plan and click NEW
Select Product "A BOM" and production quantity 100. Save

Move back to BOM Production tab
Click on Button "Create/Post Production"

Go to I/O products and verify:

One line for product A BOM. Quantity = 100
One line for product B Raw material. Quantity = -100
One line for product C Raw material. Quantity = -100

Select A BOM product
Click on Attribute Set Value icon and fill the attributes. Save

不具合のため

Fixes bug 8310 Valued stock report does not work in 240

Stock Report は表示できなかったが、SVN より 2.40 をダウンロードし、再Buildした後、このレポートのパッチを適用したところ　Date 指定の際に 19-05-2009 形式で表示されていた日付も修正された。

Openbravo.properties　には
bbdd.sessionConfig=ALTER SESSION SET NLS_DATE_FORMAT='YYYY/MM/DD' NLS_NUMERIC_CHARACTERS='.,

Windows の Registory には NLS_LANG=Japanese_Jpana.JA16SJISTILDE
select sysdate from dual では　09-05-19

Edit a product BOM

2009-05-18T14:05:00.003+09:00

1. Edit a product BOM

Short description: Add products to a BOM's product

Steps:
- Login as userA
- Go to Master Data Management->Product
- Select product BOM A
- Move to Bill of materials Tab
- Click New and fill:
  - BOM Type = Part/BOM
  - BOM Product = B Raw material
  - BOM quantity = 1
- Save and new and fill
  - BOM Type = Part/BOM
  - BOM Product = C Raw material
  - BOM quantity = 1
- Move back to Product Tab
- Click on Verify BOM button

"Bill of Materials" がチェックされていないと下記の画面になにも表示されない。

2.7 Production management

2009-05-18T14:00:00.000+09:00

2.7 Production management

1. Edit a product BOM

2. Create BOM production

3. Create Cost centre

4. Create a Process/Activity

5. Create a process plan

6. Create Work requirement

7. Create Work effort

Create goods shipment

2009-05-18T13:45:00.006+09:00

2. Create goods shipment

Short description:Create a goods shipment from a sales order

Steps:
- Login as userA
- Go to Sales management->Transactions->Create shipments from orders
- Select the sales order and click process

ERROR=ORA-20000 : inline 10productWithoutAttributeSet@

成功（データ　依存?)

Process completed successfully
Order No. 50008 -> Shipment No. 500000- COMPLETE SHIPMENT CREATED;

Issues to verify:
- The sales order must be disappear
- Go to Goods shipment and see that it is created
- Move to Lines tab and verify the link "Sales Order Line" is related to the correct one

Create Standard Sales Order

2009-05-18T13:44:00.004+09:00

1. Create Standard Sales Order

Short description:Create an order to be used when creates a goods shipment

Steps:
- Login as userA
- Go to Sales management->Transactions->Sales Order
- Click New and select Transaction Document: Standard Order
- Select business partner.Two possibilities:
- A.- Click on the bp icon and verify:
  - When you click the bp icon a pop-up window must show up and the radio button 'customer' must be checked. Please select CUSTOMER A
- B.- Or write in the bp box CUSA and verify:
  - A pop-up window doesn't show up and the bp box is filled with the name CUSTOMER A
- For both cases verify:
  - Invoice from: "Pamplona, Street Customer center nº1"
  - The combo box User/Contact must have the value: Alfred
  - Price list: CUSTOMER A
  - Form of payment: Money Order
  - Payment terms: 30 days, 5
  - Sales representative: SALESMAN A
- Move to tab Lines and click New. There are two possibilities:
- A.- Click on the product icon and verify:
  - When you click the product icon a pop-up window must show up.
  - The price list combo must be filled with the value CUSTOMER A
  - When click Search only 3 products must appear: A Final goods, B Final goods, C Final goods. Select A Final goods
- B.- Or write in the product box FGA and verify:
  - A pop-up window doesn't show up and the product box is filled with the name A Final goods
- For both cases verify:
  - UOM:Unit
  - Unit price:2
  - List price:2
  - Tax:VAT(3)+CHARGE(0.5)
- Fill in Ordered quantity= 1
- Move to header and complete. Verify:
  - Summed Line Amount= 2
  - Grand Total Amount= 2.07

Issues to verify:The tax VAT(3)+CHARGE(0.5) has to split into VAT 3% and Charge 0.5%. To verify this point, move to Tax tab

2.6 Sales Management

2009-05-18T13:42:00.004+09:00

2.6 Sales Management

1. Create Standard Sales Order

2. Create goods shipment

3. Create Sales invoice

4. Accounting Sales Invoice

5. Create Settlement

6. Create Remittance

7. Create Bank Statement

8. Generate invoices process

2.5 Procurement management

2009-05-18T13:39:00.001+09:00

2.5 Procurement management

Skip

2.4 Administration financial data

2009-05-18T13:38:00.000+09:00

2.4 Administration financial data

Skip

2.3 Administration accounting data

2009-05-18T13:36:00.001+09:00

2.3 Administration accounting data

1. Create fiscal calendar

2. Editing Document sequence

Import account

2009-05-18T13:03:00.009+09:00

20. Import account

Short description: Test the Accounting import works correctly

Steps:
- Login as userA
- Go to Master data management->Import data->Import File loader
- Select the chart of accounts. This chart of accounts must be the same as selected for theinitial client set up otherwise the process import accounts wouldn't overwrite the default values.
- Select the format file= Accounting-Accounts
- Mark Header first line
- Click Process

Please verify the new imported accounts are in this temporary window

- Go to the database manager software and execute the next sentences:
  - update c_elementvalue set value = 'xx' || value where ad_client_id = v_client;
  - The parameter v_client is the ID of the client that you have already created
  - delete from c_elementvalue_operand;
  - Commit;
- Go into any of the records that are in the window Import Account and click on button "Import accounts" and:
  - Update default marked
  - Delete imported marked
  - Create new combination not marked
- Click OK
- Go again to the database manager software, and execute the next statement:
  - delete from c_elementvalue where value like 'xx%' and ad_client_id =v_client;
  - commit;

Issues to verify:

If you cannot execute correctly the last statement, means the import accounts has failed

Additional data:

Please see Chart of accounts for more information

select name, ad_client_id from ad_client ;
NAME                      AD_CLIENT_ID
------------------------- ------------
System                               0
SampleClient                   1000000

update c_elementvalue set value = 'xx' || value where ad_client_id = 1000000 ;

1356行が更新されました。

delete from c_elementvalue_operand;

0行が削除されました。  commit ;

SQL> select count(*) from c_elementvalue;

COUNT(*)
----------
    2712

SQL> delete from c_elementvalue where value like 'xx%' and ad_client_id = 1000000 ;

1356行が削除されました。

SQL> commit ;

Create Physical inventory

2009-05-17T19:38:00.005+09:00

19. Create Physical inventory

Short description: Create inventory in order to test other features without needed of purchasing or producing anything

Steps:
- Login as userA
- Go to Warehouse management-->Transactions-->Physical inventory
- Click New and fill the mandatory fields and save
- Click button "Create Inventory Count List"
  - Select a storage bin=Standard
  - Inventory Quantity=0
- Click Ok
- Move to lines and for each line write in the "Quantity count" box 10000 and fill the attribute set value
- Move back to the header and process (Process inventory count)

Issues to verify:Go to Warehouse management-->Analysis tools-->Stock report and click HTML format. Products should be shown

在庫数は入力したが　Stock report は表示されない。

Edit Business partner

2009-05-17T19:11:00.001+09:00

18. Edit Business partner

Note: If you don't want to edit all the business partner using the application please use this Oracle script or this PostgreSQL script

Short description:Test the way of editing a business partner. Example for "CUSTOMER A"

Preconditions: set some sales representatives.
- Login as userA
- Go to Master Data management-->Business partner
- Click on search button from the toolbar
- Write "SALESMAN A" in the name box and click OK
- Move to Employee tab and edit the values:
  - Mark Sales Representative and save.
- Do the same for SALESMAN B.

Steps

Login as userA
Go to Master Data management-->Business partner
Click on search button from the toolbar
Write "CUSTOMER A" in the name box and click OK
Move to Customer tab and edit the values:
- Invoice Terms: Customer schedule After Delivery
- Invoice Schedule: Schedule Customer A
- Price list: Customer A
- Form of Payment: Money Order
- Payment Terms: 30 days, 5
- Sales Representative: Salesman A

Edit products

2009-05-17T18:49:00.003+09:00

17. Edit products

Note: If you don't want to edit all the products using the application please use this Oracle script or this PostgreSQL script

Short description:Test the way of editing a product. Example for product "Raw material A"

Steps
- Login as userA
- Go to Master Data Management->Product
- Click on search button from the toolbar
- Write "RMA" in the "Search Key" box and press OK
- Edit the values:
  - Tax Category=VAT 10%
  - Mark Purchase
  - Not mark Sale
  - Attribute set=Serial number
- Save

Next : Create BOM production

Create Invoice Schedule

2009-05-17T18:45:00.004+09:00

16. Create Invoice Schedule

Short description: Create an invoice schedule to use in Generate invoices test case

Steps:
- Login as userA
- Go to Master Data Management->Business Partner Setup->Invoice schedule
- Click New and fill:
  - Name: Schedule customer A
  - Invoice Frequency: Monthly
  - Day of the Month: 1
  - Invoice Cut-Off Day: 31

Create Payment term

2009-05-17T18:30:00.004+09:00

15. Create Payment term

Note: If you don't want to create all the payment terms using the application please use this Oracle script or this PostgreSQL

Short description:Create payment terms to add to business partner. Do as example "30 days, 5"

Steps:
- Login as userA
- Go to Master Data Management->Business partner setup->Payment Term
- Click New fill:
  - Value=30d/5
  - Name=30 days, 5
  - Mark "Fixed Due Date"
  - Maturity Date 1=5
  - Offset Month Due=1

Additional data: Doing the example for "30 days, 5", remember to remove from the script the code related to this issue.

DECLARE
v_paymentterm_id NUMBER(10);
v_client_id NUMBER(10);
BEGIN
SELECT MAX(AD_CLIENT_ID) INTO v_client_id FROM AD_CLIENT;

SELECT COALESCE(MAX(C_PAYMENTTERM_ID),999999) +1 INTO v_paymentterm_id FROM C_PAYMENTTERM;

INSERT INTO C_PAYMENTTERM
(C_PAYMENTTERM_ID, AD_CLIENT_ID, AD_ORG_ID, ISACTIVE, CREATED, CREATEDBY, UPDATED, UPDATEDBY,
 NAME, ISDUEFIXED, NETDAYS, FIXMONTHOFFSET, ISNEXTBUSINESSDAY, ISDEFAULT, VALUE, ISVALID)
VALUES
 (v_paymentterm_id, v_client_id, 0, 'Y', SYSDATE, 100, SYSDATE, 100, '90 DAYS', 'N', 0, 3, 'N', 'N', '90d', 'N');
ad_update_sequence();
commit;
END;

Create Pricelist

2009-05-17T17:16:00.007+09:00

14. Create Pricelist

Note: If you don't want to create all the pricelist using the application please use this Oracle script or this PostgreSQL script

Short description: Create pricelist for all the products. Do as example SALES pricelist
Steps
- Login as userA
- Go to Master Data management->Pricing->Pricelist
- Click New and fill Name=SALES mark Sales price list, currency=EUR
- Move to tab Price list version
- Click New and fill Name=Sales, Price List Adjustment= Standard and valid from date=01-01-2000
- Move to tab Product price
- Click new and select Product "A Final goods". Uncheck the flag "Stocked" in order to find the product
- Fill for each price (List price, Standard price, price limit) fill 2. Do the same for "B Final goods", "C Final goods"

Additional data: Doing the example for "SALES", remember to remove from the script the code related to this issue.

Oracle Script を実行する際には

ALTER SESSION SET NLS_DATE_FORMAT='DD/MM/YYYY' ;

が必要。

Create Attribute set

2009-05-17T17:01:00.005+09:00

13. Create Attribute set

Short description: Create sets of attributes for the Products.

Steps
- Login as userA
- Go to Master Data Management->Product Setup->Attribute Set
- Click New, fill name=Serial number
- Mark Serial No.
- Run this Oracle script or this PostgreSQL script to create the rest of sets


DECLARE
v_attributeset_id NUMBER(10);
v_client_id NUMBER(10);

BEGIN

SELECT MAX(AD_CLIENT_ID) INTO v_client_id FROM AD_CLIENT;
SELECT COALESCE(MAX(M_ATTRIBUTESET_ID),999999)+1 INTO v_attributeset_id FROM  M_ATTRIBUTESET;

INSERT INTO M_ATTRIBUTESET (M_ATTRIBUTESET_ID, AD_CLIENT_ID, AD_ORG_ID, ISACTIVE, CREATED,CREATEDBY, UPDATED, UPDATEDBY, NAME, ISLOT, ISGUARANTEEDATE, ISSERNO)
VALUES(v_attributeset_id, v_client_id, 0, 'Y', sysdate, 100,sysdate,100,'Lots','Y','Y','N');
   
AD_UPDATE_SEQUENCE;
COMMIT;
END;

Import Taxes

2009-05-17T15:24:00.003+09:00

12. Import Taxes

Short description:Import from the temporary tax table to the final one

Steps:
- Login as userA
- Go to Master Data Management->Import Data->Import Tax
- Entry in edition mode and click on button Import Tax and then OK

Issues to verify:Take a look in the field Import Error Message to see if there are any errors and Go to Financial management->Accounting->Setup->Tax rate and verify that all the taxes are there

手動で画面よりインターフェイステーブルに VAT 3% 　だけ登録し、インターフェイス処理を実行。

Tax Rate の登録を確認

Import products / Business partner

2009-05-17T14:25:00.008+09:00

10. Import products
11. Import Business partners

Short description:Import from the temporary product table to the final one

Steps:
- Login as userA
- Go to Master Data Management->Import Data->Import Products
- Entry in edition mode and click on button Import Product and then OK

Issues to verify:Take a look in the field Import Error Message to see if there are any errors and Go to Master Data Management->Product and verify that all the products are there

この画面で　”Imoprot Products" をクリックすることで一時テーブルから最終の位置に登録される。

　Product inserted: 9 　　と表示されている。

この処理により Business Partner の場合、　I_BPartner インターフェイステーブルから C_BPartner テーブルをはじめとした、いくつかのテーブルへの処理が実行されている。

Create Product/Business Partner category

2009-05-17T14:08:00.006+09:00

8. Create Product category
9. Create BusinessPartner Category

Short description:Create a product category to import the data from the temporal tables to the final tables.

Steps:
- Login as userA
- Go to Master data management->Product Setup->Product Category
- Click New and fill value=RM; Name=Raw materials and save
- Create Product categories for BOM (Bill of Materials) and FG (Finished Goods) with this Oracle script or this postgreSQL script

Additional data: Please create these categories with the values RM, BOM and FG respectively in order to import the products that belong to that category.

Raw Material 以外は　Script が用意されているので、これを実行。


DECLARE
v_client_id number(10);
v_product_category_id number(10);

BEGIN
SELECT MAX(AD_CLIENT_ID) INTO v_client_id FROM AD_CLIENT;
SELECT MAX(M_PRODUCT_CATEGORY_ID)+1 INTO v_product_category_id FROM  M_PRODUCT_CATEGORY;
INSERT INTO M_PRODUCT_CATEGORY (M_PRODUCT_CATEGORY_ID, AD_CLIENT_ID, AD_ORG_ID,
ISACTIVE, CREATED, CREATEDBY, UPDATED, UPDATEDBY, VALUE, NAME, PLANNEDMARGIN)
VALUES (v_product_category_id, v_client_id, 0 , 'Y', sysdate , 100, sysdate, 100, 'BOM', 'BOMs', 0);
v_product_category_id:=v_product_category_id + 1;
INSERT INTO M_PRODUCT_CATEGORY (M_PRODUCT_CATEGORY_ID, AD_CLIENT_ID, AD_ORG_ID,
ISACTIVE, CREATED, CREATEDBY, UPDATED, UPDATEDBY, VALUE, NAME, PLANNEDMARGIN)
VALUES (v_product_category_id, v_client_id, 0 , 'Y', sysdate , 100, sysdate, 100, 'FG', 'Final goods',0);
AD_UPDATE_SEQUENCE();
commit;
end;

Import file loader

2009-05-17T13:18:00.010+09:00

7.Import file loader

Short description: Test the import data process for Products, Business partner and taxes.

Steps:
- Login as userA
- Go to Master Data Management->Import Data->Import File Loader
- Select the file I_Products.txt and the format for the products
- Click OK. This is only to verify that the file is well format
- Select again the file and the format. Click Process
- Do the same for Business partners and taxes

Issues to verify:
- Go to Master Data Management->Import Data
- Verify that the products are in the Import Product window
- Verify that the Business partners are in the Import Business partner window
- Verify that the taxes are in the Import tax window

Additional data: To import use the .txt that are in Business partner, Products and taxes

Product データロード用の書式が手入力したものなのでまずはエラーとなることを予想していたが、１度目で Load 成功。

"Process" をクリックすることで、実際の Loading が実行される。

Taxes が "Process" でエラーとなる。　( 2.40 )

ProcessRunError と表示されるだけで、エラーの原因が表示されない

試しに　"Format file: Taxes: Complete" を選択すると書式チェックの段階でフリーズしてしまった。

６行程度のデータなので手動で入力してもこの部分はたいした工数にはならない。

Skip

このエラーの原因を検索していて以下のガイドを見つけた

OPENBRAVO CHART OF ACCOUNTS TESTING GUIDE
http://www.scribd.com/doc/2923732/OPENBRAVO-CHART-OF-ACCOUNTS-TESTING-GUIDE

Create Import Loader Format

2009-05-16T23:24:00.009+09:00

Interfaceテーブルはいくか用意されているが残念ながら BOM については用意されていない。

Interface テーブルに対して import するデータの書式はカスタム定義可能であるため、この項にて動作確認。

6.Create Import Loader Format

Short Description: Create the import format loader for Business partner, Products and taxes.

Steps
- Login as userA
- Go to Master Data Management->Import Data->Import Loader Format
- Click New and fill:
  - Name "Product"
  - Table "I_Product"
  - Format "Comma Separated"
- Move to Field Format and create new records:

Business partner, Taxes 用には SQLが用意されている。

C:\OpenbravoERP24>sqlplus erp/xxxx @6_format_loader.sql

Create role

2009-05-16T23:02:00.007+09:00

5.Create role

Short description: Create a role to relate to the user "userA"

Steps
- Login with userA
- Go to General setup->Security->Role
- Click New
- Fill Name "Sales"
- Select "Client+Organization"
- Mark the check Manual and save
- Click Grant Access: Select "Sales management" and Access "All"
- Go to Org Access and click New. Select org *
- Click New and select org Pamplona.
- Go to User Assignment and select "userA"

Issues to verify: Login with "userA" and click on "User info". Select the Role (Sales). Verify that you can only access Sales management module windows.

作成した Sales ロールでログインすると Sales 用のメニューしか表示されなくなったが、選択した先の Window の表示でエラーになるのはまだ権限設定を行なっていないからだろうか。

Create User

2009-05-16T22:44:00.009+09:00

4.Create user

Short Description: Create a user to use for the next test cases

Steps
- Login with user created by the initial client setup, SampleClientAdmin/SampleClientAdmin
- Go to General setup->Security->User
- Click New and fill the mandatory field:
  - Organization: *
  - First Name "userA"
  - Name "userA"
  - Username "userA"
- Save
- Fill the password and save. Password "userA"
- Move to User Roles and click New and select the SampleClientAdmin role.

Issues to verify: Verify that you can login with the new user and you have access to all windows

~~Openbravo ユーザーでログインして、一旦、自分の Role を　SampleClientUser に変更して~~

~~Create User しないと、この作成したユーザーの Role に　SampleClientUser 　をアサインできない。~~

Client作成時に自動作成される　User/Password = SampleClientAdmin/SampleClientAdmin

にてログインして、 userA を作成する。

M_Pricelist.C_Currency_ID に Null

2009-05-16T21:47:00.012+09:00

1.Initial client setup

issue8246 として登録されて、fix されているが、Patch がダウンロードできないようでもあり、

alter table m_pricelist modify ( c_currency_id number(10) null ) ;

SQL> desc m_pricelist ;
名前               NULL?    型
------------------ -------- -------------
M_PRICELIST_ID     NOT NULL NUMBER(10)
AD_CLIENT_ID       NOT NULL NUMBER(10)
AD_ORG_ID          NOT NULL NUMBER(10)
ISACTIVE           NOT NULL CHAR(1)
CREATED            NOT NULL DATE
CREATEDBY          NOT NULL NUMBER(10)
UPDATED            NOT NULL DATE
UPDATEDBY          NOT NULL NUMBER(10)
NAME               NOT NULL NVARCHAR2(60)
DESCRIPTION                 NVARCHAR2(255)
BASEPRICELIST_ID            NUMBER(10)
ISTAXINCLUDED      NOT NULL CHAR(1)
ISSOPRICELIST      NOT NULL CHAR(1)
ISDEFAULT          NOT NULL CHAR(1)
C_CURRENCY_ID               NUMBER(10)
ENFORCEPRICELIMIT  NOT NULL CHAR(1)

2.Delete client

しかし　ora-1400 が発生しているにもかかわらず ad_client テーブルにはデータが insert されてしまっているため、 "Delete Client" で削除しなくてはならない。

Initial client setup

2009-05-16T21:44:00.009+09:00

Initial client setup

Short Description: Test the Initial Client Setup process

Additional data: Use the System Administrator Role for this test

Steps
- Login as Openbravo/openbravo
- Click on icon "user info" and select the role "System Administrator"
- Go General Setup -> Client-> Initial client setup
- Fill the data and chart of accounts according Client sample data
- Click OK

Issues to verify: Verify that the output log is correct

ここで指定した、SampleClientAdmin ユーザーが自動的に作成される。

このユーザーでログイン(　Password = SampelClientAdmin ) し、

以後、ユーザー userA を作成する。

Reference data などインストールに問題がある場合など、この時点でエラーとなる。

2.2 Administration master data

2009-05-16T21:43:00.000+09:00

1.Initial client setup

2.Delete client

3.Import/Export Translation

Create Table / Custom Table Test

2009-05-16T18:22:00.007+09:00

Acceptance Testing
2. Test cases
2.1 Application Dictionary

がカスタムテーブルとその画面のテストケースであることがわかったためテーブルは作成したものの作業は中断し、 Skip する。

Acceptance_Testing 用 Script1.sql

http://wiki.openbravo.com/wiki/Acceptance_Testing

Execute this Oracle script


/********C_ROOM TABLE**********/


CREATE TABLE C_ROOM
(
C_ROOM_ID          NUMBER(10)    NOT NULL,
AD_CLIENT_ID       NUMBER(10)    NOT NULL,
AD_ORG_ID          NUMBER(10)    NOT NULL,
ISACTIVE           CHAR(1 BYTE)  DEFAULT 'Y'       NOT NULL,
CREATED            DATE          DEFAULT SYSDATE   NOT NULL,
CREATEDBY          NUMBER(10)    NOT NULL,
UPDATED            DATE          DEFAULT SYSDATE  NOT NULL,
UPDATEDBY          NUMBER(10)    NOT NULL,
NAME  NVARCHAR2(60) NOT NULL,
DESCRIPTION        NVARCHAR2(255),
ROOMTYPE           CHAR(2 BYTE),
LOCATION           NVARCHAR2(255)
)
TABLESPACE USERS
PCTUSED    0
PCTFREE    10
INITRANS   1
MAXTRANS   255
STORAGE    (
       INITIAL          64K
       MINEXTENTS       1
       MAXEXTENTS       2147483645
       PCTINCREASE      0
       BUFFER_POOL      DEFAULT
      )
LOGGING
NOCOMPRESS
NOCACHE
NOPARALLEL
MONITORING;


CREATE UNIQUE INDEX C_ROOM_KEY ON C_ROOM
(C_ROOM_ID)
LOGGING
TABLESPACE USERS
PCTFREE    10
INITRANS   2
MAXTRANS   255
STORAGE    (
       INITIAL          64K
       MINEXTENTS       1
       MAXEXTENTS       2147483645
       PCTINCREASE      0
       BUFFER_POOL      DEFAULT
      )
NOPARALLEL;



ALTER TABLE C_ROOM ADD (
CONSTRAINT C_ROOM_ISACTIVE_CHECK
CHECK (ISACTIVE IN ('Y', 'N')));

ALTER TABLE C_ROOM ADD (
CONSTRAINT C_ROOM_KEY
PRIMARY KEY
(C_ROOM_ID)
USING INDEX
TABLESPACE USERS
PCTFREE    10
INITRANS   2
MAXTRANS   255
STORAGE    (
INITIAL          64K
MINEXTENTS       1
MAXEXTENTS       2147483645
PCTINCREASE      0
));


ALTER TABLE C_ROOM ADD (
CONSTRAINT C_ROOM_ORG
FOREIGN KEY (AD_ORG_ID)
REFERENCES AD_ORG (AD_ORG_ID));

ALTER TABLE C_ROOM ADD (
CONSTRAINT ADCLIENT_C_ROOM
FOREIGN KEY (AD_CLIENT_ID)
REFERENCES AD_CLIENT (AD_CLIENT_ID));

/***************C_ROOMSCHEDULE*********/
CREATE TABLE C_ROOMSCHEDULE
(
C_ROOMSCHEDULE_ID  NUMBER(10)    NOT NULL,
AD_CLIENT_ID       NUMBER(10)    NOT NULL,
AD_ORG_ID          NUMBER(10)    NOT NULL,
ISACTIVE           CHAR(1 BYTE)  DEFAULT 'Y'        NOT NULL,
CREATED            DATE          DEFAULT SYSDATE   NOT NULL,
CREATEDBY          NUMBER(10)    NOT NULL,
UPDATED            DATE          DEFAULT SYSDATE   NOT NULL,
UPDATEDBY          NUMBER(10)    NOT NULL,
C_ROOM_ID          NUMBER(10)    NOT NULL,
TOPIC NVARCHAR2(255),
RESERVATIONDATE    DATE          NOT NULL,
STARTTIME          DATE          NOT NULL,
ENDTIME            DATE          NOT NULL,
AD_USER_ID         NUMBER(10),
FREQUENCY          CHAR(2 BYTE)
)
TABLESPACE USERS
PCTUSED    0
PCTFREE    10
INITRANS   1
MAXTRANS   255
STORAGE    (
       INITIAL          64K
       MINEXTENTS       1
       MAXEXTENTS       2147483645
       PCTINCREASE      0
       BUFFER_POOL      DEFAULT
      )
LOGGING
NOCOMPRESS
NOCACHE
NOPARALLEL
MONITORING;


CREATE UNIQUE INDEX C_ROOMSCHEDULE_KEY ON C_ROOMSCHEDULE
(C_ROOMSCHEDULE_ID)
LOGGING
TABLESPACE USERS
PCTFREE    10
INITRANS   2
MAXTRANS   255
STORAGE    (
       INITIAL          64K
       MINEXTENTS       1
       MAXEXTENTS       2147483645
       PCTINCREASE      0
       BUFFER_POOL      DEFAULT
      )
NOPARALLEL;




ALTER TABLE C_ROOMSCHEDULE ADD (
CONSTRAINT C_ROOMSCHEDULE_ISACTIVE_CHECK
CHECK (ISACTIVE IN ('Y', 'N')));

ALTER TABLE C_ROOMSCHEDULE ADD (
CONSTRAINT C_ROOMSCHEDULE_KEY
PRIMARY KEY
(C_ROOMSCHEDULE_ID)
USING INDEX
TABLESPACE USERS
PCTFREE    10
INITRANS   2
MAXTRANS   255
STORAGE    (
INITIAL          64K
MINEXTENTS       1
MAXEXTENTS       2147483645
PCTINCREASE      0
));


ALTER TABLE C_ROOMSCHEDULE ADD (
CONSTRAINT C_ROOMSCHEDULE_ORG
FOREIGN KEY (AD_ORG_ID)
REFERENCES AD_ORG (AD_ORG_ID));

ALTER TABLE C_ROOMSCHEDULE ADD (
CONSTRAINT ADCLIENT_C_ROOMSCHEDULE
FOREIGN KEY (AD_CLIENT_ID)
REFERENCES AD_CLIENT (AD_CLIENT_ID));

ALTER TABLE C_ROOMSCHEDULE ADD (
CONSTRAINT C_ROOMSCHEDULE_USER
FOREIGN KEY (AD_USER_ID)
REFERENCES AD_USER (AD_USER_ID));

ALTER TABLE C_ROOMSCHEDULE ADD (
CONSTRAINT C_ROOMSCHEDULE_ROOM
FOREIGN KEY (C_ROOM_ID)
REFERENCES C_ROOM (C_ROOM_ID));


/*****************C_ROOMATTEND***********/

CREATE TABLE C_ROOMATTEND
(
C_ROOMATTEND_ID           NUMBER(10)          NOT NULL,
AD_CLIENT_ID NUMBER(10)          NOT NULL,
AD_ORG_ID    NUMBER(10)          NOT NULL,
ISACTIVE     CHAR(1 BYTE)        DEFAULT 'Y'        NOT NULL,
CREATED      DATE   DEFAULT SYSDATE  NOT NULL,
CREATEDBY    NUMBER(10)          NOT NULL,
UPDATED      DATE   DEFAULT SYSDATE   NOT NULL,
UPDATEDBY    NUMBER(10)          NOT NULL,
C_ROOMSCHEDULE_ID            NUMBER(10)  NOT NULL,
MEETINGROLE  NVARCHAR2(255),
TYPEATTENDER CHAR(2 BYTE),
DEPARTMENT   CHAR(2 BYTE),
AD_USER_ID   NUMBER(10),
C_BPARTNER_IDNUMBER(10)
)
TABLESPACE USERS
PCTUSED    0
PCTFREE    10
INITRANS   1
MAXTRANS   255
STORAGE    (
       INITIAL          64K
       MINEXTENTS       1
       MAXEXTENTS       2147483645
       PCTINCREASE      0
       BUFFER_POOL      DEFAULT
      )
LOGGING
NOCOMPRESS
NOCACHE
NOPARALLEL
MONITORING;


CREATE UNIQUE INDEX C_ROOMATTEND_KEY ON C_ROOMATTEND
(C_ROOMATTEND_ID)
LOGGING
TABLESPACE USERS
PCTFREE    10
INITRANS   2
MAXTRANS   255
STORAGE    (
       INITIAL          64K
       MINEXTENTS       1
       MAXEXTENTS       2147483645
       PCTINCREASE      0
       BUFFER_POOL      DEFAULT
      )
NOPARALLEL;


ALTER TABLE C_ROOMATTEND ADD (
CONSTRAINT C_ROOMATTEND_ISACTIVE_CHECK
CHECK (ISACTIVE IN ('Y', 'N')));

ALTER TABLE C_ROOMATTEND ADD (
CONSTRAINT C_ROOMATTEND_KEY
PRIMARY KEY
(C_ROOMATTEND_ID)
USING INDEX
TABLESPACE USERS
PCTFREE    10
INITRANS   2
MAXTRANS   255
STORAGE    (
INITIAL          64K
MINEXTENTS       1
MAXEXTENTS       2147483645
PCTINCREASE      0
));


ALTER TABLE C_ROOMATTEND ADD (
CONSTRAINT ADCLIENT_C_ROOMATTEND
FOREIGN KEY (AD_CLIENT_ID)
REFERENCES AD_CLIENT (AD_CLIENT_ID));

ALTER TABLE C_ROOMATTEND ADD (
CONSTRAINT AUSER_C_ROOMATTEND
FOREIGN KEY (AD_USER_ID)
REFERENCES AD_USER (AD_USER_ID));

ALTER TABLE C_ROOMATTEND ADD (
CONSTRAINT ADORG_C_ROOMATTEND
FOREIGN KEY (AD_ORG_ID)
REFERENCES AD_ORG (AD_ORG_ID));

ALTER TABLE C_ROOMATTEND ADD (
CONSTRAINT BPARTNER_C_ROOMATTEND
FOREIGN KEY (C_BPARTNER_ID)
REFERENCES C_BPARTNER (C_BPARTNER_ID));

2.1 Application Dictionary

2009-05-16T18:21:00.005+09:00

この章はカスタマイズテーブル(テーブルを追加する場合）の機能に関するものであるため、先に実施する必要はない。

2.1 Application Dictionary

1.Create tables

2.Create functions

3.Create references

4.Add tables to dictionary

5.Create window

ORA-600　[evapls1]

2009-05-16T15:44:00.012+09:00

Oracle XE が推奨されない理由はすぐにわかることになる。

C:\oraclexe\app\oracle\admin\XE\bdump\alert.log

Sat May 16 15:25:28 2009
Errors in file c:\oraclexe\app\oracle\admin\xe\udump\xe_ora_3492.trc:
ORA-00600: 内部エラー・コード、引数: [evapls1],[],[],[],[],[],[],[]

AppsOpenbravo/config/Openbravo.properties　にて alter session している部分に追加することもできそうであるが

bbdd.sessionConfig=ALTER SESSION SET NLS_DATE_FORMAT='YYYY/MM/DD' NLS_NUMERIC_CHARACTERS='.,' "_optimizer_filter_pred_pullup"=false

このパラメータについては alter system により再起動後も有効
(use cost-based flter predicate pull up transformation)


C:\Users\Administrator>sqlplus

SQL*Plus: Release 10.2.0.1.0 - Production on 土 5月 16 15:27:03 2009
Copyright (c) 1982, 2005, Oracle.  All rights reserved.

ユーザー名を入力してください: sys
パスワードを入力してください:
ERROR:
ORA-28009: connection as SYS should be as SYSDBA or SYSOPER

ユーザー名を入力してください: sys as sysdba
パスワードを入力してください:

Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
に接続されました。
SQL> alter system  set "_optimizer_filter_pred_pullup"=false;

システムが変更されました。

shutdown immediate ; startup ;

SQL> set lines 120

SQL> show parameters _opt

NAME                                 TYPE                   VALUE
------------------------------------ ---------------------- --------
_optimizer_filter_pred_pullup        boolean                FALSE
filesystemio_options                 string
object_cache_optimal_size            integer                102400
plsql_optimize_level                 integer                2

ReInstall - Clean up demodata

2009-05-16T13:25:00.023+09:00

Demodata を削除する

Opebravo ERP は Oracleのユーザーを１つ追加している

SQL> select username , created from dba_users order by created desc ;

Seed Data,Table

AppsOpenbravo\src-db\database\masterdata
AppsOpenbravo\src-db\database\model\tables

接続ユーザー名の設定

AppsOpenbravo/config/Openbravo.properties:bbdd.user=Oracle_User
AppsOpenbravo/WebContent/WEB-INF/Openbravo.properties:bbdd.user=Oracle_User

データは Xml 形式であるため、 Oracleユーザーを変更して、再度 Installer を実行

Install : C:\OpenbravoERP24
C:\Program Files\Java\jdk1.6.0_13
C:\Program Files\ant\bin\antRun.bat
C:\Program Files\ant\bin\ant.cmd
C:\Program Files\ant\bin\ant.bat
C:\Program Files\apache-tomcat-6.0.18
C:\oraclexe\app\oracle\product\10.2.0\server\BIN
usernaem : erp
Context name : openbravo24
Demo Ddata : no

　webapps に新しいフォルダ

（apache-tomcat-6.0.18\webapps\openbravo24.war）が作成されていることを確認し、

~~uriworkermap.properties を更新(/openbravo24/*=jakarta) し、~~

webapps/openbravo24.war ファイルを　openbravo.war　に rename し、

Tomcat を再起動。

* openbravo.war と openbravo24.war ２つのプロセスが起動してしまっていた。

Openbravo の

Password を

変更

ここでユーザー指定で export しておく。


Export: Release 10.2.0.1.0 - Production on 土 5月 16 14:57:59 2009
Copyright (c) 1982, 2005, Oracle.  All rights reserved.

ユーザー名: erp
パスワード:

接続先: Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
配列フェッチ・バッファ・サイズを入力してください: 4096 >

エクスポート・ファイル: EXPDAT.DMP >

2またはUを指定(デフォルト):ユーザー 、3またはTを指定:表 > U

権限をエクスポートしますか。 (yes/no): yes >

表データをエクスポートしますか。 (yes/no): yes >

エクステントを圧縮しますか。 (yes/no): yes >

JA16SJISTILDEキャラクタ・セットおよびAL16UTF16 NCHARキャラクタ・セットでエクスポートを実行します
サーバーではAL32UTF8キャラクタ・セットを使用します(キャラクタ・セットの変換可能)
. プリスキーマ・プロシージャ型オブジェクトとアクションをエクスポート中
. ユーザーERPの外部関数ライブラリ名をエクスポート中
. PUBLICタイプのシノニムをエクスポート中
. プライベート・タイプのシノニムをエクスポート中
. ユーザーERPのオブジェクト型定義をエクスポート中
ERPのオブジェクトをエクスポートします...
. データベース・リンクをエクスポート中
. 順序番号をエクスポート中
. クラスタ定義をエクスポート中
. ERPの表をエクスポートします... 従来型パス経由...
.. 表       AD_ACCOUNTINGRPT_ELEMENT       0
.. 表                       AD_ALERT       0
.. 表              AD_ALERTRECIPIENT       0
.. 表                   AD_ALERTRULE      19
.. 表               AD_ALERTRULE_TRL       0
.. 表                  AD_ATTACHMENT       0
.. 表               AD_AUXILIARINPUT      61
.. 表                     AD_CALLOUT      81
.. 表                   AD_CHANGELOG       0
.. 表                      AD_CLIENT       1
.. 表                  AD_CLIENTINFO       1
.. 表                      AD_COLUMN    7925
.. 表               AD_COLUMN_ACCESS       0
.. 表                    AD_DATATYPE      15
.. 表                AD_DEPENDENCIES       0
.. 表                   AD_DEVELOPER     100
.. 表                   AD_DIMENSION       4
.. 表                     AD_ELEMENT    1756
.. 表                 AD_ELEMENT_TRL       0
.. 表                       AD_FIELD    7820
.. 表                  AD_FIELDGROUP      35
.. 表              AD_FIELDGROUP_TRL       0
.. 表                   AD_FIELD_TRL       0
.. 表                        AD_FORM      30
.. 表                 AD_FORM_ACCESS      14
.. 表                    AD_FORM_TRL       0
.. 表               AD_HEARTBEAT_LOG       0
.. 表              AD_ID_TRANSLATION       0
.. 表                       AD_IMAGE       7
.. 表                   AD_IMPFORMAT       3
.. 表               AD_IMPFORMAT_ROW      43
.. 表                    AD_LANGUAGE      97
.. 表                        AD_MENU     429
.. 表                    AD_MENU_TRL       0
.. 表                     AD_MESSAGE    5713
.. 表                 AD_MESSAGE_TRL       0
.. 表                AD_MODEL_OBJECT    1360
.. 表        AD_MODEL_OBJECT_MAPPING    2522
.. 表                       AD_MONTH      12
.. 表                        AD_NOTE       0
.. 表                         AD_ORG       1
.. 表                     AD_ORGINFO       0
.. 表                   AD_PINSTANCE       0
.. 表               AD_PINSTANCE_LOG       0
.. 表              AD_PINSTANCE_PARA       0
.. 表                  AD_PREFERENCE      12
.. 表                     AD_PROCESS     293
.. 表              AD_PROCESS_ACCESS      48
.. 表                AD_PROCESS_PARA     266
.. 表            AD_PROCESS_PARA_TRL       0
.. 表          AD_PROCESS_SCHEDULING       0
.. 表                 AD_PROCESS_TRL       0
.. 表               AD_RECORD_ACCESS       0
.. 表                   AD_REFERENCE     308
.. 表               AD_REFERENCE_TRL       0
.. 表                    AD_REF_LIST     734
.. 表                AD_REF_LIST_TRL       0
.. 表                  AD_REF_SEARCH      15
.. 表           AD_REF_SEARCH_COLUMN      48
.. 表                   AD_REF_TABLE      95
.. 表           AD_REGISTRATION_INFO       1
.. 表                        AD_ROLE       1
.. 表              AD_ROLE_ORGACCESS       1
.. 表                  AD_SCRIPT_SQL     670
.. 表                    AD_SEQUENCE     444
.. 表                     AD_SESSION       1
.. 表                      AD_SYSTEM       1
.. 表                 AD_SYSTEM_INFO       1
.. 表                         AD_TAB     516
.. 表                       AD_TABLE     443
.. 表                AD_TABLE_ACCESS       0
.. 表                     AD_TAB_TRL       0
.. 表                        AD_TASK       8
.. 表                 AD_TASK_ACCESS       7
.. 表                    AD_TASK_TRL       0
.. 表              AD_TEXTINTERFACES    1967
.. 表          AD_TEXTINTERFACES_TRL       0
.. 表                        AD_TREE       9
.. 表                     AD_TREEBAR       0
.. 表                    AD_TREENODE     438
.. 表                  AD_TREENODEBP       1
.. 表                  AD_TREENODEMM       0
.. 表                  AD_TREENODEPR       1
.. 表                        AD_USER       2
.. 表                  AD_USER_ROLES       2
.. 表                    AD_VAL_RULE     105
.. 表                     AD_WF_NODE      61
.. 表                 AD_WF_NODENEXT      48
.. 表                 AD_WF_NODE_TRL       0
.. 表                      AD_WINDOW     194
.. 表               AD_WINDOW_ACCESS      75
.. 表                  AD_WINDOW_TRL       0
.. 表                    AD_WORKFLOW      11
.. 表             AD_WORKFLOW_ACCESS       2
.. 表                AD_WORKFLOW_TRL       0
.. 表                     AT_COMMAND       0
.. 表                 AT_COMMAND_TRL       0
.. 表                        AT_LINE       0
.. 表                    AT_ROLLOGIN       0
.. 表                        AT_TEST       0
.. 表                AT_TESTDOCUMENT       0
.. 表            AT_TESTDOCUMENTLINE       0
.. 表                 A_AMORTIZATION       0
.. 表             A_AMORTIZATIONLINE       0
.. 表                        A_ASSET       0
.. 表                   A_ASSET_ACCT       0
.. 表               A_ASSET_ADDITION       0
.. 表                 A_ASSET_CHANGE       0
.. 表             A_ASSET_CHANGE_AMT       0
.. 表                  A_ASSET_GROUP       0
.. 表             A_ASSET_GROUP_ACCT       0
.. 表                    A_ASSET_USE       0
.. 表                   C_ACCTSCHEMA       0
.. 表           C_ACCTSCHEMA_DEFAULT       0
.. 表           C_ACCTSCHEMA_ELEMENT       0
.. 表                C_ACCTSCHEMA_GL       0
.. 表             C_ACCTSCHEMA_TABLE       0
.. 表                     C_ACCT_RPT       0
.. 表               C_ACCT_RPT_GROUP       0
.. 表                C_ACCT_RPT_NODE       0
.. 表                     C_ACTIVITY       0
.. 表                         C_BANK       0
.. 表                  C_BANKACCOUNT       0
.. 表             C_BANKACCOUNT_ACCT       0
.. 表                C_BANKSTATEMENT       0
.. 表            C_BANKSTATEMENTLINE       0
.. 表                     C_BPARTNER       0
.. 表            C_BPARTNER_DISCOUNT       0
.. 表            C_BPARTNER_LOCATION       0
.. 表               C_BP_BANKACCOUNT       0
.. 表             C_BP_CUSTOMER_ACCT       0
.. 表             C_BP_EMPLOYEE_ACCT       0
.. 表                     C_BP_GROUP       0
.. 表                C_BP_GROUP_ACCT       0
.. 表               C_BP_SALCATEGORY       0
.. 表               C_BP_TAXCATEGORY       0
.. 表               C_BP_VENDOR_ACCT       0
.. 表               C_BP_WITHHOLDING       0
.. 表                       C_BUDGET       0
.. 表                   C_BUDGETLINE       0
.. 表                     C_CALENDAR       0
.. 表                     C_CAMPAIGN       0
.. 表                         C_CASH       0
.. 表                     C_CASHBOOK       0
.. 表                C_CASHBOOK_ACCT       0
.. 表                     C_CASHLINE       0
.. 表                      C_CHANNEL       0
.. 表                       C_CHARGE       0
.. 表                  C_CHARGE_ACCT       0
.. 表                         C_CITY       0
.. 表                   C_COMMISSION       0
.. 表                C_COMMISSIONAMT       0
.. 表             C_COMMISSIONDETAIL       0
.. 表               C_COMMISSIONLINE       0
.. 表                C_COMMISSIONRUN       0
.. 表              C_CONVERSION_RATE       0
.. 表                      C_COUNTRY     240
.. 表                  C_COUNTRY_TRL     239
.. 表                     C_CURRENCY     172
.. 表                 C_CURRENCY_TRL     171
.. 表                 C_DEBT_PAYMENT       0
.. 表       C_DEBT_PAYMENT_BALANCING       0
.. 表     C_DEBT_PAYMENT_BAL_REPLACE       0
.. 表                     C_DISCOUNT       0
.. 表                      C_DOCTYPE       1
.. 表                  C_DOCTYPE_TRL       2
.. 表                C_DP_MANAGEMENT       0
.. 表            C_DP_MANAGEMENTLINE       0
.. 表                      C_ELEMENT       0
.. 表                 C_ELEMENTVALUE       0
.. 表         C_ELEMENTVALUE_OPERAND       0
.. 表             C_ELEMENTVALUE_TRL       0
.. 表                  C_EXTERNALPOS       0
.. 表         C_EXTERNALPOS_CATEGORY       0
.. 表          C_EXTERNALPOS_PRODUCT       0
.. 表                         C_FILE       0
.. 表                       C_GLITEM       0
.. 表                  C_GLITEM_ACCT       0
.. 表                     C_GREETING       0
.. 表                 C_GREETING_TRL       0
.. 表                    C_INCOTERMS       0
.. 表                C_INTERORG_ACCT       0
.. 表                      C_INVOICE       0
.. 表                  C_INVOICELINE       0
.. 表    C_INVOICELINE_ACCTDIMENSION       0
.. 表            C_INVOICELINE_OFFER       0
.. 表              C_INVOICESCHEDULE       0
.. 表                   C_INVOICETAX       0
.. 表             C_INVOICE_DISCOUNT       0
.. 表                     C_LOCATION       0
.. 表                       C_NATION       0
.. 表               C_NONBUSINESSDAY       0
.. 表                        C_ORDER       0
.. 表                    C_ORDERLINE       0
.. 表              C_ORDERLINE_OFFER       0
.. 表                     C_ORDERTAX       0
.. 表                C_ORGASSIGNMENT       0
.. 表                  C_PAYMENTTERM       0
.. 表              C_PAYMENTTERMLINE       0
.. 表              C_PAYMENTTERM_TRL       0
.. 表                       C_PERIOD       0
.. 表                C_PERIODCONTROL       0
.. 表                        C_PHASE       0
.. 表                      C_PROJECT       0
.. 表                 C_PROJECTISSUE       0
.. 表                  C_PROJECTLINE       0
.. 表                 C_PROJECTPHASE       0
.. 表              C_PROJECTPROPOSAL       0
.. 表          C_PROJECTPROPOSALLINE       0
.. 表          C_PROJECTPROPOSALTASK       0
.. 表                  C_PROJECTTASK       0
.. 表                  C_PROJECTTYPE       0
.. 表                 C_PROJECT_ACCT       0
.. 表               C_PROJECT_VENDOR       0
.. 表             C_PROMISSORYFORMAT       0
.. 表                       C_REGION     210
.. 表                   C_REMITTANCE       0
.. 表               C_REMITTANCELINE       0
.. 表         C_REMITTANCE_PARAMETER       0
.. 表              C_REMITTANCE_TYPE       0
.. 表           C_REVENUERECOGNITION       0
.. 表      C_REVENUERECOGNITION_PLAN       0
.. 表       C_REVENUERECOGNITION_RUN       0
.. 表              C_SALARY_CATEGORY       0
.. 表         C_SALARY_CATEGORY_COST       0
.. 表                  C_SALESREGION       0
.. 表                 C_SERVICELEVEL       0
.. 表             C_SERVICELEVELLINE       0
.. 表                   C_SETTLEMENT       0
.. 表                         C_TASK       0
.. 表                          C_TAX       0
.. 表                  C_TAXCATEGORY       0
.. 表              C_TAXCATEGORY_TRL       0
.. 表                   C_TAXPAYMENT       0
.. 表                  C_TAXREGISTER       0
.. 表              C_TAXREGISTERLINE       0
.. 表             C_TAXREGISTER_TYPE       0
.. 表       C_TAXREGISTER_TYPE_LINES       0
.. 表                     C_TAX_ACCT       0
.. 表                   C_TAX_REPORT       0
.. 表                      C_TAX_TRL       0
.. 表                     C_TAX_ZONE       0
.. 表                          C_UOM       9
.. 表               C_UOM_CONVERSION       0
.. 表                      C_UOM_TRL       9
.. 表             C_VALIDCOMBINATION       0
.. 表                  C_WITHHOLDING       0
.. 表             C_WITHHOLDING_ACCT       0
.. 表                         C_YEAR       0
.. 表                      FACT_ACCT       0
.. 表                  FACT_ACCT_CFS       0
.. 表                    GL_CATEGORY       1
.. 表                     GL_JOURNAL       0
.. 表                GL_JOURNALBATCH       0
.. 表                 GL_JOURNALLINE       0
.. 表                I_BANKSTATEMENT       0
.. 表                     I_BPARTNER       0
.. 表                   I_BUDGETLINE       0
.. 表                 I_ELEMENTVALUE       0
.. 表                    I_GLJOURNAL       0
.. 表                    I_INVENTORY       0
.. 表                      I_INVOICE       0
.. 表                        I_ORDER       0
.. 表                      I_PRODUCT       0
.. 表                          I_TAX       0
.. 表                         MA_CCP       0
.. 表                   MA_CCP_GROUP       0
.. 表                   MA_CCP_SHIFT       0
.. 表                  MA_COSTCENTER       0
.. 表         MA_COSTCENTER_EMPLOYEE       0
.. 表               MA_COSTCENTER_IC       0
.. 表          MA_COSTCENTER_MACHINE       0
.. 表          MA_COSTCENTER_VERSION       0
.. 表                   MA_GLOBALUSE       0
.. 表                   MA_INCIDENCE       0
.. 表               MA_INDIRECT_COST       0
.. 表         MA_INDIRECT_COST_VALUE       0
.. 表                     MA_MACHINE       0
.. 表              MA_MACHINESTATION       0
.. 表                MA_MACHINE_COST       0
.. 表                MA_MACHINE_TYPE       0
.. 表                 MA_MAINTENANCE       0
.. 表             MA_MAINT_OPERATION       0
.. 表                  MA_MAINT_PART       0
.. 表           MA_MAINT_PERIODICITY       0
.. 表             MA_MAINT_SCHEDULED       0
.. 表                MA_MAINT_WORKER       0
.. 表               MA_MEASURE_GROUP       0
.. 表               MA_MEASURE_SHIFT       0
.. 表                MA_MEASURE_TIME       0
.. 表              MA_MEASURE_VALUES       0
.. 表                     MA_PC_CASE       0
.. 表                     MA_PC_TEST       0
.. 表                    MA_PC_VALUE       0
.. 表            MA_PERIODIC_CONTROL       0
.. 表                 MA_PL_EMPLOYEE       0
.. 表                       MA_PL_IC       0
.. 表              MA_PL_INVOICELINE       0
.. 表                  MA_PL_MACHINE       0
.. 表                     MA_PROCESS       0
.. 表                 MA_PROCESSPLAN       0
.. 表         MA_PROCESSPLAN_VERSION       0
.. 表                     MA_SECTION       0
.. 表                    MA_SEQUENCE       0
.. 表             MA_SEQUENCEPRODUCT       0
.. 表           MA_SEQUENCE_EMPLOYEE       0
.. 表                 MA_SEQUENCE_IC       0
.. 表            MA_SEQUENCE_MACHINE       0
.. 表                     MA_TOOLSET       0
.. 表              MA_TOOLSETPROCESS       0
.. 表                 MA_TOOLSETUSED       0
.. 表                MA_TOOLSET_TYPE       0
.. 表                  MA_WEEMPLOYEE       0
.. 表                 MA_WEINCIDENCE       0
.. 表             MA_WORKREQUIREMENT       0
.. 表                 MA_WORKSTATION       0
.. 表                     MA_WRPHASE       0
.. 表              MA_WRPHASEPRODUCT       0
.. 表                    MRP_PLANNER       0
.. 表             MRP_PLANNINGMETHOD       0
.. 表         MRP_PLANNINGMETHODLINE       0
.. 表             MRP_RUN_PRODUCTION       0
.. 表         MRP_RUN_PRODUCTIONLINE       0
.. 表               MRP_RUN_PURCHASE       0
.. 表           MRP_RUN_PURCHASELINE       0
.. 表              MRP_SALESFORECAST       0
.. 表          MRP_SALESFORECASTLINE       0
.. 表                    M_ATTRIBUTE       0
.. 表            M_ATTRIBUTEINSTANCE       0
.. 表                 M_ATTRIBUTESET       1
.. 表         M_ATTRIBUTESETINSTANCE       1
.. 表                 M_ATTRIBUTEUSE       0
.. 表               M_ATTRIBUTEVALUE       0
.. 表                      M_COSTING       0
.. 表               M_DISCOUNTSCHEMA       0
.. 表           M_DISCOUNTSCHEMALINE       0
.. 表                      M_FREIGHT       0
.. 表              M_FREIGHTCATEGORY       0
.. 表                        M_INOUT       0
.. 表                    M_INOUTLINE       0
.. 表         M_INTERNAL_CONSUMPTION       0
.. 表     M_INTERNAL_CONSUMPTIONLINE       0
.. 表                    M_INVENTORY       0
.. 表                M_INVENTORYLINE       0
.. 表                      M_LOCATOR       0
.. 表                 M_LOCATOR_TYPE       0
.. 表                          M_LOT       0
.. 表                       M_LOTCTL       0
.. 表                     M_MATCHINV       0
.. 表                      M_MATCHPO       0
.. 表                     M_MOVEMENT       0
.. 表                 M_MOVEMENTLINE       0
.. 表                        M_OFFER       0
.. 表               M_OFFER_BPARTNER       0
.. 表               M_OFFER_BP_GROUP       0
.. 表              M_OFFER_PRICELIST       0
.. 表                M_OFFER_PRODUCT       0
.. 表               M_OFFER_PROD_CAT       0
.. 表                 M_PERPETUALINV       0
.. 表                    M_PRICELIST       0
.. 表            M_PRICELIST_VERSION       0
.. 表                      M_PRODUCT       0
.. 表                   M_PRODUCTION       0
.. 表               M_PRODUCTIONLINE       0
.. 表               M_PRODUCTIONPLAN       0
.. 表                 M_PRODUCTPRICE       0
.. 表                 M_PRODUCT_ACCT       0
.. 表                  M_PRODUCT_BOM       0
.. 表             M_PRODUCT_CATEGORY       0
.. 表        M_PRODUCT_CATEGORY_ACCT       0
.. 表             M_PRODUCT_CUSTOMER       0
.. 表                  M_PRODUCT_ORG       0
.. 表                   M_PRODUCT_PO       0
.. 表             M_PRODUCT_TEMPLATE       0
.. 表                  M_PRODUCT_TRL       0
.. 表                  M_PRODUCT_UOM       0
.. 表                       M_RAPPEL       0
.. 表              M_RAPPEL_BPARTNER       0
.. 表               M_RAPPEL_INVOICE       0
.. 表               M_RAPPEL_PRODUCT       0
.. 表       M_RAPPEL_PRODUCTCATEGORY       0
.. 表                 M_RAPPEL_SCALE       0
.. 表                    M_REPLENISH       0
.. 表                  M_REQUISITION       0
.. 表              M_REQUISITIONLINE       0
.. 表             M_REQUISITIONORDER       0
.. 表                     M_SERNOCTL       0
.. 表                      M_SHIPPER       0
.. 表               M_STORAGE_DETAIL       0
.. 表              M_STORAGE_PENDING       0
.. 表                   M_SUBSTITUTE       0
.. 表                  M_TRANSACTION       0
.. 表                    M_WAREHOUSE       0
.. 表               M_WAREHOUSE_ACCT       0
.. 表            M_WAREHOUSE_SHIPPER       0
.. 表                    M_WH_PERIOD       0
.. 表           M_WH_PERIOD_INVOICED       0
.. 表                  M_WH_SCHEDULE       0
.. 表          M_WH_SCHEDULE_PRODUCT       0
.. 表              R_CONTACTINTEREST       0
.. 表                 R_INTERESTAREA       0
.. 表                     R_MAILTEXT       0
.. 表                      R_REQUEST       0
.. 表                R_REQUESTACTION       0
.. 表             R_REQUESTPROCESSOR       0
.. 表       R_REQUESTPROCESSOR_ROUTE       0
.. 表                  R_REQUESTTYPE       0
.. 表             R_RESOURCEPLANCOST       0
.. 表                  S_EXPENSETYPE       0
.. 表                     S_RESOURCE       0
.. 表           S_RESOURCEASSIGNMENT       0
.. 表                 S_RESOURCETYPE       0
.. 表          S_RESOURCEUNAVAILABLE       0
.. 表                  S_TIMEEXPENSE       0
.. 表              S_TIMEEXPENSELINE       0
.. 表                     S_TIMETYPE       0
.. 表                           TEST       0
.. 表                 TIME_DIMENSION       0
.. 表               T_INVENTORYVALUE       0
.. 表                    T_REPLENISH       0
.. 表              T_REPORTSTATEMENT       0
.. 表                    T_SELECTION       0
.. 表                   T_SELECTION2       0
.. 表                        T_SPOOL       0
. シノニムをエクスポート中
. ビューをエクスポート中
. ストアド・プロシージャをエクスポート中
. 演算子をエクスポート中
. 参照整合性制約をエクスポート中
. トリガーをエクスポート中
. 索引タイプをエクスポート中
. ビットマップ、ファンクションおよび拡張可能索引をエクスポート中
. ポスト可能なアクションをエクスポート中
. マテリアライズド・ビューをエクスポート中
. スナップショット・ログをエクスポート中
. ジョブ・キューをエクスポート中
. リフレッシュ・グループと子をエクスポート中
. ディメンションをエクスポート中
. ポストスキーマ・プロシージャ型オブジェクトとアクションをエクスポート中
. 統計をエクスポート中
エクスポートは警告なしで正常終了しました。

Hearbeat Configuration

2009-05-16T12:55:00.007+09:00

設定しようとすると Internal Error となる。
%CATALINA_HOME%/logs のログファイルには
エラーが出力されないため、 IIS の失敗ログを
設定したところ、　Tomcat との接続自体が
500 Internal Error となってしまったため
Disable とする。