Errors occur when you try to create or change condition records using BAPI_PRICES_CONDITIONS.
Some of the issues are as follows.
1. No change pointers are generated.
2. A deletion indicator set in ERP is not replicated in the CRM system.
3. The validity dates are not transferred.
4. Condition records with overlapping validity periods are created.
You should not use BAPI_PRICES_CONDITIONS to update the condition records as the status of the FM is still ‘Not released’.
Use only those BAPIs that are listed in BAPI explorer. These are the BAPIs released by SAP for public use.
The function module BAPI_PRICES_CONDITIONS is exclusively used for SAP internal purposes.
When you use this function module, inconsistencies may occur; you should therefore not use it.
If inconsistencies have occurred already, refer to Note 94443. This note describes how you can solve these inconsistencies.
To create or change condition records automatically, consider one of the following alternatives.
1. Batch input
The report RV14BTCI can create a batch input folder in transaction LSMW.
2. IDoc message type COND_A.
Transaction WE60 provides documentation for the Basis type COND_A02 / COND_A03 / COND_A04.
Please check SAP note 1135984 for more details.