Problem in Output Message types in PO

Hi Experts,
I created a PO of type (ZRTS) and i assigend message type as ALE its working fine and idoc genereted.
but when i am usign some other PO type its not working .
Here the Partner is same (VN-Vendor)
Pls help me ..

If you have created conditin record for all the document type in MN04 then it should work becuase doc type has nothing to do for printing config.
this is basically a condition record.
check your condition record

Similar Messages

Output Message Type

Hi Experts
For the Purchase Order & Outline can i maintain the same output message type ZNEU.
But the layout forms would be different.
Shouldn't be any issue right.
Rgds
MM

Hi,
You can have the same output type name ZNEU created for both PO & Outline agreement. But ZNEU for PO will be created under application EF & for Outline agreement it will be under application EV. Thus although the name will be same it will be under different applications. Moreover you can assign different forms & routines for PO & Outline agreement.
I hope this answers your question.

Material Document output message type.

Hi Experts
Please advise the details to be maintained in MN23 for the below message type.
Goods Issue Sub-con
Material Document output message type.
Trans./Event Type:
Print Version:
Print item:
Debit/Credit Ind:
Rgds
MM

SAP-MM1 wrote:
Hi Experts
>
> Please advise the details to be maintained in MN23 for the below message type.
>
> Goods Issue Sub-con
> Material Document output message type.
>
> Trans./Event Type:
> Print Version:
> Print item:
> Debit/Credit Ind:
>
> Rgds
> MM
Hi,
Trans./Event Type: WO(Goods Movement for Subcontracting)
Print Version:1(Individual Slip)
Print item: 3(GR/GI Slip for Subcontracting)

Creation Output Message Type for Scheduling Aggrement

Hi,
Please share the detail configuration for the Output message type for scheduling aggrement, i need to use ALE IDoc so that i can send this SA to SRM system.
Regards,
Pankaj

Hi,
Output determination process for Scheduling aggrement.
SPRO-IMG-Material Management-Purchasing-Messages-Output Control-
1)First create condition table based which becomes condition record for accessing the data.
2)Create access sequence to access the data or search the based on the conditoin record in sequence of the condition table.
3)Define your message type like print,fax etc.
Maintain the conditon record for the MN07 for the output type which new one you created.
Regards
Ravi Shankar.

Problems in output messages for PO.

Hi Experts,
We have a problems with output messages determination, if I have the PO without release approval the system send the output messages ( NEU ) I need that determination doesn't occurs when the po status is unapproved.
For Explo: I create the PO 45...01 with status unapproved, the system generate tehe messages ( NEU ) but doesnt send to destination, the send only happened when i make the realese.
There is a file with more details.
[http://www.easy-share.com/1904410163/POunapproved.doc]
Thanks,
Gustavo

Hi,
In the release strategy,if the indicator changeablity is 1 the system will not allow you to take repeat out put.
Solution is that you have to change the release indicator changeability to 6(SPRO>MM>Purchasing>Purchase order>Define release procedure for purchase order>Release indicator>Changeability).
Another option is that in the message output of the PO in further data change despatch time to 3 and take a repeat out put.
Also check,
SPRO > MM > PO > Release Procedure for PO > Release indicator > Changeability of Purchasing Document During/After Release as 2 for Release ID - G and save
And then Create go to chage mode of PO and repeat the messages
Regards,
Rahul.

Change flag deactivaion for PO output message type during change mode

Hello All,
WE are using automatic message output determination functionality for PO output type. This output type has been configured for creation and change mode under Fine tuning.
Two output type are configured, for example ZAAA is output type for ALE and output type ZBBB for archiving.
Here archiving functionality is used to transfer attachment from ERP system to SUS supplier portal as a pdf file. This is done via enhancement and the attachment transfer is working fine.
During creation mode both the output types are determined and successfully processed and as a result attachment is transferred to supplier portal which is absolutely correct. In the attachment all PO line item can be seen which works well.
Now I change the PO and add a new PO line item, system automatically default both the output type for change mode and upon saving both the output type are successfully processed.
Now here is the problem in change mode only the added PO line item is sent as an attachment to the supplier portal. Here the requirement is see all the PO line items including the once which were newly added.
Solution is if we uncheck the change flag for output type ZBBB during change mode then all the PO line item can be seen under the new attachment with new version.
Please let us know how this functionality can be acheived ... is there an user exit available.
We have a work around where we are running a background job every 3 mins and based on the last successfully processed message for output type ZAAA we are attaching first output type ZBBBfor archiving the changes and then ZAAA for sending the changes along with attachment to Supplier portal.However this solution is a temporary one , we need a concrete solution for this.
Please advise.
Thanks,
Yatin

Hello All,
Thanks for the reply,
But we cannot modify the existing print program as this print program is being used in different countries also.
We already know a solution that during change mode if we remove the change flag from output type ZBBB then all the PO line items along with the recent changes can be seen under the attachment under supplier portal.
The question comes now, how do we automate this processu2026 Is there any standard progam or user exit available.
Manually, if you add a message type ZBBB in ME22N tranasction for creation mode then all PO line item with recent changes get transferred but we need to automate this process for create and change PO transaction.
Thanks,
Yatendra

Two idocs are created for one output message type

hi all,
we are communicating our sap idocs to external system using ALE.It is working smoothly.
Our problem raises here,
.idocs are creating at the time of output type attachment for purchase orders.But rarely,two idocs are creating for one message type.It means two idocs are created for same Purchase order.It makes complications for the external system.
anyone can help me pls?
thnks in advance..........

thanks jurgen for ur reply,
jurgen, the second idoc is not an "ORDCHG",It is the replica of first idoc.This one has also "ORDERS" message type.The only difference between these idocs are the time.It means the difference between the time field segments of these idocs have only three(3)seconds difference.We think that its from the system error.If it is not from the system error pls give me the explanation.
thanks in advance.......

Output Message Type MAHN not getting picked up in PO

Hello Experts
   I have configured customized output type ZMAH (similar to MAHN) for reminder process. When I am creating PO this output type is not getting picked up automatically. If I am maintaining it manually I am able to send message for ME9F (Purchase Order) and ME91F (Reminder) successfully. Upon deremination analysis I am getting this message 502 " Output ignored (requirement 103 not fulfilled) ". Reminder are getting picked up from Purchase Value Key to PO.
Any help is appreciated.
Thanks
Ankit

Hello Tej
I have maintained output device but same result.
Here I am listing all parameters that I have used for configuration can anyone please take a look and let me know if I am missing anything
Steps for new Message Type for PO Reminder (ZMAH)
1.     Defined new Table 026 Purchasing Output Determination: Document Type
                                                    (ii) 027 Purchasing Output Determination: Purch. Org./Vendor for EDI
2.     Defined new access sequence Z515 Access Sequence for Archiving.
Following are parameters to the Access Sequence
Access Sequence Number = 1
Table = 026
Description = Purchasing Output Determination: Document Type
Requirement = 103
Exclusive = Yes (box checked)
Access Sequence Number = 2
Table = 027
Description = Purchasing Output Determination: Purch. Org./Vendor for EDI
Requirement = 103
Exclusive = Yes (box checked)
3.     Maintain Output Type ZMAH for PO
General Data
Access Sequence = Z515
Access to condition (Checked)
Multiple Issuing (Checked)
Change Output
Program = SAPFM06P
FORM Routine = ENTRY_NEU
Replacement of Text Symbol
Program = SAPMM06E
FORM Routine = TEXT_SYMBOL_REPLACE
Default Values
Dispatch Time = Send Immediately (when saving application)
Transmission Medium = External Send
Communication Strategy = 0001 (E-mail Document)
Processing Routines
Transmission Medium = 5 (External Send)
Program = SAPFM06P
Form Routine = ENTRY_NEU
Form = MEDRUCK
Partner Roles
Medium = External Send
Funct = VN
Name = Vendor
4.     Fine-Tuned Control: Purchase Order
Oprat. = 3
CType = ZMAH
Name = Output for Reminder
Short Text = Urging letter (expediter)/reminder
Update Print Related Data = Yes (checked)
5.     Maintain Message Determination Schema: Purchase Order
Procedure RMBEF1 (Purchase Order)
Step = 101
Cntr = 3
CTyp = ZMAH
Description = Output for Reminder
Requirement = 103
6.     Assign Schema to Purchase Order
Procedure RMBEF1
7.     Define Partner Roles for Purchase Order
Out. = ZMAH
Med = 5 (External Send)
Funct = VN
Name = Output for Reminder
Name = Vendor
8.     Test Condition Maintained in MN04 (Master Data)
Purch. Org. = 0001
Vendor = 101281
Partner Funct = VN
Medium = 5 (External Send)
Date/Time = 4 Send immediately (when saving application)
Output Device = LP01
Cover Page Text = Reminder PO number &EKKO-EBELN&
Also I have configured Purchasing Value Key, reminders are coming to PO correctly.
Thanks
Ankit

Output message type triggering for all

Hi,
I want the output messages to be triggered for particular Vendor and doc type with ALE config.
Now the config is such tht whenever the PO is created for doc type, the output type gets triggered for ALE partner .
So need guidance.
Thanks

hi,
Please check whether the access sequence attached to your Condition type has a condition table with Document type and vendor field, if not then you can add one or create a new Access sequence and attach it to you condition type.
Next you maintain the Condition Records for the doc type and vendor combination, and the system shall trigger the message type automatically.

Output message type not triggered for few POs

---PRs got created manually. then PRs converted into POs through background job (me59n).
( 25 PRs got created manually with same vendor and pur.org combination then all PRs converted into POs through ME59N. In that 20 PRs had message type automatically but remaining POs haven't got the message type )
Condition record exists with vendor/pur.org combination.
and all IMG settings are correct.
medium is 8 (special function).
and not able to replicate the issue in quality systems.
Please Advise.
Thanks in advance.

PRs will not get any message type, POs will get a message record.
How is the situation now?
Did you get 20 POs only, or do you have 25 POs where just 20 have a message record?
In the first case convert the PR manually to a PO manually and see if you get a message record. You should not enter anything manually, it is supposed to work without entering anything manually because it was meant for auto PO. In case you have to enter anything manually, then this might be an indicator why auto PO could not work.
if the latter case, then compare a PO with and without message record on the fields that should match with your condition record.
Do you expect the same message type for all POs, are they all in the same purchasing organisation?
Read and check what is mentioned in KBA 1829682 - Output type is not determined in Purchase order

CSS Output Message Types

We're syndicating spec data to an internal web service via CSS under 6.1. Specs are syndicated twice per GSM workflow to the same system, first as a "create" and then as an "update".
So far in testing we haven't seen anything other than ADD types being output even when the same publication is syndicated more than once. The general GSM workflow steps are like this:
1. Draft
2. Developmental (Syndicate here as "create")
3. Approved (Syndicate again here as "update")
We would expect the message type at the Developmental step to be ADD, and then have a message type MODIFY at the Approved step to make it easier for the middleware program to know what it's looking at. But in both cases the XML comes out as an ADD in the syndicationCommand type attribute, and shows "Add" types in the catalog response section of the publication for both responses.
I've tried using both the Initial Load and New publication types, but they both have the same results. The questions then, are:
1. What triggers CSS to output a publication message as a MODIFY versus an ADD?
2. Does the publication type selection make any difference to the system at all for internal syndication?
Thanks!

Doing External syndications handles this scenario by setting the type to MODIFY if it has already been syndicated. Your testing is showing that this isn't having the same behavior for Internal syndications.
You could write a custom handler (like mentioned in [this previous post|https://forums.oracle.com/forums/thread.jspa?threadID=2376907] ) which checks if the spec has an already syndicated TIP and outputs a MODIFY value. You could use the ExportExtensions framework to do this.

Output message type determination through MIGO

hello experts,
I am doing MIGO for goods reciept, it is creating material document and triggering output type attached to it (ZLCO).
Same thing when i am doing through an excel sheet (this excel application is calling a Z function module thats one looks is calling Standard BAPI BAPI_GOODSMVT_CREATE), this is creating material document but not trigger output type.
Output ZLCO is not created upon VGR thru Excel Upload.
What part of code should i provide to my Z function module so that it also trigger the Output type.
Thanks,
Sumit

PRs will not get any message type, POs will get a message record.
How is the situation now?
Did you get 20 POs only, or do you have 25 POs where just 20 have a message record?
In the first case convert the PR manually to a PO manually and see if you get a message record. You should not enter anything manually, it is supposed to work without entering anything manually because it was meant for auto PO. In case you have to enter anything manually, then this might be an indicator why auto PO could not work.
if the latter case, then compare a PO with and without message record on the fields that should match with your condition record.
Do you expect the same message type for all POs, are they all in the same purchasing organisation?
Read and check what is mentioned in KBA 1829682 - Output type is not determined in Purchase order

PO Output message types for different document types

Hi,
I wanted the system automatically generate the messages whenever a PO is created for different document types like NB,UB,Blanketorder, Pilot run.
These are the steps i did...plz advice any more steps to make this work
1. the output type I am using is NEU-purchase order
2. I have created condition records for document types NB,UB,PR etc
I was sucessfull in getting the messages automatically for the standard(NB) PO..but not for the other document types
Plz advice me how I can achieve this with further configurations
Thanks
SKid

If you have created conditin record for all the document type in MN04 then it should work becuase doc type has nothing to do for printing config.
this is basically a condition record.
check your condition record

Context handling problem in output message

Hi Experts,
I have an issue where the context is not properly handled:
<Material_Master>
<Material>
<LongText> -
>exists--->createif--->E1MTXHM Segment
<Language_Code>ES</Language_Code>
<Description>EF VEW CHANGED TEXT: GAS</Description> >mapwithdefault>Splitbyvalue(Each Value)>UDF>E1MTXLM Segment
                                         |->mapwithdefault>Splitbyvalue(Each Value)>UDF>Split by value---> TDLINE Element
</LongText>
<Language_Code>ES</Language_Code>
>No "Description" Field comes,but i get the next descriptionfield value(EF VE) into this context in the output idoc
</LongText>
</Material>
<Material>
<LongText>
<Language_Code>ES</Language_Code>
<Description>EF VEW CHANGED TEXT: GAS</Description>
</LongText>
<Language_Code>ES</Language_Code>
<Description>EF VEW CHANGED TEXT: GAS</Description>
</LongText>
</Material>
</Material_Master>
The UDF used here takes the length of the input string and divides into multiple of 5 and the remainder into the last E1MTXLM Segment.
Similar logic is implemented in "TDLINE" element
Output IDoc Format:
<E1MTXHM> Segment
    <E1MTXLM> Segment
    <TDLINE> Element
    </TDLINE>
    </E1MTXLM>
</E1MTXHM>
Thanks,
Sudhansu
Edited by: Sudhansukumar Behera on Aug 15, 2009 10:54 AM
Edited by: Sudhansukumar Behera on Aug 15, 2009 10:55 AM

Hello,
You need to use UDF for this:
UDF type is Context
Arguments:
input1
input2
HashMap map = new HashMap();
for(int a=0;a<input2.length;a++){
     if(!map.containsKey(input2[a])){
          map.put(input2[a],"");
for(int a=0;a<input1.length;a++){
     if(map.containsKey(input1[a])){
          result.addValue("true");
     else{
          result.addValue("false");
mapping is something like this:
input1 -> removeContext -> UDF -> target
input2 -> removeContext -> /
Hope this helps,
Mark

PO Output Message type to set default for two output (neu and z_mail)

Hi,
we have a requirement for two output( print output and external send) at the same time when the po saved or me9f, and me99 trigers. kindly guid me the procedure to do this setting in nace,mn04 and spro.
thanks..,

Hi
YOur condiation record should have correctly for that, Genaraly for Email it will ask more then one combination like PO document type and Porg, Doc type/Vendor/Plant
If condiation recocrd id correct then you can get automaitaly when you craete the PO
Tcode for Creation of condiation record is NACR
Bhima

Problem in Output Message types in PO

Similar Messages

Maybe you are looking for