on 08-02-2009 3:22 PM
HI,
In SRM we are creating shopping carts for two vendors. The shopping carts are getting saved without any error.
For one vendor the PO is getting transferred to ECC. But for one vendor it is not getting transferred to ECC.
For the vendor where it is not getting transferred to ECC we get the message that "In case of evaluated receipt settlement, please enter tax code". But when we created a catalogue PO in ECC with same details as of SRM, the PO was created in ECC and the tax code was copied automatically.
What can be the possible reasons that one PO is getting transferred into ECC and the other is not.
Thanks,
Nandan,
Hi Nandan,
I have a similar issue that the tax code derived in the SRM is being overwritten from the tax code in ECC, is there any way to skip this.
your response will be really appreciated
Regards
Rajesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Rajesh, Are you using classical scenario or extended classical scenario? If you are using classical scenario, ECC is leading system and should determine correct tax codes based on certain parameters (ship to loc, vendor location, import/export etc). In this case you have to turn off tax calculation in SRM system. When users create shopping cart, they don't have enough information to determine tax code.
If you are using Extended classical scenario, then implement BADI to overwrite ECC determined tax code with SRM SC tax code.
Hi Purshottam,
Thanks a lot for your reply, really appreciated.
I need to check what scenario is being used as I'm a tax consultant rather than a SRM expert and as of now, ECC has a priority because it is overwriting SRM tax code updated in the shopping cart. It means we are using classic scenario.
Could you please advise what is the effort to activate BADI ?, is it a standard solution or requires ABAp effort ?.
Thanks
Rajesh
If you have classical scenario I would suggest to stop tax calculation in SRM system (this is simple configuration, your SRM consultant would know it) and let's ECC determine correct tax codes (either from NAVS condition records or PIR etc). Business case is "SC is nothing but a purchase requisition and as per std SAP purchase requisition doesn't have any tax code" . It is not possible to put correct tax while creating shopping cart, as tax code determination is based on many parameters which user's don't know at the time of SC creation.
Catalogue items have been created with structured text and the valid tax codes have been assigned to it. This business rule works at least for 70% cases and for remaining cases, it will be further updated in SC.
I feel ECC should determine tax code for goods and services as per the condition records maintained currently (MEK3) and for others it will be either by SC if it is SRM or manually if it s direct PO in ECC
I think this will be better approach, what do you suggest.
Thanks
Rajesh
If NAVS condition records maintained in ECC, then it will be used for all types of PO, catalog items, goods/service PO (created from SRM SC) and direct PO in ECC.
I implemented same design for one of my client and working successfully. We are using SRM catalog, goods/service/limit functionality and direct PO in ECC or from SCM.
In case if above solution is not suitable for your requirement, you can talk developer to enhance BAPI (BAPI_PO_CREATE) to get tax code from SRM SC and bypass default tax code determination from NAVS condition records.
If you ask for my suggestion, then i would say better to use only one method (NAVS condition records) to default tax code in PO for all scenarios (why to do additional development work, when std method is available). Just remember default tax code in PO, is only default, buyer still have an option to change tax code in PO directly. My experience is, after getting default tax code from any methods (NAVS or BAPI etc), buyer needs to change tax code oftenly in PO due to many reasons.
Hi,
Please enter the tax code for the vendor in the shopping cart and save and then check.
Regards
Ganesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Nandan,
How is your tax calculation done ? In R/3 or in SRM ?
See your customizing in SPRO:
SAP implementation Guide -> Supplier Relationship Management -> SRM Server -> Cross-Application Basic Settings -> Tax Calculation.
As you can create manually a PO in R/3 without any problem, i think you have a BAdI implemented for your tax calculation.
Check conditions in corresponding method.
Regards.
Laurent.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.