Skip to Content
author's profile photo Former Member
Former Member

Outbound INVOIC idoc to partner type LS


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

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Aug 20, 2009 at 12:58 PM

    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.



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 04, 2011 at 07:37 PM

    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.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Mar 01, 2012 at 04:29 PM

    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



    Add a comment
    10|10000 characters needed characters exceeded

    • 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

  • author's profile photo Former Member
    Former Member
    Posted on Dec 05, 2012 at 12:12 PM

    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


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.