on 03-12-2014 3:43 AM
Hi Experts,
As per business requirement, we have assigned account key as well as accruals key for freight and service tax on freight condition in our specific delivered pricing procedure. And we have assigned G/L in VKOA and OB40 for this condition. Based on this VKOA and OB40 setting, System is hitting all G/L perfectly in billing accounting document.
As per current system mapping. When we take return against billing document, System is hitting same G/L in return billing document.
But now as per business new requirement. In case of return only with particular this delivered pricing procedure, they want the Service Tax Payable GLs should not be reversed; instead, a separate set of Discount GLs are to be hit in accounting entry. And the accrual GLs, both for Freight & Service Tax on Freight, should not be triggered in Return case.
Fun fills the above requirement. We have created new access sequence in VKOA. And assigned G/L as per below screen shot.
New access sequence in VKOA is : AcctDetProcedure./SalesDocTy/Acct key
Example of G/L mapping:
App | Cnd.Ty. | Ch. | ActDPr | SaTY | ActKY | G/L | Provi.Acct |
V | KOFI | EGCA | ZDP0001 | ZRE | ERF | 57020001 | 30001199 |
For creation of new access sequence in VKOA: We have added below two new filed in structure MV12A and KOMCV.
ZAUART - Sales Document Type
ZKALSMC - Account determination procedure
Also we have right code in exit RV60AFZZ - USEREXIT_ACCOUNT_PREP_KOMKCV for mapping of this new filed value.
After above all setting, still system is not determining new set of G/L for return case. So request you to suggest the way for hitting new G/L as per above requirement.
Regards:
Haresh Panara
Hi Haresh Bhai,
You have written that you want this new G/L s to be determined only for specific pricing procedure, but you have written ZKALSMC - Account determination procedure.
In case of return only with particular this delivered pricing procedure,
So there seems some Gap.
Try with cross checking this part and let us know the result.
There is another simple alternative to achieve this requirement is via addition of 2 new Condition type with new Act Key.
In previous both Condition type assign requirement type where if system finds that specific pricing procedure available then that condition types should not be triggered.
Regards,
MJ.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Haresh,
Please find below logic which you can suggest your ABAPer to implement in Requirement Routine for de-activation of condition types.
Copy existing routine 002 and add below logic for Old condition types of Freight and Service Tax
If KOMK-AUART = 'Your specific Return Order Type'
KOMK-KALSM = ' Your Specific Pricing Procedure'
SY-SUBRC = 4
else
SY-SUBRC = 0
For newly created 2 condition type,
Copy existing routine 002 and add below logic for Old condition types of Freight and Service Tax
If KOMK-AUART = 'Your specific Return Order Type'
KOMK-KALSM = ' Your Specific Pricing Procedure'
SY-SUBRC = 0
else
SY-SUBRC = 4
Assign this both requirements and maintain respective account determination procedure so system will pick up correct accounts.
Regards,
MJ.
User | Count |
---|---|
108 | |
15 | |
10 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.