价值串可以看作是一种记帐规则,为物料移动或者发票校验包含一系的科目特征。定义一系列步骤优先顺序,每一步骤都连接不同的过账事务码,而这个本身就是称为价值串。在我们进行了物料移动或者发票校验后,并不是直接抛由到某一具体的科目中去,而是根据移动类型或者发票校验,连接到相应的价值串,通过价值串,再连接到相应的事务码(账户组)。
Value string & account group code 代表了一个完整的业务过程的,包括所有相关的transaction,预先定义的,无法修改。一个业务过程在Goods movement之中基本由以下因素决定: movement type、value updating、quantity updating、special stock、movement indicator、consumption .同样以上因素也会决定account group code 。Movement type: 不用说了,Value updating: 是否会update value,Quantity updating: 是否会update quantity,Special stock: 不同的special stock可以有不同的account posting,Movement indicator: 是否w/ or w/o po/order等等 Consumption: 就是account assignment了。 路径:OMWN 比如: 普通的101收货到stock的value string 是WE06,可以为某些transaction设置account modification,这就是account groupcode了 这里可以看到相关的value string的transactions.
Valuestring keys are for SAP internal usage. It is just a pointer to the transactionevent key which is necessary for automatic account determination.
Movement types are linked to transaction keys via valuation string in OMWNT-code.
The R/3 System automatically determines the value string assigned to a specifictransaction. It depends partly on entered parameters manually and partly onparameters derived internally by the system. The value string contains allposting transactions that are possible for a certain transaction. The programdecides which of these posting transactions lead to G/L account postings inindividual cases. You cannot define this in Customizing.
Value string WE01, for the goods receipt for a purchase order into stock,contains transactions BSX and WRX.
WE01: BSX, WRX, PRD, KDM, EIN, EKG, BSV, FRL, FRN, BSX, UMB.
WA14: BSX ,PRD, BSX, UMB
WA01: BSX, GBB, PRD, BSX, UMB
Value string RE05 contains transactions BSX and UMB.
In the standard system, value string WE01 is assigned to goods receipts (andalso cancellations and return deliveries) for Standard and Subcontractingpurchase order items without account assignment concerning valuated materialinto stock. In the case of (valuated) goods receipts for purchase order itemsnot subject to account assignment,
post the items to a stock account using the transaction key BSX and make anoffsetting entry to a GR/IR clearing account. A price difference posting(transaction key PRD) is only used if the valuated material is subject tostandard price control and if the order price (or invoice price) is differentfrom the standard price. Transaction key KDM is required in InventoryManagement for purchase orders in foreign currencies because of differences inexchange rates between goods receipts and invoice receipts, unless the materialcan not be debited or credited because it is subject to standard price control.
The transaction keys EIN and EKG (and possibly FRE – see account determinationfor delivery costs) are only used in company codes where purchase accountmanagement is active (as required in Franceand Belgiumfor example).
The transaction keys BSV, FRL, and FRN are only used for the Subcontractingitem category.
Value string WA14 is defined for deliveries without charge (movement type 511).
The following scenarios are possible:
Delivery without charge for material subject to moving average price control →No accounting document
Delivery without charge for material subject to standard price control (and ifthe posting date is in the previous period – standard price in the postingperiod = standard price in the current period) → Inventory posting (receipt atstandard price) and offsetting entry to price differences account
Delivery without charge for material subject to standard price control, withposting date in the previous period and the standard price in the postingperiod is different to the standard price in the current period → Inventoryposting (receipt at standard price) and offsetting entry to price differencesaccount (posting in the previous period) → Stock correction posting andRevenue/expense from revaluation (posting in the current period)
In the standard system, value string WA01 is assigned to goods issues and othergoods receipts. The R/3 System uses an additional influencing factor, accountgrouping, to differentiate further between the various movements during accountdetermination.
Mappingof mvt type and val string is there in OMWN.
The valuation of a goods movement is determined by the valuation strings intable T156S (or T156SY in the newer releases, as of 4.6*).
The value string has behind a posting logic: The values are calculated in theforms which have the same name as the valuation string and which are located inSAPLMBGB.
For example, if you display in SE38 the coding of SAPLMBGB, you will see thefollowing includes:
INCLUDE LMBGBFWA. " WA-Strings
INCLUDE LMBGBFWE. " WE-Strings
INCLUDE LMBGBFWF. " WF-Strings
For example, the form WA01 can be found in LMBGBFWA.
Therefore, please, never modify a valuation string as it would haveconsequences in the valuation and account determination process