背景:
Recurring Inspection是传统ERP中QM常用的功能,针对该EWM为Decentralized布署,如果是Embedded的,也差别不大(Decentralized有自己的IOT5的检验批,与ERP里的检验批为两个单据;但Embedded是共享一个检验批)。
SAP也是出一个Notes: 3120374 描述了QA07运行时,是不考虑EWM管理的库存地点。
大致做法就是用EWM里程序:/SCWM/R_STOCK_TYPE_CHANGE来schedule一个job,生成EWM的IOT5的检验批,在Decentralized布署下,这个检验批会同步到ERP中,生成ERP的检验批。
配置:
批次要激活,增加一个特征:LOBM_QNDAT (next inspection date)并分配到你的批次特性里,
EWM设置:
后台配置如下:
增加一条记录:
Inspection Type | IOT | Insp Proc. | Number Range | Decision Code Group | Decision Code Group Item | Indep. Stk Ty. |
1709 | 5 | 1 Recurring Inspection | SIOT5 | EWMIOT5 | EWMIOT5 |
ERP设置:
Maintain Inspection Type (ERP)
IMG > Quality Management > Quality Inspection > Inspection Lot Creation > Maintain Inspection Types
也同样创建一个1709的检验类型:
Maintain Inspection Lot Origins and Assign Inspection Types (ERP)
IMG: Quality Management→Quality Inspection→Inspection Lot Creation→ Maintain Inspection Lot Origins and Assign Inspection Types
Define Default Values for Inspection Type (ERP)
IMG: Quality Management→Quality Inspection→Inspection Lot Creation→Define Default Values for Inspection Type
Inspection Type 1709
100% Inspection selected
Skips allowed selected
Automatic usage decision selected
Q score procedure 06 From usage decision code
Avg. insp. duration 2
Edit Code Groups and Codes (ERP)
IMG: Quality Management → Quality Inspection → Inspection Lot Completion → Edit Code Groups and Codes for Usage Decisions
Choose in Dialog Structure Code Groups for Usage Decision.
加一条记录:
Code group | Short text | Status |
---|---|---|
EWM | UD Codes integrated with EWM | 2 Released |
基于这条记录增加以下记录:
参考:
3120374 Notes内容:
Furthermore, here is the Application Help for 'Recurring Inspection' in EWM 9.2.
The typical process is to create a batch from the EWM delivery. The next inspection date is calculated as production date (or system date) + inspection interval (which is a new field of the product and is transferred by cif from the ERP material quality management tab). The calculated next inspection date is stored in the batch master.
With report /SCWM/R_STOCK_TYPE_CHANGE, the stocks which are expired are posted to quality inspection of type IOT5. The inspection lot is created in ERP and decided in ERP. When the decision is done, the next inspection date is re-calculated as decision date + inspection interval and stored again in the batch master.
It is not planned to down port the recurring inspection functionality to SAP EWM 9.1 or below.
Report /SCWM/R_STOCK_TYPE_CHANGE is used for recurring inspection in EWM including S/4 HANA embedded EWM scenario, please see also the following documentations:
'Recurring Inspections'
- new feature in 1709:
SAP Help Portal
- further info in 1909:
SAP Help Portal