118_bpp_en_br.doc

7/30/2019 118_bpp_en_br.doc

http://slidepdf.com/reader/full/118bppenbrdoc 1/31

EHP4 for SAP ERP6.0

March 2010

English

Foreign Trade ExportProcessing (118)

SAP AGDietmar-Hopp-Allee 1669190 Walldorf Germany

Business Process Documentation

7/30/2019 118_bpp_en_br.doc


SAP Best Practices Foreign Trade Export Processing (118): BPD

Copyright

© 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission 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, Systemz10, 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 WebConsortium, 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 andimplemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer,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, WebIntelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries.

All other product and service names mentioned are the trademarks of their respective companies. Datacontained 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 affiliatedcompanies ("SAP Group") for informational purposes only, without representation or warranty of any kind, andSAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAPGroup products and services are those that are set forth in the express warranty statements accompanyingsuch products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



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 fieldnames, 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 keywords 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 asnames of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or theENTER key.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace thesewords and characters with appropriate entries.

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



Contents

1Purpose............................................................................................................................................. 5

2Prerequisites......................................................................................................................................5

2.1Master Data and Organizational Data.........................................................................................5

2.2Business Conditions....................................................................................................................7

2.3Roles........................................................................................................................................... 8

2.4Preliminary Steps........................................................................................................................ 8

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

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

4.1Credit Management Check for Sales Order..............................................................................11

4.2Sales Order Entry......................................................................................................................114.3Credit Management Review blocked Sales Orders...................................................................14

4.4Delivery Processing...................................................................................................................14

4.5Transfer Order (TO) Lean WM.................................................................................................. 16

4.6Check Batches ......................................................................................................................... 18

4.7Assign Serial Numbers..............................................................................................................19

4.8Picking....................................................................................................................................... 20

4.9Post Goods Issue......................................................................................................................21

4.10Billing.......................................................................................................................................24

4.11Nota Fiscal Document............................................................................................................. 26

5Follow-Up Processes....................................................................................................................... 27

6Appendix..........................................................................................................................................28

6.1Reversal of Process Steps........................................................................................................28

6.2SAP ERP Reports..................................................................................................................... 30

6.3Used Forms...............................................................................................................................31

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



Foreign Trade Export Processing

1 Purpose As markets become increasingly global, and business structures more complex, the need for accuracy in handling the foreign trade needs of a business is gaining rapidly in importance. Thisscenario is designed to help you meet the rapidly changing foreign trade requirements of your business.

The process starts with the creation of a customer's standard sales order. Depending on thecustomer and the material, various special events take place during the order entry, such ascustomer/material pricing, insertion of applicable discounts, checking the availability of the materials,and checking the customer‘s credit history.

Once the inventory has been reviewed, the delivery can be invoiced and the revenue together withthe cost of goods sold recorded in management accounting. This step signifies the end of thebusiness transaction within Sales and Distribution.

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 implementationphase, such as the data that reflects the organizational structure of your company and master datathat 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 thesame 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 whichyou have created master data. For more information on how to create master data, seethe Master Data Procedures documentation.

Use the following master data in the process steps described in this document:

Master /Org. Data

Value Master / Org. DataDetails

Comments

Material H11 Trading Good for Reg. See sections Business Conditions and

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



Master /Org. Data


Comments

Trading (MRP planning)

no Serial no.; no batch

Preliminary Steps.

Material H12 Trading Good for Reg.Trading (reorder pointplanning)

no Serial no.; no batch

See sections Business Conditions andPreliminary Steps.


with serial numbers, nobatch

Only use if you have activated thebuilding block Serial Number Management (126).

See the sections Business Conditions and Preliminary Steps.

Material H21 Trading Good for Reg.

Trading (reorder pointplanning)

no Serial no.; batchcontrolled (Exp. Date)

Only use if you have activated the

building block Batch Management (117).



no Serial no.; batchcontrolled (FIFOstrategy)

Only use if you have activated thebuilding block Batch Management (117).


Material F29 Finished Good MTS for

Process Industry (PDplanning)

no Serial no.; with batch(Exp. Date)

Only use if you have activated the

building block Batch Management (117).


Material F126 Finished Good MTS for Discrete Industry (PDplanning)

with Serial no.; with / w/obatch (FIFO strategy)

Only use if you have activated thebuilding block Serial Number Management (126).


Sold-to party 100010 Cliente Exportação 01 You can test the scenario usinganother domestic customer.

Ship-to party 100010 Cliente Exportação 01

Payer 100010 Cliente Exportação 01

Plant 1000 (1100)

StorageLocation

1030/1040

(1130/ 1140)

lean WM / w/o lean WM

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



Master /Org. Data


Comments

ShippingPoint

1000(1100)

Salesorganization

1000

Distributionchannel

10

Division 10

WarehouseNumber

110 Shipping

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 thefollowing processes and fulfilled the following business conditions before you are able to start goingthrough this scenario:

Business Condition Scenario

You have completed all relevant steps described in theBusiness Process Documentation Prereq. ProcessSteps (154).

Prereq. Process Steps (154)

In order to run through this scenario, the materialsmust be available in stock. If you use trading goods(HAWA) you can either:

• Run through the procurement w/o QM (130)

process, or

• Create stock using transaction MIGO (for

details see chapter Preliminary Steps).

Procurement w/o QM (130)

In order to run through this scenario, the materialsmust be available in stock. If you use finished goods(FERT) you can either:

• Run through the Make-to-Stock Production -

Discrete Industry (145) process (for materialF126) / the Make-to-Stock Production -Process Industry (146) process (for materialF29) or

• Rreate stock using transaction MIGO (for

details see chapter Preliminary Steps).

Make-to-Stock Production - DiscreteIndustry (145) (material F126)Make-to-Stock Production - ProcessIndustry (146) (material F29)

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



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 tothe user or users testing this scenario. You only need these roles if you are using the NWBCinterface. You do not need these roles if you are using the standard SAP GUI.

Business Role Technical Name Process Step

Employee(Professional User)

SAP_NBPR_EMPLOYEE-S Assignment of this role isnecessary for basicfunctionality.

Sales Administrator SAP_NBPR_SALESPERSON-S Sales Order Entry

Warehouse Clerk SAP_NBPR_WAREHOUSECLERK-S Delivery Creation

Transfer Order Creation(TO) Lean WM

Check Batches

Assign Serial Numbers

Picking

Post Goods Issue

Billing Administrator SAP_NBPR_BILLING-S Billing

Employee(Localization Brazil)

SAP_NBPR_BR_LOCBR-S Nota Fiscal Document

2.4 Preliminary Steps

In order to run through this scenario, the materials must be available in stock.

Procedure

1. Access the transaction using one of the following navigational 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)

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



Business Role Menu Warehouse Management → Consumption and Transfers → Other

Goods Movement

2. On the MIGO overview screen, make the following entries:

Field Name User Action and Values Comment

Business Transaction A01 – Goods Receipt Select A01 – Goods Receipt from the1st Drop-Down Menu

Business Transaction R10 – Other Select R10 – Other from the 2nd Drop-Down Menu

Movement Type 561 561 – Receipt per initial entry of stockbalances into unr.-use

3. Choose Enter .

4. On the Goods Receipt Other screen: Material tab page, make the following entry and chooseEnter :


Material <Material number>

5. On the Goods Receipt Other screen: Quantity tab page, make the following entry and chooseEnter :

Field Name User Action and Values

Qty in Unit of Entry 10000

6. On the Goods Receipt Other screen: Where tab page, make the following entries and chooseEnter :


Plant <plant>

Storage Location <storage location> lean WM / w/o lean WM

7. On the Goods Receipt Other screen: Batch tab page, make the following entry and chooseEnter :


Date of manufacture Enter the current

date or a date in

the past

Only relevant for material H22 and F29

8. On the Goods Receipt Other screen: Serial Numbers tab page, make the following entry andchoose Enter :


Create Serial Nos Automatically

Only relevant for material H20 andF126

9. Choose Enter .

10. Save your entries.

Result

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



The quantity of 10000 has been posted.

Financial postings:

Material DebitedAccounts Credited Accounts Cost Element / CO Object

Trading Good(HAWA)

114700Commerc.Products

910000 UploadBalance Stock

none

Finished Good(FERT)

114000 FinishedProduct

910000 UploadBalance Stock

none

3 Process Overview Table

Process Step ExternalProcessReference

BusinessCondition

BusinessRole

Trans-actionCode

ExpectedResults

Set Credit Limit Credit Management (108)

See scenariono. 108

See scenariono. 108

Credit Limit for Customer 100003 hasbeen set.

Sales Order Entry

Customer request for material

Sales Administrator

VA01

Review Blocked Sales Orders

Credit Management (108)

See scenariono. 108

See scenariono. 108

Sales order isreleased.

DeliveryCreation

WarehouseClerk

VL10C Delivery iscreated. TheWarehouseTransfer Order is created.

Transfer Order Creation (TO)Lean WM

WarehouseClerk

LT03 Transfer order is created.

Check Batches WarehouseClerk

VL02N

Assign SerialNumbers

WarehouseClerk

VL02N Serial Number is assigned.

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



Process Step ExternalProcessReference

BusinessCondition

BusinessRole

Trans-actionCode

ExpectedResults

Picking Warehouse

Clerk

VL06O Material is

picked.

Post GoodsIssue

WarehouseClerk

VL06O The goodsissue is posted.

Billing Materialshippedinvoicerequired

Billing Administrator

VF04 Billing iscarried out.

Nota FiscalDocument

J1BNFE The NotaFiscaldocument isoutput.

Incoming Payment

AccountsReceivable(157)

AccountsReceivable

See scenariono. 157

See scenario no.157

Sales: Period End Closing Operations

Sales:Period End Closing Operations(203)

See scenariono. 203

See scenario no.203

4 Process Steps

4.1 Credit Management Check for Sales Order


Use

In this process a credit limit is set for the used customer.

Procedure

Complete all the activities described in the Business Process Documentation of the scenario: Credit

Management (108).

4.2 Sales Order Entry

Use

In this activity, you will enter a sales order.

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



Prerequisites

None

Procedure

1. Access the transaction using the following navigational option:


SAP ECC Menu Logistics→ Sales and Distribution→ Sales→ Order → Create

Transaction Code VA01

If you have installed the scenario Rebate Processing: Free Goods in your system and youuse material H11, the following warning may appear: Minimum quantity 1.000 PC of free

goods has not been reached. To skip this warning, choose Enter .

If you do not want to use Lean Warehouse Management (WM), choose a storage location

Shipping w/o Lean WM (e.g. 1040) by using the following path: Goto → Item → Shipping .

Enter the selected storage location (e.g. 1040) in field Stor. Location.

2. Enter the Order type ORB (Standard Order BR) and choose Enter (you can optionally enter

organizational data).

3. Make the following entries:


Sold to party <Sold to party>

Ship to party <Ship to party>

PO number Enter a customer purchase order number as reference.

Order reason For example: Excellent price optional

Material Number <Material number>

Quantity 1

4. Choose Save.



Business Role Sales Administrator

(SAP_NBPR_SALESPERSON-S)

Business Role Menu Sales→ Customer Cockpit

2. Make the following entries and choose Display Customer :

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc




Customer Number <Customer Number>

3. On the Customer Cockpit screen, select the following option:


Other Activities Create Order Select Create Order from the Drop-Down Menu

4. On the Create Sales Order screen, make the following entries and choose Start :


Sales Document Type ORB Standard Order BR

5. On the Standard Order BR: New screen, make the following entries:

Field Name User Action and Values CommentPO number Enter a customer purchase order

number as reference.

Order reason For example: Excellent price

Material <Material number>

Order Quantity 1

If you have installed the scenario Rebate Processing: Free Goods in your system and you

use material H11, the following warning may appear: Minimum quantity 1.000 PC of freegoods has not been reached. To skip this warning, choose Enter .

If you do not want to use Lean Warehouse Management (WM), choose a storage locationShipping w/o Lean WM (e.g. 1040) by selecting the item and choosing the Product

Availability tab on the screen section next to the Item Overview section. Enter the selectedstorage location (e.g. 1040) in field Storage Location.

6. Choose Save Document. Make a note of the sales order number: __________

Result

The order is saved and the order confirmation is printed out.

The printout of the order confirmation is executed automatically and immediately (seesettings in SAP GUI transaction VV11 for output type BA00 and defaults in your user

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



settings in transaction SU3); however, only in the case when the sales order is notblocked (see next chapter Credit Management Review blocked Sales Orders).

You also have the possibility to start the print out manually (although only in the casewhen the sales order is not blocked; see next chapter Credit Management Review blocked Sales Orders):


SAP ECC Menu Logistics→ Sales and Distribution → Sales→ Order → Display

Transaction Code VA03

1. Enter the order number in the screen 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 .



(SAP_NBPR_SALESPERSON-S)

Business Role Menu Sales→ Sales Orders → Sales Order Processing

1. Choose the All Sales Orders tab page (refresh the current query if necessary).

2. Mark your sales order and choose Show Order Confirmation as PDF .

3. On the Convert Spool to PDF screen, choose Print .

4.3 Credit Management Review blocked Sales Orders


Use

In this process you will review the sales orders that might have been blocked due to the credit limitcheck.

Procedure

Complete all the activities described in the Business Process Documentation of the scenario: Credit Management (108).

4.4 Delivery Processing

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



Use

In this activity, you will create the delivery.

Prerequisites

None

Procedure



SAP ECC Menu Logistics→ Logistic Execution → Outbound Process →

Goods Issue for Outbound Delivery → Outbound Delivery

→ Create→ Collective Processing of Documents Due for

Delivery → Sales Order Items

Transaction Code VL10C



Shipping point 1000

Delivery creationdates (From)

<delivery creation date> Use this and the next field together, or use the Calc rule. Do not do both.

Delivery creationdates (To)

<delivery creation date> Use this and the last field together, or use the Calc rule. Do not do both.

Calc Rule <calculation rule> Use this field, or use the last two fields

together. Do not do both.

3. Choose Execute.

4. Select the line item(s) then choose Background .

5. Select the line with the green light then choose Details. In the dialog box you will see the deliverynumber which has been created.

6. Note down the delivery number: ______________________________.


1. Access the transaction as follows:



Business Role Menu Warehouse Management → Shipping → Outbound

Delivery

2. On the Delivery Due Orders tab page, make the following entries:


© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



Shipping point 1000

3. Choose Apply (refresh the current query if necessary).

4. Select your order you created in the previous process steps.

5. Choose Creation in Background.

6. The system issues the message: Delivery <delivery number> has been saved .

Result

A delivery is created.

Batches are automatically determined if batch management is activated.

In case of lean warehouse management, the transfer order can be created, printed andautomatically confirmed, but in this scenario (SAP Best Practices Baseline Package BR) the transfer order will not be created automatically – follow to the next step: Transfer Order (TO) Lean WM

4.5 Transfer Order (TO) Lean WM

Use

In this activity, you will create the transfer order.

Prerequisites

This step is to be used if lean WM has been activated.

Procedure



SAP ECC Menu Logistics→ Logistic Execution → Outbound Process →

Goods Issue for Outbound Delivery → Picking → Create

Transfer Order → Single Document

Transaction Code LT03




Business Role Menu Warehouse Management → Consumption and Transfers →

Create TO for Delivery



Warehouse <Warehouse Number> Warehouse Number WM.

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



Number

Delivery Delivery number Document created in the previous step.

Activate item X If this field is selected, the system copiesall items in the following screen into theactive work list.

Foreground/Backgr nd

D Background

Adopt Pick Quantity

2 Include pick. quantities in delivery andpost GI

3. Choose Enter .

4. The system issues the message: Transfer order <transfer order number> created .

Result

The transfer order is created, confirmed and the goods issue is posted.

The print out of the transfer order is executed automatically and immediately. Thisprintout is used for picking.

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


SAP ECC Menu Logistics→ Logistics Execution → Outbound Process →

Goods Issue for Outbound Delivery → Communication /

Printing → Single Print Pick Document

Transaction Code LT31

1. Enter the Warehouse Number and transfer order number (you can find this number usingtransaction VL02N and by checking the document flow) and choose Enter.

2. To start the print process, choose Transfer order → Print.




Business Role Menu Warehouse Management → Shipping → Transfer Orders

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



→ Print TO Manually

1. Enter the Warehouse Number and transfer order number (you can find TO number using

Business role menu Warehouse Management →

Shipping →

Outbound Delivery → Display Delivery and checking the document flow of your outbound delivery) and choose

Enter.

2. To start the print process, follow the path: More →Transfer order → Print.

4.6 Check Batches

Use

In this activity you will check the batch numbers assignment to the materials.

Prerequisites

This step is to be used if batch management is activated.

Procedure


1. Access the transaction by using one of the following navigational options:

SAP ECC Menu Logistics→ Sales and Distribution → Shipping and Transportation→

Outbound Delivery → Change → Single Document

Transaction Code VL02N

1. On the Change Outbound Delivery screen, enter the outbound delivery number and chooseEnter .

2. In the column Batch Split Indicator, choose Batch Split Exists.

3. In the Batch field, check the batch number assignment.




(SAP_NBPR_WAREHOUSECLERK-S) )


Delivery

2. Select the tab page Due for Post Goods Issue.

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

4. Select your Delivery.

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



5. Choose Change.

6. In the column Batch Split Indicator, choose Batch Split Exists.

7. In the Batch field, check the batch number assignment.

ResultBatch numbers are assigned to the materials.

4.7 Assign Serial Numbers

Use

In this activity you will assign serial numbers to the materials.

Prerequisites

This step is to be used if serial number management is activated.

Procedure



SAP ECC Menu Logistics→ Sales and Distribution → Shipping and

Transportation→ Outbound Delivery → Change→ Single

Document


2. On the Change Outbound Delivery screen, enter the outbound delivery number and chooseEnter .

3. Select the material to which you need to assign a serial number and choose Batch Split (e.G.Material F126). If the material is not batch-controlled (H20), choose Item Details instead of Batch Split .

4. On the Delivery XXX Change: Item Details screen, select the batch you need to assign a serial

number to and 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. For testing purposes, choose a serial number from the selection list that has a plant and a storagelocation assigned to it. Make sure that the serial number comes from the batch determined in

step Check Batches (see above) in case the material is batch-controlled (e.g. F126).

6. Save your outbound delivery.



© SAP AG of 31

7/30/2019 118_bpp_en_br.doc






Delivery



4. Select your Delivery.

5. Choose Change.

6. 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 insteadof Batch Split.

7. On the Delivery XXX Change: Item Details screen, select the batch you need to assign a serial

number to and choose More…→ Extras → Serial Numbers. If the material is not batch-

controlled (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 a plant and a storagelocation assigned to it. Make sure that the serial number comes from the batch determined instep Check Batches (see above), in case the material is batch-controlled (e.g. F126).

9. Save your outbound delivery.

Result

Serial numbers are assigned to the materials.

4.8 Picking

Use

The picking process involves taking goods from a storage location and staging the right quantity in apicking area where the goods will be prepared for shipping.

Prerequisites

This step is to be used if lean WM has not been activated.

Procedure



SAP ECC Menu Logistics→ Sales and Distribution → Shipping and Transportation→

Outbound Delivery → Lists and Logs → Outbound Delivery Monitor

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



Transaction Code VL06O

2. On the Outbound Delivery Monitor screen, choose For Picking .

3. On the Outbound Deliveries for Picking screen, make the following entry:


Shipping point <shipping point>

4. Select the Only Picking without WM checkbox.

5. Choose Execute.

6. Select your delivery note and choose Subsequent Functions → Picking Output.

7. On the Output from Picking screen, select your delivery note and choose Execute.




Business Role Menu Warehouse Management → Shipping → Outbound Delivery

1. On the Picking List (without WM) tab page, make the following entries:



2. Choose Apply (refresh the current query if necessary).

3. Select your delivery note and choose Display.

4. From the menu choose, More… → Subsequent Functions → Output from Picking.

5. To confirm the dialog box, choose Enter .

6. On the Output from Picking screen choose Execute.

7. On the Output from Picking screen, select your delivery note and choose Execute.

Result

The picking list EK00 has been printed and the picking quantity at delivery item level has beenupdated with the requested delivery quantity.

4.9 Post Goods Issue

Use

In this activity, you will post the goods issue.

Prerequisites

This step is to be used if lean WM has not been activated.

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



Procedure


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

SAP ECC Menu Logistics→ Logistics Execution → Outbound Process →

Goods Issue for Outbound Delivery → Outbound Delivery

→ Lists and Logs → Outbound Delivery Monitor

Transaction Code VL06O

2. Choose For Goods Issue.




4. Choose F8 .

5. Mark the relevant delivery.

6. Choose the Post Goods Issue.

7. Choose today’s date and select continue in the dialog box.





Business Role Menu Warehouse Management →

Shipping →

Outbound Delivery



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 issue is posted.

Delivery Note

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



The printout of the delivery note is executed automatically and immediately (see settings inSAP GUI transaction VV23 for output type LD00 and defaults in your user settings intransaction SU3).

You can also start the printout manually:


SAP ECC Menu Logistics Logistics Execution Outbound Process Goods

Issue for Outbound Delivery Outbound Delivery Display





Business Role Menu Warehouse Management → Shipping → Outbound Delivery →

Display Delivery

1. Enter your outbound delivery in the screen Display Outbound Delivery and choose from the

menu (NWBC: More…→) 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 inSAP GUI transaction VV23 for output type YBL1 and defaults in your user settings intransaction 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




© SAP AG of 31

7/30/2019 118_bpp_en_br.doc





Display Delivery

1. Enter your outbound delivery in the screen Display Outbound Delivery and choose from the

menu (NWBC: More…-> ) Outbound Delivery → Issue delivery Output.

2. Mark the line with the message type YBL1 – Bill of Lading.

3. Choose Print .

4.10 Billing

Use

In this activity you will handle the billing.

Prerequisites

None

Procedure



SAP ECC Menu Logistics→ Sales and Distribution → Billing → Billing Document →

Process Billing Due List Transaction Code VF04

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

3. Select a row and choose Individual Billing Document .

4. Choose Save.



Business Role Billing Administrator

(SAP_NBPR_BILLING-S)

Business Role Menu Sales→ Billing

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

3. Enter the relevant search criteria, select the Delivery-Related flag. Choose Apply

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

5. The system will provide you with a list of the created billing documents.

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



Result

The system generates an invoice for billing.

Material DebitedAccounts

Credited Accounts Cost Element / CO Object

TradingGood(HAWA)

100010 ClienteExportação 01

313000 Sales - ExternalMarket

313000

FinishedGood(FERT)

100010 ClienteExportação 01

313000 Sales - ExternalMarket

313000

The printout of the invoice is executed automatically and immediately (see settingsin SAP GUI transaction VV33 for output type RD00 and defaults in your user settings in transaction SU3).

You also have the possibility to start the printout manually:


SAP ECC Menu Logistics→ Sales and distribution → Billing → Billing document →

Display

Transaction Code VF03

1. Go to transaction VF03, in the screen Display Billing Document : From the menu choose Billingdocument -> Issue Output to.

2. Mark the line with the message type RD00.

3. Choose Print .



(SAP_NBPR_BILLING-S)

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 .

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



4.11 Nota Fiscal Document

Use

In this activity, the Nota Fiscal document (NF-e) is output.

Procedure

1. Access the transaction using one of the following options:


SAP ECC Menu Localization Brazil → NFE → NFE → Monitor for Electronic Nota

Fiscal

Transaction code J1BNFE

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

Business role Employee (Brazil Localization)

(SAP_NBPR_BR_LOCBR-S)

Business role menu Localization Brazil → NFE → NFE → Monitor for Electronic Nota

Fiscal

2. Enter relevant search criteria, e.g. Company Code, and choose Execute (F8).

3. On the NF-e Monitor screen, mark the document created before and choose Set NF-e number button.

4. The system creates a NF-e number and send to SEFAZ. With the answer as confirmed the NotaFiscal will be printed automatically on printer default and marked as printed. The relevantcolumns status are updated.

If the customization are defined to create a NF-e number automatically, go to transactionJ1BNFE to see the number created and the SEFAZ answer.

5. To display the Nota Fiscal document click on NF-e number.

6. Choose Back .

7. If the NF-e is marked to Rejected from SEFAZ, you should check the reason using the StatusCode.

8. On this case, before do anything, you must reset the NF-e by clicking on Reset Rejected NF-e.

9. If the error occurred on NF-e, use the transaction J1B2N to correct it (i.e. Error descriptionInvalid CFOP , out the right number of CFOP using the transaction J1B2N to change the NF ).

Another errors like Master Data you can use transactions for Vendors or Clients ( XK02 or XD02).

10. Back to NF-e Monitor screen and then mark the NF-e changed and choose the menu NF-e Send . The NF-e is send to SEFAZ, then wait for the answer.

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



Result

A nota fiscal has displayed, printed automatically and changed as needed.

If necessary to Cancel, Switch to Contingency, Skipping the NF-e or disenable the NF-e

numbers (Gap’s Skipping), you should use an of these following BPD’s, such as moreappropriate.

Option 1 – NF-e Skipping (503 – Item 03)

Option 2 – NF-e Switched or Posted under Contingency (503 – Item 02)

Option 3 – NF-e Cancel (503 – Item 01)

Option 4 – NF-e Gap’s Skipping (503 – Item 04)

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

ProcedureUsing the master data from this document, complete all the activities described in the BusinessProcess 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 like Intrastat and Extrastat reporting.

Procedure

Using the master data from this document, complete all the activities described in the BusinessProcess Documentation of the scenario: Sales: Period End Closing Operations (203) (ChaptersReview Sales Documents blocked for billing , Review Billing Due List , Review Log of collectiveinvoice creation and Review List Blocked (for accounting) Billing Documents).

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



6 Appendix

6.1 Reversal of Process Steps

In the following section, you can find the most common reversal steps, which enable you to reversesome 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 Menu Sales→ Sales Orders → Change Sales Order

Comment Select menu Sales Document → Delete

Delivery Process

Transaction Code ( SAP GUI) VL01N

Reversal: Delete Delivery




Change Delivery.

Comment Select menu Outbound Delivery → Delete

Check Batches


Reversal: Edit Batch Number



Business Role Menu Warehouse Management → Shipping →Outbound Delivery

→Change Delivery

Comment

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



Assign Serial Number


Reversal: Edit Serial Number



Business Role Menu Warehouse management → Shipping →Outbound Delivery

→Change Delivery

Comment

Picking

Transaction Code ( SAP GUI) VL06O

Reversal: Remove Picking Quantity from Delivery Item



Business Role Menu Warehouse Management → Shipping →Outbound Delivery

→Change Delivery

Comment

Post Goods IssueTransaction Code ( SAP GUI) VL02N

Reversal: Reverse Goods Issue.

Transaction Code ( SAP GUI) VL09


Business Role Menu Warehouse management → Shipping →Outbound Delivery →

Cancel Goods Issue for Delivery Note

Comment

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



Billing

Transaction Code ( SAP GUI) VF04

Reversal: Cancel Billing document

Transaction Code ( SAP GUI) J1BNFE


Business Role Menu Localização Brasil → NFE → NFE → Monitor para nota fiscal

eletrônica

Comment See Business Process Documentation NF-e Cancel (503 – Item 01)

6.2 SAP ERP Reports

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

You can find detailed descriptions of the individual reports in the following BPDdocuments, 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, which are an indispensable part of the process flow, may

be located directly in the section where they belong.

Reports

Report Title Transaction code(SAP GUI)

Business Role(NWBC)

Business RoleMenu (NWBC)

Comment

List of SalesOrders

VA05 Sales Manager (SAP_NBPR_SALESPERSON-M)

Sales → Sales

Orders → Reports

→ List of Sales

Orders

A list of allselected salesorders isdisplayed.

List BillingDocuments

VF05 Sales Manager (SAP_NBPR_SALESPERSON-M)

Sales → Sales

Orders→

Reports→ List Billing

Documents

A list of allselected billingdocuments isdisplayed.

Orders withinTime Period

SDO1 Sales Manager (SAP_NBPR_SALESPERSON-M)

Sales → Sales

Orders → Reports

→ Orders within

time period

A list of salesorders within aspecific timeperiod

Incomplete SD V.02 Sales Manager Sales → Sales A list of all

© SAP AG of 31

7/30/2019 118_bpp_en_br.doc



Documents (SAP_NBPR_SALESPERSON-M)

Orders → Reports

→ List of

Incomplete SalesOrders

incompletedocuments onthe basis of thespecifiedselection criteria

is displayed.

Outbounddelivery monitor

VL06O Warehouse Manager (SAP_NBPR_WAREHOUSEMANAGER-M)

Warehouse

Management →

Warehouse

Monitoring→

Monitor Outbound

Delivery Process →

Outbound DeliveryMonitor

Monitor for collectiveprocessing of deliveries andfor obtaininginformation ongeneral shippingprocessing.

6.3 Used Forms

Common FormName

Form TypeUsed in Process Step Output

TypeTechnical Name

Order Confirmation SmartForm Sales Order Entry BA00 YBAA_SDORC

Delivery Note SmartForm Post Goods Issue LD00 YBAA_SDDLN

Transfer Order SAP Script Delivery Due List YB_LVSTAEINZEL

Pick List SD SAP Script Picking (optional) EK00 YB_SD_PICK_SINGL

Bill of Lading SmartForm Post Goods Issue YBL1 YBAA_SDBLD

Sales Invoice SmartForm Billing RD00 YBAA_SDINV

118_bpp_en_br.doc

Documents

Transcript of 118_bpp_en_br.doc