[Solution] 1.ROUTING作成時のスケルトン作成処理にお

[Solution]
1.ROUTING作成時のスケルトン作成処理において、BOOK/YEAR をセットする案で問題ないか検討

→Weeklyで話に上がった通り、上記案で問題ないとの結論に至りました。

・これは、 Issue 3471 にて対応した案になるため、この Issue 3471 をリリースすればよい との結論に至りました。
・3471 において、「拠点をまたがるTreeの場合に他拠点のBOOK/YEARが出力され問題になるのでは」との理由で、
一旦保留になっていますが、スケルトンは拠点ごとに作成されるため、別拠点のBOOK/YEARが出力されることはないことを確認しまししたので、問題ないとの判断に至りました。

2.LCV側のP-Sheet 出力も問題ないか確認

→ LCV側も、ROUTINGテーブルのBOOK/YEARをセットしている（＝GLOZAと同じ処理である）ことが確認取れましたので、LCV側も問題ないと判断しております。

Would you approve this solution please.

ผลลัพธ์ (อังกฤษ) 1:

[Solution] 1. There are no problems in the draft to set BOOK/YEAR in the skeleton creation process when you create a ROUTING study→ We concluded as follows up story in the Weekly in the above Bill is no problem.And reached a conclusion because this proposal was supported by Issue 3471 Issue 3471 better if released.-3471 in and output bases BOOK/YEAR tree bases across the problem of, and the reason,That for once has been put on hold, but skeletons are created each BOOK/YEAR another base output and examine better because you reached a decision with no problem.2. check that also P-Sheet output of LCV→ LCV side also sets the ROUTING table BOOK/YEAR we assume 取remashita (= GLOZA same treatment in) that review because LCV side no problem.Would you approve this solution please.

ผลลัพธ์ (อังกฤษ) 2:

[Solution]
in the skeleton creation process at the time of creating 1.ROUTING, a BOOK / YEAR no problem or discussed Settosuru proposal was led as it went up to talk with → Weekly, to the conclusion that there is no problem in the above proposal. - This is to become a proposal that corresponding at Issue 3471, was concluded to be of the Issue 3471 may be released. In-3471, and the reason for the "in case of Tree across the base BOOK / YEAR of other sites is output than a problem", because it will have once pending, the skeleton is created in each location, Now that you have made ​​sure not that of another base BOOK / YEAR is output, and came to a decision with no problem. P-Sheet output also verify that no problem of 2.LCV side → LCV side, (it is the same process as = GLOZA) that set the BOOK / YEAR of ROUTING table because it was taken confirmation, LCV side I we have determined that there is no problem. Would you approve this solution please.

ผลลัพธ์ (อังกฤษ) 3:

Solution]
's skeleton in the forming process of the creation, ROUTING rose street plan to set BOOK and YEAR or problems in

→ Weekly, leading to the problems in the plan and the conclusion. And this is the Issue at corresponding security plan, which led to this release is to Issue 3471 and conclusion. In the security at the reasons in the case of Tree based across the output BOOK YEAR or other problems based on it, "Once it is on hold, the skeleton is created for each base, so as to make sure that it is not outputted based YEAR BOOK or another, leading to the judgment is not a problem. Well, LCV side than on the output LCV P Sheet or problems

→ side, set the table and ROUTING BOOK YEAR processing is the same (= GLOZA) complex was confirmed as the LCV side is judged to have no problem. Please check Would you approve this.
solution