+ All Categories
Home > Documents > 111_ERP607_BPD_EN_US

111_ERP607_BPD_EN_US

Date post: 26-Nov-2015
Category:
Upload: amar1980
View: 9 times
Download: 0 times
Share this document with a friend
Description:
en
Popular Tags:
32
EHP7 for SAP ERP 6.0 September 2013 English Returns and Complaints (111) Business Process Documentation
Transcript

Business Process Procedures

EHP7 for SAP ERP 6.0September 2013English

Returns and Complaints (111)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyBusiness Process Documentation

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

IconMeaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type StyleDescription

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 textEmphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXTNames 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 textScreen 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 textExact 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.

Contents

5Returns

51Purpose

52Prerequisites

52.1Master Data and Organizational Data

72.2Business Conditions

72.3Roles

72.4Defining Queries for Personal Object Worklist (POWL)

103Process Overview Table

124Process Steps

124.1Create Return Order

144.2Create Return Delivery

154.3Assign Serial Number

174.4Post Goods Issue

184.5Billing

194.6Post Outgoing Payment

215Follow-Up Processes

236Appendix

236.1Reversal of Process Steps

246.2SAP ERP Reports

266.3Used Forms

Returns and Complaints 1 Purpose

This scenario describes sales order returns processing. The process starts a return sales order with reference to the original invoice for the goods. An RMA document is printed, and forwarded to the customer to be attached to the incoming goods. The goods are shipped back, a return delivery is created with reference to the RMA, and the material is received into return stock. The return stock location is set to be non-MRP relevant. The goods are inspected, resulting in a disposition to either return them to stock, or scrap. A credit memo is created from the billing run, and posted to the customer's account.

2 Prerequisites

2.1 Master Data and Organizational DataDefault 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.The business process is enabled with this organization-specific master data, examples are provided in the next section.

Additional 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. dataValueMaster / org. data detailsComments

MaterialH11Trading Good for Reg. Trading (MRP planning)

no Serial no.; no batchSee sections Business Conditions and Preliminary Steps.

MaterialH12Trading Good for Reg. Trading (reorder point planning)

no Serial no.; no batchSee sections Business Conditions and Preliminary Steps.

MaterialH20Trading Good for Reg. Trading (reorder point planning)

with serial numbers, no batchOnly use if you have activated the building block Serial Number Management (126).

See the sections Business Conditions and Preliminary Steps.

MaterialH21Trading Good for Reg. Trading (reorder point planning)

no Serial no.; batch controlled (Exp. Date)Only use if you have activated the building block Batch Management (117).

See sections Business Conditions and Preliminary Steps.

MaterialH22Trading Good for Reg. Trading (reorder point planning)

no Serial no.; batch controlled (FIFO strategy)Only use if you have activated the building block Batch Management (117).See sections Business Conditions and Preliminary Steps.

MaterialF29Finished Good MTS for Process Industry (PD planning)

no Serial no.; with batch (Exp. Date)Only use if you have activated the building block Batch Management (117).See sections Business Conditions and Preliminary Steps.

MaterialF126Finished Good MTS for Discrete Industry (PD planning)

with Serial no.; with / w/o batch (FIFO strategy)Only use if you have activated the building block Serial Number Management (126).

See sections Business Conditions and Preliminary Steps.

Sold-to party100000Domestic Customer 00You can test the scenario using another domestic customer.

Ship-to party100000Domestic Customer 00

Payer100000Domestic Customer 00

Plant1000(1100)

Storage Location1060(1160)

Shipping Point100R(110R)

Sales organization1000

Distribution channel10

Division10

2.2 Business Conditions

The business process described in this Business Process Documentation is part of a bigger chain of integrated business processes or scenarios. As a consequence, you must have completed the following processes and fulfilled the following business conditions before you can start going through this scenario:

Business conditionScenario

You have completed all relevant steps described in the Business Process Documentation Prereq. Process Steps (154).Prereq. Process Steps (154)

To run through this scenario, you must already have sold some goods.Sales Order Processing: sale from stock (109)

2.3 Roles

Use

To test this scenario in the SAP NetWeaver Business Client (NWBC), ensure that the following roles are installed and assigned to the users testing this scenario. These roles are only required 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 RoleTechnical NameProcess Step

Employee (Professional User)SAP_NBPR_EMPLOYEE_SAssignment of this role is necessary for basic functionality.

Sales AdministratorSAP_NBPR_SALESPERSON_SCreate Return Order

Warehouse ClerkSAP_NBPR_WAREHOUSECLERK_SCreate Return Delivery and Post GR

Billing AdministratorSAP_NBPR_BILLING_SBilling

2.4 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 about query creation, see the Creation of Queries in Personal Object Working Lists (POWLs) section in this package's Quick Guide document (found on the package's SAP Note).1. Access the activity choosing the following navigation option:Business role Sales Administrator

(SAP_NBPR_SALESPERSON_S)

Business role menuSales Sales Orders Sales Order Processing Sales Documents Worklist

2. Choose the Define New Query link. A process template takes you through the individual steps. You work through the specified steps and define the following data:

3. For selecting the Object Type make the following entries:

Field nameUser action and valuesComment

Select Object TypeSales DocumentsBy selecting an object type, you choose one of the pre-defined types of the POWL.

Select an Existing Query As Templaten/aYou can use a template for the selected Object Type if one exists.

4. Choose the Next button.

5. Maintain selection criteria for your query as required.Field nameUser action and valuesComment

SD document categ.H

(= Returns)

Sales Document Type

*Asterisk as wildcard

6. Via the Preview button, you can get a test view of the list.

7. Next to the Preview button you find the Criteria Personalization link where you can select additional fields for the quick search.8. Choose Next.

9. Make the following entries:

Field nameUser action and valuesComment

Enter Query DescriptionAll ReturnsExample of Query Description

Activate QuerySelect checkbox to activate the query.

Select CategoryReturnsIf required create new category by choosing Create New Category

10. Choose Finish.

Result

You can now process the scenario Complaints (111).3 Process Overview Table

Process StepExternal Process ReferenceBusiness ConditionBusiness RoleTrans-action CodeExpected Results

Create Return OrderCustomer request to return goodsSales AdministratorVA01Return order created, RMA form printed

Create Return DeliveryGoods arrival on shipping dockWarehouse ClerkVL01NDelivery document created

Assign Serial NumberWarehouse ClerkVL02NSerial numbers are assigned to the materials

Post Goods IssueWarehouse ClerkVL06OThe goods receipt is posted.

BillingGoods are receipted into system per returns deliveryBilling AdministratorVF04Credit posted, document printed

Outgoing PaymentAccounts Receivable (157)See scenario no. 157See scenario no. 157See scenario no. 157

Return to VendorReturn to Vendor (136)See scenario no. 136See scenario no. 136See scenario no. 136

Stock Usage Blocking and ScrappingStock Handling: Scrap and Blocked Stock (131) (optional)See scenario no. 131See scenario no. 131See scenario no. 131

Rework Processing (Stock-Manufactured Material)Rework Processing (Stock-Manufactured Material) (151)See scenario no. 151See scenario no. 151See scenario no. 151

Closing OperationsSales: Period End Closing Operations (203)See scenario no. 203See scenario no. 203See scenario no. 203

4 Process Steps4.1 Create Return OrderUse

In this activity, you create the return order.Prerequisites

You must have a reference invoice number and a billing document according to Sales Order Processing: sale from stock (109).

Procedure

Option 1: SAP Graphical User Interface (SAP GUI)1. Access the transaction using the following navigational option:

SAP ECC MenuLogistics Sales and Distribution Sales Order Create

Transaction CodeVA01

If you have installed the Rebate Processing: Free Goods scenario in your system and you use material H11, the following warning may display: Minimum quantity 1,000 EA of free goods has not been reached. To skip this warning, choose Enter.2. Make the following entries:

Field NameUser Action and Values

Order typeYBRE (RMA Request)

Sales Organization

Distribution channel

Division

3. Choose Create with Reference.

4. In the Create with Reference dialog box, on the BillDoc tab, enter the billing document number, and then choose Item selection.

5. On the Create with Reference screen, select the items to be referenced and choose Copy.

If batch management is implemented, you have two items in the billing document (if the relevant settings for batch accumulation are not implemented, see note 77414). Select the item that has a quantity.

6. On the Create RMA Request: Overview Screen, enter an order reason (for example, Poor quality).

7. Choose the Shipping tab.

8. Enter a Storage Location for returns (for example, 1060 in plant 1000).

9. If the customer wants to return batches, on the Item Detail screen, choose the Sales A tab and define the batch number.

10. Save your entries.11. Make a note of the return order number here: ____________________.Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

1. Access the transaction using the following navigational option:

Business Role Sales Administrator

(SAP_NBPR_SALESPERSON_S)

Business Role MenuSales Customer Cockpit

If you have installed the scenario Rebate Processing: Free Goods in your system, and you use material H11, the following warning may display: Minimum quantity 1,000 EA of free goods has not been reached. To skip this warning, choose Enter.2. Make the following entries and choose Display Customer:

Field NameUser Action and ValuesComment

Customer Number100000

3. On the Customer Cockpit screen, select the following option:Field NameUser Action and ValuesComment

Other ActivitiesCreate Order

4. On the Create Sales Order screen, make the following entries and choose Continue:Field NameUser Action and ValuesComment

Sales Document TypeYBRERMA Request

Sales Organization

Distribution channel

Division

Reference DocumentEnter the billing document number to be referenced

5. On the RMA Request: New screen, make the following entries:Field NameUser Action and ValuesComment

Order reasonPoor quality

If batch management is implemented, you have two items in the billing document (if the relevant settings for batch accumulation are not implemented, see note 77414).

6. Select the item without quantity and choose Delete.

7. Select the item. 8. Choose the Product Availability tab.

9. Enter a Storage Location for returns (for example, 1060 in plant 1000)10. Choose Save Document. 11. Make a note of the sales order number: _______________.Result

The return order has been created.

The printout of the 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).

You can also start the print-out manually:

Option 1: SAP Graphical User Interface (SAP GUI)SAP ECC menuLogistics Sales and Distribution Sales Order Display

Transaction codeVA03

1. Enter the order number in the Display Sales Order: Initial Screen. From the menu, choose Sales Document ( Issue Output To.2. Select the line with the message type BA00.

3. Choose Print.Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business Role Sales Administrator

(SAP_NBPR_SALESPERSON_S)

Business Role MenuSales Sales Orders Sales Order Processing Sales Documents Worklist

1. From the Active Queries of the Returns category, choose the query All returns (refresh the current query if necessary).This query has been defined in section 2.4 - Defining Queries for Personal Object Worklist (POWL).

2. Select your return order and choose Sales Document in PDF-Format.3. On the Print Preview screen, choose Print.

4.2 Create Return Delivery

Use

In this step you create the return delivery.

Procedure

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

Option 1: SAP Graphical User Interface (SAP GUI)SAP ECC menuLogistics Sales and Distribution Sales Order Subsequent functions Outbound Delivery

Transaction codeVL01N

2. Make the following entries:

Field nameUser action and values

Shipping Point

Selection Date

Order number

3. Choose Enter.

4. Enter the Batch number for Batch Managed Items such as Material F29 and F126.5. Choose Save. If the system displays the message Document is incomplete: You cannot save the delivery, confirm the warning message with enter. The message only displays if serial number controlled materials are involved. Serial number assignment is done separately in one of the following steps.Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

1. Access the transaction choosing one of the following navigation option:

Business role Warehouse Clerk

(SAP_NBPR_WAREHOUSECLERK_S)

Business role menuWarehouse Management Shipping Outbound Delivery

2. Choose the Delivery Due Orders tab.

3. If the Quick Criterial Maintenance is not showing, choose the Show Quick Criteria Maintenance button, and then make the following entries and choose Apply (refresh the current query if necessary):

Field nameUser action and values

Shipping Point

4. Select your return order and choose Creation in Background.

5. The system issues the message Returns Delivery has been created.Result

A return delivery is created.

4.3 Assign Serial Number

Use

In this activity you assign serial numbers to the materials.

This step is to be used if Serial Number Management is activated.

Procedure

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC MenuLogistics Sales and Distribution Shipping and Transportation Outbound Delivery Change Single Document

Transaction CodeVL02N

2. On the Change Outbound Delivery screen, enter the delivery number, and choose Enter.

3. Select the material to which you need to assign a serial number, if the Material is Batch Managed, choose Batch Split (for example, Material F126). If the material is not batch controlled, (for example, Material H20) choose Item Details instead of Batch Split.

4. On the Delivery XXX Change: Item Details screen, select the batch to which you need to assign a serial number and from the menu, choose Extras ( Serial Numbers. If the material is not batch controlled (H20), choose Extras ( Serial Numbers.5. In the Maintain Serial Numbers dialog box, select the serial number from the input help. Make sure that the serial number comes from the batch determined in step 4.2 if the material is batch controlled (for example, F126).

6. Save your delivery.

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

1. Access the transaction as follows:

Business Role Warehouse Clerk

(SAP_NBPR_WAREHOUSECLERK_S)

Business Role MenuWarehouse Management Shipping Outbound Delivery

2. Choose the Due for Post Goods Issue tab.

3. Enter the Shipping Point / Receiving Pt: and choose Apply (refresh the current query if necessary).

4. Select your Delivery.

5. Choose Change.

6. If the material is batch managed, select the material to which you need to assign a serial number, and choose Batch Split (for example, Material F126). If the material is not batch controlled (H20), choose Item Details instead of Batch Split.

7. On the Delivery XXX Change: Item Details screen, select the batch you need to assign a serial number and choose More ( Extras ( Serial Numbers. If the material is not batch controlled (for example, Material H20) choose More ( Extras ( Serial Numbers.

8. In the Maintain Serial Numbers dialog box, select the serial number from the input help. For testing purposes, choose a serial number from the selection list that has no plant and no storage location assigned to it. Make sure that the serial number comes from the batch determined in step 4.2, in case the material is batch-controlled (for example, F126).

9. Save your outbound delivery.

Result

Serial numbers are assigned to the materials.

4.4 Post Goods IssueUse

In this step the goods receipt is posted.No accounting and controlling documents are generated, because this is a transfer into the stock type return that is none valuated. Further transfer postings are valuated if applicable.Procedure

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

Option 1: SAP Graphical User Interface (SAP GUI)SAP ECC menu

Logistics Logistics Execution Outbound Process Goods Issue for Outbound Delivery Outbound Delivery Lists and Logs Outbound Delivery Monitor

Transaction codeVL06O

2. Choose For Goods Issue.

3. Make the following entries:

Field nameUser action and values

Shipping point

4. Choose Execute (F8).

5. Select the relevant delivery.

6. Choose Post Goods Issue. (Choose todays date in the dialog box.)

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

1. Access the transaction as follows:

Business Role Warehouse Clerk

(SAP_NBPR_WAREHOUSECLERK_S)

Business Role MenuWarehouse Management Shipping Outbound Delivery

2. Choose the Due for Post Goods Issue tab.

3. Enter the Shipping Point / Receiving Pt: and choose Apply (refresh the current query if necessary).

4. Select your Delivery.

5. Choose Goods Issue.

6. The system issues the message Delivery xxxxxxxx was posted as a goods issue.Result

The goods receipt for the return delivery has been posted.

The return storage location is not relevant for MRP and ATP (Available to Promise). This means that the returned quantity is not available for other customer orders. A transfer posting from the return storage location into the standard storage location must be processed to make the goods available.

4.5 Billing

Use

In this activity, you handle billing.

Procedure

Option 1: SAP Graphical User Interface (SAP GUI)1. Access the transaction choosing one of the following navigation options:

SAP ECC MenuLogistics Sales and Distribution Billing Billing Document Process Billing Due List

Transaction CodeVF04

2. Enter relevant search criteria, select the delivery-related checkbox and deselect the Order-related checkbox and choose DisplayBillList (F8).

3. Select a row and choose Individual Billing Document.

4. Save your entries.Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

1. Access the transaction as follows:

Business Role Billing Administrator

(SAP_NBPR_BILLING_S)

Business Role MenuSales Billing

2. On the Billing screen, choose the Billing Due List tab (refresh the current query if necessary).

3. Enter the relevant search criteria and select the Delivery-Related checkbox. Choose Apply.

4. Select the lines with the sales documents you want to bill and then choose Billing in Background.

5. The system displays a list of the created billing documents.

Result

A cost credit memo is generated.

MaterialDebited AccountsCredited AccountsCost Element / CO Object

Trading Good (HAWA)410000

Sales revenue dom.

216100Sales Tax Accrued (AR)121000Receivables - domes.410000

Sales revenue dom.

Finished Good (FERT)410000

Sales revenue dom.

216100Sales Tax Accrued (AR)121000Receivables - domes.410000

Sales revenue dom.

The print-out of the invoice is executed automatically and immediately (see settings in SAP GUI transaction VV33 for Output Type RD00 and defaults in your user settings in transaction SU3).

You have also the possibility to start the print-out manually:

Option 1: SAP Graphical User Interface (SAP GUI)SAP ECC MenuLogistics Sales and Distribution Billing Billing Document Display

Transaction CodeVF03

1. On the Display Billing Document screen, from the menu, choose Billing document ( Issue Output to.2. Select the line with the message type RD00.3. Choose Print.

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

Business Role Billing Administrator

(SAP_NBPR_BILLING_S)

Business Role MenuSales 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.4.6 Post Outgoing Payment

Accounts Payable (158)

Use

In this process you post the outgoing payment.

Procedure

Complete all activities described in the Business Process Documentation of the scenario: Accounts Receivable (157) (sections Post Payment using Automatic Payments Program or Outgoing Payments - manually) using the master data from this document.5 Follow-Up Processes

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

Return to Vendor (136) (optional)Use

In this activity, you dispose of the inventory by returning to the vendor. Do not process any other activities in this document after running the external process.

Procedure

Complete all activities described in the Business Process Documentation of the scenario: Return to Vendor (136) using the master data from this document.

Stock Usage Blocking and Scrapping (131) (optional)Use

In this activity, the returned material can be blocked or scrapped.Procedure

Complete all activities described in the Business Process Documentation of the scenario: Stock Usage Blocking and Scrapping, (131) using the master data from this document.

Rework Processing (Stock-Manufactured Material) (151) (optional)Use

This process focuses on rework activities and material postings after production execution for the original material (including goods receipt of the product) with an additional rework production order.

Procedure

Complete all activities described in the Business Process Documentation of the scenario: Rework Processing (Stock-Manufactured Material) (151) using the master data from this document.

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

This scenario describes the collection of periodic activities such as day ending activities.

Procedure

Complete all activities described in the Business Process Documentation of the scenario: Sales: Period End Closing Operations (203) (sections on Review Sales Documents blocked for billing, Review Billing Due List, Review Log of collective invoice creation and Review List Blocked (for accounting) Billing Documents) using the master data from this document.6 Appendix6.1 Reversal of Process Steps

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

Create Return Order

Transaction code (SAP GUI)VA01

Reversal:Delete Sales Document

Transaction code (SAP GUI)VA02

Business roleSales Administrator(SAP_NBPR_SALESPERSON_S)

Business role menuSales ( Sales Orders ( Sales Order Processing ( Change Sales Order

CommentChoose menu Sales Document ( Delete.

Create Return Delivery and Post GR

Transaction code (SAP GUI)VL01N

Reversal:Delete Delivery

Transaction code (SAP GUI)VL02N

Business roleWarehouse Clerk(SAP_NBPR_WAREHOUSECLERK_S)

Business role menuWarehouse Management ( Shipping ( Outbound Delivery ( Change Delivery

CommentSelect menu Outbound

Reversal:Reverse of Goods Receipt

Assign Serial Number

Transaction code (SAP GUI)VL02N

Reversal:Edit Serial Number

Transaction code (SAP GUI)VL02N

Business roleWarehouse Clerk(SAP_NBPR_WAREHOUSECLERK_S)

Business role menuWarehouse Management ( Shipping ( Outbound Delivery ( Change Delivery

Comment

Post Goods Issue

Transaction code (SAP GUI)VL02N

Reversal:Reverse Goods Issue.

Transaction code (SAP GUI)VL09

Business roleWarehouse Clerk(SAP_NBPR_WAREHOUSECLERK_S)

Business role menuWarehouse Management ( Shipping ( Outbound Delivery ( Cancel Goods Issue for Delivery Note

Comment

Billing

Transaction code (SAP GUI)VF04

Reversal:Cancel Billing document

Transaction code (SAP GUI)VF11

Business roleBilling Administrator(SAP_NBPR_BILLING_S)

Business role menuSales ( Billing ( Cancel Billing Document

CommentGo 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 SAP ERP ReportsUse

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 for 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 TitleTransaction Code (SAP GUI)Business Role (NWBC)Business Role Menu (NWBC)Comment

List of Sales OrdersVA05Sales Manager(SAP_NBPR_SALESPERSON-M)Sales ( Sales Orders ( Reports ( List of Sales OrdersA list of all selected sales orders is displayed.

List Billing DocumentsVF05Sales Manager(SAP_NBPR_SALESPERSON-M)Sales ( Sales Orders ( Reports ( List Billing DocumentsA list of all selected billing documents is displayed.

Incomplete SD DocumentsV.02Sales Manager(SAP_NBPR_SALESPERSON-M)Sales ( Sales Orders ( Reports ( List of Incomplete Sales OrdersA list of all incomplete documents on the basis of the specified selection criteria is displayed.

ReturnsMC+MSales Manager(SAP_NBPR_SALESPERSON-M)Sales ( Sales Performance ( Material ( SIS: Material Returns, SelectionMaterial Analysis Return

Credit MemosMC+USales Manager(SAP_NBPR_SALESPERSON-M)Sales ( Sales Performance ( Material ( SIS: Material Credit Memos, Selec.Material Analysis Credit Memos

6.3 Used Forms

Common Form NameForm TypeUsed in Process stepOutput TypeTechnical name

Order ConfirmationSmartFormCreate Return OrderBA00YBUS_SDORC

Delivery NoteSmartFormCreate Return Delivery and Post GRLD00YBUS_SDDLN

Bill of LadingSmartFormCreate Return Delivery and Post GRYBL1YBUS_SDBLD

Sales InvoiceSmartFormBillingRD00YBUS_SDINV

SAP AG

Page 26 of 26

_1363432148.bin