CUSTOMER_REL

Adapter Object: CUSTOMER_REL有两个功能:

  • 同步Contact Person,以Relationship的方式
  • 同步Partner Function,同样以Relationship的方式

注意,像Ship-to,Bill-to等等,如果是自身的话(叫做self-reflection),在CRM中是不会产生Relationship的,因为CRM不允许self-reflection。而对于自定义的Partner Function,需要在CRM中配置:

  • Distribution of Partner Functions from SAP ECC into CRM
  • Distribution of Partner Functions from CRM into SAP ECC

针对self-reflection,其实在Define Partner Functions中Block选项就是干这个的,如果不勾选的话,意味着在Partner Determination过程中,可选自身作为任意的Partner Function。详见Note: 417022

在CRM中,self-reflection用BP Role来体现。但是CRM中,BP Role没有什么特殊功能,只是UI的集合,参见Note: 596334

再引用一段话:

The self reflexive partner function by design are not replicated to CRM
from R/3, because in the CRM system they do not make sense as per the
design and data model of the CRM system.

In R/3 when a customer is created in a particular sales area under a
particular account group self reflexive partner functions like
Ship-to-party, Bill-to-party and so on are added.

This information is represented in CRM in terms of roles because in CRM
partner functions refer only to the ones that a BP has with another BP
and not itself. All the information related to a BP in CRM are stored
in the BP data itself and never through partner functions.

Similarly, these partner functions will not be displayed in the
[RELATIONSHIPS] tab. Please note that self-reflecting partner
functions are not allowed in CRM because it’s physically not possible
for a Business Partner to have a relationship or a partner function
with himself. Such partner functions are subject of partner
determination process in CRM, and by default Ship-to-party, Payer and
Bill-to-Party functions are assumed for all Business Partners.
During data exchange such Partner Functions are simply ignored.

 

订单上Contact Person的地址

订单上Contact Person地址读取的顺序是这样的:

  1. The system determines all addresses of the contact person. The system uses the access sequence assigned to the contact person in the partner determination procedure to determine from where the contact person should be determined. For example, if the contact person should be determined from the activity partner, the system uses a possibly existing relationship address between contact person and activity partner if the document contains an activity partner.
  2. If this relationship address cannot be identified, the system uses any other relationship address.
  3. If no relationship address exists at all, the system uses the private address.

Via: Note 502447

Function Module:COM_PARTNER_ADDRESS_DETERMINE

 

月光光,照地堂

上周搭HU7701返深圳,B-6539,海航的新333飞机,飞机很好略过不谈。降落深圳后,放了一首童谣:月光光,照地堂,虾仔你乖乖瞓落床……顿时一阵暖流涌上心头,或者说像电了一下,因为对于广东人来说,这首歌单刀直入、最最直接地告诉你:回到家了。

没有哪个广东人,不是听这个旋律长大的。她不一定是你的摇篮曲,但却是一种情怀。这首童谣,在北京降落时听不会有这样的感触;北方人听,也不会有这种触动(请原谅我在此用这个传统的称呼,而想必你们也有自己的童谣)。所谓触景生情,真是此时此景恰到好处。

回家后查了一下,原来这首童谣用在海航的广州航线已经有一段日子,放的是“东山少爷”的版本。但在深圳航线我是第一次听见,但愿日后会继续采用。继续Google,“东山少爷”版本的童谣并非原版,而且其实也没有什么原版,关键在于版本太多,摘录Wiki的各版歌词如下:

月光光,照地堂,
蝦仔你乖乖瞓落床。
聽朝阿媽要趕插秧咯,
阿爺睇牛佢上山崗,啊。
蝦仔你快高長大咯,
幫手阿爺去睇牛羊,啊。
月光光,照地堂,
蝦仔你乖乖瞓落床。
聽朝阿爸要捕魚蝦咯,
阿嫲織網要織到天光,啊。
蝦仔你快高長大咯,
划艇撒網就更在行。
月光光,照地堂,
年三十晚,摘檳榔,
五穀豐收堆滿倉囉,
老老嫩嫩喜喜洋洋,啊…
蝦仔你快啲眯埋眼囉,
一覺瞓到大天光,啊…

Via Wiki

最后还要说再说一点,广东的文化有赖广东人自己去传承。

 

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.  >>

附件是一个例子

Inheritance of appointments from header level to item level

Inheritance of appointments from header level to item level. The inheritance process happens as follow:

  • If the appointment is assigned with a rule in the corresponding item dates profile, then the date is calculated according to the rule, and hence, is not copied from the header corresponding appointment
  • If the appointment is not assigned with a rule in the corresponding item dates profile, then the date is inherited from the header to the item level. In this case, it is possible to bypass this process by using the BADI CRM_APPOINTMENT_BADI, method CRM_APPOINTMENT_INHERIT.
  • In the case where the header and item have the same dates profile assigned, then the inheritance process is always executed independently from the appointment being assigned with a rule in the profile.

Note: 925790

PS. 身边的IBM顾问,很有钻研精神

Logon Language

没想到这也能成为一个话题,只能侧面反映SAP考虑得很多。

首先,看看CRM Web UI登陆页面的语言是确定的优先级:

  1. SICF的设置
  2. HTTP Request的language参数
  3. 浏览器默认语言的设置
  4. SU01用户的设定

Via SAP Help

然后,如需调整Web UI登陆的可选语言(即下拉框内容),可通过报表程序RSCPINST。

详见Notes: 42305, 73606