PO Message output control for specific document type

[Former Member]

Hi,

We have created a new PO message output ZNEU and new PO document type CT.

We are able to default the ZNEU for PO doc type CT maintaing condition records.

We also have output type NEU for PO doc type NB.

Although we can default the particular output type for a specific PO doc type still if condition record is not maintained,

we can use any of the output types manually for any of the PO doc type.

Is there any way to control the message output type to be used only for a particlar document type.

Example: ZNEU can be used only for doc type CT.

                 NEU can be used only for doc type NB.

Please advise.

Best Regards,

Pratap

[JL23 · Accepted solution]

I think there is no standard solution to have an output type only for a certain document type.

But you can create a requirement in the message determination schema which could prevent an unwanted output type, similar to requirement 103 which does not allow a dunning letter if the original PO was not printed.

[Former Member · Accepted solution]

Hi Jurgen,

I just wanted to be sure that there is no standard configuration for this.

Thanks for your input.

We will have to control it in the requirement routine.

Regards,

Pratap

[BijayKumarBarik]

Hi,

PO message type  should be trigger automatically for a PO creation by selecting check box of Indicator: Print Operation (1) with that PO output type  below path:

SPRO -> MM -> Purchasing > Message -> Output control -> Message types -> Define message type for Purchase Order -> Fine-Tuned Control: Purchase Order

But for multiple PO message types with respective PO document type, you can use message condition in t.code:MN04 for PO message types with respective document type.

ZNEU for doc type CT.

NEU for doc type NB.

NOTE:

For all PO message types, you have to  enter Indicator: Print Operation (1-New) and ( 2-change )

Regards,

Biju K

[kunal_ingale]

Hi Pratap ,

Either you can go for the new requirement as suggested by Jurgen or check with your ABAPer if you can go for FM to check the output type before saving the purchasing order.

Thanks

Kunal    

[Former Member]

hi Pratap,

you would like to look into 'Message Determination Schemas' and see, if you can play around there. "Maintain Message Determination Schema: Purchase Order"