Final Steps Hts en Us

8/3/2019 Final Steps Hts en Us

http://slidepdf.com/reader/full/final-steps-hts-en-us 1/12

EHP3 for SAP ERP6.0

June 2009English

Final Stepsafter Activation

SAP AGDietmar-Hopp-Allee 1669190 Walldorf Germany

1.1.1

BusinessPr ocessDocumentation



SAP Best Practices Final Steps after Activation: 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 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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400,iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9,z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+,OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

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.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service namesmentioned are the trademarks of their respective companies. Data contained in this document servesinformational 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 12




Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names,screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example

textEmphasized words or phrases in body text, titles of graphics and tables.

EXAMPLETEXT

Names of elements in the system. These include report names, programnames, transaction codes, table names, and individual key words of aprogramming language, when surrounded by body text, for example, SELECTand INCLUDE.

Example

text

Screen output. This includes file and directory names and their paths,messages, source code, names of variables and parameters as well as namesof installation, upgrade and database tools.

EXAMPLE TEXTKeys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example

text

Exact user entry. These are words or characters that you enter in the system

exactly as they appear in the documentation.

<Example

text> Variable user entry. Pointed brackets indicate that you replace these words andcharacters with appropriate entries.

© SAP AG of 12




Contents

Prerequisite Process Steps.................................................................................................................5

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

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

2.1 Business Conditions..............................................................................................................5

2.2 Roles.....................................................................................................................................5

3 Process Overview Table...............................................................................................................6

4 Process Steps..............................................................................................................................7

4.1 Roll MM Period to Current Period..........................................................................................7

4.2 Prepare Assets for Manufacturing Cost Centers...................................................................7

4.2.1 Create Asset Master Data..............................................................................................8

4.2.2 Acquisition with Automatic Offsetting Entry....................................................................8

4.3 Define Release Procedure for Purchase Orders...................................................................9

4.4 Define Tolerance Groups for Employees............................................................................10

4.5 Initial Stock Posting.............................................................................................................11

INITIAL STOCK POSTING

© SAP AG of 12




Prerequisite Process Steps

2 PurposeThis Business Process Documentation contains process steps that must be done as prerequisitebefore you can start to work through the standard Business Process Documentation of selectedlogistics scenarios.

3 Prerequisites

3.1Business ConditionsThis building block is required for the use of Best Practices scenarios in a demo environment. Thesedata are required for the scenarios and usually do not exist directly after activation. The followingprocess steps describe all necessary steps required for creating the required transactional data.

This scenario is not relevant for usual business operations,

3.2Roles

UseThe following roles must have already been installed to test this scenario in the SAP Netweaver Business Client (NWBC). The roles in this Business Process Documentation must be assigned 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.

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

Business role Technical name Process step

Finance Manager SAP_BPR_FINACC-K

Roll MM Period to Current Period (MMPV)

AssetsAccountant

SAP_BPR_ASSET-S Create Asset Master Data

Asset: Acquisition with Automatic OffsettingEntry

© SAP AG of 12




4 Process Overview TableProcess step External

process

reference

Businesscondition

Businessrole

Trans-action

code

Expectedresults

Roll MM Period toCurrent Period

FinanceManager

MMPV

Asset: CreateAsset Master

AssetsAccountant

AS01

Asset: Acquisitionwith AutomaticOffsetting Entry

AssetsAccountant

ABZON

Define ToleranceGroups for Employees

AssetAccountant

SPRO

© SAP AG of 12




5 Process Steps

5.1Roll MM Period to Current Period

Use

Perform this activity only if the MM period in the system is not set to the current period.Usually, this activity must be done once a month.

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP SystemMenu

Logistics → Materials Management → Material Master → Other →

Close Period

TransactionCode

MMPV

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

Business role Finance Manager (SAP_BPR_FINACC-K)

Business rolemenu

General Ledger → Closing Preparation → Close Period for Material Master

2. On the Close Period for Material Master Records screen, make the following entries:

Field name Description User action and values Comment

From company code

Enter the company code. #1000(for example)

Period Enter the current period. <current month>

Fiscal year Enter the current fiscalyear.

<current fiscal

year>

1.1Prepare Assets for Manufacturing Cost Centers

Use

Assets are created for manufacturing cost centers. The assets are needed for scenarios located inthe library.

This step can only be executed if the manufacturing cost centers exist.Execute transaction KS02 and check that cost center 1301 exists.

PrerequisitesCost Center 1301 exists (transaction KS02).

© SAP AG of 12




1.1.1Create Asset Master Data



SAP SystemMenu

Accounting → Financial Accounting → Fixed Assets → Asset →

Create → Asset

Transactioncode

AS01

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

Business role (Name) Assets Accountant (SAP_BPR_ASSET-S)

Business role Menu Asset Accounting → Assets → Create Asset Master Record

2. On the Create Asset: Initial screen, provide the necessary data and select Master Data:

Field name Description User action and values Comment

Asset class Number of the asset class

Company Code #1000

3. On the Create Asset: Master Data screen, make the following sets of entries on register tabGeneral and register tab Time-Dependent and save:

Asset num. Assetclass

Description assetclass

Description Cost center

Register tab General Register tabTime-dependent

<internalnumber> 2000 Machinery Hammer drill deviceHilti 22 XL 1301

<internalnumber>

2000 Machinery Compressed air -screwdriver 262

1301

80000 5000 Low-value assetsMachinery

Floor cleaningmachine 234

1301

ResultThe asset master record has been created under the number you specified in company code #1000.

1.1.1Acquisition with Automatic Offsetting Entry

Use

With this transaction the asset can be posted automatically against the Clearing account fixed assetacquisition.

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


SAP systemmenu

Accounting → Financial Accounting → Fixed Assets → Posting →

Acquisition→ External Acquisition → Acquis. w/Autom. Offsetting Entry

© SAP AG of 12




Transactioncode

ABZON

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

Business role Assets Accountant (SAP_BPR_ASSET-S)

Business role menu Asset Accounting Postings Acquis. w/Autom. Offsetting Entry

2. On the Enter Asset Transaction: Acquis. w/Autom. Offsetting Entry screen, make the followingentries for all assets created with previous step:

Field name Description User action andvalues

Comment

Existing Asset

<no. of the asset> Number of the asset created withthe previous step

Document Date

<document date> e.g. today

Amount Posted

<amount> e.g. 1000

Quantity <Quantity> Caution:The Quantity is necessary for theasset classes 2000e.g. 1

Base Unit Base Unit of Measure

<Base Unit> Caution:The Base Unit is necessary for the asset classes 20000e.g. EA

3. Post the document.

Result

The asset has been capitalize with the amount specified. In the asset master record, thecapitalization and depreciation start dates were set when the first acquisition was posted.

1.1Define Release Procedure for Purchase Orders

UseIn this activity you will confirm the release procedure for purchase orders.

Procedure1. Access the transaction using one of the following methods:

Option 1: SAP Graphical User Interface (SAP GUI)IMG menu Material Management → Purchasing → Purchase Order → Release

Procedure for Purchase Orders → Define Release Procedure for Purchase Orders

Transactioncode

SPRO

2. Double-click Release Strategies.

© SAP AG of 12




3. Select Release Prerequisites, and choose the Continue button.

4. Select Release Statuses, and choose the Continue button.

5. Choose Classification.

6. On the Change View ”Release Strategies”: Classification screen, ensure the following entriesexists (You should use the button next to the field and select the entries via drop down):

Field User Action or Values

Order type (Purchasing) Framework order Standard POStock Tranfer Order

Total net order value > 500.00 USDPurchasing Group Purchasing group 100

Purchasing group 101Purchasing group 102Purchasing group 103

7. Choose Back .

8. Choose Save.

9. Choose Release Simulation.

10. Choose Simulate Release.

11. Choose Back .

12. Choose Save, and then Exit .

ResultThe release procedure for purchase orders is defined.

1.1Define Tolerance Groups for Employees

UseIn this activity, you predefine various amount limits for your employees with which you determine:

• the maximum document amount the employee is authorized to post

• the maximum amount the employee can enter as a line item in a customer or vendor account

• the maximum cash discount percentage the employee can grant in a line item

• the maximum acceptable

Procedure1. Access the transaction using one of the following methods:

IMG menu Financial Accounting (New)→ Financial Accounting Global Settings(New → Document → Tolerance Groups→ Define Tolerance Groups for

Employees

Transactioncode

SPRO

2. Double-click Company code #1000.

3. On the Change View ”FI Tolerance Groups for Users”: Details screen, ensure the followingentries exists (you can also set the tolerance limits as required):

Field User Action or Values

© SAP AG of 12




Amount per document 9,999,999,999.00Amount per open item account item 9,999,999,999.00Cash discount per line item 5.000Revenue (Amount) 5.00Revenue (Percent) 2.0Expense (Amount) 5.00Expense (Percent) 2.0

4. Choose Save.

5. Repeat the above steps for company code 1010 if you have activate Building block 216 Enterprise Structure extension

6. Choose Back .

1.1Initial Stock Posting

PurposeThis part of the documentation describes the initial stock posting for the materials required in thescenarios for SAP Best Practices for HT-Software

PrerequisitesAll required Building Blocks must be activated! All materials must be maintained in thecorresponding client.

Make sure that material type YHBW is checked for Quantity updating


TransactionCode

SPRO

IMG Menu Logistics – General→

Material Master→

BasicSettings → Material Types → Define Attributes of

Material Types

2. Choose material type YHBW .

3. Double-click Quantity/value updating .

4. For the following rows, select the checkboxes in the Qty updating column.

Valuation Area Material Type Qty Updating

1000 YHBW X

1100 YHWB X

0001 YHWB X

5. Choose Save.

6. Choose Back .

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

SAP Menu Logistics Materials Management Purchasing Master DataSubsequent Settlement Vendor Rebate Arrangements Environment Condition/Arrangement Environment Pricing Environment

© SAP AG of 12




Value Assignment Inventory Management Goods Movement Goods receipt For Purchase Order PO number known

TransactionCode

MB01

2. On the Goods Receipts for Purchase Order: Initial Screen, enter the following data:Field name Description User action and values Notes

Movement Type 501

Plant 1000

3. Choose Enter .

4. On the Goods Receipts for Purchase Order: New Items screen, enter the following dataaccording to the table below:

MaterialMaterial type(not required for data entry)

Quantity SLoc

HT-D-DOCMEDIA 200 1030

5. Choose Enter .

© SAP AG of 12

Final Steps Hts en Us

Documents

Transcript of Final Steps Hts en Us