Things to be looked for

Transactions
 search_sap_menu - Finds the menu path to a transaction - Can either type in TX code in the
search criteria or a description- ie. 1st try SE38 and then ABAP.... the returned result is 'bottom to
top'.

EDI Specific Transactions

 VOE1 Translation between EDI categories and SD item categories
 VOE2 Table EDSC view. Customer link to sales area detail
 VOE3 Table view EDPVW. Add partner types that will be transferred to the IDoc
 VOE4 Table view EDPAR. Link external partner number with our internal number
 WEDI EDI Administrator Menu
 BALE Idoc Administration
Scheduling agreements
 OVA9 Create entries for each sold-to customer for which you will receive EDI schedule releases.
At implementation, the only field that needs to be maintained is "Check PO number," which
causes SAP to make sure that the PO number sent on the release matches the PO number on the
schedule agreement. This transaction updates table T663A. SAP will not post an EDI schedule
release, if this record is missing.
 OVAI Create entries for each Vendor / Partner description combination. (Vendors must match
sold-to Acct. at Cust., and Partner descriptions must match ship-to Partner descriptions.) This
transaction updates table T661W. SAP uses this table to determine the schedule agreement sold-to
partner.
 OVAJ If you would like SAP to post schedule requirements using discrete dates only, instead of
weekly and/or monthly buckets, you can indicate the days of the week that you deliver to this
customer. SAP will divide the customer's quantity for a week or month evenly into the days of the
week specified by the distribution function code. This code must be sent in the DELINS IDoc in
field E1EDP16-ETVTF.

IDoc Transactions
 WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business
application detail contained within the contents of a segment.
 WE05 View IDocs
 WE19 EDI test tool. Use to test inbound Function module changes.
 WE20 Partner profile configuration. Add partner detail together with inbound and outbound
relationships. We also incorporate message control on the outbound IDocs. Utilize the
organizational units to trap functional errors for further processing
 WE30 Create IDoc extension type
 WE31 Segment create
 WE57 Assign function module to logical message and IDoc type
 WE60 IDoc type documentation tool
 WE82 Link Release detail to Extension IDoc Type
 BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner
combinations
 BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use
BD88 in prior versions)
 BALA ALE Application Distribution
 BALM ALE Master Data Distribution
Output determination
856 - ASN
 V/36 Maintain output determination for deliveries (Output determination procedures). V10000
(Header output) has condition type LAVA (usually with requirement 1 NB: Use V/84 – V7ALLE –
SHAD for grouped ASNs. I.e. Group deliveries into shipments
 VV21,VV22,VV23 Create output condition records for shipping. LAVA – WE (Partner function) -
We must add each new partner with VV21
 VL71 Reissue output for deliveries
810 - Invoice
 V/54 Maintain access sequence for billing documents
 VV31,VV32,VV33 Create condition records for billing documents. (RD00 – RE Billing party)
 VF31 Reissue output for billing documents
855 – Order Response
 V/30 Sales document output types (BA00)
 V/48, V/32, V/43 Maintain access sequence for sales documents
 VV11,VV12,VV13 Create condition records for sales documents. (BA00 – SP Sold to party)

Requirements coding
 V/27 Create code to check requirements for output control. Used to check ZBA0 against BA00
output.

Sales & Distribution

Sales order / Quote / Sched Agreement / Contract
 VA02 Sales order change
 VA05 List of sales orders
 VA22 Quotation change
 VA32 Scheduling agreement change
 VA42 Contract change
Billing
 VF02 Change billing document
 VF11 Cancel Billing document
 VF04 Billing due list
 FBL5N Display Customer invoices by line
 FBL1N Display Vendor invoices by line
Delivery
 VL02N Change delivery document
 VL04 Delivery due list
 VKM5 List of deliveries
 VL06G List of outbound deliveries for goods issue
 VL06P List of outbound deliveries for picking
 VL09 Cancel goods issue
 VT02N Change shipment
 VT70 Output for shipments
General
 VKM3, VKM4 List of sales documents
  VKM1 List of blocked SD documents
 VD52 Material Determination

Workflow
 SWEAD Event queue administration
 SWE2 Event type linkages
 SWE3 Event linkages
 PPOME Organizational Unit Maintenance
 SWE5 Consistency Checks for Event Linkages
 SWUD Workflow Diagnostic Tool

General
The following section provides detail on other useful SAP areas.
Create delivery via transfer orders
Once the order is saved proceed through the following steps. The process assumes the item has values in
the warehouse bin.
 VL04 Delivery due list. Run the delivery due with your order number to create the delivery
 LT03 Create Transfer Order. EG. Warehouse: 101 and enter. Picking background. Save
The Transfer order should now be saved. It now needs to be confirmed.

 In LT03 go to menu option Transfer Order -> Confirm – Transfer Order

 Enter

 Save
The transfer order is now confirmed.
 VL02N Delivery change. EG: Edit the delivery to do the following Pack – External customer
material number = COO. External delivery number – Waybill number. BOL – Transport tag.
Carrier – Header partner – SP (E.G. FXP). Tracking number = Packing Unit
Purchase Orders
 ME22N PO Change
 ME57 Create PO from purchase requisition
ATP
 CO09 Availability overview
Goods Movement
 MIGO Post goods receipt
 MB51 Material document list
 MB01 Goods Movement
Other
 MD04 Material Requirements. Shows material requirements and releases against materials
 SE38 ABAP Editor. Used to modify ABAP programs
 SM01 Transaction list. Lock transactions in the system. Also a good tool to see what transactions
are available
 SHDB Transaction recorder (BDC)
 CMOD User exit \ project tool. Coordinates your changes into projects for the purpose of
activating all user exits for a particular project. A user exit needs to be modified before it will work
  SE16 Table contents display
 SOST View mails sent externally from SAP
 SU53 Check authorization object
 SQVI Table Quickviewer – Used to created quick client dependent reports
 ST22 ABAP Dump Analysis
 ST01 System trace
 ST11 Display developer trace
 ST05 SQL Trace
 SM21 System log
 ST22 Display short dumps
 SM12 Display locked entries

Programs
 List of ABAP Reports

Idoc
 RBDAPP01 Post inbound Idocs to application documents
 RBDAGAI2 Re-processing of IDocs after ALE input error
 RBDAGAIE Reprocessing of edited IDocs
 RBDMANIN Start error handling for non-posted Idocs
 RSEINB00 Idoc inbound processing by file
 RSEOUT00 Process outbound IDocs

General
 RV80HGEN Report 'RV80HGEN' for including customer-specific routines in the SAP standard
source code is not included automatically as an XPRA in the object list of the transport request.
See OSS note 0385067. This report needs to be run in target clients once you have implemented a
custom requirements definition.
 RSWUWFML Report that interrogates the Workflow inbox, based on certain selections, and then
forwards a notification to the respective users that they have email waiting in the SAP system. The
auto-forwarding assignment of an email address to a user can be accomplished by the
administrator and tx: SO36 or by the user themselves using tx: SO13. Use tx: SOST to view email
status’ sent from SAP.
 RHSOBJCH Corrects the following error in workflow customizing:
Transport object PDST
Information Table SOBJ is consistent as regards key tables
***Error*** Table HRP1600 Not an entry in table SOBJ
Information Table SOBJ is consistent as regards PAD tables
See note 134311 (point 2). Note 60801 also recommends the same steps regarding RHSOBJCH.
 RSPO0075 Run report RSPO0075 to activate access method M for device types.

REKH0004 SAP demo program that shows how to do 2D, 3D, and 4D graphics.
RGUGBR00 Substitution/Validation utility
RHGEN00 Regen PD and PA inconsistencies
RHGRENZ0 Delimit IT1000 and related 1001s. Program will delete any 1001 infotypes whose start date
is after the delimit date.
RHGRENZ1 Extend the end date on delimited records. Very useful when you delimit a bunch of records
incorrectly, and need to change the end date.
RHGRENZ2 Delimit IT1001 only.
RKCTSEAR Search source code for up to two strings. Also see RSRSCAN1 and
RPR_ABAP_SOURCE_SCAN. RPDTRA00 List all HR transactions.
RPR_ABAP_SOURCE_SCAN Search ABAP code for a string. Has many more options for selecting the
ABAPs to search than RSRSCAN1 or RKCTSEAR.
RPUAUD00 HR Report to list all logged changes for an employee. Uses the PCL4 Audit Cluster.
RPUAUDDL HR Report to delete audit data from the PCL4 Audit Cluster.
RPUDELPN Delete all info for an employee number, including cluster data and infotypes
RPUP1D00/10 View/Delete data from PCL1 Cluster
RPUP2D00/10 View/Delete data from PCL2 Cluster
RPUP3D00/10 View/Delete data from PCL3 Cluster
RPUP4D00/10 View/Delete data from PCL4 Cluster
RSABAPIV Mass print/display of ABAP/4 help text
RSAVGL00 Table adjustment across clients
RSBDCBTC Submit a BDC job with an internal batch number and wait for the end of the batch input
session. RSBDCDRU Prints the contents of a Batch Input session. No options for error transactions only.
RSBDCOS0 Execute UNIX commands. Looks similar to the old SAPMSOS0 program that disappeared in
3.0 RSBDCSUB Release batch input sessions automatically
RSBTCDEL Clean the old background job records
RSCLTCOP Copy tables across clients
RSDBCREO Clean batch input session log
RSINCL00 Extended program list
RSORAREL Get the Oracle Release
RSPARAM Display all instance parameters
RSPO0041 Removing old spooling objects
RSRSCAN1 Search source code for a given string. Will also search includes. Also see RKCTSEAR and
RPR_ABAP_SOURCE_SCAN.
RSSNAPDL Clean the old ABAP error dumps
RSTBSERV Compare a contents of a table between clients
RSTXFCON Converts SAPScript page formats
RSTXSCRP Save a SAPScript layout set to disk, and load it back into SAP.
RSTXSCRP Transport SAPscript files across systems
RSTXSCRP Upload and download SAPScript layout sets
RSTXTPDF4 Pass the spool number of a report's output to this program to have the output converted to
PDF format.
RSTXTRAN Add standard texts to a transport so they can be moved between systems.
RSUSR003 Check the passwords of users SAP* and DDIC in all clients
RSUSR006 List users last login
RSWBO052 Change development class of a sapscript (provided by Alan Cecchini)
RSWBO060 put objects into a request and transport it to any other system

Why implement EDI?

 Improves data accuracy: You can eliminate the need to re-enter data from paper documents and
thus prevent potential data entry errors. It is estimated to be one-tenth the cost of handling its
paper equivalent.
 Reduces technical complexity: With EDI, companies use standardized data formats to exchange
documents. EDI allows companies using different systems to achieve computer-to-computer
electronic exchange of business documents.
 Lowers personnel needs: EDI can help companies reduce the need for personnel involved in
paper business transaction processing.

 Accelerates information exchange: The lead time between start and completion of order
processing is greatly reduced. By timeous scheduling companies can plan production more
accurately and thus reduce stock inventories.
IDOC Processing

Takeaway:
To comprehend how SAP can work with multiple systems, you must understand IDocs. This overview of
IDoc terminology and how IDocs work in an enterprise will clarify the process.

--------------------------------------------------------------------------------

SAP’s presence in the IT world is justified by a central premise: It turns a company’s many individual
systems into one, big supersystem. More than a linking together of applications, SAP’s implementation
causes a redirection of the flow of information through a company and its partner companies that enhances
the potential of its business functions.

This flow of information is enabled by a core element in SAP technology: the Intermediate Document, or
IDoc. Technically, the IDoc is an example of Electronic Data Interchange (EDI). Unlike conventional EDI,
IDocs are not based on a descriptive language.

The IDoc concept borrows the best features of EDI and combines them with the best features of
conventional transaction file formats. The result is a lean data transport mechanism that is the engine of
SAP data flow, tying together applications, databases, companies, and networks. Here is a look at the
makeup of IDocs within the application architecture.

Form and content: IDoc terminology

As is often the case with proprietary technologies, SAP assigns specific, object-oriented meanings to
familiar terms. When referring to IDocs, the term document refers to a set of data comprising a functional
group of records with a business identity. (For example, all the data in a purchase order, or all the profile
information of a supplier in a supplier master record.)

A message refers to the contents of a specific implementation of an IDoc; it’s a logical reference. This
differs from a reference to the IDoc itself, which specifies the message’s physical representation. Think of it
this way: If you’re watching a parade pass by, the mayor waving to the crowd from his limousine is the
message, and the mayor’s limousine (which is specific to the mayor) is the IDoc. You’re building a logical
object, and the IDoc is both its container and the vehicle that moves it.

The IDoc control record

Each IDoc has a single control record, always the first record in the set. The structure of this record
describes the content of the data records that will follow and provides administrative information, such as
the IDoc’s functional category (Message Type/IDoc Type), as well as its origin (Sender) and destination
(Receiver) as in conventional EDI (see Figure A).
Figure A
IDOC number Sender Receiver Port Message type IDoc type
1234567890 R3NYC R3LA FILE INVOICES INVOICE01

Layout of an IDoc control record

This “cover slip” format informs the receiving system of the IDoc’s purpose, and the receiving system uses
it to determine the correct processing algorithm for handling the arriving IDoc.

Data records
The data records following the control record are structured alike, including two sections: a segment
information section and a data section.

In the first part of a data record, the segment information section describes the structure of the data that
follows, for the benefit of the IDoc processor. There is a segment name (like an EDI segment identifier) that
corresponds to a data dictionary structure to which the IDoc processor has access. The remaining
information is useful for foreign systems, such as a partner company’s Oracle system, which has no such
data dictionary.

The second part of the record is the data itself, a storage area of 1,000 characters.

Status records
If you’ve ever ordered a package from a faraway location and tracked its progress using the Internet-based
tracking utilities now provided by most major parcel carriers, you’re familiar with the list of stops and
transfer points through which a package passes on its way to you.

This collection of records is exactly what you’ll see in an IDoc that has begun its work. Following the data
records in an IDoc, status records accumulate as an IDoc makes its way from one point in a process to
another.

Typically, an IDoc will acquire several of these records as its does its job. They are simple records,
consisting of a status code (there are more than 70 codes, covering a broad range of conditions and errors),
a date/time stamp, and some additional status information fields for system audit purposes. In addition, as
errors occur in the processing of an IDoc, status records (see Figure B) are used to record these errors and
the date/time of their occurrence.
Figure B
(Display Status Record)
IDoc number 0000000000123456
Direction 1 Outbound
Status information
38 IDoc archived
(additional descriptive text)
Log time
Date 6-30-02
Time 14:35:21
Portion of IDoc status display

Plant Maintenance (PM)

Stephan Nilsson was kind enough to share some PM transactions. Stephan
Create Plant Maintenance Order
Nilsson was kind enough to share some PM transactions. IW31

IW32 Change Plant Maintenance Order

IW33 Display Plant Maintenance Order

IW34 Create Notification Order

IW51 Create Service Notification

IW52 Change Service Notification

IW53 Display Service Notification

Create Service Notification

IW54
:Problem notification

Create Service Notification

IW55
:Activity Request

Create Service Notification

IW56
:Service Request

Assign deletion Flag to Completed

IW57
Service Notifications

Change Service Notifications:

IW58
Selection of Notification

Display Service Notifications:

IW59
Selection of Notification

Production Planning
Tymon Kerste has provided me with these PP tcodes. Tymon Kerste has provided me
Create Production Order
with these PP tcodes. C001

C005N Collective Release

C011N Time Ticket

C012 Confirmation - Collective

C013 Confirmation - Cancel

Production order information

C00IS
system

Reprocess Goods
C0GI
Movements

C223 Maintain production version

General Notes
You can execute the following commands in the transaction code (tcode) field with Enter. You will find some useful
transaction codes below to work in tandem with the following commands:
To call a transaction - In the same session (window) Enter: /nxxxx (xxxx = transaction code). - In an additional
session, Enter: /oxxxx (xxxx = transaction code).
If you enter this function before any of the tcodes below, you are able to break out of your current screen/business
and begin a completely new session. Otherwise, the current business process has to be terminated, and return to the
initial user screen (the main menu) has to be initiated before entering tcode spro). /o tcode saves you the effort of
having to do this.
To end the current transaction Enter: /n. Caution: Unsaved changes are lost without warning
To delete the current session. Enter: /i.
To generate a session list Enter: /o.
To log off from the system Enter: /nend.
From John O'Meara
OSS Note 0026171 has additional information on OKCodes in SAP, and is a very useful read

BASIS/ABAP
USMM Pressing F8 will display all hotpacks applied.

SEARCH
_SAP_M Show the menu path to use to execute a given tcode. You can search by transaction code or menu text.
ENU

DI02 ABAP/4 Repository Information System: Tables.

Legacy System Migration Workbench. An addon available from SAP that can make data converstion a lot
LSMW
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. (from john.omeara@syskoplan.ie)

S002 System Administration. (from john.omeara@syskoplan.ie)

SA38 Execute a program. (from john.omeara@syskoplan.ie)

SCAT Computer Aided Test Tool

SCU0 Compare Tables

SE01 Old Transport & Corrections screen

Groups together most of the tools that you need for doing transports. In total, more than 20 tools can be
SE03
reached from this one transaction.

SE09 Workbench Organizer

SE10 New Transport & Correction screen

ABAP/4 Dictionary Maintenance SE12 ABAP/4 Dictionary Display SE13 Maintain Technical Settings
SE11
(Tables)

SE12 Dictionary: Initial Screen - enter object name. (from john.omeara@syskoplan.ie)

SE13 Access tables in ABAP/4 Dictionary. (from john.omeara@syskoplan.ie)

SE14 Utilities for Dictionary Tables

SE15 ABAP/4 Repository Information System

SE16 Data Browser: Initial Screen. (from john.omeara@syskoplan.ie)

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

Show program call hierarchy. Very useful to see the overall structure of a program. Thanks to Isabelle
SE48
Arickx for this tcode.

Table manipulation. Show what tables are behind a transaction code. Thanks to Isabelle Arickx for this
SE49
tcode.

SE51 Screen Painter: Initial Screen. (from john.omeara@syskoplan.ie)

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. (from john.omeara@syskoplan.ie)

SEARCH
From the SAP Easy Access screen, type it in the command field and you will be able to search the
_SAP_M
standard SAP menu for transaction codes / keywords. It will return the nodes to follow for you.
ENU

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. (from john.omeara@syskoplan.ie)

SM31 Table Maintenance

SM32 Table maintenance

SM35 View Batch Input Sessions

SM37 View background jobs

SM50 Process Overview. (from john.omeara@syskoplan.ie)

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/C
Transactions for processing/editing/activating new customer enhancements.
MOD

SNRO Object browser for number range maintenance. (from john.omeara@syskoplan.ie)

SPRO Start SAP IMG (Implementation Guide). (from john.omeara@syskoplan.ie)

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. (from john.omeara@syskoplan.ie)

ST22 ABAP Dump analysis

SU53 Display Authorization Values for User. (from john.omeara@syskoplan.ie)

WEDI EDI Menu. IDOC and EDI base.

WE02 Display an IDOC

WE07 IDOC Statistics

Human Resources
PA03 Change Payroll control record

PA20 Display PA Infotypes

PA30 Create/Change PA Infotypes

PP02 Quick Entry for PD object creation

Delete PA infotypes for an employee. Will not be able to delete an infotype if there is cluster data assigned
PU00
to the employee.
Sales and Distribution (SD)
OLSD Config for SD. Use Tools-Data Transfer-Conditions to setup SAP supplied BDC to load pricing data

VA01 Create Sales/Returns Order:Initial Screen

VB21 Transaction for Volume Lease Purchases (done as a sales deal)

VK15 Transaction used to enter multiple sales conditions (most will be entered here)

SAP Office
SO00 send a note through SAP, can be sent to internet, X400, etc

FI Financial Management
FGRP Report Writer screen

FM12 View blocked documents by user

FST2 Insert language specific name for G/L account. (from john.omeara@syskoplan.ie)

FST3 Display G/L account name. (from john.omeara@syskoplan.ie)

KEA0 Maintain operating concern. (from john.omeara@syskoplan.ie)

KEKE Activate CO-PA. (from john.omeara@syskoplan.ie)

KEKK Assign operating concern. (from john.omeara@syskoplan.ie)

KL04 Delete activity type. (from john.omeara@syskoplan.ie)

KS04 Delete a cost centre. (from john.omeara@syskoplan.ie)

KSH2 Change cost centre group - delete. (from john.omeara@syskoplan.ie)

OBR2 Deletion program for customers, vendors, G/L accounts. (from john.omeara@syskoplan.ie)

OKC5 Cost element/cost element group deletion. (from john.omeara@syskoplan.ie)

OKE1 Delete transaction data. (from john.omeara@syskoplan.ie)

OKE2 Delete a profit centre. (from john.omeara@syskoplan.ie)

Determine Activity Number: Activity Types (Assignment of material number/service to activity type)
OKI1
(from john.omeara@syskoplan.ie)

OMZ1 Definition of partner roles. (from john.omeara@syskoplan.ie)

OMZ2 Language dependent key reassignment for partner roles. (from john.omeara@syskoplan.ie)
Material Management (MM)
MM06 Flag material for deletion. (from john.omeara@syskoplan.ie)

materials management configuration menu, most of the stuff under this menu is not under the
OLMS-
implementation guide

MM configuration transactions
OLMB- Inventory management/Physical Inventory

OLMD- MM Consumption-Based Planning

OLME- MM Purchasing

OLML- Warehouse Management

OLMR- Invoice Verification

OLMS Material Master data

OLMW- MM Valuation/Account Assignment

Config Related
OLE OLE demo transaction

OLI0 C Plant Maintenance Master Data

OLI1 Set Up INVCO for Material Movements

OLI8 Set Up SIS for Deliveries

OLIA C Maintenance Processing

OLIP C Plant Maintenance Planning

OLIQ New set-up of QM info system

OLIX Set Up Copying/Deleting of Versions

OLIY Set Up Deletion of SIS/Inter.Storage

OLIZ Stat Set Up INVCO: Invoice Verif

OLM2 Customizing: Volume-Based Rebates

OLMB C RM-MAT Inventory Management Menu

OLMD C RM-MAT MRP Menu

OLME C MM Menu: Purchasing

OLML C MM Menu for Warehouse Management

OLMR C RM-MAT Menu: Invoice Verification

OLMS C RM-MAT Master Data Menu

OLMW C RM-MAT Valuation/Acct. Assgt. Menu

OLPA SOP Configuration

OLPE Sales order value

OLPK Customizing for capacity planning

OLPR Project System Options

OLPS Customizing Basic Data

OLPV Customizing: Std. Value Calculation

OLQB C QM QM in Procurement

OLQI Analysis

OLQM Customizing QM Quality Notifications

OLQS C QM Menu Basic Data

OLQW C QM Inspection Management

OLQZ Quality Certificates

OLS1 Customizing for Rebates

OLSD Customizing: SD

OLVA C SD Sales Menu

OLVD C SD Shipping Menu

OLVF C SD Billing Menu

OLVS C SD Menu for Master Data

SPRO Start SAP IMG (Implementation Guide). (from john.omeara@syskoplan.ie

Adding Custom Fields to POs, Outline Agreements, and

RFOs

Add custom fields to the customer include structures I_EKKODB and

 I_EKPODB

Create a project via CMOD for enhancement MM06E005.

Follow the documentation for MM06E005, and create the subscreens for
function group XM06 using transaction SE80.

Example:
SAPLXM06 0101 Subscreen header purchase order
SAPLXM06 0201 Subscreen header outline agreement
SAPLXM06 0301 Subscreen header RFQ
SAPLXM06 0111 Subscreen item purchase order
SAPLXM06 0211 Subscreen item outline agreement
SAPLXM06 0311 Subscreen item RFQ

Add fields to the appropriate screen. I reccomend calling the screen fields
EKPO_CI-name or EKKO_CI-name. This simplifies transferring data to/from
the screen.

Put code in EXIT_SAPMM06E_018 to transfer data from subscreen to structure

E_CI_EKPO.

Example:
example: e_ci_ekpo-zz_field1 = ekpo_ci-zz_field1.
e_ci_ekpo-zz_field2 = ekpo_ci-zz_field2.

Put code in EXIT_SAPMM06E_016 to transfer data from database to subscreen

using structure I_CI_EKPO.

Example:
example: ekpo_ci-zz_field1 = i_ci_ekpo-zz_field1.
ekpo_ci-zz_field2 = i_ci_ekpo-zz_field2.

Background Job/Scheduler

BACKGROUND PROCESSING IN SAP R/3

1. What the scheduler can do
 Many steps within a job: A job can consist of many steps, each running a different
program. Each step waits for the previous step to run before it starts.
 Periodic jobs: A job can be scheduled to run every minute, hour, day, week, month, or any
other specified time frame.
 Dependent jobs: A jobs can be scheduled to wait for another job to finish before it
executes.
2. What the scheduler cannot do
 Periodic dependent jobs: If you have a job that runs every night and another that
depends on it, the dependent job will run the first time, but not again after that.
 Continuing a job that has crashed: If a job crashes on step 1, the whole job stops, and
there is no way to continue processing.
 Re-running from certain job steps: If your job crashes at step 2, there is no facility to re-
run, without changing the job and removing step 1 so it does not run again.
  Waiting for a Batch Input Session: If you run a job which runs RSBDCSUB, the second
step will not wait for the batch input session to process, as it is executing in a separate
job.
3. Suggested methods for processing
 Using a self-scheduling job: A program can be set up to re-schedule itself in a job after a
specified time. This is more flexible than a periodic job.
 Jobs that create other jobs: An alternative to dependent jobs, is to run a program in the
first job which will create the next job.
 Jobs that wait for other jobs: A program can be set up that will wait for a specified job,
and runs a batch input session. Use this as a step in your job after a batch input session
has run.
4. System messaging
 Information and Success messages: Write the message text to the job log. Program and
job continues as normal
 Error and Abend messages: Write the message text to the job log. Stop the current
program from running. Cancel the entire job.
 -> any dependent programs must be scheduled in a different job
5. Suggested methods for error handling & reprocessing
 If subsequent steps in a job are not dependent on the first one finishing successfully, the
first program should be set up to crash using a success message followed by the ‘STOP’
statement.
 * Before every error message, call a routine which notifies the ‘Operations Center’ of
error type, severity, action, etc.
6. Transactions used for Background JOBS:
 SM36 - Define Background Jobs
 SM37 - Background Jobs Overview
How to define Periodic Jobs
 Execute transaction SM36
 Define Job name, Job class, Target server
 Click on 'START CONDITION' button
 Click on 'Date/Time' button
 Enter Scheduled start DATE & TIME. Check mark 'Periodic Job' field. Click on 'Period
values' button and select 'Hourly' or 'Dialy' or 'Weekly' or 'Monthly' or Other period and
SAVE. Go back to main screen.
 Click on 'STEPS' button and enter Program name and Variant under box 'ABAP
Program'. Click on 'Print Specification' button and enter Printer name under 'Output
device' and SAVE
 Click on SAVE button until you get message on bottom of the screen that describes 'Job
XYZ saved with status: Scheduled'.
 Click on 'Job overview' button or execute SM37 transaction.
 Select the appropriate 'Job name', 'User name', 'Job Status' & Schedule date under 'Job
start condition' and click on 'Execute' button or press F8.
 You will now see all your scheduled JOBS.