If a MM consultant thinks that these predefined Keys will be sufficient to meet the client requirement then he does not have to define them. In this case, the only thing he has to do is to assign the relevant G/L account to each posting transaction key(except KBS). Once this setting is done than SAP will take care of rest automatically.
In most of the cases, due to complexity of business processes at the client level, consultants find that the use of these transaction/event keys supplied with the standard system is insufficient. They are bound to create more transaction keys to meet the client’s specific requirements. Normally, these requirements come to capture the different types of freight costs either accrual or provisioned. In addition, capturing of different types of planned and unplanned delivery costs in different G/L accounts has now become commonplace. If this is the requirement, a MM consultant should take the following configuration settings in SAP.
2. Code OBYC (configure automatic posting) assign appropriate G/L Account like other Transaction Keys.
3. Assign it to one or more condition types in the relevant Pricing Procedure under appropriate column (AccKY or Provis).
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/81815/viewspace-1032463/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/81815/viewspace-1032463/