单据转换.说明.合并下推
【概述】说明下合并下推的常见问题
【常见问题】
<1>在不修改数据包时,字段的目标值、关联关系仅依赖于转换时的源单
![Image_20230206160645.webp](/download/0100486fd879303a4a7594b9291c42a8eea1.webp)
常见的如源单编号
![Image_20230206160746.webp](/download/010079ef7d21076c427cb947e6105d728c72.webp)
业务流上查
![1675670963448.webp](/download/0100cb3ba273b49b419a8bfcbe3f6af44374.webp)
<2>修改控制字段的值,不会改变关联关系(link行没有减少),仅改变源单分配关系
当我手工分配采购数量的来源时(参考:[合并下推分配](https://wenku.my7c.com/article/272008385389184512?productLineId=1)),源单编号不会刷新,还是来源多个上游,源单编号不会重新计算,关联关系也不会
![1675671062841.webp](/download/0100ca47210acf214fdbaf194a8374b04eae.webp)
业务流上查
![1675670963448.webp](/download/0100cb3ba273b49b419a8bfcbe3f6af44374.webp)
<3>上游单据全流程跟踪、下查时,看到的是存在关系的分录,而非有分配数值的分录
采购订单与采购申请单132没有数额分配,但是通过采购申请单132,下查依然能够看到采购订单
![1675671350261.webp](/download/01001fe53c9b49d5478184d2aa4880943efc.webp)
<4>在合并下推时,不能直接通过下查列表和单据数量比对比较
由于存在下推了没有分配数额的逻辑,因此下查的汇总值>=单据的数量,当且仅当该单据为直接下推时取等号。
如下图所示,采购申请单132重新再下推一个采购订单,发现总额为110超额了,但实际上并非超额
![1675671615054.webp](/download/01002ec09d3fd92f40d583c3ca1da162d152.webp)
```sql
--<0>关联关系查询
select sbill.fbillno,sEntry.fseq,node.*,tbill.fbillno from T_PUR_Requisition sbill
left join T_PUR_ReqEntry sEntry on sbill.fid = sEntry.fid
left join t_bf_instanceentry node on sEntry.fentryid = node.fsid and node.fstablename = 'T_PUR_ReqEntry' and node.fttablename = 't_PUR_POOrderEntry'
left join t_PUR_POOrderEntry tEntry on tEntry.fentryid = node.ftid
left join t_PUR_POOrder tBill on tBill.fid = tEntry.fid
where sbill.fbillno = 'CGSQ000132'
```
![1675672625166.webp](/download/0100bb84ba2b849849079f24cd1eb95bcda0.webp)
```sql
--<1>关联关系 结合分配额查询
select sbill.fbillno,sEntry.fseq,node.*,tbill.fbillno,tlk.fbaseunitqty as '分配值',tlk.fbaseunitqtyold as '分配上限' from T_PUR_Requisition sbill
left join T_PUR_ReqEntry sEntry on sbill.fid = sEntry.fid
left join t_bf_instanceentry node on sEntry.fentryid = node.fsid and node.fstablename = 'T_PUR_ReqEntry' and node.fttablename = 't_PUR_POOrderEntry'
left join t_PUR_POOrderEntry tEntry on tEntry.fentryid = node.ftid
left join t_PUR_POOrder tBill on tBill.fid = tEntry.fid
left join t_PUR_POOrderEntry_lk tlk on tEntry.fentryid = tlk.fentryid and tlk.fsid = sEntry.fentryid
where sbill.fbillno = 'CGSQ000132'
```
![1675672668283.webp](/download/0100fdd47bd991254debbf277b06fe8e4c1a.webp)
```sql
--<2>关联关系 结合分配额查询
select sbill.fbillno,sEntry.fseq,node.*,tbill.fbillno,tlk.fbaseunitqty as '分配值',tlk.fbaseunitqtyold as '分配上限' from T_PUR_Requisition sbill
left join T_PUR_ReqEntry sEntry on sbill.fid = sEntry.fid
left join t_bf_instanceentry node on sEntry.fentryid = node.fsid and node.fstablename = 'T_PUR_ReqEntry' and node.fttablename = 't_PUR_POOrderEntry'
left join t_PUR_POOrderEntry tEntry on tEntry.fentryid = node.ftid
left join t_PUR_POOrder tBill on tBill.fid = tEntry.fid
left join t_PUR_POOrderEntry_lk tlk on tEntry.fentryid = tlk.fentryid and tlk.fsid = sEntry.fentryid
where sbill.fbillno = 'CGSQ000132' and tlk.fbaseunitqty>0
```
![1675672700849.webp](/download/01006a13df1c32e54dec9af02a82ad548e2b.webp)
单据转换.说明.合并下推
【概述】说明下合并下推的常见问题【常见问题】<1>在不修改数据包时,字段的目标值、关联关系仅依赖于转换时的源单![Image_20230206160645....
点击下载文档
本文2024-09-16 18:32:40发表“云星空知识”栏目。
本文链接:https://wenku.my7c.com/article/kingdee-k3cloud-22839.html
您需要登录后才可以发表评论, 登录登录 或者 注册
最新文档
热门文章