RTP - 105 Purchase To Stock (Import) - TRAIN
RTP - 105 Purchase To Stock (Import) - TRAIN
Business Scenario
Course
Training Guide
April 24
COPYRIGHT & TRADEMARKS
Document Name:
Table of Contents
RTP - 100 Purchase to Stock.......................................................................................1
ME57 - Assign and Process Purchase Requisitions from MRP........................................1
ME9F - Print Purchase Order...........................................................................................10
MIGO - Goods Receipt with Reference to a PO..............................................................22
MIRO - Match Invoice to Purchase Order......................................................................35
F110 - Create Payment Proposal.......................................................................................43
MRBR - Release Blocked Invoice......................................................................................66
F110 - Create and Execute Payment Run.........................................................................70
ZMM_05 - Purchase Order Status and Approver Details Report.........................................82
Page iii
Training Guide
Document Name:
Purpose
This transaction is used to assign and process purchase requisitions that have been
automatically generated via MRP. The purpose is to generate MRP order
recommendations and convert them into physical orders.
Pre-requisites
- MRP has been run
- A purchasing info record must exist for the material / vendor combination
- Source lists have been created, where required
Menu Path
Logistics > Materials Management > Purchasing > Purchase Requisition > Follow-On
Functions > Assign and Process
Transaction Code
ME57
Page 1
Training Guide
Document Name:
Step Action
1. Enter the transaction code into the Command field.
Step Action
3. Enter the type of purchase requisitions to be included in the MRP run
into the Scope of List field.
Page 2
Training Guide
Document Name:
Step Action
7. Click the Assignments button to display purchase requisitions by
vendor.
8.
This screen displays both the purchase requisitions that have already
been assigned a vendor, and the purchase requisitions that are
unassigned.
10. Click the PReqs per Assignment button to display all the unassigned
purchase requisitions.
Page 3
Training Guide
Document Name:
Step Action
14. You can review further details and change the purchase requisition
quantity and delivery date, if required.
Page 4
Training Guide
Document Name:
Step Action
15. When you are ready to manually assign the vendor, click the checkbox
to select the purchase requisition.
Page 5
Training Guide
Document Name:
Step Action
17. Enter the vendor into the Fix. Vend. Field.
Page 6
Training Guide
Document Name:
Step Action
19. The purchase requisition has now been assigned a vendor.
20.
Page 7
Training Guide
Document Name:
Step Action
24. Click the Continue button.
Page 8
Training Guide
Document Name:
Step Action
25. The list of purchase requisitions for the selected vendor are displayed.
27.
The purchase requisition details default into the purchase order screen.
Click on Invoice Tab and Enter/Check the Tax Code should be V0. Now
click on conditions Tab and check the Custom Duties. You should
check the details and make changes, as required. You can change
anything that is in a white field. Grey fields cannot be changed.
SAP will prompt you to enter any fields that require data.
Page 9
Training Guide
Document Name:
Step Action
28.
If there are messages, they will display in a dialogue box as per the
following:
30.
A green tick displays next to the purchase requisition that has been
converted into a purchase order. Repeat for all remaining purchase
requisitions.
31. Click the Exit button.
32.
Page
10
Training Guide
Document Name:
Step Action
33. Click the Exit button twice.
34. Result
You have successfully assigned and processed a purchase requisition
from MRP.
Next Step
An email is sent via workflow to the designated approver, with a
hyperlink to allow easy access to the approval screen within the portal.
Purpose
Use this transaction to transmit a purchase order. Purchase orders can either be
printed, then forwarded to the vendor, or emailed direct. This will depend on the
arrangement with the vendor.
Pre-requisites
The purchase order must have been approved. Purchase orders cannot be
transmitted prior to approval.
Page 11
Training Guide
Document Name:
If the purchase order is being emailed, there must be an email address set up in the
vendor master record.
Restrictions
You can only email a purchase order to a primary vendor. Purchase orders cannot be
emailed to ordering address vendors.
Menu Path
Logistics > Materials Management > Purchasing > Purchase Order > Messages >
Print/Transmit
Transaction Code
ME9F
Step Action
1. Enter the transaction code into the Command field.
Page
12
Training Guide
Document Name:
Step Action
3.
If you want to transmit multiple purchase orders, you can either enter a
range of purchase order numbers, if the numbers are sequential, or use
the Multiple selection button to enter the individual purchase order
numbers.
The Processing Status defaults to "0" for Not Processed. Leave the
default.
6. Click the Execute button.
Page 13
Training Guide
Document Name:
Step Action
7. Click the checkbox to select the purchase order.
Step Action
8. To view the purchase order prior to transmittal clicks the Display
Message button.
Page
14
Training Guide
Document Name:
Step Action
9. Once you have viewed the purchase order, click the Back button.
Step Action
10.
Purchase orders have been set up to print for all vendors. If you want to
print the purchase order, you would click the Output Message button.
Page 15
Training Guide
Document Name:
Step Action
11.
Changes to the print output via this transaction will only apply to this
instance. Changes to the vendor master record are made by the Master
Data Maintenance team.
In this example, you are going to change the message output to email.
12. Click the checkbox to select the purchase order again.
Step Action
13. To change the purchase order output from print to email, click the
Message Details button.
Page
16
Training Guide
Document Name:
Step Action
14. Click the Medium list.
Page 17
Training Guide
Document Name:
Step Action
15. Click the External send list item which will specify email as the output.
Page
18
Training Guide
Document Name:
Step Action
16. Click the Display Means of Communication button.
Page 19
Training Guide
Document Name:
Step Action
17. Enter the communication strategy into the Comm.strategy field.
Step Action
19. Click the Save button to save the changed message output.
Page
20
Training Guide
Document Name:
Step Action
20. Note: The system displays the message: Messages saved. You are
now ready to transmit the purchase order.
Page 21
Training Guide
Document Name:
Step Action
21. Click the Output Message button to transmit the purchase order.
Step Action
22.
In this instance, because the output is email, the system displays the
message MAIL request 000000000062 created successfully.
23. Click the Exit button twice to return to the SAP main menu.
Page
22
Training Guide
Document Name:
Step Action
24. Result
You have successfully transmitted a purchase order.
Next Step
If the purchase order is being printed, you can collect the purchase
order from the printer and fax it to the vendor. If the purchase order is
being emailed it will be automatically sent to the email address that is
specified in the vendor master record.
End of Procedure.
Purpose
This lesson explains how to enter an invoice to be matched against a purchase order
for payment of Custom Duties payable to Custom Dept. of India.
Menu Path
Logistics > Materials Management > Logistics Invoice Verification > Document Entry
> Enter Invoice
Transaction Code
MIRO
Page 23
Training Guide
Document Name:
Step Action
1. Enter the transaction code for Invoice Matching.
Enter MIRO.
2. Click the Enter button.
Step Action
3. The Transaction field defaults to Invoice.
Do not change.
4. SAP calculates the date the payment is due, based on the Vendor
payment terms, by reference to the invoice date.
Page
24
Training Guide
Document Name:
Step Action
5. Enter the invoice date into the Invoice date field.
SAP will check for double invoice entry using this field and the invoice
date.
7. Enter the vendor invoice number into the Reference field.
Page 25
Training Guide
Document Name:
Step Action
12. You now need to link to the associated purchase order to match against
the invoice.
Step Action
16. Enter the Breakup of custom duties and Quantities
Page
26
Training Guide
Document Name:
Step Action
17. Payment terms are displayed on the Header section for the invoice.
18. The details from the purchase order will display in the line item section.
Green indicator - This means that SAP has matched all purchasing
documents. You can post the invoice and payment will be made to the
Vendor. Note: Payment may still be blocked if the invoice is on the
Blocked Payments Exception List, or the Vendor has been blocked for
payment.
Page 27
Training Guide
Document Name:
Step Action
21. If the invoices displays a green or yellow indicator, you can post the
invoice by clicking the Save button.
However, for the purposes of this lesson, you will view a simulation
before posting.
22. You can simulate the postings before saving, if required.
This option is useful if you have a red indicator. It may help you to
identify errors in entry.
23. Click the Simulate Document button.
24. Posting information is displayed in this screen for you to review your
entries, if required.
Step Action
25. Click the Post button.
Page
28
Training Guide
Document Name:
Step Action
26. The invoice document number is displayed at the bottom of the screen.
28. Result
You have successfully entered an invoice in SAP against a purchase
order.
Next Steps
If the invoice is not blocked, it will be included in the next payment run
based on the Invoice date and Vendor payment terms.
Purpose
Use this transaction to receipt goods or services.
This example shows how to receipt goods or services against a purchase order,
although you use this same transaction when receipting goods with reference to a
production order.
- It is here that the business receives ordered consumables and stock from a
vendor into inventory.
- A receipt provides the authority to pay a vendor. The vendor's invoice is verified
using the quantity ordered and the quantity receipted (delivered).
- The purchase order's history is updated.
Generally, goods are receipted in by the Stores function on receipt of physical goods.
However, for the receipt of external services, it is the responsibility of the Purchaser
to contact the Store person, or forward any document they have received to indicate
completion of the service .Until the goods receipt is performed, Shared Services are
unable to pay the vendor.
The goods receipt transaction (MIGO, movement 101) allows for full or partial goods
receipt of materials received from a vendor against an existing purchase order.
Page 29
Training Guide
Document Name:
Partial goods receipt means that the quantity receipted is less than the quantity
ordered. The open order quantity (quantity still to be received) is displayed on the
purchase order line item. Any number of partial goods receipts can be recorded for a
purchase order line.
Pre-requisites
An open purchase order line item. Excise Master Data need to be maintained for
Vendor and Material.
Menu Path
Logistics > Materials Management > Inventory Management > Goods Movement >
Goods Movement
Transaction Code
MIGO
Step Action
1. Enter the desired information into the Command field.
Page
30
Training Guide
Document Name:
Step Action
2. Click the Enter button.
Step Action
3.
This example shows that the last goods movement transaction was a
Return Delivery.
4. Click the button to the right of the business transaction field.
Page 31
Training Guide
Document Name:
Step Action
5. Point to the Goods Receipt list item.
6. Click the Goods Receipt list item.
7.
Page
32
Training Guide
Document Name:
Step Action
8. Click the Reference Document list.
9.
Page 33
Training Guide
Document Name:
Step Action
11.
The system defaults to the last movement type used for the business
transaction.
12. Click the Enter button.
Page
34
Training Guide
Document Name:
Step Action
15. Enter the vendor's delivery docket number into the Delivery Note field.
Set the Print via Output Control indicator if you wish to print a goods
receipt/issue slip.
17.
Select the Collective Slip option from the Version for Printing GR/GI
Slip drop-down list to print a slip including all the items in a document
18. Click the Print via Output Control option.
19. Click the button to the right of the Version for Printing GR/GI
Slip field.
Page 35
Training Guide
Document Name:
Step Action
20. Point to the Collective Slip list item.
21. Click the Collective Slip list item.
Page
36
Training Guide
Document Name:
Step Action
23. Click the OK option.
24. Now you will be able to see a new TAB for Excise Invoice. Enter Excise
Invoice Number and Excise Invoice Date.
25. Check the CENVAT posting amount for BED, AED, ECS and SECS
which will flow from Custom MIRO
26.
You can check for errors in your transaction before posting it by clicking
on the Check button. Any errors/warnings will be displayed.
Page 37
Training Guide
Document Name:
Step Action
27. Click the Check button.
Page
38
Training Guide
Document Name:
Step Action
29.
31. Result:
After a goods receipt is posted:
Purpose
Use this transaction to Post Excise Invoice i.e. to Post the CENVAT Amount. After
receiving the excisable goods and capturing the Excise Invoice in MIGO the next
step is to Post the Excise Invoice captured during MIGO. It will update the Part 2 of
CENVAT register.
Menu Path
India Localization SAP Menu> Indirect Taxes > Procurement > Excise Invoice >
Incoming Excise Invoice > Central Processing> Post Excise Invoice
Transaction Code
J1IEX
Page 39
Training Guide
Document Name:
Step Action
32. Enter "J1IEX".
33. Click the Enter button.
Page
40
Training Guide
Document Name:
Step Action
38. Click on simulate CENVAT and check the CENVAT values
39. Check Excise Invoice Indicator must be Green
Page 41
Training Guide
Document Name:
Step Action
40. Click on Post CENVAT
41. Check the register Serial Number and Other Details
42. Press Continue
43. Result
Excise Invoice has been successfully posted
Next step
Logistics Invoice Verification
End of Procedure.
Purpose
This lesson explains how to enter an invoice to be matched against a purchase order
for payment.
Page
42
Training Guide
Document Name:
Note: SAP recognizes partial deliveries/ payments and can find a match based on
the goods receipt and invoice documents.
Tolerances
Blocking tolerances exist that allow posting where small differences exist. SAP will
match where there is a difference of the lesser of 1% or $50. These differences are
posted, by SAP, to the Small Differences GL account. The Cost Centre specified on
the line item with the difference will also be updated with the difference value.
Menu Path
Logistics > Materials Management > Logistics Invoice Verification > Document Entry
> Enter Invoice
Transaction Code
MIRO
Step Action
1. Enter the transaction code for Invoice Matching.
Enter MIRO.
Page 43
Training Guide
Document Name:
Step Action
2. Click the Enter button.
Step Action
3. The Transaction field defaults to Invoice.
Do not change.
4. SAP calculates the date the payment is due, based on the Vendor
payment terms, by reference to the invoice date.
Page
44
Training Guide
Document Name:
Step Action
5. Enter the invoice date into the Invoice date field.
SAP will check for double invoice entry using this field and the invoice
date.
7. Enter the vendor invoice number into the Reference field.
Note: Ensure the tax code used is correct. Error messages will result
from an incorrect tax code.
Page 45
Training Guide
Document Name:
Step Action
11. The Text field is used to enter relevant text onto the vendor remittance
advice.
15. If the purchasing officer has entered either pricing type or Terms of
Payment text in the purchase order, you will receive a pop up enabling
you to view the details by double clicking on a text type.
Page
46
Training Guide
Document Name:
Step Action
16. You can double click one of the line items to view the text.
Step Action
17. Details of the message are displayed.
Page 47
Training Guide
Document Name:
Step Action
19. Payment terms are displayed on the Header section for the invoice.
20. The details from the purchase order will display in the line item section.
If goods were partially received and invoiced before, then only the
outstanding number of items will be displayed in the line item section.
22. If the invoice you have received is different from the amount shown on
the line item screen, in terms of value and/or quantity, you must change
the amounts shown in the line item.
Note: The invoice may not cover all line items, if multiple items exist.
SAP will then match the invoice against the purchase order and goods
receipt documents.
Page
48
Training Guide
Document Name:
Step Action
25. Red indicator - This means that an entry error has occurred and you
cannot post the invoice. Check your entries.
Green indicator - This means that SAP has matched all purchasing
documents. You can post the invoice and payment will be made to the
Vendor. Note: Payment may still be blocked if the invoice is on the
Blocked Payments Exception List, or the Vendor has been blocked for
payment.
26. Value tolerances exist whereby payment will not be blocked for small
amounts.
27. If the invoices displays a green or yellow indicator, you can post the
invoice by clicking the Save button.
However, for the purposes of this lesson, you will view a simulation
before posting.
28. You can simulate the postings before saving, if required.
This option is useful if you have a red indicator. It may help you to
identify errors in entry.
29. Click the Simulate Document button.
30. Posting information is displayed in this screen for you to review your
entries, if required.
Page 49
Training Guide
Document Name:
Step Action
31. Click the Post button.
32. The invoice document number is displayed at the bottom of the screen.
34. Result
You have successfully entered an invoice in SAP against a purchase
order.
Next Steps
If the invoice is not blocked, it will be included in the next payment run
based on the Invoice date and Vendor payment terms.
Note: Some columns, such as Amount, are not captured in this screen shot.
Page
50
Training Guide
Document Name:
Procedure
Purpose
Use this transaction to determine the parameters for a payment run and create a
proposal.
The payment proposal displays a list of all invoices that are due to be paid, based on
the parameters entered. Each line item in the proposal provides an indication where
payment will be made (green indicator). Payments that are blocked are flagged with
a red indicator.
When the proposal is created, it can be saved as an HTML file, to be email to the
payments authorisor for the appropriate company. The authorisor should then
investigate blocked payments and take appropriate action. The proposal can also be
printed and reviewed. Additionally, authorisor's will review items with a green
indicator to confirm that payment is acceptable.
Prerequisites
Ensure that blocked invoices have been reviewed and unblocked where appropriate.
Menu Path
Accounting > Financial Accounting > Accounts Payable > Periodic Processing >
Payments
Transaction Code
F110
Page 51
Training Guide
Document Name:
Step Action
1. Enter the transaction code into the Command field.
Enter "F110".
2. Click the Enter button.
If you are preparing the proposal for the company to review, preparing
the payment run in advance is recommended.
Page
52
Training Guide
Document Name:
Step Action
4. Enter the date for the payment run into the Run Date field.
Using a Rail company code example, 1000A would be for the first
payment run that day (eg. EFT run). 1000B would be for the second
payment run on that day (eg. Cheque run).
If you need to perform another run on the same day, use the next alpha
character (C) for the Identification.
6. The combination of Run Date and Identification make the run IDs
unique.
Therefore, if you run a payment run for 1000 on a different day, you use
A, B, C etc again.
Examples:
1000A 08.11.2007
1000B 08.11.2007
1000A 15.11.2007
1000B 15.11.2007
1000C 15.11.2007
Page 53
Training Guide
Document Name:
Step Action
7. Enter the run Identification code into the Identification field.
Step Action
9. In the Parameter tab, you will determine the company and Vendor
range to be included in the payment run.
10. The posting date is the date the run will be posted.
This date can be different from the Run date and Posting date, if
required.
12. In this example, the Docs entered up to date will not be changed.
13. In the Payment control area, enter the company code into the
Company codes field.
Page
54
Training Guide
Document Name:
Step Action
14. The Pmt meths field is used to determine the payment method for this
payment run.
You can enter C for a cheque run, T for an EFT run or G for Global
(Foreign Currency) payment run.
15. Enter the payment method into the Pmt meths field.
The system will automatically select all invoices which are due before
the next payment date.
17. Enter the date for the next run into the Next p/date field.
For a one off payment, you should enter the Vendor code.
19. Enter the first Vendor number for the range into the Vendor field.
Enter "1".
20. Enter the last number in the range of Vendor codes into the to field.
Enter "69999999".
21.
Page 55
Training Guide
Document Name:
Step Action
23. This tab is used to exclude values.
For example, you may want to exclude specific Vendor numbers from
the payment run.
To exclude vendors, enter the vendor numbers into the Values field
and use a comma to separate multiple vendor numbers.
Page
56
Training Guide
Document Name:
Step Action
26. Click the Due date check option.
Page 57
Training Guide
Document Name:
Step Action
27. Click the Payment method selection in all cases option.
29. Enter the first Vendor number in the range into the Vendors (from/to)
field.
Enter "1".
30. Enter the last Vendor number in the range into the Vendors (from/to)
field.
Enter "69999999".
31. Click the Printout/data medium tab.
Page
58
Training Guide
Document Name:
Step Action
32. This tab is used to specify a Variant for the payment.
- payment method
- house bank
- bank account number
- print payment advice's (remittances)
- print payment summaries
- print immediately (EFT variants)
- do not print immediately (Cheque variants).
33. Note: Although the variant specifies to 'print', this is not necessarily a
physical 'print'. For example, remittances to Vendors will not print but
will be email or faxed (depending on the communication method in a
Vendor master record) immediately to a Vendor (as long as an email or
fax number is specified in the Correspondence section of a Vendor
Master Record).
Note: All printable outputs (not including EFT by email or fax) will be
available in a spool. This can be accessed and, for example, the
payment summary can be downloaded to an HTML file.
Note: For cheques, the remittance advice and the cheque is all
contained on one sheet.
Note:
- RFF0AU_T for EFT. For New Zealand users, your program for EFT
processing will displays RFFOAVIS_FPAYM.
- RFF0US_C for Cheque
- RFF0M100 for Global Payment.
36. Make sure that you select the variant for the company code you are
processing.
Page 59
Training Guide
Document Name:
Step Action
37. For this example, double-click the entry EFT_1000 in the Variant
column.
Page
60
Training Guide
Document Name:
Step Action
38. Click the Save button.
Step Action
41. Always return to the Status tab to perform the next stage in a payment
run.
The Status tab shows the status of the run in the Status section.
42. Now that payment parameters are entered, SAP provides options to
create the Proposal and Payment Run.
Page 61
Training Guide
Document Name:
Step Action
44. Click the Start immediately option.
47. The Status area now displays that the proposal is running.
This means that SAP is now searching for all due invoices based on the
parameters entered.
You can repeatedly click the Status button to update the status.
Use the Status button as many times as required until the proposal is
created.
Page
62
Training Guide
Document Name:
Step Action
48. Click the Status button.
49. When SAP has found all invoices due for payment, the message
Payment proposal has been created is displayed.
Page 63
Training Guide
Document Name:
Step Action
53. Click the Continue button.
54. The Payment Proposal lists all invoices found by SAP that are due for
payment.
Line items with a green indicator signify that payments will be made in
the payment run.
Line items with a red indicator signify that the master record or invoices
are blocked.
55. Foreign currency payments should remain blocked as payment will be
made manually by bank draft.
56. The Payment Proposal can be downloaded into an HTML file.
The file can then be email to the authorisor for the company, for
review/approval.
Page
64
Training Guide
Document Name:
Step Action
57. Click the drop down to the right of the Export button.
Page 65
Training Guide
Document Name:
Step Action
60. Click the Save in list.
62. Name the file so that it is obvious from the file name which payment run
the file belongs to.
63. Enter the name for the file into the File name field.
65. The file is now saved and can be accessed outside SAP from the
location in which it was saved.
Page
66
Training Guide
Document Name:
Step Action
66. Click the Back button.
67.
You have just learnt the process of displaying and downloading the
payment proposal list to a local drive.
You will now learn how to display and print the payment proposal list.
Page 67
Training Guide
Document Name:
Step Action
68. Click the Edit menu.
71.
Page
68
Training Guide
Document Name:
Step Action
72. Click in the Variant field.
Page 69
Training Guide
Document Name:
Step Action
73. Click the Search button.
74.
Step Action
76. Click the Continue button.
77.
In this example the added variant, ie. Reference column field also
displays.
Page
70
Training Guide
Document Name:
Step Action
78. Click the List menu.
80.
In this example the default printer displays in the Output Device field.
Page 71
Training Guide
Document Name:
Step Action
81. Click the Continue button.
82.
The Payment Proposal List has been printed, to your designated local
printer. The following message displays at the bottom of the task bar,
"Spool request (number XXXXXXXXXX) sent to SAP printer LOCL".
Page
72
Training Guide
Document Name:
Step Action
83. Click the Back button.
Page 73
Training Guide
Document Name:
Step Action
84. Click the Exit button.
85. Result
You have successfully created a payment proposal and saved the
payment proposal as an HTML file and/or printed.
Next steps
Email the payment proposal HTML file to the authorisor for the
company code/review the printed payment proposal.
Once the payment proposal has been reviewed and approved, you can
create the payment run.
End of Procedure.
Purpose
Use this transaction to release an invoice that was blocked for payment.
Over and above the three way matching block, UGL has defined additional invoice
blocking rules.
Exceptions can be set up by authorised users to block invoices under the following
conditions:
- Material group by company code
- $ Value by company code
- Vendor by project
- all purchase without a material master - switched on by company code.
To unblock an Invoice, you must select the Blocking Procedure by which it was
originally blocked as follows:
Blocked Due to Variance - Invoice Blocked Due to the three way matching
discrepancies.
Manual Payment Block - Invoices that have been manually blocked by the user or
Blocked by exception as defined above.
Prerequisite
An invoice has been blocked for payment.
Authorisation has been obtained from the business to unblock an invoice.
Menu Path
Logistics > Materials Management > Logistics Invoice Verification > Further
Processing > Release Blocked Invoices
Page
74
Training Guide
Document Name:
Transaction Code
MRBR
Step Action
1. Enter the transaction code into the Command field.
Page 75
Training Guide
Document Name:
Step Action
3. Enter the company code into the Company Code field.
For this example, the Vendor field is left blank. Therefore, the
transaction will list all blocked invoices for all Vendors in the company
code specified.
5. The Blocking Procedure section is used to specify how the release
will be managed.
Page
76
Training Guide
Document Name:
Step Action
8. Blocked invoices for the company code specified are displayed, based
on whether you selected Manual Payment Block or Blocked Due to
Variances.
Note: If you had specified a Vendor in the previous screen, all blocked
invoices for that Vendor only would be displayed.
Step Action
9. To select an invoice to be released click the Selection box to the left of
the invoice number.
Page 77
Training Guide
Document Name:
Step Action
11. A release flag displays for the invoice line item.
14. The screen message at the bottom of the screen displays the number
of invoices released.
17. Result
You have successfully released blocked invoices.
Page
78
Training Guide
Document Name:
Purpose
Use this transaction to create a payment run for vendor payments.
The steps to download the DME bank file are also demonstrated. The file is then
uploaded to the ANZ bank (via http://www.anzdirect.co.nz/#). The bank will then pays
the vendors via EFT.
Prerequisites
The Payment Proposal must have been created and reviewed by the paying
company.
Arrangements must have been made to authorise the bank to pay the vendors
electronically, based on the uploaded bank file.
Menu Path
Accounting > Financial Accounting > Accounts Payable > Periodic Processing >
Payments
Transaction Code
F110
Page 79
Training Guide
Document Name:
Step Action
1. Enter the transaction code into the Command field.
3. The last payment run processed may be displayed in the initial screen.
Step Action
4. Click Search button in the Run Date field.
Page
80
Training Guide
Document Name:
Step Action
5. Double-click the appropriate payroll proposal.
Page 81
Training Guide
Document Name:
Step Action
7. Click the Pmnt Run button.
Page
82
Training Guide
Document Name:
Step Action
8. Click the Start immediately option.
11. The Status area now displays that the payment run is running.
This means that SAP is now searching for all due invoices based on the
proposal entered.
You can click the Status button repeatedly to update the status.
Use the status button as many times as required until the payment run
is created and posted.
Step Action
12. Click the Status button.
13. The Status area is updated to show that the payment run was carried
out.
Page 83
Training Guide
Document Name:
Step Action
14. At this stage, the accounting entries have been posted in SAP.
Step Action
17. Overtype the question mark (?) at the end of the Job name in the Job
name field.
Page
84
Training Guide
Document Name:
Step Action
19.
Page 85
Training Guide
Document Name:
Step Action
22. Click the Table row select button.
Page
86
Training Guide
Document Name:
Step Action
24. Click the Search button, to select the path/drive, where the bank file is
to be saved.
25.
Page 87
Training Guide
Document Name:
Step Action
28. Click the Download button.
29.
The bank file has been saved to your designated local drive.
Page
88
Training Guide
Document Name:
Step Action
30. Click the Back button.
Page 89
Training Guide
Document Name:
Step Action
31. Click the Exit button.
32. Results
You have successfully created and executed a payment run. The
printing requirements are also scheduled.
Next Steps
Download the payment summary file to HTML and email the file to the
appropriate company.
Additionally, if this was a cheque run, you now need to print the
cheques.
Upload the bank file to the ANZ site, for the bank to process payments
via EFT, to vendors.
End of Procedure.
Purpose
Use this transaction to display Purchase Orders raised for a Project, to check the
status of the Purchase order and to review the Purchase order Approver details.
The Purchase Order Approver details are displayed for each level in the delegation of
authorities (depending on the value of the Purchase Order).
Pre-requisites
A Purchase Order has been raised and workflowed to an approver for approval.
Menu Path
UGL Reports & Transactions > RTP Requisition to Pay > Purchasing Reports >
Purchase Order Report
Transaction Code
ZMM_05
Page
90
Training Guide
Document Name:
Step Action
1. Click in the Transaction code field.
2. Enter the desired information into the Transaction code field. Enter
"ZMM_05".
3. Click the Enter button.
4.
Page 91
Training Guide
Document Name:
Step Action
5. Click the Vertical scrollbar.
6. Click the WBS Assignment ONLY option.
8. Enter the desired information into the Project Definition field. Enter
"5000-0165".
9. Click the Execute button.
10.
Page
92
Training Guide
Document Name:
Step Action
11. Click the Horizontal scrollbar.
12.
The following columns are displayed: Gross value, the General Ledger
account the Purchase Order has been assigned to, the WBS Element
coding, the delivery date for the goods and services.
15. Click the Horizontal scrollbar.
16.
The Quantity outstanding, the value outstanding , the invoice value and
date, the Approver Levels are all displayed.
17. Click the Horizontal scrollbar.
Page 93
Training Guide
Document Name:
Step Action
21. Click the Exit button.
Step Action
22. Click the Yes button.
Page
94
Training Guide
Document Name:
Step Action
23. Click the Exit button.
24. Result
The Purchase Order Status and Approver Details report has been
displayed.
End of Procedure.
Page 95