Free Download SAP MM Books And Interview Questions

Latest SAP MM Interview Questions

noreply@blogger.com (Anonymous) — Thu, 18 Mar 2010 05:49:00 +0000

The following are some sample interview questions I have taken from the internet, sample certification questions, and from my own experience.

1. What is the difference between the stock transfer between two plants belonging to same company code and those belonging to different company code?
2. What are the fields in Purchasing view?
3. What are the steps in automatic account assignment config.
4. How do you create movement types? What are the steps involved? When will you recommend a new movement type?
5. What is meant by access sequence? When it is used?
6. How does the PO pick up the pricing schema?
7. What are the steps involved in creating a pricing procedure?
8. What are the types of special stocks available?
9. What are the types of inforecords?
10. What is meant by consignment stock?
11. What are the steps involved in consignment cycle?
12. Tell me about the subcontracting cycle.
13. How is scrap accounted in subcontracting?
14. How are the byproducts taken care of in subcontracting?
15. Tell me about the various movement types and usage.
16. What is meant by scales? Can scales be used in standard purchase order?
17. What is the difference between a contract and a scheduling agreement?
18. How does the system calculate taxes?
19. How does the system calculate nondeductible taxes?
20. What is meant by batches? How can the batches be searched?
21. How is a shelf-life item managed in SAP? What is the full cycle?
22. What are the settings required for quota arrangement?
23. What is meant by MRP Type and lot sizing?
24. Can it be configured in such a way that the external requisitions can also be taken into account while MRP runs in consumption-based planning if VB is selected as MRP type?
25. What is a reference purchase organization? When can it be used?
26. Explain the concept of split valuation and when can it be used? What are the settings required?
27. What are valuation area, valuation category and valuation class?
28. What is meant by a credit memo?
29. How are free items managed in a PO?
30. What is meant by a release strategy?
31. What are release groups and release codes?
32. What are the differences between release procedure with classification and release procedure without classification? When are they used?
32. Is it possible to have a release procedure without classification for a PO?
33. What is the maximum number of levels available in SAP?
35. Is it possible to have scales in a quotation?
36. What is GR blocked stock? When it can be used?
37. What is the movement type for return to vendor? How to reverse it?
38. How are the variations in subcontracting taken care of in SAP?
39. What are the tools available for data migration in SAP?
40. What is LSMW?
41. What is the difference between LSMW and CATT?
42. How to give specifications for developments?
43. How do you plan for a vendor rating system and move about?
44. What is RTP?
45. What is the movement type used in receipt of RTP?
46. How is an item with serial no. managed?
47. How do you make variants?
48. What are the types of tables in SAP?
49. How to inventory excise duty in SAP?
50. What are the documents generated in the MIGO 101 movement type? What are the accounts hit?

Here are some SAP MM Certification sample questions you should know the answer to:

Question:
You wish to procure a material using a purchase order. You wish to take delivery of the material at different times. A graduated discount scale exists for the material. How do you proceed if you wish to take advantage of the discount arr

Basic Rules in SAP-Sales and Distribution Module

noreply@blogger.com (Anonymous) — Thu, 17 Sep 2009 05:25:00 +0000

Sales Organization :

Responsible for:

Distribution of goods and services
Negotiating Sales Conditions
Product Liability and rights of recourse
A sales organization is uniquely assigned to a company code
Master data’s are separately maintained for a sales organization
All items in the Sales and Distribution document belong to a sales organization

Distribution Channel:

Means through which products and services reach the customer

A distribution channel:

Defines responsibilities
Helps in achieve flexible pricing
Differentiate Sales statistics

Division:

A division is used to group products and services.

A division represents a product line.

Sales Area:

A Sales area is a combination of

Sales organization
Distribution Channel
Division

Each Sales and distribution document is assigned exactly to one sales area.

A sales area can belong to only one company code.

Sales Organization

Distribution Channel

Division

Sales Area

Plant and Storage Location:

A Plant is a location where stock is maintained

Plant and storage location are used by all logistic area of R/3 System

A Plant is uniquely assigned to a company code

Shipping point:

Shipping point is the highest level of organizational unit in shipping

Each outbound delivery is processed by one shipping point

Shipping points are assigned to a plant

More than one shipping point can be assigned to a plant

Sales and Distribution is SAP begins with establishing customer relationship and ends with invoicing for the delivery of goods or service provided to the customer .

A Standard sales transaction has the following flow:

Inquiry

Quotation

Order

Delivery

Billing

The customer order management cycle begins with pre-sales activities.

A standard order in SAP contains:

Customer and material info
Pricing conditions
Delivery dates and quantities
Shipping info
Billing Info

Inventory sourcing in SAP is taken care by

Availability check

Shipping in SAP supports

Outbound delivery creation
Picking
Packing
Post Goods Issue

Billing in SAP supports

Creating invoices for products and services

Creating credit and debit memo

Cancel previously posted billing documents

Automatically transferring billing documents to accounting

When a billing document is created for a sales order we

Credit the sales revenue account

Debit the customer receivables account

Sales Document

A sales document is grouped into three structures

Header

Item

Schedule Line

Outbound delivery

A delivery document is grouped into two structures

Header

Item

Several orders can be grouped into same outbound delivery if they have same

Shipping point

Delivery date

Ship-to- address

Picking

A transfer order is created for an outbound delivery

A transfer order is created for a warehouse number

Post Goods Issue

When PGI is done the system

Updates the quantity in inventory management and delivery requirements in materials planning

Generates additional documents for accounting

Adds the delivery to the billing due list

Updates status in sales documents

Billing

We can group deliveries into single billing document if the deliveries have same

Billing date

Payer

Destination Country

The effects of billing are

Debit on the customer receivables account and credit on sales revenue account is created

Sales information system

Sales statistics is updated

Master data in SAP

SAP SD has got the following main masters:

Customer master

Material master

Condition master

Output master

Customer material information master

Customer master

General Data Sales Area Data Company Code data

Tab pages Tab pages Tab pages

Address Order Accounting

Control data Shipping Payment

Payment terms Billing Correspondence

Marketing Partner functions Insurance

Unloading points

Export data

Contact persons

The chart above shows detail on three main areas of customer master and the tab pages found under each area.

Material Master is maintained in different views and important views of sales and distribution are

Basic data 1

Sales Org 1

Sales Org 2

Sales : Gen/Plant

Foreign Trade

Sales text

Sales document in Sales and distribution mainly controls:

Number range

Item No increment

Reference mandatory

Item division

Read info record

Document pricing procedure

Incomplete messages

Alternative sales documents

Delivery block

Billing block

Immediate delivery

Delivery type

Billing type

Proposed delivery date

Lead time for delivery

Proposed pricing date

Plant determination in Sales and distribution:

To determine the plant in an order the system checks the master in the following order:

a) Customer material info. record of the sold-to –party

b) Customer master record of the ship-to-party

c) Material master record of the material

Shipping point determination

The following rule is used in determining shipping point in a sales order :

Plant + Shipping condition (Sold-to-Party) + Loading group Shipping point

Maintained in Material master Gen: Plant data

Route determination

Route determined using the following rule in Sales and Distribution (SAP)

Departure Zone of Shipping Point

Shipping condition (Sold-to-Party)

Transportation Group (Material master)

Transportation Zone (Ship-to-Party)

Route

Delivery scheduling:

As name denotes delivery scheduling is scheduling delivery for an order and it carries the following important dates:

Material availability date
Transportation planning date
Loading date
Goods Issue date
Delivery date

Availability Check in SAP:

Availability check is carried out at item level for a plant

Availability check is done on the material availability date

If material availability date is in the past the forward scheduling is done, if not backward scheduling is done.

Item category determination in the order:

Item category denotes the category to which the item belongs and the following rule is used for determination of item category. Item category controls the way in which item behaves in a sales document.

Sales document type

Item category group (Material master)

Item usage

Item category of higher level item

Item category of the item

Item category in a sales document mainly controls the following

Relevance for billing of an item

Billing block
Pricing relevance
Business data relevance item
Schedule line allowed
Item relevant for delivery
Returns
Determine cost
Credit active
Incompletion procedure
Partner determination procedure
Structure scope (relevant for bill of material explosion)
Value contract material
Contract release control

Schedule line category:

Every item which has a delivery will have a schedule line and the schedule line category is determined with the following rule:

Item category + MRP type(Material Master) Schedule line category

Schedule line category mainly controls:

Delivery Block
Movement type
Item relevant for delivery
Req/Assembly
Availability
Product Allocation

Copy Control:

Copy control is normally set for

Header
Item
Schedule line levels

To control copying procedure we have

Data transfer routines
Copying requirements
Switches

Pricing Procedure determination:

Pricing is an important component in SAP-SD. Once an order is entered taking into consideration some major factors, the pricing procedure for the particular order is determined.

The major factors taken into consideration for pricing procedure determination is:

Sales area

Customer Pricing procedure(Customer Master –Sales area data)

Document Pricing Procedure(Sales Document Type)

Pricing Procedure

What are the components of pricing procedure?

How is that a person should work on Pricing Procedure?

To start with first

Define a Condition table:

What is a condition table?

A table where the key fields are data combinations for which messages are triggered (and offered for processing).

For each data combination, there is a condition record in the table. The data part contains the actual message.

As mentioned above a condition table is a table which carries key fields for picking up the prices.

Define Access Sequences

The access sequence is a search strategy which the SAP System uses to search for condition records valid for a condition type.

For example, you can define for a price that the SAP System first searches for a customer-specific price and then for a price list price.

Recommendation

· If you define your own access sequences, the key should start with the letter Z since SAP reserves this letter for the standard system.

· Do not change access sequences contained in the standard SAP R/3 System.

Actions

1. Check to what extent you can use the access sequences contained in the standard SAP R/3 System.

2. Create new access sequences by copying a similar access sequence and changing it according to your needs. Specify an alphanumeric key which may have up to 4 digits and a textual description.

3. Maintain the accesses for the access sequence by specifying the condition tables in the desired sequence. With the sequence, you define the priority of the accesses. You can display combinations of key fields using possible entries.

4. Generating the accesses is no longer necessary as of 3.0, as this is carried out automatically. You can generate the accesses manually, if required, by choosing "Utilities".

Example

In pricing, you use a customer-material discount. The condition records you create are based on customer data from the document header and material data from each document item. The discount is only valid for 2% of your customers, however. Normally, this would mean that the system would needlessly search through every available item for 98% of your customers. In this case, pre step would improve system performance.

Define Condition Type

A characteristic of a condition. For example, in pricing, different condition types are used to distinguish between a discount that refers to a net price and a discount that refers to a gross price.

Price elements are represented in the SAP system by condition types. Price elements can be, for example, prices, surcharges, discounts, taxes or, freight, and are stored in the system in condition records.

You can, for example, define whether a discount is calculated as a percentage or a fixed amount using the condition type.

You specify an access sequence in every condition type. Thus, you define which fields the SAP system checks when searching for a valid condition record.

Note

The pricing procedure groups all condition types together which the SAP system is to automatically take into account during pricing for a business transaction (see the section "Define and assign pricing procedures").

Remember that you can only specify manually in a document those condition types which are contained in the pricing procedure.

You can change the outcome of pricing in the sales document manually. You can limit options for changing a condition type in this IMG step.

Recommendation

If you define your own condition types, the key should start with the letter Z since SAP reserves these letters for that purpose in the standard system.

Do not change the condition types which are contained in the standard SAP R/3 System.

Actions

1. Check to what extent you can use the condition types contained in the standard SAP R/3 System.

2. Create new condition types by copying a similar conditions type and changing it according to your requirements. One reason for creating a new condition type is you may require a calculation rule for a discount which is not available in the standard system.

Specify an alphanumeric key which can have up to 4 digits, and a textual description.

Specify an access sequence for the condition types. You do not need to specify an access sequence for header conditions.

3. Maintain the detail screen of the condition type.
You can also assign a reference condition type if the condition types you are working with are similar. Then you will only have to maintain condition records for the reference condition type.

In addition, you can define the upper and lower limits for the value of a condition at condition type level. This way, you limit the amounts or the scale values in the corresponding condition records.

Define Pricing Procedures

The pricing procedure defines the conditions permitted for a document and the sequence in which the system takes these conditions into account during pricing.

A standard pricing procedure is defined in the standard SAP system. It contains conditions most commonly used. These include material prices, discounts, and surcharges, such as freight, or tax.

SAP Recommendation

· Define your own pricing procedures which contain only those condition types which you use. Otherwise, the system makes un neccessary accesses to conditions.

· Do not change the pricing procedures contained in the standard SAP R/3 System.

Actions

1. Create new pricing procedures by copying a similar pricing procedure.

Specify a key with up to 6 characters and a description.

For a procedure, specify the condition types in the sequence of their usage.

Maintain the lines of the pricing procedure

2. Afterwards define the customer determination procedures for determining the procedure.

3. Define the document pricing procedures for determining the procedure.

4. Assign the procedure to the sales document types and billing types.

5. To determine the procedure, define the allowed combinations of:

Sales area
Customer pricing procedure
Document pricing procedure
Pricing procedure

Shipping:

The basis for shipping is delivery.

Delivery document controls the following in deliveries

Number range
Item no increment
Storage location rule
Route determination
Text determination
Delivery split
Gen. packing material / item
Order required

Delivery item category controls:

Check min delivery
Availability check
Relevant for picking
Storage location required
Determine storage location
Automatic batch determination
Text determination procedure

Billing:

Billing is the last phase in the SD process .Billing is the phase where the major integration of SD and FI Module happens.

Billing document has got the following structure:

Header

Item

Billing documents mainly control:

No. range
Posting block (Controls posting to accounting)
Relevant for rebate
Account determination procedure
Account determination recon account
Account determination pay.cards
Output determination procedure

Account Determination in SAP

Account determination in SAP-SD happens with the following rule

Sales Organization

Chart of Accounts

Account assignment group –Customer

Account assignment group-Material

Account Key

G/L account on which the postings has to happen.

Example ABAP Code to colour Selected row in ALV

noreply@blogger.com (Total SAP) — Mon, 07 Sep 2009 07:30:00 +0000

*&---------------------------------------------------------------------*
*& Report ZSACHIN_ALV_DEEP32

REPORT ZSACHIN_ALV_DEEP32.

TABLES: MARA.

TYPE-POOLS: SLIS.

DATA: BEGIN OF ITAB OCCURS 0,
MATNR TYPE MARA-MATNR,
ERSDA TYPE MARA-ERSDA,
ERNAM TYPE MARA-ERNAM,

* create a field of 4 char to fill the color
WA_COLOR(4) TYPE C,

END OF ITAB.

DATA: GT_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV,
WA_FIELDCAT TYPE SLIS_FIELDCAT_ALV.

* create a field symbol to add color for the selected row
FIELD-SYMBOLS: LIKE ITAB.

DATA: gd_layout type slis_layout_alv.

START-OF-SELECTION.

SELECT MATNR ERSDA ERNAM FROM MARA INTO TABLE ITAB UP TO 100 ROWS.

WA_FIELDCAT-SELTEXT_L = 'MATERIAL NUMBER'.
WA_FIELDCAT-COL_POS = '1'.
WA_FIELDCAT-TABNAME = 'MARA'.
WA_FIELDCAT-hotspot = 'X'.
WA_FIELDCAT-no_zero = 'X'.
WA_FIELDCAT-FIELDNAME = 'MATNR'.

APPEND WA_FIELDCAT TO GT_FIELDCAT.
CLEAR WA_FIELDCAT.

WA_FIELDCAT-SELTEXT_L = 'Created On'.
WA_FIELDCAT-COL_POS = '2'.
WA_FIELDCAT-TABNAME = 'MARA'.
WA_FIELDCAT-FIELDNAME = 'ERSDA'.
WA_FIELDCAT-emphasize = 'C110'.

APPEND WA_FIELDCAT TO GT_FIELDCAT.
CLEAR WA_FIELDCAT.

WA_FIELDCAT-SELTEXT_L = 'Name of Person'.
WA_FIELDCAT-COL_POS = '3'.
WA_FIELDCAT-TABNAME = 'MARA'.
WA_FIELDCAT-FIELDNAME = 'ERNAM'.
WA_FIELDCAT-just = 'R'.
*WA_FIELDCAT-emphasize = 'C600'.

APPEND WA_FIELDCAT TO GT_FIELDCAT.
CLEAR WA_FIELDCAT.

* loop through thetable to update the color forthe selected row
LOOP AT ITAB ASSIGNING .

IF SY-TABIX = '5'.
-WA_COLOR = 'C311'.
ENDIF.

ENDLOOP.

*PERFORM GET_EVENTS.

* Give the name field in which we have filled the color code
gd_layout-info_fieldname = 'WA_COLOR'.
gd_layout-zebra = 'X'.

*GD_LAYOUT-edit = 'X'. " this will make the alv editable
" and for each record make a box on left side
GD_LAYOUT-no_vline = 'X'.

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
* I_INTERFACE_CHECK = ' '
I_BYPASSING_BUFFER = 'X'
* I_BUFFER_ACTIVE = ' '
I_CALLBACK_PROGRAM = sy-repid
* I_CALLBACK_PF_STATUS_SET = 'ZSACHIN1111'
I_CALLBACK_USER_COMMAND = 'FRM_USR_COMMAND'
I_CALLBACK_TOP_OF_PAGE = 'TOP_OF_PAGE'
* I_CALLBACK_HTML_TOP_OF_PAGE = ' '
* I_CALLBACK_HTML_END_OF_LIST = ' '
* I_STRUCTURE_NAME = MARA etc
* I_BACKGROUND_ID = ' '
I_GRID_TITLE = 'TITLE OF THE GRID'
* I_GRID_SETTINGS =
IS_LAYOUT = GD_LAYOUT
IT_FIELDCAT = GT_FIELDCAT
* IT_EXCLUDING =
* IT_SPECIAL_GROUPS =
* IT_SORT =
* IT_FILTER =
* IS_SEL_HIDE =
* I_DEFAULT = 'X'
I_SAVE = 'A'
* IS_VARIANT = i_varient1
* IT_EVENTS =
* IT_EVENT_EXIT =
* IS_PRINT =
* IS_REPREP_ID =
* I_SCREEN_START_COLUMN = 0
* I_SCREEN_START_LINE = 0
* I_SCREEN_END_COLUMN = 0
* I_SCREEN_END_LINE = 0
* I_HTML_HEIGHT_TOP = 0
* I_HTML_HEIGHT_END = 0
* IT_ALV_GRAPHICS =
* IT_HYPERLINK =
* IT_ADD_FIELDCAT =
* IT_EXCEPT_QINFO =
* IR_SALV_FULLSCREEN_ADAPTER =
* IMPORTING
* E_EXIT_CAUSED_BY_CALLER =
* ES_EXIT_CAUSED_BY_USER =
TABLES
t_outtab = ITAB
EXCEPTIONS

PROGRAM_ERROR = 1
OTHERS = 2
.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

*FORM SAC_LAYOUT.

*ENDFORM.

FORM FRM_USR_COMMAND USING OK_CODE TYPE SY-UCOMM RS_SELFIELD TYPE SLIS_SELFIELD .

CASE OK_CODE.

WHEN 'PICK'.

READ TABLE ITAB INDEX RS_SELFIELD-TABINDEX.

PERFORM CALL_TRANS USING ITAB-MATNR.

ENDCASE.

ENDFORM.

FORM CALL_TRANS USING MATNR.

SET PARAMETER ID 'MAT' FIELD MATNR. "Global memory sap memory.

CALL TRANSACTION 'MM02' AND SKIP FIRST SCREEN.

ENDFORM.

form PFSTATUS.

*SET PF-STATUS 'ZSACHIN1111'.

ENDFORM.

FORM TOP_OF_PAGE.

WRITE: 'SACHIN THE BOND'.

ENDFORM.

export to excel function is not working

noreply@blogger.com (Total SAP) — Tue, 21 Apr 2009 04:43:00 +0000

i am having a problem using the export option that is available to export table data to an excel sheet.when i click the submit button, the ouput displays in the table and then when i click export i get an exception which say:...
java.lang.NullPointerException
at com.sap.ip.bi.alv.xml.ALVXMLCellCollector.collect(ALVXMLCellCollector.java:105)
at com.sap.ip.bi.alv.xml.ALVXMLDataRowCollector.collect(ALVXMLDataRowCollector.java:207)
at com.sap.ip.bi.alv.xml.ALVXMLDataTableCollector.collect(ALVXMLDataTableCollector.java:67)
at com.sap.ip.bi.alv.xml.ALVXMLTableCollector.collect(ALVXMLTableCollector.java:114)
at com.sap.ip.bi.alv.export.ALVExportXMLBase25.export(ALVExportXMLBase25.java:95)
... 87 more

and i dont get this error when i dont use "user data" connector ( a connector that contains the personal data of the user ) or when i dont click submit button to get the output.

can anyone slove this problem?

Can you tell me the procedure that you have followed..

plz elobarate your design time.

The problem is solved.It was due to a numeric field in the output of the table not due to USER DATA connector.This field is basically ´"COST" and it takes decimal values.So i just changed the value of this field to

=FLOAT(@cost) ( this converts the text string to a floating point number or you could use NVAL(@cost) even this would work )

the export function worked !!!!

Paymetric Tokenization Service

noreply@blogger.com (Total SAP) — Tue, 31 Mar 2009 06:32:00 +0000

Business Context

Paymetric's tokenization management server replaces credit card numbers in applications and databases in SAP with a token. These tokens act as surrogates for the cardholder data for use throughout your Enterprise. This allows you to remove the sensitive data without hampering your ability to serve repeat customers. Throughout this transparent process, credit card data is tokenized and routed through a single secure server, hosted online by Paymetric, ensuring no prohibited, unsecured credit card data resides in the database of your SAP systems. Paymetric's tokenization service dramatically reduces the cost and scope of achieving compliance with the Payment Card Industry Data Security Standards (PCI-DSS).

Technical Data

Implementation Platform	Paymetric's XiSecure 1.0
Services Type	A2X, synchronous

Process Components

Business Partner Data Management	The management of all the business partner master data of a company. This data contains the information needed to describe the rights and obligations of a business partner participating in various business processes, such as sales, purchasing, and accounting processes.

The following entities are part of this process component:

Business Objects

Payment Card	A card that can be presented by a cardholder to a vendor to make a cashless payment.

Service Interfaces

Payment Card Action In	The Payment Card Action In inbound service interface groups all operations that perform actions on the business object Payment Card Action or parts of it.

Service Operations

Payment Card Action In

Issue Payment Card Holder Authentication Token	Returns an authentication token for a given payment card.

docupedia - SAP's Help Library meets social media (1)

noreply@blogger.com (Total SAP) — Fri, 20 Mar 2009 16:37:00 +0000

Background:

The SAP NetWeaver Help Library or “doku” as we like to call it internally has been around as long as SAP software. It comes in many different flavors – from the SAP Library to Installation and Configuration Guides to Glossaries. Most of this documentation is produced by a diligent team of Information Developers around the world, and then goes through a thorough editing and production process before it reaches SAP customers and partners.

On the other hand we have SDN, that over time has accumulated an amazing pool of knowledge around SAP NetWeaver in form of blogs, forums, wikis, articles and more.

Currently our Help Library is not available to SDN, creating some interesting challenges for anyone looking for knowledge around SAP NetWeaver. We actually found some astonishing anecdotes from our users.

Often users have to go to two or three different places or even more to find answers to the questions they have. Some users keep “cheat sheets” of where all the answers are. Others find the documentation a good starting point but then need to find associated materials. Some users have assembled great materials that directly relate to our Library content.

On the other hand we have our Info Developers that have no indication how the materials they are producing are being received out there – what is good, what is missing, what should be changed. How is the product being used by our customers?

In my next installment I'll talk more about how docupediA will bring our product documentation to you - our community and what you can do with it.

Andrea Anderson is a Design Led Innovation coach for SAP NetWeaver PM.

Add to: del.icio.us | Digg | Reddit

Comment on this articleShare your experiences with the SAP Help library. How are you using it today?
Comment on this weblog
Showing messages 1 through 4 of 4.
Titles Only Main Topics Oldest First

*
Coments and collaboration 2 thumbs up
2008-07-31 09:56:53 Nigel James Business Card [Reply]

This is great project. Documentation that I can comment on, request, tag, etc is an excellent start. The next time I see There is no documentation for function group ... I will be thinking of this project.

Bring it on...
Nigel

*
Great stuff!
2008-07-25 23:31:39 Frank Koehntopp SAP Employee Business Card [Reply]

We have been talking about exactly this yesterday - what I'd love to have is help/notes with tags and RSS feeds, so I can create a feed (Yahoo Pipes for example) for a special product/version that has all the related information, in a river of news style.
That would be extremely helpful.

*
SAP gets (more) social -- right where we need it!
2008-07-25 16:46:20 Moya Watson SAP Employee Business Card [Reply]

Andrea -
excellent! as an ex-dokudeveloper (read in english: tech writer) at SAP, i would have loved to see my documentation "socialized" via wiki. all of us who have written tech docs know that it is the end-user who holds the ultimate keys to real knowledge of a product. we have one-million-plus golden keys on the SDN; i can't wait to see how this project progresses!
thanks,
-m

*
That's exactly what we need
2008-07-25 06:08:21 Michael Koegel SAP Employee Business Card [Reply]

Hi Andrea,
being heavily involved in projects on very early product versions and helping to round of the edges this is exactly what we need.
Being able to ammend the docu in the right places myself rather than having to find the right docu developer would speed up things alot.
On the other hand we'll still need the docu developers to make sure that the user created content is sound and well linked to background information and related topics.

Looking forward to the next installment.

Common Tables used by SAP MM

noreply@blogger.com (Total SAP) — Mon, 02 Mar 2009 10:03:00 +0000

Below are few important Common Tables used in Materials Management Modules:

EINA Purchasing Info Record- General Data
EINE Purchasing Info Record- Purchasing Organization Data
MAKT Material Descriptions
MARA General Material Data
MARC Plant Data for Material
MARD Storage Location Data for Material
MAST Material to BOM Link
MBEW Material Valuation
MKPF Header- Material Document
MSEG Document Segment- Material
MVER Material Consumption
MVKE Sales Data for materials
RKPF Document Header- Reservation
T023 Mat. groups
T024 Purchasing Groups
T156 Movement Type
T157H Help Texts for Movement Types
MOFF Lists what views have not been created
A501 Plant/Material
EBAN Purchase Requisition
EBKN Purchase Requisition Account Assignment
EKAB Release Documentation
EKBE History per Purchasing Document
EKET Scheduling Agreement Schedule Lines
EKKN Account Assignment in Purchasing Document
EKKO Purchasing Document Header
EKPO Purchasing Document Item
IKPF Header- Physical Inventory Document
ISEG Physical Inventory Document Items
LFA1 Vendor Master (General section)
LFB1 Vendor Master (Company Code)
NRIV Number range intervals
RESB Reservation/dependent requirements
T161T Texts for Purchasing Document Types

SAP MM Tips by : Bahadur

Following are the list of Important MM tables. Please check if its useful.

Inventory Management:
|-------------------------+--------+-----------------------------------------|
| | Table | Description |
|-------------------------+--------+-----------------------------------------|
| Material | MSEG | Material document / transaction details |
| Document/Movements | MKPF | Material document header information |
|-------------------------+--------+-----------------------------------------|
| Material Stock Balances | MARD | Material stock |
| | MBEW | Material stock with valuation |
|-------------------------+--------+-----------------------------------------|
| Sales Order Stock | MSKA | Stock balance with associated sales |
| | | order data |
|-------------------------+--------+-----------------------------------------|
| Stock Transport | EKUB | Index for Stock Transport Orders for |
| | MDUB | Material |
| | | Reading View of Stock Transport Ord. for|
| | | Release Ord. |
|-------------------------+--------+-----------------------------------------|
| Special Stocks | MKOL | Consignment, material provided to |
| | | vendor, etc. |
|-------------------------+--------+-----------------------------------------|

Material Master Data:
|-------------------------+---------+--------------------------------------|
| |Table | Description |
|-------------------------+---------+--------------------------------------|
| Materials | MARA | General Data, material type, group, |
| | | configurable & batch ind. |
| | MAKT | Short Texts, descriptions |
| | MARM | Conversion Factors |
| | MVKE | Sales Org, distribution channel |
| | MLAN | Sales data, tax indicator, tax |
| | MARC | classification |
| | MBEW | Plant Planning Data |
| | MLGN | Valuation Data |
| | MLGT | Warehouse Management Inventory Data |
| | MVER | Warehouse Management Storage Type |
| | MAPR | Data |
| | MARD | Consumption Data |
| | MCHA | Pointer for Forecast Data |
| | MCHB | Storage location data with stock |
| | | balances |
| | | Batches |
| | | Batch Stocks |
|-------------------------+---------+--------------------------------------|

Configure Goods/Invoice Receipts for PO in SAP

noreply@blogger.com (Total SAP) — Tue, 17 Feb 2009 03:46:00 +0000

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
o Debit 12345 Inventory 12
o Credit 67890 GR/IR 12
o New Moving Average Price = ( GR value + Total value ) / ( GR quantity + Total stock )

Invoice Recipts for Purchase Order - MR01

* Accounting Document Posting created
o Debit 67890 GR/IR 12
o Debit 12345 Inventory 3
o Credit 45678 Vendor 15
o 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
o Debit 12345 Inventory 10
o Debit 23456 Price Variance 2
o Credit 67890 GR/IR 12
o No change in Standard Price

Invoice Recipts for Purchase Order - MR01

* Accounting Document Posting created
o Debit 67890 GR/IR 12
o Debit 23456 Price Variance 3
o Credit 45678 Vendor 15
o 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

List of SAP MM Transaction codes

noreply@blogger.com (Total SAP) — Fri, 13 Feb 2009 10:54:00 +0000

All transaction are stored in table TSTC. Transaction for MM module start with M. IH09 - Display Material
MM01 - Create Material
MM02 - Change Material
MM03 - Display Material
MM50 - List Extendable Materials
MMBE - Stock Overview
MMI1 - Create Operating Supplies
MMN1 - Create Non-Stock Material
MMS1 - Create Service
MMU1 - Create Non-Valuated Material

ME51N - Create Purchase Requisition
ME52N - Change Purchase Requisition
ME53N - Display Purchase Requisition
ME5A - Purchase Requisitions: List Display
ME5J - Purchase Requisitions for Project
ME5K - Requisitions by Account Assignment
MELB - Purch. Transactions by Tracking No.

ME56 - Assign Source to Purch. Requisition
ME57 - Assign and Process Requisitions
ME58 - Ordering: Assigned Requisitions
ME59 - Automatic Generation of POs
ME54 - Release Purchase Requisition
ME55 - Collective Release of Purchase Reqs.
ME5F - Release Reminder: Purch. Requisition

MB21 - Create Reservation
MB22 - Change Reservation
MB23 - Display Reservation
MB24 - Reservations by Material
MB25 - Reservations by Account Assignment

MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents

MB21 - Create Reservation
MB22 - Change Reservation
MB23 - Display Reservation
MB24 - Reservations by Material
MB25 - Reservations by Account Assignment

MBRL - Return Delivery per Mat. Document
MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents

MB1B - Transfer Posting

MIBC - ABC Analysis for Cycle Counting

MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock

MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock

MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock

MI21 - Print physical inventory document

MI04 - Enter Inventory Count with Document
MI05 - Change Inventory Count
MI06 - Display Inventory Count
MI09 - Enter Inventory Count w/o Document
MI34 - Batch Input: Enter Count
MI35 - Batch Input: Post Zero Stock Balance
MI38 - Batch Input: Count and Differences
MI39 - Batch Input: Document and Count
MI40 - Batch Input: Doc., Count and Diff.

MI08 - Create List of Differences with Doc.
MI10 - Create List of Differences w/o Doc.
MI20 - Print List of Differences

MI11 - Physical Inventory Document Recount

MI07 - Process List of Differences
MI37 - Batch Input: Post Differences

CT01 - Create Characteristic
CT02 - Change Characteristic
CT03 - Display Characteristic

CL01 - Create Class
CL02 - Classes
CL03 - Display Class
CL04 - Delete Class
CL2B - Class Types

Difference Between Client , Purchasing Org , Plant , Company code

noreply@blogger.com (Total SAP) — Sun, 08 Feb 2009 10:28:00 +0000

What is the technical difference between Client , Purchasing Org , Plant , Company code?

Client : Unit within SAP system, self-contained, separate master data with independent set of tables. It represent corporate group.

Company Code : Smallest organisational unit of external account for which a complete, self-contained bookkeeping system can be replicated. eg, company within a corporate group.

Plant : An organisational unit within logistics, subdivides an enterprise from the viewpoint of production, procurement and materials planning.

Purchasing Org : Organisation within logistics which subdivides an enterprise according to purchasing requirements.

The procurement business process uses this organisational structure:

Client--->Company Code--->Plant--->Storage Location--->Purchasing Org/ Purchasing group

The standard procedure for creating a new plant in SAP:

SPRO -> Enterprise Structure -> Logistics - General -> Define, copy, delete, check plant

Materials Management Tables

noreply@blogger.com (Total SAP) — Tue, 03 Feb 2009 07:08:00 +0000

MBEW Material Valuation

MKPF Header- Material Document

MSEG Document Segment- Material

MVER Material Consumption

MVKE Sales Data for materials

EINA Purchasing Info Record- General Data

EINE Purchasing Info Record- Purchasing
Organization Data

MAKT Material Descriptions

MARA General Material Data

MARC Plant Data for Material

MARD Storage Location Data for Material

MAST Material to BOM Link

RKPF Document Header- Reservation

T023 Mat. groups

T024 Purchasing Groups

T156 Movement Type

Reduce costs and simplify the deployment of reporting with your applications

noreply@blogger.com (Total SAP) — Sun, 01 Feb 2009 03:58:00 +0000

In this web seminar, you will learn how Crystal Reports 2008 Developer Advantage complements the Crystal Reports family of offerings for developers to make application deployment outside the firewall more simple and cost effective.

In this session, you will learn:

How application developers can leverage the integrated Crystal Reports family of offerings
All about Crystal Reports 2008 Developer Advantage, a new runtime license for Crystal Reports
How McManus Consulting plans to derive value from implementing this new licensing option

For more information about Crystal Reports solutions, visit our website at: http://www.sap.com/solutions/sapbusinessobjects/sme/reporting/index.epx

Register for the Event

Wednesday, February 11, 2009, 10:00 am (Pacific Standard Time)

Access Information:

Event Number: 598 162 779

Event Password: 021109

Audio Information:

U.S. and Canada Attendee Phone: (866) 854-3172

Attendee International Phone: (706) 634-0746

Conference ID: 79448368

Additional International Toll-Free numbers:

ITFS Number	Country
08006661537	Argentina
1800005989	Australia
800295828	Austria
18775232207	Bahamas
8800114	Belarus
8800114	Belarus
0-80073264	Belgium
800100103	Bolivia
0-8008916210	Brazil
00-8001100180	Bulgaria
12300206168	Chile
0-18007001835	Columbia
0-8000130990	Costa Rica
0-800222610	Croatia
80094887	Cyprus
800142869	CZECH (REP)
80880365	Denmark
18887512305	Dominican Rep
3640083	Egypt
0800111089	Finland
0-800909322	France
0-8001800658	Germany
00-80018092021815	Greece
800966253	Hong Kong
06-80017646	Hungary
8008057	Iceland
8001006243	India
001-8030152021818	Indonesia
1800552552	Ireland
1809315362	Israel
800786829	Italy
18002050326	Jamaica
531160669	Japan
0-800220115	Kenya
8002173	Latvia
880030141	Lithuania
80024807	Luxembourg
1800803537	Malaysia
0-018664037413	Mexico
80093321	Monaco
0-8000232838	Netherlands
0800450120	New Zealand
18000551	Nicaragua
1-08007130924	North China
80018522	Norway
0-018002018157	Panama
80052957	Peru
0-08001113655	Poland
800815187	Portugal
0-218005030	Romania
8.108E+13	Russia
8001011512	Singapore
0-800042133	Slovakia \ Slovak Republic
0-800980254	South Africa
1-08001300748	South China
00-308131620	South Korea
900987034	Spain
0-20798505	Sweden
0800891753	Switzerland
0-0801148720	Taiwan
0-01800132017883	Thailand
1802021609	Trinidad & Tobago
8100180	Ukraine
0-8000288438	United Kingdom
40190122	Uruguay
0-8001002762	Venezuela

What data does the MM Information Record contain?

noreply@blogger.com (Total SAP) — Fri, 16 Jan 2009 11:24:00 +0000

The Information Records has data on Units of Measure, Vendor price changes after a certain level, what materials have been procured by a specific vendor, price and conditions for relevant Purchase Organization, Tolerance limits for over/under delivery, Vendor evaluation data, planned delivery time, and availability time the vendor can supply the material.

SOA Helps Hire a Hero Give Returning Veterans a Fighting Chance to Find Work

noreply@blogger.com (Total SAP) — Sun, 04 Jan 2009 06:14:00 +0000

Tue, July 29, 2008 — CIO — Hire a Hero is a small company with a big mission. It aims to help service members leaving the military make a smooth transition to civilian life by connecting them with potential employers using Web 2.0 social networking tools. After some fits and starts, the company found that a solution built on service-oriented architecture (SOA) enabled it to achieve its goals at a low cost. What's more, because of its nonprofit status, in some cases, the vendors donated the services for free.

When Hire a Hero started a couple of years ago, it had visions of building its own system, but after burning through a couple of hundred grand, Brac Selph, executive director, says he knew that if his company was going to survive, it needed to find a new plan that involved working with existing services, rather than trying to build its own solution.
Developing a New Strategy

The new approach began to develop last January when Selph realized he needed to find a less-expensive technology strategy. Throughout the winter and spring of this year, he cobbled together a solution that involved three companies: two software-as-a-service (SaaS) vendors and a data integration tool to act as a bridge between the two systems.

The first piece was Salesforce.com, a customer relationship management tool built on the SaaS model. Hire a Hero had been using Salesforce with its original homegrown system to organize information about employees and potential employers. Salesforce also helped automate many processes by building in business logic normally used for a sales channel. For instance, if members didn't send a résumé, they got an automatic reminder e-mail message. If they hadn't set up an interview, they got a message about connecting them with someone who could help. In addition, Salesforce donated the service at no cost to Hire a Hero.

The next piece was a front-end Web tool, which would enable employers and employees to enter information about themselves into the system and provide social networking functionality. Selph found a company called YourMembership.com, which is also a SaaS vendor. He says that he couldn't believe he could find a tool with 80 percent of the functionality he wanted for just $500 a month. It also enabled him to get rid of expensive technical staff, saving his company $200,000 a year.

The final and most important piece was finding data integration company XAware to provide a way to get data from YourMembership into Salesforce.
Bringing the Data Together

Selph admits he knew little or nothing about SOA when he started down this road. He only knew he wanted to take advantage of services to save his company money, that he had two systems—and he wanted them to communicate with one another. "I've got to be real frank; I wasn't even aware of the term [SOA], but it certainly fits really well with what we are doing, particularly the idea of connecting various systems to accomplish what we want to accomplish," Selph says.

Soon after going live with YourMembership.com, he ran into problems moving data into Salesforce. "We realized [quickly] that we were doing everything by hand between YourMembership.com and Salesforce.com. It may not sound like much, but it took about an hour a day to download files from YourMembership and upload them to Salesforce," Selph says. In addition, he says, something inevitably went wrong with the transfer, such as incomplete data, wrong dates and records duplication. "There was just a huge potential for error," Selph says. As frustration with the process grew, he began looking for a solution to automate the data exchange.

With only a vague idea of what he wanted to do, Selph began exploring the Salesforce.com App Exchange, looking for a data integration solution. What he found was XAware and a couple of other vendors, but it quickly became apparent that XAware fitted both technologically and culturally. XAware offered an open-source solution that would solve Hire a Hero's technology problem. With a fellow ex-Marine as CEO, XAware also had what Selph calls "an affinity for people in the military." And when he asked about a special nonprofit price, he was pleased to find they would provide the entire solution for free.

Program to Mass Select Purchase Order and print history

noreply@blogger.com (Total SAP) — Wed, 10 Dec 2008 06:31:00 +0000

4.6x

* Mass check PO history instead of doing it one at time via transaction ME22N.

report ZPOHISTORY line-size 132 no standard page heading.

tables : ekko,
ekpo,
ekbe,
mseg,
mkpf,
bkpf,
rbkp,
lfa1.

select-options: xebeln for ekko-ebeln memory id bes.

data: wttlqty like ekbe-menge,
wttlamt like ekbe-dmbtr,
wgrqty like ekbe-menge,
wgramt like ekbe-dmbtr,
wirqty like ekbe-menge,
wiramt like ekbe-dmbtr.

data: wtxt1(4),
wrefno like mkpf-xblnr,
wbktxt like mkpf-bktxt.

data: begin of awkey,
belnr like rbkp-belnr,
gjahr like rbkp-gjahr,
end of awkey.

field-groups: header.

insert
ekko-ebeln
ekko-lifnr
ekbe-belnr
ekbe-gjahr
ekbe-ebelp
ekbe-bwart
ekbe-budat
ekbe-menge
ekbe-dmbtr
ekbe-waers
ekbe-bewtp
ekpo-matnr
ekpo-meins
ekpo-txz01
* bkpf-belnr
wbktxt
wrefno
wtxt1
into header.

select * from ekko where ebeln in xebeln.
select * from ekpo where ebeln = ekko-ebeln.
select * from ekbe where ebeln = ekko-ebeln and
ebelp = ekpo-ebelp and
( bewtp = 'R' or
bewtp = 'E' or
bewtp = 'Q' ).
if ekbe-bewtp = 'E'.
wtxt1 = 'GR'.
select single * from mkpf where mblnr = ekbe-belnr and
mjahr = ekbe-gjahr.
if sy-subrc = 0.
wrefno = mkpf-xblnr.
wbktxt = mkpf-bktxt.
endif.
else.
if ekbe-bewtp = 'R'.
select single * from bkpf where BUKRS = '0001' and
BELNR = ekbe-belnr and
gjahr = ekbe-gjahr.
wtxt1 = 'IR'.
wrefno = bkpf-xblnr.
wbktxt = bkpf-bktxt.
else.
select single * from rbkp where belnr = ekbe-belnr and
gjahr = ekbe-gjahr.
wtxt1 = 'IR-L'.
wrefno = rbkp-xblnr.
wbktxt = rbkp-bktxt.
endif.
endif.
if ekbe-shkzg = 'H'.
ekbe-dmbtr = ekbe-dmbtr * -1.
ekbe-menge = ekbe-menge * -1.
endif.
extract header.
clear: wrefno, wbktxt.
endselect.
endselect.
endselect.

sort by ekko-ebeln ekbe-ebelp ekbe-bewtp ekbe-belnr.

loop.
at new ekko-ebeln.
perform po_head.
endat.
at new ekbe-ebelp.
format color col_group inverse.
write:/ '|', ekpo-matnr, ekpo-txz01,
130 '|'.
format inverse off.
endat.
format color col_normal.
shift ekbe-ebelp.
write:/ '|' no-gap,
wtxt1 no-gap, '|' no-gap,
ekbe-belnr no-gap, '|' no-gap,
(4) ekbe-ebelp no-gap, '|' no-gap,
ekbe-bwart no-gap, '|' no-gap,
ekbe-budat dd/mm/yy no-gap, '|' no-gap,
(15) ekbe-menge , ekpo-meins no-gap, '|' no-gap,
(15) ekbe-dmbtr,
* (3) ekbe-waers no-gap, '|' no-gap,
'SGD' no-gap, '|' no-gap,
* bkpf-belnr, '|' no-gap,
wrefno no-gap, '|' no-gap,
wbktxt no-gap, '|' no-gap.
hide: ekbe-belnr, ekbe-gjahr, ekbe-bewtp.
wttlqty = wttlqty + ekbe-menge.
wttlamt = wttlamt + ekbe-dmbtr.
at end of ekbe-bewtp.
format color col_total.
if wtxt1 = 'GR'.
write:/ '|' ,
'Item', ekbe-ebelp, 'Goods Receipts'.
* 25 '|'.
* 130 '|'.
wgrqty = wgrqty + wttlqty.
wgramt = wgramt + wttlamt.
elseif wtxt1 = 'IR' or
wtxt1 = 'IR-L'.
write:/ '|' ,
'Item', ekbe-ebelp, 'Invoices'.
wirqty = wirqty + wttlqty.
wiramt = wiramt + wttlamt.
endif.
write: 35 '|' no-gap,
(15) wttlqty,
' |' no-gap,
(15) wttlamt,
' |' no-gap,
130 '|'.
clear: wttlqty, wttlamt.
endat.
at end of ekbe-ebelp.
uline at /1(130).
endat.
at end of ekko-ebeln.
format color col_positive.
write:/ '|' ,
'Total Goods Receipts',
35 '|' no-gap,
(15) wgrqty,
' |' no-gap,
(15) wgramt,
' |' no-gap,
130 '|'.
write:/ '|' ,
'Total Invoices',
35 '|' no-gap,
(15) wirqty,
' |' no-gap,
(15) wiramt,
' |' no-gap,
130 '|'.
clear: wirqty, wgrqty, wiramt, wgramt.
uline at /1(130).
endat.
endloop.

at line-selection.

if sy-lisel+1(2) = 'GR'.
*if ekbe-bewtp = 'E'.
set parameter id: 'MBN' field ekbe-belnr,
'MJA' field ekbe-gjahr.
call transaction 'MB03'.
elseif sy-lisel+1(4) = 'IR-L'.
set parameter id: 'RBN' field rbkp-belnr,
'GJR' field ekbe-gjahr.
call transaction 'MIR4' and skip first screen.
elseif sy-lisel+1(2) = 'IR'.
* ekbe-bewtp = 'R'.
set parameter id: 'BLN' field ekbe-belnr,
'BUK' field '0001',
'GJR' field ekbe-gjahr.
call transaction 'FB03' and skip first screen.
endif.

*---------------------------------------------------------------------*
* FORM PO_HEAD *
*---------------------------------------------------------------------*
* ........ *
*---------------------------------------------------------------------*
form po_head.
skip.
uline at 1(130).
format color col_key.
select single * from lfa1 where lifnr = ekko-lifnr.
write:/ '|', ekko-ebeln, lfa1-name1, '(', ekko-lifnr, ')',
130 '|'.
uline at /1(130).
format color col_heading.
write:/ '|' no-gap,
'Cat ' no-gap, '|' no-gap,
'Doc No ' no-gap, '|' no-gap,
'Itm', '|' no-gap,
'Mvt' no-gap, '|' no-gap,
'Pstg.dt', '|' no-gap,
' Qty in OUn', '|' no-gap,
'Value in local curr' no-gap, '|' no-gap,
* 'Acc Doc ', '|' no-gap,
'Ref No ', '|' no-gap,
'Doc Text ', '|' no-gap.
uline at /1(130).
endform.

Program to Mass Select Purchase Order and print history

noreply@blogger.com (Total SAP) — Wed, 10 Dec 2008 06:31:00 +0000

4.6x

* Mass check PO history instead of doing it one at time via transaction ME22N.

report ZPOHISTORY line-size 132 no standard page heading.

tables : ekko,
ekpo,
ekbe,
mseg,
mkpf,
bkpf,
rbkp,
lfa1.

select-options: xebeln for ekko-ebeln memory id bes.

data: wttlqty like ekbe-menge,
wttlamt like ekbe-dmbtr,
wgrqty like ekbe-menge,
wgramt like ekbe-dmbtr,
wirqty like ekbe-menge,
wiramt like ekbe-dmbtr.

data: wtxt1(4),
wrefno like mkpf-xblnr,
wbktxt like mkpf-bktxt.

data: begin of awkey,
belnr like rbkp-belnr,
gjahr like rbkp-gjahr,
end of awkey.

field-groups: header.

sort by ekko-ebeln ekbe-ebelp ekbe-bewtp ekbe-belnr.

at line-selection.

Write BDC Program to Update Source List by Material Group - MM01

noreply@blogger.com (Total SAP) — Wed, 10 Dec 2008 06:31:00 +0000

The SCREEN SEQUENCE FOLLOWS

4.6x.

***********************************************************************
* Update Source List by Material Group
* Blocking / Unblocking the Vendor
* The Vendor code is retrieve from the Purchasing Info Record
***********************************************************************

REPORT ZSOURCE.
TABLES: EORD,
EINA,
MARC.

* Batch Input Name
PARAMETERS P-BTCHSN(12) DEFAULT 'ME01'.
* Vendor Code
PARAMETERS P-LIFNR LIKE LFA1-LIFNR DEFAULT 'XXXXX'.
* Material Group
PARAMETERS P-MATKL LIKE MARA-MATKL DEFAULT 'XXXXXXX'.
* Plants
PARAMETERS P-WERKS LIKE EORD-WERKS DEFAULT 'XX'.
* Tick Block/Untick Unblock
PARAMETERS P-NOTKZ LIKE EORD-NOTKZ DEFAULT 'X'.
* Auto / Manual run the Batch Input Program
PARAMETERS P-RUN AS CHECKBOX DEFAULT 'X'.

* INTERNAL TABLE FOR DATA
DATA: BEGIN OF ULTAB OCCURS 50,
MATNR LIKE EORD-MATNR, "Material No.
WERKS LIKE EORD-WERKS, "Plants
ZEORD LIKE EORD-ZEORD, "NO
LIFNR LIKE EINA-LIFNR, "Vendor Code
END OF ULTAB.

* INTERNAL TABLE FOR BATCH INPUT DATA
DATA: BEGIN OF IPUTTAB OCCURS 50.
INCLUDE STRUCTURE BDCDATA.
DATA: END OF IPUTTAB.

* INTERNAL TABLE FOR BATCH INPUT ERROR MESSAGE.
DATA: BEGIN OF MESSTAB OCCURS 50.
INCLUDE STRUCTURE BDCMSGCOLL.
DATA: END OF MESSTAB.

DATA: C_TAXKM LIKE MG03STEUER-TAXKM VALUE '1',
W-LINE-NO TYPE I.

REFRESH ULTAB.
SELECT * FROM EINA WHERE LIFNR = P-LIFNR
AND LOEKZ = SPACE.
SELECT SINGLE * FROM MARC WHERE MATNR = EINA-MATNR
AND WERKS = P-WERKS.
CHECK MARC-LVORM = SPACE.
CLEAR ULTAB.
SELECT * FROM EORD WHERE MATNR = EINA-MATNR
AND WERKS = P-WERKS
AND LIFNR = P-LIFNR.
ULTAB-MATNR = EORD-MATNR.
ULTAB-WERKS = EORD-WERKS.
ULTAB-ZEORD = EORD-ZEORD.
ULTAB-LIFNR = EORD-LIFNR.
APPEND ULTAB.
ENDSELECT.

IF SY-SUBRC = 4.
ULTAB-MATNR = EINA-MATNR.
ULTAB-WERKS = P-WERKS.
ULTAB-ZEORD = ''.
ULTAB-LIFNR = EINA-LIFNR.
APPEND ULTAB.
ENDIF.
ENDSELECT.

* CHECK WHETHER TABLE IS EMPTY
IF ULTAB[] is initial.
WRITE: / 'TABLE EMPTY'.
ENDIF.

* Create Batch session
PERFORM CRE-BATCH-SESS.

** LOOP TABLE TO CREATE SCREEN INPUT
SORT.
LOOP AT ULTAB.
REFRESH IPUTTAB.
PERFORM SCREEN1.
PERFORM SCREEN2.
PERFORM PRN_ULTAB.
PERFORM CLOSE-SESS.
ENDLOOP.

CALL FUNCTION 'BDC_CLOSE_GROUP'.

* END OF MAIN PROGRAM

FORM SCREEN1.
* SCREEN #1: INITAL SCREEN FOR MAINTAINING SOURCE LIST
CLEAR IPUTTAB.
IPUTTAB-PROGRAM = 'SAPLMEOR'.
IPUTTAB-DYNPRO = '200'.
IPUTTAB-DYNBEGIN = 'X'.
APPEND IPUTTAB.

* Source List : Material No.
CLEAR IPUTTAB.
IPUTTAB-FNAM = 'EORD-MATNR'.
IPUTTAB-FVAL = ULTAB-MATNR.
APPEND IPUTTAB.

* Source List : Plants.
CLEAR IPUTTAB.
IPUTTAB-FNAM = 'EORD-WERKS'.
IPUTTAB-FVAL = ULTAB-WERKS.
APPEND IPUTTAB.

ENDFORM.
***********************************************************************
* FORM : SCREEN1 *
***********************************************************************
FORM SCREEN2.
* Modify screen for SOURCE LIST
CLEAR IPUTTAB.
IPUTTAB-PROGRAM = 'SAPLMEOR'.
IPUTTAB-DYNPRO = '205'.
IPUTTAB-DYNBEGIN = 'X'.
APPEND IPUTTAB.

CLEAR IPUTTAB.
IPUTTAB-FNAM = 'EORD-VDATU(1)'.
IPUTTAB-FVAL = '01.01.2001'.
APPEND IPUTTAB.

CLEAR IPUTTAB.
IPUTTAB-FNAM = 'EORD-BDATU(1)'.
IPUTTAB-FVAL = '31.12.9999'.
APPEND IPUTTAB.

CLEAR IPUTTAB.
IPUTTAB-FNAM = 'EORD-LIFNR(1)'.
IPUTTAB-FVAL = P-LIFNR.
APPEND IPUTTAB.

CLEAR IPUTTAB.
IPUTTAB-FNAM = 'EORD-EKORG(1)'.
IPUTTAB-FVAL = 'ALL'.
APPEND IPUTTAB.

CLEAR IPUTTAB.
IPUTTAB-FNAM = 'EORD-NOTKZ(1)'.
IPUTTAB-FVAL = P-NOTKZ.
APPEND IPUTTAB.

CLEAR IPUTTAB.
IPUTTAB-FNAM = 'EORD-AUTET(1)'.
IPUTTAB-FVAL = '1'.
APPEND IPUTTAB.

* Specify that we are now done with this screen (Save it with F11)
CLEAR IPUTTAB.
IPUTTAB-FNAM = 'BDC_OKCODE'.
IPUTTAB-FVAL = '/11'.
APPEND IPUTTAB.
ENDFORM.

***********************************************************************
* FORM : CLOSE-SESS *
* DESCRIPTION : CLOSE THE SESSION *
***********************************************************************
FORM CLOSE-SESS.
* closing the session.
IF P-RUN = 'X'.
* Auto run the Batch Input Program
CALL TRANSACTION 'ME01'
USING IPUTTAB
MODE 'E'
UPDATE 'S'
MESSAGES INTO MESSTAB.
ELSE.
* Maual run the Batch Input Program
CALL FUNCTION 'BDC_INSERT'
EXPORTING
TCODE = 'ME01'
TABLES
DYNPROTAB = IPUTTAB.
ENDIF.

ENDFORM.

***********************************************************************
* FORM : PRN-ULTAB *
* DESCRIPTION : PRINT OK TABLE *
***********************************************************************
FORM PRN_ULTAB.
WRITE: / ULTAB-MATNR, ULTAB-WERKS, ULTAB-ZEORD, ULTAB-LIFNR.
W-LINE-NO = W-LINE-NO + 1.
WRITE: ' RECORD# ', W-LINE-NO.
ENDFORM.

***********************************************************************
* FORM : CRE-BATCH-SESS *
* DESCRIPTION : CREATE BATCH SESSION *
***********************************************************************
FORM CRE-BATCH-SESS.
** Create BTCI session **
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
CLIENT = SY-MANDT
GROUP = P-BTCHSN
USER = SY-UNAME
KEEP = 'X'.
ENDFORM.

How to use e-mail with ERS Invoice verifcation

noreply@blogger.com (Total SAP) — Wed, 10 Dec 2008 06:30:00 +0000

Can anyone help me with information on how to use e-mail for sending ERS invoices. I want to sent the ERS invoices to a vendor how performed a service.

The first problem I encounter is that in the Vendor masterdata I can't fill in an e-mailaddress. And therefor I can't assign it to a partnerroll.

Is it also possible to use a distributionlist? That the ERS invoice is sent to that list and from there to email-recipents?

Georg Herder

You can store an email address at the vendor master (address). The fields must have been set to inactive in the configuration.

Please review the settings in the IMG.

Then go to Mat.Management/Logisitc Invoice Verification/Message Determination (IMG)

Here you can maintain the necessary message types ( I used the SAP standard ERS, copied to ZERS),
added Mail title "Automatic Invoice Verification &RBKP-BELNR&",
added Processing routine "5" External Send with program RM08NAST,
form-routine ENTRY_ERS, form MR_PRINT (or whatever copy you like to use),
in partner functions addedd medium "5" (now I have print, fax and email).

In detail of ZERS: Access sequence 0004 etc (all from output type ERS), Replacement of text...program RM08NAST,
Form routine MAILTEXT_REPLACE (to get the doc number into the email title),
Deflt values: "4" (immediate), Medium "5",
Partner function VN (you can use PI if required),
Communication strategy "ANZ" for fax and email, Timing 1 and 4 allowed (1 for RSNAST00, variant for "MR", "ZERS")

Next: Maintain Message Schema: MR0004 ERS Procedure (MRRL)(standard),
step 10 ERS6 (EDI), 20 ZERS (email/fax),
30 ERS (print). This schema is hardcoded!

Then "Maintain Conditions" ( or trans. MRM1, MRM2, MRM3), create the necessary output condition records
for e.g. ZERS for company code with medium "5" and timing "4" or per vendor...depends what you need

((Check what communication strategy is defined in your system)).

Marc

PS: had some trouble setting this up because the output type ERS and scheam MR0004 were only in client 000.
Had to copy the missing entries from 000 by table. ERS: TNATI has language "" which forces trouble when
you use it directly. I adjusted via SE16N (okcode &sap_edit) and transport manually. Also T683S was creating
a dump with SM31, used my own util-prog to copy from 000, transport manually.

Sending mail directly from SAP via Microsoft Exchange

noreply@blogger.com (Total SAP) — Wed, 10 Dec 2008 06:30:00 +0000

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

Send SAP Purchase Order with Microsoft Outlook

noreply@blogger.com (Total SAP) — Wed, 10 Dec 2008 06:29:00 +0000

This is how it work:-

First you send the text converted Purchase Order to your SAPoffice

Sample ABAP program for sending mail 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 extention ALI. Use the Windows Explorer to default open with the Windows Notepad.

Send Purchase Order via Output Determination

noreply@blogger.com (Total SAP) — Wed, 10 Dec 2008 06:29:00 +0000

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.

Sending P.O. By Mail To Vendor

noreply@blogger.com (Total SAP) — Wed, 10 Dec 2008 06:28:00 +0000

Is there any standard programm for sending P.O.'s by e-mail to vendor's email-id?

You need to do some configuration for this.

- Goto NACE .
- Select EF and click on OUTPUT TYPES.
- Then select Output Type NEU and click on processing routines .
- In that you have to add a new entry - medium 5 .
- Then you need to assign a program, form routine and form.
- You can use the standard program i.e. SAPFM06P, FORM routine is always ENTRY_NEU and standard MEDRUCK.
- Then in PARTNER FUNCTION you need to add a new entry : medium - 5 and function - VN .
- For subject of the mail goto Mail Title and Texts. In title give PO No. &EKKO-EBELN& .
- Under General data -> Replacement of text symbols give programm as SAPMM06E and Form Routine as
TEXT_SYMBOL_REPLACE .
- Now the subject will be PO No. 1800004202.
- You need to maintain your email id in tcode SU01 and also the vendor's email id.
- Now while creating a new purchase order , change the medium to External Send .
- Then goto Communication Method and select CS01 . ALSO make sure that the Cover Page Text has value PO No. &EKKO-EBELN& .
- Goto tcode ME9F .
- Execute.
- Select the checkbox and click on Output Message.
- You will get a message MAII 00000000000001 generated .

If the BASIS guys have made the necessary configuration for sending mail then the mail will go .

You can see the status in tcode SOST.

If you want to use a z-programm and z-form then you need add the functions used in standard programm SAPFM06P for generating mail in your z-programm.

Unable To Create PO Due To Language Error

noreply@blogger.com (Total SAP) — Wed, 10 Dec 2008 06:27:00 +0000

PO Error No short text maintained in language ES - Short text in MM01

Question: I have a short text maintained in Material master in EN. The vendor master has a language set as ES( Spanish)

I logged in EN

When I try to create a PO i get a error "No short text maintained in language ES (please re-maintain material 106)" error number is ME095.

If I change the vendor lang to EN & maintain the ES lang in Material master, I am overcoming the error.

Can any one throw light on the importance of these texts & their effects.Vendor language is responsible for Po Prints I suppose & entry & display of text

Answer:
Basically, you need a communication strategy.
- What languages will you use to communicate to your vendor.
- Do not think theoretical, do it like it is done in real life.
- If you talk to your vendor in Spain, what language do you use?
- If you use English then put EN as communication langauge in your vendor master.
- You need to have material descriptions and many customizing settings available in the desired communication languages.

We usually use the local language for local vendors and English for all foreign vendors. If we have plants e.g. in Germany and Spain, then the spanish plants uses spanish for his local vendors and the german plant uses german language for the local vendors in Germany.

Both are using english for their foreign vendors. Shared vendors will have english too, as a german buyer is not able to talk in spanish or an spanish buyer is not able to talk in german language. Hence they would not know if it is accurate what will show up on a PO they create. They both can only validate the accuracy in a english written text.

Vendor language is responsible for PO Prints and I suppose also the entry and display of text. The language that SAP will be taken is from the Vendor language (Communication section) if I am not mistaken and this is the standard functionality of SAP. Of course, you can be able to manually change the language directly in the PO.

Item Wise Display of Invoice Amt to be Paid to Vendor

noreply@blogger.com (Total SAP) — Wed, 10 Dec 2008 06:27:00 +0000

I have a Reqt wherein I should be able to know line itemwise the Materials Received(GR), Invoice Price and Qty Raised, Invoice to be Paid so that pending Qty and Amt can be calculated.

I will explain the scenario in Detail----

Say a PO has 3 Line Items A,B,C of 10 Quantities each has been ordered to a vendor.

Out of which for Item A---------All the 10 Nos have been delivered.
For Item B-----------5 Nos have been delivered.
For Item C, Nothing has been delivered.
So Invoice(MIRO)has been posted for 10, 5, 0 Nos for the three Items.

In FI side, is there any transaction code where in we can go and see Line Item display of which material---------how much is the PO Qty, GR Qty, Invoice Qty and the Invoice Amt to be paid individually line itemwise?

In F.13 we could see the consolidated amt for each vendor but we want the PO Line Itemwise Qties delivered and payment amt so that the remaining Qty and Amt can be calculated.

Goto Transaction MB5S - List of GR/IR Balances

Fill in the mandatory inputs and check the result list.

Auto PO creation During GR Posting

noreply@blogger.com (Total SAP) — Wed, 10 Dec 2008 06:26:00 +0000

In the movement type config - there is an auto PO creation flag, which allows the system to automatically create PO in the background from within the GR posting transaction. Has anyone used this feature -please share your experience. We are on 46c, and I don't see any existing movement type in the system which has this flag turned on.

For business process control purpose, I suggest avoiding auto PO from GR unless it is really necessary. Instead, use "traditional" PR-PO-GR process.

Actually what is the rational of using a automatic PO function, what is the benefit and what is the disadvantages of using this function? and under what business practise is best suit to use this function?

Sometimes the SAP help portal give you a lot of technical but didn't explain thoroughly from the business perspective point of view.

One of the benefits of using this feature is that you are taking delivery of the raw materials which are delivered by trucks and since it is not possible to capture the actual receipted quantity at the time of PO creation. Other benefits is to reduce the workload of purchasing department for the case of consignment process.

How to create AUTO PO during MIGO ?

Check in customizing whether you have maintained creation of automatic PO during good receipt.
Menu path : MM -> Inventory Management -> Goods Receipt -> Create Purchase order Automatically -> Activate Auto PO creation for Mvt type.

And then activate Auto PO creation in vendor master.