AF6_ERP606_BPD_EN_CN

EHP6 for SAP ERP
6.0
September 2013
English
AFS - Outsourced
Manufacturing (AF6)
Business Process Documentation
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices AFS - Outsourced Manufacturing (AF6): Specification
Copyright
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express
permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of
other software vendors.
National product specifications may vary.
These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes
only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP Group products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of SAP AG in Germany and other countries. Please see http://www.sap.com/corporate-
en/legal/copyright/index.epx#trademark for additional trademark information and notices.
© SAP AG Page 2 of 27
Icons
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
External Process
Business Process Alternative/Decision Choice
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.
Contents
1 Purpose........................................................................................................................................ 5
2 Prerequisites................................................................................................................................ 5
2.1 Master Data and Organizational Data...................................................................................5
2.2 Business Conditions.............................................................................................................. 6
2.3 Roles..................................................................................................................................... 6
2.4 Preliminary Steps.................................................................................................................. 7
3 Process Overview Table............................................................................................................... 9
4 Process Steps............................................................................................................................ 10
4.1 Creating Outsourced Sales Order.......................................................................................10
4.2 Creating Purchase Order.................................................................................................... 11
4.3 Approval of Purchase Orders (Optional).............................................................................13
4.4 Creating Outbound Delivery Request..................................................................................14
4.5 Posting Goods Issue........................................................................................................... 16
4.6 Posting Statistical Goods Receipt.......................................................................................18
4.7 Entering Invoice................................................................................................................... 19
4.8 Posting Outgoing Payment.................................................................................................. 20
4.9 Billing................................................................................................................................... 21
5 Follow-up Processes.................................................................................................................. 22
6 Appendix.................................................................................................................................... 23
6.1 Reversal of Process Steps.................................................................................................. 23
6.2 Reporting............................................................................................................................. 25
6.3 Used Forms......................................................................................................................... 26
AFS - Outsourced Manufacturing
1 Purpose
When entering the sales order for the end-customer a subcontracting purchase requisition can be
created automatically afterwards. This purchasing document combines the third-party process with
subcontracting functionality, i.e. components can be assigned to the purchase requisition and
purchase order. Additionally the purchasing document contains the delivery address of the end-
customer.
2 Prerequisites
2.1 Master Data and Organizational Data

SAP Best Practices Standard Values
Essential master and organizational data was created in your ERP system in the implementation
phase, such as the data that reflects the organizational structure of your company and master data
that suits its operational focus, for example, master data for materials, vendors, and customers.
This master data usually consists of standardized SAP Best Practices default values, and enables
you to go through the process steps of this scenario.
Additional Master Data (Default Values)

You can test the scenario with other SAP Best Practices default values that have the
same characteristics.
Check your SAP ECC system to find out which other material master data exists.
Using Your Own Master Data

You can also use customized values for any material or organizational data for which
you have created master data. For more information on how to create master data, see
the Master Data Procedures documentation.
Use the following master data in the process steps described in this document:
Master / org. data Value Master / org. data details Comments
Material: YF-F1107 T-Shirt Subcontracting
Material YF-R1207 Jersey Fabric
Material YF-R1208 Ribbed Fabric
Delivery Plant: 1000 Plant 1
Storage Location: 10F1 Shipping w/o LWM
Master / org. data Value Master / org. data details Comments

Shipping Point 1000 Shipping Point 1000
Sales organization: 1000 Dom. Sales Org 1000
Distribution channel: 20 Wholesale 20
Division: 10 Product Division 10
Sold-to party: YFC002 Customer 02
Ship-to party: YFC002 Customer 02
Payer YFC002 Customer 02
Bill-to party YFC002 Customer 02
2.2 Business Conditions

The business process described in this Business Process Documentation (BPD) is part of a bigger
chain of integrated business processes or scenarios. As a result, you must have completed the
following processes and fulfilled the following business conditions before you can start any activities
in this scenario:
Business condition Scenario
To run through this scenario, some prerequisite Prereq. Process Steps (BB - 154)
processes steps have to be done.
To execute this activity, run the following required
steps in the Business Process Documentation of
Prereq. Process Steps (BB - 154).
2.3 Roles
Use
The following roles must have already been installed to test this scenario in the SAP Netweaver
Business Client (NWBC). The roles in this Business Process Documentation must be assigned to
the user or users testing this scenario. You only need these roles if you are using the NWBC
interface. You do not need these roles if you are using the standard SAP GUI.
Prerequisites
The business roles have been assigned to the user who is testing this scenario.
Business role Technical name Process step
Employee SAP_NBPR_EMPLOYEE_S Assignment of this role is
(Professional necessary for basic functionality.
User)
Sales SAP_NBPR_SALESPERSON_S Create Third-Party Sales Order
Administrator
Purchaser SAP_NBPR_PURCHASER_S Creating Purchase Orders
Business role Technical name Process step

Purchasing SAP_NBPR_PURCHASER_M Approval of Purchase Orders
Manager
Accounts Payable SAP_NBPR_AP_CLERK_S Invoice verification: Enter (Vendor)
Accountant Invoice
Billing SAP_NBPR_BILLING_S Billing Accounts Receivable
Administrator
Warehouse Clerk SAP_NBPR_WAREHOUSECLERK_ Creating Outbound Delivery
S Request
Posting Goods Issue
Post Statistical Goods Receipt
2.3.1 Defining Queries for Personal Object Worklist (POWL)

The following queries must be defined to test this scenario in the SAP NetWeaver Business Client
(NWBC). You only need these queries if you are using the NWBC interface. You do not need these
queries if you are using the standard SAP GUI.
The queries are necessary to access role specific worklists in the SAP NetWeaver Business Client
(NWBC).
For more information on the creation of queries, see the section Creation of Queries in
Personal Object Worklists (POWLs) in the Quick Guide
AF_ERP606_Quick_Guide_EN_CN.doc document.
2.4 Preliminary Steps

2.4.1 Posting Initial Stock
Check stock overview by T-code: MMBE to make sure if there is sufficient material in
stock. If stock is enough, please skip this step.
Use
For order and delivery creation, material stock is required for the materials you use in this scenario.
For the Rush Order scenario it is necessary to post quantity of the material into the unrestricted used
stock of the relevant plant.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics  Materials Management  Inventory Management 
Goods Movement  Goods Movement (MIGO)
Transaction code MIGO
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role Warehouse Clerk
(SAP_NBPR_WAREHOUSECLERK_S)
Business role menu Warehouse Management  Consumption and Transfers
 Other Goods Movement
2. On the Goods Receipt screen, make the following entries:
Field name User action and values Comment
Action Goods Receipt

Reference Others
3. Choose Enter. On the right side, you can see the Movement Type 501 [Receipt w/o PO].
4. If necessary choose open the Detail data and choose Hide Overview. If Tip screen pops up, you
could confirm it with Enter.
5. On the Material tab, enter YF-R1207.
6. On the Quantity tab, enter 80.
7. On the Where tab, make the following entries:
Field name User action and values Comment
Movement type 501

Plant 1000
Storage location 10F1
8. Choose Enter.
9. On the Batch tab, make the following entries:
Field name Description User action and values Comment
Grid Value WHT Grid Value for colors.
10. Choose Next Item and repeat the steps 5 - 9 for the following items:
Material Qty in UnE Movement Plant Storage Location Grid value
type (Stor.Loc)
YF-R1208 50 501 1000 10F1 WHT
11. Choose Post.
12. Choose Back (F3) to go back to the SAP Easy Access screen (SAP GUI) or choose Exit
(Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP
NetWeaver Business Client).
Result
The different materials and quantities are posted on stock in the unrestricted used stock in the
storage location 10F1 of the plant 1000.
Financial postings:
Material Debited Credited Accounts Cost Element / CO Object

Accounts
Raw Materials 14030101 Raw 50020101 Material none
(ROH) Materials consump./tr
3 Process Overview Table

Process Step External Business Business Transaction Expected
Process Condition Role Code Results
Reference
Creating Sales VA01 Sales order
Third-Party Administrator has been
Sales Order created.
Purchase
requisition has
been
generated.
Creating Purchaser ME21N Purchase

Purchase order has
Order been created
Approval of Purchasing ME28 Purchase

Purchase Manager Order is
Orders approved
Creating Warehouse ME2O Outbound

Outbound Clerk Deliveries
Delivery have been
Request created
Posting Warehouse VL02N Goods issue is

Goods Issue Clerk posted
Post Warehouse MIGO Goods receipt

Statistical Clerk is posted
Goods
Receipt
Entering Accounts MIRO Invoice is
Invoice Payable created
Accountant
Outgoing See See scenario See See scenario

Payment Accounts no. 158 scenario no. no. 158
Payable 158
(outgoing
payment)
(158)
scenario
Process Step External Business Business Transaction Expected

Process Condition Role Code Results
Reference
Billing Billing VF04 Billing is
Administrator created
Incoming Accounts Accounts See See scenario

Payment Receivable Receivable scenario no. no. 157
(157) 157
Closing Sales:
Operations Period End
Closing
Operations
(203)
4 Process Steps
4.1 Creating Outsourced Sales Order
Use
The following describes how to create the sales order for a material with Outsourced.
Procedure
SAP ECC menu Logistics  Sales and Distribution  Sales  Order 
Create
Transaction code VA01
Business role Sales Administrator
(SAP_NBPR_SALESPERSON_S)
Business role menu Sales  Sales Orders Sales Order Processing 
Create Sales Order
2. On the Create Sales Order: Initial Screen, enter the information as specified in the table below:
Order type AFS YF3P
Subcontracting
Order
Sales organization 1000
Distribution channel 20
Division 10
3. Choose Enter.
4. On the AFS Subcontr. Order: Overview header screen, enter the following values and choose
Enter:
Header
Sold-to pt YFC002
Pur. Order <free text>
RqDlv.date Today + 1 month
5. Go to AFS Item overview tab page and enter the following data in the Material field and choose
Enter.
Material YF-F1107
6. In the Requ.Cat dialog box, choose a quality and a country of origin as the example in the next
table and choose Enter.
Quality 1
Country of Origin CN
7. Mark item 000010 and choose Matrix Entry.
8. On the Sales/Distribution screen, enter the following data and choose Enter:
Dim.values XS S M L XL XXL XXXL
WHT 100
9. Choose Back (F3).
10. Choose Save.
Result
The sales order has been created. The purchase requisition has been generated using the item
category of the sales order.
The printout of the order confirmation will be available after creating or releasing PO.
4.2 Creating Purchase Order

Use
A purchase order is the request or instruction from a purchasing organization to a vendor (external
supplier).
Prerequisites
A purchase requisition has been generated through the sales order in the previous step. You can get
the purchase requisition according to the following way:
1. If you are in GUI, display the sales order with transaction VA03; If you are in NWBC, choose
business role menu Sales Sales Orders and select All Sales Orders tab page. Mark the sales
order created in previous step and choose Display. Then choose Sales tab page on the Display
AFS Subcontr. Order: Overview screen.
2. Double-click the bought-in item and choose Schedule lines tab page for item.
3. On the Schedule line tab page, you find the delivery date and the number of the purchase
requisition. To obtain further information on the purchase requisition, choose Purchase
requisition.
Procedure

SAP ECC menu Logistics  Materials Management  Purchasing 
Purchase Order  Create  Vendor/Supplying Plant
Known
Transaction code ME21N
Business role Purchaser
(SAP_NBPR_PURCHASER_S)
Business role menu Purchasing  Purchase Order  Create Purchase Order
2. On the Create Purchase Order screen, choose Document overview on if the document overview
is not already displayed.
If there is Enjoy SAP Purchase Order screen in the left of the window, choose Close.
3. Choose selection variant My Purchase Requisitions.
The document overview contains a number of different purchasing documents. Here you
find the documents necessary for your daily work (such as purchase orders, purchase
requisitions, scheduling agreements).
You can, for example, display all purchase requisitions that have to be processed on the
left of the screen, and at the same time, process the relevant purchase orders on the
right part of the screen.
4. Select the relevant purchase requisition and choose Adopt.
5. All the information of the purchase requisition will be copied into the purchase order. Choose
Document Overview Off.
6. You can find the related customer address in the Delivery Address tab page.
7. If necessary, make changes in the purchase order and choose Enter.
8. Confirm any warning messages regarding price or delivery date.
9. Choose Save.
Result
The purchase order is created in the SAP system. The system creates a message for the purchase
order, so that after the Purchase Order is approved, the information from the purchase order can be
printed and transmitted to the vendor.
The printout of the sales order confirmation is executed automatically and immediately
(see settings in SAP GUI transaction VV11 for output type BA00 and defaults in your
user settings in transaction SU3); however, only in the case when the sales order is not
blocked.
You also have the possibility to start the print out manually (although only in the case when the sales
order is not blocked):

SAP ECC menu Logistics  Sales and Distribution  Sales  Order  Display
Transaction code VA03
1. Enter the order number on the Display Sales Order: Initial Screen: From the menu, choose
Sales Document  Issue Output To.
2. Mark the line with the message type BA00.
3. Choose Print.
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role menu Sales  Sales Orders  Sales Order Processing Sales
Documents Worklist
1. From the Active Queries of category Sales Orders choose the query Search (refresh the
current query if necessary).
2. Mark your sales order and choose Sales Document in PDF-Format.
3. On the Print Preview screen, choose Print.
4.3 Approval of Purchase Orders (Optional)
Use
All the purchase orders that require release by an authorized person are listed and need to be
approved.
Only POs with a value higher than 500.00 CNY can be released in this transaction.
Procedure
SAP ECC menu Logistics  Material Management  Purchasing 
Purchase Order  Release  Collective Release
Transaction code ME28
2. On the Release (Approve) Purchasing Documents screen, enter the following
values:
Release Code 01
List with items X Check the checkbox
You need a release code for PO when the document type is NB or FO and the purchase
group is 100, 101, 102, 103and the value is greater than 500.00 CNY.
3. Choose Execute.
4. A list of all POs requiring release by this release code will be displayed.
5. Select the PO line that you want to release.
6. Choose Release and then choose Save.
7. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Business role Purchasing Manager
(SAP_NBPR_PURCHASER_M)
Business role menu Purchasing  Approval  Purchasing Documents
1. Choose on the tape All Purchase order Awaiting Release(x).
2. Enter in the Search criteria Release code 01 and choose Apply.
3. Select your purchase order and choose Release purchase order.
4. The purchase order is released.
5. Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
4.4 Creating Outbound Delivery Request
Use
This activity creates an outbound delivery request for components to be shipped to the vendor.
Procedure
SAP ECC menu Logistics  Material Management  Purchasing 
Purchase Order  Reporting  SC Stocks per Vendor
Transaction code ME2O
Business role menu Warehouse Management  Shipping  Delivery Due 
Monitoring Subcontracting Stock for Vendor
2. On the SC Stock Monitoring for Vendor screen, enter the following values:
Vendor 330002
Plant 1000
Conversion SY
Type
3. Choose Execute.
4. Expand the Current Stock under YF-R1207 and YF-R1208, and then mark the check box with
Dimension WHT.
5. Choose Create Delivery.
6. Enter the following data for which you have to post the stock for the components, and confirm
with Continue (Enter).
Stor. Location 10F1
Batch <Enter the Batch>
Quantity <Enter the Quantities> The Quantities you can
find them in the row of
Requirements via SC
orders
Delivery Date <Current Date>
7. In the Delivery for SC Vendor: Display message window, the system issues 1 message:
Delivery/ies XXXXXXXX has been saved. Confirm with Continue (Enter) and record the delivery
document number.
Result
The system generates a delivery pick list for shipping.
4.5 Posting Goods Issue

Use
This activity posts the issue of goods.
Procedure
SAP ECC menu Logistics  Logistics Execution  Outbound Process 
Goods issue for Outbound Delivery  Outbound Delivery 
Change  Single Document
Transaction code VL02N
Business role menu Warehouse Management  Shipping  Outbound Delivery 
Change Delivery
2. On the Change Outbound Delivery screen, enter the delivery document number from the earlier
section and choose enter.
3. On the Delivery for Subcon. XXXXXXXX Change: Overview screen, choose the AFS Data tab
page and then choose AFS Picking.
4. Copy the values from the Quantity field to the Pick quantity field and then choose Enter.
5. Check the entries and choose Post Goods Issue.
Result
The goods issue is posted.
Delivery Note
The printout of the delivery note is executed automatically and immediately (see settings
in SAP GUI transaction VV23 for output type LD00 and defaults in your user settings in
transaction SU3).
You can also start the printout manually:

SAP ECC menu Logistics  Logistics Execution  Outbound Process  Goods
Issue for Outbound Delivery  Outbound Delivery  Display
Display Delivery
1. Enter your outbound delivery on the Display Outbound Delivery screen and choose from the
menu (NWBC: Menu…) Outbound Delivery  Issue Delivery Output.
2. Mark the line with the message type LD00 – Delivery Note
3. Choose Print.
Bill of Lading
The printout of the bill of loading is executed automatically and immediately (see
settings in SAP GUI transaction VV23 for output type YBL1 and defaults in your user
settings in transaction SU3).
You also have the possibility to start the print out manually:

SAP ECC menu Logistics  Logistics Execution  Outbound Process  Goods
Issue for Outbound Delivery  Outbound Delivery  Display
Display Delivery
1. Enter your outbound delivery on the Display Outbound Delivery screen and choose from the
menu (NWBC: Menu…) Outbound Delivery  Issue delivery Output.
2. Mark the line with the message type YBL1 – Bill of Lading
3. Choose Print.
4.6 Posting Statistical Goods Receipt

Use
After the vendor has sent the shipping notification, you post a statistical goods receipt.
Procedure

SAP ECC menu Logistics  Logistics Execution  Inbound Process  Goods
Receipt for Purchase Order, Order, Other Transactions  Enter
Goods Receipt for Purchase Order
Transaction code MIGO
2. Make the following entries:

No field name Goods Receipt Select the action from
(first field in the the input help
main screen
area)
No field name Purchase Order Select the document
(second field in type from the input
the main help.
screen area)
3. Choose Enter.
GR Goods 101
receipt
Field next to Purchase Order
Purchase Number
Order
5. Choose Enter.
6. If necessary, change the quantity in Item details (if open) or Item overview.
7. Select the Item OK or Item overview checkbox at the bottom of the screen.
8. Click the Tree display button, for each component choose Account Assignment tab and enter
1201 in the Cost Center field.
9. Choose Save.
Business role menu Warehouse Management  Receiving  Purchase Order
1. Select the query All Purchasing Documents Ready for Goods Receipt.
2. Enter the relevant search criteria. Choose Apply (refresh the current query if necessary).
3. Select your purchase order and choose Create Material Document
4. On the Goods Receipt for Purchase Order screen, if necessary change the quantity on the
Quantity tab page.
5. Select the Item OK or Item overview checkbox at the bottom of the screen.
6. Click the Tree display button, for each component choose Account Assignment tab and enter
1201 in the Cost Center field.
7. Choose Save.
8. Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Result
The system generates a material document.
To view the material document in SAP GUI, use transaction code MB51 (or menu path
Logistics  Materials Management  Inventory Management  Environment  List
Displays  Material Documents).
To view the material document in NWBC, use menu path Warehouse Management 
Material Documents), then select the material document and choose Display Material
Document.
Financial postings:
Material Debited Accounts Credited Accounts Cost Element / CO
Object
Finished 64010101 Cost of 14010101 GR/IR-
Goods (FERT) main oper. clearing accou
Raw Materials 50010101 14030101 Raw
(ROH) Consumption, raw mat Materials
4.7 Entering Invoice

Use
In this activity, you will enter an invoice.
Procedure

SAP ECC menu Logistics  Materials Management  Logistics Invoice Verification
 Document Entry  Enter Invoice
Transaction code MIRO
Business role Accounts Payable Accountant
(SAP_NBPR_AP_CLERK_S)
Business role menu Accounts Payable  Posting  Invoices  Enter Incoming Invoice
w/ PO Reference

Company Code 1000 NWBC: Choose entry
from the input help.
Transaction Invoice Choose entry from
the input help.
Invoice Date <enter date
yyyy.mm.dd >
PO number <purchase order On tab page PO
number from previous reference in lower
steps> screen area
3. Choose Enter.
4. With the purchase order information displayed, enter the invoice amount including taxes, and
select the Calculate Tax checkbox. Choose the appropriate tax code.
5. Choose Post.
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Result
The system generates a logistics invoice and an accounting document.
Financial postings:
Material Debited Accounts Credited Accounts Cost Element / CO Object
Finished 14010101 GR/IR- 22020101 AP
Goods (FERT) clearing accou domestic
22210101 input VAT
tax
4.8 Posting Outgoing Payment
Accounts Payable (158)
Use
In this activity you will post the outgoing payment.
Procedure
Using the master data from this document, complete all the activities described in the Business
Process Documentation of the scenario: Accounts Payable (158) (Chapters Post Payments Using
the Payment Program and Post Manual Outgoing payment).
4.9 Billing
Use
In this activity, you will handle billing.
Procedure
1. Access the transaction choosing the following navigation option:

SAP ECC menu Logistics  Sales and Distribution  Billing  Billing Document 
Process Billing Due List
Transaction code VF04
2. Enter the relevant search criteria, deselect the delivery related flag, select the Order-related flag
and then choose DisplayBillList (F8).
3. Select the relevant row, and choose Individual billing document.
4. Choose Save.
Business role Billing Administrator
(SAP_NBPR_BILLING_S)
Business role menu Sales  Billing
1. On the Billing screen, choose the Billing Due List tab page (refresh the current query if
necessary).
2. Expand Show Quick Criteria Maintenance, enter the relevant search criteria; select the Order-
Related flag. Choose Apply.
3. Select the lines with the sales documents you want to bill then choose Billing in Background.
4. The system will provide you with a list of the created billing documents.
Result
The system generates an invoice for billing.

Material Debited Accounts Credited Accounts Cost Element / CO Object
Finished 11220101 AR- 60010101 domestic 60010101 Sales revenue
Goods Domestic revenue dom.
(FERT) 22210105 Output tax
The print out of the invoice is executed automatically and immediately (see settings in
transaction VV33 for Output Type RD00 and defaults in your user settings in transaction
SU3).
You also have the possibility to start the print out manually:

SAP ECC menu Logistics  Sales and distribution  Billing  Billing document 
Display
Transaction code VF03
1. At the Display Billing Document, go to transaction VF03. From the menu choose
Billing document  Issue Output to.
2. Mark the line with the message type RD00.
3. Choose Print.
Business role menu Sales  Billing  Change Billing Document
1. Enter the billing document number.
2. Choose More …  Billing Document  Issue Output to.
3. Select the relevant output and choose Print.
5 Follow-up Processes
You have finished all the activities that are part of the business process described in this document.
To accomplish the subsequent activities of this business process, and using the master data from
this document, carry out the process steps described in one or more of the following scenarios.
Accounts Receivable (157)
Use
In this activity you will post the incoming payment.
Procedure
Process Documentation of the scenario: Accounts Receivable (157) (Chapters Post Payments using
Automatic Payments Program, Post Incoming Payment from Customer Manually, Automatic
Clearing of open items in customer accounts, Manual Clearing of Open items in customer accounts).
Sales: Period End Closing Operations (203) (Optional)
Use
This scenario describes the collection of periodic activities such as day ending activities, or legal
requirements.
Procedure
Process Documentation of the scenario: Sales: Period End Closing Operations (203) (Chapters
Review Incomplete SD Documents (deliveries), Review Sales Documents blocked for billing, Review
Log of collective invoice creation).
6 Appendix
6.1 Reversal of Process Steps

In the following section, you can find the most common reversal steps, which allow you to reverse
some of the activities described in this document.
Create AFS Subcontr. Order

Transaction code (SAP GUI) VA01
Reversal: Reject Sales Order Document
Transaction code (SAP GUI) VA02
Business role menu Sales Sales Orders Sales Order Processing
Change Sales Order
Comment Go to transaction VA02 and follow the menu path:
Sales Document  Delete or choose Reject document
and select appropriate reason for a rejection of all items
or go to tab strip Reason for Rejection and select
appropriate rejection reason for selected items.
Approval of Purchase Orders
Transaction code (SAP GUI) ME28

Reversal: Cancel Release of Purchase Order
Transaction code (SAP GUI) ME28
Business role Purchasing Manager
(SAP_NBPR_PURCHASER_M)
Business role menu Purchasing  Approval  Release Purchase Order –
List
Comment Go to transaction ME28, enter the release code you
wish to cancel and mark the field Cancel Release.
Select the relevant purchase order and choose Cancel
Release. Save your results.
you only cancel release before PO printed
Post Statistical Goods Receipt

Transaction code (SAP GUI) MIGO
Reversal: Cancel Goods Receipt
Transaction code (SAP GUI) MIGO
Business role menu Warehouse Management  Consumption and
Transfers  Other Goods Movement
Comment Go to transaction MIGO choose A01 - Goods Receipt
and R01 - Purchase Order from dropdowns. Enter the
Purchase Order Number for which you want to cancel
the goods receipt. Change the movement type to 102 -
GR for PO reversal and press enter. On Material tab
page in lower section, check Item OK box and save.
Invoice verification: Enter (Vendor) Invoice

Transaction code (SAP GUI) MIRO
Reversal: Reverse Invoice Document
Transaction code (SAP GUI) MIR6
Business role Accounts Payable Accountant
(SAP_NBPR_AP_CLERK_S)
Business role menu Accounts Payable  Reporting  Invoice Overview
Comment SAP GUI: Go to transaction MIR6 and select the
relevant vendor invoices by applying the appropriate
selection criteria. From the results select the relevant
row, and double-click the document number. Choose

Invoice document  Reverse. Select a reversal reason
and a posting date in the dialog box.
NWBC: Select the relevant line and choose Reverse
Document
Billing
Transaction code (SAP GUI) VF04
Reversal: Cancel Billing document
Transaction code (SAP GUI) VF11
Business role menu Sales  Billing  Cancel Billing Document
Comment Go to transaction VF11, enter the relevant billing
document number, choose Enter and save your result.
An invoice cancellation document has been created
balancing the original invoice.
6.2 Reporting
Use
The table below lists the reports that you can use to obtain additional information on this business
process.
You can find detailed descriptions of the individual reports in the following BPD
documents, which provide a comprehensive compilation of all important reports:
 Financial Accounting: SAP ERP Reports Accounting (221)
 Logistics Processes: SAP ERP Reports for Logistics (222)
Note that the descriptions of some reports that are an indispensable part of the process flow may be
located directly in the section where they belong.
Reports
Report title Transactio Business role Business role Comment
n code (NWBC) menu (NWBC)
(SAP GUI)
List of Sales VA05 Warehouse Warehouse A list of all
Orders Manager Management  selected sales
Warehouse Inventory Control  orders is
Manager Stock Overview displayed.
(SAP_NBPR_WAR
EHOUSEMANAGE
Report title Transactio Business role Business role Comment

n code (NWBC) menu (NWBC)
(SAP GUI)
R_M)
List Billing VF05 Sales Manager Sales  Sales A list of all
Documents (SAP_NBPR_SALE Orders  Reports selected billing
SPERSON_M)  List Billing documents is
Documents displayed.
Purchase ME5K Purchasing Purchasing  A list of

Requisition per Manager Reporting  purchase
Account (SAP_NBPR_PUR Purchasing requisitions
Assignment CHASER_M) Document which are
Evaluation  assigned to a
Requisitions by sales order
Account
Assignment
Purchase ME2K Purchasing Purchasing  A list of
Orders by Manager Reporting purchase
Account (SAP_NBPR_PUR Purchasing orders which
Assignment CHASER_M) Document are assigned to
Evaluation  a sales order
Purch. Orders by
Account
Assignment
Incomplete SD V.02 Sales Manager Sales  Sales A list of all
Documents (SAP_NBPR_SALE Orders  Reports incomplete
SPERSON_M)  List of documents on
Incomplete Sales the basis of the
Orders specified
selection
criteria is
displayed.
6.3 Used Forms

Use
In some of the activities of this business process, forms were used. The table below provides details
on these forms.
Common Form Type Used in Process Step Output
Technical Name
Form Name Type
Purchase SmartForm Convert Assigned NEU YBCN_MMPO
Order Requisitions into Purchase
Orders
Order SmartForm Sales Order Entry BA00 YBCN_AFS_SDORC
Confirmation
Delivery SmartForm Post Goods Issue LD00 YBCN_AFS_SDDLN

Note
Bill of SmartForm Post Goods Issue YBL1 YBCN_AFS_SDBLD
Lading
Sales SmartForm Billing Processing RD00 YBCN_AFS_SDINV
Invoice

AF6_ERP606_BPD_EN_CN

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AF6_ERP606_BPD_EN_CN

Uploaded by

Copyright:

Available Formats

EHP6 for SAP ERP

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

National product specifications may vary.

Business Process Alternative/Decision Choice

Type Style Description

AFS - Outsourced Manufacturing

2.1 Master Data and Organizational Data

Additional Master Data (Default Values)

Using Your Own Master Data

Master / org. data Value Master / org. data details Comments

2.2 Business Conditions

Business role Technical name Process step

2.3.1 Defining Queries for Personal Object Worklist (POWL)

2.4 Preliminary Steps

Option 1: SAP Graphical User Interface (SAP GUI)

Transaction code MIGO

Action Goods Receipt

Movement type 501

Material Debited Credited Accounts Cost Element / CO Object

3 Process Overview Table

Creating Purchaser ME21N Purchase

Approval of Purchasing ME28 Purchase

Creating Warehouse ME2O Outbound

Posting Warehouse VL02N Goods issue is

Post Warehouse MIGO Goods receipt

Outgoing See See scenario See See scenario

Process Step External Business Business Transaction Expected

Incoming Accounts Accounts See See scenario

4.2 Creating Purchase Order

Option 1: SAP Graphical User Interface (SAP GUI)

Option 1: SAP Graphical User Interface (SAP GUI)

4.3 Approval of Purchase Orders (Optional)

4.4 Creating Outbound Delivery Request

4.5 Posting Goods Issue

Option 1: SAP Graphical User Interface (SAP GUI)

Option 1: SAP Graphical User Interface (SAP GUI)

4.6 Posting Statistical Goods Receipt

Option 1: SAP Graphical User Interface (SAP GUI)

2. Make the following entries:

4.7 Entering Invoice

Option 1: SAP Graphical User Interface (SAP GUI)

2. Make the following entries:

4.8 Posting Outgoing Payment

Accounts Payable (158)

Option 1: SAP Graphical User Interface (SAP GUI)

The system generates an invoice for billing.

Option 1: SAP Graphical User Interface (SAP GUI)

Accounts Receivable (157)

Sales: Period End Closing Operations (203) (Optional)

6.1 Reversal of Process Steps

Create AFS Subcontr. Order

Approval of Purchase Orders

Transaction code (SAP GUI) ME28

you only cancel release before PO printed

Post Statistical Goods Receipt

Invoice verification: Enter (Vendor) Invoice

row, and double-click the document number. Choose

Report title Transactio Business role Business role Comment

Purchase ME5K Purchasing Purchasing  A list of

6.3 Used Forms

Delivery SmartForm Post Goods Issue LD00 YBCN_AFS_SDDLN

You might also like