Business Process Procedure

Icons

Icon Meaning
Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field
names, screen titles, pushbuttons as well as menu names, paths and
options.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as
names of installation, upgrade and database tools.
EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.

Example text Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text> Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.

Page 1 of 15
 Business Process Procedure

Abbreviations
R Required entry field
(used in the end-user procedures)
O Optional entry field
(used in the end-user procedures)
C Conditional field
(used in the end-user procedures)

Page 2 of 15
 Business Process Procedure

Contents

Sl No Description Page No

1 Purpose 4
2 Create Sales Order 4
3 MRP – Single Level 5
4 Create Stock Transport Order with reference to PR 6
5 MRP – Multi Level 7
6 Create Delivery by Editing the Delivery List (In) 8
7 Picking and Post Goods Issue 10
8 Goods Receipt 10
9 Create Inter-Company Billing 10
10 Invoice Verification 12
11 Performing an Availability Check 13
12 Create Delivery Picking and Post Goods Issue 13
13 Create Billing 14

Page 3 of 15
 Business Process Procedure

Internal Procurement (Cross-Company Stock

Transfer)
1. Purpose
This scenario deals with cross-company-code stock transfers.
A customer orders goods from central sales organization . The goods are manufactured in another
production plant…, which belongs to a different company code, transferred to the main plant , and
then sent to the customer.
Focus:
 The production and main plant are in different company codes
 Purchase orders are sent from the main plant to the production plant via a stock transport order,
in a two-step procedure
 Stock is transferred from the production plant to main plant
 Inter-company billing and internal transfer price
 Outbound delivery to customer
 Customer invoices
The customer sends a purchase order to the sales organization. A standard order is created in the
vendor's system and contains main plant as the delivering plant.
Requirements planning is carried out in the main plant (ordering company code).Requirements
planning, therefore, automatically generates puchase requisition to cover the customer requirements.
A delivery (stock transfer) to the main plant PSS1 is created in the production plant. Inter-company
billing in the delivering company code (to ) is also created here.
The production plant delivers goods to the main plant. The goods receipt is posted there. The delivery
is then made to the customers, the goods issue is posted and the customer invoice is created.

2. Create Sales Order

Procedure
1.   Access the transaction using:

SAP R/3 menu Logistics  Sales and distribution  Sales  Order  Create
Transaction code VA01

2.   Enter the necessary data.

Field name Description R/O/D User action and values Comment

Order Type R OR

Page 4 of 15
 Business Process Procedure

Sales Organization R
Distribution R 01
Channel
Division R 01
Enter
Sold-to Party R
PO number O Reference PO number of the customer
Material
Order Quantity R
Enter
Save

3. The Standard Order: Availability control screen is then displayed. Because the material is not available in
the plant, a schedule line (quantity/date) cannot be confirmed for the requested delivery date.

4. Push Continue button in the Standard Order: Availability control screen

5. The Standard Order: Overview screen is displayed again.

6. Save your standard order. A message is displayed indicating that the standard order <number> has been
saved.

Make a note of this number.

7. Click Back to return to the SAP Easy Access screen.

Result
Sales order has been created.

3. MRP – Single Level

Use
Material requirements planning will cover the customer requirements by creating purchase requisition
in this plant.

Procedure
1. Access the transaction by using:
SAP R/3 menu Logistics  Production  MRP Planning Single-Item,
Single–Level Planning

Page 5 of 15
 Business Process Procedure

Transaction code MD03

2. Maintain the Single-Item, Single-Level screen in accordance with the following table:

Field Description R/O/D User Action Comments

and Values
Material R 900002
Plant R PSS1
MRP control
parameters
Processing
key
Create R Purchase requisitions in opening
purchase req. period
Delivery R Schedule lines
schedules
Create MRP MRP list
list
Planning R Adapt planning data (normal mode)
mode
Scheduling R Basic dates will be determined for
planned orders
3. Confirm your entries and the messages output by the system. Push Enter button for the warning
message ‘Please check input parameters’

The system tells you that planning has been carried out.

4. Choose Exit to go back to the SAP Easy Access screen.

Result
The purchase requisition was generate

4. Create Stock Transport Order with PR reference

Use
Stock transport order will be created with the purchase requisition reference

Procedure
1. Access the transaction by using:
SAP R/3 menu Logistics  Material Management  Purchasing  Purchase
Order  Create  Vendor/Supplying Plant Known
Transaction code ME21N

Page 6 of 15
 Business Process Procedure

2. In the Create Purchase Orde, enter the values shown in the following table:

Field Description R/O/D User Action and Values Comments

Order type R NBP
(Purchasing)
Vendor R 1005
In the Org. data Tab
Purchasing Org. R PSPO
Purch. group R PSG
Company Code R PSSL
Click button Document
Overview on
In the Overview sub- Click button Selection
screen variant and select
Purchase requisition
In the Purchase
requisition screen
Purchase R Purchase requisition
requisition number generated in the
number previous step
Execute
In the Overview sub- Select the Purchase
screen Document and click button
Adopt
Click Button Expand Item
Overview
Net Price R
Plant R PSS1
Storage R FGP
Location
Tax code On Invoice tab R V3
Save
3. Choose Exit to go back to the SAP Easy Access screen.

Result
The stock transport order was generated.

5. MRP – Multi-Level
Use
The requirements from the stock transfer order are transferred automatically to plant PM01

These requirements will be covered by planned orders in requirements planning.

Page 7 of 15
 Business Process Procedure

Procedure
1. Access the transaction by using:
SAP R/3 menu Logistics  Production Process  MRP  Planning  Single-
Item, Multi-level Planning
Transaction code MD02

2. Maintain the Single-Item, Multi-Level screen in accordance with the following table:

Field Description R/O/D User Action Comments

and Values
Material R 900002
Plant R PM01
Scope of
planning
Product group
MRP control
parameters
Processing key R
Create purchase R Purchase requisitions in
req. opening period
Delivery schedules R Schedule lines
Create MRP list R MRP list
Planning mode R Adapt planning data (normal
mode)
Scheduling R Basic dates will be determined
for plann
Process
control
parameters
Plan all O Default value
components
Display result O
Display material list O
Simulation mode O

3. Confirm your entries and the messages output by the system. Push Enter button for the warning
message ‘Please check input parameters’.
A statistical overview of the MRP run is then displayed.

4. Click Exit to return to the SAP Easy Access screen.

6. Create Delivery by Editing the Delivery List (In)

Page 8 of 15
 Business Process Procedure

Use
In this scenario, production is not taken into account. Planned orders are normally
converted to a production order.
The goods receipt for this production order is the concluding operation for production. These
steps are not shown here. Please ensure that sufficient stock is available for the delivery. If
this is not the case, carry out the following steps:
1. Call up transaction MB1C: Movement type: 561; plant: PM01; storage location: FGP,
Confirm your entries.
2. In the Enter Other Goods Receipts: New Items screen, enter: Material:; quantity: 100.
Save your entries and go back to the SAP Easy Access Screen.
The starting point for this step is as follows: the goods have been manufactured in the
delivering plant PM01 and are ready for delivery. The delivery list has to be processed for
the outbound delivery. The goods are transferred from Plant to the receiving plant .

Procedure
1. Access the transaction by using:
SAP R/3 menu Logistics  Logistics Execution  Outbound Process  Good
Issue for Outbound Delivery  Outbound Delivery  Create 
Collective Processing of Documents Due for Delivery 
Purchase Orders
Transaction code VL10B

2. Maintain the Purchase Orders, Fast Display screen in accordance with the following table:

Field Description R/O/D User Action and Values Comments

Shipping Point O PM01
/ Receiving Pt
Deliv. creation R Until the end of next week
date (See note below)
Purchase
orders Tab
Purchasing O STO number
document
3. Confirm your entries.

4. Choose Execute to display the delivery list.

If no delivery items are found for the current date, extend the delivery
creation/selection date (but not by more than 30 days, as this will exceed the

Page 9 of 15
 Business Process Procedure

maximum interval for selecting the delivery creation date) to display the next
delivery. Choose Execute again.

5. In the Activities Due for Shipping: "Purchase Orders, Fast Display" screen, select the relevant
purchase order.

6. Click the Background pushbutton.

When the delivery for the stock transport order is created, the parallel processing
popup appears (this popup is the standard system response). Choose All or
Cancel; this does not have any effect on the creation of the delivery. The delivery
is created each time.

7. A delivery is created. The system generates a log to create the delivery. To display the log,
choose the Log for delivery creation pushbutton, a new screen Delivery Creation Log will popup.

8. Select the relevant entry in the Log for delivery creation screen and then choose the Documents
pushbutton. The delivery note number is then displayed. Make a note of this number.

9. Go back to the SAP Easy Access screen.

7. Picking and Post Goods Issue (InPM01)

Procedure
1.   Access the transaction using:

SAP R/3 menu Logistics Sales and distribution  Shipping and Transportation
 Outbound delivery  Change  Single Document
Transaction code VL02N

2.   Enter the necessary data.

Field name Description R/O/D User action and values Comment

Outbound R Delivery No. generated in the
Delivery previous step
Enter
In the Picking Tab
Picking Quantity R
Click button Post goods issue

Page 10 of 15
 Business Process Procedure

Result
The goods was issued out byPM01

8. Goods Receipt (In PSS1)

Procedure
1.   Access the transaction using:

SAP R/3 menu Logistics -> Material Management -> Inventory Management ->
Goods Movement -> Goods Receipt -> For Purchase Order ->
GR for Purchase Order (MIGO)
Transaction code MIGO

2. Enter the necessary data.

Field name Description R/O/D User action and values Comment

Action can be carried R Goods Receipt A01
out in the MIGO
transaction
Reference document R Purchase Order R01
for MIGO transaction
PO number R Generated in the step “Create Stock
Transport Order with PR reference”
Enter
Item OK R Checked
Click button Post

3. Go back to the SAP Easy Access screen.

Result
The goods were received from Plant .

9. Create Inter-Company Billing (In)

Use
Now an (inter-company) invoice has to be created in the delivering company code .

Procedure

Page 11 of 15
 Business Process Procedure

1.   Access the transaction using:

SAP R/3 menu Logistics Sales and distribution  Billing  Billing Document
 Create
Transaction code VF01

2.   Enter the necessary data.

Field name Description R/O/D User action and values Comment

Billing Type R Intercompany billing IV
Document R Delivery Number
Select item
Execute
Save

10. Invoice Receipt (in PSS1)

1. Access the transaction choosing one of the following navigation options:
SAP R/3 menu Logistics  Material Management  Logistics Invoice
Verification  Document Entry  Enter Invoice
Transaction code MIRO

2. On the Enter Company Code dialog box, make the following entries:
Field name Description R/ O/ C User action and values Comment
Company Code R
Button R Enter

The company code must be entered only with the first call of the transaction "MIRO"
within a log-on. Afterwards you can modify the accounting area by choosing the
Company code change button at any time.
If incoming invoices are entered predominantly or exclusively to one company code, then
it is recommendable, to pre-allocate the company code over the user parameter
“company code “in the user master data. The input of the company code with call of the
transaction is then no longer necessary.

3. On the Enter Incoming Invoice: Company Code screen, make the following entries:
Field name Description R/ O/ C User action and values Comment

Page 12 of 15
 Business Process Procedure

Transaction O Invoice 1
Invoice date O Today’s date
Post date R Today’s date If not defaulted
Tax code O V3
Amount R
Purchase R PO number generated in
Order/Sched the step Create Stock
uling Transport Order with PR
Agreement reference
Baseline date On Payment tab R
Button O Simulate
Button R Post
Please note
document
number.

Before post the invoice, consider the traffic light function of the balance. If the invoice
amount corresponds with the value of the position, then a green traffic light is displayed.
Change now the proposed value of the amount in the item summary and press ENTER.
The value is now no longer correct and the traffic light wraps around on red. The voucher
cannot be posted; only a pre- entry is possible. Correct afterwards the amount.
If the amount of the invoice corresponds with the amount of the position, but deviates e.g.
the calculated quantities of the good receipts amount, then you receive a warning and the
traffic light displays yellow. The voucher can be posted, in the following one however it is
closed for payment. With the help of the Buttons "Messages" can be able to be displayed
you further details of occurred "errors".
In order to see, which general ledgers are posted, please press the Button "Simulating".

11. Performing an Availability Check

Use
Since no schedule lines (quantity/date) could be confirmed initially because no material was
available, an availability check must now be carried out.

Procedure
1. Access the transaction by using:
SAP R/3 menu Logistics  Sales and distribution  Sales  Order  Change
Transaction code VA02

Page 13 of 15
 Business Process Procedure

2. Maintain the Change Sales Order: Initial Screen in accordance with the following table.

Field Description R/O/C User action and values Comment

Order R Standard order which was created in the
section “Process: Sales Order Processing”
3. Confirm your entries.

4. In the Change Standard Order XX: Overview screen, select the relevant item.

5. Choose Edit  Check availability  Delivery Proposal.

6. To take a look at the confirmed schedule, choose Goto  Item  Schedule lines

7. Save your entries.

12. Create Delivery Picking and Post Goods Issue

Procedure
1.   Access the transaction using:

SAP R/3 menu Logistics Sales and distribution  Shipping and Transportation
 Outbound delivery  Create  Single Document  with
Reference to Sales Order
Transaction code VL01N

2.   Enter the necessary data.

Field name Description R/O/D User action and values Comment

Shipping point R
Selection date R Today
Order R Sales Order number
Enter
Picking Tab Enter the picking quantity
Storage Location Check the storage location for
the Plant

Post Goods Issue

Page 14 of 15
 Business Process Procedure

13. Create Billing

Procedure
1.   Access the transaction using:

SAP R/3 menu Logistics Sales and distribution  Billing  Billing Document
 Create
Transaction code VF01

2.   Enter the necessary data.

Field name Description R/O/D User action and values Comment

Document R Delivery Number
Select item
Execute
Save
Back

Page 15 of 15