自动过账会计科目配置

SAP 会计科目自动分配配置大全1 Maintain Accounting Configuration(概览)Tcode: FBKA/FBKF/FBKP输入Tcode:FBKP 进入后,看到的是图1的画面,在此应该包含了所有的科目设置,设计思路很简单,SAP 要兼顾全球的财务需求,科目设置并没有hard-coded 允许企业根据实际需求和本国的会计准则为业务交易配置相应会计科目.当点击图1-[1]或图1-[3],进入自动过帐科目设置,在这里包含了各模块的配置,下面首先重点讲述MM 自动过帐的配置(OBYC),当真正明白了这些配置及其逻辑,相信你对SAP FICO 就2 Automatic Posting Configuration (MM Module)OBYC 的画面,如图3-[1],是根据企业实际需求自定义的Transaction Key ,下面就OBYC 自上而下个transaction key 举实际例子就常用的transaction key 和科目分配做详细描述.首先,必须定义科目分配的rule 如图4,即你要怎么样配置科目,如图4-[1]表示科目将按General modification|Valuation modif.|Valuation class 三者结合给定会计科目,如你还需要让交MM 科目transaction key 和科目配置详细列表(,幅原因,假设Valuation modif.只有一个所以在建立科目配置rule 时可以不考虑它,除非你使用了多个valuation modif.在科目配置时你必须考虑,请看例1:如何使用Valuation group code ). *关于transactin key 的描述请直接看OBYC,在此省略.Stock posting (BSX)This transaction is used for all postings to stock accounts. Such postings are effected, forexample:o In inventory management in the case of goods receipts to own stock and goods issues from own stocko In invoice verification, if price differences occur in connection with incoming invoices for materials valuated at moving average price and there is adequate stock coverageo In order settlement, if the order is assigned to a material with moving average price and the actual costs at the time of settlement vary from the actual costs at the time ofgoods receiptBecause this transaction is dependent on the valuation class, it is possible to manage materials with different valuation classes in separate stock accounts.CautionTake care to ensure that:o A stock account is not used for any transaction other than BSXo Postings are not made to the account manuallyo The account is not changed in the productive system before all stock has been booked out of itOtherwise differences would arise between the total stock value of the material master records and the balance on the stock account.Account determination of valuated sales order stock and project stockNote that for valuated sales order stock and project stock (special stock E and Q) and for thetransaction/event keys BSX and GBB, you must maintain an account determination to avoidreceiving warning messages when entering data (purchase order or transfer posting) forvaluated stock.During data entry, the system attempts to execute a provisional account determination for GBB for valuated stock. The system will only replace the provisional account determination for GBB with the correct account determination for the stock account (BSX), in the background, if youenter the data for valuated stock at a later point in time.例1:如何使用Valuation group codeValuation class 用来区分不同的物料:不同的原材料,不同的半产品,不同的在产品,不同的产成品首先请执行OX14,SAP默认的Valuation level(评估级)是plant级的,在这种情况下Valuationarea就是Plant(未知何种业务会采用Company level,),这符合一般的成本核算目的,因为一个生产企业大都会根据比如产品类别甚至仓储地点(如俩存货仓库在不同地点要进行存货转移)设置plant.*你也可参考(SE11:MBEW)评估表MBEW,Valuation area即plant回顾一下这几个概念:Valuation level/Valuation area/Valuation class/Valuation type/Valuation group /Valuation method/Valuation mode/Split Valuation图例1-1[1],OMWM激活V aluation group,这样可更方便OBYC科目配置.图例1-1[2],将Valuation area（是根据组织架构而来的，不是直接建立的）组合起来.如图例1-2,所有的公司的所有plant都group在一起使用一个valuation group code CONO(和会计科目表同名,集团只使用了一个会计科目表)需要定义一个还是多个Val. Grpg Code呢?如图例1-2,比如company code 4100有两个plant 4100和4101,你可定义一个Val. Grpg Code 和company code同名叫4100 ,同样company code 5100有两个plant 5100和5101,你定义val. Grpg code 5100.这样分散和集中定义Val. Grpg Code各有什么好处.分散定义,你在OBYC里能方便为不同的公司定义相同的Valuation class给定不同的科目,如果是只使用一个Val. Grpgcode可能就难于到达目的, 当然有的科目配置可能并不需要使用Val. Grpg code(OBYC是Valuation Modif.)你根据实际需要决定使用一个还是多个Val. Grpg code(Valuation modif.)例2 PO condition和OBYC例3使用PO处理委外加工例4 Account assignment的逻辑分析例5采购运费处理1.运费进库存.2.计划外运费例6:P&L科目和成本要素的建立例7采购科目分配设置例8汇率变更影响发票校验.天啦,设计逻辑和从什么地方获取科目都要讲,什么世界?例9月结GR/IR处理委外加工的种类和处理方法(使用prod. Order和purchase order)……………..……………..Background: (10)1.Related IMG (10)Step 1.Define valuation class for those non-material (10)Step 2.Define PO Account Assignment Categories (10)Step 3. Assign account to VBR (10)Step 4.Where we define valuation class (10)2.Q&A (10)1 (10)2.................................................................................................. 错误！未定义书签。

3 (11)Background:For these so-called charge or consumption PO, When creating a PO, we choose account assignment category ‘K’ and input a material group .1.Related IMGStep 1.Define valuation class for those non-materialWe can define additional valuation class (difference from material master data) for assets or charge(service) PO (Non-material )Step 2.Define PO Account Assignment CategoriesStep 3. Assign account to VBRStep 4.Where we define valuation class2.Q&A1.How to Activate Direct Posting to G/L Accounts and Material AccountIn PRD800, The Entry had been deleted.After clicking New Entries button, the 2 lines shown as below will be seen .After that , you can see 3 tabs being added while using MIRO.And then you can directly post G/L account for vendor invoice verification .We can get the result as you require.Dr: XXX ChargeCr: Vendor AP2.What will Happen?And when you use ME2N (or other related t-code to check), you will findStill to be delivered(invoiced) qty will always have data , that means the PO is always in open status .3.Mark delv. CompletedWe can mark Delv. Completed to avoid the open POAfter marking delv. Complelted, It shows OK.So,Here is my questions, For the purpose of financial control , Enterprises often use PO for any payment (Otherwise, For the above d mentioned charge PO, we needn’t use PO but use FB60 directly make invoice verification, I think it will be more simply).Why we donn’t make a GR action which may mean we have got the service, receipt the consumption goods etc ? (Even if it might be a virtual GR—Service GR) ?什么是GR-based invoice verification?Indicator specifying that provision has been made for goods-receipt-basedinvoice verification for a purchase order item or invoice item.If this field is selected:the field "GR-based invoice verification" is preselected in the info recordwhen such a record is created for this vendor. (Note: if you change the selectionin the vendor master record, the info record does not change automatically);1.将字段设置LFM1-WEBRE(Goods-receipt-based inv.verif.)选上,在XK02将的vendor的Goods-receipt-based inv.verif.勾选上.2.在后台将字段设置LFM1-WEBRE(Goods-receipt-based inv.verif.)必输Financial accounting->Accounts Receivable and Accounts Payable->vendor account->master records->Preparations for Creating Vendor Master Records->Define Account Groups with Screen Layout (Vendors)然后选择你所需要的vendor account选edit fields status.fields status选Purchasing data->Purchasing data->Goods-receipt-based inv.verif.设置为必输Req.3.一般你此是create PO会自动把item下->invoice下的GR_based inv选上.然后你MIRO时reference doc就是migo 的mat. doc.4. T-code :OLMRLISTOr SHD0:(从菜单goto从transaction variants切到screen variant 实际上俩t-code功能一样) 然后你设置你自己的screen variant将不要的字段全hide或到后面去.将Reference Doc.(DRSEG-LFBNR)放在前面.***这个refence doc注意还有什么reference doc. no不是它,是和material doc no一般是相同的. ***其实它指向的是original mat doc no. 我的系统这个是和mat doc no同步的,***但是有的系统这个reference doc.是空的,问过MM顾问这家伙却不知道why.比如你MIGO mat doc是5000000737,MIRO的refence doc也是5000000737,但是如果你对此mat. doc比如做反冲退货什么的产生的mat doc是5000000739,很遗憾它依然对应5000000737 .我小小读了一遍MIRO code但是没时间仔细研究它究竟是什么时候出来的.***还有可能某种原因在create Po时item下->invoice下的GR_based inv并没有选上,我们公司APer说比如PO 100, MIGO 100, 也MIRO了100,比如这时退30,她可能要做两此(不知是否她吃的太饱),一次100,还有credit 30(对国外vendor),如果根据reference doc带出来是balance 70并且是MIGO 100产生的mat doc,即使你开credit memo 30带出的依旧是MIGO 100产生的original mat doc. 所以现在找user_exit coding一下基本了解,receiving plant create PO后,使用VL10B ( VL02N),anyway是supply plant产生的交货单比如叫DELNOTE1,这时在receiving plant MIGO时你在Delivery note 栏手工输入交货单DELNOTE1(第一此由仓库输入,痛苦!), 然后MIRO时你选择2 Delivery note然后带出来的是交货单DELNOTE1.如果一张大的PO有很多次交货或者很多PO多次交货, 然后自然delivery note也可带出PO,假定你已经设置好了reference doc.就是receiving plant的MIGO产生的mat doc ,也就是所谓的收货单, 原则上, 发票校验希望PO, 交货单,自己的收货单和vendor开来的真正的V AT invoice四者相同就通过.现在delivery note一下是可paste几行的, 你还不满足, anyway你希望来一个问题,直接将一两百个delivery note一下upload然后再校验,是吗? 本屠夫实在就搞不明白, 让APer小姐做个excel, 那不是有个more allocationcriterial button,慢慢paste也很快呀,我就搞不懂还要什么coding ?。