
Overview:
Conversion Direction | Local Field | External Field | Conversion |
---|---|---|---|
B - Local | CRM_ITEM_GUID | ZZTESTPOSNR | B-Convesio Routine |
Initial Download of Condition Type:
Through transaction R3AS and objects DNL_CUST_CND, DNL_CUST_CNDALL all relevant customizing and condition types were loaded in CRM
Impement BADI:
It is required to give provision for the condition type to create Price Agreement in SAP CRM
2. Implement BADI "CND_MAP_CNV_FIELD" with filter CRM_ITEM_GUID. In this implementation (Conversion Method) Item GUID must be properly divided to Document and Item Number combination, because in ECC GUID does not exist.
Like as : CONCATENATE lg_vbeln lg_posnr INTO ev_target_value.
Maintain Condition Types to Allow Price Agreement replication (ECC):
Maintain the relevant condition types in customizing which are used in Price Agreements. This customizing is done to allow the price agreement to be replicated into relevant ECC condition tables. With this entries ECC understand that data is coming from CRM and not created in ECC. Following is the path:
Change Logical System for maintain condition types (ECC):
The maintained conditions types when it is transported into target system, relevant logical systems should be changed through transaction BDLS:
The concerned table where information is stored is MNTCNT.
Summary:
After all the steps are performed, create a price agreement with an Item of released status. Check the BDOC is green and there is no error. Check the relevant condition table in CRM for example CNCCRMPRCUS780 and correspoding ECC Table A780 for entries.
Also check Sales Contract Item in ECC that price agreement is displayed. If not, please check the check box "condition index" at condition type customizing.
Please feel free with your comment and suggestions. :smile:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.