美文网首页SAP 实用篇
SAP MM MIRO发票校验合并-FI凭证超过999行(F5

SAP MM MIRO发票校验合并-FI凭证超过999行(F5

作者: 图逗 | 来源:发表于2018-08-11 08:26 被阅读33次
    系统环境:SAP HANA 1610
    业务背景介绍

    在日常业务中,应付会计在进行发票校验MIRO对账时,可能会遇到报错信息:“消息号F5727,在FI中达到的项目最大编号,已超过FI凭证('999')的项目最大“,导致发票校验无法过账;

    问题原因

    对于此种情况,根本原因有两点,其中之一是系统生成会计凭证时,对于GL类型账户分配相同的数据,若里面值字段(例如物料工厂采购订单采购行项目等字段)不相同的话,则会进行细分,就易导致会计凭证行项目过多;其二是不管是HANA系统还是ECC,其会计凭证过账,均记账到BSEG表中,且BSEG-BUZEI字段字符长度只有3位数字;

    综上所述,若发票校验校验过多的采购订单或者同批采购订单行项目分批收货次数过多,都易导致FI凭证行项目过多超过999行; FI凭证

    解决方案

    解决方案根据系统环境可分为ECC版本和HANA版本,不过其基本原理一致:通过系统配置,实现会计凭证合并,来减少FI凭证行项目;OBCY/OBCYX事物代码(所属后台表TTYPV/TTYPVX),存储会计凭证中行项目值不同导致无法合并的字段;即除了TTYPV/TTYPVX中值字段以外的所有字段都是相同的,它们能被合并成一个单独的项目。在会计凭证过账时,其存储在TTYPV/TTYPVX字段的内容会被删除;
    1)ECC版本,可直接采用OBCY,对于MIRO发票校验,其参考过程选择”RMRP发票收据“,字段填充内容可查看“额外知识-OBYC典型配置内容”所示;
    2)HANA版本,SAP提供OBCYX和OBCYA事物代码,进行数据合并,OBCYX针对BSEG进行合并处理,OBCYA针对HANA专属表ACDOCA进行合并;备注:需打NOTE 77161

    系统配置-HANA

    1. 实现ACDOCA表数据合并

    1)维护SM30:FINSVS_ACDOC_FCT
    对EBELN 和EBELP 2个字段,双击进入明细,对“汇总级别”修改成按“2相关汇总”,原来默认为空;即ACDOCA 中字段的汇总,按照基于参考交易 (AWTYP)、凭证类型 (BLART)、公司代码 (BUKRS) 和分类账 (RLDNR) 的特征组合进行汇总。


    汇总级别

    2)维护OBCYA

    对于参考过程为RMRP发票收据、MKPF材料凭证,只需加入EBELP字段;对于参考过程为VBRK销售发票,需加入EBELN、EBELP字段;此处只处理RMRP类型,故系统配置如下图所示: OBCYA
    2. 实现BSEG表数据合并

    1)维护SM31:V_TTYPS
    因HANA 1610版本中,OBCYX表字段不存在采购订单EBELN和行项目EBELP,故需要在此处新增EBELN和EBELP字段;备注:在此之前,需打NOTE 77161,才能新增成功,代码补丁内容如下所示;

    思考:上述操作,为了让OBCYX中能正常显示出EBELN,EBELP;系统允许采购和采购行项目在BSEG中进行汇总; FI汇总:允许汇总字段 Note 77161更改代码部分 2)维护OBCYX
    对于参考过程为RMRP发票收据,维护表和字段所示:
    FI中的增强凭证汇总
    3. MIRO测试实现

    MIRO发票校验,模拟测试显示会计凭证行项目共48行(含物料、工厂、数量等),正式运行保存凭证显示为30行,分配字段仅含采购订单,物料、工厂、数量等内容均为空;

    凭证合并使用风险:-来自36353NOTE

    采用OBCY进行凭证合并后,因BSEG中物料、数量等细节数据缺失,会与标准事物代码逻辑存在矛盾,标准事物代码查询报表不可使用,例如MIRO发票校验合并FI凭证后,标准事物代码IDCNGRIR_GNB(已收货未开票报表查询)无法查询到数据,其根本逻辑来源于BSEG;
    具体注意事项如下:
    Notes:
    When you carry out summarization using the material number (MATNR) during position management or invoice verification transactions, the 'material number' information is lost in the BSEG document table of Financial Accounting. Therefore no entries are written to the BSIM table. This can have the following consequences:
    Transactions such as MR51 (accounting documents for material) or MB5B (balance at posting date) produce incorrect results.
    The evaluation of balances at material number level (characteristic 0MATERIAL) in the SAP Business Information Warehouse displays faulty or incomplete results.
    You can no longer use the Value Flow Monitor (transaction CKMVFM) to compare differences at material level between price difference accounts and the relevant FI postings.
    If you delete the material number (MATNR), the amount (MENGE), the unit of measure (MEINS) or the plant (WERKS) in position management, this information is no longer available in financial accounting. The RMVKON00 report (transactions MRKO and MRPI) however, which indicates and settles the consignation stock, is based on the documents of financial accounting. This has two consequences:
    If the FI documents are not summarized, each individual withdrawal is indicated in the report and can also be individually settled. If the FI documents are summarized, several withdrawals can be displayed in one single report line and can no longer be separately settled. Furthermore, certain data, such as material number, amount and unit of measure, may no longer be displayed.
    If in the FI documents the material number or the plant is deleted and you settle the withdrawal, the tax codes that you defined using the tax indicator (in the material master) or in a purchasing info record can no longer be found. Instead, only the taxcode that you defined as default value in the Customizing settings for the invoice verification (transaction OMR2) is determined. If no valid tax code has been defined there, the settlement terminates with message FF 704.

    思考题;

    1.前端来源进行会计凭证过账时,对于GL类型账户分配相同,其值字段不同,SAP采用按不同凭证行项目进行记账处理,有什么优势?
    答:采用数据分析时,可不用查询前端数据来源,直接获取BSEG中的数据(含物料、工厂、数量、单位、事物类型),更加快捷方便;
    备注:标准事物代码IDCNGRIR_GNB(已收货未开票报表查询),其根本逻辑就来源于BSEG;

    相关NOTE

    1779136 -Extended summarization of FI documents
    77161 -Summarization of postings in FI with purchase order reference
    36353 -Accounting Interface: Summarization of FI documents

    额外知识

    额外知识-OBCY/OBCYX:OBCYX可根据参考过程+凭证类型+公司代码+表+字段进行凭证合并;OBCY只能根据参考过程+表+字段进行合并;两者功能一致,OBCYX更加细化;值得注意的是,设置了OBCYX就不能设置OBCY,反之亦然;两者只能使用一个;

    额外知识-参考过程AWTYP:通过BKPF-AWTYP对象类型,来区分凭证前端来源;以下表格为常见参考交易类型; 常见参考交易类型
    额外知识-OBYC典型配置内容:BKPF-AWTYP对象类型+值字段; 参考交易类型典型配置

    相关文章

      网友评论

        本文标题:SAP MM MIRO发票校验合并-FI凭证超过999行(F5

        本文链接:https://www.haomeiwen.com/subject/zjmrbftx.html