姓名格式

这个Function: ADDR_PERSON_NAME_FORMAT决定了BP姓名输出的格式,如果BP没有维护姓名格式,则取Standard的:

* Standardaufbereitungsregel:
line_of_rule 01 title.
line_of_rule 02 title_aca1.
*392i+
line_of_rule 03 title_sppl.
line_of_rule 04 name_first.
line_of_rule 05 initials.
line_of_rule 06 prefix1.
line_of_rule 07 name_last.

SAP GUI里头可以通过用户参数NAMEFORMAT_COUNTRY设置默认值,CRM Web UI里头就没这只歌仔唱了。

Data Determination in Access

近日在看SCM620 Pricing,Unit 4当中的Data Determination in Access只有数页,但却相当重要。不过SCM620简写得太厉害了,建议看Help文档。之所以重要,是因为原来Pricing在Access层面(Access Sequence中的一条称为Access)也是可以玩的,而且很强大。

Data Determination in Access主要用于这样的场景:取一个不在订单上的值用于Pricing。解决方法很多,SAP提供的方法是:

  • 第一步,Data Determination,就是获取这个值;
  • 第二步,Data Use,就是将上面得到的值用于Pricing中。

而根据值的获取方式,有三招:

  1. 使用KOMPAZD
  2. 使用Routines
  3. 针对Sales Deals的处理方式

上述文字比较抽象,其核心是我们不但可以用Access访问Condition Record获取价格、折扣,Condition Record还可以返回字符,而这个返回字符可以用于后续Condition Type去做Pricing。如果后续的Condition Type对应的Access Sequence直接使用这个返回值,那就是第一招,这招你不需要写Code,往KOMPAZD加Field(就是返回值),配Condition Table和Access Sequence就可以了。如果返回值不是直接用于后续的Access Sequence,那就是第二招,在Requirement里写Routine。Sales Deals不懂略过。

想象一下Condition Record可以返回字符,那它就不是条件记录了,而是一个Z表,这里有太多文章可以做了。

注意:Data determination at the level of access cannot be executed in SAP CRM.  >>

附件是一个例子

转:Road ahead for SAP consultants

SDN上的一篇文章,金融海啸下SAP顾问如何自处。

3. Size matters

This one went back and forth between me and several people, including an exchange of ideas with Jon Reed here on SDN. Majority of the people I spoke to have the idea that more and more companies will give more business to the big Tier 1 companies, since the bigger companies are percieved as a better insurance against risk. This would probably lead to more hiring at these compnies. Flip side – it probably wont pay you like an independent gig.

7. CRM and BI are dandy

Customer is king , but probably this assumes greater significance in bad times. From what I can see – from own experience and from the information from all around, I am convinced that more and more people are spending money on CRM. The much nicer UI in CRM2007 itself is probably worth the upgrade. It is also apparent that lots of BI projects are around – and my theory is that companies probably are taking a more data driven approach to decision making to reduce risk in the bad economy.

via: SDN – Road ahead for SAP consultants

外包物料成本核算时的供应商确定

一外包物料有两个供应商(采用了配额管理),进行成本核算(CK11N),该选择哪个供应商呢?在成本核算变式PPC1 -> 估价变式Valuation variant -> 外包Subcontracting页签 -> 采购中的报价Quotation in Purchasing,可选:实际配额安排Actual / 计划的配额安排Planned,它们代表什么呢?

计划安排就是配额比例,若选择计划安排,则成本核算时采用配额比例的供应商;实际配额则是算出来的,就是Quota rating,计算公式:Quota rating = Quota-allocated quantity (+ quota base quantity) / Quota。若选择实际安排,则成本核算时采用Quota rating的供应商。

至于完成的供应商决定过程,可参考SAP Library

Determining the Vendor

Total Planning & Single-Item, Multi-Level Planning

感觉上Total Planning就是Multi-Item, Multi-Level Planning,“多项多层”呗。事实上没什么“多项多层”,“总计划”和“单项多层计划”在多工厂计划中,对层的解释是不同的。总计划的多层是不跨工厂的,而单项多层的计划是跨工厂的,MRP运算一直展开到物料需求的底层。(以上针对无MRP Area)

对此,SAP Library有清楚的解释。

Single-Item, Multi-Level Planning:
If there are components in the BOM that are procured by stock transfer or production in another plant, then in single-item, multi-level planning the other plant is used for further planning.

Total Planning:
With stock transfer or production in alternative plant, the system creates the corresponding planning file entries in the alternative plant. If the alternative plant is included in the scope of planning, the system continues to plan the materials in the alternative plant. If the alternative plant is not included in the scope of planning or if you plan for a single plant without entering a scope of planning, the system does not plan in the alternative plant.

批量删除生产订单

这个问题有点怪,一般的生产订单批操作都通过COHV完成,偏偏就是没有删除订单(打删除标记DLID)。其实SAP有批量删除生产订单的程序,只是没有归属到COHV中,而是归属到归档功能中。这也好理解。

程序:PPARCHP1。SE38里运行吧,还有测试功能呢。嫌麻烦的话,自行分配一个事务码吧。

Posted in SAP