Prerequisites: All Client Computers Must Have .: Appendix

Network Installations
Appendix
Prerequisites: All Client Computers must have ….

l TCP/IP installed (network protocol)
l “Find Servers through DNS Services” (or entry in host file)
installed
l IP Addresses
l Regsvr32.exe (windows protocol)
l Must Purchase SQL Server Separately (MSDE is only
intended for single users or very small networks)
l Network Server installations must be run on the computer that
will hold the ASAP database and this computer must be
running SQL Server
Ë Client Location must purchase SQL Server separately Ë
(MSDE is only intended for single users or very small networks)
ã SAP AG 1999
n Client computers must have TCP/IP (network/internet protocol) installed and must be able to find the
Server through DNS (Domain Name Services) or through an entry in the hosts file. If this is not part
of the client computer’s network setup then the ClientSetup will be successful, but you will not be
able to run ASAP.
n To successfully run ASAP on a client PC, the network must support TCP/IP, and the Server
computer must be registered with the DNS service. If your network does not use DNS, or the ASAP
server is not registered in the DNS service then you must create an entry in the hosts file on the client
PC for that server. The hosts file is found in the Windows directory on Windows 95/98 computers
and the hosts file is found in the WinNT\System32\Drivers\etc directory on Windows NT computers
n During the network server installation, the setup program will run regsvr32.exe to register scrrun.dll.
If regsvr32.exe is not present in the Windows system directory, then the installation will fail with an
error message stating that regsvr32.exe could not be found
n To run ASAP in the Network Server environment, once the Network Server installation has
completed, users must run the ClientSetup program from the Network Server ASAP project
directory. This program is located on the project-designated server and will create the environment
required by a network client in order to run the Implementation Assistant and Q&Adb from a
Network
© SAP AG ASAP92 5-1

Business Process Procedure I
BUSINESS PROCESS PROCEDURE
Title: Create Purchase Order for Stock Material

Organization/Area Material Management
EPU Category: 5
File Name: EME21I46.DOC Release: R/3 4.6A
Responsibility: <Responsibility> Status: <Status>
Trigger:
• Direct demand for Purchase order for stock material
Business Process Procedure Overview
A purchase order is a legal document used to record an individual purchase (negotiated terms, conditions and pricing) with the
vendor or arrange for a delivery based on prior agreement. It also provides the vendor with a reference document to link to shipping
(goods receipt) and invoicing (invoice verification) processes.
The purchase order is a commitment to a vendor for a given material, in a specified quantity at a predetermined price and delivery
date.
Input - Required Fields Field Value / Comments

Vendor Vendor number
Date Purchase Order date
Purchasing Organization Should default
Purchasing Group Buyer who will purchase
Output - Results Comments

Printed purchase order Can be manually sent, faxed or EDI
Tips and Tricks

EPU Category: 5
Procedural Steps
1.1. Access Create Purchase Order: Initial screen by:
Via Menus Logistics>Materials Management>Purchasing>Purchase Order> Create>Vendor
Known
Via Transaction Code ME21
1.2. On screen “Create Purchase Order: Initial Screen”, enter information as specified in the
fields in the table below:
<<< Screen print goes here >>>
Field Name Description R/O/C User Action and Values Comments
Vendor Vendor number R Vendor number known or via
matchcode selection
Order type Order type code O Standard PO
Framework PO (BPO)
Date Purchase order date R Date PO created defaults to today’s
date
Purchase Order Purchase Order Number C Number can be internally or externally Leave blank if
Assigned internally
assigned; fill in if
external
assignment
Purchasing Purchasing Organization code R Should default
Organization
Purchasing Group Purchasing Group Code R Buyer or group of buyers
Item category Type of purchase C Standard Consignment Third-party
Text Service
Acct. assignment Account where cost are allocated O PO’s to Stock should be configured
category to allow autopostings to inventory
account
Delivery Date Delivery date category R Indicates whether the delivery date is
category to be entered and displayed as a
calendar day, week, or month.
Delivery date Date expected for delivery of O Can default from material master or
material be entered manually
Plant Plant to which delivery is to be O Select plant number
made
Storage Location Where stock is stored O Select storage location assigned to
above plant
Material Group Material group code O Will default from material master
Req. tracking Number that facilitates monitoring O Can be used in List display to list all Potential entry is
number of the procurement of required PO’s created by a certain buyer employee
materials number
Price date Price date O date price effective from
Vendor sub-range vendor purchasing info C can be entered if vendor has access
to files
Promotion vendors promotion O can refer to a particular promotion by
vendor
Acknowledgment determines whether the purchasing O Turn on button if acknowledgment is
required document (PO) is to be required
acknowledged by vendor


EPU Category: 5
Press enter.
1.3. On screen “Create Purchase Order: Item Overview”: enter information as specified in the

Item Item number of purchase order item R Defaults
Material Material number R Material master known or via
matchcode selection
Quantity Required units or quantity R Enter qty. required
Net Price Vendors Price R Vendors current price should be Note: if material
entered here is on agreement
use agreement
price not current
price
Date Date material is required R Will default Initial screen if entered
Plant Plant code R Enter plant to which stock material is
to be delivered
1.4. On screen “Create Purchase Order: Item Details”, enter information as specified in the
Info record Used to specify how vendor’s info O
update record will be updated in the system
Reminder 1, 2, 3 Reminder (in days) O
Confirmation Determines which confirmation O
control key categories are expected
Underdelivery Tolerance allowed for under delivery O
tolerance (in %)
Overdelivery Tolerance allowed for over delivery O
tolerance (in %)
Unlimited Indicates any quantity is allowed to O
be received against PO
Tax code Determines taxability of material O
Shipping Used to indicate how goods are to O
instructions be shipped
IR Indicator specifying that PO is R
expecting invoice receipt
GR-based IV Indicator specifying that invoice O
receipt can be posted for each
individual goods receipt (rather than
for each PO line item).
1.5. On screen “Create Purchase Order: Header Details”, enter information as specified in
the fields in the table below:


EPU Category: 5

Terms of delivery Vendor terms R Will default from Vendor Master
and payment
Incoterms 1&2 Transfer of ownership point R Will default from Vendor Master
Currency Currency vendor deals in R Will default from Vendor Master
Exchange rate Exchange rate of currency if applicable R Will default from Vendor Master Leave blank if intern
assigned; fill in if ex
assignment
References References documents O Quotation number, date etc
Text Overview Additional information O Shipping instructions , unloading point
etc
Salesperson Contact person at vendor site O Will default from Vendor Master
Telephone Telephone number of contact O Will default from Vendor Master
person
Invoicing Party Vendor master number used to O Will default from the Vendor master
denote the remit-to (or pay to)
address for the vendor
CtrySlsTxNo. Country of sales tax ID number C
Note: On the above table, in column “R/O/C”; “R” = required, “O” = Optional, “C” = Conditional)
Press the <save> icon.
Result: PO created under the number 45xxxxxxxx.

Business Process Procedure II
Title: Create a Standard Sales Order

Organization/Area: SD
EUP Category: 5 (Daily Processing)
File Name: Release: R/3 4.6A
Responsibility: Order Entry Clerk Status:
OVERVIEW
Trigger:
Customer places a standard sales order and/or places a standard sales order with reference to a
quote or a contract.
Business Process Description Overview

This document describes the procedure required for creating a sales order for a sold-to customer. This document also describes
how to create a sales order with reference to a quote and contract.
The sales order defines who the customer is, what pricing the customer is to receive, when the order is to be delivered, what
material and how much is to be delivered and is the basis for all following document including the delivery documents and billing
documents.
Input - Required Fields Field Value / Comments

Order Type The order type used for a standard sales order is ‘OR’
Sales Organization
Distribution Channel
Division
Sold to Party
Req.Deliv.Date
Pricing Date
Material
Order Quantity
Output - Results Comments

Creation of a sales order Refer to Business Process Procedure ‘Display a Sales Order’ or ‘Display SD
Document Flow’ for verification
Decrease in available inventory at storage Only if system is configured for commitment of inventory at order entry.
location
Tips and Tricks


Procedural Steps
(Create standard sales order)

1.1. Access transaction by:
Via Menus Logistics → Sales/Distribution → Sales
Order → Create
Via Transaction Code VA01
1.2. On screen “Create Sales Order: Initial Screen”, enter information in the fields as
specified in the table below:



Order Type Field that identifies the type of sales R Enter "Standard Order"
order
Sales Independent unit that is responsible R Enter Sales Organization for the order.
Organization for sales processing of a product or
product line
Distribution Means of getting a product to the R Enter Distribution Channel for the order.
Channel customer
Division Group of products or services R Enter Division for the order.
Sales Office Physical location responsible for sales O
certain products or services within a
given geographical area
Sales Group Group of sales people that are O
responsible for a special area of
processing of a group of products or
services within a specific sales office.
Press ENTER key Alternately, click
green
check mark icon
(Note: On above table, in column “R/O/C; R = Required, O = Optional, and C = Conditional)
1.3. On screen “Create Standard Order: Overview”, enter the information specified in the fields in
the table below:



Sold-to-Party Number of the customer to whom the R Enter the Sold-to party’s customer number
product is being sold or use matchcodes to find the number.
P.O. No. Customer’s Purchase Order Number O
Req. Deliv. Date customer requires delivery R Enter the Requested Delivery Date. Usually
Date defaults to
today’s date
Pricing Date Date that the product is priced R Enter the appropriate Pricing Date. Defaults to today
Material(s) Material Number of the product being R Enter material being ordered.
ordered
Order Quantity Amount of material the customer is R Enter quantity being ordered.
ordering
Press ENTER key Alternately, click
green
check mark


1.3.1 Dialog Box

If you identified several unloading points or several ship-to parties in the Customer Master
record, the system will display the alternatives in a dialog box. The system can propose
alternatives for Unloading Point, Ship-to Party, Payer or Bill-to Party.
Select data from these proposals by positioning the cursor on the line and clicking on “Choose”.
1.4. Availability Check

Once you have selected the data, the material data that you entered is displayed. If the system carries out
an availability check and finds that there is insufficient stock for an ordered item to be delivered on the
requested date, it displays a screen on which you can choose between several delivery proposals.
1.5. Optional Screens

If you want to enter further data for the header or the items, select the corresponding menu entry. If you
want to change data for the items, mark the items before you select a menu entry.
Enter all necessary data.


Unit Testing Conditions and Variations

SETUP DATA
DATA OBJECT VALUE/CODE DESCRIPTION COMMENTS AND NOTES
Order Type OR Standard Order
Sales Organization 1000 Germany – Frankfort
Distribution Channel 12 Sold for Resale
Division 00 Cross Division
Plant 1000
Purchasing 1000
Organization
Vendor 1000
Sold To Party 11740
Material 1400-502 1500cc MSI Motor Sport
Deluxe
Delivery Block (as you created)
CONDITIONS/STEPS
OK /
CONDITIONS & VARIATIONS EXPECTED RESULTS ACTUAL RESULTS
ERROR
Inventory Level 2,000 units
Price $5,000
Comments:
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
Approval: _________________________ Date: ____/____/____

Sample MSI Test Scenario Appendix Tools in Detail
AcceleratedSAP - Januar 13, 2001
Test Scenario No. 01 PAGE: __ OF __
SCENARIO: Sales from Stock to “Non Authorized Resellers” with transfer of requirements OWNER:
BUSINESS CASE: Full order quantity goes on special delivery block, requirements are not transferred until order has STATUS:
been approved and released
DESCRIPTION: Sales from Stock to “No Authorized Resellers” with transfer of requirements - full order quantity RUN NO.:
Customer order/ Delivery Block/ Approve & Release/MRP list/delivery/ invoice
EXPECTED RESULTS: Orders for Non authorized resellers are blocked for delivery, transfer of requirements does not take RUN DATE:
place until Orders have been approved and released from delivery block.
SETUP DATA
DATA OBJECT VALUE/CODE DESCRIPTION COMMENTS AND NOTES
Company code 1000 IDES AG – Frankfurt
Plant 1000 Hamburg
Material Master 11740-502 1500cc MSI Motor Sport
Deluxe
Customer Master 11740 Motor Mart

TRANSACTIONAL STEPS
No. BUSINESS PROCESS STEPS / TRANS. INPUT DATA / SPECIAL OUTPUT DATA / RESULT TESTER / OK /
BPP NUMBER CODE INFORMATION TEAM ERROR
0 Customer orders material
1 Create sales order (SO) VA01 Document type: SO Doc.no.:
Goods recipient:
Quantity:
Price:
Delivery Block: (non author
reseller)
(save )
2 Check scheduling VA02 (status overview) Schedule line confirmed?
3 Check availability VA02 (availability overview)
4 Check stock/requirements list MD04 Material: 1400-502 Requirement exists? SD or PP

Plant: 1000 Team
5 Create delivery with reference to SO VL01 Shipping point: 1000 Could you create a delivery?
SO Doc.no.:
Take full quantity!

6 Approve & Release Order V1.4 (display list, edit document,

remove block, save order)
7 Check stock/requirements list MD04 Material: Requirement changed from SD or PP
Plant: SO to delivery? Team
8 Check scheduling VA02 (status overview) Schedule line confirmed?

9 Create delivery with reference to SO VL01 Shipping point: 0001 Delivery Doc. No.:
SO Doc.no.:
Picking
10 Change delivery: create picking VL02 (overview picking) Picking Status = “C”
Delivery Doc.no.:
10 Delivery Post goods issue VL02 Delivery Doc.no.: Goods movement status =
“C”
12 Create invoice VF01 Delivery Doc.no.: Billing Doc.no.:
13 Check accounting documents VF03/ Billing Doc.no.: FI/CO
FB01 FI Doc.no.: Team
99 Post incoming payment FI-Team
Comments:
_________________________________________________________________________________________________________________________
_________________________________________________________________________________________________________________________
_________________________________________________________________________________________________________________________
Approval: _________________________ Date: ____/____/____
SAP, the SAP logo, R/3, AcceleratedSAP and ASAP are trademarks of SAP AG. Dokument in Demo Document Container (1)

Sample Case Procedure
Title:
Case Procedure
Organization/Area Page: 5
File Name MSI Case Procedure Updated Created by Janet White PTL Release 4.6A
Title Order to Cash Case Procedure Geography Status
Case Profile
Case Description
MSI’s has several customers that are “approved” resellers that require no formal review process. MSI
does however require a formal review process for all orders received for “non-approved” resellers.
This review process consists of obtaining approval from the Director of Sales. MSI’s approval process for
non approved reseller’s is lengthy and takes time; there for MSI standard procedure is that all orders being
reviewed for approval must not commit inventory until after the approval has been obtained.

Special Requirements
Okay? Yes No:

**Special Configuration is required: need to develop a special “reason for Ok per Rolf Schmidt – MSI Project Manager
blocking in shipping’ code (OVLS,OVLX) to satisfy this requirement **
Need to coordinate with the Shipping Team, Manufacturing Team, and

Authorization Team.
Key Integration Areas will be :
Order Fulfillment Team – will need a procedure to communicate to

Director of Sales to obtain approval and communications back to the
customer.
Shipping Team – need a procedure to manually release and ship orders

from this block once the approval has been obtain
Manufacturing Team – will need to verify that inventory is not being

committed and requirements are not being passed for these blocked
orders unit the block has been removed
Authorization Team – will need to develop special authorization to allow

manual releasing of the block.

Title:
Case Procedure
Configuration Section
Context
S Object Value/Code Description/Comments/Notes

1 SYSTEM 400
2 CLIENT T20
3 COMPANY
Business Environment
Description of the business process setting that you will be configuring to
Receive the Order → Take the Order → Manually Block Order from Delivery → Save the Order → Review & Approve Orders on
block → Release Orders from Block → Commit Inventory → Create Delivery → Create Shipment → Post Goods Issue → Create
Invoice

Configuration
Accelerator or How-to Procedure Description
VA01 (Create Standard Order ) (apply special delivery block)

V1.4 (Display Sales Orders Blocked for Delivery)
VA02 (Change Standard Order) – Review & Release from Block
VL01 (Create Delivery)
VL02 (Pick, Pack & Post Goods Issue)
VF01 (Create Billing Document)

Title:
Case Procedure
Test Section
Business Environment
Description of the business process setting that you will be testing to
- Need to validate that once an order is received from a “non approved” reseller, the order goes on special delivery block.
- Need to validate that all orders on this special delivery block do not get shipped or billed until the authorized personnel have
released the orders.
- Need to validate that orders on this special delivery block do not commit inventory and requirements do not get passed to
manufacturing until after the order has been released
- Need to validate the authorization profile for releasing orders on this special delivery block

Test Plan
Describe specific steps, explanation, input data or assumptions that need to be followed in order to perform this test.
VA01 - Create Standard Order: Customer #11740, material # 1400-502, sales org = 1000, distribution channel = 12 Sold for Resale,
Division = 00 Cross Division, PO # = 555, Qty = 1, Assign Delivery Block = Reason Code:“XX – Non Authorized Reseller”, save the
order.
VL01 – Create Delivery – attempt to create a delivery for your order for customer #11740, the system should not allow you to create
this delivery. “Order Blocked for Delivery”.
MD04 – Check Stock Requirement List – determine if requirements exists.
VA02 – Change Order – check scheduling and availability – determine if scheduling has been confirmed.
V1.4 - Display Sales Orders Blocked for Delivery: you should be able to view your order that you just created from the display list.
(Sales Order →Information System → Report Selection → Work Lists) Review & release order from Delivery Block, save order.
(VA02 – Change Sales Order)
VL01 – Create Delivery: you should now be able to create a delivery for the order for customer #1170
VL02 - Pick, Pack & Post Goods Issue: should now be able to post goods issue for manual delivery that was just created
VF01 - Create Billing Document – should now be able to create a billing document for your order that was just “posted goods issue”

Prerequisites: All Client Computers Must Have .: Appendix

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Prerequisites: All Client Computers Must Have .: Appendix

Caricato da

Copyright:

Formati disponibili

Network Installations

Prerequisites: All Client Computers must have ….

© SAP AG ASAP92 5-1

BUSINESS PROCESS PROCEDURE

Title: Create Purchase Order for Stock Material

Business Process Procedure Overview

Input - Required Fields Field Value / Comments

Purchasing Group Buyer who will purchase

Output - Results Comments

Tips and Tricks

© SAP AG ASAP92 5-2

© SAP AG ASAP92 5-3

Title: Create Purchase Order for Stock Material

Field Name Description R/O/C User Action and Values Comments

© SAP AG ASAP92 5-4

Title: Create Purchase Order for Stock Material

<<< Screen print goes here >>>

Field Name Description R/O/C User Action and Values Comments

Press the <save> icon.

Result: PO created under the number 45xxxxxxxx.

© SAP AG ASAP92 5-5

Title: Create a Standard Sales Order

Business Process Description Overview

Input - Required Fields Field Value / Comments

Output - Results Comments

Tips and Tricks

© SAP AG ASAP92 5-6

Title: Create a Standard Sales Order

(Create standard sales order)

© SAP AG ASAP92 5-7

Title: Create a Standard Sales Order

Field Name Description R/O/C User Action and Values Comments

(Note: On above table, in column “R/O/C; R = Required, O = Optional, and C = Conditional)

© SAP AG ASAP92 5-8

Title: Create a Standard Sales Order

Field Name Description R/O/C User Action and Values Comments

© SAP AG ASAP92 5-9

Title: Create a Standard Sales Order

1.3.1 Dialog Box

1.4. Availability Check

1.5. Optional Screens

Enter all necessary data.

© SAP AG ASAP92 5-10

Title: Create a Standard Sales Order

Unit Testing Conditions and Variations

Approval: _________________________ Date: ____/____/____

© SAP AG ASAP92 5-11

AcceleratedSAP - Januar 13, 2001

Test Scenario No. 01 PAGE: __ OF __

© SAP AG ASAP92 5-1

3 Check availability VA02 (availability overview)

4 Check stock/requirements list MD04 Material: 1400-502 Requirement exists? SD or PP

Take full quantity!

© SAP AG ASAP92 5-2

6 Approve & Release Order V1.4 (display list, edit document,

8 Check scheduling VA02 (status overview) Schedule line confirmed?

99 Post incoming payment FI-Team

© SAP AG ASAP92 5-3

Title Order to Cash Case Procedure Geography Status

© SAP AG ASAP92 5-5

Okay? Yes No:

Need to coordinate with the Shipping Team, Manufacturing Team, and

Key Integration Areas will be :

Approval: _____________________ Date: //

Test Scenario No. 01 PAGE: OF