Purchase requests can be created via the order recommendation screen, via reservation list and other windows. This is the pre-stage to a purchase order or purchase offer.
In the purchase request window requirements are collected, for which no order has yet been created. These can still be changed before creating an order, a drafted order or an offer is generated.
You can use beas purchase request or SAP purchase request. You can define this in Configuration Wizard.
If you create a Purchase Order or Purchase Quotation from MRP window, beas create a beas purchase request and then automatically the related SAP document.
Call up from: Materials management > purchase request
Here you can see the description from beas purchase request variant
PATH: MRP > Purchase request.
Window: mrp_purchase_master
The purchase request screen is divided into three areas:
Up left: User In this area, all users who have created a purchase requests from the MRP run are displayed. If you only want to see purchase requests of specific users, remove the selection in "OK" column and all purchase requests of that user are hidden.
Up right: Supplier In this area, all suppliers are displayed for which there are purchase orders created by the selected user.
Below: mark suppliers to get items showed, for which a purchase request has been created
|
|
Item
|
Item ID
|
Price
|
Purchase price
|
Total
|
|
Menge
|
Purchased quantity
|
Purchase date
|
Requirement date less lead time
|
Requirement date
|
|
Lead time
|
Lead time from item master
|
Warehouse
|
Standard item warehouse
|
Approved
|
Settings from origin document apply
|
Lower window section
Details tab
In the Details tab, you can add further information to the purchase request and then create a purchase order or create a drafted document. Click the relevant button to do this.
|
|
Supplier
|
Supplier ID
|
Name
|
Supplier name
|
Contact person
|
Contact person at supplier
|
Supplier reference number
|
Optional
|
Purchaser
|
Who created the purchase request
|
Terms of delivery
|
Select from terms of delivery
|
Remarks
|
Free text, remarks are transferred to the SAP Business One document. To enter in rich Text format, enable this feature in window settings.
|
Warehouse
|
Target warehouse for purchase
|
Address
|
Free text
|
Entry remarks tab Enter comments
Closing remarks tab Enter comments
Right-click menu
Same functions as on buttons below. Additionally: window settings: there the RTF mode can be activated to enter formatted remarks.
Buttons:
|
|
New
|
Create a new purchase request.
|
Delete
|
Delete the selected purchase request.
|
Open
|
Open the selected request for editing, same function as double click on the entry in the list above.
|
Create purchase order
|
After a security query, whether to close the purchase request, for the selected entry a purchase order is created, and the SAP Business One document is opened.
|
Create Draft pur. order
|
For the selected entry a drafted order is created; in SAP Business One a drafted document is created.
|
Purchase quotation create
|
After creation, there is a query, to delete the purchase request. If no, you can use this for the next supplier.
As in SAP Business One only the supplier, date, item and quantity are transferred, but not the price.
|
|
Invent.History
|
Opens the Inventory history for the selected item.
|
The program creates the documents but they will not be shown immediately.
The created document will be opened after creation automatically, by inserting the following script:
Ctrl+N+U, insert script, save, reopen the window
windowevent open
setvar=ib_OpenDocument=true
end event
beas 9.2 PL: 04
|
In this window on row level up to 4 additional fields can be defined (see Configuration wizard).
In variable "is_secondfilter" an extended filter can be stored. Accessible is only the table "BEAS_MRP_ORDER"
Use the UserEvent "windowevent dw2inretrieve" to access variable "ls_sql". It can be modified, eg. you can determine userfield1 to userfield4. Template fields should not be used here, because these can be set to invisible. Use window settings to rename or set UDF visible or invisible.
Example:
Display "hello world" in userfield 1. Therefore, userfield1-sequence will be replaced.
windowevent dw2inretrieve
setvar=ls_replace=cast('' as nvarchar(50)) as userfield1
tools=globalreplace=ls_sql=<ls_replace>='hello world'
end event
(beas 9.1 PL: 07)
|
To adjust the item list, use event dw3initretrieve
Example:
Display "hello world" in userfield 1. Therefore, userfield1-sequence will be replaced.
windowevent dw2inretrieve
setvar=ls_replace=cast('' as nvarchar(50)) as userfield1
tools=globalreplace=ls_sql=<ls_replace>='hello world'
end event
(beas 9.1 PL: 07)
|
Transfer additional fields to a purchase order is possible only via script. See Customizations
Creating a PO row, the user-event "insertline" is called up. The object "porder" is available, to which the information can be transferred.
Example:
In rows-UDF U_myfirstfield and U_mysecondfield the content of udf1 and udf2 is to be saved.
Ctrl+N+U (opens the Script-window)
windowevent insertline
porder=line=U_myfirstfield=<dw_3.item.beas_mrp_order_udf1.value>
porder=line=U_mysecondfield=<dw_3.item.beas_mrp_order_udf2.value>
end event
Close the window and re-open it.
|
|
Window: mrp_purchase_master
beas9.0-000-001-004
Help URL: https://help.beascloud.com/beas202109/index.html?bestellanforderung2.htm
|