GGB0 创建/更改有效性检查
GGB1 创建/更改替代
GGB4 激活有效性检查、替代
Table:V_GB01C GB01
Program: RGUGBR00
OBY6 公司代码全局参数 EC01 复制公司代码
科目表 信贷控制范围 会计年度变式 字段状态变式 过账期间变式
OBY7 复制会计科目表
OB29 维护会计年度变式
OBBO 维护过账期间变式
OY01 国家定义
OB22 公司代码的附加货币
OX03 维护业务范围 OKBD 维护功能范围
OBBG/OBCO/OBCP/ OBCL/FTXP 税
OBD4 维护科目组
OBC4 维护字段状态变式
OB41 记账码
OB53维护留存收益科目
FBKP 自动科目分配
OB40 税务科目分配
OBYC MM自动科目分配
OBA4 FI tolerance groups for users OBA3 客户供应商容差组 OBXL 分配原因代码到GL, Define Accounts for Overpayments/Underpayments.
In addition to the amount, you also enter a percentage rate in the Percent field. The lower limit is valid. If you only want to use absolute amounts or percentage specifications, then you must enter the maximum value in every other field. E.g. 100%
Note that you define these limits for your customers/vendors and your employees. The lower limit is valid.
OBA7 定义凭证类型 OB41 Posting Key
应收应付
OBB8 支付条件
The day limit is the calendar day to which the terms of payment are valid.
Fixed day used to overwrite the calendar day of the baseline date.
付款差异:Employee tolerance groups, G/L account tolerance groups and customer/vendor tolerance groups.
OBXL 为原因代码指定总账科目
一、年度结算的步骤:
按照平常月度执行月度结算
将总分类帐会计科目余额结转至新的会计年度
将利润中心余额结转到新的会计年度
结转资产余额到新的会计年度
5、预算余额结转到新的会计年度[T-CODE:FM01、FMJ2、FMJA、FMJB、FMJC]
1、新的年度会计凭证号码范围是否已经维护[FBN1查询凭证号码范围的跨及年度、OBH2的跨维护会计凭证号码到新的会计年度]
2、使用事务代码KS13检查成本中心的有效期,并作维护;
使用事务代码KA23检查成本要素的有效期,并作维护;
使用事务代码KL03检查作业类型的有效期,并作维护。
OAOB 折旧表分配到公司代码
OAOA 资产分类 科目确定 号码范围 屏幕格式 被分配 默认折旧方法
OADB 维护折旧范围 - 在某个折旧表下
AFAMA 维护折旧码 - 在某个折旧表下
基本方法 的后台配置是选择一个折旧方法
余额递减方法 期间控制 多层方法
OAYZ 对资产分类分配折旧范围;折旧范围下对应的使用年限、折旧码的默认值
ABAA 计划外折旧 ABMA 人工折旧 ABSO 杂项调整
特殊折旧 业务类型组 60 61 62 63
计划外折旧 业务类型组 64 65
ANLA 资产主数据 ANLB 资产折旧方法 ANLC 资产值字段 ANLP 资产周期值 ANEK 资产凭证头ANEP 资产凭证行项目 ANLZ 与时间相关的分配
原值 ANLC-KANSW + ANLC-ANSWL
1.计划外折旧和特殊折旧等非正常折旧值只影响资产净值.影响不影响折旧是看资产对应的折旧码,确切地是折旧码对应的多层方法(Tcode:AFAMS)里的基值,典型的基值有
01:购置值
03:重置价值
24:帐面净值
如果对应的基值选择01,则月折额只和购置值相关 如果基值选择24,则月折旧额和帐面净值相关.
2.可以任意使用Tcode: ABZU|ABMA|ABAA,重要的是使用的业务类型对应的业务类型组是62|63|64|65|,业务类型组是SAP预先定义的
双倍余额递减法:
阶段1::
1、基本折旧方法选择0011(Ordinary: percentage from useful life)
2、余额递减方法选择002(主要是Declining-balance multiplication factor即递减乘数因子为2,即在正常折旧率的基础上乘以2)
5、转换方法选择1(Changeover when straight-line dep. is higher (Germany)),表示当采用直线法的折旧额大于采用双倍余额递减法折旧额时进行折旧方法转换
阶段2:
4、多层方法基值仍为24,但应勾选“剩余年限”,表示资产净值在剩余年限内进行摊销
双倍余额递减法是在不考虑固定资产残值的情况下,根据每期期初固定资产账面净(固定资产账面余额减累计折旧)和双倍的直线法折旧率计算固定资产折旧的一种方法,其计算公式为:
年折旧率=2/预计折旧年限×100%
月折旧率=年折旧率/12
月折旧额=固定资产账面净值×月折旧率
多级方法:这个参数将直接影响到资产折旧。
图1 显示的是多层设置方法的界面,其中有效期开始可以进行选择,表示从哪个时间点开始计提折旧
图2 表示基值的选择,当我们进行多级方法设置的时候,需要选择计算的基础,系统中已提供了标准配置的基值计算方法,下面我将分别演示01购置值,24账面净值在是否考虑剩余使用年限的两种情况下,资产计提折旧数的不同。
假设 资产A 购置日期为2009年2月,净残值率为10%,使用年限为20年,下月开始折旧,采用直线法折旧。
第一种情况,基值为账面净值,不考虑剩余使用期
计算结果如下
计算过程如下
2009年折旧=5000*(1-10%)/20/12*10=187.5
2010年折旧=【5000*(1-10%)-187.5】/20=215.63
2011年折旧=【5000*(1-10%)-403.13】/20=204.84
第二种情况 基值为账面净值,考虑剩余使用期
计算结果如下
计算过程如下:
2009年折旧=【5000*(1-10%)/20 】 10/12 =187.5
2010年折旧=【5000*(1-10%)-187.5】/(240-10) *12=225
2011年折旧=【5000*(1-10%)-412.5】/220 *12=225
第三种情况,基值为购置价,不考虑剩余使用期
计算结果如下
计算过程如下:
2009年折旧=5000*(1-10%)/20/12*10=187.5
2010年折旧=5000*(1-10%)/20=225
2011年折旧=5000*(1-10%)/20=225
第四种情况,基值为购置价,考虑剩余使用期
计算结果如下
计算过程如下
2009年折旧=5000*(1-10%)/20=225
2010年折旧=5000*(1-10%)/(240-10)*12=234.78
2011年折旧=5000*(1-10%)/(240-22)*12=247.71
总结:从上面四种情况可以看出,对于基值、是否考虑剩余使用期的不同选择将出现不同的结果,其中对于第二种、第三种情况来说,SAP系统标配的情况下,会对本年新增的资产价值在本年已提折旧的使用期内按新价值重新补提折旧,因此一般的情况下折旧额是相等的。
Results Analysis used to collect costs by doing a periodic valuation of sales order inventories.
Results Analysis Key: Used for Account determination. The key specifies the object (example a sales order item) to be selected during results analysis calculation. (A number of valuation control parameters are linked to this key).
Production order/ sales order/
KKAX 计算在制品 CO88 结算在制品 只有FI凭证 (OKG8中定义借贷科目,借 在制品 贷 生产生病转出-在制品)
计算在制品的冲销财务分录呢??? 在下个月结算此定单时,会自动产生冲销分录。
KKAK 销售订单结果分析 VA88 结算
OVZG valuation is blank
Material document has no corresponding accounting document.
Settlement of Sales Order Items
Use
The revenue, cost of sales, and reserves for imminent loss for the sales order item are transferred to CO-PA by period.
The work in process, reserves for unrealized costs, reserves for the cost of complaints, and reserves for imminent loss for the sales order item are transferred to FI and EC-PCA by period.
Transfers the costs and revenues posted on a sales order item to further application components
Integration
You can use the Schedule Manager to assist you in performing the period-end closing activities. For more information, refer to the following sections:
Scheduler
Monitor
Flow Definition
You cannot use the multilevel worklist of the Schedule Manager in the Product Cost by Sales Order component.
If the sales order item has no results analysis key, the settlement process accomplishes the following:
If CO-PA is active, settlement transfers the costs and revenues of the sales order item to a profitability segment in CO-PA
If CO-PA is not active, settlement transfers the costs and revenues of the sales order item to a G/L account in FI.
If you have performed results analysis, the settlement process transfers the following results analysis data by period:
Inventory values
Reserves for unrealized costs
Reserves for imminent loss
Reserves for complaints and commissions
The cost of sales (if you are using a nonvaluated sales order stock and are balancing in FI using the cost-of-sales accounting method)
Cost of sales or calculated revenue
Reserves for imminent loss and complaints
The work in process to FI and EC-PCA
The reserves for unrealized costs or complaints to FI and EC-PCA
The reserves for imminent loss to FI, EC-PCA, and CO-PA
The costs and revenues relevant to the profit to CO-PA
The data is transferred to FI and EC-PCA when you settle.
If the sales order item has a results analysis key but you have not performed results analysis, the system does not settle anything.
Prerequisites
If CO-PA is active, the system generates a settlement rule when you create the sales order. The settlement rule determines whether data is settled to other objects or other areas in Controlling. In accordance with this settlement rule, the relevant data is settled to CO-PA.
If CO-PA is not active, create a settlement rule. This settlement rule that you create manually normally contains a G/L account as a receiver (such as 399999). You can also settle costs and revenues or results analysis data to objects with revenue.
You can also settle the cost of sales calculated in results analysis to a fixed asset or a cost center. To do this, you must add to the allocation structure the results analysis cost elements under which the cost of sales is updated to the order.
The settlement rule includes a distribution rule for the sales order item. The distribution rule is made up of a settlement receiver, a settlement share, and a settlement type:
The settlement receiver (such as profitability segment or G/L account) specifies the object to which the actual costs and revenue of the sales order item are settled. The settlement receiver can be proposed through the settlement profile.
The settlement share defines the percentage or the equivalence numbers used to distribute the costs to the individual settlement receivers. The settlement share for sales order items is usually 100%. A settlement share of 100% is preset in the system.
The settlement type specifies full settlement of the sales order item. This ensures that all the data on the sales order is available for results analysis.
Settlement still takes place in each period. The revenues and the cost of sales are transferred to CO-PA by period, and the work in process and the reserves are transferred to FI.
Prerequisites for Settlement to CO-PA
For a sales order item to be settled to CO-PA, you must enter valid settlement parameters for the item. Such settlement parameters include a settlement profile, an allocation structure, and a PA transfer structure. Carry out the following steps in Customizing for Product Cost Controlling under Cost Object Controlling Product Cost by Sales Order Period-End Closing Settlement:
Defining Settlement Profiles
The settlement profile determines the settlement receivers (such as profitability segment or G/L account) to which the order can be settled.
Allocation structure
PA transfer structure
Source structure
The settlement profile is defaulted through the requirements class.
If you are settling the costs and revenues to a profitability segment or G/L account, you must define an allocation structure.
The allocation structure determines which costs and revenues are settled to the settlement receiver. It splits the debit cost elements and the revenue elements according to settlement assignments and assigns the settlement assignment to a settlement cost element.
Every debit cost element and results analysis cost element must be included in the allocation structure.
Each debit cost element and results analysis cost element can only be assigned to one settlement cost element.
...