Define Message Schema for Purchase Order

In this step, you define your message schema for the purchase order and assign it to the PO.

The allowed message types for each message application (new printout, expediter, etc.) are stored in a message schema. This enables the system to suggest the relevant message automatically in a PO. You must first define the message types and then enter them in a message schema.

Note

Only one schema and one message type can be assigned to the PO.

Recommendation

x To define a new message schema, copy a similar, already-existing schema and make any necessary changes.

x If you define your own message schema, the key should begin with the letter Y or Z, because SAP

keeps these name slots free in the standard system supplied.

Activities

1. Check to what extent you can use the message schemas included in the standard SAP System and to what extent you must change them. Also check the assignment of the message schema to the PO.

2. Define your message schema for the PO.

3. Assign your message schema to the message application of the PO. To do so, choose the step

Assign Schema to Purchase Order in the Customizing activity.

Partner Roles per Message Type

In this section you specify which partner roles are allowed for the message type in connection with each individual purchasing document.

If, when creating message records, you enter a partner role that is defined as invalid, the system will issue a warning.

Define Partner Roles for Purchase Order

In this step, you define the partner roles for the message types.

Activities

Specify which partner roles are allowed for the relevant message type.

Assign Output Devices to Purchasing Groups

In this step, you assign an output device to your purchasing groups.

Prerequisites

1. You have defined your purchasing (buyer) groups.

2. In the table of valid output devices, you have defined the printers to which purchasing groups are

assigned.

Fields Relevant to Printouts of Changes

In this step, you define:

􀁸 Whether and in which purchasing documents a field is relevant to printouts of changes (change

notices).

􀁸 Which texts are included in change notices

Text output can be controlled via a text number (direct assignment) or a routine (indirect

assignment).

Example of the determination of change texts

Text number

In the standard system supplied, the change text "Unit of measurechanged" (text no. P5) is directly assigned to the base unit (MEINSfield):

If the base unit is changed in an already printed RFQ, purchase order,or outline agreement, the change text "unit of measure changed" is included in the change notice (printout of changes).

Routine

In the standard system supplied, the deletion indicator (LOEKZ field)is assigned to routine 3, which controls the outputting of the change text.

Routine 3 checks whether an item of a purchasing document hasbeen deleted or blocked. If the item has been deleted, the change text"Item cancelled" (S3-L) is included in the printout of changes. If the item has been blocked, the change text "Item blocked" (S3-S) is printed.

Recommendation

SAP recommends working with the settings of the standard system. In this case, you need take no further action.

Activities

If you wish to define further fields as relevant to change notices, youmust carry out the following activities:

1. Enter the table and field names

2. Select the document categories for which the field is to be relevant tochange notices.

3. Assign a text number or routine

Note

If you specify a text number and a routine, the routine will receivepreferential treatment.

Further Notes

􀁸 You maintain the change texts and their numbers in Customizing forPurchasing under Messages -

> Texts for Messages -> Define Texts for -> Document Printout ->

Change Texts.

􀁸 If you have specified your own routine, you can evaluate it in the userexit

EXIT_SAPLMEDRUCK_001.

ABAP Transaction Codes

USMM	Pressing F8 will display all hotpacks applied.
SEARCH_SAP_MENU	Show the menu path to use to execute a given tcode. You can search by transaction code or menu text.
DI02	ABAP/4 Repository Information System: Tables.
LSMW	Legacy System Migration Workbench. An addon available from SAP that can make data converstion a lot easier. Thanks to Serge Desland for this one.
OSS1	SAP Online Service System
OY19	Compare Tables
SM13	Update monitor. Will show update tasks status. Very useful to determine why an update failed.
S001	ABAP Development Workbench
S001	ABAP/4 Development Weorkbench.
S002	System Administration.
SA38	Execute a program.
SCAT	Computer Aided Test Tool
SCU0	Compare Tables
SE01	Old Transport & Corrections screen
SE03	Groups together most of the tools that you need for doing transports. In total, more than 20 tools can be reached from this one transaction.
SE09	Workbench Organizer
SE10	New Transport & Correction screen
SE11	ABAP/4 Dictionary Maintenance SE12 ABAP/4 Dictionary Display SE13 Maintain Technical Settings (Tables)
SE12	Dictionary: Initial Screen – enter object name.
SE13	Access tables in ABAP/4 Dictionary.
SE14	Utilities for Dictionary Tables
SE15	ABAP/4 Repository Information System
SE16	Data Browser: Initial Screen.
SE16N	Table Browser (the N stands for New, it replaces SE16). Provided by Smijo Mathew.
SE17	General Table Display
SE24	Class Builder
SE30	ABAP/4 Runtime Analysis
SE32	ABAP/4 Text Element Maintenance
SE35	ABAP/4 Dialog Modules
SE36	ABAP/4: Logical Databases
SE37	ABAP/4 Function Modules
SE38	ABAP Editor
SE39	Splitscreen Editor: Program Compare
SE41	Menu Painter
SE43	Maintain Area Menu
SE48	Show program call hierarchy. Very useful to see the overall structure of a program. Thanks to Isabelle Arickx for this tcode.
SE49	Table manipulation. Show what tables are behind a transaction code. Thanks to Isabelle Arickx for this tcode.
SE51	Screen Painter: Initial Screen.
SE54	Generate View Maintenance Module
SE61	R/3 Documentation
SE62	Industry utilities
SE63	Translation
SE64	Terminology
SE65	R/3 document. short text statistics SE66 R/3 Documentation Statistics (Test!)
SE68	Translation Administration
SE71	SAPscript layout set
SE71	SAPScript Layouts Create/Change
SE72	SAPscript styles
SE73	SAPscript font maintenance (revised)
SE74	SAPscript format conversion
SE75	SAPscript Settings
SE76	SAPscript Translation Layout Sets
SE77	SAPscript Translation Styles
SE80	ABAP/4 Development Workbench
SE81	SAP Application Hierarchy
SE82	Customer Application Hierarchy
SE83	Reuse Library. Provided by Smiho Mathew.
SE84	ABAP/4 Repository Information System
SE85	ABAP/4 Dictionary Information System
SE86	ABAP/4 Repository Information System
SE87	Data Modeler Information System
SE88	Development Coordination Info System
SE91	Maintain Messages
SE92	Maintain system log messages
SE93	Maintain Transaction.
SEARCH_SAP_MENU	From the SAP Easy Access screen, type it in the command field and you will be able to search the standard SAP menu for transaction codes / keywords. It will return the nodes to follow for you.
SEU	Object Browser
SHD0	Transaction variant maintenance
SM04	Overview of Users (cancel/delete sessions)
SM12	Lock table entries (unlock locked tables)
SM21	View the system log, very useful when you get a short dump. Provides much more info than short dump
SM30	Maintain Table Views.
SM31	Table Maintenance
SM32	Table maintenance
SM35	View Batch Input Sessions
SM37	View background jobs
SM50	Process Overview.
SM51	Delete jobs from system (BDC)
SM62	Display/Maintain events in SAP, also use function BP_EVENT_RAISE
SMEN	Display the menu path to get to a transaction
SMOD/CMOD	Transactions for processing/editing/activating new customer enhancements.
SNRO	Object browser for number range maintenance.
SPRO	Start SAP IMG (Implementation Guide).
SQ00	ABAP/4 Query: Start Queries
SQ01	ABAP/4 Query: Maintain Queries
SQ02	ABAP/4 Query: Maintain Funct. Areas
SQ03	ABAP/4 Query: Maintain User Groups
SQ07	ABAP/4 Query: Language Comparison
ST05	Trace SQL Database Requests.
ST22	ABAP Dump analysis
SU53	Display Authorization Values for User.
WEDI	EDI Menu. IDOC and EDI base.
WE02	Display an IDOC
WE07	IDOC Statistics