Message Output

[Former Member]

I have created two message types for Outline Agreement (ME32l) .

I created two seperate condition tables ( 1- Comapny Code and second : coocde , vendor ).

I set up everything in SPRO , but when i change a SA for( Cocode 1000 ( makes the condition true for 1st mess type ) and vendor (10011, makes the condition true for second message type ) , ONLY message 2 defaults in the messages .

The message 1 ( inspite of having the condition true and condition record maintained ) doesnt comes up by default ? Any idea what can be missed / wrong ?

[Former Member · Accepted solution]

Look at the following documentation. I think in your case, in production, it is deactivated(absence of the proc assignment), that is why you get the NEU output. But if message determination is activated, then you need to maintain the output settings. See the underlined documentation.

<i>Message determination deactivated

You can output purchasing documents without the message determination facility. In this case, you must not assign any message determination schemas to the the individual purchasing documents (RFQ, purchase order, etc.). The system then generates a message of the type NEU (new) for each document to be outputted. To determine the printer, the system first checks the settings for the purchasing group. If no printer has been maintained there, it checks the user parameter. If no printer has been specified there either, the system checks the fixed value for the user. <u>If no printer has been specified, the system does not generate a message record.</u></i>

[Former Member · Accepted solution]

Yes that looks exactly rt that it was deactivated So, it defaulted to the NEU . But , now if i assign it a procedure , then all the Output types that are successful for a condition should come .

i did one for Sche Agr Delkivery (me38) yesterday and it is working fine ie it defaults LPET and Zmessage both , if they both come true on condition .

[Former Member · Accepted solution]

I think the problem may be with the printer. See if a printer is determined correctly since NEU is a print and fax output. Other than that nothing comes to my mind.

[sridhar_k1]

Check Goto->Determination analysis in outputput screen of tx ME32L. Shows you detailed analysis about why a particular output type is chosen and why not other.

Regards

Sridhar

[ferry_lianto]

Hi,

Have you maintained condition records (NACR) for NEU with new key combination (created two seperate condition tables ( 1- Comapny Code and second : coocde , vendor ))?

Regards,

Ferry Lianto

[Former Member]

The condition record that triggers NEU is only COmpany COde( 1000) which is maintained in the corresponding condition table .

For Zmess , the condition rec (ccode 1000 and vendor 10011) is also maintained in its corresponding table .

[Former Member]

Hi Srinivas ,

Hats Off it was the printer assignment .. Thank you so much for going along with the problem at all steps.

Thanks Again

[Former Member]

Whew!! That was puzzling until the time I decided to look at the documentation associated with that task. Glad that it resolved the issue.

[Former Member]

Can you list out the steps you followed to configure the whole thing? Check if you have any requirements attached to one or the other message. Do you have both of them attached to the 'Message Determination Schema' of the outline agreement? Did you, by any chance click the checkbox for 'Manual Only'? Did you assign the correct partner roles for both the message types?

[Former Member]

Hi Srinivas ,

These are the steps i followed for each of the message type .

1) created Condition tables .

2) Created Access sequence pointing to these tables for each.

3)created message type..did fine tuning .

4)Requirements were already defined ( as initially the First one was there and working well ). Assigned the same requirement to my new message type .

5)Message deteremination Schema , Added my new message type to the list . Dint check manual only .

6)Defined the partner role.

The message type NEU was defaulting before i created the new message type , but now only the new is defaulting and NEU is not ?

[Former Member]

Sure looks like you followed all the steps. I don't see why the working messages type not getting included. If you remove the new message type that you created, is it going to work again for the NEU type? Is there something in the data that might have caused it to exclude the NEW type? Check the message determination log to see if there is anything that tells about it.

[Former Member]

Sure , let me remove the message type and see if it works for the NEU ...will also check the log and get back to you with the results .

Thanks

[Former Member]

Hi Srinivas,

Here is what i found out . I went to the PRD to see the settings that enable the NEU message to default . What i saw was though there was a Schema defined , but it wasnt assigned ( the field Proc was left blank ) , the checkbox for New Message determination is checked .

Now , If i assign the schema to the EV application , the NEU is somehow overriden by ZMOA ( this is the last entry in the schema definition ) ...??

[Former Member]

I have the procedure somethign like this.

10	1	NEU	Outline agreement	101
11	1	ZZZZ	Prt Outline agreemt	101
12	1	ZYYY	Fax Outline agreemt	101
20	1	AUFB	Dunning Ord Confirm	107
30	1	VNEU	Distribtd Contracts	101

As you can see, the schema has both NEU and some custom ones ZZZZ, ZYYY. Is this how it looks in your system? The standard message schema RMBEV1 is assigned to EV application here.

[Former Member]

Yes , it is exactly the same way . The ZMessage and the NEU are both based on the same req ie 101 .

I checked for PO settings too , i found that if ZNU succeeds on the condition , the NEU is overriden and not displayed .

However , yesterday for tcode me38 ( Sched Ag delivery Schedule change ) , i set it up the same way and it shows both LPET and Z message type .

[Former Member]

Then it is something in the data that is excluding it. See the outline agreement's message determination log and verify that.

What is your partner assignment? Are they both for the same partner? What transimission medium are they using?

See if you can manually insert NEU in the messages of the outline agreement, change mode.

[Former Member]

The partner assignment is :

For Zmessage : VN , CA.

For NEU : VN .

Zmess : transmission med : 5

NEU : transmission med , 1, 2 ( 1 - default ).

How do i see the message determination log ? After processing the message successfuly there is no log ( processing log ) , is that some other log u r telling or is it the same ?

Yes , i can manually insert the NEU ( it comes in the possible message type ) list .