+ All Categories
Home > Documents > 411_BPP_EN_DE

411_BPP_EN_DE

Date post: 14-Apr-2018
Category:
Upload: omer-sanatna
View: 217 times
Download: 0 times
Share this document with a friend
13
7/29/2019 411_BPP_EN_DE http://slidepdf.com/reader/full/411bppende 1/13 EHP5 for SAP ERP 6.0 June 2011 English Pre-Trading Contract (411) SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany Business Process Documentation
Transcript
Page 1: 411_BPP_EN_DE

7/29/2019 411_BPP_EN_DE

http://slidepdf.com/reader/full/411bppende 1/13

EHP5 for SAP ERP6.0

June 2011

English

Pre-Trading Contract(411)

SAP AGDietmar-Hopp-Allee 1669190 Walldorf Germany

Business Process Documentation

Page 2: 411_BPP_EN_DE

7/29/2019 411_BPP_EN_DE

http://slidepdf.com/reader/full/411bppende 2/13

SAP Best Practices Pre-Trading Contract (411): BPD

Copyright

© 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the 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 SunMicrosystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, andother 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 Objectslogo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other BusinessObjects products and services mentioned herein as well as their respective logos are trademarks or registeredtrademarks of Business Objects Software Ltd. Business Objects is an SAP company.Sybase and AdaptiveServer, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as

well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAPcompany.

 All other product and service names mentioned are the trademarks of their respective companies. Data

contained in this document serves informational purposes only. National product specifications may vary.These

materials are subject to change without notice. These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and

SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP

Group products and services are those that are set forth in the express warranty statements accompanying

such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AGPage 2 of 13

Page 3: 411_BPP_EN_DE

7/29/2019 411_BPP_EN_DE

http://slidepdf.com/reader/full/411bppende 3/13

SAP Best Practices Pre-Trading Contract (411): BPD

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 the

ENTER 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 AGPage 3 of 13

Page 4: 411_BPP_EN_DE

7/29/2019 411_BPP_EN_DE

http://slidepdf.com/reader/full/411bppende 4/13

SAP Best Practices Pre-Trading Contract (411): BPD

Contents

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

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

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

2.2 Roles.......................................................................................................................................... 6

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

4 Process Steps...................................................................................................................................6

4.1 Create a Pre-Trading Contract .................................................................................................. 6

4.2 Reprint the Customer Copy of the Precontract (Optional)..........................................................9

4.3 Reprint the Vendor Copy of the Precontract (Optional)............................................................10

4.4 Release Trade Contract........................................................................................................... 11

5 Appendix........................................................................................................................................13

5.1 Reversal of Process Steps.......................................................................................................13

5.2 Reporting..................................................................................................................................135.3 Used Forms.............................................................................................................................. 13

© SAP AGPage 4 of 13

Page 5: 411_BPP_EN_DE

7/29/2019 411_BPP_EN_DE

http://slidepdf.com/reader/full/411bppende 5/13

SAP Best Practices Pre-Trading Contract (411): BPD

1 Purpose

In general a Pre-Trading Contract can be used either as a Master Agreement with quantity update or as copy template carrying all necessary data. It is provided to store the data for pre-Sales/Purchaseactivities and long term contract.

The creation of a Pre-Trading Contract is similar to the creation of a Trading Contract. The onlydifference is that for the Pre-Trading Contract, it is not possible to generate subsequent sales ordersand purchase orders when user saves the document.

2 Prerequisites

2.1 Master Data and Organizational DataUsing Your Own Master Data

You can also use customized values for any material or organizational data for which you havecreated master data. For more information on how to create master data, see the Master DataProcedures documentation.

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

Master / Org. Data Value Master / Org. Data Details Comments

Material GT-H10

Controlling area <Controlling area> For example Controlling Area 1000

Company Code <Company Code> For example CompanyCode 1000

Plant <Plant> For example ProductionPlant 1000

Storage Location <Storage Location> For example Versand1040

Sales organization <Sales organization> For example

1100 (Intern. Sales Org)

Distributionchannel

<Distribution Channel> For example Other Sales30

Division <Division> For example ProductDivision 10

Purchaseorganization

<Purchasing organization> For example PurchasingOrg. 1000

Purchasing Group YN1 Trade Contract Grp.

TC Sales Group YN03 Grp. for Precontract

© SAP AGPage 5 of 13

Page 6: 411_BPP_EN_DE

7/29/2019 411_BPP_EN_DE

http://slidepdf.com/reader/full/411bppende 6/13

SAP Best Practices Pre-Trading Contract (411): BPD

Master / Org. Data Value Master / Org. Data Details Comments

TC PurchasingGroup

YN03 Grp. for Precontract

2.2 Roles

UseThe following roles must already have 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.

Prerequisites

Business Role Technical Name Process StepEmployee(Professional User)

SAP_NBPR_EMPLOYEE_S Assignment of this role is necessary for  basic functionality.

Trade Manager SAP_NBPR_TRADEMANAGER_GTM_M Release Precontract

Trade Specialist SAP_NBPR_TRADESPECIALIST_GTM_S Create Pre-Trading Contract

3 Process Overview Table

Process step Externalprocessreference

Businesscondition

Businessrole (nottechnicalrole for BP)

Trans-actioncode

Expectedresults

Create Precontract TradeSpecialist

WB21 Precontract hasbeen created

ReleasePrecontract

Trade Manager WB22 Precontract hasbeen released

4 Process Steps

4.1 Create a Pre-Trading Contract

UseIn this activity, you will create a two-sided Pre-Trading Contract.

© SAP AGPage 6 of 13

Page 7: 411_BPP_EN_DE

7/29/2019 411_BPP_EN_DE

http://slidepdf.com/reader/full/411bppende 7/13

SAP Best Practices Pre-Trading Contract (411): BPD

PrerequisitesNone

ProcedureOption 1: SAP Graphical User Interface (SAP GUI)

1. Access the transaction choosing the following navigational option:

SAP ECC Menu Logistics→ Global Trade Management → Trading Contract → 

Create

Transaction Code WB21

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

Business role Trade Specialist

(SAP_NBPR_TRADESPECIALIST_GTM_S)

Business role menu Trade Management → Single Document → Trading Contract 

 Actions→ Create Trading Contract 

2. Enter the Contract Type YN00 (Precontract) and choose Organizational Data (Shift + F8 ).

3. On the Organizational Data screen make the following entries:

Field name User action and values Comment

TEW Type YNWB Standard Workbench

SalesOrganization

 <Sales organization>  For example

1100 (Intern. Sales Org)

DistributionChannel

 <Distribution

Channel> For example

30 (Other Sales)

Division <Division>  For example

10 (Product Division Division 10)

PurchasingOrganization

 <Purchasing

organization> For example

1000 (Purchase Org 1000)

Purchase Group YN1 Trade Contract Grp.

Plant <Plant> For example Production Plant 1000

Storage Location <Storage Location> For example 1040 (Shipping w/o LWM)

4. Choose Copy (F5).

5. On the Create Precontract screen enter the following data:

Field name User action and values Comment

Sold to party GTMUS01 Customer in USA

Vendor GTMCN01 Supplier in China

External Number <any entry> You can use any entry; we propose to usethe BPD number BPD411-1

© SAP AGPage 7 of 13

Page 8: 411_BPP_EN_DE

7/29/2019 411_BPP_EN_DE

http://slidepdf.com/reader/full/411bppende 8/13

SAP Best Practices Pre-Trading Contract (411): BPD

6. Choose Overview (Ctrl +F8).

7. On the Item overview tab page enter the following data:

Field name User action and values Comment

Material GT-H10

8. Choose Enter .

Field name User action and values Comment

Sales Quantity 1000 PC This is the total quantity to be sold for thisitem.

Quantity Ordered 1000 PCThis is the total quantity to be purchased for this item.

Sales Price 200,00 If the Sales price is not maintainable:

Choose Sales Price Condition. In the Pricing Elements section choose Insert Row and add in the columns CnTy thecondition type GSSP In columns amount and Crcy enter the 200 EUR.

In order to return to the Item overview tabscreen choose Overview (Ctrl+F8).

Sales currency EUR

Purchase price 100,00 If the Purchase price is not maintainable:

Choose Purch. Price Condition. In thePricing Elements section choose Insert 

Row and add in the columns CnTy thecondition type GMPP In columns amountand Crcy enter the 100 EUR.

In order to return to the Item overview tabscreen choose Overview (Ctrl+F8).

Purchasecurrency

EUR

9. Choose Enter .

10. Choose Status Overview (F8 ), review the Application Status.

11. Choose Save (Ctrl +S).

12. Take a note of the trading contract number: __________ .

13. Take a note of the External Number of the trading contract number: __________ .

ResultThe pre trading contract has been created.

The print out of the pre trading contract confirmation is executed automatically andimmediately. There are two forms printed, the customer copy and the vendor copy. See

© SAP AGPage 8 of 13

Page 9: 411_BPP_EN_DE

7/29/2019 411_BPP_EN_DE

http://slidepdf.com/reader/full/411bppende 9/13

SAP Best Practices Pre-Trading Contract (411): BPD

settings in SAP GUI transaction WWTC for output type WTHC (Customer (Header)) andWTHV (Vendor (Header)).

4.2 Reprint the Customer Copy of the Precontract(Optional)

You can also start the printout manually. For the customer message do the following:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics→ Global Trade Management → Trading Contract → 

Change

Transaction code WB22

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

Business role Trade Specialist 

(SAP_NBPR_TRADESPECIALIST_GTM_S)

Business role menu Trade Management → Single Document → Trading Contract 

 Actions→ Change Trading Contract 

1. Enter your Trade Contract on the Change Precontract  screen and choose from the menu

(NWBC: More…→) Extras→ Header Output → Customer → Output

2. Mark the line with the message type WTHC– Customer (Header)

3. Choose Continue (Enter).

 Alternatively, you can do the following:Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics→ Global Trade Management → Trading Contract → 

Environment → Messages→ Overview → For Customer 

Transaction code WB2C

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

Business role Trade Specialist 

(SAP_NBPR_TRADESPECIALIST_GTM_S)

Business role menu Trade Management → Multiple Documents → Mass Printing of 

Trading Contracts → Show all Messages for Customers

1. On the Messages from Trading Contract, Customer Target Group screen enter in the Messagesection the following:

Field name User action and values Comment

Output Type  WTHC Customer (Header)

TransmissionMedium

1 Print

© SAP AGPage 9 of 13

Page 10: 411_BPP_EN_DE

7/29/2019 411_BPP_EN_DE

http://slidepdf.com/reader/full/411bppende 10/13

SAP Best Practices Pre-Trading Contract (411): BPD

Field name User action and values Comment

Sort order  01 Contract/Item/Output Type

Processing mode 2 Repeat Processing

2. In the section Trading Contract enter the Precontract Number from the previous step.

3. Choose Execute (F8).

4. On the Messages from Trading Contract, Customer Target Group screen select the row withyour Precontract and choose Process (Shift+F2).

ResultThe customer copy of the Precontract has been printed.

4.3 Reprint the Vendor Copy of the Precontract (Optional)

You can also start the printout manually. For the vendor message do the following:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics→ Global Trade Management → Trading Contract → 

Change

Transaction code WB22

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

Business role Trade Specialist 

(SAP_NBPR_TRADESPECIALIST_GTM_S)

Business role menu Trade Management → Single Document → Trading Contract 

 Actions→ Change Trading Contract 

1. Enter your Trade Contract on the Change Precontract screen and choose from the menu

(NWBC: More…→) Extras→ Header Output → Vendor → Output

2. Mark the line with the message type WTHV– Vendor (Header).

3. Choose Continue (Enter).

 Alternatively, you can do the following:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics→ Global Trade Management → Trading Contract → 

Environment → Messages→ Overview → For Vendor 

Transaction code WB2V

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

Business role Trade Specialist 

(SAP_NBPR_TRADESPECIALIST_GTM_S)

Business role menu Trade Management → Multiple Documents → Mass Printing of 

Trading Contracts → Show all Messages for Vendors

© SAP AGPage 10 of 13

Page 11: 411_BPP_EN_DE

7/29/2019 411_BPP_EN_DE

http://slidepdf.com/reader/full/411bppende 11/13

SAP Best Practices Pre-Trading Contract (411): BPD

1. On the Messages from Trading Contract, Vendor Target Group screen enter in the Messagesection the following:

Field name User action and values Comment

Output Type  WTHV  Customer (Header)TransmissionMedium

1 Print

Sort order  01

Processing mode 2 Repeat Processing

2. In the section Trading Contract enter the Precontract from the previous step.

3. Chose Execute (F8).

4. On the Messages from Trading Contract, Vendor Target Group screen select the row with your Precontract and choose Process (Shift+F2).

ResultThe vendor copy of the Precontract has been printed.

4.4 Release Trade Contract

UseIn order to use a Precontract as a reference for follow-on Trading Contracts the Precontract need tobe released.

Procedure

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics→ Global Trade Management → Trading Contract 

→ Change

Transaction code WB22 

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

Business role Trade Manager 

(SAP_NBPR_TRADEMANAGER_GTM_M)

Business role menu Trade Management → Single Document → Trading Contract 

 Actions→ Change Trading Contract 

2. Enter your Trading contract number in the Trading contract field and choose Enter.

3. On the Change Trading Contract (Sales Side) screen choose Status Overview (F8).

4. On the tab strip Status select the application status L - Released.

5. Choose Set Status.

© SAP AGPage 11 of 13

Page 12: 411_BPP_EN_DE

7/29/2019 411_BPP_EN_DE

http://slidepdf.com/reader/full/411bppende 12/13

SAP Best Practices Pre-Trading Contract (411): BPD

6. Choose Save (Ctrl +S).

ResultThe Precontract has been released for further processing.

© SAP AGPage 12 of 13

Page 13: 411_BPP_EN_DE

7/29/2019 411_BPP_EN_DE

http://slidepdf.com/reader/full/411bppende 13/13

SAP Best Practices Pre-Trading Contract (411): BPD

5 Appendix

5.1 Reversal of Process Steps

Change Precontract

Transaction Code ( SAP GUI) WB22

Reversal: Set application status for presales contract to completed

Transaction Code ( SAP GUI) WB22

Business Role Trade Specialist

(SAP_NBPR_TRADESPECIALIST_GTM-S)

Business Role Menu Trade Management → Single Document → Trading Contract 

 Actions→ Change Trading Contract 

Comment Choose Status Overview (F8) and set Application Status to 

N Completed (Document deleted logically), confirm theupcoming information message.

5.2 Reporting

The 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 BPDdocument, which provide a comprehensive compilation of operational reports:

•  Trading: Operational Reporting (407)

5.3 Used Forms

UseIn some of the activities of this business process, forms were used. The table below provides details

on these forms.

Common formname

Form type Used in processstep

Outputtype

Technical name

Trade Contract Smartform Create Pre-TradingContract

WTHCYNGT_WB_CUSTOMER

Trade Contract Smartform Create Pre-TradingContract

WTHVYNGT_WB_VENDOR

© SAP AGPage 13 of 13