Hi Sunil,
Let me give a short background info on warranty download from ERP to CRM:
The warranties in CRM and ERP are technically totally different. From the viewpoint of the
initial load in the CRM the product master needs to be available. The warranty is maintained as product and is assigned via a product reference to the component of the iBase. This warranty template needs to be assigned, this is a prerequisite for the initial load (check of start and end date) and later on if you want to assign a warranty to the iBase component.
If then an initial load is done from the ERP the warranty start and end date is checked and set in the CRM from the ERP data.
The warranty object from the ERP (master warranty) is not exchanged at all. This functionality isn't available.
The warranty start and end date is only checked when the equipment is downloaded the first time to the CRM. This is done either with an initial load in the setup or later when the equipment is created in the ERP. So the creation of the equipment is bound also with the warranty start and end date fields.
Now, with this background info, I wouldlike to add some info on the reply of Mr. Hasan.
He correctly pointed out that gc_warrenty_load is set to blank (INITIAL). But during equipment download system will read customizing information and set it to 'X' based on some settings. This happens with the below call stack:
READ_CUSTOMIZING (FORM)
CRM_CREATE_IBASE_FROM_EQUI
IF_EX_CRM_EQUI_LOAD~PERFORM_LOAD
It checks for object name 'EQUIPMENT' and R/3 table name 'BGMKOBJ'. So, this is not set in the BADI implementation. This should be set in Tx. R3AC1.
For general info on equipment download and what gets downloaded by default and its pre-requisites, please check the below doc:
Replication of Equipment Between SAP CRM and SAP ERP - Installed Base Management - SAP Library
Thanks,
Anindya