Buld Block 141

7/29/2019 Buld Block 141

http://slidepdf.com/reader/full/buld-block-141 1/26

EHP4 for SAP ERP6.0

March 2010

English

Internal ProcurementCross-Company StockTransfer (141)

SAP AGDietmar-Hopp-Allee 1669190 Walldorf Germany

Business Process Documentation

7/29/2019 Buld Block 141


SAP Best Practices Internal Procurement Cross-Company Stock Transfer (141): BPD

Copyright

© Copyright 2009 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without theexpress 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 componentsof 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, SystemStorage, 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 inventedand implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAPproducts and services mentioned herein as well as their respective logos are trademarks or registeredtrademarks 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 S.A. in the UnitedStates and in other countries. Business Objects is an SAP company.

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 itsaffiliated 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 onlywarranties for SAP Group products and services are those that are set forth in the express warrantystatements accompanying such products and services, if any. Nothing herein should be construed asconstituting an additional warranty.

© SAP AG of 26

7/29/2019 Buld Block 141



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

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 26

7/29/2019 Buld Block 141



Contents

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

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

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

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

2.3 Roles.................................................................................................................................... 7

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

2.4.1 Initial Stock Posting.......................................................................................................8

3 Process Overview Table.............................................................................................................9

4 Process Steps........................................................................................................................... 10

4.1 Creating Purchase Order...................................................................................................10

4.2 Creating Outbound Delivery for Purchase Order................................................................12

4.3 Posting Goods Issue for Delivery.......................................................................................14

4.4 Checking Status of Stock Transfer.....................................................................................15

4.5 Creating Billing Document .................................................................................................16

4.5.1 Printing out Billing Document Manually (Optional).......................................................17

4.6 Displaying Billing Document (Optional)..............................................................................18

4.7 Creating Excise Invoice .................................................................................................... 19

4.8 Posting Goods Receipt for Stock Transport Order.............................................................20

4.9 Invoice Receipt by Line Item..............................................................................................22

4.10 Outgoing Payment (Cross-Company)..............................................................................24

5 Appendix................................................................................................................................... 24

5.1 Reversal of Process Steps.................................................................................................24

5.2 SAP ERP Reports..............................................................................................................25

5.3 Used Forms........................................................................................................................25

5.3.1 Procurement................................................................................................................ 25

5.3.2 Goods Movements.......................................................................................................26

© SAP AG of 26

7/29/2019 Buld Block 141



Internal Procurement Cross-Company StockTransfer

1 PurposeThis document describes the business process of cross-company stock transfer. The scenariosupports the following functions for cross-company deliveries:

• Partner functions

• Customer for cross-company delivery (company code 1010 orders material from company

code 1000)

• Stock transport order for specific plant

• Stock transport order - assign delivery type

• Stock transport order - purchasing document type

• Field selection for movement types

• Permissible partner roles per account group

• Additional views in the material master for material to be delivered

• Conditions for the relevant material

• Vendor for supplying plant

2 Prerequisites2.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 data that suits its operational focus, for example, master data for materials, vendors, andcustomers.

This master data usually consists of standardized SAP Best Practices default values, andenables 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 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:

© SAP AG of 26

7/29/2019 Buld Block 141



Master /org. data

Value Master / Org. data details Comments

Material H11 Trading Good for Reg. Trading withline item category NORM (PD

planning)

no Serial no.; no batch

See sections BusinessConditions and Preliminary

Steps.

Plant 1000 Plant 1 Shipping plant

Plant 1010 Plant 1010 Receiving plant

StorageLocation

1020 Plant 1000 Shop floor w/o lean WM

StorageLocation

1030 Plant 1000 Shipping w/ lean WM

Storage

Location

1050 Plant 1000 Stores w/ lean WM

StorageLocation

1C10 Plant 1010 Receiving storage location

Vendor 491000 NATIONAL_PROD_PLANT_VENDOR

Purch. Org. 1010

CompanyCode

1000 Company Code 1000

CompanyCode

1010 Company Code 1010 Special Company code for Cross-company

PurchaseOrganization

1000 Purch. Org. 1000

PurchaseOrganization

1010 Purch. Org. 1010 Purch Organization for crosscompany

Purchasegroup

100 Group 100 Plant 1000

Purchasegroup

101 Purch. Group 101 Plant 1000

Purchasegroup


Purchasegroup

103 Purch. Group 103 Plant 1000

Purchasegroup


Purchasegroup


Purchasegroup


© SAP AG of 26

7/29/2019 Buld Block 141



Master /org. data

Value Master / Org. data details Comments

Purchasegroup


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 havecompleted the following processes and fulfilled the following business conditions before you canstart going through this scenario:

Business condition Scenario

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

In addition you have to execute the step “Roll MM Period to Current Period ” for company code 1010.

Prereq. Process Steps (154)

2.3 Roles

Use

The following roles must have been installed to test this scenario in the SAP Netweaver Business Client (NWBC). The roles in this Business Process Documentation must be assignedto the user or users testing this scenario. You do not need these roles if you are not using theNWBC interface, but the standard SAP GUI.

Prerequisites

The Business roles have been assigned to the user who is testing this scenario.

Business role Technical name Process step

Employee(ProfessionalUser)

SAP_NBPR_EMPLOYEE-S Assignment of this role is necessaryfor basic functionality.

Purchaser SAP_NBPR_PURCHASER-S Create Purchase Order (ME21N)

WarehouseClerk

SAP_NBPR_WAREHOUSECLERK-S

Create Outbound Delivery for PO(VL10B),

Post Goods Issue for Delivery(VL02N),

Check Status of Stock Transfer (MMBE),

Post Goods Receipt for StockTransport Order (MIGO)

WarehouseManager

SAP_NBPR_WAREHOUSEMANAGER-M

Check Status of Stock Transfer

Billing Administrator

SAP_NBPR_BILLING-S Create Billing Document

AccountsPayable

SAP_NBPR_AP_CLERK-S Invoice Receipt by Line Item

© SAP AG of 26

7/29/2019 Buld Block 141



Business role Technical name Process step

Accountant

CIN(Excise

Transaction)

SAP_BPR_IN_EXCISECLERKCreate Excise Invoice

2.4 Preliminary Steps

2.4.1 Initial Stock Posting

Use

The purpose of this activity is to post initial stock from needed material for example H11, if thereis no stock available. If there is enough stock skip this step.

Prerequisites

Material H11 must be maintained in plant 1000/ storage location 1050 (stock Lean WM) andplant 1010 / storage location 1C50 (stock Lean WM).

Procedure

1. Access the activity using one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics→ Materials Management → Inventory

Management → Goods Movement → Goods Movement

(MIGO)

Transaction code MIGO

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

Business role Warehouse Clerk

(SAP_BPR_WAREHOUSESPECIALIST-S)

Business role menu Warehouse Management → Receiving → Process Order

→Goods Movement

2. On the Initial Screen, enter the following data; then choose Enter :

Field name Description User action and values Comment

Action Goods Receipt

Reference Other

Movement Type(Inventory Management)

561 Receipt w/o purchaseorder intounrestricted-usestock.

3. Choose Enter .

4. If dialog box Change to Default Values appears, mark X in the filed Skip this in future, andchoose Continue.

5. On the Goods Receipt Other screen: Material tab page, make the following entries:

© SAP AG of 26

7/29/2019 Buld Block 141




Material H11

6. On the Goods Receipt Other screen: Quantity tab page, make the following entries:


Qty in Unit of Entry

100

7. On the Goods Receipt Other screen: Where tab page, make the following entries andchoose Enter:


Plant 1000

Storage Location 1030

8. Choose Post .

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

Result

You have stock from material H11.

3 Process Overview Table

Process step Externalprocessreference

Businesscondition

Businessrole

Trans-actioncode

Expectedresults

Create PurchaseOrder(Process)

Purchaser ME21N The systemcreates thepurchase order

Create OutboundDelivery for PurchaseOrder(Process)

The systemcreates adeliverynumber for the stock

transportorder.

WarehouseManager

VL10B The systemcreates adelivery number for the stocktransport order

Pick OutboundDelivery(Process)

WarehouseManager

VL02N On the Pickingtab, the deliverygets the pickingstatus Fullypicked

Post Goods Issuefor Delivery(Process))

WarehouseManager

VL02N The systemruns the goodsissue with themessageReplen. Cross-

company<xxxxxxx> has

© SAP AG of 26

7/29/2019 Buld Block 141



Process step Externalprocessreference

Businesscondition

Businessrole

Trans-actioncode

Expectedresults

been saved

Check Status of StockTransfer(Process)

WarehouseManager

MMBE You get anoverview of thestock in transit

Create BillingDocument

Billing Administrator

VF04 the vendor issues theinvoice to thecustomer

Print out BillingDocumentManually

Sales Administrator

VF03 Billingdocument isprinted out

Creat ExciseInvoice

Excise Clerk J1IS Excise Invoiceis created,which should besubmitted to theExcise Authorities

Post GoodsReceipt for StockTransportOrder(Process)

WarehouseManager

MIGO The systemposts the goodsreceipt for thepurchase order to the

unrestrictedstock of thereceiving plant

Invoice is Receivedby Line Item

AccountsPayable Accountant

MIRO Invoicedocument isbooked andaccountingdocument iscreated

4 Process Steps

4.1 Creating Purchase Order

Procedure

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


SAP ECC menu Logistics→ Materials Management → Purchasing → Purchase

Order → Create → Vendor/Supplying Plant Known

Transaction code ME21N

© SAP AG of 26

7/29/2019 Buld Block 141




Business role Purchaser

(SAP_NBPR_PURCHASER-S)

Business role menu Purchasing → Purchase Order → Purchase Order → CreatePurchase Order

2. On the Create Purchase Order screen, make the following entries and choose Enter:


Order type Standard PO Order type NB

Vendor for example 491000 Production Plant 1000

Org. data tabpage

ExpandHeader

Choose

Purchasing org. 1010 Purchasing Organization

1010

Purchasing group

for example 103 Purch. Group 103

Company code 1010 Company Code (1010)

Expand „Itemoverview“

Choose If item overview window isnot visible

Material for example H11

Order quantity for example 10 Any other quantity

Delivery date <Default value> Default value is Today.

If you take a date later than “at the end of the nextweek”, be sure to selectthe right date in stepCreate Outbound Delivery for Purchase Order

Net price Any Will be maintained fromexisting info record; Canbe maintained manually if required ( you candescribe conditions f.Example: Freight)

Currency INR

Plant 1010 Inter Company ProcessingPlant (Plant from an other Company Code, receivingplant)

Storage location for example 1C50 (plant

1010)

Warehouse Lean WM inplant 1010

On the Invoice tab, enter the tax code refer to the following table. Enter the exactone to adapt to your situation.

Tax Category Material Types Tax code

© SAP AG of 26

7/29/2019 Buld Block 141



Local purchase(VAT) /(CENVAT/VAT)

Trading Goods NE

Raw Material NE

Semi-finished Goods NE

Purchasing from Other states(CST) / (CENVAT/CST)

Trading Goods MD

Raw Material MD

Semi-finished Goods MD

3. Choose Enter .

4. Choose Save (Ctrl+S) to save the purchase order.

Result

The system creates the purchase order for cross company stock transfer.

If the net value for the created PO is larger than 25000.00 INR, don’t forget torelease it via transaction ME28. (refer to step 4.5 Approval of Purchase Orders inBPD 130 to get detailed information, which is about how to deal with PO approval)

4.2 Creating Outbound Delivery for Purchase Order

Procedure



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

→ Outbound Delivery → Create → Collective Processing of

Documents Due for Delivery → Purchase Orders

Transaction code VL10B



(SAP_NBPR_WAREHOUSECLERK-S)

Business role menu Warehouse Management → Shipping → Delivery Due → Purchase

Orders Due for Delivery

2. On the Purchase orders, fast display screen, make the following entries:

© SAP AG of 26

7/29/2019 Buld Block 141




Shipping point 1000

Deliv. Creation

Date

Delete values

CalcRuleDefltDlvC rDt

Rule for determining default valuefor delivery creation date

3 Due for shipment by the endof next week (+ past-duedelivs)

Purchase orderstab page

Supplying plant 1000

3. Choose Execute (F8 ).

4. Select items in overview screen and choose Create Delivery in Background (Shift + F7 ).5. Select the line with green traffic light, choose Choose Detail to get the created delivery

number and note down it for further use.

If you have also installed a Best Practices Industry Extension in your system thetransfer order probably is not created, printed and confirmed automatically. In thiscase continue with the following steps:


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

→ Outbound Delivery → Lists and Logs → Outbound Delivery

Monitor

Transaction code VL06O


Business role Warehouse Manager

(SAP_NBPR_WAREHOUSEMANAGER-M)

Business role menu Warehouse Management →Warehouse Monitoring → Monitor

Outbound Delivery Process → Outbound Delivery Monitor

1. On the Outbound Delivery Monitor screen choose For Picking .

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


Shipping point <Shipping Point>

© SAP AG of 26

7/29/2019 Buld Block 141



3. Choose Execute.

4. Choose TO in Background (Create Transfer Order in Background).

5. On the “Transfer Order for Picking: Set Parameters” pop-up screen, activate the parameter

Activate Item and fill 1 in the field Adopt Pick Quantity.

Result

The system creates a delivery number for the stock transport order. The Show/hide delivery (Shift+F8) pushbutton displays/hides the delivery created by the program. See also the Log for delivery creation (Ctrl+F4). From here, you can display the created document number for the SDdelivery by choosing Documents. Record the created number for the SD delivery.

4.3 Posting Goods Issue for Delivery

Procedure



SAP ECC menu Logistics Sales and Distribution Shipping and Transportation Post Goods Issue Outbound Delivery Single Document

Transaction code VL02N

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

3. Select the item line and go to the header Edit → Incompleteness, choose Back.

4. Select the item line and go to the header Environment → Availability , choose Back.

5. On the Replen.Cross-Company XXXXXXXX Change: Overview screen, choose tab Picking, make sure that the issuing storage location on the Picking tab page is 1030 (dispatch store).

6. Choose Post Goods Issue.





Business role menu Warehouse Management → Shipping → Outbound Delivery

© SAP AG of 26

7/29/2019 Buld Block 141



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.

5. Choose Change.

6. Select the item line and go to the header Edit → Incompleteness , choose Back.

7. Select the item line and go to the header Environment → Availability , choose Back.

8. On the Replen.Cross-Company XXXXXXXX Change: Overview screen, choose tab Picking ,make sure that the issuing strorage location on the Picking tab page is 1030 (dispatch store).

9. Choose Post Goods Issue.

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

ResultThe system runs the goods issued with the message Replen. Cross-company <xxxxxxx>Outbound delivery <xxxxxxx> has been saved .

The goods issue document (TF to stck in trans.) for the selected batch item can be seen inDisplay Outbound Delivery (Ctrl+F1) and Enter under Environment Document flow (F7). (For NWBC: More…Environment Environment Document flow (F7 ).

4.4 Checking Status of Stock Transfer

Procedure



SAP ECC menu Logistics Materials Management Inventory Management Environment Stock Stock Overview

Transaction code MMBE


Business role Warehouse Manager

(SAP_NBPR_WAREHOUSEMANAGER-M)

Business role menu Warehouse Management → Inventory Control →

Environment → Stock Overview

© SAP AG of 26

7/29/2019 Buld Block 141



2. On the Stock Overview: Company Code/Plant/Storage Location/Batch screen, make thefollowing entries:


Material H11 Material number of thematerial from the purchaseorder

Plant 1010 Inter Company ProcessingPlant (receiving plant)

Execute <F8>

Choose Detailed Display See stock type On-Order stock.

Result

You get an overview of the stock in transit. This covers all of the material that has left the

supplying plant and has not yet reached the receiving plant.

4.5 Creating Billing Document

Use

In this step, the vendor (plant 1000) issues the invoice to the customer (plant 1010).

Procedure



SAP ECC menu Logistics→ Sales and Distribution → Billing → Billing

document → Process Billing Due List

Transaction code VF04

2. On the Process Billing Due List screen, make the following entries:


Billing date from From, for example, yesterday to onemonth from today

Sold-to party for example 493000 Intercompany

customer

Delivery-related Select

Intercompany Billing

Select Must be set to getthe cross companydcouments

© SAP AG of 26

7/29/2019 Buld Block 141



3. Choose DisplayBillList .

4. On the Maintain Billing Due List screen, the system displays the delivery Comment waiting tobe billed.

5. Select the delivery you created earlier and choose Individual billing document.

6. The Intercompany Billing (IV) Create: Overview of Billing Items screen appears. To check

the document goes to header Edit → Log . A system message appears No error log created .

7. Choose Save. A system message appears Document 9xxxxxx has been saved .

8. Choose Back.


Business role Billing Administrator

(SAP_NBPR_BILLING-S)

Business role menu Sales→ Billing

1. On the Billing screen, choose Billing Due List tab page.

If your outbound delivery is not in the list, you should check the selection criteria viachange query . The field Intercompany Billing has to be switched on. Choose Apply to return to the list, input the created delivery number in field Sales Document andrefresh the list.

2. Mark the line with the sales document, which you want to bill and choose Billing inBackground .

3. The system provides you with a list of the created billing document.

Result

A billing document has been created and the postings to FI and CO have been made.

Remark:

The FI settings for Cross-company trade are not part of the solution and must be done manually.

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 settingsin transaction SU3).

4.5.1 Printing out Billing Document Manually (Optional)

Use

You have the possibility to start the printout manually.

Procedure


SAP ECC menu Logistics→ Sales and distribution → Billing → Billing

document → Display


© SAP AG of 26

7/29/2019 Buld Block 141



1. Go to transaction VF03, on the Display Billing Document screen: From the menu, chooseBilling document Issue Output To

2. Mark the line with the message type RD00

3. Choose Print .


Business role Sales Administrator


Business role menu Sales → Billing

1. On the search billing document tab, enter the billing document number and switch oncheckbox Non-Cleared Billing Documents as search criteria and choose Apply .

2. Mark the billing document and choose Display .

3. Choose More … → Billing Document → Issue Output to.

4. Select the relevant Output and choose Print .

4.6 Displaying Billing Document (Optional)

Use

In this step, the customer invoice is reviewed regarding financial postings and pricing.

Procedure


Option 1: SAP Graphical User Interface (SAP GUI)SAP ECC menu Logistics→ Sales and Distribution → Billing → Billing document →

Display


2. Enter the billing document number.

3. Choose Enter .

4. On the Intercompany Billing 900000xx (IV) Display: Overview of Billing Item screen, choose Accounting .

5. In the List of Documents in Accounting dialog box, choose the invoice 009000xxxx.

The goods were delivered from a plant that belongs to company code 1000.Nevertheless, the company code field in the accounting document shows that thecustomer invoice was posted in company code 1000. The original order was alsoentered for sales organization 1000.

6. Go back to the Invoice 900000xx (IV) Display: Overview of Billing Items screen.

7. On the Intercompany Billing 900000xx (IV) Display: Overview of Billing Item screen, choose

Goto → Header → Header.

The header data of the billing document is now

8. Go back to the Intercompany Billing 900000xx (IV) Display: Overview of Billing Item screen.

9. Select the item and choose pricing conditions header .The pricing conditions are then displayed.

© SAP AG of 26

7/29/2019 Buld Block 141



You can see here that in pricing procedure ZINICP, the total comprises conditionsPI01 (price) and some other conditions.

10. Go back to the Intercompany Billing 900000xx (IV) Display: Overview of Billing Item screen,choose Back and choose Enter.


Business role Billing Administrator


Business role menu Sales → Billing

1. On the search billing documents tab, enter the billing document number as search criteriaand choose Apply.

2. Mark the billing document and choose Display .

3. On the Intercompany Billing 90000xxx (IV) Display: Overview of Billing Item(s) screen,choose Accounting .

4. In the List of Documents in Accounting dialog box, choose the invoice 009000xxxx.

The goods were delivered from a plant that belongs to company code 1000.Nevertheless, the company code field in the accounting document shows that thecustomer invoice was also posted in company code 1000.

5. Go back to the Invoice 900000xx (IV) Display: Overview of Billing Items screen.

6. On the Intercompany Billing 900000xx (IV) Display: Overview of Billing Items screen,

choose Goto → Header → Header . The header data of the billing document is now

displayed. In the Pricing procedure field, you can see that pricing procedure ZINICP is used.

7. Go back to the Intercompany Billing 90000xxx (IV) Display: Overview of Billing Items screen.

8. Choose pricing conditions header. The pricing conditions are then displayed.

9. Go back to the Invoice 900000xx (IV) Display: Overview of Billing Items screen, chooseBack .

4.7 Creating Excise Invoice

Use

The Incoming Excise Invoice will be attached to the Outgoing Delivery Document.

Prerequisites

Post Goods Issue for the Delivery Document must be completed.

Procedure



SAP ECC menu CIN Menu(J1ILN) → Indirect Taxes → Sales / Outbound

Movements→

Excise Invoice→

For Other Movements→

Excise invoice for other movements

© SAP AG of 26

7/29/2019 Buld Block 141



Transaction code J1IS


Business role SAP_NBPR_IN_EXCISECLERK-SBusiness role menu CIN → Excise invoice for other movements

2. On the Excise Invoice Other Movements- Main Menu screen, choose Create Excise Invoice.

3. On the Excise Invoice Other Movements – Create screen, enter following entries, thenchoose Enter .


Ref.doc.type MATD

Doc Number 49XXXXXX Materialdocument

number yourecorded inprevious steps.

Doc Year 2010

Series Group 10

Excise Group 21

Customer 493000

4. On the Excise Invoice Other Movements – Create screen, enter item H11 total amount of POyou create in step 4.1 in Net Ass. Value field, enter 8 in BED%, 2 in SED%, 1 in SECESS%.

5. Choose Enter . Choose Yes if message pop-up.6. Choose Save. You will get message: 0001XXXX generated , FI document…, please record

the internal number 0001xxxxx. Note down the excise invoice number _____________.

7. On the Excise Invoice Other Movements- Main Menu screen, choose Post Excise Invoice.

8. On the next screen, make the following entries and choose Enter :


Document No Use F4 search, to

choose the

document created

just now.

Document Year 2010

9. Choose Enter again to confirm the message.

4.8 Posting Goods Receipt for Stock Transport Order

Procedure


Option 1: SAP Graphical User Interface (SAP GUI)SAP ECC menu Logistics→ Materials Management → Inventory Management →

© SAP AG of 26

7/29/2019 Buld Block 141



Goods Movement → Goods Receipt → GR for Order

Transaction code MIGO




Business role menu Warehouse Management → Receiving → Process Order → Goods

Movement

2. On the Other goods movement screen, make the following entries:


Movement type List field GR Goods receipt 101 (here: Goodsreceipt for purchaseorder intowarehouse/stores)

Reference document List field Outbound Delivery

Document number Outbound Delivery Number

Document date < current date >

Posting date < current date >

Delivery Note Enter the no. Delivery notefrom plant 1000

Entry is mandatory.

Bill of Lading <optional> Enter the documentnumber of bill of lading from plant

1000.

Enter Helpful to set thevalues first.

Item Detail: Wheretab page

Choose

Storage location 1C50 (Storage Lean WM) If not yet enteredduring creation of thepurchase order

Item OK X Has to be flagged.

Pushbutton Check Confirm messages.

You can ignore themessage “Documentflow for delivery cannot be updated”, or for example “For batch xyz of materialC10150, no classcould be determined”.

3. Choose Check to check the entries.

4. On the Excise Invoice tab page, make the following entries:


Excise Invoice Enter the excise invoicenumber

use F4 search to findout the excise invoice

© SAP AG of 26

7/29/2019 Buld Block 141




number that you’vecreated in step 4.7

Excise Inv.Date Enter the excise invoicedate

5. Choose Enter . The excise value is captured.

6. Remark: Ignore the system message relating the kind of value like “system cannot find thedelivery note number“.

7. Choose Post (Ctrl+S).

Result

The system posts the goods receipt for the purchase order to the unrestricted stock of thereceiving plant (you can check this in transaction MMBE).

4.9 Invoice Receipt by Line Item

Use

The invoice verification is done here.

Procedure



SAP ECC menu Logistics → Materials Management → Logistics Invoice

Verification → Document Entry → Enter Invoice

Transaction code MIRO


Business role Accounts Payable Accountant

(SAP_NBPR_AP_CLERK-S)

Business role menu Accounts Payable → Posting → Invoices → Enter Incoming

Invoice w/ PO Reference

2. On the Enter Incoming Invoice: Company Code XXXX screen, choose menu path Edit →

Switch Company Code, maintain company code 1010 and choose Continue (Enter).

3. On the Enter Incoming Invoice: Company Code XXXX screen, select the Basic data sub-screen and make the following entries:


Invoice date Date of the invoice (for example today)

Reference (Fictive) Invoice no. of the delivering plant

Amount Invoice (overall) amount (incl. Tax) of athe (fictive) invoice

Calculate tax Mark the flag “X”

Tax Code Same to the value in PO

Tax amount The system posts here the VAT tax of the

© SAP AG of 26

7/29/2019 Buld Block 141



PO amount

4. Go to the tab strip PO reference and make the following entries:


Purchase Order/Scheduling agreement

Relevant Purchase Order Number

Layout Invoice reduction

5. Choose Enter to get the PO data in the Item screen. Make sure that all relevant PO data arelisted in the “Item screen”.

6. Choose Simulate to simulate the invoice values. A dialog box Simulate Document in INR (Document currency) appears. Check that the balance has the amount 0 and choose Back.

7. In case of messages Clear messages are warnings and Red messages are show stoppers.Fix red messages and choose Post to save the transaction. A message appears that willconfirm posting and also advise if it is blocked for payment.

8. Choose Post to post the invoice.

Result

The invoice is booked. The system also executes the financial postings in dependency to thedata of the goods receipt and due to the input during invoice verification. The Goods Receipt /Invoice Receipt account is balanced, price differences are either booked on the inventoryaccounts (if the price control indicator in the material master is Moving price average and enoughstock to cover the invoiced quantity is available) or on accounts for pricing differences (if theprice control indicator in the material master is Standard price or not enough stock to cover theinvoiced quantity is available). Document balances are booked due to tolerance limits (Pricevariance, small differences).

The FI settings for Cross-company trade are not part of the solution and must be done manually.

© SAP AG of 26

7/29/2019 Buld Block 141



4.10 Outgoing Payment (Cross-Company)

For this activity, run the 158 – AP – Accounts Payable scenario document in itsentirety, using the master data from this scenario document. In this case there willbe no real payment but an internal clearing.

The outgoing payment process will be described but not performed because the FIpostings for Cross-company billing is not part of the solution.

5 Appendix

5.1 Reversal of Process Steps

Creating a Purchase Order

Transaction code ( SAP GUI) ME21N

Reversal: Change Purchase Order

Transaction code ( SAP GUI) ME22N

Business role Purchaser

(SAP_NBPR_PURCHASER-S)

Business role menu Purchasing → Purchase Order → Purchase Order

Comment

Create Outbound Delivery for Purchase Order

Transaction code ( SAP GUI) VL10B

Reversal: Change Outbound Delivery

Transaction code ( SAP GUI) VL02N



Business role menu Warehouse Management → Shipping → Outbound

Delivery → Change Delivery

Comment Cancel Delivery

© SAP AG of 26

7/29/2019 Buld Block 141



Post Goods Receipt for Stock

Transaction code ( SAP GUI) MIGO

Reversal: Cancel Material Document

Transaction code ( SAP GUI) MBST



Business role menu Warehouse Management → Consumption and

Transfers → Cancel Material Document

Comment Cancel Goods receipt

5.2 SAP ERP Reports

Use

The table below lists the most frequently used reports that help you to obtain additionalinformation on this business process.

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 that are an indispensable part of the process flow maybe located directly in the section where they belong.

Reports

Report title Transaction code Comment

Material Documents MB51 A list of the material documents which wereposted for one or more materials.

Warehouse Stock MB52 A List of the warehouse stock is displayed

Stock Overview MMBE A list of stock is displayed.

Execute Report KE30 A report concerning Plan/Actual Activities.

5.3 Used Forms

Use

In some of the activities of this business process, forms were used. The table below providesdetails on these forms.

5.3.1 Procurement

Common form

name

Form type Used in process step Output

type

Technical name

Purchase Order SmartForm Step 4 NEU YBIN _MMPO

© SAP AG of 26

7/29/2019 Buld Block 141



5.3.2 Goods Movements

Common formname

Form type Used in process step Outputtype

Technical name

Goods Receipt(individual slip)

SmartForm Step 4 WE01 YBIN _MMGR1

Goods Receipt(individual slip withinspection text)


Goods Receipt(collective slip)


Buld Block 141

Documents

Transcript of Buld Block 141