Professional Documents
Culture Documents
Sap MM Guide PDF
Sap MM Guide PDF
SAP Implementation
Project Pragati
USER MANUAL
USER MANUAL
Materials Management
Document name
Materials Management
DOCUMENT INFORMATION
Version
Filename
Date
Author
Reviewed
by
Document location
Changes from
previous version
V 1.0
Version
EUT -MM
REFERENCE DOCUMENTS
Document
Version
R Reference
DOCUMENT APPROVALS
Kedar Kulkarni
MM Consultant
Prepared by
(KPIT Cummins Infosystems Limited.)
Approved by
(Duro Shox Pvt Limited)
Version
1.1.1 Purpose.....................................................................................................................................................10
1.1.2 Prerequisites .............................................................................................................................................10
1.1.3 Material Master Record..............................................................................................................................10
1.1.4 Vendor Master Record...............................................................................................................................24
1.1.5 Purchasing Info Record.............................................................................................................................35
1.1.6 Source List.................................................................................................................................................41
1.1.7 CIN Master Data........................................................................................................................................43
1.1.8 Excise Condition Record............................................................................................................................53
1.2
1.2.1 Use............................................................................................................................................................56
1.2.2 Procedure..................................................................................................................................................56
1.2.3 Result.........................................................................................................................................................61
1.2.4 Example ....................................................................................................................................................61
1.3
1.3.1 Use............................................................................................................................................................61
1.3.2 Procedure..................................................................................................................................................61
1.4
1.4.1 Use............................................................................................................................................................64
1.4.2 Procedure..................................................................................................................................................64
1.4.3 Result ........................................................................................................................................................66
1.4.4 Example ....................................................................................................................................................66
1.5
1.5.1 Use............................................................................................................................................................67
1.5.2 Procedure..................................................................................................................................................67
1.5.3 Result ........................................................................................................................................................69
1.6
1.6.1 Use............................................................................................................................................................69
1.6.2 Procedure..................................................................................................................................................69
1.6.3 Result ........................................................................................................................................................70
1.6.4 Example.....................................................................................................................................................70
1.7
1.7.1 Procedure..................................................................................................................................................71
1.8.
1.8.1 Use...........................................................................................................................................................74
1.8.2 Procedure..................................................................................................................................................74
1.8.3 Result ........................................................................................................................................................76
1.9
Purchase Order__________________________________________________77
1.9.1 Use............................................................................................................................................................77
1.9.2 Procedure..................................................................................................................................................77
1.9.3 Result ........................................................................................................................................................82
1.9.4 Example ....................................................................................................................................................82
Version
1.11Message Output_________________________________________________87
1.11.1 Use.........................................................................................................................................................87
1.11.2 Procedure................................................................................................................................................87
1.12
1.12.1 Use..........................................................................................................................................................89
1.12.2 Prerequisites ...........................................................................................................................................89
1.12.3 Procedure................................................................................................................................................89
1.12.4 Result ......................................................................................................................................................99
Material document 5000000009 posted...............................................................................................99
1.12.5 Example ..................................................................................................................................................99
1.13
1.13.1 Use........................................................................................................................................................100
1.13.2 Procedure..............................................................................................................................................100
1.13.3 Result ....................................................................................................................................................105
1.13.4 Example ................................................................................................................................................105
1.14
1.14.1 Use........................................................................................................................................................106
1.14.2 Procedure..............................................................................................................................................106
1.14.3 Result ....................................................................................................................................................113
Return Delivery document created..................................................................................................................113
1.14.4 Example ................................................................................................................................................113
1.15
1.15.1 Procedure..............................................................................................................................................114
1.15.2 Result ....................................................................................................................................................116
1.15.3 Example ................................................................................................................................................116
1.16
1.16.1 Use........................................................................................................................................................117
1.16.2 Prerequisites .........................................................................................................................................117
1.16.3 Procedure..............................................................................................................................................117
1.16.4 Result ....................................................................................................................................................120
1.17
Credit Memo___________________________________________________121
1.17.1 Use........................................................................................................................................................121
1.17.2 Prerequisites .........................................................................................................................................121
1.17.3 Procedure..............................................................................................................................................121
1.17.4 Result ....................................................................................................................................................127
1.17.5 Example ................................................................................................................................................127
1.18
1.18.1 Use........................................................................................................................................................127
1.18.2 Prerequisites..........................................................................................................................................128
1.18.3 Procedure..............................................................................................................................................128
1.18.4 Result.....................................................................................................................................................133
1.18.5 Example.................................................................................................................................................133
1.19
1.19.1 Use........................................................................................................................................................134
1.19.2 Prerequisites..........................................................................................................................................134
1.19.3 Procedure..............................................................................................................................................134
1.19.4 Result ....................................................................................................................................................139
Version
1.20
1.20.1 Purpose.................................................................................................................................................140
1.20.2 Prerequisites .........................................................................................................................................140
1.20.3 Procedure..............................................................................................................................................140
1.20.4 Result.....................................................................................................................................................144
1.20.5 Example.................................................................................................................................................144
1.21
1.21.1 Purpose.................................................................................................................................................145
1.21.2 Prerequisites .........................................................................................................................................145
1.21.3 Procedure..............................................................................................................................................145
1.21.4 Result.....................................................................................................................................................150
1.21.5 Example.................................................................................................................................................150
2.3
2.3.1 Procedure................................................................................................................................................159
2.4
Message Output_________________________________________________162
2.4.1 Use..........................................................................................................................................................162
2.4.2 Procedure................................................................................................................................................162
2.5
2.5.1 Use..........................................................................................................................................................164
2.5.2 Procedure................................................................................................................................................164
2.5.3 Result ......................................................................................................................................................171
2.5.4 Example ..................................................................................................................................................171
2.6
2.6.1 Use..........................................................................................................................................................172
2.6.2 Procedure................................................................................................................................................172
2.6.3 Result ......................................................................................................................................................183
2.6.4 Example ..................................................................................................................................................183
2.7
2.7.1 Use..........................................................................................................................................................184
2.7.2 Procedure................................................................................................................................................184
2.7.3 Result ......................................................................................................................................................190
2.7.4 Example ..................................................................................................................................................190
3.1.1 Purpose...................................................................................................................................................191
3.1.2 Prerequisites ...........................................................................................................................................191
3.2
Version
3.2.1 Use..........................................................................................................................................................192
3.2.2 Prerequisites ...........................................................................................................................................192
3.2.3 Procedure................................................................................................................................................192
3.2.4 Result ......................................................................................................................................................196
3.2.5 Example ..................................................................................................................................................196
3.3
Message Output_________________________________________________197
3.3.1 Use..........................................................................................................................................................197
3.3.2 Procedure................................................................................................................................................197
3.4
3.4.1 Use..........................................................................................................................................................199
3.4.2 Prerequisites ...........................................................................................................................................199
3.4.3 Procedure................................................................................................................................................199
3.4.4 Result ......................................................................................................................................................201
3.4.5 Example ..................................................................................................................................................202
3.5
3.5.1 Use..........................................................................................................................................................202
3.5.2 Prerequisites............................................................................................................................................202
3.5.3 Procedure................................................................................................................................................202
3.5.4 Result ......................................................................................................................................................204
3.5.5 Example ..................................................................................................................................................204
3.7
3.7.1 Use..........................................................................................................................................................209
3.7.2 Prerequisites ...........................................................................................................................................209
3.7.3 Procedure................................................................................................................................................209
3.7.4 Result ......................................................................................................................................................217
3.7.5 Example ..................................................................................................................................................217
3.8
3.8.1 Use..........................................................................................................................................................218
3.8.2 Procedure................................................................................................................................................218
3.8.3 Result ......................................................................................................................................................220
3.8.4 Example ..................................................................................................................................................220
3.9
3.9.1 Use..........................................................................................................................................................221
3.9.2 Procedure................................................................................................................................................221
3.9.3 Result ......................................................................................................................................................222
3.9.4 Example ..................................................................................................................................................222
3.10
3.10.1 Use........................................................................................................................................................222
3.10.2 Procedure..............................................................................................................................................222
3.10.3 Result ....................................................................................................................................................226
3.10.4 Example ................................................................................................................................................226
5.1.1 Purpose...................................................................................................................................................227
5.1.2 Prerequisites ...........................................................................................................................................227
5.2
Version
5.2.1 Use..........................................................................................................................................................228
5.2.2 Procedure................................................................................................................................................228
5.2.3 Result ......................................................................................................................................................229
5.3
5.3.1 Use..........................................................................................................................................................230
5.3.2 Procedure................................................................................................................................................230
5.3.3 Result ......................................................................................................................................................235
5.3.4 Example...................................................................................................................................................235
5.4
5.4.1 Use..........................................................................................................................................................236
5.4.2 Procedure................................................................................................................................................236
5.4.3 Result ......................................................................................................................................................239
5.7
5.8
Message Output_________________________________________________243
5.8.1 Use..........................................................................................................................................................243
5.8.2 Procedure................................................................................................................................................243
5.9
5.9.1 Use..........................................................................................................................................................245
5.9.2 Procedure................................................................................................................................................246
5.9.3 Result ......................................................................................................................................................256
5.9.4 Example ..................................................................................................................................................256
5.10
5.10.1 Use........................................................................................................................................................257
5.10.2 Procedure..............................................................................................................................................257
5.10.3 Result ....................................................................................................................................................261
5.10.4 Example ................................................................................................................................................261
Purchase Order_________________________________________________262
6.1.1 Use..........................................................................................................................................................262
6.1.2 Procedure................................................................................................................................................262
6.1.3 Result.......................................................................................................................................................266
6.2
6.2.1 Procedure................................................................................................................................................266
6.3
6.3.2 Use..........................................................................................................................................................267
6.3.3 Prerequisites ...........................................................................................................................................267
6.3.4 Procedure................................................................................................................................................267
6.2.3 Result.......................................................................................................................................................269
6.4
6.4.1 Procedure...............................................................................................................................................269
Version
6.4.2 Result......................................................................................................................................................271
6.5
6.5.1 Use..........................................................................................................................................................272
6.5.2 Procedure................................................................................................................................................272
6.5.3 Result.......................................................................................................................................................275
7.1.1 Purpose...................................................................................................................................................276
7.1.2 Prerequisites............................................................................................................................................276
7.2
7.2.1 Use..........................................................................................................................................................277
7.2.2 Prerequisites............................................................................................................................................277
7.2.3 Procedure................................................................................................................................................277
7.2.4 Result ......................................................................................................................................................279
7.4
7.4.1 Use..........................................................................................................................................................288
7.4.2 Prerequisites............................................................................................................................................288
7.4.3 Procedure................................................................................................................................................288
7.4.4 Result ......................................................................................................................................................291
7.5
7.5.1 Use..........................................................................................................................................................292
7.5.2 Prerequisites............................................................................................................................................292
7.5.3 Procedure................................................................................................................................................292
7.5.4 Result ......................................................................................................................................................295
8.1.1 Use..........................................................................................................................................................295
8.1.2 Prerequisites............................................................................................................................................295
8.1.3 Procedure................................................................................................................................................295
8.1.4 Result ......................................................................................................................................................298
8.2
8.2.1 Use..........................................................................................................................................................298
8.2.2 Prerequisites............................................................................................................................................298
8.2.3 Procedure................................................................................................................................................298
8.2.4 Result ......................................................................................................................................................300
9. Reports .................................................................................................................................................301
7.1
Purchasing____________________________________________________301
Version
9.2
Inventory_______________________________________________________307
Icons
Icon
Meaning
Caution
Example
Note
Recommendation
Syntax
Abbreviations
R
Conditional field
Version
Purpose
This process describes the procurement process of raw materials from indigenous source of supply with Country
Version India (CIN) relevant process like processing of Excise Duty (ED) and Sales Tax (ST) process.
1.1.2
Prerequisites
The following scenario specific master data must be created for operation of this building block.
1.
2.
3.
4.
5.
6.
1.1.3
Menu Path
T Code
Internal Number
assignment .
Enter the Industry Sector
Enter the Material Type
Version
Select the required views and press Enter to input the organizational levels.
Version
1.1.3.1
Version
Version
Press Additional Data to maintain the Alternate Unit of Measures (for e.g. 1000G= 20Nos for the Semi finished
goods)
Version
1.1.3.2
Purchasing Views
Version
Version
1.1.3.3
MRP Views
Version
Version
Version
1.1.3.4
Version
1.1.3.5
Version
Accounting Views
1.1.3.6
Version
Costing Views
1.1.4
Menu Path
T Code
Version
1.1.4.1
General Data
Version
Version
Version
Version
Version
Version
1.1.4.2
Accounting Data
Reconciliation Accounts:
Version
Version
1.1.4.3
Version
Purchasing Data
Domestic Schema
Import Schema
Version
Press
1.1.5
Menu Path
T Code
Version
You use this component if you wish to store information on a vendor and a material as master data at purchasing
organization or plant level. You can create purchasing info records for different procurement types (standard,
subcontracting, pipeline, consignment).
Version
Version
No need to enter anything in the below screen as it copies all the data from the Vendor Master.
Version
Version
1.1.5.1
Result
Purchasing Info Record is created
1.1.5.2
Example
Purchasing Info Record 5300000384 is created.
Version
1.1.6
Menu Path
T Code
Source List
SAP Easy Access Logistics Materials Management Purchasing Master
Data Source List Maintain
ME01 Maintain
ME03 Display
ME04 - Changes
Version
Select if the
Vendor is fixed
Version
Enter 1 to be included
in MRP Run
Maintain the Validity
Period till until which you
will procure this material
from this vendor
1.1.7
Menu Path
T Code
1.1.7.1
Chapter IDs
Version
Version
Press
Version
1.1.7.2
Version
Version
Press
Version
1.1.7.3
Version
Press
Version
1.1.7.4
Version
Press
Version
1.1.8
1.1.8.1
Use
When you enter a purchasing document, for example, a purchase order, the R/3 System
automatically calculates the applicable excise duties using the condition technique.
1.1.8.2
Procedure
1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
No Menu path available for this transaction
Transaction code
FV11
2. Enter the appropriate Condition type (various condition types given in next page) and maintain the
respective values.
Version
Version
3. Press Ctrl+S or
4.
1.1.8.3
Result
Condition records saved.
Version
Version
Use
Request for Quotation is used to float enquiries in market to obtain quotations from prospective vendors.
This transaction is optional for the process.
1.2.2
Procedure
Version
4. Choose
(header details icon) on the toolbar, then on screen Create RFQ: Header Data, enter
information in the fields as specified in the table below:
Version
Version
5. Choose
(vendor address button) on the toolbar, then on screen Create RFQ: Vendor Address, enter
information in the fields as specified below:
After entering the vendor code and pressing enter the details of vendor will be displayed automatically.
Version
6. Press
to Save the RFQ. This will refresh the Create RFQ: Vendor Address screen to allow creation of
the same RFQ data to a new vendor by following the steps outlined above.
1.2.3
Version
Result
RFQ created
Similarly create for other vendor in the same screen and various RFQ Nos will be generated
1.2.4
Example
Use
A RFQ needs to be printed for transmitting to vendor. This transaction is optional for the process.
1.3.2
Procedure
Transaction code
ME9A
Version
Version
Version
Use
This transaction is used to maintain the quotation, which is submitted by vendors. Vendor communicates
price for material and as a result the RFQ (Request for Quotation) needs to be updated.
This transaction is optional for the process.
1.4.2
Procedure
ME47
Version
5. Enter information in the fields as specified in the table below. Some fields will not be available for input, as they
are reference fields only.
6. Once all necessary header data has been maintained, the user can then enter the price information in one
of two fashions:
a. Enter the price in the Net Price field on the Maintain Quotation: Item Overview screen by
Choosing overview icon on toolbar.
Version
b. To enter more detailed information in addition to the net price, select the line item and choose
the Item Details icon. Choose the green Back arrow to return to the Overview screen once
data has been maintained.
i. A vendors quoted price can be entered in one of two ways.
ii. Enter the net price per unit in the Net price field. This price includes the vendor's
normal discounts and surcharges only. Cash discounts (for prompt payment) and taxes
are calculated separately.
iii. Enter the gross price in the Net price field, and maintain the conditions for the item.
Then the system automatically replaces the entered gross price with the calculated net
price. If the net price for an item is entered for which pricing conditions have been
maintained, the system always replaces the price entered with the calculated net price.
iv. Enter the Tax Code for any relevant taxes (for example, Excise Duty, Sales Taxes etc.)
in the Tax code field. If a purchase order is created by referencing an RFQ, this code
facilitates the determination of the tax amount when the invoice is entered in the
system.
v. After entering tax code, after choosing this system may give an information message
showing the effective price, Choose Enter to continue.
7. Once all quotation information has been successfully entered, save the data by Choosing on the Save
button, or Choose the <Ctrl + S> keys. A message will be displayed that the data has been saved.
1.4.3
Result
Quotation is maintained.
1.4.4
Example
Version
Use
Required to compare prices from all quotations received as a result of a competitive bidding process.
This transaction is optional for the process.
1.5.2
Procedure
ME49
Version
Rank is
generated
automatically
Mean and
Effective Price is
highlighted
5. To view any of the following information for a particular quote included in the comparison, Choose the RFQ
number with the mouse to select it, then Choose the appropriate icon/button on the menu toolbar:
6. Display Material:
Allows the user to view the purchasing data in the material master record.
7. Display Vendor: Allows the user to view the vendor master record.
8. Additional Info: Allows the user to view payment terms, bid dates, currency information for all the vendor
quotations in the list.
9. If any information has been modified through the comparison list, save the RFQ before exiting. If changes
have been made and the user attempts to exit without saving, the system will return a message to verify
action.
10. To exit the transaction, choose the green Back arrow, the yellow Exit arrow, or Choose the F3 button.
1.5.3
Version
Result
Use
A Purchase Requisition is created to indicate purchase department to procure materials or services with
details like how much quantity is required, when required. Generally it is created automatically for Raw
materials and Packing Materials through MRP Run and Spares and Service related to Plant
Maintenance Purchase Requisition is generated automatically from Plant maintenance Order.
This transaction is optional for the process.
1.6.2
Procedure
Transaction code
ME51N
Enter required
Quantity
Press
1.6.3
Result
1.6.4
Example
1.7
Version
1.7.1 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Transaction code
ME51N
Enter PR No.
Version
Version
Version
1.8.
Version
1.8.1 Use
a) This section explains the functions provided by the SAP System for converting requisitions into
external purchasing documents (purchase orders, contract release orders, scheduling agreement
delivery schedules, RFQs), and the processing options thereby available to you:
Assigning means defining the desired source for each purchase requisition item
o Further processing involves generating lists of requisitions that have been assigned or flagged as
outlined above, and the subsequent creation of RFQs, purchase orders, or lines of delivery
schedules under scheduling agreements.
1.8.2 Procedure
2. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Transaction code
Version
3. The assignment of sources to and further processing of purchase requisitions are two distinct functions.
You can choose whether you wish to perform the functions in two separate steps or in just one.
4. Below are the Selection Parameters to restrict the process of PO from PR
5. Press
1. If Source List is
available click this button
1.8.3 Result
The source is assigned to PR and can be processed for PO.
Version
Version
Please ensure that Purchase Order Value does not exceed specified value and if the purchase order value
crosses this limit a release procedure is applied on this purchase order. To release the Purchase Order go
to ME28 for collective release and ME29N for individual release.
1.9.2 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Logistics Materials Management Purchasing Purchase
Order CreateVendor/Supplying Plant Known
Transaction code
ME21N
Version
2. If you want create purchase order with reference to the purchase requisition, on item details screen enter
the purchase requisition number and item number at Purch. Req. field. System will automatically adopt all
the data from requisition.
Click the
Purchasing
Requisitions
and Press
Adopt
Version
Version
Version
1.9.3 Result
Purchase Order is created.
1.9.4 Example
Standard PO created under the number 210000000.
Version
Transaction code
ME29N
Enter PO No.
Version
Version
Version
Version
1.11Message Output
1.11.1 Use
A Purchase Order needs to be printed for transmitting to vendor.
1.11.2 Procedure
2. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Logistics Materials Management Purchasing Purchase
Order Messages Print/Transmit
Transaction code
ME9F
4. Choose
to Execute.
Version
5. On screen Message Output select the appropriate Document number and perform the following:
Version
Version
1.12.2 Prerequisites
Purchase Order
1.12.3 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Logistics Materials Management Inventory Management
Goods Movement Goods Receipt For Purchase Order
PO Number Known
Transaction code
2.
MIGO
On the Goods Receipt Purchase Order screen, make the following entries:
Check for correct movement
type whenever doing goods
movement
After pressing Enter system will fetch all the data from the Purchase Order as shown below:
Version
System defaults the balance quantity in PO, change the quantity to the received quantity:
Version
Version
Version
Description
R/ O/ C
Goods
Receipt
Goods Receipt
Purchase
Order
Purchase Order
Movement
Type
Version
Comment
101
Enter
Document
Date
Document Date
Delivery Note
in Header
Vendor
Vendor
Posting Date
Posting date
Bill of lading
Bill of lading
Header text
Header text
Grayed out
Material tab
Grayed out
Quantity
defaulted from
Purchase Order
Quantity in unit of
entry
Qty in
delivery note
Quantity in delivery
note
Movement type
Stock type
Stock type
Plant
Plant
Storage
location
Storage location
Goods
Recipient
Goods Recipient
Unloading point
Text
Text
Version
Purchase Order
Del.
completed
ind.
Delivery completion
indicator
Defaulted by system if PO
Qty = GR Qty
Grayed out
Grayed out
Vendor name
For this material batch management is not active. Just for reference purpose the following
data is given.
Select Batch tab in Detail data.
You will get Excise Invoice tab at Header Data for capturing vendor excise invoice details and for posting Part I
and Part II.
6. On the Excise Invoice tab at Header Data make the following entries.
Version
System defaults
the Excise Duty
(BED & ECS)
and in case
Field name
Description
R/O/C
Comment
Capture &
Post Excise
invoice
Defaulted
Excise Group
Excise Group
Excise
Invoice
Excise invoice
Excise Inv.
Date
BED
Grayed out
AED
Grayed out
SED
Grayed out
NCCD
NCCD
Grayed out
ECS
Education Cess
Grayed out
MRP Indicator
Chapter ID of material
EI Quantity
Excise Invoice
Quantity
Base Value
BED
AED
NCCD
NCCD
SED
ECS
Education Cess
Please cross check the BED, AED, SED, NCCD and ECS amount of item as per the Vendor
Excise Invoice, legally you cannot avail more than what mentioned in Vendor Excise Invoice. All
other information is defaulted by the system. Hence, no action required by the user.
Version
Version
1.12.4 Result
Material document 5000000009 posted
1.12.5 Example
Material document 5000000009 posted
Version
Version
1.13.2 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Logistics Materials Management Logistics invoice
Verification Document Entry Enter Invoice
Transaction code
MIRO
2. If you are opening for the first time this transaction, system will ask for Company Code, please give 1000 to
go in side the transaction.
3. On the Enter Incoming Invoice: Company Code 1000 screen, make the following entries:
If Part II entry is not done then system will not allow you to POST Invoice
Unless and until you post part2 system will not allow invoice verification
Version
Version
Field name
Description
R/ O/ C
Transaction
Invoice
Header Data
Defaulted by system
Basic tab
Invoice Date
Invoice Date
Reference
Invoice reference
Posting date
Posting Date
Amount
Invoice Amount
Amount
mentioned is
only an example
Currency
Tax code
Bus.place/se
ctn
Business place or
section code
Text
Text
Payment tab
Payment tab
BaselineDt
Pmnt terms
Payment terms
Payment terms of
document, if entered will be
defaulted from purchase
order
Due on
Payment due on
Will be calculated by
Calculate tax
Comment
Will be defaulted
if payment terms
entered in PO
Grayed out
Version
system
Discount
Cash discount
Layout
Purchase order /
Schedule Agreement
Purchase order
number
Layout of invoice
verification
Defaulted for
user
Defaulted
Choose Enter
4. Choose Enter to complete the document feeding part.
5. To check the document credit and debit is balanced on the top right corner of your screen a traffic light is
displayed. Beside that Balance of the document is displayed.
Ensure that the Balance is ZERO before posting the document and the traffic light is green or yellow color.
6. If you want to see the accounting postings in simulation mode, Choose Simulation on middle of fourth row
of your screen.
Version
1.13.3 Result
Logistics Invoice verification document is posted.
1.13.4 Example
Document no. 5105600102 created
Version
Version
This transaction is used basically when purchased material is needs to be sent back to vendor because of
various reasons like poor quality, incomplete items, damaged etc.
b)
Bore proceeding with return delivery to vendor please ensure that sufficient stock is available in storage
location and if batch managed in particular batch stocks also. Other wise system will give error message.
Before doing Return Delivery to vendor, check if you have already done Invoice Verification to that Goods
Receipt. If you have already done invoice verification please raise Credit Memo to the extent of Returns
quantity and then proceed with this process. Other wise system will give an error message.
How to create Credit Memo transaction is explained in the chapter mentioned 1.17 below.
1.14.2 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Logistics Materials Management Inventory Management
Goods Movement Goods Receipt For Purchase Order
PO Number Known
Transaction code
MIGO
2. Select Return Delivery from drop down list to make Return Delivery to vendor.
3. On the Return Delivery Material Document screen, make the following entries:
Version
Version
Field name
Description
R/ O/ C
Return
Delivery
Return Delivery
Material
Document
Material Document
number
Enter
Document
Date
Document Date
Delivery Note
in Header
Posting Date
Posting date
Comment
Bill of lading
Header text
Header text
Via Delivery
Via Delivery
Version
Material tab
Grayed out
Qty in unit of
entry
Quantity in unit of
entry
Qty in
delivery note
Quantity in delivery
note
Movement
type
Movement type
Stock type
Stock type
Plant
Plant
Storage
location
Storage location
Goods
Recipient
Goods Recipient
Unloading
point
Unloading point
Reason for
Movement
Text
Text
Select
Quantity tab
in Detail data.
Select
Where tab in
Detail data.
Grayed out
Purchase Order
Grayed out
Delivery completion
indicator
Grayed out
Vendor name
Version
Version
Field name
Description
R/ O/ C
Comment
Select
Create
Excise
Invoice
Excise Group
Excise Group
Series Group
Removal time
Removal time of
goods
BED
Grayed out
AED
Grayed out
SED
Grayed out
Chapter ID of material
EI Quantity
Excise Invoice
Quantity
Base Value
BED
Goods Issue
Indicator
Please cross check the BED, AED, SED, NCCD and ECS amount of item as per the Vendor
Excise Invoice, legally you cannot avail more than what mentioned in Vendor Excise Invoice. All
other information is defaulted by the system. Hence, no action required by the user.
4. Choose Check at the top of screen.
5. Choose Post to post the document.
Version
Version
1.14.3 Result
Return Delivery document created
1.14.4 Example
Return Delivery Document No. 50000000011 created.
Note: Excise Invoice for Return delivery also will be generated in the back ground for this
transaction
Version
Description
R/O/C
Document Number
Doc Year
Document year
Enter
Version
Comment
1.15.2 Result
Excise invoice generated is displayed.
1.15.3 Example
Excise invoice 0000000014 generated and displayed.
Version
Version
1.16.2 Prerequisites
Excise Invoice Document is generated and posted.
1.16.3 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP CIN R/3
User menu
Transaction code
J1IV
Description
R/ O/ C
Comment
Excise
internal
reference
Select internal excise invoice number from drop down list, you can find it with reference to the
Excise Invoice number generated in above step 1100400070 for example with the combination of
Excise Group 10 and vendor code 10006.
Document
No.
Document Number
Document
year
Document Year
Version
5. To take printout, select Goto from the top main menu and select Print Document from the list. Or Choose
Control + P to get the access of Excise Invoice Printing screen.
7. From the list select the excise invoice number by choosing the check box left side of number.
8. To take printout on printer Choose the Printer icon or Choose F8.
Version
Version
1.16.4 Result
Excise Invoice is printed.
Version
1.17.2 Prerequisites
1.17.3 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Logistics Materials Management Logistics invoice
Verification Document Entry Enter Invoice
Transaction code
MIRO
2. If you are opening for the first time this transaction, system will ask for Company Code, please give 1000 to
go in side the transaction.
Version
Version
Field name
Description
R/ O/ C
Version
Comment
Transaction
Credit memo
Header Data
Defaulted by system
Basic tab
Invoice Date
Invoice Date
Reference
Invoice reference
Posting date
Posting Date
Amount
Currency
Tax code
Bus.place/se
ctn
Business place or
section code
Text
Text
Payment tab
Payment tab
BaselineDt
Pmnt terms
Payment terms
Payment terms of
document, if entered will be
defaulted from purchase
order
Due on
Payment due on
Will be calculated by
system
Discount
Cash discount
Calculate tax
Version
Will be defaulted
if payment terms
entered in PO
Grayed out
Layout
Purchase order /
Schedule Agreement
Purchase order
number
Layout of invoice
verification
Version
Defaulted for
user
Defaulted
Choose Enter
4. Choose Enter to complete the document feeding part.
5. To check the document credit and debit is balanced on the top right corner of your screen a traffic light is
displayed. Beside that Balance of the document is displayed.
Ensure that the Balance is ZERO before posting the document and the traffic light is green or yellow color.
6. If you want to see the accounting postings in simulation mode, Choose Simulation on middle of fourth row
of your screen.
Version
1.17.4 Result
Logistics Invoice verification document is posted.
1.17.5 Example
Document no. 5105600791 created
Version
The system takes the amount and quantity for the credit memo or invoice from the invoice or credit
memo to be cancelled, thus avoiding any differences between the invoice and the credit memo or the
credit memo and the invoice.
1.18.2 Prerequisites
An invoice document can only be cancelled if:
When you cancel documents in Logistics Invoice Verification, the document line items are not
automatically cleared in Financial Accounting. We recommend that you periodically clear such
items (using daily background jobs, for example).
1.18.3 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Logistics Materials Management Logistics invoice
Verification Further Processing Cancel Invoice Document
Transaction code
MR8M
Version
3. In the fields Invoice doc. number and Fiscal year, enter the data for the invoice document you want to
cancel.
4. In the Reversal reason field, select the reason for cancelling the invoice. This allows you to differentiate
between different types of cancellations.
Version
5. You can display the document to check. Choose Display document to do this. You can look at the items of
the document to be cancelled. Return to the initial screen by choosing Back.
Version
Version
1.18.4 Result
Document Reversed and Clear FI Documents Manually.
1.18.5 Example
Document Reversed with no. 5105600114.
Version
Version
1.19.2 Prerequisites
A GR can only be cancelled if:
1.19.3 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Logistics Materials Management Inventory Management
Goods Movement Goods Receipt For Purchase Order
PO Number Known
Transaction code
MIGO
2. Choose Cancellation and enter the respective Material Document No. (GR No.)
Version
Version
3. Press enter so that all the data will be captured automatically by the system. If any comment is there to
mention it can be mentioned in the Head Text and Text which is available at the Item level.
5. Select the Check box Item OK, after entering all the data.
You will get Excise Invoice tab at Header Data and Item Details.
Version
7. Press Ctrl+S or
Version
1.19.4 Result
Material document posted, please note the document number.
1.19.5 Example
Material document 5000000020 posted
Version
Version
1.20.2 Prerequisites
Material Document (GR) should be reversed.
1.20.3 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Country India User Menu Indirect Taxes Procurement
Excise Invoice Incoming Excise Invoice Central Processing
Capture / Change / Cancel / Display / Post
Transaction code
J1IEX
Version
Version
Version
1.20.4 Result
CENVAT Posting Reversed.
1.20.5 Example
CENVAT Posting Reversed with document no. 0000000008.
Version
Version
1.21.2 Prerequisites
1.21.3 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Country India User Menu Indirect Taxes Procurement
Excise Invoice Incoming Excise Invoice Central Processing
Capture / Change / Cancel / Display / Post
Transaction code
J1IEX
2. Select Cancel.
3. Select Vendor Excise Invoice.
Version
Version
Version
Version
1.21.4 Result
Excise Invoice has been successfully cancelled.
1.21.5 Example
Excise Invoice 0000000008 / 2008 ( 1234 ) has been successfully cancelled.
Version
Version
2.1.2 Prerequisites
The following scenario specific master data must be created for operation of this building block and
subsequent dependent building blocks.
Version
2.2.2 Prerequisites
2.2.3 Procedure
5. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Logistics Materials Management Purchasing Purchase
Order CreateVendor/Supplying Plant Known
ME21N
Transaction code
Version
Version
Version
.
8. To change the vendor for condition type select JCDB condition type and Choose on Condition detail icon
located at left bottom side of your screen.
9. System will take to new Item Conditions Detail: screen. In this screen at right bottom of screen you can
find the vendor code 60000 the main imported vendor is defaulted here. You have to replace this vendor
Version
code with respective vendors and Choose enter and green arrow to come back (F3) to condition tab of
purchase order.
10. Repeat the same for other condition types such as JCV1, JECV, JADC, and JEDB etc.
Version
2.2.4
Version
Result
A message will be displayed stating that the purchase order was saved, with the purchase order
number, please note the purchase order number.
2.2.5
Example
Standard PO created under the number 3100000000.
Transaction code
ME29N
Version
Version
Version
Use
2.4.2
Procedure
Transaction code
10. Choose
to Execute.
Version
11. On screen Message Output select the appropriate Document number and perform the following:
Version
Version
Use
In this process of Logistics Invoice Verification all the Incoming Invoices are verified in terms of their
content, prices and arithmetic. When the invoice is posted, the invoice data is saved in the system. The
system updates the data saved in the invoice documents in Materials Management and Financial
Accounting.
2.5.2
Procedure
MIRO
8. If you are opening for the first time this transaction, system will ask for Company Code, please give 1000 to
go in side the transaction.
9. On the Enter Incoming Invoice: Company Code 1000 screen, make the following entries:
Enter the Amounts of the Customs Duties Manually in the Amount Column with referring to PO.
Version
Version
Field name
Description
R/ O/ C
Transaction
Invoice
Header Data
Defaulted by system
Basic tab
Invoice Date
Invoice Date
Reference
Invoice reference
Posting date
Posting Date
Amount
Invoice Amount
Amount
mentioned is
only an example
Currency
Tax code
Bus.place/se
ctn
Business place or
section code
Text
Text
Payment tab
Payment tab
BaselineDt
Pmnt terms
Payment terms
Payment terms of
document, if entered will be
defaulted from purchase
order
Due on
Payment due on
Will be calculated by
Calculate tax
Comment
Will be defaulted
if payment terms
entered in PO
Grayed out
Version
system
Discount
Layout
Cash discount
Purchase order /
Schedule Agreement
Purchase order
number
Planned Delivery
Costs
Layout of invoice
verification
Defaulted for
user
Choose Enter
Ensure that the Balance is ZERO before posting the document and the traffic light is green or yellow color.
12. If you want to see the accounting postings in simulation mode, Choose Simulation on middle of fourth row
of your screen.
Version
13. Choose Display Currency which will lead to small pop-up window having the company code currency and
Document Currency, position the cursor on the INR to convert to Document Currency and press the details
button.
Version
Version
2.5.3
Result
2.5.4
Example
Version
2.6
Version
2.6.1
Use
Goods are received from the Vendor as a result of a Purchase Order at the receiving plant. A goods
movement is entered into the system referencing this PO and a goods receipt material document is
posted. Appropriate general ledger accounts are also posted and stocks are updated.
2.6.2
Procedure
Transaction code
2. On the Goods Receipt Purchase Order screen, make the following entries:
Field name
Description
R/ O/ C
Goods
Receipt
Goods Receipt
Inbound
Delivery
Purchase Order
Movement
Type
Comment
101
Enter
Since this is imported purchase order and you have already done invoice verification for
planned delivery cost. System will give a new popup Excise Invoice item number screen (which
is not there in normal other process) asking for Commercial invoice number and year.
Please enter the invoice verification document number which you have done in above 5105600792
and year 2006.
Version
Version
3. Choose Enter where a small pop-up window will prompt to enter the Commercial Invoice No. and Year (i.e.,
4. After pressing Enter system will fetch all the data from the Purchase Order as shown below:
Version
Version
Version
Version
Field name
Description
R/ O/ C
Goods
Receipt
Goods Receipt
Inbound
Delivery
Purchase Order
Movement
Type
Comment
101
Enter
Document
Date
Document Date
Delivery Note
in Header
Vendor
Vendor
Posting Date
Posting date
Bill of lading
Bill of lading
Grayed out
Header text
Version
Material tab
Grayed out
Quantity
defaulted from
Purchase Order
Quantity in unit of
entry
Qty in
delivery note
Quantity in delivery
note
Movement type
Stock type
Stock type
Plant
Plant
Storage
location
Storage location
Goods
Recipient
Goods Recipient
Unloading
point
Unloading point
Text
Text
Purchase Order
Del.
completed
ind.
Delivery completion
indicator
Defaulted by system if PO
Qty = GR Qty
Grayed out
Grayed out
Vendor name
For this material batch management is not active. Just for reference purpose the following
data is given.
Select Batch tab in Detail data.
Version
You will get Excise Invoice tab at Header Data for capturing vendor excise invoice details and for posting
Part I and Part II.
8. On the Excise Invoice tab at Header Data make the following entries.
Version
Field name
Description
R/O/C
Comment
Capture &
Post Excise
invoice
Defaulted
Excise Group
Excise Group
Excise
Invoice
Excise invoice
Excise Inv.
Date
BED
Grayed out
AED
Grayed out
SED
Grayed out
NCCD
NCCD
Grayed out
ECS
Education Cess
Grayed out
Chapter ID of material
EI Quantity
Excise Invoice
Quantity
Base Value
BED
AED
NCCD
NCCD
SED
ECS
Education Cess
Please cross check the BED, ECS (CVD in this case) amount of item as per the bill of lading,
legally you can not avail more than what mentioned in Vendor Excise Invoice.
In case of imported purchase order in normal case system will default CVD and ECess (invoice
verification made on commissioner of customs) amount as BED and ECS i.e. CENVAT amount.
Version
2.6.3
Result
2.6.4
Example
Version
2.7
Version
2.7.1
Use
In this process of Logistics Invoice Verification all the Incoming Invoices are verified in terms of their
content, prices and arithmetic. When the invoice is posted, the invoice data is saved in the system. The
system updates the data saved in the invoice documents in Materials Management and Financial
Accounting.
2.7.2
Procedure
MIRO
2. If you are opening for the first time this transaction, system will ask for Company Code, please give 1000 to
go in side the transaction.
3. On the Enter Incoming Invoice: Company Code 1000 screen, make the following entries:
Version
Select Goods
/Service Items
Field name
Description
R/ O/ C
Transaction
Invoice
Header Data
Defaulted by system
Basic tab
Invoice Date
Invoice Date
Reference
Invoice reference
Posting date
Posting Date
Comment
Invoice Amount
Currency
Tax code
Bus.place/se
ctn
Business place or
section code
Text
Text
Payment tab
Payment tab
BaselineDt
Pmnt terms
Payment terms
Payment terms of
document, if entered will be
defaulted from purchase
order
Due on
Payment due on
Will be calculated by
system
Discount
Cash discount
Calculate tax
Version
Amount
mentioned is
only an example
Will be defaulted
if payment terms
entered in PO
Grayed out
Purchase order
number
Defaulted for
user
Defaulted
Layout of invoice
verification
Version
Ensure that the Balance is ZERO before posting the document and the traffic light is green or yellow color.
6. If you want to see the accounting postings in simulation mode, Choose Simulation on middle of fourth row
of your screen.
Version
7. Choose Display Currency which will lead to small pop-up window having the company code currency and
Document Currency, position the cursor on the INR to convert to Document Currency and press the details
button.
Version
2.7.3
Result
2.7.4
Example
Version
Version
3.1.2 Prerequisites
The following scenario specific master data must be created for operation of this building block and
subsequent dependent building blocks.
Material Master record (Refer User Manual Procurement of Stock Materials (Domestic))
Vendor Master record (Refer User Manual Procurement of Stock Materials (Domestic))
CIN Master Data (Refer User Manual Procurement of Stock Materials (Domestic))
o
o
Chapter IDs
Material ID and chapter ID combination (Ensure Sub-Contract check box is selected for
CENVAT Determination
Vendor Excise Details
Excise Indicator for Plants
Excise Indicator for Plant and Vendor
Excise Tax Rates
Version
3.2.2 Prerequisites
Components stock should be available for providing to subcontracting vendor.
3.2.3 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Logistics Materials Management Purchasing Purchase
Order CreateVendor/Supplying Plant Known
ME21N
Transaction code
Version
Version
After filling the above data, choose on Material Data tab at item Details screen. There you will find a new icon
called Components, you have to choose on that icon to give the components list which you are likely to transfer
post to vendors and give the flowing inputs.
3. Click on the Components or Explode BOM and enter the materials that had to be sent:
Version
Version
3.2.4 Result
A message will be displayed stating that the purchase order was saved, with the purchase order
number.
3.2.5 Example
Standard PO created under the number 2400000000
Version
3.3.2 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Logistics Materials Management Purchasing Purchase
Order Messages Print/Transmit
ME9F
Transaction code
3. Choose
to Execute.
4. On screen Message Output select the appropriate Document number and perform the following:
Version
Version
3.4.2 Prerequisites
Sufficient stocks of components should be available for making transfer posting.
3.4.3 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Logistics Materials Management Inventory Management
Goods Movement Transfer posting
MB1B
Transaction code
2. On the Enter Transfer Posting: Initial Screen, make the following entries:
Field name
Document
Date
Posting Date
Movement
Type
Plant
Storage
Location
Description
Document Date
R/ O/ C
R
Posting Date
Movement Type
R
R
Input date
541
Plant
Storage location
R
R
1000
1010
Comment
Version
3.
Choose on To Purchase Order icon on the top of the screen or choose F9 on key board. System will
give new popup screen asking for purchase order number. Give the 45000000## purchase order
number and choose enter to continue.
4.
5.
6.
7.
8.
3.4.4 Result
A message will be displayed stating that the document posted.
Version
Version
3.4.5 Example
Material document 4900000039 posted.
3.5.2 Prerequisites
Select the Sub-Contracting Material in Material and Chapter ID Combination of the Excise
Master (J1ID) for the sending Material.
Ensure that the details of the receiving Material maintained in the Excise Master (J1ID).
CENVAT Determination of the Excise Master (J1ID) Maintained for the both sending and
receiving Material.
Ensure that the Assessable value for the sending material is maintained in the Excise Master
(J1ID)
3.5.3 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP User menu
Indirect Taxes Procurement
CIN Menu
Subcontracting Challans Create
Transaction code
J1IF01
Subcontracting
Version
3.
Description
Material document number
Material document year
Excise Group
Series Group
R/ O/ C
R
R
R
R
Comment
Appropriate
Appropriate
Appropriate
Choose Enter to continue, system will take new Subcontracting Challan Create screen, make the
following entries:
Field name
Select Posting tab
Posting date & time
Description
R/ O/ C
Print Immediately
Preprinted number
Comment
4.
3.5.4 Result
A message will be displayed stating that the document posted.
3.5.5 Example
Subcontracting Challan 000010001 2008; Series Group B1 successfully created.
Version
3.6
Version
3.6.1 Use
It is statutory requirement to send the components to subcontractor with 57F4 Challan.
3.6.2 Procedure
Access the transaction choosing one of the following navigation options:
SAP User menu
Indirect Taxes Procurement
CIN Menu
Subcontracting Challans Change
Transaction code
J1IF11
Subcontracting
Version
Press Enter
Version
Version
Version
3.7.2 Prerequisites
Purchase Order
3.7.3 Procedure
9. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Logistics Materials Management Inventory Management
Goods Movement Goods Receipt For Purchase Order
PO Number Known
Transaction code
MIGO
10. On the Goods Receipt Purchase Order screen, make the following entries:
11. After pressing Enter system will fetch all the data from the Purchase Order as shown below:
Version
13. System defaults the balance quantity in PO, change the quantity to the received quantity if it is different from
defaulted quantity:
Version
Version
Select Item Ok
and
Version
Field name
Description
R/ O/ C
Goods
Receipt
Goods Receipt
Purchase
Order
Purchase Order
Movement
Type
Version
Comment
101
Enter
Document
Date
Document Date
Delivery Note
in Header
Vendor
Vendor
Posting Date
Posting date
Bill of lading
Bill of lading
Header text
Header text
Grayed out
Version
Material tab
Grayed out
Quantity
defaulted from
Purchase Order
Quantity in unit of
entry
Qty in
delivery note
Quantity in delivery
note
Movement type
Stock type
Stock type
Plant
Plant
Goods
Recipient
Goods Recipient
Unloading
point
Unloading point
Text
Text
Purchase Order
Del.
completed
ind.
Delivery completion
indicator
Defaulted by system if PO
Qty = GR Qty
Grayed out
Grayed out
Vendor name
For this material batch management is not active. Just for reference purpose the following
data is given.
Select Batch tab in Detail data.
Batch number
Vendor batch
Vendor batch
15. Select the Check box Item OK, after entering all the data.
NCCD
NCCD
SED
ECS
Education Cess
Please cross check the BED, AED, SED, NCCD and ECS amount of item as per the Vendor
Excise Invoice, legally you cannot avail more than what mentioned in Vendor Excise Invoice. All
other information is defaulted by the system. Hence, no action required by the user.
Version
3.7.4 Result
Material document posted.
3.7.5 Example
Material document 5000000028 posted, You can see accounting Entries
Version
Version
3.8.2 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP User menu
Indirect Taxes Procurement Subcontracting
CIN Menu
Subcontracting Challans Reconcile Quantity
Transaction code
J1IFQ
As we have refered challan During Goods receipt here we are getting following message, If you have not refred
challan during Gr following is the Process
Version
2. On the Quantity reconciliation for Subcontracting Challan screen, make the following entriees.
Field name
Description
R/ O/ C
User action
values
Material Document
Goods Receipt
number
5000000344
Year of document
2006
Year
2006
Chalan No
Subcontacting challan No
000000031
document
and
Comment
5. Here you need to allocate the components consumed in GR stage are reconciled with challan to do this,
choose on Allocate based on FIFO icon in the middle of screen with calculator icon.
6. Or you can do allocation by entering manually also in respective line items at bottom, where Assigned
quantity filed is located in white color.
3.8.3 Result
Material document was successfully reconciled.
3.8.4 Example
Material Document 5000000028, 2008 was successfully reconciled.
Version
Version
3.9.2 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP User menu
Indirect Taxes Procurement Subcontracting
CIN Menu
Subcontracting Challans Complete/Reverse/Recredit
J1IF13
Transaction code
Description
R/ O/ C
Chalan No
Subcontacting challan No
0000000031
Excise year
Document year
2006
Comment
Version
3.9.3 Result
Subcontracting challan successfully completed.
3.9.4 Example
Subcontracting Challan 0000001 2008; Series Group B1 successfully completed.
3.10.2 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Logistics Materials Management Logistics invoice
Verification Document Entry Enter Invoice
Transaction code
MIRO
2. If you are opening for the first time this transaction, system will ask for Company Code, please give 1000 to
go in side the transaction.
3. On the Enter Incoming Invoice: Company Code 1000 screen, make the following entries:
4. Choose only the Subcontracting material to post the document:
Version
Field name
Description
R/ O/ C
Transaction
Invoice
Header Data
Defaulted by system
Basic tab
Invoice Date
Invoice Date
Reference
Invoice reference
Posting date
Posting Date
Amount
Invoice Amount
Amount
mentioned is
only an example
Currency
Comment
Version
Tax code
Bus.place/se
ctn
Business place or
section code
Text
Text
Payment tab
Payment tab
BaselineDt
Pmnt terms
Payment terms
Payment terms of
document, if entered will be
defaulted from purchase
order
Due on
Payment due on
Will be calculated by
system
Discount
Cash discount
Will be defaulted
if payment terms
entered in PO
Grayed out
Layout
Purchase order /
Schedule Agreement
Purchase order
number
Layout of invoice
verification
Defaulted for
user
Defaulted
Version
6. To check the document credit and debit is balanced on the top right corner of your screen a traffic light is
displayed. Beside that Balance of the document is displayed.
Ensure that the Balance is ZERO before posting the document and the traffic light is green or yellow color.
7. If you want to see the accounting postings in simulation mode, Choose Simulation on middle of fourth row
of your screen.
3.10.3 Result
Logistics Invoice verification document is posted.
3.10.4 Example
Document no. 5105600132 created, Account postings are following
Version
Version
5.1.2 Prerequisites
The following scenario specific master data must be created for operation of this building block and
subsequent dependent building blocks.
Version
5.2.2 Procedure
8. Access the transaction choosing one of the following navigation options:
SAP R/3 Menu
Logistics Materials Management Service Master Service
Service Master
Transaction code
AC03
10. Click on Create new service icon or press F5 (white paper icon) to create new service master.
11. Then you will get Create Service Master Record screen, make the following entries:
Version
Field name
Description
R/ O/ C
Comment
Service
Number
Leave blank
Service description
Service
Category
Service Category
Base unit of
Measurement
Base unit of
Measurement
Basic Data
Mat/srv.grp
Material Group or
Service Group
91
Division
Division
Valuation
class
Valuation class
3200
Long Text
5.2.3 Result
Service Master Record is created.
Version
Use
A Purchase Requisition is created to indicate purchase department to procure materials or services with
details like how much quantity is required, when required. Generally it is created automatically for Raw
materials and Packing Materials through MRP Run and Spares and Service related to Plant
Maintenance Purchase Requisition is generated automatically from Plant maintenance Order. In this
process Purchase Requisition is created against Quantity Contract created in above step 1.1.4 with
exact delivery / requirement date.
This transaction is optional for the process.
5.3.2
Procedure
Transaction code
ME51N
Enter the
Short Text
Version
Version
4. After pressing enter system shows a small pop-up window where respective G/L Account and Cost Center
to be entered.
Version
5. Press
Version
5.3.3
Result
5.3.4
Example
Version
Version
Use
c) This section explains the functions provided by the SAP System for converting requisitions into
external purchasing documents (purchase orders, contract release orders, scheduling agreement
delivery schedules, RFQs), and the processing options thereby available to you:
Assigning means defining the desired source for each purchase requisition item
o Further processing involves generating lists of requisitions that have been assigned or flagged as
outlined above, and the subsequent creation of RFQs, purchase orders, or lines of delivery
schedules under scheduling agreements.
5.4.2
Procedure
7. The assignment of sources to and further processing of purchase requisitions are two distinct functions.
You can choose whether you wish to perform the functions in two separate steps or in just one.
9. Press
1. If Source List is
available click this button
Version
Version
Version
5.4.3 Result
The source is assigned to PR and can be processed for PO.
5.5. For Releasing Purchase Requisition Refer User Manual for Stock Procurement
Version
Please ensure that Purchase Order Value does not exceed specified value and if the purchase order value
crosses this limit a release procedure is applied on this purchase order. To release the Purchase Order go
to ME28 for collective release and ME29N for individual release.
5.6.2 Prerequisites
1. Before creating purchase order if this vendor is subject to Tax Deduction at Source (TDS) or with
holding tax please ensures that necessary entries in vendor master is updated.
5.6.3 Procedure
6. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Logistics Materials Management Purchasing Purchase
Order CreateVendor/Supplying Plant Known
ME21N
Transaction code
7. If you want create purchase order with reference to the purchase requisition, on item details screen enter
the purchase requisition number and item number at Purch. Req. field. System will automatically adopt all
the data from requisition.
Click the
Purchasing
Requisitions
and Press
Adopt
Version
Condition Record for JSVD and JEC4 should be Maintained in FV11 with Material Group/Plant
Combination.
Select
Invoice
tab
Tax code
S1
Select S1 tax
code
Since the procurement services covered with service tax of 10% (for example only, check for
legal requirement), it is advised to select V1 tax code.
Jurisdiction
Jurisdiction code
R
Will be defaulted from plant
Version
parameters
Depending on for which plant you are procuring the services system will select Jurisdiction
code. In system the following Jurisdiction codes were configured IN00 Central
GR-based IV Goods Receipt based
O
Tick this check box
invoice verification
Srv.-based IV Service based invoice
O
Tick this check box
If Invoice
verification
Verification will
be done after the
Service Entry
sheet
8. The Purchase Order may be posted by Choosing on the Save button or Choose Control + S for saving.
5.6.4 Result
Purchase Order is created.
5.6.5 Example
Standard PO created under the number 4500000062.
5.7 For Releasing Purchase Order Refer User Manual of Stock Procurement
5.8 Message Output
5.8.1
Use
5.8.2
Procedure
14. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Logistics Materials Management Purchasing Purchase
Order Messages Print/Transmit
Transaction code
ME9F
Version
16. Choose
to Execute.
17. On screen Message Output select the appropriate Document number and perform the following:
Version
Use
Version
Version
The services actually performed (work actually done) by a service vendor are recorded in a Service
Entry Sheet with reference to the purchase order.
5.9.2
Procedure
ML81N
3. Click on Other Purch. Orders icon or Shift + F5, system will popup new screen.
Version
4. In this screen against Purchase Order field give the purchase order number which is created in above steps
and press enter to continue.
Version
8. System will give a popup screen with purchase order number on that, press enter to continue.
Version
9. Select the line item 10 and click on Services or F9 (Adopt services) icon on top of screen.
Version
Version
Version
11. You can observe the system copied the service line item from purchase order with open item quantity i.e. 1
AU.
Version
Version
13. With this the basic information of service entry sheet is fully completed. As per the requirement you can fill
other fields also if required.
14. To accept the service click on Accept icon or Control + F1 (Green flag icon).
15. You can see the traffic light is become Yellow color. That means it is ready to save the service entry sheet.
Version
16. Press
5.9.3
Result
A message indicates that the service entry sheet saved, acceptance document posted.
5.9.4
Example
Version
Version
Use
In this process of Logistics Invoice Verification all the Incoming Invoices are verified in terms of their
content, prices and arithmetic. When the invoice is posted, the invoice data is saved in the system. The
system updates the data saved in the invoice documents in Materials Management and Financial
Accounting.
5.10.2
Procedure
MIRO
2. If you are opening for the first time this transaction, system will ask for Company Code, please give 1000 to
go in side the transaction.
3. On the Enter Incoming Invoice: Company Code 1000 screen, make the following entries:
Version
Field name
Description
R/ O/ C
Transaction
Invoice
Header Data
Defaulted by system
Basic tab
Invoice Date
Invoice Date
Reference
Invoice reference
Posting date
Posting Date
Amount
Invoice Amount
Amount
Comment
Tax code
Bus.place/se
ctn
Business place or
section code
Text
Text
Payment tab
Payment tab
BaselineDt
Pmnt terms
Payment terms
Payment terms of
document, if entered will be
defaulted from purchase
order
Due on
Payment due on
Will be calculated by
system
Discount
Cash discount
Calculate tax
Version
mentioned is
only an example
Will be defaulted
if payment terms
entered in PO
Grayed out
Layout
Purchase order /
Schedule Agreement
Purchase order
number
Layout of invoice
Defaulted for
user
Defaulted
Version
Ensure that the Balance is ZERO before posting the document and the traffic light is green or yellow color.
6. If you want to see the accounting postings in simulation mode, Choose Simulation on middle of fourth row
of your screen.
5.10.3
Result
5.10.4
Example
Version
Version
Prerequisites
1. Before creating purchase order if this vendor is subject to Tax Deduction at Source (TDS) or with holding tax
please ensures that necessary entries in vendor master is updated.
2. Asset Management Module Active.
6.1.2 Procedure
7. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Logistics Materials Management Purchasing Purchase
Order CreateVendor/Supplying Plant Known
ME21N
Transaction code
Enter Account
Assignment A
and Short text of
the Assest
Enter PO Qty,Net
Price,Currency,
Material Group
Enter Code V1
Version
Version
Version
6.1.3 Result
Purchase Order Created with No. 230000000.
Version
Version
6.3.3 Prerequisites
Purchase Order
6.3.4 Procedure
16. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Logistics Materials Management Inventory Management
Goods Movement Goods Receipt For Purchase Order
PO Number Known
Transaction code
MIGO
Version
6.2.3 Result
Material Document 500000029 Posted.
J1IEX
Version
Version
Click Continue
6.4.2 Result
Excise Invoice Posted.
Version
Version
6.5.2 Procedure
4. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Logistics Materials Management Logistics invoice
Verification Document Entry Enter Invoice
Transaction code
MIRO
Click Simulate
Version
Click Save.
Version
6.5.3 Result
Invoice Document 5105600133 Posted.
Version
Version
Utilization of CENVAT
Proforma for Monthly Return under Rule 7 of the Cenvat Credit Rules, 2001
7.1.2 Prerequisites
Before execute business scenarios, you need to post the business processes transactions from other
scenarios.
As part of the integrated scenario, this scenario needs several User Manuals as prerequisites to
demonstrate these include:
Version
7.2.2 Prerequisites
User must be assigned the Indian Localization menu.
7.2.3 Procedure
9. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Country India User Menu Indirect Taxes Registers
Excise Tax CENVAT Register
Transaction code
J2I9
10. On the Proforma for Monthly Return Under Rule 57AE of the Central Excise Rule screen, make the
following entries:
R/ O/ C
Version
Field name
Description
Comment
Company
Code
Company code
1000
Excise Group
10
Posting Date
Annexure
Output to be
generated Annexure
or Abstract
Abstract
Output to be
generated Annexure
or Abstract
Inputs
Annexure to be
generated for Input
materials or Capital
Goods
Capital
Goods
Annexure to be
generated for Input
materials or Capital
Goods
Version
11. The out put can be saved into a local file or printed by using the print options.
7.2.4 Result
You are able to generate Proforma for Monthly Return Under Rule 57AE of the Central Excise Rule.
7.3
Version
7.3.2 Prerequisites
To extract the data to RG1 Register, Material numbers has to be maintained in the table J_2IRG1BAL
- Opening/Closing balance table for RG1.
7.3.3 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Country India User Menu Indirect Taxes Registers
Excise Tax Update RG23A/C Issues and RG1
Transaction code
J1I5
Version
2. On the Update of Registers RG1 and RG23(Part1) screen, make the following entries:
Field name
Description
R/ O/ C
Comment
Version
values
Company
Code
Company Code
1000
Plant
1000
Excise Group
10
Material
Document
Number
Material document
number
Document
Year
Material document
year
Posting Date
Date of Material
document Posted
Movement
Type
Storage
Location
Material
Material number to
update the RG1
Register
Document
Date
Batch
Stock Type
Rule
Excise Classification
Rule
Classification
Pre-defined
Classifications
IIM
For updating of
goods receipts
from
Manufacturing
plant use RMA
For updating of
Goods issue,
i.e. Removal
from factory on
payment of duty
for home use
Receipts
RMA- Receipt from
manufacture
ROP-Receipt from
outside under any other
provision
Issues
IDH-Removal from
factory on payment of
duty for Home use
IDE-Removal on
payment of duty for
Version
IDH
RG23/ RG1
Select the
appropriate radio
button to update
the RG1
Register. Please
select the
document entry
date radio button
Date to be considered by
the system for updation of
RG1 Register
Document Entry date
Document posting date
System date
Registers
Register to update
Select the
RG23A radio
button to update
the RG1
Register,
IIM
ROP
IPD
IWD
RG23C
IIM
ROP
IPD
IWD
RG1
IDH
RMA
IDE
ROP
3. System will display the Update of Registers RG1 and RG23 (Part1) screen:
Displays all the line items to meet the selection criteria to update the RG1 Register.
4. Select the line items which needs to be updated to RG1 Register by selecting the check box at the
beginning of the each line item
Version
Press Simulate
5. Simulate the selection by using the Simulate function or use Shift+F10 to simulate the selection
Version
Version
6. System will display the selection Green or Red Traffic lights. The line items which can be updated will be
displayed with Green Traffic Lights and the line items which can not be updated will be displayed with Red
Traffic Lights.
7. After selecting the right documents select the line item and use the Create button to update the RG1
Register or use CTRL+Shit+F11 to make register entry.
7.3.4 Result
Processing over for <number of records selected> records
Version
7.4.2 Prerequisites
You have to complete the update of RG1 Register before performing this step.
7.4.3 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Country India User Menu Indirect Taxes Registers
Excise Tax Extract
Transaction code
J2I5
Choose Execute
Version
Field name
Description
R/ O/ C
Excise Group
10
State Date
Starting date of
Extraction
End Date
Ending date of
Extraction
Selection
Registers
Mass extraction of
data to all registers
Select
individual
Registers
Selection of individual
register
Display Last
Extracted
dates
Displays the
previously upto what
date the register has
been extracted for
information
Version
Comment
User can
generate all the
registers
together or
individual
register wise
Version
4. If the RG1 Register is being generated for the Period First Time, system will execute the report and
display the pop-screen with Register name and Green Tick mark, if it is successfully extracted,
otherwise it will show the Red Cross.
Version
7.4.4 Result
RG1 data has been extracted
Using this activity, you can also extract the following Excise Registers in addition to RG1.
RG23A Part I
RG23A Part II
RG23C Part I
RG23C Part II
PLA
In the Registers select option, if you select All registers, the system will create an extract for all registers. If you only
want to create an extract for specific registers, select Select any register and then the registers that you want to
extract.
Version
7.5.2 Prerequisites
The data must be extracted to the RG1 Register for the period to which RG1 Register need to be
printed.
7.5.3 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Transaction code
J2I6
2. On the Print Excise Registers screen, select the RG1 Radio button to print the RG1 Register.
Choose
Version
Choose
Field name
Description
Excise Group
Start Date
End Date
R/ O/ C
Comment
10
For example
01.09.2005
Starting Date
For example:
29.09.2005
Ending Date
6. System will display the Print parameters maintenance screen assign the out put device name and select the
Print Preview option. System will display the output on the screen.
Version
7. See the output on the screen and based on the requirement print the output using Ctrl + P option or through
menu Text Print.
Version
7.5.4 Result
RG1 Register ready to print or you can see on the screen.
Using this activity, you can also view or print the following Excise Registers in addition to RG1
RG23A Part I
RG23A Part II
RG23C Part I
RG23C Part II
PLA
You have to print or see the registers one after another.
8.1.2 Prerequisites
The following process has been executed, if any transactions took place during the period of PLA
register extraction for payment of CENVAT and Sale of goods
8.1.3 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Country India User Menu Indirect Taxes Registers
Excise Tax Extract
Transaction code
J2I5
Version
Choose
Field name
Description
R/ O/ C
Excise Group
10
State Date
Starting date of
Extraction
End Date
Ending date of
Extraction
Selection
Registers
Mass extraction of
data to all registers
Select
individual
Registers
Selection of
individual register
Display Last
Displays the
Comment
User can
generate all the
registers
together or
individual
register wise
System will
previously upto
what date the
register has been
extracted for
information
Version
4. If the PLA Register is being extract for the Period First Time, system will execute the report and display the
pop-screen with Register name and Green Tick mark, if it is successfully extracted, otherwise it will show
the Red Cross.
Version
8.1.4 Result
PLA data has been extracted
8.2.2 Prerequisites
The data must be extracted to the PLA Register for the period to which PLA Register need to be
printed.
8.2.3 Procedure
1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu
Country India User Menu Indirect Taxes Registers
Excise Tax Print Utility program
Transaction code
J2I6
2. On the Print Excise Registers screen, select the PLA Radio button to print the PLA Register.
Version
Choose
Choose
Field name
Description
Excise Group
Start Date
End Date
R/ O/ C
Comment
10
For example
01.09.2005
Starting Date
For example
30.09.2005
Ending Date
Version
6. System will display the Print parameters maintenance screen assign the out put device name and select the
Print Preview option. System will display the output on the screen.
7. See the output on the screen and based on the requirement print the output using Ctrl + P option or through
menu Text Print.
8.2.4 Result
PLA register displayed on screen or printed.
9. Reports
7.1
Purchasing
7.1.1 Purchasing Documents per Vendor (ME2L)
Version
Choose Execute
Version
Version
Version
Choose Execute
Version
Version
9.2
Inventory
Choose Execute
Version
Version
Version
Choose Appropriate
Input for your selection.
Version
Version
Version
Version
Version
Version
Version