Business Process Test - Intercompany STO

Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 5
At a glance
Powered by AI
The document describes the process and pre-requisites for setting up an intercompany stock transfer between two SAP systems.

New document and material types need to be set up. The material and vendor/customer masters also need to be set up in both the issuing and receiving plants/company codes.

The purchasing company code creates the purchase order. This includes entering the header information, item details, and saving the purchase order number.

Business Process Testing Scenario

Scenario: MM02-IC Direct Intercompany procurement for Finished Goods

Created by Team MM Date: 20 July 2007


Scenario Description Inter company stock transport order to allow goods to be moved between
plants existing in different company codes. This will include financial
postings to move the stock value between company codes whereas
normally there would be no financial movement if the stock is moved
within a company code.

The purchase order would be created by the requesting company code


and the delivery fulfilled by the issuing company code.

Scenario below is to move stock from Antwerp to UK.

Additional Functionality Deliveries from SD


to be Tested

Pre-Requisites • New Purchasing Document Types to differentiate from normal


STO. i.e. ZUB1 for Duty Paid, ZUB2 for Duty Unpaid.
• New Delivery Document Types to correlate with different
Purchasing Document Types. i.e. ZNL1 for Duty Paid, ZNL2 for
Duty Unpaid.
• Material master must be set up in both issuing and delivery plants
with sales views for DC=04
• Vendor must be present in requesting company code with the
vendor code “PLANT xxxx” where xxxx is the issuing plant. For
example “PLANT 150D” would be to purchase goods from
Antwerp plant.
• Customer must be present in selling company code with the
customer code “PLANT xxxx” where xxxx is the receiving plant.
For example “PLANT 169B” would be for movements to NGL.
• Billing Types depend upon Order Types (Duty Paid / Duty
Unpaid)

Step Description of Test Steps Team Script/step


Menu path & transaction
1 Create PO – Done by the purchasing Company Code MM ME21N
.
Header Logistics > Material
Document type : ZUB1 OR ZUB2 Management > Purchasing
Vendor code : “PLANT 150D” (Antwerp) > Purchase order > Create
Purchasing Organization : SAE2 > ME21N -
Purchasing group: 011 Vendor/Supplying Plant
Company: 7169 Know

2 Item Detail – Done by the purchasing Company Code MM ME21N


.
Material: SAPCRV94EHDX Logistics > Material
Quantity: xx Management > Purchasing
Net price : xx > Purchase order > Create
Plant: 169B > ME21N -
Vendor/Supplying Plant
Save Know

PO number : 45XXXXXXXX

Page 1 of 5
/opt/scribd/conversion/tmp/scratch6732/51467806.doc
12/02/11 11:16
Business Process Testing Scenario
Step Description of Test Steps Team Script/step
Menu path & transaction

3 Create Outbound Delivery – Done by the issuing Company SD VL10B


. Code
Logistics > Sales And
Delete the header fields from the screen. Distribution > Shipping And
Trasportation > Outbound
TAB Purchase Order: Delivery > Create >
Collective Processing of
Supplying Plant 150D Documents Due for
Delivery
Press the Execute button (watch icon)

Page 2 of 5
/opt/scribd/conversion/tmp/scratch6732/51467806.doc
12/02/11 11:16
Business Process Testing Scenario
Step Description of Test Steps Team Script/step
Menu path & transaction

If required, the delivery will automatically generate the interface


to the 3PL for picking and despatch purposes.

4 Confirm Outbound Delivery – Done by the issuing SD VL02N


. Company Code
\ Logistics > Sales And
If not automatically confirmed by the interface programs you Distribution > Shipping And
should manually confirm the despatch of the goods from the Trasportation > Outbound
issuing plant. Delivery > Create >
Collective Processing of
Enter the delivery number 8000xxxx Documents Due for
Delivery

Insert the correct quantity in “Pick quantity” on the “Picking”


tab.

Insert the Storage location if it is not pre-entered.

Page 3 of 5
/opt/scribd/conversion/tmp/scratch6732/51467806.doc
12/02/11 11:16
Business Process Testing Scenario
Step Description of Test Steps Team Script/step
Menu path & transaction

Press the button “Post good issue”

Material documents:
490000000X

5 Receive Goods – Done by the purchasing Company Code MIGO


.
Select “A01 Goods Receipt” Logistics/Material
management/Inventory
Insert the PO number management/Goods
movement
<enter>

In the left bottom of the screen, activate the flag “Item OK”

<save>

Document number: 500000000X

6 Enter Purchase Invoice – Done by the purchasing MIRO


. Company Code
Enter the Company code 7169 Logistics/materials
management/Logistic
<enter> Invoice
Verification/Document Entry
Invoice Date: actual date

Select the appropriate tax code

TAB “PO Reference” insert PO number (450000000X)

<enter>

Activate the flag “Calculate tax”

Page 4 of 5
/opt/scribd/conversion/tmp/scratch6732/51467806.doc
12/02/11 11:16
Business Process Testing Scenario
Step Description of Test Steps Team Script/step
Menu path & transaction

Insert the correct amount + tax

TAB “Details” choose the appropriate document type

TAB “Payment” insert the actual date in the field “Baseline Dt”

Press the button “Simulate” to check the balance and the


accounts

<save>

Document number:
3060000000X

Page 5 of 5
/opt/scribd/conversion/tmp/scratch6732/51467806.doc
12/02/11 11:16

You might also like