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)

Similar Messages

Material Document Output Message

Hi
I cutomize the Mat.Doc Output Message WE01 to ZE01.
In OMJ3 I already removed the WE01 for the new plant.
However still in the Plant#2000 material document picks up both message
Where else i should remove ?
Thanks
MM

Hi Garapati
Output WE01 is already in use at other plants (ex; 1000) using different forms.
ZE01 which is to be used for plant 2000.
So, I can't delete in Output Determination or NACE/T.
I thought if I dont maintain the WE01 output type in OMJ3 for Plant 2000, suppose to not appear and only appear the ZE01.
But now both appears.
Rgds
MM

Not able to create a material document with movement type 103

I am not able to create a material document with movement type 103,
The system is populating the value as 101 .
How do I create a matdoc with movement type 103?

What is the error you receive? Please specify with message number.
On MIGO, you need to change the default value mvmt type value to 103 before you enter the PO number to be able to do 103.
Once this defualt value is set, you can enter the PO and item number in the document number fields and proceed with 103.
But you cannot change the mvmt type for already entered items from 101-103 or vice versa.
I think the 101-103 and 103-101 mvmt type conversion message is standard error message

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.

Find Material Document with Movement type 103 for material document 105

Hi experts,
In PO History, I have three line items with movement type 103 (Blocked Stock) and one with movement type 105 (From blocked stock to unrestricted stock). I would like to know the material document with movement type 105 document that has the movement type 103.
Regards,
Abdullah

Hi,
you can get the material documents (mblnr) for the movement type(bwart) in table AUFK.
But i think you need to pass some other data along with bwart like matnr or aufnr for getting the correct mblnr.
Regards,
Chaitanya

Materail recevice with referance to material document with mvt type 303

Hi Guru:
In MB1B we are creating mateiral document with movement type 303 from one plant to other plant.
Now same material we need to receive in other plant with movement type 305 in same T code Mb1B.
Now as per user requirement if there is number of item are coming in material document which is generate with movement type 303, why we need to give all material, qty, batch again in MB1B movement type 305,
while we are receving same material in plant.
In MB1B there is link to create material document with referance to material document but we can use this facility for creating new material document for movement type 303 of same mateiral, qty and batch.
Please suggest is there any way to use this 303 movement type material document with movement type 305.
Thanks.
Virendra
09887603301

Hi
In my opinion in MB1B you can not have Material Doc. as a ref. Doc. for M.Type: 305...
But for MIGO transaction you can have Material doc. as a ref. doc. for M.Type: 305
Goto ---> OLME ---> Settings for Enjoy Transaction ---> Settings for Goods Movements -
> Settings for Transactions and Referance Documents ---> There...for MIGO_TR...Transfer Posting ---> Referance Documents ---> For your M.Type: 305 assign Material Document as a Referance Documnt...
Reward if useful
Regards
S.Baskaran

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 type".

Hi,
after setting the system with the following parameters (trx MN21):
Output type: WE01,
Trans/Event type: WE
Print version: 1,2,3
Print item: 6
Output type: WE02,
Trans/Event type: WE
Print version: 1,2,3
Print item: 6
Output type: WE03,
Trans/Event type: WE
Print version: 1,2,3
Print item: 6
output types WE01, WE02, WE03 are not created automatically
What is the difference between print item 1 and 6 ?
Can't understand why
Best regards

hi,
maintain one output type we03 thru transaction mn21 with the following data
Event type:WE
Print version :3
Print indicator: 1
assign the output type to the printer.
1- material document print out
6- GI/ GR Document print out
Regards,
velu

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

Creation of Material Documents With Mvt Type

On Performing Post Goods Issue (PGI) in one Plant in case of Plant to Plant Dispatches, there should be Inbound delivery created for already created Purchase Order (PO). In addition after creation of inbound delivery, there should be material document created with 103 movement. This Material document is triggered when the inbound delivery is saved. Once Warehouse processes are finished, then Post Goods Receipt (PGR) happens, so 101 Movement Type happens for Purchase Order. PGR document should trigger one more material document with 104 movements; this document is reversal for material document with 103 movement type.
can any one suggest to enhance SAP for this?
Moderator message : Requirements dumping is not allowed, show the work you have already done. Thread locked.
Edited by: Vinod Kumar on Oct 21, 2011 5:18 PM

Hi Nitin,
Before creating the Service type of product, you have to define the Base category for Service type product. Generally the category for service will be created under the R3 hierarchy R3PRODSTYPE. You can create this category using the TCode:
COMM_HIERARCHY. Here you have to select the product type as Service and have to assign the set types to the category.
You can create a service product using the transaction : COMMPR01 -> Click on Service ICON -> Select the Category for Service Type. Then fill in the details for Service Product description, Service ID(Based on number range settings for products), Language.
Also fill other details like Base Unit of measure, Pricing condition for different sales areas for the service product.
Since you are using CRM7.0, you can do all these activities using a POWER USER role.
For more information about Set types and hierarchies please refer the following help link:
http://help.sap.com/saphelp_crm70/helpdata/EN/46/57672501a208e7e10000000a114a6b/frameset.htm
Hope this helps!
Regards,
Chethan

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.

FI document amount of material documents of movement type 413

Hi
When I create a material document (413) transfer post from sales order stock to another sales order stock. SAP automatically generate a FI documents. So, my question is that the amount of FI document is how to be calculated?
thanks
Henry

Hi,
Please check below link which will provide solution for youe query. Thanking you.
How to get print out for MIGO doc with movement type 701, 702 and 551, 552

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.......

Material Document output message type.

Similar Messages

Maybe you are looking for