ITPub博客

首页 > Linux操作系统 > Linux操作系统 > BAPI_INCOMINGINVOICE_CHANGE M8 524错误

BAPI_INCOMINGINVOICE_CHANGE M8 524错误

原创 Linux操作系统 作者:wangyuzhen 时间:2012-09-12 14:19:07 0 删除 编辑
有个将超多行项目的预制凭证拆分为多个较少行项目预制凭证的程序用到了BAPI_INCOMINGINVOICE_PARK,BAPI_INCOMINGINVOICE_CHANGE,报错M8 524 你不能处理关于交货成本的条件(You cannot process conditions for delivery costs)
在网上搜到一个帖子
http://www.erp100.com/thread-237523-1-1.html
=================================================================
做了一个根据采购订单的价格条件类型,按照不同的条件类型供应商自动做发票校验,结果在测试机上没问题,在生产机上提示:你无法处理关于交货成本的过账。后来以为权限的问题,多次测试,权限也配置了,还是不行,发mesSage咨询了一下,才发现了真正的问题。
下面是一些message的回复。

Please review the following note which gives a reason for error M8524,

please note that although the code corrections are not valid for your
release, the logic of the note is still relevant:
591415 BAPI: Delivery costs and freight vendors
"...
b) You specify a delivery costs line without a delivery vendor L1
for condition type K1 at the BAPI interface and
- there are two different delivery vendors L1 and L2 for the
same condition K1: the system generates the error message
'Processing of the conditions with delivery costs not
possible'. The reason is the missing uniqueness concerning the
line specified at the interface. In this case, you best create
a second delivery costs line at the interface with K1/L2 in
order to eliminate this problem and to fill the delivery
vendor field of the first one with L1.
...
If a combinatin occurs in which no unique assignment is possible betweenthe lines which are specified at the interface of the BAPI and the stillopen, to be settled delivery costs, the system issues an error message
..."
As the solution please take into account what note suggests:
"...
In this case, you best create a second delivery costs line at
the interface with K1/L2 in order to eliminate this problem
and to fill the delivery vendor field of the first one with L1.
..."
According to our design, As you create an invoice for planned delivery
costs using our standard BAPI process, the data ITEMDATA[]-FREIGHT_VEN
is not applied as invoicing party for the BAPI invoice, but used with
others data COND_TYPE, COND_ST_NO and COND_COUNT in ITEMDATA together tofind the condition's data from corresponding PO/item, GR DOC and PO
history's data.
It means:
. If you don't fill the freicht vendor into ITEMDATA[]-FREIGHT_VEN,
system'll try to find the condition's data only based on others data
COND_TYPE, COND_ST_NO and COND_COUNT in ITEMDATA.
. Otherwise, if you fill a vendor into ITEMDATA[]-FREIGHT_VEN, system'll try to find the condition's data based on the vendor and others data
COND_TYPE, COND_ST_NO and COND_COUNT in ITEMDATA.
. If the filled vendor in ITEMDATA[]-FREIGHT_VEN is not same as that in
PO, GR or PO history, then system can't find the condition's data from
these PO, GR or PO history's data, in this case you'll receive message
M8 524 in the BAPI process.
就是ITEMDATA[]-FREIGHT_VEN再赋上交费中心
==============================================================
之前报过一个错
M8 332 PO项目的计划交货成本的定义不正确(Planned delivery costs for PO item & & incorrectly defined)怀疑是这个问题,让开发顾问将COND_TYPE置空,结果出了这个M8 524的问题。
DEBUG到时BAPI_INCOMINGINVOICE_CHANGE时报错,在内表里将ITEMDATA-COND_TYPE加上运费条件类型,结果又报M8 332错误。再改为加上COND_TYPE
清空COND_ST_NO and COND_COUNT。总算正常了。
但不知道后面的BAPI_INCOMINGINVOICE_PARK会不会报错。

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/1605/viewspace-743243/,如需转载,请注明出处,否则将追究法律责任。

请登录后发表评论 登录
全部评论

注册时间:2007-12-11

  • 博文量
    64
  • 访问量
    944245