Outbound INVOIC idoc to partner type LS

[Former Member]

Hello,

We are trying to issue outbound invoices( Message type INVOIC / basic type INVOIC02) to a 3rd party who will be doing the billing on our behalf. We are trying to issue an ALE output type to a LS (logical system) partner type and we are receiving a message B1131, that says that partner type LS cannot be used here, only KU and LI partner types allowed.

We can create the idocs if we setup our partner as a KU customer. However, given that we are sending these to a 3rd party system, it seems that we should be using LS. Does anybody know if there is some configuration where we can choose to be able to send an idoc of message type INVOIC to a partner type LS - logical system?

Thanks in advance.

Mark Monroe

[Former Member · Accepted solution]

Hi Mark,

For your requirement you, create partner profile for LS with following steps :

Create New Partner profile and give your respective TY (User Type), Agent & Language and then follow maintain following parameters under Outbound Parameters :

Message Type : INVOIC

Under Outbound Option u2013 Tab

Receiver Port : <Mention your receiving port here, to create Receiver port you have to go to WE21 transaction>

Pack Size : 1

Transfer IDoc Immediately (Select)

Basic Type : INVOIC02

Cancel Processing After Syntax Error (Select)

Under Message Control - Tab

Application : V3

Message Type : RD00

Process Code : SD09

Hope, your problem will get resolve.

Regards..

Imran

[Former Member · Accepted solution]

Hi Imran,

Thank you for your response. However, it did not solve the problem.

Output type RD00 requires that the partner be a bill-to partner and will not work for a Logical System. We created a custom output type which is setup for ALE processing with a Logical System. We are using pretty much the same settings in the partner profile that you have suggested. The only difference is that our receiver port is a file, not an RFC, so that it does not ask for Pack Size.

Thanks,

Mark

[Former Member · Accepted solution]

Not sure if u need this info...

When the output type was created, did you also include partner functions of "LS"

[Jelena]

I'm replying to this old thread in case someone is looking for a solution through search.

The output type needs to be configured for partner function 'BP' for billing ('VN' for purchasing).

However, partner profile must be configured for logical system (LS). Make sure to leave 'partner function' blank and enter the output type on the 'Message control' tab.

When adding output type to the document (manually or via condition records), use partner function BP (or VN). The IDoc will be created for LS partner, as strange as it sounds.

This is rather counterintuitive. I tried using partner 'LS' or blank with no success. Hope this information is helpful.

[former_member254095]

Hello,

I tried your solution and I added manually an ouput but I always get an error message saying that I have to maintain outgoing EDI-connection data for partner XXXX.

Output type = ZXXX

Medium = 6 EDI

Partner function = BP

We use the LS partner so we do not want to define each partner and we need to generate an invoice in the Bill-to language.

If you have any suggestion, it will be helpfull!

Edited by: Eric Dubois on Dec 7, 2011 3:37 PM

[Jelena]

Eric, in addition to the output you also need to maintain partner profile in WE20. But instead of maintaining KU type, just create one record for logical system (LS). Make sure to leave 'Partner Role' blank.

Also I used ALE medium, not EDI. Not sure about the language though, it may or may not work.

[former_member254095]

It worked! Thank you!!!

[Former Member]

Hi,

I've tried your solution to send o/p from a PO to a third party...created a new o/p type configured it for VN

Created a logical system in BD54 and created partner profile for that logical system and left the partner role as blank.

When i go back to my PO and try to issue the o/p manually it errors out " Maintain outgoing EDI-connection data for partner XXX" this XXX is the vendor for the PO

If i change the partner function to LS and delete the partner number, gives me a pop up with the output partner details screen of the PO to select

Please Advice

Thanks,

M

[Jelena]

> When i go back to my PO and try to issue the o/p manually it errors out " Maintain outgoing EDI-connection data for partner XXX" this XXX is the vendor for the PO

Make sure to use ALE medium, not EDI. Also make sure to create a distribution model with LS and message type in BD64.

[Former Member]

Thanks,

It creates an output gets the vendor # in the partner field.. i dont want that..

I had to go back and change the partner to LS in the output type and entered the partner number of the partner profile in the partner field and created an IDoc.. still testing have to wait and see the consequences..

Thanks for going back to the thread and posting the solution... helped me a lot

Thanks,

M

[Former Member]

Ok i got this to work, however i needed to issue another output for PO change. I configured another output type tht triggered for change, maintained partner profile.

When i make changes to the PO, i see the output type with medium ALE and partner type EL, however it does not process but fails with error "wrong partner type LS". Could anyone help with this.

its wierd i have the same LS to send the PO however now get this error for another condition type for change

Thanks,

M

[Former Member]

Hallo Expert,

I went though all the current link available in SDN but couldnt find the exact solution against it.

I have the same issue with PO. When I am giving VN instead of LS then it is working fine for manual entry but when I am doing the setting in condition record as LS for automatic output type assignment it is not working. Its give the error as "Wrong partner type LS".

Could any expert help me on this. I want to assign output type automatically which is working fine so that IDOC create in real time. I did all the ALE setting and output type configuration but somewhere it is missing something as I tested for "LI" and it is working.

Expert input are higly appreciated.

Regards

Sanjay

[Jelena]

Solution has already been given in this thread - do not use partner LS in the output. In the output you need to use a partner that is appropriate for the document (Vendor, Bill-to, etc.). Output can only be proposed for those partners that are listed on the Partners tab. But all the other configuration (BD64, WE20) needs to be done for partner LS.

ALE output works differently then Print or Email output. BD64 and WE20 configuration are driving this output, not the partner type in the output.

[Former Member]

Thanks Jelena!

[JaySchwendemann]

Dear Jelena,

just wanted to say thank you. That actually worked, even if documentation from SAP seems to be sparse in this area.

Many thanks for providing input on this.

Cheers

Jens

[Former Member]

hello gurus

I don't want to open a new topic so I hope you don't mind I will ask inhere

my client is using two systems (SAP1 and SAP2) it will take very long time when will he finish the rollout to the second one)

so the point is that I have this problem (I'm new in this topic) that he wants to reflect an outboud invoice form SAP2 to SAP1 using idoc (the input is MIRO transaction in SAP1)

do you guys maybe know what will be the simplest way to manage it? Can I use a standard idoc exiting in system (Adds on?), and just make the mapping of it (I don't know how it should work, I'm not developer, just need to write complete documentation how should it work+mapping)

thank you for quick help and explanation step by step

Yaya

[Former Member]

Thanks Jelena for your reply.

But LS is coming automatically from condition record where I set it default for all document type. User don't want to go manually in message button and change it to VN when PO get created using tcode ME21n. Just they need to create PO.

Your suggestion is highly appreciated

Thanks

S

[Jelena]

Do not use LS partner in the condition records, use VN. Use some high-level accesss sequence, e.g. by Purchasing Org, so that you don't have to create condition records for every vendor. (Or whatever seems appropriate in your scenario.) As I said, in the output we need to have a proper partner for the document, not LS. SAP can somehow handle ALE distribution to LS partner even if we use a different partner in the output.

Follow-up: if I remember correctly from my excruciating debugging experience, it goes like this. SAP program checks if there is a partner profile for the same partner type (vendor, customer, etc.). If not, it goes and checks the distribution model in BD64. There it sees a record to distribute to LS partner and then goes and reads the LS partner profile. Voila. So when you use LS partner in the output, you're just confusing this program. The code there has a bunch of hardcoded values for the partner types. I think it's not even designed to expect LS partner in the output (again, if memory serves).

Edited by: Jelena Perfiljeva on Mar 1, 2012 11:44 AM