采购领域(MM-PUR)与审批程序有关的常用Notes和KBAs

[yang_bai]

• 一般性问题: 用户对于审批程序的常见问题比如审批过程中涉及哪些权限，审批特性值里面的空白符号会被识别吗
                      等等。还有关于Table和配置的问题，可以给用户前期配置审批程序一定的参考。
  
  493900 - FAQ: Release Strategy
  365604 - Release strategies in purchasing
  325478 - Refs to table fields for chars. for release strat.
  1920498 - Release strategy is limited to 8 release codes
• 移送:  很多客户是先在测试机或者开发机上配置了审批程序，调试之后再移送到生产机。以下的Note/KBA给出了
            详细的移送步骤和常见问题的解答。
  
  86900 - Transport of Release strategies (OMGQ,OMGS)
  1929514 - Release Strategy does not work after transport
  799345 - Transport of release strategy disabled
• 审批手续和版本: 以往在一些客户问题中，发现当版本作为特性值维护在审批手续中时容易出现各种问题。以下的
                              KBA给出了部分问题的解决方法。
  
  1961482 - Reset release strategy when version number is set as Characteristic in Customizing
  1961585 - Release strategy is not triggered when version number is set as a Characteristic
         
                                        
• 在采购申请/采购订单中的取消和重置:  这些是客户提问最多的环节。已经生效的审批手续在某个操作之后自动
                                                               重置了，或者本该重置的手续还维持着原样，还有取消和重置审批手续
                                                               对其他功能的影响等，都可以在下面的Note/KBA中找到答案。
  
  1770572 - Purchase requisition release strategy is not reset after executing T-Code ME56 or ME57
  2083233 - System allows cancel a release strategy after goods receipt
  1793567 - Resetting release code in release strategy affects other higher level release codes set in customizing
                   under prerequisite.
  2087860 - Not able to cancel release strategy after PO was printed
  662993 - Resetting a release that already took place

• 在采购申请和采购订单中的决定: 当用户维护了特性值配置好了审批程序后，发现在创建单据的时候没有相应的
                                                       审批程序出现时，可以参照下面Note/KBA中介绍的方法排除故障，解决问题。
  
  1497235 - Release strategy is not determined for Purchase Requisition in t-code ME51(N)/ME52(N) or Purchase
                   Order in t-code ME21(N)/ME22(N) ℹ
  2105882 - Deleted purchase order still available for approval
  1888495 - Release strategy does not trigger with future price