910 BPP en US Make to Order (Process Industry)

EHP5 for SAP ERP 6.0June 2011English

Make-to-Order (Process Industry) (910)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Documentation

SAP Best Practice Make-to-Order (Process Industry) (910): BPD

Copyright 2011 SAP AG. 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.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, 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.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. 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 AG Page 2 of 28


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example textWords 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 TEXTKeys 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.

Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

SAP AG Page 3 of 28


Contents Make-to-Order (Process Industry)................................................................................................5

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 Explanation of Material Requirements Planning...................................................................8

3 Process Overview Table...........................................................................................................10

4 Business Process Steps...........................................................................................................11

4.1 Create Planned Independent Requirements......................................................................11

4.2 Execute MRP-Planning......................................................................................................12

4.3 Create Sales Order............................................................................................................13

4.4 Execute Material Resource Planning.................................................................................14

4.5 Convert Planned Order into Process Order for Filling........................................................15

4.6 Release Process Order for Filling.......................................................................................16

4.7 Confirm Process Order for Filling.......................................................................................17

4.8 Post-Process Control for GranuSAP, Blue.........................................................................18

4.9 Create Outbound Delivery..................................................................................................20

4.10 Post Goods Issue for Outbound Delivery.........................................................................21

4.11 Billing................................................................................................................................ 22

5 Follow-Up Processes................................................................................................................24

5.1 Accounts Receivable .........................................................................................................24

5.2 Period End Closing.............................................................................................................24

6 Appendix................................................................................................................................... 25

6.1 Reversal of Process Steps.................................................................................................25

6.2 SAP ERP Reports..............................................................................................................27

SAP AG Page 4 of 28


Make-to-Order (Process Industry)

1 PurposeMake to order processing is used to sell certain specialty chemicals which are filled and packed only after a sales order is received.

The filled material is planned in order to plan the dependent requirement of the bulk. The MRP run is used to plan the requirements.

Bulk is manufactured and kept in stock based on the dependent requirements of the filled material.

On receipt of the sale order for the filled material the MRP triggers a planned order for the filled material for the sale order quantity. This planned order can be converted in to a process order to execute the filling process.

The filled material is goods received to sales order stock and then delivered the customer.

2 Prerequisites

2.1 Master Data and Organizational DataDefault ValuesEssential 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.

The business process is enabled with this organization-specific master data, examples are provided in the next section.

Additional Default ValuesYou 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 DataYou 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:

Manufacturing / TradingProduction Plant

SAP AG Page 5 of 28


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

Material CH-6000

Material CH-6200

Customer C-1000

Plant 1000

Sales organization 1000

Distribution channel 10

Division 10

2.2 Business ConditionsThe 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 Document

Costing run needs to be carried out Final Steps documentation

Check and change MM period to current period Final Steps documentation

Initial stock postings Final Steps documentation

2.3 Roles

UseThe 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.

PrerequisitesThe business roles have been assigned to the user who is testing this scenario.

Business role Technical name Process step

Employee (Professional User)

SAP_NBPR_EMPLOYEE_S Assignment of this role is necessary for basic functionality.

Production Planner SAP_NBPR_PRODPLANNER_S Create planned independent RequirementsCarry out MRP RunRelease Process order

Sales Administrator

SAP_NBPR_SALESPERSON_S Create Sales OrderCreate Delivery

Shop Floor SAP_NBPR_SHOPFLOOR_S Convert planned order to

SAP AG Page 6 of 28


Business role Technical name Process step

Specialist process orderConfirm Process Order

Quality Specialist SAP_NBPR_QUALMGR_S Results Recoding WorklistRecord Usage Decision

Warehouse Clerk SAP_NBPR_WAREHOUSECLERK_S Change Outbound Delivery

Billing Administrator

SAP_NBPR_BILLING_S Create Billing

SAP AG Page 7 of 28


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).

Business Role

Application Object Type

Variant Name

Variant Selections

Selection Criteria

Query Name

Production Planner

Create Process Order

Process Order Worklist

YB_PROCESS_H Process Order Worklist

Shop Floor Specialist

Confirming Process Order

Process Order Confirmation Worklist

YB_PROCESS_H Process Order Confirmation Worklist

2.4 Explanation of Material Requirements Planning2.4.1 Facilities Provided

PrerequisitesThe Material Requirements Planning scenario provides a one-year planning basis for materials at a plant. Planned orders (for production) or purchase requisitions (for purchasing) are generated across all bill of material levels on the basis of independent requirements and stock levels.

To execute the planning run, independent requirements must have been defined and a strategy group must have been assigned to the materials.

Material Material text Plant Strategy Reasonable monthlyquantity

MRP controller

CH-6200

GranuSAP blue, 25 LB 1000 52

for example, 40,000 LB YQ1

ProcedureMaterial requirements planning takes place in two steps:

1. Creation of independent requirements

2. Execution of the planning run

Material requirements planning is controlled via planning strategies.

2.4.2 Planning Strategy 52This strategy is used to make bulk material before a sales order is received for the finished product.

The material is produced up to the level before filling (as bulk material), and is put into storage until a sales order arrives.

Filling is not initiated until the sales order has been received.

SAP AG Page 8 of 28


With this strategy, a planned order is generated by the MRP run after a sales order is received for the filled material.

Independent requirements are input on the finished product level in this strategy.

These independent requirements generate special planned orders which only have an impact on production (i.e. become convertible into a process order) when the sales order has been received for the filled material

On all lower production levels (bulk materials, raw materials); independent requirements trigger production and procurement.

Filling is not initiated until the sales order is received.

The sales orders for this strategy are input as individual customer requirements, and are managed as an individual section in material requirements planning.

When a sales order arrives, independent requirements are set off against the quantity of the sales order.

A separate planned order which can be implemented is generated for the quantity stated in the sales order.

If the planned order quantity is not used completely by the sales order, the remaining quantity is retained.

If the sales order exceeds independent requirements, the planned order quantity is increased.

Planning level: Filled material

Stocking level: Bulk material

SAP AG Page 9 of 28


3 Process Overview TableProcess step External

process reference

Business condition

Business role Trans-action code

Expected results

Create Planned Independent Requirements

Production Planner

MD61

Execute MRP-Planning

Production Planner

MD02

Create Sales Order

Sales Administration

VA01

Execute Material Resource

Production Planner

MD02

Convert Planned Order into Process Order for Filling


COR7

Release Process Order for Filling

Production Planner

COR2

Confirm Process Order for Filling


CORK

Results Recording Worklist

Quality Specialist

QE51N

Record Usage Decision

Quality Specialist

QA11

Create Outbound Delivery

Sales Administration

VL01N

Post Goods Issue for Outbound Delivery

Warehouse Clerk

VL02N

Billing Billing Administrator

VF01

SAP AG Page 10 of 28

SAP Best Practice Make to Order (Process Industry): BPD

4 Business Process Steps

4.1 Create Planned Independent Requirements

UseThis section describes how to create independent requirements for a material.

Procedure1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics Production DRP Planning Demand Management Create

Transaction code

MD61

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role Production Planner (SAP_NBPR_PRODPLANNER_S )

Business role menu

Production Production Planning Demand Management Create Planned Indep. Requirements

2. On the Create Planned Independent Requirements: Initial Screen, select the Material view.

3. Make the following entries:

Field name Description User action and values

Comment

Material CH-6200 Accordingly also for other materials

Plant 1000 Plant 1000

Version 00

Planning horizon From...To

Leave default

Planning period M or W M for monthly, W for weekly planning

4. Choose Enter.

5. On the Plnd Ind. Reqmnts Create: Planning Table screen, make the following entries for each material you want to plan:

Field name Description User action and values Comment

Planned quantity For example, 30000 LB

6. Choose Save.

7. Choose Back (F3) 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).

4.2 Execute MRP-Planning

UseThe MRP-planning usually runs once or twice a day for all materials. To speed up the process it can be manually started for single materials.



SAP ECC menu Logistics Production - Process MRP Planning Multilevel Single-Item Planning

Transaction code

MD02


Business role Production Planner (SAP_NBPR_PRODPLANNER_S)

Business role menu Production MRP Planning MRP - Single-Item, Multi- Level

2. On the Single-Item, Multi-Level screen, make the following entries:


Material Ch-6200 material from sales order

Plant 1000

Processing Key NETCH

Create Purchase Req. 2

Detailed settings may vary, according to MRP strategy

SA Deliv. Sched. Lines 3

Create MRP list 1

Planning mode 1

Scheduling 1

Also plan unchanged components Flag set

Display results before they are saved Blank

Display material list Blank

Simulation mode Blank

3. Choose Enter twice.

4. After the Single-Item, Multi-Level MRP list is displayed, choose Back to finish the transaction.




Or


ResultMRP generated convertible planned order for the finished fill material. The Planned independent requirement for the filled material is reduced by the same order quantity.

4.3 Create Sales Order

UseThe sales order is the necessary trigger for the tank trailer management process.

PrerequisitesThe required master data must be maintained in the system.



SAP ECC menu Logistics Sales and Distribution Sales Order Create

Transaction code VA01Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

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 following data.


Order Type YQOR Standard Order

Sales Organization 1000

Distribution Channel 10 Direct Sales

Division 10 Product Division 01

3. Choose Enter.

4. On the Create Standard Order-Chem: Overview screen, enter the following data.


Comment

Sold-To Party

C-1000

PO Number Purchase order number

Any

Req. deliv. date

Desired delivery date

For example, current date + one week




Comment

Material CH-6200 SAPulat, Raw Granulate

Order Quantity

400 Bag

5. Choose Enter.

6. Ignore the message Change in invoice date: The billing date is redetermined

7. If the Standard Order Chem: Availability Control screen displays, choose Continue dlv.

8. Save your entries.


Or


4.4 Execute Material Resource Planning

UseThe material resource planning usually runs once or twice a day for all materials. To speed up the process it can be manually started for single materials.



SAP ECC menu Logistics Production - Process MRP Planning Multilevel Single-Item Planning

Transaction code

MD02


Business role Production Planner(SAP_NBPR_PRODPLANNER_S)

Business role menu Production MRP Planning MRP-Single-Item, Multi-Level

2. On the Single-Item, Multi-Level screen, make the following entries:


Material material from sales order

Plant 1000

Processing Key NETCH

Create Purchase Req. 2 Detailed settings may vary, according to MRP strategySA Deliv. Sched. Lines 3

Create MRP list 1



Planning mode 1

Scheduling 1

Also plan unchanged components Flag set

Display results before they are saved Blank

Display material list Blank

Simulation mode Blank

3. Choose Enter twice.

4. After the Single-Item, Multi-Level MRP list is displayed.


Or


ResultMRP generated convertible planned order for the finished fill material. The Planned independent requirement for the filled material is reduced by the same order qty.

4.5 Convert Planned Order into Process Order for Filling

UseTo fill the material CH-6200, the planned order must be converted into a process order.

Prerequisites A planned order for material CH-6200 is only necessary if stock for production of CH-6200 is not sufficient.



SAP ECC menu

Logistics Production - Process MRP Planned Order Convert to Process Order Individual Conversion

Transaction code COR7


Business role Shop Floor Specialist(SAP_NBPR_SHOPFLOOR_S)

Business role menu

Shop Floor Repetitive Order Processing Convert Planned Order to Proc. Order

2. On the Create Process Order: Initial Screen, make the following entries:




Planned Order < planned order > press F4 for material CH-6200

3. Choose Enter.

4. On the Create Process Order: Header General Data screen, save your entries.

5. Make a note of the process order number: _________


Or


ResultA process order for filling has been created.

4.6 Release Process Order for Filling

UseThe release step triggers the batch determination within the process order and indicates the physical beginning of the filling process.



SAP ECC menu Logistics Production - Process Process Order Process Order Change

Transaction code COR2Access through MD04

Double-Click on the process order in MD04 and choose the Change button.

2. On the Change Process Order: Initial Screen, make the following entries:


Process order < process order >

3. Choose Enter.

4. On the Change Process Order: Header General Data screen, choose Release (Ctrl+F6).

5. Save the process order.


Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role


Business role menu

Production Shopfloor Control Process Order Process Order Work List



1. Select the active query Process Order Worklist (Query name as defined in chapter Error: Reference source not found)

Choose Refresh if your order is not displayed.

2. On the Process Order Worklist screen, select the process order and from the menu, choose Process Order Change Process Order.

3. On the Change Process Order: Header General Data screen, choose Release (Ctrl+F6).

4. Save the process order.

5. Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

ResultThe availability check for the components is performed. The batch determination for CH-3200 has selected a batch. The process order for filling is released.

4.7 Confirm Process Order for Filling

UseThe Confirmation triggers the material movements for the process order and indicates the physical end of the filling process.



SAP ECC menu Logistics Production - Process Process Order Confirmation Enter for Order

Transaction code CORK

2. On the Enter Process Order Confirmation: Initial Screen, make the following entries:


Process Order

3. Choose Enter.

4. On the Process Order Comfirmation Enter: Actual Data screen, make the following entries:


Yield t/b Conf. Enter/Adjust quantity to confirm

5. Save the process order confirmation.

6. On the Shelf Life/Expiry Date screen, in the Expiry date/Manu. date field, enter a appropriate date.

7. Choose Enter.


Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Shop Floor Specialist



(SAP_NBPR_SHOPFLOOR_S)

Business role menu

Shop Floor Process Order Processing Process Order Confirmation Worklist

1. Select the active query Process Order Confirmation Worklist (Query name as defined in chapter Error: Reference source not found).

Choose Refresh if your order is not displayed.

2. On the Process Order Confirmation Worklist screen, Select the Process order and from the menu, choose Confirm Process Order Confirmations (Total).

3. On the Process Order Comfirmation Enter: Actual Data screen, make the following entries:


Yield t/b Conf. Enter/Adjust quantity to confirm

4. Save the process order confirmation.

5. On the Shelf Life/Expiry Date screen, in the Expiry date/Manu. date field, enter a appropriate date.

6. Choose Enter.

7. Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

ResultWhile saving the confirmation the system performs the goods issue movements for the components and the goods receipt for the packed material CH-6200 which is immediately available in unrestricted stock and can be sold with the following steps.

4.8 Post-Process Control for GranuSAP, Blue4.8.1 Results Recording Worklist

UseAs the final step in the inspection process, a visual check of the packaging is done. In this process step, the appropriate batch is evaluated concerning its usage.



SAP ECC menu Logistics Quality Management Quality Inspection Worklist Results Recording

Transaction code

QE51N


Business role Quality Specialist(SAP_NBPR_QUALMGR_S)

Business role Quality Management Quality Inspection Inspection Results



menu Results Recording Worklist

2. On the Results Recording Worklist screen, make the following entries:


Plant 1000

Inspection lot origin 04

Material CH-6200

3. Choose Execute (F8).

4. On the Record Results: Characteristics Overview screen, expand the menu tree and choose the correct inspection lot.

5. On the Record Results: Characteristic Overview screen, make the following entries:


Visual check (Packaging) 1Color comparison 01Density Between 0.935 and 0.945Crystallite melting point Between 258.8. and 274.3

6. Choose Enter.

7. The valuation of the characteristics (accept / reject) occurs automatically. Otherwise the user can select all items and choose Close.



Or


ResultThe QM inspection results have been recorded in the appropriate inspection lot.

4.8.2 Record Usage Decision

UseIn this process step, the appropriate batch will be evaluated concerning its usage.



SAP ECC menu

Logistics Quality Management Quality Inspection Inspection Lot Usage Decision Record

Transaction code

QA11


Business role Quality Specialist



(SAP_NBPR_QUALMGR_S)

Business role menu

Quality Management Quality Inspection Inspection Lot Record Usage Decision

2. On the Record Usage Decision: Initial Screen, make the following entries:


Comment

Inspection Lot

inspection type YQ04 for CH-6200

3. Choose Enter.

4. On the Record Usage Decision: Characteristics Overview screen, make the following entries:

Field name

Description User action and values Comment

UD code

Open the match code of this field and choose the appropriate option in the appearing menu tree.

For example: A

5. Choose Save.

For material CH-6200, the lot quantity will be posted into the unrestricted or restricted use according to the performed usage decision.

6. Accept the message A pull derivation will be performed by choosing Enter.


Or


ResultThe usage decision for inspection lot will be saved. As a result, the material will be posted into the unrestricted or restricted use according to the performed usage decision.

4.9 Create Outbound Delivery

UseYou can create a single outbound delivery for exactly one order, if you know the order number. Only the order items from this order that are due for shipment will be included in the delivery. You can make changes to the shipping data, if necessary.

PrerequisitesIf the order is blocked for credit limit check, use transaction VKM1 for release.



SAP ECC Logistics Sales and Distribution Shipping and Transportation



menu Outbound Delivery Create Single Document With Reference to Sales Order

Transaction code

VL01N


Business Role Warehouse Clerk (SAP_NBPR_WAREHOUSECLERK_S)

Business Role Menu

Warehouse Management Shipping Outbound Delivery Create Delivery

2. On the Create Outbound Delivery with Order Reference Screen, make the following entries:


Shipping point

1000

Selection date

Enter Delivery Date for the Confirmed Qty.

Look up confirmed delivery date in the sales order

Order Enter number of sales order created above

3. Choose Enter.

4. On the Delivery Create: Overview screen save the delivery.


Or


ResultThe delivery for shipping the relabeled material to the customer has been saved. A batch determination for the material has been carried out.

4.10 Post Goods Issue for Outbound Delivery

UseThe goods issue movement reduces the system inventory and is usually performed while or after the material physically leaves the plant.


SAP ECC menu

Logistics Sales and Distribution Shipping and Transportation Outbound Delivery Change Single Document

Transaction code

VL02N


Business role Warehouse Clerk



(SAP_NBPR_WAREHOUSECLERK_S)

Business role menu

Warehouse Management Shipping Outbound Delivery ChangeDelivery

2. On the Change Outbound Delivery screen, make the following entries:


Outbound Delivery < delivery number >

3. Choose Enter.

4. On the Delivery xxx Change: Overview screen, choose the Picking tab .

5. Make the following entries: (for batch material, choose Batch Split Exists of the delivery item):


Comment

Batch Split Indicator

ButtonBatch Structure

Only for batch materials

Picked Qty XXX In the line with batch assignment

6. Choose Post Goods Issue to post the goods issue.

7. The system displays the message Outbound Delivery xxx has been saved.


Or


ResultThe delivery for shipping the relabeled material to the customer has been issued. The inventory in the system has been reduced.

4.11 BillingOnce the goods issue has been posted, the delivery can be invoiced. The pricing data is transferred from the order. Only the taxes are re-determined when the billing document is created.

PrerequisitesA delivery with goods issue posting is required for billing.



SAP ECC menu Logistics Sales and Distribution Billing Billing Document Create

Transaction code

VF01




Business role Billing Administrator (SAP_NBPR_BILLING_S)

Business role menu Sales Billing Create Billing Document

2. On the Create Billing Document screen make the following entries:


Document

3. Choose Enter.

4. On the Invoice (F2) Create: Overview of Billing Items screen check the data.



Or


ResultA billing document has been generated. The document has completed status.

The corresponding documents were generated for financial accounting, profitability analysis and cost center accounting.



5 Follow-Up ProcessesYou have finished all activities that are part of the business process described in this document.

To accomplish subsequent activities of this business process, carry out the process steps described in one or more of the following scenarios, using the master data from this document.

5.1 Accounts Receivable

Accounts Receivable (157)

UseIn this activity you post the incoming payment.

Complete all activities described in the Business 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) using the master data from this document.

5.2 Period End Closing

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

UseThis scenario describes the collection of periodic activities such as day ending activities or legal requirements like Intrastat and Extrastat reporting.

ProcedureComplete all activities described in the Business Process Documentation of the scenario: Sales: Period End Closing Operations (203) (in the following sections: Review Incomplete SD Documents (deliveries), Review Sales Documents blocked for billing, Review Log of collective invoice creation) using the master data from this document.

Period End Closing "General" Plant (181)

UseIn this activity, you perform the period end financial accounting activities for the plant.

These are executed collectively as a part of month-end closing. For more information on the month-end closing procedure, see the Business Process Documentation for Period End Closing "General" Plant (181).

Month-end closing can only be executed once a month.



6 Appendix

6.1 Reversal of Process StepsIn the following section, you can find the most common reversal steps, which you can take to reverse some of the activities described in this document.

Sales Order Entry

Transaction code ( SAP GUI) VA01

Reversal: Delete Sales Document

Transaction code ( SAP GUI)

VA02

Business role Sales Administrator(SAP_NBPR_SALESPERSON_S)

Business role menu Sales Sales Orders Sales Order Processing Change Sales Order

Comment Select menu Sales Document Delete

Delivery Process

Transaction code ( SAP GUI) VL01N

Reversal: Delete Delivery


VL02N

Business role Warehouse Clerk(SAP_NBPR_WAREHOUSECLERK_S)

Business role menu Warehouse Management Shipping Outbound Delivery Change Delivery

Comment From the menu, choose Outbound Delivery Delete

Picking

Transaction code ( SAP GUI) VL06O

Reversal: Remove Picking Quantity from Delivery Item


VL02N


Business role menu Warehouse Management Shipping Outbound Delivery Change Delivery

Comment



Post Goods Issue

Transaction code ( SAP GUI) VL02N

Reversal: Reverse Goods Issue.


VL09


Business role menu

Warehouse Management Shipping Outbound Delivery Cancel Goods Issue for Delivery Note

Comment

Create Independent Requirements

Transaction code (SAP GUI) MD61

Reversal: Change Independent Requirements

Transaction code (SAP GUI)

MD62


Business role menu

Production Production Planning Demand Management Change Planned Indep. Requirements

Comment Delete line items in planning table. MRP has to be rerun to correct dependent requirements

Convert Planned Order to Process Order


COR8

Reversal: Change Process Order Restrict Processing


COR2


Business role menu

Production Shopfloor Control Process Order Process Order Work List

Comment It is not possible to delete process orders directly (deletion may only occur via archiving). Instead, further processing is restricted, so that goods movements and cost postings with reference to the restricted orders is not longer allowed



Select Technical completion if costs have already been posted with order reference, in order to allow further order settlement. Selection of Lock will not only block logistics movements but also order settlement. Final order closure is only possible if the order balance is zero.

Material Staging for Order

Transaction code (SAP GUI) MF60

Reversal: Cancel material document


MBST


Business role menu

Warehouse Management Consumption and Transfers Cancel Material Document

Comment The material posting of the material document is reversed. The original document remains in the systems database

Process Goods Issue of batch-managed components

Transaction code (SAP GUI) COIK, MIGO

Reversal: Cancel material document


MBST


Business role menu

Warehouse Management Consumption and Transfers Cancel Material Document

Comment The material posting of the material document is reversed. The original document remains in the systems database

6.2 SAP ERP Reports

UseThe table below lists the reports that you can use to obtain additional information on this business process.

ReportsReport title

Transaction code

NWBC Business Role

Business Role Menu Comment

Capacity CM01 Production Production Capacity The capacity



Planning Planner Planning Capacity Planning Cap. planning, work center load

evaluation is displayed.

Missing Parts Info System

CO24 Production Planner

Production Evaluations Reports MissingPartsInfoSyst

A list of missing parts.

Process Order Information System

COOISPI Shop Floor Specialist

Shop Floor ProcessProcess Order Confirmation Worklists

A list of all process orders.

MRP List MD05 Production Planner

Production Evaluations Reports MRP List Individual Display

The stock/requirements situation at the time of the last planning run.

Stock Overview

MMBE Warehouse Manager

Warehouse Management Inventory Control Environment Stock Overview

A list of stock is displayed.

List of Sales Orders

VA05 Sales Manager

Sales Sales Orders Reports List of Sales Orders

A list of all selected sales orders is displayed.

List Billing Documents

VF05 Sales Manager

Sales Sales Orders Reports List Billing Documents

A list of all selected billing documents is displayed.


Make-to-Order (Process Industry)1 Purpose2 Prerequisites2.1 Master Data and Organizational Data2.2 Business Conditions2.3 Roles2.3.1 Defining Queries for Personal Object Worklist (POWL)

2.4 Explanation of Material Requirements Planning2.4.1 Facilities Provided2.4.2 Planning Strategy 52

3 Process Overview Table4 Business Process Steps4.1 Create Planned Independent Requirements4.2 Execute MRP-Planning4.3 Create Sales Order4.4 Execute Material Resource Planning4.5 Convert Planned Order into Process Order for Filling4.6 Release Process Order for Filling4.7 Confirm Process Order for Filling4.8 Post-Process Control for GranuSAP, Blue4.8.1 Results Recording Worklist4.8.2 Record Usage Decision

4.9 Create Outbound Delivery4.10 Post Goods Issue for Outbound Delivery4.11 Billing

5 Follow-Up Processes5.1 Accounts Receivable5.2 Period End Closing

6 Appendix6.1 Reversal of Process Steps6.2 SAP ERP Reports