Scribd
Upload
15 views18 pages

Sap Po - Pi

Uploaded by

aaamir khan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
15 views18 pages

Sap Po - Pi

Uploaded by

aaamir khan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 18

SAP PO/PI

Message output determination for po


Message output determination for po
Message Output Determination is the process in all organizations, where purchasing
department can send their PO, Contract, and Schedule Agreement & Service Po like
documents to the vendors. For that consultants make configuration setup to the vendors according
to some parameters like document type Purchase organization, plant, company code, material and
so on. To do the output we have do the following configuration steps.

 Path: SPRO > IMG > Material Management > Purchasing > Messages > Output control

1. Condition table : in this step we will maintain group parameters in number of tables

6360959192 www.tagskills.com support@tagskills.com


 click on create condition table

 Maintain number to create the condition table

 Select the required fields to the condition tables

6360959192 www.tagskills.com support@tagskills.com


 For the table 511 I selected fields Purchase Group, Purchase Org & Document type

 So table 511 created.

 And same I will create another table 512 with fields plant, Purchase org & Purchase
document type

6360959192 www.tagskills.com support@tagskills.com


 So I crated two condition tables 511 & 512

2. Access Sequences : we will create one access sequence and assign condition tables which I
have created already in above steps

 Click on New entries

 Enter the Access sequence code and description & save

6360959192 www.tagskills.com support@tagskills.com


 select the access sequence and click on the accesses

 Click on New entries

 Maintain the two tables 511 & 512 which we have created above

 Again select the table one after other and field map them

6360959192 www.tagskills.com support@tagskills.com


 Filed mapping done for the table 511 like do for 512 and save

3. Message Types: we will define the message type

 select maintain message type for PO

6360959192 www.tagskills.com support@tagskills.com


 In this step I am going copy standard message type NEU and customize

 Here I am creating message as SEU and maintaining Access sequence which I have created
ASSM

6360959192 www.tagskills.com support@tagskills.com


 Select and click on mail title and texts here we will check the language

 like English other language also available

 And Processing routines : we have smart forms, forms , form routine


Program and type of medium
But in our case we are performing the print output medium.

6360959192 www.tagskills.com support@tagskills.com


 And the partner rules like to whom we going to send vendor, ordering address &
delivering plant. In this case we going triggering to the vendor

 After definition of message type we need to Fine-Tuned Control to the Purchase Order

 We will maintain it for the operation 1 i.e. for the new print or any other output & 2 for the
any change or second time output for the same print or any other output

6360959192 www.tagskills.com support@tagskills.com


 Maintain and save

4. Message Determination Schemas: here we will define the message schema determination

6360959192 www.tagskills.com support@tagskills.com


 Select the Maintain Message Determination Schema: Purchase Order

 Standard message schema is RMBEF1

 Copy same & customize or maintain new schema with new entries, here I am going to
maintain the defined message type in the same message schema and save.

 Here is our newly added message type SEU in standard message schema RMBEF1.

6360959192 www.tagskills.com support@tagskills.com


 Here ensure that your message schema assigned with purchase order or not

 Yes assignment is done perfectly with Purchase order

 And last and most important step is to maintain condition record for output in NACE or
MN04 for Purchase order output
 Got NACE select EF and select condition record

6360959192 www.tagskills.com support@tagskills.com


 Select your message type SEU

 Here your condition tables which you have defined 511 & 512, and assigned to access
sequence ASSM and I am selecting first one and create the condition record

6360959192 www.tagskills.com support@tagskills.com


 Here I am maintaining the combination

 And the select same and maintain the communication

 And here maintain output device LP01 and active the checkmark for the both print
immediately & release after output and then save.

 Condition record maintained successfully the last we have test the output for the purchase
order

6360959192 www.tagskills.com support@tagskills.com


 Crate the PO for combination which we have maintain in the condition record
ME21N

 Standard PO created under the number 4500019073

 Save the PO and now go and check the messages in the header
 So the output triggered successfully from the message type SEU for print output

6360959192 www.tagskills.com support@tagskills.com


 And check the print preview i.e. smart form

6360959192 www.tagskills.com support@tagskills.com


© Copyright TagSkills. The copyright in this work is vested in
TagSkills. Please note and abide by copyright laws. This
presentation is for educational purposes only, all logos, photos,
and information, etc used in this Presentation is the property
of TagSkills. SAP is a registered trademark of SAP AG in
Germany and many other countries. We are NOT associated
with SAP.

6360959192 www.tagskills.com support@tagskills.com

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy