Maintain Plant
Plant 0001 is the SAP default.
OX14 - Define Valuation Area (Tick one only- Once your system go live, no more changes)
Most company take the SAP recommended choice - Value Material Stock at Plant level
Value Material Stock at Plant or Company Level
- If you valuate material stocks at plant level, the plant is the valuation area.
- If you valuate material stocks at company code level, the company code is the valuation area.
- The decision you make applies to the whole client.
OX10 - Create / Change / View Plants
OVXB - Create / Change / View Division
OX18 - Assign Plant to company code
e.g. 0001 - 0001 - All Plants
Px1 - Plant Px1
Px2 - Plant Px2
OX19 - Assignment of company code to the Controlling Area
OB38 - Assign company code to Credit Control Area
OMJ7 - Assign business area to Plant/Valuation area and division
e.g. Plant Px1 - Business Area Bx1
Bx2
Assign Valuation area to the Business Area
.e.g. Valuation area Vx1 - Business Area Bx1
Business Area Bx2
OMS0 - Assign Factory Calendar to the Plant and Business Area
The plant plays an important role in the following areas:
- Material Valuation - If the valuation level is the plant, the material stocks are valuated at plant level. Each plant can have its own material prices and account determination.
- Inventory Management - The material stocks are managed within a plant.
- MRP - Material requirements are planned for each plant. Each plant has its own MRP data. Analyses for materials planning can be made across plants.
- Production - Each plant having they own production/planning.
- Costing - In costing, valuation prices are defined only within a plant.
- Plant Maintenance - If a plant performs plant maintenance planning tasks, it is defined as a maintenance planning plant. A maintenance planning plant can also carry out planning tasks for other plants (maintenance plants).
If you want to use the application PP (production planning) or product costing and job-order costing, you must set valuation at plant level.
The valuation level that you choose affects
- the maintenance of material master records
- the G/L accounts in which material stocks are managed
- the G/L accounts to which transactions are posted in Materials Management
Effect on the maintenance of material master records:
Depending on the valuation level chosen,
- you maintain accounting data in the material master record for each plant or for each company code
- you define a valuation price for the material in each plant or in each company code
Effect on G/L accounts:
If material stocks are valuated at company code level, all plant stocks of a material are managed in a joint stock account for each company code.
If material stocks are valuated at plant level, you can manage the material stocks for each plant in different accounts. For each plant, you can define a separate determination.
If several plants are to use account determination, you can group these plants in "Valuation and Account Assignment" Customizing.
Material Master - Introduction
The material master is the starting point for the rest of the modules.
What Material Types are there?
The material types that you use are configured in Customizing for the Material Master under
Logistics Master Data : Material Master -> Material -> Control data -> Define material type attributes.
The following list shows you the material types contained, for example, in the standard SAP R/3 System, and what their different roles are:
DIEN (services)
Services are procured externally and cannot be stored. A material master record of this material type can always contain purchasing data.
FERT (finished products)
Finished products are produced by the company itself. Since they cannot be ordered by Purchasing, a material master record of this material type does not contain purchasing data.
FHMI (production resources/tools)
Production resources/tools are procured externally and used in the manufacture of products. A material master record of this material type can contain purchasing data, but no sales data. It is managed on a quantity basis. Examples of production resources/tools are apparatus, equipment, and measuring and testing devices.
HALB (semifinished products)
Semifinished products can be procured externally (sub-contracting) as well as manufactured in-house. They are then processed by the company. A material master record of this material type can contain both purchasing and work scheduling data.
HAWA (trading goods)
Trading goods are always procured externally and then sold. A material master record of this material type can contain purchasing and sales data.
HIBE (operating supplies)
Operating supplies are procured externally and required for the manufacture of other products. A material master record of this material type can contain purchasing data but no sales data.
NLAG (non-stock material)
Non-stock material is material that is not held in stock because it is consumed immediately. (Office supplies such as stationary. You need to create purchase order and accounting document for payment but the stock balance is always zero as it is issued out immediately to the various department.)
ROH (raw materials)
Raw materials are always procured externally and then processed. Since raw materials cannot be sold, a material master record of this material type contains no sales data.
UNBW (non-valuated materials)
Non-valuated materials are managed on a quantity basis, but not by value.
VERP (packaging materials)
Packaging materials are used to transport goods and come with the goods free of charge. A material master record of this material type is managed both on a quantity basis and by value.
WETT (competitive products)
Competitive products have their own material master records created from the Basic Data view. The competitor's number, which is stored in the material master record, assigns the material to a particular competitor.
Maintain the Material Type
OMS2 - Material Type Maintenance - Create/Change/Display
Steps:-
- transaction OMS2
- click Change
- key in the Material Type you want to change e.g. FERT then hit enter
The Views belows allows you to choose the Views for each Material Type.
(Press the Page up/Page Down keys to scroll the views)
If you tried to change from FERT to HAWA in 4.6x, you will receive an error message :-
The material type cannot be changed. This is not allowed if only external procurement is defined for the new material type, or if the new material type has a different account category reference than the old material type.
To overcome it, goto OMS2 and change the HAWA material type.
In the Internal/external purchase orders sections:
Original Changes
Ext. purchase orders 2 1
Int. purchase orders 0 1
Screens in Material Master
- MM01 - Create, MM02 - Change, MM03 - Display and MM06 - Flag for deletion.
- MM04 - Display the changes done to the material master.
- MMAM - Change the Material Type. for e.g. from FERT to HALB
Configure the Material Master Screen MM01 / MM02 / MM03
OMSR - Assign the field to the field group
OMS9 - Maintain the data screen field
Unit of Measure
In the material master, there is a Units of measure button for users to store in the different conversion rate. This sample program (ZUNT) extract the data from the unit of measure conversion table.
In the Material Master the moving average price are affected by:-
- Goods Receipt for Purchase Orders
- Transfer from Plant to Plant
- Invoice Receipt
- Settlement
- Price Change
Common configuration changes-
- define new material group (OMSF)
- define new valuation class (
- define new material account assignment group (transaction OVK5) and
Customer/Material/Account keys (transaction VKOA)
Block materials from inventory posting
After blocking, when the user do a inventory posting, they will get this error message :-
E: Material xxxxx has status Blocked for procmnt/whse
To activate the blocking :-
Goto transaction MM02 - Purchasing View
Type in 01 at the MM/PP status field and save it
Create Delivery Log - Material xxx is blocked
During the Create Delivery (VL01), SAP prompt you a log that Material xxx is blocked.
During the Sales Order Create/Change for that material, there might be some update termination that causes the locked of the material (Windows hanged or power failure).
You can check using transaction SM12 - type an "*" at the User name field.
Check whether the material is in the locked list.
If it is in the locked list, asked the user to log out before you delete it from the locked list.
Maintain Storage Location
MMSC - Collective entry of Storage Location for a material.
Insert new or delete un-used Storage Location.
Maintain whether the storage location was included or excluded from MRP run.
Block Storage Location from further posting
1. You can block the storage location of a material without affecting the rest of the location using the same material.
Create a Physical Inventory document for the storage location with transaction MI01
Select the Posting Block checkbox.
This would prevent transactions from occuring until you either post or delete the physical inventory document.
(There are no impact, unless you do a post difference for the physical inventory document.)
2. Another method is to rename the storage location name.
Go to transaction OX09
Edit -> Copy as (copy the original storage location to a new name, replacing the first character e.g. ZXXX)
Edit -> Delete (delete the original storage location)
Do the reverse if you want back the original storage location.
Accounting document number range for MM
Transaction OMW9
Document Type - Double click on desire transaction code to check the document type for number range.
(e.g. MR21 Document type - PR)
Financial accounting document type - Assign the document type to a number range and account type.
(e.g. PR - Account type allowed for posting will be MS)
- Double click on the document type PR.
- Assign an unique starting number range that was not used. e.g. 88
- Choose the Account type for Material and G/L account (MS)
- The rest of the fields are optional (you can leave it as blank)
SAP definitions for account type -
- A - Assets
- D - Customers
- K - Vendors
- M - Material
- S - G/L accounts
Number ranges for financial accounting document type - Assign the number range to the running number range.
No. Year (till) From number To number Current number Ext (no tick internal or tick external)
88 9999 8800000000 8899999999 Track by SAP Blank
Accounting document will be generated if there are stocks during price change, if you don't have any stocks, no accounting document will be generated as there are no inventory to revaluate for price differences.
Valuation Class for Material Group
In 4.6x and 4.5b, you can assign valuation class to Material Group.
It is useful in the sense that user do not have to manually do an Account Assignments.
For stock items, valuation class cannot be changed whenever the stock on hand is not zero.
Valuation class are tied to a G/L account.
A change of valuation class means a change of G/L account.
In FI concept, you have to debit and credit to balance the G/L account. That is why your stock must be zero before the system allows you to changed the valuation class. If it is not zero, you have to either transfer it to another material or do a dummy issues. After changing the valuation class, do a reversal entries for the stocks which you have transfer out or you have done a dummy issues.
IMG - Material Management -> Purchasing -> Material Master -> Entry aids for items without a Material Master
G/L Accounts in MM Account Determination
The program RM07C030 check all the G/L account define in your Material Master valuation class.
Search is via Company code and Valuation area.
Compare fields status for movement types against General Ledger
Use SA38 then run RM07CUFA
Contributed by :- sapr3.tripod.com
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 · BALD Idoc development 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 · 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 determination856 - 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 & DistributionSales 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 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 GeneralThe following section provides detail on other useful SAP areas. Create delivery via transfer ordersOnce 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 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 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 · 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. |
Quicklinks
- Purchasing Tables
- SAPReader is a small program which converts purchase orders created by the SAP R/3 system into a readable document. Its purpose is to enable companies to receive purchase orders from customers who are using the SAP R/3 system, and to translate these into a format using the supplier's own product codes. The text file produced by SAPReader may then be manually entered into the supplier's system or may be electronically uploaded.
Tips for Fast Message Determination Setup
Here you are shown how to set up the message determination (output control) facility quickly. In this case, you need not read the Implementation Guide (IMG) for the other steps to set up this facility, or need only read certain parts of it.
Setting up the Message Determination Process: Options
Message determination deactivated
You can output purchasing documents without the message determination facility. In this case, you must not assign any message determination schemas to the the individual purchasing documents (RFQ, purchase order, etc.). The system then generates a message of the type NEU (new) for each document to be outputted. To determine the printer, the system first checks the settings for the purchasing group. If no printer has been maintained there, it checks the user parameter. If no printer has been specified there either, the system checks the fixed value for the user. If no printer has been specified, the system does not generate a message record.
Message determination activated
Adopt standard setting
In the standard system, the message determination facility is active. A message determination schema is supplied for and assigned to each purchasing document. If you wish to work with this standard setting, you need not make any changes in Customizing.
It is necessary that you maintain condition records for the desired message types:
1. Choose Master data -> Messages ->
1. Enter the message type and choose the key combination. The latter determines the condition table in which the condition record is stored.
2. Make the necessary entries.
3. On the next screen, create the individual condition records.
4. Via the menu options Goto -> Means of communication, enter the desired means of communication (e.g. EDI, or an output device such as a printer) for each message record.
5. Save your data
Include new message type
If you wish to do this, you must
1. Create the message type and define its fine-tuned control (e.g. whether the message type is to be used only for new printouts or only for change notices),
2. Assign the message type to a schema
3. Define the message determination
4. Maintain condition records for the message type, as described above.
How is the printer determined for message output purposes?
The system checks whether a printer has been specified in the condition record. If so, it is used. If not, it checks the message type to see whether a print parameter has been set. If no parameter has been set, no message is generated. If a parameter has been set, a printer is sought in accordance with this parameter. If a printer is found, it is used to output the message. If not, no message is generated.
Note:
You can change the printer when outputting messages (e.g. via the menu options Purchasing document> -> Messages -> Print/transmit). Select the desired message and choose Goto -> Message details -> Edit -> Means of communication.
Goods Receipts/Invoice Receipts for Purchase Order
Transaction OMW1 allows you to set whether the Price Control is a mandatory "S" or "V".
V indicate that you want the system to value the stocks with the latest price.
S indicate that you want the system to value the stocks with a fixed price method.
Price Control V - Moving Average Price
Assume Material Master current price is 10
Goods Receipts for Purchase Order - Movement Type 101
- Material Document Posting created - inventory increases
- Accounting Document Posting created
- Debit 12345 Inventory 12
- Credit 67890 GR/IR 12
- New Moving Average Price = ( GR value + Total value ) / ( GR quantity + Total stock )
Invoice Recipts for Purchase Order - MR01
- Accounting Document Posting created
- Debit 67890 GR/IR 12
- Debit 12345 Inventory 3
- Credit 45678 Vendor 15
- New Moving Average Price = ( Inventory difference of 2 + Total value ) / ( Total Stock)
Price Control S - Standard Price
Material and Accounting Document is the same.
The one with the lower value will be posted with a price variance entry.
Goods Receipts for Purchase Order - Movement Type 101
- Material Document Posting created - inventory increases
- Accounting Document Posting created
- Debit 12345 Inventory 10
- Debit 23456 Price Variance 2
- Credit 67890 GR/IR 12
- No change in Standard Price
Invoice Recipts for Purchase Order - MR01
- Accounting Document Posting created
- Debit 67890 GR/IR 12
- Debit 23456 Price Variance 3
- Credit 45678 Vendor 15
- No change in Standard Price
General Ledger Account Configuration
Transaction OMWB - Automatic posting for inventory
Inventory posting BSX
Goods receipt/inv.receipt clearing acct WRX
Cost (price) differences PRD
Transaction XK03 - Account Payable Vendor Master
Tick Accounting info. and hit the Enter key
Field name Reconcil.acct 45678
Vendor Returns Without
You can used Return Purchase Order, transaction code ME21N
At the item details, look for the Return columns and tick it.
MIGO_GR - Goods Receipt for Return Purchase Order
Movement type will be 161 to deduct the stock and 162 for reversal.
During Goods Receipt for Return Purchase Order, you do not have to change the movement type from 101 to 161 as the system will automatically assign the movement type to 161 upon saving the postings. However, before saving, check if there is a tick in the Return Column to ensure that it is a return Purchase Order.
Create a new Purchase Order Number range to differentiate
OMH6 - Define Number Ranges
Create a new Purchase Order Type to differentiate e.g ZB
OMEC - Define Document Type
Changing the PO Layout sets
OMFE - Messages: Output Programs
/: IF &EKKO-BSART& = 'ZB'.
/ RETURNED PURCHASE ORDER
: ELSE.
/ PURCHASE ORDER
/: ENDIF.
Purchasing List for Open Purchase Order, Goods Receipt, Invoices
Open Purchase Order = Open Goods Receipts ( Selection parameters WE101)
This two parameters determined what information is shown:
- selection parameter
- scope-of-list parameter
The configuation transaction code is OMEM
You can define additonal selection parameter for your users as well as untick those fields which you does not want it to be printed.
Your can have the Purchasing Documents by :-
- ME2L - Vendor
- ME2M - Material
- ML93 - Service
- ME2K - Account Assignment
- ME2C - Material Group
- ME2B - Requirement Tracking Number
- ME2N - Purchase Order Number
ME2W - Supplying Plant
Force buyers to create Purchase Order with ref. to a Pur. Req., Quotation or Pur. Ord.
Transaction OMET
- Create a new entry, give it a name and tick :-
- Ref. to PReq
- Ref. to P.O.
- Ref. to quotation
- Next, you've got to associate via SU01
- Click Parameters, insert a new parameter id EFB to the authorization code.
- Type in Parameters value you want e.g. XX
- You have to assign the control for ALL the SAP buyers via thier SAP users id.
Logoff and login again. Then try to create a Purchase Order without a reference.
Define default values for buyers
Transaction OMFI
- Double click on the default values you want to change.
- Save it.
- Next, you've got to associate via SU01
- Click Parameters, insert a new parameter id EVO to the authorization code.
- Type in Parameters value you want e.g. 01
- You have to assign the control for ALL the SAP buyers via thier SAP users id.
- Logoff and login again. Then try to create a Purchase Order and check the default values.
In the Fast Processing button :-
you can choose whether to adopt automatically all the line items fields in the Purchaes Requisitions
Puchase Order Condition
Suppose you want to calculate the GST and DISCOUNT for a Net Value of 1000.
Net value 1000
GST 10% of 1000 100
DISCOUNT 10% of 1000 100
Final Net value 900
This is what you do :-
- M/08 - Define calculation schema
- First check the conditions column Steps e.g. PB00 and PBXX belongs to step 1.
- Next check the last Steps after Actual Price
- Now, look at the column Fro To
- If you want the DISCOUNT to be calculated based on 1000, put the Steps number in the column Fro
The Fro To controls the calculation.
Information Structure
In the SAP standard info structure S012 is updated by the Purchase Order creation date, not the Goods Receipt date. e.g. a Purchase Order is created in January and good receipt is in February and March, S012 will shows the values in period January.
- Transaction MC26
- Info structure S012 Update group (stats) SAP
- Double click on Goods received qty
In the section Date field for period determination
Purchase Order Layout Sets, Message Types
Create a new message types for a different layout of Purchase Order
- M/34 - Maintain message types
- Click the Partner definition button
- Insert the new message type to the Partner
- OMQN - Fined-tuned Message Control
- Add a new Printer Operation 1 - New 2 - Change
- OMFE - Layout sets for Purchase Order
- Attach the new message type to the new layout sets
- M/36 - Maintain message detemination schema : Purchase Order
- OMQS - Assign schema to Purchase Order
- OMGF - Assign Output devices to Purchasing Groups
MN05 - Assign default Message Type to Purchasing Groups
User Defaults for Purchase Order
There are some fields which you can set as defaults for the buyer in transaction ME21.
Transaction SU01
Input the user name and click Parameters
PID Parameter value
LIF - Vendor number
BES - Purchase Order Number
BSA - Order type
EKG - Purchasing group
EKO - Purchasing organization
WRK - Plant
LAG - Storage location
MKL - Material group
WAK - Promotion
4.6x
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization objectM_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 0
1
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Prompt the last Purchase Order Price for the Material
If you want the system to take the price from the last Purchase Order, then do not maintain the conditions in the info record because it has precedence over the last
In the case when you have already maintained the conditions in the info record (or netprice), try to delete them or make them invalid by changing the validity date.
Even though no price was maintained, the info record will still keep track of the Order price history.
To check the Order price history, go into the material info record and click Environment -> Order price history
Adopt Purchase Order Header Text
To default the Header Text into the Purchase Order
Step 1 :- Maintain text in Vendor Master
- MK02 - Change Vendor
- Choose Extras -> Texts - Input the text in Purchasing memo
Step 2 :- Link Text types to Header text in Purchase Order
- OMFV - Define rules for copying (adoption of) text
- Choose Header Text
- Choose Goto -> Linkage: text types -> To vendor
- Filled in the field No. (e.g. 01 - Header Text), next tick whether you want the text to be adopted or fordisplayed only
- Choose Update to save
Create a new Purchase Order Document Type
4.6x
If you have more than one company code, you might want to define a new document type and number range to differentiate between the two company.
Define a new number range not in used
OMH6 -
Copy the NB - Standard PO to e.g. ZB
OMEC - Define Document types
Maintain :
Text for Document Header/Item
Text for Document Supplement
OMF6 - Messages Header Texts
Send Purchase Order via Output Determination
Read note 191470 - Purchase order as an e-mail
From release 4.5, you can send your purchase order via output determination. This note have indicate all the requirement and settings necessary to send purchase order via the output determination once your SAP have been connected to an External Mail System.
Send Purchase Order with Microsoft Outlook
This is how it work:-
- First you send the text converted Purchase Order to your SAPoffice
- Then from Microsoft Outlook, you can send it out externally to your Vendor
Install the SAP setup program on the SAP Presentation CD-ROM under \GUI\WINDOWS\WIN32
Execute the SAPsetup program and choose the Desktop Interfaces.
Then choose the SAP MAPI Service Provider (select Change Options to display the selection)
Once the SAP MAPI is installed. You can create your logon profile for SAPoffice.
Go into your Control Panel of your windows.
Select the Mail option from the Control Panel to call the MAPI profile manager.
Choose Add to call up the new logon profile setup wizard
Select Add from the Services and select the SAP MAPI Service Provider
Type in the required R/3 information (client, sap user name, password)
The supplied PST file is sapwrk.pst
Now, logon to your Microsoft Outlook and see whether you can access all your SAPoffice folders.
If you send the file using SP01 -> System -> List -> Send, the file will have the extension ALI. Use the Windows Explorer to default open with the Windows Notepad.
Sending mail directly from SAP via Microsoft Exchange
If you want to send your mail directly via Microsoft Exchange, you have to install the SAP Exchange Connector Software on your Microsoft Exchange Server.
The setup program SETUP.EXE is located on the R/3 Presentation CD in the directory :\GUI\WINDOWS\WIN32\SXC.
Then you have to setup :-
- SM59 - The RFC destination
- SCOT - SAPconnect
Refer to the Unix SAP Internet Mail Gateway installation steps.
Contributed by :- sapr3.tripod.com
Other tips
Transaction CL24 is particularly important if you do modification on release strategies. Especially if you delete some in OMGQ: they are not completely deleted until you delete them also in CL24. This can cause some seriously strange behavior on the system (and sometimes on the consultants and users). Tip by kuentz@alum.mit.edu
Materials Management Tables
Purchasing Tables
|
Q: We could create two Purchase Orders for full amount & quantity out of one Purchase Requisition. two goods receipts and invoice receipts on their respective POs. How can We avoid this kind of double transactions? Q: Is there a transaction or Report available to see the scrapped quantity of a particular material where goods issue is done using movement type 551? Q: We want to run multi-plant planning for 3 plants A, B and C , where the requirements of plant A and B are transferred to Plant C. Plant C is expected to consolidate the requirement and convert these requirements into requisitions and then into POs. When we do a planning at Plant C, we are unable to see the requirements for plant A and plant B. We are using the special procurement key 40 for all the materials being planned. Can we do multi plant planning at plant level as well as Material level? Q: We are doing goods receipt with Q: In MM pricing schema, there are a list of selection from A to M and 1 to 8. How can we make use of the condition sub-total field ? Q: There are some complaints that though the data is correct in User Info (USR03) , Purchase order is being printedwith wrong information . For Example: telephone Number. Where can I find correct Purchase group Information? Q: What are the tables generally used for MM Queries ?
Q: What are the typical transaction codes for IM & PO? Q: During a good issue for a inventory product (HIBE), we assign by the automatic account assignment a GL account in relation to the valuation class of the product. However we would like to change this GL account automatically depending of the cost center requested the product for consumption. How can we do it? Q: We have specified in MRP for requisitions to be created. The document type of the requisitions created is alwaysthe type NB. How can we change the document type created? Q: We have created a workflow for the purchase requisition approval process . When the event (BUS2009, RELEASESTEPCREATED) is triggered to kick off WF , the following error message is appearing A: 1. Must update the number range for events object SWE_EVTID with transaction SNRO. Q: How can we make a Taxcode as default on purchase order item detail screen ? Q: We have defined EA (each) as 0 decimal place in configuration. But transaction ME2L shows this field with three decimal places. How can I change to actual number of decimal places? Q: We have created a new movement type and assigned to a schedule line. When goods issue is posted, message -movement type zzz is not allowed for customer goods movement? Why? Q: Is it possible to generate packing list for goods issued in MM? Q: How can we track requisitions that have the deletion indicator set? Can we track the date in which the deletion indicator was set? Q: Is it possible to generate Purchase requisition (PR) with reference to Scheduling Agreement? Q: Where can I locate the latest Purchase Order price and the latest purchase order number for a material? Q: Automatic generation of Q: I would like Convert MRP generated 100 PRs into 100 POs automatically. Not one by one manually. Is it possible? Q: How can I print an Un-invoiced Receipts Report which shows Purchase Orders for which goods are received , but not yet invoiced ? We require this report with sub-totals and tied to Un-invoiced Receipts G/L Account Q: How can I calculate the net price of an inforecord for a given date? Q: Can we release a Purchase Order with price equals zero? ( like in SD- free of charge sales Order) Q: The net price is calculated by summing up the gross price condition type and subtracting /adding all discount/surcharge type condition types respectively. Any condition type which is not marked as statistical will be considered for net price calculation. We have a surcharge that is not marked as statistical and should be included in the net price but excluded in the taxation base value. Can I have a procedure where the taxes are calculated on the net price calculated till the condition type NAVS and then have this additional surcharge type? Level CondTy Description From To 100 PB00 Gross Price 200 RA01 Discount % on Gross 300 ZMUP Mark Up (value) 400 Base Value for Tax 100 300 500 ZDIS Disc. Excluded Tax 600 Net Amount 700 MST Tax 400 400 800 Net Amount With this Schema: Q: Can we change the name of the Vendor in a Q: We want to return unused material procured from a vendor and update stock or expense Account. How to do this effectively? Q: How do I define a new currency ? How can i set number of decimal places more than two? Q: Our supplier delivers his product for an Auction. We sell it in auction and pay the supplier. What is the best way to handle this? Q: How can I open a previous MM period? Q: We can make a particular indicator mandatory. Can I have a defaulted value for the indicator while creating Material master that can be changed later in MM02? Q: How can I generate a report of cancelled A2: Go to the initial screen of purchasing. Then go to PURCHASING -> LIST DISPLAYS -> BY PO NUMBER -> EDIT -> DYNAMIC SELECTION. This allows you to select certain fields from the EKKO table and EKPO table. Deletion indicator can also be seen here. Use 'dynamic selections' to determine your selection criteria and run the report. A3: You can also do this via the IMG Q: How can we detect a change in a Purchase Order? Q: We want to pop-up a screen to show the total value of PO before saving the PO so that user can decide whether to save the Q: Q: While creating a purchase order we can see that there is the "Info rec. update" in the box item detail screen. How can we change the default setting for this box? Q: I want to have multiple addresses of a vendor - for ex: mailing, shipping, payment remittance, several billing addresses, etc. Suppose we have 25 addresses for one company, what is the best way without creating 25 separate companies and their addresses? Q: The source list is created for a material ie. source list required is marked. When a Q: We want the Vendor code as 'abc1234' where first 3 characters are alpha and the last four digits are digits serial numbers. What is the solution? Q: We want to set up a Preferred Vendor list to enable users to determine the Vendor to be called for the material required while raising the Requisition. What is the best way? Q: What is the SAP standard way for deleting all the vendors centrally from the system? Inventory Management Q: How can we create one inventory doc with all your materials to count instead of generating one doc for each material? A2: Set maximum number of items to say 50 using Transaction MICN. The same can be preset using transaction OMCN. Q: How is GR/IR account related to Inventory? Q: We tried RMCB0300 to find out logical value for stock item by date. But after re-valuation, stock value is supported by month instead of date. How can we find the logical value for stock item by date? Q: How can we transfer stock from one vendor to another vendor? Q: How can I cancel a posted invoice? The error message 'BSEG-GSBER is not an input field' is appearing. Even Q: A storage location from different plant can be assigned to the warehouse of any Plant. But different storage location within the same plant cannot be assigned to the same warehouse number. Why ? Q: We are using only fixed bins and do not want to use automatic bin creation nor any strategy for removing/loading goods to the storage? In what way Ware Housing helps me?
Q: We have a lot size procedure here which is creating more order proposals. How do you set the limit value formaximum number of MRP order proposals per date in IMG? Q: What is the difference between "planned consumption" and "Unplanned consumption"? Can safety stock calculation be done on either of these? Q: We are trying to use reservations to block our existing un-restricted plant stock against a Sales Order Line Item. But the reservation is included in the Planning file when MRP is run.. We want to disable the reservation in MRP. How can I do this? Q: We do not want to convert Planned orders to requisitions in our MRP run and keep some materials in the step of planned orders. Can we do this? Q: How can I extend all material to a new plant? Q: How can we delete materials permanently from Material master? Q: SAP only provides moving average value for current, previous period, and previous year. SAP does not provide transactions/reports that will provide moving average value for a given date. Q: We have defined all the variables for the materials. However, when I attempt to use Material Matchcode object MAT1, I get the response "No possible entries found". Why? Q: The matchcode object selection is defaulted to matctcode ID "B". Iwould like to change to M "Material by Description" What is the solution? Q: We have one material master : X and the unit of measure is 'pcs' and two serial number : A,B Q: We want to change the calculation of Moving Average Price. We know that the same is in MBEW-VERPR and two transactions to consider - MRHR, MB01. Is there a transaction to change MAV or all the places it is needed? Q: What is the use of configurable material.? Q: Will Source List automatically appear in Material Master as default if maintained at plant level using OME5? A1: If you have maintained source list requirement in OME5 and have not maintained the source list for the material , Q: We have One company with a plant and another company with a sales organization. Which is better option between these - A: Cross company Stock Transport Orders can be done. Q: We can make field mandatory. We want to make a default value to a Particular field in the Material Master. Say, We want that the period indicator in the MRP2 view as "P". What is the best way? Q: The following is set up for workflow:
TS 00007986 Requisition release - TO JOBS 3.Activate event linkage WS 00000038 Workflow for purchase requisition release WE BUS2009 RELEASESTEPCREATE Purchase requisition Release step create is activated 4.Activated release codes for workflow [1= Role resolution with group, code, and plant (T16FW)] 5.Assigned release codes to agent (JOBS created in 1) A: Use transaction SWE2. Make sure "object BUS2009 event REJECTED" is enabled. |
Plant 0001 is the SAP default.
OX14 - Define Valuation Area (Tick one only- Once your system go live, no more changes)
Most company take the SAP recommended choice - Value Material Stock at Plant level
Value Material Stock at Plant or Company Level
- If you valuate material stocks at plant level, the plant is the valuation area.
- If you valuate material stocks at company code level, the company code is the valuation area.
- The decision you make applies to the whole client.
OX10 - Create / Change / View Plants
OVXB - Create / Change / View Division
OX18 - Assign Plant to company code
e.g. 0001 - 0001 - All Plants
Px1 - Plant Px1
Px2 - Plant Px2
OX19 - Assignment of company code to the Controlling Area
OB38 - Assign company code to Credit Control Area
OMJ7 - Assign business area to Plant/Valuation area and division
e.g. Plant Px1 - Business Area Bx1
Bx2
Assign Valuation area to the Business Area
.e.g. Valuation area Vx1 - Business Area Bx1
Business Area Bx2
OMS0 - Assign Factory Calendar to the Plant and Business Area
The plant plays an important role in the following areas:
- Material Valuation - If the valuation level is the plant, the material stocks are valuated at plant level. Each plant can have its own material prices and account determination.
- Inventory Management - The material stocks are managed within a plant.
- MRP - Material requirements are planned for each plant. Each plant has its own MRP data. Analyses for materials planning can be made across plants.
- Production - Each plant having they own production/planning.
- Costing - In costing, valuation prices are defined only within a plant.
- Plant Maintenance - If a plant performs plant maintenance planning tasks, it is defined as a maintenance planning plant. A maintenance planning plant can also carry out planning tasks for other plants (maintenance plants).
If you want to use the application PP (production planning) or product costing and job-order costing, you must set valuation at plant level.
The valuation level that you choose affects
- the maintenance of material master records
- the G/L accounts in which material stocks are managed
- the G/L accounts to which transactions are posted in Materials Management
Effect on the maintenance of material master records:
Depending on the valuation level chosen,
- you maintain accounting data in the material master record for each plant or for each company code
- you define a valuation price for the material in each plant or in each company code
Effect on G/L accounts:
If material stocks are valuated at company code level, all plant stocks of a material are managed in a joint stock account for each company code.
If material stocks are valuated at plant level, you can manage the material stocks for each plant in different accounts. For each plant, you can define a separate determination.
If several plants are to use account determination, you can group these plants in "Valuation and Account Assignment" Customizing.
Material Master - Introduction
The material master is the starting point for the rest of the modules.
What Material Types are there?
The material types that you use are configured in Customizing for the Material Master under
Logistics Master Data : Material Master -> Material -> Control data -> Define material type attributes.
The following list shows you the material types contained, for example, in the standard SAP R/3 System, and what their different roles are:
DIEN (services)
Services are procured externally and cannot be stored. A material master record of this material type can always contain purchasing data.
FERT (finished products)
Finished products are produced by the company itself. Since they cannot be ordered by Purchasing, a material master record of this material type does not contain purchasing data.
FHMI (production resources/tools)
Production resources/tools are procured externally and used in the manufacture of products. A material master record of this material type can contain purchasing data, but no sales data. It is managed on a quantity basis. Examples of production resources/tools are apparatus, equipment, and measuring and testing devices.
HALB (semifinished products)
Semifinished products can be procured externally (sub-contracting) as well as manufactured in-house. They are then processed by the company. A material master record of this material type can contain both purchasing and work scheduling data.
HAWA (trading goods)
Trading goods are always procured externally and then sold. A material master record of this material type can contain purchasing and sales data.
HIBE (operating supplies)
Operating supplies are procured externally and required for the manufacture of other products. A material master record of this material type can contain purchasing data but no sales data.
NLAG (non-stock material)
Non-stock material is material that is not held in stock because it is consumed immediately. (Office supplies such as stationary. You need to create purchase order and accounting document for payment but the stock balance is always zero as it is issued out immediately to the various department.)
ROH (raw materials)
Raw materials are always procured externally and then processed. Since raw materials cannot be sold, a material master record of this material type contains no sales data.
UNBW (non-valuated materials)
Non-valuated materials are managed on a quantity basis, but not by value.
VERP (packaging materials)
Packaging materials are used to transport goods and come with the goods free of charge. A material master record of this material type is managed both on a quantity basis and by value.
WETT (competitive products)
Competitive products have their own material master records created from the Basic Data view. The competitor's number, which is stored in the material master record, assigns the material to a particular competitor.
Maintain the Material Type
OMS2 - Material Type Maintenance - Create/Change/Display
Steps:-
- transaction OMS2
- click Change
- key in the Material Type you want to change e.g. FERT then hit enter
The Views belows allows you to choose the Views for each Material Type.
(Press the Page up/Page Down keys to scroll the views)
If you tried to change from FERT to HAWA in 4.6x, you will receive an error message :-
The material type cannot be changed. This is not allowed if only external procurement is defined for the new material type, or if the new material type has a different account category reference than the old material type.
To overcome it, goto OMS2 and change the HAWA material type.
In the Internal/external purchase orders sections:
Original Changes
Ext. purchase orders 2 1
Int. purchase orders 0 1
Screens in Material Master
- MM01 - Create, MM02 - Change, MM03 - Display and MM06 - Flag for deletion.
- MM04 - Display the changes done to the material master.
- MMAM - Change the Material Type. for e.g. from FERT to HALB
Configure the Material Master Screen MM01 / MM02 / MM03
OMSR - Assign the field to the field group
OMS9 - Maintain the data screen field
Unit of Measure
In the material master, there is a Units of measure button for users to store in the different conversion rate. This sample program (ZUNT) extract the data from the unit of measure conversion table.
In the Material Master the moving average price are affected by:-
- Goods Receipt for Purchase Orders
- Transfer from Plant to Plant
- Invoice Receipt
- Settlement
- Price Change
Common configuration changes-
- define new material group (OMSF)
- define new valuation class (
- define new material account assignment group (transaction OVK5) and
Customer/Material/Account keys (transaction VKOA)
Block materials from inventory posting
After blocking, when the user do a inventory posting, they will get this error message :-
E: Material xxxxx has status Blocked for procmnt/whse
To activate the blocking :-
Goto transaction MM02 - Purchasing View
Type in 01 at the MM/PP status field and save it
Create Delivery Log - Material xxx is blocked
During the Create Delivery (VL01), SAP prompt you a log that Material xxx is blocked.
During the Sales Order Create/Change for that material, there might be some update termination that causes the locked of the material (Windows hanged or power failure).
You can check using transaction SM12 - type an "*" at the User name field.
Check whether the material is in the locked list.
If it is in the locked list, asked the user to log out before you delete it from the locked list.
Maintain Storage Location
MMSC - Collective entry of Storage Location for a material.
Insert new or delete un-used Storage Location.
Maintain whether the storage location was included or excluded from MRP run.
Block Storage Location from further posting
1. You can block the storage location of a material without affecting the rest of the location using the same material.
Create a Physical Inventory document for the storage location with transaction MI01
Select the Posting Block checkbox.
This would prevent transactions from occuring until you either post or delete the physical inventory document.
(There are no impact, unless you do a post difference for the physical inventory document.)
2. Another method is to rename the storage location name.
Go to transaction OX09
Edit -> Copy as (copy the original storage location to a new name, replacing the first character e.g. ZXXX)
Edit -> Delete (delete the original storage location)
Do the reverse if you want back the original storage location.
Accounting document number range for MM
Transaction OMW9
Document Type - Double click on desire transaction code to check the document type for number range.
(e.g. MR21 Document type - PR)
Financial accounting document type - Assign the document type to a number range and account type.
(e.g. PR - Account type allowed for posting will be MS)
- Double click on the document type PR.
- Assign an unique starting number range that was not used. e.g. 88
- Choose the Account type for Material and G/L account (MS)
- The rest of the fields are optional (you can leave it as blank)
SAP definitions for account type -
- A - Assets
- D - Customers
- K - Vendors
- M - Material
- S - G/L accounts
Number ranges for financial accounting document type - Assign the number range to the running number range.
No. Year (till) From number To number Current number Ext (no tick internal or tick external)
88 9999 8800000000 8899999999 Track by SAP Blank
Accounting document will be generated if there are stocks during price change, if you don't have any stocks, no accounting document will be generated as there are no inventory to revaluate for price differences.
Valuation Class for Material Group
In 4.6x and 4.5b, you can assign valuation class to Material Group.
It is useful in the sense that user do not have to manually do an Account Assignments.
For stock items, valuation class cannot be changed whenever the stock on hand is not zero.
Valuation class are tied to a G/L account.
A change of valuation class means a change of G/L account.
In FI concept, you have to debit and credit to balance the G/L account. That is why your stock must be zero before the system allows you to changed the valuation class. If it is not zero, you have to either transfer it to another material or do a dummy issues. After changing the valuation class, do a reversal entries for the stocks which you have transfer out or you have done a dummy issues.
IMG - Material Management -> Purchasing -> Material Master -> Entry aids for items without a Material Master
G/L Accounts in MM Account Determination
The program RM07C030 check all the G/L account define in your Material Master valuation class.
Search is via Company code and Valuation area.
Compare fields status for movement types against General Ledger
Use SA38 then run RM07CUFA
Contributed by :- sapr3.tripod.com
Asriel Saporta
Information Technology, SAP Consultant & Project Manager, Home: (559)432-3677, Fax: (603)251-3097,Email: saporta@lycos.com or asaportas@yahoo.com
SAP IMPLEMENTATION SINCE 1995
AREA OF EXPERTISE: | Twelve years experience in IS (Information Systems), specializing in SAP R/3 for eight years in SD (Sales and Distribution) STC, Sales Order Processing, Billing, and Customizing, MM (Materials Management) RTP, WM (Warehouse Management) with Radio Frequency guns (RF), Wireless Access Networks (WLANs - WiFi) and Logistics Execution/Transportation/Shipping, EH&S Module for Product Safety, Dangerous Goods and Occupational Health, QM (Quality Management), Production Planning (PP), APO, SAP and HAHT E-Commerce Solutions, SAP's Customer Relationship Management (CRM) and B2B, Accelerated SAP Roadmap (ASAP). Expertise includes Wireless Networks (WLANs – WiFi), SAP R/3 Enterprise Wide International implementations involving design, implementation, mapping of To-Be processes, documentation, configuration and instruction of SAP R/3 2.2, 3.0, 3.1, 4.0, 4.5, 4.6 and upgrading SAP R/3 Versions. Heavy experience in resolving integration issues among SAP R/3 MM-WM-SD-QM with Logistics Execution’s Transportation Planning, Execution, and Freight Cost management and payment. Also Hazardous materials, Vendor Managed Inventory (VMI), Consignment, Materials Requirements Planning (MRP) and Forecasting, Business Planning and Web development experience, web site design, creation and deployment using design software and HTML language. Software knowledge MS FrontPage, HAHT IDE, FusionObject. Sites createdwww.leaseandsell.netfirms.com,www.evolutionary.netfirms.com,www.terapiajesspa.netfirms.com. Experience using several implementation tools and aides like CATT, ASAP, Visio Business Process Modeler, ARIS Toolset Business Process Modeler, Internal SAP Business Process Modeler which is linked to ARIS, Internal SAP Documentation Management tools, Microsoft Project, Lotus Notes, Powerpoint, NetMeeting for Teleconferencing and presenting SAP Demos and Presentations remotely. Project Management experience includes Project Planning and Execution, Customer Relationship management and communication, Human resources management for Training schedule. Also created training curriculum, created training schedule and planned resources (human and technical resources) required to execute the training. Executed Training in every single project in which I have been. |
INDUSTRY EXPERIENCE: | Chemical, Manufacturing, AFS, Food & Confectionary, Pharmaceutical, Automotive, Printing, Travel and Tourism, Telecommunications, Cosmetics and Personal Care, Industries. |
RELEVANT CAREER ACHIEVEMENTS
DATE: | October 2002 – Present |
CLIENT: | DAK |
POSITION: | RF SAPConsole implementation in Materials Management/ Warehouse Management/Sales & Distribution, LES/Quality Management/Production Planning with Dangerous Materials Handling. |
RESPONSIBILITIES: DAK | Implementation of 4.6C RF SAPConsole Barcoding in Materials Management, Warehouse Management with Quality Management and Production Planning for this SAP project. Used the ASAP Methodology for the Blueprint creation, and Microsoft Project for planning the Tasks and assigning responsibilities. VISIO was used for laying out the Business processes in a graphical representation. Conducted interviews with users and completed the Blueprint. Designed custom SAPConsole applications to the client’s specifications, provided program specs to ABAP programmers and worked with ABAP programmers to develop, test and provide a fully functioning standard SAP and custom RF SAPConsole application. Analyzed, evaluated and proposed all hardware/software needed for the SAPConsole implementation. This included the Servers, the Telnet Software Server, the VT 220 Emulation software, the Wireless Access Points (WLANs) with the WiFi 802b/a communication protocol, the RF Handheld Guns. Implemented WEP Security for a safe Wireless Network. Implemented and configured the Wireless Access Points (WLANs) WiFi (802b/a protocol), the RF Handheld Guns, the Telnet Server, the VT220 Emulation software. Customized the Mobile Data Entry in SAP and all necessary parts within MM, SD, WM, PP, and QM to handle the SAPConsole Processes. The following SAPConsole Processes were implemented and configured: Outbound Deliveries (SD-IM-WM), Inbound Putaway from Production (PP-IM-WM-QM), Inbound Putaway from Purchase Order/Vendor (MM-IM-WM-QM), Inbound Putaway from Cancelled Deliveries (SD-IM-WM-QM), Inbound Putaways from Return Deliveries from Customers (SD-IM-WM-QM), Inventory Movements (IM-WM-QM), Stock Transfers between plants/storage locations/stock statuses of Unrestricted and Quality Status (IM-WM-QM), Physical Inventory (MM-IM-WM-QM) Also all related printouts were configured, (Labels, Quality Certificates, Quality Notifications, Purchase Orders, RFQs, Contract Release Orders, Transfer Orders, Goods Issue/Goods Receipt Documents). Developed Training Documents on all above processes. Planned and Executed training classes of 80 users on all above processes. ASAP, Visio, MS Project, Lotus Notes were used for this 4.6 implementation. Led and managed a team of approximately 30 people dispersed among two plants in |
DATE: | January 2002 – September 2002 |
CLIENT: | DuPont (Chemical Industry) |
POSITION: | Materials Management/ Warehouse Management/Sales & Distribution, LES/Quality Management/Production Planning |
RESPONSIBILITIES: Client: Du Pont Project owned: Accenture | Implementation of 4.6C Materials Management, Warehouse Management with Quality Management and Production Planning for this SAP project. Used the ASAP Methodology for the Blueprint creation, and Microsoft Project for planning the Tasks and assigning responsibilities. VISIO was used for laying out the Business processes in a graphical representation. Conducted interviews with users and completed the Blueprint. Co-operated with ABAP programmers to develop the Master Data Load programs. Implemented Batch Management, Purchasing, Purchase Release Strategies, Warehouse Management (with Handling Units) /Inventory Management, Physical Inventory in IM and WM with Cycle Counting, Invoicing/Logistics Invoice Verification, Vandor Payment in Accounts Payable (AP), Automatic Account Assignment in FI, Vendor Evaluation,Materials Requirements Planning (MRP), Forecasting, Vendor Managed Inventory and Consignment. Pricing procedures in MM and SD were put in place especially for the Pricing Procedures related to the Stock Transport Orders. For the Purchase Release Strategies consulted and worked with the ABAP consultant to define and Workflow (WF) strategies. Quality Management integrated with WM, MM and PP in defining Inspection Plans and determining the Material Flow between QM and the other modules. Implemented Classification in many forms and uses. More specifically configured Classification for Release Strategies of Purchase Requisition, Purchase Orders and Contracts. Also configured it for Quality Management (QM), for Plant Maintainance (PM), for Batch Management. Integrated MM and PP for the business process definition and implementation of External Services procurement through the use of Process Orders and External Processing Subcontracting. Also, consulted on implementing MRP/APO/Forecasting for Raw Materials and MROs. Procurement of Services using Service Masters and Service Contracts (Outline Agreements) were defined and implemented. Defined and Configured INTER and INTRA Company Stock Transfers with MRP/APO generated replenishing requirements. Heavy experience in resolving integration issues among SAP R/3 MM-WM-SD-QM with Logistics Execution, Shipping Execution, Freight Cost management and payment. Trained users on all related processes which were implemented by me with classes of approximately 15 to 20 participants. Trained all the SMEs on a global basis – located in Logistics Execution was used for all INTER and INTRA company Stock Transfers for the generation of all necessary shipping and billing documents. This functionality was also implemented in Eurpore (BeNeLux Countries) and worked with ABAPers for the accurate generation of the legally necessary European IntraStat reporting. Determined and created BOMs for the External Services and Subcontracting needs. Managed issues involving several Hazardous materials which had special Government regulations. In addition, consulted and implemented Batch Management and Automatic Batch Determination using Classification for QM, SD, MM, WM, and PP. Also all related printouts were configured, (Quality Certificates, Quality Notifications, Purchase Orders, RFQs, Contract Release Orders, Transfer Orders, Goods Issue/Goods Receipt Documents). ASAP, Visio, MS Project, Lotus Notes were used for this 4.6 implementation. Led and managed a team of approximately 30 people dispersed around the globe (North America, |
DATE: | September 2001 – January 2002 |
CLIENT: | Sulzer Metco (Manufacturing/Chemical) |
POSITION: | Warehouse Management/Materials Management/External Processing with Subcontracting in Production Planning (PP) with Dangerous Material Handling (EH&S). |
RESPONSIBILITIES: Sulzer Metco | Full implementation of 4.6 Warehouse Management with Radio Frequency guns (RF) and Materials Management for this International SAP project. Implementation took place in Used the ASAP Methodology and ASAP Software for the Blueprint creation, monitor and execution of the project. Used Microsoft Project for planning the Tasks and assigning responsibilities. VISIO was used for laying out the Business processes in a graphical representation. Conducted interviews with users and completed the Blueprint. Mapped Vendor Master Data, between SAP system and the legacy BPCS system from SSA. Implemented the Hazardous materials functionality (EH&S). Co-operated with ABAP programmers to develop the Master Data Load programs and provided the specs for several interfaces needed with Non-SAP systems like the interface to the RF guns for the Warehouse Management. Implemented Batch Management, Purchasing, Purchase Release Strategies with Classification, Warehouse Management/Inventory Management, Physical Inventory in IM and WM with Cycle Counting, Invoicing/LIV, Automatic Account Assignment, Vendor Evaluation,Materials Requirements Planning (MRP), Forecasting, Vendor Managed Inventory (VMI), Consignment, Subcontracting. Heavy experience in resolving integration issues among SAP R/3 MM-WM-SD-QM with Logistics Execution, Shipping Execution, Freight Cost management and payment. Configurable (KMAT) material with Variant Configuration using Classification was utilized in certain Business Processes with Make to Stock and Make to Order processes in Production Planning (PP). In addition, consulted and implemented Batch Management and Automatic Batch Determination using Classification for MM, UserTraining was conducted for all the above processes. ASAP, Visio, MS Project were used for this 4.6 implementation. |
DATE: | February 2001 – September 2001 |
CLIENT: | McCormick (Food Industry) |
POSITION: | Warehouse Management/Materials Management/Quality Management. |
RESPONSIBILITIES: Client: MKC Project owned: BRAXTON Consulting Formerly known as Dloitte Consulting | Implementation of 4.6 Materials Management and Warehouse Management for this SAP project. Used the ASAP Methodology for the Blueprint creation, and Microsoft Project for planning the Tasks and assigning responsibilities. VISIO was used for laying out the Business processes in a graphical representation. Conducted interviews with users and completed the Blueprint. Co-operated with ABAP programmers to develop the Master Data Load programs. Implemented Purchasing, Purchase Release Strategies, Warehouse Management (with Handling Units) /Inventory Management, Physical Inventory in IM and WM with Cycle Counting, Invoicing/LIV, Automatic Account Assignment, Vendor Evaluation, Materials Requirements Planning (MRP), Forecasting, Vendor Managed Inventory (VMI) & Consignment. Pricing procedures in MM and SD were put in place especially for the Pricing Procedures related to the Stock Transport Orders. For the Purchase Release Strategies consulted and worked with the ABAP consultant to define and Workflow (WF) strategies. Consulted and implemented Batch Management and Automatic Batch Determination for MM, WM. Also all related printouts were configured, (Purchase Orders, RFQs, Contract Release Orders, Transfer Orders, Goods Issue/Goods Receipt Documents). Heavy experience in resolving integration issues among SAP R/3 MM-WM-SD-QM with Logistics Execution’s Transportation Planning, Shipping Execution, Freight Cost management and payment. Consulted in Quality Management (QM) integration with MM, WM, and PP for the different QM processes in relation to these modules and determined the flow of the Materials among the different Stock Statuses during Goods Receipt from Purchasing or from Production. Trained the SMEs and the Key Users on all above processes. ASAP, Visio, MS Project were used for this 4.6 implementation. |
DATE: | February 2000 – January 2001 |
CLIENT: | Continental General Tires (Automotive – Manufacturing) |
POSITION: | Materials Management Team Leader & Project Management |
RESPONSIBILITIES: Client: Continental Tyres Project owned: Siemans | Leader of the SAP Materials Management module and participation in the Project Management decision making. Project Management plans conducted for the MM module implementation, human resources co-ordination for location and time assignment, training planning for the MM module – responsible for a team of seven. Full implementation of this International SAP project in Implemented Purchasing, Inventory Management, Physical Inventory, Invoicing, Automatic Account Assignment, Materials Requirements Planning (MRP), Forecasting, Vendor Managed Inventory Vendor Managed Inventory (VMI)/Consignment. Leading all modular testing and module-integration testing. ASAP, Visio were used for this implementation. Trained users at two production plants on all processes above. Upgrading testing and implementation from 3.1I to 4.6C and creation of proposal for Upgrading strategy and benefits gained from the upgrade. |
DATE: | October 1999 – February 2000 |
CLIENT: | Metamor |
POSITION: | Sales and Distribution and Materials Management Team Lead |
RESPONSIBILITIES: Metamor Haht | Internal project upgrading SAP from 4.0 to 4.6. Responsible for executing the upgrade and hands on changes in Customizing when problems occurred. Upgrade completed in four and a half months. Also CRM responsibility in implementing MySAP CRM version 1.0. Downloaded Material Master and Customer Master from SAP to CRM, customized CRM’s Tiles. Responsibility in an Advisory role to SAP’s Development Team in Palo Alto, CA for the development of the MySAP CRM Business to Consumer Internet Sales. Additionally, was trained on the Haht SD E-Scenario and Web development experience, web site design, creation and deployment using design software and HTML language. Software knowledge MS FrontPage, HAHT IDE, FusionObject. Implemented E-Commerce sites accepting Credit Card Payments through various types of Merchant Account Vendors. Sites created: www.leaseandsell.netfirms.com,www.jimart.com.mx, www.evolutionary.netfirms.com,www.terapiajesspa.netfirms.com. |
DATE: | May 1999 – September 1999 |
CLIENT: | Sayer Lack (Paint manufacturer) |
POSITION: | Sales and Distribution and Materials Management Team Lead |
RESPONSIBILITIES: Sayer Lack | Responsible for Implementing and resolving issues related to Batch Management and Automatic Batch Determination, in SD and MM modules. Implemented Sales Order processing. Implementation of Billing, Billing Plans, Pricing and Rebate functionality. Improved the process of the company supply chain by modifying the Stock Transports between plants using SAP R/3 SD Delivery Due Lists and Automatic Batch Determination. Also resolved issues involving the Units of Measure and Batch Splits, issues on Physical Inventory and several SD issues caused by bugs in the SAP system. Managed issues involving several Hazardous materials (EH&S) which had special Government regulations. Executed transfers of Configuration Transports among the Development and Productive systems. INTER and INTRA company Stock transfers were implemented using automatic MRP generated replenishment requirements and managing the whole process through the SD process. Trained all users on the above processes. ASAP and Visio Business Process modeler were used for this implementation. |
DATE: | April 1999 to April 1999 |
CLIENT: | Polyfibron Technologies (Printing Industry) |
POSITION: | Materials Management Lead |
RESPONSIBILITIES: | Provided Post-implementation SAP R/3 support, including analysis of the actual system configuration and provided management with proposals for configuration corrections and improvements of system functionality. Provided a proposal for the SAP R/3 upgrade from 3.0F to 4.0B, after the system was analyzed. |
DATE: | March 1999 – March 1999 and March 2001 - April 2001 -Continued support provided until now. |
CLIENT: | MonierLifeTile (Manufacturing) |
POSITION: | Materials Management, Sales and Distribution Lead |
RESPONSIBILITIES: | Responsible for user training on the Material Master maintenance, which was specific to MonierLifeTile. Created thorough, step-by-step user manuals. Implementation of Billing, Pricing and Rebate functionality in Sales and Distribution (SD) module. |
DATE: | February 1999 – June 1999 and September 1999 – December 1999 – On-going support continues… |
CLIENT: | Multiquip (Manufacturing Industry) |
POSITION: | Senior Consultant – MM/SD Serialization Management Lead |
RESPONSIBILITIES: | Analyzed and configured the Automatic Account Determination in the SAP R/3 MM (Materials Management) module. Optimized the company’s Purchasing procedures, and Stock Transfers and implemented the Hazardous materials functionality. Implemented Materials Requirements Planning (MRP) and Forecasting in PP and MM. Serial numbers and full tracking of these materials with their Serial Numbers in SD and MM were used in this implementation. Also missing material notification was implemented for the appropriate users to receive automated SAP Office messages (WorkFlow) when the materials were available. Heavy experience in resolving integration issues among SAP R/3 MM-WM-SD-QM with Logistics Execution, Shipping Execution, Freight Cost management and payment. Training of all users on all the above processes. On-going support to this client continues on an as-needed basis. ASAP and Visio were used for this implemenation. |
DATE: | May 1997 to February 1999 |
CLIENT: | Gruma (Food Industry) |
POSITION: | Materials Management/Quality Management Lead and Project Management |
RESPONSIBILITIES: Project Owned by: HP, SAP | Designed and implemented the SAP R/3 system in the Client/Server environment, as part of an integrated Enterprise Wide system for Gruma. Designed the blueprint and performed the validation and integration testing procedures. Implemented all parts of the SAP R/3 MM (Materials Management) module and optimized the company’s Purchasing procedures. Tested integration issues in the SAP R/3 MM (Materials Management), SD (Sales and Distribution) and QM (Quality Management) modules. Managed the implementation of Hazardous Materials in integration with MM-SD-QM. Implemented procedures for Vendor Managed Inventory/Consignment from the MM and SD point of view. Implemented Materials Requirements Planning and Forecasting. Heavy experience in resolving integration issues among SAP R/3 MM-WM-SD-QM with Logistics Execution, Shipping Execution, Freight Cost management and payment. Qualitative and Quantitative inspection procedures were implemented. Worked with developers in functionality design and blueprinting of specific enhancements and legacy system integration for QM. Certain Quality Inspection processes were modified to be performed before actual Goods Receipt through my design and specs creation for User Exits and custom SAP programs. Physical Inventory Procedures were analyzed configured and implemented. Also Vendor Managed Inventory/Consignment, Subcontracting and Contract Service Management was defined and implemented. Determined which Material Types were to be used, configured and helped the users with the determination and collection and cleaning strategy of the Master Data for a successful upload. Responsible for all five Divisions of Gruma’s, in Trained all SMEs and Key Users of the five divisions in |
DATE: | March 1997 to April 1997 |
CLIENT: | Airtour |
POSITION: | Consultant |
RESPONSIBILITIES: | Implemented special Purchasing requirements, including special printing, Purchase Order printing requirements and SAPSCRIPT Purchase Order format modifications. |
DATE: | December 1997 – March 1997 |
CLIENT: | Mobil (Oil Industry) |
POSITION: | Consultant |
RESPONSIBILITIES: | Responsible for the blueprints and implementation of the Purchasing Optimization procedures, Consumption MRP and modification of the SAPSCRIPT Purchase Order forms. Also Inventory Management and Vendor Evaluation. Hazardous materials had to be maintained in the system for Government, Public Safety and Quality compliance rules. The SAP IS-Oil was implemented for this project. |
DATE: | September 1996 to December 1997 |
CLIENT: | Telestet (Telecommunications Industry) |
POSITION: | Consultant |
RESPONSIBILITIES: | Responsible for the blueprints and implementation of the Purchasing Optimization procedures, Consumption MRP and modification of the SAPSCRIPT Purchase Order forms. Third Party Sales Order processing, and Vendor Managed Inventory (VMI) i.e. MRP and ATP data of Customer-Vendor Requirements through EDI between the different divisions of Telestet (Telestet Wholesaler and MobiTel Retailer). |
DATE: | January 1996 to August 1996 |
CLIENT: | Beierdorf – BDF (Chemical Industry) |
POSITION: | Consultant |
RESPONSIBILITIES: | Responsible for training users in Purchasing, Inventory Management, MRP and Invoice Verification, created user manuals and Business Process Procedure Testing documents. |
DATE: | July 1995 to December 1996 |
CLIENT: | Hoechst (Chemical Industry) (Now called Aventis) |
POSITION: | Consultant |
RESPONSIBILITIES: | Responsible for training users in Purchasing, Inventory Management, MRP, Invoice Verification, created user manuals and Business Process Procedure Testing documents. |
LANGUAGES
English | Fluent |
Spanish | Fluent |
Greek | Fluent |
Italian | Intermediate |
CERTIFICATION, EDUCATION & TRAINING
Degree/Certification | Course/Major | Date Completed |
Haht SD E-Scenario | E-Commerce | January 2000 |
B2B | SAP B2B | September 2000 |
CRM | SAP CRM | October 2000 |
Delta 4.0 Ã 4.6 | SAP MM/SD/WM/QM Delta | November 2000 |
LO530 WAREHOUSE MANAGEMENT 4.0 | SAP | June 1999 |
LO531 ADVANCED WAREHOUSE MANAGEMENT 4.0 | SAP | June 1999 |
LO605 SALES ORDER PROCESSING 4.0 | SAP | July 1999 |
D40MM PROCUREMENT 4.0 DELTA, SAP R/3 MM | SAP | January 1998 |
LO705 BASICS in QUALITY MANAGEMENT 3.1 | SAP | February 1998 |
WB915 ASAP (ACCELERATED) ROADMAP 3.1 | SAP | March 1998 |
Industry Solution Oil (IS-Oil) Certification | SAP | January 1996 |
CERTIFICATION, SAP R/3 MM 2.2, SAP Hellas, | SAP | January 1996 |
ACADEMIC CREDENTIALS: | |
| |
· B. A., BUSINESS ADMINISTRATION, HONORS,
|
SAP R/3 Tips & Tricks TOP
- Logging on without being authorized
Client 066 usually exists in a SAP system because of EarlyWatch services. Often this client does not have master users. If it is true, anyone can log into the system using the client 066, user SAP*, and
- Special copy and paste
Click on the area and press CTRL+Y. It allows you to copy many lines at once and paste them afterwards.
- Long messages on footer
Click on the message and hold the mouse button. After moving the mouse to the left side.
- Direct input logs
The transaction BMV0 (direct input logs) shows all direct input logs.
- Graphics on SAPscript
The program RSTXLDMC can be used to upload graphics (file extension .tif on PC files) into individual standard text.
- Adding icons
The include «ICON» can be easily used in your programs. All icons can be checked through the transaction ICON. Sequences of characters begin and finish with the symbol @. Even plain files under operating system can contain those strings.
- Adding symbols
The include «SYMBOL» can be easily used in your programs. It makes available a great number of symbols.
- Filling up an empty date field quickly
Strike the key F4 (or click on matchcode symbol) and press ESCAPE. The current date is automaticly set.
- Setting up module FI/CO without using IMG
Almost all parameters can be set using the transactions ORFA (Asset Accounting), ORFB (Financial Accounting), and ORKS (Cost Center Accounting).
- Deleting cost elements and cost centers
Since they have no postings you can use the transaction KA04 for deleting cost elements and KS04 for deleting cost centers.
- Displaying check object when not authorized
Soon after the lock try to access the transaction SU53. It reports the last objects verified and also the respective values.
- Table analyses between two systems
The contents of a table between two systems can be checked through the transaction OY19.
- Correction and transport system
The transaction SE10 provides the easiest way to manage any request/transport and corrections.
- General command field formats
/n | Skip to the next record if you are processing one batch input session |
/bend | Cancel a batch input foreground process |
/nend | Close all R/3 sessions and logoff |
/nxxxx | Call the transaction xxxx in the same session |
/o | Generate a session list |
/oxxxx | Call the transaction xxxx in an additional session |
/i | Delete the current session |
/h | Turn the debug mode on |
/$tab | Reset all buffers (for System Administrators) |
/$sync | Synchronize instances buffers (for System Administrators) |
- Report command field formats
%pri | Print the current report |
%pc | Download the current report |
%sc | Call the find function |
p+ | Go to the next page |
p- | Go to the previous page |
p++ | Go to the last page |
p-- | Go to the first page |
- Helpful reports
RSCLTCOP | Copy tables across clients |
RSAVGL00 | Table adjustment across clients |
RSINCL00 | Extended program list |
RSBDCSUB | Release batch-input sessions automaticly |
RSTXSCRP | Transport SAPscript files across systems |
RSORAREL | Get the Oracle Release |
RGUGBR00 | Substitution/Validation utility |
RSPARAM | Display all instance parameters |
RSUSR003 | Check the passwords of users SAP* and DDIC in all clients |
RSUSR006 | List users last login |
- Meaning of info structures' first letter
A | Pricing |
B | Output determination |
C | Account determination |
D | Material determination |
E | Rebates |
F | Index |
G | Listing and Exclusion |
H | Batch determination |
I | Profile determination |
S | Statistics |
X | Statistics extra |
- Unconditional mode when importing or exporting a request/transport
Run the command R3trans -u under user «SysID»adm.
- Reapplying hot packages
If you accidently applied hot packages out of sequence for instance. Use the transaction SM31 to modify table PAT03. You have to choose the desired patch and click on delete entry.
- Main return codes of tp program
0 | Successfully done |
4 | Warnings occurred |
8 | Errors occurred |
12 | Fatal errors occurred |
16 | Internal errors occurred |
- Scheduling of system maintenance jobs
RSBTCDEL | Clean the old background job records |
RSDBCREO | Clean batch input session log |
RSPO0041 | Removing old spooling objects |
RSSNAPDL | Clean the old ABAP error dumps |
- List of most used SAP extensions and their components
CUST1 | MENUS000+C01 | Customer option in the Office menu |
CUST2 | MENUS000+C02 | Customer option in the Logistics menu |
CUST3 | MENUS000+C03 | Customer option in the Accounting menu |
CUST4 | MENUS000+C04 | Customer option in the Human Resources menu |
CUST5 | MENUS000+C05 | Customer option in the Information Systems menu |
CUST6 | MENUS000+C06 | Customer option in the Tools menu |
CUST7 | MENUS000+C07 | Customer option in the System menu |
ZXUSRU01 | Exit_saplsusf_001 | At login time |
SAPMF02D | Exit_sapmf02d_001 | When saving customer master data |
SAPMF02K | Exit_sapmf02k_001 | When saving vendor master data |
M61X0001 | Exit_saplm61c_001 | When processing MRP planning |
M61X0001 | Exit_sapmm61x_001 | When processing MRP planning |
FYTX0001 | Exit_saplv61a_001 | Modifications in pricing procedures |
MBCF0002 | Exit_sapmm07m_001 | Checks for materials documents |
SDVFX002 | Exit_saplv60b_002 | Link between SD and FI documents |
M06B0003 | Exit_sapmm06b_001 | When saving MM documents |
- Before going live
It is highly advisable to increase the next extend´s size of some tables and their indexes even before initial loadings
FI | BKPF, BSEG, BSIS, BSAD, BSAK, BSID and BSIK |
CO | COEJ, COEP, COKS, COSS and T811* |
AM | ANL* |
MM | MKPF, MSEG and BSIM |
SD | VBAP, VBAK, VBEP, VBPA, LIKP, LIPS, VBRK, VBRP, VBKD, VBUK, VBUP and VBSS |
PP | RESB and MDTB |
Accross module | ATAB, TST03, TSP01, MCSI, KNVP, ACCTIT, COEP, APQD, RFBLG, CDCLS, SDBAD and from S000 to S999 |
- Locking the whole system
Using the command tp locksys «SysID» only the user SAP* will be allowed to login. The command tp unlocksys «SysID» cancels the lock.
- Connection between SAP R/3 and operating system
The command sapevt can be used to trigger an event from the operation system. Thus, a job previously defined within R/3 will be released.
- SQL code help
Run the command oerr ora «error number» under user ora«SysID».
- Oracle import and export explanations
Run the command imp help=yes under user ora«SysID». This format can also be used with exp, impst, andexpst.
Note: | Research based on version 3.0f under Unix, Oracle data base and Windows. |
SAP R/3 Hints TOP
Of course it does not guarantee a successful implementation. It is a great deal of summed up aid, though.
- Team integration has to be enhanced
- Set high standards of performance for implementation team
- IT teams and users have to work closely during the implementation
- New ways of thinking and acting must not be discarded
- Do not underestimate the user training needs
- Project management should be on the critical list
- The nearest SAP branch should be your partner
- Consultants are not always the key to succeed
- Consultants are a good source of knowledge. On the other hand, letting them make configuration changes the transfer of knowledge will be harmed
- Foreign consultants usually do not know country-specific details
- Deepening your basis knowledge is always useful
- Avoid changing standard R/3 objects as much as possible
- Always follow the SAP rules to give names to your own objects
- Establish SAP connection as soon as possible
- Exchange information with other companies
- Focus on interfaces with non-R/3 applications
- Plan the whole environment carefully (servers, network, protocols, etc.)
- Development and production environment should be totally independent
SAP R/3 Enhancements TOP
Some special features allow you wide modifications without changing standard SAP R/3 objects. Those techniques are not as widespread as they should be. In fact they are powerful tools.
- Field exit
After entering a value in a field, it can be checked through a field exit. The system makes the field value available to be checked and changed in an ABAP/4 function. - User exit
Points previously set in the system that let you evaluate data. The fields available are also previously defined by SAP. All fields value available can be checked in an ABAP/4 program. - Validation
It allows solid data entry regarding special rules. According to previous rules, the system can evaluate an entry and a message can appear on the user's terminal if a check statement is not met. A validation step contains prerequisite statement and check statement. Both of them are defined using Boolean Logic or calling an ABAP/4 form. - Substitution
Fields contents can be changed using substitution. When data are being entered, the data can be substituted by another value regarding rules previously defined. A substitution step contains prerequisite statement, substitution value and substitution exit. All of them are defined using Boolean Logic or calling an ABAP/4 form. - Set
Values or ranges of values are specified under a set name. Sets are easier to create and maintain instead of using tables. They give you more flexibility when maintaining your system. - Key words
It allows changes on field description according to data element. The short key word used on most screen to identify the corresponding field contents can be changed too. - Requirements & formulas
ABAP/4 forms that can be used to handle pricing procedures, rounding rules, copy and data transport Sales activities.
Note: | In spite of flexibility, you should think at least twice before applying any enhancement. |
Generally speaking, validation and substitution are available on Asset Management, Controlling, Financial Accounting, and General ledger. |
SAP R/3 Troubleshooting TOP
- System gets stuck
It happens mostly when archive area is overloaded. Run the program brarchive with deletion option to release disk space. - Short dump
Not always the problem is technical. Try to create all SAPoffice users through transaction SO32 (create all SAPoffice users) and review your application data carefully. - Field exits are completely ignored
Make sure your SAP profile parameter contains the option abap/fieldexit = yes. - Transaction SE16 (table contents) does not work properly
Make usage of the menu option to regenerate the display program. You can also try changing key words according to field names. Choose Option -> Parameters users. - Rollback segments are too small
Before increasing up the rollback segment size you should verify your programs. Very often the problem belongs to them. - Files for rollback segments are already enormous
Check the rollback segments configuration. It has to match the allocated area on tablespaces. Changes have to be done using Oracle tools. - Extended help under windows does not link correctly
Check the file sapdoccd.ini under your presentation server. It must be present in the main windows directory and should assign to help files directory. - Release procedure with classification does not work
As a matter of fact you are not the only one to notice it. It hardly works. Before using release strategy you should apply all notes on - Transport area is overloaded
The command tp clearold «SysID» cleans up the transport area according to parameters previously set on the plain file TPPARAM. - Instance does not establish communication
Shutdown the whole system and check the Interprocess Communication Facilities. Any references should be found. Either the command IPCS (UNIX) or showipc «INSTANCE NUMBER» (SAP) show all message queue, semaphore set and shared memory identifier. Before trying again you have to remove them using the commandIPCRM (UNIX) or cleanipc «INSTANCE NUMBER» (SAP).
Note: | Research based on version 3.0f under Unix, Oracle data base and Windows. |
SAP R/3 Security TOP
Simple changes can rise your system security. Usage of SAProuter is a good choice when correctly implemented. Login through SAP LogonPad (from version 3.0f onwards) improve the access control. SAP profile parameters shall also contain:
- Rdisp/gui_auto_logout = 1800
The user connection is closed after 30 minutes without usage. - Login/fails_to_session_end = 3
After 3 wrong password the connection is automaticly closed. - Login/fails_to_users_lock = 5
After 5 wrong password the user is locked. - Login/min_password_lng = 6
Password length at least 6 characters. - Login/password_expiration_time = 90
Password expires after 3 months.
Note: | I do not have to waste my time telling you to change all default passwords. |
Make sure to have the master user SAP* in all clients otherwise anyone can log into your system. See Tips & Tricks. |
SAP R/3 Programming TOP
Indeed these powerful ABAP/4 functions are very interesting and can bring some advantages. Improve your home development easily. They belong to standard objects and should never be changed.
- Bp_event_raise
Trigger an event from ABAP/4 program.
- Bp_joblog_read
Fetch job log executions filling the structure TBTC5.
- G_set_get_all_values
Fetch values from a set filling the structure RGSB4.
- Popup_to_confirm_loss_of_data
Create a dialog box in which you make a question whether the user wishes to perform a processing step with loss of data.
- Popup_to_confirm_step
Create a dialog box in which you make a question whether the user wishes to perform the step.
- Popup_to_confirm_with_message
Create a dialog box in which you inform the user about a specific decision point during an action.
- Popup_to_confirm_with_value
Create a dialog box in which you make a question whether the user wishes to perform a processing step with a particular object.
- Popup_to_decide
Create a dialog box in which you require the user between the two processing alternatives, or to cancel the action.
- Popup_to_decide_with_message
Create a dialog box in which you inform the user about a specific decision point via a diagnosis text.
- Popup_to_display_text
Create a dialog box in which you display a two-line message.
- Rfc_system_info
Fetch information from the current instance filling the structure FRCSI.
- Rs_send_mail_for_spoollist
Send messages from ABAP/4 programs to SAPoffice. The structure SOLI may contain the message.
- Rzl_sleep
Hang the current application from 1 to 5 seconds.
- Rzl_submit
Submit a remote report.
- Sapgui_progress_indicator
Set progress indicator on the left lower corner of the current window.
- Sd_print_terms_of_payment
Format terms of payment according to base line date and payment terms.
- So_wind_spool_list
Browse printer spool numbers according to user informed.
- So_spool_read
Fetch printer spool according to the spool number informed.
- So_user_list_read
List of all users filling the structure SOUD3.
- Spell_amount
Return the amount in words filling the structure SPELL.
- Th_saprel
Gather information from the current system including upgrade activities. It completes fields from the structure KKS03.
- Th_server_list
Gather information of all instances filling the structure MSXXLIST.
- Th_user_list
List of logged users filling the structure UINFO.
- Th_user_info
Information about the current user. It completes fields from the structure KKS03.
- Th_wpinfo
List of work processes filling the structure WPINFO.
- Ws_upload
Transfer files from the frontend to the application server.
- Ws_download
Transfer files from the application server to the frontend.
- Ws_excel
Download files at the frontend in excel format.
- Ws_execute
Execute an external program on the presentation server.
- Ws_file_delete
Delete file at the frontend.
- Ws_volume_get
Get the label from a frontend device.
- Ws_msg
Create a dialog box in which you display an one-line message.
Note: | These functions have been used and have worked as well as they were supposed to do. |
SAP R/3 Glossary TOP
Information Technology has many key words and SAP R/3 has introduced many others. In order to understand even better this field you should keep in mind those terms.
- ALE (Application Link Enabling)
It provides integration for separate R/3 systems, keeping full interaction. This makes possible distributed enterprise applications. - Application server
The application server is used to run the business application programs in the R/3 client/server concept. The application modules are loaded from the data base server to the application server as required. Thus the application server requires only storage capacity to accommodate UNIX, Swapping and the SAP runtime environment. - Batch Input
A technique to input data safely. It ensures application data integrity for background interfaces. It pretends to be someone typing. See also direct input. - CATT (Computer Aided Test Tool)
It allows you to combine and automate sequences of repeatable transactions in test procedures. CATT reduces the number of manual tests, and forces you to test systematically, defining input values and expected test results. - CCMS (Computer Center Management System)
It allows you to monitor, control and configure your R/3 system. This toolset lets you analyze and distribute client workloads and report on resource consumption for system components. - Central System
In an R/3 central system, both application and data base software are run on one computer. - Client
In commercial, organizational and technical terms, a self-contained unit in an R/3 system with separate master records and its owns set of tables. - Client/Server System
Client/server systems are structured modularly, with components working in a sender/receiver relationship. Software components can also be used in a client/server relationship. - Communication Server
It provides the connection between local area and wide area networks and may be either a router, a bridge or a gateway. In R/3 installations, the communication server must support the TCP/IP protocol over wide area networks. - Company code
The smallest organizational unit for which a complete self-contained set of accounts can be drawn up for purposes of external reporting. This involves recording all relevant transactions and generating all supporting documents for legally-required financial statements, such as balance sheets and profit and loss statements. - Computer type
The R/3 system supports various computer types of SAP's platform partners, such as Bull, DEC, IBM and HP. The suitability of a particular computer type depends on sufficient CPU performance. - CPI-C (Common Programming Interface-Communications)
Common Programming Interface of Communication has been introduced by IBM as a high-level interface to SNA/LU6-2. CPI-C has become the subject of the X/Open stardarlization and is used by SAP to facilitate program-to-program communication between R/3 and external system. SAP offers CPI-C libraries based on TCP/IP. - Correction
It contains all the objects that a developer has changed or created. It also controls customizing that has been maintained. - CSP
A system to help SAP employees to give comprehensive support to their clients. - Data base server
The data base server stores the SAP application programs and data in the R/3 client/server concept. It also handles the SAP update program and batch jobs. - Direct Input
A recent technique to input data safely. It ensures application data integrity for background interfaces. See also batch input. - Dispatcher
The system R/3 agent that identifies the type of task (on-line, update, batch, etc.) and sends the job to an idle work process. - EarlyWatch
It is a service that entails having your R/3 installation regularly inspected by SAP employees, in other to ensure high system availability and high data throughput at all time. - Ethernet
It is a LAN architecture using bus topology. The transmission speed is 10 MBit/s. - FDDI (Fiber Distributed Data Interchange)
It is a local high-speed network with ring topology based on light wave conductors. The transmission speed is 100 MBit/s. - Field status
Indicator that specifies whether a field can take an entry in the entry screen or if it must be filled. - Firewall
It is a means of controlling access through a public network to a private network. - FTP (File Transfer Protocol)
It is the most commonly used file transmission protocol of the TCP/IP protocol family. - GUI (Graphic User Interface)
A graphical interface used by SAP environment as part of the three tiers. It is normally called user frontend. - IDES (International Demonstration and Education System)
It is a model of an international firm. It is a separate demonstration and education system for speeding up the pilot process. - IMG (Implementation Management Guide)
It is a hierarchical structure that reflects the R/3 component hierarchy and contains every configuration activity. Released from version 3.0 onwards. - Instance
It means application server and each one has its own set of work processes. - IDoc (Intermediate Document)
An IDoc is a data container for data exchange between SAP systems or between an SAP system and an external system. - ITS (Internet Transaction Server)
It links the R/3 application server with one or more Web servers, thus enabling the R/3 to communicate with the Internet. - Kernel
It means a standard core previously configured. A set of default parameters delivered with the system. - LAN (Local Area Network)
It is a network foa a tightly limited area with high level data transmission performance. Common LANs include Ethernet, Token Ring and FDDI. These LANs support different transport protocols, such as TCP/IP and IPX. - Matchcode
A tool for finding specific record. It is made up of search terms. It is used to find possible entries for an input field. - Number range
A range of numbers that are laid down per file for the assignment of document numbers. It can be internal (carried out automatically by the system) or external (carried out manually by the user). - OLE
It is a technique introduced by Microsoft to incorporate objects of one application into another.
SAP's Online Service System offers fast and effective help for R/3 System problems. It is also the basic element of communications between customers, partners, and SAP.- Repair
It contains all the objects that a developer has changed but the originals of the objects are located in another system. - RFC
A way to implement communication between application programs via Abap/4 function call. - Semaphores
When a work process locks a resource, it sets a semaphore. Another work process that also wants to access it must then wait. - SysID
A set of three letters or number that identify a system. Some sets are not allowed because they are used by SAP. They are informed when the system is installed. - TCP/IP
It is the most widely used transport protocol for open systems. R/3 clients and servers communicate using TCP/IP. - Telnet
It provides terminal access to hosts using TCP/IP protocol. It is a well-known command among Systems Administrators. - Token Ring
It is a LAN architecture with ring topology. The transmission speed is 4 MBit/s or 16 MBit/s. This involves a 'free token' which circles the loop picking up transmissions. The receiver station places a confirmation bit into the busy token. As soon as the busy token reaches the sender station again, it is converted back to a free token and sent on to the next station. - Transport
It is a request to transport objects from the software development environment, identified as the source system, to the specified target system. - WAN (Wide Area Networks)
They are normally operated either by the telephone company or by private companies that offer leased lines, switched lines or packet lines. - Work process
Work processes perform the bulk of the processing carried out by SAP systems. They perform dialog steps in user transactions and carry out updates, lock management, printing services, and so on. - Workbench
The ABAP/4 Workbench, a graphical programming environment, is used to create application programs. The programming tools are accessed using buttons, dialogs and windows. - Workflow
It consists of time and logical sequence of work items, which are processed by human agents or mechanical processing units. - X.25
It is a standardized network access protocol for the packet switching network. The maximum transmission speed is 64 KBit/s.
Many people say it cannot be considered only as a software but a way of doing business. Actually it forces the company to review its business processes. As a result business processes can be changed or not. If so, it means new designs based on built-in best pratices.
Graphical models help users understand the application software, showing how data flow through business areas and how they interact with each other. A good example of how SAP R/3 is usually implemented can be found at the simple flow chart presented below.
Each business process has a segment previously set. It is known as business application areas and make you understand better the whole system. They also provide you the level of SAP R/3 covering.
Even if you do not look forward to implementing a module, sometimes you have to set it partially. It happens commonly due to the integrated nature of the system. Functionalities have been put together establishing modules. The official division has the following configuration.
CA | Cross-Application Functions |
FI | Financial Accounting |
TR | Treasury |
CO | Controlling |
IM | Investment Management |
EC |
|
LO | Logistics General |
SD | Sales & Distribution |
MM | Materials Management |
QM | Quality Management |
PM | Plant Maintenance |
PP | Production Planning |
PS | Project System |
PD | Personnel Planning and Development |
PA | Personnel Administration and Payroll Accounting |
IN | International Development |
BC | Basis Components |
Wow.. Thanks much for sharing.. My friend also recommended you so that i can have a helping hand to make my blog as effective as possible.
ReplyDeleteSAP Training in Chennai
SAP FICO Training in Chennai
SAP ABAP Training in Chennai