on 02-16-2015 6:29 PM
Hi experts,
I'm using program ISA_CATALOG_REPLICATION to replicate the product catalog from ERP to TREX (no CRM involved at all). I would like to show zero price for some materials based on material sales data. It's unclear how to achieve this. Is it best to enhance the build catalog program (I have custom program to build the product catalog) or the replicate product catalog program? and how?
Could you please advise the best approach?
Thanks,
Satish
Hi Satish,
If you have defined the catalog prices by IPC then you can use customer specific pricies as IPC's calculation schema is determined during ERP customization which is based on order type, sales area and customer. If you are taking it directly from ERP then enhance the build catalog program.
Please let me know if my understanding about your problem is correct.
Thanks,
Hamendra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Hamendra,
The ISA is hosted from ERP and no IPC is used. Prices are fetched from ERP directly. Standard BAPI 'BAPI_PRODCAT_SAVEHEADREPLICA' is used in the custom program to build the product catalog.
Could you please give me the technical details (BADI, user-exit etc..) on how to implement this in the catalog build program?
Thanks,
Satish
Hi Satish,
Please have a look of the below URLs
http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=107774353
http://www.stechies.com/sales-related-user-exits/
Thanks,
Hamendra
Hi Satish,
Please have a look of the below paragraphs and hope will help you.
USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ) This user exit allows you to copy additional fields for pricing in the TKOMK communication structure (header fields), which have not been provided in the standard SAP system. These fields can also be used for pricing in the billing document. This user exit is described in detail in the "New fields in pricing" section.
USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ) This user exit allows you to copy additional fields for pricing in the TKOMP communication structure (item fields), which have not been provided in the standard SAP system. These fields can also be used for pricing. This user exit is described in detail in the "New fields in pricing" section.
USEREXIT_FIELD_MODIFICATION (module pool SAPMV61A, program MV61AFZA) You can use this user exit to adjust the display of individual lines in the condition screen by changing the display attributes of the screen fields. This does not include the display of subtotals. This user exit is also used in order processing. USEREXIT_FIELD_MODIFIC_KZWI (module pool SAPMV61A, program MV61AFZB) You can change the display of subtotals in the condition screen by changing the display attributes of the screen fields. This user exit is also used in order processing.
USEREXIT_FIELD_MODIFIC_KOPF (module pool SAPMV61A, program MV61AFZB) You can adjust the display of subtotals in the condition screen to your requirements by changing the display attributes of the screen fields. This user exit is also used in order processing.
USEREXIT_FIELD_MODIFIC_LEER (module pool SAPMV61A, program MV61AFZB) You can adjust the display of blank lines in the condition screen to your requirements by changing the display attributes of the screen fields. This user exit is also used in order processing.
USEREXIT_PRICING_CHECK (module pool SAPMV61, program MV61AFZA) You can install additional checks to the standard checks of condition lines (e.g. maximum/minimum value).
USEREXIT_PRICING_RULE (module pool SAPLV61A, program RV61AFZA) In the standard SAP system, it is predefined which condition categories and classes can be copied or recalculated per pricing type. You can change the predefined standard procedure for each pricing type.
USEREXIT_CHANGE_PRICING_RULE (module pool SAPMV61A, program MV61AFZA) You can use this user exit to change the pricing type that has been predefined in the copying control table in billing.
USEREXIT_XKOMV_BEWERTEN_INIT (module pool SAPLV61A, program RV61AFZB) This field is used in the formulas and therefore initialized before the loop for the pricing procedure starts.
USEREXIT_XKOMV_BEWERTEN_END (module pool SAPLV61A, program RV61AFZB) Within a loop for the price components during pricing, specific values can be transferred into the communication structures in pricing to be further processed.
USEREXIT_XKOMV_ERGAENZEN (module pool SAPLV61A, program RV61AFZB) In change mode, you can change the dynamic part of the condition record (KONVD) that is always redetermined (i.e. it is not stored in database table KONV).
USEREXIT_XKOMV_ERGAENZEN_MANU (module pool SAPLV61A, program RV61AFZB) You can use this user exit to change the ready-for-input fields of the manually entered condition record in add mode in the condition screen.
USEREXIT_XKOMV_FUELLEN (module pool SAPLV61A, program RV61AFZB) This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record.
USEREXIT_XKOMV_FUELLEN_O_KONP (module pool SAPLV61A, program RV61AFZB) This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record. This may include subtotals, manually entered conditions or conditions that have been calculated with a formula.
USEREXIT_PRICING_COPY (module pool SAPLV61A, program RV61AFZA) You can change the KONV fields for copied price components
Thanks,
Hamendra
Hi Satish,
i guess if you like to replace a damanged light blub in a car, you do not go ahead and replace also the whole car around So i think it is best you ignore all the previous messages from anyone as those go unfortunately in the wrong direction . I assume your company has already implemented all the pricing procedures anyway, so it is more about publishing the specific prices to the catalog .
There is a class available, which you can enhance. It is called CL_ISA_REPLICATION_CATALOG. Create your custom logic within a z-version of that. You only have to make sure thereafter, that your instance is called and not the standard.
This class is called whenever you try to replicate any data to TREX and it collects all data. You can use that interface to handle your pricing requirements depending on the sales area.
You have various ways do enable your requirements depending on your situation
Best regards,
Andreas
Thanks Adreas,
It is really good hook and positive thanks to you for your below comment!!!!!
i guess if you like to replace a damanged light blub in a car, you do not go ahead and replace also the whole car around So i think it is best you ignore all the previous messages from anyone as those go unfortunately in the wrong direction .
Hi Satish,
As Adreas mentioned, please have a look of SAP Note 837119 as well. It may help you.
Thanks,
Hamendra
User | Count |
---|---|
3 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.