2018年3月4日 星期日

05:32:48,975 INFO  [Doc_Invoice] AD_Dept_ID:1000083
05:32:48,975 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4215, 6020, 0, 0
05:32:48,975 INFO  [Doc_Invoice] AD_Dept_ID:1000074
05:32:48,975 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4216, 4515, 0, 0
05:32:48,991 INFO  [Doc_Invoice] AD_Dept_ID:1000075
05:32:48,991 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4217, 3010, 0, 0
05:32:48,991 INFO  [Doc_Invoice] AD_Dept_ID:1000109
05:32:48,991 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4218, 3010, 0, 0
05:32:48,991 INFO  [Doc_Invoice] AD_Dept_ID:1000086
05:32:48,991 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4219, 9031, 0, 0
05:32:48,991 INFO  [Doc_Invoice] AD_Dept_ID:1000090
05:32:48,991 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4220, 0, 0, 0
05:32:48,991 INFO  [Doc_Invoice] AD_Dept_ID:1000123
05:32:48,991 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4221, 4515, 0, 0
05:32:48,991 INFO  [Doc_Invoice] AD_Dept_ID:1000125
05:32:48,991 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4222, 18061, 0, 0
05:32:48,991 INFO  [Doc_Invoice] AD_Dept_ID:1000126
05:32:48,991 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4223, 6020, 0, 0
05:32:49,007 INFO  [Doc_Invoice] AD_Dept_ID:1000091
05:32:49,007 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4224, 0, 0, 0
05:32:49,007 INFO  [Doc_Invoice] AD_Dept_ID:1000085
05:32:49,007 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4225, 0, 0, 0
05:32:49,007 INFO  [Doc_Invoice] AD_Dept_ID:1000102
05:32:49,007 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4226, 6020, 0, 0
05:32:49,007 INFO  [Doc_Invoice] AD_Dept_ID:1000067
05:32:49,007 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4227, 1505, 0, 0
05:32:49,007 INFO  [Doc_Invoice] AD_Dept_ID:1000084
05:32:49,007 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4228, 1505, 0, 0
05:32:49,007 INFO  [Doc_Invoice] AD_Dept_ID:1000084
05:32:49,007 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4229, 1505, 0, 0
05:32:49,022 INFO  [Doc_Invoice] AD_Dept_ID:1000084
05:32:49,022 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4230, 0, 0, 0
05:32:49,022 INFO  [Doc_Invoice] AD_Dept_ID:1000115
05:32:49,022 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4231, 1505, 0, 0
05:32:49,022 INFO  [Doc_Invoice] AD_Dept_ID:1000092
05:32:49,022 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4232, 1505, 0, 0
05:32:49,022 INFO  [Doc_Invoice] AD_Dept_ID:1000127
05:32:49,022 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4233, 6020, 0, 0
05:32:49,022 INFO  [Doc_Invoice] AD_Dept_ID:1000094
05:32:49,022 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4234, 0, 0, 0
05:32:49,022 INFO  [Doc_Invoice] AD_Dept_ID:1000129
05:32:49,022 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4235, 4214, 0, 0
05:32:49,022 INFO  [Doc_Invoice] AD_Dept_ID:1000082
05:32:49,022 INFO  [Doc_Invoice] docLine.sLine_ID/LineNetAmt, PriceList, Qty:127
4236, 1505, 0, 0
05:32:49,038 INFO  [Doc_Invoice] AD_Dept_ID:1000093
05:32:49,272 INFO  [Doc_Invoice] [Doc][loadDocument] post - deleted maxFact_Acct
_ID = 0
05:32:49,272 INFO  [Doc_Invoice] post - deleted=0 <> DELETE Fact_Acct  WHE
RE AD_Table_ID=318 AND Record_ID=1101379 AND Fact_Acct_ID<=0
05:32:49,287 INFO  [STDOUT] m_ass.length:1
05:32:49,287 WARN  [Doc_Invoice] p_vo.C_Period_ID - 1000257 參數 ,p_vo.AD_Client
_ID=1000014 ,p_vo.DateAcct=2018-02-13 00:00:00.0 ,p_vo.DocumentType=API ,C_AcctS
chema_ID=null
05:32:49,287 WARN  [Doc_Invoice] open (p_vo.C_Period_ID=1000257) - true
05:32:49,287 INFO  [Doc_Invoice] [Doc][getAccount][AcctType == ACCTTYPE_C_Receiv
ableMask][參數(C_BPartner_ID) = 1002760 參數(C_AcctSchema_ID) = 1000005] SQL - S
ELECT C_ReceivableMask_Acct FROM C_BP_Customer_Acct WHERE C_BPartner_ID=? AND C_
AcctSchema_ID=?
05:32:49,381 INFO  [Doc_Invoice] [Doc][getAccount][AcctType == ACCTTYPE_C_Receiv
ableOther][參數(C_BPartner_ID) = 1002760 參數(C_AcctSchema_ID) = 1000005] SQL -
SELECT C_ReceivableOther_Acct FROM C_BP_Customer_Acct WHERE C_BPartner_ID=? AND
C_AcctSchema_ID=?
05:32:49,397 INFO  [Doc_Invoice] [Doc][getAccount][AcctType == ACCTTYPE_C_Receiv
able][參數(C_BPartner_ID) = 1002760 參數(C_AcctSchema_ID) = 1000005] SQL - SELEC
T C_Receivable_Acct FROM C_BP_Customer_Acct WHERE C_BPartner_ID=? AND C_AcctSche
ma_ID=?
05:32:49,397 INFO  [Doc_Invoice] [Doc][getAccount][AcctType == ACCTTYPE_Unearned
Revenue_Acct][參數(C_AcctSchema_ID) = 1000005] SQL - SELECT UnearnedRevenue_Acct
 FROM C_AcctSchema_Default WHERE C_AcctSchema_ID=?
05:32:49,412 INFO  [FactLine] [FactLine][convert] 幣別資料與會計綱要的幣別設定相
同,處理的幣別為本幣 - 289
05:32:49,412 WARN  [Fact] [Fact][createLine]傳入的Account為NULL,沒有會計科目
05:32:49,412 INFO  [Doc_Invoice] fact_m_taxes m_TaxAmt_Conv:0
05:32:49,412 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,412 INFO  [STDOUT] m_C_Charge_ID : 1000209
05:32:49,412 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000209 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,428 INFO  [FactLine] [FactLine][convert] 幣別資料與會計綱要的幣別設定相
同,處理的幣別為本幣 - 289
05:32:49,428 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,428 INFO  [STDOUT] m_C_Charge_ID : 1000209
05:32:49,428 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000209 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,428 INFO  [FactLine] [FactLine][convert] 幣別資料與會計綱要的幣別設定相
同,處理的幣別為本幣 - 289
05:32:49,428 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,428 INFO  [STDOUT] m_C_Charge_ID : 1000209
05:32:49,428 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000209 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,443 INFO  [FactLine] [FactLine][convert] 幣別資料與會計綱要的幣別設定相
同,處理的幣別為本幣 - 289
05:32:49,443 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,443 INFO  [STDOUT] m_C_Charge_ID : 1000158
05:32:49,443 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000158 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,443 INFO  [FactLine] [FactLine][convert] 幣別資料與會計綱要的幣別設定相
同,處理的幣別為本幣 - 289
05:32:49,443 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,443 INFO  [STDOUT] m_C_Charge_ID : 1000158
05:32:49,443 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000158 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,459 INFO  [FactLine] [FactLine][convert] 幣別資料與會計綱要的幣別設定相
同,處理的幣別為本幣 - 289
05:32:49,459 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,459 INFO  [STDOUT] m_C_Charge_ID : 1000158
05:32:49,459 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000158 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,459 INFO  [FactLine] [FactLine][convert] 幣別資料與會計綱要的幣別設定相
同,處理的幣別為本幣 - 289
05:32:49,459 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,459 INFO  [STDOUT] m_C_Charge_ID : 1000019
05:32:49,459 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000019 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,459 INFO  [FactLine] [FactLine][setAmtSource] 借貸方皆為零
05:32:49,459 WARN  [Fact] [Fact][createLine]借貸金額皆為零,無法產生會科資料(至少
需一個不為0)
05:32:49,459 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,475 INFO  [STDOUT] m_C_Charge_ID : 1000019
05:32:49,475 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000019 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,475 INFO  [FactLine] [FactLine][convert] 幣別資料與會計綱要的幣別設定相
同,處理的幣別為本幣 - 289
05:32:49,475 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,475 INFO  [STDOUT] m_C_Charge_ID : 1000019
05:32:49,475 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000019 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,475 INFO  [FactLine] [FactLine][convert] 幣別資料與會計綱要的幣別設定相
同,處理的幣別為本幣 - 289
05:32:49,475 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,475 INFO  [STDOUT] m_C_Charge_ID : 1000019
05:32:49,475 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000019 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,490 INFO  [FactLine] [FactLine][convert] 幣別資料與會計綱要的幣別設定相
同,處理的幣別為本幣 - 289
05:32:49,490 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,490 INFO  [STDOUT] m_C_Charge_ID : 1000019
05:32:49,490 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000019 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,490 INFO  [FactLine] [FactLine][setAmtSource] 借貸方皆為零
05:32:49,490 WARN  [Fact] [Fact][createLine]借貸金額皆為零,無法產生會科資料(至少
需一個不為0)
05:32:49,490 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,490 INFO  [STDOUT] m_C_Charge_ID : 1000019
05:32:49,490 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000019 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,490 INFO  [FactLine] [FactLine][setAmtSource] 借貸方皆為零
05:32:49,490 WARN  [Fact] [Fact][createLine]借貸金額皆為零,無法產生會科資料(至少
需一個不為0)
05:32:49,490 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,506 INFO  [STDOUT] m_C_Charge_ID : 1000209
05:32:49,506 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000209 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,506 INFO  [FactLine] [FactLine][convert] 幣別資料與會計綱要的幣別設定相
同,處理的幣別為本幣 - 289
05:32:49,506 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,506 INFO  [STDOUT] m_C_Charge_ID : 1000158
05:32:49,506 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000158 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,506 INFO  [FactLine] [FactLine][convert] 幣別資料與會計綱要的幣別設定相
同,處理的幣別為本幣 - 289
05:32:49,506 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,506 INFO  [STDOUT] m_C_Charge_ID : 1000209
05:32:49,506 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000209 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,521 INFO  [FactLine] [FactLine][convert] 幣別資料與會計綱要的幣別設定相
同,處理的幣別為本幣 - 289
05:32:49,521 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,521 INFO  [STDOUT] m_C_Charge_ID : 1000019
05:32:49,521 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000019 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,521 INFO  [FactLine] [FactLine][convert] 幣別資料與會計綱要的幣別設定相
同,處理的幣別為本幣 - 289
05:32:49,521 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,521 INFO  [STDOUT] m_C_Charge_ID : 1000158
05:32:49,521 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000158 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,521 INFO  [FactLine] [FactLine][setAmtSource] 借貸方皆為零
05:32:49,537 WARN  [Fact] [Fact][createLine]借貸金額皆為零,無法產生會科資料(至少
需一個不為0)
05:32:49,537 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,537 INFO  [STDOUT] m_C_Charge_ID : 1000158
05:32:49,537 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000158 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,537 INFO  [FactLine] [FactLine][convert] 幣別資料與會計綱要的幣別設定相
同,處理的幣別為本幣 - 289
05:32:49,537 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,537 INFO  [STDOUT] m_C_Charge_ID : 1000158
05:32:49,537 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000158 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,537 INFO  [FactLine] [FactLine][convert] 幣別資料與會計綱要的幣別設定相
同,處理的幣別為本幣 - 289
05:32:49,537 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,537 INFO  [STDOUT] m_C_Charge_ID : 1000158
05:32:49,537 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000158 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,553 INFO  [FactLine] [FactLine][convert] 幣別資料與會計綱要的幣別設定相
同,處理的幣別為本幣 - 289
05:32:49,553 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,553 INFO  [STDOUT] m_C_Charge_ID : 1000158
05:32:49,553 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000158 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,553 INFO  [FactLine] [FactLine][setAmtSource] 借貸方皆為零
05:32:49,553 WARN  [Fact] [Fact][createLine]借貸金額皆為零,無法產生會科資料(至少
需一個不為0)
05:32:49,553 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,553 INFO  [STDOUT] m_C_Charge_ID : 1000269
05:32:49,553 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000269 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,553 INFO  [FactLine] [FactLine][convert] 幣別資料與會計綱要的幣別設定相
同,處理的幣別為本幣 - 289
05:32:49,568 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] SQL - SELECT CH
_Expense_Acct, CH_Revenue_Acct FROM C_Charge_Acct  WHERE C_Charge_ID=? AND C_Acc
tSchema_ID=?
05:32:49,568 INFO  [STDOUT] m_C_Charge_ID : 1000158
05:32:49,568 INFO  [DocLine_Invoice] [DocLine][getChargeAccount] 參數(C_Charge_I
D) : 1000158 參數(C_AcctSchema_ID) : 1000005 從SQL抓取的欄位順序 : 1
05:32:49,568 INFO  [FactLine] [FactLine][convert] 幣別資料與會計綱要的幣別設定相
同,處理的幣別為本幣 - 289
05:32:49,568 INFO  [STDOUT] isSourceBalanced 原幣-有平衡
05:32:49,568 INFO  [STDOUT] isSegmentBalanced 指定Org.-有平衡
05:32:49,568 INFO  [Fact] [Fact][isAcctBalanced] 借貸平衡 - Fact[Doc=[API - Docu
mentNo=F180213HT104,DateAcct=2018-02-13,Sta=y],AcctSchema[1000005-HW1 UN/23 New
Taiwan Dollar],PostType=A]
05:32:49,568 INFO  [STDOUT] balanceAccounting 本位幣-有平衡
05:32:49,568 INFO  [STDOUT] balanceAccounting 換算幣-有平衡
05:32:49,615 INFO  [Fact] [Fact][balanceAccounting] Adjusting Amt=0; Line=FactLi
ne=[318:1101379,Account=[1000682,Client=1000014,Org=1000005,Acct=1001088,Name=進
項稅額,Value=1264.],Cur=289, DR=4214|4214, CR=0|0]
05:32:49,615 INFO  [Fact] [Fact][isAcctBalanced] 借貸平衡 - Fact[Doc=[API - Docu
mentNo=F180213HT104,DateAcct=2018-02-13,Sta=y],AcctSchema[1000005-HW1 UN/23 New
Taiwan Dollar],PostType=A]
05:33:15,839 INFO  [AcctServer] 自動過帳程式,每 60 分鐘執行一次,目前已休息 22 分

2013年6月12日 星期三

TU Graz 2013-09-01  倒數 72天

學生居留證

請注意在您開學之前至少12個星期就必須向奧地利台北辦事處遞交申請
依據 MSSQL Server  運算 
如果參加 .. 德語課程 2013-09-01  
SELECT CAST('2013-09-01' AS DATETIME) - (12 *7) =2013-06-09 00:00:00.000
今天是 2013-06-09 己經過期了

如果是 2013-10-01 學校正式課程
SELECT CAST('2013-10-01' AS DATETIME) - (12 *7) = 2013-07-09 00:00:00.000
2013-07-09 之前必須送件 
臺灣身份證臺灣戶籍謄
出生證明住宿證明良民證 (公證及翻譯如上述)證明您在奧地利留學有充足的財力, 譬如銀行帳戶聲明、薪資證明 
奧地利大學入學許可
您當前的大學確認信

學生居留證

請注意在您開學之前至少12個星期就必須向奧地利台北辦事處遞交申請

文件要求:

  • 學生居留證申請表格填妥並簽名
  • 有效的(並簽名)護照和護照影本
  • 2張最近護照大小彩色相片
  • 臺灣身份證或外籍居留證
  • 臺灣戶籍謄本 (英文正本或中文正本經法院或民間公證人和外交部以及奧地利辦事處公證,若正本是中文則須翻譯成德文,但譯本不用公證)
  • 出生證明(公證及翻譯如上述)
  • 奧地利大學入學許可
  • 您當前的大學/學校 / 您當前公司的確認信
  • 醫療保險證明, 包括所有在奧地利及申根地區的醫療風險, 或奧地利強制險證明
  • 證明您在奧地利留學有充足的財力, 譬如銀行帳戶聲明、薪資證明、工作合約, 自有財產證明, 或奧地利居民 "保證信" ("Haftungserklärung")
  • 良民證 (公證及翻譯如上述)
  • 住宿證明
  • 未成年者: 父母或法定監護人授權同意書〈同意書之同意人必須親自在奧地利辦事處簽名公證,不需經法院, 簽名請帶身份證、護照正影印本。
  • 未成年者在奧監護人經過當地公證之同意書。
  • 其他的文件因情況而要求
 表格及所有文件必須遞交正本和影本。

2013年6月7日 星期五

外國人 在奧地利讀大學的畢業生 = 雙聯學位算嗎 ?



http://www.advantageaustria.org/international/zentral/business-guide-oesterreich/arbeiten-in-oesterreich/Zuwanderung_aus_Nicht-EU-Staaten.zho.html#content=p6

外國大學畢業生

全球年輕人來到奧地利的大學和高等專科學校留學。在留學期間,他們學習相關學科的專業知識,並熟悉這裡的語言、文化和工作環境。他們在這裡利用所學技能和知識,成為推動奧地利經濟發展的巨大潛力。

來自非歐盟國家的大學畢業生可通過簡單的手續取得Rot-Weiß-Rot – Karte並留在這裡工作。
  • 已在某所奧地利大學、高等專科學校或公認的私立大學至少完成 (Diplomstudium ) 學位第 2 階段的學習或整個 (Masterstudium) 碩士學位的學習,在畢業後可在奧地利多停留 6 個月,利用這段時間尋找工作。
  • 如果找到與自己學歷相符且薪資達到法定最低工資的工作時,即可申請Rot-Weiß-Rot – Karte。
  • 2013 年最低工資標準:每月稅前薪資 1,998 歐元
  • 不需經過積分標準評分, 就業服務處 也不需採用替代人員辦法。

外國大學畢業生可在 6 個月居留期內直接在奧地利申請Rot-Weiß-Rot – Karte。詳情請上  移民局入口網站 找到更詳細的信息。

留學期間的工作機會:


非歐盟會員國的留學生在留學期間可以積累實務經驗,在以下範圍內從事工作:
  • 攻讀 (Diplomstudium ) 學位第 1 階段或 (Bachelorstudium) 學士學位時每周最多 10 小時,
  • 攻讀 (Diplomstudium ) 學位第 2 階段或 (Masterstudium) 碩士學位時每周最多20 小時

如已取得聘僱許可(由雇主申請),則無需採用替代人員辦法,即除去影響核發聘僱許可的最大障礙。

2013年5月27日 星期一

標準 SAP 原則上 [評價] 是依據 [工廠] 層級



Purpose

The purpose of this page is to describe the main customizing settings for Account Determination.

Overview

For every goods movement created for a valuated material, the SAP system can create two types of documents:
a material document and an accounting document.

The SAP system follows the accounting principle that for every material movement, there is a corresponding document that provides details of that movement.
In addition, an accounting document is produced that describes the financial aspects of the goods movement.
The material document and accounting (FI) document creation depend on the movement type configuration.
Through the movement type configuration and based on the customizing settings defined for the account determination the SAP System can do automatic account postings.
To determine the customizing settings for Account Determination you should GO through the following customizing path: SPRO -> IMG -> Materials Management -> Valuation and Account Assignment -> Account Determination. 
  
Below sections describe the two ways to define the account determination: Account Determination Wizard and Account Determination without Wizard. 

Account Determination Wizard

It is a proposal from SAP System to define the account determination.
In this step, you can quickly configure the system to make automatic postings by answering the wizard's questions. The wizard undertakes the functions of the following steps:
1. Defining valuation control
2. Grouping valuation areas
3. Defining valuation classes
4. Defining account grouping for movement types
5. Purchase account management
6. Configuring automatic postings
You can continue to use these transactions either in conjunction with or instead of the wizard. 

Account Determination Without Wizard

In this step, you can manually define the settings for account determination in Inventory Management and Invoice Verification.
Account determination without the wizard enables you to make a more complex configuration than account determination with the wizard, but requires that you are already familiar with the principle of automatic account determination in the ERP System.
You can configure account determination with the wizard in the first instance, for example. Then, if the wizard does not meet your company's account determination requirements, you can work without it.
You have to work without the wizard if you use the material ledger (this is standard).
  • Define Valuation Control
It can be configured by the following customizing path:
SPRO -> IMG ->
Materials Management ->
Valuation and Account Assignment ->
Account Determination ->
Account Determination without Wizard->
Define Valuation Control
.
 It defines if the valuation areas will be grouped by activating the valuation grouping code. This makes the configuration of automatic postings much easier.
In the standard SAP R/3 System, the valuation grouping code is set to active as default setting.
Firstly, you should create the valuation grouping code.
It corresponds to the transaction OMWM.
OMWM - Valuation Control

  • Group together Valuation Areas
It can be configured by the following customizing path:
SPRO -> IMG ->
Materials Management ->
Valuation and Account Assignment ->
Account Determination ->
Account Determination without Wizard->
Group together Valuation Areas.
In this step, you assign valuation areas to a valuation grouping code.
Valuation area corresponds to the organization level in which the valuation will occur.
Or the valuation occurs at the plant level or it occurs at the company code level.
如果不同的 [評價區域]
對應相同的 [評價集合碼]
就會有相同規則產生 [會計科目]

The valuation grouping code makes it easier to set automatic account determination.
Within the chart of accounts, you assign the same valuation grouping code to the valuation areas you want to assign to the same account.

The chart of account is a list of accounts.
Within a chart of accounts, you can use the valuation grouping code:
  • to define individual account determination for certain valuation areas (company codes or plants)
Example:
[評價區域]
The valuation areas 0001 and 0002 are assigned to company codes which use the same chart of accounts.

For both valuation areas, however, you would like to define a different account determination.
You must assign different valuation grouping codes (for example, 0011 and 0022) to both valuation areas. 
  • to define common account determination for several valuation areas (company codes or plants)
Example:
Valuation areas 0003 and 0004 are assigned to company codes which use the same chart of accounts. Account assignment for both valuation areas should be similar.
You assign the same valuation grouping code (for example, 0033) to both valuation areas. Thus, you only have to define account assignment for both valuation areas once. 
Requirements:  
  • You must have activated the valuation grouping code in the step Define valuation control (OMWM). 
  • You must have defined the valuation level in corporate structure Customizing. The valuation level is defined in transaction OX14 where you should decide if the valuation will occur at the plant level or company code level. 
  • You must have assigned each plant to a company code in "Enterprise structure" into the Customizing. When assigning your plants, the valuation areas are defined automatically. To assign a plant to company code you should go to transaction OX18. 
OX14 - Define Valuation Level
Recommendation:
SAP recommends that you only use a valuation grouping code within a chart of accounts in order to prevent account determination from becoming confusing. 
Default settings
標準 SAP 原則上 [評價] 是依據 [工廠] 層級

(白話文 不同工廠有不同加權平均成本) 
In the standard SAP system, valuation is predefined at plant level.
All plants are grouped together via valuation grouping code 0001.         
Group together Valuation Areas corresponds to the transaction OMWD.  
OMWD - Account Determination for Valuation Areas

  • Define Valuation Classes
It can be configured by the following customizing path:
SPRO ->
IMG ->
Materials Management ->
Valuation and Account Assignment ->
Account Determination ->
Account Determination without Wizard->
Define Valuation Classes.
In this step, you define which valuation classes are allowed for a material type.
If an user creates a material, he/she must enter the material's valuation class in the accounting data (Accounting 1 and 2 views). The ERP system uses your default settings to check whether the valuation class is allowed for the material type.
 [評價分類] 是將對應同一 [會計科目] 的 [材料]  結合
The valuation class is a key to group materials with the same account determination. 
The valuation classes depend on the material type. 
 多個 [評價分類可對應一個  [材料型式
 一個 [評價分類] 可對應多個  [材料型式
Several valuation classes are generally allowed for one material type.
A valuation class can also be allowed for several material types.
The valuation class determines the G/L accounts which will be updated as result of the goods movement generated for the material.
The valuation class makes it possible to: 因此
同一 [材料型式] 對應不同 [會計科目
不同 [材料型式] 對應同一 [會計科目
  • Post the stock values of materials of the same material type to different G/L accounts
  • Post the stock values of materials of different material types to the same G/L account 
MM03 - Display - Acoount 1 view

The link between the valuation classes and the material types is set up via the account category reference.
The account category reference is a combination of valuation classes. Precisely one account category reference is assigned to a material type.
Requirements
  • You must have defined your material types.
  • You must have defined the chart of accounts.
  • You must have agreed with Financial Accounting which materials are assigned to which accounts.
Default settings
In the standard SAP R/3 System, an account category reference is created for each material type. The account category reference is, in turn, assigned to precisely one valuation class. This means that each material type has its own valuation class. 
OMSK – Account Category reference/valuation class
OMSK – Account category reference button

OMSK - Valuation Class Button

OMSK - Material Type/Account category reference

   
  • Define Account Grouping (account modifier) for Movement Types
Using this function, you can assign an account grouping to movement types. The account grouping is a finer subdivision of the transaction/event keys for the account determination.
The account grouping is provided for the following transactions keys:
  • GBB (offsetting entry for inventory posting)
  • PRD (price differences)
  • KON (consignment liabilities)
The account grouping in the standard system is only active for transaction key GBB (offsetting entry for inventory posting). 
OMWN - Define Account Grouping for Movement Types 
  • Purchase Account Management
It is used to attend legal requirement from specific countries (France, Italy, Finland, Belgium, Spain and Portugal). In this step, you will define a specific valuation and a separate accounting document for Purchase Order postings. 
  • Configure Automatic postings
In this step, you enter the system settings for Inventory Management and Invoice Verification transactions for automatic postings to G/L accounts.
You can then check your settings using a simulation function.
What are automatic postings?
Postings are made to G/L accounts automatically in the case of Invoice Verification and Inventory Management transactions relevant to Financial and Cost Accounting. 
Example:
Posting lines are created in the following accounts in the case of a goods issue for a cost center:
  • Stock account
  • Consumption account 
How does the system find the relevant accounts?
When entering the goods movement, the user does not have to enter a G/L account, since the ERP system automatically finds the accounts for each posting based on the following data: 
  • Chart of accounts of the company code
If the user enters a company code or a plant when entering a transaction, the ERP system determines the chart of accounts which is valid for the company code.
You must define the automatic account determination individually for each chart of accounts. 
  • Valuation grouping code of the valuation area
You must define the automatic account determination individually for every valuation grouping code within a chart of accounts. It applies to all valuation areas which are assigned to this valuation grouping code.
If the user enters a company code or a plant when entering a transaction, the system determines the valuation area and the valuation grouping code. 
  • Transaction/event key
You do not have to define these transaction keys, they are determined automatically from the transaction (invoice verification) or the movement type (inventory management). In this step, you can only insert the account number for each transaction key. 
  • Account grouping (modifier) (only for GBB, PRD and KOM)
Since the transaction key GBB is used for different transactions (for example, goods issue, scraping, physical inventory), which are assigned to different accounts (for example, consumption account, scrapping, expense/income from inventory differences), it is necessary to divide the posting transaction according to a further key: account grouping code. 
  • Valuation class of material or (in case of split valuation) the valuation type
The valuation class allows you to define automatic account determination that is dependent on the material.
You can achieve this by assigning different valuation classes to the materials and by assigning different G/L accounts to the transaction key for every valuation class. 
Default settings:
G/L account assignments for the charts of accounts INT and the valuation grouping code 0001 are SAP standard.  
OMWB - Configure Automatic Postings

OBYC - Maintain FI configuration 










How to test my account determination settings? 
You should go to transaction OMWB and click on ‘simulation’ button. Then, insert the affected material, the correspondent plant and the movement type. After that, click on ‘account assignments’ button and you will see the simulation’s result.
OMWB - Simulation






Important:      
Report DFKB1INT: run it in transaction SE38. It is used to shows us the possible values for the account determination customizing settings. If the customer changed something here, it is not standard anymore.