Skip to Content
0

Adding new field to Tax condition for External service

Feb 28 at 08:35 PM

41

avatar image
Former Member

Hi! All

I have created a new condition table for NAVS to include item category of PO (ZZPSTYP). I have enhanced EXIT_SAPLMEKO_002. I have also added the new field in V_T681F. Now when I create a service PO, the correct tax condition is getting picked up.

However, when I create a service entry sheet for the PO item, the condition analysis shows that the specific condition table is getting skipped as it is not able to get the value for item category and therefore the correct tax condition is not getting picked up. What am I missing?

Regards

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

5 Answers

Jürgen L
Feb 28 at 09:39 PM
0

it could be so much easier for those who want help and faster for you to get a solution if you would just show a few screenshots e.g. from your code in the exit and from condition analysis

You can also follow the instructions from OSS note 566002 - M/03: Can't use field PSTYP in the condition table

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Mar 01 at 01:45 AM
0

Hello Jurgen, Here are the details

Created and added Table 590 with ZZPSTYP in purchasing

Added in V_T681F

Added Table 590 with ZZPSTYP in External Service Management

Code in include of EXIT_SAPLMEKO_002

Tax code determined correctly in Service PO based on condition table 590

Incorrect Tax code in service entry sheet

Looking at the Analysis of the conditions in the service entry sheet, it appears the value for KOMP-ZZPSTYP is not flowing not flowing. Any help is appreciated.


1.jpg (36.1 kB)
2.jpg (46.2 kB)
3.jpg (9.5 kB)
4.jpg (101.9 kB)
5.jpg (76.0 kB)
Share
10 |10000 characters needed characters left characters exceeded
Jürgen L
Mar 01 at 12:45 PM
0

the example from the OSS note 566002 is right the opposite to your statement: E_KOMP-PSTYP = I_KOMP-ZZPSTYP.

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Mar 01 at 03:31 PM
0

Yes Jurgen. Tried with E_KOMP-PSTYP = I_KOMP-ZZPSTYP first. This did not work since import value I_KOMP-ZZPSTYP will be blank so the value passed to E_KOMP-PSTYP will be blank. The value of PSTYP passed to the condition table in access sequence of NAVS will be blank. Therefore the tax code was not getting determined. As mentioned, when I changed the code to E_KOMP-ZZPSTYP = I_KOMP-PSTYP, the tax code determination in the PO is correct and is working as expected. See below.

The problem is that the value does not get picked up during service entry sheet creation. If I put a break point at the code added in EXIT_SAPLMEKO_002, creation of service entry sheet does not even touch this point. The question is what needs to be done so that the correct tax code is picked up in the Service entry sheet. From my understanding, the tax code in service entry sheet should get passed from the PO. But this is not happening.


1.jpg (47.4 kB)
Share
10 |10000 characters needed characters left characters exceeded
Jürgen L
Mar 01 at 05:41 PM
0
Share
10 |10000 characters needed characters left characters exceeded