69
R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 1 Guide to generate R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios Applies To SAP Business One / SAP Business One SDK / SAP Business One Integration for SAP NetWeaver 2005 Summary This document will explain not only how to configure R/3 in order to set up a connection with SAP Business One Integration for SAP Netweaver and SAP Business One; but also how to set the distribution model with all message types in order to run all the delivered scenarios covered in version 1.0 out of the box. Authors: Eddy Neveux, Felipe Ortega Aguilar. Company: SAP Title: Solution Architects Date: October 2006

B1 on netweaver

Embed Size (px)

Citation preview

Page 1: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 1

Guide to generate R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

Applies To

SAP Business One / SAP Business One SDK / SAP Business One Integration for SAP NetWeaver 2005

Summary

This document will explain not only how to configure R/3 in order to set up a connection with

SAP Business One Integration for SAP Netweaver and SAP Business One; but also how to set the

distribution model with all message types in order to run all the delivered scenarios covered in

version 1.0 out of the box.

Authors: Eddy Neveux, Felipe Ortega Aguilar.

Company: SAP

Title: Solution Architects

Date: October 2006

Page 2: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 2

Table of Content

Guide to generate R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios......................................................................... 1

Applies To ......................................................................................................... 1

Summary ........................................................................................................... 1

Table of Content ............................................................................................... 2

Terminology ...................................................................................................... 5 IMG. .............................................................................................................................5 Overview............................................................................................................ 5

1. Defining the Logical System........................................................................ 6 Procedure ..........................................................................................................................6 2. Defining the RFC Destination ...................................................................... 7 Procedure ..........................................................................................................................7 Screen shot: ......................................................................................................................7 Screen shot: ......................................................................................................................8 3. Defining Distribution Model (General) ........................................................ 9 Step 1 .............................................................................................................................9 Screen shot: ....................................................................................................................10 Step 2 ...........................................................................................................................10 Creating Message Type MATMAS .................................................................................11 Creating Message Type DESADV..................................................................................12 Creating Message Type INVOIC ....................................................................................12 Creating Message Type ORDERS .................................................................................13 Part 3 ...........................................................................................................................15 Creating Message Type ORDERS: ................................................................................15 Part 4 ...........................................................................................................................17 Generating Partner Profiles ............................................................................................17 4. Creating Customer ..................................................................................... 18 Procedure ........................................................................................................................18 1. Access transaction XD01............................................................................................18

2. Choose Continue. .................................................................................................19 3. The “Address” Tab.: ...................................................................................................19 4. Select tab “Contact persons” ......................................................................................20 5. Sales Area Data screen (Shipping Tab) .....................................................................21 6. Billing Document Tab. .................................................................................................22

Page 3: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 3

7. Company Code Data screen.......................................................................................23 8. Payment transactions Tab ..........................................................................................25 5. Creating Product ........................................................................................ 25 Procedure ........................................................................................................................25 1. Access transaction MM01...........................................................................................25 2. Select Views screen....................................................................................................26 3. Organizational Levels screen......................................................................................28 4. Basic Data Tab............................................................................................................29 5. Tab “Sales: Sales Org 1” ............................................................................................30 6. Access the Conditions screen. ...................................................................................31 7. Access the Accounting 1 Tab. ....................................................................................33 Creating Purchase Order types..................................................................... 35 Procedure ........................................................................................................................35 1. Access transaction SPRO...........................................................................................35 Maintaining Output Types for Sales Documents ......................................... 37 Procedure ........................................................................................................................37 1. Access the transaction. ...............................................................................................37 2. Details of Added Entries screen .................................................................................37 3. General Data Tab........................................................................................................37 4. Default Values Tab......................................................................................................38 Maintaining Output Determination for Sales Documents ........................... 42 Prerequisite .....................................................................................................................42 Procedure ........................................................................................................................42

Maintaining Output Types for Outbound Deliveries.................................... 44 Procedure ........................................................................................................................44 1. Access the transaction. ...............................................................................................44 2. Details of Added Entries screen .................................................................................44 3. General Data Tab........................................................................................................44 4. Default Values Tab......................................................................................................45 Maintaining Output Determination for Outbound Deliveries ...................... 49 Prerequisite .....................................................................................................................49 Procedure ........................................................................................................................49 Maintaining Output Types for Billing Documents ....................................... 51 Procedure ........................................................................................................................51 1. Access the transaction. ...............................................................................................51 2. Details of Added Entries screen .................................................................................51 3. General Data Tab........................................................................................................51 4. Default Values Tab......................................................................................................52

Page 4: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 4

Maintaining Output Determination for Billing Documents.......................... 56 Prerequisite .....................................................................................................................56 Procedure ........................................................................................................................56 Result ............................................................................................................. 57

Changing Partner Profiles ............................................................................. 58

Creating Output Condition Records for the Sales Document .................... 63 Prerequisites ...................................................................................................................63 Procedure ........................................................................................................................63 Creating Output Condition Records for the Delivery .................................. 65 Prerequisites ...................................................................................................................65 Procedure ........................................................................................................................65 Creating Output Condition Records for the Invoice.................................... 67 Prerequisites ...................................................................................................................67 Procedure ........................................................................................................................67 Related Content .............................................................................................. 69

Copyright......................................................................................................... 69

Page 5: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 5

Terminology

IMG.

SAP Customizing Implementation Guide. The IMG (Implementation Guide for R/3

Customizing). Lists all actions required for implementing the SAP System

Helps you to control and document the implementation

Overview

This document will explain not only how to configure R/3 in order to set up a connection with

SAP Business One Integration for SAP Netweaver but how to set the distribution model with all

message types in order to run all the delivered scenarios covered in version 1.0 out of the box.

To run the Master Data Distribution scenarios, the document describes how to create a

Customer and a Product with the simplest configuration possible to easily run the

synchronization of master data to the subsidiaries.

Please consider that we focus completely in the R/3 configuration and that all the screen shots

showed in the document correspond to a MyBusiness Suite 4.7 200 version, if more

information about the different scenarios is needed please refer to our Live Expert Sessions “SAP

Business One Integration for SAP NetWeaver Release 2005- Configuration” or “SAP Business

One Integration for SAP NetWeaver Release 2005- Detailed Content”), or to the delivered

documentation files in the B1i CD or Patches (under the folders “B1 INTEGRATION CONTENT

2005 Documentation”).

Page 6: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 6

1. Defining the Logical System

Procedure

Use transaction SALE

IMG Path: Application link Enabling → Sending and Reviving Systems → Logical systems →

Define Logical systems

With the following data:

Logical System: B1I00

Name: B1i LOGICAL SYSTEM00 TB1BIT

Example:

Save your entries.

Page 7: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 7

2. Defining the RFC Destination

Procedure

1. To create an RFC Destination, access the transaction as follows:

Transaction code: SALE

IMG Path: Application Link Enabling (ALE) → Sending and Receiving Systems → Systems in

Network → Define Target Systems for RFC Calls

2. Choose Create.

3. In the RFC Destination screen, enter the following data:

RFC Destination: B1I00

Connection Type : T (Start an external program via TCP/IP)

Description : RFC Destination B1I00

Screen shot:

Page 8: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 8

4. Press « Enter ».

After pressing « Enter » the screen will display more fields and Tabs.

In the “Technical Settings” tab select radio button “Registered Server Program”

5. Program ID: B1IRFC00

Screen shot:

Page 9: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 9

3. Defining Distribution Model (General)

Step 1

1. To create a new model, access the transaction as follows:

Transaction code: BD64

SAP Menu: Application Linking Enabling → Modeling and Implementing Business

Process → Maintain Distribution Model and Distribute Views

2. In the Display Distribution Model screen, choose Switch between the display and edit mode

button ( )

3. Choose Create model view.

4. In the Create model view screen, enter the following data:

Short Text: B1i00 for TB1BIT

Technical Name: B1I00

Start Date: accept defaulted date

End Date: accept defaulted date

5. Choose Continue ( ).

Page 10: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 10

Screen shot:

Step 2

1. Select the new model you just created (B1i00).

2. Choose the Add message type button

3. In the Add message type screen, enter the following data:

Sender: It will be needed to assign the value that comes from Table T000, field LOGSYS that

corresponds to the Client assigned to the training system (in the table the Client is a key field). In our

sample is RKECLNT302

Receiver: B1I00

Message type: DEBMAS

Page 11: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 11

4. Choose Continue.

Creating Message Type MATMAS

5. Select the new model you have just created.

6. Choose the Add message type button.

7. In the Add message type screen, enter the following data:

Sender: It will be needed to assign the value that comes from Table T000, field LOGSYS that

corresponds to the Client assigned to the training system (in the table the Client is a key field). In our

sample is RKECLNT302

Receiver: B1I00

Message type: MATMAS

Choose Continue.

Page 12: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 12

Creating Message Type DESADV

8. Select the new model you just created (B1I00)

9. Choose the Add message type button

10. In the Add message type screen, enter the following data:

Sender: It will be needed to assign the value that comes from Table T000, field LOGSYS that

corresponds to the Client assigned to the training system (in the table the Client is a key field). In our

sample is RKECLNT302

Receiver: B1I00

Message type: DESADV

Choose Continue.

Creating Message Type INVOIC

11. Select the new model you just created (B1i00)

12. Choose the Add message type button

Page 13: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 13

13. In the Add message type screen, enter the following data:

Sender: It will be needed to assign the value that comes from Table T000, field LOGSYS that

corresponds to the Client assigned to the training system (in the table the Client is a key field). In our

sample is RKECLNT302

Receiver: B1I00

Message type: INVOIC

Choose Continue.

Creating Message Type ORDERS

14. Select the new model you just created (B1i00)

15. Choose the Add message type button

16. In the Add message type screen, enter the following data:

Sender: It will be needed to assign the value that comes from Table T000, field LOGSYS that

corresponds to the Client assigned to the training system (in the table the Client is a key field). In our

sample is RKECLNT302

Receiver: B1I00

Message type: ORDERS

Choose Continue.

Page 14: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 14

After this step, the window should see like this: (unbranched nodes)

Page 15: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 15

Part 3

In this section we add to each Model View (B1I00 for TB1BIT) Message Type ORDERS and we

switch between the Sender and Receiver system.

Creating Message Type ORDERS:

1. Select the new model you just created (B1i00)

2. Choose the Add message type button

3. In the Add message type screen, enter the following data:

Sender: B1I00#

Receiver: It will be needed to assign the value that comes from Table T000, field LOGSYS that

corresponds to the Client assigned to the training system (in the table the Client is a key field). In our

sample is RKECLNT302

Message type: ORDERS

4. Choose Continue.

After this step, the window should see like this: (unbranched nodes) See picture in

next picture.

Page 16: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 16

Page 17: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 17

Part 4

Generating Partner Profiles

1. Select the new model (B1I00)

2. In the Menu choose Environment → Generate partner profiles to generate a partner profile.

You will be prompted to the following screen with all values set:

3. Press the “Execute” icon to generate the profiles

Page 18: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 18

4. Creating Customer

In this section we will create Customer number 30001 , that will identify the subsidiary in our

R/3 system

Procedure

1. Access transaction XD01

Field Values:

Account group: Sold-to party

Customer: 30001

Company Code: 3000

Sales Organization: 3000

Distribution Channel: 10

Division: 00

As showed in the next screen:

Page 19: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 19

2. Choose Continue.

3. The “Address” Tab.:

By default the “Address” Tab will be selected. The following values must be filled:

Title (select from the combo box): Company

Name: Thomas Bush Inc .

In the case of the Name of the customer we need to vary it by including the name of the group

at the end of it, otherwise we will get a warning message.

Search term ½: BUSH

Street/House number: 2800 South 25th Ave

The same case as in the Name Field, we need to vary the street by adding the group number.

District: COOK

Postal code: 60153

City: Maywood

Country: US

Transportation Zone: 0000000001

Region: IL

Jurisdict. Code: 1403118101

As showed in the following screen:

Page 20: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 20

4. Select tab “Contact persons”

Here we will add two lines to the table. As follows:

Name First Name

Telephone1 Department Description Function Description

Bright Chris 0002 Purchasing 11 Buyer

Henderson Harold 0002 Purchasing 02 Head of purchasing

As described in the following screen:

Page 21: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 21

5. Sales Area Data screen (Shipping Tab)

In order to access this screen, select the button and select the Shipping

Tab. Type the following information in Shipping Conditions field:

Shipping Conditions: 02

Delivering Plant: 3000

As showed in the screen shot:

Page 22: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 22

6. Billing Document Tab.

Fill the following fields as indicated: Incoterms: FCA

Description: From Plant

Terms of Payment: NT30

As showed in the following screen shot:

Page 23: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 23

7. Company Code Data screen

In order to access this screen, select the button and enter the

following value in field Rec.Account.

Rec.Account.: 140000 As in the following screen shot:

Page 24: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 24

Page 25: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 25

8. Payment transactions Tab

Enter the following values: Terms of payment: NT30

Save your entries.

5. Creating Product

In this section we will create a Product,TB1BIT-50 to run the Product Master Data Distribution

scenario.

Procedure

1. Access transaction MM01

Page 26: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 26

Field Values:

Material: TB1BIT-50

Industry Sector (select from combo box): Retail

Material Type (select from combo box): Finished Product

Screen Shot:

Select Continue.

2. Select Views screen.

In the Select Views screen select the following lines:

- Basic Data 1

- Sales: Sales Org. Data 1

- Sales: General/Plant Data

As showed in the following screen shot.

Page 27: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 27

Scroll down and select the next two views as well:

Page 28: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 28

Select Continue.

3. Organizational Levels screen

After selecting “Continue” the Organizational Levels screen will pop-up. The values to enter are: Plant: 3000

Sales Org.: 3000

Distr. Channel: 10

As indicated in the following screen:

Page 29: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 29

Select Continue.

4. Basic Data Tab

Field Values: Description: Material TB1BIT 50

Base Unit of Measure: KG

Material Group: 012

Gross weight: 20

Net weight: 15

Size/Dimensions: 442 * 421 * 109 MM

As showed in the following screen:

Page 30: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 30

Select Tab “Sales: Sales Org 1”

5. Tab “Sales: Sales Org 1”

In this screen we just need to fill one column of the matrix (Tax Classification). It is indicated in white color:

Country Country Tax Category Tax Category Tax Classification

Tax Classification

CA Canada CTX1 GST (Canada) 0 No tax CA Canada CTX2 PST (Canada) 0 No tax

CA Canada

CTX3 PST-Que & Mar(Base+)

0 No tax

US United States UTXJ Tax Jurisdict.Code

1 Taxable

Page 31: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 31

6. Access the Conditions screen.

Press the “Conditions” button.

In the Matrix enter the following values:

Scale Quantity: 1

Amount: 10

As showed in the screen shot:

Page 32: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 32

Save your entries. ( )

Page 33: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 33

Save your entries. ( )

7. Access the Accounting 1 Tab.

Enter the following values:

Price Control: S

Standard Price: 15

As showed in the next screen:

Page 34: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 34

Save your entries. ( )

Page 35: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 35

Creating Purchase Order types

In this configuration step, you define the possible order types that indicate how a customer has transmitted an order. When it processes a sales document, through integration the system enters the purchase order type into the item level of the purchase order. If you want to run both scenarios in the same environment, the purchase order type is used to distinguish between Sales from Local Stock and Sales from Central Stock. The purchase order type – INT or EXT – is set by BIU logic to R/3 sales order and transmitted via IDoc for R/3 shipping notification. BIU Delivery2GR can now distinguish whether to create a draft goods receipt for the Sales from Local Stock scenario or goods receipt for the Sales from Central Stock scenario

Procedure

1. Access transaction SPRO

Open the following path: Sales and Distribution Sales Sales Documents Sales Documents

Header Define Purchase Order Types

As in the next screen:

Page 36: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 36

2. Adding the entries

Press the Button and type the following values in the corresponding fields:

1st entry:

Pur.ord type: INT

Description: Delivery to Subs

2nd Entry:

Pur.ord type: EXT

Description: Delivery to Customer

As in the next screen:

Save your entries. ( )

Page 37: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 37

Maintaining Output Types for Sales Documents

The Output Determination component offers output functions for sales, shipping, and billing. Subsidiary connectivity via SAP Business One Integration Technology needs additional output processing settings for sending out sales orders, deliveries and billing documents using Application Link Enabling (ALE).

Procedure

1. Access the transaction.

Transaction Code: V/30 IMG step: Sales and Distribution → Basic Functions → Output Control → Output Determination

→ Output Determination Using Condition Technique → Maintain Output Determination for Sales

Documents → Maintain Output types

Change to Edit mode. Press .

Choose New entries. Press

2. Details of Added Entries screen

In this screen make the following entries: Output Type: YBA0

Description: Order Confir. Sub.

3. General Data Tab.

In the General data tab make the following entries: Access Sequence: 0003

Access to conditions: Select checkbox

Multiple issuing: Select checkbox

Page 38: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 38

4. Default Values Tab.

Select the Default values tab and make the following entries: Dispatch time: Send immediately (when saving the application)

Transmission: medium Distribution (ALE)

Partner Function: SP

Page 39: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 39

7. In the Dialog Structure screen, choose Processing routines (double click).

8. Choose New entries.

9. On the New Entries: Details of Added Entries screen make the following entries:

Transm. Medium: A

Program: RSNASTED

FORM routine: ALE_PROCESSING

Page 40: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 40

10. In the Dialog Structure screen (double click), choose Partner functions.

11. Choose new entries.

12. On the New Entries: Details of Added Entries screen make the following entries:

Medium: Distribution (ALE)

Function: SP

Page 41: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 41

Save your entries. ( )

Page 42: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 42

Maintaining Output Determination for Sales Documents

Prerequisite

The output type for sending the order confirmation to a subsidiary, for example, YBA0, is already created.

Procedure

Access the transaction by accessing the IMG step:

Sales and Distribution → Basic Functions → Output Control → Output Determination → Output

Determination Using Condition Technique → Maintain Output Determination for Sales

Documents → Maintain Output Determination Procedure

If you use standard output procedure for your sales order On the Change View “Procedures”:

Overview screen, select the entry V10000 Order Output.

Select the entry V10000 Order Output. 1. In the Dialog Structure screen, choose Control Data by double clicking.

2. Select New Entries.

3. On the New Entries: Overview of Added Entries screen, make the following entries:

Step: 110 (or any other available number)

CNTR: 0

CType: YBA0

Requirement: 2

Page 43: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 43

3. Save your entries. ( )

Page 44: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 44

Maintaining Output Types for Outbound Deliveries

The Output Determination component offers output functions for sales, shipping, and billing. Subsidiary connectivity via SAP Business One Integration Technology needs additional output processing settings for sending out sales orders, deliveries and billing documents using Application Link Enabling (ALE).

Procedure

1. Access the transaction.

Transaction Code: V/34 IMG step: Logistics Execution → Shipping → Basic Shipping Functions → Output Control →

Output Determination → Maintain Output Determination for Outbound Deliveries → Maintain

Output types

Change to Edit mode. Press .

Choose New entries. Press

2. Details of Added Entries screen

In this screen make the following entries: Output Type: YLAV

Description: Shipping Note to Sub.

3. General Data Tab.

In the General data tab make the following entries: Access Sequence: 0008

Access to conditions: Select checkbox

Page 45: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 45

4. Default Values Tab.

Select the Default values tab and make the following entries: Dispatch time: Send immediately (when saving the application)

Transmission: medium Distribution (ALE)

Partner Function: SH

Page 46: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 46

7. In the Dialog Structure screen, select Processing routines (double click).

8. Choose New entries.

9. On the New Entries: Details of Added Entries screen make the following entries:

Transm. Medium: A

Program: RSNASTED

FORM routine: ALE_PROCESSING

Page 47: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 47

10. In the Dialog Structure screen (double click), choose Partner functions.

11. Choose new entries.

12. On the New Entries: Details of Added Entries screen make the following entries:

Medium: Distribution (ALE)

Function: SH

Page 48: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 48

Save your entries. ( )

Page 49: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 49

Maintaining Output Determination for Outbound Deliveries

Prerequisite

The output type for sending out the shipping notification to the subsidiary, for example, YLAV, was created.

Procedure

Access the transaction by accessing the IMG step:

Logistics Execution → Shipping → Basic Shipping Functions → Output Control → Output Determination → Maintain Output Determination for Outbound Deliveries → Maintain Output Determination Procedure

If you use standard output procedure for your sales order On the Change View “Procedures”: Overview screen, select the entry V10000 Header Output.

Select the entry V10000 Header Output. 1. In the Dialog Structure screen, choose Control Data by double clicking.

2. Select New Entries.

3. On the New Entries: Overview of Added Entries screen, make the following entries:

Step: 150 (or any other available number)

CNTR: 0

CType: YLAV

Page 50: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 50

3. Save your entries. ( )

Page 51: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 51

Maintaining Output Types for Billing Documents

The Output Determination component offers output functions for sales, shipping, and billing. Subsidiary connectivity via SAP Business One Integration Technology needs additional output processing settings for sending out sales orders, deliveries and billing documents using Application Link Enabling (ALE).

Procedure

1. Access the transaction.

Transaction Code: V/40 IMG step: Sales and Distribution → Basic Functions → Output Control → Output Determination

→ Output Determination Using Condition Technique → Maintain Output Determination for Billing

Documents → Maintain Output types

Change to Edit mode. Press .

Choose New entries. Press

2. Details of Added Entries screen

In this screen make the following entries: Output Type: YRD0

Description: Invoice to Sub.

3. General Data Tab.

In the General data tab make the following entries: Access Sequence: 0004

Access to conditions: Select checkbox

Page 52: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 52

4. Default Values Tab.

Select the Default values tab and make the following entries: Dispatch time: Send immediately (when saving the application)

Transmission: medium Distribution (ALE)

Partner Function: BP

Page 53: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 53

7. In the Dialog Structure screen, select Processing routines (double click).

8. Choose New entries.

9. On the New Entries: Details of Added Entries screen make the following entries:

Transm. Medium: A

Program: RSNASTED

FORM routine: ALE_PROCESSING

Page 54: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 54

10. In the Dialog Structure screen (double click), choose Partner functions.

11. Choose new entries.

12. On the New Entries: Details of Added Entries screen make the following entries:

Medium: Distribution (ALE)

Function: BP

Page 55: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 55

Save your entries. ( )

Page 56: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 56

Maintaining Output Determination for Billing Documents

Prerequisite

The output type was created for sending out the invoice to the subsidiary, for example, YRD0.

Procedure

Access the transaction by accessing the IMG step:

Sales and Distribution → Basic Functions → Output Control → Output Determination → Output

Determination Using Condition Technique → Maintain Output Determination for Billing

Documents → Maintain Output Determination Procedure

If you use standard output procedure for your sales order On the Change View “Procedures”: Overview screen, select the entry V10000 Billing Output. Select the entry V10000 Billing Output. 1. In the Dialog Structure screen, choose Control Data by double clicking.

2. Select New Entries.

3. On the New Entries: Overview of Added Entries screen, make the following entries:

Step: 200 (or any other available number)

CNTR: 0

CType: YRD0

Page 57: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 57

3. Save your entries. ( )

Result

All steps in the SAP R/3 Implementation Guide (IMG) to maintain the output types and output determination to the needs of subsidiary connectivity solution are now completed. The sales document-, outbound delivery-, and billing document output types are created and assigned to the respective output determination procedures.

Page 58: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 58

Changing Partner Profiles

For ALE communication to take place, the partners must be defined with inbound or outbound parameters. This is already done by generating the partner profiles. However, some values might not be applicable to this scenario and must be changed manually. Access transaction: WE20. On the left side of the screen expand sub tree Partner type LS (Logical system).

1. Select the entry for the logical system maintained for SAP Business One Integration Technology. In our case B1II00 2. On the right hand side of the window select in the section Outbound parameter, select the message type ORDERS. As showed in the next screen:

3. To view the details, choose DetailScreenOutb. Parameter (lens icon).

Page 59: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 59

4. Go to the Message Control tab and make the following entries:

Application: V1 Message type: YBA0 Process Code: SD10

5. Save your entries. ( )

6. Choose Back. ( )

Page 60: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 60

7. Repeat the steps above to create the following entries described in the table.

Tab strip – Outbound options

Tab strip – Message Control

Message

Type Outbound

Param. Basic Type Application Message

Type Process Code

DESADV Transfer IDOC immediately

DELVRY03 V2 YLAV DELV

INVOIC Transfer IDOC immediately

INVOIC02 V3 YRD0 SD09

SYNCH Transfer IDOC immediately

SYNCHRON <Blank> <Blank> <Blank>

After successfully checking or changing the outbound parameters, you must also perform the

following steps for the inbound parameters:

On the second matrix which contains the Inbound parameter, select the message type

ORDERS.

8. To view the details, choose Detail Screen Inbound Parameter ( ).

Page 61: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 61

9.Inbound options tab

Make the following entries:

Process Code: ORDE Trigger immediately: Select the radio button

Page 62: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 62

Page 63: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 63

Creating Output Condition Records for the Sales Document

The Output Determination component offers output functions for sales, shipping, and billing. Output processing settings using Application Link Enabling (ALE) are necessary for sending out sales orders, deliveries and billing documents to SAP Business One Integration Technology.

Prerequisites

The distribution model and partner profiles were set up successfully. A customer master record for sales process from headquarters to subsidiaries was created.

Procedure ...

1. Access the transaction VV11 or via

SAP MENU: Logistics →Sales and Distribution → Master Data → Output → Sales

document → create

2. On the Create Output – Condition Records: Sales screen, make the following entries: Output type: YBA0

Page 64: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 64

3. Choose Enter. The Create Condition Records (Order Confirmation): Fast Entry screen appears. 4. On the Create Condition Records (Order Confirmation): Fast Entry screen, make the following entries: Sales organization: 3000

Customer: 30001 (The one that was created in step 4. Creating Customer )

PartF: SP

Partner: 30001 .

Medium: A

Time: 4

Language: EN

As in the next screen shot:

5. Save your entries. ( )

Page 65: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 65

Creating Output Condition Records for the Delivery

The Output Determination component offers output functions for sales, shipping, and billing. Output processing settings using Application Link Enabling (ALE) are necessary for sending out sales orders, deliveries and billing documents to SAP Business One Integration Technology.

Prerequisites

The distribution model and partner profiles were set up successfully. A customer master record for sales process from headquarters to subsidiaries was created.

Procedure ...

2. Access the transaction VV21 or via

SAP MENU: Logistics →Sales and Distribution → Master Data → Output → Shipping →

create

2. On the Create Output – Condition Records: Shipping screen, make the following entries: Output type: YLAV

3. Choose Enter. The Create Condition Records (Shipping Note to Sub.): Fast Entry screen appears.

Page 66: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 66

4. On the Create Condition Records (Shipping Note to Sub.): Fast Entry screen, make the

following entries:

Sales organization: 3000

Customer: 30001 ((The one that was created in step 4. Creating Customer)

PartF: SH

Partner: 30001

Medium: A

Time: 4

Language: EN

As in the next screen shot:

5. Save your entries. ( )

Page 67: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 67

Creating Output Condition Records for the Invoice

The Output Determination component offers output functions for sales, shipping, and billing. Output processing settings using Application Link Enabling (ALE) are necessary for sending out sales orders, deliveries and billing documents to SAP Business One Integration Technology.

Prerequisites

The distribution model and partner profiles were set up successfully. A customer master record for sales process from headquarters to subsidiaries was created.

Procedure ...

3. Access the transaction VV31 or via

SAP MENU: Logistics →Sales and Distribution → Master Data → Output →Billing

document → create

2. On the Create Output – Condition Records: Billing screen, make the following entries: Output type: YRD0

3. Choose Enter. The Create Condition Records (Invoice to Sub.): Fast Entry screen appears. 4. On the Create Condition Records (Invoice to Sub.): Fast Entry screen, make the following entries:

Page 68: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 68

Sales organization: 3000

Customer: 30001 (The one that was created in step 4. Creating Customer).

PartF: SH

Partner: 30001

Medium: A

Time: 4

Language: EN

As in the next screen shot:

5. Save your entries. ( )

Page 69: B1 on netweaver

R/3 Configuration to run SAP Business One Integration for SAP NetWeaver Scenarios

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2006 SAP AG 69

Related Content

• SAP Business One Version 2005 integration for SAP NetWeaver

Copyright

© Copyright 2006 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, 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, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, 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 Web Consortium, 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 and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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 in several other countries all over the world. 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. These materials are provided “as is” without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. Any software coding and/or code lines/strings (“Code”) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.