Smartforms table and templet auth new line.

當規劃Smartforms時有自動換行需求時，必需注意使用的是table或是templet。

元件	特性
Templet	需要加Loop，固定列高，超出欄寬換行時受列高影響而截字
Table	本身有Loop，不固定列高，超出欄寬換行不受列高影響而截字

Evaluated Receipt Settlement (ERS)

Main
Evaluated Receipt Settlement is the procedure for settling the Goods receipts automatically. Purchaser enters into the agreement with the vendor that the purchaser system posts the invoice document automatically on the basis of the purchase order and the goods receipts. Main advantage of this process is that this process eliminates the invoice variances and there is no requirement for the vendor invoices.

IMG Setting:
1.Define Message type
  SPRO> IMG>MM>LIV>Message determination > Maintain Message Types
2.Maintain Message Schemas
  SPRO> IMG>MM>LIV>Message determination > Maintain Message Schemas
3.Maintain Conditions
  SPRO> IMG>MM>LIV>Message determination > Maintain Conditions
4.Assign Forms and Programs
  SPRO> IMG>MM>LIV>Message determination > Assign Forms and programs

ERS Process:
1.Setting Vendor Master
   Control tab - AutoEvalGRSetmt check box active.
2.Setting Info Record
   Control tab - No ERS check box no active.
3.Check PO
   Invoice tab - ERS active.
4.Evaluated Receipt Settlement(ERS) with Logistics Invoice Verification
   Run T-code:MRRL. The Simulation is also possible by test run.

form
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20c57f75-d26f-2910-c3aa-dee124530121?QuickLink=index&overridelayout=true&10402410816402

UniCode - 銀行檔案TXT檔錯位

因錯位的欄位會出現在中文字的後一個欄位
所以需要算出原本8300的字元數與4110的字元數差異後
才知道下一欄要放多少位移數。

Ex:
t_text+57(40) = field.
之後要計算 下一個欄位要開始的位置~

call function 'SCMS_STRING_TO_XSTRING'
    exporting
      text     = field      --->  中英文混雜字串
      mimetype = 'C'
      encoding = '8300'   ---> 以8300 編碼轉換
    importing
      buffer   = out_str.   -->轉換出來的文字字串

  len_in_byte = xstrlen( out_str ).      >計算出8300的長度

     len_in_char =  strlen( field ).   ---> unicode長度
  diff = len_in_byte - len_in_char.    ----> 計算 unicode 與非 unicode 長度差異
                                                                         unicode 長度<=編碼8300的長度
  pos = 57 + ( 40  - diff )  .  ---> 計算下一個欄位的位置
 所以下一個欄位
t_text+pos(n) = xxxx.

Upload/Download SAPScript Form

T-Code:SE38
Program Name: RSTXSCRP

Download:
在畫面Object Name輸入要下載的Form名稱
            Mode選擇Export
            File Name輸入下載入徑

Upload: (如果要更改上傳Form Name，需打開文字檔將舊檔名至文字檔更新為新檔名後存檔)
在畫面Object Name輸入要上傳的Form名稱
            Mode選擇IMPORT
            File Name輸入上傳入徑

MB1C - Message No. M7093

事由：當A Plant 將料送至B Plant作加工，這時B廠收901收料時，不能產生GL Account。
執行MB1C時發生以下Error Message
Fld selectn for mvmt type 901 / acct 7480000 differs for Customer goods movement(015)

1.T-code: SE38.
   Program Name: RM07CUFA

2.原因Mvt: 901在Account Grouping設定為1.管價不管量 2.管價也管量..
   而B Plant該Material Type:ROH 設定為管量又管價會產生GL Account...
   故修正B Plant作901時管量不管價，不會觸發Account.

PS 相關IMG
．Logistics -General/MM/Basic Settings/Material Types/Define Attriubtes of Material Types.
．MM/Inventory Management and Physical Inventory/Movement Types/Copy, Change Movement Types.
．MM/Valuation and Account Assignment/Account Determination/Account Determinatin Without Wizard/Configure Automatic Postings.

AFAB Message No.AA776

4.7版本的AFAB需自己在程式加註Message警告Number Range需內部給號
所以Technology Upgrade後如果設定為外部給號時
便會產生Message No.AA776要求內部給號
解決方法T-Code:FBN1將外部給號打勾取消
Note:890976

MIRO - Error RW011 ( No subsequent document found in Accounting )

在升級時碰到MIR7發現無法找到FI doc.
原因是Logical System在後來被修改過而造成的
檢查方法參照 Note 781498
請Basis修正該錯誤參照Note 446294

Note 781498
Symptom
You display a logistic invoice via transaction 'Display invoice document'
(MIR4). When you click on the button 'Follow-on documents' you receive the
message 'No subsequent document found in Accounting' (RW011).

Solution
Using transaction SE16, table RBKP, enter document number, Fiscal Year.
Check the value of logical system, field LOGSYS.
Using transaction SE16, table T000, check logical system maintained for the
client. If there is a change in logical system the link to follow-on
documents in financial accounting is lost. To correct this please refer to
the note 28958. Please also refer to the other related notes.

 Note 446294
Symptom
Following a client copy, entities still have the old logical system name of the source client.

The workflow cannot use or forward on objects that were created in the source client.

Consequently, you can no longer branch to the relevant accounting document when you display the material document in transaction MB03, for example. The M7082 message appears instead:
   Material document & does not include an accounting document

Solution
Define a logical system using transaction BD54 and assign it to the target client using the client administration (transaction SCC4).
If the client was already copied, you can still convert the logical system, if necessary, using transaction BDLS.
The logical system name is not converted automatically by the client copy until after Release 4.6C with SAPKB46C21 or 4.6D with SAPKB46D08. However, a prerequisite for this is that the target client already has a logical system name before the copy is started.
With client transports the attached correction 407854 or 407856 is also required (comes with SAPKB46C32, SAPKB46D21 or SAPKB61017).