Service Rendered Date in Credit Memo

[former_member219209]

Hi Experts,

I am creating a credit memo request in CRM with reference to Invoice document which is present in ECC. While creating the Credit memo in CRM all other condition type except tax having the pricing condition date as billing date of invoice. But tax related condition types having the pricing condition date as posting date of credit memo. The tax condition types are UTXD, UTXE, XR1 to XR6.Why it is happening like this? It should also take the billing date of invoice.

One more thing, after Credit memo replication to ECC. The service rendered date is not populated automatically in ECC credit memo. Since tax calculation in ECC is based on Service rendered date, the taxes are not calculated in ECC credit memo. Again this changes flowing to CRM and remove the tax value in CRM also.

But if I manually enter the service render date in ECC credit memo then tax is calculated based on the given service render date and also replicated to CRM successfully.

Questions:

why taxes are calculated using posting date of credit memo in CRM? (It should calculate tax based on invoice's billing date)

which field in CRM credit memo is corresponding to service render date in ECC credit memo?

How to populate value of this service render date in ECC?

Thanks,

Vignesh

[Former Member · Accepted solution]

Hi Vignesh,

We had similar requirement in my previous projects wherein we were creating Complaints with reference to Invoice and then issuing credit out of complaints. Complaints doucument dont have the service rendered date by standard therefore we copied the billing date in one of the fields on the complaints and passed that value to credit memo in ECC. It calculated the tax based on the sevice rendered date.

This is one way of achieving the requirement mentioned above. Hope this helps.

Thanks,
Chandrakant

[former_member219209 · Accepted solution]

Hi Chandrakant,

Thanks! Your answer make me clear the doubt that there is no corresponding field in CRM for service render date.

In my case I need to make tax calculation based on the invoice's billing date. But if I create a credit memo in CRM its taking current date as billing date for credit memo and taxes are calculated based on the current date. It should calculate the tax based on invoice's billing date.

One good thing is expect taxes all other pricing condition values are determined based on invoice's billing date correctly. Hence in CRM credit memo I have pricing date field correctly and its also replicating to ECC.

So according to you I should implement some user exit of credit memo in ECC and populate the service render date as same as pricing date right? or is there any way to pass this service rendered date value from CRM itself?

One more issue here is before replication in CRM tax is calculated based on current date. I should also concern about this one. Let me know what need to be done for this issue?

Thanks,

Vignesh

[Former Member · Accepted solution]

Hi Vignesh,

What we did is we enhanced the Action Method in CRM to accomodate this date and pass to ECC while replication. Therefore, when the Credit memo was created in ECC it had the date and the taxes were calculated correctly.

About your concern on CRM part, you can check the pricing BADI for e.g CRM_COND_COM_BADI whether you can pass service rendered date to calculate the tax amount on that date. I havent tried it but this is just a thought.

Thanks,

Chandrakant

[former_member219209 · Accepted solution]

Hi Chandrakant,

I have implemented  CRM_DATAEXCH_BADI badi and passed the service rendered to ECC and it working fine.

Service rendered date is available in the structure cs_bapisdhd1 of method CRM_DATAEXCH_AFTER_BAPI_FILL.

In ECC taxes are calculated correctly based on the service rendered date and its again replicated to CRM.

Thanks,

Vignesh

[Former Member · Accepted solution]

Good to hear that Vignesh. Since we were using complaints we used action method. Since you are creating credit memo request in CRM, CRM_DATAEXCH_BADI badi makes sense. Thanks!