Tax code in SA - LSMW

[Former Member]

Hi,

I am creating SA using LSMW (IDOC method) but getting below strange issue:

For few lines tax code is not getting picked in SA though tax code is one of the input field in my source file. Point is for other lines it is getting picked and for some of them only it is not appearing. On further analysis found that for some materials only tax code is not getting picked in SA even it is one of the input field in my source file. Can you please provide your inputs what would be the reason for this behaviour.

Thanks,

Vihaan

[JL23 · Accepted solution]

try to enter one of these error items manually without LSMW usage, only this way you can find out if the error is in your coding or just in the transaction in general..

I guess you get the same problem. But manually you will see error messages directly can read long text of error message adnd press F1 field help. This often helps to determine the root cause.

[Former Member · Accepted solution]

Hi Jurgen,

Thanks for the reply. The problem got resolved as there was an info record for the material / vendor combination which was overwriting my source field value.

However, I am stuck with another issue - we have to update vendor material number filed also while creating SA via LSMW, I have added IDNLF field with data type C and length 35 and in my source file also giving VMN with 35 characters but still SA is gettign created with blank value for VMN. This looks straight forward requirement of populating new VMN field in SA but not working, any input on this would be great.

Thanks

Vihaan

[Former Member · Accepted solution]

Hi,

Any input on this, why vendor material number can not be populated while creating a SA using LSMW IDOC method?

I tried other fields like acknowldge no, tracking number ..everything is getting populated but VMN is not getting picked from source file.

Thanks,

Vihaan

[JL23 · Accepted solution]

have you tried the same manually in the usual transaction ? is the field open for maintenance?

Is the value in your conv-file visible and at the right place?

[Former Member · Accepted solution]

Hi Jurgen,

Yes, when I tried creating SA manually using ME31L it is allowing me to enter VMN field in item details and also during "display converted data" step in LSMW I can see VMN field is getting popuated but after SA creation step it does not appear in SA when I see in ME33L.

Another issue is with the net price, net price is one of the input field in my source file but when I try to create a multiline SA (i.e. I line in Header source file and multiple lines in item file) it is only populatinig price for 1st line and for rest of the lines it is updating it with zero price. However, when I use same LSMW for single line SAs it is creating SA correctly with price in each nd every SA. So question is why in case of multi line it is populating zero price for all the lines except the first one.

Thanks,

Vihaan

[Former Member · Accepted solution]

Hi,

Any update on this, has anybody else faced similar issue with SA creation via LSMW.

Thanks

Vihaan

[Former Member · Accepted solution]

Hi,

Raising query against an old question......I wanted to know how to upload partner function while creation SA via LSMW - especially when you have multiple vendor for a single partner type like. For example there are 3 Invoicing vendors and 2 ordering vendors and while creating SA manually via ME31L system pops up a message to user to select one vendor but wanted to know how we can achive this via LSMW?

Tks,

Vihaan

Edited by: Vihaan on Dec 20, 2011 9:54 PM

[JL23 · Accepted solution]

you have to have the vendor number of the correct partner already in your IDOC.

so you have to know this vendor already in your source file or you need a logic which can be added as ABAP coding in LSMW to determine the correct partner during run time of conversion step. otherwise SAP will add the partner who has the indicator as preffered partner in vendor master.

[Former Member · Accepted solution]

Hi Jurgen,

Thanks for the reply.

Yeah, I have partner number for my partner function with me. My question is how we will fit partner function upload in LSMW because for the same field i.e. Partner_type , you have two values OA and PI? Do we need to have a separate file for partner function where we can have both partner types captured against a single header?

also can you please confirm which fields from below partner structre needs to be mandatory populated as I am unable to create SA even i am populating values directly in field mapping step for one partner type.

PARTN_ROLE

PLANT

SUBRANGE_TX

LANGU

LANGU_ISO

PARTNR

DEF_PARTNR

DELETE_IND

Tks,

Vihaan

[JL23 · Accepted solution]

you only need PARTN_ROLE and PARTNR.

But the important part is that you need to enter the partner role with the internal key (German abbriviation): instead of OA you have to enter BA, instead of PI you have to enter RS

´

per SA and role you need one record in this partner structure. There are various ways to achieve this. if you think it is convinient to do it with an extra file, okay, it will work.

[Former Member · Accepted solution]

Hello Jurgen,

Thanks again for prompt response.

Yes, I am using BA and RS only as my input for Partner role field. To make it simple this is what I am doing..

Instead of passing values via file, first I am trying to do it with constant values i.e. directly entering values in field mapping step. For example purpose - in my case I have OA partner function with two suppliers for this, so in field mapping step, I am passing values as mentioned below:

E1BPMEOUTPARTNER

PARTN_ROLE = BA

PARTNR = 1XXXXXXXX9 (this is one of those 2 OAs)

E1BPMEOUTPARTNERX

PARTN_ROLE = BA

PARTNR = X

But still i am getting partner function missing error in LSWM and in IDOC overview I can see values are passed as mentioned above for E1BPMEOUTPARTNER segement under Data records.

However, if I try my LSMW with a supplier having only one OA then it is working fine.

Please advise.

Tks,

Vihaan

Edited by: Vihaan on Dec 20, 2011 11:25 PM

[JL23 · Accepted solution]

E1BPMEOUTPARTNERX

PARTN_ROLE = BA

PARTNR = X

If I am not mistaken, then PARTN_ROLE in this x-strcuture should have a X instead of BA

[Former Member · Accepted solution]

Hi Jurgen,

Yeah, I knew that as all ...X structure shud have X as value but for this one if click on suggested value (Question mark ICON) it gives you a field with 2 characters which normally comes as single character. So I had to populate BA.

Anyways I tried it now with X also but same results.

Anything else you would suggest or I should go for a new LSMW (I am not sure how much it will help by creating another one as this one works fine with partners where single OA is there)

Tks,

Vihaan

[Former Member · Accepted solution]

Hi Jurgen,

I have tried creating new LSMW also, very simple LSMW with not many fields - but it fails whenever there are more than one OA, for vendors with single OA it works fine. Is there any other structre which needs to populated to have partner function in SA? Or any other field whihc needs to be populated for trigger this? I ma not sure if any OSS note is there to address this issue.

Tks,

Vihaan

[former_member221541 · Accepted solution]

Hi Vihaan and Jurgen,

We are also facing similar kind of issue, only difference is we are creating our SA with reference to a contract (which has multiple OA and PI assigned). Now while creating SA via LSMW (PURSAG_CREATE message type) w r t contract we are providing inputs in E1BPMEOUTPARTNER and E1BPMEOUTPARTNERX structure for fields - PARTN_ROLE = BA and PARTNR = OA Vendor ID but it does not create SA and throws error - Mandatory PF OA missing (OA is mandatoy for our SA document type).

When we try to create SA manually w r t contract via ME31L, it gives us a pop up to select one of OA from list of valid OA in contract. My understanding was that if we input OA vendor ID in LSMW it should consider it as our choice but unfortunately it is not recognizing that input of OA (which we are providing via E1BPMEOUTPARTNER and E1BPMEOUTPARTNERX structure).

I tried searching for a OSS note for the same but could not find anyuthing which resolves it but there is one which says if you are creating SA w r t SA there is some issue with program - OSS note number is 1154064

Hi Jurgen , Please advise if you think this OSS number is relevant for our issue and if we should open a message to SAP for the same.

Note: Like Vihaan, for us also LSMW works fine if SA is being created w r to a contract which has single OA and PI.

Thanks,

Yogesh

[JL23 · Accepted solution]

the OSS note is valid in case you create SAs in reference to an other SA, but as it is a source code correction, it does not harm to implement it anyway.

There is one more OSS note: Note 1610959 - BAPI: Partners not used in new scheduling agreement

[Former Member · Accepted solution]

Hi Yogesh and Jurgen,

Did you find anything about this issue? Please let me know incase you get some solution for this.

Tks,

Vihaan

[JL23 · Accepted solution]

watch this thread

Yogesh has opened a message at SAP and will update this thread once he has a reply

[former_member221541 · Accepted solution]

Hi Vihaan,

We were able to resolve this issue by appling OSS note 1610959. You can also ask your BASIS or technical team to apply this note in your devlopment system and test it. Let us know if you are able to resolve your issue via this OSS note (though I am sure this note will solve ur issue too).

Yogesh

[Former Member · Accepted solution]

Hello Yogesh,

Thanks for the updates, I will try to get this OSS note implemented and then will confirm the results.

tks, Vihaan

[former_member221541 · Accepted solution]

Vihaan, just curious as you have marked this thread answered- was your issue also related to above mentioned OSS note?

yogesh

Edited by: Yogesh Lohiya on Dec 30, 2011 5:14 AM