SAP秀才-《MM学习指南》操作记录--- 4.补-采购审批策略的设置
2010-12-19 16:17
363 查看
注:此文章只作为本人学习SAPtarget=_blank class=link_tag>SAP的记录,仅供文档备份用途!
操作环境:SAP IDES 4.71
注: ZYF制作,转载请标注出处:ZYF-SAP童生http://blog.vsharing.com/ZYF/
SAP秀才的博客:http://scola.wang.blog.163.com/
为了能将SAP秀才-《MM学习指南》的第5篇:“计划协议及交货计划”做下去,需要在系统里设置采购审批策略。这一篇主要讲怎样在系统里设置采购审批策略的。
为了简便,策略也是一切从简,思路就是将是:所有是属于“1100”的采购组织做的采购订单(PO)都要经过审批。审批者可以指定任一用户。简单起见,本篇设置审批者仍为本人^_^!
SE11查看表:CEKKO,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image002_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image002_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image004_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image004_thumb.jpg)
选定采购组织EKORG作为审批设置的特性要素。当然如果需要的的话也可以将其他作为审批特性要素。
1.创建特性Characteristic(Tcode:CT04)
Path: IMG->Material Management->Purchasing->Purchase Order->Release Procedure for Purchase Orders->Edit Characteristic
后台->物料管理->采购->采购订单->采购订单的下达过程->编辑特性
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image006_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image006_thumb.jpg)
先输入第一个特性:Z_PUR_ORG,用它来进行采购组织的限定,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image008_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image008_thumb.jpg)
“多值”表示该审批特性可是适用于多个采购组织,而“单一值” 则只能适用于唯一的采购组织。切换到“附加数据”标签页,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image010_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image010_thumb.jpg)
Table Name = CEKKO ,Field Name = EKORG,Enter,系统提示:“取自ABAP字典的格式数据”,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image012_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image012_thumb.jpg)
。保存。
2.创建类Class(Tcode:CL02)
Path: IMG->Material Management->Purchasing->Purchase Order->Release Procedure for Purchase Orders->Edit Class
后台->物料管理->采购->采购订单->采购订单的下达过程->编辑类
类名:ZFRG_EKKO_ORG
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image014_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image014_thumb.jpg)
切换到“特性”标签页
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image016_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image016_thumb.jpg)
与之前创建的“特性”关联。保存。
3.定义审批程序(Tcode:)
Path: IMG->Material Management->Purchasing->Purchase Order->Release Procedure for Purchase Orders->Edit Class
后台->物料管理->采购->采购订单->采购订单的下达过程->定义采购订单的审批过程
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image018_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image018_thumb.jpg)
双击“批准组”,新条目:
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image020_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image020_thumb.jpg)
创建批准组:P1,关联类别:ZFRG_EKKO_ORG,保存。
说明一下,审批组可以理解为审批策略的一个集合,在后面创建了审批策略之后我们可以回过头来看看这种理解是否正确。
接下来进入“批准代码”,为“批准组”:创建审批人:PU,双击“批准代码”,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image022_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image022_thumb.jpg)
假设PO有两种状态:Blocked(冻结)和Released(已审批),进入“批准标识”:
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image024_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image024_thumb.jpg)
接下来将要创建审批策略,审批策略可以理解为审批路径,这里创建一个自我审批的路径,双击“批准策略”,新条目:
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image026_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image026_thumb.jpg)
指定“批准代码”:P1。实际上在这里没有必要把审批人具体化,这里可以理解为自己。
进入“批准先决条件”,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image028_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image028_thumb.jpg)
,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image030_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image030_thumb.jpg)
这里无须指定任何信息,“继续”即可,
进入“批准状态”,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image032_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image032_thumb.jpg)
,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image034_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image034_thumb.jpg)
这里的意思是PO初始创建状态为Blocked(冻结),P1审批之后状态转入Released(已审批)。
接下来进入“分类”,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image036_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image036_thumb.jpg)
,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image038_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image038_thumb.jpg)
保存。
4.创建角色Role(Tcode: PFCG)
Path: Tools->Administration->User Maintenance->Role Administration->Roles
前台->工具->系统管理->用户维护->角色管理->PFCG-角色
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image040_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image040_thumb.jpg)
创建一个角色:CUX_YUFENG :
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image042_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image042_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image044_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image044_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image046_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image046_thumb.jpg)
点击Change Authorization Data,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image048_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image048_thumb.jpg)
,做如下设置,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image050_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image050_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image052_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image052_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image054_thumb.jpg)
保存之后在工具栏中点击Generate
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image056_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image056_thumb.jpg)
(Shift+F5),此时界面上Status由Saved转变为generated,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image058_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image058_thumb.jpg)
,注意,执行了Generate之后不能Save,否则这个Authorization profile将不起作用,返回,此时的界面转为:
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image060_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image060_thumb.jpg)
系统产生了Profile:T-C1960001,状态=已经生成权限参数文件。
5.给用户分配角色(Tcode:SU01):
SU01:
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image062_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image062_thumb.jpg)
给用户 :YUFENG 分配角色:CUX_YUFENG,保存。OK!
现在做 采购订单时,只要采购组织为 1100 的采购订单都需要审批了,审批人为:YUFENG 。
【注意:在此审批策略配置未完成前做的采购订单是不能使用这个策略来进行审批的,ZYF-SAP童生做了好多次才明白过来,浪费了好多时间】。
SAP秀才-《MM学习指南》操作记录--- 4.补-采购审批策略的设置(完)
补:
Purchase Release Strategy(采购审批策略)
如果想需要PR或者其他采购文档(PO,contract, scheduling agreement, request for quotation (RFQ)等)在一定条件下被审批,就需要用到SAP的审批策略。
对于PR的审批可以在item级别也可以再total级别,并且有带classification和不带classification两种,不过不带classification的只能在total级别审批。我们接下来都以PO为例讲解。
Release Condition(Characteristics class)
一个PO必须满足审批条件,才会进入审批流程,比如采购总价值超过1万元,或者采购组001采购的物料等。SAP采用classification系统进行审批条件的配置。
首先通过CT04定义审批条件的要素,比如采购组或者总价值,我们可以在表CEKKO中找到所有可以被利用的字段,如果不能满足需求,就需要enhancement M06E0004
之后CL02定义class,也就是将各个审批要素组合在一起,组成一个完整的审批条件。比如采购组001采购金额大于5K采购组002采购金额大于10K
Release Strategy overview
审批策略是一个总的审批流程,可以在一个审批策略下定义release code,我们最多可以定义8个release code。定义审批策略包括定义定义release group, release code, release indicator等步骤
Release Group
同一个release group具有相同的审批level,比如我提到的001采购组大于5K的金额需要审批,而002采购组大于10K的金额需要审批,这就需要连个不同的审批组,而如果有一个第三个部门,但是依然用采购组001和大于5K的policy,那么它可以与第一组共享审批组。
我们为审批组分配Class
Release Code
Release Code我们可以理解为现实中与整个审批流程相关的人,每个审批者都会审批相应的release code。如果配置了workflow,可以将他们与workflow结合起来用,审批自动到达他们的task中。
Release Indicator
这一步骤实际是定义审批中的各种状态和在此状态时系统的反应。
比如我们这里有2个状态,在审批流程中都会是状态1,也就是没有release,可以更改PO并且不会触发新的审批流程,或者是在触发新的审批流程的值状态时进行新的审批等。后面的%value change字段限制了字段更改的最大范围,超过了一定百分比系统会产生错误信息。
Release Strategy
最后一步定义审批流程。Release codes我们看到最多输入8个,我们按照审批顺序输入。
Release prerequisites定义的是每个审批流程需要的前提,很简单,一般的审批都是一步一步进行的。都会勾成下面的样子,也就是02需要01最为条件。
Release status定义每一步被审批后,PO的状态,我们定义只有01 02都被通过了,才会进入最终的2状态
Classification相当于定义这个审批策略被触发的条件。
操作环境:SAP IDES 4.71
注: ZYF制作,转载请标注出处:ZYF-SAP童生http://blog.vsharing.com/ZYF/
SAP秀才的博客:http://scola.wang.blog.163.com/
为了能将SAP秀才-《MM学习指南》的第5篇:“计划协议及交货计划”做下去,需要在系统里设置采购审批策略。这一篇主要讲怎样在系统里设置采购审批策略的。
为了简便,策略也是一切从简,思路就是将是:所有是属于“1100”的采购组织做的采购订单(PO)都要经过审批。审批者可以指定任一用户。简单起见,本篇设置审批者仍为本人^_^!
SE11查看表:CEKKO,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image002_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image002_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image004_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image004_thumb.jpg)
选定采购组织EKORG作为审批设置的特性要素。当然如果需要的的话也可以将其他作为审批特性要素。
1.创建特性Characteristic(Tcode:CT04)
Path: IMG->Material Management->Purchasing->Purchase Order->Release Procedure for Purchase Orders->Edit Characteristic
后台->物料管理->采购->采购订单->采购订单的下达过程->编辑特性
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image006_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image006_thumb.jpg)
先输入第一个特性:Z_PUR_ORG,用它来进行采购组织的限定,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image008_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image008_thumb.jpg)
“多值”表示该审批特性可是适用于多个采购组织,而“单一值” 则只能适用于唯一的采购组织。切换到“附加数据”标签页,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image010_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image010_thumb.jpg)
Table Name = CEKKO ,Field Name = EKORG,Enter,系统提示:“取自ABAP字典的格式数据”,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image012_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image012_thumb.jpg)
。保存。
2.创建类Class(Tcode:CL02)
Path: IMG->Material Management->Purchasing->Purchase Order->Release Procedure for Purchase Orders->Edit Class
后台->物料管理->采购->采购订单->采购订单的下达过程->编辑类
类名:ZFRG_EKKO_ORG
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image014_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image014_thumb.jpg)
切换到“特性”标签页
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image016_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image016_thumb.jpg)
与之前创建的“特性”关联。保存。
3.定义审批程序(Tcode:)
Path: IMG->Material Management->Purchasing->Purchase Order->Release Procedure for Purchase Orders->Edit Class
后台->物料管理->采购->采购订单->采购订单的下达过程->定义采购订单的审批过程
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image018_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image018_thumb.jpg)
双击“批准组”,新条目:
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image020_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image020_thumb.jpg)
创建批准组:P1,关联类别:ZFRG_EKKO_ORG,保存。
说明一下,审批组可以理解为审批策略的一个集合,在后面创建了审批策略之后我们可以回过头来看看这种理解是否正确。
接下来进入“批准代码”,为“批准组”:创建审批人:PU,双击“批准代码”,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image022_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image022_thumb.jpg)
假设PO有两种状态:Blocked(冻结)和Released(已审批),进入“批准标识”:
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image024_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image024_thumb.jpg)
接下来将要创建审批策略,审批策略可以理解为审批路径,这里创建一个自我审批的路径,双击“批准策略”,新条目:
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image026_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image026_thumb.jpg)
指定“批准代码”:P1。实际上在这里没有必要把审批人具体化,这里可以理解为自己。
进入“批准先决条件”,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image028_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image028_thumb.jpg)
,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image030_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image030_thumb.jpg)
这里无须指定任何信息,“继续”即可,
进入“批准状态”,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image032_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image032_thumb.jpg)
,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image034_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image034_thumb.jpg)
这里的意思是PO初始创建状态为Blocked(冻结),P1审批之后状态转入Released(已审批)。
接下来进入“分类”,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image036_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image036_thumb.jpg)
,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image038_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image038_thumb.jpg)
保存。
4.创建角色Role(Tcode: PFCG)
Path: Tools->Administration->User Maintenance->Role Administration->Roles
前台->工具->系统管理->用户维护->角色管理->PFCG-角色
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image040_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image040_thumb.jpg)
创建一个角色:CUX_YUFENG :
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image042_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image042_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image044_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image044_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image046_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image046_thumb.jpg)
点击Change Authorization Data,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image048_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image048_thumb.jpg)
,做如下设置,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image050_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image050_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image052_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image052_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image054_thumb.jpg)
保存之后在工具栏中点击Generate
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image056_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image056_thumb.jpg)
(Shift+F5),此时界面上Status由Saved转变为generated,
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image058_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image058_thumb.jpg)
,注意,执行了Generate之后不能Save,否则这个Authorization profile将不起作用,返回,此时的界面转为:
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image060_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image060_thumb.jpg)
系统产生了Profile:T-C1960001,状态=已经生成权限参数文件。
5.给用户分配角色(Tcode:SU01):
SU01:
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image062_thumb.jpg)
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image062_thumb.jpg)
给用户 :YUFENG 分配角色:CUX_YUFENG,保存。OK!
现在做 采购订单时,只要采购组织为 1100 的采购订单都需要审批了,审批人为:YUFENG 。
【注意:在此审批策略配置未完成前做的采购订单是不能使用这个策略来进行审批的,ZYF-SAP童生做了好多次才明白过来,浪费了好多时间】。
SAP秀才-《MM学习指南》操作记录--- 4.补-采购审批策略的设置(完)
补:
Purchase Release Strategy(采购审批策略)
如果想需要PR或者其他采购文档(PO,contract, scheduling agreement, request for quotation (RFQ)等)在一定条件下被审批,就需要用到SAP的审批策略。
对于PR的审批可以在item级别也可以再total级别,并且有带classification和不带classification两种,不过不带classification的只能在total级别审批。我们接下来都以PO为例讲解。
Release Condition(Characteristics class)
一个PO必须满足审批条件,才会进入审批流程,比如采购总价值超过1万元,或者采购组001采购的物料等。SAP采用classification系统进行审批条件的配置。
首先通过CT04定义审批条件的要素,比如采购组或者总价值,我们可以在表CEKKO中找到所有可以被利用的字段,如果不能满足需求,就需要enhancement M06E0004
之后CL02定义class,也就是将各个审批要素组合在一起,组成一个完整的审批条件。比如采购组001采购金额大于5K采购组002采购金额大于10K
Release Strategy overview
审批策略是一个总的审批流程,可以在一个审批策略下定义release code,我们最多可以定义8个release code。定义审批策略包括定义定义release group, release code, release indicator等步骤
Release Group
同一个release group具有相同的审批level,比如我提到的001采购组大于5K的金额需要审批,而002采购组大于10K的金额需要审批,这就需要连个不同的审批组,而如果有一个第三个部门,但是依然用采购组001和大于5K的policy,那么它可以与第一组共享审批组。
我们为审批组分配Class
Release Code
Release Code我们可以理解为现实中与整个审批流程相关的人,每个审批者都会审批相应的release code。如果配置了workflow,可以将他们与workflow结合起来用,审批自动到达他们的task中。
Release Indicator
这一步骤实际是定义审批中的各种状态和在此状态时系统的反应。
比如我们这里有2个状态,在审批流程中都会是状态1,也就是没有release,可以更改PO并且不会触发新的审批流程,或者是在触发新的审批流程的值状态时进行新的审批等。后面的%value change字段限制了字段更改的最大范围,超过了一定百分比系统会产生错误信息。
Release Strategy
最后一步定义审批流程。Release codes我们看到最多输入8个,我们按照审批顺序输入。
Release prerequisites定义的是每个审批流程需要的前提,很简单,一般的审批都是一步一步进行的。都会勾成下面的样子,也就是02需要01最为条件。
Release status定义每一步被审批后,PO的状态,我们定义只有01 02都被通过了,才会进入最终的2状态
Classification相当于定义这个审批策略被触发的条件。
![](http://blog.vsharing.com//Uploads/UserDirs/4/1204/481312/WindowsLiveWriter/SAPMM4_132B3/clip_image054_thumb.jpg)
相关文章推荐
- SAP 《MM学习指南》操作记录---- 采购合同
- SAP 采购审批设置--(详细)
- SAP采购订单审批记录增强
- SAP采购审批策略定义及介绍
- SAP 《MM学习指南》操作记录----寄售业务(创建寄售合同、订单、收货等操作)
- SAP《MM学习指南》操作记录----仓库盘点
- SAP 《MM学习指南》操作记录----库存盘点时库存的冻结
- SAP 《MM学习指南》操作记录---- 计划协议及交货计划
- sap 采购审批策略解析
- SAP 采购订单PO基于采购金额的审批策略配置
- SAP《MM学习指南》操作记录----仓库盘点
- SAP采购申请审批记录增强
- SAP采购审批策略 purchase release strategy
- SQL Server 2012设置某用户对某些表的记录限制其删除操作
- SAP中采购订单历史记录类型文本
- 定义采购订单的审批策略(包括批准组、批准代码、批准标识)
- SAP审批策略相关表
- 采购申请审批策略增强
- MySQL设置记录操作日志
- sap审批策略解析