Vendor Downpayment in SAP

Steps below are relevant for Vendor Downpayment

1) F-47 (Downpayment Request) --> Can be created against Vendor or PO Document

2) F-48 (Post Vendor Down Payment)

3) F-54 (Clear Vendor Downpayment)

How to Commit work via SE37

Normally, when running SE37, it will not post the step, but instead, only test.
If you would like to Post / commit, then do the following. Or refer to the link below for more detailed steps.

1. Run SE37
2. Select Test --> Test Sequence from Menu Bar
3. First row should be filled with the FM that you would want to test. Second row should be BAPI_TRANSACTION_COMMIT
4. Execute
5. Now you will have to fill up with values in order to run your FM that you want to test.
6. Execute
7. The BAPI_TRANSACTION_COMMIT screen should appear. Just mark X at the WAIT Import Parameter.


http://wiki.sdn.sap.com/wiki/display/ABAP/Function+Module+Test+Sequence

How to prevent SAP from sending External Mails

Whether you are doing a SAP Upgrade Project, or working on an Issue which involves sending external mails, this setting could prevent accidentally sending out E-mails.

1) Go to SCOT
2) Expand INT
3) Double Click on SMTP
4) Add a # in the Mail Host field. E.g. before = 10.2.1.1, after = #10.2.1.1
5) Uncheck Node in Use

Useful SAP Parameters

Parameter ID is the SAP term that refers to setting a default value so that a particular field is automatically filled in for you. When the default value is filled in, you can still override it for a particular document or query. SAP does NOT provide Parameter IDs for all fields.

To use a Parameter, Go to SU3 (Own User Profile), then click on the Parameters Tab.
Here, maintain the parameters that you would like to use along with the values that you would like to default.
An example of this would be Parameter EKO (Purchasing Org). When you input Parameter EKO with value 1000, this means that whenever you enter a screen which contains Purchasing Org. field, value 1000 will automatically be defaulted for you. However, you are still able to overwrite it if you want to.

To find if a field contains a Parameter ID, click on a field --> F1 --> Technical Information. Then search if there is a Parameter ID.
Table that stores Parameter IDs is TPARA and it is possible to create custom parameter IDs that are not already available.

Useful Parameters are as below.
BFC - PR Release Code
BUK - Company Code
CAC - Controlling Area
EKG - Purchasing Group
EKO - Purchasing Org
EVO - Default Values for Buyer
FAB - Purchase Order Release Code
FIK - FM Area
FWS - Currency Unit
GJR - Fiscal Year
GR8 - Default File Transfer Download Path
KAR - Class Type
KGK - Vendor Account Group
KPL - Chart of Accounts
LAG - Storage Location
WRK - Plant
NDR = X To Default Print checked in Inventory for GR/GI slip
IVAMOUNTADJUST = X To automatically calculate Invoice Values
EFB - Buyer Default Values (Config via OMET)
ME_USE_GRID - To be able to view reports in Grid (e.g. in ME1L)

For a more comprehensive list, you could search for it in SAP by going to:
SM30 --> TPARA Table --> Display --> Application Hierarchy

If a field that you require defaulting does not have a Parameter ID, you could actually perform a few simple steps to create it.
1) T-code SM30 --> Enter Table TPARA --> Maintain
2) Enter a Parameter ID and Enter, then include a Text to describe this Parameter
3) Save
4) Assign this Parameter ID to a Data Element via SE11 --> Further Characteristics.

Output Type MLGR - GR Message Configuration

Output type MLGR - GR Message gives us the ability to inform via SAP mail that goods have been delivered or returned to the Buyer of the Purchase Order. This is indeed a neat functionality so that user is aware straight away as soon as GR is posted in SAP. It can be sent to SBWP alone, or also sent as Express message, where a popup will appear at the buyer's screen. This is good in the sense that the buyer does not have to open SBWP Inbox from time to time to check if a receipt has been done.

In order to configure this follow the steps below.


IMG→ Materials Management→ Inventory Management and Physical Inventory→ Output Determination→ Maintain Output Types
Choose Display → Change.
Select message type MLGR and choose Copy as.
Enter the name (anything of your choice) and a text, for example, goods receipt mail.
For the access sequence, enter 0003, because in the condition table, the item print indicator is also entered for this access sequence.
In the dialog structure, choose Mail Title and Texts. Enter any document title and any text for the mail.
The new message type must be included in the schema (procedure) ME0001 and at least one condition record must be created.

IMG→ Materials Management→ Inventory Management and Physical Inventory→ Output Determination→ Maintain Output Determination Procedures
Choose Conditions: Procedure .
Select the partner schema ME0001 and choose Control in the dialog structure.
Choose New Entries.
Add a new entry: level, such as 26, counter 10 and message type (The one you previously configured).
Save your input.

IMG→ Materials Management→ Inventory Management and Physical Inventory→ Output  Determination→ Maintain Conditions
Choose Create Conditions: Inventory Management .
Enter your message type and choose Key Combination.
Choose Enter.
Create the condition record with transaction type GR, print version 1, item print indicator 1/2(1 for GR, 2 for return delivery), and partner role MP.

Finally, during Purchase Order creation, GR message checkbox must be checked, this checkbox is located at the Header Details --> Delivery / Invoice Tab. Print checkbox also has to be checked during MIGO GR creation. This can be defaulted via setting user parameter NDR = X.

By performing the above, Buyers will now be able to receive a message in SAP Inbox whenever there is a Goods Receipt. However, the message will only contain a note saying that there is a Goods Receipt for your Purchase Order. It does not contain vital information such as Purchase Order number, Quantity, Vendor, etc.
To fix this, do the following.

1. use variables '&' instead of '$'

2. In transaction M706 for output type MLGR, make sure you have maintained the include by going in the long text, Choose Goto -> Change Editior, and maintain the form here :

"A goods receipt for your purchase order &MSEG-EBELN&
item &MSEG-EBELP& has just been entered.

Material: &MSEG-MATNR& &EKPO-TXZ01&
Quantity delivered: &MSEG-ERFMG&

Vendor: &MSEG-LIFNR&, &AM07M-NAME1&

Posting date: &MKPF-BLDAT&

&MFG&
&MKPF-USNAM&"

Then in MN22, delete the earlier condition record and create a new condition record in MN21
Here in the Communication in the MENU select
Goto -> Execution Parameter. You reach the dialog box Change Execution Parameter. Here you maintain the following data for mail processing:

Execution type U Transaction with memory
Execution element MB03
Memory ID MBN
Par name: RM07M-MBLNR Parameter value: MSEG-EBELN

Save

Sample of this message can be seen below.

Configuring SAP System Messages

Whenever you encounter an Error or Warning in SAP, this is when you will see a SAP system message. It is controlled via a message class along with its number. You can see as an example from the picture below.

From the screenshot above, you can see that the Message class is M3(The first 2 characters), followed by the Message number (351).

You can have an Overview of the SAP system messages via T-code SE91. It contains all the system messages there.

There are 2 things that you can do to a system message.
1) Configuring any system message of your choice to Warning, or Error. This can be done via SM30/SM31 for the following tables.

Table		Description
	T100S		List of all the system messages that the user can configure
	T100C		List of all the messages that the user has customized
	T100SA		List of all configurable application areas (or message classes)

2) Another thing that you could do is assign a separate version (Instead of 000) to your own and assign this version to a user. This gives us the functionality to have Warning for certain users, and Error for another set of users for the same system message. Whenever SAP encounters an issue, it will check whether there is a different version other than 000, and then check if the user has a parameter MSV assigned to that particular version. If not, the value under standard version 000 will be used.

Printing of Purchasing Documents

Here's a link that provides easy guidance on how to setup Printing for Purchasing Documents.
Link: http://wiki.sdn.sap.com/wiki/display/ERPSCM/Printing+of+purchasing+documents

ERP SCM Materials Management Wiki page

A very useful site which contains informative materials as well as common issues and hints.
Link: http://wiki.sdn.sap.com/wiki/display/ERPSCM/ERP+Supply+Chain+Management

Inventory Management Output Determination

Here's a link which explains Inventory Management Output Determination in an easy and structured manner.
Link: http://wiki.sdn.sap.com/wiki/display/ERPSCM/Output+Determination+in+Inventory+Management+%28IM%29#OutputDeterminationinInventoryManagement%28IM%29-15.NumberofGR%2FGIslips%28MSEGWEANZ%29

Transaction Variant - A step by step guide

Stumbled upon this SAP Wiki link. It is an easy guide to create a transaction variant which is a simple way to tailor a standard SAP screen without actually performing any actual modification.

Link: https://wiki.sdn.sap.com/wiki/display/Snippets/Transaction%20Variant%20-%20A%20Step%20by%20Step%20Guide%20for%20Creation

Link2: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a070bfbb-d34a-2d10-b092-ecbe0b0d4a4c?

Stock Consistency Check RM07KO01

You use the stock consistency check report (RM07KO01) to check the consistency of your stock data at company code level, valuation area level, or material level. This allows the system to determine possible errors in your stocks in good time, before they cause greater problems.
The report provides the following functions:

• For the table of stock values for anonymous stocks (MBEW), valuated sales order stock (EBEW), and valuated project stock (QBEW), the program checks if:

• The quantity of the total valuated stock matches the total of the individual subordinate stock segments

• The price specified corresponds to the value/plant quotient

• There is a negative price when you have a positive quantity of a material

• A negative value exists for a material when negative stocks are not allowed in Customizing

• There is a value when the relevant material has a stock level of zero

• In the case of split valuation, the program checks if:

• The quantity of the total valuated stock matches the total of the individual subordinate stock segments

• The total valuated stock for each material matches the total of the valuation segments

• The program checks for each material whether a cost estimate number exists. This updates the index for the accounting documents for the material (table CKMI1).

• In the case of materials subject to batch management, the program checks if the quantity of storage location stock matches the total of the individual subordinate batches.

• If the material ledger is active, the program checks if the tables in Inventory Management correspond to the material ledger tables.

Note:
We recommend that you run this report at regular intervals, for example, monthly after the period closing, or during the tasks for year-end closing. Periodic processing -> Consistency check.

List of Stock Values RM07MBST

SAP offers a report which we should run periodically such as once per month or during the tasks of year end closing called List of Stock Values with transaction code MB5L / MB5W or program RM07MBST. This report compares the total quantity and value of a stock against the respective stock accounts assigned (BSX).
Variances can occur when:
1) You enter postings to the stock account manually
2) Stock account is used for postings other than for stock postings. The stock GL should only be used for BSX transaction key assignment
3) The account assignment for stock accounts was changed during a productive operation, but the respective stocks however, were not deducted from the old account and posted to the new one (via 562 and 561 movement type respectively.

Analysis of conversion differences RM07AUMD

In SAP, you can maintain various unit of measures. This is by maintaining a Base Unit of Measure and alternative unit of measures. An example of alternative unit of measures are such as Goods Issue unit of measure, Order unit of measure, etc. When you perform a transaction, SAP will automatically convert all Uoms  to the Base Unit of Measure.

However, there may be times where conversion differences occur. There are 2 possibilities for this to happen.
1) When the Base Uom is a metric unit such as meter, litre, kilogram and the posting is made with a non-metric unit such as yard, gallon, pound
2) When the Base Uom is not the smallest unit of measure compared to the alternative unit of measures.

For this, run transaction MB5U or RM07AUMD to analyze and correct this conversion differences if any exist.