PO为啥不能CANCAL呢？急啊

lijinglu968

大家好：
      已批准过的PO，虽做了入库动作但全退货后，想把它取消掉，在‘采购汇总’界面操作，但提示如下图错误信息：


对这个PO单，做了以下操作：
1）第一次审批完后，采购员有修改过头信息，所以版本变成了1
2）后来物料入库后，先做退货，确定全部退完货了
3）在‘采购汇总’界面进行CANCAL，就提示上面的错误。

路过的朋友给解答下啊。。

wangzai2008

你的PO需要重新核准，才可以取消。
因为此时的PO已经对部分关键数据做过修改。

f1021378

如果是新做的订单，你打开后  虽然没有审批过 但是还是能够取消订单头的

lijinglu968

2# wangzai2008

您好，我试过重新批准，问题还是一样，现在的状态是‘已拒绝’，这个状态应也可以取消吧，但我还是不行。

apache2

这个问题发生的原因是现在这张PO和最原始的PO单上某些栏位数据修改过，系统让你恢复到最初始的PO状态。程序会检查很多表header,line,location之类的，他们都有个版本备份表。这form会调用一个数据库package来检查数据版本的差别，你在FORM里找到这个package，用工具trace一下，检查那些数据不同，改过来就行了。我碰到过的有行上税码，发运地点之类的。

xinyuliu

我碰到过这个问题，把版本进阶,approve后再做cancel就可以了

lijinglu968

问题解决了，上METALINK上查了下，是因为ORACLE PO 模块中这个订单的基表和文件归档表的数据不一致造成的，在CANCAL这个PO号时，系统会自动检查这两个表的数据是否一致，如果不同，则提示上面的错误，如果一样，则正常操作完成。
如果碰到我这个问题可到metalink网站上找下这个脚本：poarsynf.sql
本来想上传metalink上的相关页面信息的，最近这个网站我这上不了，如果大家碰到这个问题可到上面找找。

captain

good!

问题解决了，上METALINK上查了下，是因为ORACLE PO 模块中这个订单的基表和文件归档表的数据不一致造成的，在CANCAL这个PO号时，系统会自动检查这两个表的数据是否一致，如果不同，则提示上面的错误，如果一样，则正 ...
lijinglu968 发表于 2009-3-4 18:32

sunjinhai

Symptoms
When trying to Cancel a  Purchase Order(PO) or Release  the form gives error:

Please undo the changes to the document in the current revision before taking the cancel action.
You are trying to cancel a document that has been altered since its last archived revision.


STEPS
The issue can be reproduced at will with the following steps:
1)   In the Purchase Order Summary Form  query  the Purchase Order or Release
2)  Tools/ Cancel /Cancel PO  or Release and get the error message


Changes
Upgraded to 11.5.10
Cause
In 11.5.10 there was a new Enhancement done for the 'Cancel' Control action to Check the Archive Table before the cancel. The Check is to make sure for Approved Rows the Main and the Archive Table has the same Data and that there were not Changes which need to be communicate to the Supplier. When the Archive On is 'Communicate' The archive happens in a separate step so there can be Purchase Orders which are 'Approved' but the the main and the archive table are out of synchronization. In these cases the Cancel is not allowed to Happen unless the above changes are communicated to the Supplier by 'Printing' the Purchase Orders. Once this step is done the Archive of the Purchase Order happens and the Purchase Order will be eligible for cancel.

There are some Old Purchase Orders (created earlier to 11.5.10 ) where there are many Rows which were out of synchronization between the Main and the Archive table . These could be due to new columns being added. There could be many rows due to data fixed too where the Main and the Archive Table are out of Synchronization.



Solution
To implement the solution, please execute the following steps:

1-Navigate to Setup=>Purchasing=>Document Types.

2-Find in the Document Types the Standard Purchase Order type

3-Check the Archive on field : Is Archive set to 'Communicate' or set to 'Approve'


If the Archive is set to 'Communicate' you have to communicate the PO to the Supplier before you can use the Cancel Option. You can run the 'PO Output for Communicate' or 'Printed Purchase Order Report' (select 'Print Selection'-'All' and give the PO Number you want to communicate). This will create the Archive. Now you can cancel the PO.

If the Archive is set to 'Approve' you have to make the document authorization status ' Requires Reapproval' then REAPPROVE it  before you can use the Cancel Option. You can update/enter the value in the field 'Note To Supplier'. (Navigation for the field is Lines block --> Click on "More" tab.) This will change the revision number and status is set to 'REQUIRES REAPPROVAL'., Now APPROVE  the Purchase Order. Archival process will takes place here.

.

4- If  still receiving the same error message while trying to cancel the Purchase Order after completing the steps above:

4.1 Download and apply Patch 6243080

Apply the patch in a TEST environment, Patch will generate a datafix script ( poarsynf.sql )
4.2 Run the generated scripts in the same TEST environment :

4.3. Connect to SQL plus.
4.4. Run the fix script poarsynf.sql
- If you want to run the script for one PO or Release, please pass the appropriate
po_header_id or po_release_id respectively.

( you can get the po_header_id by executing the following SQL statement
Select po_header_id from po_headers_all where segment1=&PO_number; ) ** If you want the script to be ran for all the POs/Releases, then please comment out the lines that have the parameters &po_header_id and &po_release_id.


4.5  Once it is completed ensure there is no error reported.
4.6 Then validate the data.
4.7 Test the behavior (cancellation) in application to ensure that the data is correct.
4.8  Migrate the solution as appropriate to other environments.



5- If still unable to cancel the document after applying the generic datafix patch

Download and run the diagnostic scripts below.  Log a new SR and provide the output from the diagnostic scripts.

These scripts will determine the data that is not synchronized between the purchase order tables (po_headers_all, po_lines_all, po_line_locations_all and po_distributions_all)and the archive tables (po_headers_archive_all, po_lines_archive_all, po_line_locations_archive_all and po_distributions_archive_all ) for that purchase order.

zhaojeff

何必一定要cacel呢？手工将之直接关闭掉，不是更简单吗？

huangxf2008

回复 zhaojeff 的帖子

Cancel和close的意思是一样的吗？