导读
INTRODUCTION
非必填设置:ECP主数据同步的时候,经常遇到一个问题,就是ECP报错,但是这个字段两边的ecp顾问与sf顾问都觉得没实际意思,觉得没有传输的必要性,这个时候我们就可以考虑非必输的字段不必输,ECP集成其实没BIB集成的时候灵活,没有默认值填充,ecp其实也有每个信息类型控制字段不必输。
作者:vivi,来源:osinnovation。
一、故事背景:
其实就是0185信息类型,有个申请状态字段,但是这个字段其实没什么实际含义,因为能从sf传输过来,肯定是已经生效数据,这个状态多ecp就是多此一举,所以ecp去做增强不划算,sf弄一个字段去对应也不划算,所以想到的解决方案是,能不能不集成这个字段过来。因为原来bib集成的时候是可以与配置的,PTP集成基本都是代码固定写死的,所以最开始觉得应该不能配置。
消息号是 HRSFEC_SERVICES130。
二、解决方案:
其实bib与ptp是一样的,都是可以控制字段必输的选项,例如这个状态的字段,我现在想设置成非必输,可以用未使用的打上勾,那这样系统集成就会放弃这个字段集成。系统就不会报错。
sap的note是2489963,可以看出这个note有相关增强与配置表的地方。
These are the tables and BAdI that impact in the infotype framework. Note: The order indicates the prevalence of the customizing
1. The BAdI HRPAD00INFTYBL method METADATA_COMPUTATIONS (Parameter structure FIELD_METADATA_TAB and its field MANDATORY).
2. The Customizing view V_T588MFPROPC for customer definitions (if field is not Fixed in standard view)
3. The Customizing view V_T588MFPROPS for SAP definitions (Cannot be modified by customers)
So in case the standard customizing of V_T588MFPROPS doesn´t cover your needs, you should try to configure the field properties with the customer view V_T588MFPROPC. In the cases where the standard configuration (V_T588MFPROPS) has been fixed (FIXED column has been flagged) the BAdI can be used to override the pre-delivered customizing.
Warning: Evaluate carefully for which fields are the properties changed. Making optional some fields like for example ‘Payroll Area’ that are needed in subsequent processes could generate problems or inconsistencies. Consistency must be kept along the infotypes data.
See Also
Hint: The behavior of the new infotype framework can be simulated by using the transaction PUIT_UI