Using partner role in output sequence

[akrason]

Hi,

I am unsucessful in using partner role as a condition for creating differenciated outputs.

Below is the way in which I have included partner role (PARVW) in the access sequence for output determination in SD.

I have added the field PARVW (the one from KOMKBV1) into "Field Catalog (Output Sales)".

I have created a new output condition table. Note : PARVW occupies here the last position.

I have created a new access sequence and assigned it to the output type (in my case document category is a contract).

I have created output condition record in VV11.

However when I use these settings and master data to create sales document (here: contract) the header output message is not defaulted.

The message 524 in determination analysis states that the access has not been made and the field is initialised.

Only when in the access sequence I specify value source as a constant (= the desired partner role ID as maintained in output condition) the system behaves correctly.

But this way of solving the problem is not satisfying me.

I need to use several different partner roles on per customer basis in order to be able to send more than one output via transmission medium 5 (external send).

But when managing master data (condition records) I cannot list all partner roles for a given customer under the same access sequence.

To do so I have to multiply access sequences (each of then receives partner role ID as a constant) and manage more separate condition records.

Have you already come accross this strange system behavior?

Am I missing something in the standard settings?

Is PARVW-KOMKBV1 usually behaving correctly in acces sequence?

I would appreciate your expert help.

Andrzej

[RobertVit]

Hi,

i know the issue of sending multiple invoices to one customer.

Your solution approach is new to me.

Maybe you can consider these two (working) approaches:

- use a (exchange) distribution list and maintain it in customer master data

- enhance customer master data with multpile e-mail adresses (z-fields) and leverage this in ouptut program

[akrason]

@ Robert Forster

Hi Rob,

Would exchange list be easy to manage if the point is that some customers need only one single output (via medium 5), some require two parallel and identical and finally some of them ask for even more than two...

Combining the two transmissions medias (5 and 7) in the same sales document gives some more flexibility, however with a major drawback : medium 7 does not generate in standard SAP a desired PDF copy of, let's say, order acknowledgement. So the send outs are not potentially identical when it comes to the form (For the contents I can manage text with order parameters which are substituted by actual values while processing this type of send out).

To tell the truth using medium 7 gives the largest flexibility : multiple destination adresses, "to" and "copy to" differenciation, text with parameters (see above), free attachments allowed, http:/ links allowed. However a big drawback here : no PDF copy of sales order in standard SAP.

So to conclude, what solution would be, at your eyes and experience, the least "costly" in terms of changing or, hopefully, just enhancing SAP standard?