PO Orders05 automatic determination does not work

[DG]

Hi,

I have a problem.

When I add a logical system to MN04. I get a dump while processing an PO with ME21n for

PERFORM_PARAMETER_MISSING. When calling the "RSNASTED" - "EDI_PROCESSING".

When I remove the entries in MN04 it is possible to add the logical system manually to the messages in ME21N.

Then I get the warning VN006

Partner XXX_D does not exist for partner function LS .

when the idoc is produced then the ORDER05 Idoc is parked with status 30.

Are there any solutions to help with having the logical system automatic determniated and send the IDOC automatic.

Daniel Graversen

[DG]

Hi,

I have a problem.

When I add a logical system to MN04. I get a dump while processing an PO with ME21n for

PERFORM_PARAMETER_MISSING. When calling the "RSNASTED" - "EDI_PROCESSING".

When I remove the entries in MN04 it is possible to add the logical system manually to the messages in ME21N.

Then I get the warning VN006

Partner XXX_D does not exist for partner function LS .

when the idoc is produced then the ORDER05 Idoc is parked with status 30.

Are there any solutions to help with having the logical system automatic determniated and send the IDOC automatic.

Daniel Graversen

[Former Member]

Please check the following settings:

You have maintained the partners in VOE2 resp. VOE4

The partners maintained are to be inserted in MN04, field 'partner', role 'LF', medium 6

You have setup your partner-relations in tx. WE20

...

[DG]

Hi,

I have tried to update VOE4 with the logical system. But I still get the problem that Partner XXX_D does not exist for partner function LS

Daniel

[Former Member]

>

> I have tried to update VOE4 with the logical system.

???

I may be misunderstanding you totally, but usually you do not define messages of type ORDERS05 for logicals systems, but for vendors - you determine in MN04 where the purchase order should go to - and that is ususally a vendor (yes, yes, maybe in another system), so your entry in MN04 should reflect something like:

Vendor   Role  Partner     Medium
4711     LF    00000004711 6

Next in line would be generating partner combinations in WE20 for

Partner type LI

Partner role LF

Partner number 4711

Message type ORDERS

...

Port: -somethingorother which you have defined in transaction WE21describing the system/client where the purchase order should go to as a sales order-

Maybe I'm getting it all wrong. Maybe it would be best, you described your business scenario here ...

[DG]

Hi Mylène ,

Thanks for taking the time.

We could probably update all the vendors in the tables. But it just requires a lot of maintanence that, we would like to avoid having to maintain VOE2-4 and partners when we add new vendors.

For other document is it possible to send them to a logical system.

When a new PO is created the PO is send as an IDOC to a Warehouse Management System, which will handle the order when the physical goods arrive.

[Former Member]

> For other document is it possible to send them to a logical system. 

this is news to me ... where would the invoices come from etc.??

anyway, can you please provide the link to that document, so that I can read it?

thanks in advance.

Edited by: Mylène Dorias on Apr 28, 2010 3:18 PM

Daniel,

could you please check in transaction NACE whether your partner type is LS??

[DG]

The other documents is deliveries where this works. And it has nothing to do with this process. I'm not sure on where to find documentation for this.

In NACE I have configured EDI to run using LS.

[Former Member]

I have been debugging this - mind you I am not a developer - but I was correct in my understanding of the process.

This is not possible for purchase orders. Why:

Business reason:

If you send a purchase order to a vendor - it requires follow up processes, at least a goods movement or an invoice -> hence: the receipient can never be a logicals system.

This is different where a delivery note goes to a WM-system -> it get's picked in the subsystem and that is that. No follow-up processes, the rest is back in ERP. There is no 'personal identity' like a customer or vendor involved.

Technical reason:

The output processing of a purchase order uses EDI_PARTNER_TEST_OUTGOING in DV70AI0D in SAPDV70A. If you test that function with SE37 you will see that it adamantly searches EDPP1 with LI for a partner type. If you can bypass that by smuggling the correct entries into that table you will fail at EDP12 - try for yourself - there's no application to maintain those data (except for smuggling - which doesn't work either) - and that is that.

Have a nice evening anyway (and I mean that in earnest).

Cheers,

mylène

[DG]

Hi mylène,

Thank you for your in depth answer. It seems like you have a correct point in the situation.

Just so irritating that I have to find a workaround on the solution.

Guest that I'll need to set something up, so we can maintain all the partners automaticly.

Thanks

Daniel Graversen

[Former Member]

Hi,

Let all put as Mylène said. But still we can use port (trfc) to send the idoc to our other system (LS).

--

Reddy

[DG]

But we still need to maintain the WE20 and MN04 for all partners.

[Former Member]

In MN04, find a condition type which does not depends on vendor number. Like doc type.

Mantain common vendor number for all. I am not sure in inbound process of PO IDOC, does process take vendor number directly from control record of IDOc?

But in case of DELINS, there would be a logic (custamization) to find right sold2 in inbound process. process wont take sold to directly from control record of idoc.

--

Reddy

[DG]

It was possible to sent the PO Orders05 to the Logical system.

In NACE I had to use FM06AEND CHANGE_FLAG on the general data on the new message type that I created. That had somehow been changed to the EDI version.

Then MN04 could be used to determinate to which partner the document should be sent.